ICANN ICANN Email List Archives

[soac-mapo]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [soac-mapo] two GAC comments overnight (NZ time)

  • To: "Frank March" <Frank.March@xxxxxxxxxxx>, <soac-mapo@xxxxxxxxx>
  • Subject: RE: [soac-mapo] two GAC comments overnight (NZ time)
  • From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Date: Mon, 23 Aug 2010 15:27:23 -0400

Thanks Frank.  The plan is to go through the suggested edits one by one
in the call; I suggest that you raise the points you list below when we
get to each item.

 

Regarding your first point, revisiting GNSO Rec. 6 would require a GNSO
PDP, so that cannot be an objective of this group.  Moreover, that could
cause serious delays.

 

Chuck

 

From: owner-soac-mapo@xxxxxxxxx [mailto:owner-soac-mapo@xxxxxxxxx] On
Behalf Of Frank March
Sent: Monday, August 23, 2010 3:10 PM
To: soac-mapo@xxxxxxxxx
Subject: [soac-mapo] two GAC comments overnight (NZ time)

 

I have not been able to add these into the redline draft but it is
important that they be available prior to the conference call

 

1.   

As a threshold matter, the proposed deletion of Task #1 on page 2 is
inconsistent with a key point and purpose of the GAC's letter, so the
task should be retained as originally drafted.    In addition, there is
a helpful comment from Avri Doria regarding a statement in  the Rules of
Engagement section to the effect that the original purpose of the GNSO's
recommendation #6 would not be revisited; as Bertrand has already noted,
it seems clear that the group would need to revisit the original
recommendation if the GAC's position is to be fully considered.  Thanks
again for the opportunity to review the draft.  

 

2.  

 

I have a version with chnages marked for this but it would be confusing
to circulate this at this stage since an updated version has already
been circulated.

Thanks for the very interesting draft charter. I have read with great
attention the different edits and you will find attached some proposals
to bridge some of the remaining differences (with inserted commentary -
under name BPC), in particular :

 

- support for the use of "maximizing" instead of "preserving" in the
purpose of the working group, as it is more appropriate to present
"universal resolvability" as a general objective to which there can
(should) be (only) limited exceptions

- replacing robin Gross' formulation in the Key Assumptions" by an exact
quote from ICANN's Articles of Incorporation (article 4) related to
ICANN operating "in conformity with relevant principles of international
law and applicable international conventions", a reference to the
Articles of Incorporation is added for that purpose in the list of
references at the beginning of the text

- adding in the "Rules of Engagment" part a reference to "any relevant
element identified since Rec6 was passed", as it seems appropriate to
take into account the deeper understanding of the challenge that has
emerged in the last few months and the likely reformulation of the
objectives; this is also intended to take into account Avri's remark

- modifying the wording regarding minority positions in the report, so
as not to seem to imply from the onset that rough consensus cannot be
achieved within the group

- setting the date of 13 September as a deadline for a "preliminary"
report only, as it is unlikely that a full solution will have emerged by
then. 

 

In general, the setting up of such a cross-community working group is a
worthy precedent.

 

----

Frank March

Senior Specialist Advisor

Digital Development

Energy and Communications Branch, Ministry of Economic Development

33 Bowen Street, PO Box 1473, WELLINGTON

Mobile: (+64) 021 494165

 

newzealand.govt.nz - connecting you to New Zealand central & local
government services 

________________________________

Any opinions expressed in this message are not necessarily those of the
Ministry of Economic Development. This message and any files transmitted
with it are confidential and solely for the use of the intended
recipient. If you are not the intended recipient or the person
responsible for delivery to the intended recipient, be advised that you
have received this message in error and that any use is strictly
prohibited. Please contact the sender and delete the message and any
attachment from your computer. 

________________________________



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy