-----BEGIN PGP SIGNED MESSAGE----- Hi,
Are the ones in the To line aware that you are breaking RFC3056 by announcing 6to4 more specifics? RFC3056 Section 5.2 point 3: 8<------------ 6to4 prefixes more specific than 2002::/16 must not be propagated in native IPv6 routing, to prevent pollution of the IPv6 routing table by elements of the IPv4 routing table. Therefore, a 6to4 site which also has a native IPv6 connection MUST NOT advertise its 2002::/48 routing prefix on that connection, and all native IPv6 network operators MUST filter out and discard any 2002:: routing prefix advertisements longer than /16. - ------------>8 Currently you are announcing, to the rest of the world: http://www.sixxs.net/tools/grh/lg/?find=2002::/16 2002:8c6d:106::/48 8447 1853 786 5623 6939 11537 9264 2002:8c6d:106::/48 12779 3549 6939 11537 9264 2002:8c6d:106::/48 6939 11537 9264 2002:c058:6301::/48 8447 1853 786 2002:c0e7:d405::/48 8447 1853 6680 1103 11537 7570 2002:c0e7:d405::/48 1103 11537 7570 2002:c0e7:d405::/48 12779 3549 6939 11537 7570 2002:c0e7:d405::/48 6939 11537 7570 2002:c8a2::/33 8447 1853 6680 1103 11537 6939 6939 15180 2002:c8a2::/33 12337 12337 12337 6939 6939 15180 2002:c8a2::/33 1103 11537 6939 6939 15180 2002:c8a2::/33 12779 3549 6939 6939 15180 2002:c8a2::/33 6939 6939 15180 2002:c8c6:4000::/34 8447 1853 6680 1103 11537 6939 6939 15180 2002:c8c6:4000::/34 12337 12337 12337 6939 6939 15180 2002:c8c6:4000::/34 1103 11537 6939 6939 15180 2002:c8c6:4000::/34 12779 3549 6939 6939 15180 2002:c8c6:4000::/34 6939 6939 15180 2002:c8ca:7000::/36 8447 1853 6680 1103 11537 6939 6939 15180 2002:c8ca:7000::/36 1103 11537 6939 6939 15180 2002:c8ca:7000::/36 12779 3549 6939 6939 15180 2002:c8ca:7000::/36 6939 6939 15180 Summing them up: 2002:8c6d:106::/48 140.109.1.6/32 AS9264 2002:c058:6301::/48 192.88.99.1/32 AS786 2002:c0e7:d405::/48 192.231.212.5/32 AS7570 2002:c8a2::/33 200.162.0.0/17 AS15180 2002:c8c6:4000::/34 200.198.64.0/18 AS15180 2002:c8ca:7000::/36 200.202.112.0/20 AS15180 NOTEZ BIEN: % Not assigned. Free in Brazilian block: 200.198.64.0/18 Is LACNIC the RIR or is NIC.BR the one? Seeing that a complete IPv4 /9 has been carved up to them and LACNIC doesn't handle anything else? 192.88.99.1/32 is *THE* anycast address, it is *NOT* routable.... And you don't own it either, please read RFC3068 and stop that foolish announcement. In whois.ripe.net this network is documented: route: 192.88.99.0/24 descr: RFC3068-ECIX origin: AS9033 mnt-by: ECIX-MNT mnt-routes: RFC3068-MNT changed: [EMAIL PROTECTED] 20030711 source: RIPE remarks: See RFC 3068 remarks: "An Anycast Prefix for 6to4 Relay Routers" remarks: Christian Huitema remarks: June 2001 Feel free to notify your "upstreams" that they should be filtering anything more specific in 2002::/16 and should probably not be announcing cross-RIR prefixes unaggregated. Please read: IPv6 Filter Recommendations by Gert D�ring http://www.space.net/~gert/RIPE/ipv6-filters.html Minimal IPv6 Peering by Robert Kie�ling http://ip6.de.easynet.net/ipv6-minimum-peering.txt Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / [EMAIL PROTECTED] / http://unfix.org/~jeroen/ iQA/AwUBP2G0kSmqKFIzPnwjEQJi4wCgkfxKSBKl/zzvPBGyFTQp3Bjx9CIAoJAO caSxGRfOBcF0VQ1G15QvNjaP =kO2/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
