Re: How IETF treats contributors

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 01 September 2004 17:14 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11828; Wed, 1 Sep 2004 13:14:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2YjP-00064x-6D; Wed, 01 Sep 2004 13:17:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2XZ1-0008Bu-9g; Wed, 01 Sep 2004 12:02:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2WPy-0000d3-VN for ietf@megatron.ietf.org; Wed, 01 Sep 2004 10:48:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21443 for <ietf@ietf.org>; Wed, 1 Sep 2004 10:48:56 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2WS9-0003t4-IK for ietf@ietf.org; Wed, 01 Sep 2004 10:51:16 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id DDB1161B9D; Wed, 1 Sep 2004 16:48:24 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23646-05; Wed, 1 Sep 2004 16:48:23 +0200 (CEST)
Received: from [192.168.1.4] (145.80-202-211.nextgentel.com [80.202.211.145]) by eikenes.alvestrand.no (Postfix) with ESMTP id D447A61B89; Wed, 1 Sep 2004 16:48:22 +0200 (CEST)
Date: Wed, 01 Sep 2004 16:48:23 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Hadmut Danisch <hadmut@danisch.de>
Message-ID: <0CE70BFB899C776B25B082D2@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20040831185802.GA22942@danisch.de>
References: <20040830090627.GA22982@danisch.de> <Pine.LNX.4.44.0408301607571.28223-100000@cirrus.av8.net> <20040831185802.GA22942@danisch.de>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

Hadmut,

you made a complaint about the SPF draft to the IESG just prior to the 
March IETF meting in Korea.

I'd like to reproduce the answer I sent you at that time here:


> Dear Hadmut:
>
> Thank you for your inquiry.  Obviously, there is nothing that the IETF
> can do regarding the many activities that you mention as occurring
> outside the IETF process (e.g., the SPF list, the various newspaper
> articles, etc.)
>
> With respect to your complaint regarding draft-mengwong-spr-00.txt (the
> "SPF I-D") I would like to refer you to RFC 3667 "IETF Rights in
> Contributions", which updates the relevant sections of RFC 2026 regarding
> contributions to the IETF standards process - this document lists the
> various kinds of IPR that were deemed to be relevant to the IETF process.
>
> Under Section 3.4.a of RFC 3667, each contributor of an IETF document
> represents that: "The Contribution properly acknowledges all major
> Contributors.  A major Contributor is any person who has materially or
> substantially contributed to the IETF Contribution."  In addition, under
> Section 3.4.c, the Contributor represents that he has the full right to
> grant IETF a license under the copyrights in the Contribution. This seems
> to be the part of IETF procedure relevant to your complaint.
>
> If you believe that the SPF I-D infringes your copyrights or that you
> should be listed as an author of the SPF I-D, you should follow the
> procedures for conflict resolution described in Section 6.5 of RFC 2026.
> I suggest that when you submit your request, you identify the particular
> sections of the SPF-ID that you believe are infringing on your
> copyrights, together with the sections of your original publications that
> you believe have been infringed. If you believe that you have not been
> properly acknowledged for your contribution to the SPF work, please
> provide details of what acknowledgement you would deem correct and
> adequate.
>
> You may choose to discuss this further with the relevant AD for the MARID
> BOF (Steve Bellovin), or to send directly to the IESG.
>
> While the IETF is not a court of law, our processes are intended to
> facilitate the fair and equitable resolution of disputes within the IETF
> standards process. We need to facilitate the open exchange of ideas - but
> we need to make sure are being treated fairly in the process, or the
> exchange of ideas will eventually stop.
>
> Thank you for bringing this issue to our attention.
>
>             Harald Alvestrand, IETF Chair

I have not seen a reply from you to the IESG, so I do not know what has 
happened since that time.

                           Harald


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf