From nobody Thu Oct 6 00:23:02 2016 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 3485612953A for ; Thu, 6 Oct 2016 00:23:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.196 X-Spam-Level: X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996] 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 YlNZvn0c3FLY for ; Thu, 6 Oct 2016 00:22:58 -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 4BE2B126FDC for ; Thu, 6 Oct 2016 00:22:58 -0700 (PDT) Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 0D7C21B001C9; Thu, 6 Oct 2016 10:21:22 +0100 (BST) Message-ID: <57F5FBCE.6080609@erg.abdn.ac.uk> Date: Thu, 06 Oct 2016 08:22:54 +0100 From: Gorry Fairhurst Organization: University of Aberdeen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: taps@ietf.org References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> In-Reply-To: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: aaron.falk@gmail.com Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:23:01 -0000 We have just submitted an updated copy of the UDP usage draft we have been working on in TAPS. Specifically: (1) It omits the text for pass 2 and 3 that we now expect to be directly incorporated in draft-ietf-taps-transport-usage. Michael Welzl I think indicated that this text will be copied from rev -usage-udp-02. (2) It contains small changes to the document text to allow this to be publsihed as a separate document. The WG discussed whether such a document could be adopted for publication as a pair with draft-ietf-taps-transport-usage. The authors are now looking to the group to know if the WG would like to adopt this and then what further work may be needed. Best wishes, Tom & Gorry On 05/10/2016 21:46, internet-drafts@ietf.org wrote: > A new version of I-D, draft-fairhurst-taps-transports-usage-udp-03.txt > has been successfully submitted by Godred Fairhurst and posted to the > IETF repository. > > Name: draft-fairhurst-taps-transports-usage-udp > Revision: 03 > Title: Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols > Document date: 2016-10-05 > Group: Individual Submission > Pages: 18 > URL: https://www.ietf.org/internet-drafts/draft-fairhurst-taps-transports-usage-udp-03.txt > Status: https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp/ > Htmlized: https://tools.ietf.org/html/draft-fairhurst-taps-transports-usage-udp-03 > Diff: https://www.ietf.org/rfcdiff?url2=draft-fairhurst-taps-transports-usage-udp-03 > > Abstract: > This document describes how the User Datagram Protocol (UDP) and the > Lightweight User Datagram Protocol (UDP-Lite) transport protocols > expose services to applications and how an application can configure > and use the features offered by the transport service. The document > is intended as a contribution to the Transport Services (TAPS) > working group to assist in analysis of the UDP and UDP-Lite transport > interface. > > > > > 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 Thu Oct 6 00:47:07 2016 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 957DC129522 for ; Thu, 6 Oct 2016 00:47:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.196 X-Spam-Level: X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996] 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 T4zU9ka_wUek for ; Thu, 6 Oct 2016 00:47:03 -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 B18C412954A for ; Thu, 6 Oct 2016 00:47:02 -0700 (PDT) Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from ) id 1bs3OO-0004Wj-3C for taps@ietf.org; Thu, 06 Oct 2016 09:47:00 +0200 Received: from ppp-94-66-13-227.home.otenet.gr ([94.66.13.227] helo=[192.168.32.3]) by mail-mx3.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from ) id 1bs3ON-00074s-D0; Thu, 06 Oct 2016 09:47:00 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) From: Michael Welzl X-Mailer: iPhone Mail (13G36) In-Reply-To: <57F5FBCE.6080609@erg.abdn.ac.uk> Date: Thu, 6 Oct 2016 10:46:56 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> To: gorry@erg.abdn.ac.uk X-UiO-SPF-Received: X-UiO-Ratelimit-Test: rcpts/h 8 msgs/h 4 sum rcpts/h 10 sum msgs/h 5 total rcpts 46932 max rcpts/h 54 ratelimit 0 X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, MIME_QP_LONG_LINE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 01FB27CA152002B23AD316CDD008CE38FE358B57 X-UiO-SPAM-Test: remote_host: 94.66.13.227 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 7 max/h 4 blacklist 0 greylist 0 ratelimit 0 Archived-At: Cc: aaron.falk@gmail.com, taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:47:05 -0000 hi, clarification: yes i said what's written below, but i think this is the firs= t time the taps folks hear about it. so if that's fine with everyone, that'= s our plan - it seemed to us to be the most reasonable approach. about adopting this separate document, it makes sense to me Sent from my iPhone > On 6. okt. 2016, at 10.22, Gorry Fairhurst wrote: >=20 > We have just submitted an updated copy of the UDP usage draft we have been= working on in TAPS. >=20 > Specifically: >=20 > (1) It omits the text for pass 2 and 3 that we now expect to be directly i= ncorporated in draft-ietf-taps-transport-usage. > Michael Welzl I think indicated that this text will be copied from rev -us= age-udp-02. >=20 > (2) It contains small changes to the document text to allow this to be pub= lsihed as a separate document. The WG discussed whether such a document coul= d be adopted for publication as a pair with draft-ietf-taps-transport-usage.= The authors are now looking to the group to know if the WG would like to a= dopt this and then what further work may be needed. >=20 > Best wishes, >=20 > Tom & Gorry >=20 >=20 >> On 05/10/2016 21:46, internet-drafts@ietf.org wrote: >> A new version of I-D, draft-fairhurst-taps-transports-usage-udp-03.txt >> has been successfully submitted by Godred Fairhurst and posted to the >> IETF repository. >>=20 >> Name: draft-fairhurst-taps-transports-usage-udp >> Revision: 03 >> Title: Features of the User Datagram Protocol (UDP) and Lightweigh= t UDP (UDP- Lite) Transport Protocols >> Document date: 2016-10-05 >> Group: Individual Submission >> Pages: 18 >> URL: https://www.ietf.org/internet-drafts/draft-fairhurst-taps= -transports-usage-udp-03.txt >> Status: https://datatracker.ietf.org/doc/draft-fairhurst-taps-tra= nsports-usage-udp/ >> Htmlized: https://tools.ietf.org/html/draft-fairhurst-taps-transpor= ts-usage-udp-03 >> Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-fairhurst-taps-= transports-usage-udp-03 >>=20 >> Abstract: >> This document describes how the User Datagram Protocol (UDP) and the >> Lightweight User Datagram Protocol (UDP-Lite) transport protocols >> expose services to applications and how an application can configure >> and use the features offered by the transport service. The document >> is intended as a contribution to the Transport Services (TAPS) >> working group to assist in analysis of the UDP and UDP-Lite transport >> interface. >>=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 Oct 6 12:57:43 2016 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 7DA1812941E for ; Thu, 6 Oct 2016 12:57:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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 8JfhaUxMiTFA for ; Thu, 6 Oct 2016 12:57:39 -0700 (PDT) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 AE9E5129416 for ; Thu, 6 Oct 2016 12:57:39 -0700 (PDT) Received: by mail-qk0-x232.google.com with SMTP id f128so6083211qkb.1 for ; Thu, 06 Oct 2016 12:57:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xbOvywiJQ4wuWr0pvMPGsmm09o8x2WIFiE6aGwjsA4g=; b=DuvOrnAqlx8skaZxvPLFzZ7pN8ESwj54/qoAcexH+eTvfSRXHZbvh/qvMa53BrZYwA MDlUhhQDGyYWndjIcILLPDFkM670f37TVYchbWGfYnac2fvqmW70jk/+1OrAWNKExLxV N5l3NYpdzAfymIGlLpcregV4U7yHJ0FYTuYluidA+78uZlsuI4MnpnrD8eYHrIgxVnjv X2WGSDgEDXaQniWYGV/6PYpHRjsExekwC1jzCebX823my2/Ngwtl7NKo+DtbNEU/WJeu ysuE2+7uhXhWCnOsUxdqktf6Y1NtJlRLQA1vbg2eKS/9hD8A4ArCXK91L7fojMCycLM0 X04Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xbOvywiJQ4wuWr0pvMPGsmm09o8x2WIFiE6aGwjsA4g=; b=YQ8i4Px1g1QOYkqhVvEl3YuwZIgT9Y3bB0GZdnD05WVqPHl6SbC3WfhJ3mdmhvDE7A 87jazXcjyQ4NE9NOhwMmlnu9+GpEQEMKIkUAn9frOV3vLuTZ1nJq+eMIFu2YZ3Ro78eo 7TQXi8kjO7Z7fe+XOlKloT0JLtLzPJFBjPCJibL5Of4/OetQtTvyipm21B6IPzEmq4vS kz0jU6WiOHlz+evv0tAprijuvxzM+M4Ui04fOqjMCHWTibEa/cm4DLYrK6Sit0O/TaXf DHoPXtF0X5r1ls5ZnuIvmzOJyOBRI7v2G9P+FH7t4WJEtNcL3+QdlaS/R4/wTk2FUbob 1b9g== X-Gm-Message-State: AA6/9Rl/PpKdmWXENYx+uIQjx8SRfk5PUhjBwhoDixkpcCHvYn8pSyx2aPZBPLcD3+mvcA== X-Received: by 10.55.40.40 with SMTP id o40mr14003753qkh.73.1475783858825; Thu, 06 Oct 2016 12:57:38 -0700 (PDT) Received: from ?IPv6:2001:4878:8000:60:591e:16fa:8e7:e324? ([2001:4878:8000:60:591e:16fa:8e7:e324]) by smtp.gmail.com with ESMTPSA id m62sm1373920qte.11.2016.10.06.12.57.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 06 Oct 2016 12:57:37 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Aaron Falk In-Reply-To: Date: Thu, 6 Oct 2016 15:57:37 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> To: Michael Welzl X-Mailer: Apple Mail (2.3124) Archived-At: Cc: Gorry Fairhurst , taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 19:57:41 -0000 IMO, this is obviously in scope for TAPS and a useful contribution. = I=E2=80=99d like to hear any dissenting opinions about adopting this doc = as a wg item. =E2=80=94aaron > On Oct 6, 2016, at 3:46 AM, Michael Welzl wrote: >=20 > hi, >=20 > clarification: yes i said what's written below, but i think this is = the first time the taps folks hear about it. so if that's fine with = everyone, that's our plan - it seemed to us to be the most reasonable = approach. >=20 > about adopting this separate document, it makes sense to me >=20 >=20 > Sent from my iPhone >=20 >> On 6. okt. 2016, at 10.22, Gorry Fairhurst = wrote: >>=20 >> We have just submitted an updated copy of the UDP usage draft we have = been working on in TAPS. >>=20 >> Specifically: >>=20 >> (1) It omits the text for pass 2 and 3 that we now expect to be = directly incorporated in draft-ietf-taps-transport-usage. >> Michael Welzl I think indicated that this text will be copied from = rev -usage-udp-02. >>=20 >> (2) It contains small changes to the document text to allow this to = be publsihed as a separate document. The WG discussed whether such a = document could be adopted for publication as a pair with = draft-ietf-taps-transport-usage. The authors are now looking to the = group to know if the WG would like to adopt this and then what further = work may be needed. >>=20 >> Best wishes, >>=20 >> Tom & Gorry >>=20 >>=20 >>> On 05/10/2016 21:46, internet-drafts@ietf.org wrote: >>> A new version of I-D, = draft-fairhurst-taps-transports-usage-udp-03.txt >>> has been successfully submitted by Godred Fairhurst and posted to = the >>> IETF repository. >>>=20 >>> Name: draft-fairhurst-taps-transports-usage-udp >>> Revision: 03 >>> Title: Features of the User Datagram Protocol (UDP) and = Lightweight UDP (UDP- Lite) Transport Protocols >>> Document date: 2016-10-05 >>> Group: Individual Submission >>> Pages: 18 >>> URL: = https://www.ietf.org/internet-drafts/draft-fairhurst-taps-transports-usage= -udp-03.txt >>> Status: = https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp= / >>> Htmlized: = https://tools.ietf.org/html/draft-fairhurst-taps-transports-usage-udp-03 >>> Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-fairhurst-taps-transports-usage-= udp-03 >>>=20 >>> Abstract: >>> This document describes how the User Datagram Protocol (UDP) and = the >>> Lightweight User Datagram Protocol (UDP-Lite) transport protocols >>> expose services to applications and how an application can = configure >>> and use the features offered by the transport service. The = document >>> is intended as a contribution to the Transport Services (TAPS) >>> working group to assist in analysis of the UDP and UDP-Lite = transport >>> interface. >>>=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 From nobody Mon Oct 10 02:10:33 2016 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 1D44F129469 for ; Mon, 10 Oct 2016 02:10:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.196 X-Spam-Level: X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996] 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 E23sz5unLszi for ; Mon, 10 Oct 2016 02:10:29 -0700 (PDT) Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 509B3129453 for ; Mon, 10 Oct 2016 02:10:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C913DD9305; Mon, 10 Oct 2016 11:10:27 +0200 (MEST) X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 74AjiA40dTuC; Mon, 10 Oct 2016 11:10:27 +0200 (MEST) Received: from [192.168.178.33] (p5DEC2691.dip0.t-ipconnect.de [93.236.38.145]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mirjak) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 70338D9302; Mon, 10 Oct 2016 11:10:27 +0200 (MEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: =?utf-8?Q?Mirja_K=C3=BChlewind?= In-Reply-To: <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> Date: Mon, 10 Oct 2016 11:11:41 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> To: Aaron Falk X-Mailer: Apple Mail (2.3124) Archived-At: Cc: Gorry Fairhurst , Michael Welzl , taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 09:10:32 -0000 Hi all, quick question: what=E2=80=99s the advantage of having this as a = separate doc instead of merging it with draft-ietf-taps-transports-usage = (which was the original plan to my understanding)? Mirja > Am 06.10.2016 um 21:57 schrieb Aaron Falk : >=20 > IMO, this is obviously in scope for TAPS and a useful contribution. = I=E2=80=99d like to hear any dissenting opinions about adopting this doc = as a wg item. >=20 > =E2=80=94aaron >=20 >=20 >> On Oct 6, 2016, at 3:46 AM, Michael Welzl wrote: >>=20 >> hi, >>=20 >> clarification: yes i said what's written below, but i think this is = the first time the taps folks hear about it. so if that's fine with = everyone, that's our plan - it seemed to us to be the most reasonable = approach. >>=20 >> about adopting this separate document, it makes sense to me >>=20 >>=20 >> Sent from my iPhone >>=20 >>> On 6. okt. 2016, at 10.22, Gorry Fairhurst = wrote: >>>=20 >>> We have just submitted an updated copy of the UDP usage draft we = have been working on in TAPS. >>>=20 >>> Specifically: >>>=20 >>> (1) It omits the text for pass 2 and 3 that we now expect to be = directly incorporated in draft-ietf-taps-transport-usage. >>> Michael Welzl I think indicated that this text will be copied from = rev -usage-udp-02. >>>=20 >>> (2) It contains small changes to the document text to allow this to = be publsihed as a separate document. The WG discussed whether such a = document could be adopted for publication as a pair with = draft-ietf-taps-transport-usage. The authors are now looking to the = group to know if the WG would like to adopt this and then what further = work may be needed. >>>=20 >>> Best wishes, >>>=20 >>> Tom & Gorry >>>=20 >>>=20 >>>> On 05/10/2016 21:46, internet-drafts@ietf.org wrote: >>>> A new version of I-D, = draft-fairhurst-taps-transports-usage-udp-03.txt >>>> has been successfully submitted by Godred Fairhurst and posted to = the >>>> IETF repository. >>>>=20 >>>> Name: draft-fairhurst-taps-transports-usage-udp >>>> Revision: 03 >>>> Title: Features of the User Datagram Protocol (UDP) and = Lightweight UDP (UDP- Lite) Transport Protocols >>>> Document date: 2016-10-05 >>>> Group: Individual Submission >>>> Pages: 18 >>>> URL: = https://www.ietf.org/internet-drafts/draft-fairhurst-taps-transports-usage= -udp-03.txt >>>> Status: = https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp= / >>>> Htmlized: = https://tools.ietf.org/html/draft-fairhurst-taps-transports-usage-udp-03 >>>> Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-fairhurst-taps-transports-usage-= udp-03 >>>>=20 >>>> Abstract: >>>> This document describes how the User Datagram Protocol (UDP) and = the >>>> Lightweight User Datagram Protocol (UDP-Lite) transport protocols >>>> expose services to applications and how an application can = configure >>>> and use the features offered by the transport service. The = document >>>> is intended as a contribution to the Transport Services (TAPS) >>>> working group to assist in analysis of the UDP and UDP-Lite = transport >>>> interface. >>>>=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 >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps From nobody Mon Oct 10 06:11:27 2016 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 DB2D1129670 for ; Mon, 10 Oct 2016 06:11:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.896 X-Spam-Level: X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.996] 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 FR25kAOVTe13 for ; Mon, 10 Oct 2016 06:11:22 -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 DF074129639 for ; Mon, 10 Oct 2016 06:11:21 -0700 (PDT) Received: from [10.5.47.249] (unknown [85.255.236.222]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 8D17E1B00250; Mon, 10 Oct 2016 16:09:46 +0100 (BST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "Gorry (erg)" Mime-Version: 1.0 (1.0) Date: Mon, 10 Oct 2016 11:15:05 +0100 Message-Id: <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> In-Reply-To: <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> To: =?utf-8?Q?Mirja_K=C3=BChlewind?= X-Mailer: iPhone Mail (13G36) Archived-At: Cc: Aaron Falk , Michael Welzl , taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 13:11:26 -0000 Good question. In the Berlin IETF meeting - I went through arguments for and= against.=20 Some arguments for the two ID, ,were this may help to continue to receive th= e review from apps UDP users that would be less likely to happen if hurried i= n text about tcp SCTP etc. There is no document in the RFC series that docum= ent UDP API - this may be helpful roadmap to find this info. Two documents a= re easier to maintain and cite than one. Disadvantages includes two RFC numbers. We do not expect huge changes. Howev= er : Any changes to the main doc would need to be kept consistent in the dra= ft, etc. That to me suggests a need to publish as a pair, if we make 2 docs.= Gorry > On 10 Oct 2016, at 10:11, Mirja K=C3=BChlewind wrote: >=20 > Hi all, >=20 > quick question: what=E2=80=99s the advantage of having this as a separate d= oc instead of merging it with draft-ietf-taps-transports-usage (which was th= e original plan to my understanding)? >=20 > Mirja >=20 >=20 >> Am 06.10.2016 um 21:57 schrieb Aaron Falk : >>=20 >> IMO, this is obviously in scope for TAPS and a useful contribution. I=E2= =80=99d like to hear any dissenting opinions about adopting this doc as a wg= item. >>=20 >> =E2=80=94aaron >>=20 >>=20 >>> On Oct 6, 2016, at 3:46 AM, Michael Welzl wrote: >>>=20 >>> hi, >>>=20 >>> clarification: yes i said what's written below, but i think this is the f= irst time the taps folks hear about it. so if that's fine with everyone, th= at's our plan - it seemed to us to be the most reasonable approach. >>>=20 >>> about adopting this separate document, it makes sense to me >>>=20 >>>=20 >>> Sent from my iPhone >>>=20 >>>> On 6. okt. 2016, at 10.22, Gorry Fairhurst wrote= : >>>>=20 >>>> We have just submitted an updated copy of the UDP usage draft we have b= een working on in TAPS. >>>>=20 >>>> Specifically: >>>>=20 >>>> (1) It omits the text for pass 2 and 3 that we now expect to be directl= y incorporated in draft-ietf-taps-transport-usage. >>>> Michael Welzl I think indicated that this text will be copied from rev -= usage-udp-02. >>>>=20 >>>> (2) It contains small changes to the document text to allow this to be p= ublsihed as a separate document. The WG discussed whether such a document co= uld be adopted for publication as a pair with draft-ietf-taps-transport-usag= e. The authors are now looking to the group to know if the WG would like to= adopt this and then what further work may be needed. >>>>=20 >>>> Best wishes, >>>>=20 >>>> Tom & Gorry >>>>=20 >>>>=20 >>>>> On 05/10/2016 21:46, internet-drafts@ietf.org wrote: >>>>> A new version of I-D, draft-fairhurst-taps-transports-usage-udp-03.txt= >>>>> has been successfully submitted by Godred Fairhurst and posted to the >>>>> IETF repository. >>>>>=20 >>>>> Name: draft-fairhurst-taps-transports-usage-udp >>>>> Revision: 03 >>>>> Title: Features of the User Datagram Protocol (UDP) and Lightwe= ight UDP (UDP- Lite) Transport Protocols >>>>> Document date: 2016-10-05 >>>>> Group: Individual Submission >>>>> Pages: 18 >>>>> URL: https://www.ietf.org/internet-drafts/draft-fairhurst-t= aps-transports-usage-udp-03.txt >>>>> Status: https://datatracker.ietf.org/doc/draft-fairhurst-taps-= transports-usage-udp/ >>>>> Htmlized: https://tools.ietf.org/html/draft-fairhurst-taps-trans= ports-usage-udp-03 >>>>> Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-fairhurst-ta= ps-transports-usage-udp-03 >>>>>=20 >>>>> Abstract: >>>>> This document describes how the User Datagram Protocol (UDP) and the >>>>> Lightweight User Datagram Protocol (UDP-Lite) transport protocols >>>>> expose services to applications and how an application can configure >>>>> and use the features offered by the transport service. The document >>>>> is intended as a contribution to the Transport Services (TAPS) >>>>> working group to assist in analysis of the UDP and UDP-Lite transport >>>>> interface. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> Please note that it may take a couple of minutes from the time of subm= ission >>>>> 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 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps From nobody Mon Oct 10 07:36:32 2016 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 16B29129526 for ; Mon, 10 Oct 2016 07:36:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.896 X-Spam-Level: X-Spam-Status: No, score=-9.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.996] 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 MN5G8n9o4Rj5 for ; Mon, 10 Oct 2016 07:36:30 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 C0289129479 for ; Mon, 10 Oct 2016 07:36:30 -0700 (PDT) Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u9AEZTLv002962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 10 Oct 2016 07:35:31 -0700 (PDT) To: "Gorry (erg)" , =?UTF-8?Q?Mirja_K=c3=bchlewind?= References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> From: Joe Touch Message-ID: Date: Mon, 10 Oct 2016 07:35:28 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: Cc: Aaron Falk , Michael Welzl , taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 14:36:32 -0000 On 10/10/2016 3:15 AM, Gorry (erg) wrote: > ... There is no document in the RFC series that document UDP API - this may be helpful roadmap to find this info. Two documents are easier to maintain and cite than one. RFC1122 defines one in Section 4.1.4, but it basically points off to a definition of the IP API in Section 3.4, which ignores the issue of controlling source and destination ports. The true UDP API ought to be defined in the same way the TCP API is defined in RFC793, FWIW. I've proposed a way forward for UDP options; as a result, I'd be glad to take a shot at a draft UDP API doc if useful. Joe From nobody Mon Oct 10 09:56:55 2016 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 52B6E1294B7 for ; Mon, 10 Oct 2016 09:56:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.196 X-Spam-Level: X-Spam-Status: No, score=-7.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.996] 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 S9Bmbxvs6TMy for ; Mon, 10 Oct 2016 09:56:52 -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 DE5AD129499 for ; Mon, 10 Oct 2016 09:56:51 -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 4E32B1B001E0; Mon, 10 Oct 2016 19:54:31 +0100 (BST) Received: from 139.133.217.68 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 10 Oct 2016 17:56:47 +0100 Message-ID: <8ffff0caab40d9937dacd93b60ed4ba7.squirrel@erg.abdn.ac.uk> In-Reply-To: References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> Date: Mon, 10 Oct 2016 17:56:47 +0100 From: gorry@erg.abdn.ac.uk To: "Joe Touch" 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: Cc: taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 16:56:54 -0000 See below. > > On 10/10/2016 3:15 AM, Gorry (erg) wrote: >> ... There is no document in the RFC series that document UDP API - this >> may be helpful roadmap to find this info. Two documents are easier to >> maintain and cite than one. > > RFC1122 defines one in Section 4.1.4, but it basically points off to a > definition of the IP API in Section 3.4, which ignores the issue of > controlling source and destination ports. > > The true UDP API ought to be defined in the same way the TCP API is > defined in RFC793, FWIW. > OK, so in the context of TAPS, the WG called for a list of UDP services. This is what is in the ID. I thought there may something useful to publishing this as a companion INFO RFC alongside the connection-oriented services ID. I suggest it may help to indicate what an App may need to know to use UDP. This ID clearly isn't an API spec. > I've proposed a way forward for UDP options; as a result, I'd be glad to > take a shot at a draft UDP API doc if useful. I don't personally know whether an API spec for UDP is useful or not, but suspect the list of services needed by UDP Apps is the thing the WG is presnetly looking for. Gorry > Joe > > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps > From nobody Mon Oct 10 10:11:52 2016 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 3B31912973B for ; Mon, 10 Oct 2016 10:11:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.895 X-Spam-Level: X-Spam-Status: No, score=-9.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.996] 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 4qNVW7ywaSp6 for ; Mon, 10 Oct 2016 10:11:49 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 BB7F5129499 for ; Mon, 10 Oct 2016 10:11:49 -0700 (PDT) Received: from [128.9.184.153] ([128.9.184.153]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u9AHAKGN025167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 10 Oct 2016 10:10:21 -0700 (PDT) To: gorry@erg.abdn.ac.uk References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> <8ffff0caab40d9937dacd93b60ed4ba7.squirrel@erg.abdn.ac.uk> From: Joe Touch Message-ID: <0c7bd675-da36-4247-f89d-67805f030cdc@isi.edu> Date: Mon, 10 Oct 2016 10:10:19 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <8ffff0caab40d9937dacd93b60ed4ba7.squirrel@erg.abdn.ac.uk> Content-Type: multipart/alternative; boundary="------------89E4B6A10498367C3D47DB19" X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: Cc: taps@ietf.org Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 17:11:51 -0000 This is a multi-part message in MIME format. --------------89E4B6A10498367C3D47DB19 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Hi, Gorry (et al.), On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk wrote: > ... > OK, so in the context of TAPS, the WG called for a list of UDP services. > This is what is in the ID. ... > > This ID clearly isn't an API spec. > > ... > I don't personally know whether an API spec for UDP is useful or not, but > suspect the list of services needed by UDP Apps is the thing the WG is > presnetly looking for. I have to admit I have no idea what you mean by "the list of services needed by UDP Apps" if that doesn't basically start and end with the UDP API. Anything else needed by UDP apps isn't needed because they're UDP. And having that list (of "things besides the UDP API") without a proper UDP API wouldn't be very useful. Joe --------------89E4B6A10498367C3D47DB19 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit 
Hi, Gorry (et al.),

