LISP Working Group                                             S. Barkai
Internet-Draft                                                  Fermi.io
Intended status: Informational                                  F. Maino
Expires: March 28,2023                                A. Rodriguez-Natal
                                                           Cisco Systems
                                                    A. Cabellos-Aparicio
                                                   J. Paillisse Vilanova
                                       Technical University of Catalonia
                                                            D. Farinacci
                                                             lispers.net


                                                       November 23, 2022



                  Portable Edge Multipoint Sockets
                      draft-barkai-lisp-pems-03


Abstract

  This document describes the interfaces and functionality of portable
  multipoint socket objects. Each socket is instantiated per Unicast or
  Multicast Endpoint Identifiers(EID using eBPF like Unix stacks.Sockets
  are delegated and deployed across edge-compute locations for use as
  queues which assemble upstream point-to-point and multipoint-to-point
  application frames, or, as channels which segment point-to-multipoint
  and multipoint-to-multipoint application frames. Portability of queues
  and channels, traffic steering, multicast subscription and replication
  is delivered using the Locator/ID Separation Protocol (LISP).


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 February 28,2023.

Barkai, et al.           Expires March 28, 2023                [Page 1]


Internet-Draft                    LISP                    November 2022

Copyright Notice

   Copyright (c) 2022 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.  Definition of Terms . . . . . . . . . . . . . . . . . . . . . . 4
   3.  Deployment Assumptions  . . . . . . . . . . . . . . . . . . . . 5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

1.  Introduction

  This document describes the interfaces and functionality of portable
  multipoint socket objects. Each socket is instantiated per Unicast or
  Multicast Endpoint Identifiers(EID using eBPF like Unix stacks.Sockets
  are delegated and deployed across edge-compute locations for use as
  queues which assemble upstream point-to-point and multipoint-to-point
  application frames, or, as channels which segment point-to-multipoint
  and multipoint-to-multipoint application frames. Portability of queues
  and channels, traffic steering, multicast subscription and replication
  is delivered using the Locator/ID Separation Protocol (LISP).

  Distributed edge-computing and use of digital-twin constructs for
  processing physical world real-time data require new network based
  paradigms. The basic dimensions of a digital-twin constructs include:
  observable entity, instantiated digital entity, the connection between
  them, data models, raw and curated, and the services offered by twins
  as intermediate processing and data-reduction nodes.

Barkai, et al.           Expires March 28, 2023                [Page 2]


Internet-Draft                    LISP                    November 2022

  In an open field like a city, or a large network, and unlike a closed
  factory, the scale and variance between mostly active and mostly idle
  observable entities is very high. Unlike testing facilities, connected
  sensors of observed entities may be moving, observed virtual subnets
  may be moving between physical switches. Such connected sensors may be
  feeding one twin one moment, another the next.

  Dynamic conditions effect greatly the connection between the observed
  and the digital entities. Digital entities may be delegated at any
  point between edge locations in order to facilitate elasticity and
  recover from failures and disconnects. Sensors of observed entities
  and clients digital entities' services may need to switch context
  often and quickly, as well as maintain continuity when mobile access
  anchor is switched.

  Portable multipoint queues and channels address these key issues.
  Queue sockets assemble application frames from packets uploaded by
  multiple EID sources using the LISP stack. They remain reachable by
  using a re-tunneling router (RTR) configured in the socket upon
  instantiation and delegation. Assembled frames are made available from
  kernel to user space Using eBPF-Map[] type mechanisms.

  Channel sockets use eBPF-Map[] type mechanisms to receive application
  frames and group or theme EID. These frames are segmented into
  packets and transmitted using the LISP stack via their configured RTR
  for delivery using LISP signal-free (s,g) multicast [RFC8378].

 Off-Peak Socket Allocation
 Packed on less locations
   _  _    _  _
  / \/ \  / \/ \  ----
  \_/\_/  \_/\_/  ----              Peak Socket Allocation
  / \/ \  / \/ \  ----      Spread across more compute locations
  \_/\_/  \_/\_/  ----       _  _    _  _    _  _    _  _
  / \/ \  / \/ \  ----      / \/ \  / \/ \  / \/ \  / \/ \  ----
  \_/\_/  \_/\_/  ----      \_/\_/  \_/\_/  \_/\_/  \_/\_/  ----
  / \/ \  / \/ \  ----      / \/ \  / \/ \  / \/ \  / \/ \  ----
  \_/\_/  \_/\_/  ----      \_/\_/  \_/\_/  \_/\_/  \_/\_/  ----
   ^  ^    ^  ^   ^  ^       ^ ^     ^  ^    ^  ^    ^  ^   ^  ^
   Site   Site  Standby     Site    Site    Site    Site  Standby

  Figure 1: Dynamic allocation of sockets per observed entities activity


Barkai, et al.           Expires March 28,2023                 [Page 3]


Internet-Draft                    LISP                    November 2022


2. Definition of Terms

  Based on [RFC9300][RFC9301]

  Edge Computing: a distributed computing paradigm that brings
     computation closer to the sources of data. This is expected to
     improve response times and save bandwidth. Programability of edge
     computing can be associated with Internet of Things (IOT)
     applications.

  Edge Traffic Steering: Traffic steering defines the different paths
     that application traffic can take to traverse the network.
     Destination zone is also determined by these paths. In edge
     computing traffic steering can be used for network-based service
     selection.

  Digital Twin: a digital representation of an intended or actual
      real-world physical product, system, or process (a physical twin)
      that serves as the effectively indistinguishable digital
      counterpart of it for practical purposes.

  PortableQueueEID: an EID-addressable socket interface assembling point
     to point and multipoint to point application frames to user space
     from the LISP packet interface.

  PortableChannelEID: an EID-addressable socket interface segmenting
     point to multipoint and multipoint to multipoint application frames
     from user space to the LISP packet interface.

  ObservedEntitySensorEID: the EID of a connected sensor which uploads
     data and media frames for digital-twin curation and processing.

  ClientEID: the EID of a client subscribed to a published digital twin
      service (EID Source, EID theme).


Barkai, et al.           Expires March 28,2023                 [Page 4]


Internet-Draft                    LISP                    November 2022

3.  Deployment Assumptions

   (1) An application defines an EID addressing scheme to facilitate
   the connection between observed entities connected sensors and the
   digital entities tasked with representing them.

   (2) EIDs and RTRs assigned to ObservedEntitySensorEIDs, ClientEIDs.

   (3) EIDs and RTRs are assigned to instantiated PortableQueueEIDs and
   PortableChannelEIDs to facilitate data ingest processing and
   published services delivery.

   (4) ObservedEntitySensorEIDs, PortableQueueEIDs, PortableChannelEIDs
   are deployed across a LISP overlay network. Routing Locations (RLOC)
   of sensors and clients are determined by their current access
   anchor. Socket RLOCS are determined by the edge compute dev-ops
   instantiation and delegation procedures.

   (5) Based on RLOC dynamics at any given moment traffic is steered
   by LISP: from ObservedEntitySensorEIDs to PortableQueueEIDs, and
   from PortableChannelEIDs to subscribed ClientEIDs.

Barkai, et al.           Expires March 28,2023                 [Page 5]


Internet-Draft                    LISP                    November 2022

4.  Security Considerations

  The LISP overlay network is inherently secure and private.
  All information is conveyed using provisioned sockets.
  Provisioned sockets EIDs and RLOCs configured in RTRs.
  All traffic may be carried over encrypted encapsulation.

5.  Privacy Considerations

  Privacy and anti-tracking of observed entity sensors.
  Possible use of Ephemeral EIDs configured in RTRs.

6.  Acknowledgments


7.  IANA Considerations

   No IANA considerations.


Barkai, et al.           Expires March 28,2023                 [Page 6]


Internet-Draft                    LISP                    November 2022

8.  Normative References


  [RFC9300] Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
              Cabellos, Ed., "The Locator/ID Separation Protocol (LISP)"
              , RFC 9300, DOI 10.17487/RFC9300,
              October 2022, <https://www.rfc-editor.org/info/rfc9300>.

  [RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos, Ed.,
              "Locator/ID Separation Protocol (LISP) Control Plane",
               RFC 9301, DOI 10.17487/RFC9301,
               October 2022, <https://www.rfc-editor.org/info/rfc9301>.

  [RFC8378]  Farinacci, D., Moreno, V., "Signal-Free Locator/ID
              Separation Protocol (LISP) Multicast", RFC8378,
              DOI 10.17487/RFC8378, May 2018,
              <https://www.rfc-editor.org/info/rfc8378>.


Barkai, et al.           Expires March 28,2023                 [Page 7]


Internet-Draft                    LISP                    November 2022

Authors' Addresses

   Sharon Barkai
   Fermi.io
   CA
   USA

   Email: sbarkai@gmail.com


   Alberto Rodriguez-Natal
   Cisco Systems
   170 Tasman Drive
   San Jose, CA
   USA

   Email: natal@cisco.com


   Fabio Maino
   Cisco Systems
   170 Tasman Drive
   San Jose, CA
   USA

   Email: fmaino@cisco.com


   Albert Cabellos-Aparicio
   Technical University of Catalonia
   Barcelona
   Spain

   Email: acabello@ac.upc.edu


   Jordi Paillisse-Vilanova
   Technical University of Catalonia
   Barcelona
   Spain

   Email: jordip@ac.upc.edu


   Dino Farinacci
   lispers.net
   San Jose, CA
   USA

   Email: farinacci@gmail.com

Barkai, et al.           Expires March 28,2023                 [Page 8]