RSVP-TE
E663649
RSVP-TE is a signaling protocol used in MPLS networks to establish and manage traffic-engineered label-switched paths with specific resource and QoS constraints.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RSVP-TE canonical | 3 |
| Resource Reservation Protocol with Traffic Engineering extensions | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7427853 — 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: RSVP-TE Context triple: [MPLS, usesProtocol, RSVP-TE]
-
A.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
B.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
C.
MPLS
MPLS (Multiprotocol Label Switching) is a high-performance routing technique that directs data through a network using short path labels instead of long network addresses, enabling efficient traffic engineering and VPN services.
-
D.
BGP
BGP (Border Gateway Protocol) is the primary inter-domain routing protocol used to exchange routing information and determine paths between autonomous systems on the global Internet.
-
E.
OSPFv3
OSPFv3 is the version of the Open Shortest Path First routing protocol designed to operate over IPv6 networks, providing link-state routing and support for IPv6 addressing and features.
- 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: RSVP-TE Target entity description: RSVP-TE is a signaling protocol used in MPLS networks to establish and manage traffic-engineered label-switched paths with specific resource and QoS constraints.
-
A.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
-
B.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
C.
MPLS
MPLS (Multiprotocol Label Switching) is a high-performance routing technique that directs data through a network using short path labels instead of long network addresses, enabling efficient traffic engineering and VPN services.
-
D.
BGP
BGP (Border Gateway Protocol) is the primary inter-domain routing protocol used to exchange routing information and determine paths between autonomous systems on the global Internet.
-
E.
OSPFv3
OSPFv3 is the version of the Open Shortest Path First routing protocol designed to operate over IPv6 networks, providing link-state routing and support for IPv6 addressing and features.
- F. None of above. chosen
Statements (52)
| Predicate | Object |
|---|---|
| instanceOf |
network protocol
ⓘ
signaling protocol ⓘ |
| abbreviationOf |
Resource Reservation Protocol with Traffic Engineering extensions
ⓘ
linked to:
RSVP-TE
|
| associatedWith |
IP networks
ⓘ
label-switched paths ⓘ |
| basedOn | RSVP ⓘ |
| canSignal |
affinity constraints
ⓘ
bandwidth ⓘ local protection desired ⓘ preemption ⓘ priority ⓘ |
| definedInRFC |
RFC 3209
ⓘ
RFC 3473 ⓘ RFC 3477 ⓘ RFC 4090 ⓘ |
| deployment |
carrier MPLS networks
ⓘ
service provider backbones ⓘ |
| extends | RSVP ⓘ |
| fullName | Resource Reservation Protocol - Traffic Engineering ⓘ |
| messageType |
Path
ⓘ
PathErr ⓘ PathTear ⓘ Resv ⓘ ResvErr ⓘ ResvTear ⓘ |
| operatesAtLayer | network layer ⓘ |
| primaryPurpose |
establish label-switched paths
ⓘ
manage label-switched paths ⓘ |
| relationshipWith |
complements IS-IS-TE
ⓘ
complements OSPF-TE ⓘ |
| standardizedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supports |
QoS constraints
ⓘ
bandwidth reservation ⓘ explicit routing ⓘ fast reroute ⓘ protection switching ⓘ resource reservation ⓘ traffic engineering ⓘ |
| usedFor |
traffic-engineered LSP maintenance
ⓘ
traffic-engineered LSP setup ⓘ traffic-engineered LSP teardown ⓘ |
| usedIn |
MPLS
ⓘ
MPLS-TE ⓘ
linked to:
MPLS
|
| usesObject |
Explicit Route Object
ⓘ
FlowSpec ⓘ Label Object ⓘ Label Request Object ⓘ Record Route Object ⓘ Sender Template ⓘ Sender Tspec ⓘ Session Attribute Object ⓘ Session Object ⓘ |
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: RSVP-TE Description of subject: RSVP-TE is a signaling protocol used in MPLS networks to establish and manage traffic-engineered label-switched paths with specific resource and QoS constraints.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RSVP-TE