RFC 4960
E127656
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.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T1096662 — 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 4960 Context triple: [SCTP, definedInRFC, RFC 4960]
-
A.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
B.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
C.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
D.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- 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 4960 Target entity description: 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.
-
A.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
B.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
C.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
D.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| abbreviation | SCTP specification ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| definesAbbreviation | SCTP ⓘ |
| definesProperty |
SCTP applicability statement
ⓘ
SCTP association management ⓘ SCTP checksum usage ⓘ SCTP chunk types ⓘ SCTP congestion control ⓘ SCTP error handling ⓘ SCTP flow control ⓘ SCTP packet format ⓘ SCTP parameter negotiation ⓘ SCTP path selection ⓘ SCTP retransmission behavior ⓘ SCTP security considerations ⓘ SCTP state machine ⓘ SCTP stream management ⓘ SCTP timers ⓘ association setup and teardown ⓘ congestion control for SCTP ⓘ message-oriented transport ⓘ multi-homing ⓘ multi-streaming ⓘ ordered and unordered delivery ⓘ path management ⓘ reliable message delivery ⓘ |
| intendedStatus | Proposed Standard ⓘ |
| obsoletes | RFC 2960 ⓘ |
| protocolLayer | transport layer ⓘ |
| protocolType | message-oriented ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| rfcNumber | 4960 ⓘ |
| specifiesProtocol |
SCTP
ⓘ
surface form:
Stream Control Transmission Protocol
|
| supportsFeature |
multi-homing with multiple IP addresses per endpoint
ⓘ
multi-streaming within a single association ⓘ partial reliability extensions (via separate RFC) ⓘ path failover ⓘ |
| title |
SCTP
ⓘ
surface form:
Stream Control Transmission Protocol
|
| updatedBy |
RFC 5061
ⓘ
RFC 6096 ⓘ RFC 7053 ⓘ RFC 8260 ⓘ |
| useCase |
reliable message transport over IP networks
ⓘ
telephony signaling transport ⓘ |
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 4960 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
RFC 2960