RFC 8359: Network-Assigned Upstream Label
In plain English — editorial summary, not part of the RFC
This document discusses a Generalized Multi-Protocol Label Switching (GMPLS) Resource reSerVation Protocol with Traffic Engineering (RSVP-TE) mechanism that enables the network to assign an upstream label for a bidirectional Label Switched Path (LSP). This is useful in scenarios where a given node does not have sufficient information to assign the correct upstream label on its own and needs to rely on the downstream node to pick an appropriate label. This document updates RFCs 3471, 3473, and 6205 as it defines processing for a special label value in the UPSTREAM_LABEL object.
Document record
- Document ID
- RFC8359
- Published
- March 2018
- Authors
- X. Zhang; V. Beeram; I. Bryskin; D. Ceccarelli; O. Gonzalez de Dios
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8360Resource Public Key Infrastructure (RPKI) Validation ReconsideredCurrent
April 2018
- RFC 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 8362OSPFv3 Link State Advertisement (LSA) ExtensibilityCurrent
April 2018
- RFC 8363GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
May 2018
- RFC 8355Resiliency Use Cases in Source Packet Routing in Networking (SPRING) NetworksCurrent
March 2018
- RFC 8354Use Cases for IPv6 Source Packet Routing in Networking (SPRING)Current
March 2018
- RFC 8364PIM Flooding Mechanism (PFM) and Source Discovery (SD)Updated
March 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?