Re: Late IPR disclosure on RFC7024 - Opinions ?

Robert Raszuk <robert@raszuk.net> Thu, 23 October 2014 19:22 UTC

Return-Path: <rraszuk@gmail.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 012BF1ACEA3; Thu, 23 Oct 2014 12:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 bM9WZFR1CkIq; Thu, 23 Oct 2014 12:22:36 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BE2C1ACEA2; Thu, 23 Oct 2014 12:22:36 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id rl12so1548550iec.23 for <multiple recipients>; Thu, 23 Oct 2014 12:22:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AUeJGNZKH6+WjgWoZmL8cREOX5Jqz2x+jxnAy3tpcuY=; b=z6gXwrg4icqSmZ1bA/vR6rRbdwfItWw34v0ggzc4VgNmto/CnP8v3cU1mGP6up0rcZ 8t+b5qDtgIM6TBBTNOqRdkPOsaFH+lfyD8rCwSvpuv03olDj4wJOGK7O5FgCghfEKhu4 t9vkScrJASH2BpXV1zLeLCF4vLUcD1ifnGVtOGDChaC+3TAhPokAbdlHi8RZT5NpSIBZ us221sgEx80viNJ6xbTQtLLnWFUliv4SDfF9I+mUkWJN42wy/JSh2qijXV2KsqCSoKPM s5wa2szwYiNInBFDr/EvvDvKSF7IZ20U25pf+n7LIeJ6qVV9OL3f2qfe6Ojk+wj19l/l hyzg==
MIME-Version: 1.0
X-Received: by 10.107.160.200 with SMTP id j191mr3822940ioe.75.1414092155389; Thu, 23 Oct 2014 12:22:35 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.107.156.208 with HTTP; Thu, 23 Oct 2014 12:22:35 -0700 (PDT)
In-Reply-To: <5449476C.1080307@queuefull.net>
References: <544404B6.4060605@alcatel-lucent.com> <5449476C.1080307@queuefull.net>
Date: Thu, 23 Oct 2014 21:22:35 +0200
X-Google-Sender-Auth: DGBvDjK3xCera46WlYqz29BeZas
Message-ID: <CA+b+ER=WENsHrD8hFmoceVUd3qDNSBXE13xPCoEijtwzhJ9c8Q@mail.gmail.com>
Subject: Re: Late IPR disclosure on RFC7024 - Opinions ?
From: Robert Raszuk <robert@raszuk.net>
To: Benson Schliesser <bensons@queuefull.net>
Content-Type: multipart/related; boundary="001a1140ec129a235805061bfcc9"
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/gC65obL8KIOJIFmGYxE28r9Q8j4
Cc: "bess@ietf.org" <bess@ietf.org>, L3VPN <l3vpn@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 19:22:38 -0000

Looking at this I am not sure what the problem is ?

If I am not mistaken none of the RFC7024 authors are associated with the
IPR disclosure neither are even listed in the ack section.

Chairs normally ask only authors for IPR statement.

Anyone can patent anything and this is even patent outside of US.

In any case to see the details one should examine what exactly has been
patented in 2003. Quick patent search around 2003 with the same authors
reveals a few patents for "hub-and-spoke for virtual private networks".

But let's observe that the above is technically slightly different then
"virtual hub and spoke idea" which perhaps some legal skilled folks may not
be able to easily grasp ;-)

Best,
r.


On Thu, Oct 23, 2014 at 8:22 PM, Benson Schliesser <bensons@queuefull.net>
wrote:

> 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 <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
>
>