- sg16-avd - lists.packetizer.com

H.248.1 V3 Editorial Comments: § 7.1.11
by Albrecht.Schwarz＠alcatel.de 23 May '05

23 May '05

We have still an open item in § 7.1.11: [Editor's Note: There is a problem if a signal is specified with a direction that doesn't make sense or is impossible. This is an attempt at some text. Contributions for this are solicited.] Discussion: After some analysis this item may result (if at all) in a dedicated Error Code. Code #452 "No such signal in this package" is inappropriate. On the other side, there seems to be no real justification for a new codepoint. The next sentence ("error codepoint #501") seems to be applicable as well for the indicated situation. Proposal: Delete Editor's note. No further text changes proposed. Albrecht Schwarz ALCATEL

1 0

H.248.1 V3 Editorial Comments:
by Albrecht.Schwarz＠alcatel.de 23 May '05

23 May '05

A minor editorial comment to the examples in $ 6.3.4 and § 7.1.4: It's proposed to align to upper case for "Descriptor". Albrecht Schwarz ALCATEL 7.1.4: Media descriptor TerminationState Descriptor Stream descriptor LocalControl descriptor Local descriptor Remote descriptor Statistics descriptor

1 0

Meeting Announcement: H.248.1 Version 3 Online Editing Meeting
by Kevin Boyle 18 May '05

18 May '05

>From C Groves Rapporteur for Q.3/16 <christian.groves(a)ericsson.com> K Boyle II Editor of H.248.1 Version 3 <kboyle(a)nortel.com> ------------------------------------------------------------------- Subject: Notice of Online Editing Meeting for H.248.1 Version 3 Date: 23 May - 1 July 2005 ------------------------------------------------------------------- Dear Experts of Question 3/16, As agreed at the Melbourne meeting, a meeting for the purpose of editing H.248.1 Version 3 will be held via email over the course of several weeks. Details of the meeting are contained herein. 1. Date ^^^^^^^ 23rd (Monday) May - 1st (Friday) July 2005 Meeting will be conducted via email. The meeting will be considered to be convened at 0900 EDT on 23 May, and concluded at 1700 EDT on 1 July. 2. Venue ^^^^^^^^ The ITU-T SG16 mailing list: itu-sg16(a)external.cisco.com No pre-registration is necessary. 3. Topics ^^^^^^^^^ 1) Editing of H.248.1 Version 3 in preparation for the July/August SG16 meeting. 4. Documents ^^^^^^^^^^^^ 1) File format: The editor's documents will be in Word. 2) E-mail reflector E-mail address: itu-sg16(a)external.cisco.com To subscribe: Send e-mail to majordomo(a)cisco.com In the body of the message, put: subscribe itu-sg16 Please avoid the use of reflector when your document is voluminous. 3) Input documents can be retrieved from the H.248.1_Editing directory of the ftp site. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/ ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ 4) The document distribution / presentation at the meeting will be all electronic. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ 1) The editor will produce an input version of the document by 0900 EDT on May 16. 2) Each week, a portion of the document will be open for editorial comment. The schedule shall be as follows: 23 - 27 May -- Sections 1 - 7.1.14 30 May - 3 June -- Sections 7.1.15 - 14.4 6 - 10 June -- Annex A 6 - 17 June -- Annex B 20 - 24 June -- Annexes C, D, E, F, Appendices I, II, III 27 June - 1 July -- Cleanup Review 3) On Monday and Tuesday of each week, editorial comments may be posted to the list or emailed to the editor, copying the Rapporteur. The editor will compile all comments, and update the text on Wednesday. By 0900 EDT on Thursday each week, the editor will post updated text for the group's review. Thursday and Friday will be used for any further editorial commentary on the newly updated text. The editor will then finalize the text of the section. 4) By 0900 EDT on 27 June, the editor will post the resulting complete text from the editing of the previous weeks. The entire text will be open to further editorial comment on the same schedule as the previous weeks. 5) The resulting text will be the editor's input draft to the SG16 meeting in Geneva. 6) Note that *NO TECHNICAL CHANGES* will be accepted during this meeting. All proposed changes must be editorial. Technical changes to the proposed text must be proposed to the SG16 meeting in July/August per the normal contribution procedures. 7) For postings to the mailing list, please use the following subject line: "H.248.1 V3 Editorial Comments" 6. Registration ^^^^^^^^^^^^^^^ No registration is necessary, though subscription to the SG16 exploder is required. We are looking forward to a productive editing meeting. Sincerely yours, Kevin BOYLE II (Editor) Christian GROVES (Rapporteur) ----------

1 0

Question on T.38
by Francesco De Marco 09 May '05

