idnits 2.17.1
draft-ietf-adslmib-gbond-atm-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 18.
-- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on
line 747.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 758.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 765.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 771.
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 :
----------------------------------------------------------------------------
No issues found here.
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 (January 09, 2007) is 6316 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: 'G.991.2' is defined on line 649, but no explicit
reference was found in the text
== Unused Reference: 'G.993.1' is defined on line 653, but no explicit
reference was found in the text
== Unused Reference: 'IANAifType-MIB' is defined on line 664, but no
explicit reference was found in the text
== Unused Reference: 'RFC2864' is defined on line 672, but no explicit
reference was found in the text
== Unused Reference: 'RFC3635' is defined on line 676, but no explicit
reference was found in the text
== Unused Reference: 'RFC4070' is defined on line 679, but no explicit
reference was found in the text
== Unused Reference: 'RFC4319' is defined on line 684, but no explicit
reference was found in the text
** Downref: Normative reference to an Informational RFC: RFC 3410
== Outdated reference: A later version (-11) exists of
draft-ietf-adslmib-gbond-mib-00
Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 7 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: July 13, 2007 ECI Telecom
6 N. Nair
7 Wipro Technologies
8 January 09, 2007
10 ATM-Based xDSL Bonded Interfaces MIB
11 draft-ietf-adslmib-gbond-atm-mib-00.txt
13 Status of this Memo
15 By submitting this Internet-Draft, each author represents that any
16 applicable patent or other IPR claims of which he or she is aware
17 have been or will be disclosed, and any of which he or she becomes
18 aware will be disclosed, in accordance with Section 6 of BCP 79.
20 Internet-Drafts are working documents of the Internet Engineering
21 Task Force (IETF), its areas, and its working groups. Note that
22 other groups may also distribute working documents as Internet-
23 Drafts.
25 Internet-Drafts are draft documents valid for a maximum of six months
26 and may be updated, replaced, or obsoleted by other documents at any
27 time. It is inappropriate to use Internet-Drafts as reference
28 material or to cite them other than as "work in progress."
30 The list of current Internet-Drafts can be accessed at
31 http://www.ietf.org/ietf/1id-abstracts.txt.
33 The list of Internet-Draft Shadow Directories can be accessed at
34 http://www.ietf.org/shadow.html.
36 This Internet-Draft will expire on July 13, 2007.
38 Copyright Notice
40 Copyright (C) The IETF Trust (2007).
42 Abstract
44 This document defines Management Information Base (MIB) module for
45 use with network management protocols in TCP/IP based networks. This
46 document proposes an extension to the GBOND-MIB which defines a set
47 of common objects for managing multi-pair bonded Digital Subscriber
48 Line (xDSL) interfaces. In particular, it describes objects used for
49 managing parameters of the ATM based xDSL multi-pair bonded
50 interfaces, as defined in ITU-T recommendations G.998.1. The
51 Management Information Base (MIB) modules specific to the other
52 bonding technologies are defined in GBOND-ETH-MIB and GBOND-TDIM-MIB
53 respectively.
55 Table of Contents
57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
58 2. The Internet-Standard Management Framework . . . . . . . . . . 3
59 3. Management Model . . . . . . . . . . . . . . . . . . . . . . . 4
60 3.1. The DSL Forum Management Framework for xDSL Bonding . . . 4
61 3.2. Mapping of ITU-T G.998.1 Managed Objects . . . . . . . . . 4
62 3.3. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 5
63 3.4. Relation to other MIB modules . . . . . . . . . . . . . . 6
64 3.4.1. Relationship to Interfaces Group MIB module . . . . . 6
65 3.4.2. Relationship to G.BOND MIB module . . . . . . . . . . 6
66 3.5. IANA Considerations . . . . . . . . . . . . . . . . . . . 6
67 3.6. Structure of GBOND-ATM-MIB . . . . . . . . . . . . . . . . 6
68 3.7. Conventions Used . . . . . . . . . . . . . . . . . . . . . 6
69 4. xDSL multi-pair bonding ATM MIB Definitions . . . . . . . . . 7
70 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
71 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
72 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
73 7.1. Normative References . . . . . . . . . . . . . . . . . . . 14
74 7.2. Informative References . . . . . . . . . . . . . . . . . . 15
75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
76 Intellectual Property and Copyright Statements . . . . . . . . . . 17
78 1. Introduction
80 The xDSL Multi-Pair Bonding, allows a service provider to provide
81 high bandwidth services to business and residential customers over
82 multiple xDSL lines, with greater speed and resiliency, than the
83 service over a single xDSL line, bridging the gap between xDSL and
84 fiber-based transport.
86 There are three xDSL Multi-Pair Bonding schemes, also known under
87 collective name G.Bond: ATM based, Ethernet Based and time division
88 inverse multiplexing (TDIM) based
90 The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1
91 recommendation [G.998.1], which defines a method for bonding (or
92 aggregating) of multiple xDSL lines (or individual bearer channels in
93 multiple xDSL lines) into a single bi-directional logical link
94 carrying an ATM stream. This specification can be viewed as an
95 evolution of the legacy Inverse Multiplexing over ATM (IMA)
96 technology [af-phy-0086], applied to xDSL with variable rates on each
97 line/bearer channel. As with other bonding schemes, ATM bonding also
98 allows bonding of up to 32 individual sub-layers with variable rates,
99 providing common functionality for the configuration, initialization,
100 operation and monitoring of the bonded link.
102 The MIB module defined in this document defines a set of managed
103 objects specific to ATM based multi-pair bonding technology. This
104 MIB module extends the common objects specified in the GBOND-MIB
105 [I-D.ietf-adslmib-gbond-mib] modules.
107 2. The Internet-Standard Management Framework
109 For a detailed overview of the documents that describe the current
110 Internet-Standard Management Framework, please refer to section 7 of
111 RFC 3410 [RFC3410].
113 Managed objects are accessed via a virtual information store, termed
114 the Management Information Base or MIB. MIB objects are generally
115 accessed through the Simple Network Management Protocol (SNMP).
116 Objects in the MIB are defined using the mechanisms defined in the
117 Structure of Management Information (SMI). This memo specifies a MIB
118 module that is compliant to the SMIv2, which is described in STD 58,
119 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
120 [RFC2580].
122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
124 document are to be interpreted as described in RFC 2119 [RFC2119].
126 3. Management Model
128 3.1. The DSL Forum Management Framework for xDSL Bonding
130 This document makes use of the DSL Forum technical report Management
131 Framework for xDSL Bonding [WT-159], defining a management model and
132 a hierarchy of management objects for the bonded xDSL interfaces.
134 3.2. Mapping of ITU-T G.998.1 Managed Objects
136 This section contains the mapping between relevant managed objects
137 (attributes) defined in [G.998.1] and managed objects defined in this
138 document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
140 +----------+--------------------------------------------------------+
141 | G.Bond | Corresponding SNMP Object |
142 | Managed | |
143 | Object | |
144 +----------+--------------------------------------------------------+
145 | Group | |
146 | Provisio | |
147 | ning | |
148 +----------+--------------------------------------------------------+
149 | Group ID | IF-MIB::ifIndex (Group ifIndex) |
150 +----------+--------------------------------------------------------+
151 | Line | gBondAtmLineNumber |
152 | number | |
153 +----------+--------------------------------------------------------+
154 | Bearer | gBondAtmBearerNumber |
155 | number | |
156 +----------+--------------------------------------------------------+
157 | Maximum | gBondAtmUpMaxDataRate,gBondAtmDownMaxDataRate |
158 | aggregat | |
159 | edata | |
160 | rate | |
161 | (bit/s) | |
162 +----------+--------------------------------------------------------+
163 | Minimum | gBondThreshLowUpRate,gBondThreshLowDownRate |
164 | aggregat | |
165 | edata | |
166 | rate | |
167 | (bit/s) | |
168 +----------+--------------------------------------------------------+
169 | Differen | gBondAtmUpDiffDelayTolerence,gBondAtmDownDiffDelayTole |
170 | tial | rence |
171 | delay | |
172 | toleran | |
173 | ce(ms) | |
174 | Group | |
175 | Performa | |
176 | nce | |
177 +----------+--------------------------------------------------------+
178 | Achieved | gBondUpDataRate,gBondDownDataRate |
179 | aggregat | |
180 | edata | |
181 | rate | |
182 | (bit/s) | |
183 +----------+--------------------------------------------------------+
184 | Group | gBondStatus |
185 | status | |
186 +----------+--------------------------------------------------------+
187 | Group | gBondAtmShowTime |
188 | running | |
189 | time | |
190 +----------+--------------------------------------------------------+
191 | Group Rx | gBondAtmUpRxCellLossCount,gBondAtmDownRxCellLossCount |
192 | cell | |
193 | loss | |
194 | count | |
195 +----------+--------------------------------------------------------+
196 | Group | |
197 | Failure | |
198 +----------+--------------------------------------------------------+
199 | Current | gBondFltStatus |
200 | group | |
201 | failure | |
202 | reason | |
203 +----------+--------------------------------------------------------+
204 | Group | gBondAtmGroupFltCount |
205 | failure | |
206 | count | |
207 +----------+--------------------------------------------------------+
208 | Group | gBondAtmCurr15MUas,gBondAtmCurr1DayUas,gBondAtmPMHist1 |
209 | unavaila | 5MUas,gBondAtmPMHist1DayUas |
210 | ble | |
211 | seconds | |
212 +----------+--------------------------------------------------------+
214 Table 1: Mapping of ITU-T G.998.1 Managed Objects
216 3.3. Mapping of DSL Forum WT-159 Managed Objects
218 This section contains the mapping between relevant managed objects
219 (attributes) defined in [WT-159] and managed objects defined in this
220 document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
222 +-----------------------+---------------------------+
223 | G.Bond Managed Object | Corresponding SNMP Object |
224 +-----------------------+---------------------------+
225 | TBC | TBC |
226 +-----------------------+---------------------------+
228 Table 2: Mapping of DSL Forum WT-159 Managed Objects
230 3.4. Relation to other MIB modules
232 This section outlines the relationship of the MIB modules defined in
233 this document with other MIB modules described in the relevant RFCs.
234 Specifically, the following MIB modules are discussed: Interfaces
235 Group MIB (IF-MIB) and and G.Bond MIB (GBOND-MIB).
237 3.4.1. Relationship to Interfaces Group MIB module
239 A G.Bond ATM port forms a part of a multi-pair xDSL bonded interface.
240 It is managed using the MIB objects defined in the IF-MIB [RFC2863].
241 In particular the MIB object ifIndex is used to index instances of
242 G.Bond ATM ports in a system.
244 3.4.2. Relationship to G.BOND MIB module
246 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management
247 objects common for all Bonded multi-pair xDSL interfaces. In
248 particular is describes the bonding management, port and channel
249 configuration, initialization sequence etc.
251 Both GBOND-MIB and GBOND-TDIM-MIB modules are REQUIRED to manage a
252 G.Bond/TDIM port.
254 3.5. IANA Considerations
256 A new IANAifType value of g9981 SHALL be defined by the IANA [1] in
257 the [IANAifType-MIB]IANAifType-MIB module, before this document is
258 published as an RFC.
260 3.6. Structure of GBOND-ATM-MIB
262 _EdNote: Add structure based on the conclusion on fault and
263 performance reporting_
265 3.7. Conventions Used
267 _EdNote: To be added; abbreviation and textual conventions used in
268 this MIB_
270 4. xDSL multi-pair bonding ATM MIB Definitions
272 GBOND-ATM-MIB DEFINITIONS ::= BEGIN
274 IMPORTS
275 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
276 Unsigned32, Counter32, TimeTicks
277 FROM SNMPv2-SMI -- RFC 2578
278 TEXTUAL-CONVENTION, TruthValue
279 FROM SNMPv2-TC -- RFC 2579
280 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
281 FROM SNMPv2-CONF -- RFC 2580
282 ifIndex, InterfaceIndex
283 FROM IF-MIB -- RFC 2863
284 gBondMIB
285 FROM GBOND-MIB -- RFC YYYY
286 -- EdNote: Replace YYYY with the actual RFC number and
287 -- remove this note
288 ;
290 gBondAtmMIB MODULE-IDENTITY
291 LAST-UPDATED "200705140000Z" -- May 14, 2007
292 ORGANIZATION "IETF ADSL MIB Working Group"
293 CONTACT-INFO
294 "WG charter:
295 http://www.ietf.org/html.charters/adslmib-charter.html
297 Mailing Lists:
298 General Discussion: adslmib@ietf.org
299 To Subscribe: adslmib-request@ietf.org
300 In Body: subscribe your_email_address
302 Chair: Menachem Dodge
303 Postal: ECI Telecom, Ltd.
304 30 Hasivim St.,
305 Petach-Tikva 49517
306 Israel
307 Phone: +972-3-926-8421
308 EMail: menachem.dodge@ecitele.com
310 Editor: Edward Beili
311 Postal: Actelis Networks, Inc.
312 25 Bazel St., P.O.B. 10173
313 Petach-Tikva 10173
314 Israel
315 Phone: +972-3-924-3491
316 EMail: edward.beili@actelis.com
318 Editor: Narendranath Nair
319 Postal: Wipro Technologies
320 Keonics Electronics City
321 Bangalore 560 100
322 India
323 Phone: +91-99-00-12-96-29
324 EMail: narendranath.nair@wipro.com"
326 DESCRIPTION
327 "The objects in this MIB module are used to manage the
328 multi-pair bonded xDSL Interfaces using ATM inverse
329 multiplexing, defined in ITU-T recommendation G.998.1
330 (G.Bond/ATM).
332 This MIB module MUST be used in conjunction with GBOND-MIB
333 module, common to all G.Bond technologies.
335 The following references are used throughout this MIB module:
337 [WT-159] refers to:
338 DSL Forum Technical Report: 'Management Framework for xDSL
339 Bonding', January 2007.
341 Naming Conventions:
342 BCE - Bonding Channel Entity
343 CO - Central Office
344 CPE - Customer Premises Equipment
345 GBS - Generic Bonding Sublayer
346 SNR - Signal to Noise Ratio
348 Copyright (C) The Internet Society (2007). This version of this
349 MIB module is part of RFC XXXX; see the RFC itself for full
350 legal notices."
352 REVISION "200705140000Z" -- May 14, 2007
353 DESCRIPTION "Initial version, published as RFC XXXX."
355 -- EdNote: Replace XXXX with the actual RFC number and
356 -- remove this note
358 ::= { gBondMIB 1 }
360 -- Sections of the module
361 -- Structured as recommended by RFC 4181, Appendix D
363 gBondAtmObjects OBJECT IDENTIFIER ::= { gBondAtmMIB 1 }
365 gBondAtmConformance OBJECT IDENTIFIER ::= { gBondAtmMIB 2 }
366 -- Groups in the module
368 gBondAtmPort OBJECT IDENTIFIER ::= { gBondAtmObjects 1 }
370 -- Textual Conventions
372 -- Port Notifications Group
374 -- gBondAtmPortNotifications OBJECT IDENTIFIER
375 -- ::= { gBondAtmPort 0 }
377 -- G.Bond ATM Port group
379 gBondAtmPortConfTable OBJECT-TYPE
380 SYNTAX SEQUENCE OF GBondAtmPortConfEntry
381 MAX-ACCESS not-accessible
382 STATUS current
383 DESCRIPTION
384 "Table for Configuration of G.Bond ATM ports. Entries in
385 this table MUST be maintained in a persistent manner"
386 ::= { gBondAtmPort 1 }
388 gBondAtmPortConfEntry OBJECT-TYPE
389 SYNTAX GBondAtmPortConfEntry
390 MAX-ACCESS not-accessible
391 STATUS current
392 DESCRIPTION
393 "An entry in the G.Bond ATM Port Configuration table.
394 Each entry represents an G.Bond ATM port indexed by the
395 ifIndex. Additional configuration parameters are available
396 via the gBondPortConfEntry of GBOND-MIB.
397 Note that an G.Bond ATM port runs on top of a single or
398 multiple BCE port(s), which are also indexed by ifIndex."
399 INDEX { ifIndex }
400 ::= { gBondAtmPortConfTable 1 }
402 GBondAtmPortConfEntry ::=
403 SEQUENCE {
404 -- ATM Port conf Entry
405 gBondAtmUpMaxDataRate Unsigned32,
406 gBondAtmDownMaxDataRate Unsigned32,
407 gBondAtmUpDiffDelayTolerence Unsigned32,
408 gBondAtmDownDiffDelayTolerence Unsigned32
409 }
411 gBondAtmUpMaxDataRate OBJECT-TYPE
412 SYNTAX Unsigned32(1..1000000|9999999)
413 UNITS "Kbps"
414 MAX-ACCESS read-write
415 STATUS current
416 DESCRIPTION
417 "The maximum net upstream data rate a bonding group
418 is allowed to achieve to carry an ATM stream.If set
419 to '9999999', this parameter is ignored."
420 REFERENCE
421 "[G.998.1] Sec. 11.4.1 - (4)"
422 ::= { gBondAtmPortConfEntry 1 }
424 gBondAtmDownMaxDataRate OBJECT-TYPE
425 SYNTAX Unsigned32(1..1000000|9999999)
426 UNITS "Kbps"
427 MAX-ACCESS read-write
428 STATUS current
429 DESCRIPTION
430 "The maximum net downstream data rate a bonding group
431 is allowed to achieve to carry an ATM stream.If set
432 to '9999999', this parameter is ignored."
433 REFERENCE
434 "[G.998.1] Sec. 11.4.1 - (4)"
435 ::= { gBondAtmPortConfEntry 2 }
437 gBondAtmUpDiffDelayTolerence OBJECT-TYPE
438 SYNTAX Unsigned32(0..8176)
439 UNITS "milliseconds"
440 MAX-ACCESS read-write
441 STATUS current
442 DESCRIPTION
443 "The maximum upstream differential delay among member
444 links in a bonding group."
445 REFERENCE
446 "[G.998.1] Sec. 11.4.1 - (6)"
447 ::= { gBondAtmPortConfEntry 3 }
449 gBondAtmDownDiffDelayTolerence OBJECT-TYPE
450 SYNTAX Unsigned32(0..8176)
451 UNITS "milliseconds"
452 MAX-ACCESS read-write
453 STATUS current
454 DESCRIPTION
455 "The maximum downstream differential delay among member
456 links in a bonding group."
457 REFERENCE
458 "[G.998.1] Sec. 11.4.1 - (6)"
459 ::= { gBondAtmPortConfEntry 4 }
461 gBondAtmPortStatusTable OBJECT-TYPE
462 SYNTAX SEQUENCE OF GBondAtmPortStatusEntry
463 MAX-ACCESS not-accessible
464 STATUS current
465 DESCRIPTION
466 "This table provides overall status information of G.Bond
467 ATM ports, complementing the generic status information from
468 the ifTable of IF-MIB and gBondFltStatus of GBOND-MIB.
469 Additional status information about connected BCEs is
470 available from the relevant line MIBs
471 This table contains live data from the equipment. As such,
472 it is NOT persistent."
473 ::= { gBondAtmPort 2 }
475 gBondAtmPortStatusEntry OBJECT-TYPE
476 SYNTAX GBondAtmPortStatusEntry
477 MAX-ACCESS not-accessible
478 STATUS current
479 DESCRIPTION
480 "An entry in the G.Bond ATM port Status table.
481 Each entry represents a G.Bond ATM port indexed by the
482 ifIndex.
483 Note that an G.Bond GBS port runs on top of a single
484 or multiple BCE port(s), which are also indexed by ifIndex."
485 INDEX { ifIndex }
486 ::= { gBondAtmPortStatusTable 1 }
488 GBondAtmPortStatusEntry ::=
489 SEQUENCE {
490 -- ATM Port status entries
491 gBondAtmShowTime TimeTicks,
492 gBondAtmUpRxCellLossCount Counter32,
493 gBondAtmDownRxCellLossCount Counter32
494 }
496 gBondAtmShowTime OBJECT-TYPE
497 SYNTAX TimeTicks
498 UNITS "seconds"
499 MAX-ACCESS read-only
500 STATUS current
501 DESCRIPTION
502 "The accumulated time when a bonding group is in normal
503 operation."
504 REFERENCE
505 "[G.998.1] Sec. 11.4.2 - (3)"
506 ::= { gBondAtmPortStatusEntry 1 }
508 gBondAtmUpRxCellLossCount OBJECT-TYPE
509 SYNTAX Counter32
510 MAX-ACCESS read-only
511 STATUS current
512 DESCRIPTION
513 "The total number of cells that are lost at aggregation
514 output in the upstream direction from a bonding group
515 for the accumulation interval."
516 REFERENCE
517 "[G.998.1] Sec. 11.4.2 - (4)"
518 ::= { gBondAtmPortStatusEntry 2 }
520 gBondAtmDownRxCellLossCount OBJECT-TYPE
521 SYNTAX Counter32
522 MAX-ACCESS read-only
523 STATUS current
524 DESCRIPTION
525 "The total number of cells that are lost at aggregation
526 output in the downstream direction from a bonding
527 group for the accumulation interval."
528 REFERENCE
529 "[G.998.1] Sec. 11.4.2 - (4)"
530 ::= { gBondAtmPortStatusEntry 3 }
532 --
533 -- Conformance Statements
534 --
536 gBondAtmGroups OBJECT IDENTIFIER
537 ::= { gBondAtmConformance 1 }
539 gBondAtmCompliances OBJECT IDENTIFIER
540 ::= { gBondAtmConformance 2 }
542 -- Object Groups
544 gBondAtmBasicGroup OBJECT-GROUP
545 OBJECTS {
546 gBondAtmUpMaxDataRate,
547 gBondAtmDownMaxDataRate,
548 gBondAtmUpDiffDelayTolerence,
549 gBondAtmDownDiffDelayTolerence,
550 gBondAtmShowTime,
551 gBondAtmUpRxCellLossCount,
552 gBondAtmDownRxCellLossCount
553 }
554 STATUS current
555 DESCRIPTION
556 "A collection of objects representing management
557 information for G.Bond ATM ports."
558 ::= { gBondAtmGroups 1 }
560 -- Compliance Statements
562 gBondAtmCompliance MODULE-COMPLIANCE
563 STATUS current
564 DESCRIPTION
565 "The compliance statement for G.Bond ATM interfaces.
566 Compliance with the following external compliance
567 statements
568 is REQUIRED:
570 MIB Module Compliance Statement
571 ---------- --------------------
572 IF-MIB ifCompliance3
573 GBOND-MIB gBondCompliance"
575 MODULE -- this module
576 MANDATORY-GROUPS {
577 gBondAtmBasicGroup
578 }
580 ::= { gBondAtmCompliances 1 }
581 END
583 5. Security Considerations
585 The readable objects in the GBOND-ATM-MIB module (i.e., those with
586 MAX-ACCESS other than not-accessible) may be considered sensitive in
587 some environments since, collectively, they provide information about
588 the performance of network interfaces and can reveal some aspects of
589 their configuration. In particular, since a bonded xDSL port can be
590 comprised of multiple Unshielded Twisted Pair (UTP) voice grade
591 copper, located in the same bundle with other pairs belonging to
592 another operator/customer, it is theoretically possible to eavesdrop
593 to a G.Bond transmission, simply by "listening" to a cross-talk from
594 the bonded pairs, especially if the parameters of the G.Bond link in
595 question are known.
597 In such environments it is important to control also GET and NOTIFY
598 access to these objects and possibly even to encrypt their values
599 when sending them over the network via SNMP.
601 SNMP versions prior to SNMPv3 did not include adequate security.
602 Even if the network itself is secure (for example by using IPSec),
603 even then, there is no control as to who on the secure network is
604 allowed to access and GET/SET (read/change/create/delete) the objects
605 in this MIB module.
607 It is RECOMMENDED that implementers consider the security features as
608 provided by the SNMPv3 framework (see [RFC3410], section 8),
609 including full support for the SNMPv3 cryptographic mechanisms (for
610 authentication and privacy).
612 Further, deployment of SNMP versions prior to SNMPv3 is NOT
613 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
614 enable cryptographic security. It is then a customer/operator
615 responsibility to ensure that the SNMP entity giving access to an
616 instance of this MIB module is properly configured to give access to
617 the objects only to those principals (users) that have legitimate
618 rights to indeed GET or SET (change/create/delete) them.
620 6. Acknowledgments
622 This document was produced by the IETF ADSL MIB Working Group [2].
624 7. References
626 7.1. Normative References
628 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
629 Requirement Levels", BCP 14, RFC 2119, March 1997.
631 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
632 Schoenwaelder, Ed., "Structure of Management Information
633 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
635 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
636 Schoenwaelder, Ed., "Textual Conventions for SMIv2",
637 STD 58, RFC 2579, April 1999.
639 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
640 "Conformance Statements for SMIv2", STD 58, RFC 2580,
641 April 1999.
643 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
644 "Introduction and Applicability Statements for Internet-
645 Standard Management Framework", RFC 3410, December 2002.
647 7.2. Informative References
649 [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
650 (SHDSL) transceivers", ITU-T Recommendation G.991.2,
651 December 2003.
653 [G.993.1] ITU-T, "Very High speed Digital Subscriber Line
654 transceivers", ITU-T Recommendation G.993.1, June 2004.
656 [G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T
657 Recommendation G.998.3, January 2005.
659 [I-D.ietf-adslmib-gbond-mib]
660 Morgenstern, M. and N. Nair, "xDSL multi-pair bonding
661 (G.Bond) MIB", draft-ietf-adslmib-gbond-mib-00 (work in
662 progress), January 2006.
664 [IANAifType-MIB]
665 Internet Assigned Numbers Authority (IANA), "IANAifType
666 Textual Convention definition",
667 http://www.iana.org/assignments/ianaiftype-mib.
669 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
670 MIB", RFC 2863, June 2000.
672 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
673 Extension to the Interfaces Group MIB", RFC 2864,
674 June 2000.
676 [RFC3635] Flick, J., "Definitions of Managed Objects for the
677 Ethernet-like Interface Types", RFC 3635, September 2003.
679 [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
680 Extensions for Very High Speed Digital Subscriber Lines
681 (VDSL) Using Multiple Carrier Modulation (MCM) Line
682 Coding", RFC 4070, May 2005.
684 [RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
685 Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
686 Single-Pair High-Speed Digital Subscriber Line (SHDSL)
687 Lines", RFC 4319, December 2005.
689 [WT-159] Morgenstern, M., Beili, E., and N. Nair, "Management
690 Framework for xDSL Bonding", DSL Forum technical
691 report WT-159, Jan 2006.
693 [af-phy-0086]
694 ATM Forum, "Inverse Multiplexing for ATM (IMA)
695 Specification Version 1.1", ATM Forum specification af-
696 pfy-0086.001, March 1999.
698 URIs
700 [1]
702 [2]
704 Authors' Addresses
706 Edward Beili
707 Actelis Networks
708 25 Bazel St.
709 Petach-Tikva 49103
710 Israel
712 Phone: +972-3-924-3491
713 Email: edward.beili@actelis.com
715 Moti Morgenstern
716 ECI Telecom
717 30 Hasivim St.
718 Petach-Tikva 49517
719 Israel
721 Phone: +972-3-926-6258
722 Email: moti.morgenstern@ecitele.com
724 Narendranath Nair
725 Wipro Technologies
726 Keonics Electronics City
727 Bangalore 560 100
728 India
730 Phone: +91-(0)99 00 12 96 29
731 Email: narendranath.nair@wipro.com
733 Full Copyright Statement
735 Copyright (C) The IETF Trust (2007).
737 This document is subject to the rights, licenses and restrictions
738 contained in BCP 78, and except as set forth therein, the authors
739 retain all their rights.
741 This document and the information contained herein are provided on an
742 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
743 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
744 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
745 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
746 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
747 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
749 Intellectual Property
751 The IETF takes no position regarding the validity or scope of any
752 Intellectual Property Rights or other rights that might be claimed to
753 pertain to the implementation or use of the technology described in
754 this document or the extent to which any license under such rights
755 might or might not be available; nor does it represent that it has
756 made any independent effort to identify any such rights. Information
757 on the procedures with respect to rights in RFC documents can be
758 found in BCP 78 and BCP 79.
760 Copies of IPR disclosures made to the IETF Secretariat and any
761 assurances of licenses to be made available, or the result of an
762 attempt made to obtain a general license or permission for the use of
763 such proprietary rights by implementers or users of this
764 specification can be obtained from the IETF on-line IPR repository at
765 http://www.ietf.org/ipr.
767 The IETF invites any interested party to bring to its attention any
768 copyrights, patents or patent applications, or other proprietary
769 rights that may cover technology that may be required to implement
770 this standard. Please address the information to the IETF at
771 ietf-ipr@ietf.org.
773 Acknowledgment
775 Funding for the RFC Editor function is provided by the IETF
776 Administrative Support Activity (IASA).