
From nobody Thu Oct  2 02:16:48 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 996A71A0235; Thu,  2 Oct 2014 02:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 axB8PO4oUcI0; Thu,  2 Oct 2014 02:16:42 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7BDD1A01F7; Thu,  2 Oct 2014 02:16:42 -0700 (PDT)
Received: from 132-177-252-46.ip.sipit.net (132-177-252-46.ip.sipit.net [132.177.252.46] (may be forged)) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s929GcBE034668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 2 Oct 2014 04:16:40 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <542D17F5.80403@nostrum.com>
Date: Thu, 02 Oct 2014 11:16:37 +0200
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, tsvwg@ietf.org, draft-ietf-tsvwg-rsvp-pcn.all@tools.ietf.org
References: <53F659F7.3080106@nostrum.com>
In-Reply-To: <53F659F7.3080106@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/kaq6cpTvYYA6i3A-LNTmuHfi1Ow
Subject: [tsvwg] Gen-art Telechat review: draft-ietf-tsvwg-rsvp-pcn-10
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 02 Oct 2014 09:16:44 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-tsvwg-rsvp-pcn-10
Reviewer: Robert Sparks
Review Date: 2-Oct-2014
IETF LC End Date:
IESG Telechat date: 2-Oct-2014

Summary: Ready for publication as an Experimental RFC

My nits from the earlier review (below) have been addressed.

If you end up with pushback on simply using lowercase 'must' and 
'should' in your terminology session, one alternative to avoid the 
potential 2119 confusion would be to say "will" and "will usually", and 
if necessary, point to the document where the real normative statement 
lives.

RjS


_______________________________________________
On 8/21/14 10:43 PM, Robert Sparks wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-tsvwg-rsvp-pcn-09
> Reviewer: Robert Sparks
> Review Date: 21 Aug 2014
> IETF LC End Date: 26 Aug 2014
> IESG Telechat date: 2 Oct 2014
>
> Summary: Ready (with nits) for publication as Experimental.
>
> David's shepherd writeup points out that implementation and usage 
> experience is desired before producing a proposed standard. Are there 
> any points of concern about how this might behave (or misbehave) in a 
> deployed network that such experience would inform? If so, it would be 
> useful to call them out in the document.
>
> It would be nicer if the document argued why there are no new security 
> considerations introduced by the new behavior defined in this draft, 
> rather than tacitly asserting that there aren't any.
>
> The terminology section has lots of 2119 words in it. It's hard to 
> tell when these have been copied from some other draft (and this is 
> just restating them) vs when this draft is introducing a new 
> requirement. Since a new requirement would likely be missed if it 
> appeared only in a terminology section, would it be feasible to make 
> sure anything new is well covered in section 3 or 4 and remove 2119 
> from these definitions altogether?
>
> The rest of these comments are minor editorial nits:
>
> Section 1.2, paragraph 3: "Intserv over Diffserv can operate over a 
> statically provisioned Diffserv region or RSVP aware." is missing a a 
> word somewhere.
>
> Section 1.2 paragraph 4: "By using multiple aggregate reservations for 
> the same PHB allows enforcement of the different preemption priorities 
> within the aggregation region." doesn't parse. Should the initial "By" 
> be deleted?
>
> The definition for PCN-domain is very close to circular. Perhaps some 
> words can be removed?
>
>
>


From nobody Thu Oct  2 05:16:35 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAECD1A6F68; Thu,  2 Oct 2014 05:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] autolearn=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 H0IANNrWmf25; Thu,  2 Oct 2014 05:16:30 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id D02091A6EF1; Thu,  2 Oct 2014 05:16:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D02662CC61; Thu,  2 Oct 2014 15:16:24 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QTO2FOaG_Q8L; Thu,  2 Oct 2014 15:16:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0F06C2CC4D; Thu,  2 Oct 2014 15:16:16 +0300 (EEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_A0A48611-61B5-41AF-9225-2D53E3C0862E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5416FE6F.8070006@nostrum.com>
Date: Thu, 2 Oct 2014 15:16:19 +0300
Message-Id: <FCB0411E-3883-41E0-945B-2C180F564199@piuha.net>
References: <53F659F7.3080106@nostrum.com>, <dd4843f243834354b3126c28313b1ae6@EXMBX31.ad.utwente.nl> <1fee4dfecb414eb8b47673f906dcf827@EXMBX31.ad.utwente.nl> <5416FE6F.8070006@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/GpqiVUuqhI8G9uVuioHw-rjg7tM
Cc: anuragb@cisco.com, gen-art <gen-art@ietf.org>, draft-ietf-tsvwg-rsvp-pcn.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 02 Oct 2014 12:16:31 -0000

--Apple-Mail=_A0A48611-61B5-41AF-9225-2D53E3C0862E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=windows-1252

Thank you for your review, Robert. Much appreciated.

Jari


--Apple-Mail=_A0A48611-61B5-41AF-9225-2D53E3C0862E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJULUITAAoJEM80gCTQU46q16AQAJQmqWltOYkyFAjB/XOCZSDx
as+gEGMQp2OlghKb+BzQVpcxDVjJ5k0sYUALHkZs4VZNg5BpiFvIJdOFy4FJ7p6o
P1x4o1/EvNQuiuZ2qDuYAyGe42wieZqXsQU8GkRQ7szBAssAZrlIsow6EM5uYCzb
xP7A80hJqAXd5+3UveeI3K5jlX1GqbmQb39+cvGK/D5JBp1g95MwMb7dUS4omM2d
V9Cs5EVFeQsvD5wiiAvUaj8mmCP2hVcU9aqXswMRYGjlG2o5NqIvZUH4edcumbgb
9cr5ypk+McYjAZC4wJq7KCybGfDPWsTFqsL++KSjHodeUQPnARTJULdr5qn1tFsE
VIVWga9Yh9i1LdjX197iMBifNwCsHH2aN8rOWdxzy4WiTcqketS8UG8Pv6zxociF
eshKIUX9+4/2/tsIrcZwtVIS2Fsu+A8SmV4belUceFFDtB5mgr9GWZmd1aZfy6tT
GUjD4xifoxPg59PYWh3NZp3FI0zp5G8i50xGP6e9C7boXNOxgk/X3uGktZU12op4
9MavP0O2Ge/pvvdvJdRqo6aTiVcu3RAkMgFfhIdspNfTjyf83dgI195lIlQfr28u
hmp78K01bPTnNDNtAiyMRh8fF3qZYrDISxKEv0V84kaYWgWiao6HVWhdg8scTI/Z
iCvnkdb+4LND2tePprTG
=ZlXe
-----END PGP SIGNATURE-----

--Apple-Mail=_A0A48611-61B5-41AF-9225-2D53E3C0862E--


From nobody Thu Oct  2 06:51:13 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA651A0365; Thu,  2 Oct 2014 06:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 hoiaD7A50sSo; Thu,  2 Oct 2014 06:50:59 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE6BC1A0389; Thu,  2 Oct 2014 06:50:59 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id uq10so2404728igb.7 for <multiple recipients>; Thu, 02 Oct 2014 06:50:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XNkD6EZk86MF5Hhakoj+1nfjmBq3iMo8cRRT+IeN6lQ=; b=Gyw1zt+bRHMExsXJLLx/SjgmG4SJt/6yBL0SeFMN9Ou2JFu5z1lo0RGXh5hvdU2+Id 2oJ0wCZG1WvM8hxo2tI/+ZKys4YXigqkFvwqXaGJdKDZuloUpo0Js3afwIcMdbiJGLNA MNPqS/7Lpqgx01v2100+mGPyP+qSBW39DDwLB+kZ1GjcAn/HU+S5pbelaHT/nS8Tby9o XEdlMzmDTzEaYXcEFurYw+mOqwWDzEWyo35BIPM85O2bAkaCnsO1SRaV3Gd50QT8Oa7F 5q0448uxfjkuMObrTSdTiRsnfRnlmIsIjywVMU8dX+cT14KkaHj1OaPFs68NRDtac0AN w7Mw==
X-Received: by 10.50.43.137 with SMTP id w9mr4970395igl.36.1412257859105; Thu, 02 Oct 2014 06:50:59 -0700 (PDT)
Received: from [10.136.141.227] (wtenant.iit.edu. [192.42.83.149]) by mx.google.com with ESMTPSA id x9sm858174igl.10.2014.10.02.06.50.54 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Oct 2014 06:50:57 -0700 (PDT)
Message-ID: <542D583C.4080406@gmail.com>
Date: Thu, 02 Oct 2014 08:50:52 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>,  Robert Sparks <rjsparks@nostrum.com>
References: <53F659F7.3080106@nostrum.com>, <dd4843f243834354b3126c28313b1ae6@EXMBX31.ad.utwente.nl> <1fee4dfecb414eb8b47673f906dcf827@EXMBX31.ad.utwente.nl> <5416FE6F.8070006@nostrum.com> <FCB0411E-3883-41E0-945B-2C180F564199@piuha.net>
In-Reply-To: <FCB0411E-3883-41E0-945B-2C180F564199@piuha.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/6kMK5jmWd26Bu7PkNywAfCI3OzI
Cc: gen-art <gen-art@ietf.org>, anuragb@cisco.com, draft-ietf-tsvwg-rsvp-pcn.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 02 Oct 2014 13:51:04 -0000

On 10/02/2014 07:16 AM, Jari Arkko wrote:
> Thank you for your review, Robert. Much appreciated.

And thanks from me. I read 'em, too!

Spencer


From nobody Fri Oct  3 02:26:20 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171901AD000 for <tsvwg@ietfa.amsl.com>; Fri,  3 Oct 2014 02:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.587
X-Spam-Level: 
X-Spam-Status: No, score=-5.587 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 L3p3-fv3_MZC for <tsvwg@ietfa.amsl.com>; Fri,  3 Oct 2014 02:26:12 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id F12BE1ACFFA for <tsvwg@ietf.org>; Fri,  3 Oct 2014 02:26:11 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7334B2B4230; Fri,  3 Oct 2014 10:26:08 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 3 Oct 2014 10:26:07 +0100
Message-ID: <7223b846875e491ff07fbd22b1d193bc.squirrel@www.erg.abdn.ac.uk>
Date: Fri, 3 Oct 2014 10:26:07 +0100
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/3gKAPP1321KYzQfNM3C5vFoRDn8
Subject: [tsvwg] Comments on SCTP draft-ietf-tsvwg-sctp-failover-05
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 03 Oct 2014 09:26:15 -0000

https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-05

As a Chair, I think the above draft seems in good shape from a protocol
perspective, if people see other ways to improve the protocol - it would
be good to know at this stage.

The authors have requested that this be considered as a PS. I have
therefore given this a more critical read - especially carefully looking
at the language, and suggest they consider the comments below and re-issue
the draft.  If we are to consider the draft as PS, then  I think a section
needs to be added to motivate this change (which *WILL* be confirmed on
this list after this revision).

Comments follow on the document (with no intended change to thee
protocol), please consider these - I'd love to hear from others on the
list if they also have any comments on this version!

Gorry
(tsvwg chair)

—


Section 4: (NiT in language)

/In order to address the issues described in Section 3, We propose to
   update SCTP path management scheme as follows./
to
/To address the issues described in Section 3, this section
   updates SCTP path management:/
-If this is to be considered as a PS, it /specifies/ the update.

Section 4.1: (language, there is no ordering so avoid this usage):
/In order to minimize performance impact during failover/
to
/To minimise the performance impact during failover/

Section 4.1 (structure)

- If I understand correctly, the first two paras, including the 2 bullets
are actually informative discussion to introduce the method, if this is
the case could these be moved to section 4, so thats action 4.1 includes
the RFC2119 protocol update.

Section 4.1: (NiT in language)
/tweaking/tuning/

/This proposal introduces/This new method introduces/


Requirement  1 (RFC2119)
/The recommended value of PFMR = 0  when quick failover is used.  /
- is this /RECOMMENDED/ ?

Requirement 3: (NiT in language)
/PF state with least error count/
/PF state with the lowest error count/

/In case of multiple PF/
/When there are multiple PF/

Requirement 4: (Clarity)

/This
        specification recommends that heartbeats be send to PF
        destinations independently from whether the Path Heartbeat
        function (Section 8.3 of [RFC4960]) is enabled for the
        destination address or not./
- This appears at the end of the requirement. I'm not sure what is
intended, could it be that this
RECOMMENDS the use of heartbeats with PF, in which case I'd have expected
this requirement perhaps to be stated first?

Requirement 7: (NiT in language)

/state with least error count/
/state with the lowest error count/

/In  case of multiple destinations with same error count in inactive
        state/
/When there are multiple destinations with the same error count in the
inactive state/

Requirement 4: (RFC2119)


/In order to support this
        prescription a sender SHOULD allow for increment of the
        destination error counters up to some reasonable limit above
        PMR+1/
/Therefore, a sender SHOULD allow for incrementing the
        destination error counters up to some reasonable limit above
        PMR+1/
- I can see the goal of reasonable limit, but is this actually a "limit" 
- that stops further incrementing or "permits" the value to be incremented
beyond PMR+1?

/A  sender MAY choose to deploy other strategies than the above/
- good to state this, but this is the second part of a SHOULD statement
explaining options, as such I do not think it needs an upper case /MAY/
and suspect that /may/ will be sufficient.

Requirement 8: (NiT in language)

/ACKs for chunks which have been transmitted to multiple
        destinations (i.e., a chunk which has been retransmitted to a
        different destination than the destination to which the chunk
        was first transmitted) /
/ACKs for chunks that have been transmitted to multiple
        destinations (i.e., a chunk that has been retransmitted to a
        different destination than the destination to which the chunk
        was first transmitted) /
- change /which/ to /that/

Use upper case for /ack/?

/In this respect then it is specified
        that bytes of a newly acknowledged chunk which has been
        transmitted to multiple destinations SHOULD, when the conditions
        for such contribution is fulfilled following the prescriptions
        of Section 7.2 of [RFC4960], contribute to the congestion window
        growth towards the destination to which the chunk was last
        transmitted. /
- This clause is rather complex and long, please rephrase!


/A SCTP sender MAY apply a different approach for
        both the error count handling as well as the congestion control
        growth handling does it have unequivocally information as to
        which destination (including multiple destinations) the chunk
        reached.  /

- This clause is rather complex, and hard to parse, please rephrase!


Requirement 10: (Clarity)

/SCTP SHOULD provide the means to expose the PF state /
- Is this the SCTP stack should expose to the ULP, please clarify, and use
language similar to other SCTP RFCs.

/Active state ./ - remove space before stop,


/When  doing such SCTP MUST /
/When  this, the SCTP stack MUST /

/suppress exposure of PF state to ULP.  /
/suppress exposure of PF state to the ULP.  /

- I found this requirement not so clearly explained, and rather hard to
comprehend from the text.

Section 4.2: (RFC2119, Clarity)

/Post failover then, by [RFC4960] behavior, an SCTP sender migrates
   the traffic back to the original primary destination once this
   destination becomes active anew.  /
- This doesn’t seem to make sense.

No 1

/Any setting of PSMR < PFMR
       MUST be rejected by the implementation./
- MUST be rejected seems odd. Can you phrase this the other way around?
The PSMR MUST be set so that PSMAR>=PFMR.
- This seems to contradict the previous SHOULD.

No 2 and 3 do not introduce RFC 2119 requirements. Is this intentional, if
so why?

No 4
/support set of PSMR = PFMR/
/support the setting of PSMR = PFMR/


/ We recommend that SCTP-PF sticks to the standard RFC4960 switchback
   behavior as default/
- is this intended to be:
/This specifications RECOMMENDS a default configuration that uses standard
RFC4960 switchback./

/However in order to support//However, to support/

- does this section need the MAYs in capital letters, since it follows a
SHOULD?

—

Section 6:

I’m happy with this clause, if it is correct. For clarity I’d prefer the
section is prefixed by something like:
“Secutity considerations for the use of SCTP are discussed in RFCxxx and
RFCyyyy.”

Appendices: (Structure)

Two appendices are provided, but seem not to be described in the body of
the specification. - please either add references were appropriate to the
appendices or remove them.

Proposed change of status

I would expect such a section to b marked for removal before publication
by RFC-Ed (since this is ONLY an AD/IESG decision - that provides a couple
of short paras that document the evolution of the draft from EXP to PS,
and motivate that the experimental considerations are no longer an issue.
I believe the authors have clearly put this argument in the past, and hope
that this is not a difficult section to add.



From nobody Sun Oct  5 01:00:13 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0CA51A1A72 for <tsvwg@ietfa.amsl.com>; Sun,  5 Oct 2014 01:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.338
X-Spam-Level: *
X-Spam-Status: No, score=1.338 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=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 Ba0zoZ0dyRrb for <tsvwg@ietfa.amsl.com>; Sun,  5 Oct 2014 01:00:09 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D07C31A1A48 for <tsvwg@ietf.org>; Sun,  5 Oct 2014 01:00:08 -0700 (PDT)
Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 8A3D3278164 for <tsvwg@ietf.org>; Sun,  5 Oct 2014 17:00:05 +0900 (JST)
Received: by mail-lb0-f177.google.com with SMTP id w7so2835389lbi.22 for <tsvwg@ietf.org>; Sun, 05 Oct 2014 01:00:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.130.4 with SMTP id oa4mr11041022lbb.37.1412496002653; Sun, 05 Oct 2014 01:00:02 -0700 (PDT)
Received: by 10.114.98.39 with HTTP; Sun, 5 Oct 2014 01:00:02 -0700 (PDT)
In-Reply-To: <7223b846875e491ff07fbd22b1d193bc.squirrel@www.erg.abdn.ac.uk>
References: <7223b846875e491ff07fbd22b1d193bc.squirrel@www.erg.abdn.ac.uk>
Date: Sun, 5 Oct 2014 01:00:02 -0700
Message-ID: <CAO249yc77i3AEe-E89CMRrVBh+nPYy3xJ3OBy7DdAyTGqAkg-Q@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary=047d7b3a818c7c27a50504a85aee
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/MfxiR7nkuUXQ3_M2HkEtj6Do5K8
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] Comments on SCTP draft-ietf-tsvwg-sctp-failover-05
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 05 Oct 2014 08:00:12 -0000

--047d7b3a818c7c27a50504a85aee
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Gorry,

Thanks for the detailed reviews. I agree with your comments.
We will reflect them in our upcoming new version after checking if there's
any inconsistency.

Regards,
--
Yoshi

On Fri, Oct 3, 2014 at 2:26 AM, <gorry@erg.abdn.ac.uk> wrote:

> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-05
>
> As a Chair, I think the above draft seems in good shape from a protocol
> perspective, if people see other ways to improve the protocol - it would
> be good to know at this stage.
>
> The authors have requested that this be considered as a PS. I have
> therefore given this a more critical read - especially carefully looking
> at the language, and suggest they consider the comments below and re-issu=
e
> the draft.  If we are to consider the draft as PS, then  I think a sectio=
n
> needs to be added to motivate this change (which *WILL* be confirmed on
> this list after this revision).
>
> Comments follow on the document (with no intended change to thee
> protocol), please consider these - I'd love to hear from others on the
> list if they also have any comments on this version!
>
> Gorry
> (tsvwg chair)
>
> =E2=80=94
>
>
> Section 4: (NiT in language)
>
> /In order to address the issues described in Section 3, We propose to
>    update SCTP path management scheme as follows./
> to
> /To address the issues described in Section 3, this section
>    updates SCTP path management:/
> -If this is to be considered as a PS, it /specifies/ the update.
>
> Section 4.1: (language, there is no ordering so avoid this usage):
> /In order to minimize performance impact during failover/
> to
> /To minimise the performance impact during failover/
>
> Section 4.1 (structure)
>
> - If I understand correctly, the first two paras, including the 2 bullets
> are actually informative discussion to introduce the method, if this is
> the case could these be moved to section 4, so thats action 4.1 includes
> the RFC2119 protocol update.
>
> Section 4.1: (NiT in language)
> /tweaking/tuning/
>
> /This proposal introduces/This new method introduces/
>
>
> Requirement  1 (RFC2119)
> /The recommended value of PFMR =3D 0  when quick failover is used.  /
> - is this /RECOMMENDED/ ?
>
> Requirement 3: (NiT in language)
> /PF state with least error count/
> /PF state with the lowest error count/
>
> /In case of multiple PF/
> /When there are multiple PF/
>
> Requirement 4: (Clarity)
>
> /This
>         specification recommends that heartbeats be send to PF
>         destinations independently from whether the Path Heartbeat
>         function (Section 8.3 of [RFC4960]) is enabled for the
>         destination address or not./
> - This appears at the end of the requirement. I'm not sure what is
> intended, could it be that this
> RECOMMENDS the use of heartbeats with PF, in which case I'd have expected
> this requirement perhaps to be stated first?
>
> Requirement 7: (NiT in language)
>
> /state with least error count/
> /state with the lowest error count/
>
> /In  case of multiple destinations with same error count in inactive
>         state/
> /When there are multiple destinations with the same error count in the
> inactive state/
>
> Requirement 4: (RFC2119)
>
>
> /In order to support this
>         prescription a sender SHOULD allow for increment of the
>         destination error counters up to some reasonable limit above
>         PMR+1/
> /Therefore, a sender SHOULD allow for incrementing the
>         destination error counters up to some reasonable limit above
>         PMR+1/
> - I can see the goal of reasonable limit, but is this actually a "limit"
> - that stops further incrementing or "permits" the value to be incremente=
d
> beyond PMR+1?
>
> /A  sender MAY choose to deploy other strategies than the above/
> - good to state this, but this is the second part of a SHOULD statement
> explaining options, as such I do not think it needs an upper case /MAY/
> and suspect that /may/ will be sufficient.
>
> Requirement 8: (NiT in language)
>
> /ACKs for chunks which have been transmitted to multiple
>         destinations (i.e., a chunk which has been retransmitted to a
>         different destination than the destination to which the chunk
>         was first transmitted) /
> /ACKs for chunks that have been transmitted to multiple
>         destinations (i.e., a chunk that has been retransmitted to a
>         different destination than the destination to which the chunk
>         was first transmitted) /
> - change /which/ to /that/
>
> Use upper case for /ack/?
>
> /In this respect then it is specified
>         that bytes of a newly acknowledged chunk which has been
>         transmitted to multiple destinations SHOULD, when the conditions
>         for such contribution is fulfilled following the prescriptions
>         of Section 7.2 of [RFC4960], contribute to the congestion window
>         growth towards the destination to which the chunk was last
>         transmitted. /
> - This clause is rather complex and long, please rephrase!
>
>
> /A SCTP sender MAY apply a different approach for
>         both the error count handling as well as the congestion control
>         growth handling does it have unequivocally information as to
>         which destination (including multiple destinations) the chunk
>         reached.  /
>
> - This clause is rather complex, and hard to parse, please rephrase!
>
>
> Requirement 10: (Clarity)
>
> /SCTP SHOULD provide the means to expose the PF state /
> - Is this the SCTP stack should expose to the ULP, please clarify, and us=
e
> language similar to other SCTP RFCs.
>
> /Active state ./ - remove space before stop,
>
>
> /When  doing such SCTP MUST /
> /When  this, the SCTP stack MUST /
>
> /suppress exposure of PF state to ULP.  /
> /suppress exposure of PF state to the ULP.  /
>
> - I found this requirement not so clearly explained, and rather hard to
> comprehend from the text.
>
> Section 4.2: (RFC2119, Clarity)
>
> /Post failover then, by [RFC4960] behavior, an SCTP sender migrates
>    the traffic back to the original primary destination once this
>    destination becomes active anew.  /
> - This doesn=E2=80=99t seem to make sense.
>
> No 1
>
> /Any setting of PSMR < PFMR
>        MUST be rejected by the implementation./
> - MUST be rejected seems odd. Can you phrase this the other way around?
> The PSMR MUST be set so that PSMAR>=3DPFMR.
> - This seems to contradict the previous SHOULD.
>
> No 2 and 3 do not introduce RFC 2119 requirements. Is this intentional, i=
f
> so why?
>
> No 4
> /support set of PSMR =3D PFMR/
> /support the setting of PSMR =3D PFMR/
>
>
> / We recommend that SCTP-PF sticks to the standard RFC4960 switchback
>    behavior as default/
> - is this intended to be:
> /This specifications RECOMMENDS a default configuration that uses standar=
d
> RFC4960 switchback./
>
> /However in order to support//However, to support/
>
> - does this section need the MAYs in capital letters, since it follows a
> SHOULD?
>
> =E2=80=94
>
> Section 6:
>
> I=E2=80=99m happy with this clause, if it is correct. For clarity I=E2=80=
=99d prefer the
> section is prefixed by something like:
> =E2=80=9CSecutity considerations for the use of SCTP are discussed in RFC=
xxx and
> RFCyyyy.=E2=80=9D
>
> Appendices: (Structure)
>
> Two appendices are provided, but seem not to be described in the body of
> the specification. - please either add references were appropriate to the
> appendices or remove them.
>
> Proposed change of status
>
> I would expect such a section to b marked for removal before publication
> by RFC-Ed (since this is ONLY an AD/IESG decision - that provides a coupl=
e
> of short paras that document the evolution of the draft from EXP to PS,
> and motivate that the experimental considerations are no longer an issue.
> I believe the authors have clearly put this argument in the past, and hop=
e
> that this is not a difficult section to add.
>
>
>

--047d7b3a818c7c27a50504a85aee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Gorry,<div><br></div><div>Thanks for the detailed revie=
ws. I agree with your comments.=C2=A0</div><div>We will reflect them in our=
 upcoming new version after checking if there&#39;s any inconsistency.</div=
><div><br></div><div>Regards,</div><div>--</div><div>Yoshi<br><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Oct 3, 2014 at 2:26 AM=
,  <span dir=3D"ltr">&lt;<a href=3D"mailto:gorry@erg.abdn.ac.uk" target=3D"=
_blank">gorry@erg.abdn.ac.uk</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><a href=3D"https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-fail=
over-05" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-tsvwg-sct=
p-failover-05</a><br>
<br>
As a Chair, I think the above draft seems in good shape from a protocol<br>
perspective, if people see other ways to improve the protocol - it would<br=
>
be good to know at this stage.<br>
<br>
The authors have requested that this be considered as a PS. I have<br>
therefore given this a more critical read - especially carefully looking<br=
>
at the language, and suggest they consider the comments below and re-issue<=
br>
the draft.=C2=A0 If we are to consider the draft as PS, then=C2=A0 I think =
a section<br>
needs to be added to motivate this change (which *WILL* be confirmed on<br>
this list after this revision).<br>
<br>
Comments follow on the document (with no intended change to thee<br>
protocol), please consider these - I&#39;d love to hear from others on the<=
br>
list if they also have any comments on this version!<br>
<br>
Gorry<br>
(tsvwg chair)<br>
<br>
=E2=80=94<br>
<br>
<br>
Section 4: (NiT in language)<br>
<br>
/In order to address the issues described in Section 3, We propose to<br>
=C2=A0 =C2=A0update SCTP path management scheme as follows./<br>
to<br>
/To address the issues described in Section 3, this section<br>
=C2=A0 =C2=A0updates SCTP path management:/<br>
-If this is to be considered as a PS, it /specifies/ the update.<br>
<br>
Section 4.1: (language, there is no ordering so avoid this usage):<br>
/In order to minimize performance impact during failover/<br>
to<br>
/To minimise the performance impact during failover/<br>
<br>
Section 4.1 (structure)<br>
<br>
- If I understand correctly, the first two paras, including the 2 bullets<b=
r>
are actually informative discussion to introduce the method, if this is<br>
the case could these be moved to section 4, so thats action 4.1 includes<br=
>
the RFC2119 protocol update.<br>
<br>
Section 4.1: (NiT in language)<br>
/tweaking/tuning/<br>
<br>
/This proposal introduces/This new method introduces/<br>
<br>
<br>
Requirement=C2=A0 1 (RFC2119)<br>
/The recommended value of PFMR =3D 0=C2=A0 when quick failover is used.=C2=
=A0 /<br>
- is this /RECOMMENDED/ ?<br>
<br>
Requirement 3: (NiT in language)<br>
/PF state with least error count/<br>
/PF state with the lowest error count/<br>
<br>
/In case of multiple PF/<br>
/When there are multiple PF/<br>
<br>
Requirement 4: (Clarity)<br>
<br>
/This<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification recommends that heartbeats be sen=
d to PF<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations independently from whether the Pat=
h Heartbeat<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 function (Section 8.3 of [RFC4960]) is enabled =
for the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination address or not./<br>
- This appears at the end of the requirement. I&#39;m not sure what is<br>
intended, could it be that this<br>
RECOMMENDS the use of heartbeats with PF, in which case I&#39;d have expect=
ed<br>
this requirement perhaps to be stated first?<br>
<br>
Requirement 7: (NiT in language)<br>
<br>
/state with least error count/<br>
/state with the lowest error count/<br>
<br>
/In=C2=A0 case of multiple destinations with same error count in inactive<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 state/<br>
/When there are multiple destinations with the same error count in the<br>
inactive state/<br>
<br>
Requirement 4: (RFC2119)<br>
<br>
<br>
/In order to support this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 prescription a sender SHOULD allow for incremen=
t of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination error counters up to some reasonabl=
e limit above<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PMR+1/<br>
/Therefore, a sender SHOULD allow for incrementing the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination error counters up to some reasonabl=
e limit above<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PMR+1/<br>
- I can see the goal of reasonable limit, but is this actually a &quot;limi=
t&quot;<br>
- that stops further incrementing or &quot;permits&quot; the value to be in=
cremented<br>
beyond PMR+1?<br>
<br>
/A=C2=A0 sender MAY choose to deploy other strategies than the above/<br>
- good to state this, but this is the second part of a SHOULD statement<br>
explaining options, as such I do not think it needs an upper case /MAY/<br>
and suspect that /may/ will be sufficient.<br>
<br>
Requirement 8: (NiT in language)<br>
<br>
/ACKs for chunks which have been transmitted to multiple<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations (i.e., a chunk which has been retr=
ansmitted to a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 different destination than the destination to w=
hich the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 was first transmitted) /<br>
/ACKs for chunks that have been transmitted to multiple<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations (i.e., a chunk that has been retra=
nsmitted to a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 different destination than the destination to w=
hich the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 was first transmitted) /<br>
- change /which/ to /that/<br>
<br>
Use upper case for /ack/?<br>
<br>
/In this respect then it is specified<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that bytes of a newly acknowledged chunk which =
has been<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 transmitted to multiple destinations SHOULD, wh=
en the conditions<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for such contribution is fulfilled following th=
e prescriptions<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 of Section 7.2 of [RFC4960], contribute to the =
congestion window<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 growth towards the destination to which the chu=
nk was last<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 transmitted. /<br>
- This clause is rather complex and long, please rephrase!<br>
<br>
<br>
/A SCTP sender MAY apply a different approach for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 both the error count handling as well as the co=
ngestion control<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 growth handling does it have unequivocally info=
rmation as to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 which destination (including multiple destinati=
ons) the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 reached.=C2=A0 /<br>
<br>
- This clause is rather complex, and hard to parse, please rephrase!<br>
<br>
<br>
Requirement 10: (Clarity)<br>
<br>
/SCTP SHOULD provide the means to expose the PF state /<br>
- Is this the SCTP stack should expose to the ULP, please clarify, and use<=
br>
language similar to other SCTP RFCs.<br>
<br>
/Active state ./ - remove space before stop,<br>
<br>
<br>
/When=C2=A0 doing such SCTP MUST /<br>
/When=C2=A0 this, the SCTP stack MUST /<br>
<br>
/suppress exposure of PF state to ULP.=C2=A0 /<br>
/suppress exposure of PF state to the ULP.=C2=A0 /<br>
<br>
- I found this requirement not so clearly explained, and rather hard to<br>
comprehend from the text.<br>
<br>
Section 4.2: (RFC2119, Clarity)<br>
<br>
/Post failover then, by [RFC4960] behavior, an SCTP sender migrates<br>
=C2=A0 =C2=A0the traffic back to the original primary destination once this=
<br>
=C2=A0 =C2=A0destination becomes active anew.=C2=A0 /<br>
- This doesn=E2=80=99t seem to make sense.<br>
<br>
No 1<br>
<br>
/Any setting of PSMR &lt; PFMR<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0MUST be rejected by the implementation./<br>
- MUST be rejected seems odd. Can you phrase this the other way around?<br>
The PSMR MUST be set so that PSMAR&gt;=3DPFMR.<br>
- This seems to contradict the previous SHOULD.<br>
<br>
No 2 and 3 do not introduce RFC 2119 requirements. Is this intentional, if<=
br>
so why?<br>
<br>
No 4<br>
/support set of PSMR =3D PFMR/<br>
/support the setting of PSMR =3D PFMR/<br>
<br>
<br>
/ We recommend that SCTP-PF sticks to the standard RFC4960 switchback<br>
=C2=A0 =C2=A0behavior as default/<br>
- is this intended to be:<br>
/This specifications RECOMMENDS a default configuration that uses standard<=
br>
RFC4960 switchback./<br>
<br>
/However in order to support//However, to support/<br>
<br>
- does this section need the MAYs in capital letters, since it follows a<br=
>
SHOULD?<br>
<br>
=E2=80=94<br>
<br>
Section 6:<br>
<br>
I=E2=80=99m happy with this clause, if it is correct. For clarity I=E2=80=
=99d prefer the<br>
section is prefixed by something like:<br>
=E2=80=9CSecutity considerations for the use of SCTP are discussed in RFCxx=
x and<br>
RFCyyyy.=E2=80=9D<br>
<br>
Appendices: (Structure)<br>
<br>
Two appendices are provided, but seem not to be described in the body of<br=
>
the specification. - please either add references were appropriate to the<b=
r>
appendices or remove them.<br>
<br>
Proposed change of status<br>
<br>
I would expect such a section to b marked for removal before publication<br=
>
by RFC-Ed (since this is ONLY an AD/IESG decision - that provides a couple<=
br>
of short paras that document the evolution of the draft from EXP to PS,<br>
and motivate that the experimental considerations are no longer an issue.<b=
r>
I believe the authors have clearly put this argument in the past, and hope<=
br>
that this is not a difficult section to add.<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--047d7b3a818c7c27a50504a85aee--


From nobody Tue Oct  7 01:53:39 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40E41A8A0B for <tsvwg@ietfa.amsl.com>; Tue,  7 Oct 2014 01:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.135
X-Spam-Level: 
X-Spam-Status: No, score=0.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=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 Jov0Bqrx3fdh for <tsvwg@ietfa.amsl.com>; Tue,  7 Oct 2014 01:53:33 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEA1A1A0022 for <tsvwg@ietf.org>; Tue,  7 Oct 2014 01:53:32 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id m15so8568743wgh.28 for <tsvwg@ietf.org>; Tue, 07 Oct 2014 01:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=xIXFOzDd4vSa1vJIxr0ZubUlFNjz2NfVhQx4oN57+hk=; b=AonjKVKY0dogaVvHRjUv5eqHmS9/6GXl1iQixw7zX89l/T1VahFGdTfGAwfs1pa9oE QA029O8xQ/pW2JsKr/7gzlp0f64cUUwZZCeIlBbrvrr2OCltzbzSeIs+wPWO3RCfV9TA TIrU1OslBuDyTyPDUouX/7/zzu6ELZYO9DZX8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=xIXFOzDd4vSa1vJIxr0ZubUlFNjz2NfVhQx4oN57+hk=; b=QSCT1BjHudFC+TZCIstgX6CW6shzOy4TkJzmSbUuGh5v6OPYYMUrRB+85ecvlflSkQ Ty/Vj6+DnnhGUd61r5fpt4/1vRLNSWshKo2p2e8Av+zEEtaKxPAbFp6tVYov11I3Gjm5 boJBzyDum35dNVqd3jQG5wXDAXDGhxYkp6wF4XY5vtpy4D42qopSctPYCoUdx5n9SzsI Ri1RHVDWFx3VXEsI7oMHb3kXAgmmzdIWfKGk0yottyuDHWcFgMck4Wq+gk4fZ8MjAhzi bLIR9M4xJYBmHAMYaeGU9pSrKlfpH0AO8Fh15BXT0m/hXT1O1BlBvj8S8Cm07/PLnSp7 Cpxg==
X-Gm-Message-State: ALoCoQkQaUJEnkccXnQMajHmo52KNtrshfm2fRlRRnPdkGv4wVQmVtbkWpIrZe0mBL6NQHSp3Rb7yPVKD5YTvGcE5vuTcWABhKGiXh4e+BGNAI28RLU84qY=
X-Received: by 10.194.95.8 with SMTP id dg8mr3077726wjb.1.1412672011604; Tue, 07 Oct 2014 01:53:31 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <54281D3C.1020208@erg.abdn.ac.uk> <1F66672E-C132-4113-9E8B-3C9E3876A7D1@fh-muenster.de> <3c2d43921928ebc0435cd8456f4172df.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <3c2d43921928ebc0435cd8456f4172df.squirrel@www.erg.abdn.ac.uk>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJJcjN4cq3TrvkvmHm+p+GH3b5otgLVl9MeAiNI3gWbCWWZgA==
Date: Tue, 7 Oct 2014 10:53:30 +0200
Message-ID: <3ececb0d794213c7a5eecb745fd16543@mail.gmail.com>
To: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/fC75e1xs6iOaHM-tR4BOyXk6qNQ
Cc: Michael Tuexen <tuexen@fh-muenster.de>
Subject: Re: [tsvwg] WGLC conclusion for draft-ietf-tsvwg-sctp-prpolicies
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Oct 2014 08:53:35 -0000

Hi,

I am happy with the updates made in this revision which resolves all my
issues.
 It have no further comments and support to progress to submit this
version for PS.

BR, Karen

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of
> gorry@erg.abdn.ac.uk
> Sent: 28. september 2014 21:23
> To: tsvwg@ietf.org
> Cc: Michael Tuexen
> Subject: [tsvwg] WGLC conclusion for draft-ietf-tsvwg-sctp-prpolicies
>
> The above draft completed WGLC with minor comments, and resulted in a
> new revision that just been published. If you commented during the WGLC,
> please check that this revision resolves your issues, or send a message
to the
> tsvwg list.
>
> If there are no new comments, the chairs plan to submit this to our AD
with
> the intended status of PS (including an INFO section describing the
socket
> API).
>
> Best wishes,
>
> Gorry
> (tsvwg co-chair)


From nobody Tue Oct  7 09:05:25 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1594D1A6FC2; Tue,  7 Oct 2014 09:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 npJ7K2BhGgid; Tue,  7 Oct 2014 09:05:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 928C91A01A5; Tue,  7 Oct 2014 09:05:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141007160515.21447.34119.idtracker@ietfa.amsl.com>
Date: Tue, 07 Oct 2014 09:05:15 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/vjnMhW8NssvLzF1qIzXlIh1sZVc
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-11.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Oct 2014 16:05:17 -0000

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           : Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains
        Authors         : Georgios Karagiannis
                          Anurag Bhargava
	Filename        : draft-ietf-tsvwg-rsvp-pcn-11.txt
	Pages           : 29
	Date            : 2014-10-07

Abstract:
   This document specifies extensions to Generic Aggregated RSVP
   RFC 4860 for support of the PCN Controlled Load (CL) and Single
   Marking (SM) edge behaviors over a Diffserv cloud using Pre-
   Congestion Notification.





The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rsvp-pcn-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct  7 09:09:46 2014
Return-Path: <georgios.karagiannis@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4BCF1A023E for <tsvwg@ietfa.amsl.com>; Tue,  7 Oct 2014 09:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 lAVXXwDAoRGq for <tsvwg@ietfa.amsl.com>; Tue,  7 Oct 2014 09:09:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67B431A0233 for <tsvwg@ietf.org>; Tue,  7 Oct 2014 09:09:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKH60701; Tue, 07 Oct 2014 16:09:40 +0000 (GMT)
Received: from LHREML516-MBX.china.huawei.com ([169.254.1.85]) by lhreml406-hub.china.huawei.com ([10.201.5.243]) with mapi id 14.03.0158.001; Tue, 7 Oct 2014 17:09:38 +0100
From: Georgios Karagiannis <georgios.karagiannis@huawei.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-11.txt
Thread-Index: AQHP4kiaXwm0voMTmEG2U7G7GZ98e5wkzL/Q
Date: Tue, 7 Oct 2014 16:09:38 +0000
Message-ID: <C5034E44CD620A44971BAAEB372655DC637A64@LHREML516-MBX.china.huawei.com>
References: <20141007160515.21447.34119.idtracker@ietfa.amsl.com>
In-Reply-To: <20141007160515.21447.34119.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.64.103]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/kgRzxepdn7xywS9uS7VgqVxxc1E
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-11.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Oct 2014 16:09:44 -0000

RGVhciBhbGwsDQoNClBsZWFzZSBub3RlIHRoYXQgdGhlIDExIHZlcnNpb24gb2YgdGhlIGRyYWZ0
LWlldGYtdHN2d2ctcnN2cC1wY24gaGFzIGp1c3QgYmVlbiBzdWJtaXR0ZWQuDQpJbiBvdXIgb3Bp
bmlvbiwgYWxsIGNvbW1lbnRzIHJlY2VpdmVkIGZyb20gdGhlIElFU0cgaGF2ZSBiZWVuIGFkZHJl
c3NlZC4gDQpNYW55IHRoYW5rcyB0byBEYXZpZCBCbGFjayBmb3IgdGhlIGhlbHAgb24gYWRkcmVz
c2luZyB0aGVzZSBjb21tZW50cy4NCg0KQmVzdCByZWdhcmRzLA0KR2Vvcmdpb3MNCg0KDQo+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHRzdndnIFttYWlsdG86dHN2d2ctYm91
bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGludGVybmV0LQ0KPiBkcmFmdHNAaWV0Zi5vcmcN
Cj4gU2VudDogVHVlc2RheSwgT2N0b2JlciAwNywgMjAxNCA2OjA1IFBNDQo+IFRvOiBpLWQtYW5u
b3VuY2VAaWV0Zi5vcmcNCj4gQ2M6IHRzdndnQGlldGYub3JnDQo+IFN1YmplY3Q6IFt0c3Z3Z10g
SS1EIEFjdGlvbjogZHJhZnQtaWV0Zi10c3Z3Zy1yc3ZwLXBjbi0xMS50eHQNCj4gDQo+IA0KPiBB
IE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5l
dC1EcmFmdHMgZGlyZWN0b3JpZXMuDQo+ICBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRo
ZSBUcmFuc3BvcnQgQXJlYSBXb3JraW5nIEdyb3VwIFdvcmtpbmcgR3JvdXANCj4gb2YgdGhlIElF
VEYuDQo+IA0KPiAgICAgICAgIFRpdGxlICAgICAgICAgICA6IEdlbmVyaWMgQWdncmVnYXRpb24g
b2YgUmVzb3VyY2UgUmVTZXJWYXRpb24gUHJvdG9jb2wNCj4gKFJTVlApIGZvciBJUHY0IEFuZCBJ
UHY2IFJlc2VydmF0aW9ucyBvdmVyIFBDTiBkb21haW5zDQo+ICAgICAgICAgQXV0aG9ycyAgICAg
ICAgIDogR2Vvcmdpb3MgS2FyYWdpYW5uaXMNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICBB
bnVyYWcgQmhhcmdhdmENCj4gCUZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtdHN2d2ctcnN2
cC1wY24tMTEudHh0DQo+IAlQYWdlcyAgICAgICAgICAgOiAyOQ0KPiAJRGF0ZSAgICAgICAgICAg
IDogMjAxNC0xMC0wNw0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgIFRoaXMgZG9jdW1lbnQgc3BlY2lm
aWVzIGV4dGVuc2lvbnMgdG8gR2VuZXJpYyBBZ2dyZWdhdGVkIFJTVlANCj4gICAgUkZDIDQ4NjAg
Zm9yIHN1cHBvcnQgb2YgdGhlIFBDTiBDb250cm9sbGVkIExvYWQgKENMKSBhbmQgU2luZ2xlDQo+
ICAgIE1hcmtpbmcgKFNNKSBlZGdlIGJlaGF2aW9ycyBvdmVyIGEgRGlmZnNlcnYgY2xvdWQgdXNp
bmcgUHJlLQ0KPiAgICBDb25nZXN0aW9uIE5vdGlmaWNhdGlvbi4NCj4gDQo+IA0KPiANCj4gDQo+
IA0KPiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoN
Cj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1yc3Zw
LXBjbi8NCj4gDQo+IFRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZhaWxhYmxlIGF0
Og0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXRzdndnLXJzdnAtcGNu
LTExDQo+IA0KPiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUg
YXQ6DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtdHN2d2ct
cnN2cC1wY24tMTENCj4gDQo+IA0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291
cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+IHVudGlsIHRoZSBo
dG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcu
DQo+IA0KPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBG
VFAgYXQ6DQo+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQoNCg==


From nobody Wed Oct  8 00:14:47 2014
Return-Path: <weixinpeng@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 884E21A003A for <tsvwg@ietfa.amsl.com>; Wed,  8 Oct 2014 00:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 4CUuvKnu-J2v for <tsvwg@ietfa.amsl.com>; Wed,  8 Oct 2014 00:14:41 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878A01A0071 for <tsvwg@ietf.org>; Wed,  8 Oct 2014 00:14:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNK45808; Wed, 08 Oct 2014 07:14:38 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 8 Oct 2014 08:14:37 +0100
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.43]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Wed, 8 Oct 2014 15:14:30 +0800
From: Weixinpeng <weixinpeng@huawei.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
Thread-Index: AQHP4qzwvjN1F5c5n0WWmxXSC80rUpwllOwA
Date: Wed, 8 Oct 2014 07:14:29 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46D8404E9@nkgeml507-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.176]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_GCsfwXoKTV-6e-2m7OHVJWOCM0
Subject: [tsvwg] FW: New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Oct 2014 07:14:44 -0000

SGkgYWxsLA0KQSBuZXcgdmVyc2lvbiBvZiBuZXR3b3JrIGJhc2VkIGNvbmdlc3Rpb24gY29udHJv
bCBkcmFmdCBoYXMgYmVlbiBzdWJtaXR0ZWQuDQoNCkluIHRoZSBsYXN0IFRvcm9udG8gbWVldGlu
Zywgd2UgcHJlc2VudGVkIG91ciBzaW11bGF0aW9uIHJlc3VsdCBhYm91dCB0aGUgaW1wYWN0cyBv
ZiBuZXR3b3JrIGJhc2VkIGNvbmdlc3Rpb24gY29udHJvbCBvbiBlbmQtdG8tZW5kIGNvbmdlc3Rp
b24gY29udHJvbCBhbmQgdGhlIHJlc3VsdCBzZWVtcyBhY2NlcHRhYmxlIHRvIHRoZSBwZW9wbGUu
DQoNCkluIHRoaXMgbmV3IHZlcnNpb24sIHNldmVyYWwgc21hbGwgaXNzdWVzIHRoYXQgcGVvcGxl
IG1heSBiZSBpbnRlcmVzdGVkIGluIGFyZSBjbGFyaWZpZWQsIGluY2x1ZGluZyB3aGF0IGluZm9y
bWF0aW9uIHdvdWxkIGJlIGNvbnZleWVkIGZyb20gdHVubmVsIGVncmVzcyB0byBpbmdyZXNzIGZv
ciBjb25nZXN0aW9uIGNvbnRyb2wsIGhvdyB0dW5uZWwgaW5ncmVzcyBjb3VsZCB1c2UgdGhlIGlu
Zm9ybWF0aW9uIHRvIHJlZHVjZSBjb25nZXN0aW9uIGxldmVsIGluIHR1bm5lbC4NCg0KU28gbm93
IHdlIHdhbnQgdG8ga25vdyB3aGV0aGVyIHlvdSBoYXZlIGFueSBjb21tZW50cyBvciBzdWdnZXN0
aW9ucyBmb3IgdGhpcz8gDQoNCkJlc3QgUmVnYXJkcywNClhpbnBlbmcNCg0KPi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86
aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPlNlbnQ6IFdlZG5lc2RheSwgT2N0b2JlciAwOCwg
MjAxNCAxMjowNCBQTQ0KPlRvOiBXZWl4aW5wZW5nOyBMaW5nbGkgRGVuZzsgWmh1bGVpIChNQkIg
UmVzZWFyY2gpOyBaaHVsZWkgKE1CQiBSZXNlYXJjaCk7DQo+V2VpeGlucGVuZzsgTGluZ2xpIERl
bmcNCj5TdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+ZHJhZnQtd2VpLXRz
dndnLXR1bm5lbC1jb25nZXN0aW9uLWZlZWRiYWNrLTAzLnR4dA0KPg0KPg0KPkEgbmV3IHZlcnNp
b24gb2YgSS1ELCBkcmFmdC13ZWktdHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZGJhY2stMDMu
dHh0DQo+aGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBYaW5wZW5nIFdlaSBhbmQg
cG9zdGVkIHRvIHRoZSBJRVRGDQo+cmVwb3NpdG9yeS4NCj4NCj5OYW1lOgkJZHJhZnQtd2VpLXRz
dndnLXR1bm5lbC1jb25nZXN0aW9uLWZlZWRiYWNrDQo+UmV2aXNpb246CTAzDQo+VGl0bGU6CQlU
dW5uZWwgQ29uZ2VzdGlvbiBGZWVkYmFjaw0KPkRvY3VtZW50IGRhdGU6CTIwMTQtMTAtMDgNCj5H
cm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lvbg0KPlBhZ2VzOgkJMjANCj5VUkw6DQo+aHR0cDov
L3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtd2VpLXRzdndnLXR1bm5lbC1jb25n
ZXN0aW9uLWZlZWRiDQo+YWNrLTAzLnR4dA0KPlN0YXR1czoNCj5odHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC13ZWktdHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZGJhY2sv
DQo+SHRtbGl6ZWQ6DQo+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtd2VpLXRzdndn
LXR1bm5lbC1jb25nZXN0aW9uLWZlZWRiYWNrLTAzDQo+RGlmZjoNCj5odHRwOi8vd3d3LmlldGYu
b3JnL3JmY2RpZmY/dXJsMj1kcmFmdC13ZWktdHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZGJh
Y2stDQo+MDMNCj4NCj5BYnN0cmFjdDoNCj4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIG1l
Y2hhbmlzbSB0byBjYWxjdWxhdGUgY29uZ2VzdGlvbiBvZiBhDQo+ICAgdHVubmVsIHNlZ21lbnQg
YmFzZWQgb24gUkZDIDYwNDAgcmVjb21tZW5kYXRpb25zLCBhbmQgYSBmZWVkYmFjaw0KPiAgIHBy
b3RvY29sIGJ5IHdoaWNoIHRvIHNlbmQgdGhlIG1lYXN1cmVkIGNvbmdlc3Rpb24gb2YgdGhlIHR1
bm5lbCBmcm9tDQo+ICAgZWdyZXNzIHRvIGluZ3Jlc3Mgcm91dGVyLiBBIGJhc2ljICBtb2RlbCBm
b3IgbWVhc3VyaW5nIHR1bm5lbA0KPiAgIGNvbmdlc3Rpb24gYW5kIGZlZWRiYWNrIGlzIGRlc2Ny
aWJlZCwgYW5kIGEgcHJvdG9jb2wgZm9yIGNhcnJ5aW5nIHRoZQ0KPiAgIGZlZWRiYWNrIGRhdGEg
aXMgb3V0bGluZWQuDQo+DQo+DQo+DQo+DQo+DQo+UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFr
ZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPnVudGls
IHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0
Zi5vcmcuDQo+DQo+VGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K


From nobody Wed Oct  8 00:38:26 2014
Return-Path: <lei.zhu@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1641A0074 for <tsvwg@ietfa.amsl.com>; Wed,  8 Oct 2014 00:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 BXLr1XB_Vjen for <tsvwg@ietfa.amsl.com>; Wed,  8 Oct 2014 00:38:23 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78E181A0072 for <tsvwg@ietf.org>; Wed,  8 Oct 2014 00:38:23 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNK48258; Wed, 08 Oct 2014 07:38:22 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 8 Oct 2014 08:38:21 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.18]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 8 Oct 2014 15:38:09 +0800
From: "Zhulei (MBB Research)" <lei.zhu@huawei.com>
To: Weixinpeng <weixinpeng@huawei.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
Thread-Index: AQHP4qzwvjN1F5c5n0WWmxXSC80rUpwllOwAgAA4yJA=
Date: Wed, 8 Oct 2014 07:38:08 +0000
Message-ID: <470F27D1263A1B4EB73491ED995DE625259660FD@NKGEML512-MBS.china.huawei.com>
References: <C5C3BB522B1DDF478AA09545169155B46D8404E9@nkgeml507-mbx.china.huawei.com>
In-Reply-To: <C5C3BB522B1DDF478AA09545169155B46D8404E9@nkgeml507-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.65.68]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7laJjzLY4J7L29G0cVlRBrJrphA
Subject: Re: [tsvwg] New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Oct 2014 07:38:25 -0000

SGkgWGlucGVuZyBhbmQgYWxsLA0KDQpNeSBwZXJzb25hbCBub3RlcyBmcm9tIGxhc3QgSUVURiBt
ZWV0aW5nIGFyZSBmb2xsb3dpbmc6DQoxKSBGcmVkIGxpa2VzIHRvIHNlZSBjb25nZXN0aW9uIGlu
Zm9ybWF0aW9uIGZlZWRiYWNrIHRocm91Z2ggbm9ydGggYm91bmQsIGFzIGl0IGVuYWJsZXMgaGFu
ZGxlIOKAmHNoaWZ04oCZIG9wZXJhdGlvbiBpbiBjYXNlIG9mIGNvbmdlc3Rpb24uIEkgd291bGQg
c2VlIHRoaXMgY2hhbmdlIGFuZCBhZG9wdGlvbiB0byBub3RpZnkgbm9ydGhib3VuZCBpcyBhbHNv
IGFwcGxpY2FibGUgdG8gdGhpcyB1c2UuIDIpIElmIHRoaXMgZmVlZGJhY2sgaXMgY29tcGF0aWJs
ZSB3aXRoIENvbmV4LCB3aGljaCB3YXMgYWRkaW5nIGF1ZGl0IHNpZ25hbGluZyB0byBjb3VudCBj
b250cmlidXRpb24gdG8gY29uZ2VzdGlvbiBiYXNlZCBvbiBFQ04gcHJvdG9jb2wuIE15IHVuZGVy
c3RhbmRpbmcgaXMgdGhhdCB0aGlzIHByb3Bvc2FsIGlzIGNvbXBsZW1lbnRhcnkgdG8gY29uZXgg
YW5kIG90aGVyIEVDTiBtZWNoYW5pc20sIGFuZCBoYXMgaXRzIG93bmVkIGFwcGxpY2F0aW9uIHRv
IHRoaXMgY29uZ2VzdGlvbiBpbmZvcm1hdGlvbiBpbiBwYXRoLiBBIGZldyBjbGFyaWZpY2F0aW9u
IHF1ZXN0aW9ucyBmcm9tIGJyb3dzZXIgcGVyc3BlY3RpdmUsIHdoaWNoIG1ham9yaXR5IHBvaW50
IGlzIHRvIGVuc3VyZSB0aGF0IGl0IGlzIGZvciBuZXR3b3JrIG9wZXJhdGlvbiB1c2VzLiANCg0K
SWYgc28sIHRob3NlIGNvbW1lbnRzIGFyZSBqdXN0IGNsYXJpZmllZCBpbiBsYXN0IG1lZXRpbmcu
IFdlIGhhZCBjbGFyaWZpZWQgcHJvYmxlbSBzdGF0ZW1lbnRzLCBtb2JpbGUgb3BlcmF0b3Igc3Vw
cG9ydCBhbmQgc29tZSBjb21tZW50cyBpbiB0aGUgbWVldGluZy4gSWYgdGhlIHdvcmtpbmcgZ3Jv
dXAgZG9lcyBub3Qgd2FpdCBmb3IgbW9yZSBzdXBwb3J0cyB0byB0aGlzIHByb3Bvc2FsLCBJIGNh
biBzZWUgYWRvcHRpb24gcHJvY2VzcyBxdWVzdGlvbiBpcyBicm91Z2h0Lg0KDQpCZXN0IHJlZ2Fy
ZHMsDQpaaHUgTGVpDQoNCj09PT09PT09DQoNCkhpIGFsbCwNCkEgbmV3IHZlcnNpb24gb2YgbmV0
d29yayBiYXNlZCBjb25nZXN0aW9uIGNvbnRyb2wgZHJhZnQgaGFzIGJlZW4gc3VibWl0dGVkLg0K
DQpJbiB0aGUgbGFzdCBUb3JvbnRvIG1lZXRpbmcsIHdlIHByZXNlbnRlZCBvdXIgc2ltdWxhdGlv
biByZXN1bHQgYWJvdXQgdGhlIGltcGFjdHMgb2YgbmV0d29yayBiYXNlZCBjb25nZXN0aW9uIGNv
bnRyb2wgb24gZW5kLXRvLWVuZCBjb25nZXN0aW9uIGNvbnRyb2wgYW5kIHRoZSByZXN1bHQgc2Vl
bXMgYWNjZXB0YWJsZSB0byB0aGUgcGVvcGxlLg0KDQpJbiB0aGlzIG5ldyB2ZXJzaW9uLCBzZXZl
cmFsIHNtYWxsIGlzc3VlcyB0aGF0IHBlb3BsZSBtYXkgYmUgaW50ZXJlc3RlZCBpbiBhcmUgY2xh
cmlmaWVkLCBpbmNsdWRpbmcgd2hhdCBpbmZvcm1hdGlvbiB3b3VsZCBiZSBjb252ZXllZCBmcm9t
IHR1bm5lbCBlZ3Jlc3MgdG8gaW5ncmVzcyBmb3IgY29uZ2VzdGlvbiBjb250cm9sLCBob3cgdHVu
bmVsIGluZ3Jlc3MgY291bGQgdXNlIHRoZSBpbmZvcm1hdGlvbiB0byByZWR1Y2UgY29uZ2VzdGlv
biBsZXZlbCBpbiB0dW5uZWwuDQoNClNvIG5vdyB3ZSB3YW50IHRvIGtub3cgd2hldGhlciB5b3Ug
aGF2ZSBhbnkgY29tbWVudHMgb3Igc3VnZ2VzdGlvbnMgZm9yIHRoaXM/IA0KDQpCZXN0IFJlZ2Fy
ZHMsDQpYaW5wZW5nDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj5T
ZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMDgsIDIwMTQgMTI6MDQgUE0NCj5UbzogV2VpeGlucGVu
ZzsgTGluZ2xpIERlbmc7IFpodWxlaSAoTUJCIFJlc2VhcmNoKTsgWmh1bGVpIChNQkIgDQo+UmVz
ZWFyY2gpOyBXZWl4aW5wZW5nOyBMaW5nbGkgRGVuZw0KPlN1YmplY3Q6IE5ldyBWZXJzaW9uIE5v
dGlmaWNhdGlvbiBmb3INCj5kcmFmdC13ZWktdHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZGJh
Y2stMDMudHh0DQo+DQo+DQo+QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXdlaS10c3Z3Zy10
dW5uZWwtY29uZ2VzdGlvbi1mZWVkYmFjay0wMy50eHQNCj5oYXMgYmVlbiBzdWNjZXNzZnVsbHkg
c3VibWl0dGVkIGJ5IFhpbnBlbmcgV2VpIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgDQo+cmVwb3Np
dG9yeS4NCj4NCj5OYW1lOgkJZHJhZnQtd2VpLXRzdndnLXR1bm5lbC1jb25nZXN0aW9uLWZlZWRi
YWNrDQo+UmV2aXNpb246CTAzDQo+VGl0bGU6CQlUdW5uZWwgQ29uZ2VzdGlvbiBGZWVkYmFjaw0K
PkRvY3VtZW50IGRhdGU6CTIwMTQtMTAtMDgNCj5Hcm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lv
bg0KPlBhZ2VzOgkJMjANCj5VUkw6DQo+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtd2VpLXRzdndnLXR1bm5lbC1jb25nZXN0aW9uLWYNCj5lZWRiDQo+YWNrLTAzLnR4
dA0KPlN0YXR1czoNCj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC13ZWkt
dHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZA0KPmJhY2svDQo+SHRtbGl6ZWQ6DQo+aHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtd2VpLXRzdndnLXR1bm5lbC1jb25nZXN0aW9uLWZl
ZWRiYWNrLTANCj4zDQo+RGlmZjoNCj5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC13ZWktdHN2d2ctdHVubmVsLWNvbmdlc3Rpb24tZmVlZA0KPmJhY2stDQo+MDMNCj4NCj5B
YnN0cmFjdDoNCj4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIG1lY2hhbmlzbSB0byBjYWxj
dWxhdGUgY29uZ2VzdGlvbiBvZiBhDQo+ICAgdHVubmVsIHNlZ21lbnQgYmFzZWQgb24gUkZDIDYw
NDAgcmVjb21tZW5kYXRpb25zLCBhbmQgYSBmZWVkYmFjaw0KPiAgIHByb3RvY29sIGJ5IHdoaWNo
IHRvIHNlbmQgdGhlIG1lYXN1cmVkIGNvbmdlc3Rpb24gb2YgdGhlIHR1bm5lbCBmcm9tDQo+ICAg
ZWdyZXNzIHRvIGluZ3Jlc3Mgcm91dGVyLiBBIGJhc2ljICBtb2RlbCBmb3IgbWVhc3VyaW5nIHR1
bm5lbA0KPiAgIGNvbmdlc3Rpb24gYW5kIGZlZWRiYWNrIGlzIGRlc2NyaWJlZCwgYW5kIGEgcHJv
dG9jb2wgZm9yIGNhcnJ5aW5nIHRoZQ0KPiAgIGZlZWRiYWNrIGRhdGEgaXMgb3V0bGluZWQuDQo+
DQo+DQo+DQo+DQo+DQo+UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2YgDQo+c3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQg
dmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPg0KPlRo
ZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Thu Oct  9 10:03:17 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0801AD376 for <tsvwg@ietfa.amsl.com>; Thu,  9 Oct 2014 10:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.087
X-Spam-Level: 
X-Spam-Status: No, score=-5.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 SQmeELfAYytr for <tsvwg@ietfa.amsl.com>; Thu,  9 Oct 2014 10:02:56 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ADE81AD377 for <tsvwg@ietf.org>; Thu,  9 Oct 2014 10:02:37 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s99H2ZOV008667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Thu, 9 Oct 2014 13:02:35 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s99H2ZOV008667
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1412874155; bh=lpZXEVikc8T533V4Z/kkQQJFnuE=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=TLA7cpx/sdpIQawA+VPxUkxE5reAfrJ2t5PIvwaIxlZUH3VsSKOgsFAcIbmEOSRLH Nl4i8NJcqxBWsEPdRCUiElByMeIq3DUxe7ZwMzWBhCEyoSgzViJq4NWs3l3OujjlUa wFzk5QCYZy/k04Iy/mw3WwKBCNNqEd+KjSYsIII4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s99H2ZOV008667
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd05.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Thu, 9 Oct 2014 13:02:05 -0400
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s99H2Mib013351 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Thu, 9 Oct 2014 13:02:23 -0400
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub27.corp.emc.com (10.254.110.183) with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 9 Oct 2014 13:02:22 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Thu, 9 Oct 2014 13:02:22 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Document Action: 'Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains' to Experimental RFC (draft-ietf-tsvwg-rsvp-pcn-11.txt)
Thread-Index: AQHP48ciIiJ77VJf50yN9YCi3towoZwn/JAQ
Date: Thu, 9 Oct 2014 17:02:21 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493605188A@MX104CL02.corp.emc.com>
References: <20141009134608.17023.558.idtracker@ietfa.amsl.com>
In-Reply-To: <20141009134608.17023.558.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.160.153.124]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/zXNH2JrjUWHYGUAqU0wqp9H7SLg
Subject: [tsvwg] FW: Document Action: 'Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains' to Experimental RFC (draft-ietf-tsvwg-rsvp-pcn-11.txt)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 09 Oct 2014 17:03:07 -0000

FYI - I thought I'd pass along the good news, along with my thanks the auth=
ors, and everyone else who contributed, especially Francois LeFaucheur, who=
 was not only heavily involved in working on this draft during WG LC, but a=
lso handled the RSVP parameter allocation for it as the Designated Expert f=
or that registry.

Thanks,
--David

-----Original Message-----
From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of Th=
e IESG
Sent: Thursday, October 09, 2014 9:46 AM
To: IETF-Announce
Cc: RFC Editor
Subject: Document Action: 'Generic Aggregation of Resource ReSerVation Prot=
ocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains' to Experimenta=
l RFC (draft-ietf-tsvwg-rsvp-pcn-11.txt)

The IESG has approved the following document:
- 'Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4
   And IPv6 Reservations over PCN domains'
  (draft-ietf-tsvwg-rsvp-pcn-11.txt) as Experimental RFC

This document is the product of the Transport Area Working Group.

The IESG contact persons are Spencer Dawkins and Martin Stiemerling.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/





Technical Summary

   This document extends Generic Aggregated RSVP functionality (see
   RFC 4860) in order to support admission control for Pre-Congestion
   Notification (PCN).

   Experimental RFC is requested because this is new functionality
   for which implementation and usage experience is desired
   before producing a proposed standard.  The title page header
   indicates the intended Experimental status.

Working Group Summary

   The document spent a while in the WG.  As a result of WG Last
   Call, the PCN admission control decision point was moved from the
   ingress node to the egress node in order to better match RFC 4860
   functionality, and RSVP admission control is no longer performed
   for the end-to-end reservation wrt the aggregate reservation for
   the PCN domain, as PCN admission control at the egress node suffices.

Document Quality

   Francois LeFaucheur
   and Bob Briscoe reviewed during WG Last Call, and provided comments
   that resulted in significant improvements.
   RSVP Directorate Review was performed by Scott Bradner.  There are
   no known implementations due in part to the significant
   changes made as a result of WG Last Call. =20

Personnel

   Document Shepherd: David Black (tsvwg WG co-chair)
   Responsible Area Director: Spencer Dawkins (Transport)


From nobody Tue Oct 14 00:52:09 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD0631A6FC8; Tue, 14 Oct 2014 00:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 a6ISinaLs_MU; Tue, 14 Oct 2014 00:52:07 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C957B1A6FC4; Tue, 14 Oct 2014 00:52:06 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 431D02B44A7; Tue, 14 Oct 2014 08:52:05 +0100 (BST)
Received: from Gorrys-MacBook-Air.local (synology.erg.abdn.ac.uk [139.133.204.3]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7B87C2B4039; Tue, 14 Oct 2014 08:51:51 +0100 (BST)
Message-ID: <543CD616.5090509@erg.abdn.ac.uk>
Date: Tue, 14 Oct 2014 08:51:50 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/qXauiG__SYsZBD5vvo8WeDHGs_o
Cc: tsvwg-chairs@ietf.org
Subject: [tsvwg] WGLC draft-ietf-tsvwg-port-use-05 : Working Group Last Call for comments due 29/10/2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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: Tue, 14 Oct 2014 07:52:08 -0000

This email announces the start of a working group last call to
confirm publication of draft-ietf-tsvwg-port-use,
"Recommendations for Transport Port Number Uses".  This document has
received significant feedback during the first WGLC review and has now 
been updated in response to this feedback. It is now thought to be ready 
to proceed to be published as a BCP.

Please send any comments to the TSVWG list. We are interesed in feedback 
from any who have read the latest version, including those who commented 
in the first WGLC.

The draft is available at:
https://tools.ietf.org/html/draft-ietf-tsvwg-port-use-05

This last call will run for TWO weeks, ending 29th October.

James, David, and Gorry
(TSVWG Chairs)
tsvwg-chairs@ietf.org


From nobody Mon Oct 20 03:55:39 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5EB11A802F for <tsvwg@ietfa.amsl.com>; Mon, 20 Oct 2014 03:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.322
X-Spam-Level: *
X-Spam-Status: No, score=1.322 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 eXbhAq3q0k0Z for <tsvwg@ietfa.amsl.com>; Mon, 20 Oct 2014 03:55:34 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B24E1A802B for <tsvwg@ietf.org>; Mon, 20 Oct 2014 03:55:33 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id a1so5057354wgh.33 for <tsvwg@ietf.org>; Mon, 20 Oct 2014 03:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to:cc :content-type; bh=mPh53zCXx0fb0G5La/XkCXjf+frEkxjPjZQVQCzCq7w=; b=Ph9vct9nLN6IUMLXUClgdHF0Bf/rq8dyjPexxon5N0uhy5xfUhD2erA582fAEZpRjl fZ/4vrT3P+MDfY7SAzGpoNvsXy0/h4KaKpu8KglL9omn7WoOJ2mJWL10Cob+LOcFIt7v 7Al1f8Ol3urAntdPkDUbAt15kdr7beIjc2slQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:cc:content-type; bh=mPh53zCXx0fb0G5La/XkCXjf+frEkxjPjZQVQCzCq7w=; b=JL4GtRRF2Sl7bL2Sco2V+M50XgWZ2XJUro27qcnATz9fvvgbhyBu9q0nJq2Dt6M676 ebNUIUk+1Pp0Rq9QMjDkz1TMGlOXtaExCGI+Wt/9Ql6r+XcV4vcCi/JkuEek5eEEGPRG rNkgXh0vWeI2xsBJ6lz1Z7faBlcLmaZ3u7rj1vTZTErjKWjVYnMtcc7kYWQy3QgwgALM gqXqCn4Oz3fml5Ygfnb0A02Q0BWWYkVcQiRCqShWwT0YL8/KNPLLElaQA46VCszW8T9Z 9leg9QOKBym37Zn3FwsR82Cqjo3l38I92fD7SLQqLV8G6LaaRYhR+M/tUp1gVTzMQ1tQ 3Yig==
X-Gm-Message-State: ALoCoQkof71PAbMakytEOiK01Vw5RM8XhjXifO+b0ClGrLrH+HQqfy0o2Fdq1fC6J/P5rHxW7v9wnJrFBTESdKWe39KPw+mtOF/YyH/Ggrgh2THatpTWFbc=
X-Received: by 10.194.77.199 with SMTP id u7mr32686030wjw.92.1413802532511; Mon, 20 Oct 2014 03:55:32 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/sVFrFUMeRgTvNRdWFe0li5gdowg==
Date: Mon, 20 Oct 2014 12:55:31 +0200
Message-ID: <5f41137198e1b54f2b0d5a66150f02d1@mail.gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=047d7bfd061cbbd8d20505d88d0b
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/L7h9mO95HFq558S1MTPZuORfkv0
Cc: tsvwg@ietf.org
Subject: [tsvwg]  SCTP ndata SCTP-PR priority
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 20 Oct 2014 10:55:37 -0000

--047d7bfd061cbbd8d20505d88d0b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Michael,



I think that it could be beneficiary in the ndata draft to relate to
(describe) how the ndata SS-PRIORITY scheduling may be used together

with the SCTP-PR priority policy to support =E2=80=9Caccelerated=E2=80=9D p=
rioritized
delivery in which the priority messages will not only be able to expel
lower priority data from the SND buffer but, also be able to outrace lower
priority messages (set to be send on lower priority streams) from  a
transmission perspective.



Apart from the relevance from a usecase perspective then I think that such
a description could be relevant also in order to emphasize the difference

in between the message priority of SCTP-PR and the stream priority of
ndata.  For example I think that it is particularly be relevant to state
explicitly that the priority given to stream does not carry over to (has no
relation to) the SCTP-PR message priority or the messages send on the
stream.



Alternatively =E2=80=93 juts for the sort of it - but this I think would be=
 an
addition to/a change of SCTP-PR, RFC6458 and ndata-draft =E2=80=93 then one=
 could
also look to that the default SCTP-PR message priority be inherited from
the stream priority SS-PRIORITY or one may ask for a special version of the
stream scheduling SS_PRIORITY* in which this be the case. This would
alleviate SCTP Users from having to pass also the prinfo down in case the
priority in wished managed simply by differentiation on streams. The stream
priority has advantages from a receive perspective in that it would be
feasible to  implement priority on a stream perspective on the reading
side. This is not feasible for the per message prioritization.



Thanks.



BR, Karen







***************************************************************************=
****************

*Karen Egede Nielsen*

Software Architect, Ph.D.



*Tieto Denmark A/S*

R&D, Telecom & Media

=C3=85have Parkvej 27, 8260 Viby J, DK-Denmark

Direct Phone / Mobile +45 25134336

E-mail: karen.nielsen@tieto.com

***************************************************************************=
**************

www.tieto.com



*Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the reader of
this message is not the intended recipient, you are hereby notified that
any unauthorised use, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it
from your computer. **Thank You.*

--047d7bfd061cbbd8d20505d88d0b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Diso-8859-1"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filte=
red medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3D"DA" link=3D"blue" vlink=3D"purple"><div cla=
ss=3D"WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Michael,=
</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US">I think that it could be beneficia=
ry in the ndata draft to relate to (describe) how the ndata SS-PRIORITY sch=
eduling may be used together</span></p><p class=3D"MsoNormal"><span lang=3D=
"EN-US">with the SCTP-PR priority policy to support =E2=80=9Caccelerated=E2=
=80=9D prioritized delivery in which the priority messages will not only be=
 able to expel lower priority data from the SND buffer but, also be able to=
 outrace lower priority messages (set to be send on lower priority streams)=
 from=C2=A0 a transmission perspective.</span></p><p class=3D"MsoNormal"><s=
pan lang=3D"EN-US">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN=
-US">Apart from the relevance from a usecase perspective then I think that =
such a description could be relevant also in order to emphasize the differe=
nce</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">in between the me=
ssage priority of SCTP-PR and the stream priority of ndata.=C2=A0 For examp=
le I think that it is particularly be relevant to state explicitly that the=
 priority given to stream does not carry over to (has no relation to) the S=
CTP-PR message priority or the messages send on the stream.</span></p><p cl=
ass=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p><p class=3D"MsoNorm=
al"><span lang=3D"EN-US">Alternatively =E2=80=93 juts for the sort of it - =
but this I think would be an addition to/a change of SCTP-PR, RFC6458 and n=
data-draft =E2=80=93 then one could also look to that the default SCTP-PR m=
essage priority be inherited from the stream priority SS-PRIORITY or one ma=
y ask for a special version of the stream scheduling SS_PRIORITY* in which =
this be the case. This would alleviate SCTP Users from having to pass also =
the prinfo down in case the priority in wished managed simply by differenti=
ation on streams. The stream priority has advantages from a receive perspec=
tive in that it would be feasible to =C2=A0implement priority on a stream p=
erspective on the reading side. This is not feasible for the per message pr=
ioritization.</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<=
/span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks.</span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p><p class=3D"MsoNo=
rmal"><span lang=3D"EN-US">BR, Karen</span></p><p class=3D"MsoNormal"><span=
 lang=3D"EN-US">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-GB=
">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"fon=
t-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0<=
/span><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal" style=3D"line-=
height:13.0pt;text-autospace:none"><b><span lang=3D"EN-GB" style=3D"font-si=
ze:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">=
***************************************************************************=
**************</span></b><span lang=3D"EN-GB"></span></p><p class=3D"MsoNor=
mal" style=3D"line-height:13.0pt;text-autospace:none"><b><span lang=3D"EN-G=
B" style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&=
quot;;color:black">Karen Egede Nielsen</span></b><span lang=3D"EN-GB"></spa=
n></p><p class=3D"MsoNormal" style=3D"line-height:13.0pt;text-autospace:non=
e"><span lang=3D"EN-GB" style=3D"font-size:8.0pt;font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;color:black">Software Architect, Ph.D.</span><sp=
an lang=3D"EN-GB"></span></p><p class=3D"MsoNormal" style=3D"line-height:13=
.0pt;text-autospace:none"><span lang=3D"EN-GB" style=3D"font-size:8.0pt;fon=
t-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">=C2=A0</span=
><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal" style=3D"line-heigh=
t:13.0pt;text-autospace:none"><b><span lang=3D"EN-GB" style=3D"font-size:8.=
0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Tieto=
 Denmark A/S</span></b><span lang=3D"EN-GB"></span></p><p class=3D"MsoNorma=
l" style=3D"line-height:13.0pt;text-autospace:none"><span style=3D"font-siz=
e:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">R=
&amp;D, Telecom &amp; Media</span></p><p class=3D"MsoNormal" style=3D"line-=
height:13.0pt;text-autospace:none"><span style=3D"font-size:8.0pt;font-fami=
ly:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">=C3=85have Parkvej=
 27, 8260 Viby J, DK-Denmark</span></p><p class=3D"MsoNormal" style=3D"line=
-height:13.0pt;text-autospace:none"><span lang=3D"EN-GB" style=3D"font-size=
:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">Di=
rect Phone / Mobile +45 25134336</span><span lang=3D"EN-GB"></span></p><p c=
lass=3D"MsoNormal" style=3D"line-height:13.0pt;text-autospace:none"><span l=
ang=3D"IT" style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:black">E-mail: <a href=3D"mailto:karen.nielsen@tieto.co=
m"><span style=3D"color:blue">karen.nielsen@tieto.com</span></a></span><spa=
n lang=3D"EN-GB"></span></p><p class=3D"MsoNormal" style=3D"line-height:13.=
0pt;text-autospace:none"><span lang=3D"EN-GB" style=3D"font-size:8.0pt;font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">*************=
***************************************************************************=
*</span><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal" style=3D"lin=
e-height:13.0pt;text-autospace:none"><span lang=3D"EN-GB" style=3D"font-siz=
e:8.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"><=
a href=3D"http://www.tieto.com"><span style=3D"color:blue">www.tieto.com</s=
pan></a>=C2=A0 </span><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal=
" style=3D"line-height:13.0pt;text-autospace:none"><i><span lang=3D"EN-GB" =
style=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;">=C2=A0</span></i><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal"=
 style=3D"line-height:13.0pt;text-autospace:none"><i><span lang=3D"EN-GB" s=
tyle=3D"font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;">Please note: The information contained in this message may be legally pr=
ivileged and confidential and protected from disclosure. If the reader of t=
his message is not the intended recipient, you are hereby notified that any=
 unauthorised use, distribution or copying of this communication is strictl=
y prohibited. If you have received this communication in error, please noti=
fy us immediately by replying to the message and deleting it from your comp=
uter. </span></i><i><span style=3D"font-size:7.5pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;">Thank You.</span></i><span lang=3D"EN-GB"></s=
pan></p><p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D=
"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=
=A0</span><span lang=3D"EN-GB"></span></p><p class=3D"MsoNormal"><span lang=
=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;">=C2=A0</span><span lang=3D"EN-GB"></span></p><p class=
=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=3D"EN-GB">=
</span></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span><s=
pan lang=3D"EN-GB"></span></p><p class=3D"MsoNormal">=C2=A0</p></div></body=
></html>

--047d7bfd061cbbd8d20505d88d0b--


From nobody Tue Oct 21 00:45:09 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786BA1AD0A4 for <tsvwg@ietfa.amsl.com>; Tue, 21 Oct 2014 00:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.322
X-Spam-Level: *
X-Spam-Status: No, score=1.322 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Lxc4Rmv9-0F1 for <tsvwg@ietfa.amsl.com>; Tue, 21 Oct 2014 00:45:05 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044A01A6FA9 for <tsvwg@ietf.org>; Tue, 21 Oct 2014 00:45:02 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id l18so640497wgh.17 for <tsvwg@ietf.org>; Tue, 21 Oct 2014 00:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to :content-type; bh=8d12lTu4CJAltbJGAC3PTjQcc/wcDSnASn9Aq82BfN4=; b=swVMMefut24jorU/1nwZdJ3vfyQKjWS3i5JIBpHMwwyZ/qRgU5PCOZnugmkHaqsHAH hYL3YwYA09KL3jSH/N/wkqdSSrwqJOqEhLiSWAU6dm9myQOI49K+TmOoZrhTdpQQpmIm /NPBvKSRCOHXNtgPdtLBXMTO4FRvfMZcoCST8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:content-type; bh=8d12lTu4CJAltbJGAC3PTjQcc/wcDSnASn9Aq82BfN4=; b=mCldLqoE/c3yDj8RU248bqFyoThih+iN1tiHahFKj3dY0H7Jvqed6IQP4rcUOWfiDI 0WtMuHAfFoFeM4COjo5Y1GC2KTR8yOmwCkaLvP2jE1WJEv9NwtHU3XjuX4MZY5q6lWtI oDRUJ7pISkiYrFZbbQVFoAYv//OODL5uJCkBll5WhX6S8rAUWWKlEWkKXxDTr4vTX57y jECIH8ThsTUeeCsSRc6gkKH+cpeWjmm9JjGQARcNwhZ4uPBvk9vDKVvW4fvn2Z67/lXg suAt0bvRLqUuTIU3dJ93S1EN76U1edaesjoT8GlScNCrw5MKHn1US/I0fEkzgc0zo/H2 s9Lw==
X-Gm-Message-State: ALoCoQlt25Nc4HAFCkPmUJTYX4uQVrn9/Mo+wd1/xZPJvC17SnZwPx+oNIkMSKBLT9oRmdV11R7EmB7a2DKQwywvdKpizBNL9+NVw+UrLJ6YbEqejojhmYE=
X-Received: by 10.194.77.199 with SMTP id u7mr40671033wjw.92.1413877500938; Tue, 21 Oct 2014 00:45:00 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/tAuo/QwHL/soOQmyHWwF6iBvggQ==
Date: Tue, 21 Oct 2014 09:45:00 +0200
Message-ID: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>, Randall Stewart <rstewart@adaranetworks.com>, tsvwg@ietf.org
Content-Type: multipart/alternative; boundary=047d7bfd061c333f200505ea0283
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/UovBUzp2DnX3LyHLRSANWEet53I
Subject: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 21 Oct 2014 07:45:07 -0000

--047d7bfd061c333f200505ea0283
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 Hi,



I have come to realize that I for the SCTP TLP (SCTP Tail Loss probe
additions) and SCTP FR improvements (adoptation of certain RFC6675
nextseg() features for SCTP FR) that we are working on (as presented at
IETF 90) have made an assumption on the SCTP FR function which is neither
aligned with our

actual SCTP implementation nor with the text of RFC4960 (/RFC4460) as
written (section 7.2.4).



However in order to better understand the motivation for the text of
RFC4960 as written,

I would appreciate very much if the wg would comment on the following
formulation of RFC4960 section 7.2.4:



If an endpoint is in Fast Recovery and a SACK

   arrives that advances the Cumulative TSN Ack Point, the

   miss indications are incremented for all TSNs reported

   missing in the SACK.



Especially on why the text DOES NOT read:



If an endpoint is in Fast Recovery and a SACK

   arrives that advances the Cumulative TSN Ack Point, the

   miss indications are incremented for all TSNs still

   missing up to and including the Fast Recovery Exit Point.





The basic philosophi being that when the cum ack advances, then the newly
cum ack=E2=80=99ed TSN has

been assumed lost, has been retransmitted and consequently the mis
indication count should go up for

all still missing TSNs up to and including the Fast Recovery Exit Point.



It is clear that the above aproach by no means is bullet proof in the sense
that it may very well be that the cum ack advances

due to receipt of SACK without this in fact being a result of the receipt
by peer of a fast retransmitted TSN, but this is the situation

also with the approach written into RFC4960.



Many thanks in advance.



BR, Karen

--047d7bfd061c333f200505ea0283
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:DA;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3D"DA" link=3D"blue" vlink=3D"purple"><div cla=
ss=3D"WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"fo=
nt-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0=
Hi,</span></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-siz=
e:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span=
></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;=
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">I have come to realiz=
e that I for the SCTP TLP (SCTP Tail Loss probe additions) and SCTP FR impr=
ovements (adoptation of certain RFC6675 nextseg() features for SCTP FR) tha=
t we are working on (as presented at IETF 90) have made an assumption on th=
e SCTP FR function which is neither aligned with our</span></p><p class=3D"=
MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">actual SCTP implementation nor with th=
e text of RFC4960 (/RFC4460) as written (section 7.2.4). </span></p><p clas=
s=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span></p><p class=3D"MsoN=
ormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;">However in order to better understand the =
motivation for the text of RFC4960 as written,</span></p><p class=3D"MsoNor=
mal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial=
&quot;,&quot;sans-serif&quot;">I would appreciate very much if the wg would=
 comment on the following formulation of RFC4960 section 7.2.4:</span></p><=
p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span></p><p class=
=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black">If an endpoint is in Fast Recovery and =
a SACK</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 a=
rrives that advances the Cumulative TSN Ack Point, the</span></p><p class=
=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black">=C2=A0=C2=A0 miss indications are incre=
mented for all TSNs reported</span></p><p class=3D"MsoNormal"><span lang=3D=
"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color=
:black">=C2=A0=C2=A0 missing in the SACK.</span></p><p class=3D"MsoNormal">=
<span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;">=C2=A0</span></p><p class=3D"MsoNormal"><span lan=
g=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Especially on why the text DOES NOT read:</span></p><p cla=
ss=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family=
:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span></p><p class=3D"Mso=
Normal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">If an endpoint is in Fast Recovery and a SACK<=
/span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10=
.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=A0=C2=A0 arrives =
that advances the Cumulative TSN Ack Point, the</span></p><p class=3D"MsoNo=
rmal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 miss indications are incremented fo=
r all TSNs still</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" styl=
e=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=C2=
=A0=C2=A0 missing up to and including the Fast Recovery Exit Point.</span><=
/p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">=C2=A0</span></p><p class=3D=
"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quo=
t;Courier New&quot;;color:black">=C2=A0</span></p><p class=3D"MsoNormal"><s=
pan lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;">The basic philosophi being that when the cum ack ad=
vances, then the newly cum ack=E2=80=99ed TSN has </span></p><p class=3D"Ms=
oNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;">been assumed lost, has been retransmitte=
d and consequently the mis indication count should go up for </span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;">all still missing TSNs up to =
and including the Fast Recovery Exit Point.</span></p><p class=3D"MsoNormal=
"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;">=C2=A0</span></p><p class=3D"MsoNormal"><span l=
ang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">It is clear that the above aproach by no means is bullet=
 proof in the sense that it may very well be that the cum ack advances</spa=
n></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt=
;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">due to receipt of SA=
CK without this in fact being a result of the receipt by peer of a fast ret=
ransmitted TSN, but this is the situation</span></p><p class=3D"MsoNormal">=
<span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;">also with the approach written into RFC4960.</spa=
n></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt=
;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;">Many thanks in advance.</span=
></p><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;=
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span></p><p c=
lass=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font-fami=
ly:&quot;Arial&quot;,&quot;sans-serif&quot;">BR, Karen</span></p><p class=
=3D"MsoNormal"><b><span lang=3D"EN-GB" style=3D"font-size:8.0pt;font-family=
:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">=C2=A0</span></b></p=
><p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt;font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;">=C2=A0</span><span lang=
=3D"EN-GB"></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</s=
pan></p></div></body></html>

--047d7bfd061c333f200505ea0283--


From nobody Thu Oct 23 00:47:02 2014
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765C11A88F5 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 00:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.139
X-Spam-Level: *
X-Spam-Status: No, score=1.139 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 bisQ_pcCidTa for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 00:46:57 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B7971A88F8 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 00:46:57 -0700 (PDT)
Received: from [10.225.7.42] (unknown [194.95.73.101]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id C74791C104FC5; Thu, 23 Oct 2014 09:46:54 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com>
Date: Thu, 23 Oct 2014 09:46:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/VCDd3oTcTqrPoqWnu5uxxhQHvmc
Cc: tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Oct 2014 07:46:59 -0000

On 21 Oct 2014, at 09:45, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:

>  Hi,
> =20
> I have come to realize that I for the SCTP TLP (SCTP Tail Loss probe =
additions) and SCTP FR improvements (adoptation of certain RFC6675 =
nextseg() features for SCTP FR) that we are working on (as presented at =
IETF 90) have made an assumption on the SCTP FR function which is =
neither aligned with our
> actual SCTP implementation nor with the text of RFC4960 (/RFC4460) as =
written (section 7.2.4).
> =20
> However in order to better understand the motivation for the text of =
RFC4960 as written,
> I would appreciate very much if the wg would comment on the following =
formulation of RFC4960 section 7.2.4:
> =20
> If an endpoint is in Fast Recovery and a SACK
>    arrives that advances the Cumulative TSN Ack Point, the
>    miss indications are incremented for all TSNs reported
>    missing in the SACK.
> =20
> Especially on why the text DOES NOT read:
> =20
> If an endpoint is in Fast Recovery and a SACK
>    arrives that advances the Cumulative TSN Ack Point, the
>    miss indications are incremented for all TSNs still
>    missing up to and including the Fast Recovery Exit Point.
What are you asking for:
1. Do you want to limited the TSNs for which you want to increase the =
counter,
   but still consider only the ones reported in the SACK.
2. Do you want to ignore what is reported missing in the SACK and just =
base it
   on the senders view?
> =20
> =20
> The basic philosophi being that when the cum ack advances, then the =
newly cum ack=92ed TSN has
> been assumed lost, has been retransmitted and consequently the mis =
indication count should go up for
I don't understand the part: "the newly cum ack=92ed TSN has been =
assumed lost"
Could you clarify what you mean?

Best regards
Michael
> all still missing TSNs up to and including the Fast Recovery Exit =
Point.
> =20
> It is clear that the above aproach by no means is bullet proof in the =
sense that it may very well be that the cum ack advances
> due to receipt of SACK without this in fact being a result of the =
receipt by peer of a fast retransmitted TSN, but this is the situation
> also with the approach written into RFC4960.
> =20
> Many thanks in advance.
> =20
> BR, Karen


From nobody Thu Oct 23 02:04:08 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5731A894C for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 02:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.121
X-Spam-Level: ***
X-Spam-Status: No, score=3.121 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_42=0.6, J_CHICKENPOX_52=0.6, J_CHICKENPOX_62=0.6, SPF_PASS=-0.001] autolearn=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 Z4jjfR7JU10J for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 02:03:59 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0CBD1A8925 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 02:03:57 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b13so595578wgh.34 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 02:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=5FkPHrMNaCDU84AKpMaKxYWmsSUD00GtVQmiqa3c8vQ=; b=cCxrW28g1TmFqQ0fLSHYZFX8U4StYUmDaTTwMumq/jN/9g/wIUxlygcjZR0cgAh8nG hYGhNAd1hROiqsCKdxT3RubHw4alfMCbkPozEBFj22AYVYaKkISaK2g2xM1sjL9Qr0a6 HAr6gGhXB02GpiNeJzuIaR/eI+Yema+fEYyuA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=5FkPHrMNaCDU84AKpMaKxYWmsSUD00GtVQmiqa3c8vQ=; b=bvhuPqUcjHjavpxM1Gs8DEq3H6/ZYiAeFLvpOSlRXab7jALbvN05Ls2/KJZR20N3em t7s5475s2CI38scLEIkZHLSLuM8q+KsuEBiiFEYlYfOx0ZGcGhYy+UmQIP/x2hM/niLU wvt1z2QphW35qS6rHRTokLKre7aysalpYfPIeJFb2qOd1Vf/KR5KGWTd1qxzITZtv86b HqiD1joQ8qZOvxJwH6+E3lmwgHb8ZxRAbuNUhC+2pUhKXoWHMye1IvZzTm4UaTK3AnEe mEn7WWgCS3hGRI7uTQQTRjQu9BZHaOR9hvqPdZQwu/px9KDl8qdzaD/2pHj3OUJ1kSHQ nO9g==
X-Gm-Message-State: ALoCoQn14OAKgWcsAC7xukYlmUX2HTfoSzrUQxnuuKBvkZl+Gh4WYOGjR0c+2P0IZailjwTylgTgyAX0EUAD5E+V/Iqj20tb7EBYOG+YV41X8MgmaLDcKE0=
X-Received: by 10.180.211.70 with SMTP id na6mr11332608wic.3.1414055036442; Thu, 23 Oct 2014 02:03:56 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de>
In-Reply-To: <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSm82kKMA=
Date: Thu, 23 Oct 2014 11:03:55 +0200
Message-ID: <18abf78ce11ef2088038d6d6c1f8d407@mail.gmail.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7zgpVYL3QhBpIAMY02wV2KcdNtc
Cc: tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Oct 2014 09:04:01 -0000

, I would appreciate very much if the wg would
> comment on the following formulation of RFC4960 section 7.2.4:
> >
> > If an endpoint is in Fast Recovery and a SACK
> >    arrives that advances the Cumulative TSN Ack Point, the
> >    miss indications are incremented for all TSNs reported
> >    missing in the SACK.
> >
> > Especially on why the text DOES NOT read:
> >
> > If an endpoint is in Fast Recovery and a SACK
> >    arrives that advances the Cumulative TSN Ack Point, the
> >    miss indications are incremented for all TSNs still
> >    missing up to and including the Fast Recovery Exit Point.
> What are you asking for:
> 1. Do you want to limited the TSNs for which you want to increase the
> counter,
>    but still consider only the ones reported in the SACK.
[Karen] No 100% sure what you mean. This to me sounds as the present text
of RFC4960.
> 2. Do you want to ignore what is reported missing in the SACK and just
base it
>    on the senders view?
[Karen] No I don't what to ignore what it is the SACK. I want to use what
it is in SACK PLUS the senders knowledge
that the now newly cumack'ed  TSN was sent later than all TSN missing up
to and including the FR Exit point.

Do me the RFC4960 text goes only half the way. It does use what it in the
SACK and it does use the knowledge
that the now newly cumack'ed TSN TSN was sent later than some TSNs - but
here only the TSNs reported missing in the SACK.

IF there is a SACK'ed TSN after FR exit point then RFC4960 text does what
I want, but if the highest SACK'ed TSN is below the FR exit point it does
not.

I am actually much more concerned with getting mis-indications for the
TSNs below the FR exit point than above.
This is particularly important when there is a loss in the end and no new
data to drive FR. But yes we are looking at complex drop scenarios for
this to take effect

RFC6675 TCP Rescue operation (nextseg() 4)) is one way to amend FR to work
better to recover tails and we are  actually implementing this
in our SCTP SW, but for me it has still been very important to understand
when/if this is needed.

As reference then in the presentation
http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
slide 30-33 (sorry for numbers not being there consistently) we presented
some analysis of the RFC6675 effects on SCTP FR.
There are a number of loss scenarios in the tables there marked with
RFC4960 recover high L (TSN lost in the end)
This marking - assuming the text of RFC4960 is to be taken literally -
should not rightfully read
RFC6674 nextseg() 4) Rescue operation recover high L (TSN lost in the
end).


> >
> >
> > The basic philosophi being that when the cum ack advances, then the
> > newly cum ack'ed TSN has been assumed lost, has been retransmitted and
> > consequently the mis indication count should go up for
> I don't understand the part: "the newly cum ack'ed TSN has been assumed
> lost"
> Could you clarify what you mean?
>
[Karen] Let me answer by a question:
What, in your understanding, is the motivation for the following
prescription, RFC4960 section 7.2 (added by RFC4460):

          " If an endpoint is in Fast Recovery and a SACK
          arrives that advances the Cumulative TSN Ack Point, the
          miss indications are incremented for all TSNs reported
          missing in the SACK."

Is it not that the mis indications should come because the newly cumak'ed
TSN is assumed to have been fast retransmitted and
receive by peer after the other TSNs, reported as missing in the SACK, was
sent ?

BR, Karen

> Best regards
> Michael
> > all still missing TSNs up to and including the Fast Recovery Exit
Point.
> >
> > It is clear that the above aproach by no means is bullet proof in the
> > sense that it may very well be that the cum ack advances due to
> > receipt of SACK without this in fact being a result of the receipt by
peer of a
> fast retransmitted TSN, but this is the situation also with the approach
> written into RFC4960.
> >
> > Many thanks in advance.
> >
> > BR, Karen


From nobody Thu Oct 23 04:27:19 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1488F1A8AC2 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 04:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 41YvBJnM_wpQ for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 04:27:15 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 107F01A8AC1 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 04:27:14 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NBRCxG013621; Thu, 23 Oct 2014 05:27:12 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NBRCQM005245; Thu, 23 Oct 2014 05:27:12 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9NBRBbC005244; Thu, 23 Oct 2014 05:27:11 -0600
Date: Thu, 23 Oct 2014 05:27:11 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Message-ID: <20141023112711.GA3853@openss7.org>
Mail-Followup-To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/dKjcOwDzSrtYELOyzsrFhfO-3l0
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 23 Oct 2014 11:27:17 -0000

Karen,

Please see comments below:

On 21 Oct 2014, at 09:45, Karen Elisabeth Egede Nielsen wrote:
> 
>  Hi,
>  
> I have come to realize that I for the SCTP TLP (SCTP Tail Loss
> probe additions) and SCTP FR improvements (adoptation of certain
> RFC6675 nextseg() features for SCTP FR) that we are working on (as
> presented at IETF 90) have made an assumption on the SCTP FR
> function which is neither aligned with our actual SCTP
> implementation nor with the text of RFC4960 (/RFC4460) as written
> (section 7.2.4).
>  
> However in order to better understand the motivation for the text
> of RFC4960 as written, I would appreciate very much if the wg
> would comment on the following formulation of RFC4960 section
> 7.2.4:
>  
> If an endpoint is in Fast Recovery and a SACK arrives that
>    advances the Cumulative TSN Ack Point, the miss indications are
>    incremented for all TSNs reported missing in the SACK.
>  
> Especially on why the text DOES NOT read:
>  
> If an endpoint is in Fast Recovery and a SACK arrives that
>    advances the Cumulative TSN Ack Point, the miss indications are
>    incremented for all TSNs still missing up to and including the
>    Fast Recovery Exit Point.
>  

Would it be possible for you to describe a simple non-renegging
scenario in which the highest acknowledged TSN in a SACK that
advances the cummulative ack point would not encompass TSNs up
to and including the fast recovery exit point?

I can't think of one at the moment.

Also, the last paragraph of RFC4960/7.2.4 reads:

 "A straightforward implementation of the above keeps a counter for
  each TSN hole reported by a SACK.  The counter increments for each
  consecutive SACK reporting the TSN hole.  After reaching 3 and
  starting the Fast-Retransmit procedure, the counter resets to 0.
  Because cwnd in SCTP indirectly bounds the number of outstanding
  TSN's, the effect of TCAP Fast Recovery is acheived automatically
  with no adjustment to the congestion control window size."

I understand this to mean that no fast recovery exit point needs to
be tracked at all for SCTP.

Is there a reason would make it necessary to track the fast recovery
exit point?


--brian


> The basic philosophi being that when the cum ack advances, then
> the newly cum ackâ€™ed TSN has been assumed lost, has been
> retransmitted and consequently the mis indication count should go
> up for all still missing TSNs up to and including the Fast
> Recovery Exit Point.
>  
> It is clear that the above aproach by no means is bullet proof in
> the sense that it may very well be that the cum ack advances due
> to receipt of SACK without this in fact being a result of the
> receipt by peer of a fast retransmitted TSN, but this is the
> situation also with the approach written into RFC4960.
>  
> Many thanks in advance.
>  
> BR, Karen

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Oct 23 04:35:57 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B65321A8AE8 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 04:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 RSDqMV_do03w for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 04:35:53 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 483A21A8AE1 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 04:35:52 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b13so862792wgh.34 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 04:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=jf1p77wiyFOWJS4lXa9rLSwvXdPhynL20QPXuAirhMQ=; b=G0FKBfnpyVqbY2q8XnnTmle51+y3yZcd+UccXvQ1i2d4tf4tKW06i81XbpNwM2pVO3 WassTJhiAWQMZ76mZgy1vSEJSDwforvHPAqLpfpj8Rq1u/Ak7QJBqzu1M7X66B4ZBCHI kh9neakO/XvBXMqUEURncEgciexNmdRNuMEdY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=jf1p77wiyFOWJS4lXa9rLSwvXdPhynL20QPXuAirhMQ=; b=SZo8Sg0uOdXW5h7zTMc2I5FVfKAwauVwsdp3/gqLuGPfliyCiOxgWr/PGNK5lW2pn5 i/k1cPrkh/XoYhbtML1WxOXjoGaOJb6OjTLDpe7sU1PZiyA4KpYPp5euNx5Hv6ZYANDb jPSdkKdlZy8snBzfYMtnrmadsSvzw3sTcAE/Sbi74OmElcIv65yBTPpk09GQh2bDCEnk NHR2wFYKy+yjwmnVgcBfN5B817pbWyjTOmTBm5dQix2Cmy+E68bIMXwJUmR9ejV411C6 a11nB0lttyoPhgau6Jbp50tbeiutWLVG51tbdkVfyZb11LZN9FbbMJemasTebj03LrXu uWqA==
X-Gm-Message-State: ALoCoQkVbaALHOGabbrJH9Go4Lqh/rbG7lmRuQZzyCzMWmBiZB9fBDTZ2xZUFplCTBL+inAAJ3h8KrAvJ2Z1KIuY7cGQsTHQkYnPSFeneMWlObPRDGka4Sk=
X-Received: by 10.194.161.166 with SMTP id xt6mr4922845wjb.1.1414064151735; Thu, 23 Oct 2014 04:35:51 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org>
In-Reply-To: <20141023112711.GA3853@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/ObwpLyoA==
Date: Thu, 23 Oct 2014 13:35:51 +0200
Message-ID: <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com>
To: bidulock@openss7.org, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/2qdCA8g6O_VD8duUeBI50BfpdQ0
Cc: tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Oct 2014 11:35:55 -0000

Hi Brian,

Thanks please see below.

BR, Karen

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Brian F. G.
> Bidulock
> Sent: 23. oktober 2014 13:27
> To: Michael Tuexen
> Cc: Karen Elisabeth Egede Nielsen; tsvwg WG; Randall Stewart
> Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
>
> Karen,
>
> Please see comments below:
>
> On 21 Oct 2014, at 09:45, Karen Elisabeth Egede Nielsen wrote:
> >
> >  Hi,
> >
> > I have come to realize that I for the SCTP TLP (SCTP Tail Loss probe
> > additions) and SCTP FR improvements (adoptation of certain
> > RFC6675 nextseg() features for SCTP FR) that we are working on (as
> > presented at IETF 90) have made an assumption on the SCTP FR function
> > which is neither aligned with our actual SCTP implementation nor with
> > the text of RFC4960 (/RFC4460) as written (section 7.2.4).
> >
> > However in order to better understand the motivation for the text of
> > RFC4960 as written, I would appreciate very much if the wg would
> > comment on the following formulation of RFC4960 section
> > 7.2.4:
> >
> > If an endpoint is in Fast Recovery and a SACK arrives that
> >    advances the Cumulative TSN Ack Point, the miss indications are
> >    incremented for all TSNs reported missing in the SACK.
> >
> > Especially on why the text DOES NOT read:
> >
> > If an endpoint is in Fast Recovery and a SACK arrives that
> >    advances the Cumulative TSN Ack Point, the miss indications are
> >    incremented for all TSNs still missing up to and including the
> >    Fast Recovery Exit Point.
> >
>
> Would it be possible for you to describe a simple non-renegging scenario
> in
> which the highest acknowledged TSN in a SACK that advances the
> cummulative ack point would not encompass TSNs up to and including the
> fast recovery exit point?
>
> I can't think of one at the moment.

[Karen] Please see the analysis presented at IETF90:

As referenced in the presentation
http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
slide 30-33 (sorry for numbers not being there consistently) we presented
some analysis of the RFC6675 effects on SCTP FR.
There are a number of loss scenarios in the tables there marked with RFC496=
0
recover high L (TSN lost in the end) This marking - assuming the text of
RFC4960 is to be taken literally - should rightfully read
RFC6674 nextseg() 4) Rescue operation recover high L (TSN lost in the end).



>
> Also, the last paragraph of RFC4960/7.2.4 reads:
>
>  "A straightforward implementation of the above keeps a counter for
>   each TSN hole reported by a SACK.  The counter increments for each
>   consecutive SACK reporting the TSN hole.  After reaching 3 and
>   starting the Fast-Retransmit procedure, the counter resets to 0.
>   Because cwnd in SCTP indirectly bounds the number of outstanding
>   TSN's, the effect of TCAP Fast Recovery is acheived automatically
>   with no adjustment to the congestion control window size."
>
> I understand this to mean that no fast recovery exit point needs to be
> tracked at all for SCTP.
>
> Is there a reason would make it necessary to track the fast recovery exit
> point?
>
[Karen] I am not sure that I understand how to implement SCTP FR without
tracking the exit point.

BR, Karen
>
> --brian
>
>
> > The basic philosophi being that when the cum ack advances, then the
> > newly cum ack=E2=80=99ed TSN has been assumed lost, has been retransmit=
ted and
> > consequently the mis indication count should go up for all still
> > missing TSNs up to and including the Fast Recovery Exit Point.
> >
> > It is clear that the above aproach by no means is bullet proof in the
> > sense that it may very well be that the cum ack advances due to
> > receipt of SACK without this in fact being a result of the receipt by
> > peer of a fast retransmitted TSN, but this is the situation also with
> > the approach written into RFC4960.
> >
> > Many thanks in advance.
> >
> > BR, Karen
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From nobody Thu Oct 23 05:01:03 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068D51ACD88 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 05:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 phKzd-LkhC1s for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 05:00:52 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5264A1ACE1C for <tsvwg@ietf.org>; Thu, 23 Oct 2014 05:00:44 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NC0hiv013772; Thu, 23 Oct 2014 06:00:43 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NC0gne005789; Thu, 23 Oct 2014 06:00:42 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9NC0gY4005788; Thu, 23 Oct 2014 06:00:42 -0600
Date: Thu, 23 Oct 2014 06:00:42 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141023120042.GB3853@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/L3HRTZO_JnCDPdtUoW4d6BkKpso
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg WG <tsvwg@ietf.org>, Randall Stewart <rrs@netflix.com>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 23 Oct 2014 12:01:01 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:  (Thu, 23 Oct 2014 13:35:51)

--X--snip--X--
> > > However in order to better understand the motivation for the text of
> > > RFC4960 as written, I would appreciate very much if the wg would
> > > comment on the following formulation of RFC4960 section
> > > 7.2.4:
> > >
> > > If an endpoint is in Fast Recovery and a SACK arrives that
> > >    advances the Cumulative TSN Ack Point, the miss indications are
> > >    incremented for all TSNs reported missing in the SACK.
> > >
> > > Especially on why the text DOES NOT read:
> > >
> > > If an endpoint is in Fast Recovery and a SACK arrives that
> > >    advances the Cumulative TSN Ack Point, the miss indications are
> > >    incremented for all TSNs still missing up to and including the
> > >    Fast Recovery Exit Point.
> > >
> >
> > Would it be possible for you to describe a simple non-renegging
> > scenario in which the highest acknowledged TSN in a SACK that
> > advances the cummulative ack point would not encompass TSNs up
> > to and including the fast recovery exit point?
> >
> > I can't think of one at the moment.
> 
> [Karen] Please see the analysis presented at IETF90:
> 
> As referenced in the presentation
> http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
> slide 30-33 (sorry for numbers not being there consistently) we presented
> some analysis of the RFC6675 effects on SCTP FR.
> There are a number of loss scenarios in the tables there marked with RFC4960
> recover high L (TSN lost in the end) This marking - assuming the text of
> RFC4960 is to be taken literally - should rightfully read
> RFC6674 nextseg() 4) Rescue operation recover high L (TSN lost in the end).

I looked at the presentation before replying and I failed to
trace any scenario from the presentation.  Could you describe the
packet exchange for just one of them?  Treat me like I'm six years
old...

> >
> > Also, the last paragraph of RFC4960/7.2.4 reads:
> >
> >  "A straightforward implementation of the above keeps a counter for
> >   each TSN hole reported by a SACK.  The counter increments for each
> >   consecutive SACK reporting the TSN hole.  After reaching 3 and
> >   starting the Fast-Retransmit procedure, the counter resets to 0.
> >   Because cwnd in SCTP indirectly bounds the number of outstanding
> >   TSN's, the effect of TCAP Fast Recovery is acheived automatically
> >   with no adjustment to the congestion control window size."
> >
> > I understand this to mean that no fast recovery exit point needs to be
> > tracked at all for SCTP.
> >
> > Is there a reason would make it necessary to track the fast recovery exit
> > point?
> >
> [Karen] I am not sure that I understand how to implement SCTP FR without
> tracking the exit point.

The first three sentences describe how to implement SCTP FR without
tracking the exit point.  As I understand it, The purpose of the exit
point in TCP was to limit the number of packets in flight (because
TCP cwnd tracks bytes not packets).  Because SCTP cwnd indirectly limits
packets in flight all day long, the TCP FR cwnd adjustments are not
necessary, thus in SCTP tracking the FR exit point is not necessary.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Oct 23 06:07:25 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FC31A9085 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 06:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 DqfjAxAmQge5 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 06:07:19 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A52D71A9094 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 06:07:19 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9ND7Ic9014044; Thu, 23 Oct 2014 07:07:18 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9ND7IIR006814; Thu, 23 Oct 2014 07:07:18 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9ND7GVw006813; Thu, 23 Oct 2014 07:07:16 -0600
Date: Thu, 23 Oct 2014 07:07:16 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141023130716.GA6071@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, tsvwg WG <tsvwg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Yv_cknqY9NHotUUpv4dX7M_GhWQ
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [tsvwg] General comments on slides-90-tsvwg-16.pdf
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 23 Oct 2014 13:07:24 -0000

Karen,

In your presentation,

  http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf

you asked for comments on tsvwg on the material presented.  Here are
some general comments.

The procedures described appear to be concerned with avoiding T3
timeouts in as many scenarios as possible.  Stepping back and
thinking about that, I wonder what can be achieved by completely
eclipsing the T3 timeout procedure.  The procedures appear to
proceed from the assumption that T3 timeouts are evil and to be
avoided at all cost.

The evil appears to pivot on increased latencies in lossy network
(whether due to congestion or transmission errors) and not so much
on congestion avoidance procedures (cwnd).  The statement of evil,
if you will, appears to be: It takes a longer time for a T3 timeout
to occur than is necessary because better information about loss
can be available before the timeout ensues.

What RTO_MIN value are you using in your experiments?  For SIGTRAN
we have been using a RTO_MIN value of zero (0) for quite some time.
For example, ETSI TS 102 144 V1.1.1 (2003-05) specified the minimum
value for RTO.Min as 10 ms and specified with a granularity of 10 ms.
(Note that the common clock tick at the time was 10ms.)  This was
also mentioned in RFC4166/3.2.1.

There are a couple of well-known procedures that can be used to
mitigate spurious retransmissions when using a low RTO.min:

 - setting SACK_DELAY to zero (0) on both sides, or not penalizing
   a receiver for having a SACK_DELAY > RTO.

 - initiating an immediate HB probe for a destination when RTO
   approaches the granularity of the system clock to quickly
   recover a destination (especially when PMR is set to 0 or 1).

An extremely high RTO.min (e.g. 1 second) will make any procedure
that avoids a T3 timeout look good on the surface.

If your implementation is capable of setting RTO.min to zero, you
could try rerunning your experiments with an RTO.min of zero (0) to
determine whether falling back on T3 timeout is such a bad thing
after all.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Oct 23 12:12:22 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7915C1ACE93 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 3almK0V4JzgZ for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:12:18 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B66D61ACE6E for <tsvwg@ietf.org>; Thu, 23 Oct 2014 12:12:17 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NJCG5S015921; Thu, 23 Oct 2014 13:12:16 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NJCGPS013378; Thu, 23 Oct 2014 13:12:16 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9NJCFRh013377; Thu, 23 Oct 2014 13:12:15 -0600
Date: Thu, 23 Oct 2014 13:12:15 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141023191215.GA12649@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Randall Stewart <rrs@netflix.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg@ietf.org
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/CYXoPd7u7VtmybjORWNtQeHSQqI
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 23 Oct 2014 19:12:20 -0000

Karen,

Please see comments inline:

On Thu, 23 Oct 2014, Karen Elisabeth Egede Nielsen wrote:

>    HI,
> 
>    Let's assume SCTP send a batch of packets, the packets marked with L
>    below are dropped, the packets with S are sacked.
> 
>    There is no more new data to send.
> 
>    SACKs arrive resulting in the following scorebard:
> 
>    LSSSLL
> 
>    in order from low -  high TSN.
> 
>    This makes SCTP fast retransmit the first lost packet setting FR exit
>    point to last TSN.
> 
>    resulting in increase of cumack and following scoreboard (A indicate
>    cumack'ed) once this TSN is sacked (which I assume).
> 
>    AAAALL
> 
>    There is 0 miscounts of the last two lost packets even if one packet
>    send since them obviously have been Sacked.

 TSN 1 ----------------> X
 TSN 2 ----------------------------->
       <----------------------------- SACK 0, 2-2
 TSN 1 peg = 1
 TSN 3 ----------------------------->
       <----------------------------- SACK 0, 2-3
 TSN 1 peg = 2
 TSN 4 ----------------------------->
       <----------------------------- SACK 0, 2-4
 TSN 1 peg = 3
 Enter FR  exit point = TSN 1
 TSN 1 ----------------------------->
       <----------------------------- SACK 4
 CA TSN >= exit point => exit FR
 TSN 5 ----------------> X
 TSN 6 ----------------> X

 At what point is the FR exit point greater than the highest
 outstanding TSN in a SACK?  That is, at what point would pegging
 up to the exit point include more TSNs that provided in the SACK?


>    Assumed also the following loss pattern. no new packets:
> 
>    LSLSLSLL
> 
>    Then Â again this makes SCTP fast retransmit the first lost packet
>    setting FR exit point to last TSN.
> 
>    After SACK of the retransmitted packet we have:
> 
>    AALSLSLL and the first loss (TSN packet number 3) will now have 3
>    miscounts and will be allowed to be fast retransmitted following the
>    rule,
> 
>    the same again for the third L. But the ones lost in the end do not get
>    any miscounts even if they same rule that apply to the first Lost
>    packets should
> 
>    apply to the last lost ones.

 TSN 1 ----------------> X
 TSN 2 ----------------------------->
       <----------------------------- SACK 0, 2-2
 TSN 1 peg = 1
 TSN 3 ----------------> X
 TSN 4 ----------------------------->
       <----------------------------- SACK 0, 2-2, 4-4
 TSN 1 peg = 2, TSN 3 peg = 1
 TSN 5 ----------------> X
 TSN 6 ----------------------------->
       <----------------------------- SACK 0, 2-2, 4-4, 6-6
 TSN 1 peg = 3, TSN 3 peg = 2, TSN 5 peg = 1
 Enter FR  exit point = TSN 5
 TSN 1 ----------------------------->
       <----------------------------- SACK 2, 4-4, 6-6
 TSN 3 peg = 3, TSN 5 peg = 2
 TSN 3 ----------------------------->
       <----------------------------- SACK 4, 6-6
 TSN 5 peg = 3
 TSN 5 ----------------------------->
       <----------------------------- SACK 6
 CA TSN >= exit point => exit FR
 TSN 7 ----------------> X
 TSN 8 ----------------> X

 At what point is the FR exit point greater than the highest
 outstanding TSN in a SACK?  That is, at what point would pegging
 up to the exit point include more TSNs that provided in the SACK?


>    I have written this a little hastely. I hope this can give the picture.
> 
>    Perhaps with this explanation also the information in slide 30-33 of
>    the following now makes sense:
> 
>    [1]http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
> 
>    BR, Karen
> 
>    From: Randall Stewart [mailto:[2]rrs@netflix.com]
>    Sent: 23. oktober 2014 16:48
>    To: Karen Elisabeth Egede Nielsen
>    Cc: Michael Tuexen; [3]bidulock@openss7.org
>    Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
> 
>    Karen:
> 
>    Note I dropped tsvwg due to the fact that this email would get locked
>    up and held/bounced since [4]rrs@netflix.com is
>    not a subscriber to tsvwg
> 
>    I like Brian am a bit confused by your request in that I don't see how
>    this could happen.
> 
>    SCTP has the ability to identify 300+ sack gaps. I think this
>    is why the wording is the way it is. We could not conceive of a situation
>    where the SACK would come back (outside of reneging) and not list what
>    was previously there. Especially if the SACK is a response to the
>    fast-retransmit.
> 
>    In theory it *should* contain all the gap acks that were present up to
>    your "fast recovery point".
> 
>    Like Brian I too don't remember ever making a "fast recovery point" in
>    SCTP.
> 
>    Now I guess you could get a situation where the fast retransmit passed the
>    last TSN sent and the sender is thus responding.. but thats still
>    pending data that *may* still arrive.
> 
>    So unless the sender purposely stops gap-acking previously gap-acked
>    packets (reneged) then I don't see how this could happen.
> 
>    Could you explain how you see this could happen .. it could be I am
>    missing something that is clear to you..
> 
>    Thanks
> 

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Oct 23 12:35:20 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4C31ACFC8 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 PbIbTaT40aKP for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:35:15 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E52FF1ACFCD for <tsvwg@ietf.org>; Thu, 23 Oct 2014 12:35:14 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id bs8so2902415wib.15 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 12:35:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=++FSeaKKdrz4eYZSbD8YKafhIlHxd2Qh8AF7wIMtFWE=; b=heAsZLGsqM/+xN/mSN7RPKJREA6WJmj3L8oCkxa9NUWUJM+GyPJ7l6u8MonsKtI4DJ SiRsqV+B2fG6s1m3A9/OBkINIdPae0lxlBtU9XqjePulLR8ZmeUSK95y3MW2hfvSU2a/ b+Qw1Zzu++SOf8pQ17D0sIQ7oXzAqAKMCfev8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=++FSeaKKdrz4eYZSbD8YKafhIlHxd2Qh8AF7wIMtFWE=; b=CsMftmPmhcIuQ1BGijhrlo8dkjzU6YuUOd37GuCsgSROaqkHE71JyBpXBZ1Rp8ugZE QPgSp8YvN3mbfXugv0c2/cmViiDbtnmdo7QYM03qt76mv/e1gcxddnfW6vPnb8sINVFE eWGGHGsjP9jtQukG8TEIV8QjgWHK+TjtqI6JTHDFvR3VzInDC/IFF7g0lJ1K265Xi0C2 KvaN2KMEN8C1WUWCQ27WTKhMATgV/SnvCDDLL2TzMZyOfE0lqRuXmd7jvtdYSq02yE9g sNUTF+542fZbV2OwIpfTA3IGfDTytLT3ir8BfmLsvJbV2NBqS2XvamvXTCe0mfkYD5u8 Vv+A==
X-Gm-Message-State: ALoCoQlD1mK2AdaycNl8JYMo171wZhMx8AWATmQ4IkjzcinOXmu7H/FdU5XOw27ebE+mosDMFT5NdsYpDommbBx9zDC4Uh+wtTykJ40ISDjPn8fGoPDKB+w=
X-Received: by 10.194.161.166 with SMTP id xt6mr7862134wjb.1.1414092913494; Thu, 23 Oct 2014 12:35:13 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org>
In-Reply-To: <20141023191215.GA12649@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4AtTxU80B9+M+8gKdj796m26zn8A=
Date: Thu, 23 Oct 2014 21:35:06 +0200
Message-ID: <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/FucuJ5XktPrs-9qLJtsgp26lzJU
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Oct 2014 19:35:18 -0000

Hi,

The TSN are sent at the same time, not sequentially.

Assume they chunks are  ~0,6*MTU, then there would be no CWND constrains and
no HB burst constraints.
This I am saying just to avoid to get into such discussions or bundling
discussions for that matter.

BR, Karen



> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: 23. oktober 2014 21:12
> To: Karen Elisabeth Egede Nielsen
> Cc: Randall Stewart; Michael Tuexen; tsvwg@ietf.org
> Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
>
> Karen,
>
> Please see comments inline:
>
> On Thu, 23 Oct 2014, Karen Elisabeth Egede Nielsen wrote:
>
> >    HI,
> >
> >    Let's assume SCTP send a batch of packets, the packets marked with L
> >    below are dropped, the packets with S are sacked.
> >
> >    There is no more new data to send.
> >
> >    SACKs arrive resulting in the following scorebard:
> >
> >    LSSSLL
> >
> >    in order from low -  high TSN.
> >
> >    This makes SCTP fast retransmit the first lost packet setting FR exit
> >    point to last TSN.
> >
> >    resulting in increase of cumack and following scoreboard (A indicate
> >    cumack'ed) once this TSN is sacked (which I assume).
> >
> >    AAAALL
> >
> >    There is 0 miscounts of the last two lost packets even if one packet
> >    send since them obviously have been Sacked.
>
>  TSN 1 ----------------> X
>  TSN 2 ----------------------------->
>        <----------------------------- SACK 0, 2-2  TSN 1 peg = 1  TSN
> 3 -------------------
> ---------->
>        <----------------------------- SACK 0, 2-3  TSN 1 peg = 2  TSN
> 4 -------------------
> ---------->
>        <----------------------------- SACK 0, 2-4  TSN 1 peg = 3  Enter FR
> exit point =
> TSN 1  TSN 1 ----------------------------->
>        <----------------------------- SACK 4  CA TSN >= exit point => exit
> FR  TSN 5 ---
> -------------> X  TSN 6 ----------------> X
>
>  At what point is the FR exit point greater than the highest  outstanding
> TSN
> in a SACK?  That is, at what point would pegging  up to the exit point
> include
> more TSNs that provided in the SACK?
>
>
> >    Assumed also the following loss pattern. no new packets:
> >
> >    LSLSLSLL
> >
> >    Then   again this makes SCTP fast retransmit the first lost packet
> >    setting FR exit point to last TSN.
> >
> >    After SACK of the retransmitted packet we have:
> >
> >    AALSLSLL and the first loss (TSN packet number 3) will now have 3
> >    miscounts and will be allowed to be fast retransmitted following the
> >    rule,
> >
> >    the same again for the third L. But the ones lost in the end do not
> > get
> >    any miscounts even if they same rule that apply to the first Lost
> >    packets should
> >
> >    apply to the last lost ones.
>
>  TSN 1 ----------------> X
>  TSN 2 ----------------------------->
>        <----------------------------- SACK 0, 2-2  TSN 1 peg = 1  TSN
> 3 ---------------->
> X  TSN 4 ----------------------------->
>        <----------------------------- SACK 0, 2-2, 4-4  TSN 1 peg = 2, TSN
> 3 peg = 1
> TSN 5 ----------------> X  TSN 6 ----------------------------->
>        <----------------------------- SACK 0, 2-2, 4-4, 6-6  TSN 1 peg =
> 3, TSN 3 peg =
> 2, TSN 5 peg = 1  Enter FR  exit point = TSN 5  TSN
> 1 ----------------------------->
>        <----------------------------- SACK 2, 4-4, 6-6  TSN 3 peg = 3, TSN
> 5 peg = 2
> TSN 3 ----------------------------->
>        <----------------------------- SACK 4, 6-6  TSN 5 peg = 3  TSN
> 5 -------------------
> ---------->
>        <----------------------------- SACK 6  CA TSN >= exit point => exit
> FR  TSN 7 ---
> -------------> X  TSN 8 ----------------> X
>
>  At what point is the FR exit point greater than the highest  outstanding
> TSN
> in a SACK?  That is, at what point would pegging  up to the exit point
> include
> more TSNs that provided in the SACK?
>
>
> >    I have written this a little hastely. I hope this can give the
> > picture.
> >
> >    Perhaps with this explanation also the information in slide 30-33 of
> >    the following now makes sense:
> >
> >
> > [1]http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
> >
> >    BR, Karen
> >
> >    From: Randall Stewart [mailto:[2]rrs@netflix.com]
> >    Sent: 23. oktober 2014 16:48
> >    To: Karen Elisabeth Egede Nielsen
> >    Cc: Michael Tuexen; [3]bidulock@openss7.org
> >    Subject: Re: [tsvwg] SCTP mis indication counting during Fast
> > Recovery
> >
> >    Karen:
> >
> >    Note I dropped tsvwg due to the fact that this email would get locked
> >    up and held/bounced since [4]rrs@netflix.com is
> >    not a subscriber to tsvwg
> >
> >    I like Brian am a bit confused by your request in that I don't see
> > how
> >    this could happen.
> >
> >    SCTP has the ability to identify 300+ sack gaps. I think this
> >    is why the wording is the way it is. We could not conceive of a
> > situation
> >    where the SACK would come back (outside of reneging) and not list
> > what
> >    was previously there. Especially if the SACK is a response to the
> >    fast-retransmit.
> >
> >    In theory it *should* contain all the gap acks that were present up
> > to
> >    your "fast recovery point".
> >
> >    Like Brian I too don't remember ever making a "fast recovery point"
> > in
> >    SCTP.
> >
> >    Now I guess you could get a situation where the fast retransmit
> > passed
> the
> >    last TSN sent and the sender is thus responding.. but thats still
> >    pending data that *may* still arrive.
> >
> >    So unless the sender purposely stops gap-acking previously gap-acked
> >    packets (reneged) then I don't see how this could happen.
> >
> >    Could you explain how you see this could happen .. it could be I am
> >    missing something that is clear to you..
> >
> >    Thanks
> >
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From nobody Thu Oct 23 13:21:42 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669B61AD0C5 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 13:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 SfxrkFwTQH-3 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 13:21:37 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 598F21ACFD3 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 13:21:37 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NKLalO016225; Thu, 23 Oct 2014 14:21:36 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9NKLZo0014315; Thu, 23 Oct 2014 14:21:35 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9NKLYkT014314; Thu, 23 Oct 2014 14:21:34 -0600
Date: Thu, 23 Oct 2014 14:21:34 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141023202134.GA14016@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Randall Stewart <rrs@netflix.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg@ietf.org
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ru_TzPggwvpxn5BuYYiFXHGos0Y
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 23 Oct 2014 20:21:39 -0000

Karen,

Please see comments below:

Karen Elisabeth Egede Nielsen wrote:    (Thu, 23 Oct 2014 21:35:06)
> Hi,
> 
> The TSN are sent at the same time, not sequentially.
> 
> Assume they chunks are  ~0,6*MTU, then there would be no CWND constrains and
> no HB burst constraints.
> This I am saying just to avoid to get into such discussions or bundling
> discussions for that matter.
> 
> BR, Karen

Did you mean like this:

 TSN 1 ---> X
 TSN 2 ---------\
 TSN 3 --------\ \
 TSN 4 -------\ \ \
 TSN 5 ---> X  \ \ \
 TSN 6 ---> X   \ \ \
                 \ \ \-------------->
       <----------\-\---------------- SACK 0, 2-2
 TSN 1 peg = 1     \ \-------------->
       <------------\---------------- SACK 0, 2-3
 TSN 1 peg = 2       \-------------->
       <----------------------------- SACK 0, 2-4
 TSN 1 peg = 3
 Enter FR exit point = TSN 1
 TSN 1 ----------------------------->
       <----------------------------- SACK 4
 CA TSN >= exit point => exit FR


And like this:

 TSN 1 ---> X
 TSN 2 ------------\
 TSN 3 ---> X       \
 TSN 4 ------------\ \
 TSN 5 ---> X       \ \
 TSN 6 ------------\ \ \
 TSN 7 ---> X       \ \ \
 TSN 8 ---> X        \ \ \
                      \ \ \-------->
       <---------------\-\---------- SACK 0, 2-2
 TSN 1 peg = 1          \ \-------->
       <-----------------\---------- SACK 0, 2-2, 4-4
 TSN 1 peg = 2, 3 peg = 1 \-------->
       <---------------------------- SACK 0, 2-2, 4-4, 6-6
 TSN 1 peg = 3, TSN 3 peg = 2, TSN 5 peg = 1
 Enter FR  exit point = TSN 5
 TSN 1 ----------------------------->
       <----------------------------- SACK 2, 4-4, 6-6
 TSN 3 peg = 3, TSN 5 peg = 2
 TSN 3 ----------------------------->
       <----------------------------- SACK 4, 6-6
 TSN 5 peg = 3
 TSN 5 ----------------------------->
       <----------------------------- SACK 6
 CA TSN >= exit point => exit FR


The result is the same.

Again, at what point is the FR exit point greater than the
highest outstanding TSN in a SACK?

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Thu Oct 23 21:40:54 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF071A8892; Thu, 23 Oct 2014 21:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 1y5rI9JPf4kr; Thu, 23 Oct 2014 21:40:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BCF1A87EB; Thu, 23 Oct 2014 21:40:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141024044045.18449.89604.idtracker@ietfa.amsl.com>
Date: Thu, 23 Oct 2014 21:40:45 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/jkceBfbcu4_YjLuMY5KnarvPmZo
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-failover-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 04:40:47 -0000

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           : Quick Failover Algorithm in SCTP
        Authors         : Yoshifumi Nishida
                          Preethi Natarajan
                          Armando Caro
                          Paul D. Amer
                          Karen E. E. Nielsen
	Filename        : draft-ietf-tsvwg-sctp-failover-06.txt
	Pages           : 18
	Date            : 2014-10-23

Abstract:
   One of the major advantages of SCTP is that it supports multi-homed
   communication.  A multi-homed SCTP end-point has the ability to
   withstand network failures by migrating the traffic from an inactive
   network to an active one.  However, if the [RFC4960] specified
   failover operation is followed there can be a significant delay in
   the migration to the active destination addresses, thus severely
   reducing the effectiveness of SCTP multi-homed operation.

   The memo complements RFC4960 by the introduction of the Potentially
   Failed state and associated new Quick Failover operation to apply
   during network failure and specifies for SCTP senders to support this
   more performance optimal failover procedure as an add-on to the
   [RFC4960] failover operation.  The memo in addition complements
   [RFC4960] by introduction of alternative switchover operation modes
   for the data transfer path management after a failover.  These
   operation modes offer for more performance optimal operation in some
   network environments.  From the perspective of this memo the
   implementation of the additional switchover operation modes is
   considered optional.

   The procedures defined require only minimal modifications to the
   current specification.  The procedures are sender-side only and do
   not impact the SCTP receiver.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-failover-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct 23 21:55:16 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D1F1AD3F6; Thu, 23 Oct 2014 21:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 SYG7CaGr_8Bv; Thu, 23 Oct 2014 21:55:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4992B1A887B; Thu, 23 Oct 2014 21:55:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141024045512.18899.86823.idtracker@ietfa.amsl.com>
Date: Thu, 23 Oct 2014 21:55:12 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/WC081r2S2CE9ETt-vfS4hLHL3Cg
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-failover-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 04:55:14 -0000

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           : Quick Failover Algorithm in SCTP
        Authors         : Yoshifumi Nishida
                          Preethi Natarajan
                          Armando Caro
                          Paul D. Amer
                          Karen E. E. Nielsen
	Filename        : draft-ietf-tsvwg-sctp-failover-07.txt
	Pages           : 18
	Date            : 2014-10-23

Abstract:
   One of the major advantages of SCTP is that it supports multi-homed
   communication.  A multi-homed SCTP end-point has the ability to
   withstand network failures by migrating the traffic from an inactive
   network to an active one.  However, if the [RFC4960] specified
   failover operation is followed there can be a significant delay in
   the migration to the active destination addresses, thus severely
   reducing the effectiveness of SCTP multi-homed operation.

   The memo complements RFC4960 by the introduction of the Potentially
   Failed state and associated new Quick Failover operation to apply
   during network failure and specifies for SCTP senders to support this
   more performance optimal failover procedure as an add-on to the
   [RFC4960] failover operation.  The memo in addition complements
   [RFC4960] by introduction of alternative switchover operation modes
   for the data transfer path management after a failover.  These
   operation modes offer for more performance optimal operation in some
   network environments.  From the perspective of this memo the
   implementation of the additional switchover operation modes is
   considered optional.

   The procedures defined require only minimal modifications to the
   current specification.  The procedures are sender-side only and do
   not impact the SCTP receiver.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-failover-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct 23 21:59:15 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B27B1A888B for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 21:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.215
X-Spam-Level: 
X-Spam-Status: No, score=0.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Qh00edo9fg_z for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 21:59:10 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC9D51A8892 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 21:59:09 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2632B27824E for <tsvwg@ietf.org>; Fri, 24 Oct 2014 13:59:06 +0900 (JST)
Received: by mail-wg0-f50.google.com with SMTP id a1so277785wgh.9 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 21:59:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.207.77 with SMTP id lu13mr1594511wic.12.1414126744830; Thu, 23 Oct 2014 21:59:04 -0700 (PDT)
Received: by 10.194.3.82 with HTTP; Thu, 23 Oct 2014 21:59:04 -0700 (PDT)
In-Reply-To: <CAO249ye=a4+nZKOhn0-iATeyMGJTcja4grc_MUUv=DHb9+MY5g@mail.gmail.com>
References: <7223b846875e491ff07fbd22b1d193bc.squirrel@www.erg.abdn.ac.uk> <CAO249ye=a4+nZKOhn0-iATeyMGJTcja4grc_MUUv=DHb9+MY5g@mail.gmail.com>
Date: Thu, 23 Oct 2014 21:59:04 -0700
Message-ID: <CAO249ycBRny8orOY8ajoQh1BXcFeqihVZ56aVbz0LKWtd0nEPg@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3a16a4b0b7d0506240a28
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/sfgO085NN62SxTFmAavTYeijDps
Subject: [tsvwg] Fwd:  Comments on SCTP draft-ietf-tsvwg-sctp-failover-05
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 04:59:14 -0000

--001a11c3a16a4b0b7d0506240a28
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Gorry,

Thanks for the detailed reviews (again!)
We've updated our draft based on your suggestions and submitted it as -07
draft. (Sorry, I've made a mistake in 06 and resubmitted 07)
We believe there's no discrepancy, but just in case, I've inserted some
comments in lines.

Thank you so much!
--
Yoshi


On Fri, Oct 3, 2014 at 2:26 AM, <gorry@erg.abdn.ac.uk> wrote:

> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-05
>
> As a Chair, I think the above draft seems in good shape from a protocol
> perspective, if people see other ways to improve the protocol - it would
> be good to know at this stage.
>
> The authors have requested that this be considered as a PS. I have
> therefore given this a more critical read - especially carefully looking
> at the language, and suggest they consider the comments below and re-issu=
e
> the draft.  If we are to consider the draft as PS, then  I think a sectio=
n
> needs to be added to motivate this change (which *WILL* be confirmed on
> this list after this revision).
>
> Comments follow on the document (with no intended change to thee
> protocol), please consider these - I'd love to hear from others on the
> list if they also have any comments on this version!
>
> Gorry
> (tsvwg chair)
>
> =E2=80=94
>
>
> Section 4: (NiT in language)
>
> /In order to address the issues described in Section 3, We propose to
>    update SCTP path management scheme as follows./
> to
> /To address the issues described in Section 3, this section
>    updates SCTP path management:/
> -If this is to be considered as a PS, it /specifies/ the update.
>
> Section 4.1: (language, there is no ordering so avoid this usage):
> /In order to minimize performance impact during failover/
> to
> /To minimise the performance impact during failover/
>

Done.


>
> Section 4.1 (structure)
>
> - If I understand correctly, the first two paras, including the 2 bullets
> are actually informative discussion to introduce the method, if this is
> the case could these be moved to section 4, so thats action 4.1 includes
> the RFC2119 protocol update.
>

We've split Section 4.1 into two sections: "concept" and "algorithm
detail". Section 4.2 includes 2119 update.
We've also changed the title of Section 4.3 to clarify this is an optional
feature.


>
> Section 4.1: (NiT in language)
> /tweaking/tuning/
>
> /This proposal introduces/This new method introduces/
>

Done.

>
>
> Requirement  1 (RFC2119)
> /The recommended value of PFMR =3D 0  when quick failover is used.  /
> - is this /RECOMMENDED/ ?
>

We've changed to RECOMMENDED.


>
> Requirement 3: (NiT in language)
> /PF state with least error count/
> /PF state with the lowest error count/
>
> /In case of multiple PF/
> /When there are multiple PF/
>

Done.


>
> Requirement 4: (Clarity)


> /This
>         specification recommends that heartbeats be send to PF
>         destinations independently from whether the Path Heartbeat
>         function (Section 8.3 of [RFC4960]) is enabled for the
>         destination address or not./
> - This appears at the end of the requirement. I'm not sure what is
> intended, could it be that this
> RECOMMENDS the use of heartbeats with PF, in which case I'd have expected
> this requirement perhaps to be stated first?
>

We've changed the sentence to:

        It is RECOMMENDED that heartbeats be send to PF destinations
        regardless of whether the Path Heartbeat function
        (Section 8.3 of [RFC4960]) is enabled for the destination
        address or not.

Since this is not strong requirement, I think it doesn't have to be stated
first.


>
> Requirement 7: (NiT in language)
>
> /state with least error count/
> /state with the lowest error count/
>
> /In  case of multiple destinations with same error count in inactive
>         state/
> /When there are multiple destinations with the same error count in the
> inactive state/
>

Done.

>
> Requirement 4: (RFC2119)
>
>
> /In order to support this
>         prescription a sender SHOULD allow for increment of the
>         destination error counters up to some reasonable limit above
>         PMR+1/
> /Therefore, a sender SHOULD allow for incrementing the
>         destination error counters up to some reasonable limit above
>         PMR+1/
> - I can see the goal of reasonable limit, but is this actually a "limit"
> - that stops further incrementing or "permits" the value to be incremente=
d
> beyond PMR+1?
>

Done. We've changed this to:

Therefore, a sender SHOULD allow for incrementing the
destination error counters up to some reasonable limit larger than PMR+1.


>
> /A  sender MAY choose to deploy other strategies than the above/
> - good to state this, but this is the second part of a SHOULD statement
> explaining options, as such I do not think it needs an upper case /MAY/
> and suspect that /may/ will be sufficient.
>

Agree. changed to may.


>
> Requirement 8: (NiT in language)
>
> /ACKs for chunks which have been transmitted to multiple
>         destinations (i.e., a chunk which has been retransmitted to a
>         different destination than the destination to which the chunk
>         was first transmitted) /
> /ACKs for chunks that have been transmitted to multiple
>         destinations (i.e., a chunk that has been retransmitted to a
>         different destination than the destination to which the chunk
>         was first transmitted) /
> - change /which/ to /that/
>
> Use upper case for /ack/?
>

Done.

>
> /In this respect then it is specified
>         that bytes of a newly acknowledged chunk which has been
>         transmitted to multiple destinations SHOULD, when the conditions
>         for such contribution is fulfilled following the prescriptions
>         of Section 7.2 of [RFC4960], contribute to the congestion window
>         growth towards the destination to which the chunk was last
>         transmitted. /
> - This clause is rather complex and long, please rephrase!
>


We've changed it to:
     The bytes of a newly acknowledged chunk which has been transmitted

     to multiple destinations SHOULD be considered for contribution to

     the congestion window growth towards the destination where the chunk
was last sent.
     The contribution of the acked bytes to the window growth is subject to

     the prescriptions described in Section 7.2 of [RFC4960] is fulfilled.



>
> /A SCTP sender MAY apply a different approach for
>         both the error count handling as well as the congestion control
>         growth handling does it have unequivocally information as to
>         which destination (including multiple destinations) the chunk
>         reached.  /
>
> - This clause is rather complex, and hard to parse, please rephrase!
>


We've changed this to:

        A SCTP sender MAY apply a different approach for
        both the error count handling and the congestion control growth
        handling based on unequivocally information on which destination
        (including multiple destinations) the chunk reached.


>
> Requirement 10: (Clarity)
>
> /SCTP SHOULD provide the means to expose the PF state /
> - Is this the SCTP stack should expose to the ULP, please clarify, and us=
e
> language similar to other SCTP RFCs.
>
> /Active state ./ - remove space before stop,
>
>
> /When  doing such SCTP MUST /
> /When  this, the SCTP stack MUST /
>
> /suppress exposure of PF state to ULP.  /
> /suppress exposure of PF state to the ULP.  /
>

Done.


>
> - I found this requirement not so clearly explained, and rather hard to
> comprehend from the text.
>

We've changed this to:

            SCTP stack SHOULD provide the ULP with the means to expose the
PF state of its
            destinations as well as the means to notify the state
transitions from Active to PF and vice-versa.
            When doing this, such SCTP stack MUST provide the ULP with the
means to suppress exposure of PF
            state and association state transitions as well.


>
> Section 4.2: (RFC2119, Clarity)
>
> /Post failover then, by [RFC4960] behavior, an SCTP sender migrates
>    the traffic back to the original primary destination once this
>    destination becomes active anew.  /
> - This doesn=E2=80=99t seem to make sense.
>


We've changed this to:

   In [RFC4960], an SCTP sender migrates the traffic back to the
   original primary destination once this destination becomes active
   again.


> No 1
>
> /Any setting of PSMR < PFMR
>        MUST be rejected by the implementation./
> - MUST be rejected seems odd. Can you phrase this the other way around?
> The PSMR MUST be set so that PSMAR>=3DPFMR.
> - This seems to contradict the previous SHOULD.
>

We've changed this to:
            The PSMR MUST be set greater or equal to the PFMR value.

            Implementations MUST reject any other values of PSMR.


>
> No 2 and 3 do not introduce RFC 2119 requirements. Is this intentional, i=
f
> so why?
>
> No 4
> /support set of PSMR =3D PFMR/
> /support the setting of PSMR =3D PFMR/
>
>
> / We recommend that SCTP-PF sticks to the standard RFC4960 switchback
>    behavior as default/
> - is this intended to be:
> /This specifications RECOMMENDS a default configuration that uses standar=
d
> RFC4960 switchback./
>
> /However in order to support//However, to support/
>

done

>
> - does this section need the MAYs in capital letters, since it follows a
> SHOULD?
>

Yes. changed to MAY


>
> =E2=80=94
>
> Section 6:
>
> I=E2=80=99m happy with this clause, if it is correct. For clarity I=E2=80=
=99d prefer the
> section is prefixed by something like:
> =E2=80=9CSecutity considerations for the use of SCTP are discussed in RFC=
xxx and
> RFCyyyy.=E2=80=9D
>

Yes. We've added the sentences in the section.


> Appendices: (Structure)
>
> Two appendices are provided, but seem not to be described in the body of
> the specification. - please either add references were appropriate to the
> appendices or remove them.
>

We've add some texts to refer them at the end of Section 1.


>
> Proposed change of status
>
> I would expect such a section to b marked for removal before publication
> by RFC-Ed (since this is ONLY an AD/IESG decision - that provides a coupl=
e
> of short paras that document the evolution of the draft from EXP to PS,
> and motivate that the experimental considerations are no longer an issue.
> I believe the authors have clearly put this argument in the past, and hop=
e
> that this is not a difficult section to add.
>
> We've added Section 8 for this.

--001a11c3a16a4b0b7d0506240a28
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote">Hi Gorry,</div><div class=3D"gm=
ail_quote"><br></div><div class=3D"gmail_quote">Thanks for the detailed rev=
iews (again!)</div><div class=3D"gmail_quote">We&#39;ve updated our draft b=
ased on your suggestions and submitted it as -07 draft. (Sorry, I&#39;ve ma=
de a mistake in 06 and resubmitted 07)</div><div class=3D"gmail_quote">We b=
elieve there&#39;s no discrepancy, but just in case, I&#39;ve inserted some=
 comments in lines.</div><div class=3D"gmail_quote"><br></div><div class=3D=
"gmail_quote">Thank you so much!<br><div dir=3D"ltr">--</div><div dir=3D"lt=
r">Yoshi<br><div><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te"><span class=3D"">On Fri, Oct 3, 2014 at 2:26 AM,  <span dir=3D"ltr">&lt=
;<a href=3D"mailto:gorry@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abdn.a=
c.uk</a>&gt;</span> wrote:<br></span><div><div class=3D"h5"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
"><a href=3D"https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-05"=
 target=3D"_blank">https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failov=
er-05</a><br>
<br>
As a Chair, I think the above draft seems in good shape from a protocol<br>
perspective, if people see other ways to improve the protocol - it would<br=
>
be good to know at this stage.<br>
<br>
The authors have requested that this be considered as a PS. I have<br>
therefore given this a more critical read - especially carefully looking<br=
>
at the language, and suggest they consider the comments below and re-issue<=
br>
the draft.=C2=A0 If we are to consider the draft as PS, then=C2=A0 I think =
a section<br>
needs to be added to motivate this change (which *WILL* be confirmed on<br>
this list after this revision).<br>
<br>
Comments follow on the document (with no intended change to thee<br>
protocol), please consider these - I&#39;d love to hear from others on the<=
br>
list if they also have any comments on this version!<br>
<br>
Gorry<br>
(tsvwg chair)<br>
<br>
=E2=80=94<br>
<br>
<br>
Section 4: (NiT in language)<br>
<br>
/In order to address the issues described in Section 3, We propose to<br>
=C2=A0 =C2=A0update SCTP path management scheme as follows./<br>
to<br>
/To address the issues described in Section 3, this section<br>
=C2=A0 =C2=A0updates SCTP path management:/<br>
-If this is to be considered as a PS, it /specifies/ the update.<br>
<br>
Section 4.1: (language, there is no ordering so avoid this usage):<br>
/In order to minimize performance impact during failover/<br>
to<br>
/To minimise the performance impact during failover/<br></blockquote><div><=
br></div></div></div><div>Done.</div><span class=3D""><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
<br>
Section 4.1 (structure)<br>
<br>
- If I understand correctly, the first two paras, including the 2 bullets<b=
r>
are actually informative discussion to introduce the method, if this is<br>
the case could these be moved to section 4, so thats action 4.1 includes<br=
>
the RFC2119 protocol update.<br></blockquote><div><br></div></span><div>We&=
#39;ve split Section 4.1 into two sections: &quot;concept&quot; and &quot;a=
lgorithm detail&quot;. Section 4.2 includes 2119 update.</div><div>We&#39;v=
e also changed the title of Section 4.3 to clarify this is an optional feat=
ure.</div><div>=C2=A0<br></div><span class=3D""><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Section 4.1: (NiT in language)<br>
/tweaking/tuning/<br>
<br>
/This proposal introduces/This new method introduces/<br></blockquote><div>=
<br></div></span><div>Done.=C2=A0<br></div><span class=3D""><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">
<br>
<br>
Requirement=C2=A0 1 (RFC2119)<br>
/The recommended value of PFMR =3D 0=C2=A0 when quick failover is used.=C2=
=A0 /<br>
- is this /RECOMMENDED/ ?<br></blockquote><div><br></div></span><div>We&#39=
;ve changed to RECOMMENDED.</div><span class=3D""><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wid=
th:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-l=
eft:1ex">
<br>
Requirement 3: (NiT in language)<br>
/PF state with least error count/<br>
/PF state with the lowest error count/<br>
<br>
/In case of multiple PF/<br>
/When there are multiple PF/<br></blockquote><div><br></div></span><div>Don=
e.</div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:=
rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Requirement 4: (Clarity)=C2=A0</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
/This<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 specification recommends that heartbeats be sen=
d to PF<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations independently from whether the Pat=
h Heartbeat<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 function (Section 8.3 of [RFC4960]) is enabled =
for the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination address or not./<br>
- This appears at the end of the requirement. I&#39;m not sure what is<br>
intended, could it be that this<br>
RECOMMENDS the use of heartbeats with PF, in which case I&#39;d have expect=
ed<br>
this requirement perhaps to be stated first?<br></blockquote><div><br></div=
></span><div>We&#39;ve changed the sentence to:</div><div><br></div><div><d=
iv>=C2=A0 =C2=A0 =C2=A0 =C2=A0 It is RECOMMENDED that heartbeats be send to=
 PF destinations</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 regardless of whethe=
r the Path Heartbeat function</div><span class=3D""><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 (Section 8.3 of [RFC4960]) is enabled for the destination</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 address or not.</div></span></div><div><br>=
</div><div>Since this is not strong requirement, I think it doesn&#39;t hav=
e to be stated first.</div><div>=C2=A0</div><span class=3D""><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px=
;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1e=
x">
<br>
Requirement 7: (NiT in language)<br>
<br>
/state with least error count/<br>
/state with the lowest error count/<br>
<br>
/In=C2=A0 case of multiple destinations with same error count in inactive<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 state/<br>
/When there are multiple destinations with the same error count in the<br>
inactive state/<br></blockquote><div><br></div></span><div>Done.=C2=A0</div=
><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">
<br>
Requirement 4: (RFC2119)<br>
<br>
<br>
/In order to support this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 prescription a sender SHOULD allow for incremen=
t of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination error counters up to some reasonabl=
e limit above<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PMR+1/<br>
/Therefore, a sender SHOULD allow for incrementing the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destination error counters up to some reasonabl=
e limit above<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PMR+1/<br>
- I can see the goal of reasonable limit, but is this actually a &quot;limi=
t&quot;<br>
- that stops further incrementing or &quot;permits&quot; the value to be in=
cremented<br>
beyond PMR+1?<br></blockquote><div><br></div></span><div>Done. We&#39;ve ch=
anged this to:</div><div><br></div><div><span class=3D"">Therefore, a sende=
r SHOULD allow for incrementing the</span></div><div>destination error coun=
ters up to some reasonable limit larger than=C2=A0PMR+1.<br></div><span cla=
ss=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);=
border-left-style:solid;padding-left:1ex">
<br>
/A=C2=A0 sender MAY choose to deploy other strategies than the above/<br>
- good to state this, but this is the second part of a SHOULD statement<br>
explaining options, as such I do not think it needs an upper case /MAY/<br>
and suspect that /may/ will be sufficient.<br></blockquote><div><br></div><=
/span><div>Agree. changed to may.</div><span class=3D""><div>=C2=A0<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid=
;padding-left:1ex">
<br>
Requirement 8: (NiT in language)<br>
<br>
/ACKs for chunks which have been transmitted to multiple<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations (i.e., a chunk which has been retr=
ansmitted to a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 different destination than the destination to w=
hich the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 was first transmitted) /<br>
/ACKs for chunks that have been transmitted to multiple<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 destinations (i.e., a chunk that has been retra=
nsmitted to a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 different destination than the destination to w=
hich the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 was first transmitted) /<br>
- change /which/ to /that/<br>
<br>
Use upper case for /ack/?<br></blockquote><div><br></div></span><div>Done.=
=C2=A0</div><span class=3D""><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex">
<br>
/In this respect then it is specified<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that bytes of a newly acknowledged chunk which =
has been<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 transmitted to multiple destinations SHOULD, wh=
en the conditions<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for such contribution is fulfilled following th=
e prescriptions<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 of Section 7.2 of [RFC4960], contribute to the =
congestion window<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 growth towards the destination to which the chu=
nk was last<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 transmitted. /<br>
- This clause is rather complex and long, please rephrase!<br></blockquote>=
<div><br></div><div><br></div></span><div>We&#39;ve changed it to:</div><di=
v><div>=C2=A0 =C2=A0 =C2=A0The bytes of a newly acknowledged chunk which ha=
s been transmitted =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</div><div>=C2=A0 =C2=
=A0 =C2=A0to multiple destinations SHOULD be considered for contribution to=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0the =
congestion window growth towards the destination where the chunk was last s=
ent. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0</div><div>=C2=A0 =C2=
=A0 =C2=A0The contribution of the acked bytes to the window growth is subje=
ct to =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0the prescriptions de=
scribed in Section 7.2 of [RFC4960] is fulfilled. =C2=A0 =C2=A0 =C2=A0 =C2=
=A0</div></div><div>=C2=A0<br></div><span class=3D""><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-=
left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
/A SCTP sender MAY apply a different approach for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 both the error count handling as well as the co=
ngestion control<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 growth handling does it have unequivocally info=
rmation as to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 which destination (including multiple destinati=
ons) the chunk<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 reached.=C2=A0 /<br>
<br>
- This clause is rather complex, and hard to parse, please rephrase!<br></b=
lockquote><div><br></div><div><br></div></span><div>We&#39;ve changed this =
to:</div><div><br></div><div><span class=3D""><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 A SCTP sender MAY apply a different approach for</div></span><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 both the error count handling and the congestion c=
ontrol growth</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 handling based on unequ=
ivocally information on which destination</div><span class=3D""><div>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 (including multiple destinations) the chunk reached.=
=C2=A0</div></span></div><div><br></div><span class=3D""><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
Requirement 10: (Clarity)<br>
<br>
/SCTP SHOULD provide the means to expose the PF state /<br>
- Is this the SCTP stack should expose to the ULP, please clarify, and use<=
br>
language similar to other SCTP RFCs.<br>
<br>
/Active state ./ - remove space before stop,<br>
<br>
<br>
/When=C2=A0 doing such SCTP MUST /<br>
/When=C2=A0 this, the SCTP stack MUST /<br>
<br>
/suppress exposure of PF state to ULP.=C2=A0 /<br>
/suppress exposure of PF state to the ULP.=C2=A0 /<br></blockquote><div><br=
></div></span><div>Done.</div><span class=3D""><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left=
:1ex">
<br>
- I found this requirement not so clearly explained, and rather hard to<br>
comprehend from the text.<br></blockquote><div><br></div></span><div>We&#39=
;ve changed this to:</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 SCTP stack SHOULD provide the ULP with the means to expose th=
e PF state of its =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</div>=
<div>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0destinations as well as=
 the means to notify the state transitions from Active to PF and vice-versa=
. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</div><div>=
=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0When doing this, such SCTP s=
tack MUST provide the ULP with the means to suppress exposure of PF =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 state and association =
state transitions as well. =C2=A0</div><span class=3D""><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pad=
ding-left:1ex">
<br>
Section 4.2: (RFC2119, Clarity)<br>
<br>
/Post failover then, by [RFC4960] behavior, an SCTP sender migrates<br>
=C2=A0 =C2=A0the traffic back to the original primary destination once this=
<br>
=C2=A0 =C2=A0destination becomes active anew.=C2=A0 /<br>
- This doesn=E2=80=99t seem to make sense.<br></blockquote><div><br></div><=
div><br></div></span><div>We&#39;ve changed this to:</div><div><br></div><d=
iv>=C2=A0 =C2=A0In [RFC4960], an SCTP sender migrates the traffic back to t=
he</div><span class=3D""><div>=C2=A0 =C2=A0original primary destination onc=
e this destination becomes active</div></span><div>=C2=A0 =C2=A0again. =C2=
=A0</div><div><br></div><span class=3D""><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:r=
gb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
No 1<br>
<br>
/Any setting of PSMR &lt; PFMR<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0MUST be rejected by the implementation./<br>
- MUST be rejected seems odd. Can you phrase this the other way around?<br>
The PSMR MUST be set so that PSMAR&gt;=3DPFMR.<br>
- This seems to contradict the previous SHOULD.<br></blockquote><div><br></=
div></span><div>We&#39;ve changed this to:</div><div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 The PSMR MUST be set greater or equal to the PFMR =
value. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Implementations =
MUST reject any other values of PSMR.</div></div><div>=C2=A0<br></div><span=
 class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex">
<br>
No 2 and 3 do not introduce RFC 2119 requirements. Is this intentional, if<=
br>
so why?<br>
<br>
No 4<br>
/support set of PSMR =3D PFMR/<br>
/support the setting of PSMR =3D PFMR/<br>
<br>
<br>
/ We recommend that SCTP-PF sticks to the standard RFC4960 switchback<br>
=C2=A0 =C2=A0behavior as default/<br>
- is this intended to be:<br>
/This specifications RECOMMENDS a default configuration that uses standard<=
br>
RFC4960 switchback./<br>
<br>
/However in order to support//However, to support/<br></blockquote><div><br=
></div></span><div>done=C2=A0</div><span class=3D""><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
- does this section need the MAYs in capital letters, since it follows a<br=
>
SHOULD?<br></blockquote><div><br></div></span><div>Yes. changed to MAY</div=
><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<br>
=E2=80=94<br>
<br>
Section 6:<br>
<br>
I=E2=80=99m happy with this clause, if it is correct. For clarity I=E2=80=
=99d prefer the<br>
section is prefixed by something like:<br>
=E2=80=9CSecutity considerations for the use of SCTP are discussed in RFCxx=
x and<br>
RFCyyyy.=E2=80=9D<br></blockquote><div><br></div></span><div>Yes. We&#39;ve=
 added the sentences in the section.</div><span class=3D""><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">
Appendices: (Structure)<br>
<br>
Two appendices are provided, but seem not to be described in the body of<br=
>
the specification. - please either add references were appropriate to the<b=
r>
appendices or remove them.<br></blockquote><div><br></div></span><div>We&#3=
9;ve add some texts to refer them at the end of Section 1.</div><span class=
=3D""><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex">
<br>
Proposed change of status<br>
<br>
I would expect such a section to b marked for removal before publication<br=
>
by RFC-Ed (since this is ONLY an AD/IESG decision - that provides a couple<=
br>
of short paras that document the evolution of the draft from EXP to PS,<br>
and motivate that the experimental considerations are no longer an issue.<b=
r>
I believe the authors have clearly put this argument in the past, and hope<=
br>
that this is not a difficult section to add.<br><br></blockquote></span><di=
v>We&#39;ve added Section 8 for this.</div><div><br></div></div></div></div=
></div>
</div><br></div>

--001a11c3a16a4b0b7d0506240a28--


From nobody Thu Oct 23 23:23:58 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE891A88D1 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 F6d1BTSjSTMa for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:23:51 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C3B1A1BED for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:23:50 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id d1so411540wiv.2 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:23:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=HQMxQk+wmjQXb99PKBrLuEgLT5WKYxUEw19QnfXcomw=; b=iG1xQOgMKGizLb+A9774cqOSs08F/3OUGjElviAEChZrCBuAscZEH23w9Rv1Gtuq67 pkbhSHFMmSa1QPumFphuO4RULvOs8McMUNRLKhblzxQWxl9Dquz2T7lF6H/EZceTauC5 CP9MMxE8NF2BmUuJgYPr7XcsvxKnXSYK9jrAI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=HQMxQk+wmjQXb99PKBrLuEgLT5WKYxUEw19QnfXcomw=; b=LxyaYwJPqbG9oUeKK70CHI2bu4YxXLguoG4MCbmm3q2jBuwb888TQMoSKpsl1onhEz 76pBsvGeYoXr0OD7+fmZOcSSzDJATlXI+eFFtcYTcf8o2UHTLtjQDK7GgKQTCrmNS+Ps nDfCpaGJPwW5kXWzi7CCmmKhfJyqA9oUEUptxSJioTWhEHR1bKNKwIu6dvc0Qj6qyFZx uI2L00E8uPkoPcwrhuFAgzDJtAN1jv33LYlMpQjampll0dpmeRuS61BCgcZfc09F2YLT 9TUTZj0sT745bk+PuXutCX1VJtgQCjm6/gK9J88KwyPc+z7N1NOeXm8CDhcKQSvNnq4d T3kQ==
X-Gm-Message-State: ALoCoQllfUb2Ql8PlHblv1aEcg+uqx2+nwbc9JEYQVH00I14z0i6qf5Qc9D3u6sDuTdJZnDxNFZPMJGVObvtxXAkSqtAe5ZVQPa1ui1xzZ9kTn2BN1aIqZA=
X-Received: by 10.180.73.19 with SMTP id h19mr1810716wiv.3.1414131829156; Thu, 23 Oct 2014 23:23:49 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com> <5B3BC2A5-E440-49B1-AB7D-BBD47CB7F88D@netflix.com>
In-Reply-To: <5B3BC2A5-E440-49B1-AB7D-BBD47CB7F88D@netflix.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4AtTxU80B9+M+8gKdj796APN+kL8BmLf/NptbBYMA
Date: Fri, 24 Oct 2014 08:23:48 +0200
Message-ID: <050f1d7b98045826842e732c21379e4c@mail.gmail.com>
To: Randall Stewart <rrs@netflix.com>
Content-Type: multipart/alternative; boundary=f46d0438959b57c22f05062539f2
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/EicWu43Pv5sBiGwcIs9q2rO_PL0
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 06:23:54 -0000

--f46d0438959b57c22f05062539f2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Randy,



I am ok with this not being in RFC4960,

but I don=E2=80=99t really buy the argument about not knowing or the argume=
nt about
the delays.

This is generally true for ALL mis-indication counts.

Let=E2=80=99s consider this discussion as closed, we/I will get what we/I w=
ant from
RFC6675 additions to SCTP.



However, getting these arguments from you, then out of curiosity, I wonder
if you have the time and

the strength to explain the motivation for the existing text of RFC4960
saying:



If an endpoint is in Fast Recovery and a SACK

arrives that advances the Cumulative TSN Ack Point, the

miss indications are incremented for all TSNs reported

missing in the SACK.



Thanks J



BR, Karen







*From:* Randall Stewart [mailto:rrs@netflix.com]
*Sent:* 23. oktober 2014 21:47
*To:* Karen Elisabeth Egede Nielsen
*Cc:* bidulock@openss7.org; Michael Tuexen; tsvwg@ietf.org
*Subject:* Re: [tsvwg] SCTP mis indication counting during Fast Recovery



Karen:



Assume the TSN=E2=80=99s (same sequence) are sent 100ms apart..



Sure we can construct a condition where they all go at once, but I can

also construct a condition where they do not. You can=E2=80=99t increment F=
R counts

on things you have not been told.



You *can* implement one of the alternative schemes that folks have been
floating around

to recover from tail drops.. but that was never in the spec and won=E2=80=
=99t ever
be in 4960.

It may be in some other RFC, thats fine, but 4960 never had the changes in
it (however good

or bad they may be) you are asking for..



R

On Oct 23, 2014, at 12:35 PM, Karen Elisabeth Egede Nielsen <
karen.nielsen@tieto.com> wrote:



Hi,

The TSN are sent at the same time, not sequentially.

Assume they chunks are  ~0,6*MTU, then there would be no CWND constrains an=
d
no HB burst constraints.
This I am saying just to avoid to get into such discussions or bundling
discussions for that matter.

BR, Karen




-----Original Message-----
From: Brian F. G. Bidulock [mailto:bidulock@openss7.org
<bidulock@openss7.org>]
Sent: 23. oktober 2014 21:12
To: Karen Elisabeth Egede Nielsen
Cc: Randall Stewart; Michael Tuexen; tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery

Karen,

Please see comments inline:

On Thu, 23 Oct 2014, Karen Elisabeth Egede Nielsen wrote:


  HI,

  Let's assume SCTP send a batch of packets, the packets marked with L
  below are dropped, the packets with S are sacked.

  There is no more new data to send.

  SACKs arrive resulting in the following scorebard:

  LSSSLL

  in order from low -  high TSN.

  This makes SCTP fast retransmit the first lost packet setting FR exit
  point to last TSN.

  resulting in increase of cumack and following scoreboard (A indicate
  cumack'ed) once this TSN is sacked (which I assume).

  AAAALL

  There is 0 miscounts of the last two lost packets even if one packet
  send since them obviously have been Sacked.


TSN 1 ----------------> X
TSN 2 ----------------------------->
      <----------------------------- SACK 0, 2-2  TSN 1 peg =3D 1  TSN
3 -------------------
---------->
      <----------------------------- SACK 0, 2-3  TSN 1 peg =3D 2  TSN
4 -------------------
---------->
      <----------------------------- SACK 0, 2-4  TSN 1 peg =3D 3  Enter FR
exit point =3D
TSN 1  TSN 1 ----------------------------->
      <----------------------------- SACK 4  CA TSN >=3D exit point =3D> ex=
it
FR  TSN 5 ---
-------------> X  TSN 6 ----------------> X

At what point is the FR exit point greater than the highest  outstanding
TSN
in a SACK?  That is, at what point would pegging  up to the exit point
include
more TSNs that provided in the SACK?



  Assumed also the following loss pattern. no new packets:

  LSLSLSLL

  Then   again this makes SCTP fast retransmit the first lost packet
  setting FR exit point to last TSN.

  After SACK of the retransmitted packet we have:

  AALSLSLL and the first loss (TSN packet number 3) will now have 3
  miscounts and will be allowed to be fast retransmitted following the
  rule,

  the same again for the third L. But the ones lost in the end do not
get
  any miscounts even if they same rule that apply to the first Lost
  packets should

  apply to the last lost ones.


TSN 1 ----------------> X
TSN 2 ----------------------------->
      <----------------------------- SACK 0, 2-2  TSN 1 peg =3D 1  TSN
3 ---------------->
X  TSN 4 ----------------------------->
      <----------------------------- SACK 0, 2-2, 4-4  TSN 1 peg =3D 2, TSN
3 peg =3D 1
TSN 5 ----------------> X  TSN 6 ----------------------------->
      <----------------------------- SACK 0, 2-2, 4-4, 6-6  TSN 1 peg =3D
3, TSN 3 peg =3D
2, TSN 5 peg =3D 1  Enter FR  exit point =3D TSN 5  TSN
1 ----------------------------->
      <----------------------------- SACK 2, 4-4, 6-6  TSN 3 peg =3D 3, TSN
5 peg =3D 2
TSN 3 ----------------------------->
      <----------------------------- SACK 4, 6-6  TSN 5 peg =3D 3  TSN
5 -------------------
---------->
      <----------------------------- SACK 6  CA TSN >=3D exit point =3D> ex=
it
FR  TSN 7 ---
-------------> X  TSN 8 ----------------> X

At what point is the FR exit point greater than the highest  outstanding
TSN
in a SACK?  That is, at what point would pegging  up to the exit point
include
more TSNs that provided in the SACK?



  I have written this a little hastely. I hope this can give the
picture.

  Perhaps with this explanation also the information in slide 30-33 of
  the following now makes sense:


[1]http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,

  BR, Karen

  From: Randall Stewart [mailto:[2]rrs@netflix.com]
  Sent: 23. oktober 2014 16:48
  To: Karen Elisabeth Egede Nielsen
  Cc: Michael Tuexen; [3]bidulock@openss7.org
  Subject: Re: [tsvwg] SCTP mis indication counting during Fast
Recovery

  Karen:

  Note I dropped tsvwg due to the fact that this email would get locked
  up and held/bounced since [4]rrs@netflix.com is
  not a subscriber to tsvwg

  I like Brian am a bit confused by your request in that I don't see
how
  this could happen.

  SCTP has the ability to identify 300+ sack gaps. I think this
  is why the wording is the way it is. We could not conceive of a
situation
  where the SACK would come back (outside of reneging) and not list
what
  was previously there. Especially if the SACK is a response to the
  fast-retransmit.

  In theory it *should* contain all the gap acks that were present up
to
  your "fast recovery point".

  Like Brian I too don't remember ever making a "fast recovery point"
in
  SCTP.

  Now I guess you could get a situation where the fast retransmit
passed

the

  last TSN sent and the sender is thus responding.. but thats still
  pending data that *may* still arrive.

  So unless the sender purposely stops gap-acking previously gap-acked
  packets (reneged) then I don't see how this could happen.

  Could you explain how you see this could happen .. it could be I am
  missing something that is clear to you..

  Thanks


--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/



--------

Randall Stewart

rrs@netflix.com

803-317-4952

--f46d0438959b57c22f05062539f2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3D"DA" link=3D"blue" vlink=3D"purple"><div cla=
ss=3D"WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"fo=
nt-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color=
:#1f497d">Hi Randy,</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"E=
N-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">I am ok with this not being in RFC4960,</span></=
p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">but I do=
n=E2=80=99t really buy the argument about not knowing or the argument about=
 the delays.</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">This is generally true for ALL mis-indication counts. </span><=
/p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Let=E2=
=80=99s consider this discussion as closed, we/I will get what we/I want fr=
om RFC6675 additions to SCTP.</span></p><p class=3D"MsoNormal"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1f497d">However, getting these arguments fro=
m you, then out of curiosity, I wonder if you have the time and</span></p><=
p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">the strengt=
h to explain the motivation for the existing text of RFC4960 saying:</span>=
</p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=
</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:1=
1.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">If an endpoin=
t is in Fast Recovery and a SACK</span></p><p class=3D"MsoNormal"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;">arrives that advances the Cumulative TSN Ack Point, the<=
/span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11=
.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">miss indicatio=
ns are incremented for all TSNs reported</span></p><p class=3D"MsoNormal"><=
span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;">missing in the SACK.</span></p><p class=3D"MsoNo=
rmal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></p><p class=
=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks </span><spa=
n lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:Wingdings;color:#1f4=
97d">J</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"></span></p><p class=
=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></p><=
p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">BR, Karen</=
span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=
=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d">=C2=A0</span></p><div style=3D"border:none;border-left:soli=
d blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style=3D"border:none;bord=
er-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal=
"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahom=
a&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
> Randall Stewart [mailto:<a href=3D"mailto:rrs@netflix.com">rrs@netflix.co=
m</a>] <br><b>Sent:</b> 23. oktober 2014 21:47<br><b>To:</b> Karen Elisabet=
h Egede Nielsen<br><b>Cc:</b> <a href=3D"mailto:bidulock@openss7.org">bidul=
ock@openss7.org</a>; Michael Tuexen; <a href=3D"mailto:tsvwg@ietf.org">tsvw=
g@ietf.org</a><br><b>Subject:</b> Re: [tsvwg] SCTP mis indication counting =
during Fast Recovery</span></p></div></div><p class=3D"MsoNormal">=C2=A0</p=
><p class=3D"MsoNormal">Karen:</p><div><p class=3D"MsoNormal">=C2=A0</p></d=
iv><div><p class=3D"MsoNormal">Assume the TSN=E2=80=99s (same sequence) are=
 sent 100ms apart..=C2=A0</p></div><div><p class=3D"MsoNormal">=C2=A0</p></=
div><div><p class=3D"MsoNormal">Sure we can construct a condition where the=
y all go at once, but I can</p></div><div><p class=3D"MsoNormal">also const=
ruct a condition where they do not. You can=E2=80=99t increment FR counts</=
p></div><div><p class=3D"MsoNormal">on things you have not been told.</p></=
div><div><p class=3D"MsoNormal">=C2=A0</p></div><div><p class=3D"MsoNormal"=
>You *can* implement one of the alternative schemes that folks have been fl=
oating around</p></div><div><p class=3D"MsoNormal">to recover from tail dro=
ps.. but that was never in the spec and won=E2=80=99t ever be in 4960.</p><=
/div><div><p class=3D"MsoNormal">It may be in some other RFC, thats fine, b=
ut 4960 never had the changes in it (however good</p></div><div><p class=3D=
"MsoNormal">or bad they may be) you are asking for..</p></div><div><p class=
=3D"MsoNormal">=C2=A0</p></div><div><p class=3D"MsoNormal">R</p></div><div>=
<div><div><p class=3D"MsoNormal">On Oct 23, 2014, at 12:35 PM, Karen Elisab=
eth Egede Nielsen &lt;<a href=3D"mailto:karen.nielsen@tieto.com">karen.niel=
sen@tieto.com</a>&gt; wrote:</p></div><p class=3D"MsoNormal"><br><br></p><p=
 class=3D"MsoNormal">Hi,<br><br>The TSN are sent at the same time, not sequ=
entially.<br><br>Assume they chunks are =C2=A0~0,6*MTU, then there would be=
 no CWND constrains and<br>no HB burst constraints.<br>This I am saying jus=
t to avoid to get into such discussions or bundling<br>discussions for that=
 matter.<br><br>BR, Karen<br><br><br><br><br></p><p class=3D"MsoNormal">---=
--Original Message-----<br>From: Brian F. G. Bidulock [<a href=3D"mailto:bi=
dulock@openss7.org">mailto:bidulock@openss7.org</a>]<br>Sent: 23. oktober 2=
014 21:12<br>To: Karen Elisabeth Egede Nielsen<br>Cc: Randall Stewart; Mich=
ael Tuexen; <a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br>Subject=
: Re: [tsvwg] SCTP mis indication counting during Fast Recovery<br><br>Kare=
n,<br><br>Please see comments inline:<br><br>On Thu, 23 Oct 2014, Karen Eli=
sabeth Egede Nielsen wrote:<br><br><br></p><p class=3D"MsoNormal">=C2=A0=C2=
=A0HI,<br><br>=C2=A0=C2=A0Let&#39;s assume SCTP send a batch of packets, th=
e packets marked with L<br>=C2=A0=C2=A0below are dropped, the packets with =
S are sacked.<br><br>=C2=A0=C2=A0There is no more new data to send.<br><br>=
=C2=A0=C2=A0SACKs arrive resulting in the following scorebard:<br><br>=C2=
=A0=C2=A0LSSSLL<br><br>=C2=A0=C2=A0in order from low - =C2=A0high TSN.<br><=
br>=C2=A0=C2=A0This makes SCTP fast retransmit the first lost packet settin=
g FR exit<br>=C2=A0=C2=A0point to last TSN.<br><br>=C2=A0=C2=A0resulting in=
 increase of cumack and following scoreboard (A indicate<br>=C2=A0=C2=A0cum=
ack&#39;ed) once this TSN is sacked (which I assume).<br><br>=C2=A0=C2=A0AA=
AALL<br><br>=C2=A0=C2=A0There is 0 miscounts of the last two lost packets e=
ven if one packet<br>=C2=A0=C2=A0send since them obviously have been Sacked=
.</p><p class=3D"MsoNormal"><br>TSN 1 ----------------&gt; X<br>TSN 2 -----=
------------------------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;---=
-------------------------- SACK 0, 2-2 =C2=A0TSN 1 peg =3D 1 =C2=A0TSN<br>3=
 -------------------<br>----------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0&lt;----------------------------- SACK 0, 2-3 =C2=A0TSN 1 peg =3D 2 =C2=
=A0TSN<br>4 -------------------<br>----------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0&lt;----------------------------- SACK 0, 2-4 =C2=A0TSN 1 pe=
g =3D 3 =C2=A0Enter FR<br>exit point =3D<br>TSN 1 =C2=A0TSN 1 -------------=
----------------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;-----------=
------------------ SACK 4 =C2=A0CA TSN &gt;=3D exit point =3D&gt; exit<br>F=
R =C2=A0TSN 5 ---<br>-------------&gt; X =C2=A0TSN 6 ----------------&gt; X=
<br><br>At what point is the FR exit point greater than the highest =C2=A0o=
utstanding<br>TSN<br>in a SACK?=C2=A0 That is, at what point would pegging =
=C2=A0up to the exit point<br>include<br>more TSNs that provided in the SAC=
K?<br><br><br><br></p><p class=3D"MsoNormal">=C2=A0=C2=A0Assumed also the f=
ollowing loss pattern. no new packets:<br><br>=C2=A0=C2=A0LSLSLSLL<br><br>=
=C2=A0=C2=A0Then =C2=A0=C2=A0again this makes SCTP fast retransmit the firs=
t lost packet<br>=C2=A0=C2=A0setting FR exit point to last TSN.<br><br>=C2=
=A0=C2=A0After SACK of the retransmitted packet we have:<br><br>=C2=A0=C2=
=A0AALSLSLL and the first loss (TSN packet number 3) will now have 3<br>=C2=
=A0=C2=A0miscounts and will be allowed to be fast retransmitted following t=
he<br>=C2=A0=C2=A0rule,<br><br>=C2=A0=C2=A0the same again for the third L. =
But the ones lost in the end do not<br>get<br>=C2=A0=C2=A0any miscounts eve=
n if they same rule that apply to the first Lost<br>=C2=A0=C2=A0packets sho=
uld<br><br>=C2=A0=C2=A0apply to the last lost ones.</p><p class=3D"MsoNorma=
l"><br>TSN 1 ----------------&gt; X<br>TSN 2 -----------------------------&=
gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;----------------------------=
- SACK 0, 2-2 =C2=A0TSN 1 peg =3D 1 =C2=A0TSN<br>3 ----------------&gt;<br>=
X =C2=A0TSN 4 -----------------------------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0&lt;----------------------------- SACK 0, 2-2, 4-4 =C2=A0TSN 1 =
peg =3D 2, TSN<br>3 peg =3D 1<br>TSN 5 ----------------&gt; X =C2=A0TSN 6 -=
----------------------------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt=
;----------------------------- SACK 0, 2-2, 4-4, 6-6 =C2=A0TSN 1 peg =3D<br=
>3, TSN 3 peg =3D<br>2, TSN 5 peg =3D 1 =C2=A0Enter FR =C2=A0exit point =3D=
 TSN 5 =C2=A0TSN<br>1 -----------------------------&gt;<br>=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0&lt;----------------------------- SACK 2, 4-4, 6-6 =C2=
=A0TSN 3 peg =3D 3, TSN<br>5 peg =3D 2<br>TSN 3 ---------------------------=
--&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;-------------------------=
---- SACK 4, 6-6 =C2=A0TSN 5 peg =3D 3 =C2=A0TSN<br>5 -------------------<b=
r>----------&gt;<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;---------------=
-------------- SACK 6 =C2=A0CA TSN &gt;=3D exit point =3D&gt; exit<br>FR =
=C2=A0TSN 7 ---<br>-------------&gt; X =C2=A0TSN 8 ----------------&gt; X<b=
r><br>At what point is the FR exit point greater than the highest =C2=A0out=
standing<br>TSN<br>in a SACK?=C2=A0 That is, at what point would pegging =
=C2=A0up to the exit point<br>include<br>more TSNs that provided in the SAC=
K?<br><br><br><br></p><p class=3D"MsoNormal">=C2=A0=C2=A0I have written thi=
s a little hastely. I hope this can give the<br>picture.<br><br>=C2=A0=C2=
=A0Perhaps with this explanation also the information in slide 30-33 of<br>=
=C2=A0=C2=A0the following now makes sense:<br><br><br>[1]<a href=3D"http://=
www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf">http://www.ietf.=
org/proceedings/90/slides/slides-90-tsvwg-16.pdf</a>,<br><br>=C2=A0=C2=A0BR=
, Karen<br><br>=C2=A0=C2=A0From: Randall Stewart [mailto:[2]<a href=3D"mail=
to:rrs@netflix.com">rrs@netflix.com</a>]<br>=C2=A0=C2=A0Sent: 23. oktober 2=
014 16:48<br>=C2=A0=C2=A0To: Karen Elisabeth Egede Nielsen<br>=C2=A0=C2=A0C=
c: Michael Tuexen; [3]<a href=3D"mailto:bidulock@openss7.org">bidulock@open=
ss7.org</a><br>=C2=A0=C2=A0Subject: Re: [tsvwg] SCTP mis indication countin=
g during Fast<br>Recovery<br><br>=C2=A0=C2=A0Karen:<br><br>=C2=A0=C2=A0Note=
 I dropped tsvwg due to the fact that this email would get locked<br>=C2=A0=
=C2=A0up and held/bounced since [4]<a href=3D"mailto:rrs@netflix.com">rrs@n=
etflix.com</a> is<br>=C2=A0=C2=A0not a subscriber to tsvwg<br><br>=C2=A0=C2=
=A0I like Brian am a bit confused by your request in that I don&#39;t see<b=
r>how<br>=C2=A0=C2=A0this could happen.<br><br>=C2=A0=C2=A0SCTP has the abi=
lity to identify 300+ sack gaps. I think this<br>=C2=A0=C2=A0is why the wor=
ding is the way it is. We could not conceive of a<br>situation<br>=C2=A0=C2=
=A0where the SACK would come back (outside of reneging) and not list<br>wha=
t<br>=C2=A0=C2=A0was previously there. Especially if the SACK is a response=
 to the<br>=C2=A0=C2=A0fast-retransmit.<br><br>=C2=A0=C2=A0In theory it *sh=
ould* contain all the gap acks that were present up<br>to<br>=C2=A0=C2=A0yo=
ur &quot;fast recovery point&quot;.<br><br>=C2=A0=C2=A0Like Brian I too don=
&#39;t remember ever making a &quot;fast recovery point&quot;<br>in<br>=C2=
=A0=C2=A0SCTP.<br><br>=C2=A0=C2=A0Now I guess you could get a situation whe=
re the fast retransmit<br>passed</p><p class=3D"MsoNormal">the<br><br></p><=
p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=C2=A0=C2=A0last TSN s=
ent and the sender is thus responding.. but thats still<br>=C2=A0=C2=A0pend=
ing data that *may* still arrive.<br><br>=C2=A0=C2=A0So unless the sender p=
urposely stops gap-acking previously gap-acked<br>=C2=A0=C2=A0packets (rene=
ged) then I don&#39;t see how this could happen.<br><br>=C2=A0=C2=A0Could y=
ou explain how you see this could happen .. it could be I am<br>=C2=A0=C2=
=A0missing something that is clear to you..<br><br>=C2=A0=C2=A0Thanks</p><p=
 class=3D"MsoNormal"><br>--<br>Brian F. G. Bidulock<br><a href=3D"mailto:bi=
dulock@openss7.org">bidulock@openss7.org</a><br><a href=3D"http://www.opens=
s7.org/">http://www.openss7.org/</a></p></div><p class=3D"MsoNormal">=C2=A0=
</p><div><div><div><div><p class=3D"MsoNormal"><span style=3D"color:black">=
--------</span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:b=
lack">Randall Stewart</span></p></div><div><p class=3D"MsoNormal"><span sty=
le=3D"color:black"><a href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></=
span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:black">803-=
317-4952</span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:b=
lack">=C2=A0</span></p></div></div><p class=3D"MsoNormal"><span style=3D"co=
lor:black">=C2=A0</span></p></div><p class=3D"MsoNormal" style=3D"margin-bo=
ttom:12.0pt">=C2=A0</p></div><p class=3D"MsoNormal">=C2=A0</p></div></div><=
/div></body></html>

--f46d0438959b57c22f05062539f2--


From nobody Thu Oct 23 23:31:34 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB671A88D2 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 GV6om84OxsmZ for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:31:32 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308F21A1B74 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:31:32 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id n3so400263wiv.3 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=OsP/z+pk2W/N6pPD6oPXKnUR68T/AqQ1urCTJkiTPpQ=; b=aI+ygvVNdzE3NCP8lBCJ/JHg1RatyFIOaMnz2cvyrYqaD4uXQ9pmxro/cBmMu20a5k jEdk9735+KH3mONRXNFBpGkbDvJNUIyVGWXcJh2cVebCbpKvbFdrnl0mquN5yfDATMfj R1REY6mFy5pg1MlVldt/UBy7wLvnV7rsrS5Fw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=OsP/z+pk2W/N6pPD6oPXKnUR68T/AqQ1urCTJkiTPpQ=; b=NXiT/KB52+zdHxujj5S59mQkwyDrgbv7QelCd6hBrrffW7TtCLIfuQgQQ7RJBgagIb 5k6z7dQytv/RSxngm7WcZyLiGw+zURrTiKqMJ0Sva4qADgKN48ypbZ/t+zGD4EOslcWc /nbPuaJ4wDsUtRmQE2KxBAQxAKFM+GKGe1c4fxX7dHuDNVrUPod7++EbPzW/K34yc2ey 3V2lbLl66gUWvqWRFTTFoo0dZUFwRc3W/6/H7MKMQWdBYhohRH++Tlm89pkdiuaDObga c9Z4C1qK8j1X0eDVlyzAdah5Mz4RiP1eUgVrm8cQSZmlk6K+emMUoEWZtiISFswiO8gK 4/LQ==
X-Gm-Message-State: ALoCoQnugpm9HGHEqnEInY7Q7oBcUfzAY19m+OIng0VtVIo5S/rH9BYps8puonmazAjHDRhPJIKju2YIvWI3Tq7kY0NifHMeCVZ4dO2mDjb2ExkCEjs2Ncg=
X-Received: by 10.180.73.19 with SMTP id h19mr1844943wiv.3.1414132290839; Thu, 23 Oct 2014 23:31:30 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com> <20141023202134.GA14016@openss7.org>
In-Reply-To: <20141023202134.GA14016@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4AtTxU80B9+M+8gKdj796APN+kL8CSsuzF5tVd6tA
Date: Fri, 24 Oct 2014 08:31:30 +0200
Message-ID: <84566e8d1fc18ade11f8a6470598efa8@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/W0khYWHujHPmTni9AVcI7JePT_o
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 06:31:33 -0000

HI,

Please see below.

> >
> > The TSN are sent at the same time, not sequentially.
> >
> > Assume they chunks are  ~0,6*MTU, then there would be no CWND
> > constrains and no HB burst constraints.
> > This I am saying just to avoid to get into such discussions or
> > bundling discussions for that matter.
> >
> > BR, Karen
>
> Did you mean like this:
>
>  TSN 1 ---> X
>  TSN 2 ---------\
>  TSN 3 --------\ \
>  TSN 4 -------\ \ \
>  TSN 5 ---> X  \ \ \
>  TSN 6 ---> X   \ \ \
>                  \ \ \-------------->
>        <----------\-\---------------- SACK 0, 2-2
>  TSN 1 peg = 1     \ \-------------->
>        <------------\---------------- SACK 0, 2-3
>  TSN 1 peg = 2       \-------------->
>        <----------------------------- SACK 0, 2-4  TSN 1 peg = 3  Enter
FR exit point =
> TSN 1  TSN 1 ----------------------------->
>        <----------------------------- SACK 4  CA TSN >= exit point =>
exit FR
>
>
[Karen] No I don't mean like this.

I mean

TSN 1 ---> X
 TSN 2 ---------\
 TSN 3 --------\ \
 TSN 4 -------\ \ \
 TSN 5 ---> X  \ \ \
 TSN 6 ---> X   \ \ \
                 \ \ \-------------->
       <----------\-\---------------- SACK 0, 2-2
 TSN 1 peg = 1     \ \-------------->
       <------------\---------------- SACK 0, 2-3
 TSN 1 peg = 2       \-------------->
       <----------------------------- SACK 0, 2-4  TSN 1 peg = 3  Enter FR
exit point = TSN 6 !!

The FR exit point is TSN6 not TSN1.

BR, Karen

> And like this:
>
>  TSN 1 ---> X
>  TSN 2 ------------\
>  TSN 3 ---> X       \
>  TSN 4 ------------\ \
>  TSN 5 ---> X       \ \
>  TSN 6 ------------\ \ \
>  TSN 7 ---> X       \ \ \
>  TSN 8 ---> X        \ \ \
>                       \ \ \-------->
>        <---------------\-\---------- SACK 0, 2-2
>  TSN 1 peg = 1          \ \-------->
>        <-----------------\---------- SACK 0, 2-2, 4-4  TSN 1 peg = 2, 3
peg = 1 \--------
> >
>        <---------------------------- SACK 0, 2-2, 4-4, 6-6  TSN 1 peg =
3, TSN 3 peg =
> 2, TSN 5 peg = 1  Enter FR  exit point = TSN 5  TSN 1
----------------------------->
>        <----------------------------- SACK 2, 4-4, 6-6  TSN 3 peg = 3,
TSN 5 peg = 2
> TSN 3 ----------------------------->
>        <----------------------------- SACK 4, 6-6  TSN 5 peg = 3  TSN 5
-------------------
> ---------->
>        <----------------------------- SACK 6  CA TSN >= exit point =>
exit FR
>
>
> The result is the same.
>
> Again, at what point is the FR exit point greater than the highest
outstanding
> TSN in a SACK?
>

> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From nobody Thu Oct 23 23:44:06 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7A31A8840 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 J8lVhJxqzNaI for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 23:44:03 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260051A1AF5 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:44:01 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id q5so433088wiv.11 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 23:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=kovDRrFfjv0H/bjJJ6sqchftv42KNPVDEEZ42JB8Ta8=; b=neeWXCWTBgHBuLhplt5wOjahwXV0JszkBAv0QBOnPeCDglwtY7zO0sE8TUlBJKpBeP 269KPrx7ZOF1ynFJzELxhPGG3JmyPNaK59yHwJG1qIfHw4ZdrS3ph1rU6npxUbH5WhpE Fl4HemDnPGJZHeosQWfjfOUbRuCMfGkNpeQuE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=kovDRrFfjv0H/bjJJ6sqchftv42KNPVDEEZ42JB8Ta8=; b=WKJqaOd1+Ki3CIf+cnaJaEzX7qhWQcsgrhUqkWpX0bCr/LXBrhGiIj95RtdzcVnunj 7rK0RiWxfHTMPpLxmb1KoOM6u8JFJhVZp28RzS/RCtZPDIqPL7PT7oOS9iknv8+aURD0 sFnaPDFTcQo54/Maq7LZsdVdHj6befryQf4bSojtFg0JkFryrWbAjQIyYyuYtM4+qubA W/0oe5MphP2g1crro6Sp2ziDPMBzZxn3pwOIkSH58DMb/uGQUZCfmlCQxIVo5Ov4el8w 2bAVO6wmXivHlzjgA2moLSEwN+heT66wfeXBpZFoi+uiL+fSVeaw0ggR7AeF2ZqwtKZt o6ew==
X-Gm-Message-State: ALoCoQk9CUZbdn3ChHBKov2Pf37BHaCLrAng+ceUlioZwf094Z5g5W2Jw/oxZyKm7PjSphuL+kGWQdbvMKAJmTXBJ7ez0YcdFpxRfLb/A8BEMi5fuYsPBZ8=
X-Received: by 10.194.161.166 with SMTP id xt6mr2621814wjb.1.1414133040303; Thu, 23 Oct 2014 23:44:00 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <20141023130716.GA6071@openss7.org>
In-Reply-To: <20141023130716.GA6071@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGF0ymmROS+cPGYY4qoHA2I9lxWVZzTAlmQ
Date: Fri, 24 Oct 2014 08:43:59 +0200
Message-ID: <6a67ad6470b49bb9c80c2a35168335d1@mail.gmail.com>
To: bidulock@openss7.org
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ca8Nt5A68trPC6F76G96DD9vfwM
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] General comments on slides-90-tsvwg-16.pdf
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 06:44:04 -0000

Hi,

Please find comment below.

BR, Karen

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
> Sent: 23. oktober 2014 15:07
> To: Karen Elisabeth Egede Nielsen
> Cc: tsvwg WG
> Subject: General comments on slides-90-tsvwg-16.pdf
>
> Karen,
>
> In your presentation,
>
>   http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf
>
> you asked for comments on tsvwg on the material presented.  Here are
> some general comments.

[Karen] Thanks  a lot for the comments. I appreciate that very much.

>
> The procedures described appear to be concerned with avoiding T3
timeouts
> in as many scenarios as possible.  Stepping back and thinking about
that, I
> wonder what can be achieved by completely eclipsing the T3 timeout
> procedure.  The procedures appear to proceed from the assumption that T3
> timeouts are evil and to be avoided at all cost.
>
> The evil appears to pivot on increased latencies in lossy network
(whether
> due to congestion or transmission errors) and not so much on congestion
> avoidance procedures (cwnd).  The statement of evil, if you will,
appears to
> be: It takes a longer time for a T3 timeout to occur than is necessary
because
> better information about loss can be available before the timeout
ensues.
>
[Karen] Yes I agree with this.
The issue is latency of course, but there are also CWND impacts of the T3
versus the FR.
However we have not qualified these yet. It is obvious that for the
situations where the unnecessary T3 occurs
there are pauses in the traffic and CWND reductions are thus not very
detrimental.

> What RTO_MIN value are you using in your experiments?  For SIGTRAN we
> have been using a RTO_MIN value of zero (0) for quite some time.

[Karen] We use RTO_MINs of 100 or 200 msecs in the experiments.
These numbers are taking from signaling network deployments at major
operator sites, including SIGTRAN.


> For example, ETSI TS 102 144 V1.1.1 (2003-05) specified the minimum
value
> for RTO.Min as 10 ms and specified with a granularity of 10 ms.

[Karen] This sounds misguided unless you have implemented means to undo
the effect of spurious T3 timeouts.
You may get away with some of the delay-ack impacts if you use immediate
SACKs
but you don't need a lot of congestion to make the RTT abruptly surge 10
msecs.
Unless you have implemented a new good RTO algorithm you then would have
problems, I think.

> (Note that the common clock tick at the time was 10ms.)  This was also
> mentioned in RFC4166/3.2.1.
>
> There are a couple of well-known procedures that can be used to mitigate
> spurious retransmissions when using a low RTO.min:
>
>  - setting SACK_DELAY to zero (0) on both sides, or not penalizing
>    a receiver for having a SACK_DELAY > RTO.
>
[Karen] Yes but such does not help with tail losses

>  - initiating an immediate HB probe for a destination when RTO
>    approaches the granularity of the system clock to quickly
>    recover a destination (especially when PMR is set to 0 or 1).
>
> An extremely high RTO.min (e.g. 1 second) will make any procedure that
> avoids a T3 timeout look good on the surface.
>
> If your implementation is capable of setting RTO.min to zero, you could
try
> rerunning your experiments with an RTO.min of zero (0) to determine
> whether falling back on T3 timeout is such a bad thing after all.
>
[Karen] Our implementation supports RFC6458 and is used in High End Telco
networks.


> --brian
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From nobody Fri Oct 24 01:11:11 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121541AD6FC for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 01:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 uO0TNQhARBBC for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 01:11:07 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92B571A88EC for <tsvwg@ietf.org>; Fri, 24 Oct 2014 01:11:07 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id n12so539545wgh.14 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 01:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=1O624g8/ZUPJL7Duqwa80C30l0XjpNun0uOkkCxD4FY=; b=urdiarvM7hI7+Ut2dc7dlz0U7nD/2dW2NtaWajxxvxqIUpZ6x5i1yyaoucGmGdc8Al m3JDuEB0CeW5WK2VZ9sLKEElL0wHEDs5htqOf3mcILZ1s4edZ+4vcrE5poyZSGFAfF6Q 4K1jxB+bN90xHY5ew0HL+DcKXIG7zaEQJAol8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=1O624g8/ZUPJL7Duqwa80C30l0XjpNun0uOkkCxD4FY=; b=RPXA0m5K5CCqM5gqHYCmIlaM66F/Mxabw/rX1XCLo0bvAr0oIKQTuuHiIRvy6YTl+A 1ptvnGfXyEoQ4k7BtHRu3KPDwr5ZqsNyWlKua5yBQ9ARUMhSQs+MCmxoB8GuQqVIrhdf W//euFlTaosaTE3B6gdgTlw8HZe1E6q054H6N2W81Sym52z8WeVbNb1/LiA/9t3iZigv QzLI+0a/swSJXwEUyaww4b3R04X50FFFx6/NEh1y5xnsylUVjXoMdqcJlE+rcoHaknKA 0ulIJLNTlCNq4/aaD/0RZEG9+d1bV3nMO/3oRTkRIHt3Mu978Q9XA+8n8KdYwuATuFV9 Ggcg==
X-Gm-Message-State: ALoCoQnGgH96LsMFLI1xNlxSuYbJ0bP5QBlEpO0o6HpDXzIwwNbKD/ZSosUZ4uLiq6PRzrVLS1oTXcEJKnWR/+iw0T2SjAQXt2L6ywM70S8DHcQIAeJzyzw=
X-Received: by 10.194.77.199 with SMTP id u7mr3138707wjw.92.1414138266235; Fri, 24 Oct 2014 01:11:06 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org>
In-Reply-To: <20141023120042.GB3853@openss7.org>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4m6rS5HA=
Date: Fri, 24 Oct 2014 10:11:05 +0200
Message-ID: <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com>
To: bidulock@openss7.org, Randall Stewart <rrs@netflix.com>
Content-Type: text/plain; charset=UTF-8
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/6BiLpCaT-pMNgooSwbZMj40akvU
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 08:11:09 -0000

Hi Brian, Randy, Michael

Michael, Randy: I dont't know if you have the time to look at the
"tiresome" questions below .. :-)

Thanks.


> > >
> > > Is there a reason would make it necessary to track the fast recovery
> > > exit point?
> > >
> > [Karen] I am not sure that I understand how to implement SCTP FR
> > without tracking the exit point.
>
> The first three sentences describe how to implement SCTP FR without
> tracking the exit point.  As I understand it, The purpose of the exit
point in
> TCP was to limit the number of packets in flight (because TCP cwnd
tracks
> bytes not packets).  Because SCTP cwnd indirectly limits packets in
flight all
> day long, the TCP FR cwnd adjustments are not necessary, thus in SCTP
> tracking the FR exit point is not necessary.
>
[Karen]

I this really true ?  (I thought this was more about inflating/deflating
and all that TCP CC business)

You would need to maintain a FR exit point to control
the CWND handling during and after FR. Also in order to know when to take
or not
take yet a CWND/2 hit (i.e., exit and re-enter of FR).

Here one may give the side note that the RFC4960 spec is not clear on the
boundary condition when FR is existed and
CWND ramp up should commerce.

TCP RCF 5681 is more clear in its formulation that:

*CWND should not be ramped up during FR
*At exit of FR, TCP is in congestion avoidance state
*The slow start algorithm is used when cwnd < ssthresh, while the
   congestion avoidance algorithm is used when cwnd > ssthresh.  When
   cwnd and ssthresh are equal, the sender may use either slow start or
   congestion avoidance.

In RFC4960 there is no clear specification of the CC operation at exit of
FR and it thus is not
clear whether the prescription to be in CA at exit of FR is assumed to be
inherited from TCP or not.

It would be interesting to know if it is meant to be left to
implementations to start in slow start or in CA after FR exit ?
(I do realize that the CC state will transfer to CA as soon as the CWND
gest ramped up).

Still there should be no question that during FR, the CWND and
partial_bytes_ack is not increased.
Correct ?

Thanks

BR, Karen


> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From nobody Fri Oct 24 04:38:33 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2481A909F; Fri, 24 Oct 2014 04:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 cAnzgdJ8Ps7D; Fri, 24 Oct 2014 04:38:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 029CD1A8993; Fri, 24 Oct 2014 04:38:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141024113826.22061.95982.idtracker@ietfa.amsl.com>
Date: Fri, 24 Oct 2014 04:38:26 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/4OoChM4xwjzn09uPXn6YFjjk100
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-failover-08.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 11:38:28 -0000

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           : Quick Failover Algorithm in SCTP
        Authors         : Yoshifumi Nishida
                          Preethi Natarajan
                          Armando Caro
                          Paul D. Amer
                          Karen E. E. Nielsen
	Filename        : draft-ietf-tsvwg-sctp-failover-08.txt
	Pages           : 18
	Date            : 2014-10-24

Abstract:
   One of the major advantages of SCTP is that it supports multi-homed
   communication.  A multi-homed SCTP end-point has the ability to
   withstand network failures by migrating the traffic from an inactive
   network to an active one.  However, if the [RFC4960] specified
   failover operation is followed there can be a significant delay in
   the migration to the active destination addresses, thus severely
   reducing the effectiveness of SCTP multi-homed operation.

   The memo complements RFC4960 by the introduction of the Potentially
   Failed state and associated new Quick Failover operation to apply
   during network failure and specifies for SCTP senders to support this
   more performance optimal failover procedure as an add-on to the
   [RFC4960] failover operation.  The memo in addition complements
   [RFC4960] by introduction of alternative switchover operation modes
   for the data transfer path management after a failover.  These
   operation modes offer for more performance optimal operation in some
   network environments.  From the perspective of this memo the
   implementation of the additional switchover operation modes is
   considered optional.

   The procedures defined require only minimal modifications to the
   current specification.  The procedures are sender-side only and do
   not impact the SCTP receiver.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-failover-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Oct 24 06:17:00 2014
Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52651A00B2 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4yjON1g49azI for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:16:47 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0D291A0069 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 06:16:46 -0700 (PDT)
Received: from qdezc2.de.t-internal.com ([10.125.181.10]) by tcmail41.telekom.de with ESMTP; 24 Oct 2014 15:16:39 +0200
X-IronPort-AV: E=Sophos;i="5.04,780,1406584800"; d="scan'208";a="155588819"
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES128-SHA; 24 Oct 2014 15:16:38 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 24 Oct 2014 15:16:38 +0200
From: <Ruediger.Geib@telekom.de>
To: <gorry@erg.abdn.ac.uk>
Date: Fri, 24 Oct 2014 15:16:37 +0200
Thread-Topic: New Version Notification for draft-geib-tsvwg-diffserv-intercon-07.txt
Thread-Index: Ac/vi3+UKIjACQ7SSbmkr1+OQ+BwOwAABNdA
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5033B6573F6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/GWh2_K3Gc8PgOMSYzESb1vIarwM
Cc: jmpolk@cisco.com, tsvwg@ietf.org
Subject: [tsvwg] WG: New Version Notification for draft-geib-tsvwg-diffserv-intercon-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 13:16:53 -0000

R29ycnkgYW5kIFRTViBXRywNCg0KZHJhZnQgZ2VpYi1kaWZmc2Vydi1pbnRlcmNvbiBzYXcgYSBt
YWpvciByZXdyaXRlLCB0aGFua3MgdG8gRGF2aWQgQmxhY2sgd2hvIGNvLWF1dGhvcmVkIHRoaXMg
dmVyc2lvbi4gSSd2ZSBkb25lIGEgbG90IG9mIGNvcHkgYW5kIHBhc3RlIHRvIGNyZWF0ZSB0aGlz
IHZlcnNpb24sIHNvcnJ5IGlmIGFueSBwYXJ0cyBhcmUgbm90IHdlbGwgZWRpdGVkLg0KDQpObyBy
ZWFsbHkgbmV3IGNvbnRlbnQsIGJldHRlciBleHBsYW5hdGlvbiBpbnN0ZWFkLiBUaGUgZHJhZnQg
bm93IGJldHRlciBleHBsYWlucyB3aGVyZSBpdCBwaWNrcyB1cCBSRkM0NTk0IGFuZCA1MTI3IGNv
bmNlcHRzIGFuZCB3aGVyZSBpdCBkaWZmZXJzLg0KDQpJJ2QgbGlrZSB0byBhc2sgZm9yIGEgc2xv
dCBpZiBUU1YgV0cgbWVldHMgaW4gSGF3YWlpLCBhbmQgSSB0aGluayBEYXZpZCB3aWxsIHByZXNl
bnQgKGRpZG4ndCBhc2sgaGltIHlldCkuIEknZCBsaWtlIHRvIGFzayB0byBhZ3JlZSBvbiB0aGUg
ZnVydGhlciBzdGVwcyB0byBiZSB0YWtlbiB0byBwcmVwYXJlIGZvciBXRyBhZG9wdGlvbi4NCg0K
UmVnYXJkcywNCg0KUnVlZGlnZXINCg0KDQoNCi0tLS0tVXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0
LS0tLS0NClZvbjogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnXSANCkdlc2VuZGV0OiBGcmVpdGFnLCAyNC4gT2t0b2JlciAyMDE0IDE1OjA3
DQpBbjogR2VpYiwgUsO8ZGlnZXI7IERhdmlkIEwuIEJsYWNrOyBEYXZpZCBMLkJsYWNrOyBHZWli
LCBSw7xkaWdlcg0KQmV0cmVmZjogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1n
ZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA3LnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2Yg
SS1ELCBkcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA3LnR4dA0KaGFzIGJlZW4g
c3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBSdWVkaWdlciBHZWliIGFuZCBwb3N0ZWQgdG8gdGhl
IElFVEYgcmVwb3NpdG9yeS4NCg0KTmFtZToJCWRyYWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50
ZXJjb24NClJldmlzaW9uOgkwNw0KVGl0bGU6CQlEaWZmU2VydiBpbnRlcmNvbm5lY3Rpb24gY2xh
c3NlcyBhbmQgcHJhY3RpY2UNCkRvY3VtZW50IGRhdGU6CTIwMTQtMTAtMjQNCkdyb3VwOgkJSW5k
aXZpZHVhbCBTdWJtaXNzaW9uDQpQYWdlczoJCTE2DQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi1pbnRl
cmNvbi0wNy50eHQNClN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLw0KSHRtbGl6ZWQ6ICAgICAg
IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50
ZXJjb24tMDcNCkRpZmY6ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJs
Mj1kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA3DQoNCkFic3RyYWN0Og0KICAg
VGhpcyBkb2N1bWVudCBwcm9wb3NlcyBhIGxpbWl0ZWQgYW5kIHdlbGwgZGVmaW5lZCBzZXQgb2Yg
RGlmZlNlcnYNCiAgIFBIQnMgYW5kIGNvZGVwb2ludHMgdG8gYmUgYXBwbGllZCBhdCAoaW50ZXIp
Y29ubmVjdGlvbnMgb2YgdHdvDQogICBzZXBhcmF0ZWx5IGFkbWluaXN0ZXJlZCBhbmQgb3BlcmF0
ZWQgbmV0d29ya3MuICBNYW55IG5ldHdvcmsNCiAgIHByb3ZpZGVycyBvcGVyYXRlIE1QTFMgdXNp
bmcgVHJlYXRtZW50IEFnZ3JlZ2F0ZXMgZm9yIHRyYWZmaWMgbWFya2VkDQogICB3aXRoIGRpZmZl
cmVudCBEaWZmU2VydiBQSEJzLCBhbmQgdXNlIE1QTFMgZm9yIGludGVyY29ubmVjdGlvbiB3aXRo
DQogICBvdGhlciBuZXR3b3Jrcy4gIFRoaXMgZG9jdW1lbnQgb2ZmZXJzIGEgc2ltcGxlIGludGVy
Y29ubmVjdGlvbg0KICAgYXBwcm9hY2ggdGhhdCBtYXkgc2ltcGxpZnkgb3BlcmF0aW9uIG9mIERp
ZmZTZXJ2IGZvciBuZXR3b3JrDQogICBpbnRlcmNvbm5lY3Rpb24gYW1vbmcgcHJvdmlkZXJzLg0K
DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkg
dGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRp
bCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmll
dGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From nobody Fri Oct 24 06:47:21 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B301A0089 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 NV1XMc4400-z for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:47:18 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55E061A0054 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 06:47:18 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9ODlGmL021176; Fri, 24 Oct 2014 07:47:16 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9ODlGcS027628; Fri, 24 Oct 2014 07:47:16 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9ODlFQM027627; Fri, 24 Oct 2014 07:47:15 -0600
Date: Fri, 24 Oct 2014 07:47:15 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141024134715.GA20929@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Randall Stewart <rrs@netflix.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg@ietf.org
References: <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com> <20141023202134.GA14016@openss7.org> <84566e8d1fc18ade11f8a6470598efa8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <84566e8d1fc18ade11f8a6470598efa8@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/J27z41hmu37C7i8A2AvN1Pa5PKI
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Fri, 24 Oct 2014 13:47:20 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:               (Fri, 24 Oct 2014 08:31:30)
> >
> >
> [Karen] No I don't mean like this.
> 
> I mean
> 
> TSN 1 ---> X
>  TSN 2 ---------\
>  TSN 3 --------\ \
>  TSN 4 -------\ \ \
>  TSN 5 ---> X  \ \ \
>  TSN 6 ---> X   \ \ \
>                  \ \ \-------------->
>        <----------\-\---------------- SACK 0, 2-2
>  TSN 1 peg = 1     \ \-------------->
>        <------------\---------------- SACK 0, 2-3
>  TSN 1 peg = 2       \-------------->
>        <----------------------------- SACK 0, 2-4  TSN 1 peg = 3  Enter FR
> exit point = TSN 6 !!
> 
> The FR exit point is TSN6 not TSN1.
> 

Ah, you misread 7.2.4:

   6)  If not in Fast Recovery, enter Fast Recovery and mark the highest
       outstanding TSN as the Fast Recovery exit point.  When a SACK
       acknowledges all TSNs up to and including this exit point, Fast
       Recovery is exited.  While in Fast Recovery, the ssthresh and
       cwnd SHOULD NOT change for any destinations due to a subsequent
       Fast Recovery event (i.e., one SHOULD NOT reduce the cwnd further
       due to a subsequent Fast Retransmit).

TSN 5 and 6 are "in-flight" and not "outstanding".  A TSN is not
"outstanding" until a T3-timeout has occurred or it has been
gap-acked as missing.  So, the correct exit point is TSN 1.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Fri Oct 24 06:49:24 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 059E01A0006 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 NJxyl-LG8QnB for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 06:49:17 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C4B31A0078 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 06:49:15 -0700 (PDT)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9ODnAOW011240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 09:49:11 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s9ODnAOW011240
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414158552; bh=1RCEA9WHP3oOSzeyGyJkXjJ3ZYo=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=AFToYSAWAvj12HX1qmjW3uNdieLHN8xRvJRLLHogpXn2qgY6U4jZ12qS+o1MaKJlF AKs54r4tBS64JUSFmeL7DjcVePTbzSu8iA1q7ofNYbBERyCmw/PK6rTTOv3+BnlScM 4NX5rnU1lhGTrLEV+nUvsvG+fKw99DxVPiCS24XI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s9ODnAOW011240
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd04.lss.emc.com (RSA Interceptor); Fri, 24 Oct 2014 09:48:37 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9ODmsgo011967 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 09:48:59 -0400
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub02.corp.emc.com (10.254.141.104) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 24 Oct 2014 09:48:08 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 09:48:07 -0400
From: "Black, David" <david.black@emc.com>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Thread-Topic: New Version Notification for draft-geib-tsvwg-diffserv-intercon-07.txt
Thread-Index: Ac/vi3+UPH6t44ajr0KAF4c8sAlwAgAABNdAAACLuVA=
Date: Fri, 24 Oct 2014 13:48:06 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936064A9E@MX104CL02.corp.emc.com>
References: <CA7A7C64CC4ADB458B74477EA99DF6F5033B6573F6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5033B6573F6@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.106]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/tuDwrHylQyJtpEGfeu_BfY8Sx_w
Cc: "jmpolk@cisco.com" <jmpolk@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-geib-tsvwg-diffserv-intercon-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 13:49:24 -0000

Q29uc2lkZXJpbmcgdGhlIGF0dGVudGlvbiBhbmQgaW50ZXJlc3QgdGhhdCB0aGlzIGRyYWZ0IGhh
cyBnZW5lcmF0ZWQsIGl0IHdpbGwgZ2V0IHRzdndnIGFnZW5kYSB0aW1lIGluIEhvbm9sdWx1LCB0
aGUgcHJpbWFyeSBwdXJwb3NlIG9mIHdoaWNoIHdpbGwgYmUgdG8gKGZpbmFsbHkpIHJlcXVlc3Qg
dHN2d2cgV0cgYWRvcHRpb24gb2YgdGhpcyBkcmFmdC4NCg0KVGhhbmtzLA0KLS1EYXZpZA0KDQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFJ1ZWRpZ2VyLkdlaWJAdGVsZWtv
bS5kZSBbbWFpbHRvOlJ1ZWRpZ2VyLkdlaWJAdGVsZWtvbS5kZV0NCj4gU2VudDogRnJpZGF5LCBP
Y3RvYmVyIDI0LCAyMDE0IDk6MTcgQU0NCj4gVG86IGdvcnJ5QGVyZy5hYmRuLmFjLnVrDQo+IENj
OiB0c3Z3Z0BpZXRmLm9yZzsgQmxhY2ssIERhdmlkOyBqbXBvbGtAY2lzY28uY29tDQo+IFN1Ympl
Y3Q6IFdHOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWdlaWItdHN2d2ctZGlm
ZnNlcnYtaW50ZXJjb24tDQo+IDA3LnR4dA0KPiANCj4gR29ycnkgYW5kIFRTViBXRywNCj4gDQo+
IGRyYWZ0IGdlaWItZGlmZnNlcnYtaW50ZXJjb24gc2F3IGEgbWFqb3IgcmV3cml0ZSwgdGhhbmtz
IHRvIERhdmlkIEJsYWNrIHdobw0KPiBjby1hdXRob3JlZCB0aGlzIHZlcnNpb24uIEkndmUgZG9u
ZSBhIGxvdCBvZiBjb3B5IGFuZCBwYXN0ZSB0byBjcmVhdGUgdGhpcw0KPiB2ZXJzaW9uLCBzb3Jy
eSBpZiBhbnkgcGFydHMgYXJlIG5vdCB3ZWxsIGVkaXRlZC4NCj4gDQo+IE5vIHJlYWxseSBuZXcg
Y29udGVudCwgYmV0dGVyIGV4cGxhbmF0aW9uIGluc3RlYWQuIFRoZSBkcmFmdCBub3cgYmV0dGVy
DQo+IGV4cGxhaW5zIHdoZXJlIGl0IHBpY2tzIHVwIFJGQzQ1OTQgYW5kIDUxMjcgY29uY2VwdHMg
YW5kIHdoZXJlIGl0IGRpZmZlcnMuDQo+IA0KPiBJJ2QgbGlrZSB0byBhc2sgZm9yIGEgc2xvdCBp
ZiBUU1YgV0cgbWVldHMgaW4gSGF3YWlpLCBhbmQgSSB0aGluayBEYXZpZCB3aWxsDQo+IHByZXNl
bnQgKGRpZG4ndCBhc2sgaGltIHlldCkuIEknZCBsaWtlIHRvIGFzayB0byBhZ3JlZSBvbiB0aGUg
ZnVydGhlciBzdGVwcyB0bw0KPiBiZSB0YWtlbiB0byBwcmVwYXJlIGZvciBXRyBhZG9wdGlvbi4N
Cj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiBSdWVkaWdlcg0KPiANCj4gDQo+IA0KPiAtLS0tLVVyc3By
w7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+IFZvbjogaW50ZXJuZXQtZHJhZnRzQGlldGYub3Jn
IFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiBHZXNlbmRldDogRnJlaXRhZywg
MjQuIE9rdG9iZXIgMjAxNCAxNTowNw0KPiBBbjogR2VpYiwgUsO8ZGlnZXI7IERhdmlkIEwuIEJs
YWNrOyBEYXZpZCBMLkJsYWNrOyBHZWliLCBSw7xkaWdlcg0KPiBCZXRyZWZmOiBOZXcgVmVyc2lv
biBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50ZXJjb24tDQo+
IDA3LnR4dA0KPiANCj4gDQo+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1nZWliLXRzdndn
LWRpZmZzZXJ2LWludGVyY29uLTA3LnR4dA0KPiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IFJ1ZWRpZ2VyIEdlaWIgYW5kIHBvc3RlZCB0byB0aGUgSUVURg0KPiByZXBvc2l0b3J5
Lg0KPiANCj4gTmFtZToJCWRyYWZ0LWdlaWItdHN2d2ctZGlmZnNlcnYtaW50ZXJjb24NCj4gUmV2
aXNpb246CTA3DQo+IFRpdGxlOgkJRGlmZlNlcnYgaW50ZXJjb25uZWN0aW9uIGNsYXNzZXMgYW5k
IHByYWN0aWNlDQo+IERvY3VtZW50IGRhdGU6CTIwMTQtMTAtMjQNCj4gR3JvdXA6CQlJbmRpdmlk
dWFsIFN1Ym1pc3Npb24NCj4gUGFnZXM6CQkxNg0KPiBVUkw6ICAgICAgICAgICAgaHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi0NCj4g
aW50ZXJjb24tMDcudHh0DQo+IFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LQ0KPiBpbnRlcmNvbi8NCj4gSHRt
bGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWdlaWItdHN2d2ct
ZGlmZnNlcnYtaW50ZXJjb24tDQo+IDA3DQo+IERpZmY6ICAgICAgICAgICBodHRwOi8vd3d3Lmll
dGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LQ0KPiBpbnRlcmNv
bi0wNw0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgIFRoaXMgZG9jdW1lbnQgcHJvcG9zZXMgYSBsaW1p
dGVkIGFuZCB3ZWxsIGRlZmluZWQgc2V0IG9mIERpZmZTZXJ2DQo+ICAgIFBIQnMgYW5kIGNvZGVw
b2ludHMgdG8gYmUgYXBwbGllZCBhdCAoaW50ZXIpY29ubmVjdGlvbnMgb2YgdHdvDQo+ICAgIHNl
cGFyYXRlbHkgYWRtaW5pc3RlcmVkIGFuZCBvcGVyYXRlZCBuZXR3b3Jrcy4gIE1hbnkgbmV0d29y
aw0KPiAgICBwcm92aWRlcnMgb3BlcmF0ZSBNUExTIHVzaW5nIFRyZWF0bWVudCBBZ2dyZWdhdGVz
IGZvciB0cmFmZmljIG1hcmtlZA0KPiAgICB3aXRoIGRpZmZlcmVudCBEaWZmU2VydiBQSEJzLCBh
bmQgdXNlIE1QTFMgZm9yIGludGVyY29ubmVjdGlvbiB3aXRoDQo+ICAgIG90aGVyIG5ldHdvcmtz
LiAgVGhpcyBkb2N1bWVudCBvZmZlcnMgYSBzaW1wbGUgaW50ZXJjb25uZWN0aW9uDQo+ICAgIGFw
cHJvYWNoIHRoYXQgbWF5IHNpbXBsaWZ5IG9wZXJhdGlvbiBvZiBEaWZmU2VydiBmb3IgbmV0d29y
aw0KPiAgICBpbnRlcmNvbm5lY3Rpb24gYW1vbmcgcHJvdmlkZXJzLg0KPiANCj4gDQo+IA0KPiAN
Cj4gUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20g
dGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQg
ZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPiANCj4gVGhlIElFVEYgU2Vj
cmV0YXJpYXQNCg0K


From nobody Fri Oct 24 10:55:43 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B321A1A8A05 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 10:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 NIcTFuFZAYum for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 10:55:36 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 375451A89A4 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 10:55:36 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9OHtYsj022224; Fri, 24 Oct 2014 11:55:34 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9OHtY9s031805; Fri, 24 Oct 2014 11:55:34 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9OHtXVQ031804; Fri, 24 Oct 2014 11:55:33 -0600
Date: Fri, 24 Oct 2014 11:55:33 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Message-ID: <20141024175533.GA31744@openss7.org>
Mail-Followup-To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Randall Stewart <rrs@netflix.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, tsvwg WG <tsvwg@ietf.org>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/xssDwVZksIu2qsCL424fIYcVfvA
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Randall Stewart <rrs@netflix.com>, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Fri, 24 Oct 2014 17:55:40 -0000

Karen,

Karen Elisabeth Egede Nielsen wrote:            (Fri, 24 Oct 2014 10:11:05)
> Hi Brian, Randy, Michael
> 
> Michael, Randy: I dont't know if you have the time to look at the
> "tiresome" questions below .. :-)
> 
> Thanks.
> 
> 
> > > >
> > > > Is there a reason would make it necessary to track the fast recovery
> > > > exit point?
> > > >
> > > [Karen] I am not sure that I understand how to implement SCTP FR
> > > without tracking the exit point.
> >
> > The first three sentences describe how to implement SCTP FR
> > without tracking the exit point.  As I understand it, The
> > purpose of the exit point in TCP was to limit the number of
> > packets in flight (because TCP cwnd tracks bytes not packets).
> > Because SCTP cwnd indirectly limits packets in flight all day
> > long, the TCP FR cwnd adjustments are not necessary, thus in
> > SCTP tracking the FR exit point is not necessary.
> >
> [Karen]
> 
> I this really true ?  (I thought this was more about
> inflating/deflating and all that TCP CC business)

Fast recovery was introduced in draft-ieft-tsvwg-sctpimpguide-08.txt
published Feb 2003 as an optional procedure to reduce the halving of
cwnd.  If you do not implement fast recovery, such as described in
the last paragraph of 7.2.4, the rest of the document (as was the
case in RFC 2960 before), you are required to half cwnd on each and
every retransmission cycle: FR or not.  So, in your LSLSLS... case,
by not implementing fast recovery, the congestion control procedures
in 7.2.3 would have be performed on each of the retransmissions of
TSN 1, TSN 3 and TSN 5.  When implementing fast recovery, you are
permitted to skip 7.2.3 on retransmission of TSN 3 and TSN 5.  Fast
recovery essentially permits you to treat loss reports for TSN 1,
TSN 3 and TSN 5 as a single loss from the standpoint of 7.2.3
congestion avoidance.  (This is also why the exit point is TSN 5
and not TSN 7 or 8.)

> You would need to maintain a FR exit point to control the CWND
> handling during and after FR. Also in order to know when to take
> or not take yet a CWND/2 hit (i.e., exit and re-enter of FR).

No, you need to maintain an FR exit point to avoid a CWND/2 hit.
By not maintaining one you take a hit on each retransmitted TSN.

> Here one may give the side note that the RFC4960 spec is not clear
> on the boundary condition when FR is existed and CWND ramp up
> should commerce.
> 
> TCP RCF 5681 is more clear in its formulation that:
> 
> *CWND should not be ramped up during FR
> *At exit of FR, TCP is in congestion avoidance state
> *The slow start algorithm is used when cwnd < ssthresh, while the
>    congestion avoidance algorithm is used when cwnd > ssthresh.  When
>    cwnd and ssthresh are equal, the sender may use either slow start or
>    congestion avoidance.
> 
> In RFC4960 there is no clear specification of the CC operation at
> exit of FR and it thus is not clear whether the prescription to be
> in CA at exit of FR is assumed to be inherited from TCP or not.
>
> It would be interesting to know if it is meant to be left to
> implementations to start in slow start or in CA after FR exit ?
> (I do realize that the CC state will transfer to CA as soon as the
> CWND gest ramped up).

Again, the only thing that fast recovery allows you to do is to not
take some 7.2.3 hits.  That is, SCTP is always in congestion
avoidance.  All of the rules for slow start still apply when in fast
recovery; however, because the ack clock is still running, slow
start should not be necessary unless a T3 timeout ruins the day.
Perhaps it should have been noted that fast recovery is exited when
a T3 timeout occurs, but I think that is obvious if not explicitly
stated somewhere.
> 
> Still there should be no question that during FR, the CWND and
> partial_bytes_ack is not increased.
> Correct ?

Maybe not: Second last paragraph of RFC 4960/7.2.4:

   Note: Before the above adjustments, if the received SACK also
   acknowledges new DATA chunks and advances the Cumulative TSN Ack
   Point, the cwnd adjustment rules defined in Section 7.2.1 and Section
   7.2.2 must be applied first.

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Fri Oct 24 12:37:49 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA951A8969 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 12:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 VayG8Svojxcu for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 12:37:45 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 755911A03A6 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 12:37:45 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id rd3so1704476pab.13 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 12:37:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8BqToCD0NT8WNOMKHye+ggDxav1+litopOT4eCYg6mI=; b=NW5k4EI3cii9Ef7gBmknEbYm9jWwrtm5yBK0STyeMRljkSPsOlik8bwIg4B8a5Vx7x q0SM7Xv2onzjn25Ph269RS5GV0x5mTtle3wzoUmmL+VSzvs721XlChsAKV5vq+ZQuC1A B9HOlbjOxFdMmqv+k8xQfyPpcMAY0vdSHvZ8HjPNDq2ekrZvFbRDpqNKHGcjCodgQ86j M7rCkzCfxww530o8js6p5jb+1aOm8+WTuIg69SOMLnANYe58rzJJVxv4a1FNf7/sh/Tb jfbZXd0kQ2lc9JMfbYtUaCwsL0WurZBRviRg9YkvURbl/QhFSTI03/Vm5jl3vji2cGVC wBpQ==
X-Received: by 10.70.63.9 with SMTP id c9mr6862117pds.104.1414179465148; Fri, 24 Oct 2014 12:37:45 -0700 (PDT)
Received: from [192.168.178.23] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id gu10sm4501752pbc.72.2014.10.24.12.37.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 12:37:44 -0700 (PDT)
Message-ID: <544AAA92.3060004@gmail.com>
Date: Sat, 25 Oct 2014 08:37:54 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tsvwg@ietf.org,  draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org,  nvo3-chairs@tools.ietf.org
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com>
In-Reply-To: <20141024191612.9331.19202.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/zopgiudfRj1HZLrdxSDcsKM1E1E
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 19:37:47 -0000

Hi,

This draft needs to be discussed in tsvwg I think. It has some significant
problems IMHO:

1. It confuses QoS and priority in a strange way.

2. It repeats the MPLS error of trying to express service differentiation
in 3 bits.

3. It makes a completely inaccurate statement about diffserv:
"The first three bits of DS field are used for IP
precedence and the last three are used as diff serv bits."

  Brian

On 25/10/2014 08:16, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Quality of Service Marking in Virtual eXtensible Local Area Network
>         Authors         : Frank Xia
>                           Behcet Sarikaya
> 	Filename        : draft-xia-nvo3-vxlan-qosmarking-00.txt
> 	Pages           : 9
> 	Date            : 2014-10-24
> 
> Abstract:
>    The Virtual eXtensible Local Area Network enables multiple tenants to
>    operate in a data center.  Each tenant needs to be assigned a
>    priority group to prioritize their traffic.  Cloud carriers wish to
>    use quality of service to differentiate different applications.  For
>    these purposes, three bits are assigned in the eXtensible Local Area
>    Network header.  How these bits are assigned and are processed in the
>    network are explained in detail.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-xia-nvo3-vxlan-qosmarking/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-xia-nvo3-vxlan-qosmarking-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Fri Oct 24 12:54:42 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9022D1A90C1; Fri, 24 Oct 2014 12:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aV_NG3fKrgiJ; Fri, 24 Oct 2014 12:54:38 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E91411A90BA; Fri, 24 Oct 2014 12:54:37 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9OJsX6g029084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 15:54:34 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s9OJsX6g029084
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414180475; bh=8RFzd57dUerKq+zqFlUZbBVN8ks=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=PkntQlXAGfDDvbCzNTQMwL1neCo2yOYOoUtbeVzt2ji7WfscbgjWuSoqMnuLgu8CS pZuaphCS0HF3mEpwpB9P5KBfPB7BmCAEW05mHZ7TkzzgLw/RDsVem7qmT2Fs2Qr0Jf MNHt4B4Y5rnkGVVWzvHmMpjY7nI9WK3SD0trVjwE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s9OJsX6g029084
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd05.lss.emc.com (RSA Interceptor); Fri, 24 Oct 2014 15:53:47 -0400
Received: from mxhub40.corp.emc.com (mxhub40.corp.emc.com [128.222.70.107]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9OJsI5b009252 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 15:54:18 -0400
Received: from MXHUB104.corp.emc.com (10.253.58.16) by mxhub40.corp.emc.com (128.222.70.107) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 24 Oct 2014 15:54:17 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB104.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 15:54:18 -0400
From: "Black, David" <david.black@emc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>, "nvo3-chairs@tools.ietf.org" <nvo3-chairs@tools.ietf.org>
Thread-Topic: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
Thread-Index: AQHP7756nCxf6IJoF0O8TWroZ6IOLZw/55MA///AWwA=
Date: Fri, 24 Oct 2014 19:54:16 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493606574D@MX104CL02.corp.emc.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AAA92.3060004@gmail.com>
In-Reply-To: <544AAA92.3060004@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.106]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/a-bvEVRAk48Af44I22lOynFnC0I
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 19:54:40 -0000

Wytudm8zIGxpc3RdDQoNCldlbGwsIGl0ZW0gMyBpcyBkZWZpbml0ZWx5IGEgbWlzdGFrZS4gIFdl
IHdlbnQgb3ZlciB0aGF0IHBvaW50IGF0IGxlbmd0aCBkdXJpbmcNCm9uZSBvZiB0aGUgdHN2d2cg
c2Vzc2lvbnMgaW4gTG9uZG9uIGluIHRoZSBjb250ZXh0IG9mIGFub3RoZXIgZHJhZnQsIHNvIGl0
J3MNCmRpc2FwcG9pbnRpbmcgdG8gc2VlIHRoYXQgbWlzdGFrZSBzaG93aW5nIHVwIGFnYWluIHNv
IHNvb24gKHNlZSBTZWN0aW9uIDMgb2YNClJGQyAyNDc0IHRvIHVuZGVyc3RhbmQgd2h5IGl0J3Mg
YSBtaXN0YWtlKS4NCg0KVGhhbmtzLA0KLS1EYXZpZCAoYXMgdHN2d2cgY28tY2hhaXIsIHdobyBu
ZWVkcyB0byBzdGFydCBhc3NlbWJsaW5nIHRoZSBIb25vbHVsdSBhZ2VuZGEpDQoNCj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogdHN2d2cgW21haWx0bzp0c3Z3Zy1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQnJpYW4gRSBDYXJwZW50ZXINCj4gU2VudDogRnJpZGF5
LCBPY3RvYmVyIDI0LCAyMDE0IDM6MzggUE0NCj4gVG86IHRzdndnQGlldGYub3JnOyBkcmFmdC14
aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nQHRvb2xzLmlldGYub3JnOyBudm8zLQ0KPiBjaGFpcnNA
dG9vbHMuaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFt0c3Z3Z10gSS1EIEFjdGlvbjogZHJhZnQt
eGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMC50eHQNCj4gDQo+IEhpLA0KPiANCj4gVGhpcyBk
cmFmdCBuZWVkcyB0byBiZSBkaXNjdXNzZWQgaW4gdHN2d2cgSSB0aGluay4gSXQgaGFzIHNvbWUg
c2lnbmlmaWNhbnQNCj4gcHJvYmxlbXMgSU1ITzoNCj4gDQo+IDEuIEl0IGNvbmZ1c2VzIFFvUyBh
bmQgcHJpb3JpdHkgaW4gYSBzdHJhbmdlIHdheS4NCj4gDQo+IDIuIEl0IHJlcGVhdHMgdGhlIE1Q
TFMgZXJyb3Igb2YgdHJ5aW5nIHRvIGV4cHJlc3Mgc2VydmljZSBkaWZmZXJlbnRpYXRpb24NCj4g
aW4gMyBiaXRzLg0KPiANCj4gMy4gSXQgbWFrZXMgYSBjb21wbGV0ZWx5IGluYWNjdXJhdGUgc3Rh
dGVtZW50IGFib3V0IGRpZmZzZXJ2Og0KPiAiVGhlIGZpcnN0IHRocmVlIGJpdHMgb2YgRFMgZmll
bGQgYXJlIHVzZWQgZm9yIElQDQo+IHByZWNlZGVuY2UgYW5kIHRoZSBsYXN0IHRocmVlIGFyZSB1
c2VkIGFzIGRpZmYgc2VydiBiaXRzLiINCj4gDQo+ICAgQnJpYW4NCj4gDQo+IE9uIDI1LzEwLzIw
MTQgMDg6MTYsIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyB3cm90ZToNCj4gPiBBIE5ldyBJbnRl
cm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMN
Cj4gZGlyZWN0b3JpZXMuDQo+ID4NCj4gPg0KPiA+ICAgICAgICAgVGl0bGUgICAgICAgICAgIDog
UXVhbGl0eSBvZiBTZXJ2aWNlIE1hcmtpbmcgaW4gVmlydHVhbCBlWHRlbnNpYmxlDQo+IExvY2Fs
IEFyZWEgTmV0d29yaw0KPiA+ICAgICAgICAgQXV0aG9ycyAgICAgICAgIDogRnJhbmsgWGlhDQo+
ID4gICAgICAgICAgICAgICAgICAgICAgICAgICBCZWhjZXQgU2FyaWtheWENCj4gPiAJRmlsZW5h
bWUgICAgICAgIDogZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMC50eHQNCj4gPiAJ
UGFnZXMgICAgICAgICAgIDogOQ0KPiA+IAlEYXRlICAgICAgICAgICAgOiAyMDE0LTEwLTI0DQo+
ID4NCj4gPiBBYnN0cmFjdDoNCj4gPiAgICBUaGUgVmlydHVhbCBlWHRlbnNpYmxlIExvY2FsIEFy
ZWEgTmV0d29yayBlbmFibGVzIG11bHRpcGxlIHRlbmFudHMgdG8NCj4gPiAgICBvcGVyYXRlIGlu
IGEgZGF0YSBjZW50ZXIuICBFYWNoIHRlbmFudCBuZWVkcyB0byBiZSBhc3NpZ25lZCBhDQo+ID4g
ICAgcHJpb3JpdHkgZ3JvdXAgdG8gcHJpb3JpdGl6ZSB0aGVpciB0cmFmZmljLiAgQ2xvdWQgY2Fy
cmllcnMgd2lzaCB0bw0KPiA+ICAgIHVzZSBxdWFsaXR5IG9mIHNlcnZpY2UgdG8gZGlmZmVyZW50
aWF0ZSBkaWZmZXJlbnQgYXBwbGljYXRpb25zLiAgRm9yDQo+ID4gICAgdGhlc2UgcHVycG9zZXMs
IHRocmVlIGJpdHMgYXJlIGFzc2lnbmVkIGluIHRoZSBlWHRlbnNpYmxlIExvY2FsIEFyZWENCj4g
PiAgICBOZXR3b3JrIGhlYWRlci4gIEhvdyB0aGVzZSBiaXRzIGFyZSBhc3NpZ25lZCBhbmQgYXJl
IHByb2Nlc3NlZCBpbiB0aGUNCj4gPiAgICBuZXR3b3JrIGFyZSBleHBsYWluZWQgaW4gZGV0YWls
Lg0KPiA+DQo+ID4NCj4gPiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhp
cyBkcmFmdCBpczoNCj4gPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC14
aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLw0KPiA+DQo+ID4gVGhlcmUncyBhbHNvIGEgaHRtbGl6
ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+ID4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMA0KPiA+DQo+ID4NCj4gPiBQbGVhc2Ug
bm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBv
ZiBzdWJtaXNzaW9uDQo+ID4gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJl
IGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gPg0KPiA+IEludGVybmV0LURyYWZ0cyBh
cmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj4gPiBmdHA6Ly9mdHAuaWV0
Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBJLUQtQW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+
ID4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCj4gPiBJbnRlcm5ldC1EcmFmdCBkaXJlY3Rvcmllczog
aHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPiA+IG9yIGZ0cDovL2Z0cC5pZXRmLm9y
Zy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+ID4NCg0K


From nobody Fri Oct 24 16:14:54 2014
Return-Path: <therbert@google.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEFC31A19E9 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 16:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 0AMnAGtOCl8m for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 16:14:39 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C60D1A1A9D for <tsvwg@ietf.org>; Fri, 24 Oct 2014 16:14:39 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id tr6so3310283ieb.32 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 16:14:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GSzxMpB5x7cu/3edh8Mpr/YKdKS2Da9rcotyF5u/pMk=; b=WJLZ9YAX51cO4TfpmrbKfYctZxbjmfS2FPwxyq9rHDU2ANqGv773ghMtgmYXDj2AYq Jj8v3xHZjwC9GP/Le3ZNZa4IEFXMhB2cN/oL0DDikS/3wNUu0T/fa/+nIkOdvq/04nC8 i8zzfA/1q4C++V0yEHn6r5lMw5imslSy28qI9vQ5AFTwL9+EJ9rm+z7U8QF8BXO2YaJz 1LWmwxJeZNMhLa/+Ek72fIedGdA4sT+W93XWr1AoWoumoM+J+xU7Ww4V/NpKzFyqGNvI nMrENqOgzocBD7kgxYgJF5XgQ2OHsuwltZ5YM/y4eKeQSMuRE+K6oXRykvLPcuBoK/2N S4QA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=GSzxMpB5x7cu/3edh8Mpr/YKdKS2Da9rcotyF5u/pMk=; b=Pp6SkYGhOwX39YKJGqc/t49KR/GvN2+tgzAdC/d6BC8FrQqlF9zIyu8P1X+HuJ8nQo kBQ9vKWf8jE09KWuShsy8VdM2ifXAtaCt38Df0mh3qab5Pxbstabd96Hq2xedcOcxPxM 2S0mNBIskENJn5rRD19toofWd5T4Jlznl6nLI1YrfRvXpMwDFKS43s9Y/tWvFHUWLop1 Jt4/L1oPpv/rzIn2xSkI5oRRBRETdZhQ7yIWwf9KMVl3aQU0os8bZ2pGAE3DMcQ9Nxl4 mOcZNvU+oFQ6WsW3AJdApVfv4Bp+I05y303N0MLN5h/xwU3GpNYhf/3bDVHtTWQ8WD0K DAMQ==
X-Gm-Message-State: ALoCoQkCSmrO/6xUgl3L/7SuhTxISj/Y6jTn3fou/FJc4wPdyx8Qzq+xhxn5qEo7ovSZZPZ3QlZD
MIME-Version: 1.0
X-Received: by 10.43.63.17 with SMTP id xc17mr4502258icb.50.1414192478480; Fri, 24 Oct 2014 16:14:38 -0700 (PDT)
Received: by 10.64.79.34 with HTTP; Fri, 24 Oct 2014 16:14:38 -0700 (PDT)
In-Reply-To: <20141024225000.16130.29795.idtracker@ietfa.amsl.com>
References: <20141024225000.16130.29795.idtracker@ietfa.amsl.com>
Date: Fri, 24 Oct 2014 16:14:38 -0700
Message-ID: <CA+mtBx9g4Fot0gP1hZnaSfxKiDsfzix0WNxJWod5ByzWkjridA@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>, tsvwg@ietf.org
Content-Type: multipart/alternative; boundary=bcaec517a94e5310ab05063358c0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/dTmHcGJ6Ve8-WqFmCYVLU6d7cUU
Subject: [tsvwg] Fwd: New Version Notification for draft-herbert-gue-02.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 23:14:43 -0000

--bcaec517a94e5310ab05063358c0
Content-Type: text/plain; charset=UTF-8

This is an update to Generic UDP Encapsulation (GUE) draft.

Major changes from version 01:
 - Added the C bit in header to indicate payload contains a control (OAM)
message
 - Clarified use of UDP checksums, more restrictive requirements for using
zero checksums
 - Clarified interaction with NAT
 - Added a section on congestion control

Comments are appreciated.

Thanks,
Tom

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Fri, Oct 24, 2014 at 3:50 PM
Subject: New Version Notification for draft-herbert-gue-02.txt
To: Tom Herbert <therbert@google.com>, Lucy Yong <lucy.yong@huawei.com>



A new version of I-D, draft-herbert-gue-02.txt
has been successfully submitted by Tom Herbert and posted to the
IETF repository.

Name:           draft-herbert-gue
Revision:       02
Title:          Generic UDP Encapsulation
Document date:  2014-10-24
Group:          Individual Submission
Pages:          22
URL:            http://www.ietf.org/internet-drafts/draft-herbert-gue-02.txt
Status:         https://datatracker.ietf.org/doc/draft-herbert-gue/
Htmlized:       http://tools.ietf.org/html/draft-herbert-gue-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-herbert-gue-02

Abstract:
   This specification describes Generic UDP Encapsulation (GUE), which
   is a scheme for using UDP to encapsulate packets of arbitrary IP
   protocols for transport across layer 3 networks. By encapsulating
   packets in UDP, specialized capabilities in networking hardware for
   efficient handling of UDP packets can be leveraged. GUE specifies
   basic encapsulation methods upon which higher level constructs, such
   tunnels and overlay networks for network virtualization, can be
   constructed. GUE is extensible by allowing optional meta data as part
   of the encapsulation, and is generic in that it can encapsulate
   packets of various IP protocols.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--bcaec517a94e5310ab05063358c0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is an update to Generic UDP Encapsulation (GUE) draft=
.<div><br></div><div>Major changes from version 01:<div>=C2=A0- Added the C=
 bit in header to indicate payload contains a control (OAM) message</div><d=
iv>=C2=A0- Clarified use of UDP checksums, more restrictive requirements fo=
r using zero checksums</div><div>=C2=A0- Clarified interaction with NAT</di=
v><div>=C2=A0- Added a section on congestion control</div><div><br></div><d=
iv>Comments are appreciated.</div><div><br></div><div>Thanks,</div><div>Tom=
</div><div><br><div class=3D"gmail_quote">---------- Forwarded message ----=
------<br>From: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;<=
/span><br>Date: Fri, Oct 24, 2014 at 3:50 PM<br>Subject: New Version Notifi=
cation for draft-herbert-gue-02.txt<br>To: Tom Herbert &lt;<a href=3D"mailt=
o:therbert@google.com">therbert@google.com</a>&gt;, Lucy Yong &lt;<a href=
=3D"mailto:lucy.yong@huawei.com">lucy.yong@huawei.com</a>&gt;<br><br><br><b=
r>
A new version of I-D, draft-herbert-gue-02.txt<br>
has been successfully submitted by Tom Herbert and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-herbert-gue<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A002<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Generic UDP Encapsulation<br>
Document date:=C2=A0 2014-10-24<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 22<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.ietf.or=
g/internet-drafts/draft-herbert-gue-02.txt" target=3D"_blank">http://www.ie=
tf.org/internet-drafts/draft-herbert-gue-02.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-herbert-gue/" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-herbert-gue/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://tools.ietf.org/html/d=
raft-herbert-gue-02" target=3D"_blank">http://tools.ietf.org/html/draft-her=
bert-gue-02</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-herbert-gue-02" target=3D"_blank">http://www.ietf.or=
g/rfcdiff?url2=3Ddraft-herbert-gue-02</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This specification describes Generic UDP Encapsulation (GUE), =
which<br>
=C2=A0 =C2=A0is a scheme for using UDP to encapsulate packets of arbitrary =
IP<br>
=C2=A0 =C2=A0protocols for transport across layer 3 networks. By encapsulat=
ing<br>
=C2=A0 =C2=A0packets in UDP, specialized capabilities in networking hardwar=
e for<br>
=C2=A0 =C2=A0efficient handling of UDP packets can be leveraged. GUE specif=
ies<br>
=C2=A0 =C2=A0basic encapsulation methods upon which higher level constructs=
, such<br>
=C2=A0 =C2=A0tunnels and overlay networks for network virtualization, can b=
e<br>
=C2=A0 =C2=A0constructed. GUE is extensible by allowing optional meta data =
as part<br>
=C2=A0 =C2=A0of the encapsulation, and is generic in that it can encapsulat=
e<br>
=C2=A0 =C2=A0packets of various IP protocols.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br></div></div></div>

--bcaec517a94e5310ab05063358c0--


From nobody Fri Oct 24 17:40:06 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F471A1B63; Fri, 24 Oct 2014 17:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 x36TgxuViOyQ; Fri, 24 Oct 2014 17:40:02 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71A761A0636; Fri, 24 Oct 2014 17:40:02 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9P0e0Gt002015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 20:40:01 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s9P0e0Gt002015
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414197601; bh=YsY6Qz7y7IH89XWzPblYazqMRZA=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=bUXzGceqBpdRqLuSbOYDNvfZQV9dFCl93hXwTTp4dcWn1prIlSqQNIKpcc0gdgzdK zYHzWc4UoBavLQOBlyIfF8dLkdrZQPBahO3x/hnVVkwdkhiaW4+rg/739a+SjM2NYe HjXVYxLN+5EvifwdpnzEZ/tMdunWHaDPMhtYP4fw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s9P0e0Gt002015
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd03.lss.emc.com (RSA Interceptor); Fri, 24 Oct 2014 20:39:34 -0400
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9P0dju4031233 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 20:39:45 -0400
Received: from MXHUB101.corp.emc.com (10.253.50.15) by mxhub36.corp.emc.com (10.254.93.84) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 24 Oct 2014 20:39:44 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB101.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 20:39:45 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Honolulu meeting planning
Thread-Index: Ac/v7BlmEcERRaUFQvGZr6T3xEEJAg==
Date: Sat, 25 Oct 2014 00:39:43 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936066198@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.106]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/eVS0wwXN20KyEdj-EKgsPEHZMdk
Cc: "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Subject: [tsvwg] Honolulu meeting planning
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Oct 2014 00:40:05 -0000

Gentle WG members,

During IETF-91, tsvwg will meet twice:

Tuesday, 1p-3p in Coral 2
	- conflicts: httpbis, dprive, softwire, dclcrg, netconf, stir, rtgarea

Thursday, 1p-3p in Coral 1
	- conflicts: dnssd, lime, netvc[cancelled], idr, saag

I'm starting to work on putting an agenda together.  The first thing that
I noticed is that there are a number of drafts that have expired. I won't
name names here to protect the guilty ;-), but if authors of an expired
draft would like meeting time in Honolulu, submitting a revised version
of the draft by the cutoff (23:59 UTC on Monday) is RECOMMENDED ;-).

The dclcrg conflict is unfortunate - any draft that raises any congestion
issues will have to be in the Thursday session.  The saag conflict seems to
be less of a problem, but any draft that expects to raise security issues=20
will need to be in the Tuesday session.

So, my initial plan is to start with the SCTP drafts on Tuesday, put
the congestion-related and QoS-related drafts on Thursday and fit
other drafts in.  So, based on what I currently know about, not including
expired drafts, here's a tentative allocation of drafts to days:

Tuesday:
- draft-ietf-tsvwg-sctp-dtls-encaps
- draft-ietf-tsvwg-sctp-failover
- draft-ietf-tsvwg-sctp-ndata
- draft-ietf-tsvwg-sctp-prpolicies

- draft-ietf-twvwg-port-use

Thursday:
- draft-ietf-tsvwg-circuit-breaker
- draft-ietf-tsvwg-gre-in-udp-encap
- [draft-ietf-tsvwg-rsvp-app-id-vv-profiles] - status update only.
- draft-ietf-tsvwg-rtcweb-qos

- draft-eggert-tsvwg-rfc5405bis [possible WG adoption]
- draft-geib-tsvwg-diffserv-intercon [possible WG adoption]
- draft-wei-tsvwg-tunnel-congestion-feedback [possible WG adoption]

-- REQUESTS -- Please send emails to the chairs at tsvwg-chairs@ietf.org.

Authors of above drafts - guesstimates on how much meeting time is needed
would be appreciated, and please let us know who the presenter will be.
If your draft doesn't need meeting time, we *definitely* want to hear
from you. ;-).

Authors of any other drafts - if you want meeting time, please send us a
request with the name of the draft, presenter and time requested.

NOTE: Please be aware that the chairs generally want to see demonstrated
list interest in a new draft before allocating meeting time.  If time
permits, a few minutes to present a slide or two towards generating list
interest in a new draft may be available.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Fri Oct 24 17:54:02 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D021A1B39 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 17:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 f9JeZJVkGkB9 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 17:53:56 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDC1B1A1AE1 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 17:53:55 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id hz1so2053145pad.36 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 17:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8BqToCD0NT8WNOMKHye+ggDxav1+litopOT4eCYg6mI=; b=MuifHojD8BYPfTopurxHLwgXoCvVn5aych/AqxtnVaCsYXHyeeNl1K8sbR7jDvFrUC UZxA7PCzppppa4e6qNanqTWwkF46LyNRBFChxddYcyalryxe48qetHs862Ikn6irvZm9 XKYOOTjwiBA7/20JaprbOws1tcWHAcCnfC4HUJ7B4itEbPOlyVYxC997wWjFt2PMl8dr Csq45QgA8CnEBWsMC/yGTBSBGhFVniyFdZkmpedOAaUuvfTlNXseBlBZnPiMqBo73brk 4/d2HQFAaxr7V6rKBQCAYaKFThI5T8H5mhEp3aEuaBEsc9aPJM3ErlTUJBnCLiv0aBnp tMXA==
X-Received: by 10.70.42.15 with SMTP id j15mr8188547pdl.17.1414198435575; Fri, 24 Oct 2014 17:53:55 -0700 (PDT)
Received: from [192.168.178.23] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id o5sm4867682pdc.24.2014.10.24.17.53.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 17:53:54 -0700 (PDT)
Message-ID: <544AF4AD.50503@gmail.com>
Date: Sat, 25 Oct 2014 13:54:05 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tsvwg@ietf.org,  draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org,  nvo3-chairs@tools.ietf.org
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com>
In-Reply-To: <20141024191612.9331.19202.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/5NGtWr_-0XR5AALwt_UOf9QQr4U
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Oct 2014 00:53:58 -0000

Hi,

This draft needs to be discussed in tsvwg I think. It has some significant
problems IMHO:

1. It confuses QoS and priority in a strange way.

2. It repeats the MPLS error of trying to express service differentiation
in 3 bits.

3. It makes a completely inaccurate statement about diffserv:
"The first three bits of DS field are used for IP
precedence and the last three are used as diff serv bits."

  Brian

On 25/10/2014 08:16, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Quality of Service Marking in Virtual eXtensible Local Area Network
>         Authors         : Frank Xia
>                           Behcet Sarikaya
> 	Filename        : draft-xia-nvo3-vxlan-qosmarking-00.txt
> 	Pages           : 9
> 	Date            : 2014-10-24
> 
> Abstract:
>    The Virtual eXtensible Local Area Network enables multiple tenants to
>    operate in a data center.  Each tenant needs to be assigned a
>    priority group to prioritize their traffic.  Cloud carriers wish to
>    use quality of service to differentiate different applications.  For
>    these purposes, three bits are assigned in the eXtensible Local Area
>    Network header.  How these bits are assigned and are processed in the
>    network are explained in detail.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-xia-nvo3-vxlan-qosmarking/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-xia-nvo3-vxlan-qosmarking-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Fri Oct 24 20:54:20 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 821AC1A1AD6; Fri, 24 Oct 2014 20:54:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 H9yS0z1kFPY2; Fri, 24 Oct 2014 20:54:15 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E63731A1A5F; Fri, 24 Oct 2014 20:54:14 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kx10so2215480pab.6 for <multiple recipients>; Fri, 24 Oct 2014 20:54:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CFsof2q1tKHqkbNGetokNMFpFePinVMYpaSqoNx+FwY=; b=M9L8Pi2MYOGFc2jhGyMVXsbhJApufuxGTGhB2RvHGXHdPbDSxawJXrKJ+Bsv8AL8ti nb7oFFb/JRYaoSvgRol30bljr1tOhrlkmgCuicL27tZOqgO46yrIWbJr0ZAOPn+kwKxl LtF4zwGxdJl1uG2RyMwUKvZagpq/8wLjCTrFR3801YW73CFlSRIKSjG4UP6Jv83Dv4UR B2m6HtJ71YFrnPDD7g5sKusD/9GAESfCXUhMzYgxbe2HkXBmvvcCJzy26fw4UEX9THzo wlIY1wIr3EPiUgVCzC2EpdKRDrl91JoSEg1A5e9blPa0eYWJsijbN4rrI/ZhVilO+cQh XYpw==
X-Received: by 10.66.160.193 with SMTP id xm1mr8708846pab.115.1414209254520; Fri, 24 Oct 2014 20:54:14 -0700 (PDT)
Received: from [192.168.178.23] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id yw3sm5036667pbc.88.2014.10.24.20.54.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 20:54:13 -0700 (PDT)
Message-ID: <544B1EEF.7040002@gmail.com>
Date: Sat, 25 Oct 2014 16:54:23 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Xiayangsong <xiayangsong@huawei.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AF4AD.50503@gmail.com> <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com>
In-Reply-To: <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/grb9pNp6pe6XC2R4LRljyoaNP84
Cc: "nvo3-chairs@tools.ietf.org" <nvo3-chairs@tools.ietf.org>, nvo3@ietf.org, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Oct 2014 03:54:17 -0000

Hi,

On 25/10/2014 14:37, Xiayangsong wrote:
> Hi Brian
>=20
> Thanks for your attention on this topic. I am an engineer not
> a standard  guy . I discussed this idea with Behcet who
> kindly put me as the first author.
>=20
> So I try to respond you from engineering perspective.

Understood, but IETF standards are supposed to correspond to
real engineering, so that is no problem.

>=20
> Thanks Frank
>=20
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6----- =E5=8F=91=E4=BB=B6=E4=BA=
=BA: Brian E Carpenter
> [mailto:brian.e.carpenter@gmail.com] =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=
: 2014=E5=B9=B410=E6=9C=8825=E6=97=A5 8:54 =E6=94=B6
> =E4=BB=B6=E4=BA=BA: tsvwg@ietf.org;
> draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org;
> nvo3-chairs@tools.ietf.org =E4=B8=BB=E9=A2=98: Re: I-D Action:
> draft-xia-nvo3-vxlan-qosmarking-00.txt
>=20
> Hi,
>=20
> This draft needs to be discussed in tsvwg I think. It has
> some significant problems IMHO:
>=20
> 1. It confuses QoS and priority in a strange way.=20

> Frank=3D>QoS
> is about packet loss, bandwidth, latency and jitter.

Those are the usual QoS metrics of course.

> Bandwidth can be controller by CAR technology. As for latency
> and jitter, they are kind of inherent parameter of a given
> network, and there is hardly a way to controller them .
> Thus, in most scenario, QoS is about packet loss control
> which is  based on priority.

I suggest carefully reviewing RFC 2474 and RFC 2475, and the
specific descriptions of per-hop behaviours in RFC 2597 and RFC
3246. Also it is worth reviewing RFC 4594,
draft-geib-tsvwg-diffserv-intercon, and the work of the AQM WG
(http://datatracker.ietf.org/wg/aqm/charter/). Truly there is a
lot more to queue management than simple priority.

> 2. It repeats the MPLS error of trying to express service
> differentiation in 3 bits.=20


> Frank=3D>I don't know the MPLS
> error, please teach me.  However, in engineering area, MPLS 3
> bit has a pragmatic purpose.  You can check switches/routers
> specification from different vendors about this.

The problem is that re-using the three EXP (experimental) bits
in MPLS for quality of service signalling was an afterthought.
Three bits simply isn't enough to express a reasonable range of
service classes. Unfortunately it is all we have in MPLS, but
that is not a valid reason for copying the same mistake. If you
adopt 6 bits, it should be fairly easy to adopt the whole
diffserv model. That would save a lot of work, both in
specification and in implementation.

>=20
> 3. It makes a completely inaccurate statement about diffserv:
>  "The first three bits of DS field are used for IP precedence
> and the last three are used as diff serv bits."=20


> Frank=3D>I
> guess the statement was copied from some RFC, and I would
> double check it.

If so, that RFC is wrong. It is true that in some cases, the
recommended diffserv code points were chosen to have the same
bit pattern as the old ToS precedence bits. This was done so
that if packets marked with diffserv code points happened to
pass through a legacy router that supported the ToS bits, the
results would be reasonable. However, diffserv code points are
in fact defined as opaque 6-bit values. The above references
should make this clear.

In summary my suggestion is
1) use 6 bits
2) state that they are to be interpreted exactly like the DSCP
defined in RFC 2474
3) this simplifies the question of mapping between the vxlan
header and the IP header, when needed.
4) it would also simplify interworking with the QoS model for
WebRTC that is under development.

Regards
    Brian

>=20
> Brian
>=20
> On 25/10/2014 08:16, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line
>> Internet-Drafts directories.
>>=20
>>=20
>> Title           : Quality of Service Marking in Virtual
>> eXtensible Local Area Network Authors         : Frank Xia=20
>> Behcet Sarikaya Filename        :
>> draft-xia-nvo3-vxlan-qosmarking-00.txt Pages           : 9=20
>> Date            : 2014-10-24
>>=20
>> Abstract: The Virtual eXtensible Local Area Network enables
>> multiple tenants to operate in a data center.  Each tenant
>> needs to be assigned a priority group to prioritize their
>> traffic.  Cloud carriers wish to use quality of service to
>> differentiate different applications.  For these purposes,
>> three bits are assigned in the eXtensible Local Area=20
>> Network header.  How these bits are assigned and are
>> processed in the network are explained in detail.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:=20
>> https://datatracker.ietf.org/doc/draft-xia-nvo3-vxlan-qosmarking/
>>=20
>>=20
>> There's also a htmlized version available at:=20
>> http://tools.ietf.org/html/draft-xia-nvo3-vxlan-qosmarking-00
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the
>> time of submission until the htmlized version and diff are
>> available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:=20
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________=20
>> I-D-Announce mailing list I-D-Announce@ietf.org=20
>> https://www.ietf.org/mailman/listinfo/i-d-announce=20
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>=20
>=20


From nobody Sun Oct 26 09:44:17 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B251A016D for <tsvwg@ietfa.amsl.com>; Sun, 26 Oct 2014 09:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 7sA3toxEIGNf for <tsvwg@ietfa.amsl.com>; Sun, 26 Oct 2014 09:44:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E96AC1A017C for <tsvwg@ietf.org>; Sun, 26 Oct 2014 09:44:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141026164409.1285.17577.idtracker@ietfa.amsl.com>
Date: Sun, 26 Oct 2014 09:44:09 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/5RoTVsZzooi0R8ceQaTeq8LA4yE
Subject: [tsvwg] Milestones changed for tsvwg WG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 26 Oct 2014 16:44:15 -0000

Changed milestone "Submit 'Encoding and Transport of (Pre-) Congestion
Information from the Domain Egress to the Ingress' to the IESG for
consideration as an Experimental RFC", resolved as "Done".

URL: http://datatracker.ietf.org/wg/tsvwg/charter/


From nobody Sun Oct 26 11:41:28 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB5121A0365; Sun, 26 Oct 2014 11:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 R71g1bFBHVuS; Sun, 26 Oct 2014 11:41:22 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 847671A0019; Sun, 26 Oct 2014 11:41:22 -0700 (PDT)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9QIfCGM031719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Oct 2014 14:41:13 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s9QIfCGM031719
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414348873; bh=LGSlGApwRgXJ7QGOyKqwCDblVtI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=AKdGhpMrVYNgKKzYsohaRF0HE9YVNjD3UlNZxfyzwsFISRWd01LaUp/PRxh+PHBqc ILEXzGtPoW4DigiCzbcvM44eHgRouoI4DLdYRBhyP1MI875LOgnyQa53E82xBPgWwz Ibc+wmaWJ4CE//GbCMbzKUp7DmV1caIgPvPHATws=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s9QIfCGM031719
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd56.lss.emc.com (RSA Interceptor); Sun, 26 Oct 2014 14:40:28 -0400
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9QIewIN009397 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Oct 2014 14:40:59 -0400
Received: from MXHUB106.corp.emc.com (10.253.58.23) by mxhub10.corp.emc.com (10.254.92.105) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sun, 26 Oct 2014 14:40:58 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB106.corp.emc.com ([10.253.58.23]) with mapi id 14.03.0195.001; Sun, 26 Oct 2014 14:40:58 -0400
From: "Black, David" <david.black@emc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Xiayangsong <xiayangsong@huawei.com>
Thread-Topic: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
Thread-Index: AQHP7756nCxf6IJoF0O8TWroZ6IOLZxAP+qA///vW5OAAoJbAA==
Date: Sun, 26 Oct 2014 18:40:57 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936066F2C@MX104CL02.corp.emc.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AF4AD.50503@gmail.com> <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com> <544B1EEF.7040002@gmail.com>
In-Reply-To: <544B1EEF.7040002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.101]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/PBMEG8BaN4v058hjn0irJiZ2Du4
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 26 Oct 2014 18:41:25 -0000

PiBJIHN1Z2dlc3QgY2FyZWZ1bGx5IHJldmlld2luZyBSRkMgMjQ3NCBhbmQgUkZDIDI0NzUsIGFu
ZCB0aGUNCj4gc3BlY2lmaWMgZGVzY3JpcHRpb25zIG9mIHBlci1ob3AgYmVoYXZpb3VycyBpbiBS
RkMgMjU5NyBhbmQgUkZDDQo+IDMyNDYuIEFsc28gaXQgaXMgd29ydGggcmV2aWV3aW5nIFJGQyA0
NTk0LA0KPiBkcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLCBhbmQgdGhlIHdvcmsg
b2YgdGhlIEFRTSBXRw0KPiAoaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL3dnL2FxbS9jaGFy
dGVyLykuIFRydWx5IHRoZXJlIGlzIGENCj4gbG90IG1vcmUgdG8gcXVldWUgbWFuYWdlbWVudCB0
aGFuIHNpbXBsZSBwcmlvcml0eS4NCg0KVG8gYmUgbW9yZSBzcGVjaWZpYywgc2VjdGlvbiA0IG9m
IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmcNCmFwcGVhcnMgdG8gYmUgaGVhZGVkIHRv
d2FyZHMgcmVpbnZlbnRpbmcgUkZDIDQ1OTQsIHNvIEkgc3Ryb25nbHkNCnN1Z2dlc3QgcmV2aWV3
aW5nIHRoYXQgUkZDLiAgSW4gYWRkaXRpb24gdG8gdGhlIGRvY3VtZW50cyBCcmlhbg0KbGlzdGVk
LCB0aGVyZSdzIGFsc28gc29tZSBzaG9ydGVyIGRpZmZzZXJ2IGJhY2tncm91bmQgaW5mb3JtYXRp
b24NCmluIGRyYWZ0LWlldGYtZGFydC1kc2NwLXJ0cCB0aGF0IG1heSBiZSBoZWxwZnVsLg0KDQpJ
ZiBiaXQgY29uc2VydmF0aW9uIGlzIHJlYWxseSBpbXBvcnRhbnQsIEkgcmVjb21tZW5kIHJldmll
d2luZw0KUkZDIDUxMjcgaW4gYWRkaXRpb24gdG8gZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi1p
bnRlcmNvbi4NCg0KSXQgaXMgdW5mb3J0dW5hdGUgdGhhdCBkcmFmdC14aWEtbnZvMy12eGxhbi1x
b3NtYXJraW5nIG5vcm1hdGl2ZWx5DQpyZWZlcmVuY2VzIFJGQyAyNDc0LCBidXQgYXBwZWFycyB0
byBlZmZlY3RpdmVseSBpZ25vcmUgdGhhdCBSRkMuDQoNClRoYW5rcywNCi0tRGF2aWQNCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiB0c3Z3ZyBbbWFpbHRvOnRzdndnLWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBCcmlhbiBFIENhcnBlbnRlcg0KPiBTZW50OiBG
cmlkYXksIE9jdG9iZXIgMjQsIDIwMTQgMTE6NTQgUE0NCj4gVG86IFhpYXlhbmdzb25nDQo+IENj
OiBudm8zLWNoYWlyc0B0b29scy5pZXRmLm9yZzsgbnZvM0BpZXRmLm9yZzsgdHN2d2dAaWV0Zi5v
cmc7IGRyYWZ0LXhpYS1udm8zLQ0KPiB2eGxhbi1xb3NtYXJraW5nQHRvb2xzLmlldGYub3JnDQo+
IFN1YmplY3Q6IFJlOiBbdHN2d2ddIEktRCBBY3Rpb246IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFv
c21hcmtpbmctMDAudHh0DQo+IA0KPiBIaSwNCj4gDQo+IE9uIDI1LzEwLzIwMTQgMTQ6MzcsIFhp
YXlhbmdzb25nIHdyb3RlOg0KPiA+IEhpIEJyaWFuDQo+ID4NCj4gPiBUaGFua3MgZm9yIHlvdXIg
YXR0ZW50aW9uIG9uIHRoaXMgdG9waWMuIEkgYW0gYW4gZW5naW5lZXIgbm90DQo+ID4gYSBzdGFu
ZGFyZCAgZ3V5IC4gSSBkaXNjdXNzZWQgdGhpcyBpZGVhIHdpdGggQmVoY2V0IHdobw0KPiA+IGtp
bmRseSBwdXQgbWUgYXMgdGhlIGZpcnN0IGF1dGhvci4NCj4gPg0KPiA+IFNvIEkgdHJ5IHRvIHJl
c3BvbmQgeW91IGZyb20gZW5naW5lZXJpbmcgcGVyc3BlY3RpdmUuDQo+IA0KPiBVbmRlcnN0b29k
LCBidXQgSUVURiBzdGFuZGFyZHMgYXJlIHN1cHBvc2VkIHRvIGNvcnJlc3BvbmQgdG8NCj4gcmVh
bCBlbmdpbmVlcmluZywgc28gdGhhdCBpcyBubyBwcm9ibGVtLg0KPiANCj4gPg0KPiA+IFRoYW5r
cyBGcmFuaw0KPiA+DQo+ID4gLS0tLS3pgq7ku7bljp/ku7YtLS0tLSDlj5Hku7bkuro6IEJyaWFu
IEUgQ2FycGVudGVyDQo+ID4gW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dIOWP
kemAgeaXtumXtDogMjAxNOW5tDEw5pyIMjXml6UgODo1NCDmlLYNCj4gPiDku7bkuro6IHRzdndn
QGlldGYub3JnOw0KPiA+IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmdAdG9vbHMuaWV0
Zi5vcmc7DQo+ID4gbnZvMy1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcg5Li76aKYOiBSZTogSS1EIEFj
dGlvbjoNCj4gPiBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwLnR4dA0KPiA+DQo+
ID4gSGksDQo+ID4NCj4gPiBUaGlzIGRyYWZ0IG5lZWRzIHRvIGJlIGRpc2N1c3NlZCBpbiB0c3Z3
ZyBJIHRoaW5rLiBJdCBoYXMNCj4gPiBzb21lIHNpZ25pZmljYW50IHByb2JsZW1zIElNSE86DQo+
ID4NCj4gPiAxLiBJdCBjb25mdXNlcyBRb1MgYW5kIHByaW9yaXR5IGluIGEgc3RyYW5nZSB3YXku
DQo+IA0KPiA+IEZyYW5rPT5Rb1MNCj4gPiBpcyBhYm91dCBwYWNrZXQgbG9zcywgYmFuZHdpZHRo
LCBsYXRlbmN5IGFuZCBqaXR0ZXIuDQo+IA0KPiBUaG9zZSBhcmUgdGhlIHVzdWFsIFFvUyBtZXRy
aWNzIG9mIGNvdXJzZS4NCj4gDQo+ID4gQmFuZHdpZHRoIGNhbiBiZSBjb250cm9sbGVyIGJ5IENB
UiB0ZWNobm9sb2d5LiBBcyBmb3IgbGF0ZW5jeQ0KPiA+IGFuZCBqaXR0ZXIsIHRoZXkgYXJlIGtp
bmQgb2YgaW5oZXJlbnQgcGFyYW1ldGVyIG9mIGEgZ2l2ZW4NCj4gPiBuZXR3b3JrLCBhbmQgdGhl
cmUgaXMgaGFyZGx5IGEgd2F5IHRvIGNvbnRyb2xsZXIgdGhlbSAuDQo+ID4gVGh1cywgaW4gbW9z
dCBzY2VuYXJpbywgUW9TIGlzIGFib3V0IHBhY2tldCBsb3NzIGNvbnRyb2wNCj4gPiB3aGljaCBp
cyAgYmFzZWQgb24gcHJpb3JpdHkuDQo+IA0KPiBJIHN1Z2dlc3QgY2FyZWZ1bGx5IHJldmlld2lu
ZyBSRkMgMjQ3NCBhbmQgUkZDIDI0NzUsIGFuZCB0aGUNCj4gc3BlY2lmaWMgZGVzY3JpcHRpb25z
IG9mIHBlci1ob3AgYmVoYXZpb3VycyBpbiBSRkMgMjU5NyBhbmQgUkZDDQo+IDMyNDYuIEFsc28g
aXQgaXMgd29ydGggcmV2aWV3aW5nIFJGQyA0NTk0LA0KPiBkcmFmdC1nZWliLXRzdndnLWRpZmZz
ZXJ2LWludGVyY29uLCBhbmQgdGhlIHdvcmsgb2YgdGhlIEFRTSBXRw0KPiAoaHR0cDovL2RhdGF0
cmFja2VyLmlldGYub3JnL3dnL2FxbS9jaGFydGVyLykuIFRydWx5IHRoZXJlIGlzIGENCj4gbG90
IG1vcmUgdG8gcXVldWUgbWFuYWdlbWVudCB0aGFuIHNpbXBsZSBwcmlvcml0eS4NCj4gDQo+ID4g
Mi4gSXQgcmVwZWF0cyB0aGUgTVBMUyBlcnJvciBvZiB0cnlpbmcgdG8gZXhwcmVzcyBzZXJ2aWNl
DQo+ID4gZGlmZmVyZW50aWF0aW9uIGluIDMgYml0cy4NCj4gDQo+IA0KPiA+IEZyYW5rPT5JIGRv
bid0IGtub3cgdGhlIE1QTFMNCj4gPiBlcnJvciwgcGxlYXNlIHRlYWNoIG1lLiAgSG93ZXZlciwg
aW4gZW5naW5lZXJpbmcgYXJlYSwgTVBMUyAzDQo+ID4gYml0IGhhcyBhIHByYWdtYXRpYyBwdXJw
b3NlLiAgWW91IGNhbiBjaGVjayBzd2l0Y2hlcy9yb3V0ZXJzDQo+ID4gc3BlY2lmaWNhdGlvbiBm
cm9tIGRpZmZlcmVudCB2ZW5kb3JzIGFib3V0IHRoaXMuDQo+IA0KPiBUaGUgcHJvYmxlbSBpcyB0
aGF0IHJlLXVzaW5nIHRoZSB0aHJlZSBFWFAgKGV4cGVyaW1lbnRhbCkgYml0cw0KPiBpbiBNUExT
IGZvciBxdWFsaXR5IG9mIHNlcnZpY2Ugc2lnbmFsbGluZyB3YXMgYW4gYWZ0ZXJ0aG91Z2h0Lg0K
PiBUaHJlZSBiaXRzIHNpbXBseSBpc24ndCBlbm91Z2ggdG8gZXhwcmVzcyBhIHJlYXNvbmFibGUg
cmFuZ2Ugb2YNCj4gc2VydmljZSBjbGFzc2VzLiBVbmZvcnR1bmF0ZWx5IGl0IGlzIGFsbCB3ZSBo
YXZlIGluIE1QTFMsIGJ1dA0KPiB0aGF0IGlzIG5vdCBhIHZhbGlkIHJlYXNvbiBmb3IgY29weWlu
ZyB0aGUgc2FtZSBtaXN0YWtlLiBJZiB5b3UNCj4gYWRvcHQgNiBiaXRzLCBpdCBzaG91bGQgYmUg
ZmFpcmx5IGVhc3kgdG8gYWRvcHQgdGhlIHdob2xlDQo+IGRpZmZzZXJ2IG1vZGVsLiBUaGF0IHdv
dWxkIHNhdmUgYSBsb3Qgb2Ygd29yaywgYm90aCBpbg0KPiBzcGVjaWZpY2F0aW9uIGFuZCBpbiBp
bXBsZW1lbnRhdGlvbi4NCj4gDQo+ID4NCj4gPiAzLiBJdCBtYWtlcyBhIGNvbXBsZXRlbHkgaW5h
Y2N1cmF0ZSBzdGF0ZW1lbnQgYWJvdXQgZGlmZnNlcnY6DQo+ID4gICJUaGUgZmlyc3QgdGhyZWUg
Yml0cyBvZiBEUyBmaWVsZCBhcmUgdXNlZCBmb3IgSVAgcHJlY2VkZW5jZQ0KPiA+IGFuZCB0aGUg
bGFzdCB0aHJlZSBhcmUgdXNlZCBhcyBkaWZmIHNlcnYgYml0cy4iDQo+IA0KPiANCj4gPiBGcmFu
az0+SQ0KPiA+IGd1ZXNzIHRoZSBzdGF0ZW1lbnQgd2FzIGNvcGllZCBmcm9tIHNvbWUgUkZDLCBh
bmQgSSB3b3VsZA0KPiA+IGRvdWJsZSBjaGVjayBpdC4NCj4gDQo+IElmIHNvLCB0aGF0IFJGQyBp
cyB3cm9uZy4gSXQgaXMgdHJ1ZSB0aGF0IGluIHNvbWUgY2FzZXMsIHRoZQ0KPiByZWNvbW1lbmRl
ZCBkaWZmc2VydiBjb2RlIHBvaW50cyB3ZXJlIGNob3NlbiB0byBoYXZlIHRoZSBzYW1lDQo+IGJp
dCBwYXR0ZXJuIGFzIHRoZSBvbGQgVG9TIHByZWNlZGVuY2UgYml0cy4gVGhpcyB3YXMgZG9uZSBz
bw0KPiB0aGF0IGlmIHBhY2tldHMgbWFya2VkIHdpdGggZGlmZnNlcnYgY29kZSBwb2ludHMgaGFw
cGVuZWQgdG8NCj4gcGFzcyB0aHJvdWdoIGEgbGVnYWN5IHJvdXRlciB0aGF0IHN1cHBvcnRlZCB0
aGUgVG9TIGJpdHMsIHRoZQ0KPiByZXN1bHRzIHdvdWxkIGJlIHJlYXNvbmFibGUuIEhvd2V2ZXIs
IGRpZmZzZXJ2IGNvZGUgcG9pbnRzIGFyZQ0KPiBpbiBmYWN0IGRlZmluZWQgYXMgb3BhcXVlIDYt
Yml0IHZhbHVlcy4gVGhlIGFib3ZlIHJlZmVyZW5jZXMNCj4gc2hvdWxkIG1ha2UgdGhpcyBjbGVh
ci4NCj4gDQo+IEluIHN1bW1hcnkgbXkgc3VnZ2VzdGlvbiBpcw0KPiAxKSB1c2UgNiBiaXRzDQo+
IDIpIHN0YXRlIHRoYXQgdGhleSBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgZXhhY3RseSBsaWtlIHRo
ZSBEU0NQDQo+IGRlZmluZWQgaW4gUkZDIDI0NzQNCj4gMykgdGhpcyBzaW1wbGlmaWVzIHRoZSBx
dWVzdGlvbiBvZiBtYXBwaW5nIGJldHdlZW4gdGhlIHZ4bGFuDQo+IGhlYWRlciBhbmQgdGhlIElQ
IGhlYWRlciwgd2hlbiBuZWVkZWQuDQo+IDQpIGl0IHdvdWxkIGFsc28gc2ltcGxpZnkgaW50ZXJ3
b3JraW5nIHdpdGggdGhlIFFvUyBtb2RlbCBmb3INCj4gV2ViUlRDIHRoYXQgaXMgdW5kZXIgZGV2
ZWxvcG1lbnQuDQo+IA0KPiBSZWdhcmRzDQo+ICAgICBCcmlhbg0KPiANCj4gPg0KPiA+IEJyaWFu
DQo+ID4NCj4gPiBPbiAyNS8xMC8yMDE0IDA4OjE2LCBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcg
d3JvdGU6DQo+ID4+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBv
bi1saW5lDQo+ID4+IEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCj4gPj4NCj4gPj4NCj4g
Pj4gVGl0bGUgICAgICAgICAgIDogUXVhbGl0eSBvZiBTZXJ2aWNlIE1hcmtpbmcgaW4gVmlydHVh
bA0KPiA+PiBlWHRlbnNpYmxlIExvY2FsIEFyZWEgTmV0d29yayBBdXRob3JzICAgICAgICAgOiBG
cmFuayBYaWENCj4gPj4gQmVoY2V0IFNhcmlrYXlhIEZpbGVuYW1lICAgICAgICA6DQo+ID4+IGRy
YWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmctMDAudHh0IFBhZ2VzICAgICAgICAgICA6IDkN
Cj4gPj4gRGF0ZSAgICAgICAgICAgIDogMjAxNC0xMC0yNA0KPiA+Pg0KPiA+PiBBYnN0cmFjdDog
VGhlIFZpcnR1YWwgZVh0ZW5zaWJsZSBMb2NhbCBBcmVhIE5ldHdvcmsgZW5hYmxlcw0KPiA+PiBt
dWx0aXBsZSB0ZW5hbnRzIHRvIG9wZXJhdGUgaW4gYSBkYXRhIGNlbnRlci4gIEVhY2ggdGVuYW50
DQo+ID4+IG5lZWRzIHRvIGJlIGFzc2lnbmVkIGEgcHJpb3JpdHkgZ3JvdXAgdG8gcHJpb3JpdGl6
ZSB0aGVpcg0KPiA+PiB0cmFmZmljLiAgQ2xvdWQgY2FycmllcnMgd2lzaCB0byB1c2UgcXVhbGl0
eSBvZiBzZXJ2aWNlIHRvDQo+ID4+IGRpZmZlcmVudGlhdGUgZGlmZmVyZW50IGFwcGxpY2F0aW9u
cy4gIEZvciB0aGVzZSBwdXJwb3NlcywNCj4gPj4gdGhyZWUgYml0cyBhcmUgYXNzaWduZWQgaW4g
dGhlIGVYdGVuc2libGUgTG9jYWwgQXJlYQ0KPiA+PiBOZXR3b3JrIGhlYWRlci4gIEhvdyB0aGVz
ZSBiaXRzIGFyZSBhc3NpZ25lZCBhbmQgYXJlDQo+ID4+IHByb2Nlc3NlZCBpbiB0aGUgbmV0d29y
ayBhcmUgZXhwbGFpbmVkIGluIGRldGFpbC4NCj4gPj4NCj4gPj4NCj4gPj4gVGhlIElFVEYgZGF0
YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQo+ID4+IGh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmcvDQo+
ID4+DQo+ID4+DQo+ID4+IFRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZhaWxhYmxl
IGF0Og0KPiA+PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14aWEtbnZvMy12eGxh
bi1xb3NtYXJraW5nLTAwDQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IFBsZWFzZSBub3RlIHRoYXQg
aXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZQ0KPiA+PiB0aW1lIG9mIHN1
Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlDQo+ID4+IGF2
YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gPj4NCj4gPj4gSW50ZXJuZXQtRHJhZnRzIGFy
ZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPiA+PiBmdHA6Ly9mdHAuaWV0
Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiBJLUQtQW5ub3VuY2UgbWFpbGluZyBsaXN0
IEktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0KPiA+PiBJbnRlcm5ldC1EcmFmdCBkaXJlY3Rvcmllczog
aHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KPiA+PiBvciBmdHA6Ly9mdHAuaWV0Zi5v
cmcvaWV0Zi8xc2hhZG93LXNpdGVzLnR4dA0KPiA+Pg0KPiA+DQoNCg==


From nobody Mon Oct 27 02:13:28 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D358A1A1BFF for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.521
X-Spam-Level: 
X-Spam-Status: No, score=0.521 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 RFG-3jmSWyEF for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:13:22 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9A611A6F24 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 02:13:21 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id h11so3722011wiw.0 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 02:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=e+JjZAVcAjYaW2uqXdBlz+Kh5Bq2TWgBHYOjDU91cjk=; b=hScU2y/9gywBw8TYihOQo2mHdfjzQgxzvGUH2XpiZwiknxyNQ7reSrL5NV9lYqgdK0 sqdoIVEBJMJnsfkvToasgl+/5qdubJlaf1wc7LxG2IT06ZC88IoKC34iCvucfaILWMIP KobZ5WGPujVOvdbMK3039EfZ28E4vIpFARd0M=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=e+JjZAVcAjYaW2uqXdBlz+Kh5Bq2TWgBHYOjDU91cjk=; b=D0EwSWRsLMOMQh3Fgp9TGEETZSsgIF9/+dgLel0Aa9YjYW7DkwN1d+Tf0l6+nRKH8t M/c0c87hsJi8piR0zwS3jzLvVtC1WyFDj3qfVAUMPg1OIJlg8T06BNMXW+3Ugel2rURT WB1Z3I1bBCEiv+s8qo0uC5ILo+TgPRpPATyRj/av9QsGhsi8WpTKMw7S6wQriJMi+1X0 FPdzpQqWunAouhSOhHaKvizKfDzXMIQbrep0TBdxUEEuz6qZvVJiKGYXYT30fE8ifWn4 yARFDsegkf4b1kSc4lTCO60T05oOEMCSa8m5py4SQ+QxbeMhqUqJbQLfGl1lPZq+X4bh BRBQ==
X-Gm-Message-State: ALoCoQmnJdhg9J1uEenD42vY+dvTuPjQYAmNyIxnwZqVFXcUlyqTBC6FJsXp5N7mjgHQL+w/EqAD7iJLyA2C6aybZQ+snFsHXuUaGpeF5w2gIJcb2r8B+fk=
X-Received: by 10.180.211.70 with SMTP id na6mr19232153wic.3.1414401200353; Mon, 27 Oct 2014 02:13:20 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com> <4E31BB93-2CC7-4CE5-9A90-B2927954C8B8@netflix.com>
In-Reply-To: <4E31BB93-2CC7-4CE5-9A90-B2927954C8B8@netflix.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4AixiGQECfz15CpuKRSRA
Date: Mon, 27 Oct 2014 10:13:19 +0100
Message-ID: <0be1ae396dc792c28a9dadd35b645fbc@mail.gmail.com>
To: Randall Stewart <rrs@netflix.com>
Content-Type: multipart/alternative; boundary=001a11c261dc1e1025050663f1ff
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/1GyT_lUfWIFrRDz49l9MS1jiJ6g
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 09:13:28 -0000

--001a11c261dc1e1025050663f1ff
Content-Type: text/plain; charset=UTF-8

Hi Randy,



Thanks.



What are your thoughts on the following:



In RFC4960 there is no clear specification of the CC operation at exit of
FR and it thus is not
clear whether the prescription to be in CA at exit of FR is assumed to be
inherited from TCP or not.

It would be interesting to know if it is meant to be left to
implementations to start in slow start or in CA after FR exit ?

-          ??

P.S.: Our (Ericsson) SCTP goes to slow start and then to CA after exit  of
FR. But this is not what TCP (RFC%681) says on the other hand it

is a tiny (tiny!) step towards CubicJ



BR, Karen



*From:* Randall Stewart [mailto:rrs@netflix.com]
*Sent:* 24. oktober 2014 20:27
*To:* Karen Elisabeth Egede Nielsen
*Cc:* bidulock@openss7.org; Michael Tuexen; tsvwg WG
*Subject:* Re: [tsvwg] SCTP mis indication counting during Fast Recovery





On Oct 24, 2014, at 1:11 AM, Karen Elisabeth Egede Nielsen <
karen.nielsen@tieto.com> wrote:



Hi Brian, Randy, Michael

Michael, Randy: I dont't know if you have the time to look at the
"tiresome" questions below .. :-)

Thanks.




Is there a reason would make it necessary to track the fast recovery
exit point?

[Karen] I am not sure that I understand how to implement SCTP FR
without tracking the exit point.


The first three sentences describe how to implement SCTP FR without
tracking the exit point.  As I understand it, The purpose of the exit

point in

TCP was to limit the number of packets in flight (because TCP cwnd

tracks

bytes not packets).  Because SCTP cwnd indirectly limits packets in

flight all

day long, the TCP FR cwnd adjustments are not necessary, thus in SCTP
tracking the FR exit point is not necessary.

[Karen]

I this really true ?  (I thought this was more about inflating/deflating
and all that TCP CC business)

You would need to maintain a FR exit point to control
the CWND handling during and after FR. Also in order to know when to take
or not
take yet a CWND/2 hit (i.e., exit and re-enter of FR).

Here one may give the side note that the RFC4960 spec is not clear on the
boundary condition when FR is existed and
CWND ramp up should commerce.

TCP RCF 5681 is more clear in its formulation that:

*CWND should not be ramped up during FR
*At exit of FR, TCP is in congestion avoidance state
*The slow start algorithm is used when cwnd < ssthresh, while the
  congestion avoidance algorithm is used when cwnd > ssthresh.  When
  cwnd and ssthresh are equal, the sender may use either slow start or
  congestion avoidance.

In RFC4960 there is no clear specification of the CC operation at exit of
FR and it thus is not
clear whether the prescription to be in CA at exit of FR is assumed to be
inherited from TCP or not.

It would be interesting to know if it is meant to be left to
implementations to start in slow start or in CA after FR exit ?
(I do realize that the CC state will transfer to CA as soon as the CWND
gest ramped up).

Still there should be no question that during FR, the CWND and
partial_bytes_ack is not increased.
Correct ?



Right



While you are recovering a FastRetransmit.. your not going to increase PBA
or the CWND..



R




Thanks

BR, Karen



--
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/



--------

Randall Stewart

rrs@netflix.com

803-317-4952

--001a11c261dc1e1025050663f1ff
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1152722389;
	mso-list-type:hybrid;
	mso-list-template-ids:1216877266 -1227967460 67502083 67502085 67502081 67=
502083 67502085 67502081 67502083 67502085;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style></head><body lang=3D"DA" link=3D"blue" vlink=3D"purple"><div cla=
ss=3D"WordSection1"><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"fo=
nt-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color=
:#1f497d">Hi Randy,</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"E=
N-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">Thanks.</span></p><p class=3D"MsoNormal"><span l=
ang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal">=
<span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">What are your thoughts on the fol=
lowing:</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">In RFC=
4960 there is no clear specification of the CC operation at exit of<br>FR a=
nd it thus is not<br>clear whether the prescription to be in CA at exit of =
FR is assumed to be<br>inherited from TCP or not.<br><br>It would be intere=
sting to know if it is meant to be left to<br>implementations to start in s=
low start or in CA after FR exit ?<br><br></span><span lang=3D"EN-US" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d"></span></p><p class=3D"MsoListParagraph" style><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d"><span style>-<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 </span></span></span><span lang=3D"EN-US" style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">??</s=
pan></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.=
S.: Our (Ericsson) SCTP goes to slow start and then to CA after exit=C2=A0 =
of FR. But this is not what TCP (RFC%681) says on the other hand it</span><=
/p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">is a ti=
ny (tiny!) step towards Cubic</span><span lang=3D"EN-US" style=3D"font-size=
:11.0pt;font-family:Wingdings;color:#1f497d">J</span><span lang=3D"EN-US" s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d"></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"=
EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1f497d">BR, Karen</span></p><p class=3D"MsoNormal"><spa=
n lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></p><div style=3D"border=
:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div sty=
le=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"=
><p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&q=
uot;sans-serif&quot;"> Randall Stewart [mailto:<a href=3D"mailto:rrs@netfli=
x.com">rrs@netflix.com</a>] <br><b>Sent:</b> 24. oktober 2014 20:27<br><b>T=
o:</b> Karen Elisabeth Egede Nielsen<br><b>Cc:</b> <a href=3D"mailto:bidulo=
ck@openss7.org">bidulock@openss7.org</a>; Michael Tuexen; tsvwg WG<br><b>Su=
bject:</b> Re: [tsvwg] SCTP mis indication counting during Fast Recovery</s=
pan></p></div></div><p class=3D"MsoNormal">=C2=A0</p><p class=3D"MsoNormal"=
>=C2=A0</p><div><div><p class=3D"MsoNormal">On Oct 24, 2014, at 1:11 AM, Ka=
ren Elisabeth Egede Nielsen &lt;<a href=3D"mailto:karen.nielsen@tieto.com">=
karen.nielsen@tieto.com</a>&gt; wrote:</p></div><p class=3D"MsoNormal"><br>=
<br></p><p class=3D"MsoNormal">Hi Brian, Randy, Michael<br><br>Michael, Ran=
dy: I dont&#39;t know if you have the time to look at the<br>&quot;tiresome=
&quot; questions below .. :-)<br><br>Thanks.<br><br><br><br></p><blockquote=
 style=3D"margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style=3D"margin=
-top:5.0pt;margin-bottom:5.0pt"><p class=3D"MsoNormal" style=3D"margin-bott=
om:12.0pt"><br>Is there a reason would make it necessary to track the fast =
recovery<br>exit point?</p></blockquote><p class=3D"MsoNormal">[Karen] I am=
 not sure that I understand how to implement SCTP FR<br>without tracking th=
e exit point.</p></blockquote><p class=3D"MsoNormal"><br>The first three se=
ntences describe how to implement SCTP FR without<br>tracking the exit poin=
t.=C2=A0 As I understand it, The purpose of the exit</p><p class=3D"MsoNorm=
al">point in<br><br></p><p class=3D"MsoNormal">TCP was to limit the number =
of packets in flight (because TCP cwnd</p><p class=3D"MsoNormal">tracks<br>=
<br></p><p class=3D"MsoNormal">bytes not packets).=C2=A0 Because SCTP cwnd =
indirectly limits packets in</p><p class=3D"MsoNormal">flight all<br><br></=
p><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">day long, the TCP F=
R cwnd adjustments are not necessary, thus in SCTP<br>tracking the FR exit =
point is not necessary.</p><p class=3D"MsoNormal">[Karen]<br><br>I this rea=
lly true ? =C2=A0(I thought this was more about inflating/deflating<br>and =
all that TCP CC business)<br><br>You would need to maintain a FR exit point=
 to control<br>the CWND handling during and after FR. Also in order to know=
 when to take<br>or not<br>take yet a CWND/2 hit (i.e., exit and re-enter o=
f FR).<br><br>Here one may give the side note that the RFC4960 spec is not =
clear on the<br>boundary condition when FR is existed and<br>CWND ramp up s=
hould commerce.<br><br>TCP RCF 5681 is more clear in its formulation that:<=
br><br>*CWND should not be ramped up during FR<br>*At exit of FR, TCP is in=
 congestion avoidance state<br>*The slow start algorithm is used when cwnd =
&lt; ssthresh, while the<br>=C2=A0=C2=A0congestion avoidance algorithm is u=
sed when cwnd &gt; ssthresh.=C2=A0 When<br>=C2=A0=C2=A0cwnd and ssthresh ar=
e equal, the sender may use either slow start or<br>=C2=A0=C2=A0congestion =
avoidance.<br><br>In RFC4960 there is no clear specification of the CC oper=
ation at exit of<br>FR and it thus is not<br>clear whether the prescription=
 to be in CA at exit of FR is assumed to be<br>inherited from TCP or not.<b=
r><br>It would be interesting to know if it is meant to be left to<br>imple=
mentations to start in slow start or in CA after FR exit ?<br>(I do realize=
 that the CC state will transfer to CA as soon as the CWND<br>gest ramped u=
p).<br><br>Still there should be no question that during FR, the CWND and<b=
r>partial_bytes_ack is not increased.<br>Correct ?</p><div><p class=3D"MsoN=
ormal">=C2=A0</p></div><div><p class=3D"MsoNormal">Right</p></div><div><p c=
lass=3D"MsoNormal">=C2=A0</p></div><div><p class=3D"MsoNormal">While you ar=
e recovering a FastRetransmit.. your not going to increase PBA or the CWND.=
.</p></div><div><p class=3D"MsoNormal">=C2=A0</p></div><div><p class=3D"Mso=
Normal">R</p></div><p class=3D"MsoNormal"><br><br></p><p class=3D"MsoNormal=
"><br>Thanks<br><br>BR, Karen<br><br><br><br></p><p class=3D"MsoNormal">--<=
br>Brian F. G. Bidulock<br><a href=3D"mailto:bidulock@openss7.org">bidulock=
@openss7.org</a><br><a href=3D"http://www.openss7.org/">http://www.openss7.=
org/</a></p></div><p class=3D"MsoNormal">=C2=A0</p><div><div><div><div><p c=
lass=3D"MsoNormal"><span style=3D"color:black">--------</span></p></div><di=
v><p class=3D"MsoNormal"><span style=3D"color:black">Randall Stewart</span>=
</p></div><div><p class=3D"MsoNormal"><span style=3D"color:black"><a href=
=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></span></p></div><div><p cla=
ss=3D"MsoNormal"><span style=3D"color:black">803-317-4952</span></p></div><=
div><p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0</span></p></d=
iv></div><p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0</span></=
p></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=C2=A0</p></d=
iv><p class=3D"MsoNormal">=C2=A0</p></div></div></body></html>

--001a11c261dc1e1025050663f1ff--


From nobody Mon Oct 27 02:37:02 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09EF41A6F7D for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level: 
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 irz9Dp3FT0ru for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:36:53 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86ED31A8A63 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 02:36:39 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s9R9aWeR012522 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 10:36:33 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
Date: Mon, 27 Oct 2014 10:36:38 +0100
Message-ID: <00d601cff1c9$81b99f20$852cdd60$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D7_01CFF1D1.E37EF180"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/sQAadrHnivnU8T9+D26MTd/fZ3w==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/OTkA5FGZ6BeuEInBzgvtEgUzEWk
Subject: [tsvwg] An implementation of TCM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 09:36:57 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D7_01CFF1D1.E37EF180
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
We have just finished an implementation of TCM.
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
=20
The implementation is simple, but it works. Its name is =93Simplemux=94. =
It runs
in Linux. It is programmed in C, and makes use of TUN/TAP. It is here:
http://diec.unizar.es/~jsaldana/personal/simplemux_current_version.zip
=20
It is able to:
=20
- compress headers with ROHC (using this implementation:
<https://rohc-lib.org/> https://rohc-lib.org/)=20
- multiplex a number of packets using separators (something similar to
PPPMux)
- the tunnel is na=EFve at this stage: just an IP/UDP header using port =
55555
=20
- It implements four different policies for selecting which packets will =
be
multiplexed together: period, timeout, number of packets and packet size
limit.
=20
=20
The plan is to perform some tests with real traffic. We will report the
results in this list. If someone else is interested on collaborating =
and/or
doing some tests, do not hesitate to contact me.
=20
Best regards,
=20
Jose Saldana

------=_NextPart_000_00D7_01CFF1D1.E37EF180
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CFF1D1.E0C353F0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Arial","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Texto sin formato";
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>Hi =
all,<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>We </span><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>have just finished an =
implementation of TCM.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The implementation is simple, but it =
works. Its name is &#8220;<span class=3DSpellE>Simplemux</span>&#8221;. =
It runs in Linux. It is programmed in C, and makes use of TUN/TAP. It is =
here: <a =
href=3D"http://diec.unizar.es/~jsaldana/personal/simplemux_current_versio=
n.zip">http://diec.unizar.es/~jsaldana/personal/simplemux_current_version=
.zip</a><o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>It is able to:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- compress headers with ROHC (using =
this implementation: </span><a href=3D"https://rohc-lib.org/"><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>https://rohc-lib.org/</span></a><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>) =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- multiplex a number of packets using =
separators (something similar to PPPMux)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- the tunnel is na=EFve at this stage: =
just an IP/UDP header using port 55555<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- It implements four different =
policies for selecting which packets will be multiplexed together: =
period, timeout, number of packets and packet size =
limit.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The plan is to perform some tests with =
real traffic. We will report the results in this list. If someone else =
is interested on collaborating and/or doing some tests, do not hesitate =
to contact me.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Best regards,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ES;mso-no-proof:yes=
'>Jose Saldana<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_00D7_01CFF1D1.E37EF180--


From nobody Mon Oct 27 02:42:41 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC1771A8BB3 for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.521
X-Spam-Level: 
X-Spam-Status: No, score=0.521 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 OQzY4iCJrvH8 for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 02:42:36 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 156931A8BBE for <tsvwg@ietf.org>; Mon, 27 Oct 2014 02:42:35 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id ex7so5846100wid.10 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 02:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type; bh=oy2nSm8EUJ7SELKZDGl/0lbhLmT1bGosS3+mAsfibgQ=; b=Rrcy9/KEVRDceku4jU/QZIpquqQf+N352qbNCX3BhHYfCTRHq0PabJGS7DuyZr3GuH SyOlUeJKBFpN9aWg0blKdFui5HSwfl2tOKOPfpomop96VjG8F5o1pEokZU3dKKGwt3vf 3FegqlO3B+IF5Nak4YbMAtB2WXq7bPkJ8AJLs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=oy2nSm8EUJ7SELKZDGl/0lbhLmT1bGosS3+mAsfibgQ=; b=XTvqeYVh43DRAHUysrYvNJz7dPgT+jc47VzR/phgArRAFTzKD4vwVRF4GZM8hmalY+ 0WCAgsESXfTdVwYWsC/zzKCQuRJZ/KB7tOLW+ko6p19zAOsQY4wPuIWkpOPdKsQXox3L gTszliQviarNBnPoAnXcwC2zh20KR+4WoquamszCDQjEjz3WwTYwGCbOMSUIxgQ89iix 4NR6QkWkbkkj89dG170mp23ZtxOX0kPVhtZUYflv2m0NXAnq6axgXmoYnAaNhyFji9Zn fe9afuQ1srf8tBXrBYbnjkeq3j5igRQT5ngmI2VdjfD4BJpcc3bbQlv6J6Gaz0znJJYi cKjA==
X-Gm-Message-State: ALoCoQkohaA3TZ3AgppSyMw2MLMKRESCeKxqqoB3UrWRll3SJaT1COtiJht+sYs9lHA8MIP36LORJ/LXtvqNwXfpRGlwGWUXDeLCiMzey3SHF1L46Ytj5as=
X-Received: by 10.180.205.162 with SMTP id lh2mr19360240wic.14.1414402954678;  Mon, 27 Oct 2014 02:42:34 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com> <5B3BC2A5-E440-49B1-AB7D-BBD47CB7F88D@netflix.com> <050f1d7b98045826842e732c21379e4c@mail.gmail.com> <4EB53C4C-5EEF-4D2E-85F5-677DF2B78FF2@netflix.com>
In-Reply-To: <4EB53C4C-5EEF-4D2E-85F5-677DF2B78FF2@netflix.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/kzLjIfDZz68zfdPp/l/C+KpunQIN9EVSAWgpW/MA+vwszgInP2d4AtTxU80B9+M+8gKdj796APN+kL8BmLf/NgLKcBDxAblpm5ybO9GF0A==
Date: Mon, 27 Oct 2014 10:42:33 +0100
Message-ID: <5ca01eb23ed65de7a13c278935206a4a@mail.gmail.com>
To: Randall Stewart <rrs@netflix.com>
Content-Type: multipart/alternative; boundary=001a11c37d28aef03a050664591b
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/2014v8qLw92_9qj8DAJcgm-HtmA
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 09:42:38 -0000

--001a11c37d28aef03a050664591b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

*Hi Randy,*



*Thanks a lot for the willingness to continue this discussion !!*

*Please see below.*





*From:* Randall Stewart [mailto:rrs@netflix.com]
*Sent:* 24. oktober 2014 20:24
*To:* Karen Elisabeth Egede Nielsen
*Cc:* bidulock@openss7.org; Michael Tuexen
*Subject:* Re: [tsvwg] SCTP mis indication counting during Fast Recovery



Karen:



I think the reason is because you only *know* the receivers perspective

based on the SACK.

*[Karen] This I think is the case for Highest Newly Ack=E2=80=99ed part of =
the
algorithm.*



*But this part*



(#) If an endpoint is in Fast

   Recovery and a SACK arrives that advances the Cumulative TSN Ack

   Point, the miss indications are incremented for all TSNs reported

   missing in the SACK.



*which is NOT stipulating new SACK information, necessarily addresses the
senders perspective of having retransmitted the TSN now newly cumulatively
Ack=E2=80=99ed.*

*The motivation for the increase of the mis indication count of the
non-SACK=E2=80=99ed TSNs up  until the highest=E2=80=99es SACK indeed is th=
at this TSN,
i.e., the newly cum Ack=E2=80=99ed TSN, have been sent and received after t=
he
non-SACK=E2=80=99ed TSNs up  until the highest SACK.*



*This must be the only reasonable way to interpret this sentence given we
already have the Highest Newly Ack=E2=80=99ed algorithm. *



*Correct ?*



Sure you may have sent two tailing TSN=E2=80=99s in a packet

at the same time (your case I think) as you sent the other packets.. <or>
you may

have *just* sent the trailing two TSN=E2=80=99s..

*[Karen] Yes you MAY just have sent them. Still you send them before
entering FR (!) *



*(My assumption is for increase of mis indication count only up to and
including FR Exit point).*



you don=E2=80=99t know if the receiver has had time

to get them or not..

*[Karen] Well at least you have retransmitted a lost TSN which now gets
cumack=E2=80=99ed,*

*and this retransmitted TSN was sent after the trailing TSNs.*

*This is the same argument used for the non-SACK=E2=80=99ed TSNs up  until =
the
highest=E2=80=99es SACK*



The idea is that I can only base my incrementing of the gap=E2=80=99s based=
 on what
is in the SACK.. not

based on what I sent.

*[Karen] Then you should not have the prescription (#) in the first place.
Should you ?*



*Either way one is looking at an Errata =E2=80=93 or where did I go wrong ?=
*



*BR, Karen*



R

On Oct 23, 2014, at 11:23 PM, Karen Elisabeth Egede Nielsen <
karen.nielsen@tieto.com> wrote:



discussion as closed, we/I will get what we/I want from RFC6675 additions
to SCTP.



However, getting these arguments from you, then out of curiosity, I wonder
if you have the time and

the strength to explain the motivation for the existing text of RFC4960
saying:



If an endpoint is in Fast Recovery and a SACK

arrives that advances



--------

Randall Stewart

rrs@netflix.com

803-317-4952

--001a11c37d28aef03a050664591b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dus-ascii"><meta name=3D"Generator" content=3D"Microsoft Word 14 (filtere=
d medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3D"DA" link=3D"blue" vlink=3D"purple"><div cla=
ss=3D"WordSection1"><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d">Hi Randy,</span></i></b></p><p class=3D"MsoNormal"><b><i><s=
pan lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></i></b></p><p class=
=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks a lot=
 for the willingness to continue this discussion !!</span></i></b></p><p cl=
ass=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Please se=
e below.</span></i></b></p><p class=3D"MsoNormal"><span lang=3D"EN-US" styl=
e=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:#1f497d">=C2=A0</span></p><p class=3D"MsoNormal"><span lang=3D"EN-U=
S" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">=C2=A0</span></p><div style=3D"border:none;border-l=
eft:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style=3D"border:n=
one;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"M=
soNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US=
" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;"> Randall Stewart [mailto:<a href=3D"mailto:rrs@netflix.com">rrs@net=
flix.com</a>] <br><b>Sent:</b> 24. oktober 2014 20:24<br><b>To:</b> Karen E=
lisabeth Egede Nielsen<br><b>Cc:</b> <a href=3D"mailto:bidulock@openss7.org=
">bidulock@openss7.org</a>; Michael Tuexen<br><b>Subject:</b> Re: [tsvwg] S=
CTP mis indication counting during Fast Recovery</span></p></div></div><p c=
lass=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p><p class=3D"MsoNor=
mal">Karen:</p><div><p class=3D"MsoNormal">=C2=A0</p></div><div><p class=3D=
"MsoNormal">I think the reason is because you only *know* the receivers per=
spective</p></div><div><p class=3D"MsoNormal">based on the SACK. <span styl=
e=3D"color:#1f497d"></span></p><p class=3D"MsoNormal"><b><i><span lang=3D"E=
N-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">[Karen] This I think is the case for Highest New=
ly Ack=E2=80=99ed part of the algorithm.</span></i></b></p><p class=3D"MsoN=
ormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></i></b=
></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:1=
1.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"=
>But this part</span></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D=
"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:#1f497d">=C2=A0</span></i></b></p><p class=3D"MsoPlainT=
ext"><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">(#)=
 If an endpoint is in Fast</span></p><p class=3D"MsoPlainText"><span lang=
=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">=C2=A0=C2=A0 Recov=
ery and a SACK arrives that advances the Cumulative TSN Ack</span></p><p cl=
ass=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-family:&quot;Courie=
r New&quot;">=C2=A0=C2=A0 Point, the miss indications are incremented for a=
ll TSNs reported</span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" s=
tyle=3D"font-family:&quot;Courier New&quot;">=C2=A0=C2=A0 missing in the SA=
CK.</span></p><p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-=
family:&quot;Courier New&quot;">=C2=A0</span></p><p class=3D"MsoNormal"><b>=
<i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1f497d">which is NOT stipulating new S=
ACK information, necessarily addresses the senders perspective of having re=
transmitted the TSN now newly cumulatively Ack=E2=80=99ed.</span></i></b></=
p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Th=
e motivation for the increase of the mis indication count of the non-SACK=
=E2=80=99ed TSNs up =C2=A0until the highest=E2=80=99es SACK indeed is that =
this TSN, i.e., the newly cum Ack=E2=80=99ed TSN, have been sent and receiv=
ed after the non-SACK=E2=80=99ed TSNs up =C2=A0until the highest SACK.</spa=
n></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"fo=
nt-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color=
:#1f497d">=C2=A0</span></i></b></p><p class=3D"MsoNormal"><b><i><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">This must be the only reasonable way to int=
erpret this sentence given we already have the Highest Newly Ack=E2=80=99ed=
 algorithm. </span></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"E=
N-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">=C2=A0</span></i></b></p><p class=3D"MsoNormal">=
<b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d">Correct ?</span></i></b></p=
><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=
=A0</span></i></b></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Sure you =
may have sent two tailing TSN=E2=80=99s in a packet=C2=A0</span></p></div><=
div><p class=3D"MsoNormal">at the same time (your case I think) as you sent=
 the other packets.. &lt;or&gt; you may</p></div><div><p class=3D"MsoNormal=
">have *just* sent the trailing two TSN=E2=80=99s..<span style=3D"color:#1f=
497d"></span></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">[Karen] Yes you MAY just have sent them. Still you send them b=
efore entering FR (!) </span></i></b></p><p class=3D"MsoNormal"><b><i><span=
 lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></i></b></p><p class=3D"M=
soNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">(My assumption is=
 for increase of mis indication count only up to and including FR Exit poin=
t).</span></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:#1f497d">=C2=A0</span></i></b></p><p class=3D"MsoNormal"><span lan=
g=3D"EN-US"> you don=E2=80=99t know if the receiver has had time</span></p>=
</div><div><p class=3D"MsoNormal">to get them or not..</p><p class=3D"MsoNo=
rmal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Karen] Well at least=
 you have retransmitted a lost TSN which now gets cumack=E2=80=99ed,</span>=
</i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1f497d">and this retransmitted TSN was sent after the trailing TSNs.</span>=
</i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1f497d">This is the same argument used for the non-SACK=E2=80=99ed TSNs up =
=C2=A0until the highest=E2=80=99es SACK</span></i></b><span lang=3D"EN-US" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;;color:#1f497d"></span></p></div><div><p class=3D"MsoNormal"><span lan=
g=3D"EN-US">=C2=A0</span></p></div><div><p class=3D"MsoNormal">The idea is =
that I can only base my incrementing of the gap=E2=80=99s based on what is =
in the SACK.. not</p></div><div><p class=3D"MsoNormal">based on what I sent=
.</p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:1=
1.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"=
>[Karen] Then you should not have the prescription (#) in the first place. =
Should you ?</span></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"E=
N-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">=C2=A0</span></i></b></p><p class=3D"MsoNormal">=
<b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d">Either way one is looking a=
t an Errata =E2=80=93 or where did I go wrong ?</span></i></b></p><p class=
=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span=
></i></b></p><p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"fon=
t-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
#1f497d">BR, Karen</span></i></b></p></div><div><p class=3D"MsoNormal"><b><=
i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span></i></b></p></div>=
<div><p class=3D"MsoNormal"><span lang=3D"EN-US">R</span></p><div><div><p c=
lass=3D"MsoNormal"><span lang=3D"EN-US">On Oct 23, 2014, at 11:23 PM, Karen=
 Elisabeth Egede Nielsen &lt;</span><a href=3D"mailto:karen.nielsen@tieto.c=
om">karen.nielsen@tieto.com</a>&gt; wrote:</p></div><p class=3D"MsoNormal">=
<br><br></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
f497d">discussion as closed, we/I will get what we/I want from RFC6675 addi=
tions to SCTP.</span></p></div><p class=3D"MsoNormal" style=3D"text-align:s=
tart;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an></p><div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d=
">However, getting these arguments from you, then out of curiosity, I wonde=
r if you have the time and</span></p></div><div><p class=3D"MsoNormal"><spa=
n lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:#1f497d">the strength to explain the motivatio=
n for the existing text of RFC4960 saying:</span></p></div><p class=3D"MsoN=
ormal" style=3D"text-align:start;word-spacing:0px"><span lang=3D"EN-US" sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:#1f497d">=C2=A0</span></p><div><p class=3D"MsoNormal"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;">If an endpoint is in Fast Recovery and a SACK</span></p><=
/div><div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11=
.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">arrives that a=
dvances</span></p></div></div><p class=3D"MsoNormal">=C2=A0</p><div><div><d=
iv><div><p class=3D"MsoNormal"><span style=3D"color:black">--------</span><=
/p></div><div><p class=3D"MsoNormal"><span style=3D"color:black">Randall St=
ewart</span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:blac=
k"><a href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></span></p></div><=
div><p class=3D"MsoNormal"><span style=3D"color:black">803-317-4952</span><=
/p></div><div><p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0</sp=
an></p></div></div><p class=3D"MsoNormal"><span style=3D"color:black">=C2=
=A0</span></p></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=
=C2=A0</p></div><p class=3D"MsoNormal">=C2=A0</p></div></div></div></body><=
/html>

--001a11c37d28aef03a050664591b--


From rrs@netflix.com  Thu Oct 23 12:47:11 2014
Return-Path: <rrs@netflix.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446D81ACFC8 for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ssVt58YuPwNz for <tsvwg@ietfa.amsl.com>; Thu, 23 Oct 2014 12:47:06 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 015C51ACFE7 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 12:47:05 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id v10so51128pde.36 for <tsvwg@ietf.org>; Thu, 23 Oct 2014 12:47:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=1MMxddOAVomddK1Vb1r1EmY+lD6JzQ26SecGyI5P5xc=; b=lpMQrDVbxsiehzaJNzZjix5PKHyzjTul5KvEy47+XfrF+d5sIgMGkxIffRSnDpqSED dmw68zOa0ZCN9bPT2vKyE3qKMuKbTctqsHh69Yh5SDRAABQta9sJancPKTIrPkEyOiq7 cPN4sCJe62zxFsy8FIEqG9/BysxZCFgCT+9Ho=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=1MMxddOAVomddK1Vb1r1EmY+lD6JzQ26SecGyI5P5xc=; b=YZ/goMSmxynbkMAqqi8nSIFXh9H2JWCzJGj2SBa8lNcR61B4cuGvmsjzG7o4+rl5wd ogL0rSIoVVnVKgIQq8yJMejevVHcpwWszmeUByZJDnZ9/YpCVTaB3jOL1ixGih3z1OXK GbhD2KZPsgLRLnZTXRUh4nFLUJYBSoxYneNy8ysyu3vHPDOPOlMLvINmLxrk1UjOPyYk zJF/1lt9M4Rzu7myl0485LKQr27vrnKXT3SCL/j8TP2hSLD0h0qz+eExkSKoVmMJGxKb cCp7baKAlapEGQ2ZkXDjJutv0l9Q9+qfNk76hknXuFul+AQ4qQrgmrb+PtN1VAJRMJs+ e59Q==
X-Gm-Message-State: ALoCoQkeADo+eaWeqYkjcB1A/S6ei4zMOFV0MIGEAuKdTGSU1/V3w8x/JvG2H0d/+HzgTfnb9MF4
X-Received: by 10.70.46.66 with SMTP id t2mr7037773pdm.51.1414093625496; Thu, 23 Oct 2014 12:47:05 -0700 (PDT)
Received: from lgml-rrs.corp.netflix.com ([69.53.237.72]) by mx.google.com with ESMTPSA id f7sm2199731pdj.15.2014.10.23.12.47.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Oct 2014 12:47:04 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D5C9EABA-13AA-4F09-8C3B-D651009C3D92"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Randall Stewart <rrs@netflix.com>
In-Reply-To: <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com>
Date: Thu, 23 Oct 2014 12:47:02 -0700
Message-Id: <5B3BC2A5-E440-49B1-AB7D-BBD47CB7F88D@netflix.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <6CDAFDC1-A246-4754-AA5C-3B334E3B8D2E@netflix.com> <e4b7b2855f6c96e8427c90bd8dadd022@mail.gmail.com> <20141023191215.GA12649@openss7.org> <e3bd41a4eea1884c35afdd58cd6f6af3@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_24YRUUEV3aVxld8sautD_XY4F0
X-Mailman-Approved-At: Mon, 27 Oct 2014 07:07:12 -0700
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org, tsvwg@ietf.org
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 23 Oct 2014 19:48:04 -0000

--Apple-Mail=_D5C9EABA-13AA-4F09-8C3B-D651009C3D92
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Karen:

Assume the TSN=92s (same sequence) are sent 100ms apart..=20

Sure we can construct a condition where they all go at once, but I can
also construct a condition where they do not. You can=92t increment FR =
counts
on things you have not been told.

You *can* implement one of the alternative schemes that folks have been =
floating around
to recover from tail drops.. but that was never in the spec and won=92t =
ever be in 4960.
It may be in some other RFC, thats fine, but 4960 never had the changes =
in it (however good
or bad they may be) you are asking for..

R
On Oct 23, 2014, at 12:35 PM, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:

> Hi,
>=20
> The TSN are sent at the same time, not sequentially.
>=20
> Assume they chunks are  ~0,6*MTU, then there would be no CWND =
constrains and
> no HB burst constraints.
> This I am saying just to avoid to get into such discussions or =
bundling
> discussions for that matter.
>=20
> BR, Karen
>=20
>=20
>=20
>> -----Original Message-----
>> From: Brian F. G. Bidulock [mailto:bidulock@openss7.org]
>> Sent: 23. oktober 2014 21:12
>> To: Karen Elisabeth Egede Nielsen
>> Cc: Randall Stewart; Michael Tuexen; tsvwg@ietf.org
>> Subject: Re: [tsvwg] SCTP mis indication counting during Fast =
Recovery
>>=20
>> Karen,
>>=20
>> Please see comments inline:
>>=20
>> On Thu, 23 Oct 2014, Karen Elisabeth Egede Nielsen wrote:
>>=20
>>>   HI,
>>>=20
>>>   Let's assume SCTP send a batch of packets, the packets marked with =
L
>>>   below are dropped, the packets with S are sacked.
>>>=20
>>>   There is no more new data to send.
>>>=20
>>>   SACKs arrive resulting in the following scorebard:
>>>=20
>>>   LSSSLL
>>>=20
>>>   in order from low -  high TSN.
>>>=20
>>>   This makes SCTP fast retransmit the first lost packet setting FR =
exit
>>>   point to last TSN.
>>>=20
>>>   resulting in increase of cumack and following scoreboard (A =
indicate
>>>   cumack'ed) once this TSN is sacked (which I assume).
>>>=20
>>>   AAAALL
>>>=20
>>>   There is 0 miscounts of the last two lost packets even if one =
packet
>>>   send since them obviously have been Sacked.
>>=20
>> TSN 1 ----------------> X
>> TSN 2 ----------------------------->
>>       <----------------------------- SACK 0, 2-2  TSN 1 peg =3D 1  =
TSN
>> 3 -------------------
>> ---------->
>>       <----------------------------- SACK 0, 2-3  TSN 1 peg =3D 2  =
TSN
>> 4 -------------------
>> ---------->
>>       <----------------------------- SACK 0, 2-4  TSN 1 peg =3D 3  =
Enter FR
>> exit point =3D
>> TSN 1  TSN 1 ----------------------------->
>>       <----------------------------- SACK 4  CA TSN >=3D exit point =
=3D> exit
>> FR  TSN 5 ---
>> -------------> X  TSN 6 ----------------> X
>>=20
>> At what point is the FR exit point greater than the highest  =
outstanding
>> TSN
>> in a SACK?  That is, at what point would pegging  up to the exit =
point
>> include
>> more TSNs that provided in the SACK?
>>=20
>>=20
>>>   Assumed also the following loss pattern. no new packets:
>>>=20
>>>   LSLSLSLL
>>>=20
>>>   Then   again this makes SCTP fast retransmit the first lost packet
>>>   setting FR exit point to last TSN.
>>>=20
>>>   After SACK of the retransmitted packet we have:
>>>=20
>>>   AALSLSLL and the first loss (TSN packet number 3) will now have 3
>>>   miscounts and will be allowed to be fast retransmitted following =
the
>>>   rule,
>>>=20
>>>   the same again for the third L. But the ones lost in the end do =
not
>>> get
>>>   any miscounts even if they same rule that apply to the first Lost
>>>   packets should
>>>=20
>>>   apply to the last lost ones.
>>=20
>> TSN 1 ----------------> X
>> TSN 2 ----------------------------->
>>       <----------------------------- SACK 0, 2-2  TSN 1 peg =3D 1  =
TSN
>> 3 ---------------->
>> X  TSN 4 ----------------------------->
>>       <----------------------------- SACK 0, 2-2, 4-4  TSN 1 peg =3D =
2, TSN
>> 3 peg =3D 1
>> TSN 5 ----------------> X  TSN 6 ----------------------------->
>>       <----------------------------- SACK 0, 2-2, 4-4, 6-6  TSN 1 peg =
=3D
>> 3, TSN 3 peg =3D
>> 2, TSN 5 peg =3D 1  Enter FR  exit point =3D TSN 5  TSN
>> 1 ----------------------------->
>>       <----------------------------- SACK 2, 4-4, 6-6  TSN 3 peg =3D =
3, TSN
>> 5 peg =3D 2
>> TSN 3 ----------------------------->
>>       <----------------------------- SACK 4, 6-6  TSN 5 peg =3D 3  =
TSN
>> 5 -------------------
>> ---------->
>>       <----------------------------- SACK 6  CA TSN >=3D exit point =
=3D> exit
>> FR  TSN 7 ---
>> -------------> X  TSN 8 ----------------> X
>>=20
>> At what point is the FR exit point greater than the highest  =
outstanding
>> TSN
>> in a SACK?  That is, at what point would pegging  up to the exit =
point
>> include
>> more TSNs that provided in the SACK?
>>=20
>>=20
>>>   I have written this a little hastely. I hope this can give the
>>> picture.
>>>=20
>>>   Perhaps with this explanation also the information in slide 30-33 =
of
>>>   the following now makes sense:
>>>=20
>>>=20
>>> [1]http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf,
>>>=20
>>>   BR, Karen
>>>=20
>>>   From: Randall Stewart [mailto:[2]rrs@netflix.com]
>>>   Sent: 23. oktober 2014 16:48
>>>   To: Karen Elisabeth Egede Nielsen
>>>   Cc: Michael Tuexen; [3]bidulock@openss7.org
>>>   Subject: Re: [tsvwg] SCTP mis indication counting during Fast
>>> Recovery
>>>=20
>>>   Karen:
>>>=20
>>>   Note I dropped tsvwg due to the fact that this email would get =
locked
>>>   up and held/bounced since [4]rrs@netflix.com is
>>>   not a subscriber to tsvwg
>>>=20
>>>   I like Brian am a bit confused by your request in that I don't see
>>> how
>>>   this could happen.
>>>=20
>>>   SCTP has the ability to identify 300+ sack gaps. I think this
>>>   is why the wording is the way it is. We could not conceive of a
>>> situation
>>>   where the SACK would come back (outside of reneging) and not list
>>> what
>>>   was previously there. Especially if the SACK is a response to the
>>>   fast-retransmit.
>>>=20
>>>   In theory it *should* contain all the gap acks that were present =
up
>>> to
>>>   your "fast recovery point".
>>>=20
>>>   Like Brian I too don't remember ever making a "fast recovery =
point"
>>> in
>>>   SCTP.
>>>=20
>>>   Now I guess you could get a situation where the fast retransmit
>>> passed
>> the
>>>   last TSN sent and the sender is thus responding.. but thats still
>>>   pending data that *may* still arrive.
>>>=20
>>>   So unless the sender purposely stops gap-acking previously =
gap-acked
>>>   packets (reneged) then I don't see how this could happen.
>>>=20
>>>   Could you explain how you see this could happen .. it could be I =
am
>>>   missing something that is clear to you..
>>>=20
>>>   Thanks
>>>=20
>>=20
>> --
>> Brian F. G. Bidulock
>> bidulock@openss7.org
>> http://www.openss7.org/

--------
Randall Stewart
rrs@netflix.com
803-317-4952






--Apple-Mail=_D5C9EABA-13AA-4F09-8C3B-D651009C3D92
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Karen:<div><br></div><div>Assume the TSN=92s (same =
sequence) are sent 100ms apart..&nbsp;</div><div><br></div><div>Sure we =
can construct a condition where they all go at once, but I =
can</div><div>also construct a condition where they do not. You can=92t =
increment FR counts</div><div>on things you have not been =
told.</div><div><br></div><div>You *can* implement one of the =
alternative schemes that folks have been floating around</div><div>to =
recover from tail drops.. but that was never in the spec and won=92t =
ever be in 4960.</div><div>It may be in some other RFC, thats fine, but =
4960 never had the changes in it (however good</div><div>or bad they may =
be) you are asking =
for..</div><div><br></div><div>R</div><div><div><div>On Oct 23, 2014, at =
12:35 PM, Karen Elisabeth Egede Nielsen &lt;<a =
href=3D"mailto:karen.nielsen@tieto.com">karen.nielsen@tieto.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi,<br><br>The TSN are sent at the same time, not =
sequentially.<br><br>Assume they chunks are &nbsp;~0,6*MTU, then there =
would be no CWND constrains and<br>no HB burst constraints.<br>This I am =
saying just to avoid to get into such discussions or =
bundling<br>discussions for that matter.<br><br>BR, =
Karen<br><br><br><br><blockquote type=3D"cite">-----Original =
Message-----<br>From: Brian F. G. Bidulock [<a =
href=3D"mailto:bidulock@openss7.org">mailto:bidulock@openss7.org</a>]<br>S=
ent: 23. oktober 2014 21:12<br>To: Karen Elisabeth Egede Nielsen<br>Cc: =
Randall Stewart; Michael Tuexen; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br>Subject: Re: =
[tsvwg] SCTP mis indication counting during Fast =
Recovery<br><br>Karen,<br><br>Please see comments inline:<br><br>On Thu, =
23 Oct 2014, Karen Elisabeth Egede Nielsen wrote:<br><br><blockquote =
type=3D"cite"> &nbsp;&nbsp;HI,<br><br> &nbsp;&nbsp;Let's assume SCTP =
send a batch of packets, the packets marked with L<br> &nbsp;&nbsp;below =
are dropped, the packets with S are sacked.<br><br> &nbsp;&nbsp;There is =
no more new data to send.<br><br> &nbsp;&nbsp;SACKs arrive resulting in =
the following scorebard:<br><br> &nbsp;&nbsp;LSSSLL<br><br> =
&nbsp;&nbsp;in order from low - &nbsp;high TSN.<br><br> &nbsp;&nbsp;This =
makes SCTP fast retransmit the first lost packet setting FR exit<br> =
&nbsp;&nbsp;point to last TSN.<br><br> &nbsp;&nbsp;resulting in increase =
of cumack and following scoreboard (A indicate<br> =
&nbsp;&nbsp;cumack'ed) once this TSN is sacked (which I assume).<br><br> =
&nbsp;&nbsp;AAAALL<br><br> &nbsp;&nbsp;There is 0 miscounts of the last =
two lost packets even if one packet<br> &nbsp;&nbsp;send since them =
obviously have been Sacked.<br></blockquote><br> TSN 1 =
----------------&gt; X<br> TSN 2 -----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-2 &nbsp;TSN 1 peg =3D 1 &nbsp;TSN<br>3 =
-------------------<br>----------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-3 &nbsp;TSN 1 peg =3D 2 &nbsp;TSN<br>4 =
-------------------<br>----------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-4 &nbsp;TSN 1 peg =3D 3 &nbsp;Enter FR<br>exit point =3D<br>TSN =
1 &nbsp;TSN 1 -----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 4 &nbsp;CA TSN &gt;=3D exit point =3D&gt; exit<br>FR &nbsp;TSN 5 =
---<br>-------------&gt; X &nbsp;TSN 6 ----------------&gt; X<br><br> At =
what point is the FR exit point greater than the highest =
&nbsp;outstanding<br>TSN<br>in a SACK? &nbsp;That is, at what point =
would pegging &nbsp;up to the exit point<br>include<br>more TSNs that =
provided in the SACK?<br><br><br><blockquote type=3D"cite"> =
&nbsp;&nbsp;Assumed also the following loss pattern. no new =
packets:<br><br> &nbsp;&nbsp;LSLSLSLL<br><br> &nbsp;&nbsp;Then =
&nbsp;&nbsp;again this makes SCTP fast retransmit the first lost =
packet<br> &nbsp;&nbsp;setting FR exit point to last TSN.<br><br> =
&nbsp;&nbsp;After SACK of the retransmitted packet we have:<br><br> =
&nbsp;&nbsp;AALSLSLL and the first loss (TSN packet number 3) will now =
have 3<br> &nbsp;&nbsp;miscounts and will be allowed to be fast =
retransmitted following the<br> &nbsp;&nbsp;rule,<br><br> =
&nbsp;&nbsp;the same again for the third L. But the ones lost in the end =
do not<br>get<br> &nbsp;&nbsp;any miscounts even if they same rule that =
apply to the first Lost<br> &nbsp;&nbsp;packets should<br><br> =
&nbsp;&nbsp;apply to the last lost ones.<br></blockquote><br> TSN 1 =
----------------&gt; X<br> TSN 2 -----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-2 &nbsp;TSN 1 peg =3D 1 &nbsp;TSN<br>3 =
----------------&gt;<br>X &nbsp;TSN 4 =
-----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-2, 4-4 &nbsp;TSN 1 peg =3D 2, TSN<br>3 peg =3D 1<br>TSN 5 =
----------------&gt; X &nbsp;TSN 6 -----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 0, 2-2, 4-4, 6-6 &nbsp;TSN 1 peg =3D<br>3, TSN 3 peg =3D<br>2, TSN =
5 peg =3D 1 &nbsp;Enter FR &nbsp;exit point =3D TSN 5 &nbsp;TSN<br>1 =
-----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 2, 4-4, 6-6 &nbsp;TSN 3 peg =3D 3, TSN<br>5 peg =3D 2<br>TSN 3 =
-----------------------------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 4, 6-6 &nbsp;TSN 5 peg =3D 3 &nbsp;TSN<br>5 =
-------------------<br>----------&gt;<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;----------------------------- =
SACK 6 &nbsp;CA TSN &gt;=3D exit point =3D&gt; exit<br>FR &nbsp;TSN 7 =
---<br>-------------&gt; X &nbsp;TSN 8 ----------------&gt; X<br><br> At =
what point is the FR exit point greater than the highest =
&nbsp;outstanding<br>TSN<br>in a SACK? &nbsp;That is, at what point =
would pegging &nbsp;up to the exit point<br>include<br>more TSNs that =
provided in the SACK?<br><br><br><blockquote type=3D"cite"> =
&nbsp;&nbsp;I have written this a little hastely. I hope this can give =
the<br>picture.<br><br> &nbsp;&nbsp;Perhaps with this explanation also =
the information in slide 30-33 of<br> &nbsp;&nbsp;the following now =
makes sense:<br><br><br>[1]<a =
href=3D"http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf">=
http://www.ietf.org/proceedings/90/slides/slides-90-tsvwg-16.pdf</a>,<br><=
br> &nbsp;&nbsp;BR, Karen<br><br> &nbsp;&nbsp;From: Randall Stewart =
[mailto:[2]<a href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a>]<br> =
&nbsp;&nbsp;Sent: 23. oktober 2014 16:48<br> &nbsp;&nbsp;To: Karen =
Elisabeth Egede Nielsen<br> &nbsp;&nbsp;Cc: Michael Tuexen; [3]<a =
href=3D"mailto:bidulock@openss7.org">bidulock@openss7.org</a><br> =
&nbsp;&nbsp;Subject: Re: [tsvwg] SCTP mis indication counting during =
Fast<br>Recovery<br><br> &nbsp;&nbsp;Karen:<br><br> &nbsp;&nbsp;Note I =
dropped tsvwg due to the fact that this email would get locked<br> =
&nbsp;&nbsp;up and held/bounced since [4]<a =
href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a> is<br> =
&nbsp;&nbsp;not a subscriber to tsvwg<br><br> &nbsp;&nbsp;I like Brian =
am a bit confused by your request in that I don't see<br>how<br> =
&nbsp;&nbsp;this could happen.<br><br> &nbsp;&nbsp;SCTP has the ability =
to identify 300+ sack gaps. I think this<br> &nbsp;&nbsp;is why the =
wording is the way it is. We could not conceive of a<br>situation<br> =
&nbsp;&nbsp;where the SACK would come back (outside of reneging) and not =
list<br>what<br> &nbsp;&nbsp;was previously there. Especially if the =
SACK is a response to the<br> &nbsp;&nbsp;fast-retransmit.<br><br> =
&nbsp;&nbsp;In theory it *should* contain all the gap acks that were =
present up<br>to<br> &nbsp;&nbsp;your "fast recovery point".<br><br> =
&nbsp;&nbsp;Like Brian I too don't remember ever making a "fast recovery =
point"<br>in<br> &nbsp;&nbsp;SCTP.<br><br> &nbsp;&nbsp;Now I guess you =
could get a situation where the fast =
retransmit<br>passed<br></blockquote>the<br><blockquote type=3D"cite"> =
&nbsp;&nbsp;last TSN sent and the sender is thus responding.. but thats =
still<br> &nbsp;&nbsp;pending data that *may* still arrive.<br><br> =
&nbsp;&nbsp;So unless the sender purposely stops gap-acking previously =
gap-acked<br> &nbsp;&nbsp;packets (reneged) then I don't see how this =
could happen.<br><br> &nbsp;&nbsp;Could you explain how you see this =
could happen .. it could be I am<br> &nbsp;&nbsp;missing something that =
is clear to you..<br><br> =
&nbsp;&nbsp;Thanks<br><br></blockquote><br>--<br>Brian F. G. =
Bidulock<br><a =
href=3D"mailto:bidulock@openss7.org">bidulock@openss7.org</a><br>http://ww=
w.openss7.org/<br></blockquote></blockquote></div><br><div =
apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>--------</div><div>Randall Stewart</div><div><a =
href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></div><div>803-317-4952=
</div><div><br></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_D5C9EABA-13AA-4F09-8C3B-D651009C3D92--


From nobody Mon Oct 27 07:07:50 2014
Return-Path: <xiayangsong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C521A1BDA for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 18:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 OOL9sQn-_iz1 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 18:37:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 020B91A1B6C for <tsvwg@ietf.org>; Fri, 24 Oct 2014 18:37:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOA23644; Sat, 25 Oct 2014 01:37:24 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 25 Oct 2014 02:37:22 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.225]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Sat, 25 Oct 2014 09:37:17 +0800
From: Xiayangsong <xiayangsong@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>, "nvo3-chairs@tools.ietf.org" <nvo3-chairs@tools.ietf.org>
Thread-Topic: I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
Thread-Index: AQHP7+4v9fpxR/1h2EmSavyoF8P64JxAAlvg
Date: Sat, 25 Oct 2014 01:37:16 +0000
Message-ID: <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AF4AD.50503@gmail.com>
In-Reply-To: <544AF4AD.50503@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/b6fMtKfDHJhpaCbwSPUqGaIjK7Q
X-Mailman-Approved-At: Mon, 27 Oct 2014 07:07:13 -0700
Subject: Re: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Oct 2014 01:37:29 -0000

SGkgQnJpYW4NCg0KVGhhbmtzIGZvciB5b3VyIGF0dGVudGlvbiBvbiB0aGlzIHRvcGljLg0KSSBh
bSBhbiBlbmdpbmVlciBub3QgYSBzdGFuZGFyZCAgZ3V5IC4NCkkgZGlzY3Vzc2VkIHRoaXMgaWRl
YSB3aXRoIEJlaGNldCB3aG8ga2luZGx5IHB1dCBtZSBhcyB0aGUgZmlyc3QgYXV0aG9yLg0KDQpT
byBJIHRyeSB0byByZXNwb25kIHlvdSBmcm9tIGVuZ2luZWVyaW5nIHBlcnNwZWN0aXZlLg0KDQpU
aGFua3MNCkZyYW5rDQoNCi0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dIA0K5Y+R6YCB
5pe26Ze0OiAyMDE05bm0MTDmnIgyNeaXpSA4OjU0DQrmlLbku7bkuro6IHRzdndnQGlldGYub3Jn
OyBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nQHRvb2xzLmlldGYub3JnOyBudm8zLWNo
YWlyc0B0b29scy5pZXRmLm9yZw0K5Li76aKYOiBSZTogSS1EIEFjdGlvbjogZHJhZnQteGlhLW52
bzMtdnhsYW4tcW9zbWFya2luZy0wMC50eHQNCg0KSGksDQoNClRoaXMgZHJhZnQgbmVlZHMgdG8g
YmUgZGlzY3Vzc2VkIGluIHRzdndnIEkgdGhpbmsuIEl0IGhhcyBzb21lIHNpZ25pZmljYW50IHBy
b2JsZW1zIElNSE86DQoNCjEuIEl0IGNvbmZ1c2VzIFFvUyBhbmQgcHJpb3JpdHkgaW4gYSBzdHJh
bmdlIHdheS4NCkZyYW5rPT5Rb1MgaXMgYWJvdXQgcGFja2V0IGxvc3MsIGJhbmR3aWR0aCwgbGF0
ZW5jeSBhbmQgaml0dGVyLiAgQmFuZHdpZHRoIGNhbiBiZSBjb250cm9sbGVyIGJ5IENBUiB0ZWNo
bm9sb2d5Lg0KQXMgZm9yIGxhdGVuY3kgYW5kIGppdHRlciwgdGhleSBhcmUga2luZCBvZiBpbmhl
cmVudCBwYXJhbWV0ZXIgb2YgYSBnaXZlbiBuZXR3b3JrLCBhbmQgdGhlcmUgaXMgaGFyZGx5IGEg
d2F5IHRvIA0KY29udHJvbGxlciB0aGVtIC4gICBUaHVzLCBpbiBtb3N0IHNjZW5hcmlvLCBRb1Mg
aXMgYWJvdXQgcGFja2V0IGxvc3MgY29udHJvbCB3aGljaCBpcyAgYmFzZWQgb24gcHJpb3JpdHku
DQoNCjIuIEl0IHJlcGVhdHMgdGhlIE1QTFMgZXJyb3Igb2YgdHJ5aW5nIHRvIGV4cHJlc3Mgc2Vy
dmljZSBkaWZmZXJlbnRpYXRpb24gaW4gMyBiaXRzLg0KRnJhbms9PkkgZG9uJ3Qga25vdyB0aGUg
TVBMUyBlcnJvciwgcGxlYXNlIHRlYWNoIG1lLiAgSG93ZXZlciwgaW4gZW5naW5lZXJpbmcgYXJl
YSwgTVBMUyAzIGJpdA0KaGFzIGEgcHJhZ21hdGljIHB1cnBvc2UuICBZb3UgY2FuIGNoZWNrIHN3
aXRjaGVzL3JvdXRlcnMgc3BlY2lmaWNhdGlvbiBmcm9tIGRpZmZlcmVudCB2ZW5kb3JzIGFib3V0
IHRoaXMuICANCg0KMy4gSXQgbWFrZXMgYSBjb21wbGV0ZWx5IGluYWNjdXJhdGUgc3RhdGVtZW50
IGFib3V0IGRpZmZzZXJ2Og0KIlRoZSBmaXJzdCB0aHJlZSBiaXRzIG9mIERTIGZpZWxkIGFyZSB1
c2VkIGZvciBJUCBwcmVjZWRlbmNlIGFuZCB0aGUgbGFzdCB0aHJlZSBhcmUgdXNlZCBhcyBkaWZm
IHNlcnYgYml0cy4iDQpGcmFuaz0+SSBndWVzcyB0aGUgc3RhdGVtZW50IHdhcyBjb3BpZWQgZnJv
bSBzb21lIFJGQywgYW5kIEkgd291bGQgZG91YmxlIGNoZWNrIGl0Lg0KDQogIEJyaWFuDQoNCk9u
IDI1LzEwLzIwMTQgMDg6MTYsIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyB3cm90ZToNCj4gQSBO
ZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQt
RHJhZnRzIGRpcmVjdG9yaWVzLg0KPiANCj4gDQo+ICAgICAgICAgVGl0bGUgICAgICAgICAgIDog
UXVhbGl0eSBvZiBTZXJ2aWNlIE1hcmtpbmcgaW4gVmlydHVhbCBlWHRlbnNpYmxlIExvY2FsIEFy
ZWEgTmV0d29yaw0KPiAgICAgICAgIEF1dGhvcnMgICAgICAgICA6IEZyYW5rIFhpYQ0KPiAgICAg
ICAgICAgICAgICAgICAgICAgICAgIEJlaGNldCBTYXJpa2F5YQ0KPiAJRmlsZW5hbWUgICAgICAg
IDogZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMC50eHQNCj4gCVBhZ2VzICAgICAg
ICAgICA6IDkNCj4gCURhdGUgICAgICAgICAgICA6IDIwMTQtMTAtMjQNCj4gDQo+IEFic3RyYWN0
Og0KPiAgICBUaGUgVmlydHVhbCBlWHRlbnNpYmxlIExvY2FsIEFyZWEgTmV0d29yayBlbmFibGVz
IG11bHRpcGxlIHRlbmFudHMgdG8NCj4gICAgb3BlcmF0ZSBpbiBhIGRhdGEgY2VudGVyLiAgRWFj
aCB0ZW5hbnQgbmVlZHMgdG8gYmUgYXNzaWduZWQgYQ0KPiAgICBwcmlvcml0eSBncm91cCB0byBw
cmlvcml0aXplIHRoZWlyIHRyYWZmaWMuICBDbG91ZCBjYXJyaWVycyB3aXNoIHRvDQo+ICAgIHVz
ZSBxdWFsaXR5IG9mIHNlcnZpY2UgdG8gZGlmZmVyZW50aWF0ZSBkaWZmZXJlbnQgYXBwbGljYXRp
b25zLiAgRm9yDQo+ICAgIHRoZXNlIHB1cnBvc2VzLCB0aHJlZSBiaXRzIGFyZSBhc3NpZ25lZCBp
biB0aGUgZVh0ZW5zaWJsZSBMb2NhbCBBcmVhDQo+ICAgIE5ldHdvcmsgaGVhZGVyLiAgSG93IHRo
ZXNlIGJpdHMgYXJlIGFzc2lnbmVkIGFuZCBhcmUgcHJvY2Vzc2VkIGluIHRoZQ0KPiAgICBuZXR3
b3JrIGFyZSBleHBsYWluZWQgaW4gZGV0YWlsLg0KPiANCj4gDQo+IFRoZSBJRVRGIGRhdGF0cmFj
a2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiBodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLw0KPiANCj4gVGhl
cmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+IGh0dHA6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmctMDANCj4gDQo+
IA0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJv
bSB0aGUgdGltZSBvZiANCj4gc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBh
bmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPiANCj4gSW50ZXJuZXQt
RHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPiBmdHA6Ly9m
dHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiANCj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSS1ELUFubm91bmNlIG1haWxpbmcgbGlzdA0K
PiBJLUQtQW5ub3VuY2VAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pLWQtYW5ub3VuY2UNCj4gSW50ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6
Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwgb3IgDQo+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRm
LzFzaGFkb3ctc2l0ZXMudHh0DQo+IA0KDQo=


From nobody Mon Oct 27 07:08:28 2014
Return-Path: <xiayangsong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6E01A1BA9; Sun, 26 Oct 2014 18:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 dr4upYm45syY; Sun, 26 Oct 2014 18:12:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E30F1A1ACD; Sun, 26 Oct 2014 18:12:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKY62075; Mon, 27 Oct 2014 01:12:40 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Oct 2014 01:12:40 +0000
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.225]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Mon, 27 Oct 2014 09:12:35 +0800
From: Xiayangsong <xiayangsong@huawei.com>
To: "Black, David" <david.black@emc.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [tsvwg] I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
Thread-Index: AQHP7+4v9fpxR/1h2EmSavyoF8P64JxAAlvg//+mZoCAAooJgIAA8RQQ
Date: Mon, 27 Oct 2014 01:12:34 +0000
Message-ID: <CB60645E6241144CB82269604373757A603D4675@nkgeml503-mbx.china.huawei.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AF4AD.50503@gmail.com> <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com> <544B1EEF.7040002@gmail.com> <CE03DB3D7B45C245BCA0D24327794936066F2C@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D24327794936066F2C@MX104CL02.corp.emc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/NfMlwQzgohSUpYGqQW-utDpPjVY
X-Mailman-Approved-At: Mon, 27 Oct 2014 07:07:14 -0700
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>
Subject: [tsvwg] =?utf-8?b?562U5aSNOiAgSS1EIEFjdGlvbjogZHJhZnQteGlhLW52?= =?utf-8?q?o3-vxlan-qosmarking-00=2Etxt?=
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 01:12:45 -0000
X-List-Received-Date: Mon, 27 Oct 2014 01:12:45 -0000

SGkgRGF2aWQNCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldy4NClBsZWFzZSBjaGVjayBteSBpbmxp
bmUgcmVzcG9uc2UuDQoNClRoYW5rcw0KRnJhbmsNCg0KLS0tLS3pgq7ku7bljp/ku7YtLS0tLQ0K
5Y+R5Lu25Lq6OiBCbGFjaywgRGF2aWQgW21haWx0bzpkYXZpZC5ibGFja0BlbWMuY29tXSANCuWP
kemAgeaXtumXtDogMjAxNOW5tDEw5pyIMjfml6UgMjo0MQ0K5pS25Lu25Lq6OiBCcmlhbiBFIENh
cnBlbnRlcjsgWGlheWFuZ3NvbmcNCuaKhOmAgTogbnZvM0BpZXRmLm9yZzsgdHN2d2dAaWV0Zi5v
cmc7IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmdAdG9vbHMuaWV0Zi5vcmc7IEJsYWNr
LCBEYXZpZA0K5Li76aKYOiBSRTogW3RzdndnXSBJLUQgQWN0aW9uOiBkcmFmdC14aWEtbnZvMy12
eGxhbi1xb3NtYXJraW5nLTAwLnR4dA0KDQo+IEkgc3VnZ2VzdCBjYXJlZnVsbHkgcmV2aWV3aW5n
IFJGQyAyNDc0IGFuZCBSRkMgMjQ3NSwgYW5kIHRoZSBzcGVjaWZpYyANCj4gZGVzY3JpcHRpb25z
IG9mIHBlci1ob3AgYmVoYXZpb3VycyBpbiBSRkMgMjU5NyBhbmQgUkZDIDMyNDYuIEFsc28gaXQg
DQo+IGlzIHdvcnRoIHJldmlld2luZyBSRkMgNDU5NCwgZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vy
di1pbnRlcmNvbiwgYW5kIA0KPiB0aGUgd29yayBvZiB0aGUgQVFNIFdHIChodHRwOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvd2cvYXFtL2NoYXJ0ZXIvKS4gDQo+IFRydWx5IHRoZXJlIGlzIGEgbG90
IG1vcmUgdG8gcXVldWUgbWFuYWdlbWVudCB0aGFuIHNpbXBsZSBwcmlvcml0eS4NCg0KVG8gYmUg
bW9yZSBzcGVjaWZpYywgc2VjdGlvbiA0IG9mIGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtp
bmcgYXBwZWFycyB0byBiZSBoZWFkZWQgdG93YXJkcyByZWludmVudGluZyBSRkMgNDU5NCwgc28g
SSBzdHJvbmdseSBzdWdnZXN0IHJldmlld2luZyB0aGF0IFJGQy4NCkZyYW5rPT5vay4gV2Ugd2ls
bCBkZWZpbml0ZWx5IHN0dWR5IHRoZSBSRkMuDQoNCiAgSW4gYWRkaXRpb24gdG8gdGhlIGRvY3Vt
ZW50cyBCcmlhbiBsaXN0ZWQsIHRoZXJlJ3MgYWxzbyBzb21lIHNob3J0ZXIgZGlmZnNlcnYgYmFj
a2dyb3VuZCBpbmZvcm1hdGlvbiBpbiBkcmFmdC1pZXRmLWRhcnQtZHNjcC1ydHAgdGhhdCBtYXkg
YmUgaGVscGZ1bC4NCklmIGJpdCBjb25zZXJ2YXRpb24gaXMgcmVhbGx5IGltcG9ydGFudCwgSSBy
ZWNvbW1lbmQgcmV2aWV3aW5nIFJGQyA1MTI3IGluIGFkZGl0aW9uIHRvIGRyYWZ0LWdlaWItdHN2
d2ctZGlmZnNlcnYtaW50ZXJjb24uDQpGcmFuaz0+b2ssIFRoYW5rIHlvdSBhZ2FpbiBmb3IgdGhl
IG1hdGVyaWFsLg0KDQpJdCBpcyB1bmZvcnR1bmF0ZSB0aGF0IGRyYWZ0LXhpYS1udm8zLXZ4bGFu
LXFvc21hcmtpbmcgbm9ybWF0aXZlbHkgcmVmZXJlbmNlcyBSRkMgMjQ3NCwgYnV0IGFwcGVhcnMg
dG8gZWZmZWN0aXZlbHkgaWdub3JlIHRoYXQgUkZDLg0KRnJhbms9PlRoYW5rIHlvdSBwb2ludGlu
ZyBvdXQgdGhpcy4gV2Ugd2lsbCBtb2RpZnkgdGhlIGRyYWZ0ICBhbmQgaG9wZWZ1bGx5IHlvdSBj
YW4gIHJldmlldyBpdCBhZ2Fpbi4NCg0KVGhhbmtzLA0KLS1EYXZpZA0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHRzdndnIFttYWlsdG86dHN2d2ctYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIEJyaWFuIEUgDQo+IENhcnBlbnRlcg0KPiBTZW50OiBGcmlkYXks
IE9jdG9iZXIgMjQsIDIwMTQgMTE6NTQgUE0NCj4gVG86IFhpYXlhbmdzb25nDQo+IENjOiBudm8z
LWNoYWlyc0B0b29scy5pZXRmLm9yZzsgbnZvM0BpZXRmLm9yZzsgdHN2d2dAaWV0Zi5vcmc7IA0K
PiBkcmFmdC14aWEtbnZvMy0gdnhsYW4tcW9zbWFya2luZ0B0b29scy5pZXRmLm9yZw0KPiBTdWJq
ZWN0OiBSZTogW3RzdndnXSBJLUQgQWN0aW9uOiANCj4gZHJhZnQteGlhLW52bzMtdnhsYW4tcW9z
bWFya2luZy0wMC50eHQNCj4gDQo+IEhpLA0KPiANCj4gT24gMjUvMTAvMjAxNCAxNDozNywgWGlh
eWFuZ3Nvbmcgd3JvdGU6DQo+ID4gSGkgQnJpYW4NCj4gPg0KPiA+IFRoYW5rcyBmb3IgeW91ciBh
dHRlbnRpb24gb24gdGhpcyB0b3BpYy4gSSBhbSBhbiBlbmdpbmVlciBub3QgYSANCj4gPiBzdGFu
ZGFyZCAgZ3V5IC4gSSBkaXNjdXNzZWQgdGhpcyBpZGVhIHdpdGggQmVoY2V0IHdobyBraW5kbHkg
cHV0IG1lIA0KPiA+IGFzIHRoZSBmaXJzdCBhdXRob3IuDQo+ID4NCj4gPiBTbyBJIHRyeSB0byBy
ZXNwb25kIHlvdSBmcm9tIGVuZ2luZWVyaW5nIHBlcnNwZWN0aXZlLg0KPiANCj4gVW5kZXJzdG9v
ZCwgYnV0IElFVEYgc3RhbmRhcmRzIGFyZSBzdXBwb3NlZCB0byBjb3JyZXNwb25kIHRvIHJlYWwg
DQo+IGVuZ2luZWVyaW5nLCBzbyB0aGF0IGlzIG5vIHByb2JsZW0uDQo+IA0KPiA+DQo+ID4gVGhh
bmtzIEZyYW5rDQo+ID4NCj4gPiAtLS0tLemCruS7tuWOn+S7ti0tLS0tIOWPkeS7tuS6ujogQnJp
YW4gRSBDYXJwZW50ZXIgDQo+ID4gW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21d
IOWPkemAgeaXtumXtDogMjAxNOW5tDEw5pyIMjXml6UgODo1NCDmlLYNCj4gPiDku7bkuro6IHRz
dndnQGlldGYub3JnOw0KPiA+IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmdAdG9vbHMu
aWV0Zi5vcmc7DQo+ID4gbnZvMy1jaGFpcnNAdG9vbHMuaWV0Zi5vcmcg5Li76aKYOiBSZTogSS1E
IEFjdGlvbjoNCj4gPiBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwLnR4dA0KPiA+
DQo+ID4gSGksDQo+ID4NCj4gPiBUaGlzIGRyYWZ0IG5lZWRzIHRvIGJlIGRpc2N1c3NlZCBpbiB0
c3Z3ZyBJIHRoaW5rLiBJdCBoYXMgc29tZSANCj4gPiBzaWduaWZpY2FudCBwcm9ibGVtcyBJTUhP
Og0KPiA+DQo+ID4gMS4gSXQgY29uZnVzZXMgUW9TIGFuZCBwcmlvcml0eSBpbiBhIHN0cmFuZ2Ug
d2F5Lg0KPiANCj4gPiBGcmFuaz0+UW9TDQo+ID4gaXMgYWJvdXQgcGFja2V0IGxvc3MsIGJhbmR3
aWR0aCwgbGF0ZW5jeSBhbmQgaml0dGVyLg0KPiANCj4gVGhvc2UgYXJlIHRoZSB1c3VhbCBRb1Mg
bWV0cmljcyBvZiBjb3Vyc2UuDQo+IA0KPiA+IEJhbmR3aWR0aCBjYW4gYmUgY29udHJvbGxlciBi
eSBDQVIgdGVjaG5vbG9neS4gQXMgZm9yIGxhdGVuY3kgYW5kIA0KPiA+IGppdHRlciwgdGhleSBh
cmUga2luZCBvZiBpbmhlcmVudCBwYXJhbWV0ZXIgb2YgYSBnaXZlbiBuZXR3b3JrLCBhbmQgDQo+
ID4gdGhlcmUgaXMgaGFyZGx5IGEgd2F5IHRvIGNvbnRyb2xsZXIgdGhlbSAuDQo+ID4gVGh1cywg
aW4gbW9zdCBzY2VuYXJpbywgUW9TIGlzIGFib3V0IHBhY2tldCBsb3NzIGNvbnRyb2wgd2hpY2gg
aXMgIA0KPiA+IGJhc2VkIG9uIHByaW9yaXR5Lg0KPiANCj4gSSBzdWdnZXN0IGNhcmVmdWxseSBy
ZXZpZXdpbmcgUkZDIDI0NzQgYW5kIFJGQyAyNDc1LCBhbmQgdGhlIHNwZWNpZmljIA0KPiBkZXNj
cmlwdGlvbnMgb2YgcGVyLWhvcCBiZWhhdmlvdXJzIGluIFJGQyAyNTk3IGFuZCBSRkMgMzI0Ni4g
QWxzbyBpdCANCj4gaXMgd29ydGggcmV2aWV3aW5nIFJGQyA0NTk0LCBkcmFmdC1nZWliLXRzdndn
LWRpZmZzZXJ2LWludGVyY29uLCBhbmQgDQo+IHRoZSB3b3JrIG9mIHRoZSBBUU0gV0cgKGh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy93Zy9hcW0vY2hhcnRlci8pLiANCj4gVHJ1bHkgdGhlcmUg
aXMgYSBsb3QgbW9yZSB0byBxdWV1ZSBtYW5hZ2VtZW50IHRoYW4gc2ltcGxlIHByaW9yaXR5Lg0K
PiANCj4gPiAyLiBJdCByZXBlYXRzIHRoZSBNUExTIGVycm9yIG9mIHRyeWluZyB0byBleHByZXNz
IHNlcnZpY2UgDQo+ID4gZGlmZmVyZW50aWF0aW9uIGluIDMgYml0cy4NCj4gDQo+IA0KPiA+IEZy
YW5rPT5JIGRvbid0IGtub3cgdGhlIE1QTFMNCj4gPiBlcnJvciwgcGxlYXNlIHRlYWNoIG1lLiAg
SG93ZXZlciwgaW4gZW5naW5lZXJpbmcgYXJlYSwgTVBMUyAzIGJpdCANCj4gPiBoYXMgYSBwcmFn
bWF0aWMgcHVycG9zZS4gIFlvdSBjYW4gY2hlY2sgc3dpdGNoZXMvcm91dGVycyANCj4gPiBzcGVj
aWZpY2F0aW9uIGZyb20gZGlmZmVyZW50IHZlbmRvcnMgYWJvdXQgdGhpcy4NCj4gDQo+IFRoZSBw
cm9ibGVtIGlzIHRoYXQgcmUtdXNpbmcgdGhlIHRocmVlIEVYUCAoZXhwZXJpbWVudGFsKSBiaXRz
IGluIE1QTFMgDQo+IGZvciBxdWFsaXR5IG9mIHNlcnZpY2Ugc2lnbmFsbGluZyB3YXMgYW4gYWZ0
ZXJ0aG91Z2h0Lg0KPiBUaHJlZSBiaXRzIHNpbXBseSBpc24ndCBlbm91Z2ggdG8gZXhwcmVzcyBh
IHJlYXNvbmFibGUgcmFuZ2Ugb2YgDQo+IHNlcnZpY2UgY2xhc3Nlcy4gVW5mb3J0dW5hdGVseSBp
dCBpcyBhbGwgd2UgaGF2ZSBpbiBNUExTLCBidXQgdGhhdCBpcyANCj4gbm90IGEgdmFsaWQgcmVh
c29uIGZvciBjb3B5aW5nIHRoZSBzYW1lIG1pc3Rha2UuIElmIHlvdSBhZG9wdCA2IGJpdHMsIA0K
PiBpdCBzaG91bGQgYmUgZmFpcmx5IGVhc3kgdG8gYWRvcHQgdGhlIHdob2xlIGRpZmZzZXJ2IG1v
ZGVsLiBUaGF0IHdvdWxkIA0KPiBzYXZlIGEgbG90IG9mIHdvcmssIGJvdGggaW4gc3BlY2lmaWNh
dGlvbiBhbmQgaW4gaW1wbGVtZW50YXRpb24uDQo+IA0KPiA+DQo+ID4gMy4gSXQgbWFrZXMgYSBj
b21wbGV0ZWx5IGluYWNjdXJhdGUgc3RhdGVtZW50IGFib3V0IGRpZmZzZXJ2Og0KPiA+ICAiVGhl
IGZpcnN0IHRocmVlIGJpdHMgb2YgRFMgZmllbGQgYXJlIHVzZWQgZm9yIElQIHByZWNlZGVuY2Ug
YW5kIA0KPiA+IHRoZSBsYXN0IHRocmVlIGFyZSB1c2VkIGFzIGRpZmYgc2VydiBiaXRzLiINCj4g
DQo+IA0KPiA+IEZyYW5rPT5JDQo+ID4gZ3Vlc3MgdGhlIHN0YXRlbWVudCB3YXMgY29waWVkIGZy
b20gc29tZSBSRkMsIGFuZCBJIHdvdWxkIGRvdWJsZSANCj4gPiBjaGVjayBpdC4NCj4gDQo+IElm
IHNvLCB0aGF0IFJGQyBpcyB3cm9uZy4gSXQgaXMgdHJ1ZSB0aGF0IGluIHNvbWUgY2FzZXMsIHRo
ZSANCj4gcmVjb21tZW5kZWQgZGlmZnNlcnYgY29kZSBwb2ludHMgd2VyZSBjaG9zZW4gdG8gaGF2
ZSB0aGUgc2FtZSBiaXQgDQo+IHBhdHRlcm4gYXMgdGhlIG9sZCBUb1MgcHJlY2VkZW5jZSBiaXRz
LiBUaGlzIHdhcyBkb25lIHNvIHRoYXQgaWYgDQo+IHBhY2tldHMgbWFya2VkIHdpdGggZGlmZnNl
cnYgY29kZSBwb2ludHMgaGFwcGVuZWQgdG8gcGFzcyB0aHJvdWdoIGEgDQo+IGxlZ2FjeSByb3V0
ZXIgdGhhdCBzdXBwb3J0ZWQgdGhlIFRvUyBiaXRzLCB0aGUgcmVzdWx0cyB3b3VsZCBiZSANCj4g
cmVhc29uYWJsZS4gSG93ZXZlciwgZGlmZnNlcnYgY29kZSBwb2ludHMgYXJlIGluIGZhY3QgZGVm
aW5lZCBhcyANCj4gb3BhcXVlIDYtYml0IHZhbHVlcy4gVGhlIGFib3ZlIHJlZmVyZW5jZXMgc2hv
dWxkIG1ha2UgdGhpcyBjbGVhci4NCj4gDQo+IEluIHN1bW1hcnkgbXkgc3VnZ2VzdGlvbiBpcw0K
PiAxKSB1c2UgNiBiaXRzDQo+IDIpIHN0YXRlIHRoYXQgdGhleSBhcmUgdG8gYmUgaW50ZXJwcmV0
ZWQgZXhhY3RseSBsaWtlIHRoZSBEU0NQIGRlZmluZWQgDQo+IGluIFJGQyAyNDc0DQo+IDMpIHRo
aXMgc2ltcGxpZmllcyB0aGUgcXVlc3Rpb24gb2YgbWFwcGluZyBiZXR3ZWVuIHRoZSB2eGxhbiBo
ZWFkZXIgDQo+IGFuZCB0aGUgSVAgaGVhZGVyLCB3aGVuIG5lZWRlZC4NCj4gNCkgaXQgd291bGQg
YWxzbyBzaW1wbGlmeSBpbnRlcndvcmtpbmcgd2l0aCB0aGUgUW9TIG1vZGVsIGZvciBXZWJSVEMg
DQo+IHRoYXQgaXMgdW5kZXIgZGV2ZWxvcG1lbnQuDQo+IA0KPiBSZWdhcmRzDQo+ICAgICBCcmlh
bg0KPiANCj4gPg0KPiA+IEJyaWFuDQo+ID4NCj4gPiBPbiAyNS8xMC8yMDE0IDA4OjE2LCBpbnRl
cm5ldC1kcmFmdHNAaWV0Zi5vcmcgd3JvdGU6DQo+ID4+IEEgTmV3IEludGVybmV0LURyYWZ0IGlz
IGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyANCj4gPj4gZGlyZWN0
b3JpZXMuDQo+ID4+DQo+ID4+DQo+ID4+IFRpdGxlICAgICAgICAgICA6IFF1YWxpdHkgb2YgU2Vy
dmljZSBNYXJraW5nIGluIFZpcnR1YWwNCj4gPj4gZVh0ZW5zaWJsZSBMb2NhbCBBcmVhIE5ldHdv
cmsgQXV0aG9ycyAgICAgICAgIDogRnJhbmsgWGlhDQo+ID4+IEJlaGNldCBTYXJpa2F5YSBGaWxl
bmFtZSAgICAgICAgOg0KPiA+PiBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwLnR4
dCBQYWdlcyAgICAgICAgICAgOiA5DQo+ID4+IERhdGUgICAgICAgICAgICA6IDIwMTQtMTAtMjQN
Cj4gPj4NCj4gPj4gQWJzdHJhY3Q6IFRoZSBWaXJ0dWFsIGVYdGVuc2libGUgTG9jYWwgQXJlYSBO
ZXR3b3JrIGVuYWJsZXMgDQo+ID4+IG11bHRpcGxlIHRlbmFudHMgdG8gb3BlcmF0ZSBpbiBhIGRh
dGEgY2VudGVyLiAgRWFjaCB0ZW5hbnQgbmVlZHMgdG8gDQo+ID4+IGJlIGFzc2lnbmVkIGEgcHJp
b3JpdHkgZ3JvdXAgdG8gcHJpb3JpdGl6ZSB0aGVpciB0cmFmZmljLiAgQ2xvdWQgDQo+ID4+IGNh
cnJpZXJzIHdpc2ggdG8gdXNlIHF1YWxpdHkgb2Ygc2VydmljZSB0byBkaWZmZXJlbnRpYXRlIGRp
ZmZlcmVudCANCj4gPj4gYXBwbGljYXRpb25zLiAgRm9yIHRoZXNlIHB1cnBvc2VzLCB0aHJlZSBi
aXRzIGFyZSBhc3NpZ25lZCBpbiB0aGUgDQo+ID4+IGVYdGVuc2libGUgTG9jYWwgQXJlYSBOZXR3
b3JrIGhlYWRlci4gIEhvdyB0aGVzZSBiaXRzIGFyZSBhc3NpZ25lZCANCj4gPj4gYW5kIGFyZSBw
cm9jZXNzZWQgaW4gdGhlIG5ldHdvcmsgYXJlIGV4cGxhaW5lZCBpbiBkZXRhaWwuDQo+ID4+DQo+
ID4+DQo+ID4+IFRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0
IGlzOg0KPiA+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC14aWEtbnZv
My12eGxhbi1xb3NtYXJraW5nLw0KPiA+Pg0KPiA+Pg0KPiA+PiBUaGVyZSdzIGFsc28gYSBodG1s
aXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj4gPj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMA0KPiA+Pg0KPiA+Pg0KPiA+Pg0K
PiA+PiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJv
bSB0aGUgdGltZSBvZiANCj4gPj4gc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lv
biBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IA0KPiA+PiB0b29scy5pZXRmLm9yZy4NCj4gPj4N
Cj4gPj4gSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQ
IGF0Og0KPiA+PiBmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KPiA+Pg0KPiA+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiBJ
LUQtQW5ub3VuY2UgbWFpbGluZyBsaXN0IEktRC1Bbm5vdW5jZUBpZXRmLm9yZyANCj4gPj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCj4gPj4gSW50
ZXJuZXQtRHJhZnQgZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwg
b3IgDQo+ID4+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+ID4+
DQo+ID4NCg0K


From nobody Mon Oct 27 07:08:45 2014
Return-Path: <rrs@netflix.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F791A88C2 for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 11:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 rbxEkCQhvs2g for <tsvwg@ietfa.amsl.com>; Fri, 24 Oct 2014 11:26:36 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61BD91A1B3B for <tsvwg@ietf.org>; Fri, 24 Oct 2014 11:26:36 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kx10so1602414pab.12 for <tsvwg@ietf.org>; Fri, 24 Oct 2014 11:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=6cnr9MPay/aYPw2e/p1V6EwBy7WRa8CC38QuFtn0UEs=; b=bDqaA7vYmWn2a2QpjsRxy0K/xosTIjXdkiVmgsOXLRyIWkq+hdz07iBlRZuZFA3iED B6m6h+bgTfzQUSk7eG3KQ8eDzMDSzhyBXkTO/pebMunufydyzJrjTWLZxkZHOKBlD8u3 B2SafzyYggTo6sV0admkVzAVGVLIN5ZLMX2Ds=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=6cnr9MPay/aYPw2e/p1V6EwBy7WRa8CC38QuFtn0UEs=; b=P6qMgRBvzfaS/Q8EZhX7y6NNadLFYdfT9/wWWg4thKG6Xf7e5XTBojyFUH6Y+EPG4n wjzQl8qoFBjyfv7AwAo+xNQ4nvFi3JCWkDYBjEXO8yIgbF0dPlR5AXYmFbmT2pklZJC4 6BA12YPEluL6yxe1gwYcU0nczA+ESJeocpYf3xPHBEjfzCJSxq4Hkpti0+qAnHa2EXT1 lxB2skr/k6HncunTn7noRHMdYyTzKzyn4oWpZgC8/Ki9AWwUoQuZhCgOZyCanpqrmUrw SEB4RKqPLK4xihVc0A66iEbLYi6s1TcI4sBIl+W6uBmjHq8vrR7+cCjIFuy3IUM1wJjy GUFA==
X-Gm-Message-State: ALoCoQnXbJCelU6wGfuUKhr/HFaYK7tH9KFz+ijIbTEb6mlaX8+71fL7Jf5+rOCsDnU65kjILWAF
X-Received: by 10.66.221.198 with SMTP id qg6mr6505895pac.106.1414175196002; Fri, 24 Oct 2014 11:26:36 -0700 (PDT)
Received: from [172.26.55.228] (65-121-190-41.dia.static.qwest.net. [65.121.190.41]) by mx.google.com with ESMTPSA id v10sm4420985pbs.64.2014.10.24.11.26.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 11:26:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_86CBC99F-4210-4F87-90D1-FDD7A897A184"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Randall Stewart <rrs@netflix.com>
In-Reply-To: <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com>
Date: Fri, 24 Oct 2014 11:26:32 -0700
Message-Id: <4E31BB93-2CC7-4CE5-9A90-B2927954C8B8@netflix.com>
References: <53861d39c85fd6a2ac78445cbd46194e@mail.gmail.com> <E5DF7AFB-454F-4AD1-B940-3A94CFE56F70@lurchi.franken.de> <20141023112711.GA3853@openss7.org> <a5984dc3eebd84385f8811176b0698f2@mail.gmail.com> <20141023120042.GB3853@openss7.org> <9ef9ee3eccd4bc22f63b18359048d39a@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/f7snPtWGmIs0Er0FFI4AiBZwT6E
X-Mailman-Approved-At: Mon, 27 Oct 2014 07:07:12 -0700
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, bidulock@openss7.org, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP mis indication counting during Fast Recovery
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 18:26:38 -0000
X-List-Received-Date: Fri, 24 Oct 2014 18:26:38 -0000

--Apple-Mail=_86CBC99F-4210-4F87-90D1-FDD7A897A184
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 24, 2014, at 1:11 AM, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:

> Hi Brian, Randy, Michael
>=20
> Michael, Randy: I dont't know if you have the time to look at the
> "tiresome" questions below .. :-)
>=20
> Thanks.
>=20
>=20
>>>>=20
>>>> Is there a reason would make it necessary to track the fast =
recovery
>>>> exit point?
>>>>=20
>>> [Karen] I am not sure that I understand how to implement SCTP FR
>>> without tracking the exit point.
>>=20
>> The first three sentences describe how to implement SCTP FR without
>> tracking the exit point.  As I understand it, The purpose of the exit
> point in
>> TCP was to limit the number of packets in flight (because TCP cwnd
> tracks
>> bytes not packets).  Because SCTP cwnd indirectly limits packets in
> flight all
>> day long, the TCP FR cwnd adjustments are not necessary, thus in SCTP
>> tracking the FR exit point is not necessary.
>>=20
> [Karen]
>=20
> I this really true ?  (I thought this was more about =
inflating/deflating
> and all that TCP CC business)
>=20
> You would need to maintain a FR exit point to control
> the CWND handling during and after FR. Also in order to know when to =
take
> or not
> take yet a CWND/2 hit (i.e., exit and re-enter of FR).
>=20
> Here one may give the side note that the RFC4960 spec is not clear on =
the
> boundary condition when FR is existed and
> CWND ramp up should commerce.
>=20
> TCP RCF 5681 is more clear in its formulation that:
>=20
> *CWND should not be ramped up during FR
> *At exit of FR, TCP is in congestion avoidance state
> *The slow start algorithm is used when cwnd < ssthresh, while the
>   congestion avoidance algorithm is used when cwnd > ssthresh.  When
>   cwnd and ssthresh are equal, the sender may use either slow start or
>   congestion avoidance.
>=20
> In RFC4960 there is no clear specification of the CC operation at exit =
of
> FR and it thus is not
> clear whether the prescription to be in CA at exit of FR is assumed to =
be
> inherited from TCP or not.
>=20
> It would be interesting to know if it is meant to be left to
> implementations to start in slow start or in CA after FR exit ?
> (I do realize that the CC state will transfer to CA as soon as the =
CWND
> gest ramped up).
>=20
> Still there should be no question that during FR, the CWND and
> partial_bytes_ack is not increased.
> Correct ?

Right

While you are recovering a FastRetransmit.. your not going to increase =
PBA or the CWND..

R

>=20
> Thanks
>=20
> BR, Karen
>=20
>=20
>> --
>> Brian F. G. Bidulock
>> bidulock@openss7.org
>> http://www.openss7.org/

--------
Randall Stewart
rrs@netflix.com
803-317-4952






--Apple-Mail=_86CBC99F-4210-4F87-90D1-FDD7A897A184
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Oct 24, 2014, at 1:11 AM, Karen =
Elisabeth Egede Nielsen &lt;<a =
href=3D"mailto:karen.nielsen@tieto.com">karen.nielsen@tieto.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi Brian, Randy, Michael<br><br>Michael, Randy: I dont't =
know if you have the time to look at the<br>"tiresome" questions below =
.. :-)<br><br>Thanks.<br><br><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><br>Is there a reason would make =
it necessary to track the fast recovery<br>exit =
point?<br><br></blockquote>[Karen] I am not sure that I understand how =
to implement SCTP FR<br>without tracking the exit =
point.<br></blockquote><br>The first three sentences describe how to =
implement SCTP FR without<br>tracking the exit point. &nbsp;As I =
understand it, The purpose of the exit<br></blockquote>point =
in<br><blockquote type=3D"cite">TCP was to limit the number of packets =
in flight (because TCP cwnd<br></blockquote>tracks<br><blockquote =
type=3D"cite">bytes not packets). &nbsp;Because SCTP cwnd indirectly =
limits packets in<br></blockquote>flight all<br><blockquote =
type=3D"cite">day long, the TCP FR cwnd adjustments are not necessary, =
thus in SCTP<br>tracking the FR exit point is not =
necessary.<br><br></blockquote>[Karen]<br><br>I this really true ? =
&nbsp;(I thought this was more about inflating/deflating<br>and all that =
TCP CC business)<br><br>You would need to maintain a FR exit point to =
control<br>the CWND handling during and after FR. Also in order to know =
when to take<br>or not<br>take yet a CWND/2 hit (i.e., exit and re-enter =
of FR).<br><br>Here one may give the side note that the RFC4960 spec is =
not clear on the<br>boundary condition when FR is existed and<br>CWND =
ramp up should commerce.<br><br>TCP RCF 5681 is more clear in its =
formulation that:<br><br>*CWND should not be ramped up during FR<br>*At =
exit of FR, TCP is in congestion avoidance state<br>*The slow start =
algorithm is used when cwnd &lt; ssthresh, while the<br> =
&nbsp;&nbsp;congestion avoidance algorithm is used when cwnd &gt; =
ssthresh. &nbsp;When<br> &nbsp;&nbsp;cwnd and ssthresh are equal, the =
sender may use either slow start or<br> &nbsp;&nbsp;congestion =
avoidance.<br><br>In RFC4960 there is no clear specification of the CC =
operation at exit of<br>FR and it thus is not<br>clear whether the =
prescription to be in CA at exit of FR is assumed to be<br>inherited =
from TCP or not.<br><br>It would be interesting to know if it is meant =
to be left to<br>implementations to start in slow start or in CA after =
FR exit ?<br>(I do realize that the CC state will transfer to CA as soon =
as the CWND<br>gest ramped up).<br><br>Still there should be no question =
that during FR, the CWND and<br>partial_bytes_ack is not =
increased.<br>Correct =
?<br></blockquote><div><br></div><div>Right</div><div><br></div><div>While=
 you are recovering a FastRetransmit.. your not going to increase PBA or =
the CWND..</div><div><br></div><div>R</div><br><blockquote =
type=3D"cite"><br>Thanks<br><br>BR, Karen<br><br><br><blockquote =
type=3D"cite">--<br>Brian F. G. Bidulock<br><a =
href=3D"mailto:bidulock@openss7.org">bidulock@openss7.org</a><br>http://ww=
w.openss7.org/<br></blockquote></blockquote></div><br><div =
apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>--------</div><div>Randall Stewart</div><div><a =
href=3D"mailto:rrs@netflix.com">rrs@netflix.com</a></div><div>803-317-4952=
</div><div><br></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_86CBC99F-4210-4F87-90D1-FDD7A897A184--


From nobody Mon Oct 27 07:08:47 2014
Return-Path: <xiayangsong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F811A879B; Sat, 25 Oct 2014 04:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fzgznRojoTEV; Sat, 25 Oct 2014 04:13:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 183EC1A879A; Sat, 25 Oct 2014 04:13:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKX69065; Sat, 25 Oct 2014 11:13:10 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 25 Oct 2014 12:13:07 +0100
Received: from NKGEML503-MBX.china.huawei.com ([169.254.5.225]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Sat, 25 Oct 2014 19:13:04 +0800
From: Xiayangsong <xiayangsong@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: I-D Action: draft-xia-nvo3-vxlan-qosmarking-00.txt
Thread-Index: AQHP7+4v9fpxR/1h2EmSavyoF8P64JxAAlvg//+mZoCAAPsV0A==
Date: Sat, 25 Oct 2014 11:13:03 +0000
Message-ID: <CB60645E6241144CB82269604373757A603D42D9@nkgeml503-mbx.china.huawei.com>
References: <20141024191612.9331.19202.idtracker@ietfa.amsl.com> <544AF4AD.50503@gmail.com> <CB60645E6241144CB82269604373757A603D4009@nkgeml503-mbx.china.huawei.com> <544B1EEF.7040002@gmail.com>
In-Reply-To: <544B1EEF.7040002@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/yXOZx0nGQmkRtDlZDH1HMQ-ASCE
X-Mailman-Approved-At: Mon, 27 Oct 2014 07:07:13 -0700
Cc: "nvo3-chairs@tools.ietf.org" <nvo3-chairs@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org" <draft-xia-nvo3-vxlan-qosmarking@tools.ietf.org>
Subject: [tsvwg] =?utf-8?b?562U5aSNOiBJLUQgQWN0aW9uOiBkcmFmdC14aWEtbnZv?= =?utf-8?q?3-vxlan-qosmarking-00=2Etxt?=
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Oct 2014 11:13:25 -0000

SGkgIEJyaWFuDQoNClRoYW5rIGZvciB5b3VyIGNvbnN0cnVjdGl2ZSBzdWdnZXN0aW9uLg0KDQpQ
bGVhc2Ugc2VlIG15IGlubGluZSByZXNwb25zZS4NCg0KVGhhbmtzDQpGcmFuaw0KDQotLS0tLemC
ruS7tuWOn+S7ti0tLS0tDQrlj5Hku7bkuro6IEJyaWFuIEUgQ2FycGVudGVyIFttYWlsdG86YnJp
YW4uZS5jYXJwZW50ZXJAZ21haWwuY29tXSANCuWPkemAgeaXtumXtDogMjAxNOW5tDEw5pyIMjXm
l6UgMTE6NTQNCuaUtuS7tuS6ujogWGlheWFuZ3NvbmcNCuaKhOmAgTogdHN2d2dAaWV0Zi5vcmc7
IGRyYWZ0LXhpYS1udm8zLXZ4bGFuLXFvc21hcmtpbmdAdG9vbHMuaWV0Zi5vcmc7IG52bzMtY2hh
aXJzQHRvb2xzLmlldGYub3JnOyBudm8zQGlldGYub3JnDQrkuLvpopg6IFJlOiBJLUQgQWN0aW9u
OiBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwLnR4dA0KDQpIaSwNCg0KT24gMjUv
MTAvMjAxNCAxNDozNywgWGlheWFuZ3Nvbmcgd3JvdGU6DQo+IEhpIEJyaWFuDQo+IA0KPiBUaGFu
a3MgZm9yIHlvdXIgYXR0ZW50aW9uIG9uIHRoaXMgdG9waWMuIEkgYW0gYW4gZW5naW5lZXIgbm90
IGEgDQo+IHN0YW5kYXJkICBndXkgLiBJIGRpc2N1c3NlZCB0aGlzIGlkZWEgd2l0aCBCZWhjZXQg
d2hvIGtpbmRseSBwdXQgbWUgYXMgDQo+IHRoZSBmaXJzdCBhdXRob3IuDQo+IA0KPiBTbyBJIHRy
eSB0byByZXNwb25kIHlvdSBmcm9tIGVuZ2luZWVyaW5nIHBlcnNwZWN0aXZlLg0KDQpVbmRlcnN0
b29kLCBidXQgSUVURiBzdGFuZGFyZHMgYXJlIHN1cHBvc2VkIHRvIGNvcnJlc3BvbmQgdG8gcmVh
bCBlbmdpbmVlcmluZywgc28gdGhhdCBpcyBubyBwcm9ibGVtLg0KDQo+IA0KPiBUaGFua3MgRnJh
bmsNCj4gDQo+IC0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0g5Y+R5Lu25Lq6OiBCcmlhbiBFIENhcnBl
bnRlcg0KPiBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0g5Y+R6YCB5pe26Ze0
OiAyMDE05bm0MTDmnIgyNeaXpSA4OjU0IOaUtg0KPiDku7bkuro6IHRzdndnQGlldGYub3JnOw0K
PiBkcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nQHRvb2xzLmlldGYub3JnOw0KPiBudm8z
LWNoYWlyc0B0b29scy5pZXRmLm9yZyDkuLvpopg6IFJlOiBJLUQgQWN0aW9uOg0KPiBkcmFmdC14
aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwLnR4dA0KPiANCj4gSGksDQo+IA0KPiBUaGlzIGRy
YWZ0IG5lZWRzIHRvIGJlIGRpc2N1c3NlZCBpbiB0c3Z3ZyBJIHRoaW5rLiBJdCBoYXMgc29tZSAN
Cj4gc2lnbmlmaWNhbnQgcHJvYmxlbXMgSU1ITzoNCj4gDQo+IDEuIEl0IGNvbmZ1c2VzIFFvUyBh
bmQgcHJpb3JpdHkgaW4gYSBzdHJhbmdlIHdheS4gDQoNCj4gRnJhbms9PlFvUw0KPiBpcyBhYm91
dCBwYWNrZXQgbG9zcywgYmFuZHdpZHRoLCBsYXRlbmN5IGFuZCBqaXR0ZXIuDQoNClRob3NlIGFy
ZSB0aGUgdXN1YWwgUW9TIG1ldHJpY3Mgb2YgY291cnNlLg0KDQo+IEJhbmR3aWR0aCBjYW4gYmUg
Y29udHJvbGxlciBieSBDQVIgdGVjaG5vbG9neS4gQXMgZm9yIGxhdGVuY3kgYW5kIA0KPiBqaXR0
ZXIsIHRoZXkgYXJlIGtpbmQgb2YgaW5oZXJlbnQgcGFyYW1ldGVyIG9mIGEgZ2l2ZW4gbmV0d29y
aywgYW5kIA0KPiB0aGVyZSBpcyBoYXJkbHkgYSB3YXkgdG8gY29udHJvbGxlciB0aGVtIC4NCj4g
VGh1cywgaW4gbW9zdCBzY2VuYXJpbywgUW9TIGlzIGFib3V0IHBhY2tldCBsb3NzIGNvbnRyb2wg
d2hpY2ggaXMgIA0KPiBiYXNlZCBvbiBwcmlvcml0eS4NCg0KSSBzdWdnZXN0IGNhcmVmdWxseSBy
ZXZpZXdpbmcgUkZDIDI0NzQgYW5kIFJGQyAyNDc1LCBhbmQgdGhlIHNwZWNpZmljIGRlc2NyaXB0
aW9ucyBvZiBwZXItaG9wIGJlaGF2aW91cnMgaW4gUkZDIDI1OTcgYW5kIFJGQyAzMjQ2LiBBbHNv
IGl0IGlzIHdvcnRoIHJldmlld2luZyBSRkMgNDU5NCwgZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vy
di1pbnRlcmNvbiwgYW5kIHRoZSB3b3JrIG9mIHRoZSBBUU0gV0cgKGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy93Zy9hcW0vY2hhcnRlci8pLiBUcnVseSB0aGVyZSBpcyBhIGxvdCBtb3JlIHRv
IHF1ZXVlIG1hbmFnZW1lbnQgdGhhbiBzaW1wbGUgcHJpb3JpdHkuDQoNCg0KRnJhbms9PlRoYW5r
IGZvciB0aGUgaW5zdHJ1Y3Rpb24sIGFuZCBJIHdpbGwgc3R1ZHkgdGhyb3VnaCB0aGVzZSBkb2N1
bWVudHMgLg0KDQo+IDIuIEl0IHJlcGVhdHMgdGhlIE1QTFMgZXJyb3Igb2YgdHJ5aW5nIHRvIGV4
cHJlc3Mgc2VydmljZSANCj4gZGlmZmVyZW50aWF0aW9uIGluIDMgYml0cy4NCg0KDQo+IEZyYW5r
PT5JIGRvbid0IGtub3cgdGhlIE1QTFMNCj4gZXJyb3IsIHBsZWFzZSB0ZWFjaCBtZS4gIEhvd2V2
ZXIsIGluIGVuZ2luZWVyaW5nIGFyZWEsIE1QTFMgMyBiaXQgaGFzIA0KPiBhIHByYWdtYXRpYyBw
dXJwb3NlLiAgWW91IGNhbiBjaGVjayBzd2l0Y2hlcy9yb3V0ZXJzIHNwZWNpZmljYXRpb24gDQo+
IGZyb20gZGlmZmVyZW50IHZlbmRvcnMgYWJvdXQgdGhpcy4NCg0KVGhlIHByb2JsZW0gaXMgdGhh
dCByZS11c2luZyB0aGUgdGhyZWUgRVhQIChleHBlcmltZW50YWwpIGJpdHMgaW4gTVBMUyBmb3Ig
cXVhbGl0eSBvZiBzZXJ2aWNlIHNpZ25hbGxpbmcgd2FzIGFuIGFmdGVydGhvdWdodC4NClRocmVl
IGJpdHMgc2ltcGx5IGlzbid0IGVub3VnaCB0byBleHByZXNzIGEgcmVhc29uYWJsZSByYW5nZSBv
ZiBzZXJ2aWNlIGNsYXNzZXMuIFVuZm9ydHVuYXRlbHkgaXQgaXMgYWxsIHdlIGhhdmUgaW4gTVBM
UywgYnV0IHRoYXQgaXMgbm90IGEgdmFsaWQgcmVhc29uIGZvciBjb3B5aW5nIHRoZSBzYW1lIG1p
c3Rha2UuIElmIHlvdSBhZG9wdCA2IGJpdHMsIGl0IHNob3VsZCBiZSBmYWlybHkgZWFzeSB0byBh
ZG9wdCB0aGUgd2hvbGUgZGlmZnNlcnYgbW9kZWwuIFRoYXQgd291bGQgc2F2ZSBhIGxvdCBvZiB3
b3JrLCBib3RoIGluIHNwZWNpZmljYXRpb24gYW5kIGluIGltcGxlbWVudGF0aW9uLg0KDQoNCkZy
YW5rPT51bmRlcnN0b29kLg0KDQo+IA0KPiAzLiBJdCBtYWtlcyBhIGNvbXBsZXRlbHkgaW5hY2N1
cmF0ZSBzdGF0ZW1lbnQgYWJvdXQgZGlmZnNlcnY6DQo+ICAiVGhlIGZpcnN0IHRocmVlIGJpdHMg
b2YgRFMgZmllbGQgYXJlIHVzZWQgZm9yIElQIHByZWNlZGVuY2UgYW5kIHRoZSANCj4gbGFzdCB0
aHJlZSBhcmUgdXNlZCBhcyBkaWZmIHNlcnYgYml0cy4iDQoNCg0KPiBGcmFuaz0+SQ0KPiBndWVz
cyB0aGUgc3RhdGVtZW50IHdhcyBjb3BpZWQgZnJvbSBzb21lIFJGQywgYW5kIEkgd291bGQgZG91
YmxlIGNoZWNrIA0KPiBpdC4NCg0KSWYgc28sIHRoYXQgUkZDIGlzIHdyb25nLiBJdCBpcyB0cnVl
IHRoYXQgaW4gc29tZSBjYXNlcywgdGhlIHJlY29tbWVuZGVkIGRpZmZzZXJ2IGNvZGUgcG9pbnRz
IHdlcmUgY2hvc2VuIHRvIGhhdmUgdGhlIHNhbWUgYml0IHBhdHRlcm4gYXMgdGhlIG9sZCBUb1Mg
cHJlY2VkZW5jZSBiaXRzLiBUaGlzIHdhcyBkb25lIHNvIHRoYXQgaWYgcGFja2V0cyBtYXJrZWQg
d2l0aCBkaWZmc2VydiBjb2RlIHBvaW50cyBoYXBwZW5lZCB0byBwYXNzIHRocm91Z2ggYSBsZWdh
Y3kgcm91dGVyIHRoYXQgc3VwcG9ydGVkIHRoZSBUb1MgYml0cywgdGhlIHJlc3VsdHMgd291bGQg
YmUgcmVhc29uYWJsZS4gSG93ZXZlciwgZGlmZnNlcnYgY29kZSBwb2ludHMgYXJlIGluIGZhY3Qg
ZGVmaW5lZCBhcyBvcGFxdWUgNi1iaXQgdmFsdWVzLiBUaGUgYWJvdmUgcmVmZXJlbmNlcyBzaG91
bGQgbWFrZSB0aGlzIGNsZWFyLg0KDQoNCkZyYW5rPT51bmRlcnN0b29kLg0KDQpJbiBzdW1tYXJ5
IG15IHN1Z2dlc3Rpb24gaXMNCjEpIHVzZSA2IGJpdHMNCkZyYW5rPT5JIGFtIG5vdCBzdXJlLiAg
VnhMQU4gaXMgYSBNQUMgb3ZlciBVRFAgdGVjaG5vbG9neSwgYW5kIGl0IGlzIGZvciBlbXVsYXRp
bmcgRXRoZXJuZXQgbGluayBsYXllciB0aHJvdWdoIHVuZGVybHlpbmcgIElQIGluZnJhc3RydWN0
dXJlLiAgDQpJRUVFIDgwMi4xcSBzcGVjaWZpZXMgMyBiaXRzIGZvciBkaWZmZXJlbnRpYXRpbmcg
Q2xhc3Mgb2YgU2VydmljZSAoQ29TKS4gIFRoZXNlIDMgYml0cyBhcmUgIG9uZS10by1vbmUgIG1h
cHBlZCAgdG8gIFZ4TEFOIGVuY2Fwc3VsYXRpb24uDQpJIGRvbid0IGtub3cgaG93IGZpbGwgdGhl
IG90aGVyIDMgYml0cyBpZiB1c2luZyA2IGJpdHMgZm9yIFZ4TEFOIFFvUy4NCg0KMikgc3RhdGUg
dGhhdCB0aGV5IGFyZSB0byBiZSBpbnRlcnByZXRlZCBleGFjdGx5IGxpa2UgdGhlIERTQ1AgZGVm
aW5lZCBpbiBSRkMgMjQ3NA0KMykgdGhpcyBzaW1wbGlmaWVzIHRoZSBxdWVzdGlvbiBvZiBtYXBw
aW5nIGJldHdlZW4gdGhlIHZ4bGFuIGhlYWRlciBhbmQgdGhlIElQIGhlYWRlciwgd2hlbiBuZWVk
ZWQuDQo0KSBpdCB3b3VsZCBhbHNvIHNpbXBsaWZ5IGludGVyd29ya2luZyB3aXRoIHRoZSBRb1Mg
bW9kZWwgZm9yIFdlYlJUQyB0aGF0IGlzIHVuZGVyIGRldmVsb3BtZW50Lg0KDQpSZWdhcmRzDQog
ICAgQnJpYW4NCg0KPiANCj4gQnJpYW4NCj4gDQo+IE9uIDI1LzEwLzIwMTQgMDg6MTYsIGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZyB3cm90ZToNCj4+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2
YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyANCj4+IGRpcmVjdG9yaWVz
Lg0KPj4gDQo+PiANCj4+IFRpdGxlICAgICAgICAgICA6IFF1YWxpdHkgb2YgU2VydmljZSBNYXJr
aW5nIGluIFZpcnR1YWwNCj4+IGVYdGVuc2libGUgTG9jYWwgQXJlYSBOZXR3b3JrIEF1dGhvcnMg
ICAgICAgICA6IEZyYW5rIFhpYSANCj4+IEJlaGNldCBTYXJpa2F5YSBGaWxlbmFtZSAgICAgICAg
Og0KPj4gZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy0wMC50eHQgUGFnZXMgICAgICAg
ICAgIDogOSANCj4+IERhdGUgICAgICAgICAgICA6IDIwMTQtMTAtMjQNCj4+IA0KPj4gQWJzdHJh
Y3Q6IFRoZSBWaXJ0dWFsIGVYdGVuc2libGUgTG9jYWwgQXJlYSBOZXR3b3JrIGVuYWJsZXMgbXVs
dGlwbGUgDQo+PiB0ZW5hbnRzIHRvIG9wZXJhdGUgaW4gYSBkYXRhIGNlbnRlci4gIEVhY2ggdGVu
YW50IG5lZWRzIHRvIGJlIA0KPj4gYXNzaWduZWQgYSBwcmlvcml0eSBncm91cCB0byBwcmlvcml0
aXplIHRoZWlyIHRyYWZmaWMuICBDbG91ZCANCj4+IGNhcnJpZXJzIHdpc2ggdG8gdXNlIHF1YWxp
dHkgb2Ygc2VydmljZSB0byBkaWZmZXJlbnRpYXRlIGRpZmZlcmVudCANCj4+IGFwcGxpY2F0aW9u
cy4gIEZvciB0aGVzZSBwdXJwb3NlcywgdGhyZWUgYml0cyBhcmUgYXNzaWduZWQgaW4gdGhlIA0K
Pj4gZVh0ZW5zaWJsZSBMb2NhbCBBcmVhIE5ldHdvcmsgaGVhZGVyLiAgSG93IHRoZXNlIGJpdHMg
YXJlIGFzc2lnbmVkIA0KPj4gYW5kIGFyZSBwcm9jZXNzZWQgaW4gdGhlIG5ldHdvcmsgYXJlIGV4
cGxhaW5lZCBpbiBkZXRhaWwuDQo+PiANCj4+IA0KPj4gVGhlIElFVEYgZGF0YXRyYWNrZXIgc3Rh
dHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6IA0KPj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQteGlhLW52bzMtdnhsYW4tcW9zbWFya2luZy8NCj4+IA0KPj4gDQo+PiBU
aGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDogDQo+PiBodHRwOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14aWEtbnZvMy12eGxhbi1xb3NtYXJraW5nLTAwDQo+
PiANCj4+IA0KPj4gDQo+PiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9m
IG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiANCj4+IHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxp
emVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCANCj4+IHRvb2xzLmlldGYub3Jn
Lg0KPj4gDQo+PiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91
cyBGVFAgYXQ6IA0KPj4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4+IA0K
Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IEkt
RC1Bbm5vdW5jZSBtYWlsaW5nIGxpc3QgSS1ELUFubm91bmNlQGlldGYub3JnIA0KPj4gaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCj4+IEludGVybmV0
LURyYWZ0IGRpcmVjdG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sIG9yIA0K
Pj4gZnRwOi8vZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQNCj4+IA0KPiANCg0K


From nobody Mon Oct 27 07:23:54 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016781A8736 for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UPVZUYX0WLfA for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:23:11 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id A40B81A8723 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 07:23:11 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 1D3242B44AD; Mon, 27 Oct 2014 14:23:11 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 402E92B4499; Mon, 27 Oct 2014 14:23:10 +0000 (GMT)
Message-ID: <544E554E.1000404@erg.abdn.ac.uk>
Date: Mon, 27 Oct 2014 14:23:10 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <543CD616.5090509@erg.abdn.ac.uk>
In-Reply-To: <543CD616.5090509@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/FeIidA-OfKsqu8tVUC4fXYeGbPU
Subject: Re: [tsvwg] WGLC draft-ietf-tsvwg-port-use-05 : Working Group Last Call for comments due 29/10/2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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: Mon, 27 Oct 2014 14:23:15 -0000

A gentle reminder, that if you have comments on the updated ID, please 
do get back via the list by the deadline.

To date, Eliot has responded confirming he happy to see the updated 
document progress. Others please respond, especially if you commented 
during the first WGLC.

gorry


On 14/10/2014 08:51, Gorry Fairhurst wrote:
> This email announces the start of a working group last call to
> confirm publication of draft-ietf-tsvwg-port-use,
> "Recommendations for Transport Port Number Uses".  This document has
> received significant feedback during the first WGLC review and has now
> been updated in response to this feedback. It is now thought to be ready
> to proceed to be published as a BCP.
>
> Please send any comments to the TSVWG list. We are interested in feedback
> from any who have read the latest version, including those who commented
> in the first WGLC.
>
> The draft is available at:
> https://tools.ietf.org/html/draft-ietf-tsvwg-port-use-05
>
> This last call will run for TWO weeks, ending 29th October.
>
> James, David, and Gorry
> (TSVWG Chairs)
> tsvwg-chairs@ietf.org
>


From nobody Mon Oct 27 07:30:25 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E82321ACD62 for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.611
X-Spam-Level: 
X-Spam-Status: No, score=-3.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nb2XLeFQC9WU for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:29:37 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 420E21ACD47 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 07:29:36 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 944B22B44AD; Mon, 27 Oct 2014 14:29:35 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7A1602B4499 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 14:29:32 +0000 (GMT)
Message-ID: <544E56CC.2080300@erg.abdn.ac.uk>
Date: Mon, 27 Oct 2014 14:29:32 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Zsj-3SnQMp6Gk2pmhYDdMKqdCWU
Subject: [tsvwg] TSVWG Status Summary October 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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: Mon, 27 Oct 2014 14:29:44 -0000

The list below shows the status of the working group documents as we see 
it. Please check below and comment on drafts using the list. Please do 
send any corrections/omissions to the chairs.

Gorry, David & James
(TSVWG Chairs)
October 2014

-------------------------------------------------------------------
Document recently published:

None
-------------------------------------------------------------------
IDs in RFC Editor Queue (http://www.rfc-editor.org/queue.html) :

draft-ietf-tsvwg-rsvp-pcn - Document Shepherd: David

----------------------------------------------------------
IDs in IESG processing:
draft-ietf-tsvwg-sctp-prpolicies - PS - Document Shepherd: Gorry
Replaces: draft-tuexen-tsvwg-sctp-prpolicies
Nov 2013, Adopted SCTP PR Polices intended for publication as a PS RFC
March 2014, Next revision expected for WGLC.
Gorry read 20-May-2014, needs to be PS, explain Info section in wrietup
Revised ID May 2014.
1-Jul-2014 Gorry reviewed standards language
WGLC started to end July 21st, 2014
- support JHS, KN, MB, IR, GF; comments from Karen Nielson, Brian 
Bidulock, Gorry
Note: the socket API stuff, which is informational, is completely 
implemented in FreeBSD and will be released in FreeBSD 10.1
Revised ID after WGLC
All Authors responded to IPR check.
WG Shepherd write-up 27th Oct 2014

-------------------------------------------------------------------
New proposed work:
draft-eggert-tsvwg-rfc5405bis (adoption request soon)
draft-geib-tsvwg-diffserv-intercon-02.txt (next version expected to be 
called for adoption)

-------------------------------------------------------------------
WG Drafts with Chairs:
draft-ietf-tsvwg-sctp-dtls-encaps - PS - Document Shepherd: Gorry
Replaces: draft-tuexen-tsvwg-sctp-dtls-encaps-01
WG adopted 13/12/2013. Support {AB, IR, SL, MB, TD}
[Milestone: Jan 2014, PS] Implemented in Firefox (FF21).
Required by RTCweb. Comments received.
WGLC ended 28th February 2014.
Comments from Joe Touch (draft updated)
Review comments and revised ID published.
Eric Rescorla has reviewed this.
WAITING: Waiting for one author (R. Jesup) to confirm IPR
DUE: Security input needed to determine text describing DTLS version and 
how to deal with DTLS versioning.

---
draft-ietf-tsvwg-port-use - Document Shepherd: Gorry
Replaces: draft-touch-tsvwg-port-use-00
- Intended to be advice to protocol designers needing a port.
5 people looked at this document, Prague IETF-80
Individual -01 July 2011
IETF-81 insufficient feedback from WG at this time.
IETF-82, discussed.
Adopted by WG Presented IETF-86, March 2013
Milestone updated to June 2014
Mar 2014, Chairs WGLC to be started after current WG actions.
- IANA review comments received
- Sent review requests to RAI, APPS, and SEC areas during 1st WGLC.
+ Comments May 2014: Paul Hoffman; Lars Eggert; IANA; David Black;
5 Jun 2014, WGLC completed - comments received.
Revised ID after WGLC; Elliot OK with changes;
DUE:  Working Group Last Call for comments 14/10/2014, due to conclude 
29/10/2014

---
draft-ietf-tsvwg-sctp-failover - Document Shepherd: James (backup 
shepherd: gorry)
Replaces: draft-nishida-tsvwg-sctp-failover
Individual-00 Presented in Prague, IETF-80.
- Understood not to conflict with draft-tuexen-tsvwg-sctp-multipath
- PF has been implemented in FreeBSD; Linux SCTP implements partially, 
that they intend to implement full support and have no comments to the 
technical solution; Ericsson have an implementation;
Adopted by WG 26/6/2012. [Milestone: Jul 2013, EXP]
Thought ready for WGLC, four people volunteered to review.
Review done by GF with a view to the milestone becoming PS.
++ Committed reviewers : Michael Tuexen (more if possible)
Milestone update request to AD/IESG sent Oct 2014
Due: WGLC to be started in Nov 2014.

-------------------------------------------------------------------
WG Drafts
---
draft-ietf-tsvwg-rsvp-app-id-vv-profiles
Replaces: draft-polk-tsvwg-rsvp-app-id-vv-profiles
-01 Presented in Beijing, IETF-79.
-02, 14-Mar-2011
Presented IETF-80.
Seek to coordinate with music with partner ID:
draft-polk-mmusic-traffic-class-for-sdp
Gorry liaised with MMUSIC WG Chairs on companion draft (norm ref from 
this tsvwg draft).
Adopted as a TSVWG work item, December 2013, [Milestone Jul 2013].
This will update a RFC 2872 (PS).
Presented at IETF-86,
Mar 2013 (no comments)
Expected ready for WGLC (waiting on MMUSIC)
DUE: Reviewers are needed to prepare for a WGLC
---
draft-ietf-tsvwg-sctp-ndata - PS
- replaces: draft-stewart-tsvwg-sctp-ndata-03 Nov 2013,
Adopted , intended for publication as a PS RFC
Mar 2014, 5-6 people had read.
Named changed proposed at IETF-90 (Interleaved data?) and clarification 
of use-case.
DUE: Revised ID needed.
---
draft-tsvwg-gre-in-udp-encap - PS Document Shepherd: David
- replaces: draft-yong-tsvwg-gre-in-udp-encap
Dec 2013, Adopted , intended for publication as a PS RFC
Feb 2014, discussion of scope and applicability of circuit breakers
Mar 2014 consider MUST implement, SHOULD use in these environments for CB
DUE: Revised ID needed to address congestion control and UDP Zero 
Checksum for IPv6.  Revised text has been developed for MPLS-in-UDP 
draft, but needs adaptation and generalization for GRE (vs. MPLS).
DUE: Revised ID expected for Honolulu with initial adaptation - expect 
to discuss generalization in meeting.
---
draft-ietf-tsvwg-rtcweb-qos - PS - Document Shepherd: David
- Replaces: draft-dhesikan-tsvwg-rtcweb-qos
- RTCweb and QoS Markings
- Authors requested TSVWG adoption.
- Who has read the draft? (lots 10's of people)
25-Mar-2014, Adopted by tsvwg
- Who thinks it is important to do work in the IETF? (Many)
I-D updated after initial TSVWG feedback
Mar 2014, Adoption call (strong support in WG meeting London)
Adoption call concluded 24 Match 2014: intended as a PS RFC for Sept 2014
++ Magnus agreed to review this.
Early OPS-Dir review received from Fred Baker.
Oct 2014, DART draft (draft-ietf-dart-dscp-rtp): IETF LC completed, now 
in IESG evaluation.
DUE: Please comment on list, and see DART draft as related material.
---
draft-ietf-tsvwg-circuit-breaker - Document Shepherd: TBD
Call for WG adoption issued - August 2014, adopted 28th Aug.
Milestone set - Oct 2014 (by David Black)
DUE: Please comment on list

-------------------------------------------------------------------
Expired WG documents:

draft-ietf-tsvwg-ecn-encap-guidelines - Document Contact: Gorry
replaced draft-briscoe-tsvwg-ecn-encap-guidelines
-00 Presented in Prague, IETF-80.
- comments at IETF-80 (see minutes)
New ID presented in Atlanta, IETF-85. ID presented in IETF-88,89
++ forward an appropriate message (perhaps your note to the mailing list 
for approval to adopt) to ieee-ietf-coord@ietf.org)
++ Reviewers: Andrew McGregor, Dirk Kutscher, Richard Scheffnegger, 
Brian Tramwell.
Mar 2014, WG Call for adoption started, to end 4th March 2014
19 for, 1 against. 8 echoed on the list
Adoption call concluded and document adopted.
* ecn-encap-guidelines and AQM are the main new things they need to know 
about.
on <http://www.ietf.org/proceedings/86/train-3.html>IEEE802.1Q)
DUE: Please comment on list.
---
draft-ietf-tsvwg-intserv-multiple-tspec - Document Shepherd: David
WG interest in this topic recorded at IETF-78.
Charter update needed to progress this work.
5 Reviews needed to determine energy/technical direction.
WG -05 (presented in Beijing, IETF-79)
WG -06 (presented in Prague, IETF-80)
2 reviews from RSVP-DIR received (Bruce Davie, ?)
2 additional reviews promised (Ken Carlberg, Francois LeF)
Chairs asked AD for a Charter update (IESG agreed)
Draft discussed at IETF-80, and request to update charter agreed
- AD advised 4 named reviewers will be required
Adopted for progression as PS, for May 2012
- New name: 'RSVP Multiple Instance'.
Draft is now expired and dead.
DUE: Draft authors will request replacement with 
draft-polk-rsvp-multi-instance-object (and WG adoption of that draft in 
Honolulu, IETF-91)
---
draft-ietf-tsvwg-natsupp - Document Shepherd: James
Replaces: draft-stewart-natsupp-tsvwg
Dependency from BEHAVE WG.
Adopted as a work item 21 Sept 2010 (Gorry).
WG -00, 29/11/2010 Uploaded as: draft-ietf-natsupp-tsvwg
Authors restructured draft (-03)
Added support for single and multi-homed support.
IETF-86: 3 people in meeting had read -04 or -05.
Feb 2014, Authors please update following comments and align to related 
draft on SCTP NAT (conflicts found in language)
Authors expected to produce a single document to replace both.
++ Dan Wing has committed to review this.
++ Fred Baker has committed to review this.
Chairs: We plan to start a WGLC, but are expecting this document to be 
restructured and merged with draft-ietf-tsvwg-sctpnat
---
draft-ietf-tsvwg-sctpnat - Document Shepherd: Gorry
Will replace: draft-ietf-behave-sctpnat-03.txt Adopted Nov 2013.
Former BEHAVE WG work item that defines SCTP NAT support
Feb 2014, Authors please update following comments and align to related 
draft on SCTP NAT (conflicts found in language)
Chairs: - authors have requested a single document to replace both.
++ Fred Baker will review next version.
Separated the simpler case for single-homed use - this separation should 
be clearer
Chairs: We plan to start a WGLC, but are expecting this document to be 
restructured and merged with draft-ietf-tsvwg-sctpnat
---
draft-ietf-tsvwg-behave-requirements-update - Document Shepherd: David
Replaces: draft-ietf-behave-requirements-update-00
Nov 2013, Former BEHAVE WG work item intended for publication as a BCP
Mar 2014, Irene R reviewed this and found no conflict with SCTP drafts.
Some suggestions (in no particular order) for a shepherd:
++ Dave Thaler, may review, as former behave co-chair
++ David Harrington, has been around in behave, and he knows how to do 
this and volunteered multiple times.
++ Ask Jana to review this.
++ Dan has committed to review this.
Chairs: Check intention and planned timeline.
DUE: Please comment on list
---
-------------------------------------------------------------------
The following have received recent discussion at TSVWG meetings or on
the list. Inclusion in the list below does not indicate support for
these specific drafts and other contributions are also warmly welcomed.
---------------------------------------------------------------
Authors request to be considered for adoption
---
draft-geib-tsvwg-diffserv-intercon - Document Contact: David
DiffServ interconnection classes
New ID presented in Atlanta, IETF-85.
ID presented in Orlando, IETF-86, Mar 2013. Mar 2014, intended scope 
unclear at IETF London Adoption call to be considered, but scope needs 
to be first refined and a revised draft is necessary to avoid 
implications of broader applicability.
July 2014 - ID presented in Toronto. Strong hum of support to work on 
this, but a revised draft is needed first.
DUE: revised draft required, WG adoption call expected on that next version.
---
draft-eggert-tsvwg-rfc5405bis
- Individual (Gorry & Lars)
Mar 2014, the ADs proposed the WG re-open the UDP Guidelines RFC for 
update to include this work and other topics.
The authors of both drafts agreed to progress this work.
NOTE: Update milestone in charter, if adopted: ‘Multicast UDP 
Guidelines’ is being incorporated in this.
Presented IETF-90, Hum supporting adoption, none against.
++ Brian Tramwell and Jana agreed to review this.
Chairs:Adoption call to be started on list.
---
draft-wing-tsvwg-turn-flowdata-00.txt
- Individual (no decision to adopt at this time)
- QoS-aspects to be discussed in tsvwg (thought to also be relevant to 
TURN WG)
----
draft-wei-tsvwg-tunnel-congestion-feedback
- Thought to fall within TSVWG charter
--- draft-lai-tsvwg-normalizer
- Thought to fall within TSVWG charter
- Presented IETF-88 ---
draft-ohanlon-rmcat-dflow
Discussed at IETF-84, Vancouver
This draft is related to the new rmcat work.
Comments received on list prior to IETF-85. Comments IETF-90.
Authors request WG adoption at IETF-90
Request for people to read this ID, need more review comments.
DUE: Revised ID needed
---
draft-ietf-aqm-ecn-benefits
replaces draft-welzl-ecn-benefits, Individual (Michael Welzl)
- Thought to be within tsvwg or aqm WGs.
- Has been adopted as a work item in AQM, may be WGLC'ed in both.
- Please discuss on AQM WG List
---


From nobody Mon Oct 27 07:44:32 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 408121A8728 for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aL0M9xB_oVOc for <tsvwg@ietfa.amsl.com>; Mon, 27 Oct 2014 07:43:34 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3C61A8786 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 07:43:34 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 9E6792B44AD; Mon, 27 Oct 2014 14:43:33 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id EF7222B4499 for <tsvwg@ietf.org>; Mon, 27 Oct 2014 14:43:32 +0000 (GMT)
Message-ID: <544E5A14.404@erg.abdn.ac.uk>
Date: Mon, 27 Oct 2014 14:43:32 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
References: <20cdb5c72974b6bc98ab256d00baf36e.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <20cdb5c72974b6bc98ab256d00baf36e.squirrel@spey.erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/UNmYji_UweJbMUGodkMVjbZPFCg
Subject: [tsvwg] Change of intended publication status for draft-ietf-tsvwg-sctp-failover
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 14:43:40 -0000

This is a short note to confirm the change in the milestone for the 
intended publication status for draft-ietf-tsvwg-sctp-failover from EXP 
to PS.

There are several important changes that have taken place within the WG
that motivate this proposed change of status, and these were discussed 
at the TSVWG meeting in Toronto and on the list. Nobody objected to the
change.

The changes are:

1)  The reason that it was proposed as experimental was due to that the 
work initially looked to address some more fundamental changes to the CC
operation of SCTP.

These intended changes are no longer part of the specification and
consequently the spec is fully aligned with the CC operation as 
specified in RFC4960.

2) In addition there might have been some concerns about the possibility 
for this mechanism to introducing path bouncing with potential harmful 
network impacts. These concerns, however, are believed to be unfounded 
as addressed in Appendix B

We expect this document to shortly sent for WGLC.

Gorry
(TSVWG Co-Chair)



From nobody Mon Oct 27 14:54:55 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC601A00F9; Mon, 27 Oct 2014 14:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 e3IG5klJLR-J; Mon, 27 Oct 2014 14:54:35 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F1BE41A016F; Mon, 27 Oct 2014 14:54:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141027215414.20241.25260.idtracker@ietfa.amsl.com>
Date: Mon, 27 Oct 2014 14:54:14 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/gxeIoVzSxFozX5tzp9UGVRa1dG8
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-gre-in-udp-encap-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 27 Oct 2014 21:54:40 -0000

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           : Generic UDP Encapsulation for IP Tunneling
        Authors         : Edward Crabbe
                          Lucy Yong
                          Xiaohu Xu
	Filename        : draft-ietf-tsvwg-gre-in-udp-encap-03.txt
	Pages           : 18
	Date            : 2014-10-27

Abstract:
   This document describes a method of encapsulating arbitrary
   protocols within GRE and UDP headers.  In this encapsulation, the
   source UDP port may be used as an entropy field for purposes of load
   balancing while the payload protocol may be identified by the GRE
   Protocol Type.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-gre-in-udp-encap-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 28 07:26:33 2014
Return-Path: <liujianning1@126.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F171A899D for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.807
X-Spam-Level: **
X-Spam-Status: No, score=2.807 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RELAY_IS_220=2.118, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 XJtDgDEL5aIW for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 07:26:25 -0700 (PDT)
Received: from m15-113.126.com (m15-113.126.com [220.181.15.113]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5121A896B for <tsvwg@ietf.org>; Tue, 28 Oct 2014 07:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=From:Subject:Date:Message-ID:MIME-Version; bh=9fpD6 4suPczmDTTLFmB96v+uZbRLeCQNoeM3xnXsYaU=; b=qHlkLh8KD1oaiIDSF9eLv 5yVwmOIjrOkOZTYj5EEDaZ2FuK68MWwjgFcV8c1vXl/jOFiiCx5bUBbxcWr1yye+ ZKRxP0BAQdUpwQaCLG3mubAp5D2o17d1xX0BZ3MS6a+WhPwG8KDiqKlBgE8XP5zt vYiDRF1ZDfTsTaqSWl0Aqc=
Received: from CarryPC (unknown [124.205.129.97]) by smtp3 (Coremail) with SMTP id DcmowABX+3RTp09Uyw8+BA--.7S2; Tue, 28 Oct 2014 22:25:39 +0800 (CST)
From: "Carry" <liujianning1@126.com>
To: <tsvwg@ietf.org>
References: <mailman.4002.1414420223.2945.tsvwg@ietf.org>
In-Reply-To: <mailman.4002.1414420223.2945.tsvwg@ietf.org>
Date: Tue, 28 Oct 2014 22:25:32 +0800
Message-ID: <000301cff2bb$11c20d90$354628b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/x8pHy687l8Ox9Sqy5u6/u9ubepAAyCX6g
Content-Language: zh-cn
X-CM-TRANSID: DcmowABX+3RTp09Uyw8+BA--.7S2
X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvj4RiiSlUUUUU
X-Originating-IP: [124.205.129.97]
X-CM-SenderInfo: xolxyxpdqqx0jjr6ij2wof0z/1tbiWQMzEFPI8YbFzwAAsf
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Qg5MhE3AJlYlbBYeRCTjX-M5RcI
Cc: weixinpeng@huawei.com
Subject: Re: [tsvwg] New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 28 Oct 2014 14:26:26 -0000

Hi,
I have had a review of the document, and there are some questions to be
clarified:
1. It seems that after egress fed back the congestion volume information,
the ingress still won't have any information about the congestion
information on specific traffic flow?

2.In real deployment, more than one tunnels would be concatenated together
to form a path of traffic, so how to deal with this kind of situation?

Thanks!
BR
- Jianning





From nobody Tue Oct 28 16:03:23 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1DF1A1A05 for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 16:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ayf3RA70q8Ph for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 16:03:16 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1BB11A044D for <tsvwg@ietf.org>; Tue, 28 Oct 2014 16:03:15 -0700 (PDT)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9SN3BvY030916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Oct 2014 19:03:11 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s9SN3BvY030916
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414537392; bh=/2CcSXS2uh4x/17lKMWKQsnLPxI=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=bK6GQ0jn47rVzUvp2DCoVeNXyv5sgTaBDfRTif70dURw3ijKfwKEM5uptHnupN1PR o6JHB0U6dvI1ru9z1DXlwtL5LmZlwwgq+uTjqwZwa/J0+qS1vcIFGTfc+oP/U4rC3a k28n2MVBPGxUQoV69Znn07HvOLH2fNggLJQqKHaU=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s9SN3BvY030916
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd52.lss.emc.com (RSA Interceptor); Tue, 28 Oct 2014 19:02:34 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id s9SN2tTU021337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Oct 2014 19:02:56 -0400
Received: from MXHUB108.corp.emc.com (10.253.58.24) by mxhub23.corp.emc.com (128.222.70.135) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 28 Oct 2014 19:02:56 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB108.corp.emc.com ([10.253.58.24]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 19:02:08 -0400
From: "Black, David" <david.black@emc.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: WGLC draft-ietf-tsvwg-port-use-05 : David Black's comments (1 of 2)
Thread-Index: Ac/zA058r9ktjJcWSEevNyb15MjY8w==
Date: Tue, 28 Oct 2014 23:02:54 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493606CD25@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.101]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/FNfUMMzdEnyBS2r_ZHQ3WD_sq2I
Subject: [tsvwg] WGLC draft-ietf-tsvwg-port-use-05 : David Black's comments (1 of 2)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 28 Oct 2014 23:03:20 -0000

This is the first of two messages on the WGLC of
draft-ietf-tsvwg-port-use-05.

I made a number of comments on the text in the -04 draft as an
individual (not as WG chair):
http://www.ietf.org/mail-archive/web/tsvwg/current/msg12617.html
=20
The -05 version of this draft resolves all of those comments to my
satisfaction.  I appreciate Joe's attention to this, including his
wise decision to just bit-bucket the SSL mention and reference, as
SSLv3 is now at least "SHOULD NOT use" based on a recently exposed
vulnerability that's exploitable via WiFi (POODLE).

I'll send a separate second message on my comments as a WG chair in
the list discussion on the -04 draft that centered on port scarcity,
security considerations in port allocation and the relationship
of this draft to RFC 6335.

Thanks,
--David

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Gorry Fairhurst
> Sent: Monday, October 27, 2014 10:23 AM
> To: tsvwg@ietf.org
> Subject: Re: [tsvwg] WGLC draft-ietf-tsvwg-port-use-05 : Working Group La=
st
> Call for comments due 29/10/2014
>=20
> A gentle reminder, that if you have comments on the updated ID, please
> do get back via the list by the deadline.
>=20
> To date, Eliot has responded confirming he happy to see the updated
> document progress. Others please respond, especially if you commented
> during the first WGLC.
>=20
> gorry
>=20
>=20
> On 14/10/2014 08:51, Gorry Fairhurst wrote:
> > This email announces the start of a working group last call to
> > confirm publication of draft-ietf-tsvwg-port-use,
> > "Recommendations for Transport Port Number Uses".  This document has
> > received significant feedback during the first WGLC review and has now
> > been updated in response to this feedback. It is now thought to be read=
y
> > to proceed to be published as a BCP.
> >
> > Please send any comments to the TSVWG list. We are interested in feedba=
ck
> > from any who have read the latest version, including those who commente=
d
> > in the first WGLC.
> >
> > The draft is available at:
> > https://tools.ietf.org/html/draft-ietf-tsvwg-port-use-05
> >
> > This last call will run for TWO weeks, ending 29th October.
> >
> > James, David, and Gorry
> > (TSVWG Chairs)
> > tsvwg-chairs@ietf.org
> >


From nobody Tue Oct 28 16:45:18 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4531A1B4D for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 16:45:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 s4bikipongQC for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 16:45:13 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391901A1B3C for <tsvwg@ietf.org>; Tue, 28 Oct 2014 16:45:13 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9SNjCVT021365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Tue, 28 Oct 2014 19:45:12 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s9SNjCVT021365
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414539912; bh=J2gOtNJGfUaZfBbBEkWKEuCfOP0=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=OSJ4Lyz2b8ViutSznvcExwPv7OcmqKUZ5afm6jc1iDK4zXEJXBT4ngCyZlfBWWAh+ XOObY1WQ5h083RkmAoSmsCwyi5pTOoiWfJWlvwT3Wlw7qTlwfSnnxcWjpcml3cMdTy QZ3es3DcbRKmbYQtbWp3yDhbfxLMZazl10yDDRFk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s9SNjCVT021365
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd03.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Tue, 28 Oct 2014 19:44:47 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id s9SNj1ZU005465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 28 Oct 2014 19:45:01 -0400
Received: from MXHUB108.corp.emc.com (10.253.58.24) by mxhub31.corp.emc.com (128.222.70.171) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 28 Oct 2014 19:45:00 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB108.corp.emc.com ([10.253.58.24]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 19:40:53 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: WGLC draft-ietf-tsvwg-port-use-05 : David Black's comments (2 of 2)
Thread-Index: Ac/zCQj06YKTRLgQT2OOuiSYGFeROQAABNww
Date: Tue, 28 Oct 2014 23:45:00 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493606CDC3@MX104CL02.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D2432779493606CDA6@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493606CDA6@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.101]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/3VVXB16WSLRH3yii5jvdfl0EFBs
Subject: [tsvwg] WGLC draft-ietf-tsvwg-port-use-05 : David Black's comments (2 of 2)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 28 Oct 2014 23:45:15 -0000

I've now gone back and reviewed my concerns and comments on this
draft expressed as a WG chair.  I think this version of the draft
is ok wrt those concerns and comments.  Specifically:

-1- Relationship to RFC 6335

This is now clear.  The -05 draft says in both the Abstract and
Introduction that it does not modify RFC 6335, and the draft
Introduction now describes one purpose of this draft as providing
guidance to applicants for port numbers.

-2- Secure and non-secure ports

I'm satisfied with the text on allocation of secure and non-secure
ports in Section 7.4 that resulted from discussion on the list.

-3- Scarcity

On balance, I think the case has been made that continuing to treat
ports as a somewhat scarce resource is a good thing to do in order
to avoid future problems caused by running out of ports.  We do not
face a port availability crisis in the near future in part because of
the effective manner in which port assignment has been functioning,
so encouraging it to continue to function in that effective manner is
a good thing to do.  The current port assignment process does treat
ports as a somewhat scarce resource.

In addition, some of the more contentious text on this topic in the
-04 version has been removed or toned down in the -05 version.

-- Process note

Between the material on allocation of secure and non-secure ports,
the discussion of firewall interactions, and other matters, this draft
contains significantly more security material than is typical for
tsvwg drafts.  For that reason I'm going to suggest that we (WG chairs)
explicitly ask for a security directorate review of this draft after
the RFC Publication request is submitted (working with our ADs to
figure out exactly when that request should be made).

We may also want to explicitly ask for an applications directorate
review.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From nobody Tue Oct 28 18:18:59 2014
Return-Path: <mzanaty@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932541A0161 for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 18:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xb5G7x_RGg1u for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 18:18:54 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 655A81A0099 for <tsvwg@ietf.org>; Tue, 28 Oct 2014 18:18:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8033; q=dns/txt; s=iport; t=1414545536; x=1415755136; h=from:to:subject:date:message-id:mime-version; bh=KArDJdJAAJqOwmpOIOM7UHl1n/O6sobtqU8VOGm3Nnw=; b=WWQv7BDEMqjR4ASkBsAZDhydM0Ola+VZUskJx3gIO5Z0caWpW12ocGwm UhSSQCbiRUrVSn+HJkXVhhEkb3CjLF2E30iscVyQuvGjNEPZkn7vzyzW0 Qk22AtlhUS8IwXZLQaPaR8u1WBh/GUz4HwWz9lBD6KzuXqmpSLdYpQpg0 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFACQ/UFStJA2G/2dsb2JhbABcgkhGgTDXMhYBAQEBAX2ECYELAYEAJwQBiFPFLAEBCAEBAQEBHZVbBZILi12WNoF+IIFagjSBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,806,1406592000";  d="scan'208,217";a="367331467"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-3.cisco.com with ESMTP; 29 Oct 2014 01:18:55 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s9T1IrJS015621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Oct 2014 01:18:53 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.159]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Tue, 28 Oct 2014 20:18:53 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Thread-Topic: SCTP NDATA draft
Thread-Index: AQHP8xZN+enLEIitxkaKyjBZFXcC6g==
Date: Wed, 29 Oct 2014 01:18:53 +0000
Message-ID: <D075B8BB.3D24D%mzanaty@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.82.211.189]
Content-Type: multipart/alternative; boundary="_000_D075B8BB3D24Dmzanatyciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/GjnYrVFG4YWGDl91YslQAlqea4o
Subject: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 01:18:57 -0000

--_000_D075B8BB3D24Dmzanatyciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,
While reviewing this draft for becoming mandatory in rtcweb data channels, =
I see two issues, which are independent of rtcweb.

1. If negotiated, NDATA must be used for all messages. The NDATA format req=
uires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes are onl=
y useful for fragmented messages. To avoid this overhead for small non-frag=
mented messages, can we relax / optimize this rule to be NDATA must be used=
 for all *fragmented* messages, while non-fragmented messages continue to u=
se DATA?

Proposed change to the next-to-last paragraph of section 1.1:

OLD:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all user-messages and no DATA chunks.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

NEW:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all fragmented user messages, and
   DATA chunks are used for all non-fragmented user messages.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

2. Fragmented messages can=92t be interleaved. This significantly dilutes t=
he value of NDATA. Apps that truly care about head of line blocking can=92t=
 rely on NDATA at all. They must implement app layer fragmentation with mes=
sages well below common MTUs to avoid blocking, hence defeating NDATA. NDAT=
A is arguably harmful for these apps, since it is 8 bytes closer to exceedi=
ng the MTU, forcing SCTP fragments and hence risking HOL blocking. To avoid=
 this, can we relax this rule to allow interleaving fragmented messages, si=
nce MID is already part of NDATA?

Proposed change to the last paragraph of section 3.1:

OLD:
   The sender MUST NOT have more than one ordered fragmented message
   being produced in any one stream.  The sender MUST NOT have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have one ordered and one unordered fragmented message
   being produced within a single stream.  At any time multiple streams
   MAY be producing an ordered or unordered fragmented message.

NEW:
   The sender MAY have more than one ordered fragmented message
   being produced in any one stream.  The sender MAY have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have multiple ordered and unordered fragmented messages
   being produced within a single stream.  At any time multiple streams
   MAY be producing multiple ordered or unordered fragmented messages.

Regards,
Mo


--_000_D075B8BB3D24Dmzanatyciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7CA98F332B018C4A9273507E4445D938@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-fami=
ly: Arial, sans-serif;">
<div>Hi,</div>
<div>While reviewing this draft for becoming mandatory in rtcweb data chann=
els, I see two issues, which are independent of rtcweb.</div>
<div><br>
</div>
<div>1. If negotiated, NDATA must be used for all messages. The NDATA forma=
t requires 8 more bytes than DATA (for MID&#43;FSN). But these extra 8 byte=
s are only useful for fragmented messages. To avoid this overhead for small=
 non-fragmented messages, can we relax
 / optimize this rule to be NDATA must be used for all *fragmented* message=
s, while non-fragmented messages continue to use DATA?</div>
<div><br>
</div>
<div>Proposed change to the next-to-last paragraph of section 1.1:</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061]. &nbsp;If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all user-messages and no DA=
TA chunks.</b> &nbsp;It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061]. &nbsp;If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all fragmented&nbsp;user me=
ssages, and</b></div>
<div><b>&nbsp; &nbsp;DATA chunks are used for all non-fragmented user messa=
ges. &nbsp;</b>It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>2. Fragmented messages can=92t be interleaved. This significantly dilu=
tes the value of NDATA. Apps that truly care about head of line blocking ca=
n=92t rely on NDATA at all. They must implement app layer fragmentation wit=
h messages well below common MTUs to
 avoid blocking, hence defeating NDATA. NDATA is arguably harmful for these=
 apps, since it is 8 bytes closer to exceeding the MTU, forcing SCTP fragme=
nts and hence risking HOL blocking. To avoid this, can we relax this rule t=
o allow interleaving fragmented
 messages, since MID is already part of NDATA?</div>
<div><br>
</div>
<div>
<div>Proposed change to the last paragraph of section 3.1:</div>
</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MUST NOT</b> have more than one ordered fra=
gmented message</div>
<div>&nbsp; &nbsp;being produced in any one stream. &nbsp;The sender <b>MUS=
T NOT</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>one ordered and one unordered frag=
mented message</b></div>
<div>&nbsp; &nbsp;being produced within a single stream. &nbsp;At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>an ordered or unordered fragmented me=
ssage</b>.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MAY</b> have more than one ordered fragment=
ed message</div>
<div>&nbsp; &nbsp;being produced in any one stream. &nbsp;The sender <b>MAY=
</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>multiple&nbsp;ordered and&nbsp;uno=
rdered fragmented messages</b></div>
<div>&nbsp; &nbsp;being produced within a single stream. &nbsp;At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>multiple ordered or unordered fragmen=
ted messages</b>.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
</body>
</html>

--_000_D075B8BB3D24Dmzanatyciscocom_--


From nobody Tue Oct 28 19:21:30 2014
Return-Path: <aterzis@google.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 406381A1B58 for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 19:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 KyVoTluvZqaw for <tsvwg@ietfa.amsl.com>; Tue, 28 Oct 2014 19:21:26 -0700 (PDT)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F14451A0147 for <tsvwg@ietf.org>; Tue, 28 Oct 2014 19:21:25 -0700 (PDT)
Received: by mail-vc0-f182.google.com with SMTP id id10so186904vcb.41 for <tsvwg@ietf.org>; Tue, 28 Oct 2014 19:21:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Md1Ld+fA403xpo93FTBlrH+3BiXOoKRzoRkD+GjcVbI=; b=jyVHSl7BSswXH/iVCKaA5hmi7EMVcdVgDQq2VvloxkpgryN03eNcSLVEhWn2bmdkhA hNGfY9abFRJAK/9nvp5cE/flyNRnY9OLM/xLqdXbzZ+fELvBW1sjk3wA08bCrgctswq9 +53yG0hNaiEbRgVpLS2BU2K3u2rPb+Sxf0As6CuaNRTJN1QyFbTAC/85t24vyO8UbeGh MZzQqHKj2W0B1yY6TX1GnbLF+1CMq76UswDSWXUl1z57JzXbwqIIT+GxnaPk+MqP3XS/ /9YmvgDRs+H982twrNMxqiINGpTLCh1F7Y5aBKlWhvOkLLk623dBihndrDz25FynyPDO IFyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Md1Ld+fA403xpo93FTBlrH+3BiXOoKRzoRkD+GjcVbI=; b=AQ+BgH//MiJp/DaRYKFHM8vjgwndpF4cVFt07XmXmsF1VvlDPlNSv+Z8XVNhYGm5uh mSOGgliuV30sAvu+a7718j/FG42kIA4BKwvemZ7hlx5/57ok9LXum/ebwylT+Y7+toGG FIUd2EOORiQdC4FR28jacP9yfKDxVfmSk3Pxjnsbm0ao+YKfkTQTxStHQRl3uhYDD3N/ PwwyW5jgv2SFHHUTxXusxzCzwPfo5OBJl1KCMQIxv60JRk65QJnX93zy/Ew11+KarcKd LfLEin7em+XZlSeV46Cf0S+bt12iPmYQ5H5GUCRfNTlRQVRjIe7QBXuRb3qCwOA0wwRI cSdA==
X-Gm-Message-State: ALoCoQmvYMtvTBtiG3ZSEzMwONVUJmZ4RXIKuPbfbMOYcp0Xc/sH2+Z31ltyyYxVSzbhyBeOKDd6
MIME-Version: 1.0
X-Received: by 10.52.114.228 with SMTP id jj4mr2698780vdb.46.1414549284913; Tue, 28 Oct 2014 19:21:24 -0700 (PDT)
Received: by 10.31.16.193 with HTTP; Tue, 28 Oct 2014 19:21:24 -0700 (PDT)
Date: Tue, 28 Oct 2014 19:21:24 -0700
Message-ID: <CAPjgeqNA7njcVgtsDJ1haBcLuNPNMmdsO5EkyWuGgygr+mCc+g@mail.gmail.com>
From: Andreas Terzis <aterzis@google.com>
To: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary=bcaec5485a14a5300a0506866b3f
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/isB7LyxicG6rs7NaLtYdb_TF0XM
Subject: [tsvwg] New draft draft-flinck-mobile-throughput-guidance-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 02:21:27 -0000

--bcaec5485a14a5300a0506866b3f
Content-Type: text/plain; charset=UTF-8

Hi all,

I want to draw your attention to a draft we submitted on using explicit
information from the network about the capacity of the radio link available
to a mobile device:

http://www.ietf.org/id/draft-flinck-mobile-throughput-guidance-00.txt

While the proposed mechanism is application-agnostic, we describe how it
can be used for mobile video delivery. Moreover, we present test results
from an end-to-end prototype developed for mobile video delivery.

Your review and comments are appreciated


Best regards,

Andreas Terzis

--bcaec5485a14a5300a0506866b3f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I want to draw your attention t=
o a draft we submitted on using explicit information from the network about=
 the capacity of the radio link available to a mobile device:</div><div><br=
></div><div><a href=3D"http://www.ietf.org/id/draft-flinck-mobile-throughpu=
t-guidance-00.txt">http://www.ietf.org/id/draft-flinck-mobile-throughput-gu=
idance-00.txt</a><br></div><div><br></div><div>While the proposed mechanism=
 is application-agnostic, we describe how it can be used for mobile video d=
elivery. Moreover, we present test results from an end-to-end prototype dev=
eloped for mobile video delivery.=C2=A0</div><div><br></div><div>Your revie=
w and comments are appreciated</div><div><br></div><div><br></div><div>Best=
 regards,</div><div><br></div><div>Andreas Terzis</div><div><br></div><div>=
<br></div></div>

--bcaec5485a14a5300a0506866b3f--


From nobody Wed Oct 29 00:50:19 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 504E21A6F64 for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 00:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 5ZnZZP2FfO3f for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 00:50:13 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6891A023E for <tsvwg@ietf.org>; Wed, 29 Oct 2014 00:50:10 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id bs8so883021wib.5 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 00:50:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LGrttTC3Eym7DOPx+7CvglF2gATSQpSeUpzWH3TQl+I=; b=vwgnQDUimlHBW9IB7zbKtH6ZtH2Q4fhW7eNRDGO0UHw6GuYQISS4w3R30AmBqSzTP4 GJo6oiWVMIEnPi7sV7EFelTATpnaLo21UuzCVxJegp+qzT+V1j3QENDPWKh1nAqz/4jd XzIoJPjXhByvEuHA3uqAa0OU23AqufaLqmVrs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LGrttTC3Eym7DOPx+7CvglF2gATSQpSeUpzWH3TQl+I=; b=Q40SNDqW/Q68Kjvd9Vrb9GX9GudTgHmOkNYugRk2dKJZKeg6Nd5fiq82mvu1BtfqUJ KrhN3dbcaaOTQt3/m+YpooOCf3nuGpst82pz0sRZ0LRvWrB2/VZiFM352iMylG9VnydI REmZ8t19M88m/3no+mvYHrHOYAFkj6WHP7xW4qI2Gq/wYHCKoQIV9etNX7xbW/hl4tkQ CAna0TWxJdweXLTbDkt5rbUBW2c+mZMEmB9ZlnQDrcbjKW3IeSNrt6UrS3gTRkw3YisC Uw/3QR5V+nS20RnfX8EVyj7hQTfbNZN+cZcFvRCGWPu/06X86kl7abv26z+jrPLbhgN9 iC4A==
X-Gm-Message-State: ALoCoQn761sBwz9UX53pg7fDhmqev5vKrr+5eeFgqREidv9kwzlMMXuPYTlO1eGZoV0Y3x3gJ58d/go0I5Dmn0KaQAzZEr0gx9CSktdJ7+NIEVgLjqED6hk=
MIME-Version: 1.0
X-Received: by 10.194.61.208 with SMTP id s16mr10247548wjr.104.1414569009373;  Wed, 29 Oct 2014 00:50:09 -0700 (PDT)
Received: by 10.194.240.36 with HTTP; Wed, 29 Oct 2014 00:50:09 -0700 (PDT)
In-Reply-To: <D075B8BB.3D24D%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com>
Date: Wed, 29 Oct 2014 08:50:09 +0100
Message-ID: <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com>
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b86d3e6507ac305068b036e
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/izZGFjv9RVycX64vFEgfBTnSMz8
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 07:50:16 -0000

--047d7b86d3e6507ac305068b036e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mo,

Please find feedback from my side below.

BR, Karen

On 29 October 2014 02:18, Mo Zanaty (mzanaty) <mzanaty@cisco.com> wrote:

>  Hi,
> While reviewing this draft for becoming mandatory in rtcweb data channels=
,
> I see two issues, which are independent of rtcweb.
>
>  1. If negotiated, NDATA must be used for all messages. The NDATA format
> requires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes ar=
e
> only useful for fragmented messages. To avoid this overhead for small
> non-fragmented messages, can we relax / optimize this rule to be NDATA mu=
st
> be used for all *fragmented* messages, while non-fragmented messages
> continue to use DATA?
>
> This will cost in performance in SCTP SW  - optionality costs in the
processing paths.
But it is true that the extra 8 bytes also costs some. Are you mostly
concerned about the 8 bytes from a running cache footprint perspective or
from
a wire perspective ?


>  Proposed change to the next-to-last paragraph of section 1.1:
>
>  OLD:
>     The support of the N-DATA chunk is negotiated during the association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an association
> *   N-DATA chunks are used for all user-messages and no DATA chunks.*  It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations using
>    N-DATA chunks.
>
>  NEW:
>     The support of the N-DATA chunk is negotiated during the association
>    setup using the Supported Extensions Parameter as defined in
>    [RFC5061].  If N-DATA support has been negotiated for an association
> *   N-DATA chunks are used for all fragmented user messages, and*
> *   DATA chunks are used for all non-fragmented user messages.  *It
>    should be noted, that an SCTP implementation needs to support the
>    coexistence of associations using DATA chunks and associations using
>    N-DATA chunks.
>
>  2. Fragmented messages can=E2=80=99t be interleaved.
>

This is not correct. They will be interleaved with all messages sent on
other streams.
Usage of multiple streams is really a prerequisite to avoid HOL. Further,
usage of multiple streams is
the best way to enforce differences in the priority of different messages.

Personally I would have like for there to be closer coupling in between
ndata and SCTP-PR in that I would like for
the message priority (of SCTP-PR) to be inherited from the stream priority
if nothing else is specified.
I have made this request towards the ndata author, but it may have been off
list.


This significantly dilutes the value of NDATA.
>

Do you require to use one stream only ?

Apps that truly care about head of line blocking can=E2=80=99t rely on NDAT=
A at all.
>

Se above.

>
>
They must implement app layer fragmentation with messages well below common
> MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harmful
> for these apps, since it is 8 bytes closer to exceeding the MTU, forcing
> SCTP fragments and hence risking HOL blocking. To avoid this, can we rela=
x
> this rule to allow interleaving fragmented messages, since MID is already
> part of NDATA?
>
We already have the stream concept why do we need now also a new concept.
Also we would then need to control which and what to control the
interleaving with.I.e. what to give priority. Yes perhaps we could use the
message priority, but the  right thing in SCTP is to use the stream concept
which is already there !!

>
>  Proposed change to the last paragraph of section 3.1:
>
>  OLD:
>     The sender *MUST NOT* have more than one ordered fragmented message
>    being produced in any one stream.  The sender *MUST NOT* have more tha=
n
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have *one ordered and one unordered fragmented message*
>    being produced within a single stream.  At any time multiple streams
>    MAY be producing *an ordered or unordered fragmented message*.
>
>  NEW:
>     The sender *MAY* have more than one ordered fragmented message
>    being produced in any one stream.  The sender *MAY* have more than
>    one un-ordered fragmented message being produced in any one stream.
>    The sender MAY have *multiple ordered and unordered fragmented
> messages*
>    being produced within a single stream.  At any time multiple streams
>    MAY be producing *multiple ordered or unordered fragmented messages*.
>
>  Regards,
> Mo
>
>

--047d7b86d3e6507ac305068b036e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Mo,<div><br></div><div>Please find feedback from my sid=
e below.</div><div><br></div><div>BR, Karen<br><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On 29 October 2014 02:18, Mo Zanaty (mzanaty)=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:mzanaty@cisco.com" target=3D"_blan=
k">mzanaty@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi,</div>
<div>While reviewing this draft for becoming mandatory in rtcweb data chann=
els, I see two issues, which are independent of rtcweb.</div>
<div><br>
</div>
<div>1. If negotiated, NDATA must be used for all messages. The NDATA forma=
t requires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes ar=
e only useful for fragmented messages. To avoid this overhead for small non=
-fragmented messages, can we relax
 / optimize this rule to be NDATA must be used for all *fragmented* message=
s, while non-fragmented messages continue to use DATA?</div>
<div><br></div></div></blockquote><div>This will cost in performance in SCT=
P SW =C2=A0- optionality costs in the processing paths.</div><div>But it is=
 true that the extra 8 bytes also costs some. Are you mostly concerned abou=
t the 8 bytes from a running cache footprint perspective or from</div><div>=
a wire perspective ?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fami=
ly:Arial,sans-serif"><div>
</div>
<div>Proposed change to the next-to-last paragraph of section 1.1:</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>=C2=A0 =C2=A0The support of the N-DATA chunk is negotiated during the =
association</div>
<div>=C2=A0 =C2=A0setup using the Supported Extensions Parameter as defined=
 in</div>
<div>=C2=A0 =C2=A0[RFC5061].=C2=A0 If N-DATA support has been negotiated fo=
r an association</div>
<div><b>=C2=A0 =C2=A0N-DATA chunks are used for all user-messages and no DA=
TA chunks.</b> =C2=A0It</div>
<div>=C2=A0 =C2=A0should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>=C2=A0 =C2=A0coexistence of associations using DATA chunks and associa=
tions using</div>
<div>=C2=A0 =C2=A0N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>=C2=A0 =C2=A0The support of the N-DATA chunk is negotiated during the =
association</div>
<div>=C2=A0 =C2=A0setup using the Supported Extensions Parameter as defined=
 in</div>
<div>=C2=A0 =C2=A0[RFC5061].=C2=A0 If N-DATA support has been negotiated fo=
r an association</div>
<div><b>=C2=A0 =C2=A0N-DATA chunks are used for all fragmented=C2=A0user me=
ssages, and</b></div>
<div><b>=C2=A0 =C2=A0DATA chunks are used for all non-fragmented user messa=
ges. =C2=A0</b>It</div>
<div>=C2=A0 =C2=A0should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>=C2=A0 =C2=A0coexistence of associations using DATA chunks and associa=
tions using</div>
<div>=C2=A0 =C2=A0N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>2. Fragmented messages can=E2=80=99t be interleaved.</div></div></bloc=
kquote><div>=C2=A0</div><div>This is not correct. They will be interleaved =
with all messages sent on other streams.</div><div>Usage of multiple stream=
s is really a prerequisite to avoid HOL. Further, usage of multiple streams=
 is=C2=A0</div><div>the best way to enforce differences in the priority of =
different messages.</div><div><br></div><div>Personally I would have like f=
or there to be closer coupling in between ndata and SCTP-PR in that I would=
 like for</div><div>the message priority (of SCTP-PR) to be inherited from =
the stream priority if nothing else is specified.</div><div>I have made thi=
s request towards the ndata author, but it may have been off list.</div><di=
v><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wor=
d-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-family:Arial,sans-se=
rif"><div>This significantly dilutes the value of NDATA. </div></div></bloc=
kquote><div><br></div><div>Do you require to use one stream only ?<br></div=
><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:brea=
k-word;color:rgb(0,0,0);font-size:12px;font-family:Arial,sans-serif"><div>A=
pps that truly care about head of line blocking can=E2=80=99t rely on NDATA=
 at all.</div></div></blockquote><div><br></div><div>Se above.=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word;color:rgb(=
0,0,0);font-size:12px;font-family:Arial,sans-serif"><div><span style=3D"fon=
t-family:arial;font-size:small;color:rgb(34,34,34)">=C2=A0</span></div></di=
v></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break=
-word;color:rgb(0,0,0);font-size:12px;font-family:Arial,sans-serif"><div>Th=
ey must implement app layer fragmentation with messages well below common M=
TUs to
 avoid blocking, hence defeating NDATA. NDATA is arguably harmful for these=
 apps, since it is 8 bytes closer to exceeding the MTU, forcing SCTP fragme=
nts and hence risking HOL blocking. To avoid this, can we relax this rule t=
o allow interleaving fragmented
 messages, since MID is already part of NDATA?</div></div></blockquote><div=
>We already have the stream concept why do we need now also a new concept. =
Also we would then need to control which and what to control the interleavi=
ng with.I.e. what to give priority. Yes perhaps we could use the message pr=
iority, but the =C2=A0right thing in SCTP is to use the stream concept whic=
h is already there !!</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wor=
d-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-family:Arial,sans-se=
rif">
<div><br>
</div>
<div>
<div>Proposed change to the last paragraph of section 3.1:</div>
</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>=C2=A0 =C2=A0The sender <b>MUST NOT</b> have more than one ordered fra=
gmented message</div>
<div>=C2=A0 =C2=A0being produced in any one stream.=C2=A0 The sender <b>MUS=
T NOT</b> have more than</div>
<div>=C2=A0 =C2=A0one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>=C2=A0 =C2=A0The sender MAY have <b>one ordered and one unordered frag=
mented message</b></div>
<div>=C2=A0 =C2=A0being produced within a single stream.=C2=A0 At any time =
multiple streams</div>
<div>=C2=A0 =C2=A0MAY be producing <b>an ordered or unordered fragmented me=
ssage</b>.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>=C2=A0 =C2=A0The sender <b>MAY</b> have more than one ordered fragment=
ed message</div>
<div>=C2=A0 =C2=A0being produced in any one stream.=C2=A0 The sender <b>MAY=
</b> have more than</div>
<div>=C2=A0 =C2=A0one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>=C2=A0 =C2=A0The sender MAY have <b>multiple=C2=A0ordered and=C2=A0uno=
rdered fragmented messages</b></div>
<div>=C2=A0 =C2=A0being produced within a single stream.=C2=A0 At any time =
multiple streams</div>
<div>=C2=A0 =C2=A0MAY be producing <b>multiple ordered or unordered fragmen=
ted messages</b>.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
</div>

</blockquote></div><br></div></div></div>

--047d7b86d3e6507ac305068b036e--


From nobody Wed Oct 29 07:01:13 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96571A0102 for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 07:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Aq5awalvQagd for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 07:01:09 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C58811A00E8 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 07:01:08 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 1BFB92B44C7; Wed, 29 Oct 2014 14:01:08 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Wed, 29 Oct 2014 14:01:08 -0000
Message-ID: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk>
Date: Wed, 29 Oct 2014 14:01:08 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Mh9cHtabrZkUS9W400JZVMt24KU
Cc: gorry@erg.abdn.ac.uk
Subject: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 14:01:11 -0000

TSVWG,

This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08

This WGLC will last until Wednesday, 19th November, 2014, this includes
the period of the coming IETF meeting.

A good note to the list is "I have read this version of the draft,
and I approve (or support) its progression to RFC". The chairs
request notes to the list showing support to get a sense of the WG.

Of course, you can ask for alternate text (where you supply the
actual replacement text, or convey the meaning sufficiently to the
authors) for anywhere in the document that you find unclear or troublesome.

James/Gorry/David
TSVWG chairs


From nobody Wed Oct 29 08:43:19 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C85D91A1A2D for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 08:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 2PV__7_Tc8Uo for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 08:43:06 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACB8C1A1A25 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 08:43:05 -0700 (PDT)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id s9TFh4JE030810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 29 Oct 2014 11:43:04 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s9TFh4JE030810
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1414597384; bh=1ywTFytztnU0fKPvc/u57UY6t+w=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=NyqiSS58BuV7eV/p5TOQW9Q1EZSlN7NXql+eKTWDIo3oJ70AARrT8MgCuukGkniUM IpWrBw6oIV7r0EsPE0zYKBnh9l/XJwlCSX8IRZkkypE/ff/3vYMAs5nDRVRA85Bn23 GfdbisAwSsWGLLMxb/R+IlMcae+OzjVDqiKIWZ24=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s9TFh4JE030810
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd52.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Wed, 29 Oct 2014 11:42:35 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id s9TFgu9P003381 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Wed, 29 Oct 2014 11:42:57 -0400
Received: from MXHUB106.corp.emc.com (10.253.58.23) by mxhub05.corp.emc.com (128.222.70.202) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 29 Oct 2014 11:42:56 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.131]) by MXHUB106.corp.emc.com ([10.253.58.23]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 11:42:56 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Preliminary Honolulu agenda posted
Thread-Index: Ac/zjwAeoKDP2xvlQ2OQ66Fok/ZCSg==
Date: Wed, 29 Oct 2014 15:42:55 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.101]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/a7_kKvm1DvNRkoYUpyQbrxlIwdg
Subject: [tsvwg] Preliminary Honolulu agenda posted
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 15:43:13 -0000

http://www.ietf.org/proceedings/91/agenda/agenda-91-tsvwg

This is assignment of drafts to the two meeting sessions; time allocations
will be in the final agenda that is posted next week.

If you want tsvwg agenda time and haven't requested it yet, now would be a
good time to do so.  There is one request that showed up this morning that
the chairs haven't dealt with yet, so it's not reflected in this preliminar=
y
tsvwg agenda.

HEADS-UP: The Tuesday conflict between the first tsvwg session and the new
IRTF Proposed Data Center Latency Control Research Group (dclcrg) session
is a serious problem that was overlooked in assembling the Honolulu IETF
meeting agenda.  Therefore:

*** The Tuesday tsvwg session is likely to be shortened and start late ***

Please do not complain to your WG chairs about this - we found out too
late to do anything about it.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Wed Oct 29 09:03:53 2014
Return-Path: <lars@netapp.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F901A1AFD for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 09:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level: 
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7SmMOVb932Co for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 09:03:49 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92AA81A1B0C for <tsvwg@ietf.org>; Wed, 29 Oct 2014 09:03:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,810,1406617200";  d="p7s'?scan'208";a="206699615"
Received: from hioexcmbx04-prd.hq.netapp.com ([10.122.105.37]) by mx12-out.netapp.com with ESMTP; 29 Oct 2014 09:01:43 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx04-prd.hq.netapp.com (10.122.105.37) with Microsoft SMTP Server (TLS) id 15.0.995.29; Wed, 29 Oct 2014 09:01:37 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::9047:8c6c:1d6e:4581%21]) with mapi id 15.00.0995.031; Wed, 29 Oct 2014 09:01:37 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: [tsvwg] Preliminary Honolulu agenda posted
Thread-Index: Ac/zjwAeoKDP2xvlQ2OQ66Fok/ZCSgAPUoIA
Date: Wed, 29 Oct 2014 16:01:37 +0000
Message-ID: <F34154F4-EBA8-4107-AEEB-C9C3EE2E6D89@netapp.com>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.1990.1)
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_FBCF217F-947F-487C-B82E-15F3621A0050"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/tiOeXdCL21pKouHL8-o304deLmQ
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] Preliminary Honolulu agenda posted
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 16:03:50 -0000

--Apple-Mail=_FBCF217F-947F-487C-B82E-15F3621A0050
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-10-29, at 16:42, Black, David <david.black@emc.com> wrote:
>=20
> HEADS-UP: The Tuesday conflict between the first tsvwg session and the =
new
> IRTF Proposed Data Center Latency Control Research Group (dclcrg) =
session
> is a serious problem that was overlooked in assembling the Honolulu =
IETF
> meeting agenda.

it's unfortunately worse. Your other Tuesday session conflicts with the =
IRTFOPEN meeting, which will have an ANRP talk by Tobias Flach on TCP =
with FEC.

I've scheduled Tobias talk last in IRTFOPEN, so if you end up early, the =
TCP folks in TSVWG can just head over.

(Yes, we need to avoid these conflicts better in the future. The =
Honolulu agenda is so tight that not all conflicts could be avoided.)

Lars=

--Apple-Mail=_FBCF217F-947F-487C-B82E-15F3621A0050
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMVzCCBhsw
ggUDoAMCAQICAwhPlDANBgkqhkiG9w0BAQsFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0
YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
MB4XDTEzMTIwNjA3MDk0N1oXDTE0MTIwNzA3MDY0MVowOjEYMBYGA1UEAwwPbGFyc0BuZXRhcHAu
Y29tMR4wHAYJKoZIhvcNAQkBFg9sYXJzQG5ldGFwcC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQDS6c3AH5ZSxTExtqA4RCkRMWmh84KVsbd85iNmeq2VHJv2Pc9TXG6aZz7r3Fjp
qXV+VtHlHOzZ1ncpMV0ldJMgi8F45/5WpSMEg4sXnYdtheE3drgWeR816PEaydHqSnaMNutAC7Td
ykkOFHXIsVg8IblDXhfiVQiZBZd+Wz6BpyMe59gr4Bpveft18uPQIXSxE95EsDTMyd/UDLVB+AkB
gHhO0+XxauzCbNUnubyiYYGOzgQ9G8J3Ewgrr/nVR+CrBCYgIsBP3foo0/h1hE7dHyI0Gl341yR7
J0AHDQ0DPIQOQtscFuRlthksCZLCfVSK6Mh6hVCOMEjVJxrgeBU3AgMBAAGjggLVMIIC0TAJBgNV
HRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0O
BBYEFHIOXgd2Y3/7a+OqwJ2giDTpYULAMB8GA1UdIwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGC
MBoGA1UdEQQTMBGBD2xhcnNAbmV0YXBwLmNvbTCCAUwGA1UdIASCAUMwggE/MIIBOwYLKwYBBAGB
tTcBAgMwggEqMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRm
MIH3BggrBgEFBQcCAjCB6jAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgEB
GoG+VGhpcyBjZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29yZGluZyB0byB0aGUgQ2xhc3MgMSBW
YWxpZGF0aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRDb20gQ0EgcG9saWN5LCByZWxpYW5j
ZSBvbmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBjb21wbGlhbmNlIG9mIHRoZSByZWx5
aW5nIHBhcnR5IG9ibGlnYXRpb25zLjA2BgNVHR8ELzAtMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0
c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRw
Oi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0
dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczEuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQELBQADggEBAMCLv+Qk
QYJxSendSLJPbFKuMkgm1PdAVoqxKAi8HmbirBTPhxh0vzhmZ/rneCHHlqY4p6r81+Se9HsqDsB6
DBQ/IbNgs7FQlCqOvCIwbn7VK+k/0eJAyOjIaUDPoD1ZaA1AkaFjJxvD2ZUZLBNq4AvOuP52j0Dm
i0FBC6pbBfnz57wuB++3P4NBTfZABbdazHlxl/2z1RGQNGov3R6zwNZLbxU2o2ftEJ48j4unuHjP
islFru3GRp4dbm5JLuHjUdDyXtMw6CdDvlmWQCcAgtEfqbGDp9bSSE9vbXbgf8n6iHoIA96HnTBW
BTDERdixe8t0T9AyT4ks9eHFLPL+PbwwggY0MIIEHKADAgECAgEeMA0GCSqGSIb3DQEBBQUAMH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGln
aXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9u
IEF1dGhvcml0eTAeFw0wNzEwMjQyMTAxNTVaFw0xNzEwMjQyMTAxNTVaMIGMMQswCQYDVQQGEwJJ
TDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlm
aWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVk
aWF0ZSBDbGllbnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDHCYPMzi3YGrEp
pC4Tq5a+ijKDjKaIQZZVR63UbxIP6uq/I0fhCu+cQhoUfE6ERKKnu8zPf1Jwuk0tsvVCk6U9b+0U
jM0dLep3ZdE1gblK/1FwYT5Pipsu2yOMluLqwvsuz9/9f1+1PKHG/FaR/wpbfuIqu54qzHDYeqiU
fsYzoVflR80DAC7hmJ+SmZnNTWyUGHJbBpA8Q89lGxahNvuryGaC/o2/ceD2uYDX9U8Eg5DpIpGQ
dcbQeGarV04WgAUjjXX5r/2dabmtxWMZwhZna//jdiSyrrSMTGKkDiXm6/3/4ebfeZuCYKzN2P8O
2F/Xe2AC/Y7zeEsnR7FOp+uXAgMBAAGjggGtMIIBqTAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB
/wQEAwIBBjAdBgNVHQ4EFgQUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHwYDVR0jBBgwFoAUTgvvGqRA
W6UXaYcwyjRoQ9BBrvIwZgYIKwYBBQUHAQEEWjBYMCcGCCsGAQUFBzABhhtodHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vY2EwLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBbBgNVHR8EVDBSMCegJaAjhiFodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmww
J6AloCOGIWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDCBgAYDVR0gBHkwdzB1Bgsr
BgEEAYG1NwECATBmMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRm
MA0GCSqGSIb3DQEBBQUAA4ICAQAKgwh9eKssBly4Y4xerhy5I3dNoXHYfYa8PlVLL/qtXnkFgdtY
1o95CfegFJTwqBBmf8pyTUnFsukDFUI22zF5bVHzuJ+GxhnSqN2sD1qetbYwBYK2iyYA5Pg7Er1A
+hKMIzEzcduRkIMmCeUTyMyikfbUFvIBivtvkR8ZFAk22BZy+pJfAoedO61HTz4qSfQoCRcLN5A0
t4DkuVhTMXIzuQ8CnykhExD6x4e6ebIbrjZLb7L+ocR0y4YjCl/Pd4MXU91y0vTipgr/O75CDUHD
RHCCKBVmz/Rzkc/b970MEeHt5LC3NiWTgBSvrLEuVzBKM586YoRD9Dy3OHQgWI270g+5MYA8GfgI
/EPT5G7xPbCDz+zjdH89PeR3U4So4lSXur6H6vp+m9TQXPF3a0LwZrp8MQ+Z77U1uL7TelWO5lAp
sbAonrqASfTpaprFVkL4nyGH+NHST2ZJPWIBk81i6Vw0ny0qZW2Niy/QvVNKbb43A43ny076khXO
7cNbBIRdJ/6qQNq9Bqb5C0Q5nEsFcj75oxQRqlKf6TcvGbjxkJh8BYtv9ePsXklAxtm8J7GCUBth
HSQgepbkOexhJ0wP8imUkyiPHQ0GvEnd83129fZjoEhdGwXV27ioRKbj/cIq7JRXun0NbeY+UdMY
u9jGfIpDLtUUGSgsg2zMGs5R4jGCA28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UE
ChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2ln
bmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGll
bnQgQ0ECAwhPlDAJBgUrDgMCGgUAoIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqG
SIb3DQEJBTEPFw0xNDEwMjkxNjAxMzZaMCMGCSqGSIb3DQEJBDEWBBSFu7SKligf0Cyi9UpVZaJY
cGH+6jCBpQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwhP
lDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCE+U
MA0GCSqGSIb3DQEBAQUABIIBAMfNFiNrLUzXt4edM86FviRMoOF5ShAcJuDIs24fh2DIB9rpmm2n
QA9UYJ/xQupAWcyt5fZQWYcDmVk2q1D9IWJS6wooI2xwn+gA/sSdoxKx6makG6bhJQFnbSi+aCF8
zc+MBtjIlf6pODGIRw9fX8f1TAM96gwprY2WRCf/YpcqfJahyB+Q0T74AaMZJhqkbvf8iy//BX4N
Ub0/DUGkeCLiZxhKUX+Qh2WqKSUngkDNZk8yID4y6cfP4NKTwCqp3vMSi4cIbBjVIWSIohvOCXdN
0H21PDcN2UG13bM7XnbFDPELTpitVPyzjdZrXAklZ2KfptXjZYepNbzqhZg5AXoAAAAAAAA=

--Apple-Mail=_FBCF217F-947F-487C-B82E-15F3621A0050--


From nobody Wed Oct 29 09:06:44 2014
Return-Path: <lucy.yong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B0D1A1AD4 for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Fez_nEjNYTBQ for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 09:06:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89B101A19FC for <tsvwg@ietf.org>; Wed, 29 Oct 2014 09:06:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLB59383; Wed, 29 Oct 2014 16:06:06 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 29 Oct 2014 16:05:50 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Wed, 29 Oct 2014 09:05:48 -0700
From: Lucy yong <lucy.yong@huawei.com>
To: "Black, David" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Preliminary Honolulu agenda posted
Thread-Index: Ac/zjwAeoKDP2xvlQ2OQ66Fok/ZCSgAAuvPg
Date: Wed, 29 Oct 2014 16:05:48 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.147.113]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/DqUQodHgMOLWOYXQEoPDeDXeD7M
Subject: Re: [tsvwg] Preliminary Honolulu agenda posted
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 16:06:43 -0000

Here is the draft.=20
https://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-03

Look forward to the discussion in Honolulu.

Lucy

-----Original Message-----
From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
Sent: Wednesday, October 29, 2014 10:43 AM
To: tsvwg@ietf.org
Subject: [tsvwg] Preliminary Honolulu agenda posted

http://www.ietf.org/proceedings/91/agenda/agenda-91-tsvwg

This is assignment of drafts to the two meeting sessions; time allocations =
will be in the final agenda that is posted next week.

If you want tsvwg agenda time and haven't requested it yet, now would be a =
good time to do so.  There is one request that showed up this morning that =
the chairs haven't dealt with yet, so it's not reflected in this preliminar=
y tsvwg agenda.

HEADS-UP: The Tuesday conflict between the first tsvwg session and the new =
IRTF Proposed Data Center Latency Control Research Group (dclcrg) session i=
s a serious problem that was overlooked in assembling the Honolulu IETF mee=
ting agenda.  Therefore:

*** The Tuesday tsvwg session is likely to be shortened and start late ***

Please do not complain to your WG chairs about this - we found out too late=
 to do anything about it.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Wed Oct 29 12:33:13 2014
Return-Path: <mzanaty@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8C01A899C for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 12:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 4kL_uy3M9Ftq for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 12:33:08 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 280A71A897A for <tsvwg@ietf.org>; Wed, 29 Oct 2014 12:33:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17757; q=dns/txt; s=iport; t=1414611189; x=1415820789; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1vdGoOu8Vz2NxiIoYkdzRugbo8xDLzSWOlztkINSQ+M=; b=DQ+aldSoc2/V5BYwMgQZizUeacRAt1OsWEzJlxlJz4J7M1xh9UEqqqgn 9QOMiXbvab3igu5kDjqwIMutysVsxpKZx1tmfhU7YIf5MoNwhJ1aG6f/R aQd12W+5qdtv1y1SEbMj0AWP8HcZvc3A8lm9lSQBeN773+sIidUegtDIo w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAANAUVStJA2H/2dsb2JhbABcgkhGgSwE1W8CgR0WAQEBAQF9hAMBAQR5EAIBCD8HMhQRAgQOBYhByCwBAQEBAQEEAQEBAQEBAQEakDhYBgGESwWPboIfi12BMYNKkUWBfiCBWmyBBkKBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,279,1413244800";  d="scan'208,217";a="367607299"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP; 29 Oct 2014 19:33:08 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9TJX7GK008934 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Oct 2014 19:33:07 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.159]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 14:33:06 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Thread-Topic: [tsvwg] SCTP NDATA draft
Thread-Index: AQHP868pxXRMMKm9V0CCJHBU9gGZ2g==
Date: Wed, 29 Oct 2014 19:33:05 +0000
Message-ID: <D0769E4A.3D378%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com>
In-Reply-To: <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.81.3.26]
Content-Type: multipart/alternative; boundary="_000_D0769E4A3D378mzanatyciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/bPCjaKafgGQL4PH_S97gLpSxdcM
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 19:33:11 -0000

--_000_D0769E4A3D378mzanatyciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Karen,

I understand the design intent was to avoid one stream blocking another. Ho=
wever, I think that misses the true application need. It assumes applicatio=
ns only care about blocking of non-fragmented messages and don=92t care abo=
ut blocking of fragmented messages.

I think that assumption is wrong for most applications. It is certainly wro=
ng for rtcweb applications, where JSON objects would be a natural message p=
ayload for JS apps, and these can easily exceed common MTUs depending on th=
e complexity and verbosity of the JSON object.

If an application does not care about blocking, it does not need NDATA. If =
it cares, it must create a new stream for every potentially fragmented mess=
age (which requires guessing the MTU) since that will block subsequent frag=
mented messages. It must also have a garbage collector to close those strea=
ms (or otherwise mark them reusable) after ensuring delivery with an app la=
yer ack.

That is far more overhead and complexity for both the application and the S=
CTP stack than simply implementing application layer fragmentation which de=
feats NDATA. Even more true for rtcweb applications since they have the ext=
ra overhead of DCEP to open/close bidirectional channels.

So applications which truly care about blocking will almost certainly imple=
ment application layer fragmentation rather than relying on NDATA (which wi=
ll block) or jumping through hoops to create new streams for each potential=
ly fragmented message.

It should be simple to fix NDATA to meet the true application need. The tex=
t change is dead simple. There is no protocol change, since MID is already =
part of NDATA. There is only implementation effort, which should be limited=
 to maintaining FSN state for multiple MIDs per stream rather than only one=
. That seems like a small effort for making NDATA actually useful for most =
applications.

Cheers,
Mo


On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.co=
m<mailto:karen.nielsen@tieto.com>> wrote:

Hi Mo,

Please find feedback from my side below.

BR, Karen

On 29 October 2014 02:18, Mo Zanaty (mzanaty) <mzanaty@cisco.com<mailto:mza=
naty@cisco.com>> wrote:
Hi,
While reviewing this draft for becoming mandatory in rtcweb data channels, =
I see two issues, which are independent of rtcweb.

1. If negotiated, NDATA must be used for all messages. The NDATA format req=
uires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes are onl=
y useful for fragmented messages. To avoid this overhead for small non-frag=
mented messages, can we relax / optimize this rule to be NDATA must be used=
 for all *fragmented* messages, while non-fragmented messages continue to u=
se DATA?

This will cost in performance in SCTP SW  - optionality costs in the proces=
sing paths.
But it is true that the extra 8 bytes also costs some. Are you mostly conce=
rned about the 8 bytes from a running cache footprint perspective or from
a wire perspective ?

Proposed change to the next-to-last paragraph of section 1.1:

OLD:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all user-messages and no DATA chunks.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

NEW:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all fragmented user messages, and
   DATA chunks are used for all non-fragmented user messages.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

2. Fragmented messages can=92t be interleaved.

This is not correct. They will be interleaved with all messages sent on oth=
er streams.
Usage of multiple streams is really a prerequisite to avoid HOL. Further, u=
sage of multiple streams is
the best way to enforce differences in the priority of different messages.

Personally I would have like for there to be closer coupling in between nda=
ta and SCTP-PR in that I would like for
the message priority (of SCTP-PR) to be inherited from the stream priority =
if nothing else is specified.
I have made this request towards the ndata author, but it may have been off=
 list.


This significantly dilutes the value of NDATA.

Do you require to use one stream only ?

Apps that truly care about head of line blocking can=92t rely on NDATA at a=
ll.

Se above.

They must implement app layer fragmentation with messages well below common=
 MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harmful f=
or these apps, since it is 8 bytes closer to exceeding the MTU, forcing SCT=
P fragments and hence risking HOL blocking. To avoid this, can we relax thi=
s rule to allow interleaving fragmented messages, since MID is already part=
 of NDATA?
We already have the stream concept why do we need now also a new concept. A=
lso we would then need to control which and what to control the interleavin=
g with.I.e. what to give priority. Yes perhaps we could use the message pri=
ority, but the  right thing in SCTP is to use the stream concept which is a=
lready there !!

Proposed change to the last paragraph of section 3.1:

OLD:
   The sender MUST NOT have more than one ordered fragmented message
   being produced in any one stream.  The sender MUST NOT have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have one ordered and one unordered fragmented message
   being produced within a single stream.  At any time multiple streams
   MAY be producing an ordered or unordered fragmented message.

NEW:
   The sender MAY have more than one ordered fragmented message
   being produced in any one stream.  The sender MAY have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have multiple ordered and unordered fragmented messages
   being produced within a single stream.  At any time multiple streams
   MAY be producing multiple ordered or unordered fragmented messages.

Regards,
Mo



--_000_D0769E4A3D378mzanatyciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <64C068425C1C634581BFD946BEB6D48E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-fami=
ly: Arial, sans-serif;">
<div>Hi Karen,</div>
<div><br>
</div>
<div>I understand the design intent was to avoid one stream blocking anothe=
r. However, I think that misses the true application need. It assumes appli=
cations only care about blocking of non-fragmented messages and don=92t car=
e about blocking of fragmented messages.</div>
<div><br>
</div>
<div>I think that assumption is wrong for most applications. It is certainl=
y wrong for rtcweb applications, where JSON objects would be a natural mess=
age payload for JS apps, and these can easily exceed common MTUs depending =
on the complexity and verbosity
 of the JSON object.</div>
<div><br>
</div>
<div>If an application does not care about blocking, it does not need NDATA=
. If it cares, it must create a new stream for every potentially fragmented=
 message (which requires guessing the MTU) since that will block subsequent=
 fragmented messages. It must also
 have a garbage collector to close those streams (or otherwise mark them re=
usable) after ensuring delivery with an app layer ack.</div>
<div><br>
</div>
<div>That is far more overhead and complexity for both the application and =
the SCTP stack than simply implementing application layer fragmentation whi=
ch defeats NDATA. Even more true for rtcweb applications since they have th=
e extra overhead of DCEP to open/close
 bidirectional channels.</div>
<div><br>
</div>
<div>So applications which truly care about blocking will almost certainly =
implement application layer fragmentation rather than relying on NDATA (whi=
ch will block) or jumping through hoops to create new streams for each pote=
ntially fragmented message.</div>
<div><br>
</div>
<div>It should be simple to fix NDATA to meet the true application need. Th=
e text change is dead simple. There is no protocol change, since MID is alr=
eady part of NDATA. There is only implementation effort, which should be li=
mited to maintaining FSN state for
 multiple MIDs per stream rather than only one. That seems like a small eff=
ort for making NDATA actually useful for most applications.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Mo</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen &lt;<a href=3D"mai=
lto:karen.nielsen@tieto.com">karen.nielsen@tieto.com</a>&gt; wrote:</div>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Hi Mo,
<div><br>
</div>
<div>Please find feedback from my side below.</div>
<div><br>
</div>
<div>BR, Karen<br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 29 October 2014 02:18, Mo Zanaty (mzanaty) <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:mzanaty@cisco.com" target=3D"_blank">mzanaty@cisco.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi,</div>
<div>While reviewing this draft for becoming mandatory in rtcweb data chann=
els, I see two issues, which are independent of rtcweb.</div>
<div><br>
</div>
<div>1. If negotiated, NDATA must be used for all messages. The NDATA forma=
t requires 8 more bytes than DATA (for MID&#43;FSN). But these extra 8 byte=
s are only useful for fragmented messages. To avoid this overhead for small=
 non-fragmented messages, can we relax
 / optimize this rule to be NDATA must be used for all *fragmented* message=
s, while non-fragmented messages continue to use DATA?</div>
<div><br>
</div>
</div>
</blockquote>
<div>This will cost in performance in SCTP SW &nbsp;- optionality costs in =
the processing paths.</div>
<div>But it is true that the extra 8 bytes also costs some. Are you mostly =
concerned about the 8 bytes from a running cache footprint perspective or f=
rom</div>
<div>a wire perspective ?</div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div></div>
<div>Proposed change to the next-to-last paragraph of section 1.1:</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061].&nbsp; If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all user-messages and no DA=
TA chunks.</b> &nbsp;It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061].&nbsp; If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all fragmented&nbsp;user me=
ssages, and</b></div>
<div><b>&nbsp; &nbsp;DATA chunks are used for all non-fragmented user messa=
ges. &nbsp;</b>It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>2. Fragmented messages can=92t be interleaved.</div>
</div>
</blockquote>
<div>&nbsp;</div>
<div>This is not correct. They will be interleaved with all messages sent o=
n other streams.</div>
<div>Usage of multiple streams is really a prerequisite to avoid HOL. Furth=
er, usage of multiple streams is&nbsp;</div>
<div>the best way to enforce differences in the priority of different messa=
ges.</div>
<div><br>
</div>
<div>Personally I would have like for there to be closer coupling in betwee=
n ndata and SCTP-PR in that I would like for</div>
<div>the message priority (of SCTP-PR) to be inherited from the stream prio=
rity if nothing else is specified.</div>
<div>I have made this request towards the ndata author, but it may have bee=
n off list.</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>This significantly dilutes the value of NDATA. </div>
</div>
</blockquote>
<div><br>
</div>
<div>Do you require to use one stream only ?<br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Apps that truly care about head of line blocking can=92t rely on NDATA=
 at all.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Se above.&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><span style=3D"font-family:arial;font-size:small;color:rgb(34,34,34)">=
&nbsp;</span></div>
</div>
</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>They must implement app layer fragmentation with messages well below c=
ommon MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harm=
ful for these apps, since it is 8 bytes closer to exceeding the MTU, forcin=
g SCTP fragments and hence risking
 HOL blocking. To avoid this, can we relax this rule to allow interleaving =
fragmented messages, since MID is already part of NDATA?</div>
</div>
</blockquote>
<div>We already have the stream concept why do we need now also a new conce=
pt. Also we would then need to control which and what to control the interl=
eaving with.I.e. what to give priority. Yes perhaps we could use the messag=
e priority, but the &nbsp;right thing
 in SCTP is to use the stream concept which is already there !!</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><br>
</div>
<div>
<div>Proposed change to the last paragraph of section 3.1:</div>
</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MUST NOT</b> have more than one ordered fra=
gmented message</div>
<div>&nbsp; &nbsp;being produced in any one stream.&nbsp; The sender <b>MUS=
T NOT</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>one ordered and one unordered frag=
mented message</b></div>
<div>&nbsp; &nbsp;being produced within a single stream.&nbsp; At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>an ordered or unordered fragmented me=
ssage</b>.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MAY</b> have more than one ordered fragment=
ed message</div>
<div>&nbsp; &nbsp;being produced in any one stream.&nbsp; The sender <b>MAY=
</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>multiple&nbsp;ordered and&nbsp;uno=
rdered fragmented messages</b></div>
<div>&nbsp; &nbsp;being produced within a single stream.&nbsp; At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>multiple ordered or unordered fragmen=
ted messages</b>.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D0769E4A3D378mzanatyciscocom_--


From nobody Wed Oct 29 14:01:43 2014
Return-Path: <karen.nielsen@tieto.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB451A902B for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 14:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 0eZU2v8Gv0qk for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 14:01:35 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 629951A902C for <tsvwg@ietf.org>; Wed, 29 Oct 2014 14:01:22 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id k14so2843960wgh.15 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 14:01:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=C2xqpzuJ7arkv3Zd8ea77jRzMldcHC4mmcPA2s1wVEY=; b=a8Huk4gUDfoBDntwdQwrO5vVmnkggd/B2nCDJygEheRQQvE7SoQIkSO2u+aHCG8+lU 7NeHysxX1Xx8qrBOoDTtIkfs2/jkp2+LckWmyxFwnRsaQNmMNriudDYopvv2XUYxPUgr TeuWqabPIpYHh0bN5lCHRjPB53LpTCqIqaQRs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=C2xqpzuJ7arkv3Zd8ea77jRzMldcHC4mmcPA2s1wVEY=; b=SsUDuRehYQ49oBob95WRXzDXpdHna8ERHdwPRVkHUw8cyOjU1k2TWzmY/SHL6iF7Xp NNvkvDRipqxiqSCDZZuejXEvIcNf5fM60OnrQzFecgJG58VCsLRreq6/q390Y4Pzyqjc 6MKhGURXTuXwl7gLMvJR30mr8e5EPpVM3XtxvgAwOPeQjXHPaYg5Y4Paw6dU9fcsu8r7 cn2esMNf82QedYRwKfHtRCEoif9WtD+eNPxcWrbFcW+plmNHM3YG6RExfkwmdrlwtoFB pqVMpsZphryDNIJdH2XJruaazCOLWvmDdalUkApDX5K2EJhDiQoe7rB23VBewSyGIMw8 v+JA==
X-Gm-Message-State: ALoCoQnfHtTy0EpM/nPo7tntp7ycPT7ej9IjBAvCKSUsCmJAQtN6PeMdNn9Ypz5TlsqAmm+hLdNCdE5+VFMQTW/2o0dgmYiScrhdo5yfjfOgO9wPpH1e9y8=
MIME-Version: 1.0
X-Received: by 10.180.211.70 with SMTP id na6mr15153705wic.3.1414616481584; Wed, 29 Oct 2014 14:01:21 -0700 (PDT)
Received: by 10.194.240.36 with HTTP; Wed, 29 Oct 2014 14:01:21 -0700 (PDT)
In-Reply-To: <D0769E4A.3D378%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com> <D0769E4A.3D378%mzanaty@cisco.com>
Date: Wed, 29 Oct 2014 22:01:21 +0100
Message-ID: <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com>
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c261dce0f0d405069610cb
X-DomainID: tieto.com
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/dBl82k3oldz5YY3Jg_6g0xSGbT4
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Oct 2014 21:01:39 -0000

--001a11c261dce0f0d405069610cb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mo,

I am all for finding a solution that fits the needs of the application.
Just so that this is clear.

So you are actually not looking for ndata to support the interleaving
property (or that perhaps also, never mind)
but mainly to prevent RX and TX blocking for unordered delivery of larger
than PMTU messages,
possibly also for ordered delivery of such messages.

OK. If others agree then I suppose that ndata can be extended as you
suggest.
But reassembly costs, of course. Especially over a best effort network.
SCTP will have to filter and manage concurrent reassembly on yet one more
identifier/dimension.

The application need not guess the MTU, the SCTP fragmentation point can be
read on the socket (yes it may vary, but it will not jump that much around
I suppose). In special cases where the application is anyway chopping up
the messages it will be wildly best to do this in subPMTU sizes.

BR, karen






On 29 October 2014 20:33, Mo Zanaty (mzanaty) <mzanaty@cisco.com> wrote:

>  Hi Karen,
>
>  I understand the design intent was to avoid one stream blocking another.
> However, I think that misses the true application need. It assumes
> applications only care about blocking of non-fragmented messages and don=
=E2=80=99t
> care about blocking of fragmented messages.
>
>  I think that assumption is wrong for most applications. It is certainly
> wrong for rtcweb applications, where JSON objects would be a natural
> message payload for JS apps, and these can easily exceed common MTUs
> depending on the complexity and verbosity of the JSON object.
>
>  If an application does not care about blocking, it does not need NDATA.
> If it cares, it must create a new stream for every potentially fragmented
> message (which requires guessing the MTU) since that will block subsequen=
t
> fragmented messages. It must also have a garbage collector to close those
> streams (or otherwise mark them reusable) after ensuring delivery with an
> app layer ack.
>
>  That is far more overhead and complexity for both the application and
> the SCTP stack than simply implementing application layer fragmentation
> which defeats NDATA. Even more true for rtcweb applications since they ha=
ve
> the extra overhead of DCEP to open/close bidirectional channels.
>
>  So applications which truly care about blocking will almost certainly
> implement application layer fragmentation rather than relying on NDATA
> (which will block) or jumping through hoops to create new streams for eac=
h
> potentially fragmented message.
>
>  It should be simple to fix NDATA to meet the true application need. The
> text change is dead simple. There is no protocol change, since MID is
> already part of NDATA. There is only implementation effort, which should =
be
> limited to maintaining FSN state for multiple MIDs per stream rather than
> only one. That seems like a small effort for making NDATA actually useful
> for most applications.
>
>  Cheers,
> Mo
>
>
>   On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen <
> karen.nielsen@tieto.com> wrote:
>
>   Hi Mo,
>
>  Please find feedback from my side below.
>
>  BR, Karen
>
> On 29 October 2014 02:18, Mo Zanaty (mzanaty) <mzanaty@cisco.com> wrote:
>
>>  Hi,
>> While reviewing this draft for becoming mandatory in rtcweb data
>> channels, I see two issues, which are independent of rtcweb.
>>
>>  1. If negotiated, NDATA must be used for all messages. The NDATA format
>> requires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes a=
re
>> only useful for fragmented messages. To avoid this overhead for small
>> non-fragmented messages, can we relax / optimize this rule to be NDATA m=
ust
>> be used for all *fragmented* messages, while non-fragmented messages
>> continue to use DATA?
>>
>>   This will cost in performance in SCTP SW  - optionality costs in the
> processing paths.
> But it is true that the extra 8 bytes also costs some. Are you mostly
> concerned about the 8 bytes from a running cache footprint perspective or
> from
> a wire perspective ?
>
>
>>  Proposed change to the next-to-last paragraph of section 1.1:
>>
>>  OLD:
>>     The support of the N-DATA chunk is negotiated during the association
>>    setup using the Supported Extensions Parameter as defined in
>>    [RFC5061].  If N-DATA support has been negotiated for an association
>> *   N-DATA chunks are used for all user-messages and no DATA chunks.*  I=
t
>>    should be noted, that an SCTP implementation needs to support the
>>    coexistence of associations using DATA chunks and associations using
>>    N-DATA chunks.
>>
>>  NEW:
>>     The support of the N-DATA chunk is negotiated during the association
>>    setup using the Supported Extensions Parameter as defined in
>>    [RFC5061].  If N-DATA support has been negotiated for an association
>> *   N-DATA chunks are used for all fragmented user messages, and*
>> *   DATA chunks are used for all non-fragmented user messages.  *It
>>    should be noted, that an SCTP implementation needs to support the
>>    coexistence of associations using DATA chunks and associations using
>>    N-DATA chunks.
>>
>>  2. Fragmented messages can=E2=80=99t be interleaved.
>>
>
> This is not correct. They will be interleaved with all messages sent on
> other streams.
> Usage of multiple streams is really a prerequisite to avoid HOL. Further,
> usage of multiple streams is
> the best way to enforce differences in the priority of different messages=
.
>
>  Personally I would have like for there to be closer coupling in between
> ndata and SCTP-PR in that I would like for
> the message priority (of SCTP-PR) to be inherited from the stream priorit=
y
> if nothing else is specified.
> I have made this request towards the ndata author, but it may have been
> off list.
>
>
>   This significantly dilutes the value of NDATA.
>>
>
>  Do you require to use one stream only ?
>
>   Apps that truly care about head of line blocking can=E2=80=99t rely on =
NDATA at
>> all.
>>
>
>  Se above.
>
>>
>>
>  They must implement app layer fragmentation with messages well below
>> common MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably
>> harmful for these apps, since it is 8 bytes closer to exceeding the MTU,
>> forcing SCTP fragments and hence risking HOL blocking. To avoid this, ca=
n
>> we relax this rule to allow interleaving fragmented messages, since MID =
is
>> already part of NDATA?
>>
> We already have the stream concept why do we need now also a new concept.
> Also we would then need to control which and what to control the
> interleaving with.I.e. what to give priority. Yes perhaps we could use th=
e
> message priority, but the  right thing in SCTP is to use the stream conce=
pt
> which is already there !!
>
>>
>>  Proposed change to the last paragraph of section 3.1:
>>
>>  OLD:
>>     The sender *MUST NOT* have more than one ordered fragmented message
>>    being produced in any one stream.  The sender *MUST NOT* have more
>> than
>>    one un-ordered fragmented message being produced in any one stream.
>>    The sender MAY have *one ordered and one unordered fragmented message=
*
>>    being produced within a single stream.  At any time multiple streams
>>    MAY be producing *an ordered or unordered fragmented message*.
>>
>>  NEW:
>>     The sender *MAY* have more than one ordered fragmented message
>>    being produced in any one stream.  The sender *MAY* have more than
>>    one un-ordered fragmented message being produced in any one stream.
>>    The sender MAY have *multiple ordered and unordered fragmented
>> messages*
>>    being produced within a single stream.  At any time multiple streams
>>    MAY be producing *multiple ordered or unordered fragmented messages*.
>>
>>  Regards,
>> Mo
>>
>>
>

--001a11c261dce0f0d405069610cb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Mo,<div><br></div><div>I am all for finding a solution =
that fits the needs of the application. Just so that this is clear.</div><d=
iv><br></div><div>So you are actually not looking for ndata to support the =
interleaving property (or that perhaps also, never mind)</div><div>but main=
ly to prevent RX and TX blocking for unordered delivery of larger than PMTU=
 messages,=C2=A0</div><div>possibly also for ordered delivery of such messa=
ges.=C2=A0</div><div><br></div><div>OK. If others agree then I suppose that=
 ndata can be extended as you suggest.=C2=A0</div><div>But reassembly costs=
, of course. Especially over a best effort network.</div><div>SCTP will hav=
e to filter and manage concurrent reassembly on yet one more identifier/dim=
ension.<br></div><div><br></div><div>The application need not guess the MTU=
, the SCTP fragmentation point can be read on the socket (yes it may vary, =
but it will not jump that much around I suppose). In special cases where th=
e application is anyway chopping up the messages it will be wildly best to =
do this in subPMTU sizes.</div><div><br></div><div>BR, karen</div><div><br>=
</div><div><br></div><div><br></div><div><br></div><div><br></div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 29 October 2014 2=
0:33, Mo Zanaty (mzanaty) <span dir=3D"ltr">&lt;<a href=3D"mailto:mzanaty@c=
isco.com" target=3D"_blank">mzanaty@cisco.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi Karen,</div>
<div><br>
</div>
<div>I understand the design intent was to avoid one stream blocking anothe=
r. However, I think that misses the true application need. It assumes appli=
cations only care about blocking of non-fragmented messages and don=E2=80=
=99t care about blocking of fragmented messages.</div>
<div><br>
</div>
<div>I think that assumption is wrong for most applications. It is certainl=
y wrong for rtcweb applications, where JSON objects would be a natural mess=
age payload for JS apps, and these can easily exceed common MTUs depending =
on the complexity and verbosity
 of the JSON object.</div>
<div><br>
</div>
<div>If an application does not care about blocking, it does not need NDATA=
. If it cares, it must create a new stream for every potentially fragmented=
 message (which requires guessing the MTU) since that will block subsequent=
 fragmented messages. It must also
 have a garbage collector to close those streams (or otherwise mark them re=
usable) after ensuring delivery with an app layer ack.</div>
<div><br>
</div>
<div>That is far more overhead and complexity for both the application and =
the SCTP stack than simply implementing application layer fragmentation whi=
ch defeats NDATA. Even more true for rtcweb applications since they have th=
e extra overhead of DCEP to open/close
 bidirectional channels.</div>
<div><br>
</div>
<div>So applications which truly care about blocking will almost certainly =
implement application layer fragmentation rather than relying on NDATA (whi=
ch will block) or jumping through hoops to create new streams for each pote=
ntially fragmented message.</div>
<div><br>
</div>
<div>It should be simple to fix NDATA to meet the true application need. Th=
e text change is dead simple. There is no protocol change, since MID is alr=
eady part of NDATA. There is only implementation effort, which should be li=
mited to maintaining FSN state for
 multiple MIDs per stream rather than only one. That seems like a small eff=
ort for making NDATA actually useful for most applications.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Mo</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div>
<div>On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen &lt;<a href=3D"mai=
lto:karen.nielsen@tieto.com" target=3D"_blank">karen.nielsen@tieto.com</a>&=
gt; wrote:</div>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Hi Mo,
<div><br>
</div>
<div>Please find feedback from my side below.</div>
<div><br>
</div>
<div>BR, Karen<br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 29 October 2014 02:18, Mo Zanaty (mzanaty) <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:mzanaty@cisco.com" target=3D"_blank">mzanaty@cisco.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi,</div>
<div>While reviewing this draft for becoming mandatory in rtcweb data chann=
els, I see two issues, which are independent of rtcweb.</div>
<div><br>
</div>
<div>1. If negotiated, NDATA must be used for all messages. The NDATA forma=
t requires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes ar=
e only useful for fragmented messages. To avoid this overhead for small non=
-fragmented messages, can we relax
 / optimize this rule to be NDATA must be used for all *fragmented* message=
s, while non-fragmented messages continue to use DATA?</div>
<div><br>
</div>
</div>
</blockquote>
<div>This will cost in performance in SCTP SW =C2=A0- optionality costs in =
the processing paths.</div>
<div>But it is true that the extra 8 bytes also costs some. Are you mostly =
concerned about the 8 bytes from a running cache footprint perspective or f=
rom</div>
<div>a wire perspective ?</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div></div>
<div>Proposed change to the next-to-last paragraph of section 1.1:</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>=C2=A0 =C2=A0The support of the N-DATA chunk is negotiated during the =
association</div>
<div>=C2=A0 =C2=A0setup using the Supported Extensions Parameter as defined=
 in</div>
<div>=C2=A0 =C2=A0[RFC5061].=C2=A0 If N-DATA support has been negotiated fo=
r an association</div>
<div><b>=C2=A0 =C2=A0N-DATA chunks are used for all user-messages and no DA=
TA chunks.</b> =C2=A0It</div>
<div>=C2=A0 =C2=A0should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>=C2=A0 =C2=A0coexistence of associations using DATA chunks and associa=
tions using</div>
<div>=C2=A0 =C2=A0N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>=C2=A0 =C2=A0The support of the N-DATA chunk is negotiated during the =
association</div>
<div>=C2=A0 =C2=A0setup using the Supported Extensions Parameter as defined=
 in</div>
<div>=C2=A0 =C2=A0[RFC5061].=C2=A0 If N-DATA support has been negotiated fo=
r an association</div>
<div><b>=C2=A0 =C2=A0N-DATA chunks are used for all fragmented=C2=A0user me=
ssages, and</b></div>
<div><b>=C2=A0 =C2=A0DATA chunks are used for all non-fragmented user messa=
ges. =C2=A0</b>It</div>
<div>=C2=A0 =C2=A0should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>=C2=A0 =C2=A0coexistence of associations using DATA chunks and associa=
tions using</div>
<div>=C2=A0 =C2=A0N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>2. Fragmented messages can=E2=80=99t be interleaved.</div>
</div>
</blockquote>
<div>=C2=A0</div>
<div>This is not correct. They will be interleaved with all messages sent o=
n other streams.</div>
<div>Usage of multiple streams is really a prerequisite to avoid HOL. Furth=
er, usage of multiple streams is=C2=A0</div>
<div>the best way to enforce differences in the priority of different messa=
ges.</div>
<div><br>
</div>
<div>Personally I would have like for there to be closer coupling in betwee=
n ndata and SCTP-PR in that I would like for</div>
<div>the message priority (of SCTP-PR) to be inherited from the stream prio=
rity if nothing else is specified.</div>
<div>I have made this request towards the ndata author, but it may have bee=
n off list.</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>This significantly dilutes the value of NDATA. </div>
</div>
</blockquote>
<div><br>
</div>
<div>Do you require to use one stream only ?<br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Apps that truly care about head of line blocking can=E2=80=99t rely on=
 NDATA at all.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Se above.=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><span style=3D"font-family:arial;font-size:small;color:rgb(34,34,34)">=
=C2=A0</span></div>
</div>
</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>They must implement app layer fragmentation with messages well below c=
ommon MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harm=
ful for these apps, since it is 8 bytes closer to exceeding the MTU, forcin=
g SCTP fragments and hence risking
 HOL blocking. To avoid this, can we relax this rule to allow interleaving =
fragmented messages, since MID is already part of NDATA?</div>
</div>
</blockquote>
<div>We already have the stream concept why do we need now also a new conce=
pt. Also we would then need to control which and what to control the interl=
eaving with.I.e. what to give priority. Yes perhaps we could use the messag=
e priority, but the =C2=A0right thing
 in SCTP is to use the stream concept which is already there !!</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><br>
</div>
<div>
<div>Proposed change to the last paragraph of section 3.1:</div>
</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>=C2=A0 =C2=A0The sender <b>MUST NOT</b> have more than one ordered fra=
gmented message</div>
<div>=C2=A0 =C2=A0being produced in any one stream.=C2=A0 The sender <b>MUS=
T NOT</b> have more than</div>
<div>=C2=A0 =C2=A0one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>=C2=A0 =C2=A0The sender MAY have <b>one ordered and one unordered frag=
mented message</b></div>
<div>=C2=A0 =C2=A0being produced within a single stream.=C2=A0 At any time =
multiple streams</div>
<div>=C2=A0 =C2=A0MAY be producing <b>an ordered or unordered fragmented me=
ssage</b>.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>=C2=A0 =C2=A0The sender <b>MAY</b> have more than one ordered fragment=
ed message</div>
<div>=C2=A0 =C2=A0being produced in any one stream.=C2=A0 The sender <b>MAY=
</b> have more than</div>
<div>=C2=A0 =C2=A0one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>=C2=A0 =C2=A0The sender MAY have <b>multiple=C2=A0ordered and=C2=A0uno=
rdered fragmented messages</b></div>
<div>=C2=A0 =C2=A0being produced within a single stream.=C2=A0 At any time =
multiple streams</div>
<div>=C2=A0 =C2=A0MAY be producing <b>multiple ordered or unordered fragmen=
ted messages</b>.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</span>
</div>

</blockquote></div><br></div>

--001a11c261dce0f0d405069610cb--


From nobody Wed Oct 29 18:19:14 2014
Return-Path: <weixinpeng@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDCBB1ACEED for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 PpFZbVhPLbUO for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:18:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16A411ACEEA for <tsvwg@ietf.org>; Wed, 29 Oct 2014 18:18:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLB88114; Thu, 30 Oct 2014 01:18:48 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 30 Oct 2014 01:18:48 +0000
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.43]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 30 Oct 2014 09:18:40 +0800
From: Weixinpeng <weixinpeng@huawei.com>
To: Carry <liujianning1@126.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
Thread-Index: Ac/x8pHy687l8Ox9Sqy5u6/u9ubepAAyCX6gAEjzMYA=
Date: Thu, 30 Oct 2014 01:18:38 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46D8435EE@nkgeml507-mbx.china.huawei.com>
References: <mailman.4002.1414420223.2945.tsvwg@ietf.org> <000301cff2bb$11c20d90$354628b0$@com>
In-Reply-To: <000301cff2bb$11c20d90$354628b0$@com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/hgbdr5uG-2DQDg2fVHa0CVu3XLc
Cc: Weixinpeng <weixinpeng@huawei.com>
Subject: Re: [tsvwg] New Version Notification for draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Oct 2014 01:18:52 -0000

Hi,
Please see my answers inline.
Thanks!

Regards,
-Xinpeng

>-----Original Message-----
>From: Carry [mailto:liujianning1@126.com]
>Sent: Tuesday, October 28, 2014 10:26 PM
>To: tsvwg@ietf.org
>Cc: Weixinpeng
>Subject: Re: [tsvwg] New Version Notification for
>draft-wei-tsvwg-tunnel-congestion-feedback-03.txt
>
>Hi,
>I have had a review of the document, and there are some questions to be
>clarified:
>1. It seems that after egress fed back the congestion volume information, =
the
>ingress still won't have any information about the congestion information =
on
>specific traffic flow?
[Wei] Yes, what we want to do is conveying the overall congestion status in=
formation in tunnel to the ingress,
because the packets are randomly marked by routers, so when a packet is mar=
ked as CE, we cannot say that the congestion is caused by that packet.
>
>2.In real deployment, more than one tunnels would be concatenated together
>to form a path of traffic, so how to deal with this kind of situation?
[Wei] Currently, we just focus on the scenario of one tunnel, and we believ=
e it is easy to extend from one tunnel to concatenated tunnels.
>
>Thanks!
>BR
>- Jianning
>
>
>


From nobody Wed Oct 29 18:36:59 2014
Return-Path: <mzanaty@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6221C1ACF55 for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ByKA4sTeFHQI for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:36:53 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 708291ACF56 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 18:36:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21882; q=dns/txt; s=iport; t=1414632998; x=1415842598; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Osev/I/gXZRnnhUn8+BgMZcePYYNVwsmsR2bVYZdMo4=; b=Px9vBERWZ6oBFhWDnTvil88A2UReK4uygvVSTtMKeiMuzU6HeF01uQQP kpIf76kkgbYxOFLQNW+23N48svLfUm8o8x6nR2xaeTWwMB2JfIsufdaAP AwyNHjv6mR1pkScM8svW29fhLJRyP46u5728YBHt8jlRqvxnP2mOnlDmv U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAN+UUVStJA2M/2dsb2JhbABcgkhGgSwE1g8CgRgWAQEBAQF9hAMBAQR5EAIBCD8HMhQRAgQOBRuIJsgKAQEBAQEBBAEBAQEBAQEBARmQOFgGAYRLBY9ugh+LXYExg0qDL44WgX4ggVpsgQZCgQMBAQE
X-IronPort-AV: E=Sophos;i="5.07,281,1413244800";  d="scan'208,217";a="364581001"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP; 30 Oct 2014 01:36:37 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s9U1abe7029306 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Oct 2014 01:36:37 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.159]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 20:36:37 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Thread-Topic: [tsvwg] SCTP NDATA draft
Thread-Index: AQHP8+HxsJui5Nlz7UyqZBwm3+7Yvg==
Date: Thu, 30 Oct 2014 01:36:36 +0000
Message-ID: <D0770ACE.3D4E5%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com> <D0769E4A.3D378%mzanaty@cisco.com> <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com>
In-Reply-To: <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.82.222.42]
Content-Type: multipart/alternative; boundary="_000_D0770ACE3D4E5mzanatyciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/N05IlMr6ayZ6RlvPOvyEr_7ulrY
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Oct 2014 01:36:56 -0000

--_000_D0770ACE3D4E5mzanatyciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi authors,

I assume MID is a serial message id incremented for each message (ordered o=
r unordered) on the stream, and was added because SID+SSN is insufficient a=
s a serial message id for unordered messages. Is that assumption correct? I=
f so, it would be good text to add, since the draft does not define MID or =
describe its use. If incorrect, what is MID for?

Regards,
Mo

On 10/29/14, 5:01 PM, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.co=
m<mailto:karen.nielsen@tieto.com>> wrote:

Hi Mo,

I am all for finding a solution that fits the needs of the application. Jus=
t so that this is clear.

So you are actually not looking for ndata to support the interleaving prope=
rty (or that perhaps also, never mind)
but mainly to prevent RX and TX blocking for unordered delivery of larger t=
han PMTU messages,
possibly also for ordered delivery of such messages.

OK. If others agree then I suppose that ndata can be extended as you sugges=
t.
But reassembly costs, of course. Especially over a best effort network.
SCTP will have to filter and manage concurrent reassembly on yet one more i=
dentifier/dimension.

The application need not guess the MTU, the SCTP fragmentation point can be=
 read on the socket (yes it may vary, but it will not jump that much around=
 I suppose). In special cases where the application is anyway chopping up t=
he messages it will be wildly best to do this in subPMTU sizes.

BR, karen






On 29 October 2014 20:33, Mo Zanaty (mzanaty) <mzanaty@cisco.com<mailto:mza=
naty@cisco.com>> wrote:
Hi Karen,

I understand the design intent was to avoid one stream blocking another. Ho=
wever, I think that misses the true application need. It assumes applicatio=
ns only care about blocking of non-fragmented messages and don=92t care abo=
ut blocking of fragmented messages.

I think that assumption is wrong for most applications. It is certainly wro=
ng for rtcweb applications, where JSON objects would be a natural message p=
ayload for JS apps, and these can easily exceed common MTUs depending on th=
e complexity and verbosity of the JSON object.

If an application does not care about blocking, it does not need NDATA. If =
it cares, it must create a new stream for every potentially fragmented mess=
age (which requires guessing the MTU) since that will block subsequent frag=
mented messages. It must also have a garbage collector to close those strea=
ms (or otherwise mark them reusable) after ensuring delivery with an app la=
yer ack.

That is far more overhead and complexity for both the application and the S=
CTP stack than simply implementing application layer fragmentation which de=
feats NDATA. Even more true for rtcweb applications since they have the ext=
ra overhead of DCEP to open/close bidirectional channels.

So applications which truly care about blocking will almost certainly imple=
ment application layer fragmentation rather than relying on NDATA (which wi=
ll block) or jumping through hoops to create new streams for each potential=
ly fragmented message.

It should be simple to fix NDATA to meet the true application need. The tex=
t change is dead simple. There is no protocol change, since MID is already =
part of NDATA. There is only implementation effort, which should be limited=
 to maintaining FSN state for multiple MIDs per stream rather than only one=
. That seems like a small effort for making NDATA actually useful for most =
applications.

Cheers,
Mo


On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.co=
m<mailto:karen.nielsen@tieto.com>> wrote:

Hi Mo,

Please find feedback from my side below.

BR, Karen

On 29 October 2014 02:18, Mo Zanaty (mzanaty) <mzanaty@cisco.com<mailto:mza=
naty@cisco.com>> wrote:
Hi,
While reviewing this draft for becoming mandatory in rtcweb data channels, =
I see two issues, which are independent of rtcweb.

1. If negotiated, NDATA must be used for all messages. The NDATA format req=
uires 8 more bytes than DATA (for MID+FSN). But these extra 8 bytes are onl=
y useful for fragmented messages. To avoid this overhead for small non-frag=
mented messages, can we relax / optimize this rule to be NDATA must be used=
 for all *fragmented* messages, while non-fragmented messages continue to u=
se DATA?

This will cost in performance in SCTP SW  - optionality costs in the proces=
sing paths.
But it is true that the extra 8 bytes also costs some. Are you mostly conce=
rned about the 8 bytes from a running cache footprint perspective or from
a wire perspective ?

Proposed change to the next-to-last paragraph of section 1.1:

OLD:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all user-messages and no DATA chunks.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

NEW:
   The support of the N-DATA chunk is negotiated during the association
   setup using the Supported Extensions Parameter as defined in
   [RFC5061].  If N-DATA support has been negotiated for an association
   N-DATA chunks are used for all fragmented user messages, and
   DATA chunks are used for all non-fragmented user messages.  It
   should be noted, that an SCTP implementation needs to support the
   coexistence of associations using DATA chunks and associations using
   N-DATA chunks.

2. Fragmented messages can=92t be interleaved.

This is not correct. They will be interleaved with all messages sent on oth=
er streams.
Usage of multiple streams is really a prerequisite to avoid HOL. Further, u=
sage of multiple streams is
the best way to enforce differences in the priority of different messages.

Personally I would have like for there to be closer coupling in between nda=
ta and SCTP-PR in that I would like for
the message priority (of SCTP-PR) to be inherited from the stream priority =
if nothing else is specified.
I have made this request towards the ndata author, but it may have been off=
 list.


This significantly dilutes the value of NDATA.

Do you require to use one stream only ?

Apps that truly care about head of line blocking can=92t rely on NDATA at a=
ll.

Se above.

They must implement app layer fragmentation with messages well below common=
 MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harmful f=
or these apps, since it is 8 bytes closer to exceeding the MTU, forcing SCT=
P fragments and hence risking HOL blocking. To avoid this, can we relax thi=
s rule to allow interleaving fragmented messages, since MID is already part=
 of NDATA?
We already have the stream concept why do we need now also a new concept. A=
lso we would then need to control which and what to control the interleavin=
g with.I.e. what to give priority. Yes perhaps we could use the message pri=
ority, but the  right thing in SCTP is to use the stream concept which is a=
lready there !!

Proposed change to the last paragraph of section 3.1:

OLD:
   The sender MUST NOT have more than one ordered fragmented message
   being produced in any one stream.  The sender MUST NOT have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have one ordered and one unordered fragmented message
   being produced within a single stream.  At any time multiple streams
   MAY be producing an ordered or unordered fragmented message.

NEW:
   The sender MAY have more than one ordered fragmented message
   being produced in any one stream.  The sender MAY have more than
   one un-ordered fragmented message being produced in any one stream.
   The sender MAY have multiple ordered and unordered fragmented messages
   being produced within a single stream.  At any time multiple streams
   MAY be producing multiple ordered or unordered fragmented messages.

Regards,
Mo




--_000_D0770ACE3D4E5mzanatyciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <803ECCAEB89B2F4B85BE32216B54655F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-fami=
ly: Arial, sans-serif;">
<div>Hi authors,</div>
<div><br>
</div>
<div>I assume MID is a serial message id incremented for each message (orde=
red or unordered) on the stream, and was added because SID&#43;SSN is insuf=
ficient as a serial message id for unordered messages. Is that assumption c=
orrect? If so, it would be good text
 to add, since the draft does not define MID or describe its use. If incorr=
ect, what is MID for?</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>On 10/29/14, 5:01 PM, Karen Elisabeth Egede Nielsen &lt;<a href=3D"mai=
lto:karen.nielsen@tieto.com">karen.nielsen@tieto.com</a>&gt; wrote:</div>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Hi Mo,
<div><br>
</div>
<div>I am all for finding a solution that fits the needs of the application=
. Just so that this is clear.</div>
<div><br>
</div>
<div>So you are actually not looking for ndata to support the interleaving =
property (or that perhaps also, never mind)</div>
<div>but mainly to prevent RX and TX blocking for unordered delivery of lar=
ger than PMTU messages,&nbsp;</div>
<div>possibly also for ordered delivery of such messages.&nbsp;</div>
<div><br>
</div>
<div>OK. If others agree then I suppose that ndata can be extended as you s=
uggest.&nbsp;</div>
<div>But reassembly costs, of course. Especially over a best effort network=
.</div>
<div>SCTP will have to filter and manage concurrent reassembly on yet one m=
ore identifier/dimension.<br>
</div>
<div><br>
</div>
<div>The application need not guess the MTU, the SCTP fragmentation point c=
an be read on the socket (yes it may vary, but it will not jump that much a=
round I suppose). In special cases where the application is anyway chopping=
 up the messages it will be wildly
 best to do this in subPMTU sizes.</div>
<div><br>
</div>
<div>BR, karen</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 29 October 2014 20:33, Mo Zanaty (mzanaty) <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:mzanaty@cisco.com" target=3D"_blank">mzanaty@cisco.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi Karen,</div>
<div><br>
</div>
<div>I understand the design intent was to avoid one stream blocking anothe=
r. However, I think that misses the true application need. It assumes appli=
cations only care about blocking of non-fragmented messages and don=92t car=
e about blocking of fragmented messages.</div>
<div><br>
</div>
<div>I think that assumption is wrong for most applications. It is certainl=
y wrong for rtcweb applications, where JSON objects would be a natural mess=
age payload for JS apps, and these can easily exceed common MTUs depending =
on the complexity and verbosity
 of the JSON object.</div>
<div><br>
</div>
<div>If an application does not care about blocking, it does not need NDATA=
. If it cares, it must create a new stream for every potentially fragmented=
 message (which requires guessing the MTU) since that will block subsequent=
 fragmented messages. It must also
 have a garbage collector to close those streams (or otherwise mark them re=
usable) after ensuring delivery with an app layer ack.</div>
<div><br>
</div>
<div>That is far more overhead and complexity for both the application and =
the SCTP stack than simply implementing application layer fragmentation whi=
ch defeats NDATA. Even more true for rtcweb applications since they have th=
e extra overhead of DCEP to open/close
 bidirectional channels.</div>
<div><br>
</div>
<div>So applications which truly care about blocking will almost certainly =
implement application layer fragmentation rather than relying on NDATA (whi=
ch will block) or jumping through hoops to create new streams for each pote=
ntially fragmented message.</div>
<div><br>
</div>
<div>It should be simple to fix NDATA to meet the true application need. Th=
e text change is dead simple. There is no protocol change, since MID is alr=
eady part of NDATA. There is only implementation effort, which should be li=
mited to maintaining FSN state for
 multiple MIDs per stream rather than only one. That seems like a small eff=
ort for making NDATA actually useful for most applications.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Mo</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div>
<div>On 10/29/14, 3:50 AM, Karen Elisabeth Egede Nielsen &lt;<a href=3D"mai=
lto:karen.nielsen@tieto.com" target=3D"_blank">karen.nielsen@tieto.com</a>&=
gt; wrote:</div>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Hi Mo,
<div><br>
</div>
<div>Please find feedback from my side below.</div>
<div><br>
</div>
<div>BR, Karen<br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 29 October 2014 02:18, Mo Zanaty (mzanaty) <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:mzanaty@cisco.com" target=3D"_blank">mzanaty@cisco.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Hi,</div>
<div>While reviewing this draft for becoming mandatory in rtcweb data chann=
els, I see two issues, which are independent of rtcweb.</div>
<div><br>
</div>
<div>1. If negotiated, NDATA must be used for all messages. The NDATA forma=
t requires 8 more bytes than DATA (for MID&#43;FSN). But these extra 8 byte=
s are only useful for fragmented messages. To avoid this overhead for small=
 non-fragmented messages, can we relax
 / optimize this rule to be NDATA must be used for all *fragmented* message=
s, while non-fragmented messages continue to use DATA?</div>
<div><br>
</div>
</div>
</blockquote>
<div>This will cost in performance in SCTP SW &nbsp;- optionality costs in =
the processing paths.</div>
<div>But it is true that the extra 8 bytes also costs some. Are you mostly =
concerned about the 8 bytes from a running cache footprint perspective or f=
rom</div>
<div>a wire perspective ?</div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div></div>
<div>Proposed change to the next-to-last paragraph of section 1.1:</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061].&nbsp; If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all user-messages and no DA=
TA chunks.</b> &nbsp;It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The support of the N-DATA chunk is negotiated during the =
association</div>
<div>&nbsp; &nbsp;setup using the Supported Extensions Parameter as defined=
 in</div>
<div>&nbsp; &nbsp;[RFC5061].&nbsp; If N-DATA support has been negotiated fo=
r an association</div>
<div><b>&nbsp; &nbsp;N-DATA chunks are used for all fragmented&nbsp;user me=
ssages, and</b></div>
<div><b>&nbsp; &nbsp;DATA chunks are used for all non-fragmented user messa=
ges. &nbsp;</b>It</div>
<div>&nbsp; &nbsp;should be noted, that an SCTP implementation needs to sup=
port the</div>
<div>&nbsp; &nbsp;coexistence of associations using DATA chunks and associa=
tions using</div>
<div>&nbsp; &nbsp;N-DATA chunks.</div>
</div>
<div><br>
</div>
<div>2. Fragmented messages can=92t be interleaved.</div>
</div>
</blockquote>
<div>&nbsp;</div>
<div>This is not correct. They will be interleaved with all messages sent o=
n other streams.</div>
<div>Usage of multiple streams is really a prerequisite to avoid HOL. Furth=
er, usage of multiple streams is&nbsp;</div>
<div>the best way to enforce differences in the priority of different messa=
ges.</div>
<div><br>
</div>
<div>Personally I would have like for there to be closer coupling in betwee=
n ndata and SCTP-PR in that I would like for</div>
<div>the message priority (of SCTP-PR) to be inherited from the stream prio=
rity if nothing else is specified.</div>
<div>I have made this request towards the ndata author, but it may have bee=
n off list.</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>This significantly dilutes the value of NDATA. </div>
</div>
</blockquote>
<div><br>
</div>
<div>Do you require to use one stream only ?<br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>Apps that truly care about head of line blocking can=92t rely on NDATA=
 at all.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Se above.&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><span style=3D"font-family:arial;font-size:small;color:rgb(34,34,34)">=
&nbsp;</span></div>
</div>
</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div>They must implement app layer fragmentation with messages well below c=
ommon MTUs to avoid blocking, hence defeating NDATA. NDATA is arguably harm=
ful for these apps, since it is 8 bytes closer to exceeding the MTU, forcin=
g SCTP fragments and hence risking
 HOL blocking. To avoid this, can we relax this rule to allow interleaving =
fragmented messages, since MID is already part of NDATA?</div>
</div>
</blockquote>
<div>We already have the stream concept why do we need now also a new conce=
pt. Also we would then need to control which and what to control the interl=
eaving with.I.e. what to give priority. Yes perhaps we could use the messag=
e priority, but the &nbsp;right thing
 in SCTP is to use the stream concept which is already there !!</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:12px;font-fam=
ily:Arial,sans-serif">
<div><br>
</div>
<div>
<div>Proposed change to the last paragraph of section 3.1:</div>
</div>
<div><br>
</div>
<div>OLD:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MUST NOT</b> have more than one ordered fra=
gmented message</div>
<div>&nbsp; &nbsp;being produced in any one stream.&nbsp; The sender <b>MUS=
T NOT</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>one ordered and one unordered frag=
mented message</b></div>
<div>&nbsp; &nbsp;being produced within a single stream.&nbsp; At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>an ordered or unordered fragmented me=
ssage</b>.</div>
</div>
<div><br>
</div>
<div>NEW:</div>
<div>
<div>&nbsp; &nbsp;The sender <b>MAY</b> have more than one ordered fragment=
ed message</div>
<div>&nbsp; &nbsp;being produced in any one stream.&nbsp; The sender <b>MAY=
</b> have more than</div>
<div>&nbsp; &nbsp;one un-ordered fragmented message being produced in any o=
ne stream.</div>
<div>&nbsp; &nbsp;The sender MAY have <b>multiple&nbsp;ordered and&nbsp;uno=
rdered fragmented messages</b></div>
<div>&nbsp; &nbsp;being produced within a single stream.&nbsp; At any time =
multiple streams</div>
<div>&nbsp; &nbsp;MAY be producing <b>multiple ordered or unordered fragmen=
ted messages</b>.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Mo</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D0770ACE3D4E5mzanatyciscocom_--


From nobody Wed Oct 29 18:50:27 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54931ACF8C for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 s3AEJ9fKkd1v for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 18:50:22 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 665831ACF84 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 18:50:22 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9U1oD2N025288; Wed, 29 Oct 2014 19:50:13 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9U1oDh0014162; Wed, 29 Oct 2014 19:50:13 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9U1oD1V014161; Wed, 29 Oct 2014 19:50:13 -0600
Date: Wed, 29 Oct 2014 19:50:13 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Message-ID: <20141030015013.GB10436@openss7.org>
Mail-Followup-To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com> <D0769E4A.3D378%mzanaty@cisco.com> <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com> <D0770ACE.3D4E5%mzanaty@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D0770ACE.3D4E5%mzanaty@cisco.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/4rQnwqNPNoLIN1TYlhLVp8SjP1Q
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 30 Oct 2014 01:50:25 -0000

Mo,

Mo Zanaty (mzanaty) wrote:                 (Thu, 30 Oct 2014 01:36:36)
>    Hi authors,
> 
>    I assume MID is a serial message id incremented for each message
>    (ordered or unordered) on the stream, and was added because SID+SSN is
>    insufficient as a serial message id for unordered messages. Is that
>    assumption correct? If so, it would be good text to add, since the
>    draft does not define MID or describe its use. If incorrect, what is
>    MID for?

I think that it was more becuase the B and E bits are insufficient to
identify an interior fragment (ordererd or unordered).

Nevertheless, I agree that fragments from one stream should not block
fragments from another (ordered or otherwise).  I even think that an
unordered fragment should not block another message in the same stream.

That is a +1 for your changes.

There was no need for that restriction in the first place for senders on
ordered streams: NDATA (or whatever we are calling it now) simply makes
it easier for the receiver to do partial delivery and avoids some degree
of blocking at the receiver.  I agree that it should also remove all
restrictions from unordered message both within and between streams.  But
we should be careful that the language is still consistent throughout the
document.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Wed Oct 29 19:03:34 2014
Return-Path: <mzanaty@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09A041ACFBE for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 19:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 mN2E71yyR-mq for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 19:03:30 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17FBA1ACF8E for <tsvwg@ietf.org>; Wed, 29 Oct 2014 19:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1715; q=dns/txt; s=iport; t=1414634610; x=1415844210; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=baC4yVjZvPZRHHBsswF5uTUG8BQdvJBFGQ8oJ76DeaA=; b=EBdzqO1ykyQrnA5iU8qt6Xs8RZDmwBXcUvXv6w8eA6vI9U8ozzr7+oMv beQUcuT8Vbm0ZUgTHYUD98gjay3IY1KMBBJ8diE5VZMTjOO3EPx6q0Q4e BG4v8f1V2aOoFJ0Gs9PoQfjdK9M1B+z3CTlrUBmDP/V6uZbuXqHGDSJHd g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAG2bUVStJV2S/2dsb2JhbABSCoMOVFgEzjKHUQKBGRYBAQEBAX2EAwEBBDo/EAIBCDYQMiUCBA4FiEHIEQEBAQEBAQEBAQEBAQEBAQEBG5A0XAeESwWSDYtdgTGRBoQJg3hsgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,282,1413244800"; d="scan'208";a="91596790"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-8.cisco.com with ESMTP; 30 Oct 2014 02:03:29 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s9U23Smx012367 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Oct 2014 02:03:28 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.159]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0195.001; Wed, 29 Oct 2014 21:03:28 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: "bidulock@openss7.org" <bidulock@openss7.org>
Thread-Topic: [tsvwg] SCTP NDATA draft
Thread-Index: AQHP8+WxPoBlafDzHUKa2H8QSduyFw==
Date: Thu, 30 Oct 2014 02:03:27 +0000
Message-ID: <D077135F.3D50A%mzanaty@cisco.com>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com> <D0769E4A.3D378%mzanaty@cisco.com> <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com> <D0770ACE.3D4E5%mzanaty@cisco.com> <20141030015013.GB10436@openss7.org>
In-Reply-To: <20141030015013.GB10436@openss7.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [10.82.222.42]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <55B9A3B095DF8140B73638B988611234@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/HYwtMRz9jXHU44sM08aq9tkSf7s
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Oct 2014 02:03:32 -0000

I thought FSN was for serializing interior fragments while MID was for
serializing all messages on the stream. Or maybe even globally across all
streams like TSN? All I know for sure is it is a Message Identifier!  ;)

Mo

On 10/29/14, 9:50 PM, Brian F. G. Bidulock <bidulock@openss7.org> wrote:

Mo,

Mo Zanaty (mzanaty) wrote:                 (Thu, 30 Oct 2014 01:36:36)
>    Hi authors,
>=20
>    I assume MID is a serial message id incremented for each message
>    (ordered or unordered) on the stream, and was added because SID+SSN is
>    insufficient as a serial message id for unordered messages. Is that
>    assumption correct? If so, it would be good text to add, since the
>    draft does not define MID or describe its use. If incorrect, what is
>    MID for?

I think that it was more becuase the B and E bits are insufficient to
identify an interior fragment (ordererd or unordered).

Nevertheless, I agree that fragments from one stream should not block
fragments from another (ordered or otherwise).  I even think that an
unordered fragment should not block another message in the same stream.

That is a +1 for your changes.

There was no need for that restriction in the first place for senders on
ordered streams: NDATA (or whatever we are calling it now) simply makes
it easier for the receiver to do partial delivery and avoids some degree
of blocking at the receiver.  I agree that it should also remove all
restrictions from unordered message both within and between streams.  But
we should be careful that the language is still consistent throughout the
document.

--brian

--=20
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Wed Oct 29 21:59:14 2014
Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D001AD007 for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 21:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 vAMldmLaeasa for <tsvwg@ietfa.amsl.com>; Wed, 29 Oct 2014 21:59:11 -0700 (PDT)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F40A1ACE16 for <tsvwg@ietf.org>; Wed, 29 Oct 2014 21:59:11 -0700 (PDT)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9U4x4wg026072; Wed, 29 Oct 2014 22:59:04 -0600
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s9U4x4EP016426; Wed, 29 Oct 2014 22:59:04 -0600
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id s9U4x3eI016425; Wed, 29 Oct 2014 22:59:03 -0600
Date: Wed, 29 Oct 2014 22:59:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Message-ID: <20141030045903.GC10436@openss7.org>
Mail-Followup-To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>, Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <D075B8BB.3D24D%mzanaty@cisco.com> <CAChjaGzH_ciBKgbPkEqMAH_inzQZ4j3t6wiSsZ=9-qm4PAsMNg@mail.gmail.com> <D0769E4A.3D378%mzanaty@cisco.com> <CAChjaGya2DXTumzR4t4McxLMhA9n1jDaBjMPpcm9wToNy0Y8Qg@mail.gmail.com> <D0770ACE.3D4E5%mzanaty@cisco.com> <20141030015013.GB10436@openss7.org> <D077135F.3D50A%mzanaty@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D077135F.3D50A%mzanaty@cisco.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/4FnnOW-ozkFKzeOoOnkmA6t4rdg
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] SCTP NDATA draft
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
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: Thu, 30 Oct 2014 04:59:13 -0000

Mo,

Mo Zanaty (mzanaty) wrote:         (Thu, 30 Oct 2014 02:03:27)
> I thought FSN was for serializing interior fragments while MID was for
> serializing all messages on the stream. Or maybe even globally across all
> streams like TSN? All I know for sure is it is a Message Identifier!  ;)

Sorry, I reversed them...  Nevertheless, I still agree with your
objective of not blocking any fragments with any other fragments
as there is sufficient information to avoid blocking in all cases.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/


From nobody Fri Oct 31 10:11:30 2014
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C4BB1A0043 for <tsvwg@ietfa.amsl.com>; Fri, 31 Oct 2014 10:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 UzCdHv232KJH for <tsvwg@ietfa.amsl.com>; Fri, 31 Oct 2014 10:11:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 79D451A01C6 for <tsvwg@ietf.org>; Fri, 31 Oct 2014 10:11:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141031171120.4440.17485.idtracker@ietfa.amsl.com>
Date: Fri, 31 Oct 2014 10:11:20 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/0jnOujI1GZRN5_QulbN3Jo17VWI
Subject: [tsvwg] Milestones changed for tsvwg WG
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 31 Oct 2014 17:11:25 -0000

Changed milestone "Submit 'SCTP PR Polices' as a PS RFC", resolved as
"Done".

URL: http://datatracker.ietf.org/wg/tsvwg/charter/

