draft-ietf-opsawg-rfc5066bis-03.txt   draft-ietf-opsawg-rfc5066bis-04.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Updates: 5066 (if approved) June 25, 2013 Updates: 5066 (if approved) November 06, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: December 27, 2013 Expires: May 10, 2014
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-opsawg-rfc5066bis-03.txt draft-ietf-opsawg-rfc5066bis-04.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 IETF Ethernet Interfaces and Hub MIB Working MIB module from the concluded IETF Ethernet Interfaces and Hub MIB
Group to the Institute of Electrical and Electronics Engineers (IEEE) Working Group to the Institute of Electrical and Electronics
802.3 working group. Engineers (IEEE) 802.3 working group.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 December 27, 2013. This Internet-Draft will expire on May 10, 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 18 skipping to change at page 3, line 18
EFM-CU-MIB, with a set of objects for managing 10PASS-TS and EFM-CU-MIB, with a set of objects for managing 10PASS-TS and
2BASE-TL Ethernet in the First Mile Copper (EFMCu) interfaces; 2BASE-TL Ethernet in the First Mile Copper (EFMCu) interfaces;
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 the EFM-CU-MIB module for the maintenance and further development of a MIB module for
has been transfered to the Institute of Electrical and Electronics managing 2BASE-TL and 10PASS-TS interfaces, has been transfered to
Engineers (IEEE) [802.3] working group. In 2011 the IEEE developed the Institute of Electrical and Electronics Engineers (IEEE) 802.3
IEEE8023-EFM-CU-MIB module, defined in IEEE Std 802.3.1-2011 [802.3] working group. The IEEE developed IEEE8023-EFM-CU-MIB
[802.3.1] and based on the EFM-CU-MIB, defined in RFC 5066. module, defined in IEEE Std 802.3.1-2011 [802.3.1] and based on the
EFM-CU-MIB, defined in RFC 5066.
The IEEE8023-EFM-CU-MIB and EFM-CU-MIB are both valid MIB modules, The IEEE8023-EFM-CU-MIB and EFM-CU-MIB MIB modules can coexist.
which 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
skipping to change at page 4, line 5 skipping to change at page 4, line 5
The initial version of IEEE8023-EFM-CU-MIB, defined in IEEE Std The initial 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-2011, 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 IEEE8023-EFM-CU-MIB are identical to The names of the objects in the first version of the IEEE8023-EFM-CU-
those in EFM-CU-MIB. However, since both MIB modules have different MIB are identical to those in the EFM-CU-MIB. However, since both
OID values, they can coexist, allowing the management of the newer MIB modules have different OID values, they can coexist, allowing the
IEEE MIB-based devices, alongside the legacy IETF MIB-based devices. management of the newer IEEE MIB-based devices, alongside the legacy
IETF MIB-based devices.
4. Updating the MIB Modules 4. Updating the MIB Modules
With the transfer of the responsibility for maintenance and further With the transfer of the responsibility for maintenance and further
development of the EFM-CU-MIB module to the IEEE 802.3 working group, development of the EFM-CU-MIB module to the IEEE 802.3 working group,
the EFM-CU-MIB defined in RFC 5066 becomes the last valid version of the EFM-CU-MIB defined in RFC 5066 becomes the last version of that
that MIB. MIB module.
All further development of the EFM Copper Interfaces MIB will be done All further development of the EFM Copper Interfaces MIB will be done
by the IEEE 802.3 working group in the IEEE8023-EFM-CU-MIB module. by the IEEE 802.3 working group in the IEEE8023-EFM-CU-MIB module.
Requests and comments pertaining to EFM Copper Interfaces MIB SHOULD Requests and comments pertaining to EFM Copper Interfaces MIB SHOULD
be sent to the IEEE 803.3.1 task force mailing list: be sent to the IEEE 803.3 working group. Currently, the mailing list
of the IEEE 802.3.1 task force, chartered with MIB development, is
[stds-802-3-mib@listserv.ieee.org]. [stds-802-3-mib@listserv.ieee.org].
The IF-CAP-STACK-MIB remains under IETF jurisdiction and is currently The IF-CAP-STACK-MIB remains under IETF control and is currently
maintained by the [OPSAWG] working group. maintained by the [OPSAWG] working group.
5. Security Considerations 5. Security Considerations
There are no managed objects defined in IF-CAP-STACK-MIB module with There are no managed objects defined in IF-CAP-STACK-MIB module with
a MAX-ACCESS clause of read-write and/or read-create. a MAX-ACCESS clause of read-write and/or read-create.
Some of the readable objects in this MIB module (i.e., those with Some of the readable objects in this MIB module (i.e., those with
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments since they can reveal some vulnerable in some network environments since they can reveal some
skipping to change at page 5, line 34 skipping to change at page 5, line 37
This document was produced by the OPSAWG working group, whose efforts This document was produced by the OPSAWG working group, whose efforts
were advanced by the contributions of the following people (in were advanced by the contributions of the following people (in
alphabetical order): alphabetical order):
Dan Romascanu Dan Romascanu
David Harrington David Harrington
Michael MacFaden Michael MacFaden
Tom Petch
This document updates RFC 5066, authored by Edward Beili of Actelis This document updates RFC 5066, authored by Edward Beili of Actelis
Networks, and produced by the, now concluded, HUBMIB working group. Networks, and produced by the, now concluded, HUBMIB working group.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use [RFC2119] Bradner, S., "Key words for use
in RFCs to Indicate Requirement in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, Levels", BCP 14, RFC 2119,
skipping to change at page 7, line 27 skipping to change at page 7, line 32
reflector.html>. reflector.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-73-237-6852
EMail: edward.beili@actelis.com EMail: edward.beili@actelis.com
 End of changes. 14 change blocks. 
24 lines changed or deleted 28 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/