From mailman-bounces@ietf.org  Sat Jan  1 05:59:50 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09010
	for <bridge-mib-archive@ietf.org>; Sat, 1 Jan 2005 05:59:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkhAt-00078t-On
	for bridge-mib-archive@ietf.org; Sat, 01 Jan 2005 06:11:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgFR-0007TC-EJ
	for bridge-mib-archive@ietf.org; Sat, 01 Jan 2005 05:12:37 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: bridge-mib-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.9094.1104573803.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:03:23 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

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, mailman-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:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for bridge-mib-archive@ietf.org:

List                                     Password // URL
----                                     --------  
bridge-mib@ietf.org                      zopaeb    
https://www1.ietf.org/mailman/options/bridge-mib/bridge-mib-archive%40ietf.org


From bridge-mib-bounces@ietf.org  Mon Jan  3 07:46:46 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24015;
	Mon, 3 Jan 2005 07:46:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClRnt-000316-03; Mon, 03 Jan 2005 07:59:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClRXi-0002wU-3Y; Mon, 03 Jan 2005 07:42:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClRRY-0000dK-N7
	for bridge-mib@megatron.ietf.org; Mon, 03 Jan 2005 07:36:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23505
	for <bridge-mib@ietf.org>; Mon, 3 Jan 2005 07:36:15 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClRdi-0002pA-AQ
	for bridge-mib@ietf.org; Mon, 03 Jan 2005 07:48:50 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j03CaD4O025507
	for <bridge-mib@ietf.org>; Mon, 3 Jan 2005 06:36:14 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP4MRWR>; Mon, 3 Jan 2005 13:36:12 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550604F2B2@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "C. M. Heard" <heard@pobox.com>, bridge-mib@ietf.org
Subject: RE: [Bridge-mib] Review comments on draft-ietf-bridge-bridgemib-s
	miv2-07.txt
Date: Mon, 3 Jan 2005 13:36:03 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be



> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org]On
> Behalf Of C. M. Heard
> Sent: Friday, December 31, 2004 19:49
> To: bridge-mib@ietf.org
> Subject: RE: [Bridge-mib] Review comments on
> draft-ietf-bridge-bridgemib-smiv2-07.txt
> 
> 
> On Thu, 30 Dec 2004, David B Harrington wrote:
> > For the SMI experts amongst us, can we legally register the
> > MODULE-IDENTITY in the following way?
> > 
> > dot1dBridge MODULE-IDENTITY
> > 	...
> > 	::= { mib-2 17 }
> > 
> > RFC1493 registered dot1dbridge using "dot1dbridge OBJECT IDENTIFIER

I think Dave meant "dot1dBridge"  (i.e. capital B) in the above

> > ::= { mib-2 17 }"
> > Juergen pointed out that the SMIv2-to-SMIv1 translation of a
> > MODULE-IDENTITY is simply an OID, so this might be legal.
> 

Seems fine to me too.

Bert
> This is legal.  The effect is to associate a registration, as well as
> an OID value, with the descriptor dot1dBridge, but the semantics
> remain unchanged, and any MIB module that imports the descriptor will
> continue to compile, and all subordinate OIDs will resolve to the same
> value as before.  Note that RFC 2578 Section 3.6 explicitly allows the
> same descriptor to be associated with a registration and an 
> assignment:
> 
>    A descriptor is allowed to be associated with both a registration and
>    an assignment, providing both are associated with the same OBJECT
>    IDENTIFIER value and semantics.
> 
> For some precedents, the following definition in RFC 1406
> 
>    ds1 OBJECT IDENTIFIER ::= { transmission 18 }
> 
> has been translated to
> 
>    ds1 MODULE-IDENTITY
>    ...
>    ::= { transmission 18 }
> 
> in RFCs 2495 and 3895 and the following definition in RFC 1407
> 
>    ds3  OBJECT IDENTIFIER ::= { transmission 30 }
> 
> has been translated to
> 
>    ds3 MODULE-IDENTITY
>    ...
>    ::= { transmission 30 }
> 
> in RFCs 2496 and 3896.
> 
> > If we can do this, it would move the mib up under mib-2, 
> and eliminate
> > the forward reference (issue #757). 
> > It would also place the object and notification subtrees under the
> > dot1dBridge MODULE-IDENTITY, approximating the recommended practices
> > from draft-ietf-ops-mib-review-guidelines Suggested OID layout. 
> 
> All of these sound to me like Good Things.
> 
> Mike Heard
> 
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Wed Jan  5 13:30:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28303;
	Wed, 5 Jan 2005 13:30:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmG82-0000Dw-SB; Wed, 05 Jan 2005 13:43:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmFt3-0007Pt-0d; Wed, 05 Jan 2005 13:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmFpB-0006AF-VC
	for bridge-mib@megatron.ietf.org; Wed, 05 Jan 2005 13:24:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27885
	for <bridge-mib@ietf.org>; Wed, 5 Jan 2005 13:23:58 -0500 (EST)
Message-Id: <200501051823.NAA27885@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmG1e-000888-72
	for bridge-mib@ietf.org; Wed, 05 Jan 2005 13:37:04 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc13) with SMTP
	id <2005010518230301500c7ugqe>; Wed, 5 Jan 2005 18:23:03 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <bridge-mib@ietf.org>
Date: Wed, 5 Jan 2005 13:22:58 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
thread-index: AcTzU5U3SVk/m0qvSLW5IYyCXRRTMA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Subject: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit

Hi,

I have reviewed the -08- revision to see which WG Last Call issues
were resolved. Here is a summary of the issues and their resolution.
These issues have been discussed on the mailing list, and I believe
the changes reflect consensus.
If nobody raises a serious objection to any change, I will close these
issues. 
We have only one issue remaining from the WG Last Call.

-----------------------
EDITORIAL ISSUES

#758: smiv2-07: Is the BridgeId description still correct? it is not
clear that the definition is wrong. The question has been posed
publicly and nobody, including the co-chair of 802.1, responded that
it was in fact wrong. I would only like to see corrected text
submitted if this is in fact WRONG. Issue closed.

#759: rstpMIB registration. This issue is purely editorial, and the
presence or non-presence of the comment in this document is
immaterial. Editor's choice. Issue closed.

#761 portPathCost32 description - The inaccuracy is editorial, and
immaterial to the functionality of the object. No improved text has
been provided. Issue closed. 

#762: smiv2-07: unit of dot1dTpPortMaxInfo; done. Issue closed

#764 add original authors in contact information. Publicly requested
updated addresses. Done where the info was available. I suggest we
simply submit with the **missing data here** comment in -08-; this way
the author is still credited, and we do not provide inaccurate contact
info for those persons. Purely editorial. Issue closed.  

Other editorial changes:
1) "group" was changed to "subtree" througout.

-----------------------
TECHNICAL ISSUES

#757 forward reference in MODULE-IDENTITY: two proposals; either
works; editor's choice. Issue closed.

#669: smiv2-07: compliance requirements for 32-bit pathcost; and
#760 smiv2-07 changing bridgeCompliance and bridgeCompliance2: 
The description in PathCost was changed in a way that maintains
compliance for existing implementations, and tweaks the semantics of
the value 65535 for those implementations that also support
PathCost32. It almost looks legal. Precedence for this approach is
found in IF-MIB. The bridgeCompliance was renamed to
bridgeCompliance1493 and made current, and a new compiance was added
for implementations that support PathCost32. Issues closed.

-----------------------
UNRESOLVED ISSUES:

#543: smiv2-06: semantic changes; the following objects changed
semantics of an existing object: dot1dPortPriority,
dot1dStpTimeSinceTopologyChange, and dot1dStaticAllowedToGoTo. These
objects were modified to support 802.1t semantics. Since 802.1t
implementations have been fielded before this mib becomes available,
the behavior of current agent implementations might be non-compliant
with the updated definitions. Even an implementation that claims
compliance to bridgeCompliance1493 will be impacted because the
semantics of objects from RFC 1493 have been changed. 


David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 



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


From bridge-mib-bounces@ietf.org  Thu Jan  6 11:04:07 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18729;
	Thu, 6 Jan 2005 11:04:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmaKB-0000Lz-9U; Thu, 06 Jan 2005 11:17:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cma0A-00011z-CU; Thu, 06 Jan 2005 10:56:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmZwe-0008Jl-Dv
	for bridge-mib@megatron.ietf.org; Thu, 06 Jan 2005 10:53:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17663
	for <bridge-mib@ietf.org>; Thu, 6 Jan 2005 10:53:02 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cma9R-0001pN-FA
	for bridge-mib@ietf.org; Thu, 06 Jan 2005 11:06:18 -0500
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j06FqKW25767; Thu, 6 Jan 2005 10:52:20 -0500 (EST)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WKMBF8RZ>; Thu, 6 Jan 2005 07:52:20 -0800
Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BD0BA@zsc3c026.us.nortel.com>
From: "David Levi" <dlevi@nortelnetworks.com>
To: "'John Flick'" <john.flick@hp.com>
Subject: RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
Date: Thu, 6 Jan 2005 07:52:19 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0870727311=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168

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.

--===============0870727311==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F407.B39E26F2"

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_01C4F407.B39E26F2
Content-Type: text/plain

John,

>> 2. References to RFC 1493 should refer to the updated version
>>     in draft-ietf-bridge-bridgemib-smiv2-07.txt.
>> DBL> I don't think it makes sense to change this, since these 
>> DBL> references will just need to be updated to the new RFC number for 
>> DBL> draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published as 
>> DBL> an RFC.
>
>Making this change would help the RFC editor find the places that need to
be updated to refer
>to the new RFC when published, as well as alerting the RFC editor to the
dependency between
>these two drafts in case one gets approved by the IESG before the other.

I still don't like the idea of changing references to an RFC into references
to an ID.
How about if we just change 1493 to XXXX throughout the doc, and add a note
to the
RFC editor somewhere that these XXXX's need to be changed to the appropriate
RFC #
after the -smiv2- draft is published as an RFC?

-Dave

------_=_NextPart_001_01C4F407.B39E26F2
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>John,</FONT>
</P>

<P><FONT SIZE=2>&gt;&gt; 2. References to RFC 1493 should refer to the updated version</FONT>
<BR><FONT SIZE=2>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; in draft-ietf-bridge-bridgemib-smiv2-07.txt.</FONT>
<BR><FONT SIZE=2>&gt;&gt; DBL&gt; I don't think it makes sense to change this, since these </FONT>
<BR><FONT SIZE=2>&gt;&gt; DBL&gt; references will just need to be updated to the new RFC number for </FONT>
<BR><FONT SIZE=2>&gt;&gt; DBL&gt; draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published as </FONT>
<BR><FONT SIZE=2>&gt;&gt; DBL&gt; an RFC.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;Making this change would help the RFC editor find the places that need to be updated to refer</FONT>
<BR><FONT SIZE=2>&gt;to the new RFC when published, as well as alerting the RFC editor to the dependency between</FONT>
<BR><FONT SIZE=2>&gt;these two drafts in case one gets approved by the IESG before the other.</FONT>
</P>

<P><FONT SIZE=2>I still don't like the idea of changing references to an RFC into references to an ID.</FONT>
<BR><FONT SIZE=2>How about if we just change 1493 to XXXX throughout the doc, and add a note to the</FONT>
<BR><FONT SIZE=2>RFC editor somewhere that these XXXX's need to be changed to the appropriate RFC #</FONT>
<BR><FONT SIZE=2>after the -smiv2- draft is published as an RFC?</FONT>
</P>

<P><FONT SIZE=2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4F407.B39E26F2--


--===============0870727311==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0870727311==--



From bridge-mib-bounces@ietf.org  Thu Jan  6 11:22:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20198;
	Thu, 6 Jan 2005 11:22:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmacG-0002dE-Vx; Thu, 06 Jan 2005 11:36:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmaNf-0007zG-Sn; Thu, 06 Jan 2005 11:20:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmaKg-00074H-GX
	for bridge-mib@megatron.ietf.org; Thu, 06 Jan 2005 11:17:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19803
	for <bridge-mib@ietf.org>; Thu, 6 Jan 2005 11:17:52 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmaXU-0000Xb-5N
	for bridge-mib@ietf.org; Thu, 06 Jan 2005 11:31:08 -0500
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j06GH9W16965; Thu, 6 Jan 2005 11:17:09 -0500 (EST)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WKMBF8S8>; Thu, 6 Jan 2005 08:17:09 -0800
Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BD0BB@zsc3c026.us.nortel.com>
From: "David Levi" <dlevi@nortelnetworks.com>
To: "'John Flick'" <john.flick@hp.com>
Subject: RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
Date: Thu, 6 Jan 2005 08:17:08 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0523243249=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5b943e80df8c8cad631fd60298783617

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.

--===============0523243249==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F40B.2B880A90"

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_01C4F40B.2B880A90
Content-Type: text/plain

Hi John,

A few more comments below . . . 

-Dave

-----Original Message-----
From: John Flick [mailto:john.flick@hp.com] 
Sent: Friday, December 17, 2004 10:15 PM
To: Levi, David [SC100:323:EXCH]
Cc: bridge-mib@ietf.org; Congdon, Paul T; dbharrington@comcast.net
Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt


See inline.

Thanks,
John

David Levi wrote:
> Hi All,
> 
> I've fixed some of these items, as described below, in the nroff
> sources, so we'll have the changes in the next draft when/if it is 
> submitted.
> 
> -Dave
> 
> -----Original Message-----
> From: bridge-mib-bounces@ietf.org [mailto:bridge-mib-bounces@ietf.org]
> Sent: Friday, November 19, 2004 9:40 PM
> To: bridge-mib@ietf.org
> Cc: Congdon, Paul T
> Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
> 
> 
> Hi,
> 
> I have the following comments on this draft.  I have divided my 
> comments
> into introductory text, P-BRIDGE-MIB, and Q-BRIDGE-MIB.
> 



> 6. In Section 2, the following sentence:
> 
>     "IEEE 802.1Q defined port-based Virtual LANs where membership
>     is determined by the bridge port on which data frames are
>     received"
> 
>     should be updated for protocol VLANs.
> DBL> Can you suggest some text?

"IEEE 802.1Q defines port-based Virtual LANs where membership is determined
by the bridge port on which data frames are received, and
port-and-protocol-based Virtual LANs where membership is determined by the
bridge port on which frames are received and the protocol identifier of the
frame."

Note: I picked on consistency with protocol VLANs in my comments because we
define MIB objects in this document for managing protocol VLANs.  This is
not so much an issue of alignment with the latest version of 802.1Q as it is
an issue of internal consistency of this document.

DBL>  Fixed, I added your suggested text.

> 13. Much of the text in section 3.4.3 is about to be rendered obsolete
>      by draft-ietf-bridge-bridgemib-smiv2-07.txt.
> DBL> Is there anything in this section that will *not* be rendered 
> DBL> obsolete, and so should not be removed?

A minimal change would be to remove the note about compliance statements not
existing because the MIB uses SMIv1.

DBL>  I think minimal change is what we want, so I just removed the
statement SMIv1.

> P-BRIDGE-MIB comments:

> 4. Description of dot1dPortOutboundAccessPriority seems wrong - outbound
>     definition talks about received frame instead of transmitted 
> frame.
> DBL> Can others on the mailing-list verify this?  The current wording 
> DBL> is the same as was in RFC 2674.

We may want to leave this for IEEE to fix.  802.1D-1998 seems a bit
inconsistent here - the text in section 7.5.1 suggests that the outbound
access priority should be mapped from the regenerated user priority, but the
text in 7.7.5 seems to say that it should be mapped from the user_priority
in the receive data indication, which would be the receive user_priority
before the regenerated user priority mapping is applied.

DBL>  Okay, so no change.


> Q-BRIDGE-MIB comments:

> 3. dot1qForwardAllStaticPorts description talks about non-EFS behaviour,
>     but the acronym EFS has not been defined, and does not appear
>     anywhere else in this document.
> DBL> What would you suggest we change?  Perhaps adding a REFERENCE to 
> DBL> this object?

EFS probably means "extended filtering services", but the acronym is never
defined in either this document or in 802.1D.  This description talks about
non-EFS behavior.  802.1D refers to 802.1D-1990 filtering behavior as "basic
filtering services".  We should just replace "non-EFS behavior" with "basic
filtering services behavior".

DBL>  I changed the text to:
DBL>       to indicate the standard behaviour of using basic filtering
services


> 4. The description of dot1qPortAcceptableFrameTypes is no longer
>     accurate with protocol VLANs.
> DBL> Can you suggest how to change the text?

In the first paragraph of the description, replace "assigned to the PVID for
this port" with "assigned based on the PVID and VID Set for this port".

DBL>  Your suggested text doesn't indicate to what the frame is being
assigned.
DBL>  The old text did indicate this.  How about 'assigned to a VID based on
the
DBL>  port's PVID and VID settings'?



------_=_NextPart_001_01C4F40B.2B880A90
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Bridge-mib] WG Last =
Call:dratf-ietf-bridge-ext-v2-03.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi John,</FONT>
</P>

<P><FONT SIZE=3D2>A few more comments below . . . </FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: John Flick [<A =
HREF=3D"mailto:john.flick@hp.com">mailto:john.flick@hp.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Friday, December 17, 2004 10:15 PM</FONT>
<BR><FONT SIZE=3D2>To: Levi, David [SC100:323:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: bridge-mib@ietf.org; Congdon, Paul T; =
dbharrington@comcast.net</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Bridge-mib] WG Last =
Call:dratf-ietf-bridge-ext-v2-03.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>See inline.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>John</FONT>
</P>

<P><FONT SIZE=3D2>David Levi wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; Hi All,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I've fixed some of these items, as described =
below, in the nroff</FONT>
<BR><FONT SIZE=3D2>&gt; sources, so we'll have the changes in the next =
draft when/if it is </FONT>
<BR><FONT SIZE=3D2>&gt; submitted.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -Dave</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: bridge-mib-bounces@ietf.org [<A =
HREF=3D"mailto:bridge-mib-bounces@ietf.org">mailto:bridge-mib-bounces@ie=
tf.org</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Friday, November 19, 2004 9:40 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: bridge-mib@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Congdon, Paul T</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Bridge-mib] WG Last =
Call:dratf-ietf-bridge-ext-v2-03.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have the following comments on this =
draft.&nbsp; I have divided my </FONT>
<BR><FONT SIZE=3D2>&gt; comments</FONT>
<BR><FONT SIZE=3D2>&gt; into introductory text, P-BRIDGE-MIB, and =
Q-BRIDGE-MIB.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; 6. In Section 2, the following sentence:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &quot;IEEE 802.1Q =
defined port-based Virtual LANs where membership</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; is determined by the =
bridge port on which data frames are</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; received&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; should be updated for =
protocol VLANs.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; Can you suggest some text?</FONT>
</P>

<P><FONT SIZE=3D2>&quot;IEEE 802.1Q defines port-based Virtual LANs =
where membership is determined by the bridge port on which data frames =
are received, and port-and-protocol-based Virtual LANs where membership =
is determined by the bridge port on which frames are received and the =
protocol identifier of the frame.&quot;</FONT></P>

<P><FONT SIZE=3D2>Note: I picked on consistency with protocol VLANs in =
my comments because we define MIB objects in this document for managing =
protocol VLANs.&nbsp; This is not so much an issue of alignment with =
the latest version of 802.1Q as it is an issue of internal consistency =
of this document.</FONT></P>

<P><FONT SIZE=3D2>DBL&gt;&nbsp; Fixed, I added your suggested =
text.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; 13. Much of the text in section 3.4.3 is about =
to be rendered obsolete</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by =
draft-ietf-bridge-bridgemib-smiv2-07.txt.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; Is there anything in this section that =
will *not* be rendered </FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; obsolete, and so should not be =
removed?</FONT>
</P>

<P><FONT SIZE=3D2>A minimal change would be to remove the note about =
compliance statements not existing because the MIB uses SMIv1.</FONT>
</P>

<P><FONT SIZE=3D2>DBL&gt;&nbsp; I think minimal change is what we want, =
so I just removed the statement SMIv1.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; P-BRIDGE-MIB comments:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; 4. Description of =
dot1dPortOutboundAccessPriority seems wrong - outbound</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; definition talks about =
received frame instead of transmitted </FONT>
<BR><FONT SIZE=3D2>&gt; frame.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; Can others on the mailing-list verify =
this?&nbsp; The current wording </FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; is the same as was in RFC 2674.</FONT>
</P>

<P><FONT SIZE=3D2>We may want to leave this for IEEE to fix.&nbsp; =
802.1D-1998 seems a bit inconsistent here - the text in section 7.5.1 =
suggests that the outbound access priority should be mapped from the =
regenerated user priority, but the text in 7.7.5 seems to say that it =
should be mapped from the user_priority in the receive data indication, =
which would be the receive user_priority before the regenerated user =
priority mapping is applied.</FONT></P>

<P><FONT SIZE=3D2>DBL&gt;&nbsp; Okay, so no change.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; Q-BRIDGE-MIB comments:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; 3. dot1qForwardAllStaticPorts description talks =
about non-EFS behaviour,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; but the acronym EFS has =
not been defined, and does not appear</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; anywhere else in this =
document.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; What would you suggest we change?&nbsp; =
Perhaps adding a REFERENCE to </FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; this object?</FONT>
</P>

<P><FONT SIZE=3D2>EFS probably means &quot;extended filtering =
services&quot;, but the acronym is never defined in either this =
document or in 802.1D.&nbsp; This description talks about non-EFS =
behavior.&nbsp; 802.1D refers to 802.1D-1990 filtering behavior as =
&quot;basic filtering services&quot;.&nbsp; We should just replace =
&quot;non-EFS behavior&quot; with &quot;basic filtering services =
behavior&quot;.</FONT></P>

<P><FONT SIZE=3D2>DBL&gt;&nbsp; I changed the text to:</FONT>
<BR><FONT SIZE=3D2>DBL&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
indicate the standard behaviour of using basic filtering =
services</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; 4. The description of =
dot1qPortAcceptableFrameTypes is no longer</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; accurate with protocol =
VLANs.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt; Can you suggest how to change the =
text?</FONT>
</P>

<P><FONT SIZE=3D2>In the first paragraph of the description, replace =
&quot;assigned to the PVID for this port&quot; with &quot;assigned =
based on the PVID and VID Set for this port&quot;.</FONT></P>

<P><FONT SIZE=3D2>DBL&gt;&nbsp; Your suggested text doesn't indicate to =
what the frame is being assigned.</FONT>
<BR><FONT SIZE=3D2>DBL&gt;&nbsp; The old text did indicate this.&nbsp; =
How about 'assigned to a VID based on the</FONT>
<BR><FONT SIZE=3D2>DBL&gt;&nbsp; port's PVID and VID settings'?</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4F40B.2B880A90--


--===============0523243249==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0523243249==--



From bridge-mib-bounces@ietf.org  Thu Jan  6 17:32:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01279;
	Thu, 6 Jan 2005 17:32:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmgNe-0005gC-IV; Thu, 06 Jan 2005 17:45:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmg9X-00014e-Qc; Thu, 06 Jan 2005 17:30:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cmg7V-0007KH-FX
	for bridge-mib@megatron.ietf.org; Thu, 06 Jan 2005 17:28:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00745
	for <bridge-mib@ietf.org>; Thu, 6 Jan 2005 17:28:39 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmgKM-0005Yf-Dw
	for bridge-mib@ietf.org; Thu, 06 Jan 2005 17:41:59 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 9F9C8E88B
	for <bridge-mib@ietf.org>; Thu,  6 Jan 2005 23:28:03 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 18319-02; Thu,  6 Jan 2005 23:28:02 +0100 (CET)
Received: from james (I8abe.i.pppool.de [85.73.138.190])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 7D9FBE77B;
	Thu,  6 Jan 2005 23:28:02 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1Cmg6q-0006Td-Ta; Thu, 06 Jan 2005 23:28:00 +0100
Date: Thu, 6 Jan 2005 23:28:00 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: bridge-mib@ietf.org
Subject: Re: [Bridge-mib] Review comments on
	draft-ietf-bridge-bridgemib-smiv2-07.txt
Message-ID: <20050106222800.GB24475@james>
Mail-Followup-To: bridge-mib@ietf.org
References: <200412301937.OAA09486@ietf.org>
	<Pine.LNX.4.10.10412311020120.25140-100000@shell4.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.10.10412311020120.25140-100000@shell4.bayarea.net>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab

On Fri, Dec 31, 2004 at 10:48:40AM -0800, C. M. Heard wrote:
 
> > If we can do this, it would move the mib up under mib-2, and eliminate
> > the forward reference (issue #757). 
> > It would also place the object and notification subtrees under the
> > dot1dBridge MODULE-IDENTITY, approximating the recommended practices
> > from draft-ietf-ops-mib-review-guidelines Suggested OID layout. 
> 
> All of these sound to me like Good Things.

I have applied the changes. Here is the current tree structure:

  --dot1dBridge(1.3.6.1.2.1.17)		# MODULE-IDENTITY
    +--dot1dNotifications(0)
    +--dot1dBase(1)
    +--dot1dStp(2)
    +--dot1dSr(3)
    +--dot1dTp(4)
    +--dot1dStatic(5)
    +--dot1dConformance(8)
       +--dot1dGroups(1)
       +--dot1dCompliances(2)

And this is the relevant part of the MIB module:

  -- ---------------------------------------------------------- --
  -- subtrees in the Bridge MIB
  -- ---------------------------------------------------------- --

  dot1dNotifications  OBJECT IDENTIFIER ::= { dot1dBridge 0 }

  dot1dBase           OBJECT IDENTIFIER ::= { dot1dBridge 1 }
  dot1dStp            OBJECT IDENTIFIER ::= { dot1dBridge 2 }

  dot1dSr             OBJECT IDENTIFIER ::= { dot1dBridge 3 }
  -- documented in RFC 1525

  dot1dTp             OBJECT IDENTIFIER ::= { dot1dBridge 4 }
  dot1dStatic         OBJECT IDENTIFIER ::= { dot1dBridge 5 }

  -- Subtrees used by Bridge MIB Extensions:
  --      pBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 6 }
  --      qBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 7 }
  -- Note that the practice of registering related MIB modules
  -- below dot1dBridge has been discouraged since there is no
  -- robust mechanism to track such registrations.
  
  dot1dConformance    OBJECT IDENTIFIER ::= { dot1dBridge 8 }

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Thu Jan  6 17:42:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01979;
	Thu, 6 Jan 2005 17:42:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmgXx-0005wd-PJ; Thu, 06 Jan 2005 17:56:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmgK7-0005AD-O8; Thu, 06 Jan 2005 17:41:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmgId-0004MK-KH
	for bridge-mib@megatron.ietf.org; Thu, 06 Jan 2005 17:40:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01830
	for <bridge-mib@ietf.org>; Thu, 6 Jan 2005 17:40:09 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmgVU-0005re-2n
	for bridge-mib@ietf.org; Thu, 06 Jan 2005 17:53:29 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 100F6E8A2;
	Thu,  6 Jan 2005 23:39:39 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 18699-01; Thu,  6 Jan 2005 23:39:38 +0100 (CET)
Received: from james (I8abe.i.pppool.de [85.73.138.190])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id D153BE88E;
	Thu,  6 Jan 2005 23:39:37 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CmgI4-0006Tn-5y; Thu, 06 Jan 2005 23:39:36 +0100
