idnits 2.17.1 draft-ietf-ospf-ospfv3-traffic-05.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 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 444. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 421. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 428. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 434. ** 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. 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 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 (March 2005) is 6983 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 345, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2740 (ref. 'OSPFV3') (Obsoleted by RFC 5340) -- Obsolete informational reference (is this intentional?): RFC 2370 (ref. 'OPAQUE') (Obsoleted by RFC 5250) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Ishiguro 3 Internet-Draft T. Takada 4 Expires: September 2, 2005 IP Infusion, Inc 5 A. Davey 6 Data Connection Limited 7 A. Lindem (Editor) 8 Cisco Systems, Inc 9 March 2005 11 Traffic Engineering Extensions to OSPF version 3 12 draft-ietf-ospf-ospfv3-traffic-05.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on September 2, 2005. 39 Copyright Notice 41 Copyright (C) The Internet Society (2005). 43 Abstract 45 This document describes extensions to OSPFv3 to support intra-area 46 Traffic Engineering (TE). This document extends OSPFv2 TE to handle 47 IPv6 networks. A new TLV and several new sub-TLVs are defined to 48 support IPv6 networks. 50 Table of Contents 52 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 53 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Intra-Area-TE-LSA . . . . . . . . . . . . . . . . . . . . . . 5 55 4. Router IPv6 Address TLV . . . . . . . . . . . . . . . . . . . 7 56 5. Link TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 57 5.1 Link ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 8 58 5.2 Neighbor ID Sub-TLV . . . . . . . . . . . . . . . . . . . 8 59 5.3 Local Interface IPv6 Address Sub-TLV . . . . . . . . . . . 9 60 5.4 Remote Interface IPv6 Address Sub-TLV . . . . . . . . . . 10 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 64 8.1 Normative References . . . . . . . . . . . . . . . . . . . 14 65 8.2 Informative References . . . . . . . . . . . . . . . . . . 14 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14 67 A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 68 Intellectual Property and Copyright Statements . . . . . . . . 17 70 1. Requirements notation 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in RFC2119 [RFC2119]. 76 2. Introduction 78 OSPFv3 has a very flexible mechanism for adding new LS types. 79 Unknown LS types are flooded properly based on the flooding scope 80 bits in the LS type [OSPFV3]. This document proposes the addition of 81 the Intra-Area-TE LSA to OSPFv3. 83 For Traffic Engineering, this document uses "Traffic Engineering 84 Extensions to OSPF" [TE] as a base for TLV definitions. New TLVs and 85 sub-TLVs are added to [TE] to extend TE capabilities to IPv6 86 networks. Some existing TLVs and sub-TLVs require clarification for 87 OSPFv3 applicability. 89 GMPLS [GMPLS] and the Diff-Serv MPLS Extensions [TE-DIFF] are based 90 on [TE]. These functions can also be extended to OSPFv3 by utilizing 91 the TLVs and sub-TLVs described in this document. 93 3. Intra-Area-TE-LSA 95 A new LS type is defined for the Intra-Area-TE LSA. This is 96 different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are 97 used to advertise TE information [OPAQUE]. The LSA function code is 98 10, the U bit is set, and the scope is set to 01 for area-scoping. 99 When the U bit is set to 1 an OSPFv3 router must flood the LSA at its 100 defined flooding scope even if it does not recognize the LS type 101 [OSPFV3]. 103 0 1 2 3 104 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 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | LS age |0|1|1| 10 | 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | Link State ID | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | Advertising Router | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | LS sequence number | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | LS checksum | Length | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | | 117 +- TLV's -+ 118 | ... | 120 The Link State ID of an Intra-Area-TE LSA is an arbitrary value used 121 to maintain multiple Traffic Engineering LSAs. The LSA ID has no 122 topological significance. 124 The format of the TLV's within the body of a router information LSA 125 is the same as the format used by the Traffic Engineering Extensions 126 to OSPF [TE]. The LSA payload consists of one or more nested Type/ 127 Length/Value (TLV) triplets. The format of each TLV is: 129 0 1 2 3 130 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 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | Type | Length | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Value... | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 The Length field defines the length of the value portion in octets 138 (thus a TLV with no value portion would have a length of zero). The 139 TLV is padded to four-octet alignment; padding is not included in 140 the length field (so a three octet value would have a length of 141 three, but the total size of the TLV would be eight octets). Nested 142 TLVs are also 32-bit aligned. For example, a one byte value would 143 have the length field set to 1, and three octets of padding would be 144 added to the end of the value portion of the TLV. Unrecognized types 145 are ignored. 147 4. Router IPv6 Address TLV 149 The Router IPv6 Address TLV advertises a reachable IPv6 address. 150 This is a stable IPv6 address that is always reachable if there is 151 connectivity to the OSPFv3 router. 153 The Router IPv6 Address TLV has type 3, length 16, and a value 154 containing a 16 octet local IPv6 address. It MUST appear in exactly 155 one Traffic Engineering LSA originated by an OSPFv3 router supporting 156 the TE extensions. The Router IPv6 Address TLV is a top-level TLV as 157 defined in Traffic Engineering Extensions to OSPF [TE] and only one 158 top-level TLV may be contained in an LSA. 160 0 1 2 3 161 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 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | 3 | 16 | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | | 166 +-+-+-+- -+-+-+-+ 167 | | 168 +-+-+-+- Router IPv6 Address -+-+-+-+ 169 | | 170 +-+-+-+- -+-+-+-+ 171 | | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 Type A 16 bit field set to 3. 175 Length A 16 bit field that indicates the length of the value 176 portion in octets. For this TLV it is always 16. 177 Value A stable and routable IPv6 address. 179 5. Link TLV 181 The Link TLV describes a single link and consists of a set of sub- 182 TLVs [TE]. All of the sub-TLVs in [TE] other than the Link ID sub- 183 TLV are applicable to OSPFv3. The Link ID sub-TLV can't be used in 184 OSPFv3 due to the protocol differences between OSPFv2 and OSPFv3. 186 Three new sub-TLVs for the Link TLV are defined: 188 17 - Neighbor ID (8 octets) 190 18 - Local Interface IPv6 Address (16N octets, where N is the 191 number of IPv6 addresses) 193 19 - Remote Interface IPv6 Address (16N octets, where N is the 194 number of IPv6 addresses) 196 The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering 197 support. It MUST be appear exactly once in a Link TLV. All other 198 sub-TLVs defined in document MAY occur at most once in a Link TLV. 200 5.1 Link ID Sub-TLV 202 The Link ID sub-TLV is used in OSPFv2 to identify the other end of 203 the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link 204 identification. In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent 205 and MUST be ignored upon receipt. 207 5.2 Neighbor ID Sub-TLV 209 In OSPFv2, the Link ID is used to identify the other end of a link. 210 In OSPFv3, the combination of Neighbor Interface ID and Neighbor 211 Router ID are used for neighbor link identification. Both are 212 advertised in the Neighbor ID Sub-TLV. 214 Neighbor Interface ID and Neighbor Router ID values are the same as 215 described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs. 217 0 1 2 3 218 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 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | 17 | 8 | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | Neighbor Interface ID | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | Neighbor Router ID | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 Type A 16 bit field set to 17. 228 Length A 16 bit field that indicates the length of the value 229 portion in octets. For this sub-TLV it is always 8. 230 Value The neighbor's interface ID and router ID. 232 5.3 Local Interface IPv6 Address Sub-TLV 234 The Local Interface IPv6 Address sub-TLV specifies the IPv6 235 address(es) of the interface corresponding to this link. If there 236 are multiple local addresses assigned to the link then they MAY all 237 be listed in this sub-TLV. Link-local address MUST NOT be included 238 in this sub-TLV. 240 0 1 2 3 241 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 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 | 18 | Length (Multiple of 16) | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 | | 246 +-+-+-+- -+-+-+-+ 247 | | 248 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 249 | | 250 +-+-+-+- -+-+-+-+ 251 | | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | o | 254 | o | 255 | o | 256 | | 257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 | | 259 +-+-+-+- -+-+-+-+ 260 | | 261 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 262 | | 263 +-+-+-+- -+-+-+-+ 264 | | 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 Type A 16 bit field set to 18. 268 Length A 16 bit field that indicates the length of the value 269 portion in octets. For this sub-TLV, it MUST alway be a 270 multiple of 16 octets dependent on the number of IPv6 271 addresses advertised. 272 Value A variable length local interface IPv6 address list. 274 5.4 Remote Interface IPv6 Address Sub-TLV 276 The Remote Interface IPv6 Address sub-TLV advertises the IPv6 277 address(es) associated with the neighbor's interface. This Sub-TLV 278 and the Local Interface IPv6 address Sub-TLV are used to discern 279 amongst parallel links between OSPFv3 routers. If the Link Type is 280 multi-access, the Remote Interface IPv6 Address MAY be set to ::. 281 Alternately, an implementation MAY choose not to send this sub-TLV. 282 Link-local addresses should not be contained in this sub-TLV. 283 Neighbor addresses advertised in Link-LSAs with a prefix length of 284 128 and the LA bit set MAY be advertised. 286 0 1 2 3 287 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 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | 19 | Length (Multiple of 16) | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 | | 292 +-+-+-+- -+-+-+-+ 293 | | 294 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 295 | | 296 +-+-+-+- -+-+-+-+ 297 | | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 | o | 300 | o | 301 | o | 302 | | 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | | 305 +-+-+-+- -+-+-+-+ 306 | | 307 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 308 | | 309 +-+-+-+- -+-+-+-+ 310 | | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 Type A 16 bit field set to 19. 314 Length A 16 bit field that indicates the length of the value 315 portion in octets. For this sub-TLV, it MUST be a 316 multiple of 16 octets dependent on the number of IPv6 317 addresses advertised. 318 Value A variable length remote interface IPv6 address list. 320 6. Security Considerations 322 The function described in this document does not create any new 323 security issues for the OSPFv3 protocol. Security considerations for 324 the base OSPFv3 protocol are covered in [OSPFV3]. 326 7. IANA Considerations 328 The following IANA assignments are to be made from existing 329 registries: 331 1. The OSPFv3 LSA type function code 10 needs to be assigned to the 332 OSPFv3 Intra-Area-TE-LSA. 334 2. The Router IPv6 Address TLV type 3 needs to be assigned from the 335 existing registry for OSPF TE TLVs. 337 3. The Neighbor ID Sub-TLV (17), Local Interface IPv6 Address Sub- 338 TLV (18), and Remote Interface IPv6 Address Sub-TLV (19), need to 339 be assigned from the existing registry for OSPF TE Sub-TLVs. 341 8. References 343 8.1 Normative References 345 [OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 347 [OSPFV3] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", 348 RFC 2740, April 1998. 350 [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate 351 Requirement Levels", RFC 2119, March 1997. 353 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 354 Extensions to OSPF", RFC 3630, September 2003. 356 8.2 Informative References 358 [GMPLS] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 359 of Generalized MPLS", 360 draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (work in 361 progress). 363 [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, 364 July 1998. 366 [TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 367 P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi- 368 Protocol Label Switching (MPLS) Support of Differentiated 369 Services", RFC 3270. 371 Authors' Addresses 373 Kunihiro Ishiguro 374 IP Infusion, Inc 375 111 W. St. John Street, Suite 910 376 San Jose, CA 95113 377 USA 379 Email: kunihiro@ipinfusion.com 380 Toshiaki Takada 381 IP Infusion, Inc 382 111 W. St. John Street, Suite 910 383 San Jose, CA 95113 384 USA 386 Email: takada@ipinfusion.com 388 Alan Davey 389 Data Connection Limited 390 100 Church Street 391 Enfield 392 EN2 6BQ 393 UK 395 Email: Alan.Davey@dataconnection.com 397 Acee Lindem 398 Cisco Systems, Inc 399 7025 Kit Creek Road 400 Research Triangle Park, NC 27709 401 USA 403 Email: acee@cisco.com 405 Appendix A. Acknowledgments 407 Thanks to Vishwas Manral, Kireeti Kompella and Alex Zinin for their 408 comments. 410 The RFC text was produced using Marshall Rose's xml2rfc tool. 412 Intellectual Property Statement 414 The IETF takes no position regarding the validity or scope of any 415 Intellectual Property Rights or other rights that might be claimed to 416 pertain to the implementation or use of the technology described in 417 this document or the extent to which any license under such rights 418 might or might not be available; nor does it represent that it has 419 made any independent effort to identify any such rights. Information 420 on the procedures with respect to rights in RFC documents can be 421 found in BCP 78 and BCP 79. 423 Copies of IPR disclosures made to the IETF Secretariat and any 424 assurances of licenses to be made available, or the result of an 425 attempt made to obtain a general license or permission for the use of 426 such proprietary rights by implementers or users of this 427 specification can be obtained from the IETF on-line IPR repository at 428 http://www.ietf.org/ipr. 430 The IETF invites any interested party to bring to its attention any 431 copyrights, patents or patent applications, or other proprietary 432 rights that may cover technology that may be required to implement 433 this standard. Please address the information to the IETF at 434 ietf-ipr@ietf.org. 436 Disclaimer of Validity 438 This document and the information contained herein are provided on an 439 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 440 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 441 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 442 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 443 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 444 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 446 Copyright Statement 448 Copyright (C) The Internet Society (2005). This document is subject 449 to the rights, licenses and restrictions contained in BCP 78, and 450 except as set forth therein, the authors retain all their rights. 452 Acknowledgment 454 Funding for the RFC Editor function is currently provided by the 455 Internet Society.