Lines Matching refs:to
16 This memo explains extensions to the memcache binary protocol for use
37 time. It is inappropriate to use Internet-Drafts as reference
38 material or to cite them other than as "work in progress."
47 This document is subject to BCP 78 and the IETF Trust's Legal
48 Provisions Relating to IETF Documents
52 to this document. Code Components extracted from this document must
90 Sites may find that, due to their network architecture or application
95 It is a goal of this document to provide sufficient information in
96 each UDP packet as to avoid any requirement for statefulness on the
104 document are to be interpreted as described in [KEYWORDS].
164 and a Message ID corresponding to its Get request, shall then know
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
206 information in each Get Range extras to construct an appropriately
256 Bradner, S., "Key words for use in RFCs to Indicate
260 Bradner, S., "Key words for use in RFCs to Indicate