Date: Thu, 6 Jan 2005 23:39:36 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
Message-ID: <20050106223936.GC24475@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	bridge-mib@ietf.org
References: <200501051823.NAA27885@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501051823.NAA27885@ietf.org>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

On Wed, Jan 05, 2005 at 01:22:58PM -0500, David B Harrington wrote:

> UNRESOLVED ISSUES:
> 
> #543: smiv2-06: semantic changes; the following objects changed
> semantics of an existing object: dot1dPortPriority,
> dot1dStpTimeSinceTopologyChange, and dot1dStaticAllowedToGoTo. These
> objects were modified to support 802.1t semantics. Since 802.1t
> implementations have been fielded before this mib becomes available,
> the behavior of current agent implementations might be non-compliant
> with the updated definitions. Even an implementation that claims
> compliance to bridgeCompliance1493 will be impacted because the
> semantics of objects from RFC 1493 have been changed. 

dot1dStpPriority:
dot1dStpPortPriority:

I think the change is really a clarification that only a subset of
the original value range is allowed for bridges that comply to IEEE
802.1t or IEEE 802.1w so I do not see a real problem here for _agent_
implementations. Bridges supporting IEEE 802.1t or IEEE 802.1w likely
reject values which are outside the set of legal values and I would
guess that this is exactly what is currently implemented and deployed.
Can someone confirm my guess?

dot1dStpTimeSinceTopologyChange:

Can't really judge the difference since I do not know enough about
RSTP and tcWhile timers. Can someone explain what the impact of this
change might be?

dot1dStaticAllowedToGoTo:

I am not sure what the issue here is. Did this semantically chance
at all?

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Fri Jan  7 12:31:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00123;
	Fri, 7 Jan 2005 12:31:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmyAF-0000Ea-5W; Fri, 07 Jan 2005 12:44:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmxox-0008Hf-Mw; Fri, 07 Jan 2005 12:22:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cmxlj-0006Lr-0F
	for bridge-mib@megatron.ietf.org; Fri, 07 Jan 2005 12:19:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29036
	for <bridge-mib@ietf.org>; Fri, 7 Jan 2005 12:19:17 -0500 (EST)
Message-Id: <200501071719.MAA29036@ietf.org>
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cmxyf-0007d8-8t
	for bridge-mib@ietf.org; Fri, 07 Jan 2005 12:32:48 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc11) with SMTP
	id <200501071718430130000hcne>; Fri, 7 Jan 2005 17:18:43 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Review comments
	ondraft-ietf-bridge-bridgemib-smiv2-07.txt
Date: Fri, 7 Jan 2005 12:18:39 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <20050106222800.GB24475@james>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
thread-index: AcT0P4vfWtgpQuaPTQGsbV/E5lXDbQAnOlrw
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit

Hi,

I recommend that the RSTP-MIB be positioned directly under mib-2 as
well, rather than under dot1dbridge. 

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of Juergen 
> Schoenwaelder
> Sent: Thursday, January 06, 2005 5:28 PM
> To: bridge-mib@ietf.org
> Subject: Re: [Bridge-mib] Review comments 
> ondraft-ietf-bridge-bridgemib-smiv2-07.txt
> 
> On Fri, Dec 31, 2004 at 10:48:40AM -0800, C. M. Heard wrote:
>  
> > > If we can do this, it would move the mib up under mib-2, 
> and eliminate
> > > the forward reference (issue #757). 
> > > It would also place the object and notification subtrees under
the
> > > dot1dBridge MODULE-IDENTITY, approximating the 
> recommended practices
> > > from draft-ietf-ops-mib-review-guidelines Suggested OID layout. 
> > 
> > All of these sound to me like Good Things.
> 
> I have applied the changes. Here is the current tree structure:
> 
>   --dot1dBridge(1.3.6.1.2.1.17)		# MODULE-IDENTITY
>     +--dot1dNotifications(0)
>     +--dot1dBase(1)
>     +--dot1dStp(2)
>     +--dot1dSr(3)
>     +--dot1dTp(4)
>     +--dot1dStatic(5)
>     +--dot1dConformance(8)
>        +--dot1dGroups(1)
>        +--dot1dCompliances(2)
> 
> And this is the relevant part of the MIB module:
> 
>   -- ---------------------------------------------------------- --
>   -- subtrees in the Bridge MIB
>   -- ---------------------------------------------------------- --
> 
>   dot1dNotifications  OBJECT IDENTIFIER ::= { dot1dBridge 0 }
> 
>   dot1dBase           OBJECT IDENTIFIER ::= { dot1dBridge 1 }
>   dot1dStp            OBJECT IDENTIFIER ::= { dot1dBridge 2 }
> 
>   dot1dSr             OBJECT IDENTIFIER ::= { dot1dBridge 3 }
>   -- documented in RFC 1525
> 
>   dot1dTp             OBJECT IDENTIFIER ::= { dot1dBridge 4 }
>   dot1dStatic         OBJECT IDENTIFIER ::= { dot1dBridge 5 }
> 
>   -- Subtrees used by Bridge MIB Extensions:
>   --      pBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 6 }
>   --      qBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 7 }
>   -- Note that the practice of registering related MIB modules
>   -- below dot1dBridge has been discouraged since there is no
>   -- robust mechanism to track such registrations.
>   
>   dot1dConformance    OBJECT IDENTIFIER ::= { dot1dBridge 8 }
> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Fri Jan  7 15:04:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16443;
	Fri, 7 Jan 2005 15:04:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cn0Yo-0003nW-W8; Fri, 07 Jan 2005 15:18:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cn0L7-0003to-5h; Fri, 07 Jan 2005 15:04:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cn0K1-0002pY-93
	for bridge-mib@megatron.ietf.org; Fri, 07 Jan 2005 15:02:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16385
	for <bridge-mib@ietf.org>; Fri, 7 Jan 2005 15:02:55 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cn0X1-0003ZG-4l
	for bridge-mib@ietf.org; Fri, 07 Jan 2005 15:16:26 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 9436DE8A2;
	Fri,  7 Jan 2005 21:02:18 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 06233-09; Fri,  7 Jan 2005 21:02:17 +0100 (CET)
Received: from james (I867d.i.pppool.de [85.73.134.125])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 96E37E88E;
	Fri,  7 Jan 2005 21:02:17 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1Cn0JL-0001wH-Hp; Fri, 07 Jan 2005 21:02:15 +0100
Date: Fri, 7 Jan 2005 21:02:15 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Review comments
	ondraft-ietf-bridge-bridgemib-smiv2-07.txt
Message-ID: <20050107200215.GA7441@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	bridge-mib@ietf.org
References: <20050106222800.GB24475@james> <200501071719.MAA29036@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501071719.MAA29036@ietf.org>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

On Fri, Jan 07, 2005 at 12:18:39PM -0500, David B Harrington wrote:
 
> I recommend that the RSTP-MIB be positioned directly under mib-2 as
> well, rather than under dot1dbridge. 

Yes. In fact, I hacked some code into libsmi yesterday so that it will 
warn in cases where a module identity is somewhere in the internet.mgmt
subtree and not directly below mib-2, transmission or snmpModules. The
idea is that MIB authors get a warning early in the process.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Fri Jan  7 23:18:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23102;
	Fri, 7 Jan 2005 23:18:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cn8GS-0002Ru-UE; Fri, 07 Jan 2005 23:31:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cn828-0001uF-H5; Fri, 07 Jan 2005 23:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cn7r1-0006p7-CK
	for bridge-mib@megatron.ietf.org; Fri, 07 Jan 2005 23:05:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21823
	for <bridge-mib@ietf.org>; Fri, 7 Jan 2005 23:05:27 -0500 (EST)
Received: from palrel12.hp.com ([156.153.255.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cn847-0001F5-FN
	for bridge-mib@ietf.org; Fri, 07 Jan 2005 23:19:03 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160])
	by palrel12.hp.com (Postfix) with ESMTP
	id 5CDD84169F2; Fri,  7 Jan 2005 20:05:26 -0800 (PST)
Received: from [127.0.0.1] (ros54018lap.americas.hpqcorp.net [15.255.5.21])
	by rosemail.rose.hp.com (Postfix) with ESMTP id 0FEF98220;
	Fri,  7 Jan 2005 20:05:26 -0800 (PST)
Message-ID: <41DF5AAA.7060803@hp.com>
Date: Fri, 07 Jan 2005 19:59:38 -0800
From: John Flick <john.flick@hp.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Levi <dlevi@nortelnetworks.com>
Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
References: <0A11633F61BD9F40B43ABCC694004F93043BD0BB@zsc3c026.us.nortel.com>
In-Reply-To: <0A11633F61BD9F40B43ABCC694004F93043BD0BB@zsc3c026.us.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Dave,

Your changes look fine except for one nit.

David Levi wrote:
>  > 4. The description of dot1qPortAcceptableFrameTypes is no longer
>  >     accurate with protocol VLANs.
>  > DBL> Can you suggest how to change the text?
> 
> In the first paragraph of the description, replace "assigned to the PVID 
> for this port" with "assigned based on the PVID and VID Set for this port".
> 
> DBL>  Your suggested text doesn't indicate to what the frame is being 
> assigned.
> DBL>  The old text did indicate this.  How about 'assigned to a VID 
> based on the
> DBL>  port's PVID and VID settings'?

I think I would put change this to "assigned to a VID based on the PVID
and VID Set for this port."  The "VID Set" term is the protocol VLAN
term I was trying to pull in here.

John


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


From bridge-mib-bounces@ietf.org  Fri Jan  7 23:21:49 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23292;
	Fri, 7 Jan 2005 23:21:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cn8Jv-0002hx-IX; Fri, 07 Jan 2005 23:35:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cn83T-0002Lv-2h; Fri, 07 Jan 2005 23:18:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cn7um-0007At-5C
	for bridge-mib@megatron.ietf.org; Fri, 07 Jan 2005 23:09:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22296
	for <bridge-mib@ietf.org>; Fri, 7 Jan 2005 23:09:21 -0500 (EST)
Received: from palrel13.hp.com ([156.153.255.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cn87r-0001dA-9m
	for bridge-mib@ietf.org; Fri, 07 Jan 2005 23:22:57 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160])
	by palrel13.hp.com (Postfix) with ESMTP
	id 587731C14F8D; Fri,  7 Jan 2005 20:09:20 -0800 (PST)
Received: from [127.0.0.1] (ros54018lap.americas.hpqcorp.net [15.255.5.21])
	by rosemail.rose.hp.com (Postfix) with ESMTP id 4584C7FF2;
	Fri,  7 Jan 2005 20:06:55 -0800 (PST)
Message-ID: <41DF5B03.8070309@hp.com>
Date: Fri, 07 Jan 2005 20:01:07 -0800
From: John Flick <john.flick@hp.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Levi <dlevi@nortelnetworks.com>
Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
References: <0A11633F61BD9F40B43ABCC694004F93043BD0BA@zsc3c026.us.nortel.com>
In-Reply-To: <0A11633F61BD9F40B43ABCC694004F93043BD0BA@zsc3c026.us.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit

Dave,

Whatever format makes it easiest for the RFC Editor to Do The Right
Thing is fine by me.

Thanks,
John

David Levi wrote:
> John,
> 
>  >> 2. References to RFC 1493 should refer to the updated version
>  >>     in draft-ietf-bridge-bridgemib-smiv2-07.txt.
>  >> DBL> I don't think it makes sense to change this, since these
>  >> DBL> references will just need to be updated to the new RFC number for
>  >> DBL> draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published as
>  >> DBL> an RFC.
>  >
>  >Making this change would help the RFC editor find the places that need 
> to be updated to refer
>  >to the new RFC when published, as well as alerting the RFC editor to 
> the dependency between
>  >these two drafts in case one gets approved by the IESG before the other.
> 
> I still don't like the idea of changing references to an RFC into 
> references to an ID.
> How about if we just change 1493 to XXXX throughout the doc, and add a 
> note to the
> RFC editor somewhere that these XXXX's need to be changed to the 
> appropriate RFC #
> after the -smiv2- draft is published as an RFC?
> 
> -Dave
> 


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


From bridge-mib-bounces@ietf.org  Mon Jan 10 09:48:56 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23036;
	Mon, 10 Jan 2005 09:48:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co14R-0003Zu-5I; Mon, 10 Jan 2005 10:03:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co0q6-0001Xv-Ek; Mon, 10 Jan 2005 09:48:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co0oU-0001Kq-PN
	for bridge-mib@megatron.ietf.org; Mon, 10 Jan 2005 09:46:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22922
	for <bridge-mib@ietf.org>; Mon, 10 Jan 2005 09:46:32 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co126-0003Sg-Q0
	for bridge-mib@ietf.org; Mon, 10 Jan 2005 10:00:39 -0500
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0AEjv713215; Mon, 10 Jan 2005 09:45:58 -0500 (EST)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WKMBGAVH>; Mon, 10 Jan 2005 06:45:56 -0800
Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BD0C8@zsc3c026.us.nortel.com>
From: "David Levi" <dlevi@nortelnetworks.com>
To: "'John Flick'" <john.flick@hp.com>
Subject: RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
Date: Mon, 10 Jan 2005 06:45:55 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1041871072=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f

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.

--===============1041871072==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F723.168D94F0"

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_01C4F723.168D94F0
Content-Type: text/plain

John,

Okay, changed.

-Dave

-----Original Message-----
From: John Flick [mailto:john.flick@hp.com] 
Sent: Friday, January 07, 2005 11:00 PM
To: Levi, David [SC100:323:EXCH]
Cc: Congdon, Paul T; bridge-mib@ietf.org
Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt


Dave,

Your changes look fine except for one nit.

David Levi wrote:
>  > 4. The description of dot1qPortAcceptableFrameTypes is no longer
>  >     accurate with protocol VLANs.
>  > DBL> Can you suggest how to change the text?
> 
> In the first paragraph of the description, replace "assigned to the 
> PVID
> for this port" with "assigned based on the PVID and VID Set for this
port".
> 
> DBL>  Your suggested text doesn't indicate to what the frame is being
> assigned.
> DBL>  The old text did indicate this.  How about 'assigned to a VID
> based on the
> DBL>  port's PVID and VID settings'?

I think I would put change this to "assigned to a VID based on the PVID and
VID Set for this port."  The "VID Set" term is the protocol VLAN term I was
trying to pull in here.

John



------_=_NextPart_001_01C4F723.168D94F0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Bridge-mib] WG Last =
Call:dratf-ietf-bridge-ext-v2-03.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>John,</FONT>
</P>

<P><FONT SIZE=3D2>Okay, changed.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: John Flick [<A =
HREF=3D"mailto:john.flick@hp.com">mailto:john.flick@hp.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Friday, January 07, 2005 11:00 PM</FONT>
<BR><FONT SIZE=3D2>To: Levi, David [SC100:323:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: Congdon, Paul T; bridge-mib@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Bridge-mib] WG Last =
Call:dratf-ietf-bridge-ext-v2-03.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Dave,</FONT>
</P>

<P><FONT SIZE=3D2>Your changes look fine except for one nit.</FONT>
</P>

<P><FONT SIZE=3D2>David Levi wrote:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; 4. The description of =
dot1qPortAcceptableFrameTypes is no longer</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt;&nbsp;&nbsp;&nbsp;&nbsp; accurate =
with protocol VLANs.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; DBL&gt; Can you suggest how to =
change the text?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; In the first paragraph of the description, =
replace &quot;assigned to the </FONT>
<BR><FONT SIZE=3D2>&gt; PVID</FONT>
<BR><FONT SIZE=3D2>&gt; for this port&quot; with &quot;assigned based =
on the PVID and VID Set for this port&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt;&nbsp; Your suggested text doesn't =
indicate to what the frame is being</FONT>
<BR><FONT SIZE=3D2>&gt; assigned.</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt;&nbsp; The old text did indicate =
this.&nbsp; How about 'assigned to a VID</FONT>
<BR><FONT SIZE=3D2>&gt; based on the</FONT>
<BR><FONT SIZE=3D2>&gt; DBL&gt;&nbsp; port's PVID and VID =
settings'?</FONT>
</P>

<P><FONT SIZE=3D2>I think I would put change this to &quot;assigned to =
a VID based on the PVID and VID Set for this port.&quot;&nbsp; The =
&quot;VID Set&quot; term is the protocol VLAN term I was trying to pull =
in here.</FONT></P>

<P><FONT SIZE=3D2>John</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4F723.168D94F0--


--===============1041871072==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1041871072==--



From bridge-mib-bounces@ietf.org  Mon Jan 10 09:57:50 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23469;
	Mon, 10 Jan 2005 09:57:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co1D1-0003tE-Vj; Mon, 10 Jan 2005 10:11:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co0tV-00023y-Qz; Mon, 10 Jan 2005 09:51:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co0rU-0001jQ-DF
	for bridge-mib@megatron.ietf.org; Mon, 10 Jan 2005 09:49:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23066
	for <bridge-mib@ietf.org>; Mon, 10 Jan 2005 09:49:38 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co157-0003a7-3A
	for bridge-mib@ietf.org; Mon, 10 Jan 2005 10:03:45 -0500
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0AEn6713956; Mon, 10 Jan 2005 09:49:07 -0500 (EST)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WKMBGAVL>; Mon, 10 Jan 2005 06:49:06 -0800
Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BD0C9@zsc3c026.us.nortel.com>
From: "David Levi" <dlevi@nortelnetworks.com>
To: "'John Flick'" <john.flick@hp.com>
Subject: RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt
Date: Mon, 10 Jan 2005 06:49:05 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: "Congdon, Paul T" <paul.congdon@hp.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1477495773=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7

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.

--===============1477495773==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F723.880B4514"

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_01C4F723.880B4514
Content-Type: text/plain

John,

Okay, I changed all the references to XXXX, and added t a note for the
RFC editor just after the first occurance.

-Dave

-----Original Message-----
From: John Flick [mailto:john.flick@hp.com] 
Sent: Friday, January 07, 2005 11:01 PM
To: Levi, David [SC100:323:EXCH]
Cc: bridge-mib@ietf.org; Congdon, Paul T; dbharrington@comcast.net
Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt


Dave,

Whatever format makes it easiest for the RFC Editor to Do The Right Thing is
fine by me.

Thanks,
John

David Levi wrote:
> John,
> 
>  >> 2. References to RFC 1493 should refer to the updated version
>  >>     in draft-ietf-bridge-bridgemib-smiv2-07.txt.
>  >> DBL> I don't think it makes sense to change this, since these  >> 
> DBL> references will just need to be updated to the new RFC number for  
> >> DBL> draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published 
> as  >> DBL> an RFC.  >
>  >Making this change would help the RFC editor find the places that need 
> to be updated to refer
>  >to the new RFC when published, as well as alerting the RFC editor to 
> the dependency between
>  >these two drafts in case one gets approved by the IESG before the other.
> 
> I still don't like the idea of changing references to an RFC into
> references to an ID.
> How about if we just change 1493 to XXXX throughout the doc, and add a 
> note to the
> RFC editor somewhere that these XXXX's need to be changed to the 
> appropriate RFC #
> after the -smiv2- draft is published as an RFC?
> 
> -Dave
> 



------_=_NextPart_001_01C4F723.880B4514
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>John,</FONT>
</P>

<P><FONT SIZE=2>Okay, I changed all the references to XXXX, and added t a note for the</FONT>
<BR><FONT SIZE=2>RFC editor just after the first occurance.</FONT>
</P>

<P><FONT SIZE=2>-Dave</FONT>
</P>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: John Flick [<A HREF="mailto:john.flick@hp.com">mailto:john.flick@hp.com</A>] </FONT>
<BR><FONT SIZE=2>Sent: Friday, January 07, 2005 11:01 PM</FONT>
<BR><FONT SIZE=2>To: Levi, David [SC100:323:EXCH]</FONT>
<BR><FONT SIZE=2>Cc: bridge-mib@ietf.org; Congdon, Paul T; dbharrington@comcast.net</FONT>
<BR><FONT SIZE=2>Subject: Re: [Bridge-mib] WG Last Call:dratf-ietf-bridge-ext-v2-03.txt</FONT>
</P>
<BR>

<P><FONT SIZE=2>Dave,</FONT>
</P>

<P><FONT SIZE=2>Whatever format makes it easiest for the RFC Editor to Do The Right Thing is fine by me.</FONT>
</P>

<P><FONT SIZE=2>Thanks,</FONT>
<BR><FONT SIZE=2>John</FONT>
</P>

<P><FONT SIZE=2>David Levi wrote:</FONT>
<BR><FONT SIZE=2>&gt; John,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;&gt; 2. References to RFC 1493 should refer to the updated version</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; in draft-ietf-bridge-bridgemib-smiv2-07.txt.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;&gt; DBL&gt; I don't think it makes sense to change this, since these&nbsp; &gt;&gt; </FONT>
<BR><FONT SIZE=2>&gt; DBL&gt; references will just need to be updated to the new RFC number for&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&gt; DBL&gt; draft-ietf-bridge-bridgemib-smiv2-07.txt when it is published </FONT>
<BR><FONT SIZE=2>&gt; as&nbsp; &gt;&gt; DBL&gt; an RFC.&nbsp; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;Making this change would help the RFC editor find the places that need </FONT>
<BR><FONT SIZE=2>&gt; to be updated to refer</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;to the new RFC when published, as well as alerting the RFC editor to </FONT>
<BR><FONT SIZE=2>&gt; the dependency between</FONT>
<BR><FONT SIZE=2>&gt;&nbsp; &gt;these two drafts in case one gets approved by the IESG before the other.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I still don't like the idea of changing references to an RFC into</FONT>
<BR><FONT SIZE=2>&gt; references to an ID.</FONT>
<BR><FONT SIZE=2>&gt; How about if we just change 1493 to XXXX throughout the doc, and add a </FONT>
<BR><FONT SIZE=2>&gt; note to the</FONT>
<BR><FONT SIZE=2>&gt; RFC editor somewhere that these XXXX's need to be changed to the </FONT>
<BR><FONT SIZE=2>&gt; appropriate RFC #</FONT>
<BR><FONT SIZE=2>&gt; after the -smiv2- draft is published as an RFC?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; -Dave</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4F723.880B4514--


--===============1477495773==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1477495773==--



From bridge-mib-bounces@ietf.org  Tue Jan 11 16:54:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07996;
	Tue, 11 Jan 2005 16:54:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoUCM-0002C1-4y; Tue, 11 Jan 2005 17:09:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoTmK-0005Tj-88; Tue, 11 Jan 2005 16:42:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoTOu-0007Ry-Tf
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 16:18:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01636
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 16:18:02 -0500 (EST)
Message-Id: <200501112118.QAA01636@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoTcn-0008S4-Tt
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 16:32:26 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc12) with SMTP
	id <2005011121173201400ggj6oe>; Tue, 11 Jan 2005 21:17:33 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <j.schoenwaelder@iu-bremen.de>
Subject: RE: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
Date: Tue, 11 Jan 2005 16:17:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <20050106223936.GC24475@james>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
thread-index: AcT0QJ4N8v9CgZLIQpenKxXzGgis0wD4RjVw
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Cc: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi,

1) I agree with your analysis on the Priority objects.
2) I think the topologychange object has been changed in a way that
could break existing (non-RSTP-knowledgeable) applications that are
run against an RSTP-supporting agent, 
3) the range has been constrained in the revision. This is probably
not a problem, but it is a semantic change.

I think these changes are technically illegal, but if the WG accepts
them, I can live with that.
If nobody objects, I will close this issue, and submit the document
with these changes.

dbh

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] On 
> Behalf Of Juergen Schoenwaelder
> Sent: Thursday, January 06, 2005 5:40 PM
> To: David B Harrington
> Cc: bridge-mib@ietf.org
> Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 
> Issues Resolution
> 
> On Wed, Jan 05, 2005 at 01:22:58PM -0500, David B Harrington wrote:
> 
> > UNRESOLVED ISSUES:
> > 
> > #543: smiv2-06: semantic changes; the following objects changed
> > semantics of an existing object: dot1dPortPriority,
> > dot1dStpTimeSinceTopologyChange, and dot1dStaticAllowedToGoTo.
These
> > objects were modified to support 802.1t semantics. Since 802.1t
> > implementations have been fielded before this mib becomes
available,
> > the behavior of current agent implementations might be
non-compliant
> > with the updated definitions. Even an implementation that claims
> > compliance to bridgeCompliance1493 will be impacted because the
> > semantics of objects from RFC 1493 have been changed. 
> 
> dot1dStpPriority:
> dot1dStpPortPriority:
> 
> I think the change is really a clarification that only a subset of
> the original value range is allowed for bridges that comply to IEEE
> 802.1t or IEEE 802.1w so I do not see a real problem here for
_agent_
> implementations. Bridges supporting IEEE 802.1t or IEEE 802.1w
likely
> reject values which are outside the set of legal values and I would
> guess that this is exactly what is currently implemented and
deployed.
> Can someone confirm my guess?
> 
> dot1dStpTimeSinceTopologyChange:
> 
> Can't really judge the difference since I do not know enough about
> RSTP and tcWhile timers. Can someone explain what the impact of this
> change might be?
> 
> dot1dStaticAllowedToGoTo:
> 
> I am not sure what the issue here is. Did this semantically chance
> at all?
> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> 



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


From bridge-mib-bounces@ietf.org  Tue Jan 11 17:50:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12240;
	Tue, 11 Jan 2005 17:50:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoV43-0003Ty-0y; Tue, 11 Jan 2005 18:04:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoUma-0008Vy-Qp; Tue, 11 Jan 2005 17:46:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoUa7-0005Vt-5V
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 17:33:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11213
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 17:33:40 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoUnz-00034v-Vs
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 17:48:05 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 8D60BD47F;
	Tue, 11 Jan 2005 23:33:07 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 05221-04; Tue, 11 Jan 2005 23:33:06 +0100 (CET)
Received: from james (I874b.i.pppool.de [85.73.135.75])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 899F5D404;
	Tue, 11 Jan 2005 23:33:06 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CoUZU-0001df-0o; Tue, 11 Jan 2005 23:33:04 +0100
Date: Tue, 11 Jan 2005 23:33:03 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
Message-ID: <20050111223303.GB6090@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	bridge-mib@ietf.org, "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>
References: <20050106223936.GC24475@james>
	<20050111211734.CD74ED5EE@hermes.iu-bremen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050111211734.CD74ED5EE@hermes.iu-bremen.de>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

On Tue, Jan 11, 2005 at 04:17:28PM -0500, David B Harrington wrote:

> 3) the range has been constrained in the revision. This is probably
> not a problem, but it is a semantic change.

Does someone recall where the introduced size limit for ...AllowedToGoTo
object comes from?  The port index is restricted to 65535 and from that
perspective the upper boundary would be 8K and not 512 bytes (which 
is equivalent to a maximum of 4096 ports). Can some IEEE 802.1 expert
please explain this?

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Tue Jan 11 19:43:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21110;
	Tue, 11 Jan 2005 19:43:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoWq3-0005uw-Ag; Tue, 11 Jan 2005 19:58:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoWQt-0004nc-Ca; Tue, 11 Jan 2005 19:32:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoWGF-0002Bv-EN
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 19:21:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19783
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:21:16 -0500 (EST)
Received: from palrel12.hp.com ([156.153.255.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoWU9-0005PA-4i
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 19:35:42 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160])
	by palrel12.hp.com (Postfix) with ESMTP
	id F2C09406BE8; Tue, 11 Jan 2005 16:21:16 -0800 (PST)
Received: from [127.0.0.1] (ros54018lap.americas.hpqcorp.net [15.255.5.21])
	by rosemail.rose.hp.com (Postfix) with ESMTP id DD7107FFF;
	Tue, 11 Jan 2005 16:21:16 -0800 (PST)
Message-ID: <41E46C1C.9010104@hp.com>
Date: Tue, 11 Jan 2005 16:15:24 -0800
From: John Flick <john.flick@hp.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: j.schoenwaelder@iu-bremen.de
Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
References: <20050106223936.GC24475@james>	<20050111211734.CD74ED5EE@hermes.iu-bremen.de>
	<20050111223303.GB6090@james>
In-Reply-To: <20050111223303.GB6090@james>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: bridge-mib@ietf.org, "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

The PortID used to identify a port in STP (or RSTP or MSTP...) is
16 bits.  Of that, the upper four bits is used for port priority,
and the lower 12 bits are used for the port number, which
effectively limits you to 4k ports per bridge. (This was where the
changes to port priority came from in .1t.  Originally the port
priority and port number were 8 bits each, which limited you to
256 ports per bridge.)  512 bytes can hold a bitmask representing
4k ports.

John

Juergen Schoenwaelder wrote:
> On Tue, Jan 11, 2005 at 04:17:28PM -0500, David B Harrington wrote:
> 
> 
>>3) the range has been constrained in the revision. This is probably
>>not a problem, but it is a semantic change.
> 
> 
> Does someone recall where the introduced size limit for ...AllowedToGoTo
> object comes from?  The port index is restricted to 65535 and from that
> perspective the upper boundary would be 8K and not 512 bytes (which 
> is equivalent to a maximum of 4096 ports). Can some IEEE 802.1 expert
> please explain this?
> 
> /js
> 


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


From bridge-mib-bounces@ietf.org  Tue Jan 11 19:54:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22068;
	Tue, 11 Jan 2005 19:54:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoX0b-00069H-QK; Tue, 11 Jan 2005 20:09:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoWe3-0007hY-07; Tue, 11 Jan 2005 19:45:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoWS7-0004xk-Qc
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 19:33:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20595
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:33:32 -0500 (EST)
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoWg0-0005hY-IS
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 19:47:58 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160])
	by atlrel6.hp.com (Postfix) with ESMTP
	id 6973FB47B; Tue, 11 Jan 2005 19:33:32 -0500 (EST)
Received: from [127.0.0.1] (ros54018lap.americas.hpqcorp.net [15.255.5.21])
	by rosemail.rose.hp.com (Postfix) with ESMTP id 1AB1D7FFF;
	Tue, 11 Jan 2005 16:33:32 -0800 (PST)
Message-ID: <41E46EFC.40107@hp.com>
Date: Tue, 11 Jan 2005 16:27:40 -0800
From: John Flick <john.flick@hp.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dbharrington@comcast.net
Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
References: <200501112118.QAA01636@ietf.org>
In-Reply-To: <200501112118.QAA01636@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>,
        j.schoenwaelder@iu-bremen.de, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Dave,

The tcWhile timer is an internal state variable to indicate the
time remaining for the bridge to send configuration messages with
the topology change bit set.  The added text in the description of
the TimeSinceTopologyChange object just specifies from what point
in the RSTP topology change state machine the topology change
time is measured.  The "meaning" of the object is actually
unchanged.  I'm not sure how this would break an application.

John

David B Harrington wrote:
> 2) I think the topologychange object has been changed in a way that
> could break existing (non-RSTP-knowledgeable) applications that are
> run against an RSTP-supporting agent, 


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


From bridge-mib-bounces@ietf.org  Tue Jan 11 20:16:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23226;
	Tue, 11 Jan 2005 20:16:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoXLl-0006Z9-Ig; Tue, 11 Jan 2005 20:31:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoWwZ-0003K7-1L; Tue, 11 Jan 2005 20:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoWoG-0001Ff-Da
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 19:56:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22172
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:56:25 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoX28-0006BZ-Gj
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 20:10:51 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0C0l7qm024113
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:47:07 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0C0l5qm024074
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 19:47:05 -0500 (EST)
content-class: urn:content-classes:message
Subject: RE: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Jan 2005 02:56:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9FEB@is0004avexu1.global.avaya.com>
Thread-Topic: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2 Issues Resolution
Thread-Index: AcT4L/H4T4O9ZjIBRa25H/BKBQ3YRAAEHMhg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <j.schoenwaelder@iu-bremen.de>,
        "David B Harrington" <dbharrington@comcast.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable
Cc: "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>, bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable

>From the experts floor at the IEEE 802.1 interim meeting where I happen =
to be right now - the maximum number of ports on a 802.1D bridge is =
4k-1. Thus the 512 bytes size limit is justified.=20

Regards,

Dan



> -----Original Message-----
> From: bridge-mib-bounces@ietf.org=20
> [mailto:bridge-mib-bounces@ietf.org]On Behalf Of Juergen Schoenwaelder
> Sent: 12 January, 2005 12:33 AM
> To: David B Harrington
> Cc: 'Wijnen, Bert (Bert)'; bridge-mib@ietf.org
> Subject: Re: [Bridge-mib] Draft-ietf-bridge-bridgemib-smiv2=20
> Issues Resolution
>=20
>=20
> On Tue, Jan 11, 2005 at 04:17:28PM -0500, David B Harrington wrote:
>=20
> > 3) the range has been constrained in the revision. This is probably
> > not a problem, but it is a semantic change.
>=20
> Does someone recall where the introduced size limit for=20
> ...AllowedToGoTo
> object comes from?  The port index is restricted to 65535 and=20
> from that
> perspective the upper boundary would be 8K and not 512 bytes (which=20
> is equivalent to a maximum of 4096 ports). Can some IEEE 802.1 expert
> please explain this?
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561,=20
> 28725 Bremen, Germany
>=20
> _______________________________________________
> Bridge-mib mailing list
> Bridge-mib@ietf.org
> https://www1.ietf.org/mailman/listinfo/bridge-mib
>=20

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


From bridge-mib-bounces@ietf.org  Tue Jan 11 23:18:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04676;
	Tue, 11 Jan 2005 23:18:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoaBb-0001nH-EO; Tue, 11 Jan 2005 23:32:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoZrH-0000Yo-Ic; Tue, 11 Jan 2005 23:11:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoZcY-0003pT-AP
	for bridge-mib@megatron.ietf.org; Tue, 11 Jan 2005 22:56:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03285
	for <bridge-mib@ietf.org>; Tue, 11 Jan 2005 22:56:31 -0500 (EST)
Message-Id: <200501120356.WAA03285@ietf.org>
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoZqR-0001Mn-S9
	for bridge-mib@ietf.org; Tue, 11 Jan 2005 23:10:59 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc11) with SMTP
	id <2005011203553801300t0o0re>; Wed, 12 Jan 2005 03:55:38 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <bridge-mib@ietf.org>
Date: Tue, 11 Jan 2005 22:55:34 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
thread-index: AcT4WpF/OV1L8QqrSAC4Fsz8PH43Wg==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [Bridge-mib] WG Last Call
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

Hi,

All WG Last Call issues for draft-ietf-bridge-bridgemib-smiv2.txt have
been resolved.

I have asked Juergen to publish a new revision of
draft-ietf-bridge-bridgemib-smiv2 with the open issues section removed
from the document, and all corrected text put into the document, in
preparation for submitting the document to the IESG for consideration
as a Proposed Standard.

Thanks,
David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 



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


From bridge-mib-bounces@ietf.org  Wed Jan 12 02:38:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17274;
	Wed, 12 Jan 2005 02:38:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CodJ4-0005tx-1X; Wed, 12 Jan 2005 02:52:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cod3B-0001XI-9g; Wed, 12 Jan 2005 02:36:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cocvq-0007Mw-Ph; Wed, 12 Jan 2005 02:28:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13629;
	Wed, 12 Jan 2005 02:28:41 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cod9o-0005hS-Ss; Wed, 12 Jan 2005 02:43:09 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id E0574D6ED;
	Wed, 12 Jan 2005 08:28:07 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 22923-02; Wed, 12 Jan 2005 08:28:07 +0100 (CET)
Received: from james (I88f9.i.pppool.de [85.73.136.249])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 00166D404;
	Wed, 12 Jan 2005 08:28:06 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CocvF-0000wg-7E; Wed, 12 Jan 2005 08:28:05 +0100
Date: Wed, 12 Jan 2005 08:28:05 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: internet-drafts@ietf.org
Message-ID: <20050112072805.GA3625@james>
Mail-Followup-To: internet-drafts@ietf.org, bridge-mib@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: bridge-mib@ietf.org
Subject: [Bridge-mib] please post draft-ietf-bridge-bridgemib-smiv2-09.txt
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

Please post the following document as an Internet Draft:

<http://www.ibr.cs.tu-bs.de/users/schoenw/draft-ietf-bridge-bridgemib-smiv2-09.txt>

This ID is a product of the bridge mib working group.

Thanks,

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Wed Jan 12 21:10:11 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09953;
	Wed, 12 Jan 2005 21:10:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoufJ-0006XF-K2; Wed, 12 Jan 2005 21:24:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CouM5-0004Zg-Lk; Wed, 12 Jan 2005 21:04:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CouFf-0003Gc-DH
	for bridge-mib@megatron.ietf.org; Wed, 12 Jan 2005 20:58:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09022
	for <bridge-mib@ietf.org>; Wed, 12 Jan 2005 20:58:18 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CouTn-0006JA-Qx
	for bridge-mib@ietf.org; Wed, 12 Jan 2005 21:12:56 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0D1n0qm012284
	for <bridge-mib@ietf.org>; Wed, 12 Jan 2005 20:49:00 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0D1mwqm012235
	for <bridge-mib@ietf.org>; Wed, 12 Jan 2005 20:48:59 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 13 Jan 2005 03:58:14 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E30869@is0004avexu1.global.avaya.com>
Thread-Topic: [802.1] Frank's 802.1AE MIB presentation in public directory
Thread-Index: AcT40fszZy9RCn5PRYOwl7ifZk8/1QAQM+PA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <bridge-mib@ietf.org>
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Subject: [Bridge-mib] FW: [802.1] Frank's 802.1AE MIB presentation in public
	directory
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1398865137=="
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8

This is a multi-part message in MIME format.

--===============1398865137==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F913.57C8DB54"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4F913.57C8DB54
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
The forwarded message includes a pointer to the IEEE 802.1ae MIB =
presentation given at the Sacramento IEEE 802.1 interim meeting by the =
editor of this work - Frank Chao. The Bridge MIB participants are =
encouraged to look at this presentation, and at the MIB module in the =
IEEE 802.1ae draft, and provide their comments. Obviously this is =
work-in-progress.=20

Regards,

Dan

-----Original Message-----
From: IEEE 802.1 [mailto:hdk-1023.dwkfdq@ATT.NET]On Behalf Of Allyn =
Romanow
Sent: 12 January, 2005 7:55 PM
To: STDS-802-1-L@LISTSERV.IEEE.ORG
Subject: [802.1] Frank's 802.1AE MIB presentation in public directory


Here's Frank's presentation from Jan 11


http://www.ieee802.org/1/files/public/docs2005/ =
<http://www.ieee802.org/1/files/public/docs2005/ae-chao-ieee802-secy-mib-=
0111.ppt> ae-chao-ieee802-secy-mib -0111.ppt =
<http://www.ieee802.org/1/files/public/docs2005/ae-chao-ieee802-secy-mib-=
0111.ppt>=20


Sorry I earlier posted the document to the private AE directory.


IEEE 802.1 list info: http://www.ieee802.org/1/email-pages/etkg1204.html =


------_=_NextPart_001_01C4F913.57C8DB54
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
<BODY>
<DIV><STRONG><EM><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></EM></STRONG>&nbsp;</DIV>
<DIV><SPAN class=3D397185401-13012005><FONT face=3DArial color=3D#0000ff =

size=3D2><STRONG><EM>The forwarded message includes a pointer to the =
IEEE 802.1ae=20
MIB presentation given at the Sacramento IEEE 802.1 interim meeting by =
the=20
editor of this work - Frank Chao. The Bridge MIB participants are =
encouraged to=20
look at this presentation, and at the MIB module in the IEEE 802.1ae =
draft, and=20
provide their comments. Obviously this is work-in-progress.=20
</EM></STRONG></FONT></SPAN></DIV>
<P dir=3Dltr><FONT face=3DArial color=3D#0000ff=20
size=3D2><STRONG><EM>Regards,</EM></STRONG></FONT></P>
<P dir=3Dltr><FONT face=3DArial color=3D#0000ff=20
size=3D2><STRONG><EM>Dan</EM></STRONG></FONT></P>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> IEEE 802.1=20
[mailto:hdk-1023.dwkfdq@ATT.NET]<B>On Behalf Of </B>Allyn=20
Romanow<BR><B>Sent:</B> 12 January, 2005 7:55 PM<BR><B>To:</B>=20
STDS-802-1-L@LISTSERV.IEEE.ORG<BR><B>Subject:</B> [802.1] Frank's =
802.1AE MIB=20
presentation in public directory<BR><BR></FONT></DIV>Here's Frank's =
presentation=20
from Jan 11<BR><BR><BR><FONT color=3D#0000ff><U><A=20
href=3D"http://www.ieee802.org/1/files/public/docs2005/ae-chao-ieee802-se=
cy-mib-0111.ppt"=20
eudora=3D"autourl">http://www.ieee802.org/1/files/public/docs2005/</A></U=
></FONT>ae-chao-ieee802-secy-mib<A=20
href=3D"http://www.ieee802.org/1/files/public/docs2005/ae-chao-ieee802-se=
cy-mib-0111.ppt"=20
eudora=3D"autourl">-0111.ppt</A><BR><BR><BR>Sorry I earlier posted the =
document to=20
the private AE directory.<BR><BR><BR>IEEE 802.1 list info:=20
http://www.ieee802.org/1/email-pages/etkg1204.html </BODY></HTML>

------_=_NextPart_001_01C4F913.57C8DB54--


--===============1398865137==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1398865137==--



From bridge-mib-bounces@ietf.org  Thu Jan 13 16:10:20 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17015;
	Thu, 13 Jan 2005 16:10:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpCSs-0006fd-10; Thu, 13 Jan 2005 16:25:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpByx-0008Hl-Ix; Thu, 13 Jan 2005 15:54:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpBtV-0004f8-J6; Thu, 13 Jan 2005 15:48:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14240;
	Thu, 13 Jan 2005 15:48:35 -0500 (EST)
Message-Id: <200501132048.PAA14240@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 13 Jan 2005 15:48:35 -0500
Cc: bridge-mib@ietf.org
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-09.txt
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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, E. Bell
	Filename	: draft-ietf-bridge-bridgemib-smiv2-09.txt
	Pages		: 44
	Date		: 2005-1-13
	
This memo 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 MAC bridges based on
   the IEEE 802.1D-1998 standard between Local Area Network (LAN)
   segments.  Provisions are made for support of transparent bridging.
   Provisions are also made so that these objects apply to bridges
   The MIB module presented in this memo is a translation of the
   BRIDGE-MIB defined in RFC 1493 to the SMIv2 syntax.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-09.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-09.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: <2005-1-13153412.I-D@ietf.org>

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From bridge-mib-bounces@ietf.org  Tue Jan 18 22:40:00 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05970;
	Tue, 18 Jan 2005 22:40:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr6wn-0005iL-92; Tue, 18 Jan 2005 22:55:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr6fK-00064P-L4; Tue, 18 Jan 2005 22:37:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cr6ew-0005vs-E6
	for bridge-mib@megatron.ietf.org; Tue, 18 Jan 2005 22:37:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05668;
	Tue, 18 Jan 2005 22:37:27 -0500 (EST)
Message-Id: <200501190337.WAA05668@ietf.org>
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr6uK-0005dA-JV; Tue, 18 Jan 2005 22:53:24 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (sccrmhc12) with SMTP
	id <200501190336550120012d1ie>; Wed, 19 Jan 2005 03:36:55 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'David Kessens \(E-mail\)'" <david.kessens@nokia.com>,
        <iesg-secretary@ietf.org>
Date: Tue, 18 Jan 2005 22:36:48 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0286_01C4FDAE.34BCC5E0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcT92BshjWAaYb0mQk2rjApZdgdhJg==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Cc: bridge-mib@ietf.org
Subject: [Bridge-mib] Dratf-ietf=bridge=bridgemib-smiv2
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff

This is a multi-part message in MIME format.

------=_NextPart_000_0286_01C4FDAE.34BCC5E0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,

I am the shepherding WG chair for the bridge WG.
I have attached the publication request to consider
draft-ietf-bridge-bridgemib-smiv2-09.txt as a Proposed Standard.

David Harrington
dbharrington@comcast.net


------=_NextPart_000_0286_01C4FDAE.34BCC5E0
Content-Type: text/plain;
	name="publication request for bridgemib-smiv2.txt"
Content-Disposition: attachment;
	filename="publication request for bridgemib-smiv2.txt"
Content-Transfer-Encoding: quoted-printable

Publication Request for darft-ietf-bridge-bridgemib-smiv2.txt as =
Proposed Standard

Shepherding WG Chair: David Harrington

1.a) Have the chairs personally reviewed this version of the ID and
        do they believe this ID is sufficiently baked to forward to the
        IESG for publication?

Yes. Both chairs have reviewed the document.

   1.b) Has the document had adequate review from both key WG members
        and key non-WG members?  Do you have any concerns about the
        depth or breadth of the reviews that have been performed?

The document was reviewed and discussed by several WG members, including =
several MIB Doctors and several persons active in the IEEE 802.1 WG, as =
well as by Bert Wijnen, the Operations and Management Area Director.=20

   1.c) Do you have concerns that the document needs more review from a
        particular (broader) perspective (e.g., security, operational
        complexity, someone familiar with AAA, etc.)?

Although among the reviewers of the document there are several 'MIB =
Doctors' and the editor of the latest version is a MIB Doctor himself, =
no independent MIB Doctor review was performed on the latest revision.=20


   1.d) Do you have any specific concerns/issues with this document that
        you believe the ADs and/or IESG should be aware of?  For
        example, perhaps you are uncomfortable with certain parts of the
        document, or have concerns whether there really is a need for
        it, etc.  If your issues have been discussed in the WG and the
        WG has indicated it wishes to advance the document anyway, note
        if you continue to have concerns.

The scope of the work was discussed on the mailing list and at IETF-61, =
and the decision was that this MIB module should update RFC 1493 into a =
SMIv2 version, and include a very limioted number of changes needed for =
dependent documents of the WG, but will not provide updates relative to =
the ongoing evolution of the IEEE 802.1 standards. This decision is =
supported by the consensus of the WG, and was also communicated with =
IEEE 802.1. As result of the discussions between the IETF and IEEE 802.1 =
it was agreed that new MIB modules or changes in the existing standards =
that reflect the evolution of the IEEE 802.1 technology will be taken =
over by the IEEE 802.1 WG.=20


   1.e) How solid is the WG consensus behind this document?  Does it
        represent the strong concurrence of a few individuals, with
        others being silent, or does the WG as a whole understand and
        agree with it?

The Working Group today does not number too many participants. There =
seems to be strong consensus between the few active participants =
concerning this document.=20


   1.f) Has anyone threatened an appeal or otherwise indicated extreme
        discontent?  If so, please summarise what are they upset about.

No.=20


   1.g) Have the chairs verified that the document adheres to _all_ of
        the ID nits? (see http://www.ietf.org/ID-Checklist.html).

Yes. No nits found.=20


   1.h) Does the document a) split references into normative/
        informative, and b) are there normative references to IDs, where
        the IDs are not also ready for advancement or are otherwise in
        an unclear state? (Note: the RFC editor will not publish an RFC
        with normative references to IDs, it will delay publication
        until all such IDs are also ready for publication as RFCs.)

a) yes b) no


   1.i) For Standards Track and BCP documents, the IESG approval
        announcement includes a writeup section with the following
        sections:


   1.j) Please provide such a writeup.  (We will hopefully use it as is,
        but may make some changes.) For recent examples, have a look at
        the "protocol action" announcements for approved documents.

        *    Technical Summary

This memo 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 MAC bridges based on
   the IEEE 802.1D-1998 standard between Local Area Network (LAN)
   segments.  Provisions are made for support of transparent bridging.
   Provisions are also made so that these objects apply to bridges
   connected by subnetworks other than LAN segments.

   The MIB module presented in this memo is a translation of the
   BRIDGE-MIB defined in RFC 1493 to the SMIv2 syntax, updated=20
   slightly to accommodate higher speed links.


        *    Working Group Summary

The Bridge MIB Working Group discussed this document and approved its =
content=20
in a Working Group Last Call process. All issues raiseds during the WG =
Last Call have been
resolved, maintained in the RT system, and a summary of the resolutions =
was published to=20
the mailing list for comment. The WG recommends that this document be =
forwarded to the IESG for consideration as a Proposed Standard.

It is the intention of the WG that subsequent mib module work for IEEE =
802.1 technologies will be done by the IEEE 802.1 WG. There are some =
concerns about the quality of work likely to=20
result from SNMP non-experts, but the IETF is providing MIB Doctor =
review of their mib module work during the transition.

        *    Protocol Quality

The document was reviewed in detail by John Flick, and discussed by =
several other MIB experts. =20
A number of IEEE 802.1 WG members, including the vice chair, were =
involved in discussions.=20
The discussions and clarifications resulted in editorial changes in the =
document.=20
The MIB module proposed by this document is the SMIv2 version of RFC =
1493, which is=20
implemented by many vendors in the industry. Backwards compatibility has =
been maintained,=20
and most of the protocol data is identical between versions. It is =
expected that at least some of these vendors will implement the new =
version incarnated by this document, and other may=20
choose to implement it in the future, because of the growing acceptance =
of the IEEE 802.1 protocol in the industry. It is our belief that the =
document is at the appropriate quality=20
for consideration as proposed standard.=20


------=_NextPart_000_0286_01C4FDAE.34BCC5E0
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0286_01C4FDAE.34BCC5E0--





From bridge-mib-bounces@ietf.org  Thu Jan 20 08:22:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25953;
	Thu, 20 Jan 2005 08:22:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CrcVy-0006Li-Tb; Thu, 20 Jan 2005 08:38:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrcCY-0008A2-S7; Thu, 20 Jan 2005 08:18:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Crc2j-0005Y8-9l
	for bridge-mib@megatron.ietf.org; Thu, 20 Jan 2005 08:08:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24807
	for <bridge-mib@ietf.org>; Thu, 20 Jan 2005 08:08:07 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrcIO-0005us-8k
	for bridge-mib@ietf.org; Thu, 20 Jan 2005 08:24:21 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0KCweqm024886
	for <bridge-mib@ietf.org>; Thu, 20 Jan 2005 07:58:40 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j0KCwbqm024829
	for <bridge-mib@ietf.org>; Thu, 20 Jan 2005 07:58:38 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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: Thu, 20 Jan 2005 15:08:00 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038AA021@is0004avexu1.global.avaya.com>
Thread-Topic: [802.1] [802.1AB]: Problem with the lldpXdot1RemProtoVlanEntry
	table inde x
Thread-Index: AcT+xrfx14w2QYHsTJyxzVKBahpk5wAKUjRg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <bridge-mib@ietf.org>, "Mreview \(E-mail\)" <mreview@ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
Cc: Eelco Chaudron <echaudron@extremenetworks.com>
Subject: [Bridge-mib] FW: [802.1] [802.1AB]: Problem with the
	lldpXdot1RemProtoVlanEntry table inde x
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

The following question was asked on the IEEE 802.1 e-mail list. The =
referred index object lldpXdot1RemProtoVlanId has a syntax of =
Integer32(0|1..4094) - kind of similar to the TC once proposed by Bert.=20

Regards,

Dan



-----Original Message-----
From: IEEE 802.1 [mailto:hdk-0117.pgqfwd@ATT.NET]On Behalf Of Eelco =
Chaudron
Sent: 20 January, 2005 9:35 AM
To: STDS-802-1-L@LISTSERV.IEEE.ORG
Subject: [802.1] [802.1AB]: Problem with the lldpXdot1RemProtoVlanEntry =
table inde x


Hi All,

When implementing the dot1 extension MIB I was running into a problem =
with
the lldpXdot1RemProtoVlanTable.
The table has the following indexes:
  - lldpRemTimeMark
  - lldpRemLocalPortNum
  - lldpRemIndex
  - lldpXdot1RemProtoVlanId

The problem lies within the last index, lldpXdot1RemProtoVlanId. This =
can
have a value of zero, and would be causing an infinite loop when doing =
SNMP
getnext operations.

To my understanding a SNMP index can never have a value of zero, as it
indicates to SNMP to get the first value.

How would we hande this? For example not returning entries in the
lldpXdot1RemProtoVlanTable wich have a vlanid of zero? Or report the =
zero
values as 4096?

Regards,

Eelco

IEEE 802.1 list info: http://www.ieee802.org/1/email-pages/etkg1204.html

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


From bridge-mib-bounces@ietf.org  Thu Jan 20 10:33:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06897;
	Thu, 20 Jan 2005 10:33:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CreZ8-0001HY-6M; Thu, 20 Jan 2005 10:49:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CreH1-00073D-So; Thu, 20 Jan 2005 10:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CreBM-00056G-06
	for bridge-mib@megatron.ietf.org; Thu, 20 Jan 2005 10:25:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05830
	for <bridge-mib@ietf.org>; Thu, 20 Jan 2005 10:25:09 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CreR1-00015e-SL
	for bridge-mib@ietf.org; Thu, 20 Jan 2005 10:41:25 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0KFOZhb015813; 
	Thu, 20 Jan 2005 07:24:35 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0KFOc3Y011013;
	Thu, 20 Jan 2005 07:24:38 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0KFOc5E011007; Thu, 20 Jan 2005 07:24:38 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 20 Jan 2005 07:24:38 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Eelco Chaudron <echaudron@extremenetworks.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F038AA021@is0004avexu1.global.avaya.com>
Message-ID: <Pine.LNX.4.10.10501200705490.5097-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: "Mreview \(E-mail\)" <mreview@ops.ietf.org>, bridge-mib@ietf.org
Subject: [Bridge-mib] Re: FW: [802.1] [802.1AB]: Problem with the
 lldpXdot1RemProtoVlanEntry table index
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

On Thu, 20 Jan 2005, Eelco Chaudron wrote:
> When implementing the dot1 extension MIB I was running into a
> problem with the lldpXdot1RemProtoVlanTable.
> The table has the following indexes:
>   - lldpRemTimeMark
>   - lldpRemLocalPortNum
>   - lldpRemIndex
>   - lldpXdot1RemProtoVlanId
> 
> The problem lies within the last index, lldpXdot1RemProtoVlanId.
> This can have a value of zero, and would be causing an infinite
> loop when doing SNMP getnext operations.
> 
> To my understanding a SNMP index can never have a value of zero,
> as it indicates to SNMP to get the first value.

That is a misconception.  For the purpose of instance selection,
zero is a perfectly valid index value, and it is not treated
differently than any other value.

RFC 2578 recommends that index values be to 1 or greater except in
special situations.  However, it is acceptable to include zero in
the range of index values when it is semantically significant or
when it is used as the index value for a unique row with special
properties.

