[BEHAVE] [IANA #831872] Re: Protocol Action: 'Deprecation of MIB Module NAT-MIB (Managed Objects for Network Address Translators (NAT))' to Proposed Standard (draft-perrault-behave-deprecate-nat-mib-v1-04.txt)

Hi all,

Can one of you confirm that this is correct?

123	natMIB	NAT-MIB (DEPRECATED)	[RFC-perrault-behave-deprecate-nat-mib-v1-05]

See
http://www.iana.org/assignments/smi-numbers

If so, I'll send the RFC Editor a note about the change. 

thanks,
Amanda

On Mon Jul 06 20:25:15 2015, tom.taylor.stds@gmail.com wrote:
> I'd go with David as expert: the IANA Considerations section should be
> updated.
> 
> Tom
> 
> On 06/07/2015 1:24 PM, Amanda Baber via RT wrote:
> > Hi David, all,
> >
> > The IANA Considerations section says, "IANA is requested to mark that
> > identifier as OBSOLETE and to update the reference from [RFC4008] to
> > the present document."
> >
> > Should the IANA Considerations section be updated, or should the MIB
> > be updated?
> >
> > thanks,
> > Amanda
> >
> >
> >
> > On Sat Jul 04 01:41:11 2015, ietfdbh@comcast.net wrote:
> >> Hi Amanda,
> >>
> >> This is not correct.
> >>
> >> the status for natMIB is DEPRECATED, not OBSOLETE
> >>
> >> "       REVISION     "201506240000Z"
> >>     -- RFC Ed.: set to publication date
> >>          DESCRIPTION
> >>                  "Deprecation of all objects, published as RFC yyyy.
> >>                   See NAT-MIB-V2 in RFCzzzz for recommended
> >> replacement."
> >>
> >> The format for deprecated assignments is
> >> 123     natMIB  NAT-MIB (DEPRECATED)    [RFC-perrault-behave-
> >> deprecate-nat-mib-v1-05]
> >>
> >> Here is the entry for  {mib-2 68} for an example of another
> >> deprecated
> >> MIB module under mib-2.
> >> 68      vrrpMIB VRRP MIB (DEPRECATED)   [Bob_Hinden][RFC6527]
> >>
> >> Under ifTypes, there are multiple deprecated assignments (7, 11, 62,
> >> 69, 117, 184, 205, 230) that also follow this format.
> >>
> >> David Harrington
> >> ietfdbh@comcast.net
> >>
> >>
> >>
> >> On Jul 1, 2015, at 8:55 PM, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
> >> wrote:
> >>
> >>> Dear all,
> >>>
> >>> It looks good to me too.
> >>>
> >>> Thank you for your great work.
> >>>
> >>>
> >>> Thank you,
> >>> Tina
> >>>
> >>> -----Original Message-----
> >>>   From: Tom Taylor [mailto:tom.taylor.stds@gmail.com]
> >>> Sent: Thursday, July 02, 2015 10:09 AM
> >>> To: drafts-approval@iana.org
> >>> Cc: draft-perrault-behave-deprecate-nat-mib-v1.all@tools.ietf.org
> >>> Subject: Re: [IANA #830007] Protocol Action: 'Deprecation of MIB
> >>> Module NAT-MIB (Managed Objects for Network Address Translators
> >>> (NAT))' to Proposed Standard (draft-perrault-behave-deprecate-nat-
> >>> mib-v1-04.txt)
> >>>
> >>> Looks ggood, thank you.
> >>>
> >>> Tom Taylor
> >>>
> >>> On 01/07/2015 7:26 PM, Amanda Baber via RT wrote:
> >>>> Dear Authors:
> >>>>
> >>>> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
> >>>>
> >>>> We've completed the IANA Actions for the following RFC-to-be:
> >>>>
> >>>> draft-perrault-behave-deprecate-nat-mib-v1-04
> >>>>
> >>>> IANA has updated the mib-2 registration associated with value 123
> >>>> to
> >>>> read as follows:
> >>>>
> >>>> 123  natMIB (OBSOLETE)       NAT-MIB [RFC-perrault-behave-
> >>>> deprecate-
> >>>> nat-mib-v1-05]
> >>>>
> >>>> Please see
> >>>> http://www.iana.org/assignments/smi-numbers
> >>>>
> >>>>
> >>>> Please let us know whether the above IANA Actions look OK. As soon
> >>>> as we receive your confirmation, we'll notify the RFC Editor that
> >>>> this document's IANA Actions are complete. (If this document has a
> >>>> team of authors, one reply on behalf of everyone will suffice.)
> >>>>
> >>>> We'll update the reference when the RFC Editor notifies us that
> >>>> they've assigned a number.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Amanda Baber
> >>>> IANA Senior Specialist
> >>>> ICANN
> >>>>
> >>>>
> >>> _______________________________________________
> >>> Behave mailing list
> >>> Behave@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/behave
> >
> >
> >
> >