
From stephen.farrell@cs.tcd.ie  Thu Feb  2 07:04:08 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 9BE2C21F8526 for <hokey@ietfa.amsl.com>; Thu,  2 Feb 2012 07:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 qwnBuxppsgZT for <hokey@ietfa.amsl.com>; Thu,  2 Feb 2012 07:04:07 -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 7A40721F8567 for <hokey@ietf.org>; Thu,  2 Feb 2012 07:04:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 279FD171C3A for <hokey@ietf.org>; Thu,  2 Feb 2012 15:04:03 +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=1328195042; bh=qo0/0UWIJdCYA7 Y/2gUuOtv1li/2KZDIH2Lh1ii6h7A=; b=QfFZsHTIpnr5fpNJbKg4Gw3+nQzQBk GkTLoZJLJnDjTTmNGtMIPz0nFfQUF/uaQWA98oiCpA7gan8MQ6+e4fDh8tnZyf7C X9/xyobLPQU8ehVcXCFFBU6HHibdgrBLayqba5mz70eNAToukedbVJkFmKAhmJTb CpYwAcphBy9DZlORyo4qMdECVXWga1rjEc1tLnTAdQpI5DRlmp8aGCa+wcY3mmVY wT+dl1CKEZXDrlE3Kn3KzV0lxCAi129cTwJPhS91rK0/drlbnPCNXYwf+8Bxb5jp /fxuC9b70f6wv+nnuhcuvetv1LfOBkExsurCWOIfckQkkXiEyEQgv3PA==
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 ZPutAzal5Th4 for <hokey@ietf.org>; Thu,  2 Feb 2012 15:04:02 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id B75AE171C27 for <hokey@ietf.org>; Thu,  2 Feb 2012 15:04:02 +0000 (GMT)
Message-ID: <4F2AA5E2.2040106@cs.tcd.ie>
Date: Thu, 02 Feb 2012 15:04:02 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "hokey@ietf.org" <hokey@ietf.org>
References: <4F2AA2F8.4010004@ericsson.com>
In-Reply-To: <4F2AA2F8.4010004@ericsson.com>
X-Forwarded-Message-Id: <4F2AA2F8.4010004@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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, 02 Feb 2012 15:04:08 -0000

FYI

-------- Original Message --------
Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
Date: Thu, 2 Feb 2012 15:51:36 +0100
From: Miguel A. Garcia <Miguel.A.Garcia@ericsson.com>
To: Zhen Cao <zehn.cao@gmail.com>, Hui Deng <denghui02@gmail.com>, 
sunseawq@huawei.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
CC: General Area Review Team <gen-art@ietf.org>

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-hokey-erp-aak-07
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-01-02
IETF LC End Date: 2012-02-07

Summary: This draft is on the right track but has open issues, described
in the review.

Major issues:

- None

Minor issues:

- The main problem I have with this draft is the lack of normative text
(RFC 2119 reserved words) in relevant paragraphs. If interoperability is
to be granted, an effort should be taken in adding quite a few more
normative statements.

However, having said that, the section where I find more that there
should be more normative text, is Section 3, which is an "Overview"
section. In general, an overview section should use descriptive, but not
normative text.

For example, take the last paragraph in Page 5 (that continues to Page
6). One possible change is to make normative the text and move it outside
a section whose title is "Overview".

    Upon receiving the message, the ERP/AAK server MUST first use the
    keyName indicated in the keyName-NAI to look up the rIK and MUST
    check the integrity and freshness of the message. Then the ERP/AAK
    server MUST verify the identity of the peer by checking the username
    portion of the KeyName-NAI.  If any of the checks fail, the server
    MUST send an early- authentication finish message (EAP-Finish/Re-auth
    with E-flag set) with the Result flag set to '1'.  Next, the server
    MUST authorize the CAP specified in the CAP-Identifier TLV.  In
    success case, the server MUST derive a pMSK from the pRK for each CAP
    carried in the the CAP-Identifier field using the sequence number
    associated with CAP-Identifier as an input to the key derivation.
    (see d. in the figure 1).

    Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
    via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
    2). Note that key distribution in the figure 2 is one part of step d.
    in the figure 1.

The the last paragraph in Section 3 also contains an "Optionally", which
I believe should be replaced with a capitalized "OPTIONAL"

Another instance: towards the end of Section 5.2, the text reads:

    HMAC-SHA256-128 is mandatory to implement and should be enabled in
    the default configuration.

and should probably be:

    HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
    the default configuration.

Similarly, the last paragraph in Section 5.2 reads:

    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
    discarded silently.

and should probably be:

    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
    SHOULD be discarded silently.



- Another topic, Section 9 (IANA Considerations) reads:

    Further, this document registers a Early authentication usage label
    from the "USRK Key Labels" name space with a value:

       EAP Early-Authentication Root Key@ietf.org


I am missing the sentence to name the master registry where the USRK Key
Labels subregistry is stored. This is the Extended Master Session Key
(EMSK) Parameters registry (I guess). And probably this comment is also
valid for the rest of the IANA actions: the main registry is not named,
and it is hard to find it.


/Miguel
-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From Tina.Tsou.Zouting@huawei.com  Sat Feb  4 11:23:10 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 308AE21F848A for <hokey@ietfa.amsl.com>; Sat,  4 Feb 2012 11:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.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 zVCXgl-2VNjX for <hokey@ietfa.amsl.com>; Sat,  4 Feb 2012 11:23:09 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [58.251.152.66]) by ietfa.amsl.com (Postfix) with ESMTP id D046F21F847D for <hokey@ietf.org>; Sat,  4 Feb 2012 11:23:08 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYV00BFQV6C7J@szxga03-in.huawei.com> for hokey@ietf.org; Sun, 05 Feb 2012 03:23:00 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYV00JOLV6CIE@szxga03-in.huawei.com> for hokey@ietf.org; Sun, 05 Feb 2012 03:23:00 +0800 (CST)
Received: from szxeml211-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGV18167; Sun, 05 Feb 2012 03:22:05 +0800
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 05 Feb 2012 03:21:30 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.225]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Sun, 05 Feb 2012 03:22:33 +0800
Date: Sat, 04 Feb 2012 19:21:43 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <4F2AA5E2.2040106@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-id: <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
Thread-index: AQHM4bvx0aqypIEI30SvQmCQbLOi75YtIP0a
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie>
Cc: "miguel.a.garcia@ericsson.com" <miguel.a.garcia@ericsson.com>, "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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, 04 Feb 2012 19:23:10 -0000

Good catch. Thank u, Miguel.

Sent from my iPad

On Feb 2, 2012, at 7:04 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

> 
> FYI
> 
> -------- Original Message --------
> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
> Date: Thu, 2 Feb 2012 15:51:36 +0100
> From: Miguel A. Garcia <Miguel.A.Garcia@ericsson.com>
> To: Zhen Cao <zehn.cao@gmail.com>, Hui Deng <denghui02@gmail.com>, sunseawq@huawei.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> CC: General Area Review Team <gen-art@ietf.org>
> 
> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft. For background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
> 
> Please resolve these comments along with any other comments you may receive.
> 
> Document: draft-ietf-hokey-erp-aak-07
> Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
> Review Date: 2011-01-02
> IETF LC End Date: 2012-02-07
> 
> Summary: This draft is on the right track but has open issues, described
> in the review.
> 
> Major issues:
> 
> - None
> 
> Minor issues:
> 
> - The main problem I have with this draft is the lack of normative text
> (RFC 2119 reserved words) in relevant paragraphs. If interoperability is
> to be granted, an effort should be taken in adding quite a few more
> normative statements.
> 
> However, having said that, the section where I find more that there
> should be more normative text, is Section 3, which is an "Overview"
> section. In general, an overview section should use descriptive, but not
> normative text.
> 
> For example, take the last paragraph in Page 5 (that continues to Page
> 6). One possible change is to make normative the text and move it outside
> a section whose title is "Overview".
> 
>   Upon receiving the message, the ERP/AAK server MUST first use the
>   keyName indicated in the keyName-NAI to look up the rIK and MUST
>   check the integrity and freshness of the message. Then the ERP/AAK
>   server MUST verify the identity of the peer by checking the username
>   portion of the KeyName-NAI.  If any of the checks fail, the server
>   MUST send an early- authentication finish message (EAP-Finish/Re-auth
>   with E-flag set) with the Result flag set to '1'.  Next, the server
>   MUST authorize the CAP specified in the CAP-Identifier TLV.  In
>   success case, the server MUST derive a pMSK from the pRK for each CAP
>   carried in the the CAP-Identifier field using the sequence number
>   associated with CAP-Identifier as an input to the key derivation.
>   (see d. in the figure 1).
> 
>   Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>   via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>   2). Note that key distribution in the figure 2 is one part of step d.
>   in the figure 1.
> 
> The the last paragraph in Section 3 also contains an "Optionally", which
> I believe should be replaced with a capitalized "OPTIONAL"
> 
> Another instance: towards the end of Section 5.2, the text reads:
> 
>   HMAC-SHA256-128 is mandatory to implement and should be enabled in
>   the default configuration.
> 
> and should probably be:
> 
>   HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>   the default configuration.
> 
> Similarly, the last paragraph in Section 5.2 reads:
> 
>   If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>   discarded silently.
> 
> and should probably be:
> 
>   If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>   SHOULD be discarded silently.
> 
> 
> 
> - Another topic, Section 9 (IANA Considerations) reads:
> 
>   Further, this document registers a Early authentication usage label
>   from the "USRK Key Labels" name space with a value:
> 
>      EAP Early-Authentication Root Key@ietf.org
> 
> 
> I am missing the sentence to name the master registry where the USRK Key
> Labels subregistry is stored. This is the Extended Master Session Key
> (EMSK) Parameters registry (I guess). And probably this comment is also
> valid for the rest of the IANA actions: the main registry is not named,
> and it is hard to find it.
> 
> 
> /Miguel
> -- 
> Miguel A. Garcia
> +34-91-339-3608
> Ericsson Spain
> _______________________________________________
> HOKEY mailing list
> HOKEY@ietf.org
> https://www.ietf.org/mailman/listinfo/hokey

From stephen.farrell@cs.tcd.ie  Wed Feb  8 03:41:56 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 1197E21F869C for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 03:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, 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 QdY0RJ8AAiCw for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 03:41:55 -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 1C5DF21F869A for <hokey@ietf.org>; Wed,  8 Feb 2012 03:41:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DAFD1153C0E; Wed,  8 Feb 2012 11:41:53 +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=1328701313; bh=YsOJK1uPlvV3sL xnYu38Pb8UXmalLI3SCdPSwlYZvys=; b=jCbZJb3UsADLxT8ocv2cVbrR7ZtiqE XETdvBEexkyp8X3mSVLA2fVa43ipBhz+dh68k/lZGy8S8oavYggynerjqbAorlKT cgcYdlMkewGr/nzYZMPXUGWeLvBnaVqS+bvyv6LpIJkrE1ck2WEb2+3BweIZq2D3 5vbkk/vq3PBfAQrFLqCkbp9pnFpyqFlRnXCY+Fd4MbGk/2fFaf24UaHMNMQ9IPbz s62YpoBQhW5qpTgSOCv6hgmod8toxC5DfvZ51vYZrBoEAlY7smjuxLMs9hrcW7ts SAx+FB0Z1b8WSB6GB8TByhqd2xO+Y7zw2hQYgKACXH6EnaJ4qmL7gWYg==
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 AlyUd3eyHxwO; Wed,  8 Feb 2012 11:41:53 +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 E3038171C2F; Wed,  8 Feb 2012 11:41:52 +0000 (GMT)
Message-ID: <4F325F78.5070701@cs.tcd.ie>
Date: Wed, 08 Feb 2012 11:41:44 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com>
In-Reply-To: <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "miguel.a.garcia@ericsson.com" <miguel.a.garcia@ericsson.com>, "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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: Wed, 08 Feb 2012 11:41:56 -0000

Hi,

IETF LC is ended for this.

I think the only comment I saw a gen-art review (is
that right?) but that there are changes resulting from
that so I've marked this as revised I-D needed. Please
submit a -08 that includes the changes needed. (I'm not
sure if any of those will require something different
from IANA, but if they do please also respond to IANA's
mail, cc'ing me, if their actions are changed.)

As soon as we have that I can put this on an IESG
telechat agenda,

Thanks,
Stephen.


On 02/04/2012 07:21 PM, Tina TSOU wrote:
> Good catch. Thank u, Miguel.
>
> Sent from my iPad
>
> On Feb 2, 2012, at 7:04 AM, "Stephen Farrell"<stephen.farrell@cs.tcd.ie>  wrote:
>
>>
>> FYI
>>
>> -------- Original Message --------
>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>, sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>> CC: General Area Review Team<gen-art@ietf.org>
>>
>> I have been selected as the General Area Review Team (Gen-ART)
>> reviewer for this draft. For background on Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>
>> Please resolve these comments along with any other comments you may receive.
>>
>> Document: draft-ietf-hokey-erp-aak-07
>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>> Review Date: 2011-01-02
>> IETF LC End Date: 2012-02-07
>>
>> Summary: This draft is on the right track but has open issues, described
>> in the review.
>>
>> Major issues:
>>
>> - None
>>
>> Minor issues:
>>
>> - The main problem I have with this draft is the lack of normative text
>> (RFC 2119 reserved words) in relevant paragraphs. If interoperability is
>> to be granted, an effort should be taken in adding quite a few more
>> normative statements.
>>
>> However, having said that, the section where I find more that there
>> should be more normative text, is Section 3, which is an "Overview"
>> section. In general, an overview section should use descriptive, but not
>> normative text.
>>
>> For example, take the last paragraph in Page 5 (that continues to Page
>> 6). One possible change is to make normative the text and move it outside
>> a section whose title is "Overview".
>>
>>    Upon receiving the message, the ERP/AAK server MUST first use the
>>    keyName indicated in the keyName-NAI to look up the rIK and MUST
>>    check the integrity and freshness of the message. Then the ERP/AAK
>>    server MUST verify the identity of the peer by checking the username
>>    portion of the KeyName-NAI.  If any of the checks fail, the server
>>    MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>    with E-flag set) with the Result flag set to '1'.  Next, the server
>>    MUST authorize the CAP specified in the CAP-Identifier TLV.  In
>>    success case, the server MUST derive a pMSK from the pRK for each CAP
>>    carried in the the CAP-Identifier field using the sequence number
>>    associated with CAP-Identifier as an input to the key derivation.
>>    (see d. in the figure 1).
>>
>>    Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>    via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>    2). Note that key distribution in the figure 2 is one part of step d.
>>    in the figure 1.
>>
>> The the last paragraph in Section 3 also contains an "Optionally", which
>> I believe should be replaced with a capitalized "OPTIONAL"
>>
>> Another instance: towards the end of Section 5.2, the text reads:
>>
>>    HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>    the default configuration.
>>
>> and should probably be:
>>
>>    HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>    the default configuration.
>>
>> Similarly, the last paragraph in Section 5.2 reads:
>>
>>    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>    discarded silently.
>>
>> and should probably be:
>>
>>    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>    SHOULD be discarded silently.
>>
>>
>>
>> - Another topic, Section 9 (IANA Considerations) reads:
>>
>>    Further, this document registers a Early authentication usage label
>>    from the "USRK Key Labels" name space with a value:
>>
>>       EAP Early-Authentication Root Key@ietf.org
>>
>>
>> I am missing the sentence to name the master registry where the USRK Key
>> Labels subregistry is stored. This is the Extended Master Session Key
>> (EMSK) Parameters registry (I guess). And probably this comment is also
>> valid for the rest of the IANA actions: the main registry is not named,
>> and it is hard to find it.
>>
>>
>> /Miguel
>> --
>> Miguel A. Garcia
>> +34-91-339-3608
>> Ericsson Spain
>> _______________________________________________
>> HOKEY mailing list
>> HOKEY@ietf.org
>> https://www.ietf.org/mailman/listinfo/hokey
>

From stephen.farrell@cs.tcd.ie  Wed Feb  8 03:50:05 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 70AA721F85D2 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 03:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, 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 YlQnhE6AJzr3 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 03:50:03 -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 EFA0721F85C3 for <hokey@ietf.org>; Wed,  8 Feb 2012 03:50:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 60160153C0F; Wed,  8 Feb 2012 11:50:02 +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=1328701801; bh=Est6WjCS8nb1sY xKES+m/oCSGOTlN7710pBvsN82weo=; b=JKocsY5dvtynU4Pes5DOSH5FN0ptK4 NgCbkym33pmr6YXu5vasGMae5guTbMUKDmRetdpgRzF5uTSiQ3tH0BJcY/pP9y+I sSSHBmtf7+bU7/fo7TGQSrhmWbqRlo8A7yw6GEHaIeOltC03hzRQRp185iACzHdV 8GvD9SNhNtdF34/StHH/h5X0JIAziyOWzYw4+8m+Fzcw5faYZNDxQbDuKWWIttLy +3mS2/pbLSBwSoVic9G6aleEFdbDzHgwfnrF4HtSDXWC9wwIRurmz4aUsnwB2H+M iIZLvqu8pQQpAexiCU/SPc+pZRHm5P5HJ0+4B6I1uXCNgK7pXgcS5Fag==
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 Fm7En92jp8sy; Wed,  8 Feb 2012 11:50:01 +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 6BBBE171C2F; Wed,  8 Feb 2012 11:50:01 +0000 (GMT)
Message-ID: <4F326160.5040705@cs.tcd.ie>
Date: Wed, 08 Feb 2012 11:49:52 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C1FA5E0@szxeml526-mbs.china.huawei.com> <4ECE4447.6040500@cs.tcd.ie> <C0E0A32284495243BDE0AC8A066631A80C1FB925@szxeml526-mbs.china.huawei.com> <4ECE68BF.8080708@cs.tcd.ie>
In-Reply-To: <4ECE68BF.8080708@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] PROTO write-up for draft-ietf-hokey-rfc5296bis-06
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: Wed, 08 Feb 2012 11:50:05 -0000

Hi Tina,

I guess its time for me to do the AD review
of this and then on to IETF LC. Any there any
substantive changes to be made before I do my
review?

There are a few references that need updating
but that can be done after AD review.

Thanks,
S.

On 11/24/2011 03:54 PM, Stephen Farrell wrote:
>
> Hiya,
>
> On 11/24/2011 03:46 PM, Tina TSOU wrote:
>> Stephen,
>> Agreed with this ordering.
>
> Great.
>
>> Happy Thanksgiving!
>
> Not really a holiday here, but thanks,
> S
>
>>
>> Best Regards,
>> Tina TSOU
>>
>>
>> -----Original Message-----
>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>> Sent: Thursday, November 24, 2011 5:19 AM
>> To: Tina TSOU
>> Cc: hokey@ietf.org
>> Subject: Re: PROTO write-up for draft-ietf-hokey-rfc5296bis-06
>>
>>
>> Thanks Tina,
>>
>> I guess I'll queue this one up until we get the IETF LC started
>> on aak, but if you'd prefer some other ordering let me know,
>>
>> Thanks,
>> S.
>>
>> PS: Congratulations on getting your final WG document to this
>> stage!
>>
>> On 11/24/2011 04:51 AM, Tina TSOU wrote:
>>> Hi Stephen,
>>> Here is the PROTO write-up for draft-ietf-hokey-rfc5296bis-06.
>>>
>>> (1.a) Who is the Document Shepherd for this document?
>>>
>>> Tina Tsou<Tina.Tsou.Zouting@huawei.com>
>>>
>>> Has the Document Shepherd personally reviewed this version of
>>> the document and, in particular, does he or she believe this
>>> version is ready for forwarding to the IESG for publication?
>>>
>>> Yes and yes.
>>>
>>> (1.b) Has the document had adequate review both from key WG members
>>> and from key non-WG members? Does the Document Shepherd have
>>> any concerns about the depth or breadth of the reviews that
>>> have been performed?
>>>
>>> Yes and no; as the filename indicates this is just a revision
>>> of RFC 5296, mostly clearing the existing errata, cleaning up
>>> the language a bit, etc. No major technical changes were made.
>>>
>>> (1.c) Does the Document Shepherd have concerns that the document
>>> needs more review from a particular or broader perspective,
>>> e.g., security, operational complexity, someone familiar with
>>> AAA, internationalization or XML?
>>>
>>> No.
>>>
>>> (1.d) Does the Document Shepherd have any specific concerns or
>>> issues with this document that the Responsible Area Director
>>> and/or the IESG should be aware of?
>>>
>>> No.
>>>
>>> Has an IPR disclosure related to this document
>>> been filed?
>>>
>>> No.
>>>
>>> (1.e) How solid is the WG consensus behind this document? Does it
>>> represent the strong concurrence of a few individuals, with
>>> others being silent, or does the WG as a whole understand and
>>> agree with it?
>>>
>>> Consensus is as strong as for any hokey document.
>>>
>>> (1.f) Has anyone threatened an appeal or otherwise indicated extreme
>>> discontent?
>>>
>>> No.
>>>
>>> (1.g) Has the Document Shepherd personally verified that the
>>> document satisfies all ID nits?
>>>
>>> Yes; idnits generates several spurious warnings caused by
>>> interpreting elements of a figure as references and one
>>> down-reference error (see below).
>>>
>>> Has the document met all formal review criteria it needs to,
>>> such as the MIB Doctor, media type and URI type reviews?
>>>
>>> Yes.
>>>
>>> (1.h) Has the document split its references into normative and
>>> informative?
>>>
>>> No.
>>>
>>> Are there normative references to documents that
>>> are not ready for advancement or are otherwise in an unclear
>>> state?
>>>
>>> No.
>>>
>>> Are there normative references
>>> that are downward references, as described in [RFC3967]?
>>>
>>> Yes.
>>>
>>> If so, list these downward references to support the Area
>>> Director in the Last Call procedure for them [RFC3967].
>>>
>>> Split as required. No down-references.
>>>
>>>
>>> (1.i) Has the Document Shepherd verified that the document IANA
>>> consideration section exists and is consistent with the body
>>> of the document? If the document specifies protocol
>>> extensions, are reservations requested in appropriate IANA
>>> registries? Are the IANA registries clearly identified? If
>>> the document creates a new registry, does it define the
>>> proposed initial contents of the registry and an allocation
>>> procedure for future registrations? Does it suggest a
>>> reasonable name for the new registry? See [RFC5226]. If the
>>> document describes an Expert Review process has Shepherd
>>> conferred with the Responsible Area Director so that the IESG
>>> can appoint the needed Expert during the IESG Evaluation?
>>>
>>> The IANA considerations section exists; the registry is identified and
>>> there are no other new registries.
>>>
>>> (1.j) Has the Document Shepherd verified that sections of the
>>> document that are written in a formal language, such as XML
>>> code, BNF rules, MIB definitions, etc., validate correctly in
>>> an automated checker?
>>>
>>> Not applicable.
>>>
>>> (1.k) The IESG approval announcement includes a Document
>>> Announcement Write-Up. Please provide such a Document
>>> Announcement Write-Up? Recent examples can be found in the
>>> "Action" announcements for approved documents. The approval
>>> announcement contains the following sections:
>>> Technical Summary
>>> Relevant content can frequently be found in the abstract
>>> and/or introduction of the document. If not, this may be
>>> an indication that there are deficiencies in the abstract
>>> or introduction.
>>>
>>> The Extensible Authentication Protocol (EAP) is a generic framework
>>> supporting multiple types of authentication methods. In systems
>>> where EAP is used for authentication, it is desirable to avoid
>>> repeating the entire EAP exchange with another authenticator. This
>>> document 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. The re-authentication server may be in
>>> the home network or in the local network to which the peer is
>>> connecting.
>>>
>>> This memo obsoletes RFC 5296.
>>>
>>> Working Group Summary
>>> Was there anything in WG process that is worth noting? For
>>> example, was there controversy about particular points or
>>> were there decisions where the consensus was particularly
>>> rough?
>>>
>>> The document is a product of the Hokey working group. The document has
>>> working group consensus.
>>>
>>>
>>> Document Quality
>>> Are there existing implementations of the protocol? Have a
>>> significant number of vendors indicated their plan to
>>> implement the specification? Are there any reviewers that
>>> merit special mention as having done a thorough review,
>>> e.g., one that resulted in important changes or a
>>> conclusion that the document had no substantive issues? If
>>> there was a MIB Doctor, Media Type or other expert review,
>>> what was its course (briefly)? In the case of a Media Type
>>> review, on what date was the request posted?
>>>
>>> The document simplifies the usage scenarios identified and optimizes
>>> the procedure, protocol for the specific usage scenario. This
>>> document has gotten sufficient review from people with both OPS and
>>> Security background. The quality of the document is good.
>>>
>>>
>>>
>>>
>>> Best Regards,
>>> Tina TSOU
>>> http://tinatsou.weebly.com/contact.html
>>>
>>>
>>>
>>>
>>
> _______________________________________________
> HOKEY mailing list
> HOKEY@ietf.org
> https://www.ietf.org/mailman/listinfo/hokey
>

From internet-drafts@ietf.org  Wed Feb  8 04:49:22 2012
Return-Path: <internet-drafts@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 5FDA221F86C8; Wed,  8 Feb 2012 04:49:22 -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 u8+1KLy9Xlc6; Wed,  8 Feb 2012 04:49:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC6E21F8611; Wed,  8 Feb 2012 04:49:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120208124921.29473.10359.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2012 04:49:21 -0800
Cc: hokey@ietf.org
Subject: [HOKEY] I-D Action: draft-ietf-hokey-erp-aak-08.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: Wed, 08 Feb 2012 12:49:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Handover Keying Working Group of the =
IETF.

	Title           : EAP Re-authentication Protocol Extensions for Authentica=
ted Anticipatory Keying (ERP/AAK)
	Author(s)       : Zhen Cao
                          Hui Deng
                          Qin Wu
                          Glen Zorn
	Filename        : draft-ietf-hokey-erp-aak-08.txt
	Pages           : 18
	Date            : 2012-02-08

   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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-08.txt


From bill.wu@huawei.com  Wed Feb  8 04:53:28 2012
Return-Path: <bill.wu@huawei.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 A606B21F858B for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 04:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.594
X-Spam-Level: 
X-Spam-Status: No, score=-5.594 tagged_above=-999 required=5 tests=[AWL=0.405,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_MED=-4]
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 b+jVYynNwksd for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 04:53:27 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF3221F8510 for <hokey@ietf.org>; Wed,  8 Feb 2012 04:53:27 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ200DH3RSRI1@szxga03-in.huawei.com> for hokey@ietf.org; Wed, 08 Feb 2012 20:53:16 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ200BD8RSQRX@szxga03-in.huawei.com> for hokey@ietf.org; Wed, 08 Feb 2012 20:53:15 +0800 (CST)
Received: from szxeml211-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGY54103; Wed, 08 Feb 2012 20:53:00 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 20:52:19 +0800
Received: from w53375q (10.138.41.130) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 20:52:44 +0800
Date: Wed, 08 Feb 2012 20:52:42 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Message-id: <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com> <4F325F78.5070701@cs.tcd.ie>
Cc: miguel.a.garcia@ericsson.com, hokey@ietf.org
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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: Wed, 08 Feb 2012 12:53:28 -0000

Hi, Stephen and all:
We have just done the update. Diff from previous version:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-hokey-erp-aak-08

Would you like to go ahead?

Regards!
-Qin
----- Original Message ----- 
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "Tina TSOU" <Tina.Tsou.Zouting@huawei.com>
Cc: <miguel.a.garcia@ericsson.com>; <hokey@ietf.org>
Sent: Wednesday, February 08, 2012 7:41 PM
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07


> 
> Hi,
> 
> IETF LC is ended for this.
> 
> I think the only comment I saw a gen-art review (is
> that right?) but that there are changes resulting from
> that so I've marked this as revised I-D needed. Please
> submit a -08 that includes the changes needed. (I'm not
> sure if any of those will require something different
> from IANA, but if they do please also respond to IANA's
> mail, cc'ing me, if their actions are changed.)
> 
> As soon as we have that I can put this on an IESG
> telechat agenda,
> 
> Thanks,
> Stephen.
> 
> 
> On 02/04/2012 07:21 PM, Tina TSOU wrote:
>> Good catch. Thank u, Miguel.
>>
>> Sent from my iPad
>>
>> On Feb 2, 2012, at 7:04 AM, "Stephen Farrell"<stephen.farrell@cs.tcd.ie>  wrote:
>>
>>>
>>> FYI
>>>
>>> -------- Original Message --------
>>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>, sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>>> CC: General Area Review Team<gen-art@ietf.org>
>>>
>>> I have been selected as the General Area Review Team (Gen-ART)
>>> reviewer for this draft. For background on Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>
>>> Please resolve these comments along with any other comments you may receive.
>>>
>>> Document: draft-ietf-hokey-erp-aak-07
>>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>>> Review Date: 2011-01-02
>>> IETF LC End Date: 2012-02-07
>>>
>>> Summary: This draft is on the right track but has open issues, described
>>> in the review.
>>>
>>> Major issues:
>>>
>>> - None
>>>
>>> Minor issues:
>>>
>>> - The main problem I have with this draft is the lack of normative text
>>> (RFC 2119 reserved words) in relevant paragraphs. If interoperability is
>>> to be granted, an effort should be taken in adding quite a few more
>>> normative statements.
>>>
>>> However, having said that, the section where I find more that there
>>> should be more normative text, is Section 3, which is an "Overview"
>>> section. In general, an overview section should use descriptive, but not
>>> normative text.
>>>
>>> For example, take the last paragraph in Page 5 (that continues to Page
>>> 6). One possible change is to make normative the text and move it outside
>>> a section whose title is "Overview".
>>>
>>>    Upon receiving the message, the ERP/AAK server MUST first use the
>>>    keyName indicated in the keyName-NAI to look up the rIK and MUST
>>>    check the integrity and freshness of the message. Then the ERP/AAK
>>>    server MUST verify the identity of the peer by checking the username
>>>    portion of the KeyName-NAI.  If any of the checks fail, the server
>>>    MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>>    with E-flag set) with the Result flag set to '1'.  Next, the server
>>>    MUST authorize the CAP specified in the CAP-Identifier TLV.  In
>>>    success case, the server MUST derive a pMSK from the pRK for each CAP
>>>    carried in the the CAP-Identifier field using the sequence number
>>>    associated with CAP-Identifier as an input to the key derivation.
>>>    (see d. in the figure 1).
>>>
>>>    Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>>    via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>>    2). Note that key distribution in the figure 2 is one part of step d.
>>>    in the figure 1.
>>>
>>> The the last paragraph in Section 3 also contains an "Optionally", which
>>> I believe should be replaced with a capitalized "OPTIONAL"
>>>
>>> Another instance: towards the end of Section 5.2, the text reads:
>>>
>>>    HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>>    the default configuration.
>>>
>>> and should probably be:
>>>
>>>    HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>>    the default configuration.
>>>
>>> Similarly, the last paragraph in Section 5.2 reads:
>>>
>>>    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>>    discarded silently.
>>>
>>> and should probably be:
>>>
>>>    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>>    SHOULD be discarded silently.
>>>
>>>
>>>
>>> - Another topic, Section 9 (IANA Considerations) reads:
>>>
>>>    Further, this document registers a Early authentication usage label
>>>    from the "USRK Key Labels" name space with a value:
>>>
>>>       EAP Early-Authentication Root Key@ietf.org
>>>
>>>
>>> I am missing the sentence to name the master registry where the USRK Key
>>> Labels subregistry is stored. This is the Extended Master Session Key
>>> (EMSK) Parameters registry (I guess). And probably this comment is also
>>> valid for the rest of the IANA actions: the main registry is not named,
>>> and it is hard to find it.
>>>
>>>
>>> /Miguel
>>> --
>>> Miguel A. Garcia
>>> +34-91-339-3608
>>> Ericsson Spain
>>> _______________________________________________
>>> 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 stephen.farrell@cs.tcd.ie  Wed Feb  8 05:30:19 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 0794B21F85D9 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 05:30:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, 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 Lddr9LgOOlP2 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 05:30:18 -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 D226021F8585 for <hokey@ietf.org>; Wed,  8 Feb 2012 05:30:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 98347171C91; Wed,  8 Feb 2012 13:30:16 +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=1328707816; bh=nrfFjIR2lLudLp 1WxoHIe92MNEOJfvtiiaXHzWRMD44=; b=xCdMLlFzuembAcq1XWGlmFbNbMKr01 kCk351OWktvRpfL7rZEZCYoDdJ0rpuHxxTberaWOBPuwSirjVjbPVGxv4Jdf9s9p lbXRvKk+8b770EpI1OJ0l1jLEdMqgxtlY4GTfvUPMqlEs5JgLMC1AiyzaJT2dige BHLPqJFV2R1s73HWiGaDE1m/43FnG0wrslUQzQkRoy2B/3srkg2HAqZvOI8TwH5+ uTzlFvQd/iRfUINV8H1yw0Ftvxxe7MU1BqH8l7v8t7BH3Eb6fnmeBSHzH5wXkq+3 KG6z+IPp9roTgy64fsgi/KvzJ2YcalTD8qRxwTGP4udRFOthqwAgBmcQ==
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 IMXdvba2jKf5; Wed,  8 Feb 2012 13:30:16 +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 80298171C2F; Wed,  8 Feb 2012 13:30:15 +0000 (GMT)
Message-ID: <4F3278DE.8070101@cs.tcd.ie>
Date: Wed, 08 Feb 2012 13:30:06 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com> <4F325F78.5070701@cs.tcd.ie> <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com>
In-Reply-To: <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: miguel.a.garcia@ericsson.com, hokey@ietf.org
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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: Wed, 08 Feb 2012 13:30:19 -0000

Thanks Qin,

I've put this on the Feb 16th telechat agenda.

Miguel - if you could confirm the changes look ok that'd
be good. If not, just comment on that here or on the
gen-art list and we can handle it via a DISCUSS or
COMMENT on the telechat.

Thanks,
S.

On 02/08/2012 12:52 PM, Qin Wu wrote:
> Hi, Stephen and all:
> We have just done the update. Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hokey-erp-aak-08
>
> Would you like to go ahead?
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Stephen Farrell"<stephen.farrell@cs.tcd.ie>
> To: "Tina TSOU"<Tina.Tsou.Zouting@huawei.com>
> Cc:<miguel.a.garcia@ericsson.com>;<hokey@ietf.org>
> Sent: Wednesday, February 08, 2012 7:41 PM
> Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
>
>
>>
>> Hi,
>>
>> IETF LC is ended for this.
>>
>> I think the only comment I saw a gen-art review (is
>> that right?) but that there are changes resulting from
>> that so I've marked this as revised I-D needed. Please
>> submit a -08 that includes the changes needed. (I'm not
>> sure if any of those will require something different
>> from IANA, but if they do please also respond to IANA's
>> mail, cc'ing me, if their actions are changed.)
>>
>> As soon as we have that I can put this on an IESG
>> telechat agenda,
>>
>> Thanks,
>> Stephen.
>>
>>
>> On 02/04/2012 07:21 PM, Tina TSOU wrote:
>>> Good catch. Thank u, Miguel.
>>>
>>> Sent from my iPad
>>>
>>> On Feb 2, 2012, at 7:04 AM, "Stephen Farrell"<stephen.farrell@cs.tcd.ie>   wrote:
>>>
>>>>
>>>> FYI
>>>>
>>>> -------- Original Message --------
>>>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>>>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>>>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>, sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>>>> CC: General Area Review Team<gen-art@ietf.org>
>>>>
>>>> I have been selected as the General Area Review Team (Gen-ART)
>>>> reviewer for this draft. For background on Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>
>>>> Please resolve these comments along with any other comments you may receive.
>>>>
>>>> Document: draft-ietf-hokey-erp-aak-07
>>>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>>>> Review Date: 2011-01-02
>>>> IETF LC End Date: 2012-02-07
>>>>
>>>> Summary: This draft is on the right track but has open issues, described
>>>> in the review.
>>>>
>>>> Major issues:
>>>>
>>>> - None
>>>>
>>>> Minor issues:
>>>>
>>>> - The main problem I have with this draft is the lack of normative text
>>>> (RFC 2119 reserved words) in relevant paragraphs. If interoperability is
>>>> to be granted, an effort should be taken in adding quite a few more
>>>> normative statements.
>>>>
>>>> However, having said that, the section where I find more that there
>>>> should be more normative text, is Section 3, which is an "Overview"
>>>> section. In general, an overview section should use descriptive, but not
>>>> normative text.
>>>>
>>>> For example, take the last paragraph in Page 5 (that continues to Page
>>>> 6). One possible change is to make normative the text and move it outside
>>>> a section whose title is "Overview".
>>>>
>>>>     Upon receiving the message, the ERP/AAK server MUST first use the
>>>>     keyName indicated in the keyName-NAI to look up the rIK and MUST
>>>>     check the integrity and freshness of the message. Then the ERP/AAK
>>>>     server MUST verify the identity of the peer by checking the username
>>>>     portion of the KeyName-NAI.  If any of the checks fail, the server
>>>>     MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>>>     with E-flag set) with the Result flag set to '1'.  Next, the server
>>>>     MUST authorize the CAP specified in the CAP-Identifier TLV.  In
>>>>     success case, the server MUST derive a pMSK from the pRK for each CAP
>>>>     carried in the the CAP-Identifier field using the sequence number
>>>>     associated with CAP-Identifier as an input to the key derivation.
>>>>     (see d. in the figure 1).
>>>>
>>>>     Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>>>     via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>>>     2). Note that key distribution in the figure 2 is one part of step d.
>>>>     in the figure 1.
>>>>
>>>> The the last paragraph in Section 3 also contains an "Optionally", which
>>>> I believe should be replaced with a capitalized "OPTIONAL"
>>>>
>>>> Another instance: towards the end of Section 5.2, the text reads:
>>>>
>>>>     HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>>>     the default configuration.
>>>>
>>>> and should probably be:
>>>>
>>>>     HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>>>     the default configuration.
>>>>
>>>> Similarly, the last paragraph in Section 5.2 reads:
>>>>
>>>>     If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>>>     discarded silently.
>>>>
>>>> and should probably be:
>>>>
>>>>     If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>>>     SHOULD be discarded silently.
>>>>
>>>>
>>>>
>>>> - Another topic, Section 9 (IANA Considerations) reads:
>>>>
>>>>     Further, this document registers a Early authentication usage label
>>>>     from the "USRK Key Labels" name space with a value:
>>>>
>>>>        EAP Early-Authentication Root Key@ietf.org
>>>>
>>>>
>>>> I am missing the sentence to name the master registry where the USRK Key
>>>> Labels subregistry is stored. This is the Extended Master Session Key
>>>> (EMSK) Parameters registry (I guess). And probably this comment is also
>>>> valid for the rest of the IANA actions: the main registry is not named,
>>>> and it is hard to find it.
>>>>
>>>>
>>>> /Miguel
>>>> --
>>>> Miguel A. Garcia
>>>> +34-91-339-3608
>>>> Ericsson Spain
>>>> _______________________________________________
>>>> 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 stephen.farrell@cs.tcd.ie  Wed Feb  8 08:45:57 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 28C2721F86DF; Wed,  8 Feb 2012 08:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, 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 UWVquEMrRESe; Wed,  8 Feb 2012 08:45:45 -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 782DC21F8617; Wed,  8 Feb 2012 08:45:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 3BAF1171C91; Wed,  8 Feb 2012 16:45:35 +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=1328719534; bh=Y0XiOc+1BGwLBw ZiB8o668Mh2d+oAcGhlOwsYxlASZg=; b=3p2bis5GWtmIdlDpjH6HNf+2VohCAk shEZWugiOHRyxHphc3SsXQaZi517913ADxb0x8WrEFDcacSm/altEWUprI549Dss memS21SuuuuQcG6Rl76LeCh0El1xHpnrLkxTbO5afPg6OQyPkC75tlbOLyW1fcPK qYPQnUfehR9ihrh/h+g2ivabdkM7FtaekY9WkN3e+70pxG36Z9v2cCcMT5r9pq4W TaL5/pCOfcbEsnE+2ZGqBp2wRB49GScHJOJ6It1COkW6biB/uzmqEuGgcjn2/7zG shIC8aco89YMUDsJtAiOIoX1rfY6z2+PYtc3SyJtdH0gEitYaNA1PYfA==
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 3Y5WgGqKNBZY; Wed,  8 Feb 2012 16:45:34 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5E092171C2F; Wed,  8 Feb 2012 16:45:27 +0000 (GMT)
Message-ID: <4F32A6A8.3010502@cs.tcd.ie>
Date: Wed, 08 Feb 2012 16:45:28 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com> <4F325F78.5070701@cs.tcd.ie> <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com> <4F32802B.8090007@ericsson.com>
In-Reply-To: <4F32802B.8090007@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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: Wed, 08 Feb 2012 16:45:57 -0000

Thanks Miguel,

(cc'ing gen-art to close that loop)

S.

On 02/08/2012 02:01 PM, Miguel A. Garcia wrote:
> I did a quick past to the changes that I requested, and I think they are
> successfully implemented in version -08.
>
> /Miguel
>
> On 08/02/2012 13:52, Qin Wu wrote:
>> Hi, Stephen and all:
>> We have just done the update. Diff from previous version:
>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hokey-erp-aak-08
>>
>> Would you like to go ahead?
>>
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Stephen Farrell"<stephen.farrell@cs.tcd.ie>
>> To: "Tina TSOU"<Tina.Tsou.Zouting@huawei.com>
>> Cc:<miguel.a.garcia@ericsson.com>;<hokey@ietf.org>
>> Sent: Wednesday, February 08, 2012 7:41 PM
>> Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>
>>
>>>
>>> Hi,
>>>
>>> IETF LC is ended for this.
>>>
>>> I think the only comment I saw a gen-art review (is
>>> that right?) but that there are changes resulting from
>>> that so I've marked this as revised I-D needed. Please
>>> submit a -08 that includes the changes needed. (I'm not
>>> sure if any of those will require something different
>>> from IANA, but if they do please also respond to IANA's
>>> mail, cc'ing me, if their actions are changed.)
>>>
>>> As soon as we have that I can put this on an IESG
>>> telechat agenda,
>>>
>>> Thanks,
>>> Stephen.
>>>
>>>
>>> On 02/04/2012 07:21 PM, Tina TSOU wrote:
>>>> Good catch. Thank u, Miguel.
>>>>
>>>> Sent from my iPad
>>>>
>>>> On Feb 2, 2012, at 7:04 AM, "Stephen
>>>> Farrell"<stephen.farrell@cs.tcd.ie> wrote:
>>>>
>>>>>
>>>>> FYI
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>>>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>>>>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>>>>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>,
>>>>> sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>>>>> CC: General Area Review Team<gen-art@ietf.org>
>>>>>
>>>>> I have been selected as the General Area Review Team (Gen-ART)
>>>>> reviewer for this draft. For background on Gen-ART, please see the
>>>>> FAQ at
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>>
>>>>> Please resolve these comments along with any other comments you may
>>>>> receive.
>>>>>
>>>>> Document: draft-ietf-hokey-erp-aak-07
>>>>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>>>>> Review Date: 2011-01-02
>>>>> IETF LC End Date: 2012-02-07
>>>>>
>>>>> Summary: This draft is on the right track but has open issues,
>>>>> described
>>>>> in the review.
>>>>>
>>>>> Major issues:
>>>>>
>>>>> - None
>>>>>
>>>>> Minor issues:
>>>>>
>>>>> - The main problem I have with this draft is the lack of normative
>>>>> text
>>>>> (RFC 2119 reserved words) in relevant paragraphs. If
>>>>> interoperability is
>>>>> to be granted, an effort should be taken in adding quite a few more
>>>>> normative statements.
>>>>>
>>>>> However, having said that, the section where I find more that there
>>>>> should be more normative text, is Section 3, which is an "Overview"
>>>>> section. In general, an overview section should use descriptive,
>>>>> but not
>>>>> normative text.
>>>>>
>>>>> For example, take the last paragraph in Page 5 (that continues to Page
>>>>> 6). One possible change is to make normative the text and move it
>>>>> outside
>>>>> a section whose title is "Overview".
>>>>>
>>>>> Upon receiving the message, the ERP/AAK server MUST first use the
>>>>> keyName indicated in the keyName-NAI to look up the rIK and MUST
>>>>> check the integrity and freshness of the message. Then the ERP/AAK
>>>>> server MUST verify the identity of the peer by checking the username
>>>>> portion of the KeyName-NAI. If any of the checks fail, the server
>>>>> MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>>>> with E-flag set) with the Result flag set to '1'. Next, the server
>>>>> MUST authorize the CAP specified in the CAP-Identifier TLV. In
>>>>> success case, the server MUST derive a pMSK from the pRK for each CAP
>>>>> carried in the the CAP-Identifier field using the sequence number
>>>>> associated with CAP-Identifier as an input to the key derivation.
>>>>> (see d. in the figure 1).
>>>>>
>>>>> Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>>>> via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>>>> 2). Note that key distribution in the figure 2 is one part of step d.
>>>>> in the figure 1.
>>>>>
>>>>> The the last paragraph in Section 3 also contains an "Optionally",
>>>>> which
>>>>> I believe should be replaced with a capitalized "OPTIONAL"
>>>>>
>>>>> Another instance: towards the end of Section 5.2, the text reads:
>>>>>
>>>>> HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>>>> the default configuration.
>>>>>
>>>>> and should probably be:
>>>>>
>>>>> HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>>>> the default configuration.
>>>>>
>>>>> Similarly, the last paragraph in Section 5.2 reads:
>>>>>
>>>>> If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>>>> discarded silently.
>>>>>
>>>>> and should probably be:
>>>>>
>>>>> If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>>>> SHOULD be discarded silently.
>>>>>
>>>>>
>>>>>
>>>>> - Another topic, Section 9 (IANA Considerations) reads:
>>>>>
>>>>> Further, this document registers a Early authentication usage label
>>>>> from the "USRK Key Labels" name space with a value:
>>>>>
>>>>> EAP Early-Authentication Root Key@ietf.org
>>>>>
>>>>>
>>>>> I am missing the sentence to name the master registry where the
>>>>> USRK Key
>>>>> Labels subregistry is stored. This is the Extended Master Session Key
>>>>> (EMSK) Parameters registry (I guess). And probably this comment is
>>>>> also
>>>>> valid for the rest of the IANA actions: the main registry is not
>>>>> named,
>>>>> and it is hard to find it.
>>>>>
>>>>>
>>>>> /Miguel
>>>>> --
>>>>> Miguel A. Garcia
>>>>> +34-91-339-3608
>>>>> Ericsson Spain
>>>>> _______________________________________________
>>>>> 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 stephen.farrell@cs.tcd.ie  Wed Feb  8 10:43:18 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 0CA9C21F8575 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 10:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 xMBj1eCPUeNO for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 10:43:17 -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 329C321F8562 for <hokey@ietf.org>; Wed,  8 Feb 2012 10:43:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 49252171C91 for <hokey@ietf.org>; Wed,  8 Feb 2012 18:43:16 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:subject:mime-version :user-agent:from:date:message-id:received:received: x-virus-scanned; s=cs; t=1328726595; bh=kjhLScrP9RNfCwozIhsVpc10 2elP4UOhHxUtR93Omvc=; b=w1hpgCRaoIiaCThK5VuQm0MCzeIW8Md3itB+BbVg Q7q96bMMyrUrKY/xTNtUEtmj5aRuvRSsEddERdR094OmgoML5HwEqeYS4zXv3s2F N2lyI/QEgOl+Xs0Z9XENAGhnb8YIlvamCj/Dyw32by3Zx5E+9XH5JxEv5pEx224k fpIQx5W+cuTZ5ZVEFhG6ry7joJ4W0CRxTrFZodXXTvPJX0ibTMULZ1U1YjQTN0HL mdI5aU7nbKBzeY9CBkxUluj1XvMcnT9RdAvGwY9c7be7uE3Kgnp/2FmsjKFwB70M vEIlVLVX760lq6HojDiL9tqnkTXyYwbeKjAvch1GqPsE+g==
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 HGW8hhoG60Ys for <hokey@ietf.org>; Wed,  8 Feb 2012 18:43:15 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id E7C33171C2F for <hokey@ietf.org>; Wed,  8 Feb 2012 18:43:15 +0000 (GMT)
Message-ID: <4F32C244.3020202@cs.tcd.ie>
Date: Wed, 08 Feb 2012 18:43:16 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "hokey@ietf.org" <hokey@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [HOKEY] AD review of draft-ietf-hokey-rfc5296bis
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: Wed, 08 Feb 2012 18:43:18 -0000

Hi all,

My review on this is below. All of those comments
can be handled along with any other IETF LC comments
received and none is a big deal. However there is one
thing to sort out before we go ahead.

There is an IPR declaration for 5296 but none for this
document, which is very similar.

We should get that sorted out before IETF LC one way or
another. Best is to get a new declaration from the folks
who declared about 5296.

It may be that an additional short WGLC just to check
this would be useful for the record once the chairs
find out if a new IPR declaration will be forthcoming
in the near future. (I've asked Tina as shepherd to
handle this.)

Thanks,
S.

- Some references need updating, check ID-nits.
 
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-hokey-rfc5296bis-06.txt

The next three comments are about stuff that didn't really
change since 5296, so consider them suggestions (i.e.
I won't insist on any changes being made).

- 3.2, 1st para: "The peer uses the domain name..." is that
the home or visited domain name?  Same thing in the 3rd last
para of 3.2 and various other places. Which domain name
is used when could be clearer throughout I think.

- p18, last bullet is not quite clear on when a message is
considered fresh. I think it means that any sequence number
greater than the last one used is ok, and any less is
considered a replay but I'm not 100% sure from this text, but
5.4 does seem to say that. Be good to be as clear here too.

- 8, "confidentiality of identity" - does the use of some of
the channel bindings not expose identity? If so, noting that
here would be good.

nits:

- DSRK is not expanded before 1st use in section 2.

- DS-rIK and DS-rRK are used with out expansion or
explanation. (last para before 3.1)

- 3.2, 1st para: s/out of home domain/out of the home domain/

- 5.1, 1st para: s/If ER capable.../If an ER capable.../

- 3.2 s/Figure 5shows/Figure 5 shows/


From Tina.Tsou.Zouting@huawei.com  Wed Feb  8 17:03:22 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 74CCB11E8075 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 17:03:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.457
X-Spam-Level: 
X-Spam-Status: No, score=-6.457 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vd5rZbyV7WqL for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 17:03:21 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 03FCB11E8072 for <hokey@ietf.org>; Wed,  8 Feb 2012 17:03:21 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ300E3IPL89S@szxga05-in.huawei.com> for hokey@ietf.org; Thu, 09 Feb 2012 09:03:08 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ300AMCPL7CS@szxga05-in.huawei.com> for hokey@ietf.org; Thu, 09 Feb 2012 09:03:08 +0800 (CST)
Received: from szxeml211-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGY78668; Thu, 09 Feb 2012 09:02:59 +0800
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 09 Feb 2012 09:02:17 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.225]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Thu, 09 Feb 2012 09:02:39 +0800
Date: Thu, 09 Feb 2012 01:02:38 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
In-reply-to: <4F326160.5040705@cs.tcd.ie>
X-Originating-IP: [10.193.34.156]
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C29C64A@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [HOKEY] PROTO write-up for draft-ietf-hokey-rfc5296bis-06
Thread-index: AQHM5lfWEt3oFeKmx0mMi6noRczRK5YzwAVw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <C0E0A32284495243BDE0AC8A066631A80C1FA5E0@szxeml526-mbs.china.huawei.com> <4ECE4447.6040500@cs.tcd.ie> <C0E0A32284495243BDE0AC8A066631A80C1FB925@szxeml526-mbs.china.huawei.com> <4ECE68BF.8080708@cs.tcd.ie> <4F326160.5040705@cs.tcd.ie>
Cc: "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] PROTO write-up for draft-ietf-hokey-rfc5296bis-06
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, 09 Feb 2012 01:03:22 -0000

Tina


