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

Barry Leiba <barryleiba@computer.org> Wed, 28 March 2012 09:04 UTC

Return-Path: <barryleiba@gmail.com>
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 AEEB021F89C8 for <apps-discuss@ietfa.amsl.com>; Wed, 28 Mar 2012 02:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.998
X-Spam-Level:
X-Spam-Status: No, score=-102.998 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 G7ut-KbDxrgn for <apps-discuss@ietfa.amsl.com>; Wed, 28 Mar 2012 02:04:30 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4350C21F8902 for <apps-discuss@ietf.org>; Wed, 28 Mar 2012 02:04:30 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so1249534obb.31 for <apps-discuss@ietf.org>; Wed, 28 Mar 2012 02:04:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EHABw5A54KaO2kklqJIQXoQqhF2A/9Qr0/NLRyW6vPo=; b=YljH5nTPN1Ba995s/YRLuhRbEhcHtzjONL0rgl3sJTxqsNanoeGqois8c0RB+f8ONv RPawrLoShTb/iOsz9sNE7YNBJR/ZlKCHlJDG88U9PxdypfJxcWgkzDSWYqV66McnKP1z jl+bshtQdCwk9ypAbFFyDfIJpKYr51Rfyuh1lAP1EG1JSsUK4nC1PtCtMWHZ1xhulOKU bPaKHyGJKVaFNiCnkMQ97jh3EJkblaWdUgOMyMZ7VoKQfkAoEL8RV1xDJyTyKaqRvVoi 67lI0kcTQCrUxLx5ZKD5Q8qOu/ik3eNtg6BzoY0XSQbXWF9vK+HTG3r3xd03Seo9JvSL sZlQ==
MIME-Version: 1.0
Received: by 10.182.154.7 with SMTP id vk7mr3116371obb.22.1332925469842; Wed, 28 Mar 2012 02:04:29 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.60.10.68 with HTTP; Wed, 28 Mar 2012 02:04:29 -0700 (PDT)
In-Reply-To: <4F72D2C0.2040604@isode.com>
References: <503575970.11554@cnnic.cn> <4A10020DB6464A0BBA535BF75D21A9D9@LENOVO47E041CF> <9452079D1A51524AA5749AD23E003928094CEB@exch-mbx901.corp.cloudmark.com> <CAC4RtVB9vbCoHN5wwgRkVc6Yhkp7ERQKgpMeHp93HGMqYpiAQQ@mail.gmail.com> <4F6978D8.10605@gmx.de> <C68CB012D9182D408CED7B884F441D4D06A902E82B@nambxv01a.corp.adobe.com> <CALaySJ+2ULmwhpuA211ZJbZJHLWaT_BC7J0wpYtPc_uJWZY18A@mail.gmail.com> <4F72D2C0.2040604@isode.com>
Date: Wed, 28 Mar 2012 05:04:29 -0400
X-Google-Sender-Auth: ey-qiIkQ3H5616F9lA6uY6xMHu4
Message-ID: <CALaySJJWOGkTeF6x1rGAJXjirBBvbXoFSRDkGf-cPgh+Fyro_A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary="f46d04479fdd245ee704bc49e5b3"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [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, 28 Mar 2012 09:04:30 -0000

>> Sure; we're starting with FCFS (as in BCP 26), and then adding
requirements.  Perfectly fine.
>
> I think the question is who is going to enforce RFC 2119 language.

Well, IANA's going to make sure the registration request contains the
required information.  And that's all we have there.

b