Re: [PWE3] IPR issue with draft-ietf-pwe3-p2mp-pw-requirements-06

"Andrew G. Malis" <agmalis@gmail.com> Tue, 07 January 2014 11:03 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF9E1ADEBB for <pwe3@ietfa.amsl.com>; Tue, 7 Jan 2014 03:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 OAVOckDtSqc3 for <pwe3@ietfa.amsl.com>; Tue, 7 Jan 2014 03:03:16 -0800 (PST)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6181ADEB1 for <pwe3@ietf.org>; Tue, 7 Jan 2014 03:03:16 -0800 (PST)
Received: by mail-qa0-f52.google.com with SMTP id w8so395093qac.11 for <pwe3@ietf.org>; Tue, 07 Jan 2014 03:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6uvAtnMZW+zH3b2lnPoRLHUx/hOx+vcAxFAzM1/8KFo=; b=f7AaGtaFDbwqgKIksbx3MCVkBL8IWCTf370KJ5EZzzzKQ/i//qrwrlk0zkgCQvVSJi aTBdhRCCCHYWI/q/cJW4wwkWQ/4995tYLghLzOrya5zhBFqOKceAuK2niHLroIsYu+Wl E5T/daRhJf+vc130EgfCI/J9C4tJCPNB4J7KjQEDge13Z+VYHWB880Zzwa4ZoyVfnkm/ 0s1bRiwFYnsk3ARQG7HFiBM6IUfW88DCRGI/96C9jTCajm/DoDrnTwvZL8L5QPW2Ujob Os0jS1NvXs/w4T6EgZyIvjiSECc2zt4Y+0H63msV5vHCmTsD9lS6/po5f+NN6qDtG+3a wS+w==
X-Received: by 10.224.8.72 with SMTP id g8mr188286894qag.83.1389092587637; Tue, 07 Jan 2014 03:03:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Tue, 7 Jan 2014 03:02:47 -0800 (PST)
In-Reply-To: <00d201cf0b95$ac572a60$05057f20$@olddog.co.uk>
References: <CAA=duU1UKajWNPj=DT1_AJw0=ad9d6sJh+p=_VTfBenvOuu_yA@mail.gmail.com> <00d201cf0b95$ac572a60$05057f20$@olddog.co.uk>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 7 Jan 2014 06:02:47 -0500
Message-ID: <CAA=duU2akOMsLCZASQrDY--h5CBTZT3ejyKTeW4yW--eehoP-A@mail.gmail.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>, draft-ietf-pwe3-p2mp-pw-requirements@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PWE3] IPR issue with draft-ietf-pwe3-p2mp-pw-requirements-06
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 11:03:18 -0000

Adrian,

Thanks!

WG and draft authors,

Adrian asked (and I repeat for myself as well):

> What do the authors and WG think? Would removal of an option for the creation of
> a return path diminish the document?

Any other opinions?

Thanks,
Andy

On Tue, Jan 7, 2014 at 5:46 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Hi Andy,
>
> Let me speak as an individual contributor.
>
> I think this may have got buried under the pile of Christmas cards.
>
> Looking at the IPR terms and the disclosure dates, I can't say that I am
> personally happy to have this I-D go ahead covered by this disclosure.
>
> While I accept that this document is a requirements spec and so it may be hard
> to conceive how the IPR applies (there being nothing in a requirements spec that
> I can see would be implemented) i think that the requirements necessarily drive
> the solutions and thus a solution is likely to be caught by this IPR.
>
> However, it seems to my reading of the reported patent that this IPR covers MP2P
> PWs.
> Looking at the I-D, the mention of MP2P is very limited (at the bottom of
> section 3.1).
>
> My suggestion, therefore, is to remove the text in section 3.1 that may be
> encumbered so that this I-D can move ahead without any disclosed IPR. i think
> that would be a relatively minor change (although it is text that has been in
> the I-D for a long time).
>
> What do the authors and WG think? Would removal of an option for the creation of
> a return path diminish the document?
>
> Thanks,
> Adrian
>
>
>> -----Original Message-----
>> From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Andrew G. Malis
>> Sent: 23 December 2013 20:03
>> To: pwe3@ietf.org
>> Cc: draft-ietf-pwe3-p2mp-pw-requirements@tools.ietf.org
>> Subject: [PWE3] IPR issue with draft-ietf-pwe3-p2mp-pw-requirements-06
>>
>> I would like to make the WG aware of a potential IPR issue with
>> draft-ietf-pwe3-p2mp-pw-requirements-06, which I've been getting ready
>> for submission to the IESG. On Nov. 13, 2013, ORANGE filed an IPR
>> disclosure, https://datatracker.ietf.org/ipr/2249/ . The IPR concerns
>> multipoint to point PWs, which are are one of two optional return
>> paths discussed in draft-ietf-pwe3-p2mp-pw-requirements-06.
>> Point-to-point PWs are the other optional return path discussed in the
>> draft.
>>
>> Given that this IPR was disclosed late in the process, before
>> submitting this draft to the IESG, I would like to get a sense of the
>> WG as to whether it is OK to submit the draft as is, or if the WG
>> would prefer that the optional MP2P return path be removed from the
>> draft.
>>
>> As this is over the holidays, and many people are on vacation, I won't
>> take any action on the draft until at least the second week of
>> January.
>>
>> Thanks,
>> Andy