From exim@www1.ietf.org Tue Feb 3 23:50:36 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22376 for ; Tue, 3 Feb 2004 23:50:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoEzI-00039x-JU for tsvwg-archive@odin.ietf.org; Tue, 03 Feb 2004 23:50:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i144o8fu012107 for tsvwg-archive@odin.ietf.org; Tue, 3 Feb 2004 23:50:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoEzB-00035b-HN; Tue, 03 Feb 2004 23:50:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoEz6-00034O-79 for tsvwg@optimus.ietf.org; Tue, 03 Feb 2004 23:49:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22373 for ; Tue, 3 Feb 2004 23:49:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AoEz4-00006t-00 for tsvwg@ietf.org; Tue, 03 Feb 2004 23:49:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AoEyC-00001b-00 for tsvwg@ietf.org; Tue, 03 Feb 2004 23:49:00 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1AoExe-0007je-00 for tsvwg@ietf.org; Tue, 03 Feb 2004 23:48:26 -0500 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1AoExU-000LvN-Ai; Wed, 04 Feb 2004 04:48:16 +0000 To: tsvwg@ietf.org Cc: mankin@psg.com, jon.peterson@neustar.biz Reply-To: mankin@psg.com Date: Tue, 03 Feb 2004 20:48:16 -0800 From: Allison Mankin Message-Id: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , This begins a working group last call for the new revision of the Early Retranmsit i-d (draft-allman-tcp-early-rexmt-03.txt) that came out in December. It has been discussed throughout its life in TSVWG, and the authors and we think it can be completed here rather than moved to the coming TCPM working group. The WGLC is for Experimental RFC status. Comments should be made by February 17, 2004. Your TSVWG Chairs _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 4 00:33:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23272 for ; Wed, 4 Feb 2004 00:33:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoFeo-00063J-Ua for tsvwg-archive@odin.ietf.org; Wed, 04 Feb 2004 00:33:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i145X2bN023232 for tsvwg-archive@odin.ietf.org; Wed, 4 Feb 2004 00:33:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoFen-00062I-FB; Wed, 04 Feb 2004 00:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoFef-00061l-IG for tsvwg@optimus.ietf.org; Wed, 04 Feb 2004 00:32:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23263 for ; Wed, 4 Feb 2004 00:32:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AoFec-0003lx-00 for tsvwg@ietf.org; Wed, 04 Feb 2004 00:32:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AoFdh-0003fz-00 for tsvwg@ietf.org; Wed, 04 Feb 2004 00:31:54 -0500 Received: from gw.openss7.com ([142.179.199.224] ident=[+B3HogrrMvLaO+F7WpR3aQFmfh5GoV9W]) by ietf-mx with esmtp (Exim 4.12) id 1AoFcr-0003ZH-00 for tsvwg@ietf.org; Wed, 04 Feb 2004 00:31:01 -0500 Received: from ns.pigworks.openss7.net (IDENT:tgh7WarieqkgQMcMKdRCSpsM4SV9kYCT@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i145UuI06029 for ; Tue, 3 Feb 2004 22:30:56 -0700 Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id i145UuY24154 for tsvwg@ietf.org; Tue, 3 Feb 2004 22:30:56 -0700 Date: Tue, 3 Feb 2004 22:30:56 -0700 From: "Brian F. G. Bidulock" To: tsvwg@ietf.org Subject: Re: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-prsctp-03.txt Message-ID: <20040203223056.A24024@openss7.org> Reply-To: bidulock@openss7.org References: <200401281608.LAA06708@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200401281608.LAA06708@ietf.org>; from Internet-Drafts@ietf.org on Wed, Jan 28, 2004 at 11:08:13AM -0500 Organization: http://www.openss7.org/ Dsn-Notification-To: Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i145UuI06029 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable All, As we have already gone through WGLC comments on prsctp-00 and these subsequent drafts more than adequately capture the comments from WGLC, is there any reason not to advance this latest draft to IESG? --brian On Wed, 28 Jan 2004, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts dire= ctories. > This draft is a work item of the Transport Area Working Group Working G= roup of the IETF. >=20 > Title : SCTP Partial Reliability Extension > Author(s) : R. Stewart > Filename : draft-ietf-tsvwg-prsctp-03.txt > Pages : 23 > Date : 2004-1-27 > =09 > This memo describes an extension to the Stream Control Transmission > Protocol (SCTP) RFC2960 [5] that allows an SCTP endpoint to signal to > its peer that it should move the cumulative ack point forward. When > both sides of an SCTP association support this extension, it can be > used by an SCTP implementation to provide partially reliable data > transmission service to an upper layer protocol. This memo describes > (1) the protocol extensions, which consist of a new parameter for > INIT and INIT ACK, and a new FORWARD TSN chunk type (2) one example > partially reliable service that can be provided to the upper layer > via this mechanism. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-prsctp-03.txt >=20 > To remove yourself from the IETF Announcement list, send a message to=20 > ietf-announce-request with the word unsubscribe in the body of the mess= age. >=20 > Internet-Drafts are also available by anonymous FTP. Login with the use= rname > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-tsvwg-prsctp-03.txt". >=20 > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html=20 > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-tsvwg-prsctp-03.txt". > =09 > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > =09 > =09 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. --=20 Brian F. G. Bidulock =A6 The reasonable man adapts himself to the =A6 bidulock@openss7.org =A6 world; the unreasonable one persists in =A6 http://www.openss7.org/ =A6 trying to adapt the world to himself. =A6 =A6 Therefore all progress depends on the =A6 =A6 unreasonable man. -- George Bernard Shaw =A6 _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 5 22:01:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25460 for ; Thu, 5 Feb 2004 22:01:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEr-0004xC-2m for tsvwg-archive@odin.ietf.org; Thu, 05 Feb 2004 22:01:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16315P6019015 for tsvwg-archive@odin.ietf.org; Thu, 5 Feb 2004 22:01:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEn-0004wR-En; Thu, 05 Feb 2004 22:01:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AowEB-0004tn-AE for tsvwg@optimus.ietf.org; Thu, 05 Feb 2004 22:00:23 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25439 for ; Thu, 5 Feb 2004 22:00:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AowE8-0005ju-00 for tsvwg@ietf.org; Thu, 05 Feb 2004 22:00:20 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AowDC-0005iN-00 for tsvwg@ietf.org; Thu, 05 Feb 2004 21:59:23 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AowCQ-0005ev-00; Thu, 05 Feb 2004 21:58:34 -0500 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 05 Feb 2004 19:05:14 +0000 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id i162w3hk026648; Thu, 5 Feb 2004 18:58:03 -0800 (PST) Received: from cisco.com (dhcp-128-107-165-142.cisco.com [128.107.165.142]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AQA60444; Thu, 5 Feb 2004 18:58:02 -0800 (PST) Message-ID: <402302BA.4020000@cisco.com> Date: Thu, 05 Feb 2004 18:58:02 -0800 From: Rajiv Raghunarayan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: IPv6MIB , IPv6 , TSVWG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] Discontinuity timer for TCP-MIB counters Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Folks, This point came out of the IESG review of the TCP-MIB, and possibly requires wider discussion. Hence this mail to all the aliases. The current update to TCP-MIB (draft-ietf-ipv6-rfc2012-update-05.txt) does not define any special discontinuity objects, for a case when the counters in the mib experience a discontinuity. There is an implicit assumption that this would be represented by sysUpTime (SNMPv2-MIB). The IESG review suggested that we provide a discontinuity timer for the counters in the mib - could be via sysUpTime or a new discontinuity object. But we state it either way. There are issues to going either way: 1. sysUpTime: If any Counter, that uses sysUpTime as the discontinuity indicator, experiences a discontinuity, then it must reset sysUpTime (basically means a warm (re-)start). Therefore, all *other* counters that also use sysUpTime are going to look and be treated as if they also had a discontinuity. This may have performance implications, in terms of network management stations generating additional queries for these (unaffected) counters as well. 2. Add a new object for indicate discontinuity: This would necessitate adding a new (perhaps) unnecessary object, if sysUpTime can serve the purpose. In addition, systems would have an additional overhead of maintaining this information. Hence the question to folks here is: 1. Are there any known systems that can experience a discontinuity in the TCP counters without affecting the network management portion of the system. For e.g. are there systems that can restart the TCP portion of the system without restarting the network management portion of the system (or the whole system)? 2. Does anyone see any other case in which we might need to/want to maintain a discontinuity timer in the TCP-MIB? My assumption is that there might not be any systems that need an explicit discontinuity timer (but I could be wrong). Hence, would appreciate responses. Thanks, Rajiv. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 05:38:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19635 for ; Fri, 6 Feb 2004 05:38:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap3N6-0008Su-Ue for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 05:38:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16Ac4eb032443 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 05:38:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap3N3-0008QR-Ah; Fri, 06 Feb 2004 05:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap3Mi-0008Ko-Da for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 05:37:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19625 for ; Fri, 6 Feb 2004 05:37:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ap3Me-0002EQ-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 05:37:37 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ap3Ll-0002C8-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 05:36:41 -0500 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1Ap3L7-00027K-00; Fri, 06 Feb 2004 05:36:02 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i16AZS714948; Fri, 6 Feb 2004 04:35:28 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Fri, 6 Feb 2004 11:35:26 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155028EC521@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'Juergen Schoenwaelder'" , raraghun@cisco.com Cc: ipv6mib@ibr.cs.tu-bs.de, ipv6@ietf.org, tsvwg@ietf.org Date: Fri, 6 Feb 2004 11:32:01 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Tsvwg] RE: [ipv6mib] Discontinuity timer for TCP-MIB counters Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , W.r.t. > Here are my 3 thoughs on this: > > 1) So far, sysUpTime has been used by the existing TCP-MIB objects. > Introducing a new discontinuity indicator now raises the question > whether doing so breaks existing implementations. > Good point! > 2) Personally, I doubt that there will be many implementations where > TCP can experience discontinuities that do not also affect other > parts of the networking stack or the whole system. > OK, that is what we need to know. > 3) I do see the problem that sysUpTime might be more frequently reset > as we like due to some other MIBs which do not use explicit > discontinuity indicators and experience more frequent > resets. However, the root of the problem is then really in those > MIBs, not in the TCP-MIB. (Sure, by introducing a discontinuity > indicator for the TCP-MIB we can protect against other misbehaving > MIBs - but is this going to set a precedence which at the end > requires a CLR that better every MIB module has at least one, > perhaps multiple discontinuity indicators?) > You can understand that those "other MIB modules" will also use argument 1) to not have to change, rigth? > In the case of the TCP-MIB, I believe 1) is the killing argument. To > introduce a new discontinuity indicator changes the implicit semantics > of existing objects and would require to introduce new objects, which > I think is prohibitive. > > Conclusion: Spell out that sysUpTime is used as a discontinuity > indicator for the counters. > I can live with that if that is the consensus. Bert > /js _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 10:04:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28454 for ; Fri, 6 Feb 2004 10:04:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap7WW-0005NR-Az for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 10:04:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16F44YK020663 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 10:04:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap7WS-0005M3-6N; Fri, 06 Feb 2004 10:04:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap7WR-0005Lr-3W for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 10:03:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28397 for ; Fri, 6 Feb 2004 10:03:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ap7WO-0002Vy-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 10:03:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ap7VP-0002Qm-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 10:02:56 -0500 Received: from smtp01.uc3m.es ([163.117.136.121]) by ietf-mx with esmtp (Exim 4.12) id 1Ap7Uv-0002MC-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 10:02:25 -0500 Received: from localhost (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with SMTP id 7F3619468 for ; Fri, 6 Feb 2004 16:01:54 +0100 (CET) Received: from acorde.it.uc3m.es (acorde.it.uc3m.es [163.117.139.72]) by smtp01.uc3m.es (Postfix) with ESMTP id 7F38C945F; Fri, 6 Feb 2004 16:01:48 +0100 (CET) From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano To: tsvwg Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L6mzlZEZ1n8yrajmhP6V" Organization: Universidad Carlos III de Madrid Message-Id: <1076079708.807.12.camel@acorde> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 06 Feb 2004 16:01:48 +0100 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] draft-azcorra-tsvwg-tcp-blind-ack-dos-00.txt Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , --=-L6mzlZEZ1n8yrajmhP6V Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello to the TSV WG, We've just submitted an individual Internet draft. Here is a copy of the abstract: TCP relies in communication peers to implement congestion control by hosts voluntary limiting their own data rate. Nevertheless this assumption introduces unsolved DoS attack opportunities. A DoS attack can be easily performed by a host that acknowledges TCP segments not yet received (maybe even not sent). This document presents and briefly describes the problem, already identified and pointed before, but also shows than it can be easily performed (with very interesting results) and proposes some server-side modifications to TCP stack in order to make this attack more difficult to perform. The draft is available at: http://www.ietf.org/internet-drafts/draft-azcorra-tsvwg-tcp-blind-ack-dos-0= 0.txt Any comments are highly welcome. Thanks in advance, Carlos J. =09 --=20 Carlos Jes=FAs Bernardos Cano - http://www.it.uc3m.es/cjbc/ GPG FP: 1880 80D3 8004 25C7 6537 8E02 252A D295 9CFF DEAF --=-L6mzlZEZ1n8yrajmhP6V Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAI6xbJSrSlZz/3q8RAtRYAJ9H5hG+zywmqtmV68ouXX+Qe/x3KwCffJBD LtBT2A7Rqx0mn8Y5Lv8aOeg= =ig7k -----END PGP SIGNATURE----- --=-L6mzlZEZ1n8yrajmhP6V-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 18:09:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28213 for ; Fri, 6 Feb 2004 18:09:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApF5s-0003N6-T9 for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 18:09:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16N94eT012935 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 18:09:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApF5q-0003Ll-AO; Fri, 06 Feb 2004 18:09:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ap1ms-0001sp-Mm for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 03:56:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17210 for ; Fri, 6 Feb 2004 03:56:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ap1mq-0005TP-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 03:56:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ap1lt-0005Ra-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 03:55:34 -0500 Received: from agitator.ibr.cs.tu-bs.de ([134.169.34.18]) by ietf-mx with esmtp (Exim 4.12) id 1Ap1lk-0005PZ-00; Fri, 06 Feb 2004 03:55:25 -0500 Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i168t12Y018338 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Feb 2004 09:55:01 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i168t1Cw015040; Fri, 6 Feb 2004 09:55:01 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) id i168t1iV015037; Fri, 6 Feb 2004 09:55:01 +0100 Date: Fri, 6 Feb 2004 09:55:01 +0100 Message-Id: <200402060855.i168t1iV015037@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: raraghun@cisco.com CC: ipv6mib@ibr.cs.tu-bs.de, ipv6@ietf.org, tsvwg@ietf.org In-reply-to: <402302BA.4020000@cisco.com> (message from Rajiv Raghunarayan on Thu, 05 Feb 2004 18:58:02 -0800) References: <402302BA.4020000@cisco.com> X-IBRFilter-SpamReport: 0 () X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] Re: [ipv6mib] Discontinuity timer for TCP-MIB counters Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , >>>>> Rajiv Raghunarayan writes: Rajiv> The IESG review suggested that we provide a discontinuity timer Rajiv> for the counters in the mib - could be via sysUpTime or a new Rajiv> discontinuity object. But we state it either way. Here are my 3 thoughs on this: 1) So far, sysUpTime has been used by the existing TCP-MIB objects. Introducing a new discontinuity indicator now raises the question whether doing so breaks existing implementations. 2) Personally, I doubt that there will be many implementations where TCP can experience discontinuities that do not also affect other parts of the networking stack or the whole system. 3) I do see the problem that sysUpTime might be more frequently reset as we like due to some other MIBs which do not use explicit discontinuity indicators and experience more frequent resets. However, the root of the problem is then really in those MIBs, not in the TCP-MIB. (Sure, by introducing a discontinuity indicator for the TCP-MIB we can protect against other misbehaving MIBs - but is this going to set a precedence which at the end requires a CLR that better every MIB module has at least one, perhaps multiple discontinuity indicators?) In the case of the TCP-MIB, I believe 1) is the killing argument. To introduce a new discontinuity indicator changes the implicit semantics of existing objects and would require to introduce new objects, which I think is prohibitive. Conclusion: Spell out that sysUpTime is used as a discontinuity indicator for the counters. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 18:09:40 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28246 for ; Fri, 6 Feb 2004 18:09:40 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApF5s-0003NO-UQ for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 18:09:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16N94mi012937 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 18:09:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApF5q-0003M1-Qw; Fri, 06 Feb 2004 18:09:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApDTl-0008Sp-3J for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 16:25:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18629 for ; Fri, 6 Feb 2004 16:25:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApDTj-0006eY-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 16:25:35 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApDRA-000656-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 16:22:57 -0500 Received: from babbage.csee.usf.edu ([131.247.3.2]) by ietf-mx with esmtp (Exim 4.12) id 1ApDOT-0005Xy-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 16:20:10 -0500 Received: from grad.csee.usf.edu (grad [131.247.3.1]) by babbage.csee.usf.edu (8.12.9/8.12.9) with ESMTP id i16LHxZT006069 for ; Fri, 6 Feb 2004 16:17:59 -0500 (EST) Received: from localhost (sduggire@localhost) by grad.csee.usf.edu (8.10.2+Sun/8.10.2) with ESMTP id i16LHv416706 for ; Fri, 6 Feb 2004 16:17:58 -0500 (EST) X-Authentication-Warning: grad.csee.usf.edu: sduggire owned process doing -bs Date: Fri, 6 Feb 2004 16:17:57 -0500 (EST) From: sridhar duggireddy X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] How to get configuration parameters in sctp Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Hi, We are doing an experiment in which we want to compare various versions of protocols like tcp Reno, Vegas, SCTP, Westwood etc. For this I need to get the configuration parameters like ack_(highest acknowlegement received), ssthresh_, cwnd_, rtt_, t_seq_no, dupacks_ for sctp. How to get these parameters for sctp protocol? Below is the code for getting the parameters in tcp versions...Here tcpSrc is the parameter for creating connection like set regtcp [$ns create-connection TCP/Vegas $n1 TCPSink $n2 1] and then calling timeackReport $regtcp 0.025 Vegas proc timeackReport {tcpSrc interval label} { global ns frep fre qmon flow tseq oldbytesD set now [$ns now] set time [expr int (([$ns now]+$interval)/10)] $ns at [expr [$ns now]+$interval] "timeackReport $tcpSrc $interval $label" puts $label/time=[$ns now]/ack=[$tcpSrc set ack_]/ssthresh=[$tcpSrc set ssthresh_]/CongW=[$tcpSrc set cwnd_]/RTT=[$tcpSrc set rtt_]/seq=[$t$ puts $frep "time=[$ns now]/ack=[$tcpSrc set ack_]/ssthresh=[$tcpSrc set ssthresh_]/CongW=[$tcpSrc set cwnd_]/RTT=[$tcpSrc set rtt_]/seq=[$t$ puts $frep "at $now, bdepartures_=[$qmon set bdepartures_]" puts $frep "at $now, barrivals=[$qmon set barrivals_]" puts $frep "at $now, bdropss=[$qmon set bdrops_]" # puts $frep "at $now, loss=[$n2 set nlost_]" if {$now != 0} { set tseq [$tcpSrc set t_seqno_] set bytesD [ns-int64todbl $tseq] #set tag [$ns now] #puts $label/$bytesD /[$ns now]/ puts $fre "[$ns now] [$tcpSrc set ack_] [$tcpSrc set ssthresh_] [$tcpSrc set cwnd_] [$tcpSrc set rtt_] [$tcpSrc set t_seqno_] [$qmon set pdep$ set oldbytesD [expr $bytesD] Thanks, Sridhar. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 18:19:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29259 for ; Fri, 6 Feb 2004 18:19:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApFFW-0006Ya-Mv for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 18:19:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i16NJ2RK025169 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 18:19:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApFFV-0006WK-Ir; Fri, 06 Feb 2004 18:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApFEZ-00061I-N7 for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 18:18:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29133 for ; Fri, 6 Feb 2004 18:17:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApFEW-0003S8-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 18:18:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApFDa-0003Ng-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 18:17:03 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1ApFCf-0003Jw-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 18:16:05 -0500 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1ApFCU-000FUS-R9; Fri, 06 Feb 2004 23:15:54 +0000 To: tsvwg@ietf.org Cc: jon.peterson@neustar.biz, mankin@psg.com Reply-To: mankin@psg.com Date: Fri, 06 Feb 2004 15:15:53 -0800 From: Allison Mankin Message-Id: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Tsvwg] Agenda items for tsvwg at Seoul IETF? Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Hi, TSVWG folks, We're planning for TSVWG to have a meeting in Seoul. Please send your agenda items for discussion there to Jon and me. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 6 19:40:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01649 for ; Fri, 6 Feb 2004 19:40:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApGVz-0003S9-ND for tsvwg-archive@odin.ietf.org; Fri, 06 Feb 2004 19:40:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i170e7CD013242 for tsvwg-archive@odin.ietf.org; Fri, 6 Feb 2004 19:40:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApGVv-0003Qi-Qf; Fri, 06 Feb 2004 19:40:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApGV0-0003BU-Iu for tsvwg@optimus.ietf.org; Fri, 06 Feb 2004 19:39:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01600 for ; Fri, 6 Feb 2004 19:39:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApGUy-0000NL-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 19:39:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApGU3-0000KP-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 19:38:08 -0500 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 1ApGTZ-0000HL-00 for tsvwg@ietf.org; Fri, 06 Feb 2004 19:37:37 -0500 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id F07E5329B5; Fri, 6 Feb 2004 19:37:33 -0500 (EST) Received: from stimpy.eecis.udel.edu (stimpy.eecis.udel.edu [128.4.40.17]) by mail.eecis.udel.edu (Postfix) with ESMTP id 4060C329BB; Fri, 6 Feb 2004 19:37:33 -0500 (EST) Date: Fri, 6 Feb 2004 19:37:33 -0500 (EST) From: Sourabh Ladha X-X-Sender: ladha@stimpy.eecis.udel.edu To: tsvwg@ietf.org Cc: sctp-impl@external.cisco.com In-Reply-To: <200402070014.i170EbKs028386@nailgun.cisco.com> Message-ID: References: <200402070014.i170EbKs028386@nailgun.cisco.com> X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] ID: ECN Nonces for SCTP Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Dear All, Neil Spring, Randall Stewart and myself have put up a draft on how to do ECN-nonce with SCTP. You can grab a copy of the draft from - http://www.ietf.org/internet-drafts/draft-ladha-sctp-nonce-00.txt http://www.cis.udel.edu/~ladha/draft-ladha-sctp-nonce-00.txt Please direct all the comments on the tsvwg mailing list. Thanks, -Sourabh _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Feb 8 17:21:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04644 for ; Sun, 8 Feb 2004 17:21:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApxIa-0007DU-6m for tsvwg-archive@odin.ietf.org; Sun, 08 Feb 2004 17:21:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i18ML82A027736 for tsvwg-archive@odin.ietf.org; Sun, 8 Feb 2004 17:21:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApxIV-0007Cv-2X; Sun, 08 Feb 2004 17:21:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApxI8-0007Br-4N for tsvwg@optimus.ietf.org; Sun, 08 Feb 2004 17:20:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04626 for ; Sun, 8 Feb 2004 17:20:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApxI5-0006qd-00 for tsvwg@ietf.org; Sun, 08 Feb 2004 17:20:37 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApxHF-0006ln-00 for tsvwg@ietf.org; Sun, 08 Feb 2004 17:19:45 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1ApxGW-0006dw-00; Sun, 08 Feb 2004 17:19:00 -0500 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i18MIRGv007471; Sun, 8 Feb 2004 14:18:27 -0800 (PST) Received: from cisco.com (rtp-vpn1-400.cisco.com [10.82.225.144]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AQC15232; Sun, 8 Feb 2004 14:18:25 -0800 (PST) Message-ID: <4026B5B0.2050707@cisco.com> Date: Sun, 08 Feb 2004 14:18:24 -0800 From: Rajiv Raghunarayan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Juergen Schoenwaelder CC: ipv6mib@ibr.cs.tu-bs.de, ipv6@ietf.org, tsvwg@ietf.org References: <402302BA.4020000@cisco.com> <200402060855.i168t1iV015037@hansa.ibr.cs.tu-bs.de> In-Reply-To: <200402060855.i168t1iV015037@hansa.ibr.cs.tu-bs.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] Re: [ipv6mib] Discontinuity timer for TCP-MIB counters Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Juergen, Thanks for the feedback. My comments inline. Juergen Schoenwaelder wrote: >>>>>>Rajiv Raghunarayan writes: > > > Rajiv> The IESG review suggested that we provide a discontinuity timer > Rajiv> for the counters in the mib - could be via sysUpTime or a new > Rajiv> discontinuity object. But we state it either way. > > Here are my 3 thoughs on this: > > 1) So far, sysUpTime has been used by the existing TCP-MIB objects. > Introducing a new discontinuity indicator now raises the question > whether doing so breaks existing implementations. Yep. It would probably break implementations if 2) were to be an incorrect assumption for any implementation. Else, I think we shouldn't be affecting other implementations (but those case wouldn't need a separate discontinuity indicator as well!)? > > 2) Personally, I doubt that there will be many implementations where > TCP can experience discontinuities that do not also affect other > parts of the networking stack or the whole system. I suspected that, but wasn't sure. > > 3) I do see the problem that sysUpTime might be more frequently reset > as we like due to some other MIBs which do not use explicit > discontinuity indicators and experience more frequent > resets. However, the root of the problem is then really in those > MIBs, not in the TCP-MIB. (Sure, by introducing a discontinuity > indicator for the TCP-MIB we can protect against other misbehaving > MIBs - but is this going to set a precedence which at the end > requires a CLR that better every MIB module has at least one, > perhaps multiple discontinuity indicators?) Agreed. > > In the case of the TCP-MIB, I believe 1) is the killing argument. To > introduce a new discontinuity indicator changes the implicit semantics > of existing objects and would require to introduce new objects, which > I think is prohibitive. > > Conclusion: Spell out that sysUpTime is used as a discontinuity > indicator for the counters. I've modified the mib to indicate it - will submit the mib, if I do not receive any arguments to the contrary in the next couple of days. Thanks, Rajiv. > > /js > _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 9 08:50:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18637 for ; Mon, 9 Feb 2004 08:50:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqBna-0006IC-13 for tsvwg-archive@odin.ietf.org; Mon, 09 Feb 2004 08:50:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i19Do5BL024184 for tsvwg-archive@odin.ietf.org; Mon, 9 Feb 2004 08:50:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqBnX-0006Hq-7I; Mon, 09 Feb 2004 08:50:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqBmX-0006FY-M5 for tsvwg@optimus.ietf.org; Mon, 09 Feb 2004 08:49:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18459 for ; Mon, 9 Feb 2004 08:48:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqBmW-00072i-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 08:49:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqBlY-0006uD-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 08:48:01 -0500 Received: from ms1.city.ac.uk ([138.40.12.21]) by ietf-mx with esmtp (Exim 4.12) id 1AqBka-0006oH-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 08:47:01 -0500 Received: from mailswitch.city.ac.uk ([138.40.12.12] helo=mailswitch) by ms1.city.ac.uk with smtp (Exim 4.20) id 1AqBkD-0002cu-VA for tsvwg@ietf.org; Mon, 09 Feb 2004 13:46:37 +0000 Received: from lib-wlan19.city.ac.uk ([138.40.50.211] helo=WirelessLab2) by mailswitch with esmtp (Exim 3.16 #5) id 1AqBkD-0002Zg-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 13:46:37 +0000 From: "Ehsan" To: Date: Mon, 9 Feb 2004 13:45:59 -0000 Message-ID: <000001c3ef13$10273d50$d332288a@WirelessLab2> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C3EF13.10273D50" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MailScanner-Information: Please contact Computing Services for more information X-City-MailScanner: Found to be clean X-City-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=0.5, required 5, HTML_80_90 0.50) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 Subject: [Tsvwg] TCP Tahoe,Reno,Vegas Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C3EF13.10273D50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear all, I would appreciate if you can introduce me books, papers, URLs, etc that have described about Tahoe, Reno and Vegas congestion control algorithm in details. Furthermore, is there any mailing list specifically about TCP congestion control or not? Regards Ehsan ------=_NextPart_000_0001_01C3EF13.10273D50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = all,

 

I would appreciate if = you can introduce me books, papers, URLs, etc that have described about Tahoe, = Reno and Vega= s congestion control algorithm in = details.

 

Furthermore, is there = any mailing list specifically about TCP congestion control or = not?

 

Regards

 

Ehsan=

 

 

------=_NextPart_000_0001_01C3EF13.10273D50-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 9 19:52:36 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07098 for ; Mon, 9 Feb 2004 19:52:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqM8G-0007cL-0I for tsvwg-archive@odin.ietf.org; Mon, 09 Feb 2004 19:52:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1A0q7Ax029252 for tsvwg-archive@odin.ietf.org; Mon, 9 Feb 2004 19:52:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqM89-0007Zm-Gk; Mon, 09 Feb 2004 19:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqM7g-0007YO-P5 for tsvwg@optimus.ietf.org; Mon, 09 Feb 2004 19:51:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07002 for ; Mon, 9 Feb 2004 19:51:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqM7e-0003vM-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 19:51:31 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqM6b-0003mM-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 19:50:26 -0500 Received: from stewart.chicago.il.us ([66.93.186.36]) by ietf-mx with esmtp (Exim 4.12) id 1AqM5g-0003al-00 for tsvwg@ietf.org; Mon, 09 Feb 2004 19:49:28 -0500 Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1]) by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id i1A0mdO6061073; Mon, 9 Feb 2004 18:48:40 -0600 (CST) (envelope-from randall@stewart.chicago.il.us) Message-ID: <40282A63.7020508@stewart.chicago.il.us> Date: Mon, 09 Feb 2004 18:48:35 -0600 From: "Randall R. Stewart (home)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Accept-Language: en-us, en MIME-Version: 1.0 To: sridhar duggireddy CC: tsvwg@ietf.org Subject: Re: [Tsvwg] How to get configuration parameters in sctp References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit sridhar duggireddy wrote: >Hi, > > We are doing an experiment in which we want to compare various >versions of protocols like tcp Reno, Vegas, SCTP, Westwood etc. For this I >need to get the configuration parameters like ack_(highest acknowlegement >received), ssthresh_, cwnd_, rtt_, t_seq_no, dupacks_ for sctp. How to get >these parameters for sctp protocol? > Sridhar: I don't know if it will get all your values.. but the socket api I know has some of them.. take a look at draft-ietf-tsvwg-sctpsocket-07.txt And see if you can get what you want from the socket-api. If so you can find these in KAME-SCTP (for BSD), LK-SCTP (for linux) and I think Solaris and the U-of-Essen also support these fields.. Hope that helps R > Below is the code for getting the >parameters in tcp versions...Here tcpSrc is the parameter for creating >connection like >set regtcp [$ns create-connection TCP/Vegas $n1 TCPSink $n2 1] > >and then calling timeackReport $regtcp 0.025 Vegas > > >proc timeackReport {tcpSrc interval label} { > global ns frep fre qmon flow tseq oldbytesD > set now [$ns now] > set time [expr int (([$ns now]+$interval)/10)] > $ns at [expr [$ns now]+$interval] "timeackReport $tcpSrc $interval >$label" > puts $label/time=[$ns now]/ack=[$tcpSrc set ack_]/ssthresh=[$tcpSrc set >ssthresh_]/CongW=[$tcpSrc set cwnd_]/RTT=[$tcpSrc set rtt_]/seq=[$t$ > > puts $frep "time=[$ns now]/ack=[$tcpSrc set ack_]/ssthresh=[$tcpSrc set >ssthresh_]/CongW=[$tcpSrc set cwnd_]/RTT=[$tcpSrc set rtt_]/seq=[$t$ > > puts $frep "at $now, bdepartures_=[$qmon set bdepartures_]" > puts $frep "at $now, barrivals=[$qmon set barrivals_]" > puts $frep "at $now, bdropss=[$qmon set bdrops_]" ># puts $frep "at $now, loss=[$n2 set nlost_]" > >if {$now != 0} { >set tseq [$tcpSrc set t_seqno_] >set bytesD [ns-int64todbl $tseq] >#set tag [$ns now] > >#puts $label/$bytesD /[$ns now]/ >puts $fre "[$ns now] [$tcpSrc set ack_] [$tcpSrc set ssthresh_] [$tcpSrc >set cwnd_] [$tcpSrc set rtt_] [$tcpSrc set t_seqno_] [$qmon set pdep$ >set oldbytesD [expr $bytesD] > > > >Thanks, >Sridhar. > > >_______________________________________________ >tsvwg mailing list >tsvwg@ietf.org >https://www1.ietf.org/mailman/listinfo/tsvwg > > > > -- Randall R. Stewart 815-477-2127 (office) 815-342-5222 (cell phone) _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 12 16:24:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16858 for ; Thu, 12 Feb 2004 16:24:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArOJZ-0007lW-Cd for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 16:24:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CLO5Nx029850 for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 16:24:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArOJV-0007lD-FH; Thu, 12 Feb 2004 16:24:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArOIx-0007jz-Q7 for tsvwg@optimus.ietf.org; Thu, 12 Feb 2004 16:23:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16823 for ; Thu, 12 Feb 2004 16:23:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArOIu-00069s-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 16:23:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArOHz-00064t-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 16:22:28 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1ArOHM-0005v6-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 16:21:48 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 787FC77A6FE; Thu, 12 Feb 2004 16:21:19 -0500 (EST) To: tsvwg@ietf.org Cc: faber@isie.edu.cnri.reston.va.us From: Mark Allman Reply-To: mallman@icir.org Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Brown Eyed Girl Date: Thu, 12 Feb 2004 16:21:19 -0500 Message-Id: <20040212212119.787FC77A6FE@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BIZ_TLD autolearn=no version=2.60 Subject: [Tsvwg] The IESG: WG Action: TCP Maintenance and Minor Extensions (tcpm) Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Hi folks! As discussed previously, there is a new TCP WG that will be used for some current work (as sketched in the charter) and new modifications that come up for TCP. The mailing list information is included below. TCPM will meet in Korea as a split session with tsvwg (TCPM's "going away" party, if you will). Comments welcome! allman ------- Forwarded Message From: The IESG To: IETF-Announce: ; Cc: Ted Faber , Mark Allman Subject: WG Action: TCP Maintenance and Minor Extensions (tcpm) Date: Thu, 12 Feb 2004 15:34:52 -0500 A new IETF working group has been formed in the Transport Area. For additional information, please contact the Area Directors or the WG Chairs. TCP Maintenance and Minor Extensions (tcpm) - ------------------------------------------ Current Status: Active Working Group Chair(s): Ted Faber Mark Allman Transport Area Director(s): Allison Mankin Jon Peterson Transport Area Advisor: Jon Peterson Mailing Lists: General Discussion: tcpm@ietf.org To Subscribe: tcpm-request@ietf.org In Body: subscribe email_address Archive: ftp://ftp.ietf.org/ietf-mail-archive/tcpm/ Description of Working Group: TCP is currently the Internet's predominant transport protocol. To maintain TCP's utility the IETF has regularly updated both the protocol itself and the congestion control algorithms implemented by the protocol that are crucial for the stability of the Internet. These changes reflect our evolving understanding of transport protocols, congestion control and new needs presented by an ever-changing network. The TCPM WG will provide a venue within the IETF to work on these issues. The WG will serve several purposes: * The WG will mostly focus on maintenance issues (e.g., bug fixes) and modest changes to the protocol and algorithms that maintain TCP's utility. * The WG will be a venue for moving current TCP specifications along the standards track (as community energy is available for such efforts). * The WG will write a document that outlines "what is TCP". This document will be a roadmap of sorts to the various TCP specifications in the RFC series. TCPM will take a subset of the work which has been conducted in the Transport Area WG over the past several years. Specifically, some of the WG's initial work will be moved from the Transport Area WG (tsvwg). TCPM is expected to be the working group within the IETF to handle TCP changes. Proposals for additional TCP work items should be brought up within the working group. While fundamental changes to TCP or its congestion control algorithms (e.g., departure from loss-based congestion control) should be brought through TCPM, it is expected that such large changes will ultimately be handled by the Transport Area WG (tsvwg). All additional work items for TCPM will, naturally, require the approval of the Transport Services Area Area Directors and the IESG. TCP's congestion control algorithms are the model followed by alternate transports (e.g., SCTP and (in some cases) DCCP). In addition, the IETF has recently worked on several documents about algorithms that are specified for multiple protocols (e.g., TCP and SCTP) in the same document. Which WG shepherds such documents in the future will determined on a case-by-case basis. In any case, the TCPM WG will remain in close contact with other relevant WGs working on these protocols to ensure openness and stringent review from all angles. Specific Goals: * A revision of RFC 1323 based on experience and evaluation. Depending on the conclusions of the WG and the nature of the updates this document could be a candidate for Draft Standard. A current Internet-Draft has been submitted to start this process (draft-jacobson-tsvwg-1323bis-00.txt). * A "roadmap" for TCP. The protocol and associated algorithms have become spread out throughout the RFC series. This WG will issue a document that catalogs all the various TCP specifications and informational documents in the RFC series in a single location. An initial discussion (and strawman start at a list of such RFCs) has been conducted on the end2end interest list. * While there is no consensus on exactly how to deal with spurious retransmits (caused by bad RTO estimates or packet reordering) there are several proposals that will be fleshed out in this WG and likely issued as experimental documents. The current set of proposals is: draft-sarolahti-tsvwg-tcp-frto-03.txt draft-blanton-tcp-reordering-00.txt draft-bhandarkar-tcp-dcr-00.txt Goals and Milestones: Mar 04 Submit FRTO draft to IESG for publication as an Experimental RFC Mar 04 Submit Reordering Mitigation draft to IESG for publication as an Experimental RFC May 04 Submit DCR draft to IESG for publication as an Experimental RFC May 04 Submit TCP Roadmap document to IESG for publication as a Best Current Practices RFC May 04 Develop (providing editors are available) milestones for advancement to Draft Standard of identified important TCP specs (e.g. RFC 2018, 2581, 2988...) Jun 04 Submit a revision of RFC 1323 to the IESG for publication as a Proposed or Draft Standard (depending on the nature of the changes to the document) ------- End of Forwarded Message _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 12 17:16:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19413 for ; Thu, 12 Feb 2004 17:16:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArP7u-00049X-2D for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:16:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CMG5jg015943 for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:16:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArP7p-00048J-GM; Thu, 12 Feb 2004 17:16:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArP7M-00047q-3T for tsvwg@optimus.ietf.org; Thu, 12 Feb 2004 17:15:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19332 for ; Thu, 12 Feb 2004 17:15:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArP7H-0003M0-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:15:27 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArP6O-0003HY-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:14:33 -0500 Received: from gw.openss7.com ([142.179.199.224] ident=[wR+2fKJjKRb71bWUdG8SZFycgYSwQzOG]) by ietf-mx with esmtp (Exim 4.12) id 1ArP67-0003Cg-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:14:15 -0500 Received: from ns.pigworks.openss7.net (IDENT:un4sjbCZkHO8tDYLpf+t25jyjEKtcsNE@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1CMEAI22724; Thu, 12 Feb 2004 15:14:10 -0700 Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1CME9Z32413; Thu, 12 Feb 2004 15:14:09 -0700 Date: Thu, 12 Feb 2004 15:14:09 -0700 From: "Brian F. G. Bidulock" To: Mark Allman Cc: tsvwg@ietf.org, faber@isie.edu.cnri.reston.va.us Subject: Re: [Tsvwg] The IESG: WG Action: TCP Maintenance and Minor Extensions (tcpm) Message-ID: <20040212151409.A30668@openss7.org> Reply-To: bidulock@openss7.org References: <20040212212119.787FC77A6FE@guns.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040212212119.787FC77A6FE@guns.icir.org>; from mallman@icir.org on Thu, Feb 12, 2004 at 04:21:19PM -0500 Organization: http://www.openss7.org/ Dsn-Notification-To: Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1CMEAI22724 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BIZ_TLD autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Mark, Will similar work on SCTP go to tcpm? --brian On Thu, 12 Feb 2004, Mark Allman wrote: > =20 > Hi folks! >=20 > As discussed previously, there is a new TCP WG that will be used for > some current work (as sketched in the charter) and new modifications > that come up for TCP. The mailing list information is included below. >=20 > TCPM will meet in Korea as a split session with tsvwg (TCPM's "going > away" party, if you will). >=20 > Comments welcome! >=20 > allman >=20 >=20 > ------- Forwarded Message >=20 > From: The IESG > To: IETF-Announce: ; > Cc: Ted Faber , Mark Allman > Subject: WG Action: TCP Maintenance and Minor Extensions (tcpm) > Date: Thu, 12 Feb 2004 15:34:52 -0500 >=20 > A new IETF working group has been formed in the Transport Area. For ad= ditional information,=20 > please contact the Area Directors or the WG Chairs. >=20 > TCP Maintenance and Minor Extensions (tcpm) > - ------------------------------------------ >=20 > Current Status: Active Working Group >=20 > Chair(s): > Ted Faber > Mark Allman >=20 > Transport Area Director(s): > Allison Mankin > Jon Peterson >=20 > Transport Area Advisor: > Jon Peterson >=20 > Mailing Lists: > General Discussion: tcpm@ietf.org > To Subscribe: tcpm-request@ietf.org > In Body: subscribe email_address > Archive: ftp://ftp.ietf.org/ietf-mail-archive/tcpm/ >=20 > Description of Working Group: >=20 > TCP is currently the Internet's predominant transport protocol. > To maintain TCP's utility the IETF has regularly updated both > the protocol itself and the congestion control algorithms > implemented by the protocol that are crucial for the stability > of the Internet. These changes reflect our evolving > understanding of transport protocols, congestion control and new > needs presented by an ever-changing network. The TCPM WG will > provide a venue within the IETF to work on these issues. The WG > will serve several purposes: >=20 > * The WG will mostly focus on maintenance issues (e.g., bug > fixes) and modest changes to the protocol and algorithms > that maintain TCP's utility. > * The WG will be a venue for moving current TCP specifications > along the standards track (as community energy is available > for such efforts). >=20 > * The WG will write a document that outlines "what is TCP". > This document will be a roadmap of sorts to the various TCP > specifications in the RFC series. >=20 > TCPM will take a subset of the work which has been conducted in > the Transport Area WG over the past several years. > Specifically, some of the WG's initial work will be moved from > the Transport Area WG (tsvwg). >=20 > TCPM is expected to be the working group within the IETF to > handle TCP changes. Proposals for additional TCP work items > should be brought up within the working group. While > fundamental changes to TCP or its congestion control algorithms > (e.g., departure from loss-based congestion control) should be =20 > brought through TCPM, it is expected that such large changes > will ultimately be handled by the Transport Area WG (tsvwg). > All additional work items for TCPM will, naturally, require the > approval of the Transport Services Area Area Directors and the IESG.=20 >=20 > TCP's congestion control algorithms are the model followed by > alternate transports (e.g., SCTP and (in some cases) DCCP). In > addition, the IETF has recently worked on several documents > about algorithms that are specified for multiple protocols > (e.g., TCP and SCTP) in the same document. Which WG shepherds > such documents in the future will determined on a case-by-case > basis. In any case, the TCPM WG will remain in close contact > with other relevant WGs working on these protocols to ensure > openness and stringent review from all angles. >=20 > Specific Goals: >=20 > * A revision of RFC 1323 based on experience and evaluation. > Depending on the conclusions of the WG and the nature of the > updates this document could be a candidate for Draft Standard. > A current Internet-Draft has been submitted to start this > process (draft-jacobson-tsvwg-1323bis-00.txt). >=20 > * A "roadmap" for TCP. The protocol and associated algorithms > have become spread out throughout the RFC series. This WG will > issue a document that catalogs all the various TCP > specifications and informational documents in the RFC series in > a single location. An initial discussion (and strawman start at > a list of such RFCs) has been conducted on the end2end interest > list. >=20 > * While there is no consensus on exactly how to deal with spurious > retransmits (caused by bad RTO estimates or packet reordering) > there are several proposals that will be fleshed out in this WG > and likely issued as experimental documents. The current set of > proposals is: >=20 > draft-sarolahti-tsvwg-tcp-frto-03.txt > draft-blanton-tcp-reordering-00.txt=20 > draft-bhandarkar-tcp-dcr-00.txt >=20 > Goals and Milestones: >=20 > Mar 04 Submit FRTO draft to IESG for publication as an Experimental RF= C=20 > Mar 04 Submit Reordering Mitigation draft to IESG for publication as a= n Experimental RFC=20 > May 04 Submit DCR draft to IESG for publication as an Experimental RFC= =20 > May 04 Submit TCP Roadmap document to IESG for publication as a Best C= urrent Practices RFC=20 > May 04 Develop (providing editors are available) milestones for advanc= ement to Draft Standard=20 > of identified important TCP specs (e.g. RFC 2018, 2581, 2988...)=20 > Jun 04 Submit a revision of RFC 1323 to the IESG for publication as a = Proposed or Draft=20 > Standard (depending on the nature of the changes to the document)=20 >=20 > ------- End of Forwarded Message >=20 > _______________________________________________ > tsvwg mailing list > tsvwg@ietf.org > https://www1.ietf.org/mailman/listinfo/tsvwg --=20 Brian F. G. Bidulock =A6 The reasonable man adapts himself to the =A6 bidulock@openss7.org =A6 world; the unreasonable one persists in =A6 http://www.openss7.org/ =A6 trying to adapt the world to himself. =A6 =A6 Therefore all progress depends on the =A6 =A6 unreasonable man. -- George Bernard Shaw =A6 _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 12 17:33:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20346 for ; Thu, 12 Feb 2004 17:33:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPOJ-0005ZY-Nj for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:33:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CMX3OC021402 for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:33:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPOH-0005Yj-2d; Thu, 12 Feb 2004 17:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArPNq-0005Wx-8T for tsvwg@optimus.ietf.org; Thu, 12 Feb 2004 17:32:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20252 for ; Thu, 12 Feb 2004 17:32:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArPNl-0005Eg-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:32:30 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArPMo-00057N-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:31:30 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1ArPLs-0004w6-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 17:30:32 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 10B9977A6FE; Thu, 12 Feb 2004 17:30:03 -0500 (EST) To: bidulock@openss7.org From: Mark Allman Reply-To: mallman@icir.org Cc: tsvwg@ietf.org, faber@isi.edu Subject: Re: [Tsvwg] The IESG: WG Action: TCP Maintenance and Minor Extensions (tcpm) In-Reply-To: <20040212151409.A30668@openss7.org> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Brown Eyed Girl Date: Thu, 12 Feb 2004 17:30:02 -0500 Message-Id: <20040212223003.10B9977A6FE@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , > Will similar work on SCTP go to tcpm? Depends. Ted, Allison, Jon and I had a long chat about this. Some SCTP items are clearly out of scope for TCPM. For instance, specifying an SCTP option or something is a completely SCTP issue and so would stay in tsvwg. On the other hand, congestion control sorts of things are fuzzier because they likely apply to both protocols. The TCPM charter says... > TCP's congestion control algorithms are the model followed by > alternate transports (e.g., SCTP and (in some cases) DCCP). In > addition, the IETF has recently worked on several documents > about algorithms that are specified for multiple protocols > (e.g., TCP and SCTP) in the same document. Which WG shepherds > such documents in the future will determined on a case-by-case > basis. In any case, the TCPM WG will remain in close contact > with other relevant WGs working on these protocols to ensure > openness and stringent review from all angles. which gives some wiggle room in choosing a route. I think that the overlap and the fuzziness of such situations call for a case-by-case analysis. While that might not be a wholly satisfying answer I think it is the best we can do. Thanks! allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 12 19:41:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28466 for ; Thu, 12 Feb 2004 19:41:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArROB-0006lS-Sk for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 19:41:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1D0f30T025975 for tsvwg-archive@odin.ietf.org; Thu, 12 Feb 2004 19:41:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArRO9-0006kO-Hf; Thu, 12 Feb 2004 19:41:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArRNh-0006iw-F7 for tsvwg@optimus.ietf.org; Thu, 12 Feb 2004 19:40:33 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28443 for ; Thu, 12 Feb 2004 19:40:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArRNd-0003Zy-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 19:40:29 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArRMf-0003Ua-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 19:39:30 -0500 Received: from gw.openss7.com ([142.179.199.224] ident=[Cpj9tn3bsJxMCiGI6AspAZAPE8gfapXz]) by ietf-mx with esmtp (Exim 4.12) id 1ArRLn-0003QF-00 for tsvwg@ietf.org; Thu, 12 Feb 2004 19:38:35 -0500 Received: from ns.pigworks.openss7.net (IDENT:+MlXuVjnkOVUodIKG84lcsRvWc5kAJF7@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1D0cKI24885; Thu, 12 Feb 2004 17:38:20 -0700 Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1D0cJ201672; Thu, 12 Feb 2004 17:38:19 -0700 Date: Thu, 12 Feb 2004 17:38:19 -0700 From: "Brian F. G. Bidulock" To: Mark Allman Cc: tsvwg@ietf.org, faber@isi.edu Subject: Re: [Tsvwg] The IESG: WG Action: TCP Maintenance and Minor Extensions (tcpm) Message-ID: <20040212173819.A1657@openss7.org> Reply-To: bidulock@openss7.org References: <20040212151409.A30668@openss7.org> <20040212223003.10B9977A6FE@guns.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040212223003.10B9977A6FE@guns.icir.org>; from mallman@icir.org on Thu, Feb 12, 2004 at 05:30:02PM -0500 Organization: http://www.openss7.org/ Dsn-Notification-To: Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1D0cKI24885 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Mark, Sounds reasonable. Thank you for the quick answer. --brian On Thu, 12 Feb 2004, Mark Allman wrote: >=20 > > Will similar work on SCTP go to tcpm? >=20 > Depends. >=20 > Ted, Allison, Jon and I had a long chat about this. Some SCTP items ar= e > clearly out of scope for TCPM. For instance, specifying an SCTP option > or something is a completely SCTP issue and so would stay in tsvwg. On > the other hand, congestion control sorts of things are fuzzier because > they likely apply to both protocols. The TCPM charter says... >=20 > > TCP's congestion control algorithms are the model followed by > > alternate transports (e.g., SCTP and (in some cases) DCCP). In > > addition, the IETF has recently worked on several documents > > about algorithms that are specified for multiple protocols > > (e.g., TCP and SCTP) in the same document. Which WG shepherds > > such documents in the future will determined on a case-by-case > > basis. In any case, the TCPM WG will remain in close contact > > with other relevant WGs working on these protocols to ensure > > openness and stringent review from all angles. >=20 > which gives some wiggle room in choosing a route. I think that the > overlap and the fuzziness of such situations call for a case-by-case > analysis. While that might not be a wholly satisfying answer I think i= t > is the best we can do. >=20 > Thanks! >=20 > allman >=20 >=20 > -- > Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=20 Brian F. G. Bidulock =A6 The reasonable man adapts himself to the =A6 bidulock@openss7.org =A6 world; the unreasonable one persists in =A6 http://www.openss7.org/ =A6 trying to adapt the world to himself. =A6 =A6 Therefore all progress depends on the =A6 =A6 unreasonable man. -- George Bernard Shaw =A6 _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 16 17:37:40 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04445 for ; Mon, 16 Feb 2004 17:37:40 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrMX-00058t-V3 for tsvwg-archive@odin.ietf.org; Mon, 16 Feb 2004 17:37:13 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GMbDPo019721 for tsvwg-archive@odin.ietf.org; Mon, 16 Feb 2004 17:37:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrMN-000524-2w; Mon, 16 Feb 2004 17:37:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrLy-000506-Pn for tsvwg@optimus.ietf.org; Mon, 16 Feb 2004 17:36:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04379 for ; Mon, 16 Feb 2004 17:36:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsrLw-0003Sg-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:36:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsrKw-0003OV-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:35:34 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AsrKA-0003JQ-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:34:46 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2004 14:43:34 +0000 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1GMYF1m004128 for ; Mon, 16 Feb 2004 14:34:15 -0800 (PST) Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with SMTP id AQI28681; Mon, 16 Feb 2004 14:34:14 -0800 (PST) Message-Id: <6.0.3.0.2.20040216142557.05681f40@mira-sjc5-b.cisco.com > X-Sender: fred@mira-sjc5-b.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Mon, 16 Feb 2004 14:26:22 -0800 To: tsvwg@ietf.org From: Internet-Drafts@ietf.org (by way of Fred Baker ) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA, INVALID_MSGID autolearn=no version=2.60 Subject: [Tsvwg] I-D ACTION:draft-baker-tsvwg-mlpp-that-works-01.txt Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Implementing MLPP for Voice and Video in the Internet Protocol Suite Author(s) : F. Baker Filename : draft-baker-tsvwg-mlpp-that-works-01.txt Pages : 30 Date : 2004-2-16 The Defense Information Systems Agency of the United States Department of Defense, with is contractors, has proposed a service architecture for military (NATO and related agencies) telephone systems. This is called the Assured Service, and is defined in two documents: 'Architecture for Assured Service Capabilities in Voice over IP' and 'Requirements for Assured Service Capabilities in Voice over IP'. Responding to these are three documents: 'Reason Header Field for the Session Initiation Protocol', 'Extending the Session Initiation Protocol Reason Header to account for Preemption Events', 'Communications Resource Priority for the Session Initiation Protocol'. What remains to this specification is to provide a Call Admission Control procedure and a Per Hop Behavior for the data which meet the needs of this architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-baker-tsvwg-mlpp-that-works-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-baker-tsvwg-mlpp-that-works-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-baker-tsvwg-mlpp-that-works-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <2004-2-16121953.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-baker-tsvwg-mlpp-that-works-01.txt _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 16 18:24:41 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04446 for ; Mon, 16 Feb 2004 17:37:40 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrMX-00058u-Vi for tsvwg-archive@odin.ietf.org; Mon, 16 Feb 2004 17:37:13 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GMbDFC019723 for tsvwg-archive@odin.ietf.org; Mon, 16 Feb 2004 17:37:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrMP-000548-BC; Mon, 16 Feb 2004 17:37:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsrLz-00050B-Fm for tsvwg@optimus.ietf.org; Mon, 16 Feb 2004 17:36:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04382 for ; Mon, 16 Feb 2004 17:36:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsrLx-0003Sl-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:36:37 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsrKx-0003Od-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:35:35 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AsrKB-0003JQ-00 for tsvwg@ietf.org; Mon, 16 Feb 2004 17:34:47 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2004 14:43:35 +0000 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1GMYF1o004128 for ; Mon, 16 Feb 2004 14:34:17 -0800 (PST) Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with SMTP id AQI28682; Mon, 16 Feb 2004 14:34:14 -0800 (PST) Message-Id: <6.0.3.0.2.20040216142644.05533730@mira-sjc5-b.cisco.com > X-Sender: fred@mira-sjc5-b.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Mon, 16 Feb 2004 14:27:26 -0800 To: tsvwg@ietf.org From: Internet-Drafts@ietf.org (by way of Fred Baker ) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=3.7 required=5.0 tests=FORGED_MUA_EUDORA, INVALID_MSGID autolearn=no version=2.60 Subject: [Tsvwg] I-D ACTION:draft-baker-tsvwg-mlef-concerns-01.txt Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : MLEF Without Capacity Admission Does Not Satisfy MLPP Requirements Author(s) : F. Baker Filename : draft-baker-tsvwg-mlef-concerns-01.txt Pages : 21 Date : 2004-2-16 The Defense Information Systems Agency of the United States Department of Defense, with is contractors, has proposed a service architecture for military (NATO and related agencies) telephone systems. This is called the Assured Service, and is defined in two documents: 'Architecture for Assured Service Capabilities in Voice over IP' and 'Requirements for Assured Service Capabilities in Voice over IP'. Responding to these are four documents: 'Reason Header Field for the Session Initiation Protocol', 'Extending the Session Initiation Protocol Reason Header to account for Preemption Events', 'Communications Resource Priority for the Session Initiation Protocol', and the 'Multi-Level Expedited Forwarding Per Hop Behavior' (MLEF PHB). MLEF, as currently defined, has serious problems, which this draft seeks to discuss. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-baker-tsvwg-mlef-concerns-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-baker-tsvwg-mlef-concerns-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-baker-tsvwg-mlef-concerns-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-Type: text/plain Content-ID: <2004-2-16122222.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-baker-tsvwg-mlef-concerns-01.txt _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 19 16:49:44 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15368 for ; Thu, 19 Feb 2004 16:49:43 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atw2m-0004Po-B4 for tsvwg-archive@odin.ietf.org; Thu, 19 Feb 2004 16:49:16 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1JLnGpV016969 for tsvwg-archive@odin.ietf.org; Thu, 19 Feb 2004 16:49:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atw2X-0004PO-Ia; Thu, 19 Feb 2004 16:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atw22-0004Np-7S for tsvwg@optimus.ietf.org; Thu, 19 Feb 2004 16:48:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14455 for ; Thu, 19 Feb 2004 16:48:27 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Atw20-0002XA-00 for tsvwg@ietf.org; Thu, 19 Feb 2004 16:48:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atw15-0002UT-00 for tsvwg@ietf.org; Thu, 19 Feb 2004 16:47:32 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1Atw0r-0002RX-00 for tsvwg@ietf.org; Thu, 19 Feb 2004 16:47:18 -0500 Received: from pun.isi.edu (pun.isi.edu [128.9.160.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1JLlHv17259 for ; Thu, 19 Feb 2004 13:47:17 -0800 (PST) Received: from pun.isi.edu (localhost [127.0.0.1]) by pun.isi.edu (8.12.10/8.12.10) with ESMTP id i1JLlHno079792 for ; Thu, 19 Feb 2004 13:47:17 -0800 (PST) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.10/8.12.10/Submit) id i1JLlHKX079791 for tsvwg@ietf.org; Thu, 19 Feb 2004 13:47:17 -0800 (PST) (envelope-from faber) Date: Thu, 19 Feb 2004 13:47:17 -0800 From: Ted Faber To: tsvwg@ietf.org Message-ID: <20040219214717.GF79075@pun.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UTZ8bGhNySVQ9LYl" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] [faber@ISI.EDU: [tcpm] Welcome to tcpm] Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , --UTZ8bGhNySVQ9LYl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is the welcome notice to those interested in the tcpm working group, and is hopefully of some interest to people here in tsvwg as well. Please direct followups to tcpm@ietf.org . =20 Hope to see you in tcpm. ----- Forwarded message from Ted Faber ----- From: Ted Faber Date: Thu, 19 Feb 2004 13:40:06 -0800 To: tcpm@ietf.org Subject: [tcpm] Welcome to tcpm X-url: http://www.isi.edu/~faber Hi folks! Welcome to the TCPM working group. We look forward to a great working group. A few notes as we start off... * The TCPM charter is here: http://www.ietf.org/html.charters/tcpm-charter.html * TCPM will meet in Seoul. The indication has not yet made it on to the final agenda, but TCPM will split the time-slot allocated to TSV-WG (Monday; 3:30-5:30). If you have agenda items that you believe fall within TCPM please send requests to us offlist. If you have previously sent requests to Jon and Allison for TSV-WG agenda time, but you think TCPM is the more appropriate place please let us know that, too. * We really need everyone to provide solid and timely review to drafts that are posted to the TCPM list for comment. This is how things move along in the IETF and so we need a bunch of help in this area from everyone. In particular, since we are inheriting some documents from TSV-WG that are close to being ready to forward we need to get these things reviewed fairly quickly. (You'll see calls for review for individual drafts under seperate cover.) * In grepping through the I-D archives we have noted a bunch of drafts that are not on the TCPM charter but look to be within the scope of TCPM. If you are the author of such a draft and would like to think about moving it through TCPM with us that'd be great -- please send us a note. * There are two TCP documents that are staying in TSV-WG because WGLC has started in that group and introducing a move to a new group may hinder progress. This applies to the Early Retransmit i-d (draft-allman-tcp-early-rexmt-03.txt) and the Eifel Response i-d (draft-ietf-tsvwg-tcp-eifel-response-04.txt). Thanks in advance for all your help. We are looking forward to a great WG. Ted & Mark ----- End forwarded message ----- --UTZ8bGhNySVQ9LYl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFANS7laUz3f+Zf+XsRAq+AAJ4kc9U8O6hYVD5gCy9/7nSw8NsX3QCfcRCI 7FGqQd6lpU+0UokebAAmgfI= =zhFL -----END PGP SIGNATURE----- --UTZ8bGhNySVQ9LYl-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 08:48:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22154 for ; Fri, 20 Feb 2004 08:48:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuB0g-0002xe-Sw for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 08:48:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KDm6dB011367 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 08:48:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuB0d-0002wj-6G; Fri, 20 Feb 2004 08:48:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuAze-0002rM-Fp for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 08:47:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22057 for ; Fri, 20 Feb 2004 08:46:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuAzd-000178-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 08:47:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuAyb-000137-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 08:45:57 -0500 Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47]) by ietf-mx with esmtp (Exim 4.12) id 1AuAxl-00010A-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 08:45:06 -0500 Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1KDj4YG011361 for ; Fri, 20 Feb 2004 14:45:04 +0100 (MET) Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Fri, 20 Feb 2004 14:45:04 +0100 Received: from eed.ericsson.se (mailhost.eed.ericsson.se [164.48.133.33]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 166CJAHZ; Fri, 20 Feb 2004 14:45:24 +0100 Received: from EFT1701K2P109AD.ericsson.com (rac171pc.edd.ericsson.se [164.48.123.171]) by eed.ericsson.se (8.8.8p2+Sun/1.1.mit) with ESMTP id OAA20215 for ; Fri, 20 Feb 2004 14:45:02 +0100 (MET) Message-Id: <6.0.3.0.0.20040220141424.024a87b8@imap.eed.ericsson.se> X-Sender: eedrel@imap.eed.ericsson.se X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Fri, 20 Feb 2004 14:42:58 +0100 To: tsvwg@ietf.org From: Reiner Ludwig Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 20 Feb 2004 13:45:04.0383 (UTC) FILETIME=[BE82E0F0:01C3F7B7] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Better late than never ... I think this I-D should go forward. It proposes a useful algorithm that is well specified. Comments: --------- - I think you should explicitly say that conditions 2.a and 2.b, the calculation of ER_thresh, and hence the decision to fast retransmit, or not, should be executed each time a DUPACK arrives. - I think you should say something about connections that have disabled Nagle's algorithm. Do they get to use the ER algorithm, too? Minor editing nits: ------------------- - "a retransmission timer fires" > "a retransmission timer expires" - "three duplicate ACKs arrive at the sender [Jac88,RFC2581]." You should remove "Jac88" since the FR algorithm was introduced by V. Jacobson later. The reference to RFC2581 should be sufficient. - I would prefer not to see an explicit reference to the RTO minimum of 1 second. RFCs live a long life, and things like the RTO minimum can change in the future. [I hope it will change. The idea of having a fixed value as the RTO minimum is broken, but we don't need to have this discussion here ... :-)] - "in terms of bytes" > "in terms of octets" I actually don't have a strong opinion on this, but at least that would make it consistent with existing RFCs on TCP. - "the connection does support SACK Fast retransmit May be used" > "the connection does support SACK, Fast retransmit May be used" - "when ownd - SMSS bytes" > "when (ownd - SMSS) bytes" ///Reiner This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 09:06:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22592 for ; Fri, 20 Feb 2004 09:06:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuBI4-000498-9z for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 09:06:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KE649l015897 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 09:06:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuBI1-000473-3x; Fri, 20 Feb 2004 09:06:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuBHI-00044o-Pp for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 09:05:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22550 for ; Fri, 20 Feb 2004 09:05:13 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuBHH-0002Pz-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 09:05:15 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuBGF-0002JK-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 09:04:11 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1AuBFa-0002DO-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 09:03:30 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 59ED677A6D4; Fri, 20 Feb 2004 09:02:59 -0500 (EST) To: Reiner Ludwig From: Mark Allman Reply-To: mallman@icir.org Cc: tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 In-Reply-To: <6.0.3.0.0.20040220141424.024a87b8@imap.eed.ericsson.se> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: King of the Hill Date: Fri, 20 Feb 2004 09:02:59 -0500 Message-Id: <20040220140259.59ED677A6D4@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Reiner- Good comments, all. Thanks! I'll work them into a new rev. > I think you should say something about connections that have > disabled Nagle's algorithm. Do they get to use the ER algorithm, > too? Hm. Good catch. But, what to do? On the one hand, one could argue that avoiding the hefty RTO timer is good for these connections because they are likely highly interactive. On the other hand, they may well have plenty of outstanding packets to trip fast retransmit and not need early retransmit. And, further, it is difficult to easily assess whether they have enough outstanding data to trigger fast retransmit. In general, a better test for ER is whether the connection has more than 3 packets outstanding. But, we fudge that based on the number of bytes since TCP works in terms of bytes and would have to keep more (rich) state if it were to track the number of packets outstanding. I guess my inclination is to punt and say you can't use ER when Nagle is enabled. If a connection has enough data in flight to make the ER_thresh ((ownd/SMSS) - 1) calculation meaningful and is using Nagle than likely there is enough data in flight to trigger fast retransmit (or, Nagle is being used spuriously). Does that sound reasonable to folks? Thanks! allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 11:14:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00320 for ; Fri, 20 Feb 2004 11:14:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDHx-0005fK-6s for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:14:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KGE5q8021765 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:14:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDHt-0005eZ-Sa; Fri, 20 Feb 2004 11:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDH6-0005ak-N9 for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 11:13:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00286 for ; Fri, 20 Feb 2004 11:13:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuDH5-0004u0-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:13:11 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuDGC-0004q0-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:12:16 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AuDFi-0004lP-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:11:46 -0500 Received: from isi.edu (lsanca1-ar42-4-61-171-207.lsanca1.dsl-verizon.net [4.61.171.207]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1KGBav20889; Fri, 20 Feb 2004 08:11:36 -0800 (PST) Message-ID: <403631B9.7010705@isi.edu> Date: Fri, 20 Feb 2004 08:11:37 -0800 From: Joe Touch User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mallman@icir.org CC: Reiner Ludwig , tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 References: <20040220140259.59ED677A6D4@guns.icir.org> In-Reply-To: <20040220140259.59ED677A6D4@guns.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Mark Allman wrote: > Reiner- > > Good comments, all. Thanks! I'll work them into a new rev. > > >> I think you should say something about connections that have >> disabled Nagle's algorithm. Do they get to use the ER algorithm, >> too? > > > Hm. Good catch. > > But, what to do? On the one hand, one could argue that avoiding the > hefty RTO timer is good for these connections because they are likely > highly interactive. On the other hand, they may well have plenty of > outstanding packets to trip fast retransmit and not need early > retransmit. And, further, it is difficult to easily assess whether they > have enough outstanding data to trigger fast retransmit. In general, a > better test for ER is whether the connection has more than 3 packets > outstanding. But, we fudge that based on the number of bytes since TCP > works in terms of bytes and would have to keep more (rich) state if it > were to track the number of packets outstanding. That sounds like an invitation for feature interaction. It's never possible to know the number of packets TCP actually sends from the number of bytes outstanding, Nagle on or off. What happens when it's 1-off? or more? presumably it errs on the side of caution, and does nothing? In that case, at what point can a TCP implementation _know_ it can act if it doesn't keep track of the actual packets sent? Joe > I guess my inclination is to punt and say you can't use ER when Nagle is > enabled. If a connection has enough data in flight to make the > ER_thresh ((ownd/SMSS) - 1) calculation meaningful and is using Nagle > than likely there is enough data in flight to trigger fast retransmit > (or, Nagle is being used spuriously). > > Does that sound reasonable to folks? > > Thanks! > > allman > > > -- > Mark Allman -- ICIR -- http://www.icir.org/mallman/ > > > _______________________________________________ > tsvwg mailing list > tsvwg@ietf.org > https://www1.ietf.org/mailman/listinfo/tsvwg _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 11:22:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00527 for ; Fri, 20 Feb 2004 11:22:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDPg-00061c-G1 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:22:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KGM4Nl023117 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:22:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDPd-0005zy-Fb; Fri, 20 Feb 2004 11:22:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDOg-0005zM-Dw for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 11:21:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00477 for ; Fri, 20 Feb 2004 11:20:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuDOf-0005N3-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:21:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuDNj-0005Kj-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:20:04 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1AuDNK-0005HR-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:19:38 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id D69BF77A6D4; Fri, 20 Feb 2004 11:19:05 -0500 (EST) To: Joe Touch From: Mark Allman Reply-To: mallman@icir.org Cc: Reiner Ludwig , tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 In-Reply-To: <403631B9.7010705@isi.edu> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: King of the Hill Date: Fri, 20 Feb 2004 11:19:05 -0500 Message-Id: <20040220161905.D69BF77A6D4@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , > > In general, a better test for ER is whether the connection has more > > than 3 packets outstanding. But, we fudge that based on the number > > of bytes since TCP works in terms of bytes and would have to keep > > more (rich) state if it were to track the number of packets > > outstanding. > > That sounds like an invitation for feature interaction. It's never > possible to know the number of packets TCP actually sends from the > number of bytes outstanding, Nagle on or off. Right. I think we're agreeing here. I was terse this morning. Let me try again... We *could* require a TCP that wants to use ER to try to maintain a count of the number of packets in the network. In most cases, it's not that hard to keep enough state to determine this. But, we can all draw up cases when it is not so easy (retransmits that do not fall along the exact packet boundaries of the original transmissions come to mind). In some sense, this would be the ideal for ER. On the other hand, that's a whole lot of work and probably not worth the payoff. And, as you note -- could we cause interactions that we do not forsee and could be ugly. A path that sounds good to me is to say if you use Nagle then you can't use ER because assessing the number of packets in the network is non-trivial. And, we might note that if someone wants to hash out a scheme to use ER with Nagle then that is fine as future work. Is that a reasonable path forward? Thanks! allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 11:26:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00632 for ; Fri, 20 Feb 2004 11:26:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDTW-0006nq-Sm for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:26:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KGQ2b1026101 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:26:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDTV-0006lt-8p; Fri, 20 Feb 2004 11:26:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDSc-0006LT-7u for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 11:25:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00600 for ; Fri, 20 Feb 2004 11:25:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuDSb-0005Xg-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:25:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuDRY-0005Tq-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:24:01 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AuDQr-0005RI-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:23:17 -0500 Received: from isi.edu (lsanca1-ar42-4-61-171-207.lsanca1.dsl-verizon.net [4.61.171.207]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1KGNDv07117; Fri, 20 Feb 2004 08:23:13 -0800 (PST) Message-ID: <40363472.1090109@isi.edu> Date: Fri, 20 Feb 2004 08:23:14 -0800 From: Joe Touch User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mallman@icir.org CC: Reiner Ludwig , tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 References: <20040220161905.D69BF77A6D4@guns.icir.org> In-Reply-To: <20040220161905.D69BF77A6D4@guns.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Mark Allman wrote: >>>In general, a better test for ER is whether the connection has more >>>than 3 packets outstanding. But, we fudge that based on the number >>>of bytes since TCP works in terms of bytes and would have to keep >>>more (rich) state if it were to track the number of packets >>>outstanding. >> >>That sounds like an invitation for feature interaction. It's never >>possible to know the number of packets TCP actually sends from the >>number of bytes outstanding, Nagle on or off. > > Right. I think we're agreeing here. I was terse this morning. Let me > try again... We *could* require a TCP that wants to use ER to try to > maintain a count of the number of packets in the network. In most > cases, it's not that hard to keep enough state to determine this. But, > we can all draw up cases when it is not so easy (retransmits that do not > fall along the exact packet boundaries of the original transmissions > come to mind). In some sense, this would be the ideal for ER. On the > other hand, that's a whole lot of work and probably not worth the > payoff. And, as you note -- could we cause interactions that we do not > forsee and could be ugly. > > A path that sounds good to me is to say if you use Nagle then you can't > use ER because assessing the number of packets in the network is > non-trivial. And, we might note that if someone wants to hash out a > scheme to use ER with Nagle then that is fine as future work. > > Is that a reasonable path forward? I'm equally worried about ER without Nagle, though. I.e., the question is: - can you _ever_ get away with not counting actual packets sent? Joe ... _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 11:32:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00840 for ; Fri, 20 Feb 2004 11:32:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDZK-0007S1-6U for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:32:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KGW2Rq028609 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:32:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDZJ-0007RB-7o; Fri, 20 Feb 2004 11:32:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDZH-0007Qu-AZ for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 11:31:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00811 for ; Fri, 20 Feb 2004 11:31:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuDZG-00060H-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:31:58 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuDYJ-0005vS-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:30:59 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1AuDXL-0005ok-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:29:59 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id D9D1277A6D4; Fri, 20 Feb 2004 11:29:28 -0500 (EST) To: Joe Touch From: Mark Allman Reply-To: mallman@icir.org Cc: Reiner Ludwig , tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 In-Reply-To: <40363472.1090109@isi.edu> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: King of the Hill Date: Fri, 20 Feb 2004 11:29:28 -0500 Message-Id: <20040220162928.D9D1277A6D4@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Joe- > I'm equally worried about ER without Nagle, though. I.e., the question > is: > - can you _ever_ get away with not counting actual packets sent? Ah. To flip this around: What in the draft concerns you? What makes you think that we did not propose a scheme that works without counting packets? (Sorry... I might work through all the possibilities, but I am way busy with a deadline today. So, I am trying to cut to the chase of what you're getting at here. I.e., lets focus on the draft and not start the discussion from scratch.) Thanks, allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 11:49:20 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01431 for ; Fri, 20 Feb 2004 11:49:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDop-0000RE-FS for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:48:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KGm3GT001642 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 11:48:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDon-0000PC-4c; Fri, 20 Feb 2004 11:48:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuDnp-0000N1-Ox for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 11:47:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01378 for ; Fri, 20 Feb 2004 11:46:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuDno-0006yy-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:47:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuDmu-0006vd-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:46:05 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AuDmY-0006sm-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 11:45:42 -0500 Received: from isi.edu (lsanca1-ar42-4-61-171-207.lsanca1.dsl-verizon.net [4.61.171.207]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1KGjav29731; Fri, 20 Feb 2004 08:45:36 -0800 (PST) Message-ID: <403639B0.5050905@isi.edu> Date: Fri, 20 Feb 2004 08:45:36 -0800 From: Joe Touch User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mallman@icir.org CC: Reiner Ludwig , tsvwg@ietf.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 References: <20040220162928.D9D1277A6D4@guns.icir.org> In-Reply-To: <20040220162928.D9D1277A6D4@guns.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Mark Allman wrote: > Joe- > > >>I'm equally worried about ER without Nagle, though. I.e., the question >>is: >> - can you _ever_ get away with not counting actual packets sent? > > > Ah. > > To flip this around: What in the draft concerns you? What makes you > think that we did not propose a scheme that works without counting > packets? Basically, it's exactly the concern that Nagle would affect it at all ;-) I'll dig through and see if there are specifics... > (Sorry... I might work through all the possibilities, but I am way busy > with a deadline today. So, I am trying to cut to the chase of what > you're getting at here. I.e., lets focus on the draft and not start the > discussion from scratch.) > > Thanks, > allman > > > -- > Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 12:48:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03660 for ; Fri, 20 Feb 2004 12:48:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEku-0005wY-2V for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 12:48:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KHm4Cf022807 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 12:48:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEkr-0005vJ-AV; Fri, 20 Feb 2004 12:48:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuEkK-0005qN-L2 for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 12:47:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03538 for ; Fri, 20 Feb 2004 12:47:24 -0500 (EST) From: loretosa@vodafone.it Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuEkI-000340-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 12:47:26 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuEjK-0002xd-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 12:46:27 -0500 Received: from [194.185.97.41] (helo=gsp07-c21d5.vodafone.it) by ietf-mx with esmtp (Exim 4.12) id 1AuEil-0002ow-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 12:45:52 -0500 Received: from vodafone.it (127.0.0.1) by gsp07-c21d5.vodafone.it (NPlex 6.0.021C4.14) id 4033C835000006A2 for tsvwg@ietf.org; Fri, 20 Feb 2004 13:34:15 +0100 Date: Fri, 20 Feb 2004 13:34:13 +0100 Message-Id: MIME-Version: 1.0 Message-Context: text-message Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: tsvwg@ietf.org X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Tsvwg] SCTP and mobility Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi all, I'd like to know something about SCTP and mobility. I've foun= d some draft on SCTP and Mobile IP and some other study. Can someone t= ry to summarize where the research is ? I'd like receive some links or p= apers as well. regards Salvatore Loreto _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Feb 20 14:14:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07388 for ; Fri, 20 Feb 2004 14:14:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG68-0005zm-3y for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 14:14:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KJE4tT023006 for tsvwg-archive@odin.ietf.org; Fri, 20 Feb 2004 14:14:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG64-0005xc-N4; Fri, 20 Feb 2004 14:14:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG5C-0005qd-Je for tsvwg@optimus.ietf.org; Fri, 20 Feb 2004 14:13:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07283 for ; Fri, 20 Feb 2004 14:13:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuG5A-00013J-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 14:13:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuG4K-0000z0-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 14:12:12 -0500 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1AuG3J-0000um-00 for tsvwg@ietf.org; Fri, 20 Feb 2004 14:11:09 -0500 Received: from [10.0.1.2] (p5089FBAF.dip.t-dialin.net [80.137.251.175]) by mail-n.franken.de (Postfix) with ESMTP id EA3652465C; Fri, 20 Feb 2004 20:09:34 +0100 (CET) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2CB16218-63D8-11D8-87CA-000A95C37894@lurchi.franken.de> Content-Transfer-Encoding: 7bit Cc: tsvwg@ietf.org From: Michael Tuexen Subject: Re: [Tsvwg] SCTP and mobility Date: Fri, 20 Feb 2004 20:08:32 +0100 To: loretosa@vodafone.it X-Mailer: Apple Mail (2.612) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Salvatore, there are some papers about Transport Layer Mobility which discuss the possibilities / restrictions of that. DCCP also provides a method to change the transport address during the lifetime of a DCCP conversation. I think there is no need for other protocol developments, it is more how this works together with other protocols. Please note that before finishing the work on AddIP we are working on a method to secure the ASCONF chunk. The first step is SCTP-AUTH, but it will be extended in the next revision by using purpose based keys. Best regards Michael On 20. Feb 2004, at 13:34 Uhr, loretosa@vodafone.it wrote: > Hi all, > > I'd like to know something about SCTP and mobility. > I've found some draft on SCTP and Mobile IP and some other study. > > Can someone try to summarize where the research is ? > I'd like receive some links or papers as well. > > regards > Salvatore Loreto > > > _______________________________________________ > tsvwg mailing list > tsvwg@ietf.org > https://www1.ietf.org/mailman/listinfo/tsvwg > _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Feb 22 17:35:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11635 for ; Sun, 22 Feb 2004 17:35:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Av2Bn-0003Ig-Rg for tsvwg-archive@odin.ietf.org; Sun, 22 Feb 2004 17:35:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1MMZ73a012657 for tsvwg-archive@odin.ietf.org; Sun, 22 Feb 2004 17:35:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Av2Bi-0003H1-GK; Sun, 22 Feb 2004 17:35:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Av2BP-0003Fw-4U for tsvwg@optimus.ietf.org; Sun, 22 Feb 2004 17:34:43 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11620 for ; Sun, 22 Feb 2004 17:34:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Av2BM-0007Pb-00 for tsvwg@ietf.org; Sun, 22 Feb 2004 17:34:40 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Av2AP-0007Mn-00 for tsvwg@ietf.org; Sun, 22 Feb 2004 17:33:42 -0500 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net ([68.76.113.50] helo=guns.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1Av29W-0007Hh-00 for tsvwg@ietf.org; Sun, 22 Feb 2004 17:32:46 -0500 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id BA49B77A71D; Sun, 22 Feb 2004 17:32:15 -0500 (EST) To: Reiner Ludwig , tsvwg@ietf.org From: Mark Allman Reply-To: mallman@icir.org Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 In-Reply-To: <20040220140259.59ED677A6D4@guns.icir.org> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Boys of Summer Date: Sun, 22 Feb 2004 17:32:15 -0500 Message-Id: <20040222223215.BA49B77A71D@guns.icir.org> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , (typing too fast) > I guess my inclination is to punt and say you can't use ER when Nagle > is enabled. If a connection has enough data in flight to make the > ER_thresh ((ownd/SMSS) - 1) calculation meaningful and is using Nagle > than likely there is enough data in flight to trigger fast retransmit > (or, Nagle is being used spuriously). > > Does that sound reasonable to folks? By this I meant: I guess my inclination is to punt and say you can't use ER when Nagle is **disabled**. allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 02:25:37 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11220 for ; Mon, 23 Feb 2004 02:25:37 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvASj-0004HN-4Q for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 02:25:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1N7P805016394 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 02:25:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvASd-0004EF-Cs; Mon, 23 Feb 2004 02:25:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvARk-00041v-GB for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 02:24:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11084 for ; Mon, 23 Feb 2004 02:24:05 -0500 (EST) From: loretosa@vodafone.it Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvARg-0000Z8-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:24:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvAQk-0000VX-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:23:07 -0500 Received: from [194.185.97.41] (helo=gsp07-c21d5.vodafone.it) by ietf-mx with esmtp (Exim 4.12) id 1AvAQH-0000R5-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:22:37 -0500 Received: from vodafone.it (127.0.0.1) by gsp07-c21d5.vodafone.it (NPlex 6.0.021C4.14) id 4033C83500000FA7; Mon, 23 Feb 2004 07:56:06 +0100 Date: Mon, 23 Feb 2004 07:56:05 +0100 Message-Id: MIME-Version: 1.0 Message-Context: text-message Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Michael.Tuexen@lurchi.franken.de Cc: tsvwg@ietf.org X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Tsvwg] again SCTP and mobility Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi Michael, I agree with you when you say there is no need for other p= rotocol development. I think the mobility at Transport Layer is a very = ineresting issue, much more interesting than MobileIP (at application La= yer) also if Mobile IP will be used in the new US Telephone Mobile netwo= rk (CDMA2000) I don't know if you know it. Anyway, I know very little= DCCP and at present I'm not interested to it. About SCTP can you send= me some papers about your final work on AddIP ??? and also same link on= what you think it's important I've to read for a clear idea about the = mobility ad trastport level. thank you in advance Salvatore > = Hi Salvatore, > > there are some papers about Transport Layer Mobility= which > discuss the possibilities / restrictions of that. DCCP also > = provides a method to change the transport address during the > lifetime = of a DCCP conversation. I think there is no need for > other protocol de= velopments, it is more how this works together > with other protocols. = > > Please note that before finishing the work on AddIP we are working= > on a method to secure the ASCONF chunk. The first step is SCTP-AUTH, = > but it will be extended in the next revision by using purpose based > = keys. > > Best regards > Michael > > > On 20. Feb 2004, at 13:34= Uhr, loretosa@vodafone.it wrote: > > > Hi all, > > > > I'd like to = know something about SCTP and mobility. > > I've found some draft on SCT= P and Mobile IP and some other study. > > > > Can someone try to summar= ize where the research is ? > > I'd like receive some links or papers as= well. > > > > regards > > Salvatore Loreto > > > > > > ___________= ____________________________________ > > tsvwg mailing list > > tsvwg@i= etf.org > > https://www1.ietf.org/mailman/listinfo/tsvwg > > > > >= _______________________________________________ > tsvwg mailing list >= tsvwg@ietf.org > https://www1.ietf.org/mailman/listinfo/tsvwg > _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 02:56:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12329 for ; Mon, 23 Feb 2004 02:56:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvAwf-0007vu-5N for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 02:56:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1N7u5RW030421 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 02:56:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvAwd-0007uC-Kf; Mon, 23 Feb 2004 02:56:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvAvq-0007sd-TA for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 02:55:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12319 for ; Mon, 23 Feb 2004 02:55:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvAvn-0002dH-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:55:11 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvAuq-0002ZT-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:54:13 -0500 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 1AvAuX-0002V7-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 02:53:53 -0500 Received: from LocalHost (sjkoh.etri.re.kr [129.254.112.15]) by pec.etri.re.kr (8.12.10/8.12.10) with SMTP id i1N89mfM019617; Mon, 23 Feb 2004 17:09:48 +0900 (KST) Message-ID: <004401c3f9e2$1b6ed7c0$0f70fe81@LocalHost> From: "Seok J. Koh" To: , Cc: References: Subject: Re: [Tsvwg] again SCTP and mobility Date: Mon, 23 Feb 2004 16:53:21 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit > Anyway, I know very little DCCP and at present I'm not interested to it. > > About SCTP can you send me some papers about your final work on AddIP ??? > and also same link on what you think it's important I've to read for a > clear idea about the mobility ad trastport level. > For this purpose, you might be interested in reading the following I-Ds: http://www.ietf.org/internet-drafts/draft-sjkoh-sctp-mobility-03.txt http://www.ietf.org/internet-drafts/draft-sjkoh-mobile-sctp-mobileip-03.txt We are now preparing some technical papers on mSCTP, which will address how to deal with the mSCTP handover with the ADD-IP extension. Hope to let you be informed about that later. Seok J. Koh _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 07:11:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21178 for ; Mon, 23 Feb 2004 07:11:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvEvS-00017Q-7o for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 07:11:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NCB68A004278 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 07:11:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvEvO-000161-AJ; Mon, 23 Feb 2004 07:11:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvEuY-000158-GD for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 07:10:10 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21138 for ; Mon, 23 Feb 2004 07:10:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvEuU-00044B-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 07:10:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvEtW-00040l-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 07:09:07 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AvEsY-0003wx-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 07:08:06 -0500 Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NC87K12638 for ; Mon, 23 Feb 2004 14:08:07 +0200 (EET) X-Scanned: Mon, 23 Feb 2004 14:07:58 +0200 Nokia Message Protector V1.3.13 2004020314 - RELEASE Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i1NC7w8t004109 for ; Mon, 23 Feb 2004 14:07:58 +0200 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 003tGo5y; Mon, 23 Feb 2004 14:07:57 EET Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i1NC7u725274 for ; Mon, 23 Feb 2004 14:07:56 +0200 (EET) Received: from siddha.research.nokia.com ([172.21.40.117]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 23 Feb 2004 14:07:55 +0200 From: Pasi Sarolahti To: tsvwg@ietf.org Content-Type: text/plain Organization: Nokia Research Center Message-Id: <1077538074.31444.44.camel@siddha.research.nokia.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 23 Feb 2004 14:07:55 +0200 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Feb 2004 12:07:55.0502 (UTC) FILETIME=[AB7778E0:01C3FA05] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] New version of F-RTO draft Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi all, We submitted a revision of F-RTO draft ("F-RTO: An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and SCTP", draft-ietf-tsvwg-tcp-frto-01.txt) under the tsvwg last week. The draft will be moved under the tcpm wg, and we will resubmit it with a new name once the draft submission is opened again after Seoul IETF. We think the draft is ready for WG last call, so please read the draft and let us know of any comments you may have. The best place for further discussion on this draft will be under the tcpm mailing list. There haven't been much changes on the draft recently. Between draft-ietf-tsvwg-tcp-frto-00.txt (Oct '03) and draft-ietf-tsvwg-tcp-frto-01.txt (Feb '04) the main changes were: - A number of editorial changes to make the draft more readable - Rewrote parts of section 4: "Taking Actions after Detecting Spurious RTO". It earlier listed three examples for responding to spurious retransmission timeout. Those were removed, because they weren't up to date with the current versions of refered response algorithms, and we did not want to keep updating the section in case there are any future changes on the algorithms. Therefore we now briefly list the known response algorithms and give references to the I-Ds and papers that discuss responding to spurious timeout. And to give some additional context for reviewing the draft, the main changes in the previous update from draft-sarolahti-tsvwg-tcp-frto-04.txt (Jun '03) to draft-ietf-tsvwg-tcp-frto-00.txt were: - Made the algorithm description more compact by moving much of the explaining text out of the algorithm definition. - Added section 5. "SCTP Considerations" that discusses applying the F-RTO algorithm with SCTP protocol. - Added a requirement for SACK-based F-RTO algorithm that it would not be applied when earlier loss recovery is underway. This made it possible to simplify the algorithm, especially since the usefulness of detecting spurious RTO under existing loss recovery can be argued. However, we added Appendix B that discusses this topic. - Did some editing on examples with different scenarios in Appendix A to make it more understandable and readable. Thanks to all who gave us feedback on the topics above! - Pasi & Markku _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 15:11:34 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16642 for ; Mon, 23 Feb 2004 15:11:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMPz-0003Cw-U5 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:11:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NKB7ep012303 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:11:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMPu-00039l-Rv; Mon, 23 Feb 2004 15:11:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMPM-0002qb-S7 for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 15:10:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16498 for ; Mon, 23 Feb 2004 15:10:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvMPJ-0006wd-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:10:25 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvMOR-0006tN-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:09:31 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AvMO5-0006pz-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:09:09 -0500 Received: from zbl6c012.us.nortel.com (zbl6c012.corpeast.baynetworks.com [132.245.205.62]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1NK8bC02613 for ; Mon, 23 Feb 2004 15:08:38 -0500 (EST) Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com [132.245.205.52]) by zbl6c012.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1F3PA0FL; Mon, 23 Feb 2004 15:08:36 -0500 Received: from tweedy.NortelNetworks.com (tweedy.engeast.baynetworks.com [192.32.135.156]) by zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D8262MVQ; Mon, 23 Feb 2004 15:08:36 -0500 Message-Id: <6.0.1.1.0.20040223150800.0374b818@zbl6c002.corpeast.baynetworks.com> X-Sender: khchan@zbl6c002.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 23 Feb 2004 15:08:34 -0500 To: tsvwg@ietf.org From: Internet-Drafts@ietf.org (by way of Kwok Ho Chan ) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] I-D ACTION:draft-baker-diffserv-basic-classes-02.txt Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Configuration Guidelines for DiffServ Service Classes Author(s) : F. Baker Filename : draft-baker-diffserv-basic-classes-02.txt Pages : 41 Date : 2004-2-16 This paper summarizes the recommended correlation between service classes and their usage, with references to their corresponding recommended Differentiated Service Code Points (DSCP), traffic conditioners, Per-Hop Behaviors (PHB) and Active Queue Management (AQM) mechanisms. There is no intrinsic requirement that particular DSCPs, traffic conditioner PHBs and AQM be used for a certain service class, but as a policy it is useful that they be applied consistently across the network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-baker-diffserv-basic-classes-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-baker-diffserv-basic-classes-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-2-16124347.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-baker-diffserv-basic-classes-02.txt _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 15:13:28 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16865 for ; Mon, 23 Feb 2004 15:13:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMRo-0004Kz-8n for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:13:00 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NKD0Sk016641 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:13:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMRn-0004KJ-SR; Mon, 23 Feb 2004 15:12:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMRL-0004D8-D6 for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 15:12:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16745 for ; Mon, 23 Feb 2004 15:12:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvMRK-00075l-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:12:30 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvMQZ-00071R-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:11:43 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AvMPn-0006wY-00 for tsvwg@ietf.org; Mon, 23 Feb 2004 15:10:55 -0500 Received: from zbl6c012.us.nortel.com (zbl6c012.corpeast.baynetworks.com [132.245.205.62]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1NKAOC02887 for ; Mon, 23 Feb 2004 15:10:24 -0500 (EST) Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com [132.245.205.52]) by zbl6c012.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1F3PA0H2; Mon, 23 Feb 2004 15:10:23 -0500 Received: from tweedy.NortelNetworks.com (tweedy.engeast.baynetworks.com [192.32.135.156]) by zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id D8262MV4; Mon, 23 Feb 2004 15:10:22 -0500 Message-Id: <6.0.1.1.0.20040223151008.037382d8@zbl6c002.corpeast.baynetworks.com> X-Sender: khchan@zbl6c002.corpeast.baynetworks.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 23 Feb 2004 15:10:21 -0500 To: tsvwg@ietf.org From: Internet-Drafts@ietf.org (by way of Kwok Ho Chan ) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] I-D ACTION:draft-babiarz-tsvwg-rtecn-00.txt Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Congestion Notification Process for Real-Time Traffic Author(s) : J. Babiarz Filename : draft-babiarz-tsvwg-rtecn-00.txt Pages : 11 Date : 2004-2-6 This memo specifies the incorporation of Explicit Congestion Notifications (ECN) for real-time flows that use UDP such as voice, video conferencing and multimedia streaming. Defined is the marking of the two ECN bits in the IP header and the requirements put on routers that are configured to provide the ECN marking capability for real-time UDP flows. Also, an example is provided showing how ECN for real-time UDP flows can be used for admission control of VoIP flows. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-babiarz-tsvwg-rtecn-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-babiarz-tsvwg-rtecn-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-babiarz-tsvwg-rtecn-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-2-6155626.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-babiarz-tsvwg-rtecn-00.txt _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Feb 23 15:14:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17014 for ; Mon, 23 Feb 2004 15:14:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMSn-0004h6-RU for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:14:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1NKE1NP018016 for tsvwg-archive@odin.ietf.org; Mon, 23 Feb 2004 15:14:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMSn-0004gP-IE; Mon, 23 Feb 2004 15:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvMSO-0004Z3-Tr for tsvwg@optimus.ietf.org; Mon, 23 Feb 2004 15:13:36 -0500 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16896 for ; Mon, 23 Feb 2004 15:13:34 -0500 (EST) Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1AvMRu-0004Pi-Fh; Mon, 23 Feb 2004 15:13:06 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Mon, 23 Feb 2004 15:13:06 -0500 Subject: [Tsvwg] Protocol Action: 'SCTP Partial Reliability Extension' to Proposed Standard Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , The IESG has approved the following document: - 'SCTP Partial Reliability Extension ' as a Proposed Standard This document is the product of the Transport Area Working Group. The IESG contact persons are Jon Peterson and Allison Mankin. Technical Summary PR-SCTP provides an enhancement to the Stream Control Transmission Protocol (SCTP) that allows an SCTP endpoint to signal to its peer that it should mov the cumulative ack point forward. This allows SCTP to provides its users (upper layer protocols) with a partially reliable transport service. By informing a peer that it should no longer expect to receive one or more DATA chunks, SCTP endpoints can enforce their own rules governing retransmission of data. One potential application of this, which is described in the document, is a "timed reliability" service that specifies a maximum duration of time for which retransmission should be attempted. Working Group Summary The TSVWG working group supported the advancement of this document, and substantial review was performed by participants in the WG. Protocol Quality This document was reviewed for the IESG by Jon Peterson. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 06:34:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11474 for ; Wed, 25 Feb 2004 06:34:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvxIi-0007iH-GB for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 06:34:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PBY4Bw029607 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 06:34:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvxIf-0007hQ-F5; Wed, 25 Feb 2004 06:34:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvxIQ-0007gy-FT for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 06:33:46 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11446 for ; Wed, 25 Feb 2004 06:33:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvxIM-0003wx-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 06:33:42 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvxHR-0003rN-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 06:32:45 -0500 Received: from eagle.ericsson.se ([193.180.251.53]) by ietf-mx with esmtp (Exim 4.12) id 1AvxGc-0003mO-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 06:31:54 -0500 Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i1PBVtAh015483 for ; Wed, 25 Feb 2004 12:31:55 +0100 Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0); Wed, 25 Feb 2004 12:31:55 +0100 Received: from eed.ericsson.se (mailhost.eed.ericsson.se [164.48.133.33]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id FSKYNJPR; Wed, 25 Feb 2004 12:32:09 +0100 Received: from EFT1701K2P109AD.ericsson.com (dhcp5-48.eed.ericsson.se [164.48.135.48]) by eed.ericsson.se (8.8.8p2+Sun/1.1.mit) with ESMTP id MAA18071; Wed, 25 Feb 2004 12:31:53 +0100 (MET) Message-Id: <6.0.3.0.0.20040225123049.025270e0@imap.eed.ericsson.se> X-Sender: eedrel@imap.eed.ericsson.se X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 25 Feb 2004 12:31:53 +0100 To: mallman@icir.org From: Reiner Ludwig Subject: Re: [Tsvwg] WGLC on draft-allman-tcp-early-rexmt-03 Cc: tsvwg@ietf.org In-Reply-To: <20040222223215.BA49B77A71D@guns.icir.org> References: <20040220140259.59ED677A6D4@guns.icir.org> <20040222223215.BA49B77A71D@guns.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 25 Feb 2004 11:31:55.0046 (UTC) FILETIME=[F88F8C60:01C3FB92] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , At 23:32 22.02.2004, Mark Allman wrote: >By this I meant: I guess my inclination is to punt and say you can't use >ER when Nagle is **disabled**. I think that would be a good way forward. ///Reiner This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 07:40:38 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14131 for ; Wed, 25 Feb 2004 07:40:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvyKe-0004wz-TZ for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 07:40:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PCe87V019023 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 07:40:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvyKZ-0004wR-AP; Wed, 25 Feb 2004 07:40:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AvyKG-0004uc-98 for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 07:39:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14092 for ; Wed, 25 Feb 2004 07:39:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AvyKF-0002lK-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 07:39:43 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AvyJQ-0002gD-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 07:38:52 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx with esmtp (Exim 4.12) id 1AvyIe-0002UU-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 07:38:04 -0500 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e31.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i1PCbX5w509778 for ; Wed, 25 Feb 2004 07:37:33 -0500 Received: from d03nm118.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1PCbWIT103072 for ; Wed, 25 Feb 2004 05:37:32 -0700 To: tsvwg@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 Message-ID: From: Kristine Adamson Date: Wed, 25 Feb 2004 07:37:31 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 02/25/2004 05:37:32, Serialize complete at 02/25/2004 05:37:32 Content-Type: multipart/alternative; boundary="=_alternative 0045583685256E45_=" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_MESSAGE, REPLY_TO_EMPTY autolearn=no version=2.60 Subject: [Tsvwg] TCP-ESTATS-MIB questions Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. --=_alternative 0045583685256E45_= Content-Type: text/plain; charset="US-ASCII" Hello, We are beginning to investigate implementing this MIB and have the following questions: - Since there is a separate table for Listeners, I assume that no TCP connections in Listen state should be supported in any of the other tables, correct? If so, should the description of tcpEStatsConnectionState indicate that listen(2) should never be used, as is stated in the version-neutral TCP-MIB for object tcpConnectionState? - The tcpEStatsConnectIdTable description states that "Entries are retained in this table for at least 30 seconds after the TCP connection first enters the closed state." Is this true only of this table and not the entries in the other tables? If so, why does this apply to this table? Doesn't this mean that there could be entries in this table, for which there are no corresponding entries in the other tables? - tcpEStatsConnectionState has a MAX-ACCESS of read-only, but tcpConnectionState in the version-neutral TCP-MIB has a MAX-ACCESS of read-write. Should they both have the same MAX-ACCESS value? - tcpEStatsDataIpTos: Haven't IPv4 TOS and IPv6 traffic class been superceded by DSCP? Since TOS seems to belong to IPv4, wouldn't it be better to use a different name for this object, one that applied to both IPv4 and IPv6? - tcpEStatsDataSndNxt: Should this object have a syntax of ZeroBasedCounter32 instead of Integer32? - tcpEStatsDataStartTimeStamp: What does "start of the connection" mean? Does it mean the time the connection entered the Established state? - Notifications: with lots of short-lived web connections, couldn't there be a flood of notifications for this MIB? Should there be a scalar object that controls whether notifications should be created or not? Thanks! Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com --=_alternative 0045583685256E45_= Content-Type: text/html; charset="US-ASCII"
Hello,
   We are beginning to investigate implementing this MIB and have the following questions:

- Since there is a separate table for Listeners, I assume that no TCP connections in Listen state should be supported in any of the other tables, correct?  If so, should the description of tcpEStatsConnectionState indicate that listen(2) should never be used, as is stated in the version-neutral TCP-MIB for object tcpConnectionState?

- The tcpEStatsConnectIdTable description states that "Entries are retained in this table for at least 30 seconds after the TCP connection first enters the closed state."  Is this true only of this table and not the entries in the other tables?  If so, why does this apply to this table?  Doesn't this mean that there could be entries in this table, for which there are no corresponding entries in the other tables?          

- tcpEStatsConnectionState has a MAX-ACCESS of read-only, but tcpConnectionState in the version-neutral TCP-MIB has a MAX-ACCESS of read-write.  Should they both have the same MAX-ACCESS value?

- tcpEStatsDataIpTos: Haven't IPv4 TOS and IPv6 traffic class been superceded by DSCP?  Since TOS seems to belong to IPv4, wouldn't it be better to use a different name for this object, one that applied to both IPv4 and IPv6?

- tcpEStatsDataSndNxt: Should this object have a syntax of ZeroBasedCounter32 instead of Integer32?

- tcpEStatsDataStartTimeStamp: What does "start of the connection" mean?  Does it mean the time the connection entered the Established state?  

- Notifications: with lots of short-lived web connections, couldn't there be a flood of notifications for this MIB?  Should there be a scalar object that controls whether notifications should be created or not?
 
Thanks!

Kristine Adamson
IBM Communications Server for MVS: TCP/IP Development
Internet e-mail:adamson@us.ibm.com
 --=_alternative 0045583685256E45_=-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 12:45:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02374 for ; Wed, 25 Feb 2004 12:45:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw35m-0005xh-MN for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 12:45:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PHj6Og022913 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 12:45:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw35l-0005xO-2n; Wed, 25 Feb 2004 12:45:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw35W-0005w0-6D for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 12:44:50 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02280; Wed, 25 Feb 2004 12:44:38 -0500 (EST) Message-Id: <200402251744.MAA02280@ietf.org> From: The IESG To: IETF-Announce: ; Cc: tsvwg@ietf.org, Allison Mankin , Jon Peterson Date: Wed, 25 Feb 2004 12:44:38 -0500 Subject: [Tsvwg] WG Action: RECHARTER: Transport Area Working Group (tsvwg) Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , The charter of the Transport Area Working Group (tsvwg) in the Transport Area of the IETF has been updated. For additional information, please contact the Area Directors or the working group Chairs. Transport Area Working Group (tsvwg) ------------------------------------ Current Status: Active Working Group Chair(s): Allison Mankin Jon Peterson Transport Area Director(s): Allison Mankin Jon Peterson Transport Area Advisor: Jon Peterson Mailing Lists: General Discussion: tsvwg@ietf.org To Subscribe: tsvwg-request@ietf.org In Body: subscribe email_address Archive: ftp://ftp.ietf.org/ietf-mail-archive/tsvwg/ Description of Working Group: The Transport Area receives occasional proposals for the development and publication of RFCs dealing with Transport topics, but for which the required work does not rise to the level where a new working group is justified, yet the topic does not fit with an existing working group, and a single BOF would not provide the time to ensure a mature proposal. The tsvwg will serve as the forum for developing these types of proposals. The tsvwg mailing list will be used to discuss the proposals as they arise. The working group will meet if there are one or more active proposals that require discussion. The working group milestones will be updated as needed to reflect the proposals currently being worked on and the target dates for their completion. New milestones will be first reviewed by the IESG. The working group will be on-going as long as the ADs believe it serves a useful purpose. Goals and Milestones: Done Updates to RFC 793 to resolve conflict between diffserv and TCP interpretation of IP Precedence submitted for publication as Proposed Standard Done Addition to RFC 2018 to use TCP SACK for detecting unnecessary retransmissions submitted for publication as Proposed Standard Done Submit I-D on TCP Congestion Window Validation to IESG for consideration as a Proposed Standard Done Submit I-D on Computing TCP's Retransmission Timer to IESG for consideration as a Proposed Standard. Done submit revised ID for ECN to IESG for consideration as a proposed standard Done submit ID on UDP-lite to IESG for consideration as a proposed standard Done TCP-Friendly Rate Control (TFRC) unicast congestion control algorithm submitted to IESG for consideration as a proposed standard Done submit ID for SCTP unreliable transport mode to IESG for consideration as a Proposed Standard Mar 04 submit early retransmission to IESG for consideration as Experimental Mar 04 submit SCTP Implementer's Guide to IESG for consideration as an Informational RFC Apr 04 submit Eifel response to IESG for consideration as a Proposed Standard Jun 04 ECN Nonce procedure submitted to IESG for consideration as Proposed Standard Sep 04 submit ID for SCTP API for consideration as an Informational RFC Sep 04 TCP-Friendly Variable Rate Control unicast congestion control submitted to IESG for consideration as a Proposed Standard _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 13:23:32 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03878 for ; Wed, 25 Feb 2004 13:23:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw3gW-0000Hx-5V for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 13:23:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PIN4Q2001064 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 13:23:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw3gT-0000G4-73; Wed, 25 Feb 2004 13:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw3fd-0000FN-Kc for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 13:22:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03828 for ; Wed, 25 Feb 2004 13:22:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw3fb-0001tb-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:22:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw3ea-0001mk-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:21:04 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx with esmtp (Exim 4.12) id 1Aw3dh-0001bb-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:20:10 -0500 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e31.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i1PIJd5w499992 for ; Wed, 25 Feb 2004 13:19:39 -0500 Received: from d03nm118.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1PIJWwk130400 for ; Wed, 25 Feb 2004 11:19:33 -0700 To: tsvwg@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 Message-ID: From: Kristine Adamson Date: Wed, 25 Feb 2004 13:19:28 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 02/25/2004 11:19:33, Serialize complete at 02/25/2004 11:19:33 Content-Type: multipart/alternative; boundary="=_alternative 0064A6E285256E45_=" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Tsvwg] tsvwg charter Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. --=_alternative 0064A6E285256E45_= Content-Type: text/plain; charset="US-ASCII" Hello, Is the tsvwg working group still going to be responsible for the TCP-ESTATS-MIB? Also, does anyone know if work is being done on a UDP-ESTATS-MIB? Thanks! Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com --=_alternative 0064A6E285256E45_= Content-Type: text/html; charset="US-ASCII"
Hello,
   Is the tsvwg working group still going to be responsible for the TCP-ESTATS-MIB?  Also, does anyone know if work is being done on a UDP-ESTATS-MIB?  Thanks!

Kristine Adamson
IBM Communications Server for MVS: TCP/IP Development
Internet e-mail:adamson@us.ibm.com
 --=_alternative 0064A6E285256E45_=-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 13:47:33 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04634 for ; Wed, 25 Feb 2004 13:47:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw43l-0001Sy-D0 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 13:47:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PIl52v005603 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 13:47:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw43j-0001S7-VM; Wed, 25 Feb 2004 13:47:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw42k-0001Om-Fo for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 13:46:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04543 for ; Wed, 25 Feb 2004 13:45:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw42i-0003vg-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:46:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw41q-0003qs-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:45:07 -0500 Received: from mailer1.psc.edu ([128.182.58.100]) by ietf-mx with esmtp (Exim 4.12) id 1Aw415-0003lT-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 13:44:19 -0500 Received: from tesla.psc.edu (tesla.psc.edu [128.182.61.233]) by mailer1.psc.edu (8.12.10/8.12.5) with ESMTP id i1PIiI6s019834 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 25 Feb 2004 13:44:18 -0500 (EST) Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.12.10/8.12.5) with ESMTP id i1PIiIrC021596; Wed, 25 Feb 2004 13:44:18 -0500 (EST) Date: Wed, 25 Feb 2004 13:44:18 -0500 (EST) From: Matt Mathis To: Kristine Adamson cc: tsvwg@ietf.org Subject: Re: [Tsvwg] tsvwg charter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Yes we are still thinking about TCP-ESTATS-MIB. I will respond to your specific comments in a bit. You caught several oversights in the document and a few places where it needs to be clarified. Thanks for the feedback, --MM-- On Wed, 25 Feb 2004, Kristine Adamson wrote: > Hello, > Is the tsvwg working group still going to be responsible for the > TCP-ESTATS-MIB? Also, does anyone know if work is being done on a > UDP-ESTATS-MIB? Thanks! > > Kristine Adamson > IBM Communications Server for MVS: TCP/IP Development > Internet e-mail:adamson@us.ibm.com > -- --MM-- ------------------------------------------- Matt Mathis http://www.psc.edu/~mathis Work:412.268.3319 Home/Cell:412.654.7529 ------------------------------------------- A good plan today is better than a perfect plan tomorrow. - Gen Patton _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 18:57:30 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24721 for ; Wed, 25 Feb 2004 18:57:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw8tk-0000Kk-Hh for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 18:57:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1PNv4CE001247 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 18:57:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw8th-0000JS-Qo; Wed, 25 Feb 2004 18:57:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw8sx-0000FJ-PN for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 18:56:15 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24600 for ; Wed, 25 Feb 2004 18:56:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw8su-0007Py-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 18:56:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw8s0-0007Eq-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 18:55:16 -0500 Received: from babbage.csee.usf.edu ([131.247.3.2]) by ietf-mx with esmtp (Exim 4.12) id 1Aw8qw-0006zU-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 18:54:11 -0500 Received: from grad.csee.usf.edu (grad [131.247.3.1]) by babbage.csee.usf.edu (8.12.9/8.12.9) with ESMTP id i1PNptpU010775 for ; Wed, 25 Feb 2004 18:51:55 -0500 (EST) Received: from localhost (sduggire@localhost) by grad.csee.usf.edu (8.10.2+Sun/8.10.2) with ESMTP id i1PNpuO11828 for ; Wed, 25 Feb 2004 18:51:56 -0500 (EST) X-Authentication-Warning: grad.csee.usf.edu: sduggire owned process doing -bs Date: Wed, 25 Feb 2004 18:51:56 -0500 (EST) From: sridhar duggireddy X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Tsvwg] need help in sctp Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Hi, I am doing project on sctp protocol. I have to measure the throughput performance of sctp. I am using the following procedure to measure the bandwidth. set bw1 0.0 set interval 0.025 proc record {} { global ns interval qmon sctp_tf bw1 sctp0 set now [$ns now] set bw [$qmon set bdepartures_] # Bandwidth in Mbps set bw2 [expr ($bw-$bw1)*8/1000000/$interval] puts $sctp_tf "$bw2" set bw1 [expr $bw] $ns at $now "$sctp0 print cwnd_" $ns at [expr $now+$interval] "record" } I want to measure the bandwidth for every 0.025 seconds and take the average of all bandwidths after the simulation time. When I am running the above procedure I am getting all the bandwidth values as zero. I think there is problem in setting the bandwidth variable (bw1). can anyone explain how to solve this? Thanks, Sridhar. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Feb 25 20:00:38 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27479 for ; Wed, 25 Feb 2004 20:00:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw9sn-0004sT-Gq for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 20:00:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1Q109ki018736 for tsvwg-archive@odin.ietf.org; Wed, 25 Feb 2004 20:00:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw9sj-0004rj-DR; Wed, 25 Feb 2004 20:00:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aw9rw-0004pa-G0 for tsvwg@optimus.ietf.org; Wed, 25 Feb 2004 19:59:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27424 for ; Wed, 25 Feb 2004 19:59:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aw9ru-00069s-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 19:59:14 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aw9qu-00064i-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 19:58:13 -0500 Received: from mailer1.psc.edu ([128.182.58.100]) by ietf-mx with esmtp (Exim 4.12) id 1Aw9qZ-0005zz-00 for tsvwg@ietf.org; Wed, 25 Feb 2004 19:57:51 -0500 Received: from tesla.psc.edu (tesla.psc.edu [128.182.61.233]) by mailer1.psc.edu (8.12.10/8.12.5) with ESMTP id i1Q0vo6s025872 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 25 Feb 2004 19:57:51 -0500 (EST) Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.12.10/8.12.5) with ESMTP id i1Q0vorC026664; Wed, 25 Feb 2004 19:57:50 -0500 (EST) Date: Wed, 25 Feb 2004 19:57:50 -0500 (EST) From: Matt Mathis To: Kristine Adamson , Matt Mathis cc: Transport WG Subject: Re: [Tsvwg] TCP-ESTATS-MIB questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , My comments are inline below. On Wed, 25 Feb 2004, Kristine Adamson wrote: > Hello, > We are beginning to investigate implementing this MIB and have the > following questions: > > - Since there is a separate table for Listeners, I assume that no TCP > connections in Listen state should be supported in any of the other > tables, correct? If so, should the description of > tcpEStatsConnectionState indicate that listen(2) should never be used, as > is stated in the version-neutral TCP-MIB for object tcpConnectionState? Correct. I will update the document. > - The tcpEStatsConnectIdTable description states that "Entries are > retained in this table for at least 30 seconds after the TCP connection > first enters the closed state." Is this true only of this table and not > the entries in the other tables? If so, why does this apply to this > table? Doesn't this mean that there could be entries in this table, for > which there are no corresponding entries in the other tables? This is a feature to make it possible to collect completion stats (total packets, bytes, retransmissions, etc) for each connection. To be sure that you see everything you want to be able to read the stats after the connection is really dead. I don't think the other tables are useful after the connection is closed, but I will think about it. > - tcpEStatsConnectionState has a MAX-ACCESS of read-only, but > tcpConnectionState in the version-neutral TCP-MIB has a MAX-ACCESS of > read-write. Should they both have the same MAX-ACCESS value? Writing to tcpConnectionState supports a special function to force connections closed (as in an mechanism to remotely abort connections). This has always been subject to debate (and as far as I know, never implemented). It doesn't seem useful in the extended statistics MIB. > - tcpEStatsDataIpTos: Haven't IPv4 TOS and IPv6 traffic class been > superceded by DSCP? Since TOS seems to belong to IPv4, wouldn't it be > better to use a different name for this object, one that applied to both > IPv4 and IPv6? Ooops I am out of date here. Can you provide a pointer to a similar object in some other MIB? > - tcpEStatsDataSndNxt: Should this object have a syntax of > ZeroBasedCounter32 instead of Integer32? Nope, because SndNxt in not monotonic. During a "Tahoe" style loss recovery SndNxt is pulled back to SndUna. In modern TCPs this generally happens only following a timeout, but it is a required part of the TCP specifications. For the other sequence numbers, the standard specification for the TCP state variables happens to be consistent with SNMP counters, even though the TCP specification predates SNMP by about a decade. The description should emphasize this point. > - tcpEStatsDataStartTimeStamp: What does "start of the connection" mean? > Does it mean the time the connection entered the Established state? Correct. I will fix it. > - Notifications: with lots of short-lived web connections, couldn't there > be a flood of notifications for this MIB? Should there be a scalar object > that controls whether notifications should be created or not? Yep. Here is we discover that I am a TCP geek who is just pretending to know something about SNMP. I will ask my SNMP experts for a revision. Thanks! I really do appreciate the feedback. BTW I will be at the IETF, so I away not be too responsive next week. --MM-- ------------------------------------------- Matt Mathis http://www.psc.edu/~mathis Work:412.268.3319 Home/Cell:412.654.7529 ------------------------------------------- A good plan today is better than a perfect plan tomorrow. - Gen Patton _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 26 05:23:35 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02576 for ; Thu, 26 Feb 2004 05:23:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwIfb-000122-7b for tsvwg-archive@odin.ietf.org; Thu, 26 Feb 2004 05:23:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1QAN6Pn003871 for tsvwg-archive@odin.ietf.org; Thu, 26 Feb 2004 05:23:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwIfW-000105-Bb; Thu, 26 Feb 2004 05:23:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwIf1-0000wR-0D for tsvwg@optimus.ietf.org; Thu, 26 Feb 2004 05:22:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02551 for ; Thu, 26 Feb 2004 05:22:27 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwIex-0003LA-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:22:27 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwIe6-0003Gg-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:21:35 -0500 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1AwIdX-0003Bg-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:20:59 -0500 Received: from [10.0.1.2] (p5089DCAE.dip.t-dialin.net [80.137.220.174]) by mail-n.franken.de (Postfix) with ESMTP id 6C160245F4; Thu, 26 Feb 2004 11:20:59 +0100 (CET) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <16CBD810-6845-11D8-BBFD-000A95DC192A@lurchi.franken.de> Content-Transfer-Encoding: 7bit Cc: From: Michael Tuexen Subject: Re: [Tsvwg] need help in sctp Date: Thu, 26 Feb 2004 11:18:15 +0100 To: sridhar duggireddy X-Mailer: Apple Mail (2.612) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Please send ns-2 related questions to ns-users@isi.edu Best regards Michael On Feb 26, 2004, at 12:51 AM, sridhar duggireddy wrote: > Hi, > > I am doing project on sctp protocol. I have to measure the > throughput > performance of sctp. I am using the following procedure to measure the > bandwidth. > > set bw1 0.0 > set interval 0.025 > proc record {} { > global ns interval qmon sctp_tf bw1 sctp0 > > set now [$ns now] > > set bw [$qmon set bdepartures_] > > # Bandwidth in Mbps > set bw2 [expr ($bw-$bw1)*8/1000000/$interval] > > puts $sctp_tf "$bw2" > > set bw1 [expr $bw] > > $ns at $now "$sctp0 print cwnd_" > > $ns at [expr $now+$interval] "record" > > } > > I want to measure the bandwidth for every 0.025 seconds and take the > average of all bandwidths after the simulation time. When I am running > the > above procedure I am getting all the bandwidth values as zero. > > I think there is problem in setting the bandwidth variable (bw1). can > anyone explain how to solve this? > > Thanks, > Sridhar. > > > > > _______________________________________________ > tsvwg mailing list > tsvwg@ietf.org > https://www1.ietf.org/mailman/listinfo/tsvwg > _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Feb 26 14:53:38 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05411 for ; Thu, 26 Feb 2004 14:53:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRZH-0005lU-Hu for tsvwg-archive@odin.ietf.org; Thu, 26 Feb 2004 14:53:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1QJrBDO022120 for tsvwg-archive@odin.ietf.org; Thu, 26 Feb 2004 14:53:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRZ8-0005ke-UZ; Thu, 26 Feb 2004 14:53:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwRYw-0005kG-0x for tsvwg@optimus.ietf.org; Thu, 26 Feb 2004 14:52:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05374 for ; Thu, 26 Feb 2004 14:52:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwRYt-00054c-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 14:52:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwRXx-000508-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 14:51:50 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AwRXl-0004vW-00; Thu, 26 Feb 2004 14:51:37 -0500 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1QJpbk11264; Thu, 26 Feb 2004 11:51:37 -0800 (PST) Message-Id: <200402261951.i1QJpbk11264@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, tsvwg@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 26 Feb 2004 11:51:37 -0800 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Subject: [Tsvwg] RFC 3708 on Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3708 Title: Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions Author(s): E. Blanton, M. Allman Status: Experimental Date: February 2004 Mailbox: eblanton@cs.purdue.edu, mallman@icir.org Pages: 9 Characters: 20818 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-dsack-use-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3708.txt TCP and Stream Control Transmission Protocol (SCTP) provide notification of duplicate segment receipt through Duplicate Selective Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number (TSN) notification, respectively. This document presents conservative methods of using this information to identify unnecessary retransmissions for various applications. This document is a product of the Transport Area Working Group Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040226114943.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3708 --OtherAccess Content-Type: Message/External-body; name="rfc3708.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040226114943.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sat Feb 28 18:06:31 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08393 for ; Sat, 28 Feb 2004 18:06:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDX3-0004tg-JU for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:06:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1SN65pn018806 for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:06:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDX0-0004sL-1R; Sat, 28 Feb 2004 18:06:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwImx-0001Rz-3S for tsvwg@optimus.ietf.org; Thu, 26 Feb 2004 05:30:43 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02857 for ; Thu, 26 Feb 2004 05:30:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwImt-00048U-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:30:39 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwIm2-000409-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:29:47 -0500 Received: from smtp.fusemail.net ([69.31.1.141] helo=fuse1.fusemail.net) by ietf-mx with esmtp (Exim 4.12) id 1AwIl6-0003sm-00 for tsvwg@ietf.org; Thu, 26 Feb 2004 05:28:48 -0500 Received: from fusemail.com by fuse1.fusemail.net with smtp (FuseMail extSMTP) id 1AwIl6-0008Ji-Ba for tsvwg@ietf.org; Thu, 26 Feb 2004 04:28:48 -0600 Received: from 137.132.224.158 (FuseMail web user indradeepbiswas) by www.fusemail.com with HTTP; Thu, 26 Feb 2004 04:28:50 -0600 (CST) Message-ID: <2068.137.132.224.158.1077791330.fusewebmail@www.fusemail.com> Date: Thu, 26 Feb 2004 04:28:50 -0600 (CST) From: "Indradeep Biswas" To: tsvwg@ietf.org Reply-To: indradeepbiswas@hotmail.com User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.60 Subject: [Tsvwg] SNOOP implementation on Linux released Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Hi everyone, The Linux implementation of SNOOP has been released ============================================ The Communications and Internet Research Lab (CIRL) has released a Linux implementation of Berkeley Snoop. It is available on the CIRL website at http://www.cir.nus.edu.sg/research/software/snoop/snoop.html Best regards, Indradeep Biswas Honours Year Student Communications and Internet Research Lab National University of Singapore _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sat Feb 28 18:11:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08955 for ; Sat, 28 Feb 2004 18:11:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDbr-0006nj-JI for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:11:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1SNB39j026110 for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:11:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDbq-0006mx-UU; Sat, 28 Feb 2004 18:11:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDbS-0006RO-P8 for tsvwg@optimus.ietf.org; Sat, 28 Feb 2004 18:10:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08897 for ; Sat, 28 Feb 2004 18:10:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AxDbP-0005oR-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:10:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AxDaT-0005ig-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:09:37 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AxDa8-0005bc-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:09:16 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 28 Feb 2004 15:20:26 +0000 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1SN8j1m007289 for ; Sat, 28 Feb 2004 15:08:45 -0800 (PST) Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA26271 for ; Sat, 28 Feb 2004 15:08:44 -0800 (PST) Message-Id: <4.3.2.7.2.20040228170737.02c13ee8@localhost> X-Sender: jmpolk@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 28 Feb 2004 17:08:46 -0600 To: tsvwg@ietf.org From: "James M. Polk" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Tsvwg] Agenda for TSVWG yet? Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , just wondering if there was an agenda made yet that we could see... the meeting is tomorrow ;-) cheers, James ******************* Truth is not to be argued... it is to be presented _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sat Feb 28 18:51:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11053 for ; Sat, 28 Feb 2004 18:51:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxEEa-0003CM-Eg for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:51:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1SNp4OV012252 for tsvwg-archive@odin.ietf.org; Sat, 28 Feb 2004 18:51:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxEEY-0003Am-Kg; Sat, 28 Feb 2004 18:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxEE3-00038g-Lh for tsvwg@optimus.ietf.org; Sat, 28 Feb 2004 18:50:31 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11044 for ; Sat, 28 Feb 2004 18:50:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AxEE0-000256-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:50:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AxED5-00020P-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:49:31 -0500 Received: from cypress.neustar.com ([209.173.57.84]) by ietf-mx with esmtp (Exim 4.12) id 1AxECo-0001v7-00 for tsvwg@ietf.org; Sat, 28 Feb 2004 18:49:14 -0500 Received: from chiimc01.cis.neustar.com (chiimc01.neustar.com [10.32.90.4]) by cypress.neustar.com (8.12.8/8.11.6) with ESMTP id i1SNmj4P002106 for ; Sat, 28 Feb 2004 23:48:45 GMT Received: by chiimc01.cis.neustar.com with Internet Mail Service (5.5.2657.72) id ; Sat, 28 Feb 2004 17:49:03 -0600 Message-ID: From: "Peterson, Jon" To: "'tsvwg@ietf.org'" Date: Sat, 28 Feb 2004 17:48:44 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BIZ_TLD autolearn=no version=2.60 Subject: [Tsvwg] tsvwg agenda Sender: tsvwg-admin@ietf.org Errors-To: tsvwg-admin@ietf.org X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Transport Area Working Group List-Post: List-Help: List-Subscribe: , Thanks for the reminder, James. ;) The agenda follows below. Jon Peterson NeuStar, Inc. ---- Transport Area Working Group (tsvwg) MONDAY, March 1, 1530-1730 ======================================= CHAIRS: Allison Mankin Jon Peterson AGENDA: 1530 Administrivia/Agenda Bashing (note taker) 1535 TSVWG Charter, split with TCPM 1540 MLEF and MLPP (Baker/Polk) 1555 Diffserv classes (Baker/Chan/Babiarz) 1610 Congestion Notification Process for Real-Time Communications (Babiarz) 1620 DTLS (Nagendra/Rescorla) (tentative) 1630 TCPM WG meeting _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg