draft-ietf-adslmib-gbond-eth-mib-00.txt   draft-ietf-adslmib-gbond-eth-mib-01.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: December 7, 2007 ECI Telecom Expires: May 22, 2008 ECI Telecom
June 05, 2007 November 19, 2007
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-00.txt draft-ietf-adslmib-gbond-eth-mib-01.txt
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 7, 2007. This Internet-Draft will expire on May 22, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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 G.Bond MIB module with a This document proposes an extension to the G.Bond MIB module with a
skipping to change at page 4, line 25 skipping to change at page 4, line 25
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, port and channel particular it describes the bonding management, port and channel
configuration, initialization sequence etc. configuration, initialization 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.3. Relationship to EFM Copper MIB module 4.3. Relationship to EFM Copper MIB module
EFM-CU-MIB [I-D.ietf-hubmib-efm-cu-mib] module defines objects for EFM-CU-MIB [RFC5066] module defines objects for managing Ethernet in
managing Ethernet in the First Mile Copper (EFMCu) interfaces the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3-2005 [802.3]. defined in IEEE Std 802.3-2005 [802.3]. These interfaces are based
These interfaces are based on Single-pair High-speed Digital on Single-pair High-speed Digital Subscriber Line (SHDSL) [G.991.2]
Subscriber Line (SHDSL) [G.991.2] and Very High speed Digital and Very High speed Digital Subscriber Line (VDSL) [G.993.1]
Subscriber Line (VDSL) [G.993.1] technology respectively, and can be technology respectively, and can be optionally aggregated (bonded).
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. individual channels as well as physical lines.
EFM-CU-MIB can be used to manage all aspects of the EFMCu interfaces, EFM-CU-MIB can be used to manage all aspects of the EFMCu interfaces,
including the management of SHDSL/VDSL lines. GBOND-MIB and GBOND- including the management of SHDSL/VDSL lines. GBOND-MIB and GBOND-
ETH-MIB modules provide management objects only for the bonding part, ETH-MIB modules provide management objects only for the bonding part,
leaving the management of the individual xDSL interfaces (lines/ leaving the management of the individual xDSL interfaces (lines/
channels) to the respective xDSL MIB modules. channels) to the respective xDSL MIB modules.
5. MIB Structure 5. MIB Structure
5.1. Overview 5.1. Overview
_EdNote: TBC... _ _EdNote: TBC... _
5.1.1. TODO/Open Issues 5.1.1. TODO/Open Issues
o Peformance Monitoring counters
o Support for ITU-T draft BACP o Add Peformance Monitoring counters - reuse HC-PerfHist-TC-MIB
[RFC3705]
o Add support for ITU-T draft BACP (frame-based discovery and pair
management)
5.2. Mapping of IEEE 802.3 Managed Objects 5.2. Mapping of IEEE 802.3 Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [802.3] and managed objects defined in this (attributes) defined in [802.3] and managed objects defined in this
document. document.
+----------------------+---------------------------+ +----------------------+---------------------------+
| 802.3 Managed Object | Corresponding SNMP Object | | 802.3 Managed Object | Corresponding SNMP Object |
+----------------------+---------------------------+ +----------------------+---------------------------+
skipping to change at page 6, line 25 skipping to change at page 6, line 4
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxErrors | gBondEthInErrors | | aEthRxErrors | gBondEthInErrors |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxSmallFragments | gBondEthInSmallFragments | | aEthRxSmallFragments | gBondEthInSmallFragments |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxLargeFragments | gBondEthInLargeFragments | | aEthRxLargeFragments | gBondEthInLargeFragments |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxBadFragments | gBondEthInBadFragments | | aEthRxBadFragments | gBondEthInBadFragments |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxLostFragments | gBondEthInLostFragments | | aEthRxLostFragments | gBondEthInLostFragments |
+---------------------------------+-----------------------------+
| aEthRxLostStarts | gBondEthInLostStarts | | aEthRxLostStarts | gBondEthInLostStarts |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxLostEnds | gBondEthInLostEnds | | aEthRxLostEnds | gBondEthInLostEnds |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aEthRxOverflows | gBondEthInOverflows | | aEthRxOverflows | gBondEthInOverflows |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| oChannel | | | oChannel | |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
| aChannelPtmTcRxCodingViolations | gBondEthBceTcInCodingErrors | | aChannelPtmTcRxCodingViolations | gBondEthBceTcInCodingErrors |
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
skipping to change at page 6, line 47 skipping to change at page 6, line 25
+---------------------------------+-----------------------------+ +---------------------------------+-----------------------------+
Table 2: Mapping of WT-159 Managed Objects Table 2: Mapping of WT-159 Managed Objects
6. G.Bond/Ethernet MIB Definitions 6. G.Bond/Ethernet MIB Definitions
GBOND-ETH-MIB DEFINITIONS ::= BEGIN GBOND-ETH-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32 MODULE-IDENTITY, OBJECT-TYPE, Counter32
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- [RFC2580]
ifIndex ifIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- [RFC2863]
gBondMIB -- gBondMIB
FROM GBOND-MIB -- RFC YYYY -- FROM GBOND-MIB -- [RFCXXXX]
-- EdNote: Replace YYYY with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
; ;
gBondEthMIB MODULE-IDENTITY gBondEthMIB MODULE-IDENTITY
LAST-UPDATED "200706050000Z" -- June 05, 2007 LAST-UPDATED "200711190000Z" -- November 19, 2007
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 8, line 42 skipping to change at page 8, line 20
HDLC - High-level Data Link Control HDLC - High-level Data Link Control
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)
Copyright (C) The Internet Society (2007). This version of this Copyright (C) The Internet Society (2007). This version of this
MIB module is part of RFC XXXX; see the RFC itself for full MIB module is part of RFC XXXX; see the RFC itself for full
legal notices." legal notices."
REVISION "200706050000Z" -- June 05, 2007 REVISION "200711190000Z" -- November 19, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC YYYY."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace YYYY with the actual RFC number &
-- remove this note -- remove this note
::= { gBondMIB 2 } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note.
-- Sections of the module -- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D -- Structured as recommended by [RFC4181], Appendix D
gBondEthObjects OBJECT IDENTIFIER ::= { gBondEthMIB 1 } gBondEthObjects OBJECT IDENTIFIER ::= { gBondEthMIB 1 }
gBondEthConformance OBJECT IDENTIFIER ::= { gBondEthMIB 2 } gBondEthConformance OBJECT IDENTIFIER ::= { gBondEthMIB 2 }
-- Groups in the module -- Groups in the module
gBondEthPort OBJECT IDENTIFIER ::= { gBondEthObjects 1 } gBondEthPort OBJECT IDENTIFIER ::= { gBondEthObjects 1 }
gBondEthBce OBJECT IDENTIFIER ::= { gBondEthObjects 2 } gBondEthBce OBJECT IDENTIFIER ::= { gBondEthObjects 2 }
skipping to change at page 20, line 25 skipping to change at page 20, line 7
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
A new IANAifType value of g9982 SHALL be defined by the IANA [1] in An object identifier for gBondEthMIB MODULE-IDENTITY SHALL be
the IANAifType-MIB module [IANAifType-MIB], before this document is allocated by IANA in the MIB-2 transmission sub-tree, before this
published as an RFC. document is published as an RFC.
9. Acknowledgments 9. Acknowledgments
This document was produced by the IETF ADSL MIB Working Group [2]. This document was produced by the [ADSLMIB] working group.
10. References 10. References
10.1. Normative References 10.1. Normative References
[802.3] IEEE, "IEEE Standard for Information [802.3] IEEE, "IEEE Standard for Information
technology - Telecommunications and technology - Telecommunications and
information exchange between systems - information exchange between systems -
Local and metropolitan area networks - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier Specific requirements - Part 3: Carrier
Sense Multiple Access with Collision Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Detection (CSMA/CD) Access Method and
Physical Layer Specifications", IEEE Physical Layer Specifications", IEEE
Std 802.3-2005, December 2005. Std 802.3-2005, December 2005.
[G.998.2] ITU-T, "Ethernet-based multi-pair [G.998.2] ITU-T, "Ethernet-based multi-pair
bonding", ITU-T Recommendation G.998.2, bonding", ITU-T Recommendation G.998.2,
January 2005. January 2005, <http://www.itu.int/rec/
T-REC-G.998.2/en>.
[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.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed.,
and J. Schoenwaelder, Ed., "Textual and J. Schoenwaelder, Ed., "Textual
Conventions for SMIv2", STD 58, Conventions for SMIv2", STD 58,
RFC 2579, April 1999. RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. [RFC2580] McCloghrie, K., Perkins, D., and J.
Schoenwaelder, "Conformance Statements Schoenwaelder, "Conformance Statements
for SMIv2", STD 58, RFC 2580, for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The
Interfaces Group MIB", RFC 2863,
June 2000.
[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.
[WT-159] Morgenstern, M., Beili, E., and N. [WT-159] Morgenstern, M., Beili, E., and N.
Nair, "Management Framework for xDSL Nair, "Management Framework for xDSL
Bonding", DSL Forum technical Bonding", DSL Forum technical
report WT-159, May 2007. report WT-159, November 2007.
10.2. Informative References 10.2. Informative References
[ADSLMIB] IETF, "ADSL MIB (adslmib) Charter", <ht
tp://www.ietf.org/html.charters/
adslmib-charter.html>.
[G.991.2] ITU-T, "Single-pair High-speed Digital [G.991.2] ITU-T, "Single-pair High-speed Digital
Subscriber Line (SHDSL) transceivers", Subscriber Line (SHDSL) transceivers",
ITU-T Recommendation G.991.2, ITU-T Recommendation G.991.2,
December 2003. December 2003, <http://www.itu.int/rec/
T-REC-G.991.2/en>.
[G.993.1] ITU-T, "Very High speed Digital [G.993.1] ITU-T, "Very High speed Digital
Subscriber Line transceivers", ITU-T Subscriber Line transceivers", ITU-T
Recommendation G.993.1, June 2004. Recommendation G.993.1, June 2004, <htt
p://www.itu.int/rec/T-REC-G.993.1/en>.
[I-D.ietf-adslmib-gbond-mib] Beili, E., Morgenstern, M., and N. [I-D.ietf-adslmib-gbond-mib] Beili, E., Morgenstern, M., and N.
Nair, "xDSL multi-pair bonding (G.Bond) Nair, "xDSL multi-pair bonding (G.Bond)
MIB", draft-ietf-adslmib-gbond-mib-00 MIB", draft-ietf-adslmib-gbond-mib-01
(work in progress), February 2007. (work in progress), November 2007.
[I-D.ietf-hubmib-efm-cu-mib] Beili, E., "Ethernet in the First Mile
Copper (EFMCu) Interfaces MIB",
draft-ietf-hubmib-efm-cu-mib-07.txt
(work in progress), February 2007.
[IANAifType-MIB] Internet Assigned Numbers Authority [IANAifType-MIB] Internet Assigned Numbers Authority
(IANA), "IANAifType Textual Convention (IANA), "IANAifType Textual Convention
definition", http://www.iana.org/ definition", <http://www.iana.org/
assignments/ianaiftype-mib. assignments/ianaiftype-mib>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The [RFC4181] Heard, C., "Guidelines for Authors and
Interfaces Group MIB", RFC 2863, Reviewers of MIB Documents", BCP 111,
June 2000. RFC 4181, September 2005.
[RFC4836] Beili, E., "Definitions of Managed [RFC4836] Beili, E., "Definitions of Managed
Objects for IEEE 802.3 Medium Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 4836, Attachment Units (MAUs)", RFC 4836,
April 2007. April 2007.
URIs [RFC5066] Beili, E., "Ethernet in the First Mile
Copper (EFMCu) Interfaces MIB",
[1] <http://www.iana.org/> RFC 5066, November 2007.
[2] <http://www.ietf.org/html.charters/adslmib-charter.html>
Authors' Addresses Authors' Addresses
Edward Beili Edward Beili
Actelis Networks Actelis Networks
25 Bazel St. 25 Bazel St.
Petach-Tikva 49103 Petach-Tikva 49103
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
 End of changes. 28 change blocks. 
52 lines changed or deleted 60 lines changed or added

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