Posts

Posted on

Listervs have been migrated to a new server

(Update:  Microsoft is behaving badly about this.  See blog article.)

Hello to the members of the various listservs hosted by Oppedahl Patent Law Firm LLC.   Yesterday I migrated the listservs to a new server.  For many members of the listservs, hopefully this will go largely unnoticed after a few test postings of yesterday and today.  But for some members, this will be extra work and trouble.  I am sorry about this.

Here are details.

Whitelisting.  Previously the listservs were on a server at IP address 162.255.116.157.  Now the listservs are on a server at IP address 66.29.132.148.  Maybe you had previously set up a whitelisting entry in your email system to allow messages from 162.255.116.157 to reach you.  If so, you may find that now you need to set up a whitelisting entry in your email system to allow messages from 66.29.132.148 to reach you.  (Update:  Microsoft is behaving badly about this.  See blog article.)

Member password.  This migration caused a reset of your password for your subscription to the listserv.   To get your password figured out again, you might find it necessary to go to one of the eleven links below (for the listserv that you need to reset the password in) and click on the link, and follow the process for resetting your password.

Digest numbering.  If you are a digest subscriber, you will see that this migration has reset the digest numbering to volume 1.

I am sorry about the extra work and trouble.

Links to user information pages for the listservs.  The listservs affected by this server migration include:

Posted on

USPTO quietly fixes Patent Center bug CP31

click to enlarge

(Update:  shortly after this blog post, a nice person at the USPTO got in touch.)

Today, the USPTO quietly fixed Patent Center bug CP31.  For more than three years, this bug was a trap for the unwary user (blog article, June 23, 2020).  The user who made the mistake of checking for outgoing correspondence using Patent Center rather than PAIR ran the risk of malpractice in two distinct ways:

    • If the user were to check for outgoing correspondence on a Monday or a Tuesday, the Patent Center report would always state that there is no outgoing correspondence even if, in truth, there was outgoing correspondence.
    • On other days of the week, on average the Patent Center report would be missing about 11% of the user’s outgoing correspondence.

Continue reading “USPTO quietly fixes Patent Center bug CP31”

Posted on

Will the USPTO cut deep grooves in the airport runways?

When the City of Denver sold the bonds that would pay for the construction of Denver International Airport (to replace Stapleton airport), there was language in the bonds that imposed a contractual obligation:  on the day that DIA was placed into service, deep grooves would be cut into each of the runways at Stapleton.  Continue reading “Will the USPTO cut deep grooves in the airport runways?”

Posted on

NAPP will meet with USPTO people on Monday about Patent Center

Update:  the meeting took place (blog article).

The USPTO’s planned shutdown of PAIR and EFS-Web will be this coming Tuesday, November 7 at 11:59 PM Eastern Time (see countdown clock).  The National Association of Patent Practitioners (NAPP) wrote a letter to USPTO Director Kathi Vidal on October 31, 2023 (blog article), asking the USPTO to postpone the shutdown of PAIR and EFS-Web.  In response to this letter, Commissioner for Patents Vaishali Udupa has invited NAPP to meet with her and her colleagues about Patent Center on Monday, November 6.  Others attending from the USPTO will be Deputy Commissioner for Patent Administration Richard Seidel, Richard Fernandez, and Tony Uranga.  Attending on behalf of NAPP will be its president, Rich Baker, and its vice president, Dan Smith.  The meeting will take place at 11AM Eastern Time.

It will be fascinating to hear about the results of the meeting.

Posted on

USPTO leadership will, I predict, take corrective action

(Update:  USPTO leadership has, indeed, taken corrective action (blog article).)

It crosses my mind that this kind of thing with the EBC telling people that Patent Center is not ready (see blog article) will very likely lead to a corrective action by USPTO leadership. No, I do not mean that USPTO leadership will postpone the shutdown of PAIR and EFS-Web (now planned for November 8) until Patent Center is “ready”. Nor do I mean that USPTO leadership will actually do the hard work of making Patent Center “ready” between now and November 8. I mean that a memo will get circulated to the representatives at the EBC, telling them that between now and November 8, no user is to be told that the workaround for a Patent Center bug is to “use PAIR instead” or “use EFS-Web instead”.

Posted on

EBC even now tells users to use EFS-Web as workaround for Patent Center bugs

Okay, folks, let’s try to figure out if Patent Center is actually “ready” so that the USPTO can shut down PAIR and EFS-Web.  The USPTO decisionmakers have made it very clear that the views of actual USPTO customers (many of whom say the answer is “no”) are not to be credited on this point.    But suppose there were an actual USPTO employee who communicates, by the employee’s own words and actions, that they do not think Patent Center is “ready”.  Would that be enough to convince the USPTO decisionmakers otherwise?

On October 31, 2023, USPTO customer Victoria O’Conner was trying to file a PCT application in Patent Center.  But Patent Center stopped working at the fee payment selection page.  So she called the EBC.  The EBC representative said “use EFS-Web instead”.    This was EBC ticket number 1-842304670.  This is also CP ticket number CP176.

Posted on

Welcome back to blog subscribers

Hello readers!  The server that hosts this blog got hacked on October 18, during the time that I was in Washington DC for the face-to-face meeting (blog article) with USPTO people on the topic of Patent Center.  When I returned to home after these travels, I set to work dealing with the hack.  The recovery plan that I eventually arrived at was to set up a new hosting server with the plan of shutting down the old hosting server.  It was quite a lot of work to migrate all of the systems that had been on the old server, over to the new server, keeping in mind that it was very important to be extremely careful to ensure that the only stuff to be be migrated from the old server was content and not any executable code.  It meant that every instance of executable code needed to be rebuilt from scratch, from trusted sources.  And a number of new and additional protective measures needed to be in place on the new server.  And everything needed to be tested.

The way that this affects you, dear reader, is that if you are one of the thousands of subscribers to this blog, you did not get notified by email of any new blog posts after October 18.  It was just today that I successfully migrated the subscriber list over from the old (compromised) server to the new server.  So it is only today that you, as a subscriber, will resume being notified by email of new blog posts.

And this means that you did not get notified of the following nine blog posts that happened after October 18.  So here is a blog post to identify the blog posts that you did not get notified about.