Data Discovery Problem Statement
draft-mcbride-data-discovery-problem-statement-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-10
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                                                 Futurewei
Intended status: Standards Track                             D. Kutscher
Expires: January 11, 2021                               Emden University
                                                             E. Schooler
                                                                   Intel
                                                           CJ. Bernardos
                                                                    UC3M
                                                                D. Lopez
                                                          Telefonica I+D
                                                           July 10, 2020

                    Data Discovery Problem Statement
           draft-mcbride-data-discovery-problem-statement-00

Abstract

   If data is the new oil of the 21st century, then we need a
   standardized way of locating, capturing, classifying and transforming
   this raw data to generate insights and recommendations.  Data, like
   oil, needs to be discovered and captured in order to be refined and
   valuable.  While the topic of data discovery can be far reaching,
   this document focuses on the problem of actually locating data,
   throughout a network of data servers, in a standardized way.

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."

   This Internet-Draft will expire on January 11, 2021.

Copyright Notice

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

McBride, et al.         Expires January 11, 2021                [Page 1]
Internet-Draft      Data Discovery Problem Statement           July 2020

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Problem Scope . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Existing Solutions  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Proprietary . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Opensource  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   There are myriad proprietary and standardized ways of discovering
   networking devices and hosts.  There are many solutions for
   discovering data within a database.  There are proprietary, non-
   standardized, ways of discovering the data that may be stored
   throughout an environment of networking devices.  We can discover
   information about the devices but can't locate and capture stored
   data in a standard way.  With more networking devices storing
   collected data there needs to be a standard way of discovering the
   specific data needed amongst a potentially huge lake of databases.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  Problem Scope

   Data may be cached, copied and/or stored at multiple locations in the
   network on route to its final destination.  With an increasing
   percentage of devices connecting to the Internet being mobile,

McBride, et al.         Expires January 11, 2021                [Page 2]
Show full document text