左鹏 wrote:
> The "precise traffice scheduling" i mentioned is not only for performance
> reason, but also for capacity reason.
CDNs already have the ability to do precise traffic scheduling for both
performance and capacity reasons, using the existing capabilities built
into the DNS.
> yes, more
On Friday, December 15, 2017 04:19:44 PM 左鹏 wrote:
> thanks for your comment!
>
>
> > -原始邮件-
> > 发件人: "Robert Edmonds"
> > Or, put another way, we like existing resolver implementations just
> > fine, we just wish there were a lot more resolver instances, and closer
> > to clients :-)
>
thanks for your comment!
> -原始邮件-
> 发件人: "Robert Edmonds"
> 发送时间: 2017-12-15 05:40:56 (星期五)
> 收件人: "bert hubert"
> 抄送: "zuop...@cnnic.cn" , dnsop
> 主题: Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling
>
> ber
Robert Edmonds wrote:
Or, put another way, we like existing resolver implementations just
fine, we just wish there were a lot more resolver instances, and closer
to clients:-)
on it. no smiley.
--
P Vixie
___
DNSOP mailing list
DNSOP@ietf.org
http
bert hubert wrote:
> On Wed, Dec 13, 2017 at 05:36:32PM +0800, zuop...@cnnic.cn wrote:
> > so far as i know, many CDNs already use similar methods as you mentioned
> > in PowerDNS 4.1.1
> > but i think only the Authoritative Server change is not enough, support
> > on the recursive server i
From: Lanlan Pan
Date: 2017-12-13 18:25
To: Stephane Bortzmeyer
CC: zuop...@cnnic.cn; dnsop; bert hubert
Subject: Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling
Stephane Bortzmeyer 于2017年12月13日周三 下午5:58写道：
On Wed, Dec 13, 2017 at 05:31:06PM +0800,
zuop...@cnnic.cn
Stephane Bortzmeyer 于2017年12月13日周三 下午5:58写道：
> On Wed, Dec 13, 2017 at 05:31:06PM +0800,
> zuop...@cnnic.cn wrote
> a message of 130 lines which said:
>
> > (2) RFC2782 requires browser's support;
>
> Client support. This is even worse, there are much more HTTP clients
> than browsers.
>
> >
On Wed, Dec 13, 2017 at 05:31:06PM +0800,
zuop...@cnnic.cn wrote
a message of 130 lines which said:
> (2) RFC2782 requires browser's support;
Client support. This is even worse, there are much more HTTP clients
than browsers.
> Using this method, a browser has no idea about weighted AX/A
On Wed, Dec 13, 2017 at 05:36:32PM +0800, zuop...@cnnic.cn wrote:
> so far as i know, many CDNs already use similar methods as you mentioned in
> PowerDNS 4.1.1
> but i think only the Authoritative Server change is not enough, support
> on the recursive server is also very important .
> b
On Wed, Dec 13, 2017 at 09:18:23AM +0100, Stephane Bortzmeyer wrote:
> > For example, a CDN provider can’t schedule 70% of traffic to node A
> > and 30% of traffic to node B [...] adding a “weight” attribute
>
> First, the obvious question: why reinventing RFC 2782?
Implementing this worthwh
> From: bert hubert
> 3) Serve up multiple copies of the same A record, and weigh like this:
> www IN A 1.2.3.4
> www IN A 1.2.3.4
> www IN A 10.11.12.13
> And hope that record shuffling will deliver the 2:1 ratio
Same RDATA is not allowed by RFC 2181.
| 5. Resource Record Sets
|
| Each DNS Re
2017-12-13 16:43
To: Stephane Bortzmeyer
CC: zuop...@cnnic.cn; dnsop
Subject: Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling
On Wed, Dec 13, 2017 at 09:18:23AM +0100, Stephane Bortzmeyer wrote:
> > For example, a CDN provider can’t schedule 70% of traffic to node A
On Wed, Dec 13, 2017 at 09:18:23AM +0100, Stephane Bortzmeyer wrote:
> > For example, a CDN provider can’t schedule 70% of traffic to node A
> > and 30% of traffic to node B [...] adding a “weight” attribute
>
> First, the obvious question: why reinventing RFC 2782?
Implementing this worthwhile
On Wed, Dec 13, 2017 at 03:40:50PM +0800,
zuop...@cnnic.cn wrote
a message of 1343 lines which said:
> For example, a CDN provider can’t schedule 70% of traffic to node A
> and 30% of traffic to node B [...] adding a “weight” attribute
First, the obvious question: why reinventing RFC 2782?
Hi everyone,
Here’s a problem about CDN traffic scheduling. So far as I know, many
business companies use multi-CDN to speed up their websites and the CDN
providers have requirements for precise traffic scheduling especially in the
rush hour of traffic.
As CDN providers usually m
15 matches
Mail list logo
