RFC 7053
E590634
RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7053 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6408898 — 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 7053 Context triple: [RFC 4960, updatedBy, RFC 7053]
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- 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 7053 Target entity description: RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
B.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standards-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | SCTP-NAT Support ⓘ |
| addresses | SCTP operation through NATs ⓘ |
| area | Transport ⓘ |
| category | Standards Track ⓘ |
| concerns | NAT traversal for SCTP ⓘ |
| defines |
SCTP NAT traversal mechanisms
ⓘ
SCTP Network Address Translation support ⓘ procedures for SCTP endpoints interacting with NATs ⓘ requirements for SCTP-aware NATs ⓘ |
| documentType | technical specification ⓘ |
| extendsSpecificationDefinedIn | RFC 4960 NERFINISHED ⓘ |
| extendsSpecificationOf | Stream Control Transmission Protocol NERFINISHED ⓘ |
| focusesOn |
middlebox interaction with SCTP
ⓘ
multi-homing aspects in NAT environments ⓘ |
| format |
PDF
ⓘ
text ⓘ |
| hasDOI | 10.17487/RFC7053 ⓘ |
| hasKeyword |
NAT
ⓘ
SCTP NERFINISHED ⓘ middlebox ⓘ multi-homing ⓘ transport protocol ⓘ |
| hasNumber | 7053 ⓘ |
| hasRFCEditorURL | https://www.rfc-editor.org/rfc/rfc7053 ⓘ |
| isPartOfSeries | RFC 7000–7099 ⓘ |
| language | English ⓘ |
| networkLayer | transport layer ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| organization | IETF NERFINISHED ⓘ |
| protocolFamily | SCTP NERFINISHED ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| publishedIn | January 2014 ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatesToProtocol | Stream Control Transmission Protocol NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| standardizes |
behavior of SCTP endpoints in presence of NATs
ⓘ
behavior of SCTP-aware NATs ⓘ |
| status | Proposed Standard ⓘ |
| stream | Transport Area ⓘ |
| title | SCTP-NAT Support for the Stream Control Transmission Protocol NERFINISHED ⓘ |
| updates | RFC 4960 ⓘ |
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 7053 Description of subject: RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends 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.