draft-ietf-opsawg-rfc5066bis-02.txt   draft-ietf-opsawg-rfc5066bis-03.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Updates: 5066 (if approved) May 02, 2013 Updates: 5066 (if approved) June 25, 2013
Intended status: Standards Track Intended status: Standards Track
Expires: November 3, 2013 Expires: December 27, 2013
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-opsawg-rfc5066bis-02.txt draft-ietf-opsawg-rfc5066bis-03.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 IETF Ethernet Interfaces and Hub MIB Working
Group to the Institute of Electrical and Electronics Engineers (IEEE) Group to the Institute of Electrical and Electronics Engineers (IEEE)
802.3 working group. 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 November 3, 2013. This Internet-Draft will expire on December 27, 2013.
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 29 skipping to change at page 3, line 29
has been transfered to the Institute of Electrical and Electronics has been transfered to the Institute of Electrical and Electronics
Engineers (IEEE) [802.3] working group. In 2011 the IEEE developed Engineers (IEEE) [802.3] working group. In 2011 the IEEE developed
IEEE8023-EFM-CU-MIB module, defined in IEEE Std 802.3.1-2011 IEEE8023-EFM-CU-MIB module, defined in IEEE Std 802.3.1-2011
[802.3.1] and based on the EFM-CU-MIB, defined in RFC 5066. [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 are both valid MIB modules,
which 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. security considerations section for that module, since the original
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
skipping to change at page 4, line 23 skipping to change at page 4, line 23
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 valid version of
that MIB. that MIB.
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.1 task force mailing list:
[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 The IF-CAP-STACK-MIB remains under IETF jurisdiction 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 6, line 12 skipping to change at page 6, line 12
(SNMPv3)", STD 62, RFC 3414, (SNMPv3)", STD 62, RFC 3414,
December 2002. December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. [RFC3826] Blumenthal, U., Maino, F., and K.
McCloghrie, "The Advanced McCloghrie, "The Advanced
Encryption Standard (AES) Cipher Encryption Standard (AES) Cipher
Algorithm in the SNMP User-based Algorithm in the SNMP User-based
Security Model", RFC 3826, Security Model", RFC 3826,
June 2004. June 2004.
[RFC5066] Beili, E., "Ethernet in the First
Mile Copper (EFMCu) Interfaces
MIB", RFC 5066, November 2007.
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-2011, July 2011.
skipping to change at page 6, line 41 skipping to change at page 6, line 45
datatracker.ietf.org/wg/opsawg/ datatracker.ietf.org/wg/opsawg/
charter/>. charter/>.
[RFC3410] Case, J., Mundy, R., Partain, D., [RFC3410] Case, J., Mundy, R., Partain, D.,
and B. Stewart, "Introduction and and B. Stewart, "Introduction and
Applicability Statements for Applicability Statements for
Internet-Standard Management Internet-Standard Management
Framework", RFC 3410, Framework", RFC 3410,
December 2002. December 2002.
[RFC5066] Beili, E., "Ethernet in the First
Mile Copper (EFMCu) Interfaces
MIB", RFC 5066, November 2007.
[RFC5591] Harrington, D. and W. Hardaker, [RFC5591] Harrington, D. and W. Hardaker,
"Transport Security Model for the "Transport Security Model for the
Simple Network Management Simple Network Management
Protocol (SNMP)", RFC 5591, Protocol (SNMP)", RFC 5591,
June 2009. June 2009.
[RFC5592] Harrington, D., Salowey, J., and [RFC5592] Harrington, D., Salowey, J., and
W. Hardaker, "Secure Shell W. Hardaker, "Secure Shell
Transport Model for the Simple Transport Model for the Simple
Network Management Protocol Network Management Protocol
 End of changes. 8 change blocks. 
10 lines changed or deleted 11 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/