Handling of Internet-Drafts by IETF Working Groups
draft-crocker-id-adoption-09

Part 1 of my DISCUSS-DISCUSS will be solved by stressing in the document uses author and editor terms interchangeably (as agreed by Barry)
Part 2 of my DISCUSS-DISCUSS can be moved to a COMMENT. ,

      Authors/editors are
      solely chosen by the chairs -- although the views of the working
      group should be considered -- and are subject to replacement for a
      variety of reasons, as the chairs see fit.

As discussed during the telechat,

        The chair assigns who is editing the document for the WG.  
        The chair can moved from authors to contributors. 
        Do you disagree that could happened?
    Spencer: It has happened with BIS draft where the authors are no longer participating or dead. 
    Barry: It has happened in merged drafts, IPR issues, problematic authors, and the cases that Spencer indicated. 

That would be great those exceptional circumstances could be explained: merged drafts, IPR issues, authors no longer participating. And also that authors just don't disappear: they are moved to the contributors list.

When I read ...

      Authors/editors are solely chosen by the chairs

... it misses some nuance and newcomers might be mistaken.

"""
In formal terms, a working group raises and discusses each item of document content.  For difficult topics and/or difficult working group dynamics, this is the required mode.
"""
This requirement is both inappropriate for an informational document and false in practice.

The first sentence of the Introduction and the Security Considerations sentence are both awkward grammatically.

1) General: Is it also worth mentioning that upon adoption, the chair/author should send in a replaced by email so that folks can track the progression of the draft from individual -> wg -> RFC.  This is especially important if there's IPR on the individual draft.

2) s2.1: Step 1: I think that we need a bit more on this topic.  The times I've dealt with giving over change control it's been a bit more formal - authors submit an individual draft explicitly stating they're giving change control.  That draft gets published as informational and then the WG takes over.  My point is reminding the authors might not be enough.

3) s2.1: I think the first typical step you've missed is that it's not normally the chairs who just come up with the idea that a draft should be adopted - they get lobbied by authors to actually make that call.  There's usually two ways this can be done - privately through an email to the WG chairs or publicly by just blasting it off to the list.  I think a lot of folks don't know this and different WGs prefer one or other or don't care.  This seems like an important step to note in s2.1.

4) s2.2: Are the 1st two bullets kind of the same thing?

5) s2.2: I guess I don't understand this one:

   Does the document provide an acceptable platform for continued
   effort by the working group?

6) s3: Worth mentioning that if the individual draft's authors aren't selected it would be nice if they were at a minimum list in the acknowledgements section or in the contributors section?

7) s5.1: I assume the following is code for the individual draft can be WGLCed without being submitted as a WG draft:

  Such documents can be handled according to normal, internal working
   group process management.

If so I'd be better to make that clear.  If not, I think we need to make it clear that there's no requirement that when a WG adopt the draft that it MUST be resubmitted named as a WG draft.

general: The title is too broad, it only covers adoption, and
not e.g. WGLC. I'd say s/Handing/Handling Adoption/ in the
title would be better. (Apologies in advance that this
piles on from the secdir review;-) 

1.1 - "with advancement for publication as an RFC requiring
rough consensus in the working group" might confuse a new IETF
WG participant into thinking that IETF LC is not needed for
advancement as an RFC. Maybe add a bit about IETF LC?

1.1 - I wonder would "In contrast, individual submissions..."
be clearer in the 3rd para just to help the reader know we're
done describing things usually named draft-ietf-wgname?

1.2 - The WG having "final authority" again sounds like it
ignores IETF LC. I think you mean that the WG and not the
authors/editors have control but as written it could be read to
imply more, which seems a pity.

4 - "Absent charter restrictions, a working group is free to
create new documents." That seems a bit broad, would it be
better to say "that sensibly fit withing the overall scope of
the WG's charter" or some such?

4 - "well-deployed market" I think you mean that the technology
is well-deployed, but you don't need any commercial products to
exist really. I'd say rephrasing to not say "market" would be
easy and better.

5.2 - "released to them" is odd - do you need to say that?
Maybe better to just say that if a WG drop a draft then anyone
can pick it up as an individual submission, subject to the
boilerplate copyright stuff.

A few comments:

"Other than for selection of document authors/editors, as discussed in
Section 3, working group decision-making about document management is
subject to normal IETF process rules. "

Surely the selection of chairs is "subject to normal IETF process rules"?

I think you mean to distinguish between the decision making of the
WG vs the decision making of the chairs on a document, but both
are subject to IETF rules, including appeals.

===

"Is there a charter milestone that explicitly calls for such a  document?

"Is the topic of the I-D within scope for the working group?"

Isn't the former a subset of the latter?

===

Although the selection of authors/editors is the remit of the chairs
it might be worth noting that a wise chair will give regard to the 
consensus of the WG on their suitability for the task.