Re: [mif] New Version Notification for draft-sgros-dhcp-and-ipr-claim-analysis-00.txt

Margaret Cullen <mrcullen42@gmail.com> Mon, 07 December 2015 21:14 UTC

Return-Path: <mrcullen42@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7401A893E for <mif@ietfa.amsl.com>; Mon, 7 Dec 2015 13:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level:
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, 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 kHb6B81n-XmL for <mif@ietfa.amsl.com>; Mon, 7 Dec 2015 13:14:37 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 832A21A893C for <mif@ietf.org>; Mon, 7 Dec 2015 13:14:37 -0800 (PST)
Received: by qgeb1 with SMTP id b1so156346685qge.1 for <mif@ietf.org>; Mon, 07 Dec 2015 13:14:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bQRcizQw7YhvSed3x1ZSk19s5woF228CuVNtFFM3FUA=; b=zZImKQE48lgUFg0bD4gLZc1Xq86coNI3TNQ6Ipv1wxyWJa84n9Aa/Y4qdrSltldp0O GJSiRR1bK5nrpiLL2WfLNG0KlGeBvSoAV5Tn2wRC2x16rO6cEE1TEpLS0jkTyrP0F+uK TPJaLBLtS70fvamYxkrcTinUKB9OXPsjW68IM2lFU+Ski3h2moFEUS6/PFHGpY5a28XQ IbmngbWd82d9/r260YV9wzcT4K8LYW4F3Wvam4QF6zntnFJ3B2OT9HC+X59jmx2zkFNe ZJTum2liCKZ3ittCfdxjbMOIyAXBUstAvkztPTBheMMPnndD4HEoCFcEqbjN8r3n6jdP F+6Q==
X-Received: by 10.140.128.87 with SMTP id 84mr40442430qha.54.1449522876767; Mon, 07 Dec 2015 13:14:36 -0800 (PST)
Received: from new-host-3.home (pool-108-7-232-158.bstnma.fios.verizon.net. [108.7.232.158]) by smtp.gmail.com with ESMTPSA id p17sm12326691qhb.34.2015.12.07.13.14.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 07 Dec 2015 13:14:36 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Margaret Cullen <mrcullen42@gmail.com>
In-Reply-To: <56536A51.4010001@fer.hr>
Date: Mon, 07 Dec 2015 16:14:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1AF08278-4AB7-4649-8BEB-778173865340@gmail.com>
References: <20151123192422.32415.11982.idtracker@ietfa.amsl.com> <56536A51.4010001@fer.hr>
To: Stjepan Groš <stjepan.gros@fer.hr>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/BYdkctgpYgOLPiYn0K_6MQlRgpk>
X-Mailman-Approved-At: Tue, 08 Dec 2015 17:28:15 -0800
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] New Version Notification for draft-sgros-dhcp-and-ipr-claim-analysis-00.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 21:14:39 -0000


Hi Stjepan,

While it is your prerogative to write a draft about anything you like, it is not the job of an IETF WG to determine the validity of any IPR claims that is made against a WG document.  The IPR claim exists, and it is up to each individual company to determine how/if any IPR claim does or does not apply to that company's implementation of any specification.  In this case, the IPR holder has only made an IPR claim against the MIF MPVD DHCP option document.

The first question for the MIF WG in this situation is whether we want to continue to work on the MPVD DHCP option given the IPR claim or not.  That question is the subject of a separate consensus call to the list (Subject: Consensus to drop MIF mpvd dhcp document), and any comment on that question should be made in that thread.

Margaret




On Nov 23, 2015, at 2:34 PM, Stjepan Groš <stjepan.gros@fer.hr> wrote:

> Hi everyone!
> 
> We did an analysis of Huawei's IPR claim and wrote a draft about our findings.  In the end, our opinion is that this IPR doesn't matter. But in worst case it only partially covers what MIF did. Anyway, we are not lawyers and would appreciate a feedback.
> 
> SG
> 
> 
> -------- Forwarded Message --------
> Subject:	New Version Notification for draft-sgros-dhcp-and-ipr-claim-analysis-00.txt
> Date:	Mon, 23 Nov 2015 11:24:22 -0800
> From:	internet-drafts@ietf.org
> To:	Leonardo Jelenkovic <leonardo.jelenkovic@fer.hr>, Dejan Skvorc <dejan.skvorc@fer.hr>, Stjepan Gros <stjepan.gros@fer.hr>
> 
> A new version of I-D, draft-sgros-dhcp-and-ipr-claim-analysis-00.txt
> has been successfully submitted by Stjepan Gros and posted to the
> IETF repository.
> 
> Name:		draft-sgros-dhcp-and-ipr-claim-analysis
> Revision:	00
> Title:		DHCP configuration in MIF and associated IPR claim
> Document date:	2015-11-23
> Group:		Individual Submission
> Pages:		11
> URL:            
> https://www.ietf.org/internet-drafts/draft-sgros-dhcp-and-ipr-claim-analysis-00.txt
> 
> Status:         
> https://datatracker.ietf.org/doc/draft-sgros-dhcp-and-ipr-claim-analysis/
> 
> Htmlized:       
> https://tools.ietf.org/html/draft-sgros-dhcp-and-ipr-claim-analysis-00
> 
> 
> 
> Abstract:
>    The purpose of this draft is to analyze different options on how DHCP
>    can be used to configure PvD aware client.  This is done in light of
>    IPR claim made by Huawei and the necessity to find an option for
>    implementation.  In order for an option to be selected it obviously
>    must not interfere with IPR, or, IPR has to be somehow invalidated.
> 
>                                                                                   
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> 
> 
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif