Re: Proposed change to draft-ietf-nomcom-rfc2727bis-01.txt

[Brian E Carpenter <brian@hursley.ibm.com>]

Jim,

If it really does what you say, OK, but in that case the document is confusing.
At a minimum I would suggest adding a separate section that gives the
complete timeline in one place. At the moment one has to reconstruct the timeline
and as my comment shows, that isn't obvious.

Also,

> Also note that Section 3 Item 7 re-defines the advise-and-consent model
> to explicitly require the NOMCOM to interact with the confirming bodies
> during the confirmation process.

Yes, I was glad to see that. But I think it needs to be stated that this
process is allowed at least 4 weeks (as opposed to the 2 weeks it has typically
had in recent years).

   Brian

James M Galvin wrote:
> 
> On Tue, 9 Jul 2002, Brian E Carpenter wrote:
> 
>     Section 3 includes this:
> 
>     >    2.  The annual selection and confirmation process is expected to be
>     >        completed within 3 months.
> 
>     I propose that this should be changed to read
> 
>        2.  The annual selection and confirmation process is expected to be
>            completed within 5 months.
> 
> What the design team has proposed in this document, instead of extending
> the NOMCOM operational process, is to ensure the NOMCOM is fully
> operational prior to the Third IETF.  Previously, part of the NOMCOM
> time was often used to constitute or organize the NOMCOM itself.
> 
> Section 4 Item 1 requires the NOMCOM itself to be fully constituted and
> operational one month prior to the Third IETF.  Section 4 includes
> several changes to ensure this occurs.
> 
> What this does, effectively, is give approximately 2 months for the
> creation of the NOMCOM itself, approximately 3 months for the operation
> of the NOMCOM, and for the NOMCOM to be completed 1 month prior to the
> First IETF.  Everything is approximate because the precise scheduling of
> IETF meetings varies a bit from year to year.
> 
> Also note that Section 3 Item 7 re-defines the advise-and-consent model
> to explicitly require the NOMCOM to interact with the confirming bodies
> during the confirmation process.
> 
> Jim