On 24 Apr 2018, at 15:02, Ondřej Surý wrote:
And the MR was peer-review and merged into BIND master branch with
intent to backport the feature into older release branches.
I don’t think it’s a useful or helpful to change the rules for
existing adopted work.
Nobody is changing the rules (yet - but we can dream!); some people are
just being more vocal about the real need for implementation experience.
We need to have a discussion on the mechanisms that would allow
implementors to know when to start the implementation of existing
draft.
I don’t think what we need here is more ‘procedure’. Either a
draft manages to get (at least one) implementer involved early - or the
draft is most likely not worth pursuing.
From implementors point, it makes little sense to start implementing
before the protocol change is almost fully baked (aka WGLC and
further), because until then the protocol might change considerably.
It makes little sense to call a protocol change ‘fully baked’ if
nobody has checked that implementation is even possible.
So, if we require implementation report further down the road, it
needs to be more clearly defined than people suddenly shouting “this
is not ready” when WGLC starts. And while the attempt to implement
something is certainly useful to get valuable feedback, it also
imposes some costs (with undefined limit) on implementors (especially
the open source implementors) and it sort of discards the whole
“Proposed Standard” -> “Internet Standard” classification at
global IETF level.
The costs are the very best reason to demand implementation experience
before calling something ‘fully baked’. If a draft has real merit,
somebody will invest time/money. If it does not have merit, nobody will
implement, and the draft will die the death it deserves. In other words,
a draft needs to put its money where its mouth is. This way, drafts that
actually help operations (this is dnsOP, after all) will get the
attention they need, while other drafts may wither away - and that’s a
good thing.
Kind regards,
--
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
