<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Narelle,</div><div class=""><br class=""></div><div class="">I\u2019m unclear on why we would put this in part 0. These points are already reflected in paragraphs 2018, 2033, and 3047 of the proposal.</div><div class=""><br class=""></div><div class="">Alissa</div><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 19, 2015, at 10:11 AM, Narelle Clark <<a href="mailto:narelle.clark@accan.org.au" class="">narelle.clark@accan.org.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class=""><div class="">
<div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Proposed Text:</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><font size="2" dir="auto" class=""><div class="PlainText"> The additional domains under .arpa, such as \u201cin-addr.arpa\u201d and \u201cip6.arpa\u201d, do not occur in the root zone. The provision of these services are solely under the purview of the IAB as the authority of the .ARPA registry and therefore not included in the transition as existing systems will continue to apply.</div><div class="PlainText"><br class=""></div><div class="PlainText">Include references:<br class=""><a href="https://www.iab.org/documents/correspondence-reports-documents/docs200" target="_BLANK" class="">https://www.iab.org/documents/correspondence-reports-documents/docs200</a>0/iab-statement-on-infrastructure-domain-and-subdomains-may-2000/<br class=""><br class=""></div><div class="PlainText"> RFC 3172 <<a href="https://tools.ietf.org/html/rfc3172" target="_BLANK" class="">https://tools.ietf.org/html/rfc3172</a>> defines the Management Guidelines & Operational Requirements for .ARPA.</div></font><br class=""></div><div dir="auto" class="">-----8 <---------8 <-------------</div><div dir="auto" class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><div style="font-size: 100%;" dir="auto" class=""><span style="font-size: small;" class=""> I had suggested this go into the section 'Workability' because it should go with the piece on the RZM.</span></div><font size="2" dir="auto" class=""><div class="PlainText"><br class=""> I now think that both of those paragraphs should go in under the heading 'Completeness and Clarity' at the end. These are parts that are not addressed in the combined proposal and everyone is happy that they aren't.<br class=""></div><div class="PlainText"><br class=""></div><div class="PlainText">Both seem more relevant there.</div><div class="PlainText"><br class=""></div><div class="PlainText"><br class=""></div><div class="PlainText">Narelle </div><div class="PlainText"></div></font></div></div></div><div id="composer_signature" class=""></div></div>_______________________________________________<br class="">Internal-cg mailing list<br class=""><a href="mailto:Internal-cg@mm.ianacg.org" class="">Internal-cg@mm.ianacg.org</a><br class="">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org<br class=""></div></blockquote></div><br class=""></body></html>