Connecting MPLS-SPRING Islands over IP Networks
draft-xu-mpls-spring-islands-connection-over-ip-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-12
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                         X. Xu, Ed.
Internet-Draft                                                    Huawei
Intended status: Standards Track                               R. Raszuk
Expires: April 15, 2017                                     Bloomberg LP
                                                             U. Chunduri

                                                            L. Contreras
                                                          Telefonica I+D
                                                                L. Jalil
                                                                 Verizon
                                                        October 12, 2016

            Connecting MPLS-SPRING Islands over IP Networks
           draft-xu-mpls-spring-islands-connection-over-ip-00

Abstract

   MPLS-SPRING is an MPLS-based source routing paradigm in which a
   sender of a packet is allowed to partially or completely specify the
   route the packet takes through the network by imposing stacked MPLS
   labels to the packet.  To facilitate the incremental deployment of
   this new technology, this document describes a mechanism which allows
   the outermost LSP be replaced by an IP-based tunnel.

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
   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 April 15, 2017.

Copyright Notice

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

Xu, et al.               Expires April 15, 2017                 [Page 1]
Internet-Draft                                              October 2016

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Packet Forwarding Procedures  . . . . . . . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   MPLS-SPRING [I-D.ietf-spring-segment-routing-mpls] is a MPLS-based
   source routing paradigm in which a sender of a packet is allowed to
   partially or completely specify the route the packet takes through
   the network by imposing stacked MPLS labels to the packet.  To
   facilitate the incremental deployment of this new technology, this
   document describes a mechanism which allows the outermost LSP to be
   replaced by an IP-based tunnel (e.g., MPLS-in-IP/GRE tunnel
   [RFC4023], MPLS-in-UDP tunnel [RFC7510] or MPLS-in-L2TPv3 tunnel
   [RFC4817] and etc) when the nexthop along the LSP is not MPLS-SPRING-
   enabled.  The tunnel destination address would be the address of the
   egress of the outmost LSP (e.g., the egress of the active node
   segment).

   This mechanism is much useful in the MPLS-SPRING-based Service
   Function Chainning (SFC) case [I-D.xu-sfc-using-mpls-spring] where
   only a few specific routers (e.g., Service Function Forwarders (SFF)
   and classifiers) are required to be MPLS-SPRING-capable while the
   remaining routers are just required to support IP forwarding
   capability.  In addition, this mechanism is also useful in some
Show full document text