50 likes | 134 Vues
This document provides an overview of the latest EAP Working Group drafts, including updates on EAP keying framework, network selection, network discovery, NAI update, and compliance with RFC 3748. It outlines ongoing discussions, revisions, and future plans.
E N D
EAP WGDocument Status IETF-60 Jari Arkko Bernard Aboba
RFCs • RFC 3579 aka “EAP over RADIUS” published earlier [Individual] • RFC 3748 aka “2284bis” has been published recently
Drafts (1/3) • EAP state machine document • Draft-ietf-eap-statemachine-04.{txt,pdf} • In RFC editor queue • Some discussion on the list nevertheless • EAP keying framework • Draft-ietf-eap-keying-03.txt • One open issue about key naming • EAP over DIAMETER [AAA WG] • draft-ietf-aaa-eap-08.txt • WG Last Call finished • A few existing issues (resolutions proposed) • A new draft to appear right after the IETF => IESG
Drafts (2/3) • Network selection problem definition • Draft-ietf-eap-netsel-problem-01.txt • Revised based on discussion • Needs more discussion and a new revision • Will try to finish this work fast after San Diego, however • Network discovery draft [Individual] • Draft-adrangi-eap-network-discovery-01.txt • Revised based on discussion, needs another revision • Targeting individual submission process due to tight 3GPP schedule • NAI update, RFC2486bis [RADEXT WG] • Draft-arkko-roamops-rfc2486bis-02.txt • In RADEXT WG LC, to end on August 26th
Drafts (3/3) • Methods [individual] Methods submitted for RFC publication: • EAP FAST was reviewed by IESG and needs to be revised, due to TLS extension IANA rules • EAP SIM and AKA have been submitted to the RFC Editor, but need an AD sponsored review • RFC 3748 compliance review by EAP WG would be useful • All the security properties required in 3748 are documented? • Follows other MUSTs and SHOULDs in RFC 3748? • Binding problem definition • Draft-puthenkulam-eap-binding-04.txt • Not updated since IETF-58; abandoned