Network-Assigned Upstream Label
RFC 8359, “Network-Assigned Upstream Label”, is a Proposed Standard document published in March 2018 by X. Zhang, V. Beeram, I. Bryskin, D. Ceccarelli, O. Gonzalez de Dios. It updates RFC 3471, RFC 3473, RFC 6205. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8359 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8358 Update to Digital Signatures on Internet-Draft Documents
- RFC 8360 Resource Public Key Infrastructure Validation Reconsidered
- RFC 8357 Generalized UDP Source Port for DHCP Relay
- RFC 8361 Transparent Interconnection of Lots of Links : Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast Traffic
- RFC 8356 Experimental Codepoint Allocation for the Path Computation Element Communication Protocol
- RFC 8362 OSPFv3 Link State Advertisement Extensibility
- RFC 8355 Resiliency Use Cases in Source Packet Routing in Networking Networks
- RFC 8363 GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing Networks