Re: [Gen-art] Gen-ART Last Call review of draft-baeuerle-netnews-cancel-lock-05

Julien ÉLIE <julien@trigofacile.com> Mon, 10 July 2017 19:31 UTC

Return-Path: <julien@trigofacile.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3E7131899 for <gen-art@ietfa.amsl.com>; Mon, 10 Jul 2017 12:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level:
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779] 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 1vhJU8Tcodof for <gen-art@ietfa.amsl.com>; Mon, 10 Jul 2017 12:31:37 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD82131866 for <gen-art@ietf.org>; Mon, 10 Jul 2017 12:31:36 -0700 (PDT)
Received: from mbpdejulienelie.home ([86.252.120.177]) by mwinf5d81 with ME id j7Xa1v00E3pkiFq037XaMd; Mon, 10 Jul 2017 21:31:35 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Mon, 10 Jul 2017 21:31:35 +0200
X-ME-IP: 86.252.120.177
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Michael Bäuerle <michael.baeuerle@stz-e.de>, draft-baeuerle-netnews-cancel-lock.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <9be2e7af-b99d-4f86-6552-bfada936600d@alum.mit.edu> <20170707174750.487009ed@WStation4> <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu>
From: Julien ÉLIE <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <ebf51c6f-28e6-2a79-3451-debd46d862c8@trigofacile.com>
Date: Mon, 10 Jul 2017 21:31:33 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <7452e826-62e9-0d6e-32b5-dcdefcb4c2ea@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/zZ9wif206tyPp0NldUveCLgXSj8>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-baeuerle-netnews-cancel-lock-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 19:31:40 -0000

Hi Paul,

>> Julien Élie has proposed a new syntax definition.
> 
> I was copied on his mail proposing a change to RFC5536, and that is 
> tentative. *This* document would of course require a similar change. Or 
> else it could extend that change, via something like
> 
>      news-fields =/ cancel-lock / cancel-key
> 
> But that can only be done if there is actually a draft that revises 5536 
> that can then be referenced. Bottom line is that it seems there needs to 
> be some coordination of that fix with this draft.

Is a draft really needed?

In RFC 5536, I for instance read wording about taking into accounts errata:

2.3.  MIME Conformance

    User agents MUST meet the definition of MIME conformance in [RFC2049]
    and MUST also support [RFC2231].  This level of MIME conformance
    provides support for internationalization and multimedia in message
    bodies [RFC2045], [RFC2046], and [RFC2231], and support for
    internationalization of header fields [RFC2047] and [RFC2231].  Note
    that [Errata] currently exist for [RFC2045], [RFC2046], [RFC2047] and
    [RFC2231].

    [Errata]       "RFC Editor Errata",
                   <http://www.rfc-editor.org/errata.php>.



Maybe *this* document could have similar wording, like "it extends 
news-fields defined in Section 3 of [RFC5536] amended with verified 
erratum xxx".


Also note that, when referencing RFCs, the current RFC Editor's practice 
is to link to <http://www.rfc-editor.org/info/rfc5536> (that provides a 
link to the errata page).



Last but not least, for *this* document, if extending the ABNF grammar 
of another RFC gives too much bargain, then why just *not* extend 
anything and just define <cancel-lock> and <cancel-key> as-is?

Definition of Jabber-ID or DKIM-Signature header fields for instance do 
not extend anything from RFC 5322 (mail):
   https://tools.ietf.org/html/rfc7259
   https://tools.ietf.org/html/rfc6376

-- 
Julien ÉLIE

« – Chef ! On vient !
   – On se met en carré ?
   – Non ! En bosquet ! » (Astérix)