
From nobody Thu Sep  3 12:10:22 2015
Return-Path: <aaron.falk@gmail.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAD31B36F0 for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tns45k8GcEBp for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:10:20 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FEC91B2D8B for <taps@ietf.org>; Thu,  3 Sep 2015 12:09:01 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so56548862igb.0 for <taps@ietf.org>; Thu, 03 Sep 2015 12:09:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=rxshBi61Ezhr1B6Bgy8AeatxO9p4yKjB1zwoX5+Wdxg=; b=yyRqjVqYzl/xyrwSdBZS7ZLqDL2C8XzAjU4v6L6MtvPdfSBIb7xQaKuTHXQbSJO2lo XWSGElq9VpFEG62B+6olgm5THliuUF9aG0UvyWoR8X19FjsSa/UjbMf9G+DN4R+Pq9nS ZkTRWNTiA+SMmGmr31W7+WSz51jq2/RlI+583RyC+Il3x60XO8+8gT7Rt71shQl9aDRj FieSKgh5HCKOfthZAz+VKEVp4N4yaiI7GmPWqPg0Q5jBV8VSHk+yhLsUUwxwOXkkbXX4 oS7Zhu4C30jVUqzNltlceZcPGeQ/Wek/yq713L31bCcuGdVjvQeaWB1Jlnsv1OWNGphh zYYw==
MIME-Version: 1.0
X-Received: by 10.50.30.197 with SMTP id u5mr16744984igh.9.1441307340800; Thu, 03 Sep 2015 12:09:00 -0700 (PDT)
Received: by 10.64.111.131 with HTTP; Thu, 3 Sep 2015 12:09:00 -0700 (PDT)
Date: Thu, 3 Sep 2015 15:09:00 -0400
Message-ID: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com>
From: Aaron Falk <aaron.falk@gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Brian Trammell <ietf@trammell.ch>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary=047d7bdc11be0f9d95051edc84bf
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/NS1t5yZoIRnt0hzk-3pG-VqOUiU>
Cc: "taps@ietf.org" <taps@ietf.org>
Subject: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:10:21 -0000

--047d7bdc11be0f9d95051edc84bf
Content-Type: text/plain; charset=UTF-8

TAPS Editors-

Can you provide an update on the draft revisions discussed in Prague?  We
discussed a webex interim meeting to get review and hopefully some
consensus.

>From the minutes I have the following changes (this may not be complete):

   - Karen & Michael will add some text on SCTP
   - Varun will add some text on RTP
   - Brian will revert the TCP text to remove component/feature ("keep
   3.1.1, 3.1.2, strike 3.1.3, replace 4 with a list of features we'd like to
   have...? [Brian knows what to do :-)]."
   - Vincent Roca will write something about FLUTE based on NORM
   - Gorry will write something on applications learning about network
   conditions (ICMP)
   - Mirja will write something about scavenger congestion control


--aaron

--047d7bdc11be0f9d95051edc84bf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">TAPS Editors-<div><br></div><div>Can you provide an update=
 on the draft revisions discussed in Prague?=C2=A0 We discussed a webex int=
erim meeting to get review and hopefully some consensus. =C2=A0</div><div><=
br></div><div>From the minutes I have the following changes (this may not b=
e complete):</div><div><ul><li>Karen &amp; Michael will add some text on SC=
TP</li><li>Varun will add some text on RTP</li><li>Brian will revert the TC=
P text to remove component/feature (&quot;keep 3.1.1, 3.1.2, strike 3.1.3, =
replace 4 with a list of features we&#39;d like to have...? [Brian knows wh=
at to do :-)].&quot;</li><li>Vincent Roca will write something about FLUTE =
based on NORM</li><li>Gorry will write something on applications learning a=
bout network conditions (ICMP)</li><li>Mirja will write something about sca=
venger congestion control</li></ul></div><div><br></div><div>--aaron</div><=
/div>

--047d7bdc11be0f9d95051edc84bf--


From nobody Thu Sep  3 12:13:01 2015
Return-Path: <ietf@trammell.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91DC31B3DBD for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.512
X-Spam-Level: 
X-Spam-Status: No, score=-0.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OChAJ5ns-AoC for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:12:56 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4B61B3D83 for <taps@ietf.org>; Thu,  3 Sep 2015 12:12:56 -0700 (PDT)
Received: from [10.0.27.109] (dynamic-94-247-222-033.catv.glattnet.ch [94.247.222.33]) by trammell.ch (Postfix) with ESMTPSA id 9B6651A01CD; Thu,  3 Sep 2015 21:12:55 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CF213B80-64D3-4CB4-A96A-3069114E18CF"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.1
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com>
Date: Thu, 3 Sep 2015 21:12:54 +0200
Message-Id: <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch>
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com>
To: Aaron Falk <aaron.falk@gmail.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/ZggyLK3Gjn6UpGtGU6smH38zdck>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:12:58 -0000

--Apple-Mail=_CF213B80-64D3-4CB4-A96A-3069114E18CF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Aaron,

the status is pretty much "August is over and people are finally back =
from vacation, and are dusting off their inboxes."

On specific points:


> On 03 Sep 2015, at 21:09, Aaron Falk <aaron.falk@gmail.com> wrote:
>=20
> TAPS Editors-
>=20
> Can you provide an update on the draft revisions discussed in Prague?  =
We discussed a webex interim meeting to get review and hopefully some =
consensus.
>=20
> =46rom the minutes I have the following changes (this may not be =
complete):
> 	=E2=80=A2 Karen & Michael will add some text on SCTP

- will twist arms tomorrow or Tuesday.

> 	=E2=80=A2 Varun will add some text on RTP

- ditto.

> 	=E2=80=A2 Brian will revert the TCP text to remove =
component/feature ("keep 3.1.1, 3.1.2, strike 3.1.3, replace 4 with a =
list of features we'd like to have...? [Brian knows what to do :-)]."

- just needs to be done, on the list for next week.

> 	=E2=80=A2 Vincent Roca will write something about FLUTE based on =
NORM

- took a quick look at this, it looks good. Vincent also sent a =
suggestion that we mention FECFRAME here, though no integration-ready =
text.

> 	=E2=80=A2 Gorry will write something on applications learning =
about network conditions (ICMP)
> 	=E2=80=A2 Mirja will write something about scavenger congestion =
control

- will leave these to Gorry and Mirja to answer.

Cheers,

Brian


--Apple-Mail=_CF213B80-64D3-4CB4-A96A-3069114E18CF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV6Ju3AAoJENt3nsOmbNJcEPQH/2JRWW/tSoZ2kdEdY2onU8aw
SE/rBnTMI6I4lJVyK/B37D+sblbutC/GNy3rcOIph+w8PhumPBFE0SA/NNcgcgXN
PvxCClvWTB1ej2pduPtCJPIV0QBmX5dJEnCYamnH6bkCatKaMdsbAXLDSsm0khFw
qTFgUwVKbSIoOFVQ6w6jDhnGhRBlCZCH9S3oXgaH8g6BLTMNXkCI+5mhX3dNX3hv
/JsGJej9DdD8BEozgKo1D280TUHxuK5fbCCvZ/DNnbsMQZ5LtznkFW2lREESBF4Y
DZgafnhA2tQZUBOMozhqxFissAUR1EMWYqR26xhaTtOCIn25Co+lDydYdBNKliw=
=uyPr
-----END PGP SIGNATURE-----

--Apple-Mail=_CF213B80-64D3-4CB4-A96A-3069114E18CF--


From nobody Thu Sep  3 12:15:01 2015
Return-Path: <ietf@trammell.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC3A1B39AA for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G_MuGWWemLuO for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:14:57 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id B3B421B4063 for <taps@ietf.org>; Thu,  3 Sep 2015 12:14:57 -0700 (PDT)
Received: from [10.0.27.109] (dynamic-94-247-222-033.catv.glattnet.ch [94.247.222.33]) by trammell.ch (Postfix) with ESMTPSA id 1DF1C1A01CD; Thu,  3 Sep 2015 21:14:57 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B5C11269-45D5-4CD6-AA2E-B3D89E04CC13"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.1
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch>
Date: Thu, 3 Sep 2015 21:14:56 +0200
Message-Id: <239526D9-0661-452A-8877-51ECFFFE5C1E@trammell.ch>
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com> <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch>
To: Aaron Falk <aaron.falk@gmail.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/U9rRmWX1e73KAXEk5dkqXFLOAOk>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:14:59 -0000

--Apple-Mail=_B5C11269-45D5-4CD6-AA2E-B3D89E04CC13
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Ah, didn't see this was sent to the list, so:


>> On 03 Sep 2015, at 21:09, Aaron Falk <aaron.falk@gmail.com> wrote:
>>=20
>> =46rom the minutes I have the following changes (this may not be =
complete):
>> 	=E2=80=A2 Karen & Michael will add some text on SCTP
>=20
> - will twist arms tomorrow or Tuesday.
>=20
>> 	=E2=80=A2 Varun will add some text on RTP
>=20
> - ditto.

Karen, Michael, Varun, consider your arms publicly twisted. :)

Cheers,

Brian


--Apple-Mail=_B5C11269-45D5-4CD6-AA2E-B3D89E04CC13
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJV6JwwAAoJENt3nsOmbNJcUqQIAIB706576y+o99Nt9YQYaj+W
d1whOsMZmMuqAVZYxMLNzUHG3EiGkGc5+sW9Tz3npTSDCrNTdzFJYkDcZRAiuYjC
l/xMd9m1hTO3jbSnmI0zQDWkH+C1aPj34XnfwIdkSe+ySUq3+655iDIQ/ZUeDrqT
9V8+oIBcRqo1L9ejOoS9KTjFvGaW0XKvsohuePbzX3qozLNwpMQW4i42RM9RoDUt
sWgzNYSWiqNB0b/J9j1NjCseiQ96wUNnMkyfaz13oMZc8pkEL+1MEIHnfum17dhV
dh1Zur8sAa3WfWIqZkzntoqlNY/4wC/vFMf5/M1UMaMXFbLxLapzxAD2JBRcs/M=
=er3w
-----END PGP SIGNATURE-----

--Apple-Mail=_B5C11269-45D5-4CD6-AA2E-B3D89E04CC13--


From nobody Thu Sep  3 12:20:15 2015
Return-Path: <aaron.falk@gmail.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E676B1B2E15 for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PogZ801Kq437 for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 12:20:12 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6910B1B3686 for <taps@ietf.org>; Thu,  3 Sep 2015 12:19:59 -0700 (PDT)
Received: by ioiz6 with SMTP id z6so70015625ioi.2 for <taps@ietf.org>; Thu, 03 Sep 2015 12:19:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MGB1NMeys1cuL/xMh0mbOuxntPbni8UbSoUyb8MdI1o=; b=RKDDqg5n79puFVsdHSQYobhTneRoVWn48RCoRD9gM9PmhqH2edPdTGiz+USGyXq5m2 rgdkPJVMyd3f13M56DcMIWUc13ijTAN6bJEDlHsFK5+a5+b7I26vl2fqOE9Ns5Fj+tGq KX0DRRDQY5bB28RWdfwFkuGxALdQdR/DjTve7MhpG5AtBD/YCPFyGyKccR3+ZP2L0vjH dgR8qkC5ZY8OOEqPrpqx3+LeeQ/h1U8m9c7luAypwMV4HqmZmotu26m5U5PppE6eFnLo 9q+lpPRWSjnjdRESWNxcFZCgSAju3e9z2WAW+0bBLr/6sjL/aPCzchhOuFM15GuttlOk +eGQ==
MIME-Version: 1.0
X-Received: by 10.107.167.134 with SMTP id q128mr1419798ioe.137.1441307998824;  Thu, 03 Sep 2015 12:19:58 -0700 (PDT)
Received: by 10.64.111.131 with HTTP; Thu, 3 Sep 2015 12:19:58 -0700 (PDT)
In-Reply-To: <239526D9-0661-452A-8877-51ECFFFE5C1E@trammell.ch>
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com> <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch> <239526D9-0661-452A-8877-51ECFFFE5C1E@trammell.ch>
Date: Thu, 3 Sep 2015 15:19:58 -0400
Message-ID: <CAD62q9Vpthpwnbz3t2Q8UNeVUWmJQXbUDKUxdAPYNU-s9BrvBA@mail.gmail.com>
From: Aaron Falk <aaron.falk@gmail.com>
To: Brian Trammell <ietf@trammell.ch>
Content-Type: multipart/alternative; boundary=001a1134f37a4847ce051edcabac
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/Ex-IWajJfgVo6uzBvjz435KHovU>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 19:20:14 -0000

--001a1134f37a4847ce051edcabac
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for the quick update, Brian!

On Thu, Sep 3, 2015 at 3:14 PM, Brian Trammell <ietf@trammell.ch> wrote:

> Ah, didn't see this was sent to the list, so:
>
>
> >> On 03 Sep 2015, at 21:09, Aaron Falk <aaron.falk@gmail.com> wrote:
> >>
> >> From the minutes I have the following changes (this may not be
> complete):
> >>      =E2=80=A2 Karen & Michael will add some text on SCTP
> >
> > - will twist arms tomorrow or Tuesday.
> >
> >>      =E2=80=A2 Varun will add some text on RTP
> >
> > - ditto.
>
> Karen, Michael, Varun, consider your arms publicly twisted. :)
>
> Cheers,
>
> Brian
>
>

--001a1134f37a4847ce051edcabac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for the quick update, Brian!</div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Thu, Sep 3, 2015 at 3:14 PM, Br=
ian Trammell <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@trammell.ch" targ=
et=3D"_blank">ietf@trammell.ch</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Ah, didn&#39;t see this was sent to the list, so:<br>
<span class=3D""><br>
<br>
&gt;&gt; On 03 Sep 2015, at 21:09, Aaron Falk &lt;<a href=3D"mailto:aaron.f=
alk@gmail.com">aaron.falk@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
</span><span class=3D"">&gt;&gt; From the minutes I have the following chan=
ges (this may not be complete):<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Karen &amp; Michael will add some te=
xt on SCTP<br>
&gt;<br>
&gt; - will twist arms tomorrow or Tuesday.<br>
&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =E2=80=A2 Varun will add some text on RTP<br>
&gt;<br>
&gt; - ditto.<br>
<br>
</span>Karen, Michael, Varun, consider your arms publicly twisted. :)<br>
<br>
Cheers,<br>
<br>
Brian<br>
<br>
</blockquote></div><br></div>

--001a1134f37a4847ce051edcabac--


From nobody Thu Sep  3 14:06:03 2015
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1AB1B4A6F for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 14:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E26tOhNjiwaR for <taps@ietfa.amsl.com>; Thu,  3 Sep 2015 14:05:59 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A132E1B4A99 for <taps@ietf.org>; Thu,  3 Sep 2015 14:05:40 -0700 (PDT)
Received: from [10.40.41.103] (127.231.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch [178.197.231.127]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 7E22E1C0C0BCF; Thu,  3 Sep 2015 23:05:37 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <239526D9-0661-452A-8877-51ECFFFE5C1E@trammell.ch>
Date: Thu, 3 Sep 2015 23:05:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A713D4D-8F31-41BB-B6F4-19CF6BE1D47A@lurchi.franken.de>
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com> <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch> <239526D9-0661-452A-8877-51ECFFFE5C1E@trammell.ch>
To: Brian Trammell <ietf@trammell.ch>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/nlQGsBw0WppuoEGJgvivb03INs4>
Cc: Aaron Falk <aaron.falk@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 21:06:01 -0000

> On 03 Sep 2015, at 21:14, Brian Trammell <ietf@trammell.ch> wrote:
>=20
> Ah, didn't see this was sent to the list, so:
>=20
>=20
>>> On 03 Sep 2015, at 21:09, Aaron Falk <aaron.falk@gmail.com> wrote:
>>>=20
>>> =46rom the minutes I have the following changes (this may not be =
complete):
>>> 	=E2=80=A2 Karen & Michael will add some text on SCTP
>>=20
>> - will twist arms tomorrow or Tuesday.
>>=20
>>> 	=E2=80=A2 Varun will add some text on RTP
>>=20
>> - ditto.
>=20
> Karen, Michael, Varun, consider your arms publicly twisted. :)
OK. So if you are twisting my arm, please state clearly what you want me =
to write...
Seriously: I'm willing to provide SCTP related text as long as I know =
what
you want. However, I don't. I think Mirja wanted to look at the document
and come back with a statement about what is missing or could be =
improved.

So do you have any particular things you want to be added or changed?

Best regards
Michael
>=20
> Cheers,
>=20
> Brian
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps


From nobody Mon Sep  7 00:29:47 2015
Return-Path: <vincent.roca@inria.fr>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D0C1B3D06 for <taps@ietfa.amsl.com>; Mon,  7 Sep 2015 00:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.661
X-Spam-Level: 
X-Spam-Status: No, score=-4.661 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U5EBFsndLSRb for <taps@ietfa.amsl.com>; Mon,  7 Sep 2015 00:29:44 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F18B1B3D05 for <taps@ietf.org>; Mon,  7 Sep 2015 00:29:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.17,484,1437429600";  d="asc'?scan'208";a="176281432"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Sep 2015 09:29:41 +0200
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_1021A45D-8431-4B4C-9CAE-47426AD6F766"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.1
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch>
Date: Mon, 7 Sep 2015 09:29:40 +0200
Message-Id: <48BCDD96-D490-4262-835E-A51F12B69174@inria.fr>
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com> <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch>
To: Brian Trammell <ietf@trammell.ch>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/LnjhG8nDT4n8zn8Kv-5VFWqzn98>
Cc: Aaron Falk <aaron.falk@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Vincent Roca <vincent.roca@inria.fr>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Sep 2015 07:29:46 -0000

--Apple-Mail=_1021A45D-8431-4B4C-9CAE-47426AD6F766
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hello everybody,

>> 	=E2=80=A2 Vincent Roca will write something about FLUTE based on =
NORM
>=20
> - took a quick look at this, it looks good. Vincent also sent a =
suggestion that we mention FECFRAME here, though no integration-ready =
text.

I can provide some FECFRAME (https://datatracker.ietf.org/doc/rfc6363/) =
text tomorrow,
Tuesday, 8th, if you=E2=80=99re interested. This is not a big deal, =
I=E2=80=99m just waiting the =C2=AB go =C2=BB.

IMHO FECFRAME makes sense in the TAPS approach. Unlike the NORM and =
FLUTE/ALC
full featured protocols, FECFRAME is a shim layer that can be =
dynamically plugged between an
application protocol (typically RTP) and a datagram oriented transport =
protocol (typically UDP).
It then provides FEC protection, using one of the various FEC schemes =
proposed. Commercial
deployments have started and several solutions are not encumbered with =
IPR (at least so far).
I can tell you more if you want.

Cheers,

  Vincent


--Apple-Mail=_1021A45D-8431-4B4C-9CAE-47426AD6F766
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJV7TzkAAoJEHBYw8t72N4rICcQAJSQ05gKey0l6VXE43uLpwiR
CQaiNXlRv63ttcNvnAfsYsmLdpGVxGAVWDNRstmsFDcWiWbvfkhHpZHghXkw3Quk
ivZRyQHkicIql4ufjhyjzbqQi9U2m5FFZvhS3TCtWwtCsW9BN+Zu6nbxjlGfy67g
reoihcWqrewVMLe2eT4YFCu3RC+AiVIqqHzjgIJwiJlUYLCR9oRqg7XFOJrEWFUR
hRkiyVz1OA/x2NpuPFzkBzzB7ncfd/qqHi46GG9vfPQDtGQYxEMmrTF8oecECATm
sp2o3gymGdqoFXvY96cd9GGLP+HXagCWcG6fLxmUc0kAxUeP+ggbmF21EF6FhI4j
oXqJzUQWeWMZGoKUVuwEJb80wp+JuPjIQhoC5pa75zUXEQkH8qBH4srhVuXkLA4F
0lFdvpmrr0MOV2lgjHyV/a1sYbDIzqABSeeLZH5NTv/GBGL9/pIa5GWOZHbnYHMv
5j17ky9yJ6uOKMy5bdiPMVqrUpJ07BYNNxvWkAEvVPBd1zgJNQe42m8+l0S6ZdIE
XapVS3p3ygFaYKqKv7XOvSRiXub8WuuK+ue+F5Ey7WXde7t+vCQAFqgvvinbjar+
ln01oYNv0CjNp0fu/AhAzl8oRJPPTJlP8NGcIBFtj14Jqz/Q+r95yC/4SsKJCHH7
inU9E9PtZqP0U5iKVhhO
=YOBl
-----END PGP SIGNATURE-----

--Apple-Mail=_1021A45D-8431-4B4C-9CAE-47426AD6F766--


From nobody Fri Sep 11 08:40:45 2015
Return-Path: <ietf@trammell.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3241B3D61 for <taps@ietfa.amsl.com>; Fri, 11 Sep 2015 08:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Level: 
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zSxtmL-HMRv for <taps@ietfa.amsl.com>; Fri, 11 Sep 2015 08:40:41 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id AAD3C1B39AB for <taps@ietf.org>; Fri, 11 Sep 2015 08:40:41 -0700 (PDT)
Received: from nb-10604.ethz.ch (nb-10604.ethz.ch [82.130.102.91]) by trammell.ch (Postfix) with ESMTPSA id CA03E1A05F0 for <taps@ietf.org>; Fri, 11 Sep 2015 17:40:09 +0200 (CEST)
From: Brian Trammell <ietf@trammell.ch>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E10344D-9E46-48C4-B443-AD4EE90D3466@trammell.ch>
Date: Fri, 11 Sep 2015 17:40:07 +0200
To: taps WG <taps@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/mWoYe96F0k1ItG5j9wPcLWOwDvg>
Subject: [Taps] Progress on taps-trasports
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2015 15:40:43 -0000

Greetings, all,

We've integrated the FLUTE/ALC text into the working copy of the =
document (github.com/britram/taps-transports) as well as moving over to =
a slightly more streamlined Makefile (though, due to smart quote =
replacement issues I'm still debugging -- don't ask -- the toolchain to =
build the RFC from the markdown is not working at the moment).

We've discussed the decisions taken in the Prague meeting about how to =
handle features vs. components in each transport protocol section. Our =
(somewhat complicated) attempt on -06 to really describe TCP in terms of =
what we believe the components are didn't work out so well, and we'll go =
back to the previous, simpler, more thoroughly decomposed list from the =
previous version.

It strikes us that part of the issue is that what we've listed for each =
protocol in the 3.x.3 sections aren't really components (in the sense of =
sets intertwined of behaviors that are inherent to the protocol as =
designed), but rather features (whether or not these features should be =
exposed in the eventual TAPS framework). The *distinction* between a =
component and a feature, though useful for thinking about how to =
decompose protocols, is (as Michael indicated in Prague) perhaps a bit =
academic when the point of the exercise in the first place is to ensure =
we have a reasonably complete list of features that TAPS can/should =
support.

So we propose the following resolution to the components-versus-features =
confusion on a per-protocol basis:

(1) Keep each list in the 3.x.3 sections more or less as-is.
(2) Retitle the sections 3.x.3 "Features Provided" and make editorial =
changes as necessary for agreement.

Please yell if you think this is a terrible idea; otherwise we'll spin a =
-07 shortly. After this, we still need to handle the following items

	=E2=80=A2 Karen & Michael will add some text on SCTP

This is actually Mirja's action; she'll review the SCTP section and =
coordinate with Karen & Michael shortly. Arms untwisted 'til then :) and =
apologies -- I thought we were synced up here.

	=E2=80=A2 Varun will add some text on RTP

We're also missing text on WebSockets. Since we have nothing for either =
at this point, we'll strike these sections

	=E2=80=A2 Gorry will write something on applications learning =
about network conditions (ICMP)

This is still pending.

We'll integrate these into an -08, and then I think we're ready for =
WGLC.

Thanks, cheers,

Brian and Mirja=


From nobody Tue Sep 15 08:08:42 2015
Return-Path: <ietf@trammell.ch>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF501B2F86; Tue, 15 Sep 2015 08:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k54cmUrFnSdW; Tue, 15 Sep 2015 08:08:37 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 437531B2B9F; Tue, 15 Sep 2015 08:08:36 -0700 (PDT)
Received: from [IPv6:2001:67c:10ec:2a49:8000::10d6] (unknown [IPv6:2001:67c:10ec:2a49:8000::10d6]) by trammell.ch (Postfix) with ESMTPSA id 920B71A0157; Tue, 15 Sep 2015 17:08:35 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <ff92251cb49f5f5ce639057a4118b234@mail.gmail.com>
Date: Tue, 15 Sep 2015 17:08:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EC3BF52-C1FF-4E64-9F66-644D1F1570F2@trammell.ch>
References: <20150706220631.6336.219.idtracker@ietfa.amsl.com> <ff92251cb49f5f5ce639057a4118b234@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/uyGEB5A-ryk-1FVI4JNxlcpojLg>
Cc: taps@ietf.org, internet-drafts@ietf.org, i-d-announce@ietf.org
Subject: Re: [Taps] I-D Action: draft-ietf-taps-transports-06.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 15:08:40 -0000

hi Karen, all,

Apologies for overlooking this message in last week's note about "things =
to do"; add "address Karen's comments from two months ago" to this list. =
:)

Inline:

> On 15 Jul 2015, at 16:28, Karen Elisabeth Egede Nielsen =
<karen.nielsen@tieto.com> wrote:
>=20
> Hi,
>=20
> Please find a very few comments to the document. Nothing major. Please =
use
> if you see fit and only then :-)
>=20
> Section 1: End First Paragraph:
>=20
> Here it is said that a transport service feature may be minimal =
latency.
> Opposed to the other features listed here,
> like e.g. in-order or reliable delivery, then minimal latency seems a =
more
> delicate obtainable feature; How one best obtain it
> within the services provided by a certain transport protocol, may =
depend
> quite heavily on the application traffic pattern (unless CPU and =
network
> resources are unlimited).
> Also minimal latency is not a feature which any of the protocols =
described
> in the document has within its list of features (I think) or
> are you thinking minimal latency and best effort transport service =
(like
> UDP) - Or are you thinking some smart protocol of the future which =
will
> deduce how to best
> provide a minimal latency service for a particular application flow =
over a
> specific E-to-E path ?

This is a good point...=20

What we were trying to capture here is that, in the present arrangement =
of the transport layer, the features we think of are not very far =
removed from the mechanisms that provide them, while in the transport =
layer we'd like to see in the future, the features can be expressed in =
terms closer to application-layer requirements than to transport-layer =
mechanisms.

Here, minimal latency could be better stated as "a preference to accept =
loss instead of buffer-induced latency", but on second thought this is =
hard to capture in a single sentence in the intro, so we'll remove "and =
minimal latency".

>=20
> Section 3.1.2:
>=20
> Not sure if this way of describing the TCP Protocol Components is the
> right way to do.
>=20
> I think that it would be nice to have the list here use Transport =
Service
> Features names
> and then possibly - if relevant as it is done now - describe in more
> detail how the TCP Component implement the Transport Service Feature.
> I further think that one should strive -  best possibly - to use the =
same
> Transport Service Features for the different protocols when =
applicable.

This is the direction we're leaning toward, perhaps with a bit less =
explanatory text (indeed, now I recall that it was our discussion about =
these comments in Prague that led to this direction...)

> Like (some easy examples) for TCP:
>=20
> o  Single stream-oriented transmission:
>=20
>      The stream abstraction atop
>      the datagram service provided by IP is implemented by dividing =
the
>      stream into segments.
>=20
> o  Flow control:
>=20
>      Window-based flow control, with receiver-side window management
>      and signaling of available window: Scaling the flow control =
window
>      beyond 64kB requires the use of an optional feature, which has
>      performance implications in environments where this option is not
>      supported; this can be the case either if the receiver does not
>      implement window scaling or if a network node on the path strips
>      the window scaling option.
>=20
> o  Congestion Control:
>=20
>      Window-based congestion control reacting to loss, delay,
>      retransmission timeout, or an explicit congestion signal (ECN):
>      Most commonly used is a loss signal from the reliability
>      component's retransmission mechanism.  TCP reacts to a congestion
>      signal by reducing the size of the congestion window;
>      retransmission timeout is generally handled with a larger =
reaction
>      than other signals.

I suspect many of the following comments will be overtaken by the =
reorganization of these sections to be feature- rather than =
component-centered. We'll keep them in mind during the reorg, though I =
will comment briefly on a few points...

> I am not sure if Connection oriented  and Feature negotiation should =
be
> split into two features ?

At a feature level, yes. At the component level we were proposing with =
this text, they're not really separable.

> I am not sure if one wants something called Fast Transmission Start - =
or
> simply Fast Open - as a feature ?
>=20
> I am not sure what the slogan of the present bullet about Nagle should =
be.
> Also I am not so sure about the content of this section.
> Disabling Nagle does not always give the lowest latency and further =
then I
> think that we are missing the good side of Nagle in the present text.
> (the bundling of multiple stream segments into packets  and its =
benefits)

Nagle is an oddity, and a perfect example of the mechanism and =
requirements getting completely tangled up in one another we're trying =
to avoid. But the name of the algorithmic mechanism is also a shorthand =
way that everyone who kind of understands TCP will recognize as the =
requirement...

Talking about it as a pure feature, it's "data bundling". The ability to =
*disable* Nagle is kind of irrelevant in a TAPS world -- indeed, *every* =
feature should be selectable.

> I do not think that it is relevant to describe how SACK helps reduce =
the
> latency of Fast Recovery.
> If so, one could also describe how it improves the congestion control
> handling - or ? . Is it at all relevant to consider TCP without SACK
> enabled ?
> Generally I am not so sure what the latency discussion in this section =
is
> about. It says that "the retransmission timeout defines the upper
> bound...". But exp back-off _is_ used in TCP, further the statement is
> really only true if RTO-restart is used.
> Should one not rather say that RTO-based loss detection reacts based =
on
> timeouts - or why does one say anything at all here ? Is it to try to
> describe if the protocol provides some upper bound for
> the latency - if so that is more provided via MAXRT ?. The RTO gives =
an
> upper bound for when to retransmit - not as such on the reliable =
delivery.
> Then on top one have the delay in the SND buffer.
> Generally the protocol is continuously being evolved to provide low
> latency loss recovery operation. Perhaps this is relevant to state ?
>=20
> General:
>=20
> I assume that once one has settled a good way of describing the TCP
> Components, then one will try to align the other sections.
> Or alternatively one go back now and try to settle the list of =
Abstract
> Transport Service Features that existing transport protocol provides - =
and
> then afterwards
> updates the various  Transport Protocol Components sections in this =
doc,
> including the TCP one.

Yep. The good way looks a lot closer to your suggestion than to what we =
proposed in -06.

Thanks, cheers,

Brian

> Thanks.
> BR,  Karen
>=20
>> -----Original Message-----
>> From: Taps [mailto:taps-bounces@ietf.org] On Behalf Of internet-
>> drafts@ietf.org
>> Sent: Tuesday, July 07, 2015 12:07 AM
>> To: i-d-announce@ietf.org
>> Cc: taps@ietf.org
>> Subject: [Taps] I-D Action: draft-ietf-taps-transports-06.txt
>>=20
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>> This draft is a work item of the Transport Services Working Group of =
the
> IETF.
>>=20
>>       Title           : Services provided by IETF transport protocols
> and congestion
>> control mechanisms
>>       Authors         : Godred Fairhurst
>>                         Brian Trammell
>>                         Mirja Kuehlewind
>> 	Filename        : draft-ietf-taps-transports-06.txt
>> 	Pages           : 39
>> 	Date            : 2015-07-06
>>=20
>> 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.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-taps-transports/
>>=20
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-taps-transports-06
>>=20
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transports-06
>>=20
>>=20
>> 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.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org
>> https://www.ietf.org/mailman/listinfo/taps
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps


From nobody Mon Sep 21 01:44:41 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 137F51A8A9D for <taps@ietfa.amsl.com>; Mon, 21 Sep 2015 01:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uy1p7GmBQV6m for <taps@ietfa.amsl.com>; Mon, 21 Sep 2015 01:44:38 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98CCD1A8A96 for <taps@ietf.org>; Mon, 21 Sep 2015 01:44:38 -0700 (PDT)
Received: from mail-mx4.uio.no ([129.240.10.45]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1ZdwiB-0005Es-Vw for taps@ietf.org; Mon, 21 Sep 2015 10:44:35 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx4.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1ZdwiB-0002wg-Ec for taps@ietf.org; Mon, 21 Sep 2015 10:44:35 +0200
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Sep 2015 10:44:35 +0200
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com>
To: taps WG <taps@ietf.org>
Message-Id: <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 11 msgs/h 7 sum rcpts/h 15 sum msgs/h 9 total rcpts 33328 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.05, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO,  uiouri=NO)
X-UiO-Scanned: 8F42931732930594DB82FF8DA1FC3FBD031CE015
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -59 maxlevel 80 minaction 2 bait 0 mail/h: 7 total 7940 max/h 17 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/XUFJthRArc8RH4wehQlLB11bY7A>
Subject: [Taps] Fwd: New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2015 08:44:41 -0000

Dear all,

In my presentation in Prague, I proposed an approach to identify the =
services that transport protocols provide. At the end of the ensuing =
discussion, I said that I (with co-authors) would write a draft that =
explains the proposal by applying the proposed method to TCP and SCTP.

We just submitted this document - see below;  I hope that this will lead =
to some discussion on the list...

Cheers,
Michael


> Begin forwarded message:
>=20
> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for =
draft-welzl-taps-transports-00.txt
> Date: 21 Sep 2015 10:35:33 CEST
> To: Michael Welzl <michawe@ifi.uio.no>, Michael Welzl =
<michawe@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>, Naeem =
Khademi <naeemk@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>, =
Naeem Khademi <naeemk@ifi.uio.no>
> Resent-From: <michawe@ifi.uio.no>
>=20
>=20
> A new version of I-D, draft-welzl-taps-transports-00.txt
> has been successfully submitted by Michael Welzl and posted to the
> IETF repository.
>=20
> Name:		draft-welzl-taps-transports
> Revision:	00
> Title:		An Approach to Identify Services Provided by =
IETF Transport Protocols and Congestion Control Mechanisms
> Document date:	2015-09-21
> Group:		Individual Submission
> Pages:		23
> URL:            =
https://www.ietf.org/internet-drafts/draft-welzl-taps-transports-00.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-welzl-taps-transports/
> Htmlized:       =
https://tools.ietf.org/html/draft-welzl-taps-transports-00
>=20
>=20
> Abstract:
>   This document describes a method to identify services in transport
>   protocols and congestion control mechanisms.  It shows the approach
>   using TCP and SCTP (base protocol) as examples.
>=20
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat
>=20


