Re: Registration request for urn:thread:

> My opinion is "No", unless it's agreed that *all* non-members are
> licensed to see, copy, and discuss it in any forum.  

What we could also do is state "None" for the Documentation field, which would cover the case that nothing is publicly available. This was e.g. done in the CTA assignment:
https://www.iana.org/assignments/urn-formal/cta
And cdx has a similar solution: https://www.iana.org/assignments/urn-formal/cdx  (the linked website has public info, but no URN details)

This approach would require, I believe, that the "Syntax" section defines the URN syntax in sufficient detail (including sub-namespaces concept).
Or, if a separate document is required for our particular case then we could produce one as an IETF I-D later on.

thanks
Esko

-----Original Message-----
From: Dale R. Worley <[email protected]> 
Sent: Thursday, January 25, 2024 19:41
To: Esko Dijk <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [urn] Registration request for urn:thread:

Esko Dijk <[email protected]> writes:
>> This text says "published" but the page at the URL only allows access
>> under NDA.
>
> Right, the "internal use only" in the EULA seems to prohibit public
> discussion on content or quoting.  Could we say "made available by
> Thread Group to members and non-member licensees"?

My opinion is "No", unless it's agreed that *all* non-members are
licensed to see, copy, and discuss it in any forum.  See, e.g.,

    https://www.ietf.org/about/introduction/
    Introduction to the IETF
    Mission

    The IETF wants the Internet to be useful for communities that share our
    commitment to openness and fairness.

    https://www.ietf.org/about/open-records/
    Open records

    The IETF operates in an open and transparent fashion and we publish open
    records of most of the contributions, submissions, statements, and
    communications that we receive.

    https://www.ietf.org/privacy-statement/
    IETF/IRTF/IAB Privacy Statement
    Our Commitment to Transparency

    The IETF/IRTF/IAB operates in an open and transparent fashion. As a part
    of this transparency, any contributions, submissions, statements or
    communications that you make to any Party including any Personal Data,
    other than as expressly excepted in this statement, will be made public
    through electronic and other means.

Having a URN namespace whose fundamental rules and structure is trade
secret is contrary to the spirit of the IETF.

> For the sub-namespaces we can define the syntax & semantics already
> now in the request doc; so that part at least is public.
>
> For the email addresses: if personal addresses are not preferred, we
> could also list a single role address help&threadgroup.org which can
> forward technical questions to the right people. Is this preferrable?

It's definitely an improvement, as "help@..." is likely to remain valid
for longer than personal addresses.  OTOH, you may want to define a
separate "technical role" address "technical@..." and for the time
being, just forward it to "help@...", or even the two individuals you've
listed.

Dale