> -----Original Message-----
> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
> Sent: Wednesday, February 08, 2012 3:50 AM
> To: Tina TSOU
> Cc: hokey@ietf.org
> Subject: Re: [HOKEY] PROTO write-up for draft-ietf-hokey-rfc5296bis-06
> 
> 
> Hi Tina,
> 
> I guess its time for me to do the AD review
> of this and then on to IETF LC. Any there any
> substantive changes to be made before I do my
> review?
I think there are no substantive changes to be made for now.
> 
> There are a few references that need updating
> but that can be done after AD review.
> 
> Thanks,
> S.
> 
> On 11/24/2011 03:54 PM, Stephen Farrell wrote:
> >
> > Hiya,
> >
> > On 11/24/2011 03:46 PM, Tina TSOU wrote:
> >> Stephen,
> >> Agreed with this ordering.
> >
> > Great.
> >
> >> Happy Thanksgiving!
> >
> > Not really a holiday here, but thanks,
> > S
> >
> >>
> >> Best Regards,
> >> Tina TSOU
> >>
> >>
> >> -----Original Message-----
> >> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
> >> Sent: Thursday, November 24, 2011 5:19 AM
> >> To: Tina TSOU
> >> Cc: hokey@ietf.org
> >> Subject: Re: PROTO write-up for draft-ietf-hokey-rfc5296bis-06
> >>
> >>
> >> Thanks Tina,
> >>
> >> I guess I'll queue this one up until we get the IETF LC started
> >> on aak, but if you'd prefer some other ordering let me know,
> >>
> >> Thanks,
> >> S.
> >>
> >> PS: Congratulations on getting your final WG document to this
> >> stage!
> >>
> >> On 11/24/2011 04:51 AM, Tina TSOU wrote:
> >>> Hi Stephen,
> >>> Here is the PROTO write-up for draft-ietf-hokey-rfc5296bis-06.
> >>>
> >>> (1.a) Who is the Document Shepherd for this document?
> >>>
> >>> Tina Tsou<Tina.Tsou.Zouting@huawei.com>
> >>>
> >>> Has the Document Shepherd personally reviewed this version of
> >>> the document and, in particular, does he or she believe this
> >>> version is ready for forwarding to the IESG for publication?
> >>>
> >>> Yes and yes.
> >>>
> >>> (1.b) Has the document had adequate review both from key WG members
> >>> and from key non-WG members? Does the Document Shepherd have
> >>> any concerns about the depth or breadth of the reviews that
> >>> have been performed?
> >>>
> >>> Yes and no; as the filename indicates this is just a revision
> >>> of RFC 5296, mostly clearing the existing errata, cleaning up
> >>> the language a bit, etc. No major technical changes were made.
> >>>
> >>> (1.c) Does the Document Shepherd have concerns that the document
> >>> needs more review from a particular or broader perspective,
> >>> e.g., security, operational complexity, someone familiar with
> >>> AAA, internationalization or XML?
> >>>
> >>> No.
> >>>
> >>> (1.d) Does the Document Shepherd have any specific concerns or
> >>> issues with this document that the Responsible Area Director
> >>> and/or the IESG should be aware of?
> >>>
> >>> No.
> >>>
> >>> Has an IPR disclosure related to this document
> >>> been filed?
> >>>
> >>> No.
> >>>
> >>> (1.e) How solid is the WG consensus behind this document? Does it
> >>> represent the strong concurrence of a few individuals, with
> >>> others being silent, or does the WG as a whole understand and
> >>> agree with it?
> >>>
> >>> Consensus is as strong as for any hokey document.
> >>>
> >>> (1.f) Has anyone threatened an appeal or otherwise indicated extreme
> >>> discontent?
> >>>
> >>> No.
> >>>
> >>> (1.g) Has the Document Shepherd personally verified that the
> >>> document satisfies all ID nits?
> >>>
> >>> Yes; idnits generates several spurious warnings caused by
> >>> interpreting elements of a figure as references and one
> >>> down-reference error (see below).
> >>>
> >>> Has the document met all formal review criteria it needs to,
> >>> such as the MIB Doctor, media type and URI type reviews?
> >>>
> >>> Yes.
> >>>
> >>> (1.h) Has the document split its references into normative and
> >>> informative?
> >>>
> >>> No.
> >>>
> >>> Are there normative references to documents that
> >>> are not ready for advancement or are otherwise in an unclear
> >>> state?
> >>>
> >>> No.
> >>>
> >>> Are there normative references
> >>> that are downward references, as described in [RFC3967]?
> >>>
> >>> Yes.
> >>>
> >>> If so, list these downward references to support the Area
> >>> Director in the Last Call procedure for them [RFC3967].
> >>>
> >>> Split as required. No down-references.
> >>>
> >>>
> >>> (1.i) Has the Document Shepherd verified that the document IANA
> >>> consideration section exists and is consistent with the body
> >>> of the document? If the document specifies protocol
> >>> extensions, are reservations requested in appropriate IANA
> >>> registries? Are the IANA registries clearly identified? If
> >>> the document creates a new registry, does it define the
> >>> proposed initial contents of the registry and an allocation
> >>> procedure for future registrations? Does it suggest a
> >>> reasonable name for the new registry? See [RFC5226]. If the
> >>> document describes an Expert Review process has Shepherd
> >>> conferred with the Responsible Area Director so that the IESG
> >>> can appoint the needed Expert during the IESG Evaluation?
> >>>
> >>> The IANA considerations section exists; the registry is identified and
> >>> there are no other new registries.
> >>>
> >>> (1.j) Has the Document Shepherd verified that sections of the
> >>> document that are written in a formal language, such as XML
> >>> code, BNF rules, MIB definitions, etc., validate correctly in
> >>> an automated checker?
> >>>
> >>> Not applicable.
> >>>
> >>> (1.k) The IESG approval announcement includes a Document
> >>> Announcement Write-Up. Please provide such a Document
> >>> Announcement Write-Up? Recent examples can be found in the
> >>> "Action" announcements for approved documents. The approval
> >>> announcement contains the following sections:
> >>> Technical Summary
> >>> Relevant content can frequently be found in the abstract
> >>> and/or introduction of the document. If not, this may be
> >>> an indication that there are deficiencies in the abstract
> >>> or introduction.
> >>>
> >>> The Extensible Authentication Protocol (EAP) is a generic framework
> >>> supporting multiple types of authentication methods. In systems
> >>> where EAP is used for authentication, it is desirable to avoid
> >>> repeating the entire EAP exchange with another authenticator. This
> >>> document 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. The re-authentication server may be in
> >>> the home network or in the local network to which the peer is
> >>> connecting.
> >>>
> >>> This memo obsoletes RFC 5296.
> >>>
> >>> Working Group Summary
> >>> Was there anything in WG process that is worth noting? For
> >>> example, was there controversy about particular points or
> >>> were there decisions where the consensus was particularly
> >>> rough?
> >>>
> >>> The document is a product of the Hokey working group. The document has
> >>> working group consensus.
> >>>
> >>>
> >>> Document Quality
> >>> Are there existing implementations of the protocol? Have a
> >>> significant number of vendors indicated their plan to
> >>> implement the specification? Are there any reviewers that
> >>> merit special mention as having done a thorough review,
> >>> e.g., one that resulted in important changes or a
> >>> conclusion that the document had no substantive issues? If
> >>> there was a MIB Doctor, Media Type or other expert review,
> >>> what was its course (briefly)? In the case of a Media Type
> >>> review, on what date was the request posted?
> >>>
> >>> The document simplifies the usage scenarios identified and optimizes
> >>> the procedure, protocol for the specific usage scenario. This
> >>> document has gotten sufficient review from people with both OPS and
> >>> Security background. The quality of the document is good.
> >>>
> >>>
> >>>
> >>>
> >>> Best Regards,
> >>> Tina TSOU
> >>> http://tinatsou.weebly.com/contact.html
> >>>
> >>>
> >>>
> >>>
> >>
> > _______________________________________________
> > HOKEY mailing list
> > HOKEY@ietf.org
> > https://www.ietf.org/mailman/listinfo/hokey
> >

From miguel.a.garcia@ericsson.com  Wed Feb  8 06:01:20 2012
Return-Path: <miguel.a.garcia@ericsson.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 48C0721F86F3 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 06:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.884
X-Spam-Level: 
X-Spam-Status: No, score=-9.884 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8]
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 t+vQbP2kCHO2 for <hokey@ietfa.amsl.com>; Wed,  8 Feb 2012 06:01:19 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id E5E2D21F86EF for <hokey@ietf.org>; Wed,  8 Feb 2012 06:01:18 -0800 (PST)
X-AuditID: c1b4fb3d-b7b26ae000000a35-2a-4f32802c55bb
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 46.DA.02613.C20823F4; Wed,  8 Feb 2012 15:01:18 +0100 (CET)
Received: from [159.107.24.212] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Wed, 8 Feb 2012 15:01:16 +0100
Message-ID: <4F32802B.8090007@ericsson.com>
Date: Wed, 8 Feb 2012 15:01:15 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com> <4F325F78.5070701@cs.tcd.ie> <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com>
In-Reply-To: <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Wed, 08 Feb 2012 20:40:49 -0800
Cc: "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
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: Wed, 08 Feb 2012 14:01:20 -0000

I did a quick past to the changes that I requested, and I think they are 
successfully implemented in version -08.

/Miguel

On 08/02/2012 13:52, Qin Wu wrote:
> Hi, Stephen and all:
> We have just done the update. Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hokey-erp-aak-08
>
> Would you like to go ahead?
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "Stephen Farrell"<stephen.farrell@cs.tcd.ie>
> To: "Tina TSOU"<Tina.Tsou.Zouting@huawei.com>
> Cc:<miguel.a.garcia@ericsson.com>;<hokey@ietf.org>
> Sent: Wednesday, February 08, 2012 7:41 PM
> Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
>
>
>>
>> Hi,
>>
>> IETF LC is ended for this.
>>
>> I think the only comment I saw a gen-art review (is
>> that right?) but that there are changes resulting from
>> that so I've marked this as revised I-D needed. Please
>> submit a -08 that includes the changes needed. (I'm not
>> sure if any of those will require something different
>> from IANA, but if they do please also respond to IANA's
>> mail, cc'ing me, if their actions are changed.)
>>
>> As soon as we have that I can put this on an IESG
>> telechat agenda,
>>
>> Thanks,
>> Stephen.
>>
>>
>> On 02/04/2012 07:21 PM, Tina TSOU wrote:
>>> Good catch. Thank u, Miguel.
>>>
>>> Sent from my iPad
>>>
>>> On Feb 2, 2012, at 7:04 AM, "Stephen Farrell"<stephen.farrell@cs.tcd.ie>   wrote:
>>>
>>>>
>>>> FYI
>>>>
>>>> -------- Original Message --------
>>>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>>>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>>>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>, sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>>>> CC: General Area Review Team<gen-art@ietf.org>
>>>>
>>>> I have been selected as the General Area Review Team (Gen-ART)
>>>> reviewer for this draft. For background on Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>
>>>> Please resolve these comments along with any other comments you may receive.
>>>>
>>>> Document: draft-ietf-hokey-erp-aak-07
>>>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>>>> Review Date: 2011-01-02
>>>> IETF LC End Date: 2012-02-07
>>>>
>>>> Summary: This draft is on the right track but has open issues, described
>>>> in the review.
>>>>
>>>> Major issues:
>>>>
>>>> - None
>>>>
>>>> Minor issues:
>>>>
>>>> - The main problem I have with this draft is the lack of normative text
>>>> (RFC 2119 reserved words) in relevant paragraphs. If interoperability is
>>>> to be granted, an effort should be taken in adding quite a few more
>>>> normative statements.
>>>>
>>>> However, having said that, the section where I find more that there
>>>> should be more normative text, is Section 3, which is an "Overview"
>>>> section. In general, an overview section should use descriptive, but not
>>>> normative text.
>>>>
>>>> For example, take the last paragraph in Page 5 (that continues to Page
>>>> 6). One possible change is to make normative the text and move it outside
>>>> a section whose title is "Overview".
>>>>
>>>>     Upon receiving the message, the ERP/AAK server MUST first use the
>>>>     keyName indicated in the keyName-NAI to look up the rIK and MUST
>>>>     check the integrity and freshness of the message. Then the ERP/AAK
>>>>     server MUST verify the identity of the peer by checking the username
>>>>     portion of the KeyName-NAI.  If any of the checks fail, the server
>>>>     MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>>>     with E-flag set) with the Result flag set to '1'.  Next, the server
>>>>     MUST authorize the CAP specified in the CAP-Identifier TLV.  In
>>>>     success case, the server MUST derive a pMSK from the pRK for each CAP
>>>>     carried in the the CAP-Identifier field using the sequence number
>>>>     associated with CAP-Identifier as an input to the key derivation.
>>>>     (see d. in the figure 1).
>>>>
>>>>     Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>>>     via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>>>     2). Note that key distribution in the figure 2 is one part of step d.
>>>>     in the figure 1.
>>>>
>>>> The the last paragraph in Section 3 also contains an "Optionally", which
>>>> I believe should be replaced with a capitalized "OPTIONAL"
>>>>
>>>> Another instance: towards the end of Section 5.2, the text reads:
>>>>
>>>>     HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>>>     the default configuration.
>>>>
>>>> and should probably be:
>>>>
>>>>     HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>>>     the default configuration.
>>>>
>>>> Similarly, the last paragraph in Section 5.2 reads:
>>>>
>>>>     If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>>>     discarded silently.
>>>>
>>>> and should probably be:
>>>>
>>>>     If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>>>     SHOULD be discarded silently.
>>>>
>>>>
>>>>
>>>> - Another topic, Section 9 (IANA Considerations) reads:
>>>>
>>>>     Further, this document registers a Early authentication usage label
>>>>     from the "USRK Key Labels" name space with a value:
>>>>
>>>>        EAP Early-Authentication Root Key@ietf.org
>>>>
>>>>
>>>> I am missing the sentence to name the master registry where the USRK Key
>>>> Labels subregistry is stored. This is the Extended Master Session Key
>>>> (EMSK) Parameters registry (I guess). And probably this comment is also
>>>> valid for the rest of the IANA actions: the main registry is not named,
>>>> and it is hard to find it.
>>>>
>>>>
>>>> /Miguel
>>>> --
>>>> Miguel A. Garcia
>>>> +34-91-339-3608
>>>> Ericsson Spain
>>>> _______________________________________________
>>>> 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

-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From glenzorn@gmail.com  Thu Feb  9 01:46:14 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 1563221F86CE for <hokey@ietfa.amsl.com>; Thu,  9 Feb 2012 01:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.305
X-Spam-Level: 
X-Spam-Status: No, score=-1.305 tagged_above=-999 required=5 tests=[AWL=-2.566, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MANGLED_LIST=2.3, RCVD_IN_BL_SPAMCOP_NET=1.96, 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 H8Z9a2bIASRM for <hokey@ietfa.amsl.com>; Thu,  9 Feb 2012 01:46:13 -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 35A3F21F86CA for <hokey@ietf.org>; Thu,  9 Feb 2012 01:46:13 -0800 (PST)
Received: by iagf6 with SMTP id f6so2714721iag.31 for <hokey@ietf.org>; Thu, 09 Feb 2012 01:46:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=0XYCx+QEHjNhJgCCwck/RZsjIvCChNtK8b9Uiioa7M8=; b=nXUaNDhWrBMseLl7jY7cOHiduJqHLN8fgqTET6ttdkkXd4qoziw7o3JzAtMz3Aqwrx yYEENJnpr7luLDjDKQZeLUrWFgPXyr3K3OuU7miawri7BsxBOvSAbs1T9zLVO5TMNufv kbtXsefOSt3c0rsvd4nKFDaf256BQPYRdA70Q=
Received: by 10.50.194.170 with SMTP id hx10mr28891136igc.6.1328780772908; Thu, 09 Feb 2012 01:46:12 -0800 (PST)
Received: from [192.168.1.98] (ppp-124-120-55-66.revip2.asianet.co.th. [124.120.55.66]) by mx.google.com with ESMTPS id gw1sm4704474igb.0.2012.02.09.01.46.09 (version=SSLv3 cipher=OTHER); Thu, 09 Feb 2012 01:46:11 -0800 (PST)
Message-ID: <4F3395DD.4070300@gmail.com>
Date: Thu, 09 Feb 2012 16:46:05 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <4F32C244.3020202@cs.tcd.ie>
In-Reply-To: <4F32C244.3020202@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] AD review of draft-ietf-hokey-rfc5296bis
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, 09 Feb 2012 09:46:14 -0000

On 2/9/2012 1:43 AM, Stephen Farrell wrote:
> 
> Hi all,
> 
> My review on this is below. All of those comments
> can be handled along with any other IETF LC comments
> received and none is a big deal. However there is one
> thing to sort out before we go ahead.
> 
> There is an IPR declaration for 5296 but none for this
> document, which is very similar.
> 
> We should get that sorted out before IETF LC one way or
> another. Best is to get a new declaration from the folks
> who declared about 5296.
> 
> It may be that an additional short WGLC just to check
> this would be useful for the record once the chairs
> find out if a new IPR declaration will be forthcoming
> in the near future. (I've asked Tina as shepherd to
> handle this.)
> 
> Thanks,
> S.
> 
> - Some references need updating, check ID-nits.

OK.

