hi Simone,

> On 05 Mar 2015, at 03:10, Simone Ferlin-Oliveira <fer...@simula.no> wrote:
> 
> Greetings,
> 
> Sections 3.2 and 3.3 in draft-03 remind us that there are
> commonalities between MPTCP (RFC6897) and SCTP APIs (RFC6458). They
> could be further summarised, perhaps in a dedicated session to
> “multi-path features”, abstracting what both protocols provide to
> applications. It could be, for example, inside section 4 as
> subsection.

Modulo Joe's comment that we shouldn't confuse "multi-path" (which is the 
goal...), "multi-endpoint" (...the abstraction we can use at the endpoints to 
try to meet the goal...), and "multi-interface" (...and the implementation of 
the abstraction) when defining a terminology here, this sounds good to me.

> If the group agrees with that, we would like to take it (Section 4) as
> contributors.

Thanks!

Cheers,

Brian

> Thanks,
> Simone Ferlin and Olivier Mehani
> 
> On 27 February 2015 at 23:58, Brian Trammell <i...@trammell.ch> wrote:
>> Greetings, all,
>> 
>> We've posted rev -03 of the taps-transports document; this includes a new 
>> Section 3.3. on SCTP by Michael Tuexen and a new section 3.4 on UDP by Kevin 
>> Fall; thanks Michael and Kevin!
>> 
>> Comments on the new sections or the structure thereof (i.e., as input to 
>> future transport protocol sections), or indeed on anything else in the 
>> document, are very welcome. :)
>> 
>> Thanks, cheers,
>> 
>> Brian
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-dra...@ietf.org
>>> To: "Gorry Fairhurst" <go...@erg.abdn.ac.uk>, "Mirja Kuehlewind" 
>>> <mirja.kuehlew...@tik.ee.ethz.ch>, "Brian Trammell" <i...@trammell.ch>, 
>>> "Mirja Kuehlewind" <mirja.kuehlew...@tik.ee.ethz.ch>, "Godred Fairhurst" 
>>> <go...@erg.abdn.ac.uk>, "Brian Trammell" <i...@trammell.ch>
>>> Subject: New Version Notification for draft-ietf-taps-transports-03.txt
>>> Date: 27 Feb 2015 13:52:23 CET
>>> 
>>> 
>>> A new version of I-D, draft-ietf-taps-transports-03.txt
>>> has been successfully submitted by Brian Trammell and posted to the
>>> IETF repository.
>>> 
>>> Name:         draft-ietf-taps-transports
>>> Revision:     03
>>> Title:                Services provided by IETF transport protocols and 
>>> congestion control mechanisms
>>> Document date:        2015-02-27
>>> Group:                taps
>>> Pages:                25
>>> URL:            
>>> http://www.ietf.org/internet-drafts/draft-ietf-taps-transports-03.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-taps-transports/
>>> Htmlized:       http://tools.ietf.org/html/draft-ietf-taps-transports-03
>>> Diff:           
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transports-03
>>> 
>>> Abstract:
>>>  This document describes services provided by existing IETF protocols
>>>  and congestion control mechanisms.  It is designed to help
>>>  application and network stack programmers and to inform the work of
>>>  the IETF TAPS Working Group.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>> 
>>> The IETF Secretariat
>>> 
>> 
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org
>> https://www.ietf.org/mailman/listinfo/taps
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

Reply via email to