RFC 5061
E590632
RFC 5061 is an Internet Engineering Task Force (IETF) specification that extends and enhances the Stream Control Transmission Protocol (SCTP), particularly for dynamic address reconfiguration and improved transport flexibility.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5061 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6408896 — 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 5061 Context triple: [RFC 4960, updatedBy, RFC 5061]
-
A.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
B.
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.
-
C.
RFC 5011
RFC 5011 is an Internet standard that specifies automated trust anchor rollover mechanisms for DNSSEC to simplify and secure key management in the Domain Name System.
-
D.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
-
E.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
- 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 5061 Target entity description: RFC 5061 is an Internet Engineering Task Force (IETF) specification that extends and enhances the Stream Control Transmission Protocol (SCTP), particularly for dynamic address reconfiguration and improved transport flexibility.
-
A.
RFC 5661
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
B.
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.
-
C.
RFC 5011
RFC 5011 is an Internet standard that specifies automated trust anchor rollover mechanisms for DNSSEC to simplify and secure key management in the Domain Name System.
-
D.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
-
E.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| appliesTo |
SCTP associations
ⓘ
SCTP endpoints ⓘ |
| area | Transport ⓘ |
| category | Standards Track ⓘ |
| defines |
ASCONF chunk
ⓘ
ASCONF-ACK chunk NERFINISHED ⓘ Address Configuration Change (ASCONF) procedures ⓘ SCTP Dynamic Address Reconfiguration NERFINISHED ⓘ error handling for dynamic address reconfiguration ⓘ procedures for adding IP addresses to an SCTP association ⓘ procedures for changing the primary path of an SCTP association ⓘ procedures for deleting IP addresses from an SCTP association ⓘ |
| definesFor |
IPv4
ⓘ
IPv6 NERFINISHED ⓘ |
| definesMechanism |
in-band control of address reconfiguration
ⓘ
secure reconfiguration of SCTP transport addresses ⓘ |
| documentType | Internet Standard-track specification ⓘ |
| extends | RFC 2960 NERFINISHED ⓘ |
| focusesOn |
dynamic address reconfiguration
ⓘ
multihoming support in SCTP ⓘ transport-layer flexibility ⓘ |
| intendedAudience |
implementers of SCTP stacks
ⓘ
network engineers ⓘ protocol designers ⓘ |
| language | English ⓘ |
| obsoletes | none ⓘ |
| protocolLayer | transport layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| purpose |
to allow SCTP endpoints to add and remove transport addresses without restarting associations
ⓘ
to improve transport flexibility for SCTP endpoints ⓘ to support dynamic reconfiguration of IP addresses in existing SCTP associations ⓘ |
| relatedTo |
RFC 2960
ⓘ
RFC 4960 NERFINISHED ⓘ SCTP multihoming ⓘ |
| securityConsiderations |
discusses authentication of address reconfiguration messages
ⓘ
discusses protection against hijacking via address reconfiguration ⓘ |
| standardizes | signaling for address configuration changes in SCTP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration NERFINISHED ⓘ |
| updatesProtocol |
SCTP
NERFINISHED
ⓘ
Stream Control Transmission Protocol 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 5061 Description of subject: RFC 5061 is an Internet Engineering Task Force (IETF) specification that extends and enhances the Stream Control Transmission Protocol (SCTP), particularly for dynamic address reconfiguration and improved transport flexibility.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.