RE: Question on: draft-ietf-ipv6-rfc2013-update-04.txt

["David B Harrington" <dbharrington@comcast.net>]

Hi,

Having worked on management applications, I do have a strong opinion
on this. I believe we should provide a machine-readable object showing
that the object is deprecated/obsolete.

If we do this, then manager applications can import the object and its
new status, and warn the operator doing the import that the object is
now obsolete or deprecated and that they should check to see if there
is a better object to monitor.

If the application developer goes through the manual process of
finding out which object is preferred over this
now-obsolete/deprecated object, the application can advise the
operator which object to monitor instead. My real preference would be
to copy the object, change its status, and if there is another object
or mib module that provides a preferred solution, to have that
documented in the deprecated/oboleted object description so that
information is made readily available to the application developer and
the operator. That would be much more user-friendly.

We should select one standard approach and document that in the
mib-review-guidelines document.

My $.02

David Harrington
dbharrington@comcast.net

-----Original Message-----
From: owner-mreview@ops.ietf.org [mailto:owner-mreview@ops.ietf.org]
On Behalf Of Wijnen, Bert (Bert)
Sent: Tuesday, October 26, 2004 5:49 AM
To: Mreview (E-mail)
Cc: Bill Fenner (E-mail); John Flick (E-mail); Margaret Wasserman
(E-mail)
Subject: Question on: draft-ietf-ipv6-rfc2013-update-04.txt

In document  draft-ietf-ipv6-rfc2013-update-04.txt we can read that it
obsoletes RFRCs 2013 and 2454. As a result,
RFC2454 will become historic (at least that is what sect
3.1.2 suggests/states). 

I then see:

   --
   -- { udp 6 } was defined as the ipv6UdpTable in RFC2454's
   -- IPV6-UDP-MIB.  This RFC obsoletes RFC 2454, so { udp 6 } is
   -- obsoleted.
   --

And wonder if it would not be better to pick up the definitions from
RFC2454 and change the status to eitehr deprecated or obsoleted. That
way we create a machine readable form of that status, whereas
otherwise that is kind of vague.

I have no strong opinion on it. 
So I would appreciate input from ther MIB Doctor team and/or the
authors and responsible AD.

Bert