<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Jean-Christophe,</div><div><br></div>On Dec 9, 2013, at 3:43 PM, Jean-Christophe NOTHIAS I The Global Journal <<a href="mailto:jc.nothias@theglobaljournal.net">jc.nothias@theglobaljournal.net</a>> wrote:<br><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>When Jon Postel re-rooted 7 or 8 of the 12 root servers to another 'master' (away from #13), the heads of these 7/8 servers immediately agreed to do so. What's the difference with today? </div></div></blockquote><div><br></div><div>1. Jon died.</div><div>2. Relationships between the IANA and the root server operators, the US government, and other related parties have become more well understood and/or formalized in the decade+ since the event. Back when that change of distribution master occurred, it was more of a ... collegial environment than a business environment.</div><div><br></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Does that mean such a move is not that 'difficult' to do on a technical level - not talking about everyone's reaction in the chain. But just technically, would that be 'very' difficult?</div></div></blockquote><div><br></div>Changing the master distribution server for the root zone is technically trivial (it requires changing one or two IP addresses and a shared secret in a configuration file).</div><div><br></div><div>I suspect the challenging bit will be getting universal agreement among the various actors on who the new master distribution server operator is. This will most likely be a non-technical issue.</div><div><br></div><div>Regards,</div><div>-drc</div><div><br></div><link rel="File-List" href="x-msg://52/Jovan%20Kurbalija_files/filelist.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:"Lucida Calligraphy";
panose-1:3 1 1 1 1 1 1 1 1 1;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Cambria;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
<a href="<a href="<a href="http://span.il">http://span.il</a>"><a href="http://span.il</a>">http://span.il</a></a>"><a href="http://span.il">span.il</a></a>
{mso-style-name:il;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:595.0pt 842.0pt;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style></body></html>