Registration of MIME media type .pss
To: ietf-types@iana.org Subject: Registration of MIME media type *.pss MIME media type name: Application MIME subtype name: .pss Required parameters: none Optional parameters: none Encoding considerations: ESS files are binary data and thus should be encoded for MIME mail transmission. The same guidelines that apply to application/octet-stream apply to this. Security considerations: none Interoperability considerations: none Published specification: The specifications for this content type are proprietary. They are specified by Essential Security Software, Inc. Applications which use this media type: Essential Security Software product, Essential Security Suite and Ecrypt-it. Contains encrypted information. Additional information: Magic number(s): none File extension(s): *.pss Macintosh File Type Code(s): none Person & email address to contact for further information: Tony Mohr tonym@essentialsecurity.com 425.454.2632 Intended usage: common (One of COMMON, LIMITED USE or OBSOLETE) Best Regards, Tony Mohr Essential Security Software Director - Business Development Desk: 425-454-2632 Cell: 425-443-6713 Email: tonym@essentialsecurity,com Web: <blocked::blocked::BLOCKED::http://www.essentialsecurity.com> www.essentialsecurity.com "Security Made Simple"
(same comments on the application/.ecc registration) On Thursday, December 9, 2004, 10:07:45 PM, Tony wrote: TM> To: ietf-types@iana.org TM> Subject: Registration of MIME media type *.pss TM> TM> MIME media type name: Application TM> TM> MIME subtype name: .pss Why the leading dot? Note that the dot has a syntactic use in media type names. TM> Security considerations: none This is unlikely. Some indication should be given of why this data is harmless. This is particularly the case in the absence of a published specification. TM> TM> Interoperability considerations: none TM> TM> Published specification: The specifications for this TM> content type are proprietary. They are specified by Essential TM> Security Software, Inc. In that case, would a vendor tree registration not be more appropriate? application/vnd.ess.pss (note - not application/vnd..ess.pss ) and similarly application/vnd.ess.ecc TM> Applications which use this media type: Essential Security TM> Software product, Essential Security Suite and Ecrypt-it. Contains TM> encrypted information. TM> TM> Additional information: TM> TM> Magic number(s): none TM> File extension(s): *.pss TM> Macintosh File Type Code(s): none TM> TM> Person & email address to contact for further information: TM> TM> Tony Mohr TM> tonym@essentialsecurity.com TM> 425.454.2632 TM> TM> Intended usage: common TM> TM> (One of COMMON, LIMITED USE or OBSOLETE) Why common? It sounds as if limited would be more likely, if its for internal use in two products. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
At 06:45 05/01/21, Chris Lilley wrote:
(same comments on the application/.ecc registration)
On Thursday, December 9, 2004, 10:07:45 PM, Tony wrote:
TM> Security considerations: none
This is unlikely. Some indication should be given of why this data is harmless. This is particularly the case in the absence of a published specification.
Yes, and in addition particularly when looking at the applications that use this type:
TM> Applications which use this media type: Essential Security TM> Software product, Essential Security Suite and Ecrypt-it. Contains TM> encrypted information.
TM> TM> Interoperability considerations: none TM> TM> Published specification: The specifications for this TM> content type are proprietary. They are specified by Essential TM> Security Software, Inc.
In that case, would a vendor tree registration not be more appropriate?
application/vnd.ess.pss (note - not application/vnd..ess.pss )
and similarly
application/vnd.ess.ecc
Yes indeed. Regards, Martin.
participants (3)
-
Chris Lilley -
Martin Duerst -
Tony Mohr