Re: [core] draft-bormann-core-links-json: call for adoption

["Kovatsch Matthias" <[e-mail]>]

+1

I think this is useful for building larger "Cloud services" around constrained devices and M2M applications. I do not see a direct connection to core-interfaces, though.

In Orlando Carsten recalled the original incentive for writing up this format. Unfortunately, the minutes etherpad keeps resetting my connection attempts and I cannot recall the outcome. Anyone can? :)

Ciao
Matthias


From: [e-mail] [mailto:[e-mail]] On Behalf Of Andrew Mcgregor
Sent: Tuesday, May 21, 2013 2:28
To: [e-mail]
Subject: [core] draft-bormann-core-links-json: call for adoption

Consensus of the room in Orlando was to adopt draft-bormann-core-links-json as a working group document.  This email is a call for confirmation of that consensus.  Please respond if you support the adoption of this document.

>From the charter:

    5) A definition of how to use CoAP to advertise about or query for a
    Device's description. This description may include the device name and
    a list of its Resources, each with a URL, an interface description URI
    (pointing e.g. to a Web Application Description Language (WADL)
    document) and an optional name or identifier. The name taxonomy used
    for this description will be consistent with other IETF work,
    e.g. draft-cheshire-dnsext-dns-sd.

This is for making the resource discovery information available to backends.  On a technical level, this is a no-brainer.

* May 2013 Submission to IESG of "Representing CoRE Link Collections
  in JSON" for Proposed Standard

--
Andrew McGregor | SRE | [e-mail]<mailto:[e-mail]> | [phone]