IETF Logo Mail Archive

Re: [Taps] TCP components

Joe Touch <touch@isi.edu> Sat, 20 June 2015 17:33 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 ECFD51A89C4 for <taps@ietfa.amsl.com>; Sat, 20 Jun 2015 10:33:37 -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 JnWLMHJBCsNP for <taps@ietfa.amsl.com>; Sat, 20 Jun 2015 10:33:35 -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 DDF1B1A89B5 for <taps@ietf.org>; Sat, 20 Jun 2015 10:33:34 -0700 (PDT)
Received: from [192.168.1.10] (pool-71-108-123-251.lsanca.dsl-w.verizon.net [71.108.123.251]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t5KHWcvc005388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 20 Jun 2015 10:32:39 -0700 (PDT)
To: Michael Welzl <michawe@ifi.uio.no>
References: <5579768E.5060402@tik.ee.ethz.ch> <A3EF3A19-0E37-42E6-8D17-94164EBA7FDD@ifi.uio.no> <154FD7B7-9A01-43EC-927D-B9D71F1BC38D@tik.ee.ethz.ch> <57DC7DAB-7054-41BE-8515-626353782BBC@ifi.uio.no> <5581B81B.4090500@isi.edu> <725D4141-40AB-4E30-9409-96813C80905B@tik.ee.ethz.ch> <33CA72C2-D0EC-43A1-B766-D34F3636961B@ifi.uio.no> <23AACB56-2044-4E89-930B-C7D501AD7184@tik.ee.ethz.ch> <E788A309-869F-49E0-832D-429E0DA0E2F9@ifi.uio.no> <DA987915-C664-40D9-B527-9A686BA01013@tik.ee.ethz.ch> <C2962821-4DF2-44CD-BBEF-49520B5BA4D3@ifi.uio.no> <5584400C.5080406@isi.edu> <CAJ+dxNCN3Pj4x707hr50V-GZHJvQM_S8cx1g3NTZne086T3sOQ@mail.gmail.com> <5584937F.2030408@isi.edu> <CAJ+dxND-KRA_=cfe6iPG6oWD+M_YegY7MBUqnSutEKdXrjpoag@mail.gmail.com> <55849DC5.7040600@isi.edu> <D534A8F8-A4AB-41DC-83E9-C65A6C7BF902@ifi.uio.no>
From: Joe Touch <touch@isi.edu>
Message-ID: <5585A3B5.5030702@isi.edu>
Date: Sat, 20 Jun 2015 10:32:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <D534A8F8-A4AB-41DC-83E9-C65A6C7BF902@ifi.uio.no>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
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/wORSb_9kTLC_WMh_xAOn8t-iiDA>
Cc: Mohamed Oulmahdi <m.oulmahdi@gmail.com>, "taps@ietf.org" <taps@ietf.org>, Brian Trammell <ietf@trammell.ch>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, touch@isi.edu
Subject: Re: [Taps] TCP components
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: <http://www.ietf.org/mail-archive/web/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, 20 Jun 2015 17:33:38 -0000

Michael,

On 6/20/2015 1:35 AM, Michael Welzl wrote:
>
>> On 20. jun. 2015, at 00.55, Joe Touch <touch@isi.edu> wrote:
>>
>> On 6/19/2015 3:42 PM, Mohamed Oulmahdi wrote:
...
>> Let's put it this way:
>>
>> 	- if the goal of TAPS is to unify existing APIs,
>> 	then those APIs need to be summarized together in one place
>>
>>
>> 	- if TAPS is indeed focused solely on an alternate API,
>> 	then it should NOT try to 'restate' the existing TCP API
>> 	in a TAPS doc
>>
>> "Do, or do not; there is no try."
>> 	- Yoda
>
> TAPS is focused on an alternate API that it's based on existing
> transports. As a way of analyzing existing transports and creating
> a foundation for this API, document #1 is written. I think this
> discussion is about the approach taken to write document #1.
>
> So now I wonder what you're complaining about,

I'm trying to get Mohamed (and perhaps others) on the same page as you 
and I.

Joe

v2.23.0 | Report a Bug | By Email