Re: RFC3979bis section 7 -- hierarchy of preference for licensing
Thomas Narten <narten@us.ibm.com> Mon, 19 August 2013 12:19 UTC
Return-Path: <narten@us.ibm.com>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4934311E8249 for <ipr-wg@ietfa.amsl.com>; Mon, 19 Aug 2013 05:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oE8YxrDy-yN for <ipr-wg@ietfa.amsl.com>; Mon, 19 Aug 2013 05:19:11 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id D2AA411E80E2 for <ipr-wg@ietf.org>; Mon, 19 Aug 2013 05:19:10 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ipr-wg@ietf.org> from <narten@us.ibm.com>; Mon, 19 Aug 2013 08:19:09 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 19 Aug 2013 08:19:08 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 9FD1E38C804D for <ipr-wg@ietf.org>; Mon, 19 Aug 2013 08:18:35 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7JCIb6r146568 for <ipr-wg@ietf.org>; Mon, 19 Aug 2013 08:18:37 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r7JCIa0N021348 for <ipr-wg@ietf.org>; Mon, 19 Aug 2013 09:18:37 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-65-36-34.mts.ibm.com [9.65.36.34]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7JCIXtf021144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 09:18:35 -0300
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r7JCIXUN005969; Mon, 19 Aug 2013 08:18:33 -0400
Message-Id: <201308191218.r7JCIXUN005969@cichlid.raleigh.ibm.com>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: RFC3979bis section 7 -- hierarchy of preference for licensing
In-reply-to: <CE30292A.A0AE7%stewe@stewe.org>
References: <CE30292A.A0AE7%stewe@stewe.org>
Comments: In-reply-to Stephan Wenger <stewe@stewe.org> message dated "Tue, 13 Aug 2013 16:19:27 -0000."
Date: Mon, 19 Aug 2013 08:18:33 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13081912-7182-0000-0000-000008225923
Cc: "ipr-wg@ietf.org" <ipr-wg@ietf.org>
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipr-wg>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 12:19:18 -0000
I wasn't able to attend the Berlin session. Can you please remind us of what problem the suggested text is intended to fix? I.e., what is broken that needs fixing? If the intent is to just to make clear that Non-assert is more friendly to open source, and thus a preferance over simple RF, that is one thing, and I think is closer to where the IETF is today than the current RFC text. On the other hand, I'm less sure that spelling out a heirarchy is something we should (or need to) do. For one thing, it's not a straight hierarchy. IPR disclosures tend to have pesky reciprocity clauses, which mean that something like a specific RAND license may well be viewed as better (by some folks) than something "above it" in the heirarchy. It all depends on the specific clauses, which have to be evaluated on a case-by-case basis and vary quite widely today. Thomas
- RFC3979bis section 7 -- hierarchy of preference f… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Barry Leiba
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Peter Saint-Andre
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephen Farrell
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Brian E Carpenter
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephen Farrell
- RE: RFC3979bis section 7 -- hierarchy of preferen… David Rudin (LCA)
- Re: RFC3979bis section 7 -- hierarchy of preferen… Ted Hardie
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- RE: RFC3979bis section 7 -- hierarchy of preferen… Michael Cameron
- RE: RFC3979bis section 7 -- hierarchy of preferen… Turner, Kimberly A
- Re: RFC3979bis section 7 -- hierarchy of preferen… tsg
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- Re: RFC3979bis section 7 -- hierarchy of preferen… Ted Hardie
- Re: RFC3979bis section 7 -- hierarchy of preferen… Stephan Wenger
- RE: RFC3979bis section 7 -- hierarchy of preferen… David Rudin (LCA)
- Re: RFC3979bis section 7 -- hierarchy of preferen… Thomas Narten
- Re: RFC3979bis section 7 -- hierarchy of preferen… Scott Brim
- Re: RFC3979bis section 7 -- hierarchy of preferen… Brian E Carpenter
- Re: RFC3979bis section 7 -- hierarchy of preferen… Scott Brim