[H.323 Mobility:] MD-105 uploaded

Jaakko Sundquist jaakko.sundquist at NOKIA.COM
Wed Aug 2 08:18:17 EDT 2000

Hi, FX:

I like your approach that you have stated here in the email.

With respect to the draft APC.xxx that you have proposed, I have few

1. At present in H.323, there are mechanisms in place how the communications
need to be made between the GKs or between the BEs or between the GK-BE and
BE-GK when the user remain in one GK (or GK-BE) can communicate for
resolving the information with another user located within another GK (or

That is, the communication is made via the GK (or GK/BE) to locate another
GK (or GK/BE) where is use is residing (for resolving information or placing
a call).

2. The base H.323 spec and H.225.0 Annex G spec clearly provide those
mechanisms as stated in item 1.

However, your contribution appears to suggest that a GK (or BE) will use the
VLF and HLF to locate another GK (or BE) where the user resides (currently).
My assumption is that there can be HLF-to-HLF communications by-passing the
GK-to-GK (or GK/BE-BE/GK) communications for resolving the information.

It has been mentioned in my earlier emails that HLF-to-HLF communications is
not an extension of H.323 protocol.

Therefore, it appears to me that your contribution does not follow the model
that have been suggested in items 1 and 2 per H.323 and Annex G.

Am I missing anything?

Best regards,
Radhika R. Roy

-----Original Message-----
From: Francois-Xavier Derome [mailto:Francois-Xavier.Derome at ALCATEL.FR]
Sent: Tuesday, August 01, 2000 5:44 AM
Subject: Re: [H.323 Mobility:] Usage of H.225 Annex G in H.323 Annex H &
a question about BEs

I tried to follow your discussion on annex G.
Can we split the problem in 2 parts :
     - the mobility management
     - the call control
Concerning the mobility management, I think we can define the rules we want
and there should be no restriction from the current annex G limitation.

Concerning the call management, we MUST follow the current annex G and
that's what I wanted to make clear in my APC.
I think one solution could be for the BE in the mobile domain to put in the
routeinfo field  a sendAccessRequest to let him resolve the new location
with the HLF


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

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

More information about the sg16-avd mailing list