I have already received IPR responses from all the authors. There is no know 
IPR on the draft. 

Thanks,
Acee

> On Sep 1, 2026, at 10:42 PM, 刘莹(联通集团本部) <[email protected]> wrote:
> 
> Hi Acee,
> As a co-author of the draft "draft-he-lsr-srv6-mirror-sid-igp-encoding", I'm 
> not aware of any IPR that applies to it.
> Thanks!
>  China Unicom
> Ying Liu
>  From: Acee Lindem
> Date: 2026-08-31 23:25
> To: draft-he-lsr-srv6-mirror-sid-igp-encoding
> CC: lsr
> Subject: WG Adoption IPR Poll for "IGP Encoding for SRv6 Mirror SID in Egress 
> Protection" - draft-he-lsr-srv6-mirror-sid-igp-encoding-01
> 【本邮件为外部邮件,请注意核实发件人身份,并谨慎处理邮件内容中的链接及附件】
> Co-Authors,  Are you aware of any IPR that applies to 
> draft-he-lsr-srv6-mirror-sid-igp-encoding-01?  If so, has this IPR been 
> disclosed in compliance with IETF IPR rules  (see RFCs 3979, 4879, 3669 and 
> 5378 for more details).
>  There currently aren’t any IPR declarations on this simple protocol 
> extension - 
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-chen-lsr-prefix-extended-flags
>  If you are listed as a document author or contributor please respond
> to this email regardless of whether or not you are aware of any
> relevant IPR. *The response needs to be sent to the LSR WG mailing
> list.* The document will not advance to the next stage until a
> response has been received from each author and contributor.
>  If you are on the LSR WG email list but are not listed as an author or
> contributor, then please explicitly respond only if you are aware of
> any IPR that has not yet been disclosed in conformance with IETF rules.
>  There currently aren’t any IPR declarations on this draft.
>  
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-he-lsr-srv6-mirror-sid-igp-encoding
>  Thanks,
> Acee
>    _______________________________________________
> Lsr mailing list -- [email protected]
> To unsubscribe send an email to [email protected]


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

Reply via email to