Re: [Gen-art] Genart last call review of draft-ietf-dots-telemetry-use-cases-11
H Y <yuuhei.hayashi@gmail.com> Sat, 24 September 2022 07:59 UTC
Return-Path: <yuuhei.hayashi@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41E9DC14F732; Sat, 24 Sep 2022 00:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvLDdWSiRxfI; Sat, 24 Sep 2022 00:59:32 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B74EC14F5E1; Sat, 24 Sep 2022 00:59:32 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id r18so4761912eja.11; Sat, 24 Sep 2022 00:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date; bh=bSktCXgCdxT7X++ZbglWiSdsySCE+8FFWhRKxLEbbgE=; b=o57+PE9Dtj02YwEPb1P1FJjem8T7E9Q45NZhEmeBlT8EXIt/gorhP4FoibJxa6RIhk XwsWKbj9iHtclg8FWVXQ4Xx3AgiQd+GzVlfz7udazt7WDWYELkXHN7Az2I+Z3aE5g/ck tULubHqE5pnKiRBv/0J2FL+n5k4bO5Es91zzapXlGsAm8y0084/onN/UIFrOGJXKNkOh x/2E+CvBq05LsT1rymL8VhKs8tOVkJS5i4r/JsxSpCVKmpBtH2hSf7ouE/ezNKI+v9Tt rTJ5tyOm4SmUzx1h50tx1zme87zY9nvY7UTzeJDsax8dQPIry/j/r51VwUbtpsUnYcmW hkQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=bSktCXgCdxT7X++ZbglWiSdsySCE+8FFWhRKxLEbbgE=; b=yS5hk3ONe7uz+O3dAdONsnkHiuemuZiO9mZisUHvUKwtO3z6yfdXeNhFw3rquFpbjI 2Aq1K1eW/uTebLRCGzivg5ARaQpA+8IY2hlejUKCNP5rZcjIxdnGMp5pNzy9UatWXx5G joHDuttoUegxzAZ13bpZrBH0FKdo2xnwcFqiJPTgKIFSSTqUF+SWkahR3lMVhxlXM0Y0 ORaF+yRg83gBirx63xtKe8sSFOFbVEO+IfMw3k/QWRLyAYVgwMoENKKcO6L5O1FV6RWL rkdAcB6mENYGPkHCHpZIO4NWsAaO480yfWzcP6k1GpmQnXvTDy3IO2rGfr8XH70K54l4 +g9g==
X-Gm-Message-State: ACrzQf1U9VFEfMeY/MrOwwmiKtJ3XxfKo7iDT6DKbduoVLOUoHHQ1vIv G9NW2Vb13qxVsNVhEEs2jmtTHYoftB+j5KtmDD3530KkgAKC7A==
X-Google-Smtp-Source: AMsMyM6i0/yZrn+yQs1J3eUyJ+TSblS8NgKkddCG8bm4AHMfzeupHiXmMksCDKzGsXESFvrJwwfb6F06g7oKF2y5PWc=
X-Received: by 2002:a17:906:58c8:b0:6fe:91d5:18d2 with SMTP id e8-20020a17090658c800b006fe91d518d2mr10484954ejs.190.1664006370680; Sat, 24 Sep 2022 00:59:30 -0700 (PDT)
MIME-Version: 1.0
References: <166373969727.11523.6129559868974729364@ietfa.amsl.com>
In-Reply-To: <166373969727.11523.6129559868974729364@ietfa.amsl.com>
From: H Y <yuuhei.hayashi@gmail.com>
Date: Sat, 24 Sep 2022 16:59:20 +0900
Message-ID: <CAA8pjUOg6gW5+H93tKtBvQFN7i16RCGWSozrZrmg6a=4CztCnw@mail.gmail.com>
To: Peter Yee <peter@akayla.com>
Cc: gen-art@ietf.org, dots@ietf.org, draft-ietf-dots-telemetry-use-cases.all@ietf.org, last-call@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Lhyp07MCMcMgCj2pTutPDybMaJo>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-dots-telemetry-use-cases-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2022 07:59:33 -0000
Hi Peter, Thank you for your very careful review. We modified the draft to address the comments, and you can see the diff here. https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-use-cases-12 Please see inline. 2022年9月21日(水) 14:54 Peter Yee via Datatracker <noreply@ietf.org>: > > Reviewer: Peter Yee > Review result: Ready with Nits > > I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed > by the IESG for the IETF Chair. Please treat these comments just > like any other last call comments. > > For more information, please see the FAQ at > > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. > > Document: draft-ietf-dots-telemetry-use-cases-11 > Reviewer: Peter Yee > Review Date: 2022-09-20 > IETF LC End Date: 2022-09-20 > IESG Telechat date: Not scheduled for a telechat > > Summary: This document gives use cases showing how RFC 9244 can be employed for > to convey DOTS telemetry. It seems perfectly fine as an informational adjunct > to RFC 9244, giving more involved examples. > > Major issues: None. > > Minor issues: None. > > Nits/editorial comments: > > Page 3, section 3, 1st paragraph: insert “the” before “DOTS telemetry > specifications” and change “specifications” to “specification”. [Yuhei] Thanks. I addressed this comment. > > Page 4, section 3.1.1, 1st paragraph, 1st sentence: delete “such”. Change “is” > to “are”. [Yuhei] Thanks. I addressed this comment. > > Page 4, section 3.1.1, 1st paragraph, 2nd sentence: change “recent” to > “recently”. Change “Tps” to “Tbps”, unless you believe that 1 transaction per > second is a lot of traffic. One tablespoon might be. ;-) [Yuhei] Thanks. I addressed this comment. > > Page 7, 1st paragraph, 2nd sentence: change “identifies” to “identify”. Change > “of” to “about”. [Yuhei] Thanks. I addressed this comment. > > Page 7, 1st paragraph, 3rd sentence: delete the first two commas (bracketing > “then”). [Yuhei] Thanks. I addressed this comment. > > Page 7, section 3.1.2, 1st paragraph, 2nd sentence: change “under attack time” > to “at the time of an attack”. [Yuhei] Thanks. I addressed this comment. > > Page 9, 1st paragraph, 2nd sentence: change “of” to “on”. [Yuhei] Thanks. I addressed this comment. > > Page 9, 1st paragraph, 4th sentence: delete “each”. [Yuhei] Thanks. I addressed this comment. > > Page 9, 1st paragraph, 5th sentence: change “atribute” to “attribute”. [Yuhei] Thanks. I addressed this comment. > > Page 10, section 3.1.3, 1st paragraph, 1st sentence: delete “an”. [Yuhei] Thanks. I addressed this comment. > > Page 12, 1st paragraph, 2nd sentence: change “of” to “about”. Delete “a” after > “using”. [Yuhei] Thanks. I addressed this comment. > > Page 12, 1st paragraph, 3rd sentence: delete “On the other hands,” and > capitalize the ‘t’ in “the”. Insert “the” before “volume”. [Yuhei] Thanks. I addressed this comment. > > Page 12, section 3.1.4, 1st paragraph, 1st sentence: delete the comma after > “Short”. Change “internet” to “Internet”. [Yuhei] Thanks. I addressed this comment. > > Page 12, section 3.1.4, 1st paragraph, 2nd sentence: considering inserting > “salient” before “feature”. Insert “it” before “start” and change “start” to > “starts”. Change “go” to “goes” in both occurrences in the sentence. Insert > “then” before “ back to maximum”. [Yuhei] Thanks. I addressed this comment, considering Genart and Artart last call review comments. OLD: The feature of the attack is that start from zero and go to maximum values in a very short time span, then go back to zero, and back to maximum, repeating in continuous cycles at short intervals. NEW: These attacks start from zero and go to maximum values in a very short time span, then go back to zero, and then back to maximum, repeating in continuous cycles at short intervals. > > Page 12, section 3.1.4, 1st paragraph, 3rd sentence: delete “for them”. Insert > “such” before “an attack”. Change “by” to “using a”. Change “it” to “this”. [Yuhei] Thanks. I addressed this comment, considering Genart and Artart last call review comments. OLD: It is difficult for them to mitigate an attack by DMS by redirecting attack flows because it may cause route flapping in the network. NEW: It is difficult for the transit providers to mitigate such an attack with their DMSes using a redirecting attack flows because this may cause route flapping in the network. > > Page 12, section 3.1.4, 2nd paragraph, 2nd sentence: insert “the” before > “attack traffic”. [Yuhei] Thanks. I addressed this comment. > > Page 14, 1st paragraph, 3rd sentence: change “rate-limit” to “rate-limiting of”. [Yuhei] Thanks. I addressed this comment. > > Page 14, 2nd paragraph: change “gatherd” to “gathered”. [Yuhei] Thanks. I addressed this comment. > > Page 15, section 3.1.5, 1st paragraph, 3rd sentence: change “suspecious” to > “suspicious”. [Yuhei] Thanks. I addressed this comment. > > Page 15, section 3.1.5, 1st paragraph, 4th sentence: delete “an”. [Yuhei] Thanks. I addressed this comment. > > Page 15, 3rd paragraph, 2nd sentence: change “as below” to “that”. [Yuhei] Thanks. I addressed this comment. > > Page 15, 3rd paragraph, 3rd sentence: add a comma after “total attack > connection”. [Yuhei] Thanks. I addressed this comment. > > Page 17, Figure 11: change “vulnerbilities” to “vulnerabilities” twice. [Yuhei] Thanks. I addressed this comment. > > Page 19, 1st paragraph, 4th sentence: delete the two commas bracketing “then”. > Change the first space after “e.g.” to a comma. [Yuhei] Thanks. I addressed this comment. > > Page 19, section 3.2, 1st paragraph, 2nd sentence: change “counter measure” to > “countermeasure”. [Yuhei] Thanks. I addressed this comment. > > Page 19, section 3.2, 2nd paragraph, 1st sentence: change “counter measure” to > “countermeasures” (note the plural). [Yuhei] Thanks. I addressed this comment. > > Page 19, section 3.2, 2nd paragraph, last sentence: append a comma after > “”total attack traffic percentiles”. Change “detail” to “details”. [Yuhei] Thanks. I addressed this comment. > > Page 21, 1st paragraph, 2nd sentence: insert “the” before > “total-pipe-capacity”. Insert “the” before “DOTS”. [Yuhei] Thanks. I addressed this comment. > > Page 22, 1st paragraph, 1st sentence: change “mitugation” to “mitigation”. [Yuhei] Thanks. I addressed this comment. > > Page 22, 1st paragraph, 1st sentence: change “reports” to “report”. [Yuhei] Thanks. I addressed this comment. > > Page 22, 1st paragraph, 2nd sentence: change “system” to “systems”, presuming > that there can be more than one DMS reporting to the orchestrator. For the > words “sends them”, what does “them” mean? I’m assuming that the orchestrator > creates a single, integrated, deduplicated report, so I’m not sure what “them” > is. [Yuhei] Thanks. I addressed this comment. We clarified the meaning of "them". OLD: After that, the orchestrator integrates the reports from the DDoS mitigation system, while removing duplicate contents, and sends them to a network administrator by using DOTS telemetry periodically. NEW: After that, the orchestrator integrates the reports from the DDoS mitigation system, while removing duplicate contents, and sends the integrated report to a network administrator by using DOTS telemetry periodically. > > Page 22, section 3.3.1, 1st paragraph, 1st sentence: change “internet” to > “Internet”. [Yuhei] Thanks. I addressed this comment. > > Page 22, section 3.3.1, 1st paragraph, 2nd sentence: delete “On the other hand,” [Yuhei] Thanks. I addressed this comment. > > Page 22, section 3.3.1, 2nd paragraph, 1st sentence: on the assumption that > multiple flow connectors are allowed, as shown in Figure 16: change > “collector’s” to “collectors’”. [Yuhei] Thanks. I addressed this comment. > > Page 22, section 3.3.1, 2nd paragraph, 2nd sentence: change “collector” to > “collectors” on the same assumption as the previous comment. If that assumption > is incorrect, ignore both comments. Also considering changing the figure to > have a single flow collector shown in that case. [Yuhei] Thanks. I addressed this comment. We assume that multiple flow collectors are allowed as shown in Fig. 16. > > Page 25, 1st paragraph, 3rd sentence: delete the two commas bracketing “then”. [Yuhei] Thanks. I addressed this comment. > > Page 25, section 3.3.2, 2nd sentence: insert “a” or “the” before “baseline”. > Insert “the” before “DMSes”. [Yuhei] Thanks. I addressed this comment. > > Page 25, section 3.3.2, 3rd sentence: change “collector” to “collectors”. [Yuhei] Thanks. I addressed this comment. > > Page 25, Figure 18: I’m not sure what “[ Dst ]” means. It doesn’t appear > elsewhere in this specification or in RFC 9244. Perhaps “destination”?] [Yuhei] Thanks. I addressed this comment. > > Page 26, 1st paragraph, 1st sentence: I can’t parse this sentence. Consider > rewriting it. [Yuhei] Thanks. I addressed this comment. OLD: The forwarding nodes carry out mirroring traffic destined IP address. NEW: The forwarding nodes carry out traffic mirroring to copy the traffic destined a IP address and to monitor the traffic by a DMS. -
- [Gen-art] Genart last call review of draft-ietf-d… Peter Yee via Datatracker
- Re: [Gen-art] Genart last call review of draft-ie… H Y
- Re: [Gen-art] [Last-Call] Genart last call review… Lars Eggert