<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-2022-JP"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Dear Paul,<br>
<br>
Thank you for your advice. I have revised the part as follows:<br>
<br>
GEN-1xz: A protocol shall be defined or specified for
communication over Interface C.<br>
==><br>
GEN-1xz: One or more protocols may be defined or specified by an
Application for communication over Interface C.<br>
<br>
Updated version AVD-3995b has been uploaded to the /Incoming.<br>
<br>
Sakae OKUBO<br>
<br>
(10/11/30 23:54), Paul E. Jones wrote:</tt>
<blockquote cite="mid:4CF5102E.6030301@packetizer.com" type="cite">
<meta content="text/html; charset=ISO-2022-JP"
http-equiv="Content-Type">
<tt> Mr Okubo,<br>
<br>
I think the protocol used for Interface C will be defined by the
applications. This might be RTP/RTCP or something else, but
really a choice to be made for the specific application.</tt> <tt><br>
<br>
Paul</tt> <tt><br>
<br>
On 11/30/2010 6:31 AM, OKUBO Sakae wrote: </tt>
<blockquote cite="mid:4CF4E076.7080209@mxz.mesh.ne.jp" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-2022-JP">
<tt>Dear Paul,<br>
<br>
I have uploaded AVD-3995a at the /Incoming. According to the
Monday discussion, the following additions to G-1nn items of
the Requirements document have been made:<br>
<br>
- Definition of Interface K<br>
- Protocol for Interface K<br>
- Protocol for Interface C<br>
<br>
Please note that the third point was not raised at the
yesterday's discussion, but I have included it to make the
Requirements document complete by covering all of the
interfaces (A, B, C, E, K) except interface D that is not
subject to standardization (see MED-109). <br>
<br>
One thing needing further consideration is if the protocol for
Interface C (for media flow) is single or multiple. Currently
the requirement says: <br>
<br>
"<span style="font-size: 12pt;" lang="EN-GB">A protocol shall
be defined or specified for communication over Interface C.</span>"<br>
<br>
In terms of transport, it may be single like RTP, but variety
of application media may flow through this interface C.<br>
<br>
Best regards,<br>
<br>
OKUBO Sakae<br>
e-mail: <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:okubo@aoni.waseda.jp">okubo@aoni.waseda.jp</a>,
mobile phone: +81 90 2477 8603<br>
Visiting Professor<br>
Global Information and Telecommunication Institute (GITI)<br>
Waseda University<br>
******************************************************************<br>
Waseda University, YRP Ichibankan 312 Tel: +81 46 847
5406<br>
3-4 Hikarinooka, Yokosuka-shi, Kanagawa-ken<br>
239-0847 Japan<br>
H.323 videoconferencing: arranged by
advice<br>
******************************************************************<br>
<br>
</tt>
<style>@font-face {
font-family: "MS Mincho";
}@font-face {
font-family: "@MS Mincho";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 6pt 0mm 0.0001pt; font-size: 12pt; font-family: "Times New Roman"; }div.Section1 { page: Section1; }</style>
</blockquote>
</blockquote>
<tt><br>
</tt>
</body>
</html>