PASETO RFC (First Draft)

[paragonie-scott]

Thanks @tarcieri for recommending mmark.

To contribute to the RFC development.

1. Clone the rfc branch.
2. cd docs/RFC
3. Make your changes in paseto.md
4. Run the build.sh script.
5. Commit changes to paseto.md. Committing changes to the .txt file is not necessary.
6. Make a pull request against the rfc branch.

Once we're happy with the first draft, I'll merge this and email it to the IETF.

Closes #16

[rlittlefield]

Should there be a section related to the JSON encoding or the registered claims?

[paragonie-scott]

JSON is defined in a separate RFC. The registered claims deserve its own section.

[paragonie-scott]

I think we're also going to have to define XChaCha20-Poly1305 in a section too

[rlittlefield]

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.

[paragonie-scott]

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.)

[paragonie-scott]

I still need to add the Security Considerations and IANA Considerations sections, which I'm doing tonight.

[paragonie-scott]

Okay, I think I've incorporated changes that addressed your suggestions, @sjudson :)

[paragonie-scott]

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.

[lookyman]

when when