Ethernet in the First Mile Copper (EFMCu) Interfaces MIB

Internet Engineering Task Force (IETF)                          E. Beili
Request for Comments: 7124                              Actelis Networks
Updates: <a href="./rfc5066">5066</a>                                              February 2014
Category: Standards Track
ISSN: 2070-1721


        <span class="h1">Ethernet in the First Mile Copper (EFMCu) Interfaces MIB</span>

Abstract

   This document updates <a href="./rfc5066">RFC 5066</a>.  It amends that specification by
   informing the Internet community about the transition of the
   EFM-CU-MIB module from the concluded IETF Ethernet Interfaces and Hub
   MIB Working Group to the Institute of Electrical and Electronics
   Engineers (IEEE) 802.3 working group.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7124">http://www.rfc-editor.org/info/rfc7124</a>.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






<span class="grey">Beili                        Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc7124">RFC 7124</a>                  EFMCu Interfaces MIB             February 2014</span>


Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  The Internet-Standard Management Framework  . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-3">3</a>.  Mapping between EFM-CU-MIB and IEEE8023-EFM-CU-MIB  . . . . .   <a href="#page-3">3</a>
   <a href="#section-4">4</a>.  Updating the MIB Modules  . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   <a href="#section-5">5</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>
   <a href="#section-6">6</a>.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>
   <a href="#section-7">7</a>.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>
     <a href="#section-7.1">7.1</a>.  Normative References  . . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>
     <a href="#section-7.2">7.2</a>.  Informative References  . . . . . . . . . . . . . . . . .   <a href="#page-5">5</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   <a href="./rfc5066">RFC 5066</a> [<a href="./rfc5066" title=""Ethernet in the First Mile Copper (EFMCu) Interfaces MIB"">RFC5066</a>] defines two MIB modules:

      EFM-CU-MIB, with a set of objects for managing 10PASS-TS and
      2BASE-TL Ethernet in the First Mile Copper (EFMCu) interfaces;

      IF-CAP-STACK-MIB, with a set of objects describing cross-connect
      capability of a managed device with multi-layer (stacked)
      interfaces, extending the stack management objects in the
      Interfaces Group MIB and the Inverted Stack Table MIB modules.

   With the conclusion of the [<a href="#ref-HUBMIB" title=""Ethernet Interfaces and Hub MIB (hubmib) Charter"">HUBMIB</a>] working group, the responsibility
   for the maintenance and further development of a MIB module for
   managing 2BASE-TL and 10PASS-TS interfaces has been transferred to
   the Institute of Electrical and Electronics Engineers (IEEE) 802.3
   [<a href="#ref-IEEE802.3">IEEE802.3</a>] working group.  In 2011, the IEEE developed the
   IEEE8023-EFM-CU-MIB module, based on the original EFM-CU-MIB module
   [<a href="./rfc5066" title=""Ethernet in the First Mile Copper (EFMCu) Interfaces MIB"">RFC5066</a>].  The current revision of IEEE8023-EFM-CU-MIB is defined in
   IEEE Std 802.3.1-2013 [<a href="#ref-IEEE802.3.1">IEEE802.3.1</a>].

   The IEEE8023-EFM-CU-MIB and EFM-CU-MIB MIB modules can coexist.
   Existing deployments of the EFM-CU-MIB need not be upgraded, but
   operators using the MIB should expect that new equipment will use the
   IEEE8023-EFM-CU-MIB.

   Please note that the IF-CAP-STACK-MIB module was not transferred to
   IEEE and remains as defined in <a href="./rfc5066">RFC 5066</a>.  This memo provides an
   updated security considerations section for that module, since the
   original RFC did not list any security considerations for
   IF-CAP-STACK-MIB.








