draft-ietf-adslmib-vdsl-12.txt   rfc3728.txt 
Network Working Group B. Ray Network Working Group B. Ray
Category: Internet Draft PESA Switching Systems Request for Comments: 3728 PESA Switching Systems
R. Abbi Category: Standards Track R. Abbi
Alcatel Alcatel
September 2003 February 2004
Definitions of Managed Objects for Very High Definitions of Managed Objects for Very High
Speed Digital Subscriber Lines (VDSL) Speed Digital Subscriber Lines (VDSL)
draft-ietf-adslmib-vdsl-12.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects used for managing Very High Speed particular, it describes objects used for managing Very High Speed
Digital Subscriber Line (VDSL) interfaces. Digital Subscriber Line (VDSL) interfaces.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework .................... 2 1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Overview ...................................................... 2 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1 Relationship of the VDSL Line MIB Module to other MIB Modules . 3 2.1. Relationship of the VDSL Line MIB Module to other MIB
2.2 Conventions used in the MIB Module ............................ 4 Modules. . . . . . . . . . . . . . . . . . . . . . . . . 2
2.3 Structure ..................................................... 5 2.2. Conventions used in the MIB Module . . . . . . . . . . . 4
2.4 Counters, Interval Buckets and Thresholds ..................... 6 2.3. Structure. . . . . . . . . . . . . . . . . . . . . . . . 5
2.5 Profiles ...................................................... 7 2.4. Counters, Interval Buckets and Thresholds. . . . . . . . 7
2.6 Notifications ................................................. 8 2.5. Profiles . . . . . . . . . . . . . . . . . . . . . . . . 8
2.7 Persistence ................................................... 9 2.6. Notifications. . . . . . . . . . . . . . . . . . . . . . 9
3. Conformance and Compliance .................................... 10 2.7. Persistence. . . . . . . . . . . . . . . . . . . . . . . 10
4. Definitions ................................................... 10 3. Conformance and Compliance . . . . . . . . . . . . . . . . . . 11
5. Intellectual Property ......................................... 64 4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Normative References .......................................... 64 5. Security Considerations. . . . . . . . . . . . . . . . . . . . 71
7. Informative References ........................................ 65 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8. Security Considerations ....................................... 66 6.1. Normative References . . . . . . . . . . . . . . . . . . 72
9. Acknowledgements .............................................. 67 6.2. Informative References . . . . . . . . . . . . . . . . . 74
10. Authors' Addresses ............................................ 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 74
11. Full Copyright Statement ...................................... 68 8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 75
9. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 76
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a MIB
MIB module that is compliant to the SMIv2, which is described in STD module that is compliant to the SMIv2, which is described in STD 58,
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
2580 [RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Overview 2. Overview
This document describes an SNMP MIB module for managing VDSL Lines. This document describes an SNMP MIB module for managing VDSL Lines.
These definitions are based upon the specifications for VDSL as These definitions are based upon the specifications for VDSL as
defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011, defined in T1E1, ETSI, and ITU documentation [T1E1311, T1E1011,
T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971]. T1E1013, ETSI2701, ETSI2702, ITU9931, ITU9971].
The MIB module is located in the MIB tree under MIB 2 transmission, The MIB module is located in the MIB tree under MIB 2 transmission,
as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
of this document. this document.
2.1 Relationship of the VDSL Line MIB Module to other MIB Modules 2.1. Relationship of the VDSL Line MIB Module to other MIB Modules
This section outlines the relationship of this MIB with other MIBs This section outlines the relationship of this MIB with other MIBs
described in RFCs. Specifically, IF-MIB as presented in RFC 2863 described in RFCs. Specifically, IF-MIB as presented in RFC 2863
[RFC2863] is discussed. [RFC2863] is discussed.
2.1.1 General IF-MIB Integration (RFC 2863) 2.1.1. General IF-MIB Integration (RFC 2863)
The VDSL Line MIB specifies the detailed attributes of a data The VDSL Line MIB specifies the detailed attributes of a data
interface. As such, it needs to integrate with RFC 2863 [RFC2863]. interface. As such, it needs to integrate with RFC 2863 [RFC2863].
The IANA has assigned the following ifType to VDSL: The IANA has assigned the following ifType to VDSL:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
vdsl(97), -- Very H-speed Digital Subscrib. Loop vdsl(97), -- Very H-speed Digital Subscrib. Loop
... ...
} }
Additionally, a VDSL line may contain an optional fast channel Additionally, a VDSL line may contain an optional fast channel and an
and an optional interleaved channel which also integrate into RFC optional interleaved channel which also integrate into RFC 2863
2863 [RFC2863]. The IANA has assigned the following ifTypes to [RFC2863]. The IANA has assigned the following ifTypes to these
these channels: channels:
IANAifType ::= TEXTUAL-CONVENTION IANAifType ::= TEXTUAL-CONVENTION
... ...
SYNTAX INTEGER { SYNTAX INTEGER {
... ...
interleave (124), -- Interleave channel interleave (124), -- Interleave channel
fast (125), -- Fast channel fast (125), -- Fast channel
... ...
} }
2.1.2 Usage of ifTable 2.1.2. Usage of ifTable
The MIB branch identified by this ifType contains tables appropriate The MIB branch identified by this ifType contains tables appropriate
for this interface type. Most such tables extend the ifEntry table, for this interface type. Most tables extend the ifEntry table, and
and are indexed by ifIndex. For interfaces in systems implementing are indexed by ifIndex. For interfaces in systems implementing this
this MIB, those table entries indexed by ifIndex MUST be persistent. MIB, those table entries indexed by ifIndex MUST be persistent.
The following attributes are part of the mandatory ifGeneral group The following attributes are part of the mandatory ifGeneral group in
in RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB. RFC 2863 [RFC2863], and are not duplicated in the VDSL Line MIB.
=================================================================== ===================================================================
ifIndex Interface index. ifIndex Interface index.
ifDescr See interfaces MIB [RFC2863]. ifDescr See interfaces MIB [RFC2863].
ifType vdsl(97), ifType vdsl(97),
interleave(124), or interleave(124), or
fast(125) fast(125)
ifSpeed Set as appropriate. ifSpeed Set as appropriate.
ifPhysAddress This object MUST have an octet string ifPhysAddress This object MUST have an octet string
with zero length. with zero length.
ifAdminStatus See interfaces MIB [RFC2863]. ifAdminStatus See interfaces MIB [RFC2863].
ifOperStatus See interfaces MIB [RFC2863]. ifOperStatus See interfaces MIB [RFC2863].
ifLastChange See interfaces MIB [RFC2863]. ifLastChange See interfaces MIB [RFC2863].
skipping to change at page 4, line 29 skipping to change at page 4, line 23
ifConnectorPresent Set as appropriate. ifConnectorPresent Set as appropriate.
ifLinkUpDownTrapEnable Default to enabled(1). ifLinkUpDownTrapEnable Default to enabled(1).
=================================================================== ===================================================================
Figure 1: Use of ifTable Objects Figure 1: Use of ifTable Objects
Section 2.3, below, describes the structure of this MIB in relation Section 2.3, below, describes the structure of this MIB in relation
to ifEntry in greater detail. to ifEntry in greater detail.
2.2 Conventions used in the MIB Module 2.2. Conventions used in the MIB Module
2.2.1 Naming Conventions 2.2.1. Naming Conventions
A. Vtuc -- (VTUC) transceiver at near (Central) end of line A. Vtuc -- (VTUC) transceiver at near (Central) end of line
B. Vtur -- (VTUR) transceiver at Remote end of line B. Vtur -- (VTUR) transceiver at Remote end of line
C. Vtu -- One of either Vtuc or Vtur C. Vtu -- One of either Vtuc or Vtur
D. Curr -- Current D. Curr -- Current
E. Prev -- Previous E. Prev -- Previous
F. Atn -- Attenuation F. Atn -- Attenuation
G. ES -- Errored Second G. ES -- Errored Second
H. SES -- Severely Errored Second H. SES -- Severely Errored Second
I. UAS -- Unavailable Second I. UAS -- Unavailable Second
skipping to change at page 5, line 5 skipping to change at page 5, line 5
O. xxxs -- Sum of Seconds in which xxx has occured O. xxxs -- Sum of Seconds in which xxx has occured
(e.g., xxx = Lof, Los, Lpr, Lol) (e.g., xxx = Lof, Los, Lpr, Lol)
P. Max -- Maximum P. Max -- Maximum
Q. Mgn -- Margin Q. Mgn -- Margin
R. Min -- Minimum R. Min -- Minimum
S. Psd -- Power Spectral Density S. Psd -- Power Spectral Density
T. Snr -- Signal to Noise Ratio T. Snr -- Signal to Noise Ratio
U. Tx -- Transmit U. Tx -- Transmit
V. Blks -- Blocks V. Blks -- Blocks
2.2.2 Textual Conventions 2.2.2. Textual Conventions
The following textual conventions are defined to reflect the line The following textual conventions are defined to reflect the line
topology in the MIB (further discussed in the following section) topology in the MIB (further discussed in the following section) and
and to define the behavior of the statistics to be maintained to define the behavior of the statistics to be maintained by an
by an agent. agent.
o VdslLineCodingType : o VdslLineCodingType :
Attributes with this syntax identify the line coding used. Attributes with this syntax identify the line coding used. Specified
Specified as an INTEGER, the three values are: as an INTEGER, the three values are:
other(1) -- none of the following other(1) -- none of the following
mcm(2) -- Multiple Carrier Modulation mcm(2) -- Multiple Carrier Modulation
scm(3) -- Single Carrier Modulation scm(3) -- Single Carrier Modulation
o VdslLineEntity : o VdslLineEntity :
Attributes with this syntax reference the two sides of a line. Attributes with this syntax reference the two sides of a line.
Specified as an INTEGER, the two values are: Specified as an INTEGER, the two values are:
vtuc(1) -- central site transceiver vtuc(1) -- central site transceiver
vtur(2) -- remote site transceiver vtur(2) -- remote site transceiver
2.3 Structure 2.3 Structure
The MIB is structured into the following MIB groups: The MIB is structured into the following MIB groups:
o vdslGroup : o vdslGroup :
This group supports all line code independent MIB objects found This group supports all line code independent MIB objects found in
in this MIB. The following tables contain objects permitted for this MIB. The following tables contain objects permitted for ifType
ifType vdsl(97): vdsl(97):
- vdslLineTable - vdslLineTable
- vdslPhysTable - vdslPhysTable
- vdslPerfDataTable - vdslPerfDataTable
- vdslPerfIntervalTable - vdslPerfIntervalTable
- vdslPerf1DayIntervalTable - vdslPerf1DayIntervalTable
- vdslLineConfProfileTable - vdslLineConfProfileTable
- vdslLineAlarmConfProfileTable - vdslLineAlarmConfProfileTable
The following tables contain objects permitted for ifTypes The following tables contain objects permitted for ifTypes
interleave(124) and (fast): interleave(124) and (fast):
- vdslChanTable - vdslChanTable
- vdslChanPerfDataTable - vdslChanPerfDataTable
- vdslChanPerfIntervalTable - vdslChanPerfIntervalTable
- vdslChanPerf1DayIntervalTable - vdslChanPerf1DayIntervalTable
Figure 2, below, displays the relationship of the tables in the Figure 2, below, displays the relationship of the tables in the
vdslGroup to ifEntry (and each other): vdslGroup to ifEntry (and each other):
skipping to change at page 6, line 32 skipping to change at page 7, line 5
---> vdslchan1DayPerfIntervalEntry 1:(0 to 30) ---> vdslchan1DayPerfIntervalEntry 1:(0 to 30)
Figure 2: Table Relationships Figure 2: Table Relationships
o vdslNotificationGroup : o vdslNotificationGroup :
This group contains definitions of VDSL line notifications. Section This group contains definitions of VDSL line notifications. Section
2.6, below, presents greater detail on the notifications defined 2.6, below, presents greater detail on the notifications defined
within the MIB module. within the MIB module.
2.3.1 Line Topology 2.3.1. Line Topology
A VDSL Line consists of two units - a Vtuc (the central tranceiver A VDSL Line consists of two units - a Vtuc (the central transceiver
unit) and a Vtur (the remote transceiver unit). unit) and a Vtur (the remote transceiver unit).
<-- Network Side Customer Side --> <-- Network Side Customer Side -->
|<////////// VDSL Line ///////////>| |<////////// VDSL Line ///////////>|
+-------+ +-------+ +-------+ +-------+
| | | | | | | |
| Vtuc +------------------+ Vtur | | Vtuc +------------------+ Vtur |
| | | | | | | |
+-------+ +-------+ +-------+ +-------+
Figure 3: General topology for a VDSL Line Figure 3: General topology for a VDSL Line
2.4 Counters, Interval Buckets and Thresholds 2.4. Counters, Interval Buckets and Thresholds
For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los), For Loss of Frame (lof), Loss of Link (lol), Loss of Signal (los),
and Loss of Power (lpr), Errored Seconds (ES), Severely Errored and Loss of Power (lpr), Errored Seconds (ES), Severely Errored
Seconds (SES), and Unavailable Seconds (UAS) there are event Seconds (SES), and Unavailable Seconds (UAS) there are event
counters, current 15-minute, 0 to 96 15-minute history bucket(s), counters, current 15-minute, 0 to 96 15-minute history bucket(s), and
and 0 to 30 1-day history bucket(s) of "interval-counters". Each 0 to 30 1-day history bucket(s) of "interval-counters". Each current
current 15-minute event bucket has an associated threshold 15-minute event bucket has an associated threshold notification.
notification.
Each of these counters uses the textual conventions defined in the Each of these counters uses the textual conventions defined in the
HC-PerfHist-TC-MIB [RFCXXXX]. The HC-PerfHist-TC-MIB defines 64- HC-PerfHist-TC-MIB [RFC3705]. The HC-PerfHist-TC-MIB defines 64-bit
bit versions of the textual conventions found in RFC 3593 [RFC3593]. versions of the textual conventions found in RFC 3593 [RFC3593].
There is no requirement for an agent to ensure a fixed relationship There is no requirement for an agent to ensure a fixed relationship
between the start of a fifteen minute interval and any wall clock; between the start of a fifteen minute interval and any wall clock;
however, some implementations may align the fifteen minute intervals however, some implementations may align the fifteen minute intervals
with quarter hours. Likewise, an implementation may choose to align with quarter hours. Likewise, an implementation may choose to align
one day intervals with the start of a day. one day intervals with the start of a day.
Counters are not reset when a Vtu is reinitialized, only when the Counters are not reset when a Vtu is reinitialized, only when the
agent is reset or reinitialized (or under specific request outside agent is reset or reinitialized (or under specific request outside
the scope of this MIB module). the scope of this MIB module).
2.5 Profiles 2.5. Profiles
As a managed node can handle a large number of Vtus, (e.g., hundreds As a managed node can handle a large number of Vtus, (e.g., hundreds
or perhaps thousands of lines), provisioning every parameter on or perhaps thousands of lines), provisioning every parameter on every
every Vtu may become burdensome. Moreover, most lines are Vtu may become burdensome. Moreover, most lines are provisioned
provisioned identically with the same set of parameters. To identically with the same set of parameters. To simplify the
simplify the provisioning process, this MIB makes use of profiles. provisioning process, this MIB makes use of profiles. A profile is a
A profile is a set of parameters that can be shared by multiple set of parameters that can be shared by multiple lines using the same
lines using the same configuration. configuration.
The following profiles are used in this MIB module: The following profiles are used in this MIB module:
o Line Configuration Profiles - Line configuration profiles o Line Configuration Profiles - Line configuration profiles contain
contain parameters for configuring VDSL lines. They are defined parameters for configuring VDSL lines. They are defined in the
in the vdslLineConfProfileTable. vdslLineConfProfileTable.
o Alarm Configuration Profiles - These profiles contain parameters o Alarm Configuration Profiles - These profiles contain parameters
for configuring alarm thresholds for VDSL transceivers. These for configuring alarm thresholds for VDSL transceivers. These
profiles are defined in the vdslLineAlarmConfProfileTable. profiles are defined in the vdslLineAlarmConfProfileTable.
One or more lines may be configured to share parameters of a single One or more lines may be configured to share parameters of a single
profile by setting their vdslLineConfProfile objects to the value of profile by setting their vdslLineConfProfile objects to the value of
this profile. If a change is made to the profile, all lines that this profile. If a change is made to the profile, all lines that
refer to it will be reconfigured to the changed parameters. Before refer to it will be reconfigured to the changed parameters. Before a
a profile can be deleted or taken out of service it must be first profile can be deleted or taken out of service it must be first
unreferenced from all associated lines. unreferenced from all associated lines.
Implementations MUST provide a default profile with an index value Implementations MUST provide a default profile with an index value of
of 'DEFVAL' for each profile type. The values of the associated 'DEFVAL' for each profile type. The values of the associated
parameters will be vendor specific unless otherwise indicated in parameters will be vendor specific unless otherwise indicated in this
this document. Before a line's profiles have been set, these document. Before a line's profiles have been set, these profiles
profiles will be automatically used by setting vdslLineConfProfile will be automatically used by setting vdslLineConfProfile and
and vdslLineAlarmConfProfile to 'DEFVAL' where appropriate. This vdslLineAlarmConfProfile to 'DEFVAL' where appropriate. This default
default profile name, 'DEFVAL', is considered reserved in the profile name, 'DEFVAL', is considered reserved in the context of
context of profiles defined in this MIB module. profiles defined in this MIB module.
Profiles are created, assigned, and deleted dynamically using the Profiles are created, assigned, and deleted dynamically using the
profile name and profile row status in each of the ten profile profile name and profile row status in each of the ten profile tables
tables (nine line configuration tables and one alarm configuration (nine line configuration tables and one alarm configuration table).
table).
Profile changes MUST take effect immediately. These changes MAY Profile changes MUST take effect immediately. These changes MAY
result in a restart (hard reset or soft restart) of the units on the result in a restart (hard reset or soft restart) of the units on the
line. line.
2.6 Notifications 2.6. Notifications
The ability to generate the SNMP notifications coldStart/WarmStart The ability to generate the SNMP notifications coldStart/WarmStart
(per [RFC3418]) which are per agent (e.g., per Digital Subscriber (per [RFC3418]) which are per agent (e.g., per Digital Subscriber
Line Access Multiplexer, or DSLAM, in such a device), and Line Access Multiplexer, or DSLAM, in such a device), and
linkUp/linkDown (per [RFC2863]) which are per interface (i.e., VDSL linkUp/linkDown (per [RFC2863]) which are per interface (i.e., VDSL
line) is required. line) is required.
The notifications defined in this MIB are for initialization failure The notifications defined in this MIB are for initialization failure
and for the threshold crossings associated with the following and for the threshold crossings associated with the following events:
events: lof, lol, los, lpr, ES, SES, and UAS. Each threshold has lof, lol, los, lpr, ES, SES, and UAS. Each threshold has its own
its own enable/threshold value. When that value is 0, the enable/threshold value. When that value is 0, the notification is
notification is disabled. disabled.
A linkDown notification MAY be generated whenever any of lof, lol, A linkDown notification MAY be generated whenever any of lof, lol,
los, lpr, ES, SES, or UAS threshold crossing event (as defined los, lpr, ES, SES, or UAS threshold crossing event (as defined in
in this MIB module) occurs. The corresponding linkUp notification this MIB module) occurs. The corresponding linkUp notification MAY
MAY be sent when all link failure conditions are cleared. be sent when all link failure conditions are cleared.
The vdslPhysCurrStatus is a bitmask representing all outstanding The vdslPhysCurrStatus is a bitmask representing all outstanding
error conditions associated with a particular VDSL transceiver. error conditions associated with a particular VDSL transceiver. Note
Note that since status of remote transceivers is obtained via the that since status of remote transceivers is obtained via the EOC,
EOC, this information may be unavailable for units that are this information may be unavailable for units that are unreachable
unreachable via the EOC during a line error condition. Therefore, via the EOC during a line error condition. Therefore, not all
not all conditions may always be included in its current status. conditions may always be included in its current status.
Notifications corresponding to the bit fields in this object are Notifications corresponding to the bit fields in this object are
defined. defined.
A threshold notification occurs whenever the corresponding current A threshold notification occurs whenever the corresponding current
15-minute interval error counter becomes equal to, or exceeds the 15-minute interval error counter becomes equal to, or exceeds the
threshold value. One notification may be sent per interval per threshold value. One notification may be sent per interval per
interface. Since the current 15-minute counters are reset to 0 interface. Since the current 15-minute counters are reset to 0 every
every 15 minutes, if the condition persists, the notification may 15 minutes, if the condition persists, the notification may recur as
recur as often as every 15 minutes. For example, to get a often as every 15 minutes. For example, to get a notification
notification whenever a "loss of" event occurs (but at most once whenever a "loss of" event occurs (but at most once every 15
every 15 minutes), set the corresponding threshold to 1. The agent minutes), set the corresponding threshold to 1. The agent will
will generate a notification when the event originally occurs. generate a notification when the event originally occurs.
Note that the Network Management System, or NMS, may receive a Note that the Network Management System, or NMS, may receive a
linkDown notification, as well, if enabled (via linkDown notification, as well, if enabled (via
ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15 ifLinkUpDownTrapEnable [RFC2863]). At the beginning of the next 15
minute interval, the counter is reset. When the first second goes minute interval, the counter is reset. When the first second goes by
by and the event occurs, the current interval bucket will be 1, and the event occurs, the current interval bucket will be 1, which
which equals the threshold and the notification will be sent again. equals the threshold and the notification will be sent again.
2.7 Persistence 2.7. Persistence
All read-write and read-create objects defined in this MIB module All read-write and read-create objects defined in this MIB module
SHOULD be stored persistently. Following is an exhaustive list of SHOULD be stored persistently. Following is an exhaustive list of
these persistent objects: these persistent objects:
vdslLineConfProfile - vdslLineConfProfile
vdslLineAlarmConfProfile - vdslLineAlarmConfProfile
vdslLineConfProfileName - vdslLineConfProfileName
vdslLineConfDownRateMode - vdslLineConfDownRateMode
vdslLineConfUpRateMode - vdslLineConfUpRateMode
vdslLineConfDownMaxPwr - vdslLineConfDownMaxPwr
vdslLineConfUpMaxPwr - vdslLineConfUpMaxPwr
vdslLineConfDownMaxSnrMgn - vdslLineConfDownMaxSnrMgn
vdslLineConfDownMinSnrMgn - vdslLineConfDownMinSnrMgn
vdslLineConfDownTargetSnrMgn - vdslLineConfDownTargetSnrMgn
vdslLineConfUpMaxSnrMgn - vdslLineConfUpMaxSnrMgn
vdslLineConfUpMinSnrMgn - vdslLineConfUpMinSnrMgn
vdslLineConfUpTargetSnrMgn - vdslLineConfUpTargetSnrMgn
vdslLineConfDownFastMaxDataRate - vdslLineConfDownFastMaxDataRate
vdslLineConfDownFastMinDataRate - vdslLineConfDownFastMinDataRate
vdslLineConfDownSlowMaxDataRate - vdslLineConfDownSlowMaxDataRate
vdslLineConfDownSlowMinDataRate - vdslLineConfDownSlowMinDataRate
vdslLineConfUpFastMaxDataRate - vdslLineConfUpFastMaxDataRate
vdslLineConfUpFastMinDataRate - vdslLineConfUpFastMinDataRate
vdslLineConfUpSlowMaxDataRate - vdslLineConfUpSlowMaxDataRate
vdslLineConfUpSlowMinDataRate - vdslLineConfUpSlowMinDataRate
vdslLineConfDownRateRatio - vdslLineConfDownRateRatio
vdslLineConfUpRateRatio - vdslLineConfUpRateRatio
vdslLineConfDownMaxInterDelay - vdslLineConfDownMaxInterDelay
vdslLineConfUpMaxInterDelay - vdslLineConfUpMaxInterDelay
vdslLineConfDownPboControl - vdslLineConfDownPboControl
vdslLineConfUpPboControl - vdslLineConfUpPboControl
vdslLineConfDownPboLevel - vdslLineConfDownPboLevel
vdslLineConfUpPboLevel - vdslLineConfUpPboLevel
vdslLineConfDeploymentScenario - vdslLineConfDeploymentScenario
vdslLineConfAdslPresence - vdslLineConfAdslPresence
vdslLineConfApplicableStandard - vdslLineConfApplicableStandard
vdslLineConfBandPlan - vdslLineConfBandPlan
vdslLineConfBandPlanFx - vdslLineConfBandPlanFx
vdslLineConfBandOptUsage - vdslLineConfBandOptUsage
vdslLineConfUpPsdTemplate - vdslLineConfUpPsdTemplate
vdslLineConfDownPsdTemplate - vdslLineConfDownPsdTemplate
vdslLineConfHamBandMask - vdslLineConfHamBandMask
vdslLineConfCustomNotch1Start - vdslLineConfCustomNotch1Start
vdslLineConfCustomNotch1Stop - vdslLineConfCustomNotch1Stop
vdslLineConfCustomNotch2Start - vdslLineConfCustomNotch2Start
vdslLineConfCustomNotch2Stop - vdslLineConfCustomNotch2Stop
vdslLineConfDownTargetSlowBurst - vdslLineConfDownTargetSlowBurst
vdslLineConfUpTargetSlowBurst - vdslLineConfUpTargetSlowBurst
vdslLineConfDownMaxFastFec - vdslLineConfDownMaxFastFec
vdslLineConfUpMaxFastFec - vdslLineConfUpMaxFastFec
vdslLineConfLineType - vdslLineConfLineType
vdslLineConfProfRowStatus - vdslLineConfProfRowStatus
vdslLineAlarmConfProfileName - vdslLineAlarmConfProfileName
vdslLineAlarmConfThresh15MinLofs - vdslLineAlarmConfThresh15MinLofs
vdslLineAlarmConfThresh15MinLoss - vdslLineAlarmConfThresh15MinLoss
vdslLineAlarmConfThresh15MinLprs - vdslLineAlarmConfThresh15MinLprs
vdslLineAlarmConfThresh15MinLols - vdslLineAlarmConfThresh15MinLols
vdslLineAlarmConfThresh15MinESs - vdslLineAlarmConfThresh15MinESs
vdslLineAlarmConfThresh15MinSESs - vdslLineAlarmConfThresh15MinSESs
vdslLineAlarmConfThresh15MinUASs - vdslLineAlarmConfThresh15MinUASs
vdslLineAlarmConfInitFailure - vdslLineAlarmConfInitFailure
vdslLineAlarmConfProfRowStatus - vdslLineAlarmConfProfRowStatus
It should also be noted that interface indices in this MIB are It should also be noted that interface indices in this MIB are
maintained persistently. VACM data relating to these SHOULD be maintained persistently. VACM data relating to these SHOULD be
stored persistently as well [RFC3415]. stored persistently as well [RFC3415].
3. Conformance and Compliance 3. Conformance and Compliance
For VDSL lines, the following groups are mandatory: For VDSL lines, the following groups are mandatory:
- vdslGroup - vdslGroup
skipping to change at page 10, line 41 skipping to change at page 11, line 44
VDSL-LINE-MIB DEFINITIONS ::= BEGIN VDSL-LINE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Gauge32, Gauge32,
Integer32, Integer32,
Unsigned32, Unsigned32,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
transmission FROM SNMPv2-SMI transmission FROM SNMPv2-SMI -- [RFC2578]
ZeroBasedCounter64 FROM HCNUM-TC ZeroBasedCounter64 FROM HCNUM-TC -- [RFC2856]
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
RowStatus, RowStatus,
TruthValue FROM SNMPv2-TC TruthValue FROM SNMPv2-TC -- [RFC2579]
HCPerfValidIntervals, HCPerfValidIntervals,
HCPerfInvalidIntervals, HCPerfInvalidIntervals,
HCPerfTimeElapsed, HCPerfTimeElapsed,
HCPerfIntervalThreshold, HCPerfIntervalThreshold,
HCPerfCurrentCount, HCPerfCurrentCount,
HCPerfIntervalCount FROM HC-PerfHist-TC-MIB HCPerfIntervalCount FROM HC-PerfHist-TC-MIB -- [RFC3705]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580]
ifIndex FROM IF-MIB ifIndex FROM IF-MIB -- [RFC2863]
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB; -- [RFC3411]
vdslMIB MODULE-IDENTITY vdslMIB MODULE-IDENTITY
LAST-UPDATED "200309240000Z" -- September 24, 2003 LAST-UPDATED "200402190000Z" -- February 19, 2004
ORGANIZATION "ADSLMIB Working Group" ORGANIZATION "ADSLMIB Working Group"
CONTACT-INFO "WG-email: adslmib@ietf.org CONTACT-INFO "WG-email: adslmib@ietf.org
Info: https://www1.ietf.org/mailman/listinfo/adslmib Info: https://www1.ietf.org/mailman/listinfo/adslmib
Chair: Mike Sneed Chair: Mike Sneed
Sand Channel Systems Sand Channel Systems
Postal: P.O. Box 37324 Postal: P.O. Box 37324
Raleigh, NC 27627-7324 Raleigh, NC 27627-7324
USA USA
Email: sneedmike@hotmail.com Email: sneedmike@hotmail.com
skipping to change at page 11, line 28 skipping to change at page 12, line 37
Co-editor: Bob Ray Co-editor: Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
Postal: 330-A Wynn Drive Postal: 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Email: rray@pesa.com Email: rray@pesa.com
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Co-editor: Rajesh Abbi Co-editor: Rajesh Abbi
Alcatel USA Alcatel USA
Postal: 2912 Wake Forest Road Postal: 2301 Sugar Bush Road
Raleigh, NC 27609-7860 Raleigh, NC 27612-3339
USA USA
Email: Rajesh.Abbi@alcatel.com Email: Rajesh.Abbi@alcatel.com
Phone: +1 919 850 6194 Phone: +1 919 850 6194
" "
DESCRIPTION DESCRIPTION
"The MIB module defining objects for the management of a pair "The MIB module defining objects for the management of a pair
of VDSL transceivers at each end of the VDSL line. Each such of VDSL transceivers at each end of the VDSL line. Each such
line has an entry in an ifTable which may include multiple line has an entry in an ifTable which may include multiple
transceiver lines. An agent may reside at either end of the transceiver lines. An agent may reside at either end of the
VDSL line. However, the MIB is designed to require no VDSL line. However, the MIB is designed to require no
skipping to change at page 12, line 26 skipping to change at page 13, line 39
xxxs -- Sum of Seconds in which xxx has occured xxxs -- Sum of Seconds in which xxx has occured
(e.g., xxx = Lof, Los, Lpr, Lol) (e.g., xxx = Lof, Los, Lpr, Lol)
Max -- Maximum Max -- Maximum
Mgn -- Margin Mgn -- Margin
Min -- Minimum Min -- Minimum
Psd -- Power Spectral Density Psd -- Power Spectral Density
Snr -- Signal to Noise Ratio Snr -- Signal to Noise Ratio
Tx -- Transmit Tx -- Transmit
Blks -- Blocks Blks -- Blocks
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX: see the RFC of this MIB module is part of RFC 3728: see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200309240000Z" -- September 24, 2003 REVISION "200402190000Z" -- February 19, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC 3728."
::= { transmission YYYY } -- To be assigned by IANA ::= { transmission 97 }
vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 } vdslLineMib OBJECT IDENTIFIER ::= { vdslMIB 1 }
vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 } vdslMibObjects OBJECT IDENTIFIER ::= { vdslLineMib 1 }
-- --
-- textual conventions used in this MIB -- textual conventions used in this MIB
-- --
VdslLineCodingType ::= TEXTUAL-CONVENTION VdslLineCodingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax for the VDSL Line "This data type is used as the syntax for the VDSL Line
Code. Attributes with this syntax identify the line coding Code. Attributes with this syntax identify the line coding
used. Specified as an INTEGER, the three values are: used. Specified as an INTEGER, the three values are:
other(1) -- none of the following other(1) -- none of the following
mcm(2) -- Multiple Carrier Modulation mcm(2) -- Multiple Carrier Modulation
scm(3) -- Single Carrier Modulation" scm(3) -- Single Carrier Modulation"
skipping to change at page 13, line 13 skipping to change at page 14, line 25
{ {
other(1), other(1),
mcm(2), mcm(2),
scm(3) scm(3)
} }
VdslLineEntity ::= TEXTUAL-CONVENTION VdslLineEntity ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a transceiver as being either Vtuc or Vtur. "Identifies a transceiver as being either Vtuc or Vtur.
A VDSL line consists of two transcievers, a Vtuc and a A VDSL line consists of two transceivers, a Vtuc and a
Vtur. Attributes with this syntax reference the two sides Vtur. Attributes with this syntax reference the two sides
of a line. Specified as an INTEGER, the two values are: of a line. Specified as an INTEGER, the two values are:
vtuc(1) -- central site transceiver vtuc(1) -- central site transceiver
vtur(2) -- remote site transceiver" vtur(2) -- remote site transceiver"
SYNTAX INTEGER SYNTAX INTEGER
{ {
vtuc(1), vtuc(1),
vtur(2) vtur(2)
} }
skipping to change at page 23, line 51 skipping to change at page 26, line 23
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Unavailable Seconds since the unit was last "Count of Unavailable Seconds since the unit was last
reset." reset."
::= { vdslPerfDataEntry 9 } ::= { vdslPerfDataEntry 9 }
vdslPerfDataInits OBJECT-TYPE vdslPerfDataInits OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "occurences" UNITS "occurrences"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts since the unit "Count of the line initialization attempts since the unit
was last reset. This count includes both successful and was last reset. This count includes both successful and
failed attempts." failed attempts."
REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" REFERENCE "T1E1.4/2000-009R3, Part 1, common spec"
::= { vdslPerfDataEntry 10 } ::= { vdslPerfDataEntry 10 }
vdslPerfDataCurr15MinTimeElapsed OBJECT-TYPE vdslPerfDataCurr15MinTimeElapsed OBJECT-TYPE
skipping to change at page 25, line 39 skipping to change at page 28, line 20
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of Unavailable Seconds during this interval." "Count of Unavailable Seconds during this interval."
::= { vdslPerfDataEntry 18 } ::= { vdslPerfDataEntry 18 }
vdslPerfDataCurr15MinInits OBJECT-TYPE vdslPerfDataCurr15MinInits OBJECT-TYPE
SYNTAX HCPerfCurrentCount SYNTAX HCPerfCurrentCount
UNITS "occurences" UNITS "occurrences"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Count of the line initialization attempts during this "Count of the line initialization attempts during this
interval. This count includes both successful and interval. This count includes both successful and
failed attempts." failed attempts."
REFERENCE "T1E1.4/2000-009R3, Part 1, common spec" REFERENCE "T1E1.4/2000-009R3, Part 1, common spec"
::= { vdslPerfDataEntry 19 } ::= { vdslPerfDataEntry 19 }
vdslPerfData1DayValidIntervals OBJECT-TYPE vdslPerfData1DayValidIntervals OBJECT-TYPE
skipping to change at page 53, line 18 skipping to change at page 58, line 40
fastOrInterleaved(4), -- either fast or interleaved channel fastOrInterleaved(4), -- either fast or interleaved channel
-- exist, but only one at a time -- exist, but only one at a time
fastAndInterleaved(5) -- both fast and interleaved channels fastAndInterleaved(5) -- both fast and interleaved channels
-- exist -- exist
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This parameter provisions the VDSL physical entity at "This parameter provisions the VDSL physical entity at
start-up by defining whether and how the line will be start-up by defining whether and how the line will be
channelized, i.e. which channel type(s) are supported. channelized, i.e., which channel type(s) are supported.
If the line is to be channelized, the value will be other If the line is to be channelized, the value will be other
than noChannel(1). than noChannel(1).
This configuration can be activated only during start-up. This configuration can be activated only during start-up.
Afterwards, the value of vdslLineType coincides with the Afterwards, the value of vdslLineType coincides with the
value of vdslLineConfLineType. Depending on this value, value of vdslLineConfLineType. Depending on this value,
the corresponding entries in the ifTable for the the corresponding entries in the ifTable for the
interleaved and the fast channels are enabled or disabled interleaved and the fast channels are enabled or disabled
according to the value of their ifOperStatus. according to the value of their ifOperStatus.
skipping to change at page 54, line 9 skipping to change at page 59, line 36
A profile activated by setting this object to 'active'. A profile activated by setting this object to 'active'.
When 'active' is set, the system will validate the profile. When 'active' is set, the system will validate the profile.
Before a profile can be deleted or taken out of service Before a profile can be deleted or taken out of service
(by setting this object to 'destroy' or 'outOfService'), (by setting this object to 'destroy' or 'outOfService'),
it must be first unreferenced from all associated lines. it must be first unreferenced from all associated lines.
An 'active' profile may be modified at any time. Note An 'active' profile may be modified at any time. Note
that some changes may require that any referenced lines be that some changes may require that any referenced lines be
restarted (e.g. vdslLineConfLineType)." restarted (e.g., vdslLineConfLineType)."
::= { vdslLineConfProfileEntry 46 } ::= { vdslLineConfProfileEntry 46 }
-- --
-- Alarm configuration profile table -- Alarm configuration profile table
-- --
vdslLineAlarmConfProfileTable OBJECT-TYPE vdslLineAlarmConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry SYNTAX SEQUENCE OF VdslLineAlarmConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 55, line 14 skipping to change at page 60, line 46
vdslLineAlarmConfInitFailure TruthValue, vdslLineAlarmConfInitFailure TruthValue,
vdslLineAlarmConfProfRowStatus RowStatus vdslLineAlarmConfProfRowStatus RowStatus
} }
vdslLineAlarmConfProfileName OBJECT-TYPE vdslLineAlarmConfProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32)) SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name for this profile as specified by an "The name for this profile as specified by an
adminstrator." administrator."
::= { vdslLineAlarmConfProfileEntry 1 } ::= { vdslLineAlarmConfProfileEntry 1 }
vdslLineAlarmConfThresh15MinLofs OBJECT-TYPE vdslLineAlarmConfThresh15MinLofs OBJECT-TYPE
SYNTAX HCPerfIntervalThreshold SYNTAX HCPerfIntervalThreshold
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the threshold for the number of "This object configures the threshold for the number of
loss of frame seconds (lofs) within any given 15-minute loss of frame seconds (lofs) within any given 15-minute
skipping to change at page 64, line 12 skipping to change at page 71, line 5
vdslInitFailureNotification vdslInitFailureNotification
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant "This group supports notifications of significant
conditions associated with VDSL Lines." conditions associated with VDSL Lines."
::= { vdslGroups 2 } ::= { vdslGroups 2 }
END END
5. Intellectual Property Notice 5. Security Considerations
The IETF takes no position regarding the validity or scope of any There are a number of management objects defined in this MIB module
intellectual property or other rights that might be claimed to with a MAX-ACCESS clause of read-write and/or read-create. Such
pertain to the implementation or use of the technology described in objects may be considered sensitive or vulnerable in some network
this document or the extent to which any license under such rights environments. The support for SET operations in a non-secure
might or might not be available; neither does it represent that it environment without proper protection can have a negative effect on
has made any effort to identify any such rights. Information on the network operations.
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any Some of the readable objects in this MIB module (i.e., objects with a
copyrights, patents or patent applications, or other proprietary MAX-ACCESS other than not-accessible) may be considered sensitive or
rights which may cover technology that may be required to practice vulnerable in some network environments. It is thus important to
this standard. Please address the information to the IETF Executive control even GET and/or NOTIFY access to these objects and possibly
Director. to even encrypt the values of these objects when sending them over
the network via SNMP.
6. Normative References VDSL layer connectivity from the Vtur will permit the subscriber to
manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could generate
sufficient notifications to potentially overwhelm either the
management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other end-
users in either a positive or negative manner. For this reason, the
following tables should be considered to contain sensitive
information:
- vdslLineTable
- vdslLineConfProfileTable
- vdslLineAlarmConfProfileTable
Individual line utilization information, available via the
performance tables, may be considered sensitive. For example, if an
end-user has a far lower line utilization during certain periods of
the day, it may indicate an empty office or residence. For these
reasons, the following tables should be considered to contain
sensitive information:
- vdslPerfDataTable
- vdslPerfIntervalTable
- vdslPerf1DayIntervalTable
Further, notifications generated by agents implementing this MIB will
contain threshold and performance information.
It is thus important to control even GET access to the objects within
these tables and possibly to even encrypt the values of these objects
when sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the 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 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. References
6.1. Normative References
[DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management", [DSLFTR057] DSL Forum TR-057, "VDSL Network Element Management",
February 2003. February 2003.
[ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing [ETSI2701] ETSI TS 101 270-1 V1.2.1 "Transmission and Multiplexing
(TM); Access transmission systems on metallic access (TM); Access transmission systems on metallic access
cables; Very high speed Digital Subscriber Line (VDSL); cables; Very high speed Digital Subscriber Line (VDSL);
Part 1: Functional requirements", October 1999. Part 1: Functional requirements", October 1999.
[ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing [ETSI2702] ETSI TS 101 270-2 V1.1.1 "Transmission and Multiplexing
skipping to change at page 65, line 5 skipping to change at page 73, line 8
[ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line [ITU9931] ITU-T G.993.1 "Very-high-speed digital subscriber line
foundation", November 2001. foundation", November 2001.
[ITU9971] ITU-T G.997.1 "Physical layer management for Digital [ITU9971] ITU-T G.997.1 "Physical layer management for Digital
Subscriber Line (DSL) Transceivers", July 1999. Subscriber Line (DSL) Transceivers", July 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M. and S. Waldbusser, "Structure of Rose, M. and S. Waldbusser, "Structure of Management
Management Information Version 2 (SMIv2)", STD 58, RFC Information Version 2 (SMIv2)", STD 58, RFC 2578, April
2578, April 1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M. and S. Waldbusser, "Textual Conventions Rose, M. and S. Waldbusser, "Textual Conventions for
for SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
J., Rose, M. and S. Waldbusser, "Conformance Rose, M. and S. Waldbusser, "Conformance Statements for
Statements for SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2856] Bierman, A., McCloghrie, K. and R. Presuhn, "Textual
Group MIB", RFC 2863, June 2000. Conventions for Additional High Capacity Data Types", RFC
2856, June 2000.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002. 3418, December 2002.
[RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals", RFC Performance History Based on 15 Minute Intervals", RFC
3593, September 2003. 3593, September 2003.
[RFCXXXX] Ray, B. and R. Abbi, "High Capacity Textual Conventions [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions
for MIB Modules Using Performance History Based on for MIB Modules Using Performance History Based on 15
15 Minute Intervals", RFC XXXX, YYYY 2003. Minute Intervals", RFC 3705, February 2004.
[T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital [T1E1311] ANSI T1E1.4/2001-311, "Very-high-bit-rate Digital
Subscriber Line (VDSL) Metallic Interface, Part 1: Subscriber Line (VDSL) Metallic Interface, Part 1:
Functional Requirements and Common Specification", Functional Requirements and Common Specification",
February 2001. February 2001.
[T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part [T1E1011] ANSI T1E1.4/2001-011R3, "VDSL Metallic Interface, Part 2:
2: Technical Specification for a Single-Carrier Technical Specification for a Single-Carrier Modulation
Modulation (SCM) Transceiver", November 2001. (SCM) Transceiver", November 2001.
[T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part [T1E1013] ANSI T1E1.4/2001-013R4, "VDSL Metallic Interface, Part 3:
3: Technical Specification for a Multi-Carrier Technical Specification for a Multi-Carrier Modulation
Modulation (MCM) Transceiver", November 2000. (MCM) Transceiver", November 2000.
7. Informative References 6.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 3415, December 2002. Management Protocol (SNMP)", STD 62, RFC 3415, December
2002.
8. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
Some of the readable objects in this MIB module (i.e., objects with
a MAX-ACCESS other than not-accessible) may be considered sensitive
or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP.
VDSL layer connectivity from the Vtur will permit the subscriber
to manipulate both the VDSL link directly and the VDSL embedded
operations channel (EOC) for their own loop. For example, unchecked
or unfiltered fluctuations initiated by the subscriber could
generate sufficient notifications to potentially overwhelm either
the management interface to the network or the element manager.
Additionally, allowing write access to configuration data may allow
an end-user to increase their service levels or affect other
end-users in either a positive or negative manner. For this reason,
the following tables should be considered to contain sensitive
information:
vdslLineTable
vdslLineConfProfileTable
vdslLineAlarmConfProfileTable
Individual line utilization information, available via the
performance tables, may be considered sensitive. For example,
if an end-user has a far lower line utilization during certain
periods of the day, it may indicate an empty office or residence.
For these reasons, the following tables should be considered to
contain sensitive information:
- vdslPerfDataTable
- vdslPerfIntervalTable
- vdslPerf1DayIntervalTable
Further, notifications generated by agents implementing this MIB
will contain threshold and performance information.
It is thus important to control even GET access to the objects
within these tables and possibly to even encrypt the values of
these objects when sending them over the network via SNMP. Not
all versions of SNMP provide features for such a secure
environment.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the 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 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.
9. Acknowledgements 7. Acknowledgements
Greg Bathrick (Nokia) Greg Bathrick (Texas Instruments)
Umberto Bonollo (NEC) Umberto Bonollo (NEC)
Andrew Cheers (NEC) Andrew Cheers (NEC)
Felix Flemisch (Siemens) Felix Flemisch (Siemens)
David Horton (CiTR) David Horton (CiTR)
Travis Levin (Paradyne) Travis Levin (Paradyne)
Moti Morgenstern (Inovia) Moti Morgenstern (Inovia)
Randy Presuhn (BMC) Randy Presuhn (BMC)
Say Sabit (NLC) Say Sabit (NLC)
Bert Wijnen (Lucent) Bert Wijnen (Lucent)
10. Authors' Addresses 8. Authors' Addresses
Bob Ray Bob Ray
PESA Switching Systems, Inc. PESA Switching Systems, Inc.
330-A Wynn Drive 330-A Wynn Drive
Huntsville, AL 35805 Huntsville, AL 35805
USA USA
Phone: +1 256 726 9200 ext. 142 Phone: +1 256 726 9200 ext. 142
Fax: +1 256 726 9271 Fax: +1 256 726 9271
Email: rray@pesa.com EMail: rray@pesa.com
Rajesh Abbi Rajesh Abbi
Alcatel USA Alcatel USA
2912 Wake Forest Road 2301 Sugar Bush Road
Raleigh, NC 27609-7860 Raleigh, NC 27612-3339
USA USA
Phone: +1 919 850 6194 Phone: +1 919 850 6194
Email: Rajesh.Abbi@alcatel.com EMail: Rajesh.Abbi@alcatel.com
11. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
This document and translations of it may be copied and furnished to to the rights, licenses and restrictions contained in BCP 78 and
others, and derivative works that comment on or otherwise explain it except as set forth therein, the authors retain all their rights.
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assigns. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY 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.
This document and the information contained herein is provided on an Intellectual Property
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING The IETF takes no position regarding the validity or scope of any
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Intellectual Property Rights or other rights that might be claimed to
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF pertain to the implementation or use of the technology described in
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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