[DT-O] DRAFT DT-O Comments on Schedule A of the ICANN-PTI Services Agreement

[Gomes, Chuck]

Thank you very much Elise for the fast response.  Please see my responses below.

 

All: Please respond as to whether or not you agree with my responses and, if not, please explain.

 

Chuck

 

From: Elise Gerich [mailto:elise.gerich at icann.org] 
Sent: Thursday, August 18, 2016 7:11 PM
To: Gomes, Chuck; DT-O Mailing List (dto at icann.org)
Subject: Re: [DT-O] DRAFT DT-O Comments on Schedule A of the ICANN-PTI Services Agreement

 

Hello Chuck,

 

Thank you for reviewing Schedule A and for your questions.  I have taken a first crack at responding to some of the questions that you have highlighted in yellow.  Please let me know if my responses add some clarity to the services listed in your table.

 

In reference to “Executive and Administrative”, there is a question in the chart as to whether “RZERC” should be added to the description associated with the service description.  The CSC has a direct oversight role of PTI and PTI will report to the CSC regularly.   It is anticipated that administrative support for the CSC meetings and reports will be needed.  In the case of RZERC, its role per its charter is to make recommendations for proposed architectural changes to the DNS to ICANN’s Board.  A representative of PTI will serve on the RZERC. However the relationship between PTI and RZERC is different than that between PYI and the CSC, so no administrative support is anticipated due to the difference in the relationship.

[Chuck Gomes] With this understanding, I would be comfortable deleted this row of the table.

 

Regarding “Information Systems, Development, and Security”, there is a question about hardware and software procurement, as well as maintenance of hardware and software.  PTI will leverage ICANN’s IT deparment’s relationship/contracts with vendors to procure hardware, software, and maintenance contracts. This is consistent with the current practice and it enables PTI to continue to benefit from the economic savings available by combining our procurement requirements.

[Chuck Gomes] I assumed this would be the case but it seems to me that it is not totally clear in the description.  I wonder if it would be helpful to add what you say:  “PTI will leverage ICANN’s IT department’s relationship/contracts with vendors to procure hardware, software, and maintenance contracts.”

 

Regarding the question about Security Services, yes, this service includes the same cyber security services that ICANN provides for its own organization.  

[Chuck Gomes] Would it be okay to suggest an edit like this:  “Security services, including cyber security, investigations, and facilities security infrastructure.”

 

Thanks again for your review of Schedule A.  

 

Regards,

— Elise

 

From: <dto-bounces at icann.org> on behalf of "Gomes, Chuck" <cgomes at verisign.com>
Date: Thursday, August 18, 2016 at 2:59 PM
To: "DT-O Mailing List (dto at icann.org)" <dto at icann.org>
Subject: [DT-O] DRAFT DT-O Comments on Schedule A of the ICANN-PTI Services Agreement

 

I took a first crack at possible DT-O comments on Schedule A of the ICANN-PTI Services Agreement.  I request that each of you review what I did and suggest edits, additions, deletions.  I would like to send this to the IOTF list by Monday of next week if possible so please respond no later than Monday morning if possible.

 

Chuck

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/dto/attachments/20160818/3a1befa9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5909 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/dto/attachments/20160818/3a1befa9/smime-0001.p7s>