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

Ted Lemon <mellon@nominum.com> Thu, 03 June 2004 22:34 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 SAA29409; Thu, 3 Jun 2004 18:34:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BW0Md-00035v-S7; Thu, 03 Jun 2004 18:07:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVzhe-0006oK-Eh for dhcwg@megatron.ietf.org; Thu, 03 Jun 2004 17:24:46 -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 RAA19371 for <dhcwg@ietf.org>; Thu, 3 Jun 2004 17:24:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVzhd-0005lA-0z for dhcwg@ietf.org; Thu, 03 Jun 2004 17:24:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVzW5-00038P-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 17:12:50 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1BVzKu-0000NJ-00 for dhcwg@ietf.org; Thu, 03 Jun 2004 17:01:16 -0400
Received: from [10.0.1.2] (dialup-4.240.114.141.Dial1.Phoenix1.Level3.net [4.240.114.141]) by toccata.fugue.com (Postfix) with ESMTP id AA16C1B3E6B; Thu, 3 Jun 2004 16:00:09 -0500 (CDT)
In-Reply-To: <200406031713.KAA27382@redback.com>
References: <200406031713.KAA27382@redback.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <14239A78-B5A1-11D8-9ACE-000A95D9C74C@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@nominum.com>
Subject: Re: [dhcwg] IPR disclosure and <draft-ietf-dhc-subscriber-id-06.txt>
Date: Thu, 3 Jun 2004 14:00:43 -0700
To: Naiming Shen <naiming@redback.com>
X-Mailer: Apple Mail (2.618)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, Bud Millwood <budm@weird-solutions.com>
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
Content-Transfer-Encoding: 7bit

On Jun 3, 2004, at 10:13 AM, Naiming Shen wrote:
> Have you read the page on http://www.ietf.org/ipr.html ?

Personally, I don't care if the RFCs are free from IPR claims, and 
indeed the mere lack of IPR claims in the IETF IPR repository doesn't 
mean no such claims exist.   However, I do think that we shouldn't 
advance drafts to RFC when there are IPR claims on the technology in 
the draft unless either there is a really strong need for the 
technology described in the draft that overrides our concerns about IPR 
issues, or the IPR notice includes a disclaimer that offers real 
protection to implementors as well as to the person who is making the 
IPR claim.

And just to be clear, the IETF's assertions regarding the text of 
internet drafts is a very different thing than patents.   I think we're 
mostly concerned about patents here, although certainly we also don't 
want to put copyrighted text into RFCs where we don't have permission 
to do so.


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