[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 draft-ietf-isis-encapsulation-cap

Network Working Group                                              X. Xu
Internet-Draft                                                    Huawei
Intended status: Standards Track                               R. Raszuk
Expires: August 18, 2015                                      Individual
                                                             U. Chunduri
                                                                Ericsson
                                                         V. Lopezalvarez
                                                              Telefonica
                                                       February 14, 2015


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

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 could be
   applicalbe to other use cases besides that as mentioned above 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 August 18, 2015.








Xu, et al.               Expires August 18, 2015                [Page 1]


Internet-DraftAdvertising Encapsulation Capability Using ISFebruary 2015


Copyright Notice

   Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . .   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 could be applicalbe to other use
   cases besides that as mentioned above 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 August 18, 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].

3.  Advertising Encapsulation Capability

   MPLS-SPRING-enabled routers need to advertise the encapsulation
   type(s) they support by using a new sub-TLV of the IS-IS Router
   CAPABILITY TLV [RFC4971], referred to as Encapsulation Capability
   sub-TLV.  The Encapsulation Capability sub-TLV could not appear more
   than once wihin a given IS-IS Router CAPABILITY TLV.  The scope of
   the advertisement depends on the application but it is recommended
   that it SHOULD be domain-wide.  The Type code of the Encapsualtion
   Cability sub-TLV is TBD, the Length value is vairalbe, and the Value
   field contains one or more Encapsulation Type sub-TLVs with each
   indicating a particular encapsulation format that the advertising
   router supports.

   This document defines the following types of Encapsulation Type sub-
   TLV:

   1.  MPLS-in-IP tunnel [RFC4023] : Type code=TBD1; Length=0

   2.  MPLS-in-GRE tunnel [RFC4023]: Type code=TBD2; Length=0

   3.  MPLS-in-L2TPv3 tunnel [RFC4817]: Type code=TBD3; Length=0

   4.  MPLS-in-UDP tunnel [I-D.ietf-mpls-in-udp]: Type code=TBD4;
       Length=0

   5.  MPLS-in-IP tunnel with IPsec Transport Mode [RFC5566]: Type
       code=TBD5; Length=0

4.  Acknowledgements

   The authors would like to thank Carlos Pignataro for his valuable
   comments on this draft.

5.  IANA Considerations

   This memo includes a request to IANA for allocating the type codes
   for Encapsulation Capability sub-TLV and Encapsulation Type sub-TLVs.








Xu, et al.               Expires August 18, 2015                [Page 3]


Internet-DraftAdvertising Encapsulation Capability Using ISFebruary 2015


6.  Security Considerations

   This document does not introduce any new security risk.

7.  References

7.1.  Normative References

   [I-D.xu-spring-islands-connection-over-ip]
              Xu, X., Raszuk, R., and U. Chunduri, "Connecting MPLS-
              SPRING Islands over IP Networks", draft-xu-spring-islands-
              connection-over-ip-03 (work in progress), December 2014.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4971]  Vasseur, JP., Shen, N., and R. Aggarwal, "Intermediate
              System to Intermediate System (IS-IS) Extensions for
              Advertising Router Information", RFC 4971, July 2007.

7.2.  Informative References

   [I-D.ietf-mpls-in-udp]
              Xu, X., Sheth, N., Yong, L., Callon, R., and D. Black,
              "Encapsulating MPLS in UDP", draft-ietf-mpls-in-udp-11
              (work in progress), January 2015.

   [RFC4023]  Worster, T., Rekhter, Y., and E. Rosen, "Encapsulating
              MPLS in IP or Generic Routing Encapsulation (GRE)", RFC
              4023, March 2005.

   [RFC4817]  Townsley, M., Pignataro, C., Wainner, S., Seely, T., and
              J. Young, "Encapsulation of MPLS over Layer 2 Tunneling
              Protocol Version 3", RFC 4817, March 2007.

   [RFC5566]  Berger, L., White, R., and E. Rosen, "BGP IPsec Tunnel
              Encapsulation Attribute", RFC 5566, June 2009.

Authors' Addresses

   Xiaohu Xu
   Huawei

   Email: xuxiaohu@huawei.com







Xu, et al.               Expires August 18, 2015                [Page 4]


Internet-DraftAdvertising Encapsulation Capability Using ISFebruary 2015


   Robert Raszuk
   Individual

   Email: robert@raszuk.net


   Uma Chunduri
   Ericsson

   Email: uma.chunduri@ericsson.com


   Victor Lopezalvarez
   Telefonica

   Email: victor.lopezalvarez@telefonica.com



































Xu, et al.               Expires August 18, 2015                [Page 5]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/