====== SIP-025 — Transport and Runtime Mechanism Exclusion ======

[[public:00-sip-ra:99-annexes:annex-c-requirements:start|Go to Annex C: Requirements]]

===== Statement =====

The proposed [[public:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] SHALL NOT define transport protocols, message-exchange frameworks, or runtime communication mechanisms.

===== Rationale =====

Transport protocols, message-exchange frameworks, and runtime communication mechanisms are platform-specific realization choices. Incorporating them into the Reference Architecture would constrain portability, limit implementation alternatives, and risk duplicating existing standards.

SIP-RA must define architectural interactions and information exchanges independently of the technologies used to carry them. Implementations and platform-specific profiles may map those abstractions to appropriate transport and runtime mechanisms.

===== Evaluation Criteria =====

The Submission satisfies this requirement when the proposed Reference Architecture:

  - Defines interactions and information exchanges independently of a specific transport protocol
  - Avoids requiring a particular message-exchange framework
  - Avoids defining a new runtime communication mechanism
  - Permits architectural interactions to be realized using multiple transport technologies
  - Distinguishes platform-specific mappings and examples from the normative architecture
  - Avoids making conformance dependent on a particular transport or messaging product
  - References applicable existing standards rather than redefining their transport behavior

===== Referenced By =====

{{backlinks>public:00-sip-ra:99-annexes:annex-c-requirements:sip-025-transport-and-runtime-mechanism-exclusion}}

===== Notes for Editors =====

This exclusion does not prevent SIP-RA from defining abstract interaction constructs, information-flow semantics, attachment points, Interface Contracts, or requirements that a transport realization must satisfy.

A Submission may provide nonnormative mappings to protocols or frameworks to demonstrate that the architecture can be realized.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>