From hubmib-admin@ietf.org Mon Sep 3 09:19:56 2001 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 JAA09266 for ; Mon, 3 Sep 2001 09:19:56 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20036; Mon, 3 Sep 2001 09:19:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20007 for ; Mon, 3 Sep 2001 09:19:20 -0400 (EDT) Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09231 for ; Mon, 3 Sep 2001 09:17:54 -0400 (EDT) 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 JAA22355 for ; Mon, 3 Sep 2001 09:18:17 -0400 (EDT) Received: from itc-eml1.lannet.com (h149-49-38-51.avaya.com [149.49.38.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id JAA22349 for ; Mon, 3 Sep 2001 09:18:16 -0400 (EDT) Received: by ITC-EML1 with Internet Mail Service (5.5.2650.21) id ; Mon, 3 Sep 2001 16:15:48 +0200 Message-ID: <18609D34D984D31183780090279CF7E004980897@ITC-EML1> From: Dan Romascanu To: hubmib@ietf.org Cc: mrm@riverstonenet.com Date: Mon, 3 Sep 2001 16:15:42 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13482.EA1BAE40" Subject: [Hubmib] FW: [Bridge-mib] RFC 1473 dot1dStpPortEnable is not well specifie d Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C13482.EA1BAE40 Content-Type: text/plain; charset="iso-8859-8" As the suggested remedy asks for clarifications in RFC 2665 update, I am forwarding this to the hubmib list. If somebody misses the rest of the thread, it can be found in the bridge mib list archives. Regards, Dan -----Original Message----- From: Michael MacFaden [mailto:mrm@riverstonenet.com] Sent: Friday, August 31, 2001 8:18 PM To: bridge-mib@ietf.org Subject: RE: [Bridge-mib] RFC 1473 dot1dStpPortEnable is not well specifie d At 12:29 PM 8/31/2001 -0500, you wrote: >I agree. However, I don't think we can standardize what the >marketplace has implemented when their implementations are so far apart. I don't think from the data I collected they were "far apart" actually. Can you elaborate? Three of the four brouters allow for STP to be turned off. The behavior for what happens when STP is turned of is the same for all three. dot1dStpPortEnable should be clarified as to what the relationship with ifAdminStatus is in various configurations. Port Membership in dot1dBasePortTable also needs to be clarified. The ifAdminStatus behavior could easily be resolved. There really is *one* right answer for turning ifAdminStatus to down(2) for an ifType of 6. Updates to RFC 2665 should clarify that behavior. Mike MacFaden _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib ------_=_NextPart_001_01C13482.EA1BAE40 Content-Type: text/html; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable FW: [Bridge-mib] RFC 1473 dot1dStpPortEnable is not well = specifie d

As the suggested remedy asks for clarifications in = RFC 2665 update, I am forwarding this to the hubmib list. If somebody = misses the rest of the thread, it can be found in the bridge mib list = archives.

Regards,

Dan


-----Original Message-----
From: Michael MacFaden [mailto:mrm@riverstonenet.com]<= /FONT>
Sent: Friday, August 31, 2001 8:18 PM
To: bridge-mib@ietf.org
Subject: RE: [Bridge-mib] RFC 1473 = dot1dStpPortEnable is not well specifie d


At 12:29 PM 8/31/2001 -0500, you wrote:
>I agree.  However, I don't think we can = standardize what the
>marketplace has implemented when their = implementations are so far apart.

I don't think from the data I collected they were = "far apart" actually.
Can you elaborate?

Three of the four brouters allow for STP to be turned = off. The behavior
for what happens when STP is turned of is the same = for all three.
dot1dStpPortEnable should be clarified as to what = the relationship
with ifAdminStatus is in various = configurations.
Port Membership in dot1dBasePortTable also needs to = be clarified.

The ifAdminStatus behavior could easily be resolved. = There really is *one* right
answer for turning ifAdminStatus to down(2) for an = ifType of 6.
Updates to RFC 2665 should clarify that = behavior.

Mike MacFaden


_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib<= /FONT>

------_=_NextPart_001_01C13482.EA1BAE40-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Sep 3 09:26:35 2001 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 JAA09440 for ; Mon, 3 Sep 2001 09:26:34 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20365; Mon, 3 Sep 2001 09:27:42 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20337 for ; Mon, 3 Sep 2001 09:27:41 -0400 (EDT) Received: from gnat.inet.org (inet.org [63.108.254.91] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09436 for ; Mon, 3 Sep 2001 09:26:14 -0400 (EDT) Received: from mosquito.inet.org (mosquito [10.30.20.240]) by gnat.inet.org (Postfix) with ESMTP id 817158266E; Mon, 3 Sep 2001 09:27:08 -0400 (EDT) Message-Id: <5.1.0.14.2.20010903091926.00a2c590@10.30.15.2> X-Sender: rja@10.30.15.2 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 03 Sep 2001 09:21:20 -0400 To: Dan Romascanu From: RJ Atkinson Subject: Re: [Hubmib] FW: [Bridge-mib] RFC 1473 dot1dStpPortEnable is not well specifie d Cc: hubmib@ietf.org, mrm@riverstonenet.com In-Reply-To: <18609D34D984D31183780090279CF7E004980897@ITC-EML1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Could we please all post in MIME text/plain format (i.e. not proprietary Microsoft RichText, not MIME RichText, not HTML) so that all subscribers can read all the email on the list ? For folks using Outlook, this means you need to explicitly select plain text in your global settings or on a per-message basis. By default, Outlook emits gorp, not text/plain. It IS feasible to alter this setting in Outlook, according to Microsoft. As I don't have or use Outlook, please do not ask me for detailed instructions. Thanks, Ran _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Sep 17 19:23:29 2001 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 TAA24786 for ; Mon, 17 Sep 2001 19:23:29 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20276; Mon, 17 Sep 2001 19:22:44 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20065 for ; Mon, 17 Sep 2001 19:15:11 -0400 (EDT) Received: from murphys-outbound.services.quay.plus.net ([212.159.14.225]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23719 for ; Mon, 17 Sep 2001 19:15:11 -0400 (EDT) Received: (qmail 20866 invoked from network); 17 Sep 2001 23:13:49 -0000 Received: from unknown (HELO NEXUS.replicants.org.uk) (212.56.122.201) by murphys with SMTP; 17 Sep 2001 23:13:49 -0000 Received: from mail pickup service by NEXUS.replicants.org.uk with Microsoft SMTPSVC; Tue, 18 Sep 2001 00:13:49 +0100 X-From_: ietf-123-owner@loki.ietf.org Tue Jun 26 16:25:13 2001 Envelope-to: david@REPLICANTS.FREESERVE.CO.UK Delivery-date: Tue, 26 Jun 2001 16:25:13 +0100 Received: from [132.151.1.177] (helo=loki.ietf.org) by imailg2.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 15EuiG-0001WG-00; Tue, 26 Jun 2001 16:25:13 +0100 Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id KAA20024 for ietf-123-outbound.10@ietf.org; Tue, 26 Jun 2001 10:15:01 -0400 (EDT) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA18645 for ; Tue, 26 Jun 2001 07:03:22 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27441; Tue, 26 Jun 2001 07:03:21 -0400 (EDT) Message-Id: <200106261103.HAA27441@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, 26 Jun 2001 07:03:21 -0400 X-OriginalArrivalTime: 17 Sep 2001 23:13:49.0699 (UTC) FILETIME=[68CA5D30:01C13FCE] Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-00.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org --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 (DTE Power via MDI) MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-00.txt Pages : 24 Date : 25-Jun-01 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 [RFC2665] with a set of objects for managing a power Ethernet Powered Device (PD) and/or Power Source Equipment (PSE). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-00.txt 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-00.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-00.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: <20010625113314.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" C --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib