Registration of MIME media type application/sema
MIME media type name: --------------------- application MIME subtype name: ------------------ sema Required parameters: -------------------- none Optional parameters: -------------------- none Encoding considerations: ------------------------ SEMA files is the result of an encryption of an email and it consists of binary data. Security considerations: ------------------------ A SEMA file is the result of an encryption of an email (including additional attachments) and some of the security issues raised when dealing with email still remains. However, SEMA files requires password(s) to open the email, it uses internal security for creation of mail and makes it possible to securely identify senders, therefore it cannot be used as means to widely spread viruses and potential dangerous data. Published specification: ------------------------ Secured eMail is a system for encrypting/decrypting email. It consists of two parts; The Secured eMail "writer" which is a pice of software which is installed on the senders computer and is used to encrypt email; and a "reader" which is installed at the recipients computer to enable decryption of the email. The first implementation of the "writer" is distributed as an add-in to Microsoft Outlook on the Win32 platform but other implementations will follow. The first implementation of the "reader" is distributed both as an Microsoft Outlook add-in and as a standalone Win32 executable for recipients who do not use Microsoft Outlook. When an email is encrypted, it is transformed into a document with encrypted binary data called a Secured eMail Archive file and this registration is intended to register this document format as a mime type. Applications which use this media type: --------------------------------------- To this date (2004-02-11): Secured eMail Outlook Add-In Secured eMail Standalone Reader Additional information: ----------------------- Magic number(s): File extension(s): .SEMA Macintosh File Type Code(s): Person & email address to contact for further information: ---------------------------------------------------------- 1. Name : Peter Svensson 2. E-mail : peter.svensson@securedemail.se Intended usage: --------------- Common Author/Change controller: ------------------------- Secured eMail AB, Kungsporten 4e, 427 50 Billdal, Sweden http://www.securedemail.se
On Wednesday, February 11, 2004, 7:25:05 PM, Peter wrote: PS> Published specification: The first two sentences of this section give an architectural summary, and the remainder talks of implementations. Does this mean there is no published specification? If so, that would seem to conflict with: PS> Intended usage: PS> --------------- PS> Common -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
This sure looks like it belongs in the vnd. tree to me. Please see the rules regarding registrations in the IETF tree laid out in http://www.ietf.org/internet-drafts/draft-freed-mime-p4-04.txt Sections 3.1.1, 3.2.6, and 3.2.9 seem particularly relevant. Ned
MIME media type name: --------------------- application
MIME subtype name: ------------------ sema
Required parameters: -------------------- none
Optional parameters: -------------------- none
Encoding considerations: ------------------------ SEMA files is the result of an encryption of an email and it consists of binary data.
Security considerations: ------------------------ A SEMA file is the result of an encryption of an email (including additional attachments) and some of the security issues raised when dealing with email still remains. However, SEMA files requires password(s) to open the email, it uses internal security for creation of mail and makes it possible to securely identify senders, therefore it cannot be used as means to widely spread viruses and potential dangerous data.
Published specification: ------------------------ Secured eMail is a system for encrypting/decrypting email. It consists of two parts; The Secured eMail "writer" which is a pice of software which is installed on the senders computer and is used to encrypt email; and a "reader" which is installed at the recipients computer to enable decryption of the email. The first implementation of the "writer" is distributed as an add-in to Microsoft Outlook on the Win32 platform but other implementations will follow. The first implementation of the "reader" is distributed both as an Microsoft Outlook add-in and as a standalone Win32 executable for recipients who do not use Microsoft Outlook. When an email is encrypted, it is transformed into a document with encrypted binary data called a Secured eMail Archive file and this registration is intended to register this document format as a mime type.
Applications which use this media type: --------------------------------------- To this date (2004-02-11): Secured eMail Outlook Add-In Secured eMail Standalone Reader
Additional information: ----------------------- Magic number(s): File extension(s): .SEMA Macintosh File Type Code(s):
Person & email address to contact for further information: ---------------------------------------------------------- 1. Name : Peter Svensson 2. E-mail : peter.svensson@securedemail.se
Intended usage: --------------- Common
Author/Change controller: ------------------------- Secured eMail AB, Kungsporten 4e, 427 50 Billdal, Sweden http://www.securedemail.se
Please either: 1. Open your SEMA format and publish it as an RFC (preferably by joining the apropriate workgroup and ask them to help out), or 2. Register it as application/vnd.sema in the proprietary type tree. Linus Walleij
participants (4)
-
Chris Lilley -
Linus Walleij -
ned.freed＠mrochek.com -
Peter Svensson