[Teas] Fwd: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09

[Vishnu Pavan Beeram <[e-mail]>]

Forwarding this to the list for the record (original response is missing in
the archives).

Regards,
-Pavan

---------- Forwarded message ---------
From: yudong zhang <[e-mail]>
Date: Thu, Jun 9, 2022 at 7:14 PM
Subject: Re: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
To: [e-mail] <[e-mail]>
Cc: Vishnu Pavan Beeram <[e-mail]>, Dhruv Dhody <
[e-mail]>, [e-mail] <[e-mail]>,
[e-mail] <[e-mail]>, Luyuan Fang <[e-mail]>,
[e-mail] <[e-mail]>, [e-mail] <
[e-mail]>, [e-mail] <[e-mail]>,
TEAS WG <[e-mail]>, TEAS WG Chairs <[e-mail]>, Lizhenbin <
[e-mail]>, [e-mail] <[e-mail]>,
[e-mail] <[e-mail]>




Hi All,

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

Thanks,
Boris Zhang

P.S - my new email is [e-mail]



On Mon, Jun 6, 2022 at 10:34 AM Dhruv Dhody <[e-mail]> wrote:

Hi Quintin,

Your response is fine and in the TEAS mailing list archive!
Your help with getting a response from Boris Zhang (Telus) is needed!

Thanks!
Dhruv

On Mon, Jun 6, 2022 at 10:32 PM Quintin Zhao <[e-mail]>
wrote:

Dhruv and Robin,

I just replied to it again and let me know if it still doesn't go through.

Regards,
Quintin

On Mon, Jun 6, 2022 at 9:54 AM Quintin Zhao <[e-mail]>
wrote:

Hi Dhruv and Lizhenbin,

I replied to it last month and do I need to reply to it again?

Thanks,
Quintin




---------- Forwarded message ---------
From: *Quintin Zhao* <[e-mail]>
Date: Mon, May 9, 2022 at 10:20 AM
Subject: Re: Regarding IPR on draft-ietf-teas-pcecc-use-cases-09
To: <[e-mail]>
Cc: Vishnu Pavan Beeram <[e-mail]>, Dhruv Dhody <
[e-mail]>, [e-mail] <[e-mail]>,
[e-mail] <[e-mail]>, Luyuan Fang <[e-mail]>,
[e-mail] <[e-mail]>, [e-mail] <
[e-mail]>, [e-mail] <[e-mail]>,
[e-mail] <[e-mail]>, TEAS WG <[e-mail]>,
TEAS WG Chairs <[e-mail]>, Lizhenbin <[e-mail]>


Hi All,



Yes, I'm aware of IPR that applies to this draft.

Yes, the IPR has been disclosed in compliance with IETF IPR rules.



Best Regards,

Quintin

On Mon, May 9, 2022 at 8:59 AM Lizhenbin <[e-mail]> wrote:

Hi All,



Yes, I'm aware of IPR that applies to this draft.

Yes, the IPR has been disclosed in compliance with IETF IPR rules.



Best Regards,

Zhenbin (Robin)







*From:* Vishnu Pavan Beeram [mailto:[e-mail]]
*Sent:* Saturday, May 7, 2022 1:12 AM
*To:* Lizhenbin <[e-mail]>; Dhruv Dhody <[e-mail]>;
[e-mail]; [e-mail]; [e-mail]; Luyuan
Fang <[e-mail]>; [e-mail]; [e-mail];
[e-mail]; [e-mail]
*Cc:* TEAS WG <[e-mail]>; TEAS WG Chairs <[e-mail]>
*Subject:* Regarding IPR on draft-ietf-teas-pcecc-use-cases-09



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.