Hi Les, The expiration date is set to expire one year from the date of allocation. Since we made the registrations yesterday, the expiration date is different from the others. If the document hasn't been approved for publication before the expiration date, we'll contact you to ask whether you need a one-year extension.
Thanks, Sabrina On Mon Jun 04 23:02:29 2018, [email protected] wrote: > Sabrina - > > Thanx for completing this. > > Any reason why the last two codepoints > > > 22 Segment Routing Local Block (SRLB) (TEMPORARY - registered > > 2018- > > 06-04, expires 2019-06-04) [draft-ietf-isis-segment-routing- > > extensions] > > > > 24 Segment Routing Mapping Server Preference (SRMS Preference) > > (TEMPORARY - registered 2018-06-04, expires 2019-06-04) [draft- > > ietf- > > isis-segment-routing-extensions] > > expire on a different date from the others? > I hope this won’t matter as we have passed WG Last Call - but just in > case...??? > > Les > > > -----Original Message----- > > From: Sabrina Tanamal via RT <[email protected]> > > Sent: Monday, June 04, 2018 3:52 PM > > Cc: [email protected]; Les Ginsberg (ginsberg) <[email protected]>; > > draft-ietf- > > [email protected]; [email protected]; > > [email protected]; Acee Lindem (acee) <[email protected]> > > Subject: [IANA #1109980] Early Allocation Extension for "IS-IS > > Extensions for > > Segment Routing" - draft-ietf-isis-segment-routing-extensions-16.txt > > > > Hi all, > > > > We've updated the expiration date for the following registrations: > > > > In the TLV Codepoints Registry: > > > > 149 Segment Identifier / Label Binding (TEMPORARY - registered > > 2016-06- > > 29, extension registered 2018-06-04, expires 2019-06-29) n > > y > > n n [draft-ietf-isis-segment-routing-extensions] > > > > 150 Multi-Topology Segment Identifier / Label Binding (TEMPORARY - > > registered 2016-06-29, extension registered 2018-06-04, expires 2019- > > 06-29) > > n y n n [draft-ietf-isis-segment- > > routing- > > extensions] > > > > In the Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 registry: > > > > 31 Adjacency Segment Identifier (TEMPORARY - registered 2016-06- > > 29, > > extension registered 2018-06-04, expires 2019-06-29) y y > > n > > y y y [draft-ietf-isis-segment-routing- > > extensions] > > > > 32 LAN Adjacency Segment Identifier (TEMPORARY - registered 2016- > > 06-29, extension registered 2018-06-04, expires 2019-06-29) y > > y > > n y y y [draft-ietf-isis-segment- > > routing- > > extensions] > > > > In the Sub-TLVs for TLVs 135, 235, 236, and 237 registry: > > > > 3 Prefix Segment Identifier (TEMPORARY - registered 2016-06-29, > > extension registered 2018-06-04, expires 2019-06-29) y y > > y > > y [draft-ietf-isis-segment-routing-extensions] > > > > In the Sub-TLVs for TLV 242 registry: > > > > 2 Segment Routing Capability (TEMPORARY - registered 2016-06-29, > > extension registered 2018-06-04, expires 2019-06-29) [draft-ietf- > > isis- > > segment-routing-extensions] > > > > 19 Segment Routing Algorithm (TEMPORARY - registered 2016-06-29, > > extension registered 2018-06-04, expires 2019-06-29) [draft-ietf- > > isis- > > segment-routing-extensions] > > > > We've made the following early allocations: > > > > 22 Segment Routing Local Block (SRLB) (TEMPORARY - registered > > 2018- > > 06-04, expires 2019-06-04) [draft-ietf-isis-segment-routing- > > extensions] > > > > 24 Segment Routing Mapping Server Preference (SRMS Preference) > > (TEMPORARY - registered 2018-06-04, expires 2019-06-04) [draft- > > ietf- > > isis-segment-routing-extensions] > > > > Please see > > https://www.iana.org/assignments/isis-tlv-codepoints > > > > Best regards, > > > > Sabrina Tanamal > > Senior IANA Services Specialist > > > > On Tue May 15 17:12:25 2018, [email protected] wrote: > > > Hi Amanda, et al, > > > > > > I just communicated with Les, one of the designated experts for the > > > IS-IS TLV 242 registry, and the draft requires two additional Sub- > > > TLV > > > allocations: > > > > > > Sub-TLV 22 for Segment Routing Local Block (SRLB) Sub-TLV 24 for > > > Segment Routing Mapping Server (SRMS) Preference > > > > > > Thanks, > > > Acee > > > > > > From: Acee Lindem <[email protected]> > > > Date: Tuesday, May 15, 2018 at 10:54 AM > > > To: IANA <[email protected]>, Alvaro Retana <[email protected]> > > > Cc: Christian Hopps <[email protected]>, "[email protected]" > > > <[email protected]>, "draft-ietf-isis-segment-routing- > > > [email protected]" > > > <[email protected]>, Uma Chunduri > > > <[email protected]> > > > Subject: Early Allocation Extension for "IS-IS Extensions for > > > Segment > > > Routing" - draft-ietf-isis-segment-routing-extensions-16.txt > > > > > > Hi Amanda, et al IANA, Alvaro, > > > > > > For a variety of reasons, we will not finish the subject draft by > > > the > > > end of June when the IANA allocations expire. It has just completed > > > WG > > > last call but there are many fastidious reviewers are in the path > > > to > > > completion. Please extend the allocations and add any that were not > > > in > > > the original early allocations. For example, we need the SRMS > > > Preference allocated in the TLV 242 registry ASAP since we have > > > early > > > allocations to make in this registry. > > > > > > Thanks, > > > Acee > > > > > _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
