From nobody Mon Feb 1 07:13:58 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8449B1ACD2C for ; Mon, 1 Feb 2016 07:13:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 389N4JQZocQp for ; Mon, 1 Feb 2016 07:13:51 -0800 (PST) Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 528551ACD18 for ; Mon, 1 Feb 2016 07:13:51 -0800 (PST) Received: from [172.20.40.18] ([65.216.242.2]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u11FDHNa021995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 1 Feb 2016 07:13:19 -0800 (PST) To: Michael Welzl References: <82BF984C-F2CD-40F2-872D-758207BEC887@ifi.uio.no> <56AD89BB.20906@isi.edu> From: Joe Touch Message-ID: <56AF75CA.50905@isi.edu> Date: Mon, 1 Feb 2016 07:12:10 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-MailScanner-ID: u11FDHNa021995 X-ISI-4-69-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: Cc: "taps@ietf.org" , touch@isi.edu Subject: Re: [Taps] What about draft-moncaster-tsvwg-transport-services ? X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 15:13:56 -0000 On 1/30/2016 11:59 PM, Michael Welzl wrote: ... > The main question on the table is: provided that we'll incorporate > such comments, should this be a product of the WG? It's not clear it's a separate doc. It might be more useful as part of the use case description of other docs, but there's no good reason to force that decision now. IMO, some of this justification clearly needs to be clarified, but I'm not entirely sure where it best belongs. I do disagree that this should happen when we're done; IMO, we need this context to know whether we're all talking about the same kind of problem. In fact, it looks a lot like a problem statement, which more typically *precedes* other WG output. Joe From nobody Thu Feb 4 10:17:02 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACBE1AC3AF for ; Thu, 4 Feb 2016 10:17:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x12WhSJauPko for ; Thu, 4 Feb 2016 10:16:59 -0800 (PST) Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (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 539FD1AC3AB for ; Thu, 4 Feb 2016 10:16:59 -0800 (PST) Received: by mail-yk0-x233.google.com with SMTP id r207so47722607ykd.2 for ; Thu, 04 Feb 2016 10:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JMK2UujQcWehlPFx6MocQPmknpr6Jit0G/vbg7wr95c=; b=Y6FMjPXpeAgR0jND+WqN9VEv/ThK+iMLaSmca3fhkfi4gJKhfV7jFXMh3+XN9wNg+r NsLYqv2EC1dYdES5cKy7+bHE74IiYBxsLIQkAmQoxFTbQLytaBLoeVBKKdx5zJWpDsqP 2TKs/6sQJ5ZBip/OqiZhb2H9soIKmYzDS50VjeQn8kBehfjfF7mONPkADN1LrcZrNipO 13G+W+uOSqJDmSFWvCqdp88IWIBP0xrkfaXSCMG2DkfT4PDu8/r/qfxkjuYfGwgYD3Ix DjUsfj2hkaiUHiZHwmWBt//l6jHPx096wa+0jZmS5ed4KiQ4bWBGqOfdso9pC8BmRWaD 717Q== 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:date :message-id:subject:from:to:content-type; bh=JMK2UujQcWehlPFx6MocQPmknpr6Jit0G/vbg7wr95c=; b=fhVadFOn3mzuAOfaQn2NGCBp42XjhgrtQFo+DDKV7d21viYJ36WG0rA/JXykjPZ4T7 z7BR8Yg2BH2p4qN84kXM8pvNXw+j7+782kyH9FcpVoI3KZpF8KB27ju/hTzMVtLqBfDf cm2UrNknPV+DNvUG9iMDzc0oUi3md+mHxbiVsBQfcH9n63zlrWs2+Z/dfCSgenAyyR40 nNpsWFeEVjaWDtULlVG9Lk0i9X8Ak9noNbNOr92e+M2YEQ0z7dYCcwgGMRwGRHMfCuZe v5SqShWeejLrJkwZ1otYsvdkM+HJn4dkbxUWObAoq3EvMCvNHp/xEpjEuPwetdZTUEnf MPJw== X-Gm-Message-State: AG10YOTGuctd6/wiNeRc2eUWGYkHP7kiKp0w9iWgahvp26LqfGHcIhwTCoL66OAME5QCxrOtFQMSsldBSBZ1/w== MIME-Version: 1.0 X-Received: by 10.13.197.198 with SMTP id h189mr4518123ywd.254.1454609818622; Thu, 04 Feb 2016 10:16:58 -0800 (PST) Received: by 10.37.83.2 with HTTP; Thu, 4 Feb 2016 10:16:58 -0800 (PST) In-Reply-To: References: Date: Thu, 4 Feb 2016 13:16:58 -0500 Message-ID: From: Aaron Falk To: "taps@ietf.org" Content-Type: multipart/alternative; boundary=001a114e488286a3be052af5bd71 Archived-At: Subject: Re: [Taps] WGLC2 for draft-ietf-taps-transports-09.txt -- ending Feb 12, 2016 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2016 18:17:02 -0000 --001a114e488286a3be052af5bd71 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reminder that we're re-running WGLC for doc1. If you don't have time for a full review, please look at the diffs (linked below). --aaron On Fri, Jan 29, 2016 at 11:18 AM, Aaron Falk wrote: > As Brian highlights below, doc 1 has had a pretty thorough scrub and tidy > while incorporating last call comments. I think the number of changes is > sufficient that the group should take another look. Please send comments= , > pro or con, to the list. > > --aaron > > > ---------- Forwarded message ---------- > From: Brian Trammell > Date: Fri, Jan 29, 2016 at 9:39 AM > Subject: Fwd: New Version Notification for > draft-ietf-taps-transports-09.txt > To: Aaron Falk > Cc: Mirja K=C3=BChlewind , Gorry Fairhur= st < > gorry@erg.abdn.ac.uk> > > > Hi, Aaron, > > We went over the document over the past week addressing WGLC comments, an= d > also spent a good deal of time with a fine-tooth comb double-checking > editorial flow as well as the alignment of the per-protocol features with > those in the definitive feature list in section 5. As you can see from th= e > diff, the changes here (especially with respect to things we found that > were missing from the list in section 5) are not all entirely editorial, = so > we may need to run a second WGLC on this. Chair's prerogative, of course, > but I wanted to make sure you knew we weren't trying to sneak one past yo= u > here. :) If you believe one is not necessary, then this is very nearly > ready to go. > > In any case, we'd also like to slightly rearrange the transport protocol > sections in order to eliminate forward references, but we'd want to do th= at > after any second WGLC comments, since it'll make the diffs hard to follow= . > > Thanks, cheers, > > Brian > > > > Begin forwarded message: > > > > From: internet-drafts@ietf.org > > Subject: New Version Notification for draft-ietf-taps-transports-09.txt > > Date: 29 Jan 2016 15:32:13 CET > > To: "Mirja Kuehlewind" , "Gorry > Fairhurst" , "Brian Trammell" , > "Godred Fairhurst" > > > > > > A new version of I-D, draft-ietf-taps-transports-09.txt > > has been successfully submitted by Brian Trammell and posted to the > > IETF repository. > > > > Name: draft-ietf-taps-transports > > Revision: 09 > > Title: Services provided by IETF transport protocols and > congestion control mechanisms > > Document date: 2016-01-28 > > Group: taps > > Pages: 54 > > URL: > https://www.ietf.org/internet-drafts/draft-ietf-taps-transports-09.txt > > Status: > https://datatracker.ietf.org/doc/draft-ietf-taps-transports/ > > Htmlized: > https://tools.ietf.org/html/draft-ietf-taps-transports-09 > > Diff: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transports-09 > > > > 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 used as a pseudotransport. > > > > > > > > > > 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 > > > > > --001a114e488286a3be052af5bd71 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Reminder that we're re-running WGLC for doc1.=C2=A0 If= you don't have time for a full review, please look at the diffs (linke= d below).

--aaron
=
On Fri, Jan 29, 2016 at 11:18 AM, Aaron Falk= <aaron.falk@gmail.com> wrote:
As Brian highlights below, doc 1 has had a pr= etty thorough scrub and tidy while incorporating last call comments.=C2=A0 = I think the number of changes is sufficient that the group should take anot= her look.=C2=A0 Please send comments, pro or con, to the list.
--aaron


---= ------- Forwarded message ----------
From: Brian Trammell <ietf@trammell.ch>
Date: Fri, Jan 29, = 2016 at 9:39 AM
Subject: Fwd: New Version Notification for draft-ietf-ta= ps-transports-09.txt
To: Aaron Falk <aaron.falk@gmail.com>
Cc: Mirja K=C3=BC= hlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Gorry Fairhurst <gorry@erg.abdn.ac.uk= >


Hi, Aaron,

We went over the document over the past week addressing WGLC comments, and = also spent a good deal of time with a fine-tooth comb double-checking edito= rial flow as well as the alignment of the per-protocol features with those = in the definitive feature list in section 5. As you can see from the diff, = the changes here (especially with respect to things we found that were miss= ing from the list in section 5) are not all entirely editorial, so we may n= eed to run a second WGLC on this. Chair's prerogative, of course, but I= wanted to make sure you knew we weren't trying to sneak one past you h= ere. :) If you believe one is not necessary, then this is very nearly ready= to go.

