Fwd: [OPSAWG] Fwd: I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt
Benoit Claise <[email protected]> Wed, 02 Jan 2013 14:45:27 +0100
| Newsgroups | gmane.ietf.hubmib |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------050500070003080509000408 Content-Type: multipart/alternative; boundary="------------020108000409040006020105" --------------020108000409040006020105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, Forwarded to this mailer, just in case... All discussions regarding this draft should take place in OPSAWG: "[email protected]" <[email protected]> Regards, Benoit -------- Original Message -------- Subject: [OPSAWG] Fwd: I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt Date: Wed, 02 Jan 2013 14:37:27 +0100 From: Benoit Claise <[email protected]> To: [email protected] <[email protected]> CC: Edward Beili <[email protected]>, Howard Frazier <[email protected]> Dear all, Here is some background information on this document, mainly taken from the IETF-IEEE coordination call meeting minutes (http://www.ietf.org/iesg/ieee/20121029/coordination.txt). 7. IETF Ethernet MIB, ADSL MIB and IEEE 802.3 7.1. Description In the transition process between the IETF and the IEEE the following documents were taken over by IEEE 802.3: RFC 2108 - Ethernet Repeater Devices RFC 3621 - Power Ethernet MIB RFC 3635 - Ethernet-like Interface Types RFC 3637 - Ethernet WAN Interface Sublayer RFC 4836 - Ethernet Medium Attachment Units (MAUs) RFC 4837 - Ethernet Passive Optical Networks (EPON) RFC 4878 - Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces RFC 5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces MIB The IF-CAP-STACK-MIB in RFC 5066 is generic and the IETF proposed to continue to be maintained by the IETF in a separate new document The IEEE 802.3 proposed to create an RFC that documents the issues related to the transition of the Ethernet MIB work to IEEE 802.3 similar to RFC 4663 which documents the transition of the Bridge MIB work to IEEE 802.1 - The OPSAWG was rechartered in October 2012 to include the two relevant documents 7.2. Relevant Documents - IEEE 802.3.1 Draft -http://datatracker.ietf.org/wg/opsawg/charter/ - TBD OPSAWG I-Ds 7.3. Owners - Benoit Claise, Dan Romascanu, Ed Beili (IETF), Howard Frazier (IEEE 802.3) 7.4. Action Items - Dan Romascanu will enter the Sponsor Ballot pool and enter a comment suggesting that the IEEE 802.3 take out the IEEE8023-IF-CAP-STACK-MIB from their document and refer the IF-CAP-STACK-MIB instead. - Ed Beili will write an I-D targeting standards track that obsoletes RFC 5066 and extract IF-CAP-STACK-MIB from RFC5056, with wording emphasizing the generic nature of this module - Ed Beili will write an I-D targeting informational RFC, similar to RFC 4663, with: a) Listing of all the RFCs obsoleted by the IEEE 802.3.1-2011 b) A table mapping the old IETF MIB names with the corresponding new IEEE ones c) Clarifications/rules on the IETF-IEEE interactions, mailing lists, reviews d) Clarifications on the intellectual property considerations The first version will be posted by Ed. Then Dan Romascanu and Howard Frazier will add IETF-IEEE interactions chapter. - Howard Frazier to add a EDITOR'S NOTE in the current IEEE MIB document, to explain the situation Regards, Benoit -------- Original Message -------- Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt Date: Wed, 02 Jan 2013 04:17:12 -0800 From: [email protected] To: [email protected] CC: [email protected] A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF. Title : Interface Stack Capability MIB Author(s) : Edward Beili Filename : draft-ietf-opsawg-rfc5066bis-00.txt Pages : 15 Date : 2012-12-25 Abstract: This document defines Management Information Base (MIB) module for use with network management protocols in TCP/IP-based internets. This document defines 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. This document obsoletes RFC 5066. It amends that specification by moving the entire EFM-CU- MIB module along with the relevant descriptive text, to a separate document, maintained by the Institute of Electrical and Electronics Engineers (IEEE) 802.3.1 working group. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5066bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-opsawg-rfc5066bis-00 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg --------------020108000409040006020105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Dear all,<br> <br> Forwarded to this mailer, just in case...<br> All discussions regarding this draft should take place in OPSAWG: <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">"[email protected]"</a> <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a><br> <br> Regards, Benoit<br> <div class="moz-forward-container"><br> <br> -------- Original Message -------- <table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject: </th> <td>[OPSAWG] Fwd: I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th> <td>Wed, 02 Jan 2013 14:37:27 +0100</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th> <td>Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC: </th> <td>Edward Beili <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>, Howard Frazier <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> </tbody> </table> <br> <br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> Dear all,<br> <br> Here is some background information on this document, mainly taken from the IETF-IEEE coordination call meeting minutes (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/ieee/20121029/coordination.txt">http://www.ietf.org/iesg/ieee/20121029/coordination.txt</a>).<br> <br> <pre>7. IETF Ethernet MIB, ADSL MIB and IEEE 802.3 7.1. Description In the transition process between the IETF and the IEEE the following documents were taken over by IEEE 802.3: RFC 2108 - Ethernet Repeater Devices RFC 3621 - Power Ethernet MIB RFC 3635 - Ethernet-like Interface Types RFC 3637 - Ethernet WAN Interface Sublayer RFC 4836 - Ethernet Medium Attachment Units (MAUs) RFC 4837 - Ethernet Passive Optical Networks (EPON) RFC 4878 - Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces RFC 5066 - Ethernet in the First Mile Copper (EFMCu) Interfaces MIB The IF-CAP-STACK-MIB in RFC 5066 is generic and the IETF proposed to continue to be maintained by the IETF in a separate new document The IEEE 802.3 proposed to create an RFC that documents the issues related to the transition of the Ethernet MIB work to IEEE 802.3 similar to RFC 4663 which documents the transition of the Bridge MIB work to IEEE 802.1 - The OPSAWG was rechartered in October 2012 to include the two relevant documents 7.2. Relevant Documents - IEEE 802.3.1 Draft - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/wg/opsawg/charter/">http://datatracker.ietf.org/wg/opsawg/charter/</a> - TBD OPSAWG I-Ds 7.3. Owners - Benoit Claise, Dan Romascanu, Ed Beili (IETF), Howard Frazier (IEEE 802.3) 7.4. Action Items - Dan Romascanu will enter the Sponsor Ballot pool and enter a comment suggesting that the IEEE 802.3 take out the IEEE8023-IF-CAP-STACK-MIB from their document and refer the IF-CAP-STACK-MIB instead. - Ed Beili will write an I-D targeting standards track that obsoletes RFC 5066 and extract IF-CAP-STACK-MIB from RFC5056, with wording emphasizing the generic nature of this module - Ed Beili will write an I-D targeting informational RFC, similar to RFC 4663, with: a) Listing of all the RFCs obsoleted by the IEEE 802.3.1-2011 b) A table mapping the old IETF MIB names with the corresponding new IEEE ones c) Clarifications/rules on the IETF-IEEE interactions, mailing lists, reviews d) Clarifications on the intellectual property considerations The first version will be posted by Ed. Then Dan Romascanu and Howard Frazier will add IETF-IEEE interactions chapter. - Howard Frazier to add a EDITOR'S NOTE in the current IEEE MIB document, to explain the situation</pre> <br> <div class="moz-forward-container">Regards, Benoit<br> -------- Original Message -------- <table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject: </th> <td>[OPSAWG] I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th> <td>Wed, 02 Jan 2013 04:17:12 -0800</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th> <td><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th> <td><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC: </th> <td><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></td> </tr> </tbody> </table> <br> <br> <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations and Management Area Working Group Working Group of the IETF. Title : Interface Stack Capability MIB Author(s) : Edward Beili Filename : draft-ietf-opsawg-rfc5066bis-00.txt Pages : 15 Date : 2012-12-25 Abstract: This document defines Management Information Base (MIB) module for use with network management protocols in TCP/IP-based internets. This document defines 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. This document obsoletes RFC 5066. It amends that specification by moving the entire EFM-CU- MIB module along with the relevant descriptive text, to a separate document, maintained by the Institute of Electrical and Electronics Engineers (IEEE) 802.3.1 working group. The IETF datatracker status page for this draft is: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5066bis">https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5066bis</a> There's also a htmlized version available at: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-opsawg-rfc5066bis-00">http://tools.ietf.org/html/draft-ietf-opsawg-rfc5066bis-00</a> Internet-Drafts are also available by anonymous FTP at: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a> _______________________________________________ OPSAWG mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/opsawg">https://www.ietf.org/mailman/listinfo/opsawg</a> </pre> <br> </div> <br> <br> </div> <br> </body> </html> --------------020108000409040006020105-- --------------050500070003080509000408 Content-Type: text/plain; charset=windows-1252; name="Attached Message Part" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Attached Message Part" _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg --------------050500070003080509000408 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hubmib mailing list [email protected] https://www.ietf.org/mailman/listinfo/hubmib --------------050500070003080509000408--