draft-ietf-adslmib-gbond-eth-mib-07.txt   draft-ietf-adslmib-gbond-eth-mib-08.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: January 17, 2013 ECI Telecom Expires: February 10, 2013 ECI Telecom
July 16, 2012 August 09, 2012
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-07.txt draft-ietf-adslmib-gbond-eth-mib-08.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 defines an extension to the GBOND-MIB module with a set This document defines an extension to the GBOND-MIB module with a set
of objects for managing Ethernet-based multi-pair bonded xDSL 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 January 17, 2013. This Internet-Draft will expire on February 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 2, line 16 skipping to change at page 2, line 16
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. The Broadband Forum Management Framework for xDSL Bonding . . 3 3. The Broadband Forum Management Framework for xDSL Bonding . . 3
4. Relation to other MIB modules . . . . . . . . . . . . . . . . 3 4. Relation to other MIB modules . . . . . . . . . . . . . . . . 3
4.1. Relationship to Interfaces Group MIB module . . . . . . . 4 4.1. Relationship to Interfaces Group MIB module . . . . . . . 4
4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4 4.2. Relationship to G.Bond MIB module . . . . . . . . . . . . 4
4.2.1. BACP-based Discovery . . . . . . . . . . . . . . . . . 4 4.2.1. BACP-based Discovery . . . . . . . . . . . . . . . . . 4
4.3. Relationship to EFM Copper MIB module . . . . . . . . . . 6 4.3. Relationship to EFM Copper MIB module . . . . . . . . . . 6
4.4. Relationship to IEEE 802.3.1 MIB modules . . . . . . . . . 7
5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 7 5. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 7 5.2. Performance Monitoring . . . . . . . . . . . . . . . . . . 7
5.3. Mapping of Broadband Forum TR-159 Managed Objects . . . . 7 5.3. Mapping of Broadband Forum TR-159 Managed Objects . . . . 8
6. G.Bond/Ethernet MIB Definitions . . . . . . . . . . . . . . . 9 6. G.Bond/Ethernet MIB Definitions . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 48 7. Security Considerations . . . . . . . . . . . . . . . . . . . 48
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
10.1. Normative References . . . . . . . . . . . . . . . . . . . 49 10.1. Normative References . . . . . . . . . . . . . . . . . . . 50
10.2. Informative References . . . . . . . . . . . . . . . . . . 51 10.2. Informative References . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
The Ethernet-based xDSL Multi-Pair Bonding, a.k.a. G.Bond/Ethernet, The Ethernet-based xDSL Multi-Pair Bonding, a.k.a. G.Bond/Ethernet,
is specified in ITU-T G.998.2 recommendation [G.998.2], which defines is specified in ITU-T G.998.2 recommendation [G.998.2], which defines
a method for bonding (or aggregating) of multiple xDSL lines (or a method for bonding (or aggregating) of multiple xDSL lines (or
individual bearer channels in multiple xDSL lines) into a single bi- individual bearer channels in multiple xDSL lines) into a single bi-
directional logical link, carrying an Ethernet traffic. directional logical link, carrying an Ethernet traffic.
skipping to change at page 7, line 7 skipping to change at page 7, line 7
from MAU-MIB [RFC4836] for the additional bonded xDSL-specific from MAU-MIB [RFC4836] for the additional bonded xDSL-specific
operational states, GBOND-MIB provides these indication via operational states, GBOND-MIB provides these indication via
gBondPortStatOperStatus object, complementing the ifOperStatus object gBondPortStatOperStatus object, complementing the ifOperStatus object
from IF-MIB. from IF-MIB.
Finally, EFM-CU-MIB does not include historical Performance Finally, EFM-CU-MIB does not include historical Performance
Monitoring (PM), while GBOND-MIB/GBOND-MIB-ETH/xDSL-LINE-MIB Monitoring (PM), while GBOND-MIB/GBOND-MIB-ETH/xDSL-LINE-MIB
combination provides full PM functionality for a bonded link and combination provides full PM functionality for a bonded link and
individual xDSL lines. individual xDSL lines.
4.4. Relationship to IEEE 802.3.1 MIB modules
The IEEE 802.3 working group chartered a task force [IEEE802.3.1],
which continues the development of standard Ethernet-related MIB
modules based on the initial work done in the IETF. Future projects
resulting from the work of this Task Force may include and possibly
extend the work done in the IETF.
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
The main management objects defined in the G9982-MIB module are split The main management objects defined in the G9982-MIB module are split
into 2 groups, structured as recommended by RFC 4181 [RFC4181]: into 2 groups, structured as recommended by RFC 4181 [RFC4181]:
o g9982Port - containing objects for configuration, capabilities, o g9982Port - containing objects for configuration, capabilities,
status and PM of G.Bond/Eth ports. Note that the rest of the status and PM of G.Bond/Eth ports. Note that the rest of the
objects for the Generic Bonded Sub-layer (GBS) port configuration, objects for the Generic Bonded Sub-layer (GBS) port configuration,
skipping to change at page 8, line 47 skipping to change at page 9, line 4
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aEthAdminCP | g9982PortConfAdminCp | | aEthAdminCP | g9982PortConfAdminCp |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aEthOperCP | g9982PortStatOperCp | | aEthOperCP | g9982PortStatOperCp |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oChannel - BACP package | | | oChannel - BACP package | |
| (Optional) | | | (Optional) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aChannelEligibleGroupID | g9982BceConfEligibleGroupID | | aChannelEligibleGroupID | g9982BceConfEligibleGroupID |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
+---------------------------------+---------------------------------+
| aChannelEligibleStreamID | g9982BceConfPeerEligibleGroupID | | aChannelEligibleStreamID | g9982BceConfPeerEligibleGroupID |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oChannel - PM package | | | oChannel - PM package | |
| (Optional) | | | (Optional) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aChannelPtmTcRxCodingViolations | g9982BceStatTcInCodingErrors | | aChannelPtmTcRxCodingViolations | g9982BceStatTcInCodingErrors |
+---------------------------------+---------------------------------+
| aChannelPtmTcRxCrcErrors | g9982BceStatTcInCrcErrors | | aChannelPtmTcRxCrcErrors | g9982BceStatTcInCrcErrors |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 1: Mapping of TR-159 Managed Objects Table 1: Mapping of TR-159 Managed Objects
Note that some of the mapping between the objects defined in TR-159 Note that some of the mapping between the objects defined in TR-159
and the ones defined in this MIB module is not one-to-one, for and the ones defined in this MIB module is not one-to-one, for
example, while TR-159 PM attributes aGroupPerf* map to the example, while TR-159 PM attributes aGroupPerf* map to the
corresponding gBondPortPm* objects of the GBOND-MIB module, there are corresponding gBondPortPm* objects of the GBOND-MIB module, there are
no dedicated PM attributes for the g9982PortPm* objects introduced in no dedicated PM attributes for the g9982PortPm* objects introduced in
skipping to change at page 9, line 48 skipping to change at page 10, line 8
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]
; ;
------------------------------------------------------------------------ ------------------------------------------------------------------------
g9982MIB MODULE-IDENTITY g9982MIB MODULE-IDENTITY
LAST-UPDATED "201203120000Z" -- Mar 12, 2012 LAST-UPDATED "201208090000Z" -- Aug 09, 2012
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
Chair: Menachem Dodge Chair: Menachem Dodge
Postal: ECI Telecom, Ltd. Postal: ECI Telecom, Ltd.
30 Hasivim St., 30 Hasivim St.,
skipping to change at page 11, line 38 skipping to change at page 11, line 45
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 (2012). Copyright (C) The IETF Trust (2012).
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 "201203120000Z" -- Mar 12, 2012 REVISION "201208090000Z" -- Aug 09, 2012
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.
-- Sections of the module -- Sections of the module
-- Structured as recommended by [RFC4181], Appendix D -- Structured as recommended by [RFC4181], Appendix D
g9982Objects OBJECT IDENTIFIER ::= { g9982MIB 1 } g9982Objects OBJECT IDENTIFIER ::= { g9982MIB 1 }
g9982Conformance OBJECT IDENTIFIER ::= { g9982MIB 2 } g9982Conformance OBJECT IDENTIFIER ::= { g9982MIB 2 }
-- Groups in the module -- Groups in the module
g9982Port OBJECT IDENTIFIER ::= { g9982Objects 1 } g9982Port OBJECT IDENTIFIER ::= { g9982Objects 1 }
g9982Bce OBJECT IDENTIFIER ::= { g9982Objects 2 } g9982Bce OBJECT IDENTIFIER ::= { g9982Objects 2 }
------------------------------- -------------------------------
-- Textual Conventions -- Textual Conventions
skipping to change at page 51, line 46 skipping to change at page 52, line 6
Recommendation G.993.1, June 2004, <htt Recommendation G.993.1, June 2004, <htt
p://www.itu.int/rec/T-REC-G.993.1/en>. p://www.itu.int/rec/T-REC-G.993.1/en>.
[G.994.1] ITU-T, "Handshake procedures for [G.994.1] ITU-T, "Handshake procedures for
digital subscriber line (DSL) digital subscriber line (DSL)
transceivers", ITU-T transceivers", ITU-T
Recommendation G.994.1, February 2007, Recommendation G.994.1, February 2007,
<http://www.itu.int/rec/T-REC- <http://www.itu.int/rec/T-REC-
G.994.1/en>. G.994.1/en>.
[IEEE802.3.1] IEEE, "IEEE P802.3.1 Revision to IEEE
Std 802.3.1-2011 (IEEE 802.3.1a)
Ethernet MIBs Task Force", <http://
grouper.ieee.org/groups/802/3/1/>.
[RFC3410] Case, J., Mundy, R., Partain, D., and [RFC3410] Case, J., Mundy, R., Partain, D., and
B. Stewart, "Introduction and B. Stewart, "Introduction and
Applicability Statements for Internet- Applicability Statements for Internet-
Standard Management Framework", Standard Management Framework",
RFC 3410, December 2002. RFC 3410, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for [RFC3593] Tesink, K., "Textual Conventions for
MIB Modules Using Performance History MIB Modules Using Performance History
Based on 15 Minute Intervals", Based on 15 Minute Intervals",
RFC 3593, September 2003. RFC 3593, September 2003.
 End of changes. 15 change blocks. 
11 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/