Network Working Group X. Xu Internet Draft L. Yong Category: Standard Track Huawei Expires: June 2014 December 20, 2013 BGP Tunnel Encapsulation Attribute for VXLAN-gpe draft-xu-softwire-encaps-vxlan-gpe-00 Abstract This document specifies a new Border Gateway Protocol (BGP) Tunnel Type of VXLAN-gpe. 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), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on June 20, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. Xu, et al. Expires June 20, 2014 [Page 1] Internet-Draft Tunnel Encapsulation Attribute for VXLAN-gpe July 2013 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. Conventions used in this document 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]. Table of Contents 1. Introduction ................................................ 3 2. Terminology ................................................. 3 3. BGP Tunnel Type Code for VXLAN-gpe .......................... 3 4. Security Considerations ..................................... 3 5. IANA Considerations ......................................... 3 6. Acknowledgements ............................................ 3 7. References .................................................. 4 7.1. Normative References ................................... 4 7.2. Informative References ................................. 4 Authors' Addresses ............................................. 4 Xu, et al. Expires June 20, 2014 [Page 2] Internet-Draft Tunnel Encapsulation Attribute for VXLAN-gpe July 2013 1. Introduction [RFC5512] specifies a method by which Border Gateway Protocol (BGP) speakers can signal tunnel encapsulation information to each other and accordingly it defines support for Generic Routing Encapsulation (GRE)[RFC2784], Layer Two Tunneling Protocol - Version 3 (L2TPv3) [RFC3931] and IP in IP [RFC2003] tunnel types. This document builds on [RFC5512] and defines support for VXLAN-gpe [VXLAN-gpe] tunnel type. VXLAN-gpe stands for the extended VXLAN encapsulation format which contains a Protocol Type field in the VXLAN header and can be used for both Layer2 and Layer3 VPN service, in other words, the VXLAN-gpe tunnel can be used to transport either IP packets or Ethernet frames. 2. Terminology This memo makes use of the terms defined in [RFC5512]. 3. BGP Tunnel Type Code for VXLAN-gpe To use either the Encapsulation Subsequent Address Family Identifier (SAFI) or the BGP Encapsulation Extended Community defined in [RFC5512] to signal the VXLAN-gpe tunnel type information across BGP speakers, a new Tunnel Type code (TBD) indicating such tunnel type needs to be assigned by IANA. This document does not specify any specific sub-TLV. Furthermore, the BGP Encapsulation Network Layer Reachability Information (NLRI) Format is not modified by this document. 4. Security Considerations The security considerations mentioned in [RFC5512] is applicable to the new BGP Tunnel Type code for VXLAN-gpe tunnel as well. No new security risk is introduced by this new Tunnel Type code for them. 5. IANA Considerations A new BGP Tunnel Type code indicating the VXLAN-gpe tunnel type needs to be assigned by IANA. 6. Acknowledgements Thanks to. Xu, et al. Expires June 20, 2014 [Page 3] Internet-Draft Tunnel Encapsulation Attribute for VXLAN-gpe July 2013 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [VXLAN-gpe] Agarwal, P. et al., "Generic Protocol Extension for VXLAN", draft-quinn-vxlan-gpe-02 (work in progress), December 2013. 7.2. Informative References [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute", RFC 5512, April 2009. [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, March 2000. [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005. [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, October 1996. [VXLAN] Mahalingam, M., Dutt, D., etc, "VXLAN: A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks", draft-mahalingam-dutt-dcops-vxlan-05.txt (work in progress). Authors' Addresses Xiaohu Xu Huawei Technologies, Email: xuxiaohu@huawei.com Lucy Yong Huawei Technologies, USA Email: lucy.yong@huawei.com