RE: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt

"Harrington, David" <dbh@enterasys.com> Tue, 26 November 2002 17:49 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13306 for <bridge-archive@odin.ietf.org>; Tue, 26 Nov 2002 12:49:17 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAQHpYf12246 for bridge-archive@odin.ietf.org; Tue, 26 Nov 2002 12:51:34 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQHoIv12189; Tue, 26 Nov 2002 12:50:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQHnBv12132 for <bridge-mib@optimus.ietf.org>; Tue, 26 Nov 2002 12:49:11 -0500
Received: from ctron-dnm.enterasys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13178 for <bridge-mib@ietf.org>; Tue, 26 Nov 2002 12:46:21 -0500 (EST)
Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id NAA13094 for <bridge-mib@ietf.org>; Tue, 26 Nov 2002 13:01:10 -0500 (EST)
Received: from unknown(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma013029; Tue, 26 Nov 02 13:00:59 -0500
Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Tue, 26 Nov 2002 12:49:11 -0500
Received: from nhrocmbx1.enterasys.com ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Tue, 26 Nov 2002 12:49:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt
Date: Tue, 26 Nov 2002 12:49:10 -0500
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA256EB2@NHROCMBX1.ets.enterasys.com>
Thread-Topic: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt
Thread-Index: AcKVYLEuSCIpfCCATgaR8Omvf3D/EQACVpaQAAEw2wAAAH3vkAAAsszw
From: "Harrington, David" <dbh@enterasys.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "Les Bell" <Les_Bell@eur.3com.com>, <bridge-mib@ietf.org>
X-OriginalArrivalTime: 26 Nov 2002 17:49:11.0040 (UTC) FILETIME=[204C2000:01C29574]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAQHnBv12133
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
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-Transfer-Encoding: 8bit

Hi,

I was merely checking to see if IEEE802.1 had reviewed it yet. I just wanted to be sure the two groups remain in sync, and I didn't know whether we were doing WG last call before synchronizing with them, or whether the sync with them (as currently written) had already been done. I assume discussion has occurred where they will adopt the updated version? I just wanted to understand how you guys are handling the sync.

dbh

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Tuesday, November 26, 2002 12:27 PM
> To: Romascanu, Dan (Dan); Harrington, David; Les Bell;
> bridge-mib@ietf.org
> Subject: RE: [Bridge-mib] Begin WG Last Call -
> draft-ietf-bridge-8021x-00.txt
> 
> 
> Sorry - you were asking about the 802.1 WG. My understanding 
> is that the document is similar to the one in the 802.1 
> standard annex, with some minor SNMP fixes. Dan
> 
> 
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) 
> > Sent: Tuesday, November 26, 2002 7:12 PM
> > To: Harrington, David; Les Bell; bridge-mib@ietf.org
> > Subject: RE: [Bridge-mib] Begin WG Last Call - 
> > draft-ietf-bridge-8021x-00.txt
> > 
> > 
> > This is the Last Call - our opportunity to read, comment and 
> > approve! Isn't it?
> > 
> > Dan
> > 
> > 
> > > -----Original Message-----
> > > From: Harrington, David [mailto:dbh@enterasys.com]
> > > Sent: Tuesday, November 26, 2002 6:37 PM
> > > To: Les Bell; bridge-mib@ietf.org
> > > Subject: RE: [Bridge-mib] Begin WG Last Call - 
> > > draft-ietf-bridge-8021x-00.txt
> > > 
> > > 
> > > Hi Les,
> > > 
> > > Has the IEEE 802.1X working group seen and approved the mib 
> > > as currently written?
> > > 
> > > dbh
> > > 
> > > > -----Original Message-----
> > > > From: Les Bell [mailto:Les_Bell@eur.3com.com]
> > > > Sent: Tuesday, November 26, 2002 10:24 AM
> > > > To: bridge-mib@ietf.org
> > > > Subject: [Bridge-mib] Begin WG Last Call -
> > > > draft-ietf-bridge-8021x-00.txt
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi,
> > > > 
> > > > The Bridge MIB WG has completed work on the "Definitions for 
> > > > Port Access Control
> > > > (IEEE 802.1X) MIB".  This memo proposes to re-publish the 
> > > > Port Access Entity
> > > > MIB, as defined in IEEE 802.1X, in an Informational RFC, for 
> > > > the convenience of
> > > > the IETF community.
> > > > 
> > > > The WG proposes that the I-D 'draft-ietf-bridge-8021x-00.txt' 
> > > > is the completed
> > > > version of this document. The WG members are strongly urged 
> > > > to review this
> > > > document as soon as possible, and express any concerns, or
> > > > identify any errors, in an email to the Bridge MIB WG 
> > mailing list.
> > > > 
> > > > Unless there are strong objections, published on the WG 
> > > > mailing list by December
> > > > 11, 2002, this document will be forwarded to the OPS Area 
> > > > Directors for
> > > > consideration to publish as an Informational RFC.
> > > > 
> > > > Please send all comments to the WG mailing list at 
> > > > bridge-mib@ietf.org.
> > > > 
> > > > Thanks,
> > > > Les...
> > > > 
> > > > 
> > > > _______________________________________________
> > > > 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
> > > 
> > _______________________________________________
> > 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