Re: [urn] How to tell the difference (was: Re: URI Scheme with Complex Equality Rules)

Ted Hardie <ted.ietf@gmail.com> Mon, 29 August 2022 08:42 UTC

Return-Path: <ted.ietf@gmail.com>
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 96C6EC1524CB for <urn@ietfa.amsl.com>; Mon, 29 Aug 2022 01:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWS3tHD-iZzc for <urn@ietfa.amsl.com>; Mon, 29 Aug 2022 01:42:02 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D68FC1524BC for <urn@ietf.org>; Mon, 29 Aug 2022 01:42:02 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id l16so3861539ilj.2 for <urn@ietf.org>; Mon, 29 Aug 2022 01:42:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=9qTnr7GCOzrHjA2rncbAfBT1eEXpmzzTuyYj5qJnNS4=; b=qMEcEoz7VN8VAVGK1yCCeGWmGnOxAfmZe0niHNnCInyrj+Zwojqtd4CYyraOFd5OJe TUOBqmyz7Y1BCinhcEstCTkPplMTdF9LeJI45oWWhVKgxSwsCSnjzMQizLvExFAHqe0Z srGq3LF14JDSkfrg9cNmeqTiZYTdPE4ZKDMHHq53rvo0Ja7u6CDE2409dMahqhNx1gXg BmFf2ylSN/j6Y5IUYw30ndqaoUK4+D5VvQZCsPuDK+slSUGbyjss1PseFP/7F8C696DO /p7OBvhgtdFl6Uiiuzg2xnuDxiVtdCn52zT/Y3UIvYTdrTOOxdhHYgs+md/6Hpi9Bj0t 3bhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=9qTnr7GCOzrHjA2rncbAfBT1eEXpmzzTuyYj5qJnNS4=; b=xNLCDbiTuySMcx30Z/60YZE6PaDUBpaejB/UQ5TNfdY1uKnjmHgdu48/Veeu3LKfKR 6rgYDBd5g0iMYLHqwVkXJeTX13o2CPreyRVM/AnATIwdX3/JI6TqFk2DMbY+qswJ/jKG EVqfnjlkTcWicbtXkEt0m1jF4zHODXCFk4istXrHhqx2Z2xvqtqzhZ6eV1DLcCeJZZBt zDqedSkk5yFMeKwtSDkOascaVD48euAFFSt6ANdd3dTLtgYipo3ZX3go7pvdBv20foaY YfU0BoQXm0qJ2Mn1yrjImvO95W9BwKJUyK3XpLMgkv93meYdmZK2gExUBOJ9ObrBvPxk uR5g==
X-Gm-Message-State: ACgBeo3CQzKEzn8PQ/kfBFWJpgGGhcxcFxP/I3CW+TTGtClDPstYz1IZ oYlnEzEx0Vunqe7vnxyQeZoH7ojK7LBuOBJzugs=
X-Google-Smtp-Source: AA6agR5OaGdQC4kf2dYk8zq/kOZqFV9oDYcQcnpN7XYEstixa9zg00la+Kg/9BESFbisr67DjQAkII0sqysOY0zX6oM=
X-Received: by 2002:a05:6e02:1bef:b0:2e5:9ce2:23d0 with SMTP id y15-20020a056e021bef00b002e59ce223d0mr9117590ilv.93.1661762520111; Mon, 29 Aug 2022 01:42:00 -0700 (PDT)
MIME-Version: 1.0
References: <SJ0PR08MB8288507205BE2CD811F5D19BFA759@SJ0PR08MB8288.namprd08.prod.outlook.com> <SJ0PR08MB82881C9645C9F215BBB5CB03FA759@SJ0PR08MB8288.namprd08.prod.outlook.com> <CA+9kkMAvRv4845YOVHsKY6LDo5CFC0KdL=j3WF334v==nj4oTQ@mail.gmail.com> <DF50255DFCF385789EB9451E@PSB>
In-Reply-To: <DF50255DFCF385789EB9451E@PSB>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 29 Aug 2022 09:41:34 +0100
Message-ID: <CA+9kkMBo7u7nHhfJWYLZpJj4_Y2-f8KhOi_JZJ1gU8x=T5QZ4g@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: urn@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b65eb505e75d3c14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/JknEVw62Hc-IhYpdreloBRYY2sY>
Subject: Re: [urn] How to tell the difference (was: Re: URI Scheme with Complex Equality Rules)
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 29 Aug 2022 08:42:02 -0000

Hi John,

I think most of the cases where the choice is at issue depend on context,
some of which would be hard to generalize.  Things like:

Do you need folks to be able to tell by inspection/parsing what permanence
guarantees you're providing?

Do you need to reuse protocol slots which expect specific forms?

are common questions for the case where a potential non-URN URI expects to
provide similar permanence guarantees.  But once you have the answers the
conversation is a good bit more contextual, and I'm not sure how much value
generalized guidance would be.

Just my general impression, though, and I certainly don't object to someone
writing that up if they feel differently.

regards,

Ted

On Fri, Aug 26, 2022 at 6:40 PM John C Klensin <john-ietf@jck.com> wrote:

>
> Ted,
>
> Reading through this discussion caused me to realize that, while
> there are some obvious cases in both directions, there are many
> situations in which the choice between a new URN NID and a new
> URI scheme is not obvious. You've obviously got some intuition
> about that.  So do I and, while I assume ours are very similar,
> I am guessing there are edge cases on which we might not
> completely agree. Should we be trying to get some guidance on
> the subject together and written down?   Or is that likely to be
> hard enough that we are better off with case-by-case analyses
> and advice?
>
> best,
>    john
>
>
> --On Friday, August 26, 2022 17:58 +0100 Ted Hardie
> <ted.ietf@gmail.com> wrote:
>
> > Hi Randy,
> >
> >
> > On Fri, Aug 26, 2022 at 3:18 PM Randy Armstrong (OPC) <
> > randy.armstrong@opcfoundation.org> wrote:
> >
> >> Hi Ted,
> >>
> >>
> >>
> >> Thanks for the reply.
> >>
> >> I was thinking of a URI scheme instead of a URN NID, however,
> >> it appears URI scheme requires that we create RFC which is a
> >> much more cumbersome process.
> >>....
>
>
>