[dhcwg] IPR disclosure and <draft-ietf-dhc-subscriber-id-06.txt>

Ralph Droms <rdroms@cisco.com> Wed, 02 June 2004 02:32 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16205; Tue, 1 Jun 2004 22:32:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVLDI-0001WV-Kc; Tue, 01 Jun 2004 22:10:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVFWr-000764-MQ for dhcwg@megatron.ietf.org; Tue, 01 Jun 2004 16:06:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20909 for <dhcwg@ietf.org>; Tue, 1 Jun 2004 16:06:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVFWq-0007Rz-EL for dhcwg@ietf.org; Tue, 01 Jun 2004 16:06:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVFVJ-0006Sr-00 for dhcwg@ietf.org; Tue, 01 Jun 2004 16:04:58 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BVFTC-0005NP-00 for dhcwg@ietf.org; Tue, 01 Jun 2004 16:02:46 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 01 Jun 2004 13:02:59 +0000
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i51K2DXl003373 for <dhcwg@ietf.org>; Tue, 1 Jun 2004 13:02:14 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.119]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJA07403; Tue, 1 Jun 2004 16:02:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040601155834.02ada9a0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 01 Jun 2004 16:02:09 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [dhcwg] IPR disclosure and <draft-ietf-dhc-subscriber-id-06.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

The dhc WG has "Subscriber-ID Suboption for the DHCP Relay Agent
Option", <draft-ietf-dhc-subscriber-id-06.txt>", as a work item.  This
Internet Draft has passed WG last call and IETF last call.  There is
an IPR disclosure associated with this Internet Draft,
http://ietf.org/ietf/IPR/PacketFront-IPR.txt.  The WG needs to decide
if it is willing to accept the specification in the Internet Draft
with the associated IPR disclosure.

draft-ietf-dhc-subscriber-id-06.txt passed WG last call on 2003-09-12
and passed IETF last call on 2004-02-03.  During the IETF last call,
the IESG received a notification of an IPR disclosure related to the
Internet Draft.  Although the IPR disclosure had been published
2003-04-17, there was no general notification of that publication and,
apparently, no one in the dhc WG or the IESG was aware of the IPR
disclosure.

The dhc WG discussed the publication of the Internet Draft on the
dhcwg mailing list and there was support on both sides of the issue.
Because RFC 3667 and RFC 3668 were both ready for publication,
discussion was suspended pending publication of those new documents
related to IPR in the IETF.

The original IPR disclosure applied to two Internet Drafts,
<draft-ietf-dhc-subscriber-id-00.txt> and <draft-ietf-dhc-
server-override-00.txt>.  The original disclosure made no mention of
any use licensing agreements for the IPR.  Concurrently with the WG
discussion on the IPR disclosure, a new IPR disclosure was published
on 2004-02-02, which refers only to
<draft-ietf-dhc-subscriber-id-00.txt> and which includes RAND
(reasonable and non-discriminatory) licensing terms.

RFC 3667, "IETF Rights in Contributions," and RFC 3668, "Intellectual
Property Rights in IETF Technology" are both relevant to the dhc WG
discussion of <draft-ietf-dhc-subscriber-id-06.txt>.

Note that the need for disclosure of the IPR issues in this case,
although the editors of the draft are not associated with the
organization submitting the IPR disclosure, is established by section
6.1.2 of RFC 3668, which requires that:

    Any individual participating in an IETF discussion who reasonably and
    personally knows of IPR meeting the conditions of Section 6.6 which
    the individual believes Covers or may ultimately Cover a Contribution
    made by another person, or which such IETF participant reasonably and
    personally knows his or her employer or sponsor may assert against
    Implementing Technologies based on such Contribution, must make a
    disclosure in accordance with this Section 6.

<draft-ietf-dhc-subscriber-id-06.txt> contains the text required by
section 5 of RFC 3668 because of the IPR disclosure relative to the
Internet Draft. The current IPR disclosure meets the intent (if not
the letter) of section 6.4 of RFC 3668, and the licensing terms meet
the RAND requirements of section 6.5 of RFC 3668.  At this point, the
decision about whether or not to accept
<draft-ietf-dhc-subscriber-id-06.txt> as a standard rests with the dhc
WG.

I need to assess the WG consensus for how to proceed with
<draft-ietf-dhc-subscriber-id-06.txt>.  Each WG member should review
the Internet Draft, the IPR disclosure, RFC 3667 and RFC 3668 to form
an opinion about whether <draft-ietf-dhc-subscriber-id-06.txt> should
move forward through the standards process.  We will conduct a
discussion on the WG mailing list, to conclude on Friday, 2004-06-11.
I will use the discussion to assess the WG consensus.

- Ralph


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