From exim@www1.ietf.org Sat Nov 1 02:46:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18114 for ; Sat, 1 Nov 2003 02:46:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFqSR-0005kM-Qx for hubmib-archive@odin.ietf.org; Sat, 01 Nov 2003 02:46:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA17k3tq022091 for hubmib-archive@odin.ietf.org; Sat, 1 Nov 2003 02:46:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFqSP-0005k5-Nc; Sat, 01 Nov 2003 02:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFqRy-0005jN-Qf for hubmib@optimus.ietf.org; Sat, 01 Nov 2003 02:45:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18084 for ; Sat, 1 Nov 2003 02:45:22 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFqRu-00064d-00 for hubmib@ietf.org; Sat, 01 Nov 2003 02:45:30 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFqRt-00064a-00 for hubmib@ietf.org; Sat, 01 Nov 2003 02:45:29 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hA17jUv12856 for ; Fri, 31 Oct 2003 23:45:30 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 31 Oct 2003 23:45:29 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub Mib Subject: RE: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts, WG Meetings Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-1162166868-1067672175=:11374" Content-ID: Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---2133786286-1162166868-1067672175=:11374 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Colleagues, I forgot to metion this earlier, but it occurs to me that the EFM effort is not the only one that will define new standard MAU types. 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is opened up for modification to add new MAU types the WG may wish to consider adding support for 10GBASE-CX4 and 10GBASE-T media types. Attached below is an earlier message of mine on this subject. Mike ---2133786286-1162166868-1067672175=:11374 Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII Content-ID: Content-Description: [Hubmib] 10GBASE-CX4 and 10GBASE-T (fwd) Return-Path: Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13]) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA24894 for ; Tue, 14 Jan 2003 12:19:45 -0800 (envelope-from hubmib-admin@ietf.org) Received: from icicle.pobox.com (icicle-mx.pobox.com [199.26.64.83]) by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA35788 for ; Tue, 14 Jan 2003 12:19:45 -0800 (PST) (envelope-from hubmib-admin@ietf.org) Received: from www1.ietf.org (ietf.org [132.151.1.19]) by icicle.pobox.com (Postfix) with ESMTP id 0D47923DEB for ; Tue, 14 Jan 2003 15:19:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKGBJ28054; Tue, 14 Jan 2003 15:16:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKFBJ27982 for ; Tue, 14 Jan 2003 15:15:11 -0500 Received: from shell4.bayarea.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09690 for ; Tue, 14 Jan 2003 15:00:22 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA17746; Tue, 14 Jan 2003 12:03:42 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hub MIB folks, For those who aren't already aware, I'd like to bring your attention to the fact that there are two IEEE study groups at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 group is working on a 15 m shielded copper solution that will use the same PCS as does 10GBASE-LX4. The 10GBASE-T group is working on a 100 m UTP solution. Those who are interested can find more information on the 802.3 web site http://grouper.ieee.org/groups/802/3/ The 10GBASE-CX4 effort has, I believe, the much shorter timeline, and it appears that the impact on our documents will be minimal. In fact as far as I can tell, the only document that will be affected is the MAU-MIB document, and the changes to it will be confined to the following additions: [ ... ] dot3MauType10GigBaseCX4 OBJECT-IDENTITY STATUS current DESCRIPTION "X fiber over copper (per 802.3 section 54)" ::= { dot3MauType XX } -- NOTE: next unassigned value is 41 [ ... ] ifMauTypeListBits OBJECT-TYPE SYNTAX BITS { [ ... ] b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) [ ... ] } [ ... ] These would mirror the proposed changes to Clause 30, which you can find here: http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_annex30B.pdf While it is probably not be appropriate to include this stuff in the next MAU-MIB draft that includes the 802.3ae stuff, the changes are small enough that they should be able to go into a maintenance update without affecting time-in-grade, or else when then the document advances Draft Standard. The impact of 10GBASE-T is harder to gauge. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib ---2133786286-1162166868-1067672175=:11374-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sat Nov 1 03:34:41 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18113 for ; Sat, 1 Nov 2003 02:46:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFqSP-0005k5-Nc; Sat, 01 Nov 2003 02:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFqRy-0005jN-Qf for hubmib@optimus.ietf.org; Sat, 01 Nov 2003 02:45:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18084 for ; Sat, 1 Nov 2003 02:45:22 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFqRu-00064d-00 for hubmib@ietf.org; Sat, 01 Nov 2003 02:45:30 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFqRt-00064a-00 for hubmib@ietf.org; Sat, 01 Nov 2003 02:45:29 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hA17jUv12856 for ; Fri, 31 Oct 2003 23:45:30 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 31 Oct 2003 23:45:29 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub Mib Subject: RE: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts, WG Meetings Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-1162166868-1067672175=:11374" Content-ID: Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---2133786286-1162166868-1067672175=:11374 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Colleagues, I forgot to metion this earlier, but it occurs to me that the EFM effort is not the only one that will define new standard MAU types. 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is opened up for modification to add new MAU types the WG may wish to consider adding support for 10GBASE-CX4 and 10GBASE-T media types. Attached below is an earlier message of mine on this subject. Mike ---2133786286-1162166868-1067672175=:11374 Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII Content-ID: Content-Description: [Hubmib] 10GBASE-CX4 and 10GBASE-T (fwd) Return-Path: Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13]) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA24894 for ; Tue, 14 Jan 2003 12:19:45 -0800 (envelope-from hubmib-admin@ietf.org) Received: from icicle.pobox.com (icicle-mx.pobox.com [199.26.64.83]) by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA35788 for ; Tue, 14 Jan 2003 12:19:45 -0800 (PST) (envelope-from hubmib-admin@ietf.org) Received: from www1.ietf.org (ietf.org [132.151.1.19]) by icicle.pobox.com (Postfix) with ESMTP id 0D47923DEB for ; Tue, 14 Jan 2003 15:19:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKGBJ28054; Tue, 14 Jan 2003 15:16:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0EKFBJ27982 for ; Tue, 14 Jan 2003 15:15:11 -0500 Received: from shell4.bayarea.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09690 for ; Tue, 14 Jan 2003 15:00:22 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id MAA17746; Tue, 14 Jan 2003 12:03:42 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hub MIB folks, For those who aren't already aware, I'd like to bring your attention to the fact that there are two IEEE study groups at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 group is working on a 15 m shielded copper solution that will use the same PCS as does 10GBASE-LX4. The 10GBASE-T group is working on a 100 m UTP solution. Those who are interested can find more information on the 802.3 web site http://grouper.ieee.org/groups/802/3/ The 10GBASE-CX4 effort has, I believe, the much shorter timeline, and it appears that the impact on our documents will be minimal. In fact as far as I can tell, the only document that will be affected is the MAU-MIB document, and the changes to it will be confined to the following additions: [ ... ] dot3MauType10GigBaseCX4 OBJECT-IDENTITY STATUS current DESCRIPTION "X fiber over copper (per 802.3 section 54)" ::= { dot3MauType XX } -- NOTE: next unassigned value is 41 [ ... ] ifMauTypeListBits OBJECT-TYPE SYNTAX BITS { [ ... ] b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) [ ... ] } [ ... ] These would mirror the proposed changes to Clause 30, which you can find here: http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_annex30B.pdf While it is probably not be appropriate to include this stuff in the next MAU-MIB draft that includes the 802.3ae stuff, the changes are small enough that they should be able to go into a maintenance update without affecting time-in-grade, or else when then the document advances Draft Standard. The impact of 10GBASE-T is harder to gauge. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib ---2133786286-1162166868-1067672175=:11374-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Nov 3 15:55:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20837 for ; Mon, 3 Nov 2003 15:55:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlj5-0005wA-05; Mon, 03 Nov 2003 15:55:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGliY-0005uy-Rq for hubmib@optimus.ietf.org; Mon, 03 Nov 2003 15:54:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20774 for ; Mon, 3 Nov 2003 15:54:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGliX-0004M1-00 for hubmib@ietf.org; Mon, 03 Nov 2003 15:54:29 -0500 Received: from palrel13.hp.com ([156.153.255.238]) by ietf-mx with esmtp (Exim 4.12) id 1AGliW-0004Ly-00 for hubmib@ietf.org; Mon, 03 Nov 2003 15:54:28 -0500 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by palrel13.hp.com (Postfix) with ESMTP id CE9F41C0134A; Mon, 3 Nov 2003 12:54:23 -0800 (PST) Received: from rose.hp.com (ros54018fli.rose.hp.com [15.29.17.171]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id MAA18867; Mon, 3 Nov 2003 12:54:23 -0800 (PST) Message-ID: <3FA6C11E.3C0040DA@rose.hp.com> Date: Mon, 03 Nov 2003 12:57:02 -0800 From: John Flick X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "C. M. Heard" Cc: Hub Mib Subject: Re: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Mike, I do think it is appropriate to open up MAU MIB to add the types for EFM and for 10GBASE-CX4 and 10GBASE-T. In addition to the changes you noted for 10GBASE-CX4, we would need to add a new jack to the JackType TC = CX4 uses an IB4X connector. One caution here is that 10GBASE-T is alot less far along than the others, and I would not want to hold up a rev of this document for a stable 10GBASE-T specification. John "C. M. Heard" wrote: > > Colleagues, > > I forgot to metion this earlier, but it occurs to me that the EFM > effort is not the only one that will define new standard MAU types. > 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is > opened up for modification to add new MAU types the WG may wish to > consider adding support for 10GBASE-CX4 and 10GBASE-T media types. > Attached below is an earlier message of mine on this subject. > > Mike > > ---------------------------------------------------------------------------------------------------- > > Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T > Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) > From: "C. M. Heard" > To: Hub MIB > > Hub MIB folks, > > For those who aren't already aware, I'd like to bring your > attention to the fact that there are two IEEE study groups > at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 > group is working on a 15 m shielded copper solution that > will use the same PCS as does 10GBASE-LX4. The 10GBASE-T > group is working on a 100 m UTP solution. Those who are > interested can find more information on the 802.3 web site > http://grouper.ieee.org/groups/802/3/ > > The 10GBASE-CX4 effort has, I believe, the much shorter > timeline, and it appears that the impact on our documents > will be minimal. In fact as far as I can tell, the only > document that will be affected is the MAU-MIB document, > and the changes to it will be confined to the following > additions: > > [ ... ] > > dot3MauType10GigBaseCX4 OBJECT-IDENTITY > STATUS current > DESCRIPTION "X fiber over copper (per 802.3 section > 54)" > ::= { dot3MauType XX } -- NOTE: next unassigned value is 41 > > [ ... ] > > ifMauTypeListBits OBJECT-TYPE > SYNTAX BITS { > [ ... ] > b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) > [ ... ] > } > [ ... ] > > These would mirror the proposed changes to Clause 30, which you can > find here: > > http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_annex30B.pdf > > While it is probably not be appropriate to include this stuff in the > next MAU-MIB draft that includes the 802.3ae stuff, the changes are > small enough that they should be able to go into a maintenance update > without affecting time-in-grade, or else when then the document > advances Draft Standard. > > The impact of 10GBASE-T is harder to gauge. > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Nov 3 15:55:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20852 for ; Mon, 3 Nov 2003 15:55:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlj5-0005xc-Nb for hubmib-archive@odin.ietf.org; Mon, 03 Nov 2003 15:55:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Kt3rj022908 for hubmib-archive@odin.ietf.org; Mon, 3 Nov 2003 15:55:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGlj5-0005wA-05; Mon, 03 Nov 2003 15:55:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGliY-0005uy-Rq for hubmib@optimus.ietf.org; Mon, 03 Nov 2003 15:54:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20774 for ; Mon, 3 Nov 2003 15:54:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGliX-0004M1-00 for hubmib@ietf.org; Mon, 03 Nov 2003 15:54:29 -0500 Received: from palrel13.hp.com ([156.153.255.238]) by ietf-mx with esmtp (Exim 4.12) id 1AGliW-0004Ly-00 for hubmib@ietf.org; Mon, 03 Nov 2003 15:54:28 -0500 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by palrel13.hp.com (Postfix) with ESMTP id CE9F41C0134A; Mon, 3 Nov 2003 12:54:23 -0800 (PST) Received: from rose.hp.com (ros54018fli.rose.hp.com [15.29.17.171]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id MAA18867; Mon, 3 Nov 2003 12:54:23 -0800 (PST) Message-ID: <3FA6C11E.3C0040DA@rose.hp.com> Date: Mon, 03 Nov 2003 12:57:02 -0800 From: John Flick X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "C. M. Heard" Cc: Hub Mib Subject: Re: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Mike, I do think it is appropriate to open up MAU MIB to add the types for EFM and for 10GBASE-CX4 and 10GBASE-T. In addition to the changes you noted for 10GBASE-CX4, we would need to add a new jack to the JackType TC = CX4 uses an IB4X connector. One caution here is that 10GBASE-T is alot less far along than the others, and I would not want to hold up a rev of this document for a stable 10GBASE-T specification. John "C. M. Heard" wrote: > > Colleagues, > > I forgot to metion this earlier, but it occurs to me that the EFM > effort is not the only one that will define new standard MAU types. > 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is > opened up for modification to add new MAU types the WG may wish to > consider adding support for 10GBASE-CX4 and 10GBASE-T media types. > Attached below is an earlier message of mine on this subject. > > Mike > > ---------------------------------------------------------------------------------------------------- > > Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T > Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) > From: "C. M. Heard" > To: Hub MIB > > Hub MIB folks, > > For those who aren't already aware, I'd like to bring your > attention to the fact that there are two IEEE study groups > at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 > group is working on a 15 m shielded copper solution that > will use the same PCS as does 10GBASE-LX4. The 10GBASE-T > group is working on a 100 m UTP solution. Those who are > interested can find more information on the 802.3 web site > http://grouper.ieee.org/groups/802/3/ > > The 10GBASE-CX4 effort has, I believe, the much shorter > timeline, and it appears that the impact on our documents > will be minimal. In fact as far as I can tell, the only > document that will be affected is the MAU-MIB document, > and the changes to it will be confined to the following > additions: > > [ ... ] > > dot3MauType10GigBaseCX4 OBJECT-IDENTITY > STATUS current > DESCRIPTION "X fiber over copper (per 802.3 section > 54)" > ::= { dot3MauType XX } -- NOTE: next unassigned value is 41 > > [ ... ] > > ifMauTypeListBits OBJECT-TYPE > SYNTAX BITS { > [ ... ] > b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) > [ ... ] > } > [ ... ] > > These would mirror the proposed changes to Clause 30, which you can > find here: > > http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_annex30B.pdf > > While it is probably not be appropriate to include this stuff in the > next MAU-MIB draft that includes the 802.3ae stuff, the changes are > small enough that they should be able to go into a maintenance update > without affecting time-in-grade, or else when then the document > advances Draft Standard. > > The impact of 10GBASE-T is harder to gauge. > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Nov 4 07:23:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11576 for ; Tue, 4 Nov 2003 07:23:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH0D7-0000vm-3m; Tue, 04 Nov 2003 07:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH0Cb-0000pJ-9b for hubmib@optimus.ietf.org; Tue, 04 Nov 2003 07:22:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11487 for ; Tue, 4 Nov 2003 07:22:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH0Ca-0004PW-00 for hubmib@ietf.org; Tue, 04 Nov 2003 07:22:28 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AH0Ca-0004PJ-00 for hubmib@ietf.org; Tue, 04 Nov 2003 07:22:28 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hA4CLrFY006863 for ; Tue, 4 Nov 2003 07:21:54 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hA4CLoFY006832 for ; Tue, 4 Nov 2003 07:21:52 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings Date: Tue, 4 Nov 2003 14:22:18 +0200 Message-ID: Thread-Topic: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings Thread-Index: AcOiTMqxwWxS6PEVSoqBSc7L7tHh7wAdAdiA From: "Romascanu, Dan (Dan)" To: "John Flick" , "C. M. Heard" Cc: "Hub Mib" Content-Transfer-Encoding: quoted-printable Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable In order for this change to be performed, we need to add the following = to the Charter: 'The MAU MIB will be revised to include support for MAU types and jack = types for Ethernet First Mile and for 10 GB Ethernet copper'.=20 Also, the deliverables need to include the MAU MIB revisions. I suggest = time frames similar with the EFM MIBs.=20 Note the 'neutral' reference to copper 10G. If 10GBASE-T is late at = dinner and cannot provide a normative reference by the time the MAU MIB = is in last approval phases, we can take it out, so that the rest of the = work is not hold up.=20 If there are no abjections in the next week, I will forward officially = this proposal to Bert.=20 Regards, Dan > -----Original Message----- > From: John Flick [mailto:johnf@rose.hp.com] > Sent: 03 November, 2003 10:57 PM > To: C. M. Heard > Cc: Hub Mib > Subject: Re: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB=20 > Internet-Drafts,WG Meetings >=20 >=20 > Mike, >=20 > I do think it is appropriate to open up MAU MIB to add the types for > EFM and for 10GBASE-CX4 and 10GBASE-T. In addition to the changes > you noted for 10GBASE-CX4, we would need to add a new jack to the > JackType TC =3D CX4 uses an IB4X connector. One caution here is that > 10GBASE-T is alot less far along than the others, and I would not > want to hold up a rev of this document for a stable 10GBASE-T > specification. >=20 > John >=20 > "C. M. Heard" wrote: > >=20 > > Colleagues, > >=20 > > I forgot to metion this earlier, but it occurs to me that the EFM > > effort is not the only one that will define new standard MAU types. > > 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is > > opened up for modification to add new MAU types the WG may wish to > > consider adding support for 10GBASE-CX4 and 10GBASE-T media types. > > Attached below is an earlier message of mine on this subject. > >=20 > > Mike > >=20 > > =20 > -------------------------------------------------------------- > -------------------------------------- > >=20 > > Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T > > Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) > > From: "C. M. Heard" > > To: Hub MIB > >=20 > > Hub MIB folks, > >=20 > > For those who aren't already aware, I'd like to bring your > > attention to the fact that there are two IEEE study groups > > at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 > > group is working on a 15 m shielded copper solution that > > will use the same PCS as does 10GBASE-LX4. The 10GBASE-T > > group is working on a 100 m UTP solution. Those who are > > interested can find more information on the 802.3 web site > > http://grouper.ieee.org/groups/802/3/ > >=20 > > The 10GBASE-CX4 effort has, I believe, the much shorter > > timeline, and it appears that the impact on our documents > > will be minimal. In fact as far as I can tell, the only > > document that will be affected is the MAU-MIB document, > > and the changes to it will be confined to the following > > additions: > >=20 > > [ ... ] > >=20 > > dot3MauType10GigBaseCX4 OBJECT-IDENTITY > > STATUS current > > DESCRIPTION "X fiber over copper (per 802.3 section > > 54)" > > ::=3D { dot3MauType XX } -- NOTE: next unassigned=20 > value is 41 > >=20 > > [ ... ] > >=20 > > ifMauTypeListBits OBJECT-TYPE > > SYNTAX BITS { > > [ ... ] > > b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) > > [ ... ] > > } > > [ ... ] > >=20 > > These would mirror the proposed changes to Clause 30, which you can > > find here: > >=20 > >=20 http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_ann= ex30B.pdf >=20 > While it is probably not be appropriate to include this stuff in the > next MAU-MIB draft that includes the 802.3ae stuff, the changes are > small enough that they should be able to go into a maintenance update > without affecting time-in-grade, or else when then the document > advances Draft Standard. >=20 > The impact of 10GBASE-T is harder to gauge. >=20 > Mike Heard >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Nov 4 07:23:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11591 for ; Tue, 4 Nov 2003 07:23:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH0D8-0000wP-49 for hubmib-archive@odin.ietf.org; Tue, 04 Nov 2003 07:23:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4CN1GQ003608 for hubmib-archive@odin.ietf.org; Tue, 4 Nov 2003 07:23:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH0D7-0000vm-3m; Tue, 04 Nov 2003 07:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH0Cb-0000pJ-9b for hubmib@optimus.ietf.org; Tue, 04 Nov 2003 07:22:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11487 for ; Tue, 4 Nov 2003 07:22:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH0Ca-0004PW-00 for hubmib@ietf.org; Tue, 04 Nov 2003 07:22:28 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AH0Ca-0004PJ-00 for hubmib@ietf.org; Tue, 04 Nov 2003 07:22:28 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hA4CLrFY006863 for ; Tue, 4 Nov 2003 07:21:54 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hA4CLoFY006832 for ; Tue, 4 Nov 2003 07:21:52 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings Date: Tue, 4 Nov 2003 14:22:18 +0200 Message-ID: Thread-Topic: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB Internet-Drafts,WG Meetings Thread-Index: AcOiTMqxwWxS6PEVSoqBSc7L7tHh7wAdAdiA From: "Romascanu, Dan (Dan)" To: "John Flick" , "C. M. Heard" Cc: "Hub Mib" Content-Transfer-Encoding: quoted-printable Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable In order for this change to be performed, we need to add the following = to the Charter: 'The MAU MIB will be revised to include support for MAU types and jack = types for Ethernet First Mile and for 10 GB Ethernet copper'.=20 Also, the deliverables need to include the MAU MIB revisions. I suggest = time frames similar with the EFM MIBs.=20 Note the 'neutral' reference to copper 10G. If 10GBASE-T is late at = dinner and cannot provide a normative reference by the time the MAU MIB = is in last approval phases, we can take it out, so that the rest of the = work is not hold up.=20 If there are no abjections in the next week, I will forward officially = this proposal to Bert.=20 Regards, Dan > -----Original Message----- > From: John Flick [mailto:johnf@rose.hp.com] > Sent: 03 November, 2003 10:57 PM > To: C. M. Heard > Cc: Hub Mib > Subject: Re: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB=20 > Internet-Drafts,WG Meetings >=20 >=20 > Mike, >=20 > I do think it is appropriate to open up MAU MIB to add the types for > EFM and for 10GBASE-CX4 and 10GBASE-T. In addition to the changes > you noted for 10GBASE-CX4, we would need to add a new jack to the > JackType TC =3D CX4 uses an IB4X connector. One caution here is that > 10GBASE-T is alot less far along than the others, and I would not > want to hold up a rev of this document for a stable 10GBASE-T > specification. >=20 > John >=20 > "C. M. Heard" wrote: > >=20 > > Colleagues, > >=20 > > I forgot to metion this earlier, but it occurs to me that the EFM > > effort is not the only one that will define new standard MAU types. > > 10GBASE-CX4 and 10GBASE-T will also do that. So if the MAU MIB is > > opened up for modification to add new MAU types the WG may wish to > > consider adding support for 10GBASE-CX4 and 10GBASE-T media types. > > Attached below is an earlier message of mine on this subject. > >=20 > > Mike > >=20 > > =20 > -------------------------------------------------------------- > -------------------------------------- > >=20 > > Subject: [Hubmib] 10GBASE-CX4 and 10GBASE-T > > Date: Tue, 14 Jan 2003 12:03:41 -0800 (PST) > > From: "C. M. Heard" > > To: Hub MIB > >=20 > > Hub MIB folks, > >=20 > > For those who aren't already aware, I'd like to bring your > > attention to the fact that there are two IEEE study groups > > at work on new PMDs for 10 Gb/s Ethernet. The 10GBASE-CX4 > > group is working on a 15 m shielded copper solution that > > will use the same PCS as does 10GBASE-LX4. The 10GBASE-T > > group is working on a 100 m UTP solution. Those who are > > interested can find more information on the 802.3 web site > > http://grouper.ieee.org/groups/802/3/ > >=20 > > The 10GBASE-CX4 effort has, I believe, the much shorter > > timeline, and it appears that the impact on our documents > > will be minimal. In fact as far as I can tell, the only > > document that will be affected is the MAU-MIB document, > > and the changes to it will be confined to the following > > additions: > >=20 > > [ ... ] > >=20 > > dot3MauType10GigBaseCX4 OBJECT-IDENTITY > > STATUS current > > DESCRIPTION "X fiber over copper (per 802.3 section > > 54)" > > ::=3D { dot3MauType XX } -- NOTE: next unassigned=20 > value is 41 > >=20 > > [ ... ] > >=20 > > ifMauTypeListBits OBJECT-TYPE > > SYNTAX BITS { > > [ ... ] > > b10GbaseCX4(XX), -- 10GBASE-CX4 (see NOTE above) > > [ ... ] > > } > > [ ... ] > >=20 > > These would mirror the proposed changes to Clause 30, which you can > > find here: > >=20 > >=20 http://grouper.ieee.org/groups/802/3/10GBCX4/public/jan03/WP2p0_cls30_ann= ex30B.pdf >=20 > While it is probably not be appropriate to include this stuff in the > next MAU-MIB draft that includes the 802.3ae stuff, the changes are > small enough that they should be able to go into a maintenance update > without affecting time-in-grade, or else when then the document > advances Draft Standard. >=20 > The impact of 10GBASE-T is harder to gauge. >=20 > Mike Heard >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Nov 27 11:43:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12439 for ; Thu, 27 Nov 2003 11:43:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APPEL-0000r4-08; Thu, 27 Nov 2003 11:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APPDL-0000qA-KR for hubmib@optimus.ietf.org; Thu, 27 Nov 2003 11:41:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12413 for ; Thu, 27 Nov 2003 11:41:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APPDK-0002Xo-00 for hubmib@ietf.org; Thu, 27 Nov 2003 11:41:58 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1APPDK-0002Xl-00 for hubmib@ietf.org; Thu, 27 Nov 2003 11:41:58 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hARGfMFo028855 for ; Thu, 27 Nov 2003 11:41:22 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hARGfKFo028839 for ; Thu, 27 Nov 2003 11:41:21 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3B505.5DCC1BFF" Date: Thu, 27 Nov 2003 18:41:54 +0200 Message-ID: Thread-Topic: Hubmib WG - EFM MIBs Status Thread-Index: AcO1BVyJhL69jC04Tmuuj+gqWyjBnQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] Hubmib WG - EFM MIBs Status Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C3B505.5DCC1BFF Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable A short update about the WG Status. The first round of individual submissions Internet-Drafts is out for a = while: = http://www.ietf.org/internet-drafts/draft-squire-hubmib-efm-mib-00.txt = http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mib-00.txt = http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-mib-00.txt= We has a fair amount of comments and discussions until now. More is = better, so I suggest that as many people as possible read and send = comments to hubmib@ietf.org, until 12/12. By that time, we should allow = to the editors to incorporate these comments in the next round of = drafts, which according to the schedules in the charter should be issued = until the end of December. These will be already official WG submissions = (draft-ietf-hubmib-efm-....) We have been discussing about a possible interim meeting co-located with = the January Vancouver 802.3 Interim. As I understand, right now it is = not certain that IEEE 802.3ah will meet in Vancouver. When we will know = for sure, in about one week, we will discuss on the list and make the = appropriate announcement.=20 Regards, Dan ------_=_NextPart_001_01C3B505.5DCC1BFF Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Hubmib WG - EFM MIBs Status

