Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt

Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Mon, 10 October 2016 09:10 UTC

Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
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 <taps@ietfa.amsl.com>; 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 <taps@ietfa.amsl.com>; 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 <taps@ietf.org>; 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: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
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> <D0AEB91E-8E9F-4089-B599-9A8428A0642C@ifi.uio.no> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com>
To: Aaron Falk <aaron.falk@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/laAkY9YJIBA2H_7SjnJx0yM6AxY>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Michael Welzl <michawe@ifi.uio.no>, 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 <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Oct 2016 09:10:32 -0000

Hi all,

quick question: what’s 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 <aaron.falk@gmail.com>:
> 
> IMO, this is obviously in scope for TAPS and a useful contribution.  I’d like to hear any dissenting opinions about adopting this doc as a wg item.
> 
> —aaron
> 
> 
>> On Oct 6, 2016, at 3:46 AM, Michael Welzl <michawe@ifi.uio.no> wrote:
>> 
>> hi,
>> 
>> 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.
>> 
>> about adopting this separate document, it makes sense to me
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 6. okt. 2016, at 10.22, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>>> 
>>> 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
>>> 
>>> _______________________________________________
>>> Taps mailing list
>>> Taps@ietf.org
>>> https://www.ietf.org/mailman/listinfo/taps
>> 
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps