Hi Barry, There are complex factors to optimize the datacenter connection of CDN. I know every CDN need "Everything is in IP, RIPs, FIBs, AS Patch, system load, content availability, etc." to measure better path calculations. I understand that "Knowing that it is in Palo Alto California" is not something useful for Data Provider path calculation, load balance optimization, etc. Note that, I *DON'T* mean that knowing <country, province, isp> is sufficient for CDN.
But, as you methioned in last mail: * > Once the connection to the client to the CDN is made, the CDN operator has the full details of the client. * CDN can known "Everything is in IP, RIPs, FIBs, AS Patch, system load, content availability, etc." without ECS. CDN can do the BGP optimization and datacenter load balance without ECS. *Sperate the consideration of datacenter path calculation (Data Provider) and dns response (AUTH).* - Data provider can make datacenter path calculation without ECS because all clients will connect. - ECS is help AUTH to return the satisfied dns response to client. Therefore, the question is, *what can help AUTH to decide the response* ? I mean that, most of time, knowing <country, province, isp> is sufficient for AUTH make dns response. My statement Is, for example: the subnets (subnet_1 ... subnet_100) in the same <country, province, isp> geolocation, always visit the same CDN datacenter sets (DC_1 .. DC_2) . datacenter sets can be changed when network status is varied, network path connection latency become larger, load balance adjustment, etc... EIL is sufficient if AUTH make dns decison on <country, province, isp> geolocation pricise level. If your operational realities is: subnet_1 ... subnet_100 in the same <country, province, isp> geolocation, you apply subnet_1 ... subnet_50 visit DC_1, subnet_51 .. subnet_100 visit DC_2 ECS is satisfied with your statement, because your AUTH make dns decision down to subnet pricise level. Barry Raveendran Greene <bgre...@senki.org>于2017年3月24日周五 上午2:06写道： > > > On Mar 21, 2017, at 11:38 PM, Lanlan Pan <abby...@gmail.com> wrote: > > > > However, if you know about the geolocation <COUNTRY, PROVINCE, ISP>, > you can make a better response, most of time, is the best response too. > > Your statement is not matching the operational realities I live in. I > understand how mapping is done in my current environment. I understand how > it is done in many of my peer CDNs. I also understand the tools I would > need to measure better path calculations. Everything is in IP, RIPs, FIBs, > AS Patch, system load, content availability, etc. Knowing that it is in > Palo Alto California is not something useful. > > What is needed is the allocated IP block to start the mapping > determination. Then every CDN does their “secret sauce” to delver the best > customer experience. Geographic location is just not one of those factors. > ECS delivers this now. > > > > > > -- 致礼 Best Regards 潘蓝兰 Pan Lanlan
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
