Hi Guy,
Is that a problem with said requirements?
The IANA mandatory requirements for vendor MIME types are:
- they must reference media, not other things
- syntax must be correct
- parameters must be explained (there are none in this case)
- each MIME type describes only one data format, and vice-versa (the differing
little-endian,
big-endian formats are fine and count as one as they can be automatically
detected via
the magic number)
- a note that libpcap output is a binary encoding (as opposed to text)
There are also a list of "shoulds", none of which place obligations on
tcpdump.org.
Note that the "vendor" tree has no requirement for publication of the specification of the format
(ie, publication is encouraged but not required). So concerns like "neither the IETF nor the IANA
will own the file format - or even the registry of link-layer type values" are no issue. They might
be an issue for a "standards track" MIME type, but the bar is much lower for a "vendor" MIME type.
Here's some text from RFC4288 that might forestall other questions:
3.2. Vendor Tree
The vendor tree is used for media types associated with commercially
available products. "Vendor" or "producer" are construed as
equivalent and very broadly in this context.
A registration may be placed in the vendor tree by anyone who needs
to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or
organization producing the software or file format being registered.
Changes to the specification will be made at their request, as
discussed in subsequent sections.
Registrations in the vendor tree will be distinguished by the leading
facet "vnd.". That may be followed, at the discretion of the
registrant, by either a media subtype name from a well-known producer
(e.g., "vnd.mudpie") or by an IANA-approved designation of the
producer's name that is followed by a media type or product
designation (e.g., vnd.bigcompany.funnypictures).
While public exposure and review of media types to be registered in
the vendor tree is not required, using the [email protected]
mailing list for review is strongly encouraged to improve the quality
of those specifications. Registrations in the vendor tree may be
submitted directly to the IANA.
If people on the mailing list are happy with the proposal I'm happy to prepare the paperwork for
submission by you or others.
The itch I'm scratching here is to get Wireshark launching automatically on Linux, so I don't have
to teach the Linux command line when teaching networking protocols.
Cheers, Glen.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
