Re: [Ietf-and-github] Closing issues

Rob Sayre <sayrer@gmail.com> Sat, 02 November 2019 05:08 UTC

Return-Path: <sayrer@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 A498A120111 for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 22:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 oRlMY4cKH5I5 for <ietf-and-github@ietfa.amsl.com>; Fri, 1 Nov 2019 22:08:06 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 84FC2120105 for <ietf-and-github@ietf.org>; Fri, 1 Nov 2019 22:08:06 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id s17so13033732iol.12 for <ietf-and-github@ietf.org>; Fri, 01 Nov 2019 22:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yqn0iifETLrdBGoORr3SopR+gGvOa/OmFSRlU2IRgjs=; b=pfem7bHwRL0jdqrwanV4K13s7IwtbcCFtrlg+UlsG/skagh3UTBq+IHT85KV6QRUbl nmj+VcaIlTrKZZKHMVmqEvjQ9oYPN1WGGmR5Dbd5yYM2LW7NPzQM6khQ91PmINLJc8Nv Bxq6Xn2hus2Sc6yiMgTs3NKmAHRuqRP3ecA16kfxnE8S/zu8mZEA4R3ChgHi5ZWjWvb4 a9J/m8wIzsnUahI+au6plHPSehS4n4pkWKvYxqDHwfBbrcQgL7VxXs4ExWzKIqtyIYJs 0n8sWEF5KLTu1b+YoTA6K5qByeoGHL/kAcYPuFFiVzwvUbrMjvXZz2RPjC4Ga+pTlsGE urlA==
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=yqn0iifETLrdBGoORr3SopR+gGvOa/OmFSRlU2IRgjs=; b=lcLbyfEnxxPviLuOeAJ2cVdYYkYxS2HOJOsYz8OKDjkWblgPo+A7Hh4cZ7Va0c+Ona 5Wl2grkPFB0JlkIevxQgMHyZVDksSUMfdXurV8t/in1db0CE4Q7qWlowC+MPcbMm+1sm XyuRoHPreD5SAmci6+GSukH2S8ORKZ+F79TcNV8N9vL3rfDmD6rvS3oDkVfJHGKmmYAv qXvKcMgngB9VXJZiLGw1dFM7nwnBh0+vjYr/8pR3AQ+vLVihincZ3vSsN7FsIw4PD8vd Fx3fm/nhP8lSreEQtp1vsMQX28l4YURExvdiBRYI8QIq01eoMVgGIe9zFeADl3EKEOze j9Rg==
X-Gm-Message-State: APjAAAWeCsam8rB4zd8CFwa3aLlTmqi0kGEb1O6PyW6sGCc473dU7OsB yKsjAxtAx0IcL9CwEre3p7gwYhXvlNaowZanc2g=
X-Google-Smtp-Source: APXvYqxHvWTk3LPfEvBSwXHEwW0+5k/Ul6dY1+2EoOthFabcIhV4hiOEI8AuMznIAVcnoYyn0DZ3cjIIZOlzHbeFrT0=
X-Received: by 2002:a6b:f408:: with SMTP id i8mr14126676iog.73.1572671285579; Fri, 01 Nov 2019 22:08:05 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <ef7afa06-ebe1-87ca-8cf8-014071ef0ff8@gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 01 Nov 2019 22:07:54 -0700
Message-ID: <CAChr6Szk8itcq3Ysd5VFYiNX4TaMSWhyiVZzCPEw6vmv+ig8Aw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005355b3059656119f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/nBjno31DoZGe8WGXNoYczrbbTrc>
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 05:08:08 -0000

On Fri, Nov 1, 2019 at 9:51 PM Brian E Carpenter <
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.

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>> 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
> >
>
>