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

Loa Andersson <loa@pi.nu> Wed, 05 March 2014 13:20 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 BE8151A017E for <isis-wg@ietfa.amsl.com>; Wed, 5 Mar 2014 05:20:43 -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 fjv_qy14knQD for <isis-wg@ietfa.amsl.com>; Wed, 5 Mar 2014 05:20:41 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9451A0078 for <isis-wg@ietf.org>; Wed, 5 Mar 2014 05:20:41 -0800 (PST)
Received: from [192.168.0.109] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (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 9C62D18015D3; Wed, 5 Mar 2014 14:20:37 +0100 (CET)
Message-ID: <531724A8.5090008@pi.nu>
Date: Wed, 05 Mar 2014 14:20:40 +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>
In-Reply-To: <424DBB23-9ECA-41C0-8864-9DED3B008F80@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/Ry3icxiLf2TKRTTiG02GSdkoyYE
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: Wed, 05 Mar 2014 13:20:44 -0000

Hannes,

Before you have done the real allocation with IANA you can't put them
in the document!

In the ISIS case I think the code points are by expert review, but since
it is almost impossible to correctly identify the registry I can't tell
for sure.

If this is correct, there is not need to wait, you can ask the expert
for allocation based on the individual document, and there is no reason
not to do this.

I've also been notified about another concern, again I can't definitely
verify that is is true. The document allocates a very big chunk of code
points from a registry with very limited space.



/Loa

On 2014-03-05 13:58, Hannes Gredler wrote:
> loa,
>
> before we can engage in early allocation we first need to make this WG item.
> after that has been done i'll immediate ask our ADs to go for early allocation,
> such that your concerns are addressed. if you know about a specific clash
> with another document can you please put this to my attention such that
> we can work with the authors to fix this.
>
> in the meantime may i ask you therefore for having 2 weeks more patience ?
>
> thanks,
>
> /hannes
>
>
> On Mar 5, 2014, at 1:47 PM, Loa Andersson wrote:
>
>> Hannes and Chris,
>>
>> This document are allocating code-points from an existing IANA registry.
>>
>> The IANA section in the document is unclear and it is not immediately
>> possible to find.
>>
>> Questions: Which registry are the code point assigned from?
>>            What are the policies for assigning code points from this
>>            registry?
>>            Has the procedures for early allocation been followed?
>>
>> Until this is cleared up I'm opposed to accepting the document as a
>> working document.
>>
>> /Loa
>>
>> On 2014-03-05 13:34, Hannes Gredler wrote:
>>> hi,
>>>
>>> the authors of draft-previdi-isis-segment-routing-extensions are asking
>>> for acceptance as a WG item.
>>> http://tools.ietf.org/html/draft-previdi-isis-segment-routing-extensions-05
>>>
>>> please provide feedback, (support/opposition) up until March 19th 2014 (2 weeks).
>>>
>>> thanks,
>>>
>>> /hannes & chris
>>> _______________________________________________
>>> Isis-wg mailing list
>>> Isis-wg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/isis-wg
>>>
>>
>> --
>>
>>
>> Loa Andersson                        email: loa@mail01.huawei.com
>> Senior MPLS Expert                          loa@pi.nu
>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>>
>>
>
>

-- 


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