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
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
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
Sent: Monday, July 28, 2014 10:37 AM
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
_______________________________________________
Gnso-ppsai-pdp-wg mailing list
--
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
Folgen Sie uns bei Twitter oder werden Sie unser Fan
bei Facebook:
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
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
Follow us on Twitter or join our fan community on
Facebook and stay updated:
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
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
________________________________
--------------------------------------------------------
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