On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk wrote:

...
OK, so in the context of TAPS, the WG called for a list of UDP services.
This is what is in the  ID. ...

This ID clearly isn't an API spec.

...
I don't personally know whether an API spec for UDP is useful or not, but
suspect the list of services needed by UDP Apps is the thing the WG is
presnetly looking for.

I have to admit I have no idea what you mean by "the list of services
needed by UDP Apps" if that doesn't basically start and end with the UDP
API.

Anything else needed by UDP apps isn't needed because they're UDP. And
having that list (of "things besides the UDP API") without a proper UDP
API wouldn't be very useful.

Joe
--------------89E4B6A10498367C3D47DB19-- From nobody Wed Oct 12 22:39:00 2016 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 DCA3B129409 for ; Wed, 12 Oct 2016 22:38:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.895 X-Spam-Level: X-Spam-Status: No, score=-4.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.996] 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 x1icUV99AuHM for ; Wed, 12 Oct 2016 22:38:56 -0700 (PDT) Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 1EDF11295CB for ; Wed, 12 Oct 2016 22:38:56 -0700 (PDT) Received: from mail-mx2.uio.no ([129.240.10.30]) by mail-out01.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1buYjF-00062V-Qt for taps@ietf.org; Thu, 13 Oct 2016 07:38:53 +0200 Received: from 151.red-88-21-19.staticip.rima-tde.net ([88.21.19.151] helo=[10.2.5.169]) by mail-mx2.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from ) id 1buYjF-0006jl-46; Thu, 13 Oct 2016 07:38:53 +0200 Content-Type: multipart/alternative; boundary="Apple-Mail=_8A913CF1-BB23-404D-BAA1-DE5997061A72" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Michael Welzl In-Reply-To: <0c7bd675-da36-4247-f89d-67805f030cdc@isi.edu> Date: Thu, 13 Oct 2016 07:38:50 +0200 Message-Id: <8A00B6F3-F0D6-4422-85A3-F2F2762BDF0C@ifi.uio.no> References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> <8ffff0caab40d9937dacd93b60ed4ba7.squirrel@erg.abdn.ac.uk> <0c7bd675-da36-4247-f89d-67805f030cdc@isi.edu> To: Joe Touch X-Mailer: Apple Mail (2.3124) X-UiO-SPF-Received: X-UiO-Ratelimit-Test: rcpts/h 5 msgs/h 3 sum rcpts/h 8 sum msgs/h 5 total rcpts 47135 max rcpts/h 54 ratelimit 0 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: B7D62BE04CB05C7EC2DA03E56A633BC6CE0B1C1C X-UiO-SPAM-Test: remote_host: 88.21.19.151 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 5 max/h 3 blacklist 0 greylist 0 ratelimit 0 Archived-At: Cc: " Fairhurst" , "taps@ietf.org" Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 05:38:59 -0000 --Apple-Mail=_8A913CF1-BB23-404D-BAA1-DE5997061A72 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 > On 10. okt. 2016, at 19.10, Joe Touch wrote: >=20 > Hi, Gorry (et al.), >=20 > On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk = wrote: >> ... >> OK, so in the context of TAPS, the WG called for a list of UDP = services. >> This is what is in the ID. ... >>=20 >> This ID clearly isn't an API spec. >>=20 >> ... >> I don't personally know whether an API spec for UDP is useful or not, = but >> suspect the list of services needed by UDP Apps is the thing the WG = is >> presnetly looking for. > I have to admit I have no idea what you mean by "the list of services > needed by UDP Apps" if that doesn't basically start and end with the = UDP > API. It=92s not an API spec but it does =93basically start and end=94 with = the API. It follows the same approach as draft-ietf-taps-transports-usage, which also very much =93basically = starts and ends=94 with the API, in how primitives are derived. Details on this relationship are maybe clearest = in the appendix, where we describe how to contribute text (in some future version, this should probably be = renamed into =93how this document was created=94). > Anything else needed by UDP apps isn't needed because they're UDP. And > having that list (of "things besides the UDP API") without a proper = UDP > API wouldn't be very useful. It certainly is the right input for anyone creating an API. E.g., it IS = the input from which we derive our protocol-independent API in the NEAT project. Cheers, Michael --Apple-Mail=_8A913CF1-BB23-404D-BAA1-DE5997061A72 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
On 10. okt. 2016, at 19.10, Joe Touch <touch@isi.edu> = wrote:

