FW: Bridge wg charter
"Harrington, David" <[email protected]> Fri, 16 Apr 2004 17:10:16 -0400
| Newsgroups | gmane.ietf.bridge |
|---|---|
| Message-ID | <6D745637A7E0F94DA070743C55CDA9BA01976F78@NHROCMBX1.ets.enterasys.com> |
Hi, I have revised the charter to focus on the four outstanding documents, and then to work out how the IETF Bridge WG will work with the IEEE 802.1 WG for future mib work. If the WG finds this rewrite acceptable, we can try to get it in the IESG docket next week. Comments, please. dbh > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:[email protected]] > Sent: Thursday, April 15, 2004 6:19 PM > To: Harrington, David; Romascanu, Dan (Dan); Les Bell > Cc: David Kessens (E-mail) > Subject: RE: Bridge wg charter > > Thanks for the initiative Dave. > > So when you write a milestone like "Submit an ID...." > do you them mean "submit to IESG or AD" ?? > Or is that just posting it as an I-D in internet-drafts > repository. Pls make that clear. > And most important, I need dates by when you think to > "request publication" i.e. when you submit it to AD or IESG for > publication. > > I am also confused by milestones: > Jun 04 Submit the SMIv2 version of RFC 1493 > (draft-ietf-bridge-bridgemib-smiv2) for publication > as a Proposed Standard. > Jul 04 Evaluate status of RFC 1493 and get WG consensus if > advancement or other status change should be requested > > So does that mean that "evaluation starts after the SMIv2 > version of the > ID has been "submitted" (whatever that means)? But even then, > the ID is for > PS and this is to evaluate if 1493 needs to be advanced. > > Maybe it is just me. > > I also think we should write something about how we think we're going > to interact with and get involvement from IEEE 802.1, no? > (pls make sure we get proepr IEEE people involved in teh review) > > But pls adapt that a bit to make it clearer, and then feel free to > discuss on WG mailing list. If we have a feel for how well it > is supported next week, then I can put it on IESG agenda. I then need > it by Wednesday at the latest. > > Pls also keep Bernard up to date, he is now generic IETF > liasion to IEEE > 802, so it is good if he stays informed. > > Thanks, > Bert > > > -----Original Message----- > > From: Harrington, David [mailto:[email protected]] > > Sent: donderdag 15 april 2004 19:30 > > To: Romascanu, Dan (Dan); Les Bell; [email protected] > > Subject: RE: Bridge wg charter > > > > > > Hi Bert, > > > > Dan and Les have looked over this charter revision. They also > > pushed for > > later dates on the milestones, so I pushed them out. Are you OK with > > this revision? > > > > We are in agreement that it doesn't make sense to publish a mirror > > 802.1X, but a pointer document would probably be good. We > > haven't run it > > by the WG yet. > > > > dbh > > > > > -----Original Message----- > > > From: Romascanu, Dan (Dan) [mailto:[email protected]] > > > Sent: Thursday, April 15, 2004 1:05 PM > > > To: Harrington, David; Les Bell > > > Subject: RE: Bridge wg charter > > > > > > David, > > > > > > You did not send an updated charter, but if it is the old one > > > with updated schedules I am fine. > > > > > > I am OK with an informational RFC. I would keep then separate > > > at this stage. The reason is that the situation with 802.3 > > > MIBs for example is different - mainly because the IEEE 802.3 > > > WG took in the past a different approach than 802.1. > > > > > > yes, they are calling themselves Working Groups. > > > > > > Regards, > > > > > > Dan > > > > > > > > > > > > > -----Original Message----- > > > > From: Harrington, David [mailto:[email protected]] > > > > Sent: 15 April, 2004 7:56 PM > > > > To: Les Bell; Romascanu, Dan (Dan) > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > Hi, > > > > > > > > I've updated the milestones with new dates. If you're > > > > satisfied with it, > > > > and Bert is satisfied with it, we can send it to the WG for > > > > discussion. > > > > While I have discussed finalizing the documents with the > > editors, I > > > > would like to have the editors make a public commitment > > to finalize > > > > within the milestone dates. > > > > > > > > I agree that it doesn't make sense to publish 802.1X, but > > I think we > > > > need to run this through the consensus process. Part of my > > > > "survey", my > > > > proposed charter wording, and the request for a "sync" review > > > > was meant > > > > to make this apparent. > > > > > > > > Do you think we should have an informational rfc for 802.1 > > > > mibs, another > > > > 802.3, etc., or just one with pointers to IEEE mib pages > > for various > > > > subgroups/areas (what DO they call these in IEEE)? If we > > do this for > > > > IEEE, other SDOs may want similar treatment, so one rfc > > might be the > > > > simplest approach. > > > > > > > > It would be good if the RFC search engine could find keys > > > > such as 802.1, > > > > 802.3, 802.11, 802 and IEEE to find the relevant rfc(s). > > > > > > > > dbh > > > > > > > > > -----Original Message----- > > > > > From: Les Bell [mailto:[email protected]] > > > > > Sent: Wednesday, April 14, 2004 8:08 AM > > > > > To: Romascanu, Dan (Dan) > > > > > Cc: Harrington, David > > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > > > > > > > > > > > > > > Thanks. > > > > > > > > > > I agree with Dan that you should allow another month for each > > > > > of the dates > > > > > listed, unless you believe that the drafts currently issued > > > > > are ready for last > > > > > call now. If not you will need to persuade those on the > > > > > mailing list to submit > > > > > comments, apply appropriate edits, and release a new draft > > > > > before going to last > > > > > call. This could easily take more than the 6 weeks up to the > > > > > end of May. > > > > > > > > > > I think there is no longer any point in submitting the draft > > > > > that duplicates the > > > > > original 802.1X MIB with corrections applied. This MIB is > > > > > due to be superseded > > > > > with the revised publication of the 802.1X standard, which > > > > > includes the > > > > > corrections made in the current internet-draft, plus a number > > > > > of other changes > > > > > required by changes to the 802.1X standard itself. Perhaps > > > > > you should poll the > > > > > mailing list for opinions on this. > > > > > > > > > > I think it may be worthwhile generating an Informational RFC > > > > > pointing to the > > > > > 802.1 web site for the 802.1 MIBs, the 802.3 web-site for the > > > > > LACP MIB, and any > > > > > other MIBs that may be available. (I believe 802.11 > > > > > generated some MIBs, but I > > > > > do not know about their content or availability.) > > > > > > > > > > Les... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Romascanu, Dan (Dan)" <[email protected]> on > > 14/04/2004 09:52:26 > > > > > > > > > > Sent by: "Romascanu, Dan (Dan)" <[email protected]> > > > > > > > > > > > > > > > To: Les Bell/GB/3Com, "Harrington, David" > <[email protected]> > > > > > cc: > > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Les Bell [mailto:[email protected]] > > > > > > Sent: 14 April, 2004 11:48 AM > > > > > > To: Harrington, David > > > > > > Cc: Romascanu, Dan (Dan) > > > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi David, > > > > > > > > > > > > I did not receive the updated charter mentioned in > this email > > > > > > trail. Could you > > > > > > send it to me again please. > > > > > > > > > > > > Les... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > "Harrington, David" <[email protected]> on > 13/04/2004 22:48:59 > > > > > > > > > > > > Sent by: "Harrington, David" <[email protected]> > > > > > > > > > > > > > > > > > > To: "Romascanu, Dan \, Les Bell/GB/3Com > > > > > > cc: > > > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > Of course it's basically the same; I'm not trying to change > > > > > what we're > > > > > > doing, just trying to clarify the goals and set some > > > > > > milestones to shoot > > > > > > for. I found the current documents and the milestones > > > > > didn't match up > > > > > > well, and wanted to better reflect the current documents and > > > > > > what needs > > > > > > to be done. I can push up the dates if you think that's > > > > > prudent, but I > > > > > > do want to see this work done asap; my initial pass > had April > > > > > > 04 dates, > > > > > > and I changed them to May at Bert's request. > > > > > > > > > > > > We do have editors. The documents are close to complete. KC > > > > > and Vivian > > > > > > will continue to finalize the documents, as they can. If the > > > > > > work drags > > > > > > on, they won't. Tom Petch has offered to help edit. David > > > > > Levi offered > > > > > > to review the RSTP document. Mike already did some > > review of the > > > > > > documents. I think we should have adequate personnel to > > > > achieve our > > > > > > goals. > > > > > > > > > > > > I asked for the multiple types of reviews because I want to > > > > > gauge the > > > > > > level of interest from the members of the WG in completing > > > > > > these tasks. > > > > > > If they have no interest in completing the work, we can > > > > > check with the > > > > > > IEEE to see if they have enough interest to complete the > > > > > documents. If > > > > > > not, then we can probably just throw the documents away. > > > > I came into > > > > > > this role with the expectation that such might be > the result. > > > > > > > > > > > > It is possible there will be little interest because some > > > > > of the work > > > > > > that has been done is largely editorial, e.g. converting > > > > rfc1493 to > > > > > > SMIv2 format, and much of the work to be done is related to > > > > > > publication > > > > > > standards not technology standards, e.g. meeting the > > mib review > > > > > > guidelines CLRs, or is simply formalizing in a MIB what has > > > > > > already been > > > > > > defined clearly enough by the IEEE. The IETF really could > > > > > use a "good > > > > > > enough" status for documents. There isn't much in these > > > > > documents that > > > > > > stimulates me as an NMS vendor, even though the IEEE > > technology > > > > > > interests me as a hardware vendor. We'll see whether the > > > > > > industry/mailinglist is really interested in these > > mibs or not. > > > > > > > > > > > > dbh > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Romascanu, Dan (Dan) [mailto:[email protected]] > > > > > > > Sent: Tuesday, April 13, 2004 4:28 PM > > > > > > > To: Harrington, David; Les Bell > > > > > > > Subject: RE: Bridge wg charter > > > > > > > > > > > > > > Basically it's the same as the existing charter, > isn't it? I > > > > > > > would write part of the text differently, but it's at > > > > > > > wordsmithing level and I am not sure it's worth > the effort. > > > > > > > Maybe if we say - 'it's just the previous charter, we just > > > > > > > try to wrap-up and update schedules' we may be in > > > better shape. > > > > > > > > > > > > > > Talking about schedules I do not think that they are > > > > > > > realistic. Did we identify editors and reviewers? Just > > > > > > > running the Charter through the IETF would push > us in May. I > > > > > > > would suggest at least to push ahead each milestone by > > > > one month. > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Harrington, David [mailto:[email protected]] > > > > > > > > Sent: 13 April, 2004 11:14 PM > > > > > > > > To: Romascanu, Dan (Dan); Les Bell > > > > > > > > Subject: Bridge wg charter > > > > > > > > > > > > > > > > > > > > > > > > Hi Dan and Les, > > > > > > > > > > > > > > > > I'd like to rewrite the charter to reflect only what is > > > > > > > still needed. > > > > > > > > Can you look at this proposed charter and see > if you feel > > > > > > > it is a good > > > > > > > > approach, and covers everything that still needs > > to be done? > > > > > > > > > > > > > > > > Dan, Les sent me a rundown of the previous > > milestones; I'll > > > > > > > > forward that > > > > > > > > to you. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > David Harrington > > > > > > > > [email protected] > > > > > > > > Director, Network Management Architecture > > > > > > > > Office of the CTO, Enterasys Networks > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
bridge-charter-2a.html
(text/html, 6 KB)
<html> <title>Bridge MIB (bridge) Charter</title> <body bgcolor="#ffffff" > <center> <table border=0 cellpadding=0 cellspacing=0> <tr> <td><a href="/home.html"><img src="/images/header/ietflogo_sm.gif" border=0></a></td> <td><a href="/home.html"><img src="/images/header/home11.gif" border=0></a></td> <td><img src="/images/header/separator.gif" border=0></td> <td><a href="/html.charters/wg-dir.html"><img src="/images/header/wg11.gif" border=0></a></td> <td><img src="/images/header/separator.gif" border=0></td> <td><a href="/meetings/meetings.html"><img src="/images/header/meetings11.gif" border=0></a></td> <td><img src="/images/header/separator.gif" border=0></td> <td><a href="/proceedings/directory.html"><img src="/images/header/proceed11.gif" border=0></a></td> <td><img src="/images/header/separator.gif" border=0></td> <td><a href="/ID.html"><img src="/images/header/id-index11.gif" border=0></a></td> <td><img src="/images/header/separator.gif" border=0></td> <td><a href="/rfc.html"><img src="/images/header/rfc11.gif" border=0></a></td> </tr> </table> </center> <hr> <h1>Bridge MIB (bridge)</h1> <p>Last Modified: 2004-04-13 <br> <h2>Chair(s):</h2> <a href="mailto:[email protected]"><b>Les Bell <[email protected]></b></a><br> <p>Suggested Chairs:</p> <a href="mailto:[email protected]"><b>David Harrington <[email protected]></b></a><br> <a href="mailto:[email protected]"><b>Dan Romascanu <[email protected]></b></a><br> <h2>Operations and Management Area Director(s):</h2> <a href="mailto:[email protected]"><b>Bert Wijnen <[email protected]></b></a><br> <a href="mailto:[email protected]"><b>David Kessens <[email protected]></b></a><br> <h2>Operations and Management Area Advisor:</h2> <a href="mailto:[email protected]"><b>Bert Wijnen <[email protected]></b></a><br> <h2>Mailing Lists:</h2> General Discussion: [email protected]<br> To Subscribe: [email protected]<br> In Body: subscribe your_email_address<br> Archive: ftp://ftp.ietf.org/ietf-mail-archive/bridge/<br> <h2>Description of Working Group:</h2> The Bridge MIB Working Group is chartered to define a set of managed <br>objects that instrument devices that conform to the IEEE 802.1<br>standards for MAC-layer bridges.<br><br>This set of objects should be largely compliant with (and even draw <br>from) those objects defined within each of the IEEE 802.1 standards, <br>although there is no requirement that any specific object be present or <br>absent.<br><br>The set of objects should not duplicate, nor conflict with any MIB<br>object definitions defined by the IEEE 802.1 standards themselves.<br><br>The MIB object definitions produced will be for use by SNMP and will be <br>consistent with other SNMP objects, standards, and conventions.<br> <h2>Goals and Milestones:</h2> <table> <tr ALIGN=left VALIGN="top"><td WIDTH=70 VALIGN="top">Jun 04</td><td> </td><td>Submit the SMIv2 version of RFC 1493 (draft-ietf-bridge-bridgemib-smiv2) to IESG for approval as a Proposed Standard.</td></tr> <tr ALIGN=left VALIGN="top"><td WIDTH=70 VALIGN="top">Jun 04</td><td> </td><td>Submit an Internet-Draft with MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v (draft-ietf-bridge-ext-v2) to IESG for approval as a Proposed Standard.</td></tr> <tr ALIGN=left VALIGN="top"><td WIDTH=70 VALIGN="top">Jun 04</td><td> </td><td>Submit an Internet-Draft with MIB support for extensions to the Bridge standards defined in 802.1w (draft-ietf-bridge-rstpmib) to IESG for approval as a Proposed Standard.</td></tr> <tr ALIGN=left VALIGN="top"><td WIDTH=70 VALIGN="top">Jun 04</td><td> </td><td>Submit an Internet-Draft which mirrors or points to the IEEE mib for 802.1x (draft-ietf-bridge-8021x) to IESG for approval as an Informational RFC.</td></tr> <tr ALIGN=left VALIGN="top"><td WIDTH=70 VALIGN="top">Jul 04</td><td> </td><td>Discuss with IEEE 802.1 leaders and ADs how the Bridge WG will interact with the IEEE 802.1 WG in the future. Revise the WG charter or go dormant, as applicable. </td></tr> </table> <h2>Internet-Drafts:</h2> <a href="/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-06.txt"> Definitions of Managed Objects for Bridges using SMIv2 </a><br> <a href="/internet-drafts/draft-ietf-bridge-rstpmib-04.txt"> Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol </a> (31817 bytes)<br> <a href="/internet-drafts/draft-ietf-bridge-ext-v2-02.txt"> Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions </a> (167752 bytes)<br> <a href="/internet-drafts/draft-ietf-bridge-8021x-03.txt"> Definitions for Port Access Control (IEEE 802.1X) MIB </a> (84990 bytes)<br> <h2>Request For Comments:</h2> <a href="/rfc/rfc1286.txt">Definitions of Managed Objects for Bridges (RFC 1286)</a> (79104 bytes) <font color="red"> obsoleted by <a href="/rfc/rfc1493.txt">RFC 1493</a> </font> <br> <a href="/rfc/rfc1286.txt">Definitions of Managed Objects for Bridges (RFC 1286)</a> (79104 bytes) <font color="red"> obsoleted by <a href="/rfc/rfc1525.txt">RFC 1525</a> </font> <br> <a href="/rfc/rfc1493.txt">Definitions of Managed Objects for Bridges (RFC 1493)</a> (74493 bytes) <br> <a href="/rfc/rfc1525.txt">Definitions of Managed Objects for Source Routing Bridges (RFC 1525)</a> (38100 bytes) <br> <a href="/rfc/rfc2674.txt">Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions (RFC 2674)</a> (159971 bytes) <br> <HR> <i> IETF Secretariat - Please send questions, comments, and/or suggestions to </i> <a href="mailto:[email protected]">[email protected]</a>. <P> <A HREF="/html.charters/wg-dir.html"> <IMG SRC="/icons/back.gif"> Return to working group directory. </A> <P> <A HREF="/home.html"> <IMG SRC="/icons/back.gif"> <IMG SRC="/icons/back.gif"> Return to IETF home page. </A> </html>