- sg16-avd - lists.packetizer.com

Re: H323 mobility: Summary of discussion
by Roy, Radhika R, ALARC 12 Nov '99

12 Nov '99

Hi, Gösta and All: Everyone is welcomed to join discussion and bring contributions to make their point of view clearer. Anyone can bring contributions anytime no matter what the state of the document submitted by the editor is unless the standard is decided. Discussion are progressed based on contributions. Only contributions provide a basis for discussion. In the last Red Bank meeting, we had an wonderful opportunity to understand each other's points based on contributions. We have made good progress compared to that of the Berlin meeting. Definitely we need the help from the people like you and all others to have a common understanding. We expect to hear more from you in the upcoming conference call. Our final goal is to find a solution!!! Best regards, Radhika R. Roy > -----Original Message----- > From: Gösta Linder (LME) [SMTP:Gosta.Linder@LME.ERICSSON.SE] > Sent: Friday, November 12, 1999 3:36 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H323 mobility: Summary of discussion > > The discussion carried in this mails strengthen the need for some agreed > scope and model for what we mean with Mobility Management to support Multi > Media/H323 communication. This type of process to proceed was agreed in > Red Bank and that is what I hope all will agree upon as a basis for Nov 17 > teleconf meeting. TD 16 was our first attemt to come to a tighter > definition before we go into discussion of solutions. Discussion of > solutions would not be fruitful as long as we do not have a common > understanding of the problem /service to be resolved and within which > network environment the service should be introduced. > /Gösta Linder > > -----Original Message----- > From: Adam Li [mailto:adamli@ICSL.UCLA.EDU] > Sent: den 10 november 1999 10:41 > To: ITU-SG16(a)mailbag.cps.intel.com > Subject: Re: H323 mobility: Summary of discussion > > > Hi, all, > > Barry Aronson's comment seems to make a lot of sense to me. > > I am new to the H.323 group, but I've been reading the email > correspondences here for quite a while. May I ask a few dumb > questions, and please correct me and elighten me if I am wrong? > > Question: Consider the wireless case, isn't that H.323M is > going to be used over some wireless network (e.g. 3G IMT2000 > network)? If such network is already built to ensure that your > data gets transmitted to you no matter you walk or drive from > one zone to the other, why can't our H.323M terminal just > sit at the handset and wait for our data get routed to us > by the network? Or, why do we need to duplicate these > functions that are already provided, and should be provided > by the network layer? > > Maybe, all we have to do is to make sure we know the data is from > the same entity when it changes its attaching point, since each > H.323 entity is identified by the LAN address (H.323 7.1.1). > A simple extension of assigning a temporary ID number to each > entity or to each conference can solve that. > > Please enlighten if there is any special compelling reason that > I might have overlooked for duplicating an entire mobile network > functionality within H.323. Thanks in advance. > > Adam Li > > > Edgar Martinez [1] writes: > > > > Comments: follow-- > > > > Barry Aronson wrote: > > > > > All, > > > > > > I agree with Tom. We seem to be headed for designing an entire mobile > > > network within H.323 -- definitely a case of the tail wagging the dog. > If > > > this was the desire, extending existing mobile networks (AMPS, GSM, > etc.) to > > > include H.323 terminals would be simpler. > > > > This is called the WAP solution, already done but it is still > > two separate networks (MSC-CS and PDN) routed/ split out > > by a DSU from the BSC. And it does not address the fixed > > Internet PC or any PSTN/ISDN interworking. > > > > > That is, of course, unless you > > > wanted the terminals to be independent of the physical network from > the > > > network layer on up. H.323 could do this if there was an underlying > packet > > > based network -- probably IP. Using IP as a common network layer for > both > > > wireless and wired terminals is of course all the rage these days. > Given > > > that universal wireless terminals are been worked as part of IMT-2000 > (and > > > 3GPP, 3GPP-2, etc.), wouldn't it make sense to define the Annex H > issues > > > being debated in the appropriate network groups? > > > > We are looking at the H.323 mobility at the appilation layer within > > the approriate woking groups. > > > > > > > > > > > > > Maybe I misunderstood, but I thought in Santiago the purpose of Annex > H and > > > I was to make H.323 work within the context of a mobile terminal > and/or > > > user, and also allow for service mobility. > > > > I feel a mobile IP debate is in the starts here but, We are looking at > > the H.323 mobility at the appilation layer within the approriate woking > > group. > > > > What the IETF needs to address is how mobile IP interworks with Mobility > > whether is H.323, GSM, PLNM or otherwise.. > > > > > I don't think any of what is > > > being discussed for Annex H is necessary to achieve this. > > > > What being discussed here is, we are looking at > > the H.323 mobility from the appilation layer. > > > > > > > > > > > Barry > > > > > > -----Original Message----- > > > From: Mailing list for parties associated with ITU-T Study Group 16 > > > [mailto:ITU-SG16@MAILBAG.INTEL.COM]On Behalf Of Tom-PT Taylor > > > Sent: Friday, November 05, 1999 11:17 AM > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > Subject: Re: H323 mobility: Summary of discussion > > > > > > I think a basic point in this discussion is that mobility is "bigger > than" > > > H.323 and already has well-established architectural underpinnings. > It's > > > all very well to talk about an H.323 solution which we could then > adapt, but > > > we would more likely end up with an H.323-only solution as a result. > The > > > concern then would be whether vendors saw sufficient opportunity in > building > > > to this market, compared with the general market for mobility > products. > > > > -- > > 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/ > > > > > -- > Adam H. Li > Image Process Lab > University of California - Los Angeles > (Phone) 310-825-5178 (Fax) 310-825-7928

1 0

Re: H323 mobility: Summary of discussion
by Gösta Linder (LME) 12 Nov '99

12 Nov '99

The discussion carried in this mails strengthen the need for some agreed scope and model for what we mean with Mobility Management to support Multi Media/H323 communication. This type of process to proceed was agreed in Red Bank and that is what I hope all will agree upon as a basis for Nov 17 teleconf meeting. TD 16 was our first attemt to come to a tighter definition before we go into discussion of solutions. Discussion of solutions would not be fruitful as long as we do not have a common understanding of the problem /service to be resolved and within which network environment the service should be introduced. /Gösta Linder -----Original Message----- From: Adam Li [mailto:adamli@ICSL.UCLA.EDU] Sent: den 10 november 1999 10:41 To: ITU-SG16(a)mailbag.cps.intel.com Subject: Re: H323 mobility: Summary of discussion Hi, all, Barry Aronson's comment seems to make a lot of sense to me. I am new to the H.323 group, but I've been reading the email correspondences here for quite a while. May I ask a few dumb questions, and please correct me and elighten me if I am wrong? Question: Consider the wireless case, isn't that H.323M is going to be used over some wireless network (e.g. 3G IMT2000 network)? If such network is already built to ensure that your data gets transmitted to you no matter you walk or drive from one zone to the other, why can't our H.323M terminal just sit at the handset and wait for our data get routed to us by the network? Or, why do we need to duplicate these functions that are already provided, and should be provided by the network layer? Maybe, all we have to do is to make sure we know the data is from the same entity when it changes its attaching point, since each H.323 entity is identified by the LAN address (H.323 7.1.1). A simple extension of assigning a temporary ID number to each entity or to each conference can solve that. Please enlighten if there is any special compelling reason that I might have overlooked for duplicating an entire mobile network functionality within H.323. Thanks in advance. Adam Li Edgar Martinez [1] writes: > > Comments: follow-- > > Barry Aronson wrote: > > > All, > > > > I agree with Tom. We seem to be headed for designing an entire mobile > > network within H.323 -- definitely a case of the tail wagging the dog. If > > this was the desire, extending existing mobile networks (AMPS, GSM, etc.) to > > include H.323 terminals would be simpler. > > This is called the WAP solution, already done but it is still > two separate networks (MSC-CS and PDN) routed/ split out > by a DSU from the BSC. And it does not address the fixed > Internet PC or any PSTN/ISDN interworking. > > > That is, of course, unless you > > wanted the terminals to be independent of the physical network from the > > network layer on up. H.323 could do this if there was an underlying packet > > based network -- probably IP. Using IP as a common network layer for both > > wireless and wired terminals is of course all the rage these days. Given > > that universal wireless terminals are been worked as part of IMT-2000 (and > > 3GPP, 3GPP-2, etc.), wouldn't it make sense to define the Annex H issues > > being debated in the appropriate network groups? > > We are looking at the H.323 mobility at the appilation layer within > the approriate woking groups. > > > > > > > > Maybe I misunderstood, but I thought in Santiago the purpose of Annex H and > > I was to make H.323 work within the context of a mobile terminal and/or > > user, and also allow for service mobility. > > I feel a mobile IP debate is in the starts here but, We are looking at > the H.323 mobility at the appilation layer within the approriate woking > group. > > What the IETF needs to address is how mobile IP interworks with Mobility > whether is H.323, GSM, PLNM or otherwise.. > > > I don't think any of what is > > being discussed for Annex H is necessary to achieve this. > > What being discussed here is, we are looking at > the H.323 mobility from the appilation layer. > > > > > > > Barry > > > > -----Original Message----- > > From: Mailing list for parties associated with ITU-T Study Group 16 > > [mailto:ITU-SG16@MAILBAG.INTEL.COM]On Behalf Of Tom-PT Taylor > > Sent: Friday, November 05, 1999 11:17 AM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: Re: H323 mobility: Summary of discussion > > > > I think a basic point in this discussion is that mobility is "bigger than" > > H.323 and already has well-established architectural underpinnings. It's > > all very well to talk about an H.323 solution which we could then adapt, but > > we would more likely end up with an H.323-only solution as a result. The > > concern then would be whether vendors saw sufficient opportunity in building > > to this market, compared with the general market for mobility products. > > -- > 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/ > -- Adam H. Li Image Process Lab University of California - Los Angeles (Phone) 310-825-5178 (Fax) 310-825-7928

