Hi, Everyone:
I missed one point in the last email. We would also like to thank Ed for his excellent effort as an editor of H.323 Annex H in a difficult time when the idea H.323 mobility was yet to be clearer differentiating itself from lower layer IP and wireless mobility.
More importantly, Ed will be around with us as a contributor which is the most important need for H.323 Annex H.
Best regards, Radhika R. Roy, AT&T H.323 Ad Hoc Mobility Group
PS: Paul Guram - It is OK for me for the conf call on March 20, 22, 23, & 24 (NOT on March 21).
-----Original Message----- From: Roy, Radhika R, ALARC Sent: Sunday, February 20, 2000 1:28 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Re: Ad Hoc Mobility Group
Hi, Everyone:
Let us all welcome Paul in his effort to continue the work of H.323 Annex H for arranging the conference calls between now and the next Rap. meeting to be held on May 15-19 so that we can determine this important document in November 2000.
Let us also welcome Jaakko to work as the editor of Annex H as well as Paul Reddy for his excellent job for performing his work related to H.246 Annex E which had been determined in the last Feb 7-18 SG16 meeting. Now we have set a mark that H.323 is becoming ready to support mobility.
The next important thing is that we have to complete H.323 Annex H first. As Paul pointed out: Let us start with a scenario of H.323 - Roaming within an H.323 Network.
In the meantime, I also have a plan to send an email to Jean-Claude related to VLF and HLF information flows in the context H.323 mobility. I guess that this will also provide an opportunity to all how this problem can be addressed in the context of H.323 mobility.
The time in the conference call is very precious and we only be able to hold few conferences before the next Rap. meeting. We definitely have to make decisions more quickly in the conf calls for putting more stuffs by the editor so that the document can take a reasonable shape for determination in November 2000.
We hope that we have crossed the first phase of our understanding how we can address H.323 mobility problems. Any discussions via emails will expedite our understanding more quickly because the time in the conference calls is very short.
I would also request Paul to clarify how the contributions for the conference calls could be sent(I guess that the editor will be the right person). Editor can provide the URL and contribution number as we did in the past.
Best Regards, Radhika R. Roy AT&T +1 732 420 1580 rrroy@att.com
-----Original Message----- From: Guram Paul-LPG019 [mailto:lpg019@EMAIL.MOT.COM] Sent: Saturday, February 19, 2000 6:06 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Ad Hoc Mobility Group
Hello SG16 ad hoc mobility group members,
The following is a report on the current status and future plan of this ad hoc group. If I have missed out on any important points please respond to the group.
1. To ensure rapid completion of sufficient work in Annex H such that it can be considered for determination at the earliest opportunity, Paul Guram (Motorola) has been elected to chair future meetings of the mobility ad hoc group. It is planned to hold a number of conference calls, kindly facilitated by IMTC (as before), between now and the Rapporteurs meeting in May in Osaka. The group will always endeavour to reach quick agreed conclusions, after appropriate debate, to help the editor of Annex H to complete his task.
2. Ed Martinez (Motorola) has indicated that, due to his time being taken up by other work in his company, he is unable to additionally carry out the duties of the editorship for Annex H. The ad group will miss Ed and would like to thank him for the work he did and the leadership he showed in making mobility part of the overall H.323 agenda. Jaakko Sundquist (Nokia), who performed the editor's work in the Geneva meeting because of Ed's absence, has accepted to become the new editor for Annex H. This will, no doubt, be officially confirmed by Dale Skran (Q13 Rapporteur) in due course.
3. The next conference call is planned to be during the week beginning 20 March. Please inform me personally, i.e. not via the reflector, as to which dates (20 March to 24 March) are suitable for you to attend, and I will then arrange for the meeting to take place on the most appropriate date. The agenda of this meeting is as below. The main objective is to (a) define mobility scenarios, and (b) to agree on the scenario that we will pursue first for Annex H. This will help to focus on our work of defining all the aspects of this chosen scenario under the guidelines of our agreed terms of reference at the Geneva meeting. (To help in defining the scenarios, a look at the ETSI Tiphon scenarios may be useful. However, typical example scenarios are "roaming within an H.323 network", "inter-working between PSTN and H.323 networks for terminals" etc. etc. Contributions (with diagrams) on the scenario topics are to be sent via the reflector by Friday the 10th March. This will give all the participants enough time to consider the proposals for the meeting. This will allow discussion on items already seen and studied by the participants, thus saving time on lengthy presentations by the contributors, and secondly allowing participants, who may not to be able to take part in the live discussions, to have the opportunity to communicate their comments via email. Agenda: 1. Brief Introductions and agreement of agenda 2. Mobility Scenarios for Annex H 3. Adoption of the first scenario to study (in its entirety) 4. Issues related to the progress on Annex I, and H.246 Annex E 5. Report back from other mobility groups (3GPP, 3G.IP, IMT2000, MWIF, etc.). (this will be given by any participant who attends/has access to the appropriate group, and information will be that relevant to our work) 6. Any other business 7. Agenda and date of next conference call
4. On 17 February morning there was a joint ad hoc meeting with the JQG4 from SG11. See the notes below which are also being sent to JQG4. Interaction between JQG4 and our ad hoc group will continue at appropriate times in order to advance our respective work in the two groups.
Notes of a Joint Ad Hoc Meeting between SG11/ JQG4 and SG16/Ad hoc Mobility Group, on Thursday 17 February 2000 in Geneva
Present: Jean-Claude Samou France Telecom Frederic Delmond France Telecom Janusz Dobrowaski Lucent Technologies Vineet Kumar INTEL Paul Reddy INTEL Nicolas Tran Alcatel CIT Tatiana Tchaika ITU-T Paul Guram Motorola
JQG4 Issue Manager Jean-Claude Samou explained that there are five JQGs in the IMT2000 area:
JQG1 deals with radio aspects. Matters on the air interface are directly handled by other bodies such as 3GPP, JQG2 did not start, JQG3 deals with VHE scenarios and protocols. Since this is IN related, Question 22 of SG11 progresses the work, JQG4 deals with the Mobility Management aspects, and JQG5 deals with the bearer control protocol and moves are afoot to move this work into WP2 of SG11.
There is work in the IMT2000 area which could help the work in the SG16 mobility ad hoc group:
H.246 Annex E defines the NNI between H.323 and GSM/ANSI-41. Work on the development of a common mobility management protocol is going on in IMT2000. We need to look at how each group can help each other in this respect, and see if the common set of operations could be adopted for the SG16.
A generic state machine being developed Q22/11 should be studied to help the SG16 ad hoc group to see if it can be applicable to the packet network.
The relevant recommendations for study are Q.1751 and Q.1721.
Mr Delmond presented the following output document. This was seen as very useful input into the later work to be done within Annex H.
<<JQG4 Output Geneva 9910 v5.1.doc>>
Regards Paul