=20 =20 
Hi, Gorry (et al.),

On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk wrote:

...
OK, so in the context of TAPS, the WG called for a list of UDP services.
This is what is in the  ID. ...

This ID clearly isn't an API spec.

...
I don't personally know whether an API spec for UDP is useful or not, =
but
suspect the list of services needed by UDP Apps is the thing the WG is
presnetly looking for.

I have to admit I have no idea what you =
mean by "the list of services
needed by UDP Apps" if that doesn't basically start and end with the UDP
API.

It=92s not an = API spec but it does =93basically start and end=94 with the API. It = follows the same approach as
draft-ietf-taps-transports-usage, = which also very much =93basically starts and ends=94 with the API, in = how
primitives are derived. Details on this relationship are = maybe clearest in the appendix, where we describe
how to = contribute text  (in some future version, this should probably be = renamed into =93how this document was
created=94).
Anything else needed by UDP apps isn't needed =
because they're UDP. And
having that list (of "things besides the UDP API") without a proper UDP
API wouldn't be very useful.

It certainly is = the right input for anyone creating an API. E.g., it IS the input from = which we derive our protocol-independent
API in the NEAT = project.

Cheers,
Michael

= --Apple-Mail=_8A913CF1-BB23-404D-BAA1-DE5997061A72-- From nobody Fri Oct 21 16:28:02 2016 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 E60E312998C; Fri, 21 Oct 2016 16:21:21 -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.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147709208193.28214.5586959158286607675.idtracker@ietfa.amsl.com> Date: Fri, 21 Oct 2016 16:21:21 -0700 Archived-At: Cc: spencerdawkins.ietf@gmail.com, taps@ietf.org Subject: [Taps] taps - Requested session has been scheduled for IETF 97 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 23:21:26 -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 (1:30:00) Wednesday, Morning Session I 0930-1100 Room Name: Grand Ballroom 2 size: 200 --------------------------------------------- Request Information: --------------------------------------------------------- Working Group Name: Transport Services Area Name: Transport Area Session Requester: Aaron Falk Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 80 Conflicts to Avoid: First Priority: maprg dispatch tcpm iccrg tsvwg ippm rmcat aqm tsvarea appsawg apparea quic Second Priority: webpush tcpinc nvo3 mptcp icnrg httpbis irtfopen Third Priority: mmusic tram Special Requests: --------------------------------------------------------- From nobody Tue Oct 25 05:55:59 2016 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 305C7129462; Tue, 25 Oct 2016 05:55:57 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147740015719.15178.1525272535015458570.idtracker@ietfa.amsl.com> Date: Tue, 25 Oct 2016 05:55:57 -0700 Archived-At: Cc: taps@ietf.org Subject: [Taps] I-D Action: draft-ietf-taps-transports-12.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 12:55:57 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Services of the IETF. Title : Services provided by IETF transport protocols and congestion control mechanisms Authors : Godred Fairhurst Brian Trammell Mirja Kuehlewind Filename : draft-ietf-taps-transports-12.txt Pages : 53 Date : 2016-10-25 Abstract: This document describes, surveys, classifies and compares the protocol mechanisms provided by existing IETF protocols, as background for determining a common set of transport services. It examines the Transmission Control Protocol (TCP), Multipath TCP, the Stream Control Transmission Protocol (SCTP), the User Datagram Protocol (UDP), UDP-Lite, the Datagram Congestion Control Protocol (DCCP), the Internet Control Message Protocol (ICMP), the Realtime Transport Protocol (RTP), File Delivery over Unidirectional Transport/Asynchronous Layered Coding Reliable Multicast (FLUTE/ALC), and NACK-Oriented Reliable Multicast (NORM), Transport Layer Security (TLS), Datagram TLS (DTLS), and the Hypertext Transport Protocol (HTTP), when HTTP is used as a pseudotransport. This survey provides background for the definition of transport services within the TAPS working group. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-taps-transports-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transports-12 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 Tue Oct 25 05:57:33 2016 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 CF5CC129532 for ; Tue, 25 Oct 2016 05:57:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.333 X-Spam-Level: X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, 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 7lq-EDrN3JWP for ; Tue, 25 Oct 2016 05:57:28 -0700 (PDT) Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id B2532129546 for ; Tue, 25 Oct 2016 05:57:27 -0700 (PDT) Received: from [IPv6:2001:67c:10ec:2a49:8000::b9] (unknown [IPv6:2001:67c:10ec:2a49:8000::b9]) by trammell.ch (Postfix) with ESMTPSA id EF45F1A0F38 for ; Tue, 25 Oct 2016 14:57:26 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_1A7274DC-E973-4511-90C6-1DDCB337C823"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Pgp-Agent: GPGMail From: Brian Trammell In-Reply-To: <147740015719.15178.1525272535015458570.idtracker@ietfa.amsl.com> Date: Tue, 25 Oct 2016 14:57:26 +0200 Message-Id: <6D73236E-751A-4E0C-94C5-6BF49F590D30@trammell.ch> References: <147740015719.15178.1525272535015458570.idtracker@ietfa.amsl.com> To: taps WG X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Taps] I-D Action: draft-ietf-taps-transports-12.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 12:57:32 -0000 --Apple-Mail=_1A7274DC-E973-4511-90C6-1DDCB337C823 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings, all, This revision addresses comments in the area reviews; the document is = ready for the IESG. Cheers, Brian > On 25 Oct 2016, at 14:55, 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 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-12.txt > Pages : 53 > Date : 2016-10-25 >=20 > Abstract: > This document describes, surveys, classifies and compares the > protocol mechanisms provided by existing IETF protocols, as > background for determining a common set of transport services. It > examines the Transmission Control Protocol (TCP), Multipath TCP, the > Stream Control Transmission Protocol (SCTP), the User Datagram > Protocol (UDP), UDP-Lite, the Datagram Congestion Control Protocol > (DCCP), the Internet Control Message Protocol (ICMP), the Realtime > Transport Protocol (RTP), File Delivery over Unidirectional > Transport/Asynchronous Layered Coding Reliable Multicast = (FLUTE/ALC), > and NACK-Oriented Reliable Multicast (NORM), Transport Layer = Security > (TLS), Datagram TLS (DTLS), and the Hypertext Transport Protocol > (HTTP), when HTTP is used as a pseudotransport. This survey = provides > background for the definition of transport services within the 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-12 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transports-12 >=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 --Apple-Mail=_1A7274DC-E973-4511-90C6-1DDCB337C823 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 iQIcBAEBCgAGBQJYD1a2AAoJEIoSt78L6kajCoAP/jQ6bkdxbMej/5YtgLmhUnXz DM949qOtVdVL4MTm/k/aUfJOJYRjo6ToIIlKoVvRcDMQIaNzuwbZ1oToRpgR1hX4 J56o7u0mzou7CWL4alrovDhJRuXBjLLrKf7oh4Ht1jHn64EJWhGQ5E/EHYML5Bn6 58FzyoinazUsgFMAxHl+wA4bQON43mQN6SE44WMV7ibIHRzOLXD6pyZ5or7pmTty Ka1bWdEOnWWqXxe5lZjTns2/5xX5ebVDbdU3tUbdi+Dr5ybE4msFnucIhttGkYTu v/vNW7v0XXdhoVhuL/JdQqX3ODEUtRRYmm3BCkAii0cb9Th3JdHsnusCx/KBcOEb zzdVF0OHhig1qec0J1IGDRMzyvmaIXiqTb6CMCNDqj0haWTjd3bmmlJB6E6aoUlx qDKnR2f64JfoGTIQOaVm+t+7wmPPme2iUQZCaqj9/fBlz11o+jPnb040OwmQZcg5 gG4hh9Ly3Q1om2w8oCtddPij3qJpbsIofPgatUeknxiZUMaZqBrsQRWQEDOpSg4h KrB5+Exb6hAhCsygZBv5cWqnuH7BxkfwVeZXchZo///4QS07m6ZRSksOz4vKlGbV Z5aYKzogu+dxz2x9i/DxpUH6/H7NTen+QvKLcX/ZoQaPgoNBRMbr1A9/qzDWm6cx LUnZkU8DoLo+fRRoOKGv =/l8n -----END PGP SIGNATURE----- --Apple-Mail=_1A7274DC-E973-4511-90C6-1DDCB337C823-- From nobody Tue Oct 25 09:10:18 2016 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 07356129771 for ; Tue, 25 Oct 2016 09:10:17 -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 zvSGNIaQ8bW0 for ; Tue, 25 Oct 2016 09:10:16 -0700 (PDT) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 8C6DF1296EE for ; Tue, 25 Oct 2016 09:10:15 -0700 (PDT) Received: by mail-yw0-x22e.google.com with SMTP id w3so1747341ywg.1 for ; Tue, 25 Oct 2016 09:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YuxdddKcPX97oeGiz35E+WnGNOHKpzH9YWEXFFWOsBg=; b=fnLUuFBuQxt6ZbxgRfci1gkfCfuSlAKpmtO4Q1uSQSQysig7JuN9uXf8UZ8f+WXsOb oGX7S9ZMTG74Wt+PAofm0hfeC202J08PNeZN3bHaWV/5H8CNZ7UYjsg+sQGEc3AJn+JA H6JPC6MMLPIyaQdkwcSCeZYVZsg7CA5LgicrVTmWVm1tjppZWtMqN6aMrBqmtGKpl/iR mlOo2HcePIHwUEzYvWRFhctDEc+qQIg1J7/Z/eBMgazxwVEbid6VLDPtFYXKg44VuZPS 2E5DpkgPLoiXCS5r6Z/qvSB/1X27vexAQBDXvfUDgyhDqXoKf/smplHvkGTHKlM79qDj sJKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YuxdddKcPX97oeGiz35E+WnGNOHKpzH9YWEXFFWOsBg=; b=J2889JAL6bRi9+gtp/QXe6LGFNsc2DZ680aOJUcrM80oLixsL0drYdvq39T0pn9QsO 0TVcbUKvaRk+l+OEl+6kFYd2HkpyzqszuGQYgVNzZHDWKfMJRI6iqAsuqfwZUG+I2NDj Okz4sRtQuWHb2jwk//S3dvnm1dGCor3yDb0Ox5uHwHfU+d2fSo4AQFmQjdaqMrEXVMhx WxEKEusQ48zaQLuVY7NlWPlTX0IGFXjRmb/DKs/LmuNJCdXw6PNBLsM8fZClw9JSJC5I fZM1zr3cXwcNat7SX87cggqmvc4Ry9+WHqKsLvBvJ0VjvYXem5Eqavp0CqdozVM8Oub5 hMIg== X-Gm-Message-State: ABUngvf7PaayETE4vfdy8IEMb8bZL25s4WCDfT1kIsyaNTLVQFAxFXvbRsmAJRd71/DyX9CP2WjEhaq2eGaVUg== X-Received: by 10.13.219.80 with SMTP id d77mr2085778ywe.61.1477411814571; Tue, 25 Oct 2016 09:10:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.36.16 with HTTP; Tue, 25 Oct 2016 09:10:14 -0700 (PDT) In-Reply-To: <6D73236E-751A-4E0C-94C5-6BF49F590D30@trammell.ch> References: <147740015719.15178.1525272535015458570.idtracker@ietfa.amsl.com> <6D73236E-751A-4E0C-94C5-6BF49F590D30@trammell.ch> From: Spencer Dawkins at IETF Date: Tue, 25 Oct 2016 11:10:14 -0500 Message-ID: To: Brian Trammell Content-Type: multipart/alternative; boundary=001a114fab7e650a0b053fb2be13 Archived-At: Cc: taps WG Subject: Re: [Taps] I-D Action: draft-ietf-taps-transports-12.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 16:10:17 -0000 --001a114fab7e650a0b053fb2be13 Content-Type: text/plain; charset=UTF-8 Hi, Brian, On Tue, Oct 25, 2016 at 7:57 AM, Brian Trammell wrote: > Greetings, all, > > This revision addresses comments in the area reviews; the document is > ready for the IESG. Thanks for getting this out, pre-IETF 97. I'll put it on the first telechat agenda after the meeting (the agendas before IETF 97 are quite full). I did notice that the newly inserted text "UDP on its own does not provide support for segmentation" seems to lack parentheses, or some other delimiters. I'm not waiting for this, but if one of the authors wants to submit a revision that fixes that, your conversation with your GenART reviewer will be shorter :-) Spencer --001a114fab7e650a0b053fb2be13 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, Brian,

