<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Colleagues<br>
<br>
I suggest that we have reviewers for each proposal that include
technical savvy and less technical oriented reviewers - to make sure
that technical nuances may be appropriately considered? The next
two weeks are tight but I can volunteer where needed. May I suggest
that we need to spread out across all the submissions... Names
seems to have the greatest gravitational attraction for obvious
reasons...<br>
<br>
Joe<br>
<br>
<div class="moz-cite-prefix">On 1/6/2015 6:45 PM, Jari Arkko wrote:<br>
</div>
<blockquote
cite="mid:6BBFE574-CE11-4CD8-9840-B767ACC4A95F@piuha.net"
type="cite">
<pre wrap="">Narelle,
That there is some amount of reading to do is probably a feature in all proposals,
at least if they point to existing mechanisms described elsewhere or describe
new mechanisms with a reasonable level of detail.
No one said the ICG job was going to be easy :-) And while I’d probably classify
our task more in the category of ensuring the proposals fulfil the criteria and can
fit to the rest of the system than determining if they are satisfactory to us, in any case
there will be some reading and proposal-understanding ahead all of us. Unless
the rest of you already understand everything, I certainly do not...
If there’s anything that the IETF team can do to help provide information
or explain wrt our arrangements, let us know.
Jari
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Internal-cg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a>
</pre>
</blockquote>
<br>
</body>
</html>