[Idr] preempt BGP parameter squatting through warnings/errors in idnits tool?

Job Snijders <job@ntt.net> Mon, 13 March 2017 20:06 UTC

Return-Path: <job@instituut.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57DE1294D5 for <idr@ietfa.amsl.com>; Mon, 13 Mar 2017 13:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.418
X-Spam-Level:
X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 aAD-wjtJ3Gea for <idr@ietfa.amsl.com>; Mon, 13 Mar 2017 13:06:43 -0700 (PDT)
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD381129B00 for <idr@ietf.org>; Mon, 13 Mar 2017 13:06:43 -0700 (PDT)
Received: by mail-wm0-f42.google.com with SMTP id n11so49083497wma.1 for <idr@ietf.org>; Mon, 13 Mar 2017 13:06:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=veXaNIKM32ZXIklAvrvF13uw4coWh2HHR2ZBXwUETes=; b=C0LqShF4WEiZie+xbpxxfuW/828zMjC3BbCqHJM6d5VDBdO8iKo7yexHjVWeCP/WGO uLupXoP+jhU5AnIchaZQ6B80CuayDJgLFKMFQX3M8wf+vG81YsdfErhib3vtVaQsgbi5 Sn75//1eYjdOm5YzLoDQG4Zx8N+w8lZPvRuB8IJABwx50tryGBsf+RMsOfN2Cjs7Sd+C jkObw781Wj3gutc492udo1KdL0zyu47/hDu4LtlhIMpulux9jzpGYWy2eJaPZetuZP8s Lg2QOK3IJh5ZdobKFhKYKDe1okZKnMOmEo+4qeVIKTa3NpUcMGowBZGL6eXY4j36D/aa D94w==
X-Gm-Message-State: AFeK/H3RRC8peuucKL0I1wRk8aHZQtNnTR5m5sY3MwTWk0riBEQS5pZoyTCNzVFxEhP7Dg==
X-Received: by 10.28.150.194 with SMTP id y185mr11466174wmd.92.1489435601776; Mon, 13 Mar 2017 13:06:41 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:d171:79c6:67cd:815b]) by smtp.gmail.com with ESMTPSA id v1sm26176451wra.65.2017.03.13.13.06.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2017 13:06:37 -0700 (PDT)
Date: Mon, 13 Mar 2017 21:06:36 +0100
From: Job Snijders <job@ntt.net>
To: idr@ietf.org
Message-ID: <20170313200636.mcarzfvikh5p5pce@Vurt.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lAVMowNmvw8KWwYWVp6RnKDclNM>
Subject: [Idr] preempt BGP parameter squatting through warnings/errors in idnits tool?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2017 20:06:45 -0000

Hi group,

This morning I thought to myself: "isn't part of the codepoint squatting
challenge our dependence on manual review of drafts for documented
potential squatting?"

Perhaps the idnits tool (https://tools.ietf.org/tools/idnits/about) can
be updated in such a way to throw a warning or nit error when the
Working group is "IDR" and the "IANA Considerations" section contains
any of these regexes:

    [cCode] \(suggested [0-9]+\)
    suggested value .* [0-9]+\.
    [tT]he suggested value

Or perhaps only look for these if the string 'TDB' doesn't occur
anywhere the "IANA Considerations" section. I'm sure we can come up with
some likely heuristics based on prior submissions to catch potential
squatting-to-be.

The idnits tools could make a suggestion like:

    "It appears this draft targetted for IDR is self servicing BGP
    codepoints, please review
    https://trac.ietf.org/trac/idr/wiki/Checklist%20for%20writing%20a%20BGP-related%20draft
    or contact the IDR chairs".

Of course this may only be a small piece of the solution, but it could
help instill discipline in this working group.

Kind regards,

Job