
From nobody Wed May 11 01:27:27 2016
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E78712D511 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 01:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.216
X-Spam-Level: 
X-Spam-Status: No, score=-5.216 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, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 c9J-o1NLu6Dm for <dots@ietfa.amsl.com>; Wed, 11 May 2016 01:27:21 -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 54DB012D1C8 for <dots@ietf.org>; Wed, 11 May 2016 01:27:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CJQ77707; Wed, 11 May 2016 08:27:17 +0000 (GMT)
Received: from SZXEMA418-HUB.china.huawei.com (10.82.72.36) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 11 May 2016 09:27:16 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.36]) by SZXEMA418-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0235.001; Wed, 11 May 2016 16:27:09 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Andrew Mortensen <amortensen@arbor.net>, Robert Moskowitz <rgm-sec@htt-consult.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: Hi, some comments to DOTS requirements draft: 
Thread-Index: AdGrXuf1w+vuVmiOSjSckzMJsciMJg==
Date: Wed, 11 May 2016 08:27:08 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.91]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12AF2FE92SZXEMA502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5732ECE6.001F, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.36, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9b90905c19673114f6e06ad9a2bd044c
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/RV-AMpepbN1ctzDbBP7XHfoQfCs>
Cc: "dots@ietf.org" <dots@ietf.org>
Subject: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 08:27:25 -0000

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

Hi authors,
By reviewing this draft recently, I have the following new comments:

1.       Inter-domain coordinated DDoS protection is the important part of =
the whole DOTS solution, but it seems that current DOTS requirements draft =
does not include enough contents about this part. Especially in the followi=
ng sections:

1)       In Section 1.1: it only mentions the problem of missing the standa=
rd interface between clients and ddos protection providers (C2P scenario), =
totally misses describing the same problem for the providers to providers (=
P2P) scenario. Correspondingly, this section only emphasis the benefits of =
real-time response for the C2P scenario, do not mention other benefits of r=
esource/capabilities sharing, worldwide optimized mitigation and near sourc=
e mitigation for the P2P scenario. Please include this kind of contents in =
later version, and you can reference to other 2 DOTS drafts about inter-dom=
ain DOTS use cases and mechanisms;

2)       In Section 1.2: For clarity, I suggest to add a new terminology to=
 specify what is the domain in ODTS scope. A domain can be a network domain=
, a SMB network, a DDoS protection provider network, etc;

2.       In Section 1.2, some modification should be made to the terminolog=
ies for DOTS client, DOTS server, Client signal and Server signal, as follo=
wing:

1)       DOTS client: "..., as well as exchanging and updating other inform=
ation with DOTS server or relay, such as mitigation scope, mitigation effic=
acy and mitigation status.";

2)       DOTS server: "..., as well as exchanging and updating other inform=
ation with DOTS client or relay, such as mitigation scope, mitigation effic=
acy and mitigation status.";

3)       Client signal: "... Other signals include the messages for updatin=
g information with DOTS server or relay, such as mitigation scope and mitig=
ation efficacy.";

4)       Server signal: "... The other server signal is mitigation terminat=
ion notification ."

3.       A series of requirements for the DOTS relay are still missed in cu=
rrent draft. We need to consider how to incorporate them;

4.       In Section 2.3, suggest to add the requirement description for the=
 DOTS client's registration and registration cancelling messages, DOTS serv=
er's registration response and registration cancelling response message, wh=
ich are conveyed over the data channel.

Thanks!

B.R.
Frank

--_000_C02846B1344F344EB4FAA6FA7AF481F12AF2FE92SZXEMA502MBSchi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:21.0pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:944851610;
	mso-list-type:hybrid;
	mso-list-template-ids:-1858020660 692121452 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%2\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:42.0pt;
	text-indent:-21.0pt;}
@list l1
	{mso-list-id:1366905426;
	mso-list-type:hybrid;
	mso-list-template-ids:-1850994198 -1423698318 67698713 67698715 67698703 6=
7698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:2143645971;
	mso-list-type:hybrid;
	mso-list-template-ids:-2022378860 2030065304 67698713 67698715 67698703 67=
698713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi authors,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">By reviewing this draft recentl=
y, I have the following new comments:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">1=
.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Inter-domain coordinate=
d DDoS protection is the important part of the whole DOTS solution, but it =
seems that current DOTS requirements draft does not include enough contents=
 about this part. Especially in the
 following sections:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l1 level1 lfo2">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">1=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">In Section 1.1: it only=
 mentions the problem of missing the standard interface between clients and=
 ddos protection providers (C2P scenario), totally misses describing the sa=
me problem for the providers to providers
 (P2P) scenario. Correspondingly, this section only emphasis the benefits o=
f real-time response for the C2P scenario, do not mention other benefits of=
 resource/capabilities sharing, worldwide optimized mitigation and near sou=
rce mitigation for the P2P scenario.
 Please include this kind of contents in later version, and you can referen=
ce to other 2 DOTS drafts about inter-domain DOTS use cases and mechanisms;=
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l1 level1 lfo2">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">2=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">In Section 1.2: For cla=
rity, I suggest to add a new terminology to specify what is the domain in O=
DTS scope. A domain can be a network domain, a SMB network, a DDoS protecti=
on provider network, etc;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">2=
.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">In Section 1.2, some mo=
dification should be made to the terminologies for DOTS client, DOTS server=
, Client signal and Server signal, as following:
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">1=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">DOTS client: &#8220;<i>=
..., as well as exchanging and updating other information with DOTS server =
or relay, such as mitigation scope, mitigation efficacy and mitigation stat=
us.</i>&#8221;;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">2=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">DOTS server: &#8220;<i>=
..., as well as exchanging and updating other information with DOTS client =
or relay, such as mitigation scope, mitigation efficacy and mitigation stat=
us.</i>&#8221;;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">3=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Client signal: &#8220;<=
i>... Other signals include the messages for updating information with DOTS=
 server or relay, such as mitigation scope and mitigation efficacy.</i>&#82=
21;;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:36.0pt;text-indent:-18.0=
pt;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">4=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Server signal: &#8220;<=
i>... The other server signal is mitigation termination notification .</i>&=
#8221;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">3=
.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">A series of requirement=
s for the DOTS relay are still missed in current draft. We need to consider=
 how to incorporate them;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">4=
.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">In Section 2.3, suggest=
 to add the requirement description for the DOTS client&#8217;s registratio=
n and registration cancelling messages, DOTS server&#8217;s registration re=
sponse and registration cancelling response message,
 which are conveyed over the data channel.<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">Thanks!<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">B.R.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Frank<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_C02846B1344F344EB4FAA6FA7AF481F12AF2FE92SZXEMA502MBSchi_--


From nobody Wed May 11 04:10:12 2016
Return-Path: <nteague@verisign.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E061212D992 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 04:10:10 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign-com.20150623.gappssmtp.com
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 Wm_WG92jHJeY for <dots@ietfa.amsl.com>; Wed, 11 May 2016 04:10:04 -0700 (PDT)
Received: from mail-oi0-x263.google.com (mail-oi0-x263.google.com [IPv6:2607:f8b0:4003:c06::263]) (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 D4A4912D993 for <dots@ietf.org>; Wed, 11 May 2016 04:10:03 -0700 (PDT)
Received: by mail-oi0-x263.google.com with SMTP id u67so3029180oia.1 for <dots@ietf.org>; Wed, 11 May 2016 04:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language:user-agent :content-id:content-transfer-encoding:mime-version; bh=mRGL8rUKJIhjMjXKe8KVaY5cFJrCkNLaBzqx93BaI64=; b=BvSRugWQ3GiRQCua6Fu/wAJ7KGWmDrToqRFaILqUdEGLiioVwv5qeG+jWVKu5ra7aK JBe/WuhN0MTFXF6WpEfrHGLRUG42MwXDwJc/gR/q3kKz8L67VA6wXxMpUQxXF+aiRevl K1r1D6NGex5100PA7oEfFRCJVa3tIjSZ6u8gi5pYVpkRC+/sYxy7YGryM3KuD94d2i1o ZtUYMMl15s+Roufku8E7nTQ2vAUlyvau0qnlMa8qsFOiTWwVMU3/HrHzyqHZZrUQ3n4A K6mTTOF/Se5JiG16yWjwqV0J0ZKEh+i4I0Lhra28rxjznHBmjx3RhKM/zHzKlpR3+YsF tCmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:user-agent:content-id:content-transfer-encoding :mime-version; bh=mRGL8rUKJIhjMjXKe8KVaY5cFJrCkNLaBzqx93BaI64=; b=VcTl2fOQ/BKiGYvgEjPiSv3/oDpWT+WcSTX8ZBKgnetRZJhpghkWoiISk4aYJ6yyZ7 /HCx7mEP6aIhdgUn/2xChf5lZmjLHha+ojxdVVc6IhsUKu1IHJw3mwe1A8oWenVzcr7E H45yqU71E0YqiQYcv9W14icvZ3D3PQexjjyfrXkFEz/UH3Up5MRTdRmhBF5Kt+TKIDec F9FyeBWLcou6Hs5v8A6Srgo/aB8aYKlwMlPPppj25fYiJN/35uJy2ejS/ZDXuBitizcU 04x14p7kM8HeI1SMVFItOw7LN3elv31C5fpy/R0N0Nl7FdzAaA+ihOzhuyyA7WQw08Uu USJg==
X-Gm-Message-State: AOPr4FWbNgWuTEatW0Yf18BexAs/oRmmrRQ1Uth97iao6N/d7PtB3SfqDnSIggzH2xMrd2GzAdt4dlYxpjdT3xk4cWIPMdu9
X-Received: by 10.233.239.193 with SMTP id d184mr2731572qkg.122.1462965003132;  Wed, 11 May 2016 04:10:03 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id r134sm743166qke.10.2016.05.11.04.10.02 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 11 May 2016 04:10:03 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u4BBA1Yi003345 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 07:10:02 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 11 May 2016 07:10:01 -0400
From: "Teague, Nik" <nteague@verisign.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>, Andrew Mortensen <amortensen@arbor.net>, Robert Moskowitz <rgm-sec@htt-consult.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [Dots] Hi, some comments to DOTS requirements draft:
Thread-Index: AdGrXuf1w+vuVmiOSjSckzMJsciMJgAQKj2A
Date: Wed, 11 May 2016 11:10:01 +0000
Message-ID: <4D4A509F-9299-4609-912A-B9A6FC9532F4@verisign.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160212
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <97BB30477E19844C89D186A8D4E5AB77@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/8PkvSg-PZY-D6fmOrKU-_7-WfW8>
Cc: "dots@ietf.org" <dots@ietf.org>
Subject: Re: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 11:10:11 -0000

SGksDQoNCg0KDQpPbiAxMS8wNS8yMDE2IDA5OjI3LCAiRG90cyBvbiBiZWhhbGYgb2YgWGlhbGlh
bmcgKEZyYW5rKSIgPGRvdHMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgZnJhbmsueGlh
bGlhbmdAaHVhd2VpLmNvbT4gd3JvdGU6DQoNCj4xLiAgICAgICBJbnRlci1kb21haW4gY29vcmRp
bmF0ZWQgRERvUyBwcm90ZWN0aW9uIGlzIHRoZSBpbXBvcnRhbnQgcGFydCBvZiB0aGUgd2hvbGUg
RE9UUyBzb2x1dGlvbiwgYnV0IGl0IHNlZW1zIHRoYXQgY3VycmVudCBET1RTIHJlcXVpcmVtZW50
cyBkcmFmdCBkb2VzIG5vdCBpbmNsdWRlIGVub3VnaCBjb250ZW50cyBhYm91dCB0aGlzIHBhcnQu
IEVzcGVjaWFsbHkgaW4gdGhlIGZvbGxvd2luZyBzZWN0aW9uczoNCj4xKSAgICAgICBJbiBTZWN0
aW9uIDEuMTogaXQgb25seSBtZW50aW9ucyB0aGUgcHJvYmxlbSBvZiBtaXNzaW5nIHRoZSBzdGFu
ZGFyZCBpbnRlcmZhY2UgYmV0d2VlbiBjbGllbnRzIGFuZCBkZG9zIHByb3RlY3Rpb24gcHJvdmlk
ZXJzIChDMlAgc2NlbmFyaW8pLCB0b3RhbGx5IG1pc3NlcyBkZXNjcmliaW5nIHRoZSBzYW1lIHBy
b2JsZW0gZm9yIHRoZSBwcm92aWRlcnMgdG8gcHJvdmlkZXJzIChQMlApIHNjZW5hcmlvLiBDb3Jy
ZXNwb25kaW5nbHksIHRoaXMgc2VjdGlvbiBvbmx5IGVtcGhhc2lzIHRoZSBiZW5lZml0cyBvZiBy
ZWFsLXRpbWUgcmVzcG9uc2UgZm9yIHRoZSBDMlAgc2NlbmFyaW8sIGRvIG5vdCBtZW50aW9uIG90
aGVyIGJlbmVmaXRzIG9mIHJlc291cmNlL2NhcGFiaWxpdGllcyBzaGFyaW5nLCB3b3JsZHdpZGUg
b3B0aW1pemVkIG1pdGlnYXRpb24gYW5kIG5lYXIgc291cmNlIG1pdGlnYXRpb24gZm9yIHRoZSBQ
MlAgc2NlbmFyaW8uIFBsZWFzZSBpbmNsdWRlIHRoaXMga2luZCBvZiBjb250ZW50cyBpbiBsYXRl
ciB2ZXJzaW9uLCBhbmQgeW91IGNhbiByZWZlcmVuY2UgdG8gb3RoZXIgMiBET1RTIGRyYWZ0cyBh
Ym91dCBpbnRlci1kb21haW4gRE9UUyB1c2UgY2FzZXMgYW5kIG1lY2hhbmlzbXM7DQoNCkkgdGhp
bmsgaXRzIGltcGxpZWQgYnV0IG1heWJlIG5vdCBkZXNjcmliZWQgZXhwbGljaXRseSAtIGltaG8g
YSDigJhwMnDigJkgaGFzIGxpdHRsZSByZWFsIGRpc3RpbmN0aW9uIGZyb20gJ2MycCcuICBPbmUg
c2lkZSBpcyBhbHdheXMgYSBjbGllbnQgYW5kIHRoZSBvdGhlciBhIHNlcnZlciBmb3IgYSBnaXZl
biBzZXQgb2YgY3VzdG9tZXIgYXNzZXRzIGFuZCBwcm90ZWN0aW9uL21pdGlnYXRpb24gcmVxdWVz
dHMuDQoNCknigJltIG5vdCBzdXJlIGl0cyB1cCB0byB0aGUgcmVxdWlyZW1lbnRzIGRyYWZ0IHRv
IGNhbGwgb3V0IGJlbmVmaXRzL3Byb3MvY29ucyBvZiBhbnkgZ2l2ZW4gYXBwbGljYXRpb24gb3Ig
Zm9yIHRoYXQgbWF0dGVyIGdpdmUgd2VpZ2h0IHRvIGFueSBvbmUgZGVwbG95bWVudCB0eXBlIGJ1
dCByYXRoZXIgdGhhdCBzaG91bGQgYmUgYSBmdW5jdGlvbiBvZiB0aGUgcHJpbWFyeSB1c2UgY2Fz
ZSBkcmFmdCAob3IgaXRzIHNhdGVsbGl0ZXMpLiAgDQoNCldlIHNob3VsZCBiZSBhYmxlIHRvIG1h
dGNoIHRoZSByZXF1aXJlbWVudHMgdG8gdGhlIHZhcmlvdXMgdXNlIGNhc2VzIGFuZCB0aGVuIGlu
IHR1cm4gbWFwIHRoZSBwcm90b2NvbCBhY2NvcmRpbmdseS4gIEFuZCB0aGF04oCZcyBwcm9iYWJs
eSBhIGdvb2QgZXhlcmNpc2UgZm9yIHVzIHRvIHVuZGVydGFrZSBwcmlvciB0byBCZXJsaW4uDQoN
ClRoZSBzdWdnZXN0aW9ucyBmb3IgMS4yIHdpdGggbWl0aWdhdGlvbiBzY29wZS9lZmZpY2FjeS9z
dGF0dXMgY2FsbGVkIG91dOKApiBJIHdvdWxkIGxpa2UgdG8gc2VlIGZ1cnRoZXIgZWxhYm9yYXRp
b24gb24gdGhlc2UgdGVybXMgaW4gdGhlc2UgY29udGV4dCBiZWZvcmUgc3VnZ2VzdGluZyB0aGV5
IGdvIG5lYXIgdGhlIHJlcXVpcmVtZW50cy4gIEZyb20gbXkgcGVyc3BlY3RpdmUgb24gdGhlIHBy
b3ZpZGVyIHNpZGUgSSBkb27igJl0IGNhcmUgd2hhdCB0aGUgY2xpZW50IGRpZOKApiBqdXN0IHRo
YXQgdGhleSBhc2tlZCBmb3IgcHJvdGVjdGlvbi4gDQoNClRoYW5rcywNCg0KLU5paw0K


From nobody Wed May 11 04:32:35 2016
Return-Path: <rdobbins@arbor.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C974D12DA08 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 04:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arbor.net
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 9bwWyAzYtQeW for <dots@ietfa.amsl.com>; Wed, 11 May 2016 04:32:32 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::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 3F51A12DA18 for <dots@ietf.org>; Wed, 11 May 2016 04:31:13 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id y69so17633846pfb.1 for <dots@ietf.org>; Wed, 11 May 2016 04:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arbor.net; s=m0; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=9jXVX0ms9RSUupNGDrNhDnp45YGbpi2gTnq5EY7XRYk=; b=HbvGlptP/EZkvY8L088+OoaRFM4X/rXBJAoqZOgx3jkTAzHc+FZVNNZU+bPFXMHfyF m8GM6kQEyVJlpQCT7Oevb0LB77eK7HkKa8MVN70xMIYCAlNkXNb9hN3d/1klVrFSPL8+ oQIOFoSUKlBy2to6e+a3q02YjQQau1/9CH7mw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=9jXVX0ms9RSUupNGDrNhDnp45YGbpi2gTnq5EY7XRYk=; b=KCnHsLLJxtCH+h1ZVbgl9cuEp4hiRSo2oXg4UIEy+SpTMJd77ObmYzLLdCpOxKb4lH 5y8hU37oCe0vDUy7GCtachLdLFFyRxXnMxEprQz8RXGaHbpXQKbi1WtKlchqf+SfVbNN Ok79pw6Kdftyf6hJbGAPSYKxFhUMQ6uWB+h86cJh1HcgZv7ECH8ntImvgRG23a5sNAGI SJKrEtWsM+pH1O4JrJ8RVsjm3ox95eMf1hVpcYCsBDzeFucebjAR4U13QSAw4UJzVGU6 uSco8cVr4xbIG5UGxJKp0Y+oYb6ft4uOhu26lSc0X7lEgyIAiHtlKBqplcjywOdRB/8+ cLsQ==
X-Gm-Message-State: AOPr4FX4mHUqpHXN8Vo5MCTh7r7jb1CuxO9YokgJ6pXaAXJstdHSGtUI15YNDdQ74u4XN2xq
X-Received: by 10.98.19.131 with SMTP id 3mr4066061pft.17.1462966272823; Wed, 11 May 2016 04:31:12 -0700 (PDT)
Received: from [172.19.254.114] (202-176-81-112.static.asianet.co.th. [202.176.81.112]) by smtp.gmail.com with ESMTPSA id 133sm11537606pfw.35.2016.05.11.04.31.09 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 04:31:11 -0700 (PDT)
From: "Roland Dobbins" <rdobbins@arbor.net>
To: "Teague, Nik" <nteague@verisign.com>
Date: Wed, 11 May 2016 18:31:07 +0700
Message-ID: <DE3A5F81-C964-4B28-809B-857429334EEC@arbor.net>
In-Reply-To: <4D4A509F-9299-4609-912A-B9A6FC9532F4@verisign.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com> <4D4A509F-9299-4609-912A-B9A6FC9532F4@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/57DVemAes6VF1OnloFpMHf-e-TA>
Cc: Andrew Mortensen <amortensen@arbor.net>, Xialiang <frank.xialiang@huawei.com>, "dots@ietf.org" <dots@ietf.org>, Tirumaleswar Reddy <tireddy@cisco.com>, Robert Moskowitz <rgm-sec@htt-consult.com>
Subject: Re: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 11:32:34 -0000

On 11 May 2016, at 18:10, Teague, Nik wrote:

> I would like to see further elaboration on these terms in these 
> context before suggesting they go near the requirements.  From my 
> perspective on the provider side I don’t care what the client did… 
> just that they asked for protection.

Concur 100% - we'll take a stab at it.

-----------------------------------
Roland Dobbins <rdobbins@arbor.net>


From nobody Wed May 11 05:26:12 2016
Return-Path: <amortensen@arbor.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 593D012DA80 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 05:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arbor.net
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 SH_La2os0xNA for <dots@ietfa.amsl.com>; Wed, 11 May 2016 05:26:08 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 4465C12D67E for <dots@ietf.org>; Wed, 11 May 2016 05:26:08 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id f89so51574061ioi.0 for <dots@ietf.org>; Wed, 11 May 2016 05:26:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arbor.net; s=m0; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=jJMLmpW4WnnlZ0ckz8eDpyT3L26qqHTuL7nPPV9//uk=; b=e5jUL5GcuUFpmUP1eVquARghb1ASQlPuMzaBxsde5SS0+XHYxR7suWZo+1qGMtENOU 5rzzwWMFkSB3i+EHYDAlmQkZ9G9eMdKOADs+YoQsCEICyMhqKjCPuBazOZyx6EuRSD0t rC4DRodvy6lRp+gBZDgjC0K/noNrme7AiZQXQ=
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; bh=jJMLmpW4WnnlZ0ckz8eDpyT3L26qqHTuL7nPPV9//uk=; b=UM3Wd8Q6byCIRj3KUetEHufSfnz0R2sYRaMwRLv9wtXzMxufIA91NJKGiqTSOT14tR 7C/eY4LMlTDV6U0NIzTOym2cyG2UmJPSFoc1NNuRxmwRTFGEY4DTnm1Ykn8UUM7GCmld kDTNbTb/lAyX8Df315QJ51o1kkbBD9SmoFaPRXNJB73ZfK1QCIxP2oTbYIodLkp1LgFx hth8wj4FFxaMQu3rTj02Xq9uA/F/ZqJteGBwbBAtH3NddjL9cA3VMFtlJO9Q1v9/Y8JH C6QIbIILS3q9bGJhqZxMVP9fs3zu7TSVCJu9MPwf2UQiM3X99alIWQcTcCtqWrJl7mRm b9mQ==
X-Gm-Message-State: AOPr4FUZW7/VDw6sw5UeMnu+G4tV2hIXZjVnz577rPTJ2rsWOs7lBvJcHvwPSu3scW3qBNV4JfrTx+lSsCC3zXMJ
MIME-Version: 1.0
X-Received: by 10.36.217.10 with SMTP id p10mr4199477itg.23.1462969567553; Wed, 11 May 2016 05:26:07 -0700 (PDT)
Received: by 10.64.107.193 with HTTP; Wed, 11 May 2016 05:26:07 -0700 (PDT)
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com>
Date: Wed, 11 May 2016 08:26:07 -0400
Message-ID: <CALOivRA8c1qofYBvXq7yPbyB8hocMnVP46nPhotMmKK8C=JMBw@mail.gmail.com>
From: "Mortensen, Andrew" <amortensen@arbor.net>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>
Content-Type: multipart/alternative; boundary=001a1149a47e645e3f05329025f0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/8MCIU4vC_SdHE_EOuC0OhwAxlA4>
Cc: "dots@ietf.org" <dots@ietf.org>, "Tirumaleswar Reddy \(tireddy\)" <tireddy@cisco.com>, Robert Moskowitz <rgm-sec@htt-consult.com>
Subject: Re: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 12:26:11 -0000

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

Thanks! See my quick comment below.

On Wednesday, May 11, 2016, Xialiang (Frank) <frank.xialiang@huawei.com>
wrote:

> Hi authors,
>
> By reviewing this draft recently, I have the following new comments:
>
> 3.       A series of requirements for the DOTS relay are still missed in
> current draft. We need to consider how to incorporate them;
>
>
During the meeting I heard a call to get rid of DOTS relays, given the
operational complexity. Relayed signaling would remain a concept, but would
look more or less like what's currently called Recursive signaling in the
architecture draft. (I recall you pointing out that the Mitigator wouldn't
have to be the element recursing the signal in that case, and the DOTS
server could do it instead.)

andrew

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

Thanks! See my quick<span></span> comment below.<br><br>On Wednesday, May 1=
1, 2016, Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com">=
frank.xialiang@huawei.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi authors,<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">By reviewing this draft recentl=
y, I have the following new comments:<u></u><u></u></span></p>
<p style=3D"margin-left:18.0pt"><span lang=3D"EN-US">3.<span style=3D"font-=
size:7pt;line-height:normal;font-family:&#39;Times New Roman&#39;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u><span lang=3D"EN-US">A series of requirements for the =
DOTS relay are still missed in current draft. We need to consider how to in=
corporate them;</span></p><p style=3D"margin-left:18.0pt"></p></div></div><=
/blockquote><div><br></div><div>During the meeting I heard a call to get ri=
d of DOTS relays, given the operational complexity. Relayed signaling would=
 remain a concept, but would look more or less like what&#39;s currently=C2=
=A0called Recursive signaling=C2=A0in the architecture draft. (I=C2=A0recal=
l you pointing out that the Mitigator wouldn&#39;t have to be the element r=
ecursing the signal in that case, and the DOTS server could do it instead.)=
</div><div><br></div><div>andrew</div>

--001a1149a47e645e3f05329025f0--


From nobody Wed May 11 05:32:10 2016
Return-Path: <rdobbins@arbor.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207B912DA95 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 05:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arbor.net
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 oKi6lr-q1mXP for <dots@ietfa.amsl.com>; Wed, 11 May 2016 05:32:07 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (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 B52B512DAB7 for <dots@ietf.org>; Wed, 11 May 2016 05:31:33 -0700 (PDT)
Received: by mail-pa0-x235.google.com with SMTP id xk12so17619853pac.0 for <dots@ietf.org>; Wed, 11 May 2016 05:31:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arbor.net; s=m0; h=from:to:subject:date:message-id:in-reply-to:references:mime-version; bh=HbLtPkv2ocpiFJXRiyqiv7cgqEaxjsl9Z8q7Q+4wYds=; b=D7OegOatNj1W2ow/1lO98+HUr5ZJ/mrt4354cd9PTos0arZ6xWNp+5yv+YeJKEJzsh hhjagqe1Zz/7Afgs4bSU8ihq2myQhzJI2H9cSQ42rtpi+o5+DOpe1nnUIqgiQWDgryR/ RpxBdgD9lRqoaJo4kjzCFQLxz8J+psBDdKaP0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=HbLtPkv2ocpiFJXRiyqiv7cgqEaxjsl9Z8q7Q+4wYds=; b=jGFW2lusX0jQFSwT3IAw2nIvH3IIvUB5dyYxasYcERqYjCLdlkxoTTfKalmZDs3/dV TNHyQxi7Mjdfpz2ZmQU10VuOh2GGtGocb0UdihoVQ52LKY+u7MDwEX/NZi3KEEuJ/sYJ v+UPn9tupWCoYX4mSIxiMIrQbNOiGeCYge+gzFwLopjc418+cMM0wTyZTL2RxGxQmYAh 55HruPO3Awru4sNOIB9EMWRgGhIykZCd2U+2/trctisdUDFivA9bGj4QAtDKYT+l0pSM oI9Ezo6Cd88uingi1y6LvOympfJEFQ8owq7GNtV4yLtxiclzq6rPR+gbu93daGFAojAu z/Fg==
X-Gm-Message-State: AOPr4FVNo5yg+5uqx8xJwuVEC4RD1TOcpr2FbaC4v2FGoLMg6UJ+PuAFEysoCVxR7UFWkLvy
X-Received: by 10.66.160.133 with SMTP id xk5mr4468769pab.71.1462969893282; Wed, 11 May 2016 05:31:33 -0700 (PDT)
Received: from [172.19.254.114] (202-176-81-112.static.asianet.co.th. [202.176.81.112]) by smtp.gmail.com with ESMTPSA id 63sm11975786pff.43.2016.05.11.05.31.31 for <dots@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 05:31:32 -0700 (PDT)
From: "Roland Dobbins" <rdobbins@arbor.net>
To: "dots@ietf.org" <dots@ietf.org>
Date: Wed, 11 May 2016 19:31:30 +0700
Message-ID: <C0D8F3DE-3DA1-4042-A8A3-48ED8A3304FA@arbor.net>
In-Reply-To: <CALOivRA8c1qofYBvXq7yPbyB8hocMnVP46nPhotMmKK8C=JMBw@mail.gmail.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com> <CALOivRA8c1qofYBvXq7yPbyB8hocMnVP46nPhotMmKK8C=JMBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/jgiacyuylGNtosUdMt86Q4DcAlQ>
Subject: Re: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 12:32:09 -0000

On 11 May 2016, at 19:26, Mortensen, Andrew wrote:

> Relayed signaling would remain a concept, but would
> look more or less like what's currently called Recursive signaling in 
> the
> architecture draft.

Essentially, a server and client grafted back-to-back.  So, we'll have a 
relay function, but it won't be a distinct node type for crypto/auth 
purposes.

I believe that's what Frank was alluding to - that we need to spell this 
out.
-----------------------------------
Roland Dobbins <rdobbins@arbor.net>


From nobody Wed May 11 06:45:08 2016
Return-Path: <amortensen@arbor.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2C8A12D788 for <dots@ietfa.amsl.com>; Wed, 11 May 2016 06:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arbor.net
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 lHn5FaWzzyyK for <dots@ietfa.amsl.com>; Wed, 11 May 2016 06:45:04 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 C677C12D170 for <dots@ietf.org>; Wed, 11 May 2016 06:45:04 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id 190so54557476iow.1 for <dots@ietf.org>; Wed, 11 May 2016 06:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arbor.net; s=m0; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gCqL/HTe/2thvgeX9crTf4Y9tsPl+6Ftfp3iqVDMWvU=; b=ZD+qqGpz10eNaO4X9jF8Uj9XehysM4NZom36btWxF3+3mTlSJDSNQzwv2GTSY9dfqn zS5xA7mVKap6NinKjh8GOmR7HcA6K84a8o4NuXVOY2OKHfvtVboU/nPA+24zM8j9H59G OS1keVFQrip8p4YaQdFKn7GV/It9tJi46ZjHw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gCqL/HTe/2thvgeX9crTf4Y9tsPl+6Ftfp3iqVDMWvU=; b=ZMw6b1OeikTg5rCP5ydI6e7kLzYOVjtcnFe1OpUZmSY80J7M5CNznf/Q1MJLY0Nvs3 D1/kxIcD4A6/SnIvuEIhwT8+UFW2q/9UCJQ1VyGQ4JMgCcFffDQoDVliSptIpCK/P/wZ wOVLFhQvOKP1gjjrFATuysfSL47jKDOxfqUKbA7hVaPHnWtwAIHxDHcJDM6/mjvwC3Xl ilPrMDdf3yiTAfuV4ANZ+Sd8p82dZOtHnTiXGs79sa5+CETc1zPpo+DU8/2kjsMsYCcb 2e3hwIrZA/Jsr6C5YhcKCCKS3NfX7TdKlvW3EIyyYcfQHJWjPARCfRC394KzZZVB3Ke9 tQ5g==
X-Gm-Message-State: AOPr4FWtARDX7qP2rIylRZikjm3XHCHskx+q2pyzcOUZE8/unKI+Azqp2eIgG1MbThOFWNad
X-Received: by 10.107.6.28 with SMTP id 28mr3469178iog.18.1462974304109; Wed, 11 May 2016 06:45:04 -0700 (PDT)
Received: from ?IPv6:2620:11e:1000:10:91bb:aac1:6be:a834? ([2620:11e:1000:10:91bb:aac1:6be:a834]) by smtp.gmail.com with ESMTPSA id u187sm3002345iod.3.2016.05.11.06.45.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 06:45:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Andrew Mortensen <amortensen@arbor.net>
In-Reply-To: <C0D8F3DE-3DA1-4042-A8A3-48ED8A3304FA@arbor.net>
Date: Wed, 11 May 2016 09:45:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0569970E-7437-491B-B939-A51CF149A737@arbor.net>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com> <CALOivRA8c1qofYBvXq7yPbyB8hocMnVP46nPhotMmKK8C=JMBw@mail.gmail.com> <C0D8F3DE-3DA1-4042-A8A3-48ED8A3304FA@arbor.net>
To: Roland Dobbins <rdobbins@arbor.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/CBxKvo5HUpfbbti5tNNA_Y2E3_I>
Cc: "dots@ietf.org" <dots@ietf.org>
Subject: Re: [Dots] Hi, some comments to DOTS requirements draft:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 13:45:07 -0000

> On May 11, 2016, at 8:31 AM, Roland Dobbins <rdobbins@arbor.net> =
wrote:
>=20
> On 11 May 2016, at 19:26, Mortensen, Andrew wrote:
>=20
>> Relayed signaling would remain a concept, but would
>> look more or less like what's currently called Recursive signaling in =
the
>> architecture draft.
>=20
> Essentially, a server and client grafted back-to-back.  So, we'll have =
a relay function, but it won't be a distinct node type for crypto/auth =
purposes.
>=20
> I believe that's what Frank was alluding to - that we need to spell =
this out.

Agreed.=


From nobody Wed May 11 18:54:26 2016
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF4512D17F for <dots@ietfa.amsl.com>; Wed, 11 May 2016 18:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level: 
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 AuTNpBTJjF4C for <dots@ietfa.amsl.com>; Wed, 11 May 2016 18:54:22 -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 0C67F12B02B for <dots@ietf.org>; Wed, 11 May 2016 18:54:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id COM44404; Thu, 12 May 2016 01:54:19 +0000 (GMT)
Received: from SZXEMA419-HUB.china.huawei.com (10.82.72.37) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 12 May 2016 02:54:16 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.36]) by SZXEMA419-HUB.china.huawei.com ([10.82.72.37]) with mapi id 14.03.0235.001; Thu, 12 May 2016 09:54:10 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "Teague, Nik" <nteague@verisign.com>, Andrew Mortensen <amortensen@arbor.net>, Robert Moskowitz <rgm-sec@htt-consult.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [Dots] Hi, some comments to DOTS requirements draft:
Thread-Index: AQHRq3Wvx6tbNLNr0EujY+sz2rzPc5+0hscg
Date: Thu, 12 May 2016 01:54:10 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12AF3001F@SZXEMA502-MBS.china.huawei.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com> <4D4A509F-9299-4609-912A-B9A6FC9532F4@verisign.com>
In-Reply-To: <4D4A509F-9299-4609-912A-B9A6FC9532F4@verisign.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.91]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5733E24C.0082, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.36, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 162bd604dbc2a277e8f151bd12f2d8e3
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/NmEAk7O_xI0pUCktIyHRu-bloNw>
Cc: "dots@ietf.org" <dots@ietf.org>
Subject: [Dots] =?utf-8?b?562U5aSNOiAgSGksIHNvbWUgY29tbWVudHMgdG8gRE9UUyBy?= =?utf-8?q?equirements_draft=3A?=
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 01:54:25 -0000

