IETF Logo Mail Archive

Re: [Taps] TCP components

Joe Touch <touch@isi.edu> Thu, 16 July 2015 21:51 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 8A77D1A1B86 for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 14:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level:
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 S2Fnp_QdxYg3 for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 14:51:51 -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 A0E3C1A1B84 for <taps@ietf.org>; Thu, 16 Jul 2015 14:51:51 -0700 (PDT)
Received: from [128.9.184.152] ([128.9.184.152]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id t6GLpNBl027141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Jul 2015 14:51:24 -0700 (PDT)
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>, 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> <5a72988f46e4be6b26811213fcc4d99f@mail.gmail.com> <55A6A3C9.3040003@isi.edu> <9ec98209ec4b692bf9c172eec0c86711@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
X-Enigmail-Draft-Status: N1110
Message-ID: <55A8275B.4010907@isi.edu>
Date: Thu, 16 Jul 2015 14:51:23 -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: <9ec98209ec4b692bf9c172eec0c86711@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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/0VfEi2yVGYjKUAuNxeRE5AufVOg>
Cc: Brian Trammell <ietf@trammell.ch>, taps@ietf.org, Michael Welzl <michawe@ifi.uio.no>, 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: <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 21:51:52 -0000

Hi, Karen,

On 7/16/2015 12:57 AM, Karen Elisabeth Egede Nielsen wrote:
>> What portion of RFC793's API do you consider outdated?
....
> HI,
> 
> I was thinking about the PUSH flag mainly.
> 
> In our socket api implementation we do not allow for set of PUSH in send
> calls nor do we provide the PUSH flag indication upwards on the receiver
> side.

That's consistent with RFC1122, which updates RFC793.

> I think that after RFC793 it has been clarified that TCP MAY allow for set
> of PUSH flag in send() and MAY OPTIONALLY provide this information upwards
> on the receiver side.

Yes.

> I think that it would be questionable to follow RFC793 wording here on
> PUSH.

Sure; I was being broad in my reference back to RFC793; updates need to
be chased down too, so to the extent that the updates make RFC793
outdated, you're correct. However, the bulk of RFC793's API remains in
effect.

Joe

v2.23.0 | Report a Bug | By Email