On Tue, Oct 25, 2016 at 7:57 AM, Brian Trammell <ietf@trammell.ch= > wrote:
Greetings, all,

This revision addresses comments in the area reviews; the document is ready= for the IESG.

Thanks for getting this out,= pre-IETF 97. I'll put it on the first telechat agenda after the meetin= g (the agendas before IETF 97 are quite full).

I did no= tice that the newly inserted text "UDP on its own does not provide sup= port for segmentation" seems to lack parentheses, or some other delimi= ters. I'm not waiting for this, but if one of the authors wants to subm= it a revision that fixes that, your conversation with your GenART reviewer = will be shorter :-)

Spencer
--001a114fab7e650a0b053fb2be13-- From nobody Thu Oct 27 05:52:47 2016 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 5CEF5129449 for ; Thu, 27 Oct 2016 05:52:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.333 X-Spam-Level: X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, 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 rgPi7fd1C06U for ; Thu, 27 Oct 2016 05:52:42 -0700 (PDT) Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id D40AD12946F for ; Thu, 27 Oct 2016 05:52:41 -0700 (PDT) Received: from [IPv6:2001:67c:10ec:2a49:8000::b9] (unknown [IPv6:2001:67c:10ec:2a49:8000::b9]) by trammell.ch (Postfix) with ESMTPSA id 0A1CA1A05D5 for ; Thu, 27 Oct 2016 14:52:41 +0200 (CEST) From: Brian Trammell X-Pgp-Agent: GPGMail Content-Type: multipart/signed; boundary="Apple-Mail=_7C3F8676-D2E5-4024-B2EF-2084568EF71D"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Thu, 27 Oct 2016 14:52:40 +0200 References: <147756225934.18900.10951893813111037167.idtracker@ietfa.amsl.com> To: taps WG Message-Id: <61285C6A-6A02-4A45-9B00-F88ACF40F412@trammell.ch> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Archived-At: Subject: [Taps] Fwd: New Version Notification for draft-trammell-post-sockets-00.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 12:52:46 -0000 --Apple-Mail=_7C3F8676-D2E5-4024-B2EF-2084568EF71D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings, TAPS, We've submitted an initial version of our Post Sockets abstract = interface draft, draft-trammell-post-sockets. It's not yet clear that = we'd want this to be adopted by the TAPS working group for a future = milestone in partial fulfillment of point 3 on the charter -- perhaps = the ideas here are merely an illustration of what is possible in the = space, that could point toward a more concrete definition of an abstract = interface for TAPS. We'd like to discuss this point in Seoul. Thanks, cheers, Brian > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: New Version Notification for = draft-trammell-post-sockets-00.txt > Date: 27 October 2016 at 11:57:39 GMT+2 > To: "Mirja Kuehlewind" , "Tommy = Pauly" , "Brian Trammell" , "Colin = Perkins" >=20 >=20 > A new version of I-D, draft-trammell-post-sockets-00.txt > has been successfully submitted by Brian Trammell and posted to the > IETF repository. >=20 > Name: draft-trammell-post-sockets > Revision: 00 > Title: Post Sockets, An Abstract Programming Interface = for the Transport Layer > Document date: 2016-10-27 > Group: Individual Submission > Pages: 17 > URL: = https://www.ietf.org/internet-drafts/draft-trammell-post-sockets-00.txt > Status: = https://datatracker.ietf.org/doc/draft-trammell-post-sockets/ > Htmlized: = https://tools.ietf.org/html/draft-trammell-post-sockets-00 >=20 >=20 > Abstract: > This document describes Post Sockets, an asynchronous abstract > programming interface for the atomic transmission of objects in an > explicitly multipath environment. Post replaces connections with > long-lived associations between endpoints, with the possibility to > cache cryptographic state in order to reduce amortized connection > latency. We present this abstract interface as an illustration of > what is possible with present developments in transport protocols > when freed from the strictures of the current sockets API. >=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=_7C3F8676-D2E5-4024-B2EF-2084568EF71D 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 iQIcBAEBCgAGBQJYEfiYAAoJEIoSt78L6kajkLkQAMfHCEg/qg+BlzwgC+OY9JV7 ObpaXdUY+Mlxp9WgxCTv6jvPadjb4SFKy1w4K98ZSjCAzkF+vFqzCxo4j4692Hcz 0m/ZNbG22J6tl6RTeXddEjqwpxuzyMp90raqSpTSDW4v/+qPABhfn//l8NwfoRfq ULannW0SvRGwT32MfIoCeyavbPmA/yR+Wc2hrtnWMqPJWRyUF/hl+al5p5KxaSUC WZg4vHVZr/5WeUcdVkOwKLckjB0WjAeKAr+CZzV3z/Cj3ETxrY0qzMCRazSrcfFp yy9/1hUqk9AJkLk02CYiwEGcRlSj+id/jnoAQgo7cfINec5FVtng/F64eUfRbv08 6QGzHNJxfSjGARL9SeYcnk2fji2xa5WTau84v4fmdAKNkE1P90ah++4M3gjwJg26 ec3BrQYFDONI1lG3blWKdlXDsPY2di+BYFmAqZNLsAF29D8mmujwGM8/VRFVrxkF mPAwbwepJraJ20Rx8TMkjNheUdaY2hcTD6nhEHCQbVlte53Y1sjtvEwyNL/DsFwE p1lsbVnQ3Be6YjZrX8GZQmCSrXsMJx8nDDsi7CPJA3OitnzoRgnygU19MGpRorfq DIOujUgzo8rlhagZcrXzD5OIB+O4TGe+u5mzlVqaGbS/UabTL4ByROVoUgHVR5aa XHuH5+m+Hp23G12Qc1Rr =bGT/ -----END PGP SIGNATURE----- --Apple-Mail=_7C3F8676-D2E5-4024-B2EF-2084568EF71D-- From nobody Thu Oct 27 12:53:44 2016 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 508AA1298AB for ; Thu, 27 Oct 2016 12:53:43 -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 RYTwexpvmQxh for ; Thu, 27 Oct 2016 12:53:41 -0700 (PDT) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 46976129890 for ; Thu, 27 Oct 2016 12:53:41 -0700 (PDT) Received: by mail-qt0-x22c.google.com with SMTP id p16so23474272qta.0 for ; Thu, 27 Oct 2016 12:53:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=rV+NNmyJkkCONhTB/TYEiJSawK+chDDjbXKn555e/OI=; b=hCw/m91n36sCDqEcO8sMKLG8G2eswfCJtIkHJr9ceYRz5hltTy1kHvUMrgCSXRvPD9 5Ss3n7i6D96kbqjrRjF53yQ7xylwsyfslO9A0nTMWMg6fVJAOeOu6xbzq0lY68D74t8H thMq5oCj0g5Hk3v+jRtuD+M+8DeeY3lmsqniaRjncDaOhlDLiPhka8YllEwFPPidLfs+ e7dyMrrgT0qGJtdIrchy243HoDcjXQL/2ErtnNWaQwREQLxhX2G25BekOXmK8kebnSLj X0pFGQC1UpVxH6SUdVq1CX3aKqKfrD54tgCEPRDCHdkFj0IeIEM9b3Y3B/10yZDo/O5r X9Bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=rV+NNmyJkkCONhTB/TYEiJSawK+chDDjbXKn555e/OI=; b=cjK9HUKWb4nSHBHE4v8oRz+Ct0lZAt5rkw4FNOIbWq/sa8dp96JlW6bMljISBt6sLS 7OIHHbmAxXOWZxObHDc/h3Bg5ZPZeZTydHSBaeueacurPNNV5p8d2qoPwVuVyCleIDjo As7xMAG4Yfw9TaI2nH8i3hXSUyWuNtjrRhWsptCwVErCPCRqXxSHu6+Jq5ND3UmBUhqP DKc6rpT/fVGSXoVkzMsHdaFfrAzkMXESET/n4GjdW3QMobV17GEqHdpCfeZnQj+Bj6QW AyQB9yKmkkI2koQCeSYOnMaC5t+kwwADYqXiA5WAGChsfAIC8blURihie3dAJmtmij4W 1qCQ== X-Gm-Message-State: ABUngvcwTsDn+0Ke/sfXUJwpcOI9RQL9b40hs+IngYoVeBvodVmc74R+1BZtnbZ4d75bqQ== X-Received: by 10.237.42.40 with SMTP id c37mr1385598qtd.92.1477598020289; Thu, 27 Oct 2016 12:53:40 -0700 (PDT) Received: from bos-mpy2z.kendall.corp.akamai.com (a72-246-0-10.deploy.akamaitechnologies.com. [72.246.0.10]) by smtp.gmail.com with ESMTPSA id v24sm4432520qtv.15.2016.10.27.12.53.39 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 27 Oct 2016 12:53:39 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_0206D3D7-0098-4DB7-9704-EDBFEDECB59C" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Aaron Falk In-Reply-To: <8A00B6F3-F0D6-4422-85A3-F2F2762BDF0C@ifi.uio.no> Date: Thu, 27 Oct 2016 15:53:39 -0400 Message-Id: References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk> <8ffff0caab40d9937dacd93b60ed4ba7.squirrel@erg.abdn.ac.uk> <0c7bd675-da36-4247-f89d-67805f030cdc@isi.edu> <8A00B6F3-F0D6-4422-85A3-F2F2762BDF0C@ifi.uio.no> To: Gorry Fairhurst X-Mailer: Apple Mail (2.3124) Archived-At: Cc: "taps@ietf.org" Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 19:53:43 -0000 --Apple-Mail=_0206D3D7-0098-4DB7-9704-EDBFEDECB59C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Seems to me like we have a consensus to make this a working group doc. = We=92ll get this re-issued with a working group filename. =97aaron > On Oct 13, 2016, at 1:38 AM, Michael Welzl wrote: >=20 >>=20 >> On 10. okt. 2016, at 19.10, Joe Touch > wrote: >>=20 >> Hi, Gorry (et al.), >>=20 >> On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk = wrote: >>> ... >>> OK, so in the context of TAPS, the WG called for a list of UDP = services. >>> This is what is in the ID. ... >>>=20 >>> This ID clearly isn't an API spec. >>>=20 >>> ... >>> I don't personally know whether an API spec for UDP is useful or = not, but >>> suspect the list of services needed by UDP Apps is the thing the WG = is >>> presnetly looking for. >> I have to admit I have no idea what you mean by "the list of services >> needed by UDP Apps" if that doesn't basically start and end with the = UDP >> API. >=20 > It=92s not an API spec but it does =93basically start and end=94 with = the API. It follows the same approach as > draft-ietf-taps-transports-usage, which also very much =93basically = starts and ends=94 with the API, in how > primitives are derived. Details on this relationship are maybe = clearest in the appendix, where we describe > how to contribute text (in some future version, this should probably = be renamed into =93how this document was > created=94). >=20 >> Anything else needed by UDP apps isn't needed because they're UDP. = And >> having that list (of "things besides the UDP API") without a proper = UDP >> API wouldn't be very useful. >=20 > It certainly is the right input for anyone creating an API. E.g., it = IS the input from which we derive our protocol-independent > API in the NEAT project. >=20 > Cheers, > Michael >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps = --Apple-Mail=_0206D3D7-0098-4DB7-9704-EDBFEDECB59C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Seems to me like we have a consensus to make this a working = group doc.  We=92ll get this re-issued with a working group = filename.

