IETF Logo Mail Archive

Re: Flow label [not draft-han-6man-in-band-signaling-for-transport-qos-00.txt]

Toerless Eckert <tte@cs.fau.de> Fri, 20 October 2017 21:35 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 226C9133059 for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 14:35:03 -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 r96oUDbRruJN for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 14:35:01 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20B421329B5 for <ipv6@ietf.org>; Fri, 20 Oct 2017 14:35:00 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id EC6A058C4B0; Fri, 20 Oct 2017 23:34:56 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id D7663B0CF30; Fri, 20 Oct 2017 23:34:56 +0200 (CEST)
Date: Fri, 20 Oct 2017 23:34:56 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Tom Herbert <tom@herbertland.com>
Cc: "Leddy, John" <John_Leddy@comcast.com>, 6man WG <ipv6@ietf.org>
Subject: Re: Flow label [not draft-han-6man-in-band-signaling-for-transport-qos-00.txt]
Message-ID: <20171020213456.GA14112@faui40p.informatik.uni-erlangen.de>
References: <CALx6S36s_SoTqpPo=jXmrFC+pgUkEmF8UB_sx_0zGcK-G8JeTQ@mail.gmail.com> <20171019220935.GD878@faui40p.informatik.uni-erlangen.de> <33ff8930-d1af-ea54-7bb4-a6a9b289269e@gmail.com> <20171020144015.GA3093@faui40p.informatik.uni-erlangen.de> <8AE3421D-304B-42F9-B12A-361E21DFF069@employees.org> <CALx6S35nr8JapogAC5Gsi0iPxXhJa9NKOHhzUAnJtmqTwEGtgg@mail.gmail.com> <CDAEBFFD-3B70-41D3-BB41-FCF40ADA2115@employees.org> <CALx6S35Y7OVFFSiw4-ei84HEk0FjEXmS8TnNx8Uex9-0rAxdfg@mail.gmail.com> <2C4B0FD6-418E-441F-8B43-6C60451E3A51@cable.comcast.com> <CALx6S34918E7jJtwezMBtqWE2sL5AGowNYUuHpYBSzOt0JW1-Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CALx6S34918E7jJtwezMBtqWE2sL5AGowNYUuHpYBSzOt0JW1-Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GaoX_Q2fzrnch8mHKHvNgz-OED8>
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 21:35:03 -0000

On Fri, Oct 20, 2017 at 01:53:54PM -0700, Tom Herbert wrote:
> Yes, there is no requirement that the flow label be persistent at all in a
> flow. That gives some nice properties. For instance, at FB we implemented
> flowbender using the flow label so that when a host detects a poor quality
> path it can randomly try another flow label for the connection to hopefully
> find a better path (a type of source routing). Random Packet Spraying could
> use the flow label and randomly set it per packet to achieve perfect load
> balancing in a multi-path network.

Seems like that spraying example is a good reason why one would need to have
maybe at least two flow labels: One thats permitted to create state, and one thats
not (eg: used for load balancing). 

Toerless
> 
> Tom

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

v2.23.0 | Report a Bug | By Email