Kathleen,
On 9/12/2017 8:51 AM, Kathleen Moriarty wrote:
Having been through this process several times, a few as an
author/contributor, and one as an AD, it is very helpful to have the
guidelines that are in place already
Going back to my original posting:
What guidelines do you believe exist and where are they documented?
How is someone supposed to find those guidelines?
How does someone see the history of agreements that were formulated,
as further guidance about what the IETF arranges?
We've accepted documents that have and have
not transferred change control (as has been stated already) and being
able to work through the options has led to successful contributions.
Russ already named the PKCS documents. OVAL from DHS was another
somewhat recent one that transferred change control. This document
does need revision and has been picked up by the SACM working group.
It's been implemented by about 50 vendors, but at this phase it in't
lifecycle, it needs some fixing.
This is confusing, in several ways. First, historically the IETF always
insisted on taking change control before agreeing to work on/standardize
a specification. The only constraint on this, historically, was on the
original round of work, but with no constraints on later work. So this
sounds like an extremely basic policy got changed somewhere along the way.
It also suggests that the IETF has sometimes become a subcontractor for
some other group (that retains change control.)
Perhaps you are drawing a distinction between 'bug fixing' versus
'changing', but again, historically that has only been a constraint on
the first round of effort, not later IETF work on the specification.
Please clarify.
d/
Apparently
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net