From exim@www1.ietf.org Wed Oct 1 16:25:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02784 for ; Wed, 1 Oct 2003 16:25:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4nX2-0000Cd-P7 for tsvwg-archive@odin.ietf.org; Wed, 01 Oct 2003 16:25:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91KP8U0000738 for tsvwg-archive@odin.ietf.org; Wed, 1 Oct 2003 16:25:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4nWv-0000Bi-UR; Wed, 01 Oct 2003 16:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4nW1-00008O-UZ for tsvwg@optimus.ietf.org; Wed, 01 Oct 2003 16:24:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02715 for ; Wed, 1 Oct 2003 16:23:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4nW0-0004jP-00 for tsvwg@ietf.org; Wed, 01 Oct 2003 16:24:04 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1A4nVz-0004jM-00 for tsvwg@ietf.org; Wed, 01 Oct 2003 16:24:03 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91KO2t22397 for ; Wed, 1 Oct 2003 23:24:02 +0300 (EET DST) Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 1 Oct 2003 23:24:01 +0300 Received: from dadhcp-172019060234.americas.nokia.com ([172.19.60.234]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Wed, 1 Oct 2003 23:24:00 +0300 From: Yogesh Prem Swami To: tsvwg@ietf.org Content-Type: text/plain Organization: Nokia Research Center, Dallas Message-Id: <1065039838.27268.7.camel@atcp01.americas.nokia.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 01 Oct 2003 15:23:59 -0500 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 01 Oct 2003 20:24:01.0292 (UTC) FILETIME=[F35CD4C0:01C38859] Content-Transfer-Encoding: 7bit Subject: [Tsvwg] draft-swami-tcp-lmdr-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: , Content-Transfer-Encoding: 7bit Hello folks, An update for 'draft-swami-tcp-lmdr-01.txt' is now available from: http://www.ietf.org/internet-drafts/draft-swami-tcp-lmdr-01.txt Any comment or suggestion will be highly appreciated. Thanks --yogesh _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Oct 1 17:09:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04820 for ; Wed, 1 Oct 2003 17:09:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4oDY-0003WA-WF for tsvwg-archive@odin.ietf.org; Wed, 01 Oct 2003 17:09:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91L94bG013480 for tsvwg-archive@odin.ietf.org; Wed, 1 Oct 2003 17:09:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4oDV-0003UR-HK; Wed, 01 Oct 2003 17:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4oCv-0003Tz-BP for tsvwg@optimus.ietf.org; Wed, 01 Oct 2003 17:08:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04790 for ; Wed, 1 Oct 2003 17:08:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4oCt-0005RI-00 for tsvwg@ietf.org; Wed, 01 Oct 2003 17:08:23 -0400 Received: from cougar.icir.org ([192.150.187.76]) by ietf-mx with esmtp (Exim 4.12) id 1A4oCs-0005RF-00 for tsvwg@ietf.org; Wed, 01 Oct 2003 17:08:22 -0400 Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.12.9p1/8.12.3) with ESMTP id h91L88jA049245; Wed, 1 Oct 2003 14:08:08 -0700 (PDT) (envelope-from floyd@cougar.icir.org) Message-Id: <200310012108.h91L88jA049245@cougar.icir.org> To: tsvwg@ietf.org cc: Tom Henderson , "Andrei Gurtov" From: Sally Floyd Date: Wed, 01 Oct 2003 14:08:08 -0700 Subject: [Tsvwg] draft-ietf-tsvwg-newreno-01 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 the last IETF, I sent the following email to the mailing list: >From the tsvwg meeting at the IETF, now in progress, here are >the issues to track (in the next week) for WG Last Call, >for the NewReno TCP: > >* Add a note to the section on "Implementation issues for the data >sender" saying that the sender might want a separate flag to record >whether it is in the Fast Recovery procedure, for robustness >with window updates and out-of-order acks. > >* Add an implementation note about taking care of sequence wrap. > >* Address the issue raised by Andrei Gurtov about whether >packets are sent in response to dup acks in those cases >when Fast Recovery is not invoked (because of bugfix). We have made changes addressing these issues, and submitted a revised version of the internet-draft, which is now ready for Working Group Last Call: http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.txt http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.ps We have made no changes to the basic algorithm specified in Section 3 of the draft. Addressing the third item in the list involved adding a discussion in Section 6 about possible heuristics that a sender may use for distinguishing between three dup ACKS from a retransmitted packet that was dropped, and three dup ACKs simply from the unnecessary retransmission of three packets. - Sally http://www.icir.org/floyd/ To see the diffs, one could use wdiff to compare: http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-00.txt http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.txt or compare: http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-00.nroff http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.nroff _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Oct 2 10:52:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23390 for ; Thu, 2 Oct 2003 10:52:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54oI-0003om-46 for tsvwg-archive@odin.ietf.org; Thu, 02 Oct 2003 10:52:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h92Eq6Ds014672 for tsvwg-archive@odin.ietf.org; Thu, 2 Oct 2003 10:52:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54oD-0003oL-4x; Thu, 02 Oct 2003 10:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54nO-0003iI-HP for tsvwg@optimus.ietf.org; Thu, 02 Oct 2003 10:51:10 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23274; Thu, 2 Oct 2003 10:50:59 -0400 (EDT) Message-Id: <200310021450.KAA23274@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: tsvwg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 02 Oct 2003 10:50:58 -0400 Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-newreno-01.txt,.ps 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 Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : The NewReno Modification to TCP's Fast Recovery Algorithm Author(s) : S. Floyd, T. Henderson, A. Gurtov Filename : draft-ietf-tsvwg-newreno-01.txt,.ps Pages : 20 Date : 2003-10-2 RFC 2581 [RFC2581] documents the following four intertwined TCP congestion control algorithms: Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery. RFC 2581 [RFC2581] explicitly allows certain modifications of these algorithms, including modifications that use the TCP Selective Acknowledgement (SACK) option [RFC2018], and modifications that respond to 'partial acknowledgments' (ACKs which cover new data, but not all the data outstanding when loss was detected) in the absence of SACK. The NewReno mechanism uses an algorithm for responding to partial acknowledgments that was first proposed by Janey Hoe in [Hoe95]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-newreno-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-ietf-tsvwg-newreno-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-ietf-tsvwg-newreno-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-2110002.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tsvwg-newreno-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tsvwg-newreno-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-2110002.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Oct 2 12:27:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29436 for ; Thu, 2 Oct 2003 12:27:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56ID-0001s5-0X for tsvwg-archive@odin.ietf.org; Thu, 02 Oct 2003 12:27:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h92GR4hT007168 for tsvwg-archive@odin.ietf.org; Thu, 2 Oct 2003 12:27:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56I8-0001qj-SK; Thu, 02 Oct 2003 12:27:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A56Hi-0001qC-Fv for tsvwg@optimus.ietf.org; Thu, 02 Oct 2003 12:26:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29399 for ; Thu, 2 Oct 2003 12:26:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A56Hg-0003AU-00 for tsvwg@ietf.org; Thu, 02 Oct 2003 12:26:33 -0400 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1A56Hg-0003AQ-00 for tsvwg@ietf.org; Thu, 02 Oct 2003 12:26:32 -0400 Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92GQV623648 for ; Thu, 2 Oct 2003 19:26:31 +0300 (EET DST) Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Thu, 2 Oct 2003 19:26:30 +0300 Received: from dadhcp-172019060234.americas.nokia.com ([172.19.60.234]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 2 Oct 2003 19:26:30 +0300 From: Yogesh Prem Swami To: tsvwg@ietf.org Content-Type: text/plain Organization: Nokia Research Center, Dallas Message-Id: <1065111988.8070.3.camel@atcp01.americas.nokia.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 02 Oct 2003 11:26:28 -0500 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Oct 2003 16:26:30.0553 (UTC) FILETIME=[EFAC6090:01C38901] Content-Transfer-Encoding: 7bit Subject: [Tsvwg] Udate for draft-swami-tsvwg-tcp-dclor-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: , Content-Transfer-Encoding: 7bit Hello, An updated DCLOR draft is now available from: http://www.ietf.org/internet-drafts/draft-swami-tsvwg-tcp-dclor-02.txt Thanks Yogesh _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 6 15:13:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18076 for ; Mon, 6 Oct 2003 15:13:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6an7-0004zX-Es for tsvwg-archive@odin.ietf.org; Mon, 06 Oct 2003 15:13:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96JD9YV019146 for tsvwg-archive@odin.ietf.org; Mon, 6 Oct 2003 15:13:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6amz-0004xl-1q; Mon, 06 Oct 2003 15:13:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6amR-0004x9-Jd for tsvwg@optimus.ietf.org; Mon, 06 Oct 2003 15:12:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17929 for ; Mon, 6 Oct 2003 15:12:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6amQ-0002O4-00 for tsvwg@ietf.org; Mon, 06 Oct 2003 15:12:26 -0400 Received: from smtp808.mail.sc5.yahoo.com ([66.163.168.187]) by ietf-mx with smtp (Exim 4.12) id 1A6amP-0002O1-00 for tsvwg@ietf.org; Mon, 06 Oct 2003 15:12:25 -0400 Received: from adsl-68-76-113-50.dsl.bcvloh.ameritech.net (HELO guns.icir.org) (allman2@sbcglobal.net@68.76.113.50 with login) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 6 Oct 2003 19:12:25 -0000 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 5368AC6BCE0; Mon, 6 Oct 2003 15:12:17 -0400 (EDT) To: Sally Floyd From: Mark Allman Reply-To: mallman@icir.org Cc: tsvwg@ietf.org, Tom Henderson , "Andrei Gurtov" Subject: Re: [Tsvwg] draft-ietf-tsvwg-newreno-01 In-Reply-To: <200310012108.h91L88jA049245@cougar.icir.org> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Stairway to Heavan Date: Mon, 06 Oct 2003 15:12:17 -0400 Message-Id: <20031006191217.5368AC6BCE0@guns.icir.org> 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: , > We have made changes addressing these issues, and submitted a > revised version of the internet-draft, which is now ready for > Working Group Last Call: > > http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.txt > http://www.icir.org/floyd/papers/draft-ietf-tsvwg-newreno-01.ps I read through the document and sent the authors a few minor comments. Nothing major. My opinion is that the document is ready to go. 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 Tue Oct 7 17:18:37 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22927 for ; Tue, 7 Oct 2003 17:18:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zDi-000093-1l for tsvwg-archive@odin.ietf.org; Tue, 07 Oct 2003 17:18:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97LIEgI000553 for tsvwg-archive@odin.ietf.org; Tue, 7 Oct 2003 17:18:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6zDV-000084-A8; Tue, 07 Oct 2003 17:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6XNb-00033M-7Q for tsvwg@optimus.ietf.org; Mon, 06 Oct 2003 11:34:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07819 for ; Mon, 6 Oct 2003 11:34:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6XNa-0007IZ-00 for tsvwg@ietf.org; Mon, 06 Oct 2003 11:34:34 -0400 Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6XNV-0007IH-00 for tsvwg@ietf.org; Mon, 06 Oct 2003 11:34:32 -0400 Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id h96FXrT20234; Mon, 6 Oct 2003 18:33:53 +0300 Date: Mon, 6 Oct 2003 18:33:53 +0300 (EEST) From: Pekka Savola To: tsvwg@ietf.org cc: =?ISO-8859-1?Q?Andreas_Bergstr=F8m?= Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Tsvwg] I-D ACTION:draft-ietf-v6ops-ipv4survey-trans-03.txt (fwd) 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, Remember us asking for feedback on the "IPv4 address usage survey" a couple of weeks ago? Well, the document has been revised a bit (actually twice :-), and I believe it should address the comments received: http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-trans-03.txt Please check it out and see that it's factually correct, the recommendations in section 7 seem reasonable, etc. In particular, we've found a new Full Standard, RFC 907 ("Host Access Protocol"), which should be analyzed ;-) Thanks, Pekka writing as v6ops co-chair ---------- Forwarded message ---------- Date: Mon, 06 Oct 2003 11:11:56 -0400 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Cc: v6ops@ops.ietf.org Subject: I-D ACTION:draft-ietf-v6ops-ipv4survey-trans-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPv6 Operations Working Group of the IETF. Title : Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Author(s) : P. Nesser II, A. Bergstrom Filename : draft-ietf-v6ops-ipv4survey-trans-03.txt Pages : 0 Date : 2003-10-6 This document seeks to document all usage of IPv4 addresses in currently deployed IETF Transport Area documented standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed) as well as Experimental RFCs will be surveyed and any dependencies will be documented. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-v6ops-ipv4survey-trans-03.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-ietf-v6ops-ipv4survey-trans-03.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-ietf-v6ops-ipv4survey-trans-03.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. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 14 10:59:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13433 for ; Tue, 14 Oct 2003 10:59:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Qdk-0003Kx-El for tsvwg-archive@odin.ietf.org; Tue, 14 Oct 2003 10:59:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EExCBw012659 for tsvwg-archive@odin.ietf.org; Tue, 14 Oct 2003 10:59:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Qda-0003EY-7A; Tue, 14 Oct 2003 10:59:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Qcx-0003Dk-M2 for tsvwg@optimus.ietf.org; Tue, 14 Oct 2003 10:58:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13377 for ; Tue, 14 Oct 2003 10:58:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9Qcv-0003l1-00 for tsvwg@ietf.org; Tue, 14 Oct 2003 10:58:21 -0400 Received: from e33.co.us.ibm.com ([32.97.110.131]) by ietf-mx with esmtp (Exim 4.12) id 1A9Qcu-0003kn-00 for tsvwg@ietf.org; Tue, 14 Oct 2003 10:58:20 -0400 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.195.12]) by e33.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9EEvnjZ323604 for ; Tue, 14 Oct 2003 10:57:49 -0400 Received: from d03nm118.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.193.81]) by westrelay03.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9EEvmjU023758 for ; Tue, 14 Oct 2003 08:57:49 -0600 Importance: Normal To: tsvwg@ietf.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Kristine Adamson Date: Tue, 14 Oct 2003 10:57:47 -0400 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 10/14/2003 08:57:48 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [Tsvwg] Status of TCP-ESTATS-MIB 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: , Hello! We are looking into implementing the TCP-ESTATS-MIB in IETF draft draft-ietf-tsvwg-tcp-mib-extension-03.txt. We wondered what the status of this draft was. Is the WG still updating this MIB and will there be a new version soon (maybe for the November IETF meeting)?? Thanks, Kristine Adamson IBM Communications Server for MVS: TCP/IP Development Internet e-mail:adamson@us.ibm.com _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 14 15:36:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26418 for ; Tue, 14 Oct 2003 15:36:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Uxo-0003Wg-O6 for tsvwg-archive@odin.ietf.org; Tue, 14 Oct 2003 15:36:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EJaCMZ013550 for tsvwg-archive@odin.ietf.org; Tue, 14 Oct 2003 15:36:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Uxh-0003SM-QH; Tue, 14 Oct 2003 15:36:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Ux0-0003Kb-PC for tsvwg@optimus.ietf.org; Tue, 14 Oct 2003 15:35:22 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26216; Tue, 14 Oct 2003 15:35:13 -0400 (EDT) Message-Id: <200310141935.PAA26216@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: tsvwg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 14 Oct 2003 15:35:12 -0400 Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-dsack-use-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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : Using TCP DSACKs and SCTP Duplicate TSNs to Detect Spurious Retransmissions Author(s) : E. Blanton, M. Allman Filename : draft-ietf-tsvwg-dsack-use-02.txt Pages : 7 Date : 2003-10-14 TCP and SCTP provide notification of duplicate segment receipt through DSACK and Duplicate TSN notification, respectively. This document presents a conservative method of using this information to identify unnecessary retransmissions for various applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-dsack-use-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-ietf-tsvwg-dsack-use-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-ietf-tsvwg-dsack-use-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-14134913.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tsvwg-dsack-use-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tsvwg-dsack-use-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-14134913.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Wed Oct 15 10:15:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00974 for ; Wed, 15 Oct 2003 10:15:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9mQd-0000ak-Ak for tsvwg-archive@odin.ietf.org; Wed, 15 Oct 2003 10:15:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FEF7FK002233 for tsvwg-archive@odin.ietf.org; Wed, 15 Oct 2003 10:15:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9mQX-0000Zq-F2; Wed, 15 Oct 2003 10:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9mPo-0000XH-UY for tsvwg@optimus.ietf.org; Wed, 15 Oct 2003 10:14:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00866 for ; Wed, 15 Oct 2003 10:14:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9mPm-0004p8-00 for tsvwg@ietf.org; Wed, 15 Oct 2003 10:14:14 -0400 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 1A9mPl-0004oO-00 for tsvwg@ietf.org; Wed, 15 Oct 2003 10:14:13 -0400 Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 07E33C6C51B; Wed, 15 Oct 2003 10:13:15 -0400 (EDT) To: tsvwg@ietf.org Cc: "Ethan Blanton" Cc: "Peterson, Jon" , "Allison Mankin" From: Mark Allman Reply-To: mallman@icir.org Subject: Re: FW: [Tsvwg] Re: Last Call: 'Using TCP DSACKs and SCTP Duplicate T SNs to Detect Spurious Retransmissions' to Experimental RFC In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Freeze-Frame Date: Wed, 15 Oct 2003 10:13:15 -0400 Message-Id: <20031015141315.07E33C6C51B@guns.icir.org> 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: , Sourabh Ladha surfaced two issues with the dsack-use draft during last call. Ethan and I updated the draft (which is now draft-ietf-tsvwg-dsack-use-02.txt in the archives) per the following. > * In the draft the following is about the SACK scoreboard: "We > assume the TCP sender has a data structure to hold selective > acknowledgment information (e.g., as outlined in [RFC3517])." > > Traditionally entries lying below the cumulative ACK point are > deleted from the scoreboard. But the DSACK information normally > comes after loss recovery has exited. So how long should the > scoreboard entries be maintained beyond what is required in > 3517? (1 ACK after loss recovery exits in Fast retransmit; and > N Acks after loss recovery exits in a timeout (GoBackN)?) Good catch. We added a note that to use the scheme outlinedin the draft a TCP implementation would have to keep more history in the scoreboard. > * In the Security Considerations, ECN Nonce 3540 is offered as > a protection. But 3540 calls for disabling Nonce Sum checks > for DupAcks. Is the draft suggesting some extension to 3540 > that NS be checked for DupAcks carrying DSACK? Also a good call. We added some wiggle words to the draft. That is, per the above, the ECN nonce is not directly applicable to the problem of preventing misleading DSACK (/DupTSN) notifications. However, the principles of the ECN nonce are applicable and if we found that protection against lying receivers to be necessary then we could likely build something from the ECN nonce foundation. 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 Wed Oct 15 15:50:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19154 for ; Wed, 15 Oct 2003 15:50:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9rep-0005jL-FW for tsvwg-archive@odin.ietf.org; Wed, 15 Oct 2003 15:50:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FJo7UA022002 for tsvwg-archive@odin.ietf.org; Wed, 15 Oct 2003 15:50:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9rek-0005ik-6Y; Wed, 15 Oct 2003 15:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9reX-0005iG-Gq for tsvwg@optimus.ietf.org; Wed, 15 Oct 2003 15:49:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19133 for ; Wed, 15 Oct 2003 15:49:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9reW-0002Ka-00 for tsvwg@ietf.org; Wed, 15 Oct 2003 15:49:48 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx with esmtp (Exim 4.12) id 1A9reV-0002KW-00 for tsvwg@ietf.org; Wed, 15 Oct 2003 15:49:47 -0400 Received: from chiimc01.npac.com (chiimc01.il.neustar.com [10.32.90.4]) by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h9FJnGW13161; Wed, 15 Oct 2003 19:49:16 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id <4RGYKDT3>; Wed, 15 Oct 2003 14:50:04 -0500 Message-ID: From: "Peterson, Jon" To: "'tsvwg@ietf.org'" Cc: "'mankin@psg.com'" Date: Wed, 15 Oct 2003 14:50:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Tsvwg] agenda items for minneapolis 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: , Please contact myself and Allison if you have a draft you would like to present during the TSVWG meeting in Minneapolis. Jon Peterson NeuStar, Inc. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 17 09:34:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01644 for ; Fri, 17 Oct 2003 09:34:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUk5-0004y1-Ih for tsvwg-archive@odin.ietf.org; Fri, 17 Oct 2003 09:34:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HDY9SO019053 for tsvwg-archive@odin.ietf.org; Fri, 17 Oct 2003 09:34:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUjx-0004ww-As; Fri, 17 Oct 2003 09:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAUjW-0004w9-6S for tsvwg@optimus.ietf.org; Fri, 17 Oct 2003 09:33:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01589 for ; Fri, 17 Oct 2003 09:33:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAUjT-0003R4-00 for tsvwg@ietf.org; Fri, 17 Oct 2003 09:33:31 -0400 Received: from ee.tamu.edu ([165.91.241.199]) by ietf-mx with esmtp (Exim 4.12) id 1AAUjS-0003Qk-00 for tsvwg@ietf.org; Fri, 17 Oct 2003 09:33:31 -0400 Received: from ece122 (ece122.tamu.edu [165.91.210.35]) by ee.tamu.edu (8.12.8/8.12.8) with ESMTP id h9HDXgdb021906 for ; Fri, 17 Oct 2003 08:33:45 -0500 (CDT) Reply-To: From: "Narasimha Reddy" To: Date: Fri, 17 Oct 2003 08:33:24 -0500 Organization: Texas A & M University Message-ID: <002401c394b3$405d0280$23d25ba5@tamu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] 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 We have just submitted a draft for modifying TCP to allow smoother handling of non-congestion events such as wireless channel errors and packet reordering. The draft can be found at http://www.ietf.org/internet-drafts/draft-tcp-dcr-00.txt . Comments/suggestions/discussion/criticism welcome. Regards, Reddy A. L. Narasimha Reddy Phone:979-845-7598 Texas A & M University Fax: 979-845-2630 214 Zachry email: reddy@ee.tamu.edu College Station, TX 77843-3128 http://ee.tamu.edu/~reddy _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Oct 19 12:27:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12039 for ; Sun, 19 Oct 2003 12:27:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABGOb-0005Bn-J5 for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 12:27:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9JGR959019907 for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 12:27:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABGOT-0005AI-3e; Sun, 19 Oct 2003 12:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABGNo-00054T-2m for tsvwg@optimus.ietf.org; Sun, 19 Oct 2003 12:26:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11993 for ; Sun, 19 Oct 2003 12:26:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABGNm-0006UG-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 12:26:18 -0400 Received: from mail-n.franken.de ([193.175.24.27] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1ABGNm-0006UD-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 12:26:18 -0400 Received: from [10.0.1.2] (p5089EB60.dip.t-dialin.net [80.137.235.96]) by mail-n.franken.de (Postfix) with ESMTP id 00277245F4; Sun, 19 Oct 2003 18:26:15 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v604) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: Randall Stewart (cisco) From: Michael Tuexen Date: Sun, 19 Oct 2003 18:26:09 +0200 To: tsvwg@ietf.org X-Mailer: Apple Mail (2.604) Content-Transfer-Encoding: 7bit Subject: [Tsvwg] draft-tuexen-sctp-auth-chunk-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: , Content-Transfer-Encoding: 7bit Dear all, I would like to let you know that I have submitted a new ID from Randall Stewart and myself regarding an SCTP extension for chunk authentication. It is also available at http://www.sctp.de/internet-drafts.html Best regards Michael _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Oct 19 13:46:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13698 for ; Sun, 19 Oct 2003 13:46:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABHd4-0006hG-1p for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 13:46:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9JHk98O025702 for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 13:46:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABHcw-0006ed-PC; Sun, 19 Oct 2003 13:46:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABHcg-0006be-Mb for tsvwg@optimus.ietf.org; Sun, 19 Oct 2003 13:45:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13660 for ; Sun, 19 Oct 2003 13:45:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABHce-00070K-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 13:45:44 -0400 Received: from stewart.chicago.il.us ([66.93.186.36]) by ietf-mx with esmtp (Exim 4.12) id 1ABHcd-0006zv-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 13:45:43 -0400 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 h9JHiaIi095214; Sun, 19 Oct 2003 12:44:38 -0500 (CDT) (envelope-from randall@stewart.chicago.il.us) Message-ID: <3F92CD86.8090407@stewart.chicago.il.us> Date: Sun, 19 Oct 2003 12:44:38 -0500 From: "Randall R. Stewart (home)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030923 X-Accept-Language: en-us, en MIME-Version: 1.0 To: TSV WG list CC: =?ISO-8859-1?Q?Michael_T=FCxen?= , Peter Lei Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Tsvwg] draft-stewart-sctp-pktdrp-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: , Content-Transfer-Encoding: 7bit Dear all, I would like to let you know that I have submitted a new ID from Michael Tuexen, Peter Lei and myself regarding a new SCTP extension that deals with packet drops due to NON congestion events especially in high loss long delay type networks (satellites and radio come to mind :>) It is also available at: http://www.sctp.org (follow the RFCs and I-D's link and you can access both this draft and the authentication draft that Michael earlier announced .. as well as the current other SCTP drafts ... PR-SCTP/ADD-IP et.al) Regards R -- Randall R. Stewart randall@stewart.chicago.il.us 815-342-5222 (cell phone) _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Oct 19 21:40:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25764 for ; Sun, 19 Oct 2003 21:40:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABP1i-0000sp-6A for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 21:40:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9K1e5Ua003351 for tsvwg-archive@odin.ietf.org; Sun, 19 Oct 2003 21:40:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABP1e-0000rD-Ri; Sun, 19 Oct 2003 21:40:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABP1a-0000om-FK for tsvwg@optimus.ietf.org; Sun, 19 Oct 2003 21:39:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25739 for ; Sun, 19 Oct 2003 21:39:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABP1X-0002ST-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 21:39:55 -0400 Received: from pine.neustar.com ([209.173.57.70]) by ietf-mx with esmtp (Exim 4.12) id 1ABP1X-0002SO-00 for tsvwg@ietf.org; Sun, 19 Oct 2003 21:39:55 -0400 Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4]) by pine.neustar.com (8.11.0/8.11.0) with ESMTP id h9K1dKW17824 for ; Mon, 20 Oct 2003 01:39:20 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id ; Sun, 19 Oct 2003 20:40:15 -0500 Message-ID: From: "Peterson, Jon" To: "'tsvwg@ietf.org'" Date: Sun, 19 Oct 2003 20:40:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Tsvwg] WGLC for draft-ietf-tsvwg-newreno-01 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 chairs would like to announce a two-week Working Group Last Call for draft-ietf-tsvwg-newreno-01, commencing on October 20th and concluding on November 3rd. Please send any final comments relating to this document to the TSVWG mailing list. Jon Peterson NeuStar, Inc. _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 20 10:09:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27322 for ; Mon, 20 Oct 2003 10:09:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABaiY-0005DI-1U for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 10:09:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KE96fV019981 for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 10:09:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABaiT-0005AI-7I; Mon, 20 Oct 2003 10:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABahZ-0004sX-Hi for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 10:08:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27175 for ; Mon, 20 Oct 2003 10:07:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABahX-0000Yl-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 10:08:03 -0400 Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49]) by ietf-mx with esmtp (Exim 4.12) id 1ABahW-0000Yi-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 10:08:02 -0400 Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9KE81I2028437 for ; Mon, 20 Oct 2003 16:08:01 +0200 (MEST) Received: from eed.ericsson.se (mailhost.eed.ericsson.se [164.48.133.33]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id 43D34HSF; Mon, 20 Oct 2003 16:12:15 +0200 Received: from res0010384da36.ericsson.com (dhcp5-109.eed.ericsson.se [164.48.135.109]) by eed.ericsson.se (8.8.8+Sun/1.1.mit) with ESMTP id QAA15961 for ; Mon, 20 Oct 2003 16:08:00 +0200 (MET DST) Message-Id: <5.2.0.9.0.20031020155939.029d4e78@mailhost.eed.ericsson.se> X-Sender: eedrel@mailhost.eed.ericsson.se X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 20 Oct 2003 16:09:17 +0200 To: tsvwg@ietf.org From: Reiner Ludwig Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Tsvwg] Eifel Response -04 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 have just submitted a new revision (-04) of the I-D specifying the Eifel Response algorithm. It should be online soon. As announced at the last IETF meeting, it now only deals with spurious timeouts leaving spurious fast retransmits and the question of how to adapt DupThresh for further study. However, as opposed to what we presented at the last IETF meeting, we do not require a decaying of the congestion control state. This is a result of further private discussions, and we motivate this decision in the I-D (section 3.2 & 3.4). Instead of decaying the congestion control state, we follow RFC2861 in that ssthresh is restored to a previous state and cwnd has to be revalidated through slow-start. [This is basically what had already been specified in the -03 version of the I-D. Now, we are just more explicit about it.] ///Andrei & Reiner _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 20 14:25:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06686 for ; Mon, 20 Oct 2003 14:25:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeiO-0001jV-ET for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 14:25:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KIPCJw006621 for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 14:25:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeiE-0001gg-IR; Mon, 20 Oct 2003 14:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABehR-0001Vh-3v for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 14:24:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06638 for ; Mon, 20 Oct 2003 14:24:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABehO-00038I-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 14:24:10 -0400 Received: from igloo.df.lth.se ([194.47.250.47] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1ABehN-00038E-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 14:24:10 -0400 Received: from frodo.df.lth.se (frodo.df.lth.se [194.47.250.40]) by igloo.df.lth.se (8.11.7p1+Sun/8.9.3) with ESMTP id h9KIO7f16749 for ; Mon, 20 Oct 2003 20:24:07 +0200 (MEST) Received: from localhost (triad@localhost) by frodo.df.lth.se (8.10.2+Sun/8.10.2) with ESMTP id h9KIO7203574 for ; Mon, 20 Oct 2003 20:24:07 +0200 (MEST) Date: Mon, 20 Oct 2003 20:24:07 +0200 (MEST) From: Linus Walleij To: tsvwg@ietf.org Message-ID: X-Justice: You know what you doing. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Tsvwg] XML DTD for RFC:s storage situation 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: , I have observed a phenomenon that I need to discuss with the TSVWG. In some recently published RFC:s, XML is used to define transport formats. The XML structure is specified in DTD:s, and the DTD:s are identified with a generic IETF name and an URI. The problem I've seen is that these URI:s, references in RFC:s are dying. Take for example: RFC3080 "BEEP": http://xml.resource.org/profiles/BEEP/beep.dtd (p 47) RFC3367 "CNRP": http://ietf.org/dtd/cnrp-1.0.dtd (p 28) None of these URI:s are in existance. The DTD:s cannot be retrieved from these addresses. Now, I am writing an I-D, and the logical assumption would be that the DTD should be stored at some ietf.ord/dtd/foo.dtd-like URI. But these things doesn't seem to work in practice. What is the correct way of referring to an IETF DTD, and where is it to be stored? And who is to be communicated in order to have something actually being deposited at ietf.org/dtd/foo.dtd? See also the W3 URI "policy": http://www.w3.org/Provider/Style/URI Yours, Linus Walleij _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 20 16:29:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02845 for ; Mon, 20 Oct 2003 16:29:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABgeP-00033c-Nm for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 16:29:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KKTDQm011712 for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 16:29:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABgeC-0002zo-Uc; Mon, 20 Oct 2003 16:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABgdj-0002ud-6J for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 16:28:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02643 for ; Mon, 20 Oct 2003 16:28:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABgdh-0007UV-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 16:28:29 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1ABgdg-0007US-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 16:28:28 -0400 Received: from isi.edu (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id h9KKSMj20695; Mon, 20 Oct 2003 13:28:22 -0700 (PDT) Message-ID: <3F94456A.4000709@isi.edu> Date: Mon, 20 Oct 2003 13:28:26 -0700 From: Joe Touch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linus Walleij CC: tsvwg@ietf.org Subject: Re: [Tsvwg] XML DTD for RFC:s storage situation References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Linus Walleij wrote: > I have observed a phenomenon that I need to discuss with the TSVWG. In > some recently published RFC:s, XML is used to define transport formats. > The XML structure is specified in DTD:s, and the DTD:s are identified with > a generic IETF name and an URI. > > The problem I've seen is that these URI:s, references in RFC:s are dying. > Take for example: > > RFC3080 "BEEP": http://xml.resource.org/profiles/BEEP/beep.dtd (p 47) > RFC3367 "CNRP": http://ietf.org/dtd/cnrp-1.0.dtd (p 28) > > None of these URI:s are in existance. The DTD:s cannot be retrieved from > these addresses. Now, I am writing an I-D, and the logical assumption > would be that the DTD should be stored at some ietf.ord/dtd/foo.dtd-like > URI. But these things doesn't seem to work in practice. > > What is the correct way of referring to an IETF DTD, and where is it to be > stored? And who is to be communicated in order to have something actually > being deposited at ietf.org/dtd/foo.dtd? > > See also the W3 URI "policy": > http://www.w3.org/Provider/Style/URI > > Yours, > Linus Walleij Is there some reason the DTD shouldn't be included in an appendix to the RFC? That would at least solve the issue of its disappearance. Joe _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 20 19:30:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13909 for ; Mon, 20 Oct 2003 19:30:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjTR-0005DL-Ki for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 19:30:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KNU5EP020015 for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 19:30:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjTN-00059s-LL; Mon, 20 Oct 2003 19:30:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABjSg-0004tk-T5 for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 19:29:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13726 for ; Mon, 20 Oct 2003 19:29:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABjSf-0003Mp-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 19:29:17 -0400 Received: from mail0.yrp.nttdocomo.co.jp ([202.245.184.18] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1ABjSe-0003Mb-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 19:29:16 -0400 Received: from spg.yrp.nttdocomo.co.jp (spg.yrp.nttdocomo.co.jp [172.21.48.130]) by mail0.yrp.nttdocomo.co.jp (8.12.10/YRPHUB0-8820020412) with ESMTP id h9KNTF8w021250 for ; Tue, 21 Oct 2003 08:29:15 +0900 (JST) Received: from localhost ([172.21.51.245]) by spg.yrp.nttdocomo.co.jp (8.12.6/8.12.6) with ESMTP id h9KNTEoU024183 for ; Tue, 21 Oct 2003 08:29:14 +0900 (JST) To: tsvwg@ietf.org From: Hosei Matsuoka X-Mailer: Mew version 1.94.2 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-cite-me: matsuoka Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20031020162505E.matsuoka@spg.yrp.nttdocomo.co.jp> Date: Mon, 20 Oct 2003 16:25:05 -0700 X-Dispatcher: imput version 20000228(IM140) Lines: 17 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] draft-matsuoka-multilink-transport-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: , Content-Transfer-Encoding: 7bit Dear all, We submitted a draft for multi-link transport that use multiple wireless links in a connection simultaneously. For efficient and adaptive data striping, multi-stream senders need some more information about the receiver's links. We would like to share this perspective here. The draft is available at http://www.spg.yrp.nttdocomo.co.jp/draft-matsuoka-multilink-transport-00.txt Best regards. -- Hosei Matsuoka Multimedia Laboratories, NTT DoCoMo _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Mon Oct 20 20:05:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15308 for ; Mon, 20 Oct 2003 20:05:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABk1J-00084I-CE for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 20:05:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9L055AP031008 for tsvwg-archive@odin.ietf.org; Mon, 20 Oct 2003 20:05:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABk1G-00083A-GL; Mon, 20 Oct 2003 20:05:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABk0M-0007hB-Fw for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 20:04:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15235 for ; Mon, 20 Oct 2003 20:03:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABk0K-0003x6-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 20:04:04 -0400 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1ABk0J-0003wQ-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 20:04:03 -0400 Received: from phys-ha1mpka.Eng.Sun.COM ([129.146.14.50]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9L02uxA028132; Mon, 20 Oct 2003 17:02:56 -0700 (PDT) Received: from sun.com (shield.SFBay.Sun.COM [129.144.60.49]) by phys-ha1mpka.Eng.Sun.COM (8.8.8p2+Sun/8.8.8/ENSMAIL,v2.0) with ESMTP id RAA00613; Mon, 20 Oct 2003 17:02:56 -0700 (PDT) Message-ID: <3F9477AE.9010000@sun.com> Date: Mon, 20 Oct 2003 17:02:54 -0700 From: Kacheong Poon Organization: Sun Microsystems, Inc. User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031016 X-Accept-Language: en, zh-hk, zh-tw, zh-cn MIME-Version: 1.0 To: tsvwg@ietf.org, "Sctp-Impl (E-mail)" Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Tsvwg] Proposed changes in the SCTP socket API 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 There is one notable change in the version 7 of SCTP socket API draft on how list of IP addresses are represented. A packed array of structures is used instead of an array of fixed size structures. Besides the fact that it is incompatible with the previous drafts, it causes portability issues and is quite inefficient to implement. Unfortunately, the incompatible change was not discussed in any mailing list before it was made. In light of the issues and the desire to save memory used in some operating systems, I propose the following change in how list of IP addresses are represented in the draft. int sctp_bindx(int sd, const void *ipaddrs, int addrcnt, int flags); The parameter ipaddrs is either an array of struct in_addr if sd is a v4 socket or an array of struct in6_addr if the sd is a v6 socket (v4 address is represented as mapped address). This can save memory and copying cost (even more than that in version 7) for this call and should not have any portability issue across platforms with different alignment requirements. This also follows the fact that SCTP cares about IP addresses, not socket addresses (there is no need to replicate some info, such as port). This representation of list of IP addresses also applies to sctp_getladdrs(), sctp_getpaddrs(), and sctp_connectx(). A variant of the above which can be implemented as a replacement of bind() can be defined like int sctp_bindx(int sd, const struct sockaddr *addr, int len, const void *ipaddrs, int addrcnt, int flags); The additional parameters addr and len are the equivalents of what should be passed in the bind() call. Please comment on these changes. I know that the IETF is near so these changes may not be discussed in the next IETF. But do make suggestions on the above. Thanks. -- K. Poon. kacheong.poon@sun.com _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 00:20:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21725 for ; Tue, 21 Oct 2003 00:20:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABo08-0002yR-1B for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 00:20:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9L4K7fV011253 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 00:20:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABo02-0002td-Hh; Tue, 21 Oct 2003 00:20:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABZbw-0000da-UI for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 08:58:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24403 for ; Mon, 20 Oct 2003 08:58:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABZbv-0007gf-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 08:58:11 -0400 Received: from mail0.yrp.nttdocomo.co.jp ([202.245.184.18] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1ABZbu-0007gU-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 08:58:10 -0400 Received: from spg.yrp.nttdocomo.co.jp (spg.yrp.nttdocomo.co.jp [172.21.48.130]) by mail0.yrp.nttdocomo.co.jp (8.12.10/YRPHUB0-8820020412) with ESMTP id h9KCvv8w010182 for ; Mon, 20 Oct 2003 21:57:57 +0900 (JST) Received: from localhost ([172.21.51.245]) by spg.yrp.nttdocomo.co.jp (8.12.6/8.12.6) with ESMTP id h9KCvuoU021462 for ; Mon, 20 Oct 2003 21:57:57 +0900 (JST) To: tsvwg@ietf.org From: Hosei Matsuoka X-Mailer: Mew version 1.94.2 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-cite-me: matsuoka Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20031020055348D.matsuoka@docomolabs-usa.com> Date: Mon, 20 Oct 2003 05:53:48 -0700 X-Dispatcher: imput version 20000228(IM140) Lines: 17 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] draft-matsuoka-multilink-transport-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: , Content-Transfer-Encoding: 7bit Dear all, We submitted a draft for multi-link transport that use multiple wireless links in a connection simultaneously. For efficient and adaptive data striping, multi-stream senders need some more information about the receiver's links. We would like to share this perspective here. The draft is also available at http://www.spg.yrp.nttdocomo.co.jp/draft-matsuoka-multilink-transport-00.txt Best regards. -- Hosei Matsuoka Multimedia Laboratories, NTT DoCoMo _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 00:20:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21740 for ; Tue, 21 Oct 2003 00:20:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABo08-0002yS-1c for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 00:20:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9L4K72M011242 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 00:20:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABo03-0002uJ-Tc; Tue, 21 Oct 2003 00:20:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABj3d-0004Rs-G6 for tsvwg@optimus.ietf.org; Mon, 20 Oct 2003 19:03:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12968 for ; Mon, 20 Oct 2003 19:03:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABj3N-00030u-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 19:03:09 -0400 Received: from [65.125.189.56] (helo=drakken.dbc.mtview.ca.us) by ietf-mx with esmtp (Exim 4.12) id 1ABj3M-00030q-00 for tsvwg@ietf.org; Mon, 20 Oct 2003 19:03:09 -0400 Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h9KN37QP001198; Mon, 20 Oct 2003 16:03:07 -0700 (PDT) Date: Mon, 20 Oct 2003 16:03:07 -0700 From: Marshall Rose To: Joe Touch Cc: Linus Walleij , tsvwg@ietf.org Subject: Re: [Tsvwg] XML DTD for RFC:s storage situation Message-Id: <20031020160307.542a308e.mrose+mtr.netnews@dbc.mtview.ca.us> In-Reply-To: <3F94456A.4000709@isi.edu> References: <3F94456A.4000709@isi.edu> Organization: Dover Beach Consulting, Inc. X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > Is there some reason the DTD shouldn't be included in an appendix to the > RFC? That would at least solve the issue of its disappearance. the DTD is in the RFCs. the confusion, i think, is this: those documents use URIs not for dereferencing but for uniqueness. as an aside, in the applications area, this topic arises about every three months. perhaps it is time for someone to raise it there... /mtr _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 06:47:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12698 for ; Tue, 21 Oct 2003 06:47:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABu2e-0000LH-K4 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 06:47:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LAl8Xm001312 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 06:47:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABu2X-0000J2-GG; Tue, 21 Oct 2003 06:47:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABu1s-00006G-Aq for tsvwg@optimus.ietf.org; Tue, 21 Oct 2003 06:46:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12668 for ; Tue, 21 Oct 2003 06:46:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABu1n-000222-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 06:46:16 -0400 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 1ABu1n-00020j-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 06:46:15 -0400 Received: from cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 21 Oct 2003 03:46:28 -0700 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9LAiNjP023902; Tue, 21 Oct 2003 03:44:24 -0700 (PDT) Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ANI79275; Tue, 21 Oct 2003 03:44:23 -0700 (PDT) Message-ID: <3F950E06.1060508@cisco.com> Date: Tue, 21 Oct 2003 05:44:22 -0500 From: "Randall Stewart (cisco)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030923 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kacheong Poon CC: tsvwg@ietf.org, "Sctp-Impl (E-mail)" References: <3F9477AE.9010000@sun.com> In-Reply-To: <3F9477AE.9010000@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Tsvwg] Re: Proposed changes in the SCTP socket API 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 Kacheong: I guess I am missing something on the "packed array" If you are in IPv6 you send an array of sockaddr_in6 (with IPv4 mapped to V6) If you are in IPv4 you get send an array of sockaddr_in's I am not sure packed array is the right terminlogy.. but I do see that the array of sockaddr_in6 will cause a 64 bit alignment error. But will not your array of in_addr's also cause 64 bit aligment issues as well.. and of course you will loose the ability to call sctp_bindx() by itself and forever need to call bind() sctp_bindx() I would think you would want to at least add a port number so I only have one call to make... But I am not sure I see the advantage of sending arry's of in_addr or in6_addr vs arry's of sockaddr_in and sockaddr_in6... It could save us a few bytes in the kernel to user space transition though.. R Kacheong Poon wrote: > There is one notable change in the version 7 of SCTP socket > API draft on how list of IP addresses are represented. A > packed array of structures is used instead of an array > of fixed size structures. Besides the fact that it is > incompatible with the previous drafts, it causes > portability issues and is quite inefficient to > implement. Unfortunately, the incompatible change was > not discussed in any mailing list before it was made. > > In light of the issues and the desire to save memory used > in some operating systems, I propose the following > change in how list of IP addresses are represented in the > draft. > > int sctp_bindx(int sd, const void *ipaddrs, int addrcnt, > int flags); > > The parameter ipaddrs is either an array of struct in_addr > if sd is a v4 socket or an array of struct in6_addr if > the sd is a v6 socket (v4 address is represented as mapped > address). This can save memory and copying cost (even more > than that in version 7) for this call and should not > have any portability issue across platforms with different > alignment requirements. This also follows the fact that > SCTP cares about IP addresses, not socket addresses (there > is no need to replicate some info, such as port). This > representation of list of IP addresses also applies to > sctp_getladdrs(), sctp_getpaddrs(), and sctp_connectx(). > > A variant of the above which can be implemented as a > replacement of bind() can be defined like > > int sctp_bindx(int sd, const struct sockaddr *addr, int len, > const void *ipaddrs, int addrcnt, int flags); > > The additional parameters addr and len are the equivalents > of what should be passed in the bind() call. > > Please comment on these changes. I know that the IETF > is near so these changes may not be discussed in the next > IETF. But do make suggestions on the above. Thanks. > -- Randall R. Stewart ITD Cisco Systems Inc. rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office) _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 11:00:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22094 for ; Tue, 21 Oct 2003 11:00:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABxzW-00027U-V5 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 11:00:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LF0Aol008057 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 11:00:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABxzO-00024T-Hu; Tue, 21 Oct 2003 11:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABxzF-00022H-2W for tsvwg@optimus.ietf.org; Tue, 21 Oct 2003 10:59:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22060 for ; Tue, 21 Oct 2003 10:59:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABxzC-0004e9-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 10:59:50 -0400 Received: from igloo.df.lth.se ([194.47.250.47] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1ABxzB-0004e6-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 10:59:49 -0400 Received: from frodo.df.lth.se (frodo.df.lth.se [3ffe:200:33::28]) by igloo.df.lth.se (8.11.7p1+Sun/8.11.7) with ESMTP id h9LExkW13902 for ; Tue, 21 Oct 2003 16:59:46 +0200 (MEST) Received: from localhost (triad@localhost) by frodo.df.lth.se (8.10.2+Sun/8.10.2) with ESMTP id h9LExjS17507 for ; Tue, 21 Oct 2003 16:59:45 +0200 (MEST) X-Authentication-Warning: frodo.df.lth.se: triad owned process doing -bs Date: Tue, 21 Oct 2003 16:59:45 +0200 (MEST) From: Linus Walleij To: tsvwg@ietf.org Subject: Re: [Tsvwg] XML DTD for RFC:s storage situation In-Reply-To: <20031020160307.542a308e.mrose+mtr.netnews@dbc.mtview.ca.us> Message-ID: References: <3F94456A.4000709@isi.edu> <20031020160307.542a308e.mrose+mtr.netnews@dbc.mtview.ca.us> X-Justice: You know what you doing. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: , On Mon, 20 Oct 2003, Marshall Rose wrote: > > Is there some reason the DTD shouldn't be included in an appendix to the > > RFC? That would at least solve the issue of its disappearance. > > the DTD is in the RFCs. Yes the DTD is in the RFCs. The point raised is technical: a validating XML parser can not read RFC:s, it will dereference the URI given, if given. It *MAY* have precompiled the IETF global entries (e.g. looking in it's own program code to see if it has a PUBLIC "-//IETF//DTD BEEP//EN" root type) but if this implementation doesn't, it *MAY* try to find it using the URI. Bottom line: the URI in the DTD is for machines, not humans. If it is not present, validating machines will break. Why hasn't it yet caused any problems? Nobody validates their XML files (for performance, I guess). But it is sure permitted to do so, and the URI:s should be resolvable. RFC 3080 says: Refer to this DTD as: %BEEP; And currently this will break almost any validating XML parser. If this should be in the application area, fine, but I think it is a transport matter too. I am ready to write up an RFC saying that DTD:s *shall* be stored at ietf.org/dtd if you want to. It could resolve this issue, but would require additional administration from the IETF. Still, it seems like the only reasonable thing to do. Linus _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 15:55:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03864 for ; Tue, 21 Oct 2003 15:55:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC2b4-00079x-4D for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 15:55:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LJtE8Q027517 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 15:55:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC2as-00076M-Iz; Tue, 21 Oct 2003 15:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC2aC-0006v2-Ek for tsvwg@optimus.ietf.org; Tue, 21 Oct 2003 15:54:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03756 for ; Tue, 21 Oct 2003 15:54:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC2aA-0000SP-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 15:54:18 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 1AC2a9-0000SL-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 15:54:18 -0400 Received: from phys-ha1mpka.Eng.Sun.COM ([129.146.14.50]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h9LJrZ5u021849; Tue, 21 Oct 2003 13:53:35 -0600 (MDT) Received: from sun.com (shield.SFBay.Sun.COM [129.144.60.49]) by phys-ha1mpka.Eng.Sun.COM (8.8.8p2+Sun/8.8.8/ENSMAIL,v2.0) with ESMTP id MAA19379; Tue, 21 Oct 2003 12:53:34 -0700 (PDT) Message-ID: <3F958EBE.40904@sun.com> Date: Tue, 21 Oct 2003 12:53:34 -0700 From: Kacheong Poon Organization: Sun Microsystems, Inc. User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031016 X-Accept-Language: en, zh-hk, zh-tw, zh-cn MIME-Version: 1.0 To: "Randall Stewart (cisco)" CC: tsvwg@ietf.org, "Sctp-Impl (E-mail)" Subject: Re: [Tsvwg] Re: Proposed changes in the SCTP socket API draft References: <3F9477AE.9010000@sun.com> <3F950E06.1060508@cisco.com> In-Reply-To: <3F950E06.1060508@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Randall Stewart (cisco) wrote: > I guess I am missing something on the "packed array" > > If you are in IPv6 you send an array of > sockaddr_in6 (with IPv4 mapped to V6) This is not what is specified in the v7 draft. Please read it again. What you are saying above is indeed not a packed array. But it is also incompatible with what is specified in the v7 draft. The point I am trying to make is we should get rid of packed array. > If you are in IPv4 you get send an array of > sockaddr_in's > > I am not sure packed array is the right terminlogy.. but I do > see that the array of sockaddr_in6 will cause a 64 bit alignment > error. > > But will not your array of in_addr's also cause 64 bit aligment issues > as well.. and of course you will loose the ability to call > sctp_bindx() by itself and forever need to call > > bind() > sctp_bindx() > > I would think you would want to at least add a port number so I > only have one call to make... Check the variant in my previous mail. It includes a socket address, which includes the port number. > But I am not sure I see the advantage of sending arry's of in_addr or > in6_addr vs arry's of sockaddr_in and sockaddr_in6... > > It could save us a few bytes in the kernel to user space transition > though.. My main objection is the packed array. If people really like to waste space with duplicate info (such as port), I am fine with that. But from what I heard, the main reason for the incompatible v7 changes was because of memory usage in copying the sockaddr_storage array. I guess people will really like to save more space. -- K. Poon. kacheong.poon@sun.com _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 17:25:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10651 for ; Tue, 21 Oct 2003 17:25:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC405-0003qE-6B for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 17:25:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LLP9eu014751 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 17:25:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC3zx-0003j3-Vm; Tue, 21 Oct 2003 17:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC3zG-0003X7-B5 for tsvwg@optimus.ietf.org; Tue, 21 Oct 2003 17:24:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10539 for ; Tue, 21 Oct 2003 17:24:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC3zD-0002VJ-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 17:24:16 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AC3zA-0002Th-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 17:24:12 -0400 Received: from cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 21 Oct 2003 14:20:43 -0700 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9LLNCjP004209; Tue, 21 Oct 2003 14:23:12 -0700 (PDT) Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ANJ48287; Tue, 21 Oct 2003 14:23:11 -0700 (PDT) Message-ID: <3F95A3BE.3020500@cisco.com> Date: Tue, 21 Oct 2003 16:23:10 -0500 From: "Randall Stewart (cisco)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030923 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kacheong Poon CC: tsvwg@ietf.org, "Sctp-Impl (E-mail)" Subject: Re: [Tsvwg] Re: Proposed changes in the SCTP socket API draft References: <3F9477AE.9010000@sun.com> <3F950E06.1060508@cisco.com> <3F958EBE.40904@sun.com> In-Reply-To: <3F958EBE.40904@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Kacheong Poon wrote: > Randall Stewart (cisco) wrote: > >> I guess I am missing something on the "packed array" >> >> If you are in IPv6 you send an array of >> sockaddr_in6 (with IPv4 mapped to V6) > > > This is not what is specified in the v7 draft. Please > read it again. > > What you are saying above is indeed not a packed array. > But it is also incompatible with what is specified in > the v7 draft. The point I am trying to make is we should > get rid of packed array. > >> If you are in IPv4 you get send an array of >> sockaddr_in's >> >> I am not sure packed array is the right terminlogy.. but I do >> see that the array of sockaddr_in6 will cause a 64 bit alignment >> error. >> >> But will not your array of in_addr's also cause 64 bit aligment issues >> as well.. and of course you will loose the ability to call >> sctp_bindx() by itself and forever need to call >> >> bind() >> sctp_bindx() >> >> I would think you would want to at least add a port number so I >> only have one call to make... > > > Check the variant in my previous mail. It includes a socket > address, which includes the port number. > >> But I am not sure I see the advantage of sending arry's of in_addr or >> in6_addr vs arry's of sockaddr_in and sockaddr_in6... >> >> It could save us a few bytes in the kernel to user space transition >> though.. > > > My main objection is the packed array. If people really > like to waste space with duplicate info (such as port), > I am fine with that. But from what I heard, the main > reason for the incompatible v7 changes was because of > memory usage in copying the sockaddr_storage array. > I guess people will really like to save more space. > > > a sockaddr storage is 256 bytes. a sockaddr_in is 16 bytes and a sockaddr_in6 is 28 bytes I can put 9 sockaddr_in6's in a sockaddr_storage structure I can put 16 sockaddr_in's in a sockaddr_storage structure There is an extreme magnitude of difference between the sockaddr_inX and sockaddr_storage sizes.. I will take a look at the v7 draft again.. it seems to me the word you are hostile to is packed.. and I think we can easily take that word out of the document... R -- Randall R. Stewart ITD Cisco Systems Inc. rrs@cisco.com 815-342-5222(cell) or 815-477-2127(office) _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 21 18:59:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16488 for ; Tue, 21 Oct 2003 18:59:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC5T0-0008Li-Bp for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 18:59:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LMx6ie032095 for tsvwg-archive@odin.ietf.org; Tue, 21 Oct 2003 18:59:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC5Sv-0008Kl-MT; Tue, 21 Oct 2003 18:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC5Ss-0008KL-Px for tsvwg@optimus.ietf.org; Tue, 21 Oct 2003 18:58:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16466 for ; Tue, 21 Oct 2003 18:58:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC5Sk-00043M-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 18:58:50 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1AC5Sk-00043J-00 for tsvwg@ietf.org; Tue, 21 Oct 2003 18:58:50 -0400 Received: from isi.edu (nib.isi.edu [128.9.160.144]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id h9LMwgj01320; Tue, 21 Oct 2003 15:58:42 -0700 (PDT) Message-ID: <3F95BA2B.3070702@isi.edu> Date: Tue, 21 Oct 2003 15:58:51 -0700 From: Joe Touch Organization: USC/ISI User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linus Walleij CC: tsvwg@ietf.org Subject: Re: [Tsvwg] XML DTD for RFC:s storage situation References: <3F94456A.4000709@isi.edu> <20031020160307.542a308e.mrose+mtr.netnews@dbc.mtview.ca.us> In-Reply-To: X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Linus Walleij wrote: > On Mon, 20 Oct 2003, Marshall Rose wrote: > > >>>Is there some reason the DTD shouldn't be included in an appendix to the >>>RFC? That would at least solve the issue of its disappearance. >> >>the DTD is in the RFCs. > > > Yes the DTD is in the RFCs. The point raised is technical: a validating > XML parser can not read RFC:s, it will dereference the URI given, if > given. It *MAY* have precompiled the IETF global entries (e.g. looking in > it's own program code to see if it has a PUBLIC "-//IETF//DTD BEEP//EN" > root type) but if this implementation doesn't, it *MAY* try to find it > using the URI. > > Bottom line: the URI in the DTD is for machines, not humans. If it is not > present, validating machines will break. > > Why hasn't it yet caused any problems? Nobody validates their XML files > (for performance, I guess). But it is sure permitted to do so, and the > URI:s should be resolvable. > > RFC 3080 says: > > Refer to this DTD as: > > "http://xml.resource.org/profiles/BEEP/beep.dtd"> > %BEEP; > > And currently this will break almost any validating XML parser. > > If this should be in the application area, fine, but I think it is a > transport matter too. > > I am ready to write up an RFC saying that DTD:s *shall* be stored at > ietf.org/dtd if you want to. It could resolve this issue, but would > require additional administration from the IETF. Still, it seems like the > only reasonable thing to do. > > Linus The IETF might not be the best place for these. RFCs are authoritatively maintianed by the RFC Editor; protocol registries are maintained by IANA. This sounds closer to an IANA registry than anything else. Joe _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 24 10:54:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05869 for ; Fri, 24 Oct 2003 10:54:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3KT-0003Up-9M for tsvwg-archive@odin.ietf.org; Fri, 24 Oct 2003 10:54:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OEsHLA013435 for tsvwg-archive@odin.ietf.org; Fri, 24 Oct 2003 10:54:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3KD-0003RD-53; Fri, 24 Oct 2003 10:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3JU-0003H0-7f for tsvwg@optimus.ietf.org; Fri, 24 Oct 2003 10:53:16 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05644; Fri, 24 Oct 2003 10:53:03 -0400 (EDT) Message-Id: <200310241453.KAA05644@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: tsvwg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 24 Oct 2003 10:53:03 -0400 Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-tcp-frto-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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : F-RTO: An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and SCTP Author(s) : P. Sarolahti Filename : draft-ietf-tsvwg-tcp-frto-00.txt Pages : 18 Date : 2003-10-23 Spurious retransmission timeouts (RTOs) cause suboptimal TCP performance, because they often result in unnecessary retransmission of the last window of data. This document describes the 'Forward RTO Recovery' (F-RTO) algorithm for detecting spurious TCP RTOs. F-RTO is a TCP sender only algorithm that does not require any TCP options to operate. After retransmitting the first unacknowledged segment triggered by an RTO, the F-RTO algorithm at a TCP sender monitors the incoming acknowledgements to determine whether the timeout was spurious and to decide whether to send new segments or retransmit unacknowledged segments. The algorithm effectively helps to avoid additional unnecessary retransmissions and thereby improves TCP performance in case of a spurious timeout. The F-RTO algorithm can also be applied with the SCTP protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-tcp-frto-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-ietf-tsvwg-tcp-frto-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-ietf-tsvwg-tcp-frto-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-24104001.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tsvwg-tcp-frto-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tsvwg-tcp-frto-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-24104001.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Sun Oct 26 19:48:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06555 for ; Sun, 26 Oct 2003 19:48:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADvYC-0004yE-K3 for tsvwg-archive@odin.ietf.org; Sun, 26 Oct 2003 19:48:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R0m4Ab019100 for tsvwg-archive@odin.ietf.org; Sun, 26 Oct 2003 19: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 1ADvY9-0004xq-9M; Sun, 26 Oct 2003 19: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 1ADvXs-0004xC-95 for tsvwg@optimus.ietf.org; Sun, 26 Oct 2003 19:47: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 TAA06542 for ; Sun, 26 Oct 2003 19:47:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADvXq-0003X3-00 for tsvwg@ietf.org; Sun, 26 Oct 2003 19:47:42 -0500 Received: from dialup3.icsi.berkeley.edu ([192.150.187.243] helo=lawyers.icir.org) by ietf-mx with esmtp (Exim 4.12) id 1ADvXn-0003Wt-00 for tsvwg@ietf.org; Sun, 26 Oct 2003 19:47:42 -0500 Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id BB0306E807; Sun, 26 Oct 2003 11:40:19 -0500 (EST) To: "Peterson, Jon" From: Mark Allman Reply-To: mallman@icir.org Cc: "'tsvwg@ietf.org'" Subject: Re: [Tsvwg] WGLC for draft-ietf-tsvwg-newreno-01 In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Little Miss Can't Be Wrong Date: Sun, 26 Oct 2003 11:40:19 -0500 Message-Id: <20031026164019.BB0306E807@lawyers.icir.org> 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: , Jon- > The chairs would like to announce a two-week Working Group Last > Call for draft-ietf-tsvwg-newreno-01, commencing on October 20th > and concluding on November 3rd. Please send any final comments > relating to this document to the TSVWG mailing list. I have read through the draft and think it should go forward. (fwiw) allman -- Mark Allman -- ICSI/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 Oct 27 17:06:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18358 for ; Mon, 27 Oct 2003 17: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 1AEFV5-0006vJ-6V for tsvwg-archive@odin.ietf.org; Mon, 27 Oct 2003 17:06:13 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RM6Bjv026572 for tsvwg-archive@odin.ietf.org; Mon, 27 Oct 2003 17:06:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEFUw-0006tN-DO; Mon, 27 Oct 2003 17: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 1AEFUD-0006po-2a for tsvwg@optimus.ietf.org; Mon, 27 Oct 2003 17:05:17 -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 RAA18238 for ; Mon, 27 Oct 2003 17:05:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEFUA-0006sT-00 for tsvwg@ietf.org; Mon, 27 Oct 2003 17:05:14 -0500 Received: from cougar.icir.org ([192.150.187.76]) by ietf-mx with esmtp (Exim 4.12) id 1AEFUA-0006sO-00 for tsvwg@ietf.org; Mon, 27 Oct 2003 17:05:14 -0500 Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.12.9p1/8.12.3) with ESMTP id h9RM5CGa065252; Mon, 27 Oct 2003 14:05:12 -0800 (PST) (envelope-from floyd@cougar.icir.org) Message-Id: <200310272205.h9RM5CGa065252@cougar.icir.org> To: "Peterson, Jon" , mankin@psg.com cc: tsvwg@ietf.org From: Sally Floyd Date: Mon, 27 Oct 2003 14:05:12 -0800 Subject: [Tsvwg] draft-ietf-tsvwg-slowstart-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: , Jon and Allison - When I asked for WG Last Call on the highspeed TCP document back in July, I meant to also ask for WG Last Call on the companion document on Limited Slow-start. This is draft-ietf-tsvwg-slowstart-00.txt, "Limited Slow-Start for TCP with Large Congestion Windows", at "http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-slowstart-00.txt". (This is my fault. In my July 29 email to you asking for WG Last Call for draft-ietf-tsvwg-highspeed-00.txt, I forgot to mention draft-ietf-tsvwg-slowstart-00.txt.) This is a very small document suggesting an optional modification to TCP's slow-start to limit the amount of the increase in the congestion window from one RTT to another during slow-start, and I talked about it in presentations at tsvwg, so I don't think it needs to be talked about at tsvwg again. I think that a WG Last Call would probably be sufficient. Many thanks, and apologies for the hassle... - Sally http://www.icir.org/floyd/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 28 00:43:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12914 for ; Tue, 28 Oct 2003 00:43:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEMdE-0003kC-NR for tsvwg-archive@odin.ietf.org; Tue, 28 Oct 2003 00:43:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9S5h4wj014368 for tsvwg-archive@odin.ietf.org; Tue, 28 Oct 2003 00:43:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEMdB-0003jN-J3; Tue, 28 Oct 2003 00:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEMd2-0003ff-Nl for tsvwg@optimus.ietf.org; Tue, 28 Oct 2003 00:42:52 -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 AAA12841 for ; Tue, 28 Oct 2003 00:42:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEMcz-0007ac-00 for tsvwg@ietf.org; Tue, 28 Oct 2003 00:42:49 -0500 Received: from pine.neustar.com ([209.173.57.70]) by ietf-mx with esmtp (Exim 4.12) id 1AEMcz-0007ZQ-00 for tsvwg@ietf.org; Tue, 28 Oct 2003 00:42:49 -0500 Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4]) by pine.neustar.com (8.12.8/8.11.0) with ESMTP id h9S5gJb9001628; Tue, 28 Oct 2003 05:42:19 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id ; Mon, 27 Oct 2003 23:43:26 -0600 Message-ID: From: "Peterson, Jon" To: "'Sally Floyd'" , mankin@psg.com Cc: tsvwg@ietf.org Date: Mon, 27 Oct 2003 23:43:18 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Tsvwg] RE: draft-ietf-tsvwg-slowstart-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: , No problem. We'll announce a WGLC on the slowstart draft shortly. Jon Peterson NeuStar, Inc. > -----Original Message----- > From: Sally Floyd [mailto:floyd@icir.org] > Sent: Monday, October 27, 2003 2:05 PM > To: Peterson, Jon; mankin@psg.com > Cc: tsvwg@ietf.org > Subject: draft-ietf-tsvwg-slowstart-00.txt > > > Jon and Allison - > > When I asked for WG Last Call on the highspeed TCP document > back in July, I meant to also ask for WG Last Call on the companion > document on Limited Slow-start. This is > draft-ietf-tsvwg-slowstart-00.txt, > "Limited Slow-Start for TCP with Large Congestion Windows", > at > "http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-slowstart-00.txt". (This is my fault. In my July 29 email to you asking for WG Last Call for draft-ietf-tsvwg-highspeed-00.txt, I forgot to mention draft-ietf-tsvwg-slowstart-00.txt.) This is a very small document suggesting an optional modification to TCP's slow-start to limit the amount of the increase in the congestion window from one RTT to another during slow-start, and I talked about it in presentations at tsvwg, so I don't think it needs to be talked about at tsvwg again. I think that a WG Last Call would probably be sufficient. Many thanks, and apologies for the hassle... - Sally http://www.icir.org/floyd/ _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Tue Oct 28 22:50:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21743 for ; Tue, 28 Oct 2003 22:50: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 1AEhLY-0004OS-9I for tsvwg-archive@odin.ietf.org; Tue, 28 Oct 2003 22:50:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T3oCkt016849 for tsvwg-archive@odin.ietf.org; Tue, 28 Oct 2003 22:50:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEhLO-0004N1-8Z; Tue, 28 Oct 2003 22:50:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEhKr-0004Lc-8A for tsvwg@optimus.ietf.org; Tue, 28 Oct 2003 22:49:29 -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 WAA21716 for ; Tue, 28 Oct 2003 22:49:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEhKn-0000Hl-00 for tsvwg@ietf.org; Tue, 28 Oct 2003 22:49:25 -0500 Received: from rwcrmhc13.comcast.net ([204.127.198.39]) by ietf-mx with esmtp (Exim 4.12) id 1AEhKn-0000HQ-00 for tsvwg@ietf.org; Tue, 28 Oct 2003 22:49:25 -0500 Received: from dfnjgl21 (12-237-229-250.client.attbi.com[12.237.229.250]) by comcast.net (rwcrmhc13) with SMTP id <2003102903485401500fket1e> (Authid: sdawkins@comcast.net); Wed, 29 Oct 2003 03:48:55 +0000 Message-ID: <0a2501c39dcf$9e583d80$0400a8c0@DFNJGL21> Reply-To: "Spencer Dawkins" From: "Spencer Dawkins" To: "TSVWG Mailing List" Cc: "Carl Williams" , "Jon Peterson" , "Allison Mankin" Date: Tue, 28 Oct 2003 21:49:12 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] End-to-end Notification I-D available for comments 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 At the IETF 56 TRIGTRAN BoF, we got positive feedback on doing an end-to-end notification for link-up, using end-to-end implicit notifications. We've finally written this up - the draft was announced at http://www.ietf.org/mail-archive/ietf-announce/Current/msg26924.html, and is available at http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-linkup-01.txt. This documents a protocol change proposed in the PILC LINK document (draft-ietf-pilc-link-design-13.txt), since the PILC WG is not chartered to proposal protocol changes. Since this notification has no resemblance to the notifications under discussion in TRIGTRAN, ALIAS, or DNA, we'd like to discuss it on TSVWG, as agreed with Jon and Allison a long time ago. Please fire away! Spencer, for Spencer and Carl _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Thu Oct 30 15:03:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07750 for ; Thu, 30 Oct 2003 15:03:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ0b-0004cD-9s for tsvwg-archive@odin.ietf.org; Thu, 30 Oct 2003 15:03:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UK35xO017740 for tsvwg-archive@odin.ietf.org; Thu, 30 Oct 2003 15:03:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJ0X-0004bO-4n; Thu, 30 Oct 2003 15:03:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFIzx-0004Xj-TH for tsvwg@optimus.ietf.org; Thu, 30 Oct 2003 15:02:25 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07711; Thu, 30 Oct 2003 15:02:13 -0500 (EST) Message-Id: <200310302002.PAA07711@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: tsvwg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 30 Oct 2003 15:02:13 -0500 Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-tcp-eifel-response-04.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: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : The Eifel Response Algorithm for TCP Author(s) : R. Ludwig, A. Gurtov Filename : draft-ietf-tsvwg-tcp-eifel-response-04.txt Pages : 11 Date : 2003-10-30 The Eifel response algorithm requires a detection algorithm to detect a posteriori whether the TCP sender has entered loss recovery unnecessarily. In response to a spurious timeout it adapts the retransmission timer to avoid further spurious timeouts, and can avoid - depending on the detection algorithm - the often unnecessary go-back-N retransmits that would otherwise be sent. Likewise, it adapts the duplicate acknowledgement threshold in response to a spurious fast retransmit. In both cases, the Eifel response algorithm restores the congestion control state in such a way that packet bursts are avoided. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-tcp-eifel-response-04.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-ietf-tsvwg-tcp-eifel-response-04.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-ietf-tsvwg-tcp-eifel-response-04.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-10-30150059.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tsvwg-tcp-eifel-response-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tsvwg-tcp-eifel-response-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-30150059.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 02:28:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15963 for ; Fri, 31 Oct 2003 02:28:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFThW-000734-EM for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 02:28:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V7S6aG027002 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 02:28:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFThS-0006zD-Mn; Fri, 31 Oct 2003 02:28:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFKGE-0004AU-3z for tsvwg@optimus.ietf.org; Thu, 30 Oct 2003 16:23:18 -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 QAA12248 for ; Thu, 30 Oct 2003 16:23:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFKGC-0002SL-00 for tsvwg@ietf.org; Thu, 30 Oct 2003 16:23:16 -0500 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1AFKGB-0002Rp-00 for tsvwg@ietf.org; Thu, 30 Oct 2003 16:23:15 -0500 Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9ULMjxA005141; Thu, 30 Oct 2003 13:22:45 -0800 (PST) Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id h9ULMjbx022758; Thu, 30 Oct 2003 16:22:45 -0500 (EST) Received: from thunk (localhost [127.0.0.1]) by thunk.east.sun.com (8.12.10+Sun/8.12.10) with ESMTP id h9ULMiS4000324; Thu, 30 Oct 2003 16:22:44 -0500 (EST) Message-Id: <200310302122.h9ULMiS4000324@thunk.east.sun.com> From: Bill Sommerfeld To: Pekka Savola cc: tsvwg@ietf.org, v6ops@ops.ietf.org In-Reply-To: Your message of "Thu, 30 Oct 2003 22:14:24 +0200." Reply-to: sommerfeld@east.sun.com Date: Thu, 30 Oct 2003 16:22:44 -0500 Subject: [Tsvwg] Re: TCP and ICMP soft-errors in IPv4/6 environments 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: , > Has this been discussed in the transport area? Is there something to be > done about this, e.g. a BCP document discussing this practice and > suggesting ICMP DU's are OK when establishing connections -- or something > else? Maybe the right answer here is a "slewed parallel" connection establishment; start with one address, and if you get a soft error or a RTO-sized timeout, try a second, third, fourth, etc., connection, but leave the prior ones open in the event they complete successfully. Soft errors wouldn't kill the first connection -- they'd just be a a hint to try another connection in parallel. This should probably be buried in a library routine so that applications don't have to reinvent this wheel. - Bill _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 03:14:55 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15964 for ; Fri, 31 Oct 2003 02:28:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFThW-000733-Dp for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 02:28:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V7S6Hs027004 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 02:28:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFThR-0006yl-DM; Fri, 31 Oct 2003 02:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFJC5-0006ci-LF for tsvwg@optimus.ietf.org; Thu, 30 Oct 2003 15:14:57 -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 PAA09304 for ; Thu, 30 Oct 2003 15:14:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFJC4-0001T2-00 for tsvwg@ietf.org; Thu, 30 Oct 2003 15:14:56 -0500 Received: from netcore.fi ([193.94.160.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFJC3-0001Qz-00 for tsvwg@ietf.org; Thu, 30 Oct 2003 15:14:55 -0500 Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id h9UKEOt24301; Thu, 30 Oct 2003 22:14:24 +0200 Date: Thu, 30 Oct 2003 22:14:24 +0200 (EET) From: Pekka Savola To: tsvwg@ietf.org cc: v6ops@ops.ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Tsvwg] TCP and ICMP soft-errors in IPv4/6 environments 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, (Targeted at Transport area, v6ops is there just to keep v6ops in the loop, this has already been discussed there at some length..) With dual-stack IPv4/6 deployments, when a TCP connection is tried to both an IPv6 and IPv4 address, these are done in serial w/ a getaddrinfo loop (in the typical case). If the first destination is unreachable (e.g. resulting in a host unreachable ICMPv6 message). The old host requirements document states that TCP MUST NOT abort connections on such soft errors. However, this poses some problems in current deployments where multiple addresses are tried sequentially, as summarized above. This is discussed more in section 2.3 of: http://www.ietf.org/internet-drafts/draft-ietf-v6ops-v6onbydefault-00.txt Has this been discussed in the transport area? Is there something to be done about this, e.g. a BCP document discussing this practice and suggesting ICMP DU's are OK when establishing connections -- or something else? Pekka Writing as v6ops co-chair -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 03:28:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17639 for ; Fri, 31 Oct 2003 03:28:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUdX-0005Xy-OY for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 03:28:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V8S3RW021323 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 03:28:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUdW-0005Xl-33; Fri, 31 Oct 2003 03:28:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUcf-0005UV-Kw for tsvwg@optimus.ietf.org; Fri, 31 Oct 2003 03:27: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 DAA17615 for ; Fri, 31 Oct 2003 03:26:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFUcd-0003o8-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 03:27:07 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AFUcc-0003nx-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 03:27:06 -0500 Received: from [193.180.251.49] (helo=albatross-ext.wise.edt.ericsson.se) by manatick with esmtp (Exim 4.24) id 1AFUcS-0006T1-N1 for tsvwg@ietf.org; Fri, 31 Oct 2003 03:26:56 -0500 Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9V8QQI2023371 for ; Fri, 31 Oct 2003 09:26:26 +0100 (MET) 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 V63BGY53; Fri, 31 Oct 2003 09:26:31 +0100 Received: from res0010384da36.ericsson.com (rac169pc.edd.ericsson.se [164.48.123.169]) by eed.ericsson.se (8.8.8+Sun/1.1.mit) with ESMTP id JAA02424 for ; Fri, 31 Oct 2003 09:26:23 +0100 (MET) Message-Id: <5.2.0.9.0.20031031092448.00a9d658@mailhost.eed.ericsson.se> X-Sender: eedrel@mailhost.eed.ericsson.se X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 31 Oct 2003 09:27:43 +0100 To: tsvwg@ietf.org From: Reiner Ludwig In-Reply-To: <200310302002.PAA07711@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Tsvwg] Re: I-D ACTION:draft-ietf-tsvwg-tcp-eifel-response-04.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: , Just to avoid confusion ... Apparently the -04 version of this I-D was announced with the abstract of the -03 version. This is the correct abstract: Based on an appropriate detection algorithm, the Eifel response algorithm provides a way for a TCP sender to respond to a detected spurious timeout. It adapts the retransmission timer to avoid further spurious timeouts, and can avoid - depending on the detection algorithm - the often unnecessary go-back-N retransmits that would otherwise be sent. In addition, the Eifel response algorithm restores the congestion control state in such a way that packet bursts are avoided. The linkhttp://www.ietf.org/internet-drafts/draft-ietf-tsvwg-tcp-eifel-response-04.txt is correct, though. ///Reiner At 21:02 30.10.2003, you wrote: >A New Internet-Draft is available from the on-line Internet-Drafts >directories. >This draft is a work item of the Transport Area Working Group Working >Group of the IETF. > > Title : The Eifel Response Algorithm for TCP > Author(s) : R. Ludwig, A. Gurtov > Filename : draft-ietf-tsvwg-tcp-eifel-response-04.txt > Pages : 11 > Date : 2003-10-30 > >The Eifel response algorithm requires a detection algorithm to detect >a posteriori whether the TCP sender has entered loss recovery >unnecessarily. In response to a spurious timeout it adapts the >retransmission timer to avoid further spurious timeouts, and can >avoid - depending on the detection algorithm - the often unnecessary >go-back-N retransmits that would otherwise be sent. Likewise, it >adapts the duplicate acknowledgement threshold in response to a >spurious fast retransmit. In both cases, the Eifel response algorithm >restores the congestion control state in such a way that packet >bursts are avoided. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-tcp-eifel-response-04.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-ietf-tsvwg-tcp-eifel-response-04.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-ietf-tsvwg-tcp-eifel-response-04.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: <2003-10-30150059.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-ietf-tsvwg-tcp-eifel-response-04.txt > > _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 18:08:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24327 for ; Fri, 31 Oct 2003 18:08: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 1AFiNI-0002GA-0n for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 18:08:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9VN8BvG008646 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 18:08:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFiN7-0002Dt-S1; Fri, 31 Oct 2003 18:08:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFiMY-00021c-P0 for tsvwg@optimus.ietf.org; Fri, 31 Oct 2003 18:07:26 -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 SAA24164 for ; Fri, 31 Oct 2003 18:07:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFiMV-00013G-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 18:07:23 -0500 Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com) by ietf-mx with esmtp (Exim 4.12) id 1AFiMV-00013C-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 18:07:23 -0500 Received: from [172.16.1.206] (helo=CCPU00192) by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian)) id 1AFiML-0004dk-C1; Fri, 31 Oct 2003 15:07:13 -0800 From: "Hanping Long" To: Cc: Date: Fri, 31 Oct 2003 03:07:02 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] one-to-many/one-to-one socket API extension 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: , Content-Transfer-Encoding: 7bit Hi, Regarding the one-to-many(UDP style) and one-to-one(tcp style) socket interface in socket API, one-to-many is more effiencient in terms of exploring the new features of SCTP, can anyone tell me which feature that one-to-one style interface CANNOT make use of? Though each association could have its dedicated buffer space for one-to-many style API, all the associations will fail if their related socket fails. But if one socket fails for one-to-one style API, only one association will fail. Is this the benefit of one-to-one style API? or it's not possible in reality? But for one-to-one style, the maximum number of associations is limited by the number of socket the specific OS allows to open, as well as the select() call could handle(the value of FD_SETSIZE). Any suggestion or idea is highly appreciated! hanping _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 20:48:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28150 for ; Fri, 31 Oct 2003 20:48:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFkrz-0002Jw-Ei for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 20:48:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA11m3rw008897 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 20: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 1AFkrw-0002JI-KC; Fri, 31 Oct 2003 20:48:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFkr5-0002As-Cv for tsvwg@optimus.ietf.org; Fri, 31 Oct 2003 20:47:07 -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 UAA28110 for ; Fri, 31 Oct 2003 20:46:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFkr2-0002da-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 20:47:04 -0500 Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com) by ietf-mx with esmtp (Exim 4.12) id 1AFkr2-0002dP-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 20:47:04 -0500 Received: from [172.16.1.206] (helo=CCPU00192) by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian)) id 1AFkqx-00051P-T9; Fri, 31 Oct 2003 17:46:59 -0800 From: "Hanping Long" To: Cc: Date: Fri, 31 Oct 2003 05:46:35 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [Tsvwg] socket API extension for SCTP checksum 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, The SCTP checksum is migrating from Adler32 to CRC32. During the transient phase, these two check will be co-existing. I am wondering if we could add a preprocessor for the checksum type so that the user could choose to inter-op with old SCTP implementation only supporting Adaler32 if necessary. thanks, hanping _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg From exim@www1.ietf.org Fri Oct 31 21:35:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28895 for ; Fri, 31 Oct 2003 21:35:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFlbV-0006HU-0Q for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 21:35:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA12Z4L2024112 for tsvwg-archive@odin.ietf.org; Fri, 31 Oct 2003 21:35:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFlbT-0006G3-2i; Fri, 31 Oct 2003 21:35:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFlbM-0006FR-JL for tsvwg@optimus.ietf.org; Fri, 31 Oct 2003 21:34:58 -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 VAA28888 for ; Fri, 31 Oct 2003 21:34:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFlbJ-00031s-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 21:34:53 -0500 Received: from gw.openss7.com ([142.179.199.224] ident=[hlaxnw+rxw7n4c8ZFr3/FAqqxCv+gzSL]) by ietf-mx with esmtp (Exim 4.12) id 1AFlb0-00031n-00 for tsvwg@ietf.org; Fri, 31 Oct 2003 21:34:48 -0500 Received: from ns.pigworks.openss7.net (IDENT:caDRMA//cyvacsSuEI5nhRvQokf0XuLy@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id hA12YPa22002; Fri, 31 Oct 2003 19:34:25 -0700 Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id hA12YK531912; Fri, 31 Oct 2003 19:34:20 -0700 Date: Fri, 31 Oct 2003 19:34:20 -0700 From: "Brian F. G. Bidulock" To: Hanping Long Cc: lksctp-developers@lists.sourceforge.net, tsvwg@ietf.org Subject: Re: [Tsvwg] socket API extension for SCTP checksum Message-ID: <20031031193420.A31900@openss7.org> Reply-To: bidulock@openss7.org References: 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: ; from hanl@ccpu.com on Fri, Oct 31, 2003 at 05:46:35AM -0800 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 hA12YPa22002 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 Hanping, Adler32 is deprecated. --brian On Fri, 31 Oct 2003, Hanping Long wrote: > Hi, >=20 > The SCTP checksum is migrating from Adler32 to CRC32. During the transi= ent > phase, these two check will be co-existing. >=20 > I am wondering if we could add a preprocessor for the checksum type so = that > the user could choose to inter-op with old SCTP implementation only > supporting Adaler32 if necessary. >=20 > thanks, > hanping >=20 >=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