[Yeti DNS Discuss] 答复: [Yeti DNS Operators] FW: RFC 8483 on Yeti DNS Testbed
ljsong at biigroup.cn
Mon Oct 22 18:53:32 UTC 2018
Sorry for duplicated mails. Yeti ML is down for days.
发件人: operators [mailto:operators-bounces at lists.yeti-dns.org] 代表 Davey Song(宋林健)
发送时间: 2018年10月21日 9:23
收件人: discuss at lists.yeti-dns.org; operators at lists.yeti-dns.org
主题: [Yeti DNS Operators] FW: RFC 8483 on Yeti DNS Testbed
RFC 8483 Yeti DNS Testbed is published. Congratulations!
Thanks for all people putting efforts on this work. Yeti is not perfect, and we will continue to move it forward!
---------- Forwarded message ---------
From: <rfc-editor at rfc-editor.org>
Date: Sat, 20 Oct 2018 at 02:52
Subject: RFC 8483 on Yeti DNS Testbed
To: <ietf-announce at ietf.org>, <rfc-dist at rfc-editor.org>
Cc: <drafts-update-ref at iana.org>, <rfc-editor at rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
Title: Yeti DNS Testbed
Author: L. Song, Ed.,
Date: October 2018
Mailbox: songlinjian at gmail.com,
dliu at biigroup.com,
vixie at tisf.net,
kato at wide.ad.jp,
shane at time-travellers.org
I-D Tag: draft-song-yeti-testbed-experience-10.txt
Yeti DNS is an experimental, non-production root server testbed that
provides an environment where technical and operational experiments
can safely be performed without risk to production root server
infrastructure. This document aims solely to document the technical
and operational experience of deploying a system that is similar to
but different from the Root Server system (on which the Internet's
Domain Name System is designed and built).
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
Association Management Solutions, LLC
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss