Data Discovery Use Cases
draft-mcbride-data-discovery-use-cases-00

Document Type Active Internet-Draft (individual)
Authors Mike McBride  , Jim Guichard  , Yingzhen Qu  , Thomas Hardjono  , Carlos Bernardos 
Last updated 2021-02-19
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         M. McBride
Internet-Draft                                               J. Guichard
Intended status: Informational                                     Y. Qu
Expires: August 23, 2021                                       Futurewei
                                                             T. Hardjono
                                                                     MIT
                                                           CJ. Bernardos
                                                                    UC3M
                                                       February 19, 2021

                        Data Discovery Use Cases
               draft-mcbride-data-discovery-use-cases-00

Abstract

   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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

McBride, et al.          Expires August 23, 2021                [Page 1]
Internet-Draft          Data Discovery Use Cases           February 2021

   This Internet-Draft will expire on August 23, 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Types of Data . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Application-Aware Service Function Chaining . . . . . . .   4
     5.2.  Available CPU and Memory Resources  . . . . . . . . . . .   5
     5.3.  Data Dependency . . . . . . . . . . . . . . . . . . . . .   5
     5.4.  Distributed Ledgers . . . . . . . . . . . . . . . . . . .   5
     5.5.  Edge Computing  . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   An application might need to query the network to discover resources
   that can help the local application perform a particular task.  There
   could be volumes of data which needs to be searched and discovered in
   order to provide a result to be acted upon.

   Data discovery might involve an application requesting data.  It
   might involve a device looking to store data or to request the
Show full document text