IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 24 May 2019 20:00 UTC

Return-Path: <brian.e.carpenter@gmail.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 01BBA1200F1 for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 13:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ud5wy1uXwDBd for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 13:00:28 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 97339120106 for <ietf@ietf.org>; Fri, 24 May 2019 13:00:19 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id y11so1065361pfm.13 for <ietf@ietf.org>; Fri, 24 May 2019 13:00:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Wn0grSbdDYzRgt5YtwJRksqY5Ocj0xAnJXeb4lb8P5w=; b=YDRqpw0fvpLkQ/qOTY2Ky4cKNtIYSa7noAgk5Trx7Qkdku8Tec9x2E3iZYTFLZX8fl /+PfCvnyD8cIwIbNUPhKN2i/DHoEBzcBDZ2tzMDvBuKjfCSxzihKXzjaiEzdCWFp/b4N FwCbi9KpMDSr16b5aD/4vlvRacj8huB+gSh6jVIKfJzstTR8dWt9tSomy+VPvzfVm5mf VFAdzvZ8sY5bPiMVxmjEVVKfmO3uWFaER6vYC8l3DLUms5zTYAV0GvoFMonuHP9AJJik C+IsxkKrgFU9dui8slLuBcVb7UXadI4MoxKzEyMzItfINooaRCuaX0aP42rjnnE/P0+0 iFCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Wn0grSbdDYzRgt5YtwJRksqY5Ocj0xAnJXeb4lb8P5w=; b=icHqszLKo4qvbWdGPPRMrQZWnDLRZwOA1uY0kdkm5wWbAJDROo6EGuQ9hNe5zGG0me bIMbpuS4cqJvzZysIu8KS3VCYPYYw+KPNKGJumzObFmk3jwpqr277cXPG8Btsajdvk62 mDJIaLDWtpmvY8LCTyLC68EIPc6jAynFYVHRlTQo6MNHmsFtpnZpINltFZO0s7u7kFbx z9TSoLCf1NTwmX+u1dzaiNIikenEUL1N792u8C6PsVJffRvmm9Sxb94iZ6+nsyEOscEf XgjIYhztrCsGDfWWbT7kiP5hZQl/47NIqk9xFUI3ONROF9hb4P4cmrj/Q567AtoHE+UM d/uQ==
X-Gm-Message-State: APjAAAUnhpZsfA9fhDQSCZs45y55zQnVnclry1bLX4QjW93EnxBHQ85N aEKFalX+jXd6gvZ3KvY4bmffAY8d
X-Google-Smtp-Source: APXvYqyVOoCS+QP/ztvElIJLv7dH0E1cjdLkyax/E7fTZE8NiIk32sKTpujrOEZysiVxFCJ0/d/vsA==
X-Received: by 2002:a62:36c1:: with SMTP id d184mr94938488pfa.49.1558728018793; Fri, 24 May 2019 13:00:18 -0700 (PDT)
Received: from [192.168.178.30] (229.129.69.111.dynamic.snap.net.nz. [111.69.129.229]) by smtp.gmail.com with ESMTPSA id e10sm6109713pfm.137.2019.05.24.13.00.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 May 2019 13:00:17 -0700 (PDT)
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: Eric Rescorla <ekr@rtfm.com>, S Moonesamy <sm+ietf@elandsys.com>
Cc: John C Klensin <john-ietf@jck.com>, IETF discussion list <ietf@ietf.org>
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> <CABcZeBOZbiN=1tOzzSzGy3UC02_f0c9jBC-Jwj3urO0WsRDxJw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1ebe1d16-a79b-aa41-9df1-5c2f5b158d34@gmail.com>
Date: Sat, 25 May 2019 08:00:13 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBOZbiN=1tOzzSzGy3UC02_f0c9jBC-Jwj3urO0WsRDxJw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xHINStPjhv1e3r0xAuqN7ATI_5A>
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 20:00:30 -0000

On 24-May-19 21:50, Eric Rescorla wrote:
> 
> 
> On Fri, May 24, 2019 at 2:15 AM S Moonesamy <sm+ietf@elandsys.com <mailto:sm%2Bietf@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.

There's certainly no rule, but there have been many cases where an
AD has raised the issue of potential conflict of interest - if a WG Chair
is a lead author for an important WG draft, that person can certainly
not make the consensus judgement. And I know that some ADs have been more
insistent on this point than others, especially if both co-chairs are also
protagonists of the draft.

    Brian

v2.23.0 | Report a Bug | By Email