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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-12-03
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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
Internet-Draft                                                    Huawei
Intended status: Standards Track                               R. Raszuk
Expires: June 6, 2015                                      Mirantis Inc.
                                                             U. Chunduri
                                                                Ericsson
                                                        December 3, 2014

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

Abstract

   MPLS-SPRING is a 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.  The current MPLS-SRPING architecture requires an end-to-
   end MPLS Label Switched Path (LSP) between any two MPLS-SPRING-
   enabled routers (e.g., two adjacent hops of a given explicit path).
   In order to enable MPLS-SPRING-enabled routers to be deployed even
   when there are non-MPLS routers along the path between two MPLS-
   SPRING-enabled routers, it is desirable to have an alternative, which
   allows the use of IP-based tunnels (e.g., GRE tunnels) to connect two
   MPLS-SPRING-enabled routers.  This document describes a mechanism for
   such usage.

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 June 6, 2015.

Xu, et al.                Expires June 6, 2015                  [Page 1]
Internet-Draft                                             December 2014

Copyright Notice

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

1.  Introduction

   MPLS-SPRING [I-D.ietf-spring-segment-routing-mpls] is a 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.  The
   current MPLS-SRPING architecture requires an end-to-end MPLS Label
   Switched Path (LSP) between any two MPLS-SPRING-enabled routers
   (e.g., two adjacent hops of a given explicit path).  In order to
   enable MPLS-SPRING-enabled routers to be deployed even when there are
   non-MPLS routers along the path between two MPLS-SPRING-enabled
   routers, it is desirable to have an alternative, which allows the use
   of IP-based tunnels (e.g., MPLS-in-IP/GRE tunnel [RFC4023], MPLS-in-
   L2TPv3 tunnel [RFC4817] or MPLS-in-UDP tunnel [I-D.ietf-mpls-in-udp])
   to connect two MPLS-SPRING-enabled routers which are specified as
   adjacent hops of a given explicit path.  The tunnel destination
   address would be the address of next-hop MPLS-SPRING-enabled router
   along the explicit path, and this would cause the packet to be
   delivered to the next explicit hop.  In this procedure, the ingress
Show full document text