[Dots] comments for this document as contributor://答复: I-D Action: draft-ietf-dots-server-discovery-03.txt

"Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com> Fri, 21 June 2019 08:24 UTC

Return-Path: <frank.xialiang@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2746C120173 for <dots@ietfa.amsl.com>; Fri, 21 Jun 2019 01:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id edqS129JHEDs for <dots@ietfa.amsl.com>; Fri, 21 Jun 2019 01:24:06 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (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 47549120123 for <dots@ietf.org>; Fri, 21 Jun 2019 01:24:06 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 70CD04B594D3314CDDD5 for <dots@ietf.org>; Fri, 21 Jun 2019 09:24:02 +0100 (IST)
Received: from DGGEMM421-HUB.china.huawei.com ( by lhreml704-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 21 Jun 2019 09:23:59 +0100
Received: from DGGEMM511-MBX.china.huawei.com ([]) by dggemm421-hub.china.huawei.com ([]) with mapi id 14.03.0439.000; Fri, 21 Jun 2019 16:20:05 +0800
From: "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: =?utf-8?B?Y29tbWVudHMgZm9yIHRoaXMgZG9jdW1lbnQgYXMgY29udHJpYnV0b3I6Ly8=?= =?utf-8?B?562U5aSNOiBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLWRvdHMtc2VydmVyLWRp?= =?utf-8?Q?scovery-03.txt?=
Thread-Index: AdUoAc6D6bAbWctJRc2/vRHMZHXNOg==
Date: Fri, 21 Jun 2019 08:20:05 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F13E7AC66A@dggemm511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/YaVMU6HbOpQKC9EutIHgegk98KE>
Subject: [Dots] =?utf-8?q?comments_for_this_document_as_contributor=3A//?= =?utf-8?q?=E7=AD=94=E5=A4=8D=3A_I-D_Action=3A_draft-ietf-dots-server-disc?= =?utf-8?q?overy-03=2Etxt?=
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, 21 Jun 2019 08:24:09 -0000

Hi authors,
I have several comments as contributor below:

1. nits
    Section 1: 
        s/The discovery methods can also used by a DOTS server to locate.../ The discovery methods can also be used by a DOTS server to locate.../
        s/ [I-D.ietf-netconf-zerotouch]/[RFC8527]/
    title section 5: s/DHCP Options for DOTS/ DHCP Options for DOTS Agent Discovery/
    section 5.1.1: s/ The DHCPv6 DOTS option/ The DHCPv6 DOTS Reference Identifier option/
    section 5.1.2: s/ The DHCPv6 DOTS option/ The DHCPv6 DOTS Address option/
    section 5.2.1: s/ The DHCPv4 DOTS option/ The DHCPv4 DOTS Reference Identifier option/
    section 5.2.2: s/ The DHCPv4 DOTS option/ The DHCPv4 DOTS Address option/

    1) In section 1, I don't see any relation of happy eyeball with your proposed dots agent discovery mechanism, it not so necessary to mention it;
    2) In section 4, " DOTS clients will prefer information received from the discovery methods in the order listed. ": in what kind of order?
    3) For section 5.1.3 and section 5.2.3, there seems to be some confusions and conflictions about these points: what is the goal of returning more than one instance of OPTION_V6_DOTS if must only use the first instance? Does one DOTS Reference Identifier Option include one or multiple dots-agent-name?
    4) In section 5.2.1, will figure 5 be more appropriate as figure 3?
    5) For section 6--DNS service resolution , this section does not clarify the process and details about how to get DOTS agent IP based on the retrieved DOTS agent name?
    6) Section 7 (DNS-SD) is very short, can you clarify briefly what is the essential difference between this mechanism and previous DNS service resolution mechanism?
    7) Is it possible to list the pro & con, or at least the related constraints for each discovery mechanisms at the end of the document? I think it's useful for reader in the real implementation.



发件人: Dots [mailto:dots-bounces@ietf.org] 代表 mohamed.boucadair@orange.com
发送时间: 2019年5月31日 17:19
收件人: dots@ietf.org
主题: Re: [Dots] I-D Action: draft-ietf-dots-server-discovery-03.txt

Hi all, 

The main change in this version is to integrate call-home considerations. 

We do think this version is stable enough for a WGLC. 


> -----Message d'origine-----
> De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de 
> internet-drafts@ietf.org Envoyé : vendredi 31 mai 2019 11:10 À : 
> i-d-announce@ietf.org Cc : dots@ietf.org Objet : I-D Action: 
> draft-ietf-dots-server-discovery-03.txt
> 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 
>         Title           : Distributed-Denial-of-Service Open Threat
> Signaling (DOTS) Server Discovery
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
> 	Filename        : draft-ietf-dots-server-discovery-03.txt
> 	Pages           : 22
> 	Date            : 2019-05-31
> Abstract:
>    It may not be possible for a network to determine the cause for an
>    attack, but instead just realize that some resources seem to be under
>    attack.  To fill that gap, Distributed-Denial-of-Service Open Threat
>    Signaling (DOTS) allows a network to inform a DOTS server that it is
>    under a potential attack so that appropriate mitigation actions are
>    undertaken.
>    This document specifies mechanisms to configure DOTS clients with
>    DOTS servers.  The discovery procedure also covers the DOTS Signal
>    Channel Call Home.
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-server-discovery/
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-server-discovery-03
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-server-discovery
> -03
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-server-discovery-03
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at 
> tools.ietf.org.
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> _______________________________________________
> 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

Dots mailing list