IETF Logo Mail Archive

RE: [Trigtran] TRIGTRAN Justification

Kacheong Poon <poon@cs.wisc.edu> Fri, 17 January 2003 21:33 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 QAA05026 for <trigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 16:33:20 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0HLn6832063 for trigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 16:49:06 -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 h0HLn6J32060 for <trigtran-web-archive@optimus.ietf.org>; Fri, 17 Jan 2003 16:49:06 -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 QAA05018 for <trigtran-web-archive@ietf.org>; Fri, 17 Jan 2003 16:32:49 -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 h0HLn2J32047; Fri, 17 Jan 2003 16:49:02 -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 h0HLWCJ30871 for <trigtran@optimus.ietf.org>; Fri, 17 Jan 2003 16:32:12 -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 QAA04704 for <trigtran@ietf.org>; Fri, 17 Jan 2003 16:15:55 -0500 (EST)
Received: (from poon@localhost) by parmesan.cs.wisc.edu (8.9.2/8.9.2) id PAA05304; Fri, 17 Jan 2003 15:19:18 -0600 (CST)
Date: Fri, 17 Jan 2003 15:19:18 -0600
From: Kacheong Poon <poon@cs.wisc.edu>
Message-Id: <200301172119.PAA05304@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>:

>----
>On most of the deployed WIRELESS networks I've seen, 
>almost all corporate IPSEC VPN tunnels terminate at 
>the gateway into the wireless network (no IPSEC within 
>the wireless network). In this case, TRIGTRAN-capable 
>access router wouldn't be affected by IPSEC VPN tunnels.
>----

I see.  I guess the point to note is that trigger will
not work in all kind of network topology.  I believe an
end2end mechanism will.

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

v2.23.0 | Report a Bug | By Email