From hubmib-admin@ietf.org Mon Dec 8 06:47:14 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06280 for ; Mon, 8 Dec 2003 06:47:14 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATJqv-0002PG-4R; Mon, 08 Dec 2003 06:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATJqs-0002P5-9E for hubmib@optimus.ietf.org; Mon, 08 Dec 2003 06:46:58 -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 GAA06259 for ; Mon, 8 Dec 2003 06:46:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATJqo-0001bk-00 for hubmib@ietf.org; Mon, 08 Dec 2003 06:46:54 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1ATJqn-0001bg-00 for hubmib@ietf.org; Mon, 08 Dec 2003 06:46:53 -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 hB8BkGFo026873 for ; Mon, 8 Dec 2003 06:46:16 -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 hB8BkEFo026846 for ; Mon, 8 Dec 2003 06:46:15 -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_01C3BD80.F863B838" Date: Mon, 8 Dec 2003 13:46:51 +0200 Message-ID: Thread-Topic: Interim Meeting Co-located with the IEEE 802.3ah Interim. Thread-Index: AcO9gPhC8harHeOJTrWDS5xzjkUjJQ== From: "Romascanu, Dan (Dan)" To: Cc: "Howard Frazier" Subject: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Interim. 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_01C3BD80.F863B838 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Howard Frazier, the Chair of IEEE 802.3ah announced us that IEEE 802.3ah = will meet in Vancouver in the week of 1/12/2004. An official = announcement will go out soon. If so, the option of organizing a = co-located interim meeting of the Ethernet Interfaces and Hub MIB WG is = real. Howard and the IEEE 802 can support us with meeting facilities at = the same location where IEEE 802.3ah meet, which is Fairmont Hotel = Vancouver. However, we would need to pay the participation fee at the = IEEE meeting. Since this is an interim meeting for all of the 802 = working groups, the registration fee for the meeting has been set by the = 802 treasurer, and will be $300. This fee buys you the right to attend = any of the IEEE 802 meetings planned during the week. More information = about the meeting can be found at: http://www.ieee802.org/meeting/index.html We need to make a decision in the next couple of days in order to have = the meeting announcement going out until Friday - one month before the = meeting date. In order to decide, we need to know how many people intent = to attend. Please send an email to me on this respect until Wednesday = morning 8AM PT the latest. Please do it, even if you intended to attend = anyway the IEEE meeting, or if you would be coming especially because of = the IETF Ethernet Interfaces and Hub MIB WG interim. Thanks and Regards, Dan ------_=_NextPart_001_01C3BD80.F863B838 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Interim Meeting Co-located with the IEEE 802.3ah Interim.

Howard Frazier, the Chair of = IEEE 802.3ah announced us that IEEE 802.3ah will meet in Vancouver in = the week of 1/12/2004. An official announcement will go out soon. If so, = the option of organizing a co-located interim meeting of the Ethernet = Interfaces and Hub MIB WG is real. Howard and the IEEE 802 can support = us with meeting facilities at the same location where IEEE 802.3ah meet, = which is Fairmont Hotel Vancouver. However, we would need to pay the = participation fee at the IEEE meeting. Since this is an interim meeting for all of the 802 = working groups, the registration fee for the meeting has been set by the = 802 treasurer, and will be $300.  This fee buys you the right to = attend any of the IEEE 802 meetings planned during the week. More = information about the meeting can be found at:

http://www.ieee802.org= /meeting/index.html

We need to make a decision in = the next couple of days in order to have the meeting announcement going = out until Friday - one month before the meeting date. In order to = decide, we need to know how many people intent to attend. Please send an = email to me on this respect until Wednesday morning 8AM PT the latest. = Please do it, even if you intended to attend anyway the IEEE meeting, or = if you would be coming especially because of the IETF Ethernet = Interfaces and Hub MIB WG interim.

Thanks and = Regards,

Dan



------_=_NextPart_001_01C3BD80.F863B838-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 8 06:47:14 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06282 for ; Mon, 8 Dec 2003 06:47:14 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATJqv-0002Pf-Tt for hubmib-archive@odin.ietf.org; Mon, 08 Dec 2003 06:47:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8Bl1ce009267 for hubmib-archive@odin.ietf.org; Mon, 8 Dec 2003 06:47:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATJqv-0002PG-4R; Mon, 08 Dec 2003 06:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATJqs-0002P5-9E for hubmib@optimus.ietf.org; Mon, 08 Dec 2003 06:46:58 -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 GAA06259 for ; Mon, 8 Dec 2003 06:46:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATJqo-0001bk-00 for hubmib@ietf.org; Mon, 08 Dec 2003 06:46:54 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1ATJqn-0001bg-00 for hubmib@ietf.org; Mon, 08 Dec 2003 06:46:53 -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 hB8BkGFo026873 for ; Mon, 8 Dec 2003 06:46:16 -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 hB8BkEFo026846 for ; Mon, 8 Dec 2003 06:46:15 -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_01C3BD80.F863B838" Date: Mon, 8 Dec 2003 13:46:51 +0200 Message-ID: Thread-Topic: Interim Meeting Co-located with the IEEE 802.3ah Interim. Thread-Index: AcO9gPhC8harHeOJTrWDS5xzjkUjJQ== From: "Romascanu, Dan (Dan)" To: Cc: "Howard Frazier" Subject: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Interim. 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_01C3BD80.F863B838 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Howard Frazier, the Chair of IEEE 802.3ah announced us that IEEE 802.3ah = will meet in Vancouver in the week of 1/12/2004. An official = announcement will go out soon. If so, the option of organizing a = co-located interim meeting of the Ethernet Interfaces and Hub MIB WG is = real. Howard and the IEEE 802 can support us with meeting facilities at = the same location where IEEE 802.3ah meet, which is Fairmont Hotel = Vancouver. However, we would need to pay the participation fee at the = IEEE meeting. Since this is an interim meeting for all of the 802 = working groups, the registration fee for the meeting has been set by the = 802 treasurer, and will be $300. This fee buys you the right to attend = any of the IEEE 802 meetings planned during the week. More information = about the meeting can be found at: http://www.ieee802.org/meeting/index.html We need to make a decision in the next couple of days in order to have = the meeting announcement going out until Friday - one month before the = meeting date. In order to decide, we need to know how many people intent = to attend. Please send an email to me on this respect until Wednesday = morning 8AM PT the latest. Please do it, even if you intended to attend = anyway the IEEE meeting, or if you would be coming especially because of = the IETF Ethernet Interfaces and Hub MIB WG interim. Thanks and Regards, Dan ------_=_NextPart_001_01C3BD80.F863B838 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Interim Meeting Co-located with the IEEE 802.3ah Interim.

Howard Frazier, the Chair of = IEEE 802.3ah announced us that IEEE 802.3ah will meet in Vancouver in = the week of 1/12/2004. An official announcement will go out soon. If so, = the option of organizing a co-located interim meeting of the Ethernet = Interfaces and Hub MIB WG is real. Howard and the IEEE 802 can support = us with meeting facilities at the same location where IEEE 802.3ah meet, = which is Fairmont Hotel Vancouver. However, we would need to pay the = participation fee at the IEEE meeting. Since this is an interim meeting for all of the 802 = working groups, the registration fee for the meeting has been set by the = 802 treasurer, and will be $300.  This fee buys you the right to = attend any of the IEEE 802 meetings planned during the week. More = information about the meeting can be found at:

http://www.ieee802.org= /meeting/index.html

We need to make a decision in = the next couple of days in order to have the meeting announcement going = out until Friday - one month before the meeting date. In order to = decide, we need to know how many people intent to attend. Please send an = email to me on this respect until Wednesday morning 8AM PT the latest. = Please do it, even if you intended to attend anyway the IEEE meeting, or = if you would be coming especially because of the IETF Ethernet = Interfaces and Hub MIB WG interim.

Thanks and = Regards,

Dan



