A new Request for Comments is now available in online RFC libraries.
RFC 9678
Title: Forward Secrecy Extension to the
Improved Extensible Authentication Protocol Method
for Authentication and Key Agreement (EAP-AKA' FS)
Author: J. Arkko,
K. Norrman,
J. Preuß Mattsson
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: jari.ar...@piuha.net,
karl.norr...@ericsson.com,
john.matts...@ericsson.com
Pages: 25
Updates: RFC 5448, RFC 9048
I-D Tag: draft-ietf-emu-aka-pfs-12.txt
URL: https://www.rfc-editor.org/info/rfc9678
DOI: 10.17487/RFC9678
This document updates RFC 9048, "Improved Extensible Authentication
Protocol Method for 3GPP Mobile Network Authentication and Key
Agreement (EAP-AKA')", and its predecessor RFC 5448 with an optional
extension providing ephemeral key exchange. The extension EAP-AKA'
Forward Secrecy (EAP-AKA' FS), when negotiated, provides forward
secrecy for the session keys generated as a part of the
authentication run in EAP-AKA'. This prevents an attacker who has
gained access to the long-term key from obtaining session keys
established in the past. In addition, EAP-AKA' FS mitigates passive
attacks (e.g., large-scale pervasive monitoring) against future
sessions. This forces attackers to use active attacks instead.
This document is a product of the EAP Method Update Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org
