Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129

I support it for all these attribute codes.
However, we should give the users of 129, 241, 242 and 243 a chance to ask for a reservation of the codes they are using.
At least give them the option to reserve them once they are deprecated by this document.

Thanks,
Jakob.

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders
> Sent: Tuesday, November 01, 2016 6:33 AM
> To: John G.Scudder <jgs@juniper.net>
> Cc: IETF IDR Working Group <idr@ietf.org>
> Subject: Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129
> 
> Dear working group,
> 
> To prevent having multiple drafts in quick succession covering the same
> style of issue - I'd like your feedback on the following:
> 
> I believe that bgp path attribute 241, 242, 243 should also be added to
> this draft for the same reasons as 30, 31 and 129 are listed.
> 
> OLD:
>     This document requests IANA to deprecate the following BGP Path
>     attributes: 30, 31, and 129.
> 
> NEW:
>     This document requests IANA to deprecate the following BGP Path
>     attributes: 30, 31, 129, 241, 242, and 243.
> 
> Does anyone object? If so, why?
> 
> Unilaterally changing the document while in its mid-flight through the
> working group adoption process might be considered bad form, hence my
> request for feedback on the 241,242,243 topic.
> 
> Please note - the deprecation of an attribute can be undone if proper
> process is followed. The priority here is to prevent IANA from assigning
> tainted codepoints to innocent bystanders, thus a deprecation document
> needs to exist. In time the working group has the power to undeprecate
> them for specific purposes.
> 
> Kind regards,
> 
> Job
> 
> On Mon, Oct 31, 2016 at 05:18:57PM -0400, John G.Scudder wrote:
> > Hi Everyone,
> >
> > The author has asked for the WG to adopt  draft-snijders-idr-deprecate-30-31-129.
> >
> > If you support or oppose adoption please reply indicating so. Reasons for your position are helpful, as
> volunteering to review, comment, and/or shepherd. As an aside, I will note that I don't think the WG has the option
> of doing nothing, so if you oppose adoption please address what you think should be done instead.
> >
> > The adoption call will end November 13.
> >
> > Thanks,
> >
> > --John
> >
> > P.S.: https://tools.ietf.org/html/draft-snijders-idr-deprecate-30-31-129-01
> >
> > Abstract
> >
> >    This document requests IANA to deprecate the following BGP path
> >    attributes values: 30, 31 and 129.
> >
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr