[Gnso-ppsai-pdp-wg] Agenda for WG call on 29 July
Kathy Kleiman
kathy at kathykleiman.com
Tue Jul 29 13:57:36 UTC 2014
Great discussion. Quick question: where do we stand on the cost-sharing
arrangements, e.g., "charging a reasonable fee for relaying certain
types of communications" (from our current E-1 template)?
Best,
Kathy
:
> Regarding the relay time frame, I think Volker's two business hour
> relay standard is doable assuming the P/P has an automated forwarding
> system for email or web form submissions to the registrant. I don't
> believe that's a reasonable time frame if human intervention is
> required to make the relay happen. To accommodate human involvement,
> I suggest a relay standard of no less than one or maybe two business days.
>
>
> From: Holly Raiche <h.raiche at internode.on.net
> <mailto:h.raiche at internode.on.net>>
> Date: Tuesday, July 29, 2014 4:16 AM
> To: "gnso-ppsai-pdp-wg at icann.org <mailto:gnso-ppsai-pdp-wg at icann.org>"
> <gnso-ppsai-pdp-wg at icann.org <mailto:gnso-ppsai-pdp-wg at icann.org>>
> Subject: Re: [Gnso-ppsai-pdp-wg] Agenda for WG call on 29 July
>
> First, I support Kathy's proposed wording. In fact, I think we should
> be dealing separately with the law enforcement/warrant situations
> where a 24/7 contact point is required and where there can be very
> prompt response to a very real threat of some kind, and other material
> to be relayed - which is where we are now.
>
> Clearly, yes, renewal notices and anything else required under the RAA
> should either be relayed or automatically dealt with so the beneficial
> registrant is informed. The harder question is what else is forwarded
> and how. I think we need to agree on words that describe the kind of
> material that should be relayed separately from how that is done. I
> do appreciate that actually forwarding mail is time consuming and
> costly. Some P/P providers may want to offer that service (and charge
> accordingly) but I'm not sure it is something that ICANN could
> mandate. It may make more sense to reach an agreed description of
> what should be forwarded (and lots of thought needed for that one) and
> leave it up to P/P providers as to how material is relayed, providing
> they describe to potential customers both what material they relay and
> what they will/will not do to actually relay the material
> (mail/email/whatever).
>
>
> I think that is close to Steve's suggestion, but I take Volker's point
> about the timing. I also take other points made in that other
> providers may, as part of the service, not relay material that are
> just marketing or other material that is close to spam in nature.
>
> I am an apology for this meeting - and sorry I will miss what will be
> an interesting discussion
>
> HOlly
>
> On 29 Jul 2014, at 7:40 pm, Luc SEUFER <lseufer at dclgroup.eu
> <mailto:lseufer at dclgroup.eu>> wrote:
>
> As most often, I agree with Volker.
> Furthermore I think we should keep the "request methods" clearly
> separated. An email or a fax can be automatically relayed, a
> postal mail requires human intervention.
> Luc
> On 29 Jul 2014, at 11:28, Volker Greimann
> <vgreimann at key-systems.net
> <mailto:vgreimann at key-systems.net><mailto:vgreimann at key-systems.net>
> <mailto:vgreimann at key-systems.net%3E>> wrote:
> Hi Steven,
> I also strongly object to the relay timeframe you are suggesting.
> There are such things as holidays and week-ends. I therefore
> propose the timeframe for manual relay should be no less than two
> business hours.
> Regarding the first part, I also have an issue with the "all relay
> requests". We for example also filter purchase inquiries and
> offers, which may not be spam in a strict sense.
> Volker
> As the updated template reflects, there has been considerable
> discussion about what overall policy regarding relay should be
> expressed in accreditation standards, and how the use of spam and
> other filters should be reflected. Let me suggest the following
> formulation for consideration:
> " P/P service providers must forward all relay requests received
> at the e-mail address provided for the domain name in Whois (or
> via the webform to which requesters are directed, if this
> technique is used), subject to the use of commercially reasonable
> measures (including CAPTCHA on web forms) to filter out spam,
> abusive communications, and the like. In the case of manual relay
> systems, relay must take place within 24 hours."
> Looking forward to discussing this on our call tomorrow.
> Steve Metalitz
> From: gnso-ppsai-pdp-wg-bounces at icann.org
> <mailto:gnso-ppsai-pdp-wg-bounces at icann.org><mailto:gnso-ppsai-pdp-wg-bounces at icann.org>
> [mailto:gnso-ppsai-pdp-wg-bounces at icann.org] On Behalf Of Mary Wong
> Sent: Monday, July 28, 2014 10:37 AM
> To: gnso-ppsai-pdp-wg at icann.org
> <mailto:gnso-ppsai-pdp-wg at icann.org><mailto:gnso-ppsai-pdp-wg at icann.org>
> Subject: [Gnso-ppsai-pdp-wg] Agenda for WG call on 29 July
> Dear WG members,
> The proposed agenda for the next WG meeting on 29 July is as follows:
> 1. Roll Call/Updates to SOI
> 2. Continue discussions on E-1 (updated template sent pm 23
> July; attached here again -- with a minor typo corrected - for
> your review)
> 3. Commence discussions on E-2 (if time permits)
> 4. Next steps/next meeting
> We will add the updated template for E-1 to the WG wiki, in
> accordance with the usual practice, as well.
> Thanks and cheers
> Mary
> Mary Wong
> Senior Policy Director
> Internet Corporation for Assigned Names & Numbers (ICANN)
> Telephone: +1 603 574 4892
> Email: mary.wong at icann.org
> <mailto:mary.wong at icann.org><mailto:mary.wong at icann.org>
> _______________________________________________
> Gnso-ppsai-pdp-wg mailing list
> Gnso-ppsai-pdp-wg at icann.org
> <mailto:Gnso-ppsai-pdp-wg at icann.org><mailto:Gnso-ppsai-pdp-wg at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
> --
> Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
> Mit freundlichen Grüßen,
> Volker A. Greimann
> - Rechtsabteilung -
> Key-Systems GmbH
> Im Oberen Werk 1
> 66386 St. Ingbert
> Tel.: +49 (0) 6894 - 9396 901
> Fax.: +49 (0) 6894 - 9396 851
> Email: vgreimann at key-systems.net
> <mailto:vgreimann at key-systems.net><mailto:vgreimann at key-systems.net>
> Web: www.key-systems.net<http://www.key-systems.net/> /
> www.RRPproxy.net<http://www.rrpproxy.net/>
> www.domaindiscount24.com<http://www.domaindiscount24.com/> /
> www.BrandShelter.com<http://www.brandshelter.com/>
> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
> www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
> www.twitter.com/key_systems<http://www.twitter.com/key_systems>
> Geschäftsführer: Alexander Siffrin
> Handelsregister Nr.: HR B 18835 - Saarbruecken
> Umsatzsteuer ID.: DE211006534
> Member of the KEYDRIVE GROUP
> www.keydrive.lu<http://www.keydrive.lu/>
> Der Inhalt dieser Nachricht ist vertraulich und nur für den
> angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe,
> Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist
> unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so
> bitten wir Sie, sich mit uns per E-Mail oder telefonisch in
> Verbindung zu setzen.
> --------------------------------------------
> Should you have any further questions, please do not hesitate to
> contact us.
> Best regards,
> Volker A. Greimann
> - legal department -
> Key-Systems GmbH
> Im Oberen Werk 1
> 66386 St. Ingbert
> Tel.: +49 (0) 6894 - 9396 901
> Fax.: +49 (0) 6894 - 9396 851
> Email: vgreimann at key-systems.net
> <mailto:vgreimann at key-systems.net><mailto:vgreimann at key-systems.net>
> Web: www.key-systems.net<http://www.key-systems.net/> /
> www.RRPproxy.net<http://www.rrpproxy.net/>
> www.domaindiscount24.com<http://www.domaindiscount24.com/> /
> www.BrandShelter.com<http://www.brandshelter.com/>
> Follow us on Twitter or join our fan community on Facebook and
> stay updated:
> www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
> www.twitter.com/key_systems<http://www.twitter.com/key_systems>
> CEO: Alexander Siffrin
> Registration No.: HR B 18835 - Saarbruecken
> V.A.T. ID.: DE211006534
> Member of the KEYDRIVE GROUP
> www.keydrive.lu<http://www.keydrive.lu/>
> This e-mail and its attachments is intended only for the person to
> whom it is addressed. Furthermore it is not permitted to publish
> any content of this email. You must not use, disclose, copy, print
> or rely on this e-mail. If an addressing or transmission error has
> misdirected this e-mail, kindly notify the author by replying to
> this e-mail or contacting us by telephone.
> _______________________________________________
> Gnso-ppsai-pdp-wg mailing list
> Gnso-ppsai-pdp-wg at icann.org
> <mailto:Gnso-ppsai-pdp-wg at icann.org><mailto:Gnso-ppsai-pdp-wg at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
> ________________________________
> --------------------------------------------------------
> This e-mail and any attached files are confidential and intended
> solely for the use of the individual or entity to whom they are
> addressed. If you have received this e-mail by mistake, please
> notify the sender immediately and delete it from your system. You
> must not copy the message or disclose its contents to anyone.
> Think of the environment: don't print this e-mail unless you
> really need to.
> --------------------------------------------------------
> _______________________________________________
> Gnso-ppsai-pdp-wg mailing list
> Gnso-ppsai-pdp-wg at icann.org <mailto:Gnso-ppsai-pdp-wg at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
>
>
> _______________________________________________
> Gnso-ppsai-pdp-wg mailing list
> Gnso-ppsai-pdp-wg at icann.org <mailto:Gnso-ppsai-pdp-wg at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
>
>
>
> _______________________________________________
> Gnso-ppsai-pdp-wg mailing list
> Gnso-ppsai-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-ppsai-pdp-wg/attachments/20140729/613faf54/attachment-0001.html>
More information about the Gnso-ppsai-pdp-wg
mailing list