This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
- Previous message (by thread): [ipv6-wg] not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
- Next message (by thread): [ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Christian Seitz
chris at in-berlin.de
Tue Jul 26 09:01:31 CEST 2011
Hi Gert, On Mon, 25 Jul 2011, Gert Doering wrote: > On Mon, Jul 25, 2011 at 11:37:05AM +0200, Sander Steffann wrote: >>> 5) ? >> >> Adapt uRPF so that it does't filter ICMP error messages. Whether this >> is useful depends on how much ICMP error messages with unreachable >> source addresses we expect to see? When people/organizations start to >> use ULA addresses it might be more than we see now. > > Indeed this sounds like a good "option #5". > > Christian, can your gear do IPv6-uRPF-with-permit-ACLs in Hardware? > > (My gear can only do IPv6-uRPF in software, no matter what options I > use, so we currently filter by ACL) both Juniper MX960 and Cisco CRS-1 are able to do IPv6 uRPF incl. permit ACL (Cisco) and fail-filter (Juniper) in hardware so we would like to use it as for IPv4. Regards, Chris
- Previous message (by thread): [ipv6-wg] not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
- Next message (by thread): [ipv6-wg] Re: not announcing IXP IPv6 peering lan prefixes in global BGP table possibly breaks PMTUD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]