Re: [v6ops] RFC2119 Upper Case Syntax for rfc2460bis
james woodyatt <jhw@conjury.org> Thu, 05 November 2015 13:53 UTC
Return-Path: <jhw@conjury.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565D71B2CD1 for <v6ops@ietfa.amsl.com>; Thu, 5 Nov 2015 05:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TFXmfjDLTDvI for <v6ops@ietfa.amsl.com>; Thu, 5 Nov 2015 05:53:56 -0800 (PST)
Received: from prime.conjury.org (prime.conjury.org [IPv6:2607:f2f8:a938::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878721B2CD5 for <v6ops@ietf.org>; Thu, 5 Nov 2015 05:53:55 -0800 (PST)
Received: from [10.71.13.83] (122x216x24x202.ap122.ftth.ucom.ne.jp [122.216.24.202]) by prime.conjury.org (Postfix) with ESMTPSA id 8733486E5E; Thu, 5 Nov 2015 05:53:54 -0800 (PST)
References: <7B3C244B-8B06-4DD6-A8FD-B4B1A64D66A0@gmail.com> <9130A0EE-04F3-4B99-B675-AE4DC5B5BBBC@gmail.com> <8FC43AD9-F854-4763-AA8B-EF1F64493AB7@nestlabs.com> <5626D56C.4090706@umn.edu> <56297ACF.4000701@umn.edu> <33751EAE-1F00-4A54-9D74-6CD1839F86AB@gmail.com> <562AC9B0.4020409@umn.edu> <0A008CF4-86EE-470C-9C87-241ACC812D28@gmail.com> <5FD4B50E-9481-445F-BD10-7200C919BE60@nestlabs.com> <C311D4A7-9A0A-4858-9A7E-D7954BBE6C29@gmail.com> <537F1DC8-DE42-4BD3-986A-C6C89493827D@nestlabs.com> <9F630BB6-55E8-420A-A3F1-955A274B19AF@gmail.com>
From: james woodyatt <jhw@conjury.org>
Content-Type: text/plain; charset="utf-8"
X-Mailer: iPhone Mail (12H321)
In-Reply-To: <9F630BB6-55E8-420A-A3F1-955A274B19AF@gmail.com>
Message-Id: <08128F4B-4352-46E1-B346-6CB2E4B01219@conjury.org>
Date: Thu, 05 Nov 2015 22:53:53 +0900
To: Bob Hinden <bob.hinden@gmail.com>, "v6ops@ietf.org list" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/k0xZ3Y2lDOf9-xC7t8hWIuEcFpg>
X-Mailman-Approved-At: Sat, 07 Nov 2015 15:45:30 -0800
Subject: Re: [v6ops] RFC2119 Upper Case Syntax for rfc2460bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 13:53:58 -0000
Sigh. Of course it doesn't. It merely says the keywords are "often" capitalized. It then proceeds to use the keywords itself, and always capitalizes them. I stand corrected. I give up. There is no winning here. —sent from my phone > On Nov 5, 2015, at 18:55, Bob Hinden <bob.hinden@gmail.com> 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. > > Bob > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > --------------------------------------------------------------------
- Re: [v6ops] RFC2119 Upper Case Syntax for rfc2460… james woodyatt