idnits 2.17.1 draft-ietf-ospf-ospfv3-traffic-08.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, updated by RFC 4748 on line 451. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 462. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 469. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 475. 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 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 (January 3, 2007) is 6320 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 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: 2 errors (**), 0 flaws (~~), 1 warning (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Ishiguro 3 Internet-Draft V. Manral 4 Intended status: Standards Track IP Infusion, Inc 5 Expires: July 7, 2007 A. Davey 6 Data Connection Limited 7 A. Lindem (Editor) 8 Redback Networks 9 January 3, 2007 11 Traffic Engineering Extensions to OSPF version 3 12 draft-ietf-ospf-ospfv3-traffic-08.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 July 7, 2007. 39 Copyright Notice 41 Copyright (C) The IETF Trust (2007). 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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 54 2. Intra-Area-TE-LSA . . . . . . . . . . . . . . . . . . . . . . 4 55 2.1. Intra-Area-TE-LSA Payload . . . . . . . . . . . . . . . . 5 56 3. Router IPv6 Address TLV . . . . . . . . . . . . . . . . . . . 6 57 4. Link TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 58 4.1. Link ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 7 59 4.2. Neighbor ID Sub-TLV . . . . . . . . . . . . . . . . . . . 7 60 4.3. Local Interface IPv6 Address Sub-TLV . . . . . . . . . . . 8 61 4.4. Remote Interface IPv6 Address Sub-TLV . . . . . . . . . . 9 62 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 64 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 65 7.1. Normative References . . . . . . . . . . . . . . . . . . . 13 66 7.2. Informative References . . . . . . . . . . . . . . . . . . 13 67 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 14 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 69 Intellectual Property and Copyright Statements . . . . . . . . . . 16 71 1. Introduction 73 OSPFv3 has a very flexible mechanism for adding new LS types. 74 Unknown LS types are flooded properly based on the flooding scope 75 bits in the LS type [OSPFV3]. This document proposes the addition of 76 the Intra-Area-TE LSA to OSPFv3. 78 For Traffic Engineering, this document uses "Traffic Engineering 79 Extensions to OSPF" [TE] as a base for TLV definitions. New TLVs and 80 sub-TLVs are added to [TE] to extend TE capabilities to IPv6 81 networks. Some existing TLVs and sub-TLVs require clarification for 82 OSPFv3 applicability. 84 GMPLS [GMPLS] and the Diff-Serv MPLS Extensions [TE-DIFF] are based 85 on [TE]. These functions can also be extended to OSPFv3 by utilizing 86 the TLVs and sub-TLVs described in this document. 88 1.1. Requirements notation 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC2119 93 [RFC-KEYWORDS]. 95 2. Intra-Area-TE-LSA 97 A new LS type is defined for the Intra-Area-TE LSA. This is 98 different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are 99 used to advertise TE information [OPAQUE]. The LSA function code is 100 10, the U bit is set, and the scope is set to 01 for area-scoping. 101 When the U bit is set to 1, an OSPFv3 router must flood the LSA at 102 its defined flooding scope even if it does not recognize the LS type 103 [OSPFV3]. 105 0 1 2 3 106 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 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | LS age |0|1|1| 10 | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | Link State ID | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | Advertising Router | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | LS sequence number | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | LS checksum | Length | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | | 119 +- TLVs -+ 120 | ... | 122 OSPFv3 Intra-Area-TE-LSA 124 The Link State ID of an Intra-Area-TE LSA is an arbitrary value used 125 to maintain multiple Traffic Engineering LSAs. The LSA ID has no 126 topological significance. 128 The format of the TLVs within the body of a router information LSA is 129 the same as the format used by the Traffic Engineering Extensions to 130 OSPF [TE]. The LSA payload consists of one or more nested Type/ 131 Length/Value (TLV) triplets. The format of each TLV is: 133 0 1 2 3 134 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 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Type | Length | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Value... | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 TLV Format 143 The Length field defines the length of the value portion in octets 144 (thus a TLV with no value portion would have a length of zero). The 145 TLV is padded to four-octet alignment; padding is not included in the 146 length field (so a three octet value would have a length of three, 147 but the total size of the TLV would be eight octets). Nested TLVs 148 are also 32-bit aligned. For example, a one byte value would have 149 the length field set to 1, and three octets of padding would be added 150 to the end of the value portion of the TLV. Unrecognized types are 151 ignored. 153 2.1. Intra-Area-TE-LSA Payload 155 An Intra-Area-TE-LSA contains one top-level TLV. There are two 156 applicable top-level TLVs: 158 2 - Link TLV 160 3 - Router IPv6 Address TLV 162 3. Router IPv6 Address TLV 164 The Router IPv6 Address TLV advertises a reachable IPv6 address. 165 This is a stable IPv6 address that is always reachable if there is 166 connectivity to the OSPFv3 router. 168 The Router IPv6 Address TLV has type 3, length 16, and a value 169 containing a 16 octet local IPv6 address. It MUST appear in exactly 170 one Traffic Engineering LSA originated by an OSPFv3 router supporting 171 the TE extensions. The Router IPv6 Address TLV is a top-level TLV as 172 defined in Traffic Engineering Extensions to OSPF [TE] and only one 173 top-level TLV may be contained in an LSA. 175 0 1 2 3 176 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 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 | 3 | 16 | 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | | 181 +-+-+-+- -+-+-+-+ 182 | | 183 +-+-+-+- Router IPv6 Address -+-+-+-+ 184 | | 185 +-+-+-+- -+-+-+-+ 186 | | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 Type A 16 bit field set to 3. 190 Length A 16 bit field that indicates the length of the value 191 portion in octets. For this TLV it is always 16. 192 Value A stable and routable IPv6 address. 194 Router IPv6 Address TLV 196 4. Link TLV 198 The Link TLV describes a single link and consists of a set of sub- 199 TLVs [TE]. All of the sub-TLVs in [TE] other than the Link ID sub- 200 TLV are applicable to OSPFv3. The Link ID sub-TLV can't be used in 201 OSPFv3 due to the protocol differences between OSPFv2 and OSPFv3. 203 Three new sub-TLVs for the Link TLV are defined: 205 18 - Neighbor ID (8 octets) 207 19 - Local Interface IPv6 Address (16N octets, where N is the 208 number of IPv6 addresses) 210 20 - Remote Interface IPv6 Address (16N octets, where N is the 211 number of IPv6 addresses) 213 The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering 214 support. It MUST appear exactly once in a Link TLV. All other sub- 215 TLVs defined in this document MAY occur at most once in a Link TLV. 217 4.1. Link ID Sub-TLV 219 The Link ID sub-TLV is used in OSPFv2 to identify the other end of 220 the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link 221 identification. In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent 222 and MUST be ignored upon receipt. 224 4.2. Neighbor ID Sub-TLV 226 In OSPFv2, the Link ID is used to identify the other end of a link. 227 In OSPFv3, the combination of Neighbor Interface ID and Neighbor 228 Router ID is used for neighbor link identification. Both are 229 advertised in the Neighbor ID Sub-TLV. 231 Neighbor Interface ID and Neighbor Router ID values are the same as 232 described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs. 234 0 1 2 3 235 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 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | 18 | 8 | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | Neighbor Interface ID | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | Neighbor Router ID | 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 Type A 16 bit field set to 18. 245 Length A 16 bit field that indicates the length of the value 246 portion in octets. For this sub-TLV it is always 8. 247 Value The neighbor's interface ID and router ID. 249 Neighbor ID Sub-TLV 251 4.3. Local Interface IPv6 Address Sub-TLV 253 The Local Interface IPv6 Address sub-TLV specifies the IPv6 254 address(es) of the interface corresponding to this link. If there 255 are multiple local addresses assigned to the link then they MAY all 256 be listed in this sub-TLV. Link-local addresses MUST NOT be included 257 in this sub-TLV. 259 0 1 2 3 260 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 261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 | 19 | Length | 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | | 265 +-+-+-+- -+-+-+-+ 266 | | 267 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 268 | | 269 +-+-+-+- -+-+-+-+ 270 | | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | o | 273 | o | 274 | o | 275 | | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | | 278 +-+-+-+- -+-+-+-+ 279 | | 280 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 281 | | 282 +-+-+-+- -+-+-+-+ 283 | | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 Type A 16 bit field set to 19. 287 Length A 16 bit field that indicates the length of the value 288 portion in octets. For this sub-TLV, it MUST always be a 289 multiple of 16 octets dependent on the number of IPv6 290 global addresses advertised. 291 Value A list of one or more local IPv6 interface addresses 292 each consuming 16 octets. 294 Local Interface IPv6 Address Sub-TLV 296 4.4. Remote Interface IPv6 Address Sub-TLV 298 The Remote Interface IPv6 Address sub-TLV advertises the IPv6 299 address(es) associated with the neighbor's interface. This Sub-TLV 300 and the Local Interface IPv6 address Sub-TLV are used to discern 301 amongst parallel links between OSPFv3 routers. If the Link Type is 302 multi-access, the Remote Interface IPv6 Address MAY be set to ::. 303 Alternately, an implementation MAY choose not to send this sub-TLV. 304 Link-local addresses MUST NOT be advertised in this sub-TLV. 305 Neighbor addresses advertised in Link-LSAs with a prefix length of 306 128 and the LA bit set MAY be advertised. 308 0 1 2 3 309 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 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | 20 | Length | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 | | 314 +-+-+-+- -+-+-+-+ 315 | | 316 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 317 | | 318 +-+-+-+- -+-+-+-+ 319 | | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | o | 322 | o | 323 | o | 324 | | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | | 327 +-+-+-+- -+-+-+-+ 328 | | 329 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 330 | | 331 +-+-+-+- -+-+-+-+ 332 | | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 Type A 16 bit field set to 20. 336 Length A 16 bit field that indicates the length of the value 337 portion in octets. For this sub-TLV, it MUST be a 338 multiple of 16 octets dependent on the number of IPv6 339 global addresses advertised. 340 Value A variable length remote interface IPv6 address list. 342 Remote Interface IPv6 Address Sub-TLV 344 5. Security Considerations 346 The function described in this document does not create any new 347 security issues for the OSPFv3 protocol. Security considerations for 348 the base OSPFv3 protocol are covered in [OSPFV3]. 350 6. IANA Considerations 352 The following IANA assignments are to be made from existing 353 registries: 355 1. The OSPFv3 LSA type function code 10 needs to be assigned to the 356 OSPFv3 Intra-Area-TE-LSA. 358 2. The Router IPv6 Address TLV type 3 needs to be assigned from the 359 existing registry for OSPF TE TLVs. 361 3. The Neighbor ID Sub-TLV (18), Local Interface IPv6 Address Sub- 362 TLV (19), and Remote Interface IPv6 Address Sub-TLV (20), need to 363 be assigned from the existing registry for OSPF TE Sub-TLVs. 365 7. References 367 7.1. Normative References 369 [OSPFV3] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", 370 RFC 2740, April 1998. 372 [RFC-KEYWORDS] 373 Bradner, S., "Key words for use in RFC's to Indicate 374 Requirement Levels", RFC 2119, March 1997. 376 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 377 Extensions to OSPF", RFC 3630, September 2003. 379 7.2. Informative References 381 [GMPLS] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 382 of Generalized MPLS", 383 draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (work in 384 progress). 386 [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, 387 July 1998. 389 [TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 390 P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi- 391 Protocol Label Switching (MPLS) Support of Differentiated 392 Services", RFC 3270. 394 Appendix A. Acknowledgments 396 Thanks to Vishwas Manral, Kireeti Kompella, Alex Zinin, and Adrian 397 Farrell for their comments. 399 The RFC text was produced using Marshall Rose's xml2rfc tool. 401 Authors' Addresses 403 Kunihiro Ishiguro 404 IP Infusion, Inc 405 125 South Market Street, Suite 900 406 San Jose, CA 95113 407 USA 409 Email: kunihiro@ipinfusion.com 411 Vishwas Manral 412 IP Infusion, Inc 413 #41, Ground Floor, 5th Cross Road 414 8th Main Road 415 Vasanth Nagar, Bangalore 560052 416 India 418 Email: vishwas@ipinfusion.com 420 Alan Davey 421 Data Connection Limited 422 100 Church Street 423 Enfield 424 EN2 6BQ 425 UK 427 Email: Alan.Davey@dataconnection.com 429 Acee Lindem 430 Redback Networks 431 102 Carric Bend Court 432 Cary, NC 27519 433 USA 435 Email: acee@redback.com 437 Full Copyright Statement 439 Copyright (C) The IETF Trust (2007). 441 This document is subject to the rights, licenses and restrictions 442 contained in BCP 78, and except as set forth therein, the authors 443 retain all their rights. 445 This document and the information contained herein are provided on an 446 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 447 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 448 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 449 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 450 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 451 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 453 Intellectual Property 455 The IETF takes no position regarding the validity or scope of any 456 Intellectual Property Rights or other rights that might be claimed to 457 pertain to the implementation or use of the technology described in 458 this document or the extent to which any license under such rights 459 might or might not be available; nor does it represent that it has 460 made any independent effort to identify any such rights. Information 461 on the procedures with respect to rights in RFC documents can be 462 found in BCP 78 and BCP 79. 464 Copies of IPR disclosures made to the IETF Secretariat and any 465 assurances of licenses to be made available, or the result of an 466 attempt made to obtain a general license or permission for the use of 467 such proprietary rights by implementers or users of this 468 specification can be obtained from the IETF on-line IPR repository at 469 http://www.ietf.org/ipr. 471 The IETF invites any interested party to bring to its attention any 472 copyrights, patents or patent applications, or other proprietary 473 rights that may cover technology that may be required to implement 474 this standard. Please address the information to the IETF at 475 ietf-ipr@ietf.org. 477 Acknowledgment 479 Funding for the RFC Editor function is provided by the IETF 480 Administrative Support Activity (IASA).