Re: proposed IPSEC changes/extensions
Hilarie Orman <ho@earth.hpc.org> Thu, 31 October 1996 16:25 UTC
Received: from cnri by ietf.org id aa02031; 31 Oct 96 11:25 EST
Received: from neptune.hq.tis.com by CNRI.Reston.VA.US id aa13976; 31 Oct 96 11:25 EST
Received: from neptune.tis.com by neptune.TIS.COM id aa16443; 31 Oct 96 10:50 EST
Date: Thu, 31 Oct 1996 09:46:34 -0500
From: Hilarie Orman <ho@earth.hpc.org>
Message-Id: <199610311446.JAA02150@earth.hpc.org>
To: ipsec@tis.com
MMDF-Warning: Unable to confirm address in preceding line at neptune.TIS.COM
Subject: Re: proposed IPSEC changes/extensions
Sender: ipsec-approval@neptune.tis.com
Precedence: bulk
> > Certainly support for *sending* packets with arbitrarily-nested headers > > is harder to implement. > Yep! I don't see why. Define the SA's, make a list of them, perform some form of "open" operation with the list. Send. Interpret list, one SA at a time. Hilarie
- proposed IPSEC changes/extensions Stephen Kent
- Re: proposed IPSEC changes/extensions David Wagner
- Re: proposed IPSEC changes/extensions Ran Atkinson
- Re: proposed IPSEC changes/extensions Hilarie Orman
- Re: proposed IPSEC changes/extensions pau
- Re: proposed IPSEC changes/extensions Michael Sabin
- Re: proposed IPSEC changes/extensions Stephen Kent
- Re: proposed IPSEC changes/extensions pau
- Re: proposed IPSEC changes/extensions Bill Sommerfeld
- Re: proposed IPSEC changes/extensions pau
- Re: proposed IPSEC changes/extensions Santeri Paavolainen
- Re: proposed IPSEC changes/extensions Rodney Thayer
- Re: proposed IPSEC changes/extensions Santeri Paavolainen
- Re: proposed IPSEC changes/extensions Stephen Kent
- Re: proposed IPSEC changes/extensions David Wagner
- Re: proposed IPSEC changes/extensions Steven Bellovin
- Re: proposed IPSEC changes/extensions Michael Sabin
- Re: proposed IPSEC changes/extensions John Gilmore