Re: [Taps] Fwd: New Version Notification for draft-grinnemo-taps-he-02.txt

Hi, all, Some observations: - HE-trans MUST NOT be used to try different combinations of options within a given transport - I'm wondering about the potential for problems when ports are reused between different attempts, e.g., IPv6-TCP then IPv4-TCP - the document works only for

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

> On 21 Mar 2017, at 09:06, Yoshifumi Nishida wrote: > > On Thu, Mar 9, 2017 at 7:43 AM, Michael Welzl wrote: > > > On Mar 8, 2017, at 9:36 AM, Michael Welzl wrote: > > > > Dear all, > > > > This is a quite major update: from

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

On Thu, Mar 9, 2017 at 7:43 AM, Michael Welzl wrote: > > > On Mar 8, 2017, at 9:36 AM, Michael Welzl wrote: > > > > Dear all, > > > > This is a quite major update: from our (author's) point of view, it now > (at last!) captures all the RFC-defined API

Re: [Taps] New Version Notification for draft-gjessing-taps-minset-04.txt

Hi everyone, With one week having passed since this posting, and one week to go until the meeting, I thought I'd send a reminder - folks, please consider taking a look at this. For a fast way of reading this: - keep in mind that we removed all transport features that either don't require