- sg16-avd - lists.packetizer.com

[H.323 Mobility:] Comments to various mails
by Jaakko Sundquist 17 Apr '00

17 Apr '00

Hi all, It certainly seems that we have some discussion going on in the reflector. I haven't read the mails since thursday and there really has been a flood of them, so I'll try to gather all my comments in this message. Radhika, thanks to our discussions last week I have finally understood your intentions on a couple of issues. First the issue of home/visited network. I think I now understand what you mean when you say that a zone may include more than one network (a part of the zone runs on IP and another part on ATM for instance), but I still fail to see, why we should define such concepts, the H.323 layer should not really be concerned what the underlying network type is. Furthermore, you made the argument that since H.323 has defined the topology of the H.323 systems in terms of network address/zone/domain we should also define home/visited network address/zone/domain. I do not agree on this. So far I have not seen any reason for defining any other of these concepts than the already defined Home/Visited Administrative Domain. The only important issue with these home/visited concepts in my mind is the location of the HLF of the user and I would argue that the entity administering some part of the network should also own the HLFs in that part of the network. Thus defining the Home Administrative Domain of a user as the Domain that contains the HLF of the user makes sense, but since we are not binding the HLF to any particilar zone or network we do not need to define or use the terms home zone/network. Secondly, I think I understand, albeit somewhat vaguely, now, what exactly you are meaning with Intra-zone, Inter-zone and Inter-domain communications. The difficulty with these terms in the context of Annex H is, however, that traditionally these terms have been used in H.323 only when there is a call involved. In other words, we haven't talked about e.g. an Inter-zone registration procedure previously in H.323. The problem when using (at least) the terms Intra/Inter-zone with the Annex H work is that we have not made any assumptions about the relationships of the mobility functional entities and zones, i.e. a VLF or a HLF is not defined to be a part of any zone. Thus, when you are talking about Inter-zone or Inter-domain communications for e.g. the terminal/user registration or location updating procedure, what exactly are you meaning? My guess is that the division that you are referring to, is based on the previous location of the User, i.e. in the same zone or another zone, am I correct? Anyway, I'm quite sure that we need to address all the issues that you are thinking of, but dividing the work in steps defined by the Intra/Inter-zone/domain communications is not the best approach in my opinion. Steve, I think that we need to clarify the issue of home/visited domain execution of services, so that both of these models are understood by all the members of the group. Maybe some co-work could be done by us? As for the discussion on "not breaking up the current H.323 model", I'll just say that I share the opinion that all registrations, etc. should be done via the gatekeeper in order to preserve the old H.323 model. I see no point in doing the registration straight to the VLF. I'm not quite sure, what Steve's contribution was all about in this respect, but we'll probably be discussing that in the teleconference. ------------------------------------------------ Jaakko Sundquist * +358 50 3598281 * Audere est Facere! jaakko.sundquist(a)nokia.com * ------------------------------------------------

1 0

Re: Q12-14/16 Rapporteur meeting in Osaka
by Sakae OKUBO 16 Apr '00

16 Apr '00

Dear Mr. Reddy, >Please assign me an APC number for " H.246 Annex E white paper draft" APC-1757 has been allocated to your draft white contribution. Best regards, Sakae OKUBO *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp ***********************************************************

1 0

unsubscribe
by Henry H. Wong 16 Apr '00

16 Apr '00

unsubscribe Best Regards, Henry H. Wong, Chairman CEO, SS8 Networks Inc. "SS8 is the signaling and service solutions for the Internet, just like SS7 for the PSTN" E-mail: Henry(a)SS8Networks.com Cellular #: (408) 234-6810 Worldwide Headquarters: Silicon Valley 2025 Gateway Place, Suite 318, San Jose, CA 95110 My Office: (408) 501-2108 Fax: (408) 501-2101 Main #: (408) 501-2100 Advanced R&D Center: Silicon Valley North 135 Michael Cowpland Drive, Suite 200, Kanata, Ontario, K2M 2E9, Canada My Office: (613) 592-3798 Fax: (613) 592-9634 Main #: (613) 592-8450 ***************************************************************************** This document, and any documents attached to this e-mail, contain information from SS8 Networks Inc., and are for the sole use of the above individual or entity. Such information may be privileged, confidential or exempt from disclosure under law. Any other dissemination, distribution or copying of this communication is strictly prohibited. Please notify us immediately by telephone if you are not the intended recipient and return the original message to us at the above address. We will reimburse your reasonable phone and postage expenses for doing so. *****************************************************************************

