q_zhang at huawei.com
Thu Jul 21 21:26:21 EDT 2005
Dear Gunnar Hellstrom,
Very thanks for your comments.
About your reminded questions, I have some opinion as below for your
"1.Scope collision with F.703 Multimedia Conversation Service
Here is a clarification for scope description about F.703 and F.VTIP.
F.703 describes a general requirements of multimedia conversation service,
many conversation services are covered in it, such as videotelephony, etc.
And for each specific service, for example videotelephony service, it is
necessary to describe the detailed requirement. So F.720 describes the
sub-general requirements of videotelephony service, then F.721 for ISDN,
F.723 for PSTN videotelephony service respectively, and F.VTIP intends to
describe the requirements of IP videotelephony service.
"2. The real time text medium is missing in the definition..."
I agree that real time text medium is very important for people with
hearing or speech disabilities. In F.VTIP, the IP videotelephony service
is divided into basic and enhanced service, the real time text medium has
been included in enhanced IP videotelephony service, I'm considering how
to emphasize these features in F.VTIP.
Sincerely thanks again for your kind advice.
> ----- Original Message -----
> From: "Gunnar Hellstrom" <gunnar.hellstrom at omnitor.se>
> To: "OKUBO Sakae" <okubo at MXZ.MESH.NE.JP>; "zhangqing"
<q_zhang at huawei.com>
> Cc: <itu-sg16 at external.cisco.com>
> Sent: Wednesday, July 20, 2005 5:48 AM
> Subject: RE: ABOUT F.VTIP
> Dear Qing Zhang,
> I have read the F.VTIP draft and have a couple of questions/comments:
> 1. Scope collision with F.703 Multimedia Conversation Service
> It is not earlier habit of F.70x Recommendations to be network type
specific. They describe multimedia service requirements in general terms,
from the human point of view regardless of network type. F.703 already
defines and describes the Video Telephony service and should be
interpreted to define it on both circuit switched and IP networks. I think
having an IP specific definition of Video Telephony in the F.70x series
> Today, we also have an emphasis of evening out network influence on
service experience in the NGN activities.
> I suggest that you drop the IP specifics in this draft and merge it as
an update to F.703.
> 2. The real time text medium is missing in the definition.
> In F.703 there is a service defined called "total conversation". It is a
very impotant superset of video telephony created by adding real time
conversational text medium to video telephony. The text is transmitted
with the same flow as it is typed in order to give the call participants a
good feeling of being in contact. No irritating waiting for the other one
to complete a sentence, it all can be read by the participants as it is
> This addition has been driven by requirements from people with hearing
or speech disabilities, but the feature has very general value.
> SG16 has been quite aware of the need to take accessibility for people
with disabilities in account when creating Recommendations. This trend is
finally spreading to other groups, and F.703 and other mainstream
Recommendations with accessibility included form very important references
in the work with deployment of accessible mainstream services.
> If advice no 1 to merge your document with F.703 is not followed, I
suggest that IP total conversation is added to the F.VTIP draft with a
description similar to the one for total conversation and the text medium
> I suggest that you declare three media to be normal for IP Video
telephony; video, text and audio.
> Best regards
> Gunnar Hellström
> Gunnar Hellström
> Omnitor AB
> Renathvägen 2
> SE 121 37 Johanneshov
> +46 8 556 002 03
> Mob: +46 708 204 288
> Gunnar.Hellstrom at Omnitor.se
>>From: zhangqing [mailto:q_zhang at huawei.com]
>>Sent: Tuesday, July 12, 2005 6:09 PM
>>To: OKUBO Sakae
>>Cc: itu-sg16 at external.cisco.com
>>Subject: ABOUT F.VTIP
>>Dear Mr. Okubo and all,
>>Attached file is the new edition of F.VTIP.
>>I appreciate the comments from Mr.Okubo and Mr. Blin
>>Jean-Pierre, more comments and suggestions are solicited.
>>Huawei Technologies Co., Ltd
>>Tel : +86-755-89650436
>>Fax : +86-755-89651312
>>E-mail: q_zhang at huawei.com
>>----- Original Message -----
>>From: "OKUBO Sakae" <okubo at MXZ.MESH.NE.JP>
>>To: <itu-sg16 at external.cisco.com>
>>Sent: Tuesday, July 12, 2005 10:49 AM
>>Subject: SG16 meeting during 26 July - 5 August
>>> Dear WP2/16 experts,
>>> Here are two pieces of information and request toward the upcoming
>>> SG16 meeting.
>>> 1/ Q.5 Rapporteur
>>> Very unfortunately Mr. Bob Gilman advised the SG16 management of his
>>> resignation from Q.5 Rapporteur and we reluctantly have to accept
>>> this. As an emergency measure we have asked Mr. Paul Jones to lead
>>> the Q.5 works at the upcoming SG16 meeting.
>>> Using this opportunity I would like to thank Bob not only for his
>>> excellent leadership in the NAT/firewall traversal issue as
>>> Rapporteur, but also for his valuable contributions to the H.323,
>>> H.235 and other SG16 topics as expert since around 1999.
>>> 2/ Documents for the meeting
>>> Since this meeting is of Study Group level, all the documents are
>>> handled by TSB, not by a Rapporteur.
>>> However, you may wish to upload your documents to the avc-site for
>>> advance review by the experts. In that case, place your document at:
>>> user: avguest
>>> password: Avguest
>>> or email it to me, then I will move it to:
>>> user: avguest
>>> password: Avguest
>>> Best regards,
>>> OKUBO Sakae
>>> e-mail: sokubo at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 11622 bytes
Desc: not available
More information about the sg16-avd