[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Re: RFC2119 Upper Case Syntax for rfc2460bis
From:       David Farmer <farmer () umn ! edu>
Date:       2015-11-06 21:48:15
Message-ID: 563D201F.4050305 () umn ! edu
[Download RAW message or body]

On 11/5/15 03:55 , Bob Hinden wrote:
> James,
> 
> > That’s why having a note right there in RFC 2460bis that explains the divergence \
> > from the recommended capitalization strategy is an acceptable compromise to me.
> 
> While I am not against adding text to clarify how the language is used in these \
> drafts, but please show where it says that capitalization is required or even \
> recommended?  It doesn’t say that in RFC2119.

There is nothing that explicitly says it.  I think because the suggested 
boiler within RFC2119 used ALL-CAPS to add emphasis to the quoted 
keywords, it has become a common practice, and one might even call it de 
facto IETF style to use All-CAPS to add emphasis to normative uses of 
RFC2119 keywords.

Personally, I think as this is a style issue, and it SHOULD be well 
within the editorial discretion of the author.  And, I'd really prefer 
we not do something like update RFC2119 to make it mandatory, but we could.

That said, if I were the author of this, given the importance and 
expected longevity of this, I would probably update the RFC2119 key 
words to use ALL-CAPS.  But I'm with James, "having a note right there 
in RFC 2460bis that explains the divergence from the [expected] 
capitalization strategy is an acceptable compromise".   James originally 
call it "the recommend capitalization strategy", I think it is more 
accurate to call it "the expected capitalization strategy".

Finally, I would strongly object to the idea of leaving all the keywords 
lowercase, and omitting the RFC2119 boilerplate and reference or other 
similar note.  But you agreed to provide such a note.  So, once we see 
the proposed text I expect we can quickly finish this.

thanks
-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]