1 0

Comparison of Mobility Contributions and Combined Proposal that i s Consistent with H.323 Standard
by Roy, Radhika R, ALARC 16 Apr '00

16 Apr '00

Hi, Everyone: It is an attempt to streamline our discussions for the conference call (April 17) so that we can save time while I am my inputs. We have seen some contributions in solving the problems for intra-zone (AT&T), inter-zone/intra-domain (Alcatel, AT&T, and Ericsson [?]) and inter-domain (Alcatel and Ericsson) communications. Here are some high-level comments and proposed combined proposal related to those contributions: 1. Intra-Zone, 2. Inter-Zone/Intra-Doamin, and Inter-Domain. 1. INTRA-ZONE AT&T contribution (MD-017) deals with the intra-domain communication that describes: a. Mobile communications environments, b. Discovery, c. Registration, and d. Intra-Network Roaming. However, some aspects of Alcatel's contribution (MD-0XX) can be applicable for intra-zone communications as well. A. Mobile Communications Environment The highly cellular (wireless)-based mobile environment where 100s and 1000s of users entering and leaving a cell requires that the new discovery message like MGA (AT&T's contribution MD-017) is needed to discover the GK for signaling EFFICIENCY (while GRQ either multicast or non-multicast can be used in complimentary manner if the MGA message is not received within a certain period of time). It may be mentioned that mobile IP also uses the similar mechanism in the network layer for discovery. B. Discovery MGA message, which is appropriate in a highly mobile environment as stated in A, will discover the GK. The same discovery mechanism can be used for all cases: Intra-Zone, Inter-Zone, and Inter-Domain. Proposal to accept the New MGA Message for Discovery: · Let us accept the new MGA message for discovery (in combination with GRQ/GFC/GRJ message with multicast/non-multicast) that can be used for all cases: Intra-Zone, Inter-Zone, and Inter-Domain. C. Registration Like Rec. H.323 , this contribution is consistent with the fact that the association of the mobile entities has to be made with the GK through the GK. The same registration mechanism can be used for cases: Intra-Zone, Inter-Zone, and Inter-Domain. However, we believe that the HLF identities, like Alcatel's contribution (and VLF identities like Ericsson's to make their proposal consistent with the H.323 standard) contribution can also be passed during the registration process. The important point that I am making is that the HLF and VLF Ids, previously not known to the mobile, can be passed to the mobile by the GK during the registration confirmation (RCF). Proposal for the extended RRQ/RCF/RRJ: · The proposal is that we can combine AT&T, Alcatel, and Ericsson proposal together to create the new extended RRQ, RCF, and RRJ message that can be used, as indicated above, for the mobile environment in all cases: Intra-Zone, Inter-Zone, and Inter-Domain. 2. INTER-ZONE (INTRA-DOMAIN) Both AT&T (MD-018) and Alcatel (MD-0XX) address the inter-zone/intra-domain communications that are consistent with the H.323 standard. A. Discovery AT&T (MD-018) describes the discovery of the GK using the MGA message if the GK is not priori known. Proposal: · Let us accept the new MGA message as stated above for discovery in the highly mobile environment. B. Registration and Location Updates For registration, both AT&T (MD-017) and Alcatel (MD-0XX) contribution are in consistent with the H.323 standard because the association of the mobile entities are done via the GK. However, there some minor variations in these two proposals that seem to be complementary. For example, AT&T contribution describes that there are couple of possible ways for exchanging the mobility related information: Extension of LRQ or Creation of New Mobility Binding Messages for intra-domain (Extension of accessRequest Message or Creation of New Mobility Binding Messages for inter-domain). Ericsson's proposal shows that we need to extend the LRQ message. In addition, we can add HLF Ids as stated earlier (we can also reconcile Ericsson's proposal to pass the VLF Ids during the registration). It has to be clarified whether the pre-call setup messages like ARQ/ACF/ARJ messages to be extended or not. Although Alcatel's proposal shows only one registration scenario with one HLF architecture, it is also possible to have other scenarios as shown in AT&T's contribution using the SAME protocol. · Proposal for the extended RRQ/RCF/RRJ: The proposal is that we can combine AT&T, Alcatel, and Ericsson proposal together to create the new extended RRQ, RCF, and RRJ message that can be used, as indicated above, for the mobile environment in all cases: Intra-Zone, Inter-Zone, and Inter-Domain. · Proposal for Location Updates related to Mobility: The proposal is that we can combine AT&T and Ericsson proposal together to have all the mobility parameters for the mobile users in the signaling messages for intra-domain communications either creating new mobility binding messages or extending the LRQ/LCF/LRJ Messages (advantages and disadvantages of the two methods can seen in AT&T proposal). · Proposal for ARQ Message: We need to investigate whether the ARQ/ACF/ARJ messages to be extended. C. Call Establishment Once we decide about discovery, registration, and location update messages, the call establishment can be done in several ways. The call scenario shown in Alcatel's proposal is one of the reasonable ways to do this. AT&T may also like to explore the alternative call scenarios in the subsequent contributions as well so that we can discuss pros and cons for each. The most important conclusion seems to be that we do NOT need to create any new signaling messages for the call establishment. 3. INTER-DOMAIN Both Alcatel (MD-0XX) and Ericsson (MD-0XX) have contributions in this area. AT&T plans to bring new contributions in this area. However, it appears that Alcatel's contribution is consistent with the H.323 standard because it uses the pre-call setup messages (e.g., ARQ) in association with the GK (which is foundation of the H.323 standard). It is very important to note that Alcatel's proposal shows that the new locationQuery message is going through the BEs of two different administrative domains. In AT&T proposal (MD-018 and earlier contributions), it has been suggested that we need to investigate whether can extend the accessRequest message of H.225.0 Annex G because these message sets are very efficient. However, the mobility related parameters proposed in AT&T contributions (MD-017 and MD-018) should also be present. Ericsson's proposal appears that it is NOT associating itself with the GK for registration. It is rather by-passing the GK and is registering with the VLF directly. It seems to be that it is breaking the basic foundation of the H.323 standard. It is almost like creating a NEW protocol. Alcatel's proposal and discussions in AT&T's contributions reveal the fact that we do not need to break the foundation of the H.323 standard to extend H.323 to support mobility. I have also shown how Ericsson's proposal can be accommodates in the context of AT&T's and Alcatel's proposals for registration messages. · Proposal: · To accept the logical step to associate the information of the H.323 mobile users for registration via the GK as shown in AT&T's and Alcatel's proposals that conforms to the H.323 standard. · Decide whether we extend the accessRequest messages of create new messages for mobility management in H.225.0 Annex G. · To include all mobility related parameter as proposed in AT&T's, Alcatel's, and Ericsson's proposal. I like to see that other members also provide their comments. Best regards, Radhika R. Roy AT&T +1 732 420 1580 rrroy(a)att.com

1 0

Steps for Extensions for Mobility Consistent with H.323 Standard
by Roy, Radhika R, ALARC 16 Apr '00

16 Apr '00

Hi, Everyone: The stake for extensions of H.323 to support mobility is so great that people who are familiar with H.323 will be able to understand very easily. Many of those people may not be attending the H.323 Ad Hoc Mobility Group meetings, but they can foresee what I am talking about. 1. Association through Registration with the GK The registration of H.323 entities with the GK establishes the association such that all information related to terminals/users is passed to the GK. The GK becomes the ONLY source where the information related to the H.323 entities is available. It is very important to note that H.323 does NOT allow any other entities other than the GK to have the association with registration of the endpoints (e.g., terminals) through registration. This fundamental concept has allowed to define a zone that is managed by a GK. So, the zone has become the building block for H.323. Later on, we have defined domain that contains one or more zones. All other entities (e.g., BEs) collect this information from the GKs and transfer that information between the BEs in a more efficient way. Please note that even the BEs does NOT have the association with the endpoints (e.g., terminals). Therefore, the model for extensions of H.323 to support mobility MUST be consistent with Rec. H.323. 2. Intra-Zone and Inter-Zone Communications When the mobile users move between the cells, the mobility is primarily becomes intra-zone communications because many cells are expected to be controlled by a single GK. At best, two GKs may be involved when mobile users move between the cells. So, intra-zone solution need to be used for inter-zone communications. These solutions are complementary. So, we have to address the intra-zone communications first before we move to the inter-zone solution. Once we finish intra- and inter-zone communications, we will then move to inter-domain communications because inter-domain communications solution is dependent on the other two. 3. Inter-Domain Communications In some situations, two BEs of two administrative domains may be involved if mobile users move between the cells. H.225.0 Annex G defines inter-domain communication via BEs ONLY. This standard does NOT allow to communicate between the two administrative domains with any other entities other than the BEs. H.323 mobility solution MUST be consistent with Rec. H.225.0 Annex G. 4. Problems for Not Solving Problems Step-by-Step One bright example is H.225.0 Annex G. BEs are allowed to use the efficient message sets like accessRequest and others, while the GKs cannot. Even it cannot be used between the GK and the BE. The model is broken from end-to-end perspective. The future of H.323 seems to be very bleak because of this fundamental problem. Who is to blame? This has created a fundamental problem to make progress in H.323. Now people are trying to bring contributions to use those efficient Annex G message sets for intra-zone and inter-zone communications, but these contributions are not being accepted because of opposition by a very few. Do we want create the same problem for H.323 mobility by-passing the step-by-step method creating highly inconsistent solution? Best regards, Radhika R. Roy AT&T H.323 Ad Hoc Mobility Group

1 0

Re: [H.323 Mobility:] questions on MTD-016
by Roy, Radhika R, ALARC 16 Apr '00

16 Apr '00

Hi, Steve: I guess that you did not get my point exactly. It is NOT exactly where the "service" to be executed. It is user's choice whether certain things to could be perfumed as their choices (for example not to reveal addresses while NOT moving - for example mobile IP permits) etc. Now where the service to be permitted, we may have another debate. There should be flexibility: Home Domain vs Foreign Domain and other criteria. As I explained earlier, what is meant by network in H.323. Please see the email sent in response to Jaakko's. I would be pleases to explain in terms of home/foreign (visiting/visited/target) domain/zone/network address. For the role of the GK in H.323 is clear. There is no ambiguity. Please see my email that will be sent very shortly. Please also see email that will be shortly how we can reconcile all contributions together describing the role of GKs, HLFs, and VLFs: AT&T, Alcatel and yours (Ericsson). Best regards, Radhika R. Roy AT&T -----Original Message----- From: Stephen Terrill [mailto:stephen.terrill@ericsson.com] Sent: Sunday, April 16, 2000 5:11 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: [H.323 Mobility:] questions on MTD-016 Hi Roy, I still don´t understand why it is a "users" choice where the "services" are executed - I would have thought that this would be networks choice - and the means for doing that is what we are now discussing. Can you please clarify why a user "MAY" which to decieded this. One thing that is now clear is that there are different expectations of the roles of the gatekeepers, VLFs, HLFs etc expressed amongst the participants of the list - and this has to be clarified. Regards, ..//steve "Roy, Radhika R, ALARC" wrote: > Hi, Steve: > > In H.323, GKs are the communication entities thorough which registration and > other services are obtained by users while VLFs and HLFs are used ad > databases to store the information that are appropriate related to the > mobility management. > > In H.323, a user is always associated with a GK through registration, and a > GK manages a zone where all its H.323 registered users reside. In addition, > a GK also manages resources of the zone. > > Please also see the mobility management information flows in AT&T > contributions MD-017 and MD-018 how the GK is involved to resolve > information via VLF and HLF. > > A mobile user MAY like to differentiate between a home GK and a foreign GK > (security and many other reasons). It is an OPTION, not mandatory. > > Hope this clarifies your questions. > > Best regards, > Radhika > > -----Original Message----- > From: Stephen Terrill [mailto:stephen.terrill@ERICSSON.COM] > Sent: Friday, April 14, 2000 8:02 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: [H.323 Mobility:] questions on MTD-016 > > Hi Roy, > > Can you please clarify why the gatekeeper selected for the services is a > "user" issue? > > Regards, > > ..//steve > > "Roy, Radhika R, ALARC" wrote: > > > Hi, Vineet and Steve: > > > > I like to add couple of points with respects to your emails as follows: > > > > HLF: > > > > It is interesting to note that there appears to be an "implicit" > assumption > > that there is only one HLF in a domain (no matter what happens in the > > future). > > > > Let us NOT make our protocol "hard-wired" like this. > > > > The protocol should be flexible enough to accommodate one or multiple HLFs > > in a domain. > > > > If one wants to choose one HLF per domain, it MUST be left as an > > implementation issue, NOT a protocol issue. > > > > Home GK: > > > > In the same token, if one wants to declare a GK as its home GK, this > option > > MUST be provided to a user. It is a choice that MUST be given to a user. > If > > anyone does NOT like this option, they MAY not use it. > > > > Home Network/Network Address: > > > > In the same token, if anyone wants to declare a network address as its > home > > network, this option MUST also be provided. > > > > GK Discovery: > > > > The "old" inefficient GRQ discovery mechanisms may not be the only OPTION > to > > discover the GK. in a highly mobile cellular environment. An alternative > > mechanism, like MGA message can be listened to discover the GK as well. > > > > Best regards, > > Radhika R. Roy > > > > > -----Original Message----- > > > From: Kumar, Vineet [SMTP:vineet.kumar@INTEL.COM] > > > Sent: Thursday, April 13, 2000 4:34 PM > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > Subject: Re: [H.323 Mobility:] questions on MTD-016 > > > > > > Steve, > > > > > > Thanks for your reply. My comments are embedded in the email below. > > > > > > vineet > > > > > > -----Original Message----- > > > From: Stephen Terrill [mailto:stephen.terrill@ERICSSON.COM] > > > Sent: Thursday, April 13, 2000 4:42 AM > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > Subject: Re: [H.323 Mobility:] questions on MTD-016 > > > > > > > > > Hi, > > > > > > I shall try to answer some of these questions below. > > > > > > Regards, > > > > > > ..//steve > > > > > > > > > > > > "Kumar, Vineet" wrote: > > > > > > > Stephen, > > > > > > > > I have a couple of questions on your contribution MTD-016. These are: > > > > > > > > 1. H.323 already has mechanisms for discovering the gatekeeper. Are > you > > > suggesting in your contribution that the terminal should discover the > VLF > > > instead of the visiting gatekeeper ? Or, are you assuming that the VLF > is > > > integrated in the visiting gatekeeper ? > > > > > > This can be discussed - I was of the opionion that we should discover > the > > > VLF and send the registration to the home environment after that. > > > However, > > > we haven´t agreed on the role of the VLF, and visited gatekeeper, home > > > gatekeerp and HLF - when we come to agree on what these are, my proposal > > > may > > > change. > > > > > > <vineet:begin> Yes, this could be discussed in the conference call. My > > > suggestion is to reinvent as less as possible. Since we are adding > > > Mobility > > > to H.323, we should just fill in the gaps that are missing. > > > <vineet:end> > > > > > > > > > > > > 2. In H.323, authentication of the terminal and the gatekeeper is done > > > at > > > the time of discovery. In fact, in H.323 all messages between the > terminal > > > and the gatekeeper can be authenticated and the message integrity > > > preserved. > > > In your contribution, authentication is done at the time of > registration. > > > Why is this preferable to what is already in H.323 ? > > > > > > I would be interested to understand which gatekeeper you were > considering > > > should do the authentication. I would assume that the real > authentication > > > would have to be done at home - as such it would be necessary to find > the > > > visited network services, and then register/authenticate at home. > > > > > > <vineet:begin> I agree with your model but my preference is to preserve > > > the > > > way H.323 works today in that the authentication of both the user (not > > > terminal) and the gatekeeper (doesn't matter whether the gk is visisted > or > > > home) can be done at the time of discovery. The protocol between the > > > terminal and the gk does not change regardless of whether it is the home > > > gk > > > or the visited gk. The terminal sends its hashed password or certificate > > > in > > > the cryptotoken field of the GRQ message. The visisted gk tunnels the > > > entire > > > message to the terminal's Home Administrative Domain for authentication > > > and > > > authorization. There may be an Authentication Function in the Home > > > Administrative Domain that authenticates its users. If the user is > > > successfully authenticated by the Home Administrative Domain then a new > > > temporary password is assigned by the Home Administrative Domain to the > > > terminal and the visited gk in GCF for use during that session. This > > > exchange is explained in detail in the contribution I made for the last > > > conference call. I can't find the MD #. Does anyone know the MD # ? > > > <vineet:end> > > > > > > > > > > > > 3. What is the reason for the information flow from the HLF to the > home > > > gatekeeper, and from the home gatekeeperr to the HLF ? I don't think we > > > can > > > assume that there is only one home gatekeeper that the terminal may be > > > using. In fact, the home gatekeeper may not have any information about > the > > > user. > > > > > > I certainly don´t assume that there is only one home gatekeeper. I > assume > > > that there will be a number of home gatekeepers, but perhaps only one > (or > > > few) HLFs. In this case, we need an function to select the gatekeeper > > > that > > > the user is going to camp on - and this may depend on load, subscriber > > > profile, policy - or a lot of things. > > > > > > <vineet:begin> I guess I will have to understand the model that you have > > > in > > > mind regarding the use of a home gk on which the terminal camps on. In > my > > > model the HLF will send all pertinent information about its user to the > > > VLF. > > > The home gk is not needed. > > > <vineet:end> > > > > > > > > > > > > Regards, > > > > vineet

