Re: [v6ops] RFC 2119 language in an informational draft?

On Thu, Aug 5, 2021 at 12:00 PM tom petch <ietfc@btconnect.com> wrote:

> From: v6ops <v6ops-bounces@ietf.org> on behalf of Fred Baker <
> fredbaker.ietf@gmail.com>
> Sent: 05 August 2021 09:17
>
> May I suggest that an informational draft doesn't impose requirements, so
> there is no need for RFC 2119 language?
>
> <tp>
> I think that that suggestion is erroneous.

+1.

While this might be argumentum ad antiquitam, it is clear that this isn't
the standard interpretation.

Looking through the RFCs 8000 and above, I find 262 Informational documents
using RFC2119 (RFC8174) language, and >4000 instances:
$ for file in (grep -l 'Category: Informational' rfc8???.txt)
                                                  egrep
"SHOULD|MUST|REQUIRED|SHALL|RECOMMENDED|MAY|OPTIONAL" $file
                                              end > ~/tmp/info_2119.txt
$ wc -l ~/tmp/info_2119.txt
  4023

This undercounts the number because there may be multiple instances of 2119
language per line.

> Protocol specifications from other parties who publish via the ISE should
not be barred from using RFC8174 language.  RFC7868 comes to mind and if I
knew how to search for ISE publications, I suspect that I would find many
more.

Looking through ISE documents >8000 I find roughly 1700 instances:

for file in (grep -l 'Independent Submission' rfc8???.txt)
                                               egrep --with-filename
"SHOULD|MUST|REQUIRED|SHALL|RECOMMENDED|MAY|OPTIONAL" $file
                                           end > ~/tmp/ise_2119.txt

wc -l ~/tmp/ise_2119.txt
    1737

The last 10 for spot-checkin':
more /Users/wkumari/tmp/ise_2119.txt | awk '{print $1}' | sort | uniq |
tail -10
rfc8774.txt:
rfc8785.txt:
rfc8802.txt:
rfc8805.txt:
rfc8902.txt:
rfc8904.txt:
rfc8905.txt:
rfc8927.txt:
rfc8962.txt:
rfc8998.txt:

>
> Tom Petch
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra