IETF Logo Mail Archive

Re: Reference based Routing (RbR)

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 24 May 2020 21:46 UTC

Return-Path: <brian.e.carpenter@gmail.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 168013A0C88 for <ipv6@ietfa.amsl.com>; Sun, 24 May 2020 14:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jv43DbZ7saFH for <ipv6@ietfa.amsl.com>; Sun, 24 May 2020 14:46:04 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B59483A0C82 for <6man@ietf.org>; Sun, 24 May 2020 14:46:04 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id ci23so7710211pjb.5 for <6man@ietf.org>; Sun, 24 May 2020 14:46:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=V1rHd0rZZFDojpUeNuwqsvd83itADZy9MeTA57+zFH8=; b=awlAVDwTGpdMJxdc3vSK4pWzrR7KqZqz2wjR5TpnLr5V/p7hcT+gomI356osbQII+0 YNXjdKHhEo/KLxoUyDzskwJnCByiJWbe7WjNpyiBurEwy4g/BQDI8comUkxVmkuyHpJN 2frNyIhs74QSgDXO2r6IgEFBfSXB1Fw/m7c1aFp02qKQuEjCyX5fijo8hlZMNLuqcNA3 SaESvjyhq1tPmua7S/ci4JhkbRbA89oatcOJfj1GzQeYzxT5lBTQgAg3/ppIspYQ7kG/ IF9R0slepA6iN9wtYRv/pJ7Y3MOKu35jFveTYDo13JdJmN4UFpqxFE2dDLYNRS41YmMd kz9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=V1rHd0rZZFDojpUeNuwqsvd83itADZy9MeTA57+zFH8=; b=tWwghsKC+Oo5yw6ZtLjJxwV4MHhkjFftJac2l+QcdW38nXmbNFj5H+2QMbj0Uvm8MK NmBIAiVhZTHj1IxMV8CnrYjBxEEAARxJWgw0Byg1cBNZTbib9zcjomOBT0HlRM5defzb f59yrK8J32z51oGtvoGTMFMwWXrI5gFHDhAkMXGBmCK8sdEr44qRdH7QURkgWqUuQ77i A9CehifOLuhg8mBrET9pLQAqkipJ4xWWp/DDb5+Ced1vTcdunpmsDBnqGexmCedtweFD uUAGONJL1GHqMCWmW6WR/u0kpfXHZ/0q3hD0riR1EFnRltDKvQfdjZWDB2YJ1LDQiaaS Br1Q==
X-Gm-Message-State: AOAM533h8+yUmq1bn/TCEvfAUuoR3GxS9y6GjvBTZtL9bz7Zce29DLSa otx/2BMNzlb27icMOqMPpeLsicRJ
X-Google-Smtp-Source: ABdhPJyV8LKmFEZEVOHJLcEtBqxuuyciHDxgXz12v+CpHhnuxOh2nJZT7OCV135aEpg9pRibEeKz8A==
X-Received: by 2002:a17:90a:a784:: with SMTP id f4mr12971319pjq.131.1590356762586; Sun, 24 May 2020 14:46:02 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.12.178]) by smtp.gmail.com with ESMTPSA id u1sm10205669pgf.28.2020.05.24.14.46.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 24 May 2020 14:46:01 -0700 (PDT)
Subject: Re: Reference based Routing (RbR)
To: Robert Raszuk <robert@raszuk.net>, Nick Hilliard <nick@foobar.org>
Cc: 6man <6man@ietf.org>
References: <82165E20-884F-467B-B364-1B0A8B84A38A@tony.li> <05B3C66C-5CB2-4871-8AF9-52517C56866C@employees.org> <32ca2b0e-3fdd-9c27-736c-7033a3e7a37b@foobar.org> <CAOj+MMH_jnK8U3vPszZfn-Hdm-q0v=OKEbaHF4nAwTQabioaKQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e4a65823-91cd-eb95-73af-6562f91fb729@gmail.com>
Date: Mon, 25 May 2020 09:45:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAOj+MMH_jnK8U3vPszZfn-Hdm-q0v=OKEbaHF4nAwTQabioaKQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tZhUl9h7x5UTxphFDsnDUh5Ptp0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 24 May 2020 21:46:10 -0000

On 25-May-20 09:06, Robert Raszuk wrote:
> Hi Nick, 
> 
> FYI 
> https://blog.apnic.net/2018/01/11/ipv6-flow-label-misuse-hashing/  

The IETF is not the protocol police. If vendors ignore published standards, it really isn't something we can fix.

   Brian

> 
> Thx,
> R. 
> 
> On Sun, May 24, 2020 at 11:04 PM Nick Hilliard <nick@foobar.org <mailto:nick@foobar.org>> wrote:
> 
>     Ole Troan wrote on 24/05/2020 21:50:
>     > Inside a limited domain using encapsulation, which is what all these
>     > solutions cover, you could likely use the flow label as a “path
>     > tag”.
> 
>     this is not a safe assumption.  The target deployment scenarios appear
>     to be own-tenancy networks with an emphasis on large-scale datacentre
>     implementations.  In this sort of situation it would be normal for the
>     network fabric to use multiple links between routing nodes, thereby
>     creating a requirement for load balancing.  Removing one of the entropy
>     sources for bucket management would be unwise in these circumstances,
>     particularly given the likelihood of elephant flows.
> 
>     Nick
> 
>     --------------------------------------------------------------------
>     IETF IPv6 working group mailing list
>     ipv6@ietf.org <mailto:ipv6@ietf.org>
>     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>     --------------------------------------------------------------------
> 
> 
> --------------------------------------------------------------------
> 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