Re: [netmod] upcoming adoptions - this appendix is normative

Lou Berger <lberger@labn.net> Mon, 02 October 2017 11:59 UTC

Return-Path: <lberger@labn.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948E51345D2 for <netmod@ietfa.amsl.com>; Mon, 2 Oct 2017 04:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 H-TMH3QUYvsn for <netmod@ietfa.amsl.com>; Mon, 2 Oct 2017 04:59:00 -0700 (PDT)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B6D1323B4 for <netmod@ietf.org>; Mon, 2 Oct 2017 04:58:59 -0700 (PDT)
Received: from cmgw3 (unknown [10.0.90.84]) by gproxy8.mail.unifiedlayer.com (Postfix) with ESMTP id 1B3C91AB1BE for <netmod@ietf.org>; Mon, 2 Oct 2017 05:58:55 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id Gbyr1w0072SSUrH01byuhU; Mon, 02 Oct 2017 05:58:55 -0600
X-Authority-Analysis: v=2.2 cv=K/VSJ2eI c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=02M-m0pO-4AA:10 a=AUd_NHdVAAAA:8 a=wU2YTnxGAAAA:8 a=48vgC7mUAAAA:8 a=fCKLsFGb-9ytqeNey90A:9 a=QEXdDO2ut3YA:10 a=Yz9wTY_ffGCQnEDHKrcv:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=hS4b1bRSZ8IlML0AuQHZowjopplzeyqykLMGsEo4MlE=; b=TDZqmMKSiLW8ut5H1MnlvbRZSz vrUDmGc/B6w6x8yf4zNe948oCksoAAnxWfCLRzi6Pp8KBkkAN2mWRoCDZfPcZBo0orU213Gq3LTGA LHwN5fqgVbjMTcN1o5CY7ezKE;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:36178 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1dyzN5-0023rU-09; Mon, 02 Oct 2017 05:58:51 -0600
To: Benoit Claise <bclaise@cisco.com>, "t.petch" <ietfc@btconnect.com>, Kent Watsen <kwatsen@juniper.net>, Robert Wilton <rwilton@cisco.com>, netmod@ietf.org
References: <36ba3d4b-1ae1-0666-12cf-db41e172924b@cisco.com> <75739d75-da96-b340-2403-d0949ac54ed7@labn.net> <19134054-D52E-4A6D-992A-A47F365557AD@juniper.net> <2891bd09-0e0d-415c-2714-15141a293e42@cisco.com> <D14158EF-77F4-4E0A-9A06-213F5CF04647@juniper.net> <011d01d32d77$c8e0a500$4001a8c0@gateway.2wire.net> <9c0d8394-b2a4-180a-2454-8955c1721423@labn.net> <003801d32e3f$ba625460$4001a8c0@gateway.2wire.net> <920d0500-e7ea-66ff-5124-a025a438dbac@cisco.com> <15edcab6a58.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <20171002110504.d6kscxoot3nb3c3a@elstar.local>
From: Lou Berger <lberger@labn.net>
Message-ID: <4f2f072c-ff80-30a9-5bc8-08a9d527f52b@labn.net>
Date: Mon, 02 Oct 2017 07:58:47 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20171002110504.d6kscxoot3nb3c3a@elstar.local>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1dyzN5-0023rU-09
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:36178
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pCNSO2kyrpHk1DoycX2sQvnoFWg>
Subject: Re: [netmod] upcoming adoptions - this appendix is normative
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2017 11:59:01 -0000

Juerge,

Understood.  I think you made this clear in our previous discussion on
this topic, even though ~93% of the RFCs published in the last 5 years
use it.   We certainly can discuss this with our AD, and if there's
sufficient interest in the WG even discuss it in Singapore. If others
are interested in face to face time for such a discussion, please let us
(all) know on the list.

Cheers,

Lou

On 10/2/2017 7:05 AM, Juergen Schoenwaelder wrote:
> Lou,
>
> the conclusion is that we add RFC 2119 here and there but I disagree
> with the notion that normative text needs RFC 2119 language, i.e.,
> that text that does not use RFC 2119 language is not normative. See
> the pointers to the RFCs that I have provided. Now you want to make
> this even a rule for all future WG docs so I strongly oppose to that.
>
> /js
>
> On Mon, Oct 02, 2017 at 06:39:35AM -0400, Lou Berger wrote:
>> Benoit,
>>
>> I think this and related topic was closed with the conclusion of sticking
>> with 2119 language for normative text in current and future WG docs. We
>> certainly can add this sentence as well.
>>
>> Lou
>>
>>
>> On October 2, 2017 5:11:20 AM Benoit Claise <bclaise@cisco.com> wrote:
>>
>>> Dear all,
>>>
>>> To avoid any confusion, just clearly mention it.
>>>      "This appendix is normative | informative"
>>> No need to debate for hours on this.
>>>
>>> Regards, Benoit
>>>> ----- Original Message -----
>>>> From: "Lou Berger" <lberger@labn.net>
>>>> Sent: Thursday, September 14, 2017 6:06 PM
>>>>
>>>>> On 9/14/2017 12:36 PM, t.petch wrote:
>>>>>> Appendices are Normative if they say that they are Normative.  The
>>>>>> default is that they are not so say that they are and they are.
>>>> This is
>>>>>> well established practice.
>>>>> Hi Tom,
>>>>> My memory (I haven't checked recently) is there is nothing in or
>>>>> defined process that says if an Appendix is normative or not. Other
>>>>> SDOs certainly have formal definitions here. Within the IETF, my view
>>>>> has been that if an appendix includes RFC2119 language, it is
>>>>> normative. Actually, strictly speaking, any text in a Standards Track
>>>>> RFC that doesn't include RFC2119 language is just informative.
>>>> Lou
>>>>
>>>> Try RFC4910.
>>>>
>>>> '   This appendix is normative.'
>>>>
>>>> and not a SHOULD or a MUST in sight.
>>>>
>>>> Tom Petch
>>>>
>>>>> Lou
>>>>>
>>>> _______________________________________________
>>>> netmod mailing list
>>>> netmod@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netmod
>>>> .
>>>>
>>>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod