November 1999 - sg16-avd - lists.packetizer.com

Re: Problem in Connect Message in H.2250 V3
by Guntram Diehl 18 Nov '99

18 Nov '99

Hi, I would say the table does not indicate a order of the IEs. The order of the IEs within the message is determined by the code value. Guntram > -----Original Message----- > From: Aseem Agarwal [mailto:aseem@trillium.com] > Sent: Wednesday, November 17, 1999 11:44 PM > To: h323implementors(a)imtc.org > Cc: ITU-SG16(a)mailbag.cps.intel.com > Subject: Problem in Connect Message in H.2250 V3 > > > Hi All > > There is a problem in the additions made to Q.931 part of Connect > message in H.2250V3. Two new IEs have been added AFTER > User-to-User IE. > > The IE codes for the new IEs added are: > Connected Number : 0x4c > Connected Subaddress: 0x4d > > The IE code for User-to-User is 0x7e > > According to Q.931 coding Rules [section: 4.5.1], the IEs in > a message > should be in ascending order of their respective code > values. These two > IEs should be added after Date/Time IE. > > Comments ? > > aseem(a)trillium.com > -------------------------------------------------------------- > ----------- > for list subscription instructions, > send email to h323implementors-request(a)imtc.org with text "info" > >

1 0

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 17 Nov '99

17 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