09 May '05

Gentlemen, I'm writing for a question about T.38 and h245 requestMode. At par. D.5 of H.323 AnnexD, it is written: "either endpoint may detect fax tones (i.e. CNG or CED) or the presence of V.21 carrier and HDLC flags. Typical scenarios for facsimile call detection rely on the analysis of CNG calling tone and a response of the CED answer tone and/or the initiation of fax procedures using the V.21 carrier and HDLC flags. Note that in some implementations the presence of either CNG or CED are optional. Therefore, both endpoints should take an active role in order to properly detect fax." and "When using two unidirectional fax channels, the endpoint that detected the tone shall initiate the standard H.245 Mode Request procedure by sending a requestMode message to its remote counterpart" The question is: if both the endpoints detect the tone, both can send a requestMode and this can happen at the same time; in this case both will receive, other than send, a requestMode. How is solved this situation? Has one of them to accept the change and the other has to reject it, or both can accept the change? Is there a standard procedure to be applied in this case (based for example on the master-slave decision, or what else)? I know that one possible solution is to implement the application so that only the "receiving fax endpoint" (i.e. the one detecting the CED at his local analog interface) sends the requestMode, but this seems not being recomanded by AnnexD. Kind regards, Francesco

1 0

Contribution AVD-2737 uploaded
by Louis Fourie 09 May '05

09 May '05

Experts, I have uploaded Draft H.235.8 (AVD-2737) to the Incoming directory. - Louis Fourie Cisco Systems

1 0

Contribution AVD-2719 uploaded
by Patrick Luthi 09 May '05

09 May '05

Dear experts, I have just uploaded to the Incoming directory AVD-2719 "Proposed solution to support non-ASCII characters in H.320 and H.323 without causing MBE BAS code emulation" which is a joint contribution from Tandberg and Polycom. Best regards, Patrick Luthi _____________________________ Patrick Luthi Manager - Technical Standards Rapporteur (chairman) for the ITU-T multimedia systems, terminals and data-conferencing Experts group (Question 1/16) TANDBERG N-1366 Lysaker, Norway Phone: + 47 67 125 125 Direct: +41 21 801 8420 e-mail: patrick.luthi(a)tandberg.net

1 0

[SUSPECT ATTACHMENT] AVD 2732, 2733, 2734
by Sasha Ruditsky 08 May '05

08 May '05

Hi Attached are the AVDs 2732, 2733, and 2734 for the Biel-Bienne meeting (BTW I failed to contact ftp3.itu.int <ftp://ftp3.itu.int/> due to "500 Connection refused (Winsock error #10061)" Thanks, Sasha

1 0

Registration of documents for upcoming meeting
by Paul E. Jones 06 May '05

06 May '05

Folks, This is just a reminder that today is the deadline for registering documents for the upcoming meeting of various questions in WP2. I have uploaded the latest list of registered documents. You can see the list here: http://ftp3.itu.ch/av-arch/avc-site/2005-2008/0505_Bie/0505_Bie.html If you have intention of submitting a contribution, please let me know ASAP. Please review this list to make sure that I did not miss your document. Thanks, Paul

1 0

REMINDER: Meeting Announcement: Joint Rapporteur Meeting of Quest
by Euchner Martin 27 Apr '05

27 Apr '05

Dear all, This is a reminder for the joint Rapporteurs meeting in Biel-Bienne (CH) from 17th (Tuesday) May - 20 May (Friday) 2005. Here are some important dates: Registration of attendance - by May 9, to Aline Charmillot <aline.charmillot(a)bakom.admin.ch> Registration of the document: by 23:59 UTC, 7 May 2005, to Paul Jones <paulej(a)packetizer.com> Distribution of the document: by 23:59 UTC, 10 May 2005 Use the ftp site (or e-mail reflector) for distribution Note - Contributions after the above dates are dealt with as "late" and their consideration is up to the meeting. The meeting information is available at the following place: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/Biel_Invitation.do c Early indication of your submission plan is welcome and encouraged. With kind regards Martin Euchner. ----------------------------------------------------------------------- | Dipl.-Inf. Meeting organizer | Martin Euchner Phone: +49 89 722 55790 | Siemens AG.....................Fax : +49 89 722 62366 | COM GC PS 3 mailto:Martin.Euchner@siemens.com | mailto:martin.euchner@ties.itu.int | Hofmannstr. 51 Intranet: http://ietf.icn.siemens.de/sr3/Standardisation_Topics/security/ | D-81359 Muenchen Internet: http://www.siemens.de/ | __________________ | Germany ----------------------------------------------------------------------- -----Original Message----- From: Euchner Martin Sent: Dienstag, 5. April 2005 12:52 To: SG16 Cc: Pierre-Andre Probst; Paul Barrett; Yushi Naito; LAMBLIN Claude FTRD/DIH/LAN; Sebestyen Istvan; Campos, Simao; Paul E. Jones; Bob Gilman; bastien.lamer(a)rd.francetelecom.com; Euchner Martin; Leo Lehmann; 'patrick.luthi(a)tandberg.net' Subject: Meeting Announcement: Joint Rapporteur Meeting of Questions 2, 5, 21, 25 and 29/16 in Biel-Bienne/Switzerland Cc Mr. P-A. Probst, Chairman of SG16 <probst-pa(a)bluewin.ch> Mr. Paul Barrett, Vice Chairman of SG16 <paul.barrett(a)psytechnics.com> Mr. Yushi Naito, Vice Chairman of SG16 <naitoy(a)attglobal.net> Ms. Claude Lamblin, Vice Chairman of SG16 <claude.lamblin(a)rd.francetelecom.com> Mr. I Sebestyen, Vice Chairman of SG16 <Istvan.Sebestyen(a)siemens.com> Mr. S. Campos-Neto, ITU TSB <simao.campos(a)itu.int> P Luthi Rapporteur for Q.1/16 <patrick.luthi(a)tandberg.net> De P Jones Rapporteur for Q.2/16 <paulej(a)packetizer.com> R Gilman Rapporteur for Q.5/16 <rrg(a)avaya.com> B Lamer Rapporteur for Q.21/16 <bastien.lamer(a)rd.francetelecom.com> M Euchner Rapporteur for Q.25/16 <Martin.Euchner(a)siemens.com> L Lehmann Rapporteur for Q.29/16 <Leo.Lehmann(a)bakom.admin.ch> ------------------------------------------------------------------- Subject: Notice of Joint Rapporteur Meeting in Biel-Bienne/Switzerland Date: 17 May - 20 May 2005 ------------------------------------------------------------------- Dear Experts of Questions 2, 5, 21, 25 and 29/16, The subject meeting of ITU-T SG16 experts will be held in Biel-Bienne/Switzerland at the Federal Office of Communications (OFCOM). Details of the meeting are contained herein. Please note that Q.1/16 will meet concurrently and we will have joint or serial sessions with these Questions." 1. Date ^^^^^^^ 17th (Tuesday) May - 20 May (Friday) 2005 Meeting will start at 9:00 AM on the first day Closing around 18:00 on the final day 2. Venue ^^^^^^^^ Federal Office of Communications (OFCOM) Rue de l'Avenir 44/ Zukunftstrasse 44 CH2501 Biel-Bienne Switzerland http://www.bakom.ch/en/amt/kontaktadressen/index.html Please contact the reception of OFCOM in the morning of each meeting day to get access to the meeting room. 3. Topics (tentative) ^^^^^^^^^^^^^^^^^^^^^ 1) Review of the relevant group activities 2) Q.2/16 Real-Time Audio, Video, and Data Communication over Packet-Switched Networks - Coordinate with other SDOs, Questions, or Study Groups - Review items proposed for the H.323-series Implementers Guide - Progress work on the following work items * H.323 Annex Gv2 * H.323 Annex I * H.460.17 (RAS Tunneling) * H.460.geo * H.460.location * H.460.dhcp * H.460.gaam * H.460.presence - Discuss miscellaneous and new work items 3) Q.5/16 Control of NAT and Firewall Traversal for H.300-Series Multimedia Systems - Coordinate with other SDOs, Questions, or Study Groups - Progress work on H.proxy - Consider various solution proposals for NAT/FW traversal 4) Q.21/16 Multimedia Architecture - Progress work on * Multimedia Architecture and End to end Open Services Architectural Framework. * Analysis of relevant Architectures prepared by other bodies 5) Q.25/16 Multimedia Security in Next-Generation Networks - Progress work on * H.235.x V4 subseries, * H.FSIC, * H.460.spn, - Coordination, - Maintenance H.235, - Consider new material. 6) Q.29/16 Mobility for Multimedia Systems and Services - Follow up status of work items - Service Mobility for Multi Media Architecture 7) Interaction with other groups 8) Future work plan 4. Documents ^^^^^^^^^^^^ /// Registration of the document: by 23:59 UTC, 7 May 2005 /// /// Distribution of the document: by 23:59 UTC, 10 May 2005 /// /// Use the ftp site (or e-mail reflector) for distribution /// 1) When you are going to submit a document, please notify Paul Jones <paulej(a)packetizer.com>, document manager of this meeting, as soon as possible, by 23:59 UTC, Friday 7 May 2005 at the latest. Document number AVD-nnnn will be allocated. Early indication of your submission plan is welcome and encouraged. Note - Prefix "AVD" comes from Audio, Video and Data. 2) You are advised to include a header as follows: ------------------------------------------------------------------ | | | ITU Telecommunication Standardization Sector Document AVD-{nnnn}| | Study Group 16 {Version m if relevant}| | 1,2,5,21,25 and 29/16 Rapporteur Meeting {Date}| | Biel-Bienne May 17 - 20 May 2005 | | | | SOURCE*: { } | | TITLE : { } | | PURPOSE: {Proposal, Discussion, Information, Report, etc.} | | | | _________________________ | | | | | | | | *Contact: Name, e-mail | ------------------------------------------------------------------ Note: A template for the AVD document can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/AVD-template.doc> This may be modified and used for the purpose of document submission at this meeting. 3) File format: Use of Word, PDF, ASCII or HTML is recommended. 4) 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 9 May 2005 or before) by posting them at either of the following: - Uploading via FTP Site: ftp3.itu.int/ User ID: avguest Password: Avguest (Note the uppercase 'A') Directory: avc-site/Incoming - E-mail reflector E-mail address: itu-sg16(a)external.cisco.com To subscribe: Send e-mail to majordomo(a)cisco.com In the body of the message, put: subscribe itu-sg16 Please avoid the use of reflector when your document is voluminous. 5) Input documents can be retrieved from 0505_Bie directory of the ftp site once Mr. Jones has an opportunity to put them into place. The documents will also be available through the following URLs: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie ftp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/0505_Bie 6) The document distribution / presentation at the meeting will be all electronic. Participants must bring along a laptop, wireless lan card and/or Ethernet card, and Ethernet cable in order to access the documents. 5. Logistic information ^^^^^^^^^^^^^^^^^^^^^^^ The meeting will be hosted by the Federal Office of Communications (OFCOM) at the OFCOM premises in Biel-Bienne/Switzerland. The meeting invitation containing logistic information can be found at: <http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/Biel_Invitation.d oc> 6. Registration ^^^^^^^^^^^^^^^ To register your meeting attendance, please send the attached registration sheet via e-mail or fax to Aline Charmillot e-mail : aline.charmillot(a)bakom.admin.ch Fax : +41 32 327 55 28 providing the family name, given name, company name, and e-mail address of person(s) attending. Early registration of your attendance is welcome and encouraged. 7. Hotel Room Reservation ^^^^^^^^^^^^^^^^^^^^^^^^^ To secure a room please make you reservation directly to one of the hotels, which are listed in the meeting invitation (http://ftp3.itu.int/av-arch/avc-site/2005-2008/0505_Bie/Biel_Invitation.d oc) as soon as possible. We are looking forward to meeting with you in Biel-Bienne. Sincerely yours, Paul JONES (document manager of this meeting) Robert GILMAN Bastien LAMER Martin EUCHNER (meeting organizer of this meeting) Leo LEHMANN (meeting host of this meeting) ----------

1 0

FW: [AVT] RFC 4040 on RTP Payload Format for a 64 kbit/s TransparentCall
by simao.campos＠ITU.INT 22 Apr '05

22 Apr '05

Dear experts, FYI. Best regards, Simao -----Original Message----- From: avt-bounces(a)ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of rfc-editor(a)rfc-editor.org Sent: 21 April 2005 01:05 To: ietf-announce(a)ietf.org Cc: avt(a)ietf.org; rfc-editor(a)rfc-editor.org Subject: [AVT] RFC 4040 on RTP Payload Format for a 64 kbit/s TransparentCall --NextPart A new Request for Comments is now available in online RFC libraries. RFC 4040 Title: RTP Payload Format for a 64 kbit/s Transparent Call Author(s): R. Kreuter Status: Standards Track Date: April 2005 Mailbox: ruediger.kreuter(a)siemens.com Pages: 8 Characters: 15363 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtp-clearmode-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4040.txt This document describes how to carry 64 kbit/s channel data transparently in RTP packets, using a pseudo-codec called "Clearmode". It also serves as registration for a related MIME type called "audio/clearmode". "Clearmode" is a basic feature of VoIP Media Gateways. This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST(a)IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST(a)RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info(a)RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info(a)RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager(a)RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR(a)RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute .. Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO(a)RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <050420160230.RFC(a)RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc4040 --OtherAccess Content-Type: Message/External-body; name="rfc4040.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <050420160230.RFC(a)RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Audio/Video Transport Working Group avt(a)ietf.org https://www1.ietf.org/mailman/listinfo/avt

1 0