From bclaise@cisco.com Wed Jan 2 05:45:39 2013 Return-Path: X-Original-To: hubmib@ietfa.amsl.com Delivered-To: hubmib@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01B821F858C for ; Wed, 2 Jan 2013 05:45:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.406 X-Spam-Level: X-Spam-Status: No, score=-10.406 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19159Yflq8ya for ; Wed, 2 Jan 2013 05:45:38 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 6B33E21F858A for ; Wed, 2 Jan 2013 05:45:30 -0800 (PST) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r02DjTh0018990; Wed, 2 Jan 2013 14:45:29 +0100 (CET) Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r02DjRIj019283; Wed, 2 Jan 2013 14:45:27 +0100 (CET) Message-ID: <50E439F7.5080703@cisco.com> Date: Wed, 02 Jan 2013 14:45:27 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: hubmib@ietf.org References: <50E43817.1010407@cisco.com> In-Reply-To: <50E43817.1010407@cisco.com> X-Forwarded-Message-Id: <50E43817.1010407@cisco.com> Content-Type: multipart/mixed; boundary="------------050500070003080509000408" Cc: "opsawg-chairs@tools.ietf.org" Subject: [Hubmib] Fwd: [OPSAWG] Fwd: I-D Action: draft-ietf-opsawg-rfc5066bis-00.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 13:45:39 -0000 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: "opsawg@ietf.org" 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 To: opsawg@ietf.org CC: Edward Beili , Howard Frazier 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: internet-drafts@ietf.org To: i-d-announce@ietf.org CC: opsawg@ietf.org 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 OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg --------------020108000409040006020105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

Forwarded to this mailer, just in case...
All discussions regarding this draft should take place in OPSAWG: "opsawg@ietf.org" <opsawg@ietf.org>

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 <bclaise@cisco.com>
To: opsawg@ietf.org <opsawg@ietf.org>
CC: Edward Beili <EdwardB@actelis.com>, Howard Frazier <hfrazier@broadcom.com>


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: internet-drafts@ietf.org
To: i-d-announce@ietf.org
CC: opsawg@ietf.org 


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
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg




--------------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 OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg --------------050500070003080509000408--