=97aaron



On Oct 13, 2016, at 1:38 AM, = Michael Welzl <michawe@ifi.uio.no> wrote:


On = 10. okt. 2016, at 19.10, Joe Touch <touch@isi.edu> wrote:

Hi, Gorry (et al.),

On 10/10/2016 9:56 AM, gorry@erg.abdn.ac.uk wrote:

...
OK, so in the context of TAPS, the WG called for a list of UDP services.
This is what is in the  ID. ...

This ID clearly isn't an API spec.

...
I don't personally know whether an API spec for UDP is useful or not, =
but
suspect the list of services needed by UDP Apps is the thing the WG is
presnetly looking for.

I have to admit I have no =
idea what you mean by "the list of services
needed by UDP Apps" if that doesn't basically start and end with the UDP
API.

It=92s= not an API spec but it does =93basically start and end=94 with the API. = It follows the same approach as
draft-ietf-taps-transports-usage, which also very much = =93basically starts and ends=94 with the API, in how
primitives are derived. = Details on this relationship are maybe clearest in the appendix, where = we describe
how to = contribute text  (in some future version, this should probably be = renamed into =93how this document was
created=94).

Anything else needed by UDP apps isn't needed because they're =
UDP. And
having that list (of "things besides the UDP API") without a proper UDP
API wouldn't be very useful.

It = certainly is the right input for anyone creating an API. E.g., it IS the = input from which we derive our protocol-independent
API in the NEAT = project.

Cheers,
Michael

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

= --Apple-Mail=_0206D3D7-0098-4DB7-9704-EDBFEDECB59C-- From nobody Thu Oct 27 12:57:23 2016 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 4CDEE1295DD; Thu, 27 Oct 2016 12:57:22 -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.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147759824229.24694.17364016351052910301.idtracker@ietfa.amsl.com> Date: Thu, 27 Oct 2016 12:57:22 -0700 Archived-At: Subject: [Taps] The TAPS WG has placed draft-fairhurst-taps-transports-usage-udp in state "Adopted by a WG" X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 19:57:22 -0000 The TAPS WG has placed draft-fairhurst-taps-transports-usage-udp in state Adopted by a WG (entered by Aaron Falk) The document is available at https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp/ Comment: Extends TAPS transport analysis to cover UDP. From nobody Fri Oct 28 12:26:58 2016 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 7C6E6129665 for ; Fri, 28 Oct 2016 12:26:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 yP_zXBItMs0c for ; Fri, 28 Oct 2016 12:26:55 -0700 (PDT) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 57E3F12965E for ; Fri, 28 Oct 2016 12:26:55 -0700 (PDT) X-AuditID: c1b4fb30-b87ff70000000cb2-d8-5813a67c8b96 Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by (Symantec Mail Security) with SMTP id 0F.87.03250.C76A3185; Fri, 28 Oct 2016 21:26:53 +0200 (CEST) Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.24) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 28 Oct 2016 21:26:52 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ooha50uA/XDzHd4i7u02t8KYLW8cWTr8j2jlsYA/Wmw=; b=Ybb83eLowvFxO6xpOhyZyNDq7s0dS7ZJRZNNXNLV0rjvHBfh+8rvUbwI8YFmZmS3Fp7n1Kg5APfhDgq+I9GMNzx4LPRdEdaQeqL73eihSH1BMRDuVXItSBXnrdXD8owqmcrnVvFqXBIoRI8WyyJMDlqGdzaMEKTaIScZIpUiyjc= Received: from AM3PR07MB292.eurprd07.prod.outlook.com (10.242.108.153) by AM3PR07MB291.eurprd07.prod.outlook.com (10.242.108.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.679.5; Fri, 28 Oct 2016 19:26:49 +0000 Received: from AM3PR07MB292.eurprd07.prod.outlook.com ([fe80::4073:398:9056:882c]) by AM3PR07MB292.eurprd07.prod.outlook.com ([fe80::4073:398:9056:882c%14]) with mapi id 15.01.0707.002; Fri, 28 Oct 2016 19:26:49 +0000 From: Zaheduzzaman Sarker To: "taps@ietf.org" Thread-Topic: IETF97 agenda Thread-Index: AdIxURDFQPrFvmmNSSqOMk9zzAQ18w== Date: Fri, 28 Oct 2016 19:26:49 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=zaheduzzaman.sarker@ericsson.com; x-originating-ip: [95.109.38.59] x-ms-office365-filtering-correlation-id: acc99faf-0ba1-46f4-9678-08d3ff685d37 x-microsoft-exchange-diagnostics: 1; AM3PR07MB291; 6:7zx48dAdKTguWiMeSw4pbL2GHwzfGb+aUpxUO3FCqfUsyxxZQOWJACbHbiGyqL2Wu15ROt1Lb+TlVzod3BhOH13MnFqnwkhW+6std8eQebL6JlO4KFpxAFzmlrV4K6nR+7taHRSezvpBujkYwlbYmm95S21Xh0piiNdEg7PjFeJbQ9Kfz0kZtRJekg0OMBqa0c1tCh5E0mUSMxzJPqkMftqSkauEzhJTyf5xCpQjCoNgBxB38cTM8YLESP72J1d2tC0GJx0zJHhYL9NpRG6xA1iBzj44CoTLFQsXOSS90AvebOn1ejdoIT4wVJFNb6/X; 5:ykczimA0y5OJv1bbod6uwi/lF8Wko4J5QCrHlGzq6Onp9IYE0itC30iaYRFw6p9Ehua5wwkSAR2TVgVKoGmlbTAh97w+9CKpkROqySJI2SM04zYbO1bOFc19t6OX8Y1USK4pbDiR6WDwtDjIl4O1ws1bzNPZtfg5C6AkFRPp56E=; 24:PfxEA7924PuAo61qj3umQ1q3CGXUemS12k4+Cw0INGDTh07b/uIIIFMESUZvbhD5fPPNDiKwSIWHBFva62gyUtDF8l2rL4tMpf/HBbkyymQ=; 7:pWMt2HFx294S6qUYKNpGhxl1+PJjzUjoI/qbnj82lcr1Usl6MqDOqfiutr4Ek6yZoN3rq5CYhGDvZ5+gV0MySFBqEFIGBrlFUqmhimVNsH3wKqlW+BRSZINFpOaX044a4T0WKw898c5NGWY/+kkJ1vkOuMTkKbAbseaUR5m4EsWzPqYfplAP53w+txgsOW0yEIORinZ3WzBpjpmUdK8v5/upmR1yYfQf6camW58ocAWdGMa2MbnnZxAik512bzhNqq2HKu2U5wd1Z8AraAIF43j9xL8EI4Ks4LWWA7Zt21SSkmYEo7y/Y5SVg5VBmpVqC9hraiL5mdY+rtSXSBgTOu4YP6rqTzDPgd6d8UNg518= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM3PR07MB291; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(37575265505322)(120809045254105)(202460600054446)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:AM3PR07MB291; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB291; x-forefront-prvs: 0109D382B0 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(189002)(199003)(3280700002)(97736004)(15975445007)(2351001)(3660700001)(2900100001)(450100001)(5250100002)(2501003)(5660300001)(189998001)(106356001)(7116003)(11100500001)(2906002)(66066001)(33656002)(68736007)(50986999)(54356999)(229853001)(15974865002)(7846002)(7736002)(8936002)(9686002)(101416001)(305945005)(5002640100001)(86362001)(74316002)(5640700001)(19580405001)(110136003)(586003)(19580395003)(6916009)(76576001)(107886002)(105586002)(102836003)(7696004)(87936001)(81166006)(8676002)(92566002)(6116002)(1730700003)(81156014)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB291; H:AM3PR07MB292.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_AM3PR07MB292BA815C504FA23626E8C29FAD0AM3PR07MB292eurprd_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2016 19:26:49.3566 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB291 X-OriginatorOrg: ericsson.com X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFKsWRmVeSWpSXmKPExsUyM2K7hG7tMuEIg68fdS3uxDgweixZ8pMp gDGKyyYlNSezLLVI3y6BK+PqaamCjbIVd+c/ZW9gPCfVxcjJISFgIrHg+nfGLkYuDiGB9YwS 13v3sEA4JxglVh7uZANxWAR6mSXOzJ0ClZnKJPH1xgVWCOc+o8TBpgVADgcHm4CNxOPFfiBz RQSUJS7v38gGYgsLiElsnLiVCSIuLdH04Q8jhK0n0dj+hxXEZhFQlTh/+xoLiM0rECUx60UX M4jNCNT7/dQasF5mAXGJW0/mM0HcLSCxZM95ZghbVOLl43+sEPXJElO/trJBxBUkbkyfyAJh +0qcvn0U7E8JgWYOiX3bLkIlXCWm/18OZWdKnPh+HGpBjsSK13sZIextjBKHzshD2DIS817O YYEY9JpVYl3fHHaQhJBAqsTyta2MEB9LSdy90glly0i8uLMXHEDMAvkS71pzIZ4UlDg58wnL BEa1WUh+m4VQNQtJFUSJnsSNqVPYIGxtiWULXzND2LoSM/4dYkEWX8DIvopRtDi1OCk33chI L7UoM7m4OD9PLy+1ZBMjMMUc3PLbYAfjy+eOhxgFOBiVeHgVJglHCLEmlhVX5h5ilOBgVhLh NZkPFOJNSaysSi3Kjy8qzUktPsQozcGiJM5rtvJ+uJBAemJJanZqakFqEUyWiYNTqoHReG49 z6rH4U1JmfyaZxNWGk8peCq/L3iSy+FnZxb6Lv3CP+V+v4v0zZxfOzRZSzcGMWopvegUTWbf kqTDkul5wJVzyqxVx9y29fulTDA7WT4hpGPV9PksLzhXP2r0ePYhgNXsg5X/jzl3Qz7rq1/z kD/0as6xSd9vV1p1xH8ICNE34ZnOf6tAiaU4I9FQi7moOBEAIe3JES0DAAA= Archived-At: Subject: [Taps] IETF97 agenda X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 19:26:57 -0000 --_000_AM3PR07MB292BA815C504FA23626E8C29FAD0AM3PR07MB292eurprd_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Agenda for IETF97 TAPS session uploaded https://datatracker.ietf.org/meetin= g/97/agenda/taps/ BR Zahed =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D ANM ZAHEDUZZAMAN SARKER Services, Media and Network Features Eircsson Research Ericsson Laboratoriegr=E4nd 11 97128 Lule=E5, Sweden Phone +46 10 717 37 43 Mobile +46 76 115 37 43 Office +46 76 115 37 43 Fax +46 920 996 21 zaheduzzaman.sarker@ericsson.com www.ericsson.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --_000_AM3PR07MB292BA815C504FA23626E8C29FAD0AM3PR07MB292eurprd_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Agenda for IETF97 TAPS session uploaded https://datatrac= ker.ietf.org/meeting/97/agenda/taps/
 
BR
 
Zahed
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
ANM ZAHEDUZZAMAN SARKER

Services, Media and Network Features
Eircsson Research

Ericsson=
Laboratoriegr=E4nd 11
97128 Lule=E5, Sweden
Phone +46 10 717 37 43
Mobile +46 76 115 37 43
Office +46 76 115 37 43
Fax +46 920 996 21
zaheduzzaman.sarker@ericsson.com
www.ericsson.com<= /u>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D
 
 
 
 --_000_AM3PR07MB292BA815C504FA23626E8C29FAD0AM3PR07MB292eurprd_-- From nobody Mon Oct 31 01:46:57 2016 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 02F40129454; Mon, 31 Oct 2016 01:46:56 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147790361600.32501.7478545182864824365.idtracker@ietfa.amsl.com> Date: Mon, 31 Oct 2016 01:46:56 -0700 Archived-At: Cc: taps@ietf.org Subject: [Taps] I-D Action: draft-ietf-taps-transports-usage-02.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2016 08:46:56 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Services of the IETF. Title : On the Usage of Transport Service Features Provided by IETF Transport Protocols Authors : Michael Welzl Michael Tuexen Naeem Khademi Filename : draft-ietf-taps-transports-usage-02.txt Pages : 39 Date : 2016-10-31 Abstract: This document describes how transport protocols expose services to applications and how an application can configure and use the features of a transport service. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-taps-transports-usage-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transports-usage-02 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 31 10:51:00 2016 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 811AE12996D for ; Mon, 31 Oct 2016 10:50:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 AiczdwndJHTK for ; Mon, 31 Oct 2016 10:50:58 -0700 (PDT) Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCC40127058 for ; Mon, 31 Oct 2016 10:50:57 -0700 (PDT) Received: from [2001:630:40:70e0::107] (port=62521) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1c1GjX-0006zV-KY; Mon, 31 Oct 2016 17:50:56 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Colin Perkins Date: Mon, 31 Oct 2016 17:50:52 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <147790945916.32520.5249086464476907910.idtracker@ietfa.amsl.com> To: taps@ietf.org X-Mailer: Apple Mail (2.3124) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Archived-At: Cc: Stephen McQuistin , Marwan Fayed Subject: [Taps] Fwd: I-D Action: draft-mcquistin-taps-low-latency-services-00.txt X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2016 17:50:59 -0000 Hi TAPS working group, We=E2=80=99ve submitted draft-mcquistin-taps-low-latency-services-00 on = =E2=80=9CTransport Services for Low-Latency Real-Time Applications=E2=80=9D= which might be of interest. This expands on the presentation Stephen = McQuistin gave to the TAPS group in IETF 96 in Berlin, and discusses the = transport service requirements for low-latency real-time applications. This is input to the TAPS process, and to the Post Sockets discussion.=20= Comments appreciated! I=E2=80=99ll also be briefly presenting the work = at IETF 97 in Seoul. Cheers, Colin > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: I-D Action: draft-mcquistin-taps-low-latency-services-00.txt > Date: 31 October 2016 at 10:24:19 GMT > To: > Reply-To: internet-drafts@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. >=20 >=20 > Title : Transport Services for Low-Latency Real-Time = Applications > Authors : Stephen McQuistin > Colin Perkins > Marwan Fayed > Filename : = draft-mcquistin-taps-low-latency-services-00.txt > Pages : 12 > Date : 2016-10-31 >=20 > Abstract: > This document describes the set of transport services required by > low-latency, real-time applications. These services are derived = from > the needs of the applications, rather than from the current > capabilities of the transport layer. An example API, based on the > Berkeley Sockets API, is also provided, alongside examples of how = the > target applications would use the API to access the transport > services described. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-mcquistin-taps-low-latency-services= / >=20 > There's also a htmlized version available at: > = https://tools.ietf.org/html/draft-mcquistin-taps-low-latency-services-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 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --=20 Colin Perkins https://csperkins.org/