idnits 2.17.1 draft-ietf-adslmib-gbond-eth-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1022. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1033. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1040. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1046. 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 13 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (November 19, 2007) is 6003 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) == Missing Reference: 'RFC3705' is mentioned on line 161, but not defined == Missing Reference: 'RFCXXXX' is mentioned on line 240, but not defined == Unused Reference: 'IANAifType-MIB' is defined on line 970, but no explicit reference was found in the text == Unused Reference: 'RFC4836' is defined on line 979, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'G.998.2' ** Downref: Normative reference to an Informational RFC: RFC 3410 -- Possible downref: Non-RFC (?) normative reference: ref. 'WT-159' == Outdated reference: A later version (-11) exists of draft-ietf-adslmib-gbond-mib-01 Summary: 2 errors (**), 0 flaws (~~), 8 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Intended status: Standards Track M. Morgenstern 5 Expires: May 22, 2008 ECI Telecom 6 November 19, 2007 8 Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB 9 draft-ietf-adslmib-gbond-eth-mib-01.txt 11 Status of This Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on May 22, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 This document defines Management Information Base (MIB) module for 43 use with network management protocols in TCP/IP based internets. 44 This document proposes an extension to the G.Bond MIB module with a 45 set of objects for managing Ethernet-based multi-pair bonded xDSL 46 interfaces, defined in ITU-T recommendation G.998.2. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 3 53 4. Relation to other MIB modules . . . . . . . . . . . . . . . . 3 54 4.1. Relationship to Interfaces Group MIB module . . . . . . . 4 55 4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4 56 4.3. Relationship to EFM Copper MIB module . . . . . . . . . . 4 57 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 5.1.1. TODO/Open Issues . . . . . . . . . . . . . . . . . . . 4 60 5.2. Mapping of IEEE 802.3 Managed Objects . . . . . . . . . . 5 61 5.3. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 5 62 6. G.Bond/Ethernet MIB Definitions . . . . . . . . . . . . . . . 6 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 64 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 65 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 66 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 67 10.1. Normative References . . . . . . . . . . . . . . . . . . . 20 68 10.2. Informative References . . . . . . . . . . . . . . . . . . 21 70 1. Introduction 72 The Ethernet-based xDSL Multi-Pair Bonding, a.k.a. G.Bond/Ethernet, 73 is specified in ITU-T G.998.2 recommendation [G.998.2], which defines 74 a method for bonding (or aggregating) of multiple xDSL lines into a 75 single bi-directional logical link, carrying an Ethernet traffic. 77 The MIB module, defined in this document, provides G.Bond/Ethernet 78 specific objects for the management of G.998.2 bonded interfaces, 79 extending the common bonding objects specified in GBOND-MIB 80 [I-D.ietf-adslmib-gbond-mib] module. 82 2. The Internet-Standard Management Framework 84 For a detailed overview of the documents that describe the current 85 Internet-Standard Management Framework, please refer to section 7 of 86 RFC 3410 [RFC3410]. 88 Managed objects are accessed via a virtual information store, termed 89 the Management Information Base or MIB. MIB objects are generally 90 accessed through the Simple Network Management Protocol (SNMP). 91 Objects in the MIB are defined using the mechanisms defined in the 92 Structure of Management Information (SMI). This memo specifies a MIB 93 module that is compliant to the SMIv2, which is described in STD 58, 94 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 95 [RFC2580]. 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 RFC 2119 [RFC2119]. 101 3. The DSL Forum Management Framework for xDSL Bonding 103 This document makes use of the DSL Forum technical report Management 104 Framework for xDSL Bonding [WT-159], defining a management model and 105 a hierarchy of management objects for the bonded xDSL interfaces. 107 4. Relation to other MIB modules 109 This section outlines the relationship of the MIB modules defined in 110 this document with other MIB modules described in the relevant RFCs. 111 Specifically, the following MIB modules are discussed: Interfaces 112 Group MIB (IF-MIB), G.Bond MIB (GBOND-MIB), and EFM Copper MIB (EFM- 113 CU-MIB). 115 4.1. Relationship to Interfaces Group MIB module 117 A G.Bond/Ethernet port is a private case of a Bonded multi-pair xDSL 118 interface and as such is managed using generic interface management 119 objects defined in the IF-MIB [RFC2863]. In particular, an interface 120 index (ifIndex) is used to index instances of G.Bond/Ethernet ports 121 and channels in a managed system. 123 4.2. Relationship to G.Bond MIB module 125 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management 126 objects common for all Bonded multi-pair xDSL interfaces. In 127 particular it describes the bonding management, port and channel 128 configuration, initialization sequence etc. 130 Both GBOND-MIB and GBOND-ETH-MIB modules are REQUIRED to manage a 131 G.Bond/Ethernet port. 133 4.3. Relationship to EFM Copper MIB module 135 EFM-CU-MIB [RFC5066] module defines objects for managing Ethernet in 136 the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, 137 defined in IEEE Std 802.3-2005 [802.3]. These interfaces are based 138 on Single-pair High-speed Digital Subscriber Line (SHDSL) [G.991.2] 139 and Very High speed Digital Subscriber Line (VDSL) [G.993.1] 140 technology respectively, and can be optionally aggregated (bonded). 142 ITU-T G.998.2 specification extends the IEEE 802.3 Clause 61 bonding 143 to work over any xDSL technology, providing the ability to bond 144 individual channels as well as physical lines. 146 EFM-CU-MIB can be used to manage all aspects of the EFMCu interfaces, 147 including the management of SHDSL/VDSL lines. GBOND-MIB and GBOND- 148 ETH-MIB modules provide management objects only for the bonding part, 149 leaving the management of the individual xDSL interfaces (lines/ 150 channels) to the respective xDSL MIB modules. 152 5. MIB Structure 154 5.1. Overview 156 _EdNote: TBC... _ 158 5.1.1. TODO/Open Issues 160 o Add Peformance Monitoring counters - reuse HC-PerfHist-TC-MIB 161 [RFC3705] 163 o Add support for ITU-T draft BACP (frame-based discovery and pair 164 management) 166 5.2. Mapping of IEEE 802.3 Managed Objects 168 This section contains the mapping between relevant managed objects 169 (attributes) defined in [802.3] and managed objects defined in this 170 document. 172 +----------------------+---------------------------+ 173 | 802.3 Managed Object | Corresponding SNMP Object | 174 +----------------------+---------------------------+ 175 | oGroup | | 176 +----------------------+---------------------------+ 177 +----------------------+---------------------------+ 178 | TBC... | TBC... | 179 +----------------------+---------------------------+ 181 Table 1: Mapping of 802.3 Managed Objects 183 _EdNote: Finish the table and remove TBC... _ 185 5.3. Mapping of DSL Forum WT-159 Managed Objects 187 This section contains the mapping between relevant managed objects 188 (attributes) defined in [WT-159] and managed objects defined in this 189 document. 191 +---------------------------------+-----------------------------+ 192 | WT-159 Managed Object | Corresponding SNMP Object | 193 +---------------------------------+-----------------------------+ 194 | oBondEth | | 195 +---------------------------------+-----------------------------+ 196 | aEthTcAdminType | gBondEthTcAdminType | 197 +---------------------------------+-----------------------------+ 198 | aEthTcOperType | gBondEthTcOperType | 199 +---------------------------------+-----------------------------+ 200 | aEthTcTypesSupported | gBondEthTcTypesSupported | 201 +---------------------------------+-----------------------------+ 202 | aEthRxErrors | gBondEthInErrors | 203 +---------------------------------+-----------------------------+ 204 | aEthRxSmallFragments | gBondEthInSmallFragments | 205 +---------------------------------+-----------------------------+ 206 | aEthRxLargeFragments | gBondEthInLargeFragments | 207 +---------------------------------+-----------------------------+ 208 | aEthRxBadFragments | gBondEthInBadFragments | 209 +---------------------------------+-----------------------------+ 210 | aEthRxLostFragments | gBondEthInLostFragments | 211 | aEthRxLostStarts | gBondEthInLostStarts | 212 +---------------------------------+-----------------------------+ 213 | aEthRxLostEnds | gBondEthInLostEnds | 214 +---------------------------------+-----------------------------+ 215 | aEthRxOverflows | gBondEthInOverflows | 216 +---------------------------------+-----------------------------+ 217 | oChannel | | 218 +---------------------------------+-----------------------------+ 219 | aChannelPtmTcRxCodingViolations | gBondEthBceTcInCodingErrors | 220 +---------------------------------+-----------------------------+ 221 | aChannelPtmTcRxCrcErrors | gBondEthBceTcInCrcErrors | 222 +---------------------------------+-----------------------------+ 224 Table 2: Mapping of WT-159 Managed Objects 226 6. G.Bond/Ethernet MIB Definitions 228 GBOND-ETH-MIB DEFINITIONS ::= BEGIN 230 IMPORTS 231 MODULE-IDENTITY, OBJECT-TYPE, Counter32 232 FROM SNMPv2-SMI -- [RFC2578] 233 TEXTUAL-CONVENTION 234 FROM SNMPv2-TC -- [RFC2579] 235 MODULE-COMPLIANCE, OBJECT-GROUP 236 FROM SNMPv2-CONF -- [RFC2580] 237 ifIndex 238 FROM IF-MIB -- [RFC2863] 239 -- gBondMIB 240 -- FROM GBOND-MIB -- [RFCXXXX] 241 -- EdNote: Replace XXXX with the actual RFC number & 242 -- remove this note 243 ; 245 gBondEthMIB MODULE-IDENTITY 246 LAST-UPDATED "200711190000Z" -- November 19, 2007 247 ORGANIZATION "IETF ADSL MIB Working Group" 248 CONTACT-INFO 249 "WG charter: 250 http://www.ietf.org/html.charters/adslmib-charter.html 252 Mailing Lists: 253 General Discussion: adslmib@ietf.org 254 To Subscribe: adslmib-request@ietf.org 255 In Body: subscribe your_email_address 257 Chair: Menachem Dodge 258 Postal: ECI Telecom, Ltd. 260 30 Hasivim St., 261 Petach-Tikva 49517 262 Israel 263 Phone: +972-3-926-8421 264 EMail: menachem.dodge@ecitele.com 266 Editor: Edward Beili 267 Postal: Actelis Networks, Inc. 268 25 Bazel St., P.O.B. 10173 269 Petach-Tikva 10173 270 Israel 271 Phone: +972-3-924-3491 272 EMail: edward.beili@actelis.com 274 Editor: Moti Morgenstern 275 Postal: ECI Telecom 276 30 Hasivim St. 277 Petach-Tikva 49517 278 Israel 279 Phone: +972-3-926-6258 280 EMail: moti.morgenstern@ecitele.com" 282 DESCRIPTION 283 "The objects in this MIB module are used to manage the 284 Ethernet-based multi-pair bonded xDSL Interfaces, defined in 285 ITU-T recommendation G.998.2 (G.Bond/Ethernet). 287 This MIB module MUST be used in conjunction with GBOND-MIB 288 module, common to all G.Bond technologies. 290 The following references are used throughout this MIB module: 292 [G.998.2] refers to: 293 ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair 294 bonding', January 2005. 296 [802.3] refers to: 297 IEEE Std 802.3-2005: 'IEEE Standard for Information 298 technology - Telecommunications and information exchange 299 between systems - Local and metropolitan area networks - 300 Specific requirements - 301 Part 3: Carrier Sense Multiple Access with Collision 302 Detection (CSMA/CD) Access Method and Physical Layer 303 Specifications', December 2005. 305 [WT-159] refers to: 306 DSL Forum Technical Report: 'Management Framework for xDSL 307 Bonding', May 2007. 309 Naming Conventions: 310 BCE - Bonding Channel Entity 311 CO - Central Office 312 CPE - Customer Premises Equipment 313 GBS - Generic Bonding Sublayer 314 HDLC - High-level Data Link Control 315 PTM-TC - Packet Transfer Mode Transmission Convergence 316 (sub-layer) 317 SNR - Signal to Noise Ratio 318 TC - Transmission Convergence (sub-layer) 320 Copyright (C) The Internet Society (2007). This version of this 321 MIB module is part of RFC XXXX; see the RFC itself for full 322 legal notices." 324 REVISION "200711190000Z" -- November 19, 2007 325 DESCRIPTION "Initial version, published as RFC YYYY." 327 -- EdNote: Replace YYYY with the actual RFC number & 328 -- remove this note 330 ::= { mib-2 ZZZ } 332 -- EdNote: Replace ZZZ with a real OID once it is 333 -- allocated & remove this note. 335 -- Sections of the module 336 -- Structured as recommended by [RFC4181], Appendix D 338 gBondEthObjects OBJECT IDENTIFIER ::= { gBondEthMIB 1 } 340 gBondEthConformance OBJECT IDENTIFIER ::= { gBondEthMIB 2 } 342 -- Groups in the module 344 gBondEthPort OBJECT IDENTIFIER ::= { gBondEthObjects 1 } 346 gBondEthBce OBJECT IDENTIFIER ::= { gBondEthObjects 2 } 348 -- Textual Conventions 350 GBondEthPtmTcType ::= TEXTUAL-CONVENTION 351 STATUS current 352 DESCRIPTION 353 "This textual convention represents possible PTM-TC types in 354 G.bond/Eth ports. The following values are defined: 355 tc6465 - 64/65-octet encapsulation, as defined in 356 [802.3] Clause 61.3.3 358 tcHDLC - HDLC encapsulation, as defined in [G.998.2] 359 Annex B" 360 SYNTAX INTEGER { 361 tc6465(1), 362 tcHDLC(2) 363 } 365 -- GBS Notifications group 366 -- empty -- 368 -- GBS group 370 gBondEthPortConfTable OBJECT-TYPE 371 SYNTAX SEQUENCE OF GBondEthPortConfEntry 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "Table for Configuration of G.Bond/Eth GBS ports. Entries in 376 this table MUST be maintained in a persistent manner" 377 ::= { gBondEthPort 1 } 379 gBondEthPortConfEntry OBJECT-TYPE 380 SYNTAX GBondEthPortConfEntry 381 MAX-ACCESS not-accessible 382 STATUS current 383 DESCRIPTION 384 "An entry in the G.Bond/Eth Port Configuration table. 385 Each entry represents an G.Bond Ethernet port indexed by the 386 ifIndex. 387 Note that an G.Bond/Eth GBS port runs on top of a single 388 or multiple BCE port(s), which are also indexed by ifIndex." 389 INDEX { ifIndex } 390 ::= { gBondEthPortConfTable 1 } 392 GBondEthPortConfEntry ::= 393 SEQUENCE { 394 gBondEthTcAdminType GBondEthPtmTcType 395 } 397 gBondEthTcAdminType OBJECT-TYPE 398 SYNTAX GBondEthPtmTcType 399 MAX-ACCESS read-write 400 STATUS current 401 DESCRIPTION 402 "Administrative (desired) PTM-TC encapsulation type of 403 G.Bond/Eth port (GBS). 404 Possible values are: 405 tc6465(1) - 64/65-octet encapsulation 406 tcHDLC(2) - HDLC encapsulation 407 Attempts to set a port to a non-supported PTM-TC encapsulation 408 type (see gBondEthTcTypesSupported) SHALL be rejected. 410 Changing gBondEthTcAdminType is a traffic disruptive 411 operation and as such SHALL be done when the link is Down. 412 Attempts to cange this object SHALL be rejected if the link 413 is Up or Initializing. 415 This object maps to the WT-159 attribute aEthTcAdminType. 417 This object MUST be maintained in a persistent manner." 418 REFERENCE 419 "[WT-159] 5.5.3.1" 420 ::= { gBondEthPortConfEntry 1 } 422 gBondEthPortCapabilityTable OBJECT-TYPE 423 SYNTAX SEQUENCE OF GBondEthPortCapabilityEntry 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "Table for Capabilities of G.Bond/Eth Ports. Entries in this 428 table MUST be maintained in a persistent manner" 429 ::= { gBondEthPort 2 } 431 gBondEthPortCapabilityEntry OBJECT-TYPE 432 SYNTAX GBondEthPortCapabilityEntry 433 MAX-ACCESS not-accessible 434 STATUS current 435 DESCRIPTION 436 "An entry in the G.Bond/Eth Port Capability table. 437 Each entry represents an G.Bond port indexed by the ifIndex. 438 Note that a G.Bond GBS port runs on top of a single 439 or multiple BCE port(s), which are also indexed by ifIndex." 440 INDEX { ifIndex } 441 ::= { gBondEthPortCapabilityTable 1 } 443 GBondEthPortCapabilityEntry ::= 444 SEQUENCE { 445 gBondEthTcTypesSupported BITS 446 } 448 gBondEthTcTypesSupported OBJECT-TYPE 449 SYNTAX BITS { 450 tc6465(0), 451 tcHDLC(1) 452 } 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "PTM-TC Encapsulation types supported by the G.Bond/Eth port. 457 This is a bitmap of possible encapsulation types. The various 458 bit positions are: 459 tc6465 - GBS is capable of 64/65-octet encapsulation 460 tcHDLC - GBS is capable of HDLC encapsulation 462 A desired encapsulation is determined by 463 gBondEthTcAdminType, while gBondEthTcOperType reflects the 464 current operating mode. 466 This object maps to the WT-159 attribute 467 aEthTcTypesSupported." 468 REFERENCE 469 "[WT-159] 5.5.3.3" 470 ::= { gBondEthPortCapabilityEntry 1 } 472 gBondEthPortStatusTable OBJECT-TYPE 473 SYNTAX SEQUENCE OF GBondEthPortStatusEntry 474 MAX-ACCESS not-accessible 475 STATUS current 476 DESCRIPTION 477 "This table provides overall status information of G.Bond 478 ports, complementing the generic status information from the 479 ifTable of IF-MIB. Additional status information about 480 connected BCEs is available from the relevant line MIBs 482 This table contains live data from the equipment. As such, 483 it is NOT persistent." 484 ::= { gBondEthPort 3 } 486 gBondEthPortStatusEntry OBJECT-TYPE 487 SYNTAX GBondEthPortStatusEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "An entry in the G.Bond/Eth Port Status table. 492 Each entry represents an G.Bond/Eth port indexed by the 493 ifIndex. 494 Note that an G.Bond GBS port runs on top of a single 495 or multiple BCE port(s), which are also indexed by ifIndex." 496 INDEX { ifIndex } 497 ::= { gBondEthPortStatusTable 1 } 499 GBondEthPortStatusEntry ::= 500 SEQUENCE { 501 gBondEthTcOperType GBondEthPtmTcType, 502 gBondEthInErrors Counter32, 503 gBondEthInSmallFragments Counter32, 504 gBondEthInLargeFragments Counter32, 505 gBondEthInBadFragments Counter32, 506 gBondEthInLostFragments Counter32, 507 gBondEthInLostStarts Counter32, 508 gBondEthInLostEnds Counter32, 509 gBondEthInOverflows Counter32 510 } 512 gBondEthTcOperType OBJECT-TYPE 513 SYNTAX GBondEthPtmTcType 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "Current operational encapsulation type of the G.Bond/Eth 518 port. 519 Possible values are: 520 tc6465(1) - GBS uses 64/65-octet encapsulation 521 tcHDLC(2) - GBS uses HDLC encapsulation 523 The operational PTM-TC encapsulation type can be configured 524 via gBondEthTcAdminType variable. 526 This objects maps to the WT-159 aEthTcOperType." 527 REFERENCE 528 "[WT-159] 5.5.3.2" 529 ::= { gBondEthPortStatusEntry 1 } 531 gBondEthInErrors OBJECT-TYPE 532 SYNTAX Counter32 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "A number of fragments that have been received across the 537 gamma interface and discarded. 539 This object maps to the WT-159 attribute aEthRxErrors. 541 Discontinuities in the value of this counter can occur at 542 re-initialization of the management system, and at other times 543 as indicated by the value of ifCounterDiscontinuityTime, 544 defined in IF-MIB." 545 REFERENCE 546 "[WT-159] 5.5.3.4" 547 ::= { gBondEthPortStatusEntry 2 } 549 gBondEthInSmallFragments OBJECT-TYPE 550 SYNTAX Counter32 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "A number of fragments smaller than minFragmentSize 555 (64 Bytes), that have been received across the gamma 556 interface and discarded. 558 This object maps to the WT-159 attribute aEthRxSmallFragments. 560 Discontinuities in the value of this counter can occur at 561 re-initialization of the management system, and at other times 562 as indicated by the value of ifCounterDiscontinuityTime, 563 defined in IF-MIB." 564 REFERENCE 565 "[WT-159] 5.5.3.5" 566 ::= { gBondEthPortStatusEntry 3 } 568 gBondEthInLargeFragments OBJECT-TYPE 569 SYNTAX Counter32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "A number of fragments larger than maxFragmentSize 574 (512 Bytes), which have been received across the gamma 575 interface and discarded. 577 This object maps to the WT-159 attribute aEthRxLargeFragments. 579 Discontinuities in the value of this counter can occur at 580 re-initialization of the management system, and at other times 581 as indicated by the value of ifCounterDiscontinuityTime, 582 defined in IF-MIB." 583 REFERENCE 584 "[WT-159] 5.5.3.6" 585 ::= { gBondEthPortStatusEntry 4 } 587 gBondEthInBadFragments OBJECT-TYPE 588 SYNTAX Counter32 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "A number of fragments which do not fit into the sequence 593 expected by the frame assembly function, that have been 594 received across the gamma interface and discarded (the 595 frame buffer is flushed to the next valid frame start). 597 This object maps to the WT-159 attribute aEthRxBadFragments. 599 Discontinuities in the value of this counter can occur at 600 re-initialization of the management system, and at other times 601 as indicated by the value of ifCounterDiscontinuityTime, 602 defined in IF-MIB." 603 REFERENCE 604 "[WT-159] 5.5.3.7" 605 ::= { gBondEthPortStatusEntry 5 } 607 gBondEthInLostFragments OBJECT-TYPE 608 SYNTAX Counter32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "A number of gaps in the sequence of fragments, which have 613 been received across the gamma interface (the frame buffer is 614 flushed to the next valid frame start, when fragment/fragments 615 expected by the frame assembly function is/are not received). 617 This object maps to the WT-159 attribute aEthRxLostFragments. 619 Discontinuities in the value of this counter can occur at 620 re-initialization of the management system, and at other times 621 as indicated by the value of ifCounterDiscontinuityTime, 622 defined in IF-MIB." 623 REFERENCE 624 "[WT-159] 5.5.3.8" 625 ::= { gBondEthPortStatusEntry 6 } 627 gBondEthInLostStarts OBJECT-TYPE 628 SYNTAX Counter32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "A number of missing StartOfPacket indicators expected by the 633 frame assembly function. 635 This object maps to the WT-159 attribute aEthRxLostStarts. 637 Discontinuities in the value of this counter can occur at 638 re-initialization of the management system, and at other times 639 as indicated by the value of ifCounterDiscontinuityTime, 640 defined in IF-MIB." 641 REFERENCE 642 "[WT-159] 5.5.3.9" 643 ::= { gBondEthPortStatusEntry 7 } 645 gBondEthInLostEnds OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "A number of missing EndOfPacket indicators expected by the 651 frame assembly function. 653 This object maps to the WT-159 attribute aEthRxLostEnds. 655 Discontinuities in the value of this counter can occur at 656 re-initialization of the management system, and at other times 657 as indicated by the value of ifCounterDiscontinuityTime, 658 defined in IF-MIB." 659 REFERENCE 660 "[WT-159] 5.5.3.10" 661 ::= { gBondEthPortStatusEntry 8 } 663 gBondEthInOverflows OBJECT-TYPE 664 SYNTAX Counter32 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "A number of fragments, received across the gamma interface 669 and discarded, which would have caused the frame assembly 670 buffer to overflow. 672 This object maps to the WT-159 attribute aEthRxOverflows. 674 Discontinuities in the value of this counter can occur at 675 re-initialization of the management system, and at other times 676 as indicated by the value of ifCounterDiscontinuityTime, 677 defined in IF-MIB." 678 REFERENCE 679 "[WT-159] 5.5.3.11" 680 ::= { gBondEthPortStatusEntry 9 } 682 -- BCE group 684 gBondEthBceStatusTable OBJECT-TYPE 685 SYNTAX SEQUENCE OF GBondEthBceStatusEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "This table provides common status information of G.Bond/Eth 690 BCE ports. 692 This table contains live data from the equipment. As such, 693 it is NOT persistent." 694 ::= { gBondEthBce 1 } 696 gBondEthBceStatusEntry OBJECT-TYPE 697 SYNTAX GBondEthBceStatusEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "An entry in the G.Bond/Eth BCE Status table. 702 Each entry represents common aspects of a G.Bond/Eth BCE port 703 indexed by the ifIndex. Note that a BCE port can be stacked 704 below a single GBS port, also indexed by ifIndex, 705 possibly together with other BCE ports." 706 INDEX { ifIndex } 707 ::= { gBondEthBceStatusTable 1 } 709 GBondEthBceStatusEntry ::= 710 SEQUENCE { 711 gBondEthBceTcInCodingErrors Counter32, 712 gBondEthBceTcInCrcErrors Counter32 713 } 715 gBondEthBceTcInCodingErrors OBJECT-TYPE 716 SYNTAX Counter32 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "A number of PTM-TC encapsulation errors. This counter is 721 incremented for each encapsulation error detected by the 722 PTM-TC receive function. 724 This object maps to WT-159 attribute 725 aChannelPtmTcRxCodingViolations. 727 Discontinuities in the value of this counter can occur at 728 re-initialization of the management system, and at other times 729 as indicated by the value of ifCounterDiscontinuityTime, 730 defined in IF-MIB." 731 REFERENCE 732 "[WT-159] 5.5.7.5" 733 ::= { gBondEthBceStatusEntry 1 } 735 gBondEthBceTcInCrcErrors OBJECT-TYPE 736 SYNTAX Counter32 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "A number of PTM-TC CRC errors. This counter is incremented 741 for each CRC error detected by the PTM-TC receive function. 743 This object maps to WT-159 attribute aChannelPtmTcRxCrcErrors. 745 Discontinuities in the value of this counter can occur at 746 re-initialization of the management system, and at other times 747 as indicated by the value of ifCounterDiscontinuityTime, 748 defined in IF-MIB." 749 REFERENCE 750 "[WT-159] 5.5.7.6" 751 ::= { gBondEthBceStatusEntry 2 } 753 -- 754 -- Conformance Statements 755 -- 757 gBondEthGroups OBJECT IDENTIFIER 758 ::= { gBondEthConformance 1 } 760 gBondEthCompliances OBJECT IDENTIFIER 761 ::= { gBondEthConformance 2 } 763 -- Object Groups 765 gBondEthBasicGroup OBJECT-GROUP 766 OBJECTS { 767 gBondEthTcTypesSupported, 768 gBondEthTcAdminType, 769 gBondEthTcOperType, 770 gBondEthInErrors, 771 gBondEthInSmallFragments, 772 gBondEthInLargeFragments, 773 gBondEthInBadFragments, 774 gBondEthInLostFragments, 775 gBondEthInLostStarts, 776 gBondEthInLostEnds, 777 gBondEthInOverflows, 778 gBondEthBceTcInCodingErrors, 779 gBondEthBceTcInCrcErrors 780 } 781 STATUS current 782 DESCRIPTION 783 "A collection of objects representing management information 784 for G.Bond/Eth GBS ports." 785 ::= { gBondEthGroups 1 } 787 gBondEthBceGroup OBJECT-GROUP 788 OBJECTS { 789 gBondEthBceTcInCodingErrors, 790 gBondEthBceTcInCrcErrors 791 } 792 STATUS current 793 DESCRIPTION 794 "A collection of objects representing OPTIONAL management 795 information for G.Bond/Eth BCE ports." 796 ::= { gBondEthGroups 2 } 798 -- Compliance Statements 800 gBondEthCompliance MODULE-COMPLIANCE 801 STATUS current 802 DESCRIPTION 803 "The compliance statement for G.Bond Ethernet interfaces. 804 Compliance with the following external compliance statements 805 is REQUIRED: 807 MIB Module Compliance Statement 808 ---------- -------------------- 809 IF-MIB ifCompliance3 810 GBOND-MIB gBondCompliance" 812 MODULE -- this module 813 MANDATORY-GROUPS { 814 gBondEthBasicGroup 815 } 817 GROUP gBondEthBceGroup 818 DESCRIPTION 819 "Support for this group is OPTIONAL" 821 OBJECT gBondEthTcTypesSupported 822 SYNTAX BITS { 823 tc6465(0), 824 tcHDLC(1) 825 } 826 DESCRIPTION 827 "Support for all TC types is not required. However at least 828 one value SHALL be supported" 830 OBJECT gBondEthTcAdminType 831 MIN-ACCESS read-only 832 DESCRIPTION 833 "Write access is not required (needed only for GBS 834 supporting more than a single TC encapsulation type, i.e. 835 tc6465 and tcHDLC" 837 ::= { gBondEthCompliances 1 } 838 END 840 7. Security Considerations 842 There is a number of managed objects defined in the GBOND-ETH-MIB 843 module that have a MAX-ACCESS clause of read-write or read-create. 844 Writing to these objects can have potentially disruptive effects on 845 network operation, for example: 847 o Changing of gBondEthPortConfTable configuration paratemers (e.g. 848 gBondEthTcAdminType) MAY lead to a complete service interruption, 849 in case the specified PTM-TC encapsulation type is not supported 850 by the remote end. 852 The user of the GBOND-ETH-MIB module must therefore be aware that 853 support for SET operations in a non-secure environment without proper 854 protection can have a negative effect on network operations. 856 The readable objects in the GBOND-ETH-MIB module (i.e., those with 857 MAX-ACCESS other than not-accessible) may be considered sensitive in 858 some environments since, collectively, they provide information about 859 the performance of network interfaces and can reveal some aspects of 860 their configuration. 862 In such environments it is important to control also GET and NOTIFY 863 access to these objects and possibly even to encrypt their values 864 when sending them over the network via SNMP. 866 SNMP versions prior to SNMPv3 did not include adequate security. 867 Even if the network itself is secure (for example by using IPSec), 868 even then, there is no control as to who on the secure network is 869 allowed to access and GET/SET (read/change/create/delete) the objects 870 in this MIB module. 872 It is RECOMMENDED that implementers consider the security features as 873 provided by the SNMPv3 framework (see [RFC3410], section 8), 874 including full support for the SNMPv3 cryptographic mechanisms (for 875 authentication and privacy). 877 Further, deployment of SNMP versions prior to SNMPv3 is NOT 878 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 879 enable cryptographic security. It is then a customer/operator 880 responsibility to ensure that the SNMP entity giving access to an 881 instance of this MIB module is properly configured to give access to 882 the objects only to those principals (users) that have legitimate 883 rights to indeed GET or SET (change/create/delete) them. 885 8. IANA Considerations 887 An object identifier for gBondEthMIB MODULE-IDENTITY SHALL be 888 allocated by IANA in the MIB-2 transmission sub-tree, before this 889 document is published as an RFC. 891 9. Acknowledgments 893 This document was produced by the [ADSLMIB] working group. 895 10. References 897 10.1. Normative References 899 [802.3] IEEE, "IEEE Standard for Information 900 technology - Telecommunications and 901 information exchange between systems - 902 Local and metropolitan area networks - 903 Specific requirements - Part 3: Carrier 904 Sense Multiple Access with Collision 905 Detection (CSMA/CD) Access Method and 906 Physical Layer Specifications", IEEE 907 Std 802.3-2005, December 2005. 909 [G.998.2] ITU-T, "Ethernet-based multi-pair 910 bonding", ITU-T Recommendation G.998.2, 911 January 2005, . 914 [RFC2119] Bradner, S., "Key words for use in RFCs 915 to Indicate Requirement Levels", 916 BCP 14, RFC 2119, March 1997. 918 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 919 and J. Schoenwaelder, Ed., "Structure 920 of Management Information Version 2 921 (SMIv2)", STD 58, RFC 2578, April 1999. 923 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 924 and J. Schoenwaelder, Ed., "Textual 925 Conventions for SMIv2", STD 58, 926 RFC 2579, April 1999. 928 [RFC2580] McCloghrie, K., Perkins, D., and J. 929 Schoenwaelder, "Conformance Statements 930 for SMIv2", STD 58, RFC 2580, 931 April 1999. 933 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 934 Interfaces Group MIB", RFC 2863, 935 June 2000. 937 [RFC3410] Case, J., Mundy, R., Partain, D., and 938 B. Stewart, "Introduction and 939 Applicability Statements for Internet- 940 Standard Management Framework", 941 RFC 3410, December 2002. 943 [WT-159] Morgenstern, M., Beili, E., and N. 944 Nair, "Management Framework for xDSL 945 Bonding", DSL Forum technical 946 report WT-159, November 2007. 948 10.2. Informative References 950 [ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", . 954 [G.991.2] ITU-T, "Single-pair High-speed Digital 955 Subscriber Line (SHDSL) transceivers", 956 ITU-T Recommendation G.991.2, 957 December 2003, . 960 [G.993.1] ITU-T, "Very High speed Digital 961 Subscriber Line transceivers", ITU-T 962 Recommendation G.993.1, June 2004, . 965 [I-D.ietf-adslmib-gbond-mib] Beili, E., Morgenstern, M., and N. 966 Nair, "xDSL multi-pair bonding (G.Bond) 967 MIB", draft-ietf-adslmib-gbond-mib-01 968 (work in progress), November 2007. 970 [IANAifType-MIB] Internet Assigned Numbers Authority 971 (IANA), "IANAifType Textual Convention 972 definition", . 975 [RFC4181] Heard, C., "Guidelines for Authors and 976 Reviewers of MIB Documents", BCP 111, 977 RFC 4181, September 2005. 979 [RFC4836] Beili, E., "Definitions of Managed 980 Objects for IEEE 802.3 Medium 981 Attachment Units (MAUs)", RFC 4836, 982 April 2007. 984 [RFC5066] Beili, E., "Ethernet in the First Mile 985 Copper (EFMCu) Interfaces MIB", 986 RFC 5066, November 2007. 988 Authors' Addresses 990 Edward Beili 991 Actelis Networks 992 25 Bazel St. 993 Petach-Tikva 49103 994 Israel 996 Phone: +972-3-924-3491 997 EMail: edward.beili@actelis.com 999 Moti Morgenstern 1000 ECI Telecom 1001 30 Hasivim St. 1002 Petach-Tikva 49517 1003 Israel 1005 Phone: +972-3-926-6258 1006 EMail: moti.morgenstern@ecitele.com 1008 Full Copyright Statement 1010 Copyright (C) The IETF Trust (2007). 1012 This document is subject to the rights, licenses and restrictions 1013 contained in BCP 78, and except as set forth therein, the authors 1014 retain all their rights. 1016 This document and the information contained herein are provided on an 1017 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1018 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1019 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1020 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1021 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1022 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1024 Intellectual Property 1026 The IETF takes no position regarding the validity or scope of any 1027 Intellectual Property Rights or other rights that might be claimed to 1028 pertain to the implementation or use of the technology described in 1029 this document or the extent to which any license under such rights 1030 might or might not be available; nor does it represent that it has 1031 made any independent effort to identify any such rights. Information 1032 on the procedures with respect to rights in RFC documents can be 1033 found in BCP 78 and BCP 79. 1035 Copies of IPR disclosures made to the IETF Secretariat and any 1036 assurances of licenses to be made available, or the result of an 1037 attempt made to obtain a general license or permission for the use of 1038 such proprietary rights by implementers or users of this 1039 specification can be obtained from the IETF on-line IPR repository at 1040 http://www.ietf.org/ipr. 1042 The IETF invites any interested party to bring to its attention any 1043 copyrights, patents or patent applications, or other proprietary 1044 rights that may cover technology that may be required to implement 1045 this standard. Please address the information to the IETF at 1046 ietf-ipr@ietf.org. 1048 Acknowledgement 1050 Funding for the RFC Editor function is provided by the IETF 1051 Administrative Support Activity (IASA).