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

Michael Welzl <michawe@ifi.uio.no> Thu, 06 October 2016 07:47 UTC

Return-Path: <michawe@ifi.uio.no>
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 <taps@ietfa.amsl.com>; 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 <taps@ietfa.amsl.com>; 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 <taps@ietf.org>; 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 <michawe@ifi.uio.no>) 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 <michawe@ifi.uio.no>) 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 <michawe@ifi.uio.no>
X-Mailer: iPhone Mail (13G36)
In-Reply-To: <57F5FBCE.6080609@erg.abdn.ac.uk>
Date: Thu, 06 Oct 2016 10:46:56 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0AEB91E-8E9F-4089-B599-9A8428A0642C@ifi.uio.no>
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: <https://mailarchive.ietf.org/arch/msg/taps/Li0mAw1Y6EWOg-Trm_GIi-z4tZU>
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 <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 07:47:05 -0000

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