Hi Michael,
>
>Okay, it seems we're all on the same page. My heavy reaction to the email
>before (and sorry Karen, I had forgotten why you sent it! Indeed that was
>agreed upon at the last meeting) was because I'm afraid of the logical
>conclusion:
>"this is what applications currently configure
gede Nielsen
>> Cc: Michael Welzl; taps WG
>> Subject: Re: [Taps] API richness
>>
>> Hi Karen,
>>
>> instead of discussing what applications currently configure, I would rather
>> like
>> to know why they configure it; what the goal they try to reach and
HI Mirja,
>-Original Message-
>From: Mirja Kühlewind [mailto:mirja.kuehlew...@tik.ee.ethz.ch]
>Sent: Friday, May 29, 2015 10:13 AM
>To: Karen Elisabeth Egede Nielsen
>Cc: Michael Welzl; taps WG
>Subject: Re: [Taps] API richness
>
>Hi Karen,
>
>instead o
is.
>
> With CC tuning, I meant control which CC algorithm to choose.
>
> BR, Karen
>
>> -Original Message-
>> From: Michael Welzl [mailto:mich...@ifi.uio.no]
>> Sent: Thursday, May 28, 2015 9:39 PM
>> To: Karen Elisabeth Egede Nielsen
>> Cc:
Message-
>From: Michael Welzl [mailto:mich...@ifi.uio.no]
>Sent: Thursday, May 28, 2015 9:39 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: Aaron Falk; taps@ietf.org
>Subject: Re: [Taps] API richness
>
>
>> On 27. mai 2015, at 08.22, Karen Elisabeth Egede Nielsen
> wrote:
>
> On 27. mai 2015, at 08.22, Karen Elisabeth Egede Nielsen
> wrote:
>
> HI,
>
> As an example of presently relied on API richness, then the following
> parameters of TCP/SCTP are parameters that today typically are tuned by
> signaling applications on a per connection/association basis or an a
HI,
As an example of presently relied on API richness, then the following
parameters of TCP/SCTP are parameters that today typically are tuned by
signaling applications on a per connection/association basis or an a per
signaling application basis. Here multiple signaling applications may share
the
