Re: [Taps] How to handle Protocol stacks that are not equivalent
Anna Brunström <anna.brunstrom@kau.se> Tue, 23 July 2019 20:53 UTC
Return-Path: <anna.brunstrom@kau.se>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA74120153 for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 13:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.297
X-Spam-Level:
X-Spam-Status: No, score=-4.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kau.se
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 mjQ2d1WgWstz for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 13:53:22 -0700 (PDT)
Received: from smtp1.kau.se (smtp1.kau.se [130.243.21.250]) by ietfa.amsl.com (Postfix) with ESMTP id 892D4120999 for <taps@ietf.org>; Tue, 23 Jul 2019 13:53:22 -0700 (PDT)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [192.36.171.202]) by smtp1.kau.se (Postfix) with ESMTP id 626331804B33; Tue, 23 Jul 2019 22:53:21 +0200 (CEST)
Received: from Exch-A3.personal.kau (exch-a3.kau.se [130.243.19.84]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x6NKrJgh145551 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Tue, 23 Jul 2019 22:53:20 +0200
Received: from Exch-A2.personal.kau (130.243.19.83) by Exch-A3.personal.kau (130.243.19.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1591.10; Tue, 23 Jul 2019 22:53:19 +0200
Received: from Exch-A2.personal.kau ([fe80::d09:7e68:ff95:4a60]) by Exch-A2.personal.kau ([fe80::d09:7e68:ff95:4a60%7]) with mapi id 15.01.1591.017; Tue, 23 Jul 2019 22:53:06 +0200
From: Anna Brunström <anna.brunstrom@kau.se>
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, Max Franke <mfranke@inet.tu-berlin.de>
CC: Joe Touch <touch@strayalpha.com>, Theresa Enghardt <theresa@inet.tu-berlin.de>, "taps@ietf.org" <taps@ietf.org>
Thread-Topic: [Taps] How to handle Protocol stacks that are not equivalent
Thread-Index: AQHVQNQriOlnBtdw5kCBd2y9GfbT16bYI10AgAAKWoCAAAMSAIAACicAgAABEgCAAAHSgIAAHY4AgABTrGA=
Date: Tue, 23 Jul 2019 20:53:06 +0000
Message-ID: <ce92bad3a6294c78a4078d60da05615d@kau.se>
References: <fcbd50de-9364-4e33-aebb-dccaeece8141@email.android.com> <E6C9EB11-7537-4CB5-A75D-9295A6B5A5BD@apple.com>
In-Reply-To: <E6C9EB11-7537-4CB5-A75D-9295A6B5A5BD@apple.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.243.27.149]
Content-Type: multipart/alternative; boundary="_000_ce92bad3a6294c78a4078d60da05615dkause_"
MIME-Version: 1.0
X-Bayes-Prob: 0.9999 (Score 5, tokens from: outbound, outbound-kau-se:default, kau-se:default, base:default, @@RPTN)
X-p0f-Info: os=Windows 7 or 8, link=Ethernet or modem
X-CanIt-Geo: No geolocation information available for fe80::d09:7e68:ff95:4a60
X-CanItPRO-Stream: outbound-kau-se:outbound (inherits from outbound-kau-se:default, kau-se:default, base:default)
X-Canit-Stats-ID: 0a0EkRjcr - ac600e4db7d6 - 20190723
X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?c=f&i=0a0EkRjcr&m=ac600e4db7d6&rlm=outbound-kau-se&t=20190723
X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?c=n&i=0a0EkRjcr&m=ac600e4db7d6&rlm=outbound-kau-se&t=20190723
X-Antispam-Training-Phish: https://mailfilter.sunet.se/canit/b.php?c=p&i=0a0EkRjcr&m=ac600e4db7d6&rlm=outbound-kau-se&t=20190723
X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?c=s&i=0a0EkRjcr&m=ac600e4db7d6&rlm=outbound-kau-se&t=20190723
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kau.se; h=from:to:cc :subject:date:message-id:references:in-reply-to:content-type :mime-version; s=canit; bh=cR2ttHEzd15MDyQs1P2DVsov5a/LDXCQJg0A7 NGJ2O8=; b=PTmwtR69eq4+kECXE/wp0/ahI14sFuoKqWF7+WQrgmKnsyWUpu7U7 QD+gljJs5Mh5MWSxTH9RsxuweZdDQ71GLX8g6x6V+TECzcQPbDbp4ivZ3QhxKI1z tRTct3VgwsuT4goCWPPCp2JsvgFuqNCvIGNKWtPqZx79FyFPw6ejr+2mjug6HikZ 6NLzjX6IFsD73OFaYMgcQVqtnISwUWzUIsSmGacN/4F0pvnVEUSxqtzzvqLF68jw UQXqiF9J55g9LboxTMZuD0MpVPAEu8YEqtffwLyzKomAsOzM8eRtRWknkssuAng1 CXULbL2ee9r/LFn2MXJ0N251P2oJZuQog==
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/22-oK7NTULNtmArFOA3vH-aOizA>
Subject: Re: [Taps] How to handle Protocol stacks that are not equivalent
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <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: Tue, 23 Jul 2019 20:53:26 -0000
From: Taps <taps-bounces@ietf.org> On Behalf Of Tommy Pauly Sent: den 23 juli 2019 19:52 To: Max Franke <mfranke@inet.tu-berlin.de> Cc: Joe Touch <touch@strayalpha.com>; Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; Theresa Enghardt <theresa@inet.tu-berlin.de>; taps@ietf.org Subject: Re: [Taps] How to handle Protocol stacks that are not equivalent Yes, that's correct. My interpretation is that being in the candidate set already requires equivalence. Same here, seems we all agree on this. Thanks, Anna We can make the text more clear here, but it isn't a technical change. Thanks, Tommy On Jul 23, 2019, at 12:05 PM, Max Franke <mfranke@inet.tu-berlin.de<mailto:mfranke@inet.tu-berlin.de>> wrote: So if I understand this correctly, this boils down to the fact that if two protocols are in the candidate set for racing they are also equivalent? Thus we dont have to worry about unequivalent protocols as they are never part of the same candidate set anyway? Best Max Am 23.07.2019 11:59 schrieb Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>: Hi Joe, Yes, I completely agree. The current text in -arch expresses this as: 2. Both stacks MUST offer the same transport services, as required by the application. For example, if an application specifies that it requires reliable transmission of data, then a Protocol Stack using UDP without any reliability layer on top would not be allowed to replace a Protocol Stack using TCP. However, if the application does not require reliability, then a Protocol Stack that adds unnecessary reliability might be allowed as an equivalent Protocol Stack as long as it does not conflict with any other application-requested properties. If you think we can clarify this any further, let me know! Thanks, Tommy On Jul 23, 2019, at 11:55 AM, Joe Touch <touch@strayalpha.com<mailto:touch@strayalpha.com>> wrote: On Jul 23, 2019, at 8:19 AM, Theresa Enghardt <theresa@inet.tu-berlin.de<mailto:theresa@inet.tu-berlin.de>> wrote: Another important difference between TCP and UDP are Message Boundaries. So in some cases, TCP + Framer may be equivalent to UDP. FWIW, they might provide *similar* capabilities, even only those that the app is concerned about, but there are a LOT of other differences that can’t be glossed over. In some cases, it is TCP that is lacking (as above); in others, UDP). It’s only important whether the user does or doesn’t care about those properties. When they match what they care about, they can be considered equivalent. I.e., there’s not likely going to be a strict and absolute equivalence between transports. Equivalence is TO THE USER, relative to their constraints. Joe _______________________________________________ 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] How to handle Protocol stacks that are not… Philipp S. Tiesel
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Gorry Fairhurst
- Re: [Taps] How to handle Protocol stacks that are… Theresa Enghardt
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Joe Touch
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Max Franke
- Re: [Taps] How to handle Protocol stacks that are… Joe Touch
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Anna Brunström
- Re: [Taps] How to handle Protocol stacks that are… Theresa Enghardt
- Re: [Taps] How to handle Protocol stacks that are… Max Franke
- Re: [Taps] How to handle Protocol stacks that are… Philipp S. Tiesel