idnits 2.17.1
draft-ietf-adslmib-gbond-tdim-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 17.
-- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on
line 1294.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1305.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1312.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1318.
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 (April 29, 2007) is 6206 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)
-- Possible downref: Non-RFC (?) normative reference: ref. 'G.998.3'
** 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
Summary: 2 errors (**), 0 flaws (~~), 3 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 N. Nair
5 Expires: October 31, 2007 Wipro Technologies
6 April 29, 2007
8 xDSL multi-pair bonding using Time-Division Inverse Multiplexing
9 (G.Bond/TDIM) MIB
10 draft-ietf-adslmib-gbond-tdim-mib-00.txt
12 Status of This Memo
14 By submitting this Internet-Draft, each author represents that any
15 applicable patent or other IPR claims of which he or she is aware
16 have been or will be disclosed, and any of which he or she becomes
17 aware will be disclosed, in accordance with Section 6 of BCP 79.
19 Internet-Drafts are working documents of the Internet Engineering
20 Task Force (IETF), its areas, and its working groups. Note that
21 other groups may also distribute working documents as Internet-
22 Drafts.
24 Internet-Drafts are draft documents valid for a maximum of six months
25 and may be updated, replaced, or obsoleted by other documents at any
26 time. It is inappropriate to use Internet-Drafts as reference
27 material or to cite them other than as "work in progress."
29 The list of current Internet-Drafts can be accessed at
30 http://www.ietf.org/ietf/1id-abstracts.txt.
32 The list of Internet-Draft Shadow Directories can be accessed at
33 http://www.ietf.org/shadow.html.
35 This Internet-Draft will expire on October 31, 2007.
37 Copyright Notice
39 Copyright (C) The IETF Trust (2007).
41 Abstract
43 This document defines Management Information Base (MIB) module for
44 use with network management protocols in TCP/IP based internets.
45 This document proposes an extension to the G.Bond MIB module with a
46 set of objects for managing multi-pair bonded xDSL interfaces using
47 Time-Division Inverse Multiplexing (TDIM), defined in ITU-T
48 recommendation G.998.3.
50 Table of Contents
52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
53 2. The Internet-Standard Management Framework . . . . . . . . . . 3
54 3. The DSL Forum Management Framework for xDSL Bonding . . . . . 3
55 4. Relationship to other MIB modules . . . . . . . . . . . . . . 3
56 4.1. Relationship to Interfaces Group MIB module . . . . . . . 4
57 4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4
58 4.3. Relationship to Other MIB modules . . . . . . . . . . . . 4
59 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 4
60 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 4
61 5.2. Protection Configuration . . . . . . . . . . . . . . . . . 4
62 5.3. Service Configuration . . . . . . . . . . . . . . . . . . 4
63 5.3.1. Management of TDM Services . . . . . . . . . . . . . . 5
64 5.4. Mapping of ITU-T G.998.3 Managed Objects . . . . . . . . . 5
65 5.5. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 7
66 6. G.Bond/TDIM MIB Definitions . . . . . . . . . . . . . . . . . 7
67 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25
68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
69 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26
70 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
71 10.1. Normative References . . . . . . . . . . . . . . . . . . . 26
72 10.2. Informative References . . . . . . . . . . . . . . . . . . 27
74 1. Introduction
76 The Multi-pair bonding using time-division inverse multiplexing
77 (TDIM), a.k.a. G.Bond/TDIM, is specified in ITU-T G.998.3
78 recommendation [G.998.3], which defines a method for bonding (or
79 aggregating) of multiple xDSL lines into a single bi-directional
80 logical link carrying a mix of various traffic streams, e.g.
81 Ethernet, Asynchronous Transfer Mode (ATM), Time-Division
82 Multiplexing (TDM).
84 The MIB module, defined in this document, provides G.Bond/TDIM
85 specific objects for the management of G.998.3 bonded interfaces,
86 extending the common bonding objects specified in GBOND-MIB
87 [I-D.ietf-adslmib-gbond-mib] module.
89 2. The Internet-Standard Management Framework
91 For a detailed overview of the documents that describe the current
92 Internet-Standard Management Framework, please refer to section 7 of
93 RFC 3410 [RFC3410].
95 Managed objects are accessed via a virtual information store, termed
96 the Management Information Base or MIB. MIB objects are generally
97 accessed through the Simple Network Management Protocol (SNMP).
98 Objects in the MIB are defined using the mechanisms defined in the
99 Structure of Management Information (SMI). This memo specifies a MIB
100 module that is compliant to the SMIv2, which is described in STD 58,
101 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
102 [RFC2580].
104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
106 document are to be interpreted as described in RFC 2119 [RFC2119].
108 3. The DSL Forum Management Framework for xDSL Bonding
110 This document makes use of the DSL Forum technical report Management
111 Framework for xDSL Bonding [WT-159], defining a management model and
112 a hierarchy of management objects for the bonded xDSL interfaces.
114 4. Relationship to other MIB modules
116 This section outlines the relationship of the MIB modules defined in
117 this document with other MIB modules described in the relevant RFCs.
118 Specifically, the following MIB modules are discussed: Interfaces
119 Group MIB (IF-MIB) and G.Bond MIB (GBOND-MIB).
121 4.1. Relationship to Interfaces Group MIB module
123 A G.Bond/TDIM port is a private case of a Bonded multi-pair xDSL
124 interface and as such is managed using generic interface management
125 objects defined in the IF-MIB [RFC2863]. In particular an interface
126 index (ifIndex) is used to index instances of G.Bond/TDIM ports in a
127 system.
129 4.2. Relationship to G.Bond MIB module
131 GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management
132 objects common for all Bonded multi-pair xDSL interfaces. In
133 particular is describes the bonding management, port and channel
134 configuration, initialization sequence etc.
136 Both GBOND-MIB and GBOND-TDIM-MIB modules are REQUIRED to manage a
137 G.Bond/TDIM port.
139 4.3. Relationship to Other MIB modules
141 _EdNote: Add here services layering model and MIBs for ATM, Ethernet
142 and TDM services. _
144 5. MIB Structure
146 5.1. Overview
148 _EdNote: TBC... _
150 5.2. Protection Configuration
152 G.Bond/TDIM specification allows an optional Forward Error Correction
153 (FEC) and Interleaver block, which, if supported and enabled,
154 provides a degree of protection against micro-interruptions, alien
155 noise, and even individual Bonding Channel Entity (BCE) failures,
156 a.k.a. cut-line protection.
158 Management objects in the gBondTdimPortConfTable can be used to
159 configure and quiery the FEC and Interleaver function of the G.Bond/
160 TDIM port.
162 5.3. Service Configuration
164 Unlike the other two xDSL Multi-Pair Bonding schemes (G.Bond/ATM and
165 G.Bond/Ethernet), which send the information required for reassembly
166 of the fragmented data along with the data, G.Bond/TDIM is a
167 synchronous scheme, requiring both ends to know the data distribution
168 tables before any actual data transfer can happen.
170 Management objects in the gBondTdimServiceTable can be used to
171 configure and quiery the configuration of services transported via
172 the G.Bond/TDIM link. The services may be configured when the link
173 is down prior to the link's initialization. The sum of all the
174 services' bandwidth SHOULD be less or equal to the target data rate
175 of the bonded link. Note that G.Bond/TDIM links are symmetrical,
176 i.e. their upstream data rate equals to the downstream data rate.
178 5.3.1. Management of TDM Services
180 G.Bond/TDIM protocol provides an ability to map TDM services into the
181 TDIM bonded link directly, without any additional overhead. It
182 addresses only structure-agnostic TDM transport, disregarding any
183 structure that may be imposed on these streams, in particular the
184 structure imposed by the standard TDM framing [G.704].
186 _EdNote: Describe service allocation + conection with IfIndex of the
187 service ports, prioritization and notifications. Should we allow
188 dynamic service assignment while the G.Bond/TDIM link is up? Think
189 about Performance Monitoring for services. Think about common things
190 between G.Bond/TDIM and PWE3, may be there's a potential for reuse,
191 see PW-*-MIB modules in
192 http://www.ietf.org/html.charters/pwe3-charter.html _
194 5.4. Mapping of ITU-T G.998.3 Managed Objects
196 This section contains the mapping between relevant managed objects
197 (attributes) defined in [G.998.3] and managed objects defined in this
198 document.
200 +------------------------+--------------------------------------+
201 | G.998.3 Managed Object | Corresponding SNMP Object |
202 +------------------------+--------------------------------------+
203 | oGroup | |
204 +------------------------+--------------------------------------+
205 | aFECSupported | gBondTdimFecSupported |
206 +------------------------+--------------------------------------+
207 | aFECAdminState | gBondTdimFecAdminState |
208 +------------------------+--------------------------------------+
209 | aFECWordSize | gBondTdimFecWordSize |
210 +------------------------+--------------------------------------+
211 | aFECRedundancySize | gBondTdimFecRedundancySize |
212 +------------------------+--------------------------------------+
213 | aFECInterleaverType | gBondTdimFecInterleaverType |
214 +------------------------+--------------------------------------+
215 | aFECInterleaverDepth | gBondTdimFecInterleaverDepth |
216 +------------------------+--------------------------------------+
217 | aFECWordSize | gBondTdimFecMaxWordSize |
218 +------------------------+--------------------------------------+
219 | aFECRedundancySize | gBondTdimFecMaxRedundancySize |
220 +------------------------+--------------------------------------+
221 | aFECInterleaverType | gBondTdimFecInterleaverTypeSupported |
222 +------------------------+--------------------------------------+
223 | aFECInterleaverDepth | gBondTdimFecMaxInterleaverDepth |
224 +------------------------+--------------------------------------+
225 | aCRC4Errors | gBondTdimCrc4Errors |
226 +------------------------+--------------------------------------+
227 | aCRC6Errors | gBondTdimCrc6Errors |
228 +------------------------+--------------------------------------+
229 | aCRC8Errors | gBondTdimCrc8Errors |
230 +------------------------+--------------------------------------+
231 | oService | |
232 +------------------------+--------------------------------------+
233 | aServiceID | gBondTdimServiceIndex |
234 +------------------------+--------------------------------------+
235 | aServiceType | gBondTdimServiceType |
236 +------------------------+--------------------------------------+
237 | aServiceSize | gBondTdimServiceSize |
238 +------------------------+--------------------------------------+
239 | TBC... | TBC... |
240 +------------------------+--------------------------------------+
242 Table 1: Mapping of G.998.3 Managed Objects
244 _EdNote: Finish the table and remove TBC... _
246 5.5. Mapping of DSL Forum WT-159 Managed Objects
248 This section contains the mapping between relevant managed objects
249 (attributes) defined in [WT-159] and managed objects defined in this
250 document.
252 +-----------------------+---------------------------+
253 | WT-159 Managed Object | Corresponding SNMP Object |
254 +-----------------------+---------------------------+
255 | aServiceIfIdx | gBondTdimServiceIfIdx |
256 +-----------------------+---------------------------+
257 | TBC... | TBC... |
258 +-----------------------+---------------------------+
260 Table 2: Mapping of WT-159 Managed Objects
262 _EdNote: Finish the table and remove TBC... make sure aServiceIfIdx
263 is in WT-159. _
265 6. G.Bond/TDIM MIB Definitions
267 GBOND-TDIM-MIB DEFINITIONS ::= BEGIN
269 IMPORTS
270 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
271 Unsigned32, Counter32
272 FROM SNMPv2-SMI -- RFC 2578
273 TEXTUAL-CONVENTION, TruthValue
274 FROM SNMPv2-TC -- RFC 2579
275 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
276 FROM SNMPv2-CONF -- RFC 2580
277 ifIndex, InterfaceIndex
278 FROM IF-MIB -- RFC 2863
279 gBondMIB
280 FROM GBOND-MIB -- RFC YYYY
281 -- EdNote: Replace YYYY with the actual RFC number &
282 -- remove this note
283 ;
285 gBondTdimMIB MODULE-IDENTITY
286 LAST-UPDATED "200704290000Z" -- April 29, 2007
287 ORGANIZATION "IETF ADSL MIB Working Group"
288 CONTACT-INFO
289 "WG charter:
290 http://www.ietf.org/html.charters/adslmib-charter.html
292 Mailing Lists:
293 General Discussion: adslmib@ietf.org
294 To Subscribe: adslmib-request@ietf.org
295 In Body: subscribe your_email_address
297 Chair: Menachem Dodge
298 Postal: ECI Telecom, Ltd.
299 30 Hasivim St.,
300 Petach-Tikva 49517
301 Israel
302 Phone: +972-3-926-8421
303 EMail: menachem.dodge@ecitele.com
305 Editor: Edward Beili
306 Postal: Actelis Networks, Inc.
307 25 Bazel St., P.O.B. 10173
308 Petach-Tikva 10173
309 Israel
310 Phone: +972-3-924-3491
311 EMail: edward.beili@actelis.com
313 Editor: Narendranath Nair
314 Postal: Wipro Technologies
315 Keonics Electronics City
316 Bangalore 560 100
317 India
318 Phone: +91-80-2852-0408 x85338
319 EMail: narendranath.nair@wipro.com"
321 DESCRIPTION
322 "The objects in this MIB module are used to manage the
323 multi-pair bonded xDSL Interfaces using time-division inverse
324 multiplexing (TDIM), defined in ITU-T recommendation G.998.3
325 (G.Bond/TDIM).
327 This MIB module MUST be used in conjunction with GBOND-MIB
328 module, common to all G.Bond technologies.
330 The following references are used throughout this MIB module:
332 [G.998.3] refers to:
333 ITU-T Recommendation G.998.1: 'Multi-pair bonding using
334 time-division inverse multiplexing', January 2005.
336 [WT-159] refers to:
337 DSL Forum Technical Report: 'Management Framework for xDSL
338 Bonding', January 2007.
340 Naming Conventions:
341 BCE - Bonding Channel Entity
342 CO - Central Office
343 CPE - Customer Premises Equipment
344 GBS - Generic Bonding Sublayer
345 SNR - Signal to Noise Ratio
347 Copyright (C) The Internet Society (2007). This version of this
348 MIB module is part of RFC XXXX; see the RFC itself for full
349 legal notices."
351 REVISION "200704290000Z" -- April 29, 2007
352 DESCRIPTION "Initial version, published as RFC XXXX."
354 -- EdNote: Replace XXXX with the actual RFC number &
355 -- remove this note
357 ::= { gBondMIB 3 }
359 -- Sections of the module
360 -- Structured as recommended by RFC 4181, Appendix D
362 gBondTdimObjects OBJECT IDENTIFIER ::= { gBondTdimMIB 1 }
364 gBondTdimConformance OBJECT IDENTIFIER ::= { gBondTdimMIB 2 }
366 -- Groups in the module
368 gBondTdimPort OBJECT IDENTIFIER ::= { gBondTdimObjects 1 }
370 -- Textual Conventions
372 GBondTdimServiceIndex ::= TEXTUAL-CONVENTION
373 DISPLAY-HINT "d"
374 STATUS current
375 DESCRIPTION
376 "A unique value, greater than zero, for each Service defined
377 in the managed G.Bond TDIM port, showing its relative position
378 inside the G.Bond/TDIM frame.
379 It is RECOMMENDED that values are assigned contiguously
380 starting from 1. The value for each Service MUST remain
381 constant at least from one re-initialization of the entity's
382 network management system to the next re-initialization."
383 SYNTAX Unsigned32 (1..60)
385 -- Port Notifications Group
387 gBondTdimPortNotifications OBJECT IDENTIFIER
388 ::= { gBondTdimPort 0 }
390 gBondTdimServiceUp NOTIFICATION-TYPE
391 OBJECTS {
392 -- ifIndex is not needed here since we are under specific GBS
393 gBondTdimServiceIfIdx,
394 gBondTdimServiceOperState
395 }
396 STATUS current
397 DESCRIPTION
398 "This notification indicates that a service indicated by the
399 gBondTdimServiceIfIdx in a particular G.Bond TDIM port' is
400 passing traffic.
402 This notification MAY be send for the G.Bond TDIM port, while
403 the port is Up, when the gBondTdimServiceOperState object has
404 left the Down state.
406 Generation of this notification is controlled by the
407 gBondTdimServiceUpDownEnable object."
408 ::= { gBondTdimPortNotifications 1 }
410 gBondTdimServiceDown NOTIFICATION-TYPE
411 OBJECTS {
412 -- ifIndex is not needed here since we are under specific GBS
413 gBondTdimServiceIfIdx,
414 gBondTdimServiceOperState
415 }
416 STATUS current
417 DESCRIPTION
418 "This notification indicates that a service indicated by the
419 gBondTdimServiceIfIdx in a particular G.Bond TDIM port' has
420 stopped passing the traffic.
422 This notification MAY be send for the G.Bond TDIM port, while
423 the port is Up, when the gBondTdimServiceOperState object has
424 entered the Down state.
426 Generation of this notification is controlled by the
427 gBondTdimServiceUpDownEnable object."
428 ::= { gBondTdimPortNotifications 2 }
430 -- G.Bond TDIM Port group
432 gBondTdimPortConfTable OBJECT-TYPE
433 SYNTAX SEQUENCE OF GBondTdimPortConfEntry
434 MAX-ACCESS not-accessible
435 STATUS current
436 DESCRIPTION
437 "Table for Configuration of G.Bond TDIM ports. Entries in
438 this table MUST be maintained in a persistent manner"
439 ::= { gBondTdimPort 1 }
441 gBondTdimPortConfEntry OBJECT-TYPE
442 SYNTAX GBondTdimPortConfEntry
443 MAX-ACCESS not-accessible
444 STATUS current
445 DESCRIPTION
446 "An entry in the G.Bond TDIM Port Configuration table.
447 Each entry represents an G.Bond TDIM port indexed by the
448 ifIndex. Additional conifguration parameters are available
449 via the gBondPortConfEntry of GBOND-MIB.
450 Note that an G.Bond TDIM port runs on top of a single or
451 multiple BCE port(s), which are also indexed by ifIndex."
452 INDEX { ifIndex }
453 ::= { gBondTdimPortConfTable 1 }
455 GBondTdimPortConfEntry ::=
456 SEQUENCE {
457 gBondTdimFecAdminState TruthValue,
458 gBondTdimFecWordSize Unsigned32,
459 gBondTdimFecRedundancySize Unsigned32,
460 gBondTdimFecInterleaverType INTEGER,
461 gBondTdimFecInterleaverDepth Unsigned32,
462 gBondTdimServiceUpDownEnable TruthValue
463 }
465 gBondTdimFecAdminState OBJECT-TYPE
466 SYNTAX TruthValue
467 MAX-ACCESS read-write
468 STATUS current
469 DESCRIPTION
470 "A desired state of the OPTIONAL Forward Error Correction
471 (FEC) function of the G.Bond TDIM port.
473 A value of 'false' indicates that the FEC function is
474 disabled. A value of 'true' indicates that the FEC SHALL be
475 enabled, if supported by the G.Bond TDIM port, as indicated
476 by the gBondTdimFecSupported object.
478 For the GBS-R ports, the value of this object cannot be
479 changed directly. This value may be changed as a result of
480 writing operation on the gBondTdimFecSupported object of a
481 remote GBS-C.
483 Modifications of this object MUST be performed when the link
484 is Down.
485 Attempts to change this object MUST be rejected (in case of
486 SNMP with the error inconsistentValue), if the link is Up or
487 Initializing or if it is an GBS-R.
489 This object MUST be maintained in a persistent manner.
491 This object maps to G.998.3 attribute aFECAdminState"
492 REFERENCE
493 "[G.998.3] Appendix II, B-X"
494 ::= { gBondTdimPortConfEntry 1 }
496 gBondTdimFecWordSize OBJECT-TYPE
497 SYNTAX Unsigned32(0|20..255)
498 UNITS "octets"
499 MAX-ACCESS read-write
500 STATUS current
501 DESCRIPTION
502 "A FEC code word size in octets for the G.Bond TDIM ports
503 supporting FEC function.
505 This object is read-write for the GBS-C ports and read-only
506 for the GBS-R.
508 A value of zero SHALL be returned if the FEC is disabled
509 (via gBondTdimFecAdminState) or not supported.
511 Changing of the FEC code word size MUST be performed when the
512 FEC enabled link is Down. Attempts to change this object MUST
513 be rejected (In case of SNMP with the error
514 inconsistentValue), if the link is Up or Initializing or the
515 FEC function is disabled/not supported.
517 This object MUST be maintained in a persistent manner.
519 This object maps to G.998.3 attribute aFECWordSize"
520 REFERENCE
521 "[G.998.3] Appendix II, B-XI"
522 ::= { gBondTdimPortConfEntry 2 }
524 gBondTdimFecRedundancySize OBJECT-TYPE
525 SYNTAX Unsigned32(0|2|4|8|16|20)
526 UNITS "octets"
527 MAX-ACCESS read-write
528 STATUS current
529 DESCRIPTION
530 "A FEC redundancy word size in octets for the G.Bond TDIM
531 ports supporting FEC function.
533 This object is read-write for the GBS-C ports and read-only
534 for the GBS-R.
536 A value of zero SHALL be returned if the FEC is disabled
537 (via gBondTdimFecAdminState) or not supported.
539 Changing of the FEC redundancy word size MUST be performed
540 when the FEC enabled link is Down. Attempts to change this
541 object MUST be rejected (In case of SNMP with the error
542 inconsistentValue), if the link is Up or Initializing or the
543 FEC function is disabled/not supported.
545 This object MUST be maintained in a persistent manner.
547 This object maps to G.998.3 attribute aFECRedundancySize"
548 REFERENCE
549 "[G.998.3] Appendix II, B-XII"
550 ::= { gBondTdimPortConfEntry 3 }
552 gBondTdimFecInterleaverType OBJECT-TYPE
553 SYNTAX INTEGER {
554 none(0),
555 block(1),
556 convolution(2)
557 }
558 MAX-ACCESS read-write
559 STATUS current
560 DESCRIPTION
561 "An Interleaver type for the G.Bond TDIM ports supporting
562 FEC function.
564 This object is read-write for the GBS-C ports and read-only
565 for the GBS-R.
567 A value of none(0) SHALL be returned if the FEC is disabled
568 (via gBondTdimFecAdminState) or not supported.
570 Changing of the Interleaver type MUST be performed when the
571 FEC enabled link is Down. Attempts to change this object MUST
572 be rejected (In case of SNMP with the error
573 inconsistentValue), if the link is Up or Initializing or the
574 FEC function is disabled/not supported.
576 This object MUST be maintained in a persistent manner.
578 This object maps to G.998.3 attribute aFECInterleaverType"
579 REFERENCE
580 "[G.998.3] Appendix II, B-XIII"
581 ::= { gBondTdimPortConfEntry 4 }
583 gBondTdimFecInterleaverDepth OBJECT-TYPE
584 SYNTAX Unsigned32(0|1|2|3|4|6|8|12|16|24|32|48|96)
585 MAX-ACCESS read-write
586 STATUS current
587 DESCRIPTION
588 "An Interleaver Depth for the G.Bond TDIM ports supporting
589 FEC function.
591 This object is read-write for the GBS-C ports and read-only
592 for the GBS-R.
594 A value of zero SHALL be returned if the FEC is disabled
595 (via gBondTdimFecAdminState) or not supported.
597 Changing of the Interleaver Depth MUST be performed when the
598 FEC enabled link is Down. Attempts to change this object MUST
599 be rejected (In case of SNMP with the error
600 inconsistentValue), if the link is Up or Initializing or the
601 FEC function is disabled/not supported.
603 This object MUST be maintained in a persistent manner.
605 This object maps to G.998.3 attribute aFECInterleaverDepth"
606 REFERENCE
607 "[G.998.3] Appendix II, B-XIV"
608 ::= { gBondTdimPortConfEntry 5 }
610 gBondTdimServiceUpDownEnable OBJECT-TYPE
611 SYNTAX TruthValue
612 MAX-ACCESS read-write
613 STATUS current
614 DESCRIPTION
615 "Indicates whether gBondTdimServiceUp and gBondTdimServiceDown
616 notifications should be generated for this interface.
618 Value of true(1) indicates that the notifications are enabled.
619 Value of false(2) indicates that the notifications are
620 disabled.
622 This object MUST be maintained in a persistent manner."
623 ::= { gBondTdimPortConfEntry 6 }
625 gBondTdimPortCapabilityTable OBJECT-TYPE
626 SYNTAX SEQUENCE OF GBondTdimPortCapabilityEntry
627 MAX-ACCESS not-accessible
628 STATUS current
629 DESCRIPTION
630 "Table for Capabilities of G.Bond TDIM ports. Entries in this
631 table MUST be maintained in a persistent manner"
632 ::= { gBondTdimPort 2 }
634 gBondTdimPortCapabilityEntry OBJECT-TYPE
635 SYNTAX GBondTdimPortCapabilityEntry
636 MAX-ACCESS not-accessible
637 STATUS current
638 DESCRIPTION
639 "An entry in the G.Bond TDIM port Capability table.
640 Each entry represents an G.Bond TDIM port indexed by the
641 ifIndex. Additional capabilities are available via the
642 gBondPortCapabilityEntry of GBOND-MIB.
643 Note that a G.Bond TDIM port runs on top of a single
644 or multiple BCE port(s), which are also indexed by ifIndex."
645 INDEX { ifIndex }
646 ::= { gBondTdimPortCapabilityTable 1 }
648 GBondTdimPortCapabilityEntry ::=
649 SEQUENCE {
650 gBondTdimFecSupported TruthValue,
651 gBondTdimFecMaxWordSize Unsigned32,
652 gBondTdimFecMaxRedundancySize Unsigned32,
653 gBondTdimFecInterleaverTypeSupported INTEGER,
654 gBondTdimFecMaxInterleaverDepth Unsigned32
655 }
657 gBondTdimFecSupported OBJECT-TYPE
658 SYNTAX TruthValue
659 MAX-ACCESS read-only
660 STATUS current
661 DESCRIPTION
662 "FEC and Interleaver Capability of the G.Bond/TDIM port.
663 This object has a value of true(1) when the port supports the
664 FEC and Interleaver function.
665 A value of false(2) is returned when the port does not
666 support the FEC and Interleaver function.
668 This object maps to the G.998.3 attribute aFECSupported."
669 REFERENCE
670 "[G.998.3] Appendix II, B-VI"
671 ::= { gBondTdimPortCapabilityEntry 1 }
673 gBondTdimFecMaxWordSize OBJECT-TYPE
674 SYNTAX Unsigned32(0|20..255)
675 UNITS "octets"
676 MAX-ACCESS read-only
677 STATUS current
678 DESCRIPTION
679 "A Maximum supported FEC code word size in octets for the
680 G.Bond TDIM ports with FEC function.
682 A value of zero SHALL be returned if the FEC is not supported.
684 This object partially maps to G.998.3 attribute aFECWordSize"
685 REFERENCE
686 "[G.998.3] Appendix II, B-XI"
687 ::= { gBondTdimPortCapabilityEntry 2 }
689 gBondTdimFecMaxRedundancySize OBJECT-TYPE
690 SYNTAX Unsigned32(0|2|4|8|16|20)
691 UNITS "octets"
692 MAX-ACCESS read-only
693 STATUS current
694 DESCRIPTION
695 "A Maximum supported FEC redundancy word size in octets for
696 the G.Bond TDIM ports with FEC function.
698 A value of zero SHALL be returned if the FEC is not supported.
700 This object partially maps to G.998.3 attribute
701 aFECRedundancySize"
702 REFERENCE
703 "[G.998.3] Appendix II, B-XII"
704 ::= { gBondTdimPortCapabilityEntry 3 }
706 gBondTdimFecInterleaverTypeSupported OBJECT-TYPE
707 SYNTAX INTEGER {
708 none(0),
709 block(1),
710 convolution(2),
711 blockConvolution(3)
712 }
713 MAX-ACCESS read-only
714 STATUS current
715 DESCRIPTION
716 "Suported Interleaver types for the G.Bond TDIM ports with
717 FEC function.
719 Possible values are:
720 none - the port does not support interleaving
721 block - the port supports Block Interleaver
722 convolution - the port supports Convolution Interleaver
723 blockConvolution - the port supports both Block and
724 Convolution Interleaver
726 This object partially maps to G.998.3 attribute
727 aFECInterleaverType"
728 REFERENCE
729 "[G.998.3] Appendix II, B-XIII"
730 ::= { gBondTdimPortCapabilityEntry 4 }
732 gBondTdimFecMaxInterleaverDepth OBJECT-TYPE
733 SYNTAX Unsigned32(0|1|2|3|4|6|8|12|16|24|32|48|96)
734 MAX-ACCESS read-only
735 STATUS current
736 DESCRIPTION
737 "A Maximum Interleaver Depth for the G.Bond TDIM ports with
738 FEC function.
740 A value of zero SHALL be returned if the Interleaver is not
741 supported.
743 This object partially maps to G.998.3 attribute
744 aFECInterleaverDepth"
745 REFERENCE
746 "[G.998.3] Appendix II, B-XIV"
747 ::= { gBondTdimPortCapabilityEntry 5 }
749 gBondTdimPortStatusTable OBJECT-TYPE
750 SYNTAX SEQUENCE OF GBondTdimPortStatusEntry
751 MAX-ACCESS not-accessible
752 STATUS current
753 DESCRIPTION
754 "This table provides overall status information of G.Bond
755 TDIM ports, complementing the generic status information from
756 the ifTable of IF-MIB and gBondFltStatus of GBOND-MIB.
757 Additional status information about connected BCEs is
758 available from the relevant line MIBs
760 This table contains live data from the equibcent. As such,
761 it is NOT persistent."
762 ::= { gBondTdimPort 3 }
764 gBondTdimPortStatusEntry OBJECT-TYPE
765 SYNTAX GBondTdimPortStatusEntry
766 MAX-ACCESS not-accessible
767 STATUS current
768 DESCRIPTION
769 "An entry in the G.Bond TDIM port Status table.
770 Each entry represents a G.Bond TDIM port indexed by the
771 ifIndex.
772 Note that an G.Bond GBS port runs on top of a single
773 or multiple BCE port(s), which are also indexed by ifIndex."
774 INDEX { ifIndex }
775 ::= { gBondTdimPortStatusTable 1 }
777 GBondTdimPortStatusEntry ::=
778 SEQUENCE {
779 gBondTdimCrc4Errors Counter32,
780 gBondTdimCrc6Errors Counter32,
781 gBondTdimCrc8Errors Counter32,
782 gBondTdimFltStatus BITS
783 }
785 gBondTdimCrc4Errors OBJECT-TYPE
786 SYNTAX Counter32
787 MAX-ACCESS read-only
788 STATUS current
789 DESCRIPTION
790 "The total number of CRC-4 errors (frame header error) on all
791 pairs in the G.Bond TDIM port. Simultaneous errors on M lines
792 SHOULD be counted M times.
794 This object maps to G.998.3 attribute aCRC4Errors.
796 Discontinuities in the value of this counter can occur at
797 re-initialization of the management system, and at other times
798 as indicated by the value of ifCounterDiscontinuityTime,
799 defined in IF-MIB."
800 REFERENCE
801 "[G.998.3] Appendix II, B-VII"
802 ::= { gBondTdimPortStatusEntry 1 }
804 gBondTdimCrc6Errors OBJECT-TYPE
805 SYNTAX Counter32
806 MAX-ACCESS read-only
807 STATUS current
808 DESCRIPTION
809 "The total number of CRC-6 errors (super-frame error) on all
810 pairs in the G.Bond TDIM port. Simultaneous errors on M lines
811 SHOULD be counted 1 time.
813 This object maps to G.998.3 attribute aCRC6Errors.
815 Discontinuities in the value of this counter can occur at
816 re-initialization of the management system, and at other times
817 as indicated by the value of ifCounterDiscontinuityTime,
818 defined in IF-MIB."
819 REFERENCE
820 "[G.998.3] Appendix II, B-VIII"
822 ::= { gBondTdimPortStatusEntry 2 }
824 gBondTdimCrc8Errors OBJECT-TYPE
825 SYNTAX Counter32
826 MAX-ACCESS read-only
827 STATUS current
828 DESCRIPTION
829 "The total number of CRC-8 errors (event/message error) on all
830 pairs in the G.Bond TDIM port. Simultaneous errors on M lines
831 SHOULD be counted M times.
833 This object maps to G.998.3 attribute aCRC8Errors.
835 Discontinuities in the value of this counter can occur at
836 re-initialization of the management system, and at other times
837 as indicated by the value of ifCounterDiscontinuityTime,
838 defined in IF-MIB."
839 REFERENCE
840 "[G.998.3] Appendix II, B-IX"
841 ::= { gBondTdimPortStatusEntry 3 }
843 gBondTdimFltStatus OBJECT-TYPE
844 SYNTAX BITS {
845 serviceDown(0),
846 wrongConfig(1)
847 }
848 MAX-ACCESS read-only
849 STATUS current
850 DESCRIPTION
851 "G.Bond TDIM port Fault Status. This is a bitmap of possible
852 conditions. The various bit positions are:
853 serviceDown - at least one of the services defined
854 for this aggregation group is down
855 (due to low rate).
856 wrongConfig - at least one BCE at the remote GBS-R
857 is already connected to another GBS.
859 This object is intended to supplement ifOperStatus object
860 in IF-MIB and gBondFltStatus in GBOND-MIB."
861 REFERENCE
862 "G.998.3 Section 6.3;
863 IF-MIB, ifOperStatus; GBOND-MIB, gBondFltStatus"
864 ::= { gBondTdimPortStatusEntry 4 }
866 gBondTdimServiceTable OBJECT-TYPE
867 SYNTAX SEQUENCE OF GBondTdimServiceEntry
868 MAX-ACCESS not-accessible
869 STATUS current
870 DESCRIPTION
871 "Table of Services in G.Bond TDIM ports.
872 Entries in this table MUST be maintained in a persistent
873 manner"
874 ::= { gBondTdimPort 4 }
876 gBondTdimServiceEntry OBJECT-TYPE
877 SYNTAX GBondTdimServiceEntry
878 MAX-ACCESS not-accessible
879 STATUS current
880 DESCRIPTION
881 "An entry in the G.Bond TDIM Port Service table, containing
882 the management information applicable to a particular Service
883 in a G.Bond TDIM port, indexed by the gBondTdimServiceIdx."
884 INDEX { gBondTdimServiceIdx }
885 ::= { gBondTdimServiceTable 1 }
887 GBondTdimServiceEntry ::=
888 SEQUENCE {
889 gBondTdimServiceIdx GBondTdimServiceIndex,
890 gBondTdimServiceIfIdx InterfaceIndex,
891 gBondTdimServiceType INTEGER,
892 gBondTdimServiceSize Unsigned32,
893 gBondTdimServiceOperState INTEGER
894 }
896 gBondTdimServiceIdx OBJECT-TYPE
897 SYNTAX GBondTdimServiceIndex
898 MAX-ACCESS not-accessible
899 STATUS current
900 DESCRIPTION
901 "G.Bond TDIM Service index - a unique index associated with
902 a particular service entry, indicating relative placement of
903 the service inside the G.Bond/TDIM frame.
905 There can be up to 60 services defined over TDIM bonded
906 facility. Services with lower indices have higher priority in
907 case of bandwidth degradation.
909 This objects maps to G.998.3 attribute aServiceID."
910 REFERENCE
911 "[G.998.3] Appendix II, C-I"
912 ::= { gBondTdimServiceEntry 1 }
914 gBondTdimServiceIfIdx OBJECT-TYPE
915 SYNTAX InterfaceIndex
916 MAX-ACCESS read-write
917 STATUS current
918 DESCRIPTION
919 "This is a unique index within the ifTable. It represents
920 the interface index of a service to be transmitted over the
921 G.Bond/TDIM service instance.
923 This objects maps to WT-159 attribute aServiceIfIndex."
924 REFERENCE
925 "[WT-159] ZZZ"
926 -- EdNote: update WT-159 and replace ZZZ and aServiceIfIndex
927 -- with exact references
928 ::= { gBondTdimServiceEntry 2 }
930 gBondTdimServiceType OBJECT-TYPE
931 SYNTAX INTEGER {
932 ds1(0),
933 e1(1),
934 nxds0(2),
935 nxe0(3),
936 ds3(4),
937 e3(5),
938 clock(6),
939 ethernet(7),
940 atm(8),
941 gfpNoFCS(9),
942 gfp(10)
943 }
944 MAX-ACCESS read-write
945 STATUS current
946 DESCRIPTION
947 "G.Bond TDIM Service Type.
949 Possible values are:
950 ds1 - Clear Channel DS1 (synchronous)
951 e1 - Clear Channel E1 (synchronous)
952 nxds0 - Fractional DS1 (synchronous)
953 nxe0 - Fractional E1 (synchronous)
954 ds3 - DS3 (synchronous)
955 e3 - E3 (synchronous)
956 clock - Clock transfer (synchronous)
957 ethernet - Ethernet (asynchronous)
958 atm - ATM (asynchronous)
959 gfpNoFCS - GFP encapsulated without FCS (asynchronous)
960 gfp - GFP encapsulated with FCS (asynchronous)
962 For the GBS-R ports, the value of this object cannot be
963 changed directly. This value may be changed as a result of
964 writing operation on the gBondTdimServiceType object of a
965 remote GBS-C.
967 Modifications of this object MUST be performed when the link
968 is Down.
969 Attempts to change this object MUST be rejected (in case of
970 SNMP with the error inconsistentValue), if the link is Up or
971 Initializing or if it is an GBS-R.
973 This object MUST be maintained in a persistent manner.
975 This object maps to G.998.3 attribute aServiceType"
976 REFERENCE
977 "[G.998.3] Appendix II, C-II"
978 ::= { gBondTdimServiceEntry 3 }
980 gBondTdimServiceSize OBJECT-TYPE
981 SYNTAX Unsigned32(0|20..255)
982 UNITS "octets"
983 MAX-ACCESS read-write
984 STATUS current
985 DESCRIPTION
986 "Service size in octets per bonding sub-block for a specific
987 service identified by gBondTdimServiceIdx.
989 For TDM (synchronous) services with variable size
990 e.g. fractional DS1/E1 - this object represents the number of
991 DS0/E0 channels.
992 For asynchronous services (Ethernet, ATM, GFPnoFCS or GFP) -
993 this object represents max. number of octets.
995 A GET operation returns current value.
996 A SET operation, allowed on GBS-C only when the link is Down,
997 changes the service size to the indicated value. If the link
998 is not down or the service type is fixed rate TDM service
999 (gBondTdimServiceType is NxDS0, NxE0, DS1, E1, DS3, E3 or
1000 Clock), the operation MUST be rejected (in case of SNMP with
1001 the error inconsistentValue).
1003 This object MUST be maintained in a persistent manner.
1005 This object maps to G.998.3 attribute aServiceSize"
1006 REFERENCE
1007 "[G.998.3] Appendix II, C-III"
1008 ::= { gBondTdimServiceEntry 4 }
1010 gBondTdimServiceOperState OBJECT-TYPE
1011 SYNTAX INTEGER {
1012 up(1),
1013 down(2)
1014 }
1015 MAX-ACCESS read-only
1016 STATUS current
1017 DESCRIPTION
1018 "G.Bond TDIM Service Operation State.
1020 Possible values are:
1021 up - Service is up passing traffic.
1022 down - Service is down, due to a variety of
1023 reasons, e.g. G.Bond TDIM port is
1024 down, current link bandwidth is too
1025 low to support a particular service,
1026 etc."
1027 REFERENCE
1028 "[G.998.3] 10.2.3"
1029 ::= { gBondTdimServiceEntry 5 }
1031 --
1032 -- Conformance Statements
1033 --
1035 gBondTdimGroups OBJECT IDENTIFIER
1036 ::= { gBondTdimConformance 1 }
1038 gBondTdimCompliances OBJECT IDENTIFIER
1039 ::= { gBondTdimConformance 2 }
1041 -- Object Groups
1043 gBondTdimBasicGroup OBJECT-GROUP
1044 OBJECTS {
1045 gBondTdimCrc4Errors,
1046 gBondTdimCrc6Errors,
1047 gBondTdimCrc8Errors,
1048 gBondTdimFecSupported,
1049 gBondTdimServiceIfIdx,
1050 gBondTdimServiceType,
1051 gBondTdimServiceSize,
1052 gBondTdimServiceOperState,
1053 gBondTdimServiceUpDownEnable,
1054 gBondTdimFltStatus
1055 }
1056 STATUS current
1057 DESCRIPTION
1058 "A collection of objects representing management information
1059 for G.Bond TDIM ports."
1061 ::= { gBondTdimGroups 1 }
1063 gBondTdimFecGroup OBJECT-GROUP
1064 OBJECTS {
1065 gBondTdimFecSupported,
1066 gBondTdimFecAdminState,
1067 gBondTdimFecWordSize,
1068 gBondTdimFecRedundancySize,
1069 gBondTdimFecInterleaverType,
1070 gBondTdimFecInterleaverDepth,
1071 gBondTdimFecMaxWordSize,
1072 gBondTdimFecMaxRedundancySize,
1073 gBondTdimFecInterleaverTypeSupported,
1074 gBondTdimFecMaxInterleaverDepth
1075 }
1076 STATUS current
1077 DESCRIPTION
1078 "A collection of objects supporting OPTIONAL Forward Error
1079 Correction (FEC) and Interleaver function in G.Bond TDIM
1080 ports."
1081 ::= { gBondTdimGroups 2 }
1083 gBondTdimAlarmConfGroup OBJECT-GROUP
1084 OBJECTS {
1085 gBondTdimServiceUpDownEnable
1086 }
1087 STATUS current
1088 DESCRIPTION
1089 "A collection of objects required for configuration of alarm
1090 thresholds and notifications in G.Bond TDIM ports."
1091 ::= { gBondTdimGroups 3 }
1093 gBondTdimNotificationGroup NOTIFICATION-GROUP
1094 NOTIFICATIONS {
1095 gBondTdimServiceUp,
1096 gBondTdimServiceDown
1097 }
1098 STATUS current
1099 DESCRIPTION
1100 "This group supports notifications of significant conditions
1101 associated with G.Bond TDIM ports."
1102 ::= { gBondTdimGroups 4 }
1104 -- Compliance Statements
1106 gBondTdimCompliance MODULE-COMPLIANCE
1107 STATUS current
1108 DESCRIPTION
1109 "The compliance statement for G.Bond TDIM interfaces.
1110 Compliance with the following external compliance statements
1111 is REQUIRED:
1113 MIB Module Compliance Statement
1114 ---------- --------------------
1115 IF-MIB ifCompliance3
1116 GBOND-MIB gBondCompliance"
1118 MODULE -- this module
1119 MANDATORY-GROUPS {
1120 gBondTdimBasicGroup,
1121 gBondTdimAlarmConfGroup,
1122 gBondTdimNotificationGroup
1123 }
1125 GROUP gBondTdimFecGroup
1126 DESCRIPTION
1127 "Support for this group is only required for implementations
1128 supporting G.Bond FEC and Interleaver function."
1130 ::= { gBondTdimCompliances 1 }
1131 END
1133 7. Security Considerations
1135 There is a number of managed objects defined in the GBOND-TDIM-MIB
1136 module that have a MAX-ACCESS clause of read-write or read-create.
1137 Most objects are writeable only when the link is Down. Writing to
1138 these objects can have potentially disruptive effects on network
1139 operation, for example:
1141 o Changing of gBondTdimServiceTable configuration paratemers (e.g.
1142 gBondTdimServiceType or gBondTdimServiceSize) MAY lead to a
1143 potential service impairment, for example a TDM service would be
1144 dropped if there's not enough actual bandwidth on the bonded link
1145 to support this service.
1147 o Changing of gBondTdimPortConfTable configuration parameters (e.g.
1148 gBondTdimFecAdminState) MAY lead to anything from link quality and
1149 rate degradation to a complete link initialization failure.
1151 The user of the GBOND-TDIM-MIB module must therefore be aware that
1152 support for SET operations in a non-secure environment without proper
1153 protection can have a negative effect on network operations.
1155 The readable objects in the GBOND-TDIM-MIB module (i.e., those with
1156 MAX-ACCESS other than not-accessible) may be considered sensitive in
1157 some environments since, collectively, they provide information about
1158 the performance of network interfaces and can reveal some aspects of
1159 their configuration.
1161 In such environments it is important to control also GET and NOTIFY
1162 access to these objects and possibly even to encrypt their values
1163 when sending them over the network via SNMP.
1165 SNMP versions prior to SNMPv3 did not include adequate security.
1166 Even if the network itself is secure (for example by using IPSec),
1167 even then, there is no control as to who on the secure network is
1168 allowed to access and GET/SET (read/change/create/delete) the objects
1169 in this MIB module.
1171 It is RECOMMENDED that implementers consider the security features as
1172 provided by the SNMPv3 framework (see [RFC3410], section 8),
1173 including full support for the SNMPv3 cryptographic mechanisms (for
1174 authentication and privacy).
1176 Further, deployment of SNMP versions prior to SNMPv3 is NOT
1177 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
1178 enable cryptographic security. It is then a customer/operator
1179 responsibility to ensure that the SNMP entity giving access to an
1180 instance of this MIB module is properly configured to give access to
1181 the objects only to those principals (users) that have legitimate
1182 rights to indeed GET or SET (change/create/delete) them.
1184 8. IANA Considerations
1186 A new IANAifType value of g9983 SHALL be defined by the IANA [1] in
1187 the IANAifType-MIB module [IANAifType-MIB], before this document is
1188 published as an RFC.
1190 9. Acknowledgments
1192 This document was produced by the IETF ADSL MIB Working Group [2].
1194 10. References
1196 10.1. Normative References
1198 [G.998.3] ITU-T, "Multi-pair bonding using time-
1199 division inverse multiplexing", ITU-T
1200 Recommendation G.998.3, January 2005.
1202 [RFC2119] Bradner, S., "Key words for use in RFCs
1203 to Indicate Requirement Levels",
1204 BCP 14, RFC 2119, March 1997.
1206 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
1207 and J. Schoenwaelder, Ed., "Structure
1208 of Management Information Version 2
1209 (SMIv2)", STD 58, RFC 2578, April 1999.
1211 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed.,
1212 and J. Schoenwaelder, Ed., "Textual
1213 Conventions for SMIv2", STD 58,
1214 RFC 2579, April 1999.
1216 [RFC2580] McCloghrie, K., Perkins, D., and J.
1217 Schoenwaelder, "Conformance Statements
1218 for SMIv2", STD 58, RFC 2580,
1219 April 1999.
1221 [RFC3410] Case, J., Mundy, R., Partain, D., and
1222 B. Stewart, "Introduction and
1223 Applicability Statements for Internet-
1224 Standard Management Framework",
1225 RFC 3410, December 2002.
1227 [WT-159] Morgenstern, M., Beili, E., and N.
1228 Nair, "Management Framework for xDSL
1229 Bonding", DSL Forum technical
1230 report WT-159, Jan 2007.
1232 10.2. Informative References
1234 [G.704] ITU-T, "Synchronous frame structures
1235 used at 1544, 6312, 2048, 8448 and
1236 44736 Kbit/s hierarchical levels.",
1237 ITU-T Recommendation G.704,
1238 October 1998.
1240 [I-D.ietf-adslmib-gbond-mib] Beili, E., Morgenstern, M., and N.
1241 Nair, "xDSL multi-pair bonding (G.Bond)
1242 MIB", draft-ietf-adslmib-gbond-mib-00
1243 (work in progress), February 2007.
1245 [IANAifType-MIB] Internet Assigned Numbers Authority
1246 (IANA), "IANAifType Textual Convention
1247 definition", http://www.iana.org/
1248 assignments/ianaiftype-mib.
1250 [RFC2863] McCloghrie, K. and F. Kastenholz, "The
1251 Interfaces Group MIB", RFC 2863,
1252 June 2000.
1254 URIs
1256 [1]
1258 [2]
1260 Authors' Addresses
1262 Edward Beili
1263 Actelis Networks
1264 25 Bazel St.
1265 Petach-Tikva 49103
1266 Israel
1268 Phone: +972-3-924-3491
1269 EMail: edward.beili@actelis.com
1271 Narendranath Nair
1272 Wipro Technologies
1273 Keonics Electronics City
1274 Bangalore 560 100
1275 India
1277 Phone: +91-80-2852-0408 x85338
1278 EMail: narendranath.nair@wipro.com
1280 Full Copyright Statement
1282 Copyright (C) The IETF Trust (2007).
1284 This document is subject to the rights, licenses and restrictions
1285 contained in BCP 78, and except as set forth therein, the authors
1286 retain all their rights.
1288 This document and the information contained herein are provided on an
1289 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1290 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1291 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1292 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1293 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1294 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1296 Intellectual Property
1298 The IETF takes no position regarding the validity or scope of any
1299 Intellectual Property Rights or other rights that might be claimed to
1300 pertain to the implementation or use of the technology described in
1301 this document or the extent to which any license under such rights
1302 might or might not be available; nor does it represent that it has
1303 made any independent effort to identify any such rights. Information
1304 on the procedures with respect to rights in RFC documents can be
1305 found in BCP 78 and BCP 79.
1307 Copies of IPR disclosures made to the IETF Secretariat and any
1308 assurances of licenses to be made available, or the result of an
1309 attempt made to obtain a general license or permission for the use of
1310 such proprietary rights by implementers or users of this
1311 specification can be obtained from the IETF on-line IPR repository at
1312 http://www.ietf.org/ipr.
1314 The IETF invites any interested party to bring to its attention any
1315 copyrights, patents or patent applications, or other proprietary
1316 rights that may cover technology that may be required to implement
1317 this standard. Please address the information to the IETF at
1318 ietf-ipr@ietf.org.
1320 Acknowledgement
1322 Funding for the RFC Editor function is provided by the IETF
1323 Administrative Support Activity (IASA).