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

Re: H.323 mobility: dowlaoded MTD-10
by Edgar Martinez [1] 16 Nov '99

16 Nov '99

Dear Paul, Thank you I have downloaded MTD-10a for the conference meeting. Regards, Ed "Reddy, Paul K" wrote: > Dear Edgar, > > I have assigned the following MTD number upon your request: > > MTD-10: > Title: IMT-2000 Global Roaming and Interworking Scenarios > (Reference only) > Company: Motorola > > regards, > > Paul > > Paul K. Reddy > Intel Corporation > USA > -----Original Message----- > From: Edgar Martinez [1] [mailto:martinze@cig.mot.com] > Sent: Monday, November 15, 1999 11:04 PM > To: Reddy, Paul K; Entirely SG16 > Subject: H.323 mobility: Reserve one MTD and revised two > Importance: High > > Dear Paul, > > I would like a new MTD number for the following contribution: > > Title: IMT-2000 Global Roaming and Interworking Scenarios > (Reference only) > --- > > And will also like to inform you that I have downloaded > two revised documents: > > 1. Was MTD-O4 now is MTD-04a > 2. Was MTD-05 now is MTD-05a > > I will only present only the latest versions in the > meeting. > > Thank you, > Ed > > "Edgar Martinez [1]" wrote: > > > Paul, > > > > I will like to reserve the following MTDs. MTD 03, 04 and 05. > > For the h.332 mobility Ad-hoc meeting. > > > > 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). > > > > 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

H.323 mobility Conference Call
by Roy, Radhika R, ALARC 16 Nov '99

16 Nov '99

Hi, Everyone: Let me clarify few things on behalf of the H.323 Ad Hoc Mobility Group as follows: 1. Temporary document numbers will be provided by Paul K. Reddy Intel Architecture Labs, Intel Corporation, 2111 NE 25th Avenue, Hillsboro, OR - 97124, USA, Office Phone# +1 (503)-264-9896 paul.k.reddy(a)INTEL.COM http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ Please contact Paul for allocation and uploading of the documents in the web site. 2. Editors for H.323 Annexes are as follows: * H.323 Annex H: User, Terminal, and Service Mobility in H.323 - Editor: E. Martinez, Motorola * H.323 Annex I: Packet-based Multimedia Telephony over Error Prone Channels - Editor: B. Aronson, Toshiba 3. Tomorrow's (November 17, 1999) conference call is being hosted by Intel. I would request both Paul and Ed keep the meeting minutes. The meeting minutes will be distributed later. 4. The next conference call will be hosted by AT&T (time and date will be decided tomorrow). However, I would request Paul to allocate the document numbers as he is doing now. 5. I am enclosing a file containing all APC/TD numbers and titles of the SG16 Q.12-Q.14 Red Bank meeting and the upcoming conference call. If you have any questions, please let me know. Best regards, Radhika R. Roy On Behalf of H.323 Ad Hoc Mobility Group AT&T + 1 732 420 1580 rrroy(a)att.com <<Title.doc>>

1 0

Re: H.323 mobility: Reserve one MTD and revised two
by Reddy, Paul K 16 Nov '99

16 Nov '99

Dear Edgar, I have assigned the following MTD number upon your request: MTD-10: Title: IMT-2000 Global Roaming and Interworking Scenarios (Reference only) Company: Motorola regards, Paul Paul K. Reddy Intel Corporation USA -----Original Message----- From: Edgar Martinez [1] [mailto:martinze@cig.mot.com] Sent: Monday, November 15, 1999 11:04 PM To: Reddy, Paul K; Entirely SG16 Subject: H.323 mobility: Reserve one MTD and revised two Importance: High Dear Paul, I would like a new MTD number for the following contribution: Title: IMT-2000 Global Roaming and Interworking Scenarios (Reference only) --- And will also like to inform you that I have downloaded two revised documents: 1. Was MTD-O4 now is MTD-04a 2. Was MTD-05 now is MTD-05a I will only present only the latest versions in the meeting. Thank you, Ed "Edgar Martinez [1]" wrote: > Paul, > > I will like to reserve the following MTDs. MTD 03, 04 and 05. > For the h.332 mobility Ad-hoc meeting. > > 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). > > 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

