IETF Logo Mail Archive

Re: IPCOMP and IPSEC

Naganand Doraswamy <naganand@BayNetworks.COM> Thu, 28 May 1998 13:00 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id JAA26751 for ipsec-outgoing; Thu, 28 May 1998 09:00:22 -0400 (EDT)
Message-Id: <3.0.32.19980528085427.00db5a50@bl-mail1.corpeast.baynetworks.com>
X-Sender: ndoraswa_pop@bl-mail1.corpeast.baynetworks.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 28 May 1998 08:54:28 -0400
To: Stephen Waters <Stephen.Waters@digital.com>, ippcp@external.cisco.com, ipsec@tis.com
From: Naganand Doraswamy <naganand@BayNetworks.COM>
Subject: Re: IPCOMP and IPSEC
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

>If this is supported, is it detailed anywhere?  For example, if an
>Explicit IV is used, would it come after the ESP header or after the
>IPCOMP header?
>

You construct the ESP payload in the same fashion for any protocol payload
you are carrying. ESP treats IPCOMP as an other protocol- IP, TCP.
--Naganand

-----------------------------------------------------------------
Naganand Doraswamy				(978)916-1323 (O)
Bay Architecture Lab				(978)916-0620 (Fax)
3 Federal St, Mail Stop BL3-03
Billerica, MA 01821

v2.30.2 | Report a Bug | By Email | System Status