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

Henrik Levkowetz <henrik@levkowetz.com> Fri, 17 March 2017 16:36 UTC

Return-Path: <henrik@levkowetz.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 85ED81294CA for <tools-development@ietfa.amsl.com>; Fri, 17 Mar 2017 09:36:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] 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 FcdDuFfnXPss for <tools-development@ietfa.amsl.com>; Fri, 17 Mar 2017 09:36:40 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE40E1294A5 for <tools-development@ietf.org>; Fri, 17 Mar 2017 09:36:39 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:60315 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1courm-0002N2-Ek; Fri, 17 Mar 2017 09:36:39 -0700
To: Ben Campbell <ben@nostrum.com>, IETF Tools Development <tools-development@ietf.org>
References: <148968846715.14133.14617215650520249241.idtracker@ietfa.amsl.com> <2812E2C7-2E1A-40E4-A781-2ED7C27DC1B5@nostrum.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <58CC108F.3040801@levkowetz.com>
Date: Fri, 17 Mar 2017 17:36:31 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <2812E2C7-2E1A-40E4-A781-2ED7C27DC1B5@nostrum.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="V5hfc4x8TNEKvfGRi23H8AsQAKx7X7nIf"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: tools-development@ietf.org, ben@nostrum.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/9CfcIzoCfLnPlvpGYAVRX_eKxII>
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: Fri, 17 Mar 2017 16:36:41 -0000

Hi Ben,

On 2017-03-16 19:31, Ben Campbell 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.

I can do a new idnits release as soon as the RFC number for the new
RFC is available, so I know the exact boilerplate text.  Should take me
a couple of hours, at most.

Best regards,

	Henrik

> 
> 
> Thanks!
> 
> Ben.
> 
> Forwarded message:
> 
>> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
>> To: ben@nostrum.com, draft-leiba-rfc2119-update@ietf.org
>> Subject: ID Tracker State Update Notice: 
>> <draft-leiba-rfc2119-update-02.txt>
>> Date: Thu, 16 Mar 2017 11:21:07 -0700
>>
>> IESG state changed to Approved-announcement to be sent from IESG 
>> Evaluation
>> ID Tracker URL: 
>> https://datatracker.ietf.org/doc/draft-leiba-rfc2119-update/
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development
>