idnits 2.17.1
draft-ietf-adslmib-gbond-eth-mib-00.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 1012.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1023.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1030.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1036.
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 (June 05, 2007) is 6168 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
== Unused Reference: 'RFC4836' is defined on line 967, 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-00
== Outdated reference: A later version (-08) exists of
draft-ietf-hubmib-efm-cu-mib-07
Summary: 2 errors (**), 0 flaws (~~), 6 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: December 7, 2007 ECI Telecom
6 June 05, 2007
8 Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB
9 draft-ietf-adslmib-gbond-eth-mib-00.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 December 7, 2007.
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 [I-D.ietf-hubmib-efm-cu-mib] module defines objects for
136 managing Ethernet in the First Mile Copper (EFMCu) interfaces
137 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3-2005 [802.3].
138 These interfaces are based on Single-pair High-speed Digital
139 Subscriber Line (SHDSL) [G.991.2] and Very High speed Digital
140 Subscriber Line (VDSL) [G.993.1] technology respectively, and can be
141 optionally aggregated (bonded).
143 ITU-T G.998.2 specification extends the IEEE 802.3 Clause 61 bonding
144 to work over any xDSL technology, providing the ability to bond
145 individual channels as well as physical lines.
147 EFM-CU-MIB can be used to manage all aspects of the EFMCu interfaces,
148 including the management of SHDSL/VDSL lines. GBOND-MIB and GBOND-
149 ETH-MIB modules provide management objects only for the bonding part,
150 leaving the management of the individual xDSL interfaces (lines/
151 channels) to the respective xDSL MIB modules.
153 5. MIB Structure
155 5.1. Overview
157 _EdNote: TBC... _
159 5.1.1. TODO/Open Issues
160 o Peformance Monitoring counters
162 o Support for ITU-T draft BACP
164 5.2. Mapping of IEEE 802.3 Managed Objects
166 This section contains the mapping between relevant managed objects
167 (attributes) defined in [802.3] and managed objects defined in this
168 document.
170 +----------------------+---------------------------+
171 | 802.3 Managed Object | Corresponding SNMP Object |
172 +----------------------+---------------------------+
173 | oGroup | |
174 +----------------------+---------------------------+
175 +----------------------+---------------------------+
176 | TBC... | TBC... |
177 +----------------------+---------------------------+
179 Table 1: Mapping of 802.3 Managed Objects
181 _EdNote: Finish the table and remove TBC... _
183 5.3. Mapping of DSL Forum WT-159 Managed Objects
185 This section contains the mapping between relevant managed objects
186 (attributes) defined in [WT-159] and managed objects defined in this
187 document.
189 +---------------------------------+-----------------------------+
190 | WT-159 Managed Object | Corresponding SNMP Object |
191 +---------------------------------+-----------------------------+
192 | oBondEth | |
193 +---------------------------------+-----------------------------+
194 | aEthTcAdminType | gBondEthTcAdminType |
195 +---------------------------------+-----------------------------+
196 | aEthTcOperType | gBondEthTcOperType |
197 +---------------------------------+-----------------------------+
198 | aEthTcTypesSupported | gBondEthTcTypesSupported |
199 +---------------------------------+-----------------------------+
200 | aEthRxErrors | gBondEthInErrors |
201 +---------------------------------+-----------------------------+
202 | aEthRxSmallFragments | gBondEthInSmallFragments |
203 +---------------------------------+-----------------------------+
204 | aEthRxLargeFragments | gBondEthInLargeFragments |
205 +---------------------------------+-----------------------------+
206 | aEthRxBadFragments | gBondEthInBadFragments |
207 +---------------------------------+-----------------------------+
208 | aEthRxLostFragments | gBondEthInLostFragments |
209 +---------------------------------+-----------------------------+
210 | aEthRxLostStarts | gBondEthInLostStarts |
211 +---------------------------------+-----------------------------+
212 | aEthRxLostEnds | gBondEthInLostEnds |
213 +---------------------------------+-----------------------------+
214 | aEthRxOverflows | gBondEthInOverflows |
215 +---------------------------------+-----------------------------+
216 | oChannel | |
217 +---------------------------------+-----------------------------+
218 | aChannelPtmTcRxCodingViolations | gBondEthBceTcInCodingErrors |
219 +---------------------------------+-----------------------------+
220 | aChannelPtmTcRxCrcErrors | gBondEthBceTcInCrcErrors |
221 +---------------------------------+-----------------------------+
223 Table 2: Mapping of WT-159 Managed Objects
225 6. G.Bond/Ethernet MIB Definitions
227 GBOND-ETH-MIB DEFINITIONS ::= BEGIN
229 IMPORTS
230 MODULE-IDENTITY, OBJECT-TYPE, Counter32
231 FROM SNMPv2-SMI -- RFC 2578
232 TEXTUAL-CONVENTION
233 FROM SNMPv2-TC -- RFC 2579
234 MODULE-COMPLIANCE, OBJECT-GROUP
235 FROM SNMPv2-CONF -- RFC 2580
236 ifIndex
237 FROM IF-MIB -- RFC 2863
238 gBondMIB
239 FROM GBOND-MIB -- RFC YYYY
240 -- EdNote: Replace YYYY with the actual RFC number &
241 -- remove this note
242 ;
244 gBondEthMIB MODULE-IDENTITY
245 LAST-UPDATED "200706050000Z" -- June 05, 2007
246 ORGANIZATION "IETF ADSL MIB Working Group"
247 CONTACT-INFO
248 "WG charter:
249 http://www.ietf.org/html.charters/adslmib-charter.html
251 Mailing Lists:
252 General Discussion: adslmib@ietf.org
253 To Subscribe: adslmib-request@ietf.org
254 In Body: subscribe your_email_address
256 Chair: Menachem Dodge
257 Postal: ECI Telecom, Ltd.
258 30 Hasivim St.,
259 Petach-Tikva 49517
260 Israel
261 Phone: +972-3-926-8421
262 EMail: menachem.dodge@ecitele.com
264 Editor: Edward Beili
265 Postal: Actelis Networks, Inc.
266 25 Bazel St., P.O.B. 10173
267 Petach-Tikva 10173
268 Israel
269 Phone: +972-3-924-3491
270 EMail: edward.beili@actelis.com
272 Editor: Moti Morgenstern
273 Postal: ECI Telecom
274 30 Hasivim St.
275 Petach-Tikva 49517
276 Israel
277 Phone: +972-3-926-6258
278 EMail: moti.morgenstern@ecitele.com"
280 DESCRIPTION
281 "The objects in this MIB module are used to manage the
282 Ethernet-based multi-pair bonded xDSL Interfaces, defined in
283 ITU-T recommendation G.998.2 (G.Bond/Ethernet).
285 This MIB module MUST be used in conjunction with GBOND-MIB
286 module, common to all G.Bond technologies.
288 The following references are used throughout this MIB module:
290 [G.998.2] refers to:
291 ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
292 bonding', January 2005.
294 [802.3] refers to:
295 IEEE Std 802.3-2005: 'IEEE Standard for Information
296 technology - Telecommunications and information exchange
297 between systems - Local and metropolitan area networks -
298 Specific requirements -
299 Part 3: Carrier Sense Multiple Access with Collision
300 Detection (CSMA/CD) Access Method and Physical Layer
301 Specifications', December 2005.
303 [WT-159] refers to:
304 DSL Forum Technical Report: 'Management Framework for xDSL
305 Bonding', May 2007.
307 Naming Conventions:
308 BCE - Bonding Channel Entity
309 CO - Central Office
310 CPE - Customer Premises Equipment
311 GBS - Generic Bonding Sublayer
312 HDLC - High-level Data Link Control
313 PTM-TC - Packet Transfer Mode Transmission Convergence
314 (sub-layer)
315 SNR - Signal to Noise Ratio
316 TC - Transmission Convergence (sub-layer)
318 Copyright (C) The Internet Society (2007). This version of this
319 MIB module is part of RFC XXXX; see the RFC itself for full
320 legal notices."
322 REVISION "200706050000Z" -- June 05, 2007
323 DESCRIPTION "Initial version, published as RFC XXXX."
325 -- EdNote: Replace XXXX with the actual RFC number &
326 -- remove this note
328 ::= { gBondMIB 2 }
330 -- Sections of the module
331 -- Structured as recommended by RFC 4181, Appendix D
332 gBondEthObjects OBJECT IDENTIFIER ::= { gBondEthMIB 1 }
334 gBondEthConformance OBJECT IDENTIFIER ::= { gBondEthMIB 2 }
336 -- Groups in the module
338 gBondEthPort OBJECT IDENTIFIER ::= { gBondEthObjects 1 }
340 gBondEthBce OBJECT IDENTIFIER ::= { gBondEthObjects 2 }
342 -- Textual Conventions
344 GBondEthPtmTcType ::= TEXTUAL-CONVENTION
345 STATUS current
346 DESCRIPTION
347 "This textual convention represents possible PTM-TC types in
348 G.bond/Eth ports. The following values are defined:
349 tc6465 - 64/65-octet encapsulation, as defined in
350 [802.3] Clause 61.3.3
351 tcHDLC - HDLC encapsulation, as defined in [G.998.2]
352 Annex B"
353 SYNTAX INTEGER {
354 tc6465(1),
355 tcHDLC(2)
356 }
358 -- GBS Notifications group
359 -- empty --
361 -- GBS group
363 gBondEthPortConfTable OBJECT-TYPE
364 SYNTAX SEQUENCE OF GBondEthPortConfEntry
365 MAX-ACCESS not-accessible
366 STATUS current
367 DESCRIPTION
368 "Table for Configuration of G.Bond/Eth GBS ports. Entries in
369 this table MUST be maintained in a persistent manner"
370 ::= { gBondEthPort 1 }
372 gBondEthPortConfEntry OBJECT-TYPE
373 SYNTAX GBondEthPortConfEntry
374 MAX-ACCESS not-accessible
375 STATUS current
376 DESCRIPTION
377 "An entry in the G.Bond/Eth Port Configuration table.
378 Each entry represents an G.Bond Ethernet port indexed by the
379 ifIndex.
381 Note that an G.Bond/Eth GBS port runs on top of a single
382 or multiple BCE port(s), which are also indexed by ifIndex."
383 INDEX { ifIndex }
384 ::= { gBondEthPortConfTable 1 }
386 GBondEthPortConfEntry ::=
387 SEQUENCE {
388 gBondEthTcAdminType GBondEthPtmTcType
389 }
391 gBondEthTcAdminType OBJECT-TYPE
392 SYNTAX GBondEthPtmTcType
393 MAX-ACCESS read-write
394 STATUS current
395 DESCRIPTION
396 "Administrative (desired) PTM-TC encapsulation type of
397 G.Bond/Eth port (GBS).
398 Possible values are:
399 tc6465(1) - 64/65-octet encapsulation
400 tcHDLC(2) - HDLC encapsulation
401 Attempts to set a port to a non-supported PTM-TC encapsulation
402 type (see gBondEthTcTypesSupported) SHALL be rejected.
404 Changing gBondEthTcAdminType is a traffic disruptive
405 operation and as such SHALL be done when the link is Down.
406 Attempts to cange this object SHALL be rejected if the link
407 is Up or Initializing.
409 This object maps to the WT-159 attribute aEthTcAdminType.
411 This object MUST be maintained in a persistent manner."
412 REFERENCE
413 "[WT-159] 5.5.3.1"
414 ::= { gBondEthPortConfEntry 1 }
416 gBondEthPortCapabilityTable OBJECT-TYPE
417 SYNTAX SEQUENCE OF GBondEthPortCapabilityEntry
418 MAX-ACCESS not-accessible
419 STATUS current
420 DESCRIPTION
421 "Table for Capabilities of G.Bond/Eth Ports. Entries in this
422 table MUST be maintained in a persistent manner"
423 ::= { gBondEthPort 2 }
425 gBondEthPortCapabilityEntry OBJECT-TYPE
426 SYNTAX GBondEthPortCapabilityEntry
427 MAX-ACCESS not-accessible
428 STATUS current
429 DESCRIPTION
430 "An entry in the G.Bond/Eth Port Capability table.
431 Each entry represents an G.Bond port indexed by the ifIndex.
432 Note that a G.Bond GBS port runs on top of a single
433 or multiple BCE port(s), which are also indexed by ifIndex."
434 INDEX { ifIndex }
435 ::= { gBondEthPortCapabilityTable 1 }
437 GBondEthPortCapabilityEntry ::=
438 SEQUENCE {
439 gBondEthTcTypesSupported BITS
440 }
442 gBondEthTcTypesSupported OBJECT-TYPE
443 SYNTAX BITS {
444 tc6465(0),
445 tcHDLC(1)
446 }
447 MAX-ACCESS read-only
448 STATUS current
449 DESCRIPTION
450 "PTM-TC Encapsulation types supported by the G.Bond/Eth port.
451 This is a bitmap of possible encapsulation types. The various
452 bit positions are:
453 tc6465 - GBS is capable of 64/65-octet encapsulation
454 tcHDLC - GBS is capable of HDLC encapsulation
456 A desired encapsulation is determined by
457 gBondEthTcAdminType, while gBondEthTcOperType reflects the
458 current operating mode.
460 This object maps to the WT-159 attribute
461 aEthTcTypesSupported."
462 REFERENCE
463 "[WT-159] 5.5.3.3"
464 ::= { gBondEthPortCapabilityEntry 1 }
466 gBondEthPortStatusTable OBJECT-TYPE
467 SYNTAX SEQUENCE OF GBondEthPortStatusEntry
468 MAX-ACCESS not-accessible
469 STATUS current
470 DESCRIPTION
471 "This table provides overall status information of G.Bond
472 ports, complementing the generic status information from the
473 ifTable of IF-MIB. Additional status information about
474 connected BCEs is available from the relevant line MIBs
475 This table contains live data from the equipment. As such,
476 it is NOT persistent."
477 ::= { gBondEthPort 3 }
479 gBondEthPortStatusEntry OBJECT-TYPE
480 SYNTAX GBondEthPortStatusEntry
481 MAX-ACCESS not-accessible
482 STATUS current
483 DESCRIPTION
484 "An entry in the G.Bond/Eth Port Status table.
485 Each entry represents an G.Bond/Eth port indexed by the
486 ifIndex.
487 Note that an G.Bond GBS port runs on top of a single
488 or multiple BCE port(s), which are also indexed by ifIndex."
489 INDEX { ifIndex }
490 ::= { gBondEthPortStatusTable 1 }
492 GBondEthPortStatusEntry ::=
493 SEQUENCE {
494 gBondEthTcOperType GBondEthPtmTcType,
495 gBondEthInErrors Counter32,
496 gBondEthInSmallFragments Counter32,
497 gBondEthInLargeFragments Counter32,
498 gBondEthInBadFragments Counter32,
499 gBondEthInLostFragments Counter32,
500 gBondEthInLostStarts Counter32,
501 gBondEthInLostEnds Counter32,
502 gBondEthInOverflows Counter32
503 }
505 gBondEthTcOperType OBJECT-TYPE
506 SYNTAX GBondEthPtmTcType
507 MAX-ACCESS read-only
508 STATUS current
509 DESCRIPTION
510 "Current operational encapsulation type of the G.Bond/Eth
511 port.
512 Possible values are:
513 tc6465(1) - GBS uses 64/65-octet encapsulation
514 tcHDLC(2) - GBS uses HDLC encapsulation
516 The operational PTM-TC encapsulation type can be configured
517 via gBondEthTcAdminType variable.
519 This objects maps to the WT-159 aEthTcOperType."
520 REFERENCE
521 "[WT-159] 5.5.3.2"
522 ::= { gBondEthPortStatusEntry 1 }
524 gBondEthInErrors OBJECT-TYPE
525 SYNTAX Counter32
526 MAX-ACCESS read-only
527 STATUS current
528 DESCRIPTION
529 "A number of fragments that have been received across the
530 gamma interface and discarded.
532 This object maps to the WT-159 attribute aEthRxErrors.
534 Discontinuities in the value of this counter can occur at
535 re-initialization of the management system, and at other times
536 as indicated by the value of ifCounterDiscontinuityTime,
537 defined in IF-MIB."
538 REFERENCE
539 "[WT-159] 5.5.3.4"
540 ::= { gBondEthPortStatusEntry 2 }
542 gBondEthInSmallFragments OBJECT-TYPE
543 SYNTAX Counter32
544 MAX-ACCESS read-only
545 STATUS current
546 DESCRIPTION
547 "A number of fragments smaller than minFragmentSize
548 (64 Bytes), that have been received across the gamma
549 interface and discarded.
551 This object maps to the WT-159 attribute aEthRxSmallFragments.
553 Discontinuities in the value of this counter can occur at
554 re-initialization of the management system, and at other times
555 as indicated by the value of ifCounterDiscontinuityTime,
556 defined in IF-MIB."
557 REFERENCE
558 "[WT-159] 5.5.3.5"
559 ::= { gBondEthPortStatusEntry 3 }
561 gBondEthInLargeFragments OBJECT-TYPE
562 SYNTAX Counter32
563 MAX-ACCESS read-only
564 STATUS current
565 DESCRIPTION
566 "A number of fragments larger than maxFragmentSize
567 (512 Bytes), which have been received across the gamma
568 interface and discarded.
570 This object maps to the WT-159 attribute aEthRxLargeFragments.
572 Discontinuities in the value of this counter can occur at
573 re-initialization of the management system, and at other times
574 as indicated by the value of ifCounterDiscontinuityTime,
575 defined in IF-MIB."
576 REFERENCE
577 "[WT-159] 5.5.3.6"
578 ::= { gBondEthPortStatusEntry 4 }
580 gBondEthInBadFragments OBJECT-TYPE
581 SYNTAX Counter32
582 MAX-ACCESS read-only
583 STATUS current
584 DESCRIPTION
585 "A number of fragments which do not fit into the sequence
586 expected by the frame assembly function, that have been
587 received across the gamma interface and discarded (the
588 frame buffer is flushed to the next valid frame start).
590 This object maps to the WT-159 attribute aEthRxBadFragments.
592 Discontinuities in the value of this counter can occur at
593 re-initialization of the management system, and at other times
594 as indicated by the value of ifCounterDiscontinuityTime,
595 defined in IF-MIB."
596 REFERENCE
597 "[WT-159] 5.5.3.7"
598 ::= { gBondEthPortStatusEntry 5 }
600 gBondEthInLostFragments OBJECT-TYPE
601 SYNTAX Counter32
602 MAX-ACCESS read-only
603 STATUS current
604 DESCRIPTION
605 "A number of gaps in the sequence of fragments, which have
606 been received across the gamma interface (the frame buffer is
607 flushed to the next valid frame start, when fragment/fragments
608 expected by the frame assembly function is/are not received).
610 This object maps to the WT-159 attribute aEthRxLostFragments.
612 Discontinuities in the value of this counter can occur at
613 re-initialization of the management system, and at other times
614 as indicated by the value of ifCounterDiscontinuityTime,
615 defined in IF-MIB."
616 REFERENCE
617 "[WT-159] 5.5.3.8"
618 ::= { gBondEthPortStatusEntry 6 }
620 gBondEthInLostStarts OBJECT-TYPE
621 SYNTAX Counter32
622 MAX-ACCESS read-only
623 STATUS current
624 DESCRIPTION
625 "A number of missing StartOfPacket indicators expected by the
626 frame assembly function.
628 This object maps to the WT-159 attribute aEthRxLostStarts.
630 Discontinuities in the value of this counter can occur at
631 re-initialization of the management system, and at other times
632 as indicated by the value of ifCounterDiscontinuityTime,
633 defined in IF-MIB."
634 REFERENCE
635 "[WT-159] 5.5.3.9"
636 ::= { gBondEthPortStatusEntry 7 }
638 gBondEthInLostEnds OBJECT-TYPE
639 SYNTAX Counter32
640 MAX-ACCESS read-only
641 STATUS current
642 DESCRIPTION
643 "A number of missing EndOfPacket indicators expected by the
644 frame assembly function.
646 This object maps to the WT-159 attribute aEthRxLostEnds.
648 Discontinuities in the value of this counter can occur at
649 re-initialization of the management system, and at other times
650 as indicated by the value of ifCounterDiscontinuityTime,
651 defined in IF-MIB."
652 REFERENCE
653 "[WT-159] 5.5.3.10"
654 ::= { gBondEthPortStatusEntry 8 }
656 gBondEthInOverflows OBJECT-TYPE
657 SYNTAX Counter32
658 MAX-ACCESS read-only
659 STATUS current
660 DESCRIPTION
661 "A number of fragments, received across the gamma interface
662 and discarded, which would have caused the frame assembly
663 buffer to overflow.
665 This object maps to the WT-159 attribute aEthRxOverflows.
667 Discontinuities in the value of this counter can occur at
668 re-initialization of the management system, and at other times
669 as indicated by the value of ifCounterDiscontinuityTime,
670 defined in IF-MIB."
671 REFERENCE
672 "[WT-159] 5.5.3.11"
673 ::= { gBondEthPortStatusEntry 9 }
675 -- BCE group
677 gBondEthBceStatusTable OBJECT-TYPE
678 SYNTAX SEQUENCE OF GBondEthBceStatusEntry
679 MAX-ACCESS not-accessible
680 STATUS current
681 DESCRIPTION
682 "This table provides common status information of G.Bond/Eth
683 BCE ports.
685 This table contains live data from the equipment. As such,
686 it is NOT persistent."
687 ::= { gBondEthBce 1 }
689 gBondEthBceStatusEntry OBJECT-TYPE
690 SYNTAX GBondEthBceStatusEntry
691 MAX-ACCESS not-accessible
692 STATUS current
693 DESCRIPTION
694 "An entry in the G.Bond/Eth BCE Status table.
695 Each entry represents common aspects of a G.Bond/Eth BCE port
696 indexed by the ifIndex. Note that a BCE port can be stacked
697 below a single GBS port, also indexed by ifIndex,
698 possibly together with other BCE ports."
699 INDEX { ifIndex }
700 ::= { gBondEthBceStatusTable 1 }
702 GBondEthBceStatusEntry ::=
703 SEQUENCE {
704 gBondEthBceTcInCodingErrors Counter32,
705 gBondEthBceTcInCrcErrors Counter32
706 }
708 gBondEthBceTcInCodingErrors OBJECT-TYPE
709 SYNTAX Counter32
710 MAX-ACCESS read-only
711 STATUS current
712 DESCRIPTION
713 "A number of PTM-TC encapsulation errors. This counter is
714 incremented for each encapsulation error detected by the
715 PTM-TC receive function.
717 This object maps to WT-159 attribute
718 aChannelPtmTcRxCodingViolations.
720 Discontinuities in the value of this counter can occur at
721 re-initialization of the management system, and at other times
722 as indicated by the value of ifCounterDiscontinuityTime,
723 defined in IF-MIB."
724 REFERENCE
725 "[WT-159] 5.5.7.5"
726 ::= { gBondEthBceStatusEntry 1 }
728 gBondEthBceTcInCrcErrors OBJECT-TYPE
729 SYNTAX Counter32
730 MAX-ACCESS read-only
731 STATUS current
732 DESCRIPTION
733 "A number of PTM-TC CRC errors. This counter is incremented
734 for each CRC error detected by the PTM-TC receive function.
736 This object maps to WT-159 attribute aChannelPtmTcRxCrcErrors.
738 Discontinuities in the value of this counter can occur at
739 re-initialization of the management system, and at other times
740 as indicated by the value of ifCounterDiscontinuityTime,
741 defined in IF-MIB."
742 REFERENCE
743 "[WT-159] 5.5.7.6"
744 ::= { gBondEthBceStatusEntry 2 }
746 --
747 -- Conformance Statements
748 --
750 gBondEthGroups OBJECT IDENTIFIER
751 ::= { gBondEthConformance 1 }
753 gBondEthCompliances OBJECT IDENTIFIER
754 ::= { gBondEthConformance 2 }
756 -- Object Groups
758 gBondEthBasicGroup OBJECT-GROUP
759 OBJECTS {
760 gBondEthTcTypesSupported,
761 gBondEthTcAdminType,
762 gBondEthTcOperType,
763 gBondEthInErrors,
764 gBondEthInSmallFragments,
765 gBondEthInLargeFragments,
766 gBondEthInBadFragments,
767 gBondEthInLostFragments,
768 gBondEthInLostStarts,
769 gBondEthInLostEnds,
770 gBondEthInOverflows,
771 gBondEthBceTcInCodingErrors,
772 gBondEthBceTcInCrcErrors
773 }
774 STATUS current
775 DESCRIPTION
776 "A collection of objects representing management information
777 for G.Bond/Eth GBS ports."
778 ::= { gBondEthGroups 1 }
780 gBondEthBceGroup OBJECT-GROUP
781 OBJECTS {
782 gBondEthBceTcInCodingErrors,
783 gBondEthBceTcInCrcErrors
784 }
785 STATUS current
786 DESCRIPTION
787 "A collection of objects representing OPTIONAL management
788 information for G.Bond/Eth BCE ports."
789 ::= { gBondEthGroups 2 }
791 -- Compliance Statements
793 gBondEthCompliance MODULE-COMPLIANCE
794 STATUS current
795 DESCRIPTION
796 "The compliance statement for G.Bond Ethernet interfaces.
797 Compliance with the following external compliance statements
798 is REQUIRED:
800 MIB Module Compliance Statement
801 ---------- --------------------
802 IF-MIB ifCompliance3
803 GBOND-MIB gBondCompliance"
805 MODULE -- this module
806 MANDATORY-GROUPS {
807 gBondEthBasicGroup
808 }
810 GROUP gBondEthBceGroup
811 DESCRIPTION
812 "Support for this group is OPTIONAL"
814 OBJECT gBondEthTcTypesSupported
815 SYNTAX BITS {
816 tc6465(0),
817 tcHDLC(1)
818 }
819 DESCRIPTION
820 "Support for all TC types is not required. However at least
821 one value SHALL be supported"
823 OBJECT gBondEthTcAdminType
824 MIN-ACCESS read-only
825 DESCRIPTION
826 "Write access is not required (needed only for GBS
827 supporting more than a single TC encapsulation type, i.e.
828 tc6465 and tcHDLC"
830 ::= { gBondEthCompliances 1 }
831 END
833 7. Security Considerations
835 There is a number of managed objects defined in the GBOND-ETH-MIB
836 module that have a MAX-ACCESS clause of read-write or read-create.
837 Writing to these objects can have potentially disruptive effects on
838 network operation, for example:
840 o Changing of gBondEthPortConfTable configuration paratemers (e.g.
841 gBondEthTcAdminType) MAY lead to a complete service interruption,
842 in case the specified PTM-TC encapsulation type is not supported
843 by the remote end.
845 The user of the GBOND-ETH-MIB module must therefore be aware that
846 support for SET operations in a non-secure environment without proper
847 protection can have a negative effect on network operations.
849 The readable objects in the GBOND-ETH-MIB module (i.e., those with
850 MAX-ACCESS other than not-accessible) may be considered sensitive in
851 some environments since, collectively, they provide information about
852 the performance of network interfaces and can reveal some aspects of
853 their configuration.
855 In such environments it is important to control also GET and NOTIFY
856 access to these objects and possibly even to encrypt their values
857 when sending them over the network via SNMP.
859 SNMP versions prior to SNMPv3 did not include adequate security.
861 Even if the network itself is secure (for example by using IPSec),
862 even then, there is no control as to who on the secure network is
863 allowed to access and GET/SET (read/change/create/delete) the objects
864 in this MIB module.
866 It is RECOMMENDED that implementers consider the security features as
867 provided by the SNMPv3 framework (see [RFC3410], section 8),
868 including full support for the SNMPv3 cryptographic mechanisms (for
869 authentication and privacy).
871 Further, deployment of SNMP versions prior to SNMPv3 is NOT
872 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
873 enable cryptographic security. It is then a customer/operator
874 responsibility to ensure that the SNMP entity giving access to an
875 instance of this MIB module is properly configured to give access to
876 the objects only to those principals (users) that have legitimate
877 rights to indeed GET or SET (change/create/delete) them.
879 8. IANA Considerations
881 A new IANAifType value of g9982 SHALL be defined by the IANA [1] in
882 the IANAifType-MIB module [IANAifType-MIB], before this document is
883 published as an RFC.
885 9. Acknowledgments
887 This document was produced by the IETF ADSL MIB Working Group [2].
889 10. References
891 10.1. Normative References
893 [802.3] IEEE, "IEEE Standard for Information
894 technology - Telecommunications and
895 information exchange between systems -
896 Local and metropolitan area networks -
897 Specific requirements - Part 3: Carrier
898 Sense Multiple Access with Collision
899 Detection (CSMA/CD) Access Method and
900 Physical Layer Specifications", IEEE
901 Std 802.3-2005, December 2005.
903 [G.998.2] ITU-T, "Ethernet-based multi-pair
904 bonding", ITU-T Recommendation G.998.2,
905 January 2005.
907 [RFC2119] Bradner, S., "Key words for use in RFCs
908 to Indicate Requirement Levels",
909 BCP 14, RFC 2119, March 1997.
911 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
912 and J. Schoenwaelder, Ed., "Structure
913 of Management Information Version 2
914 (SMIv2)", STD 58, RFC 2578, April 1999.
916 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed.,
917 and J. Schoenwaelder, Ed., "Textual
918 Conventions for SMIv2", STD 58,
919 RFC 2579, April 1999.
921 [RFC2580] McCloghrie, K., Perkins, D., and J.
922 Schoenwaelder, "Conformance Statements
923 for SMIv2", STD 58, RFC 2580,
924 April 1999.
926 [RFC3410] Case, J., Mundy, R., Partain, D., and
927 B. Stewart, "Introduction and
928 Applicability Statements for Internet-
929 Standard Management Framework",
930 RFC 3410, December 2002.
932 [WT-159] Morgenstern, M., Beili, E., and N.
933 Nair, "Management Framework for xDSL
934 Bonding", DSL Forum technical
935 report WT-159, May 2007.
937 10.2. Informative References
939 [G.991.2] ITU-T, "Single-pair High-speed Digital
940 Subscriber Line (SHDSL) transceivers",
941 ITU-T Recommendation G.991.2,
942 December 2003.
944 [G.993.1] ITU-T, "Very High speed Digital
945 Subscriber Line transceivers", ITU-T
946 Recommendation G.993.1, June 2004.
948 [I-D.ietf-adslmib-gbond-mib] Beili, E., Morgenstern, M., and N.
949 Nair, "xDSL multi-pair bonding (G.Bond)
950 MIB", draft-ietf-adslmib-gbond-mib-00
951 (work in progress), February 2007.
953 [I-D.ietf-hubmib-efm-cu-mib] Beili, E., "Ethernet in the First Mile
954 Copper (EFMCu) Interfaces MIB",
955 draft-ietf-hubmib-efm-cu-mib-07.txt
956 (work in progress), February 2007.
958 [IANAifType-MIB] Internet Assigned Numbers Authority
959 (IANA), "IANAifType Textual Convention
960 definition", http://www.iana.org/
961 assignments/ianaiftype-mib.
963 [RFC2863] McCloghrie, K. and F. Kastenholz, "The
964 Interfaces Group MIB", RFC 2863,
965 June 2000.
967 [RFC4836] Beili, E., "Definitions of Managed
968 Objects for IEEE 802.3 Medium
969 Attachment Units (MAUs)", RFC 4836,
970 April 2007.
972 URIs
974 [1]
976 [2]
978 Authors' Addresses
980 Edward Beili
981 Actelis Networks
982 25 Bazel St.
983 Petach-Tikva 49103
984 Israel
986 Phone: +972-3-924-3491
987 EMail: edward.beili@actelis.com
989 Moti Morgenstern
990 ECI Telecom
991 30 Hasivim St.
992 Petach-Tikva 49517
993 Israel
995 Phone: +972-3-926-6258
996 EMail: moti.morgenstern@ecitele.com
998 Full Copyright Statement
1000 Copyright (C) The IETF Trust (2007).
1002 This document is subject to the rights, licenses and restrictions
1003 contained in BCP 78, and except as set forth therein, the authors
1004 retain all their rights.
1006 This document and the information contained herein are provided on an
1007 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1008 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1009 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1010 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1011 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1012 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1014 Intellectual Property
1016 The IETF takes no position regarding the validity or scope of any
1017 Intellectual Property Rights or other rights that might be claimed to
1018 pertain to the implementation or use of the technology described in
1019 this document or the extent to which any license under such rights
1020 might or might not be available; nor does it represent that it has
1021 made any independent effort to identify any such rights. Information
1022 on the procedures with respect to rights in RFC documents can be
1023 found in BCP 78 and BCP 79.
1025 Copies of IPR disclosures made to the IETF Secretariat and any
1026 assurances of licenses to be made available, or the result of an
1027 attempt made to obtain a general license or permission for the use of
1028 such proprietary rights by implementers or users of this
1029 specification can be obtained from the IETF on-line IPR repository at
1030 http://www.ietf.org/ipr.
1032 The IETF invites any interested party to bring to its attention any
1033 copyrights, patents or patent applications, or other proprietary
1034 rights that may cover technology that may be required to implement
1035 this standard. Please address the information to the IETF at
1036 ietf-ipr@ietf.org.
1038 Acknowledgement
1040 Funding for the RFC Editor function is provided by the IETF
1041 Administrative Support Activity (IASA).