[Ipsec] Minor comment/question on draft-ietf-ipsec-esp-v3-09.txt

Markku Savela <msa@burp.tkv.asdf.org> Wed, 16 February 2005 14:09 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 JAA11279 for <ipsec-archive@lists.ietf.org>; Wed, 16 Feb 2005 09:09:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Pko-0000vB-Sl; Wed, 16 Feb 2005 09:02:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Pht-0000PW-JW for ipsec@megatron.ietf.org; Wed, 16 Feb 2005 08:59:09 -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 IAA10433 for <ipsec@ietf.org>; Wed, 16 Feb 2005 08:59:07 -0500 (EST)
Received: from burp.tkv.asdf.org ([212.16.99.49] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Q38-0004b1-I0 for ipsec@ietf.org; Wed, 16 Feb 2005 09:21:08 -0500
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1]) by burp.tkv.asdf.org (8.13.2/8.13.2/Debian-1) with ESMTP id j1GDx5oA016621 for <ipsec@ietf.org>; Wed, 16 Feb 2005 15:59:05 +0200
Received: (from msa@localhost) by burp.tkv.asdf.org (8.13.2/8.13.2/Submit) id j1GDx5SK016618; Wed, 16 Feb 2005 15:59:05 +0200
Date: Wed, 16 Feb 2005 15:59:05 +0200
Message-Id: <200502161359.j1GDx5SK016618@burp.tkv.asdf.org>
From: Markku Savela <msa@burp.tkv.asdf.org>
To: ipsec@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [Ipsec] Minor comment/question on draft-ietf-ipsec-esp-v3-09.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>
Sender: ipsec-bounces@ietf.org
Errors-To: ipsec-bounces@ietf.org

Minor nit (or my misunderstanding of something), but in

2.3  Payload Data
   ...
   Note that the beginning of the next layer protocol header MUST be
   aligned relative to the beginning of the ESP header as follows. For
   IPv4, this alignment is a multiple of 4 bytes. For IPv6, the
   alignment is a multiple of 8 bytes.
   ...


I'm puzzled about what the "next layer protocol header" means? With
ESP, the packet really does not have any next layer header, that needs
alignment.

The paragraphah can be deleted?

[Of course, after inbound ESP processing we have the header and it
must be properly aligned, but that is a different matter.]

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