RFC 6635
E700361
RFC 6635 is an Internet Engineering Task Force (IETF) document that specified earlier technical standards or procedures later superseded and refined by RFC 8728.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6635 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T7928386 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6635 Context triple: [RFC 8728, obsoletes, RFC 6635]
-
A.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
B.
RFC 4035
RFC 4035 is an Internet standard that specifies the protocol modifications and operational considerations for deploying DNS Security Extensions (DNSSEC) in the Domain Name System.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
-
E.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6635 Target entity description: RFC 6635 is an Internet Engineering Task Force (IETF) document that specified earlier technical standards or procedures later superseded and refined by RFC 8728.
-
A.
RFC 9135
RFC 9135 is an IETF specification that defines procedures and extensions for Ethernet VPN (EVPN) technologies used in modern IP/MPLS networks.
-
B.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
C.
RFC 4035
RFC 4035 is an Internet standard that specifies the protocol modifications and operational considerations for deploying DNS Security Extensions (DNSSEC) in the Domain Name System.
-
D.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
E.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
- F. None of above. chosen
Statements (20)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| category | Standards Track ⓘ |
| defines | IANA registries for PCE ⓘ |
| documentType | Technical standard ⓘ |
| focusesOn | IANA registry structure for PCE ⓘ |
| hasRFCNumber | 6635 ⓘ |
| hasSuccessor | RFC 8728 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 8728 ⓘ |
| partOfSeries |
RFC series
ⓘ
linked to:
RFCs
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
IANA considerations
ⓘ
PCE communication protocol ⓘ Path Computation Element ⓘ |
| standardizationOrganization |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Obsoleted ⓘ |
| updatesStatusOf | PCE-related IANA registries ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 6635 Description of subject: RFC 6635 is an Internet Engineering Task Force (IETF) document that specified earlier technical standards or procedures later superseded and refined by RFC 8728.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.