Hi Pierre,  Maxence, and Paolo,

Many thanks for the effort put into this document. I really like this.

FWIW, you may find a review here:


  *   pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-bmp-loc-peer-00-rev%20Med.pdf
  *   doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/raw/refs/heads/master/2025/draft-ietf-grow-bmp-loc-peer-00-rev%20Med.doc

I have a doubt about the implications on 9096. I included the excerpt in the 
review so that you can check.

On the address type design, the current values can be handled without an 
explicit address type field (length=1 is indication for self-originated @, no 
need distinguish IPv4 vs IPv6 if the design mandates encoding IPv4 addresses as 
IPv4-embeded IPv6 addresses, the other remaining type can fall under the 
zone-id cons in, e.g., rfc6874.). I understand that having that field is a 
provision future types, but are there other address types not already covered 
here?

If you maintain the address type registry, please add more considerations about 
the registry policy.

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

Reply via email to