[gnso-rds-pdp-wg] FW: Notes from today's RDS PDP WG meeting

Thu Sep 22 15:28:46 UTC 2016

Chuck,

I would think that this is already covered in our list.  If it's not
already covered (which would surprise me), it certainly must.

Greg

On Thu, Sep 22, 2016 at 10:59 AM, Gomes, Chuck <cgomes at verisign.com> wrote:

> Should an additional possible requirement (or requirements) be added to
> cover the UDRP and URS need or is that already covered?
>
>
>
> Chuck
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-
> bounces at icann.org] *On Behalf Of *Greg Aaron
> *Sent:* Thursday, September 22, 2016 7:55 AM
> *To:* Volker Greimann; gnso-rds-pdp-wg at icann.org
>
> *Subject:* Re: [gnso-rds-pdp-wg] FW: Notes from today's RDS PDP WG meeting
>
>
>
> A parallel case: The UDRP and URS policies rely on contact data that is
> published publicly in gTLD registration directory services.  The reason is
> so identify that potential complainants can see it and make decisions about
> whether to mount a challenge, and so that UDRP and URS dispute resolution
> service providers can use the data to send the required communications.
>
>
>
> Could UDRP be altered to work without published contact data?  Maybe it’s
> not impossible.  But we can probably agree that the requirement currently
> exists – the current policy task assumes and necessitates data availability.
>
>
>
> Besides, the exercise here is for the WG to compile a list of “possible
> requirements.”  The group agreed to be liberal in the listings and debate
> their merits later.
>
>
>
> All best,
>
> --Greg
>
>
>
>
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-
> bounces at icann.org <gnso-rds-pdp-wg-bounces at icann.org>] *On Behalf Of *Volker
> Greimann
> *Sent:* Thursday, September 22, 2016 5:27 AM
> *To:* gnso-rds-pdp-wg at icann.org
> *Subject:* Re: [gnso-rds-pdp-wg] FW: Notes from today's RDS PDP WG meeting
>
>
>
> Hi Greg,
>
> you said it would be difficult but not it would be impossible, right? So I
> would assume the contractual requirement would still be accomplishable even
> without special access. A lot of the required data would also be in the
> registry databases as well, such as nameserver data, registration dates,
> etc, so no access to the RDS would be required for that purpose.
>
> Best,
>
> Volker
>
>
>
> Am 22.09.2016 um 00:04 schrieb Greg Aaron:
>
> Derived requirement: the data must be available for this stated purpose.
> If something is required (as in this case by a contract), then one must
> have the means to accomplish it.
>
>
>
>
>
> *From:* Gomes, Chuck [mailto:cgomes at verisign.com <cgomes at verisign.com>]
> *Sent:* Wednesday, September 21, 2016 5:58 PM
> *To:* Greg Aaron <gca at icginc.com> <gca at icginc.com>
> *Cc:* gnso-rds-pdp-wg at icann.org
> *Subject:* Re: [gnso-rds-pdp-wg] FW: Notes from today's RDS PDP WG meeting
>
>
>
> I don't question that at all Greg but what is the possible requirement?
>
>
>
> Chuck
>
> Sent from my iPhone
>
>
> On Sep 21, 2016, at 5:53 PM, Greg Aaron <gca at icginc.com> wrote:
>
> Dear Chuck:
>
>
>
> It is very difficult to perform DA-D43-R03 (assess whether domains in the
> TLD are being used to perpetrate security threats) without looking at
> registration data.  Review of registration dates, nameservers, contact
> data, etc. are often required to perform thatdiligence.
>
>
>
> BTW, this GAC safeguard was then incorporated into the nTLD contracts,
> Specification 11 paragraph 3b, which says that registry operators are also
> required to record actions taken as a result of these periodic security
> checks.
>
>
>
> So I suggest we leave it in.
>
>
>
> All best,
>
> --Greg
>
>
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-
> bounces at icann.org <gnso-rds-pdp-wg-bounces at icann.org>] *On Behalf Of *Gomes,
> Chuck
> *Sent:* Wednesday, September 21, 2016 5:27 PM
> *To:* gnso-rds-pdp-wg at icann.org
> *Subject:* [gnso-rds-pdp-wg] FW: Notes from today's RDS PDP WG meeting
>
>
>
> In my review of the eight (8) possible requirements in the attached file,
> I think it is obvious that none of them are relevant to the RDS and hence
> should be deleted from the v.4 of the triaged list of possible
> requirements.  If anyone, disagrees with my assessment, please identify any
> of the possible requirements that you think are relevant to the RDS and
> explain why so that the WG can discuss.  If not, I suggest that in our next
> meeting that quickly finalize a decision to delete them all.
>
>
>
> Chuck
>
>
>
> *From:* gnso-rds-pdp-wg-bounces at icann.org [mailto:gnso-rds-pdp-wg-
> bounces at icann.org <gnso-rds-pdp-wg-bounces at icann.org>] *On Behalf Of *Lisa
> Phifer
> *Sent:* Wednesday, September 21, 2016 2:54 AM
> *To:* gnso-rds-pdp-wg at icann.org
> *Subject:* Re: [gnso-rds-pdp-wg] Notes from today's RDS PDP WG meeting
>
>
>
> Dear all,
>
> With regard to action item #3 below, attached please find a small excerpt
> from draft 4 of the triaged possible requirements list, containing only
> those PRs marked "??" for review and possible deletion. During triage, we
> could not find a direct link between these PRs and registration directory
> services and so were unable to assign them codes and keywords.  WG members
> are therefore asked to consider if and how these flagged PRs are relevant
> to the RDS.
>
> Best regards,
> Lisa
>
>
> At 12:33 AM 9/21/2016, Marika Konings wrote:
>
>
> *3. Review Draft 4 of triaged possible requirements list *·  Discuss
> possible deletion of flagged PRs (those marked "??")
> ·  Discuss WG feedback on phase, code, and keyword mappings
> ·  Identify essential missing inputs (if any) and plan to include them
>
> *Action item #2*: WG members to review latest version of triaged possible
> requirements, including specific questions identified, in order to commence
> deliberations.
>
> *Action item #3*: Staff to circulate possible deletion of flagged PRs to
> mailing list to encourage input by WG members ahead of next week's meeting
>
>
>
> _______________________________________________
>
> gnso-rds-pdp-wg mailing list
>
> gnso-rds-pdp-wg at icann.org
>
> https://mm.icann.org/mailman/listinfo/gnso-rds-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
>
>
>
> Web: www.key-systems.net / www.RRPproxy.net
>
> www.domaindiscount24.com / www.BrandShelter.com
>
>
>
> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
>
> www.facebook.com/KeySystems
>
> 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
>
>
>
> 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
>
>
>
> Web: www.key-systems.net / www.RRPproxy.net
>
> www.domaindiscount24.com / www.BrandShelter.com
>
>
>
> Follow us on Twitter or join our fan community on Facebook and stay updated:
>
> www.facebook.com/KeySystems
>
> 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
>
>
>
> 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-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160922/f70f4bb5/attachment.html>