Hi Acee, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Acee Lindem <acee.i...@gmail.com> > Envoyé : mercredi 26 mars 2025 01:56 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> > Cc : The IESG <i...@ietf.org>; draft-ietf-lsr-ospf-prefix-extended- > fl...@ietf.org; lsr-cha...@ietf.org; lsr <lsr@ietf.org> > Objet : Re: Mohamed Boucadair's Yes on draft-ietf-lsr-ospf-prefix- > extended-flags-06: (with COMMENT) > > > Speaking as document shepherd: > > Hi Med, > > See inline. > > > > On Mar 25, 2025, at 4:28 AM, Mohamed Boucadair via Datatracker > <nore...@ietf.org> wrote: > > > > Mohamed Boucadair has entered the following ballot position for > > draft-ietf-lsr-ospf-prefix-extended-flags-06: Yes > > > > When responding, please keep the subject line intact and reply to > all > > email addresses included in the To and CC lines. (Feel free to cut > > this introductory paragraph, however.) > > > > -------------------------------------------------------------------- > > COMMENT: > > -------------------------------------------------------------------- > > > > Hi Ran, Detao, Peter, Ketan, and Liyan, > > > > Thank you for the effort put into this specification. This is an > > important piece of work. > > > > I definitely support this. I have some few comments that I’d like to > > be addressed, especially the first three comments and the comment in > Section 3. > > > > # General > > > > ## Should we have a recommendation whether the remaining flags are > > assigned first vs. use of the sub-TLV? I think we need a guidance > (not rigid, though). > > I don't even know what you mean by this question - I doubt the authors > do. > [Med] Let me reformulate it then. When looking at "https://www.iana.org/assignments/ospfv2-parameters/ospfv2-parameters.xhtml#extended-prefix-tlv-flags";, I see that three flags were assigned out of 8. So, when new flags are being proposed, (1) Should we allocate the remaining flags in the main TLV till exhaustion and then use the PAF sub-TLV Or (2) Should be selective in future usage that will be elected to use the main flags vs. PAF sub-TLV As a side note, It would be helpful if the IANA registry indicate the unassigned flags. Not sur > > > > > ## Not sure if this is assumed, but is it allowed that a group of > bits > > (e.g., 2 > > bits) may be allocated for one single purpose? The current > description > > seems to assume that flags will be allocated individually. > > This is not limited by the specification so if one were to define a > Trid (i.e., 3 states), it could take 2 bits. [Med] Glad to hear that. My comment is to anchor the possibility to allocate multiple bits for one single usage in the base spec. > However, the draft that defines this should deal with that. It need > not be here. > > > > > ## Should we have configuration parameters to control the use of the > > flags (e.g., rfc8362#appendix-A)? > > No. Configuration will be described in the future documents that > define the bits. [Med] I wasn't referring to individual flags themselves, but the actual use of the sub-TLV at the first place. The approach in rfc8362#appendix-A is what I'm looking for. > > Thanks, > Acee > ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
