Early Review of draft-ietf-opsawg-secure-tacacs-yang-04
review-ietf-opsawg-secure-tacacs-yang-04-yangdoctors-early-rahman-2025-01-22-00
Request | Review of | draft-ietf-opsawg-secure-tacacs-yang |
---|---|---|
Requested revision | No specific revision (document currently at 10) | |
Type | Early Review | |
Team | YANG Doctors (yangdoctors) | |
Deadline | 2025-01-31 | |
Requested | 2025-01-10 | |
Requested by | Joe Clarke | |
Authors | Mohamed Boucadair , Bo Wu | |
I-D last updated | 2025-04-30 (Latest revision 2025-04-30) | |
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) |
|
Assignment | Reviewer | Reshad Rahman |
State | Completed | |
Request | Early review on draft-ietf-opsawg-secure-tacacs-yang by YANG Doctors Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/yang-doctors/UYtlu_klmjRDHOrRgxYXI6qlAJo | |
Reviewed revision | 04 (document currently at 10) | |
Result | Ready w/issues | |
Completed | 2025-01-22 |
review-ietf-opsawg-secure-tacacs-yang-04-yangdoctors-early-rahman-2025-01-22-00
Disclaimer: I am not a TACACS+ nor a TLS expert. Overall the document looks good. Here are what I perceive are issues which should be addressed. "leaf address": it is of type inet:host, so is not necessarily an IP address as per the name and description. Rename to "server" or "host"? But this would be a non backwards compatible change.... At least change the description to say "IP address or host name of the ACACS+ server." leaf address { type inet:host; mandatory true; description "The address of the TACACS+ server."; } It is not clear to me why "leaf domain-name" was added. Section 3 refers to section 3.3 of [I-D.ietf-opsawg-tacacs-tls13] but that section does not mention domain-name. 'domain-name': Provides a domain name of the server per Section 3.3 of [I-D.ietf-opsawg-tacacs-tls13]. "leaf vrf-instance": not needed if source-type is source-interface (since the VRF of the source interface would be used)? Add "must not()" statement or describe the behaviour if vrf-instance does not have the same value as source-interface's VRF. "leaf port": remove the commented out “default 49”? "choice source-type": do we need “mandatary true”? Same question for the 2 instances of “choice ref-or-explicit” "leaf single-connection": please add a reference. I think that should be to Section 4.3 of [RFC8907].