Okay, no worries; I understand. Thanks for the pointer in the right direction.
On Mon, Jan 4, 2016 at 4:17 PM, Keith Winstein <kei...@cs.stanford.edu> wrote: > Hi Zach -- I think, frankly, a rigorous spec is unlikely to happen soon > unless somebody really wants it. Most of the demand we get has been for new > features (scrollback, SSH-agent forwarding, server-side roaming, better > handling of new Unicode characters), many of which will require protocol > mods anyway. > > -Keith > > On Mon, Jan 4, 2016 at 3:22 PM, Zach Walton <zacw...@gmail.com> wrote: > >> Thanks Keith. Any plans to codify SSP into an RFC? I ask because it makes >> the barrier for entry as a developer lower, and easier to sell SSP as a >> good technical decision to a business or development team. >> >> On Mon, Jan 4, 2016 at 3:12 PM, Keith Winstein <kei...@cs.stanford.edu> >> wrote: >> >>> Short answer is, yes, source code is basically the definitive reference >>> (and mosh-paper.pdf / mosh-paper-draft.pdf). The state-synchronized objects >>> that define the Mosh protocol are in >>> https://github.com/mobile-shell/mosh/tree/master/src/statesync >>> >>> Best regards, >>> Keith >>> >>> On Mon, Jan 4, 2016 at 2:08 PM, Zach Walton <zacw...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I've trolled through the mosh-devel archives and didn't see an answer >>>> to this; is there a specification or RFC for SSP, or is ( >>>> https://mosh.mit.edu/mosh-paper-draft.pdf) the definitive source >>>> (along with the mosh source code)? >>>> >>>> Thanks! >>>> >>>> _______________________________________________ >>>> mosh-devel mailing list >>>> mosh-devel@mit.edu >>>> http://mailman.mit.edu/mailman/listinfo/mosh-devel >>>> >>>> >>> >> >
_______________________________________________ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel
