RE: [legal] Enough is Enough.

[Khaled Omar <eng.khaled.omar@xxxxxxxxxxx>]

>> The simplest path for Khaled is to update each of his drafts, replacing the content with a short text that says something like "This contribution has been withdrawn." That way, everyone who searches for the draft will be shown the latest version and learn its status. We call such drafts "tombstones", but that's jargon.

Why I need to do that, all what I’m trying to do now is to take my work and unsubscribe, I don’t want to leave my work at the IETF public archive with such a comment at the latest version, the IESG can approve the deletion and that’s all, whom at the IESG, I don’t know, please tell me who is responsible and authorized to do that.

 

Khaled Omar

 

From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of Christian Huitema
Sent: Tuesday, October 20, 2020 11:00 PM
To: Jay Daley <jay@xxxxxxxx>; Timothy Mcsweeney <tim@xxxxxxxxxxxxxx>
Cc: ietf@xxxxxxxx; legal@xxxxxxxx
Subject: Re: [legal] Enough is Enough.

 

 

On 10/20/2020 1:52 PM, Jay Daley wrote:

On 21/10/2020, at 9:37 AM, Timothy Mcsweeney <tim@xxxxxxxxxxxxxx> wrote:

Jay,

As stated in BCP 79

"The authors retain all other rights, but cannot withdraw the above

rights from the IETF Trust and the IETF."

That was in BCP 78.  And section 4 makes that argument moot for Khaled, don't you agree? 

No I don’t.  The I-Ds in question are very clearly "Contributions made as part of the IETF Processes" and so section 4 does not apply. 

 

And that's an important principle. The archive is the archive. Once something has been written and published, it cannot be unwritten and unpublished.

The simplest path for Khaled is to update each of his drafts, replacing the content with a short text that says something like "This contribution has been withdrawn." That way, everyone who searches for the draft will be shown the latest version and learn its status. We call such drafts "tombstones", but that's jargon.

-- Christian Huitema