1 = Counter-Proposals and Offers = 2 3 When attempting to schedule an event, an attendee may suggest an alternative 4 time by issuing a counter-proposal in the form of a `COUNTER` message. Upon 5 receiving a counter-proposal, an organiser may then issue an updated 6 invitation with new details (potentially matching those suggested in the 7 counter-proposal, but not necessarily) for attendees to accept or decline. 8 Alternatively, an organiser may refuse to consider other times and send the 9 attendee concerned a `DECLINECOUNTER` message. 10 11 == Offers to Schedule == 12 13 It can be useful for an attendee issuing such a counter-proposal to mark the 14 periods involved as tentatively occupied until they know that their proposal 15 has been accepted or not; it is also useful for the organiser to be able to 16 rely on such periods being temporarily reserved by attendees so that any 17 acceptance of a counter-proposal will succeed instead of failing because an 18 attendee has chosen to dedicate those periods to something else. Thus, an 19 attendee will make a temporary offer of scheduling for periods of time 20 associated with an event, expiring such an offer in case the organiser chooses 21 not to respond in a timely fashion (or at all). 22 23 == Managing Counter-Proposals == 24 25 Each attendee invited to an event may respond with a counter-proposal. Thus, 26 an organiser needs to be able to collect multiple counter-proposals for each 27 event and to choose one to accept, if any are to be accepted at all. In 28 principle, an organiser could merge details of different proposals, 29 particularly if multiple periods are involved (and also if different attendees 30 are suggested in different proposals), with the resulting combination of 31 details being issued as a new request to all attendees.