//cmh


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 01:57:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17758;
	Tue, 25 Jan 2005 01:57:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtKu8-0003TL-Mi; Tue, 25 Jan 2005 02:14:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtKcr-0008VR-9T; Tue, 25 Jan 2005 01:56:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtKbn-0008IK-An
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 01:55:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17677
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 01:55:25 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtKsR-0003Nr-Kg
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 02:12:40 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0P6sqQQ004853
	for <bridge-mib@ietf.org>; Mon, 24 Jan 2005 22:54:52 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0P6stZA005739;
	Mon, 24 Jan 2005 22:54:55 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0P6ssH5005734; Mon, 24 Jan 2005 22:54:55 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Mon, 24 Jan 2005 22:54:54 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
In-Reply-To: <E1CrNGX-0003v4-Ou@psg.com>
Message-ID: <Pine.LNX.4.10.10501231229370.15163-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Subject: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48

On Wed, 19 Jan 2005, David B Harrington wrote:
> Draft-iet-bridge-bridgemib-smiv2-09.txt has been submitted for
> advancement.
> It has already been reviewed by myself and Dan R. (WG chairs), and
> Juergen S. (the editor).
> We should have an independent MIB Doctor review of the document.
> Anybody willing to do this?

Here are the findings of a quick mini-review:

1.) I-D Boilerplate -- OK

2.) Abstract -- OK

3.) MIB Boilerplate -- OK

4.) Security Considerations Section -- OK

5.) IANA Considerations Section -- OK

6.) References -- OK

7.) Copyright Notices -- the one in the MIB module has a 2004
date.  That (and the LAST-UPDATED/REVISION clause dates) should
be brought up-to-date if another revision is spun;  if no other
things are corrected this can probably be left to the RFC Editor.

8.) IPR Notice -- OK

9.) Other issues -- a few editorial nits (and one item that I
consider important) were picked up:

(a) unexpanded acronym (PICS, in Sec. 3.1):

   Transmission Priority           These objects are not required
                                   as per the Pics Proforma and
                                   not considered useful.

If in the judgment of the editors the audience is likely to know
what a PICS Proforma is and that one would be found in IEEE Std
802.1D-1998 then maybe this is OK (it was not a problem for me).

(b) grammar:

3.1.2  The dot1dStp Subtree

   This subtree contains the objects that denote the bridge's state with
   respect to the Spanning Tree Protocol.  If a node does not
   implemented the Spanning Tree Protocol, this subtree will not be
   implemented.

s/If a node does not implemented/If a node does not implement/

(c) style:

3.1.3  The dot1dSr Subtree

   This subtree contains the objects that describe the entity's state
   with respect to source route bridging.  If source routing is not
   supported this subtree will not be implemented.  This subtree is
   applicable to source route only, and SRT bridges.  This subtree
   described in RFC 1525 [RFC1525] is applicable only to source route
   bridging.

The following replacement text is suggested:

   This subtree is described in RFC 1525 [RFC1525].  It contains the
   objects that describe the entity's state with respect to source route
   bridging.  If source routing is not supported then this subtree will
   not be implemented.

Or even:

   This subtree is described in RFC 1525 [RFC1525].

I like this last the best of all.

(d) inaccurate text:

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not been
   included in this MIB module because they overlap with objects in
   other MIB modules applicable to a bridge implementing this MIB.  In
   particular, it is assumed that a bridge implementing the BRIDGE-MIB
   module will also implement (at least) the 'system' subtree of the
   SNMPv2-MIB [RFC3418] and the 'interfaces' subtree of the IF-MIB
   [RFC2863].

Minimal fix:

s/'system' subtree/systemGroup/ here and in Section 3.2.1

s/'interfaces' subtree/ifGeneralInformationGroup/ here and
in Section 3.2.2

An alternate fix, to cater to old (RFC 1493) implementations,
would be to say in this section:

"In particular, it is assumed that a bridge implementing the
BRIDGE-MIB module will also implement (at a minimum) either
the 'system' and 'interface' subtrees of MIB-II [RFC1213] or
the systemGroup of the SNMPv2-MIB [RFC3418] and the
ifGeneralInformationGroup of the IF-MIB [RFC2863]."

with similar changes in 3.2.1 and 3.2.2.  Note that RFC 1213
would have to be added as a normative reference.

Note: I consider the above to be a MUST FIX, since otherwise
the specification of the prerequisites is just too vague.

10.) Technical content -- the extent of my technical review was
to go over the output from smidiff.  I noticed a couple of things:

(a) the following is (formally) a violation of the revision rules
in RFC 2578 Section 10, since it might result in a compilation
failure of a module that IMPORTS MacAdress from BRIDGE-MIB instead
of from SNMPv2-TC:

/usr/local/share/mibs/ietf/BRIDGE-MIB:17 [1] {type-removed} type
`MacAddress' has been deleted

An RFC content search revealed that all of the published IETF MIB
modules (other than BRIDGE-MIB) that use MacAddesss actually
import it from SNMPv2-TC.  However, that might not be true of
enterprise MIB modules or of MIB modules maintained by other SDOs,
and there is no effective way I know of to search for such usage.

So I wonder if it might not have been better to have left the
definition in place, but to make its status 'deprecated' and
have text pointing potential users to the version in SNMPv2-TC.

I won't squawk if the WG wants to leave this as is.

(b) also, the following changes violate our MIB review guidelines:

BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
`transparent-only' changed to `transparentOnly' at type used in
`dot1dBaseType'
BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
`sourceroute-only' changed to `sourcerouteOnly' at type used in in
`dot1dBaseType'

See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
bullet on p. 29.  The WG will have to judge for itself whether the
issue raised there applies in this case (I think it does, but I am
not interested in picking a fight if the WG disagrees).  Note that
if this change is backed out then smilint will complain about the
hyphens (as it does about legacy read-only index columns).

(c) As a result of 9(d) above, I noticed that the compliance
statements do not spell out the prerequisites, as is has been
done in some recent MIB modules.  It might be worthwhile to
consider doing that here.  For bridgeCompliance1493 it would be
necessary to specifiy this information in the DESCRIPTION clause
(since, presumably, that one would call out the old MIB-II
subtrees).  For bridgeComplianceXXXX one could IMPORT the
systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
from IF-MIB and list them in the MANDATORY-GROUPS clause.

Note:  IMHO, this is just a nice-to-have.  Spelling out the
prerequisites in the text of Section 3 is good enough for me.
The OPS AD for NM has been know to disagree with me on this :-)

Mike Heard


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 03:30:57 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09426;
	Tue, 25 Jan 2005 03:30:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtMMu-0006jv-6f; Tue, 25 Jan 2005 03:48:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtM4n-0000RS-Db; Tue, 25 Jan 2005 03:29:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtLwE-0006xd-4T
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 03:20:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08422
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 03:20:34 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtMCr-0006FH-Pn
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 03:37:50 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 32903D45B;
	Tue, 25 Jan 2005 09:19:59 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 06086-04; Tue, 25 Jan 2005 09:19:57 +0100 (CET)
Received: from james (I964d.i.pppool.de [85.73.150.77])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 44EE8B88A;
	Tue, 25 Jan 2005 09:19:57 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CtLvX-00015K-F0; Tue, 25 Jan 2005 09:19:55 +0100
Date: Tue, 25 Jan 2005 09:19:55 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050125081955.GA4039@james>
Mail-Followup-To: "C. M. Heard" <heard@pobox.com>,
	"Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
References: <E1CrNGX-0003v4-Ou@psg.com>
	<Pine.LNX.4.10.10501231229370.15163-100000@shell4.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.10.10501231229370.15163-100000@shell4.bayarea.net>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34
Cc: "Bridge-Mib \(E-mail\)" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80

On Mon, Jan 24, 2005 at 10:54:54PM -0800, C. M. Heard wrote:
 
> Here are the findings of a quick mini-review:

Thanks Mike. Let me briefly react to your comments.
 
> 1.) I-D Boilerplate -- OK
> 
> 2.) Abstract -- OK
> 
> 3.) MIB Boilerplate -- OK
> 
> 4.) Security Considerations Section -- OK
> 
> 5.) IANA Considerations Section -- OK
> 
> 6.) References -- OK
> 
> 7.) Copyright Notices -- the one in the MIB module has a 2004
> date.  That (and the LAST-UPDATED/REVISION clause dates) should
> be brought up-to-date if another revision is spun;  if no other
> things are corrected this can probably be left to the RFC Editor.

I probably need to learn how to let xml2rfc put in the right year
automatically. ;-)
 
> 8.) IPR Notice -- OK
> 
> 9.) Other issues -- a few editorial nits (and one item that I
> consider important) were picked up:
> 
> (a) unexpanded acronym (PICS, in Sec. 3.1):
> 
>    Transmission Priority           These objects are not required
>                                    as per the Pics Proforma and
>                                    not considered useful.
> 
> If in the judgment of the editors the audience is likely to know
> what a PICS Proforma is and that one would be found in IEEE Std
> 802.1D-1998 then maybe this is OK (it was not a problem for me).

Would be no problem to spell out Protocol Implementation Conformance
Statement (PICS) or to simply add a reference to 802.1D-1998 if
someone confirms that this document actually contains the PICS
referred to here. Can someone please check?
 
> (b) grammar:
> 
> 3.1.2  The dot1dStp Subtree
> 
>    This subtree contains the objects that denote the bridge's state with
>    respect to the Spanning Tree Protocol.  If a node does not
>    implemented the Spanning Tree Protocol, this subtree will not be
>    implemented.
> 
> s/If a node does not implemented/If a node does not implement/

ack

> (c) style:
> 
> 3.1.3  The dot1dSr Subtree
> 
>    This subtree contains the objects that describe the entity's state
>    with respect to source route bridging.  If source routing is not
>    supported this subtree will not be implemented.  This subtree is
>    applicable to source route only, and SRT bridges.  This subtree
>    described in RFC 1525 [RFC1525] is applicable only to source route
>    bridging.
> 
> The following replacement text is suggested:
> 
>    This subtree is described in RFC 1525 [RFC1525].  It contains the
>    objects that describe the entity's state with respect to source route
>    bridging.  If source routing is not supported then this subtree will
>    not be implemented.
> 
> Or even:
> 
>    This subtree is described in RFC 1525 [RFC1525].
> 
> I like this last the best of all.

Either if find with me. The second is probably more user friendly while
the last one is surely the least problematic one.
 
> (d) inaccurate text:
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects have not been
>    included in this MIB module because they overlap with objects in
>    other MIB modules applicable to a bridge implementing this MIB.  In
>    particular, it is assumed that a bridge implementing the BRIDGE-MIB
>    module will also implement (at least) the 'system' subtree of the
>    SNMPv2-MIB [RFC3418] and the 'interfaces' subtree of the IF-MIB
>    [RFC2863].
> 
> Minimal fix:
> 
> s/'system' subtree/systemGroup/ here and in Section 3.2.1
> 
> s/'interfaces' subtree/ifGeneralInformationGroup/ here and
> in Section 3.2.2
> 
> An alternate fix, to cater to old (RFC 1493) implementations,
> would be to say in this section:
> 
> "In particular, it is assumed that a bridge implementing the
> BRIDGE-MIB module will also implement (at a minimum) either
> the 'system' and 'interface' subtrees of MIB-II [RFC1213] or
> the systemGroup of the SNMPv2-MIB [RFC3418] and the
> ifGeneralInformationGroup of the IF-MIB [RFC2863]."
> 
> with similar changes in 3.2.1 and 3.2.2.  Note that RFC 1213
> would have to be added as a normative reference.
> 
> Note: I consider the above to be a MUST FIX, since otherwise
> the specification of the prerequisites is just too vague.

This text has been vague in RFC 1493 and I just tried to keep it 
vague. Note that s/'system' subtree/systemGroup/ does not really 
work since the systemGroup includes objects that did not really 
exit when RFC 1493 was published. I also prefer to avoid the 
introduction of a normative reference to [RFC1213]. So if you 
want clarity, the right approach is IMHO to simply list the 
system objects that did exist when RFC 1493 was published.
(We could even define this formally in the compliance statement 
by importing the objects and defining a suitable group. The 
IETF so far to my knowledge has never done formal dependency 
definitions in this way.)

Note that the some reasoning applies to the 'interfaces' subtree.
I again doubt that ifGeneralInformationGroup is exactly what was
meant when RFC 1493 was published. If we dive deeper, then we
have to note that things like ifInNUcastPkts, which were current
definitions at the time RFC 1493 was published, are now deprecated.
So do we document what was meant by RFC 1493 or do we document 
what makes sense with our current interpretation of the IF-MIB? 
Since we now go for Proposed rather Standard, we might actually 
do the later. But still, we should be careful since we have lots 
of deployed implementations of this MIB.
 
> 10.) Technical content -- the extent of my technical review was
> to go over the output from smidiff.  I noticed a couple of things:
> 
> (a) the following is (formally) a violation of the revision rules
> in RFC 2578 Section 10, since it might result in a compilation
> failure of a module that IMPORTS MacAdress from BRIDGE-MIB instead
> of from SNMPv2-TC:
> 
> /usr/local/share/mibs/ietf/BRIDGE-MIB:17 [1] {type-removed} type
> `MacAddress' has been deleted
> 
> An RFC content search revealed that all of the published IETF MIB
> modules (other than BRIDGE-MIB) that use MacAddesss actually
> import it from SNMPv2-TC.  However, that might not be true of
> enterprise MIB modules or of MIB modules maintained by other SDOs,
> and there is no effective way I know of to search for such usage.
> 
> So I wonder if it might not have been better to have left the
> definition in place, but to make its status 'deprecated' and
> have text pointing potential users to the version in SNMPv2-TC.
> 
> I won't squawk if the WG wants to leave this as is.

The formally correct solution would have been to keep the MacAddress
definition, changing the status to obsolete and to import the
MacAddress from SNMPv2-TC and use it throughout the MIB module.
Since both TCs have the same name, one would have to use module
qualified names (SNMPv2-TC.MacAddress). While this is legal and
would formally precisely say what we are trying to achieve, doing
so very likely breaks a number of simple minded MIB parsers...
 
> (b) also, the following changes violate our MIB review guidelines:
> 
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `transparent-only' changed to `transparentOnly' at type used in
> `dot1dBaseType'
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> `dot1dBaseType'
> 
> See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> bullet on p. 29.  The WG will have to judge for itself whether the
> issue raised there applies in this case (I think it does, but I am
> not interested in picking a fight if the WG disagrees).  Note that
> if this change is backed out then smilint will complain about the
> hyphens (as it does about legacy read-only index columns).

CLR #1: hyphens are not allowed in named numbers labels
CLR #2: you should not change named number labels

So which one ranks higher? I can go both ways. But whatever we do,
it won't be perfect.
 
> (c) As a result of 9(d) above, I noticed that the compliance
> statements do not spell out the prerequisites, as is has been
> done in some recent MIB modules.  It might be worthwhile to
> consider doing that here.  For bridgeCompliance1493 it would be
> necessary to specifiy this information in the DESCRIPTION clause
> (since, presumably, that one would call out the old MIB-II
> subtrees).  For bridgeComplianceXXXX one could IMPORT the
> systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
> from IF-MIB and list them in the MANDATORY-GROUPS clause.

As I wrote above, simply using the systemGroup and the
ifGeneralInformationGroup may not cut it. Thers is also the
ifFixedLengthGroup and the ifPacketGroup that I think applies
and conditionally the ifHCFixedLengthGroup and ifHCPacketGroup
and all the other material in RFC 2863. Can we not simply
request that implementations must comply to ifCompliance3?
(There is unfortunately no SMI construct to reference another
compliance statement.)

/js
 
-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Tue Jan 25 04:58:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16612;
	Tue, 25 Jan 2005 04:58:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtNjP-0001e7-Vh; Tue, 25 Jan 2005 05:15:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtNRa-0007SX-0A; Tue, 25 Jan 2005 04:57:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtNQy-0007Km-IB
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 04:56:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15774
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 04:56:26 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtNhd-0001RN-9Y
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 05:13:41 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0P9toQQ027355
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 01:55:50 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0P9tsIQ006885;
	Tue, 25 Jan 2005 01:55:54 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0P9trBo006881; Tue, 25 Jan 2005 01:55:53 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 Jan 2005 01:55:53 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050125081955.GA4039@james>
Message-ID: <Pine.LNX.4.10.10501250056270.27738-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48

On Tue, 25 Jan 2005, Juergen Schoenwaelder wrote:
> > (d) inaccurate text:
> > 
> > 3.2  Relationship to Other MIB Modules
> > 
> >    As described above, some IEEE 802.1D management objects have not been
> >    included in this MIB module because they overlap with objects in
> >    other MIB modules applicable to a bridge implementing this MIB.  In
> >    particular, it is assumed that a bridge implementing the BRIDGE-MIB
> >    module will also implement (at least) the 'system' subtree of the
> >    SNMPv2-MIB [RFC3418] and the 'interfaces' subtree of the IF-MIB
> >    [RFC2863].
> > 
> > Minimal fix:
> > 
> > s/'system' subtree/systemGroup/ here and in Section 3.2.1
> > 
> > s/'interfaces' subtree/ifGeneralInformationGroup/ here and
> > in Section 3.2.2
> > 
> > An alternate fix, to cater to old (RFC 1493) implementations,
> > would be to say in this section:
> > 
> > "In particular, it is assumed that a bridge implementing the
> > BRIDGE-MIB module will also implement (at a minimum) either
> > the 'system' and 'interface' subtrees of MIB-II [RFC1213] or
> > the systemGroup of the SNMPv2-MIB [RFC3418] and the
> > ifGeneralInformationGroup of the IF-MIB [RFC2863]."
> > 
> > with similar changes in 3.2.1 and 3.2.2.  Note that RFC 1213
> > would have to be added as a normative reference.
> > 
> > Note: I consider the above to be a MUST FIX, since otherwise
> > the specification of the prerequisites is just too vague.
> 
> This text has been vague in RFC 1493 and I just tried to keep it 
> vague. Note that s/'system' subtree/systemGroup/ does not really 
> work since the systemGroup includes objects that did not really 
> exit when RFC 1493 was published. I also prefer to avoid the 
> introduction of a normative reference to [RFC1213]. So if you 
> want clarity, the right approach is IMHO to simply list the 
> system objects that did exist when RFC 1493 was published.
> (We could even define this formally in the compliance statement 
> by importing the objects and defining a suitable group. The 
> IETF so far to my knowledge has never done formal dependency 
> definitions in this way.)

Actually that is not legal;  conformance groups must be defined in
the same module with the objects or notifications that they contain.

> Note that the some reasoning applies to the 'interfaces' subtree.
> I again doubt that ifGeneralInformationGroup is exactly what was
> meant when RFC 1493 was published. If we dive deeper, then we
> have to note that things like ifInNUcastPkts, which were current
> definitions at the time RFC 1493 was published, are now deprecated.
> So do we document what was meant by RFC 1493 or do we document 
> what makes sense with our current interpretation of the IF-MIB? 
> Since we now go for Proposed rather Standard, we might actually 
> do the later. But still, we should be careful since we have lots 
> of deployed implementations of this MIB.

My problems are not just the vagueness of Section 3.2, but with the
outright inaccuracy of and 3.2.2, wrought by just changing the
reference from RFC 1213 to RFC 2863.  Specifically, 3.2.2 says:

   In the Interfaces Group MIB [RFC2863], the 'interfaces' subtree is
   defined as being mandatory for all systems and contains information
   on an entity's interfaces, where each interface is thought of as
   being attached to a `subnetwork'. 

As written that is false.  It would be true, however, if one
substituted "ifGeneralInformationGroup" in place of "'interfaces'
subtree", as that group is the only one that is unconditionally
mandatory for all interface types.

3.2.1 says:

   In the SNMPv2-MIB [RFC3418], the 'system' subtree is defined as being
   mandatory for all systems.  Thus, those objects apply to the entity
   as a whole irrespective of whether the entity's sole functionality is
   bridging, or whether bridging is only a subset of the entity's
   functionality.

What RFC 3418 actually says is that the systemGroup defines objects
that are common to all managed systems.  In this case it so happens
that the systemGroup contains all the objects in the 'system'
subtree, and no others.

In defense of my "minimal fix" proposal, note that (a) the two
groups do include all the objects from SNMPv2-MIB and IF-MIB that
are mentioned in Section 3.1, and (b) it is the simplest way I can
see to fix the inaccurate text in Section 3.2.2.

> > 10.) Technical content -- the extent of my technical review was
> > to go over the output from smidiff.  I noticed a couple of things:
...
> > (b) also, the following changes violate our MIB review guidelines:
> > 
> > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > `transparent-only' changed to `transparentOnly' at type used in
> > `dot1dBaseType'
> > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> > `dot1dBaseType'
> > 
> > See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> > bullet on p. 29.  The WG will have to judge for itself whether the
> > issue raised there applies in this case (I think it does, but I am
> > not interested in picking a fight if the WG disagrees).  Note that
> > if this change is backed out then smilint will complain about the
> > hyphens (as it does about legacy read-only index columns).
> 
> CLR #1: hyphens are not allowed in named numbers labels
> CLR #2: you should not change named number labels
> 
> So which one ranks higher? I can go both ways. But whatever we do,
> it won't be perfect.

#1 is a CLR since it is there because people didn't like hyphens,
even though they did no harm (proof: SMIv1 was fine with them).

#2 is not a CLR since it is there to keep people from making changes
that cause existing MIB modules not to compile when a new rev is
introduced.

So, #2 trumps #1.

And in this case, #1 does not even apply:  RFC 2578 grants an
exemption to the no-hyphen rule for MIB modules that are translated
from SMIv1.

But as I said, I will not pick a fight about this.

> > (c) As a result of 9(d) above, I noticed that the compliance
> > statements do not spell out the prerequisites, as is has been
> > done in some recent MIB modules.  It might be worthwhile to
> > consider doing that here.  For bridgeCompliance1493 it would be
> > necessary to specifiy this information in the DESCRIPTION clause
> > (since, presumably, that one would call out the old MIB-II
> > subtrees).  For bridgeComplianceXXXX one could IMPORT the
> > systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
> > from IF-MIB and list them in the MANDATORY-GROUPS clause.
> 
> As I wrote above, simply using the systemGroup and the
> ifGeneralInformationGroup may not cut it. Thers is also the
> ifFixedLengthGroup and the ifPacketGroup that I think applies
> and conditionally the ifHCFixedLengthGroup and ifHCPacketGroup
> and all the other material in RFC 2863. Can we not simply
> request that implementations must comply to ifCompliance3?
> (There is unfortunately no SMI construct to reference another
> compliance statement.)

There is no formal construct, but you can do so with the DESCRIPTION
clause.  See the compliance statements in RFCs 3535 and 3536 for
some examples.  Both of those require that implementations support
ifCompliance3.  And for the systemGroup stuff, you could IMPORT it
from SNMPv2-MIB and mention it in the MANDATORY-GROUPS clause.

Mike


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 05:04:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18712;
	Tue, 25 Jan 2005 05:04:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtNpH-000245-50; Tue, 25 Jan 2005 05:21:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtNVg-0007yx-Bk; Tue, 25 Jan 2005 05:01:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtNV4-0007ng-L6
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 05:00:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17929
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 05:00:40 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtNlj-0001nL-Sl
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 05:17:56 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0PA09QQ028103
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 02:00:09 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0PA0Dos007545
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 02:00:13 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0PA0Coo007542
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 02:00:13 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 Jan 2005 02:00:12 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <Pine.LNX.4.10.10501250056270.27738-100000@shell4.bayarea.net>
Message-ID: <Pine.LNX.4.10.10501250157050.7030-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

On Tue, 25 Jan 2005, C. M. Heard wrote:
> See the compliance statements in RFCs 3535 and 3536

I meant to say RFCs 3635 and 3636.

//cmh


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 05:10:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19144;
	Tue, 25 Jan 2005 05:10:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtNvI-0002Go-Ua; Tue, 25 Jan 2005 05:27:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtNc0-0000ld-Sx; Tue, 25 Jan 2005 05:07:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtNXM-0000DP-2X
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 05:03:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18624
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 05:02:57 -0500 (EST)
Received: from columba.eur.3com.com ([161.71.171.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtNnx-0001z6-BJ
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 05:20:14 -0500
Received: from toucana.eur.3com.com (eurelay.eur.3com.com [140.204.220.50])
	by columba.eur.3com.com  with ESMTP id j0PA4tuQ014023;
	Tue, 25 Jan 2005 10:04:55 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206])
	by toucana.eur.3com.com  with SMTP id j0PA7VAI006717;
	Tue, 25 Jan 2005 10:07:32 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998))
	id 80256F94.0037654F ; Tue, 25 Jan 2005 10:05:04 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: j.schoenwaelder@iu-bremen.de
Message-ID: <80256F94.00376339.00@notesmta.eur.3com.com>
Date: Tue, 25 Jan 2005 10:02:38 +0000
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: "C. M. Heard" <heard@pobox.com>,
        "Bridge-Mib \(E-mail\)" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22




> > (a) unexpanded acronym (PICS, in Sec. 3.1):
> >
> >    Transmission Priority           These objects are not required
> >                                    as per the Pics Proforma and
> >                                    not considered useful.
> >
> > If in the judgment of the editors the audience is likely to know
> > what a PICS Proforma is and that one would be found in IEEE Std
> > 802.1D-1998 then maybe this is OK (it was not a problem for me).
>
> Would be no problem to spell out Protocol Implementation Conformance
> Statement (PICS) or to simply add a reference to 802.1D-1998 if
> someone confirms that this document actually contains the PICS
> referred to here. Can someone please check?

The PICS is in IEEE Std 802.1D-1998 Annex A

Les...



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


From bridge-mib-bounces@ietf.org  Tue Jan 25 05:47:29 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21683;
	Tue, 25 Jan 2005 05:47:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtOV4-0003WT-Ao; Tue, 25 Jan 2005 06:04:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtODG-0006DE-K9; Tue, 25 Jan 2005 05:46:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtO93-0005Kf-77
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 05:42:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21180
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 05:41:58 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtOPj-0003Gv-PJ
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 05:59:16 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 14A56D8CD;
	Tue, 25 Jan 2005 11:41:29 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 13537-08; Tue, 25 Jan 2005 11:41:27 +0100 (CET)
Received: from james (unknown [10.50.248.235])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id C606B9C2C;
	Tue, 25 Jan 2005 11:41:27 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CtO8V-0000f9-UP; Tue, 25 Jan 2005 11:41:27 +0100
Date: Tue, 25 Jan 2005 11:41:27 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050125104127.GA2413@james>
Mail-Followup-To: "C. M. Heard" <heard@pobox.com>,
	"Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
References: <20050125081955.GA4039@james>
	<Pine.LNX.4.10.10501250056270.27738-100000@shell4.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.10.10501250056270.27738-100000@shell4.bayarea.net>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: "Bridge-Mib \(E-mail\)" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc

On Tue, Jan 25, 2005 at 01:55:53AM -0800, C. M. Heard wrote:

