draft-ietf-opsawg-rfc5066bis-05.txt   draft-ietf-opsawg-rfc5066bis-06.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Updates: 5066 (if approved) November 20, 2013 Updates: 5066 (if approved) November 26, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: May 24, 2014 Expires: May 30, 2014
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-opsawg-rfc5066bis-05.txt draft-ietf-opsawg-rfc5066bis-06.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 24, 2014. This Internet-Draft will expire on May 30, 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. In 2011, the IEEE developed IEEE8023-EFM-CU- [IEEE802.3] working group. In 2011, the IEEE developed IEEE8023-EFM-
MIB module, based on the original EFM-CU-MIB module. The current CU-MIB module, based on the original EFM-CU-MIB module [RFC5066].
revision of IEEE8023-EFM-CU-MIB is defined in IEEE Std 802.3.1-2013 The current revision of IEEE8023-EFM-CU-MIB is defined in IEEE Std
[802.3.1]. 802.3.1-2013 [IEEE802.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
skipping to change at page 4, line 21 skipping to change at page 4, line 21
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 version of that the EFM-CU-MIB defined in RFC 5066 becomes the last version of that
MIB module. 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 working group. Currently, the mailing list be sent to the IEEE 802.3.1 task force, currently chartered with MIB
of the IEEE 802.3.1 task force, chartered with MIB development, is development, via its mailing list [LIST802.3.1].
[stds-802-3-mib@listserv.ieee.org].
The IF-CAP-STACK-MIB remains under IETF control 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
skipping to change at page 5, line 47 skipping to change at page 5, line 46
Tom Petch 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
in RFCs to Indicate Requirement Requirement Levels", BCP 14, RFC 2119, March 1997.
Levels", BCP 14, RFC 2119,
March 1997.
[RFC3414] Blumenthal, U. and B. Wijnen, [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security
"User-based Security Model (USM) Model (USM) for version 3 of the Simple Network
for version 3 of the Simple Management Protocol (SNMPv3)", STD 62, RFC 3414,
Network Management Protocol December 2002.
(SNMPv3)", STD 62, RFC 3414,
December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
McCloghrie, "The Advanced Advanced Encryption Standard (AES) Cipher Algorithm in
Encryption Standard (AES) Cipher the SNMP User-based Security Model", RFC 3826,
Algorithm in the SNMP User-based June 2004.
Security Model", RFC 3826,
June 2004.
[RFC5066] Beili, E., "Ethernet in the First [RFC5066] Beili, E., "Ethernet in the First Mile Copper (EFMCu)
Mile Copper (EFMCu) Interfaces Interfaces MIB", RFC 5066, November 2007.
MIB", RFC 5066, November 2007.
8.2. Informative References 8.2. Informative References
[802.3] IEEE, "802.3 Ethernet Working [HUBMIB] IETF, "Ethernet Interfaces and Hub MIB (hubmib)
Group", Charter",
<http://www.ieee802.org/3>. <http://datatracker.ietf.org/wg/hubmib/charter/>.
[802.3.1] IEEE, "IEEE Standard for [IEEE802.3] IEEE, "802.3 Ethernet Working Group",
Management Information Base (MIB) <http://www.ieee802.org/3>.
Definitions for Ethernet", IEEE
Std 802.3.1-2013, June 2013.
[HUBMIB] IETF, "Ethernet Interfaces and [IEEE802.3.1] IEEE, "IEEE Standard for Management Information Base
Hub MIB (hubmib) Charter", <http: (MIB) Definitions for Ethernet", IEEE Std 802.3.1-
//datatracker.ietf.org/wg/hubmib/ 2013, June 2013.
charter/>.
[OPSAWG] IETF, "Operations and Management [LIST802.3.1] IEEE, "802.3 MIB Email Reflector",
Area Working Group (opsawg) <http://www.ieee802.org/3/be/reflector.html>.
Charter", <http://
datatracker.ietf.org/wg/opsawg/
charter/>.
[RFC3410] Case, J., Mundy, R., Partain, D., [OPSAWG] IETF, "Operations and Management Area Working Group
and B. Stewart, "Introduction and (opsawg) Charter",
Applicability Statements for <http://datatracker.ietf.org/wg/opsawg/charter/>.
Internet-Standard Management
Framework", RFC 3410,
December 2002.
[RFC5591] Harrington, D. and W. Hardaker, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Transport Security Model for the "Introduction and Applicability Statements for
Simple Network Management Internet-Standard Management Framework", RFC 3410,
Protocol (SNMP)", RFC 5591, December 2002.
June 2009.
[RFC5592] Harrington, D., Salowey, J., and [RFC5591] Harrington, D. and W. Hardaker, "Transport Security
W. Hardaker, "Secure Shell Model for the Simple Network Management Protocol
Transport Model for the Simple (SNMP)", RFC 5591, June 2009.
Network Management Protocol
(SNMP)", RFC 5592, June 2009.
[RFC6353] Hardaker, W., "Transport Layer [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Security (TLS) Transport Model Shell Transport Model for the Simple Network
for the Simple Network Management Management Protocol (SNMP)", RFC 5592, June 2009.
Protocol (SNMP)", RFC 6353,
July 2011.
[stds-802-3-mib@listserv.ieee.org] IEEE, "802.3 MIB Email [RFC6353] Hardaker, W., "Transport Layer Security (TLS)
Reflector", <http:// Transport Model for the Simple Network Management
www.ieee802.org/3/be/ Protocol (SNMP)", RFC 6353, July 2011.
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-73-237-6852 Phone: +972-73-237-6852
 End of changes. 19 change blocks. 
72 lines changed or deleted 49 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/