architecture-as-code icon indicating copy to clipboard operation
architecture-as-code copied to clipboard

Introduce Internet Layer Protocol

Open Adwoa-Konadu-Appiah opened this issue 8 months ago • 1 comments

### Calm Schema Change Proposal

Target Schema: interface.json

Description of Change: This proposal seeks to add an internet-layer interface to the list of calm interfaces for the protocol based on the TCP/IP protocol Use Cases: Users, including internet-layer interfaces on a node, will now define it as an internet-layer protocol, providing an interface for internet protocols between two nodes.

Proposed Schema Changes:

"internet-layer-protocol-interface": {
      "$ref": "#/defs/interface-type",
      "type": "object",
      "properties": {
        "protocol": {
          "type": "array",
          "items": {
             "$ref": "#/defs/internet-layer-protocol-interface-type"
          },
          "uniqueItems": 1,
          "minItems": 1
        }
      },
    "required": [
      "protocol"
    ]
    },
    "internet-layer-protocol-interface-type": {
      "enum": [
        "IPV4",
        "IPV6",
        "ICMP",
        "ARP",
        "RARP",
        "IGMP",
        "IPSec"
      ]
    }

Adwoa-Konadu-Appiah avatar Apr 17 '25 13:04 Adwoa-Konadu-Appiah

Rather than introducing this as a definition, suggest we look to agree on adopting https://github.com/finos/architecture-as-code/issues/1083 and then publish new interface definitions in a similar way to how we publish control requirements.

rocketstack-matt avatar Apr 17 '25 15:04 rocketstack-matt

We don't plan to centrally publish standards at this time, individual orgs will host their own.

rocketstack-matt avatar Sep 25 '25 15:09 rocketstack-matt