Joe:

This resolves my concern.  I've asked the SecDir Secretary how to post an 
unrequested review.

Russ


> On Apr 3, 2025, at 12:49 PM, Joe Clarke (jclarke) <[email protected]> wrote:
> 
> Thanks, Russ.  The authors have published -19.  The diff is at 
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-tacacs-tls13-19.  
> If you agree with the modified text can you amend your DIR review to Ready?
>  
> Thanks.
>  
> Joe
>  
> From: Russ Housley <[email protected] <mailto:[email protected]>>
> Date: Thursday, March 13, 2025 at 23:02
> To: Douglas Gash (dcmgash) <[email protected] 
> <mailto:[email protected]>>
> Cc: [email protected] <mailto:[email protected]> 
> <[email protected] <mailto:[email protected]>>, IETF 
> SecDir <[email protected] <mailto:[email protected]>>, 
> [email protected] 
> <mailto:[email protected]> 
> <[email protected] 
> <mailto:[email protected]>>, [email protected] 
> <mailto:[email protected]> <[email protected] <mailto:[email protected]>>, 
> [email protected] <mailto:[email protected]> <[email protected] 
> <mailto:[email protected]>>
> Subject: Re: [Last-Call] Secdir last call review of 
> draft-ietf-opsawg-tacacs-tls13-18
> 
> This approach works for me.
>  
> Russ
> 
> 
> On Mar 13, 2025, at 5:33 AM, Douglas Gash (dcmgash) 
> <[email protected] 
> <mailto:[email protected]>> wrote:
>  
> Just to confirm, there are three authentication methods (Cert, PSK, RPK). 
> Cert MUST be implemented, the other two MAY be implemented, as they become 
> mature.
>  
> We have made two specific changes, which we hope will clarify:
>  
> 1.      We have indicated that the two options (PSK and RPK) are alternatives 
> to Cert based, to avoid the impression that they are augmentations which are 
> intended to work in combination.
> 2.      In the start of the Cert based section, we have clarified that this 
> section covers Cert based only.
>  
> Please let us know if this new version changes clarify this intent.

_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to