RFC 5172
E877707
RFC 5172 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier PPP specifications to define enhanced cryptographic and security mechanisms for Point-to-Point Protocol connections.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5172 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10628729 — 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 5172 Context triple: [RFC 1661, obsoletedBy, RFC 5172]
-
A.
RFC 5072
RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
-
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 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.
-
D.
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.
-
E.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- 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 5172 Target entity description: RFC 5172 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier PPP specifications to define enhanced cryptographic and security mechanisms for Point-to-Point Protocol connections.
-
A.
RFC 5072
RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
-
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 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.
-
D.
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.
-
E.
RFC 8552
RFC 8552 is an Internet Engineering Task Force (IETF) standards document that specifies technical protocols and procedures used in Internet communications.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| aimsTo |
enhance security of PPP authentication
ⓘ
provide stronger cryptographic protection for PPP EAP ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
HMAC-based authentication for PPP EAP
ⓘ
PPP EAP authentication method using keyed hash message authentication codes ⓘ PPP EAP authentication using keyed message digests ⓘ negotiation of HMAC algorithms within EAP over PPP ⓘ |
| focusesOn |
cryptographic authentication mechanisms
ⓘ
keyed hash message authentication codes ⓘ security mechanisms for PPP connections ⓘ |
| hasAbbreviation | RFC 5172 ⓘ |
| intendedFor |
PPP links
ⓘ
PPP-based network access authentication ⓘ |
| language | English ⓘ |
| medium | electronic document ⓘ |
| obsoletes | RFC 2716 ⓘ |
| organization |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| partOf |
RFC series
ⓘ
linked to:
RFC Series Working Group
|
| protocol |
EAP
ⓘ
PPP Extensible Authentication Protocol ⓘ
linked to:
Extensible Authentication Protocol
Point-to-Point Protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| standardizes |
HMAC algorithm negotiation for PPP EAP
ⓘ
use of HMAC for EAP authentication over PPP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| subject |
EAP
ⓘ
HMAC ⓘ PPP ⓘ link-layer authentication ⓘ network security ⓘ |
| title | Negotiation for Keyed Hash Message Authentication Code (HMAC) Authentication within PPP Extensible Authentication Protocol (EAP) ⓘ |
| updates |
RFC 1994
ⓘ
RFC 2716 ⓘ RFC 3748 ⓘ |
| uses |
HMAC
ⓘ
keyed hash functions ⓘ |
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 5172 Description of subject: RFC 5172 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier PPP specifications to define enhanced cryptographic and security mechanisms for Point-to-Point Protocol connections.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.