IETF RFC 3031
E663647
IETF RFC 3031 is the foundational standards document that specifies the architecture and key mechanisms of Multiprotocol Label Switching (MPLS) in IP networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| IETF RFC 3031 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7427830 — 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: IETF RFC 3031 Context triple: [MPLS, definedIn, IETF RFC 3031]
-
A.
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.
-
B.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
C.
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.
-
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 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- 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: IETF RFC 3031 Target entity description: IETF RFC 3031 is the foundational standards document that specifies the architecture and key mechanisms of Multiprotocol Label Switching (MPLS) in IP networks.
-
A.
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.
-
B.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
C.
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.
-
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 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard ⓘ |
| appliesTo |
IP networks
ⓘ
multiprotocol networks ⓘ |
| area | Routing Area ⓘ |
| category | Standards Track ⓘ |
| defines |
Forwarding Equivalence Class
NERFINISHED
ⓘ
Label Edge Router ⓘ Label Switched Path NERFINISHED ⓘ Label Switching Router ⓘ MPLS forwarding model ⓘ MPLS label ⓘ MPLS label stack ⓘ MPLS shim header usage ⓘ Multiprotocol Label Switching architecture NERFINISHED ⓘ conservative label retention ⓘ downstream unsolicited label distribution ⓘ downstream-on-demand label distribution ⓘ independent control ⓘ label distribution control modes ⓘ label merging ⓘ label swapping ⓘ liberal label retention ⓘ ordered control ⓘ penultimate hop popping ⓘ |
| foundationFor |
MPLS VPNs
NERFINISHED
ⓘ
MPLS traffic engineering ⓘ MPLS-based QoS mechanisms ⓘ |
| language | English ⓘ |
| obsoletedBy | IETF RFC 3031bis (work in progress, not yet an RFC as of 2024) NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
IETF RFC 3032
NERFINISHED
ⓘ
IETF RFC 3036 NERFINISHED ⓘ IETF RFC 3209 NERFINISHED ⓘ |
| specifies |
MPLS data plane behavior
ⓘ
MPLS forwarding between Label Switching Routers ⓘ constraints on label distribution protocols ⓘ encapsulation of MPLS labels with network layer packets ⓘ interaction of MPLS with conventional IP routing ⓘ requirements for MPLS-capable routers ⓘ support for multiple network layer protocols over MPLS ⓘ use of label stacks for hierarchical routing ⓘ |
| standardizes | core MPLS architectural concepts ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Multiprotocol Label Switching
NERFINISHED
ⓘ
packet switching ⓘ routing architecture ⓘ |
| title | Multiprotocol Label Switching Architecture NERFINISHED ⓘ |
| workingGroup | Multiprotocol Label Switching (MPLS) 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: IETF RFC 3031 Description of subject: IETF RFC 3031 is the foundational standards document that specifies the architecture and key mechanisms of Multiprotocol Label Switching (MPLS) in IP networks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.