Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt

Brian Trammell <ietf@trammell.ch> Thu, 16 July 2015 13:04 UTC

Return-Path: <ietf@trammell.ch>
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 ACC691B3ABB for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 06:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.312
X-Spam-Level:
X-Spam-Status: No, score=-1.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_45=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 KnrTuSDuIRCC for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 06:04:44 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id CD13F1B3ABA for <taps@ietf.org>; Thu, 16 Jul 2015 06:04:38 -0700 (PDT)
Received: from [IPv6:2001:67c:10ec:2a49:8000::b9] (unknown [IPv6:2001:67c:10ec:2a49:8000::b9]) by trammell.ch (Postfix) with ESMTPSA id 67DD31A03F3; Thu, 16 Jul 2015 15:04:37 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_82AA79B2-6FCD-4BCC-A318-677D9AC8B502"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <A6A77B18-C8F4-4C87-8493-8FF11AC98AA1@ifi.uio.no>
Date: Thu, 16 Jul 2015 15:04:36 +0200
Message-Id: <032C97CD-A8D3-4553-9DD1-B17E2295AC43@trammell.ch>
References: <5b2e19f286a3eaf18d2ccf7da39abbbf@mail.gmail.com> <A6A77B18-C8F4-4C87-8493-8FF11AC98AA1@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/2VmydQ11-Edq_WIlCSG68DLREoI>
Cc: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, "taps@ietf.org" <taps@ietf.org>, Stein Gjessing <steing@ifi.uio.no>
Subject: Re: [Taps] Comments on draft-gjessing-taps-minset-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: Thu, 16 Jul 2015 13:04:45 -0000

hi Michael,

...inline...

> On 16 Jul 2015, at 13:23, Michael Welzl <michawe@ifi.uio.no> wrote:

<snip>

>> Ideally, I think, then one would use a common term for Nagle(-like)
>> bundling for TCP and SCTP.
> 
> Agreed, we actually did that in Michael Welzl, Stefan Jörer, Stein Gjessing: "Towards a Protocol-Independent Internet Transport API", FutureNet IV workshop in conjunction with of IEEE ICC 2011, 5-9 June 2011, Kyoto, Japan,
> using app PDU bundling because it's more meaningful than Nagle.
> 
> But here the idea was just to copy+paste the list from doc 1 (version 4) and put things under the correct headings, as a way to show how we *could* apply categorization methods.

hm, so perhaps we should have coordinated here. That list, in that version, wasn't quite complete. In the current version it's still not quite complete, as we're still trying to nail down how to partition the space of features (and how to divide things that are actually features from things that are just accidental effects of the way protocols have evolved). There are also aspects of the interfaces (coming from the interface discussion) we'd like to capture, on which we'd like to discuss f2f next Thursday.

Perhaps another way to approach this would be to start with a list of features we think we want in doc 2, and to use the background from doc 1 to fill in the gaps...

Cheers,

Brian

> Cheers,
> Michael
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps