Just to chime in on what Jeffrey mentioned related to application layer load balancing web content or session load balancing can have a sticky persistence session setting using cookies which most all load balancers support so the connection remains pinned throughout its duration to the same server.
https://www.imperva.com/learn/availability/sticky-session-persistence-and-cookies/#what-is-a-sticky-session What is a sticky session Session stickiness, a.k.a., session persistence, is a process in which a load balancer creates an affinity between a client and a specific network server for the duration of a session, (i.e., the time a specific IP spends on a website). Using sticky sessions can help improve user experience and optimize network resource usage. With sticky sessions, a load balancer assigns an identifying attribute to a user, typically by issuing a cookie or by tracking their IP details. Then, according to the tracking ID, a load balancer can start routing all of the requests of this user to a specific server for the duration of the session. Kind Regards Gyan On Thu, Nov 11, 2021 at 9:09 AM Jeffrey (Zhaohui) Zhang <zzhang= [email protected]> wrote: > Hi, > > I did not have time to comment during today's LSR session so I am bringing > this to the list. I am also adding IDR and 6man lists because all these > three drafts are about the same use case. > > There were a long email discussion on the 6man draft here: > https://mailarchive.ietf.org/arch/msg/ipv6/4rw-pBcNZN7mzkArjUtVUzLcQJU/ > back in March. > > There are basically two problems here: > > 1. which server to pick > 2. how to stick to the same server when a UE (mobile device) moves > > The long discussion on the 6man list is mainly focused on #2. I don't know > if we can say there was a conclusion, but some people (me included) believe > that both problems are best solved at "app layer" instead of routing layer > - just put a load balancer next to the 5G UPF. > > Jeffrey > > -----Original Message----- > From: Jeffrey (Zhaohui) Zhang > Sent: Thursday, March 25, 2021 3:46 PM > To: Linda Dunbar <[email protected]>; Kaippallimalil John < > [email protected]>; IPv6 List <[email protected]>; idr@ietf. > org <[email protected]> > Subject: questions about draft-dunbar-idr-5g-edge-compute-app-meta-data > and draft-dunbar-6man-5g-edge-compute-sticky-service > > Hi Linda, John, > > I have the following questions. > > The two related drafts listed the following three problems respectively: > > 1.3. Problem#1: ANYCAST in 5G EC Environment.............. 6 > 1.4. Problem #2: Unbalanced Anycast Distribution due to UE > Mobility.................................................. 7 > 1.5. Problem 3: Application Server Relocation............. 7 > > 1.2. Problem #1: ANYCAST in 5G EC Environment.............. 4 > 1.3. Problem #2: sticking to original App Server........... 5 > 1.4. Problem #3: Application Server Relocation............. 5 > > Why is problem #2 different in the two drafts? Is it true that none of the > two drafts address problem #3? > The idr draft talk about "soft anchoring" problem and solution - how is > that different from the "sticky service"? > > Thanks. > Jeffrey > > Juniper Business Use Only > > _______________________________________________ > Idr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/idr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email [email protected] <[email protected]>* *M 301 502-1347*
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