Alcatel contribution for mobility ad-hoc group meeting
by Laurent Thiebaut 16 Nov '99

16 Nov '99

Please find attached the 2 following contributions from Alcatel for tomorrow's audio meeting. - (Contribution MTD-08) Integrating 3GPP's architecture into the H.323 wireless IP mobility system - (Draft Contribution MTDalc) Clear Split of functions between Call Control and (radio) Access networks A contribution number is currently requested for the second contribution. I apologize for sending them out on the exploder and not having (yet) copied them on the ftp server, but I am at home and can only access to my e_mail --> I send these contributions by mail to let you as much time as possible to read them beforehand. Best regards Laurent T. --------------------------------------------------------------------------- V Laurent Thiebaut tel: +33 (0)1 3077 0645 A L C A T E L e.mail:laurent.thiebaut@alcatel.fr ---------------------------------------------------------------------------

1 0

Re: H.323 Mobility: Quick comments on MTDs
by Edgar Martinez [1] 16 Nov '99

16 Nov '99

Please see comments: Jaakko Sundquist wrote: > Hi all, > > I have a couple of comments on some of the MTDs that I would like to make > already before the telephone conference. > > First a small typo in MTD-02. In item 4, it should probably say H.246 Annex > E instead of H.248 Annex E. > > Second, MTD-04. I would like to start this conversation already on the > mailing list to save some time. I do not think that we should have separate > chapters in the H.323 Annex H for the interworking issues. Instead, I think > that these things must be taken into consideration in all the other chapters > defining the H.323 Mobility. I agreed with you, one reason for chapters 8-11 is to Summarize all the interworking requirements identified in the earlier chapters. And reference other H.246 Annex's for more details. And maybe provide a matrix of the level of interworking supported for each network type, e.g., GSM etc. > Also, the more detailed definitions concerning > the PLMN-interworking should be handled in the H.246 Annex E. On PLNM interworking does it include PSTN, INAP, CAMEL, MAP, Supplementery sevices and regulated Service like LNP?? and Which Terminal types which 2G or 3G terminals are supported ... I saw H.323 Annex-H has the Main document to put high level requirements for interworking networks and terminals that maybe captured in details by other Documents like H.246 Annex-(E...Z). > > Furthermore, I'm not quite sure what is meant by the chapter 7 title: > Recommended Reliable Transport Protocol for the IP Mobile subsystems. I > think this chapter (or it could be divided into a couple of chapters) should > include the procedure definitions (with message sequences, etc.) as well as > the message and message field definitions (such as ASN.1). Chapter 7, can be very simple or not, we can just reference protocols e.g., CSTP and Sigtran and for IP Transport part used between the IP mobility subsytems e.g., between HLF and GK for reliable transport of signaling and QoS. > > Another one that I don't quite understand is chapter 11: Mobile IP Network > Interworking. What is this chapter actually meant to include? I believe that this chapter 11 can include requirements for H.323 Annex-I to consider the interworking between the H.323 Network Mobility Management and the Mobile IP transport application. Chapter 11 can provide some high level requirements to H.323 Annex-I. To consider a way or ways for the H.323 Network Mobility Management application to request a change of an IP address to the Mobile IP Transport Appilcation, in the event of handover and/or roaming that may change the Terminal IP address and/or Network Point of Attachment (NoPA). Within a active call or active state. In summary, I see H.323 Annex-H as the core mobility requirements the interworking sections are no more then, high level requirements that we need to make sure works with the Core, that is, the PURE H.323 IP mobility network and the H.323 standard Framework. For example Location Area could a interworking requirement. Lets say add a chapter 12 called "Location Area interworking with H.323 Mobility". The context it is chapter 12 could start like this. For Location Area to work within the H.323 mobility framework. One needs to address the following ..................Or changes to the LA ID format where needed to account for IP addressing etc........ --end-- Good questions and like everything else, we all need to agreed on what should be included in the H.323 Annex-H document and we all have a equal vote. The document will reflect our collective decision. Regards, Ed > > > - 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. > ------------------------------------------------------- -- 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: VoIP Test Equipment
by Kausar, Nadia 16 Nov '99

