Re: Issue: Transition rules?

[Michael StJohns <mstjohns@mindspring.com>]

At 12:07 10/14/2003, James M Galvin wrote:
> In general, all approved documents take effect immediately.  I don't
> believe this document should be any different and I don't believe we
> need to state that explicitly.
>
> However, I presume you are suggesting we document the "edge case" of
> whether or not an operational NOMCOM is required to employ a revised
> document if one is published during its tenure?  (It's probably worth
> noting for completeness there is always an operational NOMCOM, and in
> the current draft revision there is a short period of time when two may
> be operating concurrently.)


No.  The problem is that there are possible edge conditions between the two 
documents (2727 vs 2727bis).  One example right off the top:  2727bis 
allows a challenge to the selection process for the Nomcom and sets a 1 
week period after the selection has been made for that challenge, 2727 
doesn't have such a concept.  Say 2727bis is approved during the one week 
period (which it won't be) - which rule applies?  Say its approved one 
month later - an argument could be made that challenges could occur from 
the approval date for the one week.  An edge case that has no prima facia 
resolution.  (Note - one such challenge would be that the Nomcom chair 
excluded from the volunteer pool people who were qualified under 2727bis 
rules of 3 of 5).

There may be others where process under 2727 conflicts with, impedes or 
differs from 2727bis.

Regardless, this nomcom should follow 2727 and assuming 2727bis gets 
approved, the next nomcom can follow 2727bis.

Note that none of the above prohibits the sitting nomcom from adopting 
procedure rules from 2727bis that don't conflict with 2727, but that's 
their choice, not ours.

Later, Mike



> With protocols I believe we all expect that when a revision is published
> it will be adopted immediately and implementations will transition as
> soon as possible.  It's not a perfect expectation but it mostly works.
> We should have the same situation with this document.
>
> Do we need to document that?
>
> I would not do it in this document.  If we believe that IETF procedures
> in general should be adopted when approved then let's make that the
> policy for all procedures.  I do not believe this document should be
> special with respect to this issue.
>
> I think we should have just such a policy.
>
> Jim
>
>
>
>
> On Mon, 13 Oct 2003, Harald Tveit Alvestrand wrote:
>
>     Date: Mon, 13 Oct 2003 10:09:56 +0200
>     From: Harald Tveit Alvestrand <harald@alvestrand.no>
>     To: ietf-nomcom@lists.elistx.com
>     Subject: Issue: Transition rules?
>
>     because of the timing stuff, this has gone from a non-issue to perhaps an
>     issue......
>
>     the current nomcom doc says nothing about when it takes effect, or what
>     that effect is on a currently seated nomcom.
>
>     I think one sensible procedure would be that it takes effect the 
> moment the
>     ISOC Board accepts a motion to observe that this is current IETF 
> procedure
>     (or some other convoluted wording), and that a sitting nomcom switch to
>     using the rules as far as possible, but does not change decisions 
> taken in
>     the past (for instance, the change in selection rules would not force a
>     current nomcom member to resign, but the sitting nomcom would be expected
>     to use the new rules when communicating with the confirming bodies).
>
>     1) Does that make sense?
>     2) Should the document say so?
>
>     Of course, an alternate is that the rules take effect when the IESG has
>     approved the document. Thoughts?
>
>                      Harald
>
>
>
>     ----------------------------------------------------------------
>     To subscribe or unsubscribe from this elist use the subscription
>     manager: <http://lists.elistx.com/subscribe>
>
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.elistx.com/subscribe>