From daemon@optimus.ietf.org  Tue Feb 19 07:00:51 2002
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 HAA14773
	for <bridge-archive@odin.ietf.org>; Tue, 19 Feb 2002 07:00:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA00673
	for bridge-archive@odin.ietf.org; Tue, 19 Feb 2002 07:00:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00631;
	Tue, 19 Feb 2002 07:00:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00600
	for <bridge-mib@optimus.ietf.org>; Tue, 19 Feb 2002 07:00:45 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14754;
	Tue, 19 Feb 2002 07:00:44 -0500 (EST)
Message-Id: <200202191200.HAA14754@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: bridge-mib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 19 Feb 2002 07:00:44 -0500
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-02.txt
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bridge MIB Working Group of the IETF.

	Title		: Definitions of Managed Objects for Bridges
	Author(s)	: k. Norseth et al.
	Filename	: draft-ietf-bridge-bridgemib-smiv2-02.txt
	Pages		: 36
	Date		: 18-Feb-02
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-02.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-bridge-bridgemib-smiv2-02.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-bridge-bridgemib-smiv2-02.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:	<20020218134000.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-bridge-bridgemib-smiv2-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020218134000.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Tue Feb 19 16:04:13 2002
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 QAA05528
	for <bridge-archive@odin.ietf.org>; Tue, 19 Feb 2002 16:04:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA03109
	for bridge-archive@odin.ietf.org; Tue, 19 Feb 2002 16:04:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA03098;
	Tue, 19 Feb 2002 16:04:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA03063
	for <bridge-mib@optimus.ietf.org>; Tue, 19 Feb 2002 16:04:05 -0500 (EST)
Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05520
	for <bridge-mib@ietf.org>; Tue, 19 Feb 2002 16:04:02 -0500 (EST)
Received: from agile.yagosys.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id NAA25912; Tue, 19 Feb 2002 13:03:29 -0800 (PST)
Received: from agile.yagosys.com (agile.yagosys.com [127.0.0.1])
	by agile.yagosys.com (8.12.0/8.12.0) with ESMTP id g1JL3TJC001433
	for <bridge-mib@ietf.org>; Tue, 19 Feb 2002 13:03:29 -0800
Received: (from mrm@localhost)
	by agile.yagosys.com (8.12.0/8.12.0/Submit) id g1JL3TEq001432
	for bridge-mib@ietf.org; Tue, 19 Feb 2002 13:03:29 -0800
Date: Tue, 19 Feb 2002 13:03:29 -0800
From: Michael MacFaden <mrm@riverstonenet.com>
To: bridge-mib@ietf.org
Message-ID: <20020219130329.G1223@riverstonenet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Operating-System: GNU/Linux 2.4.17
Subject: [Bridge-mib] References in bridge mib module out of date
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org

The draft-ietf-bridge-bridgemib-smiv2-02.txt
still references the 1990 IEEE 802.1D-1990 document.

Will the references in this document
be brought up to date to reflect the current
sections in a newer IEEE 802.1D spec?

Please?  

It will make it much easier to implement.
Also last I looked, one can no longer download
the 1990 spec, but the 1998 is freely available.

Mike


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



From daemon@optimus.ietf.org  Tue Feb 19 22:28:26 2002
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 WAA12144
	for <bridge-archive@odin.ietf.org>; Tue, 19 Feb 2002 22:28:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA18648
	for bridge-archive@odin.ietf.org; Tue, 19 Feb 2002 22:28:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA18632;
	Tue, 19 Feb 2002 22:28:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA18604
	for <bridge-mib@optimus.ietf.org>; Tue, 19 Feb 2002 22:28:10 -0500 (EST)
Received: from c001.snv.cp.net (c001-h001.c001.snv.cp.net [209.228.32.115])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12139
	for <bridge-mib@ietf.org>; Tue, 19 Feb 2002 22:28:07 -0500 (EST)
Received: (cpmta 4132 invoked from network); 19 Feb 2002 19:27:38 -0800
Received: from 24.221.253.53 (HELO slc252750)
  by smtp.register-admin.com (209.228.32.115) with SMTP; 19 Feb 2002 19:27:38 -0800
