RFC 2960
E590631
RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2960 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6408895 — 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 2960 Context triple: [RFC 4960, obsoletes, RFC 2960]
-
A.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
B.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
C.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
D.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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 2960 Target entity description: RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
-
A.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
B.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
C.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
D.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| abbreviation | SCTP NERFINISHED ⓘ |
| area | Transport Area NERFINISHED ⓘ |
| associationModel | connection-oriented association ⓘ |
| category | Transport ⓘ |
| defines | Stream Control Transmission Protocol NERFINISHED ⓘ |
| definesTerm |
SCTP association
ⓘ
SCTP stream ⓘ stream sequence number ⓘ transmission sequence number ⓘ verification tag ⓘ |
| designGoal |
avoid head-of-line blocking seen in TCP
ⓘ
provide robust multi-homing support ⓘ support telephony signaling over IP ⓘ |
| intendedUse |
general Internet use
ⓘ
telephony signaling transport ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4960 NERFINISHED ⓘ |
| organization | Network Working Group NERFINISHED ⓘ |
| protocolLayer | transport layer ⓘ |
| protocolType | message-oriented transport protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
TCP
NERFINISHED
ⓘ
UDP NERFINISHED ⓘ |
| specifies |
SCTP association setup and teardown
ⓘ
SCTP congestion control mechanisms ⓘ SCTP error handling ⓘ SCTP flow control mechanisms ⓘ SCTP packet structure ⓘ SCTP security considerations ⓘ |
| standardizes |
SCTP control chunks
ⓘ
SCTP data chunks ⓘ SCTP header format ⓘ |
| status | Proposed Standard ⓘ |
| streamCountCapability | multiple independent streams per association ⓘ |
| supportsFeature |
congestion control
ⓘ
multi-homing ⓘ multi-streaming ⓘ ordered and unordered delivery ⓘ path failover ⓘ reliable data transfer ⓘ |
| title | Stream Control Transmission Protocol NERFINISHED ⓘ |
| transportServiceFor | IP networks ⓘ |
| updates | none ⓘ |
| uses | chunk-based message format ⓘ |
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 2960 Description of subject: RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.