One document matched: draft-taylor-opsawg-mibs-to-ieee80231-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2108 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.2108.xml">
<!ENTITY RFC3621 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3621.xml">
<!ENTITY RFC3635 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3635.xml">
<!ENTITY RFC3637 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3637.xml">
<!ENTITY RFC4663 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4663.xml">
<!ENTITY RFC4836 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4836.xml">
<!ENTITY RFC4837 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4837.xml">
<!ENTITY RFC4878 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4878.xml">
<!ENTITY RFC5066 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5066.xml">]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-
Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-taylor-opsawg-mibs-to-ieee80231-00"
ipr="trust200902">
<!-- ***** FRONT MATTER ***** -->
<front>
<title abbrev="MIBs Passed To IEEE 802.3">MIBs Passed From the IETF
To IEEE 802.3 and Currently Documented In IEEE 802.3.1-2013</title>
<!-- Authors -->
<!-- add 'role="editor"' below for the editors if appropriate -->
<author initials="T." surname="Taylor" fullname="Tom Taylor"
role="editor">
<organization>PT Taylor Consulting</organization>
<address>
<postal>
<street></street>
<city>Ottawa</city>
<region></region>
<code></code>
<country>Canada</country>
</postal>
<phone></phone>
<email>tom.taylor.stds@gmail.com</email>
</address>
</author>
<date year="2014" />
<!-- Meta-data Declarations -->
<area>Operations and Management</area>
<workgroup>OPSAWG</workgroup>
<keyword>TBD</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>This document records the transfer of ownership of a number of MIBs
relating to ethernet, from the IETF to IEEE 802.3. Like RFC 4663, it
describes the procedures associated with the transfer. Unlike RFC 4663, this
documentation is retrospective in nature, since the transfer happened
several years ago. Deviations from the planned procedures described in RFC
4663 are noted for historical interest [in a later version of this draft -
PTT]. </t>
</abstract>
</front>
<!-- *****FRONT MATTER ***** -->
<!-- *****BODY ***** -->
<middle>
<section anchor="intro" title="Introduction">
<t><xref target="RFC4663"/>, published in September, 2006, described
a plan for transferring four MIBs related to bridges from IETF to
IEEE 802.1 ownership. Some years later, another transfer of ownership
took place, this time related to ethernet and directed to IEEE 802.3.
<xref target="RFC4663"/> clearly enunciates the motivation for the
transfers and also provides an introduction to IEEE standardization
procedures. The discussions of those topics will not be repeated
here.</t>
<t>The IEEE version of this second lot of transferred MIBs was published as
802.3.1-2011 in February, 2011. The IEEE 802.3.1 specification was
subsequently updated. The latest version, IEEE 802.3.1-2013 <xref
target="IEEE802.3.1-2013"/>, is the basis for this document.</t>
<section title="Requirements Language">
<t>This document uses no requirements language.</t>
</section>
</section> <!-- intro -->
<section anchor="whatMIBs" title="IETF and Corresponding IEEE 802.3 MIBs">
<t>This section tabulates the MIBs that were transferred to IEEE 802.3,
identifying the IETF source document, the corresponding chapter of
<xref target="IEEE802.3.1-2013"/>, and the location of the MIB itself
in ASCII format.</t>
<t>IETF MIB Name: DOT3-OAM-MIB
<vspace blankLines="0"/>
IETF Reference: Definitions and Managed Objects for
Operations, Administration, and Maintenance (OAM) Functions on
Ethernet-Like Interfaces <xref target="RFC4878"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-DOT3-OAM-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 6, Ethernet
operations, administration, and maintenance (OAM) MIB module
<vspace blankLines="0"/>
MIB Location:
http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C6mib.txt
</t>
<t>IETF MIB Name: SNMP-REPEATER-MIB
<vspace blankLines="0"/>
IETF Reference: Definitions of Managed
Objects for IEEE 802.3 Repeater Devices using SMIv2 <xref target="RFC2108"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-SNMP-REPEATER-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 7, Ethernet repeater device MIB
module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C7mib.txt
</t>
<t>IETF MIB Name: POWER-ETHERNET-MIB
<vspace blankLines="0"/>
IETF Reference: Power Ethernet MIB <xref target="RFC3621"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-POWER-ETHERNET-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 8, Ethernet data terminal equipment
(DTE) power via medium dependent interface (MDI) MIB module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C8mib.txt
</t>
<t>IETF MIB Name: DOT3-EPON-MIB
<vspace blankLines="0"/>
IETF Reference: Managed Objects of Ethernet Passive Optical Networks
(EPON) <xref target="RFC4837"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-DOT3-EPON-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 9, Ethernet passive optical
networks (EPON) MIB module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C9mib.txt</t>
<t>IETF MIB Name: EtherLike-MIB
<vspace blankLines="0"/>
IETF Reference: Definitions of Managed Objects for the
Ethernet-like Interface Types <xref target="RFC3635"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name:
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C10mib.txt</t>
<t>IETF MIB Name: EFM-CU-MIB
<vspace blankLines="0"/>
IETF Reference: Ethernet in the First Mile Copper (EFMCu)
Interfaces MIB <xref target="RFC5066"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-EFM-CU-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 11, Ethernet in the First
Mile copper (EFMCu) interfaces MIB module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C11mib.tx</t>
<t>IETF MIB Name: ETHER-WIS
<vspace blankLines="0"/>
IETF Reference: Definitions of Managed Objects for the Ethernet
WAN Interface Sublayer <xref target="RFC3637"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-ETHER-WIS-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 12, Ethernet wide area
network (WAN) interface sublayer (WIS) MIB module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C12mib.txt</t>
<t>IETF MIB Name: MAU-MIB
<vspace blankLines="0"/>
IETF Reference: Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) <xref target="RFC4836"/>
<vspace blankLines="0"/>
IEEE 802.3 MIB Name: IEEE8023-MAU-MIB
<vspace blankLines="0"/>
IEEE 802.3.1-2013 description: Chapter 13, Ethernet medium
attachment units (MAUs) MIB module
<vspace blankLines="0"/>
MIB Location: http://www.ieee802.org/3/1/public/mib_modules/20130411/
802dot3dot1C13mib.txt</t>
</section> <!-- whatMIBs -->
<section anchor="procs" title="Procedural Aspects Of the Transfer">
<section anchor="ASCII" title="IEEE MIB Modules in ASCII Format">
<t>See <xref target="RFC4663"/>.</t>
</section> <!-- ASCII -->
<section anchor="OIDreg" title="OID Registration for New MIB Modules">
<t>See <xref target="RFC4663"/>.</t>
</section> <!-- OIDreg -->
<section anchor="mailList" title="Mailing List Discussions">
<t>See <xref target="RFC4663"/>.</t>
</section> <!-- mailList -->
<section anchor="MIBdoct" title="IETF MIB Doctor Reviews">
<t>See <xref target="RFC4663"/>.</t>
</section> <!-- MIBdoct -->
</section> <!-- procs -->
<section anchor="sec" title="Security Considerations">
<t>This document records the transfer of ownership of ethernet-related
MIBs to IEEE 802.3.1 several years ago. The transfer has no security
implications.</t>
</section> <!-- sec -->
<section anchor="iana" title="IANA Considerations">
<t>This document requires no actions by IANA.</t>
</section> <!-- iana -->
<section anchor="IPRconsid" title="IPR Considerations">
<t>See <xref target="RFC4663"/>.</t>
</section> <!-- IPRconsid -->
</middle>
<!-- *****BODY ***** -->
<!-- *****BACK MATTER ***** -->
<back>
<references title="Informative References">
&RFC2108;
&RFC3621;
&RFC3635;
&RFC3637;
&RFC4663;
&RFC4836;
&RFC4837;
&RFC4878;
&RFC5066;
<reference anchor="IEEE802.3.1-2013">
<front>
<title>IEEE Standard for Management Information Base (MIB) Definitions for
Ethernet</title>
<author initials="" surname="">
<organization>IEEE Computer Society</organization>
</author>
<date month="June" year="2013"/>
</front>
</reference>
</references>
</back>
<!-- *****BACK MATTER ***** -->
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 12:32:25 |