IETF Logo Mail Archive

Re: [apps-discuss] Retroactive application of draft-ietf-appsawg-uri-scheme-reg - comprehensive review

Barry Leiba <barryleiba@computer.org> Sun, 19 April 2015 02:14 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85AEB1A0204; Sat, 18 Apr 2015 19:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 ty0PiyPYnEEM; Sat, 18 Apr 2015 19:14:41 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4AB61A0123; Sat, 18 Apr 2015 19:14:41 -0700 (PDT)
Received: by iejt8 with SMTP id t8so95708024iej.2; Sat, 18 Apr 2015 19:14:41 -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:message-id:subject :from:to:cc:content-type; bh=0h8UcZ9k2I7S7krCXD0vQ2p1H7WF9m/8gGo/TC/QLSM=; b=hnAhcyZ3ldqqAPflTEceFYGKD4YDSKflf4UFTcaMVfDgyJuX2ZsqvR/6NOxb5Dssae doUWh10nNyYqLGjx6B1wvB+7yoREbjYZh46hY5aAWP8KOr/fzMrrjz/wvhzujpL1e2F1 rUnMKwMRwya/GmwfQoNtZyZR3I9hJil7HFk9vuaS9qycCYIQgRE05QU/G+rfx9v41zot 7Ayr7KA+/6xlnOOFJW8bPw6wfUO1aZeYYkefT5nZq+bHsNgjKuJLDQnvfqMKhtZZ0gVn fMp7FmvH0WgDJQgxmwArnSQu+2gEFfOtPeEoT3zJW1J1ZQNOfEOiEOVxtu0ydbQUzMSQ zCYQ==
MIME-Version: 1.0
X-Received: by 10.50.138.70 with SMTP id qo6mr12671049igb.40.1429409681076; Sat, 18 Apr 2015 19:14:41 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.107.7.130 with HTTP; Sat, 18 Apr 2015 19:14:40 -0700 (PDT)
In-Reply-To: <A5076874-9226-4DD5-8454-1084D90C60D9@adobe.com>
References: <2E49FA112B054FFAED69D8A1@JcK-HP8200.jck.com> <CALaySJ+JdE5YrBuXv343_CfNP4mYxOR94JV4q_Uso4VoWfD=Ng@mail.gmail.com> <723FBC93979E1019101319C5@JcK-HP8200.jck.com> <CALaySJL-QbQ7rMRmBHTCjNbjUMKdrHrNSBLZ5zyVQ69VvXMu3A@mail.gmail.com> <AB0D76A4BFEEA77B7878126E@JcK-HP8200.jck.com> <CALaySJ+4STYA1YDeUKVTLj7FXCcTSo1W_kRTf2Vc-VSQnke22w@mail.gmail.com> <55301F9F.5080207@att.com> <E9D930CF73F16EC450FE7811@JcK-HP8200.jck.com> <55316A2B.5090900@ninebynine.org> <CEC31053B7E64D53478FB2F6@JcK-HP8200.jck.com> <A5076874-9226-4DD5-8454-1084D90C60D9@adobe.com>
Date: Sat, 18 Apr 2015 22:14:40 -0400
X-Google-Sender-Auth: jm28g8F_ANk1vjbNL00mnO1QFB4
Message-ID: <CALaySJLZR8pLpB0BpX9UMqe3oTi8cehMPHvpbBkRfopP-zhZsw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Larry Masinter <masinter@adobe.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/Sn5jSKRn-9Jdzudje4VKIcaYs6s>
Cc: Apps Discuss <apps-discuss@ietf.org>, Graham Klyne <gk@ninebynine.org>, "draft-ietf-appsawg-uri-scheme-reg.all@ietf.org" <draft-ietf-appsawg-uri-scheme-reg.all@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [apps-discuss] Retroactive application of draft-ietf-appsawg-uri-scheme-reg - comprehensive review
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 19 Apr 2015 02:14:42 -0000

I think what Larry says here is exactly right -- this, in particular:

> But these are GUIDELINES. There is no formal or IANA-enforced
> requirements or Expert Reviewer override.  IETF consensus on a
> URN document that directs IANA to change the "urn:" scheme
> registration will cause the registration to change. Explaining why
> you're not following BCP 35 might be helpful in getting IETF
> consensus, but there is no specifics on what constitutes an
> adequate justification.

I'm happy to consider that this is the last that needs to be said on
this topic with respect to this document.  Thanks, Larry.

Barry

v2.23.0 | Report a Bug | By Email