Hi Randy, To never have to revisit this point, I would suggest for a capability containing a char of value N, for the N extra MESSAGE to be read before the KA, the extra MESSAGEs being OPENs, which should have the Version to Identifier data zero’ed (and ignored) with then the extra capabilities to be considered as if they were present at the end of the current OPEN.
The extra OPEN being themselves up to 65k in size. Happy to provide an implementation to test against if we reach consensus. Thomas > On 9 Mar 2017, at 14:41, Randy Bush <[email protected]> wrote: > >> Thank you for sharing this scenario. It would indeed work at the small >> cost (or perhaps not so small) to require an extra round trip at setup >> time which is most likely un-avoideable whatever is done. > > then a double open. i.e. a 4096 open which has the extended capability > exchange and then an optional extended open > > randy _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
