Re: [midcom] NAT traversal in IPSEC
Melinda Shore <mshore@cisco.com> Sun, 18 November 2001 15:02 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25323 for <midcom-archive@odin.ietf.org>; Sun, 18 Nov 2001 10:02:07 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA20885 for midcom-archive@odin.ietf.org; Sun, 18 Nov 2001 10:02:11 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20510; Sun, 18 Nov 2001 09:58:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20481 for <midcom@optimus.ietf.org>; Sun, 18 Nov 2001 09:58:08 -0500 (EST)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25217 for <midcom@ietf.org>; Sun, 18 Nov 2001 09:58:04 -0500 (EST)
Received: from mira-sjc5-4.cisco.com (mira-sjc5-4.cisco.com [171.71.163.21]) by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id fAIEval15813; Sun, 18 Nov 2001 06:57:36 -0800 (PST)
Received: from spandex.cisco.com (ssh-rtp1.cisco.com [161.44.11.166]) by mira-sjc5-4.cisco.com (Mirapoint) with ESMTP id ABZ14239; Sun, 18 Nov 2001 06:57:08 -0800 (PST)
Message-Id: <5.1.0.14.0.20011118095812.00a53da0@localhost>
X-Sender: mshore@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 18 Nov 2001 10:00:09 -0500
To: Shai Mohaban <shai@kagoor.com>, midcom@ietf.org
From: Melinda Shore <mshore@cisco.com>
Subject: Re: [midcom] NAT traversal in IPSEC
In-Reply-To: <NBBBKGLPAACDDACNPCCMOEEIINAA.shai@kagoor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <midcom.ietf.org>
X-BeenThere: midcom@ietf.org
At 08:42 PM 11/17/01 -0800, Shai Mohaban wrote: >Does anyone follow the related work in the IPSEC WG? It seems that some IDs >there are dealing with similar issues: >http://www.ietf.org/internet-drafts/draft-ietf-ipsec-nat-reqts-00.txt >http://www.ietf.org/internet-drafts/draft-ietf-ipsec-nat-t-ike-01.txt >http://www.ietf.org/internet-drafts/draft-ietf-ipsec-udp-encaps-justificatio >n-00.txt They're dealing with a different set of problems - it's not that they don't know where to send the traffic, it's that header rewrites break the HMAC. Melinda _______________________________________________ midcom mailing list midcom@ietf.org http://www1.ietf.org/mailman/listinfo/midcom
- [midcom] NAT traversal in IPSEC Shai Mohaban
- Re: [midcom] NAT traversal in IPSEC Melinda Shore