Network-Assigned Upstream Label
RFC 8359

Document Type RFC - Proposed Standard (March 2018; No errata)
Last updated 2018-03-13
Replaces draft-ietf-ccamp-network-assigned-upstream-label
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2015 - Submit network assig... )
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2017-06-22)
IESG IESG state RFC 8359 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to "Lou Berger" <lberger@labn.net>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                     X. Zhang, Ed.
Request for Comments: 8359                           Huawei Technologies
Updates: 3471, 3473, 6205                                 V. Beeram, Ed.
Category: Standards Track                               Juniper Networks
ISSN: 2070-1721                                               I. Bryskin
                                                     Huawei Technologies
                                                           D. Ceccarelli
                                                                Ericsson
                                                     O. Gonzalez de Dios
                                                              Telefonica
                                                              March 2018

                    Network-Assigned Upstream Label

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8359.

Zhang, et al.                Standards Track                    [Page 1]
RFC 8359             Network Assigned Upstream-Label          March 2018

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Unassigned Upstream Label . . . . . . . . . . . . . . . . . .   3
     3.1.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Backwards Compatibility . . . . . . . . . . . . . . . . .   5
   4.  Use-Case: Wavelength Setup for IP over Optical Networks . . .   5
     4.1.  Initial Setup . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Wavelength Change . . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   A functional description of the Generalized Multi-Protocol Label
   Switching (GMPLS) signaling extensions for setting up a bidirectional
   Label Switched Path (LSP) is provided in [RFC3471].  The GMPLS
   Resource reSerVation Protocol with Traffic Engineering (RSVP-TE)
   extensions for setting up a bidirectional LSP are specified in
   [RFC3473].  The bidirectional LSP setup is indicated by the presence
   of an UPSTREAM_LABEL object in the Path message.  As per the existing
   setup procedure outlined for a bidirectional LSP, each upstream node
   must allocate a valid upstream label on the outgoing interface before
   sending the initial Path message downstream.  However, there are
   certain scenarios (see Section 4) where it is not desirable or
   possible for a given node to pick the upstream label on its own.

Zhang, et al.                Standards Track                    [Page 2]
Show full document text