[Dots] Roman Danyliw's No Objection on draft-ietf-dots-robust-blocks-05: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Mon, 03 October 2022 16:46 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 1927FC14EB1E; Mon, 3 Oct 2022 09:46:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dots-robust-blocks@ietf.org, dots-chairs@ietf.org, dots@ietf.org, valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 8.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <166481560609.59028.16387659415973902260@ietfa.amsl.com>
Date: Mon, 03 Oct 2022 09:46:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/htFAL_DP6lka-7dAVVLbK2Npib8>
Subject: [Dots] Roman Danyliw's No Objection on draft-ietf-dots-robust-blocks-05: (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: Mon, 03 Oct 2022 16:46:46 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-dots-robust-blocks-05: 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-robust-blocks/



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

Section 7.  Recommend a pointer to explain the intent usage of the YANG module.

OLD
   This document defines YANG data structures that are meant to be used
   as an abstract representation in DOTS signal channel messages.  As
   such, the "ietf-dots-robust-trans" module (Section 5) does not
   introduce any new vulnerabilities beyond those specified above.

NEW

Consistent with Section 5 of [RFC9131], this YANG module is not intended to be
used via NETCONF/RESTCONF for DOTS server management purposes.  It serves as an
abstract representation in DOTS signal channel messages.   The
"ietf-dots-robust-trans" module (Section 5) does not introduce any new
vulnerabilities beyond those specified above.