idnits 2.17.1 draft-ietf-ospf-ospfv3-traffic-06.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 455. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 432. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 439. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 445. ** 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 (October 20, 2005) is 6756 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 356, 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: April 23, 2006 IP Infusion, Inc 5 A. Davey 6 Data Connection Limited 7 A. Lindem (Editor) 8 Cisco Systems, Inc 9 October 20, 2005 11 Traffic Engineering Extensions to OSPF version 3 12 draft-ietf-ospf-ospfv3-traffic-06.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 April 23, 2006. 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. 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 68 A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 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 [RFC2119]. 94 2. Intra-Area-TE-LSA 96 A new LS type is defined for the Intra-Area-TE LSA. This is 97 different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are 98 used to advertise TE information [OPAQUE]. The LSA function code is 99 10, the U bit is set, and the scope is set to 01 for area-scoping. 100 When the U bit is set to 1 an OSPFv3 router must flood the LSA at its 101 defined flooding scope even if it does not recognize the LS type 102 [OSPFV3]. 104 0 1 2 3 105 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 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | LS age |0|1|1| 10 | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | Link State ID | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | Advertising Router | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | LS sequence number | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | LS checksum | Length | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | | 118 +- TLVs -+ 119 | ... | 121 The Link State ID of an Intra-Area-TE LSA is an arbitrary value used 122 to maintain multiple Traffic Engineering LSAs. The LSA ID has no 123 topological significance. 125 The format of the TLVs within the body of a router information LSA is 126 the same as the format used by the Traffic Engineering Extensions to 127 OSPF [TE]. The LSA payload consists of one or more nested Type/ 128 Length/Value (TLV) triplets. The format of each TLV is: 130 0 1 2 3 131 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 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | Type | Length | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | Value... | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 The Length field defines the length of the value portion in octets 139 (thus a TLV with no value portion would have a length of zero). The 140 TLV is padded to four-octet alignment; padding is not included in 141 the length field (so a three octet value would have a length of 142 three, but the total size of the TLV would be eight octets). Nested 143 TLVs are also 32-bit aligned. For example, a one byte value would 144 have the length field set to 1, and three octets of padding would be 145 added to the end of the value portion of the TLV. Unrecognized types 146 are ignored. 148 2.1 Intra-Area-TE-LSA Payload 150 An Intra-Area-TE-LSA contains one top-level TLV. There are two 151 applicable top-level TLVs: 153 2 - Link TLV 155 3 - Router IPv6 Address TLV 157 3. Router IPv6 Address TLV 159 The Router IPv6 Address TLV advertises a reachable IPv6 address. 160 This is a stable IPv6 address that is always reachable if there is 161 connectivity to the OSPFv3 router. 163 The Router IPv6 Address TLV has type 3, length 16, and a value 164 containing a 16 octet local IPv6 address. It MUST appear in exactly 165 one Traffic Engineering LSA originated by an OSPFv3 router supporting 166 the TE extensions. The Router IPv6 Address TLV is a top-level TLV as 167 defined in Traffic Engineering Extensions to OSPF [TE] and only one 168 top-level TLV may be contained in an LSA. 170 0 1 2 3 171 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 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | 3 | 16 | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 | | 176 +-+-+-+- -+-+-+-+ 177 | | 178 +-+-+-+- Router IPv6 Address -+-+-+-+ 179 | | 180 +-+-+-+- -+-+-+-+ 181 | | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 Type A 16 bit field set to 3. 185 Length A 16 bit field that indicates the length of the value 186 portion in octets. For this TLV it is always 16. 187 Value A stable and routable IPv6 address. 189 4. Link TLV 191 The Link TLV describes a single link and consists of a set of sub- 192 TLVs [TE]. All of the sub-TLVs in [TE] other than the Link ID sub- 193 TLV are applicable to OSPFv3. The Link ID sub-TLV can't be used in 194 OSPFv3 due to the protocol differences between OSPFv2 and OSPFv3. 196 Three new sub-TLVs for the Link TLV are defined: 198 18 - Neighbor ID (8 octets) 200 19 - Local Interface IPv6 Address (16N octets, where N is the 201 number of IPv6 addresses) 203 20 - Remote Interface IPv6 Address (16N octets, where N is the 204 number of IPv6 addresses) 206 The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering 207 support. It MUST be appear exactly once in a Link TLV. All other 208 sub-TLVs defined in this document MAY occur at most once in a Link 209 TLV. 211 4.1 Link ID Sub-TLV 213 The Link ID sub-TLV is used in OSPFv2 to identify the other end of 214 the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link 215 identification. In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent 216 and MUST be ignored upon receipt. 218 4.2 Neighbor ID Sub-TLV 220 In OSPFv2, the Link ID is used to identify the other end of a link. 221 In OSPFv3, the combination of Neighbor Interface ID and Neighbor 222 Router ID is used for neighbor link identification. Both are 223 advertised in the Neighbor ID Sub-TLV. 225 Neighbor Interface ID and Neighbor Router ID values are the same as 226 described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs. 228 0 1 2 3 229 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 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | 18 | 8 | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Neighbor Interface ID | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | Neighbor Router ID | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 238 Type A 16 bit field set to 18. 239 Length A 16 bit field that indicates the length of the value 240 portion in octets. For this sub-TLV it is always 8. 241 Value The neighbor's interface ID and router ID. 243 4.3 Local Interface IPv6 Address Sub-TLV 245 The Local Interface IPv6 Address sub-TLV specifies the IPv6 246 address(es) of the interface corresponding to this link. If there 247 are multiple local addresses assigned to the link then they MAY all 248 be listed in this sub-TLV. Link-local addresses MUST NOT be included 249 in this sub-TLV. 251 0 1 2 3 252 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 253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 254 | 19 | Length (Multiple of 16) | 255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 | | 257 +-+-+-+- -+-+-+-+ 258 | | 259 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 260 | | 261 +-+-+-+- -+-+-+-+ 262 | | 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | o | 265 | o | 266 | o | 267 | | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | | 270 +-+-+-+- -+-+-+-+ 271 | | 272 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 273 | | 274 +-+-+-+- -+-+-+-+ 275 | | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 Type A 16 bit field set to 19. 279 Length A 16 bit field that indicates the length of the value 280 portion in octets. For this sub-TLV, it MUST always be a 281 multiple of 16 octets dependent on the number of IPv6 282 addresses advertised. 283 Value A variable length local interface IPv6 address list. 285 4.4 Remote Interface IPv6 Address Sub-TLV 287 The Remote Interface IPv6 Address sub-TLV advertises the IPv6 288 address(es) associated with the neighbor's interface. This Sub-TLV 289 and the Local Interface IPv6 address Sub-TLV are used to discern 290 amongst parallel links between OSPFv3 routers. If the Link Type is 291 multi-access, the Remote Interface IPv6 Address MAY be set to ::. 292 Alternately, an implementation MAY choose not to send this sub-TLV. 293 Link-local addresses MUST NOT be advertised in this sub-TLV. 294 Neighbor addresses advertised in Link-LSAs with a prefix length of 295 128 and the LA bit set MAY be advertised. 297 0 1 2 3 298 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 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | 20 | Length (Multiple of 16) | 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 | | 303 +-+-+-+- -+-+-+-+ 304 | | 305 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 306 | | 307 +-+-+-+- -+-+-+-+ 308 | | 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | o | 311 | o | 312 | o | 313 | | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | | 316 +-+-+-+- -+-+-+-+ 317 | | 318 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 319 | | 320 +-+-+-+- -+-+-+-+ 321 | | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 Type A 16 bit field set to 20. 325 Length A 16 bit field that indicates the length of the value 326 portion in octets. For this sub-TLV, it MUST be a 327 multiple of 16 octets dependent on the number of IPv6 328 addresses advertised. 329 Value A variable length remote interface IPv6 address list. 331 5. Security Considerations 333 The function described in this document does not create any new 334 security issues for the OSPFv3 protocol. Security considerations for 335 the base OSPFv3 protocol are covered in [OSPFV3]. 337 6. IANA Considerations 339 The following IANA assignments are to be made from existing 340 registries: 342 1. The OSPFv3 LSA type function code 10 needs to be assigned to the 343 OSPFv3 Intra-Area-TE-LSA. 345 2. The Router IPv6 Address TLV type 3 needs to be assigned from the 346 existing registry for OSPF TE TLVs. 348 3. The Neighbor ID Sub-TLV (18), Local Interface IPv6 Address Sub- 349 TLV (19), and Remote Interface IPv6 Address Sub-TLV (20), need to 350 be assigned from the existing registry for OSPF TE Sub-TLVs. 352 7. References 354 7.1 Normative References 356 [OSPF] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 358 [OSPFV3] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", 359 RFC 2740, April 1998. 361 [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate 362 Requirement Levels", RFC 2119, March 1997. 364 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 365 Extensions to OSPF", RFC 3630, September 2003. 367 7.2 Informative References 369 [GMPLS] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 370 of Generalized MPLS", 371 draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (work in 372 progress). 374 [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, 375 July 1998. 377 [TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 378 P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi- 379 Protocol Label Switching (MPLS) Support of Differentiated 380 Services", RFC 3270. 382 Authors' Addresses 384 Kunihiro Ishiguro 385 IP Infusion, Inc 386 111 W. St. John Street, Suite 910 387 San Jose, CA 95113 388 USA 390 Email: kunihiro@ipinfusion.com 391 Toshiaki Takada 392 IP Infusion, Inc 393 111 W. St. John Street, Suite 910 394 San Jose, CA 95113 395 USA 397 Email: takada@ipinfusion.com 399 Alan Davey 400 Data Connection Limited 401 100 Church Street 402 Enfield 403 EN2 6BQ 404 UK 406 Email: Alan.Davey@dataconnection.com 408 Acee Lindem 409 Cisco Systems, Inc 410 7025 Kit Creek Road 411 Research Triangle Park, NC 27709 412 USA 414 Email: acee@cisco.com 416 Appendix A. Acknowledgments 418 Thanks to Vishwas Manral, Kireeti Kompella, Alex Zinin, and Adrian 419 Farrell for their comments. 421 The RFC text was produced using Marshall Rose's xml2rfc tool. 423 Intellectual Property Statement 425 The IETF takes no position regarding the validity or scope of any 426 Intellectual Property Rights or other rights that might be claimed to 427 pertain to the implementation or use of the technology described in 428 this document or the extent to which any license under such rights 429 might or might not be available; nor does it represent that it has 430 made any independent effort to identify any such rights. Information 431 on the procedures with respect to rights in RFC documents can be 432 found in BCP 78 and BCP 79. 434 Copies of IPR disclosures made to the IETF Secretariat and any 435 assurances of licenses to be made available, or the result of an 436 attempt made to obtain a general license or permission for the use of 437 such proprietary rights by implementers or users of this 438 specification can be obtained from the IETF on-line IPR repository at 439 http://www.ietf.org/ipr. 441 The IETF invites any interested party to bring to its attention any 442 copyrights, patents or patent applications, or other proprietary 443 rights that may cover technology that may be required to implement 444 this standard. Please address the information to the IETF at 445 ietf-ipr@ietf.org. 447 Disclaimer of Validity 449 This document and the information contained herein are provided on an 450 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 451 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 452 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 453 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 454 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 455 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 457 Copyright Statement 459 Copyright (C) The Internet Society (2005). This document is subject 460 to the rights, licenses and restrictions contained in BCP 78, and 461 except as set forth therein, the authors retain all their rights. 463 Acknowledgment 465 Funding for the RFC Editor function is currently provided by the 466 Internet Society.