------_=_NextPart_001_01C3BD80.F863B838-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Dec 9 12:08:15 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03860 for ; Tue, 9 Dec 2003 12:08:15 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATlL7-00072o-As; Tue, 09 Dec 2003 12:08:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATlE7-00066Y-Us for hubmib@optimus.ietf.org; Tue, 09 Dec 2003 12:00:48 -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 MAA03580 for ; Tue, 9 Dec 2003 12:00:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATlE3-0003CY-00 for hubmib@ietf.org; Tue, 09 Dec 2003 12:00:43 -0500 Received: from columba1.eur.3com.com ([161.71.171.235]) by ietf-mx with esmtp (Exim 4.12) id 1ATlDx-0003CR-00 for hubmib@ietf.org; Tue, 09 Dec 2003 12:00:38 -0500 Received: from toucana.eur.3com.com (eurelay.eur.3com.com [140.204.220.50]) by columba1.eur.3com.com with ESMTP id hB9Gxe4q025321; Tue, 9 Dec 2003 16:59:40 GMT Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id hB9H2Tja001607; Tue, 9 Dec 2003 17:02:29 GMT Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256DF7.005D5FFF ; Tue, 9 Dec 2003 16:59:54 +0000 X-Lotus-FromDomain: 3COM From: "David Law" To: hubmib@ietf.org cc: "Howard Frazier" Message-ID: <80256DF7.005D5EF4.00@notesmta.eur.3com.com> Date: Tue, 9 Dec 2003 17:04:34 +0000 Subject: Re: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Interim. Mime-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable 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 All, Further to Dan's e-mail below the IEEE 802.3 Interim meeting notice is = available on the IEEE 802.3 web site at the URL -[ http://www.ieee802.org/3/interims/vancouver_04.html ]. Best regards, David Law "Romascanu, Dan (Dan)" @ietf.org on 08/12/2003 11:4= 6:51 Sent by: hubmib-admin@ietf.org To: cc: "Howard Frazier" Subject: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Int= erim. Howard Frazier, the Chair of IEEE 802.3ah announced us that IEEE 802.3a= h will meet in Vancouver in the week of 1/12/2004. An official announcement wi= ll go out soon. If so, the option of organizing a co-located interim meeting of t= he Ethernet Interfaces and Hub MIB WG is real. Howard and the IEEE 802 can= support us with meeting facilities at the same location where IEEE 802.3ah meet= , which is Fairmont Hotel Vancouver. However, we would need to pay the particip= ation fee at the IEEE meeting. Since this is an interim meeting for all of the 80= 2 working groups, the registration fee for the meeting has been set by the 802 tr= easurer, and will be $300.=A0 This fee buys you the right to attend any of the I= EEE 802 meetings planned during the week. More information about the meeting ca= n be found at: http://www.ieee802.org/meeting/index.html We need to make a decision in the next couple of days in order to have = the meeting announcement going out until Friday - one month before the meet= ing date. In order to decide, we need to know how many people intent to attend. P= lease send an email to me on this respect until Wednesday morning 8AM PT the = latest. Please do it, even if you intended to attend anyway the IEEE meeting, o= r if you would be coming especially because of the IETF Ethernet Interfaces and = Hub MIB WG interim. Thanks and Regards, Dan = _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Dec 9 12:08:16 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03875 for ; Tue, 9 Dec 2003 12:08:16 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATlL8-00073J-AJ for hubmib-archive@odin.ietf.org; Tue, 09 Dec 2003 12:08:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9H82w4027095 for hubmib-archive@odin.ietf.org; Tue, 9 Dec 2003 12:08:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATlL7-00072o-As; Tue, 09 Dec 2003 12:08:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATlE7-00066Y-Us for hubmib@optimus.ietf.org; Tue, 09 Dec 2003 12:00:48 -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 MAA03580 for ; Tue, 9 Dec 2003 12:00:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATlE3-0003CY-00 for hubmib@ietf.org; Tue, 09 Dec 2003 12:00:43 -0500 Received: from columba1.eur.3com.com ([161.71.171.235]) by ietf-mx with esmtp (Exim 4.12) id 1ATlDx-0003CR-00 for hubmib@ietf.org; Tue, 09 Dec 2003 12:00:38 -0500 Received: from toucana.eur.3com.com (eurelay.eur.3com.com [140.204.220.50]) by columba1.eur.3com.com with ESMTP id hB9Gxe4q025321; Tue, 9 Dec 2003 16:59:40 GMT Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id hB9H2Tja001607; Tue, 9 Dec 2003 17:02:29 GMT Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256DF7.005D5FFF ; Tue, 9 Dec 2003 16:59:54 +0000 X-Lotus-FromDomain: 3COM From: "David Law" To: hubmib@ietf.org cc: "Howard Frazier" Message-ID: <80256DF7.005D5EF4.00@notesmta.eur.3com.com> Date: Tue, 9 Dec 2003 17:04:34 +0000 Subject: Re: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Interim. Mime-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable 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 All, Further to Dan's e-mail below the IEEE 802.3 Interim meeting notice is = available on the IEEE 802.3 web site at the URL -[ http://www.ieee802.org/3/interims/vancouver_04.html ]. Best regards, David Law "Romascanu, Dan (Dan)" @ietf.org on 08/12/2003 11:4= 6:51 Sent by: hubmib-admin@ietf.org To: cc: "Howard Frazier" Subject: [Hubmib] Interim Meeting Co-located with the IEEE 802.3ah Int= erim. Howard Frazier, the Chair of IEEE 802.3ah announced us that IEEE 802.3a= h will meet in Vancouver in the week of 1/12/2004. An official announcement wi= ll go out soon. If so, the option of organizing a co-located interim meeting of t= he Ethernet Interfaces and Hub MIB WG is real. Howard and the IEEE 802 can= support us with meeting facilities at the same location where IEEE 802.3ah meet= , which is Fairmont Hotel Vancouver. However, we would need to pay the particip= ation fee at the IEEE meeting. Since this is an interim meeting for all of the 80= 2 working groups, the registration fee for the meeting has been set by the 802 tr= easurer, and will be $300.=A0 This fee buys you the right to attend any of the I= EEE 802 meetings planned during the week. More information about the meeting ca= n be found at: http://www.ieee802.org/meeting/index.html We need to make a decision in the next couple of days in order to have = the meeting announcement going out until Friday - one month before the meet= ing date. In order to decide, we need to know how many people intent to attend. P= lease send an email to me on this respect until Wednesday morning 8AM PT the = latest. Please do it, even if you intended to attend anyway the IEEE meeting, o= r if you would be coming especially because of the IETF Ethernet Interfaces and = Hub MIB WG interim. Thanks and Regards, Dan = _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Dec 10 12:57:57 2003 Return-Path: Received: from optimus.ietf.org by ietf.org.ietf.org (SMI-8.6/SMI-SVR4) id MAA23993; Wed, 10 Dec 2003 12:57:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AU8b2-00050P-KY; Wed, 10 Dec 2003 12:58:00 -0500 Received: from ns.cnri.reston.va.us ([132.151.1.1]) by optimus.ietf.org with esmtp (Exim 4.20) id 1AU8aR-000503-3L for hubmib@optimus.cnri.reston.va.us; Wed, 10 Dec 2003 12:57:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org.ietf.org) by ns.cnri.reston.va.us with smtp (Exim 4.20) id 1AU8aP-0004n3-M1 for hubmib@optimus; Wed, 10 Dec 2003 12:57:21 -0500 Received: from ietf-mx by ietf.org.ietf.org (SMI-8.6/SMI-SVR4) id MAA23986; Wed, 10 Dec 2003 12:57:17 -0500 Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AU8aO-0004mG-00 for hubmib@ietf.org; Wed, 10 Dec 2003 12:57:20 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AU8aN-0004mD-00 for hubmib@ietf.org; Wed, 10 Dec 2003 12:57:19 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBAHsTGa022292 for ; Wed, 10 Dec 2003 12:54:29 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBAHsAGa021967 for ; Wed, 10 Dec 2003 12:54:12 -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_01C3BF47.01A8A256" Date: Wed, 10 Dec 2003 19:56:58 +0200 Message-ID: Thread-Topic: No Interim Meeting Thread-Index: AcO/RwGWY2XJ70nQRgmyImg8c3jlcQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] No Interim Meeting 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-length: 2728 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3BF47.01A8A256 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable The response to the idea of an Interim Meeting of the Ethernet = Interfaces and Hub MIB WG co-located with the January IEEE Interim = meeting in Vancouver was less than enthusiastic. I received only a = handful of confirmations of participation, less than the critical number = to justify calling for a meeting. So, there will be no interim meeting = of the WG in Vancouver.=20 We will however try to stick as close as possible to the schedule in the = charter. I would like to require the editors to start working on the = next round of Internet-Drafts, which should be the = draft-hubmib-efm-....-00 versions, due to the end of the month. Please = help the editors improve the quality of their documents by reading the = current drafts and sending your comments by the end of this week. This = is what I intent to do as well. Regards, Dan ------_=_NextPart_001_01C3BF47.01A8A256 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable No Interim Meeting

The response to the idea of = an Interim Meeting of the Ethernet Interfaces and Hub MIB WG co-located = with the January IEEE Interim meeting in Vancouver was less than = enthusiastic. I received only a handful of confirmations of = participation, less than the critical number to justify calling for a = meeting. So, there will be no interim meeting of the WG in Vancouver. =

We will however try to stick = as close as possible to the schedule in the charter. I would like to = require the editors to start working on the next round of = Internet-Drafts, which should be the draft-hubmib-efm-....-00 versions, = due to the end of the month. Please help the editors improve the quality = of their documents by reading the current drafts and sending your = comments by the end of this week. This is what I intent to do as = well.

Regards,

Dan

------_=_NextPart_001_01C3BF47.01A8A256-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Wed Dec 10 12:59:44 2003 Return-Path: Received: from optimus.ietf.org by ietf.org.ietf.org (SMI-8.6/SMI-SVR4) id MAA23995; Wed, 10 Dec 2003 12:57:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AU8b3-00050j-0x for hubmib-archive@odin.ietf.org; Wed, 10 Dec 2003 12:58:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBAHw0ia019255 for hubmib-archive@odin.ietf.org; Wed, 10 Dec 2003 12:58:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AU8b2-00050P-KY; Wed, 10 Dec 2003 12:58:00 -0500 Received: from ns.cnri.reston.va.us ([132.151.1.1]) by optimus.ietf.org with esmtp (Exim 4.20) id 1AU8aR-000503-3L for hubmib@optimus.cnri.reston.va.us; Wed, 10 Dec 2003 12:57:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org.ietf.org) by ns.cnri.reston.va.us with smtp (Exim 4.20) id 1AU8aP-0004n3-M1 for hubmib@optimus; Wed, 10 Dec 2003 12:57:21 -0500 Received: from ietf-mx by ietf.org.ietf.org (SMI-8.6/SMI-SVR4) id MAA23986; Wed, 10 Dec 2003 12:57:17 -0500 Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AU8aO-0004mG-00 for hubmib@ietf.org; Wed, 10 Dec 2003 12:57:20 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AU8aN-0004mD-00 for hubmib@ietf.org; Wed, 10 Dec 2003 12:57:19 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBAHsTGa022292 for ; Wed, 10 Dec 2003 12:54:29 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBAHsAGa021967 for ; Wed, 10 Dec 2003 12:54:12 -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_01C3BF47.01A8A256" Date: Wed, 10 Dec 2003 19:56:58 +0200 Message-ID: Thread-Topic: No Interim Meeting Thread-Index: AcO/RwGWY2XJ70nQRgmyImg8c3jlcQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] No Interim Meeting 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-length: 2729 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3BF47.01A8A256 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable The response to the idea of an Interim Meeting of the Ethernet = Interfaces and Hub MIB WG co-located with the January IEEE Interim = meeting in Vancouver was less than enthusiastic. I received only a = handful of confirmations of participation, less than the critical number = to justify calling for a meeting. So, there will be no interim meeting = of the WG in Vancouver.=20 We will however try to stick as close as possible to the schedule in the = charter. I would like to require the editors to start working on the = next round of Internet-Drafts, which should be the = draft-hubmib-efm-....-00 versions, due to the end of the month. Please = help the editors improve the quality of their documents by reading the = current drafts and sending your comments by the end of this week. This = is what I intent to do as well. Regards, Dan ------_=_NextPart_001_01C3BF47.01A8A256 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable No Interim Meeting

The response to the idea of = an Interim Meeting of the Ethernet Interfaces and Hub MIB WG co-located = with the January IEEE Interim meeting in Vancouver was less than = enthusiastic. I received only a handful of confirmations of = participation, less than the critical number to justify calling for a = meeting. So, there will be no interim meeting of the WG in Vancouver. =

We will however try to stick = as close as possible to the schedule in the charter. I would like to = require the editors to start working on the next round of = Internet-Drafts, which should be the draft-hubmib-efm-....-00 versions, = due to the end of the month. Please help the editors improve the quality = of their documents by reading the current drafts and sending your = comments by the end of this week. This is what I intent to do as = well.

Regards,

Dan

------_=_NextPart_001_01C3BF47.01A8A256-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Dec 10 15:46:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15879 for ; Wed, 10 Dec 2003 15:46:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUBDe-0006EY-1i; Wed, 10 Dec 2003 15:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUBCh-0006Ck-UG for hubmib@optimus.ietf.org; Wed, 10 Dec 2003 15:45:03 -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 PAA15817 for ; Wed, 10 Dec 2003 15:45:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUBCf-00010L-00 for hubmib@ietf.org; Wed, 10 Dec 2003 15:45:01 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AUBCf-00010I-00 for hubmib@ietf.org; Wed, 10 Dec 2003 15:45:01 -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 hBAKiMFo019811 for ; Wed, 10 Dec 2003 15:44: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 hBAKiHFo019692 for ; Wed, 10 Dec 2003 15:44:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] No Interim Meeting Date: Wed, 10 Dec 2003 22:44:49 +0200 Message-ID: Thread-Topic: [Hubmib] No Interim Meeting Thread-Index: AcO/XFMVKEFE3zqLQqCpY3FGtNwpdQAAd+SQ From: "Romascanu, Dan (Dan)" To: "Edward Beili" Cc: 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 No, I was meaning draft-ietf-hubmib-efm-...-00.txt - first round of WG = Internet-Drafts. > -----Original Message----- > From: Edward Beili [mailto:EdwardB@actelis.com] > Sent: 10 December, 2003 10:33 PM > To: Romascanu, Dan (Dan) > Subject: RE: [Hubmib] No Interim Meeting >=20 >=20 > Dan, >=20 > did you mean=20 > draft-hubmib-efm-....-01 versions ? > ^^ > Regards, > -Edward >=20 > -----Original Message----- > From: Romascanu, Dan (Dan) > To: hubmib@ietf.org > Sent: 12/10/03 7:56 PM > Subject: [Hubmib] No Interim Meeting >=20 > The response to the idea of an Interim Meeting of the Ethernet > Interfaces and Hub MIB WG co-located with the January IEEE Interim > meeting in Vancouver was less than enthusiastic. I received only a > handful of confirmations of participation, less than the=20 > critical number > to justify calling for a meeting. So, there will be no interim meeting > of the WG in Vancouver.=20 >=20 > We will however try to stick as close as possible to the=20 > schedule in the > charter. I would like to require the editors to start working on the > next round of Internet-Drafts, which should be the > draft-hubmib-efm-....-00 versions, due to the end of the month. Please > help the editors improve the quality of their documents by reading the > current drafts and sending your comments by the end of this week. This > is what I intent to do as well. >=20 > Regards, >=20 > Dan >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Wed Dec 10 15:46:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15882 for ; Wed, 10 Dec 2003 15:46:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUBDf-0006Fa-SS for hubmib-archive@odin.ietf.org; Wed, 10 Dec 2003 15:46:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBAKk3ZN024012 for hubmib-archive@odin.ietf.org; Wed, 10 Dec 2003 15: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 1AUBDe-0006EY-1i; Wed, 10 Dec 2003 15:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUBCh-0006Ck-UG for hubmib@optimus.ietf.org; Wed, 10 Dec 2003 15:45:03 -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 PAA15817 for ; Wed, 10 Dec 2003 15:45:01 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUBCf-00010L-00 for hubmib@ietf.org; Wed, 10 Dec 2003 15:45:01 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AUBCf-00010I-00 for hubmib@ietf.org; Wed, 10 Dec 2003 15:45:01 -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 hBAKiMFo019811 for ; Wed, 10 Dec 2003 15:44: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 hBAKiHFo019692 for ; Wed, 10 Dec 2003 15:44:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] No Interim Meeting Date: Wed, 10 Dec 2003 22:44:49 +0200 Message-ID: Thread-Topic: [Hubmib] No Interim Meeting Thread-Index: AcO/XFMVKEFE3zqLQqCpY3FGtNwpdQAAd+SQ From: "Romascanu, Dan (Dan)" To: "Edward Beili" Cc: 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 No, I was meaning draft-ietf-hubmib-efm-...-00.txt - first round of WG = Internet-Drafts. > -----Original Message----- > From: Edward Beili [mailto:EdwardB@actelis.com] > Sent: 10 December, 2003 10:33 PM > To: Romascanu, Dan (Dan) > Subject: RE: [Hubmib] No Interim Meeting >=20 >=20 > Dan, >=20 > did you mean=20 > draft-hubmib-efm-....-01 versions ? > ^^ > Regards, > -Edward >=20 > -----Original Message----- > From: Romascanu, Dan (Dan) > To: hubmib@ietf.org > Sent: 12/10/03 7:56 PM > Subject: [Hubmib] No Interim Meeting >=20 > The response to the idea of an Interim Meeting of the Ethernet > Interfaces and Hub MIB WG co-located with the January IEEE Interim > meeting in Vancouver was less than enthusiastic. I received only a > handful of confirmations of participation, less than the=20 > critical number > to justify calling for a meeting. So, there will be no interim meeting > of the WG in Vancouver.=20 >=20 > We will however try to stick as close as possible to the=20 > schedule in the > charter. I would like to require the editors to start working on the > next round of Internet-Drafts, which should be the > draft-hubmib-efm-....-00 versions, due to the end of the month. Please > help the editors improve the quality of their documents by reading the > current drafts and sending your comments by the end of this week. This > is what I intent to do as well. >=20 > Regards, >=20 > Dan >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Dec 18 06:58:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16639 for ; Thu, 18 Dec 2003 06:58:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWwn2-00054c-HK; Thu, 18 Dec 2003 06:58:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWwme-00054J-GW for hubmib@optimus.ietf.org; Thu, 18 Dec 2003 06:57:36 -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 GAA16620 for ; Thu, 18 Dec 2003 06:57:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWwma-0003FE-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWwmY-0003F7-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:31 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AWwmY-0003F4-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:30 -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 hBIBuoK4005557 for ; Thu, 18 Dec 2003 06:56:51 -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 hBIBumK4005524 for ; Thu, 18 Dec 2003 06:56:49 -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_01C3C55E.1C508036" Date: Thu, 18 Dec 2003 13:57:28 +0200 Message-ID: Thread-Topic: draft-squire-hubmib-efm-mib-00.txt Thread-Index: AcPFXhxKmjhzq7aaSg6cefU9rdW5iw== From: "Romascanu, Dan (Dan)" To: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] draft-squire-hubmib-efm-mib-00.txt 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_01C3C55E.1C508036 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are some comments and questions on = draft-squire-hubmib-efm-mib-00.txt. Please take them into consideration = for the next revision of the document. Regards, Dan A. Technical A1. Oui should be defined as a Textual Convention. The editor note in = the text asks the question 'Is this defined anywhere else?' As far as I = know, it is not. A2. Must include Conformance clause for the MIB module to compile = correctly A3. Wrt. the Technical note asking 'where in the existing MIB hierarchy = we wish to hang these new capabilities' the current Draft got it right. = The MIB Guidelines = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 02.txt recommend to create new MIB modules under mib-2. You need to add = however the following note to the RFC Editor: -- RFC Ed.: replace XXX with IANA-assigned number & remove this note=20 A4. I find contradictory the fact that while the DESCRIPTION clause of = dot3OamTable states that 'There will be one row in this table for each = Ethernet-like interface in the system that supports the Ethernet OAM = functions', the rows in the table are created by managers. I think that = row creation should be automatic, as the agent knows when an interface = has OAM capabilities. If the OAM capabilities need not be activated on a = given interface, the operator can use dot3AdminState to disable them. A5. The editorial notes around dot3OamOperStatus seem to indicate that = some changes are required in Clause 30. I would like to know where these = changes are, taking into account the phase of the IEEE Draft, and I = recommend that we make sure to have alignment before the two documents. A6. I think that row creation in dot3OamPeerTable should be automatic. = The agent knows the value of dot3OamOperStatus on the interface, and = needs not wait for a manager command in order to activate the function = on the interface. B. Editorial - Major B1. Must fill in the Reference section. Moreover, references need to be = split in separate Normative and Informative references. See = http://www.ops.ietf.org/mib-boilerplate.html B2. I would like to have Section 3 more verbose about the other EFM MIB = documents. A users of these MIBs will probably read this document first, = and look for some guidance. The other two MIB modules should be = mentioned in the Informative References, and the fact that it is = expected that the Common OAM MIB be supported for any OAM flavor should = be mentioned. B3.Must include Security section B4. Must Include Intellectual Property section B5. Must include Copyright Notices section C. Editorial - Minor C1. It is strongly recommended that internet-drafts include a notice = (with e-mail address) of where comments should be sent. C2. The document does not belong to the 'Network Working Group' as = specified in the header. As the next version will be an official WG = document, I suggest to mention 'Ethernet Interfaces and Hub MIB'. C3. References in the text should point to the IEEE document in the = Normative References section, wherever relevant C4. The DESCRIPTION Clause of efmCommonMib mentions the October version = of the P802.3ah Draft. You need to include a note to the RFC editor to = replace this reference with the normative standard reference, when it = will be available. C5. Get rid of the commented variables in the dot2OamTable, unless you = intent to make some point that I am missing them by leaving them there. C6. I suggest that the editorial note after dot3OamUnidirectional = Support be introduced in the DESCRIPTION clause C7. If 'OAM Frames' and 'OAM PDUs' are synonym, I suggest that frames be = replaced by PDU in the DESCRIPTION clauses of dot3OamPduTx and = dot3OamPduRx. C8. Fill-in all TBD references in the MIB ------_=_NextPart_001_01C3C55E.1C508036 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable draft-squire-hubmib-efm-mib-00.txt

