- sg16-avd - lists.packetizer.com

Comments on MTD-03/03a
by Roy, Radhika R, ALARC 17 Nov '99

17 Nov '99

Hi, Ed and Everyone: With respect the editor's document (MTD-03/03a: Annex H (User, Terminal and Service Mobility in H.323) submitted by Ed Martinez, I have additional comments: Section 5.1 Basic Identification Concepts: Location Area Identity (set of Network Attachments associated)* * Please add the following: Note that Location Area Identity "some members have some objection to agree on this term, but we will revisit these terms when we finalize our architectural solution." I would request to add this comment in the document as we did for other cases. Best regards, Radhika R. Roy AT&T

1 0

Minutes from the H.323 Mobility Meeting
by Paul E. Jones 17 Nov '99

17 Nov '99

H.323 Mobility Meeting November 17, 1999 8-10AM EST Relevant files can be found here: ftp://standard.pictel.com/avc-site/Incoming/H.323_Mobility Meeting Scope ------------- User, service, and terminal mobility (Annex H/H.323) Liaisons -------- It was noted that the ITU-T SG16 will liaison with ITU-T SG11, ITU-R IMT-2000, ETSI TIPHON, as they are also addressing mobility. It was also suggested that we provide information to the IMTC (http://www.imtc.org) and 3GPP (http://www.3gpp.org/) although they are not a standards body, per se. Report from Red Bank -------------------- MTD-02 reiterated what was discussed and agreed to in Red Bank. It was noted that TD-65 from Red Bank was an initial outline, but that was expanded and can be found in MTD-04a. MTD-03 (Draft Annex H) ---------------------- This document contains the current draft text of H.323 Annex H. This document defines the ideas, functions, and entities of the H.323 mobile system. It also defines the requirements and architecture, though those sections are not fleshed out nor agreed to. People objected to the statement in the Scope section that stated "NPoA can change also during a call, thus allowing handovers", since we do not yet have an architecture defined. It was also suggested that we remove the references to IMT-2000, as it implies the H.323 mobile system will be compatible with IMT-2000. In reality, we want to borrow their ideas, but interworking will still be required between H.323 systems and IMT-2000 systems. MTD-04 (Additional Items for Annex H Outlines) ---------------------------------------------- Several new sections to Annex H were proposed, including the areas of reliable transport of signaling, roaming interworking with non-H.323 networks, handover interworking with non-H.323 networks, non-H.323 supplementary services interworking, and mobile IP network interworking. However, only sections on roaming interworking with non-H.323 networks and non-H.323 supplementary services interworking were accepted as new sections in Annex H. Some issues were felt out of scope and others were felt as appropriate for Annex I/H.323. Closing ------- It was agreed that future conferences will be hosted by the IMTC. Since little progress was made during the conference call, more discussion needs to take place on the mailing list. Prior to the next call, we will narrow the number of documents we will discuss during the call. The next call will be Monday, November 29, 1999 from 8-10AM PST.

1 0

Re: MTD-07 upload assistance requested
by Edgar Martinez [1] 17 Nov '99

17 Nov '99

done "Anders Svennevik (ERA)" wrote: > I have not been able to upload my MTD to the avc-site, I think due to our firewall. > Could somebody please place it at > ftp://standard.pictel.com/avc-site/Incoming/H323_Mobility > > The title is 'Definition of terms for H.323 Annex H.' > > Anders Svennevik > Ericsson Radio Systems > > <<mtd07.zip>> > > ------------------------------------------------------------------------ > Name: mtd07.zip > mtd07.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.323 mobility: Reminder Conference Call on Nov 17, 1999 and the Agenda
by Roy, Radhika R, ALARC 17 Nov '99

17 Nov '99

Hi, Everyone: In addition to agenda distributed by Paul, I like to mention that any APCs/TDs submitted in the Red Bank SG16 Q.13 meeting related to H.323 mobility can also be discussed as appropriate. As I mentioned that we did not have time to go through all items of each contribution in the Red Bank meeting. Many Red Bank contributions have more detail discussion of H.323 mobility functional entities and architecture related to Annex H. Similar is the case for H.246 Annex E. Best regards, Radhika R. Roy AT&T > -----Original Message----- > From: Reddy, Paul K [SMTP:paul.k.reddy@INTEL.COM] > Sent: Wednesday, November 17, 1999 12:37 AM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H.323 mobility:Reminder Conference Call on Nov 17, 1999 > and the Agenda > > Hi Everyone, > > ******************************************************** > REMINDER REMINDER REMINDER > ******************************************************** > > Please see the following information for the tomorrow's conference call > and > the contributions assigned to the Agenda Items, and also the list of > contributions to be discussed tomorrow: > > Conference Call Bridge Information: > Date: November 17, 1999 > Time: 8:00 AM to 10:00 AM (Pacific Standard Time (PST)) > > Conference Call Bridge Number: +1 (916)-356-9200 > Reservation Number: 3-327470 > Passcode: 5421571 > > Note: There are 20 ports available for the conference call, please use one > or two ports per company. > > Procedure to join the conference call: > · Please call +1 (916)-356-9200 and > · wait for voice prompt to enter the first digit of reservation number, > and > enter "3"as the first digit of reservation number, > · and then wait for the voice prompt to enter the passcode, and enter > 5421571 as passcode, then you will be bridged to conference call. > > Agenda > 1. Call to Order & Opening Remarks > 2. Attendance Registration > 3. Introduction and Numbering of Contributions: MTD-14 > 4. Agenda Review and Approval:- MTD-01a > 4a. Review H.323 Mobility Ad Hoc Meeting report: TD-65.doc > 5. Correspondence to other standards groups > 6. Old Business:- MTD-02a, MTD-04a > 6a. review: TD-16, TD-42b > 6b. H.323 Mobility Functional Entities (HLF, VLF, AuF, IWF: MTD-03a, > MTD-06,MTD-07, MTD-09 > 6c. H.323 Mobility Architecture :- MTD-05a, MTD-08 > 6d. > 7. New Business > 7a. H.323 Interworking with PLMNs (H.246 Annex E scope, terms of > reference and work plan): MTD-13, MTD-10a > 8. Meeting Schedule: > 8a. Discuss next conference call meetings: MTD-11, MTD-12 > 9. Review Assignments > 10. Review Workplan > 11. Open Discussion > 12. Adjourn > > The following are the list of contributions for tomorrows conference call: > > MTD-01a: > Title: H.323 Mobility Ad Hoc Group Interim meeting via Conference Call > Agenda > Company: Intel > > MTD-02a: > Title: H.323 Mobility Ad Hoc Group Activity Report > Company: AT&T > > MTD-03a: > Title: H.323 Annex-H Draft and outline > Company: Motorola > > MTD-04a: > 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-05a: > Title: Informational only) Full migration from GPRS > to a Multimedia IP network (from the H.323 IP network > perspective). > Company: Motorola > > MTD-06: > Title: H.323 Functional Architecture and Reference Points. > Company: Nokia > > MTD-07: "Definition of terms for H.323 Annex H". > Company: Ericsson << Not uploaded to the reflector>>> > > MTD-08: 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. > Company: Alcatel > > MTD-09: > Title: Clear Split of functions between multimedia Call Control and > (radio) > Access networks. > Company: Alcatel > > MTD-10a: > Title: IMT-2000 Global Roaming and Interworking Scenarios > (Reference only) > Company: Motorola > > MTD-11: > Title: H.323 Mobility Ad Hoc Group Interim meeting via Conference Call > Agenda > Company: Nokia, Intel > > MTD-12: > Title: AT&T's proposal to host next H.323 Mobility Ad Hoc group conference > call. > Company: AT&T > > MTD-13: > Title: H.246 Annex E Goal and Workplan > Company: Intel > > MTD-14: > Title: List of all H.323 Mobility contributions submitted at Red Bank, NJ, > USA and Nov 17, 1999 conference call > Company: AT&T, Intel > > All of the documents have been copied into the following directory: > http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/Conference_ > Ca > ll_11_17_1999 except Ericsson's contribution MTD-07, which is not > submitted > yet. > > 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

1 0

Re: H.323 mobility Conference Call
by Roy, Radhika R, ALARC 17 Nov '99

17 Nov '99

All: Pl. see change in title. Paul has been requested to upload the document. Thanks, Radhika > -----Original Message----- > From: Reddy, Paul K [SMTP:paul.k.reddy@INTEL.COM] > Sent: Tuesday, November 16, 1999 6:21 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: Re: H.323 mobility Conference Call > > Hi Radhika, > > I have assigned a MTD number for the following AT&T proposal to host next > conference call > > MTD-12: > Title: AT&T's proposal to host next H.323 Mobility Ad Hoc group conference > call. > Company: AT&T > > Can you please include the following proposal in the MTD-12 document and > send it me or upload it to > http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ directory. > > Note: All requests for MTD numbers and document submissions will be closed > at 6:30 PM (Pacific Standard Time), USA time for tomorrows conference > call. > > regards, > Paul > > 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 > > > > -----Original Message----- > From: Roy, Radhika R, ALARC [mailto:rrroy@ATT.COM] > Sent: Tuesday, November 16, 1999 2:37 PM > To: ITU-SG16(a)MAILBAG.INTEL.COM > Subject: H.323 mobility Conference Call > > > 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

MTD-07 upload assistance requested
by Anders Svennevik (ERA) 17 Nov '99

17 Nov '99

I have not been able to upload my MTD to the avc-site, I think due to our firewall. Could somebody please place it at ftp://standard.pictel.com/avc-site/Incoming/H323_Mobility The title is 'Definition of terms for H.323 Annex H.' Anders Svennevik Ericsson Radio Systems <<mtd07.zip>>

1 0

Re: H.323 mobility:Reminder Conference Call on Nov 17, 1999 and the Agenda
by Reddy, Paul K 17 Nov '99

17 Nov '99

Hi Everyone, ******************************************************** REMINDER REMINDER REMINDER ******************************************************** Please see the following information for the tomorrow's conference call and the contributions assigned to the Agenda Items, and also the list of contributions to be discussed tomorrow: Conference Call Bridge Information: Date: November 17, 1999 Time: 8:00 AM to 10:00 AM (Pacific Standard Time (PST)) Conference Call Bridge Number: +1 (916)-356-9200 Reservation Number: 3-327470 Passcode: 5421571 Note: There are 20 ports available for the conference call, please use one or two ports per company. Procedure to join the conference call: · Please call +1 (916)-356-9200 and · wait for voice prompt to enter the first digit of reservation number, and enter "3"as the first digit of reservation number, · and then wait for the voice prompt to enter the passcode, and enter 5421571 as passcode, then you will be bridged to conference call. Agenda 1. Call to Order & Opening Remarks 2. Attendance Registration 3. Introduction and Numbering of Contributions: MTD-14 4. Agenda Review and Approval:- MTD-01a 4a. Review H.323 Mobility Ad Hoc Meeting report: TD-65.doc 5. Correspondence to other standards groups 6. Old Business:- MTD-02a, MTD-04a 6a. review: TD-16, TD-42b 6b. H.323 Mobility Functional Entities (HLF, VLF, AuF, IWF: MTD-03a, MTD-06,MTD-07, MTD-09 6c. H.323 Mobility Architecture :- MTD-05a, MTD-08 6d. 7. New Business 7a. H.323 Interworking with PLMNs (H.246 Annex E scope, terms of reference and work plan): MTD-13, MTD-10a 8. Meeting Schedule: 8a. Discuss next conference call meetings: MTD-11, MTD-12 9. Review Assignments 10. Review Workplan 11. Open Discussion 12. Adjourn The following are the list of contributions for tomorrows conference call: MTD-01a: Title: H.323 Mobility Ad Hoc Group Interim meeting via Conference Call Agenda Company: Intel MTD-02a: Title: H.323 Mobility Ad Hoc Group Activity Report Company: AT&T MTD-03a: Title: H.323 Annex-H Draft and outline Company: Motorola MTD-04a: 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-05a: Title: Informational only) Full migration from GPRS to a Multimedia IP network (from the H.323 IP network perspective). Company: Motorola MTD-06: Title: H.323 Functional Architecture and Reference Points. Company: Nokia MTD-07: "Definition of terms for H.323 Annex H". Company: Ericsson << Not uploaded to the reflector>>> MTD-08: 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. Company: Alcatel MTD-09: Title: Clear Split of functions between multimedia Call Control and (radio) Access networks. Company: Alcatel MTD-10a: Title: IMT-2000 Global Roaming and Interworking Scenarios (Reference only) Company: Motorola MTD-11: Title: H.323 Mobility Ad Hoc Group Interim meeting via Conference Call Agenda Company: Nokia, Intel MTD-12: Title: AT&T's proposal to host next H.323 Mobility Ad Hoc group conference call. Company: AT&T MTD-13: Title: H.246 Annex E Goal and Workplan Company: Intel MTD-14: Title: List of all H.323 Mobility contributions submitted at Red Bank, NJ, USA and Nov 17, 1999 conference call Company: AT&T, Intel All of the documents have been copied into the following directory: http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/Conference_Ca ll_11_17_1999 except Ericsson's contribution MTD-07, which is not submitted yet. 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

1 0

Re: H.323 Mobility: Quick comments on MTDs
by Reddy, Paul K 16 Nov '99

16 Nov '99

Hi All, Intel supports the Nokia's proposal on the detailed definitions concerning the PLMN-interworking should be handled in the H.246 Annex E. Intel is bringing in a contribution on H.246 Annex E Goal and Workplan as MTD-13 document. regards, 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: Jaakko Sundquist [mailto:jaakko.sundquist@NOKIA.COM] Sent: Tuesday, November 16, 1999 5:59 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: H.323 Mobility: Quick comments on MTDs 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

Re: H.323 mobility Conference Call
by Reddy, Paul K 16 Nov '99

16 Nov '99

Hi Radhika, I have assigned a MTD number for the following AT&T proposal to host next conference call MTD-12: Title: AT&T's proposal to host next H.323 Mobility Ad Hoc group conference call. Company: AT&T Can you please include the following proposal in the MTD-12 document and send it me or upload it to http://standard.pictel.com/ftp/avc-site/Incoming/H323_Mobility/ directory. Note: All requests for MTD numbers and document submissions will be closed at 6:30 PM (Pacific Standard Time), USA time for tomorrows conference call. regards, Paul 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 -----Original Message----- From: Roy, Radhika R, ALARC [mailto:rrroy@ATT.COM] Sent: Tuesday, November 16, 1999 2:37 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: H.323 mobility Conference Call 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: 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

H.323 mobility: Reserve one MTD and revised two
by Edgar Martinez [1] 16 Nov '99

16 Nov '99

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

Re: Alcatel Reaction on H.323m contributions
by Reddy, Paul K 15 Nov '99

15 Nov '99

Hi Laurent, Welcome to the Group. For your information, ITU-T SG16 Q13/A14 H.323 Mobility Annex-H group has formed a H.323 Mobility Ad Hoc working group in order to make progress in the development of H.323 Mobility Annex-H standard specifications. The H.323 Mobility Ad Hoc group agreed to have interim conference call meeting on Nov 17, 1999 8:00 am to 10:00 am (PST) in order to discuss contributions from different interested parties towards 6b. H.323 Mobility Functional Entities (HLF, VLF, AuF, IWF) 6c. H.323 Mobility Architecture of the agenda items. The following procedure was adopted by the Ad Hoc group: 1. Interested parties submitting contributions should request MTD-XX number from Conference Call chair and upload the document into the ftp site shown below. 2. Your MTD-08 document will be assigned to an agenda item and it will be discussed during the conference call accordingly. Your enclosed document showed the MTD-05 number,which is already assigned to Motorola. I am assigning the following MTD number for your document, please make changes and upload the document to the ftp://standard.pictel.com/avc-site/Incoming directory. MTD-08: 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. Company: Alcatel Regards, -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: Laurent Thiebaut [mailto:LAURENT.THIEBAUT@ALCATEL.FR] Sent: Monday, November 15, 1999 9:40 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: Alcatel Reaction on H.323m contributions 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 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. 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)

1 0

Re: H.323 mobility:MTD number request
by Reddy, Paul K 15 Nov '99

15 Nov '99

