Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt

Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com> Thu, 16 July 2015 11:33 UTC

From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <5b2e19f286a3eaf18d2ccf7da39abbbf@mail.gmail.com> <A6A77B18-C8F4-4C87-8493-8FF11AC98AA1@ifi.uio.no>
In-Reply-To: <A6A77B18-C8F4-4C87-8493-8FF11AC98AA1@ifi.uio.no>
MIME-Version: 1.0
Thread-Index: AQEc5Xz/B23yf9Eiv4yTBTpDy7OwEgJ6rVYLnzHT3XA=
Date: Thu, 16 Jul 2015 13:33:13 +0200
Message-ID: <4462808352bc6bde2e6d677d0d0e71e8@mail.gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/_hB4zwtocZrG9RxOOg9wJgjxS74>
Cc: Stein Gjessing <steing@ifi.uio.no>, taps@ietf.org
Subject: Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt
Precedence: list

HI,


>-----Original Message-----
>From: Michael Welzl [mailto:michawe@ifi.uio.no]
>Sent: Thursday, July 16, 2015 1:23 PM
>To: Karen Elisabeth Egede Nielsen
>Cc: taps@ietf.org; Stein Gjessing
>Subject: Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt
>
>Hi, thanks!
>
>Below:
>
>
>> On 16 Jul 2015, at 11:22, Karen Elisabeth Egede Nielsen
><karen.nielsen@tieto.com> wrote:
>>
>> HI,
>>
>> A few initial comments the definition of the transport service
>> features as they appear from section 3 (and TAPS1):
>>
>> Unidirectional/bidirectional: I am not sure what this means exactly:
>> Does it refer to that data transfer is negotiated for both directions
>> perhaps ? But then it only applies to connection oriented transport.
>> Does it refer to that control info is going back ?
>> Does it refer to that messages (which ever form) are going back on the
>> reverse network path ? Then it does not necessarily apply to SCTP MH.
>
>Sorry for not being clear enough: it means that it's a feature that can be
>used
>just on one side, without requiring the other side to be involved  (e.g.
>Nagle is
>just a sender-side mechanism).
>
[Karen ] Thanks. very precise. So we should call this single-sided or alike.
Not something that seems to have a direction or be related to how data
flows.
>
>>   o  non-reliable delivery:
>>       add SCTP
>>
>>   o  reliable delivery:
>>        add SCTP
>>
>>  Suggest to rephrase
>>
>>   o  reliable and partially reliable delivery
>> -->
>>   o  partially reliable delivery:
>>      SCTP
>>
>>   o  drop notification :
>>       add SCTP
>>
>>   o  ordered delivery:
>>       add SCTP
>>
>>   o  unordered delivery:
>>       add SCTP
>
>ACK, thanks
>
>
>> Ideally, I think, then one would use a common term for Nagle(-like)
>> bundling for TCP and SCTP.
>
>Agreed, we actually did that in Michael Welzl, Stefan Jörer, Stein
>Gjessing:
>"Towards a Protocol-Independent Internet Transport API", FutureNet IV
>workshop in conjunction with of IEEE ICC 2011, 5-9 June 2011, Kyoto, Japan,
>using app PDU bundling because it's more meaningful than Nagle.
>
[Karen ] Great.
>But here the idea was just to copy+paste the list from doc 1 (version 4)
>and
>put things under the correct headings, as a way to show how we *could*
>apply categorization methods.
>
[Karen ] Yes I understand that. But the write-up serves very well to help
unify and clarify the terms - which I suppose is the goal :-).

BR, Karen

>Cheers,
>Michael

Re: [Taps] Comments on draft-gjessing-taps-minset… Karen Elisabeth Egede Nielsen
Re: [Taps] Comments on draft-gjessing-taps-minset… Michael Welzl
Re: [Taps] Comments on draft-gjessing-taps-minset… Karen Elisabeth Egede Nielsen
Re: [Taps] Comments on draft-gjessing-taps-minset… Brian Trammell
Re: [Taps] Comments on draft-gjessing-taps-minset… Michael Welzl