[Search] [txt|pdf|bibtex] [Tracker] [WG] [Email] [Nits]

Versions: 00                                                            
Network Working Group                                      Frank Dawson
Internet Draft                                          IBM Corporation
<draft-ietf-calsch-csp-00.txt>                        November 26, 1996
Expires June 1997


          MIME Calendaring and Scheduling Content Type Profile


Status of this Memo

   This document is an Internet-Draft. Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups. Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months.  Internet-Drafts may be updated, replaced, or made obsolete
   by other documents at any time.  It is not appropriate to use
   Internet-Drafts as reference material or to cite them other than as a
   "working draft" or "work in progress".

   To learn the current status of any Internet-Draft, please check the
   1id-abstracts.txt listing contained in the Internet-Drafts Shadow
   Directories on ds.internic.net (US East Coast), nic.nordu.net
   (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
   Rim).

   Distribution of this document is unlimited.


Abstract

   The use of mail enabled applications such as calendaring and
   scheduling has grown considerably in the last decade. Enterprise and
   inter-enterprise business has become dependent on rapid scheduling of
   events and actions using this information technology. The store-and-
   forward characteristic of electronic messaging technologies has been
   shown to be complementary to the asynchronous nature of group
   communications. However, the longer term growth of mail enabled
   applications, such as calendaring and scheduling, is currently
   limited by the lack of Internet standards for the message content
   types that these groupware applications are based on. This
   specification is intended to progress the level of interoperability
   possible between dissimilar calendaring and scheduling applications
   that communicate using an SMTP or MIME transport.

   This specification defines a usage profile for the MIME Calendaring
   and Scheduling Content Type [MIME-CAL]. Any MIME based calendaring
   and scheduling application that supports this MIME Calendaring and
   Scheduling Content Type profile will be able to interoperate with
   other MIME based calendaring and scheduling applications using a
   broad range of scheduling functions.

   Table of Contents

1. Introduction........................................................2


Dawson                             1                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


 1.1 Content Type Profile Summary .....................................3
 1.2 Message Protocol Summary .........................................4
2. Intended Use........................................................5
 2.1 Request and reply to an event ....................................5
 2.2 Request and reply to a todo ......................................6
 2.3 Request and reply to free/busy time ..............................7
 2.4 Negotiate an event ...............................................8
 2.5 Delegate an event ...............................................10
 2.6 Cancel an event .................................................11
3. Profile Specification..............................................12
 3.1 EVENT/REQUEST Profile ...........................................14
 3.2 EVENT/REPLY Profile .............................................16
 3.3 EVENT/COUNTER Profile ...........................................18
 3.4 EVENT/DECLINE-COUNTER Profile ...................................20
 3.5 EVENT/MODIFY Profile ............................................22
 3.6 EVENT/REPLACE Profile ...........................................24
 3.7 EVENT/CANCEL Profile ............................................26
 3.8 EVENT/DELEGATE Profile ..........................................28
 3.9 EVENT/RESEND Profile ............................................30
 3.10 FREE-BUSY/REQUEST Profile ......................................32
 3.11 FREE-BUSY/REPLY Profile ........................................33
 3.12 TODO/REQUEST Profile ...........................................35
 3.13 TODO/REPLY Profile .............................................37
 3.14 TODO/COUNTER Profile ...........................................39
 3.15 TODO/DECLINE-COUNTER Profile ...................................41
 3.16 TODO/MODIFY Profile ............................................43
 3.17 TODO/REPLACE Profile ...........................................45
 3.18 TODO/CANCEL Profile ............................................47
 3.19 TODO/DELEGATE Profile ..........................................49
 3.20 TODO/RESEND Profile ............................................51
4. MIME registrations.................................................53
 4.1 Security Considerations .........................................53
5. Example MIME Message Segments......................................53
 5.1 Simple event/request message ....................................53
 5.2 Negotiated Event Request and Reply ..............................54
 5.3 Event/request based on free-busy time search results ............58
6. Acknowledgments....................................................62
7. Bibliography.......................................................62
8. Author's Address...................................................62

1. Introduction

   This specification defines a usage profile for the MIME Calendaring
   and Scheduling Content Type [MIME-CAL]. [MIME-CAL] provides for the
   capture and exchange of information normally stored within a
   calendaring and scheduling application; such as a Personal
   Information Manager or a Group Scheduling product. The usage profile
   defines a set of MIME messages that form the basis for a message
   based protocol that supports a wide range of group scheduling
   capabilities. These capabilities include the ability to negotiate,
   schedule, modify, delegate and cancel calendar events or todos; as
   well as, request and reply with free/busy time data.




Dawson                             2                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


1.1 Content Type Profile Summary

   The [MIME-CAL] usage profile takes the form of a registration request
   for a series of [MIME-CAL] content type profiles. Specifically, these
   content type profiles include:




              Content-Type Profile  Description
              Type/Subtype Name


              EVENT/REQUEST         Make a request for an
                                    event


              EVENT/REPLY           Reply to an event
                                    request


              EVENT/COUNTER         Make a counter proposal
                                    to the event request


              EVENT/DECLINE-        Decline the counter
              COUNTER               proposal to the event
                                    request


              EVENT/MODIFY          Modify a subset of the
                                    details of an existing
                                    event request


              EVENT/REPLACE         Replace the current
                                    event request with a
                                    complete set of
                                    information


              EVENT/CANCEL          Cancel an existing
                                    event request


              EVENT/DELEGATE        Delegate an existing
                                    event request


              EVENT/RESEND          Request a duplicate of
                                    the current event
                                    request information




Dawson                             3                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



              TODO/REQUEST          Assign a todo


              TODO/REPLY            Reply to a todo
                                    assignment


              TODO/COUNTER          Make a counter proposal
                                    for the todo request


              TODO/DECLINE-COUNTER  Decline a counter
                                    proposal for the todo
                                    request


              TODO/MODIFY           Modify a subset of the
                                    details of an existing
                                    todo assignment


              TODO/REPLACE          Replace the current
                                    todo request with a
                                    complete set of
                                    information


              TODO/CANCEL           Cancel an existing todo


              TODO/DELEGATE         Delegate an existing
                                    todo


              TODO/RESEND           Request a duplicate of
                                    the current todo
                                    request information


              FREE-BUSY/REQUEST     Free/busy time request


              FREE-BUSY/REPLY       Reply to an existing
                                    free/busy time request
                                    with free/busy time
                                    data


1.2 Message Protocol Summary

   This usage profile provides for calendaring and scheduling operations
   including: requesting, replying to, modifying, canceling and
   delegating either an event or todo calendar component. In addition,


Dawson                             4                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   the profiles provide for the request for and reply of free/busy time
   data. These functions are supported through the use of a simple
   message based protocol, as defined by this profile.

   The calendaring and scheduling capabilities are implemented by a
   request-and-reply form of message exchange. For example, an
   appointment type of event would be created between two individual by
   one individual, acting as the event _owner_,  sending an
   EVENT/REQUEST message to the other individual. The recipient of the
   event request message would confirm or decline the proposed
   appointment with an EVENT/REPLY message. A todo or action item could
   similarly be assigned with a TODO/REQUEST and TODO/REPLY message
   sequence. And, a free/busy time data representation of an interval of
   an individual's calendar can be retrieved by a FREE-BUSY/REQUEST and
   FREE-BUSY/REPLY message sequence. More sophisticated scheduling
   operations such as negotiating an appointment request is also
   supported with request-and-reply using the EVENT/COUNTER and
   EVENT/REPLACE or EVENT/DECLINE-COUNTER message sequences between a
   recipient of an EVENT/REQUEST and the _owner_ and/or _organizer_ of
   the event. Similarly, a todo can be negotiated between two
   individuals using the analogous todo component message types.

   The recipient of an event or a todo request can also request an
   updated or duplicate copy of the calendar component description with
   the EVENT/RESEND or TODO/RESENT message types. These messages are
   sent from the recipient of a existing event or todo request to the
   _owner_ and/or _organizer_ of the corresponding event or todo. The
   _owner_ and/or _organizer_ of the calendar component would reply with
   the EVENT/REPLACE or the TODO/REPLACE message type.

   A number of the calendaring and scheduling capabilities defined by
   this usage profile are based a single message exchange, rather than a
   request-and-reply message sequence. For example, an _owner_ or
   _organizer_ of an event or todo can modify a subset of the details of
   the calendar component with the EVENT/MODIFY or TODO/MODIFY message
   types. The complete set of calendar component details can be replaced
   with the EVENT/REPLACE or TODO/REPLACE message types. An event or an
   assigned todo can be canceled by the _owner_ and/or _organizer_ of
   the calendar component with the EVENT/CANCEL or the TODO/CANCEL
   message types.

2. Intended Use

   This usage profile defines a sequence of MIME message types that
   provide for a broad set of scheduling operations. The following
   scenarios provide a limited summary of some of the intended use of
   these messages. Refer to the MIME message segments in section 5 for a
   more detailed set of examples.

2.1 Request and reply to an event

   Individual _A_ requests a meeting between individuals _A_, _B_ and
   _C_. Individual _B_ confirms attendance to the meeting. Individual



Dawson                             5                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   _C_ declines attendance. The following table illustrates the sequence
   of messages that would be exchanged between these individuals.




Action                  Originator               Recipient


Initiate a meeting      _A_ sends EVENT/REQUEST
request                 message to _B_ and _C_


Accept the meeting                               _B_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _CONFIRMED_


Decline the meeting                              _C_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _DECLINED_


Confirm meeting status  _A_ sends EVENT/REPLACE
with attendees          message to _B_ and _C_
                        with current
                        information for event.
                        SEQUENC property is
                        _1_.




2.2 Request and reply to a todo

   Individual _A_ assigns a todo to individual _B_. Individual _B_
   accepts the todo. The following table illustrates the sequence of
   messages that would be exchanged between these individuals.














Dawson                             6                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996




Action                  Originator               Recipient


Assign a todo           _A_ sends TODO/REQUEST
                        message to _B_.


Accept the todo                                  _B_ sends TODO/REPLY
                                                 message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _ACCEPTED_


Confirm todo status     _A_ sends TODO/REPLACE
with attendee           message to _B_ with
                        current information for
                        todo. SEQUENCE property
                        is _1_.




   A similar set of messages could have been exchanged to assign a todo
   to a group of individuals.

2.3 Request and reply to free/busy time

   Individual _A_ requests free/busy time of individuals _B_ and _C_.
   Individual _B_ and _C_ reply to the free/busy time request. The
   following table illustrates the sequence of messages that would be
   exchanged between these individuals.






















Dawson                             7                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996




Action                  Originator               Recipient


Request free time       _A_ sends FREE-BUSY/
                        REQUEST message to _B_
                        and _C_. The interval
                        for the free/busy time
                        is specified with the
                        DTSTART and DTEND
                        properties. The desired
                        duration of time is
                        specified with the
                        DURATION property..


Reply with free/busy                             _B_ sends FREE-
time data                                        BUSY/REPLY message to
                                                 _A_ with an event MIME
                                                 calendar component for
                                                 each free/busy time
                                                 interval. UID
                                                 corresponds to original
                                                 request.

                                                 _C_ sends FREE-
                                                 BUSY/REPLY message to
                                                 _A_ with an event MIME
                                                 calendar component for
                                                 each free/busy time
                                                 interval. UID
                                                 corresponds to original
                                                 request.




2.4 Negotiate an event

   Individual _A_ requests a meeting between individuals _A_, _B_ and
   _C_. Individual _B_ confirms attendance to the meeting. Individual
   _C_ counter proposes. Individual _A_ accepts the counter proposal.
   Individual _C_ confirms attendance to the meeting. Individual _B_
   accepts the modified meeting request. Individual _A_ distributes the
   revised meeting details and attendee status. The following table
   illustrates the sequence of messages that would be exchanged between
   these individuals.




Action                  Originator               Recipient



Dawson                             8                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



Initiate a meeting      _A_ sends EVENT/REQUEST
request                 message to _B_ and _C_


Accept the meeting                               _B_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _CONFIRMED_


Counter proposal for                             _C_ sends EVENT/COUNTER
the meeting request                              message to _A_
                                                 signaling a request to
                                                 revise some detail
                                                 about the request


Accept the counter      _A_ sends EVENT/MODIFY
proposal                message to _B_ and _C_.
                        SEQUENCE parameter is
                        _1_.


Confirm revised meeting                          _C_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _CONFIRMED_.
                                                 RESPONSE-SEQUENCE and
                                                 SEQUENCE parameters are
                                                 both _1_.

                                                 _B_ sends EVENT/REPLY
                                                 message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _CONFIRMED_.
                                                 RESPONSE-SEQUENCE and
                                                 SEQUENCE parameters are
                                                 both _1_.


Redistribute meeting    _A_ sends EVENT/REPLACE
details and status to   message to _B_ and _C_
attendees               with current
                        information for event.
                        SEQUENCE property is
                        _2_.






Dawson                             9                  Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Individual _A_ could have declined the counter proposal for the
   meeting request with the EVENT/DECLINE-COUNTER message. Individual
   _B_ could have declined the original meeting request with the
   EVENT/REPLY message or delegated the original meeting request with a
   combination of the EVENT/REPLY to the originator and the
   EVENT/DELEGATE to the delegated individual (e.g., Individual _D_).

   An analogous exchange of todo component messages could have been used
   to negotiate a todo.

2.5 Delegate an event

   Individual _A_ requests a meeting between individuals _A_ and _B_.
   Individual _B_ delegates attendance to the meeting to individual _C_.
   Individual _C_ confirms attendance to the meeting. Individual _A_
   distributes the revised meeting details and attendee status. The
   following table illustrates the sequence of messages that would be
   exchanged between these individuals.




Action                  Originator               Recipient


Initiate a meeting      _A_ sends EVENT/REQUEST
request                 message to _B_ and _C_


Delegate the meeting                             _B_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _DELEGATED_ and an
                                                 ATTENDEE property has
                                                 been added for _C_.

                                                 _B_ sends
                                                 EVENT/DELEGATE message
                                                 to _C_ with the
                                                 original meeting
                                                 request information.
                                                 The ATTENDEE/STATUS
                                                 property parameter for
                                                 _B_ has been set to
                                                 _DELEGATED_. An
                                                 ATTENDEE property has
                                                 been added for _C_.


Confirm meeting                                  _C_ sends EVENT/REPLY
attendance                                       message to _A_ with
                                                 it's ATTENDEE/STATUS



Dawson                             10                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                                                 property parameter set
                                                 to _CONFIRMED_


Redistribute meeting    _A_ sends EVENT/REPLACE
details and status to   message to _B_ and _C_
attendees               with current
                        information for event.
                        SEQUENCE property is
                        _1_




   Individual _C_ could have declined the delegated proposal for the
   meeting request with the EVENT/REPLY message being sent to both _A_
   and _B_.

   An analogous exchange of todo component messages could have been used
   to delegate a todo.

2.6 Cancel an event

   Individual _A_ requests a meeting between individuals _A_ and _B_.
   Individual _B_ declines attendance to the meeting. Individual _A_
   decides to cancel the meeting. The following table illustrates the
   sequence of messages that would be exchanged between these
   individuals.




Action                  Originator               Recipient


Initiate a meeting      _A_ sends EVENT/REQUEST
request                 message to _B_ and _C_


Decline the meeting                              _B_ sends EVENT/REPLY
request                                          message to _A_ with
                                                 it's ATTENDEE/STATUS
                                                 property parameter set
                                                 to _DECLINED_


Cancel the meeting      _A_ sends EVENT/CANCEL
                        message to _B_ to
                        cancel the meeting.
                        SEQUENCE parameter is
                        _1_.




Dawson                             11                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996




3. Profile Specification

   The following sections define each of the profiles included in this
   specification. If a MIME Calendaring and Scheduling Content Type
   property is not specified in the profile definition, then it is not
   allowed in a MIME entity conforming to the profile.

   The following usage profiles are defined by this document. Each
   profile type/subtype provides support for a particular scheduling
   operation. Taken as a whole, these profiles provide support for a
   robust level of calendaring and scheduling functionality.




              Content-Type Profile  Description
              Type/Subtype Name


              EVENT/REQUEST         Make a request for an
                                    event


              EVENT/REPLY           Reply to an event
                                    request


              EVENT/COUNTER         Make a counter proposal
                                    to the event request


              EVENT/DECLINE-        Decline the counter
              COUNTER               proposal to the event
                                    request


              EVENT/MODIFY          Modify a subset of the
                                    details of an existing
                                    event request


              EVENT/REPLACE         Replace the current
                                    event request with a
                                    complete set of
                                    information


              EVENT/CANCEL          Cancel an existing
                                    event request


              EVENT/DELEGATE        Delegate an existing


Dawson                             12                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                                    event request


              EVENT/RESEND          Request a duplicate of
                                    the current event
                                    request information


              TODO/REQUEST          Assign a todo


              TODO/REPLY            Reply to a todo
                                    assignment


              TODO/COUNTER          Make a counter proposal
                                    for the todo request


              TODO/DECLINE-COUNTER  Decline a counter
                                    proposal for the todo
                                    request


              TODO/MODIFY           Modify a subset of the
                                    details of an existing
                                    todo assignment


              TODO/REPLACE          Replace the current
                                    todo request with a
                                    complete set of
                                    information


              TODO/CANCEL           Cancel an existing todo


              TODO/DELEGATE         Delegate an existing
                                    todo


              TODO/RESEND           Request a duplicate of
                                    the current todo
                                    request information


              FREE-BUSY/REQUEST     Free/busy time request


              FREE-BUSY/REPLY       Reply to an existing
                                    free/busy time request



Dawson                             13                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                                    with free/busy time
                                    data




3.1 EVENT/REQUEST Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/REQUEST
   Profile name: Event request
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based request for
           scheduling a calendar event such as a meeting or an
           appointment. The message is sent from an originator (i.e.,
           OWNER or ORGANIZER) of an event request to one or more
           intended recipients. By default, the originator is the OWNER
           of the event. The OWNER is a ROLE parameter value for the
           ATTENDEE property.
   Profile type/subtype: EVENT/REQUEST
   Required header fields:


        Header Field Name  Value, Parameter Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/request_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/request_.



Dawson                             14                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DTEND              Must be equal to or later than DTSTART.

        DTSTART            Must be before DTEND.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.


   Optional component properties:
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE,
        EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM,
        RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to request a new event with a group of people. Either the
   EVENT/MODIFY, EVENT/REPLACE, or a sequence of the EVENT/CANCEL



Dawson                             15                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   followed by the EVENT/REQUEST profile types should be used by the
   originator to change this event.
   Intended usage: COMMON

3.2 EVENT/REPLY Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/REPLY
   Profile name: Event reply
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based reply to an event
           request such as a meeting or appointment; in order to update
           the status of an attendee. The message is sent from a
           recipient of an event request back to the event OWNER and/or
           ORGANIZER.
   Profile type/subtype: EVENT/REPLY
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/reply_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/reply_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.



Dawson                             16                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           Required if STATUS for recipient is not
                           specified. An instance corresponding to the
                           attendee replying to the original request.
                           If the attendee is delegating the request,
                           then an additional ATTENDEE property must
                           also be included for the individual being
                           delegated to.

        DESCRIPTION        Value may be used as a secondary matching
                           field.

        DTEND              Value may be used as a secondary matching
                           field.

        DTSTART            Value may be used as a secondary matching
                           field

        RESPONSE-SEQUENCE  Required if not zero. Value used to properly
                           sequence receipt of various replies.

        SEQUENCE           Required if not zero. Value used to properly
                           sequence replies to various versions of the
                           event request.

        STATUS             Required if ATTENDEE not specified.

        UID                Value used as a primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request.



Dawson                             17                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



   Optional component properties:
        LAST-MODIFIED, SUMMARY, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to reply to an event request. Note: This profile is not used
           to make a counter proposal to various event request details.
           This would be accomplished by sending an EVENT/COUNTER
           message to the OWNER and/or ORGANIZER of the original event
           request. This profile is ONLY USED to reply to an event
           request such as a meeting or appointment; in order to update
           the status of an attendee. An EVENT/REPLY to a recurring
           event, may contain the EXRULE or EXDATE property in order to
           indicate that the ATTENDEE is only replying to a subset of
           the occurrences in the original EVENT/REQUEST.
   Intended usage: COMMON

3.3 EVENT/COUNTER Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/COUNTER
   Profile name: Counter an existing event request
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based counter to an event
           request. The message is sent from an a recipient of an
           existing event request to the OWNER and/or ORGANIZER of the
           original event request. The OWNER and ORGANIZER are ROLE
           parameter values for the ATTENDEE property.
   Profile type/subtype: EVENT/COUNTER
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/counter_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field


Dawson                             18                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/counter_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DTEND              Must be equal to or later than DTSTART.

        DTSTART            Must be before DTEND.

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.




Dawson                             19                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Optional component properties:
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE,
        EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM,
        RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to counter a request for a new event. The message is sent from a
   recipient of an existing event request to the originator of the event
   request.
   Intended usage: COMMON

