Sheng, Brian, el at: I reviewed draft-ietf-intarea-flow-label-balancing-00
Here are my comments: ------------------------------------- The draft is to suggest using IPv6 header's flow label field to identify different flows from IPv6 hosts. The draft tries to emphasize that the flow label can help devices along the way between Source & destination to achieve better flow separation or finer tuned traffic balancing if there are multiple paths. However, the Section 3 devotes so much to various LB schemes. But many are irrelevant. There are many different types of Load Balance, the DNS based load balancing, which is often called global LB, has nothing to do with LB in front of a cluster of servers. Some description about LB in Section 3 is not quite to the point. For example, the second bullet you stated: "Another method, for HTTP servers, is to operate a layer 7 reverse proxy in front of the server farm." The LB in front of a cluster of servers is orthogonal to DNS based global LB. Your draft didn't even mention "Direct Server Return (DSR)" LB scheme which is used heavily in DC to balance load among a cluster of servers. In this scheme, all the servers in a cluster share a common IP address which is same as the LB, or use floating IP address for hosts. The figure in Page 7 is has some errors too. The DNS based Load Balancing is usually in the Access network. (I really think this figure is not necessary because it doesn't help the draft at all). The LB for Server Cluster is more likely located in a Data Center. Therefore, I suggest that you replace Section 3 with following: 3. Summary of Load Balancing Techniques: There are many different types of Load Balancing in networks. There is DNS based global LB, typically placed closer to clients, there are also LB for a cluster of servers who share same IP address as the LB, there are other LB. This draft is to describe how flow label can further optimize load balancer in front of a cluster of servers. Highlight of Load Balancing Algorithms: Typical industry standard load balancing algorithms available today include: Round Robin Least Connections Fastest Response Time Weighted Round Robin Weighted Least Connections Custom values assigned to individual servers in a pool based on SNMP or other communication mechanism 4. An improved Load Balancing Algorithms using Flow Label (you can describe how Flow Label improve the LB algorithms currently being deployed"). Linda > -----Original Message----- > From: Sheng Jiang > Sent: Monday, April 01, 2013 9:04 PM > To: Linda Dunbar > Subject: RE: Reviewing of flow label balancing > > http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-00 > > Many thank, > > Sheng > > >-----Original Message----- > >From: Linda Dunbar > >Sent: Monday, April 01, 2013 10:14 PM > >To: Sheng Jiang > >Subject: RE: Reviewing of flow label balancing > > > >Sheng, > > > >Sorry for slipping through my mind. > >Can you send me the link? > > > >Linda > > > >> -----Original Message----- > >> From: Sheng Jiang > >> Sent: Monday, April 01, 2013 2:02 AM > >> To: Linda Dunbar > >> Cc: Brian E Carpenter; Suresh Krishnan > >> Subject: Reviewing of flow label balancing > >> > >> Hi, Linda, > >> > >> You volunteered to review our flow label balancing document during > the > >> IntArea meeting in Orlando. Could you please confirm when we can get > >> your feedback? > >> > >> Many thanks and best regards, > >> > >> Sheng _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
