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

Alan Greenberg alan.greenberg at mcgill.ca
Thu Jul 6 15:37:09 UTC 2017


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20170706/a5ae28cd/attachment.html>


More information about the RDS-WHOIS2-RT mailing list