- Gnso-newgtld-wg - lists.icann.org

Re: [Gnso-newgtld-wg] Predictability - Section 1.2.2
by Jamie Baxter April 18, 2018

April 18, 2018

2 1

Predictability - Section 1.2.2
by Jeff Neuman April 17, 2018

April 17, 2018

Anne, Thanks for the thorough comments. I have renamed the e-mail Chain to reflect the Section of the Report and give my thoughts: 1. Comment from Anne: Under Section 1.2.2 Predictability, item c., Please add the following first sentence. “Currently, as a result of recommendations made by the GNSO, the ICANN Board implemented a process for issues that arise during the implementation phase that permits the GNSO to provide “GNSO Input” or “GNSO Guidance” on an issue or to advise the Board that the issue requires either a full or Expedited PDP. Guidelines for these processes are provided in the GNSO’s Consensus Policy Implementation Framework (“CPIF”). In the second sentence, please change “The Working Group believes that” to “there is support in the Working Group for a recommendation that”. Response from Jeff: Good Suggestions. Can I offer the following slight tweaks: “Under Section 1.2.2 Predictability, item c., Please add the following first sentence. “Currently, as a result of consensus recommendations made by the GNSO, the ICANN Board implemented approved the GNSO’s Consensus Policy Implementation Framework (“CPIF”) {footnote to Framework} a process for issues that arise during the implementation phase of Consensus Policies. This that permits the GNSO to provide “GNSO Input” or “GNSO Guidance” on an issue or to advise the Board that the issue requires either a full or Expedited PDP {Insert Footnote to CPIF where definitions can be found for these terms}. Guidelines for these processes are provided in the GNSO’s Consensus Policy Implementation Framework (“CPIF”).” 1. Comment from Anne: In the second sentence, please change “The Working Group believes that” to “there is support in the Working Group for a recommendation that”. Response from Jeff: Agree with that change. 1. Comment from Anne: In the section “Anticipated Outcome”, please add the following after the first sentence: “The existing CPIF also recognizes this fact and provides for three mechanisms that mandate a process for additional advice where issues arise.” However, many in the New gTLD Subsequent Procedures PDP WG are seeking to establish a supplemental framework (designed to apply when implementation is complete) which, even in the event of changes, etc etc.” Response from Jeff: I think the second paragraph in that section along with the expansion of the discussion in the next section “Details of the Predictability Framework” does exactly what you recommend. Do you disagree? 1. Comment from Anne: In the last sentence in that section on “Anticipated Outcome”, the use of the term “after program launch” is unclear. “Launch” is a clear term as to a particular TLD. Acceptance of applications could be considered “launch” of the next round, but at that time, there would likely still be an IRT. What exactly do we mean by “implementation is considered complete” and who makes that determination? Response from Jeff: In the “Details of the Predictability Framework” Section, under Phase 3 we state: “For the purposes of the New gTLD Program, the effective date may better be considered as the date of program/Applicant Guidebook adoption by the ICANN Board or the opening of the application window.” How about we do the following: 1. Put a footnote in the “Anticipated Outcome” section pointing to where we define “Launch”. 2. Make it clear in the sentence referenced in Phase 3 above is our proposed definition of “Launch” and 3. Add a question in the Feedback section that asks for comment on our definition of Launch. 1. Comment from Anne: In the Section “Details of the Predictability Framework”, please Delete a portion of the second sentence of this section after the word, “ambiguities” and insert the following: “The GNSO proposed and the Board adopted a process whereby the GNSO could provide additional input with respect to various issues which might arise in the implementation phase”. Then begin the new sentence. “The WG is considering proposing the addition of a fourth element to be known as the ‘Predictability Framework” etc etc. (No need for underlining in the actual text – I show this only for emphasis on the requested changes.) Response from Jeff: I am a little confused as to why you are referring to it as a fourth element. The first element is policy development. The second is implementation (as covered by the CPIF). The Implementation Phase ends when the program is launched. Therefore, the third is this “Predictability Framework.” What am I missing? The Predictability Framework which envisions setting up a Standing IRT can refer things back to Phase 1 or Phase 2 at their discretion, but I re-read the CPIF and it does not necessarily apply once there is a launch of a program and changes to operations may need to be made. That is why we are creating this Framework in the first place as discussed on the numerous call. That said, I have no issue adding the work “considering” before the word “proposing” in that first paragraph. 1. Comment from Anne: Add the following to list of questions for feedback: How do you see the proposed Predictability Framework interacting with the existing CPIF procedures known as GNSO Input, GNSO Guidance, and GNSO Expedited PDP? In other words, when would these processes be utilized and when would application of the Predictability Framework make more sense? Response from Jeff: Makes sense. We will work that in. Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw The following additions/changes are needed to avoid the conflict with existing ICANN Board adopted policy in this arena: Under Section 1.2.2 Predictability, item c., Please add the following first sentence. “Currently, as a result of recommendations made by the GNSO, the ICANN Board implemented a process for issues that arise during the implementation phase that permits the GNSO to provide “GNSO Input” or “GNSO Guidance” on an issue or to advise the Board that the issue requires either a full or Expedited PDP. Guidelines for these processes are provided in the GNSO’s Consensus Policy Implementation Framework (“CPIF”). In the second sentence, please change “The Working Group believes that” to “there is support in the Working Group for a recommendation that”. In the section “Anticipated Outcome”, please add the following after the first sentence: “The existing CPIF also recognizes this fact and provides for three mechanisms that mandate a process for additional advice where issues arise.” However, many in the New gTLD Subsequent Procedures PDP WG are seeking to establish a supplemental framework (designed to apply when implementation is complete) which, even in the event of changes, etc etc.” In the last sentence in that section on “Anticipated Outcome”, the use of the term “after program launch” is unclear. “Launch” is a clear term as to a particular TLD. Acceptance of applications could be considered “launch” of the next round, but at that time, there would likely still be an IRT. What exactly do we mean by “implementation is considered complete” and who makes that determination? In the Section “Details of the Predictability Framework”, please Delete a portion of the second sentence of this section after the word, “ambiguities” and insert the following: “The GNSO proposed and the Board adopted a process whereby the GNSO could provide additional input with respect to various issues which might arise in the implementation phase”. Then begin the new sentence. “The WG is considering proposing the addition of a fourth element to be known as the ‘Predictability Framework” etc etc. (No need for underlining in the actual text – I show this only for emphasis on the requested changes.) In the Section entitled “What specific questions are the PDP WG seeking feedback on?”, please add the following question: * How do you see the proposed Predictability Framework interacting with the existing CPIF procedures known as GNSO Input, GNSO Guidance, and GNSO Expedited PDP? In other words, when would these processes be utilized and when would application of the Predictability Framework make more sense? Thank you, Anne Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman(a)lrrc.com<mailto:AAikman@lrrc.com> _____________________________ [cid:image001.png@01D3D632.20A99590] Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 2000 Tucson, Arizona 85701-1611 lrrc.com<http://lrrc.com/> From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Steve Chan Sent: Friday, April 13, 2018 8:39 PM To: gnso-newgtld-wg(a)icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday 16 April 2018 at 20:00 UTC, for 90 minutes. 1. Agenda Review 2. Roll Call/SOIs 3. Review of the Initial Report (continued) 4. AOB For item 3 of the agenda, we will be reviewing another section of the draft Initial Report. Attached, please find an extract of the section on Overarching Issues, which includes eight (8) topics. Those signed up as Members to this PDP WG should have received meeting information from the SOAC Support team. If you did not receive these participation details or if you would like to send your apologies, please contact the SOAC Support team (gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>). Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org<mailto:steve.chan@icann.org> mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses<applewebdata://310CAD3E-E244-4690-A938-C2655DD44BDE/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/ ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

2 8

Re: [Gnso-newgtld-wg] Predictability - Section 1.2.2
by Jamie Baxter April 17, 2018

April 17, 2018

2 1

Re: [Gnso-newgtld-wg] Predictability - Section 1.2.2
by Jamie Baxter April 17, 2018

April 17, 2018

3 2

Re: [Gnso-newgtld-wg] [Ext] RE: Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC
by Steve Chan April 17, 2018

April 17, 2018

Dear Anne, all, Thanks to you and others for pointing out the challenges of dealing with only a PDF. Your concerns are noted and we will be sure to include as both Word and PDF going forward. Best, Steve From: "Aikman-Scalese, Anne" <AAikman(a)lrrc.com> Date: Tuesday, April 17, 2018 at 11:12 AM To: 'Jeff Neuman' <jeff.neuman(a)comlaude.com>, Steve Chan <steve.chan(a)icann.org>, "gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> Subject: [Ext] RE: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC A pdf presents the lease convenient option for participation– and the most difficult and time-consuming to suggest changes via e-mail. Those not using Microsoft Word for document creation can still copy text from a Word document using any number of free applications on numerous platforms. They can then paste that text into e-mail to preserve your version control. Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman(a)lrrc.com _____________________________ Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 2000 Tucson, Arizona 85701-1611 lrrc.com[lrrc.com] From: Jeff Neuman [mailto:jeff.neuman@comlaude.com] Sent: Tuesday, April 17, 2018 6:40 AM To: Aikman-Scalese, Anne; 'Steve Chan'; gnso-newgtld-wg(a)icann.org Subject: RE: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC Thanks Anne. We will look into finding other ways to handle this. We know everyone can’t use Google Docs and Microsoft Word also presents issues for those not using Microsoft and for version control. Will address the substance of your comments separately. Thanks again. Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com or jeff.neuman(a)comlaude.com T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces(a)icann.org> On Behalf Of Aikman-Scalese, Anne Sent: Monday, April 16, 2018 8:26 PM To: 'Steve Chan' <steve.chan(a)icann.org>; gnso-newgtld-wg(a)icann.org Subject: Re: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC Jeff, Cheryl,et al, The Overarching Issues document was sent out in pdf format, which makes it extremely difficult to copy and paste language for suggested changes. Could staff please also forward a Word copy in future with the pdf? (In addition, we do need to see these drafts with more time prior to the call where the WG will be addressing them. ) Following the guidelines you set out for comment on today’s call, the section on the Predictability Framework does not reflect the discussions in the WG. The following additions/changes are needed to avoid the conflict with existing ICANN Board adopted policy in this arena: Under Section 1.2.2 Predictability, item c., Please add the following first sentence. “Currently, as a result of recommendations made by the GNSO, the ICANN Board implemented a process for issues that arise during the implementation phase that permits the GNSO to provide “GNSO Input” or “GNSO Guidance” on an issue or to advise the Board that the issue requires either a full or Expedited PDP. Guidelines for these processes are provided in the GNSO’s Consensus Policy Implementation Framework (“CPIF”). In the second sentence, please change “The Working Group believes that” to “there is support in the Working Group for a recommendation that”. In the section “Anticipated Outcome”, please add the following after the first sentence: “The existing CPIF also recognizes this fact and provides for three mechanisms that mandate a process for additional advice where issues arise.” However, many in the New gTLD Subsequent Procedures PDP WG are seeking to establish a supplemental framework (designed to apply when implementation is complete) which, even in the event of changes, etc etc.” In the last sentence in that section on “Anticipated Outcome”, the use of the term “after program launch” is unclear. “Launch” is a clear term as to a particular TLD. Acceptance of applications could be considered “launch” of the next round, but at that time, there would likely still be an IRT. What exactly do we mean by “implementation is considered complete” and who makes that determination? In the Section “Details of the Predictability Framework”, please Delete a portion of the second sentence of this section after the word, “ambiguities” and insert the following: “The GNSO proposed and the Board adopted a process whereby the GNSO could provide additional input with respect to various issues which might arise in the implementation phase”. Then begin the new sentence. “The WG is considering proposing the addition of a fourth element to be known as the ‘Predictability Framework” etc etc. (No need for underlining in the actual text – I show this only for emphasis on the requested changes.) In the Section entitled “What specific questions are the PDP WG seeking feedback on?”, please add the following question: How do you see the proposed Predictability Framework interacting with the existing CPIF procedures known as GNSO Input, GNSO Guidance, and GNSO Expedited PDP? In other words, when would these processes be utilized and when would application of the Predictability Framework make more sense? Thank you, Anne Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman(a)lrrc.com _____________________________ Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 2000 Tucson, Arizona 85701-1611 lrrc.com[lrrc.com] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Steve Chan Sent: Friday, April 13, 2018 8:39 PM To: gnso-newgtld-wg(a)icann.org Subject: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday 16 April 2018 at 20:00 UTC, for 90 minutes. Agenda Review Roll Call/SOIs Review of the Initial Report (continued) AOB For item 3 of the agenda, we will be reviewing another section of the draft Initial Report. Attached, please find an extract of the section on Overarching Issues, which includes eight (8) topics. Those signed up as Members to this PDP WG should have received meeting information from the SOAC Support team. If you did not receive these participation details or if you would like to send your apologies, please contact the SOAC Support team (gnso-secs(a)icann.org) Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages[gnso.icann.org]. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO[twitter.com] Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/[facebook.com] http://gnso.icann.org/en/[gnso.icann.org] This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

1 0

Proposed agenda - New gTLD Subsequent Procedures PDP WG - 16 April 2018 at 20:00 UTC
by Steve Chan April 17, 2018

April 17, 2018

Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday 16 April 2018 at 20:00 UTC, for 90 minutes. Agenda Review Roll Call/SOIs Review of the Initial Report (continued) AOB For item 3 of the agenda, we will be reviewing another section of the draft Initial Report. Attached, please find an extract of the section on Overarching Issues, which includes eight (8) topics. Those signed up as Members to this PDP WG should have received meeting information from the SOAC Support team. If you did not receive these participation details or if you would like to send your apologies, please contact the SOAC Support team (gnso-secs(a)icann.org) Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

3 4

Re: [Gnso-newgtld-wg] Predictability - Section 1.2.2
by Jamie Baxter April 17, 2018

April 17, 2018

2 1

Deliberations and Recommendations - CW comments
by lists＠christopherwilkinson.eu Wilkinson April 17, 2018

April 17, 2018

Good evening: > > Allow me to amplify and confirm my few Chat comments during the conference call last Monday afternoon, 9 April 2018. > > In general the working document (1.12 Deliberations etc .) is an excursion into a working method with which I am quite unfamiliar, so I ask those of you who have this for your bread-and-butter to bear with me for a little while. I also have noted that the document is in the form of questions for discussion and not recommendations at this stage. So I hope that some of my comments may still be taken into account. > > Indeed, at some points, I find the drafting on some issues rather uncertain; there are ambiguities and options that - from the point of view of a rather more conventional approach – might be described as loopholes. ICANN and GNSO will no doubt have gathered that the next 'round' will be scrutinised by third parties far more thoroughly than was the case in 2004 or 2012. More specifically: > > 1. Rollout: It would be helpful to have information about how many new TLDs have still not been implemented, and why. > > For instance, after the 24 months allowed, it is not clear why “… extensions…should continue to be available according to the same terms and conditions as they were allowed during the 2012 round.” > > In a related question, “The Work Track was also careful to avoid drawing the conclusion that only having <nic.TLD> registered constituted 'squatting' or 'warehousing' “ > > Taken together these two statements leave the strong impression that the Work Track would in practice accept squatting and warehousing of new TLDs. Was that intended? > > If there has been 'unwanted behaviour' – and the subsequent discussion suggests that there has been – then one might have expected a rather more proactive approach to discouraging such in the future. > > 2. Contractual compliance - pricing for premium domains. > > The document discusses the issue of 'pricing for premium domains' but reports that 'The WT has not reached any conclusions on this issue'. Whereas it is quite likely that applicant representations and related authorisations would address prmium pricing. > > For instance, in the case of a geographical name, there would normally be a presumption of non-discrimination between Registrants, such as towns or other communities, within that geo-TLD. > > More generally, ICANN might consider moving towards a policy whereby the economic 'rent' for a 'premium name' should accrue to the Registrant and not to the Registry. Otherwise it would appear that the Registry would be taking advantage of its monopoly over their TLD in question in an unjustifiably discriminatory manner. > > 3. Contractual compliance – enforceability of representations > > The document reports that the WT considered a proposal 'that all applicant representations should be included in the registry agreement' and that 'There was no agreement … in support of this proposal.' > > This would appear to be a rather weak conclusion which might be queried at a later stage because it does not really respond to the four questions indicated under f. Deliberations. > > > * * * > > The above is but a summary of the main concerns evoked by this section of the draft. I look forward to discussing these and other aspects in due course. > > Christopher Wilkinson

10 13

GNSO Council Liaisons to the New gTLD Subsequent Procedures PDP WG
by Steve Chan April 17, 2018

April 17, 2018

Dear WG Members, This message is to inform you that Paul McGrady, the previous Council liaison to the New gTLD Subsequent Procedures PDP WG, has stepped down from the position to serve instead as the Council liaison to the Review of All Rights Protection Mechanisms in All gTLDs PDP WG. At ICANN61, the GNSO Council acknowledged the broad list of topics within the New gTLD Subsequent Procedures PDP WG’s remit and noted that serving as an informed liaison can prove challenging with a plenary group and five (5) Work Tracks. In order to mitigate that challenge, at least to some degree, two Councilors volunteered to serve as Council liaisons to this PDP WG; please note that Donna Austin and Keith Drazek have agreed to jointly serve in this role. Best, Steve Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0

Recording, attendance & Webex Chat | New gTLD Subsequent Procedures Working Group Call | Monday, 16 April 2018 20:00 UTC
by Julie Bisland April 17, 2018

April 17, 2018

Dear All, Please find the attendance and Webex chat of the call attached to this email, and the MP3 recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 16 April 2018 at 20:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/Ti68B MP3: https://audio.icann.org/gnso/gnso-new-gtld-subsequent-16apr18-en.mp3 The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Main wiki page for the working group: https://community.icann.org/x/RgV1Aw Thank you. Kind regards, Julie

1 0