[14] RFC 2480 - Gateways and MIME Security Multiparts, , https://tools.ietf.org/html/rfc2480
[1] S/Mime and PGP Products and Interoperability ( 版) http://www.strom.com/places/smime.html
[2] RFC 7281 - Authentication-Results Registration for S/MIME Signature Verification ( ( 版)) https://tools.ietf.org/html/rfc7281
[3] RFC 7114 - Creation of a Registry for smime-type Parameter Values ( ( 版)) https://tools.ietf.org/html/rfc7114
[4] RFC 7107 - Object Identifier Registry for the S/MIME Mail Security Working Group ( ( 版)) https://tools.ietf.org/html/rfc7107
[5] Secure MIME Datasheet ( 版) http://web.archive.org/web/19970709141721/http://home.netscape.com/assist/security/smime/datasheet.html
[6] RFC 7508 - Securing Header Fields with S/MIME ( 版) https://tools.ietf.org/html/rfc7508
[7] RFC 7107 - Object Identifier Registry for the S/MIME Mail Security Working Group ( ( 版)) http://tools.ietf.org/html/rfc7107
OCNでは、送信するメールにシマンテック社*2発行の電子証明書を添付し、電子的に封(署名)をします。
メールソフトによっては、電子署名が「smime.p7s」という添付ファイルとして表示されることがあります。
[9] RFC 4262 - X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities () https://tools.ietf.org/html/rfc4262
[10] 自堕落な技術者の日記 : S/MIME署名/暗号メール機能が最強だと思うOutlook Expressとのお別れ - livedoor Blog(ブログ) () http://blog.livedoor.jp/k_urushima/archives/1729954.html
[11] RFC 8162 - Using Secure DNS to Associate Certificates with Domain Names for S/MIME () https://tools.ietf.org/html/rfc8162
all PIDF implementations that
support the XML Schema extensions for location information described
in this document MUST support S/MIME; in particular, they MUST
support the CMS [6] EnvelopedData and SignedData content types, which
are used for encryption and digital signatures, respectively.
[13] OpenPGPとS/MIMEに脆弱性、適切な実装をしていないクライアントが原因 | スラド セキュリティ () https://security.srad.jp/story/18/05/16/074217/