Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
Alexey Melnikov <alexey.melnikov@isode.com> Sat, 28 January 2012 14:15 UTC
Return-Path: <alexey.melnikov@isode.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 011FA21F855B for <ietf@ietfa.amsl.com>; Sat, 28 Jan 2012 06:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 kInd-w06wWmz for <ietf@ietfa.amsl.com>; Sat, 28 Jan 2012 06:15:51 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 90F4021F8503 for <ietf@ietf.org>; Sat, 28 Jan 2012 06:15:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1327760149; d=isode.com; s=selector; i=@isode.com; bh=XfOXnyRpbN3tlt+Kj0Dlh28YZ9WuzlXwDhvBuZdHyt8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Nlrkyvpr0G+OpltPrS6rg8Adh3nXBhUZlYaXgQARZT+bY/y5HnuPCYGSmCvml2S14cxjM+ ZxH1563rkPVRsBSLeJ3PuTC9Zv3SlqDpjOrYWa1EfdDnfI4RdQJazAu8jOcN4Gg0VKwXKz KABDPHKYTBWLX9QM9U8A3CSQ1wu2GRU=;
Received: from [188.29.1.112] (188.29.1.112.threembb.co.uk [188.29.1.112]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <TyQDEQAV54LJ@rufus.isode.com>; Sat, 28 Jan 2012 14:15:47 +0000
Message-ID: <4F23FFAA.8050707@isode.com>
Date: Sat, 28 Jan 2012 14:01:15 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
References: <20120125201714.3903.82295.idtracker@ietfa.amsl.com> <4F2075BE.5070201@nostrum.com> <033901ccdbab$6bae0900$430a1b00$@olddog.co.uk> <CD5674C3CD99574EBA7432465FC13C1B226F573BC9@DC-US1MBEX4.global.avaya.com> <4F208AEF.5060406@qualcomm.com> <CD5674C3CD99574EBA7432465FC13C1B226F573BCE@DC-US1MBEX4.global.avaya.com> <4F21ABF2.7040002@qualcomm.com> <6842.1327617385@marajade.sandelman.ca> <F5833273385BB34F99288B3648C4F06F19C9A7D9F5@EXCH-C2.corp.cloudmark.com> <CAC4RtVBfe5G=eEotH3gceVCm9grc7qxCT1siykbF+cHeNdArxA@mail.gmail.com>
In-Reply-To: <CAC4RtVBfe5G=eEotH3gceVCm9grc7qxCT1siykbF+cHeNdArxA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <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: Sat, 28 Jan 2012 14:15:52 -0000
On 27/01/2012 01:50, Barry Leiba wrote: [...] > On Thu, Jan 26, 2012 at 12:37 PM, John C Klensin <john-ietf@jck.com> > wrote:>> 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). > That is, indeed the situation. Qian Sun, the original Huawei author, > got a new assignment in the company, and stopped participating in the > IETF a few years ago, after he and Alexey had started the documents. > I can't speak for him about why he didn't understand the disclosure > rules; as I understand it, he seems to have thought the patents didn't > need to be disclosed until the RFC was published. I just want to add that I was not aware of the fact that Qian Sun has filed patent applications, he didn't tell me. (Not that it makes much difference, but in the interest of historical accuracy: In one case I started the draft by myself and Qian Sun offered to help with finishing it. In another case Qian Sun wrote a draft based on text from my other RFC and was bugging me to help out.) >> 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. > Some time last year, Kepeng and I offered to work with Alexey to > finish the two docs, which had seen slow progress for some while. > Only when the documents were approved and in the RFC Editor queue did > Kepeng learn about Qian's patent applications. He immediately alerted > me. I asked the RFC Editor to stop publication (one was in AUTH48 at > the time), and alerted Pete Resnick and the Sieve chairs. Kepeng > pushed Huawei's IP law department to expedite the disclosure, which > they turned around in two days for us. I assure all of you that > Kepeng and I were blindsided by this. I obviously believe you :-). As much as I hate the whole situation, I am glad that this happened before the document got published as an RFC, not after. >> 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. > Unlikely in this case, yes. I leave it to you whether you trust what > I say, but I can only repeat that we did not know, and acted very > quickly when we found out.
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Adam Roach
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Adrian Farrel
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Peter Saint-Andre
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Thomas Nadeau
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Worley, Dale R (Dale)
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Peter Saint-Andre
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Adam Roach
- Violation of IETF process (was: Second Last Call:… SM
- RE: Violation of IETF process (was: Second Last C… Adrian Farrel
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Dave CROCKER
- RE: Violation of IETF process (was: Second Last C… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Dave Cridland
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Harald Alvestrand
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Bob Hinden
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- RE: Violation of IETF process (was: Second Last C… Murray S. Kucherawy
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… John C Klensin
- encouraging compliance with IPR disclosure rules Peter Saint-Andre
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Worley, Dale R (Dale)
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: encouraging compliance with IPR disclosure ru… SM
- Re: Violation of IETF process todd glassey
- Re: Second Last Call: <draft-ietf-sieve-notify-si… todd glassey
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Kevin P. Fleming
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Martin Rex
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Cyrus Daboo
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Cyrus Daboo
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Michael Richardson
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Hector
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Pete Resnick
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Barry Leiba
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Ted Hardie
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Steven Bellovin
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Barry Leiba
- Re: Second Last Call: <draft-ietf-sieve-notify-si… SM
- RE: Second Last Call: <draft-ietf-sieve-notify-si… Murray S. Kucherawy
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Hector Santos
- Re: Second Last Call: <draft-ietf-sieve-notify-si… t.petch
- Re: [sieve] Second Last Call: <draft-ietf-sieve-n… Arnt Gulbrandsen
- Re: encouraging compliance with IPR disclosure ru… Polk, William T.
- Re: encouraging compliance with IPR disclosure ru… Scott Brim
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Dave CROCKER
- Re: Second Last Call: <draft-ietf-sieve-notify-si… Alexey Melnikov
- Re: encouraging compliance with IPR disclosure ru… todd glassey