Would breaking up the Crypto Operations chapter be useful

[athoelke]

With the addition of key wrapping and XOF, there are now fourteen sections in the Cyrpto Operations chapter.

In addition, to keep consistency across the specification, I aim to have every API definition be at outline level 4 - but ideally the PAKE section would have an extra level.

As done in many other crypto specifications, I am debating whether to split this chapter into Symmetric cryptography, Asymmetric cryptography, PAKE, and Other cryptographic services (as PAKE can be either symmetric or asymmetric, it can justiy its own chapter).

Also I am considering some heirarchy in the preamble 7 chapters - at the moment the top level chpater list tends to hide the API itself.

• Have the Design goals and Sample Architectures as sections within the Introduction
• Keep Functionality overview as a top level chapter
• Have Library conventions, Implementation considerations and Usage considerations as sections within a single chapter on Using this specification (?)