RE: [Trigtran] TRIGTRAN Justification

"Spencer Dawkins" <sdawkins@cynetanetworks.com> Fri, 17 January 2003 21:35 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 QAA05092 for <trigtran-archive@odin.ietf.org>; Fri, 17 Jan 2003 16:35:34 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0HLpLh32175 for trigtran-archive@odin.ietf.org; Fri, 17 Jan 2003 16:51:21 -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 h0HLpKJ32172 for <trigtran-web-archive@optimus.ietf.org>; Fri, 17 Jan 2003 16:51:20 -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 QAA05074 for <trigtran-web-archive@ietf.org>; Fri, 17 Jan 2003 16:35:03 -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 h0HLpHJ32151; Fri, 17 Jan 2003 16:51:17 -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 h0HLb9J31285 for <trigtran@optimus.ietf.org>; Fri, 17 Jan 2003 16:37:09 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04754 for <trigtran@ietf.org>; Fri, 17 Jan 2003 16:20:52 -0500 (EST)
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] TRIGTRAN Justification
Date: Fri, 17 Jan 2003 15:24:15 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543BA83@mail.cynetanetworks.com>
Thread-Topic: [Trigtran] TRIGTRAN Justification
Thread-Index: AcK+bS16/vDFbmo9RDK2F4QNqtDK1gAASaiA
From: Spencer Dawkins <sdawkins@cynetanetworks.com>
To: trigtran@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0HLb9J31286
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

OK, I think we've talked this through. My suggestion is that 
the next couple of weeks, we focus on what additional things 
a transport would want to know, that transports don't get told
explicitly today.

Spencer

> -----Original Message-----
> From: Kacheong Poon [mailto:poon@cs.wisc.edu]
> Sent: Friday, January 17, 2003 3:13 PM
> To: Spencer Dawkins; trigtran@ietf.org
> Subject: RE: [Trigtran] TRIGTRAN Justification
> 
> 
> Included message from "Spencer Dawkins" <sdawkins@cynetanetworks.com>:
> 
> >----
> >What I'm getting from your e-mails is that we're 
> >missing a possible path forward.
> >
> >I've been looking at only two choices:
> >
> >- implicit end-to-end signaling, and 
> >- explicit triggers
> >
> >If I'm getting your point (please let me know if not), 
> >you're thinking of a third choice,
> >
> >- explicit end-to-end signaling
> >
> >Would you see this as part of TCP, 
> >or a completely different mechanism?
> >----
> 
> Yes, I think it is another choice that should be evaluated
> before deciding which notification mechanism is the best
> one to spend effort on.
> 
> 							K. Poon.
> 
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran