Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

["Ketan Talaulikar (ketant)" <[e-mail]>]

Hi PK,

AFAIK there was no objection and enough support for the Early Code Point Allocation call which concluded on 5/14. So I believe the chairs/AD would need to get this action done with IANA.

We had recommended values at the start of this discussion : https://mailarchive.ietf.org/arch/msg/idr/YmKvUQ0iuDCf_ijWUiwNz6unXAU

Reproducing it again below

          Codepoint       Description              Reference
          ------------------------------------------------------
          12              Preference sub-TLV       This document
          13              Binding SID sub-TLV      This document
          128             Segment List sub-TLV     This document
          14              ENLP sub-TLV             This document
          15              Priority sub-TLV         This document
          129             Policy Name sub-TLV      This document

Thanks,
Ketan

From: Przemyslaw Krol <[e-mail]>
Sent: 23 May 2019 17:40
To: Kausik Majumdar (kmajumda) <[e-mail]>
Cc: Ketan Talaulikar (ketant) <[e-mail]>; Susan Hares <[e-mail]>; [e-mail]; [e-mail]
Subject: Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

Greetings,

How long does this process usually take?

thanks,
pk

On Tue, Apr 30, 2019 at 9:27 AM Kausik Majumdar (kmajumda) <[e-mail]<mailto:[e-mail]>> wrote:

Hi Sue et all,

I support the early allocation of BGP Tunnel Allocation Sub-TLVs defined in section 8.3 :

          TBD1            ENLP sub-TLV             This document
          TBD2            Priority sub-TLV         This document
          TBD3            Policy Name sub-TLV      This document

This would be needed for implementation.

Thanks,
Kausik

From: Idr <[e-mail]<mailto:[e-mail]>> On Behalf Of Ketan Talaulikar (ketant)
Sent: Tuesday, April 30, 2019 7:04 AM
To: Susan Hares <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; Przemyslaw Krol <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

Hi Sue/All,

I support the early allocation for code-points for the remaining TLVs defined in this WG document. We need the same for implementation.

Thanks,
Ketan

From: Idr <[e-mail]<mailto:[e-mail]>> On Behalf Of Susan Hares
Sent: 30 April 2019 18:27
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

This begins a 2 week call for early allocation for draft-ietf-idr-segment-routing-te-policy-05.txt .

https://datatracker..ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/<https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/>

Please note that in this draft in section 8.1-8.3 to some values with existing early allocation, but in sections 8.3 there are 3 values:  (ENLP sub-TLV, Priority sub-TLV, and Policy Name sub-TLV) that need early assignment.   Section 8.4, 8.5 and 8.6 define new registries which do not need early allocation.

Please comment early and often on early allocation.   The authors have indicated their preference for values on this email list.

The authors have indicated that they have 3+ implementations which need these values in order to complete the IDR implementation requirements.

Cheerily, Susan Hares



--
Przemyslaw "PK" Krol |
 Strategic Network Engineer
ing | [e-mail]<mailto:[e-mail]>