Re: [radext] I-D Action: draft-ietf-radext-tls-psk-06.txt

  This revision updates the text to clarify recent discussions on PSK identities.

   In short:

* 4279 says UTF-8

* 8446 says tickets are opaque blobs, encrypted and signed

* 9257 says "whoops, yes, those are in conflict, that's the way it is".

  So we can't fix that issue here.  We just have to document it, and live with it.

> On Jan 15, 2024, at 2:12 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-radext-tls-psk-06.txt is now available. It is a work
> item of the RADIUS EXTensions (RADEXT) WG of the IETF.
> 
>   Title:   RADIUS and TLS-PSK
>   Author:  Alan DeKok
>   Name:    draft-ietf-radext-tls-psk-06.txt
>   Pages:   19
>   Dates:   2024-01-15
> 
> Abstract:
> 
>   This document gives implementation and operational considerations for
>   using TLS-PSK with RADIUS/TLS (RFC6614) and RADIUS/DTLS (RFC7360).
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-radext-tls-psk/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-radext-tls-psk-06.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-radext-tls-psk-06
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext