Re: Extended seq number

Stephen Kent <kent@bbn.com> Tue, 23 April 2002 20:43 UTC

Mime-Version: 1.0
Message-Id: <p0510030ab8eb6f7c2a6d@[128.89.88.34]>
In-Reply-To: <4.3.2.7.1.20020423120550.00bd0510@golf.cpgdesign.analog.com>
References: <4.3.2.7.1.20020423120550.00bd0510@golf.cpgdesign.analog.com>
Date: Tue, 23 Apr 2002 16:08:27 -0400
To: Ramana Yarlagadda <ramana.yarlagadda@analog.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Extended seq number
Cc: ipsec@lists.tislabs.com
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

At 12:05 PM -0700 4/23/02, Ramana Yarlagadda wrote:
>Hi, All
>
>I am going thruough the Draft-ietf-ipsec-esp-v3-02.txt.
>
>1)  Extended Sequence number is of 64bits (optioanally) and  the ICV 
>is calucluated over the entire 64bits.but the sequence number 
>transmitted  is of 32 bits , to keep the overhead low.
>
>Because of  this requirement  implementaion becomes quite complex, 
>at least not straight forward.  what  we frame (IPSec header) is 
>different from what we send.
>
>
>-cheers
>-ramana

The high order 32 bits of the ESN are appended to the packet 
specifically to make it easier to strip them prior to transmission. 
I don't know how to make it easier, and still not send the extra bits.

Steve

Extended seq number Ramana Yarlagadda
Re: Extended seq number Stephen Kent
Re: Extended seq number Ramana Yarlagadda