Rubber stamp objections generally come when there are two competing
implementations of different standards that do roughly the same thing, or
when someone brings a standard to the IETF that has issues, but they're
hoping to get the IETF to publish it as an RFC without having change
control. Neither is a particularly sympathetic situation.
On Wed, Aug 3, 2016 at 2:55 PM, Viktor Dukhovni
<ietf-dane(_at_)dukhovni(_dot_)org>
wrote:
On Aug 3, 2016, at 4:15 AM, Randy Bush <randy(_at_)psg(_dot_)com> wrote:
if you write a draft and have running example code, you are accused to
be just coming to the ietf for a rubber stamp (cf. sidr).
The Postfix code for DANE in SMTP was developed in parallel with the early
drafts of RFC767[12]. I don't recall any "rubber stamp" objections.
Perhaps
that was an exception, but at least that objection is not universal.
Work on the Postfix code began in Mar/2013 and on the new drafts in
May/2013.
Stable code in Postfix 2.11 was released in Jan/2014, and the RFCs were
finally
published in Oct/2015.
--
Viktor.