X-Sent: 20 Feb 2002 03:27:38 GMT
Message-ID: <00ac01c1b9be$f13e47c0$850f880a@slc252750>
Reply-To: "K.C. Norseth" <kcn@norseth.com>
From: "K.C. Norseth" <kcn@norseth.com>
To: "Michael MacFaden" <mrm@riverstonenet.com>, <bridge-mib@ietf.org>
References: <20020219130329.G1223@riverstonenet.com>
Subject: Re: [Bridge-mib] References in bridge mib module out of date
Date: Tue, 19 Feb 2002 20:30:25 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org
Content-Transfer-Encoding: 7bit

Hi Mike,

Thanks for catching this.  I am getting clarification on how to handle this.
We do need to update the reference.

K.C.

----- Original Message -----
From: Michael MacFaden <mrm@riverstonenet.com>
To: <bridge-mib@ietf.org>
Sent: Tuesday, February 19, 2002 2:03 PM
Subject: [Bridge-mib] References in bridge mib module out of date


| The draft-ietf-bridge-bridgemib-smiv2-02.txt
| still references the 1990 IEEE 802.1D-1990 document.
|
| Will the references in this document
| be brought up to date to reflect the current
| sections in a newer IEEE 802.1D spec?
|
| Please?
|
| It will make it much easier to implement.
| Also last I looked, one can no longer download
| the 1990 spec, but the 1998 is freely available.
|
| Mike
|
|
| _______________________________________________
| Bridge-mib mailing list
| Bridge-mib@ietf.org
| https://www1.ietf.org/mailman/listinfo/bridge-mib
|


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



From daemon@optimus.ietf.org  Wed Feb 20 01:44:22 2002
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 BAA15922
	for <bridge-archive@odin.ietf.org>; Wed, 20 Feb 2002 01:44:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA04974
	for bridge-archive@odin.ietf.org; Wed, 20 Feb 2002 01:44:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04960;
	Wed, 20 Feb 2002 01:44:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04929
	for <bridge-mib@optimus.ietf.org>; Wed, 20 Feb 2002 01:44:13 -0500 (EST)
Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15918
	for <bridge-mib@ietf.org>; Wed, 20 Feb 2002 01:44:11 -0500 (EST)
Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-44418U200L2S100) with SMTP id AAA459;
          Wed, 20 Feb 2002 08:47:18 +0200
Reply-To: <Arozin@Opticalaccess.com>
From: alexr@nbase.co.il (Alex Ruzin)
To: "'K.C. Norseth'" <kcn@norseth.com>,
        "'Michael MacFaden'" <mrm@riverstonenet.com>, <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-02.txt
Date: Wed, 20 Feb 2002 08:46:02 +0200
Message-ID: <01ad01c1b9da$4399b340$87885ac2@Alexr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <00ac01c1b9be$f13e47c0$850f880a@slc252750>
Content-Transfer-Encoding: 7bit
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

I expected to see here the objects
dot1dStpAdminPortPathCost32 and dot1dStpOperPortPathCost32
instead of a single dot1dStpPortPathCost32.
What about it ?

Best regards, Alex
---------------------
Open Source RSTP http://rstplib.sourceforge.net/
Optical Access Ltd. http://www.opticalaccess.com
 

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



From daemon@optimus.ietf.org  Tue Feb 26 12:26:10 2002
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 MAA11610
	for <bridge-archive@odin.ietf.org>; Tue, 26 Feb 2002 12:26:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA27194
	for bridge-archive@odin.ietf.org; Tue, 26 Feb 2002 12:26:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27176;
	Tue, 26 Feb 2002 12:26:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27142
	for <bridge-mib@optimus.ietf.org>; Tue, 26 Feb 2002 12:26:08 -0500 (EST)
Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11595
	for <bridge-mib@ietf.org>; Tue, 26 Feb 2002 12:26:02 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50])
	by columba.www.eur.3com.com  with ESMTP id g1QHRqx17329;
	Tue, 26 Feb 2002 17:27:52 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206])
	by toucana.eur.3com.com  with SMTP id g1QHPs110961;
	Tue, 26 Feb 2002 17:25:58 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256B6C.005FD3CA ; Tue, 26 Feb 2002 17:26:41 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: "Hema Magesh" <hema.ramani@wipro.com>
cc: stds-802-1@ieee.org, bridge-mib@ietf.org
Message-ID: <80256B6C.005FD2CD.00@notesmta.eur.3com.com>
Date: Tue, 26 Feb 2002 17:21:23 +0000
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Bridge-mib] Re: Doubt Regarding Learning Constraints.
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org



Hema,

This should be discussed on the IETF Bridge-MIB mailing list,
bridge-mib@ietf.org.

Response in-line.

Les...

On 26 Feb 2002, "Hema Magesh" <hema.ramani@wipro.com> wrote:

> Hi,
>
>       I have a query regarding the VLAN Learning Constraint.
>
>       In an hybrid bridge (Both IVL and SVL capable).
>       Learning Constraints are set by Management and the values are present in
the Learning Constraint table.
>
>       The RFC - 2674 , speaks about a default Constraint Type and Set the
extract is present below.
>       (http://www.ietf.org/rfc/rfc2674.txt)
>
>       My understanding is, We can have a default Constraint type - this can be
either "Shared or Independent" ,
>       for every VLAN which does not have any Constraint associated with it.
>
>       If the Constraint Type is independent then all Vlan's filtering entries
are given unique FID's.

Yes.

>       If its default constraint type is "Shared".Then all Vlan's filtering
entries are given the same FID's.

Yes.

>       If this understanding is correct. Then I have the following doubts.
>
>   1#. If the ConstraintSetDefault = F1 (which I believe is the FID ).
>       and the ConstraintType Default = "Shared" .

The Constraint Set identified by this value is mapped to a FID by a proprietary
mechanism internal to the Bridge doing the mapping.  The FID allocated by the
Bridge is shown in dot1qVlanFdbId.

>       Hence all VLAN's which has no constraints would be associated with this
FID.
>       Now if via management, if a fixed allocation is done with the same FID
F1(the default one)
>       with a VLAN which has constraints in the learning Constraint table.
>       Should we take a stand that the default FID cannot be set for VLAN's for
which constraints' exist?.

There is no restriction preventing an entry in dot1qLearningConstraintsTable
from assigning a VLAN to the default constraint set.  Such an entry is
unnecessary, but it is not wrong.

>       Similarly if the default FID is changing dynamically then again if a
FIXED allocation is already associated with this FID
>       Can we give an error asking to request for some other default FID?.

I think what you are asking is: "Can you change the dot1qConstraintSetDefault
to use the same set as an existing entry in dot1qLearningConstraintsTable?"

Again, there is no restriction preventing this.

If your implementation does not allow the default constraint set to share one of
the sets configured in the table, then you may reject the requested change with
an "inconsistent value" error.

>   2#. Having the same initial conditions now if one of the VLAN which has the
default FID F1 associated
>         has a Learning Constraint set then it should no more be associated
with the default FID .
>
>       But again if the constraints are deleted then we need to associate the
VLAN's for which no more VLAN Constraints
>       are present to the default FID?.

Again, if your implementation does not allow you to configure an entry in the
table which identifies the same constraint set as the default constraint set,
then you may reject the requested change with an "inconsistent value" error.

>       In the standard 802.1Q-1998 does not mention about default constraints.
>       So Is this some additional features which are present in the RFC or
>       the standard has some details which needs to be interpreted in this
way?.

802.1Q does not specify how to deal with VLANs learnt through GVRP, or manually
configured, for which no learning constraints have been defined.  This was added
to the RFC to allow the behaviour to be defined.

>   Regards
>   Hema
>
>
>
>
>   RFC -2674 extract:
>
>   dot1qConstraintSetDefault OBJECT-TYPE
>       SYNTAX      INTEGER (0..65535)
>       MAX-ACCESS  read-write
>       STATUS      current
>       DESCRIPTION
>           "The identity of the constraint set to which a VLAN
>           belongs, if there is not an explicit entry for that VLAN
>           in dot1qLearningConstraintsTable."
>       ::= { dot1qVlan 9 }
>
>   dot1qConstraintTypeDefault OBJECT-TYPE
>       SYNTAX      INTEGER {
>                       independent(1),
>                       shared(2)
>                   }
>       MAX-ACCESS  read-write
>       STATUS      current
>       DESCRIPTION
>           "The type of constraint set to which a VLAN belongs, if
>           there is not an explicit entry for that VLAN in
>           dot1qLearningConstraintsTable.  The types are as defined
>           for dot1qConstraintType."
>       ::= { dot1qVlan 10 }



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



From daemon@ns.ietf.org  Thu Feb 28 03:01:32 2002
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 DAA14072
	for <bridge-archive@odin.ietf.org>; Thu, 28 Feb 2002 03:01:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA11507
	for bridge-archive@odin.ietf.org; Thu, 28 Feb 2002 03:01:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11473;
	Thu, 28 Feb 2002 03:01:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11410
	for <bridge-mib@ns.ietf.org>; Thu, 28 Feb 2002 03:01:11 -0500 (EST)
Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14062
	for <bridge-mib@ietf.org>; Thu, 28 Feb 2002 03:01:07 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50])
	by columba.www.eur.3com.com  with ESMTP id g1S82ox29810;
	Thu, 28 Feb 2002 08:02:50 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206])
	by toucana.eur.3com.com  with SMTP id g1S80tc01492;
	Thu, 28 Feb 2002 08:00:55 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256B6E.002C1B1C ; Thu, 28 Feb 2002 08:01:45 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: Arozin@Opticalaccess.com
