Re: Late IPR disclosure on RFC7024 - Opinions ?

Benson Schliesser <bensons@queuefull.net> Fri, 24 October 2014 01:26 UTC

Return-Path: <bensons@queuefull.net>
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 B46D01AD62A for <l3vpn@ietfa.amsl.com>; Thu, 23 Oct 2014 18:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
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 YsHg0vp0c6AF for <l3vpn@ietfa.amsl.com>; Thu, 23 Oct 2014 18:26:15 -0700 (PDT)
Received: from mail-yh0-f42.google.com (mail-yh0-f42.google.com [209.85.213.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8B801AD5B9 for <l3vpn@ietf.org>; Thu, 23 Oct 2014 18:26:14 -0700 (PDT)
Received: by mail-yh0-f42.google.com with SMTP id t59so1739821yho.15 for <l3vpn@ietf.org>; Thu, 23 Oct 2014 18:26:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=sCKpq/7/TsGKG2X54VPJjA6EVgwjHWnDEHIrjdlgosA=; b=diVFymCj5I+szYoanatWbR1nEw+4pCgDoA8kDxtfHu5spl04yWOI1hFpySmgXunkkJ 6TA7+LqrxNaNSQ4e7aLySpr8DK+wJghLWilS01GMZ6GW8UN7RahsxSATmsappPQxTnVo BFZ2KrSBcZQGd3qGuo5hnnbf9JIm2Ilgjo6sq3lE8+aINJfNPpILPmbVbYpK0kIwP6nn Zedq1tWGIqVU5LY5nDMWpGaDgDVzEnkC3QfThLVL9960CPgyfUOni1K25wRjRhygMUsa qL129DI/j0sq3UlHc1LTOebZ2k7acT/8af79d2M/9IPaTiG0RIuGsM6Wg+WMNBDIUlok mkwg==
X-Gm-Message-State: ALoCoQlX9QXoN09BVuq0RqiHbFl3NG+KVxKjToMBV2AG+ykKMd7HK9mhhRXSZKTNYXE71UOy6OKW
X-Received: by 10.170.94.5 with SMTP id l5mr1263386yka.111.1414113974128; Thu, 23 Oct 2014 18:26:14 -0700 (PDT)
Received: from wasteland-6.local (67.20.138.103.dyn-e120.pool.hargray.net. [67.20.138.103]) by mx.google.com with ESMTPSA id k35sm2934544qge.42.2014.10.23.18.26.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Oct 2014 18:26:13 -0700 (PDT)
Message-ID: <5449AAB3.2000105@queuefull.net>
Date: Thu, 23 Oct 2014 21:26:11 -0400
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Subject: Re: Late IPR disclosure on RFC7024 - Opinions ?
References: <544404B6.4060605@alcatel-lucent.com> <5449476C.1080307@queuefull.net> <54497999.8050500@alcatel-lucent.com>
In-Reply-To: <54497999.8050500@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------080100050603050205020407"
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/RUO7M2MyROPUsTRKXkl4L9rcTpw
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: Fri, 24 Oct 2014 01:26:17 -0000

Thanks, Martin.

Your response makes sense.

In particular, I agree that focusing on individuals is in-line with the 
spirit of the IETF. Unfortunately that might be a structural weakness - 
perhaps even an attack vector - in this context. This comment 
notwithstanding, it probably isn't appropriate for a WG to explore this 
issue in isolation, but rather a topic for broader IETF discussion 
including the IESG, IAB, etc.

As for the more concrete options 1 to 4 that I described, my personal 
choice would be #1. My rationale has to do with IPR issues that aren't 
appropriate for discussion on an IETF list.

Cheers,
-Benson


> Martin Vigoureux <mailto:martin.vigoureux@alcatel-lucent.com>
> October 23, 2014 at 5:56 PM
> 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
>
>
> Benson Schliesser <mailto:bensons@queuefull.net>
> October 23, 2014 at 2:22 PM
> 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
>