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 21:41 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 E268E132A1A for <ipv6@ietfa.amsl.com>; Thu, 19 Oct 2017 14:41:51 -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 ctfVOAwilqwd for <ipv6@ietfa.amsl.com>; Thu, 19 Oct 2017 14:41:50 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 C85661321A0 for <ipv6@ietf.org>; Thu, 19 Oct 2017 14:41:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v9JLfnZt030681; Thu, 19 Oct 2017 14:41:49 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v9JLfhoI030642 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 19 Oct 2017 14:41:43 -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 14:41:42 -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 14:41:43 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Toerless Eckert <tte@cs.fau.de>
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+MnUgwu2qqQUiZZRbG4Yh0Q6LrsV4w
Date: Thu, 19 Oct 2017 21:41:42 +0000
Message-ID: <296dd642b31741cc8ec4aa4b52913037@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>
In-Reply-To: <20171019211637.GB878@faui40p.informatik.uni-erlangen.de>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/NMBKpvCL6OwOBBUw-QJXFatAly0>
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 21:41:52 -0000

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Toerless Eckert

> 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 would agree I  principle, although IPv6 does have that flow label that makes the 5-tuple less essential to identify an individual "flow," and it sits at layer 3. 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

v2.23.0 | Report a Bug | By Email