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

Robert Raszuk <robert@raszuk.net> Tue, 01 November 2016 14:02 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E8412953A for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 07:02:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nlwn4M4JS3Ye for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 07:02:40 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A5B01294C3 for <idr@ietf.org>; Tue, 1 Nov 2016 07:02:39 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id a197so79877120wmd.0 for <idr@ietf.org>; Tue, 01 Nov 2016 07:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=m3UgNutFTm/ETvA4K/2C7pGezKSdVbuWGCLBa+reRjo=; b=yxdm7nHTKkjWAMe0QV/1XthIGuwHV3q4L/Zg/Jh4ttgJ6JU99Km781ZJjaH6anwZkj gnnCHnAxoM1FL0vFQW2Mcz07MFm+GPBBxdY5q1UkIXFJHeauavnKLKBj+HglOo+Zn7qF jNEf4/TLJlBBzMUtY1wMOsc2PtGbSQZeQIK6edv8KuCAWg1A52T2WcwRnM2B3T7OJtmV zm6NbHdB6LVErKODiJcPxlYw5ceFbEvXescnrzxFTKkJML2h68dGhW+cSbUtU9wRUJlF Hz7oFc7v3ZAP72mnrpMY6l6NhYNR1Byt1EpgYT1jHSG9IJgYq6j0A1+msFyg2bo1bDR9 en9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=m3UgNutFTm/ETvA4K/2C7pGezKSdVbuWGCLBa+reRjo=; b=mXn5eI8wFEIsLCNHZSgm9/D7rCIMX1hRXl6o6sCA6iqcqS6aHV3oxshihs/KoHuJlK bp5IdeHfUY66FsnRhDbns2EncoHJwTm7r2TA53gpedC5Yc8KQ0x5UQC2AY+ADrOeKrMv lKZZ/yd8BzMeyGLRijPSuy8ooka7I9jGV/YanLJBvVxZwvANEMDRltCh8sH0Bza+hl+X UeonDHGbxafdsXxNaSRjC6nZMEiizwAK9Yn/jbTARUXJE/nu6bzESjRvoNIV/zkonxEQ 5JVgQMbVYeNJiGqU3rinYtnHKSp7aaSz6GQ5Hf63DE5OsR3An9boya2QWTNkjtOHWKCb seEw==
X-Gm-Message-State: ABUngveF9z8r3KQfnRC2hl5kwz5oI7FvKM1TfMbSsFKSutIQBvstG3cwUdRCv3frvI50Xt8eki39B0KeXnfdWw==
X-Received: by 10.28.217.139 with SMTP id q133mr1903574wmg.17.1478008958080; Tue, 01 Nov 2016 07:02:38 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.80.137.69 with HTTP; Tue, 1 Nov 2016 07:02:37 -0700 (PDT)
In-Reply-To: <20161101133240.GK1581@hanna.meerval.net>
References: <169A4C1A-302E-4FE0-841A-ADA63E812E1F@juniper.net> <20161101133240.GK1581@hanna.meerval.net>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 1 Nov 2016 15:02:37 +0100
X-Google-Sender-Auth: pqVUsYMQqOlZ6D9eBAz8mdfL3_w
Message-ID: <CA+b+ERnh8MMDgCoviLDRvOxbOky=8pBtHC8Z-WCQr6xFF_ZzGQ@mail.gmail.com>
To: Job Snijders <job@instituut.net>
Content-Type: multipart/alternative; boundary=001a11468750ebda8005403dc677
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dlIjWXJeSyx_443uio_mVESnkPQ>
Cc: IETF IDR Working Group <idr@ietf.org>
Subject: Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2016 14:02:43 -0000

Hi Job,

Have you consider marking those codepoints as "RESERVED" rather then
"DEPRECIATED".

Reason being that if any of the applications they have been squatted on
behalf of want to use them - it would be pretty easy to allocate them.

The other alternative would be to allocate them to those applications now
(for which the drafts exist) as IANA early allocations. If you depreciate
them now and we know that as example Contrail Multicast is important either
your draft will need to quickly be moved to historic or yet another types
will need to be allocated again.

In any of the above Large Communities will get virgin BGP attribute type
which I believe is the main point here.

Cheers,
R.


On Tue, Nov 1, 2016 at 2:32 PM, Job Snijders <job@instituut.net> wrote:

> 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
>