Computing at the edge
draft-nordmark-t2trg-computing-edge-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                        E. Nordmark
Internet-Draft                                                    Zededa
Intended status: Standards Track                        October 22, 2018
Expires: April 25, 2019

                         Computing at the edge
                 draft-nordmark-t2trg-computing-edge-00

Abstract

   There has been some discussion about edge computing in the T2TRG.
   This note explores the edge from a computing perspective, and from
   that suggests aspects of networking that relate to edge computing.
   It includes some potential research problems for networking edge
   computing.

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 http://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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (http://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.

Nordmark                 Expires April 25, 2019                 [Page 1]
Internet-Draft                idloc privacy                 October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  What is computing?  . . . . . . . . . . . . . . . . . . . . .   2
   3.  What is edge? . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Why edge computing? . . . . . . . . . . . . . . . . . . . . .   4
   5.  Networking for Edge Computing . . . . . . . . . . . . . . . .   5
   6.  Application connectivity  . . . . . . . . . . . . . . . . . .   5
   7.  Potential research topics . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. Informative References  . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Edge computing has gained increased interest industry over the last
   few years and there has already been some discussion in the IETF and
   IRTF as exemplified by [I-D.zhang-iiot-edge-computing-gap-analysis],
   [I-D.hong-iot-edge-computing], and
   [I-D.geng-iiot-edge-computing-problem-statement].  This note builds
   on that work while taking a step back from the networking aspects to
   look at how computing would happen at the edge and what is needed to
   satisfy that computing.  The note also tries to separate out the
   motivations for computing edge from the attributes of the edge.

2.  What is computing?

   The general notion of computing is likely to be clear; some
   programmable ability in the form of CPU/GPU plus some memory, with
   some ability to interact with the external word (I/O, networking),
   with optional ability to store data locally with persistence.

   However, it might be useful to try to separate the flexibility of
   edge computing from fixed function devices which do not have the
   capacity or flexibility to perform other functions than envisioned
   prior to their deployment.  Such fixed function devices still require
   a software/firmware update capability as discussed in [RFC8240], but
   they do not require handling new application deployment and
   associated new communication patterns.

   These more flexible devices are likely to be larger than the class 2
   devices defined in [RFC7228], however if applications are
   sufficiently small, constrained devices might very well be edge
   computing devices.  But in general it makes sense to think about
   devices of the Raspberry Pi class and larger.

Nordmark                 Expires April 25, 2019                 [Page 2]
Internet-Draft                idloc privacy                 October 2018

   If the set of applications which might be deployed on a device isn't
   known prior to deployment it might be difficult to determine a
Show full document text