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/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Previous message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Next message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friacas
cfriacas at fccn.pt
Sat Mar 24 16:08:10 CET 2007
On Sat, 24 Mar 2007, Trent Lloyd wrote: >>>> It is not reachable from me (2a01:d0::11:1) :( >>> >>> It looks like your prefix is being filtered by an upstream ISP. We've >>> contacted them and asked them to correct this. >> >> Go figure... some choose not to filter out 3ffe::'s while others are >> filtering IPv6 Unicast production address space. ;-) > > I think there are some people that haven't woken up to the fact address > space is being allocated out of more than just 2001:: now, for example I > currently have some space from 2402:: (2402:8000::/32 specifically) and > it seems a few people are possibly filtering this, among other things I > can't get to isc.org. > > Cheers, > Trent Good that you are complaining. It's the 1st step to see it solved! :-) Cheers, Carlos
- Previous message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
- Next message (by thread): [ipv6-wg] IPv6 Deployment Panel at ICANN, Lisbon
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]