Protocol Action: 'Extensible Authentication Protocol (EAP) Key Management Framework' to Proposed Standard

The IESG <> Fri, 30 May 2008 22:31 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id CABA93A6C23; Fri, 30 May 2008 15:31:30 -0700 (PDT)
Received: by (Postfix, from userid 30) id 7CA353A6BDA; Fri, 30 May 2008 15:31:29 -0700 (PDT)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Extensible Authentication Protocol (EAP) Key Management Framework' to Proposed Standard
Message-Id: <>
Date: Fri, 30 May 2008 15:31:29 -0700
Cc: Internet Architecture Board <>, eap chair <>, eap mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

The IESG has approved the following document:

- 'Extensible Authentication Protocol (EAP) Key Management Framework '
   <draft-ietf-eap-keying-22.txt> as a Proposed Standard

This document is the product of the Extensible Authentication Protocol 
Working Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:

Technical Summary

  This document specifies the EAP key hierarchy and provides a
  framework for the transport and usage of keying material generated
  by EAP authentication algorithms, known as "methods". It also 
  provides a system-level security analysis, according to the 
  principles described in "Guidance for AAA Key Management".

Working Group Summary

  Much of the WG discussion of this document centered on aspects of
  key management, including key creation, deletion, transport and
  naming. EAP usage is growing increasingly diverse, so that there
  was discussion about whether the the examples depict the issues 
  encountered in existing EAP lower layer implementations, and whether 
  the principles articulated are universal or merely true for all
  existing implementations. There was also discussion about
  the relationship between this document and "Guidance for AAA Key
  Management" which articulates principles that AAA Key Management
  solutions must satisfy to qualify for standards track publication.

Document Quality

  There are existing implementations of this document, and further    
  implementations are likely.


  Bernard Aboba is the document shepherd. The responsible Area Director
  is Jari Arkko. No IANA expert is needed.

IETF-Announce mailing list