Hi Med, Thank you for your quick response and for considering the VRF aspect. I see your point that since our TACACS+ YANG module doesn’t define VRF itself (it simply references the network instances model), it might not require any changes on that front. That makes sense to me, and I’m comfortable with leaving it as is.
If you happen to change your mind or think of any improvement regarding VRF handling later on, I’m certainly open to discussing it again. For now, I’m glad we’re on the same page and can move forward. Thanks again for your feedback, and I’m looking forward to finalizing this document with you soon. Best regards, Tina From: [email protected] Date: 2025年4月25日 (周五) 03:17 Subject: [External] RE: [OPS-DIR]Opsdir ietf last call review of draft-ietf-opsawg-secure-tacacs-yang-09 To: "Tina Tsou"<[email protected]> Cc: "[email protected]"<[email protected]>, " [email protected]"< [email protected]>, "[email protected]"< [email protected]>, "[email protected]"<[email protected]> Hi Tina, Thank you for clarifying the VRF point. I don’t think a change is needed as we don’t define the VRF itself but I will think further about this. Cheers, Med *De :* Tina Tsou <[email protected]> *Envoyé :* vendredi 18 avril 2025 19:28 *À :* BOUCADAIR Mohamed INNOV/NET <[email protected]> *Cc :* [email protected]; [email protected]; [email protected]; [email protected] *Objet :* Re: [External] RE: [OPS-DIR]Opsdir ietf last call review of draft-ietf-opsawg-secure-tacacs-yang-09 Bonjour Med, Replies are inline. From: <[email protected]>[email protected] Date: 2025年4月18日 (周五) 02:18 Subject: [External] RE: [OPS-DIR]Opsdir ietf last call review of draft-ietf-opsawg-secure-tacacs-yang-09 To: "Tina Tsou"< <[email protected]>[email protected]>, " <[email protected]>[email protected]"< <[email protected]>[email protected]> Cc: " <[email protected]> [email protected]"< <[email protected]> [email protected]>, " <[email protected]> [email protected]"< <[email protected]>[email protected]>, " <[email protected]>[email protected]"< <[email protected]>[email protected]> Hi Tina, Thank you for the review. Please see inline. Cheers, Med (as doc editor) > -----Message d'origine----- > De : Tina Tsou via Datatracker < <[email protected]>[email protected]> > Envoyé : vendredi 18 avril 2025 10:18 > À : <[email protected]>[email protected] > Cc : <[email protected]> [email protected]; last- > <[email protected]>[email protected]; <[email protected]>[email protected] > Objet : [OPS-DIR]Opsdir ietf last call review of draft-ietf-opsawg- > secure-tacacs-yang-09 > > > Document: draft-ietf-opsawg-secure-tacacs-yang > Title: A YANG Data Model for Terminal Access Controller Access- > Control System Plus (TACACS+) > Reviewer: Tina Tsou > Review result: Has Nits > > - Consider clarifying the default port for TACACS+ over TLS once > IANA assigns it. [Med] We do already have a note for this: Please apply the following replacements: ... * TBD --> the assigned port number in Section 7 of [I-D.ietf-opsawg-tacacs-tls13] > - Note using TLS requires the device to also implement the relevant > crypto key/cert models. [Med] Indeed. This is covered by this text: This YANG module uses types and groupings defined in [RFC6991], [RFC8341], [RFC8343], [RFC8529], [RFC9640], [RFC9641], [RFC9642], and [RFC9645]. > - Think about VRF uniqueness scenario, if needed, adjust the YANG > unique statement. [Med] Can you please elaborate on this one? Thanks. [Tina] Allowing identical addresses in different VRFs. > - "port number of TACACS+ server port number" is repetitive [Med] Good catch. Fixed at <https://github.com/boucadair/secure-tacacs-yang/pull/17/commits/9966efba1eb36cd6868df141fa690ce41d72b9e2> https://github.com/boucadair/secure-tacacs-yang/pull/17/commits/9966efba1eb36cd6868df141fa690ce41d72b9e2 ____________________________________________________________________________________________________________ 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 -- [email protected] To unsubscribe send an email to [email protected]