> 
> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-hokey-rfc5296bis-06.txt
> 
> 
> The next three comments are about stuff that didn't really
> change since 5296, so consider them suggestions (i.e.
> I won't insist on any changes being made).
> 
> - 3.2, 1st para: "The peer uses the domain name..." is that
> the home or visited domain name?  Same thing in the 3rd last
> para of 3.2 and various other places. Which domain name
> is used when could be clearer throughout I think.

Just looking at 3.2, it really seems that the domain name in question is
quite clear from the context(and the fact that the name is used in the
computation of a DSRK, which only used in a roaming situation).

> 
> - p18, last bullet is not quite clear on when a message is
> considered fresh. I think it means that any sequence number
> greater than the last one used is ok, and any less is
> considered a replay but I'm not 100% sure from this text, but
> 5.4 does seem to say that. Be good to be as clear here too.

Sorry, but again I'm just not getting it :(.  The start of the bullet in
question reads:

      Upon receipt of an EAP-Initiate/Re-auth message, the home ER
      server verifies whether the message is fresh or is a replay by
      evaluating whether the received sequence number is equal to or
      greater than the expected sequence number for that rIK.

Whats not clear?

> 
> - 8, "confidentiality of identity" - does the use of some of
> the channel bindings not expose identity? If so, noting that
> here would be good.

Excellent point!  How's this?

      Confidentiality of identity

         Deployments where privacy is a concern may find the use of
         rIKname-NAI to route ERP messages serves their privacy
         requirements.  Note that it is plausible to associate multiple
         runs of ERP messages since the rIKname is not changed as part
         of the ERP protocol.  There was no consensus for that
         requirement at the time of development of this specification.
         If the rIKname is not used and the Peer-ID is used instead, the
         ERP exchange will reveal the Peer-ID over the wire.  The use of
         channel bindings may compromise identity confidentiality, as
         well, for example, if the Calling-Station-ID AVP is used and
         contains a value that can be linked to a user (e.g., a
         telephone number).

> 
> nits:
> 
> - DSRK is not expanded before 1st use in section 2.

True; neither is 'EMSK'.  That is because the acronyms are defined in
RFC 5295 and RFC 3748, respectively, which are normative references
cited before the first usage of either term.

> 
> - DS-rIK and DS-rRK are used with out expansion or
> explanation. (last para before 3.1)

OK.

> 
> - 3.2, 1st para: s/out of home domain/out of the home domain/

OK.

> 
> - 5.1, 1st para: s/If ER capable.../If an ER capable.../

OK, probably needs a hyphen, too.

> 
> - 3.2 s/Figure 5shows/Figure 5 shows/

OK.

> 
> _______________________________________________
> HOKEY mailing list
> HOKEY@ietf.org
> https://www.ietf.org/mailman/listinfo/hokey


From stephen.farrell@cs.tcd.ie  Thu Feb  9 02:01: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 5F90121F86D0 for <hokey@ietfa.amsl.com>; Thu,  9 Feb 2012 02:01:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.149
X-Spam-Level: 
X-Spam-Status: No, score=-101.149 tagged_above=-999 required=5 tests=[AWL=-1.450, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, MANGLED_LIST=2.3, 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 9dG2SFce+h2L for <hokey@ietfa.amsl.com>; Thu,  9 Feb 2012 02:01:14 -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 5814021F86C4 for <hokey@ietf.org>; Thu,  9 Feb 2012 02:01:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BD7B9171D0B; Thu,  9 Feb 2012 10:01:13 +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=1328781673; bh=pNiNmKm+4EgqpQ DxIRqHHJzgikZ20XpBc9GuJ9zlCek=; b=WAXzxECOAH/wIB/UiY72EYPb3isF3+ PrtZ17ofPP0f3usdQaGl/jgfYvz0rq5DHRNkpg9xWaEfJHTWaSBcQ2lbwz9mUKXE 4swB3Dqf8I1GTKqcoV6SQ6Js+l7U//yVPQWfV3hw60gmZltnIQqAroVAcet4noig pDScnegs3lkCLhi9xC0kA94Fdk8RAyU/qBj30zF6Wo4E3TJEMGIUVoasIeDJHIE0 Z/uYZ5s//Er/aGwyBFDh/D2cJ+cc7duS+kmrpJ4ue6VSGVhzFnBQnXjN348O158/ fr00BYg1t5ANeifwEOJzjzZwmstnoPI/T3M/pWB2j2ZHRu07h8AcYYzQ==
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 N+oyJvJPiNFU; Thu,  9 Feb 2012 10:01:13 +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 26463171C71; Thu,  9 Feb 2012 10:01:13 +0000 (GMT)
Message-ID: <4F33995F.10106@cs.tcd.ie>
Date: Thu, 09 Feb 2012 10:01:03 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Glen Zorn <glenzorn@gmail.com>
References: <4F32C244.3020202@cs.tcd.ie> <4F3395DD.4070300@gmail.com>
In-Reply-To: <4F3395DD.4070300@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "hokey@ietf.org" <hokey@ietf.org>
Subject: Re: [HOKEY] AD review of draft-ietf-hokey-rfc5296bis
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, 09 Feb 2012 10:01:15 -0000

Hi Glen,

On 02/09/2012 09:46 AM, Glen Zorn wrote:
> On 2/9/2012 1:43 AM, Stephen Farrell wrote:
>>
>> Hi all,
>>
>> My review on this is below. All of those comments
>> can be handled along with any other IETF LC comments
>> received and none is a big deal. However there is one
>> thing to sort out before we go ahead.
>>
>> There is an IPR declaration for 5296 but none for this
>> document, which is very similar.
>>
>> We should get that sorted out before IETF LC one way or
>> another. Best is to get a new declaration from the folks
>> who declared about 5296.
>>
>> It may be that an additional short WGLC just to check
>> this would be useful for the record once the chairs
>> find out if a new IPR declaration will be forthcoming
>> in the near future. (I've asked Tina as shepherd to
>> handle this.)
>>
>> Thanks,
>> S.
>>
>> - Some references need updating, check ID-nits.
>
> OK.
>
>>
>> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-hokey-rfc5296bis-06.txt
>>
>>
>> The next three comments are about stuff that didn't really
>> change since 5296, so consider them suggestions (i.e.
>> I won't insist on any changes being made).
>>
>> - 3.2, 1st para: "The peer uses the domain name..." is that
>> the home or visited domain name?  Same thing in the 3rd last
>> para of 3.2 and various other places. Which domain name
>> is used when could be clearer throughout I think.
>
> Just looking at 3.2, it really seems that the domain name in question is
> quite clear from the context(and the fact that the name is used in the
> computation of a DSRK, which only used in a roaming situation).

If you say so, I believe you. Maybe I needed to read it again
(or better:-) but I found it a bit confusing. I guess if I were
paying enough attention to write code it might be fine. I could
also buy an argument that specifying home/visited appropriately
every time you say "domain name" might end up worse as well.

>> - p18, last bullet is not quite clear on when a message is
>> considered fresh. I think it means that any sequence number
>> greater than the last one used is ok, and any less is
>> considered a replay but I'm not 100% sure from this text, but
>> 5.4 does seem to say that. Be good to be as clear here too.
>
> Sorry, but again I'm just not getting it :(.  The start of the bullet in
> question reads:
>
>        Upon receipt of an EAP-Initiate/Re-auth message, the home ER
>        server verifies whether the message is fresh or is a replay by
>        evaluating whether the received sequence number is equal to or
>        greater than the expected sequence number for that rIK.
>
> Whats not clear?

On p18, the expected sequence number is not (yet) explained.
It is later though, in 5.4, so this is just me being v. picky.

>> - 8, "confidentiality of identity" - does the use of some of
>> the channel bindings not expose identity? If so, noting that
>> here would be good.
>
> Excellent point!  How's this?
>
>        Confidentiality of identity
>
>           Deployments where privacy is a concern may find the use of
>           rIKname-NAI to route ERP messages serves their privacy
>           requirements.  Note that it is plausible to associate multiple
>           runs of ERP messages since the rIKname is not changed as part
>           of the ERP protocol.  There was no consensus for that
>           requirement at the time of development of this specification.
>           If the rIKname is not used and the Peer-ID is used instead, the
>           ERP exchange will reveal the Peer-ID over the wire.  The use of
>           channel bindings may compromise identity confidentiality, as
>           well, for example, if the Calling-Station-ID AVP is used and
>           contains a value that can be linked to a user (e.g., a
>           telephone number).

Lovely.

>> nits:
>>
>> - DSRK is not expanded before 1st use in section 2.
>
> True; neither is 'EMSK'.  That is because the acronyms are defined in
> RFC 5295 and RFC 3748, respectively, which are normative references
> cited before the first usage of either term.

Fair enough.

Cheers,
S.

>> - DS-rIK and DS-rRK are used with out expansion or
>> explanation. (last para before 3.1)
>
> OK.
>
>>
>> - 3.2, 1st para: s/out of home domain/out of the home domain/
>
> OK.
>
>>
>> - 5.1, 1st para: s/If ER capable.../If an ER capable.../
>
> OK, probably needs a hyphen, too.
>
>>
>> - 3.2 s/Figure 5shows/Figure 5 shows/
>
> OK.
>
>>
>> _______________________________________________
>> HOKEY mailing list
>> HOKEY@ietf.org
>> https://www.ietf.org/mailman/listinfo/hokey
>
>

From internet-drafts@ietf.org  Sun Feb 12 03:01:28 2012
Return-Path: <internet-drafts@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 2980D21F861D; Sun, 12 Feb 2012 03:01:28 -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 KFMt--oUF+Ei; Sun, 12 Feb 2012 03:01:27 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67BF21F85B9; Sun, 12 Feb 2012 03:01:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120212110108.11084.10493.idtracker@ietfa.amsl.com>
Date: Sun, 12 Feb 2012 03:01:08 -0800
Cc: hokey@ietf.org
Subject: [HOKEY] I-D Action: draft-ietf-hokey-erp-aak-09.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: Sun, 12 Feb 2012 11:01:28 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Handover Keying Working Group of the =
IETF.

	Title           : EAP Re-authentication Protocol Extensions for Authentica=
ted Anticipatory Keying (ERP/AAK)
	Author(s)       : Zhen Cao
                          Hui Deng
                          Qin Wu
                          Glen Zorn
	Filename        : draft-ietf-hokey-erp-aak-09.txt
	Pages           : 19
	Date            : 2012-02-12

   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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-09.txt


From internet-drafts@ietf.org  Fri Feb 17 02:47:32 2012
Return-Path: <internet-drafts@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 9349421F8841; Fri, 17 Feb 2012 02:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 78P+eetmfjFF; Fri, 17 Feb 2012 02:47:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00A1821F87AB; Fri, 17 Feb 2012 02:47:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p2
Message-ID: <20120217104731.16425.32788.idtracker@ietfa.amsl.com>
Date: Fri, 17 Feb 2012 02:47:31 -0800
Cc: hokey@ietf.org
Subject: [HOKEY] I-D Action: 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: Fri, 17 Feb 2012 10:47:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Handover Keying Working Group of the =
IETF.

	Title           : EAP Re-authentication Protocol Extensions for Authentica=
ted Anticipatory Keying (ERP/AAK)
	Author(s)       : Zhen Cao
                          Hui Deng
                          Qin Wu
                          Glen Zorn
	Filename        : draft-ietf-hokey-erp-aak-10.txt
	Pages           : 20
	Date            : 2012-02-17

   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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-hokey-erp-aak-10.txt


From Tina.Tsou.Zouting@huawei.com  Fri Feb 17 16:00:40 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 4DFFB21F8650 for <hokey@ietfa.amsl.com>; Fri, 17 Feb 2012 16:00:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.42
X-Spam-Level: 
X-Spam-Status: No, score=-0.42 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.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 5FGynC+ptq+W for <hokey@ietfa.amsl.com>; Fri, 17 Feb 2012 16:00:39 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [58.251.152.66]) by ietfa.amsl.com (Postfix) with ESMTP id A65A621F864E for <hokey@ietf.org>; Fri, 17 Feb 2012 16:00:39 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZK00AG3AOQ6O@szxga03-in.huawei.com> for hokey@ietf.org; Sat, 18 Feb 2012 08:00:26 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZK00EO4AOQEF@szxga03-in.huawei.com> for hokey@ietf.org; Sat, 18 Feb 2012 08:00:26 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AHE79626; Sat, 18 Feb 2012 08:00:25 +0800
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 18 Feb 2012 08:00:11 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.64]) by szxeml416-hub.china.huawei.com ([10.82.67.155]) with mapi id 14.01.0323.003; Sat, 18 Feb 2012 08:00:19 +0800
Date: Sat, 18 Feb 2012 00:00:18 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Originating-IP: [10.200.65.155]
To: "hokey@ietf.org" <hokey@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C2C4386@szxeml526-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: New one-week WGLC limited to 5926bis IPR
Thread-index: Aczt0Edtg6lwZFtJR7eTn/C4pstAZw==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [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: Sat, 18 Feb 2012 00:00:40 -0000

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



From stephen.farrell@cs.tcd.ie  Tue Feb 21 09:23:07 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 2CCEF21F881D for <hokey@ietfa.amsl.com>; Tue, 21 Feb 2012 09:23:06 -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=[AWL=0.000, 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 zGs4Chu71F+C for <hokey@ietfa.amsl.com>; Tue, 21 Feb 2012 09:22:59 -0800 (PST)
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 3693421F871D for <hokey@ietf.org>; Tue, 21 Feb 2012 09:22:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id A204F171CFD; Tue, 21 Feb 2012 17:22:58 +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=1329844978; bh=f47OV8pSS9ChqI 1d8mF80gi1rQ0+5JcTNQktbWW17OA=; b=XynzuwdJt5wmLkF2Fm1G8bc5+cb4Fs 3iOq/MS5gpSeQrMfPVMKSiG2biX8q4q4x5e1YqEzDlLXcwykr4qCEWO1kVJLRsLE 2yxIYLjXhnol/w0Y7n5wwty4zZlJBlHjVRb2l9vgIwn3kQQBZLC3KJ68ARzkO0Qp k6SKY5Df9k4wADF9SiMyY/Vk1tWdMBd3Wgbl9LxN7QA+qUlXDJmCXjnbQ17PnMIs B0m9dIipKZegAFkQOXTYyd4UH0x1kBKourhq2zLWuxkLl733KTi4XbgGlNGjW7TH OFRfRtAAfi6BQo2vMD6N2wOkTDq+f0tEfirY54gZu43+ZAcV89wKA/Wg==
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 eQNjt6ldt6R5; Tue, 21 Feb 2012 17:22:58 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C95BE171C28; Tue, 21 Feb 2012 17:22:52 +0000 (GMT)
Message-ID: <4F43D2ED.8010003@cs.tcd.ie>
Date: Tue, 21 Feb 2012 17:22:53 +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: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C2C4386@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C2C4386@szxeml526-mbs.china.huawei.com>
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: Tue, 21 Feb 2012 17:23:07 -0000

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
>

From ietf-ipr@ietf.org  Mon Feb 27 14:47:18 2012
Return-Path: <ietf-ipr@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 651F621E803D; Mon, 27 Feb 2012 14:47:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.392
X-Spam-Level: 
X-Spam-Status: No, score=-102.392 tagged_above=-999 required=5 tests=[AWL=0.207, 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 d3Nv-nJ61iQy; Mon, 27 Feb 2012 14:47:17 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2CCB21E801E; Mon, 27 Feb 2012 14:47:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: sunseawq@huawei.com, glenzorn@gmail.com, caozhen@chinamobile.com, young@h3c.com, hebaohong@catr.cn
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120227224717.7717.44017.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2012 14:47:17 -0800
Cc: hokey@ietf.org, glenzorn@gmail.com, turners@ieca.com, ipr-announce@ietf.org, tena@huawei.com
Subject: [HOKEY] IPR Disclosure: Stephen Farrell's Statement about IPR related to	draft-ietf-hokey-rfc5296bis-06 belonging to Microsoft
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, 27 Feb 2012 22:47:18 -0000

Dear Wenson Wu, Glen Zorn, Zhen Cao, Yang Shi, Baohong He:

 An IPR disclosure that pertains to your Internet-Draft entitled "EAP Exten=
sions
for EAP Re-authentication Protocol (ERP)" (draft-ietf-hokey-rfc5296bis) was
submitted to the IETF Secretariat on 2012-02-27 and has been posted on the =
"IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1694/). The title of the IPR disclosure is
"Stephen Farrell's Statement about IPR related to draft-ietf-hokey-rfc5296b=
is-06
belonging to Microsoft."");

The IETF Secretariat


From iesg-secretary@ietf.org  Mon Feb 27 14:58:08 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 B6A2C21E8036; Mon, 27 Feb 2012 14:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 xezf7+BZo7d3; Mon, 27 Feb 2012 14:58:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 376DC21E8014; Mon, 27 Feb 2012 14:58:08 -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: <20120227225808.10519.65529.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2012 14:58:08 -0800
Cc: hokey@ietf.org
Subject: [HOKEY] Last Call: <draft-ietf-hokey-rfc5296bis-06.txt> (EAP Extensions for	EAP Re-authentication Protocol (ERP)) to Proposed Standard
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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, 27 Feb 2012 22:58:08 -0000

The IESG has received a request from the Handover Keying WG (hokey) to
consider the following document:
- 'EAP Extensions for EAP Re-authentication Protocol (ERP)'
  <draft-ietf-hokey-rfc5296bis-06.txt> as a Proposed Standard

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 2012-03-12. 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 Extensible Authentication Protocol (EAP) is a generic framework
   supporting multiple types of authentication methods.  In systems
   where EAP is used for authentication, it is desirable to avoid
   repeating the entire EAP exchange with another authenticator.  This
   document 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.  The re-authentication server may be in
   the home network or in the local network to which the peer is
   connecting.

   This memo obsoletes RFC 5296.



The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-hokey-rfc5296bis/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-hokey-rfc5296bis/ballot/

This draft will be updated to actually include a reference to
RFC 5296 (its sort of, but not quite, there now) and fix a 
couple of outdated references.

The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1694/