16 Nov '99

hi testtools specialises in H.323 and SIP analyser (http://www.testtools.co.uk/ and then follow the link for VT320 , also check this web site too http://www.networkcomputing.com/1023/1023sp2.html cheers Nadia +++++++++++++++++++++++++ Nadia Kausar IP Engineer Level 3 Communication 66 Prescott Street London E1 8HG tel: +44 (0)171 864 0949 mobile: (0) 7880 506 195 -----Original Message----- From: Jean Ko [mailto:hjko@metro.telecom.samsung.co.kr] Sent: 13 November 1999 04:36 To: Mailing List, h323implementors; Mailing list for parties associated with ITU-T Study Group 16 Subject: VoIP Test Equipment Hi All, I need to find VoIP test equipments for protocol, performance, electrical charicteristics testing. Anyone know where I can buy VoIP test equipments? Best Regards, Jean Ko ------------------------------------------------------------------------- for list subscription instructions, send email to h323implementors-request(a)imtc.org with text "info"

1 0

H.323 Mobility: Quick comments on MTDs
by Jaakko Sundquist 16 Nov '99

16 Nov '99

Hi all, I have a couple of comments on some of the MTDs that I would like to make already before the telephone conference. First a small typo in MTD-02. In item 4, it should probably say H.246 Annex E instead of H.248 Annex E. Second, MTD-04. I would like to start this conversation already on the mailing list to save some time. I do not think that we should have separate chapters in the H.323 Annex H for the interworking issues. Instead, I think that these things must be taken into consideration in all the other chapters defining the H.323 Mobility. Also, the more detailed definitions concerning the PLMN-interworking should be handled in the H.246 Annex E. Furthermore, I'm not quite sure what is meant by the chapter 7 title: Recommended Reliable Transport Protocol for the IP Mobile subsystems. I think this chapter (or it could be divided into a couple of chapters) should include the procedure definitions (with message sequences, etc.) as well as the message and message field definitions (such as ASN.1). Another one that I don't quite understand is chapter 11: Mobile IP Network Interworking. What is this chapter actually meant to include? - 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

H.323 Mobility: MTD-06 uploaded
by Jaakko Sundquist 16 Nov '99

16 Nov '99

Hi all, I have uploaded MTD-06 to the URL: ftp://standard.pictel.com/avc-site/Incoming/H323_Mobility/MTD-06.zip . The title of the document is: H.323 Annex H 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: Alcatel Reaction on H.323m contributions
by Laurent Thiebaut 16 Nov '99

16 Nov '99

Mister Martinez, I apologize for having let the impression of using your name as well as your work as well as the "Mobility AD-HOC group" source for my comment on your contribution. This was not in my mind a contribution but just a clarification on 3GPP view about multimedia mobility. I understand you felt that my mail was incorrect (not respecting your work nor the rules of working within your group). This was not at all my intention and I ask you to forgive me. To the group, I apologize for having brought some mess in your discussions. My intent was just to ask for a clarification in contribution MTD-05. The first figure of contribution MTD-05 is exactly option 1 of 3GPP 23.922. My question is on the two following figures: are they aiming at representing 3GPP's view or Motorola's view or the current view of your group? My intrusion into your debate was just to try to clarify that the 2 last figures do not exactly represent 3GPP view. If I have inserted description of MSC and GMSC servers, it is because an option 2 is refered to in MTD-05 and I (may be wrongly) understood that it was 3GPP architectural option 2 that was refered to in the second figure of MTD-05 (3GPP architecture option 2 aims at allowing the "All IP" network to interface Circuit Switched terminals and uses MSC and GMSC servers for that purpose). To come to the only intersting question that is the question on the ground, my comment is that we should try to separate the access layer (GPRS, CDMA, ...) from the call control layer (H323, GK, ...) to allow each evolving on its own pace and to have clear separation between the standardization bodies that work on radio access and on multimedia architecture. I have sent e_mail comment because I have been only aware very recently that you have this week an audio-conference and I thought it was too late to send written contributions. If it is not too late, I would need - 2 contribution numbers (One MTD-08 has already been given to me by Mr. Reddy, which I thankvery much for his explanations, but I need another number). - explanations on how to praticipate to the conference call (number to call...) Finally, I apologize again (and I ask especially Mr. Martinez to forgive me) if I have introduced some mess in your discussions. Best regards Laurent T. --------------------------------------------------------------------------- V Laurent Thiebaut tel: +33 (0)1 3077 0645 A L C A T E L e.mail:laurent.thiebaut@alcatel.fr --------------------------------------------------------------------------- ______________________________ Reply Separator _________________________________ Subject: Re: Alcatel Reaction on H.323m contributions Author: martinze(a)CIG.MOT.COM Date: 15/11/99 21:01 Dear MR. Thiebaut, The document you just send out has my name on the contact list. Which you edited without my consent. You should respect everyone's work and next time you change any contribution you put your name and use a different MTD. The original MTD-05 is in. ftp://standard.pictel.com/avc-site/Incoming Also the contribution source is "Mobility Ad-hoc group"??? I am part of the "Mobility AD-HOC group" and again neither myself or anyone representing Motorola or myself gave MR. Thiebaut permission or concur the use of the "Mobility Ad-hoc group" as the source. I hope you do not represent how things are done in 3GPP. MR. Thiebaut, on your blindness attempt to re-used my work to promote your own views. Let me warn you, the document was put in informational only. I send out email that we should restrain from comments until we went over all the contributions first in the conference call meeting. To ALL, The Edited MTD-05 in this email is not from Motorola please contact MR. Laurent Thiebaut <LAURENT.THIEBAUT(a)ALCATEL.FR> with your comments. I would not even bother to use the SG16 mailer to do so. see below for further comments: Laurent Thiebaut wrote: > Hello everybody, > I have just subscribe to itu-sg16. > I'm mostly interested in H.323 link with radio access, being involved in > 3GPP standardization (3GPP S2 working group responsible of network > architecture) > > Please find attached some comments on Contribution "Integrating > 3GPP's option-1 architecture into the H.323 wireless IP mobility > system and a full migration from GPRS to a Multimedia IP network > proposal" (file MTD-05) - source Motorola - to be discussed on > wednesday about H323 mobility. > > - comment on section "Alternate Proposal for an all IP option for 3GPP > R'00. The purpose the all IP proposal is also to allow support of release > 99 CS domain terminals. In addition it will also support the IP based > services of option 1." > > The figure shown in the contribution does **NOT** correspond to the > support of the CS terminals as described in 3GPP 23.922. This option 2 > of the 3GPP standard corresponds to the option 1 architecture plus > -- a MSC server mainly that comprises the call control and > mobility control parts of a GSM/UMTS R99 MSC. > MSC server controls the parts of the call state that pertain to > connection control for media channels in a MGW. > -- A GMSC server that mainly comprises the call control and > mobility control parts of a GSM/UMTS R99 GMSC. > The attached MTD05comment.zip contains extracts from 3GPP23.922 that > explain the 3GPP position on network architecture. The following is clearly stated in the document: For simplicity, only the 3GPP interfaces relevant to H.323 interfaces are shown for discussion. If one wants to compare, please See 3G TR 23.922 version 1.0.0[6] for full details of option 1. > > > The following further discrepancies between contribution MTD05 and > 3GPP specifications are: > -- The network architecture defined by 3GPP does *NOT* > imply to have the GK and the SGSN function mixed, > -- nor has 3GPP accepted to merge the GGSN and the MG > functions > -- nor has 3GPP accepted to have a Gi interface between > UTRAN (radio) and GGSN (Gateway to Packet Data networks such as > Intranets / ISPs). > Merging of functions is always possible at the implementation level > but should not be dictated by standardization when not necessary. > > As H.323 networks may have to interact with other non 3GPP radio (and > even mobile, non terrestrial radio) networks, it is better to have, > as 3GPP has done, a clear separation between (radio) access bearer > layer - UTRAN, ERAN, SGSN, GGSN for 3GPP networks, PDSN for CDMA2000 > networks - and multimedia call control layer e.g. GK. What I am talking about is "Full migration from GPRS to Multimedia IP network". Not a decompose MSC or GMSC the so-called Circuit Switched Trunk Gateway WGW (aka switch) and MSC server (aka SCP) your so-called all IP concepts. Finally in a full IP network the only separation that will exist is Circuit Switched networks (Old) and IP based networks (New). The bridge between the Old and New, will be the Signaling gateways and media gateways. Conclusion: ---------------- The H.323 mobility group should also consider the interworking of the GPRS network and provide a GPRS migration path to a full IP network solution. Such as the work in H.323 is providing an interworking and migration path for the PSTN to a full IP network solution. In addition the H.323 mobility group could include the two options "Alternate Proposal for an all IP option for 3GPP R'00" interim solution, and the Full migration from GPRS into H.323 Annex-H interworking sections. Further details can be discussed within the H.323 mobility group. > > > Best regards > Laurent T. > --------------------------------------------------------------------------- > V Laurent Thiebaut tel: +33 (0)1 3077 0645 > A L C A T E L e.mail:laurent.thiebaut@alcatel.fr > --------------------------------------------------------------------------- > (Alcatel representant to 3GPP SA Working group 2 that is responsible of 3GPP > system architecture) > > ------------------------------------------------------------------------ > Name: mtd-05~1.zip > mtd-05~1.zip Type: Winzip32 File (application/x-winzip) > Encoding: base64 -- 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.450.3 interrogation procedure
by Henri M�enp�� 16 Nov '99

16 Nov '99

Thank you Karl for your answer. I do have two follow-ups though: 1) I suppose you meant "...information to the interrogating user..." rather than "served user" in your answer (according to H.450.3 terminology) ?!? 2) So this information is returned to the interrogating user on a per activated diversion basis. E.g. served user returns two CD activations: "CFU to number X with remoteEnabled TRUE" and "CFB to number Y with remoteEnabled FALSE". Now, the interrogating user knows that IT can deactivate/reactivate the CFU of the served user, but not the CFB activation?? This is the only way I can understand it at the moment. Is this really the logic behind it? -Henri Mäenpää -----Original Message----- From: EXT Karl.Klaghofer(a)icn.siemens.de [mailto:Karl.Klaghofer@icn.siemens.de] Sent: 15. November 1999 21:30 To: ITU-SG16(a)mailbag.cps.intel.com Subject: AW: H.450.3 interrogation procedure Henri, By means of this field, the interrogation result may provide information to the served user, whether remote activation has been enabled (allowed). Karl Klaghofer > -----Ursprüngliche Nachricht----- > Von: Henri Mdenpdd [SMTP:henri.maenpaa@NOKIA.COM] > Gesendet am: Donnerstag, 11. November 1999 12:29 > An: ITU-SG16(a)mailbag.cps.intel.com > Betreff: H.450.3 interrogation procedure > > All, > > I have a question concerning H.450.3 Call Diversion supplementary service, > and more specifically about the interrogation procedure. > > The response to an interrogation of current activations consists of a list > of IntResult IEs. > Each of these describe one diversion activation "description". Among the > information fields is this boolean value remoteEnabled. > What is the purpose of this? > > -Henri Mäenpää

1 0