Hi,
In line:
> On Nov 14, 2017, at 8:20 AM, Tommy Pauly wrote:
>
> A couple initial comments on the minset document:
>
> In Section 4:
>
> - Title should be "4. A MinSet Abstract Interface" not "4. An MinSet
> Abstract Interface”
Ack,
> For this:
>
> 3. Not offer any of the transport
On Tue, Nov 14, 2017 at 8:20 AM, Tommy Pauly wrote:
> TLS:
>
> We can discuss in the group, but I think that security can stay a separate
> document for now. You wouldn't "fall back" to TLS—TLS is just something you
> can use underneath the TAPS API, and you either have security or you don't.
> Th
A couple initial comments on the minset document:
In Section 4:
- Title should be "4. A MinSet Abstract Interface" not "4. An MinSet Abstract
Interface"
For this:
3. Not offer any of the transport features of these protocols and
the LEDBAT congestion control mechanism that do not req
Hi everyone,
This update addresses 2 out of 3 major comments that we got at the last meeting:
1) also fall-back to UDP => done. This turned out to be much easier than I
thought because the set of transport features for which TCP is a possible
fall-back is, with *one* exception (receiving a me
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Services WG of the IETF.
Title : A Minimal Set of Transport Services for TAPS Systems
Authors : Michael Welzl
Stei
