RFC 3921
E846652
RFC 3921 is an Internet standard that originally specified instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3921 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10158009 — 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 3921 Context triple: [RFC 6121, updates, RFC 3921]
-
A.
RFC 3920
RFC 3920 is the original specification that defined the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP) before being superseded by RFC 6120.
-
B.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
C.
RFC 5721
RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
- 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 3921 Target entity description: RFC 3921 is an Internet standard that originally specified instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
-
A.
RFC 3920
RFC 3920 is the original specification that defined the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP) before being superseded by RFC 6120.
-
B.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
-
C.
RFC 5721
RFC 5721 was an Internet standards document that defined an earlier approach to email-related functionality before being superseded by RFC 6856.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation | XMPP IM NERFINISHED ⓘ |
| appliesTo |
XMPP clients
ⓘ
XMPP servers ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
XML stanza usage for IM and presence in XMPP
ⓘ
delivery semantics for XMPP instant messages ⓘ directed presence behavior in XMPP ⓘ error handling for XMPP IM and presence ⓘ instant messaging for XMPP ⓘ message archiving semantics in XMPP IM ⓘ message routing rules for XMPP IM ⓘ message types for XMPP IM ⓘ offline message handling in XMPP ⓘ presence for XMPP ⓘ presence subscription states in XMPP ⓘ privacy list interaction with IM and presence in XMPP ⓘ resource binding behavior relevant to IM and presence ⓘ roster item semantics in XMPP ⓘ roster management for XMPP ⓘ subscription semantics for XMPP presence ⓘ |
| focusesOn | application semantics of XMPP for IM and presence ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 6120
NERFINISHED
ⓘ
RFC 6121 NERFINISHED ⓘ |
| organization | Internet Engineering Task Force NERFINISHED ⓘ |
| protocol | Extensible Messaging and Presence Protocol NERFINISHED ⓘ |
| protocolFamily | XMPP core and extensions ⓘ |
| relatedTo |
RFC 3920
NERFINISHED
ⓘ
RFC 6120 ⓘ RFC 6121 NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| standardizes |
client-to-server instant messaging behavior in XMPP
ⓘ
presence subscription and notification in XMPP ⓘ server-to-server instant messaging behavior in XMPP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Internet messaging protocols
ⓘ
instant messaging ⓘ presence ⓘ |
| title | Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence NERFINISHED ⓘ |
| updates | RFC 3920 NERFINISHED ⓘ |
| workingGroup | XMPP Working Group NERFINISHED ⓘ |
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 3921 Description of subject: RFC 3921 is an Internet standard that originally specified instant messaging and presence functionality for the Extensible Messaging and Presence Protocol (XMPP).
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.