Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 25 March 2016 19:40 UTC

Return-Path: <brian.e.carpenter@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 18FB012D0A1 for <ietf@ietfa.amsl.com>; Fri, 25 Mar 2016 12:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VQBy1H3_r4F1 for <ietf@ietfa.amsl.com>; Fri, 25 Mar 2016 12:40:45 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 291A412D67E for <ietf@ietf.org>; Fri, 25 Mar 2016 12:40:42 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id u190so88886337pfb.3 for <ietf@ietf.org>; Fri, 25 Mar 2016 12:40:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=elpBVMrGYIIBf9E0nE+/ajAAqnZUOH1+KG2BxoT0REg=; b=G1kf4/hFUpDNQ4YMYm+zvPecBga+x26FQqbt6saLVx7SOp3qHW7spF353zZWm61yjF z1XOaDczVdhC7tv3GTnckQuER4TtsMzzXOxzEeVemG0J7xl/HpJu85+LFRFPHroslJev ol9x7yGv4tvk7PuNDdd0s1d4L8FnrnJa0brHcKjjVpG/04+RPOaBt1kzYtWaPib2UnIv 78FOy5gYLetPx+qZ5yQngtuirzUmwB/LO6iZxTaLQGgjnAuTZhLFJO+M7PySgdIkxv3Y qO3hxUyf4OuhnT+XYSm9vNWeUaCojN296b8UQJ04ylSJfiF5jXKyNR+hiWZBRQ8Q+pSQ Ak6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=elpBVMrGYIIBf9E0nE+/ajAAqnZUOH1+KG2BxoT0REg=; b=bZI/OSUEgtbJt6M8xyTHbkkEdhb3DtK/ErQqWeOkKDTLFcPu1YIuD+MKplnvQw+14t 7UlEtn8xx6jBoD6vS2ADoX6wIY3EVlcV4ONuMHW3DPu3grkbZuFr75i/Z/PjzHnFrIqm pIj0qwGOMwrh/eGrDNLtvHHecJk4xUL+xp7vs97JHonez9EcAEz/Y6z479WRD9LAJ9wn U703npRP7iECFbuHyWq81dVcKMpIfvYlMIcGwGBpXSB+sol4BBd2oXohXnL2fcOP683c DCPWMZIKSCzbpVRbY1fi7ARxAO/94Ziylovo0xuYDRjBOkjTxxYDrs++T8Avp4GXKaLW /a5w==
X-Gm-Message-State: AD7BkJKktC3799KSyaNgwQvS2p20DxJMX9Rz+sPyqxuVMUBUW7RJqDc5ryLsKUC4cvUNZQ==
X-Received: by 10.98.9.83 with SMTP id e80mr23552262pfd.34.1458934841689; Fri, 25 Mar 2016 12:40:41 -0700 (PDT)
Received: from ?IPv6:2406:e007:65bb:1:28cc:dc4c:9703:6781? ([2406:e007:65bb:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id n66sm18141959pfj.39.2016.03.25.12.40.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Mar 2016 12:40:40 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Russ Housley <housley@vigilsec.com>, Jari Arkko <jari.arkko@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <DC9B799D-A1EF-457C-B791-9F103FDA7CD6@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56F59441.8030901@gmail.com>
Date: Sat, 26 Mar 2016 08:40:49 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <DC9B799D-A1EF-457C-B791-9F103FDA7CD6@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_vR8Tq_7NyFvL790DUQ_I6cUEyI>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 25 Mar 2016 19:40:47 -0000

Russ,

Comment at the end:

On 26/03/2016 05:28, Russ Housley wrote:
> Jari:
> 
> I looked at the diff between RFC 3979 and draft-bradner-rfc3979bis-08.txt.  The changes are substantial.  Over the last few years there have been sessions at IETF meetings about the things that needed to be clarified, but my interpretation of those discussions was that we had most things right and a few things needed to be clarified.  So the extent of the proposed changes is a bit of a surprise to me.  I do not find Section 13 helpful is explaining the changes that were made, or the rationale for them.
> 
> The definition of Contribution now includes:
> 
>       o any IETF-sanctioned design team or portion thereof,
> 
> I really have a problem with the use of "IETF-sanctioned” in this bullet.  RFC 2418 talks about design teams.  It says:
> 
> 6.5. Design teams
> 
>    It is often useful, and perhaps inevitable, for a sub-group of a
>    working group to develop a proposal to solve a particular problem.
>    Such a sub-group is called a design team.  In order for a design team
>    to remain small and agile, it is acceptable to have closed membership
>    and private meetings.  Design teams may range from an informal chat
>    between people in a hallway to a formal set of expert volunteers that
>    the WG chair or AD appoints to attack a controversial problem.  The
>    output of a design team is always subject to approval, rejection or
>    modification by the WG as a whole.
> 
> It seems to me that the design team, whether established by the leadership or self organized, intends to influence the IETF document.  For this reason, I think that any design team participation must be considered a contribution.

It's clear that any design team *output* is a contribution. But if a group
of friends have a chat over lunch, not as a design team mandated by WG chairs,
and one of them mentions a silly idea that is rejected in favour of a good
idea that the group later proposes to the WG, is that silly idea a contribution?
I don't think so.

All the same, I think the phrase "IETF-sanctioned" is redundant. A citation
of RFC 2418 would be in order, perhaps.

Regards
   Brian