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

["Ben Campbell" <[e-mail]>]

I'm going to say DMARC is higher priority. It's causing actual pain. But 
let me confirm that with the IESG.

Thanks!

Ben.

On 16 Mar 2017, at 15:19, Russ Housley wrote:

> 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 <[e-mail]> 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.