From mailman-admin@ietf.org Sun Jun 1 13:04:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21929 for ; Sun, 1 Jun 2003 13:04:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51H4SB23112 for ; Sun, 1 Jun 2003 13:04:28 -0400 Date: Sun, 01 Jun 2003 13:04:28 -0400 Message-ID: <20030601170428.11734.62677.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: hubmib-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, hubmib-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for hubmib-archive@lists.ietf.org: List Password // URL ---- -------- hubmib@ietf.org XUKx https://www1.ietf.org/mailman/options/hubmib/hubmib-archive%40lists.ietf.org From mailnull@www1.ietf.org Sun Jun 1 15:53:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00566 for ; Sun, 1 Jun 2003 15:53:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h51Jr9W25341 for hubmib-archive@odin.ietf.org; Sun, 1 Jun 2003 15:53:09 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51Jr9B25336; Sun, 1 Jun 2003 15:53:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51Jq9B25295 for ; Sun, 1 Jun 2003 15:52:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00543 for ; Sun, 1 Jun 2003 15:52:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MYqV-0004gA-00 for hubmib@ietf.org; Sun, 01 Jun 2003 15:50:23 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19MYqU-0004g7-00 for hubmib@ietf.org; Sun, 01 Jun 2003 15:50:22 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h51Jq6805365; Sun, 1 Jun 2003 12:52:06 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Sun, 1 Jun 2003 12:52:05 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: Re: [Hubmib] Power Ethernet MIB - WG Last Call In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Tue, 27 May 2003, Romascanu, Dan (Dan) wrote: >This is an Ethernet Interfaces and Hub MIB WG Last Call for the >Power Ethernet MIB. The document can be found at: > >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt Here is a MIB doctor nit that I seem to have missed previously: in the MODULE-IDENTITY invocation the UTC time of the most recent REVISION clause does not match that of the LAST-UPDATED clause. See section 4.5 of . //cmh _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sun Jun 1 15:53:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00580 for ; Sun, 1 Jun 2003 15:53:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51Jr9B25336; Sun, 1 Jun 2003 15:53:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h51Jq9B25295 for ; Sun, 1 Jun 2003 15:52:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00543 for ; Sun, 1 Jun 2003 15:52:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MYqV-0004gA-00 for hubmib@ietf.org; Sun, 01 Jun 2003 15:50:23 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19MYqU-0004g7-00 for hubmib@ietf.org; Sun, 01 Jun 2003 15:50:22 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h51Jq6805365; Sun, 1 Jun 2003 12:52:06 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Sun, 1 Jun 2003 12:52:05 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: Re: [Hubmib] Power Ethernet MIB - WG Last Call In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Tue, 27 May 2003, Romascanu, Dan (Dan) wrote: >This is an Ethernet Interfaces and Hub MIB WG Last Call for the >Power Ethernet MIB. The document can be found at: > >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt Here is a MIB doctor nit that I seem to have missed previously: in the MODULE-IDENTITY invocation the UTC time of the most recent REVISION clause does not match that of the LAST-UPDATED clause. See section 4.5 of . //cmh _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon Jun 2 01:29:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12502 for ; Mon, 2 Jun 2003 01:29:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h525TC229469 for hubmib-archive@odin.ietf.org; Mon, 2 Jun 2003 01:29:12 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h525TBB29464; Mon, 2 Jun 2003 01:29:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h525SSB29430 for ; Mon, 2 Jun 2003 01:28:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12482 for ; Mon, 2 Jun 2003 01:28:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MhqB-0007QD-00 for hubmib@ietf.org; Mon, 02 Jun 2003 01:26:39 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19MhqA-0007QA-00 for hubmib@ietf.org; Mon, 02 Jun 2003 01:26:38 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h525SNA12109 for ; Sun, 1 Jun 2003 22:28:23 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Sun, 1 Jun 2003 22:28:22 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard (fwd) Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hub MIB folks -- Dan Romascanu asked me to forward the following message to the list. The context of the discussion was a last call comment raised by the IANA representative on the MAU-MIB regarding the following language in the DESCRIPTION clauses of rpMauType and ifMauType: This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. The issue raised by the IANA representative is that the above language by itself does not provide any instructions on how to administer MAU type assignments. Despite the above language (which has been around since RFC 1515) MAU type assignments for IEEE 802 standard have been historically been managed by the working group. The solution proposed below is to reword the DESCRIPTION clauses to remove the "is managed by the IANA" language. Comments from other WG members are solicited. Regards, Mike Heard ---------- Forwarded message ---------- Date: Wed, 28 May 2003 09:56:58 -0700 (PDT) From: C. M. Heard To: "Wijnen, Bert (Bert)" Cc: John Flick , "Dan Romascanu (E-mail)" , IANA Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard On Wed, 28 May 2003, Wijnen, Bert (Bert) wrote: > Mmm... strange that I overlooked this. Apparently we all did. > I guess we (probably the WG) need to decide how we want to > handle this. Seems like we have these choices: > > a.We ask IANA to keep a registry under dot3MauType, in which > case we need to add an IANA Considerations section to explain > how to make new assignments. If we choose for this one, we might > be better of to make it an IANA maintained MIB Module. > b.We state that new values can only be created by Standards Action > (as per RFC2434) and then we're basically done. Seems IANA need to > do nothing in this case. We could wonder if we want IANA > to administer these and make a public list of the assignments (to > make it easier in the future to recognize if conflicts would arise). > If so we need to tell them about that in IANA consoderations > If not, we may want to remove all IANA related text I think. > c.Seems we have only been adding new values in this document itself. > So we could mention that the only valid values are 0.0 and the > ones listed within this MIB module. In that case there is also > no IANA considerations and we may want to remove the IANA text. > > So... did we intend to ever allow other MIB modules to make > MauType assignments? Did we intend to allow proprietary > MauTypes (e.g. OIDs that we do not control al all?) Bert, We probably want something a little different from any of these alternatives. In practice, the WG always has to manage the standard (i.e., IEEE 802.3) MAU type assignments since adding a new standard MAU type requires that a corresponding bit position be defined for ifMauTypeListBits. The language "assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA" in the DESCRIPTION clauses of rpMauType and ifMauType dates all the way back to RFC 1515, but it seems to be historical since (i) no IANA MAU type registry was ever created (or if it was, I can't find any evidence of it now) and (ii) the WG has been managing all new standard MAU types that have appeared in the various revisions of the MAU-MIB (RFC 2239, RFC 2668, and the present document). This has been a practical necessity since the type list object ifMauTypeList (now replaced by ifMauTypeListBits) was introduced in RFC 2239. It was (and I think still is) the intent to allow non-standard MAU types. The DESCRIPTION clause for ifMauTypeListBits says: DESCRIPTION "A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapabilityBits. Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed above." In view of this, I think the correct course of action would be: (i) remove the language "assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA" and instead of saying that an initial set of values is defined , say that values for standard IEEE 802.3 MAU types are defined; (ii) inform the IANA that we don't need for them to create or maintain an MAU type registry ... in fact we don't need for them to do anything at all with respect to this document. Here are the specific wording changes that I propose. Change the DESCRIPTION clause of rpMauType as follows: FROM: DESCRIPTION "This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." TO: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." and change the DESCRIPTION clause of ifMauType as follows: FROM: DESCRIPTION "This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. This object represents the operational type of the MAU, as determined by either (1) the result of the auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object ifMauDefaultType. In case (2), a set to the object ifMauDefaultType will force the MAU into the new operating mode." TO: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. This object represents the operational type of the MAU, as determined by either (1) the result of the auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object ifMauDefaultType. In case (2), a set to the object ifMauDefaultType will force the MAU into the new operating mode." With those changes there would be no mention of IANA in the document. Note that this will still allow an enterprise to manage equipment with proprietary MAU types; the OID values to identify the proprietary MAU types would be assigned under the enterprise's OID tree and would not require any external coordination (other than to get an enterprise number in the first place). Comments? Mike Heard > > -----Original Message----- > > From: IANA [mailto:iana@iana.org] > > Sent: dinsdag 27 mei 2003 20:42 > > To: iesg@ietf.org > > Cc: johnf@rose.hp.com > > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 > > Medium Attachment Units (MAUs) to Proposed Standard > > > > > > IESG: > > > > The IANA has reviewed the following Internet-Draft which is > > in Last Call: , and > > has the following comments with regards to the publication of > > this document: > > > > It is not clear what this document is requesting the IANA > > do. Clarification is needed. > > > > Please respond to the IANA about our concerns with regards to this > > document. Failing to do so may cause delay of the approval and > > publication of your document. > > > > Thank you. > > > > Michelle S. Cotton > > (on behalf of the IANA) _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 2 01:29:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12519 for ; Mon, 2 Jun 2003 01:29:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h525TBB29464; Mon, 2 Jun 2003 01:29:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h525SSB29430 for ; Mon, 2 Jun 2003 01:28:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12482 for ; Mon, 2 Jun 2003 01:28:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MhqB-0007QD-00 for hubmib@ietf.org; Mon, 02 Jun 2003 01:26:39 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19MhqA-0007QA-00 for hubmib@ietf.org; Mon, 02 Jun 2003 01:26:38 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h525SNA12109 for ; Sun, 1 Jun 2003 22:28:23 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Sun, 1 Jun 2003 22:28:22 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard (fwd) Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hub MIB folks -- Dan Romascanu asked me to forward the following message to the list. The context of the discussion was a last call comment raised by the IANA representative on the MAU-MIB regarding the following language in the DESCRIPTION clauses of rpMauType and ifMauType: This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. The issue raised by the IANA representative is that the above language by itself does not provide any instructions on how to administer MAU type assignments. Despite the above language (which has been around since RFC 1515) MAU type assignments for IEEE 802 standard have been historically been managed by the working group. The solution proposed below is to reword the DESCRIPTION clauses to remove the "is managed by the IANA" language. Comments from other WG members are solicited. Regards, Mike Heard ---------- Forwarded message ---------- Date: Wed, 28 May 2003 09:56:58 -0700 (PDT) From: C. M. Heard To: "Wijnen, Bert (Bert)" Cc: John Flick , "Dan Romascanu (E-mail)" , IANA Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard On Wed, 28 May 2003, Wijnen, Bert (Bert) wrote: > Mmm... strange that I overlooked this. Apparently we all did. > I guess we (probably the WG) need to decide how we want to > handle this. Seems like we have these choices: > > a.We ask IANA to keep a registry under dot3MauType, in which > case we need to add an IANA Considerations section to explain > how to make new assignments. If we choose for this one, we might > be better of to make it an IANA maintained MIB Module. > b.We state that new values can only be created by Standards Action > (as per RFC2434) and then we're basically done. Seems IANA need to > do nothing in this case. We could wonder if we want IANA > to administer these and make a public list of the assignments (to > make it easier in the future to recognize if conflicts would arise). > If so we need to tell them about that in IANA consoderations > If not, we may want to remove all IANA related text I think. > c.Seems we have only been adding new values in this document itself. > So we could mention that the only valid values are 0.0 and the > ones listed within this MIB module. In that case there is also > no IANA considerations and we may want to remove the IANA text. > > So... did we intend to ever allow other MIB modules to make > MauType assignments? Did we intend to allow proprietary > MauTypes (e.g. OIDs that we do not control al all?) Bert, We probably want something a little different from any of these alternatives. In practice, the WG always has to manage the standard (i.e., IEEE 802.3) MAU type assignments since adding a new standard MAU type requires that a corresponding bit position be defined for ifMauTypeListBits. The language "assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA" in the DESCRIPTION clauses of rpMauType and ifMauType dates all the way back to RFC 1515, but it seems to be historical since (i) no IANA MAU type registry was ever created (or if it was, I can't find any evidence of it now) and (ii) the WG has been managing all new standard MAU types that have appeared in the various revisions of the MAU-MIB (RFC 2239, RFC 2668, and the present document). This has been a practical necessity since the type list object ifMauTypeList (now replaced by ifMauTypeListBits) was introduced in RFC 2239. It was (and I think still is) the intent to allow non-standard MAU types. The DESCRIPTION clause for ifMauTypeListBits says: DESCRIPTION "A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapabilityBits. Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed above." In view of this, I think the correct course of action would be: (i) remove the language "assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA" and instead of saying that an initial set of values is defined , say that values for standard IEEE 802.3 MAU types are defined; (ii) inform the IANA that we don't need for them to create or maintain an MAU type registry ... in fact we don't need for them to do anything at all with respect to this document. Here are the specific wording changes that I propose. Change the DESCRIPTION clause of rpMauType as follows: FROM: DESCRIPTION "This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." TO: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." and change the DESCRIPTION clause of ifMauType as follows: FROM: DESCRIPTION "This object identifies the MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. This object represents the operational type of the MAU, as determined by either (1) the result of the auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object ifMauDefaultType. In case (2), a set to the object ifMauDefaultType will force the MAU into the new operating mode." TO: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. This object represents the operational type of the MAU, as determined by either (1) the result of the auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object ifMauDefaultType. In case (2), a set to the object ifMauDefaultType will force the MAU into the new operating mode." With those changes there would be no mention of IANA in the document. Note that this will still allow an enterprise to manage equipment with proprietary MAU types; the OID values to identify the proprietary MAU types would be assigned under the enterprise's OID tree and would not require any external coordination (other than to get an enterprise number in the first place). Comments? Mike Heard > > -----Original Message----- > > From: IANA [mailto:iana@iana.org] > > Sent: dinsdag 27 mei 2003 20:42 > > To: iesg@ietf.org > > Cc: johnf@rose.hp.com > > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 > > Medium Attachment Units (MAUs) to Proposed Standard > > > > > > IESG: > > > > The IANA has reviewed the following Internet-Draft which is > > in Last Call: , and > > has the following comments with regards to the publication of > > this document: > > > > It is not clear what this document is requesting the IANA > > do. Clarification is needed. > > > > Please respond to the IANA about our concerns with regards to this > > document. Failing to do so may cause delay of the approval and > > publication of your document. > > > > Thank you. > > > > Michelle S. Cotton > > (on behalf of the IANA) _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon Jun 2 18:16:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27278 for ; Mon, 2 Jun 2003 18:16:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h52MGIs28583 for hubmib-archive@odin.ietf.org; Mon, 2 Jun 2003 18:16:18 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52MGHB28578; Mon, 2 Jun 2003 18:16:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52MF1B28544 for ; Mon, 2 Jun 2003 18:15:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27152 for ; Mon, 2 Jun 2003 18:14:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MxYE-0006uk-00 for hubmib@ietf.org; Mon, 02 Jun 2003 18:13:10 -0400 Received: from atlrel6.hp.com ([156.153.255.205]) by ietf-mx with esmtp (Exim 4.12) id 19MxYD-0006uh-00 for hubmib@ietf.org; Mon, 02 Jun 2003 18:13:09 -0400 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by atlrel6.hp.com (Postfix) with ESMTP id 6F2F61C00B3B; Mon, 2 Jun 2003 18:14:55 -0400 (EDT) Received: from rose.hp.com (ros54018fli.rose.hp.com [15.29.17.171]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id PAA04622; Mon, 2 Jun 2003 15:14:54 -0700 (PDT) Message-ID: <3EDBCC5B.23C3E554@rose.hp.com> Date: Mon, 02 Jun 2003 15:14:51 -0700 From: John Flick X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "C. M. Heard" Cc: Hub MIB Mailing List Subject: Re: [Hubmib] RE: Last Call: Definitions of Managed Objects for IEEE 802.3 MediumAttachment Units (MAUs) to Proposed Standard (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I agree with Mike's interpretation below. The "IANA" text below has been there since the initial version of this document. We have never had, or intended to have, an IANA registry, and we have always allowed for proprietary MAU types, and this has been used in several cases: - vendors who ship products using pre-standard MAUs, or for which the IEEE standard is done but the MIB update isn't. For example, many vendors were shipping gigabit MAUs, and supporting the MAU MIB for them, long before we finished RFC 2668. - widely implemented, but non-standard MAU types. A good example here is long-haul gigabit, for which there is no IEEE standard, but many vendors have implemented it. - truly proprietary MAU types. I know we have at least one of these. I will make the updates Mike suggests below, as well as fixing the other outstanding nits that Mike found in March, and post a new version today or tomorrow. John "C. M. Heard" wrote: > > Hub MIB folks -- > > Dan Romascanu asked me to forward the following message to the list. > The context of the discussion was a last call comment raised by the > IANA representative on the MAU-MIB regarding the following language > in the DESCRIPTION clauses of rpMauType and ifMauType: > > This object identifies the MAU type. An initial set of MAU types > are defined above. The assignment of OBJECT IDENTIFIERs to new > types of MAUs is managed by the IANA. > > The issue raised by the IANA representative is that the above > language by itself does not provide any instructions on how to > administer MAU type assignments. > > Despite the above language (which has been around since RFC 1515) > MAU type assignments for IEEE 802 standard have been historically > been managed by the working group. The solution proposed below is > to reword the DESCRIPTION clauses to remove the "is managed by the > IANA" language. > > Comments from other WG members are solicited. > > Regards, > > Mike Heard > > ---------- Forwarded message ---------- > Date: Wed, 28 May 2003 09:56:58 -0700 (PDT) > From: C. M. Heard > To: "Wijnen, Bert (Bert)" > Cc: John Flick , > "Dan Romascanu (E-mail)" , IANA > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium > Attachment Units (MAUs) to Proposed Standard > > On Wed, 28 May 2003, Wijnen, Bert (Bert) wrote: > > Mmm... strange that I overlooked this. > > Apparently we all did. > > > I guess we (probably the WG) need to decide how we want to > > handle this. Seems like we have these choices: > > > > a.We ask IANA to keep a registry under dot3MauType, in which > > case we need to add an IANA Considerations section to explain > > how to make new assignments. If we choose for this one, we might > > be better of to make it an IANA maintained MIB Module. > > b.We state that new values can only be created by Standards Action > > (as per RFC2434) and then we're basically done. Seems IANA need to > > do nothing in this case. We could wonder if we want IANA > > to administer these and make a public list of the assignments (to > > make it easier in the future to recognize if conflicts would arise). > > If so we need to tell them about that in IANA consoderations > > If not, we may want to remove all IANA related text I think. > > c.Seems we have only been adding new values in this document itself. > > So we could mention that the only valid values are 0.0 and the > > ones listed within this MIB module. In that case there is also > > no IANA considerations and we may want to remove the IANA text. > > > > So... did we intend to ever allow other MIB modules to make > > MauType assignments? Did we intend to allow proprietary > > MauTypes (e.g. OIDs that we do not control al all?) > > Bert, > > We probably want something a little different from any of these > alternatives. > > In practice, the WG always has to manage the standard (i.e., IEEE > 802.3) MAU type assignments since adding a new standard MAU type > requires that a corresponding bit position be defined for > ifMauTypeListBits. The language "assignment of OBJECT IDENTIFIERs to > new types of MAUs is managed by the IANA" in the DESCRIPTION clauses > of rpMauType and ifMauType dates all the way back to RFC 1515, but > it seems to be historical since (i) no IANA MAU type registry was > ever created (or if it was, I can't find any evidence of it now) and > (ii) the WG has been managing all new standard MAU types that have > appeared in the various revisions of the MAU-MIB (RFC 2239, RFC > 2668, and the present document). This has been a practical > necessity since the type list object ifMauTypeList (now replaced by > ifMauTypeListBits) was introduced in RFC 2239. > > It was (and I think still is) the intent to allow non-standard MAU > types. The DESCRIPTION clause for ifMauTypeListBits says: > > DESCRIPTION "A value that uniquely identifies the set of > possible IEEE 802.3 types that the MAU could be. > If auto-negotiation is present on this MAU, this > object will map to ifMauAutoNegCapabilityBits. > > Note that this MAU may be capable of operating > as a MAU type that is beyond the scope of this > MIB. This is indicated by returning the > bit value bOther in addition to any bit values > for capabilities that are listed above." > > In view of this, I think the correct course of action would be: > > (i) remove the language "assignment of OBJECT IDENTIFIERs to new > types of MAUs is managed by the IANA" and instead of saying that an > initial set of values is defined , say that values for standard IEEE > 802.3 MAU types are defined; > > (ii) inform the IANA that we don't need for them to create or > maintain an MAU type registry ... in fact we don't need for them to > do anything at all with respect to this document. > > Here are the specific wording changes that I propose. > > Change the DESCRIPTION clause of rpMauType as follows: > > FROM: > DESCRIPTION "This object identifies the MAU type. An > initial set of MAU types are defined above. The > assignment of OBJECT IDENTIFIERs to new types of > MAUs is managed by the IANA. If the MAU type is > unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value." > > TO: > DESCRIPTION "This object identifies the MAU type. Values for > standard IEEE 802.3 MAU types are defined above. > If the MAU type is unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value." > > and change the DESCRIPTION clause of ifMauType as follows: > > FROM: > DESCRIPTION "This object identifies the MAU type. An > initial set of MAU types are defined above. The > assignment of OBJECT IDENTIFIERs to new types of > MAUs is managed by the IANA. If the MAU type is > unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value. > > This object represents the operational type of > the MAU, as determined by either (1) the result > of the auto-negotiation function or (2) if > auto-negotiation is not enabled or is not > implemented for this MAU, by the value of the > object ifMauDefaultType. In case (2), a set to > the object ifMauDefaultType will force the MAU > into the new operating mode." > > TO: > DESCRIPTION "This object identifies the MAU type. Values for > standard IEEE 802.3 MAU types are defined above. > If the MAU type is unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value. > > This object represents the operational type of > the MAU, as determined by either (1) the result > of the auto-negotiation function or (2) if > auto-negotiation is not enabled or is not > implemented for this MAU, by the value of the > object ifMauDefaultType. In case (2), a set to > the object ifMauDefaultType will force the MAU > into the new operating mode." > > With those changes there would be no mention of IANA in the > document. Note that this will still allow an enterprise to manage > equipment with proprietary MAU types; the OID values to identify > the proprietary MAU types would be assigned under the enterprise's > OID tree and would not require any external coordination (other than > to get an enterprise number in the first place). > > Comments? > > Mike Heard > > > > -----Original Message----- > > > From: IANA [mailto:iana@iana.org] > > > Sent: dinsdag 27 mei 2003 20:42 > > > To: iesg@ietf.org > > > Cc: johnf@rose.hp.com > > > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 > > > Medium Attachment Units (MAUs) to Proposed Standard > > > > > > > > > IESG: > > > > > > The IANA has reviewed the following Internet-Draft which is > > > in Last Call: , and > > > has the following comments with regards to the publication of > > > this document: > > > > > > It is not clear what this document is requesting the IANA > > > do. Clarification is needed. > > > > > > Please respond to the IANA about our concerns with regards to this > > > document. Failing to do so may cause delay of the approval and > > > publication of your document. > > > > > > Thank you. > > > > > > Michelle S. Cotton > > > (on behalf of the IANA) > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 2 18:16:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27293 for ; Mon, 2 Jun 2003 18:16:59 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52MGHB28578; Mon, 2 Jun 2003 18:16:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h52MF1B28544 for ; Mon, 2 Jun 2003 18:15:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27152 for ; Mon, 2 Jun 2003 18:14:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MxYE-0006uk-00 for hubmib@ietf.org; Mon, 02 Jun 2003 18:13:10 -0400 Received: from atlrel6.hp.com ([156.153.255.205]) by ietf-mx with esmtp (Exim 4.12) id 19MxYD-0006uh-00 for hubmib@ietf.org; Mon, 02 Jun 2003 18:13:09 -0400 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by atlrel6.hp.com (Postfix) with ESMTP id 6F2F61C00B3B; Mon, 2 Jun 2003 18:14:55 -0400 (EDT) Received: from rose.hp.com (ros54018fli.rose.hp.com [15.29.17.171]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id PAA04622; Mon, 2 Jun 2003 15:14:54 -0700 (PDT) Message-ID: <3EDBCC5B.23C3E554@rose.hp.com> Date: Mon, 02 Jun 2003 15:14:51 -0700 From: John Flick X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "C. M. Heard" Cc: Hub MIB Mailing List Subject: Re: [Hubmib] RE: Last Call: Definitions of Managed Objects for IEEE 802.3 MediumAttachment Units (MAUs) to Proposed Standard (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I agree with Mike's interpretation below. The "IANA" text below has been there since the initial version of this document. We have never had, or intended to have, an IANA registry, and we have always allowed for proprietary MAU types, and this has been used in several cases: - vendors who ship products using pre-standard MAUs, or for which the IEEE standard is done but the MIB update isn't. For example, many vendors were shipping gigabit MAUs, and supporting the MAU MIB for them, long before we finished RFC 2668. - widely implemented, but non-standard MAU types. A good example here is long-haul gigabit, for which there is no IEEE standard, but many vendors have implemented it. - truly proprietary MAU types. I know we have at least one of these. I will make the updates Mike suggests below, as well as fixing the other outstanding nits that Mike found in March, and post a new version today or tomorrow. John "C. M. Heard" wrote: > > Hub MIB folks -- > > Dan Romascanu asked me to forward the following message to the list. > The context of the discussion was a last call comment raised by the > IANA representative on the MAU-MIB regarding the following language > in the DESCRIPTION clauses of rpMauType and ifMauType: > > This object identifies the MAU type. An initial set of MAU types > are defined above. The assignment of OBJECT IDENTIFIERs to new > types of MAUs is managed by the IANA. > > The issue raised by the IANA representative is that the above > language by itself does not provide any instructions on how to > administer MAU type assignments. > > Despite the above language (which has been around since RFC 1515) > MAU type assignments for IEEE 802 standard have been historically > been managed by the working group. The solution proposed below is > to reword the DESCRIPTION clauses to remove the "is managed by the > IANA" language. > > Comments from other WG members are solicited. > > Regards, > > Mike Heard > > ---------- Forwarded message ---------- > Date: Wed, 28 May 2003 09:56:58 -0700 (PDT) > From: C. M. Heard > To: "Wijnen, Bert (Bert)" > Cc: John Flick , > "Dan Romascanu (E-mail)" , IANA > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 Medium > Attachment Units (MAUs) to Proposed Standard > > On Wed, 28 May 2003, Wijnen, Bert (Bert) wrote: > > Mmm... strange that I overlooked this. > > Apparently we all did. > > > I guess we (probably the WG) need to decide how we want to > > handle this. Seems like we have these choices: > > > > a.We ask IANA to keep a registry under dot3MauType, in which > > case we need to add an IANA Considerations section to explain > > how to make new assignments. If we choose for this one, we might > > be better of to make it an IANA maintained MIB Module. > > b.We state that new values can only be created by Standards Action > > (as per RFC2434) and then we're basically done. Seems IANA need to > > do nothing in this case. We could wonder if we want IANA > > to administer these and make a public list of the assignments (to > > make it easier in the future to recognize if conflicts would arise). > > If so we need to tell them about that in IANA consoderations > > If not, we may want to remove all IANA related text I think. > > c.Seems we have only been adding new values in this document itself. > > So we could mention that the only valid values are 0.0 and the > > ones listed within this MIB module. In that case there is also > > no IANA considerations and we may want to remove the IANA text. > > > > So... did we intend to ever allow other MIB modules to make > > MauType assignments? Did we intend to allow proprietary > > MauTypes (e.g. OIDs that we do not control al all?) > > Bert, > > We probably want something a little different from any of these > alternatives. > > In practice, the WG always has to manage the standard (i.e., IEEE > 802.3) MAU type assignments since adding a new standard MAU type > requires that a corresponding bit position be defined for > ifMauTypeListBits. The language "assignment of OBJECT IDENTIFIERs to > new types of MAUs is managed by the IANA" in the DESCRIPTION clauses > of rpMauType and ifMauType dates all the way back to RFC 1515, but > it seems to be historical since (i) no IANA MAU type registry was > ever created (or if it was, I can't find any evidence of it now) and > (ii) the WG has been managing all new standard MAU types that have > appeared in the various revisions of the MAU-MIB (RFC 2239, RFC > 2668, and the present document). This has been a practical > necessity since the type list object ifMauTypeList (now replaced by > ifMauTypeListBits) was introduced in RFC 2239. > > It was (and I think still is) the intent to allow non-standard MAU > types. The DESCRIPTION clause for ifMauTypeListBits says: > > DESCRIPTION "A value that uniquely identifies the set of > possible IEEE 802.3 types that the MAU could be. > If auto-negotiation is present on this MAU, this > object will map to ifMauAutoNegCapabilityBits. > > Note that this MAU may be capable of operating > as a MAU type that is beyond the scope of this > MIB. This is indicated by returning the > bit value bOther in addition to any bit values > for capabilities that are listed above." > > In view of this, I think the correct course of action would be: > > (i) remove the language "assignment of OBJECT IDENTIFIERs to new > types of MAUs is managed by the IANA" and instead of saying that an > initial set of values is defined , say that values for standard IEEE > 802.3 MAU types are defined; > > (ii) inform the IANA that we don't need for them to create or > maintain an MAU type registry ... in fact we don't need for them to > do anything at all with respect to this document. > > Here are the specific wording changes that I propose. > > Change the DESCRIPTION clause of rpMauType as follows: > > FROM: > DESCRIPTION "This object identifies the MAU type. An > initial set of MAU types are defined above. The > assignment of OBJECT IDENTIFIERs to new types of > MAUs is managed by the IANA. If the MAU type is > unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value." > > TO: > DESCRIPTION "This object identifies the MAU type. Values for > standard IEEE 802.3 MAU types are defined above. > If the MAU type is unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value." > > and change the DESCRIPTION clause of ifMauType as follows: > > FROM: > DESCRIPTION "This object identifies the MAU type. An > initial set of MAU types are defined above. The > assignment of OBJECT IDENTIFIERs to new types of > MAUs is managed by the IANA. If the MAU type is > unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value. > > This object represents the operational type of > the MAU, as determined by either (1) the result > of the auto-negotiation function or (2) if > auto-negotiation is not enabled or is not > implemented for this MAU, by the value of the > object ifMauDefaultType. In case (2), a set to > the object ifMauDefaultType will force the MAU > into the new operating mode." > > TO: > DESCRIPTION "This object identifies the MAU type. Values for > standard IEEE 802.3 MAU types are defined above. > If the MAU type is unknown, the object identifier > > unknownMauType OBJECT IDENTIFIER ::= { 0 0 } > > is returned. Note that unknownMauType is a > syntactically valid object identifier, and any > conformant implementation of ASN.1 and the BER > must be able to generate and recognize this > value. > > This object represents the operational type of > the MAU, as determined by either (1) the result > of the auto-negotiation function or (2) if > auto-negotiation is not enabled or is not > implemented for this MAU, by the value of the > object ifMauDefaultType. In case (2), a set to > the object ifMauDefaultType will force the MAU > into the new operating mode." > > With those changes there would be no mention of IANA in the > document. Note that this will still allow an enterprise to manage > equipment with proprietary MAU types; the OID values to identify > the proprietary MAU types would be assigned under the enterprise's > OID tree and would not require any external coordination (other than > to get an enterprise number in the first place). > > Comments? > > Mike Heard > > > > -----Original Message----- > > > From: IANA [mailto:iana@iana.org] > > > Sent: dinsdag 27 mei 2003 20:42 > > > To: iesg@ietf.org > > > Cc: johnf@rose.hp.com > > > Subject: RE: Last Call: Definitions of Managed Objects for IEEE 802.3 > > > Medium Attachment Units (MAUs) to Proposed Standard > > > > > > > > > IESG: > > > > > > The IANA has reviewed the following Internet-Draft which is > > > in Last Call: , and > > > has the following comments with regards to the publication of > > > this document: > > > > > > It is not clear what this document is requesting the IANA > > > do. Clarification is needed. > > > > > > Please respond to the IANA about our concerns with regards to this > > > document. Failing to do so may cause delay of the approval and > > > publication of your document. > > > > > > Thank you. > > > > > > Michelle S. Cotton > > > (on behalf of the IANA) > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Wed Jun 4 08:01:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13348 for ; Wed, 4 Jun 2003 08:01:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54C15X08376 for hubmib-archive@odin.ietf.org; Wed, 4 Jun 2003 08:01:05 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54C14B08370; Wed, 4 Jun 2003 08:01:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54BvAB08104 for ; Wed, 4 Jun 2003 07:57:10 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12827; Wed, 4 Jun 2003 07:57:08 -0400 (EDT) Message-Id: <200306041157.HAA12827@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 04 Jun 2003 07:57:07 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-04.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Author(s) : J. Flick Filename : draft-ietf-hubmib-mau-mib-v3-04.txt Pages : 62 Date : 2003-6-3 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. Distribution of this memo is unlimited. Please forward comments to hubmib@ietf.org. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-mau-mib-v3-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-3151225.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-mau-mib-v3-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-3151225.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Jun 4 08:01:41 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13377 for ; Wed, 4 Jun 2003 08:01:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54C14B08370; Wed, 4 Jun 2003 08:01:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54BvAB08104 for ; Wed, 4 Jun 2003 07:57:10 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12827; Wed, 4 Jun 2003 07:57:08 -0400 (EDT) Message-Id: <200306041157.HAA12827@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 04 Jun 2003 07:57:07 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-04.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Author(s) : J. Flick Filename : draft-ietf-hubmib-mau-mib-v3-04.txt Pages : 62 Date : 2003-6-3 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. Distribution of this memo is unlimited. Please forward comments to hubmib@ietf.org. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-mau-mib-v3-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-3151225.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-mau-mib-v3-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-mau-mib-v3-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-3151225.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Thu Jun 12 06:30:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02543 for ; Thu, 12 Jun 2003 06:30:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CAULg06767 for hubmib-archive@odin.ietf.org; Thu, 12 Jun 2003 06:30:21 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CAUKm06761; Thu, 12 Jun 2003 06:30:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CATOm06673 for ; Thu, 12 Jun 2003 06:29:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02468 for ; Thu, 12 Jun 2003 06:29:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QPIZ-0000X0-00 for hubmib@ietf.org; Thu, 12 Jun 2003 06:27:15 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19QPIY-0000Wx-00 for hubmib@ietf.org; Thu, 12 Jun 2003 06:27:14 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA21309 for ; Thu, 12 Jun 2003 06:26:38 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA21294 for ; Thu, 12 Jun 2003 06:26:37 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C330CD.7AFA30AE" Date: Thu, 12 Jun 2003 13:29:18 +0300 Message-ID: Thread-Topic: End of PoE MIB WG Last Call Thread-Index: AcMwrNpywzsKO9hYQt2FUDiqru+CgQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] End of PoE MIB WG Last Call 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_01C330CD.7AFA30AE Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable We completed the PoE WG MIB Last call. Comments were received from C.M. = Heard, Charles McTague, and Derek Pitcher, and we thank them and = everybody else who read the document and silently agreed, for their = help. The comments seem to be minor and editorial fixes. Avi and myself = will issue in the next few days a new Internet-Draft, and forward it to = the Area Director for consideration of the document as a Proposed = Standard. Regards, Dan ------_=_NextPart_001_01C330CD.7AFA30AE Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable End of PoE MIB WG Last Call

We completed the PoE WG MIB = Last call. Comments were received from C.M. Heard, Charles McTague, and = Derek Pitcher, and we thank them and everybody else who read the = document and silently agreed, for their help. The comments seem to be = minor and editorial fixes. Avi and myself will issue in the next few = days a new Internet-Draft, and forward it to the Area Director for = consideration of the document as a Proposed Standard.

Regards,

Dan

------_=_NextPart_001_01C330CD.7AFA30AE-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 12 06:30:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02558 for ; Thu, 12 Jun 2003 06:30:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CAUKm06761; Thu, 12 Jun 2003 06:30:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CATOm06673 for ; Thu, 12 Jun 2003 06:29:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02468 for ; Thu, 12 Jun 2003 06:29:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QPIZ-0000X0-00 for hubmib@ietf.org; Thu, 12 Jun 2003 06:27:15 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19QPIY-0000Wx-00 for hubmib@ietf.org; Thu, 12 Jun 2003 06:27:14 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA21309 for ; Thu, 12 Jun 2003 06:26:38 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA21294 for ; Thu, 12 Jun 2003 06:26:37 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C330CD.7AFA30AE" Date: Thu, 12 Jun 2003 13:29:18 +0300 Message-ID: Thread-Topic: End of PoE MIB WG Last Call Thread-Index: AcMwrNpywzsKO9hYQt2FUDiqru+CgQ== From: "Romascanu, Dan (Dan)" To: Subject: [Hubmib] End of PoE MIB WG Last Call 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_01C330CD.7AFA30AE Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable We completed the PoE WG MIB Last call. Comments were received from C.M. = Heard, Charles McTague, and Derek Pitcher, and we thank them and = everybody else who read the document and silently agreed, for their = help. The comments seem to be minor and editorial fixes. Avi and myself = will issue in the next few days a new Internet-Draft, and forward it to = the Area Director for consideration of the document as a Proposed = Standard. Regards, Dan ------_=_NextPart_001_01C330CD.7AFA30AE Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable End of PoE MIB WG Last Call

We completed the PoE WG MIB = Last call. Comments were received from C.M. Heard, Charles McTague, and = Derek Pitcher, and we thank them and everybody else who read the = document and silently agreed, for their help. The comments seem to be = minor and editorial fixes. Avi and myself will issue in the next few = days a new Internet-Draft, and forward it to the Area Director for = consideration of the document as a Proposed Standard.

Regards,

Dan

------_=_NextPart_001_01C330CD.7AFA30AE-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Thu Jun 12 19:58:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01949 for ; Thu, 12 Jun 2003 19:58:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CNw8203054 for hubmib-archive@odin.ietf.org; Thu, 12 Jun 2003 19:58:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CIG2a14051; Thu, 12 Jun 2003 14:16:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CIF2m13977 for ; Thu, 12 Jun 2003 14:15:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21511 for ; Thu, 12 Jun 2003 14:14:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWZA-0004zC-00 for hubmib@ietf.org; Thu, 12 Jun 2003 14:12:52 -0400 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19QWZ9-0004yg-00 for hubmib@ietf.org; Thu, 12 Jun 2003 14:12:51 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h5CIEPt01745 for ; Thu, 12 Jun 2003 13:14:25 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10SS3A>; Thu, 12 Jun 2003 20:14:23 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15501CD078E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Hubmib Mailing List (E-mail)" Date: Thu, 12 Jun 2003 20:14:21 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] IESG approved HUBMIB WG documents 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: , IESG just approved the following: o Definitions of Managed Objects for the Ethernet-like Interface Types (Proposed Standard) - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (Proposed Standard) - Definition of Managed Objects for the Ethernet WAN Interface Sublayer (Proposed Standard) - Applicability Statement for Reclassification of RFC 1643 to Historic Status (Informational) Formal announcement will come from IESG on IETF announce in the next few days. Thanks for all the good work! Thanks, Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 12 19:58:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01964 for ; Thu, 12 Jun 2003 19:58:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CIG2a14051; Thu, 12 Jun 2003 14:16:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CIF2m13977 for ; Thu, 12 Jun 2003 14:15:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21511 for ; Thu, 12 Jun 2003 14:14:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWZA-0004zC-00 for hubmib@ietf.org; Thu, 12 Jun 2003 14:12:52 -0400 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19QWZ9-0004yg-00 for hubmib@ietf.org; Thu, 12 Jun 2003 14:12:51 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h5CIEPt01745 for ; Thu, 12 Jun 2003 13:14:25 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10SS3A>; Thu, 12 Jun 2003 20:14:23 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15501CD078E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Hubmib Mailing List (E-mail)" Date: Thu, 12 Jun 2003 20:14:21 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] IESG approved HUBMIB WG documents 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: , IESG just approved the following: o Definitions of Managed Objects for the Ethernet-like Interface Types (Proposed Standard) - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (Proposed Standard) - Definition of Managed Objects for the Ethernet WAN Interface Sublayer (Proposed Standard) - Applicability Statement for Reclassification of RFC 1643 to Historic Status (Informational) Formal announcement will come from IESG on IETF announce in the next few days. Thanks for all the good work! Thanks, Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon Jun 16 07:36:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08442 for ; Mon, 16 Jun 2003 07:36:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GBa2n26521 for hubmib-archive@odin.ietf.org; Mon, 16 Jun 2003 07:36:02 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GAR0a22458; Mon, 16 Jun 2003 06:27:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GAQRm22427 for ; Mon, 16 Jun 2003 06:26:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07498 for ; Mon, 16 Jun 2003 06:26:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rr9m-0001DS-00 for hubmib@ietf.org; Mon, 16 Jun 2003 06:24:10 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19Rr9l-0001DP-00 for hubmib@ietf.org; Mon, 16 Jun 2003 06:24:09 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5GANCN20139 for ; Mon, 16 Jun 2003 06:23:12 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5GANBE20135 for ; Mon, 16 Jun 2003 06:23:11 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Hubmib] IESG approved HUBMIB WG documents Date: Mon, 16 Jun 2003 13:26:21 +0300 Message-ID: Thread-Topic: [Hubmib] IESG approved HUBMIB WG documents Thread-Index: AcMxP6FbRNvuAftXSmuciNKQa0LAcQCsf6sw From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "Hubmib Mailing List (E-mail)" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5GAQRm22428 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: 8bit Special thanks to Mike Heard and John Flick - editors of this round of the documents. Dan > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: Thursday, June 12, 2003 9:14 PM > To: Hubmib Mailing List (E-mail) > Subject: [Hubmib] IESG approved HUBMIB WG documents > > > IESG just approved the following: > o Definitions of Managed Objects for the Ethernet-like > Interface > Types (Proposed Standard) > > - Definitions of Managed Objects for IEEE 802.3 Medium > Attachment Units (MAUs) (Proposed Standard) > > - Definition of Managed Objects for the Ethernet WAN > Interface > Sublayer (Proposed Standard) > > - Applicability Statement for Reclassification of RFC 1643 to > Historic Status (Informational) > > > Formal announcement will come from IESG on IETF announce in the next > few days. > > Thanks for all the good work! > > Thanks, > Bert > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 16 07:36:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08457 for ; Mon, 16 Jun 2003 07:36:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GAR0a22458; Mon, 16 Jun 2003 06:27:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GAQRm22427 for ; Mon, 16 Jun 2003 06:26:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07498 for ; Mon, 16 Jun 2003 06:26:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rr9m-0001DS-00 for hubmib@ietf.org; Mon, 16 Jun 2003 06:24:10 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19Rr9l-0001DP-00 for hubmib@ietf.org; Mon, 16 Jun 2003 06:24:09 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5GANCN20139 for ; Mon, 16 Jun 2003 06:23:12 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5GANBE20135 for ; Mon, 16 Jun 2003 06:23:11 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Hubmib] IESG approved HUBMIB WG documents Date: Mon, 16 Jun 2003 13:26:21 +0300 Message-ID: Thread-Topic: [Hubmib] IESG approved HUBMIB WG documents Thread-Index: AcMxP6FbRNvuAftXSmuciNKQa0LAcQCsf6sw From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "Hubmib Mailing List (E-mail)" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5GAQRm22428 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: 8bit Special thanks to Mike Heard and John Flick - editors of this round of the documents. Dan > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: Thursday, June 12, 2003 9:14 PM > To: Hubmib Mailing List (E-mail) > Subject: [Hubmib] IESG approved HUBMIB WG documents > > > IESG just approved the following: > o Definitions of Managed Objects for the Ethernet-like > Interface > Types (Proposed Standard) > > - Definitions of Managed Objects for IEEE 802.3 Medium > Attachment Units (MAUs) (Proposed Standard) > > - Definition of Managed Objects for the Ethernet WAN > Interface > Sublayer (Proposed Standard) > > - Applicability Statement for Reclassification of RFC 1643 to > Historic Status (Informational) > > > Formal announcement will come from IESG on IETF announce in the next > few days. > > Thanks for all the good work! > > Thanks, > Bert > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon Jun 16 08:21:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09903 for ; Mon, 16 Jun 2003 08:21:54 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GCLP230285 for hubmib-archive@odin.ietf.org; Mon, 16 Jun 2003 08:21:25 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G7Y1a10760; Mon, 16 Jun 2003 03:34:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5FERpm02946 for ; Sun, 15 Jun 2003 10:27:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03533 for ; Sun, 15 Jun 2003 10:27:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RYRs-0003rp-00 for hubmib@ietf.org; Sun, 15 Jun 2003 10:25:36 -0400 Received: from [192.116.151.125] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 19RYRr-0003rm-00 for hubmib@ietf.org; Sun, 15 Jun 2003 10:25:35 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Sun, 15 Jun 2003 17:29:40 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF2741812@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" Cc: Ilan Reingold , Gilad Rozen , George Lasry , "'hubmib@ietf.org'" Date: Sun, 15 Jun 2003 17:29:39 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I'm interested to become a co-editor of the 802.3ah MIB. My company specializes in Aggregated Copper EFM systems (currently long reach - 2BaseTL). Regards, -Edward Beili Senior System Engineer Actelis Networks > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Friday, May 30, 2003 11:43 AM > To: Edward Beili > Cc: Ilan Reingold > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Thanks. What level of involvement can you assume? Are you > interested to be a co-editor of the future standard? Also, > what flavor of EFM do you / your company specialize in? > > If would also be VERY useful if you can provide your positive > answer to the Hub MIB e-mail list (hubmib@ietf.org). We need > visible proof of interest in the participation in order to > have this work approved by the IETF leadership. There is no > need to subscribe to the list in order to send mail (unless > you want to be subscribed). > > Regards, > > Dan > > > > -----Original Message----- > > From: Edward Beili [mailto:EdwardB@actelis.com] > > Sent: Thursday, May 29, 2003 11:29 PM > > To: Romascanu, Dan (Dan) > > Cc: Ilan Reingold > > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > > > > Hi Dan, > > > > There's definitely a need for EFM related changes in existing MIBs. > > I've asked this question in Seoul and was told that you are > > coordinating the > > work. > > I would like to be involved in it. > > > > Regards, > > -Edward Beili > > Senior System Engineer > > Actelis Networks > > > > -----Original Message----- > > From: Romascanu, Dan (Dan) > > To: hubmib@ietf.org > > Cc: stds-802-3-efm@ieee.org > > Sent: 5/29/03 6:35 PM > > Subject: [EFM] IEEE 802.3ah MIB? > > > > Our Area Directors copied me on a query that they received about > > eventual work on a IEEE 802.3af MIB. I have sent a query to > > the WG list > > last January, and I do not remember having received any > > feedback. Truth > > is that by that point in time the Management and OAM clauses > > in the EFM > > work were pretty open. This has probably changed by now and with the > > 802.3ah Draft getting closer to Sponsor Ballot, it is > probably a good > > time to ask the question again. is there interest for a > 802.3ah (EFM) > > MIB work in the IETF Ethernet Interfaces and Hub MIB > Working Group? As > > the IETF rules say, we need a visible level of interest, and > > volunteers > > to commit to do the work in order to be able to discuss > re-chartering > > the WG with the ADs. > > > > I am copying the IEEE 802.3ah list - feedback is obviously > > welcome from > > them as well. > > > > Thanks, > > > > Dan > > > > Dan Romascanu, > > > > Chair, IETF Ethernet Interfaces and Hub MIB WG > > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 16 08:22:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09921 for ; Mon, 16 Jun 2003 08:22:11 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G7Y1a10760; Mon, 16 Jun 2003 03:34:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5FERpm02946 for ; Sun, 15 Jun 2003 10:27:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03533 for ; Sun, 15 Jun 2003 10:27:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RYRs-0003rp-00 for hubmib@ietf.org; Sun, 15 Jun 2003 10:25:36 -0400 Received: from [192.116.151.125] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 19RYRr-0003rm-00 for hubmib@ietf.org; Sun, 15 Jun 2003 10:25:35 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Sun, 15 Jun 2003 17:29:40 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF2741812@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" Cc: Ilan Reingold , Gilad Rozen , George Lasry , "'hubmib@ietf.org'" Date: Sun, 15 Jun 2003 17:29:39 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1255" Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I'm interested to become a co-editor of the 802.3ah MIB. My company specializes in Aggregated Copper EFM systems (currently long reach - 2BaseTL). Regards, -Edward Beili Senior System Engineer Actelis Networks > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Friday, May 30, 2003 11:43 AM > To: Edward Beili > Cc: Ilan Reingold > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Thanks. What level of involvement can you assume? Are you > interested to be a co-editor of the future standard? Also, > what flavor of EFM do you / your company specialize in? > > If would also be VERY useful if you can provide your positive > answer to the Hub MIB e-mail list (hubmib@ietf.org). We need > visible proof of interest in the participation in order to > have this work approved by the IETF leadership. There is no > need to subscribe to the list in order to send mail (unless > you want to be subscribed). > > Regards, > > Dan > > > > -----Original Message----- > > From: Edward Beili [mailto:EdwardB@actelis.com] > > Sent: Thursday, May 29, 2003 11:29 PM > > To: Romascanu, Dan (Dan) > > Cc: Ilan Reingold > > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > > > > Hi Dan, > > > > There's definitely a need for EFM related changes in existing MIBs. > > I've asked this question in Seoul and was told that you are > > coordinating the > > work. > > I would like to be involved in it. > > > > Regards, > > -Edward Beili > > Senior System Engineer > > Actelis Networks > > > > -----Original Message----- > > From: Romascanu, Dan (Dan) > > To: hubmib@ietf.org > > Cc: stds-802-3-efm@ieee.org > > Sent: 5/29/03 6:35 PM > > Subject: [EFM] IEEE 802.3ah MIB? > > > > Our Area Directors copied me on a query that they received about > > eventual work on a IEEE 802.3af MIB. I have sent a query to > > the WG list > > last January, and I do not remember having received any > > feedback. Truth > > is that by that point in time the Management and OAM clauses > > in the EFM > > work were pretty open. This has probably changed by now and with the > > 802.3ah Draft getting closer to Sponsor Ballot, it is > probably a good > > time to ask the question again. is there interest for a > 802.3ah (EFM) > > MIB work in the IETF Ethernet Interfaces and Hub MIB > Working Group? As > > the IETF rules say, we need a visible level of interest, and > > volunteers > > to commit to do the work in order to be able to discuss > re-chartering > > the WG with the ADs. > > > > I am copying the IEEE 802.3ah list - feedback is obviously > > welcome from > > them as well. > > > > Thanks, > > > > Dan > > > > Dan Romascanu, > > > > Chair, IETF Ethernet Interfaces and Hub MIB WG > > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue Jun 17 00:43:38 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16757 for ; Tue, 17 Jun 2003 00:43:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H4hBN05108 for hubmib-archive@odin.ietf.org; Tue, 17 Jun 2003 00:43:11 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJN0a28692; Mon, 16 Jun 2003 15:23:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJM1m28656 for ; Mon, 16 Jun 2003 15:22:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27300; Mon, 16 Jun 2003 15:21:55 -0400 (EDT) Message-Id: <200306161921.PAA27300@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , hubmib@ietf.org From: The IESG Date: Mon, 16 Jun 2003 15:21:55 -0400 Subject: [Hubmib] Protocol Action: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard 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: , The IESG has approved the following documents. These documents are the product of the Ethernet Interfaces and Hub MIB Working Group. The IESG contact persons are Randy Bush and Bert Wijnen o Definitions of Managed Objects for the Ethernet-like Interface Types Proposed Standard o Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Proposed Standard o Definition of Managed Objects for the Ethernet WAN Interface Sublayer Proposed Standard o Applicability Statement for Reclassification of RFC 1643 to Historic Status Informational At the same time, the IESG approved the re-classification of RFC1643 to Historic Status. Technical Summary o Definitions of Managed Objects for the Ethernet-like Interface Types. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like interfaces. This memo obsoletes RFC 2665. It updates that specification by including management information useful for the management of 10 Gigabit per second (Gb/s) Ethernet interfaces. o Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. o Definition of Managed Objects for the Ethernet WAN Interface Sublayer This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). The MIB module defined in this memo is an extension of the SONET/SDH Interface MIB and is implemented in conjunction with it and with the Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the Interfaces Group MIB, and the Inverted Stack Table MIB. o Applicability Statement for Reclassification of RFC 1643 to Historic Status This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation. Working Group Summary There is Working Group Consensus on the above documents for Proposed Standard and for reclassification of RFC1643 to Historic Status. Protocol Quality These documents have been reviewed for the IESG by Bert Wijnen. RFC-Editor note: In document draft-ietf-hubmib-mau-mib-v3-04.txt, pls remove an extraneous "IANA. " on page 25. CURRENT TEXT: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. IANA. If the MAU type is unknown, the object identifier SHOULD BE: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Jun 17 00:43:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16785 for ; Tue, 17 Jun 2003 00:43:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJN0a28692; Mon, 16 Jun 2003 15:23:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GJM1m28656 for ; Mon, 16 Jun 2003 15:22:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27300; Mon, 16 Jun 2003 15:21:55 -0400 (EDT) Message-Id: <200306161921.PAA27300@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , hubmib@ietf.org From: The IESG Date: Mon, 16 Jun 2003 15:21:55 -0400 Subject: [Hubmib] Protocol Action: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard 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: , The IESG has approved the following documents. These documents are the product of the Ethernet Interfaces and Hub MIB Working Group. The IESG contact persons are Randy Bush and Bert Wijnen o Definitions of Managed Objects for the Ethernet-like Interface Types Proposed Standard o Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Proposed Standard o Definition of Managed Objects for the Ethernet WAN Interface Sublayer Proposed Standard o Applicability Statement for Reclassification of RFC 1643 to Historic Status Informational At the same time, the IESG approved the re-classification of RFC1643 to Historic Status. Technical Summary o Definitions of Managed Objects for the Ethernet-like Interface Types. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like interfaces. This memo obsoletes RFC 2665. It updates that specification by including management information useful for the management of 10 Gigabit per second (Gb/s) Ethernet interfaces. o Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. o Definition of Managed Objects for the Ethernet WAN Interface Sublayer This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). The MIB module defined in this memo is an extension of the SONET/SDH Interface MIB and is implemented in conjunction with it and with the Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the Interfaces Group MIB, and the Inverted Stack Table MIB. o Applicability Statement for Reclassification of RFC 1643 to Historic Status This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation. Working Group Summary There is Working Group Consensus on the above documents for Proposed Standard and for reclassification of RFC1643 to Historic Status. Protocol Quality These documents have been reviewed for the IESG by Bert Wijnen. RFC-Editor note: In document draft-ietf-hubmib-mau-mib-v3-04.txt, pls remove an extraneous "IANA. " on page 25. CURRENT TEXT: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. IANA. If the MAU type is unknown, the object identifier SHOULD BE: DESCRIPTION "This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined above. If the MAU type is unknown, the object identifier Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Fri Jun 20 14:27:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23083 for ; Fri, 20 Jun 2003 14:27:35 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KIR7c06113 for hubmib-archive@odin.ietf.org; Fri, 20 Jun 2003 14:27:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQbH-0001V4-4m; Fri, 20 Jun 2003 14:27:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQb0-0001Rv-Gk for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 14:26:46 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22740; Fri, 20 Jun 2003 14:26:43 -0400 (EDT) Message-Id: <200306201826.OAA22740@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 20 Jun 2003 14:26:42 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt Pages : 21 Date : 2003-6-20 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-20140137.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-20140137.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Jun 20 14:53:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27303 for ; Fri, 20 Jun 2003 14:53:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TR0P-0003oA-82; Fri, 20 Jun 2003 14:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQzc-0003ki-UB for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 14:52:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27138 for ; Fri, 20 Jun 2003 14:52:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TQzZ-0000dm-00 for hubmib@ietf.org; Fri, 20 Jun 2003 14:52:09 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19TQzY-0000d7-00 for hubmib@ietf.org; Fri, 20 Jun 2003 14:52:09 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5KIq0Z04589 for ; Fri, 20 Jun 2003 11:52:00 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 20 Jun 2003 11:51:59 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: Re: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt In-Reply-To: <200306201826.OAA22740@ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Fri, 20 Jun 2003 Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line > Internet-Drafts directories. This draft is a work item of the > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt > Pages : 21 > Date : 2003-6-20 This version addresses all my previous "must-fix" MIB doctor review comments and does not raise any new ones. It also seems to address all the other WG Last Call comments; if the other commenters are indeed satisfied, I think that we forward this document to the IESG for consideration as a Proposed Standard. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Fri Jun 20 15:14:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00498 for ; Fri, 20 Jun 2003 15:14:30 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KJE1K19165 for hubmib-archive@odin.ietf.org; Fri, 20 Jun 2003 15:14:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRKj-0004z0-7A; Fri, 20 Jun 2003 15:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRKd-0004yg-VF for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 15:13:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00408 for ; Fri, 20 Jun 2003 15:13:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TRKc-0001LN-00 for hubmib@ietf.org; Fri, 20 Jun 2003 15:13:55 -0400 Received: from ctron-dnm.enterasys.com ([12.25.1.120] ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 19TRKb-0001L6-00 for hubmib@ietf.org; Fri, 20 Jun 2003 15:13:53 -0400 Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id PAA27725 for ; Fri, 20 Jun 2003 15:27:24 -0400 (EDT) Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma027708; Fri, 20 Jun 03 15:27:16 -0400 Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2 with InterScan Messaging Security Suite; Fri, 20 Jun 2003 15:14:40 -0400 Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 20 Jun 2003 15:14:40 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Date: Fri, 20 Jun 2003 15:14:39 -0400 Message-ID: Thread-Topic: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Thread-Index: AcM3XWTPheeUAh+qS1y9Rl7OBnrLagAAokbA From: "McTague, Charles" To: "C. M. Heard" , "Hub MIB Mailing List" X-OriginalArrivalTime: 20 Jun 2003 19:14:40.0080 (UTC) FILETIME=[328A0500:01C33760] 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: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA00498 This draft does seem to address my original concerns about sparse object numbering. I did just notice that there is OID sparseness in the notifications (there is no 2 or 3) but I'm fine with it if everyone else is. chuck --------------------------- Charles McTague Principal Firmware Engineer Enterasys Networks, Inc. >-----Original Message----- >From: C. M. Heard [mailto:heard@pobox.com] >Sent: Fri, 20 June, 2003 2:52 PM >To: Hub MIB Mailing List >Subject: Re: [Hubmib] I-D >ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt > > >On Fri, 20 Jun 2003 Internet-Drafts@ietf.org wrote: >> A New Internet-Draft is available from the on-line >> Internet-Drafts directories. This draft is a work item of the >> Ethernet Interfaces and Hub MIB Working Group of the IETF. >> >> Title : Power Ethernet MIB >> Author(s) : A. Berger, D. Romascanu >> Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt >> Pages : 21 >> Date : 2003-6-20 > >This version addresses all my previous "must-fix" MIB doctor review >comments and does not raise any new ones. It also seems to address >all the other WG Last Call comments; if the other commenters are >indeed satisfied, I think that we forward this document to the IESG >for consideration as a Proposed Standard. > >Mike Heard > > >_______________________________________________ >Hubmib mailing list >Hubmib@ietf.org >https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Jun 20 15:17:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23084 for ; Fri, 20 Jun 2003 14:27:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQbH-0001V4-4m; Fri, 20 Jun 2003 14:27:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQb0-0001Rv-Gk for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 14:26:46 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22740; Fri, 20 Jun 2003 14:26:43 -0400 (EDT) Message-Id: <200306201826.OAA22740@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 20 Jun 2003 14:26:42 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt Pages : 21 Date : 2003-6-20 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-20140137.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-20140137.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Fri Jun 20 15:30:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02895 for ; Fri, 20 Jun 2003 15:30:33 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KJU4p22421 for hubmib-archive@odin.ietf.org; Fri, 20 Jun 2003 15:30:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRaD-0005pJ-1d; Fri, 20 Jun 2003 15:30:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRa7-0005oy-DO for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 15:29:55 -0400 Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02771 for ; Fri, 20 Jun 2003 15:29:49 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5KJTjo17776 for ; Fri, 20 Jun 2003 12:29:45 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 20 Jun 2003 12:29:44 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Fri, 20 Jun 2003, McTague, Charles wrote: > This draft does seem to address my original concerns about sparse > object numbering. I did just notice that there is OID sparseness > in the notifications (there is no 2 or 3) but I'm fine with it if > everyone else is. We both seem to have missed this in our previous comments. Ideally it would be fixed but I am willing to leave it to the discretion of the document authors. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Jun 20 15:30:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02894 for ; Fri, 20 Jun 2003 15:30:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRaD-0005pJ-1d; Fri, 20 Jun 2003 15:30:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRa7-0005oy-DO for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 15:29:55 -0400 Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02771 for ; Fri, 20 Jun 2003 15:29:49 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5KJTjo17776 for ; Fri, 20 Jun 2003 12:29:45 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 20 Jun 2003 12:29:44 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Fri, 20 Jun 2003, McTague, Charles wrote: > This draft does seem to address my original concerns about sparse > object numbering. I did just notice that there is OID sparseness > in the notifications (there is no 2 or 3) but I'm fine with it if > everyone else is. We both seem to have missed this in our previous comments. Ideally it would be fixed but I am willing to leave it to the discretion of the document authors. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Fri Jun 20 15:41:13 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27304 for ; Fri, 20 Jun 2003 14:53:28 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KIr1414649 for hubmib-archive@odin.ietf.org; Fri, 20 Jun 2003 14:53:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TR0P-0003oA-82; Fri, 20 Jun 2003 14:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TQzc-0003ki-UB for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 14:52:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27138 for ; Fri, 20 Jun 2003 14:52:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TQzZ-0000dm-00 for hubmib@ietf.org; Fri, 20 Jun 2003 14:52:09 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19TQzY-0000d7-00 for hubmib@ietf.org; Fri, 20 Jun 2003 14:52:09 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5KIq0Z04589 for ; Fri, 20 Jun 2003 11:52:00 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 20 Jun 2003 11:51:59 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: Re: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt In-Reply-To: <200306201826.OAA22740@ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Fri, 20 Jun 2003 Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line > Internet-Drafts directories. This draft is a work item of the > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt > Pages : 21 > Date : 2003-6-20 This version addresses all my previous "must-fix" MIB doctor review comments and does not raise any new ones. It also seems to address all the other WG Last Call comments; if the other commenters are indeed satisfied, I think that we forward this document to the IESG for consideration as a Proposed Standard. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Jun 20 16:02:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00499 for ; Fri, 20 Jun 2003 15:14:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRKj-0004z0-7A; Fri, 20 Jun 2003 15:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TRKd-0004yg-VF for hubmib@optimus.ietf.org; Fri, 20 Jun 2003 15:13:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00408 for ; Fri, 20 Jun 2003 15:13:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TRKc-0001LN-00 for hubmib@ietf.org; Fri, 20 Jun 2003 15:13:55 -0400 Received: from ctron-dnm.enterasys.com ([12.25.1.120] ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 19TRKb-0001L6-00 for hubmib@ietf.org; Fri, 20 Jun 2003 15:13:53 -0400 Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id PAA27725 for ; Fri, 20 Jun 2003 15:27:24 -0400 (EDT) Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma027708; Fri, 20 Jun 03 15:27:16 -0400 Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2 with InterScan Messaging Security Suite; Fri, 20 Jun 2003 15:14:40 -0400 Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 20 Jun 2003 15:14:40 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Date: Fri, 20 Jun 2003 15:14:39 -0400 Message-ID: Thread-Topic: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Thread-Index: AcM3XWTPheeUAh+qS1y9Rl7OBnrLagAAokbA From: "McTague, Charles" To: "C. M. Heard" , "Hub MIB Mailing List" X-OriginalArrivalTime: 20 Jun 2003 19:14:40.0080 (UTC) FILETIME=[328A0500:01C33760] 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: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA00499 This draft does seem to address my original concerns about sparse object numbering. I did just notice that there is OID sparseness in the notifications (there is no 2 or 3) but I'm fine with it if everyone else is. chuck --------------------------- Charles McTague Principal Firmware Engineer Enterasys Networks, Inc. >-----Original Message----- >From: C. M. Heard [mailto:heard@pobox.com] >Sent: Fri, 20 June, 2003 2:52 PM >To: Hub MIB Mailing List >Subject: Re: [Hubmib] I-D >ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt > > >On Fri, 20 Jun 2003 Internet-Drafts@ietf.org wrote: >> A New Internet-Draft is available from the on-line >> Internet-Drafts directories. This draft is a work item of the >> Ethernet Interfaces and Hub MIB Working Group of the IETF. >> >> Title : Power Ethernet MIB >> Author(s) : A. Berger, D. Romascanu >> Filename : draft-ietf-hubmib-power-ethernet-mib-06.txt >> Pages : 21 >> Date : 2003-6-20 > >This version addresses all my previous "must-fix" MIB doctor review >comments and does not raise any new ones. It also seems to address >all the other WG Last Call comments; if the other commenters are >indeed satisfied, I think that we forward this document to the IESG >for consideration as a Proposed Standard. > >Mike Heard > > >_______________________________________________ >Hubmib mailing list >Hubmib@ietf.org >https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sun Jun 22 02:18:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05880 for ; Sun, 22 Jun 2003 02:18:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TyAr-0006dY-FG; Sun, 22 Jun 2003 02:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TyAE-0006dF-OU for hubmib@optimus.ietf.org; Sun, 22 Jun 2003 02:17:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05766 for ; Sun, 22 Jun 2003 02:17:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TyA6-0002rN-00 for hubmib@ietf.org; Sun, 22 Jun 2003 02:17:14 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19Ty9v-0002rK-00 for hubmib@ietf.org; Sun, 22 Jun 2003 02:17:03 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5M6DV822269 for ; Sun, 22 Jun 2003 02:13:31 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5M6DUf22263 for ; Sun, 22 Jun 2003 02:13:30 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Date: Sun, 22 Jun 2003 09:16:42 +0300 Message-ID: Thread-Topic: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Thread-Index: AcM3Ymn8cvS/cngTTvekadtVvx+I2ABI1nDw From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hub MIB Mailing List" 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 I will issue version 07 fixing this problem. Thanks to both of you for = the careful reviewing of the draft.=20 Dan > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, June 20, 2003 10:30 PM > To: Hub MIB Mailing List > Subject: RE: [Hubmib] I-D=20 > ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt >=20 >=20 > On Fri, 20 Jun 2003, McTague, Charles wrote: > > This draft does seem to address my original concerns about sparse > > object numbering. I did just notice that there is OID sparseness > > in the notifications (there is no 2 or 3) but I'm fine with it if=20 > > everyone else is. >=20 > We both seem to have missed this in our previous comments. Ideally > it would be fixed but I am willing to leave it to the discretion of > the document authors. >=20 > Mike Heard >=20 >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Sun Jun 22 02:18:32 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05884 for ; Sun, 22 Jun 2003 02:18:32 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5M6I4D25529 for hubmib-archive@odin.ietf.org; Sun, 22 Jun 2003 02:18:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TyAr-0006dY-FG; Sun, 22 Jun 2003 02:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TyAE-0006dF-OU for hubmib@optimus.ietf.org; Sun, 22 Jun 2003 02:17:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05766 for ; Sun, 22 Jun 2003 02:17:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TyA6-0002rN-00 for hubmib@ietf.org; Sun, 22 Jun 2003 02:17:14 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19Ty9v-0002rK-00 for hubmib@ietf.org; Sun, 22 Jun 2003 02:17:03 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5M6DV822269 for ; Sun, 22 Jun 2003 02:13:31 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5M6DUf22263 for ; Sun, 22 Jun 2003 02:13:30 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Date: Sun, 22 Jun 2003 09:16:42 +0300 Message-ID: Thread-Topic: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt Thread-Index: AcM3Ymn8cvS/cngTTvekadtVvx+I2ABI1nDw From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hub MIB Mailing List" 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 I will issue version 07 fixing this problem. Thanks to both of you for = the careful reviewing of the draft.=20 Dan > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, June 20, 2003 10:30 PM > To: Hub MIB Mailing List > Subject: RE: [Hubmib] I-D=20 > ACTION:draft-ietf-hubmib-power-ethernet-mib-06.txt >=20 >=20 > On Fri, 20 Jun 2003, McTague, Charles wrote: > > This draft does seem to address my original concerns about sparse > > object numbering. I did just notice that there is OID sparseness > > in the notifications (there is no 2 or 3) but I'm fine with it if=20 > > everyone else is. >=20 > We both seem to have missed this in our previous comments. Ideally > it would be fixed but I am willing to leave it to the discretion of > the document authors. >=20 > Mike Heard >=20 >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue Jun 24 06:25:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09370 for ; Tue, 24 Jun 2003 06:25:27 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OAP1b15581 for hubmib-archive@odin.ietf.org; Tue, 24 Jun 2003 06:25:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Ukyy-00042w-M1; Tue, 24 Jun 2003 06:25:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uky1-0003ze-9A for hubmib@optimus.ietf.org; Tue, 24 Jun 2003 06:24:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09248; Tue, 24 Jun 2003 06:23:56 -0400 (EDT) Message-Id: <200306241023.GAA09248@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 24 Jun 2003 06:23:56 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-07.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-07.txt Pages : 21 Date : 2003-6-23 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-23141807.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-23141807.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Jun 24 07:12:07 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09371 for ; Tue, 24 Jun 2003 06:25:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Ukyy-00042w-M1; Tue, 24 Jun 2003 06:25:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uky1-0003ze-9A for hubmib@optimus.ietf.org; Tue, 24 Jun 2003 06:24:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09248; Tue, 24 Jun 2003 06:23:56 -0400 (EDT) Message-Id: <200306241023.GAA09248@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 24 Jun 2003 06:23:56 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-07.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-07.txt Pages : 21 Date : 2003-6-23 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-23141807.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-23141807.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 02:26:14 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09878 for ; Thu, 26 Jun 2003 02:26:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQBp-0005Xb-Ob; Thu, 26 Jun 2003 02:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQBH-0005S6-Ei for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 02:24:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09760 for ; Thu, 26 Jun 2003 02:24:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQAr-0005zi-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:24:01 -0400 Received: from [192.114.173.84] (helo=sun.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 19VQAg-0005zZ-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:23:50 -0400 Received: by sun.powerdsine.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Jun 2003 09:21:02 +0200 Message-ID: <0C2C45920CE4D611A7CE00D0B723EDA5D7266B@sun.powerdsine.com> From: Daniel Feldman To: "'hubmib@ietf.org'" Date: Thu, 26 Jun 2003 09:21:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] Power Ethernet MIB drafts 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: , Dear Mr. Romascanu, I was looking at http://www.ietf.org/html.charters/hubmib-charter.html and the link to the Power Ethernet MIB now points to a draft 8 which has its text cut (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08 .txt), while the last message in the mailing list (http://www1.ietf.org/mail-archive/working-groups/hubmib/current/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > 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 Thu Jun 26 02:26:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09877 for ; Thu, 26 Jun 2003 02:26:14 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5Q6P2121322 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 02:25:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQBp-0005Xb-Ob; Thu, 26 Jun 2003 02:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQBH-0005S6-Ei for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 02:24:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09760 for ; Thu, 26 Jun 2003 02:24:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQAr-0005zi-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:24:01 -0400 Received: from [192.114.173.84] (helo=sun.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 19VQAg-0005zZ-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:23:50 -0400 Received: by sun.powerdsine.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Jun 2003 09:21:02 +0200 Message-ID: <0C2C45920CE4D611A7CE00D0B723EDA5D7266B@sun.powerdsine.com> From: Daniel Feldman To: "'hubmib@ietf.org'" Date: Thu, 26 Jun 2003 09:21:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] Power Ethernet MIB drafts 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: , Dear Mr. Romascanu, I was looking at http://www.ietf.org/html.charters/hubmib-charter.html and the link to the Power Ethernet MIB now points to a draft 8 which has its text cut (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08 .txt), while the last message in the mailing list (http://www1.ietf.org/mail-archive/working-groups/hubmib/current/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > 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 Thu Jun 26 04:24:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11977 for ; Thu, 26 Jun 2003 04:24:39 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5Q8OCE22131 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 04:24:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VS39-0005j8-4t; Thu, 26 Jun 2003 04:24:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VROl-0003FV-TM for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 03:42:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11252 for ; Thu, 26 Jun 2003 03:42:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VROU-0006PH-00 for hubmib@ietf.org; Thu, 26 Jun 2003 03:42:10 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19VROJ-0006PC-00 for hubmib@ietf.org; Thu, 26 Jun 2003 03:41:59 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5Q7fRr17855; Thu, 26 Jun 2003 00:41:27 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 26 Jun 2003 00:41:26 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Daniel Feldman cc: "'hubmib@ietf.org'" Subject: Re: [Hubmib] Power Ethernet MIB drafts In-Reply-To: <0C2C45920CE4D611A7CE00D0B723EDA5D7266B@sun.powerdsine.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Thu, 26 Jun 2003, Daniel Feldman wrote: > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/current/msg00379.ht > ml) talked about a draft 7. > Do you know what's the latest and most updated draft? Is it in last > call? The latest draft is -08, which is available in the I-D repository but has not yet been announced. The announcement should appear shortly. Dan will have the authoritative answer, but my understanding is that WG last call is done and the next step is to send the document to the IESG (at which point it will undergo IETF last call). BTW, the only difference between -07 and -08 is a fix to the LAST-UPDATED time in the MIB module. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 05:12:12 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11976 for ; Thu, 26 Jun 2003 04:24:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VS39-0005j8-4t; Thu, 26 Jun 2003 04:24:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VROl-0003FV-TM for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 03:42:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11252 for ; Thu, 26 Jun 2003 03:42:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VROU-0006PH-00 for hubmib@ietf.org; Thu, 26 Jun 2003 03:42:10 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19VROJ-0006PC-00 for hubmib@ietf.org; Thu, 26 Jun 2003 03:41:59 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h5Q7fRr17855; Thu, 26 Jun 2003 00:41:27 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 26 Jun 2003 00:41:26 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Daniel Feldman cc: "'hubmib@ietf.org'" Subject: Re: [Hubmib] Power Ethernet MIB drafts In-Reply-To: <0C2C45920CE4D611A7CE00D0B723EDA5D7266B@sun.powerdsine.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Thu, 26 Jun 2003, Daniel Feldman wrote: > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/current/msg00379.ht > ml) talked about a draft 7. > Do you know what's the latest and most updated draft? Is it in last > call? The latest draft is -08, which is available in the I-D repository but has not yet been announced. The announcement should appear shortly. Dan will have the authoritative answer, but my understanding is that WG last call is done and the next step is to send the document to the IESG (at which point it will undergo IETF last call). BTW, the only difference between -07 and -08 is a fix to the LAST-UPDATED time in the MIB module. Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 06:21:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14301 for ; Thu, 26 Jun 2003 06:21:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTsD-0007uE-TC; Thu, 26 Jun 2003 06:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTrR-0007qu-Au for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 06:20:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14275 for ; Thu, 26 Jun 2003 06:20:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VTrN-0007AL-00 for hubmib@ietf.org; Thu, 26 Jun 2003 06:20:09 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19VTrC-0007AA-00 for hubmib@ietf.org; Thu, 26 Jun 2003 06:19:58 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA11226 for ; Thu, 26 Jun 2003 06:16:56 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA11222 for ; Thu, 26 Jun 2003 06:16:55 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] Power Ethernet MIB drafts Date: Thu, 26 Jun 2003 13:19:37 +0300 Message-ID: Thread-Topic: [Hubmib] Power Ethernet MIB drafts Thread-Index: AcM7q7ImhqAxlABYQHGAdZtky67vZAAIC8zQ From: "Romascanu, Dan (Dan)" To: "Daniel Feldman" , 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 Daniel, The latest version is draft 8. It was submitted on Monday, 6/23 but the = announcement is yet to show up. There is no difference between draft 7 = and draft 8, excepting the correction of an in-accurate date in the LAST = UPDATE clause.=20 The MIB already went through the second WG Last Call, and all the = comments received during the last call were incorporated. As soon as the = announcement will be out, I will submit the document to the IESG for = consideration as Proposed Standard. Regards, Dan > -----Original Message----- > From: Daniel Feldman [mailto:danielf@powerdsine.com] > Sent: 26 June, 2003 10:21 AM > To: 'hubmib@ietf.org' > Subject: [Hubmib] Power Ethernet MIB drafts >=20 >=20 > Dear Mr. Romascanu, > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the=20 > link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e > thernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/curre nt/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > Daniel Feldman >=20 > Product Manager=20 > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 06:23:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14390 for ; Thu, 26 Jun 2003 06:23:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTu9-000824-Ka; Thu, 26 Jun 2003 06:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQtw-0000vi-An for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 03:12:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09071 for ; Thu, 26 Jun 2003 02:14:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQ1M-0005vm-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:14:12 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19VQ1B-0005vf-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:14:02 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA01968 for ; Thu, 26 Jun 2003 01:51:25 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA01904 for ; Thu, 26 Jun 2003 01:51:23 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33BA7.5A2BA4AF" Date: Thu, 26 Jun 2003 08:54:05 +0300 Message-ID: Thread-Topic: SG 15 Representatives at IETF #57 Thread-Index: AcM7SjQ7cehH1cjKQaWCzaXykVXYEAAXGEGA From: "Romascanu, Dan (Dan)" To: "Peter Wery" , , , , , , , , , , , , , , , , Cc: , , , , , , , , , , , Subject: [Hubmib] RE: SG 15 Representatives at IETF #57 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_01C33BA7.5A2BA4AF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Peter, =20 Thank you for your message. =20 The Ethernet Interfaces and Hub MIB Working Group (hubmib) has no = meeting scheduled at the 57th IETF. If you are interested in the WG = activity, and would like to provide inputs related to its scope, you may = use the WG e-mail list - hubmib@ietf.org. =20 Regards, =20 Dan =20 Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG =20 -----Original Message----- From: Peter Wery [mailto:wery@nortelnetworks.com] Sent: 25 June, 2003 9:46 PM To: ronald.p.bonica@wcom.com; 'kireeti@juniper.net'; = james_luciani@mindspring.com; awduche@isocore.com; avri@acm.org; = ksundell@nortelnetworks.com; swallow@cisco.com; loa@pi.se; = rwilder@masergy.com; ejk@tech.org; jboyle@pdnets.com; Romascanu, Dan = (Dan); fayely98@hotmail.com; tbrunner@omneon.com; = randy_presuhn@mindspring.com; mundy@tislabs.com; dbh@enterasys.com Cc: randy@psg.com; 'sob@harvard.edu'; 'bwijnen@lucent.com'; = zinin@psg.com; narten@us.ibm.com; erik.nordmark@sun.com; = sjtrowbridge@lucent.com; wesam.alanqar@mail.sprint.com; = hklam@lucent.com; jonathan.sadler@tellabs.com; paolo.rosa@itu.int Subject: SG 15 Representatives at IETF #57 Gentlemen,=20 in line with the provisions of the 'IETF and ITU-T Collaboration = Guidelines' (RFC 3356, clause 3.2.2), please be advised that the = following people plan to participate (registration fees apply) in your = WGs at the upcoming IETF # 57 (13-18 July 2003, Vienna, Austria): - Wesam Alanqar in his role as 'SG 15 Representative to IETF ccamp and = ipo'=20 - Jonathan Sadler in his role as 'SG 15 Representative to IETF gsmp'=20 - Kam Lam in his role as 'SG 15 Representative to IETF on Transport = Network Management', i.e. =20 WGs atommib, hubmib, ifmib, disman, snmpv3=20 - Steve Trowbridge (Vice-Chairman of SG 15) in his role as Chairman of = ITU-T WP 3/15 (OTN =20 Structure), i.e. relevant to IETF ccamp, ipo, mpls, ppvpn, tewg and = other sub-IP related activities.=20 These SG 15 people may also present Liaison Statements from SG 15 as = appropriate. =20 Regards,=20 Peter Wery=20 Chairman ITU-T Study Group 15=20 T: +1 613 763 7603=20 F: +1 613 763 2697=20 E: wery@nortelnetworks.com=20 ------_=_NextPart_001_01C33BA7.5A2BA4AF Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SG 15 Representatives at IETF #57
Peter,
 
