Hi all,

This version adequately addresses my previous reviews.

The only remaining comments I have are triggered by the recent mgt exercise 
https://mailarchive.ietf.org/arch/msg/opsawg/dRBbEoJ3Kgd8U9uvdcQbdFM3Sfo/ which 
revealed the need to be explicit about the intended behavior on some few items:

* only a domain name is provisioned
* when both a domain name and a list of addresses are provided (e.g., should 
that domain name passed to a resolution library)
* address selection procedure when a list of @ is available (e.g., should 8305 
be followed)
* keepalives

I know that RFC 8907 is silent about items 1-3, but that’s not a reason to not 
remedy to that and have clear guidance here.

Cheers,
Med

De : Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>
Envoyé : lundi 24 juin 2024 14:35
À : ops...@ietf.org
Cc : uta@ietf.org
Objet : [OPSAWG]WG LC: draft-ietf-opsawg-tacacs-tls13

With shepherd in hand (thanks, Med), we are kicking off a two-week working 
group last call for the TACACS+ secured with TLS 1.3 draft.  This draft has 
received several reviews, and the authors have addressed all outstanding 
comments.  That said, I have re-requested reviews from SEC DIR and OPS DIR to 
confirm it has resolved previously-raised issues.

The question about port seems to have been addressed with a custom port being 
an appropriate proposal.

The chairs would like all comments and feedback by July 8, 2024.  We will be 
re-running the IPR poll in parallel.

(Copying TLS in Applications [uta] list for more TLS application-layer 
visibility.)

Thanks.

Joe
____________________________________________________________________________________________________________
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.
_______________________________________________
Uta mailing list -- uta@ietf.org
To unsubscribe send an email to uta-le...@ietf.org

Reply via email to