IETF Last Call Review of draft-ietf-opsawg-secure-tacacs-yang-09
review-ietf-opsawg-secure-tacacs-yang-09-opsdir-lc-tsou-2025-04-18-00

Request Review of draft-ietf-opsawg-secure-tacacs-yang
Requested revision No specific revision (document currently at 13)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2025-03-27
Requested 2025-03-06
Requested by Joe Clarke
Authors Mohamed Boucadair , Bo Wu
I-D last updated 2025-07-10 (Latest revision 2025-07-07)
Completed reviews Yangdoctors Early review of -04 by Reshad Rahman (diff)
Opsdir IETF Last Call review of -09 by Tina Tsou (diff)
Yangdoctors IETF Last Call review of -05 by Reshad Rahman (diff)
Yangdoctors IETF Last Call review of -11 by Reshad Rahman (diff)
Secdir IETF Last Call review of -12 by Robert Sparks (diff)
Genart IETF Last Call review of -11 by Ines Robles (diff)
Comments 
We had an early YANG Doc review, and we want to make sure that all issues have been addressed, plus make sure the model resonates with the ops community.
Assignment Reviewer Tina Tsou
State Completed
Request IETF Last Call review on draft-ietf-opsawg-secure-tacacs-yang by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/6tN9Fzr9Ym5Hc3EWcw8MZyatXtw
Reviewed revision 09 (document currently at 13)
Result Has nits
Completed 2025-04-18
review-ietf-opsawg-secure-tacacs-yang-09-opsdir-lc-tsou-2025-04-18-00
- Consider clarifying the default port for TACACS+ over TLS once IANA assigns it.
- Note using TLS requires the device to also implement the relevant crypto key/cert models.
- Think about VRF uniqueness scenario, if needed, adjust the YANG unique statement.
- "port number of TACACS+ server port number" is repetitive