<span class="grey">Beili                        Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc7124">RFC 7124</a>                  EFMCu Interfaces MIB             February 2014</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  The Internet-Standard Management Framework</span>

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of
   RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in <a href="./rfc2119">RFC</a>
   <a href="./rfc2119">2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Mapping between EFM-CU-MIB and IEEE8023-EFM-CU-MIB</span>

   The current version of IEEE8023-EFM-CU-MIB, defined in IEEE Std
   802.3.1-2013, has MODULE-IDENTITY of ieee8023efmCuMIB with an object
   identifier allocated under the { iso(1)
   iso-identified-organization(3) ieee(111)
   standards-association-numbered-series-standards(2) lan-man-stds(802)
   ieee802dot3(3) ieee802dot3dot1mibs(1) } sub-tree.

   The EFM-CU-MIB has MODULE-IDENTITY of efmCuMIB with an object
   identifier allocated under the mib-2 sub-tree.

   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 modules have different OID values, they can
   coexist, allowing the management of the newer IEEE MIB-based devices
   alongside the legacy IETF MIB-based devices.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Updating the MIB Modules</span>

   With the transfer of the responsibility for maintenance and further
   development of the EFM-CU-MIB module to the IEEE 802.3 working group,
   the EFM-CU-MIB defined in <a href="./rfc5066">RFC 5066</a> becomes the last version of that
   MIB module.

   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.
   Requests and comments pertaining to EFM Copper Interfaces MIB should
   be sent to the IEEE 802.3.1 task force, currently chartered with MIB
   development, via its mailing list [<a href="#ref-LIST802.3.1">LIST802.3.1</a>].

   The IF-CAP-STACK-MIB remains under IETF control and is currently
   maintained by the [<a href="#ref-OPSAWG" title=""Operations and Management Area Working Group (opsawg) Charter"">OPSAWG</a>] working group.







<span class="grey">Beili                        Standards Track                    [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc7124">RFC 7124</a>                  EFMCu Interfaces MIB             February 2014</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   There are no managed objects defined in the IF-CAP-STACK-MIB module
   with a MAX-ACCESS clause of read-write and/or read-create.  So, if
   this MIB module is implemented correctly, then there is no risk that
   an intruder can alter or create any management objects of this MIB
   module via direct SNMP SET operations.

   Some of the readable objects in this MIB module (i.e., objects with a
   MAX-ACCESS other than not-accessible) may be considered sensitive or
   vulnerable in some network environments.

   In particular, ifCapStackStatus and ifInvCapStackStatus can identify
   cross-connect capability of multi-layer (stacked) network interfaces,
   potentially revealing the underlying hardware architecture of the
   managed device.

   It is thus important to control even GET and/or NOTIFY access to
   these objects and possibly to even encrypt the values of these
   objects when sending them over the network via SNMP.

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPsec),
   there is no control as to who on the secure network is allowed to
   access and GET/SET (read/change/create/delete) the objects in this
   MIB module.

   Implementations SHOULD provide the security features described by the
   SNMPv3 framework (see [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>]), and implementations claiming
   compliance to the SNMPv3 standard MUST include full support for
   authentication and privacy via the User-based Security Model (USM)
   [<a href="./rfc3414" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">RFC3414</a>] with the AES cipher algorithm [<a href="./rfc3826" title=""The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model"">RFC3826</a>].  Implementations
   MAY also provide support for the Transport Security Model (TSM)
   [<a href="./rfc5591" title=""Transport Security Model for the Simple Network Management Protocol (SNMP)"">RFC5591</a>] in combination with a secure transport such as SSH
   [<a href="./rfc5592" title=""Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)"">RFC5592</a>] or TLS/DTLS [<a href="./rfc6353" title=""Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)"">RFC6353</a>].

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module is properly configured to give access to
   the objects only to those principals (users) that have legitimate
   rights to indeed GET or SET (change/create/delete) them.








