Additional notes, background for 9 January IRT Call
Dear Colleagues, In advance of our meeting on Tuesday, I'm including a few background points that may have been forgotten or lost since it's been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT's feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week. With respect to the feedback received on PPAA Section 3.12 (abuse contact): Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report). Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply IRT feedback re: Section 3.12.2 is noted-I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself. Section 3.14: This edit was proposed based on text from Final Report in the IP framework-this was discussed briefly on a prior IRT call but can be discussed further. Section 3.17: IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report. Section 3.19: This requirement was included in the Final Report. Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>
My apologies, but I've had a conflict arise for Tuesday. Darcy __________ *Darcy Southwell *| Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart On Wed, Jan 3, 2018 at 9:34 AM, Amy Bivins <amy.bivins@icann.org> wrote:
Dear Colleagues,
In advance of our meeting on Tuesday, I’m including a few background points that may have been forgotten or lost since it’s been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT’s feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week.
*With respect to the feedback received on PPAA Section 3.12 (abuse contact):* Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report).
Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply
IRT feedback re: Section 3.12.2 is noted—I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself.
*Section 3.14: *This edit was proposed based on text from Final Report in the IP framework—this was discussed briefly on a prior IRT call but can be discussed further.
*Section 3.17: *IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report.
*Section 3.19: *This requirement was included in the Final Report.
Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week.
Best,
Amy
*Amy E. Bivins*
Registrar Services and Engagement Senior Manager
Registrar Services and Industry Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct: +1 (202) 249-7551 <(202)%20249-7551>
Fax: +1 (202) 789-0104 <(202)%20789-0104>
Email: amy.bivins@icann.org
www.icann.org
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
Me too Sent from my iPad On Jan 8, 2018, at 8:07 PM, Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> wrote: My apologies, but I've had a conflict arise for Tuesday. Darcy __________ Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart [https://www.endurance.com/wp-content/themes/endurance/assets/images/enduranc...] On Wed, Jan 3, 2018 at 9:34 AM, Amy Bivins <amy.bivins@icann.org<mailto:amy.bivins@icann.org>> wrote: Dear Colleagues, In advance of our meeting on Tuesday, I’m including a few background points that may have been forgotten or lost since it’s been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT’s feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week. With respect to the feedback received on PPAA Section 3.12 (abuse contact): Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report). Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply IRT feedback re: Section 3.12.2 is noted—I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself. Section 3.14: This edit was proposed based on text from Final Report in the IP framework—this was discussed briefly on a prior IRT call but can be discussed further. Section 3.17: IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report. Section 3.19: This requirement was included in the Final Report. Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551<tel:(202)%20249-7551> Fax: +1 (202) 789-0104<tel:(202)%20789-0104> Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org> _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
Ditto Theo On 9-1-2018 11:48, Victoria Sheckler wrote:
Me too
Sent from my iPad
On Jan 8, 2018, at 8:07 PM, Darcy Southwell <darcy.southwell@endurance.com <mailto:darcy.southwell@endurance.com>> wrote:
My apologies, but I've had a conflict arise for Tuesday.
Darcy
__________
*Darcy Southwell *| Compliance Officer
M: +1 503-453-7305 │ Skype: darcy.enyeart
On Wed, Jan 3, 2018 at 9:34 AM, Amy Bivins <amy.bivins@icann.org <mailto:amy.bivins@icann.org>> wrote:
Dear Colleagues,
In advance of our meeting on Tuesday, I’m including a few background points that may have been forgotten or lost since it’s been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT’s feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week.
*With respect to the feedback received on PPAA Section 3.12 (abuse contact):* Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report).
Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply
IRT feedback re: Section 3.12.2 is noted—I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself.
*Section 3.14: *This edit was proposed based on text from Final Report in the IP framework—this was discussed briefly on a prior IRT call but can be discussed further.
*Section 3.17: *IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report.
*Section 3.19: *This requirement was included in the Final Report.
Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week.
Best,
Amy
*Amy E. Bivins*
Registrar Services and Engagement Senior Manager
Registrar Services and Industry Relations
Internet Corporation for Assigned Names and Numbers (ICANN)
Direct: +1 (202) 249-7551 <tel:%28202%29%20249-7551>
Fax: +1 (202) 789-0104 <tel:%28202%29%20789-0104>
Email: amy.bivins@icann.org <mailto:amy.bivins@icann.org>
www.icann.org <http://www.icann.org>
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org <mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl <https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl>
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org <mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
_______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
I also send my apologies. Many thanks Lindsay Lindsay Hamilton-Reid Legal Counsel Direct: +44 (0)1452 509145 | Mobile: 07720 091147 | Email: Lindsay.Hamilton-Reid@1and1.co.uk<mailto:Lindsay.Hamilton-Reid@1and1.co.uk> www.fasthosts.co.uk<http://www.fasthosts.co.uk/> www.1and1.co.uk<http://www.1and1.co.uk/> [fh-1and1] © 2015 All rights reserved. Fasthosts is the trading name of Fasthosts Internet Limited. Company registration no. 03656438. Registered in England and Wales. Registered office: Discovery House, 154 Southgate Street, Gloucester, GL1 2EX. VAT no. 720821857. 1&1 is the trading name of 1&1 Internet Limited. Company registration no. 03953678. Registered in England and Wales. Registered office: Discovery House, 154 Southgate Street, Gloucester, GL1 2EX. VAT no. 752539027. This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use any part of it - please delete all copies immediately and notify 1&1 on 0844 335 1211 or Fasthosts on 0333 0142 700. Any statements, opinions or information in this message are provided by the author, not on behalf of 1&1 and/or Fasthosts, unless subsequently confirmed by an individual who is authorised to represent 1&1 and/or Fasthosts. [linkedin]<http://www.linkedin.com/company/fasthosts-internet-ltd>[twitter]<https://twitter.com/Fasthosts>[facebook]<https://www.facebook.com/fasthostsinternet>[gplus]<https://plus.google.com/u/0/b/107582097021398424605/+fasthosts/posts>[blog]<http://blogs.fasthosts.co.uk/>[youtube]<http://www.youtube.com/user/Fasthostsinternet> From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of theo geurts Sent: 09 January 2018 14:17 To: gdd-gnso-ppsai-impl@icann.org Subject: Re: [Gdd-gnso-ppsai-impl] Additional notes, background for 9 January IRT Call Ditto Theo On 9-1-2018 11:48, Victoria Sheckler wrote: Me too Sent from my iPad On Jan 8, 2018, at 8:07 PM, Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> wrote: My apologies, but I've had a conflict arise for Tuesday. Darcy __________ Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart [https://www.endurance.com/wp-content/themes/endurance/assets/images/enduranc...] On Wed, Jan 3, 2018 at 9:34 AM, Amy Bivins <amy.bivins@icann.org<mailto:amy.bivins@icann.org>> wrote: Dear Colleagues, In advance of our meeting on Tuesday, I’m including a few background points that may have been forgotten or lost since it’s been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT’s feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week. With respect to the feedback received on PPAA Section 3.12 (abuse contact): Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report). Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply IRT feedback re: Section 3.12.2 is noted—I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself. Section 3.14: This edit was proposed based on text from Final Report in the IP framework—this was discussed briefly on a prior IRT call but can be discussed further. Section 3.17: IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report. Section 3.19: This requirement was included in the Final Report. Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551<tel:%28202%29%20249-7551> Fax: +1 (202) 789-0104<tel:%28202%29%20789-0104> Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org> _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
Hi Lindsay, Thank you for this, I have noted your apology for today’s meeting. Kind regards, Michelle From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces@icann.org<mailto:gdd-gnso-ppsai-impl-bounces@icann.org>> on behalf of Lindsay Hamilton-Reid <Lindsay.Hamilton-Reid@fasthosts.com<mailto:Lindsay.Hamilton-Reid@fasthosts.com>> Reply-To: "gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>" <gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> Date: Tuesday, January 9, 2018 at 8:18 AM To: "gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>" <gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> Subject: Re: [Gdd-gnso-ppsai-impl] Additional notes, background for 9 January IRT Call I also send my apologies. Many thanks Lindsay Lindsay Hamilton-Reid Legal Counsel Direct: +44 (0)1452 509145 | Mobile: 07720 091147 | Email:Lindsay.Hamilton-Reid@1and1.co.uk<mailto:Lindsay.Hamilton-Reid@1and1.co.uk> www.fasthosts.co.uk[fasthosts.co.uk]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fasthosts.co.uk_&d=D...> www.1and1.co.uk[1and1.co.uk]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.1and1.co.uk_&d=DwMGa...> [fh-1and1] ? 2015 All rights reserved. Fasthosts is the trading name of Fasthosts Internet Limited. Company registration no. 03656438. Registered in England and Wales. Registered office: Discovery House, 154 Southgate Street, Gloucester, GL1 2EX. VAT no. 720821857. 1&1 is the trading name of 1&1 Internet Limited. Company registration no. 03953678. Registered in England and Wales. Registered office: Discovery House, 154 Southgate Street, Gloucester, GL1 2EX. VAT no. 752539027. This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use any part of it - please delete all copies immediately and notify 1&1 on 0844 335 1211 or Fasthosts on 0333 0142 700. Any statements, opinions or information in this message are provided by the author, not on behalf of 1&1 and/or Fasthosts, unless subsequently confirmed by an individual who is authorised to represent 1&1 and/or Fasthosts. [linkedin][linkedin.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_fasthosts-2Dinternet-2Dltd&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=0TlXxc7PZEXUEJLFMVr0bFYkRL1W-I-Oum1jlnRuDu4&e=>[twitter][twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_Fasthosts&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=BFjK0hKe3gRUUer-kWrllNz5YpxEPbcI2TYQ9KqhBG0&e=>[facebook][facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_fasthostsinternet&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=pltOEprRNWXRII1Xol9wL_pUBV6lBcfiOS_Jfczkm14&e=>[gplus][plus.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_u_0_b_107582097021398424605_-2Bfasthosts_posts&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=OXTfwP92xz_poZgfYvTwnlugfNzkom_npZTJspGjrZM&e=>[blog][blogs.fasthosts.co.uk]<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.fasthosts.co.uk_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=vS_PSD6qwrxiRmhvPgt-olJIhcdnpxm2kP1h2p7yIbw&e=>[youtube][youtube.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_user_Fasthostsinternet&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=OZ0MSh6YVEFZKkkcjb6SshFacEGfqPxGmf5pceQsLAY&s=045rkaWCXDDGVc7n2BNNHekzzW2aRYNIWrwHAtAirXs&e=> From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of theo geurts Sent: 09 January 2018 14:17 To: gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org> Subject: Re: [Gdd-gnso-ppsai-impl] Additional notes, background for 9 January IRT Call Ditto Theo On 9-1-2018 11:48, Victoria Sheckler wrote: Me too Sent from my iPad On Jan 8, 2018, at 8:07 PM, Darcy Southwell <darcy.southwell@endurance.com<mailto:darcy.southwell@endurance.com>> wrote: My apologies, but I've had a conflict arise for Tuesday. Darcy __________ Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart [https://www.endurance.com/wp-content/themes/endurance/assets/images/enduranc...] On Wed, Jan 3, 2018 at 9:34 AM, Amy Bivins <amy.bivins@icann.org<mailto:amy.bivins@icann.org>> wrote: Dear Colleagues, In advance of our meeting on Tuesday, I’m including a few background points that may have been forgotten or lost since it’s been awhile since we have discussed the upcoming PPAA sections we expect to cover during the meeting. Reviewing the IRT’s feedback on the substance of the draft contract, we will likely be able to make it through the rest of the PPAA draft (not including the specifications) next week. With respect to the feedback received on PPAA Section 3.12 (abuse contact):Per discussion on IRT calls in early 2017, we began drafting this section with RAA requirements where Final Report was silent (final report mentioned "designated" rather than "dedicated" contact but was otherwise silent on specific abuse contact requirements. The IRT supported this approach at the time. We adapted RAA requirements, per IRT discussions and Final Report, to allow for abuse contact options other than an email address (per recommendation in final report--"to address increasing volumes of spam" associated with the publication of an abuse contact email address (see p. 62 of Final Report). Re: PSWG feedback--this "abuse contact" provision governs when other frameworks (LEA or IP) do not apply IRT feedback re: Section 3.12.2 is noted—I believe the edits were added in an attempt to capture the requirements of the LEA framework, but this can be handled within the framework itself. Section 3.14: This edit was proposed based on text from Final Report in the IP framework—this was discussed briefly on a prior IRT call but can be discussed further. Section 3.17: IRT feedback was that this does not read consistently with Final Report. IRT members who raised this point are asked to explain why/how they believe this is inconstant with the Final Report, as our interpretation of this text is that it has the same meaning as the Final Report. Section 3.19: This requirement was included in the Final Report. Please provide any further feedback on these or any other aspects of the PPAA and issues identified in the issues list on the list prior to our call next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551<tel:%28202%29%20249-7551> Fax: +1 (202) 789-0104<tel:%28202%29%20789-0104> Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&c...> _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl@icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl
participants (6)
-
Amy Bivins -
Darcy Southwell -
Lindsay Hamilton-Reid -
Michelle DeSmyter -
theo geurts -
Victoria Sheckler