RFC 2756 (rfc2756) - Page 2 of 15


Hyper Text Caching Protocol (HTCP/0



Alternative Format: Original Text Document



RFC 2756         Hyper Text Caching Protocol (HTCP/0.0)     January 2000


   1.3.  This document specifies a Hyper Text Caching Protocol (HTCP)
   which permits full request and response headers to be used in cache
   management, and expands the domain of cache management to include
   monitoring a remote cache's additions and deletions, requesting
   immediate deletions, and sending hints about web objects such as the
   third party locations of cacheable objects or the measured
   uncacheability or unavailability of web objects.

2.  HTCP Protocol

   2.1.  All multi-octet HTCP protocol elements are transmitted in
   network byte order.  All RESERVED fields should be set to binary zero
   by senders and left unexamined by receivers.  Headers must be
   presented with the CRLF line termination, as in HTTP.

   2.2.  Any hostnames specified should be compatible between sender and
   receiver, such that if a private naming scheme (such as HOSTS.TXT or
   NIS) is in use, names depending on such schemes will only be sent to
   HTCP neighbors who are known to participate in said schemes.  Raw
   addresses (dotted quad IPv4, or colon-format IPv6) are universal, as
   are public DNS names.  Use of private names or addresses will require
   special operational care.

   2.3.  HTCP messages may be sent as UDP datagrams, or over TCP
   connections.  UDP must be supported.  HTCP agents must not be
   isolated from NETWORK failures and delays.  An HTCP agent should be
   prepared to act in useful ways when no response is forthcoming, or
   when responses are delayed or reordered or damaged.  TCP is optional
   and is expected to be used only for protocol debugging.  The IANA has
   assigned port 4827 as the standard TCP and UDP port number for HTCP.

   2.4.  A set of configuration variables concerning transport
   characteristics should be maintained for each agent which is capable
   of initiating HTCP transactions, perhaps with a set of per-agent
   global defaults.  These variables are:

   Maximum number of unacknowledged transactions before a "failure" is
   imputed.

   Maximum interval without a response to some transaction before a
   "failure" is imputed.

   Minimum interval before trying a new transaction after a failure.








Vixie & Wessels               Experimental