Re: [Teas] Regarding IPR on draft-ietf-teas-rsvp-ingress-protection

Vishnu Pavan Beeram <> Sun, 19 March 2017 11:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 56782124BFA; Sun, 19 Mar 2017 04:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 Cr8SZHgd-0nf; Sun, 19 Mar 2017 04:05:30 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 95AF41201FA; Sun, 19 Mar 2017 04:05:30 -0700 (PDT)
Received: by with SMTP id z204so1755283vkd.1; Sun, 19 Mar 2017 04:05:30 -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=cZ8iE+ZC5nANmV6uaF6x/RSvjboVhx0WPWe/IC05bMk=; b=nQpEoG80L95eUSpeCsX/mmPArtqGJQJal7MIHGRTaB+5nDDmSFRTWtSlOYcyI9JKnX zBUvzXhG69BcziasLCVqQdeA5Ojm8vRNBPt6JK94eJ4lj7HV5piWHur+EwAEnNZ3z/os SuGSiQFm3ZSV0eoqSC3EcmiRN5YZtttesvz1HSjKhbomV8Bh2lCCDbIykPKSZTBVVq/I rdTSYIUWH9b72hZRqrgnM+N4WwjUCNBlZuMbeL6YqvO59C9OM7hLboZyxeaPFZItmsDM yVCCwBCO3Upd3iT2iuQtOs0Lf6tnIH7bPZgiCT2Hl4+wWnf2l3bJUFR7wwfAtthed2aC WhIw==
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=cZ8iE+ZC5nANmV6uaF6x/RSvjboVhx0WPWe/IC05bMk=; b=TEWNpAZ2Utvd9viT9zGH0xBsJouZFVuQGNAP1CSJgIumkUCHS/jALmjOnqsAd1nt3A OAJFxICOPmye8hzFDT4fyV0fmhTr5MiOumBTj03I7heznLJySSCYrSCczSOh7tdheUsr NexILawOxvYlQdYyMOCYDO3kVhFSiSakfo6i8oi7Hh36evghB+Eyjhrjy0pNd5G5LAoQ z3rcTTUOX9/sxwnP9lYZ42PztoS2uJFVKNmWLsNkHW54kF9C57c6jM8Kgsp7dSbTPif8 U8GkQpUg8DBlsjAKJfN13133pMGBZzasvl/hriG4R7A9M3Zo0xVMzYNl04fJOoSqS9ad K84w==
X-Gm-Message-State: AFeK/H26fFes+ZtJuplGubyiauMDbVizJYHeD9CPyx8WCi7GwDDvOME2WBcKlr/99agYm6lFvcdc/XDqvuOCgw==
X-Received: by with SMTP id s125mr9463790vkg.118.1489921529715; Sun, 19 Mar 2017 04:05:29 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sun, 19 Mar 2017 04:05:29 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Vishnu Pavan Beeram <>
Date: Sun, 19 Mar 2017 07:05:29 -0400
Message-ID: <>
To: Huaimo Chen <>, Raveendra Torvi <>, Ning So <>,,,, "Tarek Saad (tsaad)" <>,,,,,,,
Cc: "" <>, TEAS WG Chairs <>
Content-Type: multipart/alternative; boundary=94eb2c07be0685a79e054b1363ec
Archived-At: <>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-rsvp-ingress-protection
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: Sun, 19 Mar 2017 11:05:32 -0000

All the required responses are in. We'll start WG LC for this after the
upcoming IETF meeting.

- Pavan

On Mon, Mar 6, 2017 at 4:34 PM, Vishnu Pavan Beeram <>

> Authors, Contributors, WG,
> As part of the preparation for WG Last Call
> 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,
> Pavan and Lou
> PS Please include all listed in the headers of this message in your
> response.