<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>Perhaps we could look down the other end of the telescope.<div class=""><br class=""></div><div class="">I'm wondering: how do we know that the RSOs are sufficiently technologically heterogenous? Perhaps the session could simply discuss differing approaches to these types of issues, highlight plusses and minuses, and continue to encourage diverse implementations. There would be no "mandate" to adopt solutions and no need to identify anything as "best." </div><div class=""><br class=""></div><div class="">Just a thought.</div><div class=""><br class=""></div><div class="">Kind regards</div><div class=""><br class=""></div><div class="">Rob</div><div class=""><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px; font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><br class="Apple-interchange-newline">--</div><div>Robert Carolina</div><div>General Counsel</div><div>Internet Systems Consortium</div><div>+447712007095 (mobile, WhatsApp, Signal)</div><div><a href="mailto:rob@isc.org" class="">rob@isc.org</a></div><div class="">My normal time zone: GMT/GMT+1</div><div class="">LinkedIn:</div><div class=""><a href="http://www.linkedin.com/in/robertcarolina/" class="">www.linkedin.com/in/robertcarolina/</a><br class=""><br class=""></div></div><div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="font-size: 11px;" class="">ISC and Internet Systems Consortium are names used by Internet Systems Consortium, Inc (a not-for-profit company) and its wholly owned subsidiary Internet Systems Corporation, both incorporated in Delaware with headquarters<span class="Apple-converted-space"> </span>in New Hampshire, USA.</span></div><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px; font-variant-caps: normal; text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="font-style: normal; font-size: 11px;" class=""><br class=""></span></div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px; font-variant-caps: normal; text-align: start; text-indent: 0px; float: none; font-style: normal; font-size: 11px; display: inline !important;" class=""><font class="">This transmission (the email and all attachments) is intended solely for the addressee(s). The contents are confidential and may be legally privileged. If you are not the intended addressee, or if this transmission has been addressed to you in error, you must not disclose, reproduce, or use the transmission or read any attachment. Delivery of this transmission to any person other than the intended recipient(s) does not waive privilege or confidentiality. If you have received this transmission in error, please reply by e-mail to explain receipt in error and then delete.</font></span></div></div></div></div></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 10 Dec 2021, at 12:38, Baojun Liu <<a href="mailto:bjliu0@gmail.com" class="">bjliu0@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I couldn't agree more with Paul's point. <div class="">How to host a root server instance is outside the scope of RSSAC.</div><div class=""><font class=""><span style="caret-color: rgb(0, 0, 0);" class="">Pre-RSOs should have independent rights to choose their DNS implementation, operating system and physical server.</span></font><span style="caret-color: rgb(0, 0, 0);" class=""> In addition, I believe that BGP routing policies are much more complex in the real world. </span><div class=""><div class=""><font class=""><span style="caret-color: rgb(0, 0, 0);" class="">From a diversity perspective, perhaps, it is not a good idea to seek out best security practices for hosting root server instances.</span></font></div><div style="caret-color: rgb(0, 0, 0);" class=""><br class=""></div></div></div><div class="">Baojun Liu.</div><div class=""><br class=""><blockquote type="cite" class=""><div class="">2021年12月2日 上午12:36，Harish Chowdhary <<a href="mailto:intern3tgovernance@gmail.com" class="">intern3tgovernance@gmail.com</a>> 写道：</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">Hi,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">Before taking the final decision, i hope we may do have a broader discussion.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Thanks,</div><div dir="auto" class="">Harish Chowdhary</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 1 Dec, 2021, 9:24 pm Paul Hoffman, <<a href="mailto:paul.hoffman@icann.org" class="">paul.hoffman@icann.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Dec 1, 2021, at 6:41 AM, Andrew McConachie <<a href="mailto:andrew.mcconachie@icann.org" target="_blank" rel="noreferrer" class="">andrew.mcconachie@icann.org</a>> wrote:<br class="">
> One work item that came up was a suggestion from maybe two years ago that the RSSAC Caucus investigate best current practices for hosting root server instances. This work would look at requirements for hosting instances including such things as physical requirements, BGP peering, etc. It would identify requirements common to most RSOs and document best practices in an RSSAC publication. The Admin Committee felt this item is out of scope for the RSSAC Caucus to consider, primarily because this is a consideration for each RSO to make independently. However, the Admin Committee also wanted to give the Caucus a chance to respond in case others disagree.<br class="">
<br class="">
Isn't the specification of instance hosting requirements per-RSO? If so, having a cross-RSO list of requirements would go against the principle of RSO independence.<br class="">
<br class="">
--Paul Hoffman_______________________________________________<br class="">
rssac-caucus mailing list<br class="">
<a href="mailto:rssac-caucus@icann.org" target="_blank" rel="noreferrer" class="">rssac-caucus@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/rssac-caucus" rel="noreferrer noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/rssac-caucus</a><br class="">
<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>
_______________________________________________<br class="">rssac-caucus mailing list<br class=""><a href="mailto:rssac-caucus@icann.org" class="">rssac-caucus@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/rssac-caucus" class="">https://mm.icann.org/mailman/listinfo/rssac-caucus</a><br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div>_______________________________________________<br class="">rssac-caucus mailing list<br class=""><a href="mailto:rssac-caucus@icann.org" class="">rssac-caucus@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/rssac-caucus<br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></body></html>