RFC 5749 on Distribution of EAP-Based Keys for Handover and Re-Authentication

rfc-editor@rfc-editor.org Wed, 10 March 2010 19:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id DD21A3A69F8; Wed, 10 Mar 2010 11:19:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id E2-I11WyQ76D; Wed, 10 Mar 2010 11:19:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9C3273A6C38; Wed, 10 Mar 2010 11:18:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 188AEE073C; Wed, 10 Mar 2010 11:18:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5749 on Distribution of EAP-Based Keys for Handover and Re-Authentication
From: rfc-editor@rfc-editor.org
Message-Id: <20100310191829.188AEE073C@rfc-editor.org>
Date: Wed, 10 Mar 2010 11:18:29 -0800
Cc: hokey@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2010 19:20:06 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5749

        Title:      Distribution of EAP-Based Keys for 
                    Handover and Re-Authentication 
        Author:     K. Hoeper, Ed.,
                    M. Nakhjiri, Y. Ohba, Ed.
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    khoeper@motorola.com, 
        Pages:      12
        Characters: 27242
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hokey-key-mgm-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5749.txt

This document describes an abstract mechanism for delivering root
keys from an Extensible Authentication Protocol (EAP) server to
another network server that requires the keys for offering security
protected services, such as re-authentication, to an EAP peer.  The
distributed root key can be either a usage-specific root key (USRK),
a domain-specific root key (DSRK), or a domain-specific usage-
specific root key (DSUSRK) that has been derived from an Extended
Master Session Key (EMSK) hierarchy previously established between
the EAP server and an EAP peer.  This document defines a template for
a key distribution exchange (KDE) protocol that can distribute these
different types of root keys using a AAA (Authentication,
Authorization, and Accounting) protocol and discusses its security
requirements.  The described protocol template does not specify
message formats, data encoding, or other implementation details.  It
thus needs to be instantiated with a specific protocol (e.g., RADIUS
or Diameter) before it can be used.  [STANDARDS TRACK]

This document is a product of the Handover Keying Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC