Hi Kotikalapudi/Alex,

Thank you for your effort put into this document.

FWIW, you may find my review can be found at (*):

  *   Pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2025/draft-ietf-grow-route-leak-detection-mitigation-12-rev%20Med.pdf
  *   Doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/raw/refs/heads/master/2025/draft-ietf-grow-route-leak-detection-mitigation-12-rev%20Med.doc

I'm supportive of means to help route leak prevention/detection, however I have 
some reservations about the approach in the draft:

  *   The main argument (not technical one, though) is that the solution can be 
faster to deploy. That argument is appealing... however, I don't think that 
argument stands anymore after several years.
  *   Unless I'm mistaken, there is no registry to record the requested class.
  *   The doc mandates how policies are configured (including on those ASes not 
adhering to the spec!): I'm not comfortable with that tone in the draft, let 
alone that we don't have means to enforce these various MUST on policies.

Cheers,
Med

(*) I'm definitely missing of the context around the draft
(*) I know that it is frustrating to receive this kind of comments after ten 
years working on a proposal. Sorry for that.

____________________________________________________________________________________________________________
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