August 2005 - sg16-avd - lists.packetizer.com

FW: socorro!
by simao.campos＠ITU.INT 31 Aug '05

31 Aug '05

Dear colleagues, can someone help this engineer from Brazil? I will translate his two questions: 1) When RRq fails in H.225.0 and there is a retransmission, requestSeqNum is repeated. His question is, what does he use as the timestamp? I presume it remains the same. 2) What happens with the timestamp when summer savings time (clock is adjusted one hour ahead or behind) starts? I presume if it changes outside a session, it is business as usual; if it changes in the middle of a session, then it should stick to the original one, and start +,- 1 hour for the next sessions open. Please copy any replies to him at: José Antonio Mechaileh jmechail(a)terra.com.br as he does not subscribe to this mailing list. Thanks! Simao _____ From: José Antonio Mechaileh [mailto:jmechail@terra.com.br] Sent: 30 August 2005 16:49 To: Campos, Simao Subject: socorro! Caro amigo Simão Socorro! I need help! Estou com uma dúvida a respeito de H.225 e não estou achando a resposta: quando um RRQ falha por algum motivo e ocorre uma retransmissão, o valor de "requestSeqNum" é repetido. Ver abaixo: "requestSeqNum in messages is used to keep track of multiple outstanding requests. Any associated response messages (success or failure) shall have the corresponding requestSeqNum returned with it. Retransmitted messages shall have the same requestSeqNum. RequestSeqNum increments by 1 modulo 65536." A dúvida é: o que acontece com o timestamp? Deve ser repetido também??? Ou ele sempre aumenta? Outra dúvida: o que acontece com o horário de verão? O relógio volta ou avança 1 hora. O que acontece com o Timestamp nessas situações? Muito obrigado pela ajuda! Um abraço Zé

1 0

FW: socorro!
by simao.campos＠itu.int 30 Aug '05

30 Aug '05

Dear colleagues, can someone help this engineer from Brazil? I will translate his two questions: 1) When RRq fails in H.225.0 and there is a retransmission, requestSeqNum is repeated. His question is, what does he use as the timestamp? I presume it remains the same. 2) What happens with the timestamp when summer savings time (clock is adjusted one hour ahead or behind) starts? I presume if it changes outside a session, it is business as usual; if it changes in the middle of a session, then it should stick to the original one, and start +,- 1 hour for the next sessions open. Please copy any replies to him at: José Antonio Mechaileh jmechail(a)terra.com.br as he does not subscribe to this mailing list. Thanks! Simao _____ From: José Antonio Mechaileh [mailto:jmechail@terra.com.br] Sent: 30 August 2005 16:49 To: Campos, Simao Subject: socorro! Caro amigo Simão Socorro! I need help! Estou com uma dúvida a respeito de H.225 e não estou achando a resposta: quando um RRQ falha por algum motivo e ocorre uma retransmissão, o valor de "requestSeqNum" é repetido. Ver abaixo: "requestSeqNum in messages is used to keep track of multiple outstanding requests. Any associated response messages (success or failure) shall have the corresponding requestSeqNum returned with it. Retransmitted messages shall have the same requestSeqNum. RequestSeqNum increments by 1 modulo 65536." A dúvida é: o que acontece com o timestamp? Deve ser repetido também??? Ou ele sempre aumenta? Outra dúvida: o que acontece com o horário de verão? O relógio volta ou avança 1 hora. O que acontece com o Timestamp nessas situações? Muito obrigado pela ajuda! Um abraço Zé

1 0

Request for posting
by OKUBO Sakae 16 Aug '05

16 Aug '05

Dear Rapporteurs and Editors, This is to request you to post the final texts for consent and approval at the avc-site for wider review. Please upload them at: ftp://ftp3.itu.int/avc-site/Incoming user: avguest password: Avguest or e-mail them to me. Then I will place them at the /0507_Gen directory. -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Last Call has started
by OKUBO Sakae 16 Aug '05

16 Aug '05

Dear experts, Please note that Last Call for the draft Recommendations consented at the closing plenary of SG16 on 5 August has just started with deadline of 12 September 2005. For further details, please visit: http://www.itu.int/ITU-T/studygroups/com16/aap/index.html -- Best regards, OKUBO Sakae, Co-Chair of WP2/16 e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Last Call has started
by OKUBO Sakae 16 Aug '05

16 Aug '05

Dear experts, Please note that Last Call for the draft Recommendations consented at the closing plenary of SG16 on 5 August has just started with deadline of 12 September 2005. For further details, please visit: http://www.itu.int/ITU-T/studygroups/com16/aap/index.html -- Best regards, OKUBO Sakae, Co-Chair of WP2/16 e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ******************************************************************

1 0

