I’m not aware of any applicable IPR.
Thanks.

From: Mach Chen <[email protected]>
Date: Wednesday, 13 May 2026 at 05:06
To: Alvaro Retana <[email protected]>; 
[email protected] 
<[email protected]>
Cc: [email protected] <[email protected]>; spring Chairs <[email protected]>
Subject: RE: IPR Declaration for draft-ietf-spring-sr-redundancy-protection 
(WGLC)

Hi,

I am not aware of any undisclosed IPR that applies to the document.

Best regards,
Mach

From: Alvaro Retana <[email protected]>
Sent: Friday, May 8, 2026 5:35 AM
To: [email protected]
Cc: [email protected]; spring Chairs <[email protected]>
Subject: IPR Declaration for draft-ietf-spring-sr-redundancy-protection (WGLC)

Dear authors and contributors:

In preparation for a WGLC, we’re starting this IPR check. Receiving replies 
from all authors and contributors is a prerequisite before the start of the 
WGLC.

Are you aware of any IPR that applies to this draft?

If so, has it been disclosed in compliance with IETF IPR rules?  See BCP78 and 
BCP79 for more details.  For any undisclosed IPR, please provide any additional 
information 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 proceed to the next stage only after 
receiving a response from each listed author and contributor.


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 encourage you to notify the IETF if you are aware of IPR that may 
be related to this document or to refrain from participating in any 
contribution or discussion related to your undisclosed IPR.  For more 
information, please see https://www.ietf.org/standards/ipr/

Thank you,

Alvaro (for the spring-chairs)

_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to