[RDS-WHOIS2-RT] NextGen Registration Data Distribution Service

Fri Jul 7 12:48:02 UTC 2017

While I agree that purpose is a central question and we will not be able 
to deal with data protection issues until we cut that gordian knot, 
since we just spent weeks on it in RDS I doubt we should attempt it in 
the Who2 review.

I think if we stick to a very tight interpretation of the last review's 
recommendations, and sail very tight to the wind, we can get through 
this in a reasonable time.

Stephanie

On 2017-07-07 04:36, Volker Greimann wrote:
>
> The problem about asking this question is that to do so, we would 
> first have to define the purpose of Whois and that is a bees nest 
> because everyone only feels his part of the elephant in the darkness 
> on that topic.
>
> Not saying that we shouldn't do it anyway, but it would complicate our 
> work significantly.
>
> Best,
>
> Volker
>
>
> Am 06.07.2017 um 17:37 schrieb Alan Greenberg:
>> I am less sure than Carlton that we MUST discuss this. I have no 
>> problem with discussing whether the current WHOIS protocol is fit for 
>> purpose, *_but it better be a pretty short discussion_*! If anyone 
>> has a good argument why it IS fit for purpose, it should be shared 
>> pretty quickly.
>>
>> The inability of a 7-bit protocol to handle today's IDN world, and 
>> the inability to handle any level of 
>> authorization/authentication/gating (which is generally understood to 
>> be necessary to allow critical information to be collected but not 
>> universally displayed in support of privacy legislation) makes the 
>> answer pretty clear. And as the charter Carlton points to indicates, 
>> this has been clear for quite some time.
>>
>> This is a REVIEW team. I believe it is well beyond our scope to 
>> debate whether the current protocol can be modified to meet new 
>> needs, to specify or design a replacement or to review possible 
>> replacements. And I have little interest in debating whether any new 
>> protocol should be called WHOIS (pretending it is the same), 
>> WHOIS-Mark-2, RDAP, WEIRDS, WIERDS or Betelgeuse.
>>
>> Alan
>>
>>
>> At 05/07/2017 10:08 AM, Carlton Samuels wrote:
>>
>>> Dear All:
>>> I believe this review will have to answer the question as to whether 
>>> the current WHOIS protocol is fit to purpose in a evolved DNS 
>>> environment in one or other job stream.  Some may recall that the 
>>> RDAP is being proposed as a fit and proper replacement.
>>>
>>> You may wish for background to examine the IETF charters for Web 
>>> Extensible Internet Registration Data Service (WEIRDS) from whence 
>>> came RDAP.
>>>
>>> https://tools.ietf.org/wg/weirds/charters 
>>> <https://tools.ietf.org/wg/weirds/charters>
>>>
>>> Best,
>>> -Carlton
>>>
>>> ==============================
>>> /Carlton A Samuels/
>>> /Mobile: 876-818-1799
>>> //Strategy, Planning, Governance, Assessment & Turnaround/
>>> =============================
>>> Content-Type: text/plain; charset="us-ascii"
>>> Content-Transfer-Encoding: 7bit
>>> Content-Disposition: inline
>>> X-Microsoft-Exchange-Diagnostics:
>>> 1;DM5PR03MB2714;27:B4FAKC1/EM3XOvHOPyoJ57PmCR+VxY4KD2MBdt6vWtlFgLD4tOOlcsV3foNFR93KAoIM9yzc2f7ovNf8Z27tswcz7fr1TllQNyArpqDRUCTG3fAIGxT2DaVNoDvfJnqPlCyckJle2pLGGdCKNOvr+w==
>>> X-Microsoft-Antispam-Mailbox-Delivery:
>>> ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(520000050)(520002050)(750028)(400001001223)(400125100095)(61617095)(400001002128)(400125200095);
>>>
>>> _______________________________________________
>>> RDS-WHOIS2-RT mailing list
>>> RDS-WHOIS2-RT at icann.org
>>> https://mm.icann.org/mailman/listinfo/rds-whois2-rt 
>>> <https://mm.icann.org/mailman/listinfo/rds-whois2-rt>
>>
>>
>> _______________________________________________
>> RDS-WHOIS2-RT mailing list
>> RDS-WHOIS2-RT at icann.org
>> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
> -- 
> 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.
>
>
>
>
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20170707/78d46e9e/attachment-0001.html>