Further clarify v7 field description

[LiosK]

Further clarify v7 field description

[kyzer-davis]

Seems logical enough to me. I am always down for further clarification so folks don't need to assume.
Also I am fine with posts here or over on that repo. I am watching both repos and the IETF mailer for changes to compile between drafts.

I'll slate this for Draft 01 of the biz doc and add it to my EITF 115 talking points.

[LiosK]

Should I post this to https://github.com/ietf-wg-uuidrev/rfc4122bis/issues ? Perhaps, it would be helpful if the new repository had a similar change proposal template.

[LiosK]

Alternatively, we can add several paragraphs below the bit layout figure to describe the spec using BCP 14 keywords like:

The unix_ts_ms field MUST be dedicated to a 48-bit big-endian unsigned integer representing Unix epoch millisecond timestamp as per Section 6.1. The 12-bit rand_a and 62-bit rand_b fields, jointly, MUST be filled with one of the following data:

1. pseudo-random data as per Section 6.8;
2. a big-endian unsigned integer representing fixed-length dedicated counter as per Section 6.2, with the remaining bits being padded with pseudo-random data as per Section 6.8; or,
3. a big-endian unsigned integer representing monotonic random counter as per Section 6.2.