I wrote earlier:
The issue is the status of 128.66.0.0/16. This block, TEST-B, has been
used for example purposes. There is no RFC that talks about this
block, but my understanding is that IANA/ARIN have marked it as
reserved. If you search the Internet you will find at least some
number of examples and firewall rule sets that use this block, but I
have no good idea about how widespread such usage is.
What should we do about this block? Some of the potential answers
include documenting its role, marking it as reserved but deprecating
its use in examples, and returning it to the free pool immediately
(with a warning sign about possible filtering problems).
Geoff brought up the argument that RFC 3330 already effectively released
this block, as it did not list it as a special purpose block. Having
read the responses on this thread and having talked to several people
off-line, I'm getting the sense that returning 128.66.0.0/16 to the free
pool should be the recommended action. (Or recognizing that it was
already returned there earlier ...)
Is everyone happy with this course of action?
We still have no exact information about how widespread the use of this
block in example is. Google finds some examples and two books from
O'Reilly published in the 1990s have used it. We also intend to post a
question in registry and operator forums to solicit further comments.
Hopefully that will reveal any widespread usage.
I also believe that it would be better to explicitly document the fact
that this block is no longer reserved for this purpose. Here are some
suggested words that could go to draft-iana-ipv4-examples, Section 6:
Note that 128.66.0.0/16 has been used for some examples in
the past . However, this block did not appear in the list of
special prefixes in RFC 3330 or its successors, and the block
is therefore not reserved for any special purpose. The block
can be used for regular address assignments with caution.
Jari Arkko
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf