Re: AD Sponsorship of draft-moonesamy-recall-rev

Eric Rescorla <ekr@rtfm.com> Fri, 24 May 2019 09:51 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F69012009E for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 02:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlwdEDr3gVl3 for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 02:51:24 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FF3612009C for <ietf@ietf.org>; Fri, 24 May 2019 02:51:24 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id n22so6636631lfe.12 for <ietf@ietf.org>; Fri, 24 May 2019 02:51:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r7x3ekMDuLfwsq87Te0VDKpbWr2rR+6/GtlYP9FZEcw=; b=B4nXRrniTGHfYiAcrdGLXPgWcSuy7nxN7FzjtCObS67ucikyOx8H6v0LK/foPyqhIJ 73uPYYP4sY/FfFriqDGjq5MyzPMsHFeDONZ52cjpss62aByYe36Xf1YCkhkhImxMUT1p dzkgbiPRpY6wHBh7aPdXmg+EB5nmpKgMG+vAsnzGwvNlZsmss9D/eBh0c5hvLPiB9kNT 1bzlJfw11gOzVe6BeLC6Vv9a1PnWUKkZG8pnC2zBJZ2eHOgJtatbBMyR0YaO7zEv/r/Q 5MbdE2FrAi7NYR1eVIWBFcVhKl+QBxbaSlcgDcYt6h9Jju6kjETPajrUGhEiToYCvFuO /gfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r7x3ekMDuLfwsq87Te0VDKpbWr2rR+6/GtlYP9FZEcw=; b=QlpFxVBPkoTfKwDIK5fkfUBPSM7V4q8zT5uj5eB84EGYmkvdZLozWGYm1EcBVAC0/U VIHN/pYgvgJYbo63F66V91yEZU48rYCEMNN8a7/vAUlYxFXHxRZq/22bmWWcZuuGdyoC v8NegbytqfN9BhSBQYHVBCZ9G71fO4EssnTPLn+DGMrJ6+0cunUgV3FGtnVOWstht2md wNowpRDwgZg8L7wzWS8fr4fhMm2DoPsZTsPdBB16R9UmG6PiIdVnnrL2ZLgKfYRBEBmM 60WgP6ycdJ/U53Ei1icIoy/WjEjHV3IEL/sytPbHR+6VncBzlelITjsF+rpTklx4phBn qBBw==
X-Gm-Message-State: APjAAAWCMDSj64kPTdna8FVQJ9qu8Cjhr2xRETXoSKckut9Qew5qSWLJ JebY7DvcHyzOeWuNHYNNG2M3aC1pMYlM4CXS5knl1G9P
X-Google-Smtp-Source: APXvYqz3TEWRMN3tml9oAtDGUmK5SGpyFOUXUyYpNQy165oxPj/D8E3xlhTpSF/brz7sgOX+pY6rvTNB3vg91yDs7gI=
X-Received: by 2002:ac2:4c38:: with SMTP id u24mr33437352lfq.168.1558691482522; Fri, 24 May 2019 02:51:22 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB> <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com> <E85C84CF-DB0B-410E-A0B2-A7C7E705E469@kaloom.com> <6.2.5.6.2.20190518141450.1163e590@elandnews.com> <75FF5D48-C416-4198-BC44-1B25524BF0E2@cooperw.in> <6.2.5.6.2.20190520025912.0ce8f378@elandnews.com> <CABcZeBNV0VxRrW0-Z4hY4zh_Ok3cRM8FJGyogYogP6R6X8K12Q@mail.gmail.com> <6.2.5.6.2.20190524004523.0ccaf558@elandnews.com>
In-Reply-To: <6.2.5.6.2.20190524004523.0ccaf558@elandnews.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 24 May 2019 02:50:46 -0700
Message-ID: <CABcZeBOZbiN=1tOzzSzGy3UC02_f0c9jBC-Jwj3urO0WsRDxJw@mail.gmail.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF discussion list <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary="000000000000216d5c05899f242b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rMxVNg3Ig18BegkGOWQMYQlcbvY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2019 09:51:26 -0000

On Fri, May 24, 2019 at 2:15 AM S Moonesamy <sm+ietf@elandsys.com> wrote:

> As a comment about IETF process, it was pointed out to me that a
> Working Group Chair cannot author drafts within his/her working
> group. That does not seem to be a problem for other Working Group
> Chairs; some of them have been authored drafts in their working
> groups.  That can create a perception that the rule, if there is one,
> is applied in different ways to different people.


It's not quite clear what the gravamen of your complaint is here. To the
best of my knowledge, no such rule exists. Obviously, you might have
been misinformed, but I'm not sure what you're hoping for as a result.



  I am okay if the
> IAB wishes to provide guidance on a problem statement about that as
> part of the revision to IETF eligibility procedures.
>

I don't understand what you are asking for, here. As I said, to the best
of my knowledge no such rule exists, so it's not clear what IAB would
do here.


> I read draft-rescorla-istar-recall-00.  One of the conclusions from
> it is that the recall system is so unwieldy that it is undeployable
> even in the most egregious cases.  I could not figure out the
> rationale for having an accountability mechanism which, by design, is
> not intended to work.
>

This misunderstands the document, which doesn't say that the recall system
was not intended to work, but merely that it does not in fact work. One need
not look far in the IETF to find other processes and technologies which
were expected to work but do not.

-Ekr


> There is the following sentence at the end of Section 3 of the draft:
> "The Chair of the IETF may not be removed by expulsion".  That is an
> interesting proposal.
>
> Regards,
> S. Moonesamy
>
>