![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A new IETF working group has been proposed in the Operations and
Management Area. The IESG has not made any determination as yet.
The following Description was submitted, and is provided for
informational purposes:
ADSL MIB (adslmib)
------------------
Current Status: Proposed Working Group
Chair(s):
Michael Sneed <mike.sneed at pulse.com>
David Allan <dallan at nortel.ca>
Operations and Management Area Director(s):
Harald Alvestrand <Harald.Alvestrand at maxware.no>
Bert Wijnen <wijnen at vnet.ibm.com>
Operations and Management Area Advisor:
Bert Wijnen <wijnen at vnet.ibm.com>
Technical Advisor(s):
Kaj Tesink <kaj at cc.bellcore.com>
Editor(s):
Greg Bathrick <bathricg at agcs.com>
Mailing Lists:
General Discussion:adsl at xlist.agcs.com
To Subscribe: mgr at xlist.agcs.com
In Body: subscribe/unsubscribe adsl
Archive: http://www.agcs.com/adsl/
Description of Working Group:
The ADSL Working Group is chartered to define a set of managed objects
to be used for management of Asymmetric Digital Subscriber Line services
as defined by ANSI T1.413. The initial effort will define those
management objects common to all ADSL lines regardless of line-code.
The devices to be managed using these managed objects will include:
1) Access provider equipment containing ATU-C modems,
such as DSLAMs, and
2) Subscriber equipment containing ATU-R modems such as routers,
NIC cards, and standalone modem devices.
The MIBs defined by this group will be generated using SMIv2, will be
consistent with the SNMP management framework, and will describe the
relationship of the objects defined to existing MIBs such as those
described by RFC2233, and RFC1695. The working group will consider the
input of the ADSL forum, and will utilize the existing ADSL Forum line
MIB as a starting point for its work when that document is submitted as
an Internet Draft. The working group plans on producing a single
standards track MIB suitable for use in both access provider and
subscriber equipment.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.