Keith Medcalf wrote:
> I should that the Security Implications are NONE.
>
> There are no security implications in setting a MIME type for "magic
> number" containing SQLite3 databases.
RFC 6838 § 4.6 says that
| the security considerations MUST NOT state that there are "no security
| issues
I should that the Security Implications are NONE.
There are no security implications in setting a MIME type for "magic number"
containing SQLite3 databases.
I should think that the "Interoperability Considerations" are that the
contained data cannot be processed as a stream and it must be
Paul van Genuchten wrote:
> i’m currently not a member of the sqlite consortium.
RFC 6838 § 3.2 says:
| A registration may be placed in the vendor tree by anyone who needs
| to interchange files associated with some product or set of products.
| However, the registration properly belongs to the
3 matches
Mail list logo