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] Usenix: Google deploys IPv6 for internal network

Previous message (by thread): [ipv6-wg] Usenix: Google deploys IPv6 for internal network
Next message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Carsten Schiefner ripe-wgs.cs at schiefner.de
Mon Dec 19 12:45:11 CET 2011

Florian, all -

Am 17.12.2011 13:45, schrieb Florian Weimer:
>> is an interesting read-up for at least some of you...
> 
> I wonder if they have implemented some form of source address
> validation and prevented unicast flooding, or if they essentially run
> without those safeguards inside each VLAN.  (With a hard limit of 256
> VLANs per building, those VLANs are probably rather large in some
> cases.)

maybe some Google employees being involved in v6 deployments - and I
know that the RIPE community has some on board: hint, hint! ;-) - want
to fill us in here?

Best,

	-C.

Previous message (by thread): [ipv6-wg] Usenix: Google deploys IPv6 for internal network
Next message (by thread): [ipv6-wg] RIPE-501 replacement document - IPsec question to community - we need your input.

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]