<span class="grey">Beili                        Standards Track                    [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc7124">RFC 7124</a>                  EFMCu Interfaces MIB             February 2014</span>


<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Acknowledgments</span>

   This document was produced by the OPSAWG working group, whose efforts
   were advanced by the contributions of the following people (in
   alphabetical order):

      Dan Romascanu

      David Harrington

      Michael MacFaden

      Tom Petch

   This document updates <a href="./rfc5066">RFC 5066</a>, authored by Edward Beili of Actelis
   Networks, and produced by the now-concluded HUBMIB working group.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  References</span>

<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC3414">RFC3414</a>]  Blumenthal, U. and B. Wijnen, "User-based Security Model
              (USM) for version 3 of the Simple Network Management
              Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>, December 2002.

   [<a id="ref-RFC3826">RFC3826</a>]  Blumenthal, U., Maino, F., and K. McCloghrie, "The
              Advanced Encryption Standard (AES) Cipher Algorithm in the
              SNMP User-based Security Model", <a href="./rfc3826">RFC 3826</a>, June 2004.

   [<a id="ref-RFC5066">RFC5066</a>]  Beili, E., "Ethernet in the First Mile Copper (EFMCu)
              Interfaces MIB", <a href="./rfc5066">RFC 5066</a>, November 2007.

<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>.  Informative References</span>

   [<a id="ref-HUBMIB">HUBMIB</a>]   IETF, "Ethernet Interfaces and Hub MIB (hubmib) Charter",
              <<a href="http://datatracker.ietf.org/wg/hubmib/charter/">http://datatracker.ietf.org/wg/hubmib/charter/</a>>.

   [<a id="ref-IEEE802.3.1">IEEE802.3.1</a>]
              IEEE, "IEEE Standard for Management Information Base (MIB)
              Definitions for Ethernet", IEEE Std 802.3.1-2013, June
              2013, <<a href="http://standards.ieee.org/getieee802/download/802.3.1-2013.pdf">http://standards.ieee.org/getieee802/download/</a>
              <a href="http://standards.ieee.org/getieee802/download/802.3.1-2013.pdf">802.3.1-2013.pdf</a>>.






<span class="grey">Beili                        Standards Track                    [Page 5]</span>

<span id="page-6" ></span>
<span class="grey"><a href="./rfc7124">RFC 7124</a>                  EFMCu Interfaces MIB             February 2014</span>


   [<a id="ref-IEEE802.3">IEEE802.3</a>]
              IEEE, "802.3 Ethernet Working Group",
              <<a href="http://www.ieee802.org/3">http://www.ieee802.org/3</a>>.

   [<a id="ref-LIST802.3.1">LIST802.3.1</a>]
              IEEE, "802.3 MIB Email Reflector",
              <<a href="http://www.ieee802.org/3/be/reflector.html">http://www.ieee802.org/3/be/reflector.html</a>>.

   [<a id="ref-OPSAWG">OPSAWG</a>]   IETF, "Operations and Management Area Working Group
              (opsawg) Charter",
              <<a href="http://datatracker.ietf.org/wg/opsawg/charter/">http://datatracker.ietf.org/wg/opsawg/charter/</a>>.

   [<a id="ref-RFC3410">RFC3410</a>]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.

   [<a id="ref-RFC5591">RFC5591</a>]  Harrington, D. and W. Hardaker, "Transport Security Model
              for the Simple Network Management Protocol (SNMP)", <a href="./rfc5591">RFC</a>
              <a href="./rfc5591">5591</a>, June 2009.

   [<a id="ref-RFC5592">RFC5592</a>]  Harrington, D., Salowey, J., and W. Hardaker, "Secure
              Shell Transport Model for the Simple Network Management
              Protocol (SNMP)", <a href="./rfc5592">RFC 5592</a>, June 2009.

   [<a id="ref-RFC6353">RFC6353</a>]  Hardaker, W., "Transport Layer Security (TLS) Transport
              Model for the Simple Network Management Protocol (SNMP)",
              <a href="./rfc6353">RFC 6353</a>, July 2011.

Author's Address

   Edward Beili
   Actelis Networks
   Bazel 25
   Petach-Tikva  49103
   Israel

   Phone: +972-73-237-6852
   EMail: [email protected]













Beili                        Standards Track                    [Page 6]