Re: [Taps] TCP components

Joe Touch <touch@isi.edu> Thu, 18 June 2015 22:52 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 EEDC01A9030 for <taps@ietfa.amsl.com>; Thu, 18 Jun 2015 15:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level:
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lq2NsLU3hrxM for <taps@ietfa.amsl.com>; Thu, 18 Jun 2015 15:52:09 -0700 (PDT)
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 554FB1A8A9D for <taps@ietf.org>; Thu, 18 Jun 2015 15:52:09 -0700 (PDT)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id t5IMpOaU015294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 18 Jun 2015 15:51:25 -0700 (PDT)
To: Michael Welzl <michawe@ifi.uio.no>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
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>
From: Joe Touch <touch@isi.edu>
Message-ID: <55834B6C.5020000@isi.edu>
Date: Thu, 18 Jun 2015 15:51:24 -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: <E788A309-869F-49E0-832D-429E0DA0E2F9@ifi.uio.no>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: t5IMpOaU015294
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/mMIkiJzYGxAh8P847la_AEjRE8Y>
Cc: Brian Trammell <ietf@trammell.ch>, "taps@ietf.org" <taps@ietf.org>, 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: Thu, 18 Jun 2015 22:52:10 -0000

+1

On 6/18/2015 9:44 AM, Michael Welzl wrote:
> *My*  goal is, and has always been, to provide a simpler, general API
> that is protocol independent. Note that this is not only for
> simplicity for ease of use BUT also for the sake of being able to
> automatize. After all the major goal is to remove the strict binding
> between applications and a specific protocol choice.
>
> To be able to do this (documents 2 and 3), we first need a list of
> the existing services - our toolbox, if you wish (document 1).
> Figuring out what's missing / wrong about today's APIs (except that
> they are bound to a specific protocol) has never been*my*  major
> intention, and I certainly don't see that as the goal of this
> document. I'd be surprised if that's what the charter suggests?! But
> of course my opinion is only what it is, the charter reflects the
> consensus...