Opposition 91234514
OtherUSPTO
Opposition 91234514 at USPTO between CamelBak Products, LLC and Williamson-Dickie Holding Company, over the mark DUXBAK, filed May 12, 2017. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- May 12, 2017
- Marks involved
- 14
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the DUXBAK filing.
DUXBAK filed
Application 86935892 filed at the USPTO.Opposition filed
CamelBak Products, LLC started opposition 91234514 at USPTO against DUXBAK.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| DUXBAK | Contested | 86935892 | USPTO |
| CAMELBAK | Relied on | 73797876 | USPTO |
| CAMELBAK | Relied on | 74455063 | USPTO |
| THERMOBAK | Relied on | 74702135 | USPTO |
| HYDROBAK | Relied on | 75118170 | USPTO |
| CAMELBAK | Relied on | 77067406 | USPTO |
| HYDROBAK | Relied on | 77067644 | USPTO |
| RACEBAK | Relied on | 77473466 | USPTO |
| ARMORBAK | Relied on | 77519530 | USPTO |
| CAMELBAK | Relied on | 78621408 | USPTO |
| BAK | Relied on | 85778301 | USPTO |
| CAMELBAK | Relied on | 85778305 | USPTO |
+2 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_07d7f0fc-af47-41f9-8678-00688937259e
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_07d7f0fc-af47-41f9-8678-00688937259e",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91234514",
"status": "other",
"office_code": "US",
"filed_date": "2017-05-12",
"parties": [
{
"name": "CamelBak Products, LLC",
"role": "opponent"
},
{
"name": "Williamson-Dickie Holding Company",
"role": "respondent"
}
]
}