RFC 5072
E875729
RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5072 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10628728 — 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 5072 Context triple: [RFC 1661, obsoletedBy, RFC 5072]
-
A.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
B.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
E.
RFC 7672
RFC 7672 is an Internet standards document that specifies how to use DNS-Based Authentication of Named Entities (DANE) with SMTP to provide secure email transport.
- 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 5072 Target entity description: RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
-
A.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
B.
RFC 4172
RFC 4172 is an IETF standards document that specifies the Internet Fibre Channel Protocol (iFCP), enabling the transport of Fibre Channel frames over IP networks.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 7472
RFC 7472 is an Internet Engineering Task Force (IETF) specification that defines extensions and mechanisms for the Internet Printing Protocol (IPP), enhancing network printing capabilities and interoperability.
-
E.
RFC 7672
RFC 7672 is an Internet standards document that specifies how to use DNS-Based Authentication of Named Entities (DANE) with SMTP to provide secure email transport.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
PPP links over various physical media
ⓘ
dial-up PPP connections ⓘ point-to-point links ⓘ tunneled PPP links ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
|
| category | Standards Track ⓘ |
| defines |
IANA considerations for IPv6CP code and option values
ⓘ
IPv6 Control Protocol for PPP ⓘ IPv6 interface identifier negotiation over PPP ⓘ IPv6 packet encapsulation over PPP ⓘ IPv6CP code and option types ⓘ IPv6CP configuration option formats ⓘ IPv6CP state machine behavior ⓘ Maximum Receive Unit (MRU) considerations for IPv6 over PPP ⓘ PPP IPv6 Control Protocol (IPv6CP) options ⓘ requirements for IPv6 over PPP interoperability ⓘ security considerations for IPv6 over PPP ⓘ |
| intendedAudience |
network operators
ⓘ
network protocol implementers ⓘ standards developers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2472 ⓘ |
| partOf | IPv6 standards suite ⓘ |
| protocolSpecified |
IPv6 over PPP
ⓘ
linked to:
IPv6 Control Protocol for PPP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedProtocol |
IPv6
ⓘ
PPP ⓘ Point-to-Point Protocol ⓘ |
| shortName |
IPv6CP
ⓘ
linked to:
IPv6 Control Protocol for PPP
|
| specifies |
IPv6CP configuration and termination
ⓘ
IPv6CP error handling ⓘ IPv6CP negotiation procedures ⓘ IPv6CP option negotiation for compression (if used) ⓘ IPv6CP option negotiation for interface identifiers ⓘ IPv6CP packet formats ⓘ interaction of IPv6CP with PPP LCP ⓘ link-local IPv6 address formation on PPP links ⓘ transmission of IPv6 packets over PPP links ⓘ use of PPP Network Control Protocol for IPv6 ⓘ |
| standardizes |
IPv6CP option type values
ⓘ
PPP protocol field value for IPv6 ⓘ |
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | IP Version 6 over PPP ⓘ |
| updates | RFC 1661 ⓘ |
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 5072 Description of subject: RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.