From mailman-admin@ietf.org Tue Apr 1 10:17:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18987 for ; Tue, 1 Apr 2003 10:17:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31FfhK02629 for ; Tue, 1 Apr 2003 10:41:43 -0500 Date: Tue, 01 Apr 2003 10:41:43 -0500 Message-ID: <20030401154143.29326.66859.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: pilc-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, pilc-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for pilc-archive@lists.ietf.org: List Password // URL ---- -------- pilc@ietf.org HsCZ https://www1.ietf.org/mailman/options/pilc/pilc-archive%40lists.ietf.org From mailnull@www1.ietf.org Thu Apr 3 08:28:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19238 for ; Thu, 3 Apr 2003 08:28:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h33DUQB13428 for pilc-archive@odin.ietf.org; Thu, 3 Apr 2003 08:30:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h33DUQK13425 for ; Thu, 3 Apr 2003 08:30:26 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19228 for ; Thu, 3 Apr 2003 08:27:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h33DN9K13060; Thu, 3 Apr 2003 08:23:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h33DLxK13013 for ; Thu, 3 Apr 2003 08:21:59 -0500 Received: from web10905.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18901 for ; Thu, 3 Apr 2003 08:19:11 -0500 (EST) Message-ID: <20030403132139.32737.qmail@web10905.mail.yahoo.com> Received: from [12.237.229.250] by web10905.mail.yahoo.com via HTTP; Thu, 03 Apr 2003 05:21:39 PST Date: Thu, 3 Apr 2003 05:21:39 -0800 (PST) From: Spencer Dawkins To: ietf-secretariat@ietf.org Cc: Jon Peterson , Allison Mankin , Aaron Falk , pilc@ietf.org, Scott Bradner MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [pilc] Fwd: Connection splitting patent relevant to PILC community Sender: pilc-admin@ietf.org Errors-To: pilc-admin@ietf.org X-BeenThere: pilc@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Performance Implications of Link Characteristics IETF Working Group List-Post: List-Help: List-Subscribe: , Dear IETF Secretariat, Aaron Falk and I are co-chairs of the PILC working group. We were notified this week by Emmanuel Duros of a notice claiming patent infringement that Emmanuel passed along to us. Scott Bradner says we are encouraged (not required) to notify the IETF of this claim, so, here's what we know, so far. Title: "Data transmission on client-server system using TCP/IP" No. Publication: DE19910023 Date of publication: 2000-09-14 Date of recording/priority: 1999-03-08 Inventors: Kellerer Wolfgang, Zurek-Terhardt Guenther, Sties Peter Company: Rodhe and Schwarz Patent granted in: Germany Brief summary: This patent covers the "dividing" of one connection into two connections to accommodate a low bandwidth path. PILC produced BCP and Informational specifications, including RFC 3135 "Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations" (J. Border, M. Kojo, J. Griner, G. Montenegro, Z. Shelby, June 2001, Informational, ftp://ftp.rfc-editor.org/in-notes/rfc3135.txt). RFC 3135 describes "split connections" in section 2.4, and discusses implications of PEP use, including connection splitting, in section 4.1. Although it's an Informational RFC, not a standards-track document, there's apparently some overlap between what's being described in the RFC and what's claimed by the patent holders. Emmanuel's contact information is included as an attachment. He has indicated a willingness to provide scans (in German) and translations (to English) to the IESG Secretariat, if this is helpful to the IETF community. We have copied the PILC mailing list on this e-mail for their information (but not for their discussion of patent validity on the mailing list!). Spencer, for Spencer and Aaron --- Emmanuel Duros wrote: > Subject: Connection splitting patent ?? > From: Emmanuel Duros > To: spencer_dawkins@yahoo.com, falk@isi.edu, > mallman@grc.nasa.gov > Date: 31 Mar 2003 11:38:11 +0200 > > Dear All, > > A few days ago my company received a patent infrigement from a > german > company called Rodhe & Schwarz. > > This company claims to have a patent for what we call at IETF > "connection splitting". > > The patent describes an architecture with a link that has some > specific > characteristics such as a satellite link. This link is then > surrounded > by 2 equipements that split, for obvious reasons, in 3 > connections an > end-to-end TCP connections... [ deleted down to ] > Emmanuel > -- > Emmanuel Duros http://www.udcast.com > 2455 Route des Dolines BP355 | Tel : +33 (0)4 93 00 16 60 > 06906 Sophia Antipolis France | Fax : +33 (0)4 93 00 16 61 > ** Full IP over Broadcast Media ** _______________________________________________ pilc mailing list pilc@ietf.org https://www1.ietf.org/mailman/listinfo/pilc http://www.ietf.org/html.charters/pilc-charter.html http://pilc.grc.nasa.gov/