Thank you for your = message.
 
The Ethernet Interfaces and Hub MIB Working Group (hubmib) has = no meeting=20 scheduled at the 57th IETF. If you are interested in the WG=20 activity, and would like to provide inputs related to its scope, = you may=20 use the WG e-mail list - hubmib@ietf.org.=
 
Regards,
 
Dan
 
Dan Romascanu,
Chair, IETF Ethernet Interfaces and Hub MIB=20 WG
 
-----Original Message-----
From: Peter Wery=20 [mailto:wery@nortelnetworks.com]
Sent: 25 June, 2003 9:46=20 PM
To: ronald.p.bonica@wcom.com; 'kireeti@juniper.net';=20 james_luciani@mindspring.com; awduche@isocore.com; avri@acm.org;=20 ksundell@nortelnetworks.com; swallow@cisco.com; loa@pi.se;=20 rwilder@masergy.com; ejk@tech.org; jboyle@pdnets.com; Romascanu, Dan = (Dan);=20 fayely98@hotmail.com; tbrunner@omneon.com; = randy_presuhn@mindspring.com;=20 mundy@tislabs.com; dbh@enterasys.com
Cc: randy@psg.com;=20 'sob@harvard.edu'; 'bwijnen@lucent.com'; zinin@psg.com; = narten@us.ibm.com;=20 erik.nordmark@sun.com; sjtrowbridge@lucent.com; = wesam.alanqar@mail.sprint.com;=20 hklam@lucent.com; jonathan.sadler@tellabs.com;=20 paolo.rosa@itu.int
Subject: SG 15 Representatives at IETF=20 #57

Gentlemen,

in line with the provisions of the = 'IETF and ITU-T=20 Collaboration Guidelines' (RFC = 3356,=20 clause 3.2.2), please be advised that the = following=20 people plan to participate (registration fees apply)  in your WGs = at the=20 upcoming IETF # 57 (13-18 July 2003, Vienna, Austria):

- Wesam Alanqar in his role as  = 'SG 15=20 Representative to IETF ccamp and ipo'
-=20 Jonathan Sadler in his role as  'SG 15 Representative to IETF=20 gsmp'
- Kam Lam  in his = role as =20 'SG 15 Representative to IETF on Transport Network Management', = i.e. =20
  WGs atommib, hubmib, = ifmib, disman,=20 snmpv3
- Steve Trowbridge = (Vice-Chairman of=20 SG 15) in his role as Chairman of ITU-T WP 3/15 (OTN  =
  Structure), i.e. relevant to IETF ccamp, = ipo, mpls,=20 ppvpn, tewg and other sub-IP related activities.

These SG 15 people may also present = Liaison=20 Statements from SG 15 as appropriate. 

Regards,

Peter=20 Wery
Chairman ITU-T=20 Study Group 15

T:     +1 613 763=20 7603
F:     +1 613 763 2697
E:     = wery@nortelnetworks.com=20



