ietf-mta-filters
[Top] [All Lists]

RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard

2012-01-25 15:51:28
Please also see US patent 20090204681 visible at
http://ip.com/patapp/US20090204681 
 
In my opinion, this second last call should be suspended until this significant
breach of the IETF's IPR policy set out in BCP79 has been resolved.
 
While it is important to find out what the IETF community's view of this
situation is, there are two questions:
 
1. What does the WG think about the I-D being IPR encumbered and do they want to
develop an alternate solution that is not encumbered?
 
2. How will the IETF handle the breach of IPR policy?
 
I believe the document should be returned to the working group who are the main
victims of the disruptive behaviour by the author.
 
Thanks,
Adrian
 
From: ietf-bounces(_at_)ietf(_dot_)org 
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On Behalf Of Adam
Roach
Sent: 25 January 2012 21:36
To: ietf(_at_)ietf(_dot_)org
Cc: sieve(_at_)ietf(_dot_)org; The IESG; IETF-Announce
Subject: Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt>
(Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard
 
Just to make sure I understand the sequence of events:
1.      August 21, 2007: Huawei files a patent (CN 200710076523.4) on using SIP
for SIEVE notifications. The inventor is listed as a single Huawei employee.
2.      August 30, 2007: That same Huawei employee and two additional authors
publish an IETF draft ( draft-melnikov-sieve-notify-sip-message-00) on using SIP
for SIEVE notifications.
3.      September 2007 - September 2011: The SIEVE working group discusses and
improves the IETF draft.
4.      October 6, 2011: The IESG approves the IETF draft for publication as an
RFC.
5.      December 14th, 2011: Huawei files an IPR disclosure with the IETF
informing it of patent CN 200710076523.4

Is that correct? Am I leaving anything out?

/a


On 1/25/12 2:17 PM, The IESG wrote: 
 
The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Notification Mechanism: SIP MESSAGE'
  <draft-ietf-sieve-notify-sip-message-08.txt> as a Proposed Standard
 
Last calls were earlier issued on version -05 of this document and this
document was approved by the IESG on 2011-10-06. Subsequently,
an IPR disclosure statement for this draft was submitted.
This Second Last Call is intended to determine whether the community
is still comfortable with publication of this document in light of the IPR
statement.
The relevant IPR statement is available at:
 
https://datatracker.ietf.org/ipr/1658/
 
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2012-02-08. Exceptionally, comments 
may be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
 
Abstract
 
 
   This document describes a profile of the Sieve extension for
   notifications, to allow notifications to be sent over SIP MESSAGE.
 
 
 
 
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sieve-notify-sip-message/
 
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sieve-notify-sip-message/
 
 
The following IPR Declarations may be related to this I-D:
 
   http://datatracker.ietf.org/ipr/1658/
 
 
 
_______________________________________________
IETF-Announce mailing list
IETF-Announce(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-announce
 
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
<Prev in Thread] Current Thread [Next in Thread>