Introduce Interface for Application Layer Protocol
Calm Schema Change Proposal
Target Schema: interface.json
Description of Change: This proposal seeks to add an application-layer interface to the list of calm interfaces for the protocol based on the TCP/IP . Use Cases: Users, including application-layer interfaces on a node, will now define it as an application-layer protocol, providing an interface for application protocols between two nodes.
Proposed Schema Changes:
"application-layer-protocol-interface": {
"$ref": "#/defs/interface-type",
"type": "object",
"properties": {
"protocol": {
"type": "array",
"items": {
"$ref": "#/defs/application-protocol-interface-type"
},
"uniqueItems": 1,
"minItems": 1
}
},
"required": [
"protocol"
]
},
"application-protocol-interface-type": {
"enum": [
"HTTP",
"HTTPS",
"FTP",
"SFTP",
"TFTP",
"POP3",
"SMTP",
"SNMP",
"DNS",
"Telnet",
"SSH",
"DHCP",
"NTP",
"LDAP",
"RTP"
]
}
Rather than introducing this as a definition, suggest we look to agree on adopting #1083 and then publish new interface definitions in a similar way to how we publish control requirements.
We don't plan to centrally publish standards at this time, individual orgs will host their own.
We don't plan to centrally publish standards at this time, individual orgs will host their own.