rfc9671v2.txt		rfc9671.txt
	skipping to change at line 132 ¶		skipping to change at line 132 ¶
	[ :addresses <string-list> ]		[ :addresses <string-list> ]
	[ :updatesonly / :calendarid <string> ]		[ :updatesonly / :calendarid <string> ]
	[ :deletecancelled ]		[ :deletecancelled ]
	[ :organizers <ext-list-name: string> ]		[ :organizers <ext-list-name: string> ]
	[ :outcome <variablename: string> ]		[ :outcome <variablename: string> ]
	[ :reason <variablename: string> ]		[ :reason <variablename: string> ]
	The "processcalendar" action is used to parse encapsulated calendar		The "processcalendar" action is used to parse encapsulated calendar
	data and perform the appropriate action based on the content. If the		data and perform the appropriate action based on the content. If the
	calendar data is malformed in any way, it MUST be ignored and no		calendar data is malformed in any way, it MUST be ignored and no
	action is taken. Otherwise, based on the iTIP method (see		action is taken. Otherwise, calendar objects may be created,
	Section 1.4 of [RFC5546]) of the message, calendar objects are		updated, or deleted from a given calendar.
	created, updated, or deleted from a given calendar.
	This action can be used with or without the "extlists" extension		This action can be used with or without the "extlists" extension
	[RFC6134]. When the "extlists" extension is enabled in a script		[RFC6134]. When the "extlists" extension is enabled in a script
	using <require "extlists">, the script can use the :organizers		using <require "extlists">, the script can use the :organizers
	argument (Section 4.6) in the "processcalendar" action as described		argument (Section 4.6) in the "processcalendar" action as described
	below. When the "extlists" extension is not enabled, the :organizers		below. When the "extlists" extension is not enabled, the :organizers
	argument MUST NOT be used and MUST cause an error according to		argument MUST NOT be used and MUST cause an error according to
	[RFC5228].		[RFC5228].
	This action can be used with or without the "variables" extension		This action can be used with or without the "variables" extension
	skipping to change at line 277 ¶		skipping to change at line 276 ¶
	The optional :outcome argument specifies the name of a variable into		The optional :outcome argument specifies the name of a variable into
	which one of the following strings specifying the outcome of the		which one of the following strings specifying the outcome of the
	action will be stored:		action will be stored:
	"no_action": No action was performed (e.g., the message didn't		"no_action": No action was performed (e.g., the message didn't
	contain calendar data, or the set of provided options prevented		contain calendar data, or the set of provided options prevented
	the message from being processed).		the message from being processed).
	"added": A new calendar object was added to a calendar.		"added": A new calendar object was added to a calendar.
	"updated": A calendar resource was updated, cancelled, or removed		"updated": A calendar object was updated, cancelled, or removed from
	from the calendar.		the calendar.
	"error": The message would have been processed but encountered an		"error": The message would have been processed but encountered an
	error in doing so.		error in doing so.
	4.8. Reason Argument		4.8. Reason Argument
	The optional :reason argument specifies the name of a variable into		The optional :reason argument specifies the name of a variable into
	which a string describing the reason for the outcome will be stored.		which a string describing the reason for the outcome will be stored.
	If no reason for the outcome is available, implementations MUST set		If no reason for the outcome is available, implementations MUST set
	the variable to the empty string.		the variable to the empty string.
End of changes. 2 change blocks.
	5 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.