1 0

H.323 mobility:MTD number request
by Jaakko Sundquist 12 Nov '99

12 Nov '99

Hi Paul, Could you reserve an MTD number for Nokia. The title of the document will be something along the lines: H.323 Functional Architecture and Reference Points. - 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. -------------------------------------------------------

1 0

Re: H.323 mobility:Reserve TDs
by Reddy, Paul K 11 Nov '99

11 Nov '99

Hi Radhika, Yes, I am assigning the MTD-xx numbers for the all the contributions submitted to be discussed during our conference call. -Paul Paul K. Reddy Intel Architecture Labs, Intel Corporation, 2111 NE 25th Avenue, Hillsboro, OR - 97124, USA, Office Phone# +1 (503)-264-9896 -----Original Message----- From: Roy, Radhika R, ALARC [mailto:rrroy@ATT.COM] Sent: Thursday, November 11, 1999 5:57 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: H.323 mobility:Reserve TDs Hi, Ed and Paul: Did we not agree that we will provide "MTD.xxx" instead of "TD.xxx" to differentiate from the regular "TD.xxx"? Thanks, Radhika > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: Wednesday, November 10, 1999 10:37 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.323 mobility:Reserve TDs > > Paul, > > I will like to reserve the following TDs. TD 03, 04 and 05. > For the h.332 mobility Ad-hoc meeting. > > TD-03 will be H.323 Annex-H Darft and outline. > > TD-04 will be the Level 1 headings for H.323 Annex-H > interworking with legcay mobile networks and mobile > terminals (from the IP network perspective). > > TD-05 (Informational only) Full migration from GPRS > to a Multimedia IP network (from the H.323 IP network > perspective). > > Thank you, > -- > 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

Re: H.323 mobility:Reserve TDs
by Reddy, Paul K 11 Nov '99

11 Nov '99

