Re: [Teas] Regarding IPR on draft-deshmukh-teas-rsvp-rmr-extension

Vishnu Pavan Beeram <> Wed, 02 May 2018 01:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E52C412D77D; Tue, 1 May 2018 18:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id myau-GdY2naD; Tue, 1 May 2018 18:36:56 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CDEBA124F57; Tue, 1 May 2018 18:36:56 -0700 (PDT)
Received: by with SMTP id j5so10364988pfh.2; Tue, 01 May 2018 18:36:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iV5BJt8qkSk4qwTRUrl4Zy5tSKQk2G1By6kYH0MBg5s=; b=mKN4Of3ce3oJAUmMblvpR7nbs2u6lqK+VXnw4GfE55IXM8oQ1nvVrgFHXQrd7I/3O5 B6FNyWanzpwpD34Sp4u4UKwni7WZTdZ7GDLnhtUo9oYUMxK+mo1ibx10vjRILwC7sOmG Qnu7O3zBB6tr5F1/yGa9R60k64g4+MER2qQuegDiVVmBe8oeV0N0GMSwuomkf02uNhdq DGwsr9IBpdWz5RbmWhA34jFT3kfkvaMbcfTk3JBlAadVycEdfFuxPmBISUPIewNW8S5M AFab6E515MIvPAHc4NfBZer1hCss6H3c3jafuUEXfwfCmjgTEJUYc+sTP/Y+wCf8vwi2 nhHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iV5BJt8qkSk4qwTRUrl4Zy5tSKQk2G1By6kYH0MBg5s=; b=BgWvvUnrB96F3e7IqJIH4D63Mpz8Hfh8ZSLuJJNq2dBX/3SdXBaigx414TmwTgz7Yp pAHfYdGr8+GpLnMHUm1USIhHB7Hi2cFO6IZ+B4Rp2yOYh777Yw8sqaghB+35XGVx6n+A fBX6DmUrwEyu4PT+MiV6VNB/oYlGxfDNxXg4dvk8OuRjqrgwVg/dvcA3Wyw45b+XuTm6 F1Wx4Y40OjJ+xpHSNInFSnob7QAUycoNUYzQVY/iVeJFLZ0MGZ60/ELN7stMMj+uolil ZO/AutR6jVZilzprhdZrzfYyfR0M/4sWtRQrbqCmM7Bgb3hOWVuwGqpgmAbnoVI5lFVc sKJQ==
X-Gm-Message-State: ALQs6tA6Y/AD88/QC87hweTggtDl+meXpmKenIHDPOqgRbROK2kLJDo4 I0HuHHhLfKVCOtZABB6c7+MdzUFXIJFNzQE1UUg=
X-Google-Smtp-Source: AB8JxZpCjfCWBLStDu5sHimvKLn9bNohN7fAY+/mKZBS/Azm7nI5O1EYwe52tXtii2KgD2Q9VxrUJZmVxUtU7pBIXho=
X-Received: by 2002:a17:902:850a:: with SMTP id bj10-v6mr9753973plb.239.1525225016481; Tue, 01 May 2018 18:36:56 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 1 May 2018 18:36:55 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Vishnu Pavan Beeram <>
Date: Tue, 1 May 2018 21:36:55 -0400
Message-ID: <>
To:,,,, Raveendra Torvi <>
Cc: TEAS WG <>, TEAS WG Chairs <>
Content-Type: multipart/alternative; boundary="0000000000004f5e64056b2f1f07"
Archived-At: <>
Subject: Re: [Teas] Regarding IPR on draft-deshmukh-teas-rsvp-rmr-extension
X-Mailman-Version: 2.1.22
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: Wed, 02 May 2018 01:36:59 -0000

We are still waiting on responses for this. Please include all listed in
the headers of this message in your


On Wed, Feb 21, 2018 at 4:21 PM, Vishnu Pavan Beeram <>;

> 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
> 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,
> TEAS WG Chairs
> PS Please include all listed in the headers of this message in your
> response.