Hi, Jaakko:
Pl. my comments below:
Thanks, Radhika
-----Original Message----- From: Jaakko Sundquist [SMTP:jaakko.sundquist@nokia.com] Sent: Monday, April 17, 2000 10:34 AM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: [H.323 Mobility:] Comments to various mails
Hi Radhika,
Comments embedded...
Hi, Jaakko:
I am providing a very quick response because we will have the conf call within 45 minutes.
Same here...
Second, the H.323 mobility protocol proposed by AT&T, Alcatel or others do NOT tie to any topology. The topology shown has come into play to provide descriptions so that people can understand, and we can say all requirements are met no matter what the topoloy is. For example, your contribution and references figures - we need to see whether all toplopies can be satisfied using the SAME protocol.
I did not claim that the contributions were tied to any topology. I was simply questioning the need to define or use the terms: home/visited network/zone.
[Roy, Radhika R] There shall be ONLY reference to the network address [home/visiting/visited/target] because "network" itself does NOT mean anything clearly. It is an OPTION, not mandatory. The contributions explain that what the benefits are:
1. To hide network address as the mobile moves from one place to another if needed. For example, a mobile may communicate with the other party without revealing its present network point of attachment, while the other party may be assuming the mobile is still in its home network point of attachment. The mobile can keep its privacy. (Mobile also allows to keep privacy.)
2. In multimedia communications environment, it may allow, if needed, to treat different media differently. For example, audio and/or video may be directed to the mobile's present network point of attachment, while data may be sent to my home network point of attachment (for storage or other purposes).
3. A service provider may be able to DIFFERENTIATE services based on the home network point of attachment (because a service may be subscribed in mobile's home domain/zone with a certain agreement and mobile's home network point of attachment may provide one of the most IMPORTANT identities to accomplish this).
4. To Facilitate for keeping track of the mobile user's profile based on the home network point of attachment in addition to other parameters stored in the HLF/VLF by the service provider.
5. It may so happen that a mobile may reveal the network point of attachment (e.g., audio) while it may not reveal the network point of attachment for data because of security reason. As a result, the communications may happen like this: Real-time audio and video are coming directly between the calling parities while data can shared from mobile's home network point of attachment without revealing its address.
6. There can other benefits in keeping its "home" network point of attachment known as a reference point (similar "benefits" along the line "home administrative domain").
7. In the same token, visiting/visited/target network point of attachment is useful to keep references in managing the mobility especially by the service providers. For example, it the target network point of attachment can be predicted or supplied by the mobile user at the time of registration, a service provider can make planning of the resources ahead of the time to provide services before the mobile can move in that zone/domain.
With respect to home zone/GK, it is another reference from mobility management point of (similar "benefits" along the line "home administrative domain").
Third, no contribution (AT&T, Alcatel, or Ericsson) has suggested that HLF or VLF has to belong to a zone or by couple of zones or otherwise.
This is exactly why I do not see any point in defining home/visited zone. Or if we do define them the home zone should be clearly defined in such a way that it does not imply that the HLF is a part of the home zone, but home zones are all the zones that belong to the Home Administrative Domain.
[Roy, Radhika R] This is helpful from mobility management point of view because association is made via the GKs. Yes, you are right that home zone belongs to the home adm domain, but not ALL zones of a given adm domain are the mobile's home zone. There is only ONE zone is the mobile's home zone. This distinction is very helpful from mobility management point of view in H.323.
Yes, I agree the home zone definition should NOT interfere with the definition of HLF. An HLF may contain the information of many one or many home zones of many mobile users of a given Adm domain. Now HLF is a database behind the GK that keeps the permanent information including mobile's home network point of attachment.
I hope that you will NOT mis-interpret the intend of the main idea behind the contributions.
I don't think so and I do think that we have some valuable contributions for this teleconference and they will certainly help the progress of the work.
[Roy, Radhika R] I appreciate. I am sorry to see that I could not choose the right word. I take my comments off.
-Jaakko