draft-ietf-adslmib-gbond-eth-mib-03.txt   draft-ietf-adslmib-gbond-eth-mib-04.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Intended status: Standards Track M. Morgenstern Intended status: Standards Track M. Morgenstern
Expires: September 15, 2011 ECI Telecom Expires: November 27, 2011 ECI Telecom
March 14, 2011 May 26, 2011
Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB
draft-ietf-adslmib-gbond-eth-mib-03.txt draft-ietf-adslmib-gbond-eth-mib-04.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 Ethernet-based multi-pair bonded xDSL set of objects for managing Ethernet-based multi-pair bonded xDSL
interfaces, defined in ITU-T recommendation G.998.2. interfaces, defined in ITU-T recommendation G.998.2.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 34 skipping to change at page 3, line 34
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. Relation to other MIB modules 4. Relation to other MIB modules
skipping to change at page 4, line 18 skipping to change at page 4, line 18
interface and as such is managed using generic interface management interface and as such is managed using generic interface management
objects defined in the IF-MIB [RFC2863]. In particular, an interface objects defined in the IF-MIB [RFC2863]. In particular, an interface
index (ifIndex) is used to index instances of G.Bond/Ethernet ports, index (ifIndex) is used to index instances of G.Bond/Ethernet ports,
as well as xDSL lines/channels, in a managed system. as well as xDSL lines/channels, in a managed system.
4.2. Relationship to G.Bond MIB module 4.2. Relationship to G.Bond MIB module
GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management
objects common for all bonded multi-pair xDSL interfaces. In objects common for all bonded multi-pair xDSL interfaces. In
particular it describes the bonding management, bonded port and particular it describes the bonding management, bonded port and
channel configuration, [G.994.1] handshake-based discovery, channel configuration, handshake-based discovery, initialization
initialization sequence etc. sequence etc.
Both GBOND-MIB and GBOND-ETH-MIB modules are REQUIRED to manage a Both GBOND-MIB and GBOND-ETH-MIB modules are REQUIRED to manage a
G.Bond/Ethernet port. G.Bond/Ethernet port.
4.2.1. BACP-based Discovery 4.2.1. BACP-based Discovery
All G.998 protocols share a G.handshake-based remote Bonding Channel All G.998 protocols share a remote Bonding Channel Entity (BCE)
Entity (BCE) discovery. The GBOND-MIB module provides an example of discovery, using the [G.994.1] handshake (G.hs). The GBOND-MIB
an automatic BCE connection to the corresponding GPS ports of a module provides an example of an automatic BCE connection to the
generic G.998 multi-port Central Office (CO) device, using the corresponding GPS ports of a generic G.998 multi-port Central Office
G.handshake-based discovery. Amendment 2 to the ITU-T G.998.2 (CO) device, using the G.hs-based BCE discovery. Amendment 2 to the
specification [G.998.2-Amd2], provides an alternative optional ITU-T G.998.2 specification [G.998.2-Amd2], provides an alternative
Bonding Aggregation Control Protocol (BACP) for in-service discovery, optional Bonding Aggregation Control Protocol (BACP) for in-service
aggregation and pair management. discovery, aggregation and pair management.
The following pseudo-code gives the same example of the discovery and The following pseudo-code gives the same example of the discovery and
automatic BCE assignment for a multi-GBS G.Bond/Eth CO device, using automatic BCE assignment for a multi-GBS G.Bond/Eth CO device, using
BACP objects defined in this MIB module, IF-CAP-STACK-MIB and IF-MIB BACP objects defined in this MIB module, IF-CAP-STACK-MIB and IF-MIB
modules [Note that automatic BCE assignment is only shown here for modules [Note that automatic BCE assignment is only shown here for
the purposes of the example. Fixed BCE pre-assignment, manual the purposes of the example. Fixed BCE pre-assignment, manual
assignment or auto-assignment using an alternative internal algorithm assignment or auto-assignment using an alternative internal algorithm
may be chosen by a particular implementation]: may be chosen by a particular implementation]:
// Go over all GBS ports in the CO device // Go over all GBS ports in the CO device
skipping to change at page 5, line 47 skipping to change at page 5, line 47
ADD bce[j] TO ifStackTable[gbs[i]]; ADD bce[j] TO ifStackTable[gbs[i]];
gbs[i].NumBCEs = gbs[i].NumBCEs + 1; gbs[i].NumBCEs = gbs[i].NumBCEs + 1;
} }
} }
// At this point we have discovered all local BCEs which // At this point we have discovered all local BCEs which
// are physically connected to the same remote RT_device // are physically connected to the same remote RT_device
// and connected them to GBS[i]. Go to the next GBS. // and connected them to GBS[i]. Go to the next GBS.
BREAK; BREAK;
} }
ELSE ELSE
{ // Use default G.HS discovery protocol { // Use default G.hs discovery protocol
... ...
} }
} }
} }
An SNMP Agent for a G.Bond device builds ifCapStackTable and its An SNMP Agent for a G.Bond device builds ifCapStackTable and its
inverse ifInvCapStackTable on device initialiation, according to the inverse ifInvCapStackTable on device initialization, according to the
cross-connect capabilities of the device. When BACP is used, the cross-connect capabilities of the device. When BACP is used, the
gBondEthBceEligibleGroupID object identifying bonding eligibility gBondEthBceEligibleGroupID object identifying bonding eligibility
MUST be automatically updated, whenever the ifCapStackTable/ MUST be automatically updated, whenever the ifCapStackTable/
ifInvCapStackTable are changed. ifInvCapStackTable are changed.
4.3. Relationship to EFM Copper MIB module 4.3. Relationship to EFM Copper MIB module
EFM-CU-MIB [RFC5066] module defines objects for managing Ethernet in EFM-CU-MIB [RFC5066] module defines objects for managing Ethernet in
the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
defined in IEEE Std 802.3-2005 [802.3]. These interfaces are based defined in IEEE Std 802.3-2005 [802.3]. These interfaces are based
on Single-pair High-speed Digital Subscriber Line (SHDSL) [G.991.2] on Single-pair High-speed Digital Subscriber Line (SHDSL) [G.991.2]
and Very High speed Digital Subscriber Line (VDSL) [G.993.1] and Very High speed Digital Subscriber Line (VDSL) [G.993.1]
technology respectively, and can be optionally aggregated (bonded). technology respectively, and can be optionally aggregated (bonded).
ITU-T G.998.2 specification extends the IEEE 802.3 Clause 61 bonding ITU-T G.998.2 specification extends the IEEE 802.3 Clause 61 bonding
to work over any xDSL technology, providing the ability to bond to work over any xDSL technology, providing the ability to bond
individual channels as well as physical lines. It also allows the individual channels as well as physical lines. It also allows the
use of alternative HDLC encapsulation instead of the default 64/ use of alternative HDLC encapsulation instead of the default 64/
65-octet encapsulation and adds a new optional Bonding Aggregation 65-octet encapsulation and adds a new optional Bonding Aggregation
Control Protocol (BACP) for in-service discovery, aggregation and Control Protocol (BACP) for in-service discovery, aggregation and
pair management instead of the default G.handshake-based bonding pair management instead of the default G.hs-based bonding protocol,
protocol, which cannot be used in-service, while the link is up. which cannot be used in-service, while the link is up.
EFM-CU-MIB can be used to manage all aspects of the EFMCu physical EFM-CU-MIB can be used to manage all aspects of the EFMCu physical
interfaces (PHYs), including a complete (within the scope of the interfaces (PHYs), including a complete (within the scope of the
802.3 standard) management of the SHDSL/VDSL lines. GBOND-MIB and 802.3 standard) management of the SHDSL/VDSL lines. GBOND-MIB and
GBOND-ETH-MIB modules on the other hand, provide management objects GBOND-ETH-MIB modules on the other hand, provide management objects
only for the bonding part, leaving the management of the individual only for the bonding part, leaving the management of the individual
xDSL interfaces (lines/channels) to the respective xDSL-LINE-MIB xDSL interfaces (lines/channels) to the respective xDSL-LINE-MIB
modules. modules.
Therefore an IEEE 802.3 2BASE-TL/10PASS-TS interface can be managed Therefore an IEEE 802.3 2BASE-TL/10PASS-TS interface can be managed
skipping to change at page 9, line 38 skipping to change at page 9, line 38
ifIndex ifIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed HCPerfTimeElapsed
FROM HC-PerfHist-TC-MIB -- [RFC3705] FROM HC-PerfHist-TC-MIB -- [RFC3705]
; ;
------------------------------------------------------------------------ ------------------------------------------------------------------------
gBondEthMIB MODULE-IDENTITY gBondEthMIB 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 11, line 25 skipping to change at page 11, line 25
PTM-TC - Packet Transfer Mode Transmission Convergence PTM-TC - Packet Transfer Mode Transmission Convergence
(sub-layer) (sub-layer)
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TC - Transmission Convergence (sub-layer) TC - Transmission Convergence (sub-layer)
UAS - Unavailable Seconds UAS - Unavailable Seconds
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 35, line 27 skipping to change at page 35, line 27
gBondEthPortPerf1DayIntervalRxOverflows HCPerfCurrentCount, gBondEthPortPerf1DayIntervalRxOverflows HCPerfCurrentCount,
gBondEthPortPerf1DayIntervalValid TruthValue gBondEthPortPerf1DayIntervalValid TruthValue
} }
gBondEthPortPerf1DayIntervalIndex OBJECT-TYPE gBondEthPortPerf1DayIntervalIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..7) SYNTAX Unsigned32 (1..7)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Performance Data Interval number. 1 is the most recent previous "Performance Data Interval number. 1 is the most recent previous
interval; interval 7 is 24 hours ago. interval; interval 7 is 7 days ago.
Intervals 2..7 are OPTIONAL. Intervals 2..7 are OPTIONAL.
This object partially maps to the TR-159 attribute This object partially maps to the TR-159 attribute
aGroupPerf1DayIntervalNumber." aGroupPerf1DayIntervalNumber."
REFERENCE REFERENCE
"[TR-159] 5.5.1.62" "[TR-159] 5.5.1.62"
::= { gBondEthPortPerf1DayEntry 1 } ::= { gBondEthPortPerf1DayEntry 1 }
gBondEthPortPerf1DayIntervalMoniTime OBJECT-TYPE gBondEthPortPerf1DayIntervalMoniTime OBJECT-TYPE
SYNTAX HCPerfTimeElapsed SYNTAX HCPerfTimeElapsed
skipping to change at page 49, line 10 skipping to change at page 49, line 10
T-REC-G.998.2/en>. T-REC-G.998.2/en>.
[G.998.2-Amd2] ITU-T, "Ethernet-based multi-pair [G.998.2-Amd2] ITU-T, "Ethernet-based multi-pair
bonding Amendment 2", ITU-T bonding Amendment 2", ITU-T
Recommendation G.998.2/Amd.2, Recommendation G.998.2/Amd.2,
December 2007, <http://www.itu.int/rec/ December 2007, <http://www.itu.int/rec/
T-REC-G.998.2-200712-I!Amd2/en>. T-REC-G.998.2-200712-I!Amd2/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. 13 change blocks. 
25 lines changed or deleted 26 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/