NCSG-DISCUSS Archives

NCSG-Discuss

NCSG-DISCUSS@LISTSERV.SYR.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Milton L Mueller <[log in to unmask]>
Reply To:
Milton L Mueller <[log in to unmask]>
Date:
Mon, 25 Jan 2010 16:54:36 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Mary:
FYI, an attempt to summarize so you can perhaps make up your own mind:

> > Currently the 2 motions are either to (1) delay a PDP for a year
> (proposed by the Registrars); or (2) initiate a PDP (along fairly broad
> lines to look at vertical integration for both new and existing gTLDs,
> proposed by the Commercial Stakeholder Group).

A correction: there is no vertical integration of existing TLDs. Existing TLDs, even when they employ JM/CO, are not vertically integrated. 

In favor of 1): 
 - VI issues are long term and involve major changes in policy, fees, etc. 
 - Bundling JM/CO together with VI would require separate decisions and processes anyway. 
 - JM/CO is not a policy change, it is happening already
 - A PDP on the bigger issues should happen but to do so now simply holds up the many new entrants (not vertically integrated) who would thrive if they could do JM/CO but would die with either no JM/CO or another years' delay.

Against 1): 
- JM/CO is a policy change
- JM/CO is closely related to VI and so the issues should be considered together. 

I am not sure (asomeone more procedurally up on GNSO needs to answer this) but in her private fulminations to me Avri said something to the effect that the GNSO must review and approve the DAG when it is finished. IF so, I believe that this is the magical solution to our dilemma because the review of the DAG allows the opponents and supporters of JM/CO to have their debate without a PDP. 

--MM

ATOM RSS1 RSS2