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

Re: H.248.1 V3 Editorial Comments: § 7.1.
by Christian Groves 25 May '05

25 May '05

Hello Kevin, I would concur with Albrecht on this. Regards, Christian Albrecht.Schwarz(a)alcatel.de wrote: > 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

RE: Meeting Announcement: H.248.1 Version 3 Online Editing Meetin
by OKUBO Sakae 23 May '05

23 May '05

Dear Kevin and all, At 10:25 -0400 05/05/23, Kevin Boyle wrote: >[...] >These are currently in the Incoming folder, but will soon be >available in the H.248.1_Editing directory. > >The documents will also be available through the following URLs: ><http://ftp3.itu.int/av-arch/avc-site/2005-2008/H.248.1_Editing/>http://f tp3.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/>f tp://avguest:Avguest@ftp3.itu.int/avc-site/2005-2008/H.248.1_Editing/ They have been moved to the place indicated above. -- 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

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

23 May '05

Colleagues, Per the schedule posted last week, the input drafts for the H.248.1 V3 Editing meeting have been uploaded. There are 7 documents, marked TD1 - TD7: TD1 - H.248.1 V3 Input Draft TD2 - H.248.1 V3 Clean Version TD3 - H.248.1 V3 Week 1 sections TD4 - H.248.1 V3 Week 2 sections TD5 - H.248.1 V3 Week 3 sections TD6 - H.248.1 V3 Week 4 sections TD7 - H.248.1 V3 Week 5 sections These are currently in the Incoming folder, but will soon be available in the H.248.1_Editing directory. 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/ Kevin

1 0

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