Bridge MIB (bridge)

The IESG | 7 Nov 2002 21:11

Picon

Note Well Statement


From time to time, especially just before a meeting, this statement is to
be sent to each and every IETF working group mailing list.
===========================================================================

				NOTE WELL

All statements related to the activities of the IETF and addressed to the
IETF are subject to all provisions of Section 10 of RFC 2026, which grants
to the IETF and its participants certain licenses and rights in such
statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which are
addressed to

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

Statements made outside of an IETF meeting, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not subject to these provisions.

Les Bell | 26 Nov 2002 16:24

Picon

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 <at> ietf.org.

Thanks,
Les...

Harrington, David | 26 Nov 2002 17:37

RE: 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 <at> eur.3com.com]
> Sent: Tuesday, November 26, 2002 10:24 AM
> To: bridge-mib <at> 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

(Continue reading)

Les Bell | 26 Nov 2002 18:07

Picon

RE: Begin WG Last Call - draft-ietf-bridge-8021x-00 .txt


I have permission from the IEEE 802.1X working group to publish this MIB.  They
have been aware that this draft is available since it was first produced.  I am
copying this working group on this reply, to give them another chance to
comment.

Les...

"Harrington, David" <dbh <at> enterasys.com> on 26/11/2002 16:37:21

Sent by:  "Harrington, David" <dbh <at> enterasys.com>

To:   Les Bell/GB/3Com, bridge-mib <at> ietf.org
cc:
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 <at> eur.3com.com]
> Sent: Tuesday, November 26, 2002 10:24 AM
> To: bridge-mib <at> ietf.org
> Subject: [Bridge-mib] Begin WG Last Call -
> draft-ietf-bridge-8021x-00.txt
>

(Continue reading)

Romascanu, Dan (Dan | 26 Nov 2002 18:12

RE: 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 <at> enterasys.com]
> Sent: Tuesday, November 26, 2002 6:37 PM
> To: Les Bell; bridge-mib <at> 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 <at> eur.3com.com]
> > Sent: Tuesday, November 26, 2002 10:24 AM
> > To: bridge-mib <at> ietf.org
> > Subject: [Bridge-mib] Begin WG Last Call -
> > draft-ietf-bridge-8021x-00.txt
> > 
> > 
> > 
> > 
> >

(Continue reading)

Romascanu, Dan (Dan | 26 Nov 2002 18:26

RE: 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 <at> 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 <at> enterasys.com]
> > Sent: Tuesday, November 26, 2002 6:37 PM
> > To: Les Bell; bridge-mib <at> 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?
> >

(Continue reading)

Harrington, David | 26 Nov 2002 18:49

RE: Begin WG Last Call - draft-ietf-bridge-8021x-00.txt

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 <at> avaya.com]
> Sent: Tuesday, November 26, 2002 12:27 PM
> To: Romascanu, Dan (Dan); Harrington, David; Les Bell;
> bridge-mib <at> 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 <at> ietf.org
> > Subject: RE: [Bridge-mib] Begin WG Last Call - 
> > draft-ietf-bridge-8021x-00.txt
> >

(Continue reading)

Michael MacFaden | 27 Nov 2002 04:36

Re: Begin WG Last Call - draft-ietf-bridge-8021x-00.txt

On Tue, Nov 26, 2002 at 03:24:08PM +0000, Les Bell wrote:
>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.

I would suggest (strongly) that these errors be fixed. 

Errors from SMILINT 0.2.9
IEEE8021-PAE-MIB:191: node `dot1xPaePortReauthenticate' must be
contained in at least one conformance group
./IEEE8021-PAE-MIB:1121: node `dot1xAuthSessionUserName' must be
contained in at least one conformance group

From SMICNG 2.2.11

E: f(IEEE8021-PAE-MIB), (33,9) Leading sub-Id value for item
"ieee8021paeMIB" is invalid
W: f(IEEE8021-PAE-MIB), (191,1) Item "dot1xPaePortReauthenticate" is not
contained in any group defined in the current module
W: f(IEEE8021-PAE-MIB), (1121,1) Item "dot1xAuthSessionUserName" is not
contained in any group defined in the current module

