Re: [urn] Summary of WG decisions Re: Feedback on draft-ietf-urnbis-semantics-clarif-03

Andrew Newton <andy@hxr.us> Tue, 31 May 2016 17:26 UTC

Return-Path: <andy@hxr.us>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6494212D0C2 for <urn@ietfa.amsl.com>; Tue, 31 May 2016 10:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20150623.gappssmtp.com
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 dHpWi2JaUgM9 for <urn@ietfa.amsl.com>; Tue, 31 May 2016 10:26:30 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 3947D12D869 for <urn@ietf.org>; Tue, 31 May 2016 10:26:30 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id n129so117605046wmn.1 for <urn@ietf.org>; Tue, 31 May 2016 10:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=r/Zty8zu7GSSi6Hgg4PgREG7NikmsK/RvNjRaYsAbX4=; b=lNXTJi+3VWcSRzqccr3kzHBBSs0M8fDU2V7oTKIJqd3uR1Nm9+KEsLMFaRZje7bq1s lK/7TCMOE5kL8COm4Qhi2nNbhnCsXDbMBFfYU9RBm+LIe45y7B1nuCO32PuLEBTyX2Nn zW4SATlvybHfn5pLdd9LB8HRYkKskOPR02yCtlu71qdKStQtbGgT8dE4eKBWhsrHpdPd FGx9eDaDGIVLL8a32o85Z6khynzvXFfnA5+N8NpFSDyrmV2wVMCYprZTNY1kdQ8h5HnQ qn5voh41ZGTvIOQWQREOfy0z32mIRm1CRlaYT439YdBdRJOP/vxCN6s3parawCxenEfl VFFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=r/Zty8zu7GSSi6Hgg4PgREG7NikmsK/RvNjRaYsAbX4=; b=Gaprj8N+K9ifpxlgtypPtBWPmYkCQkHCeNA0zkyBBKceUxzUCXGVW07ED51XtwTZi2 tqsVhEl1hSoUX/Zvi7AK8A967G5vdXXr0G11pFkhJLxnv4v8WT/NrxrzDGUIztuxblmx c3/yJ1ZPEUQlCXSgrhk898LeCutsFjh9qAeCjS4xMV3qSkxjqtmgR/Ax9NvTQ0lsJCbO +UI4yUUATV7y6JIOaB0CpYSrzuPay8IBe9Gb4V4F5m30tli6GLcYI28HacWzqZGd4q8o xRQCPPJRew9zTgXkLDfDhAqOCM+KBHY4nUoEFTu2KRCLDr+yn5BVSj57HLe73cDO8x2Q V76w==
X-Gm-Message-State: ALyK8tKWbgLtv5NZExnS4nUZFRvCYvvl+We3pX2Drm7uSfvFId0WiEiPj2Vuahu3e/9NM3WzSjdsAv4LdIFYQw==
MIME-Version: 1.0
X-Received: by 10.194.192.10 with SMTP id hc10mr32596870wjc.71.1464715588615; Tue, 31 May 2016 10:26:28 -0700 (PDT)
Received: by 10.194.153.39 with HTTP; Tue, 31 May 2016 10:26:28 -0700 (PDT)
X-Originating-IP: [192.149.252.11]
In-Reply-To: <49F8F126DD3A54640049E2F9@JcK-HP8200.jck.com>
References: <231532ef-e195-b73d-4a34-eb445bdd1900@gmx.de> <c19ff352-cd49-d664-9365-28898cff3050@gmx.de> <1F5D414703BF94503600A5E3@JcK-HP8200.jck.com> <CAAQiQRf0DYh-BuwRaEY6xLpQyNrxw55dFH=s+FRjVATkCM8HDQ@mail.gmail.com> <9dd1f7f1-843e-822b-a352-8b51d6f4192c@gmx.de> <0626757a-430e-4c25-07e0-efd04e92c377@seantek.com> <CAAQiQRdoOSKx26g3D-KEf-Mf8rQHf6Rm6jzR56wQHraLXrXMdg@mail.gmail.com> <dabb41d1-b4d0-8d44-eeb9-1c734ef06cd1@gmx.de> <49F8F126DD3A54640049E2F9@JcK-HP8200.jck.com>
Date: Tue, 31 May 2016 19:26:28 +0200
Message-ID: <CAAQiQRcVwn3oa5ktMp8A5CrpECik96Sm_2SS+ccXBvScipeCUg@mail.gmail.com>
From: Andrew Newton <andy@hxr.us>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/XZ28BQ9VglOqkavVYDVzWVwTBRI>
Cc: Julian Reschke <julian.reschke@gmx.de>, "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] Summary of WG decisions Re: Feedback on draft-ietf-urnbis-semantics-clarif-03
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 17:26:32 -0000

On Tue, May 31, 2016 at 5:48 PM, John C Klensin <john-ietf@jck.com> wrote:
>
>
> Just so you know (and to repeat what I've at least hinted at),
> I've been looking at  draft-ietf-urnbis-semantics-clarif since
> Julian's first posting on the issue to see if I could find thing
> that could reasonably be improved.  I've found several [1] and
> put new text into a working draft for -04 but have not posted it
> pending input and direction from the co-Chairs [2].
>

Yes, please publish it.

> I don't believe those changes will satisfy Julian's concerns.
> The reasons are connected to why I've been looking for
> instructions from the co-chairs and summarized in Andy's note.
> >From my point of view, this document updates 3986 _for URNs
> only_, it is not an attempt at a general update (that should
> have been quite clear from the first sentence of Section 4; -04
> will be even more clear on the subject).  In principle, we could
> do a paragraph by paragraph review of what portions of 3986 are
> affected by that, but it would be a lot of work, it would make
> this document longer and more complicated, and I don't believe
> that anyone would read it except for the purpose of finding
> things to quibble and pick nits about.  I see that as
> potentially a huge source of further delay and not particularly
> useful; if you disagree, please work with Andy to convince the
> WG.

Agreed.

>
> Similar comments apply to "whether it is needed".  Before the
> decisions that led, first to the "URNs are not URIs" proposal
> and then to this document, the WG spent seemingly-endless months
> bogged down in discussions about whether a particular mechanism
> or usage was consistent with, or permitted by, 3986.  For each
> case, some people argued that it was, others argued with equal
> passion, that it was not.  We were not converging on subjects
> that were arguably outside the WG's scope, such as whether 3986
> needed work or was clear enough.   While there are technical
> arguments having to do with differing layering abstractions that
> I believe justify the separation, my impression of the WG's
> conclusion was that we simply needed to separate ourselves from
> those arguments if we were to make progress.   So, if the
> question is "whether this is needed to make URN work proceed"
> the answer is that the WG decided "yes" and Section 2 of
> draft-ietf-urnbis-semantics-clarif (at least -02 and later) is
> intended to say that.  If the question were, instead, "can the
> WG prove to the satisfaction of all readers and interpreters of
> 3986 than it is impossible to develop a functional URN model
> that meets the needs of the communities the WG has identified
> without some separation from 3986", that answer to that question
> is probably "no", or at least "no within the level of energy
> that exists", but I hope the WG doesn't need to do that.
>

Again, agreed.

-andy