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

I don't know.
Could the contents of links-json not be combined with core-interfaces?

I can imagine that we have other documents defining the json contents 
for different management subjects

Peter van der stok

Rahman, Akbar schreef op 2013-05-21 05:50:
> +1
> 
> Akbar
> 
> FROM: core-bounces@ietf.org [mailto:core-bounces@ietf.org] ON BEHALF
> OF Andrew Mcgregor
> SENT: Monday, May 20, 2013 8:28 PM
> TO: core@ietf.org
> 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 | andrewmcgr@google.com | +61 4 8143 7128
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core