1 0

Re: [H.323 Mobility:] questions on MTD-016
by Roy, Radhika R, ALARC 16 Apr '00

16 Apr '00

Hi, Steve: In H.323, GKs are the communication entities thorough which registration and other services are obtained by users while VLFs and HLFs are used ad databases to store the information that are appropriate related to the mobility management. In H.323, a user is always associated with a GK through registration, and a GK manages a zone where all its H.323 registered users reside. In addition, a GK also manages resources of the zone. Please also see the mobility management information flows in AT&T contributions MD-017 and MD-018 how the GK is involved to resolve information via VLF and HLF. A mobile user MAY like to differentiate between a home GK and a foreign GK (security and many other reasons). It is an OPTION, not mandatory. Hope this clarifies your questions. Best regards, Radhika -----Original Message----- From: Stephen Terrill [mailto:stephen.terrill@ERICSSON.COM] Sent: Friday, April 14, 2000 8:02 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: [H.323 Mobility:] questions on MTD-016 Hi Roy, Can you please clarify why the gatekeeper selected for the services is a "user" issue? Regards, ..//steve "Roy, Radhika R, ALARC" wrote: > Hi, Vineet and Steve: > > I like to add couple of points with respects to your emails as follows: > > HLF: > > It is interesting to note that there appears to be an "implicit" assumption > that there is only one HLF in a domain (no matter what happens in the > future). > > Let us NOT make our protocol "hard-wired" like this. > > The protocol should be flexible enough to accommodate one or multiple HLFs > in a domain. > > If one wants to choose one HLF per domain, it MUST be left as an > implementation issue, NOT a protocol issue. > > Home GK: > > In the same token, if one wants to declare a GK as its home GK, this option > MUST be provided to a user. It is a choice that MUST be given to a user. If > anyone does NOT like this option, they MAY not use it. > > Home Network/Network Address: > > In the same token, if anyone wants to declare a network address as its home > network, this option MUST also be provided. > > GK Discovery: > > The "old" inefficient GRQ discovery mechanisms may not be the only OPTION to > discover the GK. in a highly mobile cellular environment. An alternative > mechanism, like MGA message can be listened to discover the GK as well. > > Best regards, > Radhika R. Roy > > > -----Original Message----- > > From: Kumar, Vineet [SMTP:vineet.kumar@INTEL.COM] > > Sent: Thursday, April 13, 2000 4:34 PM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: Re: [H.323 Mobility:] questions on MTD-016 > > > > Steve, > > > > Thanks for your reply. My comments are embedded in the email below. > > > > vineet > > > > -----Original Message----- > > From: Stephen Terrill [mailto:stephen.terrill@ERICSSON.COM] > > Sent: Thursday, April 13, 2000 4:42 AM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: Re: [H.323 Mobility:] questions on MTD-016 > > > > > > Hi, > > > > I shall try to answer some of these questions below. > > > > Regards, > > > > ..//steve > > > > > > > > "Kumar, Vineet" wrote: > > > > > Stephen, > > > > > > I have a couple of questions on your contribution MTD-016. These are: > > > > > > 1. H.323 already has mechanisms for discovering the gatekeeper. Are you > > suggesting in your contribution that the terminal should discover the VLF > > instead of the visiting gatekeeper ? Or, are you assuming that the VLF is > > integrated in the visiting gatekeeper ? > > > > This can be discussed - I was of the opionion that we should discover the > > VLF and send the registration to the home environment after that. > > However, > > we haven´t agreed on the role of the VLF, and visited gatekeeper, home > > gatekeerp and HLF - when we come to agree on what these are, my proposal > > may > > change. > > > > <vineet:begin> Yes, this could be discussed in the conference call. My > > suggestion is to reinvent as less as possible. Since we are adding > > Mobility > > to H.323, we should just fill in the gaps that are missing. > > <vineet:end> > > > > > > > > > 2. In H.323, authentication of the terminal and the gatekeeper is done > > at > > the time of discovery. In fact, in H.323 all messages between the terminal > > and the gatekeeper can be authenticated and the message integrity > > preserved. > > In your contribution, authentication is done at the time of registration. > > Why is this preferable to what is already in H.323 ? > > > > I would be interested to understand which gatekeeper you were considering > > should do the authentication. I would assume that the real authentication > > would have to be done at home - as such it would be necessary to find the > > visited network services, and then register/authenticate at home. > > > > <vineet:begin> I agree with your model but my preference is to preserve > > the > > way H.323 works today in that the authentication of both the user (not > > terminal) and the gatekeeper (doesn't matter whether the gk is visisted or > > home) can be done at the time of discovery. The protocol between the > > terminal and the gk does not change regardless of whether it is the home > > gk > > or the visited gk. The terminal sends its hashed password or certificate > > in > > the cryptotoken field of the GRQ message. The visisted gk tunnels the > > entire > > message to the terminal's Home Administrative Domain for authentication > > and > > authorization. There may be an Authentication Function in the Home > > Administrative Domain that authenticates its users. If the user is > > successfully authenticated by the Home Administrative Domain then a new > > temporary password is assigned by the Home Administrative Domain to the > > terminal and the visited gk in GCF for use during that session. This > > exchange is explained in detail in the contribution I made for the last > > conference call. I can't find the MD #. Does anyone know the MD # ? > > <vineet:end> > > > > > > > > > 3. What is the reason for the information flow from the HLF to the home > > gatekeeper, and from the home gatekeeperr to the HLF ? I don't think we > > can > > assume that there is only one home gatekeeper that the terminal may be > > using. In fact, the home gatekeeper may not have any information about the > > user. > > > > I certainly don´t assume that there is only one home gatekeeper. I assume > > that there will be a number of home gatekeepers, but perhaps only one (or > > few) HLFs. In this case, we need an function to select the gatekeeper > > that > > the user is going to camp on - and this may depend on load, subscriber > > profile, policy - or a lot of things. > > > > <vineet:begin> I guess I will have to understand the model that you have > > in > > mind regarding the use of a home gk on which the terminal camps on. In my > > model the HLF will send all pertinent information about its user to the > > VLF. > > The home gk is not needed. > > <vineet:end> > > > > > > > > > Regards, > > > vineet

