IETF Logo Mail Archive

RE: I-D Action: draft-han-6man-in-band-signaling-for-transport-qos-00.txt

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Thu, 19 October 2017 22:13 UTC

Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6629C13431B for <ipv6@ietfa.amsl.com>; Thu, 19 Oct 2017 15:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 nsVY2WzpYrb9 for <ipv6@ietfa.amsl.com>; Thu, 19 Oct 2017 15:13:19 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4530F13420D for <ipv6@ietf.org>; Thu, 19 Oct 2017 15:13:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v9JMDI4Y044403; Thu, 19 Oct 2017 15:13:18 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v9JMDHC8044399 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 19 Oct 2017 15:13:17 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 19 Oct 2017 15:13:16 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Thu, 19 Oct 2017 15:13:17 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tom Herbert <tom@herbertland.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: I-D Action: draft-han-6man-in-band-signaling-for-transport-qos-00.txt
Thread-Topic: I-D Action: draft-han-6man-in-band-signaling-for-transport-qos-00.txt
Thread-Index: AQHTSR+MnUgwu2qqQUiZZRbG4Yh0Q6LrsV4wgAB9HID//4ueQA==
Date: Thu, 19 Oct 2017 22:13:16 +0000
Message-ID: <2b3610187ec64b69941d638d48a71373@XCH15-06-11.nw.nos.boeing.com>
References: <150774513036.24791.2138264254901122467@ietfa.amsl.com> <cc11634a-b5a2-88b9-f36f-82b3fd9d8d70@gmail.com> <1D30AF33624CDD4A99E8C395069A2A162CD734B2@sjceml521-mbx.china.huawei.com> <a4da4b26-6402-ad0d-a5f5-5bddc192b8f7@gmail.com> <4E40E3EF-B0E5-490E-BFF2-0511D97E9E80@employees.org> <CALx6S341v1zd2Q9bts8-zrKxU59kieJTJJ=nHQ5w4oQZg=t_cA@mail.gmail.com> <17525287-DDA8-4930-B90B-F9228DF69A90@employees.org> <CALx6S37wLvuJ9tUGjYmzm63eq_bxq0jXSEgfCtH_2i74SvrbLA@mail.gmail.com> <20171017181646.GD31973@faui40p.informatik.uni-erlangen.de> <CALx6S34VRS4GumsFSqN8uDkv4TOLC8q+rOvyN=evUk83KPeHHg@mail.gmail.com> <20171019211637.GB878@faui40p.informatik.uni-erlangen.de> <296dd642b31741cc8ec4aa4b52913037@XCH15-06-11.nw.nos.boeing.com> <CALx6S36s_SoTqpPo=jXmrFC+pgUkEmF8UB_sx_0zGcK-G8JeTQ@mail.gmail.com>
In-Reply-To: <CALx6S36s_SoTqpPo=jXmrFC+pgUkEmF8UB_sx_0zGcK-G8JeTQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KyBdcSEas2pzC2fDk_aadbh0z0E>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2017 22:13:20 -0000

From: Tom Herbert [mailto:tom@herbertland.com] 

>> The problem remains, though: security mechanisms, which render the layer
>> 4 QoS knobs unworkable. Everything outside the "security enclaves" at
>> either end, and these security enclaves might just be inside the two end
>> hosts themselves, will have to be delivered best effort.
>
> Bert, I don't follow. One of the big wins using the 3-tuple is that it can
> still indicate a flow even if all the transport transport headers and
> payload are encrypted. So this should allow specifying QoS without
> revealing anything about the content except that the sender wants to group
> certain packets together as a flow and apply QoS on them.

True, Tom. I was responding to Toeless, when he says:

"Finally wrt. architectural cleanlyness: Per-flow service negotiation IMHO is clearly a transport layer function, there is no concept of 5-tuple flows at IP layer."

I saw that Toerless just responded, so he might be saying the same thing. But constraining the idea of in-band signaling to just IPv6 ought to be more workable, although you do need to get all those intermediate routers involved. I dunno. This always seems like the Achilles heel.

Bert

v2.23.0 | Report a Bug | By Email