Re: Status of a disclosure when technology is removed from a draft?
tsg <tglassey@earthlink.net> Fri, 26 April 2013 19:50 UTC
Return-Path: <tglassey@earthlink.net>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8196F21F9954 for <ipr-wg@ietfa.amsl.com>; Fri, 26 Apr 2013 12:50:20 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPg9IDADMpbf for <ipr-wg@ietfa.amsl.com>; Fri, 26 Apr 2013 12:50:20 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5638321F9909 for <ipr-wg@ietf.org>; Fri, 26 Apr 2013 12:50:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=JNWFv4X6vTVzVbpvnY2CG8bhM7DbkNeXDSe6Lk68bIz1sJEXiLl+iivVydq8rii4; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.1.101]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1UVoew-000387-KC for ipr-wg@ietf.org; Fri, 26 Apr 2013 15:50:18 -0400
Message-ID: <517ADA79.8080307@earthlink.net>
Date: Fri, 26 Apr 2013 12:50:17 -0700
From: tsg <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ipr-wg@ietf.org
Subject: Re: Status of a disclosure when technology is removed from a draft?
References: <517AD92C.6070400@gmail.com>
In-Reply-To: <517AD92C.6070400@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79a807dfc1bed60f83e0b023463d15d184350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipr-wg>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 19:50:20 -0000
Brian - the IETF published with a permanent and non revokable license to use the first IP publication. Now that it has a piece of objectionable IPR in it - its too late. The cat is already out of the bag and based on the license there is an issue. todd On 04/26/2013 12:44 PM, Brian E Carpenter wrote: > Hi, > > A case has just occurred of the following sequence: > > 1. A draft is posted that contains an algorithm; > 2. A corresponding IPR disclosure is posted; > 3. After WG discussion, the draft is updated with the algorithm removed. > > What next? The IPR disclosure is still there. Normally, we assume > that the disclosure remains relevant to following versions of the > draft without being re-posted each time. (In fact, do we even expect > a repeat disclosure for the eventual RFC? I don't think so.) > > Is there a need for a formal rule for this case? > > And what should the IPR holder do now? If they do nothing, the > updated draft might be assumed to be encumbered. > > (FYI the draft is draft-krishnan-opsawg-large-flow-load-balancing > and the disclosure is https://datatracker.ietf.org/ipr/2060/ .) > > Brian > _______________________________________________ > Ipr-wg mailing list > Ipr-wg@ietf.org > https://www.ietf.org/mailman/listinfo/ipr-wg >
- Status of a disclosure when technology is removed… Brian E Carpenter
- Re: Status of a disclosure when technology is rem… tsg
- Re: Status of a disclosure when technology is rem… GTW
- Re: Status of a disclosure when technology is rem… Brian E Carpenter
- Re: Status of a disclosure when technology is rem… Scott Brim
- Re: Status of a disclosure when technology is rem… Carsten Bormann
- Re: Status of a disclosure when technology is rem… tsg
- Re: Status of a disclosure when technology is rem… Brian E Carpenter
- Re: Status of a disclosure when technology is rem… Scott Brim
- Re: Status of a disclosure when technology is rem… Brian E Carpenter
- RE: Status of a disclosure when technology is rem… Black, David
- Re: Status of a disclosure when technology is rem… tsg
- Re: Status of a disclosure when technology is rem… tsg