Invalidity dossier

US 5777989

TCP/IP host name resolution for machines on several domains

Current assignee: International Business Machines Corp

Added 9/21/2026, 10:20:58 AM

At a glanceNo PTAB challengesNo litigation on file

Active provider: DeepSeek · deepseek-flash

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

Patent Overview — US 5,777,989

Title: TCP/IP host name resolution for machines on several domains

Assignee: International Business Machines Corp. (IBM), original assignee; inventor John Ryan McGarvey.

Dates: Priority/filing date 1995-12-19; publication/grant 1998-07-07; anticipated expiration 2015-12-19. Status listed as "Expired – Lifetime" (a legal-status assumption, not a legal conclusion).

Purpose: TCP/IP name resolution conventionally assumes a host connects to a single domain whose name servers can resolve all hosts on the network — an assumption stated in RFC 1034, section 2.4. That assumption fails when a host is simultaneously connected to multiple domains (e.g., a private network and the Internet), because each domain's name servers cannot resolve names in the other. The invention remedies this by enhancing TCP/IP address resolution so a host attached to several domains can resolve destination addresses across them.

Plain-language scope: The local host is configured with two or more primary domain name servers, one per connected domain, with server names kept in lists (primary first, alternates following). Resolution requests are sent simultaneously to the primary servers in all domains; if any queried server returns a positive response, the corresponding address is used. The enhancement preserves standard name resolution processing (short names concatenated with configured domain names into fully qualified names), leaves the name resolution packet format unchanged, works with existing networks and servers, and supports existing RFC 1034 query types (name-to-address, address-to-name, MX/mail resolution). Queries may be carried via TCP virtual circuits, UDP datagrams, or other packets.

What the excerpt does not establish: It does not provide the full claims, complete description, or drawing contents; details of omitted text; any prosecution history; validity, enforceability, or infringement analysis; litigation; ownership transfers beyond the recorded IBM assignment; or prior-art comparisons. No such matters are asserted here.

Source: https://patents.google.com/patent/US5777989/en

Generated 10/1/2026, 10:01:46 PM

Cases on file (0)

Specific litigation cases in our database that name US patent 5777989. The free-form analysis below may also discuss cases beyond this list.

No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.

Litigation summary

Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.

Log in to generate
Not generated yet. Log in to request this analysis.

Proceedings on file (0)

All PTAB activity →

AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.

No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.

PTAB challenges

AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.

Log in to generate
Not generated yet. Log in to request this analysis.

Assignment history

Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.

Log in to generate
Not generated yet. Log in to request this analysis.

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

Log in to generate
Not generated yet. Log in to request this analysis.

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Log in to generate
Not generated yet. Log in to request this analysis.

Extensions

Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.

Log in to generate
Not generated yet. Log in to request this analysis.

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

Log in to generate
Not generated yet. Log in to request this analysis.