On 3 Sep 2014, at 13:21, joel jaeggli <joe...@bogus.com> wrote: > On 9/3/14 10:01 AM, David Conrad wrote: > >> On Sep 3, 2014, at 8:42 AM, Guangqing Deng <dengguangq...@cnnic.cn> >> wrote: >>> From RFC1034 section 4.1, it seems that the way used for improving >>> the redundancy and resilience of DNS system is to increase DNS >>> servers. I agree that for the performance of the DNS system, the >>> redundancy and resilience are the first goal and low latency is the >>> second goal. Usually, the first goal mainly depends on the DNS >>> server deployment policy (such as the total number and geographical >>> distribution of DNS severs) and the second goal relates to not only >>> the DNS server deployment policy but also the method used for DNS >>> clients selecting the best DNS server like any cast. > > anycast is not a selection mechanism employed by a client. it is the > network that determines the catchment area served by a given anycast > instance.
RFC4786 may be a useful reference.
(and I remember when that document was progressing through the IESG there was
confusion over the word "catchment"; we inserted a definition to make the use
of that word clearer, pasted here since Joel used it too.)
Catchment: in physical geography, an area drained by a river, also
known as a drainage basin. By analogy, as used in this document,
the topological region of a network within which packets directed
at an Anycast Address are routed to one particular node.
Joe
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
