[HOKEY] RFC 6697 on Handover Keying (HOKEY) Architecture Design

rfc-editor@rfc-editor.org Thu, 26 July 2012 20:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 262B311E80BA; Thu, 26 Jul 2012 13:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.27
X-Spam-Level:
X-Spam-Status: No, score=-102.27 tagged_above=-999 required=5 tests=[AWL=0.330, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 9hD-rKho0bzv; Thu, 26 Jul 2012 13:28:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 866A411E80D3; Thu, 26 Jul 2012 13:28:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2850672E009; Thu, 26 Jul 2012 13:28:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120726202833.2850672E009@rfc-editor.org>
Date: Thu, 26 Jul 2012 13:28:33 -0700 (PDT)
Cc: hokey@ietf.org, rfc-editor@rfc-editor.org
Subject: [HOKEY] RFC 6697 on Handover Keying (HOKEY) Architecture Design
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: Thu, 26 Jul 2012 20:28:50 -0000

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

        
        RFC 6697

        Title:      Handover Keying (HOKEY) Architecture Design 
        Author:     G. Zorn, Ed.,
                    Q. Wu, T. Taylor,
                    Y. Nir, K. Hoeper,
                    S. Decugis
        Status:     Informational
        Stream:     IETF
        Date:       July 2012
        Mailbox:    glenzorn@gmail.com, 
                    bill.wu@huawei.com, 
                    tom.taylor.stds@gmail.com,
                    ynir@checkpoint.com, 
                    khoeper@motorolasolutions.com, 
                    sdecugis@freediameter.net
        Pages:      20
        Characters: 44243
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hokey-arch-design-11.txt

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

The Handover Keying (HOKEY) Working Group seeks to minimize handover
delay due to authentication when a peer moves from one point of
attachment to another.  Work has progressed on two different
approaches to reduce handover delay: early authentication (so that
authentication does not need to be performed during handover), and
reuse of cryptographic material generated during an initial
authentication to save time during re-authentication.  A basic
assumption is that the mobile host or "peer" is initially
authenticated using the Extensible Authentication Protocol (EAP),
executed between the peer and an EAP server as defined in RFC 3748.

This document defines the HOKEY architecture.  Specifically, it
describes design objectives, the functional environment within which
handover keying operates, the functions to be performed by the HOKEY
architecture itself, and the assignment of those functions to
architectural components.  It goes on to illustrate the operation of
the architecture within various deployment scenarios that are
described more fully in other documents produced by the HOKEY Working
Group.  This document is not an Internet Standards Track specification;
it is published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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