[noise] NoiseSocket and payload padding in handshake messages

[Christopher Wood]

On Wed, Apr 18, 2018 at 11:46 AM Trevor Perrin <trevp at trevp.net> wrote:

> On Wed, Apr 18, 2018 at 2:35 PM, Alexey Ermishkin <scratch.net at gmail.com>
wrote:
> > Should we just add a note on 2 bytes field in encrypted handshake
payload or also accompany it with counting formulas?

> We should definitely clarify section 2.3 here:


https://github.com/noiseprotocol/noisesocket_spec/blob/master/output/noisesocket.pdf

> We could also clarify section 5 (API) as Nemanja suggested.  I'm not
> sure how useful the API section is turning out to be, we could also
> describe this section more clearly as a "recommendation" or remove it
> entirely.  Would be interesting to hear from other implementers or
> potential implementers what they think of the API.

FWIW, not being an implementer myself, I think it makes more sense to punt
the API section altogether. One could also move it to an appendix and make
clear it's a recommendation. It seems to be an unnecessary implementation
detail now.

Best,
Chris