draft-ietf-adslmib-adsllinemib-07.txt   draft-ietf-adslmib-adsllinemib-08.txt 
INTERNET-DRAFT ADSL Line MIB Gregory Bathrick INTERNET-DRAFT ADSL Line MIB Gregory Bathrick
AG Communication Systems AG Communication Systems
Faye Ly Faye Ly
Copper Mountain Networks Copper Mountain Networks
May 5, 1999 May 14, 1999
Definitions of Managed Objects Definitions of Managed Objects
for the ADSL Lines for the ADSL Lines
May 5, 1999 May 14, 1999
draft-ietf-adslmib-adsllinemib-07.txt draft-ietf-adslmib-adsllinemib-08.txt
1. Status of this Memo 1. 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.
skipping to change at page 2, line 16 skipping to change at page 2, line 16
It should be noted that the ADSL Forum Network Management Working It should be noted that the ADSL Forum Network Management Working
Group provided input towards the content of this document. See the Group provided input towards the content of this document. See the
Acknowledgement Section for a list of individuals who made this Acknowledgement Section for a list of individuals who made this
document possible. document possible.
3. The SNMP Network Management Framework 3. 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 2271 [13]. o An overall architecture, described in RFC 2571 [13].
o Mechanisms for describing and naming objects and events for o Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 and Structure of Management Information (SMI) is called SMIv1 and
described in RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16]. described in RFC 1155 [14], RFC 1212 [15] and RFC 1215 [16].
The second version, called SMIv2, is described in RFC 1902 The second version, called SMIv2, is described in RFC 2578
[1], RFC 1903 [2] and RFC 1904 [17]. [1], RFC 2579 [2] and RFC 2580 [17].
o Message protocols for transferring management information. o Message protocols for transferring management information.
The first version of the SNMP message protocol is called The first version of the SNMP message protocol is called
SNMPv1 and described in RFC 1157 [7]. A second version of SNMPv1 and described in RFC 1157 [7]. A second version of
the SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[18] and RFC 1906 [19]. The third version of the message [18] and RFC 1906 [19]. The third version of the message
protocol is called SNMPv3 and described in RFC 1906 [19], RFC protocol is called SNMPv3 and described in RFC 1906 [19], RFC
2272 [20] and RFC 2274 [21]. 2572 [20] and RFC 2574 [21].
o Protocol operations for accessing management information. o Protocol operations for accessing management information.
The first set of protocol operations and associated PDU The first set of protocol operations and associated PDU
formats is described in RFC 1157 [7]. A second set of formats is described in RFC 1157 [7]. A second set of
protocol operations and associated PDU formats is described protocol operations and associated PDU formats is described
in RFC 1905 [8]. in RFC 1905 [8].
o A set of fundamental applications described in RFC 2273 [22] o A set of fundamental applications described in RFC 2573 [22]
and the view-based access control mechanism described in RFC and the view-based access control mechanism described in RFC
2275 [23]. 2575 [23].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This document specifies a MIB module that is compliant to the SMIv2. This document specifies a MIB module that is compliant to the SMIv2.
A MIB conforming to the SMIv1 can be produced through the appropriate A MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (e.g., use of Counter64). Some machine translation is possible (e.g., use of Counter64). Some machine
readable information in SMIv2 will be converted into textual readable information in SMIv2 will be converted into textual
descriptions in SMIv1 during the translation process. However, this descriptions in SMIv1 during the translation process. However, this
loss of machine readable information is not considered to change the loss of machine readable information is not considered to change the
semantics of the MIB. semantics of the MIB.
skipping to change at page 7, line 4 skipping to change at page 6, line 42
Figure 3: Use of ifStackTable (part 1) Figure 3: Use of ifStackTable (part 1)
The ifStackTable is then used to show the relationships between the The ifStackTable is then used to show the relationships between the
various ADSL interfaces, as illustrated below in figure 4. various ADSL interfaces, as illustrated below in figure 4.
HigherLayer LowerLayer HigherLayer LowerLayer
-------------------------- --------------------------
j i j i
k i k i
Figure 4: Use of ifStackTable (part 2)
Figure 4: Use of ifStackTable (part 2)
The ifRcvAddressTable is not applicable for ADSL interfaces. The ifRcvAddressTable is not applicable for ADSL interfaces.
5.2 Relationship with RFC 2037 [25] 5.2 Relationship with RFC 2037 [25]
Implementation of the Entity MIB [25] is optional. It in no way Implementation of the Entity MIB [25] is optional. It in no way
alters the information required in the adslLineMib, nor does it alter alters the information required in the adslLineMib, nor does it alter
the relationship with IF-MIB. the relationship with IF-MIB.
The Entity MIB introduces a standardized way of presenting the The Entity MIB introduces a standardized way of presenting the
components of complex systems, such as a Digital Subscriber Line components of complex systems, such as a Digital Subscriber Line
skipping to change at page 13, line 10 skipping to change at page 13, line 4
ADSL lines. ADSL lines.
o MODE-II: Static Profiles - one profile per ADSL physical line o MODE-II: Static Profiles - one profile per ADSL physical line
always. always.
6.4.1 MODE-I : Dynamic Profiles 6.4.1 MODE-I : Dynamic Profiles
Implementations using this mode will enable the manager to Implementations using this mode will enable the manager to
dynamically create and delete profiles as needed. The index of the dynamically create and delete profiles as needed. The index of the
profile is an locally-unique administratively assigned name for the profile is an locally-unique administratively assigned name for the
profile having the textual convention `SnmpAdminString' profile having the textual convention `SnmpAdminString' (RFC2571
(RFC2271[13]). [13]).
One or more ADSL lines may be configured to share parameters of a One or more ADSL lines may be configured to share parameters of a
single profile (e.g., adslLineConfProfileName = `silver') by setting single profile (e.g., adslLineConfProfileName = `silver') by setting
its adslLineConfProfile objects to the index value of this profile. its adslLineConfProfile objects to the index value of this profile.
If a change is made to the profile, all lines that refer to it will If a change is made to the profile, all lines that refer to it will
be re-configured to the changed parameters. Before a profile can be be re-configured to the changed parameters. Before a profile can be
deleted or taken out of service it must be first unreferenced from deleted or taken out of service it must be first unreferenced from
all associated lines. all associated lines.
This figure below shows an example of how this mode can be This figure below shows an example of how this mode can be
skipping to change at page 16, line 46 skipping to change at page 16, line 43
7. Conformance and Compliance 7. Conformance and Compliance
See the conformance and compliance statements within the information See the conformance and compliance statements within the information
module. module.
8. Definitions 8. Definitions
ADSL-TC-MIB DEFINITIONS ::= BEGIN ADSL-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Gauge32, transmission,
OBJECT-TYPE, mib-2 FROM SNMPv2-SMI MODULE-IDENTITY, Gauge32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
adsltcmib MODULE-IDENTITY adsltcmib MODULE-IDENTITY
LAST-UPDATED "9905052200Z" LAST-UPDATED "9905052200Z"
ORGANIZATION "IETF ADSL MIB Working Group" ORGANIZATION "IETF ADSL MIB Working Group"
CONTACT-INFO CONTACT-INFO
" "
Gregory Bathrick Gregory Bathrick
AG Communication Systems AG Communication Systems
A Subsidiary of Lucent Technologies A Subsidiary of Lucent Technologies
2500 W Utopia Rd. 2500 W Utopia Rd.
skipping to change at page 17, line 38 skipping to change at page 17, line 34
Tel: +1 650-858-8500 Tel: +1 650-858-8500
Fax: +1 650-858-8085 Fax: +1 650-858-8085
E-Mail: faye@coppermountain.com E-Mail: faye@coppermountain.com
IETF ADSL MIB Working Group (adsl@xlist.agcs.com) IETF ADSL MIB Working Group (adsl@xlist.agcs.com)
" "
DESCRIPTION DESCRIPTION
"The MIB module which provides a ADSL "The MIB module which provides a ADSL
Line Coding Textual Convention to be used Line Coding Textual Convention to be used
by ADSL Lines." by ADSL Lines."
::= { mib-2 94 2 } -- adslMIB 2 ::= { transmission 94 2 } -- adslMIB 2
AdslLineCodingType ::= TEXTUAL-CONVENTION AdslLineCodingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax for the ADSL "This data type is used as the syntax for the ADSL
Line Code." Line Code."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1),-- none of the following other(1),-- none of the following
dmt (2), -- Discrete MultiTone dmt (2), -- Discrete MultiTone
cap (3), -- Carrierless Amplitude & Phase modulation cap (3), -- Carrierless Amplitude & Phase modulation
skipping to change at page 19, line 9 skipping to change at page 19, line 5
AdslPerfTimeElapsed ::= TEXTUAL-CONVENTION AdslPerfTimeElapsed ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds that have elapsed since "The number of seconds that have elapsed since
the beginning of the current measurement period. the beginning of the current measurement period.
If, for some reason, such as an adjustment in the If, for some reason, such as an adjustment in the
system's time-of-day clock, the current interval system's time-of-day clock, the current interval
exceeds the maximum value, the agent will return exceeds the maximum value, the agent will return
the maximum value." the maximum value."
SYNTAX Gauge32 END SYNTAX Gauge32
END
ADSL-LINE-MIB DEFINITIONS ::= BEGIN ADSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Gauge32, Counter32, Gauge32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
transmission, Unsigned32 FROM SNMPv2-SMI transmission, Unsigned32 FROM SNMPv2-SMI
RowStatus, RowStatus,
TruthValue, VariablePointer FROM SNMPv2-TC TruthValue, VariablePointer FROM SNMPv2-TC
skipping to change at page 68, line 11 skipping to change at page 68, line 5
::= { adslMibObjects 14} ::= { adslMibObjects 14}
adslLineConfProfileEntry OBJECT-TYPE adslLineConfProfileEntry OBJECT-TYPE
SYNTAX AdslLineConfProfileEntry SYNTAX AdslLineConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of an ADSL modem. represents the configuration of an ADSL modem.
When `dynamic' profiles are implemented, a When `dynamic' profiles are implemented, a default
profile is created in one step with all necessary
parameter values and adslLineConfProfileRowStatus set
to createAndGo. This RowStatus object is also used
to destroy profiles.
Also when `dynamic' profiles are implemented, a default
profile will always exist. This profile's name will profile will always exist. This profile's name will
be set to `DEFVAL' and its parameters will be set be set to `DEFVAL' and its parameters will be set
to vendor specific values, unless otherwise specified to vendor specific values, unless otherwise specified
in this document. in this document.
When `static' profiles are implemented, profiles When `static' profiles are implemented, profiles
are automaticly created or destroyed as ADSL are automaticly created or destroyed as ADSL
physical lines are discovered and removed by physical lines are discovered and removed by
the system. The name of the profile will be the system. The name of the profile will be
equivalent to the decimal value of the line's equivalent to the decimal value of the line's
skipping to change at page 78, line 26 skipping to change at page 78, line 14
::= { adslMibObjects 15} ::= { adslMibObjects 15}
adslLineAlarmConfProfileEntry OBJECT-TYPE adslLineAlarmConfProfileEntry OBJECT-TYPE
SYNTAX AdslLineAlarmConfProfileEntry SYNTAX AdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry consists of a list of parameters that "Each entry consists of a list of parameters that
represents the configuration of an ADSL modem. represents the configuration of an ADSL modem.
When `dynamic' profiles are implemented, a When `dynamic' profiles are implemented, a default
profile is created in one step with all necessary
parameter values and adslLineConfProfileRowStatus set
to createAndGo. This RowStatus object is also used
to destroy profiles.
Also when `dynamic' profiles are implemented, a default
profile will always exist. This profile's name will profile will always exist. This profile's name will
be set to `DEFVAL' and its parameters will be set to be set to `DEFVAL' and its parameters will be set to
vendor specific values, unless otherwise specified vendor specific values, unless otherwise specified
in this document. in this document.
When `static' profiles are implemented, profiles When `static' profiles are implemented, profiles
are automaticly created or destroyed as ADSL are automaticly created or destroyed as ADSL
physical lines are discovered and removed by physical lines are discovered and removed by
the system. The name of the profile will be the system. The name of the profile will be
equivalent to the decimal value of the line's equivalent to the decimal value of the line's
skipping to change at page 89, line 8 skipping to change at page 88, line 37
"This group is optional. Implementations which "This group is optional. Implementations which
require ATU-C channel block event counters should require ATU-C channel block event counters should
implement this group." implement this group."
GROUP adslAturChanPerformanceGroup GROUP adslAturChanPerformanceGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require ATU-R channel block event counters should require ATU-R channel block event counters should
implement this group." implement this group."
OBJECT adslAtucIntervalNumber OBJECT adslLineConfProfile
SYNTAX INTEGER (1..1) MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C 15-minute "Read-only access is applicable when static
performance interval." profiles are implemented."
OBJECT adslAturIntervalNumber OBJECT adslAtucConfRateMode
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R 15-minute "Read-write access is applicable when
performance interval." static profiles are implemented."
OBJECT adslAtucChanIntervalNumber OBJECT adslAtucConfRateChanRatio
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C "Read-write access is applicable when
channel 15-minute performance interval." static profiles are implemented."
OBJECT adslAturChanIntervalNumber OBJECT adslAtucConfTargetSnrMgn
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R "Read-write access is applicable when
channel 15-minute performance interval." static profiles are implemented."
OBJECT adslLineConfProfile OBJECT adslAtucConfMaxSnrMgn
MIN-ACCESS read-only MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"Read-only access is applicable when static "Read-write access is applicable when
profiles are implemented." static profiles are implemented."
OBJECT adslAtucConfMinSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucConfDownshiftSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucConfUpshiftSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucConfMinUpshiftTime
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucConfMinDownshiftTime
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucChanConfFastMinTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucChanConfInterleaveMinTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucChanConfFastMaxTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucChanConfInterleaveMaxTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucChanConfMaxInterleaveDelay
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfRateMode
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfRateChanRatio
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfTargetSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfMaxSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfMinSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfDownshiftSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfUpshiftSnrMgn
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfMinUpshiftTime
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturConfMinDownshiftTime
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturChanConfFastMinTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturChanConfInterleaveMinTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturChanConfFastMaxTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturChanConfInterleaveMaxTxRate
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturChanConfMaxInterleaveDelay
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslLineConfProfileRowStatus OBJECT adslLineConfProfileRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-only access is applicable only when static "Read-only access is applicable only when static
profiles are implemented." profiles are implemented."
OBJECT adslLineAlarmConfProfile OBJECT adslLineAlarmConfProfile
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-only access is applicable only when static "Read-only access is applicable only when static
profiles are implemented." profiles are implemented."
OBJECT adslAtucThresh15MinLofs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThresh15MinLoss
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThresh15MinLols
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThresh15MinLprs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThresh15MinESs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshFastRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshInterleaveRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshFastRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshInterleaveRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucInitFailureTrapEnable
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLofs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLoss
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLprs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinESs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshFastRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshInterleaveRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshFastRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshInterleaveRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslLineAlarmConfProfileRowStatus OBJECT adslLineAlarmConfProfileRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-only access is applicable only when static "Read-only access is applicable only when static
profiles are implemented." profiles are implemented."
::= { adslCompliances 1 } ::= { adslCompliances 1 }
-- ATU-R agent compliance statements -- ATU-R agent compliance statements
adslLineMibAturCompliance MODULE-COMPLIANCE adslLineMibAturCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities "The compliance statement for SNMP entities
which manage ADSL ATU-R interfaces." which manage ADSL ATU-R interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS MANDATORY-GROUPS
skipping to change at page 91, line 6 skipping to change at page 95, line 47
"This group is optional. Implementations which "This group is optional. Implementations which
require ATU-C channel block event counters should require ATU-C channel block event counters should
implement this group." implement this group."
GROUP adslAturAturChanPerformanceGroup GROUP adslAturAturChanPerformanceGroup
DESCRIPTION DESCRIPTION
"This group is optional. Implementations which "This group is optional. Implementations which
require ATU-R channel block event counters should require ATU-R channel block event counters should
implement this group." implement this group."
OBJECT adslAtucIntervalNumber OBJECT adslLineAlarmConfProfile
SYNTAX INTEGER (1..1) MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C 15-minute "Read-only access is applicable only when static
performance interval." profiles are implemented."
OBJECT adslAtucThresh15MinLofs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturIntervalNumber OBJECT adslAtucThresh15MinLoss
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R 15-minute "Read-write access is applicable when
performance interval." static profiles are implemented."
OBJECT adslAtucChanIntervalNumber OBJECT adslAtucThresh15MinESs
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-C "Read-write access is applicable when
channel 15-minute performance interval." static profiles are implemented."
OBJECT adslAturChanIntervalNumber OBJECT adslAtucThreshFastRateUp
SYNTAX INTEGER (1..1) MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"It is allowable to implement only one ATU-R "Read-write access is applicable when
channel 15-minute performance interval." static profiles are implemented."
OBJECT adslLineAlarmConfProfile OBJECT adslAtucThreshInterleaveRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucThreshFastRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAtucInitFailureTrapEnable
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLofs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLoss
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinLprs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThresh15MinESs
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshFastRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshInterleaveRateUp
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshFastRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslAturThreshInterleaveRateDown
MIN-ACCESS read-write
DESCRIPTION
"Read-write access is applicable when
static profiles are implemented."
OBJECT adslLineAlarmConfProfileRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Read-only access is applicable only when static "Read-only access is applicable only when static
profiles are implemented." profiles are implemented."
OBJECT adslAtucCurrStatus OBJECT adslAtucCurrStatus
SYNTAX BITS { SYNTAX BITS {
noDefect(0), noDefect(0),
lossOfFraming(1), lossOfFraming(1),
lossOfSignal(2) lossOfSignal(2)
} }
DESCRIPTION DESCRIPTION
"It is allowable to implement only noDefect(0), "It is allowable to implement only noDefect(0),
lossOfFraming(1) and lossOfSignal(2) by the ATU-R lossOfFraming(1) and lossOfSignal(2) by the ATU-R
agent." agent."
skipping to change at page 98, line 6 skipping to change at page 104, line 22
::= { adslGroups 14 } ::= { adslGroups 14 }
adslAturPhysicalGroup OBJECT-GROUP adslAturPhysicalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
adslAtucInvVendorID, adslAtucInvVendorID,
adslAtucInvVersionNumber, adslAtucInvVersionNumber,
adslAtucCurrOutputPwr, adslAtucCurrAttainableRate, adslAtucCurrOutputPwr, adslAtucCurrAttainableRate,
adslAturInvSerialNumber, adslAturInvVendorID, adslAturInvSerialNumber, adslAturInvVendorID,
adslAturInvVersionNumber, adslAturCurrSnrMgn, adslAturInvVersionNumber, adslAturCurrSnrMgn,
adslAturCurrAtn, adslAturCurrStatus, adslAturCurrAtn, adslAturCurrStatus,
adslAturCurrOutputPwr, adslAturCurrAttainableRate adslAturCurrOutputPwr, adslAturCurrAttainableRate,
adslAtucCurrStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing physical "A collection of objects providing physical
configuration information of the ADSL Line on the configuration information of the ADSL Line on the
ATU-R side." ATU-R side."
::= { adslGroups 15 } ::= { adslGroups 15 }
adslAturChannelGroup OBJECT-GROUP adslAturChannelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 102, line 33 skipping to change at page 108, line 50
adslAturPerfLofsThreshTrap, adslAturPerfLofsThreshTrap,
adslAturPerfLossThreshTrap, adslAturPerfLossThreshTrap,
adslAturPerfLprsThreshTrap, adslAturPerfLprsThreshTrap,
adslAturPerfESsThreshTrap, adslAturPerfESsThreshTrap,
adslAturRateChangeTrap adslAturRateChangeTrap
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of ADSL notifications implemented by "The collection of ADSL notifications implemented by
the ATU-R agent." the ATU-R agent."
::= { adslGroups 25 } END ::= { adslGroups 25 }
END
9. Acknowledgments 9. Acknowledgments
The current authors/editors are: The current authors/editors are:
Gregory Bathrick (AG Communication Systems) Gregory Bathrick (AG Communication Systems)
Faye Ly (Copper Mountain Networks) Faye Ly (Copper Mountain Networks)
Input from the ADSL Forum was edited by: Input from the ADSL Forum was edited by:
skipping to change at page 103, line 33 skipping to change at page 110, line 4
Mike Sneed (Pulsecom) Mike Sneed (Pulsecom)
Ted Soo-Hoo (Pulsecom) Ted Soo-Hoo (Pulsecom)
John Stehman (Diamond Lane) John Stehman (Diamond Lane)
Chuck Storry (Newbridge) Chuck Storry (Newbridge)
Chi-Lin Tom (AFC) Chi-Lin Tom (AFC)
Frank Van der Putten (Alcatel) Frank Van der Putten (Alcatel)
Marc Van Vlimmeren (Alcatel) Marc Van Vlimmeren (Alcatel)
Bert Wijnen (IBM) Bert Wijnen (IBM)
10. References 10. References
[1] B. Wijnen, D. Harrington, R. Presuhn, "Structure of
Management Information Version 2 (SMIv2)" RFC 2578,
April 1999.
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [2] K. McCloghrie, D. Perkins, J. Schoenwaelder,
S. Waldbusser, "Structure of Management Information for Version "Textual Conventions for SMIv2", RFC 2579, April 1999.
2 of the Simple Network Management Protocol (SNMPv2)",
RFC 1902, January 1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for SNMPv2", RFC 1903, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[3] ADSL Forum TR-005, "Network Management Element Management", [3] ADSL Forum TR-005, "Network Management Element Management",
March 1998. March 1998.
[4] McCloghrie, K., and M. Rose, Editors, "Management [4] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991. Performance Systems International, March 1991.
[5] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [5] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
skipping to change at page 104, line 26 skipping to change at page 110, line 40
Research, Performance Systems International, MIT Lab for Research, Performance Systems International, MIT Lab for
Computer Science, May 1990. Computer Science, May 1990.
[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Protocol Operations for Version 2 of the Simple S. Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[9] ADSL Forum TR-006, "SNMP-based ADSL Line MIB", March 1998. [9] ADSL Forum TR-006, "SNMP-based ADSL Line MIB", March 1998.
[10] American National Standards Institute, ANSI T1.413-1995, [10] American National Standards Institute, ANSI T1.413-1995,
August 1995. August 1995
[11] ADSL Forum WT-014, "DMT Line Code Specific MIB", February 1999. [11] ADSL Forum WT-014, "DMT Line Code Specific MIB", February 1999
[12] ADSL Forum WT-015, "CAP Line Code Specific MIB", February 1999. [12] ADSL Forum WT-015, "CAP Line Code Specific MIB", February 1999
[13] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [13] B. Wijnen, D. Harrington, R. Presuhn, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2571, April 1999
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[14] Rose, M., and K. McCloghrie, "Structure and Identification of [14] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990 Performance Systems International, Hughes LAN Systems, May 1990
[15] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [15] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems, RFC 1212, Performance Systems International, Hughes LAN Systems,
March 1991 March 1991
[16] M. Rose, "A Convention for Defining Traps for use with the [16] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, Performance Systems International, March SNMP", RFC 1215, Performance Systems International, March
1991 1991
[17] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [17] K. McCloghrie, D. Perkins, J. Schoenwaelder, "Conformance
Waldbusser, "Conformance Statements for Version 2 of the Simple Statements for SMIv2", RFC 2580, April 1999
Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [18] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901,
SNMP Research, Inc., Cisco Systems, Inc., Dover Beach SNMP Research, Inc., Cisco Systems, Inc., Dover Beach
Consulting, Inc., International Network Services, January 1996. Consulting, Inc., International Network Services, January 1996.
[19] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. [19] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for Version 2 of the Simple Waldbusser, "Transport Mappings for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Network Management Protocol (SNMPv2)", RFC 1906, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996. International Network Services, January 1996.
[20] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [20] Case, J., Harrington D., R. Presuhn, B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Protocol (SNMP)", RFC 2572, April 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[21] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [21] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. (SNMPv3)", RFC 2574, Aprile 1999.
[22] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications", [22] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications",
RFC 2273, SNMP Research, Inc., Secure Computing Corporation, RFC 2573, April 1999.
Cisco Systems, January 1998.
[23] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [23] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software,
Inc., Cisco Systems, Inc., January 1998. Inc., Cisco Systems, Inc., April 1999.
[24] Ahmed, M., and K. Tesink, Editors, "Definitions of Managed [24] Ahmed, M., and K. Tesink, Editors, "Definitions of Managed
Objects for ATM Management Version 8.0 using SMIv2", RFC 1695, Objects for ATM Management Version 8.0 using SMIv2", RFC 1695,
Bell Communications Research, August 1994. Bell Communications Research, August 1994.
[25] McCloghrie, K. and A. Bierman, "Entity MIB", RFC 2037, October [25] McCloghrie, K. and A. Bierman, "Entity MIB", RFC 2037, October
1996. 1996.
[26] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO [26] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO
10646", RFC 2044, October 1996. 10646", RFC 2044, October 1996.
skipping to change at page 106, line 27 skipping to change at page 112, line 33
objects and possibly to even encrypt the values of these object when objects and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of SNMP sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment. provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the 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 2274 [21] and the View-based Access Control Model Security Model RFC 2574 [21] and the View-based Access Control Model
RFC 2275 [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
configured to give access to those objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
3) ADSL layer connectivity from the ATU-R will permit the subscriber 3) ADSL layer connectivity from the ATU-R will permit the subscriber
to manipulate both the ADSL link directly and the AOC/EOC channels to manipulate both the ADSL link directly and the AOC/EOC channels
for their own loop. For example, unchecked or unfiltered for their own loop. For example, unchecked or unfiltered
fluctuations initiated by the subscriber could generate sufficient fluctuations initiated by the subscriber could generate sufficient
skipping to change at page 107, line 35 skipping to change at page 113, line 40
4. Object Definitions ..................................... 3 4. Object Definitions ..................................... 3
5. Relationship of the ADSL LINE MIB with standard MIBs ... 3 5. Relationship of the ADSL LINE MIB with standard MIBs ... 3
6. Conventions used in the MIB ............................ 7 6. Conventions used in the MIB ............................ 7
7. Conformance and Compliance ............................. 16 7. Conformance and Compliance ............................. 16
8. Definitions ............................................ 16 8. Definitions ............................................ 16
9. Acknowledgments ........................................ 102 9. Acknowledgments ........................................ 109
10. References ............................................. 103 10. References ............................................. 109
11. Security Considerations ................................ 105 11. Security Considerations ................................ 112
12. Authors' Addresses ..................................... 106 12. Authors' Addresses ..................................... 112
 End of changes. 

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