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

S Moonesamy <sm+ietf@elandsys.com> Fri, 24 May 2019 15:35 UTC

Return-Path: <sm@elandsys.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 202971202F5 for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 08:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=42Me24o6; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=gkjVDlpW
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 WUpShLSPTgjm for <ietf@ietfa.amsl.com>; Fri, 24 May 2019 08:35:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 879C21201ED for <ietf@ietf.org>; Fri, 24 May 2019 08:35:30 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.49.188]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x4OFZCsu012590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2019 08:35:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1558712126; x=1558798526; bh=shMFY418TYj39W0FuEljwb1d01vkpr6R31EaTI23DaE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=42Me24o6Ut+LN8/ic4TDezRysafKsWzBcgBvUw/Nbd44t8iiWa/C816cMMpgyKZPL zIyUBeiNNdRXJiujtflFgTghvq4ML5wjpX1o6kO+wI47T5sOwR0G83oEJ7PN0bK6aB YaMpNuCSJa1eBvYsRkA/RMqu8/BPW3oxszstwOQ4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1558712126; x=1558798526; i=@elandsys.com; bh=shMFY418TYj39W0FuEljwb1d01vkpr6R31EaTI23DaE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gkjVDlpWso0uzE/Uo7a5W2sGl52/1g/5gP+iutzZ56KW9Ffs+YuBITJJIk4Dl3V8A J2bs2ZtpI6IFGcVL83KRrcKC7tNgEE6r6SNeq3DLdeANyNy21AtVjpC43gDtIFNX4q 7Adhtv4yOp2/8yW4Qfm+Gy8C8oiVJb7PULJ1LvL4=
Message-Id: <6.2.5.6.2.20190524035947.0c7bf400@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 May 2019 08:32:55 -0700
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Cc: Eric Rescorla <ekr@rtfm.com>, John C Klensin <john-ietf@jck.com>
In-Reply-To: <CAKKJt-fxYm5+YuCOF8skD8ej0vZnGTT9_7JzdSgpnyYnp2232g@mail.g mail.com>
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> <CAKKJt-fxYm5+YuCOF8skD8ej0vZnGTT9_7JzdSgpnyYnp2232g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q0zflZ1awPH_tumbKeUiDS_Zqcg>
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 15:35:32 -0000

Hi Spencer,
At 02:49 AM 24-05-2019, Spencer Dawkins at IETF wrote:
>This is actually written down in more detail in 
>https://www.iab.org/documents/correspondence-reports-documents/2012-2/iab-member-roles-in-evaluating-new-work-proposals/, 
>which seems to be one of the more obscure practices at IETF, since 
>when I was on IESG and referred to it in discussions with IESG and 
>IAB members, people often told me they hadn't seen it.

I sent an email to the IAB on 20 May to seek clarification.  There 
hasn't been any reply up to now.

>I was only on the IESG for six years, but AFAIK, this isn't quite right.

I would like to thank Mr Rescorla and you for providing feedback on the above.

>Working group chairs, and ADs, have a lot of flexibility because we 
>rely on them to Do The Right Thing, If that flexibility is misused, 
>that's a problem. Please speak up if this looks like a problem to 
>you - there is an appeals chain, and it starts with the person who 
>takes a problematic action.

I am not sure whether you are aware of what happens (it may be 
different nowadays) when a persons speaks up on this mailing list.

The appeal records are inaccessible:

   > GET /iesg/appeal/response-to-klensin-2017-11-29.html HTTP/1.1
   > Host: www.ietf.org
   > User-Agent: [removed]
   > Accept: */*
   >
   * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
   < HTTP/2 404
   < date: Fri, 24 May 2019 14:04:25 GMT

   > GET /iesg/appeal/response-to-masotta-2013-11-14.html HTTP/1.1
   > Host: www.ietf.org
   > User-Agent: [removed]
   > Accept: */*
   >
   * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
   < HTTP/2 404
   < date: Fri, 24 May 2019 14:07:35 GMT

There were eight people who filed appeals over the last 10 
years.  There is only one of them who regularly participates in IETF 
discussions.  Does that mean that none of the other regular IETF 
participants took action when they saw a person taking a problematic 
action?  Or is it because none of the Area Directors have ever taken 
a problematic action?

Would the short draft be "AD sponsored" if the it was authored by an 
Area Director?  I suggest looking at the previous cases, e.g. RFC 7475.

Regards,
S. Moonesamy