idnits 2.17.1 draft-xu-softwire-encaps-udp-00.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 (February 12, 2013) is 4089 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) == Missing Reference: 'IP-IN-UDP' is mentioned on line 91, but not defined == Missing Reference: 'MPLS-IN-UDP' is mentioned on line 92, but not defined == Unused Reference: 'MPLS-in-UDP' is defined on line 150, but no explicit reference was found in the text == Unused Reference: 'IP-in-UDP' is defined on line 154, but no explicit reference was found in the text -- 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-00 == Outdated reference: A later version (-03) exists of draft-xu-softwire-ip-in-udp-00 Summary: 0 errors (**), 0 flaws (~~), 8 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 Contrail 8 Y. Lee 9 Comcast 11 Y. Fan 12 China Telecom 14 Expires: August 2013 February 12, 2013 16 BGP Tunnel Encapsulation Attribute for UDP 18 draft-xu-softwire-encaps-udp-00 20 Abstract 22 This document specifies a new Border Gateway Protocol (BGP) Tunnel 23 Type of User Datagram Protocol (UDP) tunnels. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other documents 37 at any time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on August 12, 2013. 48 Copyright Notice 50 Copyright (c) 2013 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described in 60 Section 4.e of the Trust Legal Provisions and are provided without 61 warranty as described in the Simplified BSD License. 63 Conventions used in this document 65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 67 document are to be interpreted as described in RFC-2119 [RFC2119]. 69 Table of Contents 71 1. Introduction ................................................ 3 72 2. Terminology ................................................. 3 73 3. BGP Tunnel Type Code for UDP ................................ 3 74 4. Security Considerations ..................................... 3 75 5. IANA Considerations ......................................... 3 76 6. Acknowledgements ............................................ 3 77 7. References .................................................. 4 78 7.1. Normative References ................................... 4 79 7.2. Informative References ................................. 4 80 Authors' Addresses ............................................. 4 82 1. Introduction 84 [RFC5512] specifies a method by which Border Gateway Protocol (BGP) 85 speakers can signal tunnel encapsulation information to each other 86 and accordingly it defines support for Generic Routing Encapsulation 87 (GRE)[RFC2784], Layer Two Tunneling Protocol - Version 3 (L2TPv3) 88 [RFC3931] and IP in IP [RFC2003] tunnel types. This document builds 89 on [RFC5512] and defines support for the User Datagram Protocol (UDP) 90 tunnel type which is applicable to at least the following two 91 application cases: IP-in-UDP encapsulation [IP-IN-UDP] and MPLS-in- 92 UDP encapsulation [MPLS-IN-UDP]. 94 2. Terminology 96 This memo makes use of the terms defined in [RFC5512]. 98 3. BGP Tunnel Type Code for UDP 100 To use either the Encapsulation Subsequent Address Family Identifier 101 (SAFI) or the BGP Encapsulation Extended Community defined in 102 [RFC5512] to signal the UDP tunnel type information across BGP 103 speakers, a new Tunnel Type code (TBD) indicating the UDP tunnel 104 type needs to be assigned by IANA. 106 This document does not specify any UDP tunnel specific sub-TLV. 107 Furthermore, the BGP Encapsulation Network Layer Reachability 108 Information (NLRI) Format is not modified by this document. 110 4. Security Considerations 112 The security considerations mentioned in [RFC5512] is applicable to 113 this new BGP Tunnel Type code for UDP tunnels as well. No new 114 security risk is introduced by this new Tunnel Type code for UDP 115 tunnels. 117 5. IANA Considerations 119 A new BGP Tunnel Type code indicating the UDP tunnel type needs to 120 be assigned by IANA. 122 6. Acknowledgements 124 Thanks to. 126 7. References 128 7.1. Normative References 130 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 131 Requirement Levels", BCP 14, RFC 2119, March 1997. 133 7.2. Informative References 135 [RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation 136 Subsequent Address Family Identifier (SAFI) and the BGP 137 Tunnel Encapsulation Attribute", RFC 5512, April 2009. 139 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 140 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 141 March 2000. 143 [RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., 144 "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 145 3931, March 2005. 147 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, 148 October 1996. 150 [MPLS-in-UDP] Xu, X., Sheth, N., Yong, L., Pignataro, C., Fan, Y and 151 Z. Li, "Encapsulating MPLS in UDP", draft-ietf-mpls-in- 152 udp-00.txt (work in progress), January 2013. 154 [IP-in-UDP] Xu, X., Pignataro, C., Towsley, M., Lee, Y and Y. Fan, 155 "Encapsulating IP in UDP", draft-xu-softwire-ip-in-udp- 156 00.txt (work in progress), December 2012. 158 Authors' Addresses 160 Xiaohu Xu 161 Huawei Technologies, 162 Beijing, China 163 Phone: +86-10-60610041 164 Email: xuxiaohu@huawei.com 166 Zhenbin Li 167 Huawei Technologies, 168 Beijing, China 169 Phone: +86-10-60613676 170 Email: lizhenbin@huawei.com 171 Nischal Sheth 172 Nischal Sheth 173 Contrail Systems 174 Email: nsheth@contrailsystems.com 176 Yongbing Fan 177 China Telecom 178 Guangzhou, China. 179 Phone: +86 20 38639121 180 Email: fanyb@gsta.com 182 Yiu Lee 183 Comcast 184 One Comcast Center 185 Philadelphia, PA 1903 186 USA 187 Email: Yiu_Lee@Cable.Comcast.com