Re: TLV conflict
Alia Atlas <[email protected]> Thu, 14 Dec 2017 10:00:31 -0500
| Newsgroups | gmane.ietf.isis |
|---|---|
| Message-ID | <CAG4d1rfuYrDua6Ws18AhNfqhyZRjQkMOrXsEFuiUZtXaaMY-EA__25262.2563545176$1513263673$gmane$org@mail.gmail.com> |
Hi Harish, Please take a look at https://www.iana.org/assignments/isis-tlv-codepoints/isis-tlv-codepoints.xhtml#isis-tlv-codepoints-242 where it is clear that draft-ietf-isis-segment-routing-msd has an early temporary registration for type 23. draft-ietf-isis-segment-routing-msd-02 should be updated to clearly state the IANA allocations that have already happened. draft-ietf-isis-segment-routing-extensions-13 MUST be updated to clearly state the IANA allocations that have already happened for it (e.g. values 2 & 19) and to STOP SQUATTING on already allocated code-points. Thank you for bringing this to our attention! Regards, Alia On Thu, Dec 14, 2017 at 9:41 AM, Harish R Prabhu <[email protected]> wrote: > While going through the I-Ds pertaining to SR attributes, it was found > that the following 2 TLVs have been assigned the same Type number > > SRMS Preference Sub-TLV : > https://tools.ietf.org/html/draft-ietf-isis-segment- > routing-extensions-13#section-3.4 > > Node MSD Advertisement : > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-msd-02#page-4 > > Both these sections talk about different sub tlvs under > router_capabilities TLV, but type value assigned is 23 for both. > > Request to address this. > > Thanks, > -- > Harish R Prabhu > Bangalore, India. > mailtp:[email protected] > > _______________________________________________ > Isis-wg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ Isis-wg mailing list [email protected] https://www.ietf.org/mailman/listinfo/isis-wg