Re: [Ietf-and-github] Closing issues

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 02 November 2019 19:28 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A66E1200C4 for <ietf-and-github@ietfa.amsl.com>; Sat, 2 Nov 2019 12:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 k5gK74YChgYT for <ietf-and-github@ietfa.amsl.com>; Sat, 2 Nov 2019 12:28:15 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 9192612022D for <ietf-and-github@ietf.org>; Sat, 2 Nov 2019 12:28:11 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id e4so8587797pgs.1 for <ietf-and-github@ietf.org>; Sat, 02 Nov 2019 12:28:11 -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=UDbNWoyM37YM61uY/aR6/eQRVrenk9blcK5qgZhn6IQ=; b=BKdLVonUYmOJpK1mRaaRHDl70GXvHrmq/dkJCIWJnGSnt2SLEGTUr2UqkCPcMP7V8f QXaAN3o6mSqa2Cm+LCAgvNmdD3yCT/UVrx2I0XjEnNLYrmuanMQAlaWbZ2VeI8jwlNs6 GHfnpy+MBGmCWuyXy/R/yEbfjjvmvKzSvw2G2c5ahAemlRd/kieL8Rew44iYqGtMJNTi JNc1koEImW+kfushLrj+mMb3emvbvauxG0fWnskBo91suVgtP1oV5LFHffeA0QJvzFnu weCl4SsYAezqEbpzD4MjcI17liKISM8B39BMy8OX3AHGQWeaIdv6au1j45/QKVzukeqV fgcQ==
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=UDbNWoyM37YM61uY/aR6/eQRVrenk9blcK5qgZhn6IQ=; b=FxgAMXzmeJO0z268k/0zzW7JVYJ6dE/3WOZG0rHGb2HXvSWt8s8UVxxEejbHErkRGX 3/bU0Fm3SnnFh/nWAyh5SmuyOgDK9iMWfmUm4hIO+ckJ0/cKeoPkyxyvYKuK7HJPGR4U DLBX1/QXFwA+XG7b15jLfYfoY/5SbRWgFji4CdCfk/A99rRfAat5QJVDbw6fWiamifcy Qmv4F+VhIkPHhGKjcMKIX3W6a+NsMRjSs/lb1kIN4TJ1C0kNmY0HyoNEyxSjj9MeznFu q0m3mvjrYkA298ne1DXR2E9sZId+a8ykQq3n0+5/WV3HzI5nyBylfZnqvAGM+WYSCcmF WTXw==
X-Gm-Message-State: APjAAAW7+rgOaTVslc9S3gxlrU9YIlzA4cH+oj8C6FaYD23kZSj8tQVr dEjsfu/ucKe1Bt2TbtBz3p74O6+X
X-Google-Smtp-Source: APXvYqxxhoNMjtXHBDl4b6u6Wh/ndaBSubvIE9qdM09fUsVt4NXy8+XJ2xCuCZqA6hWCSoKabuRmig==
X-Received: by 2002:a17:90a:ba89:: with SMTP id t9mr15215878pjr.29.1572722890664; Sat, 02 Nov 2019 12:28:10 -0700 (PDT)
Received: from [192.168.178.30] (46.137.69.111.dynamic.snap.net.nz. [111.69.137.46]) by smtp.gmail.com with ESMTPSA id w2sm10621901pgr.78.2019.11.02.12.28.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Nov 2019 12:28:09 -0700 (PDT)
To: Rob Sayre <sayrer@gmail.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
References: <CAChr6SyD=SE=z=Rvsp11orymu1=DMfvYe3X-xmwdCV8_3ygdJA@mail.gmail.com> <a1be63d2-67c7-4efe-a0b6-5e18531c0cce@www.fastmail.com> <CAChr6SyZoasUYt0BUryppAwHz7JS0ncSGZP-iY-zQTGQAZLLzw@mail.gmail.com> <CAChr6Sw+SDCUd_FDPG-z-Lg=T3ZH3YgjBjMzB8A1W3mJsSk2zg@mail.gmail.com> <9E634E81-48C5-4EDA-B98E-972A7CACF641@akamai.com> <CAChr6Sz1pz2JpamQupBDsdTb4ArNJOfVAtZs9BypCnWbaSYEPg@mail.gmail.com> <200DEDAC-A18D-45B4-BC0F-69D8970CED47@akamai.com> <CAChr6Sx7k_WGvkWG-mk-kfV1hwYjUUKb6Rf3sCfihRtD5MO4QA@mail.gmail.com> <1c10b7bd-8580-0ff6-8e3e-0c4e2c48518e@joelhalpern.com> <3dbbafe7-43b9-191e-4cc8-ce192c016627@gmail.com> <CAChr6SzrRfLwia6cYix_8ub5H152gorXP-6ivguyT8d99_pZ-g@mail.gmail.com> <ef7afa06-ebe1-87ca-8cf8-014071ef0ff8@gmail.com> <CAChr6Szk8itcq3Ysd5VFYiNX4TaMSWhyiVZzCPEw6vmv+ig8Aw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <843f0e20-cfd7-7c98-5709-e5d7b206f23c@gmail.com>
Date: Sun, 03 Nov 2019 08:28:06 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAChr6Szk8itcq3Ysd5VFYiNX4TaMSWhyiVZzCPEw6vmv+ig8Aw@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-and-github/O5iOGkPjwY7hOOjdPi8pBjqN3Ws>
Subject: Re: [Ietf-and-github] Closing issues
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Nov 2019 19:28:17 -0000

