draft-ietf-hubmib-efm-cu-mib-04.txt   draft-ietf-hubmib-efm-cu-mib-05.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: April 27, 2006 October 24, 2005 Expires: December 19, 2006 June 17, 2006
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-04.txt draft-ietf-hubmib-efm-cu-mib-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 27, 2006. This Internet-Draft will expire on December 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
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 TCP/IP based internets. use with network management protocols in TCP/IP based internets.
This document proposes an extension to the Ethernet-like Interfaces This document proposes an extension to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing an MIB and MAU MIB modules with a set of objects for managing an
Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and
2BASE-TL, defined in IEEE Std 802.3ah-2004. 2BASE-TL, defined in IEEE Std 802.3ah-2004.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8 3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8
3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9
3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10
3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11
4.3. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 4.3. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 75
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 77
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.1. Normative References . . . . . . . . . . . . . . . . . . . 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 77
9.2. Informative References . . . . . . . . . . . . . . . . . . 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 78
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 80
Intellectual Property and Copyright Statements . . . . . . . . . . 73 Intellectual Property and Copyright Statements . . . . . . . . . . 81
1. Introduction 1. Introduction
New Ethernet-like interfaces have been defined in the Institute of New Ethernet-like interfaces have been defined in the Institute of
Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
[802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular [802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a
part of the base IEEE Standard 802.3-2005 [802.3]. In particular
2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
voice-grade copper pairs, have been specified for the long and short voice-grade copper pairs, have been specified for the long and short
reach respectively. These interfaces, collectively called EFMCu, are reach respectively. These interfaces, collectively called EFMCu, are
based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications
and support variable rates and optional Physical Medium Entity (PME) and support variable rates and optional Physical Medium Entity (PME)
aggregation (a.k.a. multi-pair bonding). aggregation (a.k.a. multi-pair bonding).
2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long
single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using
5dB target noise margin). 5dB target noise margin).
skipping to change at page 4, line 30 skipping to change at page 4, line 31
[RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK- [RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK-
MIB [RFC2864]. MIB [RFC2864].
3.1.1. Layering Model 3.1.1. Layering Model
An EFMCu interface can aggregate up to 32 Physical Medium Entity An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
A generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, connected to a MAC via Medium Independent Interface (PCS) ports, each connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of (MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details. 61.1 of [802.3ah] for more details.
Each PME in the aggregated EFMCu port is represented in the Interface Each PME in the aggregated EFMCu port is represented in the Interface
table (ifTable) as a separate port with ifType of shdsl(169) for table (ifTable) as a separate port with ifType of shdsl(169) for
2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in
[IANAifType-MIB]. [IANAifType-MIB].
ifSpeed for each PME SHALL return the actual data bitrate of the ifSpeed for each PME SHALL return the actual data bitrate of the
active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero
value SHALL be returned when PME is initializing or down. value SHALL be returned when PME is initializing or down.
The ifSpeed of the PCS is the sum of the current operating data rates The ifSpeed of the PCS is the sum of the current operating data rates
of all PMEs in the aggregation group, without the 64/65B of all PMEs in the aggregation group, without the 64/65B
encapsulation overhead and PAF overhead, but acounting for the Inter- encapsulation overhead and PAF overhead, but accounting for the
Frame Gaps (IFG). Inter-Frame Gaps (IFG).
When using the stated definition of ifSpeed for the PCS, there would When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are be no frame loss in the following configuration (the test-sets are
configured to generate 100% of back to back traffic, i.e. minimal configured to generate 100% of back to back traffic, i.e. minimal
IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM
interfaces are obviously aggregated): interfaces are aggregated, to achieve the shown speed):
[testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset]
ifSpeed= 10Mbps 10Mbps 10Mbps ifSpeed= 10Mbps 10Mbps 10Mbps
[testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset]
ifSpeed= 100Mbps 100Mbps 100Mbps ifSpeed= 100Mbps 100Mbps 100Mbps
Figure 1: Example configuration with no frame loss Figure 1: Example configuration with no frame loss
The following figure shows the layering diagram and corresponding use The following figure shows the layering diagram and corresponding use
skipping to change at page 6, line 35 skipping to change at page 6, line 35
This MIB module allows a Network Management application to query PAF This MIB module allows a Network Management application to query PAF
capability and enable/disable it if supported. Note that enabling capability and enable/disable it if supported. Note that enabling
PAF effectively turns on fragmentation and re-assembly, even on a PAF effectively turns on fragmentation and re-assembly, even on a
single-PME port. single-PME port.
3.1.3. Discovery Operation 3.1.3. Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be respective aggregation groups (PCS). This information can then be
used to detect copper missconnections or for an automatic assignment used to detect copper misconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of fixed pre- of the local PMEs into aggregation groups instead of fixed pre-
configuration. configuration.
This MIB module allows a Network Management application to control This MIB module allows a Network Management application to control
EFM Discovery mechanism and query its results. Note that the EFM Discovery mechanism and query its results. Note that the
Discovery mechanism can work only if PAF is supported and enabled. Discovery mechanism can work only if PAF is supported and enabled.
Two tables are used by Discovery mechanism: ifStackTable and Two tables are used by Discovery mechanism: ifStackTable and
ifAvailableStackTable defined. The following pseudo-code defines an ifAvailableStackTable defined. The following pseudo-code defines an
example of Discovery and automatic PME assignment for a generic PAF example of Discovery and automatic PME assignment for a generic PAF
skipping to change at page 7, line 51 skipping to change at page 7, line 51
contained in the Clause 45 PME_Available_register (see [802.3ah] contained in the Clause 45 PME_Available_register (see [802.3ah]
61.1.5.3 and 45.2.3.20). 61.1.5.3 and 45.2.3.20).
Adding a PME to the ifStackTable row for a specific PCS, involves Adding a PME to the ifStackTable row for a specific PCS, involves
actual connection of the PME to the PCS, which can be done by actual connection of the PME to the PCS, which can be done by
modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3
and 45.2.3.21). and 45.2.3.21).
Note that PCS port does not have to be operationally 'down' for the Note that PCS port does not have to be operationally 'down' for the
connection to succeed. In fact, a dynamic PME addition (and removal) connection to succeed. In fact, a dynamic PME addition (and removal)
MAY be implemented whith an available PME being initialized first (by MAY be implemented with an available PME being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally setting its ifAdminStatus to 'up') and then added to an operationally
'up' PCS port, by modifying a respective ifStackTable entry. 'up' PCS port, by modifying a respective ifStackTable entry.
It is RECOMMENDED that a removal of the last operationally 'up' PME It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the from an operationally 'up' PCS would be rejected by the
implementation, as this action would completely drop the link. implementation, as this action would completely drop the link.
3.1.4. EFMCu ports initialization 3.1.4. EFMCu ports initialization
EFMCu ports being built on top of xDSL technology, require a lengthy EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise pair. Sometimes, when the copper line is too long or the noise on
environment on the line is too high, that 'training' process may fail the line is too high, that 'training' process may fail to achieve a
to achieve a specific target rate with required characteristics. specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB, controls the desired state
of a PCS and a PME port. Setting this object to 'up' instructs a of a PCS with all the PMEs connected to it or of an individual PME
particular PCS or PME to start initialization process, which may take port. Setting this object to 'up' instructs a particular PCS or PME
tens of seconds for EFMCu ports, especially if PAF is involved. The to start initialization process, which may take tens of seconds for
ifOperStatus object shows the operational state of an interface EFMCu ports, especially if PAF is involved. The ifOperStatus object
(extended by efmCuPmeOperStatus defined in this MIB module for PME shows the operational state of an interface (extended by
interfaces). ifMauMediaAvailable object from MAU-MIB for PCS and
efmCuPmeOperStatus defined in this MIB module for PME interfaces).
A disconnected PME may be initialized by changing the ifAdminState A disconnected PME may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS
initializes all PMEs connected to that particular PCS. Note that in initializes all PMEs connected to that particular PCS. Note that in
case of PAF some interfaces may fail to initialize while others case of PAF some interfaces may fail to initialize while others
succeed. The PCS is considered operationally 'up' if at least one succeed. The PCS is considered operationally 'up' if at least one
PME aggregated by its PAF is operationally 'up'. When all PMEs PME aggregated by its PAF is operationally 'up'. When all PMEs
connected to the PCS are 'down' the PCS SHALL be considered connected to the PCS are 'down' the PCS SHALL be considered
operationally 'lowerLayerDown'. The PCS SHALL be considered operationally 'lowerLayerDown'. The PCS SHALL be considered
operationally 'notPresent' if it is not connected to any PME. The operationally 'notPresent' if it is not connected to any PME. The
skipping to change at page 9, line 20 skipping to change at page 9, line 22
| ifIndex | Interface index. Note that each PME and each PCS | | ifIndex | Interface index. Note that each PME and each PCS |
| | in the EFMCu PHY MUST have a unique index, as | | | in the EFMCu PHY MUST have a unique index, as |
| | there some PCS and PME specific attributes | | | there some PCS and PME specific attributes |
| | accessible only on the PCS or PME level. | | | accessible only on the PCS or PME level. |
| ifType | ethernetCsmacd(6) for PCS, shdsl(169) for | | ifType | ethernetCsmacd(6) for PCS, shdsl(169) for |
| | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME | | | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME |
| ifSpeed | Operating data rate for the PME. For the PCS it | | ifSpeed | Operating data rate for the PME. For the PCS it |
| | is the sum of the current operating data rates of | | | is the sum of the current operating data rates of |
| | all PMEs in the aggregation group, without the | | | all PMEs in the aggregation group, without the |
| | 64/65B encapsulation overhead and PAF overhead, | | | 64/65B encapsulation overhead and PAF overhead, |
| | but acounting for the Inter-Frame Gaps (IFG) | | | but accounting for the Inter-Frame Gaps (IFG) |
| ifAdminStatus | Setting this object to 'up' instructs a | | ifAdminStatus | Setting this object to 'up' instructs a |
| | particular PCS (with all PMEs connected to it) or | | | particular PCS (with all PMEs connected to it) or |
| | PME to start initialization process | | | PME to start initialization process |
| ifOperStatus | efmCuPmeOperStatus supplements the 'down' value | | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | of ifOperStatus for PMEs. | | | of ifOperStatus for PMEs. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1 Table 1
3.2. Relation to SHDSL MIB module 3.2. Relation to SHDSL MIB module
G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all
that not all attributes of G.SHDSL modems reflected in HDSL2-SHDSL- attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have
LINE-MIB have adequate management objects (Clause 30 attributes and adequate management objects (Clause 30 attributes and Clause 45
Clause 45 registers) in the EFM standard. registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency (e.g. prefixing the 2BASE-TL PME related objects and name consistency (e.g. prefixing the 2BASE-TL PME related objects
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
objects in this MIB module. objects in this MIB module.
However, if some functionality, not available in this MIB module, is However, if some functionality, not available in this MIB module, is
required and supported by the PME, e.g. performance monitoring, required and supported by the PME, e.g. performance monitoring,
relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and applied for
PMEs of 2BASE-TL subtype. PMEs of 2BASE-TL subtype.
3.3. Relation to VDSL MIB module 3.3. Relation to VDSL MIB module
VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port,
are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all
attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have
adequate management objects (Clause 30 attributes and Clause 45 adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard. registers) in the EFM standard.
skipping to change at page 10, line 30 skipping to change at page 10, line 30
required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB
groups MAY be included and applied for PMEs of 10PASS-TS subtype. groups MAY be included and applied for PMEs of 10PASS-TS subtype.
3.4. Relation to Ethernet-Like and MAU MIB modules 3.4. Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf- The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf-
hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
Additionally IANA-MAU-MIB defines two new values of
ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable
- availableReduced and ready, specifically for the EFMCu ports. Due
to the PME aggregation, the EFMCu interpretation of some possible
ifMauMediaAvailable values differs from other MAUs as follows:
o unknown - the EFMCu interface (PCS with connected PMEs) is
initializing
o ready - the interface is down, at least one PME in the aggregation
group (all PMEs connected to the PCS) is ready for handshake
o available - the interface is up, all PMEs in the aggregation group
are up
o notAvailable - the interface is down, all PMEs in the aggregation
group are down, no handshake tones are detected by any PME
o availableReduced - the interface is up, a link fault is detected
at the receive direction by one or more PMEs in the aggregation
group, but at least one PME is up
o pmdLinkFault - a link fault is detected at the receive direction
by all PMEs in the aggregation group
As an EtherLike interface every EFMCu port (an ifEntry representing a As an EtherLike interface every EFMCu port (an ifEntry representing a
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType
of ethernetCsmacd(6). While most of the MAU characteristics are not of ethernetCsmacd(6). While most of the MAU characteristics are not
applicable to the EFMCu ports (no auto-negotiation, media available, applicable to the EFMCu ports (no auto-negotiation, false carriers or
false carriers or jabber), they SHALL return an appropriate ifMauType jabber), they SHALL return an appropriate ifMauType
(dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the
management software to look in the EFM-CU-MIB for the desired management software to look in the EFM-CU-MIB for the desired
information. For example the information on the particular EFMCu information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB module. efmCuOperSubType, defined in this MIB module.
Since EFMCu PMEs are not EtherLike interfaces, they cannot be Since EFMCu PMEs are not EtherLike interfaces, they cannot be
instantiated as MAU interface objects. instantiated as MAU interface objects.
4. MIB Structure 4. MIB Structure
skipping to change at page 12, line 14 skipping to change at page 12, line 39
efmCuPmeAdminProfile object, which overwrites profile set by efmCuPmeAdminProfile object, which overwrites profile set by
efmCuAdminProfile. efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically, object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed) to reflect achieved parameters in adaptive (not fixed)
initialization. initialization.
4.3. Mapping of IEEE 802.3ah Managed Objects 4.3. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the IF- defined in this document and in associated MIB modules, i.e., the IF-
MIB [RFC2863]. MIB [RFC2863].
Note that majority of the objects defined in this MIB module do not Note that majority of the objects defined in this MIB module do not
have direct counterparts in Clause 30 and instead refer to Clause 45 have direct counterparts in Clause 30 and instead refer to Clause 45
registers. registers.
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oMAU - Basic Package | |
| (Mandatory) | |
| aMAUType | ifMauType (MAU-MIB) |
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
| aMediaAvailable | ifMediaAvailable (MAU-MIB) |
| oPAF - Basic Package | | | oPAF - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
| aPAFID | ifIndex (IF-MIB) | | aPAFID | ifIndex (IF-MIB) |
| aPhyEnd | efmCuPhySide | | aPhyEnd | efmCuPhySide |
| aPHYCurrentStatus | efmCuStatus | | aPHYCurrentStatus | efmCuStatus |
| aPAFSupported | efmCuPAFSupported | | aPAFSupported | efmCuPAFSupported |
| oPAF - PME Aggregation Package | | | oPAF - PME Aggregation Package | |
| (Optional) | | | (Optional) | |
| aPAFAdminState | efmCuPAFAdminState | | aPAFAdminState | efmCuPAFAdminState |
| aLocalPAFCapacity | efmCuPAFCapacity | | aLocalPAFCapacity | efmCuPAFCapacity |
skipping to change at page 13, line 21 skipping to change at page 14, line 9
EFM-CU-MIB DEFINITIONS ::= BEGIN EFM-CU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2 Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580] FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed, InterfaceIndex ifIndex, ifSpeed, InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200510240000Z" -- October 24, 2005 LAST-UPDATED "200606170000Z" -- June 17, 2006
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 14, line 4 skipping to change at page 14, line 38
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Postal: Avaya
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@avaya.com E-mail: dromasca@avaya.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks Inc. Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com" E-mail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage "The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004. 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
which is now a part of IEEE Std. 802.3-2005.
The following reference is used throughout this MIB module: The following references are used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Std 802.3ah-2004: 'IEEE Standard for Information IEEE Std 802.3ah-2004: 'IEEE Standard for Information
technology - Telecommunications and information exchange technology - Telecommunications and information exchange
between systems - Local and metropolitan area networks - between systems - Local and metropolitan area networks -
Specific requirements - Specific requirements -
Part 3: Carrier Sense Multiple Access with Collision Part 3: Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Physical Layer Detection (CSMA/CD) Access Method and Physical Layer
Specifications - Specifications -
Amendment: Media Access Control Parameters, Physical Amendment: Media Access Control Parameters, Physical
Layers and Management Parameters for Subscriber Access Layers and Management Parameters for Subscriber Access
Networks', 07 September 2004. Networks', 07 September 2004.
Of particular interest are Clause 61, 'Physical Coding Of particular interest are Clause 61, 'Physical Coding
Sublayer (PCS) and common specifications, type 10PASS-TS and Sublayer (PCS) and common specifications, type 10PASS-TS and
type 2BASE-TL', Clause 30, 'Management', Clause 45, type 2BASE-TL', Clause 30, 'Management', Clause 45,
'Management Data Input/Output (MDIO) Interface', Annex 62A, 'Management Data Input/Output (MDIO) Interface', Annex 62A,
'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
2BASE-TL'. 2BASE-TL'.
[G.991.2] refers to:
ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
Subscriber Line (SHDSL) transceivers', December 2003.
[ANFP] refers to:
NICC Document ND1602:2005/08: 'Specification of the Access
Network Frequency Plan (ANFP) applicable to transmission
systems used on the BT Access Network,' August 2005.
Naming Conventions: Naming Conventions:
Atn - Attenuation Atn - Attenuation
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
EFM - Ethernet in the First Mile EFM - Ethernet in the First Mile
EFMCu - EFM Copper EFMCu - EFM Copper
MDIO - Management Data Input/Output MDIO - Management Data Input/Output
Mgn - Margin Mgn - Margin
PAF - PME Aggregation Function PAF - PME Aggregation Function
PBO - Power Back-Off
PCS - Physical Coding Sublayer PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent PMD - Physical Medium Dependent
PME - Physical Medium Entity PME - Physical Medium Entity
PSD - Power Spectral Density PSD - Power Spectral Density
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation TCPAM - Trellis Coded Pulse Amplitude Modulation
Copyright (C) The Internet Society (2004). This version
Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200606170000Z" -- June 17, 2006
REVISION "200510240000Z" -- October 24, 2005
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 YYY } ::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 15, line 38 skipping to change at page 16, line 34
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
-- Textual Conventions -- Textual Conventions
ProfileIndex ::= TEXTUAL-CONVENTION ProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value, greater than zero, for each PME configuration "A unique value, greater than zero, for each PME configuration
profile in the managed EFMCu port. It is recommended that profile in the managed EFMCu port. It is RECOMMENDED that
values are assigned contiguously starting from 1. The value values are assigned contiguously starting from 1. The value
for each profile must remain constant at least from one for each profile MUST remain constant at least from one
re-initialization of the entity's network management system re-initialization of the entity's network management system
to the next re-initialization." to the next re-initialization."
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
ProfileIndexOrZero ::= TEXTUAL-CONVENTION ProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the ProfileIndex "This textual convention is an extension of the ProfileIndex
convention. The latter defines a greater than zero value used convention. The latter defines a greater than zero value used
to identify a PME profile in the managed EFMCu port. This to identify a PME profile in the managed EFMCu port. This
extension permits the additional value of zero. The value of extension permits the additional value of zero. The value of
zero is object-specific and must therefore be defined as part zero is object-specific and MUST therefore be defined as part
of the description of any object which uses this syntax. of the description of any object which uses this syntax.
Examples of the usage of zero value migh include situations Examples of the usage of zero value might include situations
where current operational profile is unknown." where current operational profile is unknown."
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
ProfileIndexList ::= TEXTUAL-CONVENTION ProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" DISPLAY-HINT "1d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a list of up to 6 ProfileIndex's. "Represents a list of up to 6 ProfileIndex's.
The ProfileIndex textual convention defines a greater than The ProfileIndex textual convention defines a greater than
zero value used to identify a PME profile in the managed EFMCu zero value used to identify a PME profile in the managed EFMCu
skipping to change at page 16, line 41 skipping to change at page 17, line 37
possible values of true(1) and false(2). This possible values of true(1) and false(2). This
extension permits the additional value of unknown(0), which extension permits the additional value of unknown(0), which
can be returned as a result of GET operation, when an exact can be returned as a result of GET operation, when an exact
true or false value of the object cannot be determined." true or false value of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) } SYNTAX INTEGER { unknown(0), true(1), false(2) }
-- Port Notifications Group -- Port Notifications Group
efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
efmCuLowBandwidth NOTIFICATION-TYPE efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific PCS -- ifIndex is not needed here since we are under specific PCS
ifSpeed, ifSpeed,
efmCuThreshLowBandwidth efmCuThreshLowRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that EFMCu port's data rate "This notification indicates that the EFMCu port' data rate
reached or dropped below a Low Bandwidth Threshold has reached/dropped below or exceeded the low rate threshold,
(i.e. bandwidth degradation happening in case of PAF when one specified by efmCuThreshLowRate.
or more PMEs drop)."
-- EdNote: add throttling limitations here This notification MAY be send for the -O subtype ports
(2BaseTL-O/10PassTS-O) while the port is up, on the crossing
event in both directions: from normal (rate is above the
threshold) to low (rate equals the threshold or below it) and
from low to normal. This notification is not applicable to
the -R subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and
efmCuLowRateCrossing notifications to be sent.
The adaptive nature of the EFMCu technology allows the port to
adapt itself to the changes in the copper environment, e.g.
an impulse noise, alien crosstalk or a micro-interruption may
temporarily drop one or more PMEs in the aggregation group,
causing a rate degradation of the aggregated EFMCu link.
The dropped PMEs would then try to re-initialize, possibly at
a lower rate than before, adjusting the rate to provide
required target SNR margin.
Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object."
::= { efmCuPortNotifications 1 } ::= { efmCuPortNotifications 1 }
-- PCS Port group -- PCS Port group
efmCuPortConfTable OBJECT-TYPE efmCuPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry SYNTAX SEQUENCE OF EfmCuPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
skipping to change at page 17, line 39 skipping to change at page 19, line 9
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPortConfTable 1 } ::= { efmCuPortConfTable 1 }
EfmCuPortConfEntry ::= EfmCuPortConfEntry ::=
SEQUENCE { SEQUENCE {
efmCuPAFAdminState INTEGER, efmCuPAFAdminState INTEGER,
efmCuPAFDiscoveryCode PhysAddress, efmCuPAFDiscoveryCode PhysAddress,
efmCuAdminProfile ProfileIndexList, efmCuAdminProfile ProfileIndexList,
efmCuTargetDataRate Unsigned32, efmCuTargetDataRate Unsigned32,
efmCuTargetSnrMgn Unsigned32, efmCuTargetSnrMgn Unsigned32,
efmCuThreshLowBandwidth Unsigned32, efmCuAdaptiveSpectra TruthValue,
efmCuLowBandwidthEnable TruthValue efmCuThreshLowRate Unsigned32,
efmCuLowRateCrossingEnable TruthValue
} }
efmCuPAFAdminState OBJECT-TYPE efmCuPAFAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 19, line 49 skipping to change at page 21, line 19
By default this object has a value of 0x01, referencing 1st By default this object has a value of 0x01, referencing 1st
entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable.
This object is writable and readable for the -O subtype This object is writable and readable for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for
the -R subtype (2BaseTL-R or 10PassTS-R) ports. the -R subtype (2BaseTL-R or 10PassTS-R) ports.
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object must be performed when the link is Modification of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a list with a member Attempts to set this object to a list with a member
value, that is not the value of the index for an active entry value, that is not the value of the index for an active entry
in the corresponding profile table, MUST be rejected. in the corresponding profile table, MUST be rejected.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { '01'H } DEFVAL { '01'H }
::= { efmCuPortConfEntry 3 } ::= { efmCuPortConfEntry 3 }
skipping to change at page 20, line 29 skipping to change at page 21, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired EFMCu port 'net' (as seen across MII) Data Rate in "Desired EFMCu port 'net' (as seen across MII) Data Rate in
Kbps, to be achieved during initialization, under spectral Kbps, to be achieved during initialization, under spectral
restrictions placed on each PME via efmCuAdminProfile or restrictions placed on each PME via efmCuAdminProfile or
efmCuPmeAdminProfile, with the desired SNR Margin specified by efmCuPmeAdminProfile, with the desired SNR Margin specified by
efmCuTargetSnrMgn. efmCuTargetSnrMgn.
In case of PAF, this object represents a sum of individual PME In case of PAF, this object represents a sum of individual PME
data rates, modified to compensate for fragmentation and data rates, modified to compensate for fragmentation and
64/65B framing overhead (e.g. target data rate of 10Mbps 64/65B framing overhead (e.g. target data rate of 10Mbps
shall allow lossless transmission of full-duplex 10Mbps SHALL allow lossless transmission of full-duplex 10Mbps
Ethernet frame stream with minimal inter-frame gap). Ethernet frame stream with minimal inter-frame gap).
The value is limited above by 100Mbps as this is the max The value is limited above by 100Mbps as this is the max
burst rate across MII for EFMCu ports. burst rate across MII for EFMCu ports.
The value between 1 and 100000 indicates that the total data The value between 1 and 100000 indicates that the total data
rate (ifSpeed) of the EFMCu port after initialization should rate (ifSpeed) of the EFMCu port after initialization SHALL
be equal to the target data rate or less, if the target data be equal to the target data rate or less, if the target data
rate cannot be achieved under spectral restrictions specified rate cannot be achieved under spectral restrictions specified
by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR
margin. In case the copper environment allows to achieve margin. In case the copper environment allows to achieve
higher total data rate than specified by the target, the higher total data rate than that specified by the target, the
excess capability SHALL be converted to additional SNR margin excess capability SHALL be either converted to additional SNR
and spread evenly across all active PMEs assigned to the (PCS) margin or reclaimed by minimizing transmit power as controlled
port. by efmCuAdaptiveSpectra.
The value of 999999 means that the target data rate is not The value of 999999 means that the target data rate is not
fixed and should be set to the maximum attainable rate during fixed and SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin. restrictions and with desired SNR Margin.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of the Target Data Rate MUST be performed when the Changing of the Target Data Rate MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
with the error inconsistentValue, if the link is Up or with the error inconsistentValue, if the link is Up or
Initializing. Initializing.
skipping to change at page 21, line 47 skipping to change at page 23, line 18
Initializing. Initializing.
Note that current SNR Margin of the PMEs comprising the EFMCu Note that current SNR Margin of the PMEs comprising the EFMCu
port is represented by efmCuPmeSnrMgn. port is represented by efmCuPmeSnrMgn.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.1.2" "[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 } ::= { efmCuPortConfEntry 5 }
efmCuThreshLowBandwidth OBJECT-TYPE efmCuAdaptiveSpectra OBJECT-TYPE
SYNTAX Unsigned32(400..100000) SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates how to utilize excess capacity when the copper
environment allows to achieve higher total data rate than that
specified by the efmCuTargetDataRate.
Value of true(1) indicates that the excess capability SHALL be
reclaimed by minimizing transmit power, e.g. using higher
constellations and Power Back-Off, in order to reduce
interference to other copper pairs in the binder and the
adverse impact to link/system performance.
Value of false(2) indicates that the excess capability SHALL
be converted to additional SNR margin and spread evenly across
all active PMEs assigned to the (PCS) port, to increase link
robustness.
This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected with the
error inconsistentValue, if the link is Up or Initializing.
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 }
efmCuThreshLowRate OBJECT-TYPE
SYNTAX Unsigned32(1..100000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the EFMCu port Low Bandwidth alarm "This object configures the EFMCu port low rate crossing alarm
threshold. When the current value of ifSpeed for this port threshold. When the current value of ifSpeed for this port
reaches or drops below this threshold, an reaches/drops below or exceeds this threshold, an
efmCuLowBandwidth notification MAY be generated if enabled by efmCuLowRateCrossing notification MAY be generated if enabled
efmCuLowBandwidthEnable. by efmCuLowRateCrossingEnable.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 } ::= { efmCuPortConfEntry 7 }
efmCuLowBandwidthEnable OBJECT-TYPE efmCuLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuLowBandwidth notifications should be "Indicates whether efmCuLowRateCrossing notifications should
generated for this interface. be generated for this interface.
Value of true(1) indicates that efmCuLowBandwidth Value of true(1) indicates that efmCuLowRateCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. Value of false(2) indicates that
the notification is disabled. the notification is disabled.
This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 7 } ::= { efmCuPortConfEntry 8 }
efmCuPortCapabilityTable OBJECT-TYPE efmCuPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a Ports. Entries in this table MUST be maintained in a
persistent manner" persistent manner"
::= { efmCuPort 2 } ::= { efmCuPort 2 }
skipping to change at page 24, line 48 skipping to change at page 27, line 5
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10" "[802.3ah] 61.2.2, 30.11.1.1.10"
::= { efmCuPortCapabilityEntry 4 } ::= { efmCuPortCapabilityEntry 4 }
efmCuPortStatusTable OBJECT-TYPE efmCuPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortStatusEntry SYNTAX SEQUENCE OF EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of EFMCu "This table provides overall status information of EFMCu
2BASE-TL/10PASS-TS ports. This table contains live data from 2BASE-TL/10PASS-TS ports, complementing the generic status
the equipment. As such, it is NOT persistent." information from the ifTable of IF-MIB and ifMauTable of
MAU-MIB. Additional status information about connected PMEs
is available from efmCuPmeStatusTable.
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPort 3 } ::= { efmCuPort 3 }
efmCuPortStatusEntry OBJECT-TYPE efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu Port Status table. "An entry in the EFMCu Port Status table.
Each entry represents an EFMCu port indexed by the ifIndex. Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex." or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
skipping to change at page 25, line 34 skipping to change at page 27, line 44
efmCuPAFInBadFragments Counter32, efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32, efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32, efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32, efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32 efmCuPAFInOverflows Counter32
} }
efmCuFltStatus OBJECT-TYPE efmCuFltStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
noPeer(0), noPeer(0),
pmeSubTypeMismatch(1), peerPowerLoss(1),
lowBandwidth(2) pmeSubTypeMismatch(2),
lowRate(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"EFMCu (PCS) port Fault Status. This is a bitmap of possible "EFMCu (PCS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are: conditions. The various bit positions are:
noPeer - peer PHY cannot be reached (e.g. noPeer - peer PHY cannot be reached (e.g.
no PMEs attached, all PMEs are Down no PMEs attached, all PMEs are Down
etc.) More info is available in etc.) More info is available in
efmCuPmeFltStatus. efmCuPmeFltStatus.
peerPowerLoss - peer PHY has indicated impending unit
failure due to loss of local power
('Dying Gasp').
pmeSubTypeMismatch - local PMEs in the aggregation group pmeSubTypeMismatch - local PMEs in the aggregation group
are not of the same sub-type, e.g. are not of the same sub-type, e.g.
some PMEs in the local device are -O some PMEs in the local device are -O
while others are -R subtype. while others are -R subtype.
lowBandwidth - ifSpeed of the port reached or droped lowRate - ifSpeed of the port reached or dropped
below efmCuThreshLowBandwidth below efmCuThreshLowRate
This object is intended to supplement ifOperStatus object This object is intended to supplement ifOperStatus object
in IF-MIB. in IF-MIB and ifMauMediaAvailable in MAU-MIB.
Additional information is available via efmCuPmeFltStatus Additional information is available via efmCuPmeFltStatus
object for each PME in the aggregation group (single PME if object for each PME in the aggregation group (single PME if
PAF is disabled)." PAF is disabled)."
REFERENCE REFERENCE
"ifOperStatus in IF-MIB; efmCuPmeFltStatus" "IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 } ::= { efmCuPortStatusEntry 1 }
efmCuPortSide OBJECT-TYPE efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
subscriber(1), subscriber(1),
office(2), office(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 27, line 30 skipping to change at page 29, line 47
REFERENCE REFERENCE
"[802.3ah] 45.2.3.21" "[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 } ::= { efmCuPortStatusEntry 4 }
efmCuPAFInSmallFragments OBJECT-TYPE efmCuPAFInSmallFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments smaller than minFragmentSize "A number of fragments smaller than minFragmentSize
(64 Bytes), that have been received across the gamma interface (64 Bytes), which have been received across the gamma
and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF small fragments this object maps to the 10P/2B PAF small fragments
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.22" "[802.3ah] 45.2.3.22"
::= { efmCuPortStatusEntry 5 } ::= { efmCuPortStatusEntry 5 }
efmCuPAFInLargeFragments OBJECT-TYPE efmCuPAFInLargeFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments larger than maxFragmentSize "A number of fragments larger than maxFragmentSize
(512 Bytes), that have been received across the gamma (512 Bytes), which have been received across the gamma
interface and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF large fragments this object maps to the 10P/2B PAF large fragments
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.23" "[802.3ah] 45.2.3.23"
skipping to change at page 28, line 39 skipping to change at page 31, line 7
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.25" "[802.3ah] 45.2.3.25"
::= { efmCuPortStatusEntry 7 } ::= { efmCuPortStatusEntry 7 }
efmCuPAFInLostFragments OBJECT-TYPE efmCuPAFInLostFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of gaps in the sequence of fragments, that have been "A number of gaps in the sequence of fragments, which have
received across the gamma interface (the frame buffer is been received across the gamma interface (the frame buffer is
flushed to the next valid frame start, when fragment/fragments flushed to the next valid frame start, when fragment/fragments
expected by the frame assembly function is/are not received). expected by the frame assembly function is/are not received).
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost fragment this object maps to the 10P/2B PAF lost fragment
register." register."
REFERENCE REFERENCE
skipping to change at page 29, line 47 skipping to change at page 32, line 15
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.28" "[802.3ah] 45.2.3.28"
::= { efmCuPortStatusEntry 10 } ::= { efmCuPortStatusEntry 10 }
efmCuPAFInOverflows OBJECT-TYPE efmCuPAFInOverflows OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragements, received accross the gamma interface "A number of fragments, received across the gamma interface
and discarded, which would have caused the frame assembly and discarded, which would have caused the frame assembly
buffer to overflow. buffer to overflow.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF overflow register." this object maps to the 10P/2B PAF overflow register."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.24" "[802.3ah] 45.2.3.24"
::= { efmCuPortStatusEntry 11 } ::= { efmCuPortStatusEntry 11 }
-- PME Notifications Group -- PME Notifications Group
efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 }
-- EdNote: Should I add more notifications here, for example
-- efmCuPmePerfES,
-- efmCuPmePerfSES,
-- efmCuPmePerfCRCanomalies,
-- efmCuPmePerfLOSWS,
-- efmCuPmePerfUAS,
-- efmCuPmeDeviceFault,
-- efmCuPmeLocalPowerLoss
-- Another option would be to reference HDSL2-SHDSL-LINE-MIB
-- or VDSL-LINE-EXT-MCM-MIB, reusing notifications defined there.
efmCuPmeLineAtnCrossing NOTIFICATION-TYPE efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeLineAtn, efmCuPmeLineAtn,
efmCuPmeThreshLineAtn efmCuPmeThreshLineAtn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the loop attenuation "This notification indicates that the loop attenuation
threshold (as per the efmCuPmeThreshLineAtn threshold (as per the efmCuPmeThreshLineAtn
value) has been reached/exceeded for the 2BASE-TL/10PASS-TS value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
PME. This notification MAY be send on the crossing event in PME. This notification MAY be send on the crossing event in
both directions: from normal to exceeded and from exceeded both directions: from normal to exceeded and from exceeded
to normal. to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification,
is implemented to prevent intermittent notifications to be
sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeLineAtnCrossingEnable object." efmCuPmeLineAtnCrossingEnable object."
-- EdNote: add throttling limitations here, with 10 sec
-- debouncing on clear to prevenmt intermittent alarms
::= { efmCuPmeNotifications 1 } ::= { efmCuPmeNotifications 1 }
efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeSnrMgn, efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the SNR margin threshold "This notification indicates that the SNR margin threshold
(as per the efmCuPmeThreshSnrMgn value) has been (as per the efmCuPmeThreshSnrMgn value) has been
reached/exceeded for the 2BASE-TL/10PASS-TS PME. reached/exceeded for the 2BASE-TL/10PASS-TS PME.
This notification MAY be send on the crossing event in This notification MAY be send on the crossing event in
both directions: from normal to exceeded and from exceeded both directions: from normal to exceeded and from exceeded
to normal. to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification,
is implemented to prevent intermittent notifications to be
sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object." efmCuPmeSnrMgnCrossingEnable object."
-- EdNote: add throttling limitations here, with 10 sec
-- debouncing on clear to prevenmt intermittent alarms
::= { efmCuPmeNotifications 2 } ::= { efmCuPmeNotifications 2 }
efmCuPmeDeviceFault NOTIFICATION-TYPE efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus efmCuPmeFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that a fault in the PME has been "This notification indicates that a fault in the PME has been
detected by a vendor specific diagnostic or a self-test. detected by a vendor specific diagnostic or a self-test.
skipping to change at page 33, line 25 skipping to change at page 35, line 36
ieee10PassTSR(4), ieee10PassTSR(4),
ieee2BaseTLor10PassTSR(5), ieee2BaseTLor10PassTSR(5),
ieee2BaseTLor10PassTSO(6), ieee2BaseTLor10PassTSO(6),
ieee10PassTSor2BaseTLO(7) ieee10PassTSor2BaseTLO(7)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Administrative (desired) sub-type of the PME. "Administrative (desired) sub-type of the PME.
Possible values are: Possible values are:
ieee2BaseTLO - PME shall operate as 2BaseTL-O ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
ieee2BaseTLR - PME shall operate as 2BaseTL-R ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
ieee10PassTSO - PME shall operate as 10PassTS-O ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME shall operate as 10PassTS-R ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME shall operate as 2BaseTL-R or ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. Actual value will be 10PassTS-R. Actual value will be
set by -O link partner during set by -O link partner during
initialization (handshake). initialization (handshake).
ieee2BaseTLor10PassTSO - PME shall operate as 2BaseTL-O ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. Actual (preferred) or 10PassTS-O. Actual
value will be set during value will be set during
initialization depending on -R initialization depending on -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
2BaseTL mode, 10PassTS will be 2BaseTL mode, 10PassTS will be
used). used).
ieee10PassTSor2BaseTLO - PME shall operate as 10PassTS-O
ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
(preferred) or 2BaseTL-O. Actual (preferred) or 2BaseTL-O. Actual
value will be set during value will be set during
initialization depending on -R initialization depending on -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
10PassTS mode, 2BaseTL will be 10PassTS mode, 2BaseTL will be
used). used).
Changing efmCuPmeAdminSubType is a traffic disruptive Changing efmCuPmeAdminSubType is a traffic disruptive
operation and as such SHALL be done when the link is Down. operation and as such SHALL be done when the link is Down.
skipping to change at page 34, line 4 skipping to change at page 36, line 16
(preferred) or 2BaseTL-O. Actual (preferred) or 2BaseTL-O. Actual
value will be set during value will be set during
initialization depending on -R initialization depending on -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
10PassTS mode, 2BaseTL will be 10PassTS mode, 2BaseTL will be
used). used).
Changing efmCuPmeAdminSubType is a traffic disruptive Changing efmCuPmeAdminSubType is a traffic disruptive
operation and as such SHALL be done when the link is Down. operation and as such SHALL be done when the link is Down.
Attempts to change this object SHALL be ignored if the link Attempts to change this object SHALL be ignored if the link
is Up or Initializing. is Up or Initializing.
Attempts to change this object to an unsupported subtype Attempts to change this object to an unsupported subtype
(see efmCuPmeSubTypesSupported) SHALL be rejected. (see efmCuPmeSubTypesSupported) SHALL be rejected.
The current operational sub type is indicated by The current operational sub type is indicated by
efmCuPmeOperSubType variable. efmCuPmeOperSubType variable.
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port sub-type select this object combines values of the Port sub-type select bits
bits and the PMA/PMD type selection bits in the 10P/2B and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
PMA/PMD control register" control register"
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
::= { efmCuPmeConfEntry 1 } ::= { efmCuPmeConfEntry 1 }
efmCuPmeAdminProfile OBJECT-TYPE efmCuPmeAdminProfile OBJECT-TYPE
SYNTAX ProfileIndexOrZero SYNTAX ProfileIndexOrZero
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired PME configuration Profile. This object is a pointer "Desired PME configuration Profile. This object is a pointer
to an entry in either efmCuPme2BProfileTable or to an entry in either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current operating
operating SubType of the PME. The value of this object is the SubType of the PME. The value of this object is the index of
index of the referenced profile. the referenced profile.
The value of zero (default) indicates that the PME is The value of zero (default) indicates that the PME is
configured via efmCuAdminProfile object for the PCS port, configured via efmCuAdminProfile object for the PCS port,
to which this PME is assigned. That is, the profile referenced to which this PME is assigned. That is, the profile referenced
by efmCuPmeAdminProfile takes precedence over the profile(s) by efmCuPmeAdminProfile takes precedence over the profile(s)
referenced by efmCuAdminProfile. referenced by efmCuAdminProfile.
This object is writable and readable for the CO subtype PMEs This object is writable and readable for the CO subtype PMEs
(2BaseTL-O or 10PassTS-O). It is unavailable for the CPE (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE
subtype (2BaseTL-R or 10PassTS-R). subtype (2BaseTL-R or 10PassTS-R).
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object must be performed when the link is Modification of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a value that is not the Attempts to set this object to a value that is not the value
value of the index for an active entry in the corresponding of the index for an active entry in the corresponding profile
profile table, MUST be rejected." table, MUST be rejected."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { 0 } DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 } ::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PAF Remote Discovery Code of the PME port at CO. "PAF Remote Discovery Code of the PME port at CO.
A 6 Byte long Discovery Code of the peer PCS connected via A 6 Byte long Discovery Code of the peer PCS connected via
the PME. the PME.
Reading this object results in a Discovery Get operation. Reading this object results in a Discovery Get operation.
Writing a zero to this object results in a Discovery Writing a zero to this object results in a Discovery
Clear_if_Same operation (the value of efmCuPAFDiscoveryCode Clear_if_Same operation (the value of efmCuPAFDiscoveryCode
at the peer PCS shall be the same as efmCuPAFDiscoveryCode of at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of
the local PCS associated with the PME for the operation to the local PCS associated with the PME for the operation to
succeed). succeed).
Writing a non-zero value to this object results in a Writing a non-zero value to this object results in a
Discovery Set_if_Clear operation. Discovery Set_if_Clear operation.
This object does not exist in CPE port subtypes. A zero length This object does not exist in CPE port subtypes. A zero length
octet string SHALL be returned for CPE port subtypes and also octet string SHALL be returned for CPE port subtypes and also
when PAF aggregation is not enabled. when PAF aggregation is not enabled.
Discovery MUST be performed when the link is Down. Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected with the error Attempts to change this object MUST be rejected with the error
skipping to change at page 36, line 8 skipping to change at page 38, line 18
"Desired Line Attenuation Threshold for the 2B/10P PME. "Desired Line Attenuation Threshold for the 2B/10P PME.
This object configures the line attenuation alarm threshold. This object configures the line attenuation alarm threshold.
When the current value of Line Attenuation reaches or When the current value of Line Attenuation reaches or
exceeds this threshold, a efmCuPmeLineAtnCrossing exceeds this threshold, a efmCuPmeLineAtnCrossing
notification MAY be generated, if enabled by notification MAY be generated, if enabled by
efmCuPmeLineAtnCrossingEnable. efmCuPmeLineAtnCrossingEnable.
This object is writable for the CO subtype PMEs (-O). This object is writable for the CO subtype PMEs (-O).
It is read-only for the CPE subtype (-R). It is read-only for the CPE subtype (-R).
Changing of the Line Attenuation Threshold must be performed Changing of the Line Attenuation Threshold MUST be performed
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up rejected with the error inconsistentValue, if the link is Up
or Initializing. or Initializing.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object will map to the Loop attenuation threshold bits in object maps to the Loop attenuation threshold bits in
the 2B PMD line quality thresholds register" the 2B PMD line quality thresholds register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.36" "[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 4 } ::= { efmCuPmeConfEntry 4 }
efmCuPmeThreshSnrMgn OBJECT-TYPE efmCuPmeThreshSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128) SYNTAX Integer32(-127..128)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired SNR Margin Threshold for the 2B/10P PME. "Desired SNR Margin Threshold for the 2B/10P PME.
This object configures the SNR margin alarm threshold. This object configures the SNR margin alarm threshold.
When the current value of SNR Margin reaches When the current value of SNR Margin reaches or exceeds this
or exceeds this threshold, a efmCuPmeSnrMgnCrossing threshold, a efmCuPmeSnrMgnCrossing notification MAY be
notification MAY be generated, if enabled by generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
efmCuPmeSnrMgnCrossingEnable.
This object is writable for the CO subtype PMEs This object is writable for the CO subtype PMEs
(2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype
(2BaseTL-R/10PassTS-R). (2BaseTL-R/10PassTS-R).
Changing of the SNR Margin Threshold must be performed when Changing of the SNR Margin Threshold MUST be performed when
the link is Down. Attempts to change this object MUST be the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up rejected with the error inconsistentValue, if the link is Up
or Initializing. or Initializing.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object will map to the SNR margin threshold bits in the object maps to the SNR margin threshold bits in the 2B PMD
2B PMD line quality thresholds register" line quality thresholds register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.36" "[802.3ah] 45.2.1.36"
::= { efmCuPmeConfEntry 5 } ::= { efmCuPmeConfEntry 5 }
efmCuPmeLineAtnCrossingEnable OBJECT-TYPE efmCuPmeLineAtnCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeLineAtnCrossing notifications "Indicates whether efmCuPmeLineAtnCrossing notifications
skipping to change at page 39, line 21 skipping to change at page 41, line 31
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME supported sub-types. This is a bitmap of possible "PME supported sub-types. This is a bitmap of possible
sub-types. The various bit positions are: sub-types. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSO - PME is capable of operating as 10PassTS-O
ieee10PassTSR - PME is capable of operating as 10PassTS-R ieee10PassTSR - PME is capable of operating as 10PassTS-R
An desired mode of operation is determined by An desired mode of operation is determined by
efmCuPmeAdminSubType, while efmCuPmeOperSubType relects the efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
current operating mode. current operating mode.
If a Clause 45 MDIO Interface to the PCS is present, then this If a Clause 45 MDIO Interface to the PCS is present, then this
object combines the 10PASS-TS capable and 2BASE-TL capable object combines the 10PASS-TS capable and 2BASE-TL capable
bits in the 10P/2B PMA/PMD speed ability register and the bits in the 10P/2B PMA/PMD speed ability register and the
CO supported and CPE supported bits in the 10P/2B PMA/PMD CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register" status register"
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
45.2.1.12.3" 45.2.1.12.3"
skipping to change at page 40, line 23 skipping to change at page 42, line 33
EfmCuPmeStatusEntry ::= EfmCuPmeStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeOperStatus INTEGER, efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS, efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER, efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile ProfileIndexOrZero, efmCuPmeOperProfile ProfileIndexOrZero,
efmCuPmeSnrMgn Integer32, efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32, efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32, efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32, efmCuPmePeerLineAtn Integer32,
efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32, efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32 efmCuPmeTCCrcErrors Counter32
} }
efmCuPmeOperStatus OBJECT-TYPE efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
downNotReady(2), downNotReady(2),
downReady(3), downReady(3),
init(4) init(4)
skipping to change at page 41, line 46 skipping to change at page 44, line 9
deviceFault - Indicates a vendor-dependent deviceFault - Indicates a vendor-dependent
diagnostic or self-test fault diagnostic or self-test fault
has been detected. has been detected.
configInitFailure - Configuration initialization failure, configInitFailure - Configuration initialization failure,
due to inability of the PME link to due to inability of the PME link to
support configuration profile, support configuration profile,
requested during initialization. requested during initialization.
protocolInitFailure - Protocol initialization failure, protocolInitFailure - Protocol initialization failure,
due to incompatible protocol used by due to incompatible protocol used by
the Peer PME during init (that could the Peer PME during init (that could
happen if a peer PMD is G.SDHSL/VDSL happen if a peer PMD is a regular
modem for 2BASE-TL/10PASS-TS PME G.SDHSL/VDSL modem instead of a
respectively). 2BASE-TL/10PASS-TS PME).
This object is intended to supplement ifOperStatus in IF-MIB. This object is intended to supplement ifOperStatus in IF-MIB.
The indications hold information about the last fault. This object holds information about the last fault.
efmCuPmeFltStatus is cleared by the device restart. efmCuPmeFltStatus is cleared by the device restart.
In addition lossOfFraming, configInitFailure and In addition lossOfFraming, configInitFailure and
protocolInitFailure are cleared by PME init. protocolInitFailure are cleared by PME init.
deviceFault is cleared by successful diagnostics/test. deviceFault is cleared by successful diagnostics/test.
snrMgnDefect and lineAtnDefect are cleared by SNR Margin snrMgnDefect and lineAtnDefect are cleared by SNR Margin
and line Attenuation respectively returning to norm and by and line Attenuation respectively returning to norm and by
PME init. PME init.
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPMEStatus. aPMEStatus.
skipping to change at page 45, line 12 skipping to change at page 47, line 23
This object is not supported by CPE port subtypes. This object is not supported by CPE port subtypes.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 20P/2B link partner Line Attenuation object maps to the 20P/2B link partner Line Attenuation
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.19" "[802.3ah] 45.2.1.19"
::= { efmCuPmeStatusEntry 8 } ::= { efmCuPmeStatusEntry 8 }
efmCuPmeEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192|65535)
UNITS "m"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the equivalent loop's Physical Length in
meters, as perceived by the PME after the link is established.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any
bridged taps.
The value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the Equivalent
Length.
For 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is
present, then this object maps to the 10P Electrical Length
register"
REFERENCE
"[802.3ah] 45.2.1.21"
::= { efmCuPmeStatusEntry 9 }
efmCuPmeTCCodingErrors OBJECT-TYPE efmCuPmeTCCodingErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of 64/65-octet encapsulation errors. This counter is "A number of 64/65-octet encapsulation errors. This counter is
incremented for each 64/65-octet encapsulation error detected incremented for each 64/65-octet encapsulation error detected
by the 64/65-octet receive function. by the 64/65-octet receive function.
The value of zero SHALL be returned when PME is down or The value of zero SHALL be returned when PME is down or
initializing. initializing.
If a Clause 45 MDIO Interface to the PME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register this object maps to the TC coding violations register
(see 45.2.6.12)." (see 45.2.6.12)."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.1, 45.2.6.12" "[802.3ah] 61.3.3.1, 45.2.6.12"
::= { efmCuPmeStatusEntry 9 } ::= { efmCuPmeStatusEntry 10 }
efmCuPmeTCCrcErrors OBJECT-TYPE efmCuPmeTCCrcErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of TC-CRC errors. This counter is incremented for "A number of TC-CRC errors. This counter is incremented for
each TC-CRC error detected by the 64/65-octet receive function each TC-CRC error detected by the 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19). (see 61.3.3.3 and Figure 61-19).
The value of zero SHALL be returned when PME is down or The value of zero SHALL be returned when PME is down or
initializing. initializing.
If a Clause 45 MDIO Interface to the PCME TC is present, then If a Clause 45 MDIO Interface to the PCME TC is present, then
this object maps to the TC CRC error register this object maps to the TC CRC error register
(see 45.2.6.11)." (see 45.2.6.11)."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.3, 45.2.6.11" "[802.3ah] 61.3.3.3, 45.2.6.11"
::= { efmCuPmeStatusEntry 10 } ::= { efmCuPmeStatusEntry 11 }
-- 2BASE-TL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BProfileTable OBJECT-TYPE efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of administrative and "This table supports definitions of administrative and
operating Profiles for 2BASE-TL PMEs. operating Profiles for 2BASE-TL PMEs.
First 14 entries in this table SHALL always be defined as First 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A): follows (see 802.3ah Annex 63A):
-------+------+-----+--------+------------------ -------+-------+-------+-----+------+------------------
Profile Rate Power Region Constellation Profile MinRate MaxRate Power Region Constellation
index (Kbps) (dBm) (G.991.2) index (Kbps) (Kbps) (dBm)
-------+------+-----+--------+------------------ -------+-------+-------+-----+------+------------------
1 5696 13.5 1 32-TCPAM (default) 1 5696 5696 13.5 1 32-TCPAM (default)
2 3072 13.5 1 32-TCPAM 2 3072 3072 13.5 1 32-TCPAM
3 2048 13.5 1 16-TCPAM 3 2048 2048 13.5 1 16-TCPAM
4 1024 13.5 1 16-TCPAM 4 1024 1024 13.5 1 16-TCPAM
5 704 13.5 1 16-TCPAM 5 704 704 13.5 1 16-TCPAM
6 512 13.5 1 16-TCPAM 6 512 512 13.5 1 16-TCPAM
7 5696 14.5 2 32-TCPAM 7 5696 5696 14.5 2 32-TCPAM
8 3072 14.5 2 32-TCPAM 8 3072 3072 14.5 2 32-TCPAM
9 2048 14.5 2 16-TCPAM 9 2048 2048 14.5 2 16-TCPAM
10 1024 13.5 2 16-TCPAM 10 1024 1024 13.5 2 16-TCPAM
11 704 13.5 2 16-TCPAM 11 704 704 13.5 2 16-TCPAM
12 512 13.5 2 16-TCPAM 12 512 512 13.5 2 16-TCPAM
13 0 0 1 0 (best effort) 13 192 5696 0 1 0 (best effort)
14 0 0 2 0 (best effort) 14 192 5696 0 2 0 (best effort)
These default entries SHALL be created during agent These default entries SHALL be created during agent
initialization and MUST not be deleted. initialization and MUST NOT be deleted.
Entries following the first 14, can be dynamically created and Entries following the first 14, can be dynamically created and
deleted, to provide custom administrative (configuration) deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles. profiles and automatic operating profiles.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] Annex 63A, 30.11.2.1.6" "[802.3ah] Annex 63A, 30.11.2.1.6"
::= { efmCuPme2B 2 } ::= { efmCuPme2B 2 }
skipping to change at page 47, line 15 skipping to change at page 49, line 49
efmCuPmeAdminProfile is zero), it represent the desired efmCuPmeAdminProfile is zero), it represent the desired
parameters the 2BaseTL-O PME initialization. parameters the 2BaseTL-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object, If a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the it represents current operating parameters of the
operational PME. operational PME.
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active' active entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST not be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex } INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BProfileTable 1 } ::= { efmCuPme2BProfileTable 1 }
EfmCuPme2BProfileEntry ::= EfmCuPme2BProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BProfileIndex ProfileIndex, efmCuPme2BProfileIndex ProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString, efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER, efmCuPme2BRegion INTEGER,
efmCuPme2BDataRate Unsigned32, efmCuPme2BsMode ProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BPower Unsigned32, efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER, efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus efmCuPme2BProfileRowStatus RowStatus
} }
efmCuPme2BProfileIndex OBJECT-TYPE efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex SYNTAX ProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Profile index. "2BASE-TL PME Profile index.
This object is the unique index associated with this profile. This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile Entries in this table are referenced via efmCuAdminProfile
or efmCuPmeAdminProfile objects." or efmCuPmeAdminProfile objects."
::= { efmCuPme2BProfileEntry 1 } ::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileDescr OBJECT-TYPE efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..255)) SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 2BASE-TL PME "A textual string containing information about 2BASE-TL PME
Profile. The string MAY include information about data rate Profile. The string MAY include information about data rate
and spectral limitations of this particular profile." and spectral limitations of this particular profile."
::= { efmCuPme2BProfileEntry 2 } ::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
region1(1), region1(1),
region2(2) region2(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Power Spectral Density (PSD) Regional settings as "Regional settings for 2BASE-TL PME, as specified in the
specified in the relevant Regional Annex of [G.991.2]. relevant Regional Annex of [G.991.2].
Regional settings place limitations on the max allowed Regional settings specify Power Spectral Density (PSD) mask,
data rate, power and constellation. Power Back-Off (PBO) values and place limitations on the max
allowed data rate, power and constellation.
Possible values for this object are: Possible values for this object are:
region1 -- Annexes A and F (e.g. North America) region1 - Annexes A and F (e.g. North America)
region2 -- Annexes B and G (e.g. Europe) region2 - Annexes B and G (e.g. Europe)
Changing of the Region must be performed when the link is Annex A/B specify regional settings for data rates 192-2304
Down. Kbps using 16-TCPAM encoding.
Attempts to change this object MUST be rejected with Annex F/G specify regional settings for rates 2320-3840 Kbps
the error inconsistentValue, if the link is Up or using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
Initializing. encoding.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Region bits in the 2B general object partially maps to the Region bits in the 2B general
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.42" "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 } ::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BDataRate OBJECT-TYPE efmCuPme2BsMode OBJECT-TYPE
SYNTAX Unsigned32(0..5696) SYNTAX ProfileIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Desired custom Spectral Mode for 2BASE-TL PME. This object
is a pointer to an entry in efmCuPme2BsModeTable and a block
of entries in efmCuPme2BRateReachTable, which together define
(country-specific) reach dependent rate limitations in
addition to those defined by efmCuPme2BRegion.
The value of this object is the index of the referenced
spectral mode.
The value of zero (default) indicates that no specific
spectral mode is applicable.
Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral
mode table, MUST be rejected."
REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { 0 }
::= { efmCuPme2BProfileEntry 4 }
efmCuPme2BMinDataRate OBJECT-TYPE
SYNTAX Unsigned32(192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Data Rate. "Minimum Data Rate for the 2BASE-TL PME.
The rate is fixed when the value of this object is n x 64Kbps,
where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. This object can take values of (n x 64)Kbps,
The value of 0 in the administrative profile means that data where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
rate is not fixed but is adaptive and should be set to the
maximum attainable rate during line probing, under the The data rate of the 2BASE-TL PME is considered 'fixed' when
spectral limitations placed by the efmCuPme2BRegion. the value of this object equals that of efmCuPme2BMaxDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode.
Note that current operational data rate of the PME is
represented by ifSpeed object of IF-MIB.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Min/Max Data Rate1 bits in the 2B PMD object maps to the Min Data Rate1 bits in the 2B PMD
parameters register. parameters register.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 4 } ::= { efmCuPme2BProfileEntry 5 }
efmCuPme2BMaxDataRate OBJECT-TYPE
SYNTAX Unsigned32(192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Data Rate for the 2BASE-TL PME.
This object can take values of (n x 64)Kbps,
where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
The data rate of the 2BASE-TL PME is considered 'fixed' when
the value of this object equals that of efmCuPme2BMinDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode.
Note that current operational data rate of the PME is
represented by ifSpeed object of IF-MIB.
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Max Data Rate1 bits in the 2B PMD
parameters register.
This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 }
efmCuPme2BPower OBJECT-TYPE efmCuPme2BPower OBJECT-TYPE
SYNTAX Unsigned32(0|10..42) SYNTAX Unsigned32(0|10..42)
UNITS "0.5 dBm" UNITS "0.5 dBm"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signal Transmit Power. Multiple of 0.5dBm. "Signal Transmit Power. Multiple of 0.5dBm.
The value of 0 in the administrative profile means that the The value of 0 in the administrative profile means that the
signal transmit power is not fixed and should be set to signal transmit power is not fixed and SHALL be set to
maximize the attainable rate, under the spectral limitations maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion. placed by the efmCuPme2BRegion and efmCuPme2BsMode.
Changing of the Signal Transmit Power must be performed when
the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up
or Initializing.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object will map to the Power1 bits in the 2B PMD object maps to the Power1 bits in the 2B PMD parameters
parameters register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 5 } ::= { efmCuPme2BProfileEntry 7 }
efmCuPme2BConstellation OBJECT-TYPE efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
adaptive(0), adaptive(0),
tcpam16(1), tcpam16(1),
tcpam32(2) tcpam32(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"TCPAM Constellation of the 2BASE-TL PME. "TCPAM Constellation of the 2BASE-TL PME.
The possible values are: The possible values are:
adaptive(0) - either 16- or 32-TCPAM adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM tcpam32(2) - 32-TCPAM
The value of adaptive(0) in the administrative profile means The value of adaptive(0) in the administrative profile means
that the constellation is not fixed and should be set to that the constellation is not fixed and SHALL be set to
maximize the attainable rate, under the spectral limitations maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion. placed by the efmCuPme2BRegion and efmCuPme2BsMode.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object map to the Constellation1 bits in the 2B general object maps to the Constellation1 bits in the 2B general
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 } ::= { efmCuPme2BProfileEntry 8 }
efmCuPme2BProfileRowStatus OBJECT-TYPE efmCuPme2BProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation/deletion of the associated "This object controls creation/deletion of the associated
entry in efmCuPme2BProfileTable per the semantics of entry in efmCuPme2BProfileTable per the semantics of
RowStatus. RowStatus.
If an 'active' entry is referenced via efmCuAdminProfile or If an 'active' entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile, the entry MUST remain 'active' until all efmCuPmeAdminProfile, the entry MUST remain 'active' until all
references are removed." references are removed."
::= { efmCuPme2BProfileEntry 7 } ::= { efmCuPme2BProfileEntry 9 }
efmCuPme2BsModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations in addition to
those specified by efmCuPme2BRegion.
Some countries spectral regulations (e.g. UK ANFP) limit the
length of the loops for certain data rates. This table allows
these country-specific limitations to be specified.
Entries in this table referenced by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are
removed.
This table MUST be maintained in a persistent manner."
REFERENCE
"efmCu2BReachRateTable"
::= { efmCuPme2B 3 }
efmCuPme2BsModeEntry OBJECT-TYPE
SYNTAX EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry specifies spectral mode description and its index,
which is used to reference corresponding entries in the
efmCu2BReachRateTable.
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 }
EfmCuPme2BsModeEntry ::=
SEQUENCE {
efmCuPme2BsModeIndex ProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus
}
efmCuPme2BsModeIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral
mode.
Entries in this table are referenced via efmCuPme2BsMode
object."
::= { efmCuPme2BsModeEntry 1 }
efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about 2BASE-TL PME
spectral mode. The string MAY include information about
corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 }
efmCuPme2BsModeRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme2BsModeTable per the semantics of
RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed."
::= { efmCuPme2BsModeEntry 3 }
efmCuPme2BReachRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definition of administrative custom
spectral modes for 2BASE-TL PMEs, providing spectral
limitations in addition to those specified by
efmCuPme2BRegion.
The spectral regulations in some countries (e.g. UK ANFP)
limit the length of the loops for certain data rates.
This table allows these country-specific limitations to be
specified.
Below is an example of this table for [ANFP]:
----------+-------+-------+
Equivalent MaxRate MaxRate
Length PAM16 PAM32
(m) (Kbps) (Kbps)
----------+-------+-------+
975 2304 5696
1125 2304 5504
1275 2304 5120
1350 2304 4864
1425 2304 4544
1500 2304 4288
1575 2304 3968
1650 2304 3776
1725 2304 3520
1800 2304 3264
1875 2304 3072
1950 2048 2688
2100 1792 2368
2250 1536 0
2400 1408 0
2550 1280 0
2775 1152 0
2925 1152 0
3150 1088 0
3375 1024 0
----------+-------+-------+
Entries in this table referenced by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are
removed.
This table MUST be maintained in a persistent manner."
REFERENCE
"[ANFP]"
::= { efmCuPme2B 4 }
efmCuPme2BReachRateEntry OBJECT-TYPE
SYNTAX EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry specifies maximum 2BASE-TL PME data rates
allowed for a certain equivalent loop length, when using
16-TCPAM or 32-TCPAM encoding.
When 2BASE-TL PME is initialized, its data rate MUST NOT
exceed one of the following limitations:
- the value of efmCuPme2BMaxDataRate
- maximum data rate allowed by efmCuPme2BRegion and
efmCuPme2BPower
- maximum data rate for a given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by the PME.
It is RECOMMENDED that the efmCuPme2BEquivalentLength values
are assigned in the increasing order, starting from the
minimum value.
Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BEquivalentLength }
::= { efmCuPme2BReachRateTable 1 }
EfmCuPme2BReachRateEntry ::=
SEQUENCE {
efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus
}
efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192)
UNITS "m"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum allowed Equivalent loop's Physical Length in meters
for the specified data rates.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any
bridged taps."
REFERENCE
""
::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be
used at this distance."
REFERENCE
""
::= { efmCuPme2BReachRateEntry 2 }
efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be
used at this distance."
REFERENCE
""
::= { efmCuPme2BReachRateEntry 3 }
efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme2BReachRateTable per the semantics of
RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed."
::= { efmCuPme2BReachRateEntry 4 }
-- 10PASS-TS specific PME group -- 10PASS-TS specific PME group
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PProfileTable OBJECT-TYPE efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of configuration profiles for "This table supports definitions of configuration profiles for
skipping to change at page 51, line 17 skipping to change at page 59, line 45
15 6 0 2,6,10,11 50 10 15 6 0 2,6,10,11 50 10
16 17 0 2,5,9,11 30 30 16 17 0 2,5,9,11 30 30
17 8 0 2,6,10,11 30 5 17 8 0 2,6,10,11 30 5
18 4 0 2,6,10,11 25 25 18 4 0 2,6,10,11 25 25
19 4 0 2,6,10,11 15 15 19 4 0 2,6,10,11 15 15
20 23 0 2,5,9,11 10 10 20 23 0 2,5,9,11 10 10
21 23 0 2,5,9,11 5 5 21 23 0 2,5,9,11 5 5
22 30 0 0 200 50 22 30 0 0 200 50
These default entries SHALL be created by during agent These default entries SHALL be created by during agent
initialization and MUST not be deleted. initialization and MUST NOT be deleted.
Entries following the first 22, can be dynamically created and Entries following the first 22, can be dynamically created and
deleted, to provide custom administrative (configuration) deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles. profiles and automatic operating profiles.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] Annex 62B.3, 30.11.2.1.6" "[802.3ah] Annex 62B.3, 30.11.2.1.6"
::= { efmCuPme10P 1 } ::= { efmCuPme10P 1 }
skipping to change at page 51, line 48 skipping to change at page 60, line 28
efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the desired efmCuPmeAdminProfile is zero), it represent the desired
parameters the 10PassTS-O PME initialization. parameters the 10PassTS-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object, If a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the PME. it represents current operating parameters of the PME.
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active' 'active' entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST not be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex } INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 } ::= { efmCuPme10PProfileTable 1 }
EfmCuPme10PProfileEntry ::= EfmCuPme10PProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PProfileIndex ProfileIndex, efmCuPme10PProfileIndex ProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString, efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER, efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER, efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS, efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER, efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus efmCuPme10PProfileRowStatus RowStatus
skipping to change at page 52, line 28 skipping to change at page 61, line 8
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Profile Index. "10PASS-TS PME Profile Index.
This object is the unique index associated with this profile. This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile or Entries in this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile." efmCuPmeAdminProfile."
::= { efmCuPme10PProfileEntry 1 } ::= { efmCuPme10PProfileEntry 1 }
efmCuPme10PProfileDescr OBJECT-TYPE efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..255)) SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 10PASS-TS PME "A textual string containing information about 10PASS-TS PME
Profile. The string MAY include information about data rate Profile. The string MAY include information about data rate
and spectral limitations of this particular profile." and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 } ::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 58, line 21 skipping to change at page 66, line 48
SYNTAX EfmCuPme10PStatusEntry SYNTAX EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu 10PASS-TS PME Status table." "An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry } AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 } ::= { efmCuPme10PStatusTable 1 }
EfmCuPme10PStatusEntry ::= EfmCuPme10PStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PElectricalLength Integer32,
efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32 efmCuPme10PFECUncorrectedBlocks Counter32
-- EdNote: To be continued
} }
efmCuPme10PElectricalLength OBJECT-TYPE
SYNTAX Integer32(0..8192|65535)
UNITS "m"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Electrical Length in meters as perceived by the 10PASS-TS PME
after the link is established.
The value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the Electrical
Length.
If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the 10P Electrical Length register"
REFERENCE
"[802.3ah] 45.2.1.21"
::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received and corrected FEC codewords in 10PASS-TS "A count of received and corrected FEC codewords in 10PASS-TS
PME. PME.
This object maps to aPMEFECCorrectedBlocks attribute in This object maps to aPMEFECCorrectedBlocks attribute in
clause 30. clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC correctable errors then this object maps to the 10P FEC correctable errors
register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.22" "[802.3ah] 45.2.1.22"
::= { efmCuPme10PStatusEntry 2 } ::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received FEC codewords in 10PASS-TS PME, which are "A count of received FEC codewords in 10PASS-TS PME, which are
uncorrectable. uncorrectable.
This object maps to aPMEFECUncorrectableBlocks attribute in This object maps to aPMEFECUncorrectableBlocks attribute in
clause 30. clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC uncorrectable errors then this object maps to the 10P FEC uncorrectable errors
register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.23" "[802.3ah] 45.2.1.23"
::= { efmCuPme10PStatusEntry 3 } ::= { efmCuPme10PStatusEntry 2 }
-- ifAvailableStackTable for use in Discovery -- ifAvailableStackTable for use in Discovery
ifAvailableStackTable OBJECT-TYPE ifAvailableStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfAvailableStackEntry SYNTAX SEQUENCE OF IfAvailableStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table, modeled after ifStackTable from [IF-MIB], "This table, modeled after ifStackTable from IF-MIB,
contains information on the possible 'on-top-of' contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships in interfaces (as opposed to actual relationships in
ifStackTable). In particular, it contains information on ifStackTable). In particular, it contains information on
which PCS ports (sublayers) can possibly run 'on top of' which PCS ports (sublayers) can possibly run 'on top of'
which PMEs (sublayers), as determined by cross-connect which PMEs (sublayers), as determined by cross-connect
capability of the EFMCu device, where each sub-layer capability of the EFMCu device, where each sub-layer
corresponds to a conceptual row in the ifTable. For example, corresponds to a conceptual row in the ifTable. For example,
when the PCS port with ifIndex value x can be connected when the PCS port with ifIndex value x can be connected
to run on top of the PME with ifIndex value y, then this table to run on top of the PME with ifIndex value y, then this table
skipping to change at page 60, line 14 skipping to change at page 68, line 21
ifAvailableStackStatus.x.y=capable ifAvailableStackStatus.x.y=capable
Note that there's always at least on PCS for each PME and at Note that there's always at least on PCS for each PME and at
least one PME for each PCS in the EFMCu devices, with least one PME for each PCS in the EFMCu devices, with
efmCuPAFCapacity and efmCuPeerPAFCapacity indicating efmCuPAFCapacity and efmCuPeerPAFCapacity indicating
maximum number of PMEs which can be aggregated by local and maximum number of PMEs which can be aggregated by local and
remote PCS port respectively. remote PCS port respectively.
This table is read only as it describes device capability" This table is read only as it describes device capability"
REFERENCE REFERENCE
"ifStackTable of RFC 2863" "IF-MIB, ifStackTable"
::= { efmCuObjects 3 } ::= { efmCuObjects 3 }
ifAvailableStackEntry OBJECT-TYPE ifAvailableStackEntry OBJECT-TYPE
SYNTAX IfAvailableStackEntry SYNTAX IfAvailableStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular relationship between two "Information on a particular relationship between two
sub-layers, specifying that one sub-layer (PCS) runs on 'top' sub-layers, specifying that one sub-layer (PCS) runs on 'top'
of the other sub-layer (PME). Each sub-layer corresponds to a of the other sub-layer (PME). Each sub-layer corresponds to a
skipping to change at page 62, line 16 skipping to change at page 70, line 23
efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }
-- Object Groups -- Object Groups
efmCuBasicGroup OBJECT-GROUP efmCuBasicGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPAFSupported, efmCuPAFSupported,
efmCuAdminProfile, efmCuAdminProfile,
efmCuTargetDataRate, efmCuTargetDataRate,
efmCuTargetSnrMgn, efmCuTargetSnrMgn,
efmCuAdaptiveSpectra,
efmCuPortSide, efmCuPortSide,
efmCuFltStatus efmCuFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for all of EFMCu ports." "A collection of objects required for all of EFMCu ports."
::= { efmCuGroups 1 } ::= { efmCuGroups 1 }
efmCuPAFGroup OBJECT-GROUP efmCuPAFGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 62, line 37 skipping to change at page 70, line 45
efmCuPAFCapacity, efmCuPAFCapacity,
efmCuPeerPAFCapacity, efmCuPeerPAFCapacity,
efmCuPAFAdminState, efmCuPAFAdminState,
efmCuPAFDiscoveryCode, efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs, efmCuNumPMEs,
ifAvailableStackStatus ifAvailableStackStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for optional PME "A collection of objects required for OPTIONAL PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports." Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 } ::= { efmCuGroups 2 }
ifStackCapabilityGroup OBJECT-GROUP ifStackCapabilityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ifAvailableStackStatus ifAvailableStackStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information on "A collection of objects providing information on
skipping to change at page 63, line 16 skipping to change at page 71, line 25
efmCuPAFInSmallFragments, efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments, efmCuPAFInLargeFragments,
efmCuPAFInBadFragments, efmCuPAFInBadFragments,
efmCuPAFInLostFragments, efmCuPAFInLostFragments,
efmCuPAFInLostStarts, efmCuPAFInLostStarts,
efmCuPAFInLostEnds, efmCuPAFInLostEnds,
efmCuPAFInOverflows efmCuPAFInOverflows
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting optional error counters "A collection of objects supporting OPTIONAL error counters
of PAF on EFMCu ports." of PAF on EFMCu ports."
::= { efmCuGroups 4 } ::= { efmCuGroups 4 }
efmCuPmeGroup OBJECT-GROUP efmCuPmeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPmeAdminProfile, efmCuPmeAdminProfile,
efmCuPmeOperStatus, efmCuPmeOperStatus,
efmCuPmeFltStatus, efmCuPmeFltStatus,
efmCuPmeSubTypesSupported, efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType, efmCuPmeAdminSubType,
efmCuPmeOperSubType, efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuPmeOperProfile, efmCuPmeOperProfile,
efmCuPmeSnrMgn, efmCuPmeSnrMgn,
efmCuPmePeerSnrMgn, efmCuPmePeerSnrMgn,
efmCuPmeLineAtn, efmCuPmeLineAtn,
efmCuPmePeerLineAtn, efmCuPmePeerLineAtn,
efmCuPmeEquivalentLength,
efmCuPmeTCCodingErrors, efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors, efmCuPmeTCCrcErrors,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
a 2BASE-TL/10PASS-TS PME." a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 5 } ::= { efmCuGroups 5 }
efmCuAlarmConfGroup OBJECT-GROUP efmCuAlarmConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuThreshLowBandwidth, efmCuThreshLowRate,
efmCuLowBandwidthEnable, efmCuLowRateCrossingEnable,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeLineAtnCrossingEnable, efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn, efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable, efmCuPmeSnrMgnCrossingEnable,
efmCuPmeLineAtnCrossingEnable,
efmCuPmeDeviceFaultEnable, efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable, efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable efmCuPmeProtocolInitFailEnable
-- efmCuPmeThreshES,
-- efmCuPmethreshSES,
-- efmCuPmeThreshCRCanomalies,
-- efmCuPmeThreshLOSWS,
-- efmCuPmeThreshUAS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for configuration of alarm "A collection of objects required for configuration of alarm
thresholds and notifications in EFMCu ports." thresholds and notifications in EFMCu ports."
::= { efmCuGroups 6 } ::= { efmCuGroups 6 }
efmCuNotificationGroup NOTIFICATION-GROUP efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
efmCuLowBandwidth, efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing, efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing, efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault, efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure, efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure efmCuPmeProtocolInitFailure
-- efmCuPmePerfES,
-- efmCuPmePerfSES,
-- efmCuPmePerfCRCanomalies,
-- efmCuPmePerfLOSWS,
-- efmCuPmePerfUAS,
-- efmCuPmeDeviceFault, -- efmCuPmeDeviceFault,
-- efmCuPmeLocalPowerLoss -- efmCuPmeLocalPowerLoss
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant conditions "This group supports notifications of significant conditions
associated with EFMCu ports." associated with EFMCu ports."
::= { efmCuGroups 7 } ::= { efmCuGroups 7 }
efmCuPme2BProfileGroup OBJECT-GROUP efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme2BProfileDescr, efmCuPme2BProfileDescr,
efmCuPme2BRegion, efmCuPme2BRegion,
efmCuPme2BDataRate, efmCuPme2BsMode,
efmCuPme2BMinDataRate,
efmCuPme2BMaxDataRate,
efmCuPme2BPower, efmCuPme2BPower,
efmCuPme2BConstellation, efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus efmCuPme2BProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 2BASE-TL ports." profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 8 } ::= { efmCuGroups 8 }
skipping to change at page 65, line 28 skipping to change at page 73, line 29
efmCuPme10PProfileRowStatus efmCuPme10PProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 10PASS-TS ports." profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 9 } ::= { efmCuGroups 9 }
efmCuPme10PStatusGroup OBJECT-GROUP efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme10PElectricalLength,
efmCuPme10PFECCorrectedBlocks, efmCuPme10PFECCorrectedBlocks,
efmCuPme10PFECUncorrectedBlocks efmCuPme10PFECUncorrectedBlocks
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing status information "A collection of objects providing status information
specific to 10PASS-TS PMEs." specific to 10PASS-TS PMEs."
::= { efmCuGroups 10 } ::= { efmCuGroups 10 }
-- Compliance Statements -- Compliance Statements
efmCuCompliance MODULE-COMPLIANCE efmCuCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for 2BASE-TL/10PASS-TS interfaces. "The compliance statement for 2BASE-TL/10PASS-TS interfaces.
Compliance with the following external compliance statements Compliance with the following external compliance statements
is prerequisite: is REQUIRED:
MIB Module Compliance Statement MIB Module Compliance Statement
---------- -------------------- ---------- --------------------
IF-MIB ifCompliance3 IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance IF-INVERTED-STACK-MIB ifInvCompliance
EtherLike-MIB dot3Compliance2 EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3" MAU-MIB mauModIfCompl3"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
skipping to change at page 66, line 31 skipping to change at page 74, line 31
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting 10PASS-TS Phy." supporting 10PASS-TS Phy."
GROUP efmCuPAFGroup GROUP efmCuPAFGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for "Support for this group is only required for
implementations supporting PME Aggregation Function (PAF)." implementations supporting PME Aggregation Function (PAF)."
GROUP ifStackCapabilityGroup GROUP ifStackCapabilityGroup
DESCRIPTION DESCRIPTION
"Support for this group is optional for implementations "Support for this group is OPTIONAL for implementations
supporting layered interfaces architecture with supporting layered interfaces architecture with
flexible cross-connect between the layers." flexible cross-connect between the layers."
GROUP efmCuPAFErrorsGroup GROUP efmCuPAFErrorsGroup
DESCRIPTION DESCRIPTION
"Support for this group is optional for implementations "Support for this group is OPTIONAL for implementations
supporting PME Aggregation Function (PAF)." supporting PME Aggregation Function (PAF)."
GROUP efmCuPme10PStatusGroup GROUP efmCuPme10PStatusGroup
DESCRIPTION DESCRIPTION
"Support for this group is optional for implementations "Support for this group is OPTIONAL for implementations
supporting 10PASS-TS Phy." supporting 10PASS-TS Phy."
OBJECT efmCuPmeSubTypesSupported OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS { SYNTAX BITS {
ieee2BaseTLO(0), ieee2BaseTLO(0),
ieee2BaseTLR(1), ieee2BaseTLR(1),
ieee10PassTSO(2), ieee10PassTSO(2),
ieee10PassTSR(3) ieee10PassTSR(3)
} }
DESCRIPTION DESCRIPTION
skipping to change at page 67, line 19 skipping to change at page 75, line 19
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required (needed only for PMEs "Write access is not required (needed only for PMEs
supporting more than a single subtype, e.g. supporting more than a single subtype, e.g.
ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and
ieee10PassTSR)" ieee10PassTSR)"
OBJECT efmCuTargetSnrMgn OBJECT efmCuTargetSnrMgn
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is optional. For PHYs without write access "Write access is OPTIONAL. For PHYs without write access
the target SNR margin SHALL be fixed at 5dB for 2BASE-TL the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
and 6dB for 10PASS-TS." and 6dB for 10PASS-TS."
-- EdNote: To be Continued OBJECT efmCuAdaptiveSpectra
MIN-ACCESS read-only
DESCRIPTION
"Write access is OPTIONAL. For PHYs without write access
the default value SHOULD be false."
::= { efmCuCompliances 1 } ::= { efmCuCompliances 1 }
END END
6. Security Considerations 6. Security Considerations
There is a number of managed objects defined in this MIB module that There is a number of managed objects defined in this MIB module that
have a MAX-ACCESS clause of read-write or read-create. Most objects have a MAX-ACCESS clause of read-write or read-create. Most objects
are writeable only when the link is Down. Writing to these objects are writeable only when the link is Down. Writing to these objects
can have potentially disruptive effects on network operation, for can have potentially disruptive effects on network operation, for
skipping to change at page 69, line 11 skipping to change at page 77, line 14
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
The two new values of dot3MauType (dot3MauType2BaseTL and The two new values of dot3MauType (dot3MauType2BaseTL and
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit
definitions (b2BaseTL and b10PassTS) SHALL be defined by the IANA in definitions (b2BaseTL and b10PassTS), as well as the new values for
the IANA-MAU-TC-MIB module (see [I-D.ietf-hubmib-rfc3636bis]) before IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined
this document is published as an RFC. by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib-
rfc3636bis]) before this document is published as an RFC.
8. Acknowledgments 8. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Dan Romascanu Dan Romascanu
Marina Popilov
Mathias Riess Mathias Riess
Matt Squire Matt Squire
Mike Heard Mike Heard
Udi Ashkenazi Udi Ashkenazi
9. References 9. References
9.1. Normative References 9.1. Normative References
[802.3] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications", IEEE Std 802.3-2005, December 2005.
[802.3ah] IEEE, "IEEE Standard for Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications - Amendment: Media Access Control Layer Specifications - Amendment: Media Access Control
Parameters, Physical Layers and Management Parameters for Parameters, Physical Layers and Management Parameters for
Subscriber Access Networks", IEEE Std 802.3ah-2004, Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004. September 2004.
skipping to change at page 70, line 22 skipping to change at page 78, line 35
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[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.
9.2. Informative References 9.2. Informative References
[ANFP] Network Interoperability Consultative Committee (NICC),
"Specification of the Access Network Frequency Plan (ANFP)
applicable to transmission systems used on the BT Access
Network", NICC Document ND1602:2005/08, August 2005.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2, (SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003. December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line [G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004. transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-adslmib-gshdslbis]
Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for G.shdsl.bis Lines",
draft-ietf-adslmib-gshdslbis-11 (work in progress),
May 2005.
[I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects for the Ethernet Passive Khermosh, L., "Managed Objects of EPON",
Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work draft-ietf-hubmib-efm-epon-mib-04 (work in progress),
in progress), March 2005. February 2006.
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Ethernet in the First Mile (EFM) Common MIB", Squire, M., "Definitions and Managed Objects for OAM
draft-ietf-hubmib-efm-mib-03 (work in progress), Functions on Ethernet Like Interfaces",
March 2005. draft-ietf-hubmib-efm-mib-04 (work in progress),
March 2006.
[I-D.ietf-hubmib-rfc3636bis] [I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3 Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-02 (work in progress), draft-ietf-hubmib-rfc3636bis-03 (work in progress),
October 2005. June 2006.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
skipping to change at page 72, line 5 skipping to change at page 79, line 37
June 2000. June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line (VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", RFC 4070, May 2005. Coding", RFC 4070, May 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
Email: edward.beili@actelis.com Email: edward.beili@actelis.com
skipping to change at page 73, line 41 skipping to change at page 81, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 153 change blocks. 
276 lines changed or deleted 674 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/