<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] NCA Assignments
- To: avri@xxxxxxx
- Subject: RE: [council] NCA Assignments
- From: Tim Ruiz <tim@xxxxxxxxxxx>
- Date: Thu, 08 Oct 2009 05:52:08 -0700
- Cc: council@xxxxxxxxxxxxxx
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
I don't agree with this process. Besides questions about randomness I
think we just need
a liitle more time. Unfortunately I will likely miss the call today.
Having some routine tests
that are taking longer than expected.
Tim
Sent from Go Daddy Mobile Mail.
> -------- Original Message --------
> Subject: Re: [council] NCA Assignments
> From: Avri Doria <avri@xxxxxxx>
> Date: Thu, October 08, 2009 7:11 am
> To: Council GNSO <council@xxxxxxxxxxxxxx>
>
> Hi,
>
> Not having heard, and proceeding to the final step,
>
> >>
> >> d. If the GNSO Council Houses and/or their respective Stakeholder
> >> Groups are unable to reach agreement, then the new, inexperienced
> >> NCA will take the non-voting Council seat and random selection will
> >> be used to assign the other two NCAs to Houses before the Council
> >> meeting on 8 October 2009.
> >
> > Note: If I need to do a random selection, I will use the Wednesday 7
> > Oct Powerball Lottery number
> > (http://www.powerball.com/powerball/pb_numbers.asp
> > ) as seed to the IETF RFC3797 random selection algorithm with the
> > names ordered alphabetic by first name.; ie. Olga, Terry. Doing so,
> > however, will result in at least one of the NCAs being given an
> > assignment that is contrary to their expressed interests.
>
> The lottery number for yesterday was: 2 20 21 38 50
>
> Using alphabetical order for the picks, the names are ordered:
>
> 1. Olga
> 2. Terry
>
> Also using alphabetical order for the assignments,
>
> 1st name picked goes to Contracted Parties House
> 2nd name picked goes to Non Contracted Parties House
>
> the RFC3797 program run (included below) picks #2 first
>
> meaning:
>
> Terry is assigned to Contracted
> Olga is assigned to Non Contracted
> Andrei, by motion, is non-voting Council seat.
>
> a.
>
> Run of the RFC3797 program
>
> Type size of pool:
> (or 'exit' to exit) 2
> Type number of items to be selected:
> (or 'exit' to exit) 1
> Approximately 1.1 bits of entropy needed.
>
> Type #1 randomness or 'end' followed by new line.
> Up to 16 integers or the word 'float' followed by up
> to 16 x.y format reals.
> 2 20 21 38 50
> 2 20 21 38 50
> Type #2 randomness or 'end' followed by new line.
> Up to 16 integers or the word 'float' followed by up
> to 16 x.y format reals.
> end
> Key is:
> 2.20.21.38.50./
> index hex value of MD5 div selected
> 1 EFC9E973E94E5D3BB70D8CDE6C0EDBCD 2 -> 2 <-
>
> Done, type any character to exit.
>
>
> On 8 Oct 2009, at 10:05, Avri Doria wrote:
>
> >
> > Hi,
> >
> > I have not heard from any of the other SG representative on the
> > subject of NCA assignment.
> >
> > I will run the lottery shortly unless I hear that people have
> > reached agreement.
> >
> > Using alphabetical order for the picks, the names will be ordered:
> >
> > 1. Olga
> > 2. Terry
> >
> > Using alphabetical order for the assignments,
> >
> > 1st name picked goes to Contracted Parties House
> > 2nd name picked goes to Non Contracted Parties House
> >
> > thanks
> >
> > a.
> >
> >
> >
> > On 8 Oct 2009, at 00:53, Avri Doria wrote:
> >
> >>
> >> Hi,
> >>
> >> Thanks Kristina.
> >>
> >> Assuming the NCSG agrees, it remains for the Contracted Parties
> >> House to agree or not to the assignment of Andrei. If they do, I
> >> assume the assignment of Olga as the non voting just falls out.
> >>
> >> I am in the UK, and about to go to sleep after a longs day's
> >> flight. I will hold off running the random selection until I hear
> >> back from folks tomorrow.
> >>
> >> a.
> >>
> >>
> >>
> >> On 7 Oct 2009, at 16:08, Rosette, Kristina wrote:
> >>
> >>> All,
> >>>
> >>> On behalf of the Commercial Stakeholder Group, I write to advise
> >>> that Terry's preference to be assigned to the Non-Contracted
> >>> Parties House is acceptable to us. I communicated this
> >>> information yesterday to the NCSG point person on the issue. As
> >>> no other SG has yet posted any assignment-related information, we
> >>> are posting to the Council list in the hope of facilitating
> >>> Council completion of the assignment process in the previously
> >>> agreed upon timeframe.
> >>>
> >>> K
> >>>
> >>
> >>
> >
> >
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|