idnits 2.17.1 draft-ietf-frnetmib-atmiwf-01.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 expiration date. The document expiration date should appear on the first and last 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? == Mismatching filename: the document gives the document name as 'draft-ieft-frnetmib-atmiwf-01', but the file name used is 'draft-ietf-frnetmib-atmiwf-01' == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 42 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 268: '...nIndex value and MUST refer to the sam...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 219 has weird spacing: '...nnIndex when ...' == Line 478 has weird spacing: '...orIndex when...' == Line 1025 has weird spacing: '...for the purpo...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (February 20, 1999) is 9196 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: '5' is defined on line 944, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 948, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 953, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 958, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 966, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '5') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '6') (Obsoleted by RFC 3418) -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 13 errors (**), 0 flaws (~~), 12 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft FR/ATM Service Interworking MIB February 1999 4 Definitions of Managed Objects 5 for Monitoring and Controlling the 6 Frame Relay/ATM PVC Service Interworking Function 8 February 20, 1999 10 draft-ieft-frnetmib-atmiwf-01.txt 12 Kenneth Rehbehn 13 Visual Networks 14 krehbehn@visualnetworks.com 16 Orly Nicklass 17 RAD Data Communications, Ltd. 18 Orly_n@rad.co.il 20 George Mouradian 21 AT&T Labs 22 gvm@att.com 24 Status of this Memo 26 This document is an Internet-Draft and is in full conformance with 27 all provisions of Section 10 of RFC2026. Internet-Drafts are working 28 documents of the Internet Engineering Task Force (IETF), its areas, 29 and its working groups. Note that other groups may also distribute 30 working documents as Internet-Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet- Drafts as reference 35 material or to cite them other than as ``work in progress.'' 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Abstract 45 This memo defines a Management Information Base (MIB) for monitoring 46 and controlling a service interworking function (IWF) for Permanent 47 Virtual Connections (PVC) between Frame Relay and Asynchronous 48 Transfer Mode (ATM) technologies. 50 Copyright Notice 52 Copyright (C) The Internet Society (1999). All Rights Reserved. 54 Table of Contents 56 1 The SNMPv2 Network Management Framework ...................... 4 57 2 Object Definitions ........................................... 5 58 3 Overview ..................................................... 6 59 3.1 Frame Relay/ATM Service Interworking ....................... 6 60 4 Object Definitions ........................................... 7 61 4.1 The FR/ATM PVC Service IWF Connection Group ................ 9 62 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 15 63 5 Frame Relay/ATM PVC Service Interworking TRAP ................ 21 64 6 Conformance Information ...................................... 22 65 6.1 Compliance Statement For Equipment ......................... 22 66 6.2 Compliance Statement For Service (CNM Interface) ........... 24 67 6.3 Units of Conformance ....................................... 26 68 6.3.1 Basic FR/ATM IWF PVC Connection Group .................... 26 69 6.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 26 70 6.3.3 Notification Group ....................................... 27 71 7 Acknowledgments .............................................. 28 72 8 References ................................................... 29 73 9 Security Considerations ...................................... 30 74 10 Authors' Addresses .......................................... 30 75 11 Copyright Section ........................................... 31 77 1. The SNMPv2 Network Management Framework 79 The SNMP Network Management Framework presently consists of three 80 major components. They are: 82 o the SMI, described in RFC 1902 [1] - the mechanisms used for 83 describing and naming objects for the purpose of management. 85 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 86 objects for the Internet suite of protocols. 88 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol 89 for accessing managed objects. 91 The Framework permits new objects to be defined for the 92 purpose of experimentation and evaluation. 94 2. Object Definitions 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. Objects in the MIB are 98 defined using the subset of Abstract Syntax Notation One (ASN.1) 99 defined in the SMI. In particular, each object type is named by an 100 OBJECT IDENTIFIER, an administratively assigned name. The object 101 type together with an object instance serves to uniquely identify a 102 specific instantiation of the object. For human convenience, we 103 often use a textual string, termed the descriptor, to refer to the 104 object type. 106 3. Overview 108 This document defines a Management Information Base (MIB) for 109 monitoring and controlling a service interworking function (IWF) for 110 Permanent Virtual Connections (PVC) between Frame Relay and 111 Asynchronous Transfer Mode (ATM) technologies. The agreements on 112 which this MIB is based were reached jointly by the Frame Relay Forum 113 and the ATM Forum and are documented in the Frame Relay Forum 114 Document FRF.8 [9]. 116 In the future, the MIB defined in this document may be used or 117 extended for service interworking using Switched Virtual Connections. 119 3.1. Frame Relay/ATM Service Interworking 121 Service interworking applies when a Frame Relay service user 122 interworks with an ATM service user, the ATM service user performs no 123 frame relaying service-specific functions, and the frame relay 124 service user performs no ATM service-specific functions. The 125 optional translation of particular higher layer protocols to satisfy 126 the requirements of end-systems may also be implemented. 128 Consult FRF.8 [9] for more details. 130 4. Object Definitions 132 FR-ATM-PVC-SERVICE-INTERWORKING-MIB DEFINITIONS ::= BEGIN 134 IMPORTS 135 MODULE-IDENTITY, OBJECT-TYPE, 136 NOTIFICATION-TYPE, 137 transmission, Integer32, BITS, Counter32 FROM SNMPv2-SMI 139 TEXTUAL-CONVENTION, RowStatus, 140 TimeStamp FROM SNMPv2-TC 142 MODULE-COMPLIANCE, OBJECT-GROUP, 143 NOTIFICATION-GROUP FROM SNMPv2-CONF 145 AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB 147 InterfaceIndex FROM IF-MIB; 149 frAtmIwfMIB MODULE-IDENTITY 150 LAST-UPDATED "9902200000Z" 151 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" 152 CONTACT-INFO 153 "Kenneth Rehbehn 154 Postal: Visual Networks 155 2092 Gaither Road 156 Rockville, MD USA 20850 157 Tel: +1 301 296 2325 158 Fax: +1 301 296 2302 159 E-mail: krehbehn@visualnetworks.com 161 Orly Nicklass 162 Postal: RAD Data Communications Ltd. 163 12 Hanechoshet St. 164 Tel Aviv 69710 165 Israel 166 Tel: +972 (3) 6459588 167 Fax: +972 (3) 6472675 168 E-mail: orly@radmail.rad.co.il 170 George Mouradian 171 Postal: AT&T Labs, Room 1G-325 172 101 Crawfords Corner Road 173 Holmdel, NJ 07733-3030 174 Tel: +1 908 949 7671 175 Email: gvm@att.com" 177 DESCRIPTION 178 "The MIB module for monitoring and controlling the 179 Frame Relay/ATM PVC Service Interworking 180 Function." 181 ::= { transmission xxx } 183 -- 184 -- Object Identifiers 185 -- 186 frAtmIwfMIBObjects OBJECT IDENTIFIER ::= { frAtmIwfMIB 1 } 188 frAtmIwfTraps OBJECT IDENTIFIER ::= { frAtmIwfMIB 2 } 189 frAtmIwfTrapsPrefix OBJECT IDENTIFIER ::= { frAtmIwfTraps 0 } 191 frAtmIwfConformance OBJECT IDENTIFIER ::= { frAtmIwfMIB 3 } 192 frAtmIwfGroups OBJECT IDENTIFIER ::= { frAtmIwfConformance 1 } 193 frAtmIwfCompliances OBJECT IDENTIFIER ::= { frAtmIwfConformance 2 } 195 -- 196 -- Textual Conventions 197 -- 199 Dlci ::= TEXTUAL-CONVENTION 200 STATUS current 201 DESCRIPTION 202 "This data type is a DLCI for a PVC segment end-point." 203 SYNTAX Integer32 205 -- 206 -- The FR/ATM PVC Service IWF Group 207 -- 208 -- The Frame Relay/ATM PVC Service Interworking Function 209 -- Connection Table contains all connections utilizing 210 -- the interworking function. 211 -- 213 frAtmIwfConnIndexNext OBJECT-TYPE 214 SYNTAX Integer32 (0..2147483647) 215 MAX-ACCESS read-only 216 STATUS current 217 DESCRIPTION 218 "This object contains an appropriate value to be 219 used for frAtmIwfConnIndex when creating entries 220 in the frAtmIwfConnectionTable. The value 0 221 indicates that no unassigned entries are 222 available. To obtain the frAtmIwfConnIndexNext 223 value for a new entry, the manager issues a 224 management protocol retrieval operation to obtain 225 the current value of this object. After each 226 retrieval, the agent should modify the value to 227 the next unassigned index." 228 ::= { frAtmIwfMIBObjects 1 } 230 frAtmIwfConnectionTable OBJECT-TYPE 231 SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry 232 MAX-ACCESS not-accessible 233 STATUS current 234 DESCRIPTION 235 "A table in which each row represents a Frame 236 Relay/ATM interworking connection." 237 ::= { frAtmIwfMIBObjects 2 } 239 frAtmIwfConnectionEntry OBJECT-TYPE 240 SYNTAX FrAtmIwfConnectionEntry 241 MAX-ACCESS not-accessible 242 STATUS current 243 DESCRIPTION 244 "The FrAtmIwfConnectionEntry provides an entry for 245 an interworking connection between a Frame Relay 246 PVC and one or more ATM PVCs. A single Frame 247 Relay PVC connected to a single ATM PVC is refered 248 to as a `point-to-point' connection and is 249 represented by a single row in the FR/ATM IWF 250 Connection Table. The case of a single Frame 251 Relay PVC connected to multiple ATM PVCs is 252 refered to as a `point-to-multipoint' connection 253 and is represented by multiple rows in the FR/ATM 254 IWF Connection Table. 256 The object frAtmIwfConnIndex uniquely identifies 257 each point-to-point or point-to-multipoint 258 connection. The manager obtains the 259 frAtmIwfConnIndex value for by reading the 260 frAtmIwfConnIndexNext object. 262 After a frAtmIwfConnIndex is assigned for the 263 connection, the manager creates one or more rows 264 in the Cross Connect Table; one for each cross- 265 connection between the frame relay PVC and an ATM 266 PVC. In the case of `point-to-multipoint' 267 connections, all rows are indexed by the same 268 frAtmIwfConnIndex value and MUST refer to the same 269 frame relay PVC. An entry can be created only 270 when the Frame Relay PVC and at least one ATM PVC 271 exist. 273 A row can be established by one-step set-request 274 with all required parameter values and 275 frAtmIwfConnRowStatus set to createAndGo(4). The 276 Agent should perform all error checking as needed. 277 A pair of cross-connected PVCs, as identified by a 278 particular value of the indexes, is released by 279 setting frAtmIwfConnRowStatus to destroy(6). The 280 Agent may release all associated resources. The 281 manager may remove the related PVCs thereafter." 282 INDEX { frAtmIwfConnIndex, 283 frAtmIwfConnAtmPort, 284 frAtmIwfConnVpi, 285 frAtmIwfConnVci, 286 frAtmIwfConnFrPort, 287 frAtmIwfConnDlci 288 } 289 ::= { frAtmIwfConnectionTable 1 } 291 FrAtmIwfConnectionEntry ::= 292 SEQUENCE { 293 frAtmIwfConnIndex Integer32, 294 frAtmIwfConnAtmPort InterfaceIndex, 295 frAtmIwfConnVpi AtmVpIdentifier, 296 frAtmIwfConnVci AtmVcIdentifier, 297 frAtmIwfConnFrPort InterfaceIndex, 298 frAtmIwfConnDlci Dlci, 299 frAtmIwfConnRowStatus RowStatus, 300 frAtmIwfConnAdminStatus INTEGER, 301 frAtmIwfConnAtm2FrOperStatus INTEGER, 302 frAtmIwfConnAtm2FrLastChange TimeStamp, 303 frAtmIwfConnFr2AtmOperStatus INTEGER, 304 frAtmIwfConnFr2AtmLastChange TimeStamp, 305 frAtmIwfConnUnrecognizedPayloadHeaders Counter32, 306 frAtmIwfConnectionDescriptor Integer32 307 } 309 frAtmIwfConnIndex OBJECT-TYPE 310 SYNTAX Integer32 311 MAX-ACCESS not-accessible 312 STATUS current 313 DESCRIPTION 314 "A unique index to identify this interworking 315 connection." 316 ::= { frAtmIwfConnectionEntry 1 } 318 frAtmIwfConnAtmPort OBJECT-TYPE 319 SYNTAX InterfaceIndex 320 MAX-ACCESS not-accessible 321 STATUS current 322 DESCRIPTION 323 "The index in the ifTable that identifies the ATM 324 port for this interworking connection." 325 ::= { frAtmIwfConnectionEntry 2 } 327 frAtmIwfConnVpi OBJECT-TYPE 328 SYNTAX AtmVpIdentifier 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "The VPI of the ATM PVC end point for this 333 interworking connection." 334 ::= { frAtmIwfConnectionEntry 3 } 336 frAtmIwfConnVci OBJECT-TYPE 337 SYNTAX AtmVcIdentifier 338 MAX-ACCESS not-accessible 339 STATUS current 340 DESCRIPTION 341 "The VCI of the ATM PVC end point for this 342 interworking 343 connection." 344 ::= { frAtmIwfConnectionEntry 4 } 346 frAtmIwfConnFrPort OBJECT-TYPE 347 SYNTAX InterfaceIndex 348 MAX-ACCESS not-accessible 349 STATUS current 350 DESCRIPTION 351 "The index in the ifTable that identifies the 352 Frame Relay port for this interworking 353 connection." 354 ::= { frAtmIwfConnectionEntry 5 } 356 frAtmIwfConnDlci OBJECT-TYPE 357 SYNTAX Dlci 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "The DLCI that identifies the Frame Relay PVC end 362 point for this interworking connection." 363 ::= { frAtmIwfConnectionEntry 6 } 365 frAtmIwfConnRowStatus OBJECT-TYPE 366 SYNTAX RowStatus 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "The status of this table row. This entry is used 371 to create, change or delete a cross-connect. This 372 object can not be set to active(6) unless the 373 frAtmIwfConnAdminStatus exist in this row. To turn 374 on a cross-connect, the frAtmIwfConnAdminStatus is 375 set to up(1)." 376 ::= { frAtmIwfConnectionEntry 7 } 378 frAtmIwfConnAdminStatus OBJECT-TYPE 379 SYNTAX INTEGER { up(1), down(2) } 380 MAX-ACCESS read-create 381 STATUS current 382 DESCRIPTION 383 "The desired operational state for this 384 interworking connection." 386 ::= { frAtmIwfConnectionEntry 8 } 388 frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE 389 SYNTAX INTEGER { up(1), down(2) } 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The current operational state of this 394 interworking connection in the direction from ATM 395 to FR end." 396 ::= { frAtmIwfConnectionEntry 9 } 398 frAtmIwfConnAtm2FrLastChange OBJECT-TYPE 399 SYNTAX TimeStamp 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The value of sysUpTime at the time this 404 interworking connection entered its current 405 operational state in the ATM to FR direction. If 406 the current state was entered prior to the last 407 re-initialization of the local network management 408 subsystem, then this object contains a zero 409 value." 410 ::= { frAtmIwfConnectionEntry 10 } 412 frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE 413 SYNTAX INTEGER { up(1), down(2) } 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The current operational state of this 418 interworking connection in the direction from FR 419 to ATM end." 420 ::= { frAtmIwfConnectionEntry 11 } 422 frAtmIwfConnFr2AtmLastChange OBJECT-TYPE 423 SYNTAX TimeStamp 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The value of sysUpTime at the time this 428 interworking connection entered its current 429 operational state in the FR to ATM direction. If 430 the current state was entered prior to the last 431 re-initialization of the local network management 432 subsystem, then this object contains a zero 433 value." 434 ::= { frAtmIwfConnectionEntry 12 } 436 frAtmIwfConnUnrecognizedPayloadHeaders OBJECT-TYPE 437 SYNTAX Counter32 438 UNITS "Frames" 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "This attribute counts the number of frames 443 discarded by the IWF because, while operating in 444 Translation Mode, the IWF is unable to decode the 445 incoming frame payload header according to the 446 mapping rules. (i.e., payload header not 447 recognized by the IWF). 449 When operating in Transparent Mode, the IWF must 450 return noSuchInstance." 451 REFERENCE 452 "FRF.8 [9], Section 5.3.1" 453 ::= { frAtmIwfConnectionEntry 13 } 455 frAtmIwfConnectionDescriptor OBJECT-TYPE 456 SYNTAX Integer32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The value represents a pointer to the relevant 461 descriptor in the IWF descriptor table." 462 ::= { frAtmIwfConnectionEntry 14 } 464 -- 465 -- The FR/ATM PVC Service IWF Connection Descriptor Group 466 -- 467 -- The Frame Relay/ATM PVC Service Interworking Function 468 -- Connection Descriptor table. A descriptor provides the 469 -- attributes for a type of interworked connection. 470 -- 472 frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE 473 SYNTAX Integer32 (0..2147483647) 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "This object contains an appropriate value to be 478 used for frAtmIwfConnectionDescriptorIndex when 479 creating entries in the 480 frAtmIwfConnectionDescriptorTable. The value 0 481 indicates that no unassigned entries are 482 available. To obtain the 483 frAtmIwfConnectionDescriptorIndexNext value for a 484 new entry, the manager issues a management 485 protocol retrieval operation to obtain the current 486 value of this object. After each retrieval, the 487 agent should modify the value to the next 488 unassigned index." 489 ::= { frAtmIwfMIBObjects 3 } 491 frAtmIwfConnectionDescriptorTable OBJECT-TYPE 492 SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 "A table in which each row represents a descriptor 497 for one type of Frame Relay/ATM interworking 498 connection. A descriptor may be assigned to zero 499 or more FR/ATM PVC service IWF connections." 500 ::= { frAtmIwfMIBObjects 4 } 502 frAtmIwfConnectionDescriptorEntry OBJECT-TYPE 503 SYNTAX FrAtmIwfConnectionDescriptorEntry 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "An entry for a descriptor in an interworking 508 connection between a Frame Relay PVC and an ATM 509 PVC." 510 INDEX { frAtmIwfConnectionDescriptorIndex } 511 ::= { frAtmIwfConnectionDescriptorTable 1 } 513 FrAtmIwfConnectionDescriptorEntry ::= 514 SEQUENCE { 515 frAtmIwfConnectionDescriptorIndex Integer32, 516 frAtmIwfConnDeToClpMappingMode INTEGER, 517 frAtmIwfConnClpToDeMappingMode INTEGER, 518 frAtmIwfConnCongestionMappingMode INTEGER, 519 frAtmIwfConnEncapsulationMappingMode INTEGER, 520 frAtmIwfConnEncapsulationMappings BITS, 521 frAtmIwfConnFragAndReassEnabled INTEGER, 522 frAtmIwfConnArpTranslationEnabled INTEGER 523 } 525 frAtmIwfConnectionDescriptorIndex OBJECT-TYPE 526 SYNTAX Integer32 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "A unique value to identify a descriptor in the 531 table " 532 ::= { frAtmIwfConnectionDescriptorEntry 1 } 534 frAtmIwfConnDeToClpMappingMode OBJECT-TYPE 535 SYNTAX INTEGER { 536 mode1(1), 537 mode2Const0(2), 538 mode2Const1(3) 539 } 540 MAX-ACCESS read-write 541 STATUS current 542 DESCRIPTION 543 "This object describes which mode of translation 544 is in use for loss priority mapping in the Frame 545 Relay to ATM direction. 547 mode1 = the DE field in the Q.922 core frame 548 shall be mapped to the ATM CLP filed 549 of every cell generated by the 550 segmentation process of the AAL5 551 PDU containing the information of 552 that frame. 554 mode2Contst0 = the ATM CLP filed of every cell 555 generated by the segmentation process 556 of the AAL5 PDU containing the 557 information of that frame shall be 558 set to constant 0. 560 mode2Contst1 = the ATM CLP filed of every cell 561 generated by the segmentation process 562 of the AAL5 PDU containing the 563 information of that frame shall be set 564 to constant 1." 565 REFERENCE 566 "FRF.8 [9], Section 4.2.1" 567 DEFVAL { mode1 } 568 ::= { frAtmIwfConnectionDescriptorEntry 2 } 570 frAtmIwfConnClpToDeMappingMode OBJECT-TYPE 571 SYNTAX INTEGER { 572 mode1(1), 573 mode2Const0(2), 574 mode2Const1(3) 575 } 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "This object describes which mode of translation 580 is in use for loss priority mapping in the ATM to 581 Frame Relay direction. 583 mode1 = if one or more cells in a frame has its CLP 584 field set, the DE field of the Q.922 core 585 frame should be set. 587 mode2Const0 = the DE field of the Q.922 core frame should 588 be set to constant 0. 590 mode2Const1 = the DE field of the Q.922 core frame should 591 be set to constant 1." 593 REFERENCE 594 "FRF.8 [9], Section 4.2.2" 595 DEFVAL { mode1 } 596 ::= { frAtmIwfConnectionDescriptorEntry 3 } 598 frAtmIwfConnCongestionMappingMode OBJECT-TYPE 599 SYNTAX INTEGER { 600 mode1(1), 601 mode2(2) 602 } 603 MAX-ACCESS read-write 604 STATUS current 605 DESCRIPTION 606 "This object describes which mode of translation 607 is in use for forward congestion indication 608 mapping in the Frame Relay to ATM direction. 610 mode1 = The FECN field in the Q.922 core frame shall be 611 mapped to the ATM EFCI field of every cell 612 generated by the segmentation process of the 613 AAL5 PDU containing the information of that 614 frame. 616 mode2 = The FECN field in the Q.922 core frame shall not 617 be mapped to the ATM EFCI field of cells 618 generated by the segmentation process of the AAL5 619 PDU containing the information of that frame. 620 The EFCI field is always set to 'congestion not 621 experienced'. 623 In both of the modes above, if there is congestion 624 in the forward direction in the ATM layer within 625 the IWF, then the IWF can set the EFCI field to 626 'congestion experienced'." 627 REFERENCE 628 "FRF.8 [9], Section 4.3.1.1" 629 DEFVAL { mode1 } 630 ::= { frAtmIwfConnectionDescriptorEntry 4 } 632 frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE 633 SYNTAX INTEGER { 634 transparentMode(1), 635 translationMode(2) 636 } 637 MAX-ACCESS read-write 638 STATUS current 639 DESCRIPTION 640 "This object indicates whether the mapping of 641 upper layer protocol encapsulation is enabled on 642 this interworking connection. 644 transparentMode = Forward the encapsulations unaltered. 646 translationMode = Perform mapping between the two 647 encapsulations due to the 648 incompatibilities of the two methods." 650 REFERENCE 651 "FRF.8 [9], Section 5.3" 652 DEFVAL { transparentMode } 653 ::= { frAtmIwfConnectionDescriptorEntry 5 } 655 frAtmIwfConnEncapsulationMappings OBJECT-TYPE 656 SYNTAX BITS { 657 none (0), -- Transparent mode operation 658 bridgedPdus(1), -- PID: 0x00-01,-07,-02 or -08 659 bridged802dot6(2), -- PID: 0x00-0B 660 bPdus(3), -- PID: 0x00-0E or -0F 661 routedIp(4), -- NLPID: OxCC 662 routedOsi(5), -- NLPID: Ox81, 0x82 or 0x83 663 otherRouted(6), -- 664 x25Iso8202(7), -- 665 q933q2931(8) } 666 MAX-ACCESS read-write 667 STATUS current 668 DESCRIPTION 669 "If upper layer protocol encapsulation mapping is 670 enabled on this interworking connection, then this 671 attribute enumerates which of the encapsulation 672 mappings are supported." 673 REFERENCE 674 "FRF.8 [9], Section 5.3.1" 675 DEFVAL { { none } } 676 ::= { frAtmIwfConnectionDescriptorEntry 6 } 678 frAtmIwfConnFragAndReassEnabled OBJECT-TYPE 679 SYNTAX INTEGER { enabled(1), notEnabled(2)} 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The attribute indicates whether fragmentation and 684 reassembly is enabled for this connection." 685 REFERENCE 686 "FRF.8 [9], Section 5.3.1.4" 687 DEFVAL { notEnabled } 688 ::= { frAtmIwfConnectionDescriptorEntry 7 } 690 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE 691 SYNTAX INTEGER { enabled(1), notEnabled(2)} 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "The attribute indicates whether ARP translation 696 is enabled for this connection." 697 REFERENCE 698 "FRF.8 [9], Section 5.4" 699 DEFVAL { notEnabled } 700 ::= { frAtmIwfConnectionDescriptorEntry 8 } 702 -- 703 -- Frame Relay/ATM PVC Service Interworking TRAP 704 -- 706 frAtmIwfConnStatusChange NOTIFICATION-TYPE 707 OBJECTS { frAtmIwfConnIndex, 708 frAtmIwfConnAtmPort, 709 frAtmIwfConnVpi, 710 frAtmIwfConnVci, 711 frAtmIwfConnFrPort, 712 frAtmIwfConnDlci, 713 frAtmIwfConnAdminStatus, 714 frAtmIwfConnAtm2FrOperStatus, 715 frAtmIwfConnFr2AtmOperStatus 716 } 717 STATUS current 718 DESCRIPTION 719 "An indication that the status of this 720 interworking connection has changed." 721 ::= { frAtmIwfTrapsPrefix 1 } 723 -- 724 -- Conformance Information 725 -- 727 -- 728 -- Compliance Statement For Equipment 729 -- 731 frAtmIwfEquipmentCompliance MODULE-COMPLIANCE 732 STATUS current 733 DESCRIPTION 734 "The compliance statement for equipment that 735 implements the FR/ATM Interworking MIB." 737 MODULE -- this module 738 MANDATORY-GROUPS { frAtmIwfBasicGroup, 739 frAtmIwfConnectionDescriptorGroup, 740 frAtmIwfNotificationsGroup } 742 OBJECT frAtmIwfConnDeToClpMappingMode 743 SYNTAX INTEGER { mode1(1) } 744 DESCRIPTION 745 "Only support for Mode 1 is required." 747 OBJECT frAtmIwfConnClpToDeMappingMode 748 SYNTAX INTEGER { mode1(1) } 749 DESCRIPTION 750 "Only support for Mode 1 is required." 752 OBJECT frAtmIwfConnCongestionMappingMode 753 SYNTAX INTEGER { mode1(1) } 754 DESCRIPTION 755 "Only support for Mode 1 is required." 757 OBJECT frAtmIwfConnEncapsulationMappingMode 758 SYNTAX INTEGER { transparentMode(1) } 759 DESCRIPTION 760 "Support for Translation Mode is not required." 762 OBJECT frAtmIwfConnEncapsulationMappings 763 SYNTAX BITS { none(0) } 764 DESCRIPTION 765 "The IWF may provide one, some or none of the 766 encapsulation translations defined in section 767 5.3.1 of FRF.8 [9]." 769 OBJECT frAtmIwfConnFragAndReassEnabled 770 SYNTAX INTEGER { notEnabled(2) } 771 DESCRIPTION 772 "Only support for Mode 1 is required." 774 OBJECT frAtmIwfConnArpTranslationEnabled 775 SYNTAX INTEGER { notEnabled(2) } 776 DESCRIPTION 777 "Support for ARP Translation is not required." 779 ::= { frAtmIwfCompliances 1 } 781 -- 782 -- Compliance Statement For Service (CNM Interface) 783 -- 785 frAtmIwfServiceCompliance MODULE-COMPLIANCE 786 STATUS current 787 DESCRIPTION 788 "The compliance statement for a CNM interface that 789 implements the FR/ATM Interworking MIB." 791 MODULE -- this module 792 MANDATORY-GROUPS { frAtmIwfBasicGroup, 793 frAtmIwfConnectionDescriptorGroup, 794 frAtmIwfNotificationsGroup } 796 -- 797 -- Exceptions for each object type implemented for a 798 -- CNM view of the FR/ATM Interworking MIB 799 -- 800 OBJECT frAtmIwfConnAdminStatus 801 MIN-ACCESS read-only 802 DESCRIPTION 803 "Write access is not required." 805 OBJECT frAtmIwfConnDeToClpMappingMode 806 SYNTAX INTEGER { mode1(1) } 807 MIN-ACCESS read-only 808 DESCRIPTION 809 "Support for Mode 1 is required. Other modes are 810 optional. Write access is not required." 812 OBJECT frAtmIwfConnClpToDeMappingMode 813 SYNTAX INTEGER { mode1(1) } 814 MIN-ACCESS read-only 815 DESCRIPTION 816 "Support for Mode 1 is required. Other modes are 817 optional. Write access is not required." 819 OBJECT frAtmIwfConnCongestionMappingMode 820 SYNTAX INTEGER { mode1(1) } 821 MIN-ACCESS read-only 822 DESCRIPTION 823 "Support for Mode 1 is required. Other modes are 824 optional. Write access is not required." 826 OBJECT frAtmIwfConnEncapsulationMappingMode 827 SYNTAX INTEGER { transparentMode(1) } 828 MIN-ACCESS read-only 829 DESCRIPTION 830 "Support for Transparent Mode is required. 831 Translation Mode is optional. Write access is not 832 required." 834 OBJECT frAtmIwfConnEncapsulationMappings 835 SYNTAX BITS { none(0) } 836 MIN-ACCESS read-only 837 DESCRIPTION 838 "The IWF may provide one, some or none of the 839 encapsulation translations defined in section 840 5.3.1 of FRF.8 [9]. Write access is not required." 842 OBJECT frAtmIwfConnFragAndReassEnabled 843 SYNTAX INTEGER { notEnabled(2) } 844 MIN-ACCESS read-only 845 DESCRIPTION 846 "Support for Fragmentation and Reassembly is not 847 required. Write access is not required." 849 OBJECT frAtmIwfConnArpTranslationEnabled 850 SYNTAX INTEGER { notEnabled(2) } 851 MIN-ACCESS read-only 852 DESCRIPTION 853 "Support for ARP Translation is not required. 854 Write access is not required." 856 OBJECT frAtmIwfConnRowStatus 857 MIN-ACCESS read-only 858 DESCRIPTION 859 "Write access is not required." 861 ::= { frAtmIwfCompliances 2 } 863 -- 864 -- Units of Conformance 865 -- 867 -- 868 -- Basic FR/ATM IWF PVC Connection Group 869 -- 870 frAtmIwfBasicGroup OBJECT-GROUP 871 OBJECTS { frAtmIwfConnIndexNext, 872 frAtmIwfConnAdminStatus, 873 frAtmIwfConnAtm2FrOperStatus, 874 frAtmIwfConnAtm2FrLastChange, 875 frAtmIwfConnFr2AtmOperStatus, 876 frAtmIwfConnFr2AtmLastChange, 877 frAtmIwfConnUnrecognizedPayloadHeaders, 878 frAtmIwfConnectionDescriptor, 879 frAtmIwfConnRowStatus } 880 STATUS current 881 DESCRIPTION 882 "The collection of basic objects for configuration 883 and control of FR/ATM interworking connections." 884 ::= { frAtmIwfGroups 1 } 886 -- 887 -- FR/ATM IWF PVC Connection Descriptor Group 888 -- 890 frAtmIwfConnectionDescriptorGroup OBJECT-GROUP 891 OBJECTS { 892 frAtmIwfConnectionDescriptorIndexNext, 893 frAtmIwfConnDeToClpMappingMode, 894 frAtmIwfConnClpToDeMappingMode, 895 frAtmIwfConnCongestionMappingMode, 896 frAtmIwfConnEncapsulationMappingMode, 897 frAtmIwfConnEncapsulationMappings, 898 frAtmIwfConnUnrecognizedPayloadHeaders, 899 frAtmIwfConnFragAndReassEnabled, 900 frAtmIwfConnArpTranslationEnabled 901 } 902 STATUS current 903 DESCRIPTION 904 "The collection of basic objects for specification 905 of FR/ATM interworking connection descriptors." 906 ::= { frAtmIwfGroups 2 } 908 -- 909 -- Notfication Group 910 -- 912 frAtmIwfNotificationsGroup NOTIFICATION-GROUP 913 NOTIFICATIONS { frAtmIwfConnStatusChange } 914 STATUS current 915 DESCRIPTION 916 "The notification for FR/ATM interworking status 917 change." 918 ::= { frAtmIwfGroups 3 } 919 END 921 7. Acknowledgments 923 This document was produced by the Frame Relay Service MIB Working 924 Group. 926 8. References 928 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 929 S. Waldbusser, "Structure of Management Information for version 2 930 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 931 January 1996. 933 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 934 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 935 RFC 1213, March 1991. 937 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 938 Management Protocol", RFC 1157, May 1990. 940 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 941 S. Waldbusser, "Protocol Operations for version 2 of the Simple 942 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 944 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 945 S. Waldbusser, "Transport Mappings for version 2 of the Simple 946 Network Management Protocol (SNMPv2)", RFC 1906, January 1996. 948 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 949 S. Waldbusser, "Management Information Base for version 2 of the 950 Simple Network Management Protocol (SNMPv2)", RFC 1907, January 951 1996. 953 [7] Information processing systems - Open Systems Interconnection, 954 "Specification of Abstract Syntax Notation One (ASN.1)", 955 International Organization for Standardization, International 956 Standard 8824, December 1987. 958 [8] Information processing systems - Open Systems Interconnection, 959 "Specification of Basic Encoding Rules for Abstract Syntax Notation 960 One (ASN.1)", International Organization for Standardization, 961 International Standard 8825, December 1987. 963 [9] Frame Relay/ATM PVC Service Interworking Implementation Agreement, 964 Frame Relay Forum, Document Number FRF.8, April 14, 1995. 966 [10] Network Working Group, Noto, Spiegel, and Tesink, "Definitions 967 of Textual Conventions and OBJECT-IDENTITIES for ATM Management", 968 RFC 2514, February 1999. 970 9. Security Considerations 972 This MIB adds no security issues that are not raised by SNMP itself. As 973 a Network Management Protocol, SNMP is capable of changing the 974 configuration of a system, of denial of service attacks through 975 requiring the agent to respond to its messages, and displaying values of 976 system counters and configuration settings in the clear where an 977 adversary might read them. This, however, is not in itself a threat: 978 this is the function of the protocol, but could be misused. Such misuse 979 can be avoided or minimized through SNMP Security. 981 10. Authors' Addresses 983 Kenneth Rehbehn 984 Visual Networks 985 2092 Gaither Road 986 Rockville, MD, USA 20850 988 Phone: +1 301 296-2325 990 EMail: krehbehn@visualnetworks.com 992 Orly Nicklass 993 RAD Data Communications, Ltd. 994 12 Hanechoshet St. 995 Tel Aviv 69710 996 Israel 998 Phone: +972 (3) 6459588 1000 E-mail: orly@radmail.rad.co.il 1002 George Mouradian 1003 AT&T Labs, Room 1G-325 1004 101 Crawfords Corner Road 1005 Holmdel, NJ USA 07733 1007 Phone: +1 908 949 7671 1009 EMail: gvm@att.com 1011 11. Copyright Section 1013 Copyright (C) The Internet Society (1999). All Rights 1014 Reserved. 1016 This document and translations of it may be copied and 1017 furnished to others, and derivative works that comment on or 1018 otherwise explain it or assist in its implementation may be 1019 prepared, copied, published and distributed, in whole or in 1020 part, without restriction of any kind, provided that the above 1021 copyright notice and this paragraph are included on all such 1022 copies and derivative works. However, this document itself may 1023 not be modified in any way, such as by removing the copyright 1024 notice or references to the Internet Society or other Internet 1025 organizations, except as needed for the purpose of developing 1026 Internet standards in which case the procedures for copyrights 1027 defined in the Internet Standards process must be followed, or 1028 as required to translate it into languages other than English. 1030 The limited permissions granted above are perpetual and will 1031 not be revoked by the Internet Society or its successors or 1032 assigns. 1034 This document and the information contained herein is provided 1035 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1036 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1037 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1038 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1039 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1040 PARTICULAR PURPOSE.