idnits 2.17.1 draft-ietf-ospf-ospfv3-traffic-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 408. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 385. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 392. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 398. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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.) -- The document date (February 19, 2005) is 6998 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) == Unused Reference: 'OSPF' is defined on line 318, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 323, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2740 (ref. 'OSPFV3') (Obsoleted by RFC 5340) -- Duplicate reference: RFC2328, mentioned in 'RFC2119', was also mentioned in 'OSPF'. -- Obsolete informational reference (is this intentional?): RFC 2370 (ref. 'OPAQUE') (Obsoleted by RFC 5250) Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group K. Ishiguro 2 Internet-Draft T. Takada 3 Expires: August 20, 2005 IP Infusion, Inc 4 A. Lindem (Editor) 5 Cisco Systems, Inc 6 February 19, 2005 8 Traffic Engineering Extensions to OSPF version 3 9 draft-ietf-ospf-ospfv3-traffic-03.txt 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on August 20, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2005). 42 Abstract 44 This document describes extensions to OSPFv3 to support intra-area 45 Traffic Engineering (TE). This document extends OSPFv2 TE to handle 46 IPv6 networks. A new TLV and several new sub-TLVs are defined to 47 support IPv6 networks. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Intra-Area-TE-LSA . . . . . . . . . . . . . . . . . . . . . . 4 53 3. Router IPv6 Address TLV . . . . . . . . . . . . . . . . . . . 6 54 4. Link TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 55 4.1 Link ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 7 56 4.2 Neighbor ID Sub-TLV . . . . . . . . . . . . . . . . . . . 7 57 4.3 Local Interface IPv6 Address Sub-TLV . . . . . . . . . . . 8 58 4.4 Remote Interface IPv6 Address Sub-TLV . . . . . . . . . . 9 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 61 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 62 7.1 Normative References . . . . . . . . . . . . . . . . . . . . 13 63 7.2 Informative References . . . . . . . . . . . . . . . . . . . 13 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 65 A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 66 Intellectual Property and Copyright Statements . . . . . . . . 16 68 1. Introduction 70 OSPFv3 has a very flexible mechanism for adding new LS types. 71 Unknown LS types are flooded properly based on the flooding scope 72 bits in the LS type [OSPFV3]. This document proposes the addition of 73 the Intra-Area-TE LSA to OSPFv3. 75 For Traffic Engineering, this document uses "Traffic Engineering 76 Extensions to OSPF" [TE] as a base for TLV definitions. New TLSs and 77 sub-TLVs are added to [TE] to extend TE capabilities to IPv6 78 networks. Some TLVs and sub-TLVs require clarification for OSPFv3 79 applicabilty. 81 GMPLS [GMPLS] and the Diff-Serv MPLS Extensions [TE-DIFF] are based 82 on [TE]. These functions can also be extended to OSPFv3 by utilizing 83 the TLV and sub-TLVs described in this document. 85 2. Intra-Area-TE-LSA 87 A new LS type is defined for the Intra-Area-TE LSA. This is 88 different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are 89 used to advertise TE information [OPAQUE]. The LSA function code is 90 10, the U bit is set, and the scope is set to 01 for area-scoping. 91 When the U bit is set to 1 an OSPFv3 router must flood the LSA at 92 its defined flooding scope even if it does not recognize the LS type 93 [OSPFV3]. 95 0 1 2 3 96 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 97 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 98 | LS age |1|1|0| 10 | 99 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 | Link State ID (Interface ID) | 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 | Advertising Router | 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | LS sequence number | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | LS checksum | Length | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | | 109 +- TLV's -+ 110 | ... | 112 The Link State ID of an Intra-Area-TE LSA will be the Interface ID of 113 the link. 115 The format of the TLV's within the body of a router information LSA 116 is the same as the format used by the Traffic Engineering Extensions 117 to OSPF [TE]. The LSA payload consists of one or more nested Type/ 118 Length/Value (TLV) triplets. The format of each TLV is: 120 0 1 2 3 121 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Type | Length | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Value... | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 The Length field defines the length of the value portion in octets 129 (thus a TLV with no value portion would have a length of zero). The 130 TLV is padded to four-octet alignment; padding is not included in 131 the length field (so a three octet value would have a length of 132 three, but the total size of the TLV would be eight octets). Nested 133 TLV's are also 32-bit aligned. For example, a one byte value would 134 have the length field set to 1, and three octets of padding would be 135 added to the end of the value portion of the TLV. Unrecognized types 136 are ignored. 138 3. Router IPv6 Address TLV 140 The Router IPv6 Address TLV will advertise a reachable IPv6 address. 141 This is a stable IPv6 address that is always reachable if there is 142 connectivity to the OSPFv3 router. 144 The Router IPv6 Address TLV has type 3, length 16, and a value 145 containing a 16 octet local IPv6 address. It MUST appear in exactly 146 one Traffic Engineering LSA originated by an OSPFv3 router supporting 147 the TE extensions. 149 0 1 2 3 150 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | 3 | 16 | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | | 155 +-+-+-+- -+-+-+-+ 156 | | 157 +-+-+-+- Router IPv6 Address -+-+-+-+ 158 | | 159 +-+-+-+- -+-+-+-+ 160 | | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 Type A 16 bit field set to 3. 164 Length A 16 bit field that indicates the length of the value 165 portion in octets. For this TLV it is always 16. 166 Value A stable and routable IPv6 address. 168 4. Link TLV 170 The Link TLV describes a single link and consists a set of sub-TLVs 171 [TE]. All of sub-TLVs in [TE] other than the Link ID sub-TLV are 172 applicable to OSPFv3. The Link ID sub-TLV can't be used in OSPFv3 173 due to the protocol differences between OSPFv2 and OSPFv3. 175 Three new sub-TLVs for the Link TLV are defined: 176 17 - Neighbor ID (8 octets) 177 18 - Local Interface IPv6 Address (16N octets) 178 19 - Remote Interface IPv6 Address (16N octets) 180 4.1 Link ID Sub-TLV 182 The Link ID sub-TLV is used in OSPFv2 to identify the other end of 183 the link. In OSPFv3, the Neighbor ID sub-TLV should be used for link 184 identification. In OSPFv3, The Link ID sub-TLV should not be sent 185 and should be ignored upon receipt. 187 4.2 Neighbor ID Sub-TLV 189 In OSPFv2, the Link ID is used to identify the other end of a link. 190 In OSPFv3, the combination of Neighbor Interface ID and Neighbor 191 Router ID are used for neighbor link identification. Both are 192 advertised in the Neighbor ID Sub-TLV. 194 Neighbor Interface ID and Neighbor Router ID values are the same as 195 described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs. 197 0 1 2 3 198 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | 17 | 8 | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Neighbor Interface ID | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | Neighbor Router ID | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 Type A 16 bit field set to 17. 208 Length A 16 bit field that indicates the length of the value 209 portion in octets. For this sub-TLV it is always 8. 210 Value The neighbor's interface ID and router ID. 212 4.3 Local Interface IPv6 Address Sub-TLV 214 The Local Interface IPv6 Address sub-TLV specifies the IPv6 215 address(es) of the interface corresponding to this link. If there 216 are multiple local addresses on the link, they are all listed in this 217 sub-TLV. Link-local address should not be included in this sub-TLV. 219 0 1 2 3 220 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | 18 | Length (Multiple of 16) | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | | 225 +-+-+-+- -+-+-+-+ 226 | | 227 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 228 | | 229 +-+-+-+- -+-+-+-+ 230 | | 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 232 | o | 233 | o | 234 | o | 235 | | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | | 238 +-+-+-+- -+-+-+-+ 239 | | 240 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 241 | | 242 +-+-+-+- -+-+-+-+ 243 | | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 Type A 16 bit field set to 18. 247 Length A 16 bit field that indicates the length of the value 248 portion in octets. For this sub-TLV it will alway be a 249 multiple of 16 octets dependent on the number of IPv6 250 addresses advertised. 251 Value A variable length local interface IPv6 address list. 253 4.4 Remote Interface IPv6 Address Sub-TLV 255 The Remote Interface IPv6 Address sub-TLV advertises the IPv6 256 address(es) associated with neighbor's interface. This Sub-TLV and 257 the Local Interface IPv6 address Sub-TLV are used to discern amongst 258 parallel links between OSPFv3 routers. If the Link Type is 259 multi-access, the Remote Interface IPv6 Address is set to ::. 260 Link-local addresses should not be contained in this sub-TLV. 262 0 1 2 3 263 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | 19 | Length (Multiple of 16) | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | | 268 +-+-+-+- -+-+-+-+ 269 | | 270 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 271 | | 272 +-+-+-+- -+-+-+-+ 273 | | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | o | 276 | o | 277 | o | 278 | | 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | | 281 +-+-+-+- -+-+-+-+ 282 | | 283 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 284 | | 285 +-+-+-+- -+-+-+-+ 286 | | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 Type A 16 bit field set to 19. 290 Length A 16 bit field that indicates the length of the value 291 portion in octets. For this sub-TLV it will alway be a 292 multiple of 16 octets dependent on the number of IPv6 293 addresses advertised. 294 Value A variable length remote interface IPv6 address list. 296 5. Security Considerations 298 The function described in this document does not create any new 299 security issues for the OSPFv3 protocol. Security considerations for 300 the base OSPFv3 protocol are covered in [OSPFV3]. 302 6. IANA Considerations 304 The following IANA assignments are to be made from existing 305 registries: 306 1. The OSPFv3 LSA type function code 10 will need to be reserved for 307 the OSPFv3 Intra-Area-TE-LSA. 308 2. The Router IPv6 Address TLV type 3 will be assigned from the 309 existing registry for OSPF TE TLVs. 310 3. The Neighbor ID Sub-TLV (17), Local Interface IPv6 Address 311 Sub-TLV (18), and Remote Interface IPv6 Address Sub-TLV (19), 312 will be assigned from the existing registry for OSPF TE Sub-TLVs. 314 7. References 316 7.1 Normative References 318 [OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 320 [OSPFV3] Coltun, R., Ferguson, D. and J. Moy, "OSPF for IPv6", RFC 321 2740, April 1998. 323 [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate 324 Requirement Levels", RFC 2328, March 1977. 326 [TE] Katz, D., Yeung, D. and K. Kompella, "Traffic Engineering 327 Extensions to OSPF", RFC 3630, September 2003. 329 7.2 Informative References 331 [GMPLS] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 332 of Generalized MPLS", 333 draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (work in 334 progress). 336 [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, July 337 1998. 339 [TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 340 P., Krishnan, R., Cheval, P. and J. Heinanen, 341 "Multi-Protocol Label Switching (MPLS) Support of 342 Differentiated Services", RFC 3270. 344 Authors' Addresses 346 Kunihiro Ishiguro 347 IP Infusion, Inc 348 111 W. St. John Street, Suite 910 349 San Jose, CA 95113 350 USA 352 EMail: kunihiro@ipinfusion.com 353 Toshiaki Takada 354 IP Infusion, Inc 355 111 W. St. John Street, Suite 910 356 San Jose, CA 95113 357 USA 359 EMail: takada@ipinfusion.com 361 Acee Lindem 362 Cisco Systems, Inc 363 7025 Kit Creek Road 364 Research Triangle Park, NC 27709 365 USA 367 EMail: acee@cisco.com 369 Appendix A. Acknowledgments 371 Thanks to Vishwas Manral, Kireeti Kompella and Alex Zinin for their 372 comments. 374 The RFC text was produced using Marshall Rose's xml2rfc tool. 376 Intellectual Property Statement 378 The IETF takes no position regarding the validity or scope of any 379 Intellectual Property Rights or other rights that might be claimed to 380 pertain to the implementation or use of the technology described in 381 this document or the extent to which any license under such rights 382 might or might not be available; nor does it represent that it has 383 made any independent effort to identify any such rights. Information 384 on the procedures with respect to rights in RFC documents can be 385 found in BCP 78 and BCP 79. 387 Copies of IPR disclosures made to the IETF Secretariat and any 388 assurances of licenses to be made available, or the result of an 389 attempt made to obtain a general license or permission for the use of 390 such proprietary rights by implementers or users of this 391 specification can be obtained from the IETF on-line IPR repository at 392 http://www.ietf.org/ipr. 394 The IETF invites any interested party to bring to its attention any 395 copyrights, patents or patent applications, or other proprietary 396 rights that may cover technology that may be required to implement 397 this standard. Please address the information to the IETF at 398 ietf-ipr@ietf.org. 400 Disclaimer of Validity 402 This document and the information contained herein are provided on an 403 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 404 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 405 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 406 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 407 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 408 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 410 Copyright Statement 412 Copyright (C) The Internet Society (2005). This document is subject 413 to the rights, licenses and restrictions contained in BCP 78, and 414 except as set forth therein, the authors retain all their rights. 416 Acknowledgment 418 Funding for the RFC Editor function is currently provided by the 419 Internet Society.