Network Working Group E. Beili
Internet-Draft Actelis Networks
Intended status: Standards Track M. Morgenstern
Expires: July 13, 2007 ECI Telecom
N. Nair
Wipro Technologies
January 09, 2007
ATM-Based xDSL Bonded Interfaces MIB
draft-ietf-adslmib-gbond-atm-mib-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 13, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines Management Information Base (MIB) module for
use with network management protocols in TCP/IP based networks. This
document proposes an extension to the GBOND-MIB which defines a set
of common objects for managing multi-pair bonded Digital Subscriber
Line (xDSL) interfaces. In particular, it describes objects used for
Beili, et al. Expires July 13, 2007 [Page 1]
Internet-Draft G.Bond ATM MIB January 2007
managing parameters of the ATM based xDSL multi-pair bonded
interfaces, as defined in ITU-T recommendations G.998.1. The
Management Information Base (MIB) modules specific to the other
bonding technologies are defined in GBOND-ETH-MIB and GBOND-TDIM-MIB
respectively.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Management Model . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. The DSL Forum Management Framework for xDSL Bonding . . . 4
3.2. Mapping of ITU-T G.998.1 Managed Objects . . . . . . . . . 4
3.3. Mapping of DSL Forum WT-159 Managed Objects . . . . . . . 5
3.4. Relation to other MIB modules . . . . . . . . . . . . . . 6
3.4.1. Relationship to Interfaces Group MIB module . . . . . 6
3.4.2. Relationship to G.BOND MIB module . . . . . . . . . . 6
3.5. IANA Considerations . . . . . . . . . . . . . . . . . . . 6
3.6. Structure of GBOND-ATM-MIB . . . . . . . . . . . . . . . . 6
3.7. Conventions Used . . . . . . . . . . . . . . . . . . . . . 6
4. xDSL multi-pair bonding ATM MIB Definitions . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . . . 17
Beili, et al. Expires July 13, 2007 [Page 2]
Internet-Draft G.Bond ATM MIB January 2007
1. Introduction
The xDSL Multi-Pair Bonding, allows a service provider to provide
high bandwidth services to business and residential customers over
multiple xDSL lines, with greater speed and resiliency, than the
service over a single xDSL line, bridging the gap between xDSL and
fiber-based transport.
There are three xDSL Multi-Pair Bonding schemes, also known under
collective name G.Bond: ATM based, Ethernet Based and time division
inverse multiplexing (TDIM) based
The ATM-Based Multi-Pair Bonding, specified in ITU-T G.998.1
recommendation [G.998.1], which defines a method for bonding (or
aggregating) of multiple xDSL lines (or individual bearer channels in
multiple xDSL lines) into a single bi-directional logical link
carrying an ATM stream. This specification can be viewed as an
evolution of the legacy Inverse Multiplexing over ATM (IMA)
technology [af-phy-0086], applied to xDSL with variable rates on each
line/bearer channel. As with other bonding schemes, ATM bonding also
allows bonding of up to 32 individual sub-layers with variable rates,
providing common functionality for the configuration, initialization,
operation and monitoring of the bonded link.
The MIB module defined in this document defines a set of managed
objects specific to ATM based multi-pair bonding technology. This
MIB module extends the common objects specified in the GBOND-MIB
[I-D.ietf-adslmib-gbond-mib] modules.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
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
[RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Beili, et al. Expires July 13, 2007 [Page 3]
Internet-Draft G.Bond ATM MIB January 2007
3. Management Model
3.1. The DSL Forum Management Framework for xDSL Bonding
This document makes use of the DSL Forum technical report Management
Framework for xDSL Bonding [WT-159], defining a management model and
a hierarchy of management objects for the bonded xDSL interfaces.
3.2. Mapping of ITU-T G.998.1 Managed Objects
This section contains the mapping between relevant managed objects
(attributes) defined in [G.998.1] and managed objects defined in this
document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
+----------+--------------------------------------------------------+
| G.Bond | Corresponding SNMP Object |
| Managed | |
| Object | |
+----------+--------------------------------------------------------+
| Group | |
| Provisio | |
| ning | |
+----------+--------------------------------------------------------+
| Group ID | IF-MIB::ifIndex (Group ifIndex) |
+----------+--------------------------------------------------------+
| Line | gBondAtmLineNumber |
| number | |
+----------+--------------------------------------------------------+
| Bearer | gBondAtmBearerNumber |
| number | |
+----------+--------------------------------------------------------+
| Maximum | gBondAtmUpMaxDataRate,gBondAtmDownMaxDataRate |
| aggregat | |
| edata | |
| rate | |
| (bit/s) | |
+----------+--------------------------------------------------------+
| Minimum | gBondThreshLowUpRate,gBondThreshLowDownRate |
| aggregat | |
| edata | |
| rate | |
| (bit/s) | |
+----------+--------------------------------------------------------+
| Differen | gBondAtmUpDiffDelayTolerence,gBondAtmDownDiffDelayTole |
| tial | rence |
| delay | |
| toleran | |
| ce(ms) | |
Beili, et al. Expires July 13, 2007 [Page 4]
Internet-Draft G.Bond ATM MIB January 2007
| Group | |
| Performa | |
| nce | |
+----------+--------------------------------------------------------+
| Achieved | gBondUpDataRate,gBondDownDataRate |
| aggregat | |
| edata | |
| rate | |
| (bit/s) | |
+----------+--------------------------------------------------------+
| Group | gBondStatus |
| status | |
+----------+--------------------------------------------------------+
| Group | gBondAtmShowTime |
| running | |
| time | |
+----------+--------------------------------------------------------+
| Group Rx | gBondAtmUpRxCellLossCount,gBondAtmDownRxCellLossCount |
| cell | |
| loss | |
| count | |
+----------+--------------------------------------------------------+
| Group | |
| Failure | |
+----------+--------------------------------------------------------+
| Current | gBondFltStatus |
| group | |
| failure | |
| reason | |
+----------+--------------------------------------------------------+
| Group | gBondAtmGroupFltCount |
| failure | |
| count | |
+----------+--------------------------------------------------------+
| Group | gBondAtmCurr15MUas,gBondAtmCurr1DayUas,gBondAtmPMHist1 |
| unavaila | 5MUas,gBondAtmPMHist1DayUas |
| ble | |
| seconds | |
+----------+--------------------------------------------------------+
Table 1: Mapping of ITU-T G.998.1 Managed Objects
3.3. Mapping of DSL Forum WT-159 Managed Objects
This section contains the mapping between relevant managed objects
(attributes) defined in [WT-159] and managed objects defined in this
document and in associated MIB modules, i.e., the IF-MIB [RFC2863].
Beili, et al. Expires July 13, 2007 [Page 5]
Internet-Draft G.Bond ATM MIB January 2007
+-----------------------+---------------------------+
| G.Bond Managed Object | Corresponding SNMP Object |
+-----------------------+---------------------------+
| TBC | TBC |
+-----------------------+---------------------------+
Table 2: Mapping of DSL Forum WT-159 Managed Objects
3.4. Relation to other MIB modules
This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs.
Specifically, the following MIB modules are discussed: Interfaces
Group MIB (IF-MIB) and and G.Bond MIB (GBOND-MIB).
3.4.1. Relationship to Interfaces Group MIB module
A G.Bond ATM port forms a part of a multi-pair xDSL bonded interface.
It is managed using the MIB objects defined in the IF-MIB [RFC2863].
In particular the MIB object ifIndex is used to index instances of
G.Bond ATM ports in a system.
3.4.2. Relationship to G.BOND MIB module
GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management
objects common for all Bonded multi-pair xDSL interfaces. In
particular is describes the bonding management, port and channel
configuration, initialization sequence etc.
Both GBOND-MIB and GBOND-TDIM-MIB modules are REQUIRED to manage a
G.Bond/TDIM port.
3.5. IANA Considerations
A new IANAifType value of g9981 SHALL be defined by the IANA [1] in
the [IANAifType-MIB]IANAifType-MIB module, before this document is
published as an RFC.
3.6. Structure of GBOND-ATM-MIB
_EdNote: Add structure based on the conclusion on fault and
performance reporting_
3.7. Conventions Used
_EdNote: To be added; abbreviation and textual conventions used in
this MIB_
Beili, et al. Expires July 13, 2007 [Page 6]
Internet-Draft G.Bond ATM MIB January 2007
4. xDSL multi-pair bonding ATM MIB Definitions
GBOND-ATM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
ifIndex, InterfaceIndex
FROM IF-MIB -- RFC 2863
gBondMIB
FROM GBOND-MIB -- RFC YYYY
-- EdNote: Replace YYYY with the actual RFC number and
-- remove this note
;
gBondAtmMIB MODULE-IDENTITY
LAST-UPDATED "200705140000Z" -- May 14, 2007
ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/adslmib-charter.html
Mailing Lists:
General Discussion: adslmib@ietf.org
To Subscribe: adslmib-request@ietf.org
In Body: subscribe your_email_address
Chair: Menachem Dodge
Postal: ECI Telecom, Ltd.
30 Hasivim St.,
Petach-Tikva 49517
Israel
Phone: +972-3-926-8421
EMail: menachem.dodge@ecitele.com
Editor: Edward Beili
Postal: Actelis Networks, Inc.
25 Bazel St., P.O.B. 10173
Petach-Tikva 10173
Israel
Phone: +972-3-924-3491
EMail: edward.beili@actelis.com
Beili, et al. Expires July 13, 2007 [Page 7]
Internet-Draft G.Bond ATM MIB January 2007
Editor: Narendranath Nair
Postal: Wipro Technologies
Keonics Electronics City
Bangalore 560 100
India
Phone: +91-99-00-12-96-29
EMail: narendranath.nair@wipro.com"
DESCRIPTION
"The objects in this MIB module are used to manage the
multi-pair bonded xDSL Interfaces using ATM inverse
multiplexing, defined in ITU-T recommendation G.998.1
(G.Bond/ATM).
This MIB module MUST be used in conjunction with GBOND-MIB
module, common to all G.Bond technologies.
The following references are used throughout this MIB module:
[WT-159] refers to:
DSL Forum Technical Report: 'Management Framework for xDSL
Bonding', January 2007.
Naming Conventions:
BCE - Bonding Channel Entity
CO - Central Office
CPE - Customer Premises Equipment
GBS - Generic Bonding Sublayer
SNR - Signal to Noise Ratio
Copyright (C) The Internet Society (2007). This version of this
MIB module is part of RFC XXXX; see the RFC itself for full
legal notices."
REVISION "200705140000Z" -- May 14, 2007
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number and
-- remove this note
::= { gBondMIB 1 }
-- Sections of the module
-- Structured as recommended by RFC 4181, Appendix D
gBondAtmObjects OBJECT IDENTIFIER ::= { gBondAtmMIB 1 }
gBondAtmConformance OBJECT IDENTIFIER ::= { gBondAtmMIB 2 }
Beili, et al. Expires July 13, 2007 [Page 8]
Internet-Draft G.Bond ATM MIB January 2007
-- Groups in the module
gBondAtmPort OBJECT IDENTIFIER ::= { gBondAtmObjects 1 }
-- Textual Conventions
-- Port Notifications Group
-- gBondAtmPortNotifications OBJECT IDENTIFIER
-- ::= { gBondAtmPort 0 }
-- G.Bond ATM Port group
gBondAtmPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GBondAtmPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of G.Bond ATM ports. Entries in
this table MUST be maintained in a persistent manner"
::= { gBondAtmPort 1 }
gBondAtmPortConfEntry OBJECT-TYPE
SYNTAX GBondAtmPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond ATM Port Configuration table.
Each entry represents an G.Bond ATM port indexed by the
ifIndex. Additional configuration parameters are available
via the gBondPortConfEntry of GBOND-MIB.
Note that an G.Bond ATM port runs on top of a single or
multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { gBondAtmPortConfTable 1 }
GBondAtmPortConfEntry ::=
SEQUENCE {
-- ATM Port conf Entry
gBondAtmUpMaxDataRate Unsigned32,
gBondAtmDownMaxDataRate Unsigned32,
gBondAtmUpDiffDelayTolerence Unsigned32,
gBondAtmDownDiffDelayTolerence Unsigned32
}
gBondAtmUpMaxDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps"
Beili, et al. Expires July 13, 2007 [Page 9]
Internet-Draft G.Bond ATM MIB January 2007
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum net upstream data rate a bonding group
is allowed to achieve to carry an ATM stream.If set
to '9999999', this parameter is ignored."
REFERENCE
"[G.998.1] Sec. 11.4.1 - (4)"
::= { gBondAtmPortConfEntry 1 }
gBondAtmDownMaxDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..1000000|9999999)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum net downstream data rate a bonding group
is allowed to achieve to carry an ATM stream.If set
to '9999999', this parameter is ignored."
REFERENCE
"[G.998.1] Sec. 11.4.1 - (4)"
::= { gBondAtmPortConfEntry 2 }
gBondAtmUpDiffDelayTolerence OBJECT-TYPE
SYNTAX Unsigned32(0..8176)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum upstream differential delay among member
links in a bonding group."
REFERENCE
"[G.998.1] Sec. 11.4.1 - (6)"
::= { gBondAtmPortConfEntry 3 }
gBondAtmDownDiffDelayTolerence OBJECT-TYPE
SYNTAX Unsigned32(0..8176)
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum downstream differential delay among member
links in a bonding group."
REFERENCE
"[G.998.1] Sec. 11.4.1 - (6)"
::= { gBondAtmPortConfEntry 4 }
gBondAtmPortStatusTable OBJECT-TYPE
Beili, et al. Expires July 13, 2007 [Page 10]
Internet-Draft G.Bond ATM MIB January 2007
SYNTAX SEQUENCE OF GBondAtmPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides overall status information of G.Bond
ATM ports, complementing the generic status information from
the ifTable of IF-MIB and gBondFltStatus of GBOND-MIB.
Additional status information about connected BCEs is
available from the relevant line MIBs
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { gBondAtmPort 2 }
gBondAtmPortStatusEntry OBJECT-TYPE
SYNTAX GBondAtmPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the G.Bond ATM port Status table.
Each entry represents a G.Bond ATM port indexed by the
ifIndex.
Note that an G.Bond GBS port runs on top of a single
or multiple BCE port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { gBondAtmPortStatusTable 1 }
GBondAtmPortStatusEntry ::=
SEQUENCE {
-- ATM Port status entries
gBondAtmShowTime TimeTicks,
gBondAtmUpRxCellLossCount Counter32,
gBondAtmDownRxCellLossCount Counter32
}
gBondAtmShowTime OBJECT-TYPE
SYNTAX TimeTicks
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The accumulated time when a bonding group is in normal
operation."
REFERENCE
"[G.998.1] Sec. 11.4.2 - (3)"
::= { gBondAtmPortStatusEntry 1 }
gBondAtmUpRxCellLossCount OBJECT-TYPE
SYNTAX Counter32
Beili, et al. Expires July 13, 2007 [Page 11]
Internet-Draft G.Bond ATM MIB January 2007
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of cells that are lost at aggregation
output in the upstream direction from a bonding group
for the accumulation interval."
REFERENCE
"[G.998.1] Sec. 11.4.2 - (4)"
::= { gBondAtmPortStatusEntry 2 }
gBondAtmDownRxCellLossCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of cells that are lost at aggregation
output in the downstream direction from a bonding
group for the accumulation interval."
REFERENCE
"[G.998.1] Sec. 11.4.2 - (4)"
::= { gBondAtmPortStatusEntry 3 }
--
-- Conformance Statements
--
gBondAtmGroups OBJECT IDENTIFIER
::= { gBondAtmConformance 1 }
gBondAtmCompliances OBJECT IDENTIFIER
::= { gBondAtmConformance 2 }
-- Object Groups
gBondAtmBasicGroup OBJECT-GROUP
OBJECTS {
gBondAtmUpMaxDataRate,
gBondAtmDownMaxDataRate,
gBondAtmUpDiffDelayTolerence,
gBondAtmDownDiffDelayTolerence,
gBondAtmShowTime,
gBondAtmUpRxCellLossCount,
gBondAtmDownRxCellLossCount
}
STATUS current
DESCRIPTION
"A collection of objects representing management
Beili, et al. Expires July 13, 2007 [Page 12]
Internet-Draft G.Bond ATM MIB January 2007
information for G.Bond ATM ports."
::= { gBondAtmGroups 1 }
-- Compliance Statements
gBondAtmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for G.Bond ATM interfaces.
Compliance with the following external compliance
statements
is REQUIRED:
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
GBOND-MIB gBondCompliance"
MODULE -- this module
MANDATORY-GROUPS {
gBondAtmBasicGroup
}
::= { gBondAtmCompliances 1 }
END
5. Security Considerations
The readable objects in the GBOND-ATM-MIB module (i.e., those with
MAX-ACCESS other than not-accessible) may be considered sensitive in
some environments since, collectively, they provide information about
the performance of network interfaces and can reveal some aspects of
their configuration. In particular, since a bonded xDSL port can be
comprised of multiple Unshielded Twisted Pair (UTP) voice grade
copper, located in the same bundle with other pairs belonging to
another operator/customer, it is theoretically possible to eavesdrop
to a G.Bond transmission, simply by "listening" to a cross-talk from
the bonded pairs, especially if the parameters of the G.Bond link in
question are known.
In such environments it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
Beili, et al. Expires July 13, 2007 [Page 13]
Internet-Draft G.Bond ATM MIB January 2007
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. Acknowledgments
This document was produced by the IETF ADSL MIB Working Group [2].
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Beili, et al. Expires July 13, 2007 [Page 14]
Internet-Draft G.Bond ATM MIB January 2007
7.2. Informative References
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.
[G.998.1] ITU-T, "ATM-based multi-pair bonding", ITU-T
Recommendation G.998.3, January 2005.
[I-D.ietf-adslmib-gbond-mib]
Morgenstern, M. and N. Nair, "xDSL multi-pair bonding
(G.Bond) MIB", draft-ietf-adslmib-gbond-mib-00 (work in
progress), January 2006.
[IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864,
June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", RFC 4070, May 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005.
[WT-159] Morgenstern, M., Beili, E., and N. Nair, "Management
Framework for xDSL Bonding", DSL Forum technical
report WT-159, Jan 2006.
[af-phy-0086]
ATM Forum, "Inverse Multiplexing for ATM (IMA)
Beili, et al. Expires July 13, 2007 [Page 15]
Internet-Draft G.Bond ATM MIB January 2007
Specification Version 1.1", ATM Forum specification af-
pfy-0086.001, March 1999.
URIs
[1]
[2]
Authors' Addresses
Edward Beili
Actelis Networks
25 Bazel St.
Petach-Tikva 49103
Israel
Phone: +972-3-924-3491
Email: edward.beili@actelis.com
Moti Morgenstern
ECI Telecom
30 Hasivim St.
Petach-Tikva 49517
Israel
Phone: +972-3-926-6258
Email: moti.morgenstern@ecitele.com
Narendranath Nair
Wipro Technologies
Keonics Electronics City
Bangalore 560 100
India
Phone: +91-(0)99 00 12 96 29
Email: narendranath.nair@wipro.com
Beili, et al. Expires July 13, 2007 [Page 16]
Internet-Draft G.Bond ATM MIB January 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Beili, et al. Expires July 13, 2007 [Page 17]