Re: [Netconf] Regarding IPR on draft-voit-netconf-notification-messages-01

Andy Bierman <andy@yumaworks.com> Tue, 22 August 2017 18:00 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA037132935 for <netconf@ietfa.amsl.com>; Tue, 22 Aug 2017 11:00:23 -0700 (PDT)
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 jMhTLpi1ER0v for <netconf@ietfa.amsl.com>; Tue, 22 Aug 2017 11:00:21 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 782201321A4 for <netconf@ietf.org>; Tue, 22 Aug 2017 11:00:21 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id z132so3249331wmg.1 for <netconf@ietf.org>; Tue, 22 Aug 2017 11:00:21 -0700 (PDT)
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=JEwIzoEmpcvfyIorWIWU85DG+TW7x+fGgo1eLp1b2n4=; b=zdIdAEuZuMrvV/Y3g5ILBqCZk7eTIbIUtgR0Q0rB0zLYWg8YvGMBfhbmI5NJmiKwzj sbJ7HkiyT2iDWrTAgEr6ho2V+Pj12zeNo7bYgRnLFoJORe/STiIm/Y6PozWnacOYS/8Z v5jiVNxYn+vpnPCw/4iD9JyTqeB5ppw3L7akC2j18XaYXQ8+P2PTfgkt0NSRAJa9fQkU xdVej/EP+8TSF2BObNldvwqgXCPUuc7ETxmM2dYnvwdWiLIUa9ll20RpEvCWOtLkI0nf wYJdz9N60BFleR3Z0UCD4NOgdSomBk8r0RVWxlHwiLdSKOcirIb6ALdR0TFVbC2apRlP RXfA==
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=JEwIzoEmpcvfyIorWIWU85DG+TW7x+fGgo1eLp1b2n4=; b=jM0n5n5qwXNhRssf40e+HPVe+1MnrxolaxCqLMNeMdQUvYFGSJOwwvxfz5l1Ro/ok8 qm5r6Sb11zAu4g8lfjJLE+fwSWfpvvpJ/OQ/fgmaLWYFu2zvKGTRmk3uqEAzaRWqBVqB G3ulYlfqO9/AUdzt1OxH8teO+jAfHVGQzVGn4lm41+1pDZn2rwFtJ4qlvv8BH9oWUV0H LItWobIF7uykWwn53dLX9t4Fjbf9TlDUD2AwsFErQFS8Yi73rBgmehZQoQ+FZeOO/9Pp MPkBR0Pi+hgVEe0//CtQI5oxPyqcEIYnbh0nrPc1fA9HJLkK8pWfSGrhDv7LTSiQsdwg XjpA==
X-Gm-Message-State: AHYfb5h5lmCWKRBvTUGpFMj9mX2eSOA8ZhKWubZjKkHv5kyX3PsIodJR +ibNyZwXWg+AB9FTGhpOJrjWFhnG8mjj
X-Received: by 10.28.16.133 with SMTP id 127mr232301wmq.75.1503424819749; Tue, 22 Aug 2017 11:00:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.221 with HTTP; Tue, 22 Aug 2017 11:00:18 -0700 (PDT)
In-Reply-To: <0BB5D437-8C0A-4E56-BE19-0FE027D57EB2@juniper.net>
References: <0BB5D437-8C0A-4E56-BE19-0FE027D57EB2@juniper.net>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 22 Aug 2017 11:00:18 -0700
Message-ID: <CABCOCHSsk+7TxXrz7X8meirNvQbbrjz--f7h=suYy9xwB6wMpQ@mail.gmail.com>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "evoit@cisco.com" <evoit@cisco.com>, "ludwig@clemm.org" <ludwig@clemm.org>, "timjenki@cisco.com" <timjenki@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1146d95053fc7805575b5eb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/uBZQWbm98tBNNOJ8N09d6TOUKrU>
Subject: Re: [Netconf] Regarding IPR on draft-voit-netconf-notification-messages-01
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Aug 2017 18:00:23 -0000

Hi,

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

Andy


On Mon, Aug 21, 2017 at 3:06 PM, Kent Watsen <kwatsen@juniper.net> wrote:

> Authors,
>
> As part of preparation for WG Adoption of "draft-voit-netconf-notification-messages-01",
> are you aware of any IPR that applies to this draft?
>
> 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 3979, 4879, 3669 and 5378 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,
> Kent (and Mahesh)
>
> PS Please include all listed in the headers of this message in your
> response.
>
>
>
>
>