Re: [Taps] On Profiles for TAPS Preconnections

> On Jul 22, 2019, at 6:56 PM, Philipp S. Tiesel wrote: > > Hi, > >> On 22. Jul 2019, at 15:09, Tommy Pauly >> wrote: >> >> An issue we discussed today in the TAPS meeting was whether or not we should >> add a concept of "profiles" to the Transport Services APIs. An example of a >> profil

Re: [Taps] On Profiles for TAPS Preconnections

Hi, > On 22. Jul 2019, at 15:09, Tommy Pauly > wrote: > > An issue we discussed today in the TAPS meeting was whether or not we should > add a concept of "profiles" to the Transport Services APIs. An example of a > profile is a "reliable, secure, in-order stream"; or "unreliable datagrams".

Re: [Taps] Draft should point at existing implementations

Hi, I added a comment to this issue because I saw it on your slides, to explain: this isn’t really worth discussing. I meant it only as a “todo item” for myself and assigned it to me. I’ll do it when I do my planned next update on the implementation draft (which this is about). Sorry, I guess

[Taps] How to handle Protocol stacks that are not equivalent

Hi, as time did not permit to discuss all open issues in the session today, I’ll take them to the list as proposed. This issue is based on Github issue #305: https://github.com/ietf-tapswg/api-drafts/issues/305 Following the architecture draft, only protocol stacks that are equivalent can be s

[Taps] Implementation should separate out protocol-specific bits

Hi, as time did not permit to discuss all open issues in the session today, I’ll take them to the list as proposed. This issue is based on Github issue #248: https://github.com/ietf-tapswg/api-drafts/issues/248 The issue suggests to restructure the API to separate out protocol-specific bits.

[Taps] Draft should point at existing implementations

Hi, as time did not permit to discuss all open issues in the session today, I’ll take them to the list as proposed. This issue is based on Github issue #145: https://github.com/ietf-tapswg/api-drafts/issues/145 The issue ask for the drafts to point at existing TAPS implementations. It might be

[Taps] On Profiles for TAPS Preconnections

An issue we discussed today in the TAPS meeting was whether or not we should add a concept of "profiles" to the Transport Services APIs. An example of a profile is a "reliable, secure, in-order stream"; or "unreliable datagrams". Another way to think of these profiles are as convenient ways to i