Dear Edgar, I have assigned the Mobile Temporary Document numbers as you requested to 3 documents, which are submitted towards conference call discussion on November 17, 1999. MTD-03: Title: H.323 Annex-H Draft and outline Company: Motorola MTD-04: Title: The Level 1 headings for H.323 Annex-H interworking with legacy mobile networks and mobile terminals (from the IP network perspective). Company: Motorola MTD-05: Title: Informational only) Full migration from GPRS to a Multimedia IP network (from the H.323 IP network perspective). Company: Motorola Also, the MTD-03, MTD-04, MTD-05 documents have been copied into the following directory: http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ Please reply, to this email, if you have any questions. thanks, Paul Paul K. Reddy Intel Architecture Labs, Intel Corporation, 2111 NE 25th Avenue, Hillsboro, OR - 97124, USA, Office Phone# +1 (503)-264-9896 -----Original Message----- From: Edgar Martinez [1] [mailto:martinze@CIG.MOT.COM] Sent: Wednesday, November 10, 1999 7:37 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: H.323 mobility:Reserve TDs Paul, I will like to reserve the following TDs. TD 03, 04 and 05. For the h.332 mobility Ad-hoc meeting. TD-03 will be H.323 Annex-H Darft and outline. TD-04 will be the Level 1 headings for H.323 Annex-H interworking with legcay mobile networks and mobile terminals (from the IP network perspective). TD-05 (Informational only) Full migration from GPRS to a Multimedia IP network (from the H.323 IP network perspective). Thank you, -- 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

H.323 Mobilty: Downloaded MTD 03-05
by Edgar Martinez [1] 11 Nov '99

11 Nov '99

Dear Mobility Team, Not to overload SG16 mailer with comments as contributions start to come in. I will like to suggest that we restrain from any comments to the MTD's until we have the conference call and are given opportunely to explain the MTD. Contributions MTD-03, 04, 05 have been loaded to ftp://standard.pictel.com/avc-site/Incoming MTD-03 will be H.323 Annex-H Darft and outline. > > > > MTD-04 will be the Level 1 headings for H.323 Annex-H interworking with legcay mobile networks and mobile terminals (from the IP network perspective). > > > > MTD-05 (Informational only) Full migration from GPRS to a Multimedia IP network (from the H.323 IP network perspective). Best Regards, -- 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

Re: H.323 mobility: Reserve TDs
by Edgar Martinez [1] 11 Nov '99

11 Nov '99

Great, We do not to have maintain a separate directory for mobility. I will then download my MTD's to the regular Incoming. ftp://standard.pictel.com/avc-site/Incoming Thanks, Ed "Roy, Radhika R, ALARC" wrote: > Hi, Ed: > > We did not hear any objection after your suggestion. Now we are assuming > that it is OK to use MTD.xxx for our mobility work. > > Best regards, > Radhika > > > -----Original Message----- > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > Sent: Thursday, November 11, 1999 8:54 AM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: Re: H.323 mobility:Reserve TDs > > > > Hi Radhika, > > > > I suggested it, if it is OK by everyone I prefer > > MTD.xxx it will also help to keep track of the > > Mobility TD's without having to open the other > > regular TD's to look for the subject. > > > > Regards, > > Ed > > > > "Roy, Radhika R, ALARC" wrote: > > > > > Hi, Ed and Paul: > > > > > > Did we not agree that we will provide "MTD.xxx" instead of "TD.xxx" to > > > differentiate from the regular "TD.xxx"? > > > > > > Thanks, > > > Radhika > > > > > > > -----Original Message----- > > > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > > > Sent: Wednesday, November 10, 1999 10:37 PM > > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > > Subject: H.323 mobility:Reserve TDs > > > > > > > > Paul, > > > > > > > > I will like to reserve the following TDs. TD 03, 04 and 05. > > > > For the h.332 mobility Ad-hoc meeting. > > > > > > > > TD-03 will be H.323 Annex-H Darft and outline. > > > > > > > > TD-04 will be the Level 1 headings for H.323 Annex-H > > > > interworking with legcay mobile networks and mobile > > > > terminals (from the IP network perspective). > > > > > > > > TD-05 (Informational only) Full migration from GPRS > > > > to a Multimedia IP network (from the H.323 IP network > > > > perspective). > > > > > > > > Thank you, > > > > -- > > > > 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/ > > > > -- > > 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/ -- 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

Re: H.323 mobility: Reserve TDs
by Roy, Radhika R, ALARC 11 Nov '99

11 Nov '99

Hi, Ed: We did not hear any objection after your suggestion. Now we are assuming that it is OK to use MTD.xxx for our mobility work. Best regards, Radhika > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: Thursday, November 11, 1999 8:54 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H.323 mobility:Reserve TDs > > Hi Radhika, > > I suggested it, if it is OK by everyone I prefer > MTD.xxx it will also help to keep track of the > Mobility TD's without having to open the other > regular TD's to look for the subject. > > Regards, > Ed > > "Roy, Radhika R, ALARC" wrote: > > > Hi, Ed and Paul: > > > > Did we not agree that we will provide "MTD.xxx" instead of "TD.xxx" to > > differentiate from the regular "TD.xxx"? > > > > Thanks, > > Radhika > > > > > -----Original Message----- > > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > > Sent: Wednesday, November 10, 1999 10:37 PM > > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > > Subject: H.323 mobility:Reserve TDs > > > > > > Paul, > > > > > > I will like to reserve the following TDs. TD 03, 04 and 05. > > > For the h.332 mobility Ad-hoc meeting. > > > > > > TD-03 will be H.323 Annex-H Darft and outline. > > > > > > TD-04 will be the Level 1 headings for H.323 Annex-H > > > interworking with legcay mobile networks and mobile > > > terminals (from the IP network perspective). > > > > > > TD-05 (Informational only) Full migration from GPRS > > > to a Multimedia IP network (from the H.323 IP network > > > perspective). > > > > > > Thank you, > > > -- > > > 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/ > > -- > 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

Re: H.323 mobility:Reserve TDs
by Roy, Radhika R, ALARC 11 Nov '99

11 Nov '99

Hi, Ed and Paul: Did we not agree that we will provide "MTD.xxx" instead of "TD.xxx" to differentiate from the regular "TD.xxx"? Thanks, Radhika > -----Original Message----- > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > Sent: Wednesday, November 10, 1999 10:37 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.323 mobility:Reserve TDs > > Paul, > > I will like to reserve the following TDs. TD 03, 04 and 05. > For the h.332 mobility Ad-hoc meeting. > > TD-03 will be H.323 Annex-H Darft and outline. > > TD-04 will be the Level 1 headings for H.323 Annex-H > interworking with legcay mobile networks and mobile > terminals (from the IP network perspective). > > TD-05 (Informational only) Full migration from GPRS > to a Multimedia IP network (from the H.323 IP network > perspective). > > Thank you, > -- > 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

Re: H.323 mobility:Reserve TDs
by Edgar Martinez [1] 11 Nov '99

11 Nov '99

Hi Radhika, I suggested it, if it is OK by everyone I prefer MTD.xxx it will also help to keep track of the Mobility TD's without having to open the other regular TD's to look for the subject. Regards, Ed "Roy, Radhika R, ALARC" wrote: > Hi, Ed and Paul: > > Did we not agree that we will provide "MTD.xxx" instead of "TD.xxx" to > differentiate from the regular "TD.xxx"? > > Thanks, > Radhika > > > -----Original Message----- > > From: Edgar Martinez [1] [SMTP:martinze@CIG.MOT.COM] > > Sent: Wednesday, November 10, 1999 10:37 PM > > To: ITU-SG16(a)MAILBAG.INTEL.COM > > Subject: H.323 mobility:Reserve TDs > > > > Paul, > > > > I will like to reserve the following TDs. TD 03, 04 and 05. > > For the h.332 mobility Ad-hoc meeting. > > > > TD-03 will be H.323 Annex-H Darft and outline. > > > > TD-04 will be the Level 1 headings for H.323 Annex-H > > interworking with legcay mobile networks and mobile > > terminals (from the IP network perspective). > > > > TD-05 (Informational only) Full migration from GPRS > > to a Multimedia IP network (from the H.323 IP network > > perspective). > > > > Thank you, > > -- > > 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/ -- 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