[saag] Re: New Version Notification for draft-rsalz-crypto-registries-00.txt

[Randy Bush <[e-mail]>]

< rant >

>> A draft may be stable.  The spec in the draft is not.  Authors
>> may choose to update that spec at any time.  Therefore, if
>> implementers are looking for spec stability, drafts are the wrong
> 
> As long as the code points are references by versioned drafts,
> this is not an issue. We are looking at the few cases where this
> was done using an unversioned draft and working with IANA to
> resolve those.

it is not about control, our delicate egos, blah blah blah

standards are for the *users* so that we have vendor/implementation
choice.  the screw from vendor A must fit the nut from vendor B.
this would seem to require long lived immutable documents.  to
create them is why we go through the review process from hell.  as
eliot points out, internet-drafts do not make that bar, period.
neither does github.

the ietf's politically dominated and vendor driven process seems to
have become so farblunget that doing work 'outside' (aka in the real
world) becomes more and more attractive.  and this 'discussion' sure
makes that tension clear.

doing work inside the ietf should be attractive and productive, not
like pushing a rock uphill while being second guessed.

randy, hearing the ghosts of jon, bob braden, joyce, ...