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