<div dir="ltr"><div><br></div><div>Hi all,</div><div><br></div>Quick status update for the Noise spec revision 34:<div><br></div><div>Noise Explorer is finishing an updated analysis, sounds like we'll get it this week.  If everything checks out, I'll publish the spec afterwards.</div><div><br></div><div>Thus it's a great time to do last-minute proof-reading, if anyone's so inclined.  There's a change log, so you can focus on the parts that were updated (or look at diffs):</div><div><br></div><div><div><div><a href="https://github.com/noiseprotocol/noise_spec/tree/rev34">https://github.com/noiseprotocol/noise_spec/tree/rev34</a></div><div><a href="https://github.com/noiseprotocol/noise_spec/blob/rev34/output/noise.pdf">https://github.com/noiseprotocol/noise_spec/blob/rev34/output/noise.pdf</a></div></div><div><br></div></div><div><br></div><div>Trevor</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 29, 2018 at 2:18 AM, Trevor Perrin <span dir="ltr"><<a href="mailto:trevp@trevp.net" target="_blank">trevp@trevp.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I updated revision 34 draft with:<br>
<br>
 * Security properties for deferred patterns in appendix, taken from<br>
Noise Explorer.<br>
<br>
 * Renamed "authentication" / "confidentiality" security properties in<br>
spec to "source" / "destination", since the Noise Explorer team<br>
pointed out these categories don't map directly to the previous terms.<br>
<br>
 * In section 10, clarified the distinction between "switch protocols"<br>
(a protocol that Bob switches to) and "fallback protocols" (a protocol<br>
that uses the fallback modifier).<br>
<br>
 * In section 10, removed some of the description of a "type byte";<br>
and generalized/renamed the "Type fields" discussion in "Application<br>
responsibilities" to discuss "Negotiation data".<br>
<br>
 * Added X1N pattern (which I forgot somehow; so needs to be added to<br>
Noise Explorer too).<br>
<br>
<br>
For the first two points, I'd like to follow-up with Noise Explorer<br>
team and see whether they agree with how the spec presents these<br>
properties.  In particular, do they still want 2 additional<br>
categories? [1].<br>
<br>
For the next 2 points:  we don't want to put NoiseSocket/NLS stuff in<br>
this spec, but I think exploring those things has improved our<br>
understanding of how to build things around Noise, so reflecting that<br>
better understanding in this spec makes sense.<br>
<br>
We could use proof-reading of the security properties table, that's a<br>
lot for me to transcribe from Noise Explorer..<br>
<br>
Other comments?<br>
<br>
I keep saying this, but hopefully we can publish this week.<br>
<br>
<br>
<a href="https://github.com/noiseprotocol/noise_spec/tree/rev34" rel="noreferrer" target="_blank">https://github.com/<wbr>noiseprotocol/noise_spec/tree/<wbr>rev34</a><br>
<a href="https://github.com/noiseprotocol/noise_spec/blob/rev34/output/noise.pdf" rel="noreferrer" target="_blank">https://github.com/<wbr>noiseprotocol/noise_spec/blob/<wbr>rev34/output/noise.pdf</a><br>
<br>
<br>
Trevor<br>
<br>
[1] <a href="https://github.com/noiseprotocol/noise_spec/tree/rev34" rel="noreferrer" target="_blank">https://github.com/<wbr>noiseprotocol/noise_spec/tree/<wbr>rev34</a><br>
</blockquote></div><br></div>