Hi Anders, The following MTD number has been assigned to your document: MTD-07: "Definition of terms for H.323 Annex H". Company: Ericsson Regards, -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: Anders Svennevik (ERA) [mailto:Anders.Svennevik@era.ericsson.se] Sent: Monday, November 15, 1999 1:17 AM To: 'Mailing list for parties associated with ITU-T Study Group 16'; 'paul.k.reddy(a)INTEL.COM' Subject: RE: H.323 mobility:MTD number request Hi, Could I have an MTD number? The title of the document will most likely be something along the lines of "Defintion of terms for H.323 Annex H". Anders Svennevik Ericsson Radio

1 0

Re: Alcatel Reaction on H.323m contributions
by Edgar Martinez [1] 15 Nov '99

15 Nov '99

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

[Robustness] Conference call - final reminder and more agenda ite ms -- Tuesday, November 16 11AM EST USA
by Maureen Stillman 15 Nov '99

15 Nov '99

This is a final reminder that we will be having the first teleconference on robustness sponsored by Nokia on Tuesday, November 16 at 11AM EST USA. The phone number to call is: 613-688-2795 and the access code is 1097#. You must enter the pound key after the access code. The tentative agenda is: Definitions of Terms for robustness Items that can be settled in the short term Additional agenda items from the mailing list: They are topics we should discuss during the phone call or decide to defer. I took most of this text directly from your e-mail messages.... Summary of Agenda Items from the mailing list: 1) contribution D.225 - "Framework for Reliable H.323 Gatekeeper Architectures" How will this contribution be added and referenced in the "terms of reference" Red Bank document TD-028? 2) Further discussion of the proposal in Red Bank to strike the text in the current version that allows for the closure of the call signaling channel while a call is still in progress. 3) Recovery from GK crash 4) The more difficult problem is that upon TCP channel failure, the TPKT connection gets out of synch. It means that the application layer doesn't know automatically what part of information got lost. In this case, in order to synchronize H.323 Call state between the two sides, application level handshake must be introduced. This is also definitely a job for our Robustness group. 5) Another issue we have at hand is that of "what is a call signaling channel?" There used to be a one to one mapping between TCP connections and call signaling channels. This is not the case any longer-- one may have multiple calls over the same call signaling channel and one may not even use TCP. Making this distinction will be important for the robustness work being started, as the "logical" connection (the call signaling channel) and the "physical" connection (the TCP or UDP connection) must be referred to independently. (I'm quite open to new terms for here...). It is important to recognize whether an endpoint has closed the call signaling channel (as we understand it today) or if the physical connection has failed. Since we do not signal that we are going to close the call signaling channel today-- we just close the socket-- it makes this problem more difficult. 6) Actually, the SCTP transport protocol defined by Sigtran is specifically designed to address the path level robustness. It is designed to support multiple NIC cards (a.k.a. multi-homed nodes) and provide transparent interface and path failure detection and recovery. 7) think that Sigtran could be used to provide the GK "switch over" to a hot standby GK from the IP layer point of view. Conference Call Participants (so far): all are welcome to join in! Rich Bowen rkbowen(a)cisco.com Roy Radhika rrroy(a)att.com Orit Levin orit(a)radvision.com Dave Walker dave_walker(a)Mitel.com Terry Anderson tla(a)lucent.com Kumar, Vineet vineet.kumar(a)intel.com Asaf Steifeld AsafS(a)radware.co.il Michael Corrigan Michael_Corrigan(a)mw.3com.com Robert Callaghan Robert.Callaghan(a)siemenscom.com Glen Freundlich ggf(a)lucent.com Boaz Michaely Boaz_Michaely(a)vocaltec.com Jean-philippe Caradec caradec(a)piano.grenoble.hp.com Talk to you Tuesday.... -- maureen Maureen Stillman Member of Scientific Staff Voice: (607)273-0724 x62 Nokia IP Telephony Fax: (607)275-3610 127 W. State Street Mobile: (607)227-2933 Ithaca, NY 14850 e-mail: maureen.stillman(a)nokia.com www.nokia.com

1 0

AW: H.450.3 interrogation procedure
by Karl.Klaghofer＠ICN.SIEMENS.DE 15 Nov '99

15 Nov '99

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