<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<style>@font-face {
font-family: "Courier New";
}@font-face {
font-family: "Wingdings";
}@font-face {
font-family: "Calibri";
}@font-face {
font-family: "Cambria";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0cm 0cm 10pt; font-size: 12pt; font-family: "Times New Roman"; }p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph { margin: 0cm 0cm 10pt 36pt; font-size: 12pt; font-family: "Times New Roman"; }p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst { margin: 0cm 0cm 0.0001pt 36pt; font-size: 12pt; font-family: "Times New Roman"; }p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle { margin: 0cm 0cm 0.0001pt 36pt; font-size: 12pt; font-family: "Times New Roman"; }p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast { margin: 0cm 0cm 10pt 36pt; font-size: 12pt; font-family: "Times New Roman"; }div.Section1 { page: Section1; }ol { margin-bottom: 0cm; }ul { margin-bottom: 0cm; }</style>
<p class="MsoNormal"><span style="font-family: Calibri;">Thank you
Walu and McTim<br>
<br>
This will be a good opportunity for Kenyan stakeholders, (we are
very active in
both ICANN and IGF spaces) to input and wish to encourage more
comments online
as well as during the meeting on Tuesday.</span><span
style="font-family: Calibri;"> </span></p>
<p class="MsoNormal"><span style="font-family: Calibri;">Comments
are
requested along these 6 areas/aspects:</span><span
style="font-family: Calibri;"></span></p>
<p class="MsoListParagraphCxSpFirst" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">In
light of technology changes and market developments, should the
IANA functions
continue to be treated as interdependent technical functions?
For example, does
the coordination of the assignment of technical protocol
parameters need to be
done by the same entity that administers certain
responsibilities as sociated
with root zone management? Please provide specific information
to support why
or why not, taking into account security and stability issues.</span><span
style="font-family: Calibri;"></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">The
performance of the IANA functions often relies upon the policies
and procedures
developed by a variety of entities within the Internet technical
community such
as the IETF, the RIRs and ccTLD operators. Should the IANA
functions contract
include references to these entities, the policies they develop
and instructions
that the contractorfollow the policies? Please provide specific
information as
to why or why not. If yes, please provide language you believe
accurately
captures these relationships. </span><span style="font-family:
Calibri;"></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">previously
raised by some governments and ccTLD operators and the need to
ensure the
stability of and security of the DNS, are there changes that
could be made to how
root zone management requests for ccTLDs are processed? Please
provide specific
information as to why or why not. If yes, please provide
specific suggestions.</span><span style="font-family: Calibri;"></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">-Broad
performance metrics and reporting are currently required under
the contract.\7\
Are the current metrics and reporting requirements sufficient?
Please provide
specific information as to why or why not. If not, what specific
changes should
be made?</span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">Can
process improvements or performance enhancements be made to the
IANA functions
contract to better reflect the needs of users of the IANA
functions to improve
the overall customer experience? Should mechanisms be employed
to provide
formalized user input and/or feedback, outreach and coordination
with the users
of the IANA functions? Is additional information related to the
performance and
administration of the IANA functions needed in the interest of
more
transparency? Please provide specific information as to why or
why not.</span><span style="font-family: Calibri;"></span></p>
<p class="MsoListParagraphCxSpLast" style="margin: 0.1pt 0cm
0.0001pt 36pt; text-align: justify; text-indent: -18pt;"><span
style="font-family: Symbol;"><span style="">·<span style="font:
7pt "Times New Roman";"> </span></span></span><span
style="font-family: Calibri;">Should
additional security considerations and/or enhancements be
factored into
requirements for the performance of the IANA functions? Please
provide specific
information as to why or why not. If additional security
considerations should
be included, please provide specific suggestions.</span><span
style="font-family: Calibri;"></span></p>
<p class="MsoNormal" style="margin: 0.1pt 0cm 0.0001pt; text-align:
justify;"><span style="font-family: Calibri;"> <br>
best</span> Alice, <br>
<br>
<span style="font-family: Calibri;"></span><span
style="font-family: Calibri;"></span></p>
<p class="MsoNormal"><span style="font-family: Calibri;"> </span></p>
<blockquote cite="mid:528019.61914.qm@web161718.mail.bf1.yahoo.com"
type="cite">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top">--- On <b>Sat,
3/26/11, McTim <i><a class="moz-txt-link-rfc2396E" href="mailto:dogwallah@gmail.com"><dogwallah@gmail.com></a></i></b>
wrote:
<div><br>
</div>
<div><a moz-do-not-send="true" rel="nofollow"
target="_blank"
href="http://www.ntia.doc.gov/comments/110207099-1099-01/attachments/ACF2EF.pdf">http://www.ntia.doc.gov/comments/110207099-1099-01/attachments/ACF2EF.pdf</a> </div>
<div><br>
</div>
@McTim,<br>
<br>
True, ICANN says more else the same thing; but think about
it, maybe ICANN says what we ask it to say and they
reflect our thoughts and aspirations. That is the nature
of a multistakeholder, bottom up organisation that ICANN
is.<br>
<br>
walu.<br>
nb: also refer to my original message and you will see
that I never claimed exclusive rights to these comments. I
simply digested the same for the local community.<br>
<br>
--- On <b>Sat, 3/26/11, McTim <i><a class="moz-txt-link-rfc2396E" href="mailto:dogwallah@gmail.com"><dogwallah@gmail.com></a></i></b>
wrote:<br>
<blockquote style="border-left: 2px solid rgb(16, 16,
255); margin-left: 5px; padding-left: 5px;"><br>
From: McTim <a class="moz-txt-link-rfc2396E" href="mailto:dogwallah@gmail.com"><dogwallah@gmail.com></a><br>
Subject: Re: [kictanet] STAKEHOLDERS COMMENTS ON IANA
FUNCTIONS-my comments<br>
To: "Walubengo J" <a class="moz-txt-link-rfc2396E" href="mailto:jwalu@yahoo.com"><jwalu@yahoo.com></a><br>
Cc: "KICTAnet KICTAnet"
<a class="moz-txt-link-rfc2396E" href="mailto:kictanet@lists.kictanet.or.ke"><kictanet@lists.kictanet.or.ke></a><br>
Date: Saturday, March 26, 2011, 5:04 PM<br>
<br>
<div id="yiv1843133424"><br>
<br>
<div class="yiv1843133424gmail_quote">On Sat, Mar 26,
2011 at 4:42 PM, Walubengo J <span dir="ltr"><<a
moz-do-not-send="true" rel="nofollow"
ymailto="mailto:jwalu@yahoo.com" target="_blank"
href="/mc/compose?to=jwalu@yahoo.com">jwalu@yahoo.com</a>></span>
wrote:<br>
<blockquote class="yiv1843133424gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px
solid rgb(204, 204, 204); padding-left: 1ex;">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top">Wambua,<br>
<br>
I wont make it for the meeting but plse
register my comment on the above as
follows:<br>
<br>
1. No single government should have
oversight powers over <a
moz-do-not-send="true" rel="nofollow"
target="_blank"
href="http://en.wikipedia.org/wiki/Internet_Assigned_Numbers_Authority">IANA
</a>functions(core operational functions
of the Internet).<br>
</td>
</tr>
</tbody>
</table>
</blockquote>
<div><br>
</div>
<div>That's what the original White Paper
said...it's just 20 years later now.</div>
<div><br>
</div>
<div><br>
</div>
<div>NB: IANA functions are administrative, not
operational.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="yiv1843133424gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px
solid rgb(204, 204, 204); padding-left: 1ex;">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font: inherit;" valign="top">2.
It is therefore best that the US
government relinquishes oversight powers
over the IANA function in a progressive
manner i.e. by moving its relationship
with <a moz-do-not-send="true"
rel="nofollow" target="_blank"
href="http://www.icann.org/">ICANN</a>
over IANA function from the current
"Contractual" agreement to a "Cooperation"
agreement locally known as an <a
moz-do-not-send="true" rel="nofollow"
target="_blank"
href="http://en.wikipedia.org/wiki/Memorandum_of_agreement">MOA</a>
and eventually an non-legal agreement
sometimes known as an <a
moz-do-not-send="true" rel="nofollow"
target="_blank"
href="http://en.wikipedia.org/wiki/Memorandum_of_understanding">MoU</a></td>
</tr>
</tbody>
</table>
</blockquote>
<div><br>
</div>
<div>that's what ICANN says too:</div>
<div><br>
</div>
<div><a moz-do-not-send="true" rel="nofollow"
target="_blank"
href="http://www.ntia.doc.gov/comments/110207099-1099-01/attachments/ACF2EF.pdf">http://www.ntia.doc.gov/comments/110207099-1099-01/attachments/ACF2EF.pdf</a> </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
-- <br>
Cheers,<br>
<br>
McTim<br>
"A name indicates what we seek. An address indicates
where it is. A route indicates how we get there." Jon
Postel<br>
</div>
</blockquote>
</td>
</tr>
</tbody>
</table>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
kictanet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>
<a class="moz-txt-link-freetext" href="http://lists.kictanet.or.ke/mailman/listinfo/kictanet">http://lists.kictanet.or.ke/mailman/listinfo/kictanet</a>
This message was sent to: <a class="moz-txt-link-abbreviated" href="mailto:alice@apc.org">alice@apc.org</a>
Unsubscribe or change your options at <a class="moz-txt-link-freetext" href="http://lists.kictanet.or.ke/mailman/options/kictanet/alice%40apc.org">http://lists.kictanet.or.ke/mailman/options/kictanet/alice%40apc.org</a>
</pre>
</blockquote>
<br>
</body>
</html>