Re: [Teas] Regarding IPR on draft-nsdt-teas-ns-framework-04

Dhruv Dhody <> Sat, 15 August 2020 05:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9CF0F3A07E7; Fri, 14 Aug 2020 22:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kcWEug1PrRB5; Fri, 14 Aug 2020 22:56:41 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 384E83A07E5; Fri, 14 Aug 2020 22:56:41 -0700 (PDT)
Received: by with SMTP id h4so12836240ioe.5; Fri, 14 Aug 2020 22:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B0Zm4XlftSl7I+Iw1Qv6vUx3biIXoTUcnsi8tPo5Q98=; b=UShRp6QeEg/vKWWyZIznycsBiiFmke7T2vx0E/OSlKBKph8JGmCUdtA06EEm+XGUCm Z0O3M+Mh5izNGdzCiSEM/sPEHgPp3mNRTG4+knMNKyk8GwK13QLL34qUlBzVBkWuaPLG /MmuKFySdEGFdFCMV55hHIVtUqOPoGdeeZOLzuq47URrMTPV6UcIraF1+khdhNdfSrCN nQJG0R9CAehYQR/TuixQjOVlXyuygZb1sV4JrHJLHcqVZ2qJt0KDEqyw34/OKJS00+nH T4Mo7yrroEUIyJwSNTUrtkUD5HbvqdfJbmHLyeww4KOWsdoHvmLizYpnf51EQ9+geE/L oglw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B0Zm4XlftSl7I+Iw1Qv6vUx3biIXoTUcnsi8tPo5Q98=; b=QWmWzA6pR5OidUhw0O+lJxWXDCT6+2gBa5gOWmS6mOPZb2GboN+OcXO/DCYencUltH 3buufS0vsxt433E1EYkwE4BoosSYqC4+uMTP7gsqATQJQMt1Ptw1/TRGoGL044LUpknE zAVfm1qEf5D7klv/CDIsS+SwM6PrRCOZSZvUIoo/IxJFGz7JNgZDBmITClQv2drD/uDs feUL19SU8h30p0DBPRTRg4kzUXVapx6i2EQj0INXVQVqtbBnHLLwpSeRUANJeHepnmb0 yNukHAFwkgh1mMQiBuBxuMHviNgVqDpmS2siCKc76QrnxNvyTc46zRjX1jrxeYv3EWFz qfzw==
X-Gm-Message-State: AOAM530iIqdcGoNMMEOmmkukI35HEZWr0MZdLHa4kbZ+Efk3jp8HtFVh p3FRNAR3yYkxxemns1nUjtjUIb3Z+3CZ70N85z0=
X-Google-Smtp-Source: ABdhPJz2ho1zWXJvkIzpk4BLG1dU0D79tnYNDZ3jaIqk5VuXtMjBPWPIrFTbNSlc8Y6aGb0qVbZRZR2MhD8k3VThsBM=
X-Received: by 2002:a6b:e002:: with SMTP id z2mr4822970iog.178.1597471000352; Fri, 14 Aug 2020 22:56:40 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Dhruv Dhody <>
Date: Sat, 15 Aug 2020 11:26:04 +0530
Message-ID: <>
To: Lou Berger <>
Cc: Jari Arkko <>, "Rokui, Reza (Nokia - CA/Ottawa)" <>, Xufeng Liu <>, Jie Dong <>, Eric Gray <>, John E Drake <>, TEAS WG <>, TEAS WG Chairs <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Teas] Regarding IPR on draft-nsdt-teas-ns-framework-04
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 15 Aug 2020 05:56:46 -0000

Hi Lou,

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


On Fri, Aug 14, 2020 at 6:51 PM Lou Berger <> wrote:
> Authors, Contributors, WG,
> As part of the preparation for polling for WG document adoption:
> Are you aware of any IPR that applies to draft 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 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
> 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
> Thank you,
> Lou (and Pavan)