RE: TRIGTRAN Security Considerations (was: RE: [Trigtran] TRIGTRAN Nextsteps ("let the games begin"))

john.loughney@nokia.com Wed, 15 January 2003 04:36 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 XAA22265 for <trigtran-archive@odin.ietf.org>; Tue, 14 Jan 2003 23:36:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0F4p6i30865 for trigtran-archive@odin.ietf.org; Tue, 14 Jan 2003 23:51: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 h0F4p5J30862 for <trigtran-web-archive@optimus.ietf.org>; Tue, 14 Jan 2003 23:51:05 -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 XAA22260 for <trigtran-web-archive@ietf.org>; Tue, 14 Jan 2003 23:36:08 -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 h0F4p1J30854; Tue, 14 Jan 2003 23:51:01 -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 h0F4oxJ30835 for <trigtran@optimus.ietf.org>; Tue, 14 Jan 2003 23:50:59 -0500
Received: from mgw-x1.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22257 for <trigtran@ietf.org>; Tue, 14 Jan 2003 23:36:01 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id h0F4cO002440 for <trigtran@ietf.org>; Wed, 15 Jan 2003 06:38:24 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5fccf8f541ac158f25049@esvir05nok.ntc.nokia.com>; Wed, 15 Jan 2003 06:39:20 +0200
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 15 Jan 2003 06:39:19 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 15 Jan 2003 06:39:18 +0200
Received: from esebe022.NOE.Nokia.com ([172.21.138.113]) by esebe013.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 15 Jan 2003 06:39:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: TRIGTRAN Security Considerations (was: RE: [Trigtran] TRIGTRAN Nextsteps ("let the games begin"))
Date: Wed, 15 Jan 2003 06:39:17 +0200
Message-ID: <A16A3EE4D4CA124FADC7987B1AC89FE440EA87@esebe022.ntc.nokia.com>
Thread-Topic: [Trigtran] TRIGTRAN Nextsteps ("let the games begin")
Thread-Index: AcK7D/szmzj3l8ePS/6cWbM+IrtUHAAB5McQACEOlIAAD5u40AAdcPdA
To: sdawkins@cynetanetworks.com, trigtran@ietf.org
X-OriginalArrivalTime: 15 Jan 2003 04:39:18.0247 (UTC) FILETIME=[10A54F70:01C2BC50]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0F4oxJ30836
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Spencer,

So, cutting to the chase:

> So, I think the short answer to John's question is, "yes, 
> that's exactly the kind of thing I'd hope TRIGTRAN triggers 
> would be used for."

Good, I think that would be a useful thing for TRIGTRAN to work
on.

thanks,
John

> 
> Spencer
> 
> > -----Original Message-----
> > From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]
> > Sent: Tuesday, January 14, 2003 1:11 AM
> > To: Spencer Dawkins; trigtran@ietf.org
> > Subject: RE: TRIGTRAN Security Considerations (was: RE: [Trigtran]
> > TRIGTRAN Nextsteps ("let the games begin"))
> > 
> > 
> > Spencer,
> > 
> > Quick question - in a number of wireless networks, there can 
> > be spurious time-outs
> > due to radio unavailability (or bad layer 2/3 coupling).  
> > Quite often, this can 
> > kick-off a chain of events, along the line of time-out -> tcp 
> > abort -> application 
> > protocol tear-down, security association tear-down.  Can 
> > TRIGTRAN also be used to 
> > prevent unnescessary tear-downs (a sort of - hold on, don't 
> > disconnect quite yet 
> > message)? If so, your text below might need to be updated slightly.
> > 
> > thanks,
> > John
> _______________________________________________
> Trigtran mailing list
> Trigtran@ietf.org
> https://www1.ietf.org/mailman/listinfo/trigtran
> 
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran