Re: Hop-by-hop [not draft-han-6man-in-band-signaling-for-transport-qos-00.txt]

Toerless Eckert <tte@cs.fau.de> Fri, 20 October 2017 16:41 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 5FA2C1342EC for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 09:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 n-k5Q8Wg3B-q for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 09:41:36 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB7AB132D67 for <ipv6@ietf.org>; Fri, 20 Oct 2017 09:41:35 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id EFE6958C4B0; Fri, 20 Oct 2017 18:41:31 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id D895CB0CF20; Fri, 20 Oct 2017 18:41:31 +0200 (CEST)
Date: Fri, 20 Oct 2017 18:41:31 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>
Subject: Re: Hop-by-hop [not draft-han-6man-in-band-signaling-for-transport-qos-00.txt]
Message-ID: <20171020164131.GD3093@faui40p.informatik.uni-erlangen.de>
References: <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> <e7da5913-1fd9-a476-e654-44cb5cfdc10c@gmail.com> <20171019212353.GC878@faui40p.informatik.uni-erlangen.de> <e4f7ea8b-ce0e-d829-7b1e-b53c3a890355@gmail.com> <e03ad50248824701bf3f6fbedcfa1ca4@XCH15-06-11.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <e03ad50248824701bf3f6fbedcfa1ca4@XCH15-06-11.nw.nos.boeing.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xaE6Hdj0Bn8wcbzBULFXHcS3QV4>
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: Fri, 20 Oct 2017 16:41:40 -0000

On Fri, Oct 20, 2017 at 12:51:23AM +0000, Manfredi, Albert E wrote:
> Absolutely, and that's the rub, isn't it? In-band QoS, no matter really whether it's done using an IPv6 3-tuple, or IP-agnostic 5-tuple (without encryption), is ultimately practical only inside walled gardens.

IMHO only true for DiffServ QoS unmodified, not for other forms
of QoS. DiffServ QoS even has fundamental challenges inside walled
gardens:

- Way to complex to dynamically adjust queue share of classes
  in enterprise deployments (only useful in mission specific network
  with well defineable persistent traffic profiles).
- Unnecessary differentiation now that a lot more media traffic is elastic
  and a lot more best effort traffic not buffer-bloaty

> These discussions bring me back to ... ATM. Trying to re-create ATM with IP. But ATM died, in large part, because of this.

I don't know. There is this cool flying car from the 50th in the Seattle
Museum of Flight. I don't think its historic state proves that planes
or cars are bad ideas.  1280 is the the 53 and flying cars are also coming
back and so will QoS.

Anyhow. Even though DSCP is in IPv6 header and this WG claims that
it must be the ones deciding on onpath packet inspection, i fear
the mayority here is not interested in QoS, so lets move the discussion
to TSVWG.

Cheers
    Toerless

> Bert
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
---
tte@cs.fau.de