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

[Michael Koster <[e-mail]>]

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?

Best regards,

Michael

> On Jul 17, 2018, at 5:04 PM, Peter Saint-Andre <[e-mail]> 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 <[e-mail]> 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
>>> 
>>> 
>> 
>