Extended seq number
Ramana Yarlagadda <ramana.yarlagadda@analog.com> Tue, 23 April 2002 19:38 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 g3NJcwa06222; Tue, 23 Apr 2002 12:38:59 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id OAA14580 Tue, 23 Apr 2002 14:55:53 -0400 (EDT)
Message-Id: <4.3.2.7.1.20020423120550.00bd0510@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 12:05:57 -0700
To: ipsec@lists.tislabs.com
From: Ramana Yarlagadda <ramana.yarlagadda@analog.com>
Subject: Extended seq number
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
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
- Extended seq number Ramana Yarlagadda
- Re: Extended seq number Stephen Kent
- Re: Extended seq number Ramana Yarlagadda