Hi Martin, Thanks for your review and please check inline below for responses.
The changes as discussed below will be updated in the next version of the document. On Fri, Sep 16, 2022 at 11:22 PM Acee Lindem (acee) <acee= 40cisco....@dmarc.ietf.org> wrote: > Thanks Martin - Thanks for the Routing Directorate review!! > > > On 9/16/22, 12:49 PM, "Lsr on behalf of Martin Vigoureux" < > lsr-boun...@ietf.org on behalf of martin.vigour...@nokia.com> wrote: > > Hi, > > I apologize for providing this review way past the deadline. > The document is of very good quality and clearly the result of careful > work, which makes it hard to find anything to say. > Fortunately, I think I've found something :-) > > > Types in the range 45056-65535 are not to be assigned at this time. > Before any assignments can be made in the 33024-65535 range, there > MUST be an IETF specification that specifies IANA Considerations > that > cover the range being assigned. > I think you mean 45056-65535 rather than 33024-65535 because part of > it > (33024-45055) is covered as FCFS. > > Agreed. KT> Ack - will be fixed. > > > Also, this appears twice: Section 13.5 and 13.6 > > Agreed that it needs to be changed here as well. These are separate > registries. KT> Ack - will be fixed. > > > Beyond that, the document looks ready to me. > > As a side note, I'm not sure why segments is between double quotes in > the Abstract. > > Agreed. KT> Ack - will be fixed. Thanks, Ketan > > > Thanks, > Acee > > > -m > > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr >
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
