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 14:40 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 AAD921241F3 for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 07:40:22 -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 i507LsRYsFQb for <ipv6@ietfa.amsl.com>; Fri, 20 Oct 2017 07:40:19 -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 B9F06128D0D for <ipv6@ietf.org>; Fri, 20 Oct 2017 07:40:19 -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 C9B4858C4B8; Fri, 20 Oct 2017 16:40:15 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id AA4FBB0CF23; Fri, 20 Oct 2017 16:40:15 +0200 (CEST)
Date: Fri, 20 Oct 2017 16:40:15 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ipv6@ietf.org
Subject: Re: Flow label [not draft-han-6man-in-band-signaling-for-transport-qos-00.txt]
Message-ID: <20171020144015.GA3093@faui40p.informatik.uni-erlangen.de>
References: <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> <20171019220935.GD878@faui40p.informatik.uni-erlangen.de> <33ff8930-d1af-ea54-7bb4-a6a9b289269e@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <33ff8930-d1af-ea54-7bb4-a6a9b289269e@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GyUEN1we-KeiJk8wcMjIZ8hIaNU>
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 14:40:23 -0000

On Fri, Oct 20, 2017 at 01:05:49PM +1300, Brian E Carpenter wrote:
> > Problem with flow label is same as with hop-by-hop option: burned because
> > nobody should dare use it for something useful with all the inconsistent 
> > code out in the field.  Nothing against redefining it (with new encoding)
                                                          ^^^^^^^^^^^^^^^^^^^
> There is no encoding. It's 20 opaque bits (and always has been). Please
> read https://tools.ietf.org/html/rfc6437.

Sorry, lame use of words. Meant to say "stronger definition of DO and DONTs
which may include new semantics". I never tried to analyze the state of
affairs on flow label as i did for router alert. Just taking it from what
i heard, last from Joel at the pechakucha.

Btw: IPv6 router alert did already fix one broken piece of IPv4 router
alert, the registry is more flexible ;-))

Cheers
    Toerless

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

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

v2.23.0 | Report a Bug | By Email