Terminology for Computing in the Network

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 11 September 2023.¶

Copyright Notice

Copyright (c) 2023 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.¶

Table of Contents

1. Introduction

The ongoing development of ever richer computing capabilities within network elements is often captured as Computing in the Network (COIN). However, there are different interpretations of the term, often revolving around the 'place' of execution, captured by the 'in-network' aspect of COIN [TRANSPORT]. The different views range from 'only computations on networking hardware' on the one hand to 'COIN is a subset of edge/cloud computing' on the other hand. These differences in interpretation often lead to difficulties in discussions.¶

The goal of this document is to contribute to the clarity in any discussion on COIN through outlining what is a first understanding of a terminology that ought to be used in such discussion. The first definitions in this context were proposed by [I-D.draft-kutscher-coinrg-dir-02] and later adapted by [I-D.draft-irtf-coinrg-use-cases-02] before being moved to this separate document for broader discussion.¶

With this in mind, this document captures the current state of agreement on a common terminology. It is likely that the document will (need to) see a future revision if this understanding is improved through increased insights and changes in the views of the community.¶

2. Terminology

Programmable Network Devices (PNDs): network devices, such as network interface cards and switches, which are programmable, e.g., using P4 or other languages.¶

(COIN) Execution Environment: a class of target environments for function execution, for example, a JVM-based execution environment that can run functions represented in JVM byte code¶

COIN System: the PNDs (and end systems) and their execution environments, together with the communication resources interconnecting them, operated by a single provider or through interactions between multiple providers that jointly offer COIN capabilities¶

COIN Capability: a feature enabled through the joint processing of computation and communication resources in the network¶

(COIN) Program: a monolithic functionality that is provided according to the specification for said program and which may be requested by a user. A composite service can be built by orchestrating a combination of monolithic COIN programs.¶

(COIN) Program Instance: one running instance of a program¶

COIN Experience: a new user experience brought about through the utilization of COIN capabilities¶

3. Security Considerations

TBD¶

4. IANA Considerations

N/A¶

5. Conclusion

This document defines a core terminology for COIN at this point in the work of COIN RG and is thus positioned as a living document which may see revision in due course.¶

Authors' Addresses