There are RFCs that cover the use of some network blocks for documentation as long as all you donât need a net bigger than IPv4 Class C.
IPv6 there is a big range. I am disappointed they didnât use 2001:D0C::/32.
https://tools.ietf.org/html/rfc5737
3.
Documentation Address Blocks
The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2),
and 203.0.113.0/24 (TEST-NET-3) are provided for use in
documentation.
https://tools.ietf.org/html/rfc3849
The document describes the use of the IPv6
address prefix 2001:DB8::/32 as a reserved prefix for use in
documentation.
From:
<openc2@lists.oasis-open.org> on behalf of "Considine, Toby" <Toby.Considine@unc.edu>
Date: Tuesday, October 9, 2018 at 11:18 AM
To: OASIS OpenC2 List <openc2@lists.oasis-open.org>
Subject: [openc2] Hollywood Phone Numbers
Also known as the âJenny Jennyâ problem
This thought came out of the detailed conversation on Address Serialization and the Examples at the end of the language call.
Movies have long been careful to use non-exchanges, phone numbers that cannot be assigned, perhaps to avoid causing the sleepless romantic to call the hero/heroine late at night and tormenting the hapless possessor
of the number. For a number of years after the rock song âJennyâ came out, the phone number 867-5309 was not assigned by phone companies.
In the same way specification can create a virtual DOS on the addresses chosen in the examples. Perhaps that is a reason to use a non-routable address for all examples.
No action required. It was just the thoughts rattling around in my head after the call.
tc