draft-ietf-opsawg-rfc5066bis-04.txt   draft-ietf-opsawg-rfc5066bis-05.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Updates: 5066 (if approved) November 06, 2013 Updates: 5066 (if approved) November 20, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: May 10, 2014 Expires: May 24, 2014
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-opsawg-rfc5066bis-04.txt draft-ietf-opsawg-rfc5066bis-05.txt
Abstract Abstract
This document updates RFC 5066. It amends that specification by This document updates RFC 5066. It amends that specification by
informing the internet community about the transition of the EFM-CU- informing the internet community about the transition of the EFM-CU-
MIB module from the concluded IETF Ethernet Interfaces and Hub MIB MIB module from the concluded IETF Ethernet Interfaces and Hub MIB
Working Group to the Institute of Electrical and Electronics Working Group to the Institute of Electrical and Electronics
Engineers (IEEE) 802.3 working group. Engineers (IEEE) 802.3 working group.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on May 10, 2014. This Internet-Draft will expire on May 24, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 21 skipping to change at page 3, line 21
IF-CAP-STACK-MIB, with a set of objects describing cross-connect IF-CAP-STACK-MIB, with a set of objects describing cross-connect
capability of a managed device with multi-layer (stacked) capability of a managed device with multi-layer (stacked)
interfaces, extending the stack management objects in the interfaces, extending the stack management objects in the
Interfaces Group MIB and the Inverted Stack Table MIB modules. Interfaces Group MIB and the Inverted Stack Table MIB modules.
With the conclusion of the [HUBMIB] working group, the responsibility With the conclusion of the [HUBMIB] working group, the responsibility
for the maintenance and further development of a MIB module for for the maintenance and further development of a MIB module for
managing 2BASE-TL and 10PASS-TS interfaces, has been transfered to managing 2BASE-TL and 10PASS-TS interfaces, has been transfered to
the Institute of Electrical and Electronics Engineers (IEEE) 802.3 the Institute of Electrical and Electronics Engineers (IEEE) 802.3
[802.3] working group. The IEEE developed IEEE8023-EFM-CU-MIB [802.3] working group. In 2011, the IEEE developed IEEE8023-EFM-CU-
module, defined in IEEE Std 802.3.1-2011 [802.3.1] and based on the MIB module, based on the original EFM-CU-MIB module. The current
EFM-CU-MIB, defined in RFC 5066. revision of IEEE8023-EFM-CU-MIB is defined in IEEE Std 802.3.1-2013
[802.3.1].
The IEEE8023-EFM-CU-MIB and EFM-CU-MIB MIB modules can coexist. The IEEE8023-EFM-CU-MIB and EFM-CU-MIB MIB modules can coexist.
Please note that IF-CAP-STACK-MIB module was not transfered to IEEE Please note that IF-CAP-STACK-MIB module was not transfered to IEEE
and remains as defined in RFC 5066. This memo provides an updated and remains as defined in RFC 5066. This memo provides an updated
security considerations section for that module, since the original < security considerations section for that module, since the original
RFC did not list any security consideration for IF-CAP-STACK-MIB. RFC did not list any security consideration for IF-CAP-STACK-MIB.
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].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119]. 2119 [RFC2119].
3. Mapping between EFM-CU-MIB and IEEE8023-EFM-CU-MIB 3. Mapping between EFM-CU-MIB and IEEE8023-EFM-CU-MIB
The initial version of IEEE8023-EFM-CU-MIB, defined in IEEE Std The current version of IEEE8023-EFM-CU-MIB, defined in IEEE Std
802.3.1-2011, has MODULE-IDENTITY of ieee8023efmCuMIB with an object 802.3.1-2013, has MODULE-IDENTITY of ieee8023efmCuMIB with an object
identifier allocated under the { org ieee standards-association- identifier allocated under the { org ieee standards-association-
numbers-series-standards lan-man-stds ieee802dot3 ieee802dot3dot1mibs numbers-series-standards lan-man-stds ieee802dot3 ieee802dot3dot1mibs
} sub-tree. } sub-tree.
The EFM-CU-MIB has MODULE-IDENTITY of efmCuMIB with an object The EFM-CU-MIB has MODULE-IDENTITY of efmCuMIB with an object
identifier allocated under the mib-2 sub-tree. identifier allocated under the mib-2 sub-tree.
The names of the objects in the first version of the IEEE8023-EFM-CU- The names of the objects in the first version of the IEEE8023-EFM-CU-
MIB are identical to those in the EFM-CU-MIB. However, since both MIB are identical to those in the EFM-CU-MIB. However, since both
MIB modules have different OID values, they can coexist, allowing the MIB modules have different OID values, they can coexist, allowing the
skipping to change at page 6, line 29 skipping to change at page 6, line 32
8.2. Informative References 8.2. Informative References
[802.3] IEEE, "802.3 Ethernet Working [802.3] IEEE, "802.3 Ethernet Working
Group", Group",
<http://www.ieee802.org/3>. <http://www.ieee802.org/3>.
[802.3.1] IEEE, "IEEE Standard for [802.3.1] IEEE, "IEEE Standard for
Management Information Base (MIB) Management Information Base (MIB)
Definitions for Ethernet", IEEE Definitions for Ethernet", IEEE
Std 802.3.1-2011, July 2011. Std 802.3.1-2013, June 2013.
[HUBMIB] IETF, "Ethernet Interfaces and [HUBMIB] IETF, "Ethernet Interfaces and
Hub MIB (hubmib) Charter", <http: Hub MIB (hubmib) Charter", <http:
//datatracker.ietf.org/wg/hubmib/ //datatracker.ietf.org/wg/hubmib/
charter/>. charter/>.
[OPSAWG] IETF, "Operations and Management [OPSAWG] IETF, "Operations and Management
Area Working Group (opsawg) Area Working Group (opsawg)
Charter", <http:// Charter", <http://
datatracker.ietf.org/wg/opsawg/ datatracker.ietf.org/wg/opsawg/
 End of changes. 8 change blocks. 
11 lines changed or deleted 12 lines changed or added

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