Outcome of the SG16 meeting (26 July - 5 August 2005)
by OKUBO Sakae 06 Aug '05

06 Aug '05

Dear experts, The subject SG16 meeting has concluded with consent and approval of the documents as listed after my signature. An interim Rapporteur meeting will be planned during 28 November - 2 December 2005 (place is yet to be decided). Please see the following meeting report for the detailed outcome: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/WP2_report_050805. zip ftp://ftp3.itu.int/avc-site/2005-2008/0507_Gen/WP2_report_050805.zip user: avguest password: Avguest -- Best regards, OKUBO Sakae e-mail: sokubo(a)waseda.jp Visiting Professor Graduate School of Science and Engineering Waseda University ****************************************************************** Waseda University, YRP Ichibankan 312 Tel: +81 46 847 5406 3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken Fax: +81 46 847 5413 239-0847 Japan H.323 videoconferencing: arranged by advice ****************************************************************** <Recommendations for Consent> Draft new Corrigendum 4 to H.222.0 | ISO/IEC 13818-1 "Information Technology - Generic Coding Of Moving Pictures And Associated Audio Information: Systems" Draft new H.221 Amendment 1 "Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices" Draft new H.230 Amendment 1 "Frame-synchronous control and indication signals for audiovisual systems" Draft revised H.239 Draft revised H.241 "Extended video procedures and control signals for H.300 series terminals" Draft new H.242 Amendment 1 "System for establishing communication between audiovisual terminals using digital channels up to 2 Mbit/s" Draft revised H.243 "Procedures for establishing communication between three or more audiovisual terminals using digital channels up to 1920 kbit/s" Draft revised H.324 "Terminal for low bit-rate multimedia communication" Draft revised H.245 "Control protocol for multimedia communication" Draft new H.246 Amendment 1 "Interworking of H-Series multimedia terminals with H-Series multimedia terminals and voice/voiceband terminals on GSTN and ISDN" Draft new H.460.17 "Tunneling RAS through H.225.0" Draft new H.460.20 "Location Number for H.323" Draft revised H.248.1 version 3 "Gateway Control Protocol" Draft Revision 1 of H.248.8 "Error Codes and Service Change Reasons" Draft new H.248.36 "Hanging Termination Detection Package" Draft new H.248.37 "IP NAPT Traversal Package" Draft new H.460.18 "Traversal of H.323 signalling across Firewalls and NATs" Draft new H.460.19 "Firewall and NAT traversal procedures for media in H.323 systems" Draft new F.741 (ex F.AvoD) "Service description and requirements for Audiovisual on Demand services" Draft new F.742 (ex F.DL) "Service description and requirements for distance learning services" Draft new F.733 (ex F.MMCIP) "Service description and requirements for multimedia conference services over IP networks" Draft new F.724 (ex F.VTIP) "Service description and requirements for videotelephony services over IP networks" Draft new Rec. H.235.0 "Security framework for H-series (H.323 and other H.245-based) multimedia systems" (for Consent) Draft new Rec. H.235.1 "Baseline Security Profile" (for Consent) Draft new Rec. H.235.2 "Signature Security Profile" (for Consent) Draft new Rec. H.235.3 "Hybrid Security Profile" (for Consent) Draft new Rec. H.235.4 "Direct and Selective Routed Call Security" (for Consent) Draft for new Rec. H.235.5 "Framework for secure authentication in RAS using weak shared secrets" (for Consent) Draft new Rec. H.235.6 "Voice encryption profile with native H.235/H.245 key management" (for Consent) Draft new Rec. H.235.7 "Usage of the MIKEY Key Management Protocol for the Secure Real Time Transport Protocol (SRTP) within H.235" (for Consent) Draft new Rec. H.235.8 "Key Exchange for SRTP using secure Signalling Channels" (for Consent) Draft new Rec. H.235.9 "Security Gateway Support for H.323" (for Consent) ========== <Documents for Approval> Draft revised Implementors' Guide for T.120-series Draft revised 3.7.3 H.323-Series Implementors$B%f(B Guide Draft revised H-Series Supplement 4 "Repository of generic parameters for ITU-T Recommendations H.460.x sub-series" Draft new Supplement 2 to the H-Series: H.248 Sub-Series: Packages Guide Release 7 Draft New Technical Paper "The Requirements for Network Address Translator and Firewall Traversal of H.323 Multimedia Systems" Draft New Technical Paper "Firewall and NAT traversal Problems in H.323 Systems" Draft new H.235 Version 3 (2003) Implementors$B%f(B Guide "Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals" (for Approval) Draft new Technical Paper on Usage of the H.510 protocol for the support of H.323 based Multimedia Services within GPRS/IMT2000 networks ==========

1 0