RFC 6121
E233819
RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6121 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T2114330 — 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 6121 Context triple: [XMPP, hasCoreSpecification, RFC 6121]
-
A.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
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 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
E.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
- 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 6121 Target entity description: RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
-
A.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
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 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
E.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| appliesTo |
XMPP clients
ⓘ
XMPP servers ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
instant messaging semantics for XMPP
ⓘ
presence semantics for XMPP ⓘ |
| definesConcept |
XMPP roster
ⓘ
chat session semantics ⓘ directed presence ⓘ error conditions for XMPP IM and presence ⓘ message types in XMPP IM ⓘ offline message handling ⓘ presence stanzas in XMPP ⓘ presence subscription states ⓘ |
| definesMechanism |
XMPP instant messaging
ⓘ
XMPP presence ⓘ error handling for XMPP IM and presence ⓘ message delivery semantics ⓘ message routing rules ⓘ presence subscription model ⓘ roster management ⓘ |
| definesProtocol |
core instant messaging functionality for XMPP
ⓘ
core presence functionality for XMPP ⓘ |
| documentType | Internet Standards Track RFC ⓘ |
| focusesOn | client-to-server instant messaging and presence semantics ⓘ |
| intendedUse | standardization of interoperable instant messaging and presence over XMPP ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3921 ⓘ |
| partOfSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| protocolAcronym | XMPP ⓘ |
| protocolFamily |
Extensible Messaging and Presence Protocol
ⓘ
linked to:
XMPP
|
| protocolLayer | application layer ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
RFC 6120
ⓘ
RFC 6122 ⓘ |
| rfcNumber | 6121 ⓘ |
| standardizes |
core features of XMPP-based instant messaging
ⓘ
core features of XMPP-based presence ⓘ |
| standardsTrack | Proposed Standard ⓘ |
| status | Internet Standard Track document ⓘ |
| title |
XMPP: Instant Messaging and Presence
ⓘ
linked to:
XMPP
|
| updates | RFC 3921 ⓘ |
| usesTransport | XMPP streams defined in RFC 6120 ⓘ |
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 6121 Description of subject: RFC 6121 is an IETF standard that defines the core instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.