Description
Classify an integer octet from zero through 255 by leading bits: below 128 as ncs, below 192 as rfc, below 224 as microsoft, and the remainder as future.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Classify an integer octet from zero through 255 by leading bits: below 128 as ncs, below 192 as rfc, below 224 as microsoft, and the remainder as future.
When to use this tool
Use Uuid Variant Bit Pattern Check when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter octet. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read variant, rfcVariant. Inspect rfcVariant before interpreting the associated values.
Classify an integer octet from zero through 255 by leading bits: below 128 as ncs, below 192 as rfc, below 224 as microsoft, and the remainder as future. Return rfcVariant for the second interval.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| octet | Octet | Required. Safe integer; minimum 0; maximum 255. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| variant | Variant | Required. Text; maximum UTF-16 length 8192. |
| rfcVariant | Rfc Variant | Required. Boolean. |
{
"input": {
"octet": 154
},
"output": {
"variant": "rfc",
"rfcVariant": true
}
}Limitations and assumptions
- The input is one already extracted variant octet, not a complete UUID. The label does not check version, UUID syntax, identifier uniqueness, or whether a reserved pattern is usable.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- Mac Eui Local Multicast Bit Check
Inspect the multicast and locally administered bits of a supplied MAC/EUI first octet.
- Uuid Version Nibble Consistency
Check hyphenated UUID shape and compare its version nibble with an expected value.