idnits 2.17.1 draft-ietf-ancp-mib-an-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance 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 IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (January 9, 2014) is 3753 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. De Cnodder 3 Internet-Draft Alcatel-Lucent 4 Intended status: Standards Track M. Morgenstern 5 Expires: July 13, 2014 ECI Telecom Ltd. 6 January 9, 2014 8 Access Node Control Protocol (ANCP) MIB module for Access Nodes 9 draft-ietf-ancp-mib-an-12.txt 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols. In particular it defines 15 objects for managing access nodes that are using the Access Node 16 Control Protocol (ANCP). 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on July 13, 2014. 35 Copyright Notice 37 Copyright (c) 2014 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. The Internet-Standard Management Framework . . . . . . . . . 2 54 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 57 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 3 58 5.2. The ANCP MIB module Subtree . . . . . . . . . . . . . . . 3 59 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 3 60 5.4. The Table Structures . . . . . . . . . . . . . . . . . . 4 61 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 62 6.1. Relationship to the Interfaces Group MIB module . . . . . 5 63 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . 5 64 7. ANCP MIB Definitions for the Access Node . . . . . . . . . . 6 65 8. Security Considerations . . . . . . . . . . . . . . . . . . . 31 66 9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 37 67 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 68 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 69 11.1. Normative References . . . . . . . . . . . . . . . . . . 38 70 11.2. Informative References . . . . . . . . . . . . . . . . . 38 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 73 1. Introduction 75 This memo defines a portion of the Management Information Base (MIB) 76 for use with network management protocols. In particular it defines 77 objects for managing access nodes as described in [RFC5851] that are 78 using the Access Node Control Protocol defined in [RFC6320]. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies MIB 91 modules that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 3. Conventions 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119]. 101 4. Overview 103 In [RFC5851], the framework for the Access Node Control Protocol 104 (ANCP) is described. It defines 2 network entities, the Access Node 105 (AN) and the Network Access Server (NAS), between which ANCP sessions 106 are established. The detailed protocol specification of ANCP is 107 described in [RFC6320]. This document specifies a MIB module for an 108 AN that supports ANCP, and a MIB module that defines textual 109 conventions. 111 This document specifies MIB modules for an AN as defined in 112 [RFC6320], and any protocol extensions not defined in [RFC6320] are 113 not covered by this document. Also MIB modules for a NAS are not 114 covered by this document. 116 5. Structure of the MIB Module 118 5.1. Textual Conventions 120 New textual conventions, AncpSessionCapabilities, AncpVersion, 121 AncpName, and AncpPartitionId are defined in a seperate MIB module in 122 this document. These textual conventions are used for the 123 convenience of humans reading the MIB. 125 5.2. The ANCP MIB module Subtree 127 ANCP-TC-MIB is the first MIB module defined in this document, and it 128 is put under mib-2. Also the second MIB module defined in this 129 document, ANCP-AN-MIB is put under mib-2. 131 5.3. The Notifications Subtree 133 Notifications are defined to inform the management station about 134 state changes of ANCP sessions, whenever an ANCP session changes 135 state. Two notifications are defined for this purpose. The 136 notification ancpAnSessionUp is to inform the management station when 137 the session comes up, and the notification ancpAnSessionDown is to 138 inform when the ANCP session is down again after it was up before. 140 Attributes are introduced to enable and disable the generation of 141 these notifications per ANCP session. No other special measures for 142 congestion avoidance for the notifications are needed because the 143 number of ANCP sessions in an access node is typically small. In 144 addition, establishing an ANCP session and tearing down it again, 145 takes some time such that for a particular ANCP session, not many 146 notifications in a short time period can be generated. 148 5.4. The Table Structures 150 The ANCP MIB module for the AN has 3 tables. The tables are the 151 following: 153 o ancpAnSessionConfigTable 155 This table is used to configure ANCP sessions at the AN towards a 156 specific NAS. The NAS is identified by a number of attributes in 157 this table (ancpAnSessionConfigNasIpAddressType and 158 ancpAnSessionConfigNasIpAddress). The other attributes in this 159 table can be used to configure properties that are specific for 160 that particular ANCP session. The interface to which the ANCP 161 session is bound is also configured in this table. This interface 162 can be an IP interface, an ATM PVC, a VLAN (or VLAN stack), or any 163 other interface defined in IF-MIB. 165 o ancpAnCurrentSessionTable 167 This table shows the operational state of a particular ANCP 168 session, as well as the actual values of various parameters 169 associated with it. The table also provides statistical 170 information collected for each particular ANCP session. Each 171 session configured in ancpAnSessionConfigTable has a corresponding 172 row in ancpAnCurrentSessionTable. When a session is configured or 173 deleted in the ancpAnSessionConfigTable, then the corresponding 174 row of that session in the ancpAnCurrentSessionTable is, 175 respectively, automatically created or deleted. 177 o ancpAnInterfaceConfigTable 179 This table is used to assign interfaces to particular partitions 180 if partitions are being used as indicated by the scalar 181 ancpAnPartitionsUsed. When partitions are used, a row in this 182 table is created automatically when a user facing interface for 183 which the system supports ANCP is created in the ifTable of the 184 IF-MIB [RFC2863]. 186 Four groups are defined: 188 o ancpAnConfigGroup 190 This group contains all objects of the ancpAnSessionConfigTable in 191 which the ANCP sessions are configured in the access node. 193 o ancpAnCurrentGroup 195 This group contains all objects of the 196 ancpAnCurrentSessionTable where the operational state and other 197 information of the ANCP sessions are shown. 199 o ancpAnInterfaceGroup 201 This group contains all objects to configure interfaces to be used 202 by ANCP. Assigning interfaces to particular partitions is part of 203 this group in case partitions are used. 205 o ancpAnNotificationsGroup 207 This group contains the notifications that indicate state changes 208 of ANCP sessions. 210 6. Relationship to Other MIB Modules 212 6.1. Relationship to the Interfaces Group MIB module 214 There is a dependency between the ANCP MIB module and the Interfaces 215 Group MIB (IF-MIB) defined in [RFC2863]. The ifIndex defined in the 216 ifTable of IF-MIB is used as the index of the 217 ancpAnInterfaceConfigTable defined in the ANCP MIB module for access 218 nodes. Each time that an entry is created in the ifTable for which 219 the system supports ANCP (e.g., in a DSLAM this is typically for each 220 DSL line), a row is created automatically in the 221 ancpAnInterfaceConfigTable if partitions are being used. 223 6.2. MIB modules required for IMPORTS 225 The ANCP TC MIB module requires the following MIB modules for 226 IMPORTS: 228 o SNMPv2-SMI defined in [RFC2578] 230 o SNMPv2-TC defined in [RFC2579] 232 The ANCP MIB module for access nodes requires thefollowing MIB 233 modules for IMPORTS: 235 o SNMPv2-SMI defined in [RFC2578] 237 o RMON2-MIB defined in [RFC4502] 239 o IF-MIB defined in [RFC2863] 241 o INET-ADDRESS-MIB defined in [RFC4001] 243 o SNMPv2-CONF defined in [RFC2580] 245 o SNMPv2-TC defined in [RFC2579] 247 o Q-BRIDGE-MIB defined in [RFC4363] 249 o ANCP-TC-MIB defined in this document 251 7. ANCP MIB Definitions for the Access Node 253 ANCP-TC-MIB DEFINITIONS ::= BEGIN 255 IMPORTS 256 MODULE-IDENTITY, mib-2, Unsigned32 257 FROM SNMPv2-SMI -- RFC2578 259 TEXTUAL-CONVENTION 260 FROM SNMPv2-TC; -- RFC2579 262 ancpTcMIB MODULE-IDENTITY 263 LAST-UPDATED "201306240000Z" -- 24 June 2013 264 ORGANIZATION "IETF ANCP Working Group" 265 CONTACT-INFO 266 " Editors: 268 Stefaan De Cnodder 269 Alcatel-Lucent 270 Postal: Copernicuslaan 50 271 B-2018 Antwerp 272 Belgium 273 EMail: stefaan.de_cnodder@alcatel-lucent.com 274 Phone: +32 3 240 85 15 275 Moti Morgenstern 276 ECI Telecom Ltd. 277 Postal: 30 Hasivim St. 278 Petach Tikva 4959388, 279 Israel 280 Email: moti.morgenstern@ecitele.com 281 Phone: +972 3 926 6258 282 " 283 DESCRIPTION 284 "This MIB module provides Textual Conventions to be 285 used by MIB modules for AN and NAS that are implementing 286 the Access Node Control Protocol (ANCP). 288 Copyright (C) The IETF Trust (2008). The initial version 289 of this MIB module was published in RFC yyyy; for full 290 legal notices see the RFC itself." 291 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 292 REVISION "201306240000Z" -- 24 June 2013 293 DESCRIPTION "Initial version as published in RFC yyyy." 294 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 295 ::= { mib-2 xxx } 296 -- The value xxx to be assigned by IANA. 298 -- 299 -- Textual Conventions 300 -- 302 AncpSessionCapabilities ::= TEXTUAL-CONVENTION 303 STATUS current 304 DESCRIPTION 305 "ANCP capabilities supported by the AN. 306 The following capabilities are available: 307 dslTopologyDiscovery (1) - Access Topology Discovery 308 dslLineConfiguration (2) - Line Configuration 309 dslLineTesting (4) - Layer 2 OAM 310 A bit set means the associated capability is supported." 311 SYNTAX BITS { 312 dslTopologyDiscovery (1), 313 dslLineConfiguration (2), 314 dslLineTesting (4) 315 } 317 AncpVersion ::= TEXTUAL-CONVENTION 318 STATUS current 319 DESCRIPTION 320 "The version numbers defined for the ANCP protocol. 321 The version numbers used are defined in the 322 specifications of the respective protocol. 324 Version 50 is defined in [RFC6320]. 325 Other numbers may be defined for other versions of the 326 ANCP protocol." 327 SYNTAX Unsigned32 329 AncpPartitionId ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "A 8-bit value identifying a partition on the AN." 333 SYNTAX OCTET STRING (SIZE(1)) 335 AncpName ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "The Name is a 48-bit quantity. 339 A 48-bit IEEE 802 MAC address, if 340 available, may be used." 341 SYNTAX OCTET STRING (SIZE(6)) 342 END 344 ANCP-AN-MIB DEFINITIONS ::= BEGIN 346 IMPORTS 347 MODULE-IDENTITY, OBJECT-TYPE, 348 Unsigned32, TimeTicks,zeroDotZero, 349 NOTIFICATION-TYPE, mib-2 350 FROM SNMPv2-SMI -- RFC2578 351 ZeroBasedCounter32 352 FROM RMON2-MIB -- RFC4502 353 InterfaceIndex, ifIndex FROM IF-MIB -- RFC2863 354 InetAddressType, InetAddress, InetPortNumber 355 FROM INET-ADDRESS-MIB -- RFC4001 356 MODULE-COMPLIANCE, OBJECT-GROUP, 357 NOTIFICATION-GROUP 358 FROM SNMPv2-CONF -- RFC2580 359 RowStatus, TruthValue, RowPointer 360 FROM SNMPv2-TC -- RFC2579 361 VlanIdOrNone 362 FROM Q-BRIDGE-MIB -- RFC4363 363 AncpSessionCapabilities, AncpVersion, 364 AncpPartitionId, AncpName 365 FROM ANCP-TC-MIB; -- This document 367 ancpAnMIB MODULE-IDENTITY 368 LAST-UPDATED "201306240000Z" -- 24 June 2013 369 ORGANIZATION "IETF ANCP Working Group" 370 CONTACT-INFO 371 " Editors: 373 Stefaan De Cnodder 374 Alcatel-Lucent 375 Postal: Copernicuslaan 50 376 B-2018 Antwerp 377 Belgium 378 EMail: stefaan.de_cnodder@alcatel-lucent.com 379 Phone: +32 3 240 85 15 381 Moti Morgenstern 382 ECI Telecom Ltd. 383 Postal: 30 Hasivim St. 384 Petach Tikva 4959388, 385 Israel 386 Email: moti.morgenstern@ecitele.com 387 Phone: +972 3 926 6258 388 " 389 DESCRIPTION 390 "The MIB module for entities implementing the access node 391 side of the Access Node Control Protocol (ANCP). 393 Copyright (C) The IETF Trust (2008). The initial version 394 of this MIB module was published in RFC yyyy; for full 395 legal notices see the RFC itself." 396 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 397 REVISION "201306240000Z" -- 24 June 2013 398 DESCRIPTION "Initial version as published in RFC yyyy." 399 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 400 ::= { mib-2 xxx } 401 -- The value xxx to be assigned by IANA. 403 ancpAnNotifications OBJECT IDENTIFIER ::= { ancpAnMIB 0 } 404 ancpAnObjects OBJECT IDENTIFIER ::= { ancpAnMIB 1 } 405 ancpAnConformance OBJECT IDENTIFIER ::= { ancpAnMIB 2 } 407 -- 408 -- Global ANCP Control Parameters 409 -- 410 -- The following scalar parameters globally control the behavior 411 -- of the ANCP implementation 412 -- 414 ancpAnPartitionsUsed OBJECT-TYPE 416 SYNTAX TruthValue 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "This object allows the manager to specify whether or 421 not to use the 'Partition ID' field in the ANCP message 422 header. When set to 'false' the application does not 423 use partitions and the ancpAnSessionConfigPartitionId 424 object MUST be zero for all sessions. In addition, rows 425 SHOULD NOT be created in the ancpAnInterfaceConfigTable. 426 When set to 'true' the application uses partitions and 427 the ancpAnSessionConfigPartitionId object MUST be set, 428 for every session, to a nonzero value. In such a case, 429 rows are created in ancpAnInterfaceConfigTable. The 430 default value zero in ancpAnInterfaceConfigPartitionId 431 object means that the operator did not associate the 432 interface with a particular partition. Note that 433 modifying the value of this object is restricted. 434 E.g., prior to setting it from 'true' to 'false' 435 ancpAnSessionConfigRowStatus objects for all sessions 436 should be set to notInService and the partition ID value 437 MUST be set to zero. 438 The value of this object is persistent." 439 DEFVAL { false } 440 ::= { ancpAnObjects 1 } 442 -- 443 -- Configuration of ANCP Sessions 444 -- 446 ancpAnNextSessionId OBJECT-TYPE 447 SYNTAX Unsigned32 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The object reports the next index (potential value of 452 ancpAnSessionConfigSessionId) which is available for 453 creating a new row in ancpAnSessionConfigTable. 454 If no such value is available (e.g., the table is full 455 or any other reason) the object reports '0' (zero). 456 An available value V becomes unavailable when a row is 457 actually created with ancpAnSessionConfigSessionId=V and 458 until then consecutive GET commands with this object may 459 return the same value V. Note that eventually only one 460 row creation with the value V can succeed. 461 An unavailable value V becomes available again when a 462 row with ancpAnSessionConfigSessionId=V in 463 ancpAnSessionConfigTable is deleted." 464 ::= { ancpAnObjects 2 } 466 ancpAnSessionConfigTable OBJECT-TYPE 467 SYNTAX SEQUENCE OF AncpAnSessionConfigEntry 468 MAX-ACCESS not-accessible 469 STATUS current 470 DESCRIPTION 471 "This table represents the ANCP sessions in the access 472 node. An entry in this table needs to be configured 473 (created) before an ANCP session might be started." 474 ::= { ancpAnObjects 3 } 476 ancpAnSessionConfigEntry OBJECT-TYPE 477 SYNTAX AncpAnSessionConfigEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "An entry in the table showing the data for a 482 specific actual or yet to be established session. 483 If partitions are used, one session corresponds to 484 one specific access node partition." 485 INDEX { ancpAnSessionConfigSessionId } 486 ::= { ancpAnSessionConfigTable 1 } 488 AncpAnSessionConfigEntry ::= SEQUENCE { 489 ancpAnSessionConfigSessionId Unsigned32, 490 ancpAnSessionConfigRowStatus RowStatus, 491 ancpAnSessionConfigAncpVersion AncpVersion, 492 ancpAnSessionConfigEncapsulationType INTEGER, 493 ancpAnSessionConfigCapabilities AncpSessionCapabilities, 494 ancpAnSessionConfigAliveTimer Unsigned32, 495 ancpAnSessionConfigPortReportShaper Unsigned32, 496 ancpAnSessionConfigAggregateReportShaper Unsigned32, 497 ancpAnSessionConfigTransportRetryTimer Unsigned32, 498 ancpAnSessionConfigAncpRetryTimer Unsigned32, 499 ancpAnSessionConfigAnName AncpName, 500 ancpAnSessionConfigPartitionId AncpPartitionId, 501 ancpAnSessionConfigWindowSize Unsigned32, 502 ancpAnSessionConfigRelatedInterface InterfaceIndex, 503 ancpAnSessionConfigRelatedEntity RowPointer, 504 ancpAnSessionConfigSvid VlanIdOrNone, 505 ancpAnSessionConfigSPrio Unsigned32, 506 ancpAnSessionConfigCvid VlanIdOrNone, 507 ancpAnSessionConfigCPrio Unsigned32, 508 ancpAnSessionConfigNasIpAddressType InetAddressType, 509 ancpAnSessionConfigNasIpAddress InetAddress, 510 ancpAnSessionConfigEncapPortNumber InetPortNumber, 511 ancpAnSessionConfigNotifyDnEnable TruthValue, 512 ancpAnSessionConfigNotifyUpEnable TruthValue 513 } 515 ancpAnSessionConfigSessionId OBJECT-TYPE 516 SYNTAX Unsigned32 (1..255) 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "An index of a session referred by this row. The index 521 is unique across all partitions. 522 The referred session may be actually established or 523 just potential. 524 Prior to creating a row in the table it is advised to 525 check the ancpAnNextSessionId for an available index." 526 ::= { ancpAnSessionConfigEntry 1 } 528 ancpAnSessionConfigRowStatus OBJECT-TYPE 529 SYNTAX RowStatus 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "An object that allows entries in this table to 534 be created, modified and deleted using the RowStatus 535 convention. 536 A SET operation to any other attribute in this row, 537 when this object is set to 'active' (1), MUST be 538 rejected with an SNMP error (e.g., inconsistentValue). 539 In order to perform a SET operation to any other 540 attribute in this table the manager MUST set this 541 object to notInService (2). After setting the object 542 back to 'active' the implementation MAY tear down the 543 session and recreate it, depending on what session 544 attributes have been modified. " 545 ::= { ancpAnSessionConfigEntry 2 } 547 ancpAnSessionConfigAncpVersion OBJECT-TYPE 548 SYNTAX AncpVersion 549 MAX-ACCESS read-create 550 STATUS current 551 DESCRIPTION 552 "The maximum version number of the ANCP protocol that 553 may be used in this session. The value of this object 554 is persistent." 555 DEFVAL { 50 } 556 ::= { ancpAnSessionConfigEntry 3 } 558 ancpAnSessionConfigEncapsulationType OBJECT-TYPE 559 SYNTAX INTEGER { 560 tcp(1) 561 } 562 MAX-ACCESS read-create 563 STATUS current 564 DESCRIPTION 565 "Required encapsulation for this session. The value of 566 this object is persistent." 567 DEFVAL { tcp } 568 ::= { ancpAnSessionConfigEntry 4 } 570 ancpAnSessionConfigCapabilities OBJECT-TYPE 571 SYNTAX AncpSessionCapabilities 572 MAX-ACCESS read-create 573 STATUS current 574 DESCRIPTION 575 "ANCP capabilities supported by the AN in this session. 576 When all bits are set to zero then this means that no 577 capabilities are supported. The value of this object 578 is persistent." 579 DEFVAL { { dslTopologyDiscovery, dslLineTesting } } 580 ::= { ancpAnSessionConfigEntry 5 } 582 ancpAnSessionConfigAliveTimer OBJECT-TYPE 583 SYNTAX Unsigned32(1..255) 584 UNITS "deciseconds" 585 MAX-ACCESS read-create 586 STATUS current 587 DESCRIPTION 588 "The timer specifies the nominal time between periodic 589 adjacency protocol messages generated by the access 590 node. 591 It is a constant for the duration of an ANCP session. 592 The timer is specified in units of 100ms. The value 593 of this object is persistent." 594 DEFVAL { 250 } 595 ::= { ancpAnSessionConfigEntry 6 } 597 ancpAnSessionConfigPortReportShaper OBJECT-TYPE 598 SYNTAX Unsigned32(1..255) 599 UNITS "deciseconds" 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "The timer specifies the nominal time between 604 2 EventReport messages related to the same port. 605 It is a constant for the duration of a ANCP session. 606 The timer is specified in units of 100ms. The value 607 of this object is persistent." 608 DEFVAL { 10 } 609 ::= { ancpAnSessionConfigEntry 7 } 611 ancpAnSessionConfigAggregateReportShaper OBJECT-TYPE 612 SYNTAX Unsigned32(1..2550) 613 UNITS "centiseconds" 614 MAX-ACCESS read-create 615 STATUS current 616 DESCRIPTION 617 "The timer specifies the nominal time between 618 2 EventReport messages related to any port. 619 It is a constant for the duration of a ANCP session. 620 The timer is specified in units of 10ms. The value 621 of this object is persistent." 622 DEFVAL { 10 } 623 ::= { ancpAnSessionConfigEntry 8 } 625 ancpAnSessionConfigTransportRetryTimer OBJECT-TYPE 626 SYNTAX Unsigned32(0..255) 627 UNITS "deciseconds" 628 MAX-ACCESS read-create 629 STATUS current 630 DESCRIPTION 631 "The timer specifies the nominal time between 2 632 transport connection setup attempts done by the 633 access node. 634 The transport protocol is specified in 635 ancpAnSessionConfigEncapsulationType. 636 The timer is specified in units of 100ms. 637 A value 0 means that the access node will NOT 638 initiate nor setup the transport connection. The 639 value of this object is persistent." 640 DEFVAL { 10 } 641 ::= { ancpAnSessionConfigEntry 9 } 643 ancpAnSessionConfigAncpRetryTimer OBJECT-TYPE 644 SYNTAX Unsigned32(0..255) 645 UNITS "deciseconds" 646 MAX-ACCESS read-create 647 STATUS current 648 DESCRIPTION 649 "The timer specifies the nominal time between 650 2 ANCP connection setup attempts. 651 The timer is specified in units of 100ms. 652 A value 0 means that the access node will NOT 653 spontaneously trigger an ANCP session. 654 Whatever the setting of this timer, the access 655 node shall always listen for ANCP session setup. 656 The value of this object is persistent." 657 DEFVAL { 10 } 658 ::= { ancpAnSessionConfigEntry 10 } 660 ancpAnSessionConfigAnName OBJECT-TYPE 661 SYNTAX AncpName 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "The name of the access node. The first three octets 666 must be an Organizationally Unique Identifier (OUI) 667 that identifies the manufacturer of the access node. 668 This object can be (one of) the MAC address(es) of the 669 access node on the network side. 670 When set to zero, the access node shall autonomously 671 decide on using the most appropriate MAC address of the 672 access node. Then the actually used access node name 673 can be read from ancpAnCurrentSessionAnName. 674 The value of this object is persistent." 675 DEFVAL { '000000000000'H } 676 ::= { ancpAnSessionConfigEntry 11 } 678 ancpAnSessionConfigPartitionId OBJECT-TYPE 679 SYNTAX AncpPartitionId 680 MAX-ACCESS read-create 681 STATUS current 682 DESCRIPTION 683 "The Id for this session's specific access node 684 partition. 685 This object has a meaning only if partitions are used 686 (ancpAnPartitionsUsed='true') and is ignored 687 otherwise. 688 The value of this object is persistent." 689 DEFVAL { '00'H } 690 ::= { ancpAnSessionConfigEntry 12 } 692 ancpAnSessionConfigWindowSize OBJECT-TYPE 693 SYNTAX Unsigned32(1..65535) 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "The maximum number of unacknowledged request messages 698 that may be transmitted by the controller without the 699 possibility of loss. This field is used to prevent 700 request messages from being lost in the access node 701 because of overflow in the receive buffer. The field is 702 a hint to the controller. The value of this object is 703 persistent." 704 DEFVAL { 10 } 705 ::= { ancpAnSessionConfigEntry 13 } 707 ancpAnSessionConfigRelatedInterface OBJECT-TYPE 708 SYNTAX InterfaceIndex 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "This object contains the value of an ifIndex object, 713 defined in IF-MIB, indicating an interface 714 corresponding to this session. 715 The corresponding interface might be either physical 716 or logical (e.g., IP Interface). 717 The value of this object is persistent." 718 ::= { ancpAnSessionConfigEntry 14 } 720 ancpAnSessionConfigRelatedEntity OBJECT-TYPE 721 SYNTAX RowPointer 722 MAX-ACCESS read-create 723 STATUS current 724 DESCRIPTION 725 "This object contains the name of an object instance 726 uniquely identifying a lower layer entity associated 727 with this session. For example, in the case where the 728 session is associated with an ATM VCC, this object might 729 be set to an object identifier uniquely identifying 730 that VCC (e.g., an object instance in atmVclTable). 731 If unused, this object MUST have the value zeroDotZero. 732 The value of this object is persistent." 733 DEFVAL { zeroDotZero } 734 ::= { ancpAnSessionConfigEntry 15 } 736 ancpAnSessionConfigSvid OBJECT-TYPE 737 SYNTAX VlanIdOrNone 738 MAX-ACCESS read-create 739 STATUS current 740 DESCRIPTION 741 "If the session is associated with a single VLAN, this 742 object contains the VLAN ID of the single VLAN tag. If 743 ancpAnSessionConfigCvid is also nonzero then the 744 session is associated with two VLAN tags, S-VLAN tag 745 and C-VLAN tag, then this object contains the VLAN ID 746 of the S-VLAN tag (the outer VLAN tag). In both cases 747 the value of this object SHOULD be nonzero. 748 If the session is not associated with any VLAN, this 749 object MUST have the default value 0. 750 The value of this object is persistent." 751 DEFVAL { 0 } 752 ::= { ancpAnSessionConfigEntry 16 } 754 ancpAnSessionConfigSPrio OBJECT-TYPE 755 SYNTAX Unsigned32(0..7 | 65535) 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "If the session is associated with a single VLAN, this 760 object contains the priority value of the single VLAN 761 tag. 762 If ancpAnSessionConfigCvid is also nonzero then the 763 session is associated with two VLAN tags, S-VLAN tag 764 and C-VLAN tag, then this object contains the priority 765 value of the S-VLAN tag (the priority value of the 766 outer VLAN tag). In both cases the value of this object 767 SHOULD be in the range 0 to 7 inclusive. 768 If the session is not associated with any VLAN, this 769 object MUST have the default value 65535. 770 The value of this object is persistent." 771 DEFVAL { 65535 } 772 ::= { ancpAnSessionConfigEntry 17 } 774 ancpAnSessionConfigCvid OBJECT-TYPE 775 SYNTAX VlanIdOrNone 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "If the session is associated with two VLANs, has both 780 S-VLAN tag and C-VLAN tag, this object contains the 781 VLAN ID of the inner VLAN tag (also called C-VLAN ID). 782 In such a case the value of this object SHOULD be 783 nonzero. 784 If the session is not associated with any VLAN or if it 785 is associated with a single VLAN, this object MUST 786 have the default value 0. 787 The value of this object is persistent." 788 DEFVAL { 0 } 789 ::= { ancpAnSessionConfigEntry 18 } 791 ancpAnSessionConfigCPrio OBJECT-TYPE 792 SYNTAX Unsigned32(0..7 | 65535) 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "If the session is associated with two VLANs, has both 797 S-VLAN tag and C-VLAN tag, this object contains the 798 priority value of the inner VLAN tag (also called 799 C-VLAN priority). In such a case the value of this 800 object SHOULD be in the range 0 to 7 inclusive. 801 If the session is not associated with any VLAN or if it 802 is associated with a single VLAN, this object MUST have 803 the default value 65535. 804 The value of this object is persistent." 806 DEFVAL { 65535 } 807 ::= { ancpAnSessionConfigEntry 19 } 809 ancpAnSessionConfigNasIpAddressType OBJECT-TYPE 810 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 811 MAX-ACCESS read-create 812 STATUS current 813 DESCRIPTION 814 "The type of address in ancpAnSessionConfigNasIpAddress. 815 The value of this object is persistent. 816 Note that although other types of addresses are defined 817 in the InetAddressType textual convention, this object 818 is limited to IPv4 and IPv6 addresses." 819 ::= { ancpAnSessionConfigEntry 20 } 821 ancpAnSessionConfigNasIpAddress OBJECT-TYPE 822 SYNTAX InetAddress 823 MAX-ACCESS read-create 824 STATUS current 825 DESCRIPTION 826 "The IP address used for the ANCP session peer (NAS). 827 The type of this IP address attribute is determined 828 by the value of ancpAnSessionConfigNasIpAddressType. 829 The value of this object is persistent." 830 ::= { ancpAnSessionConfigEntry 21 } 832 ancpAnSessionConfigEncapPortNumber OBJECT-TYPE 833 SYNTAX InetPortNumber (1..65535) 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "The port number used for the transport protocol 838 establishment to the ANCP peer. The transport 839 protocol type is specified by 840 ancpAnSessionConfigEncapsulationType and as 841 it is set by default to 'tcp' then the default 842 port number is set to 6068 (see details in 843 http://www.iana.org/). Other port numbers may 844 be relevant if other transport protocols are used. 845 The value of this object is persistent." 846 DEFVAL { 6068 } 847 ::= { ancpAnSessionConfigEntry 22 } 849 ancpAnSessionConfigNotifyDnEnable OBJECT-TYPE 850 SYNTAX TruthValue 851 MAX-ACCESS read-create 852 STATUS current 853 DESCRIPTION 854 "This object specifies if ancpAnSessionDown 855 notification should be generated when this session 856 leaves the 'estab' state as given by 857 ancpAnCurrentSessionState in the corresponding row 858 in ancpAnCurrentSessionTable. 859 The value of this object is persistent." 860 DEFVAL { false } 861 ::= { ancpAnSessionConfigEntry 23 } 863 ancpAnSessionConfigNotifyUpEnable OBJECT-TYPE 864 SYNTAX TruthValue 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "This object specifies if ancpAnSessionUp 869 notification should be generated when this session 870 goes to 'estab' state as given by 871 ancpAnCurrentSessionState in the corresponding row 872 in ancpAnCurrentSessionTable. 873 The value of this object is persistent." 874 DEFVAL { false } 875 ::= { ancpAnSessionConfigEntry 24 } 877 -- 878 -- Operational Information of ANCP Sessions 879 -- 881 ancpAnCurrentSessionTable OBJECT-TYPE 882 SYNTAX SEQUENCE OF AncpAnCurrentSessionEntry 883 MAX-ACCESS not-accessible 884 STATUS current 885 DESCRIPTION 886 "This table gives actual information of the sessions 887 in the access node. 888 A row in this table is available only for active 889 sessions, i.e., for each session that its corresponding 890 row status (ancpAnSessionConfigRowStatus) in 891 ancpAnSessionConfigTable is set to either 'active' (1) 892 or 'notInService' (2). 893 A row in this table is deleted when the corresponding 894 row in the ancpAnSessionConfigTable is deleted." 895 ::= { ancpAnObjects 4 } 897 ancpAnCurrentSessionEntry OBJECT-TYPE 898 SYNTAX AncpAnCurrentSessionEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "An entry in the table showing the data for a 903 specific actual session." 904 INDEX { ancpAnSessionConfigSessionId } 905 ::= { ancpAnCurrentSessionTable 1 } 907 AncpAnCurrentSessionEntry ::= SEQUENCE { 908 ancpAnCurrentSessionState INTEGER, 909 ancpAnCurrentSessionAncpVersion AncpVersion, 910 ancpAnCurrentSessionAnName AncpName, 911 ancpAnCurrentSessionNasName AncpName, 912 ancpAnCurrentSessionAnIpAddressType InetAddressType, 913 ancpAnCurrentSessionAnIpAddress InetAddress, 914 ancpAnCurrentSessionAnInstance Unsigned32, 915 ancpAnCurrentSessionNasInstance Unsigned32, 916 ancpAnCurrentSessionCapabilities AncpSessionCapabilities, 917 ancpAnCurrentSessionStartUptime TimeTicks, 918 ancpAnCurrentSessionDiscontinuityTime TimeTicks, 919 ancpAnCurrentSessionStatSentMessages ZeroBasedCounter32, 920 ancpAnCurrentSessionStatReceivedValidMessages 921 ZeroBasedCounter32, 922 ancpAnCurrentSessionStatDiscardedMessages ZeroBasedCounter32, 923 ancpAnCurrentSessionStatReceivedAdjSyn ZeroBasedCounter32, 924 ancpAnCurrentSessionStatReceivedAdjSynack ZeroBasedCounter32, 925 ancpAnCurrentSessionStatReceivedAdjAck ZeroBasedCounter32, 926 ancpAnCurrentSessionStatReceivedAdjRstack ZeroBasedCounter32, 927 ancpAnCurrentSessionStatTransmittedAdjSyn ZeroBasedCounter32, 928 ancpAnCurrentSessionStatTransmittedAdjSynack 929 ZeroBasedCounter32, 930 ancpAnCurrentSessionStatTransmittedAdjAck ZeroBasedCounter32, 931 ancpAnCurrentSessionStatTransmittedAdjRstack 932 ZeroBasedCounter32 933 } 935 ancpAnCurrentSessionState OBJECT-TYPE 936 SYNTAX INTEGER { 937 other(1), 938 synsent(2), 939 synrcvd(3), 940 estab(4), 941 syncloss(5) 942 } 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The state of this session as defined in the ANCP 947 specification. 948 the state other(1) is returned if the session state 949 cannot be reflected by any other valid object-value. 951 The state syncloss(5) indicates that the AN has 952 declared loss of synchronization as defined in section 953 3.5.2.7 of RFC 6320." 954 ::= { ancpAnCurrentSessionEntry 1 } 956 ancpAnCurrentSessionAncpVersion OBJECT-TYPE 957 SYNTAX AncpVersion 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "The actual version number of the ANCP protocol that 962 is used in this session. 963 This object has value 0 if ancpAnCurrentSessionState is 964 not estab(4)." 965 ::= { ancpAnCurrentSessionEntry 2 } 967 ancpAnCurrentSessionAnName OBJECT-TYPE 968 SYNTAX AncpName 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The name of the access node used in this session. 973 It should be the same as ancpAnSessionConfigAnName if 974 that object is not set to zero. 975 If ancpAnSessionConfigAnName is set to zero, then this 976 object will contain the MAC address selected by the 977 access node as described in the description of 978 ancpAnSessionConfigAnName. 979 The value of this object is used as value for the 980 'Sender Name' field in the header of the ANCP messages 981 generated for this session by the AN." 982 ::= { ancpAnCurrentSessionEntry 3 } 984 ancpAnCurrentSessionNasName OBJECT-TYPE 985 SYNTAX AncpName 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "The name of the NAS as advertised in the adjacency 990 message. 991 The value of this object is set to the value of the 992 'Sender Name' field in the header of the ANCP messages 993 received on this session. This object has value 0 if 994 ancpAnCurrentSessionState is not estab(4)." 995 ::= { ancpAnCurrentSessionEntry 4 } 997 ancpAnCurrentSessionAnIpAddressType OBJECT-TYPE 998 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "The type of address in ancpAnCurrentSessionAnIpAddress. 1003 Note that although other types of addresses are defined 1004 in the InetAddressType textual convention, this object 1005 is limited to IPv4 and IPv6 addresses." 1006 ::= { ancpAnCurrentSessionEntry 5 } 1008 ancpAnCurrentSessionAnIpAddress OBJECT-TYPE 1009 SYNTAX InetAddress 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "The IP address used for the access node. 1014 The type of this IP address attribute is determined 1015 by the value of ancpAnCurrentSessionAnIpAddressType." 1016 ::= { ancpAnCurrentSessionEntry 6 } 1018 ancpAnCurrentSessionAnInstance OBJECT-TYPE 1019 SYNTAX Unsigned32(0..16777215) 1020 MAX-ACCESS read-only 1021 STATUS current 1022 DESCRIPTION 1023 "The instance number used by the access node during this 1024 session. The Instance number is a 24-bit number 1025 that should be guaranteed to be unique within 1026 the recent past and to change when the link 1027 or node comes back up after going down. Zero is 1028 not a valid instance number. 1029 This object has value 0 if ancpAnCurrentSessionState is 1030 not estab(4)." 1031 ::= { ancpAnCurrentSessionEntry 7 } 1033 ancpAnCurrentSessionNasInstance OBJECT-TYPE 1034 SYNTAX Unsigned32(0..16777215) 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The instance number used by the NAS during this 1039 session. The Instance number is a 24-bit number 1040 that should be guaranteed to be unique within 1041 the recent past and to change when the link 1042 or node comes back up after going down. 1043 This object has value 0 if ancpAnCurrentSessionState is 1044 not estab(4)." 1045 ::= { ancpAnCurrentSessionEntry 8 } 1047 ancpAnCurrentSessionCapabilities OBJECT-TYPE 1048 SYNTAX AncpSessionCapabilities 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "The common ANCP capabilities supported by the AN and 1053 NAS in this session. 1054 The object has the value 0 if no capabilities are 1055 supported 1056 or if ancpAnCurrentSessionState is not estab(4)." 1057 ::= { ancpAnCurrentSessionEntry 9 } 1059 ancpAnCurrentSessionStartUptime OBJECT-TYPE 1060 SYNTAX TimeTicks 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "The value of sysUpTime when the session came to 1065 established state. 1066 This object has value 0 if ancpAnCurrentSessionState is 1067 not estab(4)." 1068 ::= { ancpAnCurrentSessionEntry 10 } 1070 ancpAnCurrentSessionDiscontinuityTime OBJECT-TYPE 1071 SYNTAX TimeTicks 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The value of sysUpTime on the most recent occasion at 1076 which session's counters suffered a discontinuity. 1077 If no such discontinuities have occurred since then, 1078 this object contains the same value as 1079 ancpAnCurrentSessionStartUptime." 1080 ::= { ancpAnCurrentSessionEntry 11 } 1082 ancpAnCurrentSessionStatSentMessages OBJECT-TYPE 1083 SYNTAX ZeroBasedCounter32 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "The number of messages that have been sent in this 1088 session by the access node. 1089 All ANCP messages pertaining to this session shall 1090 be counted, also including adjacency protocol messages 1091 and failure response messages. 1092 Discontinuities of this counter are indicated by 1093 ancpAnCurrentSessionDiscontinuityTime." 1094 ::= { ancpAnCurrentSessionEntry 12 } 1096 ancpAnCurrentSessionStatReceivedValidMessages OBJECT-TYPE 1097 SYNTAX ZeroBasedCounter32 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The number of messages that have been received and 1102 processed in this session by the access node. 1103 All ANCP messages pertaining to this session shall 1104 be counted, also including adjacency protocol messages 1105 and failure response messages. 1106 Discontinuities of this counter are indicated by 1107 ancpAnCurrentSessionDiscontinuityTime." 1108 ::= { ancpAnCurrentSessionEntry 13 } 1110 ancpAnCurrentSessionStatDiscardedMessages OBJECT-TYPE 1111 SYNTAX ZeroBasedCounter32 1112 MAX-ACCESS read-only 1113 STATUS current 1114 DESCRIPTION 1115 "The number of messages that in this session have been 1116 received and discarded for whatever reason by the 1117 access node. 1118 All ANCP messages pertaining to this session shall 1119 be counted, also including adjacency protocol messages 1120 and failure response messages. 1121 Discontinuities of this counter are indicated by 1122 ancpAnCurrentSessionDiscontinuityTime." 1123 ::= { ancpAnCurrentSessionEntry 14 } 1125 ancpAnCurrentSessionStatReceivedAdjSyn OBJECT-TYPE 1126 SYNTAX ZeroBasedCounter32 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "The number of adjacency SYN messages that in this 1131 session have been received by the access node. 1132 Discontinuities of this counter are indicated by 1133 ancpAnCurrentSessionDiscontinuityTime." 1134 ::= { ancpAnCurrentSessionEntry 15 } 1136 ancpAnCurrentSessionStatReceivedAdjSynack OBJECT-TYPE 1137 SYNTAX ZeroBasedCounter32 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "The number of adjacency SYNACK messages that in this 1142 session have been received by the access node. 1143 Discontinuities of this counter are indicated by 1144 ancpAnCurrentSessionDiscontinuityTime." 1145 ::= { ancpAnCurrentSessionEntry 16 } 1147 ancpAnCurrentSessionStatReceivedAdjAck OBJECT-TYPE 1148 SYNTAX ZeroBasedCounter32 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The number of adjacency ACK messages that in this 1153 session have been received by the access node. 1154 Discontinuities of this counter are indicated by 1155 ancpAnCurrentSessionDiscontinuityTime." 1156 ::= { ancpAnCurrentSessionEntry 17 } 1158 ancpAnCurrentSessionStatReceivedAdjRstack OBJECT-TYPE 1159 SYNTAX ZeroBasedCounter32 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The number of adjacency RSTACK messages that in this 1164 session have been received by the access node. 1165 Discontinuities of this counter are indicated by 1166 ancpAnCurrentSessionDiscontinuityTime." 1167 ::= { ancpAnCurrentSessionEntry 18 } 1169 ancpAnCurrentSessionStatTransmittedAdjSyn OBJECT-TYPE 1170 SYNTAX ZeroBasedCounter32 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "The number of adjacency SYN messages that in this 1175 session have been transmitted by the access node. 1176 Discontinuities of this counter are indicated by 1177 ancpAnCurrentSessionDiscontinuityTime." 1178 ::= { ancpAnCurrentSessionEntry 19 } 1180 ancpAnCurrentSessionStatTransmittedAdjSynack OBJECT-TYPE 1181 SYNTAX ZeroBasedCounter32 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The number of adjacency SYNACK messages that in this 1186 session have been transmitted by the access node. 1187 Discontinuities of this counter are indicated by 1188 ancpAnCurrentSessionDiscontinuityTime." 1189 ::= { ancpAnCurrentSessionEntry 20 } 1191 ancpAnCurrentSessionStatTransmittedAdjAck OBJECT-TYPE 1192 SYNTAX ZeroBasedCounter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The number of adjacency ACK messages that in this 1197 session have been transmitted by the access node. 1198 Discontinuities of this counter are indicated by 1199 ancpAnCurrentSessionDiscontinuityTime." 1200 ::= { ancpAnCurrentSessionEntry 21 } 1202 ancpAnCurrentSessionStatTransmittedAdjRstack OBJECT-TYPE 1203 SYNTAX ZeroBasedCounter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The number of adjacency RSTACK messages that in this 1208 session have been transmitted by the access node. 1209 Discontinuities of this counter are indicated by 1210 ancpAnCurrentSessionDiscontinuityTime." 1211 ::= { ancpAnCurrentSessionEntry 22 } 1213 -- 1214 -- Partitions 1215 -- 1217 ancpAnInterfaceConfigTable OBJECT-TYPE 1218 SYNTAX SEQUENCE OF AncpAnInterfaceConfigEntry 1219 MAX-ACCESS not-accessible 1220 STATUS current 1221 DESCRIPTION 1222 "This table configures the association of user facing 1223 interfaces to ANCP partitions in the access node. 1224 An entry in this table needs to be added by the agent 1225 for each relevant user facing interface with the value 1226 of ancpAnInterfaceConfigPartitionId set to zero at the 1227 time of the creation of the row. A relevant user facing 1228 interface is created whenever a row is created in the 1229 ifTable of the IF-MIB that can be controlled by ANCP. 1230 When such an interface is deleted from the ifTable, the 1231 corresponding row in this table has to be removed by 1232 the agent. 1233 Rows should only be created by the agent when 1234 ancpAnPartitionsUsed is set to 'true'. If no 1235 partitions are used, then no rows should be created in 1236 this table." 1237 ::= { ancpAnObjects 5 } 1239 ancpAnInterfaceConfigEntry OBJECT-TYPE 1240 SYNTAX AncpAnInterfaceConfigEntry 1241 MAX-ACCESS not-accessible 1242 STATUS current 1243 DESCRIPTION 1244 "An entry in the table showing the partition id for a 1245 specific user facing interface" 1246 INDEX { ifIndex } 1247 ::= { ancpAnInterfaceConfigTable 1 } 1249 AncpAnInterfaceConfigEntry ::= SEQUENCE { 1250 ancpAnInterfaceConfigPartitionId AncpPartitionId 1251 } 1253 ancpAnInterfaceConfigPartitionId OBJECT-TYPE 1254 SYNTAX AncpPartitionId 1255 MAX-ACCESS read-write 1256 STATUS current 1257 DESCRIPTION 1258 "A partition Id associated with the related ifIndex. 1259 Upon creation of the row, the value is set to '00'H. 1260 The value of this object is persistent." 1261 DEFVAL { '00'H } 1262 ::= { ancpAnInterfaceConfigEntry 1 } 1264 -- 1265 -- Notifications 1266 -- 1268 ancpAnSessionDown NOTIFICATION-TYPE 1269 OBJECTS { 1270 ancpAnCurrentSessionAnIpAddressType, 1271 ancpAnCurrentSessionAnIpAddress, 1272 ancpAnSessionConfigNasIpAddressType, 1273 ancpAnSessionConfigNasIpAddress, 1274 ancpAnCurrentSessionAnInstance, 1275 ancpAnCurrentSessionNasInstance, 1276 ancpAnCurrentSessionStartUptime, 1277 ancpAnCurrentSessionDiscontinuityTime, 1278 ancpAnCurrentSessionStatSentMessages, 1279 ancpAnCurrentSessionStatReceivedValidMessages, 1280 ancpAnCurrentSessionStatDiscardedMessages, 1281 ancpAnCurrentSessionStatReceivedAdjSyn, 1282 ancpAnCurrentSessionStatReceivedAdjSynack, 1283 ancpAnCurrentSessionStatReceivedAdjAck, 1284 ancpAnCurrentSessionStatReceivedAdjRstack, 1285 ancpAnCurrentSessionStatTransmittedAdjSyn, 1286 ancpAnCurrentSessionStatTransmittedAdjSynack, 1287 ancpAnCurrentSessionStatTransmittedAdjAck, 1288 ancpAnCurrentSessionStatTransmittedAdjRstack 1289 } 1290 STATUS current 1291 DESCRIPTION 1292 "This notification is generated whenever an ANCP session 1293 goes down. A session can go down for several reasons: 1294 1) The ANCP session can be deleted by a manager from the 1295 ancpAnSessionConfigTable, and hence it will also be 1296 removed from the ancpAnCurrentSessionTable. 1297 2) The session can go operational down due to some 1298 malfunction in the network, the AN, or the NAS. In 1299 this case, the ANCP session will be still in the 1300 ancpAnSessionConfigTable and 1301 ancpAnCurrentSessionTable, but the 1302 ancpAnCurrentSessionState moves from the 'estab' 1303 state to another state. 1304 This notification is only generated when 1305 ancpAnSessionConfigNotifyDnEnable of this session is 1306 set to true." 1307 ::= { ancpAnNotifications 1 } 1309 ancpAnSessionUp NOTIFICATION-TYPE 1310 OBJECTS { 1311 ancpAnCurrentSessionAnInstance 1312 } 1313 STATUS current 1314 DESCRIPTION 1315 "This notification is generated when an ANCP session 1316 enters the 'estab' state as given by 1317 ancpAnCurrentSessionState. 1318 Since ancpAnCurrentSessionAnInstance identifies the ANCP 1319 session uniquely the other attributes can be derived 1320 from this attribute. 1321 This notification is only generated when 1322 ancpAnSessionConfigNotifyUpEnable of this session is set 1323 to true." 1324 ::= { ancpAnNotifications 2 } 1326 -- 1327 -- ANCP AN Compliance 1328 -- 1330 ancpAnGroups OBJECT IDENTIFIER ::= { ancpAnConformance 1 } 1331 ancpAnCompliances OBJECT IDENTIFIER ::= { ancpAnConformance 2 } 1333 ancpAnModuleCompliance MODULE-COMPLIANCE 1334 STATUS current 1335 DESCRIPTION 1336 "The compliance statement for agents that support 1337 the ANCP MIB module for access nodes." 1338 MODULE -- this module 1339 MANDATORY-GROUPS { 1340 ancpAnConfigGroup, 1341 ancpAnCurrentGroup, 1342 ancpAnInterfaceGroup, 1343 ancpAnNotificationsGroup 1344 } 1345 ::= { ancpAnCompliances 1 } 1347 -- units of conformance 1349 ancpAnConfigGroup OBJECT-GROUP 1350 OBJECTS { 1351 ancpAnNextSessionId, 1352 ancpAnSessionConfigRowStatus, 1353 ancpAnSessionConfigAncpVersion, 1354 ancpAnSessionConfigEncapsulationType, 1355 ancpAnSessionConfigCapabilities, 1356 ancpAnSessionConfigAliveTimer, 1357 ancpAnSessionConfigPortReportShaper, 1358 ancpAnSessionConfigAggregateReportShaper, 1359 ancpAnSessionConfigTransportRetryTimer, 1360 ancpAnSessionConfigAncpRetryTimer, 1361 ancpAnSessionConfigAnName, 1362 ancpAnSessionConfigPartitionId, 1363 ancpAnSessionConfigWindowSize, 1364 ancpAnSessionConfigNasIpAddressType, 1365 ancpAnSessionConfigNasIpAddress, 1366 ancpAnSessionConfigEncapPortNumber, 1367 ancpAnSessionConfigNotifyDnEnable, 1368 ancpAnSessionConfigNotifyUpEnable 1369 } 1370 STATUS current 1371 DESCRIPTION 1372 "These objects apply to the configuration of ANCP 1373 sessions in access nodes." 1374 ::= { ancpAnGroups 1 } 1376 ancpAnRelatedInterfaceGroup OBJECT-GROUP 1377 OBJECTS { 1378 ancpAnSessionConfigRelatedInterface 1379 } 1380 STATUS current 1381 DESCRIPTION 1382 "This object contains the ifIndex of an interface defined 1383 in IF-MIB. If an ANCP session must be associated with an 1384 IP interface, then this group must be supported. This 1385 group also must be supported together with the 1386 ancpAnRelatedEntityGroup in case the ANCP session is to 1387 be associated with an ATM PVC." 1388 ::= { ancpAnGroups 2 } 1390 ancpAnRelatedEntityGroup OBJECT-GROUP 1391 OBJECTS { 1392 ancpAnSessionConfigRelatedEntity 1393 } 1394 STATUS current 1395 DESCRIPTION 1396 "This object contains the name of an object instance 1397 uniquely identifying a lower layer entity. If an ANCP 1398 session must be associated with an ATM PVC, then this 1399 group together with ancpAnRelatedInterfaceGroup must be 1400 supported." 1401 ::= { ancpAnGroups 3 } 1403 ancpAnRelatedVlanGroup OBJECT-GROUP 1404 OBJECTS { 1405 ancpAnSessionConfigSvid, 1406 ancpAnSessionConfigSPrio, 1407 ancpAnSessionConfigCvid, 1408 ancpAnSessionConfigCPrio 1409 } 1410 STATUS current 1411 DESCRIPTION 1412 "These objects contains all VLAN related configuration 1413 when the ANCP session is associated with a particular 1414 VLAN. If an ANCP session must be associated with a 1415 VLAN (or VLAN stack), then this group must be 1416 supported." 1417 ::= { ancpAnGroups 4 } 1419 ancpAnCurrentGroup OBJECT-GROUP 1420 OBJECTS { 1421 ancpAnCurrentSessionState, 1422 ancpAnCurrentSessionAncpVersion, 1423 ancpAnCurrentSessionAnName, 1424 ancpAnCurrentSessionNasName, 1425 ancpAnCurrentSessionAnIpAddressType, 1426 ancpAnCurrentSessionAnIpAddress, 1427 ancpAnCurrentSessionAnInstance, 1428 ancpAnCurrentSessionNasInstance, 1429 ancpAnCurrentSessionCapabilities, 1430 ancpAnCurrentSessionStartUptime, 1431 ancpAnCurrentSessionDiscontinuityTime, 1432 ancpAnCurrentSessionStatSentMessages, 1433 ancpAnCurrentSessionStatReceivedValidMessages, 1434 ancpAnCurrentSessionStatDiscardedMessages, 1435 ancpAnCurrentSessionStatReceivedAdjSyn, 1436 ancpAnCurrentSessionStatReceivedAdjSynack, 1437 ancpAnCurrentSessionStatReceivedAdjAck, 1438 ancpAnCurrentSessionStatReceivedAdjRstack, 1439 ancpAnCurrentSessionStatTransmittedAdjSyn, 1440 ancpAnCurrentSessionStatTransmittedAdjSynack, 1441 ancpAnCurrentSessionStatTransmittedAdjAck, 1442 ancpAnCurrentSessionStatTransmittedAdjRstack 1443 } 1444 STATUS current 1445 DESCRIPTION 1446 "These objects show the operational state of all ANCP 1447 sessions configured in the access node." 1448 ::= { ancpAnGroups 5 } 1450 ancpAnInterfaceGroup OBJECT-GROUP 1451 OBJECTS { 1452 ancpAnPartitionsUsed, 1453 ancpAnInterfaceConfigPartitionId 1454 } 1455 STATUS current 1456 DESCRIPTION 1457 "These objects are used to assign user facing interface 1458 to partitions." 1459 ::= { ancpAnGroups 6 } 1461 ancpAnNotificationsGroup NOTIFICATION-GROUP 1462 NOTIFICATIONS { 1463 ancpAnSessionDown, 1464 ancpAnSessionUp 1465 } 1466 STATUS current 1467 DESCRIPTION 1468 "These objects are used to enable or disable the 1469 generation of notifications by the access node about 1470 changes in the state of ANCP sessions." 1471 ::= { ancpAnGroups 7 } 1473 END 1475 8. Security Considerations 1477 There are a number of management objects defined in this MIB module 1478 with a MAX-ACCESS clause of read-write and/or read-create. Such 1479 objects may be considered sensitive or vulnerable in some network 1480 environments. The support for SET operations in a non-secure 1481 environment without proper protection can have a negative effect on 1482 network operations. These are the tables and objects and their 1483 sensitivity/vulnerability: 1485 o ancpAnPartitionsUsed 1487 This scalar object supports SET operations. Unauthorized changes 1488 to this object could result in a wrong interpretation of 1489 ancpAnSessionConfigPartitionId attribute of all sessions, as if 1490 all sessions use partition id zero, or to actually disabling the 1491 use of partitions in the system. 1493 o ancpAnSessionConfigTable 1495 The table consists of the following objects that support SET 1496 operations: 1498 * ancpAnSessionConfigRowStatus 1500 * ancpAnSessionConfigAncpVersion 1502 * ancpAnSessionConfigEncapsulationType 1504 * ancpAnSessionConfigCapabilities 1506 * ancpAnSessionConfigAliveTimer 1508 * ancpAnSessionConfigPortReportShaper 1510 * ancpAnSessionConfigAggregateReportShaper 1512 * ancpAnSessionConfigTransportRetryTimer 1514 * ancpAnSessionConfigAncpRetryTimer 1516 * ancpAnSessionConfigAnName 1518 * ancpAnSessionConfigPartitionId 1520 * ancpAnSessionConfigWindowSize 1522 * ancpAnSessionConfigRelatedInterface 1523 * ancpAnSessionConfigRelatedEntity 1525 * ancpAnSessionConfigSvid 1527 * ancpAnSessionConfigSPrio 1529 * ancpAnSessionConfigCvid 1531 * ancpAnSessionConfigCPrio 1533 * ancpAnSessionConfigNasIpAddressType 1535 * ancpAnSessionConfigNasIpAddress 1537 * ancpAnSessionConfigEncapPortNumber 1539 * ancpAnSessionConfigNotifyDnEnable 1541 * ancpAnSessionConfigNotifyUpEnable 1543 Unauthorized changes to ancpAnSessionConfigRowStatus could result 1544 in session being created or brought into service prematurely; or 1545 could result in session being inadvertently deleted or taken out 1546 of service. 1548 Unauthorized changes to ancpAnSessionConfigAncpVersion could have 1549 an adverse operational effect by limiting the ANCP version to be 1550 used in the context of this session or enabling an ANCP version 1551 number that is actually unsupported by the access node. 1553 Unauthorized changes to ancpAnSessionConfigEncapsulationType could 1554 have an adverse operational effect by configuring the session to 1555 use an undesired or even unsupported protocol. 1557 Unauthorized changes to ancpAnSessionConfigCapabilities could have 1558 an adverse operational effect by disabling certain ANCP 1559 capabilities that the operator assumed that are enabled, or enable 1560 a capability that the operator would not like to activate. 1562 Unauthorized changes to ancpAnSessionConfigAliveTimer could have 1563 an adverse operational effect by increasing the frequency of 1564 adjacency protocol messages generated by the access node and 1565 leading to an overload of such messages. Decreasing the frequency 1566 of such messages may harm the synchronization between the access 1567 node and the NAS. 1569 Unauthorized changes to ancpAnSessionConfigPortReportShaper or 1570 ancpAnSessionConfigAggregateReportShaper could have an adverse 1571 operational effect by increasing the frequency of Event Report 1572 messages generated by the access node and leading to an overload 1573 of such messages. Decreasing the frequency of such messages may 1574 delay the responsiveness of the system to events associated with 1575 one or more ports. 1577 Unauthorized changes to ancpAnSessionConfigTransportRetryTimer 1578 could have an adverse operational effect by increasing the 1579 frequency of transport connection setup attempts initiated by the 1580 access node or even unexpectedly enabling the access node to 1581 initiate the transport connection setup when that supposed to be 1582 disabled. Alternatively, when the operator basically planned 1583 transport connection setup attempts by the access node 1584 unauthorized changes to the attribute may cause unexpected low 1585 frequency of such attempts or unexpectedly disable those attempts. 1587 Unauthorized changes to ancpAnSessionConfigAncpRetryTimer could 1588 have an adverse operational effect by increasing the frequency of 1589 ANCP connection setup attempts initiated by the access node or 1590 even unexpectedly enabling the access node to initiate the ANCP 1591 connection setup when that supposed to be disabled. 1592 Alternatively, when the operator basically planned ANCP connection 1593 setup attempts by the access node unauthorized changes to the 1594 attribute may cause unexpected low frequency of such attempts or 1595 unexpectedly disable those attempts. 1597 Unauthorized changes to ancpAnSessionConfigAnName could confuse 1598 the NAS, e.g., by detecting the same name from multiple access 1599 nodes. This may also override the operator's will to allow/avoid 1600 the access node to autonomously determine its name. 1602 Unauthorized changes to ancpAnSessionConfigPartitionId could mean 1603 that partitions are used when actually they are not, or vice 1604 versa. It could also at least specify a different partition ID 1605 than the one actually associated with the session. 1607 Unauthorized changes to ancpAnSessionConfigWindowSize are not 1608 directly harmful. However, if the controller adopts the suggested 1609 wrong window size it may either cause the controller to send too 1610 many messages in a window or unnecessarily limit itself and that 1611 could reduce the system performance. 1613 Unauthorized changes to ancpAnSessionConfigRelatedInterface and/or 1614 ancpAnSessionConfigRelatedEntity and/or ancpAnSessionConfigSvid 1615 and/or ancpAnSessionConfigCvid can result in the ANCP packets to 1616 be sent out on the wrong interface. This means that the ANCP 1617 packets to establish a session can be received by someone who is 1618 not the intended receiver. 1620 Unauthorized changes to ancpAnSessionConfigSPrio and/or 1621 ancpAnSessionConfigCPrio may give the ANCP packets a lower or a 1622 higher priority in the network compared to other packets. 1623 Lowering the priority might result in a reduced timely behavior of 1624 the ANCP session, and increasing the priority may result in 1625 impacting other traffic in the network than ANCP. 1627 Unauthorized changes to ancpAnSessionConfigNasIpAddressType and/or 1628 ancpAnSessionConfigNasIpAddress and/or 1629 ancpAnSessionConfigEncapPortNumber could produce a wrong address 1630 type (interpretation) and/or IP address for the NAS and/or specify 1631 a wrong transport protocol port number for the session, 1632 respectively. 1634 Unauthorized changes to ancpAnSessionConfigNotifyDnEnable could 1635 lead (if the change was setting the attribute to 'enable') to 1636 overload of notification messages at the SNMP manager in case 1637 multiple sessions leave the 'estab' state simultaneously. If the 1638 change was setting the attribute to 'disable' it could lead to 1639 hiding the actual session state from the SNMP manager. 1641 Unauthorized changes to ancpAnSessionConfigNotifyUpEnable could 1642 lead (if the change was setting the attribute to 'enable') to 1643 overload of notification messages at the SNMP manager in case 1644 multiple sessions enter the 'estab' state simultaneously. If the 1645 change was setting the attribute to 'disable' it could lead to 1646 hiding the actual session state from the SNMP manager. 1648 o ancpAnInterfaceConfigTable 1650 The table consists of the following objects that support SET 1651 operations: 1653 * ancpAnInterfaceConfigPartitionId 1655 Unauthorized changes to ancpAnInterfaceConfigPartitionId could 1656 result in a wrong association between the interface and a 1657 partition. It could result in not being able to manage the 1658 interface from the correct session and/or to exposing the 1659 interface to a wrong NAS. 1661 Some of the readable objects in this MIB module (i.e., objects with a 1662 MAX-ACCESS other than not-accessible) may be considered sensitive or 1663 vulnerable in some network environments. It is thus important to 1664 control even GET and/or NOTIFY access to these objects and possibly 1665 to even encrypt the values of these objects when sending them over 1666 the network via SNMP. This is the table and these are the objects 1667 and their sensitivity/vulnerability: 1669 o ancpAnCurrentSessionTable 1671 Access to these objects would allow an intruder to obtain 1672 information about which vendor's equipment is in use on the 1673 network. Further, such information is considered sensitive in 1674 many environments for competitive reasons. 1676 * ancpAnCurrentSessionState 1678 * ancpAnCurrentSessionAncpVersion 1680 * ancpAnCurrentSessionAnName 1682 * ancpAnCurrentSessionNasName 1684 * ancpAnCurrentSessionAnIpAddressType 1686 * ancpAnCurrentSessionAnIpAddress 1688 * ancpAnCurrentSessionAnInstance 1690 * ancpAnCurrentSessionNasInstance 1692 * ancpAnCurrentSessionCapabilities 1694 * ancpAnCurrentSessionStartUptime 1696 * ancpAnCurrentSessionDiscontinuityTime 1698 * ancpAnCurrentSessionStatSentMessages 1700 * ancpAnCurrentSessionStatReceivedValidMessages 1702 * ancpAnCurrentSessionStatDiscardedMessages 1704 * ancpAnCurrentSessionStatReceivedAdjSyn 1705 * ancpAnCurrentSessionStatReceivedAdjSynack 1707 * ancpAnCurrentSessionStatReceivedAdjAck 1709 * ancpAnCurrentSessionStatReceivedAdjRstack 1711 * ancpAnCurrentSessionStatTransmittedAdjSyn 1713 * ancpAnCurrentSessionStatTransmittedAdjSynack 1715 * ancpAnCurrentSessionStatTransmittedAdjAck 1717 * ancpAnCurrentSessionStatTransmittedAdjRstack 1719 SNMP versions prior to SNMPv3 did not include adequate security. 1720 Even if the network itself is secure (for example by using IPSec), 1721 even then, there is no control as to who on the secure network is 1722 allowed to access and GET/SET (read/change/create/delete) the objects 1723 in this MIB module. 1725 It is RECOMMENDED that implementers consider the security features as 1726 provided by the SNMPv3 framework (see [RFC3410], Section 8), 1727 including full support for the SNMPv3 cryptographic mechanisms (for 1728 authentication and privacy). 1730 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1731 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1732 enable cryptographic security. It is then a customer/operator 1733 responsibility to ensure that the SNMP entity giving access to an 1734 instance of this MIB module is properly configured to give access to 1735 the objects only to those principals (users) that have legitimate 1736 rights to indeed GET or SET (change/create/delete) them. 1738 9. IANA considerations 1740 IANA is requested to assign two OID's xxx under mib-2 for ANCP-TC-MIB 1741 and ANCP-AN-MIB. 1743 10. Acknowledgements 1745 The authors would like to thank Paul Reynders, Bert Wijnen and Tom 1746 Taylor for their feedback. 1748 11. References 1749 11.1. Normative References 1751 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1752 Requirement Levels", BCP 14, RFC 2119, March 1997. 1754 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1755 Schoenwaelder, Ed., "Structure of Management Information 1756 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1758 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1759 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1760 58, RFC 2579, April 1999. 1762 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1763 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1764 April 1999. 1766 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1767 MIB", RFC 2863, June 2000. 1769 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1770 Schoenwaelder, "Textual Conventions for Internet Network 1771 Addresses", RFC 4001, February 2005. 1773 [RFC4363] Levi, D. and D. Harrington, "Definitions of Managed 1774 Objects for Bridges with Traffic Classes, Multicast 1775 Filtering, and Virtual LAN Extensions", RFC 4363, January 1776 2006. 1778 [RFC4502] Waldbusser, S., "Remote Network Monitoring Management 1779 Information Base Version 2", RFC 4502, May 2006. 1781 [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. 1782 Taylor, "Protocol for Access Node Control Mechanism in 1783 Broadband Networks", RFC 6320, October 2011. 1785 11.2. Informative References 1787 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1788 "Introduction and Applicability Statements for Internet- 1789 Standard Management Framework", RFC 3410, December 2002. 1791 [RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. 1792 Wadhwa, "Framework and Requirements for an Access Node 1793 Control Mechanism in Broadband Multi-Service Networks", 1794 RFC 5851, May 2010. 1796 Authors' Addresses 1798 Stefaan De Cnodder 1799 Alcatel-Lucent 1800 Copernicuslaan 50 1801 B-2018 Antwerp 1802 Belgium 1804 Phone: +32 3 240 85 15 1805 Email: stefaan.de_cnodder@alcatel-lucent.com 1807 Moti Morgenstern 1808 ECI Telecom Ltd. 1809 30 Hasivim St. 1810 Petach Tikva 4959388 1811 Israel 1813 Phone: +972 3 926 6258 1814 Fax: +972 3 928 7322 1815 Email: moti.Morgenstern@ecitele.com