Re: [HOKEY] Last Call: <draft-ietf-hokey-arch-design-08.txt> (Handover Keying (HOKEY) Architecture Design) to Informational RFC

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 21 November 2011 13:02 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 6B68C21F8C3C for <hokey@ietfa.amsl.com>; Mon, 21 Nov 2011 05:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 P8f6v1J8lg9G for <hokey@ietfa.amsl.com>; Mon, 21 Nov 2011 05:02:39 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE1721F8C34 for <hokey@ietf.org>; Mon, 21 Nov 2011 05:02:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id C648B171C02 for <hokey@ietf.org>; Mon, 21 Nov 2011 13:02:38 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1321880554; bh=NhFimv3lrp42nA C7s6WcAPkSNzPHp84MmbYGcNYs7Es=; b=KMhF9hC3fFlvoKtW6NcN+RXTVMONaH S430VQiadt64XvrxHyNRn8zyatFExlq5cxWYhq5HLM/kxfFAlgtsrOQvzvsivc4u tnOOtV5HEH0FZ/wCo3W25kn2dGV+zOAKGpPqx/QvUDmjWmP1wZMGY7Vco/k2n/zC +O///xkOoDsTSUlbdQiTm2QqvUnaP0+b05UjMxWl8RsQjxCtzGVut8e58ZdwiM3m JN7ACFWmhV+1zt6cTHf/jkXiJ21m0HlzRTuLxFn9u/h/YUIyeUHFYfsF7YzWbDUy +j15L+Zr8JBlonm/sXXH0p14MrySidRKSI0xKr1bmfxXKnG1I2ZhTWzw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 12+Mxz+GSpeC; Mon, 21 Nov 2011 13:02:34 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 522DC171CC7; Mon, 21 Nov 2011 13:02:34 +0000 (GMT)
Message-ID: <4ECA4BEA.10209@cs.tcd.ie>
Date: Mon, 21 Nov 2011 13:02:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20111102155614.26099.28031.idtracker@ietfa.amsl.com> <4EC44EEB.4040409@cs.tcd.ie> <4ECA4BB1.8000105@cs.tcd.ie>
In-Reply-To: <4ECA4BB1.8000105@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hokey@ietf.org
Subject: Re: [HOKEY] Last Call: <draft-ietf-hokey-arch-design-08.txt> (Handover Keying (HOKEY) Architecture Design) to Informational RFC
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: Mon, 21 Nov 2011 13:02:40 -0000

Ok, mail crossing in the ether:-) I'll put it on
the Dec 1 telechat.

Thanks,
S.

On 11/21/2011 01:01 PM, Stephen Farrell wrote:
>
> ping: I'm waiting on a confirmation from you...
>
> If you get that to me before tomorrow I can put
> it on the Dec 1 telechat. Or it can go on the
> Dec 15 one if not.
>
> S.
>
> On 11/17/2011 12:01 AM, Stephen Farrell wrote:
>>
>> Folks,
>>
>> IETF last call on this is done. Were there any changes
>> resulting? I didn't see any.
>>
>> Are there any further changes to be made? I can't
>> recall any but this was a last-minute-before-the-
>> cutoff submission so there might be.
>>
>> There was also a secdir review [1] with a nit. Fix that
>> or not as you choose.
>>
>> Once you confirm no more changes are needed to me I'll
>> put it on a telechat agenda,
>>
>> Thanks,
>> S.
>>
>> [1] http://www.ietf.org/mail-archive/web/secdir/current/msg02976.html
>>
>> On 11/02/2011 03:56 PM, The IESG wrote:
>>>
>>> The IESG has received a request from the Handover Keying WG (hokey) to
>>> consider the following document:
>>> - 'Handover Keying (HOKEY) Architecture Design'
>>> <draft-ietf-hokey-arch-design-08.txt> as an Informational RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2011-11-16. Exceptionally, comments
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>> 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.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-hokey-arch-design/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-hokey-arch-design/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>> _______________________________________________
>>> HOKEY mailing list
>>> HOKEY@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hokey
>>>
>> _______________________________________________
>> HOKEY mailing list
>> HOKEY@ietf.org
>> https://www.ietf.org/mailman/listinfo/hokey
>>
> _______________________________________________
> HOKEY mailing list
> HOKEY@ietf.org
> https://www.ietf.org/mailman/listinfo/hokey
>