Advertising Encapsulation Capability Using IS-IS
draft-xu-isis-encapsulation-cap-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-02-28
Replaced by draft-ietf-isis-encapsulation-cap
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)
Network Working Group                                              X. Xu
Internet-Draft                                                    Huawei
Intended status: Standards Track                               R. Raszuk
Expires: September 1, 2015                                    Individual
                                                             U. Chunduri
                                                                Ericsson
                                                            L. Contreras
                                                          Telefonica I+D
                                                       February 28, 2015

            Advertising Encapsulation Capability Using IS-IS
                   draft-xu-isis-encapsulation-cap-03

Abstract

   In a particular network environment where MPLS-SPRING-enabled routers
   are partially deployed, it needs to transport MPLS traffic through an
   IP-based tunnel between two MPLS-SPRING-enabled routers so as to
   traverse non-MPLS routers.  The ingress of the IP-based tunnel must
   know which encapsulation type is supported by the egress of that IP-
   based tunnel.This document describes how to advertise the
   encapsulation capability of MPLS-SPRING-enabled routers using IS-IS.
   Note that this encapsulation capablity advertisment may be applicalbe
   to other use cases as well.

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 September 1, 2015.

Copyright Notice

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

Xu, et al.              Expires September 1, 2015               [Page 1]
Internet-DraftAdvertising Encapsulation Capability Using ISFebruary 2015

   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 . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Advertising Encapsulation Capability  . . . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   [I-D.xu-spring-islands-connection-over-ip] describes a particular
   network environment where MPLS-SPRING-enabled routers are partially
   deployed and therefore it needs to transport MPLS traffic through an
   IP-based tunnel between two MPLS-SPRING-enabled routers so as to
   traverse non-MPLS routers.  The ingress of the IP-based tunnel (i.e.,
   tunnel encapsulator) must know which encapsulation type is supported
   by the egress of the IP-based tunnel (i.e., tunnel decapsulator).This
   document describes how to advertise the encapsulation capability of
   MPLS-SPRING-enabled routers using IS-IS.  Note that this
   encapsulation capablity advertisment may be applicalbe to other use
   cases as well.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Xu, et al.              Expires September 1, 2015               [Page 2]
Internet-DraftAdvertising Encapsulation Capability Using ISFebruary 2015

2.  Terminology

   This memo makes use of the terms defined in [RFC4971] and
   [I-D.xu-spring-islands-connection-over-ip].
Show full document text