October 2000 - sg16-avd - lists.packetizer.com

Uploaded Contributions
by CHATRAS Bruno FTRD/DAC/ISS 30 Oct '00

30 Oct '00

The following contributions: APC-2020 France Telecom Support of a direction indication in the generic announcement package APC-2021 France Telecom Proposed package for data transmission over analog lines have been uploaded to: ftp://standard.pictel.com/avc-site/Incoming/ Mr Okubo could you please move them to the 0011_Gen directory. Best Regards. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: APC-number request
by Sakae OKUBO 30 Oct '00

30 Oct '00

Dear Mr. Suzuki, Mr. Sundquist, Mr. Li, Mr. Chatras, The following APC numbers have been allocated to your contributions: APC-2016 NTT DoCoMo Support of HTTP in H.324 APC-2017 Nokia Comparison of 3GPP All IP and H.323 Annex H architectures APC-2018 UCLA, Samsung Draft text for "Generic Uneven Level Protection (ULP)" for Annex I of H.323 APC-2019 UCLA, Samsung Proposals for H.323 Annex I APC-2020 France Telecom Support of a direction indication in the generic announcement package APC-2021 France Telecom Proposed package for data transmission over analog lines 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: APC Number Request
by Sakae OKUBO 30 Oct '00

30 Oct '00

Dear Mr. Sang-gil Kim, The following APC numbers have been allocated to your contributions: APC-2014 >Source: Korea Telecom >Title: Comment to H.323 Annex K APC-2015 >Source: Korea Telecom >Title: A Procedure for Multimedia Mail Service 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

[H.323 Mobility:] MD-110 uploaded (new messages to H.225 Annex G)
by Jaakko Sundquist 30 Oct '00

30 Oct '00

Mr. Fortinsky et al, I have uploaded MD-110 containing a contribution on adding new, authentication related messages to the H.225 Annex G protocol, to the URL: ftp://standard.pictel.com/avc-site/Incoming/Mobility-AHG/MD-110_AdditionOfMe ssagesToH225AnnexG.zip . I will send the contribution also to the two meetings in Geneva, but if you send comments really quickly (tomorrow) to me, I may be able to make some changes to the contribution, before distributing it. ------------------------------------------------ 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: APC-number request
by Jaakko Sundquist 30 Oct '00

30 Oct '00

Hi again, I forgot one APC-number: "Comparison of 3GPP All IP and H.323 Annex H architectures" - as a Nokia contribution. I hope, I'm still on time... thanks in advance anyway. -Jaakko Sundquist > -----Original Message----- > From: EXT Sakae OKUBO [mailto:okubo@giti.waseda.ac.jp] > Sent: 29. October 2000 18:21 > To: jaakko.sundquist(a)nokia.com > Cc: Q.12-14/16 Reflector; wg5-3 TTC > Subject: Re: APC-number request > > > Dear Mr. Sundquist > > APC numbers have been allocated as follows: > > >Could you allocate APC-numbers for me for the following > contributions: > > APC-2011 > >"H.323 Annex H Draft" - as the editor contribution > > APC-2012 > >"New messages to the H.225 Annex G protocol" - as a Nokia > contribution > > APC-2013 > >"Changes to the H.323 Annex H" - as a Nokia contribution. > > 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

Questions on SDL keys used in H.245
by Lin Liu 30 Oct '00

30 Oct '00

Dear experts, I am a PhD student working in the area of modelling and analysis of communication protocols with formal methods. Currently I am looking at the H.245 recommendation. I have got a trivial question about the SDL keys used in H.245 (published in 05/99). In Figure C.1/H.245 -SDL key, "signal from protocol user" (the one with double vertical lines at the right side) and "local signal received" (the one with single vertical line) are defined as different SDL keys. But in the SDL specifications of some H.245 procedures, it seems that these two keys (as well as "signal to protocol user" and "local signal sent") are used undistinguishably. For example, in Figure C.9/H245 - Incoming CESE SDL, "local signal received" key is used for primitive "TRANSFER.response", which expected by me to be reprensentated as key "signal from protocol user" because it IS the primitive issued by the CESE user. There are some other simliar situations in this and other figures as well. I feel confused with these, is there anything inside the protocol which I have not got yet or is it the problem with misusing the SDL keys ? Could anybody interested in this can give me some hints ? Looking forward to your reply. Thanks a lot. Lin Liu ================ PhD student School of Electrical and Information Engineering University of South Australia The Mawson Lakes Campus, SA 5095, Australia ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Contributions Uploaded
by Christian Groves 30 Oct '00

30 Oct '00

Hello, Contributions: APC-1997 Editor (C Groves) Draft H.248 Implementors' Guide APC-1998 Editor (C Groves) Draft H.248 Annex K - Generic Announcement Package APC-1999 Editor (A Heidermark) Draft H.248 Annex L - Error Code and Service Change Reason Description APC-2000 Ericsson H.248 Annex x - Load Control Package APC-2001 Ericsson Direction in H.248 annex K APC-2002 Ericsson Signal on Root for H248v2 Have been uploaded to : ftp://standard.pictel.com/avc-site/Incoming/ Mr. Okubo could you please move these to the //standard.pictel.com/avc-site/0011_Gen directory? Regards, Christian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

APC-number request
by Jaakko Sundquist 29 Oct '00

29 Oct '00

Mr. Okubo, Could you allocate APC-numbers for me for the following contributions: "H.323 Annex H Draft" - as the editor contribution "New messages to the H.225 Annex G protocol" - as a Nokia contribution "Changes to the H.323 Annex H" - as a Nokia contribution. Thanks in advance. ------------------------------------------------ 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

2 1

List of APC documents
by Sakae OKUBO 29 Oct '00

29 Oct '00

Dear Q12-14/16 experts, Thsi is to remind you of the following deadlines for the input contributions to the Q12-14/16 Rapporteur meeting on 9-10 November: /// Registration of the document: by 23:59 UTC, 30 October /// /// Distribution of the document: by 23:59 UTC, 2 November /// /// Use the ftp site (or e-mail reflector) for distribution /// Please find attached a current list of registered documents. Its Word file is available as: http://standard.pictel.com/ftp/avc-site/0011_Gen/0011_Gen.doc 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 *********************************************************** Documents of the Q.12-14/16 Geneva meeting (9-10 November 2000) APC-1950 SG11 (Q.BIC/11) Liaison To SG 12, SG 13 And SG 16 Asking For Guidance On Quality Of Services to be Supported with the BICC Protocol APC-1951 Study Group 11 BICC Special Rapporteurs Liaison to SG 16 proposing some additional clarifications in the H.323 Implementers Guide for H.246 Annex C. APC-1952 SG 11 Joint Special Rapporteurs for BICC Support of directionality in "H.248 Annex K - Announcement Package" APC-1953 Accord Networks Support bi directional channels in annex C fast start APC-1954 Lucent Technologies, NTT DoCoMo H.324 Annex C multimedia call package for H.248 APC-1955 NTT DoCoMo, NEC Identification of references to IETF Documents in H.225.0 version 4 (per Recommendation A.5) APC-1956 Oki Electric Adding ServiceControl fields to LCF/LRJ APC-1957 Editor (P Jones) H.323 Implementor's Guide APC-1958 Editor (P Jones) H.323 v4 APC-1959 Editor (O Levin) H.323 Annex O Draft APC-1960 Lucent Technologies Proposal to create an SDL representation of H.248 APC-1961 Editor (M Euchner) Resolution of an inconsistency in Draft H.235 Version 2 regarding Section B.4.3 APC-1962 Editor (M Euchner) Resolution of an inconsistency in Draft H.235 Version 2 regarding the use of the password and shared secret APC-1963 Editor (M Euchner) Clarification on the use of sendersID and generalID in white Draft H.235 Version 2 APC-1964 Editor (M Euchner) REVISED ITU-T RECOMMENDATION H.235 VERSION 2 - SECURITY AND ENCRYPTION FOR H-SERIES (H.323 AND OTHER H.245-BASED) MULTIMEDIA TERMINALS - CORRECTED VERSION FOR DECISION APC-1965 Editor (M Euchner) Draft H.235 Version 3 - Security and encryption for H-Series (H.323 and other H.245-based) multimedia terminals APC-1966 Editor (M Euchner) Draft H.235v3 Annex F: "Hybrid Security Profile" APC-1967 Editor (M Euchner) Draft H.235v3 Annex G: "Security for H.323 Annex H in H.323 Mobile Environments" APC-1968 Editor (T Anderson) Draft H323 Annex R APC-1969 Editor (P Jones) Editorial and Technical Corrections to H.323v4 APC-1970 Cisco Systems Signalling of ingress and egress Carrier/Circuit Identifier information in H.225.0 Messages and Annex G Messages APC-1971 Cisco Systems Third Party Re-routing of a Fast Connect Initiated Call APC-1972 Cisco Systems Ported Number Indications in H.225.0 messages APC-1973 Cisco Systems Reserving Resources for Calls APC-1974 Editor (R Callaghan) H.450.12 - Common Information Additional Network Feature for H.323 APC-1975 Editor (R Callaghan) H.323 Annex M.3 - Tunneling DSS1 in H.323 APC-1976 Siemens H.323 Annex M.3 - Tunneling DSS1 in H.323 - Architecture APC-1977 Siemens Deficiencies of H.225.0 for a native transport of DSS1 APC-1978 AT&T Mobility Architecture and Protocol: H.323 Application Specific and Generic Value Added Services APC-1979 AT&T Application Layer QOS Signalling Architecture and Protocol: H.323 Application Specific and Generic Value Added Services APC-1980 AT&T Common Value Added Intelligent Backend Services (BES) Protocols for all Applications APC-1981 Editor (K Klaghofer) Editorial comments to H.450.9 White document (COM16-117E) APC-1982 Editor (K Klaghofer) H.450.10 Call Offer Supplementary Service for H.323 APC-1983 Editor (K Klaghofer) H.450.11 Call Intrusion Supplementary Service for H.323 APC-1984 Editor (M Fortinsky) H.225.0 Annex G version 2 APC-1985 VocalTec Communications H.225.0 Annex G Profile Negotiation APC-1986 VocalTec Communications Clarifications Related to H.225.0 Annex G Service ID's APC-1987 Editor (F Audet) H.323 Annex M.1 - QSIG tunnelling APC-1988 PictureTel RTP Payload Types in H.245 APC-1989 PictureTel Proposed New H.245 messages for H.263++ Annex U and Annex W.6.3.12 APC-1990 Comverse Network Systems H.225.0 Annex G v2: support for Service Zone APC-1991 Comverse Network Systems H.225.0 v4: Enhancing SupportedProtocols to indicate video APC-1992 Siemens {to be advised} APC-1993 Siemens {to be advised} APC-1994 Siemens {to be advised} APC-1995 Lucent Technologies Issues for H.248 implementors' guide APC-1996 Nortel Networks Proposed corrections to H.323v4 Annex D on T.38 fax switchover APC-1997 Editor (C Groves) Draft H.248 Implementors' Guide APC-1998 Editor (C Groves) Draft H.248 Annex K - Generic Announcement Package APC-1999 Editor (C Groves) Draft H.248 Annex L - Error Code and Service Change Reason Description APC-2000 Ericsson H.248 Annex x - Load Control Package APC-2001 Ericsson Direction in H.248 annex K APC-2002 Ericsson Signal on Root for H248v2 APC-2003 France Telecom Mobility management protocol in H.323 Annex H APC-2004 Editor (M Buckley) Latest Draft of Annex N of H.323 APC-2005 Lucent Technologies Transport QoS Parameters and Traffic Descriptor for QoS Characterisation in H.323 systems APC-2006 Editor (M Buckley) Latest draft of TIPHON DTS05003 "End to End Quality of Service Control and Signalling in TIPHON Systems" APC-2007 Editor (A Heidermark) Editorial changes to Annex H to H.248 APC-2008 Editor (A Heidermark) Editorial changes to Annex I to H.248 APC-2009 LM Ericsson Use of Call Independent Signalling for Service Control APC-2010 Nortel Networks Use of inband tones in H.323 using special RTP payload types ---------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0

