rfc2652.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   Applications which use this media type:

      This media type is used to contain information about indices and
      how they inter-operate to form meshes of index servers.

   Additional information:

      This media type is not a standalone type. It is the top level of a
      tree similar to the vnd or prs trees specified in Section 2.1 of
      RFC2048. There are four specified branches to this tree:
            application/index.cmd
            application/index.response
            application/index.obj
            application/index.vnd



Allen & Mealling            Standards Track                    [Page 15]

RFC 2652               MIME Definitions for CIP              August 1999


      Each of these branches is a tree in its own right with types
      registered below them. See those registrations for more
      information on the types allowed below those branches.


   Person & email address to contact for further information:

   Intended usage: LIMITED USE

   Author/Change controller:

Command tree

   To: [e-mail]
   Subject: Registration of MIME media type application/index.cmd

   MIME media type name: application

   MIME subtype name: index.cmd

   Required parameters: none

   Optional parameters: none

   Encoding considerations: none

   Security considerations:

      Security considerations come into play in at least the following
      two scenarios.  Indexing information can leak undesirable amounts
      of proprietary information, unless carefully controlled. At a more
      fundamental level, the CIP protocol itself requires external
      security services to operate in a safe manner. Both topics are
      covered below.

   Interoperability considerations:

      Implementors should handle unknown commands gracefully.

   Published specification:

      RFC 2652









Allen & Mealling            Standards Track                    [Page 16]

RFC 2652               MIME Definitions for CIP              August 1999


   Applications which use this media type:

      This media type is the top of a tree of media types that express
      commands between hosts that exchange indices for the purpose of
      routing referrals.

   Additional information:

      This media type is not a standalone type. It is the top of a tree
      similar to the vnd and prs trees specified in Section 2.1 of
      RFC2048. Types registered within this tree are limited to being
      commands as specified in the document(s) referenced in the
      "Published specifications" section.

   Person & email address to contact for further information:

   Intended usage: LIMITED USE

   Author/Change controller:

Response tree

   To: [e-mail]
   Subject: Registration of MIME media type application/index.response

   MIME media type name: application

   MIME subtype name: index.response

   Required parameters: code

   Optional parameters: none

   Encoding considerations: none

   Security considerations:

      Security considerations come into play in at least the following
      two scenarios.  Indexing information can leak undesirable amounts
      of proprietary information, unless carefully controlled. At a more
      fundamental level, the CIP protocol itself requires external
      security services to operate in a safe manner. Both topics are
      covered below.

   Interoperability considerations:

      Implementors should handle unknown responses gracefully.




Allen & Mealling            Standards Track                    [Page 17]

RFC 2652               MIME Definitions for CIP              August 1999


   Published specification:

      RFC 2652

   Applications which use this media type:

      This media type is used to encode responses to CIP commands passed
      between hosts that exchange indices for the purpose of routing
      referrals.

   Additional information:

      This media type _is_ a standalone type. The code parameter
      contains the specific response code as specified by Appendix B of
      the specification document.

   Person & email address to contact for further information:

   Intended usage: LIMITED USE

   Author/Change controller:

Index Object tree

   To: [e-mail]
   Subject: Registration of MIME media type application/index.obj

   MIME media type name: application

   MIME subtype name: index.obj

   Required parameters: type, dsi, base-uri

   Optional parameters: none

   Encoding considerations: none

   Security considerations:

      Security considerations come into play in at least the following
      two scenarios.  Indexing information can leak undesirable amounts
      of proprietary information, unless carefully controlled. At a more
      fundamental level, the CIP protocol itself requires external
      security services to operate in a safe manner. Both topics are
      covered below.






Allen & Mealling            Standards Track                    [Page 18]

RFC 2652               MIME Definitions for CIP              August 1999


   Interoperability considerations:

      Implementors should handle unknown index objects according to
      rules specified in the published specification.

   Published specification:

      RFC 2652

   Applications which use this media type:

      This media type is the top of a tree of media types that express
      indexes that are exchanged between hosts that operate within a
      referral mesh.

   Additional information:

      This media type is not a standalone type. It is the top of a tree
      similar to the vnd and prs trees specified in Section 2.1 of
      RFC2048. Types registered within this tree are limited to being
      representations of indexes that contain some summary of the data
      found in some database and is used to generate referrals as
      specified in the above specified publication.

   Person & email address to contact for further information:

   Intended usage: LIMITED USE

   Author/Change controller:

Vendor tree

   To: [e-mail]
   Subject: Registration of MIME media type application/index.vnd

   MIME media type name: application

   MIME subtype name: index.vnd

   Required parameters: none

   Optional parameters: none

   Encoding considerations: none







Allen & Mealling            Standards Track                    [Page 19]

RFC 2652               MIME Definitions for CIP              August 1999


   Security considerations:

      Security considerations come into play in at least the following
      two scenarios.  Indexing information can leak undesirable amounts
      of proprietary information, unless carefully controlled. At a more
      fundamental level, the CIP protocol itself requires external
      security services to operate in a safe manner. Both topics are
      covered below.

   Interoperability considerations:

      Implementors should handle unknown objects gracefully.

   Published specification:

      RFC 2652

   Applications which use this media type:

      This media type is the top of a tree of media types that express
      vendor specific extensions to the framework specified in the
      published specifications.

   Additional information:

      This media type is not a standalone type. It is the top of a tree
      similar to the vnd and prs trees specified in Section 2.1 of
      RFC2048. Types registered within this tree are limited to being
      vendor specific extensions to the CIP framework as specified in
      the publications. Any registrations within this tree are still
      limited to dealing with indexes, meshes and referrals.

   Person & email address to contact for further information:

   Intended usage: LIMITED USE

Appendix B: Response Codes

   The meaning of the various digits in the response codes is discussed
   in RFC-821, Appendix E.

   The following response codes are defined for use by CIPv3 servers.
   Implementors must use these exact codes; undefined codes should be
   interpreted by CIP servers as fatal protocol errors.  Instead of
   defining new codes for unforeseen situations, implementors must adapt
   one of the given codes. The implementation should attach a useful
   alternative comment to the reused response code.




Allen & Mealling            Standards Track                    [Page 20]

RFC 2652               MIME Definitions for CIP              August 1999


      Code    Suggested description text
              Sender-CIP action
      --------------------------------------------------------
      220     Initial server banner message

      300     Requested CIP version accepted
              Continue with CIP transaction, in the specified
              version.

      222     Connection closing (in response to sender-CIP close)
              Done with transaction.

      200     MIME request received and processed
              Expect no output, continue session (or close)

      201     MIME request received and processed, output follows
              Read a response, delimited by SMTP-style message
              delimiter.

      400     Temporarily unable to process request
              Retry at a later time. May be used to indicate
              that the server does not currently have the
              resources available to accept an index.

      500     Bad MIME message format
              Retry with correctly formatted MIME request.

      501     Unknown or missing request in application/index.cmd
              Retry with correct CIP command.

      502     Request is missing required CIP attributes
              Retry with correct CIP attributes.

      520     Aborting connection for some unexpected reason
              Retry and/or alert local administrator.

      530     Request requires valid signature
              Sign the request, if possible, and retry.
              Otherwise, report problem to the administrator.

      531     Request has invalid signature
              Report problem to the administrator.


      532     Cannot check signature
              Alert local administrator, who should cooperate with
              remote administrator to diagnose and resolve the
              problem. (Probably missing a public key.)



Allen & Mealling            Standards Track                    [Page 21]

RFC 2652               MIME Definitions for CIP              August 1999


5.  Full Copyright Statement

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Allen & Mealling            Standards Track                    [Page 22]