Re: [Gendispatch] New Version Notification - draft-eggert-bcp45bis-05.txt

As the one who proposed moving to the normal appeals process, let me
support that proposal:

1. If one has a problem with what someone does, one should start
there.  In this case, ask the SAAs (politely and without assuming
they're being evil) to reconsider, and give reasons.

2. One should then move up the chain.  In this case, the next step is
to ask the one who appointed them -- the IETF Chair -- to review the
situation and weigh in.  Given that the IETF Chair appoints the SAAs
and then steps back and lets them do their jobs, it's reasonable that
the IETF Chair has not even been following the specific situation.
S/he should be given a chance to resolve it.

3. Continue moving up.  The next "up" is the IESG, and then the IAB
after that.  They're all available, and it makes sense to invoke them
in turn, just as for any other decision in the IETF.  This does not
allow the IESG to suppress anything, because an appeal can still
always go to the IAB.

4. The original plan, where the IAB is the only entity to appeal to,
gives no mechanism for reasonable review and resolution by the chair
or relevant ADs.  As I said at the time, a multi-level appeal process
is always better than having only one step available.

Keith, please tell us why you think the IETF Chair and the IESG should
not have a chance to review -- and perhaps support -- an appeal before
it goes to the IAB.  Given that it *can* still go to the IAB, how does
letting the IESG try to resolve it first allow them to suppress input
that it doesn't like?

Barry

On Fri, Oct 1, 2021 at 3:20 PM Keith Moore <moore@network-heretics.com> wrote:
>
> I definitely do not think that either the IETF Chair or the IESG should
> be in the appeals process for SAA actions.   This lets the IESG
> effectively suppress input that it does not like, for arbitrary reasons,
> and makes any notions of IETF Consensus extremely dubious.
>
> Please consider this objection added to my other several objections to
> this proposal.
>
> Keith
>
> On 10/1/21 2:39 AM, internet-drafts@ietf.org wrote:
> > A new version (-05) has been submitted for draft-eggert-bcp45bis:
> > https://www.ietf.org/archive/id/draft-eggert-bcp45bis-05.txt
> > https://www.ietf.org/archive/id/draft-eggert-bcp45bis-05.html
> >
> >
> > The IETF datatracker page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-eggert-bcp45bis/
> >
> > Diff from previous version:
> > https://www.ietf.org/rfcdiff?url2=draft-eggert-bcp45bis-05
> >
> > IETF Secretariat.
> >
> >
>
> --
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch