Re: [Taps] New Version Notification for draft-welzl-taps-transports-00.txt
Joe Touch <touch@isi.edu> Sat, 24 October 2015 01:15 UTC
Return-Path: <touch@isi.edu>
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 33AE51B2C86 for <taps@ietfa.amsl.com>; Fri, 23 Oct 2015 18:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 D12yi7vqpB5u for <taps@ietfa.amsl.com>; Fri, 23 Oct 2015 18:15:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4ABF1B2C75 for <taps@ietf.org>; Fri, 23 Oct 2015 18:15:41 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t9O1F49u012746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 23 Oct 2015 18:15:08 -0700 (PDT)
To: Brian Trammell <ietf@trammell.ch>, Aaron Falk <aaron.falk@gmail.com>
References: <20150921083533.19273.62189.idtracker@ietfa.amsl.com> <C5DCD4E3-C795-4C21-AA17-D59CA7F02D17@ifi.uio.no> <1D77A9B2-C37B-4ACF-A90D-DB485BC79B28@mjmontpetit.com> <92f091c456879303283af39e26ea14d5.squirrel@erg.abdn.ac.uk> <435C039A-5B01-450B-9223-883194F0B94D@mjmontpetit.com> <BCE21679-705E-4B51-B946-95D80A7EAE1A@ifi.uio.no> <CAD62q9VXwMw3-rU9YaWvyU=1EV6giEm6C8k4Vb+iwTs_oevFWg@mail.gmail.com> <0FB76D15-3904-4D10-8FFD-F0E445E2564C@trammell.ch>
From: Joe Touch <touch@isi.edu>
Message-ID: <562ADB98.6070306@isi.edu>
Date: Fri, 23 Oct 2015 18:15:04 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <0FB76D15-3904-4D10-8FFD-F0E445E2564C@trammell.ch>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/-0I51ngl_M5G1h7sk9EQJwIFj58>
Cc: "<gorry@erg.abdn.ac.uk> Fairhurst" <gorry@erg.abdn.ac.uk>, "taps@ietf.org" <taps@ietf.org>, Marie-Jose Montpetit <marie@mjmontpetit.com>, Michael Welzl <michawe@ifi.uio.no>, touch@isi.edu
Subject: Re: [Taps] New Version Notification for draft-welzl-taps-transports-00.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 24 Oct 2015 01:15:44 -0000
+1 I have read this version in detail (and provided feedback), and think it is a useful document. Joe On 10/5/2015 12:49 PM, Brian Trammell wrote: > In transit, please excuse the brevity. > > Broadly I appreciate the effort to do the decomposition in a less > arbitrary way. I'm not convinced it's actually less arbitrary, but this > is largely irrelevant: it's a *different* way to do the decomposition, > so points of agreement (of which, at least on TCP and SCTP, there are > many) reinforce confidence that we're doing this right. I tend to agree > with Gorry's suggestion on the way forward. > > Cheers, Brian > > Sent from my iPhone > > On 05 Oct 2015, at 11:42, Aaron Falk <aaron.falk@gmail.com > <mailto:aaron.falk@gmail.com>> wrote: > >> Have others read this draft yet? It is clearly aimed at addressing >> charter deliverable #1. Do other folks have an opinion on how well it >> helps the group achieve the goals in our charter? Should we use this >> document in some way? I'm looking for more input from the working >> group on how we should proceed. >> >> My opinion: I am very mindful (& appreciative) of the significant >> effort by Mirja and Brian and the other contributors on >> draft-ietf-taps-transports. The discussion around this doc has been >> very useful for clarifying (to me) how difficult it can be to pull >> useful common abstractions out of the 30+ years of transport >> technologies. Having been down this path for over a year, I >> appreciate the fairly narrow approach draft-welzl-taps-transports and >> think it may be the best chance for TAPS to succeed. >> >> Please share your views. >> >> --aaron >> >> >> On Sat, Sep 26, 2015 at 10:50 AM, Michael Welzl <michawe@ifi.uio.no >> <mailto:michawe@ifi.uio.no>> wrote: >> >> +1 >> >> > On 26. sep. 2015, at 13.28, Marie-Jose Montpetit >> <marie@mjmontpetit.com <mailto:marie@mjmontpetit.com>> wrote: >> > >> > Makes sense. >> > >> >> On Sep 26, 2015, at 3:17 AM, gorry@erg.abdn.ac.uk >> <mailto:gorry@erg.abdn.ac.uk> wrote: >> >> >> >> We seem to have two documents in a space where we started with >> one. These >> >> are different, to me this is OK. Both seem close to charter >> milestone 1. I >> >> don't see much overlap between the contents of the descriptive >> language >> >> and the API-focussed analysis, and any overlap could be eliminated. >> >> >> >> To me, doc 1 (current chartered item) can evolve to provide >> background and >> >> missing documentation for anyone in the IETF, and should compare >> >> transports in a broad way and draw out the idea that they provide >> >> services. This appears to be harder to get right than I for one >> had hoped, >> >> and still has a wide scope. Not a bad thing. I suggest it will >> provide a >> >> reference to stop us rat-holing when people ask what is "this" >> and explain >> >> how all these transports stack-up against one another (good >> pun?). We can >> >> (I suggest) finish this doc in this way. >> >> >> >> I do like the idea of a second document focussed ONLY on the >> Transport API >> >> (I'd call this 1a). In this we can avoid this"discussion of >> what are >> >> transports" and move to a more focussed process in doc 1b, >> Most of >> >> that troublesome descriptive text can go into 1, and ensure we >> keep that >> >> one readable to anyone in the IETF. >> >> >> >> Could I suggest the two docs against the first milestone will >> help us >> >> make progress towards the next milestone faster. (Assuming we >> can keep >> >> the two aligned, which seems quite doable). I can see also how >> the docs >> >> are useful to different people. I'd like to see both mature and >> provide >> >> inputs to move forward. >> >> >> >> Gorry >> >> >> >> >> >>> Interesting and inline to getting transport API(s) >> >>> >> >>> Marie-José Montpetit >> >>> marie@mjmontpetit.com <mailto:marie@mjmontpetit.com> >> >>> mariejo@mit.edu <mailto:mariejo@mit.edu> >> >>> >> >>>> On Sep 21, 2015, at 04:44, Michael Welzl <michawe@ifi.uio.no >> <mailto:michawe@ifi.uio.no>> wrote: >> >>>> >> >>>> Dear all, >> >>>> >> >>>> In my presentation in Prague, I proposed an approach to >> identify the >> >>>> services that transport protocols provide. At the end of the >> ensuing >> >>>> discussion, I said that I (with co-authors) would write a >> draft that >> >>>> explains the proposal by applying the proposed method to TCP >> and SCTP. >> >>>> >> >>>> We just submitted this document - see below; I hope that >> this will lead >> >>>> to some discussion on the list... >> >>>> >> >>>> Cheers, >> >>>> Michael >> >>>> >> >>>> >> >>>>> Begin forwarded message: >> >>>>> >> >>>>> From: <internet-drafts@ietf.org >> <mailto:internet-drafts@ietf.org>> >> >>>>> Subject: New Version Notification for >> >>>>> draft-welzl-taps-transports-00.txt >> >>>>> Date: 21 Sep 2015 10:35:33 CEST >> >>>>> To: Michael Welzl <michawe@ifi.uio.no >> <mailto:michawe@ifi.uio.no>>, Michael Welzl >> >>>>> <michawe@ifi.uio.no <mailto:michawe@ifi.uio.no>>, Michael >> Tuexen <tuexen@fh-muenster.de <mailto:tuexen@fh-muenster.de>>, Naeem >> >>>>> Khademi <naeemk@ifi.uio.no <mailto:naeemk@ifi.uio.no>>, >> Michael Tuexen <tuexen@fh-muenster.de <mailto:tuexen@fh-muenster.de>>, >> >>>>> Naeem Khademi <naeemk@ifi.uio.no <mailto:naeemk@ifi.uio.no>> >> >>>>> Resent-From: <michawe@ifi.uio.no <mailto:michawe@ifi.uio.no>> >> >>>>> >> >>>>> >> >>>>> A new version of I-D, draft-welzl-taps-transports-00.txt >> >>>>> has been successfully submitted by Michael Welzl and posted >> to the >> >>>>> IETF repository. >> >>>>> >> >>>>> Name: draft-welzl-taps-transports >> >>>>> Revision: 00 >> >>>>> Title: An Approach to Identify Services Provided by IETF >> >>>>> Transport Protocols and Congestion Control Mechanisms >> >>>>> Document date: 2015-09-21 >> >>>>> Group: Individual Submission >> >>>>> Pages: 23 >> >>>>> URL: >> >>>>> >> https://www.ietf.org/internet-drafts/draft-welzl-taps-transports-00.txt >> >>>>> Status: >> >>>>> https://datatracker.ietf.org/doc/draft-welzl-taps-transports/ >> >>>>> Htmlized: >> >>>>> https://tools.ietf.org/html/draft-welzl-taps-transports-00 >> >>>>> >> >>>>> >> >>>>> Abstract: >> >>>>> This document describes a method to identify services in >> transport >> >>>>> protocols and congestion control mechanisms. It shows the >> approach >> >>>>> using TCP and SCTP (base protocol) as examples. >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> 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 <http://tools.ietf.org>. >> >>>>> >> >>>>> The IETF Secretariat >> >>>> >> >>>> _______________________________________________ >> >>>> Taps mailing list >> >>>> Taps@ietf.org <mailto:Taps@ietf.org> >> >>>> https://www.ietf.org/mailman/listinfo/taps >> >>> >> >>> _______________________________________________ >> >>> Taps mailing list >> >>> Taps@ietf.org <mailto:Taps@ietf.org> >> >>> https://www.ietf.org/mailman/listinfo/taps >> >>> >> >> >> > >> >> _______________________________________________ >> Taps mailing list >> Taps@ietf.org <mailto:Taps@ietf.org> >> https://www.ietf.org/mailman/listinfo/taps >> >> >> _______________________________________________ >> Taps mailing list >> Taps@ietf.org <mailto:Taps@ietf.org> >> https://www.ietf.org/mailman/listinfo/taps > > > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps >
- [Taps] Fwd: New Version Notification for draft-we… Michael Welzl
- Re: [Taps] Fwd: New Version Notification for draf… MJmontpetit.com
- Re: [Taps] Fwd: New Version Notification for draf… gorry
- Re: [Taps] Fwd: New Version Notification for draf… Marie-Jose Montpetit
- Re: [Taps] New Version Notification for draft-wel… Michael Welzl
- Re: [Taps] New Version Notification for draft-wel… Aaron Falk
- Re: [Taps] New Version Notification for draft-wel… Brian Trammell
- Re: [Taps] New Version Notification for draft-wel… Michael Welzl
- Re: [Taps] New Version Notification for draft-wel… Brian Trammell
- Re: [Taps] New Version Notification for draft-wel… Joe Touch
- Re: [Taps] Fwd: New Version Notification for draf… Karen Elisabeth Egede Nielsen
- Re: [Taps] New Version Notification for draft-wel… Michael Welzl
- Re: [Taps] New Version Notification for draft-wel… Karen Elisabeth Egede Nielsen