idnits 2.17.1 draft-nalawade-kapoor-tunnel-safi-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 8 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 9 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 77: '...P SSA Attribute, MUST contain at least...' RFC 2119 keyword, line 78: '...odes for this SAFI. It MAY contain one...' RFC 2119 keyword, line 124: '...ue contained in this Length field MUST...' RFC 2119 keyword, line 131: '... the information SHOULD take the sende...' RFC 2119 keyword, line 195: '...ue contained in this Length field MUST...' (6 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Length A 2 Octet field that specifies the length of the L2TPv3 attribute in octets. The value contained in this Length field MUST not exceed the total length of the BGP SSA [SSA] Attribute minus the total length of any prior TLVs. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Length A 2 Octet field that specifies the length of the mGRE information in octets. The value contained in this Length field MUST not exceed the total length of the BGP SSA [SSA] Attribute minus the total length of any prior TLVs. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: 'BGP-UPDATEv2' is mentioned on line 60, but not defined == Missing Reference: 'SSA' is mentioned on line 255, but not defined == Missing Reference: 'BGP-MP' is mentioned on line 242, but not defined == Unused Reference: 'BGP-CAP' is defined on line 285, but no explicit reference was found in the text == Unused Reference: 'MULTI-BGP' is defined on line 291, but no explicit reference was found in the text == Unused Reference: 'IPSEC-ARCH' is defined on line 297, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-AFI' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-SAFI' == Outdated reference: A later version (-26) exists of draft-ietf-idr-bgp4-22 -- Unexpected draft version: The latest known version of draft-ietf-idr-rfc2842bis is -01, but you're referring to -02. -- No information found for draft-nalawade-kapoor-bgp-ssa - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'BGP-SSA' == Outdated reference: A later version (-10) exists of draft-ietf-idr-rfc2858bis-02 ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC-ARCH') (Obsoleted by RFC 4301) Summary: 5 errors (**), 0 flaws (~~), 14 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Gargi Nalawade 3 Internet Draft Ruchi Kapoor 4 Expires: April 2004 Dan Tappan 6 Cisco Systems 8 Tunnel SAFI 10 draft-nalawade-kapoor-tunnel-safi-01.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 There is a need for Tunnel end-point discovery within and across 36 Autonomous Systems. BGP is the only protocol that is widely-spoken 37 across Autonomous Systems and can carry this information. This 38 document defines how BGP speakers can convey Tunnel end-point 39 reachability information. 41 1. Introduction 43 Two end-points of a Tunnel need to know the end-point information and 44 its binding to a network address at the remote point. Normally, this 45 can be statically shared and configured. But in case of a large 46 network where there may be a need for a large number of tunnels, the 47 number of tunnel end-points that need to be exchanged and maintained, 48 grows. It then needs to be exchanged and maintained using an inter-AS 49 protocol. 51 2. The Tunnel SAFI 53 This document defines a new SAFI called the Tunnel SAFI. The [IANA-AFI] [IANA-SAFI] value pair used to identify this SAFI is 55 (AFI=1, SAFI=TBD) for the IPv4 AFI and (AFI=2, SAFI=TBD) for the IPv6 56 AFI. 58 For BGP Speakers supporting [BGP-4], the tunnel end point address 59 will be carried as an NLRI in the MP_REACH attribute for this SAFI. 60 For BGP Speakers suppprting [BGP-UPDATEv2], the tunnel end point 61 address will be carried as an NLRI in the NLRI section of the BGP 62 Updatev2 message. 64 The NLRI will be encoded as a 2-octet Identifier followed by the NLRI 65 format as specified by the respective AFI. The Identifier will 66 contain a 2-octet Identifier that identifies the Tunnel end point 67 being advertised. This Identifier enables multiple Tunnel end-points 68 to share the same network address, thus conserving the number of 69 addresses needed to be configured by the operator on each of the 70 Tunnel-endpoints. 72 3. BGP Attribute 74 The BGP SSA Attribute [BGP-SSA] will be used to carry the Tunnel 75 end-point information. 77 The Value Field of the BGP SSA Attribute, MUST contain at least one 78 of the following valid Type codes for this SAFI. It MAY contain one 79 or more TLVs with these Type codes. 81 Type 1: L2TPv3 Tunnel information 83 Type 2: mGRE Tunnel information 85 Type 3: IPSec Tunnel information 87 Type 4: MPLS Tunnel information 89 3.1. L2TPv3 Tunnel information TLV 91 The L2TPv3 Tunnel Information TLV has a type of 1. The value part of 92 the L2TPv3 Tunnel Information Type contains the following : 94 - Preference (2 Octets) 95 - Flags (1 Octet) 96 - Cookie Length (1 Octet) 97 - Session ID (4 Octets) 98 - Cookie (Variable) 100 The L2TPv3 Tunnel Information TLV looks as follows : 102 0 1 103 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 105 | Type = 0x01 | 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Length (2 octets) | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | Preference (2 octets) | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 |S| Flags | Cookie Length | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Session ID (4 Octets) | 114 | | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | | 117 | Cookie (Variable) | 118 | | 119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 where 123 Length A 2 Octet field that specifies the length of the L2TPv3 124 attribute in octets. The value contained in this Length field MUST 125 not exceed the total length of the BGP SSA [SSA] Attribute minus the 126 total length of any prior TLVs. 128 Preference A 2 Octet field containing a Preference associated with 129 the TLV. The Preference value indicates a preferred ordering of 130 tunneling encapsulations according to the sender. The recipient of 131 the information SHOULD take the sender's preference into account in 132 selecting which encapsulation it will use. A higher value indicates a 133 higher preference. 135 Flags A 1 Octet field containing flag-bits. The leftmost bit 136 indicates whether Sequence numbering is to be used or not. The 137 remaining bits are reserved for future use. 139 Cookie Length Cookie Length is a 1 Octet field that contains the 140 length of the Variable length Cookie. 142 Session ID A 4 Octet field containing a non-zero identifier for a 143 session. 145 Cookie Cookie is a variable length (maximum 64 bits), value used by 146 L2TPv3 to check the association of a received data message with the 147 session identified by the Session ID. 149 The default value of the Length Field for the L2TPv3 Tunnel 150 information TLV is between 8 and 16 bytes, depending on the length of 151 the Cookie field specified in Cookie length. If the length of the TLV 152 is greater than that value, the subsequent portion of the Value field 153 contains one or more sub-TLVs. 155 A Sub-TLV when present is of the following format : 157 0 1 158 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | Sub-Type | Length | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | Value (Variable) | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 where Sub-Type & Length are of 1-Octet each & the Value field is 166 variable as specified by the Length. 168 3.2. mGRE Tunnel Information TLV 170 The mGRE Tunnel Information Type has a Type 2. The value part of the 171 mGRE Tunnel Information Type contains the following : 173 - Preference (2 Octets) 174 - Flags (1 Octet) 175 - mGRE Key (0 or 4 Octets) 177 The mGRE Tunnel Information TLV looks as follows : 179 0 1 180 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | Type = 0x02 | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | Length (2 octets) | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | Preference (2 octets) | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 |S|K| Flags | | 189 +-+-+-+-+-+-+-+-+ | 190 | mGRE Key (4 Octets) | 191 | | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 Length A 2 Octet field that specifies the length of the mGRE 195 information in octets. The value contained in this Length field MUST 196 not exceed the total length of the BGP SSA [SSA] Attribute minus the 197 total length of any prior TLVs. 199 Preference A 2 Octet field containing a Preference associated with 200 the TLV. The Preference value indicates a preferred ordering of 201 tunneling encapsulations according to the sender. The recipient of 202 the information SHOULD take the sender's preference into account in 203 selecting which encapsulation it will use. A higher value indicates a 204 higher preference. 206 Flags A 1 Octet field containing flag-bits. The leftmost bit 207 indicates whether Sequence numbering is to be used or not. The 2nd 208 bit indicates whether an mGRE Key is present or not. The remaining 209 bits are reserved for future use. 211 mGRE Key A 4 Octet field containing an optional mGRE Key. 213 If the Length field of the TLV contains a value greater than 3 Octets 214 plus the value specified in the Key Length, the subsequent portion of 215 the Value field contains one or more sub-TLVs. 217 A Sub-TLV when present is of the following format : 219 0 1 220 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | Sub-Type | Length | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | Value (Variable) | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 where Sub-Type & Length are of 1-Octet each & the Value field is 228 variable as specified by the Length. 230 3.3. IPSec Tunnel Information TLV 232 The IPSec Tunnel Information Type has a Type 3. The format of the 233 IPSec Tunnel Information TLV is TBD. 235 3.4. MPLS TLV 237 The MPLS TLV has a Type 4. The format of the MPLS TLV is TBD. 239 4. Capability Advertisement 241 A BGP speaker that wishes to exchange the IPv4-Tunnel SAFI, MUST use 242 the MP_EXT Capability Code as defined in [BGP-MP], to advertise the 243 corresponding (AFI, SAFI) pair. 245 A BGP speaker MAY participate in the distribution of IPv4-Tunnel 246 information. 248 5. Operation 250 A BGP Speaker that receives the Capability for the IPv4-Tunnel or 251 IPv6-Tunnel SAFI, MAY advertise the IPv4-Tunnel or IPv6-Tunnel 252 prefixes to that peer respectively. 254 In the UPDATE message for this SAFI sent to a peer, a BGP speaker 255 MUST only advertise the SAFI-specific attribute [SSA] TLVs that are 256 defined as valid for this SAFI. 258 If a BGP Speaker receives an SSA TLV that it does not recognize, it 259 will accept it and propagate it to other peers. 261 6. Deployment Considerations 263 In order for the Tunnels to come up between two end-points, the BGP 264 Speakers advertising the Tunnel end-points using the Ipv4 Tunnel 265 SAFI, MUST exchange at least one common encapsulation option. 267 7. Security Considerations 268 This extension to BGP does not change the underlying security issues. 270 8. Acknowledgements 272 We would like to thank Jim Guichard, Arjun Sreekantiah, Shyam Suri, 273 Chandrashekhar Appanna, John Scudder and Mark Townsley for their 274 comments and suggestions. 276 9. References 278 [IANA-AFI] http://www.iana.org/assignments/address-family-numbers 280 [IANA-SAFI] http://www.iana.org/assignments/safi-namespace 282 [BGP-4] Rekhter, Y. and T. Li (editors), "A Border Gateway Protocol 283 4 (BGP-4)", Internet Draft draft-ietf-idr-bgp4-22.txt, February 2004. 285 [BGP-CAP] Chandra, R., Scudder, J., "Capabilities Advertisement with 286 BGP-4", draft-ietf-idr-rfc2842bis-02.txt, April 2002. 288 [BGP-SSA] Kapoor R., Nalawade G., "BGPv4 SAFI-Specific Attribute", 289 draft-nalawade-kapoor-bgp-ssa-00.txt, work in progress. 291 [MULTI-BGP] Bates et al, "Multiprotocol Extensions for BGP-4", draft- 292 ietf-idr-rfc2858bis-02.txt, work in progress. 294 [BGP_UPDATEv2] Nalawade G.et al, "BGPv4 Update-v2 Message", draft- 295 nalawade-bgp-update-v2-01.txt, work in progress. 297 [IPSEC-ARCH] Kent, S., and R. Atkinson, "Security Architecture for 298 the Internet Protocol", RFC 2401, November 1998. 300 10. Authors' Addresses 302 Gargi Nalawade 303 Cisco Systems, Inc 304 170 West Tasman Drive 305 San Jose, CA 95134 306 mailto:gargi@cisco.com 308 Ruchi Kapoor 309 Cisco Systems, Inc 310 170 West Tasman Drive 311 San Jose, CA 95134 312 mailto:ruchi@cisco.com 314 Dan Tappan 315 Cisco Systems, Inc 316 170 West Tasman Drive 317 San Jose, CA 95134 318 mailto:tappan@cisco.com 320 11. Intellectual Property Statement 322 The IETF takes no position regarding the validity or scope of any 323 intellectual property or other rights that might be claimed to 324 pertain to the implementation or use of the technology described in 325 this document or the extent to which any license under such rights 326 might or might not be available; neither does it represent that it 327 has made any effort to identify any such rights. Information on the 328 IETF's procedures with respect to rights in standards-track and 329 standards- related documentation can be found in BCP-11. Copies of 330 claims of rights made available for publication and any assurances of 331 licenses to be made available, or the result of an attempt made to 332 obtain a general license or permission for the use of such 333 proprietary rights by implementers or users of this specification can 334 be obtained from the IETF Secretariat. 336 The IETF invites any interested party to bring to its attention any 337 copyrights, patents or patent applications, or other proprietary 338 rights which may cover technology that may be required to practice 339 this standard. Please address the information to the IETF Executive 340 Director. 342 12. Full Copyright Statement 344 Copyright (C) The Internet Society (2003). All Rights Reserved. 346 This document and translations of it may be copied and furnished to 347 others, and derivative works that comment on or otherwise explain it 348 or assist in its implementation may be prepared, copied, published 349 and distributed, in whole or in part, without restriction of any 350 kind, provided that the above copyright notice and this paragraph are 351 included on all such copies and derivative works. However, this 352 document itself may not be modified in any way, such as by removing 353 the copyright notice or references to the Internet Society or other 354 Internet organizations, except as needed for the purpose of 355 developing Internet standards in which case the procedures for 356 copyrights defined in the Internet Standards process must be 357 followed, or as required to translate it into languages other than 358 English. The limited permissions granted above are perpetual and 359 will not be revoked by the Internet Society or its successors or 360 assigns. This document and the information contained herein is 361 provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE 362 INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 363 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 364 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 365 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 367 13. Expiration Date 369 This memo is filed as , and 370 expires February, 2004.