[HOKEY] Comments to draft-ietf-hokey-erp-aak-04

金多伟 <strobeking@gmail.com> Thu, 11 August 2011 01:54 UTC

From: =?gb2312?B?vfC24M6w?= <strobeking@gmail.com>
To: <hokey@ietf.org>
Date: Thu, 11 Aug 2011 09:54:37 +0800
Message-ID: <000001cc57c9$a34bab30$e9e30190$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CC580C.B16EEB30"
Thread-Index: AcxXyaBDQ4Ohv68aSBWGFNz/76MFjg==
Content-Language: en-us
Subject: [HOKEY] Comments to draft-ietf-hokey-erp-aak-04
Precedence: list

Hi All,

 

I have read the draft, and found the technique content are okay, but I found
the following typos for the authors to correct.

 

1. In abstract, the first paragraph, "a generic framework supporting
multiple _types_ of authentication methods"

 

2. In Section 4, the second paragraph, it should be "if the peer has _been_
previously authenticated by means of ERP or ERP/AAK"

 

3.In Section 5.2, the explanation about TVs and TLVs(the first paragraph in
page 8), it should be “The username part of the NAI is the EMSKname used
_to_ identify the peer”

 

4. In Section 5.2, the explanation about Cryptosuite (the fourth paragraph
in page 8), it should be “key lengths and output lengths are either
indicated or (are) obvious from the cryptosuite name”

 

5. In Section 5.3, the explanation about Cryptosuite (the fifth paragraph in
page 10), it should be “key lengths and output lengths are either indicated
or (are) obvious from the cryptosuite name”

 

6. In Section 8, the eighth paragraph, it should be “the peer and the
server derive the keys independently using parameters known _by_ each
entity”

 

7 In section 8, the thirteenth paragraph, it should be “Any domain-specific
keys are further restricted _to be used_ only in the domain….”

 

--

Best regards,

 

Duowei Jin

[HOKEY] Comments to draft-ietf-hokey-erp-aak-04 金多伟
Re: [HOKEY] Comments to draft-ietf-hokey-erp-aak-… Zhen Cao