[HOKEY] Fwd: New Version Notification for draft-ietf-hokey-erp-aak-07.txt

Zhen Cao <zehn.cao@gmail.com> Tue, 17 January 2012 09:11 UTC

Return-Path: <zehn.cao@gmail.com>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 352FE21F847B for <hokey@ietfa.amsl.com>; Tue, 17 Jan 2012 01:11:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level:
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GByj0+qoDVM0 for <hokey@ietfa.amsl.com>; Tue, 17 Jan 2012 01:10:59 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE6D21F844C for <hokey@ietf.org>; Tue, 17 Jan 2012 01:10:59 -0800 (PST)
Received: by iaae16 with SMTP id e16so11007577iaa.31 for <hokey@ietf.org>; Tue, 17 Jan 2012 01:10:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=dVW0w9W2NGVOSJdi0cODA4IkHOpN/oSse5n12yTuTBM=; b=gk4OTSz+T4oiHi2W05NvAX6OJHmlpw2D8tqGh1hLICfjri12RbmCbGof3Konwo2Vte noZZZcS8K+qqBmbIe9zWe0RmEIbj9bePh0Fy6LDyUmGXIuiezo8sD77eU2pYBOADb6y2 4gQSAqrWe1yocJ+dBC68DYa1EpomYxYqhaqDU=
MIME-Version: 1.0
Received: by 10.50.10.225 with SMTP id l1mr16688740igb.9.1326791459205; Tue, 17 Jan 2012 01:10:59 -0800 (PST)
Received: by 10.43.132.197 with HTTP; Tue, 17 Jan 2012 01:10:59 -0800 (PST)
In-Reply-To: <20120117070823.32246.89759.idtracker@ietfa.amsl.com>
References: <20120117070823.32246.89759.idtracker@ietfa.amsl.com>
Date: Tue, 17 Jan 2012 17:10:59 +0800
Message-ID: <CAProHAQQzuQ-69s9w-ynhf3c9tnYFdbWcKdSKg-ftTZXNOJTzg@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: hokey <hokey@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [HOKEY] Fwd: New Version Notification for draft-ietf-hokey-erp-aak-07.txt
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: Tue, 17 Jan 2012 09:11:00 -0000

Hi All,

Please find the new version of the erp-aak draft. Thanks.


---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Tue, Jan 17, 2012 at 3:08 PM
Subject: New Version Notification for draft-ietf-hokey-erp-aak-07.txt
To: sunseawq@huawei.com
Cc: denghui02@gmail.com, zehn.cao@gmail.com, sunseawq@huawei.com,
glenzorn@gmail.com


A new version of I-D, draft-ietf-hokey-erp-aak-07.txt has been
successfully submitted by Qin Wu and posted to the IETF repository.

Filename:        draft-ietf-hokey-erp-aak
Revision:        07
Title:           EAP Re-authentication Protocol Extensions for
Authenticated Anticipatory Keying (ERP/AAK)
Creation date:   2012-01-17
WG ID:           hokey
Number of pages: 18

Abstract:
  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.




The IETF Secretariat


-- 
Best regards,
Zhen