Opposition · USPTO

Opposition 91225480

OtherUSPTO

Opposition 91225480 at USPTO between Digi International Inc. and Digifense LLC, over the mark DIGIFENSE, filed Dec 22, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 22, 2015
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

Digi International Inc.

Company trademarks
Respondent

Digifense LLC

Timeline

How the case has moved

Dates from the USPTO record and the DIGIFENSE filing.

  1. DIGIFENSE filed

    Application 86591689 filed at the USPTO.
  2. Opposition filed

    Digi International Inc. started opposition 91225480 at USPTO against DIGIFENSE.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

MarkRoleApplicationOffice
DIGIFENSEContested86591689USPTO
DIGIBOARDRelied on74071818USPTO
DIGI INTERNATIONALRelied on74480054USPTO
DIGIRelied on74547516USPTO
DIGI CONNECTSRelied on74655746USPTO
DIGIRelied on75193524USPTO
DIGIRelied on75193725USPTO
DIGIRelied on75207246USPTO
DIGIRelied on75215067USPTO
DIGI INTERNATIONALRelied on75576649USPTO
DIGI NEORelied on76239207USPTO
DIGIRelied on76258111USPTO

+24 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_b83c3bce-71ce-40ad-a391-279936886f80
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b83c3bce-71ce-40ad-a391-279936886f80",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91225480",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-12-22",
  "parties": [
    {
      "name": "Digi International Inc.",
      "role": "opponent"
    },
    {
      "name": "Digifense LLC",
      "role": "respondent"
    }
  ]
}