FW: An important step for interoperability and functionality of text communication: RFC 4103 replaces RFC 2793.

simao.campos at itu.int simao.campos at itu.int
Tue Jun 7 09:35:55 EDT 2005


Dear editors and all,

Very belatedly, please find after the signature my comments to the 
following four documents posted in April:

F.VTIP
Service description and requirements for videotelephony over IP 
services (Editor:  Mr Zhang Qing)
<http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FVTI
P_050414.zip>

F.MMCIP
Service description and requirements for multimedia conferencing over 
IP services (Editor: Ms Sun Mingjun)
<http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FMMC
IPv1.1_050410.zip>

F.DL
Service description and requirements for distance learning services 
(Editor: Ms Nie Xiuying)
<http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/Fdlr
ev1_050410clear.zip>

F.AVoD
Service description and requirements for audiovisual on demand 
services (Editor: Ms Nie Xiuying)
<http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FAVO
Drev1_050414.zip>

They are mostly editorial to make the documents more understandable. 
Your review about the substance is requested so that we can decide in 
July if these documents be processed as draft Recommendations.

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
******************************************************************

Comments common to the four documents
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

1/ I would suggest to include an introductory text to the service 
scenario section indicating its purposes, something like:

This section describes typical service scenarios to illustrate the 
... service and to derive its technical requirements.

2/ Please make sure that the "requirements" section reflects all of 
what the service scenarios indicate.

3/ "stage" vs "step"

Since the terms "stage 1", "stage 2" and "stage 3" have particular 
meanings defined in I.130, please use "step" for our current 
documents.

4/ Use of capital letters

It looks the use of capital letters are not consistent. The ITU 
guideline is in Appendix I to A.15:

Unnecessary use of capitalized words should be avoided.

5/ Editorial observations

I have placed marked up documents with my observations at the following
place:

http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FVTIP
_050414_SO.zip
http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FMMCI
P_050410_SO.zip
http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/Fdl_0
50410_SO.zip
http://ftp3.itu.int/av-arch/avc-site/2005-2008/0507_Gen/Working_Docs/FAVOD
_050414_SO.zip

Please note that the text in {} is not a modification itself but 
shows my comment or question


F.VTIP
^^^^^^

1/ Section 4, 3rd paragraph

It may hint that videotelephony service = conventional telephony service.

The use of videotelephony services ... ==> The way to place a call of 
videotelephony services is just the same as that of conventional 
telephony services ...

2/ Section 4, 2nd bullet

Audio and video mixing devices may be operated by the "network" or by 
the "user." It would be more appropriate to delete "network" from 
"network devices."

3/ Section 5.2

"unmanned baby-sitting for unattended kids" should be "unmanned 
baby-sitting for kids"? Kids with baby-sitting are attended, I think,

4/ Section 5.3

It is not clear to me how the service profiles will be utilized in 
this document or other places. Please add some more positive 
statements of the intention. Just "for references" looks weak.

5/ Section 6.1.3, 1st paragraph

Can we replace "800 customer service" with a generic naming? I think 
"800" is the number in the US, it is called "free dial" service in 
Japan and the number starts with 0120.

6/ Section 7.1, Basic requirements, 3rd bullet

I wonder if "when necessary" adds particular meaning compared to the 
sentence without those two words.

7/ Section 7.6.1, 2nd sentence

"terminal-based echo-cancellation" means acoustic echo-cancellation? 
Its parallel term would be "network-based" echo-cancellation. Here we 
are addressing echo due to the feedback from the loud-speaker to the 
microphone, not the one due to the 4-wire to 2-wire conversion in the 
network. My point is that network-based echo-cancellation may in 
principle deal with both network echo and acoustic echo while the 
terminal-based echo-canllelation deals with only acoustic echo.

8/ Section 7.6.4 1st sentence

I am afraid "whenever there are motions in the human facial regions, 
e.g., lips or eyes" is not always true. Probably you are referring to 
the case where frame dropping is employed when a large amount of data 
is generated due to large motions. I would suggest to describe the 
case more precisely or delete the quoted text.

F.MMCIP
^^^^^^^

1/ Section 2.6

As we have "multimedia conference service" in Section 2.9, I would 
suggest the following:

A type of multimedia conference service that utilizes networks for 
control and media transfer.

2/ Section 2.7, last sentence

As we may also use ALM (Application Layer Multicast) in the future, 
use of network transport multicast may not be an only solution. "may" 
instead of "should" would be more appropriate.

3/ Section 5, 2nd paragraph

"If there are two or more terminals, ..." I wonder if the number be 
"three or more" instead of "two ore more". The multimedia information 
control and exchange is needed also for the case where only two 
terminals are involved?

4/ Section 5, 3 bullets

It looks multiple viewpoints are involved to get these three types of 
terminal: hardware/software, full/part time use, movable/fixed. 
Please sort them out.

5/ Section 6.1, 2nd sentence

We need clarification here.

Since the "Voice/Video/Data Switch & Process function" is in the 
IP-based Network area, the multimedia path between the switch&process 
function and the right most User is understood to be IP. Does this 
mean that PSTN Access terminal is using IP over PSTN? It looks more 
realistic to me that the switch&process function has PSTN interface 
and the voice is ordinary analog one.

6/ Section 6.3

I would suggest to unify the function listing style as verb first.

F.DL
^^^^

1/ Table of Contents

Why ex Section 8 Requirements has been dropped in this draft? It 
should be an essential part as shown in the title and scope.

2/ Section 1

I cannot understand the meaning of "responsive application solution" 
and the intention of including the "when applicable ITU-T 
Recommendations are not yet available" part. The latter looks 
contradictory if this documents is intended as an ITU-T 
Recommendation.

3/ Section 2

We need to check if we can include IEEE standards as part of the 
normative references.

4/ Section 3, Distance Learning

I do not understand what "sometimes connectedness" means.

5/ Section 6, last paragraph

The same comment as 1/.

6/ Section 7.1.1, Case 2, Stage 1

It is implied that DLSP provides instant messaging. Videophone and 
telephone look separate from DLSP. Is that the intention?

7/ Section 7.3, 1st paragraph

I would suggest to itemize listed applications as bullets.

8/ Section 7.3, 2nd paragraph

"conferences" and "files distribution applications" look too generic 
for this document addressing distance learning service.

9/ Section 8.2

I would suggest to itemize listed applications under the sentence:

The following are desirable adjuncts to the distance learning application:

F.avod
^^^^^^

1/ Section 5, 2nd paragraph

I wonder if the scope of this document is limited to the use of 
"current carriers networks." I believe it should also take into 
account other type of networks like corporate, private ones.

2/ Section 6.1, 2nd paragraph

This description doe not match Figure 1. "Control and management 
system" is a part of the "service provider" there.

3/ Section 6.1, after Figure 1, 2nd bullet, 2nd sentence

It is hard to capture the structure of this sentence. Please rephrase it.

4/ Section 6.1

"value-added services" is too generic. We need some examples in the 
context of avod.

5/ Section 7.1, 1st paragraph, 3rd sentence

I cannot understand what "integrating centralized or distributed 
methods" means.

6/ Section 7.2, 1st paragraph, 4th sentence starting with "Some 
current affairs, ..."

This sentence is incomplete.

7/ Section 7.3, Stage 5, 2nd last sentence

It is not clear to me how "due to he has passed the authentication 
before" related to other part of the sentence.

8/ Section 8.3, 3rd sentence

This sentence is incomplete.

9/ Section 8.6, after the three bullets

What is "start time"? Response time to the request of an audiovisual
content?

10/ Section 9, 2)

Add some more descriptions, "control" is necessary in any type of 
avod applications as far as "on demand" is involved.

11/ Section 11.2, 1st sentence

It looks we are comparing the two different categories; provider (SP 
stands for Service Provider) and system (videoconference system). It 
is not a surprise if they are quite different in functions.

==========
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 15674 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20050609/4588fc21/attachment-0006.bin>


More information about the sg16-avd mailing list