From 412aae90b0d3d498e743b4551850239904b4127a Mon Sep 17 00:00:00 2001 From: Michael Zappa Date: Tue, 12 Dec 2023 16:44:44 -0700 Subject: [PATCH 1/2] add attachment+endpoint definitions Signed-off-by: Michael Zappa --- SPEC.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/SPEC.md b/SPEC.md index eee34ee4..acc2fbe0 100644 --- a/SPEC.md +++ b/SPEC.md @@ -69,11 +69,13 @@ Released versions of the spec are available as Git tags. This document proposes a generic plugin-based networking solution for application containers on Linux, the _Container Networking Interface_, or _CNI_. -For the purposes of this proposal, we define three terms very specifically: +For the purposes of this proposal, we define six terms very specifically: - _container_ is a network isolation domain, though the actual isolation technology is not defined by the specification. This could be a [network namespace][namespaces] or a virtual machine, for example. - _network_ refers to a group of endpoints that are uniquely addressable that can communicate amongst each other. This could be either an individual container (as specified above), a machine, or some other network device (e.g. a router). Containers can be conceptually _added to_ or _removed from_ one or more networks. - _runtime_ is the program responsible for executing CNI plugins. - _plugin_ is a program that applies a specified network configuration. +- _attachment is the operation of applying a network configuration to a container, which results in an endpoint. +- _endpoint is a uniquely addressable, container-scoped connection to a single network. This document aims to specify the interface between "runtimes" and "plugins". The key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may" and "optional" are used as specified in [RFC 2119][rfc-2119]. From 082873df2bf821af25a3edf0f8c7218e96d32d29 Mon Sep 17 00:00:00 2001 From: Michael Zappa Date: Mon, 8 Jan 2024 08:37:50 -0700 Subject: [PATCH 2/2] update wording Signed-off-by: Michael Zappa --- SPEC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SPEC.md b/SPEC.md index acc2fbe0..3d0ea6f9 100644 --- a/SPEC.md +++ b/SPEC.md @@ -75,7 +75,7 @@ For the purposes of this proposal, we define six terms very specifically: - _runtime_ is the program responsible for executing CNI plugins. - _plugin_ is a program that applies a specified network configuration. - _attachment is the operation of applying a network configuration to a container, which results in an endpoint. -- _endpoint is a uniquely addressable, container-scoped connection to a single network. +- _endpoint is a uniquely identifiable, container-scoped connection to a single network. This document aims to specify the interface between "runtimes" and "plugins". The key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may" and "optional" are used as specified in [RFC 2119][rfc-2119].