IETF Logo Mail Archive

Re: [core] Link-format to DNS-SD mapping: URI rt values

Peter Saint-Andre <stpeter@mozilla.com> Wed, 18 July 2018 00:13 UTC

Return-Path: <stpeter@mozilla.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13403130E8C for <core@ietfa.amsl.com>; Tue, 17 Jul 2018 17:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 W3TfxpKsv2wu for <core@ietfa.amsl.com>; Tue, 17 Jul 2018 17:13:05 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 B396F130E91 for <core@ietf.org>; Tue, 17 Jul 2018 17:13:05 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id l14-v6so2563530iob.7 for <core@ietf.org>; Tue, 17 Jul 2018 17:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R2PhTdrJrEGTFVFW4XVaPdz2Eu7A0QIKLQm5HzjzJrs=; b=U7FqV3U3tRMZ0JjoGM131I/DJsUf3ajdYH2ziIo5F+oDWmALkHzQXsxt9JtKRe5JGg /Z2uR1JTcSDAVlx5G/F/zoqT2mPLXOJdNWZ7hXRGTdDg2tnzTA7vwo/IVmLZzPwrRh9C gtLtabkQefS+FLNNXvhXoCx6GFEjv7QqvVZug=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R2PhTdrJrEGTFVFW4XVaPdz2Eu7A0QIKLQm5HzjzJrs=; b=X1rEaQgg6Xjl/vHiLwmRjf9KwUIQnjRGbBOc+oXqwEjZmeFSaCgckQDxHMKnkwtz+a eHDonyyLzCrWmimzZDngqtLxwq0CSvRzmPvQ3zNpGbRXEDsNFg2BmGi4DRnzYHT15IWw Ye9CtXsiz/TJxr9z0sWTT1aPDhine921zJYVPxWBW4csTgrOsFB0NdxoUxbCkL1O6E6y j5qAR+iIAbBDJVXmyPjJzxU7O/C9QB3eAKencen8lsORwhp6iPTpb2xxNzNl2afVKAyP oquxPLqKJJJXYne0KlFjcdHx+b7hYV7IJKnn0aaDaFQmpSYvcxX51d62AdWVnyWQf2Vk iuew==
X-Gm-Message-State: AOUpUlHRvzCvEZBAP9TEEcSTPHmNltDGTXtgBcIbGfl5+X8pS1mbD8QY 3AI8F/JPbcj2a9G6YMkPDn3qdFXyqVI=
X-Google-Smtp-Source: AA+uWPzqmV8g+UM1YSiNlki4dG32tNZllrzcaKaEQbKUXy4R2VMKNBU+QLxy/3OJ+6KyO0nwaS0wpQ==
X-Received: by 2002:a5e:dc49:: with SMTP id s9-v6mr3237655iop.237.1531872784878; Tue, 17 Jul 2018 17:13:04 -0700 (PDT)
Received: from [192.168.1.10] ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id z22-v6sm1090962iog.63.2018.07.17.17.13.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 17:13:04 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Peter Saint-Andre <stpeter@mozilla.com>
X-Mailer: iPhone Mail (15F79)
In-Reply-To: <18410D8B-9683-488B-A4CC-CDB737206256@gmail.com>
Date: Tue, 17 Jul 2018 18:13:03 -0600
Cc: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>, "core@ietf.org" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A18983BC-5CB7-44BC-9F71-6A4DC805B3AA@mozilla.com>
References: <DM5PR2101MB0805A11EFC50C8329FD31FECA35D0@DM5PR2101MB0805.namprd21.prod.outlook.com> <132BF0EA-F284-4857-BE93-2A04608D828A@gmail.com> <db98effa-398c-a1e0-f6d1-8732c6e99e0e@mozilla.com> <D79DD063-F6B4-4995-9FBB-266976EA7E6F@gmail.com> <56f4ed81-5f87-86d9-5acc-f7864a788f06@mozilla.com> <18410D8B-9683-488B-A4CC-CDB737206256@gmail.com>
To: Michael Koster <michaeljohnkoster@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/aj2neIxuY22WhLzdPigVWnrmCaY>
Subject: Re: [core] Link-format to DNS-SD mapping: URI rt values
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2018 00:13:08 -0000

> On Jul 17, 2018, at 5:21 PM, Michael Koster <michaeljohnkoster@gmail.com> wrote:
> 
> Thanks, Peter,
> 
> For future reference, how should one format URN examples, in messages and drafts, so as not to imply that they are being freely minted?

It’s best to use the urn:example namespace from RFC 6963.

Peter

> 
> Best regards,
> 
> Michael
> 
>> On Jul 17, 2018, at 5:04 PM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>> 
>> On 7/17/18 2:55 PM, Michael Koster wrote:
>>> Yes obviously... My example assumes that one has a URN namespace. 
>>> 
>>> Is that an unreasonabe assumption?
>> 
>> Well, it depends on what kind of organizations we're talking about. When
>> I worked at Cisco, I saw developers creating urn:cisco:foo URNs and you
>> can't just mint your namespaces, so that was bad.
>> 
>>> Many of the organizations I work with have or plan to have URN namespaces.
>> 
>> Excellent. Please point them to RFC 8141 for the updated definition of
>> URNs and the updated registration process for URN namespaces... :-)
>> 
>> https://tools.ietf.org/html/rfc8141
>> 
>> Peter
>> 
>> (team lead, URN namespace expert review team)
>> 
>> 
>> 
>>> 
>>> Best regards,
>>> 
>>> Michael
>>> 
>>>> On Jul 17, 2018, at 4:31 PM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>>>> 
>>>> On 7/16/18 3:30 PM, Michael Koster wrote:
>>>>> Or the URN form may also be used, e.g. "rt=urn:myorg:sensor:temperature" which can enable an organization to manage its own namespace
>>>> 
>>>> Don't do that. You can't just create your own URN namespaces:
>>>> 
>>>> https://tools.ietf.org/html/rfc8141#section-5
>>>> 
>>>> It's better to use URIs with the domain name of your organization, or
>>>> use the urn:example namespace:
>>>> 
>>>> https://tools.ietf.org/html/rfc6963
>>>> 
>>>> Peter
>>>> 
>>>> 
>>> 
>> 
>

v2.23.0 | Report a Bug | By Email