Annex G and Roaming?

Wan-jiun Liao wjliao at CC.EE.NTU.EDU.TW
Fri Apr 23 22:22:51 EDT 1999


Hi, 

    I would like to share with all you experts my views on the provisions
of mobility for H.323. Attached please find a paper entitled "Mobile
Internet Telephony: mobile extensions to H.323", which has been
presented and published at IEEE Infocom '99. Any commnets/suggestions are
solicited and welcome.

    The major point I would like to say in the paper is that H.323 
has provided an excellent environment for the mobility support, even
without the support of mobile IP. I just demonstrated how to reuse the
possible existing signaling to realize registration, call tracking, and
roaming for mobile IP phone services.

Best regards, 
 
Wanjiun Liao

Assit. Prof.
Dept. of Electrical Engineering
National Taiwan University
Taipei, Taiwan

On Fri, 23 Apr 1999, Edgar Martinez [1] wrote:

> I fully support the interworking between the
> legacy mobile network VLR/HLR applications and
> H.323 GK access via the SG to provide seamless
> roaming between PLMN and IP networks. This
> work will need to be addressed in Tiphon's WG7.
> 
> Regards,
> 
> Ed
> 
> "Roy, Radhika R, ALCOO" wrote:
> >
> > Hi Everyone:
> >
> > Yes, I guess that the roaming has not been addressed in the present H.225.0
> > AnnexG. To address roaming in a standard way, it will require to change the
> > scope of Annex G.
> >
> > Annex G addresses the inter-domain communications.
> >
> > We have not yet standardized the basic roaming schemes even for the simple
> > intra-domain communications.
> >
> > Last year, we discussed this problem, and some suggestions were made to
> > solve this using the home and visiting GK. The discussion did not go too far
> > to create a standard.
> >
> > It is an important topic, and let us create a standard in H.323 to support
> > roaming.
> >
> > Let us understand that, in H.323, we are talking in the application layer,
> > and not the networking layer. That is, roaming schemes have to be supported
> > in the H.323 application layer that can take advantage of the mobility
> > solutions provided in the network layer (e.g., mobile IP).
> >
> > Thanks,
> > Radhika R. Roy
> > AT&T
> >
> > > -----Original Message-----
> > > From: Espen Skjæran [SMTP:Espen.Skjaeran at ERICSSON.COM]
> > > Sent: Friday, April 23, 1999 8:55 AM
> > > To:   ITU-SG16 at MAILBAG.INTEL.COM
> > > Subject:      Annex G and Roaming?
> > >
> > > Hi all,
> > >
> > > I've recently heard (unofficially)  that some claim Annex G
> > > (APC-1546/TD-20 in Monterey)
> > > also to support roaming of users between different domains.
> > >
> > > If this is true, I wonder how.
> > >
> > > I can see how the AccessRequest/ValidationRequest might be sent from a
> > > visiting domain to the home domain for per-call authorization. While
> > > this might work in simple cases, it will hinder the use of services
> > > while roaming.
> > > I can not either see any mechanism to authorize the roaming
> > > registration.
> > >
> > > I am sorry to post based on "rumors", but this may change the scope of
> > > Annex G significally, and I worry if this might affect future work on
> > > roaming. As Tiphon has just started their work on roaming by analysing
> > > existing roaming techniques in telco and datacom/IETF work,and not yet
> > > reached any conclusion, it seems premature to use annex G
> > > in its current state for roaming.
> > >
> > > Espen
> 
> --
> Edgar Martinez - Principal Staff Engineer
> Email mailto:martinze at cig.mot.com
> FAX 1-847-632-3145 - - Voice 1-847-632-5278
> 1501 West Shure Drive, Arlington Hgts. IL 60004
> TIPHON & Other Stds -- http://www.cig.mot.com/~martinze/
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 250_345991494.ps.gz
Type: application/octet-stream
Size: 565058 bytes
Desc: 
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/19990424/24c95c40/attachment-0004.obj>


More information about the sg16-avd mailing list