<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="">Then I will continue to smack them for it.<div class=""><br class=""></div><div class="">People and the government, especially, should use English (or whatever language is appropriate) as it exists and don’t overload terms with unconventional definitions just to avoid learning what they actually mean. It’s bad form, confusing, and disruptive to meaningful progress.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 19, 2015, at 10:40 , David Conrad <<a href="mailto:drc@virtualized.org" class="">drc@virtualized.org</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; -webkit-line-break: after-white-space;" class="">Owen,<div class=""><br class=""></div><div class="">In the Affirmation of Commitments, NTIA decided to redefine the term "DNS" as:</div><div class=""><br class=""></div><div class="">"For the purposes of this Affirmation the Internet's domain name and addressing system (DNS) is defined as: domain names; Internet protocol addresses and autonomous system numbers; protocol port and parameter numbers. ICANN coordinates these identifiers at the overall level, consistent with its mission."</div><div class=""><br class=""></div><div class="">(See footnote 1 of <font color="#4787ff" class=""><u class=""><a href="http://www.ntia.doc.gov/files/ntia/publications/affirmation_of_commitments_2009.pdf" class="">http://www.ntia.doc.gov/files/ntia/publications/affirmation_of_commitments_2009.pdf</a>)</u></font></div><div class=""><font color="#4787ff" class=""><u class=""><br class=""></u></font></div><div class="">Despite the confusions this obviously causes (as indicated by your note), they continue to use their definition of "the DNS" in these sorts of announcements.</div><div class=""> </div><div class="">Regards,</div><div class="">-drc</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Aug 19, 2015, at 9:50 AM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.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; -webkit-line-break: after-white-space;" class="">The first thing I see in this that sets off alarm bells is the first paragraph. I sincerely hope NTIA realizes that there is much more at stake here than just DNS.<div class=""><br class=""></div><div class="">While I realize that DNS and more specifically domain names are the cash cow tail that wags the IANA dog, if we are not careful in this transition process to make sure that IETF and Numbers retain their independence and an independent control of their relationship with the IANA functions provider, including the ability to select a new IANA functions provider for their purposes, thins can get very bad for the internet very quickly.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Aug 17, 2015, at 23:19 , Mwendwa Kivuva <<a href="mailto:Kivuva@transworldafrica.com" class="">Kivuva@transworldafrica.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div style="font-family: Calibri, sans-serif; font-size: 14px;" class="">Here is an interesting development from the US NTIA on the IANA transition to the global multistakeholder community. A summary is NTIA will extend its contract with ICANN for at least a year to September 2016 and a possibility of a 3 year extension to September 2018.</div><div style="font-family: Calibri, sans-serif; font-size: 14px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px;" class=""> <a href="http://www.ntia.doc.gov/blog/2015/update-iana-transition" target="_blank" class="">http://www.<span class="il">ntia</span>.doc.gov/<span class="il">blog</span>/2015/<span class="il">update</span>-iana-transition</a>. </div><div style="font-family: Calibri, sans-serif; font-size: 14px;" class=""><br class=""></div><div style="font-family: Calibri, sans-serif; font-size: 14px;" class=""><h1 style="font-size: large; margin: 0px auto; line-height: 1.2em; color: rgb(16, 40, 70); font-family: Arial, Helvetica, sans-serif;" class="">An <span class="il">Update</span> on the IANA Transition</h1><div style="font-family: Arial, Helvetica, sans-serif; font-size: 14.3999996185303px; line-height: 21.5999984741211px;" class=""><div style="margin: 0.5em 0px 1em; padding-bottom: 1em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(244, 217, 69);" class=""><span style="font-size: 0.8em; font-style: italic;" class="">August 17, 2015 by Assistant Secretary for Communications and Information and <span class="il">NTIA</span> Administrator Lawrence E. Strickling</span><div class=""><img alt="Assistant Secretary for Communications and Information and NTIA Administrator Lawrence E. Strickling" title="Assistant Secretary for Communications and Information and NTIA Administrator Lawrence E. Strickling" width="165" height="198" style="border: 0px; float: left; margin: 10px 15px 0pt 0pt;" class=""></div><div style="margin: 0.5em 0px;" class=""><div class=""><div class=""></div></div><p style="line-height: 1.2em;" class="">The Internet’s global multistakeholder community has made tremendous progress in its work to develop a proposal to transition the historic stewardship role <span class="il">NTIA</span> has played related to Internet’s domain name system (DNS).</p><p style="line-height: 1.2em;" class="">When we <a href="http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition-key-internet-domain-name-functions" target="_blank" style="color: rgb(0, 90, 140); text-decoration: none; font-weight: bold;" class="">announced</a> our intent in March 2014 to complete the privatization of the DNS, we noted that the base period of our contract with ICANN to perform technical functions related to the DNS, known as the IANA functions, expired on September 30, 2015. However, it has become increasingly apparent over the last few months that the community needs time to complete its work, have the plan reviewed by the U.S. Government and then implement it if it is approved.</p><p style="line-height: 1.2em;" class="">Accordingly, in May we asked the groups developing the transition documents how long it would take to finish and implement their proposals. After factoring in time for public comment, U.S. Government evaluation and implementation of the proposals, the community estimated it could take until at least September 2016 to complete this process. In response to their feedback, we informed Congress on Friday that we plan to extend our IANA contract with ICANN for one year to September 30, 2016. Beyond 2016, we have options to extend the contract for up to three additional years if needed.</p><p style="line-height: 1.2em;" class="">This one-year extension will provide the community with the time it needs to finish its work. The groups are already far along in planning the IANA transition and are currently taking comments on their IANA transition proposals. As we indicated in a recent <a href="http://www.ntia.doc.gov/files/ntia/publications/fr_iana_transition_comment_notice_08102015.pdf" target="_blank" style="color: rgb(0, 90, 140); text-decoration: none; font-weight: bold;" class="">Federal Register notice</a>, we encourage all interested stakeholders to engage and weigh in on the proposals.</p><p style="line-height: 1.2em;" class="">In preparation for the implementation phase of the IANA stewardship transition, <span class="il">NTIA</span> also asked Verisign and ICANN to submit a proposal detailing how best to remove <span class="il">NTIA</span>’s administrative role associated with root zone management, which the groups working on the transition were not asked to address. We asked Verisign and ICANN to submit a proposal detailing how best to do this in a manner that maintains the security, stability and resiliency of the DNS. Under the current root zone management system, Verisign edits and distributes the root zone file after it has received authorization to do so from <span class="il">NTIA</span>. Verisign and ICANN have developed a <a href="http://www.ntia.doc.gov/files/ntia/publications/root_zone_administrator_proposal-relatedtoiana_functionsste-final.pdf" target="_blank" style="color: rgb(0, 90, 140); text-decoration: none; font-weight: bold;" class="">proposal</a> that outlines a technical plan and testing regime for phasing out the largely clerical role <span class="il">NTIA</span> currently plays in this process. The testing will occur in a parallel environment that will not disrupt the current operation of the root zone management system.</p><p style="line-height: 1.2em;" class="">These developments will help ensure that the IANA transition will be done in a manner that preserves the security and stability of the DNS.</p></div></div></div></div></div><div class="gmail_extra" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class="">______________________<br class="">Mwendwa Kivuva, Nairobi, Kenya<br class=""><br class="">"There are some men who lift the age they inhabit, till all men walk on higher ground in that lifetime." - Maxwell Anderson<br class=""><div class=""><br class=""></div></div></div></div></div></div><br class=""><div class="gmail_quote">On 3 August 2015 at 08:57, Mwendwa Kivuva<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:Kivuva@transworldafrica.com" target="_blank" class="">Kivuva@transworldafrica.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div dir="ltr" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">Greetings,</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">Here is an update on the IANA stewardship proposal as it pertains the numbering community. Community feedback is highly appreciated.</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">COMMUNITY ENGAGEMENT:</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">The CRISP team has been exploring the best way of informing and engaging the numbering community as it pertains to the IANA Stewardship transition. In that regard, an easy to understand info-graphic has been released for the community. The info-graphic is available here: </span><a rel="nofollow" href="https://www.nro.net/wp-content/uploads/Number_Community_Proposal_Overview.pdf" target="_blank" style="color: rgb(102, 17, 204); font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">https://www.nro.net/wp-content/uploads/Number_Community_Proposal_Overview.pdf</a>. The NRO website has also been enhanced to make it more intuitive easy to navigate. Check it here <a href="https://www.nro.net/nro-and-internet-governance/iana-oversight" target="_blank" class="">https://www.nro.net/nro-and-internet-governance/iana-oversight</a><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">On 8 July, the Africa Domain Name System Forum 2015 held in Nairobi had a discussion on the IANA Stewardship Transition. </span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">REVIEW COMMITTEE CHARTER:</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">NRO developed the Review Committee Charter. The RIRs community was given an opportunity to give feedback on the charter. The CRISP team did not find any inconsistency between the Review Committee Charter and the numbering community proposal.</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">SLA</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">The NRO legal team drafted the SLA that is to be signed between the RIRs and the IANA functions operator. This arrangement will directly reflect and</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">enforce the IANA Numbering Services Operator’s accountability to the Internet Number Community. The community gave its feedback on the SLA. The CRISP team also analysed the SLA for consistency with the numbering community proposal. The SLA is available here </span><a rel="nofollow" href="https://www.nro.net/wp-content/uploads/Numbers-SLA-1.0.pdf" target="_blank" style="color: rgb(102, 17, 204); font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">https://www.nro.net/wp-content/uploads/Numbers-SLA-1.0.pdf</a><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">IPR ISSUE - </span><a rel="nofollow" href="http://iana.org/" target="_blank" style="color: rgb(102, 17, 204); font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">IANA.org</a><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""> and IANA trademark</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">The numbering community proposed the IPRs related to the IANA function be held by an independent entity, preferably the IETF Trust. The other two proposals have not contradicted this view but CWG proposal has not expressly stated the position for the names community. ICG has requested CWG to clarify their position on the IPR issue. CWG are still deliberating on it, and have suggested to conduct a stress test on the whole IPR issue. There are 3 trademarks involved: (i) "Internet Assigned Numbers Authority," (ii) "IANA", and (iii) the IANA Logo, which consists of IANA in stylized letters plus Internet Assigned Numbers Authority.</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">The Internal ICG mailing list has this statement allegedly from the ICANN board "The board wishes to reassure the community that in the event any of the IANA functions are transferred away from ICANN, appropriate rights to use the intellectual property associated with the IANA functions will be granted without delay to the new operator or to an entity the operational communities unanimously designate." </span><a rel="nofollow" href="http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/2015-July/000814.html" target="_blank" style="color: rgb(102, 17, 204); font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/2015-July/000814.html</a><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">THE TRANSITION AT US HOUSE OF REPRESENTATIVES. </span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">On June 23, the US House of Representatives passed the DOTCOM Act, a bill that provides for congressional oversight of a U.S. government handoff of oversight of the IANA functions. One takeaway from congressional hearings on the handoff was that both sides agreed that the handoff of the IANA functions from oversight by the National Telecommunications & Information Administration to a multistakeholder model wouldn't be ready by the Sept. 30, 2015 expiration date of the current contract with ICANN. </span><a rel="nofollow" href="http://fcw.com/articles/2015/06/23/house-it-votes.aspx" target="_blank" style="color: rgb(102, 17, 204); font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">http://fcw.com/articles/2015/06/23/house-it-votes.aspx</a><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">ICG PROGRESS</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">-----</span><br style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><span style="font-family: 'Roboto Slab', 'Times New Roman', serif; font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">The IANA stewardship transition Coordination Group (ICG) has combined the proposals from the numbering, protocol parameters , and names community into one consolidated proposal. The three respective communities are expected to study the document for compatibility and interoperability and comment on any (in)consistencies and realignments with each other, and ensure the proposal meet the NTIA requirements. The proposal is out for public comment from July 31 to September 8, 2015.</span><div class=""><font color="rgba(0, 0, 0, 0.8)" face="Roboto Slab, Times New Roman, serif" class=""><span style="font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font color="#ba0000" face="Roboto Slab, Times New Roman, serif" class=""><span style="font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><div class="">Specific questions about which the ICG is seeking comment are listed below. </div><div class=""><br class=""></div><div class="">Questions Concerning the Proposal as a Whole</div><div class=""><br class=""></div><div class="">1. Completeness and clarity: Is the combined proposal complete? Each of the operational community proposals contains aspects to be completed in the future when the proposal is implemented. Is the combined proposal specified in sufficient detail such that it can be evaluated against the NTIA criteria?</div><div class="">2. Compatibility and interoperability: Do the operational community proposals work together in a single proposal? Do they suggest any incompatible arrangements where compatibility appears to be required? Is the handling of any conflicting overlaps between the functions resolved in a workable manner?</div><div class="">3. Accountability: Do the operational community proposals together include appropriate and properly supported independent accountability mechanisms for running the IANA functions? Are there any gaps in overall accountability under the single proposal?</div><div class="">4. Workability: Do the results of any tests or evaluations of workability that were included in the operational community proposals conflict with each other or raise possible concerns when considered in combination?</div><div class=""><br class=""></div><div class="">Questions Concerning NTIA Criteria</div><div class=""><br class=""></div><div class="">5. Do you believe the proposal supports and enhances the multistakeholder model? If yes, please explain why. If not, please explain why and what proposal modifications you believe are necessary.</div><div class="">6. Do you believe the proposal maintains the security, stability, and resiliency of the DNS? If yes, please explain why. If not, please explain why and what proposal modifications you believe are necessary.</div><div class="">7. Do you believe the proposal meets the needs and expectations of the global customers and partners of the IANA services? If yes, please explain why. If not, please explain why and what proposal modifications you believe are necessary. Please indicate if you are a customer or partner of the IANA services.</div><div class="">8. Do you believe the proposal maintains the openness of the Internet? If yes, please explain why. If not, please explain why and what proposal modifications you believe are necessary.</div><div class="">9. Do you have any concerns that the proposal is replacing NTIA’s role with a government-led or inter-governmental organization solution? If yes, please explain why and what proposal modifications you believe are necessary. If not, please explain why.</div><div class="">10. Do you believe that the implementation of the proposal will continue to uphold the NTIA criteria in the future? If yes, please explain why. If not, please explain why and what proposal modifications you believe are necessary.</div><div class=""><br class=""></div><div class="">Questions Concerning ICG Report and Executive Summary</div><div class=""><br class=""></div><div class="">11. Do you believe the ICG report and executive summary accurately reflect all necessary aspects of the overall proposal? If not, please explain what modifications you believe are necessary.</div><div class=""><br class=""></div><div class="">General Questions</div><div class=""><br class=""></div><div class="">12. Do you have any general comments for the ICG about the proposal?</div><div class=""><br class=""></div><div class="">The full announcement and more information can be found at the ICG's website: <a href="https://www.ianacg.org/calls-for-input/combined-proposal-public-comment-period/" target="_blank" class="">https://www.ianacg.org/calls-for-input/combined-proposal-public-comment-period/</a></div></span></font></div><div class=""><font color="rgba(0, 0, 0, 0.8)" face="Roboto Slab, Times New Roman, serif" class=""><span style="font-size: 14px; line-height: 19px; white-space: pre-wrap;" class=""><br class=""></span></font></div><div class=""><font color="rgba(0, 0, 0, 0.8)" face="Roboto Slab, Times New Roman, serif" class=""><span style="font-size: 14px; line-height: 19px; white-space: pre-wrap;" class="">Sincerely,<br clear="all" class=""></span></font><div class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">______________________<br class="">Mwendwa Kivuva, Nairobi, Kenya</div><div dir="ltr" class="">For the AFRINIC CRISP TEAM<br class=""><br class="">"There are some men who lift the age they inhabit, till all men walk on higher ground in that lifetime." - Maxwell Anderson<br class=""><div class=""><br class=""></div></div></div></div></div></div></div></div></blockquote></div><br class=""></div><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">rpd mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><a href="mailto:rpd@afrinic.net" class="">rpd@afrinic.net</a></span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="https://lists.afrinic.net/mailman/listinfo/rpd" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">https://lists.afrinic.net/mailman/listinfo/rpd</a></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">rpd mailing list<br class=""><a href="mailto:rpd@afrinic.net" class="">rpd@afrinic.net</a><br class=""><a href="https://lists.afrinic.net/mailman/listinfo/rpd" class="">https://lists.afrinic.net/mailman/listinfo/rpd</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>