Introduce Network Layer Protocols

[Adwoa-Konadu-Appiah]

Calm Schema Change Proposal

Target Schema: interface.json

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

Proposed Schema Changes:

    "network-layer-protocol-interface": {
      "$ref": "#/defs/interface-type",
      "type": "object",
      "properties": {
        "protocol": {
          "type": "array",
          "items": {
             "$ref": "#/defs/network-layer-protocol-interface-type"
          },
          "uniqueItems": 1,
          "minItems": 1
        }
      },
    "required": [
      "protocol"
    ]
    },
    "network-layer-protocol-interface-type": {
      "enum": [
        "Ethernet",
        "Wi-Fi",
        "PPP",
        "Frame Relay",
        "ATM",
        "FDDI",
        "DSL",
        "ISDN",
        "SONET",
        "MAC",
        "Device drivers",
        "Hardware interfaces"
      ]
    }

[rocketstack-matt]

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]

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