Here are some comments and = questions on draft-squire-hubmib-efm-mib-00.txt. Please take them into = consideration for the next revision of the document.

Regards,

Dan


A. Technical

A1. Oui should be defined as = a Textual Convention. The editor note in the text asks the = question 'Is = this defined anywhere else?' As far as I know, it is = not.

A2. Must = include Conformance clause for the MIB module to compile = correctly

A3. Wrt. = the Technical note asking 'where in the existing MIB hierarchy we wish to hang these = new capabilities' the current Draft got it = right. The MIB Guidelines http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-02.txt recommend to create new MIB modules under = mib-2. You need to add however the following note to the RFC = Editor:

-- RFC = Ed.: replace XXX with IANA-assigned number & remove this = note =

A4. I find = contradictory the fact that while the DESCRIPTION clause of dot3OamTable = states that 'There will be one row in this table for each Ethernet-like = interface in the system that supports the Ethernet OAM functions', the = rows in the table are created by managers. I think that row creation = should be automatic, as the agent knows when an interface has OAM = capabilities. If the OAM capabilities need not be activated on a given = interface, the operator can use dot3AdminState to disable = them.

A5. The = editorial notes around dot3OamOperStatus seem to indicate that some = changes are required in Clause 30. I would like to know where these = changes are, taking into account the phase of the IEEE Draft, and I = recommend that we make sure to have alignment before the two = documents.

A6. I think = that row creation in dot3OamPeerTable should be automatic. The agent = knows the value of dot3OamOperStatus on the interface, and needs not = wait for a manager command in order to activate the function on the = interface.


B. = Editorial - Major

B1. Must = fill in the Reference section. Moreover, references need to be split in = separate Normative and Informative references. See http://www.ops.ietf= .org/mib-boilerplate.html

B2. I would = like to have Section 3 more verbose about the other EFM MIB documents. A = users of these MIBs will probably read this document first, and look for = some guidance. The other two MIB modules should be mentioned in the = Informative References, and the fact that it is expected that the Common = OAM MIB be supported for any OAM flavor should be = mentioned.

B3.Must = include Security section

B4. Must = Include Intellectual Property section

B5. Must = include Copyright Notices section


C. = Editorial - Minor

C1. It is = strongly recommended that internet-drafts include a notice (with e-mail = address) of where comments should be sent.

C2. The = document does not belong to the 'Network Working Group' as specified in = the header. As the next version will be an official WG document, I = suggest to mention 'Ethernet Interfaces and Hub MIB'.

C3. References in the text should = point to the IEEE document in the Normative References section, wherever = relevant

C4. The = DESCRIPTION Clause of efmCommonMib mentions the October version of the = P802.3ah Draft. You need to include a note to the RFC editor to replace = this reference with the normative standard reference, when it will be = available.

C5. Get = rid of the commented variables in the dot2OamTable, unless you intent to = make some point that I am missing them by leaving them = there.

C6. I = suggest that the editorial note after dot3OamUnidirectional Support be = introduced in the DESCRIPTION clause

C7. If = 'OAM Frames' and 'OAM PDUs' are synonym, I suggest that frames be = replaced by PDU in the DESCRIPTION clauses of dot3OamPduTx and = dot3OamPduRx.

C8. = Fill-in all TBD references in the MIB









------_=_NextPart_001_01C3C55E.1C508036-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Dec 18 07:48:28 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16640 for ; Thu, 18 Dec 2003 06:58:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWwn4-00054x-Tm for hubmib-archive@odin.ietf.org; Thu, 18 Dec 2003 06:58:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIBw2J6019519 for hubmib-archive@odin.ietf.org; Thu, 18 Dec 2003 06:58:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWwn2-00054c-HK; Thu, 18 Dec 2003 06:58:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWwme-00054J-GW for hubmib@optimus.ietf.org; Thu, 18 Dec 2003 06:57:36 -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 GAA16620 for ; Thu, 18 Dec 2003 06:57:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWwma-0003FE-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWwmY-0003F7-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:31 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AWwmY-0003F4-00 for hubmib@ietf.org; Thu, 18 Dec 2003 06:57:30 -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 hBIBuoK4005557 for ; Thu, 18 Dec 2003 06:56:51 -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 hBIBumK4005524 for ; Thu, 18 Dec 2003 06:56:49 -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_01C3C55E.1C508036" Date: Thu, 18 Dec 2003 13:57:28 +0200 Message-ID: Thread-Topic: draft-squire-hubmib-efm-mib-00.txt Thread-Index: AcPFXhxKmjhzq7aaSg6cefU9rdW5iw== From: "Romascanu, Dan (Dan)" To: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] draft-squire-hubmib-efm-mib-00.txt 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_01C3C55E.1C508036 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are some comments and questions on = draft-squire-hubmib-efm-mib-00.txt. Please take them into consideration = for the next revision of the document. Regards, Dan A. Technical A1. Oui should be defined as a Textual Convention. The editor note in = the text asks the question 'Is this defined anywhere else?' As far as I = know, it is not. A2. Must include Conformance clause for the MIB module to compile = correctly A3. Wrt. the Technical note asking 'where in the existing MIB hierarchy = we wish to hang these new capabilities' the current Draft got it right. = The MIB Guidelines = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 02.txt recommend to create new MIB modules under mib-2. You need to add = however the following note to the RFC Editor: -- RFC Ed.: replace XXX with IANA-assigned number & remove this note=20 A4. I find contradictory the fact that while the DESCRIPTION clause of = dot3OamTable states that 'There will be one row in this table for each = Ethernet-like interface in the system that supports the Ethernet OAM = functions', the rows in the table are created by managers. I think that = row creation should be automatic, as the agent knows when an interface = has OAM capabilities. If the OAM capabilities need not be activated on a = given interface, the operator can use dot3AdminState to disable them. A5. The editorial notes around dot3OamOperStatus seem to indicate that = some changes are required in Clause 30. I would like to know where these = changes are, taking into account the phase of the IEEE Draft, and I = recommend that we make sure to have alignment before the two documents. A6. I think that row creation in dot3OamPeerTable should be automatic. = The agent knows the value of dot3OamOperStatus on the interface, and = needs not wait for a manager command in order to activate the function = on the interface. B. Editorial - Major B1. Must fill in the Reference section. Moreover, references need to be = split in separate Normative and Informative references. See = http://www.ops.ietf.org/mib-boilerplate.html B2. I would like to have Section 3 more verbose about the other EFM MIB = documents. A users of these MIBs will probably read this document first, = and look for some guidance. The other two MIB modules should be = mentioned in the Informative References, and the fact that it is = expected that the Common OAM MIB be supported for any OAM flavor should = be mentioned. B3.Must include Security section B4. Must Include Intellectual Property section B5. Must include Copyright Notices section C. Editorial - Minor C1. It is strongly recommended that internet-drafts include a notice = (with e-mail address) of where comments should be sent. C2. The document does not belong to the 'Network Working Group' as = specified in the header. As the next version will be an official WG = document, I suggest to mention 'Ethernet Interfaces and Hub MIB'. C3. References in the text should point to the IEEE document in the = Normative References section, wherever relevant C4. The DESCRIPTION Clause of efmCommonMib mentions the October version = of the P802.3ah Draft. You need to include a note to the RFC editor to = replace this reference with the normative standard reference, when it = will be available. C5. Get rid of the commented variables in the dot2OamTable, unless you = intent to make some point that I am missing them by leaving them there. C6. I suggest that the editorial note after dot3OamUnidirectional = Support be introduced in the DESCRIPTION clause C7. If 'OAM Frames' and 'OAM PDUs' are synonym, I suggest that frames be = replaced by PDU in the DESCRIPTION clauses of dot3OamPduTx and = dot3OamPduRx. C8. Fill-in all TBD references in the MIB ------_=_NextPart_001_01C3C55E.1C508036 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable draft-squire-hubmib-efm-mib-00.txt

Here are some comments and = questions on draft-squire-hubmib-efm-mib-00.txt. Please take them into = consideration for the next revision of the document.

Regards,

Dan


A. Technical

A1. Oui should be defined as = a Textual Convention. The editor note in the text asks the = question 'Is = this defined anywhere else?' As far as I know, it is = not.

A2. Must = include Conformance clause for the MIB module to compile = correctly

A3. Wrt. = the Technical note asking 'where in the existing MIB hierarchy we wish to hang these = new capabilities' the current Draft got it = right. The MIB Guidelines http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-02.txt recommend to create new MIB modules under = mib-2. You need to add however the following note to the RFC = Editor:

-- RFC = Ed.: replace XXX with IANA-assigned number & remove this = note =

A4. I find = contradictory the fact that while the DESCRIPTION clause of dot3OamTable = states that 'There will be one row in this table for each Ethernet-like = interface in the system that supports the Ethernet OAM functions', the = rows in the table are created by managers. I think that row creation = should be automatic, as the agent knows when an interface has OAM = capabilities. If the OAM capabilities need not be activated on a given = interface, the operator can use dot3AdminState to disable = them.

A5. The = editorial notes around dot3OamOperStatus seem to indicate that some = changes are required in Clause 30. I would like to know where these = changes are, taking into account the phase of the IEEE Draft, and I = recommend that we make sure to have alignment before the two = documents.

A6. I think = that row creation in dot3OamPeerTable should be automatic. The agent = knows the value of dot3OamOperStatus on the interface, and needs not = wait for a manager command in order to activate the function on the = interface.


B. = Editorial - Major

B1. Must = fill in the Reference section. Moreover, references need to be split in = separate Normative and Informative references. See http://www.ops.ietf= .org/mib-boilerplate.html

B2. I would = like to have Section 3 more verbose about the other EFM MIB documents. A = users of these MIBs will probably read this document first, and look for = some guidance. The other two MIB modules should be mentioned in the = Informative References, and the fact that it is expected that the Common = OAM MIB be supported for any OAM flavor should be = mentioned.

B3.Must = include Security section

B4. Must = Include Intellectual Property section

B5. Must = include Copyright Notices section


C. = Editorial - Minor

C1. It is = strongly recommended that internet-drafts include a notice (with e-mail = address) of where comments should be sent.

C2. The = document does not belong to the 'Network Working Group' as specified in = the header. As the next version will be an official WG document, I = suggest to mention 'Ethernet Interfaces and Hub MIB'.

C3. References in the text should = point to the IEEE document in the Normative References section, wherever = relevant

C4. The = DESCRIPTION Clause of efmCommonMib mentions the October version of the = P802.3ah Draft. You need to include a note to the RFC editor to replace = this reference with the normative standard reference, when it will be = available.

C5. Get = rid of the commented variables in the dot2OamTable, unless you intent to = make some point that I am missing them by leaving them = there.

C6. I = suggest that the editorial note after dot3OamUnidirectional Support be = introduced in the DESCRIPTION clause

C7. If = 'OAM Frames' and 'OAM PDUs' are synonym, I suggest that frames be = replaced by PDU in the DESCRIPTION clauses of dot3OamPduTx and = dot3OamPduRx.

C8. = Fill-in all TBD references in the MIB