A short update about the WG = Status.

The first round of individual = submissions Internet-Drafts is out for a while:


   http://www.ietf.org/internet-drafts/draft-squire-hubmib-efm-mib-00= .txt

   http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mi= b-00.txt

   http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-= mib-00.txt

We has a fair amount of = comments and discussions until now. More is better, so I suggest that as = many people as possible read and send comments to hubmib@ietf.org, until = 12/12. By that time, we should allow to the editors to incorporate these = comments in the next round of drafts, which according to the schedules = in the charter should be issued until the end of December. These will be = already official WG submissions (draft-ietf-hubmib-efm-....)

We have been discussing about = a possible interim meeting co-located with the January Vancouver 802.3 = Interim. As I understand, right now it is not certain that IEEE 802.3ah = will meet in Vancouver. When we will know for sure, in about one week, = we will discuss on the list and make the appropriate announcement. =

Regards,

Dan

------_=_NextPart_001_01C3B505.5DCC1BFF-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Nov 27 12:29:16 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12441 for ; Thu, 27 Nov 2003 11:43:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APPEM-0000rg-2a for hubmib-archive@odin.ietf.org; Thu, 27 Nov 2003 11:43:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hARGh26T003316 for hubmib-archive@odin.ietf.org; Thu, 27 Nov 2003 11:43:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APPEL-0000r4-08; Thu, 27 Nov 2003 11:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1APPDL-0000qA-KR for hubmib@optimus.ietf.org; Thu, 27 Nov 2003 11:41:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12413 for ; Thu, 27 Nov 2003 11:41:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1APPDK-0002Xo-00 for hubmib@ietf.org; Thu, 27 Nov 2003 11:41:58 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1APPDK-0002Xl-00 for hubmib@ietf.org; Thu, 27 Nov 2003 11:41:58 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hARGfMFo028855 for ; Thu, 27 Nov 2003 11:41:22 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hARGfKFo028839 for ; Thu, 27 Nov 2003 11:41:21 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3B505.5DCC1BFF" Date: Thu, 27 Nov 2003 18:41:54 +0200 Message-ID: Thread-Topic: Hubmib WG - EFM MIBs Status Thread-Index: AcO1BVyJhL69jC04Tmuuj+gqWyjBnQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] Hubmib WG - EFM MIBs Status Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C3B505.5DCC1BFF Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable A short update about the WG Status. The first round of individual submissions Internet-Drafts is out for a = while: = http://www.ietf.org/internet-drafts/draft-squire-hubmib-efm-mib-00.txt = http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mib-00.txt = http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-mib-00.txt= We has a fair amount of comments and discussions until now. More is = better, so I suggest that as many people as possible read and send = comments to hubmib@ietf.org, until 12/12. By that time, we should allow = to the editors to incorporate these comments in the next round of = drafts, which according to the schedules in the charter should be issued = until the end of December. These will be already official WG submissions = (draft-ietf-hubmib-efm-....) We have been discussing about a possible interim meeting co-located with = the January Vancouver 802.3 Interim. As I understand, right now it is = not certain that IEEE 802.3ah will meet in Vancouver. When we will know = for sure, in about one week, we will discuss on the list and make the = appropriate announcement.=20 Regards, Dan ------_=_NextPart_001_01C3B505.5DCC1BFF Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Hubmib WG - EFM MIBs Status

A short update about the WG = Status.

The first round of individual = submissions Internet-Drafts is out for a while:


   http://www.ietf.org/internet-drafts/draft-squire-hubmib-efm-mib-00= .txt

   http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mi= b-00.txt

   http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-= mib-00.txt

We has a fair amount of = comments and discussions until now. More is better, so I suggest that as = many people as possible read and send comments to hubmib@ietf.org, until = 12/12. By that time, we should allow to the editors to incorporate these = comments in the next round of drafts, which according to the schedules = in the charter should be issued until the end of December. These will be = already official WG submissions (draft-ietf-hubmib-efm-....)

We have been discussing about = a possible interim meeting co-located with the January Vancouver 802.3 = Interim. As I understand, right now it is not certain that IEEE 802.3ah = will meet in Vancouver. When we will know for sure, in about one week, = we will discuss on the list and make the appropriate announcement. =

Regards,

Dan

------_=_NextPart_001_01C3B505.5DCC1BFF-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib