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

Stephen Kent <kent@bbn.com> Thu, 30 December 2004 15:04 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 KAA18483 for <ipsec-archive@lists.ietf.org>; Thu, 30 Dec 2004 10:04:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck1k7-00047V-EA; Thu, 30 Dec 2004 09:57:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck1hR-0002zR-AE for ipsec@megatron.ietf.org; Thu, 30 Dec 2004 09:54: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 JAA17687 for <ipsec@ietf.org>; Thu, 30 Dec 2004 09:54:47 -0500 (EST)
Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck1sl-0001xN-BR for ipsec@ietf.org; Thu, 30 Dec 2004 10:06:32 -0500
Received: from [128.89.89.75] (dhcp89-089-075.bbn.com [128.89.89.75]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id iBUEs6jj022286; Thu, 30 Dec 2004 09:54:10 -0500 (EST)
Mime-Version: 1.0
Message-Id: <p06200740bdf9c6088e00@[128.89.89.75]>
In-Reply-To: <BB6D74C75CC76A419B6D6FA7C38317B207EA8C@sinett-sbs.SiNett.LAN>
References: <BB6D74C75CC76A419B6D6FA7C38317B207EA8C@sinett-sbs.SiNett.LAN>
Date: Thu, 30 Dec 2004 09:50:55 -0500
To: Vishwas Manral <Vishwas@sinett.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: [Ipsec] draft-ietf-ipsec-esp-ah-algorithms-02.txt
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: ipsec@ietf.org, Donald.Eastlake@Motorola.com
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="===============0053636849=="
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org

At 10:13 PM -0800 12/29/04, Vishwas Manral wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>	boundary="----_=_NextPart_001_01C4EE36.BC7E3950"
>
>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?

Good point. since we changed the requirements for encryption-only 
support in this round of document revisions, I think a SHOULD here is 
correct.

Steve
_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec