<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, sans-serif;">I have to say that with this particular issue, I don't think it's the USPTO – there appears to be a backlog in the reviewing institutions. I dealt with one recently that took well over 6 months to get shaken loose,
and the USPTO people were very helpful when I called them. Start with Licensing & Review, and then get to the SPE. They can bump the reviewing agency.</span></div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, sans-serif;"><br>
</span></div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, sans-serif;">There is a 6 month provision after which you may have the right to transmit without FFL ... but my understanding is that you then take on the liability to determine it's not national-security technology ...</span></div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, sans-serif;"><br>
</span></div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, sans-serif;">PCT publishing etc may be behind, and you may lose the benefit of timely ISR/WO and/or the ability to pursue a Chapter II Demand (if desired), but as long as they get it out by 30 months there shouldn't be a problem
with national phase.</span></div>
<div id="Signature"></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Pct <pct-bounces@oppedahl-lists.com> on behalf of Carl Oppedahl via Pct <pct@oppedahl-lists.com><br>
<b>Sent:</b> Monday, February 12, 2024 6:39 PM<br>
<b>To:</b> For users of the PCT and ePCT. This is not for laypersons to seek legal advice. <pct@oppedahl-lists.com><br>
<b>Cc:</b> Carl Oppedahl <carl@oppedahl.com><br>
<b>Subject:</b> [Pct] security review delays (was Re: USPTO - Slower than usual)</font>
<div> </div>
</div>
<div>
<div class="x_moz-cite-prefix">On 2/12/2024 5:29 PM, Wanda T. Kellar via Pct wrote:<br>
</div>
<blockquote type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal}
.x_MsoChpDefault
{font-family:"Calibri",sans-serif}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-size:14.0pt; color:black">What has gotten into the USPTO?</span></p>
[...]<span style="font-size:14.0pt; color:black"></span>
<p class="x_MsoListParagraph" style="text-indent:-.25in"><span style="font-size:14.0pt; color:black"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:14.0pt; color:black">Several PCT applications filed, and 6 months later, they are still under secrecy review.</span></p>
</div>
</blockquote>
<p>This problem is largely within the practitioner's power to avoid. Simply file in RO/IB instead of RO/US.</p>
<p>First, if the invention was not made in the US, you don't need an FFL to satisfy US security requirements anyway, so file in RO/IB.</p>
<p>Even if the invention was made in the US, barring some surprise you already had an FFL in your US priority document. That FFL makes it okay to file in RO/IB (assuming that you did not add significant new matter).
<br>
</p>
<p>Even if you added significant new matter, just plan ahead by a week or two, and file the text of the to-be-filed PCT as a US provisional, and likely as not you will seen an FFL in that filing receipt. If so, then that makes it okay to file in RO/IB. And
also gives you a potent rules-based-IBR benefit.</p>
<p>See session 14 at <a class="x_moz-txt-link-freetext" href="https://blog.oppedahl.com/the-2022-schwegman-advanced-pct-training/" originalsrc="https://blog.oppedahl.com/the-2022-schwegman-advanced-pct-training/" shash="w9n9Qdl3LX0OeTz+1OTM9cv3OS8kMzxb4I/DMtatQTfz+tt25tvBXx4Hbpa6j1XSALm6kkkGhj7eyFlvDnfvJETSu4eP/GgoUcJvQ5aGkRIoUaTtDwH6RTngQndHwFy6chhZh5Xq059dvZdtZBCM8CUq/jByvuAonYOE+tvojfI=">
https://blog.oppedahl.com/the-2022-schwegman-advanced-pct-training/</a> . Free of charge.</p>
<p><br>
</p>
</div>
</body>
</html>