[CWG-Stewardship] architectural changes to the root system

[Greg Shatan]

This raises the issue of separation -- if we involve the PTI Board in
policy, isn't that the wrong side of the line?  Shouldn't policy be dealt
with on the ICANN side of the divide?  (Also, we are requiring more of a
working board, and less of a minimalist board by going down this road.)

On Wed, Apr 22, 2015 at 4:06 PM, Milton L Mueller <mueller at syr.edu> wrote:

>
>
> > -----Original Message-----
> > On Wed, Apr 22, 2015 at 02:16:23AM -0400, Greg Shatan wrote:
> > > This issue (who makes decisions about or approves "architectural
> > > changes to the root system" in the absence of the NTIA) bears further
> > > review.  The CSC doesn't seem like the right place at all.  The PTI
> > > Board makes some sense, but only if we are not keeping it minimalist.
> > > Could the NTIA role simply disappear (as we propose to happen with the
> > > authorization/validation function)?
> >
> > Why isn't this the names community within ICANN?  That's where the policy
> > resides, I thought?
> >
>
> Good point. While the policy might be developed by some combination of
> ccNSO and GNSO, The "decider" should be the PTI board, not the ICANN board.
> Speaking as someone who was on DT-F, we understood these "architectural
> changes" to be processes that drew on a broad range of expertise around the
> community, and viewed NTIA's role as someone who made the final approval
> rather than as someone who ran the policy process.
>
> Another point here is that ICANN's policy making apparatus is actually
> poorly organized when it comes to decisions that cross ccTLD and GTLD
> lines. I think they would have to form a cross-community working group to
> deal with such issues. Nothing terribly difficult about that, but I still
> think it makes a lot more sense for the recommendations of such a ccwg to
> be submitted to the PTI board for approval than the ICANN board.
>
> _______________________________________________
> CWG-Stewardship mailing list
> CWG-Stewardship at icann.org
> https://mm.icann.org/mailman/listinfo/cwg-stewardship
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20150422/7b028036/attachment.html>