Re: [HOKEY] WGLC on draft-ietf-hokey-erp-aak

[Glen Zorn <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/10/2011 10:35 AM, Qin Wu wrote:

> Hi,
> I read and support this work forward. 
> Here is my comments belows:
> 1. Abstract
> [Qin]: The abstract is too long. I suggest to change from
> "
>    The Extensible Authentication Protocol (EAP) is a generic framework
>    supporting multiple 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 prior to handover
>    upon one or more candidate attachment points (CAPs).  AAK uses the
>    AAA infrastructure for key transport.
> 
>    This document specifies the extensions necessary to enable AAK
>    support in ERP.
> "
> to
> "
>    Authenticated Anticipatory Keying (AAK) is a method by which
>    cryptographic keying material may be established prior to handover
>    upon one or more candidate attachment points (CAPs).  AAK uses the
>    AAA infrastructure for key transport.
> 
>    This document specifies the extensions necessary to enable AAK
>    support in ERP.
> "

Actually, I don't think that the Abstract is too long at all.

> Section 4 First Paragraph
> "
>    As an optimization of ERP, ERP/AAK uses key hierarchy similar to that
>   of ERP.  
> "
>  [Qin]: Suggest to change "optimization" as "extension".

Agree, & also change "uses key" to "uses a key"

> 
> Section 4 Fist paragraph:
> "
> The hierarchy relationship is illustrated in Figure 2, below.
> "
> [Qin]: suggestion to change as:
> "
> The hierarchy relationship is illustrated in Figure 2 shown below.

Why?

...

> 
> Section 7 last setence:
>    [Qin]: Remove the last sentence since we can resue the extisting AAA message.

What message did you have in mind?  I can't think of any that do what is
necessary.

...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNz3J+AAoJEG4XtfZZU7RfheYIAIFhMJ6tP0cf+WZLzMeZML2b
AO9yhaqbouCCxpCdXUGHLwrTOtyKEyXrXA62ZUHfh2LtKbR1B/K7SCp/nW3e2hEk
ewItOuyfGEgQN4KoPQhL9FakfVPQFezEKse3TdwV4x7v9/foASV8U5CW0wFXI5sj
UZColU5PtvKEGRK7/yUcxDie9kA0xwCPsrLzxdRfdnQjMBGuOmexwK4fpe9i4K7d
ZVyVs9ey7DEgujFmOJ7OnBIiTC6OnarXkWelN3cvliGtjNekc/VM55J7tqUWqcRl
6R0RvRe/ok20X8DseuWl2aLFKA8A7QvES0LzecblHSnw8auN/OGUIpFqRhJ2EvA=
=N0xC
-----END PGP SIGNATURE-----