RE: [Trigtran] TRIGTRAN LinkUp first draft available
"Duke, Martin" <martin.duke@boeing.com> Fri, 08 August 2003 15:06 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 LAA14504 for <trigtran-archive@odin.ietf.org>; Fri, 8 Aug 2003 11:06:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l8od-0000l5-9b for trigtran-archive@odin.ietf.org; Fri, 08 Aug 2003 11:06:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h78F63tl002911 for trigtran-archive@odin.ietf.org; Fri, 8 Aug 2003 11:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l8od-0000ks-6K for trigtran-web-archive@optimus.ietf.org; Fri, 08 Aug 2003 11:06:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14496 for <trigtran-web-archive@ietf.org>; Fri, 8 Aug 2003 11:05:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19l8oa-0001OB-00 for trigtran-web-archive@ietf.org; Fri, 08 Aug 2003 11:06:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19l8oZ-0001O8-00 for trigtran-web-archive@ietf.org; Fri, 08 Aug 2003 11:05:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l8ob-0000kD-Mu; Fri, 08 Aug 2003 11:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19l8oV-0000jm-4e for trigtran@optimus.ietf.org; Fri, 08 Aug 2003 11:05:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14492 for <trigtran@ietf.org>; Fri, 8 Aug 2003 11:05:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19l8oS-0001O5-00 for trigtran@ietf.org; Fri, 08 Aug 2003 11:05:52 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx with esmtp (Exim 4.12) id 19l8oR-0001O1-00 for trigtran@ietf.org; Fri, 08 Aug 2003 11:05:51 -0400
Received: from slb-av-01.boeing.com ([129.172.13.4]) by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id IAA27246; Fri, 8 Aug 2003 08:05:07 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id IAA09267; Fri, 8 Aug 2003 08:05:50 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h78F4lR25068; Fri, 8 Aug 2003 08:04:47 -0700 (PDT)
Received: from XCH-NW-03.nw.nos.boeing.com ([192.42.226.68]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662); Fri, 8 Aug 2003 08:04:51 -0700
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: RE: [Trigtran] TRIGTRAN LinkUp first draft available
Date: Fri, 08 Aug 2003 08:04:51 -0700
Message-ID: <B96DB973FD58EE469E4426886240EE97294A59@xch-nw-03.nw.nos.boeing.com>
Thread-Topic: [Trigtran] TRIGTRAN LinkUp first draft available
Thread-Index: AcNdSUYzv4F+Ey9ESBqP7WWJHflgAAAdRl6g
From: "Duke, Martin" <martin.duke@boeing.com>
To: Spencer Dawkins <spencer@mcsr-labs.org>, Trigtran Mailing List <trigtran@ietf.org>
X-OriginalArrivalTime: 08 Aug 2003 15:04:51.0483 (UTC) FILETIME=[6AE15EB0:01C35DBE]
Content-Transfer-Encoding: quoted-printable
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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Spencer, My apologies. You are correct both about your mechanism and the way in which I misunderstood it. Martin > -----Original Message----- > From: Spencer Dawkins [mailto:spencer@mcsr-labs.org] > Sent: Thursday, August 07, 2003 6:05 PM > To: Trigtran Mailing List > Subject: Re: [Trigtran] TRIGTRAN LinkUp first draft available > > > Dear Martin, > > I am confused. Let me try to dig out a bit. > > The current LinkUp draft is an end-to-end mechanism - no intermediary > is involved, and no intermediary modifications (to allow buffering or > ACK-from-intermediary) are required. > > If a sending TCP sees an iimmediately-adjacent interface go active > ("LinkUp"), the sending TCP already knows everything it needs to know, > in order to short-circuit an RTO timer and retransmit - just send the > first queued packet available from the application. > > LinkUp covers the case where a receiving TCP sees its > immediately-adjacent interface go active. The only in-band signal the > receiving TCP can send to indicate LinkUp to the far-end sending TCP > is an ACK - that's the "hint" for the far-end sending TCP to > short-circuit its RTO timer and retransmit. > > Are we talking about the same thing? (I'm wondering if you're thinking > about buffering data packets at an intermediary, which sees its > immediately-adjacent interface go active and retransmits the data > packet) > > Spencer > > ----- Original Message ----- > From: "Duke, Martin" <martin.duke@boeing.com> > To: "Spencer Dawkins" <spencer@mcsr-labs.org>; "Trigtran Mailing List" > <trigtran@ietf.org> > Cc: "Henderson, Thomas R" <thomas.r.henderson@boeing.com> > Sent: Thursday, August 07, 2003 5:16 PM > Subject: RE: [Trigtran] TRIGTRAN LinkUp first draft available > > > Spencer, > > Have you considered buffering the DATA packets rather than the ACKs? > > This has significant benefits: > - The middlebox doesn't have to buffer packets until the outage is > detected, since DATA will be retransmitted by the endpoint anyway. > > - sender-side modification is not strictly necessary. Consider: > The DATA packet buffered will either be new to the receiver, or of an > earlier sequence number. In either case, if it was retransmitted by > the sender, the sender hasn't seen the ACK for it. The receiver will > generate either an ACK or a DUPACK, but it will advance the sender's > "left edge" and generate new transmissions. > > Thoughts? > > -Martin > > > -----Original Message----- > > From: Spencer Dawkins [mailto:spencer@mcsr-labs.org] > > Sent: Tuesday, August 05, 2003 10:33 AM > > To: Trigtran Mailing List > > Cc: Jon Peterson; Allison Mankin > > Subject: [Trigtran] TRIGTRAN work moving to new locations > > > > > > Just to let people know my/Carl's current understanding of > TRIGTRAN - > > and Jon and Allison can correct any misstatements, of course! > > > > We gave a TRIGTRAN perspective at the ALIAS BoF in Vienna > > (http://www.ietf.org/ietf/03jul/alias.txt), and it looks like the > > following things are happening: > > > > - Hui-Lan and Kevin are expecting to develop mechanisms that would > > support "Performance Enhancing Proxies" > > (http://www.ietf.org/rfc/rfc3135.txt), as described in PILC, as part > > of a broader class of problems, so most of the TRIGTRAN notification > > discussion should move to ALIAS (TO JOIN: > > http://mailman.berkeley.intel-research.net/mailman/listinfo/alias) > > > > - Part of this work will include characterization of the services > > offered by intermediaries, so this portion of TRIGTRAN will move to > > ALIAS as well > > > > - the LinkUp work will continue, but will move to TSVWG, because no > > intermediaries are involved in the current draft > > > (http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-linkup-00. > > txt) > > > > I'm expecting to send out an updated LinkUp draft in the > > not-too-distant future, but we didn't really get to talk about the > > current draft in Vienna, so I'm very eager to hear comments before > we > > sail into TSVWG - first impressions matter, of course. > > > > And thanks for your help and feedback. Carl and I put up a full page > > of acknowledgements in San Francisco, and we probably missed people. > > We couldn't have gotten this far without you. > > > > Spencer, for Spencer and Carl > > > > > > _______________________________________________ > > 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 > _______________________________________________ Trigtran mailing list Trigtran@ietf.org https://www1.ietf.org/mailman/listinfo/trigtran
- RE: [Trigtran] TRIGTRAN LinkUp first draft availa… Duke, Martin
- Re: [Trigtran] TRIGTRAN LinkUp first draft availa… Spencer Dawkins
- RE: [Trigtran] TRIGTRAN LinkUp first draft availa… Duke, Martin