[Ipsec] draft-ietf-ipsec-esp-ah-algorithms-02.txt

"Vishwas Manral" <Vishwas@sinett.com> Thu, 30 December 2004 06:15 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29903 for <ipsec-archive@lists.ietf.org>; Thu, 30 Dec 2004 01:15:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjtWg-0002gn-4V; Thu, 30 Dec 2004 01:11:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjtRV-0000QO-EE for ipsec@megatron.ietf.org; Thu, 30 Dec 2004 01:05:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29060 for <ipsec@ietf.org>; Thu, 30 Dec 2004 01:05:48 -0500 (EST)
Received: from 63-197-255-158.ded.pacbell.net ([63.197.255.158] helo=sinett.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cjtcc-0006mE-4W for ipsec@ietf.org; Thu, 30 Dec 2004 01:17:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Dec 2004 22:13:53 -0800
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B207EA8C@sinett-sbs.SiNett.LAN>
Thread-Topic: draft-ietf-ipsec-esp-ah-algorithms-02.txt
thread-index: AcTuNrx5A28r3JvQS4mNs3cB6B6maA==
From: Vishwas Manral <Vishwas@sinett.com>
To: ipsec@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: Donald.Eastlake@Motorola.com
Subject: [Ipsec] draft-ietf-ipsec-esp-ah-algorithms-02.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0918636134=="
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org

Hi Donald,
 
I have some minor comments: -
 
1. For ESP we state that "MUST    NULL"(must support NULL authentication). However 
http://www.ietf.org/internet-drafts/draft-ietf-ipsec-esp-v3-09.txt <http://www.ietf.org/internet-drafts/draft-ietf-ipsec-esp-v3-09.txt>  very clearly seems to state "However, this standard does not require ESP implementations to offer an encryption-only service."
 
We may want to change the MUST to SHOULD. Steve?
 
2. A more general comment, what about all the algorithm's that are specified by IETF but not in the document or a different key size, e.g. "SHOULD+    AES-CBC with 128-bit keys" what about other key sizes. I understand it is stated that: -
  "To ensure interoperability between disparate implementations it is necessary to
   specify a set of mandatory-to-implement algorithms to ensure at least one algorithm
   that all implementations will have available." however SHOULD's(I guess not mandatory) are specified.
 
Thanks,
Vishwas
_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec