From nobody Wed Oct 18 10:05:41 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A4D68132C2A; Wed, 18 Oct 2017 10:05:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150834634067.12470.17507962567351566281.idtracker@ietfa.amsl.com> Date: Wed, 18 Oct 2017 10:05:40 -0700 Archived-At: Subject: [Taps] The TAPS WG has placed draft-gjessing-taps-minset in state "Adopted by a WG" X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 17:05:40 -0000 The TAPS WG has placed draft-gjessing-taps-minset in state Adopted by a WG (entered by Aaron Falk) The document is available at https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/ Comment: >From the minutes at https://datatracker.ietf.org/meeting/99/materials/minutes-99-taps/: *** Chairs call for consensus: Please hum if you support adoption? (dozens) Please hum if you do NOT support adoption? (few) We have consensus to adopt. *** From nobody Fri Oct 20 17:31:20 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FBBB13457F; Fri, 20 Oct 2017 17:24:30 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: spencerdawkins.ietf@gmail.com, taps@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150854547025.20809.12531279577237853581.idtracker@ietfa.amsl.com> Date: Fri, 20 Oct 2017 17:24:30 -0700 Archived-At: Subject: [Taps] taps - Requested session has been scheduled for IETF 100 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 00:24:30 -0000 Dear Aaron Falk, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. taps Session 1 (2:30:00) Tuesday, Morning Session I 0930-1200 Room Name: Olivia size: 150 --------------------------------------------- Request Information: --------------------------------------------------------- Working Group Name: Transport Services Area Name: Transport Area Session Requester: Aaron Falk Number of Sessions: 1 Length of Session(s): 2.5 Hours Number of Attendees: 80 Conflicts to Avoid: First Priority: maprg dispatch tcpm iccrg tsvwg ippm rmcat aqm tsvarea quic Second Priority: webpush tcpinc nvo3 mptcp icnrg httpbis dots i2nsf ideas Third Priority: mmusic tram sacm mile ipwave cfrg saag People who must be present: Aaron Falk Michael Welzl Spencer Dawkins Brian Trammell Zaheduzzaman Sarker Mirja Kuehlewind Tommy Pauly Resources Requested: Experimental Room Setup (U-Shape and classroom, subject to availability) Special Requests: U-shaped room would be nice, not required. --------------------------------------------------------- From nobody Sun Oct 22 16:43:36 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F99413C09F; Sun, 22 Oct 2017 16:43:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: taps@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150871580801.24896.1276317669567869148@ietfa.amsl.com> Date: Sun, 22 Oct 2017 16:43:28 -0700 Archived-At: Subject: [Taps] I-D Action: draft-ietf-taps-minset-00.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 23:43:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Services WG of the IETF. Title : A Minimal Set of Transport Services for TAPS Systems Authors : Michael Welzl Stein Gjessing Filename : draft-ietf-taps-minset-00.txt Pages : 53 Date : 2017-10-22 Abstract: This draft recommends a minimal set of IETF Transport Services offered by end systems supporting TAPS, and gives guidance on choosing among the available mechanisms and protocols. It is based on the set of transport features given in the TAPS document draft- ietf-taps-transports-usage-08. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-minset/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-taps-minset-00 https://datatracker.ietf.org/doc/html/draft-ietf-taps-minset-00 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Oct 23 01:38:08 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F7D13F0A0 for ; Mon, 23 Oct 2017 01:38:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 C7s8wFXHtF-b for ; Mon, 23 Oct 2017 01:38:04 -0700 (PDT) Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 5985F13F09C for ; Mon, 23 Oct 2017 01:38:04 -0700 (PDT) Received: from mail-mx01.uio.no ([129.240.10.26]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1e6YFF-000BdO-M9 for taps@ietf.org; Mon, 23 Oct 2017 10:38:01 +0200 Received: from [85.119.46.8] (helo=[172.23.14.248]) by mail-mx01.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1e6YFE-0001hH-NY for taps@ietf.org; Mon, 23 Oct 2017 10:38:01 +0200 From: Michael Welzl Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Mon, 23 Oct 2017 10:38:01 +0200 References: <150871580801.24896.1276317669567869148@ietfa.amsl.com> To: "taps@ietf.org" In-Reply-To: <150871580801.24896.1276317669567869148@ietfa.amsl.com> Message-Id: <7403AB1A-33FC-461A-B88F-B8DB8FC08881@ifi.uio.no> X-Mailer: Apple Mail (2.3273) X-UiO-SPF-Received: Received-SPF: neutral (mail-mx01.uio.no: 85.119.46.8 is neither permitted nor denied by domain of ifi.uio.no) client-ip=85.119.46.8; envelope-from=michawe@ifi.uio.no; helo=[172.23.14.248]; 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: 8A77D2E39A36A984D632A25796F08A2B45C44666 Archived-At: Subject: Re: [Taps] I-D Action: draft-ietf-taps-minset-00.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 08:38:07 -0000 Hi everyone, This update addresses 2 out of 3 major comments that we got at the last = meeting: 1) also fall-back to UDP =3D> done. This turned out to be much easier = than I thought because the set of transport features for which TCP is a = possible fall-back is, with *one* exception (receiving a message) = strictly a superset of transport features for which UDP is a possible = fall-back. Sorry for the clumsy sentence but the point is, TCP itself = is of course *not* strictly a superset of UDP itself, but that doesn=E2=80= =99t matter. Anyway, because of this superset relationship, we were = able to just mark limitations that arise when requiring to fall back to = UDP with (!UDP). 2) make it clearer that the abstract interface description of the min = set is *not* an API proposal =3D> done. I hope this is now clear enough = for folks. 3) make it less TCP-specific, also consider fall-back to e.g. TLS =3D> = not done. Maybe next time? Thanks for the very useful feedback, everyone who was there last time! Also, there are now considerations on how to begin. With the minset as = it was, it is possible for TAPS to choose UDP as a protocol and for the = application to later request reliability. At least such deadlocks must = be prevented - I=E2=80=99m not claiming that what we put in there is = generally ideal (in fact the text explains why it isn=E2=80=99t), but it = is one possible approach that avoids such deadlocks. Chairs: I=E2=80=99d like to request a 20-minute slot for this update, if = possible (I think this should be enough including discussions, as my = presentation would probably fit in about 10 minutes). Cheers, Michael > On Oct 23, 2017, at 1:43 AM, internet-drafts@ietf.org wrote: >=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 WG of the IETF. >=20 > Title : A Minimal Set of Transport Services for TAPS = Systems > Authors : Michael Welzl > Stein Gjessing > Filename : draft-ietf-taps-minset-00.txt > Pages : 53 > Date : 2017-10-22 >=20 > Abstract: > This draft recommends a minimal set of IETF Transport Services > offered by end systems supporting TAPS, and gives guidance on > choosing among the available mechanisms and protocols. It is based > on the set of transport features given in the TAPS document draft- > ietf-taps-transports-usage-08. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-taps-minset/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-taps-minset-00 > https://datatracker.ietf.org/doc/html/draft-ietf-taps-minset-00 >=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 From nobody Mon Oct 23 08:22:36 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6FF4139438 for ; Mon, 23 Oct 2017 08:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.101 X-Spam-Level: X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 1u4NcT0L4QqI for ; Mon, 23 Oct 2017 08:22:34 -0700 (PDT) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 97FA5139428 for ; Mon, 23 Oct 2017 08:22:34 -0700 (PDT) Received: by mail-qt0-x234.google.com with SMTP id 31so26565865qtz.9 for ; Mon, 23 Oct 2017 08:22:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=CHDTKgU6PUcXvXRUg8KDjvXWl8D+wzo2eNIv8fbPG6w=; b=mynGeiBOYe+AzShJQBsoRkPBN++4/K3IaXVyN2UaMDOqkA+Ag7xY+G2xIF4Gy+Vfma bXu2qOW47CsSlgsElCg63VmXqlk1fQYhUTk0LGc16Ygf9GLPjtu9LO17gzvrT/cRIT5a itYB2UCBRGgatESmiREk6L44Q2O1VZEyxG0ErgybOpbXQyLmAovBpBhqN0tTgXgkMvri BatUSZFXCggQaDJn1J5LpxZFX1gP7eKxP4UTN8thXuyM55IhX/mQEIO9L80EhT1egFwF iCztDMeQ0KX172ualdAFAlNlesKhZJNwLYCSsVFobA+kKzxBaDVjhZKWYDzIR8rwODC6 tOLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=CHDTKgU6PUcXvXRUg8KDjvXWl8D+wzo2eNIv8fbPG6w=; b=RiawWth1U88LzzET5uuUzpQp282RocbblJ8Upl5YkJvbEeoNJzoQKMCc10o2341Eip IzXtRt94kSCFHv5MyN8sUDB3W1uG/TM4s5xl4+KDJubanjNK7SvPWa4JU+MrV4Nvvcf2 Wfn/RucF3Ykg3p33kEtiqP1lHfKArHJOyb31En9NA0Lsq0oqSfqaI0jMVuX3sB8LIfP+ v0+0kXRT1d91aCfxSR6BgTw7hres+NC5vHkUnWu7x5MIAxxTnO7E8wrL0hE0B+Vx8F7I Rdye79PwA9czLdqr96ZV+gTvGs6srFXtws8oV1qPErkuJMjt0ycQQoGW3lT7M4u+aEdU JuVA== X-Gm-Message-State: AMCzsaXDdnQoOrD8hyGvNwW7wayxbAtAlerMJDi7dWvzk0GI670erqRR L+YpkboYcShGXiQ+jMyor9rD8pka X-Google-Smtp-Source: ABhQp+S+hJ5HsZXz0Ot5Ulx+Ehk2DjLZ6vkDl2J8UPLjMB+tDHqb/nOp9QexGNDJaSxkNd86VG/Inw== X-Received: by 10.200.6.136 with SMTP id f8mr17015563qth.265.1508772153302; Mon, 23 Oct 2017 08:22:33 -0700 (PDT) Received: from [172.19.35.215] ([2601:184:4980:a321:bc29:6e4b:a04a:dac9]) by smtp.gmail.com with ESMTPSA id n186sm4759130qkd.20.2017.10.23.08.22.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Oct 2017 08:22:32 -0700 (PDT) From: "Aaron Falk" To: "taps WG" Cc: "Zaheduzzaman Sarker" Date: Mon, 23 Oct 2017 11:22:47 -0400 Message-ID: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; markup=markdown Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.7r5425) Archived-At: Subject: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 15:22:36 -0000 Please send your interest for TAPS agenda time. Already have: draft-ietf-taps-minset-00.txt Thanks, —aaron From nobody Mon Oct 23 22:54:49 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0953D13BB74 for ; Mon, 23 Oct 2017 22:54:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ioWzxcMqlpV8 for ; Mon, 23 Oct 2017 22:54:46 -0700 (PDT) Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30FFA13AE04 for ; Mon, 23 Oct 2017 22:54:46 -0700 (PDT) Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id E9DE03404D5; Tue, 24 Oct 2017 07:54:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.19437); Tue, 24 Oct 2017 07:54:44 +0200 (CEST) Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue, 24 Oct 2017 07:54:44 +0200 (CEST) Received: from dhcp-24-116.ripemtg.ripe.net (account ietf@trammell.ch [193.0.24.116] verified) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 33679438; Tue, 24 Oct 2017 07:54:44 +0200 From: "Brian Trammell (IETF)" Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_AA9A5A48-2EA9-4681-A910-5D379795A758"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Tue, 24 Oct 2017 09:54:45 +0400 In-Reply-To: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> Cc: taps WG , Zaheduzzaman Sarker To: Aaron Falk References: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 05:54:48 -0000 --Apple-Mail=_AA9A5A48-2EA9-4681-A910-5D379795A758 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 We'd like some time (~15-20 min) to talk about a soon-to-be-submitted = update to draft-trammell-taps-post-sockets. Thanks, cheers, Brian > On 23 Oct 2017, at 19:22, Aaron Falk wrote: >=20 > Please send your interest for TAPS agenda time. >=20 > Already have: draft-ietf-taps-minset-00.txt >=20 > Thanks, >=20 > =E2=80=94aaron >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps --Apple-Mail=_AA9A5A48-2EA9-4681-A910-5D379795A758 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlnu1aUACgkQihK3vwvq RqOWDQ//VWULfImjxTbs7UwjtC4eZ8oVK242xUQo0rgvLqCV8p89MpwabEiTUlbC bV/KCBNPMPsszEtDoPXzh49bAfpH8ZUreWL6HP/3WJB4MbdOXP6aiJbPXNsPMV1f I9mQ0JIY1aNSsy8yJSJyTz5/wV8RkpMiG3G06p/pcSrATmC4DwkpPD9E3AkRAwGy ijJF31iOG8t+gTfpIDEncIg++Wqsxhu8kF0XRvPagxUcofq9zXsGCoIXfCwQkGwb uB7Otbioeugp2UVAxgk/aoTIJ5ZBE6NW/9f6YeaMVqSu4jFEGnPrIqLvh93Irodz e09TLzIjjT1zaseLCjQajmYNm6BIDk6I+lKh/aFKYWimf2si0zU4g1KtrPNBFwbX 0u9tZHW2V6DoAxsmi3+0XyBNd36Oqya570K+MLHYr8FSfcWMpii33Xd3bV0NXm0E rYmad/LAyLc9SWOFhyTGkfpnoA45UtAeLjDVyrDu/1bkX9BxDzeeteiER3ObevVH eVi4HG7vw6iT0ZWzYuys04c93ulFTzX9r3LGgMyJV3NL7pYoFMM5D+b12MqtZk8/ sl0H7nvsKzM0aPrWrEutrNcg24ysmHUoi0Q74c1N+MPbDZVhhDfI0AMIS+ag2ghZ OMqAFWoVuVNvMxPwifJx1XhjOi6IbN0pL0demoGHbID2BRlqMBk= =O3wb -----END PGP SIGNATURE----- --Apple-Mail=_AA9A5A48-2EA9-4681-A910-5D379795A758-- From nobody Tue Oct 24 06:12:41 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7962313F629 for ; Tue, 24 Oct 2017 06:12:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 6lvHySP5es-j for ; Tue, 24 Oct 2017 06:12:38 -0700 (PDT) Received: from einhorn-mail.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 8A98113F619 for ; Tue, 24 Oct 2017 06:12:37 -0700 (PDT) X-Envelope-From: phils@in-panik.de Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id v9ODBsVE011058 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 24 Oct 2017 15:11:54 +0200 Received: from [2001:638:809:ff1f::8295:dc66] by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e6yzQ-0005aj-3W; Tue, 24 Oct 2017 15:11:28 +0200 From: "Philipp S. Tiesel" Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_B17B198A-6FB3-40B6-B33B-C47F9B77CBAF"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Date: Tue, 24 Oct 2017 15:11:44 +0200 In-Reply-To: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> Cc: taps WG , Zaheduzzaman Sarker To: Aaron Falk References: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> X-Mailer: Apple Mail (2.3445.1.7) Archived-At: Subject: Re: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 13:12:40 -0000 --Apple-Mail=_B17B198A-6FB3-40B6-B33B-C47F9B77CBAF Content-Type: multipart/alternative; boundary="Apple-Mail=_6D83E82A-CD25-4FB8-A2B2-2989ACB57007" --Apple-Mail=_6D83E82A-CD25-4FB8-A2B2-2989ACB57007 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 We=E2=80=99l like some time (~15-20min) to discuss our = soon-to-be-submitted update to draft-tiesel-taps-socketintents. Details and questions i would like to discuss will follow with the = update. AVE! Philipp S. Tiesel / phils=E2=80=A6 > On 23. Oct 2017, at 17:22, Aaron Falk wrote: >=20 > Please send your interest for TAPS agenda time. >=20 > Already have: draft-ietf-taps-minset-00.txt >=20 > Thanks, >=20 > =E2=80=94aaron >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps -- = {phils}--->---(phils@in-panik.de)--->---(http://phils.in-panik.de)----, wenn w eine aube ist dn man au dran dre en = | o Schr an muss hc h (Kurt = Schwitters) | :wq! <----(phone: +49-179-6737439)---<---(jabber: = phils@in-panik.de)----' --Apple-Mail=_6D83E82A-CD25-4FB8-A2B2-2989ACB57007 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 We=E2=80=99l like some time (~15-20min) to discuss our = soon-to-be-submitted update to draft-tiesel-taps-socketintents.

