[Yeti DNS Discuss] We need your opinion Re: New servers added to Yeti testbed
joao at bondis.org
Mon Apr 18 08:35:02 UTC 2016
> On 14 Apr 2016, at 06:51, Davey Song(宋林健) <ljsong at biigroup.cn> wrote:
> Hi colleagues,
> This is a follow-up mail about new servers added to Yeti testbed, Which need your attention and participation.
> After previous mail , BII and another existing operator applied to run additional servers. BII now got approval and ready to add three servers this weekend (one in Guangzhou via China Mobile , Two in Shanghai and Chengdu via CERNET2). After this adding, BII also consider to donate additional 5 VPSs outside of China in next step. Note that according to current policy of Yeti DNS project, these additional servers is allowed and to be reclaimed in high priority if new operator apply it. One example of additional server is dahu2.yeti.eu.org <http://dahu2.yeti.eu.org/>.
> However, it may happen that BII as a yeti server operator and one of coordinators who runs nearly 10 servers. Given that Yeti now is put under a big spotlight (WEF and IGP articles), it may introduce political and optical controversy from public,. To make everything public and transparent, the coordinators decide some kind of poll is required on this mailing list and drive it carefully by the community consensus.
> As one proposal, a careful adoption of these servers (or future servers) is to put them under the name of [a-e].yeti-dns.org <http://yeti-dns.org/> which is operator jointly by Yeti coordinator.
If I understand this correctly you are saying that servers made available by BII, whether operated directly by BII or delegated to other parties will be named as a-e.$chosen_domain, operating as anycast instances of one of those 5 letters. I think BII as the owner of that infrastructure has all the right to decide how it is operated, so no worries on that front. I would just caution everyone to really examine the perils of delegated anycast, where the same named network resources is operated by different parties as it introduces some coordination issues with a possibility for a given anycast, let’s say a.$chosen_domain, may end up with certain frequency in an inconsistent state and without a clear path for reporting and resolution.
> More specifically, TISF will manage the domain (yeti-dns.org <http://yeti-dns.org/>). BII will operator the VPS, WIDE will severed as a supervisor. And the national flag of this server presented in the website will be the country where the server located.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss