Hi Simone,
thanks for this offer. The idea of this document is to first describe all
existing protocols separately and then based on these descriptions detect common
transport service features. And, this might be again a terminology issues, this
is not about the API that is exposed to the higher layer but rather about the
actual feature that are implemented below.
I see this the following way: the reason for writing this document is not that
someone can later read a nice summary about existing IETF (transport) protocol
but it about the group doing the exercise to make sure that we don't missing
something just because we all believe we are expert anyway...
Having said this, I'd like to first see a complete section (3.2) on MPTCP before
we start to writing something on this in section 4. However, I'm sure you could
also help to provide some text in section 3.2...? That would be great!
Mirja
On 05.03.2015 03:10, Simone Ferlin-Oliveira 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.
If the group agrees with that, we would like to take it (Section 4) as
contributors.
Thanks,
Simone Ferlin and Olivier Mehani
On 27 February 2015 at 23:58, Brian Trammell <[email protected]> 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: [email protected]
To: "Gorry Fairhurst" <[email protected]>, "Mirja Kuehlewind" <[email protected]>, "Brian Trammell"
<[email protected]>, "Mirja Kuehlewind" <[email protected]>, "Godred Fairhurst" <[email protected]>, "Brian
Trammell" <[email protected]>
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
[email protected]
https://www.ietf.org/mailman/listinfo/taps
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
--
------------------------------------------
Dipl.-Ing. Mirja Kühlewind
Communication Systems Group
Institute TIK, ETH Zürich
Gloriastrasse 35, 8092 Zürich, Switzerland
Room ETZ G93
phone: +41 44 63 26932
email: [email protected]
------------------------------------------
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
