[RFCI-Discuss] IPv6 and BogusMX

Simon Arlott simon at arlott.org
Sun Mar 23 10:17:29 EDT 2008


On 23/03/08 13:53, Derek J. Balling wrote:
> It means I have no way of testing it. :-)
> 
> So here's what I need, you can do this privately to me if you like:
> 
>     - A couple syntactically valid IPv6 addresses ... things which I
> could use to

2001:4b10:1005:0:204:23ff:fea8:25f1
2001:4860:0:1001::68
2001:7fd::1
fd6c:7131:6575::40c1:4e59:9
fe80::250:8bff:fef2:4814
::

>         - prove that doing a straight MX_hostname -> valid_ipv6 test
> "passes"
>         - prove that doing MX points to IPv6 address fails


>     - A couple RFC-bogus IP addresses (as defined by the above-mentioned
> URL) so I can

Everything except 2000::/3 is bogus because it's not globally routable.
The IPv6 version of 192.0.2.0/24 is 2001:DB8::/32 (rfc3849).

Specific bogus address ranges that might be seen that would work on the 
right private network would be:
	::1 (localhost)
	::ffff:0:0/96 (ipv4-mapped addresses)
	fc00::/7 (unique local unicast)
	fe80::/10 (link local)
	fec0::/10 (site local, now deprecated)
Also,
	ff00::/8 (multicast)

>         - prove that situating an MX_hostname in bogon-IPv6-space will
> generate a "fail"
> 
> I'll throw those addresses (and a couple others) into my own personal
> little "scrap workspace" that I use for testing changes to bogusmx. Once
> I think it's "ready for prime-time", we'll push it live and hopefully,
> all five people that are using IPv6 will be ok. :-)
> 
> Cheers,
> D

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


More information about the RFCI-Discuss mailing list