Hi all, We didn't initially include the 9105 example at https://datatracker.ietf.org/doc/html/rfc9105#name-example-tacacs-authenticati in draft-ietf-opsawg-secure-tacacs-yang because we wanted to have an example with TLS use.
However, when reviewing the 9105 example it appeared that it has several problems. The fix can be seen https://github.com/boucadair/secure-tacacs-yang/blob/main/json-example/9105-ex.json As we are obsoleting 9105, I'm not sure there is a value in filling an erratum for this. We will thus (re)include the corrected example back in an appendix of draft-ietf-opsawg-secure-tacacs-yang. When checking the example, also found a minor error in a must statement: https://github.com/boucadair/secure-tacacs-yang/commit/bc6cbdc3f56927f2dbd687ab0723cb5ac30c680a. These fixes will appear in a next version to be published SOON. 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.
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
