Re: Enough is Enough.

Toerless Eckert <tte@cs.fau.de> Sat, 24 October 2020 19:04 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 1E8583A1030; Sat, 24 Oct 2020 12:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Je9S_pWt8TGh; Sat, 24 Oct 2020 12:04:42 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACD553A0B75; Sat, 24 Oct 2020 12:04:42 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 19A06548068; Sat, 24 Oct 2020 21:04:37 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0BCAE440059; Sat, 24 Oct 2020 21:04:37 +0200 (CEST)
Date: Sat, 24 Oct 2020 21:04:37 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Ofer Inbar <cos@aaaaa.org>
Cc: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, "legal@ietf.org" <legal@ietf.org>, Khaled Omar <eng.khaled.omar@outlook.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Enough is Enough.
Message-ID: <20201024190436.GC52044@faui48f.informatik.uni-erlangen.de>
References: <MN2PR11MB4366A0264CACD3D1B18E82E4B51F0@MN2PR11MB4366.namprd11.prod.outlook.com> <20201024153933.GB52044@faui48f.informatik.uni-erlangen.de> <20201024160758.GF2632@mip.aaaaa.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20201024160758.GF2632@mip.aaaaa.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OBszY-nvuGcz11Jw-sJyexppfuA>
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: Sat, 24 Oct 2020 19:04:45 -0000

On Sat, Oct 24, 2020 at 12:07:58PM -0400, Ofer Inbar wrote:
> On Sat, Oct 24, 2020 at 05:39:33PM +0200,
> Toerless Eckert <tte@cs.fau.de> wrote:
> > Technically, the key reason for not removing the drafts to me is that
> > only because Khaled was posting the drafts to the IETF did he get cycles from
> > the IETF community that was expressed through many public and (from what i
> > read) also private emails. And it could be seen as a disrespect to those
> > that did spend cycles on reading those drafts and providing feedback to
> > remove the drafts. Especially given how the public exchanges about the
> > draft are archived and those archives would not be comprehensible if the
> > references documents where removed.
> 
> You made it seem like a secondary point, but for me personally, the
> main reason not to remove drafts is to make it possible for people
> reading the list archives or looking into history later on, to see
> what was being discussed at the time and read it directly.

I am not a native english speaker. I did not intend to make it seem secondary.
I would be happy to receive language suggestion to avoid this misperception
for future reference.

To me there are no clearly prioritizeable choices here.

> For that reason, I would feel quite uncomfortable if I saw drafts
> being removed from the archives merely because the submitter wished to
> stop working with the IETF.

I am sure Khaled would argue that it is not "mereley because", but that
his desire to do so is based on the community behavior specific to his case.

> Having the drafts present does not
> prevent the submitter from ceasing to work with the IETF.  Knowing
> that that's all it takes to get a draft removed, would make me feel
> about any future draft "this might just disappear later", which
> changes the way people might relate to all future proposals.

The only rules we seem to have is "unusual circumstances". Hence i would
say you "slippery slope" argument invalidates itself: If incidents like
this would occur more frequently they would not be unusual anymore.

Still waiting of course for someone to explain better boundary definition
of "unusual circumstances".

Cheers
    Toerless

>   -- Cos

-- 
---
tte@cs.fau.de