IETF Logo Mail Archive

Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery

"Panwei (William)" <william.panwei@huawei.com> Sat, 26 January 2019 09:38 UTC

Return-Path: <william.panwei@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 E01A912D4ED for <dots@ietfa.amsl.com>; Sat, 26 Jan 2019 01:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93KxB_th3RcE for <dots@ietfa.amsl.com>; Sat, 26 Jan 2019 01:38:11 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 90E4A127133 for <dots@ietf.org>; Sat, 26 Jan 2019 01:38:11 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 587DC90050468E39D656 for <dots@ietf.org>; Sat, 26 Jan 2019 09:38:09 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 26 Jan 2019 09:38:08 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.167]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Sat, 26 Jan 2019 17:38:00 +0800
From: "Panwei (William)" <william.panwei@huawei.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Call for adoption on draft-boucadair-dots-server-discovery
Thread-Index: AdSI+mzom/yrMKu/SJm1ohZrl+sYtAsQHQGA
Date: Sat, 26 Jan 2019 09:38:00 +0000
Message-ID: <30E95A901DB42F44BA42D69DB20DFA6A6093D744@nkgeml513-mbx.china.huawei.com>
References: <359EC4B99E040048A7131E0F4E113AFC0184C52F1B@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC0184C52F1B@marathon>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.37.117]
Content-Type: multipart/alternative; boundary="_000_30E95A901DB42F44BA42D69DB20DFA6A6093D744nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/sjW95NQ92jrrzQFR7qGKqpQgJmU>
Subject: Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery
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: Sat, 26 Jan 2019 09:38:14 -0000

Hi,



I support adoption of this draft.



Two typos:

1. Section 5
When only DOTS server' IP
               ^^^^^^^
addresses are configured, a reference identifier must also be
configured for authentication purposes.

"server'" should be "server's".



2. Section 9.1.2 and 9.2.2
9.1.2. Format Format of DOTS Address Option
       ^^^^^^^^^^^^^
9.2.2. Format Format of DOTS Address Option
       ^^^^^^^^^^^^^

Duplicate "Format".



Two comments:

1. Section 9.1.1 and 9.2.1 describe the DOTS Reference Identifier Option, but the content of these Option is DOTS server name. I'm not quite familiar with this, so I just raise this and want to make sure if the content is right.

2. In section 9.1.2, the "List of DOTS IPv4 Addresses" contains one or more IPv4 addresses of a DOTS server, and the "OPTION_V4_DOTS" can include multiple lists. When the "OPTION_V4_DOTS" includes multiple lists, do these lists belong to one DOTS server or multiple DOTS servers? My understanding is that multiple lists belong to multiple DOTS servers and one DOTS server only has one list. I'm not quite sure, maybe an example can be added in the draft.





Best Regards

Wei Pan





> -----Original Message-----

> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Roman Danyliw

> Sent: Saturday, December 01, 2018 6:22 AM

> To: dots@ietf.org

> Subject: [Dots] Call for adoption on draft-boucadair-dots-server-discovery

>

> Hello!

>

> This is the start of a two week call for input on the WG adoption of the

> document:

>

> draft-boucadair-dots-server-discovery

> https://tools.ietf.org/html/draft-boucadair-dots-server-discovery-05

>

> The document has been presented and discussed at IETF 103, IETF 100

> and IETF 99;  and revisions have been made based on WG feedback.

> Discussion of adoption of this draft was previously deferred pending

> submission of the signal draft for publication (which occurred in

> September 2018).

>

> At the IETF 103 meeting, there were not many participants who had read

> the draft.

>

> Please provide feedback to the list/chairs if you believe that this

> document should be adopted as a WG document.  The adoption call will

> end on December 14 2018.

>

> Regards,

> Roman and Frank

>

> _______________________________________________

> Dots mailing list

> Dots@ietf.org<mailto:Dots@ietf.org>

> https://www.ietf.org/mailman/listinfo/dots

v2.23.0 | Report a Bug | By Email