[sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message

Pete Resnick <presnick@qualcomm.com> Thu, 15 December 2011 21:29 UTC

Message-ID: <4EEA65E9.2050802@qualcomm.com>
Date: Thu, 15 Dec 2011 15:26:01 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: SIEVE <sieve@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
Precedence: list

Folks,

As you have seen by now, the IETF has received 2 IPR disclosures, one 
regarding draft-ietf-sieve-convert and the other involving 
draft-ietf-sieve-notify-sip-message.

https://datatracker.ietf.org/ipr/1657/
https://datatracker.ietf.org/ipr/1658/


Unfortunately, we have been told that Qian Sun, one of the co-authors of 
the document, is the author of the patent in question, filed back in 
2008, and that he failed to disclose this at the time. I think this was 
pretty clearly a violation of RFC 3979, and the IESG will take up the 
question of what, if any, appropriate measures need to be taken because 
of that. Qian Sun is apparently no longer an active IETF participant, 
and his co-workers who are active IETF participants asked their company 
to disclose against the two documents as soon as they discovered what 
had happened. That's where were are now.

However, I did want to bring this to the attention of the working group 
and ask about the following:

Both of these drafts are already approved and in the RFC Editor queue. 
Right now, the RFC Editor has been asked to hold off publication for the 
moment until we decide the next steps. We could treat the IPR 
disclosures just as we would for any already published RFC (that is, we 
can simply say that it is out of our hands). However, since publication 
has not occurred, we can ask the RFC Editor to return the documents to 
the WG for further review, which as far as I can tell the RFC Editor 
always agrees to do. So, I ask that you all review the disclosures and 
ask the following question to the group:

After having reviewed the disclosures, does anyone in the WG wish to 
discuss the impact of these disclosures on the decision to publish these 
documents as they are? If so, I will likely ask the chairs to run a WGLC 
on the documents, and then I will run a new IETF Last Call with a 
pointer to the IPR disclosures. On the other hand, if there is *strong* 
consensus now on the list that it is fine go forward as-is, I will 
consider the matter settled and tell the RFC Editor to continue processing.

Please let us know what you think.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

[sieve] IPR Disclosures on draft-ietf-sieve-inclu… Pete Resnick
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Barry Leiba
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Alexey Melnikov
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Alexey Melnikov
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Arnt Gulbrandsen
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Arnt Gulbrandsen
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Cyrus Daboo
Re: [sieve] IPR Disclosures on draft-ietf-sieve-i… Aaron Stone