idnits 2.17.1 draft-nadeau-mpls-mgmt-overview-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 3 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC3031]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 2001) is 8229 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) == Missing Reference: 'MPLSArch' is mentioned on line 166, but not defined == Missing Reference: 'LDPMIB' is mentioned on line 97, but not defined == Missing Reference: 'TC-MIB' is mentioned on line 157, but not defined == Missing Reference: 'SMIv2TC' is mentioned on line 158, but not defined == Missing Reference: 'MPLSFW' is mentioned on line 166, but not defined == Missing Reference: 'VPNMIB' is mentioned on line 274, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'FTNMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LBMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWE3ARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'PPVPNFW' ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) Summary: 16 errors (**), 0 flaws (~~), 9 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: April 2002 4 Cheenu Srinivasan 5 Alphion Corp. 7 Adrian Farrel 8 Movaz Networks, Inc. 10 October 2001 12 Multiprotocol Label Switching (MPLS) Management Overview 14 draft-nadeau-mpls-mgmt-overview-00.txt 16 Status of this Memo 18 This document is an Internet-Draft and is in full 19 conformance with all provisions of Section 10 of RFC 2026 20 [RFC2026]. 22 Internet-Drafts are working documents of the Internet 23 Engineering Task Force (IETF), its areas, and its working 24 groups. Note that other groups may also distribute working 25 documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of 28 six months and may be updated, replaced, or obsoleted by 29 other documents at any time. It is inappropriate to use 30 Internet-Drafts as reference material or to cite them other 31 than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be 37 accessed at http://www.ietf.org/shadow.html. 39 Table of Contents 41 Abstract ................................................... 2 42 1. Introduction ............................................ 2 43 2. Terminology ............................................. 2 44 3. The SNMP Management Framework ........................... 3 45 4. MIBs Addressed by the MPLS Management Framework ......... 4 46 4.1. MPLS-TC-MIB ........................................... 4 47 4.2. MPLS-LSR-MIB .......................................... 4 48 4.2.1.Dependencies ......................................... 4 49 4.3. MPLS-LDP-MIB .......................................... 5 50 4.3.1.Dependencies ......................................... 5 51 4.4. MPLS-TE-MIB ........................................... 5 52 4.4.1.Dependencies ......................................... 5 53 4.5. MPLS-FTN-MIB .......................................... 5 54 4.5.1.Dependencies ......................................... 6 55 4.6. MPLS-LINK-BUNDLING-MIB ................................ 6 56 4.6.1.Dependencies ......................................... 6 57 4.7. PPVPN-MPLS-VPN-MIB .................................... 6 58 4.7.1.Dependencies ......................................... 6 59 5. Dependencies on Other IETF Working Groups ............... 7 60 5.1. Pseudo Wire Emulation Edge to Edge MIBs ............... 7 61 5.2. Provider Provisioned Virtual Private Network MIBs ..... 7 62 5.3. Common Control and Measurement Plane (ccamp) WG ....... 7 63 6. Security Considerations ................................. 7 64 7. Acknowledgments ......................................... 7 65 8. References .............................................. 8 66 9. Authors' Addresses ..................................... 10 67 10. Full Copyright Statement .............................. 11 69 Abstract 71 This memo describes the Multi-Protocol Label Switching 72 (MPLS) [RFC3031] management architecture and the inter- 73 relationships between the different management information 74 bases (MIBs). 76 1. Introduction 78 This memo defines a Management Architecture for Multi- 79 Protocol Label Switching. In particular, it describes how 80 various managed objects defined in various Management 81 Information Base (MIB) documents model different aspects of 82 Multi-Protocol Label Switching (MPLS) [MPLSArch]. 83 Furthermore, this document explains the interactions and 84 dependencies between each of these documents. 86 Comments should be made directly to the MPLS mailing list 87 at mpls@uu.net. 89 This memo does not, in its draft form, specify a standard 90 for the Internet community. 92 2. Terminology 94 This document uses terminology from the MPLS architecture 95 document [MPLSArch] and various MPLS-related MIBs such as 96 the MPLS-TC-MIB [TCMIB], MPLS-LSR-MIB [LSRMIB], MPLS-TE-MIB 97 [TEMIB], MPLS-LDP-MIB [LDPMIB], MPLS-FTN-MIB [FTNMIB], and 98 the MPLS-LINK-BUNDLING-MIB [LBMIB]. 100 3. The SNMP Management Framework 102 The SNMP Management Framework presently consists of five 103 major components: 105 - An overall architecture, described in RFC 2571 106 [RFC2571]. 108 - Mechanisms for describing and naming objects and events 109 for the purpose of management. The first version of 110 this Structure of Management Information (SMI) is 111 called SMIv1 and described in STD 16, RFC 1155 112 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, RFC 113 1215 [RFC1215]. The second version, called SMIv2, is 114 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 115 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 117 - Message protocols for transferring management 118 information. The first version of the SNMP message 119 protocol is called SNMPv1 and described in STD 15, RFC 120 1157 [RFC1157]. A second version of the SNMP message 121 protocol, which is not an Internet standards track 122 protocol, is called SNMPv2c and described in RFC 1901 123 [RFC1901] and RFC 1906 [RFC1906]. The third version of 124 the message protocol is called SNMPv3 and described in 125 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 126 [RFC2574]. 128 - Protocol operations for accessing management 129 information. The first set of protocol operations and 130 associated PDU formats is described in STD 15, RFC 1157 131 [RFC1157]. A second set of protocol operations and 132 associated PDU formats is described in RFC 1905 133 [RFC1905]. 135 - A set of fundamental applications described in RFC 2573 136 [RFC2573] and the view-based access control mechanism 137 described in RFC 2575 [RFC2575]. 139 A more detailed introduction to the current SNMP Management 140 Framework can be found in RFC 2570 [RFC2570]. 142 Managed objects are accessed via a virtual information 143 store, termed the Management Information Base or MIB. 144 Objects in the MIB are defined using the mechanisms defined 145 in the SMI. 147 4. MIBs Addressed by the MPLS Management Framework 149 This section will briefly explain what the purpose of each 150 MPLS-related MIB is and what it can be used for. Each 151 section contains a subsection that details the 152 interdependencies between that MIB and any of the other 153 MPLS MIBs. 155 4.1. MPLS-TC-MIB 157 The MPLS-TC-MIB [TC-MIB] describes textual conventions 158 [SMIv2TC] and object identities that may be common to MPLS- 159 related MIBs. For example, the textual convention for 160 representing an MPLS label should be commonly represented 161 and used by all MPLS-related MIBs. 163 4.2. MPLS-LSR-MIB 165 The MPLS-LSR-MIB describes managed objects for modeling a 166 Multi-Protocol Label Switching (MPLS) [MPLSArch, MPLSFW] 167 Label Switch Router (LSR). In particular, this MIB is used 168 to model and manage the basic label switching behavior and 169 the label forwarding information base (LFIB) of an MPLS 170 LSR. In doing so, the MIB provides a view of the LSPs that 171 are being switched by the LSR in question. 173 This MIB is the basis for many of the MPLS MIBs, since 174 basic MPLS label switching is common to all MPLS 175 applications. In general, the MPLS-LSR-MIB provides a 176 model of incoming labels on MPLS-enabled interfaces being 177 mapped to outgoing labels on MPLS-enabled interfaces via a 178 conceptual object called an MPLS cross-connect. MPLS cross- 179 connect entries and their properties are represented in the 180 MPLS cross-connect table (mplsXCTable) in the LSR MIB. MPLS 181 cross-connect entries are typically referred to by other 182 MIBs in order to reference the underlying MPLS LSP. 184 For example, the MPLS-TE-MIB [TEMIB] models traffic 185 engineered tunnels. These tunnels map to one more 186 underlying MPLS LSPs. Thus, the MPLS-TE-MIB's tunnel table 187 (mplsTunnelTable) entries refer to the underlying LSP by 188 pointing to entries in mplsXCTable. 190 4.2.1. Dependencies 192 This MIB does not directly depend upon any other MPLS MIBs. 193 It does represent MPLS-enabled interfaces as entries in the 194 Interfaces MIB [RFC2233] Interface Table (ifTable). This 195 MIB imports several textual conventions from the MPLS-TC- 196 MIB [TCMIB]. 198 4.3. MPLS-LDP-MIB 200 The MPLS-LDP-MIB describes managed objects used to model 201 and manage the Multiprotocol Label Switching Label 202 Distribution Protocol (LDP). 204 4.3.1. Dependencies 206 Forward Equivalency Class (FEC) entries in the LDP MIB�s 207 xxxx table () are mapped to LSPs by pointing to an entry in 208 mplsXCTable in the MPLS-LSR-MIB. This MIB also imports 209 several textual conventions from the MPLS-TC-MIB [TCMIB]. 211 4.4. MPLS-TE-MIB 213 The MPLS-TE-MIB [TEMIB] describes managed objects that are 214 used to model and manage MPLS Traffic Engineered (TE) 215 Tunnels. The MIB is based around a table that represents TE 216 tunnels that either originate at the LSR in question or 217 traverse via or terminate on the LSR. Note that the later 218 case is optional, as only tunnel "heads" are required to be 219 represented. This MIB provides statistics and configuration 220 objects needed for TE tunnels. 222 4.4.1. Dependencies 224 This MIB depends on the MPLS-LSR-MIB [LSRMIB] and 225 Interfaces MIB [RFC2233]. Tunnel entries in the MPLS-TE- 226 MIB�s mplsTunnelTable refer to entries in mplsXCTable in 227 the MPLS-LSR-MIB. When MPLS TE tunnels are represented as 228 interfaces, entries for such tunnels in mplsTunnelTable 229 have corresponding entries in the Interfaces MIB�s 230 [RFC2233] Interfaces Table (ifTable). This MIB also imports 231 several textual conventions from the MPLS-TC-MIB [TCMIB]. 233 4.5. MPLS-FTN-MIB 235 The MPLS-FTN-MIB [FTNMIB] describes managed objects that 236 are used to model and manage the MPLS FEC-to-NHLFE mappings 237 which take place at any LSR that is on the edge between an 238 MPLS domain and a non-MPLS domain. On each such edge LSR, 239 to map traffic from the non-MPLS domain into the MPLS 240 domain, the FEC-to-NHLFE mapping objects in the MPLS-FTN- 241 MIB must be supported. In the case of an IP-to-MPLS 242 mapping, the FEC objects describe IP 5-tuples representing 243 IP source and destination ranges, protocol ranges etc. 244 Matching IP packets can be mapped to an NHLFE which can 245 either be an MPLS LSP or an MPLS TE tunnel. 247 4.5.1. Dependencies 249 This MIB relies directly on the MPLS-LSR-MIB [LSRMIB] and 250 MPLS-TE-MIB [TEMIB]. FECs can be mapped to two types of 251 NHLFEs by the MPLS-FTN-MIB. When the NHLFE is an LSP, the 252 FEC-to-NHLFE mapping is accomplished by referring to a 253 corresponding entry in mplsXCTable in the MPLS-LSR-MIB. 254 When the NHLFE is an MPLS TE tunnel, this mapping is 255 accomplished by referring to a corresponding entry in 256 mplsTunnelTable in MPLS-TE-MIB. 258 4.6. MPLS-LINK-BUNDLING-MIB 260 The MPLS-LINK-BUNDLING-MIB [LBMIB] describes managed 261 objects that are used to model and manage the MPLS TE 262 interfaces, as well as the link bundling relationship that 263 may exist between those interfaces. 265 4.6.1. Dependencies 267 The MPLS-LINK-BUNDLING-MIB [LBMIB] interacts directly only 268 with the Interfaces MIB [RFC2233]; it references MPLS TE 269 interfaces that are modeled by entries in the interfaces 270 table (ifTable) in the Interfaces MIB [RFC2233]. 272 4.7. PPVPN-MPLS-VPN-MIB 274 The PPVPN-MPLS-VPN-MIB [VPNMIB] describes managed objects 275 that are used to model and manage RFC2277bis MPLS VPNs. 276 This MIB contains tables which model virtual routing 277 forwarding entries (VRFs), as well as the interfaces 278 associated with those VRFs. 280 4.7.1. Dependencies 282 This MIB currently has not direct dependencies to any of 283 the MPLS MIBs. This MIB does model MPLS VPN interfaces as 284 entries in the Interfaces MIB [RFC2233]. This MIB may be 285 modified in the future to import textual conventions from 286 the MPLS-TC-MIB [TCMIB]. 288 5. Dependencies on Other IETF Working Groups 290 This section will detail the broad interactions between 291 other working groups and the MPLS MIBs. 293 5.1. Pseudo Wire Emulation Edge to Edge MIBs 295 The Pseudo Wire Emulation Edge to Edge (pwe3) working group 296 has produced a framework [PWE3ARCH] describes a framework 297 for PWE3 MIBs. Since the PWE3 architecture includes the use 298 of MPLS as an emulated service and as a PSN service, the 299 MPLS MIBs described above may be leveraged. This framework 300 document describes the interactions between the MPLS MIBs 301 and the PWE3 MIBs. 303 5.2. Provider Provisioned Virtual Private Network MIBs 305 At present, the Provider Provisioned Virtual Private 306 Network (PPVPN) working group has not included a discussion 307 of how the MPLS MIBs interact with the MIBs being produced 308 by that working group. The authors of this draft hope to 309 make a forthcoming addition to their framework [PPVPNFW] 310 document detailing these interactions. At the moment, there 311 is only a single MIB produced which interacts with the MPLS 312 MIBs, as this MIB is described above in section 314 5.3. Common Control and Measurement Plane (ccamp) WG 316 At present, there are no MIBs produced by the CCAMP working 317 group that interact directly with the MPLS MIBs. However, 318 in the future, the existing MPLS MIBs will need to be 319 extended and augmented to facilitate the technology being 320 produced by this working group. 322 6. Security Considerations 324 This document describes the inter-relationships amongst the 325 different MIBs relevant to MPLS management and as such does 326 not have any security implications beyond those imposed by 327 these MIBs themselves. 329 7. Acknowledgments 331 TBD. 333 8. References 335 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 336 Viswanathan, A. and H. Sjostrand, 337 "Definition of Textual Conventions and 338 OBJECT-IDENTITIES for Multi-Protocol Label 339 Switching (MPLS) Management", Internet Draft 340 , August 341 2001. 343 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 344 Nadeau, "MPLS Label Switch Router Management 345 Information Base Using SMIv2", Internet 346 Draft , 347 January 2001. 349 [TEMIB] Srinivasan, C., Viswanathan, A. and T. 350 Nadeau, "MPLS Traffic Engineering Management 351 Information Base Using SMIv2", Internet 352 Draft , 353 August 2001. 355 [FTNMIB] Nadeau, T., Srinivasan, C., and A. 356 Viswanathan, "Multiprotocol Label Switching 357 (MPLS) FEC-To-NHLFE (FTN) Management 358 Information Base", Internet Draft , August 2001. 361 [LBMIB] Dubuc, M., Dharanikota, S., Nadeau, T., J. 362 Lang, "Link Bundling Management Information 363 Base Using SMIv2", Internet Draft , September 365 2001. 367 [PWE3ARCH] Pate, P., Xiao, X., White., C., Kompella., 368 K., Malis, A., Johnson, T., and T. Nadeau, 369 "Framework for Pseudo Wire Emulation Edge-to- 370 Edge (PWE3)", Internet Draft , September, 2001. 373 [PPVPNFW] Callon, R., Suzuki, M., Gleeson, B., Malis, 374 A., Muthukrishnan, K., Rosen, E., Sargor, 375 C., and J. Yu, "A Framework for Provider 376 Provisioned Virtual Private Networks", 377 Internet Draft , July 2001. 380 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 381 Identification of Management Information for 382 TCP/IP-based Internets", RFC 1155, May 1990. 384 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 385 Davin, "Simple Network Management Protocol", 386 RFC 1157, May 1990. 388 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 389 Definitions", RFC 1212, March 1991. 391 [RFC1215] M. Rose, "A Convention for Defining Traps 392 for use with the SNMP", RFC 1215, March 393 1991. 395 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 396 Waldbusser, "Introduction to Community-based 397 SNMPv2", RFC 1901, January 1996. 399 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 400 Waldbusser, "Protocol Operations for Version 401 2 of the Simple Network Management Protocol 402 (SNMPv2)", RFC 1905, January 1996. 404 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 405 Waldbusser, "Transport Mappings for Version 406 2 of the Simple Network Management Protocol 407 (SNMPv2)", RFC 1906, January 1996. 409 [RFC2026] S. Bradner, "The Internet Standards Process 410 -- Revision 3", RFC 2026, October 1996. 412 [RFC2233] McCloghrie, K. and F. Kastenholtz, "The 413 Interface Group MIB Using SMIv2", RFC 2233, 414 November 1997. 416 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 417 Stewart, "Introduction to Version 3 of the 418 Internet-standard Network Management 419 Framework", RFC 2570, April 1999. 421 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 422 "An Architecture for Describing SNMP 423 Management Frameworks", RFC 2571, April 424 1999. 426 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 427 Wijnen, "Message Processing and Dispatching 428 for the Simple Network Management Protocol 429 (SNMP)", RFC 2572, April 1999. 431 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 432 Applications", RFC 2573, April 1999. 434 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 435 Security Model (USM) for version 3 of the 436 Simple Network Management Protocol 437 (SNMPv3)", RFC 2574, April 1999. 439 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 440 "View-based Access Control Model (VACM) for 441 the Simple Network Management Protocol 442 (SNMP)", RFC 2575, April 1999. 444 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 445 J., Case, J., Rose, M., and S. Waldbusser, 446 "Structure of Management Information Version 447 2 (SMIv2)", STD 58, RFC 2578, April 1999. 449 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 450 J., Case, J., Rose, M., and S. Waldbusser, 451 "Textual Conventions for SMIv2", STD 58, RFC 452 2579, April 1999. 454 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 455 J., Case, J., Rose, M., and S. Waldbusser, 456 "Conformance Statements for SMIv2", STD 58, 457 RFC 2580, April 1999. 459 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 460 "Multiprotocol Label Switching 461 Architecture", RFC 3031, January 2001. 463 9. Authors' Addresses 465 Thomas D. Nadeau 466 Cisco Systems, Inc. 467 300 Apollo Drive 468 Chelmsford, MA 01824 469 Phone: +1-978-244-3051 470 Email: tnadeau@cisco.com 472 Cheenu Srinivasan 473 Alphion Corp. 474 4 Industrial Way West 475 Eatontown, NJ 07724 476 Phone: +1-732-676-7066 477 Email: cheenu@alphion.com 479 Adrian Farrel 480 Movaz Networks, Inc. 482 7926 Jones Branch Drive, Suite 615 483 McLean, VA 22102 484 Phone: +1-703-847-9847 485 Email: afarrel@movaz.com 487 10. Full Copyright Statement 489 Copyright (C) The Internet Society (2001). All Rights 490 Reserved. 492 This document and translations of it may be copied and 493 furnished to others, and derivative works that comment on 494 or otherwise explain it or assist in its implementation may 495 be prepared, copied, published and distributed, in whole or 496 in part, without restriction of any kind, provided that the 497 above copyright notice and this paragraph are included on 498 all such copies and derivative works. However, this 499 document itself may not be modified in any way, such as by 500 removing the copyright notice or references to the Internet 501 Society or other Internet organizations, except as needed 502 for the purpose of developing Internet standards in which 503 case the procedures for copyrights defined in the Internet 504 Standards process must be followed, or as required to 505 translate it into languages other than English. 507 The limited permissions granted above are perpetual and 508 will not be revoked by the Internet Society or its 509 successors or assigns. This document and the information 510 contained herein is provided on an "AS IS" basis and THE 511 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 512 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 513 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 514 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 515 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 516 PURPOSE.