Re: [core] Disclosing Implementation Information: draft-bormann-t2trg-rel-impl-01.txt

[Jaime Jiménez <[e-mail]>]

Hi,

chair hat off. I find the draft very useful and easy to implement.
I'd expect that CoAP implementations out there can incorporate it quickly.
If there are other potential link-relations that are needed we might
want to bundle them in one document similar to RFC6903.

Ciao, Jaime

On Fri, Mar 27, 2020 at 05:13:19PM +0100, Carsten Bormann wrote:
> In 2018, we had a discussion about providing self-description information that tells a client something about the implementation (and version) of the server.  So I wrote a brief draft, and I seem to remember everybody nodded, but it wasn’t quite clear whether that was because they agreed or because they fell asleep.
> 
> By now, it has become more clear that disclosure of implementation information can be quite useful.  Actually, we already have RFC 8520 (MUD) for some very specific information of this kind.  A more free-form version still seems useful, and can use Web Linking (RFC 8288) and Link-Format (RFC 6690) so the specification itself is quite minimal.
> 
> So I have added some security considerations (pointing out, among other things, that this disclosure is not always desirable) and cleaned up the text a bit.  See links below.
> 
> Comments (+1, -1, or actual text) would be welcome, both from T2TRG and from CoRE.  It seems the CoRE working group might want to consider working group adoption of this draft or a next version, at which time it would transition from the RG context to the WG.
> 
> Grüße, Carsten
> 
> 
> > On 2020-03-27, at 16:58, [e-mail] wrote:
> > 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > 
> > 
> > Title           : impl-info: A link relation type for disclosing implementation information
> > Author          : Carsten Bormann
> > Filename        : draft-bormann-t2trg-rel-impl-01.txt
> > Pages           : 4
> > Date            : 2020-03-27
> > 
> > Abstract:
> >   For debugging, it is often helpful to have information about the
> >   implementation of a peer.  The present specification defines a link
> >   relation type, "impl-info", that can be used to convey such
> >   information via self-description, such as in the "/.well-known/core"
> >   resource.
> > 
> > 
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-bormann-t2trg-rel-impl/
> > 
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-bormann-t2trg-rel-impl-01
> > https://datatracker.ietf.org/doc/html/draft-bormann-t2trg-rel-impl-01
> > 
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-bormann-t2trg-rel-impl-01
> > 
> > 
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > 
> > _______________________________________________
> > I-D-Announce mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> _______________________________________________
> core mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/core