Chris Lonvick
Wed, 07 Jun 2006 12:06:42 -0700
Hi, RFC3979 is our guide here: http://www.ietf.org/rfc/rfc3979.txt
From Section 2 of that document:
===
RFC 2026, Section 10 established three basic principles regarding the
IETF dealing with claims of Intellectual Property Rights:
(a) the IETF will make no determination about the validity of any
particular IPR claim
(b) the IETF following normal processes can decide to use technology
for which IPR disclosures have been made if it decides that such
a use is warranted
(c) in order for the working group and the rest of the IETF to have
the information needed to make an informed decision about the use
of a particular technology, all those contributing to the working
group's discussions must disclose the existence of any IPR the
Contributor or other IETF participant believes Covers or may
ultimately Cover the technology under discussion. This applies
to both Contributors and other participants, and applies whether
they contribute in person, via email or by other means. The
requirement applies to all IPR of the participant, the
participant's employer, sponsor, or others represented by the
participants, that is reasonably and personally known to the
participant. No patent search is required.
===
As I see it (IANAL), we can decide to use the IPR, or not. For us to
proceed, we will need:
1) to hear what the claim is, and 2) to decide if the terms of use are acceptable. The latter is in the disclosure that David sent around.Section 6.4 of RFC 3979 give specifics about what must be disclosed. I'll ask Miao and Yuhzi to give us what specifics they can at this time - can you update the disclosure notice to include what section of draft-ietf-syslog-transport-tls-01.txt contains the claimed IPR according to RFC 3979 Section 6.4.1.
While we're waiting for that, I'll ask for people to look over the licensing terms and provide feedback to the list about its acceptability.
Thanks, Chris On Wed, 7 Jun 2006, Balazs Scheidler wrote:
On Wed, 2006-06-07 at 13:25 -0400, David B Harrington wrote:Hi, As co-chair it is my responsibility to make the WG aware that there has been a disclosure that an unpublished pending patent application might be infringed by the implementation of the specifications in draft-ietf-syslog-transport-tls-01.txt. The disclosure can be found at https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=717. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] co-chair, Syslog WGThis is insane. I just tried google to search for syslog-ng and stunnel, I got 89000 result pages, the contents most probably describing how to combine syslog-ng and TLS, e.g. transfer syslog messages on a TLS encrypted channel I would call that prior art, although the details of the patent is to be seen, but I am not happy. I might even choose not to interoperate with the protocol specified here with syslog-ng. Puzzled. -- Bazsi _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
_______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog