FNAL and ESNet - Phil DeMAr
ESnet has already deployed IPv6 in their backbone.
US Gov mandated to have IPv6 native on public services (dns, web, mail) by the 
end of Q3 2012. Second mile stone: 2014, all the clients must be native IPv6.
Labs are not pressed because Esnet has ipv4 addresses available; not many use 
cases; lack of resources.
But Labs will focus on the 2012 milestone. The ESCC group  has been put in 
place; it has 3 TF:
- Plaaning process
- technical implementation
- implication for security
Planning TF now working on a checklist as planning template.
Dave: can the document be shared?
Phil: yes, the documents will be available to the Hepix WG.
Dave: you didn't mention much the applications
Phil: WE're now focusing on the web,mail applications, security; applications 
are in the second phase. Labs are encouraged to build sand boxes for users to 
let them test their applications.


DESY - Kars
Desy is connected to DFn and they have already an IPv6 peering.
Almost all network devices already support ospfv3.
Firewall suports ipv6 already (Juniper)
RA is disabled. At the moment is static assignements and will go for dhcpv6.
No dedicated testbed, ipv6 is tested on the production network (few subnets).
Applications: testing mail servers and F5 loadbalancers.


INFN - Francesco
INFN has started testing v6 on 4 sites. Got /40 from GARR.
How to authorize access? ACls, 802.1x, IPsec?
Will go for dual-stack transition.
Most monitoring tools are still lacking v6 support.
When to do the transition? Risk of allowing v6 too early: it will be preferred 
and must be as good as v4.



IPv6 day
According to De-CIX, the IPv6 traffic stayed:
http://www.de-cix.net0cintent/network.html
EPFL experience:
http://ditwww.epfl.ch/SIC/SA/SPIP/Publications/IMG/pdf/fi-6-2011.pdf