Re: [Dots] 答复: Shepherd review of draft-ietf-dots-telemetry-use-cases

Valery Smyslov <smyslov.ietf@gmail.com> Mon, 11 April 2022 11:20 UTC

Return-Path: <smyslov.ietf@gmail.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 1C5F63A17E8; Mon, 11 Apr 2022 04:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 tDuIaqN8FkTt; Mon, 11 Apr 2022 04:20:17 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 EE89E3A17E1; Mon, 11 Apr 2022 04:20:16 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id t25so25988883lfg.7; Mon, 11 Apr 2022 04:20:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=svAcXY5gdDTh8dpT1JPYhiyNJ5wNH+s/pNPqom+VbWs=; b=h4utLbylCRk1Y9w2BUjv5xiexswXfPInRLLEczhN8ktLzL+w/eaRnyc1QVJj0PAFCf 2SETREvRf7VsSERB3qArRfYJ/hOTMZOLlH4hQwdgkvA27+56zmyX5trgXuXKdNoxEsjU vsyj1PJp6659QUjrPIlZFxmAoErY3wcfZq6WQ/2PBhsoNv6ErcPPHrtGONw9JSr8WHkn wepmHmOrV8NXsG5knLSw4uh6ohHTaTQcvVSSBiBtA+MJUadSTcBmS15vwRP6i7cBg10v VD6Bqtaocr7kD7D/0LDamjiQJqdwM9oknV2hIZxP92Q0jfsZg8rccHtQq1CaKMQ6nQX8 kpvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=svAcXY5gdDTh8dpT1JPYhiyNJ5wNH+s/pNPqom+VbWs=; b=FkxAHwLrA8Xsa6HKQCTzbLiWxuO4xFxm7WvNu6iSe2g2rt2/coPFcjNZ5vW40x0N2u YQnmddaBewHFhJTdl6thvrMXtcKck7hPEerQTvkkJUnl6zA1ZCrsum6D53c0ZhrA+KRP NmiBntMnFtwqQKL+mL22blJ0XqXyFqXI61rkDHBCQF30B5zQS9ptK7W2G8S/E4iZGBnC 3kMqjRLKB6dP3A91m8I1UznWaQNcqK9kNEI2yZtVILCOIZM+oK3d9DJp9ICmDcp3nRV3 2g+tDczXCeC3j55YowUSu71GQ2hW4ouAEc0TK7iHuxCD4ZLUEmJgBY99QypBGdwMoIw5 GOMQ==
X-Gm-Message-State: AOAM5321XuMysVDXAZGu/pfapUJCaqlMY3hhhz1mtoL4UlTCqQ1tvD6s UjI488GKv27V4Q8kIJbimYW1Jb71lSw=
X-Google-Smtp-Source: ABdhPJxZAM5UwyMA+UBEgcdVaLK/JkMOOcLPV4tOp8TyNwTI4QbWiYY1K4MpsgZtaBmCW0wdU3I/6g==
X-Received: by 2002:a05:6512:3a83:b0:46a:38a2:d7e with SMTP id q3-20020a0565123a8300b0046a38a20d7emr11649880lfu.61.1649676014212; Mon, 11 Apr 2022 04:20:14 -0700 (PDT)
Received: from buildpc ([93.188.44.204]) by smtp.gmail.com with ESMTPSA id u19-20020a197913000000b00448a1f20261sm3295854lfc.34.2022.04.11.04.20.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Apr 2022 04:20:13 -0700 (PDT)
From: Valery Smyslov <smyslov.ietf@gmail.com>
To: 'SuLi' <suli@chinamobile.com>
Cc: draft-ietf-dots-telemetry-use-cases@ietf.org, 'dots' <dots@ietf.org>, 'dots-chairs' <dots-chairs@ietf.org>
References: <19f101d84506$df98e810$9ecab830$@smyslov.net> <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com> <1bec01d847f5$47685890$d63909b0$@smyslov.net> <002b01d848c7$858cd240$90a676c0$@com>
In-Reply-To: <002b01d848c7$858cd240$90a676c0$@com>
Date: Mon, 11 Apr 2022 14:20:12 +0300
Message-ID: <1fb701d84d96$1d4f5080$57edf180$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVlQNLgeASXdSWg3oo1N+vMEhaoAHfpd/4AmLtYWYCcZdk/6u6YESQ
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/-J7SHDHbrQHK6aoqZmjpTc8D0_s>
Subject: Re: [Dots] 答复: Shepherd review of draft-ietf-dots-telemetry-use-cases
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 Apr 2022 11:20:22 -0000

Hi,

BCP78 and BCP79 requires that all authors and contributors confirm that they are 
not _aware_ of any IPR (or disclose them). So, it is not sufficient to confirm 
that you don't _have_ any IPR, you must confirm that you are not _aware_
of any IPR (for example, your employer may have one). Note, that you are not
required to search through all IPRs, you only required to confirm that you
are not aware of any.

So, please you re-confirm that you are not aware of any IPR related to the draft.

Regards,
Valery.

> Dear all:
> 	I don't have any IPR in this draft.
> 
> Best Regards!
> Su Li(粟栗)
> 
> -----邮件原件-----
> 发件人: Valery Smyslov [mailto:valery@smyslov.net]
> 发送时间: 2022年4月4日 15:26
> 收件人: 'H Y'
> 抄送: draft-ietf-dots-telemetry-use-cases@ietf.org; 'dots'; 'dots-chairs'
> 主题: RE: Shepherd review of draft-ietf-dots-telemetry-use-cases
> 
> Hi Yuhei,
> 
> thank you for updating the document. I've been waiting for the
> remaining author to provide IPR confirmation. Once I receive it,
> I'll send the document to IESG.
> 
> Regards,
> Valery.
> 
> > Hi Valery,
> >
> > Thank you for your careful review.
> >
> > We fixed the nits and posted it as draft-ietf-dots-telemetry-use-cases-10.
> >
> > >4. Section 3.1.1.
> > >   After that, the orchestrator
> > >   orders the forwarding nodes to redirect as much of the top talker's traffic...
> > > Shouldn't it be top-talkers' ?
> > >7. Section 3.1.5.
> > > s/The forwarding nodes  send traffic statistics ... to the orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> >
> > We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so we
> > fixed them all.
> >
> > Thanks,
> > Yuhei
> >
> > 2022年3月31日(木) 22:54 Valery Smyslov <valery@smyslov.net>:
> > >
> > > Hi,
> > >
> > > I reviewed the document and found some nits (mostly grammar and typos).
> > >
> > > 1. Abstract.
> > >
> > > The expansion of DOTS is "DDoS Open Threat Signaling". In the abstract it is expanded as "Denial-of-
> service
> > Open Threat Signaling".
> > >
> > > 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
> > >
> > > All contain the same typo:
> > >
> > > s/S is for DOTS client functionality/S is for DOTS server functionality
> > >
> > > 3. Section 3.1.1.
> > >
> > > IPFIX, BGP, SNMP aren't expanded on first use.
> > >
> > > 4. Section 3.1.1.
> > >
> > >    After that, the orchestrator
> > >    orders the forwarding nodes to redirect as much of the top talker's traffic...
> > >
> > > Shouldn't it be top-talkers' ?
> > >
> > > 5. Figure 7.
> > >
> > > s/BGP Flow spec/BGP Flowspec
> > >
> > > 6. Section 3.1.5.
> > >
> > > s/It may also necessary/It may also be necessary
> > >
> > > 7. Section 3.1.5.
> > >
> > > s/The forwarding nodes  send traffic statistics ... to the orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> > >
> > > 8. Section 3.2.
> > >
> > > s/Figure 15 provides ...  from the orchestrator to the network ./Figure 15 provides ...  from the
> orchestrator
> > to the network.
> > >
> > > 9. Section 3.2.
> > >
> > > s/Then, the DDoS mitigation systems reports the status of DDoS countermeasures to the orchestrator
> > sending "attack-detail" telemetry
> > > attributes./
> > > Then, the DDoS mitigation systems reports the status of DDoS countermeasures to the orchestrator by
> > sending "attack-detail"
> > > telemetry attributes.
> > >
> > > 10. Section 3.2.
> > >
> > > s/After  that, the orchestrator integrates the reports ... and send it to a network administrator .../
> > > After  that, the orchestrator integrates the reports ... and sends them to a network administrator ...
> > >
> > > (two places)
> > >
> > > 11. Section 3.3.1.
> > >
> > >    On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic better
> > >    than flow monitoring.
> > >
> > > I have trouble parsing this text. Probably:
> > >
> > >   On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic
> > >    than flow monitoring.
> > >
> > > 12. Section 3.3.1.
> > >
> > > s/The aim of this use case is to increases flow collector's detection .../The aim of this use case is to increase
> > flow collector's
> > > detection ...
> > >
> > > 13. Section 3.3.1.
> > >
> > > s/statisticsto/statistics to
> > >
> > > 14. Section 4.
> > >
> > > s/a DDoS attacks/DDoS attacks
> > >
> > > Regards,
> > > Valery.
> > >
> >
> >
> > --
> > ----------------------------------
> > Yuuhei HAYASHI
> > 08065300884
> > yuuhei.hayashi@gmail.com
> > iehuuy_0220@docomo.ne.jp
> > ----------------------------------
> 
> 
> 
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots