Re: Protecting Copyright.
Phillip Hallam-Baker <phill@hallambaker.com> Tue, 28 April 2020 18:52 UTC
Return-Path: <hallam@gmail.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 4E4DE3A0986 for <ietf@ietfa.amsl.com>; Tue, 28 Apr 2020 11:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.395
X-Spam-Level:
X-Spam-Status: No, score=-1.395 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 SpNzjNDfQlxD for <ietf@ietfa.amsl.com>; Tue, 28 Apr 2020 11:52:08 -0700 (PDT)
Received: from mail-oo1-f46.google.com (mail-oo1-f46.google.com [209.85.161.46]) (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 49DBD3A0AFD for <ietf@ietf.org>; Tue, 28 Apr 2020 11:51:21 -0700 (PDT)
Received: by mail-oo1-f46.google.com with SMTP id b17so4935662ooa.0 for <ietf@ietf.org>; Tue, 28 Apr 2020 11:51:21 -0700 (PDT)
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=Rt5uRgWda3EEAe9kBtQqI6dxWIiK5eZ+wR1L5SRJwCQ=; b=VHumLbtGGCBnCY9v/+BEM35yb/Je5uMuIfe7jKfnPsSgyfCFwMvzP1TUjOzovfI10k srnQCdvNxqfX/giFs1HcdAnBeYr0inu2E8Y1qlIk8Q42z9+dfgQrcFI68ehvXej9808C oduyf4LRLOPZnBh2hg7PIbspVMRXk5yymNefZi2ek5TQGN7DNjnc1lbmwPsc9AQLoIvp tFqEKVMezYlPVcO18V/T4dBQTkrIiT1EbC4oEpqqj2UMJEs68kZatM+9at5hbudUwxZ2 h3vdDhWdP7uRgts9mNQeR83lgWimQQwXmDDJQaAlZ+tfyxQ4FML5NR6NblTm9pfs+5ff Ix1A==
X-Gm-Message-State: AGi0Pub8vFUIjZsxVDXg4JQ7lSjI0qPsyYcDpiDRhP8Q4PT5kbP06urk G2Q/Bfz7o74cwlD+YDx+lO6vbl8V+95N0u37kSqmtoUV
X-Google-Smtp-Source: APiQypKneUbQa/8S2knUfDqK0faeZp6NRdmFLj6rdMXoRUNw393OKGtvhoUpz37mOp7Sp6zkYad9K6fZ41mdiD/qJFg=
X-Received: by 2002:a4a:bf0f:: with SMTP id r15mr22576006oop.12.1588099880488; Tue, 28 Apr 2020 11:51:20 -0700 (PDT)
MIME-Version: 1.0
References: <PR3P194MB0843FDF8253D2F017876787FAEAC0@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <F2CA6102-B081-4C47-8522-6A53BBB7460F@eggert.org> <PR3P194MB0843D79072ED8487BE6005EEAEAC0@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <6639B02C-A3E4-4254-9DA5-EE2673314286@episteme.net>
In-Reply-To: <6639B02C-A3E4-4254-9DA5-EE2673314286@episteme.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 28 Apr 2020 14:51:09 -0400
Message-ID: <CAMm+Lwgr04VNg+cQ7MD6kj7fzo6-Nn5A_HenFNStuy-1ffEmTg@mail.gmail.com>
Subject: Re: Protecting Copyright.
To: Pete Resnick <resnick@episteme.net>
Cc: Khaled Omar <eng.khaled.omar@outlook.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003e941d05a45e5177"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aC14ViVvalSubdIE9nz3AruxGPM>
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, 28 Apr 2020 18:52:10 -0000
Just to elaborate on Pete's response. The reason the rules are set up this way is to account for two problems that have been encountered in the past. One problem that comes up repeatedly is that someone writes a draft and stops participating in IETF process. In some cases the original author may be unreachable, there may be six authors, some may even have died. It is often completely impractical to revise a draft in those circumstances. So a draft might have to be completely rewritten to make a minor change. The other issue is that someone writes a proposal, someone else copies the entire proposal with changes the original authors disagree with and submit that with their own names on it. That is not common but has happened to me once, (though in that particular case my name had already dropped off the draft in question for reasons of politics of getting it adopted.) So the rules give two options for good reason. But for most cases, what we really need is possibly a third option which is closer to a 'moral right' sort of approach. In certain cases I do reserve copyright but what I am really after is a weaker condition which is attribution. I would be quite happy with someone taking one of my drafts and using it as the basis for a new draft provided that there is a prominent notice on the front page (or HTML equivalent) stating that this is a continuation of my draft and acknowledging that while I do not endorse this particular variation, it is built on my work. That might be something worth considering for the future as part of RFC evolution. On Tue, Apr 28, 2020 at 2:10 PM Pete Resnick <resnick@episteme.net> wrote: > On 28 Apr 2020, at 12:42, Khaled Omar wrote: > > > Is this means that anyone can use the contents of the IDs stored at > > the ietf repository !!!! > > Anyone who is contributing their work to the standards process can > include derivative works of other items contributed to the standards > process (caveat the information below). > > > So what is the copyright text included at the beginning and the end of > > each ID !!!! > > It specifically allows for derivative works. See BCP 78 (RFC 5378) > section 5.3.c <https://tools.ietf.org/html/bcp78#section-5.3>. By > including that copyright statement (and not including any other > limitations), the author has granted the right to make those derivative > works. > > > Does this includes applying what is included inside the ID without > > contacting the draft authors ?! > > Yes. An author is allowed to limit the right to make derivative works > (see section 6 <https://tools.ietf.org/html/bcp78#section-6>, but I do > not see this limitation in draft-omar-nep, which means you have granted > the right to make derivative works to the IETF Trust, and the IETF Trust > grants the right to include derivative works in new contributions to the > standards process to other authors. There is no requirement for > contacting the original draft author. > > pr > -- > Pete Resnick https://www.episteme.net/ > All connections to the world are tenuous at best > >
- Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. Rob Wilton (rwilton)
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Lars Eggert
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Pete Resnick
- Re: Protecting Copyright. JORDI PALET MARTINEZ
- Re: Protecting Copyright. DOLLY, MARTIN C
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Scott O. Bradner
- Re: Protecting Copyright. Pete Resnick
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Scott O. Bradner
- Re: Protecting Copyright. Phillip Hallam-Baker
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. John C Klensin
- Re: Protecting Copyright. Scott O. Bradner
- Re: Protecting Copyright. Scott O. Bradner
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Pete Resnick
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Scott O. Bradner
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Pete Resnick
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Michael StJohns
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. John C Klensin
- Re: Protecting Copyright. Keith Moore
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Abdussalam Baryun
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Salz, Rich
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Christer Holmberg
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Robert Raszuk
- Re: Protecting Copyright. Joseph Touch
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. Adrian Farrel
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. John C Klensin
- RE: Protecting Copyright. Adrian Farrel
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Salz, Rich
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. S Moonesamy
- RE: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. S Moonesamy
- Re: Protecting Copyright. Salz, Rich
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Salz, Rich
- RE: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Bob Hinden
- Re: Protecting Copyright. Khaled Omar
- RE: Protecting Copyright. John C Klensin
- Re: Protecting Copyright. Michael StJohns
- Re: Protecting Copyright. Khaled Omar
- Re: Protecting Copyright. Abdussalam Baryun