Hi, Everyone:

In addition to uploading of the contributions, I feel that it would be better we could start email discussion on these contributions if possible. It may save time in the upcoming Portland meeting. In this connection, I am enclosing the summary of the two contributions as follows:

APC-1932: Comments on H.323 Annex H (MTD-101b) Abstract

Comments on H.323 Annex H have been provided to modify the text and figures of MTD-101b. The comments have been provided in two categories: General and Specific. The general comments are applicable for the entire document while the specific comments are to be considered case by case basis for each section.

It has been clearly mentioned how AT&T contributions APC-1926, D.354, APC-1770, and others can be used to take care of all comments.

These comments were also provided to the SG16 email reflector, and it is believed that these comments were accepted because no counter technical arguments were received in the email reflector explaining the fact why these comments were not acceptable.

APC-1926: H.323 Intra-Zone Mobility Management using the AuF and HLF Abstract

We have discussed how the network address (e.g., IP address) can be acquired using different mechanisms (e.g., DHCP, mobile IP, or other schemes) by an H.323 mobile entity if it moves from one place to another. Once the network address is obtained after being connected to a network, it can listen to the mobile gatekeeper advertisement (MGA) message for discovering the GK in a well-known multicast port (alternatively, the GRQ message can also be sent to discover the GK). If needed, the MGA can also be unicast to the mobile entity although the process may not be so dynamic as in the case of the multicast.

We have shown that a new GK advertisement message (MGA) [3] is the most efficient way of discovering the GK in a highly as well as relatively less mobile environment: Cell-based wireless network, wireless LAN, and/or wire-line network. In addition, the extended GRQ/GCF/GRJ [3] messages can also be used in certain situations when MGA message is not received within certain time interval. The combination of the MGA and GRQ message scheme makes the GK discovery most efficient and reliable for mobile communications environments.

It has been clearly depicted how the extended RRQ [3] message needs to be used to take care of many options that a mobile entity may like to use for service provisioning in static mode because the mobility service related parameters need to be stored in the HLF. In this situation, a GK needs to access the HLF directly, and does NOT need to use the VLF. The direct communications between the home GK and the HLF may also be needed for storing and retrieving the mobility related information when the mobile remains in its home network point of attachment (home-NPoA) or if it moves from its home network to a foreign (visiting/target) network in its home zone because an H.323 mobile entity that remains within a home zone is NOT considered a "visitor" or "foreigner" by the home GK.

The primary services that are needed are the discovery of the mobile gatekeepers (GKs), registration with the GK by the mobile entities, location updates for mobile's visiting, home, and visited network address along with interaction of the authentication function (AuF) and home location function (HLF) as the mobile entity changes its point of attachments (e.g., network point of attachment).

We have discussed some issues as follows: Should we include the service related profile in the RRQ message for dynamically service provisioning in the HLF and new messages between the GK and AuF/HLF?

Finally, we have shown communications message flows for location updates for intra-zone communications to mange the mobility of mobile entities. It may be observed that the communications to the AuF and HLF entities are performed via the GK.

Best regards,

Radhika R. Roy AT&T +1 732 420 1580 rrroy@att.com

-----Original Message----- From: Roy, Radhika R, ALCOO Sent: Friday, August 11, 2000 9:47 AM To: 'Sakae OKUBO' Subject: APC-1926 and APC-1932

Dear Mr. OKUBO;

Kindly upload the enclosed APCs (APC-1926 and APC-1932).

Best regards, Radhika R. Roy AT&T +1 732 420 1580 rrroy@att.com

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