Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling

[[e-mail]]

> From: bert hubert <[e-mail]>
> 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 Resource Record (RR) has a label, class, type, and data.  It
|   is meaningless for two records to ever have label, class, type and
|   data all equal - servers should suppress such duplicates if
|   encountered.  It is however possible for most record types to exist
|   with the same label, class and type, but with different data.  Such a
|   group of records is hereby defined to be a Resource Record Set
|   (RRSet).

> 1) Get browsers to honour RFC 2782

  RFC 6763 DNS-Based Service Discovery shows "_http._tcp" service usage.

> From: "[e-mail]" <[e-mail]>
> (1) RFC2782 does not solve the problem of using multi-CDN  (multiple CNAME cannot coexist);
>     here we can use multipile weighted CNMAEXs (need to coexist with CNAME) to accomplish this;
>     besides, weighted CNAMEXs can control traffic ratio among several CDN providers;

  You can add many SRV RRs. (merge SRV RRs from multi-CDN).

> (2) RFC2782 requires browser's support;
>     Using this method, a browser has no idea about weighted AX/AAAAXs. 
>     It requires no change of browsers.

  Softwares that support DNS-SD may support _http._tcp.

--
Kazunori Fujiwara, JPRS <[e-mail]>