WG: Adopting draft-tuexen-tsvwg-sctp-sack-immediately as WG item?

"Adhari, Hakim" <hakim.adhari@uni-due.de> Sat, 20 August 2011 11:23 UTC

Return-Path: <hakim.adhari@uni-due.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB0C21F86BF for <tsvwg@ietfa.amsl.com>; Sat, 20 Aug 2011 04:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vtBmCcwTes6h for <tsvwg@ietfa.amsl.com>; Sat, 20 Aug 2011 04:23:53 -0700 (PDT)
Received: from mailoutzim.uni-due.de (mailoutzim.uni-due.de [132.252.185.16]) by ietfa.amsl.com (Postfix) with ESMTP id 3164921F86B3 for <tsvwg@ietf.org>; Sat, 20 Aug 2011 04:23:52 -0700 (PDT)
Received: from EXCHANGE01.win.uni-due.de (ex02.win.uni-due.de [132.252.180.21]) by mailoutzim.uni-due.de (8.13.1/8.13.1) with ESMTP id p7KBOjfh006805 for <tsvwg@ietf.org>; Sat, 20 Aug 2011 13:24:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: WG: Adopting draft-tuexen-tsvwg-sctp-sack-immediately as WG item?
Date: Sat, 20 Aug 2011 13:25:18 +0200
Message-ID: <F2D94777FF0928419037E41A47C847F60CAEC3CF@EXCHANGE01.win.uni-due.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Adopting draft-tuexen-tsvwg-sctp-sack-immediately as WG item?
Thread-Index: AcxegW52iYpdxIAeSoiavcpHwwkaggABCovA
From: "Adhari, Hakim" <hakim.adhari@uni-due.de>
To: tsvwg@ietf.org
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.16
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 11:23:54 -0000

Hi all,

I have worked with the FreeBSD implementation of SACK-IMMEDIATELY and I
think it is quite useful to improve the performance. I would review this
document.

Best wishes,

Hakim Adhari

Research Assistant at the Computer Networking Technology Group,
University of Duisburg-Essen
http://www.tdr.wiwi.uni-due.de/team/hakim-adhari/




----------  Weitergeleitete Nachricht  ----------

Betreff: Adopting draft-tuexen-tsvwg-sctp-sack-immediately as WG item?
Datum: Dienstag 09 August 2011, 09:36:10
Von: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
An: tsvwg chair <tsvwg-chairs@tools.ietf.org>

The authors of "SACK-IMMEDIATELY extension for the Stream Control
Transmission Protocol draft-tuexen-tsvwg-sctp-sack-immediately-06.txt" 
requests that this is adopted as WG item.

    This document defines a method for a sender of a DATA chunk to
    indicate that the corresponding SACK chunk should be sent back
    immediately.

There was hum indicating general WG support for this at the last IETF in
Quebec City, and the document appears mature to complete quickly. This
email is to allow people to confirm that there is sufficient energy to
complete this work in TSVWG.

* PLEASE send an email to this list if you think this work needs to be
done in the IETF (even if you previously noted this at the IETF).

* PLEASE send an email to this list if you think adopting this document
in TSVWG is a good *OR* a bad idea.

* Please also indicate if you are willing to REVIEW such a document
during its development - our AD has indicated that we expect to have at
least 4 people who commit to review WG outputs. If you can promise to do
this please say!

Please provide any comments at the latest by 23rd August 2011.

Best regards

Gorry & James
(TSVWG Co-Chairs)