From nobody Mon Sep 21 04:14:24 2015
Return-Path: <marie@mjmontpetit.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C191B3098 for <taps@ietfa.amsl.com>; Mon, 21 Sep 2015 04:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9yGKEfnxWey for <taps@ietfa.amsl.com>; Mon, 21 Sep 2015 04:14:20 -0700 (PDT)
Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com [209.85.220.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C383D1B3097 for <taps@ietf.org>; Mon, 21 Sep 2015 04:14:20 -0700 (PDT)
Received: by qkap81 with SMTP id p81so42951613qka.2 for <taps@ietf.org>; Mon, 21 Sep 2015 04:14:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=D2axM6cMJPcdlUn6rvsh+gNFH6Jr3EeUGflsAUO3HYg=; b=L5DPztVN0MZaDBBx4HvdXZbcYoB+gvgyOkEH1USHv030Y6gChMZuIm2kzOpDpymUK5 UClyxoErSzCW4wCHjXIuN5/fty7Lsv1QOw+yiczob9iW4pUS8KanTGI2YV4Z/LX0zWBN bB8Rty/YBzuakRs4O9KFEI41KVI740hb34etDiDxQCXfQIPGLDVE2kvrdicHOZ1GyIyr WYH1pelDQcVf82ObSG79Fn9reJ2B976iKyuQK4+H2VJiyoSMf9wnMVs82aL2D8I1Vcfj 2S4aRL1XlzI3EkuoA9mv98YjAdDY4Jehc+GN+SYCD1X7T0Z6g1rOKbE+U0mcTv1k5Sa9 z3Wg==
X-Gm-Message-State: ALoCoQklkWXoqpHHgIxJIsYUc97XPVlvh92nwSQMjBXp+zw9aqPsgx6UDLJo8mJaer21KeMy8kWW
X-Received: by 10.55.197.82 with SMTP id p79mr21696877qki.5.1442834059920; Mon, 21 Sep 2015 04:14:19 -0700 (PDT)
Received: from [172.16.42.2] (c-76-118-234-192.hsd1.ma.comcast.net. [76.118.234.192]) by smtp.gmail.com with ESMTPSA id b16sm9687460qkj.1.2015.09.21.04.14.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Sep 2015 04:14:19 -0700 (PDT)
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no>
Mime-Version: 1.0 (1.0)
In-Reply-To: <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com>
X-Mailer: iPad Mail (13A344)
From: "MJmontpetit.com" <marie@mjmontpetit.com>
Date: Mon, 21 Sep 2015 07:14:21 -0400
To: Michael Welzl <michawe@ifi.uio.no>
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/164JHuQc_MLYj1-_4NgHkscDd8o>
Cc: taps WG <taps@ietf.org>
Subject: Re: [Taps] Fwd: New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2015 11:14:22 -0000

Interesting and inline to getting transport API(s)

Marie-Jos=C3=A9 Montpetit
marie@mjmontpetit.com
mariejo@mit.edu

> On Sep 21, 2015, at 04:44, Michael Welzl <michawe@ifi.uio.no> wrote:
>=20
> Dear all,
>=20
> In my presentation in Prague, I proposed an approach to identify the servi=
ces that transport protocols provide. At the end of the ensuing discussion, I=
 said that I (with co-authors) would write a draft that explains the proposa=
l by applying the proposed method to TCP and SCTP.
>=20
> We just submitted this document - see below;  I hope that this will lead t=
o some discussion on the list...
>=20
> Cheers,
> Michael
>=20
>=20
>> Begin forwarded message:
>>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for draft-welzl-taps-transports-00.txt
>> Date: 21 Sep 2015 10:35:33 CEST
>> To: Michael Welzl <michawe@ifi.uio.no>, Michael Welzl <michawe@ifi.uio.no=
>, Michael Tuexen <tuexen@fh-muenster.de>, Naeem Khademi <naeemk@ifi.uio.no>=
, Michael Tuexen <tuexen@fh-muenster.de>, Naeem Khademi <naeemk@ifi.uio.no>
>> Resent-From: <michawe@ifi.uio.no>
>>=20
>>=20
>> A new version of I-D, draft-welzl-taps-transports-00.txt
>> has been successfully submitted by Michael Welzl and posted to the
>> IETF repository.
>>=20
>> Name:        draft-welzl-taps-transports
>> Revision:    00
>> Title:        An Approach to Identify Services Provided by IETF Transport=
 Protocols and Congestion Control Mechanisms
>> Document date:    2015-09-21
>> Group:        Individual Submission
>> Pages:        23
>> URL:            https://www.ietf.org/internet-drafts/draft-welzl-taps-tra=
nsports-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-welzl-taps-transpo=
rts/
>> Htmlized:       https://tools.ietf.org/html/draft-welzl-taps-transports-0=
0
>>=20
>>=20
>> Abstract:
>>  This document describes a method to identify services in transport
>>  protocols and congestion control mechanisms.  It shows the approach
>>  using TCP and SCTP (base protocol) as examples.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of submiss=
ion
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> The IETF Secretariat
>=20
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps


From nobody Thu Sep 24 02:07:28 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1751A8869 for <taps@ietfa.amsl.com>; Thu, 24 Sep 2015 02:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAvTm2V295EH for <taps@ietfa.amsl.com>; Thu, 24 Sep 2015 02:07:26 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id E95311A8861 for <taps@ietf.org>; Thu, 24 Sep 2015 02:07:25 -0700 (PDT)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:4807:9fa8:f4c3:b672]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 5BF251B00277; Thu, 24 Sep 2015 10:07:03 +0100 (BST)
References: <CAD62q9V+kXWR26NGbOr6ZHp0N+WqmPxb_8AqSOZAgfRpMgBVLQ@mail.gmail.com> <5C27F30C-AF58-41A1-8AB2-CDDE5CA0D7F0@trammell.ch> <48BCDD96-D490-4262-835E-A51F12B69174@inria.fr>
To: Vincent Roca <vincent.roca@inria.fr>, Brian Trammell <ietf@trammell.ch>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683.
Message-ID: <5603BD4B.3040704@erg.abdn.ac.uk>
Date: Thu, 24 Sep 2015 10:07:23 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <48BCDD96-D490-4262-835E-A51F12B69174@inria.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/51olKxDtdaUng2IVrIEuqmn-494>
Cc: Aaron Falk <aaron.falk@gmail.com>, =?UTF-8?Q?Mirja_K=c3=bchlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] document progress update?
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2015 09:07:27 -0000

I'd have thought it was worth seeing if FECFRAME fits as something to 
talk about.

It is used in places. There are transport concerns that differ and could 
be highlighted  - because some uses require pre-provisioned capacity 
(aka, do not have CC), so we probably need to say something about 
managed environments.

Whether it is a transport protocol (like TCP, UDP, websockets, etc), or 
a component (like ledbat) could be an interesting first debate.

What do others think?

Gorry

On 07/09/2015 08:29, Vincent Roca wrote:
> Hello everybody,
>
>>> 	• Vincent Roca will write something about FLUTE based on NORM
>>
>> - took a quick look at this, it looks good. Vincent also sent a suggestion that we mention FECFRAME here, though no integration-ready text.
>
> I can provide some FECFRAME (https://datatracker.ietf.org/doc/rfc6363/) text tomorrow,
> Tuesday, 8th, if you’re interested. This is not a big deal, I’m just waiting the « go ».
>
> IMHO FECFRAME makes sense in the TAPS approach. Unlike the NORM and FLUTE/ALC
> full featured protocols, FECFRAME is a shim layer that can be dynamically plugged between an
> application protocol (typically RTP) and a datagram oriented transport protocol (typically UDP).
> It then provides FEC protection, using one of the various FEC schemes proposed. Commercial
> deployments have started and several solutions are not encumbered with IPR (at least so far).
> I can tell you more if you want.
>
> Cheers,
>
>    Vincent
>
>
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
>


From nobody Sat Sep 26 00:17:24 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD021A0018 for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 00:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWWNGylirLAE for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 00:17:21 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 19C891A0015 for <taps@ietf.org>; Sat, 26 Sep 2015 00:17:21 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 85BFE1B0036C; Sat, 26 Sep 2015 08:24:27 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Sat, 26 Sep 2015 08:17:20 +0100
Message-ID: <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk>
In-Reply-To: <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com>
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no> <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com>
Date: Sat, 26 Sep 2015 08:17:20 +0100
From: gorry@erg.abdn.ac.uk
To: "MJmontpetit.com" <marie@mjmontpetit.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/fhNiReG90CocDGjXzAuj9jfXuc8>
Cc: Michael Welzl <michawe@ifi.uio.no>, taps WG <taps@ietf.org>
Subject: Re: [Taps] Fwd: New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Sep 2015 07:17:23 -0000

We seem to have two documents in a space where we started with one. These
are different, to me this is OK. Both seem close to charter milestone 1. I
 don't see much overlap between the contents of the descriptive language
and the API-focussed analysis, and any overlap could be eliminated.

To me, doc 1 (current chartered item) can evolve to provide background and
 missing documentation for anyone in the IETF, and should compare 
transports in a broad way and draw out the idea that they provide
services. This appears to be harder to get right than I for one had hoped,
and still has a wide scope. Not a bad thing. I suggest it will provide a
reference to stop us rat-holing when people ask what is "this" and explain
how all these transports stack-up against one another (good pun?). We can
(I suggest) finish this doc in this way.

I do like the idea of a second document focussed ONLY on the Transport API
 (I'd call this 1a). In this we can avoid this"discussion of what are
transports"  and move to  a  more focussed  process in doc 1b,  Most of
that troublesome descriptive  text can go into 1, and ensure we keep that
one readable to anyone in the  IETF.

Could  I suggest the two docs against the first milestone will help us
make  progress towards the next milestone faster. (Assuming we can keep
the two aligned, which seems quite doable). I can see also how the  docs
are useful to different people. I'd like to see both mature and provide
inputs to move forward.

Gorry


> Interesting and inline to getting transport API(s)
>
> Marie-JosÃ© Montpetit
> marie@mjmontpetit.com
> mariejo@mit.edu
>
>> On Sep 21, 2015, at 04:44, Michael Welzl <michawe@ifi.uio.no> wrote:
>>
>> Dear all,
>>
>> In my presentation in Prague, I proposed an approach to identify the
>> services that transport protocols provide. At the end of the ensuing
>> discussion, I said that I (with co-authors) would write a draft that
>> explains the proposal by applying the proposed method to TCP and SCTP.
>>
>> We just submitted this document - see below;  I hope that this will lead
>> to some discussion on the list...
>>
>> Cheers,
>> Michael
>>
>>
>>> Begin forwarded message:
>>>
>>> From: <internet-drafts@ietf.org>
>>> Subject: New Version Notification for
>>> draft-welzl-taps-transports-00.txt
>>> Date: 21 Sep 2015 10:35:33 CEST
>>> To: Michael Welzl <michawe@ifi.uio.no>, Michael Welzl
>>> <michawe@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>, Naeem
>>> Khademi <naeemk@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>,
>>> Naeem Khademi <naeemk@ifi.uio.no>
>>> Resent-From: <michawe@ifi.uio.no>
>>>
>>>
>>> A new version of I-D, draft-welzl-taps-transports-00.txt
>>> has been successfully submitted by Michael Welzl and posted to the
>>> IETF repository.
>>>
>>> Name:        draft-welzl-taps-transports
>>> Revision:    00
>>> Title:        An Approach to Identify Services Provided by IETF
>>> Transport Protocols and Congestion Control Mechanisms
>>> Document date:    2015-09-21
>>> Group:        Individual Submission
>>> Pages:        23
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-welzl-taps-transports-00.txt
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-welzl-taps-transports/
>>> Htmlized:
>>> https://tools.ietf.org/html/draft-welzl-taps-transports-00
>>>
>>>
>>> Abstract:
>>>  This document describes a method to identify services in transport
>>>  protocols and congestion control mechanisms.  It shows the approach
>>>  using TCP and SCTP (base protocol) as examples.
>>>
>>>
>>>
>>>
>>> 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
>


From nobody Sat Sep 26 04:29:02 2015
Return-Path: <marie@mjmontpetit.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587811B2CC3 for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 04:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n58Hfj2FGj3F for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 04:28:59 -0700 (PDT)
Received: from mail-qg0-f41.google.com (mail-qg0-f41.google.com [209.85.192.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F5621B2CC2 for <taps@ietf.org>; Sat, 26 Sep 2015 04:28:59 -0700 (PDT)
Received: by qgx61 with SMTP id 61so88506231qgx.3 for <taps@ietf.org>; Sat, 26 Sep 2015 04:28:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=fUSde3c5d0cx84D+VG+aaOmnPJd2elAn6o1MkBXApZo=; b=PV3w9bXrTqX5xEVktUItuW2BVKiQw86KQbtXlu5TDM9C6S+whmmdNAX/5notlrE6Al +GP8zzBRFDylHN3SKMJfAF6RsdbsxtYyS4RLLv2QgDAPHVUVDy4KL/yyaFJYpoyjX7DJ cBPnWLODgd+liVjupnk3hm6C6uOtAIjktD5J73S3NE+wdzQSQ2U8AIh846L1gmEOp0zG gysnI+19MgRwOsdcKcRV96drTAGTHL4eDv0KAHQMYSnE7WG9GFspTGE66tXI/Vyxao5g wpK+LHtAHFgqb5obBQ6ca8BeBQnQBws6LEjK2VZTAEUi/NUc0iUcvc/9VhaKUIEbgtQW 5RgQ==
X-Gm-Message-State: ALoCoQlhSUFrW0lHaVtoGwA8/zxH8TOFdZ9WzxEd1EZhoOzmh3R+8ypTQa8QkVExUyL7MywernRv
X-Received: by 10.140.104.51 with SMTP id z48mr11299730qge.21.1443266938312; Sat, 26 Sep 2015 04:28:58 -0700 (PDT)
Received: from [10.0.1.21] (c-76-118-234-192.hsd1.ma.comcast.net. [76.118.234.192]) by smtp.gmail.com with ESMTPSA id 188sm3260280qht.21.2015.09.26.04.28.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 26 Sep 2015 04:28:57 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset=iso-8859-1
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
X-Priority: 3 (Normal)
In-Reply-To: <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk>
Date: Sat, 26 Sep 2015 07:28:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <435C039A-5B01-450B-9223-883194F0B94D@mjmontpetit.com>
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no> <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com> <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/mVFhkpUzrWYiAKNouoGxHjc50_o>
Cc: Michael Welzl <michawe@ifi.uio.no>, taps WG <taps@ietf.org>
Subject: Re: [Taps] Fwd: New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Sep 2015 11:29:01 -0000

Makes sense.=20

> On Sep 26, 2015, at 3:17 AM, gorry@erg.abdn.ac.uk wrote:
>=20
> We seem to have two documents in a space where we started with one. =
These
> are different, to me this is OK. Both seem close to charter milestone =
1. I
> don't see much overlap between the contents of the descriptive =
language
> and the API-focussed analysis, and any overlap could be eliminated.
>=20
> To me, doc 1 (current chartered item) can evolve to provide background =
and
> missing documentation for anyone in the IETF, and should compare=20
> transports in a broad way and draw out the idea that they provide
> services. This appears to be harder to get right than I for one had =
hoped,
> and still has a wide scope. Not a bad thing. I suggest it will provide =
a
> reference to stop us rat-holing when people ask what is "this" and =
explain
> how all these transports stack-up against one another (good pun?). We =
can
> (I suggest) finish this doc in this way.
>=20
> I do like the idea of a second document focussed ONLY on the Transport =
API
> (I'd call this 1a). In this we can avoid this"discussion of what are
> transports"  and move to  a  more focussed  process in doc 1b,  Most =
of
> that troublesome descriptive  text can go into 1, and ensure we keep =
that
> one readable to anyone in the  IETF.
>=20
> Could  I suggest the two docs against the first milestone will help us
> make  progress towards the next milestone faster. (Assuming we can =
keep
> the two aligned, which seems quite doable). I can see also how the  =
docs
> are useful to different people. I'd like to see both mature and =
provide
> inputs to move forward.
>=20
> Gorry
>=20
>=20
>> Interesting and inline to getting transport API(s)
>>=20
>> Marie-Jos=C3=A9 Montpetit
>> marie@mjmontpetit.com
>> mariejo@mit.edu
>>=20
>>> On Sep 21, 2015, at 04:44, Michael Welzl <michawe@ifi.uio.no> wrote:
>>>=20
>>> Dear all,
>>>=20
>>> In my presentation in Prague, I proposed an approach to identify the
>>> services that transport protocols provide. At the end of the ensuing
>>> discussion, I said that I (with co-authors) would write a draft that
>>> explains the proposal by applying the proposed method to TCP and =
SCTP.
>>>=20
>>> We just submitted this document - see below;  I hope that this will =
lead
>>> to some discussion on the list...
>>>=20
>>> Cheers,
>>> Michael
>>>=20
>>>=20
>>>> Begin forwarded message:
>>>>=20
>>>> From: <internet-drafts@ietf.org>
>>>> Subject: New Version Notification for
>>>> draft-welzl-taps-transports-00.txt
>>>> Date: 21 Sep 2015 10:35:33 CEST
>>>> To: Michael Welzl <michawe@ifi.uio.no>, Michael Welzl
>>>> <michawe@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>, Naeem
>>>> Khademi <naeemk@ifi.uio.no>, Michael Tuexen =
<tuexen@fh-muenster.de>,
>>>> Naeem Khademi <naeemk@ifi.uio.no>
>>>> Resent-From: <michawe@ifi.uio.no>
>>>>=20
>>>>=20
>>>> A new version of I-D, draft-welzl-taps-transports-00.txt
>>>> has been successfully submitted by Michael Welzl and posted to the
>>>> IETF repository.
>>>>=20
>>>> Name:        draft-welzl-taps-transports
>>>> Revision:    00
>>>> Title:        An Approach to Identify Services Provided by IETF
>>>> Transport Protocols and Congestion Control Mechanisms
>>>> Document date:    2015-09-21
>>>> Group:        Individual Submission
>>>> Pages:        23
>>>> URL:
>>>> =
https://www.ietf.org/internet-drafts/draft-welzl-taps-transports-00.txt
>>>> Status:
>>>> https://datatracker.ietf.org/doc/draft-welzl-taps-transports/
>>>> Htmlized:
>>>> https://tools.ietf.org/html/draft-welzl-taps-transports-00
>>>>=20
>>>>=20
>>>> Abstract:
>>>> This document describes a method to identify services in transport
>>>> protocols and congestion control mechanisms.  It shows the approach
>>>> using TCP and SCTP (base protocol) as examples.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> 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.
>>>>=20
>>>> The IETF Secretariat
>>>=20
>>> _______________________________________________
>>> Taps mailing list
>>> Taps@ietf.org
>>> https://www.ietf.org/mailman/listinfo/taps
>>=20
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org
>> https://www.ietf.org/mailman/listinfo/taps
>>=20
>=20


From nobody Sat Sep 26 07:50:27 2015
Return-Path: <michawe@ifi.uio.no>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E27D01B2EA4 for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 07:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LquB58V6JbCb for <taps@ietfa.amsl.com>; Sat, 26 Sep 2015 07:50:23 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC9B91B2EA3 for <taps@ietf.org>; Sat, 26 Sep 2015 07:50:22 -0700 (PDT)
Received: from mail-mx2.uio.no ([129.240.10.30]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1Zfqnr-0005od-Uh; Sat, 26 Sep 2015 16:50:19 +0200
Received: from 089144206220.atnat0015.highway.bob.at ([89.144.206.220] helo=[192.168.0.101]) by mail-mx2.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1Zfqnp-0000mF-R2; Sat, 26 Sep 2015 16:50:19 +0200
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Welzl <michawe@ifi.uio.no>
X-Priority: 3 (Normal)
In-Reply-To: <435C039A-5B01-450B-9223-883194F0B94D@mjmontpetit.com>
Date: Sat, 26 Sep 2015 16:50:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCE21679-705E-4B51-B946-95D80A7EAE1A@ifi.uio.no>
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no> <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com> <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk> <435C039A-5B01-450B-9223-883194F0B94D@mjmontpetit.com>
To: Marie-Jose Montpetit <marie@mjmontpetit.com>
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 3 msgs/h 1 sum rcpts/h 4 sum msgs/h 1 total rcpts 33604 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: D6280D2F40BF78845F26265BFD458F90641BA207
X-UiO-SPAM-Test: remote_host: 89.144.206.220 spam_score: -49 maxlevel 80 minaction 2 bait 0 blacklist 0 greylist 0 ratelimit 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/KgHjircktFSVKSep_dZM134zb6A>
Cc: "<gorry@erg.abdn.ac.uk> Fairhurst" <gorry@erg.abdn.ac.uk>, "taps@ietf.org" <taps@ietf.org>
Subject: Re: [Taps] New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Sep 2015 14:50:26 -0000

+1

> On 26. sep. 2015, at 13.28, Marie-Jose Montpetit =
<marie@mjmontpetit.com> wrote:
>=20
> Makes sense.=20
>=20
>> On Sep 26, 2015, at 3:17 AM, gorry@erg.abdn.ac.uk wrote:
>>=20
>> We seem to have two documents in a space where we started with one. =
These
>> are different, to me this is OK. Both seem close to charter milestone =
1. I
>> don't see much overlap between the contents of the descriptive =
language
>> and the API-focussed analysis, and any overlap could be eliminated.
>>=20
>> To me, doc 1 (current chartered item) can evolve to provide =
background and
>> missing documentation for anyone in the IETF, and should compare=20
>> transports in a broad way and draw out the idea that they provide
>> services. This appears to be harder to get right than I for one had =
hoped,
>> and still has a wide scope. Not a bad thing. I suggest it will =
provide a
>> reference to stop us rat-holing when people ask what is "this" and =
explain
>> how all these transports stack-up against one another (good pun?). We =
can
>> (I suggest) finish this doc in this way.
>>=20
>> I do like the idea of a second document focussed ONLY on the =
Transport API
>> (I'd call this 1a). In this we can avoid this"discussion of what are
>> transports"  and move to  a  more focussed  process in doc 1b,  Most =
of
>> that troublesome descriptive  text can go into 1, and ensure we keep =
that
>> one readable to anyone in the  IETF.
>>=20
>> Could  I suggest the two docs against the first milestone will help =
us
>> make  progress towards the next milestone faster. (Assuming we can =
keep
>> the two aligned, which seems quite doable). I can see also how the  =
docs
>> are useful to different people. I'd like to see both mature and =
provide
>> inputs to move forward.
>>=20
>> Gorry
>>=20
>>=20
>>> Interesting and inline to getting transport API(s)
>>>=20
>>> Marie-Jos=C3=A9 Montpetit
>>> marie@mjmontpetit.com
>>> mariejo@mit.edu
>>>=20
>>>> On Sep 21, 2015, at 04:44, Michael Welzl <michawe@ifi.uio.no> =
wrote:
>>>>=20
>>>> Dear all,
>>>>=20
>>>> In my presentation in Prague, I proposed an approach to identify =
the
>>>> services that transport protocols provide. At the end of the =
ensuing
>>>> discussion, I said that I (with co-authors) would write a draft =
that
>>>> explains the proposal by applying the proposed method to TCP and =
SCTP.
>>>>=20
>>>> We just submitted this document - see below;  I hope that this will =
lead
>>>> to some discussion on the list...
>>>>=20
>>>> Cheers,
>>>> Michael
>>>>=20
>>>>=20
>>>>> Begin forwarded message:
>>>>>=20
>>>>> From: <internet-drafts@ietf.org>
>>>>> Subject: New Version Notification for
>>>>> draft-welzl-taps-transports-00.txt
>>>>> Date: 21 Sep 2015 10:35:33 CEST
>>>>> To: Michael Welzl <michawe@ifi.uio.no>, Michael Welzl
>>>>> <michawe@ifi.uio.no>, Michael Tuexen <tuexen@fh-muenster.de>, =
Naeem
>>>>> Khademi <naeemk@ifi.uio.no>, Michael Tuexen =
<tuexen@fh-muenster.de>,
>>>>> Naeem Khademi <naeemk@ifi.uio.no>
>>>>> Resent-From: <michawe@ifi.uio.no>
>>>>>=20
>>>>>=20
>>>>> A new version of I-D, draft-welzl-taps-transports-00.txt
>>>>> has been successfully submitted by Michael Welzl and posted to the
>>>>> IETF repository.
>>>>>=20
>>>>> Name:        draft-welzl-taps-transports
>>>>> Revision:    00
>>>>> Title:        An Approach to Identify Services Provided by IETF
>>>>> Transport Protocols and Congestion Control Mechanisms
>>>>> Document date:    2015-09-21
>>>>> Group:        Individual Submission
>>>>> Pages:        23
>>>>> URL:
>>>>> =
https://www.ietf.org/internet-drafts/draft-welzl-taps-transports-00.txt
>>>>> Status:
>>>>> https://datatracker.ietf.org/doc/draft-welzl-taps-transports/
>>>>> Htmlized:
>>>>> https://tools.ietf.org/html/draft-welzl-taps-transports-00
>>>>>=20
>>>>>=20
>>>>> Abstract:
>>>>> This document describes a method to identify services in transport
>>>>> protocols and congestion control mechanisms.  It shows the =
approach
>>>>> using TCP and SCTP (base protocol) as examples.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> The IETF Secretariat
>>>>=20
>>>> _______________________________________________
>>>> Taps mailing list
>>>> Taps@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/taps
>>>=20
>>> _______________________________________________
>>> Taps mailing list
>>> Taps@ietf.org
>>> https://www.ietf.org/mailman/listinfo/taps
>>>=20
>>=20
>=20

