Guidelines/Guidelines-for-example-data.md

@@ -10,17 +10,19 @@ In the examples, the numeric placeholder value convention is:
 | `m` | Decimal number |
 | `n` | Decimal number |
 | `x` | Hexadecimal number |
+| `z` | Decimal number |
+
 
 # DNS name (including email address domains)
 
-[RFC 2606 section 2](https://datatracker.ietf.org/doc/html/rfc2606#section-2) reserves four top level domains for test and documentation purposes:
+IETF RFC 2606 section 2 reserves four top level domains for test and documentation purposes:
 
 * `.test`
 * `.example`
 * `.invalid`
 * `.localhost`
 
-[RFC 2606 section 3](https://datatracker.ietf.org/doc/html/rfc2606#section-3) also states that IANA reserves the following second level domain names for example and documentation purposes:
+IETF RFC 2606 section 3 also states that IANA reserves the following second level domain names for example and documentation purposes:
 
 * `.example.com`
 * `.example.net`
@@ -38,57 +40,93 @@ References:
 * [IETF RFC 2606 - Reserved Top Level DNS Names](https://tools.ietf.org/html/rfc2606)
 * [IETF RFC 6761 - Special-Use Domain Names](https://tools.ietf.org/html/rfc6761)
 
+
+# EUI-48
+
+See [MAC address](#MAC-address).
+
+IETF RFC 9542 section 2.1.2 describes the EUI-48 values for documentation.
+
+EUI-48 was formerly known as a MAC address.
+
+Examples:
+| MAC address range | Description |
+|-------------------|-------------|
+| `00:00:5e:00:53:xx` | Unicast |
+| `01:00:5e:90:10:xx` | Multicast |
+
+**Note**: Our preference is to use lower-case (not upper-case) hexadecimal, and colon (not dash) separators.
+
+References:
+
+* [IETF RFC 9542 - IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters](https://tools.ietf.org/html/rfc9542)
+
+
 # EUI-64
 
+IETF RFC 9542 sections 2.2.2 and 2.2.3 describes various EUI-64 values for documentation.
+
 Examples:
+
 | EUI-64 range | Description |
 |--------------|-------------|
-| `00:00:5e:ef:10:00:00:xx` | Unicast, general |
-| `00:00:5e:ff:fe:00:53:xx` | EUI-48 (MAC address) derived |
-| `01:00:5e:ff:fe:90:10:xx` | Multicast, general |
-| `02:00:5e:10:00:00:00:xx` | Modified EUI-48, for IPv6 from EUI-48 MAC address |
+| `00:00:5e:ef:10:00:00:xx` | General unicast |
+| `00:00:5e:fe:c0:00:02:xx` <br>`00:00:5e:fe:c6:33:64:xx` <br>`00:00:5e:fe:cb:00:71:xx` | IPv4 derived unicast |
+| `00:00:5e:ff:fe:00:53:xx` | EUI-48 (MAC address) derived unicast |
+| `01:00:5e:ef:10:00:00:xx` | General multicast |
+| `01:00:5e:fe:c0:00:02:xx` <br>`01:00:5e:fe:c6:33:64:xx` <br>`01:00:5e:fe:cb:00:71:xx` | IPv4 multicast, derived from IPv4 unicast |
+| `01:00:5e:ff:fe:90:10:xx` | EUI-48 (MAC address) derived multicast |
+| `02:00:5e:10:00:00:00:xx` | Modified EUI-64, for IPv6 interface identifiers |
 
 **Note**: Our preference is to use lower-case (not upper-case) hexadecimal, and colon (not dash) separators.
 
 References:
 
-* [IETF RFC 7042 - IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters section 2.2.3](https://tools.ietf.org/html/rfc7042)
+* [IETF RFC 9542 - IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters](https://tools.ietf.org/html/rfc9542)
+
 
 # IMEI
 
-We don't have a solution here yet. Research notes:
+An IMEI is comprised of a 6 digit Type Allocation Code (TAC) and an 8 digit serial number.
+
+As at July 2025 there are not IMEI ranges for documentation.
+GSMA TS.06 section 9 describes TACs for test purposes.
 
-* An IMEI is broken up into TAC + Serial.
-* The first 2 digits of the TAC is the "Reporting Body Identifier" (RBI).
-* RBIs are managed by GSMA, per GSMA TS.06.
-* There are test RBIs, and we could see if there's a reserved value for documentation.
+Examples:
 
-E.g., See "00 44" in GSMA TS.06 annex B, allocated by John Talbot @ TUV SUD.
+| IMEI range | Description |
+|------------|-------------|
+| 0044nnnnzzzzzz | Test IMEI range for all countries except North America. `nnnn` is a manufacturer code, and `zzzzzz` is the serial number. Refer to GSMA TS.06 section 9.1. |
+| 001nnn00zzzzzz | Test IMEI range for North America. `nnn` is the MNC of the allocating body. `zzzzzz` is the test handset model and serial number. Refer to GSMA TS.06 section 9.2. |
 
 References:
 
-* [International Mobile Equipment Identity](https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity)
-* [Type Allocation Code](https://en.wikipedia.org/wiki/Type_Allocation_Code)
-* [Reporting Body Identifier](https://en.wikipedia.org/wiki/Reporting_Body_Identifier)
-* [GSMA TS.06 IMEI allocation and approval process annexes A and B](https://www.gsma.com/newsroom/resources/ts-06-imei-allocation-and-approval-process-2/)
+* [GSMA TS.06 IMEI allocation and approval process](https://www.gsma.com/newsroom/gsma_resources/ts-06-imei-allocation-and-approval-process-2/)
+* Wikipedia: [International Mobile Equipment Identity](https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity)
+* Wikipedia: [Type Allocation Code](https://en.wikipedia.org/wiki/Type_Allocation_Code)
+
 
 # IMSI
 
-ETSI TS 123 003 clause 2.2 describes the IMSI as up to 15 digits:
+ETSI TS 123 003 clause 2.2 and Rec. ITU-T E.212 clause 6.1 describe the IMSI as up to 15 digits:
 
 * 3 digits Mobile Country Code (MCC)
 * 2-3 digits Mobile Network Code (MNC)
-* 9-10 digits Mobile Subscriber Identification Number (MSIN)
+* 1-10 digits Mobile Subscriber Identification Number (MSIN). 
 
-Allocate IMSIs with the leading 5-6 digits per [Mobile Country Code (MCC) and Mobile Network Code (MNC)](#mobile-country-code-mcc-and-mobile-network-code-mnc). The remaining 9-10 digits of MSIN may be any digits.
+Allocate IMSIs with the leading 5-6 digits per [Mobile Country Code (MCC) and Mobile Network Code (MNC)](#mobile-country-code-mcc-and-mobile-network-code-mnc). The remaining 1-10 digits of MSIN may be any digits. In theory the resulting IMSI can be fewer than 15 digits, but generally IMSIs are 15 digits.
 
 References:
 
-* [Mobile Country Code (MCC) and Mobile Network Code (MNC)](#mobile-country-code-mcc-and-mobile-network-code-mnc)
 * [ETSI TS 123 003: "Numbering, addressing and identification (3GPP TS 23.003)"](https://www.etsi.org/deliver/etsi_ts/123000_123099/123003/)
+* [Mobile Country Code (MCC) and Mobile Network Code (MNC)](#mobile-country-code-mcc-and-mobile-network-code-mnc)
+* [Rec. ITU-T E.212 (06/24): "The international identification plan for public networks and subscriptions"](https://www.itu.int/rec/T-REC-E.212-202406-I/en)
+
 
 # IPv4 address/prefix
 
+IETF RFC 5737 section 3 describes IPv4 addresses for documentation, and IETF RFC 6598 section 7 describes the IPv4 prefix for shared address space.
+
 Examples:
 | IPv4 prefix | Description |
 |-------------|-------------|
@@ -104,12 +142,15 @@ References:
 * [IETF RFC 5737 - IPv4 Address Blocks Reserved for Documentation](https://tools.ietf.org/html/rfc5737)
 * [IETF RFC 6598 - IANA-Reserved IPv4 Prefix for Shared Address Space](https://tools.ietf.org/html/rfc6598)
 
+
 # IPv6 address/prefix
 
+IETF RFC 3849 section 2 describes IPv6 prefixes for documentation.
+
 Examples:
 | IPv6 prefix | Description |
 |-------------|-------------|
-| `2001:DB8::/32` | IPv6 prefix allocated for documentation purposes |
+| `2001:db8::/32` | IPv6 prefix allocated for documentation purposes |
 
 Use IPv6 addresses from these prefixes.
 
@@ -119,61 +160,55 @@ References:
 
 * [IETF RFC 3849 - IPv6 Address Prefix Reserved for Documentation](https://tools.ietf.org/html/rfc3849)
 
-# MAC address (EUI-48)
 
-Examples:
-| MAC address range | Description |
-|-------------------|-------------|
-| `00:00:5e:00:53:xx` | Unicast |
-| `01:00:5e:90:10:xx` | Multicast |
+# MAC address
 
-**Note**: Our preference is to use lower-case (not upper-case) hexadecimal, and colon (not dash) separators.
-
-References:
+See section [EUI-48](#eui-48).
 
-* [IETF RFC 7042 - IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters section 2.1.2](https://tools.ietf.org/html/rfc7042)
 
 # Mobile Country Code (MCC) and Mobile Network Code (MNC)
 
 The combination of the MCC and MNC is often referred to as the PLMN, and is used as the first 5-6 digits of an [IMSI](#imsi).
 
+Rec. ITU-T E.212 appendix III allocates MCC and MNCs for testing purposes.
+
 Examples:
 | MCC | MNC | Description |
 |-----|-----|-------------|
-| `001` | `01` | Test network (unofficial ?) |
-| `001` | `001` | Test network (unofficial ?) |
-| `999` | `99` | Internal use |
-| `999` | `999` | Internal use |
+| `999` | `99`  | Test MCC and 2 digit MNC |
+| `999` | `999` | Test MCC and 3 digit MCC |
 
 References:
 
-* [Mobile Country Code](https://en.wikipedia.org/wiki/Mobile_country_code)
-* [ITU Operational Bulletin No. 1156](https://www.itu.int/pub/T-SP-OB.1156-2018)
+* Wikipedia: [Mobile Country Code](https://en.wikipedia.org/wiki/Mobile_country_code)
+* [Rec. ITU-T E.212 (06/24): "The international identification plan for public networks and subscriptions"](https://www.itu.int/rec/T-REC-E.212-202406-I/en)
+
 
 # Phone numbers
 
 Various countries allocate "drama" or "fiction" ranges - see the references.
 
-ITU E.164 doesn't appear to have any reserved dialing codes for test or example purposes, but does give a list of reserved and spare codes.
+ITU-T E.164 doesn't appear to have any reserved country dialing codes for test or documentation purposes, but does give a list of reserved and spare codes.
 
 Examples:
 | E.164 range | Description |
 |-------------|-------------|
 | `1 mmm 555 01nn` | US, CA: geographic area for area prefix `mmm` |
-| `33 1 99 00 nn nn` | FR: Île-de-France / Paris (TBC) |
-| `33 6 39 98 nn nn` | FR: mobile services (TBC) |
+| `33 1 99 00 nn nn` | FR: Île-de-France / Paris |
+| `33 6 39 98 nn nn` | FR: mobile services |
 | `44 1632 960 nnn` | UK: no geographic area |
 | `44 20 7946 0nnn` | UK: London |
 | `44 7700 900 nnn` | UK: mobile services |
-| `49 171 39200 nn` | DE: mobile services |
-| `49 176 040690 nn` | DE: mobile services |
+| `49 171 39200 nn` | DE: mobile services (Telekom) |
+| `49 176 040690 nn` | DE: mobile services (O2-Telefónica) |
+| `49 152 28817386`` | DE: mobile services (Vodafone). Other numbers with various prefixes available. |
 | `49 30 23 125 nnn` | DE: Berlin |
-| `61 2 5550 nnn` | AU: Canberra |
+| `61 2 5550 nnnn` | AU: Canberra |
 | `61 491 570 006` | AU: mobile service. Other numbers with various prefixes available. |
 
 References:
 
-* [ITU E.164 dialling code bulleting](https://www.itu.int/dms_pub/itu-t/opb/sp/T-SP-E.164D-2016-PDF-E.pdf)
+* [List of Recommendation ITU-T E.164 assigned country codes](http://handle.itu.int/11.1002/pub/80eefa4f-en)
 * [AU: Phone numbers for use in TV shows, films and creative works](https://www.acma.gov.au/phone-numbers-use-tv-shows-films-and-creative-works)
 * [DE: Rufnummern für Medienproduktionen („Drama Numbers“) (_Numbers for media productions ("Drama Numbers")_) (pdf)](https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Nummerierung/Rufnummern/Mittlg148_2021.pdf?__blob=publicationFile&v=1)
 * [FR: Décision n°2018-0881 modifiée de l'Autorité de régulation des communications électroniques et des postes en date du 24 juillet 2018 établissant le plan national de numérotation et ses règles de gestion (pdf)](https://www.arcep.fr/uploads/tx_gsavis/18-0881.pdf)