Re: [Tsvwg] AD review of draft-ietf-tsvwg-quickstart-05

Erblichs <erblichs@earthlink.net> Wed, 16 August 2006 17:50 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDPWj-0001GT-3m; Wed, 16 Aug 2006 13:50:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDPWh-0001GO-IY for tsvwg@ietf.org; Wed, 16 Aug 2006 13:49:59 -0400
Received: from elasmtp-spurfowl.atl.sa.earthlink.net ([209.86.89.66]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDPWd-0006NE-5W for tsvwg@ietf.org; Wed, 16 Aug 2006 13:49:59 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=qEssePJ87qWNo2iWAFLL55bzLM+lbCRAm1BUYh7qgJa+FjOK/5FFns4hkKk6p2sY; h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.88.39] (helo=earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GDPWa-0003WX-Dp; Wed, 16 Aug 2006 13:49:52 -0400
Message-ID: <44E35B1C.77EB46C0@earthlink.net>
Date: Wed, 16 Aug 2006 10:51:24 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Sally Floyd <floyd@icir.org>
Subject: Re: [Tsvwg] AD review of draft-ietf-tsvwg-quickstart-05
References: <200608090334.k793YI8t044826@cougar.icir.org>
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec798a113724de1103891daa265ac01a8018350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.88.39
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: Lars Eggert <lars.eggert@netlab.nec.de>, pasi.sarolathi@iki.fi, tsvwg <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally Floyd,

	Requesting sending rate:

	  I would like to know whether async speeds for the flows
	  are an issue. What I mean by async flows is say a 1Gb capacity
	  flow in one direction and say under 10Mb in the reverse direction.
	  Any two figures that are drasticly different would be acceptable.

	  Thus, request sending rate SHOULDN'T also need to "reserve"
	  return bandwidth. And ack reduction in the reverse direction
	  would also indicate a form of congestion.

	  I did not see these two above items mentioned in this draft.

	Mitchell Erblich
	-----------------

Sally Floyd wrote:
> 
> Lars -
> 
> > find my review of draft-ietf-tsvwg-quickstart-05 below. I didn't find
> > any major technical issues, it's mostly small nits.
> >
> > One overall meta-comment, however, is that the document mixes
> > specification (description of the mechanism and protocols) and
> > applicability statements (discussion of behavior, effects, issues,
> > plus long appendices discussing related work, design options not
> > taken, a rebuttal to a review, etc.) This makes it difficult for the
> > reader to extract the mandatory-to-implement pieces out of the overall
> > work.
> >
> > For a Standards Track document, I'd require that this be addressed,
> > probably by refactoring the document into multiple smaller and more
> > focused ones. Since this is going for Experimental, I'm not going to
> > require this, but still would like to strongly suggest that the
> > authors discuss whether presenting the large body of work in a small
> > number of more focused documents (maybe: architecture, IP-layer
> > extension specification, TCP extension specification, applicability
> > statement) may not be more readable.
> 
> Many thanks for the review.  We made all the changes, and submitted the
> revised version, at:
> http://www.icir.org/floyd/papers/draft-ietf-tsvwg-quickstart-06.txt
> http://www.icir.org/floyd/papers/draft-ietf-tsvwg-quickstart-06.ps
> 
> We deleted one appendix (the one on "Feedback from Bob Briscoe"),
> and added two paragraphs to the Introduction saying that all of the
> formal specifications are in Sections 3, 4, and 6.
> 
> - Sally
> 
>       Changes from draft-ietf-tsvwg-quickstart-05:
> 
>       * Minor editing in response to IESG feedback.
>         This includes changing one "should" to "SHOULD",
>         and changing formating of the IANA Considerations
>         section.
> 
>       * Clarifying in the Introduction that the QS router
>         does not give preferential treatment to QS packets.
>         In response to email from Fil Dickinson.
> 
>       * Added a discussion of interactions between
>         Quick-Start and draft-ietf-pmtud-method.  Feedback
>         from IESG.
> 
>       * Deleted Appendix F on "Feedback from Bob Briscoe".
>         From feedback from the IESG about deleting unnecessary
>         appendices.
> 
>       * Added a paragraph to the Introduction about which
>         sections contain normative references, and which
>         sections are general discussion.  Feedback from
>         IESG.