[HOKEY] RFC 6630 on EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)

rfc-editor@rfc-editor.org Sat, 02 June 2012 01:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9A87211E80FC; Fri, 1 Jun 2012 18:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.027
X-Spam-Status: No, score=-103.027 tagged_above=-999 required=5 tests=[AWL=2.050, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id tSVagHyoPdzD; Fri, 1 Jun 2012 18:52:02 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 0A4B911E8116; Fri, 1 Jun 2012 18:52:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5B181B1E008; Fri, 1 Jun 2012 18:51:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120602015114.5B181B1E008@rfc-editor.org>
Date: Fri, 1 Jun 2012 18:51:14 -0700 (PDT)
Cc: hokey@ietf.org, rfc-editor@rfc-editor.org
Subject: [HOKEY] RFC 6630 on EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 01:52:02 -0000

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

        RFC 6630

        Title:      EAP Re-authentication Protocol Extensions for 
                    Authenticated Anticipatory Keying (ERP/AAK) 
        Author:     Z. Cao, H. Deng,
                    Q. Wu, G. Zorn, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2012
        Mailbox:    zehn.cao@gmail.com, 
        Pages:      20
        Characters: 40373
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hokey-erp-aak-10.txt

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

The Extensible Authentication Protocol (EAP) is a generic framework
supporting multiple types of authentication methods.

The EAP Re-authentication Protocol (ERP) specifies extensions to EAP
and the EAP keying hierarchy to support an EAP method-independent
protocol for efficient re-authentication between the peer and an EAP
re-authentication server through any authenticator.

Authenticated Anticipatory Keying (AAK) is a method by which
cryptographic keying material may be established upon one or more
Candidate Attachment Points (CAPs) prior to handover.  AAK uses the
AAA infrastructure for key transport.

This document specifies the extensions necessary to enable AAK
support in ERP.  [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