Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.3

Multipurpose Internet Mail Extensions (MIME)
Multipurpose Internet Mail Extensions (MIME) Standard or Specification

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Multipurpose Internet Mail Extensions (MIME) defines a message representation protocol specifying considerable detail about United States (US) - American Standard Code for Information Interchange (ASCII) message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the MIME, redefines the format of messages to allow for:
  • textual message bodies in character sets other than US-ASCII
  • an extensible set of different formats for non-textual message bodies
  • multi-part message bodies
  • textual header information in character sets other than US-ASCII
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: View Decisions
Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v23.11
Decision Date: 11/28/2023 at 19:44:27 UTC
Aliases: RFC 1341; RFC 1521; RFC 2045
Introduced By: TRMSP
Standards Body: Internet Engineering Task Force (IETF)
- The information contained on this page is accurate as of the Decision Date (11/28/2023 at 19:44:27 UTC).