Re: [Taps] Fwd: Possible TAPS challenges

FWIW, #8 was raised when MPTCP was created - I pointed out that this system, like HTTP muxing, was doomed to needing to reinvent the whole of IP at the TCP layer (or HTTP layer, for HTTP muxing). That includes differentiated services. Joe On 3/21/2018 10:10 AM, Aaron Falk wrote: > > Mark Handley

Re: [Taps] I-D Action: draft-ietf-taps-minset-03.txt

Hi all, This is the tiny update that addresses the things we said we’d do before the draft could go to WGLC: We updated the sentence referencing the security draft [I-D.pauly-taps-transport-security] to say that "the minimum security requirements for a taps system are discussed in a separate se

Re: [Taps] IPv6 address usage

Hello, Erik, On 03/21/2018 05:47 PM, Erik Kline wrote: > On 21 March 2018 at 09:58, Fernando Gont wrote: >> Folks, >> >> Based on the feedback received today, I have split our document >> >> into this tw

[Taps] Fwd: Possible TAPS challenges

Mark Handley sent this thought provoking note after our meeting this morning. Some ideas here that stretch the architecture, I think. At least we need to consider extensibility of the API. Forwarding with permission. --aaron Forwarded message: From: Mark Handley To: Colin Perkins > , aa

[Taps] IPv6 address usage

Folks, Based on the feedback received today, I have split our document into this two documents: * Problem statement with respect to limitations of the Sockets API:

Re: [Taps] conflicting policies

for historical perspective, this is similar to the problem of "feature interaction" in old private phone exchanges 30 years back - its (in general) quite a hard problem if you can't just order all the preferences... On Wed, Mar 21, 2018 at 11:34 AM, Roni Even (A) wrote: > Hi, > > I made this com

[Taps] I-D Action: draft-ietf-taps-minset-03.txt

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

Re: [Taps] conflicting policies

Agreed that the implementations should not do “magical” or unexpected things. In the example question there are actually two elements at play: - How to rank preferences and policies at connection establishment time - How to treat path changes that may be disruptive to established connections For

Re: [Taps] conflicting policies

I personally think this is an important topic. The topic also appeared in the TAPS chartering, and my thoughts are currently: - I think we should ensure that the decisions made by TAPS systems are evident, at least in the logging. Implementations should not just provide "magic". - I'd expect

[Taps] New working group documents

At the TAPS wg meeting today, we discussed making several contributions to be working group documents. There was a strong consensus in the room to adopt all of these. If you weren’t in the room and have any objections to the working group developing these docs, this is the thread on which to

[Taps] Github repository for arch/interface/implementation drafts...

is https://github.com/taps-api/drafts. We're using the issue tracker at https://github.com/taps-api/drafts/issues; please feel free to add comments or file issues there. Cheers, Brian signature.asc Description: Message signed with OpenPGP ___ Taps m

Re: [Taps] Problem Statement Regarding IPv6 Address Usage (Fwd: New Version Notification for draft-gont-taps-address-usage-problem-statement-00.txt)

Fernando Just browsed today (at TAPS :-O ) your draft and interesting ;-) You may make clear in 7.1 (incoming connections) that there are some applications listening to a prefix, such as a /64 -éric On 28/02/18 12:29, "Taps on behalf of Fernando Gont" wrote: Folks, We have repos

[Taps] conflicting policies

Hi, I made this comment in the past in QUIC when discussing migration. One policy may be prefer wifi over cellular network, Second policy prefers quic cove TCP Now I walk into my house and my cellphone has HTTP over QUIC. At home will switch to wifi but quic is not supported on the wifi so will f