From mailman-bounces@ietf.org Fri Oct 1 06:37:10 2004 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 GAA15622 for ; Fri, 1 Oct 2004 06:37:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDKvD-0003wt-Uq for bridge-mib-archive@ietf.org; Fri, 01 Oct 2004 06:45:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDJhB-0002mE-04 for bridge-mib-archive@ietf.org; Fri, 01 Oct 2004 05:27:21 -0400 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: Date: Fri, 01 Oct 2004 05:12:06 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list 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 Tue Oct 5 18:57:57 2004 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 SAA21008 for ; Tue, 5 Oct 2004 18:57:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEyPF-0003Su-I8 for bridge-mib-archive@ietf.org; Tue, 05 Oct 2004 19:07:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEyBX-0000KO-PK; Tue, 05 Oct 2004 18:53:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEy78-00082j-0J for bridge-mib@megatron.ietf.org; Tue, 05 Oct 2004 18:48:58 -0400 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 SAA20106 for ; Tue, 5 Oct 2004 18:48:55 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEyGV-00023e-0O for bridge-mib@ietf.org; Tue, 05 Oct 2004 18:58:39 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 1AC2B998E; Wed, 6 Oct 2004 00:48:25 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 05387-07; Wed, 6 Oct 2004 00:48:24 +0200 (CEST) Received: from james (G503b.g.pppool.de [80.185.80.59]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id DAA35992C; Wed, 6 Oct 2004 00:48:23 +0200 (CEST) Received: from schoenw by james with local (Exim 4.34) id 1CEy6b-0000fr-Qb; Wed, 06 Oct 2004 00:48:25 +0200 Date: Wed, 6 Oct 2004 00:48:25 +0200 From: Juergen Schoenwaelder To: David B Harrington Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt Message-ID: <20041005224825.GA2498@james> Mail-Followup-To: David B Harrington , bridge-mib@ietf.org References: <200409301230.IAA15316@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409301230.IAA15316@ietf.org> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 2.9 (++) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 2.9 (++) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe On Thu, Sep 30, 2004 at 08:29:52AM -0400, David B Harrington wrote: > Hi, > > draft-ietf-ops-vlanid-tc-mib-00.txt has been submitted to for > publication as an I-D. > Please review this document and comment. > > If you read it and find nothing to which you strongly object, please > say so. If you have concerns about the content, or find typos or grammar > errors, please say so. In RFC 2674, I read the following: VlanIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A value used to index per-VLAN tables: values of 0 and 4095 are not permitted; if the value is between 1 and 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with global scope within a given bridged domain (see VlanId textual convention). If the value is greater than 4095 then it represents a VLAN with scope local to the particular agent, i.e. one without a global VLAN-ID assigned to it. Such VLANs are outside the scope of IEEE 802.1Q but it is convenient to be able to manage them in the same way using this MIB." SYNTAX Unsigned32 Note the language about values greater than 4095. The VLAN-ID-MIB defines things such as: VlanIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The VLAN ID that uniquely identifies a VLAN. It is the 12-bit VLAN ID used in the VLAN Tag header. The range is defined by the REFERENCEd specification. " REFERENCE "IEEE Std 802.1Q 2003 Edition, Virtual Bridged Local Area Networks. " SYNTAX Integer32 (1..4094) I think we need to speel out guidelines in which situations which TC should be used and why. As it stands, it is kind of confusing for me as an outsider. How are those local scope VLAN IDs used in practice? (I don't think they fit into tagged frames.) > Should this be a separate document, or should it be merged into > rfc2674bis? Please indicate your preference when commenting on the draft. Is there actually a plan to revise RFC 2674? /js -- Juergen Schoenwaelder International University Bremen 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 Oct 6 00:59:51 2004 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 AAA19628 for ; Wed, 6 Oct 2004 00:59:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF43X-00057d-Jn for bridge-mib-archive@ietf.org; Wed, 06 Oct 2004 01:09:39 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF3t3-0008UM-DY; Wed, 06 Oct 2004 00:58:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF3sQ-0008Mg-73 for bridge-mib@megatron.ietf.org; Wed, 06 Oct 2004 00:58:10 -0400 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 AAA19552 for ; Wed, 6 Oct 2004 00:58:07 -0400 (EDT) Message-Id: <200410060458.AAA19552@ietf.org> Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF41q-00054J-P5 for bridge-mib@ietf.org; Wed, 06 Oct 2004 01:07:55 -0400 Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (rwcrmhc12) with SMTP id <2004100604573701400rfmm0e>; Wed, 6 Oct 2004 04:57:38 +0000 From: "David B Harrington" To: Subject: RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt Date: Wed, 6 Oct 2004 00:57:37 -0400 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: <20041005224825.GA2498@james> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcSrLWzFtcsHeA0gSHOY4UxEjDJ96gALDmtw X-Spam-Score: 0.1 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Content-Transfer-Encoding: 7bit Cc: 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Content-Transfer-Encoding: 7bit Hi Juergen, Some vendors use 0 as "no vlan" and some use 0 as a wildcard. I believe other values are used for other local proprietary purposes. There has been debate about whether the TCs should permit the mib module designer to define special semantics per object, or whether the values should be standardized. I agree some guidelines for usage should be provided. Personally, I think it would be good to standardize the local vlan IDs for use in management, otherwise a manager application would need to know whether it was a box from vendor-A or vendor-B, or which mib module it is used in, to understand the semantics and present the info in a user-friendly manner. RFC2674bis (draft-ietf-bridge-ext-v2-02.txt) has been a product of this WG, but the draft expired in August. We expect to have a revision published before IETF61, possibly with TCs and usage guidelines included. David Harrington dbharrington@comcast.net Bridge-mib co-chair -----Original Message----- From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] On Behalf Of Juergen Schoenwaelder Sent: Tuesday, October 05, 2004 6:48 PM To: David B Harrington Cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt On Thu, Sep 30, 2004 at 08:29:52AM -0400, David B Harrington wrote: > Hi, > > draft-ietf-ops-vlanid-tc-mib-00.txt has been submitted to for > publication as an I-D. > Please review this document and comment. > > If you read it and find nothing to which you strongly object, please > say so. If you have concerns about the content, or find typos or > grammar errors, please say so. In RFC 2674, I read the following: VlanIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A value used to index per-VLAN tables: values of 0 and 4095 are not permitted; if the value is between 1 and 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with global scope within a given bridged domain (see VlanId textual convention). If the value is greater than 4095 then it represents a VLAN with scope local to the particular agent, i.e. one without a global VLAN-ID assigned to it. Such VLANs are outside the scope of IEEE 802.1Q but it is convenient to be able to manage them in the same way using this MIB." SYNTAX Unsigned32 Note the language about values greater than 4095. The VLAN-ID-MIB defines things such as: VlanIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The VLAN ID that uniquely identifies a VLAN. It is the 12-bit VLAN ID used in the VLAN Tag header. The range is defined by the REFERENCEd specification. " REFERENCE "IEEE Std 802.1Q 2003 Edition, Virtual Bridged Local Area Networks. " SYNTAX Integer32 (1..4094) I think we need to speel out guidelines in which situations which TC should be used and why. As it stands, it is kind of confusing for me as an outsider. How are those local scope VLAN IDs used in practice? (I don't think they fit into tagged frames.) > Should this be a separate document, or should it be merged into > rfc2674bis? Please indicate your preference when commenting on the draft. Is there actually a plan to revise RFC 2674? /js -- Juergen Schoenwaelder International University Bremen 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 Oct 6 02:49:03 2004 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 CAA24099 for ; Wed, 6 Oct 2004 02:49:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5lB-0001pG-Ve for bridge-mib-archive@ietf.org; Wed, 06 Oct 2004 02:58:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5as-0005p2-8E; Wed, 06 Oct 2004 02:48:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5a1-0005is-AQ for bridge-mib@megatron.ietf.org; Wed, 06 Oct 2004 02:47:17 -0400 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 CAA24042 for ; Wed, 6 Oct 2004 02:47:15 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5jR-0001le-B3 for bridge-mib@ietf.org; Wed, 06 Oct 2004 02:57:03 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 95DC899CB; Wed, 6 Oct 2004 08:46:43 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 24004-08; Wed, 6 Oct 2004 08:46:42 +0200 (CEST) Received: from james (unknown [212.201.46.187]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id 81620992C; Wed, 6 Oct 2004 08:46:42 +0200 (CEST) Received: from schoenw by james with local (Exim 4.34) id 1CF5ZS-0000Wq-7L; Wed, 06 Oct 2004 08:46:42 +0200 Date: Wed, 6 Oct 2004 08:46:41 +0200 From: Juergen Schoenwaelder To: David B Harrington Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt Message-ID: <20041006064641.GB1745@james> Mail-Followup-To: David B Harrington , bridge-mib@ietf.org References: <20041005224825.GA2498@james> <20041006045739.7186698D3@hermes.iu-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041006045739.7186698D3@hermes.iu-bremen.de> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 On Wed, Oct 06, 2004 at 12:57:37AM -0400, David B Harrington wrote: > Some vendors use 0 as "no vlan" and some use 0 as a wildcard. I > believe other values are used for other local proprietary purposes. > There has been debate about whether the TCs should permit the mib > module designer to define special semantics per object, or whether the > values should be standardized. > > I agree some guidelines for usage should be provided. > > Personally, I think it would be good to standardize the local vlan IDs > for use in management, otherwise a manager application would need to > know whether it was a box from vendor-A or vendor-B, or which mib > module it is used in, to understand the semantics and present the info > in a user-friendly manner. Well, my concern was about value > 4095 which RFC 2674 explicitely permits in the VlanIndex TC but not in the VlanId TC and Bert's MIB module does not discuss this either. In principle, if RFC 2674 is indeed revised in due time, I think putting the VLAN TCs in an update of the Q-BRIDGE-MIB probably not a bad thing. But even then it needs to be spelled out clearly which TC should be used in which situation. However, if the Q-BRIDGE-MIB update ends up taking years to be finalized, then going forward with Bert's ID might be easier. /js -- Juergen Schoenwaelder International University Bremen 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 Oct 15 12:33:38 2004 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 MAA17996 for ; Fri, 15 Oct 2004 12:33:37 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIVCo-0003gD-LU for bridge-mib-archive@ietf.org; Fri, 15 Oct 2004 12:45:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIUqE-00016V-1O; Fri, 15 Oct 2004 12:22:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIUfj-0005xE-Uy for bridge-mib@megatron.ietf.org; Fri, 15 Oct 2004 12:11:16 -0400 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 MAA16633 for ; Fri, 15 Oct 2004 12:11:12 -0400 (EDT) Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIUr8-0003Cl-5b for bridge-mib@ietf.org; Fri, 15 Oct 2004 12:23:02 -0400 Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9FGAbt01534; Fri, 15 Oct 2004 11:10:38 -0500 (CDT) Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Oct 2004 09:10:37 -0700 Message-ID: <0A11633F61BD9F40B43ABCC694004F93043BCE9B@zsc3c026.us.nortel.com> From: "David Levi" To: "'dbharrington@comcast.net'" , j.schoenwaelder@iu-bremen.de Subject: RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt Date: Fri, 15 Oct 2004 09:10:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.5 (/) X-Scan-Signature: 10dcc25e55b9b5f7d6ded516404bdc4c Cc: 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: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0945070720==" Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 07e9b4af03a165a413ec6e4d37ae537b 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. --===============0945070720== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4B2D1.3597AA5C" 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_01C4B2D1.3597AA5C Content-Type: text/plain Hi David, I've updated all the boilerplate text and references, and added the new TCs. Can I get some suggested text for the usage guidelines for the new TCs? You mentioned in a previous e-mail that there were some issues on RT, but I can't find anything there. Any pointers on where to look? -Dave -----Original Message----- From: bridge-mib-bounces@ietf.org [mailto:bridge-mib-bounces@ietf.org] Sent: Wednesday, October 06, 2004 12:58 AM To: j.schoenwaelder@iu-bremen.de Cc: bridge-mib@ietf.org Subject: RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt Hi Juergen, Some vendors use 0 as "no vlan" and some use 0 as a wildcard. I believe other values are used for other local proprietary purposes. There has been debate about whether the TCs should permit the mib module designer to define special semantics per object, or whether the values should be standardized. I agree some guidelines for usage should be provided. Personally, I think it would be good to standardize the local vlan IDs for use in management, otherwise a manager application would need to know whether it was a box from vendor-A or vendor-B, or which mib module it is used in, to understand the semantics and present the info in a user-friendly manner. RFC2674bis (draft-ietf-bridge-ext-v2-02.txt) has been a product of this WG, but the draft expired in August. We expect to have a revision published before IETF61, possibly with TCs and usage guidelines included. David Harrington dbharrington@comcast.net Bridge-mib co-chair -----Original Message----- From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] On Behalf Of Juergen Schoenwaelder Sent: Tuesday, October 05, 2004 6:48 PM To: David B Harrington Cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt On Thu, Sep 30, 2004 at 08:29:52AM -0400, David B Harrington wrote: > Hi, > > draft-ietf-ops-vlanid-tc-mib-00.txt has been submitted to for > publication as an I-D. > Please review this document and comment. > > If you read it and find nothing to which you strongly object, please > say so. If you have concerns about the content, or find typos or > grammar errors, please say so. In RFC 2674, I read the following: VlanIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A value used to index per-VLAN tables: values of 0 and 4095 are not permitted; if the value is between 1 and 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with global scope within a given bridged domain (see VlanId textual convention). If the value is greater than 4095 then it represents a VLAN with scope local to the particular agent, i.e. one without a global VLAN-ID assigned to it. Such VLANs are outside the scope of IEEE 802.1Q but it is convenient to be able to manage them in the same way using this MIB." SYNTAX Unsigned32 Note the language about values greater than 4095. The VLAN-ID-MIB defines things such as: VlanIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The VLAN ID that uniquely identifies a VLAN. It is the 12-bit VLAN ID used in the VLAN Tag header. The range is defined by the REFERENCEd specification. " REFERENCE "IEEE Std 802.1Q 2003 Edition, Virtual Bridged Local Area Networks. " SYNTAX Integer32 (1..4094) I think we need to speel out guidelines in which situations which TC should be used and why. As it stands, it is kind of confusing for me as an outsider. How are those local scope VLAN IDs used in practice? (I don't think they fit into tagged frames.) > Should this be a separate document, or should it be merged into > rfc2674bis? Please indicate your preference when commenting on the draft. Is there actually a plan to revise RFC 2674? /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib ------_=_NextPart_001_01C4B2D1.3597AA5C Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt

Hi David,

I've updated all the boilerplate text and references, = and added the new TCs.
Can I get some suggested text for the usage = guidelines for the new TCs?

You mentioned in a previous e-mail that there were = some issues on RT, but
I can't find anything there.  Any pointers on = where to look?

-Dave

-----Original Message-----
From: bridge-mib-bounces@ietf.org [mailto:bridge-mib-bounces@ie= tf.org]
Sent: Wednesday, October 06, 2004 12:58 AM
To: j.schoenwaelder@iu-bremen.de
Cc: bridge-mib@ietf.org
Subject: RE: [Bridge-mib] = draft-ietf-ops-vlanid-tc-mib-00.txt


Hi Juergen,

Some vendors use 0 as "no vlan" and some = use 0 as a wildcard. I believe other values are used for other local = proprietary purposes. There has been debate about whether the TCs = should permit the mib module designer to define special semantics per = object, or whether the values should be standardized.

I agree some guidelines for usage should be = provided. 

Personally, I think it would be good to standardize = the local vlan IDs for use in management, otherwise a manager = application would need to know whether it was a box from vendor-A or = vendor-B, or which mib module it is used in, to understand the = semantics and present the info in a user-friendly manner.

RFC2674bis (draft-ietf-bridge-ext-v2-02.txt) has been = a product of this WG, but the draft expired in August. We expect to = have a revision published before IETF61, possibly with TCs and usage = guidelines included.

David Harrington
dbharrington@comcast.net
Bridge-mib co-chair
 
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] = On Behalf Of Juergen Schoenwaelder
Sent: Tuesday, October 05, 2004 6:48 PM
To: David B Harrington
Cc: bridge-mib@ietf.org
Subject: Re: [Bridge-mib] = draft-ietf-ops-vlanid-tc-mib-00.txt

On Thu, Sep 30, 2004 at 08:29:52AM -0400, David B = Harrington wrote:
> Hi,
>
> draft-ietf-ops-vlanid-tc-mib-00.txt has been = submitted to for
> publication as an I-D.
> Please review this document and comment.
>
> If you read it and find nothing to which you = strongly object, please

> say so. If you have concerns about the content, = or find typos or
> grammar errors, please say so.

In RFC 2674, I read the following:

VlanIndex ::=3D TEXTUAL-CONVENTION
    = STATUS      current
    DESCRIPTION
        "A = value used to index per-VLAN tables: values of 0 and
        4095 are = not permitted; if the value is between 1 and
        4094 = inclusive, it represents an IEEE 802.1Q VLAN-ID with
        global = scope within a given bridged domain (see VlanId
        textual = convention).  If the value is greater than 4095
        then it = represents a VLAN with scope local to the
        = particular agent, i.e. one without a global VLAN-ID
        assigned = to it. Such VLANs are outside the scope of
        IEEE = 802.1Q but it is convenient to be able to manage them
        in the = same way using this MIB."
    = SYNTAX      Unsigned32

Note the language about values greater than 4095. The = VLAN-ID-MIB defines things such as:

VlanIdentifier        ::=3D = TEXTUAL-CONVENTION
    = DISPLAY-HINT     "d"
    = STATUS           = current
    = DESCRIPTION      "The VLAN ID that = uniquely identifies a VLAN.  It
          &nb= sp;           is the = 12-bit VLAN ID used in the VLAN Tag header.
          &nb= sp;           The = range is defined by the REFERENCEd specification.
          &nb= sp;          "
    = REFERENCE        "IEEE Std = 802.1Q 2003 Edition, Virtual Bridged
          &nb= sp;           Local = Area Networks.
          &nb= sp;          "
    = SYNTAX           = Integer32 (1..4094)

I think we need to speel out guidelines in which = situations which TC should be used and why. As it stands, it is kind of = confusing for me as an outsider. How are those local scope VLAN IDs = used in practice? (I don't think they fit into tagged = frames.)

 
> Should this be a separate document, or should = it be merged into
> rfc2674bis? Please indicate your preference = when commenting on the
draft.

Is there actually a plan to revise RFC 2674?

/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<= /FONT>

------_=_NextPart_001_01C4B2D1.3597AA5C-- --===============0945070720== 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 --===============0945070720==-- From bridge-mib-bounces@ietf.org Fri Oct 15 17:40:05 2004 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 RAA25283 for ; Fri, 15 Oct 2004 17:40:05 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIZzP-0006Ep-98 for bridge-mib-archive@ietf.org; Fri, 15 Oct 2004 17:51:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIZc3-0004H5-8I; Fri, 15 Oct 2004 17:27:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIZ8I-0004Oz-1P for bridge-mib@megatron.ietf.org; Fri, 15 Oct 2004 16:57:02 -0400 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 QAA17392 for ; Fri, 15 Oct 2004 16:56:59 -0400 (EDT) Message-Id: <200410152056.QAA17392@ietf.org> Received: from sccrmhc13.comcast.net ([204.127.202.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIZJj-0003tS-0M for bridge-mib@ietf.org; Fri, 15 Oct 2004 17:08:51 -0400 Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (sccrmhc13) with SMTP id <20041015205629016000p0npe>; Fri, 15 Oct 2004 20:56:30 +0000 From: "David B Harrington" To: Date: Fri, 15 Oct 2004 16:56:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcSy9bxa1pVbzGdjQhGIKLXkvYlPawAAiEKA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.1 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] FW: [New-work] FW: [802.1] P802.1ah, P802.1ai circulation of draft PARs under 30-day rule 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: 7bit FYI. > The following proposed new IEEE 802.1 work items may be of > interest to IETF Working Groups. Please note that these > proposed work items have not yet been approved. > > > Please find two draft PARs and corresponding 5c's at the following > locations: P802.1ah is a proposed project to develop a standard to scale multiple Provider Provisioned bridges. This work will be compatible with 802.1Q (Virtual LANs), 802.1ad (Provider Bridging), and 802.1ag. > > P802.1ah draft PAR and 5C: > > http://www.ieee802.org/1/files/public/docs2004/802-1ah-draft-p ar-for-30- > day-rule.htm > > http://www.ieee802.org/1/files/public/docs2004/802-1ah-5c.pdf P802.1ah is a proposed project to develop a standard (MRP) to improve topology conversion time for GVRP and GMRP protocols. > > P802.1ai draft PAR and 5C: > > http://www.ieee802.org/1/files/public/docs2004/802-1ai-draft-p ar-for-30- > day-rule.htm > > http://www.ieee802.org/1/files/public/docs2004/802-1ai-5c.pdf > > 802.1 intends to submit these pars to the closing SEC meeting > in November for approval for forwarding to NesCom. > No work associated with these projects will be done in the IETF. If the projects are approved, the MIB modules to manage these will be done in the IEEE 802.1 WG Please send any comments to the 802.1 mailing list. > > IEEE 802.1 list info: > http://www.ieee802.org/1/email-pages/sjqnf904.html > David Harrington dbharrington@comcast.net Bridge-mib co-chair _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From bridge-mib-bounces@ietf.org Thu Oct 21 21:17:01 2004 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 VAA20883 for ; Thu, 21 Oct 2004 21:17:01 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKoFw-000087-HE for bridge-mib-archive@ietf.org; Thu, 21 Oct 2004 21:30:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKlT5-0002RA-Pi; Thu, 21 Oct 2004 18:31:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKkAj-0002rL-QO for bridge-mib@megatron.ietf.org; Thu, 21 Oct 2004 17:08:33 -0400 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 RAA27355 for ; Thu, 21 Oct 2004 17:08:30 -0400 (EDT) Message-Id: <200410212108.RAA27355@ietf.org> Received: from sccrmhc13.comcast.net ([204.127.202.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKkNO-0000lU-5O for bridge-mib@ietf.org; Thu, 21 Oct 2004 17:21:40 -0400 Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (sccrmhc13) with SMTP id <20041021210754016000t3qve>; Thu, 21 Oct 2004 21:07:54 +0000 From: "David B Harrington" To: Date: Thu, 21 Oct 2004 17:07:54 -0400 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: AcS3sggmu5ADoRSuRLGD43KLhAD8QQ== X-Spam-Score: 0.1 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] IETF61 meeting slot 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Hi, I have requested a one-hour meeting slot at IETF61. The proposed agenda: 5 agenda bashing, blue-sheets, note-takers, etc 15 status of the documents, last call review status 20 Vlan TCs added to draft-ietf-bridgemib-bridge-extensions 20 the transition of MIB module responsibility to the IEEE 802.1 WG David Harrington dbharrington@comcast.net Bridge-mib co-chair _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From bridge-mib-bounces@ietf.org Fri Oct 22 07:11:57 2004 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 HAA23206 for ; Fri, 22 Oct 2004 07:11:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKxXk-0003fc-K7 for bridge-mib-archive@ietf.org; Fri, 22 Oct 2004 07:25:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKxCC-0004q0-Jh; Fri, 22 Oct 2004 07:02:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKx9K-0003UK-Cm for bridge-mib@megatron.ietf.org; Fri, 22 Oct 2004 06:59:58 -0400 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 GAA22083 for ; Fri, 22 Oct 2004 06:59:54 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKxM6-0003SU-9t for bridge-mib@ietf.org; Fri, 22 Oct 2004 07:13:11 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 7959E9A83 for ; Fri, 22 Oct 2004 12:59:23 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 24623-02; Fri, 22 Oct 2004 12:59:22 +0200 (CEST) Received: from james (facultypc-151.faculty.iu-bremen.de [212.201.48.151]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id B36559837; Fri, 22 Oct 2004 12:59:22 +0200 (CEST) Received: from schoenw by james with local (Exim 4.34) id 1CKx8k-0000eC-CN; Fri, 22 Oct 2004 12:59:22 +0200 Date: Fri, 22 Oct 2004 12:59:22 +0200 From: Juergen Schoenwaelder To: bridge-mib@ietf.org Message-ID: <20041022105922.GA2480@james> Mail-Followup-To: bridge-mib@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Bridge-mib] bridge mib revision 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 I am currently updating the BRIDGE-MIB to make it ready for last call. There is one addition which I do not understand and where I need your help. The following text got added to the description clause of the dot1dStaticAllowedToGoTo object: This exceeds the minimum required SNMP packet size supported. This is sufficient to allow the maximum 4096 ports now supported. dot1dStaticAllowedToGoTo is an OCTET STRING (SIZE (0..512)), so 4096 ports fit into 512 bytes. Can someone explain to me what this paragraph is trying to convey to the reader? /js -- Juergen Schoenwaelder International University Bremen 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 Oct 22 07:15:06 2004 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 HAA23930 for ; Fri, 22 Oct 2004 07:15:06 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKxan-0003kY-Bo for bridge-mib-archive@ietf.org; Fri, 22 Oct 2004 07:28:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKxM1-0007v3-V3; Fri, 22 Oct 2004 07:13:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKxFD-0005NW-8F for bridge-mib@megatron.ietf.org; Fri, 22 Oct 2004 07:06:03 -0400 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 HAA22606 for ; Fri, 22 Oct 2004 07:05:59 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKxRz-0003XY-Mu for bridge-mib@ietf.org; Fri, 22 Oct 2004 07:19:16 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 27A159A83 for ; Fri, 22 Oct 2004 13:05:30 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 24966-04; Fri, 22 Oct 2004 13:05:29 +0200 (CEST) Received: from james (facultypc-151.faculty.iu-bremen.de [212.201.48.151]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id 61C569FF3; Fri, 22 Oct 2004 13:05:23 +0200 (CEST) Received: from schoenw by james with local (Exim 4.34) id 1CKxEZ-0000eT-B5; Fri, 22 Oct 2004 13:05:23 +0200 Date: Fri, 22 Oct 2004 13:05:23 +0200 From: Juergen Schoenwaelder To: bridge-mib@ietf.org Message-ID: <20041022110523.GA2503@james> Mail-Followup-To: bridge-mib@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Bridge-mib] dot1dStpPortPathCost32 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 The revised BRIDGE-MIB adds dot1dStpPortPathCost32 and makes it mandatory. I think this is broken since existing deployed implementations won't support that object and thus are not compliant. Can someone please explain in which situations the increased range of dot1dStpPortPathCost32 is actually needed? Is this only relevant for rapid spanning tree? In that case, I think the object should be conditionally mandatory for boxes that do rapid spanning tree and the old one stays current, probably with a special value to use in case dot1dStpPortPathCost32 actually has the larger path cost. Please give advise. /js -- Juergen Schoenwaelder International University Bremen 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 Oct 22 18:15:51 2004 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 SAA01417 for ; Fri, 22 Oct 2004 18:15:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL7uB-0005Q9-3s for bridge-mib-archive@ietf.org; Fri, 22 Oct 2004 18:29:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL6l5-0000xV-Kw; Fri, 22 Oct 2004 17:15:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL641-00062q-WA for bridge-mib@megatron.ietf.org; Fri, 22 Oct 2004 16:31:06 -0400 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 QAA09458 for ; Fri, 22 Oct 2004 16:31:01 -0400 (EDT) Received: from pop-a065d01.pas.sa.earthlink.net ([207.217.121.248]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL6Gs-0006oK-4a for bridge-mib@ietf.org; Fri, 22 Oct 2004 16:44:22 -0400 Received: from h-69-3-92-124.snvacaid.dynamic.covad.net ([69.3.92.124] helo=oemcomputer) by pop-a065d01.pas.sa.earthlink.net with smtp (Exim 3.33 #1) id 1CL63w-0000VT-00 for bridge-mib@ietf.org; Fri, 22 Oct 2004 13:31:00 -0700 Message-ID: <004501c4b876$27fc14a0$7f1afea9@oemcomputer> From: "Randy Presuhn" To: References: <20041022105922.GA2480@james> Subject: Re: [Bridge-mib] bridge mib revision Date: Fri, 22 Oct 2004 13:31:46 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 X-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: bridge-mib.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Hi - > From: "Juergen Schoenwaelder" > To: > Sent: Friday, October 22, 2004 3:59 AM > Subject: [Bridge-mib] bridge mib revision > > I am currently updating the BRIDGE-MIB to make it ready for last call. > There is one addition which I do not understand and where I need your > help. The following text got added to the description clause of the > dot1dStaticAllowedToGoTo object: > > This exceeds the minimum required SNMP packet size > supported. This is sufficient to allow the maximum > 4096 ports now supported. > > dot1dStaticAllowedToGoTo is an OCTET STRING (SIZE (0..512)), so 4096 > ports fit into 512 bytes. Can someone explain to me what this paragraph > is trying to convey to the reader? ... It's a health warning, though it could be clearer. A value 512 bytes long would make the SNMP PDU larger than the 484 "minimum maximum" from RFC 3417 clause 3.2 second paragraph. Consequently, SNMP engines that are going to shovel this value around need to support more than that minimum maximum. Randy _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From bridge-mib-bounces@ietf.org Thu Oct 28 11:01:56 2004 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 LAA21590 for ; Thu, 28 Oct 2004 11:01:56 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNC0t-0003PU-Nl for bridge-mib-archive@ietf.org; Thu, 28 Oct 2004 11:16:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBYu-00029r-Un; Thu, 28 Oct 2004 10:47:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBQi-00089q-E8; Thu, 28 Oct 2004 10:39:08 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18444; Thu, 28 Oct 2004 10:39:07 -0400 (EDT) Message-Id: <200410281439.KAA18444@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, 28 Oct 2004 10:39:07 -0400 Cc: bridge-mib@ietf.org Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-07.txt X-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: bridge-mib.ietf.org List-Unsubscribe: , List-Post: List-Help: List-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-07.txt Pages : 44 Date : 2004-10-27 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-07.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-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-28105528.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-bridge-bridgemib-smiv2-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-28105528.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 Fri Oct 29 14:04:11 2004 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 OAA20188 for ; Fri, 29 Oct 2004 14:04:11 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNbL1-0004oN-W3 for bridge-mib-archive@ietf.org; Fri, 29 Oct 2004 14:19:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNb5h-0001RG-F2; Fri, 29 Oct 2004 14:03:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNb1G-0004s5-U6 for bridge-mib@megatron.ietf.org; Fri, 29 Oct 2004 13:58:34 -0400 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 NAA19695 for ; Fri, 29 Oct 2004 13:58:33 -0400 (EDT) Message-Id: <200410291758.NAA19695@ietf.org> Received: from sccrmhc11.comcast.net ([204.127.202.55]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNbFa-0004fu-6o for bridge-mib@ietf.org; Fri, 29 Oct 2004 14:13:23 -0400 Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (sccrmhc11) with SMTP id <20041029175802011002v4q5e>; Fri, 29 Oct 2004 17:58:02 +0000 From: "David B Harrington" To: Date: Fri, 29 Oct 2004 13:58:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcS9HPhoFnQC3wpqSbWpAaW6tR6YtgAv0BBgAAENHlA= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.1 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] Bridge WG agenda 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: , List-Post: List-Help: List-Subscribe: , Sender: bridge-mib-bounces@ietf.org Errors-To: bridge-mib-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7bit Hi, The Bridge WG is scheduled for a session at IETF61 on Tuesday 1700-1800. The initial agenda is: 5 agenda bashing 20 status of documents, last call review status 35 the transition to IEEE 802.1 If anybody has anything they believe should be discussed in this session, please speak up. David Harrington dbharrington@comcast.net Bridge-mib co-chair _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib