IETF Logo Mail Archive

[Dots] Shepherd feedback on draft-ietf-dots-data-channel-21

Roman Danyliw <rdd@cert.org> Wed, 26 September 2018 20:36 UTC

Return-Path: <rdd@cert.org>
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 B438F128C65 for <dots@ietfa.amsl.com>; Wed, 26 Sep 2018 13:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 713Kl5YRqTwp for <dots@ietfa.amsl.com>; Wed, 26 Sep 2018 13:36:13 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A863B126CC7 for <dots@ietf.org>; Wed, 26 Sep 2018 13:36:13 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w8QKaAko046706 for <dots@ietf.org>; Wed, 26 Sep 2018 16:36:10 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu w8QKaAko046706
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1537994170; bh=CNt0RaP70ZqvNWnFdOwqUfJH8ajDIjdrEYaPy7UH5Ak=; h=From:To:Subject:Date:From; b=KUi+c3PEp8Xu8e16BaSGHveNPZ/SdJCMJ0JspNkU5w3hwrqulVONdXot7lLsd8ioB wpocow5XA0cq6fX5SGZinDZj+uSEyhp+//V29MY9748jQ6fWljDmmZ24bA6ALRm5WY DD9R7uxVd3b4JtBw1UAikZBgRNQqAPxhtg4Ewnzk=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w8QKa5Vq010584 for <dots@ietf.org>; Wed, 26 Sep 2018 16:36:05 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0399.000; Wed, 26 Sep 2018 16:36:05 -0400
From: Roman Danyliw <rdd@cert.org>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Shepherd feedback on draft-ietf-dots-data-channel-21
Thread-Index: AdRV19jHE2e2qdMcQo+LZPRf9LNaNg==
Date: Wed, 26 Sep 2018 20:36:03 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC014C45627E@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/qYoNT8h1DPJtC1UYMYuau-KKPmg>
Subject: [Dots] Shepherd feedback on draft-ietf-dots-data-channel-21
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: Wed, 26 Sep 2018 20:36:16 -0000

Hi!

In preparing my write-up for draft-ietf-dots-data-channel-21 I found no issues beyond one of formatting.  idnits 2.15.01 reported:

--[ snip idnits output ]--
tmp/draft-ietf-dots-data-channel-21.txt(933): Line is too long: the offending characters are 'tor'
tmp/draft-ietf-dots-data-channel-21.txt(934): Line is too long: the offending characters are ')?'
tmp/draft-ietf-dots-data-channel-21.txt(937): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(939): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(944): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(946): Line is too long: the offending characters are 'ator)'
tmp/draft-ietf-dots-data-channel-21.txt(947): Line is too long: the offending characters are 'operator'
tmp/draft-ietf-dots-data-channel-21.txt(948): Line is too long: the offending characters are ')?'
tmp/draft-ietf-dots-data-channel-21.txt(959): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(961): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(966): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1003): Line is too long: the offending characters are 'tor'
tmp/draft-ietf-dots-data-channel-21.txt(1004): Line is too long: the offending characters are ')?'
tmp/draft-ietf-dots-data-channel-21.txt(1015): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1017): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1022): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1024): Line is too long: the offending characters are 'ator)'
tmp/draft-ietf-dots-data-channel-21.txt(1025): Line is too long: the offending characters are 'operator'
tmp/draft-ietf-dots-data-channel-21.txt(1026): Line is too long: the offending characters are ')?'
tmp/draft-ietf-dots-data-channel-21.txt(1029): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1031): Line is too long: the offending characters are 'r'
tmp/draft-ietf-dots-data-channel-21.txt(1036): Line is too long: the offending characters are 'r'

  ** There are 22 instances of too long lines in the document, the longest
     one being 8 characters in excess of 72.
--[ end ]--

To get more context on which were the offending lines:

--[ snip]--
$ cat draft-ietf-dots-data-channel-21.txt | awk 'length($0) > 72 {print NR ":" $0}'
933:       |              |     |     |     +--rw source-port-range-or-operator
934:       |              |     |     |        +--rw (port-range-or-operator)?
937:       |              |     |     |           |  |       inet:port-number
939:       |              |     |     |           |          inet:port-number
944:       |              |     |     |                      inet:port-number
946:       |              |     |        +--:(destination-port-range-or-operator)
947:       |              |     |           +--rw destination-port-range-or-operator
948:       |              |     |              +--rw (port-range-or-operator)?
959:       |              |     |                 |  |       inet:port-number
961:       |              |     |                 |          inet:port-number
966:       |              |     |                            inet:port-number
1003:       |              |     |     |     +--rw source-port-range-or-operator
1004:       |              |     |     |        +--rw (port-range-or-operator)?
1015:       |              |     |     |           |  |       inet:port-number
1017:       |              |     |     |           |          inet:port-number
1022:       |              |     |     |                      inet:port-number
1024:       |              |     |        +--:(destination-port-range-or-operator)
1025:       |              |     |           +--rw destination-port-range-or-operator
1026:       |              |     |              +--rw (port-range-or-operator)?
1029:       |              |     |                 |  |       inet:port-number
1031:       |              |     |                 |          inet:port-number
1036:       |              |     |                            inet:port-number
--[snip]--

Can these please be fixed in a -22 prior to requesting publication.

Thanks,
Roman

v2.23.0 | Report a Bug | By Email