Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
"Black, David" <david.black@emc.com> Wed, 20 March 2013 02:57 UTC
Return-Path: <david.black@emc.com>
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 7A11821F85DB for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 sUV+7Qpz4H-B for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2013 19:57:45 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8A021F86CB for <tsvwg@ietf.org>; Tue, 19 Mar 2013 19:57:37 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2vZs8020943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Mar 2013 22:57:35 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 19 Mar 2013 22:57:23 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2K2vNr4016397; Tue, 19 Mar 2013 22:57:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Tue, 19 Mar 2013 22:57:23 -0400
From: "Black, David" <david.black@emc.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Date: Tue, 19 Mar 2013 22:57:21 -0400
Thread-Topic: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
Thread-Index: Ac4k01sCfQXBSLIgT6iW7UnrYRiiRQAQS/8w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293AEE3FE@MX15A.corp.emc.com>
References: <4F605902.40009@erg.abdn.ac.uk> <5148B330.3000304@erg.abdn.ac.uk>
In-Reply-To: <5148B330.3000304@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately-02: 19th March 2013
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: Wed, 20 Mar 2013 02:57:46 -0000
Comments as an individual - <WG co-chair hat OFF> The draft generally looks good - I have a bunch of minor comments. End of Section 3 - I suggest adding a sentence about the new I-bit: This bit was Reserved in RFC 4960 - RFC 4960 specified that this bit should be set to 0 by the sender and ignored by the receiver. Section 4.1 - The paragraph in this section describes an example of a situation in which it is appropriate to set the I-bit. It needs an introductory sentence to say that it is an example, e.g.: One example of a situation in which it may be desirable for an application to trigger setting of the I-bit involves the SCTP_SENDER_DRY_EVENT in the SCTP socket API [RFC6458]. Section 4.2 - Suggest "should" -> "SHOULD" in the following paragraph: If the association is in the SHUTDOWN-PENDING state, the I-bit should be set. This reduces the number of simultaneous associations in case of a busy server handling short living associations. Also an editorial nit in the above - "in case of" -> "for" Another editorial nit in the following: If an SCTP association supports the SCTP Stream Reconfiguration extension defined in [RFC6525], the performance can be improved by setting the I-bit when there are pending reconfiguration requests requiring no outstanding DATA chunks. "requiring" -> "that require that there be" Section 5.2: On reception of an SCTP packet containing a DATA chunk with the I-bit set, the receiver SHOULD NOT delay the sending of the corresponding SACK chunk and send it back immediately. "SACK chunk and send it back immediately" -> "SACK chunk, i.e., the receiver SHOULD immediately respond with the corresponding SACK chunk" Section 8: Please tell IANA which registry to use by including the name of the registry. Section 9: Change start of paragraph to acknowledge new security consideration: OLD This document does not add any additional security considerations in addition to the ones given in [RFC4960]. It should be noted that a malicious sender can force its peer to send packets containing a SACK NEW See [RFC4960] for general security considerations for SCTP. In addition, a malicious sender can force its peer to send packets containing a SACK END Thanks, --David > -----Original Message----- > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of > Gorry Fairhurst > Sent: Tuesday, March 19, 2013 2:49 PM > To: tsvwg WG > Subject: [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sctp-sack-immediately- > 02: 19th March 2013 > > > This email announces the start of a working group last call for > draft-ietf-tsvwg-sctp-sack-immediately-02.txt, "SACK-IMMEDIATELY > Extension for the Stream Control Transmission Protocol". This document > is now thought to be ready to proceed to be published as a PS. Please > send any comments to the TSVWG list. > > The draft is available at: > http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-sack-immediately/ > > The last call will run for TWO weeks, ending Friday 5th April 2013. > > Emails saying "I support" or "I don't support" publication are also most > helpful in judging the WG consensus. Please let us know if this draft > is useful and seems to provide the correct advice. > > James, David and Gorry > (TSVWG Chairs) > tsvwg-chairs@ietf.org > > > > > > >
- WGLC Announcement for draft-ietf-tsvwg-iana-ports… Gorry Fairhurst
- Re: WGLC Announcement for draft-ietf-tsvwg-iana-p… t.petch
- Re: WGLC Announcement for draft-ietf-tsvwg-iana-p… Magnus Westerlund
- Re: WGLC Announcement for draft-ietf-tsvwg-iana-p… t.petch
- Re: WGLC Announcement for draft-ietf-tsvwg-iana-p… Magnus Westerlund
- Re: WGLC Announcement for draft-ietf-tsvwg-iana-p… t.petch
- WGLC Announcement for draft-ietf-tsvwg-source-que… Gorry Fairhurst
- WGLC Announcement for draft-ietf-tsvwg-byte-pkt-c… Gorry Fairhurst
- Note: WGLC Announcement for draft-ietf-tsvwg-byte… Gorry Fairhurst
- Re: Note: WGLC Announcement for draft-ietf-tsvwg-… John Leslie
- RE: Note: WGLC Announcement for draft-ietf-tsvwg-… philip.eardley
- Re: Note: WGLC Announcement for draft-ietf-tsvwg-… Bob Briscoe
- Re: Note: WGLC Announcement for draft-ietf-tsvwg-… John Leslie
- Re: [tsvwg] Note: WGLC Announcement for draft-iet… Manner Jukka
- [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sc… Gorry Fairhurst
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Black, David
- [tsvwg] WGLC Announcement for draft-ietf-tsvwg-sc… Gorry Fairhurst
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Black, David
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Yoshifumi Nishida
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Welzl
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Yoshifumi Nishida
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Thomas Dreibholz
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Thomas Dreibholz
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Welzl
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Becke, Martin
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Becke, Martin
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Welzl
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Thomas Dreibholz
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Thomas Dreibholz
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Welzl
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Welzl
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Anna Brunstrom
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Irene Rüngeler
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Anna Brunstrom
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Michael Tuexen
- [tsvwg] WGLC for draft-ietf-tsvwg-sctp-sack-immed… gorry
- Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-sack-i… Michael Tuexen
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Randy Stewart
- Re: [tsvwg] WGLC Announcement for draft-ietf-tsvw… Yoshifumi Nishida