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-04 Abstract This document describes the interfaces and functionality of portable multipoint socket objects. Each socket is instantiated per Unicast or Multicast Endpoint Identifier(EID) using eBPF like Unix stack. Sockets are delegated and deployed across compute locations either as queues which receive and assemble upstream point-to-point and multipoint-to- point application frames, or, as channels which segment and transmit point-to-multipoint and multipoint-to-multipoint application frames. Portability of socket queues and channels, traffic steering, multicast subscription and replication, to and from socket objects 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 Identifier(EID) using eBPF like Unix stack. Sockets are delegated and deployed across compute locations either as queues which receive and assemble upstream point-to-point and multipoint-to- point application frames, or, as channels which segment and transmit point-to-multipoint and multipoint-to-multipoint application frames. Portability of socket queues and channels, traffic steering, multicast subscription and replication, to and from socket objects 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 to handle the capacity and decentralized fragmentation. In order to organize the compute logic in such environments dimensions of a digital-twin constructs are considered: the observable entity, the instantiated digital entity, the connection between them, data models, raw and curated, and the services offered these intermediate building blocks for distributed processing and data-reduction. 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. As examples observed virtual subnets locations may be moving between physical switches, street segments may observed using moving vehicles. Connected sensors may be feeding one twin of an observed entity one moment, and 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 to facilitate compute elasticity or to recover from failures and disconnects. Connected sensors and clients of digital entities 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. The received assembled frames are made available from socket to user space using eBPF-Map[] type mechanisms. Channel sockets use eBPF-Map[] type mechanisms to receive application frames and a 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 across locations per 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) defined by the observed entity, digital entity, the connection between them, data models, and services. Socket: is a software structure within a network node of a computer network that serves as an endpoint for sending and receiving data across the network. Typical Unix sockets are coupled with specific processes, however this document does not assume this model. A functional and more portable programming model may be used to access sockets structure. EndpointIdentifier (EID): is a source and destination address of hosts in a typical LISP network, however in this document EIDs are used to distinguish between socket objects regardless of the host they are instantiated in right now. PortableQueueEID: an EID-addressable socket interface assembling point to point and multipoint to point application frames to user space from the LISP packet interface supporting QueueRead(EID, Frame). PortableChannelEID: an EID-addressable socket interface segmenting point to multipoint and multipoint to multipoint application frames from user space to the LISP interface, ChannelWrite(EID,EID,Frame). 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 connected sensors of observed entities and the digital entities tasked with representing them. (2) EIDs and RTRs assigned to ObservedEntitySensorEIDs and ClientEIDs to be able to communicate with Portable Edge Multipoint Sockets. (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: reassigning EIDs and purging data-structures associated with them. (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, . [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, . [RFC8378] Farinacci, D., Moreno, V., "Signal-Free Locator/ID Separation Protocol (LISP) Multicast", RFC8378, DOI 10.17487/RFC8378, May 2018, . 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]