From 8ab7b9c38958b3a947295370bff8d9a149b2240d Mon Sep 17 00:00:00 2001 From: "tmp_github@goffi.org" Date: Mon, 13 Jan 2025 00:27:54 +0100 Subject: [PATCH] Add ProtoXEP: GRE Formatter: MIME This GRE Formatter uses Multipurpose Internet Mail Extensions (MIME) to format payload. --- inbox/gre-formatter-mime.xml | 113 +++++++++++++++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 inbox/gre-formatter-mime.xml diff --git a/inbox/gre-formatter-mime.xml b/inbox/gre-formatter-mime.xml new file mode 100644 index 00000000..c8b58e64 --- /dev/null +++ b/inbox/gre-formatter-mime.xml @@ -0,0 +1,113 @@ + + +%ents; +]> + + +
+ GRE Formatter: MIME + This GRE Formatter uses Multipurpose Internet Mail Extensions (MIME) to format payload. + + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + XEP-0001 + + + + gre-formatter-mime + + gre + formatter + + + Jérôme + Poisson + goffi@goffi.org + goffi@jabber.fr + + + 0.0.1 + 2025-01-12 + jp +

First draft.

 + +
+ + +

This XEP defines a GRE Formatter that uses Multipurpose Internet Mail Extensions (MIME) as specified in RFC 2045, RFC 2046, RFC 2047, RFC 2183, and RFC 2231. This formatter will ensure that payloads are structured according to the MIME standards, allowing for proper formatting before encryption.

+ + + +

The design goals of this GRE Formatter are:

+
    +
  • Be usable with email gateways to send and receive end-to-end encrypted emails.
    • +
  • The formatter should be capable of handling attachments by creating appropriate MIME parts.
    • +
  • Compliance with RFC 2045, RFC 2046, RFC 2047, RFC 2183, and RFC 2231.
    • +
+ + + +

MIME payloads must conform to the following structure:

+
    +
  • Text Content: For text/plain and other text-based MIME types, the payload SHOULD be encoded in UTF-8.
    • +
  • Attachments: Attachments should be enclosed within a multipart/mixed container. Each attachment should have its own MIME part with appropriate headers like Content-Type and Content-Disposition.
    • +
+

Formatted payload MUST be constructed according to the rules defined in RFCs 2045 through 2231.

+ + + +

The following business rules apply to the MIME GRE Formatter:

+
    +
  • The use of &xep0247; is recommended to avoid reaching stanza limits, especially when attachments are used.
    • +
  • The use of Content-Disposition headers for attachments is recommended to facilitate proper handling by legacy systems.
    • +
+ + + +

If an entity supports the MIME GRE Formatter, it MUST advertise it by including the "urn:xmpp:gre:formatter:mime:0" discovery feature in response to a &xep0030; information request.

+ + +]]> + + + ... + + + ... + +]]> + + + + +

This document introduces no security considerations above and beyond those already defined in XEP-0XXX Gateway Relayed Encryption.

+ + + +

This document does not require interaction with &IANA;.

+ + + +

TODO

+ + + +

Thanks to NLNet foundation/NGI Zero Core for funding the work on this specification.

+ + +