draft-ietf-hubmib-efm-cu-mib-08.txt   rfc5066.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Request for Comments: 5066 Actelis Networks
Intended status: Standards Track July 29, 2007 Category: Standards Track November 2007
Expires: January 30, 2008
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-08.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 30, 2008.
Copyright Notice Status of This Memo
Copyright (C) The IETF Trust (2007). This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract Abstract
This document defines Management Information Base (MIB) modules for This document defines Management Information Base (MIB) modules for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP-based internets.
This document describes extensions to the Ethernet-like Interfaces This document describes extensions to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing Ethernet MIB and Medium Attachment Unit (MAU) MIB modules with a set of
in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, objects for managing Ethernet in the First Mile Copper (EFMCu)
defined in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has interfaces 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3ah-2004
been integrated into IEEE Std 802.3-2005). In addition a set of (note: IEEE Std 802.3ah-2004 has been integrated into IEEE Std 802.3-
objects is defined, describing cross-connect capability of a managed 2005). In addition, a set of objects is defined, describing cross-
device with multi-layer (stacked) interfaces, extending the stack connect capability of a managed device with multi-layer (stacked)
management objects in the Interfaces Group MIB and the Inverted Stack interfaces, extending the stack management objects in the Interfaces
Table MIB modules. Group MIB and the Inverted Stack Table MIB modules.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 3. Relation to Other MIB Modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4 3.1. Relation to Interfaces Group MIB Module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 9 3.1.4. EFMCu Ports Initialization . . . . . . . . . . . . . . 9
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 11 3.2. Relation to SHDSL MIB Module . . . . . . . . . . . . . . . 11
3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 11 3.3. Relation to VDSL MIB Module . . . . . . . . . . . . . . . 12
3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 12 3.4. Relation to Ethernet-Like and MAU MIB Modules . . . . . . 12
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13 4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13
4.2. Interface stack capability MIB Overview . . . . . . . . . 13 4.2. Interface Stack Capability MIB Overview . . . . . . . . . 13
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14 4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22 6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 84 7. Security Considerations . . . . . . . . . . . . . . . . . . . 84
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 86
10.1. Normative References . . . . . . . . . . . . . . . . . . . 87 10.1. Normative References . . . . . . . . . . . . . . . . . . . 86
10.2. Informative References . . . . . . . . . . . . . . . . . . 88 10.2. Informative References . . . . . . . . . . . . . . . . . . 88
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 89
Intellectual Property and Copyright Statements . . . . . . . . . . 90
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), which is now a [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 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 EFM Copper reach, respectively. These interfaces, collectively called EFM
(EFMCu), are based on Single-pair High-speed Digital Subscriber Line Copper (EFMCu), are based on Single-pair High-speed Digital
(SHDSL) [G.991.2] and Very High speed Digital Subscriber Line (VDSL) Subscriber Line (SHDSL) [G.991.2] and Very High speed Digital
[G.993.1] technology, supporting optional Physical Medium Entity Subscriber Line (VDSL) [G.993.1] technology, supporting optional
(PME) aggregation (a.k.a. multi-pair bonding) with variable rates. Physical Medium Entity (PME) aggregation (a.k.a. multi-pair bonding)
with variable rates.
2BASE-TL PHY is capable of providing at least 2Mbps over a 2700 m 2BASE-TL PHY is capable of providing at least 2Mbps over a 2700 m
long single copper pair with a mean Bit Error Rate (BER) of 10^-7 long single copper pair with a mean Bit Error Rate (BER) of 10^-7
(using 5dB target noise margin). (using 5dB target noise margin).
10PASS-TS PHY is capable of providing at least 10Mbps over a 750 m 10PASS-TS PHY is capable of providing at least 10Mbps over a 750 m
long single copper pair with a mean BER of 10^-7 (using 6dB target long single copper pair with a mean BER of 10^-7 (using 6dB target
noise margin). noise margin).
This memo defines a Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community to manage with network management protocols in the Internet community to manage
EFMCu interfaces. In addition a MIB module is defined describing the EFMCu interfaces. In addition, a MIB module is defined describing
cross-connect capability of a stacked interface. the cross-connect capability of a stacked interface.
Note that managed objects for Operation, Administration and Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON) Maintenance (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [RFC4878] and clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [RFC4878] and
EFM-EPON-MIB [RFC4837] respectively. EFM-EPON-MIB [RFC4837], respectively.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies MIB Structure of Management Information (SMI). This memo specifies MIB
modules that are compliant to the SMIv2, which is described in STD modules that are compliant to the SMIv2, which is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
2580 [RFC2580]. 2580 [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Relation to other MIB modules 3. Relation to Other MIB Modules
This section outlines the relationship of the MIB modules defined in This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs. this document with other MIB modules described in the relevant RFCs.
Specifically, the Interfaces Group MIB (IF-MIB), Ethernet-Like Specifically, the Interfaces Group MIB (IF-MIB), Ethernet-Like
(EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB), and
(VDSL-LINE-EXT-MCM-MIB) modules are discussed. VDSL (VDSL-LINE-EXT-MCM-MIB) modules are discussed.
3.1. Relation to Interfaces Group MIB module 3.1. Relation to Interfaces Group MIB Module
2BASE-TL and 10PASS-TS PHY's specified in the EFM-CU-MIB module are 2BASE-TL and 10PASS-TS PHYs specified in the EFM-CU-MIB module are
stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such
are managed using generic interface management objects defined in the are managed using generic interface management objects defined in the
IF-MIB [RFC2863]. IF-MIB [RFC2863].
The stack management, i.e. actual connection of the sub-layers to the The stack management (i.e., actual connection of the sub-layers to
top layer interface, is done via the ifStackTable, as defined in the the top-layer interface) is done via the ifStackTable, as defined in
IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the the IF-MIB [RFC2863], and its inverse ifInvStackTable, as defined in
IF-INVERTED-STACK-MIB [RFC2864]. the IF-INVERTED-STACK-MIB [RFC2864].
The new tables ifCapStackTable and its inverse ifInvCapStackTable The new tables ifCapStackTable and its inverse ifInvCapStackTable
defined in the IF-CAP-STACK-MIB module below, extend the stack defined in the IF-CAP-STACK-MIB module below, extend the stack
management with an ability to describe possible connections or cross- management with an ability to describe possible connections or cross-
connect capability, when a flexible cross-connect matrix is present connect capability, when a flexible cross-connect matrix is present
between the interface layers. between the interface layers.
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 the 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, each connected to a MAC via a Medium Independent (PCS) ports, each connected to a Media Access Controller (MAC) via a
Interface (MII) at the upper layer, and cross-connected to a number Medium Independent Interface (MII) at the upper layer, and cross-
of underlying PMEs, with a single PCS per PME relationship, see connected to a number of underlying PMEs, with a single PCS per PME
clause 61.1 of [802.3ah] for more details. relationship. See clause 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 interface with ifType of shdsl(169) for table (ifTable) as a separate interface 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). A active PME (e.g., for 2BaseTL PMEs it is a multiple of 64 Kbps). A
zero value SHALL be returned when the PME is initializing or down. zero value SHALL be returned when the 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/65-octet
encapsulation overhead and PAF overhead, but accounting for the encapsulation overhead and PAF overhead, but accounting for the
Inter-Frame Gaps (IFG). Inter-Frame Gaps (IFGs).
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 aggregated, to achieve the shown speed): 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|
skipping to change at page 6, line 39 skipping to change at page 6, line 39
The ifStackTable is indexed by the ifIndex values of the aggregated The ifStackTable is indexed by the ifIndex values of the aggregated
EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a
Network Management application to determine which PMEs are connected Network Management application to determine which PMEs are connected
to a particular PCS and change connections (if supported by the to a particular PCS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME. determine which PCS runs on top of a particular PME.
A new table ifCapStackTable defined in the IF-CAP-STACK-MIB module, A new table ifCapStackTable, defined in the IF-CAP-STACK-MIB module,
specifies for each higher-layer interface (e.g. PCS port) a list of specifies for each higher-layer interface (e.g., PCS port) a list of
lower-layer interfaces (e.g. PMEs), which can possibly be cross- lower-layer interfaces (e.g., PMEs), which can possibly be cross-
connected to that higher-layer interface, determined by the cross- connected to that higher-layer interface, determined by the cross-
connect capability of the device. This table, modeled after connect capability of the device. This table, modeled after
ifStackTable, is read-only, reflecting current cross-connect ifStackTable, is read-only, reflecting current cross-connect
capability of a stacked interface, which can be dynamic in some capability of stacked interface, which can be dynamic in some
implementations (e.g. if PMEs are located on a pluggable module and implementations (e.g., if PMEs are located on a pluggable module and
the module is pulled out). Note that PME availability per PCS, the module is pulled out). Note that PME availability per PCS,
described by ifCapStackTable, can be constrained by other parameters, described by ifCapStackTable, can be constrained by other parameters,
for example by aggregation capacity of a PCS or by the PME in for example, by aggregation capacity of a PCS or by the PME in
question being already connected to another PCS. So, in order to question being already connected to another PCS. So, in order to
ensure that a particular PME can be connected to the PCS, all ensure that a particular PME can be connected to the PCS, all
respective parameters (e.g. ifCapStackTable, ifStackTable and respective parameters (e.g., ifCapStackTable, ifStackTable, and
efmCuPAFCapacity) SHALL be inspected. efmCuPAFCapacity) SHALL be inspected.
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
describes which higher-layer interfaces (e.g. PCS ports) can describes which higher-layer interfaces (e.g., PCS ports) can
possibly be connected to a particular lower-layer interface (e.g. possibly be connected to a particular lower-layer interface (e.g.,
PME), providing an inverted mapping of the ifCapStackTable. While it PME), providing an inverted mapping of the ifCapStackTable. While it
contains no additional information beyond that already contained in contains no additional information beyond that already contained in
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface. connected to run on top of a particular interface.
3.1.2. PME Aggregation Function (PAF) 3.1.2. PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) allows a number of PMEs to be The PME Aggregation Function (PAF) allows a number of PMEs to be
aggregated onto a PCS port, by fragmenting the Ethernet frames, aggregated onto a PCS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple PMEs and assembling the transmitting the fragments over multiple PMEs, and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS). (2BASE-TL and 10PASS-TS).
The EFM-CU-MIB module allows a Network Management application to The EFM-CU-MIB module allows a Network Management application to
query the PAF capability and enable/disable it if supported. Note query the PAF capability and enable/disable it if supported. Note
that enabling PAF effectively turns on fragmentation and re-assembly, that enabling PAF effectively turns on fragmentation and re-assembly,
even on a single-PME port. even on a single-PME port.
skipping to change at page 7, line 51 skipping to change at page 8, line 7
of the local PMEs into aggregation groups instead of a fixed pre- of the local PMEs into aggregation groups instead of a fixed pre-
configuration. configuration.
The MIB modules defined in this document allow a Network Management The MIB modules defined in this document allow a Network Management
application to control the EFM Discovery mechanism and query its application to control the EFM Discovery mechanism and query its
results. Note that the Discovery mechanism can work only if PAF is results. Note that the Discovery mechanism can work only if PAF is
supported and enabled. supported and enabled.
Two tables are used by the EFM Discovery mechanism: ifStackTable and Two tables are used by the EFM Discovery mechanism: ifStackTable and
ifCapStackTable. The following pseudo-code gives an example of the ifCapStackTable. The following pseudo-code gives an example of the
Discovery and automatic PME assignment for a generic PAF enabled Discovery and automatic PME assignment for a generic PAF-enabled
multi-PCS EFMCu device, located at Central Office (CO), using objects multi-PCS EFMCu device, located at Central Office (CO), using objects
defined in these MIB modules and in the IF-MIB [Note that automatic defined in these MIB modules and in the IF-MIB (Note that automatic
PME assignment is only shown here for the purposes of the example. PME assignment is only shown here for the purposes of the example.
Fixed PME pre-assignment, manual assignment or auto-assignment using Fixed PME pre-assignment, manual assignment, or auto-assignment using
an alternative internal algorithm may be chosen by a particular an alternative internal algorithm may be chosen by a particular
implementation]: implementation):
// Go over all PCS ports in the CO device // Go over all PCS ports in the CO device
FOREACH pcs[i] IN CO_device FOREACH pcs[i] IN CO_device
{ // Perform discovery and auto-assignment only on PAF enabled ports { // Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs // with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity )
{ // Assign a unique 6-octets local discovery code to the PCS { // Assign a unique 6-octet local discovery code to the PCS
// e.g. MAC address // e.g., MAC address
dc = pcs[i].DiscoveryCode = MAC[i]; dc = pcs[i].DiscoveryCode = MAC[i];
// Go over all disconnected PMEs, which can // Go over all disconnected PMEs, which can
// potentially be connected to the PCS // potentially be connected to the PCS
FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]] // not connected NOT IN ifStackTable[pcs[i]] // not connected
{ // Try to grab the remote RT_device, by writing the value { // Try to grab the remote RT_device, by writing the value
// of the local 6-octet discovery code to the remote // of the local 6-octet discovery code to the remote
// discovery code register (via handshake mechanism). // discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it // This operation is atomic Set-if-Clear action, i.e., it
// would succeed only if the remote discovery register was // would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get // zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME // operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer. // is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = pme[j].RemoteDiscoveryCode; // Get r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote RT_device connected via PME[j] is/was a peer { // Remote RT_device connected via PME[j] is/was a peer
// for PCS[i] and there is room for another PME in the // for PCS[i] and there is room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not // PCS[i] aggregation group (max. PAF capacity is not
// reached yet). // reached yet).
// Connect this PME to the PCS (via ifStackTable, // Connect this PME to the PCS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is // ifInvStackTable being inverse of ifStackTable is
// updated automatically, i.e. pcs[i] is auto-added // updated automatically, i.e., pcs[i] is auto-added
// to ifInvStackTable[pme[j]]) // to ifInvStackTable[pme[j]])
ADD pme[j] TO ifStackTable[pcs[i]]; ADD pme[j] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other disconnected PMEs, // Discover all other disconnected PMEs,
// attached to the same RT_device and connect them to // attached to the same RT_device and connect them to
// the PCS provided there is enough room for more PMEs. // the PCS provided there is enough room for more PMEs.
FOREACH pme[k] IN ifCapStackTable[pcs[i]] AND FOREACH pme[k] IN ifCapStackTable[pcs[i]] AND
NOT IN ifStackTable[pcs[i]] NOT IN ifStackTable[pcs[i]]
{ // Get Remote Discovery Code from the PME to see if { // Get Remote Discovery Code from the PME to see if
// it belongs to a connected RT_device "grabbed" by // it belongs to a connected RT_device "grabbed" by
skipping to change at page 9, line 27 skipping to change at page 9, line 29
BREAK; BREAK;
} }
} }
} }
An SNMP Agent for an EFMCu device builds the ifCapStackTable and its An SNMP Agent for an EFMCu device builds the ifCapStackTable and its
inverse ifInvCapStackTable according to the information contained in inverse ifInvCapStackTable according to the information contained in
the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and
45.2.3.20). 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 the PCS port does not have to be operationally 'down' for Note that the PCS port does not have to be operationally 'down' for
the connection to succeed. In fact, a dynamic PME addition (and the connection to succeed. In fact, a dynamic PME addition (and
removal) MAY be implemented with an available PME being initialized removal) MAY be implemented with an available PME being initialized
first (by setting its ifAdminStatus to 'up') and then added to an first (by setting its ifAdminStatus to 'up') and then added to an
operationally 'up' PCS port, by modifying a respective ifStackTable operationally 'up' PCS port, by modifying a respective ifStackTable
(and respective ifInvStackTable) entry. (and respective ifInvStackTable) 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 the required data rate on a particular cooperatively to achieve the required data rate on a particular
copper pair. Sometimes, when the copper line is too long or the copper pair. Sometimes, when the copper line is too long or the
noise on the line is too high, that 'training' process may fail to noise on the line is too high, that 'training' process may fail to
achieve a specific target rate with required characteristics. achieve a 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 with all the PMEs connected to it or of an individual PME of a PCS with all the PMEs connected to it or of an individual PME
port. Setting this object to 'up' instructs a particular PCS or PME port. Setting this object to 'up' instructs a particular PCS or PME
to start the initialization process, which may take tens of seconds to start the initialization process, which may take tens of seconds
for EFMCu ports, especially if PAF is involved. The ifOperStatus for EFMCu ports, especially if PAF is involved. The ifOperStatus
skipping to change at page 10, line 21 skipping to change at page 10, line 24
ifMauMediaAvailable object from MAU-MIB for PCS and ifMauMediaAvailable object from MAU-MIB for PCS and
efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME
interfaces). 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
PCS/PME interface SHALL remain operationally 'down' during PCS/PME interface SHALL remain operationally 'down' during
initialization. initialization.
The efmCuPmeOperStatus defined in the EFM-CU-MIB module expands PME's The efmCuPmeOperStatus defined in the EFM-CU-MIB module expands PME's
ifOperStatus value of 'down' to 'downReady', 'downNotReady' and ifOperStatus value of 'down' to 'downReady', 'downNotReady', and
'init' values, indicating various EFMCu PME specific states. 'init' values, indicating various EFMCu PME-specific states.
3.1.5. Usage of ifTable 3.1.5. Usage of ifTable
Both PME and PCS interfaces of the EFMCu PHY are managed using Both PME and PCS interfaces of the EFMCu PHY are managed using
interface specific management objects defined in the EFM-CU-MIB interface-specific management objects defined in the EFM-CU-MIB
module and generic interface objects from the ifTable of IF-MIB, with module and generic interface objects from the ifTable of IF-MIB, with
all management table entries referenced by the interface index all management table entries referenced by the interface index
ifIndex. ifIndex.
The following table summarizes EFMCu specific interpretations for The following table summarizes EFMCu-specific interpretations for
some of the ifTable objects specified in the mandatory some of the ifTable objects specified in the mandatory
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation | | IF-MIB object | EFMCu interpretation |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| 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 are some PCS and PME specific attributes | | | there are 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/65-octet encapsulation overhead and PAF |
| | but accounting for the Inter-Frame Gaps (IFG) | | | overhead, but accounting for the Inter-Frame Gaps |
| | (IFGs). |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| 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: EFMCu interpretation of IF-MIB objects Table 1: EFMCu interpretation of IF-MIB objects
3.2. Relation to SHDSL MIB module 3.2. Relation to SHDSL MIB Module
G.SHDSL.bis modems, similar to PMEs comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PMEs comprising a 2BASE-TL port, are
described in the HDSL2-SHDSL-LINE-MIB module [RFC4319]. Note that described in the HDSL2-SHDSL-LINE-MIB module [RFC4319]. Note that
not all attributes of G.SHDSL modems reflected in the HDSL2-SHDSL- not all attributes of G.SHDSL modems reflected in the HDSL2-SHDSL-
LINE-MIB module have adequate management objects (Clause 30 LINE-MIB module have adequate management objects (Clause 30
attributes and Clause 45 registers) in the EFM standard. attributes and Clause 45 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
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the
objects in the EFM-CU-MIB module. relevant objects in the EFM-CU-MIB module.
However, if some functionality not available in the EFM-CU-MIB module However, if some functionality not available in the EFM-CU-MIB module
is required and supported by the PME, e.g. performance monitoring, is required and supported by the PME, e.g., performance monitoring,
relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and applied 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 modems, similar to the PME(s) comprising a 10PASS-TS port, are VDSL modems, similar to the PME(s) comprising a 10PASS-TS port, are
described in the VDSL-LINE-EXT-MCM-MIB module [RFC4070]. Note that described in the VDSL-LINE-EXT-MCM-MIB module [RFC4070]. Note that
not all attributes of VDSL modems reflected in the VDSL-LINE-EXT-MCM- not all attributes of VDSL modems reflected in the VDSL-LINE-EXT-MCM-
MIB module have adequate management objects (Clause 30 attributes and MIB module have adequate management objects (Clause 30 attributes and
Clause 45 registers) in the EFM standard. Clause 45 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, it was decided not to reference VDSL-LINE-EXT- and name consistency, it was decided not to reference VDSL-LINE-EXT-
MCM-MIB objects, but define all the relevant objects in the EFM-CU- MCM-MIB objects, but define all the relevant objects in the EFM-CU-
MIB module. MIB module.
However, if some functionality not available in the EFM-CU-MIB module However, if some functionality not available in the EFM-CU-MIB module
is required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB is 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 the EtherLike-MIB [RFC3635] and MAU-MIB The implementation of the EtherLike-MIB [RFC3635] and MAU-MIB
[RFC4836] modules is REQUIRED for EFMCu interfaces. [RFC4836] modules is REQUIRED for 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-MIB module (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB module
[RFC4836] for EFMCu MAUs: [RFC4836] for 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, the IANA-MAU-MIB module defines two new values of Additionally, the IANA-MAU-MIB module defines two new values of
ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable ifMauMediaAvailable, specifically for EFMCu ports: availableReduced
- availableReduced and ready, specifically for EFMCu ports. Due to and ready (in textual convention IANAifMauMediaAvailable). Due to
the PME aggregation, the EFMCu interpretation of some possible the PME aggregation, the EFMCu interpretation of some possible
ifMauMediaAvailable values differs from other MAUs as follows: ifMauMediaAvailable values differs from other MAUs as follows:
o unknown - the EFMCu interface (PCS with connected PMEs) is o unknown - the EFMCu interface (PCS with connected PMEs) is
initializing Initializing
o ready - the interface is down, at least one PME in the aggregation o ready - the interface is Down, at least one PME in the aggregation
group (all PMEs connected to the PCS) is ready for handshake group (all PMEs connected to the PCS) is ready for handshake
o available - the interface is up, all PMEs in the aggregation group o available - the interface is Up, all PMEs in the aggregation group
are up 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 notAvailable - the interface is down, all PMEs in the aggregation o availableReduced - the interface is Up, a link fault is detected
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 at the receive direction by one or more PMEs in the aggregation
group, but at least one PME is up group, but at least one PME is Up
o pmdLinkFault - a link fault is detected at the receive direction o pmdLinkFault - a link fault is detected at the receive direction
by all PMEs in the aggregation group 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
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType a consolidation of LLC, MAC, and PCS (sub)layers) SHALL return an
of ethernetCsmacd(6). While most of the MAU characteristics are not ifType of ethernetCsmacd(6). While most of the MAU characteristics
applicable to the EFMCu ports (no auto-negotiation, false carriers or are not applicable to the EFMCu ports (no auto-negotiation, false
jabber), they SHALL return an appropriate ifMauType carriers, or 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 module for the desired management software to look in the EFM-CU-MIB module 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 the EFM-CU-MIB module. efmCuOperSubType, defined in the EFM-CU-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
4.1. EFM Copper MIB Overview 4.1. EFM Copper MIB Overview
The main management objects defined in the EFM-CU-MIB module are The main management objects defined in the EFM-CU-MIB module are
split into 2 groups: split into 2 groups:
o efmCuPort - containing objects for configuration, capabilities, o efmCuPort - containing objects for configuration, capabilities,
status and notifications, common to all EFMCu PHYs. status, and notifications, common to all EFMCu PHYs.
o efmCuPme - containing objects for configuration, capabilities, o efmCuPme - containing objects for configuration, capabilities,
status and notifications of EFMCu PMEs. status, and notifications of EFMCu PMEs.
The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P
groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS groups, which define PME profiles specific to 2BASE-TL and 10PASS-TS
PMEs respectively, as well as PME specific status information. PMEs, respectively, as well as PME-specific status information.
4.2. Interface stack capability MIB Overview 4.2. Interface Stack Capability MIB Overview
The IF-CAP-STACK-MIB module contains 2 tables: The IF-CAP-STACK-MIB module contains 2 tables:
o ifCapStackTable - containing objects that define possible o ifCapStackTable - containing objects that define possible
relationships among the sub-layers of an interface with flexible relationships among the sub-layers of an interface with flexible
cross-connect (cross-connect capability). cross-connect (cross-connect capability).
o ifInvCapStackTable - an inverse of the ifCapstackTable. o ifInvCapStackTable - an inverse of the ifCapstackTable.
4.3. PME Profiles 4.3. PME Profiles
skipping to change at page 14, line 23 skipping to change at page 14, line 35
for "best-effort" provisioning of 2BASE-TL PMEs. An ability to for "best-effort" provisioning of 2BASE-TL PMEs. An ability to
define new configuration profiles is also provided to allow for EFMCu define new configuration profiles is also provided to allow for EFMCu
deployment tailored to specific copper environments and spectral deployment tailored to specific copper environments and spectral
regulations. regulations.
A specific configuration or administrative profile is assigned to a A specific configuration or administrative profile is assigned to a
specific PME via the efmCuPmeAdminProfile object. If specific PME via the efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then the efmCuAdminProfile object of efmCuPmeAdminProfile is zero, then the efmCuAdminProfile object of
the PCS port connected to the PME determines the configuration the PCS port connected to the PME determines the configuration
profile (or a list of possible profiles) for that PME. This profile (or a list of possible profiles) for that PME. This
mechanism allows to specify a common profile for all PMEs connected mechanism allows specifying a common profile for all PMEs connected
to the PCS port, with an ability to change individual PME profiles by to the PCS port, with an ability to change individual PME profiles by
setting efmCuPmeAdminProfile object, which overwrites the profile set setting efmCuPmeAdminProfile object, which overwrites the profile set
by efmCuAdminProfile. by efmCuAdminProfile.
A current operating PME profile is pointed to by *the* A current operating PME profile is pointed to by the
efmCuPmeOperProfile object. Note that this profile entry can be efmCuPmeOperProfile object. Note that this profile entry can be
created automatically to reflect achieved parameters in adaptive (not created automatically to reflect achieved parameters in adaptive (not
fixed) initialization. fixed) initialization.
4.4. Mapping of IEEE 802.3ah Managed Objects 4.4. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between relevant 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].
skipping to change at page 16, line 28 skipping to change at page 16, line 32
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 2: Mapping of IEEE 802.3 Managed Objects Table 2: Mapping of IEEE 802.3 Managed Objects
5. Interface Stack Capability MIB Definitions 5. Interface Stack Capability MIB Definitions
IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2 MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- [RFC2578]
TruthValue TruthValue
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- [RFC2580]
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- [RFC2863]
ifInvStackGroup ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- RFC 2864 FROM IF-INVERTED-STACK-MIB -- [RFC2864]
; ;
ifCapStackMIB MODULE-IDENTITY ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200707290000Z" -- July 29, 2007 LAST-UPDATED "200711070000Z" -- November 07, 2007
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/OLD/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
Chair: Bert Wijnen Chair: Bert Wijnen
Postal: Alcatel-Lucent Postal: Alcatel-Lucent
Schagen 33 Schagen 33
3461 GL Linschoten 3461 GL Linschoten
Netherlands Netherlands
Tel: +31-348-407-775 Phone: +31-348-407-775
E-mail: bwijnen@alcatel-lucent.com EMail: bwijnen@alcatel-lucent.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 Phone: +972-3-924-3491
E-mail: edward.beili@actelis.com" EMail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to describe "The objects in this MIB module are used to describe
cross-connect capabilities of stacked (layered) interfaces, cross-connect capabilities of stacked (layered) interfaces,
complementing ifStackTable and ifInvStackTable defined in complementing ifStackTable and ifInvStackTable defined in
IF-MIB and IF-INVERTED-STACK-MIB respectively. IF-MIB and IF-INVERTED-STACK-MIB, respectively.
Copyright (C) The IETF Trust (2007). This version Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC 5066; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200707290000Z" -- July 29, 2007 REVISION "200711070000Z" -- November 07, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC 5066."
-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note
::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is ::= { mib-2 166 }
-- allocated & remove this note.
-- Sections of the module -- Sections of the module
-- Structured as recommended by RFC 4181, see -- Structured as recommended by [RFC4181], see
-- Appendix D: Suggested OID Layout -- Appendix D: Suggested OID Layout
ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 } ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 } ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 }
-- Groups in the module -- Groups in the module
-- --
-- ifCapStackTable group -- ifCapStackTable group
skipping to change at page 18, line 29 skipping to change at page 18, line 26
device, where each sub-layer corresponds to a conceptual row device, where each sub-layer corresponds to a conceptual row
in the ifTable. For example, when the sub-layer with ifIndex in the ifTable. For example, when the sub-layer with ifIndex
value x can be connected to run on top of the sub-layer with value x can be connected to run on top of the sub-layer with
ifIndex value y, then this table contains: ifIndex value y, then this table contains:
ifCapStackStatus.x.y=true ifCapStackStatus.x.y=true
The ifCapStackStatus.x.y row does not exist if it is The ifCapStackStatus.x.y row does not exist if it is
impossible to connect between the sub-layers x and y. impossible to connect between the sub-layers x and y.
Note that for most stacked interfaces (e.g. 2BASE-TL) Note that for most stacked interfaces (e.g., 2BASE-TL)
there's always at least one higher-level interface (e.g. PCS there's always at least one higher-level interface (e.g., PCS
port) for each lower-level interface (e.g. PME) and at port) for each lower-level interface (e.g., PME) and at
least one lower-level interface for each higher-level least one lower-level interface for each higher-level
interface, that is, there is at least a single row with a interface, that is, there is at least a single row with a
'true' status for any such existing value of x or y. 'true' status for any such existing value of x or y.
This table is read-only as it describes device capabilities." This table is read-only as it describes device capabilities."
REFERENCE REFERENCE
"IF-MIB, ifStackTable" "IF-MIB, ifStackTable"
::= { ifCapStackObjects 1 } ::= { ifCapStackObjects 1 }
ifCapStackEntry OBJECT-TYPE ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry SYNTAX IfCapStackEntry
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 MAY possibly run sub-layers, specifying that one sub-layer MAY possibly run
on 'top' of the other sub-layer. Each sub-layer corresponds on 'top' of the other sub-layer. Each sub-layer corresponds
to a conceptual row in the ifTable (interface index for to a conceptual row in the ifTable (interface index for
lower- and higher-layer respectively)." lower and higher layer, respectively)."
INDEX { INDEX {
ifStackHigherLayer, ifStackHigherLayer,
ifStackLowerLayer ifStackLowerLayer
} }
::= { ifCapStackTable 1 } ::= { ifCapStackTable 1 }
IfCapStackEntry ::= SEQUENCE { IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus TruthValue ifCapStackStatus TruthValue
} }
skipping to change at page 19, line 27 skipping to change at page 19, line 24
DESCRIPTION DESCRIPTION
"The status of the 'cross-connect capability' relationship "The status of the 'cross-connect capability' relationship
between two sub-layers. The following values can be returned: between two sub-layers. The following values can be returned:
true(1) - indicates that the sub-layer interface, true(1) - indicates that the sub-layer interface,
identified by the ifStackLowerLayer MAY identified by the ifStackLowerLayer MAY
be connected to run 'below' the sub-layer be connected to run 'below' the sub-layer
interface, identified by the interface, identified by the
ifStackHigherLayer index. ifStackHigherLayer index.
false(2) - the sub-layer interfaces cannot be false(2) - the sub-layer interfaces cannot be
connected temporarily due to connected temporarily due to
unavailability of the interface(s), e.g. unavailability of the interface(s), e.g.,
one of the interfaces is located on an one of the interfaces is located on an
absent pluggable module. absent pluggable module.
Note that lower-layer interface availability per higher-layer, Note that lower-layer interface availability per higher-layer,
indicated by the value of 'true', can be constrained by indicated by the value of 'true', can be constrained by
other parameters, for example by the aggregation capacity of other parameters, for example, by the aggregation capacity of
a higher-layer interface or by the lower-layer interface in a higher-layer interface or by the lower-layer interface in
question being already connected to another higher-layer question being already connected to another higher-layer
interface. In order to ensure that a particular sub-layer can interface. In order to ensure that a particular sub-layer can
be connected to another sub-layer, all respective objects be connected to another sub-layer, all respective objects
(e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for (e.g., ifCapStackTable, ifStackTable, and efmCuPAFCapacity for
for EFMCu interfaces) SHALL be inspected. EFMCu interfaces) SHALL be inspected.
This object is read-only, unlike ifStackStatus, as it This object is read-only, unlike ifStackStatus, as it
describes a cross-connect capability." describes a cross-connect capability."
::= { ifCapStackEntry 1 } ::= { ifCapStackEntry 1 }
ifInvCapStackTable OBJECT-TYPE ifInvCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfInvCapStackEntry SYNTAX SEQUENCE OF IfInvCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 21, line 4 skipping to change at page 20, line 50
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the possible 'cross-connect capability' "The status of the possible 'cross-connect capability'
relationship between two sub-layers. relationship between two sub-layers.
An instance of this object exists for each instance of the An instance of this object exists for each instance of the
ifCapStackStatus object, and vice versa. For example, if the ifCapStackStatus object, and vice versa. For example, if the
variable ifCapStackStatus.H.L exists, then the variable variable ifCapStackStatus.H.L exists, then the variable
ifInvStackStatus.L.H must also exist, and vice versa. In ifInvCapStackStatus.L.H must also exist, and vice versa. In
addition, the two variables always have the same value. addition, the two variables always have the same value.
The ifInvStackStatus object is read-only, as it describes The ifInvCapStackStatus object is read-only, as it describes
a cross-connect capability." a cross-connect capability."
REFERENCE REFERENCE
"ifCapStackStatus" "ifCapStackStatus"
::= { ifInvCapStackEntry 1 } ::= { ifInvCapStackEntry 1 }
-- --
-- Conformance Statements -- Conformance Statements
-- --
ifCapStackGroups OBJECT IDENTIFIER ::= ifCapStackGroups OBJECT IDENTIFIER ::=
skipping to change at page 22, line 38 skipping to change at page 22, line 35
::= { ifCapStackCompliances 1 } ::= { ifCapStackCompliances 1 }
END END
6. EFM Copper MIB Definitions 6. EFM Copper MIB Definitions
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 -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
ifIndex, ifSpeed ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- [RFC2863]
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200707290000Z" -- July 29, 2007 LAST-UPDATED "200711140000Z" -- November 14, 2007
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/OLD/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
Chair: Bert Wijnen Chair: Bert Wijnen
Postal: Alcatel-Lucent Postal: Alcatel-Lucent
Schagen 33 Schagen 33
3461 GL Linschoten 3461 GL Linschoten
Netherlands Netherlands
Phone: +31-348-407-775 Phone: +31-348-407-775
Email: bwijnen@alcatel-lucent.com EMail: bwijnen@alcatel-lucent.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
Phone: +972-3-924-3491 Phone: +972-3-924-3491
Email: edward.beili@actelis.com" Email: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
skipping to change at page 25, line 4 skipping to change at page 24, line 48
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 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 IETF Trust (2007). This version Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC 5066; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200711140000Z" -- November 14, 2007
DESCRIPTION "Initial version, published as RFC 5066."
REVISION "200707290000Z" -- July 29, 2007 ::= { mib-2 167 }
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note
::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note.
-- Sections of the module -- Sections of the module
efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
-- Groups in the module -- Groups in the module
efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
skipping to change at page 25, line 49 skipping to change at page 25, line 39
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)
EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of EfmProfileIndex "This textual convention is an extension of the
convention. The latter defines a greater than zero value used EfmProfileIndex convention. The latter defines a greater than
to identify a PME profile in the managed EFMCu port. This zero value used to identify a PME profile in the managed EFMCu
extension permits the additional value of zero. The value of port. This extension permits the additional value of zero.
zero is object-specific and MUST therefore be defined as part The value of zero is object-specific and MUST therefore be
of the description of any object which uses this syntax. defined as part of the description of any object that uses
this syntax.
Examples of the usage of zero value might include situations Examples of the usage of zero value might include situations
where current operational profile is unknown." where the current operational profile is unknown."
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
EfmProfileIndexList ::= TEXTUAL-CONVENTION EfmProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" DISPLAY-HINT "1d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention represents a list of up to 6 "This textual convention represents a list of up to 6
EfmProfileIndex values, any of which can be chosen for EfmProfileIndex values, any of which can be chosen for
configuration of an PME in a managed EFMCu port. configuration of a PME in a managed EFMCu port.
The EfmProfileIndex textual convention defines a greater than The EfmProfileIndex textual convention defines a greater than
zero value used to identify a PME profile. zero value used to identify a PME profile.
The value of this object is a concatenation of zero or The value of this object is a concatenation of zero or
more (up to 6) octets, where each octet contains an 8-bit more (up to 6) octets, where each octet contains an 8-bit
EfmProfileIndex value. EfmProfileIndex value.
A zero-length octet string is object-specific and MUST A zero-length octet string is object-specific and MUST
therefore be defined as part of the description of any object therefore be defined as part of the description of any object
which uses this syntax. Examples of the usage of a zero-length that uses this syntax. Examples of the usage of a zero-length
value might include situations where an object using this value might include situations where an object using this
textual convention is irrelevant for a specific EFMCu port textual convention is irrelevant for a specific EFMCu port
type." type."
SYNTAX OCTET STRING (SIZE(0..6)) SYNTAX OCTET STRING (SIZE(0..6))
EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the TruthValue "This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with possible convention. The latter defines a boolean value with possible
values of true(1) and false(2). This extension permits the values of true(1) and false(2). This extension permits the
additional value of unknown(0), that can be returned as the additional value of unknown(0), which can be returned as the
result of a GET operation, when an exact true or false value result of a GET operation when an exact true or false value
of the object cannot be determined." 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 }
efmCuLowRateCrossing NOTIFICATION-TYPE efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ifSpeed, ifSpeed,
efmCuThreshLowRate efmCuThreshLowRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the EFMCu port's data rate "This notification indicates that the EFMCu port's data rate
has reached/dropped below or exceeded the low rate threshold, has reached/dropped below or exceeded the low rate threshold,
specified by efmCuThreshLowRate. specified by efmCuThreshLowRate.
This notification MAY be sent for the -O subtype ports This notification MAY be sent for the -O subtype ports
(2BaseTL-O/10PassTS-O) while the port is up, on the crossing (2BaseTL-O/10PassTS-O) while the port is Up, on the crossing
event in both directions: from normal (rate is above the event in both directions: from normal (rate is above the
threshold) to low (rate equals the threshold or below it) and threshold) to low (rate equals the threshold or below it) and
from low to normal. This notification is not applicable to from low to normal. This notification is not applicable to
the -R subtypes. the -R subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and the notification, between the detection of the condition and the notification,
is implemented to prevent simultaneous LinkUp/LinkDown and is implemented to prevent simultaneous LinkUp/LinkDown and
efmCuLowRateCrossing notifications to be sent. efmCuLowRateCrossing notifications to be sent.
The adaptive nature of the EFMCu technology allows the port to The adaptive nature of the EFMCu technology allows the port to
adapt itself to the changes in the copper environment, e.g. adapt itself to the changes in the copper environment, e.g.,
an impulse noise, alien crosstalk or a micro-interruption may an impulse noise, alien crosstalk, or a micro-interruption may
temporarily drop one or more PMEs in the aggregation group, temporarily drop one or more PMEs in the aggregation group,
causing a rate degradation of the aggregated EFMCu link. causing a rate degradation of the aggregated EFMCu link.
The dropped PMEs would then try to re-initialize, possibly at The dropped PMEs would then try to re-initialize, possibly at
a lower rate than before, adjusting the rate to provide a lower rate than before, adjusting the rate to provide
required target SNR margin. required target SNR margin.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object." 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)
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 1 } ::= { efmCuPort 1 }
efmCuPortConfEntry OBJECT-TYPE efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu Port Configuration table. "An entry in the EFMCu Port Configuration 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 }
::= { efmCuPortConfTable 1 } ::= { efmCuPortConfTable 1 }
EfmCuPortConfEntry ::= EfmCuPortConfEntry ::=
SEQUENCE { SEQUENCE {
efmCuPAFAdminState INTEGER, efmCuPAFAdminState INTEGER,
efmCuPAFDiscoveryCode PhysAddress, efmCuPAFDiscoveryCode PhysAddress,
skipping to change at page 28, line 33 skipping to change at page 28, line 23
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
"Administrative (desired) state of the PAF of the EFMCu port "Administrative (desired) state of the PAF of the EFMCu port
(PCS). (PCS).
When 'disabled', PME Aggregation will not be performed by the When 'disabled', PME aggregation will not be performed by the
PCS. No more than a single PME can be assigned to this PCS in PCS. No more than a single PME can be assigned to this PCS in
this case. this case.
When 'enabled', PAF will be performed by the PCS when the link When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported. is Up, even on a single attached PME, if PAF is supported.
PCS ports incapable of supporting PAF SHALL return a value of PCS ports incapable of supporting PAF SHALL return a value of
'disabled'. Attempts to 'enable' such ports SHALL be rejected. 'disabled'. Attempts to 'enable' such ports SHALL be
rejected.
A PAF 'enabled' port with multiple PMEs assigned cannot be A PAF 'enabled' port with multiple PMEs assigned cannot be
'disabled'. Attempts to 'disable' such port SHALL be rejected, 'disabled'. Attempts to 'disable' such port SHALL be
until at most one PME is left assigned. rejected, until at most one PME is left assigned.
Changing PAFAdminState is a traffic disruptive operation and Changing PAFAdminState is a traffic-disruptive operation and
as such SHALL be done when the link is Down. Attempts to as such SHALL be done when the link is Down. Attempts to
change this object SHALL be rejected if the link is Up or change this object SHALL be rejected if the link is Up or
Initializing. Initializing.
This object maps to the Clause 30 attribute aPAFAdminState. This object maps to the Clause 30 attribute aPAFAdminState.
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 maps to the PAF enable bit in the 10P/2B PCS control object maps to the PAF enable bit in the 10P/2B PCS control
register. register.
skipping to change at page 29, line 13 skipping to change at page 29, line 4
This object maps to the Clause 30 attribute aPAFAdminState. This object maps to the Clause 30 attribute aPAFAdminState.
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 maps to the PAF enable bit in the 10P/2B PCS control object maps to the PAF enable bit in the 10P/2B PCS control
register. register.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 45.2.3.18.3" "[802.3ah] 61.2.2, 45.2.3.18.3"
::= { efmCuPortConfEntry 1 } ::= { efmCuPortConfEntry 1 }
efmCuPAFDiscoveryCode OBJECT-TYPE efmCuPAFDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(0|6)) SYNTAX PhysAddress (SIZE(0|6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PAF Discovery Code of the EFMCu port (PCS). "PAF Discovery Code of the EFMCu port (PCS).
A unique 6 octet long code used by the Discovery function, A unique 6-octet code used by the Discovery function,
when PAF is supported. when PAF is supported.
PCS ports incapable of supporting PAF SHALL return a PCS ports incapable of supporting PAF SHALL return a
zero-length octet string on an attempt to read this object. zero-length octet string on an attempt to read this object.
An attempt to write to this object SHALL be rejected for such An attempt to write to this object SHALL be rejected for such
ports. ports.
This object MUST be instantiated for the -O subtype PCS before This object MUST be instantiated for the -O subtype PCS before
writing operations on the efmCuPAFRemoteDiscoveryCode writing operations on the efmCuPAFRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by PMEs (Set_if_Clear and Clear_if_Same) are performed by PMEs
associated with the PCS. associated with the PCS.
The initial value of this object for -R subtype ports after The initial value of this object for -R subtype ports after
skipping to change at page 29, line 43 skipping to change at page 29, line 33
as a result of writing operation on the as a result of writing operation on the
efmCuPAFRemoteDiscoveryCode object of remote PME of -O efmCuPAFRemoteDiscoveryCode object of remote PME of -O
subtype, connected to one of the local PMEs associated with subtype, connected to one of the local PMEs associated with
the PCS. the PCS.
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 (in case of Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or SNMP with the error inconsistentValue), if the link is Up or
Initializing. Initializing.
The PAF Discovery code maps to the local Discovery code The PAF Discovery Code maps to the local Discovery code
variable in PAF (note that it does not have a corresponding variable in PAF (note that it does not have a corresponding
Clause 45 register)" Clause 45 register)."
REFERENCE REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
61A.2" 61A.2"
::= { efmCuPortConfEntry 2 } ::= { efmCuPortConfEntry 2 }
efmCuAdminProfile OBJECT-TYPE efmCuAdminProfile OBJECT-TYPE
SYNTAX EfmProfileIndexList SYNTAX EfmProfileIndexList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 30, line 23 skipping to change at page 30, line 15
The value of this object is a list of up to 6 indices of The value of this object is a list of up to 6 indices of
profiles. If this list consists of a single profile index, profiles. If this list consists of a single profile index,
then all PMEs assigned to this EFMCu port SHALL be configured then all PMEs assigned to this EFMCu port SHALL be configured
according to the profile referenced by that index, unless it according to the profile referenced by that index, unless it
is overwritten by a corresponding non-zero is overwritten by a corresponding non-zero
efmCuPmeAdminProfile instance, which takes precedence over efmCuPmeAdminProfile instance, which takes precedence over
efmCuAdminProfile. efmCuAdminProfile.
A list consisting of more than one index allows each PME A list consisting of more than one index allows each PME
in the port to be configured according to any profile in the port to be configured according to any profile
specified in the list. specified in the list.
By default this object has a value of 0x01, referencing the By default, this object has a value of 0x01, referencing the
1st entry in efmCuPme2BProfileTable or 1st entry in efmCuPme2BProfileTable or
efmCuPme10PProfileTable. 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 irrelevant for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for
the -R subtype (2BaseTL-R or 10PassTS-R) ports - a the -R subtype (2BaseTL-R or 10PassTS-R) ports -- a
zero-length octet string SHALL be returned on an attempt to zero-length octet string SHALL be returned on an attempt to
read this object and an attempt to change this object MUST be read this object and an attempt to change this object MUST be
rejected in this case. rejected in this case.
Note that the current operational profile value is available Note that the current operational profile value is available
via the efmCuPmeOperProfile object. via the efmCuPmeOperProfile object.
Any modification of this object MUST be performed when the Any modification of this object 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
if the link is Up or Initializing. rejected, if the link is Up or Initializing.
Attempts to set this object to a list with a member value that Attempts to set this object to a list with a member value that
is not the value of the index for an active entry in the is not the value of the index for an active entry in the
corresponding profile table MUST be rejected. corresponding profile table MUST be rejected.
This object maps to the Clause 30 attribute aProfileSelect. This object maps to the Clause 30 attribute aProfileSelect.
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 }
skipping to change at page 31, line 4 skipping to change at page 30, line 43
is not the value of the index for an active entry in the is not the value of the index for an active entry in the
corresponding profile table MUST be rejected. corresponding profile table MUST be rejected.
This object maps to the Clause 30 attribute aProfileSelect. This object maps to the Clause 30 attribute aProfileSelect.
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 }
efmCuTargetDataRate OBJECT-TYPE efmCuTargetDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..100000|999999) SYNTAX Unsigned32(1..100000|999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
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/65-octet encapsulation overhead (e.g., target data rate of
SHALL allow lossless transmission of a full-duplex 10Mbps 10 Mbps SHALL allow lossless transmission of a full-duplex
Ethernet frame stream with minimal inter-frame gap). 10 Mbps 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 SHALL be rate (ifSpeed) of the EFMCu port after initialization SHALL be
equal to the target data rate or less, if the target data rate equal to the target data rate or less, if the target data rate
cannot be achieved under spectral restrictions specified by cannot be achieved under spectral restrictions specified by
efmCuAdminProfile/efmCuPmeAdminProfile and with the desired efmCuAdminProfile/efmCuPmeAdminProfile and with the desired
SNR margin. In case the copper environment allows to achieve SNR margin. In case the copper environment allows a higher
a higher total data rate than that specified by the target, total data rate to be achieved than that specified by the
the excess capability SHALL be either converted to additional target, the excess capability SHALL be either converted to
SNR margin or reclaimed by minimizing transmit power as additional SNR margin or reclaimed by minimizing transmit
controlled by efmCuAdaptiveSpectra. power as controlled 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 SHALL 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 the desired SNR Margin. restrictions and with the 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
(in case of SNMP with the error inconsistentValue), if the (in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. link is Up or Initializing.
Note that the current Data Rate of the EFMCu port is Note that the current Data Rate of the EFMCu port is
skipping to change at page 32, line 12 skipping to change at page 31, line 51
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 4 } ::= { efmCuPortConfEntry 4 }
efmCuTargetSnrMgn OBJECT-TYPE efmCuTargetSnrMgn OBJECT-TYPE
SYNTAX Unsigned32(0..21) SYNTAX Unsigned32(0..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired EFMCu port SNR Margin to be achieved on all PMEs "Desired EFMCu port SNR margin to be achieved on all PMEs
assigned to the port, during initialization. (The SNR margin assigned to the port, during initialization. (The SNR margin
is the difference between the desired SNR and the actual SNR). is the difference between the desired SNR and the actual SNR).
Note that 802.3ah recommends using a default Target SNR Margin Note that 802.3ah recommends using a default target SNR margin
of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order of 5 dB for 2BASE-TL ports and 6 dB for 10PASS-TS ports in
to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA order to achieve a mean Bit Error Rate (BER) of 10^-7 at the
service interface. PMA service interface.
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 SNR Margin MUST be performed when the Changing of the target SNR margin 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
(in case of SNMP with the error inconsistentValue), if the (in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. link is Up or Initializing.
Note that the current SNR Margin of the PMEs comprising the Note that the current SNR margin of the PMEs comprising the
EFMCu port is represented by efmCuPmeSnrMgn. EFMCu 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 }
efmCuAdaptiveSpectra OBJECT-TYPE efmCuAdaptiveSpectra OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates how to utilize excess capacity when the copper "Indicates how to utilize excess capacity when the copper
environment allows to achieve a higher total data rate than environment allows a higher total data rate to be achieved
that specified by the efmCuTargetDataRate. than that specified by the efmCuTargetDataRate.
A value of true(1) indicates that the excess capability SHALL A value of true(1) indicates that the excess capability SHALL
be reclaimed by minimizing transmit power, e.g. using higher be reclaimed by minimizing transmit power, e.g., using higher
constellations and Power Back-Off, in order to reduce constellations and Power Back-Off, in order to reduce
interference to other copper pairs in the binder and the interference to other copper pairs in the binder and the
adverse impact to link/system performance. adverse impact to link/system performance.
A value of false(2) indicates that the excess capability SHALL A value of false(2) indicates that the excess capability SHALL
be converted to additional SNR margin and spread evenly across be converted to additional SNR margin and spread evenly across
all active PMEs assigned to the (PCS) port, to increase link all active PMEs assigned to the (PCS) port, to increase link
robustness. robustness.
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 this object MUST be performed when the link is Changing of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected (in case Down. Attempts to change this object MUST be rejected (in
of SNMP with the error inconsistentValue), if the link is Up case of SNMP with the error inconsistentValue), if the link
or Initializing. is Up or Initializing.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 } ::= { efmCuPortConfEntry 6 }
efmCuThreshLowRate OBJECT-TYPE efmCuThreshLowRate OBJECT-TYPE
SYNTAX Unsigned32(1..100000) 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 rate crossing 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/drops below or exceeds this threshold, an reaches/drops below or exceeds this threshold, an
efmCuLowRateCrossing notification MAY be generated if enabled efmCuLowRateCrossing notification MAY be generated if enabled
by efmCuLowRateCrossingEnable. 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 7 } ::= { efmCuPortConfEntry 7 }
skipping to change at page 34, line 43 skipping to change at page 34, line 35
efmCuPeerPAFSupported EfmTruthValueOrUnknown, efmCuPeerPAFSupported EfmTruthValueOrUnknown,
efmCuPAFCapacity Unsigned32, efmCuPAFCapacity Unsigned32,
efmCuPeerPAFCapacity Unsigned32 efmCuPeerPAFCapacity Unsigned32
} }
efmCuPAFSupported OBJECT-TYPE efmCuPAFSupported OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME Aggregation Function (PAF) Capability of the EFMCu port "PME Aggregation Function (PAF) capability of the EFMCu port
(PCS). (PCS).
This object has a value of true(1) when the PCS can perform This object has a value of true(1) when the PCS can perform
PME aggregation on the available PMEs. PME aggregation on the available PMEs.
Ports incapable of PAF SHALL return a value of false(2). Ports incapable of PAF SHALL return a value of false(2).
This object maps to the Clause 30 attribute aPAFSupported. This object maps to the Clause 30 attribute aPAFSupported.
If a Clause 45 MDIO Interface to the PCS is present, If a Clause 45 MDIO Interface to the PCS is present,
then this object maps to the PAF available bit in the then this object maps to the PAF available bit in the
10P/2B capability register." 10P/2B capability register."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPortCapabilityEntry 1 } ::= { efmCuPortCapabilityEntry 1 }
efmCuPeerPAFSupported OBJECT-TYPE efmCuPeerPAFSupported OBJECT-TYPE
SYNTAX EfmTruthValueOrUnknown SYNTAX EfmTruthValueOrUnknown
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME Aggregation Function (PAF) Capability of the EFMCu port "PME Aggregation Function (PAF) capability of the EFMCu port
(PCS) link partner. (PCS) link partner.
This object has a value of true(1) when the remote PCS can This object has a value of true(1) when the remote PCS can
perform PME aggregation on its available PMEs. perform PME aggregation on its available PMEs.
Ports whose peers are incapable of PAF SHALL return a value Ports whose peers are incapable of PAF SHALL return a value
of false(2). of false(2).
Ports whose peers cannot be reached because of the link Ports whose peers cannot be reached because of the link
state SHALL return a value of unknown(0). state SHALL return a value of unknown(0).
This object maps to the Clause 30 attribute This object maps to the Clause 30 attribute
aRemotePAFSupported. aRemotePAFSupported.
skipping to change at page 36, line 8 skipping to change at page 35, line 48
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6" "[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortCapabilityEntry 3 } ::= { efmCuPortCapabilityEntry 3 }
efmCuPeerPAFCapacity OBJECT-TYPE efmCuPeerPAFCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32) SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of PMEs that can be aggregated by the PAF of the peer "Number of PMEs that can be aggregated by the PAF of the peer
Phy (PCS port). PHY (PCS port).
Value of 0 is returned when peer PAF Capacity is unknown A value of 0 is returned when peer PAF capacity is unknown
(peer cannot be reached). (peer cannot be reached).
This object maps to the Clause 30 attribute This object maps to the Clause 30 attribute
aRemotePAFCapacity." aRemotePAFCapacity."
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
skipping to change at page 37, line 25 skipping to change at page 37, line 16
noPeer(0), noPeer(0),
peerPowerLoss(1), peerPowerLoss(1),
pmeSubTypeMismatch(2), pmeSubTypeMismatch(2),
lowRate(3) 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 - the peer PHY cannot be reached (e.g. noPeer - the 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 - the peer PHY has indicated impending peerPowerLoss - the peer PHY has indicated impending
unit failure due to loss of local unit failure due to loss of local
power ('Dying Gasp'). 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 subtype, 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.
lowRate - ifSpeed of the port reached or dropped lowRate - ifSpeed of the port reached or dropped
below efmCuThreshLowRate below efmCuThreshLowRate.
This object is intended to supplement the ifOperStatus object This object is intended to supplement the ifOperStatus object
in IF-MIB and ifMauMediaAvailable in MAU-MIB. in IF-MIB and ifMauMediaAvailable in MAU-MIB.
Additional information is available via the efmCuPmeFltStatus Additional information is available via the 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
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable; "IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus" efmCuPmeFltStatus"
skipping to change at page 38, line 12 skipping to change at page 37, line 51
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
DESCRIPTION DESCRIPTION
"EFM port mode of operation (subtype). "EFM port mode of operation (subtype).
The value of 'subscriber' indicates the port is designated as The value of 'subscriber' indicates that the port is
'-R' subtype (all PMEs assigned to this port are of subtype designated as '-R' subtype (all PMEs assigned to this port are
'-R'). of subtype '-R').
The value of the 'office' indicates that the port is The value of the 'office' indicates that the port is
designated as '-O' subtype (all PMEs assigned to this port are designated as '-O' subtype (all PMEs assigned to this port are
of subtype '-O'). of subtype '-O').
The value of 'unknown' indicates that the port has no assigned The value of 'unknown' indicates that the port has no assigned
PMEs yet or that the assigned PMEs are not of the same side PMEs yet or that the assigned PMEs are not of the same side
(subTypePMEMismatch). (subTypePMEMismatch).
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPhyEnd" aPhyEnd."
REFERENCE REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2" "[802.3ah] 61.1, 30.11.1.1.2"
::= { efmCuPortStatusEntry 2 } ::= { efmCuPortStatusEntry 2 }
efmCuNumPMEs OBJECT-TYPE efmCuNumPMEs OBJECT-TYPE
SYNTAX Unsigned32 (0..32) SYNTAX Unsigned32 (0..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PMEs that is currently aggregated by the local "The number of PMEs that is currently aggregated by the local
skipping to change at page 39, line 24 skipping to change at page 39, line 15
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
"The number of fragments smaller than minFragmentSize "The number of fragments smaller than minFragmentSize
(64 Bytes), which have been received across the gamma (64 bytes) that have been received across the gamma interface
interface and discarded. 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.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
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
"The number of fragments larger than maxFragmentSize "The number of fragments larger than maxFragmentSize
(512 Bytes), which have been received across the gamma (512 bytes) that have been received across the gamma interface
interface and discarded. 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.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.23" "[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 } ::= { efmCuPortStatusEntry 6 }
efmCuPAFInBadFragments OBJECT-TYPE efmCuPAFInBadFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of fragments which do not fit into the sequence "The number of fragments that do not fit into the sequence
expected by the frame assembly function, that have been expected by the frame assembly function and that have been
received across the gamma interface and discarded (the received across the gamma interface and discarded (the
frame buffer is flushed to the next valid frame start). frame buffer is flushed to the next valid frame start).
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 bad fragments this object maps to the 10P/2B PAF bad fragments register.
register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
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
"The number of gaps in the sequence of fragments, which have "The number of gaps in the sequence of fragments that have
been 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.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.26" "[802.3ah] 45.2.3.26"
::= { efmCuPortStatusEntry 8 } ::= { efmCuPortStatusEntry 8 }
efmCuPAFInLostStarts OBJECT-TYPE efmCuPAFInLostStarts OBJECT-TYPE
skipping to change at page 43, line 13 skipping to change at page 42, line 47
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 sent on the crossing event in PME. This notification MAY be sent 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, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and the notification, between the detection of the condition and the notification,
is implemented to prevent intermittent notifications to be is implemented to prevent intermittent notifications from
sent. being sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeLineAtnCrossingEnable object." efmCuPmeLineAtnCrossingEnable object."
::= { efmCuPmeNotifications 1 } ::= { efmCuPmeNotifications 1 }
efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeSnrMgn, efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
skipping to change at page 43, line 36 skipping to change at page 43, line 22
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 sent on the crossing event in This notification MAY be sent 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, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and the notification, between the detection of the condition and the notification,
is implemented to prevent intermittent notifications to be is implemented to prevent intermittent notifications from
sent. being sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object." efmCuPmeSnrMgnCrossingEnable object."
::= { 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.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeDeviceFaultEnable object." efmCuPmeDeviceFaultEnable object."
::= { efmCuPmeNotifications 3 } ::= { efmCuPmeNotifications 3 }
efmCuPmeConfigInitFailure NOTIFICATION-TYPE efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus, efmCuPmeFltStatus,
efmCuAdminProfile, efmCuAdminProfile,
efmCuPmeAdminProfile efmCuPmeAdminProfile
skipping to change at page 44, line 49 skipping to change at page 44, line 34
-- The PME group -- The PME group
efmCuPmeConfTable OBJECT-TYPE efmCuPmeConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeConfEntry SYNTAX SEQUENCE OF EfmCuPmeConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of common aspects for EFMCu "Table for Configuration of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
aspects specific to 2BASE-TL or 10PASS-TS PME types is aspects specific to 2BASE-TL or 10PASS-TS PME types is
represented in efmCuPme2BConfTable and efmCuPme10PConfTable represented in efmCuPme2BConfTable and efmCuPme10PConfTable,
respectively. respectively.
Entries in this table MUST be maintained in a persistent Entries in this table MUST be maintained in a persistent
manner." manner."
::= { efmCuPme 1 } ::= { efmCuPme 1 }
efmCuPmeConfEntry OBJECT-TYPE efmCuPmeConfEntry OBJECT-TYPE
SYNTAX EfmCuPmeConfEntry SYNTAX EfmCuPmeConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 45, line 47 skipping to change at page 45, line 33
ieee2BaseTLR(2), ieee2BaseTLR(2),
ieee10PassTSO(3), ieee10PassTSO(3),
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) subtype 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. The actual value will 10PassTS-R. The actual value will
be set by the -O link partner be set by the -O link partner
during initialization (handshake). during initialization (handshake).
ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. The (preferred) or 10PassTS-O. The
actual value will be set during actual value will be set during
initialization depending on the -R initialization depending on the -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. The (preferred) or 2BaseTL-O. The
actual value will be set during actual value will be set during
initialization depending on the -R initialization depending on the -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 rejected if the link Attempts to change this object SHALL be rejected 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 The current operational sub type is indicated by the
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 bits this object combines values of the Port subtype select bits
and the PMA/PMD type selection bits in the 10P/2B PMA/PMD and the PMA/PMD type selection bits in the 10P/2B 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 EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
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 the efmCuPme2BProfileTable or the to an entry in either the efmCuPme2BProfileTable or the
efmCuPme10PProfileTable, depending on the current operating efmCuPme10PProfileTable, depending on the current operating
SubType of the PME. The value of this object is the index of SubType of the PME. The value of this object is the 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 the efmCuAdminProfile object for the PCS port configured via the 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
by efmCuPmeAdminProfile takes precedence over the profile(s) referenced by efmCuPmeAdminProfile takes precedence
referenced by efmCuAdminProfile. over the profile(s) 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 irrelevant for the CPE (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE
subtype (2BaseTL-R or 10PassTS-R) - a zero value SHALL be subtype (2BaseTL-R or 10PassTS-R) -- a zero value SHALL be
returned on an attempt to read this object and any attempt returned on an attempt to read this object and any attempt
to change this object MUST be rejected in this case. to change this object MUST be rejected in this case.
Note that the current operational profile value is available Note that the current operational profile value is available
via efmCuPmeOperProfile object. via efmCuPmeOperProfile object.
Any modification of this object MUST be performed when the Any modification of this object 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
if the link is Up or Initializing. rejected, if the link is Up or Initializing.
Attempts to set this object to a value that is not the value Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding profile of the index for an active entry in the corresponding profile
table MUST be rejected. table MUST be rejected.
This object maps to the Clause 30 attribute aProfileSelect. This object maps to the Clause 30 attribute aProfileSelect.
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 { 0 } DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 } ::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(0|6)) SYNTAX PhysAddress (SIZE(0|6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PAF Remote Discovery Code of the PME port at the CO. "PAF Remote Discovery Code of the PME port at the CO.
The 6 octet long Discovery Code of the peer PCS connected via The 6-octet 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.
Setting this object to all zeroes results in a Discovery Setting this object to all zeroes 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.
A zero-length octet string SHALL be returned on an attempt to A zero-length octet string SHALL be returned on an attempt to
read this object when PAF aggregation is not enabled. read this object when PAF aggregation is not enabled.
This object is irrelevant in CPE port (-R) subtypes: in this This object is irrelevant in CPE port (-R) subtypes: in this
case a zero-length octet string SHALL be returned on an case, a zero-length octet string SHALL be returned on an
attempt to read this object, writing to this object SHALL attempt to read this object; writing to this object SHALL
be rejected. be rejected.
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 (in case of Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or SNMP with the error inconsistentValue), if the link is Up or
Initializing. Initializing.
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 is a function of 10P/2B aggregation discovery this object is a function of 10P/2B aggregation discovery
control register, Discovery operation result bits in 10P/2B control register, Discovery operation result bits in 10P/2B
aggregation and discovery status register and aggregation and discovery status register and
10P/2B aggregation discovery code register" 10P/2B aggregation discovery code register."
REFERENCE REFERENCE
"[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8"
::= { efmCuPmeConfEntry 3 } ::= { efmCuPmeConfEntry 3 }
efmCuPmeThreshLineAtn OBJECT-TYPE efmCuPmeThreshLineAtn 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 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, an 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 (in case of SNMP with the error inconsistentValue), rejected (in case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. 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 maps 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 or exceeds this When the current value of SNR margin reaches or exceeds this
threshold, a efmCuPmeSnrMgnCrossing notification MAY be threshold, an efmCuPmeSnrMgnCrossing notification MAY be
generated, if enabled by efmCuPmeSnrMgnCrossingEnable. generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
This object is writable for the CO subtype PMEs This object is writable for the CO subtype PMEs
(2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype (2BaseTL-O/10PassTS-O). 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 (in case of SNMP with the error inconsistentValue), rejected (in case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. 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 maps to the SNR margin threshold bits in the 2B PMD object maps to the SNR margin threshold bits in the 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
should be generated for this interface. should be generated for this interface.
A value of true(1) indicates that efmCuPmeLineAtnCrossing A value of true(1) indicates that efmCuPmeLineAtnCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 6 } ::= { efmCuPmeConfEntry 6 }
efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeSnrMgnCrossing notifications "Indicates whether efmCuPmeSnrMgnCrossing notifications
should be generated for this interface. should be generated for this interface.
A value of true(1) indicates that efmCuPmeSnrMgnCrossing A value of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 7 } ::= { efmCuPmeConfEntry 7 }
efmCuPmeDeviceFaultEnable OBJECT-TYPE efmCuPmeDeviceFaultEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeDeviceFault notifications "Indicates whether efmCuPmeDeviceFault notifications
should be generated for this interface. should be generated for this interface.
A value of true(1) indicates that efmCuPmeDeviceFault A value of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 8 } ::= { efmCuPmeConfEntry 8 }
efmCuPmeConfigInitFailEnable OBJECT-TYPE efmCuPmeConfigInitFailEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeConfigInitFailure notifications "Indicates whether efmCuPmeConfigInitFailure notifications
should be generated for this interface. should be generated for this interface.
skipping to change at page 51, line 47 skipping to change at page 51, line 32
efmCuPmeSubTypesSupported OBJECT-TYPE efmCuPmeSubTypesSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
ieee2BaseTLO(0), ieee2BaseTLO(0),
ieee2BaseTLR(1), ieee2BaseTLR(1),
ieee10PassTSO(2), ieee10PassTSO(2),
ieee10PassTSR(3) ieee10PassTSR(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME supported sub-types. This is a bitmap of possible "PME supported subtypes. This is a bitmap of possible
sub-types. The various bit positions are: subtypes. 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
The desired mode of operation is determined by The desired mode of operation is determined by
efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects 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"
::= { efmCuPmeCapabilityEntry 1 } ::= { efmCuPmeCapabilityEntry 1 }
efmCuPmeStatusTable OBJECT-TYPE efmCuPmeStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeStatusEntry SYNTAX SEQUENCE OF EfmCuPmeStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides common status information of EFMCu "This table provides common status information of EFMCu
2BASE-TL/10PASS-TS PME ports. Status information specific 2BASE-TL/10PASS-TS PME ports. Status information specific
to 10PASS-TS PME is represented in efmCuPme10PStatusTable. to 10PASS-TS PME is represented in efmCuPme10PStatusTable.
This table contains live data from the equipment. As such, This table contains live data from the equipment. As such,
skipping to change at page 53, line 25 skipping to change at page 53, line 8
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
downNotReady(2), downNotReady(2),
downReady(3), downReady(3),
init(4) init(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current PME link Operational Status. Possible values are: "Current PME link Operational Status. Possible values are:
up(1) - The link is Up and ready to pass 64/65B up(1) - The link is Up and ready to pass
encoded frames or fragments. 64/65-octet encoded frames or fragments.
downNotReady(2) - The link is Down and the PME does not downNotReady(2) - The link is Down and the PME does not
detect Handshake tones from its peer. This detect Handshake tones from its peer.
value may indicate a possible problem with This value may indicate a possible
the peer PME. problem with the peer PME.
downReady(3) - The link is Down and the PME detects downReady(3) - The link is Down and the PME detects
Handshake tones from its peer. Handshake tones from its peer.
init(4) - The link is initializing, as a result of init(4) - The link is Initializing, as a result of
ifAdminStatus being set to 'up' for a ifAdminStatus being set to 'up' for a
particular PME or a PCS the PME is particular PME or a PCS to which the PME
connected to. is connected.
This object is intended to supplement the Down(2) state of This object is intended to supplement the Down(2) state of
ifOperStatus. ifOperStatus.
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPMEStatus. aPMEStatus.
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 partially maps to PMA/PMD link status bits in 10P/2B object partially maps to PMA/PMD link status bits in 10P/2B
PMA/PMD status register." PMA/PMD status register."
skipping to change at page 54, line 20 skipping to change at page 53, line 51
protocolInitFailure(5) protocolInitFailure(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current/Last PME link Fault Status. This is a bitmap of "Current/Last PME link Fault Status. This is a bitmap of
possible conditions. The various bit positions are: possible conditions. The various bit positions are:
lossOfFraming - Loss of Framing for 10P or lossOfFraming - Loss of Framing for 10P or
Loss of Sync word for 2B PMD or Loss of Sync word for 2B PMD or
Loss of 64/65B Framing Loss of 64/65-octet framing.
snrMgnDefect - SNR Margin dropped below the Threshold
lineAtnDefect - Line Attenuation exceeds the Threshold snrMgnDefect - SNR margin dropped below the
threshold.
lineAtnDefect - Line Attenuation exceeds the
threshold.
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 the configuration profile, support the configuration profile,
requested during initialization. requested during initialization.
protocolInitFailure - Protocol initialization failure, due protocolInitFailure - Protocol initialization failure, due
to an incompatible protocol used by to an incompatible protocol used by
the Peer PME during init (that could the peer PME during init (that could
happen if a peer PMD is a regular happen if a peer PMD is a regular
G.SDHSL/VDSL modem instead of a G.SDHSL/VDSL modem instead of a
2BASE-TL/10PASS-TS PME). 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.
This object holds 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.
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 consolidates information from various PMA/PMD object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register, registers, namely: Fault bit in PMA/PMD status 1 register,
10P/2B PMA/PMD link loss register, 10P/2B PMA/PMD link loss register,
10P outgoing indicator bits status register, 10P outgoing indicator bits status register,
skipping to change at page 55, line 25 skipping to change at page 55, line 10
efmCuPmeOperSubType OBJECT-TYPE efmCuPmeOperSubType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ieee2BaseTLO(1), ieee2BaseTLO(1),
ieee2BaseTLR(2), ieee2BaseTLR(2),
ieee10PassTSO(3), ieee10PassTSO(3),
ieee10PassTSR(4) ieee10PassTSR(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operational sub-type of the PME. "Current operational subtype of the PME.
Possible values are: Possible values are:
ieee2BaseTLO - PME operates as 2BaseTL-O ieee2BaseTLO - PME operates as 2BaseTL-O
ieee2BaseTLR - PME operates as 2BaseTL-R ieee2BaseTLR - PME operates as 2BaseTL-R
ieee10PassTSO - PME operates as 10PassTS-O ieee10PassTSO - PME operates as 10PassTS-O
ieee10PassTSR - PME operates as 10PassTS-R ieee10PassTSR - PME operates as 10PassTS-R
The desired operational sub type of the PME can be configured The desired operational sub type of the PME can be configured
via the efmCuPmeAdminSubType variable. via the efmCuPmeAdminSubType 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 subtype select
bits, the PMA/PMD type selection bits in the 10P/2B bits, the PMA/PMD type selection bits in the 10P/2B
PMA/PMD control register and the PMA/PMD link status bits in PMA/PMD control register, and the PMA/PMD link status bits in
the 10P/2B PMA/PMD status register." the 10P/2B PMA/PMD status register."
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 3 } ::= { efmCuPmeStatusEntry 3 }
efmCuPmeOperProfile OBJECT-TYPE efmCuPmeOperProfile OBJECT-TYPE
SYNTAX EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME current operating profile. This object is a pointer to "PME current operating profile. This object is a pointer to
an entry in either the efmCuPme2BProfileTable or the an entry in either the efmCuPme2BProfileTable or the
efmCuPme10PProfileTable, depending on the current operating efmCuPme10PProfileTable, depending on the current operating
SubType of the PME as indicated by efmCuPmeOperSubType. SubType of the PME as indicated by efmCuPmeOperSubType.
Note that a profile entry to which efmCuPmeOperProfile is Note that a profile entry to which efmCuPmeOperProfile is
pointing to can be created automatically to reflect achieved pointing can be created automatically to reflect achieved
parameters in adaptive (not fixed) initialization, parameters in adaptive (not fixed) initialization,
i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or
efmCuPmeAdminProfile may differ. efmCuPmeAdminProfile may differ.
The value of zero indicates that the PME is down or The value of zero indicates that the PME is Down or
initializing. Initializing.
This object partially maps to the aOperatingProfile attribute This object partially maps to the aOperatingProfile attribute
in Clause 30." in Clause 30."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.7" "[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 } ::= { efmCuPmeStatusEntry 4 }
efmCuPmeSnrMgn OBJECT-TYPE efmCuPmeSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Signal-to-Noise Ratio (SNR) margin with respect "The current Signal to Noise Ratio (SNR) margin with respect
to the received signal as perceived by the local PME. to the received signal as perceived by the local PME.
The value of 65535 is returned when the PME is down or The value of 65535 is returned when the PME is Down or
initializing. Initializing.
This object maps to the aPMESNRMgn attribute in Clause 30. This object maps to the aPMESNRMgn attribute in Clause 30.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B RX SNR margin register." object maps to the 10P/2B RX SNR margin register."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.4, 45.2.1.16" "[802.3ah] 30.11.2.1.4, 45.2.1.16"
::= { efmCuPmeStatusEntry 5 } ::= { efmCuPmeStatusEntry 5 }
efmCuPmePeerSnrMgn OBJECT-TYPE efmCuPmePeerSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current SNR margin in dB with respect to the received "The current SNR margin in dB with respect to the received
signal, as perceived by the remote (link partner) PME. signal, as perceived by the remote (link partner) PME.
The value of 65535 is returned when the PME is down or The value of 65535 is returned when the PME is Down or
initializing. Initializing.
This object is irrelevant for the -R PME subtypes. The value This object is irrelevant for the -R PME subtypes. The value
of 65535 SHALL be returned in this case. of 65535 SHALL be returned in this case.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B link partner RX SNR margin object maps to the 10P/2B link partner RX SNR margin
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.17" "[802.3ah] 45.2.1.17"
::= { efmCuPmeStatusEntry 6} ::= { efmCuPmeStatusEntry 6}
efmCuPmeLineAtn OBJECT-TYPE efmCuPmeLineAtn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Line Attenuation in dB as perceived by the local "The current Line Attenuation in dB as perceived by the local
PME. PME.
The value of 65535 is returned when the PME is down or
initializing. The value of 65535 is returned when the PME is Down or
Initializing.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the Line Attenuation register" object maps to the Line Attenuation register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.18" "[802.3ah] 45.2.1.18"
::= { efmCuPmeStatusEntry 7 } ::= { efmCuPmeStatusEntry 7 }
efmCuPmePeerLineAtn OBJECT-TYPE efmCuPmePeerLineAtn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Line Attenuation in dB as perceived by the remote "The current Line Attenuation in dB as perceived by the remote
(link partner) PME. (link partner) PME.
The value of 65535 is returned when the PME is down or The value of 65535 is returned when the PME is Down or
initializing. Initializing.
This object is irrelevant for the -R PME subtypes. The value This object is irrelevant for the -R PME subtypes. The value
of 65535 SHALL be returned in this case. of 65535 SHALL be returned in this case.
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 }
skipping to change at page 58, line 18 skipping to change at page 57, line 52
meters, as perceived by the PME after the link is established. meters, as perceived by the PME after the link is established.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any perfect square root attenuation characteristic, without any
bridged taps. bridged taps.
The value of 65535 is returned if the link is Down or The value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the equivalent Initializing or the PME is unable to estimate the equivalent
length. length.
For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME
is present, then this object maps to the 10P Electrical Length is present, then this object maps to the 10P Electrical Length
register" register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.21" "[802.3ah] 45.2.1.21"
::= { efmCuPmeStatusEntry 9 } ::= { 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
"The number of 64/65-octet encapsulation errors. This counter "The number of 64/65-octet encapsulation errors. This counter
skipping to change at page 61, line 41 skipping to change at page 61, line 25
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
"Regional settings for a 2BASE-TL PME, as specified in the "Regional settings for a 2BASE-TL PME, as specified in the
relevant Regional Annex of [G.991.2]. relevant Regional Annex of [G.991.2].
Regional settings specify the Power Spectral Density (PSD) Regional settings specify the Power Spectral Density (PSD)
mask, Power Back-Off (PBO) values and place limitations on the mask and the Power Back-Off (PBO) values, and place
max allowed data rate, power and constellation. 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)
Annex A/B specify regional settings for data rates 192-2304 Annex A/B specify regional settings for data rates 192-2304
Kbps using 16-TCPAM encoding. Kbps using 16-TCPAM encoding.
Annex F/G specify regional settings for rates 2320-3840 Kbps Annex F/G specify regional settings for rates 2320-3840 Kbps
using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
encoding. 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 partially maps to the Region bits in the 2B general object partially maps to the Region bits in the 2B general
parameter register." parameter register."
skipping to change at page 62, line 21 skipping to change at page 62, line 6
::= { efmCuPme2BProfileEntry 3 } ::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BsMode OBJECT-TYPE efmCuPme2BsMode OBJECT-TYPE
SYNTAX EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired custom Spectral Mode for a 2BASE-TL PME. This object "Desired custom Spectral Mode for a 2BASE-TL PME. This object
is a pointer to an entry in efmCuPme2BsModeTable and a block is a pointer to an entry in efmCuPme2BsModeTable and a block
of entries in efmCuPme2BRateReachTable, which together define of entries in efmCuPme2BRateReachTable, which together define
(country-specific) reach dependent rate limitations in (country-specific) reach-dependent rate limitations in
addition to those defined by efmCuPme2BRegion. addition to those defined by efmCuPme2BRegion.
The value of this object is the index of the referenced The value of this object is the index of the referenced
spectral mode. spectral mode.
The value of zero (default) indicates that no specific The value of zero (default) indicates that no specific
spectral mode is applicable. spectral mode is applicable.
Attempts to set this object to a value that is not the value Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral of the index for an active entry in the corresponding spectral
mode table MUST be rejected." mode table MUST be rejected."
skipping to change at page 64, line 17 skipping to change at page 63, line 49
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 SHALL 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 and efmCuPme2BsMode. 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 maps to the Power1 bits in the 2B PMD parameters object maps to the Power1 bits in the 2B PMD parameters
register" register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 7 } ::= { efmCuPme2BProfileEntry 7 }
efmCuPme2BConstellation OBJECT-TYPE efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
adaptive(0), adaptive(0),
tcpam16(1), tcpam16(1),
tcpam32(2) tcpam32(2)
} }
skipping to change at page 65, line 6 skipping to change at page 64, line 38
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 8 } ::= { 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 the creation, modification or deletion "This object controls the creation, modification, or deletion
of the associated entry in the efmCuPme2BProfileTable per the of the associated entry in the efmCuPme2BProfileTable per the
semantics of RowStatus. semantics of RowStatus.
If an 'active' entry is referenced via efmCuAdminProfile or If an 'active' entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile instance(s), the entry MUST remain efmCuPmeAdminProfile instance(s), the entry MUST remain
'active'. 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify
existing entry it MUST be taken out of service (by setting an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified, and set 'active'
again." again."
::= { efmCuPme2BProfileEntry 9 } ::= { efmCuPme2BProfileEntry 9 }
efmCuPme2BsModeTable OBJECT-TYPE efmCuPme2BsModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports "This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations in addition to 2BASE-TL PMEs, describing spectral limitations in addition to
those specified by efmCuPme2BRegion. those specified by efmCuPme2BRegion.
skipping to change at page 65, line 30 skipping to change at page 65, line 14
efmCuPme2BsModeTable OBJECT-TYPE efmCuPme2BsModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports "This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations in addition to 2BASE-TL PMEs, describing spectral limitations in addition to
those specified by efmCuPme2BRegion. those specified by efmCuPme2BRegion.
In some countries, spectral regulations (e.g. UK ANFP) limit In some countries, spectral regulations (e.g., UK ANFP) limit
the length of the loops for certain data rates. This table the length of the loops for certain data rates. This table
allows these country-specific limitations to be specified. allows these country-specific limitations to be specified.
Entries in this table referenced by the efmCuPme2BsMode Entries in this table referenced by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are MUST NOT be deleted until all the active references are
removed. removed.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"efmCu2BReachRateTable" "efmCu2BReachRateTable"
skipping to change at page 66, line 45 skipping to change at page 66, line 28
spectral mode. The string may include information about spectral mode. The string may include information about
corresponding (country-specific) spectral regulations corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode." and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 } ::= { efmCuPme2BsModeEntry 2 }
efmCuPme2BsModeRowStatus OBJECT-TYPE efmCuPme2BsModeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls creation, modification, or deletion of
the associated entry in efmCuPme2BsModeTable per the semantics the associated entry in efmCuPme2BsModeTable per the semantics
of RowStatus. of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode If an 'active' entry is referenced via efmCuPme2BsMode
instance(s), the entry MUST remain 'active'. instance(s), the entry MUST remain 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify
existing entry it MUST be taken out of service (by setting an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified, and set 'active'
again." again."
::= { efmCuPme2BsModeEntry 3 } ::= { efmCuPme2BsModeEntry 3 }
efmCuPme2BReachRateTable OBJECT-TYPE efmCuPme2BReachRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports the definition of administrative custom "This table supports the definition of administrative custom
spectral modes for 2BASE-TL PMEs, providing spectral spectral modes for 2BASE-TL PMEs, providing spectral
limitations in addition to those specified by limitations in addition to those specified by
efmCuPme2BRegion. efmCuPme2BRegion.
The spectral regulations in some countries (e.g. UK ANFP) The spectral regulations in some countries (e.g., UK ANFP)
limit the length of the loops for certain data rates. limit the length of the loops for certain data rates.
This table allows these country-specific limitations to be This table allows these country-specific limitations to be
specified. specified.
Below is an example of this table for [ANFP]: Below is an example of this table for [ANFP]:
----------+-------+------- ----------+-------+-------
Equivalent MaxRate MaxRate Equivalent MaxRate MaxRate
Length PAM16 PAM32 Length PAM16 PAM32
(m) (Kbps) (Kbps) (m) (Kbps) (Kbps)
----------+-------+------- ----------+-------+-------
skipping to change at page 68, line 28 skipping to change at page 68, line 13
allowed for a certain equivalent loop length, when using allowed for a certain equivalent loop length, when using
16-TCPAM or 32-TCPAM encoding. 16-TCPAM or 32-TCPAM encoding.
When a 2BASE-TL PME is initialized, its data rate MUST NOT When a 2BASE-TL PME is initialized, its data rate MUST NOT
exceed one of the following limitations: exceed one of the following limitations:
- the value of efmCuPme2BMaxDataRate - the value of efmCuPme2BMaxDataRate
- maximum data rate allowed by efmCuPme2BRegion and - maximum data rate allowed by efmCuPme2BRegion and
efmCuPme2BPower efmCuPme2BPower
- maximum data rate for a given encoding specified in the - maximum data rate for a given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by the PME. length, estimated by the PME
It is RECOMMENDED that the efmCuPme2BEquivalentLength values It is RECOMMENDED that the efmCuPme2BEquivalentLength values
are assigned in increasing order, starting from the minimum are assigned in increasing order, starting from the minimum
value. value.
Entries may be created/deleted using the row creation/ Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus." deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex } INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme2BReachRateTable 1 } ::= { efmCuPme2BReachRateTable 1 }
skipping to change at page 69, line 6 skipping to change at page 68, line 39
efmCuPme2BMaxDataRatePam32 Unsigned32, efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus efmCuPme2BReachRateRowStatus RowStatus
} }
efmCuPme2BReachRateIndex OBJECT-TYPE efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX EfmProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL custom spectral mode Reach-Rate table index. "2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with each enry." This object is the unique index associated with each entry."
::= { efmCuPme2BReachRateEntry 1 } ::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BEquivalentLength OBJECT-TYPE efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192) SYNTAX Unsigned32(0..8192)
UNITS "m" UNITS "m"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum allowed equivalent loop's physical length in meters "Maximum allowed equivalent loop's physical length in meters
for the specified data rates. for the specified data rates.
skipping to change at page 69, line 51 skipping to change at page 69, line 36
equivalent loop's length using TC-PAM32 encoding. equivalent loop's length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be The value of zero means that TC-PAM32 encoding should not be
used at this distance." used at this distance."
::= { efmCuPme2BReachRateEntry 4 } ::= { efmCuPme2BReachRateEntry 4 }
efmCuPme2BReachRateRowStatus OBJECT-TYPE efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls the creation, modification or deletion "This object controls the creation, modification, or deletion
of the associated entry in the efmCuPme2BReachRateTable per of the associated entry in the efmCuPme2BReachRateTable per
the semantics of RowStatus. the semantics of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode If an 'active' entry is referenced via efmCuPme2BsMode
instance(s), the entry MUST remain 'active'. instance(s), the entry MUST remain 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify
existing entry it MUST be taken out of service (by setting an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified, and set 'active'
again." again."
::= { efmCuPme2BReachRateEntry 5 } ::= { efmCuPme2BReachRateEntry 5 }
-- 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
10PASS-TS PMEs. 10PASS-TS PMEs.
The first 22 entries in this table SHALL always be defined as The first 22 entries in this table SHALL always be defined as
skipping to change at page 72, line 15 skipping to change at page 71, line 48
efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PPayloadURateProfile INTEGER, efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus efmCuPme10PProfileRowStatus RowStatus
} }
efmCuPme10PProfileIndex OBJECT-TYPE efmCuPme10PProfileIndex OBJECT-TYPE
SYNTAX EfmProfileIndex SYNTAX EfmProfileIndex
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 SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 75, line 43 skipping to change at page 75, line 28
profile5(5) 6-2 - 17 3.500 3.800 profile5(5) 6-2 - 17 3.500 3.800
profile6(6) - 15-1 - 3.500 4.000 profile6(6) - 15-1 - 3.500 4.000
profile7(7) F-5 #04 - - 3.747 3.754 profile7(7) F-5 #04 - - 3.747 3.754
profile8(8) F-5 #05 - - 3.791 3.805 profile8(8) F-5 #05 - - 3.791 3.805
profile9(9) 6-2 - 17 7.000 7.100 profile9(9) 6-2 - 17 7.000 7.100
profile10(10) F-5 #06 15-1 - 7.000 7.300 profile10(10) F-5 #06 15-1 - 7.000 7.300
profile11(11) 6-2 15-1 1 10.100 10.150 profile11(11) 6-2 15-1 1 10.100 10.150
--------------+--------+------+------------+------+------ --------------+--------+------+------------+------+------
Any combination of profiles can be specified by ORing Any combination of profiles can be specified by ORing
individual profiles, for example value of 0x2230 selects individual profiles, for example, a value of 0x2230 selects
profiles 2,6,10 and 11." profiles 2, 6, 10, and 11."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.5" "[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 5 } ::= { efmCuPme10PProfileEntry 5 }
efmCuPme10PPayloadDRateProfile OBJECT-TYPE efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile5(5), profile5(5),
profile10(10), profile10(10),
profile15(15), profile15(15),
profile20(20), profile20(20),
skipping to change at page 76, line 35 skipping to change at page 76, line 20
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
profile140(140) - 70 Mbps profile140(140) - 70 Mbps
profile200(200) - 100 Mbps profile200(200) - 100 Mbps
Each value represents a target for the PME's Downstream Each value represents a target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of Payload Bitrate as seen at the MII. If the payload rate of
the selected profile cannot be achieved based on the loop the selected profile cannot be achieved based on the loop
environment, bandplan and PSD mask, the PME initialization environment, bandplan, and PSD mask, the PME initialization
SHALL fail." SHALL fail."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6" "[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 6 } ::= { efmCuPme10PProfileEntry 6 }
efmCuPme10PPayloadURateProfile OBJECT-TYPE efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile5(5), profile5(5),
profile10(10), profile10(10),
profile15(15), profile15(15),
skipping to change at page 77, line 19 skipping to change at page 77, line 4
in 802.3 Annex 62A. Possible values are: in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
Each value represents a target for the PME's Upstream Payload Each value represents a target for the PME's Upstream Payload
Bitrate as seen at the MII. If the payload rate of the Bitrate as seen at the MII. If the payload rate of the
selected profile cannot be achieved based on the loop selected profile cannot be achieved based on the loop
environment, bandplan and PSD mask, the PME initialization environment, bandplan, and PSD mask, the PME initialization
SHALL fail." SHALL fail."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6" "[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 7 } ::= { efmCuPme10PProfileEntry 7 }
efmCuPme10PProfileRowStatus OBJECT-TYPE efmCuPme10PProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls creation, modification, or deletion of
the associated entry in efmCuPme10PProfileTable per the the associated entry in efmCuPme10PProfileTable per the
semantics of RowStatus. semantics of 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 efmCuPmeAdminProfile, the entry MUST remain 'active' until
all references are removed. all references are removed.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify
existing entry it MUST be taken out of service (by setting an existing entry, it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified, and set 'active'
again." again."
::= { efmCuPme10PProfileEntry 8 } ::= { efmCuPme10PProfileEntry 8 }
efmCuPme10PStatusTable OBJECT-TYPE efmCuPme10PStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides status information of EFMCu 10PASS-TS "This table provides status information of EFMCu 10PASS-TS
PMEs (modems). PMEs (modems).
skipping to change at page 78, line 33 skipping to change at page 78, line 17
SEQUENCE { SEQUENCE {
efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32 efmCuPme10PFECUncorrectedBlocks Counter32
} }
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received and corrected FEC codewords in this "The number of received and corrected Forward Error Correction
10PASS-TS PME. (FEC) codewords in this 10PASS-TS PME.
This object maps to the aPMEFECCorrectedBlocks attribute in This object maps to the 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.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
skipping to change at page 83, line 38 skipping to change at page 83, line 22
MANDATORY-GROUPS { MANDATORY-GROUPS {
efmCuBasicGroup, efmCuBasicGroup,
efmCuPmeGroup, efmCuPmeGroup,
efmCuAlarmConfGroup, efmCuAlarmConfGroup,
efmCuNotificationGroup efmCuNotificationGroup
} }
GROUP efmCuPme2BProfileGroup GROUP efmCuPme2BProfileGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting 2BASE-TL Phy." supporting 2BASE-TL PHY."
GROUP efmCuPme10PProfileGroup GROUP efmCuPme10PProfileGroup
DESCRIPTION DESCRIPTION
"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 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
"Support for all subtypes is not required. However at least "Support for all subtypes is not required. However, at
one value SHALL be supported" least one value SHALL be supported."
OBJECT efmCuPmeAdminSubType OBJECT efmCuPmeAdminSubType
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 ieee2BaseTLR or ieee10PassTSO and ieee2BaseTLO and ieee2BaseTLR or ieee10PassTSO 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."
OBJECT efmCuAdaptiveSpectra OBJECT efmCuAdaptiveSpectra
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 default value SHOULD be false." the default value SHOULD be false."
::= { efmCuCompliances 1 } ::= { efmCuCompliances 1 }
END END
7. Security Considerations 7. Security Considerations
There is a number of managed objects defined in the EFM-CU-MIB module There is a number of managed objects defined in the EFM-CU-MIB module
that have a MAX-ACCESS clause of read-write or read-create. Most that 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, objects can have potentially disruptive effects on network operation,
for example: for example:
o Changing of efmCuPmeAdminSubType may lead to a potential locking o Changing of efmCuPmeAdminSubType may lead to a potential locking
of the link, as peer PMEs of the same sub-type cannot exchange of the link, as peer PMEs of the same subtype cannot exchange
handshake messages. handshake messages.
o Changing of efmCuPAFAdminState to enabled may lead to a potential o Changing of efmCuPAFAdminState to enabled may lead to a potential
locking of the link, if the peer Phy does not support PAF. locking of the link, if the peer PHY does not support PAF.
o Changing of efmCuPAFDiscoveryCode, before the discovery operation, o Changing of efmCuPAFDiscoveryCode, before the discovery operation,
may lead to a wrongful discovery, for example when two -O ports may lead to a wrongful discovery, for example, when two -O ports
are connected to the same multi-PME -R port and both -O ports have are connected to the same multi-PME -R port and both -O ports have
the same Discovery register value. the same Discovery register value.
o Changing PCS or PME configuration parameters (e.g. profile of a o Changing PCS or PME configuration parameters (e.g., profile of a
PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) may lead PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) may lead
to anything from link quality and rate degradation to a complete to anything from link quality and rate degradation to a complete
link initialization failure, as ability of an EFMCu port to link initialization failure, as ability of an EFMCu port to
support a particular configuration depends on the copper support a particular configuration depends on the copper
environment. environment.
o Activation of a PME can cause a severe degradation of service for o Activation of a PME can cause a severe degradation of service for
another EFMCu Phy, whose PME(s) may be affected by the cross-talk another EFMCu PHY, whose PME(s) may be affected by the cross-talk
from the newly activated PME. from the newly activated PME.
o Removal of a PME from an operationally 'up' EFMCu port, o Removal of a PME from an operationally 'up' EFMCu port,
aggregating several PMEs, may cause port's rate degradation aggregating several PMEs, may cause port's rate degradation.
The user of the EFM-CU-MIB module must therefore be aware that The user of the EFM-CU-MIB module must therefore be aware that
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
The readable objects in the EFM-CU-MIB module (i.e., those with MAX- The readable objects in the EFM-CU-MIB module (i.e., those with MAX-
ACCESS other than not-accessible) may be considered sensitive in some ACCESS other than not-accessible) may be considered sensitive in some
environments since, collectively, they provide information about the environments since, collectively, they provide information about the
performance of network interfaces and can reveal some aspects of performance of network interfaces and can reveal some aspects of
their configuration. In particular, since EFMCu can be carried over their configuration. In particular, since EFMCu can be carried over
Unshielded Twisted Pair (UTP) voice grade copper in a bundle with Unshielded Twisted Pair (UTP) voice-grade copper in a bundle with
other pairs belonging to another operator/customer, it is other pairs belonging to another operator/customer, it is
theoretically possible to eavesdrop to an EFMCu transmission simply theoretically possible to eavesdrop to an EFMCu transmission simply
by "listening" to a cross-talk from the EFMCu pairs, especially if by "listening" to a cross-talk from the EFMCu pairs, especially if
the parameters of the EFMCu link in question are known. the parameters of the EFMCu link in question are known.
In such environments it is important to control also GET and NOTIFY In such environments, it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP. when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in these MIB modules. in these MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
skipping to change at page 86, line 27 skipping to change at page 86, line 11
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
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 these MIB modules is properly configured to give access instance of these MIB modules is properly configured to give access
to the objects only to those principals (users) that have legitimate to 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.
8. IANA Considerations 8. IANA Considerations
Object identifiers for the efmCuMIB MODULE-IDENTITY and ifCapStackMIB Object identifiers for the efmCuMIB MODULE-IDENTITY and ifCapStackMIB
MODULE-IDENTITY SHALL be allocated by IANA in the MIB-2 sub-tree, MODULE-IDENTITY have been allocated by IANA in the MIB-2 sub-tree.
before this document is published.
9. Acknowledgments 9. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the [HUBMIB] working group, whose
MIB Working Group [1], whose efforts were greatly advanced by the efforts were greatly advanced by the contributions of the following
contributions of the following people (in alphabetical order): people (in alphabetical order):
Udi Ashkenazi (Actelis) Udi Ashkenazi (Actelis)
Mike Heard Mike Heard
Alfred Hoenes (TR-Sys) Alfred Hoenes (TR-Sys)
Marina Popilov (Actelis) Marina Popilov (Actelis)
Mathias Riess (Infineon) Mathias Riess (Infineon)
skipping to change at page 87, line 4 skipping to change at page 86, line 32
Alfred Hoenes (TR-Sys) Alfred Hoenes (TR-Sys)
Marina Popilov (Actelis) Marina Popilov (Actelis)
Mathias Riess (Infineon) Mathias Riess (Infineon)
Dan Romascanu (Avaya) Dan Romascanu (Avaya)
Matt Squire (Hatteras) Matt Squire (Hatteras)
Bert Wijnen (Alcatel) Bert Wijnen (Alcatel)
10. References 10. References
10.1. Normative References 10.1. Normative References
[802.3] IEEE, "IEEE Standard for Information technology - [802.3] 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 -
requirements - Part 3: Carrier Sense Multiple Access with Specific requirements - Part 3: Carrier Sense
Collision Detection (CSMA/CD) Access Method and Physical Multiple Access with Collision Detection (CSMA/CD)
Layer Specifications", IEEE Std 802.3-2005, December 2005. 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 -
requirements - Part 3: Carrier Sense Multiple Access with Specific requirements - Part 3: Carrier Sense
Collision Detection (CSMA/CD) Access Method and Physical Multiple Access with Collision Detection (CSMA/CD)
Layer Specifications - Amendment: Media Access Control Access Method and Physical Layer Specifications -
Parameters, Physical Layers and Management Parameters for Amendment: Media Access Control 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.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber
(SHDSL) transceivers", ITU-T Recommendation G.991.2, Line (SHDSL) transceivers", ITU-T
December 2003. Recommendation G.991.2, December 2003,
<http://www.itu.int/rec/T-REC-G.991.2/en>.
[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,
<http://www.itu.int/rec/T-REC-G.993.1/en>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for
STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[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,
April 1999. RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack
Extension to the Interfaces Group MIB", RFC 2864, Table Extension to the Interfaces Group MIB",
June 2000. RFC 2864, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network
Management Protocol (SNMP) Management Frameworks",
STD 62, RFC 3411, December 2002.
[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.
[RFC4836] Beili, E., "Definitions of Managed Objects for IEEE 802.3 [RFC4836] Beili, E., "Definitions of Managed Objects for IEEE
Medium Attachment Units (MAUs)", RFC 4836, April 2007. 802.3 Medium Attachment Units (MAUs)", RFC 4836,
April 2007.
[T1.424] ANSI, "Interface Between Networks and Customer [T1.424] ANSI, "Interface Between Networks and Customer
Installation Very-high-bit-rate Digital Subscriber Lines Installation Very-high-bit-rate Digital Subscriber
(VDSL) Metallic Interface (DMT Based)", American National Lines (VDSL) Metallic Interface (DMT Based)",
Standard T1.424-2004, June 2004. American National Standard T1.424-2004, June 2004.
[TS 101 270-1] [TS 101 270-1] ETSI, "Transmission and Multiplexing (TM); Access
ETSI, "Transmission and Multiplexing (TM); Access transmission systems on metallic access cables;
transmission systems on metallic access cables; Very high Very high speed Digital Subscriber Line (VDSL);
speed Digital Subscriber Line (VDSL); Part 1: Functional Part 1: Functional requirements", Technical
requirements", Technical Specification TS 101 270-1, Specification TS 101 270-1, October 2005.
October 2005.
10.2. Informative References 10.2. Informative References
[ANFP] Network Interoperability Consultative Committee (NICC), [ANFP] Network Interoperability Consultative Committee
"Specification of the Access Network Frequency Plan (ANFP) (NICC), "Specification of the Access Network
applicable to transmission systems used on the BT Access Frequency Plan (ANFP) applicable to transmission
Network", NICC Document ND1602:2005/08, August 2005. systems used on the BT Access Network", NICC
Document ND1602:2005/08, August 2005.
[IANAifType-MIB] [HUBMIB] IETF, "Ethernet Interfaces and Hub MIB (hubmib)
Internet Assigned Numbers Authority (IANA), "IANAifType Charter", <http://www.ietf.org/html.charters/OLD/
Textual Convention definition", hubmib-charter.html>.
http://www.iana.org/assignments/ianaiftype-mib.
[IANAifType-MIB] Internet Assigned Numbers Authority (IANA),
"IANAifType Textual Convention definition",
<http://www.iana.org/assignments/ianaiftype-mib>.
[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
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed
Extensions for Very High Speed Digital Subscriber Lines Object Extensions for Very High Speed Digital
(VDSL) Using Multiple Carrier Modulation (MCM) Line Subscriber Lines (VDSL) Using Multiple Carrier
Coding", RFC 4070, May 2005. Modulation (MCM) Line Coding", RFC 4070, May 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and MIB Documents", BCP 111, RFC 4181, September 2005.
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005.
[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical [RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of
Networks (EPON)", RFC 4837, July 2007. Managed Objects for High Bit-Rate DSL - 2nd
generation (HDSL2) and Single-Pair High-Speed
Digital Subscriber Line (SHDSL) Lines", RFC 4319,
December 2005.
[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive
Optical Networks (EPON)", RFC 4837, July 2007.
[RFC4878] Squire, M., "Definitions and Managed Objects for [RFC4878] Squire, M., "Definitions and Managed Objects for
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions on Ethernet-Like Interfaces", RFC 4878, Functions on Ethernet-Like Interfaces", RFC 4878,
June 2007. June 2007.
URIs
[1] <http://www.ietf.org/html.charters/hubmib-charter.html>
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
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
skipping to change at page 90, line 44 skipping to change at line 4199
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 275 change blocks. 
474 lines changed or deleted 451 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/