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

"Eggert, Lars" <lars@netapp.com> Mon, 04 April 2016 12:42 UTC

Return-Path: <lars@netapp.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 E085A12D520 for <ietf@ietfa.amsl.com>; Mon, 4 Apr 2016 05:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.931
X-Spam-Level:
X-Spam-Status: No, score=-6.931 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 rkG-dKXW5kz5 for <ietf@ietfa.amsl.com>; Mon, 4 Apr 2016 05:42:06 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC09012D5CA for <ietf@ietf.org>; Mon, 4 Apr 2016 05:42:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.24,440,1455004800"; d="asc'?scan'208";a="110366566"
Received: from hioexcmbx03-prd.hq.netapp.com ([10.122.105.36]) by mx141-out.netapp.com with ESMTP; 04 Apr 2016 05:37:05 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx03-prd.hq.netapp.com (10.122.105.36) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Mon, 4 Apr 2016 05:37:05 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::c07c:8fcd:f7e4:f32b%21]) with mapi id 15.00.1156.000; Mon, 4 Apr 2016 05:37:05 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTaY75yXT30okCzmxElqsDSFp96SlCA
Date: Mon, 4 Apr 2016 12:37:04 +0000
Message-ID: <4A755FC7-6E3F-4787-B5B1-464F29D675FD@netapp.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
In-Reply-To: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.120.60.35]
Content-Type: multipart/signed; boundary="Apple-Mail=_72E2329F-0DE9-452A-B19D-6AEC8AAC1D13"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N6gb93K_pn8j5oT38xZWd4BEcIQ>
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: Mon, 04 Apr 2016 12:42:09 -0000

Hi,

I mostly ready this from the perspective of the IRTF, since this is intended to also apply to us. I found that that wasn't terribly clear from the current text.

Lars

Section 1., paragraph 0:
> 1. Definitions

  Sorting these definitions alphabetically is not really helpful to the
  reader. Could you order them such that terms are defined before being
  referred to, or at least try?


Section 1., paragraph 3:
>    b. "Contribution": any submission to the IETF intended by the
>       Contributor for publication as all or part of an Internet-Draft or
>       RFC and any statement made within the context of an IETF activity,
>       in each case that is intended to affect the IETF Standards Process
>       or that is related to the activity of an Alternate Stream that has
>       adopted this definition.

 What do you mean by "this definition"? Also, it's not clear what
 "activity of an Alternate Stream" is supposed to convey. I think this
 intends to capture work occurring in IRTF RGs, but it's a pretty
 indirect way of stating this.


Section 1., paragraph 4:
>       Such statements include oral statements, as well as written and
>       electronic communications, which are addressed to:

  The list below does not include IRTF mailing lists or meetings.


Section 1., paragraph 9:
>    e. "IETF": In the context of this document, the IETF includes all
>       individuals who participate in meetings, working groups, mailing
>       lists, functions and other activities which are organized or
>       initiated by ISOC, the IESG or the IAB under the general
>       designation of the Internet Engineering Task Force or IETF, but
>       solely to the extent of such participation.

  For clarity, I would also call out the IRTF and its RGs here.


Section 1., paragraph 10:

>    f. "IETF Documents": RFCs and Internet-Drafts that are published as
>       part of the IETF Standards Process.  These are also referred to as
>       "IETF Stream Documents" as defined in Section 5.1.1 of RFC 4844.

  What about RFCs and Internet-Drafts that are intended as contributions
  to IRTF activities? It would be useful to maybe add "...part of the
  IETF Standards Process and related activities" to make this clearer.


Section 1., paragraph 11:
>    g. "IETF Standards Process": the activities undertaken by the IETF in
>       any of the settings described in the above definition of
>       Contribution.  The IETF Standards Process may include
>       participation in activities and publication of documents that are
>       not directed toward the development of IETF standards or
>       specifications, such as the development and publication of
>       informational documents.

  I'd again explicitly call out the alternate streams here. And maybe
  this document is meant for lawyers and I am not one, but having a
  definition called "IETF Standards Process" that also includes all of
  our non-standard-setting activities is confusing.


Section 1., paragraph 17:
>    m. "RFC": the basic publication series for the IETF.  RFCs are
>       published by the RFC Editor and once published are never modified.
>       (See [RFC2026] Section 2.1)

  Might want to mention the existence of errata.


Section 5.5., paragraph 0:
> 5.5. Licensing Information in an IPR Disclosure

  It's been running code on the IRTF side to be very OK with not having
  license terms included, esp. if it significantly delays the official
  filing of the disclosure, since RGs don't set standards and therefore
  don't really need to consider licensing terms. Not clear if that
  should be discussed here.


Section 11., paragraph 2:
>    The legal rules that apply to documents in Alternate Streams are
>    established by the managers of those Alternate Streams as defined in
>    [RFC 4844]. (i.e., the Internet Architecture Board (IAB), Internet
>    Research Steering Group (IRSG) and Independent Submission Editor).

  Is the IRSG really the manager of the IRTF stream? I thought it was
  the IRTF chair, but I can't find the definitive answer in either 4844,
  5742 or 5743...