Thanks,
Mike MacFaden

(Continue reading)

Les Bell | 27 Nov 2002 12:28

Picon

Re: Begin WG Last Call - draft-ietf-bridge-8021x-00 .txt


These errors are in the MIB as published in IEEE 802.1X-2001.
The draft already corrects these errors.

Les...

Michael MacFaden <mrm <at> riverstonenet.com> on 27/11/2002 03:36:19

Sent by:  Michael MacFaden <mrm <at> riverstonenet.com>

To:   Les Bell/GB/3Com
cc:   bridge-mib <at> ietf.org
Subject:  Re: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt

On Tue, Nov 26, 2002 at 03:24:08PM +0000, Les Bell wrote:
>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.

I would suggest (strongly) that these errors be fixed.

Errors from SMILINT 0.2.9
IEEE8021-PAE-MIB:191: node `dot1xPaePortReauthenticate' must be
contained in at least one conformance group

(Continue reading)

Michael MacFaden | 27 Nov 2002 20:05

Re: Begin WG Last Call - draft-ietf-bridge-8021x-00 .txt

On Wed, Nov 27, 2002 at 11:28:09AM +0000, Les Bell wrote:
>These errors are in the MIB as published in IEEE 802.1X-2001.
>The draft already corrects these errors.

When will there be an 01 I-D?  

Thanks,
Mike MacFaden

Group

gmane.ietf.bridge.

Advertisement

Search Archive

Page

1 | 2

Articles in period: 11

November 2002

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

what values are to be send for the traps defined in the Bridge-mib (28 Jun 2007)
bridge-mib Source code (22 Jun 2007)
From where can i get Bridge MIB Objects info in linux. (22 Jun 2007)
FW: Static fdb table in q-bridge MIB? (17 Apr 2007)
Doubt on 802.1w (max age) (19 Jan 2007)
[802.1 - 1083] FW: Connectivity Fault Management MIB (19 Nov 2006)
Connectivity Fault Management MIB (15 Nov 2006)
Connectivity Fault Management MIB (14 Nov 2006)
Out of Office AutoReply: Returned mail: see transcript for details (10 Aug 2006)
New trap (17 Jul 2006)
Question on IETF rfc4364; dot1qStaticUnicastTable (26 Apr 2006)
Mailing list (22 Feb 2006)
WG Action: Conclusion of Bridge MIB (bridge) (15 Feb 2006)
BridgeMIB WG closing (8 Feb 2006)
FW: RFC 4363 on Definitions of Managed Objects for B ridges with Traff (1 Feb 2006)
RFC 4363 on Definitions of Managed Objects for Bridges with Traffic Cl (1 Feb 2006)
FW: RFC 4318 on Definitions of Managed Objects for Bridges with R apid (27 Dec 2005)
RFC 4318 on Definitions of Managed Objects for Bridges with Rapid Span (23 Dec 2005)
Draft-harrington-8021-mib-transition-00.txt (9 Oct 2005)
FW: RFC 4188 on Definitions of Managed Objects for B ridges (4 Oct 2005)
Protocol Action: 'Definitions of Managed Objects for Bridges with Tra (4 Oct 2005)

Archives

2	February 2009
4	June 2007
2	April 2007
1	February 2007
2	January 2007
4	November 2006
1	August 2006
2	July 2006
1	April 2006
5	February 2006
2	December 2005
9	October 2005
3	September 2005
17	August 2005
20	July 2005
14	June 2005
1	May 2005
11	April 2005
5	March 2005
10	February 2005
54	January 2005
22	December 2004
39	November 2004
11	October 2004
12	September 2004
3	August 2004
20	July 2004
3	June 2004
33	April 2004
13	March 2004
6	February 2004
8	January 2004
7	December 2003
7	November 2003
4	October 2003
17	September 2003
5	August 2003
18	July 2003
3	June 2003
4	May 2003
1	April 2003
24	February 2003
2	January 2003
4	December 2002
11	November 2002
1	October 2002
1	September 2002
7	August 2002
8	July 2002
6	June 2002
14	May 2002
9	April 2002

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template