Greetings, Submitted for feedback, the following media type registration appears in draft-ietf-ipfix-file, currently in IESG processing. Thanks, Brian Type name: application Subtype name: ipfix Required parameters: none Optional parameters: none Encoding considerations: IPFIX files are binary, and therefore must be encoded in non-binary contexts. Security considerations: See the Security Considerations section (Section 12) of this document, and the Security Considerations section of [RFC5101]. Interoperability considerations: See the Detailed Specification section (Section 7) of this document. The format is designed to be broadly interoperable, as any valid stream of IPFIX Messages over any transport specified in [RFC5101] MUST be recognizable as a valid IPFIX File. Published specification: This document, especially Section 7, and [RFC5101]. Applications that use this media type: Various IPFIX implementations (see [RFC5153]) support the construction of IPFIX File Readers and Writers. Additional information: none Magic number(s): None, although the first two bytes of any IPFIX file are the first two bytes of a message header, the Version field, which as of [RFC5101] are always 10 in network byte order: 0x00, 0x0A. File extension(s): .ipfix Macintosh file type code(s): none For further information: Authors of this document, IETF IPFIX Working Group Intended usage: LIMITED USE Restrictions on usage: none Change controller: Authors of this document, IETF IPFIX Working Group