RFC 3920
E845092
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3920 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T10157960 — 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 3920 Context triple: [RFC 6120, obsoletes, RFC 3920]
-
A.
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.
-
B.
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.
-
C.
RFC 4120
RFC 4120 is the IETF specification that defines the Kerberos Network Authentication Service protocol used for secure, ticket-based authentication in distributed systems.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 3977
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
- 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 3920 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
RFC 4120
RFC 4120 is the IETF specification that defines the Kerberos Network Authentication Service protocol used for secure, ticket-based authentication in distributed systems.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 3977
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments
ⓘ
technical standard ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
XML streaming framework for XMPP
ⓘ
XMPP core ⓘ
linked to:
XMPP
authentication framework for XMPP ⓘ |
| definesConcept |
XMPP client-to-server communication
ⓘ
XMPP error stanzas ⓘ XMPP resource binding ⓘ XMPP server-to-server communication ⓘ XMPP stanza routing ⓘ XMPP stream negotiation ⓘ |
| definesNamespace |
jabber:client
ⓘ
jabber:server ⓘ urn:ietf:params:xml:ns:xmpp-sasl ⓘ urn:ietf:params:xml:ns:xmpp-streams ⓘ |
| focusesOn |
instant messaging
ⓘ
presence ⓘ |
| intendedFor |
developers of XMPP implementations
ⓘ
protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 6120 ⓘ |
| partOf |
XMPP specification suite
ⓘ
linked to:
IETF XMPP Working Group
|
| protocolFamily |
Extensible Messaging and Presence Protocol
ⓘ
linked to:
XMPP
XMPP ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
Jabber protocol
ⓘ
RFC 3921 ⓘ RFC 6120 ⓘ |
| RFCNumber | 3920 ⓘ |
| securityMechanism |
SASL
ⓘ
TLS ⓘ |
| specifies |
SASL authentication for XMPP
ⓘ
TLS usage for XMPP ⓘ XMPP addressing ⓘ XMPP entities ⓘ XMPP error handling ⓘ XMPP security features ⓘ XMPP streams ⓘ
linked to:
XMPP
|
| standardizes | core XMPP protocol ⓘ |
| status | Obsoleted ⓘ |
| streamingMediaType | text ⓘ |
| title |
Extensible Messaging and Presence Protocol (XMPP): Core
ⓘ
linked to:
XMPP
|
| transportLayer |
TCP
ⓘ
linked to:
Transmission Control Protocol
|
| usesDataFormat | XML ⓘ |
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 3920 Description of subject: 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.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.