Skip to content

Latest commit

 

History

History
107 lines (77 loc) · 3.77 KB

mir-7.md

File metadata and controls

107 lines (77 loc) · 3.77 KB
Raw
mir title description author status type category created
7
Server Capabilities API
Server Capabilities API
Igor Rendulic (@igorrendulic)
Draft
API
API
2022-07-06

Abstract

Server capabilities API is able to communicate all capabilities of the server, such as:

  • active API version
  • available communication protocols
  • maximum message size
  • maximum single attachment size

Motivation

Defining server capabilities is to simplify the way servers communicate among each other and also client to server communication. The main idea is to lower the number of communication glitches.

Specification

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

Every server MUST have at least 2 protocols:

  • REST API for client-server interface operations
  • PROTO for inner server communication

Protocol MUST have a version defined. The versions number MUST comply to format of Semantic versioning three-part version number

Type MUST be either https or proto string.

Purpose of the protocol MUST be one of the values: restapi or exchange

MaximumMessageSizeBytes and MaximumSingleAttachmentSizeBytes must be size defined in bytes. Messages that exceed the maximum sizes MAY be accepted but the default behaviour is to expect failure.

// ServerCapabilites
type ServerCapabilities struct {
	EmailDomains                     []string          `json:"emailDomains,omitempty"`                                     // supported email domains
	SupportedProtocols               []*ServerProtocol `json:"supportedProtocols" validate:"required,min=2"`               // list of supported protocols (at least REST and Proto protocols)
	MaximumMessageSizeBytes          int64             `json:"maximumMessageSizeBytes" validate:"required,min=1"`          // maximum message size in bytes
	MaximumSingleAttachmentSizeBytes int64             `json:"maximumSingleAttachmentSizeBytes" validate:"required,min=1"` // maximum single attachment size in bytes
}

// Protocol description, purpose and version
type ServerProtocol struct {
	Name    string `json:"name,omitempty"`                                     // name of the protocol
	Version string `json:"version" validate:"required"`                        // version of the protocol
	Type    string `json:"type" validate:"required,oneof=https proto"`         // type of the protocol
	Purpose string `json:"purpose" validate:"required,oneof=restapi exchange"` // purpose of the protocol
}

ServerCapabilities

  • EmailDomains - list of supported email domains (e.g. [mail.io]), optional
  • SupportedProtocols - list of supported protocols.

Operations

Get Server Capabilities

RECOMMENDED URL path for REST API: GET https://{path}/capabilities

Example response:

{
  "emailDomains": ["mail.io"],
  "supportedProtocols": [
    {
      "version": "1.1.0",
      "type": "https",
      "purpose": "restapi"
    },
    {
      "version": "1.0",
      "type": "proto",
      "purpose": "exchange"
    }
  ],
  "maximumMessageSizeBytes": 20000000,
  "maximumSingleAttachmentSizeBytes": 3000000
}

Rationale

The server capabilities are meant to lower the communication glitches for server to server and client to server communications.

Backwards Compatibility

Versioning of protocols is essential for backwards compatibility. Servers MUST be able to support all previous versions of implemented protocols.

Security Considerations

All API communication must be conducted over TLS 1.2 or newer protocol.

Copyright

Copyright and related rights waived via CC0.