cc: "'K.C. Norseth'" <kcn@norseth.com>,
        "'Michael MacFaden'" <mrm@riverstonenet.com>, bridge-mib@ietf.org
Message-ID: <80256B6E.002C198D.00@notesmta.eur.3com.com>
Date: Thu, 28 Feb 2002 07:56:22 +0000
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-02
	.txt
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org



Alex,

Can you explain why we need an Admin and Operational version of PathCost,
please?

Under what circumstances could these values differ?

Les...





alexr@nbase.co.il (Alex Ruzin)@ietf.org on 20/02/2002 06:46:02

Please respond to <Arozin@Opticalaccess.com>

Sent by:  bridge-mib-admin@ietf.org


To:   "'K.C. Norseth'" <kcn@norseth.com>, "'Michael MacFaden'"
      <mrm@riverstonenet.com>, <bridge-mib@ietf.org>
cc:
Subject:  RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-02.txt


Hi,

I expected to see here the objects
dot1dStpAdminPortPathCost32 and dot1dStpOperPortPathCost32
instead of a single dot1dStpPortPathCost32.
What about it ?

Best regards, Alex
---------------------
Open Source RSTP http://rstplib.sourceforge.net/
Optical Access Ltd. http://www.opticalaccess.com


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





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



From daemon@ns.ietf.org  Thu Feb 28 03:27:12 2002
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 DAA14428
	for <bridge-archive@odin.ietf.org>; Thu, 28 Feb 2002 03:27:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA12688
	for bridge-archive@odin.ietf.org; Thu, 28 Feb 2002 03:27:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA12680;
	Thu, 28 Feb 2002 03:27:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA12643
	for <bridge-mib@ns.ietf.org>; Thu, 28 Feb 2002 03:27:06 -0500 (EST)
Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14423
	for <bridge-mib@ietf.org>; Thu, 28 Feb 2002 03:27:02 -0500 (EST)
Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-44418U200L2S100) with SMTP id AAA483;
          Thu, 28 Feb 2002 10:30:01 +0200
Reply-To: <Arozin@Opticalaccess.com>
From: alexr@nbase.co.il (Alex Ruzin)
To: "'Les Bell'" <Les_Bell@eur.3com.com>
Cc: "'K.C. Norseth'" <kcn@norseth.com>,
        "'Michael MacFaden'" <mrm@riverstonenet.com>, <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-02.txt
Date: Thu, 28 Feb 2002 10:28:41 +0200
Message-ID: <009601c1c031$eeac6310$87885ac2@Alexr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <80256B6E.002C198D.00@notesmta.eur.3com.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <bridge-mib.ietf.org>
X-BeenThere: bridge-mib@ietf.org
Content-Transfer-Encoding: 7bit

On Thursday, February 28, 2002 9:56 AM Les Bell asked
Les> Alex> I expected to see here the objects
Les> Alex> dot1dStpAdminPortPathCost32 and dot1dStpOperPortPathCost32
Les> Alex> instead of a single dot1dStpPortPathCost32.
Les> Alex> What about it ?
Les> Alex,
Les> Can you explain why we need an Admin and Operational version 
Les> of PathCost, please?
Les> Under what circumstances could these values differ?
Les> Les...

Les,
We would like to define "auto selection" for PortPathCost.
I mean, for example, if dot1dStpAdminPortPathCost32 is set to "0",
the agent could select dot1dStpOperPortPathCost32 automatically,
corresponding to table 17-7 in 17.28.2 of 802.1s.
When dot1dStpAdminPortPathCost32 is set to positive value, agent could
use this value for dot1dStpOperPortPathCost32.
I don't see any other solution to force the agent to use table 17.7.
May be I missed something?

Thank you for your interest in my remarks, Alex


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



