RFC 6122
E845093
RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6122 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10157974 — 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 6122 Context triple: [RFC 6120, relatedTo, RFC 6122]
-
A.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
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 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
- 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 6122 Target entity description: RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
-
A.
RFC 6062
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
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 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Extensible Messaging and Presence Protocol
NERFINISHED
ⓘ
Jabber identifiers ⓘ XMPP NERFINISHED ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
JID structure
ⓘ
Jabber Identifier format ⓘ XMPP address format ⓘ domainpart of a JID ⓘ localpart of a JID ⓘ resourcepart of a JID ⓘ rules for XMPP address comparison ⓘ rules for XMPP address preparation ⓘ |
| definesTerm |
JID
ⓘ
Jabber Identifier NERFINISHED ⓘ |
| focusesOn | addressing in XMPP ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3920 NERFINISHED ⓘ |
| partOfSeries | RFC NERFINISHED ⓘ |
| protocol |
Extensible Messaging and Presence Protocol
NERFINISHED
ⓘ
XMPP NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatedTo |
RFC 6120
ⓘ
RFC 6121 NERFINISHED ⓘ |
| specifies |
Unicode handling for XMPP addresses
ⓘ
case mapping rules for XMPP localparts ⓘ normalization of XMPP addresses for comparison ⓘ rules for bare JIDs ⓘ rules for full JIDs ⓘ |
| standardizes |
format of XMPP addresses
ⓘ
handling of XMPP addresses ⓘ |
| status | Proposed Standard ⓘ |
| title | Extensible Messaging and Presence Protocol (XMPP): Address Format NERFINISHED ⓘ |
| uses |
IDNA
NERFINISHED
ⓘ
Internationalized Domain Names in Applications NERFINISHED ⓘ stringprep ⓘ |
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 6122 Description of subject: RFC 6122 is an Internet standard that specifies the format and handling of XMPP (Jabber) addresses, defining how identifiers are structured and compared in the Extensible Messaging and Presence Protocol.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.