RFC 6096
E590633
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6096 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6408897 — 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 6096 Context triple: [RFC 4960, updatedBy, RFC 6096]
-
A.
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.
-
B.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
C.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
D.
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.
-
E.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
- 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 6096 Target entity description: RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
-
A.
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.
-
B.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
C.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
D.
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.
-
E.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
- F. None of above. chosen
Statements (35)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
standards-track document ⓘ |
| appliesTo | SCTP implementations ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| clarifies | use of flags in SCTP chunk headers ⓘ |
| defines |
IANA registry for SCTP chunk flags
NERFINISHED
ⓘ
SCTP chunk flags registration procedure ⓘ |
| format |
PDF
ⓘ
text ⓘ |
| isAbout | control information in SCTP chunks ⓘ |
| language | English ⓘ |
| number | 6096 ⓘ |
| obsoletes | none ⓘ |
| protocol | Stream Control Transmission Protocol NERFINISHED ⓘ |
| protocolAbbreviation | SCTP NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| refines | SCTP specification in RFC 4960 ⓘ |
| registryManagedBy |
IANA
NERFINISHED
ⓘ
Internet Assigned Numbers Authority NERFINISHED ⓘ |
| relation | part of the SCTP standards family ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifies | IANA considerations for SCTP chunk flags ⓘ |
| standardizes | allocation of SCTP chunk flag bits ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Internet protocols
ⓘ
SCTP extensions ⓘ transport protocols ⓘ |
| title | Stream Control Transmission Protocol (SCTP) Chunk Flags Registration NERFINISHED ⓘ |
| type | technical specification ⓘ |
| updates | RFC 4960 ⓘ |
| workingGroup | Transport Area 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 6096 Description of subject: RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.