[registrars] RRA Amendment Notification for .COM

[Robert Gomez]

From: ICANN Global Support Center <globalsupport at icann.org>
Date: Wednesday, January 8, 2020 at 4:37 PM
To: "gbunton at tucows.com" <gbunton at tucows.com>, "secretariat at icannregistrars.org" <secretariat at icannregistrars.org>, "registrars at icann.org" <registrars at icann.org>
Cc: Karla Hakansson <karla.hakansson at icann.org>, Andrew Dickson <andrew.dickson at icann.org>, Andee Hill <andee.hill at icann.org>, Carlos Chavoya <carlos.chavoya at icann.org>, Robert Gomez <robert.gomez at icann.org>, Camia Frank <camia.frank at icann.org>, Jeanne Gregg <jeanne.gregg at icann.org>, "pkane at verisign.com" <pkane at verisign.com>
Subject: [Ext] RRA Amendment Notification for .COM [ ref:_00D616tJk._5004MZKWph:ref ]

Hello Graeme,

Attached, please find the following documents for .COM submitted by Verisign, Inc. to be shared with your Stakeholder Group:

1.                   Cover Letter filename = Transmittal Letter_Proposed Revisions to COM RRA_012020
2.                   Red-lined RRA Amendment filename = Ex_A_Proposed Revisions to COM RRA_012020_Transmittal to ICANN
3.                   Clean RRA Amendment filename = Proposed com RRA Appendix 8A_Clean
4.                   Summary of Changes filename = Ex_B_Summary of Proposed Revisions to COM RRA_012020_Transmittal to ICANN (002)

Per the RRA Amendment Procedure, the RrSG has up to 21 days to review the proposed changes. If the registrars have concerns, please advise ICANN by responding to this message no later than 23:59 UTC on 29 January 2020. If there is no response by this time, ICANN will assume there are no concerns and will continue processing the request. If the RrSG responds with concerns, ICANN will continue to the next step of the RRA Amendment Procedure which is to consult with the RrSG and the Registry Operator.

If you have any further inquiries, please let me know.

Kind regards,

Robert Gomez
GDD Service Delivery
[Image removed by sender.]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/registrars/attachments/20200109/e340052c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Transmittal Letter_Proposed Revisions to COM RRA_012020.pdf
Type: application/pdf
Size: 44841 bytes
Desc: Transmittal Letter_Proposed Revisions to COM RRA_012020.pdf
URL: <https://mm.icann.org/pipermail/registrars/attachments/20200109/e340052c/TransmittalLetter_ProposedRevisionstoCOMRRA_012020.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ex_B_Summary of Proposed Revisions to COM RRA_012020_Transmittal to ICANN (002).pdf
Type: application/pdf
Size: 197752 bytes
Desc: Ex_B_Summary of Proposed Revisions to COM RRA_012020_Transmittal to ICANN (002).pdf
URL: <https://mm.icann.org/pipermail/registrars/attachments/20200109/e340052c/Ex_B_SummaryofProposedRevisionstoCOMRRA_012020_TransmittaltoICANN002.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Proposed com RRA Appendix 8A_Clean.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 87452 bytes
Desc: Proposed com RRA Appendix 8A_Clean.docx
URL: <https://mm.icann.org/pipermail/registrars/attachments/20200109/e340052c/ProposedcomRRAAppendix8A_Clean.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ex_A_Proposed Revisions to COM RRA_012020_Transmittal to ICANN.pdf
Type: application/pdf
Size: 147539 bytes
Desc: Ex_A_Proposed Revisions to COM RRA_012020_Transmittal to ICANN.pdf
URL: <https://mm.icann.org/pipermail/registrars/attachments/20200109/e340052c/Ex_A_ProposedRevisionstoCOMRRA_012020_TransmittaltoICANN.pdf>