IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Change to 2119 Boilerplate in IDNits

Russ Housley <housley@vigilsec.com> Thu, 16 March 2017 20:19 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F732129A4C for <tools-development@ietfa.amsl.com>; Thu, 16 Mar 2017 13:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 fzSmk-jrAMGb for <tools-development@ietfa.amsl.com>; Thu, 16 Mar 2017 13:19:13 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2904B1296A2 for <tools-development@ietf.org>; Thu, 16 Mar 2017 13:19:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6FBF63004B6 for <tools-development@ietf.org>; Thu, 16 Mar 2017 16:19:12 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2rx-xx2fhlAX for <tools-development@ietf.org>; Thu, 16 Mar 2017 16:19:11 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 577A3300250; Thu, 16 Mar 2017 16:19:11 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <2812E2C7-2E1A-40E4-A781-2ED7C27DC1B5@nostrum.com>
Date: Thu, 16 Mar 2017 16:19:12 -0400
Cc: IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FED8FEC7-5AA3-4505-B699-45A216A003C0@vigilsec.com>
References: <148968846715.14133.14617215650520249241.idtracker@ietfa.amsl.com> <2812E2C7-2E1A-40E4-A781-2ED7C27DC1B5@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/sqJkNfYU4kUc4XsixiwPgXdY0XY>
Subject: Re: [TOOLS-DEVELOPMENT] Change to 2119 Boilerplate in IDNits
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 20:19:14 -0000

Ben:

Please tell us which of these activities has higher priority:

1) The DMARC and alias code.  Recall that this was perviously blocked by the version of Mailman that were we using, and the upgrade last Tuesday included an upgrade to Mailman.

2) The IDnits for bit RFC 2119 and draft-leiba-rfc2119-update boilerplate.

Russ


> On Mar 16, 2017, at 2:31 PM, Ben Campbell <ben@nostrum.com> wrote:
> 
> (Writing As IESG tools liaison, and also as the responsible AD for the draft)
> 
> Hi,
> 
> The IESG approved draft-leiba-rfc2119-update today. This draft changes the 2119 keyword boilerplate so that words are only to be interpreted with their 2119 meanings when in all-caps. Standard case instances are to be interpreted by their normal dictionary definitions.
> 
> This will require a change to IDNits to allow the new boilerplate. The IESG would like to see IDNits accept the new boilerplate as soon as possible, while continuing to allow the old boilerplate for the time being. At some point in the future, the IESG will request the old boilerplate to no longer be accepted.
> 
> Robert and Henrik, can you estimate when this might be possible? While the draft still needs to go through the RFC Editor process, I would be surprised to see changes in the proposed new boilerplate.
> 
> 
> Thanks!
> 
> Ben.

v2.23.0 | Report a Bug | By Email