draft-ietf-hubmib-efm-cu-mib-06.txt   draft-ietf-hubmib-efm-cu-mib-07.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: April 15, 2007 October 12, 2006 Intended status: Standards Track February 21, 2007
Expires: August 25, 2007
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-06.txt draft-ietf-hubmib-efm-cu-mib-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 15, 2007. This Internet-Draft will expire on August 25, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
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 proposes an extension 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 MAU MIB modules with a set of objects for managing Ethernet
in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
defined in IEEE Std 802.3ah-2004. In addition a set of objects is defined in IEEE Std 802.3ah-2004. In addition a set of objects is
defined, describing cross-connect capability of a managed device with defined, describing cross-connect capability of a managed device with
multi-layer (stacked) interfaces, extending the stack management multi-layer (stacked) interfaces, extending the stack management
objects in the Interfaces Group MIB and the Inverted Stack Table MIB objects in the Interfaces Group MIB and the Inverted Stack Table MIB
modules. 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) . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . 9 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 10
3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 10 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 11
3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 11
3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 11 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 12
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 12 4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13
4.2. Interface stack capability MIB Overview . . . . . . . . . 12 4.2. Interface stack capability MIB Overview . . . . . . . . . 13
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 13 4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 14 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 21 6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . 84
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 83 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 83 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84 10. Notes to RFC Editor . . . . . . . . . . . . . . . . . . . . . 86
10.1. Normative References . . . . . . . . . . . . . . . . . . . 84 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87
10.2. Informative References . . . . . . . . . . . . . . . . . . 85 11.1. Normative References . . . . . . . . . . . . . . . . . . . 87
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 87 11.2. Informative References . . . . . . . . . . . . . . . . . . 88
Intellectual Property and Copyright Statements . . . . . . . . . . 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 EFMCu, are reach respectively. These interfaces, collectively called EFM Copper
based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications (EFMCu), are based on Single-pair High-speed Digital Subscriber Line
and support variable rates and optional Physical Medium Entity (PME) (SHDSL) [G.991.2] and Very High speed Digital Subscriber Line (VDSL)
aggregation (a.k.a. multi-pair bonding). [G.993.1] technology, supporting optional 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 2700 m long 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long
single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using
5dB target noise margin). 5dB target noise margin).
10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long
single copper pair with a mean BER of 10^-7 (using 6dB target noise single copper pair with a mean BER of 10^-7 (using 6dB target noise
margin). 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 EFMCu interfaces. In addition a MIB module is defined describing
cross-connect capability of a stacked interface. 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) Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf- clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB
hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB
respectively. [I-D.ietf-hubmib-efm-epon-mib] 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 a MIB Structure of Management Information (SMI). This memo specifies MIB
module that is compliant to the SMIv2, which is described in STD 58, modules that are compliant to the SMIv2, which is described in STD
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
[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, Interfaces Group MIB (IF-MIB), Ethernet-Like Specifically, Interfaces Group MIB (IF-MIB), Ethernet-Like
skipping to change at page 4, line 48 skipping to change at page 4, line 48
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
A generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, each connected to a MAC via Medium Independent Interface (PCS) ports, each connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of (MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details. 61.1 of [802.3ah] for more details.
Each PME in the aggregated EFMCu port is represented in the Interface Each PME in the aggregated EFMCu port is represented in the Interface
table (ifTable) as a separate port with ifType of shdsl(169) for table (ifTable) as a separate 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). Zero active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero
value SHALL be returned when PME is initializing or down. value SHALL be returned when PME is initializing or down.
The ifSpeed of the PCS is the sum of the current operating data rates The ifSpeed of the PCS is the sum of the current operating data rates
of all PMEs in the aggregation group, without the 64/65B of all PMEs in the aggregation group, without the 64/65B
encapsulation overhead and PAF overhead, but accounting for the encapsulation overhead and PAF overhead, but accounting for the
Inter-Frame Gaps (IFG). Inter-Frame Gaps (IFG).
When using the stated definition of ifSpeed for the PCS, there would When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are be no frame loss in the following configuration (the test-sets are
configured to generate 100% of back to back traffic, i.e. minimal configured to generate 100% of back to back traffic, i.e. minimal
IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM
interfaces are 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|
'-------' '--' '---' '-------'
ifSpeed= 100Mbps 100Mbps 100Mbps ifSpeed= 100Mbps 100Mbps 100Mbps
Figure 1: Example configuration with no frame loss Figure 1: Example configuration with no frame loss
The following figure shows the IEEE 802.3 layering diagram and
corresponding use of ifTable and ifMauTable:
The following figure shows the layering diagram and corresponding use .-------------------------. -
of ifTable and ifMauTable: | LLC | ^
_________________________ _
| LLC | |
+-------------------------+ | 1 ifEntry +-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6) | MAC | | ifType: ethernetCsmacd(6)
+-------------------------+ > ifMauEntry +-------------------------+ ) ifMauEntry
| Reconsiliation | | ifMauType: dot3MauType2BaseTL or | Reconsiliation | | ifMauType: dot3MauType2BaseTL or
+-------------------------+ | dot3MauType10PassTS +-------------------------+ | dot3MauType10PassTS
| PCS | | | PCS | v
+-------------+---+-------+ + +-------------+---+-------+ -
| TC \ | | | | | TC \ | | | ^
+-----\ | | | | +-----\ | | | |
| PMA > PME 1 |...| PME N | > N ifEntry (N=1..32) | PMA )PME 1 |...| PME N | ) N ifEntry (N=1..32)
+-----/ | | | | ifType: shdsl(169) or vdsl(97) +-----/ | | | | ifType: shdsl(169) or vdsl(97)
| PMD/ | | | | | PMD/ | | | v
-------------+---+------- - '-------------+---+-------' -
LLC - Logical Link Control PMA - Physical Medium Attachment
MAC - Media Access Control PMD - Physical Medium Dependent
PCS - Physical Coding Sub-layer PME - Physical Medium Entity
TC - Transmission Convergence
Figure 2: Use of ifTable and ifMauTable for EFMCu ports Figure 2: Use of ifTable and ifMauTable for EFMCu ports
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
skipping to change at page 7, line 33 skipping to change at page 8, line 15
defined in these MIB modules and in IF-MIB [Note that automatic PME defined in these MIB modules and in IF-MIB [Note that automatic PME
assignment is only shown here for the purposes of the example. Fixed assignment is only shown here for the purposes of the example. Fixed
PME pre-assignment, manual assignment or auto-assignment using an PME pre-assignment, manual assignment or auto-assignment using an
alternative internal algorithm may be chosen by a particular 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 &lt; pcs[i].PAFCapacity )
{ dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6-octets per PCS
// Go over all disconnected PMEs, which can // Go over all disconnected PMEs, which can
// pottentially 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 ifInvStackTable[pme[j]] // not connected NOT ifInvStackTable[pme[j]] // 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 Byte 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 &lt; pcs[i].PAFCapacity) IF ( r == dc AND pcs[i].NumPMEs &lt; 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 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) // updated automatically)
ADD pme[j] TO ifStackTable[pcs[i]]; ADD pme[j] TO ifStackTable[pcs[i]];
// pcs[i] is auto-added to ifInvStackTable[pme[j]] // pcs[i] is auto-added to ifInvStackTable[pme[j]]
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 ifInvStackTable[pme[k]] NOT ifInvStackTable[pme[k]]
{ r = pme[k].RemoteDiscoveryCode; // Get { r = pme[k].RemoteDiscoveryCode; // Get
IF ( r == dc AND IF ( r == dc AND
pcs[i].NumPMEs &lt; pcs[i].PAFCapacity) pcs[i].NumPMEs &lt; pcs[i].PAFCapacity)
{ ADD pme[k] TO ifStackTable[pcs[i]]; { ADD pme[k] TO ifStackTable[pcs[i]];
// pcs[i] is added TO ifInvStackTable[pme[k]] // pcs[i] is added TO ifInvStackTable[pme[k]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
} }
} }
} }
// At this point we have discovered all local PMEs which // At this point we have discovered all local PMEs which
// are physically connected to the same remote RT_device // are physically connected to the same remote RT_device
// and connected them to PCS[i]. Go to the next PCS. // and connected them to PCS[i]. Go to the next PCS.
BREAK; BREAK;
skipping to change at page 9, line 51 skipping to change at page 10, line 34
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 by 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 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/65B encapsulation overhead and PAF overhead, |
| | but accounting for the Inter-Frame Gaps (IFG) | | | but accounting for the Inter-Frame Gaps (IFG) |
+---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a | | ifAdminStatus | Setting this object to 'up' instructs a |
| | particular PCS (with all PMEs connected to it) or | | | particular PCS (with all PMEs connected to it) or |
| | PME to start initialization process | | | PME to start initialization process |
+---------------+---------------------------------------------------+
| ifOperStatus | efmCuPmeOperStatus supplements the 'down' value | | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | of ifOperStatus for PMEs. | | | of ifOperStatus for PMEs. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1 Table 1: 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 PME(s) comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all
attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have
adequate management objects (Clause 30 attributes and Clause 45 adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard. registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
skipping to change at page 10, line 51 skipping to change at page 11, line 43
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
objects in the EFM-CU-MIB module. objects in the EFM-CU-MIB module.
However, if some functionality, not available in the EFM-CU-MIB However, if some functionality, not available in the EFM-CU-MIB
module, is required and supported by the PME, e.g. performance module, is required and supported by the PME, e.g. performance
monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and
applied for PMEs of 2BASE-TL subtype. applied for PMEs of 2BASE-TL subtype.
3.3. Relation to VDSL MIB module 3.3. Relation to VDSL MIB module
VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, VDSL modems, similar to the PME(s) comprising a 10PASS-TS port, are
are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all
attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have
adequate management objects (Clause 30 attributes and Clause 45 adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard. registers) in the EFM standard.
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 However, if some functionality, not available in the EFM-CU-MIB
module, is required and supported by the PME, relevant VDSL-LINE-EXT- module, is required and supported by the PME, relevant VDSL-LINE-EXT-
MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS
subtype. subtype.
3.4. Relation to Ethernet-Like and MAU MIB modules 3.4. Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf- The implementation of EtherLike-MIB [RFC3635] and MAU-MIB
hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. [I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
skipping to change at page 13, line 20 skipping to change at page 14, line 10
provisioning every parameter on every EFMCu PHY may become provisioning every parameter on every EFMCu PHY may become
burdensome. Moreover, most PMEs are provisioned identically with the burdensome. Moreover, most PMEs are provisioned identically with the
same set of parameters. To simplify the provisioning process, the same set of parameters. To simplify the provisioning process, the
EFM-CU-MIB module makes use of configuration profiles, similar to EFM-CU-MIB module makes use of configuration profiles, similar to
HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set
of parameters, used either for configuration or representation of a of parameters, used either for configuration or representation of a
PME. The same profile can be shared by multiple PME ports, using the PME. The same profile can be shared by multiple PME ports, using the
same configuration. same configuration.
The PME profiles are defined in efmCuPme2BProfileTable and The PME profiles are defined in efmCuPme2BProfileTable and
efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. efmCuPme10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively.
There are 12 predefined standard profiles for 2BASE-TL and 22 There are 12 predefined standard profiles for 2BASE-TL and 22
standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for
rapid provisioning of EFMCu PHYs in most scenarios. In addition the rapid provisioning of EFMCu PHYs in most scenarios. In addition the
EFM-CU-MIB defines two additional predefined profiles for "best- EFM-CU-MIB defines two additional predefined profiles for "best-
effort" provisioning of 2BASE-TL PMEs. An ability to define new effort" provisioning of 2BASE-TL PMEs. An ability to define new
configuration profiles is also provided to allow for EFMCu deployment configuration profiles is also provided to allow for EFMCu deployment
tailored to specific copper environment and spectral regulations. tailored to specific copper environment and spectral regulations.
A specific configuration or administrative profile is assigned to a A specific configuration or administrative profile is assigned to a
specific PME via efmCuPmeAdminProfile object. If specific PME via efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the
PCS port, connected to the PME, determines the configuration profile PCS port, connected to the PME, determines the configuration profile
(or a list of possible profiles) for that PME. This mechanism allows (or a list of possible profiles) for that PME. This mechanism allows
to specify a common profile(s) for all PMEs connected to the PCS to specify a common profile(s) for all PMEs connected to the PCS
port, with an ability to change individual PME profiles by setting port, with an ability to change individual PME profiles by setting
efmCuPmeAdminProfile object, which overwrites profile set by efmCuPmeAdminProfile object, which overwrites the profile set by
efmCuAdminProfile. efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically, object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed) to reflect achieved parameters in adaptive (not fixed)
initialization. initialization.
4.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
skipping to change at page 14, line 11 skipping to change at page 15, line 10
Note that majority of the objects defined in the EFM-CU-MIB module do Note that majority of the objects defined in the EFM-CU-MIB module do
not have direct counterparts in Clause 30 and instead refer to Clause not have direct counterparts in Clause 30 and instead refer to Clause
45 registers. 45 registers.
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oMAU - Basic Package | | | oMAU - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+
| aMAUType | ifMauType (MAU-MIB) | | aMAUType | ifMauType (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) | | aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
+---------------------------------+---------------------------------+
| aMediaAvailable | ifMediaAvailable (MAU-MIB) | | aMediaAvailable | ifMediaAvailable (MAU-MIB) |
+---------------------------------+---------------------------------+
| oPAF - Basic Package | | | oPAF - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+
| aPAFID | ifIndex (IF-MIB) | | aPAFID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aPhyEnd | efmCuPhySide | | aPhyEnd | efmCuPhySide |
+---------------------------------+---------------------------------+
| aPHYCurrentStatus | efmCuStatus | | aPHYCurrentStatus | efmCuStatus |
+---------------------------------+---------------------------------+
| aPAFSupported | efmCuPAFSupported | | aPAFSupported | efmCuPAFSupported |
+---------------------------------+---------------------------------+
| oPAF - PME Aggregation Package | | | oPAF - PME Aggregation Package | |
| (Optional) | | | (Optional) | |
+---------------------------------+---------------------------------+
| aPAFAdminState | efmCuPAFAdminState | | aPAFAdminState | efmCuPAFAdminState |
+---------------------------------+---------------------------------+
| aLocalPAFCapacity | efmCuPAFCapacity | | aLocalPAFCapacity | efmCuPAFCapacity |
+---------------------------------+---------------------------------+
| aLocalPMEAvailable | ifCapStackTable | | aLocalPMEAvailable | ifCapStackTable |
+---------------------------------+---------------------------------+
| aLocalPMEAggregate | ifStackTable (IF-MIB) | | aLocalPMEAggregate | ifStackTable (IF-MIB) |
+---------------------------------+---------------------------------+
| aRemotePAFSupported | efmCuRemotePAFSupported | | aRemotePAFSupported | efmCuRemotePAFSupported |
+---------------------------------+---------------------------------+
| aRemotePAFCapacity | efmCuRemotePAFCapacity | | aRemotePAFCapacity | efmCuRemotePAFCapacity |
+---------------------------------+---------------------------------+
| aRemotePMEAggregate | | | aRemotePMEAggregate | |
+---------------------------------+---------------------------------+
| oPME - 10P/2B Package | | | oPME - 10P/2B Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+
| aPMEID | ifIndex (IF-MIB) | | aPMEID | ifIndex (IF-MIB) |
+---------------------------------+---------------------------------+
| aPMEAdminState | ifAdminState (IF-MIB) | | aPMEAdminState | ifAdminState (IF-MIB) |
+---------------------------------+---------------------------------+
| aPMEStatus | efmCuPmeStatus | | aPMEStatus | efmCuPmeStatus |
| aPMESNRMgn | efmCuPmeSnrMgn | | aPMESNRMgn | efmCuPmeSnrMgn |
+---------------------------------+---------------------------------+
| aTCCodingViolations | efmCuPmeTCCodingErrors | | aTCCodingViolations | efmCuPmeTCCodingErrors |
+---------------------------------+---------------------------------+
| aTCCRCErrors | efmCuPmeTCCrcErrors | | aTCCRCErrors | efmCuPmeTCCrcErrors |
+---------------------------------+---------------------------------+
| aProfileSelect | efmCuAdminProfile, | | aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile | | | efmCuPmeAdminProfile |
+---------------------------------+---------------------------------+
| aOperatingProfile | efmCuPmeOperProfile | | aOperatingProfile | efmCuPmeOperProfile |
+---------------------------------+---------------------------------+
| aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks |
+---------------------------------+---------------------------------+
| aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 2 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 -- RFC 2578
RowStatus TruthValue
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- RFC 2864
; ;
ifCapStackMIB MODULE-IDENTITY ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200610120000Z" -- October 12, 2006 LAST-UPDATED "200702210000Z" -- February 21, 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/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: Dan Romascanu Postal: Alcatel-Lucent
Postal: Avaya Schagen 33
Atidim Technology Park, Bldg. 3 3461 GL Linschoten
Tel Aviv 61131 Netherlands
Israel Tel: +31-348-407-775
Tel: +972 3 645 8414 E-mail: bwijnen@alcatel-lucent.com
E-mail: dromasca@avaya.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks Inc. Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com" E-mail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to 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 Internet Society (2006). 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 XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200610120000Z" -- October 12, 2006
REVISION "200702210000Z" -- February 21, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 ZZZ } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is -- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
-- Sections of the module -- Sections of the module
-- Structured as recommended by RFC 4181, see
-- Appendix D: Suggested OID Layout
ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 } ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 }
-- Groups in the module -- Groups in the module
-- --
-- ifCapStackTable group -- ifCapStackTable group
-- --
ifCapStackTable OBJECT-TYPE ifCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfCapStackEntry SYNTAX SEQUENCE OF IfCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 16, line 42 skipping to change at page 18, line 24
relationships between the multiple sub-layers of network relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships described in interfaces (as opposed to actual relationships described in
ifStackTable). In particular, it contains information on ifStackTable). In particular, it contains information on
which sub-layers MAY possibly run 'on top of' which other which sub-layers MAY possibly run 'on top of' which other
sub-layers, as determined by cross-connect capability of the sub-layers, as determined by cross-connect capability of the
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=active ifCapStackStatus.x.y=true
ifCapStackStatus.x.y row does not exist if it is 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 'active' row interface, that is, there is at least a single row with a
for any existing value of x or y. 'true' status for any existing value of x or y.
This table is read only as it describes device capability" This table is read only as it describes device capability"
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 runs on 'top' of the sub-layers, specifying that one sub-layer MAY possibly run
other sub-layer. Each sub-layer corresponds to a conceptual on 'top' of the other sub-layer. Each sub-layer corresponds
row in the ifTable (interface index for lower- and to a conceptual row in the ifTable (interface index for
higher-layer respectively)." lower- and higher-layer respectively)."
INDEX { INDEX {
ifStackHigherLayer, ifStackHigherLayer,
ifStackLowerLayer ifStackLowerLayer
} }
::= { ifCapStackTable 1 } ::= { ifCapStackTable 1 }
IfCapStackEntry ::= SEQUENCE { IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus RowStatus ifCapStackStatus TruthValue
} }
ifCapStackStatus OBJECT-TYPE ifCapStackStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
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:
active(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.
notInService(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 a one of the interfaces is located on an
pluggable module which is absent. 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 'active', 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. for 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."
skipping to change at page 18, line 29 skipping to change at page 20, line 14
table, modeled after ifInvStackTable from table, modeled after ifInvStackTable from
IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable
defined in this MIB module. defined in this MIB module.
In particular, this table contains information on which In particular, this table contains information on which
sub-layers MAY run 'underneath' which other sub-layers, where sub-layers MAY run 'underneath' which other sub-layers, where
each sub-layer corresponds to a conceptual row in the ifTable. each sub-layer corresponds to a conceptual row in the ifTable.
For example, when the sub-layer with ifIndex value x MAY be For example, when the sub-layer with ifIndex value x MAY be
connected to run underneath the sub-layer with ifIndex value connected to run underneath the sub-layer with ifIndex value
y, then this table contains: y, then this table contains:
ifInvCapStackStatus.x.y=active ifInvCapStackStatus.x.y=true
This table contains exactly the same number of rows as the This table contains exactly the same number of rows as the
ifCapStackTable, but the rows appear in a different order. ifCapStackTable, but the rows appear in a different order.
This table is read only as it describes a cross-connect This table is read only as it describes a cross-connect
capability." capability."
REFERENCE REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable" "IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { ifCapStackObjects 2 } ::= { ifCapStackObjects 2 }
skipping to change at page 19, line 4 skipping to change at page 20, line 36
SYNTAX IfInvCapStackEntry SYNTAX IfInvCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular relationship between two sub- "Information on a particular relationship between two sub-
layers, specifying that one sub-layer MAY run underneath the layers, specifying that one sub-layer MAY run underneath the
other sub-layer. Each sub-layer corresponds to a conceptual other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable." row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer } INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvCapStackTable 1 } ::= { ifInvCapStackTable 1 }
IfInvCapStackEntry ::= SEQUENCE { IfInvCapStackEntry ::= SEQUENCE {
ifInvCapStackStatus RowStatus ifInvCapStackStatus TruthValue
} }
ifInvCapStackStatus OBJECT-TYPE ifInvCapStackStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the possible relationship between two "The status of the possible 'cross-connect capability'
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 ifInvStackStatus.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 ifInvStackStatus object is read-only, as it describes
a cross-connect capability." a cross-connect capability."
REFERENCE
"ifCapStackStatus"
::= { ifInvCapStackEntry 1 } ::= { ifInvCapStackEntry 1 }
-- --
-- ifCapStackConformance group
--
ifCapStackConformance OBJECT IDENTIFIER
::= { ifCapStackObjects 3 }
-- Conformance Statements -- Conformance Statements
--
ifCapStackGroups OBJECT IDENTIFIER ::= ifCapStackGroups OBJECT IDENTIFIER ::=
{ ifCapStackConformance 1 } { ifCapStackConformance 1 }
ifCapStackCompliances OBJECT IDENTIFIER ::= ifCapStackCompliances OBJECT IDENTIFIER ::=
{ ifCapStackConformance 2 } { ifCapStackConformance 2 }
-- Units of Conformance -- Units of Conformance
ifCapStackGroup OBJECT-GROUP ifCapStackGroup OBJECT-GROUP
skipping to change at page 20, line 15 skipping to change at page 21, line 45
::= { ifCapStackGroups 1 } ::= { ifCapStackGroups 1 }
-- Compliance Statements -- Compliance Statements
ifCapStackCompliance MODULE-COMPLIANCE ifCapStackCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities, which provide "The compliance statement for SNMP entities, which provide
information on the cross-connect capability of multi-layer information on the cross-connect capability of multi-layer
(stacked) network interfaces, with flexible cross-connect (stacked) network interfaces, with flexible cross-connect
between the sub-layers. between the sub-layers."
Compliance with the following external compliance statements
is REQUIRED:
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifCapStackGroup ifCapStackGroup
} }
OBJECT ifCapStackStatus OBJECT ifCapStackStatus
SYNTAX INTEGER { active(1) } SYNTAX TruthValue { true(1) }
DESCRIPTION DESCRIPTION
"Support for the notInService(2) value is OPTIONAL for "Support for the false(2) value is OPTIONAL for
implementations supporting pluggable interfaces." implementations supporting pluggable interfaces."
OBJECT ifInvCapStackStatus OBJECT ifInvCapStackStatus
SYNTAX INTEGER { active(1) } SYNTAX TruthValue { true(1) }
DESCRIPTION DESCRIPTION
"Support for the notInService(2) value is OPTIONAL for "Support for the false(2) value is OPTIONAL for
implementations supporting pluggable interfaces." implementations supporting pluggable interfaces."
MODULE IF-MIB MODULE IF-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifStackGroup2 ifStackGroup2
} }
MODULE IF-INVERTED-STACK-MIB MODULE IF-INVERTED-STACK-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifInvStackGroup ifInvStackGroup
skipping to change at page 21, line 26 skipping to change at page 22, line 50
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200610120000Z" -- October 12, 2006 LAST-UPDATED "200702210000Z" -- February 21, 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/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: Dan Romascanu Chair: Bert Wijnen
Postal: Avaya Postal: Alcatel-Lucent
Atidim Technology Park, Bldg. 3 Schagen 33
Tel Aviv 61131 3461 GL Linschoten
Israel Netherlands
Tel: +972 3 645 8414 Tel: +31-348-407-775
E-mail: dromasca@avaya.com E-mail: 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 Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com" E-mail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage "The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
skipping to change at page 23, line 15 skipping to change at page 24, line 35
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 Internet Society (2006). 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 XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200610120000Z" -- October 12, 2006 REVISION "200702210000Z" -- February 21, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 YYY } ::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 23, line 44 skipping to change at page 25, line 16
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 }
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
-- Textual Conventions -- Textual Conventions
ProfileIndex ::= TEXTUAL-CONVENTION EfmProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value, greater than zero, for each PME configuration "A unique value, greater than zero, for each PME configuration
profile in the managed EFMCu port. It is RECOMMENDED that profile in the managed EFMCu port. It is RECOMMENDED that
values are assigned contiguously starting from 1. The value values are assigned contiguously starting from 1. The value
for each profile MUST remain constant at least from one for each profile MUST remain constant at least from one
re-initialization of the entity's network management system re-initialization of the entity's network management system
to the next re-initialization." to the next re-initialization."
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
ProfileIndexOrZero ::= TEXTUAL-CONVENTION EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the ProfileIndex "This textual convention is an extension of EfmProfileIndex
convention. The latter defines a greater than zero value used convention. The latter defines a greater than zero value used
to identify a PME profile in the managed EFMCu port. This to identify a PME profile in the managed EFMCu port. This
extension permits the additional value of zero. The value of extension permits the additional value of zero. The value of
zero is object-specific and MUST therefore be defined as part zero is object-specific and MUST therefore be defined as part
of the description of any object which uses this syntax. of the description of any object which uses this syntax.
Examples of the usage of zero value might include situations Examples of the usage of zero value might include situations
where current operational profile is unknown." where current operational profile is unknown."
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
ProfileIndexList ::= TEXTUAL-CONVENTION EfmProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" DISPLAY-HINT "1d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a list of up to 6 ProfileIndex's. "This textual convention represents a list of up to 6
The ProfileIndex textual convention defines a greater than EfmProfileIndex's, any of which can be chosen for
zero value used to identify a PME profile in the managed EFMCu configuration of an PME in a managed EFMCu port.
port. The value of this object is a concatenation of one or The EfmProfileIndex textual convention defines a greater than
zero value used to identify a PME profile.
The value of this object is a concatenation of one 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
ProfileIndex value. EfmProfileIndex value.
The ProfileIndexList specifies a list of alternative A zero length octet string is object-specific and MUST
profiles, any of which can be chosen for configuration of an therefore be defined as part of the description of any object
PME." which uses this syntax. Examples of the usage of zero length
SYNTAX OCTET STRING (SIZE(1..6)) value might include situations where an object using this
textual convention is irrelevant for a specific EFMCu port
type."
SYNTAX OCTET STRING (SIZE(0..6))
TruthValueOrUnknown ::= 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 convention. The latter defines a boolean value with
possible values of true(1) and false(2). This possible values of true(1) and false(2). This
extension permits the additional value of unknown(0), which extension permits the additional value of unknown(0), which
can be returned as a result of GET operation, when an exact can be returned as a result of GET operation, when an exact
true or false value of the object cannot be determined." true or false value of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) } SYNTAX INTEGER { unknown(0), true(1), false(2) }
skipping to change at page 26, line 20 skipping to change at page 27, line 46
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,
efmCuAdminProfile ProfileIndexList, efmCuAdminProfile EfmProfileIndexList,
efmCuTargetDataRate Unsigned32, efmCuTargetDataRate Unsigned32,
efmCuTargetSnrMgn Unsigned32, efmCuTargetSnrMgn Unsigned32,
efmCuAdaptiveSpectra TruthValue, efmCuAdaptiveSpectra TruthValue,
efmCuThreshLowRate Unsigned32, efmCuThreshLowRate Unsigned32,
efmCuLowRateCrossingEnable TruthValue efmCuLowRateCrossingEnable TruthValue
} }
efmCuPAFAdminState OBJECT-TYPE efmCuPAFAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Administrative (desired) state of the PAF of the EFMCu port "Administrative (desired) state of the PAF of the EFMCu port
(PCS). (PCS).
skipping to change at page 26, line 45 skipping to change at page 28, line 21
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 ignored. 'disabled'. Attempts to 'enable' such ports SHALL be rejected.
PAF 'enabled' port with multiple PMEs assigned cannot be 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 rejected,
until at most one PME is left assigned. 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 ignored 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.
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 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 Byte long code used by the Discovery function, when A unique 6 octet long code used by the Discovery function,
PAF is supported. when PAF is supported.
PCS ports incapable of supporting PAF SHALL return a value of PCS ports incapable of supporting PAF SHALL return a zero
all zeroes. Attempts to change this object SHALL be ignored in length octet string on an attempt to read this object. An
this case. attempt to write to this object SHALL be rejected for such
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 value of this object is read-only for -R port subtypes. The initial value of this object for -R subtype ports after
The initial value of this object for -R ports after reset reset is all zeroes. For -R subtype ports, the value of this
is 0. This value may be changed as a result of writing object cannot be changed directly. This value may be changed
operation on efmCuPAFRemoteDiscoveryCode variable of remote as a result of writing operation on the
PME of -O subtype, connected to one of the local PMEs efmCuPAFRemoteDiscoveryCode object of remote PME of -O
associated with the PCS. subtype, connected to one of the local PMEs associated with
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 with the error Attempts to change this object MUST be rejected (in case of
inconsistentValue if the link is Up or Initializing. SNMP with the error inconsistentValue), if the link is Up or
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" "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
61A.2"
::= { efmCuPortConfEntry 2 } ::= { efmCuPortConfEntry 2 }
efmCuAdminProfile OBJECT-TYPE efmCuAdminProfile OBJECT-TYPE
SYNTAX ProfileIndexList SYNTAX EfmProfileIndexList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired configuration Profile(s), common for all PMEs in the "Desired configuration Profile(s), common for all PMEs in the
EFMCu port. This object is a list of pointers to entries in EFMCu port. This object is a list of pointers to entries in
either efmCuPme2BProfileTable or either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current
operating SubType of the EFMCu port as indicated by operating SubType of the EFMCu port as indicated by
efmCuPortSide. efmCuPortSide.
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
skipping to change at page 28, line 24 skipping to change at page 30, line 4
efmCuPortSide. efmCuPortSide.
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 corresponding non-zero efmCuPmeAdminProfile, is overwritten by corresponding non-zero efmCuPmeAdminProfile,
which takes precedence over efmCuAdminProfile. which takes precedence over efmCuAdminProfile.
The list, consisting of more than one index, allows each PME The 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 1st By default this object has a value of 0x01, referencing 1st
entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable.
This object is writable and readable for the -O subtype This object is writable and readable for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for
the -R subtype (2BaseTL-R or 10PassTS-R) ports. the -R subtype (2BaseTL-R or 10PassTS-R) ports - a zero
length octet string SHALL be returned on an attempt to read
this object and an attempt to change this object MUST be
rejected in this case.
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object MUST be performed when the link is Modification of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a list with a member Attempts to set this object to a list with a member
value, that is not the value of the index for an active entry value, that is not the value of the index for an active entry
in the corresponding profile table, MUST be rejected. in the corresponding profile table, MUST be rejected.
skipping to change at page 29, line 40 skipping to change at page 31, line 23
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 desired SNR Margin. restrictions and with desired SNR Margin.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of the Target Data Rate MUST be performed when the Changing of the Target Data Rate MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
with the error inconsistentValue, if the link is Up or (in case of SNMP with the error inconsistentValue), if the
Initializing. link is Up or Initializing.
Note that current Data Rate of the EFMCu port is represented Note that current Data Rate of the EFMCu port is represented
by ifSpeed object of IF-MIB. by ifSpeed object of IF-MIB.
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"
skipping to change at page 30, line 21 skipping to change at page 32, line 4
Note that 802.3ah recommends using default Target SNR Margin Note that 802.3ah recommends using default Target SNR Margin
of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order
to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA
service interface. 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
with the error inconsistentValue, if the link is Up or (in case of SNMP with the error inconsistentValue), if the
Initializing. link is Up or Initializing.
Note that current SNR Margin of the PMEs comprising the EFMCu Note that current SNR Margin of the PMEs comprising the EFMCu
port is represented by efmCuPmeSnrMgn. port is represented by efmCuPmeSnrMgn.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.1.2" "[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 } ::= { efmCuPortConfEntry 5 }
efmCuAdaptiveSpectra OBJECT-TYPE efmCuAdaptiveSpectra OBJECT-TYPE
skipping to change at page 31, line 9 skipping to change at page 32, line 39
Value of false(2) indicates that the excess capability SHALL 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 with the Down. Attempts to change this object MUST be rejected (in case
error inconsistentValue, if the link is Up or Initializing. of SNMP with the error inconsistentValue), if the link 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
skipping to change at page 32, line 20 skipping to change at page 34, line 4
persistent manner" persistent manner"
::= { efmCuPort 2 } ::= { efmCuPort 2 }
efmCuPortCapabilityEntry OBJECT-TYPE efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu Port Capability table. "An entry in the EFMCu Port Capability 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 }
::= { efmCuPortCapabilityTable 1 } ::= { efmCuPortCapabilityTable 1 }
EfmCuPortCapabilityEntry ::= EfmCuPortCapabilityEntry ::=
SEQUENCE { SEQUENCE {
efmCuPAFSupported TruthValue, efmCuPAFSupported TruthValue,
efmCuPeerPAFSupported TruthValueOrUnknown, 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
skipping to change at page 33, line 4 skipping to change at page 34, line 37
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 TruthValueOrUnknown 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
skipping to change at page 43, line 16 skipping to change at page 44, line 50
Each entry represents common aspects of an EFMCu PME port Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex, stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled." possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPmeConfTable 1 } ::= { efmCuPmeConfTable 1 }
EfmCuPmeConfEntry ::= EfmCuPmeConfEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeAdminSubType INTEGER, efmCuPmeAdminSubType INTEGER,
efmCuPmeAdminProfile ProfileIndexOrZero, efmCuPmeAdminProfile EfmProfileIndexOrZero,
efmCuPAFRemoteDiscoveryCode PhysAddress, efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32, efmCuPmeThreshLineAtn Integer32,
efmCuPmeThreshSnrMgn Integer32, efmCuPmeThreshSnrMgn Integer32,
efmCuPmeLineAtnCrossingEnable TruthValue, efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue, efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue, efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue, efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue efmCuPmeProtocolInitFailEnable TruthValue
} }
skipping to change at page 44, line 21 skipping to change at page 46, line 7
(preferred) or 2BaseTL-O. Actual (preferred) or 2BaseTL-O. Actual
value will be set during value will be set during
initialization depending on -R initialization depending on -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
10PassTS mode, 2BaseTL will be 10PassTS mode, 2BaseTL will be
used). used).
Changing efmCuPmeAdminSubType is a traffic disruptive Changing efmCuPmeAdminSubType is a traffic disruptive
operation and as such SHALL be done when the link is Down. operation and as such SHALL be done when the link is Down.
Attempts to change this object SHALL be ignored if the link Attempts to change this object SHALL be 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 current operational sub type is indicated by
efmCuPmeOperSubType variable. efmCuPmeOperSubType variable.
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port sub-type select bits this object combines values of the Port sub-type 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 ProfileIndexOrZero 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 efmCuPme2BProfileTable or to an entry in either efmCuPme2BProfileTable or
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 efmCuAdminProfile object for the PCS port, configured via efmCuAdminProfile object for the PCS port,
to which this PME is assigned. That is, the profile referenced to which this PME is assigned. That is, the profile referenced
by efmCuPmeAdminProfile takes precedence over the profile(s) by efmCuPmeAdminProfile takes precedence over the profile(s)
referenced by efmCuAdminProfile. referenced by efmCuAdminProfile.
This object is writable and readable for the CO subtype PMEs This object is writable and readable for the CO subtype PMEs
(2BaseTL-O or 10PassTS-O). It is unavailable for the CPE (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE
subtype (2BaseTL-R or 10PassTS-R). subtype (2BaseTL-R or 10PassTS-R) - a zero value SHALL be
returned on an attempt to read this object and any attempt
to change this object MUST be rejected in this case.
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object MUST be performed when the link is Modification of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a value that is not the 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."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { 0 } DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 } ::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress (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 CO. "PAF Remote Discovery Code of the PME port at CO.
A 6 Byte long Discovery Code of the peer PCS connected via A 6 octet long Discovery Code of the peer PCS connected via
the PME. the PME.
Reading this object results in a Discovery Get operation. Reading this object results in a Discovery Get operation.
Writing a zero to this object results in a Discovery 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.
This object does not exist in CPE port subtypes. A zero length A zero-length octet string SHALL be returned on an attempt to
octet string SHALL be returned for CPE port subtypes and also read this object when PAF aggregation is not enabled.
when PAF aggregation is not enabled.
This object is irrelevant in CPE port (-R) subtypes: in this
case a zero length octet string SHALL be returned on an
attempt to read this object, writing to this object SHALL
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 with the error Attempts to change this object MUST be rejected (in case of
inconsistentValue, if the link is Up or Initializing. SNMP with the error inconsistentValue), if the link is Up or
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 }
skipping to change at page 46, line 25 skipping to change at page 48, line 18
When the current value of Line Attenuation reaches or When the current value of Line Attenuation reaches or
exceeds this threshold, a efmCuPmeLineAtnCrossing exceeds this threshold, a efmCuPmeLineAtnCrossing
notification MAY be generated, if enabled by notification MAY be generated, if enabled by
efmCuPmeLineAtnCrossingEnable. efmCuPmeLineAtnCrossingEnable.
This object is writable for the CO subtype PMEs (-O). This object is writable for the CO subtype PMEs (-O).
It is read-only for the CPE subtype (-R). It is read-only for the CPE subtype (-R).
Changing of the Line Attenuation Threshold MUST be performed Changing of the Line Attenuation Threshold MUST be performed
when the link is Down. Attempts to change this object MUST be when the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up rejected (in case of SNMP with the error inconsistentValue),
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)
skipping to change at page 47, line 5 skipping to change at page 48, line 46
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, a 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-R). It is read-only for the CPE subtype (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype
(2BaseTL-R/10PassTS-R). (2BaseTL-R/10PassTS-R).
Changing of the SNR Margin Threshold MUST be performed when Changing of the SNR Margin Threshold MUST be performed when
the link is Down. Attempts to change this object MUST be the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up rejected (in case of SNMP with the error inconsistentValue),
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
skipping to change at page 50, line 33 skipping to change at page 52, line 27
stacked below a single PCS port, also indexed by ifIndex, stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled." possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPmeStatusTable 1 } ::= { efmCuPmeStatusTable 1 }
EfmCuPmeStatusEntry ::= EfmCuPmeStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeOperStatus INTEGER, efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS, efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER, efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile ProfileIndexOrZero, efmCuPmeOperProfile EfmProfileIndexOrZero,
efmCuPmeSnrMgn Integer32, efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32, efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32, efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32, efmCuPmePeerLineAtn Integer32,
efmCuPmeEquivalentLength Unsigned32, efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32, efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32 efmCuPmeTCCrcErrors Counter32
} }
efmCuPmeOperStatus OBJECT-TYPE efmCuPmeOperStatus OBJECT-TYPE
skipping to change at page 53, line 26 skipping to change at page 55, line 19
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port sub-type select this object combines values of the Port sub-type select
bits, 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 ProfileIndexOrZero 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 efmCuPme2BProfileTable or an entry in either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current
operating SubType of the PME as indicated by operating SubType of the PME as indicated by
efmCuPmeOperSubType. 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 to, 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 PME is down or initializing. The value of zero indicates that PME is down or initializing.
This object partially maps to the aOperatingProfile This object partially maps to the aOperatingProfile
attribute in Clause 30." attribute 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)
skipping to change at page 54, line 30 skipping to change at page 56, line 24
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 PME is down or The value of 65535 is returned when PME is down or
initializing. initializing.
This object is not supported by -R PME subtypes. This object is irrelevant for the -R PME subtypes. The value
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)
skipping to change at page 55, line 19 skipping to change at page 57, line 13
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 PME is down or The value of 65535 is returned when PME is down or
initializing. initializing.
This object is not supported by CPE port subtypes. This object is irrelevant for the -R PME subtypes. The value
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 }
efmCuPmeEquivalentLength OBJECT-TYPE efmCuPmeEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192|65535) SYNTAX Unsigned32(0..8192|65535)
skipping to change at page 58, line 25 skipping to change at page 60, line 19
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active' active entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST NOT be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex } INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BProfileTable 1 } ::= { efmCuPme2BProfileTable 1 }
EfmCuPme2BProfileEntry ::= EfmCuPme2BProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BProfileIndex ProfileIndex, efmCuPme2BProfileIndex EfmProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString, efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER, efmCuPme2BRegion INTEGER,
efmCuPme2BsMode ProfileIndexOrZero, efmCuPme2BsMode EfmProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32, efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRate Unsigned32, efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BPower Unsigned32, efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER, efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus efmCuPme2BProfileRowStatus RowStatus
} }
efmCuPme2BProfileIndex OBJECT-TYPE efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Profile index. "2BASE-TL PME Profile index.
This object is the unique index associated with this profile. This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile Entries in this table are referenced via efmCuAdminProfile
or efmCuPmeAdminProfile objects." or efmCuPmeAdminProfile objects."
::= { efmCuPme2BProfileEntry 1 } ::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileDescr OBJECT-TYPE efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 2BASE-TL PME "A textual string containing information about 2BASE-TL PME
Profile. The string MAY include information about data rate Profile. The string may include information about data rate
and spectral limitations of this particular profile." and spectral limitations of this particular profile."
::= { efmCuPme2BProfileEntry 2 } ::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
region1(1), region1(1),
region2(2) region2(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 59, line 40 skipping to change at page 61, line 35
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."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G" "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 } ::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BsMode OBJECT-TYPE efmCuPme2BsMode OBJECT-TYPE
SYNTAX ProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired custom Spectral Mode for 2BASE-TL PME. This object "Desired custom Spectral Mode for 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
skipping to change at page 62, line 32 skipping to change at page 64, line 27
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 creation/deletion of the associated "This object controls creation, modification or deletion of
entry in efmCuPme2BProfileTable per the semantics of the associated entry in efmCuPme2BProfileTable per the
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 all efmCuPmeAdminProfile, the entry MUST remain 'active' until all
references are removed." references are removed.
An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active'
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
skipping to change at page 63, line 32 skipping to change at page 65, line 34
which is used to reference corresponding entries in the which is used to reference corresponding entries in the
efmCu2BReachRateTable. efmCu2BReachRateTable.
Entries may be created/deleted using the row creation/ Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus." deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex } INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 } ::= { efmCuPme2BsModeTable 1 }
EfmCuPme2BsModeEntry ::= EfmCuPme2BsModeEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BsModeIndex ProfileIndex, efmCuPme2BsModeIndex EfmProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString, efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus efmCuPme2BsModeRowStatus RowStatus
} }
efmCuPme2BsModeIndex OBJECT-TYPE efmCuPme2BsModeIndex OBJECT-TYPE
SYNTAX ProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Spectral Mode index. "2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral This object is the unique index associated with this spectral
mode. mode.
Entries in this table are referenced via efmCuPme2BsMode Entries in this table are referenced via efmCuPme2BsMode
object." object."
::= { efmCuPme2BsModeEntry 1 } ::= { efmCuPme2BsModeEntry 1 }
efmCuPme2BsModeDescr OBJECT-TYPE efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 2BASE-TL PME "A textual string containing information about 2BASE-TL PME
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/deletion of the associated "This object controls creation, modification or deletion of
entry in efmCuPme2BsModeTable per the semantics of the associated entry in efmCuPme2BsModeTable per the semantics
RowStatus. of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed." entry MUST remain 'active' until all references are removed.
An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active'
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 definition of administrative custom "This table supports 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
skipping to change at page 66, line 10 skipping to change at page 68, line 17
are assigned in the increasing order, starting from the are assigned in the increasing order, starting from the
minimum value. minimum 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 }
EfmCuPme2BReachRateEntry ::= EfmCuPme2BReachRateEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BReachRateIndex ProfileIndex, efmCuPme2BReachRateIndex EfmProfileIndex,
efmCuPme2BEquivalentLength Unsigned32, efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32, efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32, efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus efmCuPme2BReachRateRowStatus RowStatus
} }
efmCuPme2BReachRateIndex OBJECT-TYPE efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX ProfileIndex 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 enry."
::= { efmCuPme2BReachRateEntry 1 } ::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BEquivalentLength OBJECT-TYPE efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192) SYNTAX Unsigned32(0..8192)
UNITS "m" UNITS "m"
skipping to change at page 67, line 20 skipping to change at page 69, line 27
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 creation/deletion of the associated "This object controls creation, modification or deletion of
entry in efmCuPme2BReachRateTable per the semantics of the associated entry in efmCuPme2BReachRateTable per the
RowStatus. semantics of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed." entry MUST remain 'active' until all references are removed.
An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active'
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
10PassTL PMEs. 10PASS-TS PMEs.
First 22 entries in this table SHALL always be defined as First 22 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 62B.3): follows (see 802.3ah Annex 62B.3):
-------+--------+----+---------+-----+------------ -------+--------+----+---------+-----+------------
Profile Bandplan UPBO BandNotch DRate URate Profile Bandplan UPBO BandNotch DRate URate
Index PSDMask# p# p# p# p# Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+------------ -------+--------+----+---------+-----+------------
1 1 3 2,6,10,11 20 20(default) 1 1 3 2,6,10,11 20 20(default)
2 13 5 0 20 20 2 13 5 0 20 20
3 1 1 0 20 20 3 1 1 0 20 20
4 16 0 0 100 100 4 16 0 0 100 100
skipping to change at page 69, line 4 skipping to change at page 71, line 18
efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the desired efmCuPmeAdminProfile is zero), it represent the desired
parameters the 10PassTS-O PME initialization. parameters the 10PassTS-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object, If a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the PME. it represents current operating parameters of the PME.
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active' 'active' entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST NOT be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex } INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 } ::= { efmCuPme10PProfileTable 1 }
EfmCuPme10PProfileEntry ::= EfmCuPme10PProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PProfileIndex ProfileIndex, efmCuPme10PProfileIndex EfmProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString, efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER, efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER, efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS, efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER, efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus efmCuPme10PProfileRowStatus RowStatus
} }
efmCuPme10PProfileIndex OBJECT-TYPE efmCuPme10PProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex 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
"A textual string containing information about 10PASS-TS PME "A textual string containing information about 10PASS-TS PME
Profile. The string MAY include information about data rate Profile. The string may include information about data rate
and spectral limitations of this particular profile." and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 } ::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile1(1), profile1(1),
profile2(2), profile2(2),
profile3(3), profile3(3),
profile4(4), profile4(4),
profile5(5), profile5(5),
skipping to change at page 74, line 39 skipping to change at page 77, line 4
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.
This object maps to the aPayloadRateProfileDownstream This object maps to the aPayloadRateProfileDownstream
attribute in Clause 30." attribute in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.21" "[802.3ah] Annex 62A.3.6, 30.5.1.1.21"
::= { 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/deletion of the associated "This object controls creation, modification or deletion of
entry in efmCuPme10PProfileTable per the semantics of the associated entry in efmCuPme10PProfileTable per the
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
existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active'
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
"Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." "This table provides status information of EFMCu 10PASS-TS
PMEs (modems).
This table contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme10P 2 } ::= { efmCuPme10P 2 }
efmCuPme10PStatusEntry OBJECT-TYPE efmCuPme10PStatusEntry OBJECT-TYPE
SYNTAX EfmCuPme10PStatusEntry SYNTAX EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu 10PASS-TS PME Status table." "An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry } AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 } ::= { efmCuPme10PStatusTable 1 }
skipping to change at page 76, line 47 skipping to change at page 79, line 22
efmCuPAFSupported, efmCuPAFSupported,
efmCuAdminProfile, efmCuAdminProfile,
efmCuTargetDataRate, efmCuTargetDataRate,
efmCuTargetSnrMgn, efmCuTargetSnrMgn,
efmCuAdaptiveSpectra, efmCuAdaptiveSpectra,
efmCuPortSide, efmCuPortSide,
efmCuFltStatus efmCuFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for all of EFMCu ports." "A collection of objects representing management information
common for all types of EFMCu ports."
::= { efmCuGroups 1 } ::= { efmCuGroups 1 }
efmCuPAFGroup OBJECT-GROUP efmCuPAFGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPeerPAFSupported, efmCuPeerPAFSupported,
efmCuPAFCapacity, efmCuPAFCapacity,
efmCuPeerPAFCapacity, efmCuPeerPAFCapacity,
efmCuPAFAdminState, efmCuPAFAdminState,
efmCuPAFDiscoveryCode, efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs efmCuNumPMEs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for OPTIONAL PME "A collection of objects supporting OPTIONAL PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports." Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 } ::= { efmCuGroups 2 }
efmCuPAFErrorsGroup OBJECT-GROUP efmCuPAFErrorsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPAFInErrors, efmCuPAFInErrors,
efmCuPAFInSmallFragments, efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments, efmCuPAFInLargeFragments,
efmCuPAFInBadFragments, efmCuPAFInBadFragments,
efmCuPAFInLostFragments, efmCuPAFInLostFragments,
skipping to change at page 78, line 27 skipping to change at page 80, line 51
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeLineAtnCrossingEnable, efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn, efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable, efmCuPmeSnrMgnCrossingEnable,
efmCuPmeDeviceFaultEnable, efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable, efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable efmCuPmeProtocolInitFailEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for configuration of alarm "A collection of objects supporting configuration of alarm
thresholds and notifications in EFMCu ports." thresholds and notifications in EFMCu ports."
::= { efmCuGroups 5 } ::= { efmCuGroups 5 }
efmCuNotificationGroup NOTIFICATION-GROUP efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
efmCuLowRateCrossing, efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing, efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing, efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault, efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure, efmCuPmeConfigInitFailure,
skipping to change at page 81, line 28 skipping to change at page 84, line 4
} }
DESCRIPTION DESCRIPTION
"Support for all subtypes is not required. However at least "Support for all subtypes is not required. However at least
one value SHALL be supported" 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 ieee2BaseTSR or ieee2BaseTLR 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
skipping to change at page 82, line 13 skipping to change at page 84, line 32
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 sub-type 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 evasdrop to an EFMCu transmission simply by theoretically possible to evasdrop to an EFMCu transmission simply by
"listening" to a cross-talk from an EFMCu pair, especially if the "listening" to a cross-talk from the EFMCu pairs, especially if the
parameters of the EFMCu link in question are known. In such parameters of the EFMCu link in question are known.
environments it is important to control even GET and NOTIFY access to
these objects and possibly even to encrypt their values when sending In such environments it is important to control also GET and NOTIFY
them over the network via SNMP. access to these objects and possibly even to encrypt their values
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
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
skipping to change at page 83, line 33 skipping to change at page 86, line 11
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
The two new values of dot3MauType (dot3MauType2BaseTL and The two new values of dot3MauType (dot3MauType2BaseTL and
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit
definitions (b2BaseTL and b10PassTS), as well as the new values for definitions (b2BaseTL and b10PassTS), as well as the new values for
IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined
by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib- by the IANA in the IANA-MAU-MIB module (see
rfc3636bis]) before this document is published as an RFC. [I-D.ietf-hubmib-rfc3636bis]) before this document is published as an
RFC.
Additionally, object identifiers for efmCuMIB MODULE-IDENTITY and
ifCapStackMIB MODULE-IDENTITY SHALL be 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 IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group [1], whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Dan Romascanu Bert Wijnen (Alcatel)
Marina Popilov Dan Romascanu (Avaya)
Mathias Riess Marina Popilov (Actelis)
Mathias Riess (Infineon)
Matt Squire (Hatteras)
Matt Squire
Mike Heard Mike Heard
Udi Ashkenazi Udi Ashkenazi (Actelis)
10. References 10. Notes to RFC Editor
10.1. Normative References This section contains notes to the RFC Editor and should be removed
prior to publication.
Please replace [I-D.ietf-hubmib-efm-mib] and
[I-D.ietf-hubmib-rfc3636bis] with actual RFC numbers if those are
available at time of publication.
11. References
11.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 - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications", IEEE Std 802.3-2005, December 2005. Layer Specifications", IEEE Std 802.3-2005, December 2005.
[802.3ah] IEEE, "IEEE Standard for Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications - Amendment: Media Access Control Layer Specifications - Amendment: Media Access Control
Parameters, Physical Layers and Management Parameters for Parameters, Physical Layers and Management Parameters for
Subscriber Access Networks", IEEE Std 802.3ah-2004, Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004. September 2004.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-05 (work in progress),
July 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Textual McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for 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, RFC 2580,
April 1999. April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
"Introduction and Applicability Statements for Internet- MIB", RFC 2863, June 2000.
Standard Management Framework", RFC 3410, December 2002.
10.2. Informative References [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864,
June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003.
11.2. Informative References
[ANFP] Network Interoperability Consultative Committee (NICC), [ANFP] Network Interoperability Consultative Committee (NICC),
"Specification of the Access Network Frequency Plan (ANFP) "Specification of the Access Network Frequency Plan (ANFP)
applicable to transmission systems used on the BT Access applicable to transmission systems used on the BT Access
Network", NICC Document ND1602:2005/08, August 2005. Network", NICC Document ND1602:2005/08, August 2005.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects of EPON", Khermosh, L., "Managed Objects of EPON",
draft-ietf-hubmib-efm-epon-mib-05 (work in progress), draft-ietf-hubmib-efm-epon-mib-06 (work in progress),
July 2006. November 2006.
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Definitions and Managed Objects for OAM Squire, M., "Definitions and Managed Objects for OAM
Functions on Ethernet Like Interfaces", Functions on Ethernet Like Interfaces",
draft-ietf-hubmib-efm-mib-04 (work in progress), draft-ietf-hubmib-efm-mib-05 (work in progress),
March 2006. October 2006.
[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-05 (work in progress),
July 2006.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
MIB", RFC 2863, June 2000. "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864,
June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line (VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", RFC 4070, May 2005. Coding", RFC 4070, May 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed [RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005. Lines", RFC 4319, December 2005.
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
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 88, line 29 skipping to change at page 90, line 45
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.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 202 change blocks. 
300 lines changed or deleted 418 lines changed or added

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