Re: [netmod] Regarding IPR on draft-ietf-netmod-entity-05

Andy Bierman <andy@yumaworks.com> Tue, 28 November 2017 21:28 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF51124205 for <netmod@ietfa.amsl.com>; Tue, 28 Nov 2017 13:28:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.com
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 x5EFCPRoEAou for <netmod@ietfa.amsl.com>; Tue, 28 Nov 2017 13:28:48 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 067051275C5 for <netmod@ietf.org>; Tue, 28 Nov 2017 13:28:48 -0800 (PST)
Received: by mail-lf0-x22f.google.com with SMTP id f18so1460741lfg.8 for <netmod@ietf.org>; Tue, 28 Nov 2017 13:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=t+CuQFjEkRIAx81+/Jbuo4q8yaTI34Fmmtv5yO7O5jU=; b=xQ0PfaN47nxsB8Rh9BEisyDODajpLKE1CnsSU7rNkvzN4hhBXiX3zRCSgZoX9BRUgq WQ/9VBrl/sNJG10Zpq0HwmZ99iF9PpVkcD1dexQH0bmLlAc471xNaW0ewQ1whk51grLc kiBr7NHA6YuRrEqpZ0GPrDLV3ngAjSw6WEQLeoTS2yzoGuiICrOI+jbPX/1y/sy/s8Ii Vtc6V9tVr9Ibu6dziXoE3ZMhlUlPw8i6LpZCtiPY1t2deXxx8bbUEljNrRJnSe8k1s11 +64XsWsoMEthPV1pWZo9uo6JHw7ZfcBlxVxTyuzI7oe26bi6I03LvhnR9KUgJAUfZfQj VW2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t+CuQFjEkRIAx81+/Jbuo4q8yaTI34Fmmtv5yO7O5jU=; b=qQfs+OPnebEhDxvuNPLUsibZHYOXjROCjSfmprdXz65GAHg7w3UZBqlq3HSh12BJgX Mn8sOIpKGbIPthKuUf4RZMBmJCtahtwEMV/WzgtIoK2hkE8lazdmtFdxgbkH9leC6/+j l6xQvtCfx2UOrT/eldh3e1woj9A3AMVNX2rSv2BxWbCLhvwf46n2TO0loi4luQVCcoe5 BxkP3yHrb+VsLs4QVPtcpLm/sEhb6U3fqlhv4DrYhR7tctBvJlReSjMhrTv/8uJ7CLBj Vh2cNQ415sUvIXYlL56j5tSnBPHuE3Z3xOJ6HIQhcYqS6jf8JKmrVfc725VmXKA6tJL2 KVaQ==
X-Gm-Message-State: AJaThX66u6U7071S19qcjorfrQgF4V3yxQKr763aU8yT3gISzyyNAJY9 9ht+pCv5m8Dn74dR+dEhFjxW2TUNr9x+hgzwcveIww==
X-Google-Smtp-Source: AGs4zMZ1Q7IkwctcEqc2W4uY1bBKZxi9c3aVQ3DyWZFjXyNPqC+FfKvoKrQCHTd2d5SdytwLscqyvzqsOhEj9cdq+tE=
X-Received: by 10.46.17.153 with SMTP id 25mr268801ljr.36.1511904526307; Tue, 28 Nov 2017 13:28:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.33.81 with HTTP; Tue, 28 Nov 2017 13:28:45 -0800 (PST)
In-Reply-To: <56c5dbed-0fcd-516d-cdb0-e38180e390c8@labn.net>
References: <56c5dbed-0fcd-516d-cdb0-e38180e390c8@labn.net>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 28 Nov 2017 13:28:45 -0800
Message-ID: <CABCOCHQF5EE0yyuPcG5fuHc5p0Z3NsyX9zzmf=npVLu9GUSdPw@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Cc: Martin Bjorklund <mbj@tail-f.com>, Jie Dong <jie.dong@huawei.com>, Dan Romascanu <dromasca@gmail.com>, NetMod WG Chairs <netmod-chairs@ietf.org>, NetMod WG <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1a615e39a957055f11b43c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/O24xl3_DEFlfMDnelS5oagIUabY>
Subject: Re: [netmod] Regarding IPR on draft-ietf-netmod-entity-05
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Nov 2017 21:28:50 -0000

No, I'm not aware of any IPR that applies to this draft


Andy


On Tue, Nov 28, 2017 at 11:06 AM, Lou Berger <lberger@labn.net> wrote:

> Authors, Contributors, WG,
>
> As part of the preparation for WG Last Call:
>
> Are you aware of any IPR that applies to drafts identified above?
>
> Please state either:
>
> "No, I'm not aware of any IPR that applies to this draft"
> or
> "Yes, I'm aware of IPR that applies to this draft"
>
> If so, has this IPR been disclosed in compliance with IETF IPR rules
> (see RFCs 3669, 5378 and 8179 for more details)?
>
> If yes to the above, please state either:
>
> "Yes, the IPR has been disclosed in compliance with IETF IPR rules"
> or
> "No, the IPR has not been disclosed"
>
> If you answer no, please provide any additional details you think
> appropriate.
>
> If you are listed as a document author or contributor please answer the
> above by responding to this email regardless of whether or not you are
> aware of any relevant IPR. This document will not advance to the next
> stage until a response has been received from each author and listed
> contributor. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S
> TO LINES.
>
> If you are on the WG email list or attend WG meetings but are not listed
> as an author or contributor, we remind you of your obligations under
> the IETF IPR rules which encourages you to notify the IETF if you are
> aware of IPR of others on an IETF contribution, or to refrain from
> participating in any contribution or discussion related to your
> undisclosed IPR. For more information, please see the RFCs listed above
> and
> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>
> Thank you,
> NetMod WG Chairs
>
> PS Please include all listed in the headers of this message in your
> response.
>
>
>