Thank you, Trang. I understand where the last part comes from now, a unilateral change would be a contradiction in terms for “SLA”… “PTI + ICANN” is also fine by me then.

Regards,

Philippe

 

 

Dear Philippe,

 

Thank you for your support of the clarifications. Regarding your comment on the third row of slide 7, PTI would of course be the one performing the implementation. If the implementation needs ICANN org approval before implementation can begin (as envisaged under certain circumstances in the SLA change document being drafted for example), then that process would take place. So, I guess it all goes to if the row is capturing only the implementation activity, or the steps leading up to it as well. If the former, then I agree with you that PTI makes sense.

 

Best,

 

Trang

 

Thanks Bart.

 

I would agree that we need to align the terminology with the current situation, so I support the changes you suggest. Not quite sure about “Slide 7 – Third row”, seems to me it may be PTI only but happy to be corrected.  

 

Regards,

Philippe

 

 

Dear Phillippe, Martin, all,

Thank you for the comments received to date. Included updated version, which also includes comments and suggestion from Trang.

There is one major point that I want to draw to your attention with respect to the inclusion of the table of Measures. The table refers to language in the charter, in particular IFO. However, as this effectiveness review is about the current situation, and for clarity, it is suggested to replace IFO with PTI or ICANN & PTI where appropriate.

See Slide 5,6, and 7. The suggested changes are:

Slide 5 – Second row, “IANA Functions Operator” should be changed to “PTI” for clarity:

Slide 5 – Third row, “IANA Functions Operator” should be changed to “PTI and ICANN” to more accurately reflect the RAPs

Slide 7 – Second row, “IFO” should be changed to “PTI and ICANN” for clarity

Slide 7 – Third row, “IFO” should change to “PTI and ICANN” for clarity and for consistency with the SLA change process being drafted.

 Slide 7  row 1 , the requirement to meet annually is not in charter, only a requirement for “as needs demand”? Also, replacing “IFO” with “ICANN and PTI.”

 

Please advise

Kind regards,

Bart

 

 

Bart,

 

Thanks for this. I think that’s good, noted a typo on slide two bullet point two (“without”?) there’s probably a word missing there, and a couple of others: Slide 3: “taks” and Slide 9 “Prepratory”

 

Regards,

 

Philippe

 

 

Dear all,

Please find included the intitial draft for the RT presentations in Barcelona.

I have drafted it on the basis of Phillipe’s example, the template document and using latest version of Debbie’s document.

Please note that:

CSC has appointed Elain Pruis as its liaison and PTI has appointed Kim Davies as its liaison. We are awaiting appointment of the ICANN Org liaison. For the time being I have included Trang and Amy Creamer in cc.

Kind regards,

Bart

 

 

_________________________________________________________________________________________________________________________

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.

_________________________________________________________________________________________________________________________

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.

_________________________________________________________________________________________________________________________

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.