Skip to main content

Network-Assigned Upstream Label
RFC 8359

Revision differences

Document history

Date By Action
2018-03-14
(System) IANA registries were updated to include RFC8359
2018-03-13
(System)
Received changes through RFC Editor sync (created alias RFC 8359, changed title to 'Network-Assigned Upstream Label', changed abstract to 'This document discusses a Generalized …
Received changes through RFC Editor sync (created alias RFC 8359, changed title to 'Network-Assigned Upstream Label', changed abstract to '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.', changed pages to 10, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-03-13, changed IESG state to RFC Published, created updates relation between draft-ietf-teas-network-assigned-upstream-label and RFC 3471, created updates relation between draft-ietf-teas-network-assigned-upstream-label and RFC 3473, created updates relation between draft-ietf-teas-network-assigned-upstream-label and RFC 6205)
2018-03-13
(System) RFC published