3.4 EVENT/DECLINE-COUNTER Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/DECLINE-
           COUNTER
   Profile name: Decline event request counter proposal.
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based decline of an
           existing event request counter proposal. The message is sent
           by the OWNER and/or ORGANIZER of the original, existing event
           request to the originator of the event request counter
           proposal. The OWNER and ORGANIZER are ROLE parameter values
           for the ATTENDEE property.
   Profile type/subtype: EVENT/DECLINE-COUNTER
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/decline-counter_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:



Dawson                             20                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/decline-counter_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           Value represents the originator of the
                           counter proposal.

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        If specified: DESCRIPTION, DTEND, EXDATE, EXRULE, LOCATION,
        RNUM, RDATE, RRULE, RESOURCES, DTSTART, SUMMARY, indicate that
        the event counter was declined because based on the value of
        these properties.
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to decline a counter proposal for an existing event request.


Dawson                             21                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           A MIME entity corresponding to this profile can only be sent
           by one of the recipients of an existing event request. It is
           sent to the OWNER and/or ORGANIZER of the original, existing
           event request. The optional properties in the message are
           specified to indicate the basis for declining the event
           counter proposal. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property.
   Intended usage: COMMON

3.5 EVENT/MODIFY Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/MODIFY
   Profile name: Event modify
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based modification of a
           subset of the description of an existing calendar event
           request. The message is sent from the originator of the
           original event request to one or more of the original
           recipients.
   Profile type/subtype: EVENT/MODIFY
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/modify_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/modify_.



Dawson                             22                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        DESCRIPTION        Value may be used as a secondary matching
                           field.

        DTEND              Value may be used as a secondary matching
                           field.

        DTSTART            Value may be used as a secondary matching
                           field.

        SEQUENCE           Value must be the ordinal of the revision
                           (i.e., 1st revision value would be _1_).

        UID                Value must be a globally unique value.
                           Property must be maintained by the
                           recipient.

        Any of the         Value corresponds to a modified property
        optional           value. If a property is specified with the
        properties.        unchanged, original value, it will still be
                           assumed to be a modified property value.


   Optional component properties:
        ATTACH, ATTENDEE, AALARM, CATEGORIES, CLASS, CREATED, DALARM,
        EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY,



Dawson                             23                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY,
        TRANSP, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           by the originator of an event request to send modifications
           to an existing event. The MIME entity with this profile can
           only be sent by the OWNER and/or ORGANIZER of the original
           event request. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property. This message is intended to
           be used to change a subset of the event details. The
           preferred method of effecting a wholesale change for an event
           is to send an EVENT/REPLACE message or to send an
           EVENT/CANCEL message for the original event request followed
           by an EVENT/REQUEST message the details for the new event.
   Intended usage: COMMON

3.6 EVENT/REPLACE Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/REPLACE
   Profile name: Replace an event request.
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based update of the
           complete description for a calendar event such as a meeting
           or an appointment. The message is sent from an originator
           (i.e., OWNER or ORGANIZER) of an event request to one or more
           intended recipients. By default, the originator is the OWNER
           of the event. The OWNER is a ROLE parameter value for the
           ATTENDEE property.
   Profile type/subtype: EVENT/REPLACE
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/replace_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING


Dawson                             24                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/replace_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DTEND              Must be equal to or later than DTSTART.

        DTSTART            Must be before DTEND.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.


   Optional component properties:


Dawson                             25                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE,
        EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM,
        RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to replace the description of an event with the recipients of an
   existing event request.
   Intended usage: COMMON

3.7 EVENT/CANCEL Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/CANCEL
   Profile name: Event cancellation
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based cancellation of an
           existing event request such as a meeting or an appointment.
           The message is sent by the OWNER and/or ORGANIZER of the
           original, existing event request to the recipients of the
           original event request. The OWNER and ORGANIZER are ROLE
           parameter values for the ATTENDEE property.
   Profile type/subtype: EVENT/CANCEL
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/cancel_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints



Dawson                             26                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        PROFILE            Value must be _event/cancel_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        DESCRIPTION        Value used as a tertiary matching field

        DTEND              Value used as a secondary matching field.

        DTSTART            Value used as a secondary matching field

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        LAST-MODIFIED, RELATED-TO (can be used to find linked events),
        SUMMARY, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to cancel an existing event request. A MIME entity
           corresponding to this profile can only be sent by the OWNER
           and/or ORGANIZER of the original, existing event request. In
           the event that the recipient application does not have the
           persistent UID property for the calendar component, the


Dawson                             27                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           optional properties can be used to select the calendar entry
           corresponding to this request. The OWNER and ORGANIZER are
           ROLE parameter values for the ATTENDEE property.
   Intended usage: COMMON

3.8 EVENT/DELEGATE Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/DELEGATE
   Profile name: Event delegation
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based delegation of an
           existing event request such as a meeting or appointment to an
           alternate individual. The message is sent by any of the
           attendees of an existing event request to another delegated
           attendee and possibly the originator, OWNER, or ORGANIZER of
           the event request. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property.
   Profile type/subtype: EVENT/DELEGATE
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/delegate_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _event/delegate_.

        DAYLIGHT           Value must reflect DST observance at



Dawson                             28                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


                           originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each delegated attendee. In addition, an
                           ATTENDEE instance must be specified for the
                           individual being delegated to.

        DESCRIPTION        None

        DTEND              Must be equal to or later than DTSTART

        DTSTART            Must be before DTEND.

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero

        UID                Value must be a globally unique value.
                           Property must be maintained by the
                           recipient.


   Optional component properties:
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE,
        EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM,
        RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to delegate an existing event request to another person. A MIME
   entity corresponding to this profile may be sent by any of the
   attendees of an existing event request. The properties from the


Dawson                             29                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   original event request must be included in the calendar component to
   assure that the delegated attendee has a complete specification of
   the delegated event. This may include a description that reflects
   numerous revisions of the original request. The message must also
   contain an ATTENDEE property corresponding to the individual being
   delegated to.
   Intended usage: COMMON

3.9 EVENT/RESEND Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile EVENT/RESEND
   Profile name: Request an update or duplicate or an existing event
           request.
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based request for an
           update or duplicate of the specification for an existing
           event request such as a meeting or an appointment. The
           message is sent by the recipient of an existing event request
           to the OWNER and/or ORGANIZER of the original, existing event
           request. The OWNER and ORGANIZER are ROLE parameter values
           for the ATTENDEE property.
   Profile type/subtype: EVENT/RESEND
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _event/resend_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints



Dawson                             30                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        PROFILE            Value must be _event/resend_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        DESCRIPTION, DTEND, DTSTART, LAST-MODIFIED, RELATED-TO, SUMMARY,
        URL can be used as secondary matching fields for the event.
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to request an update or duplicate of the specification of an
           existing event request. A MIME entity corresponding to this
           profile can only be sent by the recipient of an existing
           event request. It is sent to the OWNER and/or ORGANIZER of
           the original, existing event request. In the event that the
           recipient application does not have the persistent UID
           property for the calendar component, the optional properties
           can be used to select the calendar entry corresponding to



Dawson                             31                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           this request. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property.
   Intended usage: COMMON

3.10 FREE-BUSY/REQUEST Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile FREE-BUSY/REQUEST
   Profile name: Free/busy request
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based request of
           free/busy time data from a group of people. The message is
           sent by the originator of the free/busy time request to
           individual recipients of the request.
   Profile type/subtype: FREE-BUSY/REQUEST
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _free-busy/request_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY
                           operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY
                           operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _free-busy/request_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.




Dawson                             32                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGH (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each attendee for which free/busy time data
                           is being requested

        DTEND              Must be equal to or later than DTSTART.
                           Represents the end of the free/busy time
                           search interval

        DTSTART            Must be before or the same as DTEND.
                           Represents the start of the free/busy time
                           search interval

        DURATION           Represents the length of free time being
                           requested.

        UID                Value must be a globally unique value.
                           Property must be maintained by the
                           recipient.


   Optional component properties:
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to request free/busy time data from another person.
   Intended usage: COMMON

3.11 FREE-BUSY/REPLY Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile FREE-BUSY/REPLY
   Profile name: Free/busy reply


Dawson                             33                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based reply of free/busy
           time data. The message is sent by the recipient of the
           free/busy time request to the originator of the request.
   Profile type/subtype: FREE-BUSY/REPLY
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _free-busy/reply_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY
                           operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY
                           operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: EVENT
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _free-busy/reply_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.



Dawson                             34                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           The recipient that is replying to the
                           free/busy time request.

        DTEND              Must be equal to or later than DTSTART.

        DTSTART            This is the start date/time of the free/busy
                           time interval. The date must be before or
                           the same as DTEND.

        TRANSP             This indicates whether the date/time
                           sequence represents a busy (a value of _0_)
                           or free (a value of _1_) time interval.

        UID                Value must be a globally unique value. This
                           value corresponds to the UID in the original
                           free/busy time request.


   Optional component properties:
        STATUS, CATEGORIES
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to reply to a free/busy time request. Numerous intervals of free/busy
   time data are represented as separate MIME event components.
   Intended usage: COMMON

3.12 TODO/REQUEST Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/REQUEST
   Profile name: Todo request
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based assignment of a
           todo or action item. The message is sent from an originator
           (i.e., OWNER or ORGANIZER) of an todo request to one or more
           intended recipients. By default, the originator is the OWNER
           of the todo. The OWNER is a ROLE parameter value for the
           ATTENDEE property.
   Profile type/subtype: TODO/REQUEST
   Required header fields:



Dawson                             35                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/request_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/request_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).


Dawson                             36                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DUE                Must be equal to or later than DTSTART.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.


   Optional component properties:
        DTSTART - Default is the same as DUE value. Indicates the
        date/time that the todo is to first appear on the calendar.
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, EXDATE,
        EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY, PALARM,
        RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY, TRANSP,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to assign a new todo to a group of people. Either the TODO/MODIFY,
   TODO/REPLACE, or a sequence of the TODO/CANCEL followed by the
   TODO/REQUEST profile types should be used by the originator to change
   this todo.
   Intended usage: COMMON

3.13 TODO/REPLY Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/REPLY
   Profile name: Todo reply
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based reply to an todo
           assignment; in order to update the status and possibly the
           completion date of the todo assignee. The message is sent
           from a recipient of an todo request back to the todo OWNER
           and/or ORGANIZER.
   Profile type/subtype: TODO/REPLY
   Required header fields:









Dawson                             37                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/reply_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/reply_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).


Dawson                             38                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           Required if STATUS for recipient is not
                           specified. An instance corresponding to the
                           attendee replying to the original request.
                           If the attendee is delegating the request,
                           then an additional ATTENDEE property must
                           also be included for the individual being
                           delegated to.

        COMPLETED          Required if todo has been completed.

        DESCRIPTION        Value may be used as a secondary matching
                           field.

        DUE                Value may be used as a secondary matching
                           field.

        RESPONSE-SEQUENCE  Required if not zero. Value used to properly
                           sequence receipt of various replies.

        SEQUENCE           Required if not zero. Value used to properly
                           sequence replies to various versions of the
                           todo request.

        STATUS             Required if ATTENDEE not specified.

        UID                Value used as a primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request.


   Optional component properties:
        DTSTART, EXDATE, EXRULE, LAST-MODIFIED, SUMMARY, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to reply to an todo assignment. Note: This profile is not
           used to make a counter proposal to various todo request
           details. This would be accomplished by sending a TODO/COUNTER
           message to the OWNER and/or ORGANIZER of the original todo
           request. This profile is ONLY USED to reply to an todo
           request; in order to update the status of a todo assignee. A
           TODO/REPLY to a recurring todo, may contain the EXRULE or
           EXDATE property in order to indicate that the ATTENDEE is
           only replying to a subset of the occurrences in the original
           TODO/REQUEST.
   Intended usage: COMMON

3.14 TODO/COUNTER Profile
   To: ietf-calendar@imc.org


Dawson                             39                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Subject: Registration of text/calendar MIME profile TODO/COUNTER
   Profile name: Counter an existing todo request
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based counter to an todo
           request. The message is sent from an a recipient of an
           existing todo request to the OWNER and/or ORGANIZER of the
           original todo request. The OWNER and ORGANIZER are ROLE
           parameter values for the ATTENDEE property.
   Profile type/subtype: TODO/COUNTER
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/counter_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/counter_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values



Dawson                             40                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DUE                Must be equal to or later than DTSTART.

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.


   Optional component properties:
        DTSTART, ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM,
        EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY,
        PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY,
        TRANSP, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to counter a request for a new todo. The message is sent from a
   recipient of an existing todo request to the originator of the todo
   request.
   Intended usage: COMMON

3.15 TODO/DECLINE-COUNTER Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/DECLINE-
           COUNTER
   Profile name: Decline todo request counter proposal.
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based decline of an


Dawson                             41                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           existing todo request counter proposal. The message is sent
           by the OWNER and/or ORGANIZER of the original, existing todo
           request to the originator of the todo request counter
           proposal. The OWNER and ORGANIZER are ROLE parameter values
           for the ATTENDEE property.
   Profile type/subtype: TODO/DECLINE-COUNTER
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/decline-counter_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/decline-counter_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if



Dawson                             42                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           Value represents the originator of the
                           counter proposal.

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        If specified: DESCRIPTION, DUE, EXDATE, EXRULE, LOCATION,
        PRIORITY, RNUM, RDATE, RRULE, RESOURCES, DTSTART, SUMMARY,
        indicate that the todo counter was declined because based on the
        value of these properties.
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to decline a counter proposal for an existing todo request. A
           MIME entity corresponding to this profile can only be sent by
           one of the recipients of an existing todo request. It is sent
           to the OWNER and/or ORGANIZER of the original, existing todo
           request. The optional properties in the message are specified
           to indicate the basis for declining the todo counter
           proposal. The OWNER and ORGANIZER are ROLE parameter values
           for the ATTENDEE property.
   Intended usage: COMMON

3.16 TODO/MODIFY Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/MODIFY
   Profile name: Todo modify
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based modification of a
           subset of the description of an existing calendar todo
           request. The message is sent from the originator of the


Dawson                             43                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           original todo request to one or more of the original
           recipients.
   Profile type/subtype: TODO/MODIFY
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/modify_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/modify_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.



Dawson                             44                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        DESCRIPTION        Value may be used as a secondary matching
                           field.

        DUE                Value may be used as a secondary matching
                           field.

        SEQUENCE           Value must be the ordinal of the revision
                           (i.e., 1st revision value would be _1_).

        UID                Value must be a globally unique value.
                           Property must be maintained by the
                           recipient.

        Any of the         Value corresponds to a modified property
        optional           value. If a property is specified with the
        properties.        unchanged, original value, it will still be
                           assumed to be a modified property value.


   Optional component properties:
        ATTACH, ATTENDEE, AALARM, CATEGORIES, CLASS, CREATED, DALARM,
        EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY,
        PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, DTSTART, STATUS,
        SUMMARY, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           by the originator of an todo request to send modifications to
           an existing todo. The MIME entity with this profile can only
           be sent by the OWNER and/or ORGANIZER of the original todo
           request. The OWNER and ORGANIZER are ROLE parameter values
           for the ATTENDEE property. This message is intended to be
           used to change a subset of the todo details. The preferred
           method of effecting a wholesale change for an todo is to send
           an TODO/REPLACE message or to send an TODO/CANCEL message for
           the original todo request followed by an TODO/REQUEST message
           the details for the new todo.
   Intended usage: COMMON

3.17 TODO/REPLACE Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/REPLACE
   Profile name: Replace an todo request.



Dawson                             45                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based update of the
           complete description for a calendar todo such as a meeting or
           an appointment. The message is sent from an originator (i.e.,
           OWNER or ORGANIZER) of an todo request to one or more
           intended recipients. By default, the originator is the OWNER
           of the todo. The OWNER is a ROLE parameter value for the
           ATTENDEE property.
   Profile type/subtype: TODO/REPLACE
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/replace_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/replace_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values



Dawson                             46                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each invited attendee.

        DESCRIPTION        None.

        DUE                Must be equal to or later than DTSTART.

        SEQUENCE           Required if not zero.

        UID                Value must be a globally unique value.
                           Property must be used by the recipient in
                           all responses to this request.


   Optional component properties:
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, DTSTART,
        EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY,
        PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to replace the description of an todo with the recipients of an
   existing todo request.
   Intended usage: COMMON

3.18 TODO/CANCEL Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/CANCEL
   Profile name: Todo cancellation
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based cancellation of an
           existing todo request. The message is sent by the OWNER
           and/or ORGANIZER of the original, existing todo request to
           the recipients of the original todo request. The OWNER and



Dawson                             47                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


           ORGANIZER are ROLE parameter values for the ATTENDEE
           property.
   Profile type/subtype: TODO/CANCEL
   Required header fields:


        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/cancel_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/cancel_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.



Dawson                             48                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        DESCRIPTION        Value used as a tertiary matching field

        DUE                Value used as a secondary matching field.

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        DTSTART, LAST-MODIFIED, PRIORITY, RELATED-TO (can be used to
        find linked todos), SUMMARY, URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to cancel an existing todo request. A MIME entity
           corresponding to this profile can only be sent by the OWNER
           and/or ORGANIZER of the original, existing todo request. In
           the event that the recipient application does not have the
           persistent UID property for the calendar component, the
           optional properties can be used to select the calendar entry
           corresponding to this request. The OWNER and ORGANIZER are
           ROLE parameter values for the ATTENDEE property.
   Intended usage: COMMON

3.19 TODO/DELEGATE Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/DELEGATE
   Profile name: Todo delegation
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based delegation of an
           existing todo request such as a meeting or appointment to an
           alternate individual. The message is sent by any of the
           attendees of an existing todo request to another delegated
           attendee and possibly the originator, OWNER, or ORGANIZER of
           the todo request. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property.
   Profile type/subtype: TODO/DELEGATE
   Required header fields:




Dawson                             49                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/delegate_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/delegate_.

        DAYLIGHT           Value must reflect DST observance at
                           originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        GEO
        TZ      (If date/time values in component properties are UTC).
        Any non-standard calendar property.
   Required component properties:



Dawson                             50                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Property Name      Value / Usage Constraints

        ATTENDEE           A property instance must be specified for
                           each delegated attendee. In addition, an
                           ATTENDEE instance must be specified for the
                           individual being delegated to.

        DESCRIPTION        None

        DUE                Must be equal to or later than DTSTART

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero

        UID                Value must be a globally unique value.
                           Property must be maintained by the
                           recipient.


   Optional component properties:
        ATTACH, AALARM, CATEGORIES, CLASS, CREATED, DALARM, DTSTART,
        EXDATE, EXRULE, LAST-MODIFIED, LOCATION, MALARM, RNUM, PRIORITY,
        PALARM, RELATED-TO, RDATE, RRULE, RESOURCES, STATUS, SUMMARY,
        URL
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
   to delegate an existing todo request to another person. A MIME entity
   corresponding to this profile may be sent by any of the attendees of
   an existing todo request. The properties from the original todo
   request must be included in the calendar component to assure that the
   delegated attendee has a complete specification of the delegated
   todo. This may include a description that reflects numerous revisions
   of the original request. The message must also contain an ATTENDEE
   property corresponding to the individual being delegated to.
   Intended usage: COMMON

3.20 TODO/RESEND Profile
   To: ietf-calendar@imc.org
   Subject: Registration of text/calendar MIME profile TODO/RESEND
   Profile name: Request an update or duplicate or an existing todo
           request.
   Profile purpose: Define a MIME Calendaring and Scheduling usage
           profile that allows for the message based request for an
           update or duplicate of the specification for an existing todo
           request. The message is sent by the recipient of an existing
           todo request to the OWNER and/or ORGANIZER of the original,
           existing todo request. The OWNER and ORGANIZER are ROLE
           parameter values for the ATTENDEE property.
   Profile type/subtype: TODO/RESEND
   Required header fields:




Dawson                             51                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



        Header Field Name  Value / Usage Constraints

        CONTENT-TYPE       Value must be _text/calendar_. Profile
                           parameter must be specified with the value
                           _todo/resend_.

        CONTENT-ID         Required on secondary body part/MIME
                           entities. Value must be globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.

        MESSAGE-ID         Required on the primary body part/MIME
                           entity. Value must be a globally unique
                           value. Recipient must maintain this value in
                           order to assure association for REPLY,
                           MODIFY, CANCEL, and DELEGATE operations.


   Optional header fields:
        CONTENT-LANGUAGE
        TRANSFER-ENCODING
        Any non-standard header field
   Calendar component: TODO
   Required calendar properties:


        Property Name      Value / Usage Constraints

        PROFILE            Value must be _todo/resend_.

        DAYLIGHT           Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect DST
                           observance at originator's location.

        PRODID             Value must be a unique identification of the
                           application that generated the calendar
                           object.

        TZ                 Property is required if the date/time values
                           in the component properties are specified in
                           local time. Value must reflect the time zone
                           of the originator's location. Optional if
                           the date/time values are specified in UTC.

        VERSION            Value must be _1.0_.


   Optional calendar properties:
        DAYLIGHT (If date/time values in component properties are UTC).
        GEO
        TZ      (If date/time values in component properties are UTC).


Dawson                             52                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


        Any non-standard calendar property.
   Required component properties:


        Property Name      Value / Usage Constraints

        RESPONSE-SEQUENCE  Required if not zero.

        SEQUENCE           Required if not zero.

        UID                Value used as the primary matching field.
                           Value is equal to the globally unique value
                           specified in the original request or any
                           subsequent modification request.


   Optional component properties:
        DESCRIPTION, DUE, DTSTART, LAST-MODIFIED, PRIORITY, RELATED-TO,
        SUMMARY, URL can be used as secondary matching fields for the
        todo.
        Any non-standard properties
   Profile special notes: A MIME entity with this profile type is used
           to request an update or duplicate of the specification of an
           existing todo request. A MIME entity corresponding to this
           profile can only be sent by the recipient of an existing todo
           request. It is sent to the OWNER and/or ORGANIZER of the
           original, existing todo request. In the todo that the
           recipient application does not have the persistent UID
           property for the calendar component, the optional properties
           can be used to select the calendar entry corresponding to
           this request. The OWNER and ORGANIZER are ROLE parameter
           values for the ATTENDEE property.
   Intended usage: COMMON

4. MIME registrations

   This memo is meant to serve as the basis for registration of a MIME
   Calendaring and Scheduling Content Type usage profile per [MIME-CAL].

4.1 Security Considerations

   Security issues are not discussed in this memo.

5. Example MIME Message Segments

   The following provides some example MIME message segments that
   demonstrate the usage of the message types defined by this [MIME-CAL]
   usage profile.

5.1 Simple event/request message

   The following example message segment issues an event/request that
   does not require any reply. The message is sent as a singular
   _text/calendar_ content type, body part.


Dawson                             53                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996



   From: jsmith@host1.com
   To: ietf-calendar@imc.org
   Subject: First IETF-Calendar Working Group Meeting
   MIME-Version: 1.0
   Message-ID: <id1@host1.com>
   Content-Type: text/calendar;Profile=event/request

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;EXPECT=REQUEST:ietf-calendar@imc.org
   DESCRIPTION:First IETF-Calendaring and Scheduling Working Group
      Meeting
   CATEGORIES:MEETING
   CLASS:PUBLIC
   DCREATED:19961022T083000
   SUMMARY:IETF Calendaring Working Group Meeting
   DTSTART:19961210T210000Z
   DTEND:19961210T220000Z
   LOCATION:San Jose, CA - Fairmont Hotel
   UID:guid-1.host1.com
   END:VEVENT
   END:VCALENDAR


5.2 Negotiated Event Request and Reply

   The following message segments provide an example of a message
   exchange that would involve negotiating a event request between two
   parties and the subsequent confirmation of the recipient of the
   request. In the example, dboss@host1.com is the OWNER of the request
   and nmploye@host2.com is the recipient of the request.

   The following message is an event request.

   From: dboss@host1.com
   To: nmploye@host2.com
   Subject: Your Annual Review
   MIME-Version: 1.0
   Message-ID: <id2@host1.com>
   Content-Type: text/calendar;Profile=event/request

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com
   DESCRIPTION:Employee: N. Mploye's 360 Review


Dawson                             54                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   CATEGORIES:MEETING
   CLASS:CONFIDENTIAL
   DCREATED:19960401T083000
   SUMMARY:Your Annual Review
   DTSTART:19960415T130000
   DTEND:19960415T131500
   LOCATION:Bldg. 01/Room 07-1A
   UID:guid-2.host1.com
   END:VEVENT
   END:VCALENDAR


   The following message is a counter proposal message.

   From: nmploye@host2.com
   To: dboss@host1.com
   Subject: Let's Reschedule The 360 Review
   Content-Type: multipart/mixed;boundary=example2
   MIME-Version: 1.0
   Message-ID: <id1@host2.com>

   --example2
   Content-Type: text/plain
   Content-Id:<part1.id1@host2.com>

   D:
   I can't make the scheduled 360 review. Remember
   it is tax-day! Besides, 15 minutes is not adequate.
   - M.

   --example2--

   --example2
   Content-Type: text/calendar;Profile=event/counter
   Content-Id:<part2.id1@host2.com>

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com
   DESCRIPTION:Employee: N. Mploye's 360 Review
   CATEGORIES:MEETING
   CLASS:CONFIDENTIAL
   SUMMARY:Your Annual Review
   DTSTART:19960416T130000
   DTEND:19960416T140000
   LOCATION:Bldg. 02/Room 00-99Z
   UID:guid-1.host2.com
   END:VEVENT
   END:VCALENDAR



Dawson                             55                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   --example2--


   The decline of the counter proposal and revised event request message
   follows:

   From: dboss@host1.com
   To: nmploye@host2.com
   Subject: Can't Do Your Reschedule
   Content-Type: multipart/mixed;boundary=example2
   Message-Id:<id3@host1.com>
   MIME-Version: 1.0

   --example2
   Content-Type: text/plain
   Content-Id: <part1.id3@host1.com>

   M:
   I understand that 4/15 is tax-day. Somehow, I am not
   surprised that you are doing your taxes at the last minute!

   The 4/16 reschedule date is okay, but we will have to do this
   in my office, not yours. We can also complete this in one half
   hour or less.
   - D.

   --example2--

   --example2
   Content-Type: text/calendar;Profile=event/decline
   Content-Id: <part2.id-3@host1.com>

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE:nmeploye@host2.com
   LOCATION:Bldg. 02/Room 00-99Z
   UID:guid-1.host2.com
   END:VEVENT
   END:VCALENDAR

   --example2--

   --example2
   Content-Type: text/calendar;Profile=event/request
   Content-Id: <part3.id-3@host1.com>

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00


Dawson                             56                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;EXPECT=REQUIRE;RSVP=YES:nmploye@host2.com
   DESCRIPTION:Employee: N. Mploye's 360 Review
   CATEGORIES:MEETING
   CLASS:CONFIDENTIAL
   SUMMARY:Your Annual Review
   DTSTART:19960416T130000
   DTEND:19960416T133000
   LOCATION:Bldg. 01/Room 07-1A
   UID:guid-1.host1.com
   SEQUENCE:1
   END:VEVENT
   END:VCALENDAR

   --example2--


   The event reply message confirming attendance follows:

   From: nmploye@host2.com
   To: dboss@host1.com
   Subject: Let's Reschedule The 360 Review
   Content-Type: multipart/mixed;boundary=example2
   Message-Id: <id-2@host2.com>
   MIME-Version: 1.0

   --example2
   Content-Type: text/plain
   Content-Id: <part1.id-2@host2.com>

   D:
   Well, I guess we can do this review quickly!
   - M.

   --example2--

   --example2
   Content-Type: text/calendar;Profile=event/reply
   Content-Id: <part2.id-2@host2.com>

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;STATUS=CONFIRMED:nmploye@host2.com
   UID:guid-1.host2.com
   SEQUENCE:1
   END:VEVENT
   END:VCALENDAR

   --example2--


Dawson                             57                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996




5.3 Event/request based on free-busy time search results

   The following example illustrates using free-busy time results to
   schedule an event with a group of individuals. The message sequence
   involves a free-busy/request from the orginator to a group of
   potential group of meeting attendees. The recipients return free/busy
   time results with the free-busy/reply message. The originator uses
   this information to generate an event/request. The messages are sent
   as singular _text/calendar_ content type, body parts.

   The following message segment is a free/busy time request to a group
   of potential meeting attendees.

   From: jsmith@host1.com
   To: jdoe@host2.com, imquik@host3.com
   Subject: Free/Busy Time Request
   MIME-Version: 1.0
   Message-ID: <id4@host1.com>
   Content-Type: text/calendar;Profile=free-busy/request

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE:jdoe@host2.com
   ATTENDEE:imquik@host3.com
   DURATION:P1H30M
   DTSTART:19961112T083000
   DTEND:19961112T170000
   UID:guid-3.host1.com
   END:VEVENT
   END:VCALENDAR


   The following two message segment are the resultant free/busy time
   data replies from the two potential meeting attendees. The two reply
   messages assume that the originator had access privileges within the
   recipient calendaring and scheduling applications to get the returned
   information. The first message segment is the free-busy/reply from
   the first recipient. Notice that the first recipient's calendaring
   and scheduling application only returns free time data.

   From: jdoe@host2.com
   To: jsmith@host1.com
   Subject: Free/Busy Time Request
   MIME-Version: 1.0
   Message-ID: <id5@host2.com>
   Content-Type: text/calendar;Profile=free-busy/reply

   BEGIN:VCALENDAR


Dawson                             58                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE:jdoe@host2.com
   DTSTART:19961112T090000
   DTEND:19961112T110000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:jdoe@host2.com
   DTSTART:19961112T130000
   DTEND:19961112T133000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:jdoe@host2.com
   DTSTART:19961112T141500
   DTEND:19961112T143000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:jdoe@host2.com
   DTSTART:19961112T150000
   DTEND:19961112T170000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   END:VCALENDAR


   This is the free-busy/reply from the second recipient. Notice that
   the second recipient's calendaring and scheduling application returns
   both free and busy time data. In addition, more information is
   returned than the first recipient's application.

   From: imquik@host3.com
   To: jsmith@host1.com
   Subject: Free/Busy Time Request
   MIME-Version: 1.0
   Message-ID: <id1@host3.com>
   Content-Type: text/calendar;Profile=free-busy/reply

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//ABC Software//NONSGML VaporCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com


Dawson                             59                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   DTSTART:19961112T083000
   DTEND:19961112T110000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com
   CATEGORIES:MISCELLANEOUS
   CLASS:PUBLIC
   DESCRIPTION:Lunch With The Boss
   DTSTART:19961112T110000
   DTEND:19961112T130000
   TRANSP:0
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com
   CLASS:CONFIDENTIAL
   DTSTART:19961112T130000
   DTEND:19961112T133000
   TRANSP:0
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com
   DTSTART:19961112T133000
   DTEND:19961112T141500
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com
   CATEGORIES:PHONE CALL;PROJECT
   CLASS:PUBLIC
   DESCRIPTION:Weekly Project Status Call
   DTSTART:19961112T141500
   DTEND:19961112T143000
   TRANSP:0
   UID:guid-3.host1.com
   END:VEVENT
   BEGIN:VEVENT
   ATTENDEE:imquik@host3.com
   DTSTART:19961112T143000
   DTEND:19961112T170000
   TRANSP:1
   UID:guid-3.host1.com
   END:VEVENT
   END:VCALENDAR


   The following message is the event/request message that uses the free
   time results from the previous messages.

   From: jsmith@host1.com


Dawson                             60                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


   To: jdoe@host2.com, imquik@host3.com
   Subject: New Project Discussion
   MIME-Version: 1.0
   Message-ID: <id5@host1.com>
   Content-Type: multipart/mixed;boundary=example3
   MIME-Version: 1.0

   --example3
   Content-Type: text/plain
   Content-Id: <part1.id-5@host1.com>

   Folks:

   We have to more quickly on this new Internet C&S standard. I want
   meet with you all and draft a project plan that (a) will result in
   a product in the channels by year-end and (b) we can take to the
   Board after COMDEX in November.

   - John.

   --example2--

   --example2

   Content-Type: text/calendar;Profile=event/request
   Content-Id: <part2.id5@host1.com>

   BEGIN:VCALENDAR
   DAYLIGHT:TRUE;-06:00;19960407T025959;19961027T010000;EST;EDT
   PRODID:-//RDU Software//NONSGML HandCal//EN
   TZ:-05:00
   VERSION:1.0
   BEGIN:VEVENT
   ATTENDEE;EXPECT=REQUIRE;RSVP=YES:jdoe@host2.com
   ATTENDEE;EXPECT=REQUIRE;RSVP=YES:imquik@host3.com
   SUMMARY:New Project Discussion
   DESCRIPTION:New Project D
   CATEGORIES:MEETING;PROJECT
   CLASS:PRIVATE
   DCREATED:19961104T083000
   DTSTART:199611125T153000
   DTEND:19961112T170000
   LOCATION:Big Conf. Room
   UID:guid-4.host1.com
   END:VEVENT
   END:VCALENDAR

   --example2--








Dawson                             61                 Expires June 1997


Internet Draft       MIME C&S Content Type Profile    November 26, 1996


6. Acknowledgments

   A hearty thanks to the IETF Calendaring and Scheduling Working Group
   and also the following individuals who have participated in the
   drafting, review and discussion of this memo:

   Roland Alden, Harald T. Alvestrand, Denis Bigorgne, John Binici, Bill
   Bliss, Andre Courtemanche, Dave Crocker, Alec Dun, Ross Finlayson,
   Randell Flink, Ned Freed, Patrik Falstrom, Anik Ganguly, Chuck
   Grandgent, Mark Handley, Steve Hanna, Paul B. Hill, Mark Horton,
   Bruce Kahn, C. Harald Koch, Theodore Lorek, Keith Moore, Cecil
   Rhodes, Chris Newman, Ralph Patterson, Pete Resnick, Keith Rhodes,
   Robert Ripberger, Andras Salamar, Vinod Seraphin, Ken Shan, Andrew
   Shuman, William P. Spencer, Mark Towfiq, Robert Visnov, James L.
   Weiner, Mike Weston, William Wyatt.

7. Bibliography

   [RFC1521]  N. Borenstein and N. Freed, "MIME (Multipurpose Internet
   Mail Extensions) Part One: Mechanisms for Internet Draft  UTF-825
   July 1996 Specifying and Describing the Format of Internet Message
   Bodies", RFC 1521, Bellcore, Innosoft, September 1993.

   [MIME-CAL]  F. Dawson, _MIME Calendaring and Scheduling Content
   Type_, Internet Draft, draft-dawson-csct-00.txt, IBM Corporation,
   October 1996.

8. Author's Address

   The following address information is provided in a MIME-VCARD,
   Electronic Business Card, format.


   BEGIN:VCARD
   FN:Frank Dawson
   ORG:IBM Corporation
   ADR;WORK;POSTAL;PARCEL:;APNA/CC-303/Bldg. 002;3039 Cornwallis Rd;
     Research Triangle Park;NC;27709;USA
   TEL;WORK;MSG:+1-919-254-5861
   TEL;WORK;FAX:+1-919-543-6822
   EMAIL;INTERNET:fdawson@us1.ibm.com
   EMAIL;HOME;INTERNET:fdawson@earthlink.net
   URL;HOME:http://home.earthlink.net/~fdawson
   END:VCARD












Dawson                             62                 Expires June 1997