- sg16-avd - lists.packetizer.com

[H.323 Mobility:] MD-105 uploaded
by Jaakko Sundquist 02 Aug '00

02 Aug '00

Hi folks, I have just uploaded MD-105 to URL: ftp://standard.pictel.com/avc-site/Incoming/Mobility-AHG/Md-105_UsageOfH225A nnexG.zip . The contribution includes a proposal for using the H.225 Annex G protocol in H.323 Annex H. A few comments about the contribution below: -Generally the H.225 Annex G protocol seems to fit to the needs of H.323 Annex H quite well. -Especially the procedures for locating the called User can easily be done by adopting the H.225 Annex G protocol. -Location updating procedures seem to be possible without any big changes to the protocol, but the authentication procedures probably require some additions and/or changes. -I have written the contribution with the assumption that the H.225 Annex G protocol can be used in interfaces: GK-VLF, VLF-HLF and HLF-AuF. This also includes the Inter-domain communications between VLFs and HLFs, although in some pictures I have used co-located BE/VLF and BE/HLF entities, just to show that at least this way the Inter-domain communications should be possible. -Also, after a bit of reconsideration, I think that we could leave the HLF-AuF interface out of the first version of the standard and assume that the AuF is always co-located with a HLF (at least from the point of view of the H.323 system). The interface is, however, described as using the H.225 Annex G protocol in this contribution. I'm sure that you have questions and comments, so shoot! ------------------------------------------------ Jaakko Sundquist * +358 50 3598281 * Audere est Facere! jaakko.sundquist(a)nokia.com * ------------------------------------------------ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: [H.323 Mobility:] Usage of H.225 Annex G in H.323 Annex H & a question about BEs
by Roy, Radhika R, ALCOO 01 Aug '00

01 Aug '00

Hi, FX: I like your approach that you have stated here in the email. With respect to the draft APC.xxx that you have proposed, I have few questions: 1. At present in H.323, there are mechanisms in place how the communications need to be made between the GKs or between the BEs or between the GK-BE and BE-GK when the user remain in one GK (or GK-BE) can communicate for resolving the information with another user located within another GK (or BE/GK). That is, the communication is made via the GK (or GK/BE) to locate another GK (or GK/BE) where is use is residing (for resolving information or placing a call). 2. The base H.323 spec and H.225.0 Annex G spec clearly provide those mechanisms as stated in item 1. However, your contribution appears to suggest that a GK (or BE) will use the VLF and HLF to locate another GK (or BE) where the user resides (currently). My assumption is that there can be HLF-to-HLF communications by-passing the GK-to-GK (or GK/BE-BE/GK) communications for resolving the information. It has been mentioned in my earlier emails that HLF-to-HLF communications is not an extension of H.323 protocol. Therefore, it appears to me that your contribution does not follow the model that have been suggested in items 1 and 2 per H.323 and Annex G. Am I missing anything? Best regards, Radhika R. Roy AT&T -----Original Message----- From: Francois-Xavier Derome [mailto:Francois-Xavier.Derome@ALCATEL.FR] Sent: Tuesday, August 01, 2000 5:44 AM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Re: [H.323 Mobility:] Usage of H.225 Annex G in H.323 Annex H & a question about BEs I tried to follow your discussion on annex G. Can we split the problem in 2 parts : - the mobility management - the call control Concerning the mobility management, I think we can define the rules we want and there should be no restriction from the current annex G limitation. Concerning the call management, we MUST follow the current annex G and that's what I wanted to make clear in my APC. I think one solution could be for the BE in the mobile domain to put in the routeinfo field a sendAccessRequest to let him resolve the new location with the HLF fx ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Request for APC number
by Sakae OKUBO 01 Aug '00

01 Aug '00

Dear Mr. Cordell and Mr. Gilman, In response to your requests, your contributions have been registered as follows: APC-1896 BT Use of the Generic Framework during Registration and other RAS Messaging APC-1897 BT Additional Data Types for GenericData APC-1898 BT Clarification on the Handling of Unknown conferenceGoals APC-1899 Lucent Technologies Fast Channel Open for H.245 Best regards, Sakae OKUBO *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

[Robustness] Draft and minutes from 7/27 meeting
by Terry L Anderson 01 Aug '00

01 Aug '00

I have uploaded: ftp://standard.pictel.com/avc-site/Incoming/Robustness-AHG/AnnexRdraft0727.… Which include: 1. changes from 7/27 meeting 2. a stab at specifying how to use GenericData rather than our existing fields 3. adding DDP stuff to Appendix R1. 4. misc other editing Well discuss these at our meeting on Thursday. Thursday: Aug 3 11:00 EDT (15:00 UT) for 2 hr Phone: 1 888 559 7255 (calling from US) Phone: 1 908 860 0000 (calling from outside US) code: 531480 Note this will be our last call before Portland as I will be on vacation from Aug 7 until the Portland meeting. After any changes suggested on 7/27 I will be uploading the draft as the contribution. Of course we will work on it at Portland. Minutes 7/27: Attending: Terry Anderson - Lucent Paul Jones - Cisco Sasha Ruditsky - Radvision Archana Nehru (and another?) - Trillium Issues: 1. Consider use of GenericData rather than current data fields. 2. clarify "closer to called party" in 8.1 and "closer to calling party" in 10.3. Suggestion was to use the call reference flag in CRV. 3. We discussed issue of reestablishing a multiplexed channel and the need to re-establish it with the same set of calls that the previous one had, making the list something that must be shared in Shared Repository. 4. we still needed a discussion of how to handle mixed method (a/b) for the two channels through a signal routing entity. 5. We discussed the desire to have a single keepalive apply to all connections between the same pair of entities and the problems of determining whether two channels were really between the same pair. Agreed to list the issues and consider further. -- ------------------------------------------------------------ Terry L Anderson mailto:tla@lucent.com Tel:908.582.7013 Fax:908.582.6729 Pager:800.759.8352 pin 1704572 1704572(a)skytel.com Lucent Technologies/ Voice Over IP Access Networks/ Applications Grp Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

1 0

Re: [H.323 Mobility:] Usage of H.225 Annex G in H.323 Annex H & a question about BEs
by Francois-Xavier Derome 01 Aug '00

01 Aug '00

I tried to follow your discussion on annex G. Can we split the problem in 2 parts : - the mobility management - the call control Concerning the mobility management, I think we can define the rules we want and there should be no restriction from the current annex G limitation. Concerning the call management, we MUST follow the current annex G and that's what I wanted to make clear in my APC. I think one solution could be for the BE in the mobile domain to put in the routeinfo field a sendAccessRequest to let him resolve the new location with the HLF fx ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Liaison statement from ETSI Tiphon
by Sakae OKUBO 01 Aug '00

01 Aug '00

Dear Mr. Euchner, >I would like to bring the following Liaison statement to your attention, >which ETSI Tiphon meeting produced last week. I'm sending this liaison >statement even though you might receive it again officially through the >ETSI secretariat. This has been numbered APC-1895 and uploaded to /0008_Por directory. Best regards, Sakae OKUBO *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Request for APC number
by Sakae OKUBO 31 Jul '00

31 Jul '00

Dear Mr. Derome, APC-1894 has been allocated to your contribution. >SOURCE*: ALCATEL >TITLE: Modification to H.323 annex H >__________________ > >Abstract: > >In order to allow a smoth migration from the current H.323 and the H.323 >with mobility support we propose to add the following requirement : > >The procedures should allow an H.323 terminal without mobility function >located in an H.323 domain without mobility function to reach a mobile >H.323 terminal. > >This contribution proposes to add this new requirement to the current >chapter 7 and some modification to the current text related to this new >requirement. Best regards, Sakae OKUBO *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

IP Telecom Services Workshop 2000: Call for Participation
by Gregory W. Bond 31 Jul '00

31 Jul '00

[Please accept our apologies for multiple copies of this call.] ------------- CALL FOR PARTICIPATION --------------- IP TELECOM SERVICES WORKSHOP 2000 (IPTS 2000) co-located with Fall 2000 Voice on the Net (VON) organized by AT&T Labs Research pulver.com Cobb Galleria, Atlanta, Georgia, U.S.A September 11, 2000 http://www.research.att.com/conf/ipts2000/ ----------------------------------------------------------- IPTS 2000 is a new workshop dedicated to the important, emerging field of IP Telecom Services research. In contrast to the services available on the PSTN, a new world of telecom services is possible on an IP-based infrastructure. This world presents new challenges for service development, deployment and management. This one-day workshop will serve as a forum for the dissemination of research relating to these challenges. We have put together an excellent technical program that includes 8 original research papers, a plenary talk, and a round table discussion. We look forward to the participation from you and your colleagues in the telecom industry and the research community. TECHNICAL PROGRAM Plenary Talk - speaker to be announced DFC as the basis for ECLIPSE, an IP communications software platform Greg Bond, Eric Cheung, Andrew Forrest, Michael Jackson, Hal Purdy, Chris Ramming, and Pamela Zave AT&T Labs Research Experimenting with PARLAY in a SIP Environment: Early Results Stephane Desrochers, Roch H. Glitho, Kindy Sylla Ericsson Research Canada Approach For Services in Converged Networks Sanjiv Kapur, Rakesh Vij Hughes Software Systems Unified Messaging using SIP and RTSP Kundan Singh and Henning Schulzrinne Columbia University SPHINX: A Study in Convergent Telephony Kumar V. Vemuri Lucent Technologies SPHINX: Advanced Scenarios for H.323-SIP Interoperation Kumar V. Vemuri Lucent Technologies Where Should Services Reside in Internet Telephony Systems? Xiaotao Wu and Henning Schulzrinne Columbia University A Transformation Approach for Service Creation in a Hybrid IP-IN Network Cyril Carrez, Elie Najm, Alexandre Tauveron Ecole Nationale Superieure des Telecom Roundtable Discussion - topic to be announced CONFERENCE VENUE AND RELATED EVENTS IPTS 2000 will be held on September 11, 2000 in Atlanta, Georgia. The workshop will be co-located with Fall 2000 Voice on the Net (VON). Registration details about Fall 2000 VON can be found at http://pulver.com. IPTS 2000 is organized by AT&T Labs Research (http://www.research.att.com) and pulver.com (http://pulver.com). WORKSHOP CO-CHAIRS Greg Bond, AT&T Labs Research Eric Cheung, AT&T Labs Research PROGRAM COMMITTEE Mauricio Arango, Sun Microsystems Labs Joanne Atlee, University of Waterloo Ralph Blumenthal, Daewoo Telecom Scott Hoffpauir, BroadSoft Evan Magill, University of Strathclyde Peter Mataga, dynamicsoft Bernie Pagurek, Carleton University Jonathan Rosenberg, dynamicsoft Henning Schulzrinne, Columbia University Greg Utas, Nortel Networks Pamela Zave, AT&T Labs Research FURTHER GENERAL INFORMATION http://www.research.att.com/conf/ipts2000 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: Notice of the Portland meeting in August 2000
by Meyer, Greg W 31 Jul '00

31 Jul '00

Q.11-14/16 Experts: This is the last week to register for the Portland meeting before the block of hotel rooms is released on August 7th. Please see the links below to download the PortlandInfoPack.zip file. Fill out the form on the last page of the document and fax it to Intel Meeting Services. Please contact me if you have any questions. Thank you, Greg Meyer Intel Corportation +1.503.264.9506 mailto:greg.w.meyer@intel.com -----Original Message----- From: Sakae OKUBO [mailto:okubo@GITI.WASEDA.AC.JP] Sent: Sunday, July 02, 2000 11:54 PM To: ITU-SG16(a)MAILBAG.INTEL.COM Subject: Notice of the Portland meeting in August 2000 Dear Q12-14/16 experts, Please find attached the notice of the Portland meeting during 21-25 August 2000 as well as the logistic information from the host, Intel. The two files are also placed at the PictureTel ftp site: http://standard.pictel.com/ftp/avc-site/0008_Por/Notice_ITU-T_Portland.txt http://standard.pictel.com/ftp/avc-site/0008_Por/PortlandInfoPack.zip Please note that you are required to send your participation registration and hotel room reservation by 7 August 2000. Best regards, Sakae OKUBO *********************************************************** Waseda Research Center Telecommunications Advancement Organization of Japan (TAO) 5th Floor, Nishi-Waseda Bldg. 1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan Tel: +81 3 5286 3830 (to be transferred) +81 3 3204 8194 (direct) Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** 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. G. Meyer, Intel 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 3204 8194 Fax: +81 3 5287 7287 E-mail: okubo(a)giti.or.jp Dale SKRAN Rapporteur for Q.13/16 in ITU-T SG16 Sonus Networks 4400 Route 9 South Suite 1000 Freehold, NJ 07748 USA Tel: +1 732 409 5107 Fax: +1 732 409 5172 E-mail: dskran(a)sonusnet.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(a)lucent.com ------------------------------------------------------------ Subject: Notice of Q.12-14/16 Rapporteur Meeting in Portland Date: 3 July 2000 ------------------------------------------------------------ Dear Q.12-14/16 experts, The subject meeting of ITU-T SG16 experts will be held in Portland, USA at the kind invitation of Intel Corporation. Please note that Q.11/16 and Q.15/16 will meet concurrently at the same place and have joint session(s) with Q.12-14/16. 1. Date ^^^^^^^ 21 (Monday) - 25 (Friday) August 2000 starting at 9:00 on the first day closing at 18:00 on the final day 2. Venue ^^^^^^^^ The Resort At The Mountain 68010 East Fairway Welches, OR 97067 Tel: +1-503-662-3101 (for messages) 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group meetings 2) Q.12/16 B-ISDN multimedia systems and terminals - 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 - Toward determination in November: * H.323 Annex H (User, Service, and Terminal Mobility in H.323) * H.323 Annex I (Packet based MM Telephony over Error Prone Channels) * H.450.10 (Call Offer Supplementary Services) * H.450.11 (Call Intrusion) * H.450.12 (Common Information Additional Network) * H.225.0 Annex G V2 (Inter-domain) * H.323 Annex R (Robustness) * H.323 Annex M.3 (DSS1 Tunneling) * H.323 Annex E V2 (UDP call signaling) - Progress work for: * H.323 Annex N (QoS) * H.323 Annex O (Internet protocols and technologies complementary to H.323) * Other new items that may arise 4) Q.14/16 Common protocols, MCUs and protocols for interworking with H.300-series terminals - Toward determination in November: * H.248 Annex L * H.248 Annex M * H.235 V8 - Progress work for: * H.246 Annex D * H.248 V2 * H.341 V2 * other new items that may arise (e.g., new packages for H.248) 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:59 UTC, 11 August /// /// Distribution of the document: by 23:59 UTC, 14 August /// /// 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:59 UTC, Friday 11 August at the latest. Document number (APC-nnnn) 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-{nnnn}| | Study Group 16 {Version m if relevant}| | Q.12-14/16 Rapporteur Meeting {Date}| | Portland, 21-25 August 2000 | | | | 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 (23:59 UTC, Monday 14 August 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(a)mailbag.intel.com Please avoid the use of reflector when your document is voluminous. 4) Input documents can be retrieved from /0008_Por directory of the ftp site. 5) The document distribution / presentation at the meeting will be all electronic. Participants must bring along their laptop, 10BASE-T card and cord, and optionally wireless LAN card (please follow the host's advice). 6) The copying service is very limited and expensive at the meeting site. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ Please see the attached document provided by the meeting host (http://standard.pictel.com/ftp/avc-site/0008_Por/PortlandInfoPack.zip). 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send the attached form to the meeting secretariat by 7 August 2000: Intel Meeting Service ATTN: Valerie Nester Fax: +1 480 554 7775 AND advise Rapporteurs of your attendance by e-mail: To: okubo(a)giti.or.jp, dskran(a)sonusnet.com, ggf(a)lucent.com, tom.geary(a)conexant.com, garysull(a)microsoft.com Subject: Portland meeting registration Name: Company: Arrival: Departure: 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ Please send the attached form to the meeting secretariat together with the meeting registration. Special package room rate is $149.18 (single or double occupancy) per night including breakfast, tax and gratuity. The block reservation is held until 7 August. We are looking forward to meeting with you in Portland. Sincerely yours, Sakae OKUBO Dale SKRAN Glen FREUNDLICH ---------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

[Robustness] Minutes of the 7/20 call
by Terry L Anderson 31 Jul '00

31 Jul '00

Attendence (correct me if I missed anyone): Terry Anderson - Lucent Maureen Stillman - Nokia Sasha Ruditsky - Radvision Archana Nehru (and another?) - Trillium We discussed the 7/11 draft and the following points were made: 10.1 Detecting Failure - KeepAlive - callIdentifier should be optional - for multiplexed channels, CRV should be set to 0 and callIdentifier omitted. - the need for keepAlive in Method B may be unclear 10.2 Transport Address and ... -the new fields are not needed in Alerting and Call Proceeding. 10.3 Sychnronizing State -section is not needed. 11.3.1.4 An old TCP Connection Closure - I may have missed a point in this section. If you raised an issue here, please bring it up again. ASN.1 changes - RecoveryCallSignalPoint should be SEQUENCE OF SEQUENCE [The current white draft of H.225.0v4 has only SEQUENCE of has SEQUENCE OF RecoveryCallSignalPoint in each message so I believe we do NOT need a change] [I also want to change the name to BackupCallSignalAddress to better match our text] 11.5 - we need a similar SDL for Method B. 12 Method B: State Recovery... - clarify lack of need for KeepAlives 12.3 - detecting failure for case where backup establishes connection to a neighbor that has not yet detected failure. I also changed all instances of "Fault Tolerant Repository" to "Shared Repository" "element" or "component" to "entity" "IE" or "element" when referring to a part of the ASN.1 structure to "field" to be consistent with the language H.323 and H.225 are trying to move to. I checked our changes in the white draft of H.225.0v4 and removed all our ASN.1 that has already been incorporated. I now show only changes that are still needed. I have not yet done the similar check with H.323v4. A new draft, addressing most of the above, is available at: ftp://standard.pictel.com/avc-site/Incoming/Robustness-AHG/AnnexRdraft0720.… We will continue our discussion at our future calls: Thursday: July 27, Aug 3 11:00 EDT (15:00 UT) for 2 hr Phone: 1 888 559 7255 (calling from US) Phone: 1 908 860 0000 (calling from outside US) code: 531480 -- ------------------------------------------------------------ Terry L Anderson mailto:tla@lucent.com Tel:908.582.7013 Fax:908.582.6729 Pager:800.759.8352 pin 1704572 1704572(a)skytel.com Lucent Technologies/ Voice Over IP Access Networks/ Applications Grp Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974 http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

4 7