[council] Proposed GNSO Council comment on the draft FY20 IANA/PTI Budget

Mon Nov 12 12:58:48 UTC 2018

Thanks Ayden. I think it would be a useful amendment to make despite the timeline going beyond FY20.
Regards,
Philippe

-------- Message d'origine --------
De : Ayden Férdeline <icann at ferdeline.com>
Date : 12/11/2018 13:01 (GMT+01:00)
À : "McGrady, Paul D." <PMcGrady at winston.com>
Cc : GNSO Council List <council at gnso.icann.org>
Objet : Re: [council] Proposed GNSO Council comment on the draft FY20 IANA/PTI Budget

Dear all,

Please find attached a proposed revision to the Council's comment on the FY20 IANA/PTI Budget.

We should change this sentence:

The GNSO Council notes that its current priorities and policy development activities do not appear to intersect directly with the operations of the IANA Functions by PTI.

To read:

The GNSO Council notes that one of our current policy development activities does potentially intersect with the operations of the IANA Functions by PTI. The New gTLD Subsequent Procedures Policy Development Process Working Group is currently developing Policy that may ultimately instruct IANA to place new TLDs into the root. However, it is not anticipated that delegation would occur in FY20.

If there are any concerns with the attached comment being submitted today, can you please advise so on the mailing list by 18:00 UTC today. Thank you.

Best wishes,
Ayden Férdeline

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 9 November 2018 17:04, McGrady, Paul D. <PMcGrady at winston.com> wrote:

Thanks Ayden.

I have set this to the IPC for any comments.  However, can you please clarify what is meant by “The GNSO Council notes that its current priorities and policy development activities do not appear to intersect directly with the operations of the IANA Functions by PTI.”  Seems to me that the Subsequent Procedures PDP is working on Policy related to a process which ultimately instructs IANA to put new TLDs in the root, so I’m not sure that the statement is accurate.  Is there a way to clarify what was meant by this sentence?  Thanks!

Best,
Paul

From: council <council-bounces at gnso.icann.org> On Behalf Of Ayden Férdeline
Sent: Friday, November 9, 2018 9:08 AM
To: Ayden Férdeline <icann at ferdeline.com>
Cc: GNSO Council List <council at gnso.icann.org>
Subject: Re: [council] Proposed GNSO Council comment on the draft FY20 IANA/PTI Budget

Dear all,

Just a friendly reminder; the attached comment will be submitted on behalf of the GNSO Council this coming Monday, unless an objection is raised. (The only further edit that would be made would be to remove the 'draft' watermark from the document.) Thank you.

Kind regards,

Ayden Férdeline

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Wednesday, 7 November 2018 11:00, Ayden Férdeline <icann at ferdeline.com<mailto:icann at ferdeline.com>> wrote:

Dear all,

On behalf of the Council's Standing Committee on Budget and Operations, please find attached a comment that we have prepared on the draft FY20 IANA/PTI budget.

We are seeking to submit this comment on behalf of the Council on 12 November 2018, absent any objections from a member of the Council.

With apologies for not getting this into your inbox sooner, can you please review the attached document as a matter of urgency. Thank you very much.

Kind regards,

Ayden Férdeline

________________________________
The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20181112/7e048206/attachment.html>