Network Assigned Upstream-Label
draft-ietf-teas-network-assigned-upstream-label-09

Document Type Active Internet-Draft (teas WG)
Last updated 2017-11-06 (latest revision 2017-10-30)
Replaces draft-ietf-ccamp-network-assigned-upstream-label
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2015 - Submit network assig... )
Other - see Comment Log
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2017-06-22)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to "Lou Berger" <lberger@labn.net>
TEAS Working Group                                         X. Zhang, Ed.
Internet-Draft                                       Huawei Technologies
Updates: 3471, 3473, 6205 (if approved)                   V. Beeram, Ed.
Intended status: Standards Track                        Juniper Networks
Expires: May 3, 2018                                          I. Bryskin
                                                     Huawei Technologies
                                                           D. Ceccarelli
                                                                Ericsson
                                                     O. Gonzalez de Dios
                                                              Telefonica
                                                        October 30, 2017

                    Network Assigned Upstream-Label
           draft-ietf-teas-network-assigned-upstream-label-09

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Zhang, et al.              Expires May 3, 2018                  [Page 1]
Internet-Draft       Network Assigned Upstream-Label        October 2017

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 3, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.  Unassigned Upstream Label . . . . . . . . . . . . . . . . . .   3
     2.1.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Backwards Compatibility . . . . . . . . . . . . . . . . .   5
   3.  Use-Case: Wavelength Setup for IP over Optical Networks . . .   5
     3.1.  Initial Setup . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Wavelength Change . . . . . . . . . . . . . . . . . . . .   7
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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
Show full document text