Re: FW: [802.3.1_MIBS] FW: 802.3.1-2011ApprovalNotification

Hi Glenn, 

Thanks for reminding one important reason for not making the IETF Bridge
MIBs obsolete. 

There is no intention to change this, at least AFAIK. 

Regards,

Dan 
> -----Original Message-----
> From: Glenn Parsons [mailto:[email protected]]
> Sent: Tuesday, July 19, 2011 1:42 AM
> To: Romascanu, Dan (Dan); Bert Wijnen (IETF); C. M. Heard
> Cc: Hubmib; David B Harrington
> Subject: RE: [Hubmib] FW: [802.3.1_MIBS] FW: 802.3.1-
> 2011ApprovalNotification
> 
> Dan,
> 
> We did not discuss this option for the 802.1 MIBs at the time, even
> though that was the general intent.
> 
> The view was that if someone wanted to implement a simple bridge, they
> could use the IETF MIBs (in RFC 4188, 4318 & 4363).
> 
> As a result we imported some definitions from the IETF BRIDGE-MIB and
> Q-BRIDGE-MIB instead of redefining them.
> 
> Given this, is making the IETF Bridge MIBs obsolete appropriate?
> 
> For 802.3, I don't think there are any imports from the IETF MIBS, so
> this would be cleaner.
> 
> Cheers,
> Glenn.
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Romascanu, Dan (Dan)
> Sent: July-18-11 4:39 PM
> To: Bert Wijnen (IETF); C. M. Heard
> Cc: Hubmib; David B Harrington
> Subject: Re: [Hubmib] FW: [802.3.1_MIBS] FW: 802.3.1-
> 2011ApprovalNotification
> 
> 
> 
> Hi Bert,
> 
> I thought that we can avoid the writing of such an RFC for the
> transition of the Ethernet MIB documents to IEEE 802.3, as we already
> approved the transition process within the IESG, and the IEEE 802.3
> have completed the first phase of the work. Would you or somebody else
> object to having the IESG approve marking the IETF RFCs as 'obsolete'
> and pointing to the IEEE 802.3 in the meta-data or you do believe that
> we must have this information in an RFC and run this through a
> consensus process which is broader than the IESG?
> 
> Thanks and Regards,
> 
> Dan
> 
> > -----Original Message-----
> > From: Bert Wijnen (IETF) [mailto:[email protected]]
> > Sent: Monday, July 18, 2011 11:26 PM
> > To: Romascanu, Dan (Dan); C. M. Heard
> > Cc: Hubmib; David B Harrington
> > Subject: Re: [Hubmib] FW: [802.3.1_MIBS] FW: 802.3.1-
> > 2011ApprovalNotification
> >
> > Well, my proposal then would be that we write a 1-2 page
> informational
> > RFC that explains that the new IEEE modules are the newer modules
and
> > should be used.
> > The new RFC that we write then obsoletes the IETF MIB RFCs. So they
> do
> > not become historic, but they get obsoleted bij an informational (or
> > BCP if that is better) RFC document that explains why and points
> to
> > the new current IEEE MIB modules.
> >
> > Bert
> > ----- Original Message -----
> > From: "Romascanu, Dan (Dan)" <[email protected]>
> > To: "Bert (IETF) Wijnen" <[email protected]>; "C. M. Heard"
> > <[email protected]>
> > Cc: "Hubmib" <[email protected]>; "David B Harrington"
> > <[email protected]>
> > Sent: Monday, July 18, 2011 9:34 PM
> > Subject: Re: [Hubmib] FW: [802.3.1_MIBS] FW: 802.3.1-
> > 2011ApprovalNotification
> >
> >
> > >
> > >
> > > Hi,
> > >
> > > I am not sure, I need to consult with the IESG, as the issue of a
> > > non-IETF document obsoleting an IETF document may be rather new. I
> > see
> > > that we did not make such a note on RFC 4188, when work was
> > transferred
> > > to the IEEE 802.1WG. I am copying DBH who wrote RFC 4663.
> > >
> > > To be clear - we are talking only about the meta-data for these
> RFCs,
> > > not about changing their status to Historic (for which the
> procedure
> > is
> > > described by an IESG statement -
> > >
> http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html)
> > >
> > > Thanks and Regards,
> > >
> > > Dan
> > >
> > >> -----Original Message-----
> > >> From: [email protected] [mailto:[email protected]] On
> > >> Behalf Of Bert (IETF) Wijnen
> > >> Sent: Sunday, July 17, 2011 11:24 PM
> > >> To: C. M. Heard
> > >> Cc: Romascanu, Dan (Dan); Hubmib
> > >> Subject: Re: [Hubmib] FW: [802.3.1_MIBS] FW: 802.3.1-2011
> > >> ApprovalNotification
> > >>
> > >> On 7/16/11 5:24 PM, C. M. Heard wrote:
> > >> > Dan,
> > >> >
> > >> > This new IEEE standard was published on July 1, 2011.  Since it
> > >> > includes updated versions of the MIB modules defined in RFC
> 2108,
> > >> > RFC 3621, RFC 3635, RFC 3637, RFC 4836, RFC 4837, RFC 4878, and
> > RFC
> > >> > 5066, a question arises: would it be appropriate for the
> meta-data
> > >> > for these RFCs to indicate that they are obsoleted by IEEE Std
> > >> > 802.3.1?
> > >>
> > >> Not sure if the RFC-editor can do or normally doies this. Dan, do
> > you
> > >> know.
> > >>
> > >> If not, I guess we could write 1-2 page RFC that obsoletes the
> > listed
> > >> RFCs with a
> > >> pointer to the IEEE document.
> > >>
> > >> Bert
> > >> >
> > >> > Mike Heard
> > >> >
> > >> > On Sun, 22 May 2011, Romascanu, Dan (Dan) wrote:
> > >> >> FYI.
> > >> >>
> > >> >> Regards,
> > >> >>
> > >> >> Dan
> > >> >>
> > >> >> -----Original Message-----
> > >> >> From: Howard Frazier [mailto:[email protected]]
> > >> >> Sent: Saturday, May 21, 2011 12:06 AM
> > >> >> To: [email protected]
> > >> >> Subject: [802.3.1_MIBS] FW: 802.3.1-2011 Approval Notification
> > >> >>
> > >> >> Dear Members of the IEEE 802.3.1 Ethernet MIB modules Task
> Force,
> > >> >>
> > >> >> The initial version of P802.3.1/D3.1 Standard for Management
> > >> Information Base (MIB) definitions for Ethernet has been approved
> as
> > > an
> > >> IEEE standard. See below. Congratulations and thanks to all of
you
> > for
> > >> your work on this project.
> > >> >>
> > >> >> A PAR for a revision of the standard is on the agenda for the
> > June
> > >> IEEE-SA Standards Board meeting.
> > >> >>
> > >> >> We will hold a short meeting next Thursday afternoon in
> > conjunction
> > >> with the IEEE 802.3 interim meetings in Incline Village, NV, to
> plan
> > >> our work for the revision project.
> > >> >>
> > >> >> Howard Frazier
> > >> >> Chair, IEEE 802.3.1 Ethernet MIB modules Task Force
> > >> >>
> > >> >> -----Original Message-----
> > >> >> From: Law, David [mailto:[email protected]]
> > >> >> Sent: Friday, May 20, 2011 12:05 PM
> > >> >> To: Howard Frazier
> > >> >> Subject: FW: 802.3.1-2011 Approval Notification
> > >> >>
> > >> >> Hi Howard,
> > >> >>
> > >> >> On checking I found that I did have the approval notification.
> > >> >>
> > >> >> Congratulations!!
> > >> >>
> > >> >> Best regards,
> > >> >>    David
> > >> >> _______________________________________
> > >> >>
> > >> >> From: [email protected] [mailto:[email protected]]
> > >> >> Sent: 17 May 2011 14:28
> > >> >> To: Law, David
> > >> >> Cc: [email protected]; [email protected];
> > > [email protected];
> > >> [email protected]
> > >> >> Subject: 802.3.1-2011 Approval Notification
> > >> >>
> > >> >>
> > >> >> 17 May 2011
> > >> >>
> > >> >> David Law
> > >> >> HP Ltd.
> > >> >> 20 Clayknowes Ave
> > >> >> Musselburgh, East Lothian EH21 6UR Scotland
> > >> >>
> > >> >> cc:          Paul Nikolich, Sponsor Chair
> > >> >>          Kathryn Bennett, Program Manager
> > >> >>                Kim Breitfelder, Manager Standards Publishing
> > >> >>          Thomas Geoffrey, Negative Balloter
> > >> >>
> > >> >> RE: NEW P802.3.1/D3.1 (C/LM) Standard for Management
> Information
> > >> Base (MIB) definitions for Ethernet
> > >> >> Dear David,
> > >> >>
> > >> >> I am pleased to inform you that P802.3.1 was approved as a new
> > >> standard by the IEEE-SA Standards Board on 16 May 2011. A copy of
> > the
> > >> document will be forwarded to the Standards Publications
> Department.
> > >> The editor assigned to work on the project will contact you.
> > >> >>
> > >> >> All IEEE standards shall be updated within five years of
> approval
> > > by
> > >> the IEEE-SA Standards Board. If the standard is not revised,
> > >> reaffirmed, or withdrawn within five years, the Sponsor will be
> > >> notified that it will be submitted to the Standards Board for
> > >> administrative withdrawal.
> > >> >>
> > >> >> It should be noted that any negative balloters have the right
> to
> > >> appeal. Please consult the following web pages for information on
> > this
> > >> process:
> > >> >>
> > >> >> http://standards.ieee.org/develop/policies/bylaws/
> > >> >>
> > >> >> http://standards.ieee.org/develop/policies/opman/
> > >> >>
> > >> >> Please contact me if you have any questions prior to speaking
> > with
> > >> your editor.
> > >> >>
> > >> >> Sincerely,
> > >> >> ************************************************
> > >> >> Karen M. Evangelista
> > >> >> IEEE - SA Governance, Administrator IEEE Standards Activities
> > >> >> Department
> > >> >> 445 Hoes Lane
> > >> >> Piscataway, NJ 08854-4141 USA
> > >> >> TEL: +1 732 562 3854
> > >> >> FAX: +1 732 796 6966
> > >> >> [email protected]
> > >> >> *************************************************
> > >> >>
> > >> >>
> > >> >> _______________________________________________
> > >> >> Hubmib mailing list
> > >> >> [email protected]
> > >> >> https://www.ietf.org/mailman/listinfo/hubmib
> > >>
> > >> _______________________________________________
> > >> Hubmib mailing list
> > >> [email protected]
> > >> https://www.ietf.org/mailman/listinfo/hubmib
> > > _______________________________________________
> > > Hubmib mailing list
> > > [email protected]
> > > https://www.ietf.org/mailman/listinfo/hubmib
> 
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/hubmib