[Cfrg] Editing work on github of draft-ladd-safecurves

[Watson Ladd <[e-mail]>]

Dear all,
To avoid clogging up the IETF with endless revisions, I've decided to
do the wordsmithing on github. Emails to me are still excellent ways
of communicating issues, but for those inclined to do typo work and
other valuable (and underappreciated) editing efforts, feel free to
examine an up-to-date copy at github.com/wbl/safecurvesdraft.

Quite a few people have argued that I need to explain the
double-and-add algorithm, even though it is standard. Then again I
have no idea what sort of implementation details are generally
considered necessary in a draft, especially when they are completely
unnecessary to specify the "what" of the behavior. This seems to me to
be the biggest issue of contention with regards to the draft: some
people want something ala RFC 6090, while I want to avoid massive
bloat with implementation details that anyone implementing this draft
probably knows anyway. This isn't a strongly principled stand on my
part, but I would like to see this move through swiftly.

Sincerely,
Watson Ladd