
From nobody Wed Apr  1 03:22:54 2015
Return-Path: <bob.briscoe@bt.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 6B8121A8A4B for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.089
X-Spam-Level: 
X-Spam-Status: No, score=0.089 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 0GiwZXeLWBhU for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:22:49 -0700 (PDT)
Received: from hubrelay-by-03.bt.com (hubrelay-by-03.bt.com [62.7.242.139]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84A21A903A for <tsvwg@ietf.org>; Wed,  1 Apr 2015 03:22:41 -0700 (PDT)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR03-UKBR.bt.com (10.216.161.35) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 1 Apr 2015 11:22:35 +0100
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 1 Apr 2015 11:22:35 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.3.181.6; Wed, 1 Apr 2015 11:22:33 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.178.68])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id t31AMU7K013470; Wed, 1 Apr 2015 11:22:31 +0100
Message-ID: <201504011022.t31AMU7K013470@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 1 Apr 2015 11:16:36 +0100
To: "Arunachalam, Swaminathan (NSN - US/Irving)" <swaminathan.arunachalam@nsn.com>, Helen Parsons <helenparsons@google.com>, Shahid Akhtar <shahid.akhtar@alcatel-lucent.com>, "ext Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>, Ankur Jain <jankur@google.com>, "Cosimini Peter, Vodafone Group" <Peter.Cosimini@vodafone.com>, "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>, "Klas, Guenter, Vodafone Group" <Guenter.Klas@vodafone.com>, Andreas Terzis <aterzis@google.com>, "Sprecher, Nurit" <nurit.sprecher@nsn.com>, "Gopal, Ram" <ram.gopal@nsn.com>,  "Szilagyi, Peter" <peter.1.szilagyi@nsn.com>, "Vulkan, Csaba" <csaba.vulkan@nsn.com>
From: Bob Briscoe <bob.briscoe@bt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MEzkVSqFeFuqyNb-eYaLHkmcp9Y>
Cc: iccrg IRTF list <iccrg@cs.ucl.ac.uk>, tsvwg IETF list <tsvwg@ietf.org>
Subject: [tsvwg] Mobile Throughput Guidance: reading list
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, 01 Apr 2015 10:22:50 -0000

Folks,

When you presented these two drafts in tsvwg last week, there were a 
number of suggestions for further reading:
* draft-sprecher-mobile-tg-exposure-req-arch
* draft-flinck-mobile-throughput-guidance

RFC6077 "Open Issues in Internet Congestion Control" provides most if 
not all these references in one place. It gives a good grounding in 
all the pitfalls and problems surrounding explicit-rate guidance both 
from a control perspective, and the security and scalability of the 
various signalling approaches that have been proposed.

Admittedly it's a little dated (it was brought up to date just before 
it was published in 2011, even though it was started a few years 
earlier). So some issues have been partially addressed since then. 
But most are still open.

Also, you may be able to get round some of the problems by limiting 
applicability, e.g. by placing the source next to the RAN, etc.

Cheers


Bob


________________________________________________________________
Bob Briscoe,                                                  BT  


From nobody Wed Apr  1 04:42:05 2015
Return-Path: <rs@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 8C86B1A8974 for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 LG4yRx8LyxmL for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 04:42:01 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77FA71A898A for <tsvwg@ietf.org>; Wed,  1 Apr 2015 04:42:00 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.11,503,1422950400"; d="scan'208,217"; a="33945495"
Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx141-out.netapp.com with ESMTP; 01 Apr 2015 04:41:44 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.995.29; Wed, 1 Apr 2015 04:41:43 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com ([::1]) by hioexcmbx05-prd.hq.netapp.com ([fe80::29f7:3e3f:78c5:a0bc%21]) with mapi id 15.00.0995.031; Wed, 1 Apr 2015 04:41:44 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "draft-ietf-tsvwg-ecn-encap-guidelines@tools.ietf.org" <draft-ietf-tsvwg-ecn-encap-guidelines@tools.ietf.org>
Thread-Topic: Review draft-ietf-tsvwg-ecn-encap-guidelines
Thread-Index: AdBsY8BxOHVA7fk0RXmQ49Ip2cU8oQ==
Date: Wed, 1 Apr 2015 11:41:43 +0000
Message-ID: <c72725b7d5ba4619b190d9b29a64db6c@hioexcmbx05-prd.hq.netapp.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.122.56.79]
Content-Type: multipart/alternative; boundary="_000_c72725b7d5ba4619b190d9b29a64db6chioexcmbx05prdhqnetappc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/b9_1o122Sb0-lS9mUE2hRIGHlkk>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tsvwg] Review draft-ietf-tsvwg-ecn-encap-guidelines
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, 01 Apr 2015 11:42:04 -0000

--_000_c72725b7d5ba4619b190d9b29a64db6chioexcmbx05prdhqnetappc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bob, Pat, John,

I've reviewed this document; As is well known, I'm a big fan of ECN and sup=
port this draft.

A few nits and word-smithings:

Sec 1, 3rd para:

s/(v4 & v6)/(v4 and v6)/


5th para:


"However, this has often be more due to the inability of the original
   TCP protocol to saturate the links"

Better:

However, this has often more to do with the inability of the TCP protocol i=
n the (New)Reno variant to saturate the links.

8th para:
s/most tricky aspect/most delicate aspect/


s/congestion would just deteriorate further/congestion would build up furth=
er/ (deteriorating congestion may not be unambiguous; same 2 sentences furt=
her)

Sec 2, PDU

s/&/and/

Move the definition of Load Regulator forward by 2 items (ECN-PDU refer to =
that).


Sec 4,

Definition of "Null"

Would that include networks which are virtually loss-less (eg. FibreChannel=
 with credit-based transmission schemes [FCVI and FC-IP are two schemes to =
run IP over this type of network]), or (theoretical) optimal Flow-Control e=
nabled Ethernet networks, and perhaps Infiniband (not too familiar with tha=
t)? I'm trying to decipher what packet network nodes "cannot experience con=
gestion". Perhaps a slightly expanded text giving an concrete example would=
 help here. Reading section 4.4 seems to indicate my examples might be the =
ones you had in mind.

Sec 4.1., 2nd para

s/3 & 4/3, and 4/

7th para:


s/"However, in ATM, this is only as part " / ... only a part/


s/ layer--the/layer -- the/

Sec 4.3, 2nd para:


s/approaching congestion or congested/approaching congestion or is congeste=
d/





Sec 5.4, last para:



s/future use through new standards actions./... new standards body actions.=
/





Section 7:



Would there be any value in discussing a hypothetical "feed-back and up" mo=
de? Without loss for non-ECT-PDUs and marking of inner headers for ECT-PDUs=
?


















Richard Scheffenegger

--_000_c72725b7d5ba4619b190d9b29a64db6chioexcmbx05prdhqnetappc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered 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;}
/* 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";}
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";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:DE-AT;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[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=3D"DE-AT" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Bob, Pat, John,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;ve reviewed this docume=
nt; As is well known, I&#8217;m a big fan of ECN and support this draft.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">A few nits and word-smithings:<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sec 1, 3<sup>rd</sup> para:<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/(v4 &amp; v6)/(v4 and v6)/<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">5<sup>th</sup> para:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US">&#8220;</span>=
<span lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">However, this h=
as often be more due to the inability of the original<o:p></o:p></span></pr=
e>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN-=
US" style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;color:bla=
ck;mso-fareast-language:DE-AT">&nbsp;&nbsp; TCP protocol to saturate the li=
nks&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Better: <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, this has often more to=
 do with the inability of the TCP protocol in the (New)Reno variant to satu=
rate the links.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">8<sup>th</sup> para:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/most tricky aspect/most delic=
ate aspect/<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US">s/</span><span=
 lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">congestion would jus=
t deteriorate further/congestion would build up further/ (deteriorating con=
gestion may not be unambiguous; same 2 sentences further)<o:p></o:p></span>=
</pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sec 2, PDU<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/&amp;/and/<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Move the definition of Load Reg=
ulator forward by 2 items (ECN-PDU refer to that).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sec 4,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Definition of &#8220;Null&#8221=
;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Would that include networks whi=
ch are virtually loss-less (eg. FibreChannel with credit-based transmission=
 schemes [FCVI and FC-IP are two schemes to run IP over this type of networ=
k]), or (theoretical) optimal Flow-Control
 enabled Ethernet networks, and perhaps Infiniband (not too familiar with t=
hat)? I&#8217;m trying to decipher what packet network nodes &#8220;cannot =
experience congestion&#8221;. Perhaps a slightly expanded text giving an co=
ncrete example would help here. Reading section 4.4
 seems to indicate my examples might be the ones you had in mind.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sec 4.1., 2<sup>nd</sup> para<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/3 &amp; 4/3, and 4/<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">7<sup>th</sup> para:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US">s/&#8220;</spa=
n><span lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">However, in A=
TM, this is only as part &#8220; / &#8230; only a part/<o:p></o:p></span></=
pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US">s/</span><span=
 lang=3D"EN-US" style=3D"font-size:12.0pt;color:black"> layer--the/layer --=
 the/<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sec 4.3, 2<sup>nd</sup> para:<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black">s/approaching congestion or congested/approaching =
congestion or is congested/<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black">Sec 5.4, last para:<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black">s/future use through new standards actions./&#8230=
; new standards body actions./<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">Section 7:<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black">Would there be any value in discussing a hypotheti=
cal &#8220;feed-back and up&#8221; mode? Without loss for non-ECT-PDUs and =
marking of inner headers for ECT-PDUs?<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:12.0pt;color:black"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:9.0pt;fon=
t-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#454545;mso-fareast=
-language:DE-AT">Richard Scheffenegger<o:p></o:p></span></b></p>
</div>
</body>
</html>

--_000_c72725b7d5ba4619b190d9b29a64db6chioexcmbx05prdhqnetappc_--


From nobody Wed Apr  1 07:58:00 2015
Return-Path: <Kevin.Smith@vodafone.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 4D53A1A001B for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:41:22 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_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 O9l7aL-LVJAS for <tsvwg@ietfa.amsl.com>; Wed,  1 Apr 2015 03:41:18 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.118]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9A821A000D for <tsvwg@ietf.org>; Wed,  1 Apr 2015 03:41:17 -0700 (PDT)
Received: from [193.109.255.99] by server-14.bemta-14.messagelabs.com id 26/90-31676-C4BCB155; Wed, 01 Apr 2015 10:41:16 +0000
X-Env-Sender: Kevin.Smith@vodafone.com
X-Msg-Ref: server-12.tower-48.messagelabs.com!1427884875!8855820!1
X-Originating-IP: [195.232.244.135]
X-StarScan-Received: 
X-StarScan-Version: 6.13.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25737 invoked from network); 1 Apr 2015 10:41:15 -0000
Received: from mailout03.vodafone.com (HELO mailout03.vodafone.com) (195.232.244.135) by server-12.tower-48.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  1 Apr 2015 10:41:15 -0000
Received: from mailint02.vodafone.com (mailint02.vodafone.com [195.232.244.199]) by mailout03.vodafone.com (Postfix) with ESMTP id 3lH3wW1NNnz17HNP; Wed,  1 Apr 2015 12:41:15 +0200 (CEST)
Received: from mailint02.vodafone.com (localhost [127.0.0.1]) by mailint02.vodafone.com (Postfix) with ESMTP id 3lH3wW01vyzQjPs; Wed,  1 Apr 2015 12:41:15 +0200 (CEST)
Received: from VOEXC04W.internal.vodafone.com (voexc04w.dc-ratingen.de [145.230.101.24]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint02.vodafone.com (Postfix) with ESMTPS id 3lH3wV6mPPzQk91; Wed,  1 Apr 2015 12:41:14 +0200 (CEST)
Received: from VOEXC28W.internal.vodafone.com (145.230.103.200) by VOEXC04W.internal.vodafone.com (145.230.101.24) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 1 Apr 2015 12:41:14 +0200
Received: from VOEXM17W.internal.vodafone.com ([169.254.1.163]) by voexc28w ([145.230.103.200]) with mapi id 14.03.0224.002; Wed, 1 Apr 2015 12:41:13 +0200
From: "Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>
To: "Sprecher, Nurit (Nokia - IL/Hod HaSharon)" <nurit.sprecher@nokia.com>, ext Bob Briscoe <bob.briscoe@bt.com>, "Arunachalam, Swaminathan (Nokia - US/Irving)" <swaminathan.arunachalam@nokia.com>, Helen Parsons <helenparsons@google.com>, Shahid Akhtar <shahid.akhtar@alcatel-lucent.com>, Ankur Jain <jankur@google.com>, "Cosimini, Peter, Vodafone Group" <Peter.Cosimini@vodafone.com>, "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia.com>, "Klas, Guenter, Vodafone Group" <Guenter.Klas@vodafone.com>, Andreas Terzis <aterzis@google.com>, "Gopal, Ram (Nokia - US/Mountain View)" <ram.gopal@nokia.com>, "Szilagyi, Peter 1. (Nokia - HU/Budapest)" <peter.1.szilagyi@nokia.com>, "Vulkan, Csaba (Nokia - HU/Budapest)" <csaba.vulkan@nokia.com>
Thread-Topic: Mobile Throughput Guidance: reading list
Thread-Index: AQHQbGXSUvAlkxNvqUSkhcbyyyIBrp031USAgAAiLQA=
Date: Wed, 1 Apr 2015 10:41:13 +0000
Message-ID: <A4BAAB326B17CE40B45830B745F70F108DFC6021@VOEXM17W.internal.vodafone.com>
References: <201504011022.t31AMU7K013470@bagheera.jungle.bt.co.uk> <9B067372C2434A429FBD4CF7F0E869FD206EDA9F@DEMUMBX009.nsn-intra.net>
In-Reply-To: <9B067372C2434A429FBD4CF7F0E869FD206EDA9F@DEMUMBX009.nsn-intra.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/zlYCNbcS2Fjj1_YzfSHzZSVILlY>
X-Mailman-Approved-At: Wed, 01 Apr 2015 07:57:59 -0700
Cc: iccrg IRTF list <iccrg@cs.ucl.ac.uk>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [tsvwg] Mobile Throughput Guidance: reading list
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, 01 Apr 2015 10:41:22 -0000

Hi Bob,

Indeed, many thanks for the advice here and at Dallas!

@All:
As well as RFC 6077 I would recommend browsing Bob's publications at: http:=
//bobbriscoe.net/pubs.html=20

Cheers
Kevin


-----Original Message-----
From: Sprecher, Nurit (Nokia - IL/Hod HaSharon) [mailto:nurit.sprecher@noki=
a.com]=20
Sent: 01 April 2015 11:37
To: ext Bob Briscoe; Arunachalam, Swaminathan (Nokia - US/Irving); Helen Pa=
rsons; Shahid Akhtar; Smith, Kevin, (R&D) Vodafone Group; Ankur Jain; Cosim=
ini, Peter, Vodafone Group; Flinck, Hannu (Nokia - FI/Espoo); Klas, Guenter=
, Vodafone Group; Andreas Terzis; Gopal, Ram (Nokia - US/Mountain View); Sz=
ilagyi, Peter 1. (Nokia - HU/Budapest); Vulkan, Csaba (Nokia - HU/Budapest)
Cc: tsvwg IETF list; iccrg IRTF list; Ben Niven-Jenkins
Subject: RE: Mobile Throughput Guidance: reading list

Thank you Bob for the reference and the good comment during the meeting.
We will look into the document (and may come with questions/ thoughts, etc.=
).
Best regards,
Nurit

-----Original Message-----
From: ext Bob Briscoe [mailto:bob.briscoe@bt.com]
Sent: Wednesday, April 01, 2015 1:17 PM
To: Arunachalam, Swaminathan (Nokia - US/Irving); Helen Parsons; Shahid Akh=
tar; ext Smith, Kevin, (R&D) Vodafone Group; Ankur Jain; Cosimini Peter, Vo=
dafone Group; Flinck, Hannu (Nokia - FI/Espoo); Klas, Guenter, Vodafone Gro=
up; Andreas Terzis; Sprecher, Nurit (Nokia - IL/Hod HaSharon); Gopal, Ram (=
Nokia - US/Mountain View); Szilagyi, Peter 1. (Nokia - HU/Budapest); Vulkan=
, Csaba (Nokia - HU/Budapest)
Cc: tsvwg IETF list; iccrg IRTF list; Ben Niven-Jenkins
Subject: Mobile Throughput Guidance: reading list

Folks,

When you presented these two drafts in tsvwg last week, there were a number=
 of suggestions for further reading:
* draft-sprecher-mobile-tg-exposure-req-arch
* draft-flinck-mobile-throughput-guidance

RFC6077 "Open Issues in Internet Congestion Control" provides most if not a=
ll these references in one place. It gives a good grounding in all the pitf=
alls and problems surrounding explicit-rate guidance both from a control pe=
rspective, and the security and scalability of the various signalling appro=
aches that have been proposed.

Admittedly it's a little dated (it was brought up to date just before it wa=
s published in 2011, even though it was started a few years earlier). So so=
me issues have been partially addressed since then.=20
But most are still open.

Also, you may be able to get round some of the problems by limiting applica=
bility, e.g. by placing the source next to the RAN, etc.

Cheers


Bob


________________________________________________________________
Bob Briscoe,                                                  BT =20


From nobody Thu Apr  2 07:35:38 2015
Return-Path: <magnus.westerlund@ericsson.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 A18591B2CDD; Thu,  2 Apr 2015 07:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 F_gtJ4HkeLoq; Thu,  2 Apr 2015 07:35:35 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D7ED1B2CDC; Thu,  2 Apr 2015 07:35:34 -0700 (PDT)
X-AuditID: c1b4fb30-f79996d000006ebb-91-551d53b4a8fb
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 4F.40.28347.4B35D155; Thu,  2 Apr 2015 16:35:32 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.210.2; Thu, 2 Apr 2015 16:35:31 +0200
Message-ID: <551D53AF.6050400@ericsson.com>
Date: Thu, 2 Apr 2015 16:35:27 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: <internet-drafts@ietf.org>, <i-d-announce@ietf.org>
References: <20150331163828.5530.2044.idtracker@ietfa.amsl.com>
In-Reply-To: <20150331163828.5530.2044.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHLMWRmVeSWpSXmKPExsUyM+Jvje6WYNlQg2MzpSyW7HrObPHhbq7F sTd32RyYPZYs+ckUwBjFZZOSmpNZllqkb5fAlXF7ewdrwQLlijOTJjI1MJ6W7mLk5JAQMJHo /XKUBcIWk7hwbz1bFyMXh5DAUUaJS6cbWCCcZYwSa543MnYxcnDwCmhLLFhUC9LAIqAisXzj frBmNgELiZs/GtlAbFGBYImf7buZQGxeAUGJkzOfsIC0igiYS2xaZgliMguISMz5rQFSISxg JTH/9Uew4UIC9hL/f6iAmJwCDhJfF+VDFGtKrN+lD1LMLCAv0bx1NjOILQR0SUNTB+sERsFZ SDbNQuiYhaRjASPzKkbR4tTipNx0IyO91KLM5OLi/Dy9vNSSTYzAAD245bfBDsaXzx0PMQpw MCrx8D64JRMqxJpYVlyZe4hRmoNFSZzXzvhQiJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG 2lmmndVch34lrbipfS1y/qfIsovvtS5vD5+8eM20gLR/Mxw83029f9HQp34754xCQUP5me+0 exgctp58wFW45p3xfeGOjyLKrBWf2Dyjlc8fXmeRXvt+GrfzUr738htajA7X7Cn2MJrv9WpJ 8pXVv9MnGfILT7aYGaJwST/1x7tlDH0r7/8oUWIpzkg01GIuKk4EAExwv0IxAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/zzItmgNYb5ilG0LlZZ-r1fRrRMg>
Cc: tsvwg@ietf.org
Subject: [tsvwg] Review of draft-ietf-tsvwg-circuit-breaker-01.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, 02 Apr 2015 14:35:36 -0000

Hi,

I have reviewed draft-ietf-tsvwg-circuit-breaker-01 and have some comments.

1. Section 1.1:

   o  Fast-Trip Circuit Breakers: The relatively short timescale used by
      this form of circuit breaker is intended to protect a flow or
      related group of flows.

   o  Slow-Trip Circuit Breakers: This circuit breaker utilises a longer
      timescale and is designed to protect traffic aggregates.

I reacted to the use of "protect" in these bullets. It is after all the
network that is protected. I wonder if you instead should use "operate
on" or something else that actual makes it clear that the CB types works
with different types of network traffics.

2. Section 3.1:

I saw Caitlin's comment on this draft version. This indicates that the
draft may need to make it clearer that the ingress point may actually be
a endpoint, client or server, not just tunnel ingresses. It depends on
the protocol and its application.

3. Section 3.1:

   2.  An Egress meter (at the receiver or tunnel egress) records the
       number/bytes received in each measurement interval.  This
       measures the supported load and may utilise other signals to
       detect the effect of congestion (e.g., loss/marking experienced
       over the path).

I wonder if you already here need a little more discussion of the
implications of marking rather than dropping packets in congestion
situations. The draft comes back to this later with more detail, but I
wonder if this needs special discussion, maybe even its own introduction
sub-section somewhere.

4. Section 4:
      The minimum time must be
      significantly longer than the time that current CC algorithms need
      to reduce their rate following detection of congestion (i.e.  many
      path RTTs).

I think this might need to be reformulated to talk not of the path RTT,
rather the longest RTT present in any flow part of the measured
aggregate as that is what can limit the speed of CC response for an
aggregate.

5. Section 5.1.1:

   The sender monitors reception of RTCP Reception Report (RR or XRR)
   packets that convey reception quality feedback information.

I think you might have to be slightly more correct in this sentence. I
would suggest:

   The sender monitors reception of RTCP Sender/Reception Report (SR/RR)
   packets that convey reception quality feedback information.

The RTCP XR can be skipped as the only RTCP XR used by the RTP CB is the
ECN report, and that is covered in the next sentence.

6. Section 5.1.1:

  1.  An RTP CB triggers on reported lack of progress.

"lack of progress" is a bit unclear in the context of RTP. I wonder if
you should rather say "on reported failure to receive any RTP packets
(Forward Path Timeout)."

7. Section 5.1.1:

    2.  An RTP CB triggers when no receiver reports messages are
       received.

Is okay, possibly to align with previous bullet add "(Return Path Timeout)"

8. Section 5.1.1:

   3.  An RTP CB uses a TFRC-style check and sets a hard upper limit to
       the long-term RTP throughput (over many RTTs).

If I didn't know what this CB is, I think I would fail to understand it
correctly. Because I think it is important to get across that the upper
throughput limit is recalculated on report interval basis and will be
fluctuating based on input. A possible rewrite could be:

  3. An RTP CB is based on TFRC-style throughput estimation, based on
loss event rate and RTT, and trigger if the RTP stream's usage is a
significantly more (10-times) the estimated rate.

9. Section 5.1.1:

I further wonder if one should include a paragraph to discuss the
scaling of the number of RTCP reporting intervals the CB works on. As
RTCP reporting intervals depends on both configured RTCP bandwidth
values as well as the endpoints view of the number of SSRCs in the
session and their roles (Senders or receivers only) this can vary
significantly from less than 1 ms to many seconds.


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Apr  2 07:41:54 2015
Return-Path: <magnus.westerlund@ericsson.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 95DE41B2D02 for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 07:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6bUJHKkC8Gif for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 07:41:51 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBEC31B2CF9 for <tsvwg@ietf.org>; Thu,  2 Apr 2015 07:41:40 -0700 (PDT)
X-AuditID: c1b4fb3a-f79146d0000070a3-0c-551d5522e221
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D7.46.28835.2255D155; Thu,  2 Apr 2015 16:41:39 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.210.2; Thu, 2 Apr 2015 16:41:38 +0200
Message-ID: <551D5521.3070403@ericsson.com>
Date: Thu, 2 Apr 2015 16:41:37 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Caitlin Bestler <cait@asomi.com>, <gorry@erg.abdn.ac.uk>
References: <20150331163828.5530.2044.idtracker@ietfa.amsl.com> <a8fb924ad1262f15492d7f1c8db1291e.squirrel@erg.abdn.ac.uk> a786d0bf-dfdf-4afd-baab-61d0e8f0a1e2@asomi.com>
In-Reply-To: <a8fb924ad1262f15492d7f1c8db1291e.squirrel@erg.abdn.ac.uk> a786d0bf-dfdf-4afd-baab-61d0e8f0a1e2@asomi.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUyM+Jvja5yqGyowYo2Dov1rxYxWbxum81o cezNXTYHZo+vU9awefR8fsHksWTJT6YA5igum5TUnMyy1CJ9uwSujPaJWQXn+Cr6j55gbGB8 wd3FyMkhIWAi8evBXHYIW0ziwr31bF2MXBxCAkcZJRpvr2OBcJYxSvw8dYMVpIpXQFui49h/ IJuDg0VAReLm0nqQMJuAhcTNH41sILaoQLDEz/bdTBDlghInZz5hAbFFBGwkrszdwQbSyiwg IjHntwZIWFjAQ6L//QNWiFWrGCWenrnBDFLDKVAusWdDNkS5psT6Xfog5cwC8hLNW2czg9hC QMc0NHWwTmAUnIVk2SyEjllIOhYwMq9iFC1OLS7OTTcy0kstykwuLs7P08tLLdnECAzdg1t+ W+1gPPjc8RCjAAejEg/vg1syoUKsiWXFlbmHGKU5WJTEee2MD4UICaQnlqRmp6YWpBbFF5Xm pBYfYmTi4JRqYJR/o3ZY3INV9OZOncCV224/Xu4784uPTeHxWI2/61LSlZIPuiz88yExMm6W vPi8Js/veY7xS9u/moZunVrNreSwqOAYR57i2efcz/b+VOOS5pkwO6wxXsL5V+JO/t8y175b /N3dFXHjmoVU/OMHs9kX9E07m6lmsVheeFveMxk70Ss9dm2LzJRYijMSDbWYi4oTAfQQhWM+ AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/q7npQXzhplKgJEIaUjpsi8Y6_78>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-circuit-breaker-01.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, 02 Apr 2015 14:41:52 -0000

On 2015-04-01 00:50, Caitlin Bestler wrote:
> Why is this draft "standards track"? This strikes me as
> informational.

It is intended to become an BCP. I think that is appropriate. I see this
as an requirements document with IETF consensus. Or if you will with
fangs. One can't simply ignore it, one have to relate to it due to its
status.

As I see it this document is quite similar to the UDP usage guidelines
that also is a BCP.

> 
> In particular, are they circuit-breaking devices deployed or
> contemplated that the authors feel would be out of compliance should
> this be adopted and would therefore be deprecated (or preferably
> deactivated)?
> 
> My sense from the presentations was that the draft sought to
> standardize terminology and improve our ability to talk about circuit
> breaker functionality, rather than to attempt to prescribe what these
> middle-boxes actually do. (Not  that middle-boxes are all that great
> with compliance to begin with).
> 

The requirements in section 4 is what is actually normative.

I also react to that you write middleboxes. The CB document discusses
all types of CBs. Both tunnel ingress to egress, but also CB being done
between any type of sender and receiver, independent if they are server,
clients, middleboxes, endpoint etc. But this should be clarified as I
commented in my review.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Apr  2 10:09:22 2015
Return-Path: <mattmathis@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 AF16A1AD366 for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:09:16 -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 e1yHySijTmut for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:09:15 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D261AD2C0 for <tsvwg@ietf.org>; Thu,  2 Apr 2015 10:09:13 -0700 (PDT)
Received: by obbgh1 with SMTP id gh1so131469420obb.1 for <tsvwg@ietf.org>; Thu, 02 Apr 2015 10:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=VJL9h8XqWeTsBCnRnu2psqADHyz7sTJcFFHqopnF5jY=; b=XgWoU7Ys7QZ8JlkfwBFwoOGyLJgrxIsVc/FxZJLR6WNkQF5lk0mDFgxCkCuiFnitom 3NeS0yaDyKVK0mIS3WxiYjM1RGalg3xDsFp8OPire4XEX8Pl/dzKwgOcf3Dxl0uzurQJ E47hzJfx9C3X/Faq0oRm2tsb4H70HrybUVdBNzQCJZaPTiFnWeP6wym/B8Vxru5Svds/ M3S8M28wxOYKq+TuITLb/E5YxTbU5HCysELjBf4stN5IQHiOBe8O4zPU5Kk6XW/Fdi/A rb/CH7Y2ceYTYStr0gWdse0zUaBMncb83o94wAq92EbxVNheJJTW1nvnbxZr6kKM7aW1 wmQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=VJL9h8XqWeTsBCnRnu2psqADHyz7sTJcFFHqopnF5jY=; b=N1x7/AZw9Rf49B+8mFzis6HWzPKbEx0w9NwwvXMQS9pAbJEcaGhy1o6xNLLI8H77is Amj9gnGidwLDavJPFVmlxAEaRiB8wE8M1nBqSuo4kEG/IbPC5t1Vo6Z1f2hu44wsGULE DUQWfPqVBN0dgfGkJIAw+LtZAdYszn0o4O4poPJJsVq8dJlsKu+GZLADmRI96dPq1x+I QSiPN5OAQXjE76kjB6aZKTwE41Q9xEAfaRvGG9HIdEKQrVmEQ4k9Hbx7R+js200/3wIo FMpkY2ZbpECkfBOvW6KrvtIPdrgMSP8MuYUCFRqRMvVJ7GZIubIGMk7qo9SsTGZGvEdZ Xjhg==
X-Gm-Message-State: ALoCoQloyDYV3unlQWm5tDKtWq2YSVIr7f9ObRd3XBNxkN/YLGcDQr65UXyJYLz3vuQZD1FoQin3
X-Received: by 10.60.123.83 with SMTP id ly19mr12674210oeb.8.1427994552653; Thu, 02 Apr 2015 10:09:12 -0700 (PDT)
MIME-Version: 1.0
References: <20150331163828.5530.2044.idtracker@ietfa.amsl.com> <a8fb924ad1262f15492d7f1c8db1291e.squirrel@erg.abdn.ac.uk> <551D5521.3070403@ericsson.com>
In-Reply-To: <551D5521.3070403@ericsson.com>
From: Matt Mathis <mattmathis@google.com>
Date: Thu, 02 Apr 2015 17:09:12 +0000
Message-ID: <CAH56bmCVjcq80JfGXtbGbZUoreL94dJDNssr5BxYyCMiw_2_Vg@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Caitlin Bestler <cait@asomi.com>, gorry@erg.abdn.ac.uk
Content-Type: multipart/alternative; boundary=047d7b5d54980d83700512c0e48a
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/XDNOWODn8YsvaLLR8hH3S91ve0M>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-circuit-breaker-01.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, 02 Apr 2015 17:09:16 -0000

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

For CBR applications, the correct answer to "What mandatory congestion
control are you using?" should be "A circuit breaker".  I believe that this
requires standards track.

On Thu, Apr 2, 2015 at 7:41 AM Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> On 2015-04-01 00:50, Caitlin Bestler wrote:
> > Why is this draft "standards track"? This strikes me as
> > informational.
>
> It is intended to become an BCP. I think that is appropriate. I see this
> as an requirements document with IETF consensus. Or if you will with
> fangs. One can't simply ignore it, one have to relate to it due to its
> status.
>
> As I see it this document is quite similar to the UDP usage guidelines
> that also is a BCP.
>
> >
> > In particular, are they circuit-breaking devices deployed or
> > contemplated that the authors feel would be out of compliance should
> > this be adopted and would therefore be deprecated (or preferably
> > deactivated)?
> >
> > My sense from the presentations was that the draft sought to
> > standardize terminology and improve our ability to talk about circuit
> > breaker functionality, rather than to attempt to prescribe what these
> > middle-boxes actually do. (Not  that middle-boxes are all that great
> > with compliance to begin with).
> >
>
> The requirements in section 4 is what is actually normative.
>
> I also react to that you write middleboxes. The CB document discusses
> all types of CBs. Both tunnel ingress to egress, but also CB being done
> between any type of sender and receiver, independent if they are server,
> clients, middleboxes, endpoint etc. But this should be clarified as I
> commented in my review.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>

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

<div dir=3D"ltr">For CBR applications, the correct answer to &quot;What man=
datory congestion control are you using?&quot; should be &quot;A circuit br=
eaker&quot;.=C2=A0 I believe that this requires standards track.<br></div><=
br><div class=3D"gmail_quote">On Thu, Apr 2, 2015 at 7:41 AM Magnus Westerl=
und &lt;<a href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund=
@ericsson.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2015-04-0=
1 00:50, Caitlin Bestler wrote:<br>
&gt; Why is this draft &quot;standards track&quot;? This strikes me as<br>
&gt; informational.<br>
<br>
It is intended to become an BCP. I think that is appropriate. I see this<br=
>
as an requirements document with IETF consensus. Or if you will with<br>
fangs. One can&#39;t simply ignore it, one have to relate to it due to its<=
br>
status.<br>
<br>
As I see it this document is quite similar to the UDP usage guidelines<br>
that also is a BCP.<br>
<br>
&gt;<br>
&gt; In particular, are they circuit-breaking devices deployed or<br>
&gt; contemplated that the authors feel would be out of compliance should<b=
r>
&gt; this be adopted and would therefore be deprecated (or preferably<br>
&gt; deactivated)?<br>
&gt;<br>
&gt; My sense from the presentations was that the draft sought to<br>
&gt; standardize terminology and improve our ability to talk about circuit<=
br>
&gt; breaker functionality, rather than to attempt to prescribe what these<=
br>
&gt; middle-boxes actually do. (Not=C2=A0 that middle-boxes are all that gr=
eat<br>
&gt; with compliance to begin with).<br>
&gt;<br>
<br>
The requirements in section 4 is what is actually normative.<br>
<br>
I also react to that you write middleboxes. The CB document discusses<br>
all types of CBs. Both tunnel ingress to egress, but also CB being done<br>
between any type of sender and receiver, independent if they are server,<br=
>
clients, middleboxes, endpoint etc. But this should be clarified as I<br>
commented in my review.<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 +46 10 7148287<br>
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
<br>
</blockquote></div>

--047d7b5d54980d83700512c0e48a--


From nobody Thu Apr  2 10:50:49 2015
Return-Path: <caitlin.bestler@nexenta.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 C1A3D1B2DA3 for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 ftbJPnb5ecq2 for <tsvwg@ietfa.amsl.com>; Thu,  2 Apr 2015 10:50:46 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41ADE1B2DA2 for <tsvwg@ietf.org>; Thu,  2 Apr 2015 10:50:46 -0700 (PDT)
Received: by padcy3 with SMTP id cy3so90764157pad.3 for <tsvwg@ietf.org>; Thu, 02 Apr 2015 10:50:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Es1s3Oj017Pl7HOLc0obFd9IU2DRZYMoUh7YYB2wyCI=; b=dfAsVPQuJLP5w3hkIdal1bseovBZfY1uMoRVhpZzrcynhVo+kf73vamESem5bwUg/k 616RauXs3RP95t1TF1hQ6m2UYlKWB1gix/YkIpdhsCO6l7CHvpy5qkS8HwdACX5cyQX5 N748hhZBlzbzqhABDcT9CR80RBYyHDKr2oLl4cc7zRckyIiCsTMXJ5khC2Jjr7m97LK9 66yUP3n1B7PZKuXyBVtpFZw5X2MZT/00wupiGlzobD+xdIV22EWpAdr16c6zLQKhNM1X BfpItX20FVnqFhm3MSAEKPIFhU1nSZmcbQebAXp5TSSlrdfnXxzLC+DrQHfPxqkLKi/9 p9Iw==
X-Gm-Message-State: ALoCoQlIEDIcPPKkJrDDKLIc6sGPyqGhXKkj0E6BifeFfOgiJngM0xTEpu7kTfNeOVuM0/o4HjiR
X-Received: by 10.70.39.73 with SMTP id n9mr46803516pdk.159.1427997045923; Thu, 02 Apr 2015 10:50:45 -0700 (PDT)
Received: from Macintosh-2.local (67-207-110-172.static.wiline.com. [67.207.110.172]) by mx.google.com with ESMTPSA id he10sm2279586pbc.18.2015.04.02.10.50.44 for <tsvwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2015 10:50:44 -0700 (PDT)
Message-ID: <551D817D.30404@nexenta.com>
Date: Thu, 02 Apr 2015 10:50:53 -0700
From: Caitlin Bestler <caitlin.bestler@nexenta.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <mailman.894.1427994559.11274.tsvwg@ietf.org>
In-Reply-To: <mailman.894.1427994559.11274.tsvwg@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/_smIfVNTSJ2_W8x_e_BEqvF5frI>
Subject: Re: [tsvwg] Circuti Breaker as BCP or as compulsory standard
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 Apr 2015 17:50:47 -0000

On 4/2/15 10:09 AM, Matt Matthis wrote:
>
> For CBR applications, the correct answer to "What mandatory congestion
> control are you using?" should be "A circuit breaker".  I believe that this
> requires standards track.
>
> On Thu, Apr 2, 2015 at 7:41 AM Magnus Westerlund <
> magnus.westerlund@ericsson.com> wrote:
>
>
A BCP strikes me as fitting. It will also be far easier to reach consensus
that this document represents the best common practices than it will
be to reach consensus on what MUST be provisioned for all flows.

For example, we have reference architectures where customers are
expected to apply L2 rate shaping to limit the aggregate storage flows
in each L2 subnet. Coming up with MUST/SHOULD language that is
inclusive of this type of solution as well as per-flow end-to-end metering
will be very difficult even though both serve the same goal of protecting
"other" traffic from the subject traffic getting out of control.


From nobody Mon Apr  6 17:51:19 2015
Return-Path: <touch@isi.edu>
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 A341A1ACE7E for <tsvwg@ietfa.amsl.com>; Mon,  6 Apr 2015 17:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 W-EtKfjMkO5g for <tsvwg@ietfa.amsl.com>; Mon,  6 Apr 2015 17:51:16 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C62801ACE7A for <tsvwg@ietf.org>; Mon,  6 Apr 2015 17:51:16 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t370okLj004192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 6 Apr 2015 17:50:46 -0700 (PDT)
Message-ID: <552329E4.7060703@isi.edu>
Date: Mon, 06 Apr 2015 17:50:44 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Caitlin Bestler <cait@asomi.com>, gorry@erg.abdn.ac.uk
References: <20150331163828.5530.2044.idtracker@ietfa.amsl.com> <a8fb924ad1262f15492d7f1c8db1291e.squirrel@erg.abdn.ac.uk> a786d0bf-dfdf-4afd-baab-61d0e8f0a1e2@asomi.com>
In-Reply-To: <a8fb924ad1262f15492d7f1c8db1291e.squirrel@erg.abdn.ac.uk> a786d0bf-dfdf-4afd-baab-61d0e8f0a1e2@asomi.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/uMsoyRMwoBkmoWK8fE_pEZaeKoM>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-circuit-breaker-01.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 Apr 2015 00:51:17 -0000

On 3/31/2015 3:50 PM, Caitlin Bestler wrote:
> Why is this draft "standards track"? This strikes me as informational.

It's intended as BCP, and that seems to be most appropriate for this
kind of recommendation.

Joe


From nobody Tue Apr  7 07:49:33 2015
Return-Path: <nagesh.shamnur@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 CF32A1B35EF for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 07:01:02 -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 6yweddfLzyBc for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 07:00:58 -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 07DFB1B35E3 for <tsvwg@ietf.org>; Tue,  7 Apr 2015 07:00:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUO66957; Tue, 07 Apr 2015 14:00:51 +0000 (GMT)
Received: from SZXEML428-HUB.china.huawei.com (10.82.67.183) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 7 Apr 2015 15:00:49 +0100
Received: from SZXEML512-MBS.china.huawei.com ([169.254.8.253]) by szxeml428-hub.china.huawei.com ([10.82.67.183]) with mapi id 14.03.0158.001; Tue, 7 Apr 2015 22:00:41 +0800
From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
Thread-Index: AQHQWrO+FK3Kue/eZk+9NATFV6YBL51BvvUQ
Date: Tue, 7 Apr 2015 14:00:41 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com>
In-Reply-To: <20150309215448.3165.2371.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.148.238]
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/JCVM7oCi9fvF8aGTjHQ7IC7jiPA>
X-Mailman-Approved-At: Tue, 07 Apr 2015 07:49:32 -0700
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 07 Apr 2015 14:01:03 -0000

SGkgR3JvdXAsDQoJV2hpbGUgZ29pbmcgdGhyb3VnaCB0aGUgZHJhZnQsIGRyYWZ0LWlldGYtdHN2
d2ctc2N0cC1uZGF0YS0wMyBJIGdvdCB0aGUgZm9sbG93aW5nIGRvdWJ0IGFuZCBoZW5jZSB0aGlz
IG1haWwuDQoNCglXaHkgTUlEIGlzIHJlcXVpcmVkIGV2ZW4gZm9yIHRoZSB1bm9yZGVyZWQgZGF0
YSwgYnkgdGhlIG5hdHVyZSBvZiB0aGUgdW5vcmRlcmVkIGRhdGEsIGl0IGNhbiBjb21lIGluIGFu
eSBvcmRlciwgYW5kIGhlbmNlIFNTTi9NSUQgaXMgbm90IHJlcXVpcmVkLiANCg0KCSBJcyBpdCB0
aGF0LCBpdCBDYW4gTUlEIGJlIHVzZWQgb25seSBpbiBjYXNlIG9mIHVub3JkZXJlZCBmcmFnbWVu
dCBkYXRhIGFuZCBub3QgZm9yIGFsbCB0aGUgdW5vcmRlcmVkIGRhdGE/IEJ1dCBhZ2FpbiwgYXMg
cGVyIHRoZSBkcmFmdCwgdGhlIHNlbmRlciBNVVNUIE5PVCBoYXZlIG1vcmUgdGhhbiBvbmUgdW4t
b3JkZXJlZCBmcmFnbWVudGVkIG1lc3NhZ2UgYmVpbmcgcHJvZHVjZWQgaW4gYW55IG9uZSBzdHJl
YW0sIHNvIGluIHRoYXQgY2FzZSBhbHNvLCBNSUQgd291bGRuJ3QgYmUgcmVxdWlyZWQuIA0KDQoJ
SXMgdGhlcmUgc29tZXRoaW5nIHdoaWNoIEkgYW0gbWlzc2luZyBoZXJlPw0KDQpSZWdhcmRzLA0K
TmFnZXNoLg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogdHN2d2cgW21haWx0
bzp0c3Z3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgaW50ZXJuZXQtZHJhZnRzQGll
dGYub3JnDQpTZW50OiAxMCBNYXJjaCAyMDE1IDA1OjU1DQpUbzogaS1kLWFubm91bmNlQGlldGYu
b3JnDQpDYzogdHN2d2dAaWV0Zi5vcmcNClN1YmplY3Q6IFt0c3Z3Z10gSS1EIEFjdGlvbjogZHJh
ZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLTAzLnR4dA0KDQoNCkEgTmV3IEludGVybmV0LURyYWZ0
IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmll
cy4NCiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBUcmFuc3BvcnQgQXJlYSBXb3Jr
aW5nIEdyb3VwIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQoNCiAgICAgICAgVGl0bGUgICAg
ICAgICAgIDogU3RyZWFtIFNjaGVkdWxlcnMgYW5kIFVzZXIgTWVzc2FnZSBJbnRlcmxlYXZpbmcg
Zm9yIHRoZSBTdHJlYW0gQ29udHJvbCBUcmFuc21pc3Npb24gUHJvdG9jb2wNCiAgICAgICAgQXV0
aG9ycyAgICAgICAgIDogUmFuZGFsbCBSLiBTdGV3YXJ0DQogICAgICAgICAgICAgICAgICAgICAg
ICAgIE1pY2hhZWwgVHVleGVuDQogICAgICAgICAgICAgICAgICAgICAgICAgIFNhbHZhdG9yZSBM
b3JldG8NCiAgICAgICAgICAgICAgICAgICAgICAgICAgUm9iaW4gU2VnZ2VsbWFubg0KCUZpbGVu
YW1lICAgICAgICA6IGRyYWZ0LWlldGYtdHN2d2ctc2N0cC1uZGF0YS0wMy50eHQNCglQYWdlcyAg
ICAgICAgICAgOiAxNA0KCURhdGUgICAgICAgICAgICA6IDIwMTUtMDMtMDkNCg0KQWJzdHJhY3Q6
DQogICBUaGUgU3RyZWFtIENvbnRyb2wgVHJhbnNtaXNzaW9uIFByb3RvY29sIChTQ1RQKSBpcyBh
IG1lc3NhZ2Ugb3JpZW50ZWQNCiAgIHRyYW5zcG9ydCBwcm90b2NvbCBzdXBwb3J0aW5nIGFyYml0
cmFyeSBsYXJnZSB1c2VyIG1lc3NhZ2VzLg0KICAgSG93ZXZlciwgdGhlIHNlbmRlciBjYW4gbm90
IGludGVybGVhdmUgZGlmZmVyZW50IHVzZXIgbWVzc2FnZXMgd2hpY2gNCiAgIGNhdXNlcyBoZWFk
IG9mIGxpbmUgYmxvY2tpbmcgYXQgdGhlIHNlbmRlciBzaWRlLiAgVG8gb3ZlcmNvbWUgdGhpcw0K
ICAgbGltaXRhdGlvbiwgdGhpcyBkb2N1bWVudCBhZGRzIGEgbmV3IGRhdGEgY2h1bmsgdG8gU0NU
UC4NCg0KICAgV2hlbmV2ZXIgYW4gU0NUUCBzZW5kZXIgaXMgYWxsb3dlZCB0byBzZW5kIGEgdXNl
ciBkYXRhLCBpdCBjYW4NCiAgIHBvc3NpYmx5IGNob29zZSBmcm9tIG11bHRpcGxlIG91dGdvaW5n
IFNDVFAgc3RyZWFtcy4gIE11bHRpcGxlIHdheXMNCiAgIGZvciB0aGlzIHNlbGVjdGlvbiwgY2Fs
bGVkIHN0cmVhbSBzY2hlZHVsZXJzLCBhcmUgZGVmaW5lZC4gIFNvbWUgb2YNCiAgIHRoZW0gZG9u
J3QgcmVxdWlyZSB0aGUgc3VwcG9ydCBvZiB1c2VyIG1lc3NhZ2UgaW50ZXJsZWF2aW5nLCBzb21l
IGRvLg0KDQoNClRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0
IGlzOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi10c3Z3Zy1z
Y3RwLW5kYXRhLw0KDQpUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBh
dDoNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdHN2d2ctc2N0cC1uZGF0
YS0wMw0KDQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6
DQpodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLXRzdndnLXNjdHAt
bmRhdGEtMDMNCg0KDQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1p
bnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJz
aW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNCkludGVybmV0
LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCmZ0cDovL2Z0
cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQoNCg==


From nobody Tue Apr  7 08:01:52 2015
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 59B801B3692 for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 08:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 l7ORvZX7sbv1 for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 08:01:40 -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 0B1F61B36AC for <tsvwg@ietf.org>; Tue,  7 Apr 2015 08:01:39 -0700 (PDT)
Received: from [192.168.1.200] (p508F1706.dip0.t-ipconnect.de [80.143.23.6]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 391081C1623B0; Tue,  7 Apr 2015 17:01:36 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com>
Date: Tue, 7 Apr 2015 17:01:33 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com>
To: Nagesh shamnur <nagesh.shamnur@huawei.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/OBhlvZEPE3e1WZ_T5qHDJkkpXoc>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 07 Apr 2015 15:01:45 -0000

> On 07 Apr 2015, at 16:00, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>=20
> Hi Group,
> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I =
got the following doubt and hence this mail.
>=20
> 	Why MID is required even for the unordered data, by the nature =
of the unordered data, it can come in any order, and hence SSN/MID is =
not required.=20
If you have multiple fragments belonging to the same unordered message, =
you need an identifier for
that message. The MID is the same for all fragments of the same user =
message.
>=20
> 	 Is it that, it Can MID be used only in case of unordered =
fragment data and not for all the unordered data? But again, as per the =
draft, the sender MUST NOT have more than one un-ordered fragmented =
message being produced in any one stream, so in that case also, MID =
wouldn't be required.=20
That statement needs to be clarified. It means that the sender will not =
interleave two unordered fragmented
messages when breaking them into DATA chunks. However, this does not =
mean that there can't be multiple
unordered fragmented messages on the same stream in flight.

Best regards
Michael
>=20
> 	Is there something which I am missing here?
>=20
> Regards,
> Nagesh.
>=20
> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of =
internet-drafts@ietf.org
> Sent: 10 March 2015 05:55
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>=20
> 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.
>=20
>        Title           : Stream Schedulers and User Message =
Interleaving for the Stream Control Transmission Protocol
>        Authors         : Randall R. Stewart
>                          Michael Tuexen
>                          Salvatore Loreto
>                          Robin Seggelmann
> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
> 	Pages           : 14
> 	Date            : 2015-03-09
>=20
> Abstract:
>   The Stream Control Transmission Protocol (SCTP) is a message =
oriented
>   transport protocol supporting arbitrary large user messages.
>   However, the sender can not interleave different user messages which
>   causes head of line blocking at the sender side.  To overcome this
>   limitation, this document adds a new data chunk to SCTP.
>=20
>   Whenever an SCTP sender is allowed to send a user data, it can
>   possibly choose from multiple outgoing SCTP streams.  Multiple ways
>   for this selection, called stream schedulers, are defined.  Some of
>   them don't require the support of user message interleaving, some =
do.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>=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:
> ftp://ftp.ietf.org/internet-drafts/
>=20


From nobody Tue Apr  7 22:52:15 2015
Return-Path: <nagesh.shamnur@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 549AE1A00C3 for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 22:52:13 -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 BetmZqcIf2UX for <tsvwg@ietfa.amsl.com>; Tue,  7 Apr 2015 22:52:10 -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 7A5331A00A8 for <tsvwg@ietf.org>; Tue,  7 Apr 2015 22:52:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUP22762; Wed, 08 Apr 2015 05:52:08 +0000 (GMT)
Received: from SZXEML428-HUB.china.huawei.com (10.82.67.183) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 8 Apr 2015 06:52:08 +0100
Received: from SZXEML512-MBS.china.huawei.com ([169.254.8.253]) by szxeml428-hub.china.huawei.com ([10.82.67.183]) with mapi id 14.03.0158.001; Wed, 8 Apr 2015 13:52:01 +0800
From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
Thread-Index: AQHQWrO+FK3Kue/eZk+9NATFV6YBL51BvvUQ//+M/4CAAX1AMA==
Date: Wed, 8 Apr 2015 05:52:01 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de>
In-Reply-To: <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.148.238]
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/byyPIraOwzMsfyFtYcbGolbaX94>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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 Apr 2015 05:52:13 -0000

Hi Michael,
	Thanks for the answer. Please find my reply in-line.

Regards,
Nagesh.

-----Original Message-----
From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
Sent: 07 April 2015 23:02
To: Nagesh shamnur
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt

> On 07 Apr 2015, at 16:00, Nagesh shamnur <nagesh.shamnur@huawei.com> wrot=
e:
>=20
> Hi Group,
> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I got the =
following doubt and hence this mail.
>=20
> 	Why MID is required even for the unordered data, by the nature of the un=
ordered data, it can come in any order, and hence SSN/MID is not required.=
=20
If you have multiple fragments belonging to the same unordered message, you=
 need an identifier for that message. The MID is the same for all fragments=
 of the same user message.
>=20
> 	 Is it that, it Can MID be used only in case of unordered fragment data =
and not for all the unordered data? But again, as per the draft, the sender=
 MUST NOT have more than one un-ordered fragmented message being produced i=
n any one stream, so in that case also, MID wouldn't be required.=20
That statement needs to be clarified. It means that the sender will not int=
erleave two unordered fragmented messages when breaking them into DATA chun=
ks. However, this does not mean that there can't be multiple unordered frag=
mented messages on the same stream in flight.
In spite of that, for unordered messages, MID is not required. In case of D=
ATA message (earlier), for both fragmented and un-fragmented unordered mess=
ages, SSN was not required, and the receiver was able to reassemble with th=
e help of TSN, Begin and End Bits. Now in case of I-DATA chunk, since more =
than one un-ordered fragmented message cannot be interleaved, the same logi=
c as DATA chunk (TSN, B & E flags) can be used to reassemble. So, the MID c=
an be altogether removed for un-ordered messages in general.
=20
Best regards
Michael
>=20
> 	Is there something which I am missing here?
>=20
> Regards,
> Nagesh.
>=20
> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of=20
> internet-drafts@ietf.org
> Sent: 10 March 2015 05:55
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Transport Area Working Group Working Gro=
up of the IETF.
>=20
>        Title           : Stream Schedulers and User Message Interleaving =
for the Stream Control Transmission Protocol
>        Authors         : Randall R. Stewart
>                          Michael Tuexen
>                          Salvatore Loreto
>                          Robin Seggelmann
> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
> 	Pages           : 14
> 	Date            : 2015-03-09
>=20
> Abstract:
>   The Stream Control Transmission Protocol (SCTP) is a message oriented
>   transport protocol supporting arbitrary large user messages.
>   However, the sender can not interleave different user messages which
>   causes head of line blocking at the sender side.  To overcome this
>   limitation, this document adds a new data chunk to SCTP.
>=20
>   Whenever an SCTP sender is allowed to send a user data, it can
>   possibly choose from multiple outgoing SCTP streams.  Multiple ways
>   for this selection, called stream schedulers, are defined.  Some of
>   them don't require the support of user message interleaving, some do.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20


From nobody Wed Apr  8 05:26:03 2015
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 497F61B30BB; Wed,  8 Apr 2015 05:26:01 -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 kMOx3iCIhpE6; Wed,  8 Apr 2015 05:25:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8AB1A8BBF; Wed,  8 Apr 2015 05:25:59 -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.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150408122559.24328.89341.idtracker@ietfa.amsl.com>
Date: Wed, 08 Apr 2015 05:25:59 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/lzZb3GNAy40MD2uYEGeq9l8hsGI>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-02.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: Wed, 08 Apr 2015 12:26:01 -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           : UDP Usage Guidelines
        Authors         : Lars Eggert
                          Godred Fairhurst
                          Greg Shepherd
	Filename        : draft-ietf-tsvwg-rfc5405bis-02.txt
	Pages           : 42
	Date            : 2015-04-08

Abstract:
   The User Datagram Protocol (UDP) provides a minimal message-passing
   transport that has no inherent congestion control mechanisms.
   Because congestion control is critical to the stable operation of the
   Internet, applications and other protocols that choose to use UDP as
   an Internet transport must employ mechanisms to prevent congestion
   collapse and to establish some degree of fairness with concurrent
   traffic.  They may also need to implement additional mechanisms,
   depending on how they use UDP.

   This document provides guidelines on the use of UDP for the designers
   of applications, tunnels and other protocols that use UDP.
   Congestion control guidelines are a primary focus, but the document
   also provides guidance on other topics, including message sizes,
   reliability, checksums, middlebox traversal, the use of ECN, DSCPs,
   and ports.

   Some guidance is also applicable to the design of other protocols
   (e.g., protocols layered directly on IP or via IP-based tunnels),
   especially when these protocols do not themselves provide congestion
   control.

   If published as an RFC, this document will obsolete RFC5405.


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

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

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


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 Wed Apr  8 12:02:02 2015
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 5F5BE1B350A for <tsvwg@ietfa.amsl.com>; Wed,  8 Apr 2015 12:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eljBLO3DhBac for <tsvwg@ietfa.amsl.com>; Wed,  8 Apr 2015 12:01:59 -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 A53301B350F for <tsvwg@ietf.org>; Wed,  8 Apr 2015 12:01:58 -0700 (PDT)
Received: from [192.168.1.200] (p548180CA.dip0.t-ipconnect.de [84.129.128.202]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id CA3F51C104351; Wed,  8 Apr 2015 21:01:54 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com>
Date: Wed, 8 Apr 2015 21:01:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com>
To: Nagesh shamnur <nagesh.shamnur@huawei.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/8hIzRVYtmNs-9QXTojvVGozQ7C0>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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 Apr 2015 19:02:01 -0000

> On 08 Apr 2015, at 07:52, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>=20
> Hi Michael,
> 	Thanks for the answer. Please find my reply in-line.
>=20
> Regards,
> Nagesh.
>=20
> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
> Sent: 07 April 2015 23:02
> To: Nagesh shamnur
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>> On 07 Apr 2015, at 16:00, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>>=20
>> Hi Group,
>> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I =
got the following doubt and hence this mail.
>>=20
>> 	Why MID is required even for the unordered data, by the nature =
of the unordered data, it can come in any order, and hence SSN/MID is =
not required.=20
> If you have multiple fragments belonging to the same unordered =
message, you need an identifier for that message. The MID is the same =
for all fragments of the same user message.
>>=20
>> 	 Is it that, it Can MID be used only in case of unordered =
fragment data and not for all the unordered data? But again, as per the =
draft, the sender MUST NOT have more than one un-ordered fragmented =
message being produced in any one stream, so in that case also, MID =
wouldn't be required.=20
> That statement needs to be clarified. It means that the sender will =
not interleave two unordered fragmented messages when breaking them into =
DATA chunks. However, this does not mean that there can't be multiple =
unordered fragmented messages on the same stream in flight.
Hi Nagesh,

the point is that we want to allow to interleave messages from different =
streams. RFC 4960 does not
allow message interleaving at all. We don't see a need for interleaving =
multiple messages from the
same stream. This doesn't make sense for ordered messages and we don't =
think it is of much use
for unordered ones.
> In spite of that, for unordered messages, MID is not required. In case =
of DATA message (earlier), for both fragmented and un-fragmented =
unordered messages, SSN was not required, and the receiver was able to =
reassemble with the help of TSN, Begin and End Bits. Now in case of =
I-DATA chunk, since more than one un-ordered fragmented message cannot =
be interleaved, the same logic as DATA chunk (TSN, B & E flags) can be =
used to reassemble. So, the MID can be altogether removed for un-ordered =
messages in general.
But then you can't interleave messages from multiple streams. You would =
require consecutive TSN assignments.

Assume the sender sends two three unordered messages resulting in the =
following TSN assignments.

I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0]
I-DATA[flags=3DBEU;TSN=3D1;SID=3D1;MID=3D0;FSN=3D0]
I-DATA[flags=3DBEU;TSN=3D2;SID=3D1;MID=3D1;FSN=3D0]
I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D0;FSN=3D1]

Now assume that only the first and last message are received. With the =
MID, the receiver
knows that it has a complete message an can deliver it right away. =
Without the MID, the
receiver can't deliver the message, since the sender might have sent:

I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0]
I-DATA[flags=3DEU; TSN=3D1;SID=3D0;MID=3D0;FSN=3D0]
I-DATA[flags=3DBU; TSN=3D2;SID=3D0;MID=3D1;FSN=3D0]
I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D1;FSN=3D1]

and reassembling the first and last doesn't make sense.

Best regards
Michael
> Best regards
> Michael
>>=20
>> 	Is there something which I am missing here?
>>=20
>> Regards,
>> Nagesh.
>>=20
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of=20
>> internet-drafts@ietf.org
>> Sent: 10 March 2015 05:55
>> To: i-d-announce@ietf.org
>> Cc: tsvwg@ietf.org
>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>=20
>>=20
>> 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.
>>=20
>>       Title           : Stream Schedulers and User Message =
Interleaving for the Stream Control Transmission Protocol
>>       Authors         : Randall R. Stewart
>>                         Michael Tuexen
>>                         Salvatore Loreto
>>                         Robin Seggelmann
>> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
>> 	Pages           : 14
>> 	Date            : 2015-03-09
>>=20
>> Abstract:
>>  The Stream Control Transmission Protocol (SCTP) is a message =
oriented
>>  transport protocol supporting arbitrary large user messages.
>>  However, the sender can not interleave different user messages which
>>  causes head of line blocking at the sender side.  To overcome this
>>  limitation, this document adds a new data chunk to SCTP.
>>=20
>>  Whenever an SCTP sender is allowed to send a user data, it can
>>  possibly choose from multiple outgoing SCTP streams.  Multiple ways
>>  for this selection, called stream schedulers, are defined.  Some of
>>  them don't require the support of user message interleaving, some =
do.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>>=20
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>>=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:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>=20
>=20


From nobody Thu Apr  9 00:09:31 2015
Return-Path: <nagesh.shamnur@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 C7D411A1A12 for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:09:29 -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 27_YvBXLEU3b for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 00:09:27 -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 DC6511A1A02 for <tsvwg@ietf.org>; Thu,  9 Apr 2015 00:09:26 -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 BRE88581; Thu, 09 Apr 2015 07:09:23 +0000 (GMT)
Received: from SZXEML434-HUB.china.huawei.com (10.82.67.225) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Apr 2015 08:09:18 +0100
Received: from SZXEML512-MBS.china.huawei.com ([169.254.8.253]) by szxeml434-hub.china.huawei.com ([10.82.67.225]) with mapi id 14.03.0158.001; Thu, 9 Apr 2015 15:09:11 +0800
From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
Thread-Index: AQHQWrO+FK3Kue/eZk+9NATFV6YBL51BvvUQ//+M/4CAAX1AMIAAWDuAgAFQBxA=
Date: Thu, 9 Apr 2015 07:09:11 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB5284D050@szxeml512-mbs.china.huawei.com>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com> <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de>
In-Reply-To: <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.148.238]
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/xiNtOfD25_KkIS9HvPQEU97J1Zs>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 09 Apr 2015 07:09:29 -0000

-----Original Message-----
From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
Sent: 09 April 2015 03:02
To: Nagesh shamnur
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt

> On 08 Apr 2015, at 07:52, Nagesh shamnur <nagesh.shamnur@huawei.com> wrot=
e:
>=20
> Hi Michael,
> 	Thanks for the answer. Please find my reply in-line.
>=20
> Regards,
> Nagesh.
>=20
> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
> Sent: 07 April 2015 23:02
> To: Nagesh shamnur
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>> On 07 Apr 2015, at 16:00, Nagesh shamnur <nagesh.shamnur@huawei.com> wro=
te:
>>=20
>> Hi Group,
>> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I got the=
 following doubt and hence this mail.
>>=20
>> 	Why MID is required even for the unordered data, by the nature of the u=
nordered data, it can come in any order, and hence SSN/MID is not required.=
=20
> If you have multiple fragments belonging to the same unordered message, y=
ou need an identifier for that message. The MID is the same for all fragmen=
ts of the same user message.
>>=20
>> 	 Is it that, it Can MID be used only in case of unordered fragment data=
 and not for all the unordered data? But again, as per the draft, the sende=
r MUST NOT have more than one un-ordered fragmented message being produced =
in any one stream, so in that case also, MID wouldn't be required.=20
> That statement needs to be clarified. It means that the sender will not i=
nterleave two unordered fragmented messages when breaking them into DATA ch=
unks. However, this does not mean that there can't be multiple unordered fr=
agmented messages on the same stream in flight.
Hi Nagesh,

the point is that we want to allow to interleave messages from different st=
reams. RFC 4960 does not allow message interleaving at all. We don't see a =
need for interleaving multiple messages from the same stream. This doesn't =
make sense for ordered messages and we don't think it is of much use for un=
ordered ones.
> In spite of that, for unordered messages, MID is not required. In case of=
 DATA message (earlier), for both fragmented and un-fragmented unordered me=
ssages, SSN was not required, and the receiver was able to reassemble with =
the help of TSN, Begin and End Bits. Now in case of I-DATA chunk, since mor=
e than one un-ordered fragmented message cannot be interleaved, the same lo=
gic as DATA chunk (TSN, B & E flags) can be used to reassemble. So, the MID=
 can be altogether removed for un-ordered messages in general.
But then you can't interleave messages from multiple streams. You would req=
uire consecutive TSN assignments.

Assume the sender sends two three unordered messages resulting in the follo=
wing TSN assignments.

I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DBEU;TSN=
=3D1;SID=3D1;MID=3D0;FSN=3D0]
I-DATA[flags=3DBEU;TSN=3D2;SID=3D1;MID=3D1;FSN=3D0]
I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D0;FSN=3D1]

Now assume that only the first and last message are received. With the MID,=
 the receiver knows that it has a complete message an can deliver it right =
away. Without the MID, the receiver can't deliver the message, since the se=
nder might have sent:

I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DEU; TSN=
=3D1;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DBU; TSN=3D2;SID=3D0;MID=3D1;FS=
N=3D0] I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D1;FSN=3D1]

and reassembling the first and last doesn't make sense.
[Nagesh]: Thanks a lot for explaining things to me, now it makes more sense=
. In that case, is it possible to make the MID mandatory only for unordered=
 fragmented and unordered non-fragmented case, it can be ignored by both se=
nder and receiver. Since, the true nature of the unordered message can be r=
etained. Since having the MID for the unordered non-fragmented message is a=
ctually dummy and both sender and receiver wouldn't be able to take any act=
ions on that.
Best regards
Michael
> Best regards
> Michael
>>=20
>> 	Is there something which I am missing here?
>>=20
>> Regards,
>> Nagesh.
>>=20
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of=20
>> internet-drafts@ietf.org
>> Sent: 10 March 2015 05:55
>> To: i-d-announce@ietf.org
>> Cc: tsvwg@ietf.org
>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>=20
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>> This draft is a work item of the Transport Area Working Group Working Gr=
oup of the IETF.
>>=20
>>       Title           : Stream Schedulers and User Message Interleaving =
for the Stream Control Transmission Protocol
>>       Authors         : Randall R. Stewart
>>                         Michael Tuexen
>>                         Salvatore Loreto
>>                         Robin Seggelmann
>> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
>> 	Pages           : 14
>> 	Date            : 2015-03-09
>>=20
>> Abstract:
>>  The Stream Control Transmission Protocol (SCTP) is a message=20
>> oriented  transport protocol supporting arbitrary large user messages.
>>  However, the sender can not interleave different user messages which =20
>> causes head of line blocking at the sender side.  To overcome this =20
>> limitation, this document adds a new data chunk to SCTP.
>>=20
>>  Whenever an SCTP sender is allowed to send a user data, it can =20
>> possibly choose from multiple outgoing SCTP streams.  Multiple ways =20
>> for this selection, called stream schedulers, are defined.  Some of =20
>> them don't require the support of user message interleaving, some do.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>>=20
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of submis=
sion until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>=20
>=20


From nobody Thu Apr  9 01:53:20 2015
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 CD23E1AD357 for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 01:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 lgbZV9WmQjF7 for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 01:53:17 -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 B6EB41AD377 for <tsvwg@ietf.org>; Thu,  9 Apr 2015 01:53:16 -0700 (PDT)
Received: from [192.168.1.200] (p54818218.dip0.t-ipconnect.de [84.129.130.24]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 152B71C0ACF54; Thu,  9 Apr 2015 10:53:14 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4AC96705FB868F42B2075BA50F806DEB5284D050@szxeml512-mbs.china.huawei.com>
Date: Thu, 9 Apr 2015 10:53:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <21FA4EFC-8A6D-4655-8FC7-9AEB02B8696C@lurchi.franken.de>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com> <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284D050@szxeml512-mbs.china.huawei.com>
To: Nagesh shamnur <nagesh.shamnur@huawei.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/3WOXRz2MxuFHswnCEun9Wb7HY1s>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 09 Apr 2015 08:53:20 -0000

> On 09 Apr 2015, at 09:09, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>=20
>=20
> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
> Sent: 09 April 2015 03:02
> To: Nagesh shamnur
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>> On 08 Apr 2015, at 07:52, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>>=20
>> Hi Michael,
>> 	Thanks for the answer. Please find my reply in-line.
>>=20
>> Regards,
>> Nagesh.
>>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Sent: 07 April 2015 23:02
>> To: Nagesh shamnur
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>=20
>>> On 07 Apr 2015, at 16:00, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>>>=20
>>> Hi Group,
>>> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I =
got the following doubt and hence this mail.
>>>=20
>>> 	Why MID is required even for the unordered data, by the nature =
of the unordered data, it can come in any order, and hence SSN/MID is =
not required.=20
>> If you have multiple fragments belonging to the same unordered =
message, you need an identifier for that message. The MID is the same =
for all fragments of the same user message.
>>>=20
>>> 	 Is it that, it Can MID be used only in case of unordered =
fragment data and not for all the unordered data? But again, as per the =
draft, the sender MUST NOT have more than one un-ordered fragmented =
message being produced in any one stream, so in that case also, MID =
wouldn't be required.=20
>> That statement needs to be clarified. It means that the sender will =
not interleave two unordered fragmented messages when breaking them into =
DATA chunks. However, this does not mean that there can't be multiple =
unordered fragmented messages on the same stream in flight.
> Hi Nagesh,
>=20
> the point is that we want to allow to interleave messages from =
different streams. RFC 4960 does not allow message interleaving at all. =
We don't see a need for interleaving multiple messages from the same =
stream. This doesn't make sense for ordered messages and we don't think =
it is of much use for unordered ones.
>> In spite of that, for unordered messages, MID is not required. In =
case of DATA message (earlier), for both fragmented and un-fragmented =
unordered messages, SSN was not required, and the receiver was able to =
reassemble with the help of TSN, Begin and End Bits. Now in case of =
I-DATA chunk, since more than one un-ordered fragmented message cannot =
be interleaved, the same logic as DATA chunk (TSN, B & E flags) can be =
used to reassemble. So, the MID can be altogether removed for un-ordered =
messages in general.
> But then you can't interleave messages from multiple streams. You =
would require consecutive TSN assignments.
>=20
> Assume the sender sends two three unordered messages resulting in the =
following TSN assignments.
>=20
> I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0] =
I-DATA[flags=3DBEU;TSN=3D1;SID=3D1;MID=3D0;FSN=3D0]
> I-DATA[flags=3DBEU;TSN=3D2;SID=3D1;MID=3D1;FSN=3D0]
> I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D0;FSN=3D1]
>=20
> Now assume that only the first and last message are received. With the =
MID, the receiver knows that it has a complete message an can deliver it =
right away. Without the MID, the receiver can't deliver the message, =
since the sender might have sent:
>=20
> I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DEU; =
TSN=3D1;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DBU; =
TSN=3D2;SID=3D0;MID=3D1;FSN=3D0] I-DATA[flags=3DEU; =
TSN=3D3;SID=3D0;MID=3D1;FSN=3D1]
>=20
> and reassembling the first and last doesn't make sense.
> [Nagesh]: Thanks a lot for explaining things to me, now it makes more =
sense. In that case, is it possible to make the MID mandatory only for =
unordered fragmented and unordered non-fragmented case, it can be =
ignored by both sender and receiver. Since, the true nature of the =
unordered message can be retained. Since having the MID for the =
unordered non-fragmented message is actually dummy and both sender and =
receiver wouldn't be able to take any actions on that.
I agree, that for un-ordered, un-fragmented user messages the MID is not =
important for the receiver.
However, I don=E2=80=99t want to make the I-DATA chunk header a variable =
size header. So the field is always
there. =46rom my perspective, it is simpler to require the sender to =
fill in the field always by
incrementing it compared to state that it needs to be incremented =
always, except for un-ordered and
un-fragmented user messages. The receiver will just not make use of it.
I don=E2=80=99t see any benefit it setting the field to some special =
value (like 0) for un-ordered, un-fragmented.
However, it makes the code and testing more complex=E2=80=A6

Best regards
Michael
> Best regards
> Michael
>> Best regards
>> Michael
>>>=20
>>> 	Is there something which I am missing here?
>>>=20
>>> Regards,
>>> Nagesh.
>>>=20
>>> -----Original Message-----
>>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of=20
>>> internet-drafts@ietf.org
>>> Sent: 10 March 2015 05:55
>>> To: i-d-announce@ietf.org
>>> Cc: tsvwg@ietf.org
>>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>>=20
>>>=20
>>> 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.
>>>=20
>>>      Title           : Stream Schedulers and User Message =
Interleaving for the Stream Control Transmission Protocol
>>>      Authors         : Randall R. Stewart
>>>                        Michael Tuexen
>>>                        Salvatore Loreto
>>>                        Robin Seggelmann
>>> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
>>> 	Pages           : 14
>>> 	Date            : 2015-03-09
>>>=20
>>> Abstract:
>>> The Stream Control Transmission Protocol (SCTP) is a message=20
>>> oriented  transport protocol supporting arbitrary large user =
messages.
>>> However, the sender can not interleave different user messages which =
=20
>>> causes head of line blocking at the sender side.  To overcome this =20=

>>> limitation, this document adds a new data chunk to SCTP.
>>>=20
>>> Whenever an SCTP sender is allowed to send a user data, it can =20
>>> possibly choose from multiple outgoing SCTP streams.  Multiple ways =20=

>>> for this selection, called stream schedulers, are defined.  Some of =20=

>>> them don't require the support of user message interleaving, some =
do.
>>>=20
>>>=20
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>>>=20
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>>>=20
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>>>=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:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>=20
>>=20
>=20
>=20


From nobody Thu Apr  9 05:35:14 2015
Return-Path: <nagesh.shamnur@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 BEC481ACC88 for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:35:12 -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 RWR_veF9NSNY for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 05:35:09 -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 9FC8C1B29B9 for <tsvwg@ietf.org>; Thu,  9 Apr 2015 05:34:58 -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 BRF25537; Thu, 09 Apr 2015 12:34:57 +0000 (GMT)
Received: from SZXEML427-HUB.china.huawei.com (10.82.67.182) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Apr 2015 13:34:56 +0100
Received: from SZXEML512-MBS.china.huawei.com ([169.254.8.253]) by szxeml427-hub.china.huawei.com ([10.82.67.182]) with mapi id 14.03.0158.001; Thu, 9 Apr 2015 20:34:50 +0800
From: Nagesh shamnur <nagesh.shamnur@huawei.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
Thread-Index: AQHQWrO+FK3Kue/eZk+9NATFV6YBL51BvvUQ//+M/4CAAX1AMIAAWDuAgAFQBxD//5g/gIAAwxrQ
Date: Thu, 9 Apr 2015 12:34:51 +0000
Message-ID: <4AC96705FB868F42B2075BA50F806DEB5284D0BB@szxeml512-mbs.china.huawei.com>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com> <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284D050@szxeml512-mbs.china.huawei.com> <21FA4EFC-8A6D-4655-8FC7-9AEB02B8696C@lurchi.franken.de>
In-Reply-To: <21FA4EFC-8A6D-4655-8FC7-9AEB02B8696C@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.148.238]
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/UMseKiUN71q5fevZ8mHifpq4I0Q>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 09 Apr 2015 12:35:12 -0000

DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWljaGFlbCBUdWV4ZW4gW21haWx0
bzpNaWNoYWVsLlR1ZXhlbkBsdXJjaGkuZnJhbmtlbi5kZV0gDQpTZW50OiAwOSBBcHJpbCAyMDE1
IDE2OjUzDQpUbzogTmFnZXNoIHNoYW1udXINCkNjOiB0c3Z3Z0BpZXRmLm9yZw0KU3ViamVjdDog
UmU6IFt0c3Z3Z10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLTAzLnR4
dA0KDQo+IE9uIDA5IEFwciAyMDE1LCBhdCAwOTowOSwgTmFnZXNoIHNoYW1udXIgPG5hZ2VzaC5z
aGFtbnVyQGh1YXdlaS5jb20+IHdyb3RlOg0KPiANCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+IEZyb206IE1pY2hhZWwgVHVleGVuIFttYWlsdG86TWljaGFlbC5UdWV4ZW5AbHVy
Y2hpLmZyYW5rZW4uZGVdDQo+IFNlbnQ6IDA5IEFwcmlsIDIwMTUgMDM6MDINCj4gVG86IE5hZ2Vz
aCBzaGFtbnVyDQo+IENjOiB0c3Z3Z0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3RzdndnXSBJ
LUQgQWN0aW9uOiBkcmFmdC1pZXRmLXRzdndnLXNjdHAtbmRhdGEtMDMudHh0DQo+IA0KPj4gT24g
MDggQXByIDIwMTUsIGF0IDA3OjUyLCBOYWdlc2ggc2hhbW51ciA8bmFnZXNoLnNoYW1udXJAaHVh
d2VpLmNvbT4gd3JvdGU6DQo+PiANCj4+IEhpIE1pY2hhZWwsDQo+PiAJVGhhbmtzIGZvciB0aGUg
YW5zd2VyLiBQbGVhc2UgZmluZCBteSByZXBseSBpbi1saW5lLg0KPj4gDQo+PiBSZWdhcmRzLA0K
Pj4gTmFnZXNoLg0KPj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTog
TWljaGFlbCBUdWV4ZW4gW21haWx0bzpNaWNoYWVsLlR1ZXhlbkBsdXJjaGkuZnJhbmtlbi5kZV0N
Cj4+IFNlbnQ6IDA3IEFwcmlsIDIwMTUgMjM6MDINCj4+IFRvOiBOYWdlc2ggc2hhbW51cg0KPj4g
Q2M6IHRzdndnQGlldGYub3JnDQo+PiBTdWJqZWN0OiBSZTogW3RzdndnXSBJLUQgQWN0aW9uOiBk
cmFmdC1pZXRmLXRzdndnLXNjdHAtbmRhdGEtMDMudHh0DQo+PiANCj4+PiBPbiAwNyBBcHIgMjAx
NSwgYXQgMTY6MDAsIE5hZ2VzaCBzaGFtbnVyIDxuYWdlc2guc2hhbW51ckBodWF3ZWkuY29tPiB3
cm90ZToNCj4+PiANCj4+PiBIaSBHcm91cCwNCj4+PiAJV2hpbGUgZ29pbmcgdGhyb3VnaCB0aGUg
ZHJhZnQsIGRyYWZ0LWlldGYtdHN2d2ctc2N0cC1uZGF0YS0wMyBJIGdvdCB0aGUgZm9sbG93aW5n
IGRvdWJ0IGFuZCBoZW5jZSB0aGlzIG1haWwuDQo+Pj4gDQo+Pj4gCVdoeSBNSUQgaXMgcmVxdWly
ZWQgZXZlbiBmb3IgdGhlIHVub3JkZXJlZCBkYXRhLCBieSB0aGUgbmF0dXJlIG9mIHRoZSB1bm9y
ZGVyZWQgZGF0YSwgaXQgY2FuIGNvbWUgaW4gYW55IG9yZGVyLCBhbmQgaGVuY2UgU1NOL01JRCBp
cyBub3QgcmVxdWlyZWQuIA0KPj4gSWYgeW91IGhhdmUgbXVsdGlwbGUgZnJhZ21lbnRzIGJlbG9u
Z2luZyB0byB0aGUgc2FtZSB1bm9yZGVyZWQgbWVzc2FnZSwgeW91IG5lZWQgYW4gaWRlbnRpZmll
ciBmb3IgdGhhdCBtZXNzYWdlLiBUaGUgTUlEIGlzIHRoZSBzYW1lIGZvciBhbGwgZnJhZ21lbnRz
IG9mIHRoZSBzYW1lIHVzZXIgbWVzc2FnZS4NCj4+PiANCj4+PiAJIElzIGl0IHRoYXQsIGl0IENh
biBNSUQgYmUgdXNlZCBvbmx5IGluIGNhc2Ugb2YgdW5vcmRlcmVkIGZyYWdtZW50IGRhdGEgYW5k
IG5vdCBmb3IgYWxsIHRoZSB1bm9yZGVyZWQgZGF0YT8gQnV0IGFnYWluLCBhcyBwZXIgdGhlIGRy
YWZ0LCB0aGUgc2VuZGVyIE1VU1QgTk9UIGhhdmUgbW9yZSB0aGFuIG9uZSB1bi1vcmRlcmVkIGZy
YWdtZW50ZWQgbWVzc2FnZSBiZWluZyBwcm9kdWNlZCBpbiBhbnkgb25lIHN0cmVhbSwgc28gaW4g
dGhhdCBjYXNlIGFsc28sIE1JRCB3b3VsZG4ndCBiZSByZXF1aXJlZC4gDQo+PiBUaGF0IHN0YXRl
bWVudCBuZWVkcyB0byBiZSBjbGFyaWZpZWQuIEl0IG1lYW5zIHRoYXQgdGhlIHNlbmRlciB3aWxs
IG5vdCBpbnRlcmxlYXZlIHR3byB1bm9yZGVyZWQgZnJhZ21lbnRlZCBtZXNzYWdlcyB3aGVuIGJy
ZWFraW5nIHRoZW0gaW50byBEQVRBIGNodW5rcy4gSG93ZXZlciwgdGhpcyBkb2VzIG5vdCBtZWFu
IHRoYXQgdGhlcmUgY2FuJ3QgYmUgbXVsdGlwbGUgdW5vcmRlcmVkIGZyYWdtZW50ZWQgbWVzc2Fn
ZXMgb24gdGhlIHNhbWUgc3RyZWFtIGluIGZsaWdodC4NCj4gSGkgTmFnZXNoLA0KPiANCj4gdGhl
IHBvaW50IGlzIHRoYXQgd2Ugd2FudCB0byBhbGxvdyB0byBpbnRlcmxlYXZlIG1lc3NhZ2VzIGZy
b20gZGlmZmVyZW50IHN0cmVhbXMuIFJGQyA0OTYwIGRvZXMgbm90IGFsbG93IG1lc3NhZ2UgaW50
ZXJsZWF2aW5nIGF0IGFsbC4gV2UgZG9uJ3Qgc2VlIGEgbmVlZCBmb3IgaW50ZXJsZWF2aW5nIG11
bHRpcGxlIG1lc3NhZ2VzIGZyb20gdGhlIHNhbWUgc3RyZWFtLiBUaGlzIGRvZXNuJ3QgbWFrZSBz
ZW5zZSBmb3Igb3JkZXJlZCBtZXNzYWdlcyBhbmQgd2UgZG9uJ3QgdGhpbmsgaXQgaXMgb2YgbXVj
aCB1c2UgZm9yIHVub3JkZXJlZCBvbmVzLg0KPj4gSW4gc3BpdGUgb2YgdGhhdCwgZm9yIHVub3Jk
ZXJlZCBtZXNzYWdlcywgTUlEIGlzIG5vdCByZXF1aXJlZC4gSW4gY2FzZSBvZiBEQVRBIG1lc3Nh
Z2UgKGVhcmxpZXIpLCBmb3IgYm90aCBmcmFnbWVudGVkIGFuZCB1bi1mcmFnbWVudGVkIHVub3Jk
ZXJlZCBtZXNzYWdlcywgU1NOIHdhcyBub3QgcmVxdWlyZWQsIGFuZCB0aGUgcmVjZWl2ZXIgd2Fz
IGFibGUgdG8gcmVhc3NlbWJsZSB3aXRoIHRoZSBoZWxwIG9mIFRTTiwgQmVnaW4gYW5kIEVuZCBC
aXRzLiBOb3cgaW4gY2FzZSBvZiBJLURBVEEgY2h1bmssIHNpbmNlIG1vcmUgdGhhbiBvbmUgdW4t
b3JkZXJlZCBmcmFnbWVudGVkIG1lc3NhZ2UgY2Fubm90IGJlIGludGVybGVhdmVkLCB0aGUgc2Ft
ZSBsb2dpYyBhcyBEQVRBIGNodW5rIChUU04sIEIgJiBFIGZsYWdzKSBjYW4gYmUgdXNlZCB0byBy
ZWFzc2VtYmxlLiBTbywgdGhlIE1JRCBjYW4gYmUgYWx0b2dldGhlciByZW1vdmVkIGZvciB1bi1v
cmRlcmVkIG1lc3NhZ2VzIGluIGdlbmVyYWwuDQo+IEJ1dCB0aGVuIHlvdSBjYW4ndCBpbnRlcmxl
YXZlIG1lc3NhZ2VzIGZyb20gbXVsdGlwbGUgc3RyZWFtcy4gWW91IHdvdWxkIHJlcXVpcmUgY29u
c2VjdXRpdmUgVFNOIGFzc2lnbm1lbnRzLg0KPiANCj4gQXNzdW1lIHRoZSBzZW5kZXIgc2VuZHMg
dHdvIHRocmVlIHVub3JkZXJlZCBtZXNzYWdlcyByZXN1bHRpbmcgaW4gdGhlIGZvbGxvd2luZyBU
U04gYXNzaWdubWVudHMuDQo+IA0KPiBJLURBVEFbZmxhZ3M9QlU7IFRTTj0wO1NJRD0wO01JRD0w
O0ZTTj0wXSANCj4gSS1EQVRBW2ZsYWdzPUJFVTtUU049MTtTSUQ9MTtNSUQ9MDtGU049MF0NCj4g
SS1EQVRBW2ZsYWdzPUJFVTtUU049MjtTSUQ9MTtNSUQ9MTtGU049MF0NCj4gSS1EQVRBW2ZsYWdz
PUVVOyBUU049MztTSUQ9MDtNSUQ9MDtGU049MV0NCj4gDQo+IE5vdyBhc3N1bWUgdGhhdCBvbmx5
IHRoZSBmaXJzdCBhbmQgbGFzdCBtZXNzYWdlIGFyZSByZWNlaXZlZC4gV2l0aCB0aGUgTUlELCB0
aGUgcmVjZWl2ZXIga25vd3MgdGhhdCBpdCBoYXMgYSBjb21wbGV0ZSBtZXNzYWdlIGFuIGNhbiBk
ZWxpdmVyIGl0IHJpZ2h0IGF3YXkuIFdpdGhvdXQgdGhlIE1JRCwgdGhlIHJlY2VpdmVyIGNhbid0
IGRlbGl2ZXIgdGhlIG1lc3NhZ2UsIHNpbmNlIHRoZSBzZW5kZXIgbWlnaHQgaGF2ZSBzZW50Og0K
PiANCj4gSS1EQVRBW2ZsYWdzPUJVOyBUU049MDtTSUQ9MDtNSUQ9MDtGU049MF0gSS1EQVRBW2Zs
YWdzPUVVOyANCj4gVFNOPTE7U0lEPTA7TUlEPTA7RlNOPTBdIEktREFUQVtmbGFncz1CVTsgVFNO
PTI7U0lEPTA7TUlEPTE7RlNOPTBdIA0KPiBJLURBVEFbZmxhZ3M9RVU7IFRTTj0zO1NJRD0wO01J
RD0xO0ZTTj0xXQ0KPiANCj4gYW5kIHJlYXNzZW1ibGluZyB0aGUgZmlyc3QgYW5kIGxhc3QgZG9l
c24ndCBtYWtlIHNlbnNlLg0KPiBbTmFnZXNoXTogVGhhbmtzIGEgbG90IGZvciBleHBsYWluaW5n
IHRoaW5ncyB0byBtZSwgbm93IGl0IG1ha2VzIG1vcmUgc2Vuc2UuIEluIHRoYXQgY2FzZSwgaXMg
aXQgcG9zc2libGUgdG8gbWFrZSB0aGUgTUlEIG1hbmRhdG9yeSBvbmx5IGZvciB1bm9yZGVyZWQg
ZnJhZ21lbnRlZCBhbmQgdW5vcmRlcmVkIG5vbi1mcmFnbWVudGVkIGNhc2UsIGl0IGNhbiBiZSBp
Z25vcmVkIGJ5IGJvdGggc2VuZGVyIGFuZCByZWNlaXZlci4gU2luY2UsIHRoZSB0cnVlIG5hdHVy
ZSBvZiB0aGUgdW5vcmRlcmVkIG1lc3NhZ2UgY2FuIGJlIHJldGFpbmVkLiBTaW5jZSBoYXZpbmcg
dGhlIE1JRCBmb3IgdGhlIHVub3JkZXJlZCBub24tZnJhZ21lbnRlZCBtZXNzYWdlIGlzIGFjdHVh
bGx5IGR1bW15IGFuZCBib3RoIHNlbmRlciBhbmQgcmVjZWl2ZXIgd291bGRuJ3QgYmUgYWJsZSB0
byB0YWtlIGFueSBhY3Rpb25zIG9uIHRoYXQuDQpJIGFncmVlLCB0aGF0IGZvciB1bi1vcmRlcmVk
LCB1bi1mcmFnbWVudGVkIHVzZXIgbWVzc2FnZXMgdGhlIE1JRCBpcyBub3QgaW1wb3J0YW50IGZv
ciB0aGUgcmVjZWl2ZXIuDQpIb3dldmVyLCBJIGRvbuKAmXQgd2FudCB0byBtYWtlIHRoZSBJLURB
VEEgY2h1bmsgaGVhZGVyIGEgdmFyaWFibGUgc2l6ZSBoZWFkZXIuIFNvIHRoZSBmaWVsZCBpcyBh
bHdheXMgdGhlcmUuIEZyb20gbXkgcGVyc3BlY3RpdmUsIGl0IGlzIHNpbXBsZXIgdG8gcmVxdWly
ZSB0aGUgc2VuZGVyIHRvIGZpbGwgaW4gdGhlIGZpZWxkIGFsd2F5cyBieSBpbmNyZW1lbnRpbmcg
aXQgY29tcGFyZWQgdG8gc3RhdGUgdGhhdCBpdCBuZWVkcyB0byBiZSBpbmNyZW1lbnRlZCBhbHdh
eXMsIGV4Y2VwdCBmb3IgdW4tb3JkZXJlZCBhbmQgdW4tZnJhZ21lbnRlZCB1c2VyIG1lc3NhZ2Vz
LiBUaGUgcmVjZWl2ZXIgd2lsbCBqdXN0IG5vdCBtYWtlIHVzZSBvZiBpdC4NCkkgZG9u4oCZdCBz
ZWUgYW55IGJlbmVmaXQgaXQgc2V0dGluZyB0aGUgZmllbGQgdG8gc29tZSBzcGVjaWFsIHZhbHVl
IChsaWtlIDApIGZvciB1bi1vcmRlcmVkLCB1bi1mcmFnbWVudGVkLg0KSG93ZXZlciwgaXQgbWFr
ZXMgdGhlIGNvZGUgYW5kIHRlc3RpbmcgbW9yZSBjb21wbGV44oCmDQpPbiB0aGUgY29udHJhcnks
IGNhbiBtYWtlIHRoZSBwYXJhbWV0ZXIgZHVtbXkgKHNldHRpbmcgdG8gc3BlY2lhbCB2YWx1ZSBs
aWtlIDApIHdvdWxkIGJlIHN0cmFpZ2h0IGZvcndhcmQuIE1vcmVvdmVyLCBpdCB3b3VsZCBrZWVw
IGl0IGNvbnNpc3RlbnQgd2l0aCB0aGUgZGVzY3JpcHRpb24gb2YgU1NOIGluIGNhc2Ugb2YgREFU
QSBDaHVuay4gSWdub3Jpbmcgb2YgdGhpcyB2YWx1ZSBhdCB0aGUgc2VuZGVyIGFuZCBpZ25vcmlu
ZyBhdCB0aGUgcmVjZWl2ZSB3b3VsZCBtYWtlIGl0IG11Y2ggc2ltcGxlci4NCldlIG5lZWRuJ3Qg
bWFrZSB0aGUgbWVzc2FnZSBoYXZpbmcgdmFyaWFibGUgc2l6ZSBoZWFkZXIgYW5kIGtlZXAgdGhl
IGhlYWRlciBzaXplIGNvbnN0YW50LCBidXQgdGhlIHNlbmRlciBjYW4gZW5jb2RlIHRoZSB2YWx1
ZSAwIGFuZCBpdCBjYW4gYmUgaWdub3JlZCBieSB0aGUgcmVjZWl2ZXIgZm9yIHRoZSBjYXNlIG9m
IHVub3JkZXJlZCBub24tZnJhZ21lbnRlZCBkYXRhLg0KDQpCZXN0IHJlZ2FyZHMNCk1pY2hhZWwN
Cj4gQmVzdCByZWdhcmRzDQo+IE1pY2hhZWwNCj4+IEJlc3QgcmVnYXJkcw0KPj4gTWljaGFlbA0K
Pj4+IA0KPj4+IAlJcyB0aGVyZSBzb21ldGhpbmcgd2hpY2ggSSBhbSBtaXNzaW5nIGhlcmU/DQo+
Pj4gDQo+Pj4gUmVnYXJkcywNCj4+PiBOYWdlc2guDQo+Pj4gDQo+Pj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4+PiBGcm9tOiB0c3Z3ZyBbbWFpbHRvOnRzdndnLWJvdW5jZXNAaWV0Zi5v
cmddIE9uIEJlaGFsZiBPZiANCj4+PiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcNCj4+PiBTZW50
OiAxMCBNYXJjaCAyMDE1IDA1OjU1DQo+Pj4gVG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZw0KPj4+
IENjOiB0c3Z3Z0BpZXRmLm9yZw0KPj4+IFN1YmplY3Q6IFt0c3Z3Z10gSS1EIEFjdGlvbjogZHJh
ZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLTAzLnR4dA0KPj4+IA0KPj4+IA0KPj4+IEEgTmV3IElu
dGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0
cyBkaXJlY3Rvcmllcy4NCj4+PiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBUcmFu
c3BvcnQgQXJlYSBXb3JraW5nIEdyb3VwIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+Pj4g
DQo+Pj4gICAgICBUaXRsZSAgICAgICAgICAgOiBTdHJlYW0gU2NoZWR1bGVycyBhbmQgVXNlciBN
ZXNzYWdlIEludGVybGVhdmluZyBmb3IgdGhlIFN0cmVhbSBDb250cm9sIFRyYW5zbWlzc2lvbiBQ
cm90b2NvbA0KPj4+ICAgICAgQXV0aG9ycyAgICAgICAgIDogUmFuZGFsbCBSLiBTdGV3YXJ0DQo+
Pj4gICAgICAgICAgICAgICAgICAgICAgICBNaWNoYWVsIFR1ZXhlbg0KPj4+ICAgICAgICAgICAg
ICAgICAgICAgICAgU2FsdmF0b3JlIExvcmV0bw0KPj4+ICAgICAgICAgICAgICAgICAgICAgICAg
Um9iaW4gU2VnZ2VsbWFubg0KPj4+IAlGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLXRzdndn
LXNjdHAtbmRhdGEtMDMudHh0DQo+Pj4gCVBhZ2VzICAgICAgICAgICA6IDE0DQo+Pj4gCURhdGUg
ICAgICAgICAgICA6IDIwMTUtMDMtMDkNCj4+PiANCj4+PiBBYnN0cmFjdDoNCj4+PiBUaGUgU3Ry
ZWFtIENvbnRyb2wgVHJhbnNtaXNzaW9uIFByb3RvY29sIChTQ1RQKSBpcyBhIG1lc3NhZ2UgDQo+
Pj4gb3JpZW50ZWQgIHRyYW5zcG9ydCBwcm90b2NvbCBzdXBwb3J0aW5nIGFyYml0cmFyeSBsYXJn
ZSB1c2VyIG1lc3NhZ2VzLg0KPj4+IEhvd2V2ZXIsIHRoZSBzZW5kZXIgY2FuIG5vdCBpbnRlcmxl
YXZlIGRpZmZlcmVudCB1c2VyIG1lc3NhZ2VzIHdoaWNoIA0KPj4+IGNhdXNlcyBoZWFkIG9mIGxp
bmUgYmxvY2tpbmcgYXQgdGhlIHNlbmRlciBzaWRlLiAgVG8gb3ZlcmNvbWUgdGhpcyANCj4+PiBs
aW1pdGF0aW9uLCB0aGlzIGRvY3VtZW50IGFkZHMgYSBuZXcgZGF0YSBjaHVuayB0byBTQ1RQLg0K
Pj4+IA0KPj4+IFdoZW5ldmVyIGFuIFNDVFAgc2VuZGVyIGlzIGFsbG93ZWQgdG8gc2VuZCBhIHVz
ZXIgZGF0YSwgaXQgY2FuIA0KPj4+IHBvc3NpYmx5IGNob29zZSBmcm9tIG11bHRpcGxlIG91dGdv
aW5nIFNDVFAgc3RyZWFtcy4gIE11bHRpcGxlIHdheXMgDQo+Pj4gZm9yIHRoaXMgc2VsZWN0aW9u
LCBjYWxsZWQgc3RyZWFtIHNjaGVkdWxlcnMsIGFyZSBkZWZpbmVkLiAgU29tZSBvZiANCj4+PiB0
aGVtIGRvbid0IHJlcXVpcmUgdGhlIHN1cHBvcnQgb2YgdXNlciBtZXNzYWdlIGludGVybGVhdmlu
Zywgc29tZSBkby4NCj4+PiANCj4+PiANCj4+PiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMg
cGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj4+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLXRzdndnLXNjdHAtbmRhdGEvDQo+Pj4gDQo+Pj4gVGhlcmUncyBhbHNv
IGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+Pj4gaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLW5kYXRhLTAzDQo+Pj4gDQo+Pj4gQSBkaWZm
IGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPj4+IGh0dHA6Ly93
d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtdHN2d2ctc2N0cC1uZGF0YS0wMw0K
Pj4+IA0KPj4+IA0KPj4+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2Yg
bWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZl
cnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4+PiANCj4+
PiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6
DQo+Pj4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4+PiANCj4+IA0KPj4g
DQo+IA0KPiANCg0K


From nobody Thu Apr  9 12:18:12 2015
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 93DF11A8AF2 for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 12:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 uKD64cofeVXD for <tsvwg@ietfa.amsl.com>; Thu,  9 Apr 2015 12:18:07 -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 3D8251A8AFA for <tsvwg@ietf.org>; Thu,  9 Apr 2015 12:18:07 -0700 (PDT)
Received: from [192.168.1.200] (p508F095A.dip0.t-ipconnect.de [80.143.9.90]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id AF1131C1622C7; Thu,  9 Apr 2015 21:18:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <4AC96705FB868F42B2075BA50F806DEB5284D0BB@szxeml512-mbs.china.huawei.com>
Date: Thu, 9 Apr 2015 21:18:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE87285A-82F5-4E38-8BD9-1B4138CB0752@lurchi.franken.de>
References: <20150309215448.3165.2371.idtracker@ietfa.amsl.com> <4AC96705FB868F42B2075BA50F806DEB5284BED6@szxeml512-mbs.china.huawei.com> <0B70D026-E437-40E8-AE8A-DF5392BA9810@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284CF02@szxeml512-mbs.china.huawei.com> <F30CEC56-6846-4AAC-88F6-322A22F89B2F@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284D050@szxeml512-mbs.china.huawei.com> <21FA4EFC-8A6D-4655-8FC7-9AEB02B8696C@lurchi.franken.de> <4AC96705FB868F42B2075BA50F806DEB5284D0BB@szxeml512-mbs.china.huawei.com>
To: Nagesh shamnur <nagesh.shamnur@huawei.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/qdV0lPKPge9UwMI5JGl5giCsB-s>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-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, 09 Apr 2015 19:18:10 -0000

> On 09 Apr 2015, at 14:34, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>=20
>=20
> -----Original Message-----
> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]=20
> Sent: 09 April 2015 16:53
> To: Nagesh shamnur
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>=20
>> On 09 Apr 2015, at 09:09, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>>=20
>>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Sent: 09 April 2015 03:02
>> To: Nagesh shamnur
>> Cc: tsvwg@ietf.org
>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>=20
>>> On 08 Apr 2015, at 07:52, Nagesh shamnur <nagesh.shamnur@huawei.com> =
wrote:
>>>=20
>>> Hi Michael,
>>> 	Thanks for the answer. Please find my reply in-line.
>>>=20
>>> Regards,
>>> Nagesh.
>>>=20
>>> -----Original Message-----
>>> From: Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>>> Sent: 07 April 2015 23:02
>>> To: Nagesh shamnur
>>> Cc: tsvwg@ietf.org
>>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>>=20
>>>> On 07 Apr 2015, at 16:00, Nagesh shamnur =
<nagesh.shamnur@huawei.com> wrote:
>>>>=20
>>>> Hi Group,
>>>> 	While going through the draft, draft-ietf-tsvwg-sctp-ndata-03 I =
got the following doubt and hence this mail.
>>>>=20
>>>> 	Why MID is required even for the unordered data, by the nature =
of the unordered data, it can come in any order, and hence SSN/MID is =
not required.=20
>>> If you have multiple fragments belonging to the same unordered =
message, you need an identifier for that message. The MID is the same =
for all fragments of the same user message.
>>>>=20
>>>> 	 Is it that, it Can MID be used only in case of unordered =
fragment data and not for all the unordered data? But again, as per the =
draft, the sender MUST NOT have more than one un-ordered fragmented =
message being produced in any one stream, so in that case also, MID =
wouldn't be required.=20
>>> That statement needs to be clarified. It means that the sender will =
not interleave two unordered fragmented messages when breaking them into =
DATA chunks. However, this does not mean that there can't be multiple =
unordered fragmented messages on the same stream in flight.
>> Hi Nagesh,
>>=20
>> the point is that we want to allow to interleave messages from =
different streams. RFC 4960 does not allow message interleaving at all. =
We don't see a need for interleaving multiple messages from the same =
stream. This doesn't make sense for ordered messages and we don't think =
it is of much use for unordered ones.
>>> In spite of that, for unordered messages, MID is not required. In =
case of DATA message (earlier), for both fragmented and un-fragmented =
unordered messages, SSN was not required, and the receiver was able to =
reassemble with the help of TSN, Begin and End Bits. Now in case of =
I-DATA chunk, since more than one un-ordered fragmented message cannot =
be interleaved, the same logic as DATA chunk (TSN, B & E flags) can be =
used to reassemble. So, the MID can be altogether removed for un-ordered =
messages in general.
>> But then you can't interleave messages from multiple streams. You =
would require consecutive TSN assignments.
>>=20
>> Assume the sender sends two three unordered messages resulting in the =
following TSN assignments.
>>=20
>> I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0]=20
>> I-DATA[flags=3DBEU;TSN=3D1;SID=3D1;MID=3D0;FSN=3D0]
>> I-DATA[flags=3DBEU;TSN=3D2;SID=3D1;MID=3D1;FSN=3D0]
>> I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D0;FSN=3D1]
>>=20
>> Now assume that only the first and last message are received. With =
the MID, the receiver knows that it has a complete message an can =
deliver it right away. Without the MID, the receiver can't deliver the =
message, since the sender might have sent:
>>=20
>> I-DATA[flags=3DBU; TSN=3D0;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DEU;=20=

>> TSN=3D1;SID=3D0;MID=3D0;FSN=3D0] I-DATA[flags=3DBU; =
TSN=3D2;SID=3D0;MID=3D1;FSN=3D0]=20
>> I-DATA[flags=3DEU; TSN=3D3;SID=3D0;MID=3D1;FSN=3D1]
>>=20
>> and reassembling the first and last doesn't make sense.
>> [Nagesh]: Thanks a lot for explaining things to me, now it makes more =
sense. In that case, is it possible to make the MID mandatory only for =
unordered fragmented and unordered non-fragmented case, it can be =
ignored by both sender and receiver. Since, the true nature of the =
unordered message can be retained. Since having the MID for the =
unordered non-fragmented message is actually dummy and both sender and =
receiver wouldn't be able to take any actions on that.
> I agree, that for un-ordered, un-fragmented user messages the MID is =
not important for the receiver.
> However, I don=E2=80=99t want to make the I-DATA chunk header a =
variable size header. So the field is always there. =46rom my =
perspective, it is simpler to require the sender to fill in the field =
always by incrementing it compared to state that it needs to be =
incremented always, except for un-ordered and un-fragmented user =
messages. The receiver will just not make use of it.
> I don=E2=80=99t see any benefit it setting the field to some special =
value (like 0) for un-ordered, un-fragmented.
> However, it makes the code and testing more complex=E2=80=A6
> On the contrary, can make the parameter dummy (setting to special =
value like 0) would be straight forward. Moreover, it would keep it =
consistent with the description of SSN in case of DATA Chunk. Ignoring =
of this value at the sender and ignoring at the receive would make it =
much simpler.
In RFC 4960, it is not defined what the sender puts in the SSN field for =
unordered messages. It is
only stated that the receiver ignores it. See:
https://tools.ietf.org/html/rfc4960#section-6.6

I would like to make clear what the sender has to do. You are suggesting =
to treat un-ordered un-fragmented
user messages in a special way by always using MID 0. I=E2=80=99m =
proposing to not have special treatment
for them, just assigning a MID. This makes the sender side simpler: One =
if statement less to make.
The receiver doesn=E2=80=99t need to look at the value. So there is no =
difference at the receiver side.
> We needn't make the message having variable size header and keep the =
header size constant, but the sender can encode the value 0 and it can =
be ignored by the receiver for the case of unordered non-fragmented =
data.
OK. So we agree that the chunk header is the same in all cases.

Best regards
Michael
>=20
> Best regards
> Michael
>> Best regards
>> Michael
>>> Best regards
>>> Michael
>>>>=20
>>>> 	Is there something which I am missing here?
>>>>=20
>>>> Regards,
>>>> Nagesh.
>>>>=20
>>>> -----Original Message-----
>>>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of=20
>>>> internet-drafts@ietf.org
>>>> Sent: 10 March 2015 05:55
>>>> To: i-d-announce@ietf.org
>>>> Cc: tsvwg@ietf.org
>>>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-03.txt
>>>>=20
>>>>=20
>>>> 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.
>>>>=20
>>>>     Title           : Stream Schedulers and User Message =
Interleaving for the Stream Control Transmission Protocol
>>>>     Authors         : Randall R. Stewart
>>>>                       Michael Tuexen
>>>>                       Salvatore Loreto
>>>>                       Robin Seggelmann
>>>> 	Filename        : draft-ietf-tsvwg-sctp-ndata-03.txt
>>>> 	Pages           : 14
>>>> 	Date            : 2015-03-09
>>>>=20
>>>> Abstract:
>>>> The Stream Control Transmission Protocol (SCTP) is a message=20
>>>> oriented  transport protocol supporting arbitrary large user =
messages.
>>>> However, the sender can not interleave different user messages =
which=20
>>>> causes head of line blocking at the sender side.  To overcome this=20=

>>>> limitation, this document adds a new data chunk to SCTP.
>>>>=20
>>>> Whenever an SCTP sender is allowed to send a user data, it can=20
>>>> possibly choose from multiple outgoing SCTP streams.  Multiple ways=20=

>>>> for this selection, called stream schedulers, are defined.  Some of=20=

>>>> them don't require the support of user message interleaving, some =
do.
>>>>=20
>>>>=20
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/
>>>>=20
>>>> There's also a htmlized version available at:
>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-03
>>>>=20
>>>> A diff from the previous version is available at:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-ndata-03
>>>>=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:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>=20


From nobody Mon Apr 13 16:35:19 2015
Return-Path: <wwwrun@rfc-editor.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 CD32A1AD324; Mon, 13 Apr 2015 16:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 BomPoxiWQFsE; Mon, 13 Apr 2015 16:35:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id B3D121ACEA2; Mon, 13 Apr 2015 16:35:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 202DE180207; Mon, 13 Apr 2015 16:34:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150413233435.202DE180207@rfc-editor.org>
Date: Mon, 13 Apr 2015 16:34:35 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/5i8VysWx1zHYhfLDdCHmBK_ckuc>
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [tsvwg] RFC 7496 on Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
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, 13 Apr 2015 23:35:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7496

        Title:      Additional Policies for the Partially 
                    Reliable Stream Control Transmission Protocol
                    Extension 
        Author:     M. Tuexen, R. Seggelmann,
                    R. Stewart, S. Loreto
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    tuexen@fh-muenster.de, 
                    rfc@robin-seggelmann.com, 
                    randall@lakerest.net, 
                    Salvatore.Loreto@ericsson.com
        Pages:      11
        Characters: 21272
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-sctp-prpolicies-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7496

This document defines two additional policies for the Partially
Reliable Stream Control Transmission Protocol (PR-SCTP) extension.
These policies allow limitation of the number of retransmissions and
prioritization of user messages for more efficient usage of the send
buffer.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Fri Apr 17 12:12:09 2015
Return-Path: <wwwrun@rfc-editor.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 364FB1B2FA7; Fri, 17 Apr 2015 12:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.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, USER_IN_WHITELIST=-100] 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 O25VBgdQJWP6; Fri, 17 Apr 2015 12:12:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C06DE1B2F97; Fri, 17 Apr 2015 12:12:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 46C9B180205; Fri, 17 Apr 2015 12:11:22 -0700 (PDT)
To: mirja.kuehlewind@ikr.uni-stuttgart.de, kk@teraoptic.com, floyd@aciri.org,  black_david@emc.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150417191122.46C9B180205@rfc-editor.org>
Date: Fri, 17 Apr 2015 12:11:22 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/EW_kUnzfvI18XpoddtvT1PAnia8>
Cc: mls.ietf@gmail.com, rfc-editor@rfc-editor.org, iesg@ietf.org, tsvwg@ietf.org
Subject: [tsvwg] [Errata Rejected] RFC3168 (3680)
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, 17 Apr 2015 19:12:08 -0000

The following errata report has been rejected for RFC3168,
"The Addition of Explicit Congestion Notification (ECN) to IP".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3168&eid=3680

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Date Reported: 2013-07-12
Rejected by: Martin Stiemerling (IESG)

Section: 6.1.1.

Original Text
-------------
If the TCP connection does not
wish to use ECN notification for a particular packet, the sending TCP
sets the ECN codepoint to not-ECT, and the TCP receiver ignores the
CE codepoint in the received packet.

Corrected Text
--------------
If the TCP connection does not
wish to use ECN notification for a particular packet, the sending TCP
sets the ECN codepoint to not-ECT.

Notes
-----
The receiver should not ignore any CE codepoint.
 --VERIFIER NOTES-- 
This is not an editorial fix or technical clarification, but proposes to change the processing of ECN. Please go ahead and write a draft that works towards updating RFC 3168.

--------------------------------------
RFC3168 (draft-ietf-tsvwg-ecn-04)
--------------------------------------
Title               : The Addition of Explicit Congestion Notification (ECN) to IP
Publication Date    : September 2001
Author(s)           : K. Ramakrishnan, S. Floyd, D. Black
Category            : PROPOSED STANDARD
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Apr 17 12:14:37 2015
Return-Path: <wwwrun@rfc-editor.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 35AEA1B2FB6; Fri, 17 Apr 2015 12:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.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, USER_IN_WHITELIST=-100] 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 x6DBt8MtuI3j; Fri, 17 Apr 2015 12:14:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9CACA1B2FB8; Fri, 17 Apr 2015 12:14:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 546F9180205; Fri, 17 Apr 2015 12:13:47 -0700 (PDT)
To: rs@netapp.com, kk@teraoptic.com, floyd@aciri.org, black_david@emc.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150417191347.546F9180205@rfc-editor.org>
Date: Fri, 17 Apr 2015 12:13:47 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/i_PfEuv5VJ6Jtq1gBNCe-NLIX9o>
Cc: mls.ietf@gmail.com, rfc-editor@rfc-editor.org, iesg@ietf.org, tsvwg@ietf.org
Subject: [tsvwg] [Errata Verified] RFC3168 (3639)
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, 17 Apr 2015 19:14:33 -0000

The following errata report has been verified for RFC3168,
"The Addition of Explicit Congestion Notification (ECN) to IP". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3168&eid=3639

--------------------------------------
Status: Verified
Type: Technical

Reported by: Richard Scheffenegger <rs@netapp.com>
Date Reported: 2013-06-05
Verified by: Martin Stiemerling (IESG)

Section: 6.1 / 6.1.3

Original Text
-------------
Section 6.1 says:


      * The receiver receives the packet with the CE codepoint set, and
        sets the ECN-Echo flag in its next TCP ACK sent to the sender.
[...]

      * The sender sets the CWR flag in the TCP header of the next
        packet sent to the receiver to acknowledge its receipt of and
        reaction to the ECN-Echo flag.

Section 6.1.3 says:


   When TCP receives a CE data packet at the destination end-system, the
   TCP data receiver sets the ECN-Echo flag in the TCP header of the
   subsequent ACK packet. 

   [...]
                                               The TCP receiver uses the
   CWR flag received from the TCP sender to determine when to stop
   setting the ECN-Echo flag.
   

Corrected Text
--------------
Section 6.1.3 should say:
 
   The TCP receiver uses the
   CWR flag received from the TCP sender to determine when to stop
   setting the ECN-Echo flag. This check has to be performed before  
   checking if the received segment is CE marked.

Notes
-----
The ordering of the text in the bullet points in section 6.1, and the text in section 6.1.3 can led to inappropriate implementations. At least Section 6.1.3 should be strict about the handling of CE-marked CWR-segments.


If CE is checked first, and ECE set, and thereafter CWR used to disable ECE, a CE-marked CWR segment will not result in the sending of an additional window of ECEs.


All derivatives of BSD used to 

First, set ECE because of CE
Second, reset ECE because of CWR

However, the "authorative" NS2 sample code, the TBIT tool, Windows, Solaris and Linux would

First, reset ECE because of CWR
Second, set ECE because of CE

The latter approach seems to be the sensible one, and it was quickly fixed:

http://lists.freebsd.org/pipermail/freebsd-bugs/2010-April/039450.html

--------------------------------------
RFC3168 (draft-ietf-tsvwg-ecn-04)
--------------------------------------
Title               : The Addition of Explicit Congestion Notification (ECN) to IP
Publication Date    : September 2001
Author(s)           : K. Ramakrishnan, S. Floyd, D. Black
Category            : PROPOSED STANDARD
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Apr 17 12:16:22 2015
Return-Path: <wwwrun@rfc-editor.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 203E21B2FB0; Fri, 17 Apr 2015 12:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 mj8ALw-Mw2qI; Fri, 17 Apr 2015 12:16:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDB01B2FBD; Fri, 17 Apr 2015 12:16:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 12F0D180205; Fri, 17 Apr 2015 12:15:19 -0700 (PDT)
To: gds@alum.mit.edu, kk@teraoptic.com, floyd@aciri.org, black_david@emc.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150417191519.12F0D180205@rfc-editor.org>
Date: Fri, 17 Apr 2015 12:15:19 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/k8iN6Bv8Ex7n4cL9D76YljrCRgU>
Cc: mls.ietf@gmail.com, rfc-editor@rfc-editor.org, iesg@ietf.org, tsvwg@ietf.org
Subject: [tsvwg] [Errata Rejected] RFC3168 (4302)
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, 17 Apr 2015 19:16:18 -0000

The following errata report has been rejected for RFC3168,
"The Addition of Explicit Congestion Notification (ECN) to IP".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3168&eid=4302

--------------------------------------
Status: Rejected
Type: Editorial

Reported by: Greg Skinner <gds@alum.mit.edu>
Date Reported: 2015-03-15
Rejected by: Martin Stiemerling (IESG)

Section: ToC

Original Text
-------------
6.1.1.2.  Robust TCP Initialization with an Echoed Reserved
Field. 17

19.3.  Non-ECN-Based Methods of Subverting End-to-end
Congestion Control....................................................
<a href="#page-54">54</a>

Corrected Text
--------------
<a href="#section-6.1.1.2">6.1.1.2</a>.  Robust TCP Initialization
with an Echoed Reserved Field. <a href="#page-17">17</a>

<a href="#section-19.3">19.3</a>.  Non-ECN-Based Methods of
Subverting End-to-end Congestion
Control....................................................
<a href="#page-54">54</a>

Notes
-----
The errors actually occurred in the Table of Contents (ToC) section,
so I hope the Section: field in this form takes that value.  The links
to sections 6.1.1.2 and 19.3 were never generated in the ToC.
 --VERIFIER NOTES-- 
This errata is about the automatically generated html version of the RFC does not report any error in the RFC itself. 

--------------------------------------
RFC3168 (draft-ietf-tsvwg-ecn-04)
--------------------------------------
Title               : The Addition of Explicit Congestion Notification (ECN) to IP
Publication Date    : September 2001
Author(s)           : K. Ramakrishnan, S. Floyd, D. Black
Category            : PROPOSED STANDARD
Source              : Transport Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG


From nobody Sun Apr 19 12:56:43 2015
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 AF6A71B2D58 for <tsvwg@ietfa.amsl.com>; Sun, 19 Apr 2015 12:56:41 -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 l8M9LdHhVrsx for <tsvwg@ietfa.amsl.com>; Sun, 19 Apr 2015 12:56:39 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 314D31A1BDC for <tsvwg@ietf.org>; Sun, 19 Apr 2015 12:56:38 -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.1/Sentrion-MTA-4.3.0) with ESMTP id t3JJubEa025011 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Sun, 19 Apr 2015 15:56:37 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t3JJubEa025011
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1429473397; bh=3JEAHCBSs5HzdDOfet0XlLAWw6c=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=aFV+TkMoFOwCgta3tXUIEjV/PVB9vbtsB1okv7g/+MDYv7ZXeFn52xONa1O5b5mtf XXCuHlpZ5RkTYE2voRnTCpXaibZa43lapHAhnFfkfdOxaHyTREtXNoCk/ztmh+iRPz 4kcGcOwTnN8xbO0ZhBIsVY+XKpFsIZkQpXKtVmCQ=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com t3JJubEa025011
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd05.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Sun, 19 Apr 2015 15:55:53 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t3JJuQY2021250 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Sun, 19 Apr 2015 15:56:26 -0400
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub18.corp.emc.com (10.254.93.47) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sun, 19 Apr 2015 15:56:25 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.93]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0224.002; Sun, 19 Apr 2015 15:56:25 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] RFC 7496 on Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
Thread-Index: AQHQdkKjYdlONa3yIkqXMPxM5rFcHp1UyQZg
Date: Sun, 19 Apr 2015 19:56:24 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949364481B0@MX104CL02.corp.emc.com>
References: <20150413233435.202DE180207@rfc-editor.org>
In-Reply-To: <20150413233435.202DE180207@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.105.37.26]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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/zSthUBTXe7PpNBbAlvYbP3ZWpJ4>
Subject: Re: [tsvwg] RFC 7496 on Additional Policies for the Partially Reliable Stream Control Transmission Protocol Extension
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, 19 Apr 2015 19:56:41 -0000

Congratulations (slightly belated) to the authors on another RFC, and many
thanks to all who contributed!

Thanks,
--David

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of rfc-editor@rfc-
> editor.org
> Sent: Monday, April 13, 2015 7:35 PM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: tsvwg@ietf.org; rfc-editor@rfc-editor.org
> Subject: [tsvwg] RFC 7496 on Additional Policies for the Partially Reliab=
le
> Stream Control Transmission Protocol Extension
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>         RFC 7496
>=20
>         Title:      Additional Policies for the Partially
>                     Reliable Stream Control Transmission Protocol
>                     Extension
>         Author:     M. Tuexen, R. Seggelmann,
>                     R. Stewart, S. Loreto
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       April 2015
>         Mailbox:    tuexen@fh-muenster.de,
>                     rfc@robin-seggelmann.com,
>                     randall@lakerest.net,
>                     Salvatore.Loreto@ericsson.com
>         Pages:      11
>         Characters: 21272
>         Updates/Obsoletes/SeeAlso:   None
>=20
>         I-D Tag:    draft-ietf-tsvwg-sctp-prpolicies-07.txt
>=20
>         URL:        https://www.rfc-editor.org/info/rfc7496
>=20
> This document defines two additional policies for the Partially
> Reliable Stream Control Transmission Protocol (PR-SCTP) extension.
> These policies allow limitation of the number of retransmissions and
> prioritization of user messages for more efficient usage of the send
> buffer.
>=20
> This document is a product of the Transport Area Working Group Working Gr=
oup
> of the IETF.
>=20
> This is now a Proposed Standard.
>=20
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggesti=
ons
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for th=
e
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>=20
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>=20
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/rfc.html
>=20
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>=20
>=20
> The RFC Editor Team
> Association Management Solutions, LLC
>=20


From nobody Mon Apr 20 07:44:05 2015
Return-Path: <mferguson@amsl.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 DC1271B2AD2; Mon, 20 Apr 2015 06:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 gxqXHq67JWw8; Mon, 20 Apr 2015 06:09:55 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 153801B2A3A; Mon, 20 Apr 2015 06:09:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 1E7B51E5A41; Mon, 20 Apr 2015 06:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajDtTDMbjXLi; Mon, 20 Apr 2015 06:08:25 -0700 (PDT)
Received: from [10.0.1.3] (pool-100-36-211-121.washdc.fios.verizon.net [100.36.211.121]) by c8a.amsl.com (Postfix) with ESMTPA id 399681E5A31; Mon, 20 Apr 2015 06:08:24 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CC1926AA-4994-43E6-9A83-35FF3A741FFF"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <20150417191519.12F0D180205@rfc-editor.org>
Date: Mon, 20 Apr 2015 09:09:53 -0400
Message-Id: <EEFE5018-EA6D-4A30-B416-6CCE96A44D69@amsl.com>
References: <20150417191519.12F0D180205@rfc-editor.org>
To: gds@alum.mit.edu
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/MVc29-VrQXcwxD5yx1veHBKOKoU>
X-Mailman-Approved-At: Mon, 20 Apr 2015 07:44:03 -0700
Cc: tsvwg@ietf.org, floyd@aciri.org, Martin Stiemerling <mls.ietf@gmail.com>, IESG <iesg@ietf.org>, kk@teraoptic.com, black_david@emc.com, RFC System <rfc-editor@rfc-editor.org>
Subject: Re: [tsvwg] [Errata Rejected] RFC3168 (4302)
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 Apr 2015 13:09:57 -0000

--Apple-Mail=_CC1926AA-4994-43E6-9A83-35FF3A741FFF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Greetings,

Please note that we have deleted this erratum.  As mentioned at =
http://www.rfc-editor.org/errata.php, "Errata are for the RFCs as =
available from rfc-editor.org=94.

It appears that David Black has already sent notice of this issue to =
webmaster@tools.ietf.org.

Thank you.

RFC Editor/mf

On Apr 17, 2015, at 3:15 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:

> The following errata report has been rejected for RFC3168,
> "The Addition of Explicit Congestion Notification (ECN) to IP".
>=20
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3D3168&eid=3D4302
>=20
> --------------------------------------
> Status: Rejected
> Type: Editorial
>=20
> Reported by: Greg Skinner <gds@alum.mit.edu>
> Date Reported: 2015-03-15
> Rejected by: Martin Stiemerling (IESG)
>=20
> Section: ToC
>=20
> Original Text
> -------------
> 6.1.1.2.  Robust TCP Initialization with an Echoed Reserved
> Field. 17
>=20
> 19.3.  Non-ECN-Based Methods of Subverting End-to-end
> Congestion Control....................................................
> <a href=3D"#page-54">54</a>
>=20
> Corrected Text
> --------------
> <a href=3D"#section-6.1.1.2">6.1.1.2</a>.  Robust TCP Initialization
> with an Echoed Reserved Field. <a href=3D"#page-17">17</a>
>=20
> <a href=3D"#section-19.3">19.3</a>.  Non-ECN-Based Methods of
> Subverting End-to-end Congestion
> Control....................................................
> <a href=3D"#page-54">54</a>
>=20
> Notes
> -----
> The errors actually occurred in the Table of Contents (ToC) section,
> so I hope the Section: field in this form takes that value.  The links
> to sections 6.1.1.2 and 19.3 were never generated in the ToC.
> --VERIFIER NOTES--=20
> This errata is about the automatically generated html version of the =
RFC does not report any error in the RFC itself.=20
>=20
> --------------------------------------
> RFC3168 (draft-ietf-tsvwg-ecn-04)
> --------------------------------------
> Title               : The Addition of Explicit Congestion Notification =
(ECN) to IP
> Publication Date    : September 2001
> Author(s)           : K. Ramakrishnan, S. Floyd, D. Black
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>=20


--Apple-Mail=_CC1926AA-4994-43E6-9A83-35FF3A741FFF
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;"><span =
style=3D"font-family: Menlo-Regular; font-size: =
11px;">Greetings,</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px;"><br style=3D"font-family: Menlo-Regular; font-size: =
11px;"><span style=3D"font-family: Menlo-Regular; font-size: =
11px;">Please note that we have deleted this erratum. &nbsp;As mentioned =
at&nbsp;</span><a href=3D"http://www.rfc-editor.org/errata.php" =
style=3D"font-family: Menlo-Regular; font-size: =
11px;">http://www.rfc-editor.org/errata.php</a><span style=3D"font-family:=
 Menlo-Regular; font-size: 11px;">, "Errata are for the RFCs as =
available from&nbsp;</span><a href=3D"http://rfc-editor.org" =
style=3D"font-family: Menlo-Regular; font-size: =
11px;">rfc-editor.org</a><span style=3D"font-family: Menlo-Regular; =
font-size: 11px;">=94.</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px;"><br style=3D"font-family: Menlo-Regular; font-size: =
11px;"><span style=3D"font-family: Menlo-Regular; font-size: 11px;">It =
appears that David Black has already sent notice of this issue =
to&nbsp;</span><a href=3D"mailto:webmaster@tools.ietf.org" =
style=3D"font-family: Menlo-Regular; font-size: =
11px;">webmaster@tools.ietf.org</a><span style=3D"font-family: =
Menlo-Regular; font-size: 11px;">.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 11px;"><br style=3D"font-family: =
Menlo-Regular; font-size: 11px;"><span style=3D"font-family: =
Menlo-Regular; font-size: 11px;">Thank you.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px;"><br =
style=3D"font-family: Menlo-Regular; font-size: 11px;"><span =
style=3D"font-family: Menlo-Regular; font-size: 11px;">RFC =
Editor/mf</span><div><font face=3D"Menlo-Regular"><span =
style=3D"font-size: 11px;"><br></span></font><div><div>On Apr 17, 2015, =
at 3:15 PM, RFC Errata System &lt;<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&gt=
; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">The following errata report has been rejected for =
RFC3168,<br>"The Addition of Explicit Congestion Notification (ECN) to =
IP".<br><br>--------------------------------------<br>You may review the =
report below and at:<br><a =
href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D3168&amp;eid=3D4=
302">http://www.rfc-editor.org/errata_search.php?rfc=3D3168&amp;eid=3D4302=
</a><br><br>--------------------------------------<br>Status: =
Rejected<br>Type: Editorial<br><br>Reported by: Greg Skinner =
&lt;gds@alum.mit.edu&gt;<br>Date Reported: 2015-03-15<br>Rejected by: =
Martin Stiemerling (IESG)<br><br>Section: ToC<br><br>Original =
Text<br>-------------<br>6.1.1.2. &nbsp;Robust TCP Initialization with =
an Echoed Reserved<br>Field. 17<br><br>19.3. &nbsp;Non-ECN-Based Methods =
of Subverting End-to-end<br>Congestion =
Control....................................................<br>&lt;a =
href=3D"#page-54"&gt;54&lt;/a&gt;<br><br>Corrected =
Text<br>--------------<br>&lt;a =
href=3D"#section-6.1.1.2"&gt;6.1.1.2&lt;/a&gt;. &nbsp;Robust TCP =
Initialization<br>with an Echoed Reserved Field. &lt;a =
href=3D"#page-17"&gt;17&lt;/a&gt;<br><br>&lt;a =
href=3D"#section-19.3"&gt;19.3&lt;/a&gt;. &nbsp;Non-ECN-Based Methods =
of<br>Subverting End-to-end =
Congestion<br>Control....................................................<=
br>&lt;a href=3D"#page-54"&gt;54&lt;/a&gt;<br><br>Notes<br>-----<br>The =
errors actually occurred in the Table of Contents (ToC) section,<br>so I =
hope the Section: field in this form takes that value. &nbsp;The =
links<br>to sections 6.1.1.2 and 19.3 were never generated in the =
ToC.<br> --VERIFIER NOTES-- <br>This errata is about the automatically =
generated html version of the RFC does not report any error in the RFC =
itself. <br><br>--------------------------------------<br>RFC3168 =
(draft-ietf-tsvwg-ecn-04)<br>--------------------------------------<br>Tit=
le =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;: The Addition of Explicit Congestion Notification (ECN) to =
IP<br>Publication Date &nbsp;&nbsp;&nbsp;: September 2001<br>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: K. =
Ramakrishnan, S. Floyd, D. Black<br>Category =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
PROPOSED STANDARD<br>Source =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;: Transport Area Working Group<br>Area =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;: Transport<br>Stream =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;: IETF<br>Verifying Party &nbsp;&nbsp;&nbsp;&nbsp;: =
IESG<br><br></blockquote></div><br></div></body></html>=

--Apple-Mail=_CC1926AA-4994-43E6-9A83-35FF3A741FFF--


From nobody Tue Apr 21 00:58:48 2015
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 3C9EF1B3706 for <tsvwg@ietfa.amsl.com>; Tue, 21 Apr 2015 00:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_20=-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 yK0VnrmLGmZL for <tsvwg@ietfa.amsl.com>; Tue, 21 Apr 2015 00:58:45 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC6A1B3705 for <tsvwg@ietf.org>; Tue, 21 Apr 2015 00:58:45 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 437D81B002F2 for <tsvwg@ietf.org>; Tue, 21 Apr 2015 08:58:58 +0100 (BST)
Received: from 130.243.28.208 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Tue, 21 Apr 2015 08:58:03 +0100
Message-ID: <4bae1066ad3052ea553a3cd6d510a33a.squirrel@erg.abdn.ac.uk>
Date: Tue, 21 Apr 2015 08:58:03 +0100
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/D0z_gB_nfGsyeV86v-K9it-leLs>
Subject: [tsvwg] WGLC for draft-ietf-tcpm-rtorestart-07 : To end 6th May 2015
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 Apr 2015 07:58:47 -0000

TCP and SCTP RTO Restart
https://tools.ietf.org/html/draft-ietf-tcpm-rtorestart-07

The above draft is being evaluated for publication as an Experimental RFC.
It describes a proposed new method for TCP and SCTP.

TSVWG, please note this WGLC in the TCPM WG is also a request for comments
and feedback from the TSVWG.  The end of this WGLC period is 6th May.
Please CC the TCPM WG list in any emails on this topic.

Gorry Fairhurst
(TSVWG Chair)

--------------------------------------------------------------------------

Hi all,

This email starts a WGLC for draft-ietf-tcpm-rtorestart-07, running until
May 6.

Please review the latest version and please let us know if there are any
comments.

Thanks a lot!

Michael

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm


From nobody Tue Apr 21 08:25:35 2015
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 1E1E51ACE69 for <tsvwg@ietfa.amsl.com>; Tue, 21 Apr 2015 08:25:34 -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 Q333lDf9Iflz for <tsvwg@ietfa.amsl.com>; Tue, 21 Apr 2015 08:25:32 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 6250D1ACE6C for <tsvwg@ietf.org>; Tue, 21 Apr 2015 08:25:29 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t3LFPRCb005736 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Tue, 21 Apr 2015 11:25:28 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com t3LFPRCb005736
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1429629928; bh=az7itZAqnCu8PMD4EhXxG4cgFUQ=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=B7CZ0iSjWjehTQOqVahBLjGfbe7ymZnmtqXQ3RBGIJZqmjSP7/T+LBStim5tAKNER x4DizrSVCj0PbqXCMkRCcrArSR5k3Pw00eUPujc0GRPNOmuC8gKSAIlrEMzMYo+d2N 8VE7yuLH6tbO8hp+Tt0HQH8ZdXvCr8sOXaO+D/9s=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com t3LFPRCb005736
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd06.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Tue, 21 Apr 2015 11:25:05 -0400
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t3LFPAAR024916 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Tue, 21 Apr 2015 11:25:10 -0400
Received: from MXHUB107.corp.emc.com (10.253.50.23) by mxhub27.corp.emc.com (10.254.110.183) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 21 Apr 2015 11:25:10 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.55]) by MXHUB107.corp.emc.com ([10.253.50.23]) with mapi id 14.03.0224.002; Tue, 21 Apr 2015 11:25:09 -0400
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Dallas tsvwg minutes posted
Thread-Index: AdB8R1nM8YMsXOSmTMKKOm80YyKyuQ==
Date: Tue, 21 Apr 2015 15:25:09 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949364681B6@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.105.38.163]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/0hilox3incApdPIFbC82X61HV_A>
Subject: [tsvwg] Dallas tsvwg minutes 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: Tue, 21 Apr 2015 15:25:34 -0000

Many thanks to the scribes, and to Gorry for pulling these together.

https://www.ietf.org/proceedings/92/minutes/minutes-92-tsvwg

Comments and corrections are welcome.

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 Thu Apr 23 05:31:51 2015
Return-Path: <magnus.westerlund@ericsson.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 A52AF1A1AC1 for <tsvwg@ietfa.amsl.com>; Thu, 23 Apr 2015 05:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 x8rMuJdPcHWn for <tsvwg@ietfa.amsl.com>; Thu, 23 Apr 2015 05:31:46 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E2581A0382 for <tsvwg@ietf.org>; Thu, 23 Apr 2015 05:31:45 -0700 (PDT)
X-AuditID: c1b4fb2d-f79a46d0000006b4-0c-5538e6303b3c
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 6A.50.01716.F26E8355; Thu, 23 Apr 2015 14:31:44 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.3.210.2; Thu, 23 Apr 2015 14:31:43 +0200
Message-ID: <5538E62E.2070404@ericsson.com>
Date: Thu, 23 Apr 2015 14:31:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: <tsvwg@ietf.org>, <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com>
In-Reply-To: <20150408122559.24328.89341.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJLMWRmVeSWpSXmKPExsUyM+Jvja7BM4tQg6/PRS1WH5rLaHHszV02 ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvjyfxjLAXntCum/13F1sC4U6mLkZNDQsBE YuX964wQtpjEhXvr2boYuTiEBI4ySjTf3sUE4SxnlPj9ehZYFa+AtsS5NZuBEhwcLAKqEpv7 YkHCbAIWEjd/NLKB2KICURITvx5igSgXlDg58wmYLSLgJPF58m+wGmEBU4lrq5aD2UICjhIP rp4FszmBau79Xgm2ihlo5sz556FseYnmrbOZIeq1JRqaOlgnMArMQrJiFpKWWUhaFjAyr2IU LU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIDMuDW37r7mBc/drxEKMAB6MSD29Cl0WoEGtiWXFl 7iFGaQ4WJXFeO+NDIUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYK6LNrdIO5jxpdpFrjjqo ru+VtTeKs67D/GFgyrmOnF9x6dsX7Tv2+cuJzuMq6qEz/CM4spoSrf7qb3nqG7Y2073vtrH0 EqeZhRNPRi9SX3xp/qujYdyPurknbdN96iz36nD6Vdlj7EXH/61s6ft9iyXs0eWG08uTpq2t Z57/7O9Mp93bn91+qsRSnJFoqMVcVJwIAGFMvTssAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/gXiAOZBzDR66m_HS4Cu-lvPkE5E>
Subject: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-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: Thu, 23 Apr 2015 12:31:48 -0000

Hi,

I have reviewed and have some comments:

1. Section 3.1.1:

    Applications that support an uncontrolled or unadaptive transmission
    behavior SHOULD NOT do so by default and SHOULD instead require users
    to explicitly enable this mode of operation.

I think on could add as an alternative to be integrated with resource 
reservation system so that this mode is only engaged after having been 
granted the resources.

2. Section 3.1.2:

    Applications that at any time exchange only a few UDP datagrams with
    a destination SHOULD still control their transmission behavior by not
    sending on average more than one UDP datagram per round-trip time
    (RTT) to a destination.

In the discussions around the RTP circuit breakers we have found that 
this basic rule has a quite significant corner case that we need to 
discuss. As RTT -> 0, the allowed rate goes to infinity. Now RTT will 
not go to infinity, but I think we have an potential issue already on a 
LAN. Assuming a RTT of 2 ms, you are allowed to send 500 packets a 
second. Just by a 1400 bytes MSS, that is 5.6 mbps. If you have a lan 
supporting 9k Ethernet payload, then your supported non-congestion 
controlled rate becomes 36 mbps. A number of instances of an application 
behaving like this will clearly cause issues in quite a lot of LANs.

So the issue is really that any application that send sufficient number 
of packets per seconds also needs to be congestion controlled, even if 
they are of a one packet per RTT type. This should be clarified, and 
possibly some guidance on what to frequent really is. An application 
sending 10 packets per seconds to a destination, even if only one per 
RTT clearly can sample the path well enough to have a proper CC.

3. Section 3.1.3:

    Even low data-volume UDP flows may benefit from rate control, e.g.,
    an application that sends three copies of a packet to improve
    robustness to loss is RECOMMENDED to pace out those three packets
    over several RTTs, to reduce the probability that all three packets
    will be lost due to the same congestion event.

I would suggest that one changes "rate control" in the first line of the 
above paragraph to "packet pacing" as that is what being discussed. 
Usage of rate control is to easily misinterpreted to mean not the packet 
rate, but also the total bit-rate.

4. Section 3.1.5:

    Applications that support an
    uncontrolled or unadaptive transmission behavior SHOULD NOT do so by
    default and SHOULD instead require users to explicitly enable this
    mode of operation.

Same comment as in comment 1 above.

5. Section 3.4:

    Application developers SHOULD implement additional checks
    where data integrity is important, e.g., through a Cyclic Redundancy
    Check (CRC) included with the data to verify the integrity of an
    entire object/file sent over the UDP service.

I wonder if we should clarify this recommendation on additional checks. 
I think CRCs are good ways to verify that non-malicous changes has 
occured to the payload, but CRC may not be appropriate to "entire 
object/file" where better detection mechanisms may be needed that 
supports longer object better. Unless people would use a really long CRC 
polynom, I think keyed or non-keyed cryptographic hashes are more 
appropriate recommendation for object level changes, and if it can be 
keyed also protect against malicious changes.

6. Section 3.5:

     When an application is deployed in a
    controlled network environment, the deployer SHOULD investigate
    whether the target environment allows applications to use longer
    intervals, or whether it offers mechanisms to explicitly control
    middlebox state timeout durations, for example, using Middlebox
    Communications (MIDCOM) [RFC3303], Next Steps in Signaling (NSIS)
    [RFC5973], or Universal Plug and Play (UPnP) [UPnP].

Add Port Control Protocol to the list?

7. Section 4:

    The IETF has defined a reliable multicast framework [RFC3048] and
    several building blocks to aid the designers of multicast
    applications, such as [RFC3738] or [RFC4654].  Anycast senders must
    be aware that successive messages sent to the same anycast IP address
    may be delivered to different anycast nodes, i.e., arrive at
    different locations in the topology.

I think this paragraph needs to be split into two parts. As the first 
sentence and the Anycast one appears quite unrelated.

8. Section 6:

The IETF standard for securing RTP [RFC3550]
    communication sessions over UDP is the Secure Real-time Transport
    Protocol (SRTP) [RFC3711].

I think this sentence needs to be changed and primarily reference 
RFC7201. I would rather propose something like:

There exist a number of security options for RTP [RFC3550] over UDP, 
especially to accomplish key-management, see [RFC7201]. These options 
covers many different usages, including point-to-point, centralized 
group communication as well as multicast.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Apr 23 21:59:48 2015
Return-Path: <mattmathis@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 2B03A1AD241 for <tsvwg@ietfa.amsl.com>; Thu, 23 Apr 2015 21:59:47 -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 LP3mLe7zZsoi for <tsvwg@ietfa.amsl.com>; Thu, 23 Apr 2015 21:59:46 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07F0C1B2C6B for <tsvwg@ietf.org>; Thu, 23 Apr 2015 21:59:26 -0700 (PDT)
Received: by oign205 with SMTP id n205so31996152oig.2 for <tsvwg@ietf.org>; Thu, 23 Apr 2015 21:59:26 -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 :cc:content-type; bh=CYYYy1b92+vnx8DW01+vXZJ6Vruu+Y0oieHAnsipC0c=; b=BC9hCoUQMDgzvUf8p2nKMUcz5cgHk8hVjqzVT61zuD5hMlzCHsHXp2tMdL9shD8UgV VU0Oxy07gQY3Z2ssDP5te2tPE5Wgc+HLcEDtiDs7iykQW1BwT85VvdyTpovvLXCpGOtz dfd/EF/s88lhs8HtPPcxso/R7SM6x7m8BFYTpQjEcMSGhkx+XriGwmcM1b2Fq0LFqMJ8 rzqHZeB/xYM3u01YRTD4RHAvGck6wi9YKo+ztwTOiTrblywykC9gbfhGkrNPv4CkLB1M HdknQN8RCOX5y2hZGv2x81fJukwsFAtb80JQACEsNbrP/t491OPMrWKXFK+J7URVRiCi MhnA==
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=CYYYy1b92+vnx8DW01+vXZJ6Vruu+Y0oieHAnsipC0c=; b=LXtsJUoWSt5D07E+p7SkQQbk4aVFe1cpN+dEdAX3iqnNbVBbGkRgI+mMDIgKsc8brT SWrKcL+C3AtIpjXhBtInJAgIKBjOcs4tA1/JK2duEpvrFgEBOvoXf4n5abtumc4xA/OE SrV1LBzxUIpTsUjaOCiY317FAtiRbmmGfqvRoioMfrR+qnVcXDZKT/lcVWcp9cRQ/IHd EwprsWbU6jN8S+IJkcIkRNxJRL1PaIb/eEy0NdXdSktiCF0kOCVT3YKGvpO5r/ELlptZ r+iBaElgPBPxrm6bLfAakV4BCACmOP0bz0niMwJrrqklucuzJ1rBDsXKzbz3HckNvW0D MFjg==
X-Gm-Message-State: ALoCoQkPutekEdEry5w8CRhnqNoa1tRFXDNsohoh1pVLjdI3dHkuriMgoDcEt9naNw8qPYcjJM9F
MIME-Version: 1.0
X-Received: by 10.182.138.68 with SMTP id qo4mr5640086obb.56.1429851566473; Thu, 23 Apr 2015 21:59:26 -0700 (PDT)
Received: by 10.182.31.84 with HTTP; Thu, 23 Apr 2015 21:59:26 -0700 (PDT)
In-Reply-To: <5538E62E.2070404@ericsson.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com>
Date: Thu, 23 Apr 2015 21:59:26 -0700
Message-ID: <CAH56bmA6mXWyi+tyWKuVxjxhkLyc6VmUtHHmNQk7u07FKdy+yg@mail.gmail.com>
From: Matt Mathis <mattmathis@google.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=089e0160c42cb3b08a0514714207
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/TXEGGEA_tQUAvlpLnaFI4-g7aIk>
Cc: tsvwg <tsvwg@ietf.org>, draft-ietf-tsvwg-rfc5405bis@tools.ietf.org
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-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 Apr 2015 04:59:47 -0000

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

On Thu, Apr 23, 2015 at 5:31 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> In the discussions around the RTP circuit breakers we have found that this
> basic rule has a quite significant corner case that we need to discuss. As
> RTT -> 0, the allowed rate goes to infinity. Now RTT will not go to
> infinity, but I think we have an potential issue already on a LAN. Assuming
> a RTT of 2 ms, you are allowed to send 500 packets a second. Just by a 1400
> bytes MSS, that is 5.6 mbps. If you have a lan supporting 9k Ethernet
> payload, then your supported non-congestion controlled rate becomes 36
> mbps. A number of instances of an application behaving like this will
> clearly cause issues in quite a lot of LANs.
>

TCP itself has essentially the same corner case.  The above is more
conservative than standard TCP by no more than a factor of two, and that
factor of two has been in our approved code base forever  (from "if
(ssthresh <2) ssthresh=2;" )  I believe that a path having a 1uS RTT and a
bottleneck with a 1 packet drop-from-head queue will demonstrate TCP's
charming behavior (It does need to have early retransmit).

A simpler example would a 1uS path with a two packet drop tail queue.  It
is a slightly different, equally brutal, corner (cwnd=3, one loss every
other RTT or so, probably runs above 50% of link rate, even at 10Gb/s)

We need to kill the delusion that enforcing "TCP friendly congestion
control" is a solution to the Internet capacity allocation problem.   It is
neither necessary nor sufficient.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

Privacy matters!  We know from recent events that people are using our
services to speak in defiance of unjust governments.   We treat privacy and
security as matters of life and death, because for some users, they are.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 23, 2015 at 5:31 AM, Magnus Westerlund <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">magnus.wester=
lund@ericsson.com</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"><=
div style=3D"overflow:hidden">In the discussions around the RTP circuit bre=
akers we have found that this basic rule has a quite significant corner cas=
e that we need to discuss. As RTT -&gt; 0, the allowed rate goes to infinit=
y. Now RTT will not go to infinity, but I think we have an potential issue =
already on a LAN. Assuming a RTT of 2 ms, you are allowed to send 500 packe=
ts a second. Just by a 1400 bytes MSS, that is 5.6 mbps. If you have a lan =
supporting 9k Ethernet payload, then your supported non-congestion controll=
ed rate becomes 36 mbps. A number of instances of an application behaving l=
ike this will clearly cause issues in quite a lot of LANs.<br></div></block=
quote></div><br>TCP itself has essentially the same corner case.=C2=A0 The =
above is more conservative than standard TCP by no more than a factor of tw=
o, and that factor of two has been in our approved code base forever =C2=A0=
(from &quot;if (ssthresh &lt;2) ssthresh=3D2;&quot; ) =C2=A0I believe that =
a path having a 1uS RTT and a bottleneck with a 1 packet drop-from-head que=
ue will demonstrate TCP&#39;s charming behavior (It does need to have early=
 retransmit).</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail=
_extra">A simpler example would a 1uS path with a two packet drop tail queu=
e.=C2=A0 It is a slightly different, equally brutal, corner (cwnd=3D3, one =
loss every other RTT or so, probably runs above 50% of link rate, even at 1=
0Gb/s)</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
>We need to kill the delusion that enforcing &quot;TCP friendly congestion =
control&quot; is a solution to the Internet capacity allocation problem. =
=C2=A0 It is neither necessary nor sufficient.</div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra"><div><div><div dir=3D"ltr"><div>Th=
anks,</div>--MM--<br>The best way to predict the future is to create it. =
=C2=A0- Alan Kay<br><br>Privacy matters!=C2=A0 We know from recent events t=
hat people are using our services to speak in defiance of unjust government=
s. =C2=A0 We treat privacy and security as matters of life and death, becau=
se for some users, they are.</div></div></div>
</div></div>

--089e0160c42cb3b08a0514714207--


From nobody Fri Apr 24 09:16:32 2015
Return-Path: <tom@herbertland.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 6C7291B371C for <tsvwg@ietfa.amsl.com>; Fri, 24 Apr 2015 09:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 TSB9Jg0PsaHB for <tsvwg@ietfa.amsl.com>; Fri, 24 Apr 2015 09:16:30 -0700 (PDT)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1A9F1AC82C for <tsvwg@ietf.org>; Fri, 24 Apr 2015 09:16:29 -0700 (PDT)
Received: by igbhj9 with SMTP id hj9so18868916igb.1 for <tsvwg@ietf.org>; Fri, 24 Apr 2015 09:16:29 -0700 (PDT)
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=VC5k5/QzJeYVonyEcA2rqC5DjbxAVToupHsThj9rJwM=; b=N+65rv1TBVytltl/PlO21u55c5hh+X3soxlgzOcrZ8fla/ePUlfApcseLIVFYeE/l/ +linfS3Z0sQf5eNGycCuw35vx0XTHsdTLxGztLcLQTBtQUiRkEkwW4kUGM8CDSS95VnR WquEYC9pn54R67W1ZGVziQKiXfAfmrMOvdSBDAn7DEbzgUJKv2phhMxeRh6FqIRrlmio GVR2Gr43wrPF0/F8KpDzJhSjJbwkEg3vpsJjl2CmKAg2LoCXv8r7zDxRBgYqq+E3zrdK cYhNFN5FHC4YtdgjkaiT2IWsOYcktSDMygfdh4rbLTaQNeBpx+NjsR8umzDMc1U+HJtl aPBg==
X-Gm-Message-State: ALoCoQlKgEkrUHjvC1P3vBiwb4zzep3CEpYw+6ybWchWPHhSZEX7PcuqIRP3ZxuMAupLElXNsFyJ
MIME-Version: 1.0
X-Received: by 10.107.130.165 with SMTP id m37mr1029008ioi.62.1429892189428; Fri, 24 Apr 2015 09:16:29 -0700 (PDT)
Received: by 10.107.160.2 with HTTP; Fri, 24 Apr 2015 09:16:29 -0700 (PDT)
In-Reply-To: <20150424154144.17864.82671.idtracker@ietfa.amsl.com>
References: <20150424154144.17864.82671.idtracker@ietfa.amsl.com>
Date: Fri, 24 Apr 2015 09:16:29 -0700
Message-ID: <CALx6S34OXdwc5zhom9zY8f7gRSnR=SGYAm89jJo-L5ds0fWjZQ@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: tsvwg@ietf.org, spud@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/p7eoK1-LmTFB-YBj3_TUbO4xfH8>
Subject: [tsvwg] Fwd: New Version Notification for draft-herbert-udp-magic-numbers-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 Apr 2015 16:16:31 -0000

Hello,

This draft generalizes the concept of magic numbers in UDP payloads
like in the SPUD protocol prototype. These are 64 bit constants that
should allow middleboxes to correctly identify the type of a UDP
payload with high confidence. This would be applicable with several
UDP encapsulated protocols that are of interest to middleboxes to
parse.

Posting to tsvwg and spud lists.

Thanks,
Tom

---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Fri, Apr 24, 2015 at 8:41 AM
Subject: New Version Notification for draft-herbert-udp-magic-numbers-00.txt
To: Tom Herbert <tom@herbertland.com>, Lucy Yong <lucy.yong@huawei.com>



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

Name:           draft-herbert-udp-magic-numbers
Revision:       00
Title:          UDP Magic Numbers
Document date:  2015-04-24
Group:          Individual Submission
Pages:          11
URL:
http://www.ietf.org/internet-drafts/draft-herbert-udp-magic-numbers-00.txt
Status:
https://datatracker.ietf.org/doc/draft-herbert-udp-magic-numbers/
Htmlized:       http://tools.ietf.org/html/draft-herbert-udp-magic-numbers-00


Abstract:
   This specification defines magic numbers in UDP which allow a node to
   determine or confirm the protocol contained in a UDP payload. This is
   primarily applicable for encapsulation and transport protocols
   encapsulated within UDP where intermediate devices, such as middle
   boxes, need to parse these protocols for providing service. Magic
   numbers can also be used to multiplex different UDP encapsulated
   protocols over the same UDP port.




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


From nobody Fri Apr 24 11:33:08 2015
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 451EA1ACE46; Fri, 24 Apr 2015 11:33:05 -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 d0gVMlsbhucx; Fri, 24 Apr 2015 11:33:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F25A21ABB1A; Fri, 24 Apr 2015 11:33:03 -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: 6.0.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150424183303.21089.38769.idtracker@ietfa.amsl.com>
Date: Fri, 24 Apr 2015 11:33:03 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/Mci7QrDH2DDmaYajnp45DlykMR4>
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-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: Fri, 24 Apr 2015 18:33:05 -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           : Recommendations on Using Assigned Transport Port Numbers
        Author          : Joe Touch
	Filename        : draft-ietf-tsvwg-port-use-11.txt
	Pages           : 23
	Date            : 2015-04-24

Abstract:
   This document provides recommendations to application and service
   protocol designers on how to use the assigned transport protocol
   port number space and when to request a port assignment from IANA.
   It provides designer guidelines on how to interact with the IANA
   processes defined in RFC6335, thus serving to complement (but not
   update) that document.


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

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

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-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 Sun Apr 26 14:05:20 2015
Return-Path: <alissa@cooperw.in>
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 E72581AD09C; Fri, 24 Apr 2015 15:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8] 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 fwfT7KSND_Wo; Fri, 24 Apr 2015 15:14:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A278F1AD087; Fri, 24 Apr 2015 15:14:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150424221415.15450.29279.idtracker@ietfa.amsl.com>
Date: Fri, 24 Apr 2015 15:14:15 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/QqhRo63Ymp3GFB4RCrRao0Bk6xs>
X-Mailman-Approved-At: Sun, 26 Apr 2015 14:05:19 -0700
Cc: draft-ietf-tsvwg-port-use@ietf.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org
Subject: [tsvwg] Alissa Cooper's No Objection on draft-ietf-tsvwg-port-use-11: (with COMMENT)
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 Apr 2015 22:14:17 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-tsvwg-port-use-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my DISCUSS!

---

I think I may have some overlapping comments with Barry, but I wrote this
before I saw his comments, so my apologies.

-- Sec 5:
"Port numbers can also be useful for other purposes."

I would suggest s/useful/used/ because whether the purposes listed in the
previous paragraph (e.g., monitoring, blocking, etc. based on port
number) are considered "useful" is in the eye of the beholder.

-- Sec 7.4:
The term "security" is really vague. It would help to define what is
meant by "security" or "secure service."

-- Sec 7.4 and 7.5:
Both of these sections contain recommendations that are good, but seem
out of place in this document unless they could be made more specific to
port use. The ones that jumped out at me are:

   >> New services SHOULD support security, either directly or via a
   secure transport such as TLS [RFC5246].

   >> Insecure versions of new or existing secure services SHOULD be
   avoided because of the new vulnerability they create.
   
   >> Version support SHOULD be included in new services.

I would say to either remove these or add in the context of what they
have to do with port number assignment (e.g., "Version support SHOULD be
included in new services rather than relying on different port number
assignments for different versions.")

-- Sec 7.7:
"Deployments that use port numbers before deployment complicate IANA
   management of the port number space."

I think this is supposed to say "before assignment" rather than "before
deployment."

-- Sec 7.8:
""Squatting" describes the use of a number from the assigned range in
   deployed software without IANA assignment. It is hazardous because
   IANA cannot track such usage and thus cannot avoid making legitimate
   assignments that conflict with such unauthorized usage.

   Such "squatted" port numbers remain unassigned, and IANA retains the
   right to assign them when requested by applicants."

This is a little confusing -- is the first sentence supposed to say
"unassigned range"? If not, what is the assigned range, and why is IANA
said to retain the right to assign numbers that are already assigned? I
would have thought squatting would be understood as using unassigned
numbers in the system and user ranges.

"In
   particular, any unassigned code from the assigned ranges will be
   assigned by IANA, and any conflict will be easily resolved as the
   protocol designer's fault once that happens (because they would not
   be the assignee). This may reflect in the public's judgment on the
   quality of their expertise and cooperation with the Internet
   community."

This seems a little over-the-top to me. I would suggest:

"IANA may assign any code from the system or user ranges to applicants
that meet all of the relevant criteria, and is not obligated to take into
consideration the existence of squatters when doing so. Squatting is
viewed as uncooperative behavior in the Internet community."



From nobody Mon Apr 27 13:36:15 2015
Return-Path: <touch@isi.edu>
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 137031A1A28; Mon, 27 Apr 2015 13:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 L8YDGLRB6jKv; Mon, 27 Apr 2015 13:36:12 -0700 (PDT)
Received: from webspace.isi.edu (webspace.isi.edu [128.9.64.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 933D71A034C; Mon, 27 Apr 2015 13:36:12 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id t3RKZktx008621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 27 Apr 2015 13:35:47 -0700 (PDT)
Message-ID: <553E9DA2.5060303@isi.edu>
Date: Mon, 27 Apr 2015 13:35:46 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: internet-drafts@ietf.org, i-d-announce@ietf.org
References: <20150424183303.21089.38769.idtracker@ietfa.amsl.com>
In-Reply-To: <20150424183303.21089.38769.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/p5qxhy8bgEuht4GgICYnzmrkeCA>
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-port-use-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: Mon, 27 Apr 2015 20:36:14 -0000

FYI, this update is to address the final set of pending IESG comments.

Joe

On 4/24/2015 11:33 AM, internet-drafts@ietf.org wrote:
> 
> 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           : Recommendations on Using Assigned Transport Port Numbers
>         Author          : Joe Touch
> 	Filename        : draft-ietf-tsvwg-port-use-11.txt
> 	Pages           : 23
> 	Date            : 2015-04-24
> 
> Abstract:
>    This document provides recommendations to application and service
>    protocol designers on how to use the assigned transport protocol
>    port number space and when to request a port assignment from IANA.
>    It provides designer guidelines on how to interact with the IANA
>    processes defined in RFC6335, thus serving to complement (but not
>    update) that document.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-port-use-11
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-port-use-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 Wed Apr 29 07:27:18 2015
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 21F801A1AC9 for <tsvwg@ietfa.amsl.com>; Wed, 29 Apr 2015 07:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 0UwkwRgXJgRb for <tsvwg@ietfa.amsl.com>; Wed, 29 Apr 2015 07:27:15 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03ECE1A1A7E for <tsvwg@ietf.org>; Wed, 29 Apr 2015 07:27:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.11,671,1422950400"; d="scan'208";a="39997148"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx141-out.netapp.com with ESMTP; 29 Apr 2015 07:26:14 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.995.29; Wed, 29 Apr 2015 07:26:14 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::f07f:691d:89d:53b7%21]) with mapi id 15.00.0995.031; Wed, 29 Apr 2015 07:26:14 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-02.txt
Thread-Index: AQHQfcF7khB0IV5Y40KoUkCu4qu/7Z1kirgA
Date: Wed, 29 Apr 2015 14:26:13 +0000
Message-ID: <7BAA3E07-8711-4DA6-9080-9ED3B412C56B@netapp.com>
References: <20150408122559.24328.89341.idtracker@ietfa.amsl.com> <5538E62E.2070404@ericsson.com>
In-Reply-To: <5538E62E.2070404@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.2098)
x-originating-ip: [10.122.56.79]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0433486FE292B546925571C983F70289@hq.netapp.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/GweOyuqnjbxC8Gs4VXo9SfQVaA4>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rfc5405bis@tools.ietf.org" <draft-ietf-tsvwg-rfc5405bis@tools.ietf.org>
Subject: Re: [tsvwg] Review of draft-ietf-tsvwg-rfc5405bis-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: Wed, 29 Apr 2015 14:27:17 -0000

VGhhbmtzIE1hZ251cyEgSSd2ZSBwdXQgdGhpcyBvbiBteSBjaGFuZ2UgbGlzdCwgYnV0IGl0IG1h
eSB0YWtlIGEgd2hpbGUgdG8gc3BpbiBhIG5ldyB2ZXJzaW9uLg0KDQpMYXJzDQoNCk9uIDIwMTUt
NC0yMywgYXQgMTQ6MzEsIE1hZ251cyBXZXN0ZXJsdW5kIDxtYWdudXMud2VzdGVybHVuZEBlcmlj
c3Nvbi5jb20+IHdyb3RlOg0KPiANCj4gSGksDQo+IA0KPiBJIGhhdmUgcmV2aWV3ZWQgYW5kIGhh
dmUgc29tZSBjb21tZW50czoNCj4gDQo+IDEuIFNlY3Rpb24gMy4xLjE6DQo+IA0KPiAgIEFwcGxp
Y2F0aW9ucyB0aGF0IHN1cHBvcnQgYW4gdW5jb250cm9sbGVkIG9yIHVuYWRhcHRpdmUgdHJhbnNt
aXNzaW9uDQo+ICAgYmVoYXZpb3IgU0hPVUxEIE5PVCBkbyBzbyBieSBkZWZhdWx0IGFuZCBTSE9V
TEQgaW5zdGVhZCByZXF1aXJlIHVzZXJzDQo+ICAgdG8gZXhwbGljaXRseSBlbmFibGUgdGhpcyBt
b2RlIG9mIG9wZXJhdGlvbi4NCj4gDQo+IEkgdGhpbmsgb24gY291bGQgYWRkIGFzIGFuIGFsdGVy
bmF0aXZlIHRvIGJlIGludGVncmF0ZWQgd2l0aCByZXNvdXJjZSByZXNlcnZhdGlvbiBzeXN0ZW0g
c28gdGhhdCB0aGlzIG1vZGUgaXMgb25seSBlbmdhZ2VkIGFmdGVyIGhhdmluZyBiZWVuIGdyYW50
ZWQgdGhlIHJlc291cmNlcy4NCj4gDQo+IDIuIFNlY3Rpb24gMy4xLjI6DQo+IA0KPiAgIEFwcGxp
Y2F0aW9ucyB0aGF0IGF0IGFueSB0aW1lIGV4Y2hhbmdlIG9ubHkgYSBmZXcgVURQIGRhdGFncmFt
cyB3aXRoDQo+ICAgYSBkZXN0aW5hdGlvbiBTSE9VTEQgc3RpbGwgY29udHJvbCB0aGVpciB0cmFu
c21pc3Npb24gYmVoYXZpb3IgYnkgbm90DQo+ICAgc2VuZGluZyBvbiBhdmVyYWdlIG1vcmUgdGhh
biBvbmUgVURQIGRhdGFncmFtIHBlciByb3VuZC10cmlwIHRpbWUNCj4gICAoUlRUKSB0byBhIGRl
c3RpbmF0aW9uLg0KPiANCj4gSW4gdGhlIGRpc2N1c3Npb25zIGFyb3VuZCB0aGUgUlRQIGNpcmN1
aXQgYnJlYWtlcnMgd2UgaGF2ZSBmb3VuZCB0aGF0IHRoaXMgYmFzaWMgcnVsZSBoYXMgYSBxdWl0
ZSBzaWduaWZpY2FudCBjb3JuZXIgY2FzZSB0aGF0IHdlIG5lZWQgdG8gZGlzY3Vzcy4gQXMgUlRU
IC0+IDAsIHRoZSBhbGxvd2VkIHJhdGUgZ29lcyB0byBpbmZpbml0eS4gTm93IFJUVCB3aWxsIG5v
dCBnbyB0byBpbmZpbml0eSwgYnV0IEkgdGhpbmsgd2UgaGF2ZSBhbiBwb3RlbnRpYWwgaXNzdWUg
YWxyZWFkeSBvbiBhIExBTi4gQXNzdW1pbmcgYSBSVFQgb2YgMiBtcywgeW91IGFyZSBhbGxvd2Vk
IHRvIHNlbmQgNTAwIHBhY2tldHMgYSBzZWNvbmQuIEp1c3QgYnkgYSAxNDAwIGJ5dGVzIE1TUywg
dGhhdCBpcyA1LjYgbWJwcy4gSWYgeW91IGhhdmUgYSBsYW4gc3VwcG9ydGluZyA5ayBFdGhlcm5l
dCBwYXlsb2FkLCB0aGVuIHlvdXIgc3VwcG9ydGVkIG5vbi1jb25nZXN0aW9uIGNvbnRyb2xsZWQg
cmF0ZSBiZWNvbWVzIDM2IG1icHMuIEEgbnVtYmVyIG9mIGluc3RhbmNlcyBvZiBhbiBhcHBsaWNh
dGlvbiBiZWhhdmluZyBsaWtlIHRoaXMgd2lsbCBjbGVhcmx5IGNhdXNlIGlzc3VlcyBpbiBxdWl0
ZSBhIGxvdCBvZiBMQU5zLg0KPiANCj4gU28gdGhlIGlzc3VlIGlzIHJlYWxseSB0aGF0IGFueSBh
cHBsaWNhdGlvbiB0aGF0IHNlbmQgc3VmZmljaWVudCBudW1iZXIgb2YgcGFja2V0cyBwZXIgc2Vj
b25kcyBhbHNvIG5lZWRzIHRvIGJlIGNvbmdlc3Rpb24gY29udHJvbGxlZCwgZXZlbiBpZiB0aGV5
IGFyZSBvZiBhIG9uZSBwYWNrZXQgcGVyIFJUVCB0eXBlLiBUaGlzIHNob3VsZCBiZSBjbGFyaWZp
ZWQsIGFuZCBwb3NzaWJseSBzb21lIGd1aWRhbmNlIG9uIHdoYXQgdG8gZnJlcXVlbnQgcmVhbGx5
IGlzLiBBbiBhcHBsaWNhdGlvbiBzZW5kaW5nIDEwIHBhY2tldHMgcGVyIHNlY29uZHMgdG8gYSBk
ZXN0aW5hdGlvbiwgZXZlbiBpZiBvbmx5IG9uZSBwZXIgUlRUIGNsZWFybHkgY2FuIHNhbXBsZSB0
aGUgcGF0aCB3ZWxsIGVub3VnaCB0byBoYXZlIGEgcHJvcGVyIENDLg0KPiANCj4gMy4gU2VjdGlv
biAzLjEuMzoNCj4gDQo+ICAgRXZlbiBsb3cgZGF0YS12b2x1bWUgVURQIGZsb3dzIG1heSBiZW5l
Zml0IGZyb20gcmF0ZSBjb250cm9sLCBlLmcuLA0KPiAgIGFuIGFwcGxpY2F0aW9uIHRoYXQgc2Vu
ZHMgdGhyZWUgY29waWVzIG9mIGEgcGFja2V0IHRvIGltcHJvdmUNCj4gICByb2J1c3RuZXNzIHRv
IGxvc3MgaXMgUkVDT01NRU5ERUQgdG8gcGFjZSBvdXQgdGhvc2UgdGhyZWUgcGFja2V0cw0KPiAg
IG92ZXIgc2V2ZXJhbCBSVFRzLCB0byByZWR1Y2UgdGhlIHByb2JhYmlsaXR5IHRoYXQgYWxsIHRo
cmVlIHBhY2tldHMNCj4gICB3aWxsIGJlIGxvc3QgZHVlIHRvIHRoZSBzYW1lIGNvbmdlc3Rpb24g
ZXZlbnQuDQo+IA0KPiBJIHdvdWxkIHN1Z2dlc3QgdGhhdCBvbmUgY2hhbmdlcyAicmF0ZSBjb250
cm9sIiBpbiB0aGUgZmlyc3QgbGluZSBvZiB0aGUgYWJvdmUgcGFyYWdyYXBoIHRvICJwYWNrZXQg
cGFjaW5nIiBhcyB0aGF0IGlzIHdoYXQgYmVpbmcgZGlzY3Vzc2VkLiBVc2FnZSBvZiByYXRlIGNv
bnRyb2wgaXMgdG8gZWFzaWx5IG1pc2ludGVycHJldGVkIHRvIG1lYW4gbm90IHRoZSBwYWNrZXQg
cmF0ZSwgYnV0IGFsc28gdGhlIHRvdGFsIGJpdC1yYXRlLg0KPiANCj4gNC4gU2VjdGlvbiAzLjEu
NToNCj4gDQo+ICAgQXBwbGljYXRpb25zIHRoYXQgc3VwcG9ydCBhbg0KPiAgIHVuY29udHJvbGxl
ZCBvciB1bmFkYXB0aXZlIHRyYW5zbWlzc2lvbiBiZWhhdmlvciBTSE9VTEQgTk9UIGRvIHNvIGJ5
DQo+ICAgZGVmYXVsdCBhbmQgU0hPVUxEIGluc3RlYWQgcmVxdWlyZSB1c2VycyB0byBleHBsaWNp
dGx5IGVuYWJsZSB0aGlzDQo+ICAgbW9kZSBvZiBvcGVyYXRpb24uDQo+IA0KPiBTYW1lIGNvbW1l
bnQgYXMgaW4gY29tbWVudCAxIGFib3ZlLg0KPiANCj4gNS4gU2VjdGlvbiAzLjQ6DQo+IA0KPiAg
IEFwcGxpY2F0aW9uIGRldmVsb3BlcnMgU0hPVUxEIGltcGxlbWVudCBhZGRpdGlvbmFsIGNoZWNr
cw0KPiAgIHdoZXJlIGRhdGEgaW50ZWdyaXR5IGlzIGltcG9ydGFudCwgZS5nLiwgdGhyb3VnaCBh
IEN5Y2xpYyBSZWR1bmRhbmN5DQo+ICAgQ2hlY2sgKENSQykgaW5jbHVkZWQgd2l0aCB0aGUgZGF0
YSB0byB2ZXJpZnkgdGhlIGludGVncml0eSBvZiBhbg0KPiAgIGVudGlyZSBvYmplY3QvZmlsZSBz
ZW50IG92ZXIgdGhlIFVEUCBzZXJ2aWNlLg0KPiANCj4gSSB3b25kZXIgaWYgd2Ugc2hvdWxkIGNs
YXJpZnkgdGhpcyByZWNvbW1lbmRhdGlvbiBvbiBhZGRpdGlvbmFsIGNoZWNrcy4gSSB0aGluayBD
UkNzIGFyZSBnb29kIHdheXMgdG8gdmVyaWZ5IHRoYXQgbm9uLW1hbGljb3VzIGNoYW5nZXMgaGFz
IG9jY3VyZWQgdG8gdGhlIHBheWxvYWQsIGJ1dCBDUkMgbWF5IG5vdCBiZSBhcHByb3ByaWF0ZSB0
byAiZW50aXJlIG9iamVjdC9maWxlIiB3aGVyZSBiZXR0ZXIgZGV0ZWN0aW9uIG1lY2hhbmlzbXMg
bWF5IGJlIG5lZWRlZCB0aGF0IHN1cHBvcnRzIGxvbmdlciBvYmplY3QgYmV0dGVyLiBVbmxlc3Mg
cGVvcGxlIHdvdWxkIHVzZSBhIHJlYWxseSBsb25nIENSQyBwb2x5bm9tLCBJIHRoaW5rIGtleWVk
IG9yIG5vbi1rZXllZCBjcnlwdG9ncmFwaGljIGhhc2hlcyBhcmUgbW9yZSBhcHByb3ByaWF0ZSBy
ZWNvbW1lbmRhdGlvbiBmb3Igb2JqZWN0IGxldmVsIGNoYW5nZXMsIGFuZCBpZiBpdCBjYW4gYmUg
a2V5ZWQgYWxzbyBwcm90ZWN0IGFnYWluc3QgbWFsaWNpb3VzIGNoYW5nZXMuDQo+IA0KPiA2LiBT
ZWN0aW9uIDMuNToNCj4gDQo+ICAgIFdoZW4gYW4gYXBwbGljYXRpb24gaXMgZGVwbG95ZWQgaW4g
YQ0KPiAgIGNvbnRyb2xsZWQgbmV0d29yayBlbnZpcm9ubWVudCwgdGhlIGRlcGxveWVyIFNIT1VM
RCBpbnZlc3RpZ2F0ZQ0KPiAgIHdoZXRoZXIgdGhlIHRhcmdldCBlbnZpcm9ubWVudCBhbGxvd3Mg
YXBwbGljYXRpb25zIHRvIHVzZSBsb25nZXINCj4gICBpbnRlcnZhbHMsIG9yIHdoZXRoZXIgaXQg
b2ZmZXJzIG1lY2hhbmlzbXMgdG8gZXhwbGljaXRseSBjb250cm9sDQo+ICAgbWlkZGxlYm94IHN0
YXRlIHRpbWVvdXQgZHVyYXRpb25zLCBmb3IgZXhhbXBsZSwgdXNpbmcgTWlkZGxlYm94DQo+ICAg
Q29tbXVuaWNhdGlvbnMgKE1JRENPTSkgW1JGQzMzMDNdLCBOZXh0IFN0ZXBzIGluIFNpZ25hbGlu
ZyAoTlNJUykNCj4gICBbUkZDNTk3M10sIG9yIFVuaXZlcnNhbCBQbHVnIGFuZCBQbGF5IChVUG5Q
KSBbVVBuUF0uDQo+IA0KPiBBZGQgUG9ydCBDb250cm9sIFByb3RvY29sIHRvIHRoZSBsaXN0Pw0K
PiANCj4gNy4gU2VjdGlvbiA0Og0KPiANCj4gICBUaGUgSUVURiBoYXMgZGVmaW5lZCBhIHJlbGlh
YmxlIG11bHRpY2FzdCBmcmFtZXdvcmsgW1JGQzMwNDhdIGFuZA0KPiAgIHNldmVyYWwgYnVpbGRp
bmcgYmxvY2tzIHRvIGFpZCB0aGUgZGVzaWduZXJzIG9mIG11bHRpY2FzdA0KPiAgIGFwcGxpY2F0
aW9ucywgc3VjaCBhcyBbUkZDMzczOF0gb3IgW1JGQzQ2NTRdLiAgQW55Y2FzdCBzZW5kZXJzIG11
c3QNCj4gICBiZSBhd2FyZSB0aGF0IHN1Y2Nlc3NpdmUgbWVzc2FnZXMgc2VudCB0byB0aGUgc2Ft
ZSBhbnljYXN0IElQIGFkZHJlc3MNCj4gICBtYXkgYmUgZGVsaXZlcmVkIHRvIGRpZmZlcmVudCBh
bnljYXN0IG5vZGVzLCBpLmUuLCBhcnJpdmUgYXQNCj4gICBkaWZmZXJlbnQgbG9jYXRpb25zIGlu
IHRoZSB0b3BvbG9neS4NCj4gDQo+IEkgdGhpbmsgdGhpcyBwYXJhZ3JhcGggbmVlZHMgdG8gYmUg
c3BsaXQgaW50byB0d28gcGFydHMuIEFzIHRoZSBmaXJzdCBzZW50ZW5jZSBhbmQgdGhlIEFueWNh
c3Qgb25lIGFwcGVhcnMgcXVpdGUgdW5yZWxhdGVkLg0KPiANCj4gOC4gU2VjdGlvbiA2Og0KPiAN
Cj4gVGhlIElFVEYgc3RhbmRhcmQgZm9yIHNlY3VyaW5nIFJUUCBbUkZDMzU1MF0NCj4gICBjb21t
dW5pY2F0aW9uIHNlc3Npb25zIG92ZXIgVURQIGlzIHRoZSBTZWN1cmUgUmVhbC10aW1lIFRyYW5z
cG9ydA0KPiAgIFByb3RvY29sIChTUlRQKSBbUkZDMzcxMV0uDQo+IA0KPiBJIHRoaW5rIHRoaXMg
c2VudGVuY2UgbmVlZHMgdG8gYmUgY2hhbmdlZCBhbmQgcHJpbWFyaWx5IHJlZmVyZW5jZSBSRkM3
MjAxLiBJIHdvdWxkIHJhdGhlciBwcm9wb3NlIHNvbWV0aGluZyBsaWtlOg0KPiANCj4gVGhlcmUg
ZXhpc3QgYSBudW1iZXIgb2Ygc2VjdXJpdHkgb3B0aW9ucyBmb3IgUlRQIFtSRkMzNTUwXSBvdmVy
IFVEUCwgZXNwZWNpYWxseSB0byBhY2NvbXBsaXNoIGtleS1tYW5hZ2VtZW50LCBzZWUgW1JGQzcy
MDFdLiBUaGVzZSBvcHRpb25zIGNvdmVycyBtYW55IGRpZmZlcmVudCB1c2FnZXMsIGluY2x1ZGlu
ZyBwb2ludC10by1wb2ludCwgY2VudHJhbGl6ZWQgZ3JvdXAgY29tbXVuaWNhdGlvbiBhcyB3ZWxs
IGFzIG11bHRpY2FzdC4NCj4gDQo+IENoZWVycw0KPiANCj4gTWFnbnVzIFdlc3Rlcmx1bmQNCj4g
DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCj4gU2VydmljZXMsIE1lZGlhIGFuZCBOZXR3b3JrIGZlYXR1cmVz
LCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFhNDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gRXJpY3Nzb24g
QUIgICAgICAgICAgICAgICAgIHwgUGhvbmUgICs0NiAxMCA3MTQ4Mjg3DQo+IEbDpHLDtmdhdGFu
IDYgICAgICAgICAgICAgICAgIHwgTW9iaWxlICs0NiA3MyAwOTQ5MDc5DQo+IFNFLTE2NCA4MCBT
dG9ja2hvbG0sIFN3ZWRlbiB8IG1haWx0bzogbWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29t
DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCj4gDQoNCg==