In any case, we'd also like to slightly rearrange the transport protoco= l sections in order to eliminate forward references, but we'd want to d= o that after any second WGLC comments, since it'll make the diffs hard = to follow.

Thanks, cheers,

Brian


> Begin forwarded message:
>
> From: in= ternet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-taps-transports-09.tx= t
> Date: 29 Jan 2016 15:32:13 CET
> To: "Mirja Kuehlewind" <mirja.kuehlewind@tik.ee.ethz.ch>= , "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>, "Brian Trammell" &= lt;ietf@trammell.ch>, "Godred Fairhurst" <gorry@erg.abdn.ac.uk>
>
>
> A new version of I-D, draft-ietf-taps-transports-09.txt
> has been successfully submitted by Brian Trammell and posted to the > IETF repository.
>
> Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-taps-transports
> Revision:=C2=A0 =C2=A0 =C2=A009
> Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Services= provided by IETF transport protocols and congestion control mechanisms
> Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2016-01-28
> Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 taps
> Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 54
> URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-ietf-taps-t= ransports-09.txt
> Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-ietf-taps-transports/
> Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0ht= tps://tools.ietf.org/html/draft-ietf-taps-transports-09
> Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transpo= rts-09
>
> Abstract:
>=C2=A0 =C2=A0This document describes, surveys, classifies and compares = the
>=C2=A0 =C2=A0protocol mechanisms provided by existing IETF protocols, a= s
>=C2=A0 =C2=A0background for determining a common set of transport servi= ces.=C2=A0 It
>=C2=A0 =C2=A0examines the Transmission Control Protocol (TCP), Multipat= h TCP, the
>=C2=A0 =C2=A0Stream Control Transmission Protocol (SCTP), the User Data= gram
>=C2=A0 =C2=A0Protocol (UDP), UDP-Lite, the Datagram Congestion Control = Protocol
>=C2=A0 =C2=A0(DCCP), the Internet Control Message Protocol (ICMP), the = Realtime
>=C2=A0 =C2=A0Transport Protocol (RTP), File Delivery over Unidirectiona= l
>=C2=A0 =C2=A0Transport/Asynchronous Layered Coding Reliable Multicast (= FLUTE/ALC),
>=C2=A0 =C2=A0and NACK-Oriented Reliable Multicast (NORM), Transport Lay= er Security
>=C2=A0 =C2=A0(TLS), Datagram TLS (DTLS), and the Hypertext Transport Pr= otocol
>=C2=A0 =C2=A0(HTTP) when used as a pseudotransport.
>
>
>
>
> 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. >
> The IETF Secretariat
>



--001a114e488286a3be052af5bd71-- From nobody Tue Feb 23 05:05:11 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080631AD2EE for ; Tue, 23 Feb 2016 05:05:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.207 X-Spam-Level: X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZTqi_5wXlOB for ; Tue, 23 Feb 2016 05:05:08 -0800 (PST) Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 047031AD244 for ; Tue, 23 Feb 2016 05:05:08 -0800 (PST) Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:fc51:d39e:349f:fdd3]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C20F61B0010E; Tue, 23 Feb 2016 13:16:22 +0000 (GMT) To: "taps@ietf.org" From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. Message-ID: <56CC5902.7050103@erg.abdn.ac.uk> Date: Tue, 23 Feb 2016 13:05:06 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [Taps] new TAPS ID: draft-fairhurst-taps-transports-usage-udp-00 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 13:05:10 -0000 We have just posted a new ID: Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp/ This document provides input on UDP and UDP-Lite usage for the TAPS WG. In putting this together, we tried to stick with the rules of the WG usage draft, although the documentation for UDP in RFC series was more than a little erratic and scattered. I'd like to request time to present this at the BA IETF meeting, and we intend there to propose this as a formal contribution to develop the datagram part of draft-ietf-taps-transports-usage. We would very much appreciate it if people who understand UDP could read and offer any comments. If there are some comments we would be happy to make further updates before the next meeting. best wishes, Gorry & Tom From nobody Tue Feb 23 05:32:13 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3071ACE42 for ; Tue, 23 Feb 2016 05:32:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.906 X-Spam-Level: X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9aD4f12y4G_0 for ; Tue, 23 Feb 2016 05:31:58 -0800 (PST) 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 1A6AE1B2C6C for ; Tue, 23 Feb 2016 05:31:56 -0800 (PST) Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from ) id 1aYD4D-00040m-GK; Tue, 23 Feb 2016 14:31:53 +0100 Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx3.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.80) (envelope-from ) id 1aYD4D-0002bm-7b; Tue, 23 Feb 2016 14:31:53 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Michael Welzl In-Reply-To: <56CC5902.7050103@erg.abdn.ac.uk> Date: Tue, 23 Feb 2016 14:31:53 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <44846D71-5D0D-445B-BD6B-5ED876DE219E@ifi.uio.no> References: <56CC5902.7050103@erg.abdn.ac.uk> To: " Fairhurst" X-Mailer: Apple Mail (2.2104) X-UiO-SPF-Received: X-UiO-Ratelimit-Test: rcpts/h 5 msgs/h 3 sum rcpts/h 10 sum msgs/h 6 total rcpts 38517 max rcpts/h 54 ratelimit 0 X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.049, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 9AC0C884CA48C7FCC3EF9DA067C374027C543F8D X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -59 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 9195 max/h 17 blacklist 0 greylist 0 ratelimit 0 Archived-At: Cc: "taps@ietf.org" Subject: Re: [Taps] new TAPS ID: draft-fairhurst-taps-transports-usage-udp-00 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 13:32:04 -0000 Hi, I'd also like to request to present draft-ietf-taps-transports-usage-00 = or maybe an -01 version if we manage to do one by the meeting (which I = doubt). This will just be a quick update. As for the UDP and UDP-Lite draft below, it does look to me like a very = welcome addition to draft-ietf-taps-transports-usage indeed! Cheers, Michael > On 23 Feb 2016, at 14:05, Gorry Fairhurst = wrote: >=20 > We have just posted a new ID: >=20 > Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- = Lite) Transport Protocols >=20 > = https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp= / >=20 > This document provides input on UDP and UDP-Lite usage for the TAPS = WG. In putting this together, we tried to stick with the rules of the WG = usage draft, although the documentation for UDP in RFC series was more = than a little erratic and scattered. I'd like to request time to present = this at the BA IETF meeting, and we intend there to propose this as a = formal contribution to develop the datagram part of = draft-ietf-taps-transports-usage. >=20 > We would very much appreciate it if people who understand UDP could = read and offer any comments. If there are some comments we would be = happy to make further updates before the next meeting. >=20 > best wishes, >=20 > Gorry & Tom >=20 > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps From nobody Thu Feb 25 12:02:47 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1218D1B33F1 for ; Thu, 25 Feb 2016 12:02:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkbwTThjbnDR for ; Thu, 25 Feb 2016 12:02:43 -0800 (PST) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 C22941B33D7 for ; Thu, 25 Feb 2016 12:02:17 -0800 (PST) Received: by mail-yw0-x232.google.com with SMTP id e63so51759752ywc.3 for ; Thu, 25 Feb 2016 12:02:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0BsRw3NOjnF63NzgHiCp7lhgtWNx98ukGK/0E3gF0JE=; b=hcjKpxXGNFE3ERoqthbXVKghYVR2mOc5y6e5WvMpgF+F98YwnQyuEBNVI6LvfZhLf2 vQdIxlNQxWX0YE8xmrwppS7h2/UaNRlr/RY7AjOJOAbFBuIuwgJiBECMzyfZQp+RGxgl 1CRrkQ88m4VKFdZ22P8sXrYz7Wj9g5znviq39CaAsYKqQlmHZksuco1/Lr0n4EV5uW6e E+BlhjWiX49edAtunBlHtr5FoIVs/40esgWOP1pat+fV6SfgZ0k4C+QF3Lg4VHQm/Urd pSlr82CLJmIx2S1XtWUDVOjH/6g6lqIeu5ry/5ZI/dI+7bdOk3XHL/of6IVWwJy62F9j djDA== 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:date :message-id:subject:from:to:content-type; bh=0BsRw3NOjnF63NzgHiCp7lhgtWNx98ukGK/0E3gF0JE=; b=DVHMfooHdByFDWTC1MrysCLvmJt8wNdixbUgsFLlFLxZXlZ3Y0oG52pvDSaSnct1PG iCIf4I5tQpHRpxngUYOzwB3GNxXo7HKRhzgoFpXlokPR9iFeMcnjAyD//8iuem2N9wGs OmAUEkUpMK9XySfYw403xrSz64VetSWEs1nVn8UgH6r4TGUaiIVfFh0vQQladtXsb3qX sdG1Al69BcPAhUWyWzOctWw0hInaRpm/UgoqXhmtkGNdodpMZBlIJTCfcmcpasSYci+a Ahl3TDMzAJ63ynWtO/4cwXNQKlGr77m3Unn0xtlUcDAE65bYSwt+4qSc+fsUv5ZcENwX cLxg== X-Gm-Message-State: AG10YOT/TQ1X+Feqzb1Fy414IDex6DffCMcp+ROTYoCwDw74mO2clgUMkuRTK1Vm/qYsfEBZ9Vn46HYwV+RTKw== MIME-Version: 1.0 X-Received: by 10.129.95.66 with SMTP id t63mr23414500ywb.61.1456430537020; Thu, 25 Feb 2016 12:02:17 -0800 (PST) Received: by 10.37.70.198 with HTTP; Thu, 25 Feb 2016 12:02:16 -0800 (PST) In-Reply-To: References: Date: Thu, 25 Feb 2016 15:02:16 -0500 Message-ID: From: Aaron Falk To: "taps@ietf.org" Content-Type: multipart/alternative; boundary=001a1147f5a2cc9cf2052c9da843 Archived-At: Subject: Re: [Taps] WGLC2 for draft-ietf-taps-transports-09.txt -- ending Feb 12, 2016 X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2016 20:02:46 -0000 --001a1147f5a2cc9cf2052c9da843 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I saw no comments on the 2nd last call. IMO, this is a minor change to the document. Are there any objections to moving forward with publication? I am open to requests for additional delay. --aaron On Fri, Jan 29, 2016 at 11:18 AM, Aaron Falk wrote: > As Brian highlights below, doc 1 has had a pretty thorough scrub and tidy > while incorporating last call comments. I think the number of changes is > sufficient that the group should take another look. Please send comments= , > pro or con, to the list. > > --aaron > > > ---------- Forwarded message ---------- > From: Brian Trammell > Date: Fri, Jan 29, 2016 at 9:39 AM > Subject: Fwd: New Version Notification for > draft-ietf-taps-transports-09.txt > To: Aaron Falk > Cc: Mirja K=C3=BChlewind , Gorry Fairhur= st < > gorry@erg.abdn.ac.uk> > > > Hi, Aaron, > > We went over the document over the past week addressing WGLC comments, an= d > also spent a good deal of time with a fine-tooth comb double-checking > editorial flow as well as the alignment of the per-protocol features with > those in the definitive feature list in section 5. As you can see from th= e > diff, the changes here (especially with respect to things we found that > were missing from the list in section 5) are not all entirely editorial, = so > we may need to run a second WGLC on this. Chair's prerogative, of course, > but I wanted to make sure you knew we weren't trying to sneak one past yo= u > here. :) If you believe one is not necessary, then this is very nearly > ready to go. > > In any case, we'd also like to slightly rearrange the transport protocol > sections in order to eliminate forward references, but we'd want to do th= at > after any second WGLC comments, since it'll make the diffs hard to follow= . > > Thanks, cheers, > > Brian > > > > Begin forwarded message: > > > > From: internet-drafts@ietf.org > > Subject: New Version Notification for draft-ietf-taps-transports-09.txt > > Date: 29 Jan 2016 15:32:13 CET > > To: "Mirja Kuehlewind" , "Gorry > Fairhurst" , "Brian Trammell" , > "Godred Fairhurst" > > > > > > A new version of I-D, draft-ietf-taps-transports-09.txt > > has been successfully submitted by Brian Trammell and posted to the > > IETF repository. > > > > Name: draft-ietf-taps-transports > > Revision: 09 > > Title: Services provided by IETF transport protocols and > congestion control mechanisms > > Document date: 2016-01-28 > > Group: taps > > Pages: 54 > > URL: > https://www.ietf.org/internet-drafts/draft-ietf-taps-transports-09.txt > > Status: > https://datatracker.ietf.org/doc/draft-ietf-taps-transports/ > > Htmlized: > https://tools.ietf.org/html/draft-ietf-taps-transports-09 > > Diff: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transports-09 > > > > 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 used as a pseudotransport. > > > > > > > > > > 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 > > > > > --001a1147f5a2cc9cf2052c9da843 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I saw no comments on the 2nd last call.=C2=A0 IMO, this is= a minor change to the document.=C2=A0 Are there any objections to moving f= orward with publication?=C2=A0 I am open to requests for additional delay.<= div>
--aaron

On Fri, Jan 29, 2016 at 11:18 AM, Aaron Falk <aaro= n.falk@gmail.com> wrote:
As Brian highlights below, doc 1 has had a pretty thoro= ugh scrub and tidy while incorporating last call comments.=C2=A0 I think th= e number of changes is sufficient that the group should take another look.= =C2=A0 Please send comments, pro or con, to the list.

<= div>--aaron


---------- F= orwarded message ----------
From: Brian Tr= ammell <ietf@trammell.ch>
Date: Fri, Jan 29, 2016 at 9= :39 AM
Subject: Fwd: New Version Notification for draft-ietf-taps-transp= orts-09.txt
To: Aaron Falk <aaron.falk@gmail.com>
Cc: Mirja K=C3=BChlewind &= lt;mir= ja.kuehlewind@tik.ee.ethz.ch>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>

Hi, Aaron,

We went over the document over the past week addressing WGLC comments, and = also spent a good deal of time with a fine-tooth comb double-checking edito= rial flow as well as the alignment of the per-protocol features with those = in the definitive feature list in section 5. As you can see from the diff, = the changes here (especially with respect to things we found that were miss= ing from the list in section 5) are not all entirely editorial, so we may n= eed to run a second WGLC on this. Chair's prerogative, of course, but I= wanted to make sure you knew we weren't trying to sneak one past you h= ere. :) If you believe one is not necessary, then this is very nearly ready= to go.

In any case, we'd also like to slightly rearrange the transport protoco= l sections in order to eliminate forward references, but we'd want to d= o that after any second WGLC comments, since it'll make the diffs hard = to follow.

Thanks, cheers,

Brian


> Begin forwarded message:
>
> From: in= ternet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-taps-transports-09.tx= t
> Date: 29 Jan 2016 15:32:13 CET
> To: "Mirja Kuehlewind" <mirja.kuehlewind@tik.ee.ethz.ch>= , "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>, "Brian Trammell" &= lt;ietf@trammell.ch>, "Godred Fairhurst" <gorry@erg.abdn.ac.uk>
>
>
> A new version of I-D, draft-ietf-taps-transports-09.txt
> has been successfully submitted by Brian Trammell and posted to the > IETF repository.
>
> Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-taps-transports
> Revision:=C2=A0 =C2=A0 =C2=A009
> Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Services= provided by IETF transport protocols and congestion control mechanisms
> Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2016-01-28
> Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 taps
> Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 54
> URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-ietf-taps-t= ransports-09.txt
> Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-ietf-taps-transports/
> Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0ht= tps://tools.ietf.org/html/draft-ietf-taps-transports-09
> Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-taps-transpo= rts-09
>
> Abstract:
>=C2=A0 =C2=A0This document describes, surveys, classifies and compares = the
>=C2=A0 =C2=A0protocol mechanisms provided by existing IETF protocols, a= s
>=C2=A0 =C2=A0background for determining a common set of transport servi= ces.=C2=A0 It
>=C2=A0 =C2=A0examines the Transmission Control Protocol (TCP), Multipat= h TCP, the
>=C2=A0 =C2=A0Stream Control Transmission Protocol (SCTP), the User Data= gram
>=C2=A0 =C2=A0Protocol (UDP), UDP-Lite, the Datagram Congestion Control = Protocol
>=C2=A0 =C2=A0(DCCP), the Internet Control Message Protocol (ICMP), the = Realtime
>=C2=A0 =C2=A0Transport Protocol (RTP), File Delivery over Unidirectiona= l
>=C2=A0 =C2=A0Transport/Asynchronous Layered Coding Reliable Multicast (= FLUTE/ALC),
>=C2=A0 =C2=A0and NACK-Oriented Reliable Multicast (NORM), Transport Lay= er Security
>=C2=A0 =C2=A0(TLS), Datagram TLS (DTLS), and the Hypertext Transport Pr= otocol
>=C2=A0 =C2=A0(HTTP) when used as a pseudotransport.
>
>
>
>
> 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. >
> The IETF Secretariat
>



--001a1147f5a2cc9cf2052c9da843-- From nobody Fri Feb 26 06:48:14 2016 Return-Path: X-Original-To: taps@ietfa.amsl.com Delivered-To: taps@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6014A1B2D4F for ; Fri, 26 Feb 2016 06:48:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IlZJu5ulXFbZ for ; Fri, 26 Feb 2016 06:48:10 -0800 (PST) Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (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 B84D01B2D4E for ; Fri, 26 Feb 2016 06:48:10 -0800 (PST) Received: by mail-yk0-x235.google.com with SMTP id z7so36321690yka.3 for ; Fri, 26 Feb 2016 06:48:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=I82phY/k2Azj0/MIq4tJT0EjrWDjvSJhLbqBsQBBAFk=; b=qYcxhn76F00CI9giJXmTeglY1BelmKqo0hLDmkfDhKHUuQFMC/ojqaVScghnh8hI2E B3QX2/knSv6RwOkS2Y8jrQhbd3beGGQL5u1DZ1cMmoqvFnuFLZgmE7pZp+G4dnoTaCFK UN3Uc7xsLOu9qzVv9EIbLbgeCw5diZzBVVDVsRmeERFVyAjm8OvMXCWZijuYLTchQEuN TTMZeyQm6Af1eH4vrdt1pFpLOx4oOL2SopPIRwY2Y6ErDTK614xZvIPTPemXAa2ppKr0 CM33bpZS5oBEsWeLacUWfz9AbgOieCNujerWmRBPA5Tb8nK3haYDVeQVZSaW98e6DLua XuqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=I82phY/k2Azj0/MIq4tJT0EjrWDjvSJhLbqBsQBBAFk=; b=Lo7GaFJTCDZ2gXHxWEKJ9hHaBeeN6EwYIheAdSUtcT+czk35lDprs0A463T3nnTpdx 5bkoO5vZEX/R7Guk+Nh/25SmNtu4gClzfRWk7yg0/32edOoK3+w6lzx/4YcbB8ESPIRo M7Ns2eEsNgumP02e6wE6AM2YCoZHG8KB7wV1lZbRKeA8qXSKoxtBUGH7qoe+IfHrXVjh J+krNW0DJ7y/fthH1Qc2E8rhgIpjult0GRkAgtsyIJK1LkTQh9s7zO+Mr9B49Kcy8nHw ReaZD4T+YN0FQqcJQT2l/1KSLzNY39GpUbeZvLe/vIYnTUE7mkA9sW0LgnwQCs3Li51r OZFQ== X-Gm-Message-State: AD7BkJKIMN4pwA6hmKTHDVRdWXyVwJIzdAGN0dnR3CBL0kyrkNm7Db20E6DS7tvhK05JqjcyHnZhti8k+YAnow== MIME-Version: 1.0 X-Received: by 10.37.102.194 with SMTP id a185mr1060564ybc.96.1456498090033; Fri, 26 Feb 2016 06:48:10 -0800 (PST) Received: by 10.37.70.198 with HTTP; Fri, 26 Feb 2016 06:48:09 -0800 (PST) Date: Fri, 26 Feb 2016 09:48:09 -0500 Message-ID: From: Aaron Falk To: "taps@ietf.org" Content-Type: multipart/alternative; boundary=001a1147207e45caf3052cad63e8 Archived-At: Subject: [Taps] agenda planning X-BeenThere: taps@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussions on Transport Services List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2016 14:48:12 -0000 --001a1147207e45caf3052cad63e8 Content-Type: text/plain; charset=UTF-8 Proposed topics: - Proposed adoption of draft-fairhurst-taps-transports-usage-udp/ - Gorry et al - Draft update of draft-ietf-taps-transports-usage-00 - Michael et al Other topics? Are we ready to start talking about doc2 yet? 2) Specify the subset of those Transport Services, as identified > > in item 1, that end systems supporting TAPS will provide, and > > give guidance on choosing among available mechanisms and > > protocols. Note that not all the capabilities of IETF Transport > > protocols need to be exposed as Transport Services. > > --aaron --001a1147207e45caf3052cad63e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Proposed topics:

<= div>Other topics?=C2=A0 Are we ready to st= art talking about doc2 yet?

2) Specify the subset of those Transport Services, as identifie= d=C2=A0
=C2=A0 =C2=A0in item 1, that end systems supporting TAPS will provide, an= d=C2=A0
=C2=A0 =C2=A0give guidance on choosing among available mechanisms and=C2= =A0
= =C2=A0 =C2=A0protocols.=C2=A0 Note that not all the capabilities of IETF Tr= ansport=C2=A0
=C2=A0 =C2=A0protocols need to be exposed as Transport Services.

--aaron=C2=A0
--001a1147207e45caf3052cad63e8--