Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata to conclude 12th June 2017.
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sun, 28 May 2017 19:25 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 71339124D37 for <tsvwg@ietfa.amsl.com>; Sun, 28 May 2017 12:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level:
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2h1N7GLITqUO for <tsvwg@ietfa.amsl.com>; Sun, 28 May 2017 12:25:10 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id EB41E1205D3 for <tsvwg@ietf.org>; Sun, 28 May 2017 12:25:09 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 2630C1B014EA for <tsvwg@ietf.org>; Sun, 28 May 2017 22:19:35 +0100 (BST)
Message-ID: <592B2400.7080407@erg.abdn.ac.uk>
Date: Sun, 28 May 2017 20:24:48 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <592B239D.3030802@erg.abdn.ac.uk>
In-Reply-To: <592B239D.3030802@erg.abdn.ac.uk>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/FX42-0e653JPUICd7iLfd8lwrjk>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata to conclude 12th June 2017.
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 28 May 2017 19:25:11 -0000
On 28/05/2017, 20:23, Gorry Fairhurst wrote: > This email notes the start of a WGLC for draft-ietf-tsvwg-sctp-ndata. > > Please send notes to this list or the WG Chairs, if you support > publication of this draft or have any comments on the current revision > of this document. The intended status (if the document completes the > WGLC) is PS. > > The WGLC will conclude 12th June 2017. > > Best wishes, > > Gorry, David and Wes. > I have the read above document during the WGLC and I would like to add the following comments to the WGLC for this draft. Best wishes, Gorry ---- OLD: allowing to have up to NEW: allowing up to - may be better English? --- OLD: Therefore it is impossible for the sender to NEW: This document allows an SCTP sender to - The impossibility cited was the case before this document is approved. I think the alternative wording avoids this. --- OLD: complaint implementation not supporting NEW: complaint implementation that does not support --- OLD: which has been omitted from the I-DATA chunk NEW: (The I-Data chunk omits a TSN.) - Slightly confusing wording. --- Figure 2 I understood Figure 2 perfectly when I last read it, now some time has passed I found it a little harder. I think this would be much easier to understand if the text explained that this shows a scheduler with two queues of messages. Queue 1 has three messages, queue 2 has one larger message that is interleaved by dividing ... etc and explain 0...8 etc. --- Section 3.2, 3.3 etc contain the word “scheduler” in the title, but section 3.1 did not, but the text still refers to this as a scheduler, so please update the section 3.1 title to include the word “scheduler” to be consistent. --- Section 3.3 - insert comma before /which/. --- Section 3.6 - Speaks of bandwidth (twice), whereas I think it would be clearer to use the word “capacity” since this is about sharing network capacity. --- Section 4.1 OLD: Exposition NEW: Exposure - Wrong word! --- Section 4.1 - For avoidance of doubt, please use the title of the section in RFC6458 with each entry, i.e., “SCTP Header Information Structure” and “Extended SCTP Header Information Structure” and “SCTP Receive Information Structure”. ---
- [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata to c… Gorry Fairhurst
- Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata … Gorry Fairhurst
- Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata … Magnus Westerlund
- Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata … Proshin, Maksim
- Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-ndata … Michael Tuexen