(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*

This guide provides a more detailed description of the syntax that is supported along with examples.

This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.

Concept Search - What can I type?

For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.

Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.

This memo
provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this memo is unlimited.

IESG Note

This RFC is not
a candidate for any level of Internet Standard.
The IETF disclaims any
knowledge of the fitness of this RFC for any
purpose and in particular notes that the decision to publish is not based on IETF review for such things as
security, congestion control, or
inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its
discretion. Readers of this document should exercise caution in
evaluating its value for
implementation and deployment.
See RFC 3932 for more information.

Abstract

This document
describes a Cisco Systems protocol that can be used to detect and disable unidirectional Ethernet
fiber or copper links caused, for
instance, by mis-wiring of fiber strands, interface malfunctions, media converters' faults,
etc. It operates at Layer 2 in conjunction with IEEE 802.3's existing
Layer 1 fault detection mechanisms.

This document
explains the protocol objectives and applications, illustrates the specific premises the
protocol was based upon, and describes
the protocol architecture and related deployment issues to serve as a possible base for future
standardization.