Skip to main content

Data Discovery Use Cases

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Mike McBride , Jim Guichard , Yingzhen Qu , Thomas Hardjono , Carlos J. Bernardos
Last updated 2021-08-23 (Latest revision 2021-02-19)
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:


There needs to be a solution for locating and capturing data in a standardized way. Data may be cached, copied and/or stored at multiple locations in the network on route to its final destination. With an increasingly high volume of devices connecting to the Internet, support for network caching and replication is critical for continuous data availability. There are data repositories throughout a modern network and there needs to be a standardized way to locating the repositories and discovering the desired data within. There are several use cases which illustrate a need for a data discovery solution. An application might need to query the network to discover resources (program, service, resource) that can help the local application perform a particular task. Additionally, there could be volumes of data which needs to be searched and discovered in order to provide a result to be acted upon by the application. These are a couple of the use cases being addressed in this document.


Mike McBride
Jim Guichard
Yingzhen Qu
Thomas Hardjono
Carlos J. Bernardos

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