December 25 is a holiday at the USPTO

Wednesday, December 25, 2019 will be a federal holiday in the District of Columbia.  This means the USPTO will be closed.  This means that any action that would be due at the USPTO on December 25 will be timely if it is done by Thursday, December 26, 2019.

The PCT in 2019: an end of the year update from WIPO

(You can see the slides here.)

(Updated to include some of the topics.)

It has just now been announced that in just about 24 hours, Matthias Reischle-Park of WIPO will deliver a free-of-charge webinar entitled:

The PCT in 2019: end of the year update

I have learned informally what some of the topics will be:

  • Rule changes (in force and coming next year)
  • color drawings
  • best ways to contact the IB without relying on fax
  • collaborative search
  • WIPO IP Portal

I gather it will last about an hour.  My guess is that if you are a PCT enthusiast or power user, you should attend.  I plan to attend.

To register for the webinar, click here.

Listserv update – I turned on “munging”

(Update:  See a followup message here about a step that you might take to try to get the listservs working for you again.)

For those who are following my travails trying to get ISPs to accept our listserv email messages now that we are on our dedicated server (original post and update) … this posting about “munging” may be of interest.  Others are invited to skip this posting as being even more geeky than usual.  Continue reading “Listserv update – I turned on “munging””

Collaborative Search Pilot

click to enlarge

I am told that not very many applicants make use of the two Collaborative Search Pilot (CSP) programs at the USPTO.  Each of the programs offers a fast-track way to get a strong patent.  The more I think about CSP, the more I wonder why the programs get such little use.  In this blog article I will describe the programs and I will offer my thoughts as to how an applicant might go about deciding whether or not to make use of the programs. Finally I will mention the actual numbers of times the two CSP programs have gotten used by applicants. Continue reading “Collaborative Search Pilot”

Drawings that are good enough and then not good enough

Every month or so, in recent years, we receive from the USPTO a Notice to File Corrected Application Papers (NTFCAP) in a recently filed patent application that says our drawings are not good enough.  What we find to be frustrating and annoying about this is that invariably the application is a continuation or a divisional of an application in which the drawings were good enough. Today I filed a request to have such a Notice withdrawn.  Here is what I wrote:  Continue reading “Drawings that are good enough and then not good enough”

2020 is a leap year

2020 is a leap year.  What got me thinking about this is a sentence that I just wrote in an email message to instructing counsel in Turkey for a US case that our firm is handling:

We now have an Office Action and it is attached. To avoid abandonment a response must be made by February 29, 2020.

Which prompts a discourse on the inadequacy of integers.  All but the most diehard blog readers are invited to skip the following. Continue reading “2020 is a leap year”

Listserv update redux

click to enlarge

(Update:  See a followup message here about a step that you might take to try to get the listservs working for you again.)

(See also I turned on munging.)

(Updated to describe shipment of digital multimeters.)

Readers may recall my recent blog article about woes with outbound emails from our listserv server.

Alert listserv member Diane L. Gardner of Mastermind IP Law P.C. posted this comment to that blog article:

From my IT provider:

They do not have a spf record.

And her IT provider was absolutely right.  I had not attended to setting up an SPF record on our new dedicated server.  I ought to have done that sooner.  Prompted by her posting, we added the SPF record.  Here is the record:

v=spf1 +mx +a +ip4:162.213.248.195 ~all

We have sent two of our digital multimeters to Diane — one for her and one for her IT provider.  Thanks to both of you!

We also corrected a PTR (reverse DNS lookup) record.  The PTR record is “195.248.213.162.in-addr.arpa.” pointing to “server1.oppedahl-lists.com.”.

There’s a chance these two changes might help a little.

We already had and still have a DKIM record.  The DKIM record is “server1.oppedahl-lists.com.” pointing to “v=DKIM1; k=rsa; p=[public key]”.

Thanks again to the nice commenter.