IETF Logo Mail Archive

Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - Load Balancer

Fernando Gont <fgont@si6networks.com> Mon, 27 July 2020 10:09 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B05DF3A183D; Mon, 27 Jul 2020 03:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 4Z6PqnwRPrB1; Mon, 27 Jul 2020 03:09:19 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C9633A1836; Mon, 27 Jul 2020 03:09:17 -0700 (PDT)
Received: from [IPv6:2800:810:464:1f7:4ccc:6def:a83b:96ef] (unknown [IPv6:2800:810:464:1f7:4ccc:6def:a83b:96ef]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 1C87F2838A4; Mon, 27 Jul 2020 10:09:13 +0000 (UTC)
To: Mark Smith <markzzzsmith@gmail.com>, Vasilenko Eduard <vasilenko.eduard@huawei.com>
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org>
References: <b380408712364589a45ab9f39ab6f764@huawei.com> <CAO42Z2y1K7AM1-Ene_-RqWGOZ8ObgNfKyhu4PV+BUdAG8xaoKA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <4e073ff7-5230-654a-ab5f-002a6644b65b@si6networks.com>
Date: Mon, 27 Jul 2020 07:09:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAO42Z2y1K7AM1-Ene_-RqWGOZ8ObgNfKyhu4PV+BUdAG8xaoKA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wiU4Wrvcbr-sMRlSzTr_vvWsyI4>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - Load Balancer
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 10:09:21 -0000

Hello, Mark,

On 27/7/20 06:47, Mark Smith wrote:
> 
> If load balancers are going to be discussed, it also needs to be pointed 
> out that they don't follow the definition of unicast addresses.

Don't such addresses become anyast addresses, automatically, as per 
Section 2.6 of RFC4291?



> A unicast address is to uniquely identify a single node.
> 
> Load balancers share a single unicast address between multiple nodes, 
> contradictory to the unique and single node identification purpose of 
> unicast addresses.

As per RFC4291, such addresses would be anycast addresses, rather than 
unicast.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email