Re: [legal] Enough is Enough.

"Scott O. Bradner" <sob@sobco.com> Tue, 20 October 2020 23:14 UTC

Return-Path: <sob@sobco.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 0DC2A3A08FF; Tue, 20 Oct 2020 16:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 uFIS5I4R08QX; Tue, 20 Oct 2020 16:14:41 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 04BE23A0906; Tue, 20 Oct 2020 16:14:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id A3F5744A4346; Tue, 20 Oct 2020 19:14:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5snpdy8BNWXT; Tue, 20 Oct 2020 19:14:25 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id B4CC544A4320; Tue, 20 Oct 2020 19:14:23 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: [legal] Enough is Enough.
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <VI1P194MB028532875D13997DED433E9AAE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
Date: Tue, 20 Oct 2020 19:14:23 -0400
Cc: "ietf@ietf.org" <ietf@ietf.org>, IAOC Legal Committee <legal@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <81BB433C-2D20-48D9-8C13-59906D1A778F@sobco.com>
References: <VI1P194MB02851798998F8B7CAE17EBEBAE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <1244503240.69594.1603213781185@email.ionos.com> <VI1P194MB028587C3EBD5F3B842444C24AE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <CAF4+nEHhpaDUPswSPxNPtsx_daUdo95cADgk9LYDOnnRwnPkUw@mail.gmail.com> <VI1P194MB0285821C9E9877996F640B04AE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <951477273.71083.1603217515529@email.ionos.com> <VI1P194MB0285037AFE4A08626E5B0336AE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <660145062.71895.1603218804076@email.ionos.com> <VI1P194MB02858A7AA5A66986802CE483AE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <12D64980-5601-4A1D-818E-A7C8E0AA96EF@ietf.org> <957095649.74766.1603226261143@email.ionos.com> <6E027222-0293-4109-912F-D60C66218E89@ietf.org> <a1b67b9b-9033-06e1-c971-a9d3a4335759@huitema.net> <VI1P194MB02853BBD4025AE8CDF267751AE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <2FB81CBB-244B-4CFA-A83C-B8F2DBC8906C@sobco.com> <VI1P194MB028532875D13997DED433E9AAE1F0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
To: Khaled Omar <eng.khaled.omar@outlook.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B30d_xLtIVEXdw1tCw0bQislNpU>
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: Tue, 20 Oct 2020 23:14:49 -0000

by the way, it is not likely in your own interest to have these IDs deleted by the IETF (even if it were possible) 

if you ever want to prove in court that you published your ideas in a public forum (for example if someone else 
steals them or even patents them), you can point to the ID publication and the IETF Trust can provide
a declaration attesting to the fact that they were published and as to what the date of publication was

Scott


> On Oct 20, 2020, at 5:36 PM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> 
> Ok, I'll follow Christian's suggestion, but I still believe it doesn't make any sense, the older contents will not disappear completely from the IETF and this is what I wanted.
> 
> Anyway, I'll submit new versions with these tombstones.
> 
> Good luck everyone.
> 
> Khaled Omar 
> 
> -----Original Message-----
> From: Scott O. Bradner <sob@sobco.com> 
> Sent: Tuesday, October 20, 2020 11:31 PM
> To: Khaled Omar <eng.khaled.omar@outlook.com>
> Cc: ietf@ietf.org; IAOC Legal Committee <legal@ietf.org>
> Subject: Re: [legal] Enough is Enough.
> 
> Khaled,
> 	1/ as Nick pointed out, it was made very clear to you that you can not withdraw the permission you gave for the IETF to publish your ID
> 	see https://mailarchive.ietf.org/arch/msg/ietf/oUwC8jVo8pI0HQ7lx734RXTAVec/
> 
> 	2/ it would be pointless anyway, as Ted pointed out "There are a large number of repositories which mirror the internet-drafts” that
> 	are not under IETF control - IDs, once published, are forever
> 
> it is hard to see any reason to continue to fight about this - take the advice to publish “tombstones” that will hide all but the last version of your ID from anyone that does not know how to look for older versions
> 
> 
> 		Scott