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

Carsten Bormann <cabo@tzi.org> Fri, 27 March 2020 16:13 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE123A0798 for <core@ietfa.amsl.com>; Fri, 27 Mar 2020 09:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVgQdLijdy03 for <core@ietfa.amsl.com>; Fri, 27 Mar 2020 09:13:29 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3FD33A0F6D for <core@ietf.org>; Fri, 27 Mar 2020 09:13:21 -0700 (PDT)
Received: from [192.168.217.119] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 48pn2m2Hbnzyt5; Fri, 27 Mar 2020 17:13:20 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <158532472527.24402.7156077840539978248@ietfa.amsl.com>
Date: Fri, 27 Mar 2020 17:13:19 +0100
X-Mao-Original-Outgoing-Id: 607018399.770457-3e61cd2d9b717545bcba2f847154a0e0
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1A0817E-8243-49A7-9CEA-BD38270C5028@tzi.org>
References: <158532472527.24402.7156077840539978248@ietfa.amsl.com>
To: t2trg@irtf.org, "core@ietf.org WG" <core@ietf.org>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/NypJowkL3atsNMF0or75DpTT5-w>
Subject: [core] Disclosing Implementation Information: draft-bormann-t2trg-rel-impl-01.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2020 16:13:42 -0000

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, internet-drafts@ietf.org 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
> I-D-Announce@ietf.org
> 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