Hi, my 2 cents:
(1) I think the solution is just not right. It's a quick and dirty way of doing
these things. The right way imo is defining a new RDAP extension (with a
dedicated attribute to identify the authoritative source)
(2) In my opinion there are other, existing, mechanisms for discoveri
Dear Scott,
Thanks for your comments. I've already updated them in the new version and will
submit it before the end of WGLC.
Regards,
Linlin
zhoulin...@cnnic.cn
From: Hollenbeck, Scott
Date: 2018-04-13 22:41
To: 'gal...@elistx.com'; 'regext@ietf.org'
Subject: Re: [regext] WGLC: draft-ietf-re
I have read this draft. I work for an agency which has deployed RDAP
in a globally connected context. I would welcome this draft
progressing because we are already in a situation where public
services designed to unite RDAP services could leverage this draft,
and I want to see strong coherence betw
