Daniel, I've put up an Etherpad here: https://etherpad.wikimedia.org/p/gnso-rds-pbstatement-0 I did a quick search to see if there was an ICANN Etherpad and didn't find one. If there is a better spot we can move there. I also made a note that since RDAP seems to be included as a sort of mandate that we should document that too, although I have no proposed text since I'm a bit uncertain if this is true or if it is to what extent. ;) Cheers, -- Shane At 2016-06-30 10:20:54 +0300 DANIEL NANGHAKA <dndannang@gmail.com> wrote:
Thanks Shane,
Then I suggest we could use possible alternatives like the Etherpad http://etherpad.org since China does not like google.
ᐧ
Regards Nanghaka Daniel K. Executive Director - ILICIT Africa / Council Member - FOSSFA / Community Lead - ISOC Uganda Chapter Mobile +256 772 898298 (Uganda) Skype: daniel.nanghaka
----------------------------------------- *"Working for Africa" * -----------------------------------------
On Thu, Jun 30, 2016 at 10:01 AM, Shane Kerr <shane@time-travellers.org> wrote:
Daniel,
Thank you very much for kicking this off!
At 2016-06-30 09:19:38 +0300 DANIEL NANGHAKA <dndannang@gmail.com> wrote:
Please find the attached the draft problem statement.
I think we need to have a few sentences documenting the constraints of the RDS WG:
The RDS WG will not consider the questions of:
1. Whether publishing WHOIS-style data is necessary 2. What data registries will collect 3. How registry data is managed
I do not like these constraints, but if they are there then it I think that it is important to document them so it is clear that these are off-charter.
It would also be good to document where such limitations came from, but I don't know that.
If these are NOT limits, then I think the problem statement should include these questions as high-priority topics to be addressed before anything else.
I would also like to recommend probably we create a google doc for easy review and comments.
I don't really mind using a Google document for this, but it might be nice to try to find an alternate way to jointly edit stuff. (My reason is that China hates Google. When I am working out of my company's offices in Beijing it is a pain in the ass to use any Google cloud stuff.)
Cheers,
-- Shane