Dear Mr. Okubo,

As you pointed out, the item (3) still needs to be worked on and the intention is what you mentioned during the end of your mail. In addition, the Presence signalling shall be carried out using the genericData field in RAS messages (using H.323 Generic Extensibility Framework), instead of adding new IEs to RAS messages. The ASN.1 synatx of CommunicationState may be further enhanced/modified to be more generic and reflect the necessary information that Presence is required to support (e.g user information in a standard presence format). The work on this is to be carried out further and presented as AVDs in subsequent SG16 meetings.

best regards Manoj Paul.

-----Original Message----- From: OKUBO Sakae [mailto:okubo@GITI.WASEDA.AC.JP] Sent: Thursday, April 12, 2001 8:10 PM To: ITU-SG16@mailbag.cps.INTEL.COM Subject: Question on presence

Dear Mr. Manoj Paul,

I am trying to understand the concept of H.323 presence. In AVD-2087, communication states to be exchanged are listed as:

1) status of the user, 2) its reachable address, 3) user's means of communication, including the preferred mode.

The ASN.1 syntax CommunicationState in AVD-2087 includes newAliasAddress (corresponding to 2) above, I understand) and availableForCall, busy (both corresponding to 1) above).

I wonder how 3) is handled. Is it going to be added in the course of work? Or as H.323 has the H.245 capability exchange procedure, H.323 presence needs only 1) and 2) above? Or still we would like to indicate e.g. being ready to communicate with fixed H.323 terminal at office, mobile phone like H.323 or H.323 on PDA on the road before the actual communication?

Best regards,

OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo@giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com