idnits 2.17.1 draft-ietf-frnetmib-atmiwf-04.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. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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 51 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 47 instances of too long lines in the document, the longest one being 17 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 675 has weird spacing: '...nnIndex when ...' == Line 1052 has weird spacing: '...orIndex when...' == Line 1778 has weird spacing: '...for the purpo...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The exact meaning of the all-uppercase expression 'NOT REQUIRED' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. -- 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 (November 24, 1999) is 8920 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: '18' is defined on line 1667, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '19' -- Possible downref: Non-RFC (?) normative reference: ref. '20' ** Obsolete normative reference: RFC 2233 (ref. '22') (Obsoleted by RFC 2863) Summary: 18 errors (**), 0 flaws (~~), 9 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft FR/ATM Service Interworking MIB November 1999 3 Definitions of Managed Objects 4 for Monitoring and Controlling the 5 Frame Relay/ATM PVC Service Interworking Function 7 November 24, 1999 9 draft-ietf-frnetmib-atmiwf-04.txt 11 Kenneth Rehbehn 12 Visual Networks 13 krehbehn@visualnetworks.com 15 Orly Nicklass 16 RAD Data Communications, Ltd. 17 Orly_n@rad.co.il 19 George Mouradian 20 AT&T Labs 21 gvm@att.com 23 Status of this Memo 25 This document is an Internet-Draft and is in full conformance with 26 all provisions of Section 10 of RFC2026. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, 28 and its working groups. Note that other groups may also distribute 29 working documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference 34 material or to cite them other than as ``work in progress.'' 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 Abstract 44 This memo defines a Management Information Base (MIB) to configure, 45 monitor, and control a service interworking function (IWF) for 46 Permanent Virtual Connections (PVC) between Frame Relay and 47 Asynchronous Transfer Mode (ATM) technologies. 49 Copyright Notice 51 Copyright (C) The Internet Society (1999). All Rights Reserved. 53 Table of Contents 55 1 The SNMP Management Framework ................................ 4 56 2 Conventions .................................................. 5 57 3 Overview ..................................................... 6 58 3.1 Frame Relay/ATM Service Interworking Background ............ 6 59 3.2 Structure of the MIB ....................................... 7 60 3.3 Relationship to Other MIBs ................................. 8 61 3.3.1 Frame Relay Service MIB .................................. 8 62 3.3.2 Frame Relay DTE MIB ...................................... 9 63 3.3.3 ATM MIB .................................................. 9 64 3.3.4 IF MIB ................................................... 9 65 3.4 Point to Multipoint Considerations ......................... 10 66 3.5 Theory of Operation ........................................ 11 67 3.5.1 Creation Process ......................................... 11 68 3.5.2 Destruction Process ...................................... 14 69 3.5.3 Modification Process ..................................... 15 70 4 Object Definitions ........................................... 16 71 4.1 The FR/ATM PVC Service IWF Connection Group ................ 20 72 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 29 73 5 Augmentation of ATM MIB VCL Endpoint Entry (atmVclEntry) ..... 36 74 6 Frame Relay/ATM PVC Service Interworking NOTIFICATION ........ 38 75 7 Conformance Information ...................................... 39 76 7.1 Compliance Statement For Equipment ......................... 39 77 7.2 Compliance Statement For Service (CNM Interface) ........... 41 78 7.3 Units of Conformance ....................................... 43 79 7.3.1 Basic FR/ATM IWF PVC Connection Group .................... 43 80 7.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 43 81 7.3.3 ATM MIB VCL Endpoint Table Augmentation .................. 44 82 7.3.4 Notification Group ....................................... 44 83 8 Acknowledgments .............................................. 45 84 9 References ................................................... 46 85 9 Security Considerations ...................................... 48 86 10 Authors' Addresses .......................................... 49 88 1. The SNMP Management Framework 90 The SNMP Management Framework presently consists of five major 91 components: 93 o An overall architecture, described in RFC 2571 [1]. 95 o Mechanisms for describing and naming objects and events for the 96 purpose of management. The first version of this Structure of 97 Management Information (SMI) is called SMIv1 and described in 98 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The 99 second version, called SMIv2, is described in STD 58, RFC 2578 100 [5], RFC 2579 [6] and RFC 2580 [7]. 102 o Message protocols for transferring management information. The 103 first version of the SNMP message protocol is called SNMPv1 and 104 described in STD 15, RFC 1157 [8]. A second version of the SNMP 105 message protocol, which is not an Internet standards track 106 protocol, is called SNMPv2c and described in RFC 1901 [9] and 107 RFC 1906 [10]. The third version of the message protocol is 108 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 109 RFC 2574 [12]. 111 o Protocol operations for accessing management information. The 112 first set of protocol operations and associated PDU formats is 113 described in STD 15, RFC 1157 [8]. A second set of protocol 114 operations and associated PDU formats is described in RFC 1905 115 [13]. 117 o A set of fundamental applications described in RFC 2573 [14] and 118 the view-based access control mechanism described in RFC 2575 119 [15]. 121 A more detailed introduction to the current SNMP Management Framework 122 can be found in RFC 2570 [16]. 124 Managed objects are accessed via a virtual information store, termed 125 the Management Information Base or MIB. Objects in the MIB are 126 defined using the mechanisms defined in the SMI. 128 This memo specifies a MIB module that is compliant to the SMIv2. A 129 MIB conforming to the SMIv1 can be produced through the appropriate 130 translations. The resulting translated MIB must be semantically 131 equivalent, except where objects or events are omitted because no 132 translation is possible (use of Counter64). Some machine readable 133 information in SMIv2 will be converted into textual descriptions in 134 SMIv1 during the translation process. However, this loss of machine 135 readable information is not considered to change the semantics of the 136 MIB. 138 2. Conventions 140 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 141 SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when 142 they appear in this document, are to be interpreted as described in 143 RFC 2119 [23]. 145 3. Overview 147 This document defines a Management Information Base (MIB) for 148 monitoring and controlling a service interworking function (IWF) for 149 Permanent Virtual Connections (PVC) between Frame Relay and 150 Asynchronous Transfer Mode (ATM) technologies. The agreements on 151 which this MIB is based were reached jointly by the Frame Relay Forum 152 and the ATM Forum and are documented in the Frame Relay Forum 153 Document FRF.8 [17]. 155 3.1. Frame Relay/ATM Service Interworking Background 157 Frame relay to ATM interworking is a function that exchanges Protocol 158 Data Units (PDU) between a frame relay service user and an ATM 159 service user. Two types of interworking functions are specified for 160 frame relay and ATM permanent virtual connection (PVC) service users: 161 network interworking and service interworking. 163 Network interworking provides PDU forwarding between frame relay 164 service users inter-connected by an ATM service. Both endpoints are 165 frame relay PVCs. Frame Relay to ATM PVC Network Interworking is 166 defined in [20]. 168 Service interworking provides PDU forwarding so that the ATM service 169 user performs no frame relaying service-specific functions and the 170 frame relay service user performs no ATM service-specific functions. 171 Optionally, the service IWF translates particular higher layer 172 protocols to satisfy the requirements of end-systems. Frame Relay to 173 ATM PVC Service Interworking is defined in [20]. 175 This MIB describes management objects used to provision, monitor, and 176 control a Frame Relay/ATM PVC Service IWF. 178 FRF.8 [17] does not address point-to-multipoint applications of the 179 IWF. Implementations MAY provide support for point-to-multipoint 180 capability using this MIB. 182 Consult FRF.8 [17] for more details on the operation of a Frame 183 Relay/ATM PVC Service IWF. 185 3.2. Structure of the MIB 187 The Frame Relay/ATM PVC Service IWF managed objects are organized as 188 follows: 190 (1) FR/ATM PVC Service IWF cross-connect table, 192 (2) Connection description table, and 194 (3) Notification object 196 The IWF cross-connect table contains one or more rows for each 197 inter-worked connection. Each inter-worked connection is uniquely 198 identified by the frAtmIwfConnIndex object. In the case of point-to- 199 point, a single row is present. In the case of point-to-multipoint, 200 one row exists for each multipoint destination. Index objects for 201 the ATM port, VPI, VCI, frame relay port, and frame relay DLCI 202 distinguish the constituent rows used in a point-to-multipoint case. 204 Each inter-worked connection has attributes governing behavior of the 205 IWF. These attributes describe how the IWF should transform a PDU 206 during the forwarding process and provide rules for: 208 (1) Mapping the ATM CLP bit to frame relay DE bit 210 (2) Mapping the ATM congestion notification bit to frame relay 211 congestion bits 213 (3) Mapping higher protocol encapsulations between ATM and frame 214 relay 216 (4) Performing fragmentation and reassembly 218 (5) Performing ARP translation between ATM and frame relay 220 Typically, most connections share the same attributes. The attributes 221 are represented in this MIB by the connection description table. Each 222 row of the connection description table contains the attribute 223 settings common to one or more inter-worked connections. One example 224 would be full mapping and translation. All cross-connect table 225 entries that require full mapping and translation services set the 226 frAtmIwfConnectionDescriptor object to the index value for the 227 connection description table row that contains objects set to values 228 that provide full mapping and translation services. 230 A notification object provides cross-connect status change alerts. 232 3.3. Relationship to Other MIBs 234 The Frame Relay/ATM PVC Service IWF MIB describes the cross- 235 connections between frame relay and ATM service users. Each PVC 236 endpoint is provisioned and managed with a technology-specific MIB as 237 described below. 239 Each technology-specific MIB has a table of PVC endpoints (indexed by 240 ifIndex and logical link address such as the DLCI or VPI/VCI). In the 241 absence of interworking, two endpoints are cross-connected via a 242 technology-specific cross connect table (e.g., the 243 atmVcCrossConnectTable in the ATM MIB). However, a connection 244 between a frame relay endpoint and an ATM endpoint requires a cross- 245 connect in the ATM IWF MIB. 247 The following sections describe the relationship between the 248 technology-specific MIBs and the FR/ATM PVC Service IWF MIB. 250 3.3.1. Frame Relay Service MIB 252 Frame relay PVC endpoints are provisioned as rows in the Frame Relay 253 Services MIB [19] endpoint table. 255 Each frame relay PVC endpoint is described in the frPVCEndptTable. A 256 connection between two frame relay endpoints is described by an entry 257 in the frame relay PVC cross-connect table frPVCConnectTable. The 258 frPVCEndptConnectIdentifier object of each endpoint points to the 259 frPVCConnectTable cross-connect table row for the connection. 261 In the case of an inter-worked connection, the 262 frPVCEndptConnectIdentifier object is set to zero. Instead, the 263 frPVCEndptAtmIwfConnIndex object is set to the index of the FR/ATM 264 IWF cross-connect table row. 266 The frame relay PVC cross-connect table (frPVCConnectTable) does not 267 contain an entry for the FR/ATM inter-worked connection. 269 Note that the frPVCEndptConnectIdentifier and 270 frPVCEndptAtmIwfConnIndex objects are set by the system as a side- 271 effect of cross-connect establishment. Consequently, these objects 272 are read-only. 274 3.3.2. Frame Relay DTE MIB 276 The Frame Relay DTE MIB described in [19] has no relevance to the 277 FR/ATM PVC Service IWF MIB. 279 3.3.3. ATM MIB 281 ATM PVC endpoints are provisioned as rows in the ATM MIB [21] virtual 282 connection link table. 284 Each ATM connection endpoint is described in the atmVclTable. A 285 connection between two ATM endpoints is described by an entry in the 286 ATM VCL cross-connect table atmVcCrossConnectTable. The 287 atmVclCrossConnectIdentifier object of each endpoint points to the 288 atmVcCrossConnectTable row for the connection. 290 In the case of an inter-worked connection, the 291 atmVclCrossConnectIdentifier object is set to zero. Instead, the 292 frAtmIwfVclCrossConnectIdentifier object in the frAtmIwfVclEntry is 293 set to the index of the applicable FR/ATM IWF cross-connect table 294 row. 296 Note that the frAtmIwfVclCrossConnectIdentifier object is defined not 297 in the ATM MIB but in Section 5 of this MIB. Specifically, the 298 object is defined as a column object in a table that AUGMENTs the ATM 299 MIB VCL table. 301 The ATM VCL cross-connect table (atmVcCrossConnectTable) does not 302 contain an entry for the inter-worked connection. 304 Note that the atmVclCrossConnectIdentifier and 305 frAtmIwfVclCrossConnectIdentifier objects are set by the system as a 306 side-effect of cross-connect establishment. Consequently, these 307 objects are read-only. 309 3.3.4. IF MIB 311 The ifIndex defined in the IF MIB [22] identifies the specific frame 312 relay and ATM endpoint interfaces. The values frAtmIwfConnAtmPort 313 and frAtmIwfConnFrPort is used in this MIB as a component in the 314 index list for the frAtmIwfConnectionTable rows. 316 3.4. Point to Multipoint Considerations 318 This MIB supports IWF implementations providing point-to-multipoint 319 functionality. All rows of the cross-connect table indexed by the 320 same frAtmIwfConnIndex MUST utilize the same 321 frAtmIwfConnectionDescriptor value. 323 A group of cross-connect table entries indexed by the same 324 frAtmIwfConnIndex value MUST agree on which service the multipoint 325 operation is offered. Two cases are possible: 327 (1) Many frame relay PVCs cross-connected to one ATM PVC, or 329 (2) One frame relay PVC cross-connected to many ATM PVCs 331 3.5. Theory of Operation 333 3.5.1. Creation Process 335 Multiple steps are required to create a frame relay to ATM cross- 336 connection. First, rows must be created in the following tables: 338 (1) The Frame Relay Service MIB frPVCEndptTable 340 (2) The ATM MIB atmVclTable 342 (3) The FR/ATM Service IWF MIB frAtmIwfConnectionDescriptorTable 344 (4) The FR/ATM Service IWF MIB frAtmIwfConnectionTable 346 Second, the newly created rows are cross-linked. 348 Finally, the administrative and operational status objects are set to 349 'up'. 351 A step-by-step example is provided to illustrate the creation 352 process. In this example, the term "Manager" refers to a network 353 management system that issues SNMP protocol actions to an "Agent". 354 The agent is integrated with the system that implements the frame 355 relay to ATM service IWF. In this example, the following cross- 356 connection is created: 357 +-------------------------------------+ 358 +---------+ | FR/ATM PVC Service IWF | 359 | Frame | | ------------------------------ | +-----------+ 360 | Relay | +---------> frAtmIwfConnIndex K <---------+ | ATM | 361 |Endpoint | | | V | | | Endpoint | 362 | ------- | | | | | | | --------- | 363 | DLCI X | | | +------------+ | | |VPI.VCI Q.R| 364 | on |<-+ | | | +->| on | 365 |ifIndex Y| | V | | ifIndex S | 366 +---------+ | frAtmIwfConnectionDescriptorIndex L | +-----------+ 367 +-------------------------------------+ 369 Step 1 - Create the frame relay PVC endpoint 371 a) Manager requests creation of a new row in the frPVCEndptTable 373 b) Agent receives management request to create a row in 374 frPVCEndptTable for the frame relay side 376 c) A new row is created in frPVCEndptTable as follows: 378 - frPVCEndptConnectIdentifier initialized to zero 380 - frPVCEndptAtmIwfConnIndex initialized to zero 382 - remaining row objects initialized as needed for DLCI X 383 on ifIndex Y 385 Step 2 - Create the ATM PVC endpoint 387 a) Agent receives management request to create a row in atmVclTable 388 for the ATM side 390 b) A new row is created in atmVclTable and frAtmIwfVclTable (the 391 AUGMENT to the atmVclTable) as follows: 393 - atmVclCrossConnectIdentifier initialized to zero 395 - frAtmIwfVclCrossConnectIdentifier initialized to zero 397 - atmVclConnKind initialized to pvc(1) 399 - remaining row objects initialized as needed for VPI.VCI 400 Q.R on ifIndex S 402 Step 3 - Create the FR/ATM connection descriptor 404 a) If an existing connection descriptor is appropriate for the 405 new connection, go to Step 4 using the selected connection 406 descriptor index value L 408 b) Manager request a new connection descriptor index value by 409 reading frAtmIwfConnectionDescriptorIndexNext from the agent 411 c) Agent receives GET request for 412 frAtmIwfConnectionDescriptorIndexNext and responds with the 413 next available value L 415 d) Manager requests a new connection descriptor row entry using 416 the value L as the index 418 e) Agent receives SET request to create the 419 frAtmIwfConnectionDescriptorTable row entry causes the system 420 to create a row in the table. 422 Step 4 - Create the FR/ATM cross-connect 424 a) Manager requests a new cross-connect index value by reading 425 frAtmIwfConnIndexNext from the agent 427 b) Agent receives GET request for frAtmIwfConnIndexNext 428 and responds with the next available value K 430 c) Manager requests a new cross-connect row entry using the value 431 K as the index 433 d) Agent receives SET request to create the frAtmIwfConnectionTable 434 row entry (note: the frame relay and ATM PVC endpoints MUST exist 435 and be specified as part of the index fields for the 436 row 'K.S.Q.R.Y.X') 438 e) System creates a row in frAtmIwfConnectionTable for the following 439 indices: 441 - frAtmIwfConnIndex of K 443 - frAtmIwfConnAtmPort of S 445 - frAtmIwfConnVpi of Q 447 - frAtmIwfConnVci of R 449 - frAtmIwfConnFrPort of Y 451 - frAtmIwfConnDlci of X 453 - frAtmIwfConnectionDescriptor of L 455 Step 5 - The system sets the frame relay PVC endpoint and ATM VCL 456 endpoint to point to the FR/ATM cross-connect row (as a side-effect 457 of Step 4). 459 a) System sets frPVCEndptAtmIwfConnIndex to K 461 b) System sets frAtmIwfVclCrossConnectIdentifier to K 462 Step 6 - Manager signals activation by issuing a SET for the 463 frAtmIwfConnAdminStatus object using the value of 'up' 465 Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus and 466 executes internal system mechanisms to activate each PVC segment and 467 the IWF cross-connect. The successful activation permits the agent to 468 respond with 'active' when a GET request is received for the 469 following fields: 471 - frAtmIwfConnAtm2FrOperStatus 473 - frAtmIwfConnFr2AtmOperStatus 475 - atmVclOperStatus (Note: there is no comparable FRS MIB object) 477 3.5.2. Destruction Process 479 Destruction of the frame relay to ATM cross-connection is initiated 480 by the network management system. The agent's processing of the 481 request stimulates implementation-specific system clean-up actions. 482 Following removal of the row in the cross-connection table, the 483 frAtmIwfVclCrossConnectIdentifier in the frAtmIwfVclTable (AUGMENT of 484 the ATM MIB endpoint table) and frPVCEndptAtmIwfConnIndex in the 485 Frame Relay Service MIB endpoint table are both re-initialized to 486 zero. 488 A step-by-step example is provided to illustrate the destruction 489 process. 491 Step 1 - Manager requests destruction of an existing row in the 492 frAtmIwfConnectionTable by setting frAtmIwfConnRowStatus to 493 destroy(6) 495 Step 2 - Agent receives the SET request and performs implementation- 496 specific system clean-up actions for the cross-connection row 498 Step 3 - System updates the relevant cross connect information for 499 the frame relay PVC endpoint by setting frPVCEndptAtmIwfConnIndex to 500 0 501 Step 4 - System updates the relevant cross connect information for 502 the ATM PVC endpoint as follows: 504 a) System sets frAtmIwfVclCrossConnectIdentifier to 0 506 b) System sets atmVclOperStatus to 'down' (Note: there is no 507 comparable FRS MIB object) 509 Following the destruction of the FR/ATM cross-connection entry, the 510 manager MAY set the frPVCConnectRowStatus and/or atmVclRowStatus to 511 destroy(6) the associated endpoint entries. 513 3.5.3. Modification Process 515 At the discretion of the agent, a FR/ATM cross-connect may be 516 reconfigured by adding and/or deleting leafs to/from the IWF topology 517 as per the FR/ATM IWF cross-connect creation/destruction procedures. 518 Reconfiguration of traffic/service category parameter values requires 519 release of the FR/ATM IWF cross-connect before those parameter values 520 may be changed for individual frame relay or ATM endpoint segments. 522 4. Object Definitions 524 Managed objects are accessed via a virtual information store, termed 525 the Management Information Base or MIB. Objects in the MIB are 526 defined using the subset of Abstract Syntax Notation One (ASN.1) 527 defined in the SMI. In particular, each object type is named by an 528 OBJECT IDENTIFIER, an administratively assigned name. The object 529 type together with an object instance serves to uniquely identify a 530 specific instantiation of the object. For human convenience, we 531 often use a textual string, termed the descriptor, to refer to the 532 object type. 534 FR-ATM-PVC-SERVICE-IWF-MIB-EXP DEFINITIONS ::= BEGIN 536 IMPORTS 537 MODULE-IDENTITY, OBJECT-TYPE, 538 NOTIFICATION-TYPE, 539 experimental, Integer32, BITS, Counter32 FROM SNMPv2-SMI 541 TEXTUAL-CONVENTION, RowStatus, 542 TimeStamp FROM SNMPv2-TC 544 MODULE-COMPLIANCE, OBJECT-GROUP, 545 NOTIFICATION-GROUP FROM SNMPv2-CONF 547 AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB 549 atmVclEntry FROM ATM-MIB 551 InterfaceIndex FROM IF-MIB; 553 frAtmIwfMIB MODULE-IDENTITY 554 LAST-UPDATED "9911240000Z" 555 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working 556 Group" 557 CONTACT-INFO 558 "Kenneth Rehbehn 559 Postal: Visual Networks 560 2092 Gaither Road 561 Rockville, MD USA 20850 562 Tel: +1 301 296 2325 563 Fax: +1 301 296 2302 564 E-mail: krehbehn@visualnetworks.com 566 Orly Nicklass 567 Postal: RAD Data Communications Ltd. 568 12 Hanechoshet St. 569 Tel Aviv 69710 570 Israel 571 Tel: +972 (3) 6459588 572 Fax: +972 (3) 6472675 573 E-mail: orly@radmail.rad.co.il 575 George Mouradian 576 Postal: AT&T Labs, Room 1G-325 577 101 Crawfords Corner Road 578 Holmdel, NJ 07733-3030 579 Tel: +1 908 949 7671 580 Email: gvm@att.com" 582 DESCRIPTION 583 "The MIB module for monitoring and controlling the 584 Frame Relay/ATM PVC Service Interworking 585 Function." 587 -- 588 -- Revision History 589 -- 590 REVISION "9911240000Z" 591 DESCRIPTION 592 "Published as draft-ieft-frnetmib-atmiwf-04 593 o Redesigned linkage to ATM MIB using AUGMENTS 594 to VCL table" 596 REVISION "9910050000Z" 597 DESCRIPTION 598 "Published as draft-ieft-frnetmib-atmiwf-03 599 o Removed PDU translation error group 600 o State that Pt-to-MP is a MAY 601 o Provide translationModeAll 602 o Added oversized frame count 603 o Come to closure on cross-connect strategy 604 o Name change to FR-ATM-PVC-SERVICE-IWF-MIB-EXP" 606 REVISION "9906180000Z" 607 DESCRIPTION 608 "Published as draft-ieft-frnetmib-atmiwf-02 609 o Added new PDU translation error group 610 o Clarified theory of operation and relationship 611 to the ATM and Frame Relay Service MIBs 613 o Update MIB boilerplate to conform to the 614 Operations and Management Area requirements 615 for MIBs" 617 REVISION "9902200000Z" 618 DESCRIPTION 619 "Published as draft-ieft-frnetmib-atmiwf-01 620 o Isolated connection description objects 621 in frAtmIwfConnectionDescriptorTable 622 o Improved text for a number of objects 623 o Added OperStatus objects to Notification 624 for both frame and ATM sides 625 o Set OID values 626 o Clean smicng compile" 628 REVISION "9611250000Z" 629 DESCRIPTION 630 "Published as draft-ieft-frnetmib-atmiwf-00" 631 ::= { experimental 97 } 633 -- 634 -- Object Identifiers 635 -- 636 frAtmIwfMIBObjects OBJECT IDENTIFIER 637 ::= { frAtmIwfMIB 1 } 639 frAtmIwfTraps OBJECT IDENTIFIER 640 ::= { frAtmIwfMIB 2 } 641 frAtmIwfTrapsPrefix OBJECT IDENTIFIER 642 ::= { frAtmIwfTraps 0 } 644 frAtmIwfConformance OBJECT IDENTIFIER 645 ::= { frAtmIwfMIB 3 } 646 frAtmIwfGroups OBJECT IDENTIFIER 647 ::= { frAtmIwfConformance 1 } 648 frAtmIwfCompliances OBJECT IDENTIFIER 649 ::= { frAtmIwfConformance 2 } 651 -- 652 -- Textual Conventions 653 -- 655 Dlci ::= TEXTUAL-CONVENTION 656 STATUS current 657 DESCRIPTION 658 "This data type is a DLCI for a PVC segment end-point." 659 SYNTAX Integer32 (16..4194303) 661 -- 662 -- The FR/ATM PVC Service IWF Group 663 -- 664 -- The Frame Relay/ATM PVC Service Interworking Function 665 -- Connection Table contains all connections utilizing 666 -- the interworking function. 667 -- 669 frAtmIwfConnIndexNext OBJECT-TYPE 670 SYNTAX Integer32 (0..2147483647) 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "This object contains an appropriate value to be 675 used for frAtmIwfConnIndex when creating entries 676 in the frAtmIwfConnectionTable. The value 0 677 indicates that no unassigned entries are 678 available. To obtain the frAtmIwfConnIndexNext 679 value for a new entry, the manager issues a 680 management protocol retrieval operation to obtain 681 the current value of this object. After each 682 retrieval, the agent should modify the value to 683 the next unassigned index." 684 ::= { frAtmIwfMIBObjects 1 } 686 frAtmIwfConnectionTable OBJECT-TYPE 687 SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "A table in which each row represents a Frame 692 Relay/ATM interworking connection." 693 ::= { frAtmIwfMIBObjects 2 } 695 frAtmIwfConnectionEntry OBJECT-TYPE 696 SYNTAX FrAtmIwfConnectionEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The FrAtmIwfConnectionEntry provides an entry for 701 an interworking connection between a frame relay 702 PVC and one or more ATM PVCs, or an ATM PVC and 703 one or more frame relay PVCs. A single frame 704 relay PVC connected to a single ATM PVC is 705 referred to as a `point-to-point' connection and 706 is represented by a single row in the FR/ATM IWF 707 Connection Table. The case of a single frame 708 relay PVC connected to multiple ATM PVCs (or 709 single ATM PVC connected to multiple frame relay 710 PVCs) is referred to as a `point-to-multipoint' 711 connection and is represented by multiple rows in 712 the FR/ATM IWF Connection Table. 714 The object frAtmIwfConnIndex uniquely identifies 715 each point-to-point or point-to-multipoint 716 connection. The manager obtains the 717 frAtmIwfConnIndex value by reading the 718 frAtmIwfConnIndexNext object. 720 After a frAtmIwfConnIndex is assigned for the 721 connection, the manager creates one or more rows 722 in the Cross Connect Table; one for each cross- 723 connection between the frame relay PVC and an ATM 724 PVC. In the case of `point-to-multipoint' 725 connections, all rows are indexed by the same 726 frAtmIwfConnIndex value and MUST refer to the same 727 frame relay PVC or ATM PVC respectively. An entry 728 can be created only when at least one pair of 729 frame relay and ATM PVCs exist. 731 A row can be established by one-step set-request 732 with all required parameter values and 733 frAtmIwfConnRowStatus set to createAndGo(4). The 734 Agent should perform all error checking as needed. 735 A pair of cross-connected PVCs, as identified by a 736 particular value of the indexes, is released by 737 setting frAtmIwfConnRowStatus to destroy(6). The 738 Agent may release all associated resources. The 739 manager may remove the related PVCs thereafter. 740 Indexes are persistent across reboots of the 741 system." 742 INDEX { frAtmIwfConnIndex, 743 frAtmIwfConnAtmPort, 744 frAtmIwfConnVpi, 745 frAtmIwfConnVci, 746 frAtmIwfConnFrPort, 747 frAtmIwfConnDlci 748 } 749 ::= { frAtmIwfConnectionTable 1 } 751 FrAtmIwfConnectionEntry ::= 752 SEQUENCE { 753 frAtmIwfConnIndex Integer32, 754 frAtmIwfConnAtmPort InterfaceIndex, 755 frAtmIwfConnVpi AtmVpIdentifier, 756 frAtmIwfConnVci AtmVcIdentifier, 757 frAtmIwfConnFrPort InterfaceIndex, 758 frAtmIwfConnDlci Dlci, 759 frAtmIwfConnRowStatus RowStatus, 760 frAtmIwfConnAdminStatus INTEGER, 761 frAtmIwfConnAtm2FrOperStatus INTEGER, 762 frAtmIwfConnAtm2FrLastChange TimeStamp, 763 frAtmIwfConnFr2AtmOperStatus INTEGER, 764 frAtmIwfConnFr2AtmLastChange TimeStamp, 765 frAtmIwfConnectionDescriptor Integer32, 766 frAtmIwfConnFailedFrameTranslate Counter32, 767 frAtmIwfConnOverSizedFrames Counter32, 768 frAtmIwfConnFailedAal5PduTranslate Counter32, 769 frAtmIwfConnOverSizedSDUs Counter32, 770 frAtmIwfConnCrcErrors Counter32, 771 frAtmIwfConnSarTimeOuts Counter32 772 } 774 frAtmIwfConnIndex OBJECT-TYPE 775 SYNTAX Integer32 (1..2147483647) 776 MAX-ACCESS not-accessible 777 STATUS current 778 DESCRIPTION 779 "A unique index to identify this interworking 780 connection." 781 ::= { frAtmIwfConnectionEntry 1 } 783 frAtmIwfConnAtmPort OBJECT-TYPE 784 SYNTAX InterfaceIndex 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "The index in the ifTable that identifies the ATM 789 port for this interworking connection." 790 ::= { frAtmIwfConnectionEntry 2 } 792 frAtmIwfConnVpi OBJECT-TYPE 793 SYNTAX AtmVpIdentifier 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "The VPI of the ATM PVC end point for this 798 interworking connection." 799 ::= { frAtmIwfConnectionEntry 3 } 801 frAtmIwfConnVci OBJECT-TYPE 802 SYNTAX AtmVcIdentifier 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "The VCI of the ATM PVC end point for this 807 interworking 808 connection." 809 ::= { frAtmIwfConnectionEntry 4 } 811 frAtmIwfConnFrPort OBJECT-TYPE 812 SYNTAX InterfaceIndex 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "The index in the ifTable that identifies the 817 frame relay port for this interworking 818 connection." 819 ::= { frAtmIwfConnectionEntry 5 } 821 frAtmIwfConnDlci OBJECT-TYPE 822 SYNTAX Dlci 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "The DLCI that identifies the frame relay PVC end 827 point for this interworking connection." 828 ::= { frAtmIwfConnectionEntry 6 } 830 frAtmIwfConnRowStatus OBJECT-TYPE 831 SYNTAX RowStatus 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "The table row may be created with 'createAndWait' 836 or 'createAndGo'. 838 To activate a connection entry, a valid connection 839 descriptor MUST be established in the 840 frAtmIwfConnectionDescriptor object and the 841 AdminStatus of the corresponding endpoints MUST be 842 'up' & 'active'. 844 This object is set to 'destroy' to delete the 845 table row. To deactivate a connection entry, the 846 AdminStatus of the corresponding endpoints MUST be 847 'down' & 'inactive'. Otherwise, 'destroy' 848 operation MUST fail (error code 849 'inconsistentValue')." 850 ::= { frAtmIwfConnectionEntry 7 } 852 frAtmIwfConnAdminStatus OBJECT-TYPE 853 SYNTAX INTEGER { up(1), down(2) } 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "The desired operational state for this 858 interworking connection." 859 ::= { frAtmIwfConnectionEntry 8 } 861 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE 862 SYNTAX INTEGER { up(1), down(2) } 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The current operational state of this 867 interworking connection in the direction from ATM 868 to FR end." 869 ::= { frAtmIwfConnectionEntry 9 } 871 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE 872 SYNTAX TimeStamp 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "The value of sysUpTime at the time this 877 interworking connection entered its current 878 operational state in the ATM to FR direction. If 879 the current state was entered prior to the last 880 re-initialization of the local network management 881 subsystem, then this object contains a zero 882 value." 883 ::= { frAtmIwfConnectionEntry 10 } 885 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE 886 SYNTAX INTEGER { up(1), down(2) } 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The current operational state of this 891 interworking connection in the direction from FR 892 to ATM end." 893 ::= { frAtmIwfConnectionEntry 11 } 895 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE 896 SYNTAX TimeStamp 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The value of sysUpTime at the time this 901 interworking connection entered its current 902 operational state in the FR to ATM direction. If 903 the current state was entered prior to the last 904 re-initialization of the local network management 905 subsystem, then this object contains a zero 906 value." 907 ::= { frAtmIwfConnectionEntry 12 } 909 frAtmIwfConnectionDescriptor OBJECT-TYPE 910 SYNTAX Integer32 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "The value represents a pointer to the relevant 915 descriptor in the IWF descriptor table. An 916 attempt to set this value to an inactive or non- 917 existant row in the Connection Descriptor Table 918 MUST fail (error code 'inconsistentValue')." 919 ::= { frAtmIwfConnectionEntry 13 } 921 frAtmIwfConnFailedFrameTranslate OBJECT-TYPE 922 SYNTAX Counter32 923 UNITS "Frames" 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION 927 "This object counts the number of frames discarded 928 by the IWF because, while operating in Translation 929 Mode, the IWF is unable to decode the incoming 930 frame payload header according to the mapping 931 rules. (i.e., payload header not recognized by the 932 IWF). 934 Frame relay frames are received in the frame relay 935 to ATM direction of the PVC. 937 When operating in Transparent Mode, the IWF MUST 938 return noSuchInstance." 939 REFERENCE 940 "FRF.8 [17], Section 5.3.1" 941 ::= { frAtmIwfConnectionEntry 14 } 943 frAtmIwfConnOverSizedFrames OBJECT-TYPE 944 SYNTAX Counter32 945 UNITS "Frames" 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "Count of frames discarded by the IWF because the 950 frame is too large to be processed by the AAL5 951 segmentation procedure. Specifically, the frame 952 does not conform to the size specified in the 953 atmVccAal5CpcsTransmitSduSize object associated 954 with the atmVclEntry at the ATM endpoint. 956 Frame relay frames are received in the frame relay 957 to ATM direction of the PVC." 958 REFERENCE 959 "ATM MIB [21], atmVclTable 960 FRF.8 [17], 5.3.1.4" 961 ::= { frAtmIwfConnectionEntry 15 } 963 frAtmIwfConnFailedAal5PduTranslate OBJECT-TYPE 964 SYNTAX Counter32 965 UNITS "PDUs" 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "This attribute counts the number of AAL5 PDUs 970 discarded by the IWF because, while operating in 971 Translation Mode, the IWF is unable to decode the 972 incoming AAL5 PDU payload header according to the 973 mapping rules. (i.e., payload header not 974 recognized by the IWF). 976 AAL5 PDUs are received in the ATM to frame relay 977 direction of the PVC. 979 When operating in Transparent Mode, the IWF MUST 980 return noSuchInstance." 981 REFERENCE 982 "FRF.8 [17], Section 5.3.1" 983 ::= { frAtmIwfConnectionEntry 16 } 985 frAtmIwfConnOverSizedSDUs OBJECT-TYPE 986 SYNTAX Counter32 987 UNITS "SDUs" 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "Count of AAL5 SDUs discarded by the IWF because 992 the SDU is too large to be forwarded on the frame 993 relay segment of the connection. Specifically, 994 the frame does not conform to the size specified 995 in the frLportFragSize object of the FRS MIB [19]. 997 AAL5 PDUs are received in the ATM to frame relay 998 direction of the PVC." 999 REFERENCE 1000 "FRS MIB [19], frLportTable 1001 FRF.8 [17], 5.3.1.4" 1002 ::= { frAtmIwfConnectionEntry 17 } 1004 frAtmIwfConnCrcErrors OBJECT-TYPE 1005 SYNTAX Counter32 1006 UNITS "PDUs" 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The number of AAL5 CPCS PDUs received with CRC-32 1011 errors on this AAL5 VCC at the IWF. 1013 AAL5 PDUs are received in the ATM to frame relay 1014 direction of the PVC." 1015 REFERENCE 1016 "ATM MIB [21], atmVclTable" 1017 ::= { frAtmIwfConnectionEntry 18 } 1019 frAtmIwfConnSarTimeOuts OBJECT-TYPE 1020 SYNTAX Counter32 1021 UNITS "PDUs" 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The number of partially re-assembled AAL5 CPCS 1026 PDUs which were discarded on this AAL5 VCC at the 1027 IWF because they were not fully re-assembled 1028 within the required time period. If the re- 1029 assembly timer is not supported, then this object 1030 contains a zero value. 1032 AAL5 PDUs are received in the ATM to frame relay 1033 direction of the PVC." 1034 REFERENCE 1035 "ATM MIB [21], atmVclTable" 1036 ::= { frAtmIwfConnectionEntry 19 } 1038 -- 1039 -- The FR/ATM PVC Service IWF Connection Descriptor Group 1040 -- 1041 -- The Frame Relay/ATM PVC Service Interworking Function 1042 -- Connection Descriptor table. A descriptor provides the 1043 -- attributes for a type of interworked connection. 1044 -- 1046 frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE 1047 SYNTAX Integer32 (0..2147483647) 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "This object contains an appropriate value to be 1052 used for frAtmIwfConnectionDescriptorIndex when 1053 creating entries in the 1054 frAtmIwfConnectionDescriptorTable. The value 0 1055 indicates that no unassigned entries are 1056 available. To obtain the 1057 frAtmIwfConnectionDescriptorIndexNext value for a 1058 new entry, the manager issues a management 1059 protocol retrieval operation to obtain the current 1060 value of this object. After each retrieval, the 1061 agent should modify the value to the next 1062 unassigned index." 1063 ::= { frAtmIwfMIBObjects 3 } 1065 frAtmIwfConnectionDescriptorTable OBJECT-TYPE 1066 SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "A table in which each row represents a descriptor 1071 for one type of Frame Relay/ATM interworking 1072 connection. A descriptor may be assigned to zero 1073 or more FR/ATM PVC service IWF connections." 1074 ::= { frAtmIwfMIBObjects 4 } 1076 frAtmIwfConnectionDescriptorEntry OBJECT-TYPE 1077 SYNTAX FrAtmIwfConnectionDescriptorEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "An entry for a descriptor in an interworking 1082 connection between a frame relay PVC and an ATM 1083 PVC." 1084 INDEX { frAtmIwfConnectionDescriptorIndex } 1085 ::= { frAtmIwfConnectionDescriptorTable 1 } 1087 FrAtmIwfConnectionDescriptorEntry ::= 1088 SEQUENCE { 1089 frAtmIwfConnectionDescriptorIndex Integer32, 1090 frAtmIwfConnDescriptorRowStatus RowStatus, 1091 frAtmIwfConnDeToClpMappingMode INTEGER, 1092 frAtmIwfConnClpToDeMappingMode INTEGER, 1093 frAtmIwfConnCongestionMappingMode INTEGER, 1094 frAtmIwfConnEncapsulationMappingMode INTEGER, 1095 frAtmIwfConnEncapsulationMappings BITS, 1096 frAtmIwfConnFragAndReassEnabled INTEGER, 1097 frAtmIwfConnArpTranslationEnabled INTEGER 1098 } 1100 frAtmIwfConnectionDescriptorIndex OBJECT-TYPE 1101 SYNTAX Integer32 (1..2147483647) 1102 MAX-ACCESS not-accessible 1103 STATUS current 1104 DESCRIPTION 1105 "A unique value to identify a descriptor in the 1106 table " 1107 ::= { frAtmIwfConnectionDescriptorEntry 1 } 1109 frAtmIwfConnDescriptorRowStatus OBJECT-TYPE 1110 SYNTAX RowStatus 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "The status of this table row. This object is 1115 used to create or delete an entry in the 1116 descriptor table. 1118 Creation of the row requires a row index (see 1119 frAtmIwfConnectionDescriptorIndexNext). If not 1120 explicitly set or in existence, all other columns 1121 of the row will be created and initialized to the 1122 default value. During creation, this object MAY 1123 be set to The object MUST contain the value 1124 'active' before any connection table entry 1125 references the row. 1127 To destroy a row in this table, this object is set 1128 to the 'destroy' action. Row destruction MUST 1129 fail (error code 'inconsistentValue') if any 1130 connection references the row." 1131 ::= { frAtmIwfConnectionDescriptorEntry 2 } 1133 frAtmIwfConnDeToClpMappingMode OBJECT-TYPE 1134 SYNTAX INTEGER { 1135 mode1(1), 1136 mode2Const0(2), 1137 mode2Const1(3) 1138 } 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "This object describes which mode of translation 1143 is in use for loss priority mapping in the frame 1144 relay to ATM direction. 1146 mode1 = the DE field in the Q.922 core frame 1147 shall be mapped to the ATM CLP filed 1148 of every cell generated by the 1149 segmentation process of the AAL5 1150 PDU containing the information of 1151 that frame. 1153 mode2Contst0 = the ATM CLP filed of every cell 1154 generated by the segmentation process 1155 of the AAL5 PDU containing the 1156 information of that frame shall be 1157 set to constant 0. 1159 mode2Contst1 = the ATM CLP filed of every cell 1160 generated by the segmentation process 1161 of the AAL5 PDU containing the 1162 information of that frame shall be set 1163 to constant 1." 1164 REFERENCE 1165 "FRF.8 [17], Section 4.2.1" 1166 DEFVAL { mode1 } 1167 ::= { frAtmIwfConnectionDescriptorEntry 3 } 1169 frAtmIwfConnClpToDeMappingMode OBJECT-TYPE 1170 SYNTAX INTEGER { 1171 mode1(1), 1172 mode2Const0(2), 1173 mode2Const1(3) 1174 } 1175 MAX-ACCESS read-create 1176 STATUS current 1177 DESCRIPTION 1178 "This object describes which mode of translation 1179 is in use for loss priority mapping in the ATM to 1180 frame relay direction. 1182 mode1 = if one or more cells in a frame has its CLP 1183 field set, the DE field of the Q.922 core 1184 frame should be set. 1186 mode2Const0 = the DE field of the Q.922 core frame should 1187 be set to constant 0. 1189 mode2Const1 = the DE field of the Q.922 core frame should 1190 be set to constant 1." 1192 REFERENCE 1193 "FRF.8 [17], Section 4.2.2" 1194 DEFVAL { mode1 } 1195 ::= { frAtmIwfConnectionDescriptorEntry 4 } 1197 frAtmIwfConnCongestionMappingMode OBJECT-TYPE 1198 SYNTAX INTEGER { 1199 mode1(1), 1200 mode2(2) 1201 } 1202 MAX-ACCESS read-create 1203 STATUS current 1204 DESCRIPTION 1205 "This object describes which mode of translation 1206 is in use for forward congestion indication 1207 mapping in the frame relay to ATM direction. 1209 mode1 = The FECN field in the Q.922 core frame shall be 1210 mapped to the ATM EFCI field of every cell 1211 generated by the segmentation process of the 1212 AAL5 PDU containing the information of that 1213 frame. 1215 mode2 = The FECN field in the Q.922 core frame shall not 1216 be mapped to the ATM EFCI field of cells 1217 generated by the segmentation process of the AAL5 1218 PDU containing the information of that frame. 1219 The EFCI field is always set to 'congestion not 1220 experienced'. 1222 In both of the modes above, if there is congestion 1223 in the forward direction in the ATM layer within 1224 the IWF, then the IWF can set the EFCI field to 1225 'congestion experienced'." 1226 REFERENCE 1227 "FRF.8 [17], Section 4.3.1.1" 1228 DEFVAL { mode1 } 1229 ::= { frAtmIwfConnectionDescriptorEntry 5 } 1231 frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE 1232 SYNTAX INTEGER { 1233 transparentMode(1), 1234 translationMode(2), 1235 translationModeAll(3) 1236 } 1237 MAX-ACCESS read-create 1238 STATUS current 1239 DESCRIPTION 1240 "This object indicates whether the mapping of 1241 upper layer protocol encapsulation is enabled on 1242 this interworking connection. 1244 transparentMode = Forward the encapsulations unaltered. 1246 translationMode = Perform mapping between the two 1247 encapsulations due to the 1248 incompatibilities of the two methods. 1249 Mapping is provided for a subset of the 1250 potential encapsulations as itemized in 1251 frAtmIwfConnEncapsulationMappings. 1253 translationModeAll = Perform mapping between the two 1254 encapsulations due to the 1255 incompatibilities of the two methods. 1256 All encapsulations are translated." 1257 REFERENCE 1258 "FRF.8 [17], Section 5.3" 1259 DEFVAL { transparentMode } 1260 ::= { frAtmIwfConnectionDescriptorEntry 6 } 1262 frAtmIwfConnEncapsulationMappings OBJECT-TYPE 1263 SYNTAX BITS { 1264 none (0), -- Transparent mode operation 1265 bridgedPdus(1), -- PID: 0x00-01,-07,-02 or -08 1266 bridged802dot6(2), -- PID: 0x00-0B 1267 bPdus(3), -- PID: 0x00-0E or -0F 1268 routedIp(4), -- NLPID: OxCC 1269 routedOsi(5), -- NLPID: Ox81, 0x82 or 0x83 1270 otherRouted(6), -- 1271 x25Iso8202(7), -- 1272 q933q2931(8) } 1273 MAX-ACCESS read-create 1274 STATUS current 1275 DESCRIPTION 1276 "If upper layer protocol encapsulation mapping is 1277 enabled on this interworking connection, then this 1278 attribute enumerates which of the encapsulation 1279 mappings are supported." 1280 REFERENCE 1281 "FRF.8 [17], Section 5.3.1" 1282 DEFVAL { { none } } 1283 ::= { frAtmIwfConnectionDescriptorEntry 7 } 1285 frAtmIwfConnFragAndReassEnabled OBJECT-TYPE 1286 SYNTAX INTEGER { enabled(1), disabled(2)} 1287 MAX-ACCESS read-create 1288 STATUS current 1289 DESCRIPTION 1290 "The attribute indicates whether fragmentation and 1291 reassembly is enabled for this connection." 1292 REFERENCE 1293 "FRF.8 [17], Section 5.3.1.4" 1294 DEFVAL { disabled } 1295 ::= { frAtmIwfConnectionDescriptorEntry 8 } 1297 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE 1298 SYNTAX INTEGER { enabled(1), disabled(2)} 1299 MAX-ACCESS read-create 1300 STATUS current 1301 DESCRIPTION 1302 "The attribute indicates whether ARP translation 1303 is enabled for this connection." 1304 REFERENCE 1305 "FRF.8 [17], Section 5.4" 1306 DEFVAL { disabled } 1307 ::= { frAtmIwfConnectionDescriptorEntry 9 } 1309 -- 1310 -- Augmentation of ATM MIB VCL Endpoint Table (atmVclTable) 1311 -- 1312 frAtmIwfVclTable OBJECT-TYPE 1313 SYNTAX SEQUENCE OF FrAtmIwfVclEntry 1314 MAX-ACCESS not-accessible 1315 STATUS current 1316 DESCRIPTION 1317 "The FR/ATM IWF VCL Table augments the ATM MIB VCL Endpoint table." 1318 ::= { frAtmIwfMIBObjects 5 } 1320 frAtmIwfVclEntry OBJECT-TYPE 1321 SYNTAX FrAtmIwfVclEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "Entries in this table are created only by the agent. One 1326 entry exists for each ATM VCL managed by the agent." 1327 AUGMENTS { atmVclEntry } 1328 ::= { frAtmIwfVclTable 1 } 1330 FrAtmIwfVclEntry ::= SEQUENCE { 1331 frAtmIwfVclCrossConnectIdentifier Integer32 1332 } 1334 frAtmIwfVclCrossConnectIdentifier OBJECT-TYPE 1335 SYNTAX Integer32 (1..2147483647) 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "This object contains the index value of the 1340 FR/ATM cross-connect table entry used to link the 1341 ATM VCL with a frame relay PVC. 1343 Each row of the atmVclTable that is not cross- 1344 connected with a frame relay PVC MUST return the 1345 value zero when this object is read. 1347 In the case of (frame relay) point to (ATM) 1348 multipoint, multiple ATM VCLs will have the same 1349 value of this object, and all their cross- 1350 connections are identified by entries that are 1351 indexed by the same value of 1352 frAtmIwfVclCrossConnectIdentifier in the 1353 frAtmIwfConnectionTable of this MIB module. 1355 The value of this object is initialized by the 1356 agent after the associated entries in the 1357 frAtmIwfConnectionTable have been created." 1358 ::= { frAtmIwfVclEntry 1 } 1360 -- 1361 -- Frame Relay/ATM PVC Service Interworking NOTIFICATION 1362 -- 1364 frAtmIwfConnStatusChange NOTIFICATION-TYPE 1365 OBJECTS { frAtmIwfConnAdminStatus, 1366 frAtmIwfConnAtm2FrOperStatus, 1367 frAtmIwfConnFr2AtmOperStatus 1368 } 1369 STATUS current 1370 DESCRIPTION 1371 "An indication that the status of this 1372 interworking connection has changed." 1373 ::= { frAtmIwfTrapsPrefix 1 } 1375 -- 1376 -- Conformance Information 1377 -- 1379 -- 1380 -- Compliance Statement For Equipment 1381 -- 1383 frAtmIwfEquipmentCompliance MODULE-COMPLIANCE 1384 STATUS current 1385 DESCRIPTION 1386 "The compliance statement for equipment that 1387 implements the FR/ATM Interworking MIB." 1389 MODULE -- this module 1390 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1391 frAtmIwfConnectionDescriptorGroup, 1392 frAtmIwfAtmVclTableAugmentGroup, 1393 frAtmIwfNotificationsGroup } 1395 OBJECT frAtmIwfConnDeToClpMappingMode 1396 SYNTAX INTEGER { mode1(1) } 1397 DESCRIPTION 1398 "Only support for Mode 1 is REQUIRED." 1400 OBJECT frAtmIwfConnClpToDeMappingMode 1401 SYNTAX INTEGER { mode1(1) } 1402 DESCRIPTION 1403 "Only support for Mode 1 is REQUIRED." 1405 OBJECT frAtmIwfConnCongestionMappingMode 1406 SYNTAX INTEGER { mode1(1) } 1407 DESCRIPTION 1408 "Only support for Mode 1 is REQUIRED." 1410 OBJECT frAtmIwfConnEncapsulationMappingMode 1411 SYNTAX INTEGER { transparentMode(1) } 1412 DESCRIPTION 1413 "Support for Translation Mode is OPTIONAL." 1415 OBJECT frAtmIwfConnEncapsulationMappings 1416 SYNTAX BITS { none(0) } 1417 DESCRIPTION 1418 "The IWF may provide one, some or none of the 1419 encapsulation translations defined in section 1420 5.3.1 of FRF.8 [17]." 1422 OBJECT frAtmIwfConnFragAndReassEnabled 1423 SYNTAX INTEGER { disabled(2) } 1424 DESCRIPTION 1425 "Only support for Mode 1 is REQUIRED." 1427 OBJECT frAtmIwfConnArpTranslationEnabled 1428 SYNTAX INTEGER { disabled(2) } 1429 DESCRIPTION 1430 "Support for ARP Translation is NOT REQUIRED." 1432 ::= { frAtmIwfCompliances 1 } 1434 -- 1435 -- Compliance Statement For Service (CNM Interface) 1436 -- 1438 frAtmIwfServiceCompliance MODULE-COMPLIANCE 1439 STATUS current 1440 DESCRIPTION 1441 "The compliance statement for a CNM interface that 1442 implements the FR/ATM Interworking MIB." 1444 MODULE -- this module 1445 MANDATORY-GROUPS { frAtmIwfBasicGroup, 1446 frAtmIwfConnectionDescriptorGroup, 1447 frAtmIwfAtmVclTableAugmentGroup, 1448 frAtmIwfNotificationsGroup } 1450 -- 1451 -- Exceptions for each object type implemented for a 1452 -- CNM view of the FR/ATM Interworking MIB 1453 -- 1454 OBJECT frAtmIwfConnAdminStatus 1455 MIN-ACCESS read-only 1456 DESCRIPTION 1457 "Write access is not REQUIRED." 1459 OBJECT frAtmIwfConnDeToClpMappingMode 1460 SYNTAX INTEGER { mode1(1) } 1461 MIN-ACCESS read-only 1462 DESCRIPTION 1463 "Support for Mode 1 is REQUIRED. Other modes are 1464 OPTIONAL. Write access is NOT REQUIRED." 1466 OBJECT frAtmIwfConnClpToDeMappingMode 1467 SYNTAX INTEGER { mode1(1) } 1468 MIN-ACCESS read-only 1469 DESCRIPTION 1470 "Support for Mode 1 is REQUIRED. Other modes are 1471 OPTIONAL. Write access is NOT REQUIRED." 1473 OBJECT frAtmIwfConnCongestionMappingMode 1474 SYNTAX INTEGER { mode1(1) } 1475 MIN-ACCESS read-only 1476 DESCRIPTION 1477 "Support for Mode 1 is REQUIRED. Other modes are 1478 OPTIONAL. Write access is NOT REQUIRED." 1480 OBJECT frAtmIwfConnEncapsulationMappingMode 1481 SYNTAX INTEGER { transparentMode(1) } 1482 MIN-ACCESS read-only 1483 DESCRIPTION 1484 "Support for Transparent Mode is REQUIRED. 1485 Translation Mode is OPTIONAL. Write access is not 1486 required." 1488 OBJECT frAtmIwfConnEncapsulationMappings 1489 SYNTAX BITS { none(0) } 1490 MIN-ACCESS read-only 1491 DESCRIPTION 1492 "The IWF may provide one, some or none of the 1493 encapsulation translations defined in section 1494 5.3.1 of FRF.8 [17]. Write access is not 1495 required." 1497 OBJECT frAtmIwfConnFragAndReassEnabled 1498 SYNTAX INTEGER { disabled(2) } 1499 MIN-ACCESS read-only 1500 DESCRIPTION 1501 "Support for Fragmentation and Reassembly is NOT 1502 REQUIRED. Write access is not required." 1504 OBJECT frAtmIwfConnArpTranslationEnabled 1505 SYNTAX INTEGER { disabled(2) } 1506 MIN-ACCESS read-only 1507 DESCRIPTION 1508 "Support for ARP Translation is not required. 1509 Write access is not required." 1511 OBJECT frAtmIwfConnRowStatus 1512 MIN-ACCESS read-only 1513 DESCRIPTION 1514 "Write access is not required." 1516 ::= { frAtmIwfCompliances 2 } 1518 -- 1519 -- Units of Conformance 1520 -- 1522 -- 1523 -- Basic FR/ATM IWF PVC Connection Group 1524 -- 1525 frAtmIwfBasicGroup OBJECT-GROUP 1526 OBJECTS { frAtmIwfConnIndexNext, 1527 frAtmIwfConnAdminStatus, 1528 frAtmIwfConnAtm2FrOperStatus, 1529 frAtmIwfConnAtm2FrLastChange, 1530 frAtmIwfConnFr2AtmOperStatus, 1531 frAtmIwfConnFr2AtmLastChange, 1532 frAtmIwfConnectionDescriptor, 1533 frAtmIwfConnFailedFrameTranslate, 1534 frAtmIwfConnOverSizedFrames, 1535 frAtmIwfConnFailedAal5PduTranslate, 1536 frAtmIwfConnOverSizedSDUs, 1537 frAtmIwfConnCrcErrors, 1538 frAtmIwfConnSarTimeOuts, 1539 frAtmIwfConnRowStatus } 1540 STATUS current 1541 DESCRIPTION 1542 "The collection of basic objects for configuration 1543 and control of FR/ATM interworking connections." 1544 ::= { frAtmIwfGroups 1 } 1546 -- 1547 -- FR/ATM IWF PVC Connection Descriptor Group 1548 -- 1550 frAtmIwfConnectionDescriptorGroup OBJECT-GROUP 1551 OBJECTS { 1552 frAtmIwfConnectionDescriptorIndexNext, 1553 frAtmIwfConnDeToClpMappingMode, 1554 frAtmIwfConnClpToDeMappingMode, 1555 frAtmIwfConnCongestionMappingMode, 1556 frAtmIwfConnEncapsulationMappingMode, 1557 frAtmIwfConnEncapsulationMappings, 1558 frAtmIwfConnFragAndReassEnabled, 1559 frAtmIwfConnArpTranslationEnabled, 1560 frAtmIwfConnDescriptorRowStatus 1561 } 1562 STATUS current 1563 DESCRIPTION 1564 "The collection of basic objects for specification 1565 of FR/ATM interworking connection descriptors." 1566 ::= { frAtmIwfGroups 2 } 1568 -- 1569 -- ATM MIB VCL Endpoint Table Augmentation Group 1570 -- 1572 frAtmIwfAtmVclTableAugmentGroup OBJECT-GROUP 1573 OBJECTS { 1574 frAtmIwfVclCrossConnectIdentifier 1575 } 1576 STATUS current 1577 DESCRIPTION 1578 "The ATM MIB VCL Endpoint Table AUGMENT object 1579 contained in the FR/ATM PVC Service Interworking 1580 MIB." 1581 ::= { frAtmIwfGroups 3 } 1583 -- 1584 -- Notification Group 1585 -- 1587 frAtmIwfNotificationsGroup NOTIFICATION-GROUP 1588 NOTIFICATIONS { frAtmIwfConnStatusChange } 1589 STATUS current 1590 DESCRIPTION 1591 "The notification for FR/ATM interworking status 1592 change." 1593 ::= { frAtmIwfGroups 4 } 1594 END 1596 8. Acknowledgments 1598 This document was produced by the Frame Relay Service MIB Working 1599 Group. 1601 The Editors thank Bert Wijnen, Kaj Tesink, and Keith McCloghrie for 1602 providing many helpful comments and suggestions. 1604 9. References 1606 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1607 Describing SNMP Management Frameworks", RFC 2571, April 1999 1609 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1610 Management Information for TCP/IP-based Internets", STD 16, RFC 1611 1155, May 1990 1613 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1614 1212, March 1991 1616 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1617 RFC 1215, March 1991 1619 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1620 and S. Waldbusser, "Structure of Management Information Version 2 1621 (SMIv2)", STD 58, RFC 2578, April 1999 1623 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1624 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1625 2579, April 1999 1627 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1628 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1629 2580, April 1999 1631 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1632 Management Protocol", STD 15, RFC 1157, May 1990. 1634 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1635 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1637 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1638 Mappings for Version 2 of the Simple Network Management Protocol 1639 (SNMPv2)", RFC 1906, January 1996. 1641 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1642 Processing and Dispatching for the Simple Network Management 1643 Protocol (SNMP)", RFC 2572, April 1999 1645 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1646 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1647 2574, April 1999 1649 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1650 Operations for Version 2 of the Simple Network Management Protocol 1651 (SNMPv2)", RFC 1905, January 1996. 1653 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1654 2573, April 1999 1656 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1657 Control Model (VACM) for the Simple Network Management Protocol 1658 (SNMP)", RFC 2575, April 1999 1660 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1661 Version 3 of the Internet-standard Network Management Framework", 1662 RFC 2570, April 1999 1664 [17] Frame Relay/ATM PVC Service Interworking Implementation Agreement, 1665 Frame Relay Forum, Document Number FRF.8, April 14, 1995. 1667 [18] Network Working Group, Noto, Spiegel, and Tesink, "Definitions of 1668 Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 1669 2514, February 1999. 1671 [19] Network Working Group, Rehbehn, K., and D. Fowler, "Definitions of 1672 Managed Objects for Frame Relay Service", RFC xxFRSMIBv2xxx, 1673 October 1999. 1675 [20] Frame Relay/ATM PVC Network Interworking Implementation Agreement, 1676 Frame Relay Forum, Document Number FRF.5, December 20, 1994. 1678 [21] Network Working Group, K. Tesink, "Definitions of Managed Objects 1679 for ATM Management", RFC 2515, February 1999. 1681 [22] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 1682 2233, Cisco Systems, FTP Software, November 1997. 1684 [23] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1685 Levels", BCP 14, RFC 2119, March 1997. 1687 9. Security Considerations 1689 There are a number of management objects defined in this MIB that 1690 have a MAX-ACCESS clause of read-write and/or read-create. Such 1691 objects may be considered sensitive or vulnerable in some network 1692 environments. The support for SET operations in a non-secure 1693 environment without proper protection can have a negative effect on 1694 network operations. 1696 No managed objects in this MIB contain sensitive information. 1698 SNMPv1 by itself is not a secure environment. Even if the network 1699 itself is secure (for example by using IPSec), even then, there is no 1700 control as to who on the secure network is allowed to access and 1701 GET/SET (read/change/create/delete) the objects in this MIB. 1703 It is recommended that the implementers consider the security 1704 features as provided by the SNMPv3 framework. Specifically, the use 1705 of the User-based Security Model RFC 2574 [12] and the View-based 1706 Access Control Model RFC 2575 [15] is recommended. 1708 It is then a customer/user responsibility to ensure that the SNMP 1709 entity giving access to an instance of this MIB, is properly 1710 configured to give access to the objects only to those principals 1711 (users) that have legitimate rights to indeed GET or SET 1712 (change/create/delete) them. 1714 10. Authors' Addresses 1716 Kenneth Rehbehn 1717 Visual Networks 1718 2092 Gaither Road 1719 Rockville, MD, USA 20850 1721 Phone: +1 301 296-2325 1723 EMail: krehbehn@visualnetworks.com 1725 Orly Nicklass 1726 RAD Data Communications, Ltd. 1727 12 Hanechoshet St. 1728 Tel Aviv 69710 1729 Israel 1731 Phone: +972 (3) 6459588 1733 E-mail: orly@radmail.rad.co.il 1735 George Mouradian 1736 AT&T Labs, Room 1G-325 1737 101 Crawfords Corner Road 1738 Holmdel, NJ USA 07733 1740 Phone: +1 908 949 7671 1742 EMail: gvm@att.com 1744 Intellectual Property Rights 1746 The IETF takes no position regarding the validity or scope of any 1747 intellectual property or other rights that might be claimed to 1748 pertain to the implementation or use of the technology described in 1749 this document or the extent to which any license under such rights 1750 might or might not be available; neither does it represent that it 1751 has made any effort to identify any such rights. Information on the 1752 IETF's procedures with respect to rights in standards-track and 1753 standards-related documentation can be found in BCP-11. Copies of 1754 claims of rights made available for publication and any assurances of 1755 licenses to be made available, or the result of an attempt made to 1756 obtain a general license or permission for the use of such 1757 proprietary rights by implementors or users of this specification can 1758 be obtained from the IETF Secretariat. 1760 The IETF invites any interested party to bring to its attention any 1761 copyrights, patents or patent applications, or other proprietary 1762 rights which may cover technology that may be required to practice 1763 this standard. Please address the information to the IETF Executive 1764 Director. 1766 Full Copyright Statement 1768 Copyright (C) The Internet Society (1999). All Rights Reserved. 1770 This document and translations of it may be copied and furnished to 1771 others, and derivative works that comment on or otherwise explain it 1772 or assist in its implementation may be prepared, copied, published 1773 and distributed, in whole or in part, without restriction of any 1774 kind, provided that the above copyright notice and this paragraph are 1775 included on all such copies and derivative works. However, this 1776 document itself may not be modified in any way, such as by removing 1777 the copyright notice or references to the Internet Society or other 1778 Internet organizations, except as needed for the purpose of 1779 developing Internet standards in which case the procedures for 1780 copyrights defined in the Internet Standards process must be 1781 followed, or as required to translate it into languages other than 1782 English. 1784 The limited permissions granted above are perpetual and will not be 1785 revoked by the Internet Society or its successors or assigns. 1787 This document and the information contained herein is provided on an 1788 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1789 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1790 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1791 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1792 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.