Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

MIME Object Definitions for the Common Indexing Protocol (CIP) (RFC2652)

IP.com Disclosure Number: IPCOM000003241D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 28 page(s) / 39K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Allen: AUTHOR [+2]

Abstract

The Common Indexing Protocol (CIP) is used to pass indexing information from server to server in order to facilitate query routing. The protocol is comprised of several MIME objects being passed from server to server. This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group J. Allen

Request for Comments: 2652 WebTV Networks, Inc.

Category: Standards Track M. Mealling

Network Solutions, Inc.

August 1999

MIME Object Definitions for the Common Indexing Protocol (CIP)

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

The Common Indexing Protocol (CIP) is used to pass indexing

information from server to server in order to facilitate query

routing. The protocol is comprised of several MIME objects being

passed from server to server. This document describes the definitions

of those objects as well as the methods and requirements needed to

define a new index type.

1. Introduction

The Common Indexing Protocol (CIP) is used to pass indexes between

servers that combine multiple indexes and/or route queries based on

those indexes. The overall framework for the protocol is specified in

the CIP Framework document [FRAMEWORK]. This document should be read

within the context of that document as there are fundamental concepts

contained in the framework that are not fully explained here.

Since there are several different ways to index a given database

there will be multiple types of indexes to pass. These indexes may

have different transport requirements, different ways of specifying

parameters, and different referral rules. These different

requirements are handled by encapsulating the indexes within MIME

wrappers in order to have a standardized way to specify those

different parameters.

Appendix A contains the actual MIME [RFC2046] registration templates

sent to the IANA for registration [RFC2048].

This document uses language like SHOULD and SHALL that have special

meaning as specified in "Key words for use in RFCs to Indicate

Requirement Levels" [RFC2119].

2.0 CIP Transactions

Messages passed by CIP implementations over reliable transport

mechanisms fall into three categories: requests, responses and

results. All requests result in either a response or a result. A

result sent in response to a request must be int...