Movatterモバイル変換
[0]ホーム
e: Here is the text of my message. e: Klyne & Atkins Standards Track [Page 21] RFC 3862 CPIM: Message Format August 20045.2. An Example Esing MIME multipart/signed In order to secure a Message/CPIM, an application or implementation may use RFC 1847 [14], and some appropriate security protocols (e.g., S/MIME [19] or openPGP [17]), and cryptographic scheme. Using S/MIME [19] and pkcs7, the above message would look like this: x: Content-Type: multipart/signed; boundary=next; micalg=sha1; protocol=application/pkcs7-signature x: x: --next m: Content-Type: Message/CPIM s: h: From: MR SANDERS h: To: Dopey Donkey h: DateTime: 2000-12-13T13:40:00-08:00 h: Subject: the weather will be fine today h: Subject:;lang=fr beau temps prevu pour aujourd'hui h: NS: MyFeatures h: Require: MyFeatures.VitalMessageOption h: MyFeatures.VitalMessageOption: Confirmation-requested h: MyFeatures.WackyMessageOption: Use-silly-font s: e: Content-type: text/xml; charset=utf-8 e: Content-ID:<1234567890@foo.com> e: e: e: Here is the text of my message. e:
[8]ページ先頭