Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
SM <sm@resistor.net> Wed, 09 May 2012 23:02 UTC
Return-Path: <sm@resistor.net>
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 EBC8A11E8086 for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 16:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level:
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, 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 b3kwoykeB3TZ for <ietf@ietfa.amsl.com>; Wed, 9 May 2012 16:02:54 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9915311E80CF for <ietf@ietf.org>; Wed, 9 May 2012 16:02:54 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q49N2l8K006149; Wed, 9 May 2012 16:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336604572; i=@resistor.net; bh=KC0+1HJrlLofhb7vTIt5oeeMH3RATfFYBM4YrEN6i/4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ku1yaNpCziFxx8ldW8k/Pb/XbvYhsT4sG8nQRYWQ23HHS8jnkn7ThS39S70V4As8y EevIyRb14Dt6Rwlje14pQD+3HzCUA/FmGuq9X4EMDHGns3wscQ4D53dudpVLm0eyE6 p5X9Dda3V0VpYnQtns2CKbhRH0P+ms1MYDPjA2b4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336604572; i=@resistor.net; bh=KC0+1HJrlLofhb7vTIt5oeeMH3RATfFYBM4YrEN6i/4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tPphKPbfnMwsEFd3hEJjp98OUWPB2R4MDuynbaCBXvwWhpZeL2I97jzYrJjDMPJGH WrEeL2UTx47MZ8pl1S1KYaDbj4gIfFMwUBS0JEH2A8zeL0FgnPlj8YJhZcH9aUxKC8 Px7iJo4smxT9qDzsaCJvrNqAvC3RfA5HCEtXkULo=
Message-Id: <6.2.5.6.2.20120509150640.090d7098@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 15:58:47 -0700
To: Pete Resnick <presnick@qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
In-Reply-To: <4FAAD14F.40009@qualcomm.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 May 2012 23:02:58 -0000
At 13:19 09-05-2012, Pete Resnick wrote: >Shown how and by whom? I think you're conflating two things here. >Any participant can *call* for sanctions to be applied to anyone >they believe has violated the policy. No libel in saying that I >believe you have violated the policy. The sanctions ought not be >applied until the chair/AD/whoever reasonably determines that the >policy has in fact been violated. But that's not what the sentence >above is talking about. I don't want participants to think that they >can't bring up the issue of violation without some sort of "burden >of proof". Can we figure out some words that express both things? Here's some text for the entire paragraph: Any IETF participant can call for sanctions to be applied to anyone they believe has violated the IETF's IPR policy. This can be done by sending email to the appropriate IETF mailing list. The area director or working group chair will discuss the matter with the IETF participant and determine whether the policy has in fact been violated. Thus, when sanctions are called for, working group chairs will be the first actors when there is an active working group involved in the technical work, and area directors will be the first actors in other cases. I avoided the "including a short summary of the relevant facts and events" as it comes out as "burden of proof". Regards, -sm
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- RE: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Yoav Nir
- RE: Last Call: <draft-farrresnickel-ipr-sanctions… Adrian Farrel
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Pete Resnick
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Fred Baker
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Randy Bush
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Pete Resnick
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Livingood, Jason
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Mark Andrews
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Randy Bush
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Peter Saint-Andre
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Brian E Carpenter
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… SM
- Re: Last Call: <draft-farrresnickel-ipr-sanctions… Hector Santos
- Leverage Patent Search API to reduce BCP79 relate… Hector Santos
- Re: Leverage Patent Search API to reduce BCP79 re… Nick Hilliard
- Re: Leverage Patent Search API to reduce BCP79 re… Russ Housley
- Re: Leverage Patent Search API to reduce BCP79 re… Martin Rex
- URI listing (was: Leverage Patent Search API to r… SM
- Re: Leverage Patent Search API to reduce BCP79 re… ned+ietf
- Re: Leverage Patent Search API to reduce BCP79 re… Dave Crocker