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] RIPE NCC Makes Record Number of IPv6 Allocations
- Previous message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
- Next message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mohsen Souissi
mohsen.souissi at nic.fr
Fri Dec 14 00:42:43 CET 2007
On 14 Dec, Jeroen Massar wrote: | Mohsen Souissi wrote: | > On 13 Dec, Ray Plzak wrote: | > | Receiving the address space is one thing, using it is another. In other words in the case of IPv6 to date allocation has not necessarily meant implementation. It will be more interesting when all of the IPv6 allocated to date is actually put in use. I note that this is true in all of the regions. | > | | > | > ==> So here's a proposal: | > | > <Provocation> | > What if RIRs monthly published on their websites and | > mailing-lists the TOP 10 of LIRs/Customers who received an allocation | > and haven't used it for ages? Would that be a further incentive to | > eventually start deployment? ;-) | > </Provocation> | | That is already available for a long long time, just check GRH. | (http://www.sixxs.net/tools/grh/dfp/ etc etc) ==> Yes, I know your site, it is very useful btw, but you are not an RIR ;-) | BUT always note, presence in BGP doesn't mean that it is actually being | announced by the owning ISP and it doesn't tell either if behind that | route announcement there actually is anything at all that is even | remotely usable... ==> Thta's why I talked about "deployment" in my provocation above. | I rather see an announcement like that from the folks from free.fr who | simply get a prefix*1, turned it on with working global*2 transit by | getting the transit from a good transit party, then simply pushing an | update to their CPE's and presto, native IPv6 for all their customers | who have IPv6 enabled on their hosts. ==> Yes, it is among the largest ADSL ISPs in France and it has turned on a special "6to4" yesterday (called "6to4rd", an old proposal of "Rémy Désprès" at IETF and which he proposed to Free and they accepted to assign /64s out of its /32, the right-most bits beeing those of the fixed public IPv4 address of the subscriber)... and that explains what you see ;-) Cheers, Mohsen. | | Greets, | Jeroen | | -- | | *1 = they seem to also have a 'test' prefix which is an IX prefix. | *2 = There are of course people who don't update their filters and that | is why their block which falls under 2a01::/16 is getting filtered by some. | | Reminder folks: When you have filters, you have to actually maintain them...
- Previous message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
- Next message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]