Re: Late IPR disclosure on RFC7024 - Opinions ?

Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Thu, 23 October 2014 21:56 UTC

Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF641A6EED; Thu, 23 Oct 2014 14:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k0xR4kyraURa; Thu, 23 Oct 2014 14:56:50 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18E61A1AF2; Thu, 23 Oct 2014 14:56:49 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id EC5662D9E5BD1; Thu, 23 Oct 2014 21:56:43 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9NLulkK008373 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Oct 2014 23:56:47 +0200
Received: from [135.244.192.133] (135.239.27.41) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 23 Oct 2014 23:56:46 +0200
Message-ID: <54497999.8050500@alcatel-lucent.com>
Date: Thu, 23 Oct 2014 23:56:41 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Benson Schliesser <bensons@queuefull.net>
Subject: Re: Late IPR disclosure on RFC7024 - Opinions ?
References: <544404B6.4060605@alcatel-lucent.com> <5449476C.1080307@queuefull.net>
In-Reply-To: <5449476C.1080307@queuefull.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [135.239.27.41]
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/nFUW0Pb-7r8GSrJh01NwK-QaM70
Cc: l3vpn@ietf.org, bess@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn/>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 21:56:52 -0000

Hi Benson,

I would say that 1 to 4 are valid options, but it shall be the WG 
deciding the way forward.

Also, as Chairs, we can think of a variety of punitive responses, 
speaking in the general case, but these shall only concern individuals.

-m

Le 23/10/2014 20:22, Benson Schliesser a écrit :
> Hi, Martin -
>
> Just to be clear, can you elaborate on what you see as the options here?
>
> I could imagine some combination of choices: 1) keeping the status quo,
> acknowledging that the new IPR has been disclosed, and continuing to
> proceed with the document as-is, 2) changing status to something other
> than Proposed Standard, 3) revising the content (e.g. as a new RFC?) to
> avoid IPR issues that are objectionable, or 4) evaluating alternatives.
>
> Are you also aware of any options for a punitive response? I'm not sure
> whether this would be against the inventors, company that owns the IPR,
> employees of that company that should have known about the IPR, etc. I'm
> also not sure what this punitive response would actually be. BCP 79
> doesn't seem to outline anything in this direction. But it seems clear
> to me that the recent trends in late IPR disclosure are a problem for
> the IETF.
>
> Thanks for any feedback you can give.
> -Benson
>
>
>> Martin Vigoureux <mailto:martin.vigoureux@alcatel-lucent.com>
>> October 19, 2014 at 2:36 PM
>> Working Group,
>>
>> we've received couple months ago an extremely late IPR disclosure
>> (much later than what can be expected as per rules in BCP79) against
>> RFC 7024:
>>
>> https://datatracker.ietf.org/ipr/2415/
>>
>> Please take a careful look at the licensing declaration and let us
>> know whether this is subject to question RFC 7024 (both in its content
>> and/or status).
>>
>> Thank you
>>
>> M&T
>>