SGkgTmlrLA0KUGxlYXNlIHNlZSBteSBjb21tZW50cyBpbmxpbmU6DQoNCi0tLS0t6YKu5Lu25Y6f
5Lu2LS0tLS0NCuWPkeS7tuS6ujogVGVhZ3VlLCBOaWsgW21haWx0bzpudGVhZ3VlQHZlcmlzaWdu
LmNvbV0gDQrlj5HpgIHml7bpl7Q6IDIwMTblubQ15pyIMTHml6UgMTk6MTANCuaUtuS7tuS6ujog
WGlhbGlhbmcgKEZyYW5rKTsgQW5kcmV3IE1vcnRlbnNlbjsgUm9iZXJ0IE1vc2tvd2l0ejsgVGly
dW1hbGVzd2FyIFJlZGR5ICh0aXJlZGR5KQ0K5oqE6YCBOiBkb3RzQGlldGYub3JnDQrkuLvpopg6
IFJlOiBbRG90c10gSGksIHNvbWUgY29tbWVudHMgdG8gRE9UUyByZXF1aXJlbWVudHMgZHJhZnQ6
DQoNCkhpLA0KDQoNCg0KT24gMTEvMDUvMjAxNiAwOToyNywgIkRvdHMgb24gYmVoYWxmIG9mIFhp
YWxpYW5nIChGcmFuaykiIDxkb3RzLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGZyYW5r
LnhpYWxpYW5nQGh1YXdlaS5jb20+IHdyb3RlOg0KDQo+MS4gICAgICAgSW50ZXItZG9tYWluIGNv
b3JkaW5hdGVkIEREb1MgcHJvdGVjdGlvbiBpcyB0aGUgaW1wb3J0YW50IHBhcnQgb2YgdGhlIHdo
b2xlIERPVFMgc29sdXRpb24sIGJ1dCBpdCBzZWVtcyB0aGF0IGN1cnJlbnQgRE9UUyByZXF1aXJl
bWVudHMgZHJhZnQgZG9lcyBub3QgaW5jbHVkZSBlbm91Z2ggY29udGVudHMgYWJvdXQgdGhpcyBw
YXJ0LiBFc3BlY2lhbGx5IGluIHRoZSBmb2xsb3dpbmcgc2VjdGlvbnM6DQo+MSkgICAgICAgSW4g
U2VjdGlvbiAxLjE6IGl0IG9ubHkgbWVudGlvbnMgdGhlIHByb2JsZW0gb2YgbWlzc2luZyB0aGUg
c3RhbmRhcmQgaW50ZXJmYWNlIGJldHdlZW4gY2xpZW50cyBhbmQgZGRvcyBwcm90ZWN0aW9uIHBy
b3ZpZGVycyAoQzJQIHNjZW5hcmlvKSwgdG90YWxseSBtaXNzZXMgZGVzY3JpYmluZyB0aGUgc2Ft
ZSBwcm9ibGVtIGZvciB0aGUgcHJvdmlkZXJzIHRvIHByb3ZpZGVycyAoUDJQKSBzY2VuYXJpby4g
Q29ycmVzcG9uZGluZ2x5LCB0aGlzIHNlY3Rpb24gb25seSBlbXBoYXNpcyB0aGUgYmVuZWZpdHMg
b2YgcmVhbC10aW1lIHJlc3BvbnNlIGZvciB0aGUgQzJQIHNjZW5hcmlvLCBkbyBub3QgbWVudGlv
biBvdGhlciBiZW5lZml0cyBvZiByZXNvdXJjZS9jYXBhYmlsaXRpZXMgc2hhcmluZywgd29ybGR3
aWRlIG9wdGltaXplZCBtaXRpZ2F0aW9uIGFuZCBuZWFyIHNvdXJjZSBtaXRpZ2F0aW9uIGZvciB0
aGUgUDJQIHNjZW5hcmlvLiBQbGVhc2UgaW5jbHVkZSB0aGlzIGtpbmQgb2YgY29udGVudHMgaW4g
bGF0ZXIgdmVyc2lvbiwgYW5kIHlvdSBjYW4gcmVmZXJlbmNlIHRvIG90aGVyIDIgRE9UUyBkcmFm
dHMgYWJvdXQgaW50ZXItZG9tYWluIERPVFMgdXNlIGNhc2VzIGFuZCBtZWNoYW5pc21zOw0KDQpJ
IHRoaW5rIGl0cyBpbXBsaWVkIGJ1dCBtYXliZSBub3QgZGVzY3JpYmVkIGV4cGxpY2l0bHkgLSBp
bWhvIGEg4oCYcDJw4oCZIGhhcyBsaXR0bGUgcmVhbCBkaXN0aW5jdGlvbiBmcm9tICdjMnAnLiAg
T25lIHNpZGUgaXMgYWx3YXlzIGEgY2xpZW50IGFuZCB0aGUgb3RoZXIgYSBzZXJ2ZXIgZm9yIGEg
Z2l2ZW4gc2V0IG9mIGN1c3RvbWVyIGFzc2V0cyBhbmQgcHJvdGVjdGlvbi9taXRpZ2F0aW9uIHJl
cXVlc3RzLg0KW0ZyYW5rXTogVGVjaG5pY2FsbHksIHlvdSBhcmUgcmlnaHQgdGhhdCBpdCdzIGlt
cGxpZWQuIEkganVzdCB0aGluayBtb3JlIGNvbXByZWhlbnNpdmUgZGVzY3JpcHRpb25zIG9mIERP
VFMgc29sdXRpb24ncyBhcHBsaWNhdGlvbnMgYW5kIHRoZWlyIHZhbHVlcyBhcmUgYmV0dGVyIGlu
IHRoZSBpbnRyb2R1Y3Rpb24gcGFydCwgZXNwZWNpYWxseSBmb3IgdGhlIHZlcnkgaW1wb3J0YW50
IHVzZSBjYXNlcy4gQnV0IGl0J3MganVzdCBteSBwZXJzb25hbCBzdWdnZXN0aW9uIGFuZCBJIGRv
bid0IGhhdmUgc3Ryb25nIG9waW5pb25zfn4NCg0KSeKAmW0gbm90IHN1cmUgaXRzIHVwIHRvIHRo
ZSByZXF1aXJlbWVudHMgZHJhZnQgdG8gY2FsbCBvdXQgYmVuZWZpdHMvcHJvcy9jb25zIG9mIGFu
eSBnaXZlbiBhcHBsaWNhdGlvbiBvciBmb3IgdGhhdCBtYXR0ZXIgZ2l2ZSB3ZWlnaHQgdG8gYW55
IG9uZSBkZXBsb3ltZW50IHR5cGUgYnV0IHJhdGhlciB0aGF0IHNob3VsZCBiZSBhIGZ1bmN0aW9u
IG9mIHRoZSBwcmltYXJ5IHVzZSBjYXNlIGRyYWZ0IChvciBpdHMgc2F0ZWxsaXRlcykuICANCg0K
V2Ugc2hvdWxkIGJlIGFibGUgdG8gbWF0Y2ggdGhlIHJlcXVpcmVtZW50cyB0byB0aGUgdmFyaW91
cyB1c2UgY2FzZXMgYW5kIHRoZW4gaW4gdHVybiBtYXAgdGhlIHByb3RvY29sIGFjY29yZGluZ2x5
LiAgQW5kIHRoYXTigJlzIHByb2JhYmx5IGEgZ29vZCBleGVyY2lzZSBmb3IgdXMgdG8gdW5kZXJ0
YWtlIHByaW9yIHRvIEJlcmxpbi4NCltGcmFua106IHN1cmUuDQoNClRoZSBzdWdnZXN0aW9ucyBm
b3IgMS4yIHdpdGggbWl0aWdhdGlvbiBzY29wZS9lZmZpY2FjeS9zdGF0dXMgY2FsbGVkIG91dOKA
piBJIHdvdWxkIGxpa2UgdG8gc2VlIGZ1cnRoZXIgZWxhYm9yYXRpb24gb24gdGhlc2UgdGVybXMg
aW4gdGhlc2UgY29udGV4dCBiZWZvcmUgc3VnZ2VzdGluZyB0aGV5IGdvIG5lYXIgdGhlIHJlcXVp
cmVtZW50cy4gIEZyb20gbXkgcGVyc3BlY3RpdmUgb24gdGhlIHByb3ZpZGVyIHNpZGUgSSBkb27i
gJl0IGNhcmUgd2hhdCB0aGUgY2xpZW50IGRpZOKApiBqdXN0IHRoYXQgdGhleSBhc2tlZCBmb3Ig
cHJvdGVjdGlvbi4gDQpbRnJhbmtdOiBvaywgSSBhZ3JlZS4NCg0KQi5SLg0KRnJhbmsNCg0KVGhh
bmtzLA0KDQotTmlrDQo=


