Lines Matching refs:of

25 Status of This Memo
28    provisions of BCP 78 and BCP 79.
30    Internet-Drafts are working documents of the Internet Engineering
32    working documents as Internet-Drafts.  The list of current Internet-
35    Internet-Drafts are draft documents valid for a maximum of six months
49    (http://trustee.ietf.org/license-info) in effect on the date of
50    publication of this document.  Please review these documents
61    include Simplified BSD License text as described in Section 4.e of
65 Table of Contents
92    needs.  This document provides extensions and descriptions of use of
95    It is a goal of this document to provide sufficient information in
97    part of the server nor significant caching of outstanding packets on
98    the part of the client.
144    This section extends the behavior of the Get and GetQ commands as
147    When a Get or GetQ request is made via UDP, and the value of the key
150    counted), a Get Range response packet MUST be sent instead of the Get
153    1.  The Status field of the response header MUST be 0x0004.
154    2.  The Offset field of the GetR response extras MUST be 0.
155    3.  The Length field of the GetR response extras, and the data
156        contained in the Value field of the packet, SHOULD be the maximum
157        allowed length of a UDP packet, less the space required by the
160    4.  The Total value length field of the response extras MUST be the
161        actual length of the complete value.
163    The client, upon receipt of a Get Range response bearing Status 0x004
173    that it has received only the first portion of the value.  The client
174    MAY choose to request the remaining portion of the value by sending
180    transport to request byte ranges of the value for a key.  In the
181    event that the Data version check fails to match that of the key, an
204    transport to indicate the location of the bytes of the value for a
207    sized buffer in its own memory and blindly insert the contents of the