One document matched: draft-ietf-eai-popimap-downgrade-01.xml
<?xml version="1.0" encoding="US-ASCII" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]
<?rfc sortrefs="yes" ?>
<?rfc rfcedstyle="yes" ?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc toc='yes'?>
<rfc category="std" ipr="trust200902" docName="draft-ietf-eai-popimap-downgrade-01.txt">
<front>
<title abbrev="POP/IMAP Downgrade">
Post-delivery Message Downgrading for Internationalized Email Messages
</title>
<author initials="K.F." surname="Fujiwara" fullname="Kazunori Fujiwara">
<organization abbrev="JPRS">Japan Registry Services Co., Ltd.</organization>
<address>
<postal>
<street>Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda</street>
<city>Chiyoda-ku</city>
<region>Tokyo</region>
<code>101-0065</code>
<country>Japan</country>
</postal>
<phone>+81 3 5215 8451</phone>
<email>fujiwara@jprs.co.jp</email>
</address>
</author>
<date day="18" month="Apr" year="2011" />
<area>Applications</area>
<workgroup>Email Address Internationalization (EAI)</workgroup>
<keyword>EAI</keyword>
<keyword>Email Address Internationalization</keyword>
<keyword>Downgrade</keyword>
<keyword>MAIL</keyword>
<abstract>
<t>
The Email Address Internationalization (UTF8SMTP) extension allows
UTF-8 characters in mail header fields.
POP and IMAP servers support internationalized email messages.
If a POP/IMAP client does not support Email Address Internationalization,
POP/IMAP servers cannot send Internationalized Email Headers to the client
and cannot remove the message.
To avoid the situation,
this document describes a conversion mechanism
for internationalized Email messages to be traditional message format.
</t>
</abstract>
</front>
<middle>
<section title="Introduction" anchor="intro">
<t>
Traditional mail systems, which are defined by <xref target="RFC5322" />,
allow ASCII characters in mail header field values.
The UTF8SMTP extension
(<xref target="I-D.ietf-eai-frmwrk-4952bis" /> and
<xref target="I-D.ietf-eai-rfc5335bis" />
allows UTF-8 characters in mail header field values.
</t>
<t>
If a header field contains non-ASCII characters,
POP/IMAP servers cannot send Internationalized Email Headers to the client
and cannot remove the message.
This message downgrading mechanism converts mail header fields to an
all-ASCII representation. The POP/IMAP servers can use the
downgrading mechanism and send the Internationalized Email message as
a traditional form.
</t>
<t>
<xref target="I-D.ietf-eai-rfc5335bis" />
allows UTF-8 characters to be used in
mail header fields and MIME header fields. The message downgrading
mechanism specified here converts mail header fields and MIME
header fields to ASCII.
</t>
<t>
This document does not change any protocols
except by defining new header fields. It describes the conversion
method from the internationalized email messages
that are defined in
<xref target="I-D.ietf-eai-frmwrk-4952bis" />, and
<xref target="I-D.ietf-eai-rfc5335bis" />
to the traditional email messages
defined in
<xref target="RFC5322" />.
</t>
<t>
Message Downgrading may be implemented in POP server and IMAP server only.
</t>
<t>
This document tries to define the message downgrading process clearly.
</t>
<t>
Downgrading consists of the following three parts:
<list style="symbols">
<vspace blankLines="1" />
<t>New header field definitions</t>
<t>Email header field downgrading</t>
<t>MIME header field downgrading</t>
</list>
</t>
<t>
In <xref target="downgradedheader" /> of this document,
header fields starting with "Downgraded-" are introduced.
They preserve the original header fields.
</t>
<t>
Email header field downgrading is described in <xref target="HeaderDowngrading" />.
It generates ASCII-only header fields.
</t>
<t>
MIME header fields are expanded in <xref target="I-D.ietf-eai-rfc5335bis" />.
MIME header field downgrading is described in <xref target="MIMEheaderdowngrading" />.
It generates ASCII-only MIME header fields.
</t>
<t>
Displaying downgraded messages that originally contained
internationalized header fields is out of scope of this
document. A POP/IMAP client which does not support UTF8
extension does not know internationalized message format
described in <xref target="I-D.ietf-eai-rfc5335bis" />.
</t>
</section>
<section title="Terminology">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in RFC
2119 <xref target="RFC2119" />.
</t>
<t>
All specialized terms used in this specification are defined in the
Email Address Internationalization (EAI) overview
<xref target="I-D.ietf-eai-frmwrk-4952bis" />, in the mail message specifications <xref target="RFC5322" />, or in the MIME documents
<xref target="RFC2045" /> <xref target="RFC2047" /> <xref target="RFC2183" /> <xref target="RFC2231" />.
The terms "ASCII address", "internationalized email address", "non-ASCII
address", "i18mail address", "UTF8SMTP", "message", and "mailing list"
are used with the definitions from <xref target="I-D.ietf-eai-frmwrk-4952bis" />.
</t>
<t>
This document depends on <xref target="I-D.ietf-eai-rfc5335bis" />.
Key words used in those documents are used in this document, too.
</t>
<t>
The term "non-ASCII" refers to a UTF-8 string that contains at least
one non-ASCII character.
</t>
<t>
A "UTF8SMTP message" is an email message expanded by
<xref target="I-D.ietf-eai-rfc5335bis" />.
</t>
</section>
<section title="New Header Fields Definition" anchor="downgradedheader">
<t>
New header fields starting with "Downgraded-" are defined here to
preserve those mail header field values that contain
UTF-8 characters. During downgrading, one new "Downgraded-"
header field is added for each mail header field
that cannot be passed as-is to a POP/IMAP client that does not support
UTF8 extension. The original mail header field is removed or
rewritten. Only those mail header fields that contain
non-ASCII characters are affected. The result of this process
is a message that is compliant with existing email
specifications <xref target="RFC5322" />.
The original internationalized information can be retrieved by examining the
"Downgraded-" header fields that were added.
</t>
<section title="Unknown Header Fields' Preservation Header Fields" anchor="unknownencapsulation">
<t>
The unknown header fields' preservation header fields are
defined to
encapsulate those original header fields that contain non-ASCII
characters and are not otherwise provided for in this
specification. The encapsulation header field name is the
concatenation of "Downgraded-" and the original name. The value
field holds the original header field value.
</t>
<t>
The header field syntax is specified as follows: </t>
<figure>
<artwork>
<![CDATA[
fields =/ unknown-downgraded-headers ":" unstructured CRLF
unknown-downgraded-headers = "Downgraded-" original-header-field-name
original-header-field-name = field-name
field-name = 1*ftext
ftext = %d33-57 / ; Any character except
%d59-126 ; controls, SP, and ":".
]]>
</artwork>
</figure>
<t>
To encapsulate a header field in a "Downgraded-" header field:</t>
<list style="numbers">
<t>Generate a new "Downgraded-" header field whose value is the
original header field value.</t>
<t>
Treat the generated header field content as if it were unstructured,
and then apply <xref target="RFC2047" /> encoding with charset UTF-8
as necessary so the result is ASCII.
</t>
<t>Remove the original header field.</t>
</list>
</section>
</section>
<section title="Email Header Fields Downgrading" anchor="HeaderDowngrading">
<t>
This section defines the conversion method to ASCII for each header field
that may contain non-ASCII characters.
</t>
<t>
<xref target="I-D.ietf-eai-rfc5335bis" /> expands
"Received:" header fields;
<xref target="RFC5322" /> describes ABNF elements
<mailbox>, <word>, <comment>, <unstructured>;
<xref target="RFC2045" /> describes ABNF element <value>.
</t>
<section title="Downgrading Method for Each ABNF Element" anchor="DowngradeElements">
<t>
Header field downgrading is defined below for each ABNF element.
Downgrading an unknown header field is also defined as ENCAPSULATION downgrading.
Converting the header field terminates when no non-ASCII characters
remain in the header field.
</t>
<section title="RECEIVED Downgrading" anchor="element:received">
<t>If the header field name is "Received:" and
the FOR clause contains a non-ASCII address,
remove the FOR clause from the header field.
Other parts (not counting <comment>s) should not contain non-ASCII values.
</t></section>
<section title="UNSTRUCTURED Downgrading" anchor="element:unstructured">
<t>If the header field has an <unstructured> field that
contains non-ASCII characters,
apply <xref target="RFC2047" /> encoding with charset UTF-8.
</t></section>
<section title="WORD Downgrading" anchor="element:word">
<t>If the header field has any <word>
fields that contain non-ASCII characters,
apply <xref target="RFC2047" /> encoding with charset UTF-8.
</t></section>
<section title="COMMENT Downgrading" anchor="element:comment">
<t>If the header field has any <comment>
fields that contain non-ASCII characters,
apply <xref target="RFC2047" /> encoding with charset UTF-8.
</t></section>
<section title="MIME-VALUE Downgrading" anchor="element:mimevalue">
<t>If the header field has any <value> elements defined by <xref target="RFC2045" />
and the elements contain non-ASCII characters,
encode the <value> elements
according to <xref target="RFC2231" /> with charset UTF-8 and
leave the language information empty.
If the <value> element is <quoted-string>
and it contains <CFWS> outside the DQUOTE,
remove the <CFWS> before this conversion.
</t></section>
<section title="DISPLAY-NAME Downgrading" anchor="element:display-name">
<t>If the header field has any <address> (<mailbox>
or <group>) elements and
they have <display-name> elements that contain non-ASCII characters,
encode the <display-name> elements
according to <xref target="RFC2047" /> with charset UTF-8.
DISPLAY-NAME downgrading is the same algorithm as WORD downgrading.
</t></section>
<section title="MAILBOX Downgrading" anchor="element:mailbox">
<t>The <mailbox> elements have no equivalent format for non-ASCII addresses.
If the header field has any <mailbox> elements that contain non-ASCII characters,
rewrite each <mailbox> element to ASCII-only format.
The <mailbox> element that contains non-ASCII characters is one of two formats.</t>
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<t>[ Display-name ] "<" Utf8-addr-spec ">"</t>
<t>Utf8-addr-spec</t>
<list style="empty">
<vspace blankLines="1" />
<t>Rewrite both as:</t>
<t>[ Display-name ] "Internationalized Address " Encoded-word</t>
<t>" Removed:;"</t>
<t>where the <Encoded-word> is the original <Utf8-addr-spec> encoded
according to <xref target="RFC2047" />.</t>
<?rfc subcompact="no" ?>
</list>
<t>
[[ Note: If the original non-ASCII address is a part of a group address,
this rewriting may conflict the original DISPLAY-NAME.
This problem need to be fixed. ]]
</t>
</section>
<section title="ENCAPSULATION Downgrading">
<t>If the header field contains non-ASCII characters
and is such that no rule is given above,
encapsulate it in a "Downgraded-" header field as
described in <xref target="unknownencapsulation" />
as a last resort.</t>
<t>Applying this procedure to "Received:" header field is prohibited.
</t></section>
<section title="TYPED-ADDRESS Downgrading"><t>
If the header field contains <utf-8-type-addr>
and the <utf-8-type-addr> contains raw non-ASCII characters,
it is in utf-8-address form. Convert it to utf-8-addr-xtext form.
Those forms are described in <xref target="I-D.ietf-eai-rfc5337bis-dsn"/>.
COMMENT downgrading is also performed in this case.
If the address type is unrecognized and the header field contains non-ASCII characters,
then fall back to using ENCAPSULATION downgrading on the entire header field.
</t>
</section>
</section>
<section title="Downgrading Method for Each Header Field" anchor="DowngradeEachHeader">
<t>
Header fields are listed in <xref target="RFC4021" />.
This section describes the downgrading method for each header field.
</t>
<t>
If the whole mail header field does not contain non-ASCII characters,
email header field downgrading is not required.
Each header field's downgrading method is described below.
</t>
<section title="Address Header Fields That Contain <address>s"
anchor="header:address">
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<list style="hanging">
<t hangText="From:" />
<t hangText="Sender:" />
<t hangText="To:" />
<t hangText="Cc:" />
<t hangText="Bcc:" />
<t hangText="Reply-To:" />
<t hangText="Resent-From:" />
<t hangText="Resent-Sender:" />
<t hangText="Resent-To:" />
<t hangText="Resent-Cc:" />
<t hangText="Resent-Bcc:" />
<t hangText="Resent-Reply-To:" />
<t hangText="Return-Path:" />
<t hangText="Disposition-Notification-To:" />
</list>
<?rfc subcompact="no" ?>
<t>If the header field contains <mailbox> elements
that contain non-ASCII addresses,
perform COMMENT downgrading, DISPLAY-NAME downgrading, and MAILBOX downgrading.
</t>
<t>
[[ Note: RFC 5322 does not allow group syntax in "From:", "Resent-From:", "Sender:", "Resent-Sender:",
but proposed method uses group syntax.
This problem need to be fixed. ]]
</t>
</section>
<section title="Address Header Fields with Typed Addresses"
anchor="header:typedaddress">
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<list style="hanging">
<t hangText="Original-Recipient:" />
<t hangText="Final-Recipient:" />
</list>
<?rfc subcompact="no" ?>
<t>If the header field contains non-ASCII characters, perform TYPED-ADDRESS downgrading.
</t></section>
<section title="Downgrading Non-ASCII in Comments"
anchor="header:comments">
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<list style="hanging">
<t hangText="Date:" />
<t hangText="Message-ID:" />
<t hangText="Resent-Message-ID:" />
<t hangText="In-Reply-To:" />
<t hangText="References:" />
<t hangText="Resent-Date:" />
<t hangText="Resent-Message-ID:" />
<t hangText="MIME-Version:" />
<t hangText="Content-ID:" />
<t hangText="Content-Transfer-Encoding:" />
<t hangText="Content-Language:" />
<t hangText="Accept-Language:" />
<t hangText="Auto-Submitted:" />
</list>
<?rfc subcompact="no" ?>
<t>These header fields do not contain non-ASCII characters except in comments.
If the header field contains UTF-8 characters in comments, perform COMMENT downgrading.
</t></section>
<section title="Received Header Field" anchor="header:received">
<list style="hanging">
<t hangText="Received:" />
</list>
<t>Perform COMMENT downgrading and RECEIVED downgrading.</t>
</section>
<section title="MIME Content Header Fields" anchor="header:mime"><t>
<list style="hanging">
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<t hangText="Content-Type:" />
<t hangText="Content-Disposition:" />
</list>
<?rfc subcompact="no" ?>
<vspace blankLines="1" />
Perform MIME-VALUE downgrading and COMMENT downgrading.
</t></section>
<section title="Non-ASCII in <unstructured>" anchor="header:unstructured"><t>
<list style="hanging">
<?rfc subcompact="yes" ?>
<vspace blankLines="1" />
<t hangText="Subject:" />
<t hangText="Comments:" />
<t hangText="Content-Description:" />
</list>
<?rfc subcompact="no" ?>
<vspace blankLines="1" />
Perform UNSTRUCTURED downgrading.
</t></section>
<section title="Non-ASCII in <phrase>" anchor="header:phrase"><t>
<list style="hanging">
<t hangText="Keywords:" />
</list>
Perform WORD downgrading.
</t></section>
<section title="Other Header Fields" anchor="header:undefined">
<t>For all other header fields that contain non-ASCII characters,
are user-defined, and are missing from this document or future defined header fields,
perform ENCAPSULATION downgrading.</t>
<t>If the software understands the header field's structure and a downgrading
algorithm other than ENCAPSULATION is applicable, that software SHOULD use
that algorithm; ENCAPSULATION downgrading is used as a last resort.</t>
<t>Mailing list header fields (those that start in "List-")
are part of this category.</t>
</section>
</section>
</section>
<section title="MIME Body-Part Header Field Downgrading" anchor="MIMEheaderdowngrading">
<t>
MIME body-part header fields may contain non-ASCII characters
<xref target="I-D.ietf-eai-rfc5335bis" />.
This section defines the conversion method to ASCII-only header fields
for each MIME header field that contains non-ASCII characters.
Parse the message body's MIME structure at all levels and
check each MIME header field to see whether it contains non-ASCII characters.
If the header field contains non-ASCII characters in the header field value,
the header field is a target of the MIME body-part header field's downgrading.
Each MIME header field's downgrading method is described below.
COMMENT downgrading, MIME-VALUE downgrading, and UNSTRUCTURED downgrading
are described in <xref target="HeaderDowngrading" />.
<list style="hanging">
<t hangText="Content-ID:">
<vspace />
The "Content-ID:" header field does not contain non-ASCII
characters except in comments. If the header field contains
UTF-8 characters in comments, perform COMMENT downgrading.
</t>
<t hangText="Content-Type:" />
<list style="hanging" hangIndent="22">
<t hangText="Content-Disposition:">
Perform MIME-VALUE downgrading and
COMMENT downgrading.
</t>
<t hangText="Content-Description:">
Perform UNSTRUCTURED downgrading.
</t>
</list>
</list>
</t>
</section>
<section title="Security Considerations" anchor="security">
<t>
A downgraded message's header fields contain ASCII characters only.
But they still contain MIME-encapsulated header fields that contain
non-ASCII UTF-8 characters. Furthermore, the body part may contain UTF-8 characters.
Implementations parsing Internet messages need
to accept UTF-8 body parts and UTF-8 header fields that are MIME-encoded.
Thus, this document inherits the security considerations of
MIME-encoded header fields (<xref target="RFC2047" /> and
<xref target="RFC3629" />).
</t>
<t>
Rewriting header fields increases the opportunities for
undetected spoofing by malicious senders.
However, rewritten header fields are preserved into Downgraded-*
header fields, and parsing Downgraded-* header fields enables
the detection of spoofing caused by downgrading.
</t>
<t>
The techniques described here invalidate methods that depend
on digital signatures over any part of the message,
which includes the top-level header fields and body-part header fields.
Depending on the specific message being downgraded, the following techniques are likely to break: DomainKeys Identified Mail (DKIM), and possibly S/MIME and Pretty Good Privacy (PGP).
The two obvious mitigations are to stick to 7-bit transport when using these techniques
(as most/all of them presently require)
or to make sure to have UTF8SMTP end-to-end when needed.
</t>
<t>
While information in any email header field should usually be treated with
some suspicion, current email systems commonly employ various
mechanisms and protocols to make the information more trustworthy.
Currently, information in the new Downgraded-* header fields is usually
not inspected by these mechanisms, and may be even less trustworthy
than the traditional header fields.
Note that the Downgraded-* header fields could have been inserted with malicious intent
(and with content unrelated to the traditional header fields).
</t>
<t>
See the "Security Considerations" section in <xref target="I-D.ietf-eai-frmwrk-4952bis"/> for more discussion.
</t>
</section>
<section title="Implementation Notes">
<section title="RFC 2047 Encoding">
<t>
While <xref target="RFC2047" /> has a specific algorithm to deal with whitespace in
adjacent encoded words, there are a number of deployed implementations
that fail to implement the algorithm correctly. As a result, whitespace
behavior is somewhat unpredictable in practice when multiple encoded words
are used. While RFC 5322 states that implementations SHOULD limit lines
to not more than 78 characters, implementations MAY choose to allow
overly long encoded words in order to work around faulty <xref target="RFC2047" />
implementations. Implementations that choose to do so SHOULD have an
optional mechanism to limit line length to 78 characters.
</t>
</section>
</section>
<section title="IANA Considerations" anchor="iana">
<t>
IANA is requested to refuse registration of all field names
that start with "Downgraded-". For unknown header fields, use
the downgrading method described in <xref target="unknownencapsulation" />
to avoid conflicts with existing IETF activity (Email Address Internationalization).
</t>
</section>
<section title="Acknowledgements">
<t>
This document draws heavily from the experimental in-transit
message downgrading procedure described in RFC 5504
<xref target="RFC5504"/>. The contribution of the co-author
of that earlier document, Y. Yoneya, are gratefully
acknowledged.
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.I-D.draft-ietf-eai-frmwrk-4952bis-10" ?>
<?rfc include="reference.I-D.draft-ietf-eai-rfc5335bis-10" ?>
<?rfc include="reference.I-D.draft-ietf-eai-rfc5337bis-dsn-02" ?>
<?rfc include="reference.RFC.2045" ?>
<?rfc include="reference.RFC.2047" ?>
<?rfc include="reference.RFC.2183" ?>
<?rfc include="reference.RFC.2231" ?>
<?rfc include="reference.RFC.5322" ?>
<?rfc include="reference.RFC.3629" ?>
<?rfc include="reference.RFC.4021" ?>
<?rfc include="reference.RFC.2119" ?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.5504" ?>
</references>
<section title="Examples">
<section title="Downgrading Example">
<t>
This appendix shows an message downgrading example.
Consider a received mail message where:
<list style="symbols">
<t>
The sender address is a non-ASCII address, "NON-ASCII-local@example.com". Its display-name is "DISPLAY-local".
</t>
<t>
The "To:" header field contains two non-ASCII addresses, "NON-ASCII-remote1@example.net" and "NON-ASCII-remote2@example.com" Its display-names are "DISPLAY-remote1" and "DISPLAY-remote2".
</t>
<t>
The "Cc:" header field contains a non-ASCII address, "NON-ASCII-remote3@example.org".
Its display-name is "DISPLAY-remote3".
</t>
<t>Four display names contain non-ASCII characters.</t>
<t>
The Subject header field is "NON-ASCII-SUBJECT", which contains non-ASCII
characters.
</t>
<t>
There is an unknown header field "X-Unknown-Header" which contains non-ASCII
characters.
</t>
</list>
</t>
<t>
<figure title="Received message in a mail drop" anchor="example-originaleaismtpsession">
<artwork>
<![CDATA[
Return-Path: <NON-ASCII-local@example.com>
Received: from ... by ... for <NON-ASCII-remote1@example.net>
Received: from ... by ... for <NON-ASCII-remote1@example.net>
From: DISPLAY-local <NON-ASCII-local@example.com>
To: DISPLAY-remote1 <NON-ASCII-remote1@example.net>,
DISPLAY-remote2 <NON-ASCII-remote2@example.com>
Cc: DISPLAY-remote3 <NON-ASCII-remote3@example.org>
Subject: NON-ASCII-SUBJECT
Date: DATE
Message-Id: MESSAGE_ID
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Unknown-Header: NON-ASCII-CHARACTERS
MAIL_BODY
]]>
</artwork>
</figure>
</t>
<t>
The downgraded message is shown in
<xref target="example-downgrading" />.
"Return-Path:", "From:", "To:" and "Cc:" header fields are rewritten.
"X-Unknown-Header:" is encapsulated as "Downgraded-X-Unknown-Header:".
<figure title="Downgraded message" anchor="example-downgrading">
<artwork>
<![CDATA[
Return-Path: Internationalized address
=?UTF-8?Q?NON-ASCII-local@example.com?= removed:;
Received: from ... by ...
Received: from ... by ...
From: =?UTF-8?Q?DISPLAY-local?= Internationalized address
=?UTF-8?Q?NON-ASCII-local@example.com?= removed:;
To: =?UTF-8?Q?DISPLAY-remote1?= Internationalized address
=?UTF-8?Q?NON-ASCII-remote1@example.net?= removed:;,
=?UTF-8?Q?DISPLAY-remote2?= Internationalized address
=?UTF-8?Q?NON-ASCII-remote2@example.com?= removed:;,
Cc: =?UTF-8?Q?DISPLAY-remote3?= Internationalized address
=?UTF-8?Q?NON-ASCII-remote3@example.org?= removed:;
Subject: =?UTF-8?Q?NON-ASCII-SUBJECT?=
Date: DATE
Message-Id: MESSAGE_ID
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Downgraded-X-Unknown-Header: =?UTF-8?Q?NON-ASCII-CHARACTERS?=
MAIL_BODY
]]>
</artwork>
</figure>
</t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:08:59 |