New OpenDNSSEC doesn't want you to ... ride into the danger zone

A new version of OpenDNSSEC – an open-source implementation of DNSSEC – is hoping to plug a problem it is happy to have: increased use. Release candidate of version 1.4.9 was put out Monday for testing, with the key new feature being the ability to deal with a large number of zones – more than 50. "Too much concurrent zone …

[Ayemooth]

> however, the fact that there is still not a version 2.0 nearly seven years later shows that the software, and the protocol, are still not in wide usage

You mean like that other not-in-wide-usage protocol HTTP? (OK, HTTP isn't actually a protocol, but you get the idea)

[Jonathan Richards 1]

Say what?

> HTTP isn't actually a protocol

Good folk at the IETF don't agree with you.

[batfastad]

Why do you not classify Hyper Text Transfer Protocol as a protocol?

[Anonymous Coward]

... or having a version 2

[Anonymous Coward]

Say what?

"You mean like that other not-in-wide-usage protocol HTTP"

Good folk at ietf don't agree with you

https://tools.ietf.org/html/rfc7540

[AlanB]

Versioning

While HTTP/2 does exist, as others have already said, this is about version 2.0 of an _implementation_ of a protocol, not versions of the protocol itself.

OpenSSL hasn't had a 2.0 release (1.1.0 is in beta), but has had many releases over the last seven years, and is very widely used. Netscape Security Services is now at 3.21, but that doesn't mean it's three times as widely used as OpenSSL. Mostly this just shows that different open source projects use different release numbering schemes, and can't be directly compared.

(The same is true of protocol versioning. That SSL had versions 2.0 and 3.0 and TLS is working on 1.3, doesn't mean TLS isn't used as much as SSL was, it means that TLS designers had learnt from SSL mistakes, and haven't had to introduce a totally incompatible version.)