idnits 2.17.1 draft-ietf-gsmp-mib-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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 14 pages 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. ** There are 10 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 545 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (September 1999) is 8991 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: 'RFC2434' is defined on line 488, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 502, but no explicit reference was found in the text == Unused Reference: 'RFC2233' is defined on line 506, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 512, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Downref: Normative reference to an Informational RFC: RFC 1987 ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) -- Possible downref: Non-RFC (?) normative reference: ref. '24' Summary: 19 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group H. Sjostrand 2 Internet-Draft Ericsson 3 Expires March 2000 September 1999 5 Definitions of Managed Objects for 6 the General Switch Management Protocol (GSMP) 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC 2026. Internet-Drafts are 14 working documents of the Internet Engineering Task Force (IETF), its 15 areas, and its working groups. Note that other groups may also 16 distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress". 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html 29 Distribution of this document is unlimited. Please send comments to 30 the General Switch Management Protocol (gsmp) Working Group, 31 . 33 Copyright Notice 35 Copyright (C) The Internet Society (1999). All Rights Reserved. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects for the General Switch 42 Management Protocol (GSMP). 44 Table of Contents 46 1 Introduction ................................................. 3 47 2 The SNMP Management Framework ................................ 3 48 3 Structure of the MIB ......................................... 5 49 3.1 The GSMP Server Group ...................................... 5 50 3.1.1 The GSMP Control Port .................................... 5 51 3.1.2 The GSMP Status .......................................... 5 52 3.1.3 The GSMP Port table ...................................... 5 53 3.2 The GSMP Notifications Group ............................... 5 54 4 GSMP MIB Definitions ......................................... 5 55 5 Revision History ............................................. 11 56 6 Acknowledgments .............................................. 11 57 7 References ................................................... 11 58 8 Security Considerations ...................................... 13 59 9 Authors' Addresses ........................................... 13 60 10 Full Copyright Statement .................................... 13 62 1. Introduction 64 This memo defines a portion of the Management Information Base (MIB) 65 for use with network management protocols in the Internet community. 66 In particular, it describes managed objects for the General Switch 67 Management Protocol (gsmp) [RFC1987]. 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in RFC 2119 [RFC2119]. 73 2. The SNMP Management Framework 75 The SNMP Management Framework presently consists of five major 76 components: 78 o An overall architecture, described in RFC 2571 [RFC2571]. 80 o Mechanisms for describing and naming objects and events for the 81 purpose of management. The first version of this Structure of 82 Management Information (SMI) is called SMIv1 and described in 83 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 84 1215 [RFC1215]. The second version, called SMIv2, is described 85 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 86 [RFC2580]. 88 o Message protocols for transferring management information. The 89 first version of the SNMP message protocol is called SNMPv1 and 90 described in STD 15, RFC 1157 [RFC1157]. A second version of the 91 SNMP message protocol, which is not an Internet standards track 92 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 93 and RFC 1906 [RFC1906]. The third version of the message 94 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 95 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 97 o Protocol operations for accessing management information. The 98 first set of protocol operations and associated PDU formats is 99 described in STD 15, RFC 1157 [RFC1157]. A second set of 100 protocol operations and associated PDU formats is described in 101 RFC 1905 [RFC1905]. 103 o A set of fundamental applications described in RFC 2573 104 [RFC2573] and the view-based access control mechanism described 105 in RFC 2575 [RFC2575]. 107 A more detailed introduction to the current SNMP Management Framework 108 can be found in RFC 2570 [RFC2570]. 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. Objects in the MIB are 112 defined using the mechanisms defined in the SMI. 114 This memo specifies a MIB module that is compliant to the SMIv2. A 115 MIB conforming to the SMIv1 can be produced through the appropriate 116 translations. The resulting translated MIB must be semantically 117 equivalent, except where objects or events are omitted because no 118 translation is possible (use of Counter64). Some machine readable 119 information in SMIv2 will be converted into textual descriptions in 120 SMIv1 during the translation process. However, this loss of machine 121 readable information is not considered to change the semantics of the 122 MIB. 124 3. Structure of the MIB 126 This mib modelsprovides some managed objects according to GSMP v1.1 127 [RFC1987]. It does not address any of the new features in version 2 128 [RFC2397]. It is provided as a base for the work within the working 129 group to define a mib. 131 3.1 The GSMP Server Group 133 3.1.1. The GSMP Control Port 135 Used to configure the interface used for the control port. This 136 does not deal with the extended bearer capabilities of [24]. 138 3.1.2. The GSMP Status 140 The status of the GSMP adjacency. THis does not deal with the 141 additional states defined in [24]. 143 3.1.3. The GSMP Port table 145 This is a read only table of all ports available to the GSMP. This 146 does not deal with the new interface types or cababilities as defined 147 in [24]. 149 3.2. The GSMP Notifications Group 151 This is currently empty, but should be extended with notifications as 152 defined in [24]. 154 4. GSMP MIB Definitions 156 GSMP-MIB DEFINITIONS ::= BEGIN 158 IMPORTS 159 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 160 Unsigned32, experimental 161 FROM SNMPv2-SMI 162 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 163 FROM SNMPv2-CONF 164 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeInterval 165 FROM SNMPv2-TC 166 InterfaceIndex 167 FROM IF-MIB 168 AtmVcIdentifier, AtmVpIdentifier 169 FROM ATM-TC-MIB 170 ; 172 gsmpMIB MODULE-IDENTITY 173 LAST-UPDATED "9910111200Z" -- October 11, 1999 174 ORGANIZATION "General Switch Management Protocol (gsmp) Working 175 Group" 176 CONTACT-INFO 177 "Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 178 Ericsson" 179 DESCRIPTION 180 "This MIB contains managed object definitions for the 181 General Switch Management Protocol, GSMP, as defined in 182 [RFC1987]." 183 ::= { experimental 9877 } -- to be assigned 185 --**************************************************************** 186 -- GSMP Textual Conventions 187 --**************************************************************** 189 gsmpServerObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } 190 gsmpClientObjects OBJECT IDENTIFIER ::= { gsmpMIB 2 } 191 gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 3 } 192 gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 4 } 194 --**************************************************************** 195 -- GSMP Objects 196 --**************************************************************** 197 -- 198 -- GSMP Control Port 199 -- 201 gmspCtrlPortId OBJECT-TYPE 202 SYNTAX InterfaceIndex 203 MAX-ACCESS read-write 204 STATUS current 205 DESCRIPTION 206 "Identifyer of the interface which is used by the control 207 part to control via GSMP the forwarding part. In the case 208 with intergrated control part, this object is undefined. 209 Changing this value is not allowed if thera are any gsmp 210 ports defined. " 211 ::= { gsmpServerObjects 1 } 213 -- 214 -- GSMP Status 215 -- 216 gsmpAdjacencyStatus OBJECT-TYPE 217 SYNTAX INTEGER { 218 up(1), 219 down(2) 220 } 221 MAX-ACCESS read-only 222 STATUS current 223 DESCRIPTION 224 "Gives the status of the GSMP adjacency." 225 ::= { gsmpServerObjects 2 } 227 -- 228 -- GSMP Port table 229 -- 231 gsmpPortTable OBJECT-TYPE 232 SYNTAX SEQUENCE OF GsmpPortEntry 233 MAX-ACCESS not-accessible 234 STATUS current 235 DESCRIPTION 236 "The table showing all ports that are accesible and 237 controlable over the GSMP interface." 238 ::= { gsmpServerObjects 3 } 240 gsmpPortEntry OBJECT-TYPE 241 SYNTAX GsmpPortEntry 242 MAX-ACCESS not-accessible 243 STATUS current 244 DESCRIPTION 245 "An entry in the table showing 246 the data belonging to one port as 247 defined over the GSMP interface." 248 INDEX { gsmpPortId } 249 ::= { gsmpPortTable 1 } 251 GsmpPortEntry ::= SEQUENCE { 252 gsmpPortId InterfaceIndex, 253 gsmpPortSessionNbr Unsigned32, 254 gsmpPortMinVpi INTEGER, 255 gsmpPortMinVci INTEGER, 256 gsmpPortMaxVpi INTEGER, 257 gsmpPortMaxVci INTEGER, 258 gsmpPortCellRate Unsigned32, 259 gsmpPortStatus INTEGER, 260 gsmpPortLineStatus INTEGER 261 } 263 gsmpPortId OBJECT-TYPE 264 SYNTAX InterfaceIndex 265 MAX-ACCESS not-accessible 266 STATUS current 267 DESCRIPTION 268 "This attribute identifies the ATM port over GSMP to 269 to this ocnfiguration information refers. 270 It corresponds to the IfIndex. " 271 ::= { gsmpPortEntry 1 } 273 gsmpPortSessionNbr OBJECT-TYPE 274 SYNTAX Unsigned32 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "The current Port Session Number for the specified port. 279 Each switch port maintains a Port Session Number assigned 280 by the switch. The Port Session Number of a port remains 281 unchanged while the port is continuously in the Available 282 state. When a port returns to the Available state after it 283 has been Unavailable, or after a power cycle, its Port 284 Session Number is changed." 285 ::= { gsmpPortEntry 2 } 287 gsmpPortMinVpi OBJECT-TYPE 288 SYNTAX AtmVpIdentifier 289 MAX-ACCESS read-only 290 STATUS current 291 DESCRIPTION 292 "The minimum value of dynamically assigned incoming VPI that 293 the connection table on the input port can support and may 294 be controlled by GSMP." 295 ::= { gsmpPortEntry 3 } 297 gsmpPortMinVci OBJECT-TYPE 298 SYNTAX AtmVcIdentifier 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The minimum value of dynamically assigned incoming VCI that 303 the connection table on the input port can support and may 304 be controlled by GSMP." 305 ::= { gsmpPortEntry 4 } 307 gsmpPortMaxVpi OBJECT-TYPE 308 SYNTAX AtmVpIdentifier 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The maximum value of dynamically assigned incoming VPI that 313 the connection table on the input port can support and may 314 be controlled by GSMP. It is assumed that the input port 315 can handle all values of VPI within the range Min VPI to 316 Max VPI inclusive and that GSMP may control all values 317 within this range." 318 ::= { gsmpPortEntry 5 } 320 gsmpPortMaxVci OBJECT-TYPE 321 SYNTAX AtmVpIdentifier 322 MAX-ACCESS read-only 323 STATUS current 324 DESCRIPTION 325 "The maximum value of dynamically assigned incoming VPI that 326 the connection table on the input port can support and may 327 be controlled by GSMP. It is assumed that the input port 328 can handle all values of VPI within the range Min VPI to 329 Max VPI inclusive and that GSMP may control all values 330 within this range." 331 ::= { gsmpPortEntry 6 } 333 gsmpPortCellRate OBJECT-TYPE 334 SYNTAX Unsigned32 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "A measure of the bandwidth of the port. It is the rate of 339 cells arriving at or departing from the port in cells/s. It 340 is assumed that both input port and output port have the 341 same cell rate." 342 ::= { gsmpPortEntry 7 } 344 gsmpPortStatus OBJECT-TYPE 345 SYNTAX INTEGER { 346 available(1), 347 unavailable(2), 348 internalloopback(3), 349 externalloopback(4), 350 bothwayloopback(5) 351 } 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "Gives the administrative state of the port." 356 ::= { gsmpPortEntry 8 } 358 gsmpPortLineStatus OBJECT-TYPE 359 SYNTAX INTEGER { 360 up(1), 361 down(2), 362 test(3) 363 } 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The status of the physical transmission medium connected to 368 the port." 369 ::= { gsmpPortEntry 9 } 371 --****************************************************************** 372 -- Module Compliance Statement 373 --****************************************************************** 375 gsmpGroups 376 OBJECT IDENTIFIER ::= { gsmpConformance 1 } 378 gsmpCompliances 379 OBJECT IDENTIFIER ::= { gsmpConformance 2 } 381 gsmpModuleCompliance MODULE-COMPLIANCE 382 STATUS current 383 DESCRIPTION 384 "The compliance statement for agents that support 385 the GSMP MIB." 386 MODULE -- this module 387 MANDATORY-GROUPS { 388 gsmpServerGroup 389 } 390 ::= { gsmpCompliances 1 } 392 -- units of conformance 394 gsmpServerGroup OBJECT-GROUP 395 OBJECTS { 396 gmspCtrlPortId, 397 gsmpAdjacencyStatus, 398 gsmpPortSessionNbr, 399 gsmpPortMinVpi, 400 gsmpPortMinVci, 401 gsmpPortMaxVpi, 402 gsmpPortMaxVci, 403 gsmpPortCellRate, 404 gsmpPortStatus, 405 gsmpPortLineStatus 406 } 407 STATUS current 408 DESCRIPTION 409 "Objects that apply to all GSMP Server implementations." 410 ::= { gsmpGroups 1 } 412 END 414 5. Revision History 416 This section should be removed when this document is published as an 417 RFC. 419 This is the 00 version. 421 6. Acknowledgments 423 The authors would like to thank the following people: Zoltan Takacs 424 and Bo Augustsson from Ericsson. 426 7. References 428 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 429 for Describing SNMP Management Frameworks", RFC 2571, April 430 1999 432 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 433 of Management Information for TCP/IP-based Internets", STD 434 16, RFC 1155, May 1990 436 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 437 16, RFC 1212, March 1991 439 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 440 SNMP", RFC 1215, March 1991 442 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 443 Rose, M., and S. Waldbusser, "Structure of Management 444 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 446 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 447 Rose, M., and S. Waldbusser, "Textual Conventions for 448 SMIv2", STD 58, RFC 2579, April 1999 450 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 451 Rose, M., and S. Waldbusser, "Conformance Statements for 452 SMIv2", STD 58, RFC 2580, April 1999 454 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 455 Network Management Protocol", STD 15, RFC 1157, May 1990. 457 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 458 "Introduction to Community-based SNMPv2", RFC 1901, January 459 1996. 461 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 462 "Transport Mappings for Version 2 of the Simple Network 463 Management Protocol (SNMPv2)", RFC 1906, January 1996. 465 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 466 Processing and Dispatching for the Simple Network Management 467 Protocol (SNMP)", RFC 2572, April 1999 469 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 470 (USM) for version 3 of the Simple Network Management 471 Protocol (SNMPv3)", RFC 2574, April 1999 473 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 474 "Protocol Operations for Version 2 of the Simple Network 475 Management Protocol (SNMPv2)", RFC 1905, January 1996. 477 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 478 RFC 2573, April 1999 480 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 481 Access Control Model (VACM) for the Simple Network 482 Management Protocol (SNMP)", RFC 2575, April 1999 484 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 485 "Introduction to Version 3 of the Internet-standard Network 486 Management Framework", RFC 2570, April 1999 488 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an 489 IANA Considerations Section in RFCs.", RFC 2434, IBM, 490 Maxware, October 1998 492 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching 493 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 494 Switch Management Protocol Specification," Version 1.1, 495 RFC 1987, August 1996. 497 [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching 498 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 499 Switch Management Protocol Specification," Version 2.0, 500 RFC 2397, March 1998. 502 [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual 503 Conventions and OBJECT-IDENTITIES for ATM Management", 504 RFC 2514, February 1999. 506 [RFC2233] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 507 using SMIv2", RFC 2233, November 1997. 509 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement 510 Levels", BCP 14, RFC 2119, Harvard University, March 1997 512 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", 513 BCP 9, RFC 2026, Harvard University, October 1996 515 [24] Worster, et. al., "General Switch Management Protocol", work 516 in progress, October 1999 518 8. Security Considerations 520 Assuming that secure network management (such as SNMP v3) is 521 implemented, the objects represented in this MIB do not pose a threat 522 to the security of the network. 524 9. Authors' Addresses 526 Hans Sjostrand 527 Ericsson 528 Business Unit Datacom Networks and IP Services 529 S-126 25 Stockholm, Sweden 530 Phone: +46 8 719 9960 531 Email: hans.sjostrand@etx.ericsson.se 533 10. Full Copyright Statement 535 Copyright (C) The Internet Society (1999). All Rights Reserved. 537 This document and translations of it may be copied and furnished to 538 others, and derivative works that comment on or otherwise explain it 539 or assist in its implementation may be prepared, copied, published 540 and distributed, in whole or in part, without restriction of any 541 kind, provided that the above copyright notice and this paragraph are 542 included on all such copies and derivative works. However, this 543 document itself may not be modified in any way, such as by removing 544 the copyright notice or references to the Internet Society or other 545 Internet organizations, except as needed for the purpose of 546 developing Internet standards in which case the procedures for 547 copyrights defined in the Internet Standards process must be 548 followed, or as required to translate it into languages other than 549 English. 551 The limited permissions granted above are perpetual and will not be 552 revoked by the Internet Society or its successors or assigns. 554 This document and the information contained herein is provided on an 555 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 556 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 557 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 558 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 559 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.