------_=_NextPart_001_01C3C55E.1C508036-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Dec 22 01:33:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21592 for ; Mon, 22 Dec 2003 01:33:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYJbk-0001X3-VU; Mon, 22 Dec 2003 01:32:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYJbT-0001Wf-Eg for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 01:31:43 -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 BAA21561 for ; Mon, 22 Dec 2003 01:31:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYJbQ-0007Ln-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:40 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYJbP-0007Lg-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:39 -0500 Received: from [192.114.173.84] (helo=ilmail01.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 1AYJbP-0007Ky-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:39 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C854.DABBEB64" Date: Mon, 22 Dec 2003 08:28:46 +0200 Message-ID: <0E1B939480B5BF4780F76BCFCC25DBD116D637@ilmail01.powerdsine.com> Thread-Topic: Power Ethernet MIB Thread-Index: AcPIVS3f68mtyeqhTwabnaZjELV7uw== From: "Daniel Feldman" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_50_60,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Power Ethernet MIB 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_01C3C854.DABBEB64 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all, the Power Ethernet MIB draft was written on June 22nd. Today it should = expire (IANA has not assigned and RFC number to it). Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? Thanks for the help, Daniel Feldman Product Manager=20 PowerDsine Ltd. Tel: +972-9-775-5100 (Ext: 159) Fax: +972-9-775-5112 www.PowerDsine.com ------_=_NextPart_001_01C3C854.DABBEB64 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB

        Hello all,

        the Power Ethernet MIB draft was written on June 22nd. = Today it should expire (IANA has not assigned and RFC number to = it).

        Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew = it?

        Thanks for the help,

Daniel Feldman

Product Manager
PowerDsine Ltd.
Tel: +972-9-775-5100 (Ext: 159)
Fax: +972-9-775-5112
www.PowerDsine.com

------_=_NextPart_001_01C3C854.DABBEB64-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 22 01:33:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21591 for ; Mon, 22 Dec 2003 01:33:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYJbm-0001XO-3c for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 01:32:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBM6W26L005906 for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 01:32:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYJbk-0001X3-VU; Mon, 22 Dec 2003 01:32:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYJbT-0001Wf-Eg for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 01:31:43 -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 BAA21561 for ; Mon, 22 Dec 2003 01:31:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYJbQ-0007Ln-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:40 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYJbP-0007Lg-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:39 -0500 Received: from [192.114.173.84] (helo=ilmail01.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 1AYJbP-0007Ky-00 for hubmib@ietf.org; Mon, 22 Dec 2003 01:31:39 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C854.DABBEB64" Date: Mon, 22 Dec 2003 08:28:46 +0200 Message-ID: <0E1B939480B5BF4780F76BCFCC25DBD116D637@ilmail01.powerdsine.com> Thread-Topic: Power Ethernet MIB Thread-Index: AcPIVS3f68mtyeqhTwabnaZjELV7uw== From: "Daniel Feldman" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_50_60,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Power Ethernet MIB 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_01C3C854.DABBEB64 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all, the Power Ethernet MIB draft was written on June 22nd. Today it should = expire (IANA has not assigned and RFC number to it). Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? Thanks for the help, Daniel Feldman Product Manager=20 PowerDsine Ltd. Tel: +972-9-775-5100 (Ext: 159) Fax: +972-9-775-5112 www.PowerDsine.com ------_=_NextPart_001_01C3C854.DABBEB64 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB

        Hello all,

        the Power Ethernet MIB draft was written on June 22nd. = Today it should expire (IANA has not assigned and RFC number to = it).

        Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew = it?

        Thanks for the help,

Daniel Feldman

Product Manager
PowerDsine Ltd.
Tel: +972-9-775-5100 (Ext: 159)
Fax: +972-9-775-5112
www.PowerDsine.com

------_=_NextPart_001_01C3C854.DABBEB64-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Dec 22 02:32:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06167 for ; Mon, 22 Dec 2003 02:32:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYKXp-0005WO-Ri; Mon, 22 Dec 2003 02:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYKXn-0005W0-SZ for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 02:32:00 -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 CAA06141 for ; Mon, 22 Dec 2003 02:31:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYKXk-0001BX-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYKXj-0001BQ-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:55 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYKXi-0001BN-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:54 -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 hBM7VDK4003366 for ; Mon, 22 Dec 2003 02:31:13 -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 hBM7VBK4003348 for ; Mon, 22 Dec 2003 02:31:12 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C85D.AB738028" Subject: RE: [Hubmib] Power Ethernet MIB X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 09:31:53 +0200 Message-ID: Thread-Topic: Power Ethernet MIB Thread-Index: AcPIVS3f68mtyeqhTwabnaZjELV7uwAB1+LA From: "Romascanu, Dan (Dan)" To: "Daniel Feldman" , Cc: "Bert Wijnen (E-mail)" , "RFC Editor" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_50_60, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 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_01C3C85D.AB738028 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Daniel, =20 No action is needed in my opinion. The authors received the version of = the document that is supposed to be published as RFC 3612 fir the final = 48 hours review about two weeks ago, and approved it. I guess that it is = just a matter a days until the RFC will be out.=20 =20 Regards, =20 Dan =20 -----Original Message----- From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of = Daniel Feldman Sent: 22 December, 2003 8:29 AM To: hubmib@ietf.org Subject: [Hubmib] Power Ethernet MIB Hello all, the Power Ethernet MIB draft was written on June 22nd. Today it = should expire (IANA has not assigned and RFC number to it). Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? Thanks for the help, Daniel Feldman Product Manager PowerDsine Ltd. Tel: +972-9-775-5100 (Ext: 159) Fax: +972-9-775-5112 www.PowerDsine.com ------_=_NextPart_001_01C3C85D.AB738028 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB
Daniel,
 
No action is needed in my opinion. The authors received the = version of=20 the document that is supposed to be published as RFC 3612 fir the final = 48 hours=20 review about two weeks ago, and approved it. I guess that it is just a = matter a=20 days until the RFC will be out.
 
Regards,
 
Dan
 
-----Original Message-----
From: = hubmib-admin@ietf.org=20 [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel=20 Feldman
Sent: 22 December, 2003 8:29 AM
To:=20 hubmib@ietf.org
Subject: [Hubmib] Power Ethernet=20 MIB

        Hello all,

        the Power Ethernet MIB draft was written on June 22nd. Today = it should=20 expire (IANA has not assigned and RFC number to it).

        Is any action necessary, or since IANA already calls it=20 RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew=20 it?

        Thanks for the help,

Daniel=20 Feldman

Product=20 Manager
PowerDsine Ltd.
Tel: +972-9-775-5100 (Ext: = 159)
Fax: +972-9-775-5112
www.PowerDsine.com

------_=_NextPart_001_01C3C85D.AB738028-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 22 02:32:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06183 for ; Mon, 22 Dec 2003 02:32:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYKXr-0005XD-NU for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 02:32:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBM7W2EV021264 for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 02:32:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYKXp-0005WO-Ri; Mon, 22 Dec 2003 02:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYKXn-0005W0-SZ for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 02:32:00 -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 CAA06141 for ; Mon, 22 Dec 2003 02:31:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYKXk-0001BX-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYKXj-0001BQ-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:55 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYKXi-0001BN-00 for hubmib@ietf.org; Mon, 22 Dec 2003 02:31:54 -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 hBM7VDK4003366 for ; Mon, 22 Dec 2003 02:31:13 -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 hBM7VBK4003348 for ; Mon, 22 Dec 2003 02:31:12 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C85D.AB738028" Subject: RE: [Hubmib] Power Ethernet MIB X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 09:31:53 +0200 Message-ID: Thread-Topic: Power Ethernet MIB Thread-Index: AcPIVS3f68mtyeqhTwabnaZjELV7uwAB1+LA From: "Romascanu, Dan (Dan)" To: "Daniel Feldman" , Cc: "Bert Wijnen (E-mail)" , "RFC Editor" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_50_60, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 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_01C3C85D.AB738028 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Daniel, =20 No action is needed in my opinion. The authors received the version of = the document that is supposed to be published as RFC 3612 fir the final = 48 hours review about two weeks ago, and approved it. I guess that it is = just a matter a days until the RFC will be out.=20 =20 Regards, =20 Dan =20 -----Original Message----- From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of = Daniel Feldman Sent: 22 December, 2003 8:29 AM To: hubmib@ietf.org Subject: [Hubmib] Power Ethernet MIB Hello all, the Power Ethernet MIB draft was written on June 22nd. Today it = should expire (IANA has not assigned and RFC number to it). Is any action necessary, or since IANA already calls it = RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? Thanks for the help, Daniel Feldman Product Manager PowerDsine Ltd. Tel: +972-9-775-5100 (Ext: 159) Fax: +972-9-775-5112 www.PowerDsine.com ------_=_NextPart_001_01C3C85D.AB738028 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB
Daniel,
 
No action is needed in my opinion. The authors received the = version of=20 the document that is supposed to be published as RFC 3612 fir the final = 48 hours=20 review about two weeks ago, and approved it. I guess that it is just a = matter a=20 days until the RFC will be out.
 
Regards,
 
Dan
 
-----Original Message-----
From: = hubmib-admin@ietf.org=20 [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel=20 Feldman
Sent: 22 December, 2003 8:29 AM
To:=20 hubmib@ietf.org
Subject: [Hubmib] Power Ethernet=20 MIB

        Hello all,

        the Power Ethernet MIB draft was written on June 22nd. Today = it should=20 expire (IANA has not assigned and RFC number to it).

        Is any action necessary, or since IANA already calls it=20 RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew=20 it?

        Thanks for the help,

Daniel=20 Feldman

Product=20 Manager
PowerDsine Ltd.
Tel: +972-9-775-5100 (Ext: = 159)
Fax: +972-9-775-5112
www.PowerDsine.com

------_=_NextPart_001_01C3C85D.AB738028-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Dec 22 05:15:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09574 for ; Mon, 22 Dec 2003 05:15:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYN5Z-0003At-PK; Mon, 22 Dec 2003 05:15:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYN4h-00039x-Im for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 05:14:08 -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 FAA09526 for ; Mon, 22 Dec 2003 05:14:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYN4e-0004Sa-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYN4c-0004ST-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:03 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYN4c-0004SQ-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:02 -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 hBMADLK4015545 for ; Mon, 22 Dec 2003 05:13:21 -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 hBMADJK4015501 for ; Mon, 22 Dec 2003 05:13:20 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C874.518A1723" X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 12:14:00 +0200 Message-ID: Thread-Topic: Comments on draft-beili-hubmib-efm-cu-mib-00.txt Thread-Index: AcPIdFGV/jwN4pOdTOqg0XF35ZVEYA== From: "Romascanu, Dan (Dan)" To: , Cc: "C. M. Heard" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Comments on draft-beili-hubmib-efm-cu-mib-00.txt 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_01C3C874.518A1723 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments on draft-beili-hubmib-efm-cu-mib-00.txt. Please = take them into consideration for the next version of the document. Thanks and Regards, Dan A. TECHNICAL A1. I would like to hear more discussions about the layering model = described in 3.1. My personal opinions that the alternative of using = ifStackTable is more consistent with the generic layering model used by = other similar MIBs, but I would like to hear more opinions. A2. Section 3.7 needs to be filled in.=20 A3. The Security Considerations section needs to be filled in with = specific information about the security threats related to setting = values of read-write objects, as well as a list of read-only objects = considered to carry sensitive information.=20 A4. The previous released Ethernet MIB (Power Ethernet MIB) was placed = under 'mib-2' rather than 'transmission' following a comment from Mike = Heard. As Mike is also the author of the MIB Review Guidelines document = I would ask his opinion about where this MIB needs to be placed. In any = case, until the standard is released, please avoid picking a value to = make the compilation pass. Leaving the value non-defined and inserting a = note to the RFC editor is intentional practice A5. What does the requirement to change objects like PAFAdminState value = only 'when the link is Down' mean? I suppose that it implies = ifAdminStatus disabled for the respective interface, and not a fault = situation. This model also implies that there is at least one different = interface to allow the management agent in the device to be accessed. I = suggest that this is made clear in the text.=20 A6. The threshold objects in EfmCuPmd2BTable are meant to trigger = notifications, but the notifications are not defined in the MIB module. = Are they supposed to be added here, or do they need a reference some = place else? B. EDITORIAL - MAJOR B1. The document does not follow the requirements for use of the = keywords as specified in RFC 2119. Please read and comply to this = document - including the required text, as well as the use of = capitalized keywords wherever needed. C. EDITORIAL - MINOR C1. Expand the MAU and IEEE abbreviations in the Abstract section. C2. Expand PMI in the Introduction section C3 Expand PCS at its first occurrence (I think it is in 3.1) C4. Where is the SHDSL MIB defined? Needs to be added to the Informative = references, as well as G.991.2 C5. Add VDSL MIB to Informative references C6. Add RFC 3635 defining the ETHERIF-MIB to Normative References C7. It is not clear why RFC 2460 is included in the references list. ------_=_NextPart_001_01C3C874.518A1723 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-beili-hubmib-efm-cu-mib-00.txt

Here are my comments on = draft-beili-hubmib-efm-cu-mib-00.txt. Please take them into = consideration for the next version of the document.

Thanks and = Regards,

Dan

A. TECHNICAL

A1. I would like to hear more = discussions about the layering model described in 3.1. My personal = opinions that the alternative of using ifStackTable is more consistent = with the generic layering model used by other similar MIBs, but I would = like to hear more opinions.

A2. Section 3.7 needs to be = filled in.

A3. The Security = Considerations section needs to be filled in with specific information = about the security threats related to setting values of read-write = objects, as well as a list of read-only objects considered to carry = sensitive information.

A4. The previous released = Ethernet MIB (Power Ethernet MIB) was placed under 'mib-2' rather than = 'transmission' following a comment from Mike Heard. As Mike is also the = author of the MIB Review Guidelines document I would ask his opinion = about where this MIB needs to be placed. In any case, until the standard = is released, please avoid picking a value to make the compilation pass. = Leaving the value non-defined and inserting a note to the RFC editor is = intentional practice

A5. What does the requirement = to change objects like PAFAdminState value only 'when the link is Down' = mean? I suppose that it implies ifAdminStatus disabled for the = respective interface, and not a fault situation. This model also implies = that there is at least one different interface to allow the management = agent in the device to be accessed. I suggest that this is made clear in = the text.

A6. The threshold objects in = EfmCuPmd2BTable are meant to trigger notifications, but the = notifications are not defined in the MIB module. Are they supposed to be = added here, or do they need a reference some place else?


B. EDITORIAL - = MAJOR

B1. The document does not = follow the requirements for use of the keywords as specified in RFC = 2119. Please read and comply to this document - including the required = text, as well as the use of capitalized keywords wherever = needed.

C. EDITORIAL - = MINOR

C1. Expand the MAU and IEEE = abbreviations in the Abstract section.

C2. Expand PMI in the = Introduction section

C3  Expand PCS at its = first occurrence (I think it is in 3.1)

C4. Where is the SHDSL MIB = defined? Needs to be added to the Informative references, as well as = G.991.2

C5. Add VDSL MIB to = Informative references

C6. Add RFC 3635 defining the = ETHERIF-MIB to Normative References

C7. It is not clear why RFC = 2460 is included in the references list.




------_=_NextPart_001_01C3C874.518A1723-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 22 05:15:33 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09585 for ; Mon, 22 Dec 2003 05:15:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYN5d-0003Bl-9J for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 05:15:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMAF5ZZ012227 for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 05:15:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYN5Z-0003At-PK; Mon, 22 Dec 2003 05:15:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYN4h-00039x-Im for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 05:14:08 -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 FAA09526 for ; Mon, 22 Dec 2003 05:14:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYN4e-0004Sa-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYN4c-0004ST-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:03 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYN4c-0004SQ-00 for hubmib@ietf.org; Mon, 22 Dec 2003 05:14:02 -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 hBMADLK4015545 for ; Mon, 22 Dec 2003 05:13:21 -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 hBMADJK4015501 for ; Mon, 22 Dec 2003 05:13:20 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3C874.518A1723" X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 12:14:00 +0200 Message-ID: Thread-Topic: Comments on draft-beili-hubmib-efm-cu-mib-00.txt Thread-Index: AcPIdFGV/jwN4pOdTOqg0XF35ZVEYA== From: "Romascanu, Dan (Dan)" To: , Cc: "C. M. Heard" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Comments on draft-beili-hubmib-efm-cu-mib-00.txt 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_01C3C874.518A1723 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments on draft-beili-hubmib-efm-cu-mib-00.txt. Please = take them into consideration for the next version of the document. Thanks and Regards, Dan A. TECHNICAL A1. I would like to hear more discussions about the layering model = described in 3.1. My personal opinions that the alternative of using = ifStackTable is more consistent with the generic layering model used by = other similar MIBs, but I would like to hear more opinions. A2. Section 3.7 needs to be filled in.=20 A3. The Security Considerations section needs to be filled in with = specific information about the security threats related to setting = values of read-write objects, as well as a list of read-only objects = considered to carry sensitive information.=20 A4. The previous released Ethernet MIB (Power Ethernet MIB) was placed = under 'mib-2' rather than 'transmission' following a comment from Mike = Heard. As Mike is also the author of the MIB Review Guidelines document = I would ask his opinion about where this MIB needs to be placed. In any = case, until the standard is released, please avoid picking a value to = make the compilation pass. Leaving the value non-defined and inserting a = note to the RFC editor is intentional practice A5. What does the requirement to change objects like PAFAdminState value = only 'when the link is Down' mean? I suppose that it implies = ifAdminStatus disabled for the respective interface, and not a fault = situation. This model also implies that there is at least one different = interface to allow the management agent in the device to be accessed. I = suggest that this is made clear in the text.=20 A6. The threshold objects in EfmCuPmd2BTable are meant to trigger = notifications, but the notifications are not defined in the MIB module. = Are they supposed to be added here, or do they need a reference some = place else? B. EDITORIAL - MAJOR B1. The document does not follow the requirements for use of the = keywords as specified in RFC 2119. Please read and comply to this = document - including the required text, as well as the use of = capitalized keywords wherever needed. C. EDITORIAL - MINOR C1. Expand the MAU and IEEE abbreviations in the Abstract section. C2. Expand PMI in the Introduction section C3 Expand PCS at its first occurrence (I think it is in 3.1) C4. Where is the SHDSL MIB defined? Needs to be added to the Informative = references, as well as G.991.2 C5. Add VDSL MIB to Informative references C6. Add RFC 3635 defining the ETHERIF-MIB to Normative References C7. It is not clear why RFC 2460 is included in the references list. ------_=_NextPart_001_01C3C874.518A1723 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-beili-hubmib-efm-cu-mib-00.txt

Here are my comments on = draft-beili-hubmib-efm-cu-mib-00.txt. Please take them into = consideration for the next version of the document.

Thanks and = Regards,

Dan

A. TECHNICAL

A1. I would like to hear more = discussions about the layering model described in 3.1. My personal = opinions that the alternative of using ifStackTable is more consistent = with the generic layering model used by other similar MIBs, but I would = like to hear more opinions.

A2. Section 3.7 needs to be = filled in.

A3. The Security = Considerations section needs to be filled in with specific information = about the security threats related to setting values of read-write = objects, as well as a list of read-only objects considered to carry = sensitive information.

A4. The previous released = Ethernet MIB (Power Ethernet MIB) was placed under 'mib-2' rather than = 'transmission' following a comment from Mike Heard. As Mike is also the = author of the MIB Review Guidelines document I would ask his opinion = about where this MIB needs to be placed. In any case, until the standard = is released, please avoid picking a value to make the compilation pass. = Leaving the value non-defined and inserting a note to the RFC editor is = intentional practice

A5. What does the requirement = to change objects like PAFAdminState value only 'when the link is Down' = mean? I suppose that it implies ifAdminStatus disabled for the = respective interface, and not a fault situation. This model also implies = that there is at least one different interface to allow the management = agent in the device to be accessed. I suggest that this is made clear in = the text.

A6. The threshold objects in = EfmCuPmd2BTable are meant to trigger notifications, but the = notifications are not defined in the MIB module. Are they supposed to be = added here, or do they need a reference some place else?


B. EDITORIAL - = MAJOR

B1. The document does not = follow the requirements for use of the keywords as specified in RFC = 2119. Please read and comply to this document - including the required = text, as well as the use of capitalized keywords wherever = needed.

C. EDITORIAL - = MINOR

C1. Expand the MAU and IEEE = abbreviations in the Abstract section.

C2. Expand PMI in the = Introduction section

C3  Expand PCS at its = first occurrence (I think it is in 3.1)

C4. Where is the SHDSL MIB = defined? Needs to be added to the Informative references, as well as = G.991.2

C5. Add VDSL MIB to = Informative references

C6. Add RFC 3635 defining the = ETHERIF-MIB to Normative References

C7. It is not clear why RFC = 2460 is included in the references list.




------_=_NextPart_001_01C3C874.518A1723-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Dec 22 09:21:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17743 for ; Mon, 22 Dec 2003 09:21:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYQve-0002KR-F7; Mon, 22 Dec 2003 09:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYQul-0002Io-GL for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 09:20:07 -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 JAA17709 for ; Mon, 22 Dec 2003 09:20:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYQuj-0004aj-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYQug-0004aK-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:04 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYQug-0004a9-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:02 -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 hBMEJJK4003703 for ; Mon, 22 Dec 2003 09:19:19 -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 hBMEJHK4003686 for ; Mon, 22 Dec 2003 09:19:18 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 16:19:59 +0200 Message-ID: Thread-Topic: Comment on Copper and EPON MIBs Thread-Index: AcPIlfrnIcLzrIGFSoGoOQcJyERMZAAAJqAQ From: "Romascanu, Dan (Dan)" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] FW: Comment on Copper and EPON MIBs 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 Please take into account the following comment from David Law. Regards, = Dan -----Original Message----- From: David Law [mailto:David_Law@eur.3com.com] Sent: 22 December, 2003 4:20 PM To: Romascanu, Dan (Dan) Cc: edward.beili@actelis.com; lior.khermosh@passave.com; = msquire@hatterasnetworks.com; Howard Frazier; hbarrass@cisco.com Subject: Comment on Copper and EPON MIBs Hi Dan, Can I please submit a comment against both the Copper [ http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mib-00.txt = ] and PONs [ = http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-mib-00.txt= ] drafts to request that they reference IEEE P802.3 Clause 30 attributes = where possible. This has, as far as I am aware, always been the policy in the = past which I wholeheartedly support - it certainly seems to have been done in = the case of the OAM draft. I believe that in the case of IEEE P802.3ah = Ethernet in the First Mile it is even more important due to the new OAM protocol as = is described below. There are two reasons I ask for this. The first reason is that in number = of cases the object description text in the IETF draft is a duplication, or = a near duplications, of the equivalent attribute's behaviour text found in IEEE P802.3ah draft. I personally believe that it is a better idea to = cross-reference rather than duplicate text otherwise we have problems where the two = documents may diverge - I have included an example of this issue related to the aMPCPDiscoveryWindowsSent object below. The second, and in my opinion more important reason, relates to the OAM = protocol defined in Clause 57 of IEEE P802.3ah. This protocol provides a = mechanism whereby the value of attributes can be accessed from a far end device = through the OAM protocol. The Variable Request OAMPDU (see IEEE P802.3ah D3.0 = subclause 57.4.3.3) is used to request one or more MIB variables from the remote = DTE, the Variable Response OAMPDU (see IEEE P802.3ah D3.0 subclause 57.4.3.4) is = used to return one or more MIB variables. Since this protocol utilizes the MIB = defined in Clause 30, and the related arcs defined in Annex 30A, to ensure = maximum applicability in SNMP systems I believe that these IETF drafts should be = aligned to, and reference, the IEEE P802.3ah draft to the maximum extent = possible. In the cases of IETF objects that do not have a IEEE Clause 30 equivalents, = the OAM protocol Variable Request OAMPDU and Variable Response OAMPDU will be = unable to access that object from the far end device. Now please don't get me wrong, I am not saying there is anything = incorrect in these IETF drafts, all I want to do is ensure consistency between them = and Clause 30 for the reasons described above. I wholly accept that in a = number of cases where the IETF draft differs from the IEEE P802.3ah draft, it is = the IEEE P802.3ah draft that may need correction. Best regards, David Law ---- Draft MIB text ---- aMPCPDiscoveryWindowsSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read only STATUS current DESCRIPTION "A count of discovery windows generated. Increment the counter by one = for each discovery windows generated." ---- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ---- When the text from IEEE P802.3ah draft D2.0 is examined the text reads: ---- IEEE P802.3ah draft D2.0 text ---- 30.3.5.1.11 aMPCPDiscoveryWindowsSent ATTRIBUTE APPROPRIATE SYNTAX: Generalized nonresettable counter. This counter has a maximum increment = rate of 10 000 counts per second at 1000 Mb/s BEHAVIOUR DEFINED AS: A count of discovery windows generated. Increment the counter by one for = each discovery windows generated.; ---- = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D ---- As can be seen the Description text provided in the draft MIB exactly = matches the Behavior text provided in IEEE P802.3ah draft D2.0. If however the = text from IEEE P802.3ah draft D3.0 is examined it reads: ---- IEEE P802.3ah draft D3.0 text ---- 30.3.5.1.11 aMPCPDiscoveryWindowsSent ATTRIBUTE APPROPRIATE SYNTAX: Generalized nonresettable counter. This counter has a maximum increment = rate of 10 000 counts per second at 1000 Mb/s BEHAVIOUR DEFINED AS: A count of discovery windows generated. The counter is incremented by = one for each generated discovery window.; ---- = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D ---- As can be seen the description of the behavior has been refined in D3.0 = and the typo of '... each discovery windows ..' corrected. Since in the draft = MIB the text has been copied from Clause 30, rather than being referenced, the = error still exists in the draft MIB and will need to be correct. A cross = reference to Clause 30 behavior text would have avoided this issue. _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 22 09:21:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17745 for ; Mon, 22 Dec 2003 09:21:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYQvf-0002LB-Hh for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 09:21:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMEL32M008976 for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 09:21:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYQve-0002KR-F7; Mon, 22 Dec 2003 09:21:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYQul-0002Io-GL for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 09:20:07 -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 JAA17709 for ; Mon, 22 Dec 2003 09:20:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYQuj-0004aj-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYQug-0004aK-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:04 -0500 Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYQug-0004a9-00 for hubmib@ietf.org; Mon, 22 Dec 2003 09:20:02 -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 hBMEJJK4003703 for ; Mon, 22 Dec 2003 09:19:19 -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 hBMEJHK4003686 for ; Mon, 22 Dec 2003 09:19:18 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Mon, 22 Dec 2003 16:19:59 +0200 Message-ID: Thread-Topic: Comment on Copper and EPON MIBs Thread-Index: AcPIlfrnIcLzrIGFSoGoOQcJyERMZAAAJqAQ From: "Romascanu, Dan (Dan)" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] FW: Comment on Copper and EPON MIBs 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 Please take into account the following comment from David Law. Regards, = Dan -----Original Message----- From: David Law [mailto:David_Law@eur.3com.com] Sent: 22 December, 2003 4:20 PM To: Romascanu, Dan (Dan) Cc: edward.beili@actelis.com; lior.khermosh@passave.com; = msquire@hatterasnetworks.com; Howard Frazier; hbarrass@cisco.com Subject: Comment on Copper and EPON MIBs Hi Dan, Can I please submit a comment against both the Copper [ http://www.ietf.org/internet-drafts/draft-beili-hubmib-efm-cu-mib-00.txt = ] and PONs [ = http://www.ietf.org/internet-drafts/draft-khermosh-hubmib-epon-mib-00.txt= ] drafts to request that they reference IEEE P802.3 Clause 30 attributes = where possible. This has, as far as I am aware, always been the policy in the = past which I wholeheartedly support - it certainly seems to have been done in = the case of the OAM draft. I believe that in the case of IEEE P802.3ah = Ethernet in the First Mile it is even more important due to the new OAM protocol as = is described below. There are two reasons I ask for this. The first reason is that in number = of cases the object description text in the IETF draft is a duplication, or = a near duplications, of the equivalent attribute's behaviour text found in IEEE P802.3ah draft. I personally believe that it is a better idea to = cross-reference rather than duplicate text otherwise we have problems where the two = documents may diverge - I have included an example of this issue related to the aMPCPDiscoveryWindowsSent object below. The second, and in my opinion more important reason, relates to the OAM = protocol defined in Clause 57 of IEEE P802.3ah. This protocol provides a = mechanism whereby the value of attributes can be accessed from a far end device = through the OAM protocol. The Variable Request OAMPDU (see IEEE P802.3ah D3.0 = subclause 57.4.3.3) is used to request one or more MIB variables from the remote = DTE, the Variable Response OAMPDU (see IEEE P802.3ah D3.0 subclause 57.4.3.4) is = used to return one or more MIB variables. Since this protocol utilizes the MIB = defined in Clause 30, and the related arcs defined in Annex 30A, to ensure = maximum applicability in SNMP systems I believe that these IETF drafts should be = aligned to, and reference, the IEEE P802.3ah draft to the maximum extent = possible. In the cases of IETF objects that do not have a IEEE Clause 30 equivalents, = the OAM protocol Variable Request OAMPDU and Variable Response OAMPDU will be = unable to access that object from the far end device. Now please don't get me wrong, I am not saying there is anything = incorrect in these IETF drafts, all I want to do is ensure consistency between them = and Clause 30 for the reasons described above. I wholly accept that in a = number of cases where the IETF draft differs from the IEEE P802.3ah draft, it is = the IEEE P802.3ah draft that may need correction. Best regards, David Law ---- Draft MIB text ---- aMPCPDiscoveryWindowsSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read only STATUS current DESCRIPTION "A count of discovery windows generated. Increment the counter by one = for each discovery windows generated." ---- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ---- When the text from IEEE P802.3ah draft D2.0 is examined the text reads: ---- IEEE P802.3ah draft D2.0 text ---- 30.3.5.1.11 aMPCPDiscoveryWindowsSent ATTRIBUTE APPROPRIATE SYNTAX: Generalized nonresettable counter. This counter has a maximum increment = rate of 10 000 counts per second at 1000 Mb/s BEHAVIOUR DEFINED AS: A count of discovery windows generated. Increment the counter by one for = each discovery windows generated.; ---- = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D ---- As can be seen the Description text provided in the draft MIB exactly = matches the Behavior text provided in IEEE P802.3ah draft D2.0. If however the = text from IEEE P802.3ah draft D3.0 is examined it reads: ---- IEEE P802.3ah draft D3.0 text ---- 30.3.5.1.11 aMPCPDiscoveryWindowsSent ATTRIBUTE APPROPRIATE SYNTAX: Generalized nonresettable counter. This counter has a maximum increment = rate of 10 000 counts per second at 1000 Mb/s BEHAVIOUR DEFINED AS: A count of discovery windows generated. The counter is incremented by = one for each generated discovery window.; ---- = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D ---- As can be seen the description of the behavior has been refined in D3.0 = and the typo of '... each discovery windows ..' corrected. Since in the draft = MIB the text has been copied from Clause 30, rather than being referenced, the = error still exists in the draft MIB and will need to be correct. A cross = reference to Clause 30 behavior text would have avoided this issue. _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Dec 22 12:24:28 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25967 for ; Mon, 22 Dec 2003 12:24:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTmj-0001mK-No for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 12:24:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMHO1uf006825 for hubmib-archive@odin.ietf.org; Mon, 22 Dec 2003 12:24:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTmj-0001lq-8B; Mon, 22 Dec 2003 12:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTly-0001gj-A5 for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 12:23:14 -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 MAA25871 for ; Mon, 22 Dec 2003 12:23:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTlw-0002uI-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYTlv-0002uB-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:12 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTlv-0002u4-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:11 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hBMHN7f11136 for ; Mon, 22 Dec 2003 09:23:07 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 22 Dec 2003 09:23:06 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: hubmib@ietf.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Hubmib] Re: Comments on draft-beili-hubmib-efm-cu-mib-00.txt 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: , On Mon, 22 Dec 2003, Romascanu, Dan (Dan) wrote: > A. TECHNICAL > > A1. I would like to hear more discussions about the layering > model described in 3.1. My personal opinions that the > alternative of using ifStackTable is more consistent with the > generic layering model used by other similar MIBs, but I would > like to hear more opinions. I assume that what is being discussed here is the following note: Editor's Note: An alternative would be to use ifStackTable to describe cross-connect capability and efmCuAvailableStackTable to describe actual connections, so that the cross-connect action would be done in the EFM-CU-MIB by modifying the efmCuAvailableStackTable (and not in IF-MIB). Since the ifStackTable is normally used to describe and manipulate actual interlayer connections, the strategy of using it to manipulate those connections and of using efmCuAvailableStackTable to describe possible connections seems like the right way to go for me. > A2. Section 3.7 needs to be filled in. > A3. The Security Considerations section needs to be filled in > with specific information about the security threats related to > setting values of read-write objects, as well as a list of > read-only objects considered to carry sensitive information. See draft-ietf-ops-mib-review-guidelines-02.txt Section 3.6 > A4. The previous released Ethernet MIB (Power Ethernet MIB) was > placed under 'mib-2' rather than 'transmission' following a > comment from Mike Heard. As Mike is also the author of the MIB > Review Guidelines document I would ask his opinion about where > this MIB needs to be placed. In any case, until the standard is > released, please avoid picking a value to make the compilation > pass. Leaving the value non-defined and inserting a note to the > RFC editor is intentional practice I agree with all of the above. Traditionally, a MIB module is rooted in the transmission branch when it defines a media-specific extension to the ifTable relating to a specific ifType. In most other cases it's rooted under mib-2. And in no case should an Internet-Draft use a number that has not been obtained from IANA. See draft-ietf-ops-mib-review-guidelines-02.txt Section 4.5. I would like to comment more, but I have to go pack to go on a vacation. Enjoy your holidays. //cmh _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Dec 22 13:14:10 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25965 for ; Mon, 22 Dec 2003 12:24:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTmj-0001lq-8B; Mon, 22 Dec 2003 12:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTly-0001gj-A5 for hubmib@optimus.ietf.org; Mon, 22 Dec 2003 12:23:14 -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 MAA25871 for ; Mon, 22 Dec 2003 12:23:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTlw-0002uI-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYTlv-0002uB-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:12 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTlv-0002u4-00 for hubmib@ietf.org; Mon, 22 Dec 2003 12:23:11 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hBMHN7f11136 for ; Mon, 22 Dec 2003 09:23:07 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 22 Dec 2003 09:23:06 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: hubmib@ietf.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Hubmib] Re: Comments on draft-beili-hubmib-efm-cu-mib-00.txt 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: , On Mon, 22 Dec 2003, Romascanu, Dan (Dan) wrote: > A. TECHNICAL > > A1. I would like to hear more discussions about the layering > model described in 3.1. My personal opinions that the > alternative of using ifStackTable is more consistent with the > generic layering model used by other similar MIBs, but I would > like to hear more opinions. I assume that what is being discussed here is the following note: Editor's Note: An alternative would be to use ifStackTable to describe cross-connect capability and efmCuAvailableStackTable to describe actual connections, so that the cross-connect action would be done in the EFM-CU-MIB by modifying the efmCuAvailableStackTable (and not in IF-MIB). Since the ifStackTable is normally used to describe and manipulate actual interlayer connections, the strategy of using it to manipulate those connections and of using efmCuAvailableStackTable to describe possible connections seems like the right way to go for me. > A2. Section 3.7 needs to be filled in. > A3. The Security Considerations section needs to be filled in > with specific information about the security threats related to > setting values of read-write objects, as well as a list of > read-only objects considered to carry sensitive information. See draft-ietf-ops-mib-review-guidelines-02.txt Section 3.6 > A4. The previous released Ethernet MIB (Power Ethernet MIB) was > placed under 'mib-2' rather than 'transmission' following a > comment from Mike Heard. As Mike is also the author of the MIB > Review Guidelines document I would ask his opinion about where > this MIB needs to be placed. In any case, until the standard is > released, please avoid picking a value to make the compilation > pass. Leaving the value non-defined and inserting a note to the > RFC editor is intentional practice I agree with all of the above. Traditionally, a MIB module is rooted in the transmission branch when it defines a media-specific extension to the ifTable relating to a specific ifType. In most other cases it's rooted under mib-2. And in no case should an Internet-Draft use a number that has not been obtained from IANA. See draft-ietf-ops-mib-review-guidelines-02.txt Section 4.5. I would like to comment more, but I have to go pack to go on a vacation. Enjoy your holidays. //cmh _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Dec 23 10:03:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22447 for ; Tue, 23 Dec 2003 10:03:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYo3q-0002cx-4T; Tue, 23 Dec 2003 10:03:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYo3n-0002cO-Mt for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 10:03:00 -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 KAA22406 for ; Tue, 23 Dec 2003 10:02:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYo3k-000185-01 for hubmib@ietf.org; Tue, 23 Dec 2003 10:02:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYo0h-00014b-00 for hubmib@ietf.org; Tue, 23 Dec 2003 09:59:48 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYo0g-00014W-00 for hubmib@ietf.org; Tue, 23 Dec 2003 09:59:46 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBNEugkn014707 for ; Tue, 23 Dec 2003 09:56:43 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBNEuekn014639 for ; Tue, 23 Dec 2003 09:56:41 -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_01C3C965.64146035" Date: Tue, 23 Dec 2003 16:59:40 +0200 Message-ID: Thread-Topic: Comments on draft-khermosh-hubmib-epon-mib-00.txt Thread-Index: AcPJZWQUunh/dxtcQqKqBOk48Flh7Q== From: "Romascanu, Dan (Dan)" To: Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Comments on draft-khermosh-hubmib-epon-mib-00.txt 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_01C3C965.64146035 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments concerning draft-khermosh-hubmib-epon-mib-00.txt. = Please take them into consideration in the process of updating this = Internet-Draft.=20 Thanks and Regards, Dan A. TECHNICAL A1. The MIB module does not comply to the requirements for an IETF = document. It needs to be written and to compile clean in proper SMIv2, = and to follow as close as possible the recommendations in = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 02.txt.=20 A2. I do not think that amendments to the MAU MIB should be included in = this document. The procedure this Working Group has adopted in similar = cases in the past is to amend the MAU MIB and re-issue the RFC. I would = however ask for the MAU MIB editor, and the other WG members to comment = on this issue on the list. A3. There are several objects defined in the MIB that seem to be modeled = as boolean types. For such objects, using the TruthValue TC is = recommended A4. Many enumerated objects start with value 0. RFC 2578 recommends (but = does not require) that integer- valued enumerations start at 1 and be = numbered contiguously. I strongly suggest that this recommendation be = followed. B. EDITORIAL - MAJOR B1. The formatting of the document differs from the standard format = recommended for Internet-Drafts. See = http://www.ops.ietf.org/mib-boilerplate.me for a formatting example B2. Abstract - I think that the scope of the MIB is not that much on = managing EPONs, but rather devices and interfaces that conform to the = EPON standards B3. Need to add a section that relates this MIB to other relevant MIB = modules: The Interfaces MIB, the Ethernet-like Interfaces MIB, and the = Generic EFM MIB B4. Need to add a section describing the structure of the MIB B5. Need to add a security section B6. Need to add an Intellectual Property Section B7. References need to be divided in separate Normative References and = Informative References sections. SNMP references need to be included. = See http://www.ops.ietf.org/mib-boilerplate.html B8. All references need to be included in REFERENCE clauses, not in = DESCRIPTION clauses C. EDITORIAL - MINOR C1. It is not clear what is meant by the following phrase in the = Overview section: 'The document is contains the registers defined = according to the IEEE 802.3ah Draft 2.0 Annex 30A and partitioned = accordingly.' ------_=_NextPart_001_01C3C965.64146035 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-khermosh-hubmib-epon-mib-00.txt

Here are my comments = concerning draft-khermosh-hubmib-epon-mib-00.txt. Please take them into = consideration in the process of updating this Internet-Draft. =


Thanks and = Regards,

Dan

A. TECHNICAL

A1. The MIB module does not = comply to the requirements for an IETF document. It needs to be written = and to compile clean in proper SMIv2, and to follow as close as possible = the recommendations in http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-02.txt.

A2. I do not think that = amendments to the MAU MIB should be included in this document. The = procedure this Working Group has adopted in similar cases in the past is = to amend the MAU MIB and re-issue the RFC. I would however ask for the = MAU MIB editor, and the other WG members to comment on this issue on the = list.

A3. There are several objects = defined in the MIB that seem to be modeled as boolean types. For such = objects, using the TruthValue TC is recommended

A4. Many enumerated objects = start with value 0. RFC 2578 recommends (but does = not require) that integer- valued enumerations start at 1 and be = numbered contiguously. I strongly suggest that this recommendation be = followed.

B. = EDITORIAL - MAJOR

B1. The = formatting of the document differs from the standard format recommended = for Internet-Drafts. See http://www.ops.ietf.o= rg/mib-boilerplate.me for a formatting example

B2. = Abstract - I think that the scope of the MIB is not that much on = managing EPONs, but rather devices and interfaces that conform to the = EPON standards

B3. Need to = add a section that relates this MIB to other relevant MIB modules: The = Interfaces MIB, the Ethernet-like Interfaces MIB, and the Generic EFM = MIB

B4. Need to = add a section describing the structure of the MIB

B5. Need to = add a security section

B6. Need to = add an Intellectual Property Section

B7. = References need to be divided in separate Normative References and = Informative References sections. SNMP references need to be included. = See http://www.ops.ietf= .org/mib-boilerplate.html

B8. All = references need to be included in REFERENCE clauses, not in DESCRIPTION = clauses


C. = EDITORIAL - MINOR

C1. It is = not clear what is meant by the following phrase in the Overview section: = 'The document is contains the registers defined according to the IEEE = 802.3ah Draft 2.0 Annex 30A and partitioned = accordingly.'

------_=_NextPart_001_01C3C965.64146035-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Dec 23 10:03:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22463 for ; Tue, 23 Dec 2003 10:03:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYo3r-0002dH-Ep for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 10:03:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNF33EH010118 for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 10:03:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYo3q-0002cx-4T; Tue, 23 Dec 2003 10:03:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYo3n-0002cO-Mt for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 10:03:00 -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 KAA22406 for ; Tue, 23 Dec 2003 10:02:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYo3k-000185-01 for hubmib@ietf.org; Tue, 23 Dec 2003 10:02:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYo0h-00014b-00 for hubmib@ietf.org; Tue, 23 Dec 2003 09:59:48 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AYo0g-00014W-00 for hubmib@ietf.org; Tue, 23 Dec 2003 09:59:46 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBNEugkn014707 for ; Tue, 23 Dec 2003 09:56:43 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBNEuekn014639 for ; Tue, 23 Dec 2003 09:56:41 -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_01C3C965.64146035" Date: Tue, 23 Dec 2003 16:59:40 +0200 Message-ID: Thread-Topic: Comments on draft-khermosh-hubmib-epon-mib-00.txt Thread-Index: AcPJZWQUunh/dxtcQqKqBOk48Flh7Q== From: "Romascanu, Dan (Dan)" To: Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Comments on draft-khermosh-hubmib-epon-mib-00.txt 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_01C3C965.64146035 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments concerning draft-khermosh-hubmib-epon-mib-00.txt. = Please take them into consideration in the process of updating this = Internet-Draft.=20 Thanks and Regards, Dan A. TECHNICAL A1. The MIB module does not comply to the requirements for an IETF = document. It needs to be written and to compile clean in proper SMIv2, = and to follow as close as possible the recommendations in = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 02.txt.=20 A2. I do not think that amendments to the MAU MIB should be included in = this document. The procedure this Working Group has adopted in similar = cases in the past is to amend the MAU MIB and re-issue the RFC. I would = however ask for the MAU MIB editor, and the other WG members to comment = on this issue on the list. A3. There are several objects defined in the MIB that seem to be modeled = as boolean types. For such objects, using the TruthValue TC is = recommended A4. Many enumerated objects start with value 0. RFC 2578 recommends (but = does not require) that integer- valued enumerations start at 1 and be = numbered contiguously. I strongly suggest that this recommendation be = followed. B. EDITORIAL - MAJOR B1. The formatting of the document differs from the standard format = recommended for Internet-Drafts. See = http://www.ops.ietf.org/mib-boilerplate.me for a formatting example B2. Abstract - I think that the scope of the MIB is not that much on = managing EPONs, but rather devices and interfaces that conform to the = EPON standards B3. Need to add a section that relates this MIB to other relevant MIB = modules: The Interfaces MIB, the Ethernet-like Interfaces MIB, and the = Generic EFM MIB B4. Need to add a section describing the structure of the MIB B5. Need to add a security section B6. Need to add an Intellectual Property Section B7. References need to be divided in separate Normative References and = Informative References sections. SNMP references need to be included. = See http://www.ops.ietf.org/mib-boilerplate.html B8. All references need to be included in REFERENCE clauses, not in = DESCRIPTION clauses C. EDITORIAL - MINOR C1. It is not clear what is meant by the following phrase in the = Overview section: 'The document is contains the registers defined = according to the IEEE 802.3ah Draft 2.0 Annex 30A and partitioned = accordingly.' ------_=_NextPart_001_01C3C965.64146035 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-khermosh-hubmib-epon-mib-00.txt

Here are my comments = concerning draft-khermosh-hubmib-epon-mib-00.txt. Please take them into = consideration in the process of updating this Internet-Draft. =


Thanks and = Regards,

Dan

A. TECHNICAL

A1. The MIB module does not = comply to the requirements for an IETF document. It needs to be written = and to compile clean in proper SMIv2, and to follow as close as possible = the recommendations in http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-02.txt.

A2. I do not think that = amendments to the MAU MIB should be included in this document. The = procedure this Working Group has adopted in similar cases in the past is = to amend the MAU MIB and re-issue the RFC. I would however ask for the = MAU MIB editor, and the other WG members to comment on this issue on the = list.

A3. There are several objects = defined in the MIB that seem to be modeled as boolean types. For such = objects, using the TruthValue TC is recommended

A4. Many enumerated objects = start with value 0. RFC 2578 recommends (but does = not require) that integer- valued enumerations start at 1 and be = numbered contiguously. I strongly suggest that this recommendation be = followed.

B. = EDITORIAL - MAJOR

B1. The = formatting of the document differs from the standard format recommended = for Internet-Drafts. See http://www.ops.ietf.o= rg/mib-boilerplate.me for a formatting example

B2. = Abstract - I think that the scope of the MIB is not that much on = managing EPONs, but rather devices and interfaces that conform to the = EPON standards

B3. Need to = add a section that relates this MIB to other relevant MIB modules: The = Interfaces MIB, the Ethernet-like Interfaces MIB, and the Generic EFM = MIB

B4. Need to = add a section describing the structure of the MIB

B5. Need to = add a security section

B6. Need to = add an Intellectual Property Section

B7. = References need to be divided in separate Normative References and = Informative References sections. SNMP references need to be included. = See http://www.ops.ietf= .org/mib-boilerplate.html

B8. All = references need to be included in REFERENCE clauses, not in DESCRIPTION = clauses


C. = EDITORIAL - MINOR

C1. It is = not clear what is meant by the following phrase in the Overview section: = 'The document is contains the registers defined according to the IEEE = 802.3ah Draft 2.0 Annex 30A and partitioned = accordingly.'

------_=_NextPart_001_01C3C965.64146035-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Dec 23 12:19:28 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27893 for ; Tue, 23 Dec 2003 12:19:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqBR-0008CM-62; Tue, 23 Dec 2003 12:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqBL-0008BR-7J for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 12:18:57 -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 MAA27862 for ; Tue, 23 Dec 2003 12:18:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYqBJ-0005u8-01 for hubmib@ietf.org; Tue, 23 Dec 2003 12:18:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYqAM-0005tl-00 for hubmib@ietf.org; Tue, 23 Dec 2003 12:17:55 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AYqAL-0005tb-00 for hubmib@ietf.org; Tue, 23 Dec 2003 12:17:53 -0500 Received: from jet.isi.edu (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBNHHiZ13016; Tue, 23 Dec 2003 09:17:44 -0800 (PST) Received: (from rfc-ed@localhost) by jet.isi.edu (8.9.3/8.8.6) id JAA12941; Tue, 23 Dec 2003 09:17:44 -0800 (PST) Date: Tue, 23 Dec 2003 09:17:44 -0800 From: RFC Editor To: "Romascanu, Dan (Dan)" Cc: Daniel Feldman , hubmib@ietf.org, "Bert Wijnen (E-mail)" , RFC Editor Subject: Re: [Hubmib] Power Ethernet MIB Message-ID: <20031223171744.GB12850@isi.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,USER_IN_DEF_WHITELIST autolearn=no version=2.60 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: , All, We apologize for the delay. Bert had asked that we alter some of the text in "2. The Internet-Standard Management Framework" and "10. Security Considerations" to better reflect the original wording in the document. Bert, the document has been corrected and posted at: ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621.txt ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621-diff.html Please let us know if there are any other corrections necessary. We will notify IANA of the RFC number and date of publication as soon as the document has been finalized. Thank you. RFC Editor On Mon, Dec 22, 2003 at 09:31:53AM +0200, Romascanu, Dan (Dan) wrote: > Daniel, > > No action is needed in my opinion. The authors received the version of > the document that is supposed to be published as RFC 3612 fir the final > 48 hours review about two weeks ago, and approved it. I guess that it is > just a matter a days until the RFC will be out. > > Regards, > > Dan > > > -----Original Message----- > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel Feldman > Sent: 22 December, 2003 8:29 AM > To: hubmib@ietf.org > Subject: [Hubmib] Power Ethernet MIB > > > > Hello all, > > the Power Ethernet MIB draft was written on June 22nd. Today it should expire (IANA has not assigned and RFC number to it). > > Is any action necessary, or since IANA already calls it RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? > > Thanks for the help, > > Daniel Feldman > > Product Manager > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Dec 23 12:19:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27909 for ; Tue, 23 Dec 2003 12:19:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqBR-0008Cl-Id for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 12:19:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNHJ11H031535 for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 12:19:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqBR-0008CM-62; Tue, 23 Dec 2003 12:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqBL-0008BR-7J for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 12:18:57 -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 MAA27862 for ; Tue, 23 Dec 2003 12:18:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYqBJ-0005u8-01 for hubmib@ietf.org; Tue, 23 Dec 2003 12:18:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYqAM-0005tl-00 for hubmib@ietf.org; Tue, 23 Dec 2003 12:17:55 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AYqAL-0005tb-00 for hubmib@ietf.org; Tue, 23 Dec 2003 12:17:53 -0500 Received: from jet.isi.edu (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBNHHiZ13016; Tue, 23 Dec 2003 09:17:44 -0800 (PST) Received: (from rfc-ed@localhost) by jet.isi.edu (8.9.3/8.8.6) id JAA12941; Tue, 23 Dec 2003 09:17:44 -0800 (PST) Date: Tue, 23 Dec 2003 09:17:44 -0800 From: RFC Editor To: "Romascanu, Dan (Dan)" Cc: Daniel Feldman , hubmib@ietf.org, "Bert Wijnen (E-mail)" , RFC Editor Subject: Re: [Hubmib] Power Ethernet MIB Message-ID: <20031223171744.GB12850@isi.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,USER_IN_DEF_WHITELIST autolearn=no version=2.60 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: , All, We apologize for the delay. Bert had asked that we alter some of the text in "2. The Internet-Standard Management Framework" and "10. Security Considerations" to better reflect the original wording in the document. Bert, the document has been corrected and posted at: ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621.txt ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621-diff.html Please let us know if there are any other corrections necessary. We will notify IANA of the RFC number and date of publication as soon as the document has been finalized. Thank you. RFC Editor On Mon, Dec 22, 2003 at 09:31:53AM +0200, Romascanu, Dan (Dan) wrote: > Daniel, > > No action is needed in my opinion. The authors received the version of > the document that is supposed to be published as RFC 3612 fir the final > 48 hours review about two weeks ago, and approved it. I guess that it is > just a matter a days until the RFC will be out. > > Regards, > > Dan > > > -----Original Message----- > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel Feldman > Sent: 22 December, 2003 8:29 AM > To: hubmib@ietf.org > Subject: [Hubmib] Power Ethernet MIB > > > > Hello all, > > the Power Ethernet MIB draft was written on June 22nd. Today it should expire (IANA has not assigned and RFC number to it). > > Is any action necessary, or since IANA already calls it RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? > > Thanks for the help, > > Daniel Feldman > > Product Manager > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Dec 23 14:46:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04714 for ; Tue, 23 Dec 2003 14:46:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsTi-0005fw-CE; Tue, 23 Dec 2003 14:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsTJ-0005fV-M2 for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 14:45:37 -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 OAA04685 for ; Tue, 23 Dec 2003 14:45:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYsTG-0007im-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:45:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYsRK-0007ec-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:43:35 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AYsPY-0007XQ-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:41:45 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hBNJeTe24060 for ; Tue, 23 Dec 2003 13:40:44 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Tue, 23 Dec 2003 20:36:43 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155033D2CB9@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: RFC Editor , "Romascanu, Dan (Dan)" Cc: Daniel Feldman , hubmib@ietf.org, "Bert Wijnen (E-mail)" Subject: RE: [Hubmib] Power Ethernet MIB - RFC3621 to be Date: Tue, 23 Dec 2003 20:36:42 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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: , Thanks, I am now happy with the doc. AS far as I am concerned: ship it! Thanks and Happy Holidays and a good 2004! Bert > -----Original Message----- > From: RFC Editor [mailto:rfc-editor@rfc-editor.org] > Sent: dinsdag 23 december 2003 18:18 > To: Romascanu, Dan (Dan) > Cc: Daniel Feldman; hubmib@ietf.org; Bert Wijnen (E-mail); RFC Editor > Subject: Re: [Hubmib] Power Ethernet MIB > > > All, > > We apologize for the delay. Bert had asked that we alter some of the > text in "2. The Internet-Standard Management Framework" and > "10. Security Considerations" to better reflect the original > wording in > the document. > > Bert, the document has been corrected and posted at: > > ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621.txt > ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621-diff.html > > Please let us know if there are any other corrections necessary. We > will notify IANA of the RFC number and date of publication as soon as > the document has been finalized. > > Thank you. > > RFC Editor > > > On Mon, Dec 22, 2003 at 09:31:53AM +0200, Romascanu, Dan (Dan) wrote: > > Daniel, > > > > No action is needed in my opinion. The authors received the > version of > > the document that is supposed to be published as RFC 3612 > fir the final > > 48 hours review about two weeks ago, and approved it. I > guess that it is > > just a matter a days until the RFC will be out. > > > > Regards, > > > > Dan > > > > > > -----Original Message----- > > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel Feldman > Sent: 22 December, 2003 8:29 AM > To: hubmib@ietf.org > Subject: [Hubmib] Power Ethernet MIB > > > > Hello all, > > the Power Ethernet MIB draft was written on June 22nd. Today it should expire (IANA has not assigned and RFC number to it). > > Is any action necessary, or since IANA already calls it RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? > > Thanks for the help, > > Daniel Feldman > > Product Manager > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Dec 23 14:46:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04716 for ; Tue, 23 Dec 2003 14:46:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsTj-0005gi-FI for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 14:46:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNJk38d021855 for hubmib-archive@odin.ietf.org; Tue, 23 Dec 2003 14: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 1AYsTi-0005fw-CE; Tue, 23 Dec 2003 14:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsTJ-0005fV-M2 for hubmib@optimus.ietf.org; Tue, 23 Dec 2003 14:45:37 -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 OAA04685 for ; Tue, 23 Dec 2003 14:45:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYsTG-0007im-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:45:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYsRK-0007ec-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:43:35 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AYsPY-0007XQ-00 for hubmib@ietf.org; Tue, 23 Dec 2003 14:41:45 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hBNJeTe24060 for ; Tue, 23 Dec 2003 13:40:44 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Tue, 23 Dec 2003 20:36:43 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155033D2CB9@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: RFC Editor , "Romascanu, Dan (Dan)" Cc: Daniel Feldman , hubmib@ietf.org, "Bert Wijnen (E-mail)" Subject: RE: [Hubmib] Power Ethernet MIB - RFC3621 to be Date: Tue, 23 Dec 2003 20:36:42 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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: , Thanks, I am now happy with the doc. AS far as I am concerned: ship it! Thanks and Happy Holidays and a good 2004! Bert > -----Original Message----- > From: RFC Editor [mailto:rfc-editor@rfc-editor.org] > Sent: dinsdag 23 december 2003 18:18 > To: Romascanu, Dan (Dan) > Cc: Daniel Feldman; hubmib@ietf.org; Bert Wijnen (E-mail); RFC Editor > Subject: Re: [Hubmib] Power Ethernet MIB > > > All, > > We apologize for the delay. Bert had asked that we alter some of the > text in "2. The Internet-Standard Management Framework" and > "10. Security Considerations" to better reflect the original > wording in > the document. > > Bert, the document has been corrected and posted at: > > ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621.txt > ftp://ftp.rfc-editor.org/in-notes/authors/rfc3621-diff.html > > Please let us know if there are any other corrections necessary. We > will notify IANA of the RFC number and date of publication as soon as > the document has been finalized. > > Thank you. > > RFC Editor > > > On Mon, Dec 22, 2003 at 09:31:53AM +0200, Romascanu, Dan (Dan) wrote: > > Daniel, > > > > No action is needed in my opinion. The authors received the > version of > > the document that is supposed to be published as RFC 3612 > fir the final > > 48 hours review about two weeks ago, and approved it. I > guess that it is > > just a matter a days until the RFC will be out. > > > > Regards, > > > > Dan > > > > > > -----Original Message----- > > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On Behalf Of Daniel Feldman > Sent: 22 December, 2003 8:29 AM > To: hubmib@ietf.org > Subject: [Hubmib] Power Ethernet MIB > > > > Hello all, > > the Power Ethernet MIB draft was written on June 22nd. Today it should expire (IANA has not assigned and RFC number to it). > > Is any action necessary, or since IANA already calls it RFC-ietf-hubmib-power-ethernet-mib-08.txt there is no need to renew it? > > Thanks for the help, > > Daniel Feldman > > Product Manager > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Dec 24 15:56:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22469 for ; Wed, 24 Dec 2003 15:56:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZG30-0002UB-5b; Wed, 24 Dec 2003 15:56:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZG2M-0002Ts-Px for hubmib@optimus.ietf.org; Wed, 24 Dec 2003 15:55:22 -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 PAA22428 for ; Wed, 24 Dec 2003 15:55:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AZG2L-0007jE-00 for hubmib@ietf.org; Wed, 24 Dec 2003 15:55:21 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AZFyu-0007fP-00 for hubmib@ietf.org; Wed, 24 Dec 2003 15:51:49 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AZFvt-0007bS-00; Wed, 24 Dec 2003 15:48:41 -0500 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBOKmQs17926; Wed, 24 Dec 2003 12:48:26 -0800 (PST) Message-Id: <200312242048.hBOKmQs17926@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, hubmib@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Dec 2003 12:48:26 -0800 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Subject: [Hubmib] RFC 3621 on Power Ethernet MIB 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: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3621 Title: Power Ethernet MIB Author(s): A. Berger, D. Romascanu Status: Standards Track Date: December 2003 Mailbox: avib@PowerDsine.com, dromasca@avaya.com Pages: 20 Characters: 37294 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hubmib-power-ethernet-mib-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3621.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing Power Sourcing Equipment (PSE). This document is a product of the Ethernet Interfaces and Hub MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031224124704.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3621 --OtherAccess Content-Type: Message/External-body; name="rfc3621.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031224124704.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Wed Dec 24 16:44:33 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22470 for ; Wed, 24 Dec 2003 15:56:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZG31-0002Uu-A3 for hubmib-archive@odin.ietf.org; Wed, 24 Dec 2003 15:56:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBOKu3X4009579 for hubmib-archive@odin.ietf.org; Wed, 24 Dec 2003 15:56:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZG30-0002UB-5b; Wed, 24 Dec 2003 15:56:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZG2M-0002Ts-Px for hubmib@optimus.ietf.org; Wed, 24 Dec 2003 15:55:22 -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 PAA22428 for ; Wed, 24 Dec 2003 15:55:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AZG2L-0007jE-00 for hubmib@ietf.org; Wed, 24 Dec 2003 15:55:21 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AZFyu-0007fP-00 for hubmib@ietf.org; Wed, 24 Dec 2003 15:51:49 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AZFvt-0007bS-00; Wed, 24 Dec 2003 15:48:41 -0500 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBOKmQs17926; Wed, 24 Dec 2003 12:48:26 -0800 (PST) Message-Id: <200312242048.hBOKmQs17926@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, hubmib@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 24 Dec 2003 12:48:26 -0800 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Subject: [Hubmib] RFC 3621 on Power Ethernet MIB 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: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3621 Title: Power Ethernet MIB Author(s): A. Berger, D. Romascanu Status: Standards Track Date: December 2003 Mailbox: avib@PowerDsine.com, dromasca@avaya.com Pages: 20 Characters: 37294 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hubmib-power-ethernet-mib-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3621.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing Power Sourcing Equipment (PSE). This document is a product of the Ethernet Interfaces and Hub MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031224124704.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3621 --OtherAccess Content-Type: Message/External-body; name="rfc3621.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031224124704.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Fri Dec 26 02:40:52 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07092 for ; Fri, 26 Dec 2003 02:40:52 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZma1-0002wu-UE for hubmib-archive@odin.ietf.org; Fri, 26 Dec 2003 02:40:19 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBQ7eGVN011320 for hubmib-archive@odin.ietf.org; Fri, 26 Dec 2003 02:40:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZmZl-0002vb-8d; Fri, 26 Dec 2003 02:40:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZmYm-0002q1-T3 for hubmib@optimus.ietf.org; Fri, 26 Dec 2003 02:39:01 -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 CAA06908 for ; Fri, 26 Dec 2003 02:38:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AZmYj-0002tQ-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:38:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AZmWh-0002XB-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:36:53 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AZmUN-00028K-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:34:28 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBQ7VPkn019305 for ; Fri, 26 Dec 2003 02:31:25 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBQ7VNkn019287 for ; Fri, 26 Dec 2003 02:31:24 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 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: [Hubmib] RFC 3621 on Power Ethernet MIB Date: Fri, 26 Dec 2003 09:34:25 +0200 Message-ID: Thread-Topic: [Hubmib] RFC 3621 on Power Ethernet MIB Thread-Index: AcPKYF+/gzeompBJTEuUkNy/FPLTUABIXx0w From: "Romascanu, Dan (Dan)" To: , Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 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 The Power Ethernet MIB RFC was released! A nice holidays present, = completing the previous stage of the WG Charter.=20 I would like to extend my specials thanks and congratulations to Avi = Berger, who was the main editor of the MIB, and brought a tremendous = contribution to the successful completion of this work. Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On=20 > Behalf Of rfc-editor@rfc-editor.org > Sent: 24 December, 2003 10:48 PM > To: IETF-Announce; @ietf.org@rhe.post.avaya.com > Cc: rfc-editor@rfc-editor.org; hubmib@ietf.org > Subject: [Hubmib] RFC 3621 on Power Ethernet MIB >=20 >=20 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 3621 >=20 > Title: Power Ethernet MIB > Author(s): A. Berger, D. Romascanu > Status: Standards Track > Date: December 2003 > Mailbox: avib@PowerDsine.com, dromasca@avaya.com > Pages: 20 > Characters: 37294 > Updates/Obsoletes/SeeAlso: None >=20 > I-D Tag: draft-ietf-hubmib-power-ethernet-mib-08.txt >=20 > URL: ftp://ftp.rfc-editor.org/in-notes/rfc3621.txt >=20 >=20 > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > This document proposes an extension to the Ethernet-like Interfaces > MIB with a set of objects for managing Power Sourcing Equipment > (PSE). >=20 > This document is a product of the Ethernet Interfaces and Hub MIB > Working Group of the IETF. >=20 > This is now a Proposed Standard Protocol. >=20 > This document specifies an Internet standards track protocol for > the Internet community, and requests discussion and suggestions > for improvements. Please refer to the current edition of the > "Internet Official Protocol Standards" (STD 1) for the > standardization state and status of this protocol. Distribution > of this memo is unlimited. >=20 > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. >=20 > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body=20 > help: ways_to_get_rfcs. For example: >=20 > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs >=20 > help: ways_to_get_rfcs >=20 > Requests for special distribution should be addressed to either the > author of the RFC in question, or to=20 > RFC-Manager@RFC-EDITOR.ORG. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution.echo=20 > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223,=20 > Instructions to RFC > Authors, for further information. >=20 >=20 > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute >=20 > ... >=20 > Below is the data which will enable a MIME compliant Mail Reader=20 > implementation to automatically retrieve the ASCII version > of the RFCs. >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Dec 26 03:29:47 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07091 for ; Fri, 26 Dec 2003 02:40:52 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZmZl-0002vb-8d; Fri, 26 Dec 2003 02:40:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AZmYm-0002q1-T3 for hubmib@optimus.ietf.org; Fri, 26 Dec 2003 02:39:01 -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 CAA06908 for ; Fri, 26 Dec 2003 02:38:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AZmYj-0002tQ-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:38:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AZmWh-0002XB-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:36:53 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AZmUN-00028K-00 for hubmib@ietf.org; Fri, 26 Dec 2003 02:34:28 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBQ7VPkn019305 for ; Fri, 26 Dec 2003 02:31:25 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hBQ7VNkn019287 for ; Fri, 26 Dec 2003 02:31:24 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 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: [Hubmib] RFC 3621 on Power Ethernet MIB Date: Fri, 26 Dec 2003 09:34:25 +0200 Message-ID: Thread-Topic: [Hubmib] RFC 3621 on Power Ethernet MIB Thread-Index: AcPKYF+/gzeompBJTEuUkNy/FPLTUABIXx0w From: "Romascanu, Dan (Dan)" To: , Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 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 The Power Ethernet MIB RFC was released! A nice holidays present, = completing the previous stage of the WG Charter.=20 I would like to extend my specials thanks and congratulations to Avi = Berger, who was the main editor of the MIB, and brought a tremendous = contribution to the successful completion of this work. Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: hubmib-admin@ietf.org [mailto:hubmib-admin@ietf.org]On=20 > Behalf Of rfc-editor@rfc-editor.org > Sent: 24 December, 2003 10:48 PM > To: IETF-Announce; @ietf.org@rhe.post.avaya.com > Cc: rfc-editor@rfc-editor.org; hubmib@ietf.org > Subject: [Hubmib] RFC 3621 on Power Ethernet MIB >=20 >=20 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 3621 >=20 > Title: Power Ethernet MIB > Author(s): A. Berger, D. Romascanu > Status: Standards Track > Date: December 2003 > Mailbox: avib@PowerDsine.com, dromasca@avaya.com > Pages: 20 > Characters: 37294 > Updates/Obsoletes/SeeAlso: None >=20 > I-D Tag: draft-ietf-hubmib-power-ethernet-mib-08.txt >=20 > URL: ftp://ftp.rfc-editor.org/in-notes/rfc3621.txt >=20 >=20 > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > This document proposes an extension to the Ethernet-like Interfaces > MIB with a set of objects for managing Power Sourcing Equipment > (PSE). >=20 > This document is a product of the Ethernet Interfaces and Hub MIB > Working Group of the IETF. >=20 > This is now a Proposed Standard Protocol. >=20 > This document specifies an Internet standards track protocol for > the Internet community, and requests discussion and suggestions > for improvements. Please refer to the current edition of the > "Internet Official Protocol Standards" (STD 1) for the > standardization state and status of this protocol. Distribution > of this memo is unlimited. >=20 > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. >=20 > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body=20 > help: ways_to_get_rfcs. For example: >=20 > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs >=20 > help: ways_to_get_rfcs >=20 > Requests for special distribution should be addressed to either the > author of the RFC in question, or to=20 > RFC-Manager@RFC-EDITOR.ORG. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution.echo=20 > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223,=20 > Instructions to RFC > Authors, for further information. >=20 >=20 > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute >=20 > ... >=20 > Below is the data which will enable a MIME compliant Mail Reader=20 > implementation to automatically retrieve the ASCII version > of the RFCs. >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib