Jin and Liao,
I will like to inform you that ITU-sg16 has open up two new annexs in H.323 to support mobility.
H.323 Mobile Annex It was agreed during the joint meeting with Q11 to create a mobile Annex for H.323. This would take the form of a document or documents that address mobility issues, including:
Mobility, including user and service mobility Mobile issues including Layer 2 issues & timers Header compression Handoffs and the H.323 system architecture
Next Meeting Decision
H.323 Annex H (User and Service Mobility in H.323) E. Martinez (Motorola) H.323 Annex I (Terminal Mobility in H.323) (Toshiba)
Attached is the meeting information.
I resent this message because the attachments fail to deliver.
-- Subject: Re: comments on DTR07001v1_1_2r1 Date: Sun, 27 Jun 1999 07:57:36 +0800 (CST) From: Wan-jiun Liao wjliao@cc.ee.ntu.edu.tw To: "Edgar Martinez [1]" martinze@cig.mot.com CC: "Yang, Jin (Jin)" jinyang@lucent.com, TIPHON_WG7@LIST.ETSI.FR, Vli@eee.hku.hk, Wan-jiun Liao wjliao@cc.ee.ntu.edu.tw
Dear Edgar and Jin,
Thanks for your valuable comments on the part of mobile extensions to h.323. I am the author of this section. The point we would like address for our h.323 mobile extension is that we would like to demonstrate that h.323 provides an excellent environment for mobility support and thus tend to make modifications as few as possible to h.323 for mobility support. In fact, the article has been revised and extended (from infocom'99 one) since I came back from TiPHON meeting at Bangkok in May. Attached please find a copy of new revised version of mh323. Some of your questions may have answered.
Re. the following sentences,
My thoughts, rather then propose/add all the mobility extensions to H.323. I rather work on how to Tunnel Mobility Management (MM) messages from the RAN to a Wireless Call Server (WCS) via H.323. While in the same context work-out the WCS interface to the Gatekeeper to Tunnel through the TCAP/MAP messages to and from the IP network and the GSM MSC and HLR for interworking.
We have a work currently going on with a similar idea to this one. However, we still stick on making as less as possible modification to current h.323 for mobility support. The new work is almost done and will be able to support the IP network and the GSM (or DECT) MSC and HLR for interworking. We may presnet our new work at the next TiPHON's meeting then.
Thanks for your comments.
Best Reagrds,
Wanjiun Liao
On Sat, 26 Jun 1999, Edgar Martinez [1] wrote:
Dear Jin,
I am not the author of the section but I have some comments to add:
"Yang, Jin (Jin)" wrote:
Dear WG7 "roamers",
I am reading the DTR07001 draft on the part of "mobile extension to H323", section 5.11 with the following comments (I will not be able to attend the next meeting, so post my comments here):
..... "With H.323, data, voice, and video in an IP call are transmitted using the Real-time Transport Protocol [21]. "
data is not using RTP. voice and video does.
If we change the wording like the following will it be OK?
"With H.323, voice-data, and video-data in an IP call are transmitted using the Real-time Transport Protocol [21]. "
..... "Call setup and other call control signaling messages are carried out-of-band, sent through different paths other than those for the payload traffic. "
not necessarily different path.
We can change the text to read:
"In a reliable network Call setup and other call control signaling messages could be sent through different paths other than those for the payload traffic. "
-- *A reliable network are system that have a backup link connection running a reliable transport protocol like sigtran's CTP.
....... "Under the current version of H.323 service scope, however, host mobility is forbidden, resulting from the underlying IP mechanism that implicitly assumes that a host is fixed. "
Is this true? H323 is OK for mobile hosts if the mobility is provided at lower layers, which can be mobile IP based, or replying on layer2,e.g. wireless LAN layer 2 mobility support. H323, as an application layer protocol can be transparent. ......
Yes,
I propose to take out the foolowing:
"Under the current version of H.323 service scope, however, host mobility is forbidden, resulting from the underlying IP mechanism that implicitly assumes that a host is fixed. "
And replace it with:
"H323 could support mobile hosts if the mobility is provided at lower layers e.g., using IPv6, which can be mobile IP based, or replying on layer2 wireless LAN layer 2 mobility support. H323, as an application layer protocol can be transparent."
I tend to agreed with you and hope to see support of TCAP/MAP support on top of IPv6. oops!
"Moreover, Voice over IP service is a real-time connection-oriented service over packet-switched IP-based networks. Neither the circuit-switched cellular phone approach nor the connectionless Mobile IP mechanism is capable of providing mobile Internet telephony service. "
why? connection-oriented applications do not necessarily require connection-oriented transport. Although Mobile IP, as it is defined at this stage, has its limitations/issues for real-time applications in a highly, global mobile environment, people are working on it to resove them.
Iam looking towards 3GPP or TIPHON to provide us the option to send VoIP on the RAN IU-ps link. Reference to Liassion Statement sent to WG7 Bangkok 13TD146. As a first step.
.... "New approaches are required for mobile IP telephony. Through proper call setup signaling with the H.323 Gatekeeper, the address of the target endpoint (i.e., callee or called party) can be resolved before call establishment, enabling the service redirection to be completely handled in the application layer. Thus, it realizes mobile IP telephony services with IP. This approach enables mobility support without the need for additional new entities and with minimal modifications to the H.323 standard, allowing such mobile IP telephony service to be a valued-added feature in the existing H.323-compliant Internet telephony systems."
what is the extension, at the end?
My thoughts, rather then propose/add all the mobility extensions to H.323. I rather work on how to Tunnel Mobility Management (MM) messages from the RAN to a Wireless Call Server (WCS) via H.323. While in the same context work-out the WCS interface to the Gatekeeper to Tunnel through the TCAP/MAP messages to and from the IP network and the GSM MSC and HLR for interworking.
Mail archive for TIPHON_WG7 can be browsed at the following url :
http://www.etsi.org/tiphon/mailing.htm
-- 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/
Subject: Notice of the Berlin meeting Date: Fri, 25 Jun 1999 15:14:57 +0900 From: Sakae OKUBO okubo@GITI.OR.JP Reply-To: Mailing list for parties associated with ITU-T Study Group 16 ITU-SG16@mailbag.cps.intel.com To: ITU-SG16@mailbag.cps.intel.com
To Experts of ITU-T SG16 Q.12/16, Q.13/16 and Q.14/16
Cc Mr. P-A. Probst, Chairman of SG16 Mr. G. Helder, Vice-Chairman of SG16 Mr. F. Tosco, Chairman of WP2/16 Mr. F. Bigi, ITU-TSB Mr. T. Geary, Rapporteur for Q.11/16 Mr. G. Sullivan, Rapporteur for Q.15/16 Mr. J. Ott, Teles Mr. S. Wenger, Teles
De Sakae OKUBO Rapporteur for Q.12/16 in ITU-T SG16 TAO Waseda Research Center 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 Fax: +81 3 5287 7287 E-mail: okubo@giti.or.jp
Dale SKRAN Rapporteur for Q.13/16 in ITU-T SG16 Ascend Communications, Inc. 621 Shrewsbury Avenue Shrewsbury, NJ 07702 USA Tel: +1 908 450 1635 Fax: +1 908 450 1611 E-mail: Dale.Skran@ascend.com
Glen Freundlich Rapporteur for Q.14/16 in ITU-T SG16 Lucent Technologies 11900 N. Pecos Westminster, Colorado 80234 USA Tel: +1 303 538 2899 Fax: +1 303 538 3907 E-mail: ggf@lucent.com
---------------------------------------------------------- Subject: Notice of Q.12-14/16 Rapporteur Meeting in Berlin Date: 25 June 1999 ----------------------------------------------------------
Dear Q.12-14/16 experts,
The subject meeting of ITU-T SG16 experts will be held in Berlin, Germany at the kind invitation of TELES AG.
Please note that Q.11/16 and Q.15/16 will meet concurrently at the same place and have joint sessions with Q.12-14/16.
1. Date ^^^^^^^
2 (Monday) - 6 (Friday) August 1999 starting at 9:00 on the first day
2. Venue ^^^^^^^^
GRAND HOTEL ESPLANADE BERLIN Luetzowufer 15 10785 Berlin-Tiergarten Voice: +49 30 254 78-0 Fax: +49 30 265 1171 EMail: info@esplanade.de WWW: http://www.esplanade.de/eframe.htm
3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^
1) Review of the relevant group meetings
2) Q.12/16 B-ISDN multimedia systems and terminals
- White contribution for H.222.0 Amendment 7 - H.321 v2 Implementers Guide - H.310 v2 Implementers Guide - Work with Q.13 on high quality video transmission over IP - Future AV communication systems
3) Q.13/16 Packet switched multimedia systems and terminals
- Finalize white contributions for: * H.323 V3 * H.225.0 V3 * H.450.8 (Name Identification) * H.323 Annex G (Text SET) - Update H.323 Implementers guide - Further Develop: * H.323 Annex F (Secure SET) * H.323 Annex H (User/Service Mobility) * H.323 Annex I (Terminal Mobility) * H.450.9 (Call Completion on Busy) - Work with Q.14 on H.GCP white paper - Work with Q.14 on H.246 Annex C white paper - Work with Q.14 on H.246 Annex D
4) Q.14/16 Common protocols, MCUs and protocols for interworking with H.300-series terminals
- Finalize white contributions for: * Prepare H.gcp * Prepare H.246 Annex C * Prepare H.245 V6 * Prepare H.243 V2 * Prepare H.224 V2 - Progress work on IN-H.323 interface (H.246 Annex D) - Update implementers guide
5) Coordination with Q.11/16 and Q.15/16
- System aspects - Video coding aspects
6) Interaction with other groups
7) Future work plan
4. Documents ^^^^^^^^^^^^
/// Registration of the document: by 23 July (Friday) /// /// Distribution of the document: by 26 July (Monday) /// /// Use the ftp site (or e-mail reflector) for distribution ///
1) When you are going to submit a document, please notify S. Okubo as soon as possible, by 23 July (Friday) at the latest. Document number (APC-1nnn) will be allocated. Early indication of your submission plan is welcome and encouraged.
Note - Prefix "APC" comes from Atm (Q.12/16), Packet based (Q.13/16) and Common protocols (Q.14/16) based on the coordination with Q.1 ("Q1City"), Q.3 ("T120"), Q.11 ("Q11"), Q.15 ("Q15") groups.
2) You are advised to include a header as follows:
------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document APC-{1nnn}| | Study Group 16 {Version m if relevant}| | Q.12-14/16 Rapporteur Meeting {Date}| | Berlin, 2-6 August 1999 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------
3) All the contributors are requested to distribute their documents as early as possible, at least 7 calendar days in advance of the meeting (26 July or before) by posting them at either of the following:
- PictureTel ftp site (please advise S. Okubo of your posting)
Site: standard.pictel.com/avc-site Login name: anonymous Directory: Incoming
- Q.12-14/16 experts reflector
e-mail address: itu-sg16@mailbag.jf.intel.com
Please avoid the use of reflector when your document is voluminous.
4) Input documents can be retrieved from /9908_Ber directory of the ftp site.
5) Please bring 80 copies of your document to Berlin if it should be in hardcopy. Your cooperation is needed to start the meeting with all the documents at hand; please note that the copying capacity at the meeting site is very limited and expensive.
6) The document distribution / presentation at the meeting will be electronic (i.e. participants must bring their laptops along).
5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^
Please see the invitation distributed by the meeting host (http://standard.pictel.com/ftp/avc-site/9908_Ber/Invitation.txt).
6. Registration ^^^^^^^^^^^^^^^
To confirm your meeting attendance, please reply directly to TELES using the registration form distributed by the host (http://standard.pictel.com/ftp/avc-site/9908_Ber/registration-form.doc) up to and including 1 July for early regsitration with a meeting fee of DEM 500,00. Please note that after this date, the registration fee becomes DEM 650,00.
In addition, please send a separate e-mail registration to Mr. Ott and copy the Rapporteurs on this e-mail. Please use the subject and message body format shown below.
To: jo@teles.de Cc: okubo@giti.or.jp, dskran@ascend.com, ggf@lucent.com, tom.geary@conexant.com, garysull@microsoft.com Subject: Berlin meeting registration NAME: COMPANY: EMAIL: ARRIVAL: DEPARTURE:
Please attach a *small* photograph of yourself as GIF or JPG format and send this to jo@teles.de attached to the registration mail.
7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^
Please directly contact GRAND HOTEL ESPLANADE BERLIN mentioning "ITU- Meeting" to obtain the special rate; DEM 280,00 -- approximately USD 150 -- per night including a breakfast buffet for a single/double room. You need to guarantee the room reservation with your credit card.
CUTOFF DATE for the special room rate is Thursday, 1 July 1999.
We are looking forward to meeting with you in Berlin.
Sincerely yours,
Sakae OKUBO Dale SKRAN Gary THOM
----------