Re: Extended seq number
Ramana Yarlagadda <ramana.yarlagadda@analog.com> Tue, 23 April 2002 21:09 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g3NL92a15010; Tue, 23 Apr 2002 14:09:02 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id QAA14781 Tue, 23 Apr 2002 16:28:45 -0400 (EDT)
Message-Id: <4.3.2.7.1.20020423133413.00ccbef0@golf.cpgdesign.analog.com>
X-Sender: ramana@golf.cpgdesign.analog.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 23 Apr 2002 13:39:13 -0700
To: Stephen Kent <kent@bbn.com>
From: Ramana Yarlagadda <ramana.yarlagadda@analog.com>
Subject: Re: Extended seq number
Cc: ipsec@lists.tislabs.com
In-Reply-To: <p0510030ab8eb6f7c2a6d@[128.89.88.34]>
References: <4.3.2.7.1.20020423120550.00bd0510@golf.cpgdesign.analog.com> <4.3.2.7.1.20020423120550.00bd0510@golf.cpgdesign.analog.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
>>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. Sorry, I have missed it and this is what exactly i am looking for. -thanks -ramana >Steve
- Extended seq number Ramana Yarlagadda
- Re: Extended seq number Stephen Kent
- Re: Extended seq number Ramana Yarlagadda