…on and confidentiality can be achieved using Secure/MIME (S/MIME) [ RFC5750 ] [ RFC5751 ], which uses the Security Multiparts framework for MIME [ RFC1847 ]. 2.2.1 . Authorization In iTIP messages [ iTIP ], only the "Organizer" is authorized to modify or cancel calendar entries s…

…ation and confidentiality can be achieved using Secure/MIME (S/MIME) [RFC5750] [RFC5751], which uses the Security Multiparts framework for MIME [RFC1847]. 2.2.1. Authorization In iTIP messages [iTIP], only the "Organizer" is authorized to modify or cancel calendar entries she org…

…ation and confidentiality can be achieved using Secure/MIME (S/MIME) [RFC5750] [RFC5751], which uses the Security Multiparts framework for MIME [RFC1847]. 2.2.1. Authorization In iTIP messages [iTIP], only the "Organizer" is authorized to modify or cancel calendar entries she org…

…on and confidentiality can be achieved using Secure/MIME (S/MIME) [ RFC5750 ] [ RFC5751 ], which uses the Security Multiparts framework for MIME [ RFC1847 ]. 2.2.1 . Authorization In iTIP messages [ iTIP ], only the "Organizer" is authorized to modify or cancel calendar entries s…

…such, this document obsoletes version 3.2 of the S/MIME Message Specification [ RFC5751 ]. This specification contains a number of references to documents that have been obsoleted or replaced. This is intentional, as the updated documents often do not have the same information or…

…sses . . . . . . . . . . . . . . . . . . . . . . . 11 1 . Introduction S/MIME [ RFC5751 ] messages often contain a certificate (some messages contain more than one certificate). These certificates assist in authenticating the sender of the message and can be used for encrypting m…

…tead of individual UDP payloads. In these situations, CMS [ RFC5652 ], S/MIME [ RFC5751 ] or OpenPGP [ RFC4880 ] could be used. In addition, there are many non-IETF protocols in this area. Like congestion control mechanisms, security mechanisms are difficult to design and impleme…

…lities in the SMIMECapabilities attribute, which is either a signed attribute [ RFC5751 ] or a certificate extension [ RFC4262 ]. 6 . References 6.1 . Normative References [ RFC2119 ] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14 , RFC 2119 , Mar…

… example, message parts that are cryptographically signed, using e.g., S/MIME [ RFC5751 ] or Pretty Good Privacy (PGP) [ RFC3156 ], cannot be upgraded from the RFC 2047 form to normal UTF-8 characters without breaking the signature. Similarly, message parts that are encrypted may…

…ilities in the SMIMECapabilities attribute, which is either a signed attribute [RFC5751] or a certificate extension [RFC4262]. 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. …

…message cryptography, such as Pretty Good Privacy (PGP) ([RFC4880]) or S/MIME ([RFC5751]). 11.5. Untrusted Information Sources An SPF-compliant receiver gathers information from the SMTP commands it receives and from the published DNS records of the sending domain holder (e.g., "…

…sage cryptography, such as Pretty Good Privacy (PGP) ([ RFC4880 ]) or S/MIME ([ RFC5751 ]). 11.5 . Untrusted Information Sources An SPF-compliant receiver gathers information from the SMTP commands it receives and from the published DNS records of the sending domain holder (e.g.,…

… message signing (e.g., Secure/Multipurpose Internet Mail Extensions (S/MIME) [ RFC5751 ], OpenPGP [ RFC4880 ]) in that: o the message signature is written as a message header field so that neither human recipients nor existing MUA (Mail User Agent) software is confused by signat…

…sfers MIME objects to address authentication or confidentiality (e.g., S/MIME [ RFC5751 ], OpenPGP [ RFC4880 ]). In cases where the confidentiality or authenticity of information contained in vCard is a concern, the vCard SHOULD be transported using one of these secure mechanisms…

…lities in the SMIMECapabilities attribute, which is either a signed attribute [ RFC5751 ] or a certificate extension [ RFC4262 ]. 6 . References 6.1 . Normative References [ RFC2119 ] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14 , RFC 2119 , Mar…