Re: [urn] URI Scheme with Complex Equality Rules
Ted Hardie <ted.ietf@gmail.com> Fri, 26 August 2022 13:08 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 20BDAC14CF05 for <urn@ietfa.amsl.com>; Fri, 26 Aug 2022 06:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ot18TQSARnjx for <urn@ietfa.amsl.com>; Fri, 26 Aug 2022 06:08: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 07949C14F73B for <urn@ietf.org>; Fri, 26 Aug 2022 06:08:02 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id h8so780244ili.11 for <urn@ietf.org>; Fri, 26 Aug 2022 06:08:01 -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=lpbyzsGB4qF5thRMD6NsBGRCwtm5W1Be6uFaOUt050E=; b=SDXwkRARwu3OyoX9Dv+JbgNdSbJzIEguQd7iZp+BaQAPf+dWcgQoudUyucdjI9QP+L 0Xk3qPLQahuQ1FuoXnzBkXcu7oAQYzRjwKt5mRMBi43fObI33bhPCb4Ely2ZE+iJRrkp /D0oZzc3XbXwyWeaTb30X1rxwJIbewOEDQ22M4mgS8i7Krv/T9tp4uzDLuEUyunE8n3B CBbtqmlBWbhmDp5GjLyklY7CoiMxVSzIxoKABLHgN/Dah6uYsMtUEu9B6YvBHGe2xUBr jdqWk/FVFXj1iSHsPI1NjmEiTL5y4v16wxYhIefJNxY3C4piYJ+hQKM0MCU6pRLeSdNE /2Gw==
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=lpbyzsGB4qF5thRMD6NsBGRCwtm5W1Be6uFaOUt050E=; b=OdEtUPyiz5AVIq2/qhKsMxfznlBng3WdVM6/eiL3mwh1gCWwLWfeb88Vu854R3OxBq 9dMftkOfnNrWQ1XZPz7+6moY6R3RE4ptAt9z+aTzcoSloKzFrGizpf41tb2H7DXr140X 5CjFlyKRMo4JaBP/VUf3j3RxaD2QMsYHctO2BrVp3AP0ug/ymxk1KUYFUYJNIPglAOiD sgY3v7g8QT4Vg05vI1Wr6k9AON27oIn+y1t1zeNUhnV44Mg4uqywO5iL3EUePN/7WVf7 Le7oKn3PlmW4phmLgWPiKP79e+8sfstdKe9c43jD/PfmLrcnJCp98odUHRijORfvf8Qw GSkw==
X-Gm-Message-State: ACgBeo1okWMc6IxdDcR1VCVNYA1nhhvlogt3dYr3PvWIiGgDQh5tGvJb DSy7YTwkmvvJVVfM9bMk2WIs3QdY4aSdjYNbgHFJ3haafTjyzw==
X-Google-Smtp-Source: AA6agR6FHYWiU1c3YCoMlgp9ze1dssKtKMDVhCPEIyF6C/wukO3AqeJ5frYH7sPp8UjNej7k151Bgmt0sL9dXmtBBjE=
X-Received: by 2002:a05:6e02:547:b0:2e9:1e0f:5172 with SMTP id i7-20020a056e02054700b002e91e0f5172mr3875575ils.225.1661519281269; Fri, 26 Aug 2022 06:08:01 -0700 (PDT)
MIME-Version: 1.0
References: <SJ0PR08MB8288507205BE2CD811F5D19BFA759@SJ0PR08MB8288.namprd08.prod.outlook.com>
In-Reply-To: <SJ0PR08MB8288507205BE2CD811F5D19BFA759@SJ0PR08MB8288.namprd08.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 26 Aug 2022 14:07:34 +0100
Message-ID: <CA+9kkMBbeHRn+pQEO4v90d0ifCaxEZW7FU2QRUtgD8oiuD0JKg@mail.gmail.com>
To: "Randy Armstrong (OPC)" <randy.armstrong@opcfoundation.org>
Cc: "urn@ietf.org" <urn@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c30db05e7249aee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/6gwcW3Z1Lb5BTza6x-GoHV9555c>
Subject: Re: [urn] 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: Fri, 26 Aug 2022 13:08:06 -0000
Hi Randy, Based on a skim of your use case, I can't yet see why minting a URI scheme would not work. opcid://authority/parameters The authority here would be the DNS name or IP address, and the definition of the scheme could establish that you wanted case insensitive matching for the parameters (where the context would be stored). Is there something in IEC 62541 that would make this approach unviable? I admit that I did not spend any francs to get it, so I don't have examples of what the context might look like, so if you have examples you can share, that would be useful. Note that while URNs are guaranteed to be unique across the lifetime of an identifier, your scheme doesn't seem likely to want that, as it is relying on the DNS and IP address assignment, neither of which guarantees that property. regards, Ted On Fri, Aug 26, 2022 at 1:47 PM Randy Armstrong (OPC) < randy.armstrong@opcfoundation.org> wrote: > I am sending this issue to this email as per the suggestion in RFC 8141. > > > > The OPC Foundation (https://opcfoundation.org) has a need to uniquely > identify OPC UA (IEC 62541) network resources but we do not want the > complexity that comes with the various URN schemes. > > > > Specifically we need: > > > > 1. Equality checks with case-insensitive string comparisons; > 2. Human readable strings with uniqueness provided by a DNS name or IP > address (always lower case). > 3. A valid URI. > 4. R/Q/F components not allowed. > > > > We have been using urns of the form: urn:<dnsname>:<additional context>, > however, this is not technically allowed by the URN RFC. > > We do not want a syntax that needs to be parsed before any comparison can > be done. > > > > We could submit a request for our own nid but we don’t really have any > syntax requirements other than the dns name and the case-insensitive string > comparisons. > > > > What is the best way forward? > > > > Regards, > > > > Randy Armstrong > > OPC Foundation > > > > > > > > > > > _______________________________________________ > urn mailing list > urn@ietf.org > https://www.ietf.org/mailman/listinfo/urn >
- [urn] URI Scheme with Complex Equality Rules Randy Armstrong (OPC)
- Re: [urn] URI Scheme with Complex Equality Rules Ted Hardie
- Re: [urn] URI Scheme with Complex Equality Rules Randy Armstrong (OPC)
- Re: [urn] URI Scheme with Complex Equality Rules Ted Hardie
- [urn] How to tell the difference (was: Re: URI Sc… John C Klensin
- Re: [urn] URI Scheme with Complex Equality Rules Randy Armstrong (OPC)
- Re: [urn] URI Scheme with Complex Equality Rules worley
- Re: [urn] URI Scheme with Complex Equality Rules Randy Armstrong (OPC)
- Re: [urn] How to tell the difference (was: Re: UR… Ted Hardie
- Re: [urn] URI Scheme with Complex Equality Rules Peter Saint-Andre