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

[Christian Amsüss <[e-mail]>]

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
points.

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

BR
Christian

> 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