[gnso-rds-pdp-wg] List topics for this week

Fri Jun 16 11:45:00 UTC 2017

Yes – what Michele said, and Volker seems to have read it incorrectly.

  *   I said RDS server (WHOIS or otherwise), leaving protocol aside.  Assuming any kind of registration data is available, it has to be served from somewhere.  So identify the server where the data came from.  That’s what is done now; I suggest continuing to do so in the future.
  *   As we all know, under GNSO policy currently being implemented, the need for registrar-run RDS servers will go away once .COM, .NET, and .JOBS finally go from thin  thick.  However, some on the WG seem to want some sort of regime in which registrars retain the contact data and might need to serve it themselves under certain situations – in other words a return to a thin registry model for every gTLD.

--Greg

From: Michele Neylon - Blacknight [mailto:michele at blacknight.com]
Sent: Friday, June 16, 2017 5:25 AM
To: Volker Greimann <vgreimann at key-systems.net>; Greg Aaron <gca at icginc.com>; gnso-rds-pdp-wg at icann.org
Subject: Re: [gnso-rds-pdp-wg] List topics for this week

Volker

I think you may have misunderstood what Greg was suggesting.

He’s not suggesting listing a registrar whois server (or whatever it’s called) but the address / location of *the* server / service that will have the information.

As you rightly point out, that probably won’t have anything to do with the registrar in the future.

Regards

Michele

--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,R93 X265,Ireland  Company No.: 370845

From: <gnso-rds-pdp-wg-bounces at icann.org<mailto:gnso-rds-pdp-wg-bounces at icann.org>> on behalf of Volker Greimann <vgreimann at key-systems.net<mailto:vgreimann at key-systems.net>>
Date: Friday 16 June 2017 at 09:52
To: Greg Aaron <gca at icginc.com<mailto:gca at icginc.com>>, "gnso-rds-pdp-wg at icann.org<mailto:gnso-rds-pdp-wg at icann.org>" <gnso-rds-pdp-wg at icann.org<mailto:gnso-rds-pdp-wg at icann.org>>
Subject: Re: [gnso-rds-pdp-wg] List topics for this week

Hi Greg,

if there are no more whois servers, there is nothing to point to. So it would be less of a question of hiding it and more a question of does it makes sense if it points to nirvana?

Best,

Volker

Am 14.06.2017 um 19:14 schrieb Greg Aaron:
No – the identity of the server (RDAP, WHOIS, or otherwise) is useful whether the server is operated by the registry or a registrar.  It tells the source (provenance) of the data.

Plus, what is the compelling reason to hide it?  The information is useful, harms no one, and is not personal data.

“Because that field’s related to WHOIS and not a future protocol” is not a good or applicable reason.

From: gnso-rds-pdp-wg-bounces at icann.org<mailto:gnso-rds-pdp-wg-bounces at icann.org> [mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Volker Greimann
Sent: Wednesday, June 14, 2017 12:52 PM
To: gnso-rds-pdp-wg at icann.org<mailto:gnso-rds-pdp-wg at icann.org>
Subject: Re: [gnso-rds-pdp-wg] List topics for this week

To open the discussion topic of this week, I suggest to remove the Whois server from the list of public details merely for the fact that whois and registrar whois servers will no longer exist once RDS comes into play. See also 2013 RAA RDDS Spec, Art. 1:

"Until ICANN requires a different protocol, Registrar will operate a WHOIS service available via port 43 in accordance with RFC 3912, and a web-based Directory Service providing free public query-based access to at least the elements set forth in Section 3.3.1.1 through 3.3.1.8 of the Registrar Accreditation Agreement in the format set forth in Section 1.4 of this Specification."

When we are done, RDS will be that different protocol. If not our work was for naught anyway.

Best,

Volker

Am 14.06.2017 um 16:09 schrieb Gomes, Chuck via gnso-rds-pdp-wg:
One of the things we forgot to do at the end of our agenda yesterday was to identify the list discussion topics that everyone is asked to focus on this week.  Fortunately as a result of the discussion in the meeting and the questions in the poll, it appears that most everyone naturally focused on the appropriate topics which include the questions in the poll as well as the tentative conclusions that were reached in the meeting.  Here is a summary of the focus topics for this week:

New agreements reached and accepted as tentative conclusions

  *   The WG agreed to adopt the term "minimum public data set" to refer to the set of data elements deliberated thus far - that is, the list of fields that will always be public no matter the gTLD; short form focus topic = ‘minimum public data set’.
  *   The WG agreed to add DNSSEC info to the ‘minimum public data set’; short form focus topic = ‘DNSSEC Info’.
  *   The WG agreed that the expiration date should not be removed from the "Minimum Public Data Set"; short form of focus topic = ‘Expiration Date’.

From the poll

  *   Purposes of minimum public data set elements identified to date:

     *   Domain name
     *   Registrar name
     *   Registrar ID (Registrar IANA ID)
     *   Whois Server & Referral URL
     *   Name Servers
     *   Statuses
     *   Updated Date, Creation Date, Expiration Date
(These topics may be discussed as a whole or as individual discussion topics.)

According to our recently instituted procedures, please limit list discussions to the above topics this week.  As a reminder, the three rules that are particularly applicable are:

  1.  Discussion topics must be narrowly defined.
  2.  Responses must focus on the narrowly defined topics.
  3.  Ok to note dependency on another topic and state assumptions made, but keep focus on-topic.

Thanks for your cooperation.

Chuck

_______________________________________________

gnso-rds-pdp-wg mailing list

gnso-rds-pdp-wg at icann.org<mailto: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<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>

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.

--