idnits 2.17.1 draft-ietf-ospf-ospfv3-traffic-12.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 493. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 504. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 511. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 517. 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 (June 7, 2008) is 5795 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 informational reference (is this intentional?): RFC 2370 (ref. 'OPAQUE') (Obsoleted by RFC 5250) == Outdated reference: A later version (-16) exists of draft-ietf-ospf-ospfv3-mib-12 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 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: December 9, 2008 A. Davey 6 Data Connection Limited 7 A. Lindem (Editor) 8 Redback Networks 9 June 7, 2008 11 Traffic Engineering Extensions to OSPF version 3 12 draft-ietf-ospf-ospfv3-traffic-12.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 December 9, 2008. 39 Copyright Notice 41 Copyright (C) The IETF Trust (2008). 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. Management Considerations . . . . . . . . . . . . . . . . . . 12 64 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 66 8.1. Normative References . . . . . . . . . . . . . . . . . . . 14 67 8.2. Informative References . . . . . . . . . . . . . . . . . . 14 68 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 15 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 70 Intellectual Property and Copyright Statements . . . . . . . . . . 17 72 1. Introduction 74 OSPFv3 has a very flexible mechanism for adding new LS types. 75 Unknown LS types are flooded properly based on the flooding scope 76 bits in the LS type [OSPFV3]. This document defines the 77 Intra-Area-TE LSA to OSPFv3. 79 For Traffic Engineering, this document uses "Traffic Engineering 80 Extensions to OSPF" [TE] as a base for TLV definitions. New TLVs and 81 sub-TLVs are added to [TE] to extend TE capabilities to IPv6 82 networks. Some existing TLVs and sub-TLVs require clarification for 83 OSPFv3 applicability. 85 GMPLS [GMPLS] and the Diff-Serv MPLS Extensions [TE-DIFF] are based 86 on [TE]. These functions can also be extended to OSPFv3 by utilizing 87 the TLVs and sub-TLVs described in this document. 89 1.1. Requirements notation 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC2119 94 [RFC-KEYWORDS]. 96 2. Intra-Area-TE-LSA 98 A new LS type is defined for the Intra-Area-TE LSA. This is 99 different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are 100 used to advertise TE information [OPAQUE]. The LSA function code is 101 10, the U bit is set, and the scope is set to 01 for area-scoping. 102 When the U bit is set to 1, an OSPFv3 router must flood the LSA at 103 its defined flooding scope even if it does not recognize the LS type 104 [OSPFV3]. 106 0 1 2 3 107 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 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | LS age |1|0|1| 10 | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | Link State ID | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | Advertising Router | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | LS sequence number | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | LS checksum | Length | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | | 120 +- TLVs -+ 121 | ... | 123 OSPFv3 Intra-Area-TE-LSA 125 The Link State ID of an Intra-Area-TE LSA is an arbitrary value used 126 to maintain multiple Traffic Engineering LSAs. The LSA ID has no 127 topological significance. 129 The format of the TLVs within the body of an Intra-Area-TE LSA is the 130 same as the format used by the Traffic Engineering Extensions to OSPF 131 [TE]. The LSA payload consists of one or more nested Type/Length/ 132 Value (TLV) triplets. The format of each TLV is: 134 0 1 2 3 135 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 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | Type | Length | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | Value... | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 TLV Format 144 The Length field defines the length of the value portion in octets 145 (thus a TLV with no value portion would have a length of zero). The 146 TLV is padded to four-octet alignment; padding is not included in the 147 length field (so a three octet value would have a length of three, 148 but the total size of the TLV would be eight octets). Nested TLVs 149 are also 32-bit aligned. For example, a one-byte value would have 150 the length field set to 1, and three octets of padding would be added 151 to the end of the value portion of the TLV. Unrecognized types are 152 ignored. 154 2.1. Intra-Area-TE-LSA Payload 156 An Intra-Area-TE-LSA contains one top-level TLV. There are two 157 applicable top-level TLVs: 159 2 - Link TLV 161 3 - Router IPv6 Address TLV 163 3. Router IPv6 Address TLV 165 The Router IPv6 Address TLV advertises a reachable IPv6 address. 166 This is a stable IPv6 address that is always reachable if there is 167 connectivity to the OSPFv3 router. 169 The Router IPv6 Address TLV has type 3, length 16, and a value 170 containing a 16 octet local IPv6 address. A Link-local address MUST 171 NOT be specified for this TLV. It MUST appear in exactly one Traffic 172 Engineering LSA originated by an OSPFv3 router supporting the TE 173 extensions. The Router IPv6 Address TLV is a top-level TLV as 174 defined in Traffic Engineering Extensions to OSPF [TE] and only one 175 top-level TLV may be contained in an LSA. 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | 3 | 16 | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | | 183 +-+-+-+- -+-+-+-+ 184 | | 185 +-+-+-+- Router IPv6 Address -+-+-+-+ 186 | | 187 +-+-+-+- -+-+-+-+ 188 | | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 Type A 16-bit field set to 3. 192 Length A 16-bit field that indicates the length of the value 193 portion in octets. For this TLV it is always 16. 194 Value A stable and routable IPv6 address. 196 Router IPv6 Address TLV 198 4. Link TLV 200 The Link TLV describes a single link and consists of a set of sub- 201 TLVs [TE]. All of the sub-TLVs in [TE] other than the Link ID sub- 202 TLV are applicable to OSPFv3. The Link ID sub-TLV can't be used in 203 OSPFv3 since it is defined to use the OSPFv2 identification for the 204 Designated Router (DR) on multi-access networks. In OSPFv2, 205 neighbors on point-to-point networks and virtual links are identified 206 by their Router IDs while neighbors on broadcast, Non-Broadcast 207 Multi-Access (NBMA), and Point-to-Multipoint links are identified by 208 their IPv4 interface addresses (Refer to section 8.2 in [OSPFV2]). 209 The IPv4 interface address is not known to OSPFv3. In contrast to 210 OSPFv2, OSPFv3 always identifies neighboring routers by their Router 211 IDs (Refer to section 2.11 in [OSPFV3]). 213 Three new sub-TLVs for the Link TLV are defined: 215 18 - Neighbor ID (8 octets) 217 19 - Local Interface IPv6 Address (16N octets, where N is the 218 number of IPv6 addresses) 220 20 - Remote Interface IPv6 Address (16N octets, where N is the 221 number of IPv6 addresses) 223 The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering 224 support. It MUST appear exactly once in a Link TLV. All other sub- 225 TLVs defined in this document SHOULD NOT occur more than once in a 226 LINK TLV. If a sub-TLV is specified more than once, instances 227 subsequent to the first are ignored. 229 4.1. Link ID Sub-TLV 231 The Link ID sub-TLV is used in OSPFv2 to identify the other end of 232 the link. In OSPFv3, the Neighbor ID sub-TLV MUST be used for link 233 identification. In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent 234 and MUST be ignored upon receipt. 236 4.2. Neighbor ID Sub-TLV 238 In OSPFv2, the Link ID is used to identify the other end of a link. 239 In OSPFv3, the combination of Neighbor Interface ID and Neighbor 240 Router ID is used for neighbor link identification. Both are 241 advertised in the Neighbor ID Sub-TLV. 243 Neighbor Interface ID and Neighbor Router ID values are the same as 244 described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs. 246 0 1 2 3 247 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 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | 18 | 8 | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Neighbor Interface ID | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | Neighbor Router ID | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 Type A 16-bit field set to 18. 257 Length A 16-bit field that indicates the length of the value 258 portion in octets. For this sub-TLV it is always 8. 259 Value The neighbor's interface ID and router ID. 261 Neighbor ID Sub-TLV 263 4.3. Local Interface IPv6 Address Sub-TLV 265 The Local Interface IPv6 Address sub-TLV specifies the IPv6 266 address(es) of the interface corresponding to this link. If there 267 are multiple local addresses assigned to the link then they MAY all 268 be listed in this sub-TLV. Link-local addresses MUST NOT be included 269 in this sub-TLV. 271 0 1 2 3 272 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 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | 19 | Length | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 | | 277 +-+-+-+- -+-+-+-+ 278 | | 279 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 280 | | 281 +-+-+-+- -+-+-+-+ 282 | | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | o | 285 | o | 286 | o | 287 | | 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | | 290 +-+-+-+- -+-+-+-+ 291 | | 292 +-+-+-+- Local Interface IPv6 Address -+-+-+-+ 293 | | 294 +-+-+-+- -+-+-+-+ 295 | | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 Type A 16-bit field set to 19. 299 Length A 16-bit field that indicates the length of the value 300 portion in octets. For this sub-TLV, it MUST always be a 301 multiple of 16 octets dependent on the number of IPv6 302 global addresses advertised. 303 Value A list of one or more local IPv6 interface addresses 304 each consuming 16 octets. 306 Local Interface IPv6 Address Sub-TLV 308 4.4. Remote Interface IPv6 Address Sub-TLV 310 The Remote Interface IPv6 Address sub-TLV advertises the IPv6 311 address(es) associated with the neighbor's interface. This Sub-TLV 312 and the Local Interface IPv6 address Sub-TLV are used to discern 313 amongst parallel links between OSPFv3 routers. If the Link Type is 314 multi-access, the Remote Interface IPv6 Address MAY be set to ::. 315 Alternately, an implementation MAY choose not to send this sub-TLV. 316 Link-local addresses MUST NOT be advertised in this sub-TLV. 317 Neighbor addresses advertised in Link-LSAs with a prefix length of 318 128 and the LA bit set MAY be advertised. 320 0 1 2 3 321 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 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 | 20 | Length | 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 | | 326 +-+-+-+- -+-+-+-+ 327 | | 328 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 329 | | 330 +-+-+-+- -+-+-+-+ 331 | | 332 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 333 | o | 334 | o | 335 | o | 336 | | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | | 339 +-+-+-+- -+-+-+-+ 340 | | 341 +-+-+-+- Remote Interface IPv6 Address -+-+-+-+ 342 | | 343 +-+-+-+- -+-+-+-+ 344 | | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 Type A 16-bit field set to 20. 348 Length A 16-bit field that indicates the length of the value 349 portion in octets. For this sub-TLV, it MUST be a 350 multiple of 16 octets dependent on the number of IPv6 351 global addresses advertised. 352 Value A variable length remote interface IPv6 address list. 354 Remote Interface IPv6 Address Sub-TLV 356 5. Security Considerations 358 The function described in this document does not create any new 359 security issues for the OSPFv3 protocol. Security considerations for 360 the base OSPFv3 protocol [OSPFV3] and OSPFv2 Traffic Engineering [TE] 361 are applicable to OSPFv3 Traffic Engineering. 363 6. Management Considerations 365 The typical management interface for routers running the new 366 extensions to OSPF for intra-area Traffic Engineering is SNMP-based. 367 The extra management objects for configuration operations and 368 statistics are defined in [OSPFV3-MIB] and an implementation of the 369 extensions defined in this document SHOULD provide for the 370 appropriate hooks or instrumentation that allow for the MIB objects 371 to be implemented. 373 7. IANA Considerations 375 The following IANA assignments are to be made from existing 376 registries: 378 1. The OSPFv3 LSA type function code 10 needs to be assigned to the 379 OSPFv3 Intra-Area-TE-LSA. 381 2. The Router IPv6 Address TLV type 3 needs to be assigned from the 382 existing registry for OSPF TE TLVs. 384 3. The Neighbor ID Sub-TLV (18), Local Interface IPv6 Address Sub- 385 TLV (19), and Remote Interface IPv6 Address Sub-TLV (20), need to 386 be assigned from the existing registry for OSPF TE Sub-TLVs. 388 8. References 390 8.1. Normative References 392 [OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 394 [OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 395 for IPv6", draft-ietf-ospf-ospfv3-update-23.txt (work in 396 progress). 398 [RFC-KEYWORDS] 399 Bradner, S., "Key words for use in RFC's to Indicate 400 Requirement Levels", RFC 2119, March 1997. 402 [TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering 403 Extensions to OSPF", RFC 3630, September 2003. 405 8.2. Informative References 407 [GMPLS] Kompella, K. and Y. Rekhter, "OSPF Extensions in Support 408 of Generalized Multi-Protocol Switching (GMPLS)", 409 RFC 4203, October 2005. 411 [OPAQUE] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, 412 July 1998. 414 [OSPFV3-MIB] 415 Joyal, D. and V. Manral, "Management Information Base for 416 OSPFv3", draft-ietf-ospf-ospfv3-mib-12.txt (work in 417 progress). 419 [TE-DIFF] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, 420 P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi- 421 Protocol Label Switching (MPLS) Support of Differentiated 422 Services", RFC 3270. 424 Appendix A. Acknowledgments 426 Thanks to Kireeti Kompella, Alex Zinin, Adrian Farrell, and Mach Chen 427 for their comments. 429 Thanks to Vijay K. Gurbani for providing the General Area Review Team 430 (Gen-ART) review. 432 Thanks to Rob Austein for providing the Security Directorate (secdir) 433 review. 435 Thanks to Dan Romascanu for providing the text for the "Management 436 Considerations" Section 6 section in the context of the IESG review. 438 Thanks to Dave Ward, Tim Polk, Jari Arko, and Pasi Eronen for 439 comments and relevant discussion in the context of the IESG review. 441 The RFC text was produced using Marshall Rose's xml2rfc tool. 443 Authors' Addresses 445 Kunihiro Ishiguro 446 IP Infusion, Inc 447 125 South Market Street, Suite 900 448 San Jose, CA 95113 449 USA 451 Email: kunihiro@ipinfusion.com 453 Vishwas Manral 454 IP Infusion, Inc 455 #41, Ground Floor, 5th Cross Road 456 8th Main Road 457 Vasanth Nagar, Bangalore 560052 458 India 460 Email: vishwas@ipinfusion.com 462 Alan Davey 463 Data Connection Limited 464 100 Church Street 465 Enfield 466 EN2 6BQ 467 UK 469 Email: Alan.Davey@dataconnection.com 471 Acee Lindem 472 Redback Networks 473 102 Carric Bend Court 474 Cary, NC 27519 475 USA 477 Email: acee@redback.com 479 Full Copyright Statement 481 Copyright (C) The IETF Trust (2008). 483 This document is subject to the rights, licenses and restrictions 484 contained in BCP 78, and except as set forth therein, the authors 485 retain all their rights. 487 This document and the information contained herein are provided on an 488 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 489 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 490 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 491 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 492 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 493 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 495 Intellectual Property 497 The IETF takes no position regarding the validity or scope of any 498 Intellectual Property Rights or other rights that might be claimed to 499 pertain to the implementation or use of the technology described in 500 this document or the extent to which any license under such rights 501 might or might not be available; nor does it represent that it has 502 made any independent effort to identify any such rights. Information 503 on the procedures with respect to rights in RFC documents can be 504 found in BCP 78 and BCP 79. 506 Copies of IPR disclosures made to the IETF Secretariat and any 507 assurances of licenses to be made available, or the result of an 508 attempt made to obtain a general license or permission for the use of 509 such proprietary rights by implementers or users of this 510 specification can be obtained from the IETF on-line IPR repository at 511 http://www.ietf.org/ipr. 513 The IETF invites any interested party to bring to its attention any 514 copyrights, patents or patent applications, or other proprietary 515 rights that may cover technology that may be required to implement 516 this standard. Please address the information to the IETF at 517 ietf-ipr@ietf.org. 519 Acknowledgment 521 Funding for the RFC Editor function is provided by the IETF 522 Administrative Support Activity (IASA).