Dear Forum,
I'm unable to access certificate transparency logs at oak.ct.letsencrypt.org. Cause for this is that the aforementioned domain lacks a AAAA record. I hereby request that the domain be fixed and the record be added.
(Btw, please don't tell me to use IPv4. Tele Columbus turned it off for my connection yesterday. Unannounced of course.)
We will investigate adding IPv6 support to Oak.
While this was asking about Oak, I thought I'd mention our upcoming logs based on Sunlight already support IPv6. While it will take us some time to transition to those logs fully, we do plan to ensure IPv6 is fully supported there.
While I agree with the sentiment that everything on the internet should be accessible through IPv6, I don't think "misconfigured" is the correct term. As far as I can tell, there's no requirement for CT logs to be accessible on IPv6.
I believe it is time on the whole Internet for switching the phase of introducing IPv6 to the phase of eliminating the legacy protocol IPv4. I am dreaming about an RFC stating that every Internet facing service must have IPv6 as carrier protocol and IPv4 is optional only.
I agree, but a lot of ISPs are simply not implementing IPv6 and an RFC won't force them.
I hear ya, @bruncsak.
I'm dreaming of a world where everyone takes agency for their outcomes and responsibility for their actions.
I think I'll be waiting awhile (forever).
An RFC won't help here. What actually would help is Google making IPv6 a ranking factor. If that happened it would only take weeks for almost every server to be reachable via IPv6.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.