Share via

2.3.3.10 attOwner Attribute Handling by the TNEF Reader

  • Article

If the message is either a meeting request or meeting cancellation (from the organizer, who is creating or deleting a meeting), the TNEF Reader SHOULD decode the attOwner attribute, as specified in section 2.1.3.3.16, into the PidTagSentRepresenting_XXX properties, as specified in section 2.1.3.1.1.

If the message is a meeting response of any type (from attendee, accepting, declining, and so on), the TNEF Reader SHOULD decode the attOwner attribute into the PidTagReceivedRepresenting_XXX properties, as specified in section 2.1.3.1.1. The decoding process used is implementation-dependent, as long as the decoded property values match those that were originally encoded. For details about how to construct the PidTagReceivedRepresentingEntryId property, see [MS-OXOMSG] section 2.2.1.25.

The TNEF Reader MUST set the PidTag{Sent | Rcvd} EntryId property and SHOULD decode the attOwner attribute into the other PidTag{Sent | Rcvd} Representing properties.