
From iesg-secretary@ietf.org  Mon Mar  5 10:09:59 2012
Return-Path: <iesg-secretary@ietf.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 12CAC21F8782; Mon,  5 Mar 2012 10:09:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 0UoaNRBJ9YyG; Mon,  5 Mar 2012 10:09:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AB721F8790; Mon,  5 Mar 2012 10:09:57 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120305180957.16484.74839.idtracker@ietfa.amsl.com>
Date: Mon, 05 Mar 2012 10:09:57 -0800
Cc: hokey chair <hokey-chairs@tools.ietf.org>, hokey mailing list <hokey@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [HOKEY] Protocol Action: 'EAP Re-authentication Protocol Extensions for	Authenticated Anticipatory Keying (ERP/AAK)' to Proposed	Standard (draft-ietf-hokey-erp-aak-10.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: Mon, 05 Mar 2012 18:09:59 -0000

The IESG has approved the following document:
- 'EAP Re-authentication Protocol Extensions for Authenticated
   Anticipatory Keying (ERP/AAK)'
  (draft-ietf-hokey-erp-aak-10.txt) as a Proposed Standard

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

The IESG contact persons are Stephen Farrell and Sean Turner.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-hokey-erp-aak/




Technical Summary

  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.

Working Group Summary

  The document is a product of the Hokey working group. The document has
  working group consensus.

Document Quality

  The document develops a series of procedure, protocol for the specific usage
  scenario identified.
  This document has gotten sufficient review from people with
  both OPS and Security background. The quality of the document is good.

Personnel

  Stephen Farrell is the responsible AD
  Tina Tsou is the document shepherd.

RFC Editor Note

1) There's a typo that ID-nits complains about on p17 so:

OLD
       (R) 0x80 [RF5296]
NEW
      (R) 0x80 [RFC5296]


2)  Last para of page 6, a typo noted by Sean

OLD 
    thus message
NEW 
    this message

IANA Note

IANA: please note that -10 adds a new registry that wasn't in -09
as a result of IESG review.



From stephen.farrell@cs.tcd.ie  Thu Mar 22 08:39:15 2012
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 E789021F85A1 for <hokey@ietfa.amsl.com>; Thu, 22 Mar 2012 08:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, 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 pUE5c8GYJJTa for <hokey@ietfa.amsl.com>; Thu, 22 Mar 2012 08:39:15 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id AB65E21F852D for <hokey@ietf.org>; Thu, 22 Mar 2012 08:39:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1EE3E153B57; Thu, 22 Mar 2012 15:39:14 +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=1332430753; bh=hkAJGUXbh6Ndpc YM89MFw2TR31wIIEE91fz6b1NWPo4=; b=bRHbuH/4ma/swUcGOm+dPpUcHJAOv9 0TE54uHN4Mgbf3Pi5S1uM0aSMfSAdg5/zHhQ+3drL+vD4QUwx1MEDiJKJxsHn6eS 8/JSsXmO0DGLqN9UUEkL2n/BQjDDglnmhVL0mt3M6aJBxKmLPd42b2adnaRIMp/1 h3bSrI1Hsaomgki0B/JCLSm+0Fr8B0mIyHOgepBT3K2xxyq1u1cGAOXziMnB3NO2 YuvbPhsYeZLwRSUCRkRg0GYiVxv9Kq7w1d3D11WO7qaH7MvV1iSvYyyvQjC85ayD 2DlL3WLbUbK8Aa+enGqufMDoBBi2gyfsSCWqN+Qf7a7XCOKh16pdPMEg==
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 Buq7AiKN7Icq; Thu, 22 Mar 2012 15:39:13 +0000 (GMT)
Received: from [10.87.48.5] (unknown [86.45.51.117]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 37FF5153B52; Thu, 22 Mar 2012 15:39:07 +0000 (GMT)
Message-ID: <4F6B479A.5090503@cs.tcd.ie>
Date: Thu, 22 Mar 2012 15:39:06 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <C0E0A32284495243BDE0AC8A066631A80C2C4386@szxeml526-mbs.china.huawei.com> <4F43D2ED.8010003@cs.tcd.ie>
In-Reply-To: <4F43D2ED.8010003@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] New one-week WGLC limited to 5926bis IPR
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, 22 Mar 2012 15:39:16 -0000

Hi,

So IETF LC is done for this and I think my comment below
and the IANA considerations were the only things that came up.

Could the authors please handle my comment below (and check
I-D nits [1] as well which has a couple of things you may
as well handle at the same time).

For the IANA considerations, IANA asked what to do about the
existing registries in 5296 and I at least didn't know. The
IESG (I asked) felt that best would be to repeat the definition
here and ask IANA to make 5296bis be the reference for those
registries. (See some text by Barry Leiba below that makes
this clear.) If the authors/WG/chairs are ok with that the
can you do it? If you want to do something else, please tell
me what, and I'll do a quick check with the IESG that that'll
not cause a bunch of discusses.

Please post a new version after Monday and if it sorts all the
above, I'll put it on the following telechat agenda.

Thanks,
S.

[1] 
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-hokey-rfc5296bis-06.txt

Barry's best bet for basically-the-same registries in bis RFCs:

Right, that's what we've done in the past.  If the original document
also created initial entries, and the definitions of those entries are
now in the bis document, in addition to changing the registry to point
to the bis document it's often useful to also list, in IANA
Considerations, what those entries are.  Something like this:
-----------------------------
RFC 7777:
IANA is asked to create the Frobozz Magic Registry, using the
"Specification Required" registration policy [BCP26].  IANA should
please register the following initial entries in that registry:

    Name       Reference                       Status
    plover       RFC 7777, section 3.2    active
    plugh        RFC 7777, section 3.5    active
    xyzzy        RFC 7777, section 3.6    active
-----------------------------
7777bis:
IANA is asked to update the Frobozz Magic Registry, which uses the
"Specification Required" registration policy [BCP26], to refer to this
RFC.  IANA should please also update the following entries in that
registry:

    Name       Reference                       Status
    plover       7777bis, section 3.2        active
    plugh        7777bis, section 3.6        active
    xyzzy        7777bis, section 3.9        active

IANA is asked to add a new entry to the Frobozz Magic Registry, as follows:

    Name       Reference                       Status
    pirate        7777bis, section 3.8        active
-----------------------------



On 02/21/2012 05:22 PM, Stephen Farrell wrote:
>
> Hi,
>
> Not about IPR as it happens, but caused by looking at that:-)
>
> I just happened to be looking at this and I've only now
> noticed that there is actually no reference for RFC5296
> in the body of the document, which I guess isn't quite
> right. (Yes, the meta-data is fine, and yes the
> abstract says it, but without a reference.)
>
> Sorry not to have spotted this before but I bet that
> it'd generate a nit-picking discuss so maybe better
> to head that off before we go there.
>
> I'd suggest adding a sentence to end of the introduction
> saying something like:
>
> This document updates RFC 5296. [RFC5296] The main
> changes are foo and bar.
>
> Or maybe something like:
>
> This document contains a set of minor updates to
> RFC 5296 [RFC5296] based on implementation and
> deployment experience.
>
> Or whatever is actually the case.
>
> And then add the (informative) reference of course!
>
> Cheers,
> S.
>
>
> On 02/18/2012 12:00 AM, Tina TSOU wrote:
>> Dear all,
>> This starts a new one-week WGLC limited to 5926bis IPR, which ends at
>> Feb 25, 2012.
>> http://datatracker.ietf.org/doc/draft-ietf-hokey-rfc5296bis/
>>
>> The existing IPR declaration is for 5296.
>> I've asked Microsoft, we've not heard back from Microsoft.
>> We'll need to get this sorted before this gets approved.
>>
>> Best Regards,
>> Glen& Tina
>>
>>
>> _______________________________________________
>> 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
>

From glenzorn@gmail.com  Fri Mar 23 00:02:22 2012
Return-Path: <glenzorn@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 664C921F84B9 for <hokey@ietfa.amsl.com>; Fri, 23 Mar 2012 00:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 RUTm1LClXukj for <hokey@ietfa.amsl.com>; Fri, 23 Mar 2012 00:02:21 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECF321F84B6 for <hokey@ietf.org>; Fri, 23 Mar 2012 00:02:21 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so1309893wgb.13 for <hokey@ietf.org>; Fri, 23 Mar 2012 00:02:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ypTJNK12Yuny1lvxS3nTkaeGQQh65c/0UWQHNZ0Yps4=; b=FUCEU936p1jQ1bfLkh+oxggaYk3j5sYQcanmBx+1/W8qBzQzS4N3xp0DkLzDc4dO4f TC4b3U6Ug9jz4IqqHcMHKZ8aBEVd6KitBkshH6uyYtjVqEqyeyfG5/MutR+taS7Ufml2 10yT/0Js7QWwRQ/ZhymMDdoWRC3B/WKVbwkNTPEdvqCXs4kM2bCeg560xqqjjcRvcOUu y3lBtvn1K9c3WKl8QuXo2SBPMPajxaUOoKjxSzrwlNM5rG/bAlVYrp6YLo6eqpIbljw3 h1hE0T1pYaAhYgd+za2GvVl9xYDSfIRaa1bf0ONJFeM0qQVWM+vwWA87Zp+arAcq8xPA pN6A==
Received: by 10.216.139.156 with SMTP id c28mr6177880wej.57.1332486140376; Fri, 23 Mar 2012 00:02:20 -0700 (PDT)
Received: from [192.168.0.14] (mar75-9-88-171-190-61.fbx.proxad.net. [88.171.190.61]) by mx.google.com with ESMTPS id l5sm11434528wia.11.2012.03.23.00.02.18 (version=SSLv3 cipher=OTHER); Fri, 23 Mar 2012 00:02:19 -0700 (PDT)
Message-ID: <4F6C1FF8.90600@gmail.com>
Date: Fri, 23 Mar 2012 08:02:16 +0100
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <C0E0A32284495243BDE0AC8A066631A80C2C4386@szxeml526-mbs.china.huawei.com> <4F43D2ED.8010003@cs.tcd.ie> <4F6B479A.5090503@cs.tcd.ie>
In-Reply-To: <4F6B479A.5090503@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] New one-week WGLC limited to 5926bis IPR
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: Fri, 23 Mar 2012 07:02:22 -0000

On 3/22/2012 4:39 PM, Stephen Farrell wrote:
> 
> Hi,
> 
> So IETF LC is done for this and I think my comment below
> and the IANA considerations were the only things that came up.
> 
> Could the authors please handle my comment below (and check
> I-D nits [1] as well which has a couple of things you may
> as well handle at the same time).

-07 (yet to be posted) has no problems w/I-D nits except for a spurious
warning about a missing references and the incorrect error about the
normative reference to RFC 2104.

> 
> For the IANA considerations, IANA asked what to do about the
> existing registries in 5296 and I at least didn't know. The
> IESG (I asked) felt that best would be to repeat the definition
> here and ask IANA to make 5296bis be the reference for those
> registries. (See some text by Barry Leiba below that makes
> this clear.) If the authors/WG/chairs are ok with that the
> can you do it? If you want to do something else, please tell
> me what, and I'll do a quick check with the IESG that that'll
> not cause a bunch of discusses.

Personally, I think it's a really bad idea for people to use RFCs as
references for protocol numbers; the IANA registry is the authoritative
source, repeating a snapshot of that source in a document that  will
never change is at best confusing.  I would much prefer just adding
something like "For the current list of assignments related to ERP, see
the IANA registry [EAP-NUMBERS]." where [EAP-NUMBERS] cites
http://www.iana.org/assignments/eap-numbers/eap-numbers.xml.

...

> On 02/21/2012 05:22 PM, Stephen Farrell wrote:
>>
>> Hi,
>>
>> Not about IPR as it happens, but caused by looking at that:-)
>>
>> I just happened to be looking at this and I've only now
>> noticed that there is actually no reference for RFC5296
>> in the body of the document, which I guess isn't quite
>> right. (Yes, the meta-data is fine, and yes the
>> abstract says it, but without a reference.)
>>
>> Sorry not to have spotted this before but I bet that
>> it'd generate a nit-picking discuss so maybe better
>> to head that off before we go there.
>>
>> I'd suggest adding a sentence to end of the introduction
>> saying something like:
>>
>> This document updates RFC 5296. [RFC5296] The main
>> changes are foo and bar.
>>
>> Or maybe something like:
>>
>> This document contains a set of minor updates to
>> RFC 5296 [RFC5296] based on implementation and
>> deployment experience.
>>
>> Or whatever is actually the case.
>>
>> And then add the (informative) reference of course!

OK, so during the IESG review of RFC 3588bis, we got nit-picking
discusses about referencing RFC 3588 because it would be obsolete soon.
 Seems like a no-win situation to me...

...
