IETF Logo Mail Archive

Re: [IPsec] Please review draft-ietf-ipsecme-aes-ctr-ikev2-05.txt

Sean Shen 沈烁 <shenshuo@cnnic.cn> Mon, 08 March 2010 08:20 UTC

Return-Path: <shenshuo@cnnic.cn>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D08FB3A67D3 for <ipsec@core3.amsl.com>; Mon, 8 Mar 2010 00:20:34 -0800 (PST)
X-Quarantine-ID: <L2aXfotiQDDC>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level:
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[AWL=2.458, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2aXfotiQDDC for <ipsec@core3.amsl.com>; Mon, 8 Mar 2010 00:20:33 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 439C93A6781 for <ipsec@ietf.org>; Mon, 8 Mar 2010 00:20:30 -0800 (PST)
Received: (eyou send program); Mon, 08 Mar 2010 16:18:53 +0800
Message-ID: <468036333.20323@cnnic.cn>
Received: from unknown (HELO shen) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 08 Mar 2010 16:18:53 +0800
Message-ID: <00b001cabe97$fa18d130$cb7d2dc4@SHEN>
From: Sean Shen 沈烁 <shenshuo@cnnic.cn>
To: ipsec <ipsec@ietf.org>
References: <467681796.13887@cnnic.cn><7ccecf671003032200r3e0de9d8te2dcf3aab9dacdea@mail.gmail.com> <467703594.20935@cnnic.cn>
Date: Mon, 08 Mar 2010 16:08:36 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: Re: [IPsec] Please review draft-ietf-ipsecme-aes-ctr-ikev2-05.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2010 08:20:34 -0000


> Raj Singh writes:
>> Section 5. IANA Considerations can be reworded in-line with
>> ikev2bis. 
> 
> It would be better align it with ikev2-parameters iana registry. 
> 
>> 5. IANA Considerations
>> 
>> IANA has already registered the type and value for AES-CTR.
>> 
>> Name                 Number      Defined In
>> --------------------------------------------
>> 
>> ENCR_AES_CTR         13          (RFC3686 <http://tools.ietf.org/html/rfc3686>)
> 
> I.e. correct line to be put to the IANA registry will be:
> 
> 
> Number        Name                   ESP Reference  IKEv2 Reference
> ------------  ---------------------  -------------  ---------------
> 13            ENCR_AES_CTR           [RFC3686]      [RFC<this rfc>]
> 
> 
> I.e this document change sthe IKEv2 Reference column of the 
> Transform Type 1 - Encryption Algorithm Transform IDs iana table for
> number 13 - ENCR_AES_CTR from "-" to refer this document instead.

If we need to give clear expression of what a IANA reference should be, I believe the iana registry is the proper format as showed above (also at http://www.iana.org/assignments/ikev2-parameters). 

Sean

v2.23.0 | Report a Bug | By Email