Buffer Management for IPsec
shganguly@hss.hns.com Thu, 18 November 1999 14:23 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA27252; Thu, 18 Nov 1999 06:23:10 -0800 (PST)
Received: by lists.tislabs.com (8.9.1/8.9.1) id HAA03342 Thu, 18 Nov 1999 07:35:55 -0500 (EST)
From: shganguly@hss.hns.com
X-Lotus-FromDomain: HSS
To: ipsec@lists.tislabs.com
Message-ID: <6525682D.0044FCFF.00@sandesh.hss.hns.com>
Date: Thu, 18 Nov 1999 18:03:18 +0530
Subject: Buffer Management for IPsec
Mime-Version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-Disposition: inline
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Hi, This is regarding the buffer management issues for IPsec implementation. Protocols like AH, ESP require that some extra fields have to be inserted in between the original buffer. As a result of this, for doing authentication, encrption requires that the original buffer be copied to another buffer, and then do the processing. This buffer copy operation will result in a noticeable degradation in the performance of the system. Is there any way of getting over this? This problem is specifically for BITS and BITW kind of implementation. -Shamik Ganguly Hughes Software Systems, India
- Buffer Management for IPsec shganguly