draft-ietf-adslmib-adslext-11.txt   draft-ietf-adslmib-adslext-12.txt 
INTERNET-DRAFT ADSL Line Extension MIB Faye Ly INTERNET-DRAFT ADSL Line Extension MIB Faye Ly
Pedestal Networks Pedestal Networks
Gregory Bathrick Gregory Bathrick
Nokia Nokia
September 12, 2002 September 23, 2002
Definitions of Extension Managed Objects Definitions of Extension Managed Objects
for Asymmetric Digital Subscriber Lines for Asymmetric Digital Subscriber Lines
September 12, 2002 September 23, 2002
draft-ietf-adslmib-adslext-11.txt draft-ietf-adslmib-adslext-12.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
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.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes additional managed objects used for In particular, it describes additional managed objects used for
managing Asymmetric Digital Subscriber Line (ADSL) interfaces not managing Asymmetric Digital Subscriber Line (ADSL) interfaces not
covered by the ADSL Line MIB [RFC2662]. covered by the ADSL Line MIB (RFC 2662).
1. The SNMP Network Management Framework 1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events o Mechanisms for describing and naming objects and events
for the purpose of management. The first version of this for the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 Structure of Management Information (SMI) is called SMIv1
skipping to change at page 31, line 6 skipping to change at page 31, line 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of ADSL extension notifications." "The collection of ADSL extension notifications."
::= { adslExtGroups 6 } ::= { adslExtGroups 6 }
END END
7. Acknowledgments 7. Acknowledgments
This document is a product of the ADSL MIB Working Group. This document is a product of the ADSL MIB Working Group.
8. Normative References 8. References
8.1 Normative References
[ANSI T1.413] American National Standards Institute, ANSI T1.413, [ANSI T1.413] American National Standards Institute, ANSI T1.413,
Issue 2, "Standards Project for Interfaces Relating Issue 2, "Standards Project for Interfaces Relating
to Carrier to Customer Connection of ADSL Equipment", to Carrier to Customer Connection of ADSL Equipment",
1998. 1998.
[ETSI DTS/TM06006] European Telecommunications Standards Institute [ETSI DTS/TM06006] European Telecommunications Standards Institute
"ADSL European Specific Requirements", November "ADSL European Specific Requirements", November
2000. 2000.
skipping to change at page 31, line 29 skipping to change at page 31, line 31
transceivers", June 1999. transceivers", June 1999.
[ITU G.992.2] ITU-T Telecommunication Standardization Sector, [ITU G.992.2] ITU-T Telecommunication Standardization Sector,
"Splitterless asymmetric digital subscriber line "Splitterless asymmetric digital subscriber line
(ADSL) transceivers", June 1999. (ADSL) transceivers", June 1999.
[ITU G.997.1] ITU-T Telecommunication Standardization Sector, [ITU G.997.1] ITU-T Telecommunication Standardization Sector,
"Physical Layer Management of Digital Subscriber "Physical Layer Management of Digital Subscriber
Transceivers", June 1999. Transceivers", June 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2026] Bradner S., "The Internet Standards Process - [RFC2026] Bradner S., "The Internet Standards Process -
Revision 3", October 1996. Revision 3", October 1996.
[RFC2028] Hovey R., S. Bradner, "The Organizations Involved in [RFC2028] Hovey R., S. Bradner, "The Organizations Involved in
the IETF Standards Process", October 1996. the IETF Standards Process", October 1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2493] K. Tesink "Textual Conventions for MIB Modules Using
"Introduction to Version 3 of the Internet-standard Performance History Based on 15 Minute Intervals"
Network Management Framework", RFC 2570, April 1999. RFC 2493, January 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999. RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April 1999. Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
skipping to change at page 33, line 8 skipping to change at page 32, line 39
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2662] Bathrick, G. and F. Ly "Definitions of Managed Objects for [RFC2662] Bathrick, G. and F. Ly "Definitions of Managed Objects for
the ADSL Lines", May 1999. the ADSL Lines", May 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
8.2 Informative References
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
11. Security Considerations 11. Security Considerations
The following security matters should be considered when implementing The following security matters should be considered when implementing
this MIB. this MIB.
1) Blocking unauthorized access to the ADSL MIB via the element 1) Blocking unauthorized access to the ADSL MIB via the element
management system is outside the scope of this document. It should be management system is outside the scope of this document. It should be
noted that access to the MIB permits the unauthorized entity to noted that access to the MIB permits the unauthorized entity to
modify the profiles (section 6.4) such that both subscriber service modify the profiles (section 6.4) such that both subscriber service
and network operations can be interfered with. Subscriber service can and network operations can be interfered with. Subscriber service can
be altered by modifying any of a number of service characteristics be altered by modifying any of a number of service characteristics
such as rate partitioning and maximum transmission rates. Network such as rate partitioning and maximum transmission rates. Network
operations can be impacted by modification of notification thresholds operations can be impacted by modification of notification thresholds
such as Signal-to-Noise Ratio (SNR) margins. such as Signal-to-Noise Ratio (SNR) margins.
2) There are a number of managed objects in this MIB that may be 2) SNMPv1 by itself is such an insecure environment. Even if the
considered to contain sensitive information. In particular, the
certain objects may be considered sensitive in many environments,
since it would allow an intruder to obtain information about which
vendor's equipment is in use on the network. Therefore, it may be
important in some environments to control read access to these
objects and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. It is recommended access and GET (read) the objects in this MIB. It is recommended
that the implementors consider the security features as provided by that the implementors consider the security features as provided by
the SNMPv3 framework. Specifically, the use of the User-based the SNMPv3 framework. Specifically, the use of the User-based
Security Model RFC 2574 [21] and the View-based Access Control Model Security Model RFC 2574 [21] and the View-based Access Control Model
RFC 2575 [23] is recommended. RFC 2575 [23] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/