Hi,
In July, there was a mibs discussion about the changing nature of ifIndex across reboots, and how that seems to have turned out to be a mistake.
[I remember the day Keith picked me out of the audience to explain to the ifmib group why allowing ifIndex to be reassigned across reboots would be such a problem for management applications. I'm afraid I offered little support at the time, and have lived to seriously regret it ever since.]
Shouldn't that problem also be addressed in a restarted ifmib effort?
dbh
> -----Original Message-----
> From: Andy Bierman [mailto:abierman@cisco.com]
> Sent: Friday, October 04, 2002 12:12 AM
> To: Thomas Narten
> Cc: mibs@ops.ietf.org
> Subject: Re: FWD: Restart ifmib WG?
>
>
> At 01:36 PM 10/2/2002 -0400, Thomas Narten wrote:
> >I just sent the following message to the ifmib mailing list.
> Followups
> >should take place there:
> >
> > General Discussion:ifmib@ietf.org
> > To Subscribe: http://www.ietf.org/mailman/listinfo/ifmib
> > Archive: ftp://ftp.ietf.org/ietf-mail-archive/ifmib
> >
> >Thomas
> >------- Forwarded Message
> >
> >From: Thomas Narten <narten@cichlid.adsl.duke.edu>
> >To: ifmib@ietf.org
> >Date: Wed, 02 Oct 2002 13:34:14 -0400
> >Subject: Restart ifmib WG?
> >
> >The ifmib WG still exists on paper, but hasn't been active for some
> >time.
> >
> >There are still (IMO) some important work items that would be good to
> >get done. For example:
> >
> > - advance IF-MIB to full std
> > - advance inverted stack table mib to DS
> >
> >There might be some more possible items, but the above ones are
> >critical in the sense that there are other documents that can't
> >advance until the above takes place.
> >
> >Who here thinks the above are important to do? And just as important,
> >are their folk here who would be willing to contribute
> cycles reviewing
> >drafts, editing drafts, etc.?
> >
> >Are there other work items that should be considered?
>
> bug fixes:
>
> - ifTableLastChange should be TimeStamp not TimeTicks
> - ifLastChange should be TimeStamp not TimeTicks
> - ifStackLastChange should be TimeStamp not TimeTicks
>
> optional enhancements:
>
> - ifMtu needs a read-write version
>
> the following objects may be available in a different MIB
> for some media types:
>
> - ifSpeed needs a read-write version
> - ifHighSpeed needs a read-write version
>
>
> >Thomas
>
> Andy
>
>
>
>
> >------- End of Forwarded Message
>
>