[governance] Drop ALAC altogether???

[yehudakatz at mailinator.com]

Danny,

What happend after this? In the end, How did this pan out??
Where does NeuStar stand today???

Ref.:
http://atlarge-lists.icann.org/pipermail/alac_atlarge-lists.icann.org/2007q2/00
1021.html

[At-Large] [NA-Discuss] MOU - ICANN Obligations: Redelegation
Jacqueline A. Morris jam at jacquelinemorris.com 
Thu Jun 14 10:40:54 EDT 2007 
-------------------------------------------------------------------------------
-

Danny
My email was to inform you that it is not ONLY a NA concern, and that the
rest of the regions are working on cc issues as well. This was informational
and there is no reason to threaten the existence of the NARALO. The NA
region is part of the global AtLarge, and should be interested in working
together with the rest of the world, and not only in isolation. 

-----Original Message-----
From: Danny Younger [mailto:] 
Sent: Thursday, June 14, 2007 9:42 AM
To: jam at jacquelinemorris.com; 'NA Discuss'
Subject: RE: [NA-Discuss] MOU - ICANN Obligations: Redelegation

Hi Jacqueline,

Sorry to disagree, but the NeuStar contract with the
USG is scheduled to expire by the end of October
(posing a potential redelegation issue), and frankly
we don't have the luxury of waiting for the ALAC and
the CCNSO to come to grips with the global aspects of
the problem.  This is a timely regional issue for us
that we should be at liberty to handle by way of
positing an ICANN obligation in the MOU (which is
within our rights to request).	The RALOs exist to
deal with regional concerns.  Let us handle this
matter in our own fashion or let's just scrap the RALO
concept.

regards,
Danny


--- "Jacqueline A. Morris"
wrote:

> Hi Danny
> This is a concern in other places, and ALAC has set
> up several meetings with
> ccNSO in San Juan to discuss how we can work
> together on issues such as
> this. I don't think that it belongs in the NARALO
> MoU, but rather is a
> global issue that ALL regions should work on
> together.
> Jacqueline
> 
> -----Original Message-----
> From: Danny Younger 
> Sent: Thursday, June 14, 2007 9:11 AM
> To: NA Discuss
> Subject: [NA-Discuss] MOU - ICANN Obligations:
> Redelegation
> 
> I remain troubled by the total lack of transparency
> in
> the ccTLD redelegation process.  Has anyone ever
> seen
> a detailed redelegation request posted for
> consideration prior to action being taken by the
> Board?
> 
> The .us situation is particularly bad. On the last
> go-around ICANN bypassed the normal IANA processes
> to
> declare an "emergency redelegation" -- see
>
http://www.icann.org/announcements/announcement-19nov01.htm
> 
> I certainly don't want the relevant Internet
> community
> being kept in the dark should the delegation of the
> .us namespace become an issue.
> 
> I would ask that the NARALO MOU stipulate that ICANN
> has the obligation to inform the NARALO upon the
> receipt of any relevant ccTLD redelegation request
> (.us or .ca) so that community input may be provided
> (as per RFC 1591:  "it is also appropriate for
> interested parties to have some voice in selecting
> the
> designated manager.")
>
___________________________________________________________________
>
> NA-Discuss mailing list
> NA-Discuss at atlarge-lists.icann.org
>
http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.icann.
org
> ---
> Draft MoU with ICANN:
> http://www.icannwiki.org/NA_RALO_MOU
> 
> Draft Operating Principles:
> http://www.icannwiki.org/NA_RALO_OP
> 
> Draft Code of Conduct:
> http://www.icannwiki.org/NARALO_Code_of_Conduct
> ---
> 
> No virus found in this outgoing message.
> Checked by AVG Free Edition. 
> Version: 7.5.472 / Virus Database: 269.8.15/848 -
> Release Date: 6/13/2007
> 12:50 PM
 
___________________________________________________________________
____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, send any message to:
     governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
     http://lists.cpsr.org/lists/info/governance