IETF Logo Mail Archive

[apps-discuss] Use of RFC 2119, Re: WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt

Julian Reschke <julian.reschke@gmx.de> Wed, 21 March 2012 06:44 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8653221F857F for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 23:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.53
X-Spam-Level:
X-Spam-Status: No, score=-103.53 tagged_above=-999 required=5 tests=[AWL=-0.931, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUHdVMmI9QXW for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 23:44:50 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 914B621F8484 for <apps-discuss@ietf.org>; Tue, 20 Mar 2012 23:44:49 -0700 (PDT)
Received: (qmail invoked by alias); 21 Mar 2012 06:44:48 -0000
Received: from p57A6E8EB.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.232.235] by mail.gmx.net (mp031) with SMTP; 21 Mar 2012 07:44:48 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+7Vsp/Px67Rsc2FQwbfbwPUFtd0ydns8rcDxpj0Z NQ2kDzEXuS/+vT
Message-ID: <4F6978D8.10605@gmx.de>
Date: Wed, 21 Mar 2012 07:44:40 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <503575970.11554@cnnic.cn> <4A10020DB6464A0BBA535BF75D21A9D9@LENOVO47E041CF> <9452079D1A51524AA5749AD23E003928094CEB@exch-mbx901.corp.cloudmark.com> <CAC4RtVB9vbCoHN5wwgRkVc6Yhkp7ERQKgpMeHp93HGMqYpiAQQ@mail.gmail.com>
In-Reply-To: <CAC4RtVB9vbCoHN5wwgRkVc6Yhkp7ERQKgpMeHp93HGMqYpiAQQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] Use of RFC 2119, Re: WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 06:44:50 -0000

On 2012-03-21 03:34, Barry Leiba wrote:
>> [Relatively] Minor Issues:
>> I'm not so sure about use of RFC2119 language in the IANA Considerations
>> section.  You're not really describing interoperability requirements with IANA.
>
> I'm sure.  And it's my text -- this is one that Mykyta doesn't like.
> The three MUSTs in there are not directed at IANA, but at people
> writing new registrations.  They tell those people what their
> registrations have to look like, and I wanted to use MUST to stress
> that even though this is an FCFS policy, there are requirements
> nonetheless.
> ...

I'm with Murray here. This is something RFC 2119 keywords are not for.

Best regards, Julian

v2.23.0 | Report a Bug | By Email