Secure Electronic Environment (S.E.E.) Mail Business Requirements Version 2.2

You are viewing an ARCHIVED page.

19 November 2002

Download PDF to print this document [252 KB]

Document Purpose:

This document describes the business requirements that a Gateway must meet, to be able to exchange, block and report upon messages sent between S.E.E. Mail Participating Agencies.

Key S.E.E. Mail documents:

• Definitions

• Business Requirements (this document)

• Site Certification process

• Product/Supplier Accreditation Process

• Tests

Further information:

Refer to www.see.govt.nz for further information regarding the Secure Electronic Environment (S.E.E.)

Throughout this document the terms "[S**MAIL]", "[IN CONFID*NC*]", "[S*NSITV*]" and "[R*STRICT*D]" are used. This enables the document to be e-mailed from a S.E.E. participating Agency to any non-S.E.E. organisation. Before using this document "*" should be globally replaced with "E"

Revision Information:

v2.1 - Incorporates "Trusted Server" concept. v2.1a - Updated to reference SIGS. v2.2 - Updated to use existing government security classifications instead of XSEEMail

Key words:

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 Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. (http://www.ietf.org/rfc/rfc2119.txt?number=2119)

MUST is typically used where non-compliance with the requirement would impact all SEEMail Agencies.

SHOULD is typically used where non-compliance with the requirement would only impact the implementing SEEMail Agency.