[radext] Fwd: New Version Notification for draft-dekok-radext-radiusv11-02.txt

[Alan DeKok <[e-mail]>]

  I've added some text on flags in the packet header.  The intention of the flags is to allow client / server to know whether or not there was end-to-end security for RADIUS.

> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-dekok-radext-radiusv11-02.txt
> Date: March 7, 2023 at 11:05:46 AM EST
> To: "Alan DeKok" <[e-mail]>
> 
> 
> A new version of I-D, draft-dekok-radext-radiusv11-02.txt
> has been successfully submitted by Alan DeKok and posted to the
> IETF repository.
> 
> Name:		draft-dekok-radext-radiusv11
> Revision:	02
> Title:		RADIUS/TLS Version 1.1
> Document date:	2023-03-07
> Group:		Individual Submission
> Pages:		22
> URL:            https://www.ietf.org/archive/id/draft-dekok-radext-radiusv11-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-dekok-radext-radiusv11/
> Html:           https://www.ietf.org/archive/id/draft-dekok-radext-radiusv11-02.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dekok-radext-radiusv11
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-dekok-radext-radiusv11-02
> 
> Abstract:
>   This document defines Application-Layer Protocol Negotiation
>   Extensions for use with RADIUS/TLS and RADIUS/DTLS.  These extensions
>   permit the negotiation of an additional application protocol for
>   RADIUS over (D)TLS.  No changes are made to RADIUS/UDP or RADIUS/TCP.
>   The extensions allow the negotiation of a transport profile where the
>   RADIUS shared secret is no longer used, and all MD5-based packet
>   signing and attribute obfuscation methods are removed.  When this
>   extension is used, the previous Authenticator field is repurposed to
>   contain an explicit request / response identifier, called a Token.
>   The Token also allows more than 256 packets to be outstanding on one
>   connection.
> 
>   This extension can be seen as a transport profile for RADIUS, as it
>   is not an entirely new protocol.  It uses the existing RADIUS packet
>   layout and attribute format without change.  As such, it can carry
>   all present and future RADIUS attributes.  Implementation of this
>   extension requires only minor changes to the protocol encoder and
>   decoder functionality.  The protocol defined by this extension is
>   named "RADIUS version 1.1", or "radius/1.1".
> 
> 
> 
> 
> The IETF Secretariat
> 
>