Re-, Thanks for clarifying.
Added new text to cover these two points: https://github.com/boucadair/attachment-circuit-model/commit/f11efbc5400ce5c4106ce4b57056fde4c8765bc1 The full changes can be tracked using the link shared in my first reply: https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/attachment-circuit-model/draft-ietf-opsawg-teas-common-ac.txt&url_2=https://boucadair.github.io/attachment-circuit-model/Eric-IESG-review/draft-ietf-opsawg-teas-common-ac.txt . Cheers, Med De : Eric Vyncke (evyncke) <evyn...@cisco.com> Envoyé : mardi 14 janvier 2025 13:10 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; The IESG <i...@ietf.org> Cc : draft-ietf-opsawg-teas-common...@ietf.org; opsawg-cha...@ietf.org; opsawg@ietf.org; rro...@ciena.com Objet : Re: Éric Vyncke's No Objection on draft-ietf-opsawg-teas-common-ac-14: (with COMMENT) Bonjour Med, And thanks for your prompt reply and proposed changes. I have removed the comments that are agreed upon and left the ones with more information by me (look for EV>) Regards -éric From: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Date: Tuesday, 14 January 2025 at 10:41 To: Eric Vyncke (evyncke) <evyn...@cisco.com<mailto:evyn...@cisco.com>>, The IESG <i...@ietf.org<mailto:i...@ietf.org>> Cc: draft-ietf-opsawg-teas-common...@ietf.org<mailto:draft-ietf-opsawg-teas-common...@ietf.org> <draft-ietf-opsawg-teas-common...@ietf.org<mailto:draft-ietf-opsawg-teas-common...@ietf.org>>, opsawg-cha...@ietf.org<mailto:opsawg-cha...@ietf.org> <opsawg-cha...@ietf.org<mailto:opsawg-cha...@ietf.org>>, opsawg@ietf.org<mailto:opsawg@ietf.org> <opsawg@ietf.org<mailto:opsawg@ietf.org>>, rro...@ciena.com<mailto:rro...@ciena.com> <rro...@ciena.com<mailto:rro...@ciena.com>> Subject: RE: Éric Vyncke's No Objection on draft-ietf-opsawg-teas-common-ac-14: (with COMMENT) Hi Éric, Thank you for the review. Please see inline. Cheers, Med > -----Message d'origine----- > De : Éric Vyncke via Datatracker <nore...@ietf.org<mailto:nore...@ietf.org>> > Envoyé : lundi 13 janvier 2025 17:43 > À : The IESG <i...@ietf.org<mailto:i...@ietf.org>> > Cc : > draft-ietf-opsawg-teas-common...@ietf.org<mailto:draft-ietf-opsawg-teas-common...@ietf.org>; > opsawg- > cha...@ietf.org<mailto:cha...@ietf.org>; > opsawg@ietf.org<mailto:opsawg@ietf.org>; > rro...@ciena.com<mailto:rro...@ciena.com>; > rro...@ciena.com<mailto:rro...@ciena.com> > Objet : Éric Vyncke's No Objection on draft-ietf-opsawg-teas- > common-ac-14: (with COMMENT) > > > ### Section 4.1 > > It is rather unclear what `server` means in this document, even > if I can guess > some controllers in the SP domain. [Med] Is there any specific occurrence that you think is ambiguous? EV> it is in the definition of `'server-assigned-reference'` > > ### Section 4.3 > Should there a choice on how to authenticate OSPFv3 either RFC > 4552 or RFC 7166 > ? > [Med] We used to have ipsec as an option but we removed that part of the code it as we wanted to have something **common** for OSPF independent of the version. FYI, device models implemented out there such as https://github.com/openconfig/public/tree/master/release/models/ospf do not even cover ospfv3, let alone an internal option. EV> then it is perhaps worth mentionning the RFC 4553 (ipsec auth) is not supported. BTW, I also support the removal of RFC 4552 support but this should be mentioned. ____________________________________________________________________________________________________________ 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.
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