------_=_NextPart_001_01C33BA7.5A2BA4AF-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Jun 26 06:23:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14389 for ; Thu, 26 Jun 2003 06:23:27 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QAN1G30886 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 06:23:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTu9-000824-Ka; Thu, 26 Jun 2003 06:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQtw-0000vi-An for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 03:12:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09071 for ; Thu, 26 Jun 2003 02:14:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQ1M-0005vm-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:14:12 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19VQ1B-0005vf-00 for hubmib@ietf.org; Thu, 26 Jun 2003 02:14:02 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA01968 for ; Thu, 26 Jun 2003 01:51:25 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id BAA01904 for ; Thu, 26 Jun 2003 01:51:23 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33BA7.5A2BA4AF" Date: Thu, 26 Jun 2003 08:54:05 +0300 Message-ID: Thread-Topic: SG 15 Representatives at IETF #57 Thread-Index: AcM7SjQ7cehH1cjKQaWCzaXykVXYEAAXGEGA From: "Romascanu, Dan (Dan)" To: "Peter Wery" , , , , , , , , , , , , , , , , Cc: , , , , , , , , , , , Subject: [Hubmib] RE: SG 15 Representatives at IETF #57 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_01C33BA7.5A2BA4AF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Peter, =20 Thank you for your message. =20 The Ethernet Interfaces and Hub MIB Working Group (hubmib) has no = meeting scheduled at the 57th IETF. If you are interested in the WG = activity, and would like to provide inputs related to its scope, you may = use the WG e-mail list - hubmib@ietf.org. =20 Regards, =20 Dan =20 Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG =20 -----Original Message----- From: Peter Wery [mailto:wery@nortelnetworks.com] Sent: 25 June, 2003 9:46 PM To: ronald.p.bonica@wcom.com; 'kireeti@juniper.net'; = james_luciani@mindspring.com; awduche@isocore.com; avri@acm.org; = ksundell@nortelnetworks.com; swallow@cisco.com; loa@pi.se; = rwilder@masergy.com; ejk@tech.org; jboyle@pdnets.com; Romascanu, Dan = (Dan); fayely98@hotmail.com; tbrunner@omneon.com; = randy_presuhn@mindspring.com; mundy@tislabs.com; dbh@enterasys.com Cc: randy@psg.com; 'sob@harvard.edu'; 'bwijnen@lucent.com'; = zinin@psg.com; narten@us.ibm.com; erik.nordmark@sun.com; = sjtrowbridge@lucent.com; wesam.alanqar@mail.sprint.com; = hklam@lucent.com; jonathan.sadler@tellabs.com; paolo.rosa@itu.int Subject: SG 15 Representatives at IETF #57 Gentlemen,=20 in line with the provisions of the 'IETF and ITU-T Collaboration = Guidelines' (RFC 3356, clause 3.2.2), please be advised that the = following people plan to participate (registration fees apply) in your = WGs at the upcoming IETF # 57 (13-18 July 2003, Vienna, Austria): - Wesam Alanqar in his role as 'SG 15 Representative to IETF ccamp and = ipo'=20 - Jonathan Sadler in his role as 'SG 15 Representative to IETF gsmp'=20 - Kam Lam in his role as 'SG 15 Representative to IETF on Transport = Network Management', i.e. =20 WGs atommib, hubmib, ifmib, disman, snmpv3=20 - Steve Trowbridge (Vice-Chairman of SG 15) in his role as Chairman of = ITU-T WP 3/15 (OTN =20 Structure), i.e. relevant to IETF ccamp, ipo, mpls, ppvpn, tewg and = other sub-IP related activities.=20 These SG 15 people may also present Liaison Statements from SG 15 as = appropriate. =20 Regards,=20 Peter Wery=20 Chairman ITU-T Study Group 15=20 T: +1 613 763 7603=20 F: +1 613 763 2697=20 E: wery@nortelnetworks.com=20 ------_=_NextPart_001_01C33BA7.5A2BA4AF Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SG 15 Representatives at IETF #57
Peter,
 
Thank you for your = message.
 
The Ethernet Interfaces and Hub MIB Working Group (hubmib) has = no meeting=20 scheduled at the 57th IETF. If you are interested in the WG=20 activity, and would like to provide inputs related to its scope, = you may=20 use the WG e-mail list - hubmib@ietf.org.=
 
Regards,
 
Dan
 
Dan Romascanu,
Chair, IETF Ethernet Interfaces and Hub MIB=20 WG
 
-----Original Message-----
From: Peter Wery=20 [mailto:wery@nortelnetworks.com]
Sent: 25 June, 2003 9:46=20 PM
To: ronald.p.bonica@wcom.com; 'kireeti@juniper.net';=20 james_luciani@mindspring.com; awduche@isocore.com; avri@acm.org;=20 ksundell@nortelnetworks.com; swallow@cisco.com; loa@pi.se;=20 rwilder@masergy.com; ejk@tech.org; jboyle@pdnets.com; Romascanu, Dan = (Dan);=20 fayely98@hotmail.com; tbrunner@omneon.com; = randy_presuhn@mindspring.com;=20 mundy@tislabs.com; dbh@enterasys.com
Cc: randy@psg.com;=20 'sob@harvard.edu'; 'bwijnen@lucent.com'; zinin@psg.com; = narten@us.ibm.com;=20 erik.nordmark@sun.com; sjtrowbridge@lucent.com; = wesam.alanqar@mail.sprint.com;=20 hklam@lucent.com; jonathan.sadler@tellabs.com;=20 paolo.rosa@itu.int
Subject: SG 15 Representatives at IETF=20 #57

Gentlemen,

in line with the provisions of the = 'IETF and ITU-T=20 Collaboration Guidelines' (RFC = 3356,=20 clause 3.2.2), please be advised that the = following=20 people plan to participate (registration fees apply)  in your WGs = at the=20 upcoming IETF # 57 (13-18 July 2003, Vienna, Austria):

- Wesam Alanqar in his role as  = 'SG 15=20 Representative to IETF ccamp and ipo'
-=20 Jonathan Sadler in his role as  'SG 15 Representative to IETF=20 gsmp'
- Kam Lam  in his = role as =20 'SG 15 Representative to IETF on Transport Network Management', = i.e. =20
  WGs atommib, hubmib, = ifmib, disman,=20 snmpv3
- Steve Trowbridge = (Vice-Chairman of=20 SG 15) in his role as Chairman of ITU-T WP 3/15 (OTN  =
  Structure), i.e. relevant to IETF ccamp, = ipo, mpls,=20 ppvpn, tewg and other sub-IP related activities.

These SG 15 people may also present = Liaison=20 Statements from SG 15 as appropriate. 

Regards,

Peter=20 Wery
Chairman ITU-T=20 Study Group 15

T:     +1 613 763=20 7603
F:     +1 613 763 2697
E:     = wery@nortelnetworks.com=20



