[saag] EMU update for IETF 123
Peter Yee <[email protected]>
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <[email protected]> |
The EMU WG met for a single 90-minute session on Wednesday morning. Topics covered were: EAP-EDHOC (see https://datatracker.ietf.org/doc/draft-ietf-emu-eap-edhoc/). This document has completed WGLC and is awaiting its shepherd write-up. EAP-PPT (see https://datatracker.ietf.org/doc/draft-ietf-emu-eap-ppt/ ). This is a newly adopted Internet-Draft using privacy pass tokens for anonymous network access. EAP-AKA FS' PQC (see https://datatracker.ietf.org/doc/draft-ietf-emu-hybrid-pqc-eapaka/ and https://datatracker.ietf.org/doc/draft-ietf-emu-pqc-eapaka/). One covers a hybrid PQC variant to EAP-AKA FS', the other is a pure PQC variant). TEAPv2 (see https://datatracker.ietf.org/doc/draft-dekok-emu-teapv2/). TEAPv1 is documented in RFC 7170. How it is actually fielded is documented in https://datatracker.ietf.org/doc/draft-ietf-emu-rfc7170bis/, which is with the RFC Editor. TEAPv2 aims to correct the many flaws in TEAPv1 based on the learnings from the rfc7170bis effort and years of pain. PQuAKE (a proposal but not a draft, so see https://datatracker.ietf.org/meeting/123/materials/slides-123-emu-pquake-post-quantum-authenticated-key-exchange-00). This an authenticated key exchange using PQC, no digital signatures needed. Could be slipped into EDHOC or made its own EAP method. EAP defaults for devices that need to onboard (see https://datatracker.ietf.org/doc/draft-richardson-emu-eap-onboarding/). Previously presented at IETF 114 prior to when the eap.arpa material was separated out into a separate draft. Use unauthenticated EAP-TLS and a captive portal to provision credentials for a device. New TEAP TLV for Encapsulating DHCPv6 Options (see https://datatracker.ietf.org/doc/draft-lear-teap-config-options/). Send some of those DHCPv6 options in a TEAP TLV instead! Post-Quantum Enhancements to EAP-TLS and EAP-TTLS (see https://datatracker.ietf.org/doc/draft-reddy-emu-pqc-eap-tls/). Gives considerations for incorporating hybrid and pure PQC into EAP-TLS and EAP-TTLS, since there are concerns about large certificates and fragmentation, samong others. Asking for WG adoption. _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]