Re: Proposed IESG Statement on IPR Declarations

Barry Leiba <barryleiba@computer.org> Fri, 08 July 2016 15:34 UTC

Return-Path: <barryleiba.mailing.lists@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 3ABAA12D84D; Fri, 8 Jul 2016 08:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rwm1AGSsymLo; Fri, 8 Jul 2016 08:34:23 -0700 (PDT)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 BAB1D12D885; Fri, 8 Jul 2016 08:34:17 -0700 (PDT)
Received: by mail-io0-x241.google.com with SMTP id k78so10166594ioi.2; Fri, 08 Jul 2016 08:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=+Tb1+lQ1ZF/RQcC/ElJFYt8Q0CHxLzeWLt9tHOcvMeY=; b=uxo6xKp6sg3fdcyCtkFC3kWVHpK3dzEctSGNdAGEyKF5YLdPhcQy4IIqd2BdYJ0ZVn WsEYxV93zldqimW559FHMCr43S+aM4HVV9anYot8HHUE9/1DkJBcQCdpcgaoslfY2fIN Ou5ZUDNLkPbV+7KTVKHqbJUwe0iGYtCtt5eMgG9mnHOaueK08lsRwyDAlrp+aQRJwCZL 1zqnRF9xJS547wU+UYVmMRiOuj1rb3Ha6rQKLXlUw/MoLdzkPOnUBwdt+/QTOGvy8M3+ DEtFJhmeiuyVXL97TFaO44mjrWNwqjys0ERsq3+J4CQaLSyX8tPfNrcKJD6U4jEmdtWU 5tvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=+Tb1+lQ1ZF/RQcC/ElJFYt8Q0CHxLzeWLt9tHOcvMeY=; b=lBcBgbokV+6/udmGSFJcUzGHhxragBsdeb2X/hEXHQWmk3fySdSiBmjCA64rHaogei aU6962d7fsOFTBpjeUVIgHRJCp4lHTYlAAUsr5/tDdIXmMEYYvEWTMtOPePEM1zzT8WI bZAx8s74u5vaD1PUsonAYjLsY1VhUhT+/JyzHWYcSAAle+QPu7DfO5Y2uV8mtGjeOqtU 39wMgJoojZaxLkULwjHTBBm8pBEDbM0vxkFa+TPumSiuB6oKMrtNOzO8UU8dfluktLta hmZ55ps20uwH2JorVfzjcOUbfTuZZxC7/BWGZaVHrEGIru1aUh2aR0tRxEl4AM6FBG4F vEqw==
X-Gm-Message-State: ALyK8tIpVQjkNNwjhIydPkSFpUE+/pQMwZYEnhCG/BsttH5O+FeYGoMURkVutPL5RhUF/1L/CWPUxfTN/vLgfQ==
X-Received: by 10.107.134.101 with SMTP id i98mr9720535iod.41.1467992056714; Fri, 08 Jul 2016 08:34:16 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.153.78 with HTTP; Fri, 8 Jul 2016 08:34:16 -0700 (PDT)
In-Reply-To: <20160707202122.23634.18168.idtracker@ietfa.amsl.com>
References: <20160707202122.23634.18168.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 08 Jul 2016 11:34:16 -0400
X-Google-Sender-Auth: QJgagbFxeMvfry3co3DVRt97L0s
Message-ID: <CAC4RtVAEQfWN-xgtrDS0kKg6EV22hdskJKL++vsp80vi0XOjUA@mail.gmail.com>
Subject: Re: Proposed IESG Statement on IPR Declarations
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kSC27bZpyMmi50VKYHLBszfPM9s>
Cc: IESG <iesg@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, 08 Jul 2016 15:34:26 -0000

> The IESG is considering an IESG statement on IPR Declarations, and would
> like to solicit comments from the community on the proposed text. The
> proposed text is provided below.
>
> The IESG will make a decision about this matter shortly. Please provide
> comments, if any, to ietf@ietf.org or to the IESG at iesg@ietf.org
> before July 31, 2016.

The statement below seems to amount to "The IESG has nothing to do
with IPR disclosures," and nothing more.  I don't understand why the
IESG wants to put that out as an IESG Statement, rather than, say,
posting it prominently on the IPR disclosure pages (where people who
need to see it might actually see it), and making sure that it also
covers the IAB, and maybe the IAOC, ISOC, and the IETF Secretariat.

Barry

> ——
>
> IESG Statement on IPR Declarations:
>
> BCP 79 discusses Intellectual Property Rights (IPR) within the IETF
> process and technologies being worked on at the IETF.
>
> Among other things, BCP 79 specifies how and when IPR disclosures ought
> to be made. The purpose of such disclosures is to inform IETF
> participants and those that use IETF technologies about IPR that may be
> associated with the technology in question.
>
> The IESG also observes that the IETF posts all IPR disclosures (other
> than obvious spam, which is not an IPR disclosure), as they are
> received, in our IPR disclosure database. This database is available at
> https://www.ietf.org/ipr/.
>
> However, as noted in BCP 79, the IETF will make no determination about
> the validity of any particular IPR claim. Neither the IETF nor the IESG
> makes any attempt to verify patent validity or the validity of any other
> statements in the IPR disclosure text. As BCP 79, Sec. 4(B) indicates:
>
> "The IESG disclaims any responsibility for identifying the
> existence of or for evaluating the applicability of any IPR,
> disclosed or otherwise, to any IETF technology, specification or
> standard, and will take no position on the validity or scope of
> any such IPR claims."
>
> The material posted as IPR disclosures should be viewed as originating
> from the source of that information, and any issue or question related
> to the material should be directed to the source rather than the IETF.
> There is no implied endorsement or agreement by the IETF or the IESG
> with any of the material.
>