------_=_NextPart_001_01C33BA7.5A2BA4AF-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Jun 26 07:07:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14302 for ; Thu, 26 Jun 2003 06:21:28 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QAL2L30410 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 06:21:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTsD-0007uE-TC; Thu, 26 Jun 2003 06:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTrR-0007qu-Au for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 06:20:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14275 for ; Thu, 26 Jun 2003 06:20:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VTrN-0007AL-00 for hubmib@ietf.org; Thu, 26 Jun 2003 06:20:09 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19VTrC-0007AA-00 for hubmib@ietf.org; Thu, 26 Jun 2003 06:19:58 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA11226 for ; Thu, 26 Jun 2003 06:16:56 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA11222 for ; Thu, 26 Jun 2003 06:16:55 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] Power Ethernet MIB drafts Date: Thu, 26 Jun 2003 13:19:37 +0300 Message-ID: Thread-Topic: [Hubmib] Power Ethernet MIB drafts Thread-Index: AcM7q7ImhqAxlABYQHGAdZtky67vZAAIC8zQ From: "Romascanu, Dan (Dan)" To: "Daniel Feldman" , 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 Daniel, The latest version is draft 8. It was submitted on Monday, 6/23 but the = announcement is yet to show up. There is no difference between draft 7 = and draft 8, excepting the correction of an in-accurate date in the LAST = UPDATE clause.=20 The MIB already went through the second WG Last Call, and all the = comments received during the last call were incorporated. As soon as the = announcement will be out, I will submit the document to the IESG for = consideration as Proposed Standard. Regards, Dan > -----Original Message----- > From: Daniel Feldman [mailto:danielf@powerdsine.com] > Sent: 26 June, 2003 10:21 AM > To: 'hubmib@ietf.org' > Subject: [Hubmib] Power Ethernet MIB drafts >=20 >=20 > Dear Mr. Romascanu, > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the=20 > link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e > thernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/curre nt/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > Daniel Feldman >=20 > Product Manager=20 > PowerDsine Ltd. > Tel: +972-9-775-5100 (Ext: 159) > Fax: +972-9-775-5112 > www.PowerDsine.com >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 08:03:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16444 for ; Thu, 26 Jun 2003 08:03:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVSu-0007oD-Nj; Thu, 26 Jun 2003 08:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVSj-0007o1-HK for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 08:02:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16296; Thu, 26 Jun 2003 08:02:47 -0400 (EDT) Message-Id: <200306261202.IAA16296@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 26 Jun 2003 08:02:46 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-08.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-08.txt Pages : 21 Date : 2003-6-25 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-26080121.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-26080121.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 08:12:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17389 for ; Thu, 26 Jun 2003 08:12:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVbc-0000ny-Jp; Thu, 26 Jun 2003 08:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVau-0000iw-L2 for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 08:11:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17324 for ; Thu, 26 Jun 2003 08:11:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VVat-0007mj-00 for hubmib@ietf.org; Thu, 26 Jun 2003 08:11:15 -0400 Received: from [192.114.173.84] (helo=sun.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 19VVai-0007mG-00 for hubmib@ietf.org; Thu, 26 Jun 2003 08:11:05 -0400 Received: by sun.powerdsine.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Jun 2003 15:07:57 +0200 Message-ID: <0C2C45920CE4D611A7CE00D0B723EDA5D72671@sun.powerdsine.com> From: Daniel Feldman To: hubmib@ietf.org Subject: RE: [Hubmib] Power Ethernet MIB drafts Date: Thu, 26 Jun 2003 15:07:53 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" 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: , Dan, thank you. I saw the announcement. The file in the IETF server ends at page 18 (there are two pages missing). Regards, Daniel -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, June 26, 2003 12:20 PM To: Daniel Feldman; hubmib@ietf.org Subject: RE: [Hubmib] Power Ethernet MIB drafts Daniel, The latest version is draft 8. It was submitted on Monday, 6/23 but the announcement is yet to show up. There is no difference between draft 7 and draft 8, excepting the correction of an in-accurate date in the LAST UPDATE clause. The MIB already went through the second WG Last Call, and all the comments received during the last call were incorporated. As soon as the announcement will be out, I will submit the document to the IESG for consideration as Proposed Standard. Regards, Dan > -----Original Message----- > From: Daniel Feldman [mailto:danielf@powerdsine.com] > Sent: 26 June, 2003 10:21 AM > To: 'hubmib@ietf.org' > Subject: [Hubmib] Power Ethernet MIB drafts > > > Dear Mr. Romascanu, > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the > link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e > thernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/curre nt/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > 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 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Jun 26 09:02:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17390 for ; Thu, 26 Jun 2003 08:12:29 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QCC0d03104 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 08:12:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVbc-0000ny-Jp; Thu, 26 Jun 2003 08:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVau-0000iw-L2 for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 08:11:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17324 for ; Thu, 26 Jun 2003 08:11:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VVat-0007mj-00 for hubmib@ietf.org; Thu, 26 Jun 2003 08:11:15 -0400 Received: from [192.114.173.84] (helo=sun.powerdsine.com) by ietf-mx with esmtp (Exim 4.12) id 19VVai-0007mG-00 for hubmib@ietf.org; Thu, 26 Jun 2003 08:11:05 -0400 Received: by sun.powerdsine.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Jun 2003 15:07:57 +0200 Message-ID: <0C2C45920CE4D611A7CE00D0B723EDA5D72671@sun.powerdsine.com> From: Daniel Feldman To: hubmib@ietf.org Subject: RE: [Hubmib] Power Ethernet MIB drafts Date: Thu, 26 Jun 2003 15:07:53 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" 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: , Dan, thank you. I saw the announcement. The file in the IETF server ends at page 18 (there are two pages missing). Regards, Daniel -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, June 26, 2003 12:20 PM To: Daniel Feldman; hubmib@ietf.org Subject: RE: [Hubmib] Power Ethernet MIB drafts Daniel, The latest version is draft 8. It was submitted on Monday, 6/23 but the announcement is yet to show up. There is no difference between draft 7 and draft 8, excepting the correction of an in-accurate date in the LAST UPDATE clause. The MIB already went through the second WG Last Call, and all the comments received during the last call were incorporated. As soon as the announcement will be out, I will submit the document to the IESG for consideration as Proposed Standard. Regards, Dan > -----Original Message----- > From: Daniel Feldman [mailto:danielf@powerdsine.com] > Sent: 26 June, 2003 10:21 AM > To: 'hubmib@ietf.org' > Subject: [Hubmib] Power Ethernet MIB drafts > > > Dear Mr. Romascanu, > I was looking at > http://www.ietf.org/html.charters/hubmib-charter.html and the > link to the > Power Ethernet MIB now points to a draft 8 which has its text cut > (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e > thernet-mib-08 > .txt), while the last message in the mailing list > (http://www1.ietf.org/mail-archive/working-groups/hubmib/curre nt/msg00379.ht ml) talked about a draft 7. Do you know what's the latest and most updated draft? Is it in last call? Thanks in advance, Daniel. > 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 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Jun 26 09:02:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16443 for ; Thu, 26 Jun 2003 08:03:30 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QC31U30034 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 08:03:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVSu-0007oD-Nj; Thu, 26 Jun 2003 08:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VVSj-0007o1-HK for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 08:02:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16296; Thu, 26 Jun 2003 08:02:47 -0400 (EDT) Message-Id: <200306261202.IAA16296@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 26 Jun 2003 08:02:46 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-08.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-08.txt Pages : 21 Date : 2003-6-25 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hubmib-power-ethernet-mib-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-6-26080121.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-26080121.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu Jun 26 09:14:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23577 for ; Thu, 26 Jun 2003 09:14:29 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QDE1w21025 for hubmib-archive@odin.ietf.org; Thu, 26 Jun 2003 09:14:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VWZd-0005Sr-B7; Thu, 26 Jun 2003 09:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VWZ0-0005SH-NI for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 09:13:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23535 for ; Thu, 26 Jun 2003 09:13:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VWYz-0001QR-00 for hubmib@ietf.org; Thu, 26 Jun 2003 09:13:21 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19VWYo-0001Q2-00 for hubmib@ietf.org; Thu, 26 Jun 2003 09:13:10 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5QD9ZE28285 for ; Thu, 26 Jun 2003 09:09:35 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5QD9Yc28251 for ; Thu, 26 Jun 2003 09:09:34 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33BE4.A3A13453" Date: Thu, 26 Jun 2003 16:12:48 +0300 Message-ID: Thread-Topic: Power Ethernet MIB Thread-Index: AcM748yR+tD8siwlS7Crg7ZNFJYsMAAAKXgQ From: "Romascanu, Dan (Dan)" To: , Cc: 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_01C33BE4.A3A13453 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable > Bert, Randy, >=20 > The Ethernet Interfaces and Hub MIB WG completed its work on the Power = Ethernet MIB, and is submitting = http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-= 08.txt to the IESG for consideration as a Proposed Standard. The = document went through the Working Group Last Call, and Area Director MIB = Doctor review. All comments received during the WG last call and MIB = Doctor review process have been received and fixes included in the last = version of the document. >=20 > Regards, >=20 > Dan >=20 ------_=_NextPart_001_01C33BE4.A3A13453 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB

Bert, Randy,

The Ethernet Interfaces and = Hub MIB WG completed its work on the Power Ethernet MIB, and is = submitting http://www.ietf.org/internet-drafts/draft-ietf-hubmib-pow= er-ethernet-mib-08.txt to the IESG for consideration as a Proposed = Standard. The document went through the Working Group Last Call, and = Area Director MIB Doctor review. All comments received during the WG = last call and MIB Doctor review process have been received and fixes = included in the last version of the document.

Regards,

Dan

------_=_NextPart_001_01C33BE4.A3A13453-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu Jun 26 10:25:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23578 for ; Thu, 26 Jun 2003 09:14:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VWZd-0005Sr-B7; Thu, 26 Jun 2003 09:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VWZ0-0005SH-NI for hubmib@optimus.ietf.org; Thu, 26 Jun 2003 09:13:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23535 for ; Thu, 26 Jun 2003 09:13:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VWYz-0001QR-00 for hubmib@ietf.org; Thu, 26 Jun 2003 09:13:21 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19VWYo-0001Q2-00 for hubmib@ietf.org; Thu, 26 Jun 2003 09:13:10 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5QD9ZE28285 for ; Thu, 26 Jun 2003 09:09:35 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5QD9Yc28251 for ; Thu, 26 Jun 2003 09:09:34 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33BE4.A3A13453" Date: Thu, 26 Jun 2003 16:12:48 +0300 Message-ID: Thread-Topic: Power Ethernet MIB Thread-Index: AcM748yR+tD8siwlS7Crg7ZNFJYsMAAAKXgQ From: "Romascanu, Dan (Dan)" To: , Cc: 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_01C33BE4.A3A13453 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable > Bert, Randy, >=20 > The Ethernet Interfaces and Hub MIB WG completed its work on the Power = Ethernet MIB, and is submitting = http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-= 08.txt to the IESG for consideration as a Proposed Standard. The = document went through the Working Group Last Call, and Area Director MIB = Doctor review. All comments received during the WG last call and MIB = Doctor review process have been received and fixes included in the last = version of the document. >=20 > Regards, >=20 > Dan >=20 ------_=_NextPart_001_01C33BE4.A3A13453 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB

Bert, Randy,

The Ethernet Interfaces and = Hub MIB WG completed its work on the Power Ethernet MIB, and is = submitting http://www.ietf.org/internet-drafts/draft-ietf-hubmib-pow= er-ethernet-mib-08.txt to the IESG for consideration as a Proposed = Standard. The document went through the Working Group Last Call, and = Area Director MIB Doctor review. All comments received during the WG = last call and MIB Doctor review process have been received and fixes = included in the last version of the document.

Regards,

Dan

------_=_NextPart_001_01C33BE4.A3A13453-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Sun Jun 29 22:41:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14860 for ; Sun, 29 Jun 2003 22:41:30 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5U2f3706271 for hubmib-archive@odin.ietf.org; Sun, 29 Jun 2003 22:41:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WobG-0001cw-Bw; Sun, 29 Jun 2003 22:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WoaK-0001b8-T1 for hubmib@optimus.ietf.org; Sun, 29 Jun 2003 22:40:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14785 for ; Sun, 29 Jun 2003 22:40:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WoaH-0002Wy-00 for hubmib@ietf.org; Sun, 29 Jun 2003 22:40:01 -0400 Received: from mail.alloptic.com ([12.47.49.133] helo=srvnt506.ALLOPTIC.COM) by ietf-mx with esmtp (Exim 4.12) id 19Woa6-0002WH-00 for hubmib@ietf.org; Sun, 29 Jun 2003 22:39:50 -0400 Received: by srvnt506.ALLOPTIC.COM with Internet Mail Service (5.5.2653.19) id ; Sun, 29 Jun 2003 19:39:08 -0700 Message-ID: <885489B3B89FB6449F93E525DF78777F627036@srvnt506.ALLOPTIC.COM> From: "Bemmel, Vincent" To: "'Romascanu, Dan (Dan'" , "'hubmib@ietf.org'" Date: Sun, 29 Jun 2003 19:39:05 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I would like to co-edit the EPON MIB. This will include seperate MIBs for the OLT and the ONU with associated services. I hope we can show enough interest to get this work started asap. Regards, Vincent Bemmel Alloptic http://www.alloptic.com > Dan, > >I'm interested to become a co-editor of the 802.3ah MIB. >My company specializes in Aggregated Copper EFM systems >(currently long reach - 2BaseTL). > >Regards, >-Edward Beili > Senior System Engineer > Actelis Networks > > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Friday, May 30, 2003 11:43 AM > To: Edward Beili > Cc: Ilan Reingold > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Thanks. What level of involvement can you assume? Are you > interested to be a co-editor of the future standard? Also, > what flavor of EFM do you / your company specialize in? > > If would also be VERY useful if you can provide your positive > answer to the Hub MIB e-mail list (hubmib@ietf.org). We need > visible proof of interest in the participation in order to > have this work approved by the IETF leadership. There is no > need to subscribe to the list in order to send mail (unless > you want to be subscribed). > > Regards, > > Dan > > > > -----Original Message----- > > From: Edward Beili [mailto:EdwardB@actelis.com] > > Sent: Thursday, May 29, 2003 11:29 PM > > To: Romascanu, Dan (Dan) > > Cc: Ilan Reingold > > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > > > > Hi Dan, > > > > There's definitely a need for EFM related changes in existing MIBs. > > I've asked this question in Seoul and was told that you are > > coordinating the > > work. > > I would like to be involved in it. > > > > Regards, > > -Edward Beili > > Senior System Engineer > > Actelis Networks > > > > -----Original Message----- > > From: Romascanu, Dan (Dan) > > To: hubmib@ietf.org > > Cc: stds-802-3-efm@ieee.org > > Sent: 5/29/03 6:35 PM > > Subject: [EFM] IEEE 802.3ah MIB? > > > > Our Area Directors copied me on a query that they received about > > eventual work on a IEEE 802.3af MIB. I have sent a query to > > the WG list > > last January, and I do not remember having received any > > feedback. Truth > > is that by that point in time the Management and OAM clauses > > in the EFM > > work were pretty open. This has probably changed by now and with the > > 802.3ah Draft getting closer to Sponsor Ballot, it is > probably a good > > time to ask the question again. is there interest for a > 802.3ah (EFM) > > MIB work in the IETF Ethernet Interfaces and Hub MIB > Working Group? As > > the IETF rules say, we need a visible level of interest, and > > volunteers > > to commit to do the work in order to be able to discuss > re-chartering > > the WG with the ADs. > > > > I am copying the IEEE 802.3ah list - feedback is obviously > > welcome from > > them as well. > > > > Thanks, > > > > Dan > > > > Dan Romascanu, > > > > Chair, IETF Ethernet Interfaces and Hub MIB WG > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sun Jun 29 23:27:51 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14861 for ; Sun, 29 Jun 2003 22:41:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WobG-0001cw-Bw; Sun, 29 Jun 2003 22:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WoaK-0001b8-T1 for hubmib@optimus.ietf.org; Sun, 29 Jun 2003 22:40:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14785 for ; Sun, 29 Jun 2003 22:40:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WoaH-0002Wy-00 for hubmib@ietf.org; Sun, 29 Jun 2003 22:40:01 -0400 Received: from mail.alloptic.com ([12.47.49.133] helo=srvnt506.ALLOPTIC.COM) by ietf-mx with esmtp (Exim 4.12) id 19Woa6-0002WH-00 for hubmib@ietf.org; Sun, 29 Jun 2003 22:39:50 -0400 Received: by srvnt506.ALLOPTIC.COM with Internet Mail Service (5.5.2653.19) id ; Sun, 29 Jun 2003 19:39:08 -0700 Message-ID: <885489B3B89FB6449F93E525DF78777F627036@srvnt506.ALLOPTIC.COM> From: "Bemmel, Vincent" To: "'Romascanu, Dan (Dan'" , "'hubmib@ietf.org'" Date: Sun, 29 Jun 2003 19:39:05 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I would like to co-edit the EPON MIB. This will include seperate MIBs for the OLT and the ONU with associated services. I hope we can show enough interest to get this work started asap. Regards, Vincent Bemmel Alloptic http://www.alloptic.com > Dan, > >I'm interested to become a co-editor of the 802.3ah MIB. >My company specializes in Aggregated Copper EFM systems >(currently long reach - 2BaseTL). > >Regards, >-Edward Beili > Senior System Engineer > Actelis Networks > > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Friday, May 30, 2003 11:43 AM > To: Edward Beili > Cc: Ilan Reingold > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Thanks. What level of involvement can you assume? Are you > interested to be a co-editor of the future standard? Also, > what flavor of EFM do you / your company specialize in? > > If would also be VERY useful if you can provide your positive > answer to the Hub MIB e-mail list (hubmib@ietf.org). We need > visible proof of interest in the participation in order to > have this work approved by the IETF leadership. There is no > need to subscribe to the list in order to send mail (unless > you want to be subscribed). > > Regards, > > Dan > > > > -----Original Message----- > > From: Edward Beili [mailto:EdwardB@actelis.com] > > Sent: Thursday, May 29, 2003 11:29 PM > > To: Romascanu, Dan (Dan) > > Cc: Ilan Reingold > > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > > > > Hi Dan, > > > > There's definitely a need for EFM related changes in existing MIBs. > > I've asked this question in Seoul and was told that you are > > coordinating the > > work. > > I would like to be involved in it. > > > > Regards, > > -Edward Beili > > Senior System Engineer > > Actelis Networks > > > > -----Original Message----- > > From: Romascanu, Dan (Dan) > > To: hubmib@ietf.org > > Cc: stds-802-3-efm@ieee.org > > Sent: 5/29/03 6:35 PM > > Subject: [EFM] IEEE 802.3ah MIB? > > > > Our Area Directors copied me on a query that they received about > > eventual work on a IEEE 802.3af MIB. I have sent a query to > > the WG list > > last January, and I do not remember having received any > > feedback. Truth > > is that by that point in time the Management and OAM clauses > > in the EFM > > work were pretty open. This has probably changed by now and with the > > 802.3ah Draft getting closer to Sponsor Ballot, it is > probably a good > > time to ask the question again. is there interest for a > 802.3ah (EFM) > > MIB work in the IETF Ethernet Interfaces and Hub MIB > Working Group? As > > the IETF rules say, we need a visible level of interest, and > > volunteers > > to commit to do the work in order to be able to discuss > re-chartering > > the WG with the ADs. > > > > I am copying the IEEE 802.3ah list - feedback is obviously > > welcome from > > them as well. > > > > Thanks, > > > > Dan > > > > Dan Romascanu, > > > > Chair, IETF Ethernet Interfaces and Hub MIB WG > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Jun 30 11:01:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29370 for ; Mon, 30 Jun 2003 11:01:28 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UF11A14191 for hubmib-archive@odin.ietf.org; Mon, 30 Jun 2003 11:01:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X09M-0003gg-OS; Mon, 30 Jun 2003 11:01:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X08e-0003dn-4Z for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:00:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29268 for ; Mon, 30 Jun 2003 11:00:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X08b-0001YS-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:00:13 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19X08L-0001Xv-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:58 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5UEaMA25033 for ; Mon, 30 Jun 2003 10:36:22 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5UEaLs24984 for ; Mon, 30 Jun 2003 10:36:21 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Jun 2003 17:39:34 +0300 Message-ID: Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTw From: "Romascanu, Dan (Dan)" To: "Bemmel, Vincent" , Cc: Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Up to this point we have two volunteers for participating in a possible = 802.3ah MIB work - one for copper, and one for EPON. We have also noted = the interest expressed by the Chair of the IEEE 802.3ah - Howard = Frazier. This is promising, but still, IMO, under the threshold of = interest required for starting new work in the IETF Ethernet Interfaces = and Hub MIB WG. If you and/or your sponsoring company are interested in participating in = this work and/or implementing a future standard EFM MIB (whatever flavor = of EFM) in your products - please send an e-mail to hubmib@ietf.org.=20 Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 > Dan, >=20 > I would like to co-edit the EPON MIB. This will include=20 > seperate MIBs for > the OLT and the ONU with associated services. >=20 > I hope we can show enough interest to get this work started asap. >=20 > Regards, >=20 > Vincent Bemmel > Alloptic > http://www.alloptic.com >=20 > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Jun 30 11:05:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29579 for ; Mon, 30 Jun 2003 11:05:28 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UF51i14839 for hubmib-archive@odin.ietf.org; Mon, 30 Jun 2003 11:05:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0DF-0003rB-Bm; Mon, 30 Jun 2003 11:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X08M-0003cw-Qf for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:00:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29196 for ; Mon, 30 Jun 2003 10:59:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X084-0001Xr-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:40 -0400 Received: from mailserv.hatterasnetworks.com ([63.89.58.4]) by ietf-mx with esmtp (Exim 4.12) id 19X07o-0001WR-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:24 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Jun 2003 10:58:05 -0400 Message-ID: <8052E2EA753D144EB906B7A7AA39971401152A86@mailserv.hatteras.com> Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTwAADnJbA= From: "Matt Squire" To: "Romascanu, Dan (Dan)" , "Bemmel, Vincent" , Cc: Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Dan -=20 I'm interested in helping this work go forward. Me, or someone else = from my company, will help out. - Matt > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Monday, June 30, 2003 10:40 AM > To: Bemmel, Vincent; hubmib@ietf.org > Cc: stds-802-3-efm@ieee.org > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 >=20 > Up to this point we have two volunteers for participating in=20 > a possible 802.3ah MIB work - one for copper, and one for=20 > EPON. We have also noted the interest expressed by the Chair=20 > of the IEEE 802.3ah - Howard Frazier. This is promising, but=20 > still, IMO, under the threshold of interest required for=20 > starting new work in the IETF Ethernet Interfaces and Hub MIB WG. >=20 > If you and/or your sponsoring company are interested in=20 > participating in this work and/or implementing a future=20 > standard EFM MIB (whatever flavor of EFM) in your products -=20 > please send an e-mail to hubmib@ietf.org.=20 >=20 > Thanks, >=20 > Dan >=20 > Dan Romascanu, > Chair, IETF Ethernet Interfaces and Hub MIB WG >=20 >=20 >=20 > > -----Original Message----- > > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > > Sent: 30 June, 2003 5:39 AM > > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > > Subject: RE: [EFM] IEEE 802.3ah MIB? > >=20 > >=20 > > Dan, > >=20 > > I would like to co-edit the EPON MIB. This will include=20 > > seperate MIBs for > > the OLT and the ONU with associated services. > >=20 > > I hope we can show enough interest to get this work started asap. > >=20 > > Regards, > >=20 > > Vincent Bemmel > > Alloptic > > http://www.alloptic.com > >=20 > > > Dan, > > > > > >I'm interested to become a co-editor of the 802.3ah MIB. > > >My company specializes in Aggregated Copper EFM systems > > >(currently long reach - 2BaseTL). > > > > > >Regards, > > >-Edward Beili > > > Senior System Engineer > > > Actelis Networks > > > > ... >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Jun 30 11:21:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00814 for ; Mon, 30 Jun 2003 11:21:29 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UFL1s20748 for hubmib-archive@odin.ietf.org; Mon, 30 Jun 2003 11:21:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0Sj-0005OY-GT; Mon, 30 Jun 2003 11:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0SH-0005Jb-TX for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:20:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00742 for ; Mon, 30 Jun 2003 11:20:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X0S0-0001mO-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:20:16 -0400 Received: from [65.124.125.104] (helo=exchange.appiancom.com) by ietf-mx with esmtp (Exim 4.12) id 19X0Rm-0001lr-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:20:02 -0400 Received: by EXCHANGE with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jun 2003 11:22:44 -0400 Message-ID: <4D043E1F07D3D5118E9900B0D083F9F66A1A7B@EXCHANGE> From: Yonghong Ren To: "'Romascanu, Dan (Dan)'" , "Bemmel, Vincent" , hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Date: Mon, 30 Jun 2003 11:22:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I am interesting in participating in this effort. I am implementing 802.3ah OAM in our product. The need for a MIB to control the OAM functionality seems apparent. And it would be great if we can create a standard MIB. Regards, Yonghong Ren Appian Communications -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Monday, June 30, 2003 10:40 AM To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Subject: RE: [EFM] IEEE 802.3ah MIB? Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. This is promising, but still, IMO, under the threshold of interest required for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor of EFM) in your products - please send an e-mail to hubmib@ietf.org. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Dan, > > I would like to co-edit the EPON MIB. This will include > seperate MIBs for > the OLT and the ONU with associated services. > > I hope we can show enough interest to get this work started asap. > > Regards, > > Vincent Bemmel > Alloptic > http://www.alloptic.com > > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 30 11:57:17 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29369 for ; Mon, 30 Jun 2003 11:01:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X09M-0003gg-OS; Mon, 30 Jun 2003 11:01:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X08e-0003dn-4Z for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:00:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29268 for ; Mon, 30 Jun 2003 11:00:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X08b-0001YS-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:00:13 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19X08L-0001Xv-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:58 -0400 Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5UEaMA25033 for ; Mon, 30 Jun 2003 10:36:22 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h5UEaLs24984 for ; Mon, 30 Jun 2003 10:36:21 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Jun 2003 17:39:34 +0300 Message-ID: Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTw From: "Romascanu, Dan (Dan)" To: "Bemmel, Vincent" , Cc: Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Up to this point we have two volunteers for participating in a possible = 802.3ah MIB work - one for copper, and one for EPON. We have also noted = the interest expressed by the Chair of the IEEE 802.3ah - Howard = Frazier. This is promising, but still, IMO, under the threshold of = interest required for starting new work in the IETF Ethernet Interfaces = and Hub MIB WG. If you and/or your sponsoring company are interested in participating in = this work and/or implementing a future standard EFM MIB (whatever flavor = of EFM) in your products - please send an e-mail to hubmib@ietf.org.=20 Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 > Dan, >=20 > I would like to co-edit the EPON MIB. This will include=20 > seperate MIBs for > the OLT and the ONU with associated services. >=20 > I hope we can show enough interest to get this work started asap. >=20 > Regards, >=20 > Vincent Bemmel > Alloptic > http://www.alloptic.com >=20 > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 30 12:16:49 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00813 for ; Mon, 30 Jun 2003 11:21:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0Sj-0005OY-GT; Mon, 30 Jun 2003 11:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0SH-0005Jb-TX for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:20:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00742 for ; Mon, 30 Jun 2003 11:20:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X0S0-0001mO-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:20:16 -0400 Received: from [65.124.125.104] (helo=exchange.appiancom.com) by ietf-mx with esmtp (Exim 4.12) id 19X0Rm-0001lr-00 for hubmib@ietf.org; Mon, 30 Jun 2003 11:20:02 -0400 Received: by EXCHANGE with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jun 2003 11:22:44 -0400 Message-ID: <4D043E1F07D3D5118E9900B0D083F9F66A1A7B@EXCHANGE> From: Yonghong Ren To: "'Romascanu, Dan (Dan)'" , "Bemmel, Vincent" , hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Date: Mon, 30 Jun 2003 11:22:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Dan, I am interesting in participating in this effort. I am implementing 802.3ah OAM in our product. The need for a MIB to control the OAM functionality seems apparent. And it would be great if we can create a standard MIB. Regards, Yonghong Ren Appian Communications -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Monday, June 30, 2003 10:40 AM To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Subject: RE: [EFM] IEEE 802.3ah MIB? Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. This is promising, but still, IMO, under the threshold of interest required for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor of EFM) in your products - please send an e-mail to hubmib@ietf.org. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Dan, > > I would like to co-edit the EPON MIB. This will include > seperate MIBs for > the OLT and the ONU with associated services. > > I hope we can show enough interest to get this work started asap. > > Regards, > > Vincent Bemmel > Alloptic > http://www.alloptic.com > > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 30 12:47:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29580 for ; Mon, 30 Jun 2003 11:05:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X0DF-0003rB-Bm; Mon, 30 Jun 2003 11:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X08M-0003cw-Qf for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 11:00:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29196 for ; Mon, 30 Jun 2003 10:59:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X084-0001Xr-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:40 -0400 Received: from mailserv.hatterasnetworks.com ([63.89.58.4]) by ietf-mx with esmtp (Exim 4.12) id 19X07o-0001WR-00 for hubmib@ietf.org; Mon, 30 Jun 2003 10:59:24 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Jun 2003 10:58:05 -0400 Message-ID: <8052E2EA753D144EB906B7A7AA39971401152A86@mailserv.hatteras.com> Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTwAADnJbA= From: "Matt Squire" To: "Romascanu, Dan (Dan)" , "Bemmel, Vincent" , Cc: Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Dan -=20 I'm interested in helping this work go forward. Me, or someone else = from my company, will help out. - Matt > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: Monday, June 30, 2003 10:40 AM > To: Bemmel, Vincent; hubmib@ietf.org > Cc: stds-802-3-efm@ieee.org > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 >=20 > Up to this point we have two volunteers for participating in=20 > a possible 802.3ah MIB work - one for copper, and one for=20 > EPON. We have also noted the interest expressed by the Chair=20 > of the IEEE 802.3ah - Howard Frazier. This is promising, but=20 > still, IMO, under the threshold of interest required for=20 > starting new work in the IETF Ethernet Interfaces and Hub MIB WG. >=20 > If you and/or your sponsoring company are interested in=20 > participating in this work and/or implementing a future=20 > standard EFM MIB (whatever flavor of EFM) in your products -=20 > please send an e-mail to hubmib@ietf.org.=20 >=20 > Thanks, >=20 > Dan >=20 > Dan Romascanu, > Chair, IETF Ethernet Interfaces and Hub MIB WG >=20 >=20 >=20 > > -----Original Message----- > > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > > Sent: 30 June, 2003 5:39 AM > > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > > Subject: RE: [EFM] IEEE 802.3ah MIB? > >=20 > >=20 > > Dan, > >=20 > > I would like to co-edit the EPON MIB. This will include=20 > > seperate MIBs for > > the OLT and the ONU with associated services. > >=20 > > I hope we can show enough interest to get this work started asap. > >=20 > > Regards, > >=20 > > Vincent Bemmel > > Alloptic > > http://www.alloptic.com > >=20 > > > Dan, > > > > > >I'm interested to become a co-editor of the 802.3ah MIB. > > >My company specializes in Aggregated Copper EFM systems > > >(currently long reach - 2BaseTL). > > > > > >Regards, > > >-Edward Beili > > > Senior System Engineer > > > Actelis Networks > > > > ... >=20 >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 30 13:10:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06612 for ; Mon, 30 Jun 2003 13:10:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X2AC-0004Ji-Lr; Mon, 30 Jun 2003 13:10:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1AW-0008E3-CE for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 12:06:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03151 for ; Mon, 30 Jun 2003 12:05:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X1AE-0002Ej-00 for hubmib@ietf.org; Mon, 30 Jun 2003 12:05:58 -0400 Received: from [213.70.90.131] (helo=mail.advaoptical.de) by ietf-mx with esmtp (Exim 4.12) id 19X1A1-0002E6-00 for hubmib@ietf.org; Mon, 30 Jun 2003 12:05:45 -0400 Received: from adva-mailer.advaoptical.com (unverified) by mail.advaoptical.de (Content Technologies SMTPRS 4.3.1) with ESMTP id for ; Mon, 30 Jun 2003 16:44:04 +0200 Received: by adva-mailer.advaoptical.com with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jun 2003 16:49:27 +0200 Message-ID: <33BB463469A3D411B08F00508BDD1626E18B55@ntsyork.yrk.advaoptical.com> From: John Messenger To: "'hubmib@ietf.org'" Date: Mon, 30 Jun 2003 16:49:26 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] FW: [EFM] IEEE 802.3ah 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: , Hi, we are interested in implementing a future standard EFM MIB, and are interested in reviewing drafts but not in editing. Best regards, -- John -- John Messenger (JMessenger@advaoptical.com) R&D Software Manager, ADVA Optical Networking Ltd. Tel: +44-1904 699309 Fax: +44-1904 699378 www.advaoptical.com "Mind like parachute - only work when open" (Charlie Chan) -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: 30 June 2003 15:40 To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Subject: RE: [EFM] IEEE 802.3ah MIB? Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. This is promising, but still, IMO, under the threshold of interest required for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor of EFM) in your products - please send an e-mail to hubmib@ietf.org. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Dan, > > I would like to co-edit the EPON MIB. This will include > seperate MIBs for > the OLT and the ONU with associated services. > > I hope we can show enough interest to get this work started asap. > > Regards, > > Vincent Bemmel > Alloptic > http://www.alloptic.com > > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Jun 30 13:57:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06611 for ; Mon, 30 Jun 2003 13:10:29 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UHA1k16611 for hubmib-archive@odin.ietf.org; Mon, 30 Jun 2003 13:10:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X2AC-0004Ji-Lr; Mon, 30 Jun 2003 13:10:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1AW-0008E3-CE for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 12:06:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03151 for ; Mon, 30 Jun 2003 12:05:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X1AE-0002Ej-00 for hubmib@ietf.org; Mon, 30 Jun 2003 12:05:58 -0400 Received: from [213.70.90.131] (helo=mail.advaoptical.de) by ietf-mx with esmtp (Exim 4.12) id 19X1A1-0002E6-00 for hubmib@ietf.org; Mon, 30 Jun 2003 12:05:45 -0400 Received: from adva-mailer.advaoptical.com (unverified) by mail.advaoptical.de (Content Technologies SMTPRS 4.3.1) with ESMTP id for ; Mon, 30 Jun 2003 16:44:04 +0200 Received: by adva-mailer.advaoptical.com with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jun 2003 16:49:27 +0200 Message-ID: <33BB463469A3D411B08F00508BDD1626E18B55@ntsyork.yrk.advaoptical.com> From: John Messenger To: "'hubmib@ietf.org'" Date: Mon, 30 Jun 2003 16:49:26 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Hubmib] FW: [EFM] IEEE 802.3ah 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: , Hi, we are interested in implementing a future standard EFM MIB, and are interested in reviewing drafts but not in editing. Best regards, -- John -- John Messenger (JMessenger@advaoptical.com) R&D Software Manager, ADVA Optical Networking Ltd. Tel: +44-1904 699309 Fax: +44-1904 699378 www.advaoptical.com "Mind like parachute - only work when open" (Charlie Chan) -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: 30 June 2003 15:40 To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Subject: RE: [EFM] IEEE 802.3ah MIB? Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. This is promising, but still, IMO, under the threshold of interest required for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor of EFM) in your products - please send an e-mail to hubmib@ietf.org. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? > > > Dan, > > I would like to co-edit the EPON MIB. This will include > seperate MIBs for > the OLT and the ONU with associated services. > > I hope we can show enough interest to get this work started asap. > > Regards, > > Vincent Bemmel > Alloptic > http://www.alloptic.com > > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > ... _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Jun 30 19:01:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20988 for ; Mon, 30 Jun 2003 19:01:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X7dt-00082t-Dy; Mon, 30 Jun 2003 19:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X64b-0001z5-Ip for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 17:20:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16862 for ; Mon, 30 Jun 2003 17:20:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X64Z-0004SF-00 for hubmib@ietf.org; Mon, 30 Jun 2003 17:20:27 -0400 Received: from [66.151.134.40] (helo=mawebmail01.remotepipes.net) by ietf-mx with esmtp (Exim 4.12) id 19X64O-0004SA-00 for hubmib@ietf.org; Mon, 30 Jun 2003 17:20:16 -0400 Received: from ARIELTAB (unverified [210.155.48.132]) by mawebmail01.remotepipes.net (Vircom SMTPRS 5.1.202) with ESMTP id ; Mon, 30 Jun 2003 14:20:06 -0700 Message-ID: Reply-To: From: "Ariel Maislos" To: "'Romascanu, Dan \(Dan\)'" , "'Bemmel, Vincent'" , Cc: Date: Mon, 30 Jun 2003 14:19:59 -0700 Organization: Passave Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook, Build 11.0.4920 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTwAA4/iVA= Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Dan, I'm interested in promoting this activity. Me or someone from my company will participate. Ariel Ariel Maislos Passave Inc. 1557 Jasper Dr. Sunnyvale, CA 94087 ariel.maislos@passave.com Tel: (408) 530 0458 Cel: (408) 242 8599 =20 -----Original Message----- From: owner-stds-802-3-efm@majordomo.ieee.org [mailto:owner-stds-802-3-efm@majordomo.ieee.org] On Behalf Of Romascanu, = Dan (Dan) Sent: Monday, June 30, 2003 7:40 AM To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted = the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. = This is promising, but still, IMO, under the threshold of interest required = for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor = of EFM) in your products - please send an e-mail to hubmib@ietf.org.=20 Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 > Dan, >=20 > I would like to co-edit the EPON MIB. This will include=20 > seperate MIBs for > the OLT and the ONU with associated services. >=20 > I hope we can show enough interest to get this work started asap. >=20 > Regards, >=20 > Vincent Bemmel > Alloptic > http://www.alloptic.com >=20 > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Mon Jun 30 19:48:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20987 for ; Mon, 30 Jun 2003 19:01:30 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UN11r30954 for hubmib-archive@odin.ietf.org; Mon, 30 Jun 2003 19:01:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X7dt-00082t-Dy; Mon, 30 Jun 2003 19:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X64b-0001z5-Ip for hubmib@optimus.ietf.org; Mon, 30 Jun 2003 17:20:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16862 for ; Mon, 30 Jun 2003 17:20:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X64Z-0004SF-00 for hubmib@ietf.org; Mon, 30 Jun 2003 17:20:27 -0400 Received: from [66.151.134.40] (helo=mawebmail01.remotepipes.net) by ietf-mx with esmtp (Exim 4.12) id 19X64O-0004SA-00 for hubmib@ietf.org; Mon, 30 Jun 2003 17:20:16 -0400 Received: from ARIELTAB (unverified [210.155.48.132]) by mawebmail01.remotepipes.net (Vircom SMTPRS 5.1.202) with ESMTP id ; Mon, 30 Jun 2003 14:20:06 -0700 Message-ID: Reply-To: From: "Ariel Maislos" To: "'Romascanu, Dan \(Dan\)'" , "'Bemmel, Vincent'" , Cc: Date: Mon, 30 Jun 2003 14:19:59 -0700 Organization: Passave Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook, Build 11.0.4920 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcM+sMvwjBPrv8MoTpiBjKEjsAgjAgAY3vTwAA4/iVA= Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [EFM] IEEE 802.3ah 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: , Content-Transfer-Encoding: quoted-printable Dan, I'm interested in promoting this activity. Me or someone from my company will participate. Ariel Ariel Maislos Passave Inc. 1557 Jasper Dr. Sunnyvale, CA 94087 ariel.maislos@passave.com Tel: (408) 530 0458 Cel: (408) 242 8599 =20 -----Original Message----- From: owner-stds-802-3-efm@majordomo.ieee.org [mailto:owner-stds-802-3-efm@majordomo.ieee.org] On Behalf Of Romascanu, = Dan (Dan) Sent: Monday, June 30, 2003 7:40 AM To: Bemmel, Vincent; hubmib@ietf.org Cc: stds-802-3-efm@ieee.org Up to this point we have two volunteers for participating in a possible 802.3ah MIB work - one for copper, and one for EPON. We have also noted = the interest expressed by the Chair of the IEEE 802.3ah - Howard Frazier. = This is promising, but still, IMO, under the threshold of interest required = for starting new work in the IETF Ethernet Interfaces and Hub MIB WG. If you and/or your sponsoring company are interested in participating in this work and/or implementing a future standard EFM MIB (whatever flavor = of EFM) in your products - please send an e-mail to hubmib@ietf.org.=20 Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG > -----Original Message----- > From: Bemmel, Vincent [mailto:vincent.bemmel@Alloptic.com] > Sent: 30 June, 2003 5:39 AM > To: Romascanu, Dan (Dan); 'hubmib@ietf.org' > Subject: RE: [EFM] IEEE 802.3ah MIB? >=20 >=20 > Dan, >=20 > I would like to co-edit the EPON MIB. This will include=20 > seperate MIBs for > the OLT and the ONU with associated services. >=20 > I hope we can show enough interest to get this work started asap. >=20 > Regards, >=20 > Vincent Bemmel > Alloptic > http://www.alloptic.com >=20 > > Dan, > > > >I'm interested to become a co-editor of the 802.3ah MIB. > >My company specializes in Aggregated Copper EFM systems > >(currently long reach - 2BaseTL). > > > >Regards, > >-Edward Beili > > Senior System Engineer > > Actelis Networks > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib