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

I want to subscribe to your study group.
by ＠L?5=E 20 Jul '99

20 Jul '99

Hi. I'm Youngsin Lee at LGIC S/W Lab in Korea. I heard your H.323 study group from my fellow worker. Please inform me how I can subscribe to the study group. Thank you.

2 1

Uploaded Files
by Callaghan, Robert 20 Jul '99

20 Jul '99

The following documents have been uploaded to picturtel/incoming: APC-1583 APC-1585 APC-1586 APC-1587 APC-1588 ------------------------------------------------------------------ Robert Callaghan Siemens Business Communication Systems Tel: +1.561.997.3756 Fax: +1.561.997.3403 Email: Robert.Callaghan(a)ICN.Siemens.com ------------------------------------------------------------------

1 0

subscribe
by Burkert Frank 20 Jul '99

20 Jul '99

BEGIN:VCARD VERSION:2.1 N:Burkert;Frank;;; FN:Frank Burkert ORG:Siemens AG - ZT IK 2;ZT IK 2 TITLE:Project Engineer TEL;WORK;VOICE:+49 (89) 636 44199 TEL;HOME;VOICE:+49 (89) 30004117 TEL;WORK;FAX:+49 (89) 636 52393 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Building 10/ Room 445;Frank Burkert=0D=0ASiemens AG - ZT IK 2=0D=0ACorporat= e Technology=0D=0ANetworks and Multimedia Comm.=0D=0AOtto-Hahn-Ring 6;Muench= en;;81730;Germany LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Building 10/ Room 445=0D=0AFrank Burkert=0D=0ASiemens AG - ZT IK 2=0D=0ACorp= orate Technology=0D=0ANetworks and Multimedia Comm.=0D=0AOtto-Hahn-Ring 6= =0D=0AMuenchen, 81730=0D=0AGermany URL: URL: EMAIL;PREF;INTERNET:Frank.Burkert@mchp.siemens.de EMAIL;INTERNET:fburkert@lycosmail.com REV:19990625T122537Z END:VCARD

1 0

Contributions for the Berlin meeting
by Sakae OKUBO 20 Jul '99

20 Jul '99

Dear Q.12-14/16 experts, Attached please find an update of the list of contributions for the Berlin meeting. Please be reminded that the deadline of contribution submission is as follows: /// Registration of the document: by 23 July (Friday) /// /// Distribution of the document: by 26 July (Monday) /// Please also be reminded of the following note we confirmed at the Torino meeting in November 1998 (see APC-1485): "The meeting notes that contributors are requested to upload the documents on time, otherwise their proposals can legitimately be rejected on the ground that the group members lack reviewing time." Best regards, Sakae OKUBO (Mr.) *********************************************************** 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 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 L M Ericsson First draft of a H.246 Annex for text conversation and text telephony 1564 L M Ericsson H.224 Modified for text conversation 1565 (P Jones) T.35 (1999) country codes 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) 1567 L M Ericsson Generic Service ControlTransport 1568 Lucent and H.245 Generic Capabilities Definition and AT&T H.225 Packetization Specification for the North American Cellular/PCS TDMA Vocoders (ACELP and US1) 1569 BT and Tech- Editorial Clarifications to H.323 and the Know-Ware Implementer's Guide 1570 BT and Tech- Clarifications on Third-Party Pause Know-Ware 1571 Rapporteur for Q.12/16 (S Okubo) Status of Draft Amendment 7 to H.222.0|ISO/IEC 13818-1 -- Carriage of ISO/IEC 14496 (MPEG-4) content over H.222.0|ISO/IEC 13818-1 (MPEG-2) System streams 1572 Editor (K Sakai) Draft Implementor's Guide for H.321 V2 1573 Editor (S Okubo) Draft Implementor's Guide for H.310 V2 1574 SG16 Correspondence Representative to DAVIC (S Okubo) DAVIC work on TV Anytime and TV Anywhere systems 1575 Rapporteur for Q.19/16 (S Hayashi) H.245 Generic Capability Definition and H.225.0 Packetization Specification for G.729 1576 Japan Guideline for assigning the T.35 terminal provider codes in Japan 1577 Oki et al Proposed modifications to resolve the inconsistent ASN.1 syntaxes between T.38 Annex B and H.245 1578 Oki et al Proposed additional liasion to SG8 on T.38 Appnedix II 1579 Hitachi, Ltd. Prototype system of H.262 layered video transmission 1580 Nortel Networks Media Gateway control protocol architecture and requirements ------------------------------------------------------------------------

3 2

Output of your job "kdeng"
by Kate Deng 19 Jul '99

19 Jul '99

I have been trying to subscribe to SG16 since last Friday but have been rejected each time for the same reason as follow. Should I keep trying or am I not subscribing to SG16 correctly ? Please advise. Thanks. Kate Deng (Alcatel USA) ----- Begin Included Message ----- >From MAILER-DAEMON Mon Jul 19 08:58:56 1999 Date: Mon, 19 Jul 1999 06:59:36 -0700 From: "L-Soft list server at Intel Corporation (1.8c)" <LISTSERV(a)mailbag.cps.intel.com> Subject: Output of your job "kdeng" To: kdeng(a)ssd.usa.alcatel.com > subscribe itu-sg16 Sorry, the ITU-SG16 list has been locked since 99/07/15 11:15 by greg.w.meyer(a)INTEL.COM. Try again later and contact the list owner if the condition persists. Summary of resource utilization ------------------------------- CPU time: 0.000 sec Device I/O: 0 Overhead CPU: 0.002 sec Paging I/O: 0 CPU model: Pentium Pro (128M) ----- End Included Message -----

1 0

Presentation
by Paul Sijben 19 Jul '99

19 Jul '99

I have uploaded my presentation of last thursday at http://pages.hotbot.com/edu/sijben/images/megaco45.ppt Paul -- Paul Sijben Tel:+31 35 687 4774 Lucent Technologies Fax:+31 35 687 5954 Forward Looking Work mailto:sijben@lucent.com Huizen, The Netherlands http://voip.nl.lucent.com/sijben (internal)

1 0

Re: APC document numbers
by Mickey Nasiri (ETX) 19 Jul '99

19 Jul '99

Dear Mr. Okubo, Unfortunately Mr. Hellstrom can not attend the Berlin meeting. I will present his documents but the document number APC-1563 (First draft of a H.246 Annex for text conversation and text telephony) is not ready for presentation. Please cancel this document number. Best regards //Mickey Nasiri -- //Mickey Nasiri Ericsson Telecom AB Home Communications SE-126 25 STOCKHOLM Tel: +46-8-719 38 61 Mob: +46-70-319 38 61 email: mickey.nasiri(a)ericsson.com

1 0

APC Document Number
by Noriko Hosokawa 19 Jul '99

19 Jul '99

Dear Mr.Rex Coldren In responce to your request, APC-1581,1582 have been allocated to your contribution. APC-1581 > Source: Lucent Technologies and Nortel Networks > Title: H.323 v3 and H.225 v3 Support for Improved Alias Registrations APC-1582 > Source: Lucent Technologies > Title: H.323 v3 and H.225 v3 Endpoint Registration Clarifications Best regards, Sakae OKUBO (Mr.) *********************************************************** 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 Fax: +81 3 5287 7287 e-mail: okubo(a)giti.or.jp *********************************************************** Documents for Q.12-14/16 Rapporteur meeting in Berlin (2-6 August 1999) ------------------------------------------------------------------------ APC- Source Title ------------------------------------------------------------------------ 1555 ITU-T SG8 Recommendation T.38 Indications in Recommendation H.245 (TD1/WP2 of the SG16 Santiago meeting) 1556 ITU-T SG11 Support of IN services for H.323 and other IP Network based terminals (TD4/WP2 of the SG16 Santiago meeting) 1557 ITU-T SG9 Draft New Rec. J.Web "Distribution of Sound and Television Programmes over the Internet "Webcasting"" (TD22/WP2 of the SG16 Santiago meeting) 1558 ITU-T SG2 Routing of Multimedia Connections When Interworking with PSTN, ATM, and IP Networks (TD24/GEN of the SG16 Santiago meeting) 1559 SG16 WP2 Proposed Organisation going forward to new Study Period 1560 Editor (E Martinez) Annex-H (User and Service Mobility in H.323) Proposed Architecture 1561 Editor (G Hellstrom) H.323 Annex G Text Conversation and Text SET 1562 L M Ericsson H.gcp Modification proposals for Text Conversation 1563 L M Ericsson First draft of a H.246 Annex for text conversation and text telephony 1564 L M Ericsson H.224 Modified for text conversation 1565 (P Jones) T.35 (1999) country codes 1566 Editor H.243 Draft revised ITU-T Recommendation H.243 (white doc.) 1567 L M Ericsson Generic Service ControlTransport 1568 Lucent and H.245 Generic Capabilities Definition and AT&T H.225 Packetization Specification for the North American Cellular/PCS TDMA Vocoders (ACELP and US1) 1569 BT and Tech- Editorial Clarifications to H.323 and the Know-Ware Implementer's Guide 1570 BT and Tech- Clarifications on Third-Party Pause Know-Ware 1571 Rapporteur for Q.12/16 (S Okubo) Status of Draft Amendment 7 to H.222.0|ISO/IEC 13818-1 -- Carriage of ISO/IEC 14496 (MPEG-4) content over H.222.0|ISO/IEC 13818-1 (MPEG-2) System streams 1572 Editor (K Sakai) Draft Implementor's Guide for H.321 V2 1573 Editor (S Okubo) Draft Implementor's Guide for H.310 V2 1574 SG16 Correspondence Representative to DAVIC (S Okubo) DAVIC work on TV Anytime and TV Anywhere systems 1575 Rapporteur for Q.19/16 (S Hayashi) H.245 Generic Capability Definition and H.225.0 Packetization Specification for G.729 1576 Japan Guideline for assigning the T.35 terminal provider codes in Japan 1577 Oki et al Proposed modifications to resolve the inconsistent ASN.1 syntaxes between T.38 Annex B and H.245 1578 Oki et al Proposed additional liasion to SG8 on T.38 Appnedix II 1579 Hitachi, Ltd. Prototype system of H.262 layered video transmission 1580 Nortel Networks Media Gateway control protocol architecture and requirements 1581 Lucent Technologies and Nortel Networks H.323 v3 and H.225 v3 Support for Improved Alias Registrations 1582 Lucent Technologies H.323 v3 and H.225 v3 Endpoint Registration Clarifications ------------------------------------------------------------------------

1 0

ITU-SG16 Mail List Re-enabled
by Meyer, Greg W 15 Jul '99

15 Jul '99

Hi All: I have re-enabled the ITU-SG16 mail list for public postings. I turned off public postings temporarily due to a message looping condition Monday night (US west coast time). I considered keeping the list "private" where postings are open only to those subscribed to the list (there's an open subscription policy). But it turns out there's a problem with embedded mail lists where individuals who are on a company mail list that is on the ITU-SG16 mail list. Those individuals would not be able to post to the ITU-SG16 mail list if it were kept "private." I will see if any other measures can be taken to reduce the exposure to mail loops. Thanks for your patients. Greg Meyer Intel Corporation mailto:greg.w.meyer@intel.com +1.503.264.9506

1 0

Summary of Megaco Meeting Results
by Tom-PT Taylor 15 Jul '99

15 Jul '99

This is a report on what has happened here in Oslo from the syntax design team meeting Tuesday morning through the full working group meeting this morning. The activities of later Tuesday and Wednesday were controversial, so I am documenting them fairly extensively. Syntax Design Team Meeting The Tuesday morning syntax design team meeting had a number of proposals to consider. We achieved two quick conclusions: not to consider ODL as our syntax specification language, and to split the Audit command into two separate commands, one to discover capabilities, the other to determine existing status. With regard to the ODL contribution, I would like to take note of the hard work which M. Anquetil and his colleagues put into devising complete Megaco syntax specifications not only in ODL but also in ASN.1. >From this beginning we went on to consider a key issue: capability specification syntax, with the Ott and Huitema drafts as our prime source material. We found that the proposal by Ott et al provided one advance on SDP: the ability to include quantitative constraints. Matt Holdrege also pointed out that Tag-Length-Value syntax in the Ott proposal as taken up in the syntax draft by Rosen et al offered the advantage that it would be simple for service providers to modify values in the MG's capability database, the way they modify values for RADIUS. Christian Huitema and Joerg Ott more or less agreed that their respective approaches were equivalent with respect to the expression of mutually exclusive alternatives. At the point where we began to be very interested in the proposal by Ott et al, we realized that, given that it was meant to be a substitute for SDP, our development of it would be an infringement on the mandate of MMUSIC. We ended up concluding that the constraints of the situation required us instead to specify that the MGC MUST in the short term support two different systems for media description and media capabilities: one based on SDP and one to be specified by SG 16 and presumably kinder to H.245. The choice of which system to use would be up to the MG and could be audited as an MG capability. We would reserve room for evolution to a new capability description protocol if one should be produced by MMUSIC. As part of this discussion, we considered the general question of Megaco syntax and whether it should be the Tag-Length-Value system proposed by Rosen et al (which, it was noted, is actually X.409 encoding reinvented). We were unable to come to a consensus on this topic. The meeting ended, as you might expect, with a cry of despair from Brian Rosen. Follow-Up Meeting Another meeting was hastily organized, to take place Tuesday night. It was organized after the first meeting had broken up and was announced by a note on the bulletin board, which meant that word did not reach all members of the design team in time for them to change their plans for the evening. Most but not all of the twenty-odd people in the morning meeting also attended the one in the evening. The evening meeting spent most of its time on the text vs. binary encoding issue in all its variants. The clear consensus of those present was that there were two irreconciliable camps: the IETF consensus would be in favour of text, the SG 16 consensus in favour of binary, regardless of benchmark results. This meant that we had an impasse. The suggestion was made that we toss a coin. This seemed to be the only credible way out of the impasse, so I did so. The "text encoding" side came up. The meeting broke up immediately following this result. Derivation Of EBNF On Wednesday Brian Rosen and Glen Freundlich, acting in place of Bryan Hill, started the work of implementing EBNF syntax descriptions in line with the conclusions of the previous day. They had help from a number of individuals along the way, but this was in effect an editorial exercise starting from the EBNF in draft-ietf-megaco-protocol-01.txt and the parameters shown in the H.GCP draft rather than any sort of design team meeting. The results as presented in this morning's working group meeting were fairly complete. Working Group Meeting As per the previously published agenda, slightly rearranged, the meeting covered three topics: syntax, transport, and packages. Discussion of work plan fell off the end. The syntax discussion began with my presentation of the design team results. Here is my summary as presented to the working group meeting: * Agreed: split Audit into two commands * status discovery * capability discovery * Stymied: new media description and media capability syntax may infringe on MMUSIC (and maybe CONNEG) charters. Hence to be equally fair to SIP and H.323: * MGC must support both SDP and SG 16-determined encoding of H.245 * MG may support either * reserve possibility of migration to new syntax. * Political impasse on encoding. Decided for text by flipping a coin. Issue is relative value of development speed vs. performance. The final point on encoding is problematic, in that the conclusion was reached by a group that was convened without, some will maintain, adequate notice. I hope that I did not improperly influence the working group by presenting this point with the same authority as the earlier points. In any event, the working group appeared to be pleased with the outcome. This ends the controversial part of this summary of results. The rest will be presented more briefly, pending Matt Holdrege's drafting of the minutes. Syntax: discussed use of the application-level Authentication Header and concluded that it would remain an option for use when IPSEC is unavailable. The use of SDP and of other protocols for media description and media capability description will be documented in separate RFCs, one per protocol. Transport: determined a consensus in favour of mandatory support of both TCP and application layer framing in the MGC, with the choice being determined by the MG when it initiates an association. Packages: an editorial team (Mike Kallas and Christian Huitema) was appointed to draft IANA considerations for adding new packages. Package descriptions include termination properties as well as events and signals. One RFC, normatively referenced from the base protocol document, will document the basic Megaco starter set of packages; others can be added through IANA according to the documented procedures. Study Group 16 can also generate package descriptions, probably by adding them as annexes to H.248 (AKA H.GCP). I spoke in the meeting of going to working group and possibly IETF last call in September, before the ITU commits H.248 to ballot. Less optimistic individuals have suggested a joint Megaco/Q.14/16 meeting on the east coast of North America, the week of Sept. 13. Discussions on this point are welcome. Tom Taylor Advisor -- IPConnect Standards E-mail: taylor(a)nortelnetworks.com (internally, Tom-PT Taylor) Phone and FAX: +1 613 736 0961

1 0