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: 2019-Feb-10
Document File: 22 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Allen: AUTHOR [+1]

Related Documents

10.17487/RFC2652: DOI

Abstract

This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 8% 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.

Allen & Mealling Standards Track [Page 1]

RFC 2652 MIME Definitions for CIP August 1999

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 interpreted as a successful operation.

Requests, responses and results are formatted as MIME [RFC2046] messages. The specific MIME types involved are defined below.

As with all MIME objects, CIP messages may be wrapped in a security multipart package to provide authentication and privacy. The security policy with respect to all messages is implementation defined, when not explicitly discussed below. CIP implementors are strongly urged to allow server administrators maximum configurability to secure their servers against malicio...

Processing...
Loading...