Re: [Teas] Regarding IPR on draft-lee-teas-actn-vn-yang

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 02 May 2018 03:39 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 40B04126B6D; Tue, 1 May 2018 20:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 jVVLV7cQ0Ya5; Tue, 1 May 2018 20:39:57 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (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 1BE0612421A; Tue, 1 May 2018 20:39:57 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id i136-v6so6872528ita.2; Tue, 01 May 2018 20:39:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:sender:from:date:message-id :subject:to:cc; bh=Wq8/JN5VDjAjDUqxtl765beczIUpmhmJvOUiQLospmI=; b=fG2g+BRVuSGFgeyXjrWCVz9hZW/Y5mc1l1GslJOLkyui2FjEagIAySlp533OVvDYbW AUrkra12A5T5KV+qUFQmh71IosZEJcA6XDnk4IXSoWydjlFyUzFnLVHsLPKAlyLKIfRC RGEfYFQjzG2jlR3eZTu9/mDSG+Bx1GWkXlUQy88SxEwNYGdgalHjWsPq8sZKBXAlDg/q IjwhjVBy249X4Cgv2i6tRT33BkNOyEi1Ysd+4Gez2ym4XZAi33sBuVOSxVsqJvShAQjg 2SPvWKr+/cwLCMv2LAUGYb/CIc8oWeAtb7g6GfRCEzHLJA8Pp65STkcGWQffYtvTumUg ZRkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:sender:from :date:message-id:subject:to:cc; bh=Wq8/JN5VDjAjDUqxtl765beczIUpmhmJvOUiQLospmI=; b=Amnw6YJfpQW2Ny2sGALkn/SEyGN8r9RF8DYHqbZNtPWwAJ6aKfuYfLWxjND7/Vgo6g g+tuEgosgiV3GOZMYT0yU1kCDxe0J7KddOVeS2PQRwhEnq8oK8zEFQJptFRfnDMUq9Xf tc994BINxRizUsUoItKQhFgQ8GJMoMS1tMN6Y1Gilz4P+YHjXvcu3g7aEerwT9tATx8w gqQH33iGQ9U7ej7RaOrE+VP3k7e7Lt5o/jGV4+AUtqrERZ6cE/+nMy3WErEupljMfi90 O/3Bow/pS0+U3Zi+6IYUe4XZTJmGxm7T7KukXBGVd7Q4beQg201rtc7EiUNzgKFJNuPl EYoA==
X-Gm-Message-State: ALQs6tCdjkBquzplm7rpSame78IgjpmbDRFvhOKfljSUWU5fzsn0sPJ4 OqC/pNlYVyRFYGZmNZGt62rLVimc8NV98HkpcLs=
X-Google-Smtp-Source: AB8JxZoTGnY5+lar6QU2aMujd+J1gShIuI62RoxMKk1gudNj5MVj6w7RekJteRoUqPkMH0q7DRixKnXRoXLkyD3WqnA=
X-Received: by 2002:a24:8e45:: with SMTP id h66-v6mr19412532ite.152.1525232396288; Tue, 01 May 2018 20:39:56 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YzgTuiBPQmifhiME=+gVAVeVfNyvJPKeMjfzeOGD2H1-svnQ@mail.gmail.com>
In-Reply-To: <CA+YzgTuiBPQmifhiME=+gVAVeVfNyvJPKeMjfzeOGD2H1-svnQ@mail.gmail.com>
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 02 May 2018 03:39:45 +0000
X-Google-Sender-Auth: Hi4jcE50Qa46EiPrConUdnZ-wBE
Message-ID: <CAB75xn5mBnm4vtbVZzag4o_nHje8mFYyaMi-5y0GFkGcbGYssQ@mail.gmail.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Cc: Leeyoung <leeyoung@huawei.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Igor Bryskin <Igor.Bryskin@huawei.com>, =?UTF-8?B?7Jyk67mI7JiB?= <byyun@etri.re.kr>, Zhenghaomian <zhenghaomian@huawei.com>, "Zhangxian (Xian)" <zhang.xian@huawei.com>, "BELOTTI, SERGIO (SERGIO) (sergio.belotti@nokia.com)" <sergio.belotti@nokia.com>, Qin Wu <bill.wu@huawei.com>, Takuya Miyasaka <ta-miyasaka@kddi.com>, =?UTF-8?B?67CV7LaY6rG4KFRyYW5zcG9ydCBTRE4gUHJvamVjdCkgKHBldGVyLnBhcmtAa3QuY29tKQ==?= <peter.park@kt.com>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>, teas-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002e49a8056b30d7cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/XGWF2VlGdkU4TjD-JIjLEWQ5zVk>
Subject: Re: [Teas] Regarding IPR on draft-lee-teas-actn-vn-yang
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: Wed, 02 May 2018 03:39:59 -0000

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

Regards,
Dhruv

On Wed, May 2, 2018 at 7:03 AM Vishnu Pavan Beeram <vishnupavan@gmail.com>
wrote:

> Authors, Contributors, WG,
>
> As part of preparation for WG Adoption
>
> 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.
>
>
>