Re: [Isis-wg] WG acceptance for draft-previdi-isis-segment-routing-extensions-05

Loa Andersson <loa@pi.nu> Thu, 06 March 2014 10:00 UTC

Return-Path: <loa@pi.nu>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1CE1A01BE for <isis-wg@ietfa.amsl.com>; Thu, 6 Mar 2014 02:00:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 BZLxS9A4QCDa for <isis-wg@ietfa.amsl.com>; Thu, 6 Mar 2014 02:00:25 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8A01A01C1 for <isis-wg@ietf.org>; Thu, 6 Mar 2014 02:00:23 -0800 (PST)
Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 08E2E180150F; Thu, 6 Mar 2014 11:00:19 +0100 (CET)
Message-ID: <53184732.3070801@pi.nu>
Date: Thu, 06 Mar 2014 11:00:18 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Hannes Gredler <hannes@juniper.net>
References: <BB1F64CC-8394-4C33-976D-B68FA58967A1@juniper.net> <53171CEF.2050600@pi.nu> <424DBB23-9ECA-41C0-8864-9DED3B008F80@juniper.net> <531724A8.5090008@pi.nu> <F72EA2B0-52FF-4588-A0EC-3F57AC0182CC@juniper.net>
In-Reply-To: <F72EA2B0-52FF-4588-A0EC-3F57AC0182CC@juniper.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/nIpot_JLkNAfyLIc_cG16mY7faM
Cc: draft-previdi-isis-segment-routing-extensions@tools.ietf.org, Christian Hopps <chopps@rawdofmt.org>, "isis-wg@ietf.org list" <isis-wg@ietf.org>, iana-questions@iana.org, Alia Atlas <akatlas@juniper.net>, rtg-ads@tools.ietf.org
Subject: Re: [Isis-wg] WG acceptance for draft-previdi-isis-segment-routing-extensions-05
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 10:00:30 -0000

Hannes,


On 2014-03-05 14:36, Hannes Gredler wrote:
> not sure i understand - is your suggestion:
>
> 1. to issue -06 version of a draft, code-points removed
> 2. ask for WG acceptance
> 3. do early allocation
> 4. issue -07 this time with the same original code-points
>
> is this just a procedural nit or is there something substantial
> (i.e. a clash with a document that you want to bring to the WG attention)

I think this is what you would have needed to do if it were sandards
action.

In this case the allocation policy is expert review. I think you can
send the early allocation request now, i.e. jump to step 3.

I believe that you will get the early allocation if you do so. If the
experts tell you to wait you will need - as Amanda said - to say in the
draft that the code points are not allocated (only requested.

But I see no reason why the experts would tell you to wait.

Chris and you can do this on your own initiative (especially based on
the strong support for the draft already present on the mailing list).
Just send the mail to IANA and copy the rtg-ad's and ask for the
allocations. Point to the existing draft.

Now to the other question. No - I don't know of any other draft that
will clash. However that was also the case when we actually had a clash,
the result was one unhappy vendor. I'm pretty sure that you want to
avoid this, especially since it so easy to avoid.

/Loa


-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64