[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    Re: [Lsr] IPR Poll for Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsen
From:       Gyan Mishra <hayabusagsm () gmail ! com>
Date:       2023-08-30 4:33:02
Message-ID: CABNhwV2tmEJwy9E3O3dkb7Z8UEZXsPwsJJJqN=6Urrz5faJdKg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I am not aware of any undisclosed IPRs.

Thanks

Gyan

On Wed, Aug 23, 2023 at 4:02 PM Acee Lindem <acee.ietf@gmail.com> wrote:

> Co-Authors,
>
> Are you aware of any IPR that applies to
> draft-posenak-lsr-igp-ureach-prefix-announce-04?
> If so, has this IPR been disclosed in compliance with IETF IPR rules  (see
> RFCs 3979, 4879, 3669 and 5378 for more details).
>
> There are a few IPR statements already -
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-lsr-dynamic-flooding
>
> 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.
>
> Also, since there are nine authors, it would be great if you could reduce
> the author list and make
> the others contributors (which still requires an IPR response).
>
> Thanks,
> Acee
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

[Attachment #5 (text/html)]

<div dir="auto">I am not aware of any undisclosed IPRs.</div><div \
dir="auto"><br></div><div dir="auto">Thanks  </div><div dir="auto"><br></div><div \
dir="auto">Gyan</div><div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, Aug 23, 2023 at 4:02 PM Acee Lindem &lt;<a \
href="mailto:acee.ietf@gmail.com">acee.ietf@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Co-Authors, <br> <br>
Are you aware of any IPR that applies to \
draft-posenak-lsr-igp-ureach-prefix-announce-04? <br> If so, has this IPR been \
disclosed in compliance with IETF IPR rules   (see RFCs 3979, 4879, 3669 and 5378 for \
more details).<br> <br>
There are a few IPR statements already - <a \
href="https://datatracker.ietf.org/ipr/search/?submit=draft&amp;id=draft-ietf-lsr-dynamic-flooding" \
rel="noreferrer" target="_blank">https://datatracker.ietf.org/ipr/search/?submit=draft&amp;id=draft-ietf-lsr-dynamic-flooding</a><br>
 <br>
If you are listed as a document author or contributor please respond<br>
to this email regardless of whether or not you are aware of any<br>
relevant IPR. *The response needs to be sent to the LSR WG mailing<br>
list.* The document will not advance to the next stage until a<br>
response has been received from each author and contributor.<br>
<br>
If you are on the LSR WG email list but are not listed as an author or<br>
contributor, then please explicitly respond only if you are aware of<br>
any IPR that has not yet been disclosed in conformance with IETF rules.<br>
<br>
Also, since there are nine authors, it would be great if you could reduce the author \
list and make<br> the others contributors (which still requires an IPR response). \
<br> <br>
Thanks,<br>
Acee<br>
_______________________________________________<br>
Lsr mailing list<br>
<a href="mailto:Lsr@ietf.org" target="_blank">Lsr@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/lsr" rel="noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/lsr</a><br> \
</blockquote></div></div><span class="gmail_signature_prefix">-- </span><br><div \
dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div \
dir="ltr"><div dir="ltr"><div><p style="color:rgb(34,34,34)"><a \
href="http://www.verizon.com/" \
style="color:rgb(17,85,204);padding-bottom:1em;display:inline-block" \
target="_blank"><img src="http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email" \
width="81" height="18" style="height:18px;width:81px"></a><br></p><p \
style="font-size:1em;margin:0px;font-family:&quot;Verizon NHG \
DS&quot;,Arial,sans-serif;line-height:13px;color:black"><b>Gyan Mishra</b></p><p \
style="color:rgb(34,34,34);margin:0px;line-height:13px"><font face="georgia, serif" \
style="color:black;font-size:1em"><i>Network Solutions A</i></font><font \
color="#000000" face="georgia, serif"><i>rchitect  </i></font></p><p \
style="color:rgb(34,34,34);margin:0px;line-height:13px"><i \
style="color:rgb(0,0,0);font-size:13px"><font face="georgia, serif">Email <a \
href="mailto:gyan.s.mishra@verizon.com" \
target="_blank">gyan.s.mishra@verizon.com</a></font></i><font color="#000000" \
face="georgia, serif"><i><br></i></font></p><p \
style="font-size:1em;margin:0px;line-height:13px;color:black"><i><font face="georgia, \
serif">M 301 502-1347<br><br></font></i></p></div><div><br></div></div></div></div></div></div></div></div></div>




_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic