[Dots] Robert Wilton's No Objection on draft-ietf-dots-telemetry-use-cases-14: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 20 October 2022 12:27 UTC

Return-Path: <noreply@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 601A1C152585; Thu, 20 Oct 2022 05:27:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dots-telemetry-use-cases@ietf.org, dots-chairs@ietf.org, dots@ietf.org, valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 8.18.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <166626886138.39103.6251890628492350957@ietfa.amsl.com>
Date: Thu, 20 Oct 2022 05:27:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/VKLmoeOkOe1eONTUGoB_yK2PYmg>
Subject: [Dots] Robert Wilton's No Objection on draft-ietf-dots-telemetry-use-cases-14: (with COMMENT)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 20 Oct 2022 12:27:41 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-dots-telemetry-use-cases-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry-use-cases/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

Thanks for this document.  A couple of minor nits:

(1) p 2, sec 1.  Introduction

  This document presents sample use
   cases for DOTS Telemetry, which makes concrete overview and purpose
   described in [RFC9244]: what components are deployed in the network,
   how they cooperate, and what information is exchanged to effectively
   use attack-mitigation techniques.

I found this sentence hard to parse.


(2) p 5, sec 3.1.1.  Mitigating Attack Flow of Top-talker Preferentially

   The forwarding nodes send traffic statistics to the flow collectors,
   e.g., using IP Flow Information Export (IPFIX) [RFC7011].  When DDoS
   attacks occur, the flow collectors identify the attack traffic and
   send information about the top-talkers to the orchestrator using the
   "target-prefix" and "top-talkers" DOTS telemetry attributes.  The
   orchestrator then checks the available capacity of the DMSes by using
   a network management protocol, such as Simple Network Management
   Protocol (SNMP) [RFC3413] or YANG with Network Configuration Protocol
   (YANG/NETCONF) [RFC6020].

Please use RFC 7950 as the reference for YANG.  Please check other references.

Regards,
Rob