Joe Touch <[email protected]> wrote: > Version support is recommended by IANA (see RFC7506, Sec 7.5).
> Extensibility is a separate issue and doesn't replace the benefit of
> version support.
> The goal is to avoid needing to assign a new port number for GRASPv2 in
> the future.
> IMO, all messages (including NOOP) should start with a version number,
> and I'd suggest at least 2 bits (if not 4).
Everything is CBOR encoded, so we have no dependancy upon encoded bits on the
wire changing.
{Should CBOR change in an incompatible way, we'd need a new port number, true}
Otherwise, we could obsolete any of the M_ operations trivially.
We currently expect to encode the "first" layer as a CBOR array (which
creates the record boundary for TCP as well).
We could even decide that "version 2" would start with [M_GRASP2, [stuff]]
costing us perhaps two bytes, which is about the same as inserting a version
would cost, but I'm still not convinced we'd ever need to do that.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
