| 134 | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 260 | iCalendar object MUST be a fully qualified, [RFC-822] address |
| 268 | "Reply-to" values of an iMIP message. The relevant address MUST be |
| 275 | document MUST have an [RFC-2045] "Content-Type" value of |
| 277 | include the type parameter "method". The value MUST be the same as |
| 293 | A "charset" parameter MUST be present if the iCalendar object |
| 351 | the requested operation. Compliant applications MUST support signing |
| 358 | 1. The iCalendar object MUST be signed by the "Organizer" sending an |
| 385 | To address this security issue, implementations MUST provide |
| 135 | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this |
| 231 | Implementations of iMIP SHOULD verify the authenticity of the creator |
| 314 | "text/calendar" content type, scheduling messages SHOULD be sent with |
| 320 | transfer encoding SHOULD be used for iCalendar objects containing any |
| 377 | SHOULD be encrypted by a mechanism based on Security Multiparts for |