December 2001 - sg16-avd - lists.packetizer.com

Re: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informat i on
by Reddy, Paul K 06 Dec '01

06 Dec '01

Hi Karl, I will address this in the next conference call meeting. H.22x is in the scope of Q.5. We are targeting the H.22x work to be complete by February 2002 along with H.MMS.1 recommendations. Regards, Paul -----Original Message----- From: Klaghofer Karl ICN EN HC ID 14 [mailto:Karl.Klaghofer@icn.siemens.de] Sent: Friday, November 30, 2001 12:51 AM To: Reddy, Paul K Cc: ITU-SG16(a)echo.jf.INTEL.COM Subject: AW: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informat i on Hi Paul, I do not see the H.22x standard being listed as document within the scope of these upcoming Q.5 conference calls. Who (which Question) will drive the H.22x standard ? How can H.MMS.1 for example be completed by February if the actual protocol that would be used for mobility management (H.22x) is out of the scope of these Q.5 discussions ? Thanks, Karl Klaghofer, Siemens -----Ursprüngliche Nachricht----- Von: Reddy, Paul K [mailto:paul.k.reddy@INTEL.COM] Gesendet: Mittwoch, 28. November 2001 23:01 An: ITU-SG16(a)echo.jf.INTEL.COM Betreff: Re: [Mobility] Resending the email with H.235 Annex G added to th e agenda of ITU-T SG16 WP2 Q.2/Q.5/Q.G Conference Call meetings informati on Dear ITU-T SG16 WP2 Colleagues and Mobility Experts, Sorry for the delay in sending this email to the reflector and also due the outages of the SG16 reflector last week the last sent email could not be posted on this reflector. Please accept our apologies. As Rapporteur of Question_5/SG16 (Mobility for Multimedia Systems and Services) agreed in Dublin, Ireland Rapporteur's meeting to organize 3 two hours conference call meetings during Nov, Dec and January months before ITU-T SG16 face to face meeting during February, 2002 in Geneva, Switzerland. The goal of following conference call meetings are to make progress on the following recommendations: 1. H.MMS.0: User/Service Mobility Management for H.323 Multimedia Systems. 2. H.MMS.1: Terminal Mobility Management for H.323 Multimedia Systems. 3. H.MMS.2: Inter-working and Interoperability between Mobility Management for Multimedia systems and Cellular PLMNs. 4. H.MMS.3: Presence and Instant Messaging Services for mobile and non-mobile Multimedia systems. 5. H.MMS.4: Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems 6. H.235 Annex-G: Security for Multimedia Mobility (User, Terminal, Service) services. For the status of the above recommendations and related documents, please see the enclosed Dublin's Q.5 Rapporteur's meeting report. Also, please go to URL <http://standard.pictel.com/ftp/avc-site/0110_Dub> http://standard.pictel.com/ftp/avc-site/0110_Dub for Q.5/16 documents. Guidelines for contributing and participating in the following Conference calls: 1. Companies and individual experts are welcome to contribute by uploading the contributions to ftp site: ftp://standard.pictel.com/avc-site/Incoming/Q5conf/ By due dates of each conference call meetings Contributions submission due dates: * For November 30, 2001 conference call is midnight (Pacific standard time) of Nov 28, 2001 * For December 18, 2001 conference call is midnight (Pacific standard time) of Dec 14, 2001 * For January 25, 2002 conference call is midnight (Pacific standard time) of Jan 18, 2001 2. Reply to this email to <mailto:paul.k.reddy@intel.com> paul.k.reddy(a)intel.com and get confirmation of your attendance on each of the conference call meetings in order to reserve the bridge port for a guarantee access during the conference call meetings. 3. Agenda for each Conference call meeting: * Introduction * Review contributions in the following order(Note: continue where we left off in one conference call meeting to another) i. H.MMS.1 (Terminal Mobility for H.323 MM systems) and H.22x.x (Mobility Management protocol and procedures) contributions. This recommendation is targeted for approval during Feb, 2002 SG16 meeting in Geneva. ii. H.MMS.0 (User Mobility, Service Mobility for Multimedia systems) contributions. This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iii. H.MMS.3 (Presence and IM services for mobile and non-mobile Multimedia Systems (e.g., H.323 systems)). This recommendation is targeted for approval during October, 2002 SG16 meeting in Geneva. iv. H.MMS.4 (Inter-working and Interoperability between H.MMS.3 and current Presence and IM systems). This recommendation is targeted for approval during Feb, 2003 SG16 meeting in Geneva. v. H.MMS.2 (Inter-working and Interoperability between Mobility Management for MM systems and Cellular PLMNs). This recommendation is targeted for approval during October, 2003 SG16 meeting in Geneva. vi. H.235 Annex G (Security for Multimedia Mobility Services). This recommendation with Security for Terminal mobility service is targeted for approval during Feb, 2002 SG16 meeting in Geneva. If you have any questions, please email Q.5/16 Rapporteur (Mr. Paul K. Reddy) at <mailto:paul.k.reddy@intel.com> paul.k.reddy(a)intel.com Conference call Bridge information: Conference call Meeting 1: Start: Nov 30, 2001 07:00 Pacific Standard Time End: Nov 30, 2001 09:00 Pacific Standard Time Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 9899887 --------------------------------------------------- Conference Call Meeting 2: Start: Dec 18, 2001 07:00 Pacific Standard Time End: Dec 18, 2001 09:00 Pacific Standard Time User Instructions: Date: Tuesday, December 18, 2001 Lines: 10 Duration: 120 minutes Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 6449818 ----------------------------------------------------- Conference Call Meeting 3: Start: Jan 25, 2002 07:00 Pacific Time End: Jan 25, 2002 09:00 Pacific Time Moderator REDDY, PAUL K US Dial-In Number: 1-877-299-1938 International Dial-In Number: 1-617-801-9666 Passcode: 3708752 ----------------------------------------------------- regards, Paul Paul K. Reddy Rapporteur of Q.5/16 ITU-T SG16 Working Party 2 Intel Labs, 2111 N.E. 25th Avenue, mailstop: JF3-377 Hillsboro, OR-97124, USA Tel: +1 (503)-264-9896 E-mail: paul.k.reddy(a)intel.com

1 0

Report of Q.5 (mobility) phone conference, 30 November 2001
by Horvath Ernst 06 Dec '01

06 Dec '01

Report of Q.5/SG16 (Mobility) conference call on November 30, 2001 (prepared by Ernst Horvath) Participants: Messrs. Bougant (FT), Euchner (Siemens), Horvath (Siemens); part time participation: Messrs. Reddy (Intel), Roy (AT&T) Available documents: New drafts of H.235 Annex G, H.MMS.0 and H.MMS.1; temporary documents TD-EH-01, TD-EH-02, TD-EH-03 and TD-FB-01a. Due to time limits, only the temporary documents were discussed. Results: 1) The proposals in TD-EH-01 and -02 regarding new recommendation H.22x were accepted. Mr. Reddy clarified the timeframe: => Target date for H.MMS.1, H.22x and H.225.0 Annex G: February 2002 Target date for H.MMS.0: October 2002 => Open issue: Editorship for H.22x (AI for Mr. Reddy to clarify. Is Mr. Ruditsky (Radvision) intereted?) 2) The rest of the time was spent on TD-EH-03 (comments on H.MMS.0) and TD-FB-01a (answers to these comments): * There are two possible "scopes" for H.MMS.0: (a) a framework for all other mobility work in SG16 or (b) a specification of service and user mobility. In case (a) other mobility documents (in particular H.MMS.1) could refer to H.MMS.0 for definitions, architecture and general concepts; in case (b) every mobility document would have to define its own architecture etc. Given the timeframe (see above), case (b) is the more sensible approach. Contributions on this issue are welcome (by email or by joining the next conference call). * Split of topics between H.MMS.0 and H.MMS.1: User mobility has also impacts on terminal mobility and cannot be eliminated completely from H.MMS.1. The figures in TD-FB-01a were not well understood and need further discussion by email. * The architecture for mobility is still unclear. In particular the role of MAFE was unclear (a single element here, but represents different elements in real systems, e.g. GK and BE in H.323). It was suggested to leave details of the MA (multimedia application, e.g. H.323) domain out of H.MMS.0 This needs further discussion by email. * It was decided to remove all protocol stuff from H.MMS.0 and refer to H.22x instead. The information flows will be specified on a high level of abstraction (in form of primiitves, as already present in some examples). * All message flow charts need to be reworked. More discussion needed (by email). 3) The next conference call on December 18, 2001 will continue with review of the remaining documents. Input on open items (architecture, scope or split of functionality) is urgently needed.

1 0

Report of the Dublin meeting AVD-2174
by OKUBO Sakae 05 Dec '01

05 Dec '01

Dear SG16 experts, On behalf of Mr. Paul Jones, manager of the Dublin meeting, I have placed the meeting report at the following place: ftp://standard.pictel.com/avc-site/0110_Dub/AVD-2174.zip or http://standard.pictel.com/ftp/avc-site/0110_Dub/AVD-2174.zip Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo(a)giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 *********************************************************

1 0