[RFCI-Discuss] IPv6 Bogons

[Simon Arlott]

On 26/11/09 18:02, Derek J. Balling wrote:
> So, a long time ago, when I was first getting IPv6 support for  
> bogusmx, I was given (onlist? privately?) by someone:
> 
>      my @six_bogons = ('0000::/8', '0100::/8', '0200::/7', '0400::/6',
>                        '0800::/5', '1000::/4',
>                        '4000::/3',
>                        '6000::/3', '8000::/3', 'A000::/3', 'C000::/3',
>                        'E000::/4', 'F000::/5', 'F800::/6', 'FC00::/7',
>                        'FE00::/9', 'FE80::/10', 'FEC0::/10',  
> 'FF00::/8');
> 
> So now, reference:
> 
> 	http://www.rfc-ignorant.org/tools/detail.php?domain=alteredstates.info&submitted=1196030819&table=bogusmx
> 
> which has, essentially, this:
> 
> alteredstates.info.    86400    IN    AAAA    ::ffff:125.236.218.218
> 
> So...
> 
> - is this valid?

Not really. It may work, depending on the system, but they should be
using an A record for it.

It's explained in http://www.ietf.org/rfc/rfc4038.txt which states that
support for it may be disabled by default.

> - does the list of IPv6 bogons needs to be corrected in some fashion?

No, but you could add 2001:DB8::/32 which is the direct equivalent of
192.0.2.0/24, 198.51.100.0/24 or 203.0.113.0/24.

RFC3849: IPv6 Address Prefix Reserved for Documentation

> Again, what that list should contain is SIMPLY, "RFC-mandated  
> unassigned space" (e.g., the equivalent of RFC1918 space, multicast  
> ranges, permanently reserved, etc., etc.).

The only valid address range for global unicast use is still 2000::/3.

http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space

-- 
Simon Arlott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3632 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.megacity.org/pipermail/rfci-discuss/attachments/20091126/6e8e832d/attachment.bin