Hi Carsten,
(2012/09/05 17:13), Carsten Bormann wrote:
because 11nnnkkk turns into 11****** -- this loses visual access to the bit
allocation.
Again, this is all about the exposition, not about the technical content of the
proposal, so I'm not sure we need good consensus on what is the best style (we
only need to make sure there is no potential for misinterpretation).
I don't care if this is technical and editorial, but I do care the
quality of IETF specification. Honestly I think the current
representation is too loose, and I am afraid you would get the same
comment from others. If you think *** representation loses visual
access to the bit allocation, there can be other ways of
representation such as "| 1| 1|n0|n1|n2|k0|k1|k2|".
This is something to think about for general readers..
Thanks you,
Yoshihiro Ohba
Grüße, Carsten
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
