
From nobody Tue Mar 13 04:56:51 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6967D12D889 for <clue@ietfa.amsl.com>; Tue, 13 Mar 2018 04:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Level: 
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NACF044zy_Qu for <clue@ietfa.amsl.com>; Tue, 13 Mar 2018 04:56:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 1815C12D893 for <clue@ietf.org>; Tue, 13 Mar 2018 04:56:43 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 32BD1C8BFACBA for <clue@ietf.org>; Tue, 13 Mar 2018 11:56:39 +0000 (GMT)
Received: from DGGEMM424-HUB.china.huawei.com (10.1.198.41) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 13 Mar 2018 11:56:40 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by dggemm424-hub.china.huawei.com ([10.1.198.41]) with mapi id 14.03.0361.001; Tue, 13 Mar 2018 19:56:37 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: "clue@ietf.org" <clue@ietf.org>
Thread-Topic: Question about timers  (retry and timeouts) in draft-ietf-clue-protocol
Thread-Index: AdOj2NoMzin0OvqsR8qbld+eN+ClsA==
Date: Tue, 13 Mar 2018 11:56:37 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD86C0D2@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.71]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD86C0D2DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/Z8QjM3BEHlyv4nkQRlZBGOnPd5I>
Subject: [clue] Question about timers (retry and timeouts) in draft-ietf-clue-protocol
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 11:56:45 -0000

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

Hi,
An important issue that was made by Adam during his AD review has to do wit=
h timeout and retry thresholds, please provide feedback

This is the comment:

BLOCKER: General: There are several mentions of timeouts and retry threshol=
ds in the text and its corresponding state machines; however, the document =
neither defines nor cites a document as defining what these timeout and ret=
ry values are. These need to be defined and described. If the timer and ret=
ry scheme allows the two ends of the connection to have different values fo=
r timeouts and number of retries, then there need to be additional error pr=
ocedures that allow the MC and MP state machines to stay in sync (if the ti=
mer/retry values can be different, it's possible for one state machine to t=
ransition to "terminated," while the other is still active, and you need me=
ssaging to clean this up). The remainder of this comment is non-blocking: R=
elated to this, the document frequently refers to retries as "expiring" (e.=
g., "retry expired" on the state diagrams). That doesn't really make sense =
unless "retry" is the name of a timer rather than a counter; I think you me=
an to say "exhausted" or something similar.

My view as individual:

The CLUE protocol is delivered using SCTP "CLUE entities are required to us=
e ordered SCTP message delivery, with full reliability" so there is no prob=
lem with timeout for retry for the data channel (https://tools.ietf.org/htm=
l/draft-ietf-clue-datachannel-14#section-3.3.2 )

So the retry and timeout are for the application level and not for the sctp=
 transport.

>From the discussion on the mailing list during the WGLC


"The idea here is that the MC avoids entering a loop where the MP keeps on =
sending an erroneous ADV hence forcing the MC to respond with a NACK. If th=
is situation iterates for a while (# of retries), the MC terminates the ong=
oing CLUE "session".

I noticed that the discussion started even earlier and the conclusion was t=
hat retry and timeout are needed but we also need default values which were=
 never listed

My understanding is that when a receiver of a protocol message sends a nega=
tive ack as response he allows for reties of fixed message and will allow i=
t n times or quit after x time if no new message arrives.

I think that for retries any number is good but I think that 2 is OK since =
is the message sender cannot send a valid message we should abandon the cal=
l. As for timeout this can be a short one that will still allow for a round=
 trip so my view that 1 second is enough

Other thoughs?



One side comment in section 6.2 there are two instances of "number of timeo=
uts" ?



Roni Even
Clue co-chair

--_000_6E58094ECC8D8344914996DAD28F1CCD86C0D2DGGEMM506MBXchina_
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">An important issue that was made by Adam during his =
AD review has to do with timeout and retry thresholds, please provide feedb=
ack<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is the comment:<o:p></o:p></p>
<p>BLOCKER: General: There are several mentions of timeouts and retry thres=
holds in the text and its corresponding state machines; however, the docume=
nt neither defines nor cites a document as defining what these timeout and =
retry values are. These need to
 be defined and described. If the timer and retry scheme allows the two end=
s of the connection to have different values for timeouts and number of ret=
ries, then there need to be additional error procedures that allow the MC a=
nd MP state machines to stay in
 sync (if the timer/retry values can be different, it's possible for one st=
ate machine to transition to &quot;terminated,&quot; while the other is sti=
ll active, and you need messaging to clean this up). The remainder of this =
comment is non-blocking: Related to this,
 the document frequently refers to retries as &quot;expiring&quot; (e.g., &=
quot;retry expired&quot; on the state diagrams). That doesn't really make s=
ense unless &quot;retry&quot; is the name of a timer rather than a counter;=
 I think you mean to say &quot;exhausted&quot; or something similar.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">My view as individual:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The CLUE protocol is delivered using SCTP &#8220;<sp=
an style=3D"color:black">CLUE entities are required to use ordered SCTP mes=
sage delivery, with full reliability&#8221; so there is no problem with tim=
eout for retry for the data channel (<a href=3D"https://tools.ietf.org/html=
/draft-ietf-clue-datachannel-14#section-3.3.2">https://tools.ietf.org/html/=
draft-ietf-clue-datachannel-14#section-3.3.2</a>
 )<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">So the retry and timeout=
 are for the application level and not for the sctp transport.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">From the discussion on t=
he mailing list during the WGLC<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black=
">&#8220;</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#333333">The idea here is that the MC avo=
ids entering a loop where the MP keeps on sending an erroneous ADV hence fo=
rcing the MC to respond with a NACK. If this situation iterates for a while=
 (# of retries), the MC terminates the ongoing CLUE &#8220;session&#8221;. =
<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#3333=
33">I noticed that the discussion started even earlier and the conclusion w=
as that retry and timeout are needed but we also need default values which =
were never listed<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#3333=
33">My understanding is that when a receiver of a protocol message sends a =
negative ack as response he allows for reties of fixed message and will all=
ow it n times or quit after x time if no new message arrives.<o:p></o:p></s=
pan></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#3333=
33">I think that for retries any number is good but I think that 2 is OK si=
nce is the message sender cannot send a valid message we should abandon the=
 call. As for timeout this can be a short one that will still allow for a r=
ound trip so my view that 1 second is enough<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#3333=
33">Other thoughs?<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#3333=
33"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#333333">One side comment in section 6.2 there are t=
wo instances of &#8220;</span><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">number of timeouts</=
span><span style=3D"color:black">&#8221; ?<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Roni Even<o:p></o:p></p>
<p class=3D"MsoNormal">Clue co-chair<o:p></o:p></p>
</div>
</body>
</html>

--_000_6E58094ECC8D8344914996DAD28F1CCD86C0D2DGGEMM506MBXchina_--

