Subject: [saag] IETF92: RADEXT WG session report

From: <[email-masked]>
Date: Thu, 26 Mar 2015 16:22:16 +0000

We meet on Monday afternoon. About 15 people in the room but unfortunately key participants were not present in the room due to personal constraints. As a consequence, the meeting was not so lively as usual and was shorter than expected (less than 1h).

About WG documents:
*  Network Access Identifier (RFC 4282bis - draft-ietf-radext-nai-15) and RADIUS packets fragmentation (draft-ietf-radext-radius-fragmentation-12) have successfully passed the IESG evalution and are ready for publication.
* NAI-based Dynamic Peer Discover (draft-ietf-radext-dynamic-discovery-13) has completed the IETF LC and is waiting for expert review before IANA allocation.

Two WGLC will be launched right after the IETF week:
* Larger Packets for RADIUS over TCP (draft-ietf-radext-bigger-packets-03)
* IP Port Configuration and Reporting (draft-ietf-radext-ip-port-radius-ext-03)

3 new WG documents have been adopted (to be confirmed on the mailing list):
* Dynamic Authorization Proxying (draft-dekok-radext-coa-proxy-00) as candidate Standards Track RFC. This document gives guidance on how to proxy CoA messages defined in RFC5176.
* Correct use of EAP-Response/Identity (draft-winter-radext-populating-eapidentity-01) as candidate BCP. It provides recommendations for implementers of EAP peers regarding the type of EAP identities to use in EAP messages.
* RADIUS Data Types (draft-dekok-radext-datatypes-05) as informational RFC. This document clarifies the use of data type in RADIUS and defines an IANA registry for the data types that was omitted when specifying RADIUS (RFC2865)

We've discussed the errata on RFC 5176 and the WG agreed on the proposed status (Verified). This was also confirmed on the mailing list.

Finally, the WG charter has been discussed. A new charter is required as the current one is quite obsolete. A proposed text has been submitted on the mailing list and needs to be commented.

RADEXT chairs.

_________________________________________________________________________________________________________________________

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.