[ipv6-wg] "IPv6 Ripeness" measurements on RIPE Labs

* Gert Doering wrote:
>> http://labs.ripe.net/content/ipv6-ripeness
>
> You're asking for ideas for the "5th star".  Some random thoughts...
>
>  - have IPv6 transport (with addresses from their own prefix) to all/some of 
>    the DNS servers that the IPv6 reverse zone is delegated to
>
>  - have www.<theirdomain> with working IPv6 connectivity (now, 
>    <theirdomain> might not be that easy to determine for some of the
>    LIRs out there)
>
>  - have IPv6 capable MXes for some/all of the listed contact e-mail
>    addresses for the inet6num and/or the organization object

I second that.

The draft-haberman-rpsl-reachable-test proposal is unusable:

  Update FAILED: [route6] 2001:4bd8::/32AS15725
  ***Error: Syntax error in object

  route6:       2001:4bd8::/32
  descr:        DE-IKS-JENA
  origin:       AS15725
  mnt-by:       IKS-MNT
  pingable:     2001:4bd8::4000:0:0:196
  ***Error: "pingable" is not a known RPSL attribute
  ping-hdl:     IKS-RIPE
  ***Error: "ping-hdl" is not a known RPSL attribute
  ...

  Update FAILED: [route] 217.17.192.0/20AS15725
  ***Error: Syntax error in object

  route:        217.17.192.0/20
  descr:        DE-IKS-JENA
  origin:       AS15725
  mnt-by:       IKS-MNT
  pingable:     217.17.192.196
  ***Error: "pingable" is not a known RPSL attribute
  ping-hdl:     IKS-RIPE
  ***Error: "ping-hdl" is not a known RPSL attribute
  ...

Gert's tests are much more easy to fulfill:

You might monitor (reverse) DNS queries on your system (to see who is
resolving via IPv6 and who is queried for rDNSv6) 
  ;; AUTHORITY SECTION:
  8.d.b.4.1.0.0.2.ip6.arpa. NS	avalon.iks-jena.de.
  8.d.b.4.1.0.0.2.ip6.arpa. NS	jengate.thur.de.
  ;; Query time: 114 msec
  ;; SERVER: 2001:610:240:0:53::3#53(2001:610:240:0:53::3)

You might monitor your mailserver log to see which systems does send or
receive emails via IPv6:
  May  3 15:51:03 annwfn sm-mta[17288]: o43DoqKp017288:
  to=<auto-dbm at ripe.net>, delay=00:00:09, xdelay=00:00:09, mailer=esmtp,
  pri=31240, relay=postgirl.ripe.net. [IPv6:2001:610:240:11::c100:1342],
  dsn=2.0.0, stat=Sent (OK id=1O8w30-0008Kf-CC)

  May  3 15:51:08 excalibur sm-mta[6518]: o43Dp6js006518:
  from=<unread at ripe.net>, size=2642, class=0, nrcpts=6,
  msgid=<20100503135105.6EBD89B1AC at cello.ripe.net>, proto=ESMTP, daemon=MTA,
  relay=beaver.ipv6.ripe.net [IPv6:2001:610:240:11::c100:131d]
  
But your own mailinglist server should be upgraded first:
  May  3 15:07:11 excalibur sm-mta[19888]: o43D79XZ019888:
  from=<ipv6-wg-admin at ripe.net>, size=3142, class=0, nrcpts=1,
  msgid=<20100503130627.GB60850 at Space.Net>, proto=ESMTP, daemon=MTA,
  relay=postboy.ripe.net [193.0.19.3]

LIR's website is difficult to determine. You might add a field on the LIR
portal at https://lirportal.ripe.net/lirportal/liruser/general.html OTOH
what is IPv6 delivery of website? How many parts come via IPv6 how many via
IPv4? Take our website www.iks-jena.de as an example. It delivers - dual
stacked - all content via IPv6, but if IPv6 is enabled, the show remote
client address is displayed as IPv6 AND IPv4 at the same time. Is this IPv6
enabled?