RE: [Trigtran] TRIGTRAN Justification

Kacheong Poon <poon@cs.wisc.edu> Fri, 17 January 2003 19:32 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02414 for <trigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 14:32:26 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0HJm9b24809 for trigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 14:48:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HJm9J24806 for <trigtran-web-archive@optimus.ietf.org>; Fri, 17 Jan 2003 14:48:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02393 for <trigtran-web-archive@ietf.org>; Fri, 17 Jan 2003 14:31:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HJm5J24764; Fri, 17 Jan 2003 14:48:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0HJe2J24438 for <trigtran@optimus.ietf.org>; Fri, 17 Jan 2003 14:40:02 -0500
Received: from parmesan.cs.wisc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02208 for <trigtran@ietf.org>; Fri, 17 Jan 2003 14:23:48 -0500 (EST)
Received: (from poon@localhost) by parmesan.cs.wisc.edu (8.9.2/8.9.2) id NAA04830; Fri, 17 Jan 2003 13:27:10 -0600 (CST)
Date: Fri, 17 Jan 2003 13:27:10 -0600
From: Kacheong Poon <poon@cs.wisc.edu>
Message-Id: <200301171927.NAA04830@parmesan.cs.wisc.edu>
To: sdawkins@cynetanetworks.com, trigtran@ietf.org
Subject: RE: [Trigtran] TRIGTRAN Justification
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=subscribe>

Included message from "Spencer Dawkins" <sdawkins@cynetanetworks.com>:

>----
>Yes, we definitely need to think about tunnels.
>
>My immediate take is that, I don't know why TRIGTRAN shouldn't work, although
>a Transport IPSEC security gateway would have to relay the trigger (but it
>knows the relationship between the interior destination IP address and the
>tunnel, so this seems possible). But let's keep the question open, for now.
>----

My understanding of what Yogesh said is a little bit different.
Consider the most common case scenario in today's Internet.  People
use IPsec to setup VPN tunnels between their machines and corporate
gateways.  In the scenario considered by TRIGTRAN, one end point of
the tunnel is actually behind the "problematic link."  The router
on the other side of the "problematic link" has no idea what is
going on.

							K. Poon.
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran