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

Barry Leiba <barryleiba@computer.org> Fri, 17 April 2015 01:22 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 BC7FA1A8969; Thu, 16 Apr 2015 18:22:41 -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 SlE9xgCJHC3Y; Thu, 16 Apr 2015 18:22:39 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 C23FF1A895E; Thu, 16 Apr 2015 18:22:39 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so3353746igb.1; Thu, 16 Apr 2015 18:22:39 -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=gn26uy0DGFMArcWplNbXeL43Py9xgJsZPVwuIuIombU=; b=uG/pUNalP9DCtA4HRgb+9ZMv6jndrJCNXx8H0LHVJ3O7fBAbKLkyjdXT6fZ8oH5HDV yghgeAtonm51aKHoXVjNKdmfgKotF4qM40hODdOPlA2+mM7zJF/8yclQwUYQvTVqDtfr kEI86OFJjoFfluL2Y02pZ7gUL0hENix2Nxj0R24gQ45OaWu0qM77whQ0vWPWmYcKYwBY U1mFQ0DLXdiAmXUTakWUANmJzr0TenJTLamDK9R+wQGW/Ri+54NrjwScL6xbYNGDzPOW VPt/gYK5NjjCHN98SkHYDHdwk8/u9i948r69odr33IJdqHjTmi3fkzeyIV2Gd/QVOkuy shOQ==
MIME-Version: 1.0
X-Received: by 10.107.15.82 with SMTP id x79mr723162ioi.75.1429233759295; Thu, 16 Apr 2015 18:22:39 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.107.7.130 with HTTP; Thu, 16 Apr 2015 18:22:39 -0700 (PDT)
In-Reply-To: <E9D930CF73F16EC450FE7811@JcK-HP8200.jck.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>
Date: Thu, 16 Apr 2015 21:22:39 -0400
X-Google-Sender-Auth: 0-VYiek7UeIjHGIQZ7ndaPw8cjo
Message-ID: <CALaySJKPE0adSkbDS6_80ub8_gQdUHKqea-Ldc2+vVOCsLAqeA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/nb7gVlDv4LFSzsCkVG1mQUcHs0U>
Cc: "draft-ietf-appsawg-uri-scheme-reg.all@ietf.org" <draft-ietf-appsawg-uri-scheme-reg.all@ietf.org>, IESG <iesg@ietf.org>, Apps Discuss <apps-discuss@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: Fri, 17 Apr 2015 01:22:41 -0000

>> Just now, I've re-reviewed all references to 3986 within
>> draft-ietf-appsawg-uri-scheme-reg-06 and don't see anywhere
>> that it should be construed as >updating< 3986. There are lots
>> of places where people are directed to looking at 3986 and
>> 3987, and a thorough understanding of those is needed to fully
>> appreciate some of the things being said in here. But if
>> there's ANY doubt about us NOT updating them, is there a need
>> to explicitly state that, say in the introduction?
>
> In the spirit of moving on, I'd prefer to avoid requiring
> another rev and will happily settle for the assurance that
> everyone involved will provide support for my pushing back if
> anyone stands up and says "you can't do <X> in URNs because
> draft-ietf-appsawg-urn-scheme-reg clarified 3986 to prohibit it".

Thanks, John!  I'm off to ask the Secretariat to make the approval announcement.

Barry