Re: [Ipsec] Minor comment/question on draft-ietf-ipsec-esp-v3-09.txt
Stephen Kent <kent@bbn.com> Wed, 16 February 2005 21:59 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 QAA01519 for <ipsec-archive@lists.ietf.org>; Wed, 16 Feb 2005 16:59:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1XAB-0003zN-Ji; Wed, 16 Feb 2005 16:56:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1X2Q-0000Ur-W8 for ipsec@megatron.ietf.org; Wed, 16 Feb 2005 16:48:51 -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 QAA00517 for <ipsec@ietf.org>; Wed, 16 Feb 2005 16:48:48 -0500 (EST)
Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1XNk-0003ug-G1 for ipsec@ietf.org; Wed, 16 Feb 2005 17:10:53 -0500
Received: from [10.1.190.35] (ramblo.bbn.com [128.33.0.51]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id j1GLlckP027707; Wed, 16 Feb 2005 16:47:50 -0500 (EST)
Mime-Version: 1.0
Message-Id: <p06210203be392fa38c95@[10.1.190.35]>
In-Reply-To: <200502161359.j1GDx5SK016618@burp.tkv.asdf.org>
References: <200502161359.j1GDx5SK016618@burp.tkv.asdf.org>
Date: Wed, 16 Feb 2005 12:22:18 -0500
To: Markku Savela <msa@burp.tkv.asdf.org>
From: Stephen Kent <kent@bbn.com>
Subject: Re: [Ipsec] Minor comment/question on draft-ietf-ipsec-esp-v3-09.txt
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.7 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ipsec@ietf.org
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
At 3:59 PM +0200 2/16/05, Markku Savela wrote: >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.] > Inside the ESP payload, after the optional IV, is the "next layer protocol header." It is referred to as "rest of payload data" in Figure 2. Typically, for transport mode this will be TCP or UDP. For tunnel mode, it is IP. This text is part of a discussion reminding folks that the IV, if present, must preserve the 4 or 8 byte alignment requirements for the relevant IP version. We assume that the ESP payload, overall, started on an appropriate boundary, so the addition of the 8 bytes of SPI plus sequence number preserved this alignment. But the IV, if present, could break the alignment. Steve _______________________________________________ Ipsec mailing list Ipsec@ietf.org https://www1.ietf.org/mailman/listinfo/ipsec
- [Ipsec] Minor comment/question on draft-ietf-ipse… Markku Savela
- Re: [Ipsec] Minor comment/question on draft-ietf-… Stephen Kent
- Re: [Ipsec] Minor comment/question on draft-ietf-… Paul Koning
- Re: [Ipsec] Minor comment/question on draft-ietf-… Markku Savela