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

[Vasilenko Eduard <[e-mail]>]

Then it is definitely separate 5.1.x looking to other small uses cases inside 5.1 that already got their separate chapter.

From: Mark Smith [mailto:[e-mail]]
Sent: 27 июля 2020 г. 12:47
To: Vasilenko Eduard <[e-mail]>
Cc: Fernando Gont <[e-mail]>; IPv6 Operations <[e-mail]>; [e-mail]
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - Load Balancer

Hi,

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.

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.

That is why they need to do non-RFC compliant things like digging into transport layer headers to work with unicast protocols like UDP, TCP and ICMP, trying to make them work across a fleet of nodes sharing a single unicast address.

An anycast address, combined with a multi-path transport layer protocol is the way to do service load balancing in an RFC compliant way.

See Section 5.7.7 of this draft for how.

https://tools.ietf.org/html/draft-smith-6man-form-func-anycast-addresses-01#section-5.7.7

Regards,
Mark.

On Mon, 27 Jul 2020, 19:08 Vasilenko Eduard, <[e-mail]<mailto:[e-mail]>> wrote:
Hi Fernando,
Hence again, following the logic of this draft (the level of detalization that you have given to 5.1) - may be you need additional section 5.1.x: Load Balancer have to look into TCP/UDP ports. Moreover, it could not trust "Flow label" - it is not reliable practice for LB.
Or alternatively you could say something about LB in section 5.1.2, but because it is a little special case - may be better to have separate 5.1.x

Eduard
-----Original Message-----
From: v6ops [mailto:[e-mail]<mailto:[e-mail]>] On Behalf Of Fernando Gont
Sent: 26 июля 2020 г. 8:46
To: IPv6 Operations <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: [v6ops] Operational Implications of IPv6 Packets with Extension Headers (Fwd: New Version Notification for draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt)

Folks,

We have posted a rev of our IETF I-D "Operational Implications of IPv6 Packets with Extension Headers".

The I-D is available at:
https://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt

Your feedback will be appreciated.

Thanks!

Cheers,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for
draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt
Date: Sat, 25 Jul 2020 22:28:50 -0700
From: [e-mail]<mailto:[e-mail]>
To: Fernando Gont <[e-mail]<mailto:[e-mail]>>, Gert Doering <[e-mail]<mailto:[e-mail]>>, Geoff Huston <[e-mail]<mailto:[e-mail]>>, Warren Kumari <[e-mail]<mailto:[e-mail]>>, Nick Hilliard <[e-mail]<mailto:[e-mail]>>


A new version of I-D, draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt
has been successfully submitted by Fernando Gont and posted to the IETF repository.

Name:           draft-gont-v6ops-ipv6-ehs-packet-drops
Revision:       04
Title:          Operational Implications of IPv6 Packets with Extension Headers
Document date:  2020-07-25
Group:          Individual Submission
Pages:          15
URL:
https://www.ietf.org/internet-drafts/draft-gont-v6ops-ipv6-ehs-packet-drops-04.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-v6ops-ipv6-ehs-packet-drops/
Htmlized:
https://tools.ietf.org/html/draft-gont-v6ops-ipv6-ehs-packet-drops-04
Htmlized:
https://datatracker.ietf.org/doc/html/draft-gont-v6ops-ipv6-ehs-packet-drops
Diff:
https://www.ietf.org/rfcdiff?url2=draft-gont-v6ops-ipv6-ehs-packet-drops-04

Abstract:
    This document summarizes the security and operational implications of
    IPv6 extension headers, and attempts to analyze reasons why packets
    with IPv6 extension headers may be dropped in the public Internet.




Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat



_______________________________________________
v6ops mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/v6ops

_______________________________________________
v6ops mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/v6ops

_______________________________________________
v6ops mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/v6ops