
From nobody Mon Oct 11 04:33:33 2021
Return-Path: <valery@smyslov.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 9D5D73A0E7D; Mon, 11 Oct 2021 04:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.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 kqhRl6ZzSDvd; Mon, 11 Oct 2021 04:33:22 -0700 (PDT)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 DF1813A0E8A; Mon, 11 Oct 2021 04:33:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:Cc:To:From:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=pdSHNLvIERF007JnlICIOdfI3rE/4fgxxuXcYtckV5Q=; b=u0S1tYsBQJzMCyOKWQI1ldujyx MT2sFaJ1VHEXa9KHpxzLNfta/fyXg0+B0d7iPYEx6U72Klb32I3rlC2LnvYsoVE/pFqlbb61OatEp 4y0eYHdoBvclyFa9Yq20RiCAmnUBwOQn+VT7JKq5dX8r2tv+Hz5nRJEdgKWFgMw2nchdGzDko78eS DJRG2q4ArKkYF5LZAUAtRu5qcdogbR/p9yhupSnOvJXj/Lv1ODqDLhqvYjJDM+sErcLiHfkAa+1BN kUxBYCDP4UnsHkBsIKqhMVfVlfWLX2Zmmrh6WaOn5OpfPsaylWdqTfHMOgI2scYyYZklYINq0zhqs XHtA0aWw==;
Received: from [93.188.44.204] (port=50616 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1mZtYS-0005dt-6P; Mon, 11 Oct 2021 07:33:17 -0400
From: "Valery Smyslov" <valery@smyslov.net>
To: <dots@ietf.org>
Cc: <dots-chairs@ietf.org>, <draft-ietf-dots-multihoming@ietf.org>
Date: Mon, 11 Oct 2021 14:33:12 +0300
Message-ID: <002101d7be93$c890ed10$59b2c730$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ade+kv++9xgDej18RbKgd6aNUGGrkw==
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PuYp4YycliSP-35zUXIvLBjGXQY>
Subject: [Dots] WGLC for draft-ietf-dots-multihoming-07
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Oct 2021 11:33:29 -0000

Hi,

this message starts a two-week working group last call for draft-ietf-dots-multihoming-07.
The WGLC will end on Monday, October 25. Please, review the draft and send your comments to the mailing list.

Regards,
Frank & Valery.


From nobody Tue Oct 12 02:48:40 2021
Return-Path: <jon.shallow@jpshallow.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 29B673A0D77 for <dots@ietfa.amsl.com>; Tue, 12 Oct 2021 02:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 9puvQDiKcbFK for <dots@ietfa.amsl.com>; Tue, 12 Oct 2021 02:48:33 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (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 54EDA3A0CE8 for <dots@ietf.org>; Tue, 12 Oct 2021 02:48:33 -0700 (PDT)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1maEOc-0003xu-2k; Tue, 12 Oct 2021 10:48:30 +0100
From: <supjps-ietf@jpshallow.com>
To: "'Valery Smyslov'" <valery@smyslov.net>, <dots@ietf.org>
Cc: <dots-chairs@ietf.org>, <draft-ietf-dots-multihoming@ietf.org>
References: <002101d7be93$c890ed10$59b2c730$@smyslov.net>
In-Reply-To: <002101d7be93$c890ed10$59b2c730$@smyslov.net>
Date: Tue, 12 Oct 2021 10:48:27 +0100
Message-ID: <79e201d7bf4e$4e310a30$ea931e90$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH6belXfbSp5MW82qMwT7ehhypeAKuImOPA
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/aneRE5OKGyrq-MDJXDbQEnIIdk4>
Subject: Re: [Dots] WGLC for draft-ietf-dots-multihoming-07
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 12 Oct 2021 09:48:39 -0000

Hi Frank / Valery / Authors,

I have had another good read through this document.  Essentially it is
looking good.

I have the following Comments

General: I-D.ietf-dots-rfc8782-bis -> RFC9132

5.1: Will readers know what "Protocol Configuration Option" is?

5.2: The CPE MUST select ...  I have to assume that CPE is referring to the
DOTS Gateway., and a more appropriate location for this statement would be
following Figure 6 before branching off into the alternative deployment
models which do not have a DOTS gateway per se and are clients talking
direct to one or more servers.  Furthermore, in this alternative deployment
section it already states
"The use of anycast addresses to reach the DOTS servers is NOT RECOMMENDED."

5.3: This is repeated several times:-
"The use of anycast addresses is NOT RECOMMENDED to reach
   DOTS gateways."
I think it actually is only needed in the PA with specific filter rules case
(why cannot anycast be used in the PI case?)

I have the following Nits

1.: Old
upstream provider.  It can also be enabled
New (clarity on what It refers to)
upstream provider.  DOTS can also be enabled

3.: Old
Provider-Aggregatable (PA) addresses  are globally-unique
New(remove double space)
Provider-Aggregatable (PA) addresses are globally-unique

5.2: Old
   DOTS messages received from an internal DOTS client.  If anycast
   addresses are used to reach DOTS servers, the CPE may not be able to
New
   DOTS messages received from an internal DOTS client.  If anycast
   addresses are used to reach DOTS servers which cover multiple
   provisioning domains, the CPE may not be able to


Regards

Jon

> -----Original Message-----
> From: Valery Smyslov [mailto: valery@smyslov.net]
> Sent: 11 October 2021 12:33
> To: dots@ietf.org
> Cc: dots-chairs@ietf.org; draft-ietf-dots-multihoming@ietf.org
> Subject: [Dots] WGLC for draft-ietf-dots-multihoming-07
> 
> Hi,
> 
> this message starts a two-week working group last call for
draft-ietf-dots-
> multihoming-07.
> The WGLC will end on Monday, October 25. Please, review the draft and send
> your comments to the mailing list.
> 
> Regards,
> Frank & Valery.
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Fri Oct 15 06:26:47 2021
Return-Path: <kaname@nttv6.jp>
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 AD48B3A05DF for <dots@ietfa.amsl.com>; Fri, 15 Oct 2021 06:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.985
X-Spam-Level: **
X-Spam-Status: No, score=2.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, KHOP_HELO_FCRDNS=0.399, MIME_HTML_ONLY=0.1, PDS_FRNOM_TODOM_NAKED_TO=1.5, PDS_FROM_NAME_TO_DOMAIN=1.999, RCVD_IN_XBL=0.375, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, TVD_SPACE_RATIO_MINFP=0.121, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 8qB1f6gvCA-t for <dots@ietfa.amsl.com>; Fri, 15 Oct 2021 06:26:40 -0700 (PDT)
Received: from mta0.tapglove.com (bizcloud-go.tapglove.com [139.59.32.166]) (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 4E5A03A0803 for <dots@ietf.org>; Fri, 15 Oct 2021 06:26:39 -0700 (PDT)
From: ietf.org <kaname@nttv6.jp>
To: dots@ietf.org
Date: 15 Oct 2021 14:59:21 +0200
Message-ID: <20211015145921.D277E9727AF23CD8@nttv6.jp>
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/mOuDFtqTNzSJo9BopOvrU6TvqTg>
Subject: [Dots] =?UTF-8?B?5Zyo5oKo55qE55S15a2Q6YKu5Lu25biQ5oi35Lit5qOA5rWL5Yiw5byC5bi45rS75YqoIA==?=dots@ietf.org
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 15 Oct 2021 13:26:45 -0000

<p align=3D"center" style=3D"font-variant-numeric: normal; font-variant-eas=
t-asian: normal; font-stretch: normal; font-size: small; line-height: 23px;=
 font-family: Arial, Helvetica, sans-serif; padding: 0px; background-color:=
 transparent; margin: 14px 0px; min-height: 0px; overflow-wrap: break-word;=
 overflow: visible;"><font color=3D"#000000"><span style=3D"font-size: 14px=
;">&#20146;&#29233;&#30340;&#29992;&#25143;</span></font><span style=3D"fon=
t-family: arial, sans-serif; font-size: 14px;"><font color=3D"#000000">&nbs=
p;dots@ietf.org</font></span></p>
<p align=3D"center" style=3D"font-variant-numeric: normal; font-variant-eas=
t-asian: normal; padding: 0px; background-color: transparent; margin: 14px =
0px; min-height: 0px; font-stretch: normal; line-height: 23px; overflow-wra=
p: break-word; overflow: visible;"><span style=3D"font-family: Arial, Helve=
tica, sans-serif; font-size: small; background-color: transparent;"><font c=
olor=3D"#000000"><span style=3D"font-size: 14px;">&#35831;&#30830;&#35748;&=
#36825;&#23553;&#30005;&#23376;&#37038;&#20214;&#26159;&#21542;&#26377;&#25=
928;&#65292;&#22240;&#20026;&#37038;&#20214;&#19968;&#30452;&#22312;&#21453=
;&#24377;</span></font></span></p>
<p align=3D"center" style=3D"font-variant-numeric: normal; font-variant-eas=
t-asian: normal; font-stretch: normal; line-height: 23px; font-family: aria=
l, sans-serif; padding: 0px; background-color: transparent; margin: 14px 0p=
x; min-height: 0px; overflow-wrap: break-word; overflow: visible;"><span st=
yle=3D"font-family: Arial, Helvetica, sans-serif; font-size: small; backgro=
und-color: transparent;"><span style=3D"font-size: 14px;"><a data-saferedir=
ecturl=3D"https://www.google.com/url?q=3Dhttps://muprime.com/wp-admin/inclu=
des/sm/CNC/?email%3D%250%25&amp;source=3Dgmail&amp;ust=3D1634368494128000&a=
mp;usg=3DAFQjCNH10Fbu_ooX59Y4MKoGBqoYN_KYYQ" href=3D"https://cranky-zhukovs=
ky.167-71-232-210.plesk.page/sm/2018CN/2018CN/2018CN/?email=3Ddots@ietf.org=
" style=3D"color: rgb(19, 129, 68);" target=3D"_blank">&#30830;&#35748;&#26=
159;&#21542;&#26377;&#25928;</a></span></span></p>
<p align=3D"center" style=3D"font-variant-numeric: normal; font-variant-eas=
t-asian: normal; font-stretch: normal; line-height: 23px; font-family: aria=
l, sans-serif; padding: 0px; background-color: transparent; margin: 14px 0p=
x; min-height: 0px; overflow-wrap: break-word; overflow: visible;"><span st=
yle=3D"font-family: Arial, Helvetica, sans-serif; font-size: small; backgro=
und-color: transparent;"><span style=3D"font-size: 14px;">&#35874;&#35874;<=
/span></span></p>


From nobody Sun Oct 24 23:05:24 2021
Return-Path: <mohamed.boucadair@orange.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 581453A0418; Sun, 24 Oct 2021 23:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 uPio-wb8aF89; Sun, 24 Oct 2021 23:05:18 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (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 13A4A3A083C; Sun, 24 Oct 2021 23:05:18 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr24.francetelecom.fr (ESMTP service) with ESMTPS id 4Hd4Dr3jNmz1yjb;  Mon, 25 Oct 2021 08:05:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1635141916; bh=LwZEHfmFngRm9e5d3/Bal6ZWu97ZV598BARcgsK2/ko=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=JuU7gUhnaLzeNOAHc0+wxFNxU/E3hA868AC1zphnsrqo/AzhtKtFTFLGsUILZg5Nx 98uE30zkrY39Tup+O5/p3Rmpk8MZJybLGZ1IIpFXjedta/qW7vXFXN958/P+l6Rkis N9oKnVDBBZV0Bqpmp1CDzEvw4XIy+T1E1I2YgA0d2mnthz1T5n06ZH35W9sml18qaZ ZImSiUWMjJ9viS1ibEJYMnwbmWvG2d9/culeld35Q/wlHHBMWuPiEKJkLfynS3zmsy 39+ijPUdLmtKkIIYh9cBVL70CTf6ITFsv5tkgs8gnWODJQD0gPi9N5tdgtf4kvJ0ao SlkZxaYEW5gCA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr04.francetelecom.fr (ESMTP service) with ESMTPS id 4Hd4Dr2vt5z1xpL;  Mon, 25 Oct 2021 08:05:16 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "supjps-ietf@jpshallow.com" <supjps-ietf@jpshallow.com>, 'Valery Smyslov' <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "draft-ietf-dots-multihoming@ietf.org" <draft-ietf-dots-multihoming@ietf.org>
Thread-Topic: [Dots] WGLC for draft-ietf-dots-multihoming-07
Thread-Index: AQH6belXfbSp5MW82qMwT7ehhypeAKuImOPAgBVMyaA=
Content-Class: 
Date: Mon, 25 Oct 2021 06:05:15 +0000
Message-ID: <27174_1635141916_6176491C_27174_15_1_787AE7BB302AE849A7480A190F8B933035431F49@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <002101d7be93$c890ed10$59b2c730$@smyslov.net> <79e201d7bf4e$4e310a30$ea931e90$@jpshallow.com>
In-Reply-To: <79e201d7bf4e$4e310a30$ea931e90$@jpshallow.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-10-25T05:25:53Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=f3601e1c-c770-49e2-b28f-8815638112b9; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/gDWkdmvw2n8Nby-rSCyIbfMWxJU>
Subject: Re: [Dots] WGLC for draft-ietf-dots-multihoming-07
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Oct 2021 06:05:23 -0000

Hi Jon, all,

Thank you for the review.=20

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots <dots-bounces@ietf.org> De la part de supjps-ietf@jpshallow.c=
om
> Envoy=E9=A0: mardi 12 octobre 2021 11:48
> =C0=A0: 'Valery Smyslov' <valery@smyslov.net>; dots@ietf.org
> Cc=A0: dots-chairs@ietf.org; draft-ietf-dots-multihoming@ietf.org
> Objet=A0: Re: [Dots] WGLC for draft-ietf-dots-multihoming-07
>=20
> Hi Frank / Valery / Authors,
>=20
> I have had another good read through this document.  Essentially it is
> looking good.
>=20
> I have the following Comments
>=20
> General: I-D.ietf-dots-rfc8782-bis -> RFC9132

[Med] Fixed.

>=20
> 5.1: Will readers know what "Protocol Configuration Option" is?

[Med] Added a new reference for PCO:

   [TS.24008]
              3GPP, "Mobile radio interface Layer 3 specification; Core
              network protocols; Stage 3 (Release 16)", December 2019,
              <http://www.3gpp.org/DynaReport/24008.htm>.

>=20
> 5.2: The CPE MUST select ...  I have to assume that CPE is referring to
> the DOTS Gateway.

[Med] There is no DOTS gateway in this case. Internal DOTS client communica=
tes directly with DOTS servers. There are some implications at the CPE to a=
ppropriately forward the requests.

, and a more appropriate location for this statement
> would be following Figure 6 before branching off into the alternative
> deployment models which do not have a DOTS gateway per se and are clients
> talking direct to one or more servers.  Furthermore, in this alternative
> deployment section it already states "The use of anycast addresses to
> reach the DOTS servers is NOT RECOMMENDED."

[Med] Yes, but that text was in reference to Figure 7. This text is to insi=
st on the issues in reference to Figure 8.

>=20
> 5.3: This is repeated several times:-
> "The use of anycast addresses is NOT RECOMMENDED to reach
>    DOTS gateways."
> I think it actually is only needed in the PA with specific filter rules
> case (why cannot anycast be used in the PI case?)
>=20

[Med] This is problematic even in the PI case. Think about distinct CPEs (a=
nd thus DOTS gateways) that are used to connect a DOTS client domain to the=
 Internet. Only one gateway will be selected by the internal routing, and t=
hus only one server will be contacted. The DDoS traffic will still be forwa=
rded via the other interconnection link as this is a an attack targeting a =
PI resource.=20

Now rereading the text, and given that we say that ** all ** gateways must =
be contacted, I suggest we go for this change:

NEW:
The use of anycast addresses to establish DOTS sessions between DOTS client=
s and DOTS gateways is not an option.


> I have the following Nits
>=20
> 1.: Old
> upstream provider.  It can also be enabled New (clarity on what It refers
> to) upstream provider.  DOTS can also be enabled

[Med] Fixed. Thanks.=20

>=20
> 3.: Old
> Provider-Aggregatable (PA) addresses  are globally-unique New(remove
> double space) Provider-Aggregatable (PA) addresses are globally-unique

[Med] This was added by xml2rfc. Will see how to make this better.=20


>=20
> 5.2: Old
>    DOTS messages received from an internal DOTS client.  If anycast
>    addresses are used to reach DOTS servers, the CPE may not be able to
> New
>    DOTS messages received from an internal DOTS client.  If anycast
>    addresses are used to reach DOTS servers which cover multiple
>    provisioning domains, the CPE may not be able to
>=20

[Med] I went for:=20

"If anycast addresses are used to reach multiple DOTS servers..."

>=20
> Regards
>=20
> Jon
>=20
> > -----Original Message-----
> > From: Valery Smyslov [mailto: valery@smyslov.net]
> > Sent: 11 October 2021 12:33
> > To: dots@ietf.org
> > Cc: dots-chairs@ietf.org; draft-ietf-dots-multihoming@ietf.org
> > Subject: [Dots] WGLC for draft-ietf-dots-multihoming-07
> >
> > Hi,
> >
> > this message starts a two-week working group last call for
> draft-ietf-dots-
> > multihoming-07.
> > The WGLC will end on Monday, October 25. Please, review the draft and
> > send your comments to the mailing list.
> >
> > Regards,
> > Frank & Valery.
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Oct 25 08:23:10 2021
Return-Path: <internet-drafts@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 E9B033A0B0A; Mon, 25 Oct 2021 08:23:04 -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>
Cc: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <163517538490.12217.16065717500832602911@ietfa.amsl.com>
Date: Mon, 25 Oct 2021 08:23:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/4Zglk6d-agNwkzDh1nm50L0mJqQ>
Subject: [Dots] I-D Action: draft-ietf-dots-multihoming-08.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Oct 2021 15:23:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS)
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy
                          Wei Pan
	Filename        : draft-ietf-dots-multihoming-08.txt
	Pages           : 16
	Date            : 2021-10-25

Abstract:
   This document discusses multi-homing considerations for Distributed-
   Denial-of-Service Open Threat Signaling (DOTS).  The goal is to
   provide some guidance for DOTS clients/gateways when multihomed.


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

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-multihoming-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-multihoming-08


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



From nobody Tue Oct 26 00:19:30 2021
Return-Path: <mohamed.boucadair@orange.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 E4E453A117A for <dots@ietfa.amsl.com>; Tue, 26 Oct 2021 00:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 E2-EF3knsN4m for <dots@ietfa.amsl.com>; Tue, 26 Oct 2021 00:19:23 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (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 6F1E73A1180 for <dots@ietf.org>; Tue, 26 Oct 2021 00:19:23 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar24.francetelecom.fr (ESMTP service) with ESMTPS id 4Hdjqt0jKZz5wWs for <dots@ietf.org>; Tue, 26 Oct 2021 09:19:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1635232762; bh=Tsk3OFGToeKDq0IMqJGS45l3alUAzpsMekqUejSLD2I=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=I0Qulc9+IVGyRt0jFasozzyEgpfLV7dK3BmQrbSCKMO2SPmbSJFO7NrJNiXo6/Wws N47EgtnWvKIhTpZwTszo52Snx8niSmpGu2uIgYkFpPXxDxl3RNZBK8aPHzztY4IAtZ cWjX9sCBB4opE9LlmF9Oz1fC0nisKWuCPEM3kLEM9HRITTyCwIVvEGN8CSUn5wxAmi ZXPKqKCs2/P3x1WN21q56uEi6TCF/bmZFUDF+RBb5H/Ug3lYXxlyjboqGetCKxeFkT e2Zbqf4IjOhBLZMBzf/pecR0UpfCSXDrMeAPD2HM73aKPaeqlMG8ZYFpB6J+Ot8K3z PeEntxs0H46dg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4Hdjqt01g9zCqk7 for <dots@ietf.org>; Tue, 26 Oct 2021 09:19:22 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: I-D Action: draft-ietf-dots-multihoming-08.txt
Thread-Index: AQHXybQ5v+GZRERcGEaH0ilGv+/ZLqvk38gw
Content-Class: 
Date: Tue, 26 Oct 2021 07:19:21 +0000
Message-ID: <31460_1635232762_6177ABFA_31460_330_1_787AE7BB302AE849A7480A190F8B9330354338C2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <163517538490.12217.16065717500832602911@ietfa.amsl.com>
In-Reply-To: <163517538490.12217.16065717500832602911@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-10-26T07:18:12Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=ea3d4f70-c95f-4f15-88bc-a0b2de656dc7; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/wqvcNF8blqQy5B0hPXDg4eJ_odA>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-multihoming-08.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 26 Oct 2021 07:19:28 -0000

Hi all,=20

This version integrates the comments received during the WGLC from Jon.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: I-D-Announce <i-d-announce-bounces@ietf.org> De la part de interne=
t-
> drafts@ietf.org
> Envoy=E9=A0: lundi 25 octobre 2021 17:23
> =C0=A0: i-d-announce@ietf.org
> Cc=A0: dots@ietf.org
> Objet=A0: I-D Action: draft-ietf-dots-multihoming-08.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the
> IETF.
>=20
>         Title           : Multi-homing Deployment Considerations for
> Distributed-Denial-of-Service Open Threat Signaling (DOTS)
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Wei Pan
> 	Filename        : draft-ietf-dots-multihoming-08.txt
> 	Pages           : 16
> 	Date            : 2021-10-25
>=20
> Abstract:
>    This document discusses multi-homing considerations for Distributed-
>    Denial-of-Service Open Threat Signaling (DOTS).  The goal is to
>    provide some guidance for DOTS clients/gateways when multihomed.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-multihoming/
>=20
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-multihoming-08
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-multihoming-08
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Fri Oct 29 06:26:21 2021
Return-Path: <valery@smyslov.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 9AFD23A11DC; Fri, 29 Oct 2021 06:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.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 teDUI1wcYfbO; Fri, 29 Oct 2021 06:26:14 -0700 (PDT)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 2025C3A11D9; Fri, 29 Oct 2021 06:26:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=NHQcHmqJs890zEqWTMBdH+S23lxH/Ud0qgwnlmZCb7s=; b=OSbIY4VnejDjaKBVlfSFmO/C/b AukvAds8n+S7jnZDE7FrDjrQTMHdMkaVNV/k0o9QqgEtrh0xMUrV3uATIJSBant5AvRsjK77HDqOK npkx6JK/+3HBgQk5t1soOEChPG4TWWieMKSW65h9WlKiW38KHganEd7nbvqv4sRnAQIbjNe32/EZE qyjeVunjGkt9Z/drshaIN6L2Sgn6MdvG5qagGAC1Kz5o7IZJBUl33YIgn77Qsw1trmbjUILY85MW8 Daoochcq/b9PAvkduiBcSAdjocx2KwRQ9GymS122Zf6igBzesLIT9e5yeI/dKwcYNpFnOfUc2B/pr K1V9mMZw==;
Received: from [93.188.44.204] (port=63887 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1mgRtY-0000lK-9h; Fri, 29 Oct 2021 09:26:08 -0400
From: "Valery Smyslov" <valery@smyslov.net>
To: <dots@ietf.org>
Cc: <dots-chairs@ietf.org>, <draft-ietf-dots-multihoming@ietf.org>
References: <002101d7be93$c890ed10$59b2c730$@smyslov.net>
In-Reply-To: <002101d7be93$c890ed10$59b2c730$@smyslov.net>
Date: Fri, 29 Oct 2021 16:26:09 +0300
Message-ID: <059501d7ccc8$8ad61390$a0823ab0$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: ru
Thread-Index: AQH6belXfbSp5MW82qMwT7ehhypeAKukjvbw
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/B9luSwvNS49IiGUnyGwpNzyua-s>
Subject: Re: [Dots] WGLC for draft-ietf-dots-multihoming-07
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 29 Oct 2021 13:26:20 -0000

Hi,

here is my review of the draft (sorry for delay).

[chair hat on]

First, I'm a bit confused why this is a Standards Track document.
draft explicitly states that it defines no new protocol, it only 
contains recommendations how applications should deal
with multihomed scenarios.

Isn't Informational or BCP status more appropriate for this document?

A related issue - the draft has a normative reference to RFC 8811,
which is an Informational RFC and is not listed in the downref registry.
If this draft persists as Standards Track document, this should be
worked around.

[chair hat off]

Section 4.

I might be missing something very obvious, but from my reading of the scenarios 
I have an impression that only those situations when upstream network providers 
are also the DDoS mitigation providers are considered. What if you have multiple 
ISPs and a single independent DDOS mitigation provider? Or you have several
DDOS mitigation providers, and some of them are provided by ISPs and some are
independent? 

Section 5.1.

   For each provisioning domain, the DOTS client MUST resolve the DOTS
   server's name provided by a provisioning domain ([RFC8973]) using the
   DNS servers learned from the respective provisioning domain.

What if explicit configuration (RFC8973, Section 4, item 1) is used?
If this case this recommendation is unnecessary.

Section 5.1.

   Consequently, if a CPE detects a DDoS attack that spreads over all
   its network attachments, it MUST contact both DOTS servers for
   mitigation purposes.

s/both/all

Then, it seems to be implied that all network attachments 
have provided CPE with DOTS servers. In this case how
can happen what is described earlier:

  This implies that if no appropriate DOTS server is found,
   the DOTS client MUST NOT send the mitigation request to any other
   available DOTS server.

I think that this situation is only possible when some network attachments
don't provide CPE with DOTS servers.

Section 5.1.

   DOTS signaling session to a
   given DOTS server must be established using the interface from which
   the DOTS server was provisioned.

What about explicit configuration, when DOTS server IP is not associated
with a network interface?

Section 5.2.

I think the readability would benefit from moving pictures 6 and 7 closer to the text that 
refers to them. Currently they are almost half page apart.

Section 5.2.

   Each DOTS client SHOULD be provided with policies (e.g., a prefix
   filter that will be against DDoS detection alarms) that will trigger
   DOTS communications with the DOTS servers.  Such policies will help
   the DOTS client to select the appropriate destination DOTS server.

It's unclear for me to which scenario this recommendation applies.
In Figure 8 each DOTS client may communicate only with a single DOTS server.

Related question - why SHOULD (and not MUST)?.  What if clients
are not provided with these policies?

Section 5.2.

   The CPE MUST select the appropriate source IP address when forwarding
   DOTS messages received from an internal DOTS client.  If anycast
   addresses are used to reach multiple DOTS servers, the CPE may not be
   able to select the appropriate provisioning domain to which the
   mitigation request should be forwarded.  As a consequence, the
   request may not be forwarded to the appropriate DOTS server.

I'm confused. What to do in this case? Using anycast addresses
is NOT RECOMMENDED (earlier), but is not prohibited.
I believe better recommendations should be given for this case.

Section 5.3.

Again, I think it's worth to move Figure 9 closer to the text that 
refers to it.

Section 5.3.

   The use of anycast addresses
   to establish DOTS sessions between DOTS clients and DOTS gateways is
   not an option.

What does "is not an option" mean? MUST NOT be used? Or impossible to use?

Section 6.

   In particular, if a DOTS client maintains DOTS
   associations with specific DOTS servers per interconnection link, the
   DOTS client SHOULD NOT leak information specific to a given link to
   DOTS servers on different interconnection links that are not
   authorized to mitigate attacks for that given link.

How this rule can be followed when DOTS clients send requests
to all available DOTS servers (with PI scenarios)?

Regards,
Valery.


> Hi,
> 
> this message starts a two-week working group last call for draft-ietf-dots-multihoming-07.
> The WGLC will end on Monday, October 25. Please, review the draft and send your comments to the mailing
> list.
> 
> Regards,
> Frank & Valery.
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

