Re: Effective vs intended handling of patent encumbrance in IETF wg and IESG

"todd glassey" <tglassey@earthlink.net> Thu, 07 June 2007 15:37 UTC

Return-path: <ipr-wg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwK3J-0007vL-OQ; Thu, 07 Jun 2007 11:37:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwK3I-0007sx-4z for ipr-wg@ietf.org; Thu, 07 Jun 2007 11:37:32 -0400
Received: from elasmtp-banded.atl.sa.earthlink.net ([209.86.89.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwK2p-00029C-T1 for ipr-wg@ietf.org; Thu, 07 Jun 2007 11:37:05 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=sNPVpRn4p/BQz4ouJcv9QmyqXGfdNzcO12FZA2LyDuM8T4bRUiSAW9mpn3PtHJjf; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [64.125.79.23] (helo=gw) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1HwK2j-0000IM-89; Thu, 07 Jun 2007 11:36:57 -0400
Message-ID: <007b01c7a919$b2336e20$174f7d40@home.glassey.com>
From: todd glassey <tglassey@earthlink.net>
To: Scott W Brim <sbrim@cisco.com>, Thierry Moreau <thierry.moreau@connotech.com>
References: <46656415.7090505@connotech.com> <4668242B.8070309@cisco.com>
Date: Thu, 07 Jun 2007 08:37:00 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c9743973a825be9b106de4c88517df5c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.125.79.23
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ipr-wg@ietf.org
Subject: Re: Effective vs intended handling of patent encumbrance in IETF wg and IESG
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Errors-To: ipr-wg-bounces@ietf.org

The IPR-WG charter is half the problem here IMHO. The IPR WG needs to be the 
ONLY PLACE within the IETF that IPR and Participation Control issues are 
addressed. They do not belong in the IETF@IETF.ORG WG since they are 
pertinent to IPR issues directly.

Todd

----- Original Message ----- 
From: "Scott W Brim" <sbrim@cisco.com>
To: "Thierry Moreau" <thierry.moreau@connotech.com>
Cc: <ipr-wg@ietf.org>
Sent: Thursday, June 07, 2007 8:28 AM
Subject: Re: Effective vs intended handling of patent encumbrance in IETF wg 
and IESG


> If I understand correctly, you are saying that a Working Group should
> take technical issues into account just as much as it takes IPR
> encumbrance into account.  Is that right?
>
> swb
>
> On 06/05/2007 09:24 AM, Thierry Moreau allegedly wrote:
>> For your information:
>>
>> In draft-ietf-dnsext-rollover-requirements, an IETF wg effectively made
>> an a-priori decision to avoid the consideration of an IPR encumbered
>> alternative; the problem area being DNSSEC trust anchor key management.
>> I spare you the details of how the wg came to this decision, and how it
>> relates to the a-priori rejected alternative.
>>
>> Now that the IESG accepted the above draft for publication as an RFC, it
>> becomes a procedural precedent for attempts to expeditiously restrict
>> IETF activities to IPR unencumbered alternatives.
>>
>> Conversely, it reinforces the economic incentive for medium and large
>> organizations to isolate the individuals participating in the IETF
>> activities from the patent application management process.
>>
>> Also, the above draft publication decision, in a context where the
>> problem area is still lacking a solution with a reasonable explicit
>> security model, is an empirical observation of the IETF strong
>> preference for "ignoring the technology" (instead of "ignoring the IPR")
>> when a tradeoff has to be made. Inescapably then, the aggregate scope
>> and field of application of IETF protocols is deemed to shrink as
>> innovation enhances the networking technology.
>>
>> Please note that I am not well aware of the detailed procedural and
>> institutional arrangements that implement RFC3979, before the appeal
>> process can correct deviations. While I was participating in the above
>> matter, I chose not to rely on the appeal process, perhaps because it
>> wasn't clear to me how things should have gone in the first place.
>>
>> P.S. Since even RFC3979 itself is absent from the IETF ipr wg charter;
>> perhaps the above is totally off-topic.
>>
>> Regards,
>>
>
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipr-wg 


_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg