Skip to main content

The Series Transfer Pattern (STP)

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Carsten Bormann , Klaus Hartke
Last updated 2020-10-09 (Latest revision 2020-04-07)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Many applications make use of Series of data items, i.e., an array of data items where new items can be added over time. Where such Series are to be made available using REST protocols such as CoAP or HTTP, the Series has to be mapped into a structure of one or more resources and a protocol for a client to obtain the Series and to learn about new items. Various protocols have been standardized that make Series-shaped data available, with rather different properties and objectives. The present document is an attempt to extract a common underlying pattern and to define media types and an access scheme that can be used right away for further protocols that provide Series-shaped data.


Carsten Bormann
Klaus Hartke

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)