IETF Logo Mail Archive

Re: [Teas] Regarding IPR on draft-ietf-teas-yang-path-computation-18

Vishnu Pavan Beeram <vishnupavan@gmail.com> Tue, 17 May 2022 19:43 UTC

Return-Path: <vishnupavan@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 94577C15E6CA; Tue, 17 May 2022 12:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmII9budLWPZ; Tue, 17 May 2022 12:43:52 -0700 (PDT)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C8EC15E6C3; Tue, 17 May 2022 12:43:52 -0700 (PDT)
Received: by mail-il1-x12e.google.com with SMTP id b11so52731ilr.4; Tue, 17 May 2022 12:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xNxQQGkbjW8zDvfXqrDY4DLeUR+5s/x1KTaDEsjDQSk=; b=Kf+xergOIK5GHISD3I3Jg7osCgxuMcjcgdR/dmqfHvAAoBK+c0ABR9wuAqiXivZajo Khz+uEJUyKn52zIWA4qLxkFCuJp7kzK9ZvfsHvtqI8//203vrNjNEV1Xn4ujeiVoqDQu c8M+V3MEb9YqyVvt8WscZCDaUnohLhRcLRh3UZUYFdxlgFMzutxwgFZJnvZgyS5k3oZT n/l1mCdwzqM92gPTkhZWqTsZlnPg2xSKo89lvI+HgQbc+XOWYsmmysxmAZXOb0V8JnSU Dld9scYlivm8w4JdQ7Vvr10UZcP3gbfXbAchXEbxbJQdD00/QHLx6DsXPdPh7GAJjoAt w+sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xNxQQGkbjW8zDvfXqrDY4DLeUR+5s/x1KTaDEsjDQSk=; b=dxmhUR3LpeGzAm1xkCeXYfIBKFyZTdu5RssxVsLDv92gzrPwGM5Mpq/93ZwPTpMgpQ nIy0nseHXi366bBfIy/jFVOn11prD5u/EhDXWn3Ri4WbDLhGRHTtsewMJl5E6UjZg1xi rcyDuiFDl8eNVY3aAHKQ23CuGQuWWdLkt/iXiGWcIgTjm34RFE7LzWJ5srAGG3jyD6i5 IIfM3yJNghFmcRDDwVkrozeOs+6lzjVLQmE+Gsbw9WDq47kDmg2HHi/45hm2Rd2rpfHk o8f+US7k1D4T6DbSVcHqTx1EQlH/RMA3M9AYQ+oCvewC54a7YKQytdLPH6BvEX8cikEu K30Q==
X-Gm-Message-State: AOAM531UlVtIBfR11NAYyaspzkwskyYqCOj13pxaiQT4EQ7SZSFZOZzM kQ09xrK+hiJWtPQQ6yBGjvgtazGK4s4OoLrJCGY=
X-Google-Smtp-Source: ABdhPJxwj5FJFixwRPq8379cIF6gQQj8anY5TkjGN+hUPWAsLRn6f78gPsdO1EYlmrYP5kElXr90iUaSgWExhxk1Ap0=
X-Received: by 2002:a92:6706:0:b0:2cd:f8ad:dddf with SMTP id b6-20020a926706000000b002cdf8addddfmr12695867ilc.212.1652816631343; Tue, 17 May 2022 12:43:51 -0700 (PDT)
MIME-Version: 1.0
References: <CA+YzgTsTioj69oA8+6r2Skv2Oa4kAGRpa81UOjqvEUisfUKrRg@mail.gmail.com>
In-Reply-To: <CA+YzgTsTioj69oA8+6r2Skv2Oa4kAGRpa81UOjqvEUisfUKrRg@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 18 May 2022 01:13:40 +0530
Message-ID: <CA+YzgTtYYy0urzB=HY-FmPXjUE=qFHwMLt57vOLHOLLoJOspZg@mail.gmail.com>
To: Italo Busi <italo.busi@huawei.com>, "Belotti, Sergio (Nokia - IT)" <sergio.belotti@nokia.com>, Oscar Gonzalez De Dios <oscar.gonzalezdedios@telefonica.com>, Anurag Sharma <ansha@google.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, victor.lopez@nokia.com, Ricard Vilalta <ricard.vilalta@cttc.es>, karthik.sethuraman@necam.com, michael.scharf@gmail.com, "Beller, Dieter (Nokia - DE)" <dieter.beller@nokia.com>, gianmarco.bruno@ericsson.com, francesco.lazzeri@ericsson.com, younglee.tx@gmail.com, Carlo Perocchio <carlo.perocchio@ericsson.com>, Olivier Dugeon <olivier.dugeon@orange.com>, Julien Meuric <julien.meuric@orange.com>
Cc: TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000030ae9205df3a5c41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4QL1-_3lwCZZWWZ0CiJLrEN2I7s>
Subject: Re: [Teas] Regarding IPR on draft-ietf-teas-yang-path-computation-18
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 17 May 2022 19:43:54 -0000

Missing response:
francesco.lazzeri@ericsson.com

Regards,
-Pavan

On Fri, May 6, 2022 at 10:53 PM Vishnu Pavan Beeram <vishnupavan@gmail.com>
wrote:

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

v2.23.0 | Report a Bug | By Email