2 1

Should we Break H.323 Model for Mobility?
by Roy, Radhika R, ALARC 16 Apr '00

16 Apr '00

Hi, Everyone: H.323 has some definite architectural notion such as terminal, GK, GW, MCU and(MC, MP). One of the fundamental corner stones is the GK. The H.323 entities (e.g., terminals, GWs) register with the GK. A GK manages a zone with the information of all registered users along with other functions (e.g., bandwidth, resource management, etc). The "registration" with the GK is the fundamental corner stone of H.323 where an association is made by each user. That is, a GK becomes the basic source to have the information related to each user. H.323 mobility protocol MUST also follow the same H.323 architectural concept. If this basic notion is not maintained, it breaks the basic foundation of H.323. It appears that H.323 mobility likes to define additional databases like VLFs and HLFs that will store the information related to the mobile users. These databases are supposed to help the function of a GK in order to manage the mobility related information. If people think that an H.323 will be able to register with a VLF directly, does it not mean we are by-passing the basic foundation of H.323 model? Does it not opening the entirely a new set of problems in H.323? It will create a parallel architecture like GK in H.323 what is not needed at all because solutions have provided that are consistent with H.323 model and there is no need to do this. We probably have to do all over again what we have done for the GKs and BEs. We inviting unnecessary problems that are yet to imagine where we may end up with. Why do we need to do that if one can do this using the consistent H.323 model of GK? In another situation, we have to go step-by-step. First intra-zone, then inter-zone, and last of all inter-domain. Contributions are there to address those problems. The mobile users that move between cells, those cells are expected primarily remain the control of a given GK (in some cases it may be two GKs). These scenarios mostly seem to be intra-zone and inter-zone and may involve a single service provider. Of course, there will also be the calls between the two adm domains of two service providers. More importantly, solutions are inter-dependent. That is, we cannot address the problems of inter-zone without knowing the intra-zone. In the same token, we cannot address the inter-domain problems without knowing the inter-zone problem. Contributions are there. Let us proceed accordingly. Last of all, I am reminding the mess that we have made in Annex G. Now people are hungry to use the more powerful and efficient Annex G messages between the GKs. Contributions were brought to do this, but the proposals had been rejected by a very few. Who is suffering? Best regards, Radhika R. Roy AT&T

2 1

Re: Should we Break H.323 Model for Mobility?
by Tom-PT Taylor 15 Apr '00

15 Apr '00

Nothing in H.323 prevents the GK from consulting other functional entities when necessary to track the location of a user. I have been following the discussion from afar, but my impression is that (1) it is proposed to distinguish a domain-specific Location Function in support of user mobility and (2) the work on mobility is partly about how the GK interacts with this function. It makes sense that the technology of mobile communications -- really just a transport issue from the point of view of H.323 -- should be treated separately from the technology of multipoint multimedia communications, which is what H.323 was designed for. Moreover, the architectural distinction is useful to avoid undue restriction of the possible business models -- the mobility service provider may well be different from the multimedia communications service provider. > -----Original Message----- > From: Roy, Radhika R, ALARC [SMTP:rrroy@ATT.COM] > Sent: Friday, April 14, 2000 10:48 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Should we Break H.323 Model for Mobility? > > Hi, Everyone: > > H.323 has some definite architectural notion such as terminal, GK, GW, MCU > and(MC, MP). One of the fundamental corner stones is the GK. The H.323 > entities (e.g., terminals, GWs) register with the GK. A GK manages a zone > with the information of all registered users along with other functions > (e.g., bandwidth, resource management, etc). > > The "registration" with the GK is the fundamental corner stone of H.323 > where an association is made by each user. That is, a GK becomes the basic > source to have the information related to each user. > > H.323 mobility protocol MUST also follow the same H.323 architectural > concept. If this basic notion is not maintained, it breaks the basic > foundation of H.323. > > It appears that H.323 mobility likes to define additional databases like > VLFs and HLFs that will store the information related to the mobile users. > These databases are supposed to help the function of a GK in order to > manage > the mobility related information. > > If people think that an H.323 will be able to register with a VLF > directly, > does it not mean we are by-passing the basic foundation of H.323 model? > Does > it not opening the entirely a new set of problems in H.323? It will create > a > parallel architecture like GK in H.323 what is not needed at all because > solutions have provided that are consistent with H.323 model and there is > no > need to do this. We probably have to do all over again what we have done > for > the GKs and BEs. We inviting unnecessary problems that are yet to imagine > where we may end up with. Why do we need to do that if one can do this > using > the consistent H.323 model of GK? > > In another situation, we have to go step-by-step. First intra-zone, then > inter-zone, and last of all inter-domain. Contributions are there to > address > those problems. > > The mobile users that move between cells, those cells are expected > primarily > remain the control of a given GK (in some cases it may be two GKs). These > scenarios mostly seem to be intra-zone and inter-zone and may involve a > single service provider. Of course, there will also be the calls between > the > two adm domains of two service providers. > > More importantly, solutions are inter-dependent. That is, we cannot > address > the problems of inter-zone without knowing the intra-zone. In the same > token, we cannot address the inter-domain problems without knowing the > inter-zone problem. Contributions are there. Let us proceed accordingly. > > Last of all, I am reminding the mess that we have made in Annex G. Now > people are hungry to use the more powerful and efficient Annex G messages > between the GKs. Contributions were brought to do this, but the proposals > had been rejected by a very few. Who is suffering? > > Best regards, > Radhika R. Roy > AT&T

1 0

H.323 Mob: Apr 17 bridge info
by Senthil Sengodan 14 Apr '00

14 Apr '00

Folks, The following is the conference call bridge details for the upcoming H.323 mobility ad-hoc group call. As has been done for the previous calls, the conference bridge is hosted/sponsored by IMTC to help expedite the H.323 mobility work. Date: Monday, April 17, 2000 Time: 8:00 AM to 10:30 AM (Pacific Standard Time (PST)) Conference call Bridge # +1 (712)-257-2485 Passcode = 1637895 - Senthil

1 0