MPLS Label Operations in MPLS EH capable networks
draft-andersson-mpls-eh-label-stack-operations-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-20
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                          L. Andersson
Internet-Draft                                  Bronze Dragon Consulting
Intended status: Standards Track                             J. Guichard
Expires: August 24, 2019                                         H. Song
                                                               S. Bryant
                                                     Huawei Technologies
                                                       February 20, 2019

           MPLS Label Operations in MPLS EH capable networks
           draft-andersson-mpls-eh-label-stack-operations-00

Abstract

   Extension Headers (EH) carry information on in-network services and
   functions in an MPLS network.  This document describes the operations
   on the MPLS label stack when an EH is found in the packet.

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 https://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
   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 August 24, 2019.

Copyright Notice

   Copyright (c) 2019 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

Andersson, et al.        Expires August 24, 2019                [Page 1]
Internet-Draft         EH Label Stack Opedrations          February 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirement Language  . . . . . . . . . . . . . . . . . .   3
   2.  Operations on an MPLS Label Stack in an EH capable network  .   3
     2.1.  Physical Topology . . . . . . . . . . . . . . . . . . . .   3
     2.2.  A day in the life of a packet . . . . . . . . . . . . . .   5
       2.2.1.  Non-VPN Case  . . . . . . . . . . . . . . . . . . . .   6
         2.2.1.1.  Non-VPN with the EH in the packet . . . . . . . .   6
         2.2.1.2.  Non-VPN without an EH in the packet . . . . . . .   7
     2.3.  The VPN case  . . . . . . . . . . . . . . . . . . . . . .   8
       2.3.1.  VPN with EH in the packet . . . . . . . . . . . . . .   8
       2.3.2.  VPN without EH in the packet  . . . . . . . . . . . .   9
     2.4.  RSVP-TE Tunnel case . . . . . . . . . . . . . . . . . . .  10
       2.4.1.  RSVP Tunnel and EH present in the packet  . . . . . .  11
       2.4.2.  RSVP Tunnel and no EH present in the packet . . . . .  12
       2.4.3.  EH capable RSVP-TE tunnel . . . . . . . . . . . . . .  13
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   This document provides the operating procedures for EH-capable and
   non-EH-capable LSRs where MPLS Extension Headers (EH) are carried
   below the MPLS label stack.  Further we show that MPLS EHs can be
   gradually introduced into an existing MPLS network.  The capability
   to handle EHs is announced throughout the MPLS network, and LSRs that
   don't understand this information simply ignore it.

   The extension headers are carried after the MPLS Label Stack, and the
   presence of EHs are indicate in the label stack by a Extetended
   Spewcial Purpose label called Extention Headder Indicator (EHI) in
   the label stack.

   Extension headers may for example be used when it is required that
   the packet carry some metadata, more details will be found in
   [I-D.song-mpls-extension-header].  Examples of such cases are In-situ
   OAM, Network Telemetry and Measurement and Network Security.

Andersson, et al.        Expires August 24, 2019                [Page 2]
Show full document text