[Dots] Adam Roach's No Objection on draft-ietf-dots-data-channel-28: (with COMMENT)

Adam Roach via Datatracker <noreply@ietf.org> Thu, 02 May 2019 06: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 3C317120052; Wed, 1 May 2019 23:46:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-data-channel@ietf.org, Roman Danyliw <rdd@cert.org>, dots-chairs@ietf.org, rdd@cert.org, dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Adam Roach <adam@nostrum.com>
Message-ID: <155677961624.2911.12192112207910183191.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2019 23:46:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/c8Kei8cHT_jfMcQY1qWBpO68wBI>
Subject: [Dots] Adam Roach's No Objection on draft-ietf-dots-data-channel-28: (with COMMENT)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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, 02 May 2019 06:46:56 -0000

Adam Roach has entered the following ballot position for
draft-ietf-dots-data-channel-28: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


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



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


Thanks to everyone who worked on this document. Alexey covered all of my
substantive comments, and I support his DISCUSS; I only have a few editorial
nits to suggest.

---------------------------------------------------------------------------

ID Nits reports:

  ** There is 1 instance of too long lines in the document, the longest one
     being 5 characters in excess of 72.

---------------------------------------------------------------------------

§3.4:

>  its own information (e.g., server names, literal IP addresses) is
>  present in the "Via" header of a DOTS message it receives:

Nit: "...header field..."

>     header, the DOTS gateway MUST NOT forward the DOTS message.

Nit: "...header field..."

>  error-info:     <via-header> : A copy of the Via header when

Nit: "<via-header-field>...header field..."

>  o  Otherwise, the DOTS agent MUST update or insert the "Via" header
>     by appending its own information.

Nit: "...header field..."

>  DOTS client domain SHOULD remove the previous "Via" header
>  information after checking for a loop before forwarding.  This

Nit: "...header field..."