Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more operational info to server and client documentation #153

Open
masomel opened this issue Dec 9, 2016 · 0 comments
Open

Add more operational info to server and client documentation #153

masomel opened this issue Dec 9, 2016 · 0 comments

Comments

@masomel
Copy link
Member

masomel commented Dec 9, 2016

Provide more details about the server's and the client's capabilities, what an operator needs to do to get a server or a client set up and running, and security considerations. As Bryan put it, make the READMEs more like a "tutorial".

Here are some other concrete questions that we should explicitly address in our documentation:

  • Is the operator of the server expected to create a new namespace, e.g., such that users sign up for a new “CONIKS identity” account?
  • If so, how does the CONIKS server interact with the DNS namespace it lives it, what are the integration requirements with DNS and other institutional networks, etc?
  • How do users request names in this namespace, how do names transfer ownership, etc.?
  • Can users bring their existing (E-mail) identities, submit them to the CONIKS server for verification, and the CONIKS server does an E-mail challenge/response to that E-mail account before incorporating the attestation into its next Merkle tree?
  • In this case, what challenge/response technologies are currently supported - E-mail? phone/sms?
  • Which are on the roadmap for the future?
@masomel masomel added this to the 0.2.0 milestone Dec 9, 2016
@vqhuy vqhuy modified the milestones: 0.3.0, 0.2.0 Apr 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants