Hi Camilo, Paolo, Pierre, Yunan, and Thomas, FWIW, please find a review of this document at:
* pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-path-marking-tlv-02-rev%20Med.pdf * doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/refs/heads/master/2025/draft-ietf-grow-bmp-path-marking-tlv-02-rev%20Med.doc Overall, I think that the spec can be simplified. I don't see the need to have the enterprise TLV included here. There are some few issues with encoding and, again, there is a room to simplify (e.g., avoid the bitmask). I wouldn't be surprised if you received contradictory comments as the doc is out there since 2019 :-) Aah, do you really need to have a normative dependency on a spec that was expired since 2012? I would avoid that by having these parts self-contained. Also, please update the terminology to be aligned with RFC 4271. Thank you. Cheers, Med ____________________________________________________________________________________________________________ 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.
_______________________________________________ GROW mailing list -- grow@ietf.org To unsubscribe send an email to grow-le...@ietf.org
