How about adding some additional text to section 2.7, such as:
6to4 prefixes are constructed by embedding an IPv4 address into an
IPv6 prefix according to [RFC3056]. Where the IPv4 address used to
construct such a prefix is not globally-unique (or is otherwise
reserved), the resulting 6to4 prefix is unlikely to be useful.
The following is a summary of 6to4 prefixes constructed using
special-use IPv4 addresses, as documented in [RFC3330]. IPv4
prefixes which appear in [RFC3330] but which are known to have
legimitate use on the public Internet at the time of writing are
not included. Operators are advised to derive a policy for
treatment of these 6to4 prefixes which is analogous to their policy
for the corresponding IPv4 addresses.
IPv4 Prefix Description 6to4 Prefix
0.0.0.0/8 "this network" [RFC1700] 2002::/24
10.0.0.0/8 private networks [RFC1918] 2002:a00::/24
14.0.0.0/8 "public data networks" [RFC1700] 2002:e00::/24
127.0.0.0/8 loopback addresses [RFC1700] 2002:7f00::/24
169.254.0.0/16 "link local" 2002:a9fe::/32
172.16.0.0/12 private networks [RFC1918] 2002:ac10::/28
192.0.2.0/24 "test net" 2002:c000:200::/40
(etc, etc)
Joe