[Interop-dev] NetJSON DNS-SD service name & registry

[Nemesis]

Hi everyone,

while discussing NetJSON in the (spam-protected) mailing list, Barbara Stark
sent two very good suggestions, I paste that passage below

On 04/14/2016 06:20 PM, STARK, BARBARA H wrote:
>
> I looked over the stuff at the netjson website and think it's great.
I've been thinking we need something like this for several years now and
kept meaning to try to get something started (but always got
side-tracked). I'm thrilled to see that someone has done all this work
and really like the quality and readability of the spec, and high-level
design choices that have been made. I'll be looking the spec over in
more detail to see if I can provide meaningful feedback.
>
> Some additional items I'd like to explore are:
>  - Define/register a service name
(http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml)
that can be used by devices wanting to advertise/discover (DNS-SD) URLs
where such info is exposed via an HTTP API.
>  - Better define processes that would allow other orgs to extend. I
see the custom members registry, but think a little more definition is
needed. I'm wondering if it might be possible to define some syntax to
make it easy for orgs with formal registered namespace
(http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml) to
extend. Or define more formal processes.
>
> _______________________________________________
> babel mailing list
> (spam-protected)
> https://www.ietf.org/mailman/listinfo/babel


Below she gave me other suggestions regarding the service name and
DNS-SD discovery, which I'm forwarding to you all with her permission.

Read below and let me know what you think.
In the meanwhile I'm working to improve the website and I will try to
address the registry of extensions, although I believe more iterations
will be needed to get it in a way that is easy to add extensions and
easy to understand how these extensions are being used.

Federico

-------- Forwarded Message --------
Subject: RE: [babel] NetJSON DNS-SD service name
Date: Wed, 20 Apr 2016 12:30:53 +0000
From: STARK, BARBARA H <(spam-protected)>
To: Nemesis <(spam-protected)>

I took the babel list off this response, just in case they aren't
interested.

> There's a crucial question I have for you, Barbara: when do you think it's the
> right time to start this process? After draft 0 is published to the IETF? Before?
> On subsequent drafts (like draft 1 or 2)?

I think it can be done whenever you like, and is independent. Requesting
a new service name can be done by anybody using the form at
http://www.iana.org/form/ports-services. Service names like this are
handed out to whoever asks for them without requiring expert review or
drafts such.
It just needs someone to provide contact info. And the supported TXT
should be provided. For NetJSON info that can be requested by HTTP GET,
I think all you need is a path. Defined TXT keys: path=<path to document>

It might be good to then add a brief section somewhere in the draft on:
Exposing NetJSON
NetJSON does not aim to define how the data is exchanged, it could be
exposed via an HTTP API, it could be sent through UDP packets, it could
be copied from application A and pasted into application B. However, the
Service Name [PROTSERVREG] "<registered service name here>" has been
registered to provide at least one well-defined means of using DNS-SD
[RFC6763] to advertise and discover NetJSON information that can be
requested using HTTP GET.

Add to Informative References
   [PROTSERVREG]     Internet Assigned Numbers Authority (IANA),
                     "Protocol and Service Names Registry",

<http://www.iana.org/assignments/service-names-port-numbers>.
  [RFC6763]

Barbara