IETF Logo Mail Archive

RE: IPCOMP and IPSEC

Roy Pereira <rpereira@TimeStep.com> Sat, 30 May 1998 01:55 UTC

Return-Path: rpereira@TimeStep.com
Received: from beasley.cisco.com (mailgate-sj-2.cisco.com [171.69.2.135]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id SAA08748 for <ippcp-archive-file@ftp-eng.cisco.com>; Fri, 29 May 1998 18:55:27 -0700 (PDT)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by beasley.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id JAA18402 for <ippcp@external.cisco.com>; Thu, 28 May 1998 09:41:37 -0700 (PDT)
Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id JAA02526 for <ippcp@external.cisco.com>; Thu, 28 May 1998 09:41:35 -0700 (PDT)
Received: from ns.newbridge.com(192.75.23.67) by proxy2.cisco.com via smap (V2.0) id xma002505; Thu, 28 May 98 16:41:30 GMT
X-SMAP-Received-From: outside
Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id MAA01129; Thu, 28 May 1998 12:37:36 -0400 (EDT)
Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma029559; Thu May 28 12:26:20 1998
Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 28 May 1998 16:26:19 UT
Received: from exchange.timestep.com (exchange.timestep.com [192.168.219.193]) by ca.newbridge.com. (8.8.6/8.8.6) with ESMTP id MAA09020; Thu, 28 May 1998 12:26:19 -0400 (EDT)
Received: by exchange.timestep.com with Internet Mail Service (5.5.1960.3) id <LKBYXL15>; Thu, 28 May 1998 12:25:18 -0400
Message-ID: <319A1C5F94C8D11192DE00805FBBADDF1244E2@exchange.timestep.com>
From: Roy Pereira <rpereira@TimeStep.com>
To: Stephen Waters <Stephen.Waters@digital.com>, ippcp@external.cisco.com, ipsec@tis.com
Subject: RE: IPCOMP and IPSEC
Date: Thu, 28 May 1998 12:25:17 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

IPComp may be added by a security gateway just like IPSec ESP/AH is
added.  It would probably look like this though:

[IP2]
  [ESP spi+replay+iv]
    [IP1]
    [IPCOMP]
      [TCP]
      [data] 
    [ESP padding+next protocol+auth]



> -----Original Message-----
> From: Stephen Waters [mailto:Stephen.Waters@digital.com]
> Sent: Wednesday, May 27, 1998 6:19 PM
> To: ippcp@external.cisco.com; ipsec@tis.com
> Subject: IPCOMP and IPSEC
> 
> 
> 
> Is IPCOMP restricted for use by Hosts (at packet origin), or can it be
> appended by a Security Gateway as part of the process of 
> adding an IPSEC
> tunnel header?
> 
> e.g.
> 
> Original host packet [IP1][TCP][data]
> 
> After passing through a security gateway/IP tunnel:
> 
> [IP2][ESP][IPCOMP][IP1][TCP][data][padding/next protocol][ESP auth]
> 
> 
> 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?
> 
> 
> 
> 
> 
> Stephen Waters
> DEVON, UK
> 
> National: 01548 551012 / 550474
> International: 44 1548 551012 / 550474
> Stephen.Waters@Digital.com 
>

v2.23.0 | Report a Bug | By Email