RFC 4120
E718989
RFC 4120 is the IETF specification that defines the Kerberos Network Authentication Service protocol used for secure, ticket-based authentication in distributed systems.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4120 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8216206 — 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 4120 Context triple: [Kerberos, standardizedAs, RFC 4120]
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
C.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
D.
RFC 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- 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 4120 Target entity description: RFC 4120 is the IETF specification that defines the Kerberos Network Authentication Service protocol used for secure, ticket-based authentication in distributed systems.
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
C.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
D.
RFC 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| definesComponent |
Authentication Service
ⓘ
Kerberos application server NERFINISHED ⓘ Kerberos client NERFINISHED ⓘ Key Distribution Center NERFINISHED ⓘ Ticket-Granting Service NERFINISHED ⓘ |
| definesDataFormat |
Kerberos principal names
NERFINISHED
ⓘ
Kerberos realm names ⓘ authorization data ⓘ checksum structures ⓘ encrypted data fields ⓘ encryption type identifiers ⓘ host addresses ⓘ transited encoding ⓘ |
| definesMessageType |
AP-REP
NERFINISHED
ⓘ
AP-REQ NERFINISHED ⓘ AS-REP NERFINISHED ⓘ AS-REQ NERFINISHED ⓘ KRB-ERROR NERFINISHED ⓘ TGS-REP NERFINISHED ⓘ TGS-REQ NERFINISHED ⓘ |
| definesProtocol | Kerberos Network Authentication Service NERFINISHED ⓘ |
| definesProtocolVersion | Kerberos version 5 NERFINISHED ⓘ |
| focusesOn |
distributed systems security
ⓘ
network authentication ⓘ ticket-based authentication ⓘ |
| obsoletes | RFC 1510 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| standardizes |
Kerberos error codes
ⓘ
Kerberos message formats ⓘ Kerberos protocol exchanges ⓘ Kerberos ticket structure ⓘ |
| status | Internet Standard ⓘ |
| supportsFeature |
clock skew tolerance
ⓘ
cross-realm authentication ⓘ mutual authentication ⓘ replay protection ⓘ single sign-on ⓘ |
| title | The Kerberos Network Authentication Service (V5) NERFINISHED ⓘ |
| usesConcept |
authenticators
ⓘ
principals ⓘ realms ⓘ session keys ⓘ tickets ⓘ |
| usesCryptography | symmetric key cryptography ⓘ |
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 4120 Description of subject: RFC 4120 is the IETF specification that defines the Kerberos Network Authentication Service protocol used for secure, ticket-based authentication in distributed systems.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.