![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Reply below. /Larry > -----Original Message----- > From: John C Klensin [mailto:john-ietf at jck.com] > Sent: Wednesday, December 17, 2008 7:02 PM > To: lrosen at rosenlaw.com; 'IETF discussion list' > Subject: RE: IPR Questions Raised by Sam Hartman at the IETF 73 Plenary > > > > --On Wednesday, 17 December, 2008 16:56 -0800 Lawrence Rosen > <lrosen at rosenlaw.com> wrote: > > > Dave Crocker wrote: > >> That was the culture. Law often > >> follows culture, since culture creates established practice. > > > > I hope you're right. > > > > May I ask: Is there anyone on this list who is asserting a > > current copyright interest in any IETF RFC--on your own behalfFrom ietf-bounces at ietf.org Wed Dec 17 20:31:00 2008 Return-Path: <ietf-bounces at ietf.org> X-Original-To: ietf-archive at megatron.ietf.org Delivered-To: ietfarch-ietf-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C7C83A67DB; Wed, 17 Dec 2008 20:31:00 -0800 (PST) X-Original-To: ietf at core3.amsl.com Delivered-To: ietf at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41F343A65A5 for <ietf at core3.amsl.com>; Wed, 17 Dec 2008 20:30:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IM4PEjG7qreN for <ietf at core3.amsl.com>; Wed, 17 Dec 2008 20:30:57 -0800 (PST) Received: from rosenlaw.com (rosenlaw.com [192.220.47.202]) by core3.amsl.com (Postfix) with ESMTP id E543C3A67DB for <ietf at ietf.org>; Wed, 17 Dec 2008 20:30:56 -0800 (PST) Received: (qmail 40690 invoked by uid 12234); 18 Dec 2008 04:30:47 -0000 Received: from unknown (HELO LROSENTOSHIBA) ([208.106.45.202]) (envelope-sender <lrosen at rosenlaw.com>) by 192.220.47.202 (qmail-ldap-1.03) with SMTP for <ietf at ietf.org>; 18 Dec 2008 04:30:47 -0000 From: "Lawrence Rosen" <lrosen at rosenlaw.com> To: "'IETF discussion list'" <ietf at ietf.org> References: <20081211224832.C04F33A69BD at core3.amsl.com> <87zlj1zn0n.fsf at mocca.josefsson.org> <ED38349F-47E1-4A16-866C-7E408FE151E1 at multicasttech.com> <DE1EBB80D3F89D4427307614 at p3.int.jck.com> <87fxktxn7f.fsf at mocca.josefsson.org> <07892C8A-21AB-4C0D-98FF-2A8C92D450FB at multicasttech.com> <20081212201956.0CA2128C207 at core3.amsl.com> <8D78B6C7-DA00-482F-B318-B928B62DCF9F at cisco.com> <4947F2D4.5060406 at dcrocker.net> <7396A71EA64DE20F60756396 at p3.int.jck.com> <49486D3B.40808 at joelhalpern.com> <AFB3458AFCDF426E12A02B79 at p3.int.jck.com> <852DD6B9-0D81-4D97-BC79-3308B20E6E9F at multicasttech.com> <2F59A9909280D69202B4FB3D at p3.int.jck.com> <49496996.1020406 at dcrocker.net> <8573A0D1A0E693C778E62BA3 at p3.int.jck.com> <49497E10.9040809 at dcrocker.net><49498319.3070005 at gmail.com> <49498C83.3080902 at dcrocker.net> <EDC116E9DFB64EA58A38B0B84BADC061 at LROSENTOSHIBA> <D3537067AB32F1558440D752 at p3.int.jck.com> Subject: RE: IPR Questions Raised by Sam Hartman at the IETF 73 Plenary Date: Wed, 17 Dec 2008 20:29:52 -0800 Organization: Rosenlaw & Einschlag Message-ID: <A2C596B3F37A4D7BAC32036D0D78883A at LROSENTOSHIBA> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <D3537067AB32F1558440D752 at p3.int.jck.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AclgvQ2Z7uhsHlXGTbKOcRM67JUWzQAB88IA X-BeenThere: ietf at ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: lrosen at rosenlaw.com List-Id: IETF-Discussion <ietf.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=unsubscribe> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-bounces at ietf.org Errors-To: ietf-bounces at ietf.org Reply below. /Larry > -----Original Message----- > From: John C Klensin [mailto:john-ietf at jck.com] > Sent: Wednesday, December 17, 2008 7:02 PM > To: lrosen at rosenlaw.com; 'IETF discussion list' > Subject: RE: IPR Questions Raised by Sam Hartman at the IETF 73 Plenary > > > > --On Wednesday, 17 December, 2008 16:56 -0800 Lawrence Rosen > <lrosen at rosenlaw.com> wrote: > > > Dave Crocker wrote: > >> That was the culture. Law often > >> follows culture, since culture creates established practice. > > > > I hope you're right. > > > > May I ask: Is there anyone on this list who is asserting a > > current copyright interest in any IETF RFC--on your own behalf > > or > > or on behalf of your company--that would encumber the freedom > > of any IETF participants to copy, create derivative works, and > > distribute that RFC in accordance with IETF culture? > >... > > Larry, > > So that we don't get assertions about either universal negatives > or about people who are assumed to give up the right to claim > copyright interest as a consequence of not answering your > question,... [LR:] Universal negatives? I remember at least one email here yesterday or today where someone cavalierly stated that he claimed a copyright in an unnamed IETF spec. I wanted to flesh that claim out. Perhaps that person will have the courage to speak up precisely. That's the problem around here. People worry to death about IP claims that nobody is willing to actually make. People develop IP policies that solve nonexistent problems (such as the "code" vs. "text" debate) and, by doing so, add further confusion, evidenced by this current problem. I refuse to be cowed by ambiguous claims of IP, particularly copyrights that seek to inhibit the development of *functional* industry standards. It is even worse than ambiguously claiming that "there might be patented technology here" but then refusing to identify or license it, because copyright lasts for 100 years, not just 20. I can outwait the patent IP claims, but technology will be hostage for my entire lifetime to the copyrights. That can't be justified. > Your question does not distinguish between uses by IETF > participants for IETF-related purposes (e.g., standards > development) and uses by people who participate in the IETF for > purposes not directly related to IETF work (e.g., insertion into > programs or their documentation whether conforming to those > standards or not). Was the failure to make that distinction > intentional? [LR:] Yes. Both are absolutely essential for implementation of open standards. > If it was intentional, is your question intended as a back-door > way to reopen the questions about whether the IETF intends > unlimited use of its material, with or without acknowledgements > and citation and regardless of purpose, that the IPR WG resolved > in the negative? [LR:] Yes, since the front door has been closed. My question is definitely: Is anyone retaining a copyright in such functional materials with the intent to prevent unlimited use by *anyone*? Please don't assert that this need be "without acknowledgements and citation." I've never said that. As for "regardless of purpose," as long as the purpose is to obtain a specific standard functionality and thus the words are not subject to copyright, try and stop me, regardless of what the IPR WG says. > Finally, when you ask this question, are you asking as an > individual participant in the IETF process or as an attorney who > might be called upon to advise one or more clients on the > subject of dealing with the IETF and/or IETF-related IPR? If > the latter, would you mind identifying those clients and any > other interest you might have in the answers other than idle > curiousity? [LR:] I am asking as an attorney and IETF participant (we're all individuals here, I've been told, with individual opinions) who is anxious to understand why so many people on here are worried about copyright infringement and are seeking to protect copyrights they don't even have the honesty to claim outright. I care about IETF specifications in this email thread, not about any specific clients. As to whether I might represent one or more clients on this issue, my lips are sealed. > thanks, > john > > p.s. Even if it were clearly true at one time, which some would > dispute, Dave's assertion about the present IETF culture is > controversial given, at least, the IETF's history and positions > about IPR and copyright over the last decade or more. [LR:] So if the "culture" is controversial, and the "process" we've inadequately developed is controversial, perhaps we should actually consider the law. Which is what I'm trying to do. Unfortunately what people are doing here is speculating abouton behalf of your company--that would encumber the freedom > > of any IETF participants to copy, create derivative works, and > > distribute that RFC in accordance with IETF culture? > >... > > Larry, > > So that we don't get assertions about either universal negatives > or about people who are assumed to give up the right to claim > copyright interest as a consequence of not answering your > question,... [LR:] Universal negatives? I remember at least one email here yesterday or today where someone cavalierly stated that he claimed a copyright in an unnamed IETF spec. I wanted to flesh that claim out. Perhaps that person will have the courage to speak up precisely. That's the problem around here. People worry to death about IP claims that nobody is willing to actually make. People develop IP policies that solve nonexistent problems (such as the "code" vs. "text" debate) and, by doing so, add further confusion, evidenced by this current problem. I refuse to be cowed by ambiguous claims of IP, particularly copyrights that seek to inhibit the development of *functional* industry standards. It is even worse than ambiguously claiming that "there might be patented technology here" but then refusing to identify or license it, because copyright lasts for 100 years, not just 20. I can outwait the patent IP claims, but technology will be hostage for my entire lifetime to the copyrights. That can't be justified. > Your question does not distinguish between uses by IETF > participants for IETF-related purposes (e.g., standards > development) and uses by people who participate in the IETF for > purposes not directly related to IETF work (e.g., insertion into > programs or their documentation whether conforming to those > standards or not). Was the failure to make that distinction > intentional? [LR:] Yes. Both are absolutely essential for implementation of open standards. > If it was intentional, is your question intended as a back-door > way to reopen the questions about whether the IETF intends > unlimited use of its material, with or without acknowledgements > and citation and regardless of purpose, that the IPR WG resolved > in the negative? [LR:] Yes, since the front door has been closed. My question is definitely: Is anyone retaining a copyright in such functional materials with the intent to prevent unlimited use by *anyone*? Please don't assert that this need be "without acknowledgements and citation." I've never said that. As for "regardless of purpose," as long as the purpose is to obtain a specific standard functionality and thus the words are not subject to copyright, try and stop me, regardless of what the IPR WG says. > Finally, when you ask this question, are you asking as an > individual participant in the IETF process or as an attorney who > might be called upon to advise one or more clients on the > subject of dealing with the IETF and/or IETF-related IPR? If > the latter, would you mind identifying those clients and any > other interest you might have in the answers other than idle > curiousity? [LR:] I am asking as an attorney and IETF participant (we're all individuals here, I've been told, with individual opinions) who is anxious to understand why so many people on here are worried about copyright infringement and are seeking to protect copyrights they don't even have the honesty to claim outright. I care about IETF specifications in this email thread, not about any specific clients. As to whether I might represent one or more clients on this issue, my lips are sealed. > thanks, > john > > p.s. Even if it were clearly true at one time, which some would > dispute, Dave's assertion about the present IETF culture is > controversial given, at least, the IETF's history and positions > about IPR and copyright over the last decade or more. [LR:] So if the "culture" is controversial, and the "process" we've inadequately developed is controversial, perhaps we should actually consider the law. Which is what I'm trying to do. Unfortunately what people are doing here is speculating about hypothetical situations and refusing to declare their real interests in promoting restricted copyright licenses for functional specifications. _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf hypothetical situations and refusing to declare their real interests in promoting restricted copyright licenses for functional specifications. _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.