Re: (NAT) Re: Interactions between IPSEC and NAT

"Derrell D. Piper" <ddp@network-alchemy.com> Thu, 05 February 1998 18:12 UTC

Delivery-Date: Thu, 05 Feb 1998 13:12:28 -0500
Return-Path: owner-nat@livingston.com
Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.7/8.8.7a) with ESMTP id NAA15287 for <ietf-archive@ietf.org>; Thu, 5 Feb 1998 13:12:15 -0500 (EST)
Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA10872; Thu, 5 Feb 1998 10:04:50 -0800 (PST)
Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA22314 for nat-outgoing; Thu, 5 Feb 1998 10:09:54 -0800 (PST)
Message-Id: <199802051803.KAA10792@bast.livingston.com>
To: ben@ascend.com
cc: bound@zk3.dec.com, Alex Alten <Andrade@netcom.com>, perry@piermont.com, Dan Nessett <Dan_Nessett@tdc.3com.com>, ipsec@tis.com, nat@livingston.com
Subject: Re: (NAT) Re: Interactions between IPSEC and NAT
In-reply-to: Your message of "Thu, 05 Feb 1998 10:49:44 EST." <199802051549.KAA05251@carp.morningstar.com>
Date: Thu, 05 Feb 1998 10:08:56 -0800
From: "Derrell D. Piper" <ddp@network-alchemy.com>
Sender: owner-nat@livingston.com
Precedence: bulk
Reply-To: "Derrell D. Piper" <ddp@network-alchemy.com>

>I know that one of the important points mentioned in the Washington was
>that if NAT were going to fly as a WG it would need to work around the
>security interactions by modifications to the way we do NAT instead of
>modifications to the way we do security.

There's a good idea!
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe nat' in the body of the message.