Re: [Teas] Regarding IPR on draft-ietf-teas-actn-framework-10

Dhruv Dhody <dhruv.ietf@gmail.com> Sat, 28 October 2017 02:59 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33FCD13AF75; Fri, 27 Oct 2017 19:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 YTYPfqPMo27Q; Fri, 27 Oct 2017 19:59:34 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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 A220B139F18; Fri, 27 Oct 2017 19:59:34 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id 8so10654646qtv.1; Fri, 27 Oct 2017 19:59:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=tlIcW2ln17MdKjdYKRfV3Dxf2zUukzdk8qcQqsU0p4s=; b=arxrsRt62ROxEc23A+04tzzyJiL/GBm8x2DHpsrp/csTD6VDt3ajPXnz06RimywQ1x B4Xlm7niGoExj8EamKnqCcuTbdhaSFHh2mxju9/hIZjNL4ysgRsg8irnEP7lEyL31Mo6 nUDKtVERIqWRe+7lwysUy58iS7jHPPPdONSxw8jrfpGpuFQC4mMkTzLrWZxrC13NDWaC LjLUzQsPN+KmuG+dPamSra/LqKqKtGeJT3zaNONnLmqD0jo9FVxHfA0LdsZQbuEFuoBe eb50HsaxO6tf68CgtGC8/FjOArUgXglBTRxI8LBt13n69IVJ17StangAES1oD4VCoXkg 0BCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=tlIcW2ln17MdKjdYKRfV3Dxf2zUukzdk8qcQqsU0p4s=; b=UlwM5fxJoHtG6vzkpctKqN1O7TbvTuAxwEk5SJ6r3LMpX92fbnnSKZGj4uftLXcp4B aLMkkdfDZFUzPCkNgYv89tQRprKccISSDyyh7SkAb++n/POc+tWi9MgjUNTbGIIrd6yr QxGqA+CZAQusFJ+FHiZdDCwplWYMpEZLvSDcyW3MQDIc80TC6ifactj265qTco05AstG B6soufisGboAwpZ6stipt+5V3cvYAFrU0S+ffgkRjJU8o1eNSBlAgfZMECnqy+A0gS4C siI2Le/KzItHFhZ0hUMK9Av5UsCBzwQlfuqVr0m6M6B622Q8ACPWYSk+Z7iYuRz5drbW YTpQ==
X-Gm-Message-State: AMCzsaWyo6HdsoCnkhj8/EQtVmkY2IM4vETZXOIcmm/fwGbF/ULUT4BG d+pmvkRE0naKzzSEKZsXmpD4d89tpai2NcXvwoo=
X-Google-Smtp-Source: ABhQp+TM5ve489rRRSocbWi3+y7znxy8Am5fK406LqwJhvYelUnPyyBLecwiUfstJszTQXnedJu6E3bPCr63YKLmvm4=
X-Received: by 10.200.54.85 with SMTP id n21mr4188390qtb.179.1509159573760; Fri, 27 Oct 2017 19:59:33 -0700 (PDT)
MIME-Version: 1.0
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.140.86.17 with HTTP; Fri, 27 Oct 2017 19:59:33 -0700 (PDT)
In-Reply-To: <CA+YzgTunGbZzMOvS9a5fMST2LLk-GzU4mm35aU2Kkr992DLUWQ@mail.gmail.com>
References: <CA+YzgTunGbZzMOvS9a5fMST2LLk-GzU4mm35aU2Kkr992DLUWQ@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sat, 28 Oct 2017 08:29:33 +0530
X-Google-Sender-Auth: P_WVFHzQHrM4TneACqich3YjAFY
Message-ID: <CAB75xn4k8jXyAA0fBQJM5WcxeSxTostObLr5Dao4x6dJLb-URA@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Leeyoung <leeyoung@huawei.com>, Adrian Farrel <adrian@olddog.co.uk>, Italo Busi <Italo.Busi@huawei.com>, Khuzema Pithewan <kpithewan@infinera.com>, "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, Luyuan Fang <luyuanf@gmail.com>, "Diego R. Lopez" <diego@tid.es>, "Belotti, Sergio (Nokia - IT)" <sergio.belotti@nokia.com>, "King, Daniel" <d.king@lancaster.ac.uk>, Gert Grammel <ggrammel@juniper.net>, "teas@ietf.org" <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="001a11377ad84db0c2055c9298ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/u24Xu-7DLUhYq8Lpp6hz7eju39k>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-actn-framework-10
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Oct 2017 02:59:36 -0000

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

Thanks!
Dhruv

On Sat, Oct 28, 2017 at 2:58 AM, Vishnu Pavan Beeram <vishnupavan@gmail.com>;
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,
> TEAS WG Chairs
>
> PS Please include all listed in the headers of this message in your
> response.
>