Hi Ask， Ask Bjørn Hansen <a...@develooper.com>于2017年3月21日周二 下午4:11写道：
> > > On Mar 20, 2017, at 0:49, Lanlan Pan <abby...@gmail.com> wrote: > > > > Everyone has known that physical location and the topology of content > delivery DO NOT MATCH. > > As last mail reply to Warren, my proposal can offer the SAME critical > information for authoritative server to make tailored response decision as > ECS's client subnet. > > Because in database such as maxmind, ECS (client subnet) can be map > into <AS number, country, province, ISP>, which also guide network > topology. > > Therefore, if ECS has ANY value for optimizing content delivery on the > Internet, then EIL has. > > > > For example，If ECS is tell AUTH : the query is from 114.240.0.0/24. > The AUTH knows that ECS(114.240.0.0/24) is indicated (CHINA, BEIJING, > UNICOM), which is not only geolocation, but also contains network topology > information. Then AUTH can return satisfied ip address according to the > topology of content delivery. > > Except for very small networks, the network topology isn’t just the name > of the provider. I suspect that if you took away all the geoip type lookups > the larger content delivery systems would work fine; but if you did the > opposite (what you are proposing with EIL) they would not. > > I believe Netflix has public information about how their OpenConnect > system uses BGP and network topology information. > CDN providers configure their BGP with its AS neighbor, the network topology optimization focus on, make their datacenters connect to more and more important ISP (such as Level 3, Comcast, etc) , with faster and faster connect speed. Consider about DNS based delivery, as last mail I reply to brian, CDN can work finer if resolver‘s IP nearby client’s IP. See this example of ECS : Which CDNs support edns-client-subnet? <https://www.cdnplanet.com/blog/which-cdns-support-edns-client-subnet/>, they *map the ECS client subnet into the geolocation (what EIL give)*, and then make DNS decision. Because on AUTH side, they do not so care about each client subnet, but configure on aerial view geolocation level. AUTH no need configure for each client subnet, geoip-level precision check is offen took for IP connect speed sample test. Therefore, EIL <country, province, isp> can give the *SAME* *sufficent* geolocation information as ECS for AUTH, to decide which is the best IP addresses to response, because each CDN IP *serves many client subnets in the same area*. For example, all of these ECS can be map into* EIL(CHINA, BEIJING, UNICOM)* *: ECS(103.3.120.0/24 <http://103.3.120.0/24>), ECS(111.192.0.0/16 <http://111.192.0.0/16>),ECS(114.240.0.0/16 <http://114.240.0.0/16>), ECS(120.132.0.0/16 <http://120.132.0.0/16>), ECS(123.112.0.0/16 <http://123.112.0.0/16>), ECS(124.64.0.0/16 <http://124.64.0.0/16>), ECS(125.33.0.0/16 <http://125.33.0.0/16>), ECS(202.106.0.0/16 <http://202.106.0.0/16>), ECS(210.82.0.0/16 <http://210.82.0.0/16>), ECS(219.158.128.0/24 <http://219.158.128.0/24>), ECS(221.216.0.0/16 <http://221.216.0.0/16>), ECS(222.128.0.0/16 <http://222.128.0.0/16>), ECS(49.152.0.0/16 <http://49.152.0.0/16>), ECS(61.48.0.0/16 <http://61.48.0.0/16>),......* > > Ask (speaking only for myself) > > -- 致礼 Best Regards 潘蓝兰 Pan Lanlan
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
