(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.

Publishing Venue

Related People

Abstract

Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) can be route constrained by making use of the Explicit Route Object (ERO) and related subobjects as defined in [RFC3209], [RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520], and [RFC5553]. Several documents have identified the need for attributes that can be targeted at specific hops in the path of an LSP, including [RFC6163], [WSON-SIG], [RFC7571], or [OBJ-FUN]. This document provides a generic mechanism for use by these other documents.

Country

United States

Language

English (United States)

This text was extracted from an ASCII text file.

This is the abbreviated version, containing approximately
8% of the total text.

RFC 5420 extends RSVP-TE to specify or
record generic attributes that apply
to the whole of the path of a Label Switched Path (LSP). This
document defines an extension to the RSVP Explicit Route Object
(ERO) and Record Route Object (RRO) to
allow them to specify or record
generic attributes that apply to a given hop.

Status of This
Memo

This is an Internet Standards Track
document.

This document is a product of the Internet
Engineering Task Force (IETF). It represents the consensus of the IETF
community. It has received public review and has been
approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section
2 of RFC 5741.

Information about the current status of this
document, any errata, and how to
provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7570.

Copyright Notice

Copyright (c) 2015 IETF Trust and the
persons identified as the document
authors. All rights reserved.

This document is subject to BCP 78 and the
IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in
effect on the date of publication of
this document. Please review these
documents carefully, as they describe
your rights and restrictions with respect
to this document. Code Components
extracted from this document must
include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the
Simplified BSD License.