Yes, I am aware of an IPR that is associated with this Draft and the IPR
has been disclosed in compliance with IETF IPR rules.

Thanks,
R.Ashok


On Fri, Oct 17, 2025 at 9:39 AM Linda Dunbar <[email protected]>
wrote:

> Aseem
>
>
>
> That is good. Thank you.
>
>
>
> Linda
>
>
>
> *From:* Aseem Choudhary (asechoud) <[email protected]>
> *Sent:* Friday, October 17, 2025 8:54 AM
> *To:* Aseem Choudhary (asechoud) <[email protected]>;
> Kausik Majumdar <[email protected]>; Linda
> Dunbar <[email protected]>; Yingzhen Qu <[email protected]>;
> RTGWG <[email protected]>; [email protected]
> *Subject:* Re: [External] : RE: IPR call for
> draft-ietf-rtgwg-multisegment-sdwan
>
>
>
> I would like to change my response to:
>
>
>
> I am not aware of any more IPR besides the ones already disclosed at IETF
>
>
>
> Thanks,
>
> Aseem
>
> *From: *Aseem Choudhary (asechoud) <[email protected]>
> *Date: *Tuesday, October 14, 2025 at 5:09 PM
> *To: *Kausik Majumdar <[email protected]>,
> Linda Dunbar <[email protected]>, Yingzhen Qu <
> [email protected]>, RTGWG <[email protected]>,
> [email protected] <
> [email protected]>
> *Subject: *[rtgwg] Re: [External] : RE: IPR call for
> draft-ietf-rtgwg-multisegment-sdwan
>
> No, I'm not aware of any IPR that applies to this draft
>
>
>
> Thanks,
>
> Aseem
>
>
>
> *From: *Kausik Majumdar <[email protected]>
> *Date: *Monday, October 13, 2025 at 2:10 PM
> *To: *Linda Dunbar <[email protected]>, Yingzhen Qu <
> [email protected]>, RTGWG <[email protected]>,
> [email protected] <
> [email protected]>
> *Subject: *[rtgwg] Re: [External] : RE: IPR call for
> draft-ietf-rtgwg-multisegment-sdwan
>
> Yes, I am aware of an IPR that is associated with this Draft and the IPR
> has been disclosed in compliance with IETF IPR rules.
>
>
>
> Thanks,
>
> Kausik
>
>
>
> *From:* Linda Dunbar <[email protected]>
> *Sent:* Monday, October 13, 2025 11:35 AM
> *To:* Yingzhen Qu <[email protected]>; RTGWG <[email protected]>;
> [email protected]
> *Subject:* [External] : RE: IPR call for
> draft-ietf-rtgwg-multisegment-sdwan
>
>
>
> Yes, I'm aware of an IPR that has been disclosed in compliance with IETF
> IPR rules.
>
>
>
> Linda
>
>
>
> *From:* Yingzhen Qu <*[email protected] <[email protected]>*>
> *Sent:* Monday, October 13, 2025 11:17 AM
> *To:* RTGWG <*[email protected] <[email protected]>*>; 
> *[email protected]
> <[email protected]>*
> *Subject:* IPR call for draft-ietf-rtgwg-multisegment-sdwan
>
>
>
> Hi,
>
>
>
> In preparation for the WGLC of draft-ietf-rtgwg-multisegment-sdwan, we'd
> like all authors and contributors to confirm on the list that they are in
> compliance with IETF IPR rules.
>
>
>
> There are currently three IPR disclosures of this draft: 
> *https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-rtgwg-multisegment-sdwan
>  
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-rtgwg-multisegment-sdwan__;!!ACWV5N9M2RV99hQ!KwKnOoZtsW_mGi0bzylEVtVKLT7p_ndTPXUEbwjhJaAL9KMsZiHMNckZOtKCFB6_r3XBJf5mxEuHe92X743gipWSQeDfaw$>*
>
>
>
> 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.
>
> Thanks,
>
> Yingzhen
>
>
>
>
>
> Confidential – Oracle Internal
>
_______________________________________________
rtgwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to