November 1999 - sg16-avd - lists.packetizer.com

Re: H323mobility:meeting
by Roy, Radhika R, ALARC 01 Nov '99

01 Nov '99

Hi, Ed, Jaakko, and All, In H.323, zone and domain are well defined. If we can solve mobility problems within the framework of H.323 as far as practicable, we do not need to create new terminology in the context of H.323 for now. Contributions (APC-1651/1652) have also been presented also how H.323 mobility problems can be solved with the context of zones and domains. I understand that location area (LA) is also used in the cellular wireless network. If the new terminologis like location area (LA) are created for interworking between cellular-PSTN and IP networking environments, we definitely need to look into how "LA" is fitted in the context of zone or domain. However, zone and domain are the fundamental concept of H.323 that always needs to be related. Our first goal is to define a mobility architecture in the context of H.323. Our second goal is to interworking between the packet-based H.323 mobility architecture and circuit-switched based cellular-PSN/ISDN mobility architecture. In H.323, a zone may consist of many networks (e.g., many IP subnetworks). Do we need to create LAs within a zone? Will the LA be a good fit with that of cellular network for interworking at this point of time because we have not yet solved the basic problem in the context of H.323? I had some initial discussion with Jaako in the last Red Bank meeting, but we could not complete our discussion. My personal view has been that we may need something like LA to further optimize the mobility problem within a zone. For example, paging may be one of the reasons. However, I have realized that this LA concept may be more important in the context of H.323 (IP) and cellular-PSTN interworking. So, my feeling has been that we may need more functions similar to LA when interworking is concerned (Motorola's contribution APC1646 is an example). The idea has been that we should consider all those extensions in H.323 mobility architecture when we deal with interworking (second phase). Definitely, LA concept has some merits and we need to discuss it. Best regards, Radhika R. Roy AT&T + 1 732 420 1580 rrroy(a)att.com > -----Original Message----- > From: jaakko.sundquist(a)NOKIA.COM [SMTP:jaakko.sundquist@NOKIA.COM] > Sent: Monday, November 01, 1999 7:23 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H323mobility:meeting > > Hi Ed, > > I haven't read your draft yet, but I just want to make a short comment on > the definitions that you proposed. > You mention the concepts of HomeZone ID and VisitedZone ID. This implies > already to a certain architecture, namely one where the "home area" and > "visited area" of a User are defined to be identified with the accuracy of > one zone. In my contribution to the Red Bank meeting (APC 1659) I proposed > similar "home area" and "visited area" concepts based on Administrative > Domains, which in my mind makes more sense as the Domains have so far in > H.323 been the entities that are responsible for maintaining any > information > of their users. > So I propose that we think about the architecture first before defining > these terms. > > - Jaakko Sundquist > ------------------------------------------------------- > In a hole in the ground there lived a hobbit. > Not a nasty, dirty, wet hole, filled with the ends of > worms and an oozy smell, nor yet a dry, bare, > sandy hole with nothing in it to sit down on or to eat: > it was a hobbit-hole, and that means comfort. > ------------------------------------------------------- > > -----Original Message----- > From: EXT Edgar Martinez [1] > [mailto:martinze@cig.mot.com] > Sent: Monday, November 01, 1999 3:33 AM > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: H323mobility:meeting > > Dear All, > > I have put together the first proposed draft and outline > for > H.323 Annex-H. You can pick-up a copy in: > http://people.itu.int/~emartine/temp/ > > Editor's Special Note: The interworking referred in this > annex is > the interwork of legacy systems to H.323 systems. Not to > be > confused > with interworking H.323 systems to circuit switched hybrid > systems > or circuit switched adjuncts. The work proposed therewith, > does not > impact > the legacy systems or impose new requirements to the > Legacy > systems > to support H.323 terminals or H.323 systems. > > Need to add more sections to the Annex-H to comply with > TOR > e.g., > Interworking: > > Network interworking > connections between H.323 systems and mobile networks > (e.g., > GSM, ANSI > 41, ...) > connections between mobile H.323 systems and PSTN or other > networks. > > Terminal interworking > Use of non-H.323 mobile terminals (e.g., GSM handset, > H.324 > terminal, > H.320 terminal, etc.) to communicate with H.323 systems. > > Tandeming minimisation > Non-transcoding of media streams > > Also, it would be nice if we can add to the > the defiention section: > > Home Location Funtion (HFL) > Vistor Location Funtion (VFL) > Authentication user Funtion (AuF) > HomeZone ID (HZid) > VisitedZone ID (VZid) > > > > > -- > Edgar Martinez - Principal Staff Engineer > Email mailto:martinze@cig.mot.com > FAX 1-847-632-3145 - - Voice 1-847-632-5278 > 1501 West Shure Drive, Arlington Hgts. IL 60004 > Public: TIPHON & Other Stds - > http://people.itu.int/~emartine/ > Private:TIPHON & Other Stds - > http://www.cig.mot.com/~martinze/

1 0

The meaning of the reception of a "new" capability set
by frank.derks＠PHILIPS.COM 01 Nov '99

01 Nov '99

Neither H.323 nor H.245 are too clear about what it means when an endpoint receives another set of capabilities after having already received one. In previous E-mail messages on this list, I have read that capability sets are cumulative, i.e. anything "new" received in a TCS message adds to the capabilities transmitted in a previous TCS message. I have, however, found nothing in the recommendations that backs this up. So what is the intended procedure? Does a newly received set of capabilities replace the previously received set? Do capabilities received in a TCS message add to the already received capabilities? How are capabilities removed? What constitutes an "empty capability set" etc. I would appreciate it if somebody could point me in the right direction. Regards, Frank

1 0

Re: H323mobility:meeting
by jaakko.sundquist＠NOKIA.COM 01 Nov '99

01 Nov '99

Hi Ed, I haven't read your draft yet, but I just want to make a short comment on the definitions that you proposed. You mention the concepts of HomeZone ID and VisitedZone ID. This implies already to a certain architecture, namely one where the "home area" and "visited area" of a User are defined to be identified with the accuracy of one zone. In my contribution to the Red Bank meeting (APC 1659) I proposed similar "home area" and "visited area" concepts based on Administrative Domains, which in my mind makes more sense as the Domains have so far in H.323 been the entities that are responsible for maintaining any information of their users. So I propose that we think about the architecture first before defining these terms. - Jaakko Sundquist ------------------------------------------------------- In a hole in the ground there lived a hobbit. Not a nasty, dirty, wet hole, filled with the ends of worms and an oozy smell, nor yet a dry, bare, sandy hole with nothing in it to sit down on or to eat: it was a hobbit-hole, and that means comfort. ------------------------------------------------------- -----Original Message----- From: EXT Edgar Martinez [1] [mailto:martinze@cig.mot.com] Sent: Monday, November 01, 1999 3:33 AM To: ITU-SG16(a)mailbag.cps.intel.com Subject: H323mobility:meeting Dear All, I have put together the first proposed draft and outline for H.323 Annex-H. You can pick-up a copy in: http://people.itu.int/~emartine/temp/ Editor's Special Note: The interworking referred in this annex is the interwork of legacy systems to H.323 systems. Not to be confused with interworking H.323 systems to circuit switched hybrid systems or circuit switched adjuncts. The work proposed therewith, does not impact the legacy systems or impose new requirements to the Legacy systems to support H.323 terminals or H.323 systems. Need to add more sections to the Annex-H to comply with TOR e.g., Interworking: Network interworking connections between H.323 systems and mobile networks (e.g., GSM, ANSI 41, ...) connections between mobile H.323 systems and PSTN or other networks. Terminal interworking Use of non-H.323 mobile terminals (e.g., GSM handset, H.324 terminal, H.320 terminal, etc.) to communicate with H.323 systems. Tandeming minimisation Non-transcoding of media streams Also, it would be nice if we can add to the the defiention section: Home Location Funtion (HFL) Vistor Location Funtion (VFL) Authentication user Funtion (AuF) HomeZone ID (HZid) VisitedZone ID (VZid) -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

Revised(Fwd: H323mobility:meeting)
by Edgar Martinez [1] 31 Oct '99

31 Oct '99

Oh well... -------- Original Message -------- Subject: H323mobility:meeting Date: Sun, 31 Oct 1999 20:33:25 -0500 From: "Edgar Martinez [1]" <martinze(a)cig.mot.com> Organization: NSS-NAT To: Entirely SG16 <ITU-SG16(a)mailbag.cps.intel.com> CC: "TIPHON_WG7(a)LIST.ETSI.FR" <TIPHON_WG7(a)LIST.ETSI.FR> Dear All, I have put together the first proposed draft and outline for H.323 Annex-H. You can pick-up a copy in: http://people.itu.int/~emartine/temp/ Editor's Special Note: The interworking referred in this annex is the interwork of legacy systems to H.323 systems. Not to be confused with interworking H.323 systems to circuit switched hybrid systems or circuit switched adjuncts. The work proposed therewith, does not impact the legacy systems or impose new requirements to the Legacy systems to support H.323 terminals or H.323 systems. Need to add more sections to the Annex-H to comply with TOR e.g., Interworking: Network interworking connections between H.323 systems and mobile networks (e.g., GSM, ANSI 41, ...) connections between mobile H.323 systems and PSTN or other networks. Terminal interworking Use of non-H.323 mobile terminals (e.g., GSM handset, H.324 terminal, H.320 terminal, etc.) to communicate with H.323 systems. Tandeming minimisation Non-transcoding of media streams Also, it would be nice if we can add to the the defiention section: Home Location Function (HFL) Visitor Location Function (VFL) Authentication user Function (AuF) HomeZone ID (HZid) VisitedZone ID (VZid) -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0

H323mobility:meeting
by Edgar Martinez [1] 31 Oct '99

31 Oct '99

Dear All, I have put together the first proposed draft and outline for H.323 Annex-H. You can pick-up a copy in: http://people.itu.int/~emartine/temp/ Editor's Special Note: The interworking referred in this annex is the interwork of legacy systems to H.323 systems. Not to be confused with interworking H.323 systems to circuit switched hybrid systems or circuit switched adjuncts. The work proposed therewith, does not impact the legacy systems or impose new requirements to the Legacy systems to support H.323 terminals or H.323 systems. Need to add more sections to the Annex-H to comply with TOR e.g., Interworking: Network interworking connections between H.323 systems and mobile networks (e.g., GSM, ANSI 41, ...) connections between mobile H.323 systems and PSTN or other networks. Terminal interworking Use of non-H.323 mobile terminals (e.g., GSM handset, H.324 terminal, H.320 terminal, etc.) to communicate with H.323 systems. Tandeming minimisation Non-transcoding of media streams Also, it would be nice if we can add to the the defiention section: Home Location Funtion (HFL) Vistor Location Funtion (VFL) Authentication user Funtion (AuF) HomeZone ID (HZid) VisitedZone ID (VZid) -- Edgar Martinez - Principal Staff Engineer Email mailto:martinze@cig.mot.com FAX 1-847-632-3145 - - Voice 1-847-632-5278 1501 West Shure Drive, Arlington Hgts. IL 60004 Public: TIPHON & Other Stds - http://people.itu.int/~emartine/ Private:TIPHON & Other Stds - http://www.cig.mot.com/~martinze/

1 0