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

[Hannes Gredler <[e-mail]>]

On Mar 5, 2014, at 2:20 PM, Loa Andersson wrote:
> Before you have done the real allocation with IANA you can't put them
> in the document!

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)

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

the registry is here:
http://www.iana.org/assignments/isis-tlv-codepoints/isis-tlv-codepoints.xhtml#tlv-codepoints
can you further qualify what you mean by "correctly identify the registry" ?
what *specifics* references are you missing.

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

i fail to see this:

only one new code point (#149) plus a new registry is asked for
all other code-points are subTLVs which are from registries
(22,23,222,223,135,235,236,237,242 which are sparsely populated,
i.e. lots of subTLV code points still available, no scare resource.

  +-----+--------------+-------------+---------+---------+------------+
   | PDU | TLV          | subTLV      | Type    | subType | #Occurence |
   +-----+--------------+-------------+---------+---------+------------+
   | LSP | IS Neighbor  |             | 22, 23, |         |        >=0 |
   |     |              |             | 222,    |         |            |
   |     |              |             | 223     |         |            |
   |     |              | SID/Label   |         | 31      |         >0 |
   |     |              | LAN         |         | 32      |         >0 |
   |     |              | SID/Label   |         |         |            |
   | LSP | IP           |             | 135,    |         |        >=0 |
   |     | reachability |             | 235,    |         |            |
   |     |              |             | 236,    |         |            |
   |     |              |             | 237     |         |            |
   |     |              | SID/Label   |         | 3       |         >0 |
   | LSP | SID/MPLS     |             | 149     |         |        >=0 |
   |     | Binding      |             |         |         |            |
   |     |              | SID/Label   |         | 1       |         >0 |
   |     |              | ERO Metric  |         | 2       |          1 |
   |     |              | IPv4 ERO    |         | 3       |        >=0 |
   |     |              | IPv6 ERO    |         | 4       |        >=0 |
   |     |              | Unnumbered  |         | 5       |        >=0 |
   |     |              | Interface   |         |         |            |
   |     |              | ID ERO      |         |         |            |
   |     |              | IPv4 Backup |         | 6       |        >=0 |
   |     |              | ERO         |         |         |            |
   |     |              | IPv6 Backup |         | 7       |        >=0 |
   |     |              | ERO         |         |         |            |
   |     |              | Unnumbered  |         | 8       |        >=0 |
   |     |              | Interface   |         |         |            |
   |     |              | ID Backup   |         |         |            |
   |     |              | ERO         |         |         |            |
   | LSP | Router       |             | 242     |         |        >=0 |
   |     | Capability   |             |         |         |            |
   |     |              | SR          |         | 2       |        >=0 |
   |     |              | Capability  |         |         |            |
   |     |              | SR          |         | 15      |          1 |
   |     |              | Algorithm   |         |         |            |
   +-----+--------------+-------------+---------+---------+------------+



> 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
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/isis-wg
>>>> 
>>> 
>>> --
>>> 
>>> 
>>> Loa Andersson                        email: [e-mail]
>>> Senior MPLS Expert                          [e-mail]
>>> Huawei Technologies (consultant)     phone: [phone]
>>> 
>>> 
>> 
>> 
> 
> -- 
> 
> 
> Loa Andersson                        email: [e-mail]
> Senior MPLS Expert                          [e-mail]
> Huawei Technologies (consultant)     phone: [phone]
> 
>