draft-ietf-adslmib-gbond-tdim-mib-05.txt   draft-ietf-adslmib-gbond-tdim-mib-06.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Intended status: Standards Track March 14, 2011 Intended status: Standards Track May 26, 2011
Expires: September 15, 2011 Expires: November 27, 2011
xDSL multi-pair bonding using Time-Division Inverse Multiplexing xDSL multi-pair bonding using Time-Division Inverse Multiplexing
(G.Bond/TDIM) MIB (G.Bond/TDIM) MIB
draft-ietf-adslmib-gbond-tdim-mib-05.txt draft-ietf-adslmib-gbond-tdim-mib-06.txt
Abstract Abstract
This document defines Management Information Base (MIB) module for This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP based internets.
This document proposes an extension to the GBOND-MIB module with a This document proposes an extension to the GBOND-MIB module with a
set of objects for managing multi-pair bonded xDSL interfaces using set of objects for managing multi-pair bonded xDSL interfaces using
Time-Division Inverse Multiplexing (TDIM), defined in ITU-T Time-Division Inverse Multiplexing (TDIM), defined in ITU-T
recommendation G.998.3. recommendation G.998.3.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 15, 2011. This Internet-Draft will expire on November 27, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 36 skipping to change at page 3, line 36
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
3. The Broadband Forum Management Framework for xDSL Bonding 3. The Broadband Forum Management Framework for xDSL Bonding
This document makes use of the Broadband Forum technical report This document makes use of the Broadband Forum technical report
Management Framework for xDSL Bonding [TR-159], defining a management Management Framework for xDSL Bonding [TR-159], defining a management
model and a hierarchy of management objects for the bonded xDSL model and a hierarchy of management objects for the bonded xDSL
interfaces. interfaces.
4. Relationship to other MIB modules 4. Relationship to other MIB modules
skipping to change at page 5, line 14 skipping to change at page 5, line 14
5.2. Link Protection Configuration 5.2. Link Protection Configuration
G.Bond/TDIM specification allows an optional Forward Error Correction G.Bond/TDIM specification allows an optional Forward Error Correction
(FEC) and Interleaver block, which, if supported and enabled, (FEC) and Interleaver block, which, if supported and enabled,
provides a degree of protection against micro-interruptions, alien provides a degree of protection against micro-interruptions, alien
noise, and even individual Bonding Channel Entity (BCE) failures, noise, and even individual Bonding Channel Entity (BCE) failures,
a.k.a. cut-line protection. a.k.a. cut-line protection.
Management objects in the gBondTdimPortConfTable can be used to Management objects in the gBondTdimPortConfTable can be used to
configure and quiery the FEC and Interleaver function of the G.Bond/ configure and query the FEC and Interleaver function of the G.Bond/
TDIM port. TDIM port.
5.3. Service Configuration 5.3. Service Configuration
Unlike the other two xDSL Multi-Pair Bonding schemes (G.Bond/ATM and Unlike the other two xDSL Multi-Pair Bonding schemes (G.Bond/ATM and
G.Bond/Ethernet), which send the information required for reassembly G.Bond/Ethernet), which send the information required for reassembly
of the fragmented data along with the data, G.Bond/TDIM is a of the fragmented data along with the data, G.Bond/TDIM is a
synchronous scheme, requiring both ends to know the data distribution synchronous scheme, requiring both ends to know the data distribution
tables before any actual data transfer can happen. tables before any actual data transfer can happen.
Management objects in the gBondTdimPortConfTable Management objects in the gBondTdimPortConfTable
(gBondTdimAdminServices), gBondTdimServiceTable and (gBondTdimAdminServices), gBondTdimServiceTable and
gBondTdimOperServiceTable can be used to configure and quiery the gBondTdimOperServiceTable can be used to configure and query the
configuration of services transported via the G.Bond/TDIM link. The configuration of services transported via the G.Bond/TDIM link. The
services may be configured independently of the link state (i.e. in- services may be configured independently of the link state (i.e. in-
and out-of-service), as G.998.3 communicates changes in the service and out-of-service), as G.998.3 communicates changes in the service
configuration via specific Bonding Communication Channel (BCC) configuration via specific Bonding Communication Channel (BCC)
messages, switching both ends of the link to the new configuration messages, switching both ends of the link to the new configuration
synchronously. synchronously.
There can be up to 60 active services defined on a G.Bond/TDIM link. There can be up to 60 active services defined on a G.Bond/TDIM link.
This MIB module provides an ability to define up to 255 services via This MIB module provides an ability to define up to 255 services via
the gBondTdimServiceTable, with each row representing a possible the gBondTdimServiceTable, with each row representing a possible
skipping to change at page 9, line 17 skipping to change at page 9, line 17
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfIntervalCount, HCPerfIntervalCount,
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed HCPerfTimeElapsed
FROM HC-PerfHist-TC-MIB -- [RFC3705] FROM HC-PerfHist-TC-MIB -- [RFC3705]
; ;
------------------------------------------------------------------------ ------------------------------------------------------------------------
gBondTdimMIB MODULE-IDENTITY gBondTdimMIB MODULE-IDENTITY
LAST-UPDATED "201103140000Z" -- Mar 14, 2011 LAST-UPDATED "201105260000Z" -- May 26, 2011
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/adslmib-charter.html http://www.ietf.org/html.charters/adslmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: adslmib@ietf.org General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 10, line 28 skipping to change at page 10, line 28
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer GBS - Generic Bonding Sublayer
GBS-C - Generic Bonded Sub-layer, CO side GBS-C - Generic Bonded Sub-layer, CO side
GBS-R - Generic Bonded Sub-layer, RT (or CPE) side GBS-R - Generic Bonded Sub-layer, RT (or CPE) side
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
Copyright (C) The IETF Trust (2011). Copyright (C) The IETF Trust (2011).
This version of this MIB module is part of RFC YYYY; This version of this MIB module is part of RFC YYYY;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "201103140000Z" -- Mar 14, 2011 REVISION "201105260000Z" -- May 26, 2011
DESCRIPTION "Initial version, published as RFC YYYY." DESCRIPTION "Initial version, published as RFC YYYY."
-- EdNote: Replace YYYY with the actual RFC number & -- EdNote: Replace YYYY with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 ZZZ } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is -- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 13, line 25 skipping to change at page 13, line 25
this table MUST be maintained in a persistent manner" this table MUST be maintained in a persistent manner"
::= { gBondTdimPort 1 } ::= { gBondTdimPort 1 }
gBondTdimPortConfEntry OBJECT-TYPE gBondTdimPortConfEntry OBJECT-TYPE
SYNTAX GBondTdimPortConfEntry SYNTAX GBondTdimPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the G.Bond/TDIM Port Configuration table. "An entry in the G.Bond/TDIM Port Configuration table.
Each entry represents an G.Bond/TDIM port indexed by the Each entry represents an G.Bond/TDIM port indexed by the
ifIndex. Additional conifguration parameters are available ifIndex. Additional configuration parameters are available
via the gBondPortConfEntry of GBOND-MIB. via the gBondPortConfEntry of GBOND-MIB.
Note that an G.Bond/TDIM port runs on top of a single or Note that an G.Bond/TDIM port runs on top of a single or
multiple BCE port(s), which are also indexed by ifIndex." multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { gBondTdimPortConfTable 1 } ::= { gBondTdimPortConfTable 1 }
GBondTdimPortConfEntry ::= GBondTdimPortConfEntry ::=
SEQUENCE { SEQUENCE {
gBondTdimFecAdminState TruthValue, gBondTdimFecAdminState TruthValue,
gBondTdimFecWordSize Unsigned32, gBondTdimFecWordSize Unsigned32,
skipping to change at page 50, line 47 skipping to change at page 50, line 47
10.1. Normative References 10.1. Normative References
[G.998.3] ITU-T, "Multi-pair bonding using time- [G.998.3] ITU-T, "Multi-pair bonding using time-
division inverse multiplexing", ITU-T division inverse multiplexing", ITU-T
Recommendation G.998.3, January 2005, < Recommendation G.998.3, January 2005, <
http://www.itu.int/rec/T-REC- http://www.itu.int/rec/T-REC-
G.998.3/en>. G.998.3/en>.
[I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL [I-D.ietf-adslmib-gbond-mib] Beili, E. and M. Morgenstern, "xDSL
multi-pair bonding (G.Bond) MIB", multi-pair bonding (G.Bond) MIB",
draft-ietf-adslmib-gbond-mib-06 (work draft-ietf-adslmib-gbond-mib-07 (work
in progress), March 2011. in progress), May 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs [RFC2119] Bradner, S., "Key words for use in RFCs
to Indicate Requirement Levels", to Indicate Requirement Levels",
BCP 14, RFC 2119, March 1997. BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed.,
and J. Schoenwaelder, Ed., "Structure and J. Schoenwaelder, Ed., "Structure
of Management Information Version 2 of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
 End of changes. 10 change blocks. 
13 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/