From nobody Wed May 11 19:01:59 2016
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D3712B05D for <dots@ietfa.amsl.com>; Wed, 11 May 2016 19:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level: 
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 A2iG2oePMn3p for <dots@ietfa.amsl.com>; Wed, 11 May 2016 19:01:57 -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 388561200A0 for <dots@ietf.org>; Wed, 11 May 2016 19:01:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id COM45190; Thu, 12 May 2016 02:01:54 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 12 May 2016 03:01:51 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.36]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0235.001; Thu, 12 May 2016 10:01:44 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Roland Dobbins <rdobbins@arbor.net>, Andrew Mortensen <amortensen@arbor.net>
Thread-Topic: [Dots] Hi, some comments to DOTS requirements draft:
Thread-Index: AQHRq4BOvGrVnTs3UkWMWbqfyf2llZ+zJPkAgAFnQEA=
Date: Thu, 12 May 2016 02:01:44 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12AF30032@SZXEMA502-MBS.china.huawei.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12AF2FE92@SZXEMA502-MBS.china.huawei.com> <CALOivRA8c1qofYBvXq7yPbyB8hocMnVP46nPhotMmKK8C=JMBw@mail.gmail.com> <C0D8F3DE-3DA1-4042-A8A3-48ED8A3304FA@arbor.net>
In-Reply-To: <C0D8F3DE-3DA1-4042-A8A3-48ED8A3304FA@arbor.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.43.91]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.5733E412.0164, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.36, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b45de212d8f9565f0e7c7a4f6f3901f1
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/rIxl5rLRFmKCGUJKBnD7HS18Uo0>
Cc: "dots@ietf.org" <dots@ietf.org>
Subject: [Dots] =?gb2312?b?tPC4tDogIEhpLCBzb21lIGNvbW1lbnRzIHRvIERPVFMg?= =?gb2312?b?cmVxdWlyZW1lbnRzIGRyYWZ0Og==?=
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 02:01:58 -0000

SGkgUm9sYW5kIGFuZCBBbmRyZXcsDQpUaGFua3MgZm9yIGNsYXJpZmljYXRpb24gYW5kIGNvbnNp
ZGVyYXRpb24uDQoNCkIuUi4NCkZyYW5rDQoNCi0tLS0t08q8/tStvP4tLS0tLQ0Kt6K8/sjLOiBE
b3RzIFttYWlsdG86ZG90cy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIFJvbGFuZCBEb2JiaW5zDQq3
osvNyrG85DogMjAxNsTqNdTCMTHI1SAyMDozMg0KytW8/sjLOiBkb3RzQGlldGYub3JnDQrW98zi
OiBSZTogW0RvdHNdIEhpLCBzb21lIGNvbW1lbnRzIHRvIERPVFMgcmVxdWlyZW1lbnRzIGRyYWZ0
Og0KDQpPbiAxMSBNYXkgMjAxNiwgYXQgMTk6MjYsIE1vcnRlbnNlbiwgQW5kcmV3IHdyb3RlOg0K
DQo+IFJlbGF5ZWQgc2lnbmFsaW5nIHdvdWxkIHJlbWFpbiBhIGNvbmNlcHQsIGJ1dCB3b3VsZCBs
b29rIG1vcmUgb3IgbGVzcyANCj4gbGlrZSB3aGF0J3MgY3VycmVudGx5IGNhbGxlZCBSZWN1cnNp
dmUgc2lnbmFsaW5nIGluIHRoZSBhcmNoaXRlY3R1cmUgDQo+IGRyYWZ0Lg0KDQpFc3NlbnRpYWxs
eSwgYSBzZXJ2ZXIgYW5kIGNsaWVudCBncmFmdGVkIGJhY2stdG8tYmFjay4gIFNvLCB3ZSdsbCBo
YXZlIGEgcmVsYXkgZnVuY3Rpb24sIGJ1dCBpdCB3b24ndCBiZSBhIGRpc3RpbmN0IG5vZGUgdHlw
ZSBmb3IgY3J5cHRvL2F1dGggcHVycG9zZXMuDQoNCkkgYmVsaWV2ZSB0aGF0J3Mgd2hhdCBGcmFu
ayB3YXMgYWxsdWRpbmcgdG8gLSB0aGF0IHdlIG5lZWQgdG8gc3BlbGwgdGhpcyBvdXQuDQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KUm9sYW5kIERvYmJpbnMgPHJkb2JiaW5z
QGFyYm9yLm5ldD4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCkRvdHMgbWFpbGluZyBsaXN0DQpEb3RzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RvdHMNCg==


From nobody Tue May 31 12:38:31 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7233D12D7F4; Tue, 31 May 2016 12:38:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160531193830.20160.2045.idtracker@ietfa.amsl.com>
Date: Tue, 31 May 2016 12:38:30 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/ZpYpvYXqELM0KPr_BainR_kERUY>
Cc: rdd@cert.org, dots-chairs@ietf.org, Kathleen.Moriarty.ietf@gmail.com, dots@ietf.org
Subject: [Dots] dots - New Meeting Session Request for IETF 96
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 19:38:30 -0000

A new meeting session request has just been submitted by Roman Danyliw, a Chair of the dots working group.


---------------------------------------------------------
Working Group Name: DDoS Open Threat Signaling
Area Name: Security Area
Session Requester: Roman Danyliw

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: mile sacm i2nsf saag
 Second Priority: opsawg opsarea



Special Requests:
  
---------------------------------------------------------