Re: MPEG-4 elementary streams in H.323
by Scott Bradner 28 Oct '00

28 Oct '00

As has been mentioned before in this thread the AVT working group is currently evaluating draft-ietf-avt-rtp-mpeg4-es-05.txt. The IESG received the following liaison statement from ISO/IEC JTC1/SC29/WG11 (MPEG). We (the Transport Area Directors) would like to hear from SG16 (or at least the people on this list and anyone else who cares to comment) if they have any comments on this liaison statement or advice to us about what we should do at this time. Allison Mankin & Scott Bradner ---------- INTERNATIONAL ORGANISATION FOR STANDARDISATION ORGANISATION INTERNATIONALE DE NORMALISATION ISO/IEC JTC1/SC29/WG11 CODING OF MOVING PICTURES AND AUDIO ISO/IEC JTC 1/SC 29/ WG 11 N3694 October 2000, La Baule Title: Liaison Statement to IETF on MPEG-4 on IP Source: WG11 Status: Approved WG11 has progressed in the development of a framework for the carriage of MPEG-4 content over IP networks, and we have included the recent version, N3718, for your information. WG11 understands that for the carriage of MPEG-4 elementary streams over IP networks, there is an Internet-Draft <draft-ietf-avt-rtp-mpeg4-es-05.txt> eligible for promotion to a standards track RFC. However, there is no consensus yet on the payload formats for the carriage of various MPEG-4 streams in WG11. For instance, there are still strong concerns that the payload format for MPEG-4 audio specified in <draft-ietf-avt-rtp-mpeg4-es-05.txt>, while adequate for a range of applications, is not appropriate for general use. That is, <draft-ietf-avt-rtp-mpeg4-es-05.txt> may not be used in the context of MPEG-4 over IP framework in the future. WG11 would prefer to find a design for a single RTP payload format that would suffice for the carriage of all MPEG-4 content over IP networks. Therefore, WG11 is concerned about promotion of <draft-ietf-avt-rtp-mpeg4-es-05.txt> to standards track RFC because of possible interoperability problems between different types of terminals using MPEG-4 content. WG11 recommends that IETF suspend promotion to standards track RFC of all IETF drafts related to the carriage of MPEG-4 content over IP networks and wait for WG11 to finalize its current work on a generic solution that includes framework and payload formats for the carriage of MPEG-4 content over IP networks. WG11 commits to the following schedule: Draft of framework at La Baule meeting Finalization of framework by December 1st, 2000 Finalization of generic payload format by December 1st, 2000 Finalization of video payload format by December 1st, 2000 Finalization of audio payload format by January 2001 Finalization of FlexMux payload format by January 2001 WG11 is aware that the ITU-T wishes to move forward with the adoption of an RTP payload specification for MPEG-4 Elementary Streams into the H.323 suite Recommendations. Therefore, in a companion liaison statement to ITU-T SG 16, WG11 has requested that ITU-T either delay the decision for the affected H.323 suite Recommendations or allow an interim revision without incurring a long delay such as two years. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv(a)mailbag.intel.com

1 0