idnits 2.17.1 draft-xu-softwire-encaps-udp-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (July 2, 2013) is 3944 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 5512 (Obsoleted by RFC 9012) == Outdated reference: A later version (-11) exists of draft-ietf-mpls-in-udp-02 == Outdated reference: A later version (-03) exists of draft-xu-softwire-ip-in-udp-02 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group X. Xu 2 Internet Draft Z. Li 3 Category: Standard Track Huawei 5 N. Sheth 6 Juniper 8 Y. Lee 9 Comcast 11 Y. Fan 12 China Telecom 14 Rajiv Asati 15 Cisco Systems 17 Expires: January 2014 July 2, 2013 19 BGP Tunnel Encapsulation Attribute for UDP 21 draft-xu-softwire-encaps-udp-01 23 Abstract 25 This document specifies a new Border Gateway Protocol (BGP) Tunnel 26 Type of User Datagram Protocol (UDP) tunnels. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF), its areas, and its working groups. Note that 35 other groups may also distribute working documents as Internet- 36 Drafts. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/ietf/1id-abstracts.txt. 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html. 49 This Internet-Draft will expire on January 2, 2014. 51 Copyright Notice 53 Copyright (c) 2013 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Conventions used in this document 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in RFC-2119 [RFC2119]. 72 Table of Contents 74 1. Introduction ................................................ 3 75 2. Terminology ................................................. 3 76 3. BGP Tunnel Type Code for UDP ................................ 3 77 4. Security Considerations ..................................... 3 78 5. IANA Considerations ......................................... 3 79 6. Acknowledgements ............................................ 3 80 7. References .................................................. 4 81 7.1. Normative References ................................... 4 82 7.2. Informative References ................................. 4 83 Authors' Addresses ............................................. 4 85 1. Introduction 87 [RFC5512] specifies a method by which Border Gateway Protocol (BGP) 88 speakers can signal tunnel encapsulation information to each other 89 and accordingly it defines support for Generic Routing Encapsulation 90 (GRE)[RFC2784], Layer Two Tunneling Protocol - Version 3 (L2TPv3) 91 [RFC3931] and IP in IP [RFC2003] tunnel types. This document builds 92 on [RFC5512] and defines support for the User Datagram Protocol (UDP) 93 tunnel type which is applicable to at least the following two 94 application cases: IP-in-UDP encapsulation [IP-in-UDP] and MPLS-in- 95 UDP encapsulation [MPLS-in-UDP]. 97 2. Terminology 99 This memo makes use of the terms defined in [RFC5512]. 101 3. BGP Tunnel Type Code for UDP 103 To use either the Encapsulation Subsequent Address Family Identifier 104 (SAFI) or the BGP Encapsulation Extended Community defined in 105 [RFC5512] to signal the UDP tunnel type information across BGP 106 speakers, a new Tunnel Type code (TBD) indicating the UDP tunnel type 107 needs to be assigned by IANA. 109 This document does not specify any UDP tunnel specific sub-TLV. 110 Furthermore, the BGP Encapsulation Network Layer Reachability 111 Information (NLRI) Format is not modified by this document. 113 4. Security Considerations 115 The security considerations mentioned in [RFC5512] is applicable to 116 this new BGP Tunnel Type code for UDP tunnels as well. No new 117 security risk is introduced by this new Tunnel Type code for UDP 118 tunnels. 120 5. IANA Considerations 122 A new BGP Tunnel Type code indicating the UDP tunnel type needs to be 123 assigned by IANA. 125 6. Acknowledgements 127 Thanks to. 129 7. References 131 7.1. Normative References 133 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 134 Requirement Levels", BCP 14, RFC 2119, March 1997. 136 7.2. Informative References 138 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 139 Subsequent Address Family Identifier (SAFI) and the BGP 140 Tunnel Encapsulation Attribute", RFC 5512, April 2009. 142 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 143 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 144 March 2000. 146 [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., 147 "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 148 3931, March 2005. 150 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, 151 October 1996. 153 [MPLS-in-UDP] Xu, X., Sheth, N., Yong, L., Pignataro, C., Fan, Y and 154 Z. Li, "Encapsulating MPLS in UDP", draft-ietf-mpls-in-udp- 155 02.txt (work in progress), June 2013. 157 [IP-in-UDP] Xu, X., Yong, L., Lee, Y., Fan, Y., Asati, R and I. van 158 Beijnum, "Encapsulating IP in UDP", draft-xu-softwire-ip- 159 in-udp-02.txt (work in progress), July 2013. 161 Authors' Addresses 163 Xiaohu Xu 164 Huawei Technologies, 165 Beijing, China 166 Phone: +86-10-60610041 167 Email: xuxiaohu@huawei.com 169 Zhenbin Li 170 Huawei Technologies, 171 Beijing, China 172 Phone: +86-10-60613676 173 Email: lizhenbin@huawei.com 174 Nischal Sheth 175 Juniper Networks 176 1194 N. Mathilda Ave 177 Sunnyvale, CA 94089 178 Email: nsheth@juniper.net 180 Yiu Lee 181 Comcast 182 One Comcast Center 183 Philadelphia, PA 1903 184 USA 185 Email: Yiu_Lee@Cable.Comcast.com 187 Yongbing Fan 188 China Telecom 189 Guangzhou, China. 190 Phone: +86 20 38639121 191 Email: fanyb@gsta.com 193 Rajiv Asati 194 Cisco Systems 195 7025-4 Kit Creek Rd 196 PO Box 14987 197 Research Triangle Park, NC 27709 198 USA 199 Email: rajiva@cisco.com