Details and questions i = would like to discuss will follow with the update.

AVE!
  Philipp S. = Tiesel / phils=E2=80=A6

On 23. Oct 2017, at 17:22, Aaron Falk <aaron.falk@gmail.com> wrote:

Please= send your interest for TAPS agenda time.

Already have: draft-ietf-taps-minset-00.txt

Thanks,

=E2=80=94aaron

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

-- 
   {phils}--->---(phils@in-panik.de)--->---(http://phils.in-panik.de)----,
  =     wenn w eine   aube ist dn      man au = dran dre en                 =   |
           o   =   Schr        an muss     hc   =       h   (Kurt Schwitters) |
:wq! =  <----(phone: +49-179-6737439)---<---(jabber: phils@in-panik.de)----'

= --Apple-Mail=_6D83E82A-CD25-4FB8-A2B2-2989ACB57007-- --Apple-Mail=_B17B198A-6FB3-40B6-B33B-C47F9B77CBAF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIzBAEBCAAdFiEEWxyORUfQrk93Q7or9/dp0G7BPC0FAlnvPBAACgkQ9/dp0G7B PC2GFA/8C6dCLRMyHVyjzPB4Pf/f8ZiJLp7sRTYBIkW1IRAZAodZLEe7WTNzgbFe RoSePNT6lplnw+Xkmbp5ISDiUjdoC9jVah5edlYwwVRKk9MXnREUpb2zuatRaZ42 S0/x6uYPjbtBuRIBj9hmRs8c9kFvF7nGYPvnrzk0HpyK0kRsODJ3I9D/4lctnDte 35afiom709YgGrXgNcRG7Cp0HLnFHLfYEF6JJwA/+TS0dyUD8EC83O1CTg/v0Ry9 29Pj7dfOL4Z9ceuBeadn/hHsGlHK/ExZpZZutOPehdtqTLojre3soGQEfGu3VRUg nKUS1clsvcrw/Djl88mv/tg9UchjYmqD4b/02/Vyl6Ciw8I/uxLlNf4IHzO2ZYdJ wQ69HqwEwzbLSKz6CVI/n7BKslrMj+HwAx/G6zqGMZmmF2vGbVncMtBFgaGr+F7d UxhSlfcO3Fx1HSgaWAfJ5I4fd979R8fvTxEYLuwZDwhakpgzwACy6/DD0I0Mm3Xd jEez5J3VOGSEwrd8NTu/mm4dYxCUAoFWA4ck7+MHr48b7v/QByE+4SbAZBNWEmr6 /HcA2wzb/kzIHGshEJOPlHYr6QQq6uTR08QHIS1ahT055acDTSeHkHFGTDDMZuSO w9XCLYtAsjXlxHgWr85Xui3bfJF+fg1+bF5Of3RI1EHnvTsJV88= =wx8e -----END PGP SIGNATURE----- --Apple-Mail=_B17B198A-6FB3-40B6-B33B-C47F9B77CBAF-- From nobody Tue Oct 24 11:34:52 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D0B139672; Tue, 24 Oct 2017 11:34:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 JYn-wPVl72vd; Tue, 24 Oct 2017 11:34:45 -0700 (PDT) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 B48161395E9; Tue, 24 Oct 2017 11:34:44 -0700 (PDT) Received: by mail-yw0-x229.google.com with SMTP id q126so12985374ywq.10; Tue, 24 Oct 2017 11:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aPkxT4hHET7mvXsVjzqzDAd9IcilHlBa680rSJbE7d4=; b=f3J4r8hDVf9igZZ+BISvmxINVIfpkXhxvyKI0UgjRydn8JtOmq9IcTHgruqMAlB7hK UJxtx9ARmSnk2sQ5eexvmORoILbDm2fqjTJBwXqqgIEF/YJJr+ab5KxKfBGC93ztzEGX ysfqD6/21OP0PaHoMYATeHnKS48Tg0AOIfmvVnFy1XiOZ1UgQF27f+91EjCgJGZVf0ye 7Ljxsl8I+aX5zcpoNdpKy04+ZD7zwjTcTXFNuZ+4d17sHiHrgF64PU3ihEvUpkHbZdCS R9P6ueQIJQ7LdDSwSgyytRr4/15w94IrO87+cde5yumCNUsEcNboyBKdhNhZQwLUP9Ol lowg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aPkxT4hHET7mvXsVjzqzDAd9IcilHlBa680rSJbE7d4=; b=TWx5DVEoDc5j0wWknxKH6SssKiMQFbCCrrmJS8/29IpY//K3Z1bH93gtzOOpDJmOBJ NmTuLcDPhsAFREWrcQKbsKT/bqu7FVH9yQ/k04+ATQi8LQdbEtjBvvlVA7RgD9RMrSJv XNqgJ3TO/hQHAOJVIiTEXx3zs4TFZdrVbCfG5AlRJUNTl+YdsRH3j6B5WjGs7vJHzaMX Iy27CabXq84RjmpjRwLcLFISPJJfb68lF/nWcaX0tbvqA8yGd3fWi4w37nzR8XQKR67X XMiGfEGY+Zbrq4GL3pipG+dQAWNPjop0nMvnfWu0TX/HRidHRxt9LnGvf+6r0nbaSy8x 2Qog== X-Gm-Message-State: AMCzsaUneZt858Ztm9gvwqXF9XbBW5d7mEBrWpVYijRLNouGaA1AZg46 g8ybvuEsvEAlPi+SZuYc0FESrxZVwB4okaVheuM= X-Google-Smtp-Source: ABhQp+QeSJnt6zWX7oXRgafVFHES7FG/QiunvWgXtbzPNgxU+qdu1P8TeC9TW8taUNqROujuWUFIKdy2ej/1p0JPvSU= X-Received: by 10.129.208.7 with SMTP id v7mr11766917ywi.454.1508870083678; Tue, 24 Oct 2017 11:34:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.87.131 with HTTP; Tue, 24 Oct 2017 11:34:43 -0700 (PDT) In-Reply-To: References: From: Spencer Dawkins at IETF Date: Tue, 24 Oct 2017 13:34:43 -0500 Message-ID: To: "taps@ietf.org" Cc: taps-chairs@ietf.org Content-Type: multipart/alternative; boundary="94eb2c1a52ee59970b055c4f31c6" Archived-At: Subject: Re: [Taps] One RFC, or two, for draft-ietf-taps-transports-usage and draft-ietf-taps-transports-usage-udp X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 18:34:47 -0000 --94eb2c1a52ee59970b055c4f31c6 Content-Type: text/plain; charset="UTF-8" Just to make a long-delayed decision ... Based on responses to my question to TAPS about whether draft-ietf-taps-transports-usage-udp should be folded into draft-ietf-taps-transports-usage, I am seeing no support in the working group for that, and reasons why the draft-ietf-taps-transports-usage-udp draft is useful without reference to the draft-ietf-taps-transports-usage. For these reasons, I ask that the authors submit an updated draft-ietf-taps-transports-usage draft, taking into account the ballot comments from Eric, Mirja, Ben, and Benoit. I see that the draft-ietf-taps-transports-usage-udp draft has already been updated to reflect comments received during balloting. I'll send the Approved e-mails for both drafts as a set. Thanks to everyone who provided input. Spencer, as AD On Wed, Sep 13, 2017 at 11:47 PM, Spencer Dawkins at IETF < spencerdawkins.ietf@gmail.com> wrote: > Dear TAPS working group, > > Multiple ADs have asked why these two drafts aren't a single draft, in > their ballots. Those are non-blocking comments, but I'd like to explore > that, before making a decision about what should happen, and when. > > It occurs to me that these ADs are reading both drafts pretty much > back-to-back in preparation for balloting during IESG Evaluation. > > If people reading the two drafts back-to-back find the split to be a > distraction, I'd like to understand the views of the working group as to > how often you expect people to read both drafts, in order to do TAPS. > > I could imagine that people working on complete TAPS APIs might need to > read both drafts. > > What about other folks you expect to read these documents? Do you expect > that some communities only need to read one of them? > > Thanks in advance for any thoughts you can share. > > Spencer, as responsible AD for TAPS > --94eb2c1a52ee59970b055c4f31c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just to make a long-delayed decision ...

Based on responses to my question to TAPS about whether draft-ietf-t= aps-transports-usage-udp should be folded into draft-ietf-taps-transpo= rts-usage, I am seeing no support in the working group for that, and r= easons why the draft-ietf-taps-transports-usage-udp draft is useful wi= thout reference to the draft-ietf-taps-transports-usage.
For these reasons, I ask that the authors submit an updated dra= ft-ietf-taps-transports-usage draft, taking into account the ballot co= mments from Eric, Mirja, Ben, and Benoit.

I see th= at the draft-ietf-taps-transports-usage-udp draft has already been upd= ated to reflect comments received during balloting. I'll send the Appro= ved e-mails for both drafts as a set.

Thanks to ev= eryone who provided input.

Spencer, as AD

On Wed, Sep 13, 2017= at 11:47 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gma= il.com> wrote:
Dear TAPS working group,

Mu= ltiple ADs have asked why these two drafts aren't a single draft, in th= eir ballots. Those are non-blocking comments, but I'd like to explore t= hat, before making a decision about what should happen, and when.

It occurs to me that these ADs are reading both drafts pret= ty much back-to-back in preparation for balloting during IESG Evaluation.

If people reading the two drafts back-to-back find = the split to be a distraction, I'd like to understand the views of the = working group as to how often you expect people to read both drafts, in ord= er to do TAPS.

I could imagine that people working= on complete TAPS APIs might need to read both drafts.=C2=A0

=
What about other folks you expect to read these documents? Do yo= u expect that some communities only need to read one of them?
Thanks in advance for any thoughts you can share.
Spencer, as responsible AD for TAPS

--94eb2c1a52ee59970b055c4f31c6-- From nobody Tue Oct 24 21:54:08 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491C1139605 for ; Tue, 24 Oct 2017 21:54:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com 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 jX0NDXBaI-cR for ; Tue, 24 Oct 2017 21:54:05 -0700 (PDT) Received: from mail-in21.apple.com (mail-out21.apple.com [17.171.2.31]) (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 5478F139203 for ; Tue, 24 Oct 2017 21:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1508907242; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=AFxBVWadR+IP1XVjsNweyTVq4DKOOI+Il3YoF7LDBNw=; b=qQjyRAGvW0PJEajxvOP9LT6wMKnHuW1EHBf6Msm7tO7Du75LuESooS8ZO4cqKaYY MXSauQ1sKJ4dD6fuvtB9m+bcYrH4ENaQgxTb49TXsFGcZy6O9l3dgEPMPtF7Wx5u 52Q0K21n3eOk6ionpQQRP7i47NE1Q4RqZDRiFzVRVQC5jfY+v1yJfsVZ2KFLjD9Z iz8+3RFCsqmrvkr0HSydp7z16Z76lClcn1w82PjR4q9oz2AV8I7cSbRfJAnaLFcP O9rYeaLHYxIqcItIy6BT6/RVid2q8MVLE0A7fGgE874SYyIMGxTMQeLnnaEx7xXB UE9IkWaW7Np1jZa0IOPE9A==; Received: from relay4.apple.com (relay4.apple.com [17.128.113.87]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in21.apple.com (Apple Secure Mail Relay) with SMTP id AA.D1.06971.AE810F95; Tue, 24 Oct 2017 21:54:02 -0700 (PDT) X-AuditID: 11ab0215-192469c000001b3b-58-59f018eaff0e Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by relay4.apple.com (Apple SCV relay) with SMTP id 09.1E.31187.9E810F95; Tue, 24 Oct 2017 21:54:01 -0700 (PDT) MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_4Aqq9kDx9pdPLD3EfPcd6w)" Received: from [17.234.32.92] by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.1.3.20170825 64bit (built Aug 25 2017)) with ESMTPSA id <0OYD00HR94A1RU00@nwk-mmpp-sz11.apple.com>; Tue, 24 Oct 2017 21:54:01 -0700 (PDT) Sender: tpauly@apple.com From: Tommy Pauly Message-id: <5C6D34EE-355C-46E9-AD87-98D8F4002E5B@apple.com> Date: Tue, 24 Oct 2017 21:54:00 -0700 In-reply-to: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> Cc: taps WG , Zaheduzzaman Sarker To: Aaron Falk References: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> X-Mailer: Apple Mail (2.3445.5.5) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUi2FAYrvtK4kOkwatXChZtv6exWtyJsThy 6h2zA7PHr69X2Tx2zrrL7rFkyU+mAOYoLpuU1JzMstQifbsEroyt7z8xF8yUrJh9r4G5gXGL WBcjJ4eEgIlEd9tCxi5GLg4hgTVMEl0HvjHBJCbtvcAMkTjEKDGz4wtYgldAUOLH5HssIDaz QJjE7fPPWCGKvjBKHLjUAZTg4BAWkJDYvCcRpIZNQEXi+LcNzBC9NhJTnm5hB7GFBTQlTh+4 BTaHRUBVonXSXjYQm1PAVqLp5yZ2iPmhEvteLgSzRYBqlr1oB6sRApozuf0PI8ShihIPN3WB 3SAhsIBN4syrWcwTGIVmIbl1FpJbZwGdxyygLjFlSi5EWFviybsLrBC2msTC34uYkMUXMLKt YhTOTczM0c3MMzLUSywoyEnVS87P3cQIio7VTKI7GOe/MjzEKMDBqMTDmzHzfaQQa2JZcWXu IUZpDhYlcV7+l0AhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjPXVCeIfEhdOE99TWbes5/Fa cSOXQLuG6a+OT3/RfHoX84GD22Qf9XvoxTxeK+z8hHuel3xP3QauLP9alXVMt11PuvSnCS48 87i8kn/v8VlPyhbnvre0WvE7aW7fvpzPa1YvWXtgm+efdH8VtQrb8Iid13wlip+WxCaJPDxm xKrwL+/RDsX98UosxRmJhlrMRcWJANBhRytvAgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUi2FA8W/elxIdIg70dZhZtv6exWtyJsThy 6h2zA7PHr69X2Tx2zrrL7rFkyU+mAOYoLpuU1JzMstQifbsEroyt7z8xF8yUrJh9r4G5gXGL WBcjJ4eEgInEpL0XmLsYuTiEBA4xSszs+MIEkuAVEJT4MfkeC4jNLBAmcfv8M1aIoi+MEgcu dQAlODiEBSQkNu9JBKlhE1CROP5tAzNEr43ElKdb2EFsYQFNidMHboHNYRFQlWidtJcNxOYU sJVo+rmJHWJ+qMS+lwvBbBGgmmUv2sFqhIDmTG7/wwhxqKLEw01drBMY+WchOW8WkvNmAV3E LKAuMWVKLkRYW+LJuwusELaaxMLfi5iQxRcwsq1iFChKzUmsNNFLLCjISdVLzs/dxAgO5cLw HYz/llkdYhTgYFTi4c2Y+T5SiDWxrLgyFxhGHMxKIrwKr4BCvCmJlVWpRfnxRaU5qcWHGKU5 WJTEebdsBEoJpCeWpGanphakFsFkmTg4pRoY05ZyPnEQmqu4qc68ZcuN/8EtVRNeKzUfiZ43 9w2XzIyrvifE1xzgkLozR3zSgWkZnzdknOOMYBfg22+y6d+cs/ry3Xu530YUmDTklFg5bks/ UmX0sGRX4IYFnZuvtRVfzK1aw8Iuu1LVQj2iSfDf2c9blxh+6IxzzXY7c+Gj0HKmRpVE18rp SizFGYmGWsxFxYkAbewwumECAAA= Archived-At: Subject: Re: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2017 04:54:06 -0000 --Boundary_(ID_4Aqq9kDx9pdPLD3EfPcd6w) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable I've just revised my "guidelines" draft to be "Guidelines for Racing = During Connection Establishment": https://datatracker.ietf.org/doc/draft-pauly-taps-guidelines/ = https://tools.ietf.org/html/draft-pauly-taps-guidelines-01 = It would be useful to have a quick WG discussion (10-15 minutes?) on how = this work and the Protocol Happy Eyeballs draft can converge (we're = already discussing this), and how we want them to relate to other = documents. Best, Tommy > On Oct 23, 2017, at 8:22 AM, Aaron Falk wrote: >=20 > Please send your interest for TAPS agenda time. >=20 > Already have: draft-ietf-taps-minset-00.txt >=20 > Thanks, >=20 > =E2=80=94aaron >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps --Boundary_(ID_4Aqq9kDx9pdPLD3EfPcd6w) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable I've = just revised my "guidelines" draft to be "Guidelines for Racing During = Connection Establishment":

https://datatracker.ietf.org/doc/draft-pauly-taps-guidelines/
https://tools.ietf.org/html/draft-pauly-taps-guidelines-01<= /div>

It would be = useful to have a quick WG discussion (10-15 minutes?) on how this work = and the Protocol Happy Eyeballs draft can converge (we're already = discussing this), and how we want them to relate to other = documents.

Best,
Tommy

On Oct = 23, 2017, at 8:22 AM, Aaron Falk <aaron.falk@gmail.com> wrote:

Please= send your interest for TAPS agenda time.

Already have: draft-ietf-taps-minset-00.txt

Thanks,

=E2=80=94aaron

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

= --Boundary_(ID_4Aqq9kDx9pdPLD3EfPcd6w)-- From nobody Wed Oct 25 04:27:39 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA2D13AE08 for ; Wed, 25 Oct 2017 04:27:38 -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, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 84ul2L7jeFFX for ; Wed, 25 Oct 2017 04:27:36 -0700 (PDT) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 70B8C13B29C for ; Wed, 25 Oct 2017 04:27:36 -0700 (PDT) Received: by mail-lf0-x231.google.com with SMTP id w21so27468907lfc.6 for ; Wed, 25 Oct 2017 04:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=DvcpMvhdv04LHZe7Av4D+skilaqiONHMtYgfiGCn+20=; b=q8KIsHmPfeuYveX12uBqFs2APX8NG9/EnOQWXpQ56aJbUfO2LWwB0//l/qP3KgNtZO 3evBEczjrOMdP5yGg/xNilmQWG+aaTvaCdHqespjWRytycr2H8uvHDlqZDXbQzh2R2FD Tn8hz8g1oeTIL1MNsjyj1naKjWgBxAjpqulgkFWhiX4QJrPG/nq8QtWlb7kwcLLy3TRH w1oUN1nVkg6NdIOCTk4EfZghsh8WO5Ge9oNYC8OeGoZi4KIE6W7Us2vlh/uNiLdj8v4Z +e+0laoGm7qrrR0d14UhZnntEbouEKWqCVhokOrsiWniMoS/udjvawGrs0YM/bX5l1qz 1dpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=DvcpMvhdv04LHZe7Av4D+skilaqiONHMtYgfiGCn+20=; b=prLwjMrDIMzkhlAn99PfpXjygsoDDp/nWDXWPlaW/5yfhNoooMXdu1EGAcLqagfsn9 2jJ2UOkNSCaaTCqnlGO3CMw35lkXak9Im1kKIj5bAT1usXXToQaU3XymsqtJnfs3S2oZ 5ECqtybvz30FDTh2JzyX/59FlWNmigrS3Met2qT7mwVMKKLKErHTpSov8sAZZJ4HGnbi 6DcPOMxslwfUVeOP0FGlxSDvrHfzfomDCA5evsLY8d4C19oSKgoTKak/QV1G1UYiecJR fKKhIm5D+8yJDA33hQVDtT9HXzSKXWFxIPJvKmLftGsro4pspFKvURX0TVCwycruF/qo j/AQ== X-Gm-Message-State: AMCzsaVfOvP2P2syh5su4K55TeJJ0GsyvYdNsPfmlhaUCaZ8FEYZqp1W ep/uyEt+ZHULUkY9ewE0XDS1G3EDgJfwW5FphBM= X-Google-Smtp-Source: ABhQp+R/WisOMGAo5BN0SqVD+2QHQ96Qr5lMMfXTfR509E1yVQvVlLM9LKh0qsV75ALc0lJL79xoi3Dv3C+EHpMMSbg= X-Received: by 10.25.228.197 with SMTP id x66mr3315492lfi.231.1508930854562; Wed, 25 Oct 2017 04:27:34 -0700 (PDT) MIME-Version: 1.0 Sender: crowcroft@gmail.com Received: by 10.25.225.133 with HTTP; Wed, 25 Oct 2017 04:27:33 -0700 (PDT) In-Reply-To: <5C6D34EE-355C-46E9-AD87-98D8F4002E5B@apple.com> References: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> <5C6D34EE-355C-46E9-AD87-98D8F4002E5B@apple.com> From: Jon Crowcroft Date: Wed, 25 Oct 2017 12:27:33 +0100 X-Google-Sender-Auth: 8OVWMM4p1cWUkJZ_7o3xBSu137Y Message-ID: To: Tommy Pauly Cc: Aaron Falk , Zaheduzzaman Sarker , taps WG Content-Type: multipart/alternative; boundary="94eb2c0e7d8893b15c055c5d5775" Archived-At: Subject: Re: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2017 11:27:38 -0000 --94eb2c0e7d8893b15c055c5d5775 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable just one comment - this is confusing to people who care about race conditions in connection establishment protocols - you need to disambiguate competing (greedy parallel exploration of options) from "racing" somewhere in the doc:, i think:) On Wed, Oct 25, 2017 at 5:54 AM, Tommy Pauly wrote: > I've just revised my "guidelines" draft to be "Guidelines for Racing > During Connection Establishment": > > https://datatracker.ietf.org/doc/draft-pauly-taps-guidelines/ > https://tools.ietf.org/html/draft-pauly-taps-guidelines-01 > > It would be useful to have a quick WG discussion (10-15 minutes?) on how > this work and the Protocol Happy Eyeballs draft can converge (we're alrea= dy > discussing this), and how we want them to relate to other documents. > > Best, > Tommy > > > On Oct 23, 2017, at 8:22 AM, Aaron Falk wrote: > > Please send your interest for TAPS agenda time. > > Already have: draft-ietf-taps-minset-00.txt > > Thanks, > > =E2=80=94aaron > > _______________________________________________ > 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 > > --94eb2c0e7d8893b15c055c5d5775 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
just one comment - this is confusing to people who care ab= out race conditions in connection establishment protocols - you need to dis= ambiguate
competing (greedy parallel exploration of options) from "= ;racing" somewhere in the doc:, i think:)

On Wed, Oct 25, 2017 at 5:54 AM, T= ommy Pauly <tpauly@apple.com> wrote:
= I've just revised my "guidelines" draft to be "Guideline= s for Racing During Connection Establishment":


It would be useful to have= a quick WG discussion (10-15 minutes?) on how this work and the Protocol H= appy Eyeballs draft can converge (we're already discussing this), and h= ow we want them to relate to other documents.

Best= ,
Tommy


On Oct 23, 2017, at 8:22 AM, Aaron Falk <aaron.falk@gmail.com> wrote:
P= lease send your interest for TAPS agenda time.

Already have: draft-i= etf-taps-minset-00.txt

Thanks,

=E2=80=94aaron

________= _______________________________________
Taps mailing list
Taps@ietf.org
https://w= ww.ietf.org/mailman/listinfo/taps


____________________________________= ___________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps


--94eb2c0e7d8893b15c055c5d5775-- From nobody Wed Oct 25 07:35:58 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A447F1384B2 for ; Wed, 25 Oct 2017 07:35:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.3 X-Spam-Level: X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com 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 18QjneuSz6b6 for ; Wed, 25 Oct 2017 07:35:55 -0700 (PDT) Received: from mail-in7.apple.com (mail-out7.apple.com [17.151.62.29]) (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 D18D913836B for ; Wed, 25 Oct 2017 07:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1508942155; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=mS+DIUu1ttzGun3cJNvzoKUxmYM/Iw59j7K/otlHCus=; b=ndOaazBSaiYetE99HZB1MZuq8RF+m6hL9uYy2bsIITmWI1DW0KesHLNGKfyc/9u9 aFCurZpYrYBRQjT37TcRnJRxLJR//KVnbNMEjFjilN5cXaQPPkovZoDCB/I+C84s FdUFfofvP+PqtTqiRnVWjG1ikICO/KfdVuO785j+CUUuYNf7fgwFtJrb5kAbhwvd r9wr+IBi3+WYm9k+HxoVo4ydPncfy4uNyY+IraPSHmctE7iEMY3fcy7yIHfROtWK kZPZdjh4+DjNDFJkH1Crv7HXJIgMP2pJYHnJ2yg4FIbMoZ7yx9vt3uBiuyV701D2 aC1ONsLCtrt5uVOZhfZkhQ==; Received: from relay8.apple.com (relay8.apple.com [17.128.113.102]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in7.apple.com (Apple Secure Mail Relay) with SMTP id 9B.20.31255.B41A0F95; Wed, 25 Oct 2017 07:35:55 -0700 (PDT) X-AuditID: 11973e16-75bff70000007a17-6c-59f0a14b3876 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by relay8.apple.com (Apple SCV relay) with SMTP id 35.C2.13565.B41A0F95; Wed, 25 Oct 2017 07:35:55 -0700 (PDT) MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_Q+NcKtwSfUl//Mto2eOLsQ)" Received: from [17.234.5.242] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.1.3.20170825 64bit (built Aug 25 2017)) with ESMTPSA id <0OYD00JMAV7UN810@nwk-mmpp-sz13.apple.com>; Wed, 25 Oct 2017 07:35:55 -0700 (PDT) Sender: tpauly@apple.com From: Tommy Pauly Message-id: <6FA980DD-27AD-4B45-A656-D06AF687D816@apple.com> Date: Wed, 25 Oct 2017 07:35:54 -0700 In-reply-to: Cc: Aaron Falk , Zaheduzzaman Sarker , taps WG To: Jon Crowcroft References: <89E68FE8-9910-48D9-BEEB-2126DF28D082@gmail.com> <5C6D34EE-355C-46E9-AD87-98D8F4002E5B@apple.com> X-Mailer: Apple Mail (2.3445.5.5) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUi2FCYpuu98EOkwYLp6hZtv6exWjy4+ITJ 4k6MxZFT75gdWDy2th5n8fj19Sqbx85Zd9k9liz5yRTAEsVlk5Kak1mWWqRvl8CV8Wl+UsEM 44oFP14wNTAu1e1i5OSQEDCR+LF/CyuILSSwhkmi7TUzTLzr31GmLkYuoPghRolnb7sZQRK8 AoISPybfYwGxmQXCJC5cessGUfSFUeLAmdNA3RwcwgISEpv3JILUsAmoSBz/toEZotdGounK RTYQW1hAU+L0gVtgc1gEVCWWPN7CCNLKKRAssf2uPcT4ConTcw4wgdgiAnoSLw79ZIdYtY1R Yv2th6wQhypKPNzUxQqSkBDYwibRvuI34wRGoVlIbp2F5NZZQDuYBdQlpkzJhQhrSzx5d4EV wlaTWPh7EROy+AJGtlWMQrmJmTm6mXnmeokFBTmpesn5uZsYQbEy3U5sB+PDVVaHGAU4GJV4 eAWmv48UYk0sK67MPcQozcGiJM778gVQSCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA+OF1vMa Cy5onueJYcqaGsRZ8FDowoW9jctsclluHGSb/1gw1vhhdtFGDd4FU5KS9jJWVvtFHf5/UpjV XTjsg8MDA2univX/hAX36Pr2n5+sXbyu9v7+GF2h/SHfJHknOux1ev2D9byBX51sxdW/965c cbeI1OCrUupYLrJK/65X5NrEg7nii5RYijMSDbWYi4oTARNHXpZ2AgAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUi2FB8Q9d74YdIgz2TFSzafk9jtXhw8QmT xZ0YiyOn3jE7sHhsbT3O4vHr61U2j52z7rJ7LFnykymAJYrLJiU1J7MstUjfLoEr49P8pIIZ xhULfrxgamBcqtvFyMkhIWAi0fXvKFMXIxeHkMAhRolnb7sZQRK8AoISPybfYwGxmQXCJC5c essGUfSFUeLAmdPMXYwcHMICEhKb9ySC1LAJqEgc/7aBGaLXRqLpykU2EFtYQFPi9IFbYHNY BFQlljzewgjSyikQLLH9rj3E+AqJ03MOMIHYIgJ6Ei8O/WSHWLWNUWL9rYesEIcqSjzc1MU6 gZF/FpLzZiE5bxbQWGYBdYkpU3IhwtoST95dYIWw1SQW/l7EhCy+gJFtFaNAUWpOYqWFXmJB QU6qXnJ+7iZGcHAXpu1gbFpudYhRgINRiYdXYPr7SCHWxLLiylxgGHEwK4nwcpR+iBTiTUms rEotyo8vKs1JLT7EKM3BoiTOu3kjULVAemJJanZqakFqEUyWiYNTqoFx63wFsbUfT9dOm3ot 3bHkPoO3L0d7aco5+T63ReskG9l68xgivJjS5veElioqhv7/O8N5NqNl0pnYFW2MUbZ91uyy l/7xu21S/7rL5afzvZQ751pUF7ju9+Yub5015+eOJ3zvbyl/ZlB8+t/lvkuaIW+ufZ2h8/lX oidDzMuDq18z5wQt2KbEUpyRaKjFXFScCACj3UZeagIAAA== Archived-At: Subject: Re: [Taps] call for agenda items X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2017 14:35:58 -0000 --Boundary_(ID_Q+NcKtwSfUl//Mto2eOLsQ) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable > On Oct 25, 2017, at 4:27 AM, Jon Crowcroft = wrote: >=20 > just one comment - this is confusing to people who care about race = conditions in connection establishment protocols - you need to = disambiguate > competing (greedy parallel exploration of options) from "racing" = somewhere in the doc:, i think:) A fair point! We can definitely find a better term. Parallel might work, = although really what we want to discuss here is mainly a staggered-start = race of the various options. Best, Tommy >=20 > On Wed, Oct 25, 2017 at 5:54 AM, Tommy Pauly > wrote: > I've just revised my "guidelines" draft to be "Guidelines for Racing = During Connection Establishment": >=20 > https://datatracker.ietf.org/doc/draft-pauly-taps-guidelines/ = > https://tools.ietf.org/html/draft-pauly-taps-guidelines-01 = >=20 > It would be useful to have a quick WG discussion (10-15 minutes?) on = how this work and the Protocol Happy Eyeballs draft can converge (we're = already discussing this), and how we want them to relate to other = documents. >=20 > Best, > Tommy >=20 >=20 >> On Oct 23, 2017, at 8:22 AM, Aaron Falk > wrote: >>=20 >> Please send your interest for TAPS agenda time. >>=20 >> Already have: draft-ietf-taps-minset-00.txt >>=20 >> Thanks, >>=20 >> =E2=80=94aaron >>=20 >> _______________________________________________ >> Taps mailing list >> Taps@ietf.org >> https://www.ietf.org/mailman/listinfo/taps = >=20 >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps = >=20 >=20 --Boundary_(ID_Q+NcKtwSfUl//Mto2eOLsQ) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable
On = Oct 25, 2017, at 4:27 AM, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> wrote:

just one comment - this is confusing to people who care about = race conditions in connection establishment protocols - you need to = disambiguate
competing (greedy parallel exploration of = options) from "racing" somewhere in the doc:, i = think:)

A = fair point! We can definitely find a better term. Parallel might work, = although really what we want to discuss here is mainly a staggered-start = race of the various options.

Best,
Tommy


On Wed, = Oct 25, 2017 at 5:54 AM, Tommy Pauly <tpauly@apple.com> wrote:
I've just revised my "guidelines" draft to be "Guidelines for = Racing During Connection Establishment":

https://datatracker.ietf.org/doc/draft-pauly-taps-guidelines/
https://tools.ietf.org/html/draft-pauly-taps-guidelines-01

It would be useful to have a quick WG = discussion (10-15 minutes?) on how this work and the Protocol Happy = Eyeballs draft can converge (we're already discussing this), and how we = want them to relate to other documents.

Best,
Tommy


On Oct = 23, 2017, at 8:22 AM, Aaron Falk <aaron.falk@gmail.com> wrote:

Please send your interest for TAPS agenda = time.

Already have: = draft-ietf-taps-minset-00.txt

Thanks,

=E2=80=94aaron

_______________________________________________
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



= --Boundary_(ID_Q+NcKtwSfUl//Mto2eOLsQ)-- From nobody Thu Oct 26 00:56:52 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E958A13A0AA; Thu, 26 Oct 2017 00:56:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: taps@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150900461092.24096.13409026819628849043@ietfa.amsl.com> Date: Thu, 26 Oct 2017 00:56:50 -0700 Archived-At: Subject: [Taps] I-D Action: draft-ietf-taps-transports-usage-09.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 07:56:51 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Services WG of the IETF. Title : On the Usage of Transport Features Provided by IETF Transport Protocols Authors : Michael Welzl Michael Tuexen Naeem Khademi Filename : draft-ietf-taps-transports-usage-09.txt Pages : 57 Date : 2017-10-26 Abstract: This document describes how the transport protocols Transmission Control Protocol (TCP), MultiPath TCP (MPTCP), Stream Control Transmission Protocol (SCTP), User Datagram Protocol (UDP) and Lightweight User Datagram Protocol (UDP-Lite) expose services to applications and how an application can configure and use the features that make up these services. It also discusses the service provided by the Low Extra Delay Background Transport (LEDBAT) congestion control mechanism. The description results in a set of transport abstractions that can be exported in a TAPS API. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-taps-transports-usage-09 https://datatracker.ietf.org/doc/html/draft-ietf-taps-transports-usage-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transports-usage-09 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Oct 26 00:59:23 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B700013B039 for ; Thu, 26 Oct 2017 00:59:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 YjXVvSifoYg7 for ; Thu, 26 Oct 2017 00:59:15 -0700 (PDT) Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 D994B13F43E for ; Thu, 26 Oct 2017 00:59:14 -0700 (PDT) Received: from mail-mx02.uio.no ([129.240.10.43]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1e7d4L-0005Aq-91; Thu, 26 Oct 2017 09:59:13 +0200 Received: from [62.119.166.1] (helo=[10.101.1.97]) by mail-mx02.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1e7d4K-0004Gn-BD; Thu, 26 Oct 2017 09:59:13 +0200 From: Michael Welzl Message-Id: <55C21022-53DC-4BCA-A5BB-E2658766853A@ifi.uio.no> Content-Type: multipart/alternative; boundary="Apple-Mail=_AB575D79-1D0D-403E-A95A-2B4E0A824D6F" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Date: Thu, 26 Oct 2017 09:59:10 +0200 In-Reply-To: Cc: "taps@ietf.org" , taps-chairs@ietf.org To: Spencer Dawkins References: X-Mailer: Apple Mail (2.3273) X-UiO-SPF-Received: Received-SPF: neutral (mail-mx02.uio.no: 62.119.166.1 is neither permitted nor denied by domain of ifi.uio.no) client-ip=62.119.166.1; envelope-from=michawe@ifi.uio.no; helo=[10.101.1.97]; X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: A412D20043415B2493C7357E54E7472FB1A8C7DF Archived-At: Subject: Re: [Taps] One RFC, or two, for draft-ietf-taps-transports-usage and draft-ietf-taps-transports-usage-udp X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 07:59:19 -0000 --Apple-Mail=_AB575D79-1D0D-403E-A95A-2B4E0A824D6F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Thanks; I just posted an update of draft-ietf-taps-transports-usage = which, I believe, addresses all the last comments. =46rom the revision = info in the draft: *** -09: for consistency with the draft-ietf-taps-minset-00, adjusted the following transport features in "pass 3": "Choice between unordered (potentially faster) or ordered delivery of messages" divided into two transport features (one for unordered, one for ordered); the word "reliably" was added to the transport features "Hand over a message to reliably transfer (possibly multiple times) before connection establishment" and "Hand over a message to reliably transfer during connection establishment". Fixed RFC2119-style language into explicit citations (comment by Eric Rescorla and others). Addressed editorial comments by Mirja Kuehlewind, Ben Campbell, Benoit Claise and the Gen-ART reviewer Roni Even, except for moving terminology section after the intro because the terminology is already used in the intro text. *** Cheers, Michael > On Oct 24, 2017, at 8:34 PM, Spencer Dawkins at IETF = wrote: >=20 > Just to make a long-delayed decision ... >=20 > Based on responses to my question to TAPS about whether = draft-ietf-taps-transports-usage-udp should be folded into = draft-ietf-taps-transports-usage, I am seeing no support in the working = group for that, and reasons why the draft-ietf-taps-transports-usage-udp = draft is useful without reference to the = draft-ietf-taps-transports-usage. >=20 > For these reasons, I ask that the authors submit an updated = draft-ietf-taps-transports-usage draft, taking into account the ballot = comments from Eric, Mirja, Ben, and Benoit. >=20 > I see that the draft-ietf-taps-transports-usage-udp draft has already = been updated to reflect comments received during balloting. I'll send = the Approved e-mails for both drafts as a set. >=20 > Thanks to everyone who provided input. >=20 > Spencer, as AD >=20 > On Wed, Sep 13, 2017 at 11:47 PM, Spencer Dawkins at IETF = > = wrote: > Dear TAPS working group, >=20 > Multiple ADs have asked why these two drafts aren't a single draft, in = their ballots. Those are non-blocking comments, but I'd like to explore = that, before making a decision about what should happen, and when. >=20 > It occurs to me that these ADs are reading both drafts pretty much = back-to-back in preparation for balloting during IESG Evaluation. >=20 > If people reading the two drafts back-to-back find the split to be a = distraction, I'd like to understand the views of the working group as to = how often you expect people to read both drafts, in order to do TAPS. >=20 > I could imagine that people working on complete TAPS APIs might need = to read both drafts.=20 >=20 > What about other folks you expect to read these documents? Do you = expect that some communities only need to read one of them? >=20 > Thanks in advance for any thoughts you can share. >=20 > Spencer, as responsible AD for TAPS >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps --Apple-Mail=_AB575D79-1D0D-403E-A95A-2B4E0A824D6F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

Thanks;= I just posted an update of draft-ietf-taps-transports-usage which, = I believe, addresses all the last comments. =46rom the revision info in = the draft:

***
   -09: = for consistency with the draft-ietf-taps-minset-00, adjusted = the
   following transport features in = "pass 3": "Choice between unordered
  =  (potentially faster) or ordered delivery of messages" divided = into
   two transport features (one for = unordered, one for ordered); the word
  =  "reliably" was added to the transport features "Hand over a = message
   to reliably transfer (possibly = multiple times) before connection
  =  establishment" and "Hand over a message to reliably transfer = during
   connection establishment". =  Fixed RFC2119-style language into
  =  explicit citations (comment by Eric Rescorla and others). =  Addressed
   editorial comments by = Mirja Kuehlewind, Ben Campbell, Benoit Claise
  =  and the Gen-ART reviewer Roni Even, except for moving = terminology
   section after the intro = because the terminology is already used in
  =  the intro text.
***

Cheers,
Michael



On Oct 24, 2017, at 8:34 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:

Just to make a long-delayed decision ...

Based on responses to = my question to TAPS about whether draft-ietf-taps-transports-usage-udp should be folded into = draft-ietf-taps-transports-usage, I am seeing no support = in the working group for that, and reasons why the = draft-ietf-taps-transports-usage-udp draft is useful = without reference to the draft-ietf-taps-transports-usage.

For these reasons, I ask that the authors submit an updated = draft-ietf-taps-transports-usage draft, taking into = account the ballot comments from Eric, Mirja, Ben, and Benoit.

I see that the = draft-ietf-taps-transports-usage-udp draft has already = been updated to reflect comments received during balloting. I'll send = the Approved e-mails for both drafts as a set.

Thanks to everyone who provided = input.

Spencer, = as AD

On Wed, Sep 13, 2017 at 11:47 PM, Spencer Dawkins = at IETF <spencerdawkins.ietf@gmail.com> = wrote:
Dear TAPS = working group,

Multiple ADs have asked why these two drafts aren't a single = draft, in their ballots. Those are non-blocking comments, but I'd like = to explore that, before making a decision about what should happen, and = when.

It = occurs to me that these ADs are reading both drafts pretty much = back-to-back in preparation for balloting during IESG = Evaluation.

If = people reading the two drafts back-to-back find the split to be a = distraction, I'd like to understand the views of the working group as to = how often you expect people to read both drafts, in order to do = TAPS.

I could = imagine that people working on complete TAPS APIs might need to read = both drafts. 

What about other folks you expect to read these documents? Do = you expect that some communities only need to read one of = them?

Thanks = in advance for any thoughts you can share.

Spencer, as responsible AD for = TAPS

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

= --Apple-Mail=_AB575D79-1D0D-403E-A95A-2B4E0A824D6F-- From nobody Thu Oct 26 11:22:09 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A909013F448; Thu, 26 Oct 2017 11:22:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Cc: The IESG , Zaheduzzaman.Sarker@ericsson.com, taps-chairs@ietf.org, spencerdawkins.ietf@gmail.com, Zaheduzzaman Sarker , rfc-editor@rfc-editor.org, draft-ietf-taps-transports-usage-udp@ietf.org, taps@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-ID: <150904212768.24244.8428507170733170067.idtracker@ietfa.amsl.com> Date: Thu, 26 Oct 2017 11:22:07 -0700 Archived-At: Subject: [Taps] Document Action: 'Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols' to Informational RFC (draft-ietf-taps-transports-usage-udp-07.txt) X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 18:22:08 -0000 The IESG has approved the following document: - 'Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols' (draft-ietf-taps-transports-usage-udp-07.txt) as Informational RFC This document is the product of the Transport Services Working Group. The IESG contact persons are Mirja Kühlewind and Spencer Dawkins. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage-udp/ Technical Summary This document describes well established function calls as "primitives" that any program can use to get automated transport services from the UDP and UDP-lite transport protocols. These primitives are services provided by the standards-track versions of the corresponding protocols. The working group believes the primitives will be useful for users of a transport service implementation. Working Group Summary The primitives for UDP and UDP-lite were initially intended to be part of draft-ietf-transport-usage, however working group agreed to have a smaller document for these protocols, because the authors providing descriptions for these protocols had little overlap with the authors of draft-ietf-transport-usage, and the split allowed for better review by readers with expertise in these protocols. As this document describes primitives based on what already available in standards-track RFCs for those protocol it was straightforward to get consensus on the primitives. Document Quality All versions of this document got a fair amount of discussion on the working group mailing list, were well reviewed and got positive feedback during working group last call. Personnel The document shepherd is Zaheduzzaman Sarker. The responsible Area Director is Spencer Dawkins. From nobody Thu Oct 26 11:23:17 2017 Return-Path: X-Original-To: taps@ietf.org Delivered-To: taps@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D82FF13F5EA; Thu, 26 Oct 2017 11:23:03 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Cc: The IESG , Zaheduzzaman.Sarker@ericsson.com, draft-ietf-taps-transports-usage@ietf.org, rfc-editor@rfc-editor.org, taps-chairs@ietf.org, Zaheduzzaman Sarker , taps@ietf.org, spencerdawkins.ietf@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-ID: <150904218388.24096.6663313507911354729.idtracker@ietfa.amsl.com> Date: Thu, 26 Oct 2017 11:23:03 -0700 Archived-At: Subject: [Taps] Document Action: 'On the Usage of Transport Features Provided by IETF Transport Protocols' to Informational RFC (draft-ietf-taps-transports-usage-09.txt) X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 18:23:04 -0000 The IESG has approved the following document: - 'On the Usage of Transport Features Provided by IETF Transport Protocols' (draft-ietf-taps-transports-usage-09.txt) as Informational RFC This document is the product of the Transport Services Working Group. The IESG contact persons are Mirja Kühlewind and Spencer Dawkins. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/ Technical Summary This document describes well established function calls as "primitives" that any program can use to get automated transport services from TCP, MP-TCP, SCTP, LEDBAT, UDP and UDP-lite protocols. This description gives very good information about the services provided by the protocols as defined in the RFC series. Further it describes the 3 pass process the working group followed to derive the transport features. Overall this document serves as a useful source of information for users of using transport services. Working Group Summary There were discussions on what protocols the document should cover, especially for inclusion of secure protocols such as TLS and DTLS. This was well communicated with respective working groups. As at that time the TAPS working group lacked security protocol expertise, the consensus was to keep those out of the scope of the document. When this document was in the working group, TAPS was explicitly not chartered to perform detailed analysis of the security aspects of transport protocols. Document Quality As this document describes primitives based on what is already available in standards- track RFCs for the corresponding transport protocols, it was straightforward to get consensus on the primitives. All versions of this document got a fair amount of discussion in the mailing list, were well reviewed, and got positive feedback in working group last call. Personnel The document shepherd is Zaheduzzaman Sarker. The responsible Area Director is Spencer Dawkins. From nobody Mon Oct 30 08:38:22 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D8013FA9C for ; Mon, 30 Oct 2017 08:38:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 X-uLzvCN623J for ; Mon, 30 Oct 2017 08:38:16 -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 5C8C01FF525 for ; Mon, 30 Oct 2017 08:30:42 -0700 (PDT) Received: from Gs-MacBook-Pro.local (at-zeroshell-1.erg.abdn.ac.uk [139.133.217.68]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 1EE7D1B001FB; Mon, 30 Oct 2017 15:30:36 +0000 (GMT) Message-ID: <59F7459C.8020600@erg.abdn.ac.uk> Date: Mon, 30 Oct 2017 15:30:36 +0000 From: Gorry Fairhurst Reply-To: gorry@erg.abdn.ac.uk Organization: University of Aberdeen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: taps@ietf.org CC: David Ros , Tom Jones , Anna Brunstrom References: <150937724266.23209.14406691936839464875.idtracker@ietfa.amsl.com> In-Reply-To: <150937724266.23209.14406691936839464875.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-neat-00.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 15:38:20 -0000 TAPers, I've just uploaded an Internet Draft on the NEAT User API, this draft provides a high-level overview of the transport interface to the actual NEAT System (available on GIT-Hub) and outlines how this forms an API that can offer TAPS-like services in an actual system. Gorry On 30/10/2017, 15:27, internet-drafts@ietf.org wrote: > A new version of I-D, draft-fairhurst-taps-neat-00.txt > has been successfully submitted by Godred Fairhurst and posted to the > IETF repository. > > Name: draft-fairhurst-taps-neat > Revision: 00 > Title: The NEAT Interface to Transport Services > Document date: 2017-10-30 > Group: Individual Submission > Pages: 14 > URL: https://www.ietf.org/internet-drafts/draft-fairhurst-taps-neat-00.txt > Status: https://datatracker.ietf.org/doc/draft-fairhurst-taps-neat/ > Htmlized: https://tools.ietf.org/html/draft-fairhurst-taps-neat-00 > Htmlized: https://datatracker.ietf.org/doc/html/draft-fairhurst-taps-neat-00 > > > Abstract: > The NEAT System provides an example of a system designed to implement > the TAPS Transport Services. This document presents the transport > services that the NEAT User API provides to an application or upper- > layer protocol. It also describes primitives needed to interface to > the NEAT Policy Manager and how policies can be adjusted to match the > API behaviour to the properties required by an application or upper- > layer protocol using the NEAT User API. > > > > > 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 From nobody Mon Oct 30 13:16:25 2017 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C914313F554 for ; Mon, 30 Oct 2017 13:16:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 TuzDumjzGLaM for ; Mon, 30 Oct 2017 13:16:22 -0700 (PDT) Received: from einhorn-mail.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 2CC57139478 for ; Mon, 30 Oct 2017 13:16:22 -0700 (PDT) X-Envelope-From: phils@in-panik.de X-Envelope-To: Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id v9UKG0mX016911 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 30 Oct 2017 21:16:00 +0100 Received: from [2001:bf0:c801:101:c5c2:5a20:ca4:2e26] by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e9GT6-0005WU-St for taps@ietf.org; Mon, 30 Oct 2017 21:15:32 +0100 From: "Philipp S. Tiesel" Content-Type: multipart/alternative; boundary="Apple-Mail=_8B2C9D01-84F9-4A12-8DF5-1536332AD0D0" Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Message-Id: <06DE461E-D289-4B6C-AE37-28098BF7244F@in-panik.de> References: <150922047627.2738.7553047120989518171.idtracker@ietfa.amsl.com> To: taps WG Date: Mon, 30 Oct 2017 21:15:57 +0100 X-Mailer: Apple Mail (2.3445.1.7) Archived-At: Subject: [Taps] New Version Notification for draft-tiesel-taps-socketintents-01.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "IETF Transport Services \(TAPS\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 20:16:25 -0000 --Apple-Mail=_8B2C9D01-84F9-4A12-8DF5-1536332AD0D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, We=E2=80=99ve updated our Internet Draft on Socket Intents. Socket Intents are a generic mechanism for applications to express = non-requirement performance preferences, like optimize for bandwidth or = latency, and applications=E2=80=99 knowledge, like expected bandwidth = usage. =20 Socket Intents are specified in a portable way and can be added to any = transport API, including Post Sockets, the NEAT API or, with = limitations, to regular BSD sockets. With this second version, I want to raise a few questions. - Are Socket Intents easy enough? - Is the structure of Socket Intent Types sufficient to express all anticipated future non-requirement performance preferences and application knowledge? - What Socket Intent Types / kinds of information are missing? - Does the current abstract definition of Socket Intents fit the way the IETF specifies abstract APIs? We are looking forward to an active discussion here and in Singapore and = hope that we find a way to push Socket Intents forward. AVE! Philipp S. Tiesel / phils=E2=80=A6 > Begin forwarded message: >=20 > A new version of I-D, draft-tiesel-taps-socketintents-01.txt > has been successfully submitted by Philipp S. Tiesel and posted to the > IETF repository. >=20 > Name: draft-tiesel-taps-socketintents > Revision: 01 > Title: Socket Intents > Document date: 2017-10-27 > Group: Individual Submission > Pages: 15 > URL: = https://www.ietf.org/internet-drafts/draft-tiesel-taps-socketintents-01.tx= t > Status: = https://datatracker.ietf.org/doc/draft-tiesel-taps-socketintents/ > Htmlized: = https://tools.ietf.org/html/draft-tiesel-taps-socketintents-01 > Htmlized: = https://datatracker.ietf.org/doc/html/draft-tiesel-taps-socketintents-01 > Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-tiesel-taps-socketintents-01 >=20 > Abstract: > This document outlines Socket Intents, a concept that allows > applications to share their knowledge about upcoming communication > and express their performance preferences in a generic, intuitive > and, portable way. Using Socket Intents, an application can express > what it knows, assumes, expects, or wants regarding its network > communication. The information provided by Socket Intents can be > used by the network stack to optimize communication in a best-effort > way. >=20 > Socket Intent can be used to stem against the complexity of > exploiting transport diversity, e.g., to automate the choice among > multiple paths, provisioning domains or protocols. By shifting this > complexity from the application developer to the operating system, = it > enables the use of these transport features to a wider range of > applications. >=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 --Apple-Mail=_8B2C9D01-84F9-4A12-8DF5-1536332AD0D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

We=E2=80= =99ve updated our Internet Draft on Socket Intents.

Socket Intents are a = generic mechanism for applications to express non-requirement = performance preferences, like optimize for bandwidth or latency, and = applications=E2=80=99 knowledge, like expected bandwidth usage. =   
Socket Intents are specified in a = portable way and can be added to any transport API, including Post = Sockets, the NEAT API or, with limitations, to regular BSD = sockets.

With this second version, I = want to raise a few questions.

 -= Are Socket Intents easy enough?

 - Is the structure of Socket Intent = Types sufficient to express
   all anticipated = future  non-requirement performance preferences
  =  and application knowledge?

 - What Socket Intent Types / = kinds of information are missing?

 - Does the = current abstract definition of Socket Intents
   fit = the way the IETF specifies abstract APIs?

We are looking forward = to an active discussion here and in Singapore and hope that we find a = way to push Socket Intents forward.

AVE!
  Philipp S. Tiesel = / phils=E2=80=A6

Begin forwarded message:

A new version of I-D, = draft-tiesel-taps-socketintents-01.txt
has been = successfully submitted by Philipp S. Tiesel and posted to the
IETF repository.

Name: = draft-tiesel-taps-socketintents
Revision: 01
Title:= = Socket Intents
Document date: = 2017-10-27
Group: Individual Submission
Pages:= = 15
URL: =            https://www.ietf.org/internet-drafts/draft-tiesel-taps-socketin= tents-01.txt
Status: =         https://datatracker.ietf.org/doc/draft-tiesel-taps-socketintent= s/
Htmlized:       https://tools.ietf.org/html/draft-tiesel-taps-socketintents-01<= /a>
Htmlized:       https://datatracker.ietf.org/doc/html/draft-tiesel-taps-socketi= ntents-01
Diff: =           https://www.ietf.org/rfcdiff?url2=3Ddraft-tiesel-taps-socketint= ents-01

Abstract:
=   This document outlines Socket Intents, a concept that = allows
  applications to share their knowledge = about upcoming communication
  and express = their performance preferences in a generic, intuitive
=   and, portable way.  Using Socket Intents, an = application can express
  what it knows, = assumes, expects, or wants regarding its network
=   communication.  The information provided by Socket = Intents can be
  used by the network stack to = optimize communication in a best-effort
=   way.

  Socket Intent = can be used to stem against the complexity of
=   exploiting transport diversity, e.g., to automate the choice = among
  multiple paths, provisioning domains or = protocols.  By shifting this
  complexity = from the application developer to the operating system, it
=   enables the use of these transport features to a wider range = of
  applications.




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



= --Apple-Mail=_8B2C9D01-84F9-4A12-8DF5-1536332AD0D0--