On 02-Nov-19 18:07, Rob Sayre wrote:
> 
> 
> On Fri, Nov 1, 2019 at 9:51 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     > That is interesting. Has anything ever been overturned on appeal?
> 
>     For GitHub usage, I have no idea. In general:
>     https://tools.ietf.org/html/rfc2026#section-6.5
>     https://www.ietf.org/standards/process/appeals/
>     Appeals can be dealt with between the appellant, the WG Chairs, and the AD,
>     without invoking the formal process, and those go uncounted.
> 
> 
> Right,
> 
> I was wondering if anything had ever been overturned on appeal using this process.

Well, I've never done an analysis, but I'd say most of the formal appeals ended up with a compromise decision rather than a complete overturn, even for the ones that were further appealed to the IAB. But for appeals settled at the AD level, we have no idea because there's nowhere that they are logged.

That doesn't mean the appeal mechanism is an empty threat, though. I think it keeps everybody on their toes. Because of cases like the one you brought up, it needs to be 100% clear that decisions taken via GitHub are appealable, IMHO.

Regards
    Brian

> 
> thanks,
> Rob
> 
> 
> 
> 
> 
> 
>     Regards
>        Brian
> 
>     On 02-Nov-19 15:42, Rob Sayre wrote:
>     > On Fri, Nov 1, 2019 at 7:22 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com> <mailto:brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>> wrote:
>     >
>     >     On 02-Nov-19 14:41, Joel M. Halpern wrote:
>     >     > Looking at the draft, I think something that would address the issue Rob
>     >     > is raising is that the first paragraph of 4.1.2 (about closing issues)
>     >     > get an extra sentence.  Along the lines of:
>     >     >      As noted in section 2.2, this guidance MUST be communicated to and
>     >     > agreed by the working groups.
>     >
>     >     Agreed.
>     >
>     >     > One can argue that this is implicit in the document.  It seems like it
>     >     > could help clarity and can't hurt.
>     >
>     >     It's already clear in the document that normal IETF process rules
>     >     apply, i.e. RFC2418 etc. That certainly implies quite a lot, including
>     >     of course that contested decisions are appealable.
>     >
>     >
>     > That is interesting. Has anything ever been overturned on appeal?
>     >
>     > It would be good to record such an occurrence in future documents.
>     >
>     > thanks,
>     > Rob
>     >   
>