Closed paragonie-scott closed 6 years ago
Should there be a section related to the JSON encoding or the registered claims?
JSON is defined in a separate RFC. The registered claims deserve its own section.
I think we're also going to have to define XChaCha20-Poly1305 in a section too
I think we're also going to have to define XChaCha20-Poly1305 in a section too
Yes. The RFC I linked isn't enough to define the X.
This now defines HChaCha20 and uses it to build XChaCha20. (I'd like to ask @jedisct1 to spot-check this for accuracy when he has the time.)
I still need to add the Security Considerations and IANA Considerations sections, which I'm doing tonight.
Okay, I think I've incorporated changes that addressed your suggestions, @sjudson :)
I've updated the rules at the top: To avoid merge conflicts, please feel free to only change the .md
file if need be. I'll follow up any merge commits with a rebuilt .txt file commit.
Thanks @tarcieri for recommending mmark.
To contribute to the RFC development.
rfc
branch.cd docs/RFC
paseto.md
build.sh
script.paseto.md
. Committing changes to the.txt
file is not necessary.Once we're happy with the first draft, I'll merge this and email it to the IETF.
Closes #16