<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Thank you. I find the structure extremely sound and the process well designed. It could even be mimicked and adapted here and, I believe, make an improvement. Certainly it is a good example of social/governmental architecture.</DIV>
<DIV> </DIV>
<DIV>Now the hard test: does it actually work and what results?</DIV>
<DIV> </DIV>
<DIV>To this end I am reviewing input and output. Is or are there any sterling example(s)?</DIV>
<DIV> </DIV>
<DIV>My method is to go to Draft Docs. -- and work backward into discussion.</DIV>
<DIV> </DIV>
<DIV><A href="http://www.ripe.net/ripe/draft-documents/archive/index.html">http://www.ripe.net/ripe/draft-documents/archive/index.html</A> to</DIV>
<DIV><A href="http://www.ripe.net/ripe/maillists/archives/address-policy-wg/2009/index-auth.html">http://www.ripe.net/ripe/maillists/archives/address-policy-wg/2009/index-auth.html</A></DIV>
<DIV> </DIV>
<DIV>I must say like most policy/technical lists the categories help ie auth/sub/chron and these seem well kept but as usual us authors seldom stick to a well designed subject line ;-(<BR><BR>--- On <B>Sun, 1/24/10, <SPAN><SPAN>Fearghas</SPAN></SPAN> McKay <I><fm-lists@st-kilda.org></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Fearghas McKay <fm-lists@st-kilda.org><BR>Subject: Re: [governance] Re: Openess at ApNic<BR>To: governance@lists.cpsr.org<BR>Date: Sunday, January 24, 2010, 1:32 AM<BR><BR>
<DIV class=plainMail><BR>On 23 Jan 2010, at 23:30, Eric Dierker wrote:<BR><BR>> Thanks, I am studying and learning much about this and RiP e .<BR><BR>You should be aware that there is a difference between RIPE and the RIPE NCC.<BR><BR>RIPE is the community.<BR><BR>RIPE NCC - RIPE Network Coordination Centre, is the executive organisation that implements the policies that are set by the RIPE community. It is a membership organisation, and sets the fees for the implemented policies on a cost recovery basis. It does not set policy. It provides the organisation for the RIPE meetings.<BR><BR>Anyone can participate in the RIPE and the policy making process, it is open to all. The decision making process is done via mailing lists, not at face to face meetings, although meetings are used to enable discussion. The meetings are webcast, with scribes to feedback external questions. I would say it is a fine example of a bottom up organisation, but I might be
biased as a WG Chair :-)<BR><BR>All the other RIRs have a similar split between policy making and NCC/NIC/operations organisation, however I think that only RIPE has the separate naming convention for the two groups.<BR><BR>HTH<BR><BR> f<BR><BR><BR>____________________________________________________________<BR>You received this message as a subscriber on the list:<BR> <A href="http://us.mc839.mail.yahoo.com/mc/compose?to=governance@lists.cpsr.org" ymailto="mailto:governance@lists.cpsr.org">governance@lists.cpsr.org</A><BR>To be removed from the list, send any message to:<BR> <A href="http://us.mc839.mail.yahoo.com/mc/compose?to=governance-unsubscribe@lists.cpsr.org" ymailto="mailto:governance-unsubscribe@lists.cpsr.org">governance-unsubscribe@lists.cpsr.org</A><BR><BR>For all list information and functions, see:<BR> <A href="http://lists.cpsr.org/lists/info/governance"
target=_blank>http://lists.cpsr.org/lists/info/governance</A><BR><BR>Translate this email: <A href="http://translate.google.com/translate_t" target=_blank>http://translate.google.com/translate_t</A><BR></DIV></BLOCKQUOTE></td></tr></table>