> > This text has been vague in RFC 1493 and I just tried to keep it 
> > vague. Note that s/'system' subtree/systemGroup/ does not really 
> > work since the systemGroup includes objects that did not really 
> > exit when RFC 1493 was published. I also prefer to avoid the 
> > introduction of a normative reference to [RFC1213]. So if you 
> > want clarity, the right approach is IMHO to simply list the 
> > system objects that did exist when RFC 1493 was published.
> > (We could even define this formally in the compliance statement 
> > by importing the objects and defining a suitable group. The 
> > IETF so far to my knowledge has never done formal dependency 
> > definitions in this way.)
> 
> Actually that is not legal;  conformance groups must be defined in
> the same module with the objects or notifications that they contain.

You are right.
 
> > Note that the some reasoning applies to the 'interfaces' subtree.
> > I again doubt that ifGeneralInformationGroup is exactly what was
> > meant when RFC 1493 was published. If we dive deeper, then we
> > have to note that things like ifInNUcastPkts, which were current
> > definitions at the time RFC 1493 was published, are now deprecated.
> > So do we document what was meant by RFC 1493 or do we document 
> > what makes sense with our current interpretation of the IF-MIB? 
> > Since we now go for Proposed rather Standard, we might actually 
> > do the later. But still, we should be careful since we have lots 
> > of deployed implementations of this MIB.
> 
> My problems are not just the vagueness of Section 3.2, but with the
> outright inaccuracy of and 3.2.2, wrought by just changing the
> reference from RFC 1213 to RFC 2863.  Specifically, 3.2.2 says:
> 
>    In the Interfaces Group MIB [RFC2863], the 'interfaces' subtree is
>    defined as being mandatory for all systems and contains information
>    on an entity's interfaces, where each interface is thought of as
>    being attached to a `subnetwork'. 
> 
> As written that is false.  It would be true, however, if one
> substituted "ifGeneralInformationGroup" in place of "'interfaces'
> subtree", as that group is the only one that is unconditionally
> mandatory for all interface types.
> 
> 3.2.1 says:
> 
>    In the SNMPv2-MIB [RFC3418], the 'system' subtree is defined as being
>    mandatory for all systems.  Thus, those objects apply to the entity
>    as a whole irrespective of whether the entity's sole functionality is
>    bridging, or whether bridging is only a subset of the entity's
>    functionality.
> 
> What RFC 3418 actually says is that the systemGroup defines objects
> that are common to all managed systems.  In this case it so happens
> that the systemGroup contains all the objects in the 'system'
> subtree, and no others.
> 
> In defense of my "minimal fix" proposal, note that (a) the two
> groups do include all the objects from SNMPv2-MIB and IF-MIB that
> are mentioned in Section 3.1, and (b) it is the simplest way I can
> see to fix the inaccurate text in Section 3.2.2.

See my conclusion at the end of this message.

> > > 10.) Technical content -- the extent of my technical review was
> > > to go over the output from smidiff.  I noticed a couple of things:
> ...
> > > (b) also, the following changes violate our MIB review guidelines:
> > > 
> > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > `transparent-only' changed to `transparentOnly' at type used in
> > > `dot1dBaseType'
> > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> > > `dot1dBaseType'
> > > 
> > > See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> > > bullet on p. 29.  The WG will have to judge for itself whether the
> > > issue raised there applies in this case (I think it does, but I am
> > > not interested in picking a fight if the WG disagrees).  Note that
> > > if this change is backed out then smilint will complain about the
> > > hyphens (as it does about legacy read-only index columns).
> > 
> > CLR #1: hyphens are not allowed in named numbers labels
> > CLR #2: you should not change named number labels
> > 
> > So which one ranks higher? I can go both ways. But whatever we do,
> > it won't be perfect.
> 
> #1 is a CLR since it is there because people didn't like hyphens,
> even though they did no harm (proof: SMIv1 was fine with them).
> 
> #2 is not a CLR since it is there to keep people from making changes
> that cause existing MIB modules not to compile when a new rev is
> introduced.
> 
> So, #2 trumps #1.
> 
> And in this case, #1 does not even apply:  RFC 2578 grants an
> exemption to the no-hyphen rule for MIB modules that are translated
> from SMIv1.
> 
> But as I said, I will not pick a fight about this.

I certainly do not want to discuss the merrit of these rules here. I
can life either way. But it would be good if the conclusion how we
deal with this case could be recorded so that we do things consistently
the next time this pops up.
 
> > > (c) As a result of 9(d) above, I noticed that the compliance
> > > statements do not spell out the prerequisites, as is has been
> > > done in some recent MIB modules.  It might be worthwhile to
> > > consider doing that here.  For bridgeCompliance1493 it would be
> > > necessary to specifiy this information in the DESCRIPTION clause
> > > (since, presumably, that one would call out the old MIB-II
> > > subtrees).  For bridgeComplianceXXXX one could IMPORT the
> > > systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
> > > from IF-MIB and list them in the MANDATORY-GROUPS clause.
> > 
> > As I wrote above, simply using the systemGroup and the
> > ifGeneralInformationGroup may not cut it. Thers is also the
> > ifFixedLengthGroup and the ifPacketGroup that I think applies
> > and conditionally the ifHCFixedLengthGroup and ifHCPacketGroup
> > and all the other material in RFC 2863. Can we not simply
> > request that implementations must comply to ifCompliance3?
> > (There is unfortunately no SMI construct to reference another
> > compliance statement.)
> 
> There is no formal construct, but you can do so with the DESCRIPTION
> clause.  See the compliance statements in RFCs 3535 and 3536 for
> some examples.  Both of those require that implementations support
> ifCompliance3.  And for the systemGroup stuff, you could IMPORT it
> from SNMPv2-MIB and mention it in the MANDATORY-GROUPS clause.

So from this, I conclude that we probably want to add the following 
to the compliance statements:

	Note that compliance with this MIB module requires
	compliance with the ifCompliance3 MODULE-COMPLIANCE 
	statement of the IF-MIB (RFC2863) and compliance with
	the snmpBasicComplianceRev2 MODULE-COMPLIANCE of the
	SNMPv2-MIB (RFC3418).

Section 3.2.1 would be changed to the following:

	Implementations of the BRIDGE-MIB must comply with the
	snmpBasicComplianceRev2 MODULE-COMPLIANCE statement in 
	the SNMPv2-MIB [RFC2863].

Section 3.2.2 first paragraph would be changed to the following:

	Implementations of the BRIDGE-MIB must comply with the
	ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB
	[RFC2863]. In the IF-MIB terminology, an interface is
	thought of as being attached to a `subnetwork'.  (Note 
	that this term is not to be confused with `subnet' which 
	refers to an addressing partitioning scheme used in the 
	Internet suite of protocols.) The term 'segment' is used 
	in this memo to refer to such a subnetwork, whether it 
	be an Ethernet segment, a 'ring', a WAN link, or even an
        X.25 virtual circuit.

We may want to add after the first sentence (although this should 
be clear from reading the IF-MIB):

	This includes mandatory support of the ifFixedLengthGroup,
	the ifPacketGroup, and the ifCounterDiscontinuityGroup of
	the IF-MIB [RFC2863], which are conditionally mandatory
	in the ifCompliance3 statement.

Searching for the word subnetwork in the document, I found that
it is used in the description of dot1dTpLearnedEntryDiscards
and to be consistent, this should probably have been segment
rather than subnetwork.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Tue Jan 25 06:55:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26505;
	Tue, 25 Jan 2005 06:55:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtPYX-0005yS-07; Tue, 25 Jan 2005 07:12:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtPFx-0003Ho-CB; Tue, 25 Jan 2005 06:53:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtPAg-0001mI-Ac
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 06:47:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26013
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 06:47:43 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtPRM-0005hC-Ub
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 07:05:02 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 7FCC5D45B;
	Tue, 25 Jan 2005 12:47:13 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 17492-07; Tue, 25 Jan 2005 12:47:12 +0100 (CET)
Received: from james (unknown [10.50.248.235])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id A4C0FB88A;
	Tue, 25 Jan 2005 12:47:12 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CtPA7-0000nE-24; Tue, 25 Jan 2005 12:47:11 +0100
Date: Tue, 25 Jan 2005 12:47:11 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Les Bell <Les_Bell@eur.3com.com>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050125114711.GC2946@james>
Mail-Followup-To: Les Bell <Les_Bell@eur.3com.com>,
	"C. M. Heard" <heard@pobox.com>,
	"Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
References: <80256F94.00376339.00@notesmta.eur.3com.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <80256F94.00376339.00@notesmta.eur.3com.com>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: "C. M. Heard" <heard@pobox.com>,
        "Bridge-Mib \(E-mail\)" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

On Tue, Jan 25, 2005 at 10:02:38AM +0000, Les Bell wrote:
 
> > > (a) unexpanded acronym (PICS, in Sec. 3.1):
> > >
> > >    Transmission Priority           These objects are not required
> > >                                    as per the Pics Proforma and
> > >                                    not considered useful.
> > >
> > > If in the judgment of the editors the audience is likely to know
> > > what a PICS Proforma is and that one would be found in IEEE Std
> > > 802.1D-1998 then maybe this is OK (it was not a problem for me).
> >
> > Would be no problem to spell out Protocol Implementation Conformance
> > Statement (PICS) or to simply add a reference to 802.1D-1998 if
> > someone confirms that this document actually contains the PICS
> > referred to here. Can someone please check?
> 
> The PICS is in IEEE Std 802.1D-1998 Annex A

So then my proposed edit would be:

Transmission Priority           These objects are not required                  
                                as per the Pics Proforma contained              
				in [IEEE8021D] and not considered 
		                useful. 

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Tue Jan 25 08:40:59 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03447;
	Tue, 25 Jan 2005 08:40:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtRCz-0001GY-6s; Tue, 25 Jan 2005 08:58:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtQpe-0007nS-2G; Tue, 25 Jan 2005 08:34:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtQf1-0006bx-11
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 08:23:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02557
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 08:23:09 -0500 (EST)
Message-Id: <200501251323.IAA02557@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtQvj-0000g0-7I
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 08:40:27 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc12) with SMTP
	id <2005012513223401400hhrefe>; Tue, 25 Jan 2005 13:22:34 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Tue, 25 Jan 2005 08:22:31 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501231229370.15163-100000@shell4.bayarea.net>
Thread-Index: AcUCqxevK6ZXG+oQT9KWDqxjoFCoswANPmmw
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Content-Transfer-Encoding: 7bit

Hi,

Let me jump in as chair.

It is important to realize that we have already been through WGLC and
submitted the document for advancement, and cannot make any changes to
the document without "unsubmitting" it. We cannot publish a new
revision for minor changes.

I asked for an independent MIB Doctor review to ensure that there is
nothing **broken** in this document; given that it has been reviewed
by three of four MIB Doctors already, I didn't think it very likely we
missed anything, but an extra pair of eyes doesn't hurt, and reassures
the IESG it has been independently reviewed.

The editorial nits can probably be handled during the author 48-hour
period, but if they are not critical, we will probably just let it go
through as being "good enough".

If there are serious issues, I will alert the AD to include them in
the AD/IESG review and we can fix them during the advancement process
(or "unsubmit" the document an dtry again).

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Tuesday, January 25, 2005 1:55 AM
> To: Bridge-Mib (E-mail)
> Subject: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> On Wed, 19 Jan 2005, David B Harrington wrote:
> > Draft-iet-bridge-bridgemib-smiv2-09.txt has been submitted for
> > advancement.
> > It has already been reviewed by myself and Dan R. (WG chairs), and
> > Juergen S. (the editor).
> > We should have an independent MIB Doctor review of the document.
> > Anybody willing to do this?
> 
> Here are the findings of a quick mini-review:
> 
> 1.) I-D Boilerplate -- OK
> 
> 2.) Abstract -- OK
> 
> 3.) MIB Boilerplate -- OK
> 
> 4.) Security Considerations Section -- OK
> 
> 5.) IANA Considerations Section -- OK
> 
> 6.) References -- OK
> 
> 7.) Copyright Notices -- the one in the MIB module has a 2004
> date.  That (and the LAST-UPDATED/REVISION clause dates) should
> be brought up-to-date if another revision is spun;  if no other
> things are corrected this can probably be left to the RFC Editor.
> 
> 8.) IPR Notice -- OK
> 
> 9.) Other issues -- a few editorial nits (and one item that I
> consider important) were picked up:
> 
> (a) unexpanded acronym (PICS, in Sec. 3.1):
> 
>    Transmission Priority           These objects are not required
>                                    as per the Pics Proforma and
>                                    not considered useful.
> 
> If in the judgment of the editors the audience is likely to know
> what a PICS Proforma is and that one would be found in IEEE Std
> 802.1D-1998 then maybe this is OK (it was not a problem for me).
> 
> (b) grammar:
> 
> 3.1.2  The dot1dStp Subtree
> 
>    This subtree contains the objects that denote the bridge's 
> state with
>    respect to the Spanning Tree Protocol.  If a node does not
>    implemented the Spanning Tree Protocol, this subtree will not be
>    implemented.
> 
> s/If a node does not implemented/If a node does not implement/
> 
> (c) style:
> 
> 3.1.3  The dot1dSr Subtree
> 
>    This subtree contains the objects that describe the entity's
state
>    with respect to source route bridging.  If source routing is not
>    supported this subtree will not be implemented.  This subtree is
>    applicable to source route only, and SRT bridges.  This subtree
>    described in RFC 1525 [RFC1525] is applicable only to source
route
>    bridging.
> 
> The following replacement text is suggested:
> 
>    This subtree is described in RFC 1525 [RFC1525].  It contains the
>    objects that describe the entity's state with respect to 
> source route
>    bridging.  If source routing is not supported then this 
> subtree will
>    not be implemented.
> 
> Or even:
> 
>    This subtree is described in RFC 1525 [RFC1525].
> 
> I like this last the best of all.
> 
> (d) inaccurate text:
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects 
> have not been
>    included in this MIB module because they overlap with objects in
>    other MIB modules applicable to a bridge implementing this MIB.
In
>    particular, it is assumed that a bridge implementing the
BRIDGE-MIB
>    module will also implement (at least) the 'system' subtree of the
>    SNMPv2-MIB [RFC3418] and the 'interfaces' subtree of the IF-MIB
>    [RFC2863].
> 
> Minimal fix:
> 
> s/'system' subtree/systemGroup/ here and in Section 3.2.1
> 
> s/'interfaces' subtree/ifGeneralInformationGroup/ here and
> in Section 3.2.2
> 
> An alternate fix, to cater to old (RFC 1493) implementations,
> would be to say in this section:
> 
> "In particular, it is assumed that a bridge implementing the
> BRIDGE-MIB module will also implement (at a minimum) either
> the 'system' and 'interface' subtrees of MIB-II [RFC1213] or
> the systemGroup of the SNMPv2-MIB [RFC3418] and the
> ifGeneralInformationGroup of the IF-MIB [RFC2863]."
> 
> with similar changes in 3.2.1 and 3.2.2.  Note that RFC 1213
> would have to be added as a normative reference.
> 
> Note: I consider the above to be a MUST FIX, since otherwise
> the specification of the prerequisites is just too vague.
> 
> 10.) Technical content -- the extent of my technical review was
> to go over the output from smidiff.  I noticed a couple of things:
> 
> (a) the following is (formally) a violation of the revision rules
> in RFC 2578 Section 10, since it might result in a compilation
> failure of a module that IMPORTS MacAdress from BRIDGE-MIB instead
> of from SNMPv2-TC:
> 
> /usr/local/share/mibs/ietf/BRIDGE-MIB:17 [1] {type-removed} type
> `MacAddress' has been deleted
> 
> An RFC content search revealed that all of the published IETF MIB
> modules (other than BRIDGE-MIB) that use MacAddesss actually
> import it from SNMPv2-TC.  However, that might not be true of
> enterprise MIB modules or of MIB modules maintained by other SDOs,
> and there is no effective way I know of to search for such usage.
> 
> So I wonder if it might not have been better to have left the
> definition in place, but to make its status 'deprecated' and
> have text pointing potential users to the version in SNMPv2-TC.
> 
> I won't squawk if the WG wants to leave this as is.
> 
> (b) also, the following changes violate our MIB review guidelines:
> 
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `transparent-only' changed to `transparentOnly' at type used in
> `dot1dBaseType'
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> `dot1dBaseType'
> 
> See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> bullet on p. 29.  The WG will have to judge for itself whether the
> issue raised there applies in this case (I think it does, but I am
> not interested in picking a fight if the WG disagrees).  Note that
> if this change is backed out then smilint will complain about the
> hyphens (as it does about legacy read-only index columns).
> 
> (c) As a result of 9(d) above, I noticed that the compliance
> statements do not spell out the prerequisites, as is has been
> done in some recent MIB modules.  It might be worthwhile to
> consider doing that here.  For bridgeCompliance1493 it would be
> necessary to specifiy this information in the DESCRIPTION clause
> (since, presumably, that one would call out the old MIB-II
> subtrees).  For bridgeComplianceXXXX one could IMPORT the
> systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
> from IF-MIB and list them in the MANDATORY-GROUPS clause.
> 
> Note:  IMHO, this is just a nice-to-have.  Spelling out the
> prerequisites in the text of Section 3 is good enough for me.
> The OPS AD for NM has been know to disagree with me on this :-)
> 
> Mike Heard
> 
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Tue Jan 25 12:54:37 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24044;
	Tue, 25 Jan 2005 12:54:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtVAV-0001tp-6n; Tue, 25 Jan 2005 13:11:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtUs2-0001Kq-4k; Tue, 25 Jan 2005 12:52:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtUph-0000vB-2W
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 12:50:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23729
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 12:50:25 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtV6R-0001lS-31
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 13:07:47 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0PHntQQ024731
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 09:49:55 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0PHnuml031439;
	Tue, 25 Jan 2005 09:49:56 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0PHnuJx031435; Tue, 25 Jan 2005 09:49:56 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 Jan 2005 09:49:55 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050125104127.GA2413@james>
	<20050125132236.99E9E1799E2@icicle.pobox.com>
Message-ID: <Pine.LNX.4.10.10501250857430.10086-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196

On Tue, 25 Jan 2005, Juergen Schoenwaelder wrote:
> > > > 10.) Technical content -- the extent of my technical review was
> > > > to go over the output from smidiff.  I noticed a couple of things:
> > ...
> > > > (b) also, the following changes violate our MIB review guidelines:
> > > > 
> > > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > > `transparent-only' changed to `transparentOnly' at type used in
> > > > `dot1dBaseType'
> > > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > > `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> > > > `dot1dBaseType'
> > > > 
> > > > See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> > > > bullet on p. 29.  [ ... ]
...
> > But as I said, I will not pick a fight about this.
> 
> I certainly do not want to discuss the merrit of these rules here. I
> can life either way. But it would be good if the conclusion how we
> deal with this case could be recorded so that we do things consistently
> the next time this pops up.

In that case I would ask that the original labels be reinstated, in
compliance with the MIB review guidelines, because I think that the
MIB review guidelines are correct as written.

> > > > (c) As a result of 9(d) above, I noticed that the compliance
> > > > statements do not spell out the prerequisites [ ... ]
...
> So from this, I conclude that we probably want to add the following 
> to the compliance statements:
> 
> 	Note that compliance with this MIB module requires
> 	compliance with the ifCompliance3 MODULE-COMPLIANCE 
> 	statement of the IF-MIB (RFC2863) and compliance with
> 	the snmpBasicComplianceRev2 MODULE-COMPLIANCE of the
> 	SNMPv2-MIB (RFC3418).
> 
> Section 3.2.1 would be changed to the following:
> 
> 	Implementations of the BRIDGE-MIB must comply with the
> 	snmpBasicComplianceRev2 MODULE-COMPLIANCE statement in 
> 	the SNMPv2-MIB [RFC2863].
> 
> Section 3.2.2 first paragraph would be changed to the following:
> 
> 	Implementations of the BRIDGE-MIB must comply with the
> 	ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB
> 	[RFC2863]. In the IF-MIB terminology, an interface is
> 	thought of as being attached to a `subnetwork'.  (Note 
> 	that this term is not to be confused with `subnet' which 
> 	refers to an addressing partitioning scheme used in the 
> 	Internet suite of protocols.) The term 'segment' is used 
> 	in this memo to refer to such a subnetwork, whether it 
> 	be an Ethernet segment, a 'ring', a WAN link, or even an
>         X.25 virtual circuit.

Making compliance with snmpBasicComplianceRev2 raises the bar quite
a bit higher than necessary.  That compliance statement imposes a
requirement for SNMP instrumentation.  Maybe that's a good thing to
have, but it's not necessary to support the BRIDGE-MIB.  If suffices
to support the systemGroup.  But, if it is agreed to go that route,
I will have no quarrel.

> We may want to add after the first sentence (although this should
> be clear from reading the IF-MIB):
>
>       This includes mandatory support of the ifFixedLengthGroup,
>       the ifPacketGroup, and the ifCounterDiscontinuityGroup of
>       the IF-MIB [RFC2863], which are conditionally mandatory
>       in the ifCompliance3 statement.

Leave that out.  Redundant text runs the risk of being
contradictory, and this is such a case.  ifFixedLengthGroup and
ifPacketGroup are mutually exclusive in ifCompliance3.  Let RFC 2863
speak for itself.

The one other fix that I would suggest along with the above would be
the following new text for Sec. 3.2:

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not been
   included in this MIB module because they overlap with objects in
   other MIB modules applicable to a bridge implementing this MIB.  In
   particular, it is assumed that a bridge implementing the BRIDGE-MIB
   module will also implement the SNMPv2-MIB [RFC3418] and the IF-MIB
   [RFC2863].

On Tue, 25 Jan 2005, David B Harrington wrote:
> Let me jump in as chair.
> 
> It is important to realize that we have already been through WGLC and
> submitted the document for advancement, and cannot make any changes to
> the document without "unsubmitting" it. We cannot publish a new
> revision for minor changes.
> 
> I asked for an independent MIB Doctor review to ensure that there is
> nothing **broken** in this document; given that it has been reviewed
> by three of four MIB Doctors already, I didn't think it very likely we
> missed anything, but an extra pair of eyes doesn't hurt, and reassures
> the IESG it has been independently reviewed.

In that case I will withdraw all of my merely "nice-to-have" comments,
and I can resubmit the remaining stuff as IETF Last Call comments.  That
would include the editorial stuff plus the two issues discussed above.

Mike


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 13:14:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25347;
	Tue, 25 Jan 2005 13:14:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtVTl-0002ZE-OM; Tue, 25 Jan 2005 13:31:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtV8S-0003bu-CL; Tue, 25 Jan 2005 13:09:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtV2q-00035f-Vu
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 13:04:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24895
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 13:04:01 -0500 (EST)
Message-Id: <200501251804.NAA24895@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtVJZ-0002Db-It
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 13:21:24 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc13) with SMTP
	id <20050125180326015009qk66e>; Tue, 25 Jan 2005 18:03:26 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Tue, 25 Jan 2005 13:03:23 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501231229370.15163-100000@shell4.bayarea.net>
Thread-Index: AcUCqxevK6ZXG+oQT9KWDqxjoFCoswAT0QiQ
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Content-Transfer-Encoding: 7bit

Hi,

My responses to your comments, inline.

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
  

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of C. M. Heard
> 
> 7.) Copyright Notices -- the one in the MIB module has a 2004
> date.  That (and the LAST-UPDATED/REVISION clause dates) should
> be brought up-to-date if another revision is spun;  if no other
> things are corrected this can probably be left to the RFC Editor.

[as chair] The RFC editor can handle this if needed.

> 
> 8.) IPR Notice -- OK
> 
> 9.) Other issues -- a few editorial nits (and one item that I
> consider important) were picked up:
> 
> (a) unexpanded acronym (PICS, in Sec. 3.1):
> 
Good catch. However, I expect everybody implementing this mib module
will know this term from IEEE.
[as chair, if required by the RFC Editor, we can handle during 48hour
review]
> 

> 3.1.3  The dot1dSr Subtree
> 
[...]
I agree your text is cleaner, but the current text is "good enough"

> 
> (d) inaccurate text:
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects 
> have not been
>    included in this MIB module because they overlap with objects in
>    other MIB modules applicable to a bridge implementing this MIB.
In
>    particular, it is assumed that a bridge implementing the
BRIDGE-MIB
>    module will also implement (at least) the 'system' subtree of the
>    SNMPv2-MIB [RFC3418] and the 'interfaces' subtree of the IF-MIB
>    [RFC2863].
> 
> Minimal fix:
> 
> s/'system' subtree/systemGroup/ here and in Section 3.2.1
> 
> s/'interfaces' subtree/ifGeneralInformationGroup/ here and
> in Section 3.2.2

1) We need to be backwards compatible with RFC1493. We should use
(roughly) the same text used there. RFC1493 had vague prerequisites;
we cannot tighten them now without potentially making compliant
implementations non-compliant. The RFC3418 systemGroup requires more
objects than the RFC1213 system subtree. If we want to make this
change in how relationships are described, then we should open RFC3418
and add a compliance for the RFC1213 set of system objects, much as we
have done in this document with bridgeCompliance1493.
2) RFC1493 does not refer to compliance groups, but to the system and
interface groups, which in SMIv1 modules meant subtrees. So I don't
agree that the text is inaccurate, just vague.
3) We've gone around in circles on all our documents, and documents
being developed in IEEE 802.1, about whether the expectation is for
the system group in RFC1213 or the one in RFC3418; the fact is that
the expected objects are all in RFC1213, and the additional objects
defined in RFC3418 are not related to the bridge mib objects. I can
live with either specification. I agree that having both creates
unnecessary normative references (i.e. document dependencies). The
argument is mostly related to IETF-internal issues, like the desire to
declare all SMIv1 modules historic, which has nothing to do with
making it easier to manage a network device.

> 
> Note: I consider the above to be a MUST FIX, since otherwise
> the specification of the prerequisites is just too vague.

As a MIB Doctor, I don't consider this a MUST FIX, and I can tell you
that all mib modules in development in the IEEE 802.1 WG do not have
the explicit compliances you consider a MUST FIX. This is also not in
the mib-review-guidelines, is it? 

It might be good to adopt tighter cross-compliances for new mib
modules, after suitable debate, but for updating "relationship" text
for SMIv1 mib modules, I question this approach if it makes compliant
implementations non-compliant. I also have concerns about creating
dependencies between mib module compliances. We moved away from the
MIB-I and MIB-II approach and moved to a modular approach because
having everything integrally tied together was not very workable
within the IETF standards process. I think having these cross-document
compiance-dependencies works against modularity. But this is a debate
for the MIB Doctor forum rather than the bridge mib forum.

If Bert or David consider this a MUST FIX, they can add it to the AD
review comments. Otherwise, I think we should leave it unchanged. 

> 
> 10.) Technical content -- the extent of my technical review was
> to go over the output from smidiff.  I noticed a couple of things:
> 
> (a) the following is (formally) a violation of the revision rules
> in RFC 2578 Section 10, since it might result in a compilation
> failure of a module that IMPORTS MacAdress from BRIDGE-MIB instead
> of from SNMPv2-TC:
> 
I think changing this to import from SNMPv2-TC is the appropriate
thing to do since the mib module is being converted to SMIv2. The new
IMPORTS statement provides enough information for users to determine
where they should get the definition now, should their compilation
fail. 

As a contributor, I favor keeping it as is.
If Bert wants us to follow your proposal, he can add it to the AD
review.

> 
> (b) also, the following changes violate our MIB review guidelines:
> 
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `transparent-only' changed to `transparentOnly' at type used in
> `dot1dBaseType'
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> `dot1dBaseType'
> 
> See draft-ietf-ops-mib-review-guidelines-03.txt, section 4.9, first
> bullet on p. 29.  The WG will have to judge for itself whether the
> issue raised there applies in this case (I think it does, but I am
> not interested in picking a fight if the WG disagrees).  Note that
> if this change is backed out then smilint will complain about the
> hyphens (as it does about legacy read-only index columns).
> 


I do agree that technically this should not change for backwards
compatibility reasons. OTOH, the elimination of hyphaens makes it
easier to script using object names rather than OIDs. 

I don't consider this a major issue, relative to this enumeration,
because I don't think many application developers will utilize this
enumeration. In my mind, it makes no difference which we use.

If the Ads would like to see this revert to its RRFC1493 names, they
can add it to the AD Review and we'll make the change.


> (c) As a result of 9(d) above, I noticed that the compliance
> statements do not spell out the prerequisites, as is has been
> done in some recent MIB modules.  It might be worthwhile to
> consider doing that here.  For bridgeCompliance1493 it would be
> necessary to specifiy this information in the DESCRIPTION clause
> (since, presumably, that one would call out the old MIB-II
> subtrees).  For bridgeComplianceXXXX one could IMPORT the
> systemGroup from SNMPv2-MIB and the ifGeneralInformationGroup
> from IF-MIB and list them in the MANDATORY-GROUPS clause.
> 
> Note:  IMHO, this is just a nice-to-have.  Spelling out the
> prerequisites in the text of Section 3 is good enough for me.
> The OPS AD for NM has been know to disagree with me on this :-)

I think discussions of additional nits for mib reviews belongs on the
MIB Doctor list rather than the bridge mib list.
> 
> Mike Heard
> 
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Tue Jan 25 13:17:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25540;
	Tue, 25 Jan 2005 13:17:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtVWB-0002fT-MY; Tue, 25 Jan 2005 13:34:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtVDo-0004SW-Gf; Tue, 25 Jan 2005 13:15:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtVC7-00040W-TG
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 13:13:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25308
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 13:13:36 -0500 (EST)
Message-Id: <200501251813.NAA25308@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtVSs-0002YI-L8
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 13:30:59 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc12) with SMTP
	id <2005012518130701400hjd3fe>; Tue, 25 Jan 2005 18:13:07 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Tue, 25 Jan 2005 13:13:03 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501250857430.10086-100000@shell4.bayarea.net>
Thread-Index: AcUDBvVLiCzjw51wT5qkypB76lm5jgAAZJ5A
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Content-Transfer-Encoding: 7bit

Mike, 

If you provide us with a list of necessary changes, we can discuss
them and make them part of the AD review process.

We are definitely looking to eliminate nice-to-have changes and
proposed mib review requirements that are not currently included in
the mib-review-guidelines-03. 

[soapbox]
Working against constantly moving targets is one major reason why
these documents have already taken three years. If it wasn't defined
as a requirement when we started WGLC, I don't want to hear about it
now.
[end soapbox]

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Tuesday, January 25, 2005 12:50 PM
> To: Bridge-Mib (E-mail)
> Subject: Re: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> On Tue, 25 Jan 2005, Juergen Schoenwaelder wrote:
> > > > > 10.) Technical content -- the extent of my technical 
> review was
> > > > > to go over the output from smidiff.  I noticed a 
> couple of things:
> > > ...
> > > > > (b) also, the following changes violate our MIB 
> review guidelines:
> > > > > 
> > > > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} 
> warning: named number
> > > > > `transparent-only' changed to `transparentOnly' at 
> type used in
> > > > > `dot1dBaseType'
> > > > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} 
> warning: named number
> > > > > `sourceroute-only' changed to `sourcerouteOnly' at 
> type used in in
> > > > > `dot1dBaseType'
> > > > > 
> > > > > See draft-ietf-ops-mib-review-guidelines-03.txt, 
> section 4.9, first
> > > > > bullet on p. 29.  [ ... ]
> ...
> > > But as I said, I will not pick a fight about this.
> > 
> > I certainly do not want to discuss the merrit of these rules here.
I
> > can life either way. But it would be good if the conclusion how we
> > deal with this case could be recorded so that we do things 
> consistently
> > the next time this pops up.
> 
> In that case I would ask that the original labels be reinstated, in
> compliance with the MIB review guidelines, because I think that the
> MIB review guidelines are correct as written.
> 
> > > > > (c) As a result of 9(d) above, I noticed that the compliance
> > > > > statements do not spell out the prerequisites [ ... ]
> ...
> > So from this, I conclude that we probably want to add the
following 
> > to the compliance statements:
> > 
> > 	Note that compliance with this MIB module requires
> > 	compliance with the ifCompliance3 MODULE-COMPLIANCE 
> > 	statement of the IF-MIB (RFC2863) and compliance with
> > 	the snmpBasicComplianceRev2 MODULE-COMPLIANCE of the
> > 	SNMPv2-MIB (RFC3418).
> > 
> > Section 3.2.1 would be changed to the following:
> > 
> > 	Implementations of the BRIDGE-MIB must comply with the
> > 	snmpBasicComplianceRev2 MODULE-COMPLIANCE statement in 
> > 	the SNMPv2-MIB [RFC2863].
> > 
> > Section 3.2.2 first paragraph would be changed to the following:
> > 
> > 	Implementations of the BRIDGE-MIB must comply with the
> > 	ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB
> > 	[RFC2863]. In the IF-MIB terminology, an interface is
> > 	thought of as being attached to a `subnetwork'.  (Note 
> > 	that this term is not to be confused with `subnet' which 
> > 	refers to an addressing partitioning scheme used in the 
> > 	Internet suite of protocols.) The term 'segment' is used 
> > 	in this memo to refer to such a subnetwork, whether it 
> > 	be an Ethernet segment, a 'ring', a WAN link, or even an
> >         X.25 virtual circuit.
> 
> Making compliance with snmpBasicComplianceRev2 raises the bar quite
> a bit higher than necessary.  That compliance statement imposes a
> requirement for SNMP instrumentation.  Maybe that's a good thing to
> have, but it's not necessary to support the BRIDGE-MIB.  If suffices
> to support the systemGroup.  But, if it is agreed to go that route,
> I will have no quarrel.
> 
> > We may want to add after the first sentence (although this should
> > be clear from reading the IF-MIB):
> >
> >       This includes mandatory support of the ifFixedLengthGroup,
> >       the ifPacketGroup, and the ifCounterDiscontinuityGroup of
> >       the IF-MIB [RFC2863], which are conditionally mandatory
> >       in the ifCompliance3 statement.
> 
> Leave that out.  Redundant text runs the risk of being
> contradictory, and this is such a case.  ifFixedLengthGroup and
> ifPacketGroup are mutually exclusive in ifCompliance3.  Let RFC 2863
> speak for itself.
> 
> The one other fix that I would suggest along with the above would be
> the following new text for Sec. 3.2:
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects 
> have not been
>    included in this MIB module because they overlap with objects in
>    other MIB modules applicable to a bridge implementing this MIB.
In
>    particular, it is assumed that a bridge implementing the
BRIDGE-MIB
>    module will also implement the SNMPv2-MIB [RFC3418] and the
IF-MIB
>    [RFC2863].
> 
> On Tue, 25 Jan 2005, David B Harrington wrote:
> > Let me jump in as chair.
> > 
> > It is important to realize that we have already been 
> through WGLC and
> > submitted the document for advancement, and cannot make any 
> changes to
> > the document without "unsubmitting" it. We cannot publish a new
> > revision for minor changes.
> > 
> > I asked for an independent MIB Doctor review to ensure that there
is
> > nothing **broken** in this document; given that it has been
reviewed
> > by three of four MIB Doctors already, I didn't think it 
> very likely we
> > missed anything, but an extra pair of eyes doesn't hurt, 
> and reassures
> > the IESG it has been independently reviewed.
> 
> In that case I will withdraw all of my merely "nice-to-have"
comments,
> and I can resubmit the remaining stuff as IETF Last Call 
> comments.  That
> would include the editorial stuff plus the two issues discussed
above.
> 
> 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 bridge-mib-bounces@ietf.org  Tue Jan 25 15:05:04 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02693;
	Tue, 25 Jan 2005 15:05:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtXCk-00066H-8a; Tue, 25 Jan 2005 15:22:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtWsn-000641-SD; Tue, 25 Jan 2005 15:01:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtWqq-0004og-R3
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 14:59:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02200
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 14:59:46 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtX7b-0005ur-Ac
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 15:17:08 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0PJxEQQ029549
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 11:59:14 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0PJxIVR018671;
	Tue, 25 Jan 2005 11:59:18 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0PJxHNl018667; Tue, 25 Jan 2005 11:59:18 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 Jan 2005 11:59:17 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050125181308.C7E85122AF2@majesty.pobox.com>
Message-ID: <Pine.LNX.4.10.10501251140130.10803-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c

On Tue, 25 Jan 2005, David B Harrington wrote:
> If you provide us with a list of necessary changes, we can discuss
> them and make them part of the AD review process.

I already did that.  But I'll do it again.

(a) the text in Sections 3.2 was adapted from the original 1493 but
now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
Details were spelled out in previous e-mail responses to Juergen.
If you wish to leave the prerequisites exactly as they were in 1493
then you should probably revert to referring to RFC 1213.  If you
want to leave the references to 3418 and 2863 then please do
something to fix the inaccuracies, particularly in 3.2.2.

(b) undo the following changes (or get an AD waiver from the MIB
review guidelines):

BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
`transparent-only' changed to `transparentOnly' at type used in
`dot1dBaseType'
BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
`sourceroute-only' changed to `sourcerouteOnly' at type used in in
`dot1dBaseType'
 
> [soapbox]
> Working against constantly moving targets is one major reason why
> these documents have already taken three years. If it wasn't defined
> as a requirement when we started WGLC, I don't want to hear about it
> now.
> [end soapbox]

Excuse me, but you ASKED for this review, and you ASKED from someone
outside the WG to do it.  As an outsider I did not know the details
of the history, or the pre-WGLC requirements, or even that the doc
has been through WG last call, and you did not tell me about that
before I did the review.  So I applied the current MIB review
guidelines.  I am sorry that I could not read your mind.

If you are satisfied that the doc is "good enough" then ship it.  I
don't care.  I have spent enough time on this.  My job here is done
and I will shut up.

Bye,

Mike


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 17:18:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19495;
	Tue, 25 Jan 2005 17:18:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtZI7-0004VH-OO; Tue, 25 Jan 2005 17:36:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtYrP-0006xD-NZ; Tue, 25 Jan 2005 17:08:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtYRy-0001cT-51
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 16:42:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12481
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 16:42:11 -0500 (EST)
Message-Id: <200501252142.QAA12481@ietf.org>
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtYih-0001hu-NG
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 16:59:35 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc11) with SMTP
	id <2005012521413801300kbfkve>; Tue, 25 Jan 2005 21:41:38 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Tue, 25 Jan 2005 16:41:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501251140130.10803-100000@shell4.bayarea.net>
Thread-Index: AcUDGSkvThdKrs4zQUmSwSHD8SP5JQACFJww
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

 inline.

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> 
> (a) the text in Sections 3.2 was adapted from the original 1493 but
> now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> Details were spelled out in previous e-mail responses to Juergen.
> If you wish to leave the prerequisites exactly as they were in 1493
> then you should probably revert to referring to RFC 1213.  If you
> want to leave the references to 3418 and 2863 then please do
> something to fix the inaccuracies, particularly in 3.2.2.
> 
After reviewing the discussion more closely, I agree. 
This text should refer to RFC1213 for backwards compatibility.

There is no MODULE-COMPLIANCE in RFC3418 that appropriately reflects
RFC1213 compliance.
The same appears to be true for RFC2863.

> (b) undo the following changes (or get an AD waiver from the MIB
> review guidelines):
> 
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `transparent-only' changed to `transparentOnly' at type used in
> `dot1dBaseType'
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> `dot1dBaseType'
>  
I agree. The changes should be undone for backwards compatibility.

Unless I hear from others who object to this, I will forward these
recommendations to the ADs.

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 



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


From bridge-mib-bounces@ietf.org  Tue Jan 25 17:18:59 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19516;
	Tue, 25 Jan 2005 17:18:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtZIM-0004YE-M3; Tue, 25 Jan 2005 17:36:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtYrU-0006zu-8Z; Tue, 25 Jan 2005 17:08:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtYTx-0002Ro-5S
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 16:44:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12627
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 16:44:14 -0500 (EST)
Message-Id: <200501252144.QAA12627@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtYkj-0001oD-27
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 17:01:38 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc13) with SMTP
	id <20050125214343015009ihdfe>; Tue, 25 Jan 2005 21:43:43 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Tue, 25 Jan 2005 16:43:41 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501251140130.10803-100000@shell4.bayarea.net>
Thread-Index: AcUDGSkvThdKrs4zQUmSwSHD8SP5JQAAqlSg
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi Mike,

Thanks for the in-depth review. 
I realized when I read your review that I hadn't provided you with the
background info on the document.
I apologize for not doing so before you did the review.

Are there any further WG comments on these issues before I submit them
to the ADs for consideration as part of the AD review?

dbh

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Tuesday, January 25, 2005 2:59 PM
> To: 'Bridge-Mib (E-mail)'
> Subject: RE: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> On Tue, 25 Jan 2005, David B Harrington wrote:
> > If you provide us with a list of necessary changes, we can discuss
> > them and make them part of the AD review process.
> 
> I already did that.  But I'll do it again.
> 
> (a) the text in Sections 3.2 was adapted from the original 1493 but
> now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> Details were spelled out in previous e-mail responses to Juergen.
> If you wish to leave the prerequisites exactly as they were in 1493
> then you should probably revert to referring to RFC 1213.  If you
> want to leave the references to 3418 and 2863 then please do
> something to fix the inaccuracies, particularly in 3.2.2.
> 
> (b) undo the following changes (or get an AD waiver from the MIB
> review guidelines):
> 
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `transparent-only' changed to `transparentOnly' at type used in
> `dot1dBaseType'
> BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> `dot1dBaseType'
>  
> > [soapbox]
> > Working against constantly moving targets is one major reason why
> > these documents have already taken three years. If it wasn't
defined
> > as a requirement when we started WGLC, I don't want to hear about
it
> > now.
> > [end soapbox]
> 
> Excuse me, but you ASKED for this review, and you ASKED from someone
> outside the WG to do it.  As an outsider I did not know the details
> of the history, or the pre-WGLC requirements, or even that the doc
> has been through WG last call, and you did not tell me about that
> before I did the review.  So I applied the current MIB review
> guidelines.  I am sorry that I could not read your mind.
> 
> If you are satisfied that the doc is "good enough" then ship it.  I
> don't care.  I have spent enough time on this.  My job here is done
> and I will shut up.
> 
> Bye,
> 
> 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 bridge-mib-bounces@ietf.org  Tue Jan 25 18:24:11 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24988;
	Tue, 25 Jan 2005 18:24:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtaJT-0006Th-Ml; Tue, 25 Jan 2005 18:41:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cta23-0007Sw-Pt; Tue, 25 Jan 2005 18:23:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtZrN-000122-3h
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 18:12:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23799
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 18:12:30 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cta8A-00067p-Ap
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 18:29:54 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 21CC9D4B5;
	Wed, 26 Jan 2005 00:11:56 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 20653-05; Wed, 26 Jan 2005 00:11:55 +0100 (CET)
Received: from james (I8c6d.i.pppool.de [85.73.140.109])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id F3782998E;
	Wed, 26 Jan 2005 00:11:54 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CtZqj-0000iS-30; Wed, 26 Jan 2005 00:11:53 +0100
Date: Wed, 26 Jan 2005 00:11:53 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050125231153.GA2693@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	"'C. M. Heard'" <heard@pobox.com>,
	"'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
References: <Pine.LNX.4.10.10501251140130.10803-100000@shell4.bayarea.net>
	<200501252142.QAA12481@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501252142.QAA12481@ietf.org>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

On Tue, Jan 25, 2005 at 04:41:35PM -0500, David B Harrington wrote:

> > (a) the text in Sections 3.2 was adapted from the original 1493 but
> > now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> > Details were spelled out in previous e-mail responses to Juergen.
> > If you wish to leave the prerequisites exactly as they were in 1493
> > then you should probably revert to referring to RFC 1213.  If you
> > want to leave the references to 3418 and 2863 then please do
> > something to fix the inaccuracies, particularly in 3.2.2.
> > 
> After reviewing the discussion more closely, I agree. 
> This text should refer to RFC1213 for backwards compatibility.
> 
> There is no MODULE-COMPLIANCE in RFC3418 that appropriately reflects
> RFC1213 compliance.
> The same appears to be true for RFC2863.

I personally hate to see this SMIv2 proposed standard version of the
BRIDGE-MIB depend on RFC1213. So if the current text is not good
enough, I would rather prefer to work through the details to come
up with text that says what we believe RFC 1493 did say, but referring 
to the current MIB modules we have. In the worst case, we list all 
the IF-MIB/SNMPv2-MIB objects that we believe were meant when RFC 
1493 was written. We may add a note that the IF-MIB/SNMPv2-MIB
have evolved and that compliance to the current IF-MIB/SNMPv2-MIB may 
require the implementation of additional objects but doing so is not 
mandated by the BRIDGE-MIB itself.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Tue Jan 25 18:57:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27074;
	Tue, 25 Jan 2005 18:57:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtapH-0007TB-Rx; Tue, 25 Jan 2005 19:14:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtaU9-0004xr-Sm; Tue, 25 Jan 2005 18:52:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtaK0-00031q-BY
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 18:42:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26564
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 18:42:05 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ctaao-00074L-0C
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 18:59:30 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0PNfZQQ028107
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 15:41:35 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0PNfcK9031496;
	Tue, 25 Jan 2005 15:41:38 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0PNfcaS031493; Tue, 25 Jan 2005 15:41:38 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 Jan 2005 15:41:37 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050125214139.5EB00102D38@boggle.pobox.com>
Message-ID: <Pine.LNX.4.10.10501251448580.12797-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632

First, apologies to everyone for losing my cool.  Now back to
technical stuff ...

On Tue, 25 Jan 2005, David B Harrington wrote:
> > -----Original Message-----
> > From: bridge-mib-bounces@ietf.org 
> > 
> > (a) the text in Sections 3.2 was adapted from the original 1493 but
> > now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> > Details were spelled out in previous e-mail responses to Juergen.
> > If you wish to leave the prerequisites exactly as they were in 1493
> > then you should probably revert to referring to RFC 1213.  If you
> > want to leave the references to 3418 and 2863 then please do
> > something to fix the inaccuracies, particularly in 3.2.2.
> > 
> After reviewing the discussion more closely, I agree. 
> This text should refer to RFC1213 for backwards compatibility.
> 
> There is no MODULE-COMPLIANCE in RFC3418 that appropriately reflects
> RFC1213 compliance.
> The same appears to be true for RFC2863.

In the interest of not creating more problems than are solved, I'm
going to make some explicit suggestions for the fixes.  These are
just suggestions;  the editor, the chair, and AD are free to do with
them as they see fit.

First, note that Section 3.1 refers to certain objects in the
SNMPv2-MIB and the IF-MIB.  I think that this is OK since these
objects also exist in MIB-II.  So no change is suggested there.

Second, for Sections 3.2, 3.2.1, and 3.2.2, the following
replacement text, referring both to RFC 1213 and its successors,
is suggested:

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not been
   included in this MIB module because they overlap with objects in
   other MIB modules applicable to a bridge implementing this MIB.  In
   particular, it is assumed that a bridge implementing the BRIDGE-MIB
   module will also implement (at least) the 'system' subtree of MIB-II
   [RFC1213] or equivalent objects from the SNMPv2-MIB [RFC3418] and
   the 'interfaces' subtree of MIB-II or equivalent objects from the
   IF-MIB [RFC2863].  Systems that can claim compliance with the
   snmpBasicComplianceRev2 statement of the SNMPv2-MIB and with the
   ifCompliance3 statement of the IF-MIB will satisfy this assumption.

3.2.1  Relationship to the System Group

   The 'system' subtree of MIB-II [RFC21213], which is a subset of the
   systemGroup in the SNMPv2-MIB [RFC3418], is defined as being
   mandatory for all systems.  Thus, those objects apply to the entity
   as a whole irrespective of whether the entity's sole functionality is
   bridging, or whether bridging is only a subset of the entity's
   functionality.

3.2.2  Relationship to the Interfaces Group

   The 'interfaces' subtree of MIB-II [RFC1213], which is a subset of
   the IF-MIB [RFC2863], is defined as being mandatory for all systems
   and contains information on an entity's interfaces, where each
   interface is thought of as being attached to a `subnetwork'.  (Note
   that this term is not to be confused with `subnet' which refers to an
   addressing partitioning scheme used in the Internet suite of
   protocols.)  The term 'segment' is used in this memo to refer to such
   a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN
   link, or even an X.25 virtual circuit.

Third, add RFC 1213 to the normative references list.  This should
not be a problem since it is an Internet Standard.  We made a decision
many years ago NOT so send this MIB module (and the SMIv1 documents)
to Historic precisely because so many documents refer to it.

Finally, retain RFC 3418 and RFC 2863 as normative references.  The
latter is needed because of the IMPORT of InterfaceIndex, and both
are listed as alternatives to RFC 1213 in the prerequisites section.

> > (b) undo the following changes (or get an AD waiver from the MIB
> > review guidelines):
> > 
> > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > `transparent-only' changed to `transparentOnly' at type used in
> > `dot1dBaseType'
> > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> > `dot1dBaseType'
> >  
> I agree. The changes should be undone for backwards compatibility.
> 
> Unless I hear from others who object to this, I will forward these
> recommendations to the ADs.

Sounds good.

Thanks,

Mike


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


From bridge-mib-bounces@ietf.org  Tue Jan 25 19:24:51 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29863;
	Tue, 25 Jan 2005 19:24:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtbGD-0000D2-9h; Tue, 25 Jan 2005 19:42:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ctay6-0005id-1E; Tue, 25 Jan 2005 19:23:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ctarc-0003nA-WD
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 19:16:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29239
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 19:16:49 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ctb8R-0008OD-50
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 19:34:15 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j0Q0Gm4E025901
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 18:16:49 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP4645X>; Wed, 26 Jan 2005 01:16:47 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506497708@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "C. M. Heard" <heard@pobox.com>,
        "Bridge-Mib (E-mail)"
	<bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Wed, 26 Jan 2005 01:16:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab

Inline

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org]On
> Behalf Of C. M. Heard
> Sent: Wednesday, January 26, 2005 00:42
> To: Bridge-Mib (E-mail)
> Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> 
> First, apologies to everyone for losing my cool.  Now back to
> technical stuff ...
> 
Mike ... thanks for your Review. 
You didn't know the context and so I think what you did was fine.
If everyone in the IETF always stayed as cool as you are, then 
we'd have much more technical fun!

more below

> On Tue, 25 Jan 2005, David B Harrington wrote:
> > > -----Original Message-----
> > > From: bridge-mib-bounces@ietf.org 
> > > 
> > > (a) the text in Sections 3.2 was adapted from the original 1493 but
> > > now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> > > Details were spelled out in previous e-mail responses to Juergen.
> > > If you wish to leave the prerequisites exactly as they were in 1493
> > > then you should probably revert to referring to RFC 1213.  If you
> > > want to leave the references to 3418 and 2863 then please do
> > > something to fix the inaccuracies, particularly in 3.2.2.
> > > 
> > After reviewing the discussion more closely, I agree. 
> > This text should refer to RFC1213 for backwards compatibility.
> > 
> > There is no MODULE-COMPLIANCE in RFC3418 that appropriately reflects
> > RFC1213 compliance.
> > The same appears to be true for RFC2863.
> 
> In the interest of not creating more problems than are solved, I'm
> going to make some explicit suggestions for the fixes.  These are
> just suggestions;  the editor, the chair, and AD are free to do with
> them as they see fit.
> 
> First, note that Section 3.1 refers to certain objects in the
> SNMPv2-MIB and the IF-MIB.  I think that this is OK since these
> objects also exist in MIB-II.  So no change is suggested there.
> 
> Second, for Sections 3.2, 3.2.1, and 3.2.2, the following
> replacement text, referring both to RFC 1213 and its successors,
> is suggested:
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects have not been
>    included in this MIB module because they overlap with objects in
>    other MIB modules applicable to a bridge implementing this MIB.  In
>    particular, it is assumed that a bridge implementing the BRIDGE-MIB
>    module will also implement (at least) the 'system' subtree of MIB-II
>    [RFC1213] or equivalent objects from the SNMPv2-MIB [RFC3418] and
>    the 'interfaces' subtree of MIB-II or equivalent objects from the
>    IF-MIB [RFC2863].  Systems that can claim compliance with the
>    snmpBasicComplianceRev2 statement of the SNMPv2-MIB and with the
>    ifCompliance3 statement of the IF-MIB will satisfy this assumption.
> 
> 3.2.1  Relationship to the System Group
> 
>    The 'system' subtree of MIB-II [RFC21213], which is a subset of the
>    systemGroup in the SNMPv2-MIB [RFC3418], is defined as being
>    mandatory for all systems.  Thus, those objects apply to the entity
>    as a whole irrespective of whether the entity's sole functionality is
>    bridging, or whether bridging is only a subset of the entity's
>    functionality.
> 
> 3.2.2  Relationship to the Interfaces Group
> 
>    The 'interfaces' subtree of MIB-II [RFC1213], which is a subset of
>    the IF-MIB [RFC2863], is defined as being mandatory for all systems
>    and contains information on an entity's interfaces, where each
>    interface is thought of as being attached to a `subnetwork'.  (Note
>    that this term is not to be confused with `subnet' which refers to an
>    addressing partitioning scheme used in the Internet suite of
>    protocols.)  The term 'segment' is used in this memo to refer to such
>    a subnetwork, whether it be an Ethernet segment, a 'ring', a WAN
>    link, or even an X.25 virtual circuit.
> 
> Third, add RFC 1213 to the normative references list.  This should
> not be a problem since it is an Internet Standard.  We made a decision
> many years ago NOT so send this MIB module (and the SMIv1 documents)
> to Historic precisely because so many documents refer to it.
> 
Although currently it would not be an issue to let this doc make
a normative ref to RFC1213, I prefer that we get rid of it.
I think that with the above text, it is defendable that the
normative refs are to 3418 and 2863 and that we keep 1213 as
an informative reference, don't you think so?

> Finally, retain RFC 3418 and RFC 2863 as normative references.  The
> latter is needed because of the IMPORT of InterfaceIndex, and both
> are listed as alternatives to RFC 1213 in the prerequisites section.
> 
> > > (b) undo the following changes (or get an AD waiver from the MIB
> > > review guidelines):
> > > 
> > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > `transparent-only' changed to `transparentOnly' at type used in
> > > `dot1dBaseType'
> > > BRIDGE-MIB.mi2:194 [5] {named-number-changed} warning: named number
> > > `sourceroute-only' changed to `sourcerouteOnly' at type used in in
> > > `dot1dBaseType'
> > >  
> > I agree. The changes should be undone for backwards compatibility.
> > 
> > Unless I hear from others who object to this, I will forward these
> > recommendations to the ADs.
> 
I can in fact live with either if the WG is OK. If we want to keep the
new labels, then we should add some text that we explicitly considered
the (incompatible) change and that we checked all IETF MIB documents
and that we did not see an uissue there and that we believe the
impact on vendor specific MIB modules (if any) will be very minimal.

Bert
> Sounds good.
> 
> Thanks,
> 
> Mike
> 

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


From bridge-mib-bounces@ietf.org  Tue Jan 25 19:25:21 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29889;
	Tue, 25 Jan 2005 19:25:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtbGg-0000Fj-3d; Tue, 25 Jan 2005 19:42:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ctay6-0005ik-8p; Tue, 25 Jan 2005 19:23:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ctarf-0003pC-BD
	for bridge-mib@megatron.ietf.org; Tue, 25 Jan 2005 19:16:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29254
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 19:16:52 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ctb8T-0008OR-2t
	for bridge-mib@ietf.org; Tue, 25 Jan 2005 19:34:17 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j0Q0Gm4F025901
	for <bridge-mib@ietf.org>; Tue, 25 Jan 2005 18:16:52 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP4645W>; Wed, 26 Jan 2005 01:16:47 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506497707@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: j.schoenwaelder@iu-bremen.de,
        David B Harrington <dbharrington@comcast.net>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Wed, 26 Jan 2005 01:16:45 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465

> Juergen Schoenwaelder wrote:
> Sent: Wednesday, January 26, 2005 00:12
> To: David B Harrington
> Cc: 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> 
> On Tue, Jan 25, 2005 at 04:41:35PM -0500, David B Harrington wrote:
> 
> > > (a) the text in Sections 3.2 was adapted from the original 1493 but
> > > now points to RFCs 3418 and 2863.  As a result it is now inaccurate.
> > > Details were spelled out in previous e-mail responses to Juergen.
> > > If you wish to leave the prerequisites exactly as they were in 1493
> > > then you should probably revert to referring to RFC 1213.  If you
> > > want to leave the references to 3418 and 2863 then please do
> > > something to fix the inaccuracies, particularly in 3.2.2.
> > > 
> > After reviewing the discussion more closely, I agree. 
> > This text should refer to RFC1213 for backwards compatibility.
> > 
> > There is no MODULE-COMPLIANCE in RFC3418 that appropriately reflects
> > RFC1213 compliance.
> > The same appears to be true for RFC2863.
> 
> I personally hate to see this SMIv2 proposed standard version of the
> BRIDGE-MIB depend on RFC1213. So if the current text is not good
> enough, I would rather prefer to work through the details to come
> up with text that says what we believe RFC 1493 did say, but referring 
> to the current MIB modules we have. In the worst case, we list all 
> the IF-MIB/SNMPv2-MIB objects that we believe were meant when RFC 
> 1493 was written. We may add a note that the IF-MIB/SNMPv2-MIB
> have evolved and that compliance to the current IF-MIB/SNMPv2-MIB may 
> require the implementation of additional objects but doing so is not 
> mandated by the BRIDGE-MIB itself.
> 

I agree with Juergen and would prefer that we try to do so.
At some point it would be good to get rid of normative 
dependecies on RFC1213. I think we have an opportunity to 
help work towards that goal here, and we can do so relatively
easy in this case as Juergen proposes.

Bert
> /js
> 

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


From bridge-mib-bounces@ietf.org  Thu Jan 27 16:39:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02489;
	Thu, 27 Jan 2005 16:39:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuHds-0000xQ-ND; Thu, 27 Jan 2005 16:57:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuHGq-0002tK-DA; Thu, 27 Jan 2005 16:33:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuGp8-0008TO-5g
	for bridge-mib@megatron.ietf.org; Thu, 27 Jan 2005 16:05:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24936
	for <bridge-mib@ietf.org>; Thu, 27 Jan 2005 16:05:03 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuH6J-0006tH-B9
	for bridge-mib@ietf.org; Thu, 27 Jan 2005 16:22:52 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 976A7D4E0;
	Thu, 27 Jan 2005 22:04:32 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 21912-01; Thu, 27 Jan 2005 22:04:31 +0100 (CET)
Received: from james (I809a.i.pppool.de [85.73.128.154])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 1BAD7C96E;
	Thu, 27 Jan 2005 22:04:31 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CuGoW-0000pu-ST; Thu, 27 Jan 2005 22:04:29 +0100
Date: Thu, 27 Jan 2005 22:04:28 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050127210428.GA3190@james>
Mail-Followup-To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
	David B Harrington <dbharrington@comcast.net>,
	"'C. M. Heard'" <heard@pobox.com>,
	"'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B15506497707@nl0006exch001u.nl.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15506497707@nl0006exch001u.nl.lucent.com>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4

On Wed, Jan 26, 2005 at 01:16:45AM +0100, Wijnen, Bert (Bert) wrote:

> I agree with Juergen and would prefer that we try to do so.
> At some point it would be good to get rid of normative 
> dependecies on RFC1213. I think we have an opportunity to 
> help work towards that goal here, and we can do so relatively
> easy in this case as Juergen proposes.

So here is an attempt to put things into concrete words. Please let
me know how to improve this and whether this text matches your
understanding of the situation.

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not
   been included in this MIB module because they overlap with objects
   in other MIB modules applicable to a bridge implementing this MIB
   module.

3.2.1  Relationship to the SNMPv2-MIB

   The SNMPv2-MIB [RFC3418] defines objects that are generally
   applicable to managed devices. These objects apply to the device as
   a whole irrespective of whether the device's sole functionality is
   bridging, or whether bridging is only a subset of the device's
   functionality. Implementation of the BRIDGE-MIB module requires
   that at least the objects sysDescr, sysObjectID, sysUpTime,
   sysContact, sysName, sysLocation, and sysServices of the SNMPv2-MIB
   [RFC3418] are implemented.

   Note that compliance to the current SNMPv2-MIB module requires
   additional objects and notifications to be implemented as specified
   in RFC 3418 [RFC3418].

3.2.2  Relationship to the IF-MIB

   The IF-MIB [RFC2863] defines managed objects used for managing
   network interface. A network interface is thought of as being
   attached to a `subnetwork'. (Note that this term is not to be
   confused with `subnet' which refers to an addressing partitioning
   scheme used in the Internet suite of protocols.)  The term
   'segment' is used in this memo to refer to such a subnetwork,
   whether it be an Ethernet segment, a 'ring', a WAN link, or even an
   X.25 virtual circuit.

   Implementation of the BRIDGE-MIB module requires that the following
   objects of the IF-MIB module are implemented: ifNumber, ifIndex,
   ifDescr, ifType, ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus,
   ifOperStatus, ifLastChange, ifInOctets, ifInUcastPkts,
   ifInNUcastPkts, ifInDiscards, ifInErrors, ifInUnknownProtos,
   ifOutOctets, ifOutUcastPkts, ifOutNUcastPkts, ifOutDiscards,
   ifOutErrors, ifOutQLen, ifSpecific.

   Note that compliance to the current IF-MIB module requires
   additional objects and notifications to be implemented as 
   specified in RFC 2863 [RFC2863].

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Thu Jan 27 20:43:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21670;
	Thu, 27 Jan 2005 20:43:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuLRc-0006GD-3l; Thu, 27 Jan 2005 21:01:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuL4S-0004Xx-Uq; Thu, 27 Jan 2005 20:37:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuL2D-0003lh-Q0
	for bridge-mib@megatron.ietf.org; Thu, 27 Jan 2005 20:34:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20844
	for <bridge-mib@ietf.org>; Thu, 27 Jan 2005 20:34:51 -0500 (EST)
Message-Id: <200501280134.UAA20844@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuLJS-00062i-9t
	for bridge-mib@ietf.org; Thu, 27 Jan 2005 20:52:42 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc13) with SMTP
	id <20050128013421015009g4ole>; Fri, 28 Jan 2005 01:34:22 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <j.schoenwaelder@iu-bremen.de>,
        "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Thu, 27 Jan 2005 20:34:14 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcUEs8y115r7UsjAR12R0Jj2JGdOqwAGUO2AAAJQZsA=
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Content-Transfer-Encoding: 7bit
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: 7bit

Hi,

If, for accuracy reasons, we're going to list required objects from
other mib modules, then we need to be accurate.

As detailed in 3.1, the bridge mib document has referential dependence
on sysDescr and sysUpTime to identify management objects which
substitute for 802.1D management objects that are NOT included in this
mib module. No IMPORTS or DESCRIPTION clauses indicate any semantic
dependencies on any 'system' objects. The BRIDGE-MIB has no dependence
on sysObjectID, sysName, sysContact, sysLocation or sysServices - and
the BRIDGE-MIB doesn't have a dependency on sysDescr or sysUpTime,
only a documentation dependency.

The bridge mib document has referential dependence on ifPhysAddress,
ifDescr, ifType, and ifLastChange to identify management objects which
substitute for 802.1D management objects that are NOT included in this
mib module. It has an explicit dependence only on InterfaceIndex, as
indicated in the IMPORTS clause. It mentions ifIndex in a DESCRIPTION
clause (which explains what InterfaceIndex means), and it mentions
ifMtu in a comment. It mentions interface number, but not ifNumber
directly; it probably should mention ifNumber specifically. The
BRIDGE-MIB module has no dependencies on ifNumber, ifDescr, ifType,
ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange,
ifInOctets, ifInUcastPkts, ifInNUcastPkts, ifInDiscards, ifInErrors,
ifInUnknownProtos, ifOutOctets, ifOutUcastPkts, ifOutNUcastPkts,
ifOutDiscards, ifOutErrors, ifOutQLen, or ifSpecific.

--- Suggested changes to -09-:
The second sentence in 3.2 should be eliminated (as Juergen's proposed
text has done).

section 3.2.1 text should be eliminated and should be replaced by text
that identifies the system objects which substitute for 802.1D
management objects that are NOT included in this mib module (sysDescr
and sysUpTime), thus duplicating section 3.1. 

section 3.2.2 should be trimmed to remove "is defined as being
mandatory for all systems and", and should add text to identify IF-MIB
management objects which substitute for 802.1D management objects that
are NOT included in the mib module (InterfaceIndex and ifIndex), thus
duplicating section 3.1. The comment about ifMtu might better be moved
here as well, rather than having it embedded in the module as a
comment.
 
--- comments on Juergen's proposed text:
Section 3.2.1: I believe Juergen's proposed text that says
'Implementation of the BRIDGE-MIB module requires
that at least ... are implemented' is inaccurate; this mib module can
be implemented without those objects if desired, but you will miss
some of the objects recommended by 802.1-D, and the functionality they
provide (but then even if you implement this mib module plus those
objects, you'll still be missing some objects listed in 802.1-D and
the functionality they provide, as described in 3.1).

Section 3.2.2: I believe Juergen's proposed ext that says
'Implementation of the BRIDGE-MIB module requires that the following
objects of the IF-MIB module are implemented' is inaccurate in its
list, as I describe above.


David Harrington
dbharrington@comcast.net
  

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
> Sent: Thursday, January 27, 2005 4:04 PM
> To: Wijnen, Bert (Bert)
> Cc: David B Harrington; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> Subject: Re: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> On Wed, Jan 26, 2005 at 01:16:45AM +0100, Wijnen, Bert (Bert) wrote:
> 
> > I agree with Juergen and would prefer that we try to do so.
> > At some point it would be good to get rid of normative 
> > dependecies on RFC1213. I think we have an opportunity to 
> > help work towards that goal here, and we can do so relatively
> > easy in this case as Juergen proposes.
> 
> So here is an attempt to put things into concrete words. Please let
> me know how to improve this and whether this text matches your
> understanding of the situation.
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects have not
>    been included in this MIB module because they overlap with
objects
>    in other MIB modules applicable to a bridge implementing this MIB
>    module.
> 
> 3.2.1  Relationship to the SNMPv2-MIB
> 
>    The SNMPv2-MIB [RFC3418] defines objects that are generally
>    applicable to managed devices. These objects apply to the device
as
>    a whole irrespective of whether the device's sole functionality
is
>    bridging, or whether bridging is only a subset of the device's
>    functionality. Implementation of the BRIDGE-MIB module requires
>    that at least the objects sysDescr, sysObjectID, sysUpTime,
>    sysContact, sysName, sysLocation, and sysServices of the
SNMPv2-MIB
>    [RFC3418] are implemented.
> 
>    Note that compliance to the current SNMPv2-MIB module requires
>    additional objects and notifications to be implemented as
specified
>    in RFC 3418 [RFC3418].
> 
> 3.2.2  Relationship to the IF-MIB
> 
>    The IF-MIB [RFC2863] defines managed objects used for managing
>    network interface. A network interface is thought of as being
>    attached to a `subnetwork'. (Note that this term is not to be
>    confused with `subnet' which refers to an addressing partitioning
>    scheme used in the Internet suite of protocols.)  The term
>    'segment' is used in this memo to refer to such a subnetwork,
>    whether it be an Ethernet segment, a 'ring', a WAN link, or even
an
>    X.25 virtual circuit.
> 
>    Implementation of the BRIDGE-MIB module requires that the
following
>    objects of the IF-MIB module are implemented: ifNumber, ifIndex,
>    ifDescr, ifType, ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus,
>    ifOperStatus, ifLastChange, ifInOctets, ifInUcastPkts,
>    ifInNUcastPkts, ifInDiscards, ifInErrors, ifInUnknownProtos,
>    ifOutOctets, ifOutUcastPkts, ifOutNUcastPkts, ifOutDiscards,
>    ifOutErrors, ifOutQLen, ifSpecific.
> 
>    Note that compliance to the current IF-MIB module requires
>    additional objects and notifications to be implemented as 
>    specified in RFC 2863 [RFC2863].
> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> 



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


From bridge-mib-bounces@ietf.org  Thu Jan 27 21:03:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23300;
	Thu, 27 Jan 2005 21:03:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuLku-0006en-Nh; Thu, 27 Jan 2005 21:21:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuLRd-00033a-Rc; Thu, 27 Jan 2005 21:01:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuLQl-0002pJ-0I
	for bridge-mib@megatron.ietf.org; Thu, 27 Jan 2005 21:00:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23040
	for <bridge-mib@ietf.org>; Thu, 27 Jan 2005 21:00:12 -0500 (EST)
Message-Id: <200501280200.VAA23040@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuLhz-0006bU-23
	for bridge-mib@ietf.org; Thu, 27 Jan 2005 21:18:03 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc12) with SMTP
	id <20050128015941014003f6pae>; Fri, 28 Jan 2005 01:59:42 +0000
From: "David B Harrington" <ietfdbh@comcast.net>
To: <dbharrington@comcast.net>, <j.schoenwaelder@iu-bremen.de>,
        "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Thu, 27 Jan 2005 20:59:39 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <200501280134.UAA20844@ietf.org>
Thread-Index: AcUEs8y115r7UsjAR12R0Jj2JGdOqwAGUO2AAAJQZsAAAYPqoA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
Content-Transfer-Encoding: 7bit
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietfdbh@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Content-Transfer-Encoding: 7bit

Hi,

Correction:
I see I made a mistake in my proposed changes to -09- for section
3.2.2 
My proposal should have read
> section 3.2.2 should be trimmed to remove "is defined as being
> mandatory for all systems and", and should add text to identify
IF-MIB
> management objects which substitute for 802.1D management objects
that
> are NOT included in the mib module (

ifPhysAddress, ifDescr, ifType, and ifLastChange 

), thus
> duplicating section 3.1. The comment about ifMtu might better be
moved
> here as well, rather than having it embedded in the module as a
> comment.

David Harrington
dbharrington@comcast.net


> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of David B Harrington
> Sent: Thursday, January 27, 2005 8:34 PM
> To: j.schoenwaelder@iu-bremen.de; 'Wijnen, Bert (Bert)'
> Cc: 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> Subject: RE: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> Hi,
> 
> If, for accuracy reasons, we're going to list required objects from
> other mib modules, then we need to be accurate.
> 
> As detailed in 3.1, the bridge mib document has referential
dependence
> on sysDescr and sysUpTime to identify management objects which
> substitute for 802.1D management objects that are NOT included in
this
> mib module. No IMPORTS or DESCRIPTION clauses indicate any semantic
> dependencies on any 'system' objects. The BRIDGE-MIB has no
dependence
> on sysObjectID, sysName, sysContact, sysLocation or sysServices -
and
> the BRIDGE-MIB doesn't have a dependency on sysDescr or sysUpTime,
> only a documentation dependency.
> 
> The bridge mib document has referential dependence on ifPhysAddress,
> ifDescr, ifType, and ifLastChange to identify management objects
which
> substitute for 802.1D management objects that are NOT included in
this
> mib module. It has an explicit dependence only on InterfaceIndex, as
> indicated in the IMPORTS clause. It mentions ifIndex in a
DESCRIPTION
> clause (which explains what InterfaceIndex means), and it mentions
> ifMtu in a comment. It mentions interface number, but not ifNumber
> directly; it probably should mention ifNumber specifically. The
> BRIDGE-MIB module has no dependencies on ifNumber, ifDescr, ifType,
> ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange,
> ifInOctets, ifInUcastPkts, ifInNUcastPkts, ifInDiscards, ifInErrors,
> ifInUnknownProtos, ifOutOctets, ifOutUcastPkts, ifOutNUcastPkts,
> ifOutDiscards, ifOutErrors, ifOutQLen, or ifSpecific.
> 
> --- Suggested changes to -09-:
> The second sentence in 3.2 should be eliminated (as Juergen's
proposed
> text has done).
> 
> section 3.2.1 text should be eliminated and should be replaced by
text
> that identifies the system objects which substitute for 802.1D
> management objects that are NOT included in this mib module
(sysDescr
> and sysUpTime), thus duplicating section 3.1. 
> 
> section 3.2.2 should be trimmed to remove "is defined as being
> mandatory for all systems and", and should add text to identify
IF-MIB
> management objects which substitute for 802.1D management objects
that
> are NOT included in the mib module (InterfaceIndex and ifIndex),
thus
> duplicating section 3.1. The comment about ifMtu might better be
moved
> here as well, rather than having it embedded in the module as a
> comment.
>  
> --- comments on Juergen's proposed text:
> Section 3.2.1: I believe Juergen's proposed text that says
> 'Implementation of the BRIDGE-MIB module requires
> that at least ... are implemented' is inaccurate; this mib module
can
> be implemented without those objects if desired, but you will miss
> some of the objects recommended by 802.1-D, and the functionality
they
> provide (but then even if you implement this mib module plus those
> objects, you'll still be missing some objects listed in 802.1-D and
> the functionality they provide, as described in 3.1).
> 
> Section 3.2.2: I believe Juergen's proposed ext that says
> 'Implementation of the BRIDGE-MIB module requires that the following
> objects of the IF-MIB module are implemented' is inaccurate in its
> list, as I describe above.
> 
> 
> David Harrington
> dbharrington@comcast.net
>   
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
> > Sent: Thursday, January 27, 2005 4:04 PM
> > To: Wijnen, Bert (Bert)
> > Cc: David B Harrington; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> > Subject: Re: [Bridge-mib] Re:
> Draft-iet-bridge-bridgemib-smiv2-09.txt
> > 
> > On Wed, Jan 26, 2005 at 01:16:45AM +0100, Wijnen, Bert (Bert)
wrote:
> > 
> > > I agree with Juergen and would prefer that we try to do so.
> > > At some point it would be good to get rid of normative 
> > > dependecies on RFC1213. I think we have an opportunity to 
> > > help work towards that goal here, and we can do so relatively
> > > easy in this case as Juergen proposes.
> > 
> > So here is an attempt to put things into concrete words. Please
let
> > me know how to improve this and whether this text matches your
> > understanding of the situation.
> > 
> > 3.2  Relationship to Other MIB Modules
> > 
> >    As described above, some IEEE 802.1D management objects have
not
> >    been included in this MIB module because they overlap with
> objects
> >    in other MIB modules applicable to a bridge implementing this
MIB
> >    module.
> > 
> > 3.2.1  Relationship to the SNMPv2-MIB
> > 
> >    The SNMPv2-MIB [RFC3418] defines objects that are generally
> >    applicable to managed devices. These objects apply to the
device
> as
> >    a whole irrespective of whether the device's sole functionality
> is
> >    bridging, or whether bridging is only a subset of the device's
> >    functionality. Implementation of the BRIDGE-MIB module requires
> >    that at least the objects sysDescr, sysObjectID, sysUpTime,
> >    sysContact, sysName, sysLocation, and sysServices of the
> SNMPv2-MIB
> >    [RFC3418] are implemented.
> > 
> >    Note that compliance to the current SNMPv2-MIB module requires
> >    additional objects and notifications to be implemented as
> specified
> >    in RFC 3418 [RFC3418].
> > 
> > 3.2.2  Relationship to the IF-MIB
> > 
> >    The IF-MIB [RFC2863] defines managed objects used for managing
> >    network interface. A network interface is thought of as being
> >    attached to a `subnetwork'. (Note that this term is not to be
> >    confused with `subnet' which refers to an addressing
partitioning
> >    scheme used in the Internet suite of protocols.)  The term
> >    'segment' is used in this memo to refer to such a subnetwork,
> >    whether it be an Ethernet segment, a 'ring', a WAN link, or
even
> an
> >    X.25 virtual circuit.
> > 
> >    Implementation of the BRIDGE-MIB module requires that the
> following
> >    objects of the IF-MIB module are implemented: ifNumber,
ifIndex,
> >    ifDescr, ifType, ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus,
> >    ifOperStatus, ifLastChange, ifInOctets, ifInUcastPkts,
> >    ifInNUcastPkts, ifInDiscards, ifInErrors, ifInUnknownProtos,
> >    ifOutOctets, ifOutUcastPkts, ifOutNUcastPkts, ifOutDiscards,
> >    ifOutErrors, ifOutQLen, ifSpecific.
> > 
> >    Note that compliance to the current IF-MIB module requires
> >    additional objects and notifications to be implemented as 
> >    specified in RFC 2863 [RFC2863].
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder		    International 
> University Bremen
> > <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> > 28725 Bremen, Germany
> > 
> 
> 
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Fri Jan 28 00:25:51 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08313;
	Fri, 28 Jan 2005 00:25:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuOv3-0002jd-0U; Fri, 28 Jan 2005 00:43:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuOal-0005kN-O9; Fri, 28 Jan 2005 00:22:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuOZq-0005WE-85
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 00:21:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07941
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 00:21:44 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuOr3-0002eh-SX
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 00:39:39 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0S5LEsF007223
	for <bridge-mib@ietf.org>; Thu, 27 Jan 2005 21:21:14 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0S5LITq003987;
	Thu, 27 Jan 2005 21:21:18 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0S5LHKR003981; Thu, 27 Jan 2005 21:21:18 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 27 Jan 2005 21:21:17 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050128013422.D326710A4BD@lime.pobox.com>
Message-ID: <Pine.LNX.4.10.10501272110060.29439-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

On Thu, 27 Jan 2005, David B Harrington wrote:
> If, for accuracy reasons, we're going to list required objects
> from other mib modules, then we need to be accurate.

I agree.  I was about to compose a response of my own, but I was
beat to the punch.

[ ... much good stuff snipped ... ]

> --- Suggested changes to -09-:
> The second sentence in 3.2 should be eliminated (as Juergen's proposed
> text has done).
> 
> section 3.2.1 text should be eliminated and should be replaced by text
> that identifies the system objects which substitute for 802.1D
> management objects that are NOT included in this mib module (sysDescr
> and sysUpTime), thus duplicating section 3.1. 
> 
> section 3.2.2 should be trimmed to remove "is defined as being
> mandatory for all systems and", and should add text to identify IF-MIB
> management objects which substitute for 802.1D management objects that
> are NOT included in the mib module (InterfaceIndex and ifIndex), thus
> duplicating section 3.1. The comment about ifMtu might better be moved
> here as well, rather than having it embedded in the module as a
> comment.

This would be a change from 1493, but it would be going in the right
direction, by removing inessential stuff (such as the now-deprecated
objects from the old MIB-II interfaces group) and by not adding any
new stuff.  It is much better than the proposal I recently floated.

//cmh


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


From bridge-mib-bounces@ietf.org  Fri Jan 28 02:56:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02625;
	Fri, 28 Jan 2005 02:56:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuRGN-0005VV-8k; Fri, 28 Jan 2005 03:13:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuQws-0006Hx-4q; Fri, 28 Jan 2005 02:53:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuQtE-0005A9-Dh
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 02:50:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02058
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 02:49:58 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuRAV-0005Mc-LJ
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 03:07:52 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 744BCD6EA;
	Fri, 28 Jan 2005 08:49:23 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 12538-10; Fri, 28 Jan 2005 08:49:22 +0100 (CET)
Received: from james (I948f.i.pppool.de [85.73.148.143])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 3079AD4E1;
	Fri, 28 Jan 2005 08:49:22 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CuQsa-0000ur-BM; Fri, 28 Jan 2005 08:49:20 +0100
Date: Fri, 28 Jan 2005 08:49:20 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050128074920.GB2459@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	"'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
	"'C. M. Heard'" <heard@pobox.com>,
	"'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
References: <20050128013423.D4D4D9E22@hermes.iu-bremen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050128013423.D4D4D9E22@hermes.iu-bremen.de>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Wijnen,
	Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:

[...]
 
> --- comments on Juergen's proposed text:
> Section 3.2.1: I believe Juergen's proposed text that says
> 'Implementation of the BRIDGE-MIB module requires
> that at least ... are implemented' is inaccurate; this mib module can
> be implemented without those objects if desired, but you will miss
> some of the objects recommended by 802.1-D, and the functionality they
> provide (but then even if you implement this mib module plus those
> objects, you'll still be missing some objects listed in 802.1-D and
> the functionality they provide, as described in 3.1).

Obviously there is no common view what RFC 1493 was trying to say in
section 3.2.* and this is why I orginally liked to keep some rather
vague text. In practical terms, I have never seen a bridge which did
not implement the seven system scalars so from a practical perspective,
this whole debate is really a mood point and a waste of time.
 
> Section 3.2.2: I believe Juergen's proposed ext that says
> 'Implementation of the BRIDGE-MIB module requires that the following
> objects of the IF-MIB module are implemented' is inaccurate in its
> list, as I describe above.

It boils down to how you read the first paragraph in 3.2.2. My reading 
is that it says segments are considered subnetworks from the interfaces 
point of view and that the interfaces group is mandatory for all systems. 
Again, I have never seen a bridge which did not implement the full 
interfaces group.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Fri Jan 28 05:14:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14662;
	Fri, 28 Jan 2005 05:14:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuTQK-0000Is-EV; Fri, 28 Jan 2005 05:32:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuT7u-0004KX-MT; Fri, 28 Jan 2005 05:13:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuT3O-00035Q-9v
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 05:08:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14255
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 05:08:36 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuTKh-000093-Bm
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 05:26:31 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 976E1D7A0;
	Fri, 28 Jan 2005 11:08:06 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 19667-06; Fri, 28 Jan 2005 11:08:05 +0100 (CET)
Received: from james (unknown [10.50.242.227])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id A96A9C96E;
	Fri, 28 Jan 2005 11:08:05 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CuUhQ-00011A-P6; Fri, 28 Jan 2005 12:54:04 +0100
Date: Fri, 28 Jan 2005 12:54:04 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050128115404.GC3782@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	"'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
	"'C. M. Heard'" <heard@pobox.com>,
	"'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
References: <200501280134.UAA20844@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501280134.UAA20844@ietf.org>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Wijnen,
	Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
 
> If, for accuracy reasons, we're going to list required objects from
> other mib modules, then we need to be accurate.

Here is another proposal.

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not
   been included in this MIB module because they overlap with objects
   in other MIB modules applicable to a bridge implementing this MIB
   module.

3.2.1  Relationship to the SNMPv2-MIB

   The SNMPv2-MIB [RFC3418] defines objects that are generally
   applicable to managed devices. These objects apply to the device as
   a whole irrespective of whether the device's sole functionality is
   bridging, or whether bridging is only a subset of the device's
   functionality. 

   As explained in section 3.1, full support for the 802.1D management
   objects requires that the objects sysDescr and sysUpTime of the
   SNMPv2-MIB [RFC3418] are implemented. Note that compliance to the
   current SNMPv2-MIB module requires additional objects and
   notifications to be implemented as specified in RFC 3418 [RFC3418].

3.2.2  Relationship to the IF-MIB

   The IF-MIB [RFC2863] defines managed objects used for managing
   network interface. A network interface is thought of as being
   attached to a `subnetwork'. (Note that this term is not to be
   confused with `subnet' which refers to an addressing partitioning
   scheme used in the Internet suite of protocols.)  The term
   'segment' is used in this memo to refer to such a subnetwork,
   whether it be an Ethernet segment, a 'ring', a WAN link, or even an
   X.25 virtual circuit.

   As explained in section 3.1, full support for the 802.1D management
   objects requires that the objects ifIndex, ifType, ifDescr,
   ifPhysAddress, and ifLastChange of the IF-MIB [RFC2863] are
   implemented. Note that compliance to the current IF-MIB module
   requires additional objects and notifications to be implemented as
   specified in RFC 2863 [RFC2863].

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Fri Jan 28 08:41:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00095;
	Fri, 28 Jan 2005 08:41:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuWeV-00055P-Pd; Fri, 28 Jan 2005 08:59:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuWLc-0002K5-If; Fri, 28 Jan 2005 08:39:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuW98-00084n-Tv
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 08:26:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28739
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 08:26:45 -0500 (EST)
Message-Id: <200501281326.IAA28739@ietf.org>
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuWQT-0004kk-Pq
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 08:44:42 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc11) with SMTP
	id <2005012813261201300k9care>; Fri, 28 Jan 2005 13:26:13 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: <j.schoenwaelder@iu-bremen.de>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Fri, 28 Jan 2005 08:26:11 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <20050128074920.GB2459@james>
Thread-Index: AcUFDeJXJXNxU4PgQPmcZmrOGI5qzwALAcgg
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Wijnen,
	Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit

Hi Juergen,

Personally, I thought the original vague text was fine, as was the
original reference to RFC1213.
I agree that most implementations would simply do all seven system
objects, and similarly for interfaces.

But we have competing interests. You and Bert want to get rid of
references to RFC1213. Mike wants to get rid of inaccurate statements
about relationships to other mibs. I would like to keep the RFC1213
reference because compatibility with RFC1493 has been the primary
goal, but unless others in the WG speak up and say that such
compliance is the consensus and that RFC1213 is fine, as co-chair, I
need to try to adjudicate the competing consensuses.

One consensus is that we shouldn't use a reference to RFC1213. This is
the view of you and Bert; we have two persons, one being an O&M AD.
Mike and I are willing to accept that using it is undesirable, but not
critical.
Mike tells us that the OPS AD insists on accurate cross-document
dependencies; again, we have two persons, one being an AD. (We haven't
heard David actually say this however). 

Unfortunately, these two views are hard to reconcile; if you point to
RFC3418 and RFC2863 instead of RFC1213, the statements become
inaccurate; if you point to the available confirmance clauses, the
document becomes inaccurate; if you list all seven system objects and
the many interfaces objects as dependencies, the document becomes
inaccurate.

Me, I want see the document finished so we can move on to other
documents in the WG charter, and move toward WG closure. What I see is
a debate between two entrenched positions, neither of which helps an
operator manage a device. This debate is all about IETF publication
process and neither way of specifying the relationship between mib
modules offers anything substantive to an operator.

Will you yield on your insistence to not use RFC1213? Bert, will you
yield on this point? If so, consensus could move to "while we are
referenceing RFC1213, and that may be undesirable, using RFC1213 in
the statement of relationships between mib modules is in fact the
closest we can get to accurately portraying the original intent, and
therefore its usage should be acceptable."

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
> Sent: Friday, January 28, 2005 2:49 AM
> To: David B Harrington
> Cc: 'Wijnen, Bert (Bert)'; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> Subject: Re: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
> 
> [...]
>  
> > --- comments on Juergen's proposed text:
> > Section 3.2.1: I believe Juergen's proposed text that says
> > 'Implementation of the BRIDGE-MIB module requires
> > that at least ... are implemented' is inaccurate; this mib 
> module can
> > be implemented without those objects if desired, but you will miss
> > some of the objects recommended by 802.1-D, and the 
> functionality they
> > provide (but then even if you implement this mib module plus those
> > objects, you'll still be missing some objects listed in 802.1-D
and
> > the functionality they provide, as described in 3.1).
> 
> Obviously there is no common view what RFC 1493 was trying to say in
> section 3.2.* and this is why I orginally liked to keep some rather
> vague text. In practical terms, I have never seen a bridge which did
> not implement the seven system scalars so from a practical 
> perspective,
> this whole debate is really a mood point and a waste of time.
>  
> > Section 3.2.2: I believe Juergen's proposed ext that says
> > 'Implementation of the BRIDGE-MIB module requires that the
following
> > objects of the IF-MIB module are implemented' is inaccurate in its
> > list, as I describe above.
> 
> It boils down to how you read the first paragraph in 3.2.2. 
> My reading 
> is that it says segments are considered subnetworks from the 
> interfaces 
> point of view and that the interfaces group is mandatory for 
> all systems. 
> Again, I have never seen a bridge which did not implement the full 
> interfaces group.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> 



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


From bridge-mib-bounces@ietf.org  Fri Jan 28 09:11:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02724;
	Fri, 28 Jan 2005 09:11:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuX80-0005mt-0h; Fri, 28 Jan 2005 09:29:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuWin-0007qp-VG; Fri, 28 Jan 2005 09:03:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuWWr-0004w5-U8
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 08:51:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01368
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 08:51:16 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuWoB-0005KC-3N
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 09:09:13 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j0SDoghn020639
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 07:50:43 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP486SA>; Fri, 28 Jan 2005 14:50:41 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506497E5B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: dbharrington@comcast.net, j.schoenwaelder@iu-bremen.de
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Fri, 28 Jan 2005 14:50:36 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f

And so....

if the text about which objects of other modules moves to the
MODULE COMPLIANCE then you can keep a deprecated MODULE-COMPLIANCE
that exactly matches rfc1493 and create a new one that matches the
desire (of some) for moving away from RFC1213 depoendecy (if it is
listed in a deprecated MODULE-COMPLIANCE< then I think an Informative
ref is fine. The new MODULE-COMPLIANCE can refer to 3418 and 2863.
(which then become normative)

Does that help?

Bert

> -----Original Message-----
> From: David B Harrington [mailto:dbharrington@comcast.net]
> Sent: Friday, January 28, 2005 14:26
> To: j.schoenwaelder@iu-bremen.de
> Cc: 'Wijnen, Bert (Bert)'; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> 
> Hi Juergen,
> 
> Personally, I thought the original vague text was fine, as was the
> original reference to RFC1213.
> I agree that most implementations would simply do all seven system
> objects, and similarly for interfaces.
> 
> But we have competing interests. You and Bert want to get rid of
> references to RFC1213. Mike wants to get rid of inaccurate statements
> about relationships to other mibs. I would like to keep the RFC1213
> reference because compatibility with RFC1493 has been the primary
> goal, but unless others in the WG speak up and say that such
> compliance is the consensus and that RFC1213 is fine, as co-chair, I
> need to try to adjudicate the competing consensuses.
> 
> One consensus is that we shouldn't use a reference to RFC1213. This is
> the view of you and Bert; we have two persons, one being an O&M AD.
> Mike and I are willing to accept that using it is undesirable, but not
> critical.
> Mike tells us that the OPS AD insists on accurate cross-document
> dependencies; again, we have two persons, one being an AD. (We haven't
> heard David actually say this however). 
> 
> Unfortunately, these two views are hard to reconcile; if you point to
> RFC3418 and RFC2863 instead of RFC1213, the statements become
> inaccurate; if you point to the available confirmance clauses, the
> document becomes inaccurate; if you list all seven system objects and
> the many interfaces objects as dependencies, the document becomes
> inaccurate.
> 
> Me, I want see the document finished so we can move on to other
> documents in the WG charter, and move toward WG closure. What I see is
> a debate between two entrenched positions, neither of which helps an
> operator manage a device. This debate is all about IETF publication
> process and neither way of specifying the relationship between mib
> modules offers anything substantive to an operator.
> 
> Will you yield on your insistence to not use RFC1213? Bert, will you
> yield on this point? If so, consensus could move to "while we are
> referenceing RFC1213, and that may be undesirable, using RFC1213 in
> the statement of relationships between mib modules is in fact the
> closest we can get to accurately portraying the original intent, and
> therefore its usage should be acceptable."
> 
> David Harrington
> dbharrington@comcast.net
> co-chair, IETF Bridge WG
>  
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
> > Sent: Friday, January 28, 2005 2:49 AM
> > To: David B Harrington
> > Cc: 'Wijnen, Bert (Bert)'; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> > Subject: Re: [Bridge-mib] Re:
> Draft-iet-bridge-bridgemib-smiv2-09.txt
> > 
> > On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
> > 
> > [...]
> >  
> > > --- comments on Juergen's proposed text:
> > > Section 3.2.1: I believe Juergen's proposed text that says
> > > 'Implementation of the BRIDGE-MIB module requires
> > > that at least ... are implemented' is inaccurate; this mib 
> > module can
> > > be implemented without those objects if desired, but you will miss
> > > some of the objects recommended by 802.1-D, and the 
> > functionality they
> > > provide (but then even if you implement this mib module plus those
> > > objects, you'll still be missing some objects listed in 802.1-D
> and
> > > the functionality they provide, as described in 3.1).
> > 
> > Obviously there is no common view what RFC 1493 was trying to say in
> > section 3.2.* and this is why I orginally liked to keep some rather
> > vague text. In practical terms, I have never seen a bridge which did
> > not implement the seven system scalars so from a practical 
> > perspective,
> > this whole debate is really a mood point and a waste of time.
> >  
> > > Section 3.2.2: I believe Juergen's proposed ext that says
> > > 'Implementation of the BRIDGE-MIB module requires that the
> following
> > > objects of the IF-MIB module are implemented' is inaccurate in its
> > > list, as I describe above.
> > 
> > It boils down to how you read the first paragraph in 3.2.2. 
> > My reading 
> > is that it says segments are considered subnetworks from the 
> > interfaces 
> > point of view and that the interfaces group is mandatory for 
> > all systems. 
> > Again, I have never seen a bridge which did not implement the full 
> > interfaces group.
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder		    International 
> University Bremen
> > <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> > 28725 Bremen, Germany
> > 
> 
> 

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


From bridge-mib-bounces@ietf.org  Fri Jan 28 11:16:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14051;
	Fri, 28 Jan 2005 11:16:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuZ4N-0000S6-Uh; Fri, 28 Jan 2005 11:34:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuYVO-0003qS-Dl; Fri, 28 Jan 2005 10:57:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuYJt-0000iS-Rn
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 10:46:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10344
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 10:45:59 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuYbF-0007rl-FN
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 11:03:58 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 82B9AD8CC;
	Fri, 28 Jan 2005 16:45:22 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 07015-06; Fri, 28 Jan 2005 16:45:21 +0100 (CET)
Received: from james (unknown [10.50.242.227])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 847B5D4E1;
	Fri, 28 Jan 2005 16:45:21 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CuZxo-00017V-Gs; Fri, 28 Jan 2005 18:31:20 +0100
Date: Fri, 28 Jan 2005 18:31:20 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Message-ID: <20050128173120.GB4193@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>,
	"'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,
	"'C. M. Heard'" <heard@pobox.com>,
	"'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
References: <20050128074920.GB2459@james>
	<20050128132614.55389D6EA@hermes.iu-bremen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050128132614.55389D6EA@hermes.iu-bremen.de>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: "'C. M. Heard'" <heard@pobox.com>,
        "'Wijnen,
	Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

On Fri, Jan 28, 2005 at 08:26:11AM -0500, David B Harrington wrote:
 
> But we have competing interests. You and Bert want to get rid of
> references to RFC1213. Mike wants to get rid of inaccurate statements
> about relationships to other mibs. I would like to keep the RFC1213
> reference because compatibility with RFC1493 has been the primary
> goal, but unless others in the WG speak up and say that such
> compliance is the consensus and that RFC1213 is fine, as co-chair, I
> need to try to adjudicate the competing consensuses.

I don't think RFC1213 is the issue. The confusion I think is more on
the interpretation of the following paragraph:

   In MIB-II, the 'system' group is defined as being mandatory for all
   systems such that each managed entity contains one instance of each
   object in the 'system' group.  Thus, those objects apply to the
   entity as a whole irrespective of whether the entity's sole
   functionality is bridging, or whether bridging is only a subset of
   the entity's functionality.

I think it is clear what 'system' group in RFC1213 stands for. What is
less clear is whether the text conveys a requirement that the 'system'
group in RFC1213 is mandatory to implement for bridges. The other
interpretation I have heard is that only the sys* objects listed in
section 3.1 are mandatory if you want to comply to the IEEE 802.1d
definition while the BRIDGE-MIB does not require any of them to be
implemented. This is what I tried to capture in my latest proposal.

Once we agree what RFC 1493 section 3.2 really wants to say, we should
be able to phrase that same thing in terms of the SNMPv2-MIB and the
IF-MIB. I have posted two concrete proposals trying to cover the two
interpretations I have identified above. I am happy with either one.
If both don't work, someone should post another one and then we need 
to determine concensus which one is the correct one to choose.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From bridge-mib-bounces@ietf.org  Fri Jan 28 12:35:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21736;
	Fri, 28 Jan 2005 12:35:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuaJX-0002i1-NG; Fri, 28 Jan 2005 12:53:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuZts-0005iK-0H; Fri, 28 Jan 2005 12:27:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuZs1-0005CI-36
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 12:25:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20804
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 12:25:18 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cua9O-0002PY-0v
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 12:43:18 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j0SHOlaD003625
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 09:24:47 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j0SHOqSu022099;
	Fri, 28 Jan 2005 09:24:52 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j0SHOp0i022090; Fri, 28 Jan 2005 09:24:52 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Fri, 28 Jan 2005 09:24:51 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
In-Reply-To: <20050128115404.GC3782@james>
Message-ID: <Pine.LNX.4.10.10501280922460.20492-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

This proposal looks good to me.  //cmh

On Fri, 28 Jan 2005, Juergen Schoenwaelder wrote:

> On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
>  
> > If, for accuracy reasons, we're going to list required objects from
> > other mib modules, then we need to be accurate.
> 
> Here is another proposal.
> 
> 3.2  Relationship to Other MIB Modules
> 
>    As described above, some IEEE 802.1D management objects have not
>    been included in this MIB module because they overlap with objects
>    in other MIB modules applicable to a bridge implementing this MIB
>    module.
> 
> 3.2.1  Relationship to the SNMPv2-MIB
> 
>    The SNMPv2-MIB [RFC3418] defines objects that are generally
>    applicable to managed devices. These objects apply to the device as
>    a whole irrespective of whether the device's sole functionality is
>    bridging, or whether bridging is only a subset of the device's
>    functionality. 
> 
>    As explained in section 3.1, full support for the 802.1D management
>    objects requires that the objects sysDescr and sysUpTime of the
>    SNMPv2-MIB [RFC3418] are implemented. Note that compliance to the
>    current SNMPv2-MIB module requires additional objects and
>    notifications to be implemented as specified in RFC 3418 [RFC3418].
> 
> 3.2.2  Relationship to the IF-MIB
> 
>    The IF-MIB [RFC2863] defines managed objects used for managing
>    network interface. A network interface is thought of as being
>    attached to a `subnetwork'. (Note that this term is not to be
>    confused with `subnet' which refers to an addressing partitioning
>    scheme used in the Internet suite of protocols.)  The term
>    'segment' is used in this memo to refer to such a subnetwork,
>    whether it be an Ethernet segment, a 'ring', a WAN link, or even an
>    X.25 virtual circuit.
> 
>    As explained in section 3.1, full support for the 802.1D management
>    objects requires that the objects ifIndex, ifType, ifDescr,
>    ifPhysAddress, and ifLastChange of the IF-MIB [RFC2863] are
>    implemented. Note that compliance to the current IF-MIB module
>    requires additional objects and notifications to be implemented as
>    specified in RFC 2863 [RFC2863].
> 
> /js
> 
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany
> 


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


From bridge-mib-bounces@ietf.org  Fri Jan 28 13:05:11 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25010;
	Fri, 28 Jan 2005 13:05:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cuam0-0003be-6b; Fri, 28 Jan 2005 13:23:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuaU2-0005QV-8e; Fri, 28 Jan 2005 13:04:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuaRA-0004L8-I2
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 13:01:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24417
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 13:01:37 -0500 (EST)
Message-Id: <200501281801.NAA24417@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CuaiW-0003S7-Tv
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 13:19:38 -0500
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220])
	by comcast.net (rwcrmhc13) with SMTP
	id <20050128180107015009n7s8e>; Fri, 28 Jan 2005 18:01:07 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'C. M. Heard'" <heard@pobox.com>,
        "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Fri, 28 Jan 2005 13:01:05 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <Pine.LNX.4.10.10501280922460.20492-100000@shell4.bayarea.net>
Thread-Index: AcUFX87UArO+kC4YT661s7S4Fc/cnwAAzwAw
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit

This proposal looks good to me as well.

David Harrington
dbharrington@comcast.net 

> -----Original Message-----
> From: bridge-mib-bounces@ietf.org 
> [mailto:bridge-mib-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Friday, January 28, 2005 12:25 PM
> To: Bridge-Mib (E-mail)
> Subject: Re: [Bridge-mib] Re:
Draft-iet-bridge-bridgemib-smiv2-09.txt
> 
> This proposal looks good to me.  //cmh
> 
> On Fri, 28 Jan 2005, Juergen Schoenwaelder wrote:
> 
> > On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington
wrote:
> >  
> > > If, for accuracy reasons, we're going to list required 
> objects from
> > > other mib modules, then we need to be accurate.
> > 
> > Here is another proposal.
> > 
> > 3.2  Relationship to Other MIB Modules
> > 
> >    As described above, some IEEE 802.1D management objects have
not
> >    been included in this MIB module because they overlap 
> with objects
> >    in other MIB modules applicable to a bridge implementing this
MIB
> >    module.
> > 
> > 3.2.1  Relationship to the SNMPv2-MIB
> > 
> >    The SNMPv2-MIB [RFC3418] defines objects that are generally
> >    applicable to managed devices. These objects apply to 
> the device as
> >    a whole irrespective of whether the device's sole 
> functionality is
> >    bridging, or whether bridging is only a subset of the device's
> >    functionality. 
> > 
> >    As explained in section 3.1, full support for the 802.1D 
> management
> >    objects requires that the objects sysDescr and sysUpTime of the
> >    SNMPv2-MIB [RFC3418] are implemented. Note that compliance to
the
> >    current SNMPv2-MIB module requires additional objects and
> >    notifications to be implemented as specified in RFC 3418 
> [RFC3418].
> > 
> > 3.2.2  Relationship to the IF-MIB
> > 
> >    The IF-MIB [RFC2863] defines managed objects used for managing
> >    network interface. A network interface is thought of as being
> >    attached to a `subnetwork'. (Note that this term is not to be
> >    confused with `subnet' which refers to an addressing
partitioning
> >    scheme used in the Internet suite of protocols.)  The term
> >    'segment' is used in this memo to refer to such a subnetwork,
> >    whether it be an Ethernet segment, a 'ring', a WAN link, 
> or even an
> >    X.25 virtual circuit.
> > 
> >    As explained in section 3.1, full support for the 802.1D 
> management
> >    objects requires that the objects ifIndex, ifType, ifDescr,
> >    ifPhysAddress, and ifLastChange of the IF-MIB [RFC2863] are
> >    implemented. Note that compliance to the current IF-MIB module
> >    requires additional objects and notifications to be 
> implemented as
> >    specified in RFC 2863 [RFC2863].
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder		    International 
> University Bremen
> > <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
> 28725 Bremen, Germany
> > 
> 
> 
> _______________________________________________
> 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 bridge-mib-bounces@ietf.org  Fri Jan 28 13:42:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28470;
	Fri, 28 Jan 2005 13:42:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CubMT-0004Zx-GG; Fri, 28 Jan 2005 14:00:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cuawt-0003HE-6q; Fri, 28 Jan 2005 13:34:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cuamn-0000fs-2x
	for bridge-mib@megatron.ietf.org; Fri, 28 Jan 2005 13:24:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26648
	for <bridge-mib@ietf.org>; Fri, 28 Jan 2005 13:23:57 -0500 (EST)
Received: from ranger.systems.pipex.net ([62.241.162.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cub49-00043v-Rm
	for bridge-mib@ietf.org; Fri, 28 Jan 2005 13:41:58 -0500
Received: from pc6 (1Cust215.tnt8.lnd4.gbr.da.uu.net [62.188.137.215])
	by ranger.systems.pipex.net (Postfix) with SMTP id E889BE000227;
	Fri, 28 Jan 2005 18:23:23 +0000 (GMT)
Message-ID: <02f401c5055d$d6ca3280$0601a8c0@pc6>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: <dbharrington@comcast.net>, <j.schoenwaelder@iu-bremen.de>
References: <200501281326.IAA28739@ietf.org>
Subject: Re: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt
Date: Fri, 28 Jan 2005 18:19:50 +0100
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 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: 7bit
Cc: "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=subscribe>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Content-Transfer-Encoding: 7bit

I am content with references to RFC1213.

But then I don't read sections 3.1 and 3.2 as creating a dependency; rather they
explain why certain objects from the 1993 IEEE definition are not included;
normative reference? may be.  You could, but I think it would be wrong to do so,
create a much bigger 3.1 and 3.2 explaining why objects from 2002 IEEE
definition are not included:-)

I also think the reference to RFC1213 is the more accurate since for me, the
later MIB modules, particularly IF-MIB, bring in a lot more baggage which
RFC1213 never
had.  RFC1213 has a view of an interface that was right for its time, wrong now,
and I think what we have got (apart from SMIv2) is mostly a MIB module of that
era.

So I would leave RFC1213 in 3.1 and 3.2 adding a statement pointing out that
(yes, we do know that:-) these objects have been refined by later MIB modules
and making the later ones normative.

Tom Petch

----- Original Message -----
From: "David B Harrington" <dbharrington@comcast.net>
To: <j.schoenwaelder@iu-bremen.de>
Cc: "'C. M. Heard'" <heard@pobox.com>; "'Wijnen,Bert (Bert)'"
<bwijnen@lucent.com>; "'Bridge-Mib (E-mail)'" <bridge-mib@ietf.org>
Sent: Friday, January 28, 2005 2:26 PM
Subject: RE: [Bridge-mib] Re: Draft-iet-bridge-bridgemib-smiv2-09.txt


> Hi Juergen,
>
> Personally, I thought the original vague text was fine, as was the
> original reference to RFC1213.
> I agree that most implementations would simply do all seven system
> objects, and similarly for interfaces.
>
> But we have competing interests. You and Bert want to get rid of
> references to RFC1213. Mike wants to get rid of inaccurate statements
> about relationships to other mibs. I would like to keep the RFC1213
> reference because compatibility with RFC1493 has been the primary
> goal, but unless others in the WG speak up and say that such
> compliance is the consensus and that RFC1213 is fine, as co-chair, I
> need to try to adjudicate the competing consensuses.
>
> One consensus is that we shouldn't use a reference to RFC1213. This is
> the view of you and Bert; we have two persons, one being an O&M AD.
> Mike and I are willing to accept that using it is undesirable, but not
> critical.
> Mike tells us that the OPS AD insists on accurate cross-document
> dependencies; again, we have two persons, one being an AD. (We haven't
> heard David actually say this however).
>
> Unfortunately, these two views are hard to reconcile; if you point to
> RFC3418 and RFC2863 instead of RFC1213, the statements become
> inaccurate; if you point to the available confirmance clauses, the
> document becomes inaccurate; if you list all seven system objects and
> the many interfaces objects as dependencies, the document becomes
> inaccurate.
>
> Me, I want see the document finished so we can move on to other
> documents in the WG charter, and move toward WG closure. What I see is
> a debate between two entrenched positions, neither of which helps an
> operator manage a device. This debate is all about IETF publication
> process and neither way of specifying the relationship between mib
> modules offers anything substantive to an operator.
>
> Will you yield on your insistence to not use RFC1213? Bert, will you
> yield on this point? If so, consensus could move to "while we are
> referenceing RFC1213, and that may be undesirable, using RFC1213 in
> the statement of relationships between mib modules is in fact the
> closest we can get to accurately portraying the original intent, and
> therefore its usage should be acceptable."
>
> David Harrington
> dbharrington@comcast.net
> co-chair, IETF Bridge WG
>
>
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de]
> > Sent: Friday, January 28, 2005 2:49 AM
> > To: David B Harrington
> > Cc: 'Wijnen, Bert (Bert)'; 'C. M. Heard'; 'Bridge-Mib (E-mail)'
> > Subject: Re: [Bridge-mib] Re:
> Draft-iet-bridge-bridgemib-smiv2-09.txt
> >
> > On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
> >
> > [...]
> >
> > > --- comments on Juergen's proposed text:
> > > Section 3.2.1: I believe Juergen's proposed text that says
> > > 'Implementation of the BRIDGE-MIB module requires
> > > that at least ... are implemented' is inaccurate; this mib
> > module can
> > > be implemented without those objects if desired, but you will miss
> > > some of the objects recommended by 802.1-D, and the
> > functionality they
> > > provide (but then even if you implement this mib module plus those
> > > objects, you'll still be missing some objects listed in 802.1-D
> and
> > > the functionality they provide, as described in 3.1).
> >
> > Obviously there is no common view what RFC 1493 was trying to say in
> > section 3.2.* and this is why I orginally liked to keep some rather
> > vague text. In practical terms, I have never seen a bridge which did
> > not implement the seven system scalars so from a practical
> > perspective,
> > this whole debate is really a mood point and a waste of time.
> >
> > > Section 3.2.2: I believe Juergen's proposed ext that says
> > > 'Implementation of the BRIDGE-MIB module requires that the
> following
> > > objects of the IF-MIB module are implemented' is inaccurate in its
> > > list, as I describe above.
> >
> > It boils down to how you read the first paragraph in 3.2.2.
> > My reading
> > is that it says segments are considered subnetworks from the
> > interfaces
> > point of view and that the interfaces group is mandatory for
> > all systems.
> > Again, I have never seen a bridge which did not implement the full
> > interfaces group.
> >
> > /js
> >
> > --
> > Juergen Schoenwaelder     International University Bremen
> > <http://www.eecs.iu-bremen.de/>     P.O. Box 750 561,
> > 28725 Bremen, Germany
> >
>
>
>
> _______________________________________________
> 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


