[core] New version of draft-amsuess-core-transport-indication

Christian Amsüss <christian@amsuess.com> Sat, 10 July 2021 19:16 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5FB773A19AC for <core@ietfa.amsl.com>; Sat, 10 Jul 2021 12:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M2PE9fyR1w2a for <core@ietfa.amsl.com>; Sat, 10 Jul 2021 12:16:28 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EF743A196D for <core@ietf.org>; Sat, 10 Jul 2021 12:16:27 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 789504016F for <core@ietf.org>; Sat, 10 Jul 2021 21:16:22 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 3EA28D0 for <core@ietf.org>; Sat, 10 Jul 2021 21:16:21 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:c62a:3c72:f391:2b9b]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id F1509101 for <core@ietf.org>; Sat, 10 Jul 2021 21:16:20 +0200 (CEST)
Received: (nullmailer pid 521234 invoked by uid 1000); Sat, 10 Jul 2021 19:16:20 -0000
Date: Sat, 10 Jul 2021 21:16:20 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: core@ietf.org
Message-ID: <YOnyBHFJ7QSYhJUy@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/B0jFqr4PUQbU7c8"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/IU4rPUTJiU0k73fTZRFfFK5mirM>
Subject: [core] New version of draft-amsuess-core-transport-indication
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: Sat, 10 Jul 2021 19:16:33 -0000

Hello CoRE,

I've submitted a new version of transport-indication, which sets out to
be a solution to the different-protocols situation we're having.

Please have a look at the document, which should be pretty
self-explanatory by now and includes several remarks on contentiuous

Feedback on-list before the IETF would be much appreciated; at latest, I
hope to get a chance to discuss this during the session.


> Date: Sat, 10 Jul 2021 12:07:38 -0700
> Name:		draft-amsuess-core-transport-indication
> Revision:	01
> Title:		CoAP Protocol Indication
> Document date:	2021-07-10
> Group:		Individual Submission
> Pages:		20
> URL:            https://www.ietf.org/archive/id/draft-amsuess-core-transport-indication-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-amsuess-core-transport-indication/
> Html:           https://www.ietf.org/archive/id/draft-amsuess-core-transport-indication-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-amsuess-core-transport-indication
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-amsuess-core-transport-indication-01
> Abstract:
>    The Constrained Application Protocol (CoAP, [RFC7252]) is available
>    over different transports (UDP, DTLS, TCP, TLS, WebSockets), but
>    lacks a way to unify these addresses.  This document provides
>    terminology based on Web Linking [RFC8288] to express alternative
>    transports available to a device, and to optimize exchanges using
>    these.

To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom