The IPv6 reality check

What we learned so far on the IPv6 distributed testbed

Francesco Prelz

INFN, sezione di Milano

(and members of the IPv6 group)


  1. Structure of the testbed.
  2. Enabled services (and why).
  3. Further steps: FTS and DPM (via SRM).
  4. Trying to help: Uberftp.
  5. Conclusions

Structure of the testbed

What does 'IPv6 tested' mean ?

Deploying individual services in a testbed aims to answer these questions:
  1. Does the service break/slow down when used with IPv4 on a dual-stack host with IPv6 enabled ?
  2. Will the service try using (connecting/binding to) an IPv6 address (AAAA record), when available from DNS ?
  3. Will the service prefer IPv6 addresses from DNS, when preferred at the host level ?
    Does this need to be configured ? How ?
  4. Can the service be persuaded to fall back on IPv4 if needed ?


Further steps: FTS (and SRM, and DPM)

FTS implies Oracle

Oracle/IPv6 rollout issues

(material in this slide kindly provided by Giacomo Tenaglia, CERN)

Then: will the traffic actually use IPv6?