public:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:04-9-1-general:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:04-9-1-general:start [2026/09/12 18:33] – removed - external edit (Unknown date) 127.0.0.1public:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:04-9-1-general:start [2026/09/12 18:34] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== 4.9.1 General ======
 +
 +[[public:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:start|Return to Submission Format]]
 +
 +Submissions that are concise and easy to read receive more consideration.
 +
 +Submitted documentation SHOULD be confined to material directly relevant to the items requested in the RFP.
 +
 +To the greatest extent possible, the Submission SHOULD follow the document structure set out in [[https://www.iso.org/directives-and-policies.html|ISO/IEC Directives, Part 2]]: Rules for the Structure and Drafting of International Standards [ISO2]. An OMG specification template is available to help follow these guidelines.
 +
 +The keywords "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", and "NEED NOT" SHALL be used as described in Part 2 of the ISO/IEC Directives [ISO2]. These [[public:99_annexes:annex-b-terms-and-definitions:i:iso|ISO]] terms are compatible with the same terms in [[https://www.rfc-editor.org/rfc/rfc2119|IETF RFC 2119]] [RFC2119].
 +
 +The RFC 2119 terms "MUST", "MUST NOT", "OPTIONAL", "REQUIRED", "RECOMMENDED", and "NOT RECOMMENDED" SHALL NOT be used, even though RFC 2119 permits those terms.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>