Re: [v6ops] new draft: draft-li-v6ops-load-balancing-requirement-00.txt

[[e-mail]]

Thanks alot Ray for your comments and interests.

The submitted draft is mainly focused on the load balancing requirement of the network(ISP) side concentrators, i.e., the ARTF of dslite, the BR of 6rd, the NAT64 and IVI translators. Since web proxy is used at the enterprise side, it is IMO similar to B4 of dslite, and CE of 6rd.

ALG problem should be considered by the translation technology, such as NAT64. When designing the loadbalancing solution for NAT64, we will take this point into account.

Best Regards,
Zhenqiang Li
2011-07-06 

--------------------------------------------------------------------------------

From: Ray Hunter 
Sent: 2011-07-05  21:38:12 
To: [e-mail] WG; [e-mail] 
Subject: re: [v6ops] new draft: draft-li-v6ops-load-balancing-requirement-00.txt 
 
Thanks for sharing your draft with us.

I think you may be missing a whole class of bottleneck that is not 
receiving too much attention at the moment.

Many enterprises transport the majority of their traffic over the 
boundary between their 'private' internal networks and the Internet via 
use of a "web proxy."

Application Level Gateways (ALG) = RFC2766 Section 2.4 are also 
considered a valid translation mechanism between IPv4 and IPv6 islands, 
and can be especially useful for simple outbound HTTP based web traffic. 
They may also be useful for translating certain inbound requests.

Traditionally the WCCP Web Cache Proxy Protocol (non IETF protocol, but 
described in http://tools.ietf.org/html/draft-wilson-wrec-wccp-v2-01) 
has been used to balance requests between multiple proxies, or for 
example between an IPv4 router and a farm of multiple WAN acceleration 
devices.

AFAIK WCCPv2 does not (yet) support IPv6, which IMHO is quite an 
omission in the options given to enterprises to migrate to IPv6 in a 
smooth manner.

regards, and good luck with your deployment,

RayH