Calendar Access Protocol (CAP)
Voir toute la rfc dans une seule page
Page : 48 / 131
Télécharger le PDF
Auteur(s) :
S. Mansour,
G. Babics,
D. Royer
Classé sous :
Calendar user,
Cu,
Calendar user agent,
Cua,
Ical,
Calender store,
Cs
RFC 4324 Calendar Access Protocol December 2005
7. New Parameters
7.1. ACTION Parameter
Parameter Name: ACTION
Purpose: This parameter indicates the action to be taken when a
timeout occurs.
Value Type: TEXT
Conformance: This property can be specified in the "CMD" property.
When present in a "CMD" property, the "ACTION" parameter specifies
the action to be taken when the command timeout expires.
Formal Definition: The parameter is defined by the following
notation:
action-param = ";" "ACTION" "=" ( "ASK" / "ABORT" )
; If 'action-param' is supplied then
; 'latency-param' MUST be supplied.
Example:
CMD;LATENCY=10;ACTION=ASK:CREATE
7.2. ENABLE Parameter
Parameter Name: ENABLE
Purpose: This parameter indicates whether or not the property should
be ignored. For example, it can indicate that a "TRIGGER"
property in a "VALARM" component should be ignored.
Value Type: BOOLEAN
Conformance: This property can be specified in the "TRIGGER"
properties.
Description: When a non owner sends an [iTIP] "REQUEST" to a calendar
that object might contain a "VALARM" component. The owner may
wish to have local control over their own CUA and when or how
alarms are triggered.
A CUA may add the "ENABLE" parameter to any "TRIGGER" property
before booking the component. If the "ENABLE" parameter is set to
"FALSE", then the alarm will be ignored by the CUA. If set to
Royer, et al. Experimental [Page 48]