unsubscribe
Daniel Maia <danielmaiax@gmail.com> Fri, 27 January 2012 13:38 UTC
Return-Path: <danielmaiax@gmail.com>
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 EEF2521F854B for <ietf@ietfa.amsl.com>; Fri, 27 Jan 2012 05:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 s7-yrwYz92Xg for <ietf@ietfa.amsl.com>; Fri, 27 Jan 2012 05:38:54 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7E521F851D for <ietf@ietf.org>; Fri, 27 Jan 2012 05:38:48 -0800 (PST)
Received: by yenm3 with SMTP id m3so847882yen.31 for <ietf@ietf.org>; Fri, 27 Jan 2012 05:38:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hK1cB1KpOhBIdcnQdsQSJfVixaJwSFN1WIs5+sa8gU8=; b=eCnqnV28IxLcF/PzZ7ci5wYLZjN1V6r0RukzrxFA7L6QjolmCZYmf691lyhnCxkVuV Uwxjy+coQIyCQsnMbm/VUDsYkOA9dBSnj4AdPbgCZZI5Xp60aORCj8c59dsL2J6GEPwJ Owm7+YKbj6WN2x9d1MbhA/rtX6s/1Iufgzxg8=
Received: by 10.236.116.99 with SMTP id f63mr10678701yhh.119.1327671527680; Fri, 27 Jan 2012 05:38:47 -0800 (PST)
Received: from [192.168.1.102] (201-67-34-232.bsace703.dsl.brasiltelecom.net.br. [201.67.34.232]) by mx.google.com with ESMTPS id g32sm20162076ann.19.2012.01.27.05.38.45 (version=SSLv3 cipher=OTHER); Fri, 27 Jan 2012 05:38:47 -0800 (PST)
Message-ID: <4F22A8E1.1010905@gmail.com>
Date: Fri, 27 Jan 2012 11:38:41 -0200
From: Daniel Maia <danielmaiax@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: unsubscribe
References: <mailman.3520.1327607659.3200.ietf@ietf.org>
In-Reply-To: <mailman.3520.1327607659.3200.ietf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 27 Jan 2012 13:38:56 -0000
On 26/01/2012 17:54, ietf-request@ietf.org wrote: > If you have received this digest without all the individual message > attachments you will need to update your digest options in your list > subscription. To do so, go to > > https://www.ietf.org/mailman/listinfo/ietf > > Click the 'Unsubscribe or edit options' button, log in, and set "Get > MIME or Plain Text Digests?" to MIME. You can set this option > globally for all the list digests you receive at this point. > > > > Send Ietf mailing list submissions to > ietf@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/ietf > or, via email, send a message with subject or body 'help' to > ietf-request@ietf.org > > You can reach the person managing the list at > ietf-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ietf digest..." > > > Today's Topics: > > 1. Re: Second Last Call: > <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion > Mechanism: SIP MESSAGE) to Proposed Standard (John C Klensin) > 2. encouraging compliance with IPR disclosure rules > (Peter Saint-Andre) > 3. RE: Second Last Call: > <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification > Mechanism: SIP MESSAGE) to Proposed Standard (Worley, Dale R (Dale)) > 4. Re: Second Last Call: > <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification > Mechanism: SIP MESSAGE) to Proposed Standard (Pete Resnick) > 5. Re: encouraging compliance with IPR disclosure rules (SM) > 6. Re: Violation of IETF process (todd glassey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Jan 2012 12:37:06 -0500 > From: John C Klensin<john-ietf@jck.com> > To: Pete Resnick<presnick@qualcomm.com> > Cc: adrian@olddog.co.uk, sieve@ietf.org, ietf@ietf.org > Subject: Re: Second Last Call: > <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion > Mechanism: SIP MESSAGE) to Proposed Standard > Message-ID:<C5B776163626422FFE08BD2D@PST.JCK.COM> > Content-Type: text/plain; charset=us-ascii > > > > --On Thursday, January 26, 2012 10:08 -0600 Pete Resnick > <presnick@qualcomm.com> wrote: > >> As I've mentioned to others, since I'm one of the people who >> will have to judge the consensus on this question, my comments >> will remain strictly based on the facts of the events as I >> know them and on the relevant IETF procedures. It is up to the >> IETF community to decide on what the appropriate course of >> action shall be. That said, I have some comments and questions: >> >> On 1/26/12 3:31 AM, John C Klensin wrote: >> >>> It seems to me that a key question here is whether the >>> original author's decision to not disclose was made in >>> violation of company policy or whether the sequence of >>> posting the I-D, getting the document through the WG and Last >>> Call, and then posting the disclosure is a matter of company >>> policy. >> We were told by the other company employees who facilitated >> the disclosures, at the time of the disclosures, that this was >> strictly an individual's failure to comply with the IETF IPR >> Policy, that the author in question claims not to have >> understood the IETF IPR Policy, and that the company proceeded >> to make these disclosures as soon as it discovered that this >> IPR existed. I have no information to contradict that claim. > Excellent. I had hoped that was the situation. It obviously > makes things much easier (and some of my earlier comments > irrelevant). With all the effort we go to ("Note Well" and > otherwise) to be sure that people are informed about the policy, > I have trouble generating sympathy for someone who says "didn't > underatand", but that is another matter (and perhaps just my > problem). > >>> Consequently, I believe that at least the following should be >>> required: >>> >>> (1) Revision of the IPR statement so it identifies the >>> responsible individual by name, department, and title. I do >>> not believe that the rather anonymous "Director of Licensing" >>> is compliant with the intent of the IPR disclosure rules. I >>> will leave it to the lawyers to advise on whether a document >>> issued without the name (not just title) of a responsible >>> individual would even be held to be valid in the various >>> jurisdictions in which the patent might be recognized. >>> >> Are you asking that the IPR statements be updated with the >> name, department, and title of the "Director of Licensing", or >> that of the author of the documents and patents in question? > The former. > >> It seems to me that the former is a procedural question that >> is separate from the disposition of these particular >> documents, and seems like a reasonable requirement for any IPR >> disclosure. > That is correct. I believe I suggested in a later note that > this is an area to which it would be good if the Trust paid some > attention and advised the Secretariat and others accordingly. > >>> (2) A request to the company involved for someone who can >>> formally speak for that company to publicly clarify that this >>> sequence of behavior occurred in violation of company policy. >>> If there are internal rewards to individuals for filing and/or >>> being awarded patents, I assume that a decision that the >>> actions violate company policy would cause such awards to be >>> withheld in this case, even though the IETF would have no way >>> to verify whether or not that occurred. >> The IETF Chair has in the past sent messages to companies to >> inquire about their handling of IPR disclosures, so I imagine >> such a message could be sent if the IETF community desires it. > That was my assumption. On the other hand, if it is already > clear that this was either a misunderstanding, a violation of > company policy, or both, it might not be necessary. > >>> (3) A request to the company involved to remove the >>> reciprocity clause from the license stated in the disclosure >>> statement. As a show of good faith, they should agree to >>> derive no benefit from the patent other than what praise >>> accrues from having it awarded. >> I'll ask to bring this topic up with the IETF attorney. I am >> pretty sure we can *ask* that they do this as a show of good >> faith. I am also pretty certain that we can't negotiate the >> terms of a license agreement. > I was only suggesting asking. If they say "no", which they > obviously have the right to do, it is, as others have pointed > out, the WG's problem to consider what that is an issue. If the > WG is indifferent on the issue, it seems to me that the relevant > AD has a problem, but that problem is _not_ bound to the > disclosure issue. > >>> (4) Removal of the offending individual from the list of >>> authors to the acknowledgments with text similar to that >>> suggested by Adrian. Unless the company involved is willing >>> to provide the clarification suggested in (2) above, and >>> possibly the license modification suggested in (3) above, all >>> names of authors associated with that company should be >>> removed to the acknowledgements and the company affiliation >>> explicitly identified there. In either case, this should be >>> viewed as a response to a policy violation and not entangled >>> with any more general discussion of listed authors on I-Ds or >>> RFCs. >> Of course, removal of individual document editors is well >> within the rights and responsibilities of the chairs, so if >> this is the consensus of the IETF, I am sure it can be done. > That was my assumption. > >> I >> would like you to elaborate on the issue of the authors who >> are employees of the company but *not* the author of the >> patent in question. Are you saying that their names should be >> removed because, as co-workers of the author in question, they >> ought to have known (or been more diligent in confirming) that >> the IPR existed and therefore should be sanctioned for failing >> to comply with the IPR rules, or are you saying that this is a >> sanction that should be levied against the company and >> therefore its employees? > If the other authors from that company have already told us that > they were not aware of the patent application until very late in > the process and that they moved diligently toward getting an > appropriate disclosure filed as soon as they did find out, my > suggestion is moot. > > I was concerned about the (thoroughly unlikely in this case) > possibility that the other authors from that company were > personally aware of the IPR but had been, e.g., advised that > they were not to make the disclosure because someone else would > take responsibility for it. > >> I will note that RFC 3979 does not >> put a responsibility on individual participants to go discover >> IPR that may exist, nor does it make any overt requirements of >> companies since it applies only to the individual participants >> in the IETF (caveat the recognitions in sections 6.6 and 7). > Understood. My separate concerns about the implications of that > policy should a company ever choose to deliberately hide > relevant IPR from IETF participants do not apply to this case > and should not be part of the discussion. > >>> (5) Unless the clarification suggested in (2) can be provided, >>> each IETF participant who is associated with the relevant >>> company and who is in an IETF-related leadership or >>> decision-making position (WG Chairs; Editors; IESG, IAB, IAOC, >>> Nomcom, members; etc.) should be asked to make a conscientious >>> personal review as to whether this type of action sufficiently >>> compromises his or her position that resignation or some other >>> action would be appropriate and, as appropriate, to review >>> IETF policies with whatever management chains are relevant. >>> I am _not_ suggesting that anyone be asked to resign, only >>> that they engage in careful consideration of the issues and >>> their implications. >> I believe this last one is outside of the scope of the >> decisions the IETF has to take regarding the disposition of >> the particular documents. It may indeed be reasonable for >> every IETF participant to review the policies and actions of >> their own employer as they relate to IETF participation and >> make a conscientious decision whether they can continue to >> participate in the IETF, whatever their role, given those >> policies and procedures. > Complete agreement. I would, for the record, make much the same > suggestion about behavior in other situations that appeared to > push the boundaries of codes of professional ethics of the > professional societies of which many of us are members. Like > the IETF's IPR rules, those provisions are intended to be taken > seriously rather than as decoration that can be safely ignored. > The issue is an individual one, not an IETF one, and the current > issue is relevant only insofar as it should encourage all of us > --not just those involved in this document-- to take our various > personal and professional obligations seriously and to consider > the implications of circumstances in which various of them might > come into conflict. > > best, > john > > > > ------------------------------ > > Message: 2 > Date: Thu, 26 Jan 2012 10:40:20 -0700 > From: Peter Saint-Andre<stpeter@stpeter.im> > To: SM<sm@resistor.net> > Cc: Pete Resnick<presnick@qualcomm.com>, ietf@ietf.org > Subject: encouraging compliance with IPR disclosure rules > Message-ID:<4F219004.4070601@stpeter.im> > Content-Type: text/plain; charset=UTF-8 > > [ - sieve@ietf.org ] > > On 1/26/12 10:15 AM, SM wrote: >> Hi Pete, >> At 08:08 26-01-2012, Pete Resnick wrote: >>> As I've mentioned to others, since I'm one of the people who will have >>> to judge the consensus on this question, my comments will remain >>> strictly based on the facts of the events as I know them and on the >>> relevant IETF procedures. It is up to the IETF community >> The status of the memo in the drafts have this statement: >> >> "This Internet-Draft is submitted in full conformance with the >> provisions of BCP 78 and BCP 79." >> >> Have the authors been asked whether they have any issue with the above? >> >> The is a question in the write-up: "Has an IPR disclosure related to >> this document been filed?" Has the Document Shepherd been asked about >> that before the Second Last Call? >> >> The minutes from the last WG session does not mention who chaired the >> session. Did the WG Chair bring the Note Well to the attention of the WG? > In my opinion, we need to think more creatively about ways to encourage > compliance with the IPR disclosure rules. Tim Polk and I wrote an I-D on > the topic last year. Feedback would be welcome. > > http://tools.ietf.org/html/draft-polk-ipr-disclosure-00 > > Peter >
- unsubscribe Larry Holmstrom
- unsubscribe Larry Holmstrom
- unsubscribe Johnny Miguez
- unsubscribe thiagarajan.venkatachalam
- unsubscribe Vema Venkata
- Unsubscription How-To (Was: unsubscribe) Jeroen Massar
- unsubscribe alexandre.carvalho
- unsubscribe Thittai, Ranganathan N. [IE]
- unsubscribe wen.wu
- unsubscribe Deleep Srivatsa
- unsubscribe Suresh Kumar
- unsubscribe 高明军
- unsubscribe Vij, Bhavna
- unsubscribe Karnam, Swamy
- unsubscribe VADDARAHALLIRAMEGOWDA RAGHAVENDRA
- unsubscribe Daniel Maia
- unsubscribe ETATLRI
- Re: unsubscribe Vernon Schryver
- unsubscribe H. van den Eertwegh (SPC/c)
- Re: unsubscribe Thomas Narten
- unsubscribe Nitin Jain
- Re: unsubscribe John C Klensin
- Re: unsubscribe Ed Levinson
- unsubscribe Ashraf Madoukh - (913) 534-3137
- Re: unsubscribe (another nickel's worth) tracym
- unsubscribe Cerafin E. Castillo
- unsubscribe av0
- unsubscribe Carolyn M Jones
- unsubscribe Fraser Enterprise
- unsubscribe Sheldon Kopp
- Re: unsubscribe William Allen Simpson
- Re: unsubscribe Peter S. Ford
- unsubscribe Jorge Granjal
- unsubscribe AChen
- unsubscribe John V. Jaskolski
- unsubscribe rwmartin
- Re: unsubscribe C. Harald Koch
- unsubscribe MattMan
- unsubscribe Charles Sun
- unsubscribe Michael Strayer
- Re: unsubscribe Valdis.Kletnieks
- Re: unsubscribe Frank Kastenholz
- Re: unsubscribe ROBERT_GRAHAM
- Re: unsubscribe Terry Gray
- Re: unsubscribe Valdis.Kletnieks
- Re: unsubscribe Janet L. Marcisak - Sysmonster
- unsubscribe Borka Jerman-Blazic
- Re: unsubscribe Greg Skinner
- unsubscribe Minh VO
- unsubscribe RND Inc.
- unsubscribe R?mi POULET
- unsubscribe Maria Dimou-Zacharova
- unsubscribe henninge
- unsubscribe Tarak Parekh
- Re: unsubscribe Jim.Rees
- unsubscribe Derek Bennett
- unsubscribe Thomas L. Allen
- unsubscribe Bob Colvin
- unsubscribe Jim Culbert
- Re: unsubscribe Louis A. Mamakos
- unsubscribe Kenneth Weaver
- Re: unsubscribe Erik Naggum
- unsubscribe Bob Bosen
- Re: unsubscribe Geert Jan de Groot
- unsubscribe paul cheng
- unsubscribe H. van den Eertwegh (SPC/c)
- unsubscribe Borka Jerman-Blazic
- unsubscribe Masato Hirose
- unsubscribe bhavana nagendra
- Re: unsubscribe Eric Thomas
- unsubscribe T_ROWSELL
- Re: u n s u b s c r i b e Dave Crocker
- unsubscribe Jason Kuan
- unsubscribe James McNamara Jr.
- unsubscribe alex (a.d.) brown
- unsubscribe Jill Weber
- unsubscribe Brian Sheets
- unsubscribe Richard Armstrong
- unsubscribe David Fabian
- unsubscribe Fellowships
- unsubscribe Floyd Hall
- Re: unsubscribe Erik Naggum
- unsubscribe Nouriel Roubini
- RE: unsubscribe WJCarpenter
- unsubscribe Charles Benjamin
- Re: unsubscribe Frank T Solensky
- Re: unsubscribe Dave Crocker
- unsubscribe Alok Srivastava
- unsubscribe Fady Khalil
- Re: unsubscribe Noel Chiappa
- unsubscribe Mike Decker
- unsubscribe Samuli Valavuo
- unsubscribe Eric DELACOUR
- Re: unsubscribe Mark Towfiq
- unsubscribe Mitzi Carter
- unsubscribe Padmanabhan Srinagesh
- Re: unsubscribe Mike Brescia
- Re: unsubscribe Matt Crawford
- unsubscribe John Howe
- what to do about Re: unsubscribe Craig Partridge
- unsubscribe Dan Pederson
- Re: unsubscribe Dave Crocker
- unsubscribe Kim Gillett
- Re: unsubscribe Bob Braden
- unsubscribe Ryan Lee
- unsubscribe Tony Mazraani
- Re: unsubscribe Noel Chiappa
- unsubscribe ROBERT_GRAHAM
- unsubscribe james johansen
- Re: unsubscribe (another nickel's worth) Craig Metz
- unsubscribe simple
- Re: unsubscribe Barry M. Leiner
- unsubscribe Schliephake, Stephan