IETF Logo Mail Archive

Re: IPCOMP and IPSEC

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

Return-Path: naganand@BayNetworks.COM
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA02989 for <ippcp-archive-file@ftp-eng.cisco.com>; Thu, 28 May 1998 06:15:12 -0700 (PDT)
Received: from proxy3.cisco.com (proxy3.cisco.com [192.31.7.90]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id GAA13219 for <ippcp@external.cisco.com>; Thu, 28 May 1998 06:15:05 -0700 (PDT)
Received: (from smap@localhost) by proxy3.cisco.com (8.8.7/8.8.5) id GAA29014 for <ippcp@external.cisco.com>; Thu, 28 May 1998 06:15:04 -0700 (PDT)
Received: from ns2.baynetworks.com(134.177.3.16) by proxy3.cisco.com via smap (V2.0) id xma029009; Thu, 28 May 98 13:15:03 GMT
X-SMAP-Received-From: outside
Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id FAA24380; Thu, 28 May 1998 05:52:40 -0700 (PDT)
Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with SMTP id IAA24374; Thu, 28 May 1998 08:52:19 -0400 (EDT)
Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA20947; Thu, 28 May 98 08:54:47 EDT for ipsec@tis.com
Received: from ndoraswa.corpeast.baynetworks.com ([192.32.242.16]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with SMTP id AAA13891; Thu, 28 May 1998 08:52:08 -0400
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"

>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.23.0 | Report a Bug | By Email