From mmusic-bounces@ietf.org Thu Feb 02 16:50:43 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4mLj-0002cm-9L; Thu, 02 Feb 2006 16:50:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4mLd-0002aq-CU; Thu, 02 Feb 2006 16:50:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16999;
	Thu, 2 Feb 2006 16:48:49 -0500 (EST)
Received: from host10.216.41.24.conversent.net ([216.41.24.10]
	helo=acmepacket.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F4mWt-0006PX-DN; Thu, 02 Feb 2006 17:02:17 -0500
Received: from HKaplan [216.41.24.2] by acmepacket.com with ESMTP
	(SMTPD-9.01) id AE5D03C0; Thu, 02 Feb 2006 16:49:17 -0500
From: "Hadriel Kaplan" <HKaplan@acmepacket.com>
To: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
	"'Sam Hartman'" <hartmans-ietf@mit.edu>
Subject: RE: [MMUSIC] Re: comedia-tls: proposed change for certificate
	identities
Date: Thu, 2 Feb 2006 16:49:46 -0500
Message-ID: <01fe01c62842$95b70530$60c8000a@acmepacket.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYloQiMaBF2J7FUSmiXgVpcDabKMQCoSGoQ
In-Reply-To: <17374.4868.521418.118273@cnr.cs.columbia.edu>
X-Spam-Score: 3.7 (+++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org, mmusic@ietf.org, 'EKR' <ekr@networkresonance.com>,
	jon.peterson@neustar.biz, mankin@psg.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

FWIW, I like this change a lot.   
-hadriel


> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Jonathan Lennox
> Sent: Monday, January 30, 2006 8:22 AM
> To: Sam Hartman
> Cc: mankin@psg.com; EKR; mmusic@ietf.org; jon.peterson@neustar.biz;
> tls@ietf.org
> Subject: [MMUSIC] Re: comedia-tls: proposed change for certificate
> identities
> 
> On Sunday, January 29 2006, "Sam Hartman" wrote to "Jonathan Lennox,
> mmusic@ietf.org, tls@ietf.org, EKR, jon.peterson@neustar.biz,
> mankin@psg.com" saying:
> 
> > >>>>> "Jonathan" == Jonathan Lennox <lennox@cs.columbia.edu> writes:
> >
> >
> >     Jonathan> * If your SDP was sent over an end-to-end authenticated
> >     Jonathan> and integrity-protected channel, there are no
> >     Jonathan> constraints on what identity you assert in your TLS
> >     Jonathan> certificates; you can use anything you want.  Identity
> >     Jonathan> is handled by the transporting protocol.
> >
> > What about hop-by-hop authenticated with each hop integrity protected.
> > IMHO in many environments, this presents acceptable man-in-the-middle
> > risk.  I think that it may present significantly easier to deal with
> > usability issues so I think it should at least be allowed if not
> > encouraged.
> 
> This will certainly be the most common way of securing SDP, I think --
> this
> describes how sips, i.e. sip over hop-by-hop TLS, works.  You're
> vulnerable
> to a broken or subverted sip proxy server, but otherwise you're safe.
> 
> If there's consensus that it's acceptable to allow this mode, I can add
> language allowing it.  However, I think this is a big enough change I'd
> like
> to hear positive consensus for it; this should get something more than
> just
> consent-by-silence from the working group.



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Thu Feb 02 21:33:13 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4ql7-0002e5-KX; Thu, 02 Feb 2006 21:33:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4ql6-0002bH-6g
	for mmusic@megatron.ietf.org; Thu, 02 Feb 2006 21:33:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12227
	for <mmusic@ietf.org>; Thu, 2 Feb 2006 21:31:34 -0500 (EST)
Received: from mxgate1.brooktrout.com ([204.176.74.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4qwZ-000196-K3
	for mmusic@ietf.org; Thu, 02 Feb 2006 21:45:04 -0500
X-IronPort-AV: i="4.02,81,1139202000"; 
	d="scan'208,217"; a="27430496:sNHT72440616"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] RTSP & Megaco
Date: Thu, 2 Feb 2006 21:33:43 -0500
Message-ID: <330A23D8336C0346B5C1A5BB19666647021EF1AB@ATLANTIS.Brooktrout.com>
Thread-Topic: [MMUSIC] RTSP & Megaco
Thread-Index: AcYUKui1fp/1Bb/MRH+MbZGlQr0DngUF8v0w
From: "Burger, Eric" <eburger@brooktrout.com>
To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>, <mmusic@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0701610759=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0701610759==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6286A.4042CA68"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6286A.4042CA68
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is the question "Why is SDP different for Megaco?" or is the question
"Why can't I use RTSP/SIP for Megaco?"=20

=20

________________________________

From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Osher Hmelnizky
Sent: Sunday, January 08, 2006 3:10 AM
To: mmusic@ietf.org
Subject: [MMUSIC] RTSP & Megaco

=20

Is it any draft developing regarding RTSP and Megaco.=20

All drafts speak on SIP & RTSP implementations. Why megaco can't work in
the same manner.

=20

Osher=20

=20

R&D Audiocodes


------_=_NextPart_001_01C6286A.4042CA68
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is the question &#8220;Why is SDP
different for Megaco?&#8221; or is the question &#8220;Why can&#8217;t I =
use
RTSP/SIP for Megaco?&#8221; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Osher Hmelnizky<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, January 08, =
2006
3:10 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [MMUSIC] RTSP =
&amp;
Megaco</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is it any draft developing regarding RTSP and Megaco. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>All drafts speak on SIP &amp; RTSP implementations. =
Why
megaco can&#8217;t work in the same manner.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Osher <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>R&amp;D Audiocodes<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C6286A.4042CA68--


--===============0701610759==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============0701610759==--




From mmusic-bounces@ietf.org Sat Feb 04 06:17:43 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5LQF-00055I-Dx; Sat, 04 Feb 2006 06:17:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4t17-0003ZQ-QF
	for mmusic@megatron.ietf.org; Thu, 02 Feb 2006 23:57:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21890
	for <mmusic@ietf.org>; Thu, 2 Feb 2006 23:56:15 -0500 (EST)
Received: from igw2.watson.ibm.com ([129.34.20.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4tCc-0005pO-5a
	for mmusic@ietf.org; Fri, 03 Feb 2006 00:09:47 -0500
Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com
	[129.34.20.41])
	by igw2.watson.ibm.com (8.12.11/8.13.1/8.13.1-2005-04-25 igw) with
	ESMTP id k134vdWp015862; Thu, 2 Feb 2006 23:57:39 -0500
Received: from sp1n293en1.watson.ibm.com (localhost [127.0.0.1])
	by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_2) with
	ESMTP id k134vYR579342; Thu, 2 Feb 2006 23:57:34 -0500
Received: from mgsmtp00.watson.ibm.com (mgsmtp00.watson.ibm.com [9.2.40.58])
	by sp1n293en1.watson.ibm.com (8.11.7-20030924/8.11.7/01-14-2004_1) with
	ESMTP id k134vXX579340; Thu, 2 Feb 2006 23:57:33 -0500
Received: from sibylla.watson.ibm.com (sibylla.watson.ibm.com [9.2.16.101])
	by mgsmtp00.watson.ibm.com (8.12.11/8.12.11/2005/09/01) with ESMTP id
	k135uaxe007604; Fri, 3 Feb 2006 00:56:36 -0500
Received: from localhost (canetti@localhost)
	by sibylla.watson.ibm.com (AIX5.1/8.11.6p2/8.11.0/03-06-2002) with
	ESMTP id k134vU236864; Thu, 2 Feb 2006 23:57:31 -0500
Date: Thu, 2 Feb 2006 23:57:30 -0500 (EST)
From: canetti <canetti@watson.ibm.com>
To: msec@securemulticast.org
In-Reply-To: <Pine.A41.4.58.0602012334050.34614@sibylla.watson.ibm.com>
Message-ID: <Pine.A41.4.58.0602022350510.31536@sibylla.watson.ibm.com>
References: <Pine.A41.4.58.0602012334050.34614@sibylla.watson.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Sat, 04 Feb 2006 06:17:41 -0500
Cc: canetti@csail.mit.edu, ldondeti@qualcomm.com, mmusic@ietf.org, jo@acm.org,
	csp@csperkins.org
Subject: [MMUSIC] Last Call for draft-ietf-msec-mikey-rsa-r-02.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: canetti@csail.mit.edu
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org



Folks,

This is an MSEC last call on draft-ietf-msec-mikey-rsa-r-02.txt.
Version 02 was posted recently, and the document seems quite stable.
Please take time to read and comment.

MMUSIC folks: The main intended use of the proposed mode of MIKEY
is within mmusic protocols. Thus, although officially this is only an
MSEC LC, you may want to read and comment as well.

The LC will end in two weeks, on Friday Feb 17.

Thanks,

Ran

The latest version of the draft is available at:

http://www.ietf.org/internet-drafts/draft-ietf-msec-mikey-rsa-r-02.txt


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Sun Feb 05 02:40:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5eVt-0002Mw-FV; Sun, 05 Feb 2006 02:40:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F5eVq-0002Mr-T6
	for mmusic@megatron.ietf.org; Sun, 05 Feb 2006 02:40:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16027
	for <mmusic@ietf.org>; Sun, 5 Feb 2006 02:39:06 -0500 (EST)
Received: from mail1.audiocodes.com ([212.25.125.19] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5ehm-00033M-KA
	for mmusic@ietf.org; Sun, 05 Feb 2006 02:53:07 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Sun, 05 Feb 2006 10:52:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] Using RTSP with SIP
Date: Sun, 5 Feb 2006 09:41:06 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
Thread-Topic: [MMUSIC] Using RTSP with SIP
Thread-Index: AcYV4PalPJO7dTPARcCEunhAesvg2gSYY3yAAHkKxOA=
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
To: "Burger, Eric" <eburger@brooktrout.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e9d8c60d9288f2c774f26bab15869505
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2081060412=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2081060412==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C62A27.8651F2CE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C62A27.8651F2CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

What I'm trying to say is: why can't I use SIP for the call
establishment and RTSP for the stream control. How can synchronize two
protocols on the MRF side?=20

On the client side it is no problem, but server side should be aware
that two sessions are interconnected to the one specific call.

Such synchronization I saw in the SIP/MRCP draft
(draft-ietf-speechsc-mrcpv2-09).

=20

Thanks a lot

=20

Osher

=20

________________________________

From: Burger, Eric [mailto:eburger@brooktrout.com]=20
Sent: Friday, February 03, 2006 4:34 AM
To: Osher Hmelnizky
Subject: RE: [MMUSIC] Using RTSP with SIP

=20

What are you trying to accomplish?  Two sessions are two sessions.  It
is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
sessions.

=20

________________________________

From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Osher Hmelnizky
Sent: Tuesday, January 10, 2006 7:26 AM
To: mmusic@ietf.org
Subject: [MMUSIC] Using RTSP with SIP

=20

In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
synchronize the SIP and MRCP Sessios, defined

a=3Dchannel:xxx

=20

as part of application SDP.

=20

I'm trying to find out how I can synchronize SIP and RTSP streams at the
Media Server layer without any indication.

=20

As a=3Dchannel defined at the SDP level can I use this parameter to sync
between SIP and RTSP Streams.

=20

Thanks a lot.

=20

Osher

=20

=20

=20

=20


------_=_NextPart_001_01C62A27.8651F2CE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>What I&#8217;m trying to say is: =
why can&#8217;t
I use SIP for the call establishment and RTSP for the stream control. =
How can synchronize
two protocols on the MRF side? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>On the client side it is no =
problem, but
server side should be aware that two sessions are interconnected to the =
one
specific call.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Such synchronization I saw in the
SIP/MRCP </span></font><font color=3Dblack face=3DArial><span =
style=3D'font-family:
Arial;color:black'>draft (</span></font><font color=3Dblack><span
style=3D'color:black'>draft-ietf-speechsc-mrcpv2-09</span></font><font
color=3Dblack face=3DArial><span =
style=3D'font-family:Arial;color:black'>).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3DArial><span =
style=3D'font-size:
12.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3DArial><span =
style=3D'font-size:
12.0pt;font-family:Arial;color:black'>Thanks a =
lot<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3DArial><span =
style=3D'font-size:
12.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3DArial><span =
style=3D'font-size:
12.0pt;font-family:Arial;color:black'>Osher</span></font><font size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Burger, Eric
[mailto:eburger@brooktrout.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, February =
03, 2006
4:34 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Osher Hmelnizky<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
Using RTSP
with SIP</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>What are you trying to =
accomplish?&nbsp;
Two sessions are two sessions. &nbsp;It is either SIP or RTSP.&nbsp; =
MRCP (not
an IETF standard) has two, distinct =
sessions.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Osher Hmelnizky<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, January =
10, 2006
7:26 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">mmusic@ietf.org</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [MMUSIC] Using =
RTSP with
SIP</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In the last MRCP draft =
(</span></font>draft-ietf-speechsc-mrcpv2-09<font
face=3DArial><span style=3D'font-family:Arial'>), in order to =
synchronize the SIP
and MRCP Sessios, defined<o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'text-indent:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>a=3Dchannel:xxx<o:p></o:p></=
span></font></p>

<p class=3DMsoPlainText style=3D'text-indent:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>as part of application =
SDP.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I&#8217;m trying to find out how I can synchronize =
SIP and
RTSP streams at the Media Server layer without any =
indication.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As a=3Dchannel defined at the SDP level can I use =
this
parameter to sync between SIP and RTSP =
Streams.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks a lot.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Osher<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C62A27.8651F2CE--


--===============2081060412==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============2081060412==--




From mmusic-bounces@ietf.org Sun Feb 05 08:17:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F5jm1-0006NA-TH; Sun, 05 Feb 2006 08:17:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F5jlv-0006Lz-Ih
	for mmusic@megatron.ietf.org; Sun, 05 Feb 2006 08:17:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08025
	for <mmusic@ietf.org>; Sun, 5 Feb 2006 08:15:53 -0500 (EST)
Received: from mxgate1.brooktrout.com ([204.176.74.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5jxi-00065z-8q
	for mmusic@ietf.org; Sun, 05 Feb 2006 08:29:57 -0500
X-IronPort-AV: i="4.02,89,1139202000"; d="scan'208"; a="27595840:sNHT70523136"
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Using RTSP with SIP
Date: Sun, 5 Feb 2006 08:17:22 -0500
Message-ID: <330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
Thread-Topic: [MMUSIC] Using RTSP with SIP
Thread-Index: AcYV4PalPJO7dTPARcCEunhAesvg2gSYY3yAAHkKxOAAC8DMYA==
From: "Burger, Eric" <eburger@brooktrout.com>
To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

That is something totally different and explicitly outside the scope of =
MRCPv2.  What you want is something like the mediactrl work (not =
chartered).  Search the I-D directory for mediactrl.  To subscribe, send =
'subscribe mediactrl' to majordomo@lists.ubiquitysoftware.com

________________________________________
From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]=20
Sent: Sunday, February 05, 2006 2:41 AM
To: Burger, Eric
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] Using RTSP with SIP

Hi,

What I'm trying to say is: why can't I use SIP for the call =
establishment and RTSP for the stream control. How can synchronize two =
protocols on the MRF side?=20
On the client side it is no problem, but server side should be aware =
that two sessions are interconnected to the one specific call.
Such synchronization I saw in the SIP/MRCP draft =
(draft-ietf-speechsc-mrcpv2-09).

Thanks a lot

Osher

________________________________________
From: Burger, Eric [mailto:eburger@brooktrout.com]=20
Sent: Friday, February 03, 2006 4:34 AM
To: Osher Hmelnizky
Subject: RE: [MMUSIC] Using RTSP with SIP

What are you trying to accomplish?=A0 Two sessions are two sessions. =
=A0It is either SIP or RTSP.=A0 MRCP (not an IETF standard) has two, =
distinct sessions.

________________________________________
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf =
Of Osher Hmelnizky
Sent: Tuesday, January 10, 2006 7:26 AM
To: mmusic@ietf.org
Subject: [MMUSIC] Using RTSP with SIP

In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to =
synchronize the SIP and MRCP Sessios, defined
       a=3Dchannel:xxx
      =20
as part of application SDP.

I'm trying to find out how I can synchronize SIP and RTSP streams at the =
Media Server layer without any indication.

As a=3Dchannel defined at the SDP level can I use this parameter to sync =
between SIP and RTSP Streams.

Thanks a lot.

Osher




_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 06 04:45:42 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F62wI-0001j8-LV; Mon, 06 Feb 2006 04:45:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F62wG-0001gW-IL
	for mmusic@megatron.ietf.org; Mon, 06 Feb 2006 04:45:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02422
	for <mmusic@ietf.org>; Mon, 6 Feb 2006 04:44:00 -0500 (EST)
Received: from mail.uni-ulm.de ([134.60.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F638O-0005BH-AK
	for mmusic@ietf.org; Mon, 06 Feb 2006 04:58:14 -0500
Received: from uni-ulm.de (discovery.informatik.uni-ulm.de [134.60.77.113])
	(authenticated bits=0)
	by mail.uni-ulm.de (8.13.4/8.13.4) with ESMTP id k169jRfJ012697
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 6 Feb 2006 10:45:28 +0100 (MET)
Message-ID: <43E71B89.30205@uni-ulm.de>
Date: Mon, 06 Feb 2006 10:48:57 +0100
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org, Osher.Hmelnizky@audiocodes.com
References: <200602051702.k15H2S3i029734@smtp.uni-ulm.de>
In-Reply-To: <200602051702.k15H2S3i029734@smtp.uni-ulm.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi,
SIP and RTSP are two different sessions. Their frameworks do not exclude 
the scenario that both of them shall be synchronised, however, there is 
no existing solution on such synchronisation. You can synchronize SIP 
and RTSP only at presentation level (i.e. SDP), like done for SIP and 
MRCP, as at session level SIP and RTSP are different instances that are 
not aware of each other. You could "misuse" the SDP SIP/MRCP attribute 
"a=channel:xxx" with your own parameters for RTSP, or use the SDP "i=" 
line also with your own paramentes, or define your own attribute line, 
e.g. "a=stacksynch:whatever". However, all these are non-standard solutions.
KR,
Teodora

mmusic-request@ietf.org wrote:

>
>Message: 1
>Date: Sun, 5 Feb 2006 09:41:06 +0200
>From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>Subject: RE: [MMUSIC] Using RTSP with SIP
>To: "Burger, Eric" <eburger@brooktrout.com>
>Cc: mmusic@ietf.org
>Message-ID:
>	<79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi,
>
> 
>
>What I'm trying to say is: why can't I use SIP for the call
>establishment and RTSP for the stream control. How can synchronize two
>protocols on the MRF side? 
>
>On the client side it is no problem, but server side should be aware
>that two sessions are interconnected to the one specific call.
>
>Such synchronization I saw in the SIP/MRCP draft
>(draft-ietf-speechsc-mrcpv2-09).
>
> 
>
>Thanks a lot
>
> 
>
>Osher
>
> 
>
>________________________________
>
>From: Burger, Eric [mailto:eburger@brooktrout.com] 
>Sent: Friday, February 03, 2006 4:34 AM
>To: Osher Hmelnizky
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
> 
>
>What are you trying to accomplish?  Two sessions are two sessions.  It
>is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>sessions.
>
> 
>
>________________________________
>
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>Of Osher Hmelnizky
>Sent: Tuesday, January 10, 2006 7:26 AM
>To: mmusic@ietf.org
>Subject: [MMUSIC] Using RTSP with SIP
>
> 
>
>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>synchronize the SIP and MRCP Sessios, defined
>
>a=channel:xxx
>
> 
>
>as part of application SDP.
>
> 
>
>I'm trying to find out how I can synchronize SIP and RTSP streams at the
>Media Server layer without any indication.
>
> 
>
>As a=channel defined at the SDP level can I use this parameter to sync
>between SIP and RTSP Streams.
>
> 
>
>Thanks a lot.
>
> 
>
>Osher
>
> 
>
> 
>
> 
>
> 
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://www1.ietf.org/pipermail/mmusic/attachments/20060205/0ce380c0/attachment.htm
>
>------------------------------
>
>Message: 2
>Date: Sun, 5 Feb 2006 08:17:22 -0500
>From: "Burger, Eric" <eburger@brooktrout.com>
>Subject: RE: [MMUSIC] Using RTSP with SIP
>To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>Cc: mmusic@ietf.org
>Message-ID:
>	<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>That is something totally different and explicitly outside the scope of MRCPv2.  What you want is something like the mediactrl work (not chartered).  Search the I-D directory for mediactrl.  To subscribe, send 'subscribe mediactrl' to majordomo@lists.ubiquitysoftware.com
>
>________________________________________
>From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com] 
>Sent: Sunday, February 05, 2006 2:41 AM
>To: Burger, Eric
>Cc: mmusic@ietf.org
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
>Hi,
>
>What I'm trying to say is: why can't I use SIP for the call establishment and RTSP for the stream control. How can synchronize two protocols on the MRF side? 
>On the client side it is no problem, but server side should be aware that two sessions are interconnected to the one specific call.
>Such synchronization I saw in the SIP/MRCP draft (draft-ietf-speechsc-mrcpv2-09).
>
>Thanks a lot
>
>Osher
>
>________________________________________
>From: Burger, Eric [mailto:eburger@brooktrout.com] 
>Sent: Friday, February 03, 2006 4:34 AM
>To: Osher Hmelnizky
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
>What are you trying to accomplish?  Two sessions are two sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct sessions.
>
>________________________________________
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Osher Hmelnizky
>Sent: Tuesday, January 10, 2006 7:26 AM
>To: mmusic@ietf.org
>Subject: [MMUSIC] Using RTSP with SIP
>
>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to synchronize the SIP and MRCP Sessios, defined
>       a=channel:xxx
>       
>as part of application SDP.
>
>I'm trying to find out how I can synchronize SIP and RTSP streams at the Media Server layer without any indication.
>
>As a=channel defined at the SDP level can I use this parameter to sync between SIP and RTSP Streams.
>
>Thanks a lot.
>
>Osher
>
>
>
>
>
>
>------------------------------
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>
>
>End of mmusic Digest, Vol 22, Issue 3
>*************************************
>  
>

-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/ 

-----------------------------------------



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 06 04:46:57 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F62xV-0002Ht-Gl; Mon, 06 Feb 2006 04:46:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F62xR-0002Fn-Et; Mon, 06 Feb 2006 04:46:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02479;
	Mon, 6 Feb 2006 04:45:13 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F639W-0005cy-GS; Mon, 06 Feb 2006 04:59:28 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id EEFF4E77; 
	Mon,  6 Feb 2006 10:46:32 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Feb 2006 10:46:32 +0100
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 6 Feb 2006 10:46:32 +0100
Message-ID: <43E71AF8.40904@ericsson.com>
Date: Mon, 06 Feb 2006 10:46:32 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Imed.Bouazizi@nokia.com
References: <C84E0A4ABA6DD74DA5221E0833A35DF304ED5B6F@esebe101.NOE.Nokia.com>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF304ED5B6F@esebe101.NOE.Nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Feb 2006 09:46:32.0615 (UTC)
	FILETIME=[36372370:01C62B02]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org, rmt@ietf.org
Subject: [MMUSIC] Re: [Rmt] SDP descriptors for ALC
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi Imed and Rod,

I do have some comments on your proposal.

First of all why have both a=flute-tsi and an a=alc-tsi. Wouldn't a 
a=tsi attribute be more appropriate. To my understanding there is no 
difference in TSI between the two. Also if some other fully specified 
protocol uses TSI they can reuse the TSI attribute. As the protocol will 
identify if it is flute or ALC, or something else in the future I don't 
see a risk of misinterpretation. The same comment applies also to the 
channel attribute. However here something more than a=ch is probably a 
good thing to indicate that it is the number of transport channels 
rather than related to media. Maybe a=trn-ch?

I am also concerned by the use of * and no rules for the ALC/UDP 
protocol. Having something that is underspecified but no defined rules 
for how fully specified mechanisms are identified seem to be a bad 
choice. I would recommend that one uses some type of identifier space 
here. I don't think media types are the correct one, but some space 
should be set up to identify applications.

cheers

Magnus

-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 06 04:57:23 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F637b-0005nE-5u; Mon, 06 Feb 2006 04:57:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F637Y-0005mY-Ea
	for mmusic@megatron.ietf.org; Mon, 06 Feb 2006 04:57:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03126
	for <mmusic@ietf.org>; Mon, 6 Feb 2006 04:55:40 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F63Ji-0007Ai-KW
	for mmusic@ietf.org; Mon, 06 Feb 2006 05:09:55 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:60631
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1F6378-0004lt-NB; Mon, 06 Feb 2006 09:56:55 +0000
In-Reply-To: <43E71B89.30205@uni-ulm.de>
References: <200602051702.k15H2S3i029734@smtp.uni-ulm.de>
	<43E71B89.30205@uni-ulm.de>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C5BEB600-A8B3-4865-A1B2-94EDCD178E6C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
Date: Mon, 6 Feb 2006 09:56:50 +0000
To: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org, Osher.Hmelnizky@audiocodes.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

SDP has the concept of "m=control ..." to signal other control  
sessions. If one were to define how to signal RTSP sessions could be  
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for  
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
> SIP and RTSP are two different sessions. Their frameworks do not  
> exclude the scenario that both of them shall be synchronised,  
> however, there is no existing solution on such synchronisation. You  
> can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
> like done for SIP and MRCP, as at session level SIP and RTSP are  
> different instances that are not aware of each other. You could  
> "misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
> parameters for RTSP, or use the SDP "i=" line also with your own  
> paramentes, or define your own attribute line, e.g.  
> "a=stacksynch:whatever". However, all these are non-standard  
> solutions.
> KR,
> Teodora
>
> mmusic-request@ietf.org wrote:
>
>>
>> Message: 1
>> Date: Sun, 5 Feb 2006 09:41:06 +0200
>> From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Burger, Eric" <eburger@brooktrout.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	 
>> <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>>
>> What I'm trying to say is: why can't I use SIP for the call
>> establishment and RTSP for the stream control. How can synchronize  
>> two
>> protocols on the MRF side?
>> On the client side it is no problem, but server side should be aware
>> that two sessions are interconnected to the one specific call.
>>
>> Such synchronization I saw in the SIP/MRCP draft
>> (draft-ietf-speechsc-mrcpv2-09).
>>
>>
>> Thanks a lot
>>
>>
>> Osher
>>
>>
>> ________________________________
>>
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It
>> is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>> sessions.
>>
>>
>> ________________________________
>>
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf
>> Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>> synchronize the SIP and MRCP Sessios, defined
>>
>> a=channel:xxx
>>
>>
>> as part of application SDP.
>>
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the
>> Media Server layer without any indication.
>>
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync
>> between SIP and RTSP Streams.
>>
>>
>> Thanks a lot.
>>
>>
>> Osher
>>
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>> 20060205/0ce380c0/attachment.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 5 Feb 2006 08:17:22 -0500
>> From: "Burger, Eric" <eburger@brooktrout.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>> Content-Type: text/plain;	charset="iso-8859-1"
>>
>> That is something totally different and explicitly outside the  
>> scope of MRCPv2.  What you want is something like the mediactrl  
>> work (not chartered).  Search the I-D directory for mediactrl.  To  
>> subscribe, send 'subscribe mediactrl' to  
>> majordomo@lists.ubiquitysoftware.com
>>
>> ________________________________________
>> From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>> Sent: Sunday, February 05, 2006 2:41 AM
>> To: Burger, Eric
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> Hi,
>>
>> What I'm trying to say is: why can't I use SIP for the call  
>> establishment and RTSP for the stream control. How can synchronize  
>> two protocols on the MRF side? On the client side it is no  
>> problem, but server side should be aware that two sessions are  
>> interconnected to the one specific call.
>> Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>> speechsc-mrcpv2-09).
>>
>> Thanks a lot
>>
>> Osher
>>
>> ________________________________________
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>> has two, distinct sessions.
>>
>> ________________________________________
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>> to synchronize the SIP and MRCP Sessios, defined
>>       a=channel:xxx
>>       as part of application SDP.
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the Media Server layer without any indication.
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync between SIP and RTSP Streams.
>>
>> Thanks a lot.
>>
>> Osher
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> End of mmusic Digest, Vol 22, Issue 3
>> *************************************
>>
>
> -- 
> -----------------------------------------
> Teodora Guenkova-Luy
>
> Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
> 89069 Ulm, Germany
>
> Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>
> e-Mail: teodora.guenkova-luy@uni-ulm.de
>
> Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
> -----------------------------------------
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 06 10:02:03 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F67sR-0005Pv-GW; Mon, 06 Feb 2006 10:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F67sJ-0005Os-VY
	for mmusic@megatron.ietf.org; Mon, 06 Feb 2006 10:02:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25142
	for <mmusic@ietf.org>; Mon, 6 Feb 2006 10:00:02 -0500 (EST)
Received: from mail.icgcomm.com ([204.32.218.26] helo=denexg15.icgcomm.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F684J-0001Df-Jk
	for mmusic@ietf.org; Mon, 06 Feb 2006 10:14:21 -0500
Received: from Hagens1 ([10.138.85.33]) by denexg15.icgcomm.com with Microsoft
	SMTPSVC(6.0.3790.211); Mon, 6 Feb 2006 08:01:13 -0700
From: "Robert Hagens" <rhagens@envysion.com>
To: "'Colin Perkins'" <csp@csperkins.org>,
	"'Teodora Guenkova-Luy'" <teodora.guenkova-luy@uni-ulm.de>
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
Date: Mon, 6 Feb 2006 08:02:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYrBCNgaqZ7c4hlTr26PndhmTZ2NwAKbLIQ
In-Reply-To: <C5BEB600-A8B3-4865-A1B2-94EDCD178E6C@csperkins.org>
Message-ID: <DENEXG15zzlLT8UeYM700000565@denexg15.icgcomm.com>
X-OriginalArrivalTime: 06 Feb 2006 15:01:13.0356 (UTC)
	FILETIME=[2C0394C0:01C62B2E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org, Osher.Hmelnizky@audiocodes.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The other non-standard aspect of SIP/RTSP is that there is a good chuck of
overlap between SIP and RTSP. If you (for example) negotiate the SDP with
SIP, you really don't need to bother with the DESCRIBE and SETUP of RTSP.
After the SIP negotiation, you're ready to PLAY. This leads one to question
if all of the complexity of RTSP is required in these cases; a simpler
version of media control being desirable.

Rob

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: Monday, February 06, 2006 2:57 AM
To: Teodora Guenkova-Luy
Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

SDP has the concept of "m=control ..." to signal other control  
sessions. If one were to define how to signal RTSP sessions could be  
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for  
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
> SIP and RTSP are two different sessions. Their frameworks do not  
> exclude the scenario that both of them shall be synchronised,  
> however, there is no existing solution on such synchronisation. You  
> can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
> like done for SIP and MRCP, as at session level SIP and RTSP are  
> different instances that are not aware of each other. You could  
> "misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
> parameters for RTSP, or use the SDP "i=" line also with your own  
> paramentes, or define your own attribute line, e.g.  
> "a=stacksynch:whatever". However, all these are non-standard  
> solutions.
> KR,
> Teodora
>
> mmusic-request@ietf.org wrote:
>
>>
>> Message: 1
>> Date: Sun, 5 Feb 2006 09:41:06 +0200
>> From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Burger, Eric" <eburger@brooktrout.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	 
>> <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>>
>> What I'm trying to say is: why can't I use SIP for the call
>> establishment and RTSP for the stream control. How can synchronize  
>> two
>> protocols on the MRF side?
>> On the client side it is no problem, but server side should be aware
>> that two sessions are interconnected to the one specific call.
>>
>> Such synchronization I saw in the SIP/MRCP draft
>> (draft-ietf-speechsc-mrcpv2-09).
>>
>>
>> Thanks a lot
>>
>>
>> Osher
>>
>>
>> ________________________________
>>
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It
>> is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>> sessions.
>>
>>
>> ________________________________
>>
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf
>> Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>> synchronize the SIP and MRCP Sessios, defined
>>
>> a=channel:xxx
>>
>>
>> as part of application SDP.
>>
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the
>> Media Server layer without any indication.
>>
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync
>> between SIP and RTSP Streams.
>>
>>
>> Thanks a lot.
>>
>>
>> Osher
>>
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>> 20060205/0ce380c0/attachment.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 5 Feb 2006 08:17:22 -0500
>> From: "Burger, Eric" <eburger@brooktrout.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>> Content-Type: text/plain;	charset="iso-8859-1"
>>
>> That is something totally different and explicitly outside the  
>> scope of MRCPv2.  What you want is something like the mediactrl  
>> work (not chartered).  Search the I-D directory for mediactrl.  To  
>> subscribe, send 'subscribe mediactrl' to  
>> majordomo@lists.ubiquitysoftware.com
>>
>> ________________________________________
>> From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>> Sent: Sunday, February 05, 2006 2:41 AM
>> To: Burger, Eric
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> Hi,
>>
>> What I'm trying to say is: why can't I use SIP for the call  
>> establishment and RTSP for the stream control. How can synchronize  
>> two protocols on the MRF side? On the client side it is no  
>> problem, but server side should be aware that two sessions are  
>> interconnected to the one specific call.
>> Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>> speechsc-mrcpv2-09).
>>
>> Thanks a lot
>>
>> Osher
>>
>> ________________________________________
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>> has two, distinct sessions.
>>
>> ________________________________________
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>> to synchronize the SIP and MRCP Sessios, defined
>>       a=channel:xxx
>>       as part of application SDP.
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the Media Server layer without any indication.
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync between SIP and RTSP Streams.
>>
>> Thanks a lot.
>>
>> Osher
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> End of mmusic Digest, Vol 22, Issue 3
>> *************************************
>>
>
> -- 
> -----------------------------------------
> Teodora Guenkova-Luy
>
> Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
> 89069 Ulm, Germany
>
> Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>
> e-Mail: teodora.guenkova-luy@uni-ulm.de
>
> Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
> -----------------------------------------
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 07 03:01:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6NnE-00044j-Qn; Tue, 07 Feb 2006 03:01:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6NnD-00042Q-4k
	for mmusic@megatron.ietf.org; Tue, 07 Feb 2006 03:01:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00750
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 02:59:49 -0500 (EST)
Received: from mail1.audiocodes.com ([212.25.125.19] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6NzL-00058M-V9
	for mmusic@ietf.org; Tue, 07 Feb 2006 03:14:16 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Tue, 07 Feb 2006 11:10:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
Date: Tue, 7 Feb 2006 09:59:03 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD601C8A085@aclmsg.corp.audiocodes.com>
Thread-Topic: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
Thread-Index: AcYrBCNgaqZ7c4hlTr26PndhmTZ2NwAKbLIQACJ0zyA=
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
To: "Robert Hagens" <rhagens@envysion.com>,
	"Colin Perkins" <csp@csperkins.org>,
	"Teodora Guenkova-Luy" <teodora.guenkova-luy@uni-ulm.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3
Content-Transfer-Encoding: quoted-printable
Cc: mmusic@ietf.org, Oren Kudovitzky <Orenku@audiocodes.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi,

When I'm thinking on the Media server implementation in the IMS
architecture, it's clear that most of the SIP devices running over the
UDP for call establishment. Most of the xml-types streaming/media
controls over the SIP using INFO approaches. I'm not sure that this is a
right approach for real time streaming control (explicitly for video).
RTSP2 (the last draft) defines RTSP to use TCP as transport protocol.
TCP is the right approach for real time streaming control.

I adopt SIP/Info streaming control for announcement and recording, but
for real time stream control I think it's not enough, because of the big
delays when, for example Application Server should be involved in the
DTMF detection and creation of the appropriate control to the media
server.

SIP/MRCP2&RTSP seems me right approach for media server control. SIP for
session establishment and MRCP or RTSP for the streaming control and
media services.
I think it should be one common technique for synchronization between
SIP and other protocol like RTSP. It may be done using the SDP(for
example SIP/MRCP2).

Any thoughts?

Kind regards

Osher


-----Original Message-----
From: Robert Hagens [mailto:rhagens@envysion.com]=20
Sent: Monday, February 06, 2006 5:03 PM
To: 'Colin Perkins'; 'Teodora Guenkova-Luy'
Cc: mmusic@ietf.org; Osher Hmelnizky
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

The other non-standard aspect of SIP/RTSP is that there is a good chuck
of
overlap between SIP and RTSP. If you (for example) negotiate the SDP
with
SIP, you really don't need to bother with the DESCRIBE and SETUP of
RTSP.
After the SIP negotiation, you're ready to PLAY. This leads one to
question
if all of the complexity of RTSP is required in these cases; a simpler
version of media control being desirable.

Rob

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of
Colin Perkins
Sent: Monday, February 06, 2006 2:57 AM
To: Teodora Guenkova-Luy
Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

SDP has the concept of "m=3Dcontrol ..." to signal other control =20
sessions. If one were to define how to signal RTSP sessions could be =20
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for =20
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
> SIP and RTSP are two different sessions. Their frameworks do not =20
> exclude the scenario that both of them shall be synchronised, =20
> however, there is no existing solution on such synchronisation. You =20
> can synchronize SIP and RTSP only at presentation level (i.e. SDP), =20
> like done for SIP and MRCP, as at session level SIP and RTSP are =20
> different instances that are not aware of each other. You could =20
> "misuse" the SDP SIP/MRCP attribute "a=3Dchannel:xxx" with your own =20
> parameters for RTSP, or use the SDP "i=3D" line also with your own =20
> paramentes, or define your own attribute line, e.g. =20
> "a=3Dstacksynch:whatever". However, all these are non-standard =20
> solutions.
> KR,
> Teodora
>
> mmusic-request@ietf.org wrote:
>
>>
>> Message: 1
>> Date: Sun, 5 Feb 2006 09:41:06 +0200
>> From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Burger, Eric" <eburger@brooktrout.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	=20
>> <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>> Content-Type: text/plain; charset=3D"us-ascii"
>>
>> Hi,
>>
>>
>> What I'm trying to say is: why can't I use SIP for the call
>> establishment and RTSP for the stream control. How can synchronize =20
>> two
>> protocols on the MRF side?
>> On the client side it is no problem, but server side should be aware
>> that two sessions are interconnected to the one specific call.
>>
>> Such synchronization I saw in the SIP/MRCP draft
>> (draft-ietf-speechsc-mrcpv2-09).
>>
>>
>> Thanks a lot
>>
>>
>> Osher
>>
>>
>> ________________________________
>>
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday, =20
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>>
>> What are you trying to accomplish?  Two sessions are two =20
>> sessions.  It
>> is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>> sessions.
>>
>>
>> ________________________________
>>
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On =20
>> Behalf
>> Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>> synchronize the SIP and MRCP Sessios, defined
>>
>> a=3Dchannel:xxx
>>
>>
>> as part of application SDP.
>>
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams =20
>> at the
>> Media Server layer without any indication.
>>
>>
>> As a=3Dchannel defined at the SDP level can I use this parameter to =20
>> sync
>> between SIP and RTSP Streams.
>>
>>
>> Thanks a lot.
>>
>>
>> Osher
>>
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://www1.ietf.org/pipermail/mmusic/attachments/=20
>> 20060205/0ce380c0/attachment.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 5 Feb 2006 08:17:22 -0500
>> From: "Burger, Eric" <eburger@brooktrout.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>>
<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>> Content-Type: text/plain;	charset=3D"iso-8859-1"
>>
>> That is something totally different and explicitly outside the =20
>> scope of MRCPv2.  What you want is something like the mediactrl =20
>> work (not chartered).  Search the I-D directory for mediactrl.  To =20
>> subscribe, send 'subscribe mediactrl' to =20
>> majordomo@lists.ubiquitysoftware.com
>>
>> ________________________________________
>> From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com] =20
>> Sent: Sunday, February 05, 2006 2:41 AM
>> To: Burger, Eric
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> Hi,
>>
>> What I'm trying to say is: why can't I use SIP for the call =20
>> establishment and RTSP for the stream control. How can synchronize =20
>> two protocols on the MRF side? On the client side it is no =20
>> problem, but server side should be aware that two sessions are =20
>> interconnected to the one specific call.
>> Such synchronization I saw in the SIP/MRCP draft (draft-ietf-=20
>> speechsc-mrcpv2-09).
>>
>> Thanks a lot
>>
>> Osher
>>
>> ________________________________________
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday, =20
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> What are you trying to accomplish?  Two sessions are two =20
>> sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard) =20
>> has two, distinct sessions.
>>
>> ________________________________________
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On =20
>> Behalf Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order =20
>> to synchronize the SIP and MRCP Sessios, defined
>>       a=3Dchannel:xxx
>>       as part of application SDP.
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams =20
>> at the Media Server layer without any indication.
>>
>> As a=3Dchannel defined at the SDP level can I use this parameter to =20
>> sync between SIP and RTSP Streams.
>>
>> Thanks a lot.
>>
>> Osher
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> End of mmusic Digest, Vol 22, Issue 3
>> *************************************
>>
>
> --=20
> -----------------------------------------
> Teodora Guenkova-Luy
>
> Dept. Distributed Systems, University of Ulm, Oberer Eselsberg, =20
> 89069 Ulm, Germany
>
> Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>
> e-Mail: teodora.guenkova-luy@uni-ulm.de
>
> Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
> -----------------------------------------
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 07 07:22:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6RrW-0006Pg-LL; Tue, 07 Feb 2006 07:22:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6RrU-0006Di-Rx
	for mmusic@megatron.ietf.org; Tue, 07 Feb 2006 07:22:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18458
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 07:20:38 -0500 (EST)
Received: from mailrelay.swisscom-eurospot.com ([83.97.120.60]
	helo=safetwo.sceur.ch) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6S3b-0005q1-TS
	for mmusic@ietf.org; Tue, 07 Feb 2006 07:35:07 -0500
Received: from Pavillonquatre (unknown [212.180.35.242])
	by safetwo.sceur.ch (Postfix) with ESMTP id 2937B8DCF2
	for <mmusic@ietf.org>; Tue,  7 Feb 2006 12:21:46 +0000 (UTC)
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mmusic@ietf.org>
Date: Tue, 7 Feb 2006 13:21:32 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYr4Qdr+B8v9FrmTD64h1vKgbLgVA==
Message-Id: <20060207122146.2937B8DCF2@safetwo.sceur.ch>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Subject: [MMUSIC] Wireless/WiFi Convergence Conference - Paris - France
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1306433232=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1306433232==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0067_01C62BE9.697E5860"

This is a multi-part message in MIME format.

------=_NextPart_000_0067_01C62BE9.697E5860
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

UMA how? IMS when?

 

At the 2006 Wireless/WiFi Convergence Conference to be held in Paris on May
16 to May 19, distinguished experts and key players in the convergence field
will address technical issues. Carriers like BT, Orange, Vonage (etc) will
discuss their commercial experience and technological choices.

Get all details at:

 

 
<http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm>
http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm

 

 


------=_NextPart_000_0067_01C62BE9.697E5860
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>UMA how? IMS when?</span></font><font =
size=3D2><span
lang=3DEN-GB style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial'>At the 2006 Wireless/WiFi
Convergence Conference to be held in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>
on May 16 to May 19</span></font></b></strong><font size=3D2 =
face=3DArial><span
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:Arial'>, =
distinguished experts
and key players in the convergence field will address technical issues. =
Carriers
like BT, <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Orange</st1:City></st1:place>,
Vonage (etc) will discuss their commercial experience and technological
choices.</span></font><font size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Get all details at:</span></font><font =
size=3D2><span
lang=3DEN-GB style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006=
intro.htm"
title=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence200=
6intro.htm"><span
lang=3DEN-GB>http://www.upperside.fr/wirelessconvergence2006/wwconvergenc=
e2006intro.htm</span></a></span></font><font
size=3D2><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0067_01C62BE9.697E5860--



--===============1306433232==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============1306433232==--





From mmusic-bounces@ietf.org Tue Feb 07 08:42:07 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6T6c-0006LL-Pm; Tue, 07 Feb 2006 08:42:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6T6P-0006I8-Av
	for mmusic@megatron.ietf.org; Tue, 07 Feb 2006 08:41:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25950
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 08:40:04 -0500 (EST)
Received: from mail.uni-ulm.de ([134.60.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6TIf-0000Ci-Aj
	for mmusic@ietf.org; Tue, 07 Feb 2006 08:54:34 -0500
Received: from uni-ulm.de (discovery.informatik.uni-ulm.de [134.60.77.113])
	(authenticated bits=0)
	by mail.uni-ulm.de (8.13.4/8.13.4) with ESMTP id k17DfaL0014016
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 7 Feb 2006 14:41:37 +0100 (MET)
Message-ID: <43E8A464.8040107@uni-ulm.de>
Date: Tue, 07 Feb 2006 14:45:08 +0100
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Osher Hmelnizky <Osher.Hmelnizky@audiocodes.com>
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
References: <79B4F738DDD4EF4F85A4641A0FE5EFD601C8A085@aclmsg.corp.audiocodes.com>
In-Reply-To: <79B4F738DDD4EF4F85A4641A0FE5EFD601C8A085@aclmsg.corp.audiocodes.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9404aa2ccc871248c2288463bebdd6b9
Cc: Colin Perkins <csp@csperkins.org>, Oren Kudovitzky <Orenku@audiocodes.com>,
	mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1001167922=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1001167922==
Content-Type: multipart/alternative;
	boundary="------------090908080208030408050102"

This is a multi-part message in MIME format.
--------------090908080208030408050102
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dear Osher,
I see some problems with your task definition/requirements:
1. For real-time streaming you already have some kind of streaming 
control through RTCP (see also RFC 3551)
2. As SIP and RTSP are much more complex then the RTCP controls, they 
should be used only in cases that the application needs to adapt (i.e. 
to re-negotiate capabilities) and not for permanent monitoring/controls.
3. The classical TCP is not a solution when controlling mobile 
environments. It can be even an obstacle, when the underlying physical 
network is not faultless (e.g. thread failures due to carrier 
disruptions). The better solution is UDP (SIP), however, it is also not 
a perfect solution. The problem on this place is that the development of 
real-time applications considers currently only the media alone (i.e. 
aproaches like FEC, ARQ, etc.), what is not considered till now is that 
the controls for the real-time media are even more urgent then the media 
itself. SIP actually also does not provide a complete solution but 
refers to RFC 2914.
So if your media server does not care about the mobility of the clients, 
you can simplify your task and stick to TCP with both SIP and RTSP.
IMHO it is right to use SDP for signalling the association of the 
control sessions with SIP and RTSP. However, currently SDP does not 
really provide a specific solution for your problem and probably will 
not be further enhanced and developed in the future to provide a 
solution (see draft-ietf-mmusic-sdpng-trans-04).
So if you do not care about a standardized solution, but care about the 
faultlessness of your control signalling in non-mobile environments, you 
can use combinations of SIP (with TCP), RTSP and SDP and enhance them 
according to your needs using the respective enhancement mechanisms of 
these protocols. If you shall care about the clients mobility you have 
to stick to UDP (as carrier of SIP and RTSP) and ensure its 
faultlessness with e.g. DiffServ-like mechanisms.
KR,
Teodora

IMHO, SDP is the correct pla

Osher Hmelnizky wrote:

>Hi,
>
>When I'm thinking on the Media server implementation in the IMS
>architecture, it's clear that most of the SIP devices running over the
>UDP for call establishment. Most of the xml-types streaming/media
>controls over the SIP using INFO approaches. I'm not sure that this is a
>right approach for real time streaming control (explicitly for video).
>RTSP2 (the last draft) defines RTSP to use TCP as transport protocol.
>TCP is the right approach for real time streaming control.
>
>I adopt SIP/Info streaming control for announcement and recording, but
>for real time stream control I think it's not enough, because of the big
>delays when, for example Application Server should be involved in the
>DTMF detection and creation of the appropriate control to the media
>server.
>
>SIP/MRCP2&RTSP seems me right approach for media server control. SIP for
>session establishment and MRCP or RTSP for the streaming control and
>media services.
>I think it should be one common technique for synchronization between
>SIP and other protocol like RTSP. It may be done using the SDP(for
>example SIP/MRCP2).
>
>Any thoughts?
>
>Kind regards
>
>Osher
>
>
>-----Original Message-----
>From: Robert Hagens [mailto:rhagens@envysion.com] 
>Sent: Monday, February 06, 2006 5:03 PM
>To: 'Colin Perkins'; 'Teodora Guenkova-Luy'
>Cc: mmusic@ietf.org; Osher Hmelnizky
>Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
>
>The other non-standard aspect of SIP/RTSP is that there is a good chuck
>of
>overlap between SIP and RTSP. If you (for example) negotiate the SDP
>with
>SIP, you really don't need to bother with the DESCRIBE and SETUP of
>RTSP.
>After the SIP negotiation, you're ready to PLAY. This leads one to
>question
>if all of the complexity of RTSP is required in these cases; a simpler
>version of media control being desirable.
>
>Rob
>
>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>Of
>Colin Perkins
>Sent: Monday, February 06, 2006 2:57 AM
>To: Teodora Guenkova-Luy
>Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
>Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
>
>SDP has the concept of "m=control ..." to signal other control  
>sessions. If one were to define how to signal RTSP sessions could be  
>setup using SIP, that would likely be the appropriate way to do it.
>
>This subject comes up regularly - maybe it would be appropriate for  
>someone to write a draft fleshing out the details?
>
>Colin
>
>
>
>On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
>  
>
>>SIP and RTSP are two different sessions. Their frameworks do not  
>>exclude the scenario that both of them shall be synchronised,  
>>however, there is no existing solution on such synchronisation. You  
>>can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
>>like done for SIP and MRCP, as at session level SIP and RTSP are  
>>different instances that are not aware of each other. You could  
>>"misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
>>parameters for RTSP, or use the SDP "i=" line also with your own  
>>paramentes, or define your own attribute line, e.g.  
>>"a=stacksynch:whatever". However, all these are non-standard  
>>solutions.
>>KR,
>>Teodora
>>
>>mmusic-request@ietf.org wrote:
>>
>>    
>>
>>>Message: 1
>>>Date: Sun, 5 Feb 2006 09:41:06 +0200
>>>From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>To: "Burger, Eric" <eburger@brooktrout.com>
>>>Cc: mmusic@ietf.org
>>>Message-ID:
>>>	 
>>><79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>>>Content-Type: text/plain; charset="us-ascii"
>>>
>>>Hi,
>>>
>>>
>>>What I'm trying to say is: why can't I use SIP for the call
>>>establishment and RTSP for the stream control. How can synchronize  
>>>two
>>>protocols on the MRF side?
>>>On the client side it is no problem, but server side should be aware
>>>that two sessions are interconnected to the one specific call.
>>>
>>>Such synchronization I saw in the SIP/MRCP draft
>>>(draft-ietf-speechsc-mrcpv2-09).
>>>
>>>
>>>Thanks a lot
>>>
>>>
>>>Osher
>>>
>>>
>>>________________________________
>>>
>>>From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>>>February 03, 2006 4:34 AM
>>>To: Osher Hmelnizky
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>
>>>What are you trying to accomplish?  Two sessions are two  
>>>sessions.  It
>>>is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>>>sessions.
>>>
>>>
>>>________________________________
>>>
>>>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>>>Behalf
>>>Of Osher Hmelnizky
>>>Sent: Tuesday, January 10, 2006 7:26 AM
>>>To: mmusic@ietf.org
>>>Subject: [MMUSIC] Using RTSP with SIP
>>>
>>>
>>>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>>>synchronize the SIP and MRCP Sessios, defined
>>>
>>>a=channel:xxx
>>>
>>>
>>>as part of application SDP.
>>>
>>>
>>>I'm trying to find out how I can synchronize SIP and RTSP streams  
>>>at the
>>>Media Server layer without any indication.
>>>
>>>
>>>As a=channel defined at the SDP level can I use this parameter to  
>>>sync
>>>between SIP and RTSP Streams.
>>>
>>>
>>>Thanks a lot.
>>>
>>>
>>>Osher
>>>
>>>
>>>
>>>
>>>
>>>-------------- next part --------------
>>>An HTML attachment was scrubbed...
>>>URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>>>20060205/0ce380c0/attachment.htm
>>>
>>>------------------------------
>>>
>>>Message: 2
>>>Date: Sun, 5 Feb 2006 08:17:22 -0500
>>>From: "Burger, Eric" <eburger@brooktrout.com>
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>>>Cc: mmusic@ietf.org
>>>Message-ID:
>>>
>>>      
>>>
><330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>  
>
>>>Content-Type: text/plain;	charset="iso-8859-1"
>>>
>>>That is something totally different and explicitly outside the  
>>>scope of MRCPv2.  What you want is something like the mediactrl  
>>>work (not chartered).  Search the I-D directory for mediactrl.  To  
>>>subscribe, send 'subscribe mediactrl' to  
>>>majordomo@lists.ubiquitysoftware.com
>>>
>>>________________________________________
>>>From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>>>Sent: Sunday, February 05, 2006 2:41 AM
>>>To: Burger, Eric
>>>Cc: mmusic@ietf.org
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>Hi,
>>>
>>>What I'm trying to say is: why can't I use SIP for the call  
>>>establishment and RTSP for the stream control. How can synchronize  
>>>two protocols on the MRF side? On the client side it is no  
>>>problem, but server side should be aware that two sessions are  
>>>interconnected to the one specific call.
>>>Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>>>speechsc-mrcpv2-09).
>>>
>>>Thanks a lot
>>>
>>>Osher
>>>
>>>________________________________________
>>>From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>>>February 03, 2006 4:34 AM
>>>To: Osher Hmelnizky
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>What are you trying to accomplish?  Two sessions are two  
>>>sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>>>has two, distinct sessions.
>>>
>>>________________________________________
>>>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>>>Behalf Of Osher Hmelnizky
>>>Sent: Tuesday, January 10, 2006 7:26 AM
>>>To: mmusic@ietf.org
>>>Subject: [MMUSIC] Using RTSP with SIP
>>>
>>>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>>>to synchronize the SIP and MRCP Sessios, defined
>>>      a=channel:xxx
>>>      as part of application SDP.
>>>
>>>I'm trying to find out how I can synchronize SIP and RTSP streams  
>>>at the Media Server layer without any indication.
>>>
>>>As a=channel defined at the SDP level can I use this parameter to  
>>>sync between SIP and RTSP Streams.
>>>
>>>Thanks a lot.
>>>
>>>Osher
>>>
>>>
>>>
>>>
>>>
>>>
>>>------------------------------
>>>
>>>_______________________________________________
>>>mmusic mailing list
>>>mmusic@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>>End of mmusic Digest, Vol 22, Issue 3
>>>*************************************
>>>
>>>      
>>>
>>-- 
>>-----------------------------------------
>>Teodora Guenkova-Luy
>>
>>Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
>>89069 Ulm, Germany
>>
>>Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>>
>>e-Mail: teodora.guenkova-luy@uni-ulm.de
>>
>>Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
>>-----------------------------------------
>>
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic
>>    
>>
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>
>  
>

-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/ 

-----------------------------------------


--------------090908080208030408050102
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Dear Osher,<br>
I see some problems with your task definition/requirements:<br>
1. For real-time streaming you already have some kind of streaming
control through RTCP (see also RFC 3551)<br>
2. As SIP and RTSP are much more complex then the RTCP controls, they
should be used only in cases that the application needs to adapt (i.e.
to re-negotiate capabilities) and not for permanent monitoring/controls.<br>
3. The classical TCP is not a solution when controlling mobile
environments. It can be even an obstacle, when the underlying physical
network is not faultless (e.g. thread failures due to carrier
disruptions). The better solution is UDP (SIP), however, it is also not
a perfect solution. The problem on this place is that the development
of real-time applications considers currently only the media alone
(i.e. aproaches like FEC, ARQ, etc.), what is not considered till now
is that the controls for the real-time media are even more urgent then
the media itself. SIP actually also does not provide a complete
solution but refers to RFC 2914.<br>
So if your media server does not care about the mobility of the
clients, you can simplify your task and stick to TCP with both SIP and
RTSP.<br>
IMHO it is right to use SDP for signalling the association of the
control sessions with SIP and RTSP. However, currently SDP does not
really provide a specific solution for your problem and probably will
not be further enhanced and developed in the future to provide a
solution (see draft-ietf-mmusic-sdpng-trans-04).<br>
So if you do not care about a standardized solution, but care about the
faultlessness of your control signalling in non-mobile environments,
you can use combinations of SIP (with TCP), RTSP and SDP and enhance
them according to your needs using the respective enhancement
mechanisms of these protocols. If you shall care about the clients
mobility you have to stick to UDP (as carrier of SIP and RTSP) and
ensure its faultlessness with e.g. DiffServ-like mechanisms.<br>
KR,<br>
Teodora <br>
<br>
IMHO, SDP is the correct pla<br>
<br>
Osher Hmelnizky wrote:<br>
<blockquote type="cite"
 cite="mid79B4F738DDD4EF4F85A4641A0FE5EFD601C8A085@aclmsg.corp.audiocodes.com">
  <pre wrap="">Hi,

When I'm thinking on the Media server implementation in the IMS
architecture, it's clear that most of the SIP devices running over the
UDP for call establishment. Most of the xml-types streaming/media
controls over the SIP using INFO approaches. I'm not sure that this is a
right approach for real time streaming control (explicitly for video).
RTSP2 (the last draft) defines RTSP to use TCP as transport protocol.
TCP is the right approach for real time streaming control.

I adopt SIP/Info streaming control for announcement and recording, but
for real time stream control I think it's not enough, because of the big
delays when, for example Application Server should be involved in the
DTMF detection and creation of the appropriate control to the media
server.

SIP/MRCP2&amp;RTSP seems me right approach for media server control. SIP for
session establishment and MRCP or RTSP for the streaming control and
media services.
I think it should be one common technique for synchronization between
SIP and other protocol like RTSP. It may be done using the SDP(for
example SIP/MRCP2).

Any thoughts?

Kind regards

Osher


-----Original Message-----
From: Robert Hagens [<a class="moz-txt-link-freetext" href="mailto:rhagens@envysion.com">mailto:rhagens@envysion.com</a>] 
Sent: Monday, February 06, 2006 5:03 PM
To: 'Colin Perkins'; 'Teodora Guenkova-Luy'
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>; Osher Hmelnizky
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

The other non-standard aspect of SIP/RTSP is that there is a good chuck
of
overlap between SIP and RTSP. If you (for example) negotiate the SDP
with
SIP, you really don't need to bother with the DESCRIBE and SETUP of
RTSP.
After the SIP negotiation, you're ready to PLAY. This leads one to
question
if all of the complexity of RTSP is required in these cases; a simpler
version of media control being desirable.

Rob

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>] On Behalf
Of
Colin Perkins
Sent: Monday, February 06, 2006 2:57 AM
To: Teodora Guenkova-Luy
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:Osher.Hmelnizky@audiocodes.com">Osher.Hmelnizky@audiocodes.com</a>
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

SDP has the concept of "m=control ..." to signal other control  
sessions. If one were to define how to signal RTSP sessions could be  
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for  
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">SIP and RTSP are two different sessions. Their frameworks do not  
exclude the scenario that both of them shall be synchronised,  
however, there is no existing solution on such synchronisation. You  
can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
like done for SIP and MRCP, as at session level SIP and RTSP are  
different instances that are not aware of each other. You could  
"misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
parameters for RTSP, or use the SDP "i=" line also with your own  
paramentes, or define your own attribute line, e.g.  
"a=stacksynch:whatever". However, all these are non-standard  
solutions.
KR,
Teodora

<a class="moz-txt-link-abbreviated" href="mailto:mmusic-request@ietf.org">mmusic-request@ietf.org</a> wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">Message: 1
Date: Sun, 5 Feb 2006 09:41:06 +0200
From: "Osher Hmelnizky" <a class="moz-txt-link-rfc2396E" href="mailto:Osher.Hmelnizky@audiocodes.com">&lt;Osher.Hmelnizky@audiocodes.com&gt;</a>
Subject: RE: [MMUSIC] Using RTSP with SIP
To: "Burger, Eric" <a class="moz-txt-link-rfc2396E" href="mailto:eburger@brooktrout.com">&lt;eburger@brooktrout.com&gt;</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Message-ID:
	 
<a class="moz-txt-link-rfc2396E" href="mailto:79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com">&lt;79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com&gt;</a>
Content-Type: text/plain; charset="us-ascii"

Hi,


What I'm trying to say is: why can't I use SIP for the call
establishment and RTSP for the stream control. How can synchronize  
two
protocols on the MRF side?
On the client side it is no problem, but server side should be aware
that two sessions are interconnected to the one specific call.

Such synchronization I saw in the SIP/MRCP draft
(draft-ietf-speechsc-mrcpv2-09).


Thanks a lot


Osher


________________________________

From: Burger, Eric [<a class="moz-txt-link-freetext" href="mailto:eburger@brooktrout.com">mailto:eburger@brooktrout.com</a>] Sent: Friday,  
February 03, 2006 4:34 AM
To: Osher Hmelnizky
Subject: RE: [MMUSIC] Using RTSP with SIP


What are you trying to accomplish?  Two sessions are two  
sessions.  It
is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
sessions.


________________________________

From: <a class="moz-txt-link-abbreviated" href="mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>] On  
Behalf
Of Osher Hmelnizky
Sent: Tuesday, January 10, 2006 7:26 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Subject: [MMUSIC] Using RTSP with SIP


In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
synchronize the SIP and MRCP Sessios, defined

a=channel:xxx


as part of application SDP.


I'm trying to find out how I can synchronize SIP and RTSP streams  
at the
Media Server layer without any indication.


As a=channel defined at the SDP level can I use this parameter to  
sync
between SIP and RTSP Streams.


Thanks a lot.


Osher





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="moz-txt-link-freetext" href="http://www1.ietf.org/pipermail/mmusic/attachments/">http://www1.ietf.org/pipermail/mmusic/attachments/</a> 
20060205/0ce380c0/attachment.htm

------------------------------

Message: 2
Date: Sun, 5 Feb 2006 08:17:22 -0500
From: "Burger, Eric" <a class="moz-txt-link-rfc2396E" href="mailto:eburger@brooktrout.com">&lt;eburger@brooktrout.com&gt;</a>
Subject: RE: [MMUSIC] Using RTSP with SIP
To: "Osher Hmelnizky" <a class="moz-txt-link-rfc2396E" href="mailto:Osher.Hmelnizky@audiocodes.com">&lt;Osher.Hmelnizky@audiocodes.com&gt;</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Message-ID:

      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!----><a class="moz-txt-link-rfc2396E" href="mailto:330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com">&lt;330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com&gt;</a>
  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">Content-Type: text/plain;	charset="iso-8859-1"

That is something totally different and explicitly outside the  
scope of MRCPv2.  What you want is something like the mediactrl  
work (not chartered).  Search the I-D directory for mediactrl.  To  
subscribe, send 'subscribe mediactrl' to  
<a class="moz-txt-link-abbreviated" href="mailto:majordomo@lists.ubiquitysoftware.com">majordomo@lists.ubiquitysoftware.com</a>

________________________________________
From: Osher Hmelnizky [<a class="moz-txt-link-freetext" href="mailto:Osher.Hmelnizky@audiocodes.com">mailto:Osher.Hmelnizky@audiocodes.com</a>]  
Sent: Sunday, February 05, 2006 2:41 AM
To: Burger, Eric
Cc: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Subject: RE: [MMUSIC] Using RTSP with SIP

Hi,

What I'm trying to say is: why can't I use SIP for the call  
establishment and RTSP for the stream control. How can synchronize  
two protocols on the MRF side? On the client side it is no  
problem, but server side should be aware that two sessions are  
interconnected to the one specific call.
Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
speechsc-mrcpv2-09).

Thanks a lot

Osher

________________________________________
From: Burger, Eric [<a class="moz-txt-link-freetext" href="mailto:eburger@brooktrout.com">mailto:eburger@brooktrout.com</a>] Sent: Friday,  
February 03, 2006 4:34 AM
To: Osher Hmelnizky
Subject: RE: [MMUSIC] Using RTSP with SIP

What are you trying to accomplish?  Two sessions are two  
sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
has two, distinct sessions.

________________________________________
From: <a class="moz-txt-link-abbreviated" href="mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>] On  
Behalf Of Osher Hmelnizky
Sent: Tuesday, January 10, 2006 7:26 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
Subject: [MMUSIC] Using RTSP with SIP

In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
to synchronize the SIP and MRCP Sessios, defined
      a=channel:xxx
      as part of application SDP.

I'm trying to find out how I can synchronize SIP and RTSP streams  
at the Media Server layer without any indication.

As a=channel defined at the SDP level can I use this parameter to  
sync between SIP and RTSP Streams.

Thanks a lot.

Osher






------------------------------

_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/mmusic">https://www1.ietf.org/mailman/listinfo/mmusic</a>


End of mmusic Digest, Vol 22, Issue 3
*************************************

      </pre>
    </blockquote>
    <pre wrap="">-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142

e-Mail: <a class="moz-txt-link-abbreviated" href="mailto:teodora.guenkova-luy@uni-ulm.de">teodora.guenkova-luy@uni-ulm.de</a>

Home Page: <a class="moz-txt-link-freetext" href="http://www-vs.informatik.uni-ulm.de/~Guenkova/">http://www-vs.informatik.uni-ulm.de/~Guenkova/</a>
-----------------------------------------



_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/mmusic">https://www1.ietf.org/mailman/listinfo/mmusic</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->

_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/mmusic">https://www1.ietf.org/mailman/listinfo/mmusic</a>

  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: <a class="moz-txt-link-abbreviated" href="mailto:teodora.guenkova-luy@uni-ulm.de">teodora.guenkova-luy@uni-ulm.de</a>

Home Page: <a class="moz-txt-link-freetext" href="http://www-vs.informatik.uni-ulm.de/~Guenkova/">http://www-vs.informatik.uni-ulm.de/~Guenkova/</a> 

-----------------------------------------</pre>
</body>
</html>

--------------090908080208030408050102--



--===============1001167922==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============1001167922==--





From mmusic-bounces@ietf.org Tue Feb 07 09:23:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6TkU-00045l-OP; Tue, 07 Feb 2006 09:23:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6TkO-00043V-W7
	for mmusic@megatron.ietf.org; Tue, 07 Feb 2006 09:23:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29121
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 09:21:21 -0500 (EST)
From: steven.d.whitehead@verizon.com
Received: from irvmail2.verizon.com ([192.76.80.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6Twa-0001cX-Rj
	for mmusic@ietf.org; Tue, 07 Feb 2006 09:35:52 -0500
Received: from smtpirv2.verizon.com (smtpirv2.verizon.com [138.83.34.66])
	by irvmail2.verizon.com (8.13.3/8.13.3) with ESMTP id k17EMhgt022141
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 09:22:43 -0500 (EST)
Received: from irvp1cvmma01.vzh.ent.verizon.com (irvp1cvmma01.verizon.com
	[138.83.34.82])
	by smtpirv2.verizon.com (8.13.3/8.13.3) with ESMTP id k17ELXAl028601
	for <mmusic@ietf.org>; Tue, 7 Feb 2006 08:21:33 -0600 (CST)
Received: from 138.83.34.22 by irvp1cvmma01.vzh.ent.verizon.com with
	ESMTP (SMTP Relay); Tue, 07 Feb 2006 09:22:28 -0500
X-Server-Uuid: 33D99CC3-91DD-4C5F-B3C4-DE0A72F86AF5
Received: from dwsmtp01.core.verizon.com (dwsmtp01.verizon.com
	[138.83.35.62]) by coregate1.verizon.com (8.13.3/8.13.3) with ESMTP id
	k17EMSrR017826 for <mmusic@ietf.org>; Tue, 7 Feb 2006 08:22:28 -0600 (
	CST)
Date: Tue, 7 Feb 2006 09:22:28 -0500
MIME-Version: 1.0
To: mmusic@ietf.org
X-Mailer: Microsoft Outlook v 11.00.6353, MSOC v 2.00.4007.00
Message-ID: <OF4E86336A.63343BF2-ON0525710E.004E3C20@CORE.VERIZON.COM>
X-MIMETrack: Serialize by Router on DWSMTP01/HSVR/Verizon(Release
	6.5.4HF453 | August 4, 2005) at 02/07/2006 08:22:28, Serialize complete
	at 02/07/2006 08:22:28
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-WSS-ID: 6FF672AE67W76349-01-01
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c5b976cb26c967a52d72d6069c7fc54c
Content-Transfer-Encoding: 7bit
Cc: mmontpetit@motorola.com
Subject: [MMUSIC] SIP/RTSP interworking
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

I, along with Marie Montpetit, am putting together a draft that aims to
address SIP/RTSP interworking. 

The draft will have two main parts: part 1 discusses the rationale for
SIP/RTSP interworking and part 2 enumerates design options for SIP/RTSP
interworking. 

The goal is to get it out in time for discussion at the next IETF meeting.
Ultimately, we'd like mmusic (or other appropriate group) to pick up this
topic as work item. 

If you're interested in contributing to the draft, please let me know.

Thanks,
-Steve

 

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of mmusic-request@ietf.org
Sent: Tuesday, February 07, 2006 8:46 AM
To: mmusic@ietf.org
Subject: mmusic Digest, Vol 22, Issue 5

Send mmusic mailing list submissions to
	mmusic@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/mmusic
or, via email, send a message with subject or body 'help' to
	mmusic-request@ietf.org

You can reach the person managing the list at
	mmusic-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of mmusic digest..."


Today's Topics:

   1. RE: Re: mmusic Digest, Vol 22, Issue 3 (Osher Hmelnizky)
   2. Wireless/WiFi Convergence Conference - Paris - France
      (Chantal Ladouce)
   3. Re: Re: mmusic Digest, Vol 22, Issue 3 (Teodora Guenkova-Luy)


----------------------------------------------------------------------

Message: 1
Date: Tue, 7 Feb 2006 09:59:03 +0200
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
To: "Robert Hagens" <rhagens@envysion.com>,	"Colin Perkins"
	<csp@csperkins.org>,	"Teodora Guenkova-Luy"
	<teodora.guenkova-luy@uni-ulm.de>
Cc: mmusic@ietf.org, Oren Kudovitzky <Orenku@audiocodes.com>
Message-ID:
	
<79B4F738DDD4EF4F85A4641A0FE5EFD601C8A085@aclmsg.corp.audiocodes.com>
Content-Type: text/plain;	charset="us-ascii"

Hi,

When I'm thinking on the Media server implementation in the IMS
architecture, it's clear that most of the SIP devices running over the
UDP for call establishment. Most of the xml-types streaming/media
controls over the SIP using INFO approaches. I'm not sure that this is a
right approach for real time streaming control (explicitly for video).
RTSP2 (the last draft) defines RTSP to use TCP as transport protocol.
TCP is the right approach for real time streaming control.

I adopt SIP/Info streaming control for announcement and recording, but
for real time stream control I think it's not enough, because of the big
delays when, for example Application Server should be involved in the
DTMF detection and creation of the appropriate control to the media
server.

SIP/MRCP2&RTSP seems me right approach for media server control. SIP for
session establishment and MRCP or RTSP for the streaming control and
media services.
I think it should be one common technique for synchronization between
SIP and other protocol like RTSP. It may be done using the SDP(for
example SIP/MRCP2).

Any thoughts?

Kind regards

Osher


-----Original Message-----
From: Robert Hagens [mailto:rhagens@envysion.com] 
Sent: Monday, February 06, 2006 5:03 PM
To: 'Colin Perkins'; 'Teodora Guenkova-Luy'
Cc: mmusic@ietf.org; Osher Hmelnizky
Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

The other non-standard aspect of SIP/RTSP is that there is a good chuck
of
overlap between SIP and RTSP. If you (for example) negotiate the SDP
with
SIP, you really don't need to bother with the DESCRIBE and SETUP of
RTSP.
After the SIP negotiation, you're ready to PLAY. This leads one to
question
if all of the complexity of RTSP is required in these cases; a simpler
version of media control being desirable.

Rob

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of
Colin Perkins
Sent: Monday, February 06, 2006 2:57 AM
To: Teodora Guenkova-Luy
Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

SDP has the concept of "m=control ..." to signal other control  
sessions. If one were to define how to signal RTSP sessions could be  
setup using SIP, that would likely be the appropriate way to do it.

This subject comes up regularly - maybe it would be appropriate for  
someone to write a draft fleshing out the details?

Colin



On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
> SIP and RTSP are two different sessions. Their frameworks do not  
> exclude the scenario that both of them shall be synchronised,  
> however, there is no existing solution on such synchronisation. You  
> can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
> like done for SIP and MRCP, as at session level SIP and RTSP are  
> different instances that are not aware of each other. You could  
> "misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
> parameters for RTSP, or use the SDP "i=" line also with your own  
> paramentes, or define your own attribute line, e.g.  
> "a=stacksynch:whatever". However, all these are non-standard  
> solutions.
> KR,
> Teodora
>
> mmusic-request@ietf.org wrote:
>
>>
>> Message: 1
>> Date: Sun, 5 Feb 2006 09:41:06 +0200
>> From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Burger, Eric" <eburger@brooktrout.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>> 	 
>> <79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>>
>> What I'm trying to say is: why can't I use SIP for the call
>> establishment and RTSP for the stream control. How can synchronize  
>> two
>> protocols on the MRF side?
>> On the client side it is no problem, but server side should be aware
>> that two sessions are interconnected to the one specific call.
>>
>> Such synchronization I saw in the SIP/MRCP draft
>> (draft-ietf-speechsc-mrcpv2-09).
>>
>>
>> Thanks a lot
>>
>>
>> Osher
>>
>>
>> ________________________________
>>
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It
>> is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>> sessions.
>>
>>
>> ________________________________
>>
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf
>> Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>> synchronize the SIP and MRCP Sessios, defined
>>
>> a=channel:xxx
>>
>>
>> as part of application SDP.
>>
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the
>> Media Server layer without any indication.
>>
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync
>> between SIP and RTSP Streams.
>>
>>
>> Thanks a lot.
>>
>>
>> Osher
>>
>>
>>
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>> 20060205/0ce380c0/attachment.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 5 Feb 2006 08:17:22 -0500
>> From: "Burger, Eric" <eburger@brooktrout.com>
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>> To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>> Cc: mmusic@ietf.org
>> Message-ID:
>>
<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>> Content-Type: text/plain;	charset="iso-8859-1"
>>
>> That is something totally different and explicitly outside the  
>> scope of MRCPv2.  What you want is something like the mediactrl  
>> work (not chartered).  Search the I-D directory for mediactrl.  To  
>> subscribe, send 'subscribe mediactrl' to  
>> majordomo@lists.ubiquitysoftware.com
>>
>> ________________________________________
>> From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>> Sent: Sunday, February 05, 2006 2:41 AM
>> To: Burger, Eric
>> Cc: mmusic@ietf.org
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> Hi,
>>
>> What I'm trying to say is: why can't I use SIP for the call  
>> establishment and RTSP for the stream control. How can synchronize  
>> two protocols on the MRF side? On the client side it is no  
>> problem, but server side should be aware that two sessions are  
>> interconnected to the one specific call.
>> Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>> speechsc-mrcpv2-09).
>>
>> Thanks a lot
>>
>> Osher
>>
>> ________________________________________
>> From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>> February 03, 2006 4:34 AM
>> To: Osher Hmelnizky
>> Subject: RE: [MMUSIC] Using RTSP with SIP
>>
>> What are you trying to accomplish?  Two sessions are two  
>> sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>> has two, distinct sessions.
>>
>> ________________________________________
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf Of Osher Hmelnizky
>> Sent: Tuesday, January 10, 2006 7:26 AM
>> To: mmusic@ietf.org
>> Subject: [MMUSIC] Using RTSP with SIP
>>
>> In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>> to synchronize the SIP and MRCP Sessios, defined
>>       a=channel:xxx
>>       as part of application SDP.
>>
>> I'm trying to find out how I can synchronize SIP and RTSP streams  
>> at the Media Server layer without any indication.
>>
>> As a=channel defined at the SDP level can I use this parameter to  
>> sync between SIP and RTSP Streams.
>>
>> Thanks a lot.
>>
>> Osher
>>
>>
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> End of mmusic Digest, Vol 22, Issue 3
>> *************************************
>>
>
> -- 
> -----------------------------------------
> Teodora Guenkova-Luy
>
> Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
> 89069 Ulm, Germany
>
> Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>
> e-Mail: teodora.guenkova-luy@uni-ulm.de
>
> Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
> -----------------------------------------
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic




------------------------------

Message: 2
Date: Tue, 7 Feb 2006 13:21:32 +0100
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
Subject: [MMUSIC] Wireless/WiFi Convergence Conference - Paris -
	France
To: <mmusic@ietf.org>
Message-ID: <20060207122146.2937B8DCF2@safetwo.sceur.ch>
Content-Type: text/plain; charset="us-ascii"

UMA how? IMS when?

 

At the 2006 Wireless/WiFi Convergence Conference to be held in Paris on
May
16 to May 19, distinguished experts and key players in the convergence
field
will address technical issues. Carriers like BT, Orange, Vonage (etc) will
discuss their commercial experience and technological choices.

Get all details at:

 

 
<http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.ht
m>
http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/mmusic/attachments/20060207/49faad4d/attach
ment.htm

------------------------------

Message: 3
Date: Tue, 07 Feb 2006 14:45:08 +0100
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
To: Osher Hmelnizky <Osher.Hmelnizky@audiocodes.com>
Cc: Colin Perkins <csp@csperkins.org>, Oren Kudovitzky
	<Orenku@audiocodes.com>,	mmusic@ietf.org
Message-ID: <43E8A464.8040107@uni-ulm.de>
Content-Type: text/plain; charset="us-ascii"

Dear Osher,
I see some problems with your task definition/requirements:
1. For real-time streaming you already have some kind of streaming 
control through RTCP (see also RFC 3551)
2. As SIP and RTSP are much more complex then the RTCP controls, they 
should be used only in cases that the application needs to adapt (i.e. 
to re-negotiate capabilities) and not for permanent monitoring/controls.
3. The classical TCP is not a solution when controlling mobile 
environments. It can be even an obstacle, when the underlying physical 
network is not faultless (e.g. thread failures due to carrier 
disruptions). The better solution is UDP (SIP), however, it is also not 
a perfect solution. The problem on this place is that the development of 
real-time applications considers currently only the media alone (i.e. 
aproaches like FEC, ARQ, etc.), what is not considered till now is that 
the controls for the real-time media are even more urgent then the media 
itself. SIP actually also does not provide a complete solution but 
refers to RFC 2914.
So if your media server does not care about the mobility of the clients, 
you can simplify your task and stick to TCP with both SIP and RTSP.
IMHO it is right to use SDP for signalling the association of the 
control sessions with SIP and RTSP. However, currently SDP does not 
really provide a specific solution for your problem and probably will 
not be further enhanced and developed in the future to provide a 
solution (see draft-ietf-mmusic-sdpng-trans-04).
So if you do not care about a standardized solution, but care about the 
faultlessness of your control signalling in non-mobile environments, you 
can use combinations of SIP (with TCP), RTSP and SDP and enhance them 
according to your needs using the respective enhancement mechanisms of 
these protocols. If you shall care about the clients mobility you have 
to stick to UDP (as carrier of SIP and RTSP) and ensure its 
faultlessness with e.g. DiffServ-like mechanisms.
KR,
Teodora

IMHO, SDP is the correct pla

Osher Hmelnizky wrote:

>Hi,
>
>When I'm thinking on the Media server implementation in the IMS
>architecture, it's clear that most of the SIP devices running over the
>UDP for call establishment. Most of the xml-types streaming/media
>controls over the SIP using INFO approaches. I'm not sure that this is a
>right approach for real time streaming control (explicitly for video).
>RTSP2 (the last draft) defines RTSP to use TCP as transport protocol.
>TCP is the right approach for real time streaming control.
>
>I adopt SIP/Info streaming control for announcement and recording, but
>for real time stream control I think it's not enough, because of the big
>delays when, for example Application Server should be involved in the
>DTMF detection and creation of the appropriate control to the media
>server.
>
>SIP/MRCP2&RTSP seems me right approach for media server control. SIP for
>session establishment and MRCP or RTSP for the streaming control and
>media services.
>I think it should be one common technique for synchronization between
>SIP and other protocol like RTSP. It may be done using the SDP(for
>example SIP/MRCP2).
>
>Any thoughts?
>
>Kind regards
>
>Osher
>
>
>-----Original Message-----
>From: Robert Hagens [mailto:rhagens@envysion.com] 
>Sent: Monday, February 06, 2006 5:03 PM
>To: 'Colin Perkins'; 'Teodora Guenkova-Luy'
>Cc: mmusic@ietf.org; Osher Hmelnizky
>Subject: RE: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
>
>The other non-standard aspect of SIP/RTSP is that there is a good chuck
>of
>overlap between SIP and RTSP. If you (for example) negotiate the SDP
>with
>SIP, you really don't need to bother with the DESCRIBE and SETUP of
>RTSP.
>After the SIP negotiation, you're ready to PLAY. This leads one to
>question
>if all of the complexity of RTSP is required in these cases; a simpler
>version of media control being desirable.
>
>Rob
>
>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>Of
>Colin Perkins
>Sent: Monday, February 06, 2006 2:57 AM
>To: Teodora Guenkova-Luy
>Cc: mmusic@ietf.org; Osher.Hmelnizky@audiocodes.com
>Subject: Re: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
>
>SDP has the concept of "m=control ..." to signal other control  
>sessions. If one were to define how to signal RTSP sessions could be  
>setup using SIP, that would likely be the appropriate way to do it.
>
>This subject comes up regularly - maybe it would be appropriate for  
>someone to write a draft fleshing out the details?
>
>Colin
>
>
>
>On 6 Feb 2006, at 09:48, Teodora Guenkova-Luy wrote:
>  
>
>>SIP and RTSP are two different sessions. Their frameworks do not  
>>exclude the scenario that both of them shall be synchronised,  
>>however, there is no existing solution on such synchronisation. You  
>>can synchronize SIP and RTSP only at presentation level (i.e. SDP),  
>>like done for SIP and MRCP, as at session level SIP and RTSP are  
>>different instances that are not aware of each other. You could  
>>"misuse" the SDP SIP/MRCP attribute "a=channel:xxx" with your own  
>>parameters for RTSP, or use the SDP "i=" line also with your own  
>>paramentes, or define your own attribute line, e.g.  
>>"a=stacksynch:whatever". However, all these are non-standard  
>>solutions.
>>KR,
>>Teodora
>>
>>mmusic-request@ietf.org wrote:
>>
>>    
>>
>>>Message: 1
>>>Date: Sun, 5 Feb 2006 09:41:06 +0200
>>>From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>To: "Burger, Eric" <eburger@brooktrout.com>
>>>Cc: mmusic@ietf.org
>>>Message-ID:
>>>	 
>>><79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>>>Content-Type: text/plain; charset="us-ascii"
>>>
>>>Hi,
>>>
>>>
>>>What I'm trying to say is: why can't I use SIP for the call
>>>establishment and RTSP for the stream control. How can synchronize  
>>>two
>>>protocols on the MRF side?
>>>On the client side it is no problem, but server side should be aware
>>>that two sessions are interconnected to the one specific call.
>>>
>>>Such synchronization I saw in the SIP/MRCP draft
>>>(draft-ietf-speechsc-mrcpv2-09).
>>>
>>>
>>>Thanks a lot
>>>
>>>
>>>Osher
>>>
>>>
>>>________________________________
>>>
>>>From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>>>February 03, 2006 4:34 AM
>>>To: Osher Hmelnizky
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>
>>>What are you trying to accomplish?  Two sessions are two  
>>>sessions.  It
>>>is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>>>sessions.
>>>
>>>
>>>________________________________
>>>
>>>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>>>Behalf
>>>Of Osher Hmelnizky
>>>Sent: Tuesday, January 10, 2006 7:26 AM
>>>To: mmusic@ietf.org
>>>Subject: [MMUSIC] Using RTSP with SIP
>>>
>>>
>>>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>>>synchronize the SIP and MRCP Sessios, defined
>>>
>>>a=channel:xxx
>>>
>>>
>>>as part of application SDP.
>>>
>>>
>>>I'm trying to find out how I can synchronize SIP and RTSP streams  
>>>at the
>>>Media Server layer without any indication.
>>>
>>>
>>>As a=channel defined at the SDP level can I use this parameter to  
>>>sync
>>>between SIP and RTSP Streams.
>>>
>>>
>>>Thanks a lot.
>>>
>>>
>>>Osher
>>>
>>>
>>>
>>>
>>>
>>>-------------- next part --------------
>>>An HTML attachment was scrubbed...
>>>URL: http://www1.ietf.org/pipermail/mmusic/attachments/ 
>>>20060205/0ce380c0/attachment.htm
>>>
>>>------------------------------
>>>
>>>Message: 2
>>>Date: Sun, 5 Feb 2006 08:17:22 -0500
>>>From: "Burger, Eric" <eburger@brooktrout.com>
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>>>Cc: mmusic@ietf.org
>>>Message-ID:
>>>
>>>      
>>>
><330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>  
>
>>>Content-Type: text/plain;	charset="iso-8859-1"
>>>
>>>That is something totally different and explicitly outside the  
>>>scope of MRCPv2.  What you want is something like the mediactrl  
>>>work (not chartered).  Search the I-D directory for mediactrl.  To  
>>>subscribe, send 'subscribe mediactrl' to  
>>>majordomo@lists.ubiquitysoftware.com
>>>
>>>________________________________________
>>>From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com]  
>>>Sent: Sunday, February 05, 2006 2:41 AM
>>>To: Burger, Eric
>>>Cc: mmusic@ietf.org
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>Hi,
>>>
>>>What I'm trying to say is: why can't I use SIP for the call  
>>>establishment and RTSP for the stream control. How can synchronize  
>>>two protocols on the MRF side? On the client side it is no  
>>>problem, but server side should be aware that two sessions are  
>>>interconnected to the one specific call.
>>>Such synchronization I saw in the SIP/MRCP draft (draft-ietf- 
>>>speechsc-mrcpv2-09).
>>>
>>>Thanks a lot
>>>
>>>Osher
>>>
>>>________________________________________
>>>From: Burger, Eric [mailto:eburger@brooktrout.com] Sent: Friday,  
>>>February 03, 2006 4:34 AM
>>>To: Osher Hmelnizky
>>>Subject: RE: [MMUSIC] Using RTSP with SIP
>>>
>>>What are you trying to accomplish?  Two sessions are two  
>>>sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard)  
>>>has two, distinct sessions.
>>>
>>>________________________________________
>>>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>>>Behalf Of Osher Hmelnizky
>>>Sent: Tuesday, January 10, 2006 7:26 AM
>>>To: mmusic@ietf.org
>>>Subject: [MMUSIC] Using RTSP with SIP
>>>
>>>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order  
>>>to synchronize the SIP and MRCP Sessios, defined
>>>      a=channel:xxx
>>>      as part of application SDP.
>>>
>>>I'm trying to find out how I can synchronize SIP and RTSP streams  
>>>at the Media Server layer without any indication.
>>>
>>>As a=channel defined at the SDP level can I use this parameter to  
>>>sync between SIP and RTSP Streams.
>>>
>>>Thanks a lot.
>>>
>>>Osher
>>>
>>>
>>>
>>>
>>>
>>>
>>>------------------------------
>>>
>>>_______________________________________________
>>>mmusic mailing list
>>>mmusic@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>>End of mmusic Digest, Vol 22, Issue 3
>>>*************************************
>>>
>>>      
>>>
>>-- 
>>-----------------------------------------
>>Teodora Guenkova-Luy
>>
>>Dept. Distributed Systems, University of Ulm, Oberer Eselsberg,  
>>89069 Ulm, Germany
>>
>>Tel.: +49 (0731) 502-4148 FAX: +49 (0731) 502-4142
>>
>>e-Mail: teodora.guenkova-luy@uni-ulm.de
>>
>>Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/
>>-----------------------------------------
>>
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic
>>    
>>
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>
>  
>

-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/ 

-----------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/mmusic/attachments/20060207/96ebd483/attach
ment.htm

------------------------------

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic


End of mmusic Digest, Vol 22, Issue 5
*************************************



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 07 10:41:19 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6Uxz-00063U-0t; Tue, 07 Feb 2006 10:41:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6Uxw-0005rN-32; Tue, 07 Feb 2006 10:41:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04763;
	Tue, 7 Feb 2006 10:39:29 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-ext02.nokia.com ([131.228.20.94])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6VAF-0004HL-9q; Tue, 07 Feb 2006 10:54:01 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k17FexSv022283; Tue, 7 Feb 2006 17:41:06 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Feb 2006 17:41:03 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Feb 2006 17:41:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Re: [Rmt] SDP descriptors for ALC
Date: Tue, 7 Feb 2006 17:41:04 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD851301A85497@trebe101.NOE.Nokia.com>
In-Reply-To: <43E71AF8.40904@ericsson.com>
Thread-Topic: [MMUSIC] Re: [Rmt] SDP descriptors for ALC
Thread-Index: AcYrA/EK3NlAazEXTrGCwyGq8mcXeQA8NVWg
To: <magnus.westerlund@ericsson.com>, <Imed.Bouazizi@nokia.com>
X-OriginalArrivalTime: 07 Feb 2006 15:41:04.0733 (UTC)
	FILETIME=[E7CC80D0:01C62BFC]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Content-Transfer-Encoding: quoted-printable
Cc: mmusic@ietf.org, rmt@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi Magnus, thanks for the response.

3 issues: a=3Dflute-tsi; "*" fmt; ALC/UDP rules.

-----

"*" fmt...

The issue of "*" was already rasied a few times over the last 2 years in
emails and face-to-face. Originally we were considering "null" or "-"
instead of the already de facto "0" which didn't get much of a fan base
in MMUSIC. Put simply, some fmt value needs giving and we generally
don't want or need to list MIME types so either we hope the world is
aware of the de facto "0" or we assign an well known RFC's character
string. "*" just seems the best and most understandable choice. (Note, I
don't mean to exclude application/whatever and other MIME type
specifications, we just need a miscellaneous one which isn't a non
standards hack). Check out the numersous SDP examples in our
DVB+3GPP+OMA+IETF world for "0" usage.

Unless there is some world changing reason to drop "*", let's keep it

-----

ALC/UDP rules...

I'm not sure I fully grip the point. ALC is underspecified. E.g. OMA's
use of ALC is only feasible as they create a fully specified version
(actually by binding it to ESG metadata - a little beyond IETF Transport
Area's mandate), and for some reason they like to still call it ALC
giving a confusing impression that it's underspecified. Check out the
LCT and ALC RFCs or revised I-Ds and you come across a host of options,
most of which FLUTE bangs down to fully specified or leaves for
flute-sdp to fill in the parameters. Use of the checkpoint field is
totally open in ALC and in some fully specified versions it'll make a
sense to give a mapping in the session description (SDP) and in others
not. This is one example of something I simply do not want to touch
since fancy use of this field is not backed up by the same kind of
implementation rigour we have already got for FLUTE. OTOH, much of the
flute-sdp semantics could be used for LCT sessions in general and making
this explicit has its distinct advantages (I won't be picking up the
pieces of OMA-IETF divergence if it occurs, and having fought the for
DVB+3GPP+IETF I'm not sure I would recommend the job for it's fun factor
:)

So allowing underspecified ALC/UDP media means that two or more hosts
can "out-of-band" figure out what the full-spec would be and still use
the session description of underspecified ALC.

And this brings us onto the reason I've taken these 3 points out of
order. ALC vs. LCT. ALC is LCT with a few header extensions. If you were
to question why have separate LCT and ALC specifications and not just
one combined one you wouldn't be the first and certainly not the last as
there is no attempt to combine them and disturb mature specification
text and standards progress (you'd get verbose emails like this all over
the place :). It's LCT which defined the basic session semantics and ALC
and FLUTE add some more expectations of senders and recievers. As such,
I think I made and error in my response to Imed in that I should have
suggested "lct" instead of "alc" in the text string. My mind is mulling
this over during my short commutes so I may have an epiphany before
tomorrow.

Practically, if underspecified ALC or LCT is OK then we can bundle these
basics into flute-sdp, if not then forget it and let's stonewall the
whole discussion until the 3GPP+DVB+IETF aligned flute-sdp has been
published. (I am certainly unwilling to work on two at once and judging
by the number of actual text writters this may be a bit of a problem).

-----

a=3Dflute-tsi vs. a=3Dlct-tsi

Actually this is a good point which I anticipated coming up. First off
let's assume tsi is short and therefore culturally ambiguous even if
fixed in SDP stone; and that actually lct uses all these base properties
- i.e. that "a=3Dlct-tsi" is the sting to use.

This comes down to the fully specified vs. underspecified issues.
Flute-tsi clearly signals that all FLUTE/UDP media of this LCT session
("composite" or "restricted") form exactly one FLUTE session. Whereas
lct-tsi does not in fact limit what protocol ids are used in the lct
session as long as they are lct-based. I don't imagine mixed FLUTE/UDP
and ALC/UDP, but there is no sense in preventing mixed new1/xxx and
new2/xxx if someone has such a session need and the common factor is
LCT. Allowing this case does not pay my salary and I won't religeously
hang onto it, but it's a genuine use of LCT so excluding it makes no
sense.

As for flute-ch, the only reasonable argument why not to change to
lct-ch is that it would not be aligned with FLUTE SDP usage already
frozn in other standards bodies. (Obvioulsy this argument also applies
to flute-tsi but it's not as fundemental as the previous issue). In the
simplest form, flute-ch and lct-ch have exactly the same semantic.

However, if you were to start specifying the complex composite session
cases, you'd need to fix some things. Intentionally a composite (and
restricted) FLUTE session groups all FLUTE/UDP media of that composite
(or restricted) session into one FLUTE session. This is exactly right
and good. It also allows other protocol ID'ed media in the composite and
restircted sessions but those are not part of the FLUTE session (e.g. a
composite session consisting of RTP and FLUTE media which would
obviously be handled as one FLUTE session and multiple RTP media
sessions combined to one composite session). Naturally, I don't want to
get too deep into this as we'll be doing application design before long.
Needless to say, enabling application designers to use our transports is
what we are aiming to achieve.

If you were to have lct-tsi declared and also FLUTE media, how should
that be interpretted? If both lct-tsi and flute-tsi for a composite
session, what's that all about? This is the philosophical and practical
centre of all this: how underspecified can an LCT session really be?

For practical purposes, the declaration of a flute-tsi really has to say
that a FLUTE session of all FLUTE/UDP media (and without other media) is
described. For simplicity's sake, making the declaration of a flute-tsi
manditory when FLUTE/UDP media are described is acceptable; as is
explicitly stating that the use of FLUTE/UDP media with other session
semantics (including that of the parental LCT) is beyond the scope of
this specification.

For harmony reasons, we could include the LCT/UDP (or maybe ALC/UDP)
protocol id as something generic and underspecified, and the lct-tsi as
an indicator of an lct session; and require that the binding of the lct
session to specific protocol ids must be done, but is beyond the scope
of this specification. If we can't agree this, then let's allow the OMA
folk to have a stab and see if we like it after a few months. (In
anycase they'll have out flute-sdp at a reference as soon as it's
published so harmony for FLUTE sessions should be a dead cert).

We might also specify that only one of lct-tsi or flute-tsi is allowed
for one composite or restricted session. I don't see the need either
way, but if it helps consensus, why not?

-----

Cheers, Rod.



>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]=20
>On Behalf Of ext Magnus Westerlund
>Sent: 06 February, 2006 11:47
>To: Bouazizi Imed (Nokia-NRC/Tampere)
>Cc: mmusic@ietf.org; rmt@ietf.org
>Subject: [MMUSIC] Re: [Rmt] SDP descriptors for ALC
>
>Hi Imed and Rod,
>
>I do have some comments on your proposal.
>
>First of all why have both a=3Dflute-tsi and an a=3Dalc-tsi.=20
>Wouldn't a a=3Dtsi attribute be more appropriate. To my=20
>understanding there is no difference in TSI between the two.=20
>Also if some other fully specified protocol uses TSI they can=20
>reuse the TSI attribute. As the protocol will identify if it=20
>is flute or ALC, or something else in the future I don't see a=20
>risk of misinterpretation. The same comment applies also to=20
>the channel attribute. However here something more than a=3Dch=20
>is probably a good thing to indicate that it is the number of=20
>transport channels rather than related to media. Maybe a=3Dtrn-ch?
>
>I am also concerned by the use of * and no rules for the=20
>ALC/UDP protocol. Having something that is underspecified but=20
>no defined rules for how fully specified mechanisms are=20
>identified seem to be a bad choice. I would recommend that one=20
>uses some type of identifier space here. I don't think media=20
>types are the correct one, but some space should be set up to=20
>identify applications.
>
>cheers
>
>Magnus
>
>--=20
>
>Magnus Westerlund
>
>Multimedia Technologies, Ericsson Research EAB/TVA/A
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 03:59:09 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6lAL-0003SU-0n; Wed, 08 Feb 2006 03:59:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6lAI-0003PM-PI
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 03:59:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01366
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 03:57:24 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6lMp-0003Sq-RI
	for mmusic@ietf.org; Wed, 08 Feb 2006 04:12:06 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 08 Feb 2006 00:58:54 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k188wsWF005424
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 00:58:54 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 8 Feb 2006 00:58:54 -0800
Received: from [192.168.0.10] ([10.21.122.18]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Feb 2006 19:01:42 -0800
In-Reply-To: <05A1B749-4885-4A86-99EC-C898F8C1FADB@csperkins.org>
References: <24EAE5D4448B9D4592C6D234CBEBD59701503196@stntexch03.cis.neustar.com>
	<05A1B749-4885-4A86-99EC-C898F8C1FADB@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4C9E629C-F08C-4D3F-80DA-F2F70C9DFE95@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Date: Tue, 7 Feb 2006 19:01:40 -0800
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 08 Feb 2006 03:01:42.0365 (UTC)
	FILETIME=[FCECA0D0:01C62C5B]
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: Flemming Andreasen <fandreas@cisco.com>, Dan Wing <dwing@cisco.com>,
	Jon Peterson <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>,
	Brian E Carpenter <brc@zurich.ibm.com>,
	Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@acm.org>
Subject: [MMUSIC] Re: ADs - Re: Status of
	draft-ietf-mmusic-sdescriptions-12.txt?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hello,

An issue arose during RFC Editor review of draft-ietf-mmusic- 
sdescriptions-12 just prior to publication.  An Internet Draft  
document, Security Preconditions, appears among the Normative  
references.  The authors did not intend for it to be a Normative  
reference; it should have been in the Informative References  
section.  Still, this triggered a review and discussion.  Before  
proceeding to publication, the chairs and ADs wish for the WG to  
consider some of the issues of publishing draft-ietf-mmusic- 
sdescriptions without Security Preconditions.

SDP security descriptions (sdesc) as defined in draft-ietf-mmusic- 
sdescriptions-12.txt is designed to support a variety of signaling  
protocols that use SDP.  One of the most important is SIP. The way  
sdesc is defined, an answer has to be received before incoming media  
can be processed correctly by the offerer; this is unavoidable in  
cases where there are multiple crypto suites among the SDP offers.   
Without the answer, there is no way to determine which crypto offer  
has been selected by an answerer that sends media upon receiving the  
first SDP message.  This is a problem whenever media commences prior  
to receipt of the SDP answer.

The authors recognized this problem while working on the sdesc  
specification, and as a result, two of the authors wrote Security  
Preconditions (see draft-ietf-mmusic-securityprecondition-01.txt).  
However not everyone in the SIP community likes preconditions due to  
the added state machine complexity and signaling latency.  The  
current sdesc merely offers security preconditions as one possible  
solution, however it incorrectly lists it as a Normative reference.  
One alternative has already been offered (draft-wing-mmusic-sdes- 
early-media-00.txt) and at least one more extension to sdesc to  
address these issues is in the works.

  In lieu of the above, the authors would like to change the current  
Normative reference to security preconditions to be an Informative  
reference instead. There is a concern, however, that with such a  
change, we would not have a complete normative solution for SIP.  So,  
we're asking the WG members for comments.  draft-ietf-mmusic- 
sdescriptions-12.txt has finished last call in the WG and the IESG,  
but the document that completed last call relied upon security  
preconditions, which may not be the ultimate solution.  We would like  
to know if anyone in the WG objects to progressing this I-D without  
security preconditions being normative and without another normative  
solution to address the above issues. If you object, please speak up  
and let us know what the normative solution should be.

Thanks,

Mark, Flemming & Dan

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 04:22:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6lXF-0000Ed-L3; Wed, 08 Feb 2006 04:22:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6lXC-0000Cj-BV
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 04:22:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03085
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 04:20:56 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6ljc-0004Hz-FJ
	for mmusic@ietf.org; Wed, 08 Feb 2006 04:35:37 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63888
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1F6lWa-0003kJ-Gn; Wed, 08 Feb 2006 09:22:08 +0000
In-Reply-To: <4C9E629C-F08C-4D3F-80DA-F2F70C9DFE95@cisco.com>
References: <24EAE5D4448B9D4592C6D234CBEBD59701503196@stntexch03.cis.neustar.com>
	<05A1B749-4885-4A86-99EC-C898F8C1FADB@csperkins.org>
	<4C9E629C-F08C-4D3F-80DA-F2F70C9DFE95@cisco.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1363A77E-D304-4A9A-983A-608C9B1F13A3@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: ADs - Re: Status of
	draft-ietf-mmusic-sdescriptions-12.txt?
Date: Wed, 8 Feb 2006 09:22:05 +0000
To: IETF MMUSIC working group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: Flemming Andreasen <fandreas@cisco.com>, Dan Wing <dwing@cisco.com>,
	Mark Baugher <mbaugher@cisco.com>, Jon Peterson <jon.peterson@neustar.biz>,
	Allison Mankin <mankin@psg.com>,
	Brian E Carpenter <brc@zurich.ibm.com>, Joerg Ott <jo@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Folks,

In the interests of making progress, please provide any comments on  
this proposal to the mailing list before 15th February.

Colin



On 8 Feb 2006, at 03:01, Mark Baugher wrote:
> Hello,
>
> An issue arose during RFC Editor review of draft-ietf-mmusic- 
> sdescriptions-12 just prior to publication.  An Internet Draft  
> document, Security Preconditions, appears among the Normative  
> references.  The authors did not intend for it to be a Normative  
> reference; it should have been in the Informative References  
> section.  Still, this triggered a review and discussion.  Before  
> proceeding to publication, the chairs and ADs wish for the WG to  
> consider some of the issues of publishing draft-ietf-mmusic- 
> sdescriptions without Security Preconditions.
>
> SDP security descriptions (sdesc) as defined in draft-ietf-mmusic- 
> sdescriptions-12.txt is designed to support a variety of signaling  
> protocols that use SDP.  One of the most important is SIP. The way  
> sdesc is defined, an answer has to be received before incoming  
> media can be processed correctly by the offerer; this is  
> unavoidable in cases where there are multiple crypto suites among  
> the SDP offers.  Without the answer, there is no way to determine  
> which crypto offer has been selected by an answerer that sends  
> media upon receiving the first SDP message.  This is a problem  
> whenever media commences prior to receipt of the SDP answer.
>
> The authors recognized this problem while working on the sdesc  
> specification, and as a result, two of the authors wrote Security  
> Preconditions (see draft-ietf-mmusic-securityprecondition-01.txt).  
> However not everyone in the SIP community likes preconditions due  
> to the added state machine complexity and signaling latency.  The  
> current sdesc merely offers security preconditions as one possible  
> solution, however it incorrectly lists it as a Normative reference.  
> One alternative has already been offered (draft-wing-mmusic-sdes- 
> early-media-00.txt) and at least one more extension to sdesc to  
> address these issues is in the works.
>
>  In lieu of the above, the authors would like to change the current  
> Normative reference to security preconditions to be an Informative  
> reference instead. There is a concern, however, that with such a  
> change, we would not have a complete normative solution for SIP.   
> So, we're asking the WG members for comments.  draft-ietf-mmusic- 
> sdescriptions-12.txt has finished last call in the WG and the IESG,  
> but the document that completed last call relied upon security  
> preconditions, which may not be the ultimate solution.  We would  
> like to know if anyone in the WG objects to progressing this I-D  
> without security preconditions being normative and without another  
> normative solution to address the above issues. If you object,  
> please speak up and let us know what the normative solution should be.
>
> Thanks,
>
> Mark, Flemming & Dan
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 12:58:46 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6taY-0002eD-35; Wed, 08 Feb 2006 12:58:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6taA-0002Jy-JW
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 12:58:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15900
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 12:56:40 -0500 (EST)
Received: from host10.216.41.24.conversent.net ([216.41.24.10]
	helo=acmepacket.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6tmm-0006b9-AN
	for mmusic@ietf.org; Wed, 08 Feb 2006 13:11:25 -0500
Received: from HKaplan [216.41.24.2] by acmepacket.com with ESMTP
	(SMTPD-9.02) id A1230174; Wed, 08 Feb 2006 12:57:55 -0500
From: "Hadriel Kaplan" <HKaplan@acmepacket.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>, <mmusic@ietf.org>
Subject: RE: [MMUSIC] Re: ADs - Re: Status
	ofdraft-ietf-mmusic-sdescriptions-12.txt?
Date: Wed, 8 Feb 2006 12:57:48 -0500
Message-ID: <010e01c62cd9$2c34eff0$60c8000a@acmepacket.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <4C9E629C-F08C-4D3F-80DA-F2F70C9DFE95@cisco.com>
Thread-Index: AcYsjpMCVvnknintTK2j5pey9JMOhgARJ74A
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit
Cc: 'Flemming Andreasen' <fandreas@cisco.com>, 'Dan Wing' <dwing@cisco.com>,
	'Jon Peterson' <jon.peterson@neustar.biz>,
	'Allison Mankin' <mankin@psg.com>,
	'Brian E Carpenter' <brc@zurich.ibm.com>,
	'Colin Perkins' <csp@csperkins.org>, 'Joerg Ott' <jo@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

I am also in favor of changing the security preconditions piece to
Informative.  The fairly rare use of sip preconditions should be an
indicator.

Also, one your lines below I believe is misleading: "Without the answer,
there is no way to determine which crypto offer has been selected by an
answerer that sends media upon receiving the first SDP message."  That's
true, but I thought the real reason an answer has to be sent back for early
media is because the sdes offer was for the keys of the transmitting media
direction (from the offerer to the answerer) - so the offerer does not know
any of the keys to decode early received media until she gets an sdes
answer.  In other words even if only one crypto suite and one key were
offered, you would still need an answer to decrypt early media.

On a side note, I know it's too late to change, but I was always curious why
the sdes offerer sent the keys for transmitting media, instead of the ones
for receive-side as it does with everything else in SDP.  Was there a
rationale for this?

-hadriel


> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Mark Baugher
> Sent: Tuesday, February 07, 2006 10:02 PM
> To: mmusic@ietf.org
> Cc: Flemming Andreasen; Dan Wing; Jon Peterson; Allison Mankin; Brian E
> Carpenter; Colin Perkins; Joerg Ott
> Subject: [MMUSIC] Re: ADs - Re: Status ofdraft-ietf-mmusic-sdescriptions-
> 12.txt?
> 
> Hello,
> 
> An issue arose during RFC Editor review of draft-ietf-mmusic-
> sdescriptions-12 just prior to publication.  An Internet Draft
> document, Security Preconditions, appears among the Normative
> references.  The authors did not intend for it to be a Normative
> reference; it should have been in the Informative References
> section.  Still, this triggered a review and discussion.  Before
> proceeding to publication, the chairs and ADs wish for the WG to
> consider some of the issues of publishing draft-ietf-mmusic-
> sdescriptions without Security Preconditions.
> 
> SDP security descriptions (sdesc) as defined in draft-ietf-mmusic-
> sdescriptions-12.txt is designed to support a variety of signaling
> protocols that use SDP.  One of the most important is SIP. The way
> sdesc is defined, an answer has to be received before incoming media
> can be processed correctly by the offerer; this is unavoidable in
> cases where there are multiple crypto suites among the SDP offers.
> Without the answer, there is no way to determine which crypto offer
> has been selected by an answerer that sends media upon receiving the
> first SDP message.  This is a problem whenever media commences prior
> to receipt of the SDP answer.
> 
> The authors recognized this problem while working on the sdesc
> specification, and as a result, two of the authors wrote Security
> Preconditions (see draft-ietf-mmusic-securityprecondition-01.txt).
> However not everyone in the SIP community likes preconditions due to
> the added state machine complexity and signaling latency.  The
> current sdesc merely offers security preconditions as one possible
> solution, however it incorrectly lists it as a Normative reference.
> One alternative has already been offered (draft-wing-mmusic-sdes-
> early-media-00.txt) and at least one more extension to sdesc to
> address these issues is in the works.
> 
>   In lieu of the above, the authors would like to change the current
> Normative reference to security preconditions to be an Informative
> reference instead. There is a concern, however, that with such a
> change, we would not have a complete normative solution for SIP.  So,
> we're asking the WG members for comments.  draft-ietf-mmusic-
> sdescriptions-12.txt has finished last call in the WG and the IESG,
> but the document that completed last call relied upon security
> preconditions, which may not be the ultimate solution.  We would like
> to know if anyone in the WG objects to progressing this I-D without
> security preconditions being normative and without another normative
> solution to address the above issues. If you object, please speak up
> and let us know what the normative solution should be.
> 
> Thanks,
> 
> Mark, Flemming & Dan
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 14:14:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6umC-0000Pb-K2; Wed, 08 Feb 2006 14:14:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6umB-0000OC-DX
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 14:14:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22911
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 14:13:09 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6uyn-0001Fm-1z
	for mmusic@ietf.org; Wed, 08 Feb 2006 14:27:56 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-2.cisco.com with ESMTP; 08 Feb 2006 11:14:38 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k18JEZk9027442;
	Wed, 8 Feb 2006 11:14:36 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 8 Feb 2006 11:14:35 -0800
Received: from [192.168.0.10] ([10.21.121.223]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Feb 2006 11:14:33 -0800
In-Reply-To: <010e01c62cd9$2c34eff0$60c8000a@acmepacket.com>
References: <010e01c62cd9$2c34eff0$60c8000a@acmepacket.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2CB688AD-95FB-4F89-AF75-8214CEE84629@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] Re: ADs - Re: Status
	ofdraft-ietf-mmusic-sdescriptions-12.txt?
Date: Wed, 8 Feb 2006 11:14:32 -0800
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 08 Feb 2006 19:14:34.0036 (UTC)
	FILETIME=[E526C740:01C62CE3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Content-Transfer-Encoding: 7bit
Cc: 'Flemming Andreasen' <fandreas@cisco.com>, 'Dan Wing' <dwing@cisco.com>,
	mmusic@ietf.org, 'Jon Peterson' <jon.peterson@neustar.biz>,
	'Allison Mankin' <mankin@psg.com>,
	'Brian E Carpenter' <brc@zurich.ibm.com>,
	'Colin Perkins' <csp@csperkins.org>, 'Joerg Ott' <jo@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hadriel,
   Thanks for your comments.

On Feb 8, 2006, at 9:57 AM, Hadriel Kaplan wrote:

> I am also in favor of changing the security preconditions piece to
> Informative.  The fairly rare use of sip preconditions should be an
> indicator.
>
> Also, one your lines below I believe is misleading: "Without the  
> answer,
> there is no way to determine which crypto offer has been selected  
> by an
> answerer that sends media upon receiving the first SDP message."   
> That's
> true, but I thought the real reason an answer has to be sent back  
> for early
> media is because the sdes offer was for the keys of the  
> transmitting media
> direction (from the offerer to the answerer) - so the offerer does  
> not know
> any of the keys to decode early received media until she gets an sdes
> answer.  In other words even if only one crypto suite and one key were
> offered, you would still need an answer to decrypt early media.

What you say is correct and thanks for the clarification.  My point  
is that it is not simply a matter of handing a bidirectional master  
key or a second, unidirectional master key to the receiver for  
sending its media so long as multiple offers are possible.  The real  
problem to the problem of early commencement of media is the presence  
of multiple offers in the SDP message not the way a key is sent.
>
> On a side note, I know it's too late to change, but I was always  
> curious why
> the sdes offerer sent the keys for transmitting media, instead of  
> the ones
> for receive-side as it does with everything else in SDP.

I'm not sure what you mean by "as it does with everything else in  
SDP."  There are recvonly, sendonly and sendrecv attributes in SDP  
for specifying direction semantics.  In the earliest versions of SDP  
security descriptions, we allowed a direction attribute on the key so  
an SDP sender could hand a receiver a key with which to decrypt its  
received stream, encrypt its transmitted stream, or both (the "key  
use indicator" of Section 4.4.2 in http://www3.ietf.org/proceedings/ 
03jul/I-D/draft-ietf-mmusic-sdescriptions-01.txt).  This allowed a  
key to be shared among endpoints, which we generally don't want to do  
when counter mode encryption (the SRTP default) is used.  It also  
confused a lot of people.  We decided to simplify the specification  
by removing it.  I thought at the time that we could in the future  
specify a second key for the receiver to use to encrypt its stream if  
this were needed.  As I mentioned above, however, giving the receiver  
a key does not help with the current problem.

> Was there a
> rationale for this?

We did not want to share a single key by default among two or more  
end systems because SRTP AES counter mode has a risk of counter  
overlap.  Counter overlap has the risk of exposing known plaintext in  
encrypted packets.  The probability of this happening is low:  SRTP  
uses the SSRC to make each stream unique and avoid counter overlap,  
but the SSRC can collide among endpoints.  Thus, we do not want to  
make key sharing a default behavior given this one, known weakness of  
counter mode.

So why not have the SDP offerer offer two keys? The quality of the  
encryption is greatly affected by the randomness of the key.  When  
creating keys, it is best to have each side add some randomness in  
the key derivation as is commonly done in pairwise key establishment  
protocols.  This is not possible for groups and sdesc needs to  
support groups.  Supplying an encryption key to the receiver is risky  
because in some protocols, such as SIP, the supplied key is handed to  
a group of receivers when forking occurs, thus raising the  
probability of SSRC collision.  The next best thing IMHO is to at  
least allow a sender to ensure the quality of a key for *its* data by  
supplying the decryption key for its data.  I'm not religious about  
this point.  If supplying the encryption key (rather than or in  
addition to the decryption key) to the receiver solved the problem  
described above, I'd personally support that.  But it doesn't.

Mark

>
> -hadriel
>
>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
>> Behalf
>> Of Mark Baugher
>> Sent: Tuesday, February 07, 2006 10:02 PM
>> To: mmusic@ietf.org
>> Cc: Flemming Andreasen; Dan Wing; Jon Peterson; Allison Mankin;  
>> Brian E
>> Carpenter; Colin Perkins; Joerg Ott
>> Subject: [MMUSIC] Re: ADs - Re: Status ofdraft-ietf-mmusic- 
>> sdescriptions-
>> 12.txt?
>>
>> Hello,
>>
>> An issue arose during RFC Editor review of draft-ietf-mmusic-
>> sdescriptions-12 just prior to publication.  An Internet Draft
>> document, Security Preconditions, appears among the Normative
>> references.  The authors did not intend for it to be a Normative
>> reference; it should have been in the Informative References
>> section.  Still, this triggered a review and discussion.  Before
>> proceeding to publication, the chairs and ADs wish for the WG to
>> consider some of the issues of publishing draft-ietf-mmusic-
>> sdescriptions without Security Preconditions.
>>
>> SDP security descriptions (sdesc) as defined in draft-ietf-mmusic-
>> sdescriptions-12.txt is designed to support a variety of signaling
>> protocols that use SDP.  One of the most important is SIP. The way
>> sdesc is defined, an answer has to be received before incoming media
>> can be processed correctly by the offerer; this is unavoidable in
>> cases where there are multiple crypto suites among the SDP offers.
>> Without the answer, there is no way to determine which crypto offer
>> has been selected by an answerer that sends media upon receiving the
>> first SDP message.  This is a problem whenever media commences prior
>> to receipt of the SDP answer.
>>
>> The authors recognized this problem while working on the sdesc
>> specification, and as a result, two of the authors wrote Security
>> Preconditions (see draft-ietf-mmusic-securityprecondition-01.txt).
>> However not everyone in the SIP community likes preconditions due to
>> the added state machine complexity and signaling latency.  The
>> current sdesc merely offers security preconditions as one possible
>> solution, however it incorrectly lists it as a Normative reference.
>> One alternative has already been offered (draft-wing-mmusic-sdes-
>> early-media-00.txt) and at least one more extension to sdesc to
>> address these issues is in the works.
>>
>>   In lieu of the above, the authors would like to change the current
>> Normative reference to security preconditions to be an Informative
>> reference instead. There is a concern, however, that with such a
>> change, we would not have a complete normative solution for SIP.  So,
>> we're asking the WG members for comments.  draft-ietf-mmusic-
>> sdescriptions-12.txt has finished last call in the WG and the IESG,
>> but the document that completed last call relied upon security
>> preconditions, which may not be the ultimate solution.  We would like
>> to know if anyone in the WG objects to progressing this I-D without
>> security preconditions being normative and without another normative
>> solution to address the above issues. If you object, please speak up
>> and let us know what the normative solution should be.
>>
>> Thanks,
>>
>> Mark, Flemming & Dan
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 15:55:42 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6wLl-0007jH-Vq; Wed, 08 Feb 2006 15:55:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6wLk-0007Yz-31
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 15:55:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02206
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 15:53:52 -0500 (EST)
Received: from host10.216.41.24.conversent.net ([216.41.24.10]
	helo=acmepacket.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F6wYJ-0005Ml-3S
	for mmusic@ietf.org; Wed, 08 Feb 2006 16:08:40 -0500
Received: from HKaplan [216.41.24.2] by acmepacket.com with ESMTP
	(SMTPD-9.02) id AAA7031C; Wed, 08 Feb 2006 15:55:03 -0500
From: "Hadriel Kaplan" <HKaplan@acmepacket.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>
Subject: RE: [MMUSIC] Re: ADs - Re: Status
	ofdraft-ietf-mmusic-sdescriptions-12.txt?
Date: Wed, 8 Feb 2006 15:54:56 -0500
Message-ID: <011801c62cf1$eafbd170$60c8000a@acmepacket.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <2CB688AD-95FB-4F89-AF75-8214CEE84629@cisco.com>
Thread-Index: AcYs4+gcQAiV8UErSpqOz/W8fj2O3QACGepQ
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: 'Flemming Andreasen' <fandreas@cisco.com>, 'Dan Wing' <dwing@cisco.com>,
	mmusic@ietf.org, 'Jon Peterson' <jon.peterson@neustar.biz>,
	'Allison Mankin' <mankin@psg.com>,
	'Brian E Carpenter' <brc@zurich.ibm.com>,
	'Colin Perkins' <csp@csperkins.org>, 'Joerg Ott' <jo@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Comments inline...

> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Wednesday, February 08, 2006 2:15 PM
> To: Hadriel Kaplan
> Cc: mmusic@ietf.org; 'Flemming Andreasen'; 'Dan Wing'; 'Jon Peterson';
> 'Allison Mankin'; 'Brian E Carpenter'; 'Colin Perkins'; 'Joerg Ott'
> Subject: Re: [MMUSIC] Re: ADs - Re: Status ofdraft-ietf-mmusic-
> sdescriptions-12.txt?
> What you say is correct and thanks for the clarification.  My point
> is that it is not simply a matter of handing a bidirectional master
> key or a second, unidirectional master key to the receiver for
> sending its media so long as multiple offers are possible.  The real
> problem to the problem of early commencement of media is the presence
> of multiple offers in the SDP message not the way a key is sent.

But doesn't that problem get solved with unique MKIs?  In the way
draft-wing-mmusic-sdes-early-media-00.txt handles it, or at least that's how
I read it.

> > the sdes offerer sent the keys for transmitting media, instead of
> > the ones
> > for receive-side as it does with everything else in SDP.
> 
> I'm not sure what you mean by "as it does with everything else in
> SDP."  There are recvonly, sendonly and sendrecv attributes in SDP
> for specifying direction semantics.  In the earliest versions of SDP

Yup, sorry meant it more in the sense that when you make the offer you're
saying you can immediately receive any of the offered codecs at the offered
ports. (ie, with respect to early media)  A nit really.

> So why not have the SDP offerer offer two keys? The quality of the
> encryption is greatly affected by the randomness of the key.  When
> creating keys, it is best to have each side add some randomness in
> the key derivation as is commonly done in pairwise key establishment
> protocols.  This is not possible for groups and sdesc needs to
> support groups.  Supplying an encryption key to the receiver is risky
> because in some protocols, such as SIP, the supplied key is handed to
> a group of receivers when forking occurs, thus raising the
> probability of SSRC collision.  The next best thing IMHO is to at
> least allow a sender to ensure the quality of a key for *its* data by
> supplying the decryption key for its data.  I'm not religious about
> this point.  If supplying the encryption key (rather than or in
> addition to the decryption key) to the receiver solved the problem
> described above, I'd personally support that.  But it doesn't.

I was waiting for that, so I could say wouldn't that also apply to
draft-wing-mmusic-sdes-early-media-00.txt, since the draft allows the
offerer to tell the answerer both keys?  But thinking about this more, I
guess having both ways lets the market choose, which is preferred.

As to the overlapping SSRC problem with an offered key, I think the risk of
that happening, and happening for long enough to be cracked (in practical
terms), etc., is outweighed by the usefulness of early media.  But we'll get
there with the early-media draft, or just by 1xx responses w/SDP, so problem
solved.  :)

-hadriel



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 08 17:12:38 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F6xYE-0008QL-C0; Wed, 08 Feb 2006 17:12:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F6xYC-0008Lt-5S
	for mmusic@megatron.ietf.org; Wed, 08 Feb 2006 17:12:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08700
	for <mmusic@ietf.org>; Wed, 8 Feb 2006 17:10:45 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6xkj-0008JK-3M
	for mmusic@ietf.org; Wed, 08 Feb 2006 17:25:34 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-5.cisco.com with ESMTP; 08 Feb 2006 14:12:17 -0800
X-IronPort-AV: i="4.02,98,1139212800"; 
	d="scan'208"; a="254382301:sNHT34769908"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k18MCBWJ006488;
	Wed, 8 Feb 2006 14:12:16 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 8 Feb 2006 14:12:16 -0800
Received: from [192.168.0.10] ([10.21.145.25]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Feb 2006 14:12:15 -0800
In-Reply-To: <011801c62cf1$eafbd170$60c8000a@acmepacket.com>
References: <011801c62cf1$eafbd170$60c8000a@acmepacket.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <75FF3DAE-D1C4-4BCD-8A3B-9ABE302B03BA@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] Re: ADs - Re: Status
	ofdraft-ietf-mmusic-sdescriptions-12.txt?
Date: Wed, 8 Feb 2006 14:12:14 -0800
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 08 Feb 2006 22:12:15.0396 (UTC)
	FILETIME=[B7D13640:01C62CFC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit
Cc: 'Flemming Andreasen' <fandreas@cisco.com>, 'Dan Wing' <dwing@cisco.com>,
	mmusic@ietf.org, 'Jon Peterson' <jon.peterson@neustar.biz>,
	'Allison Mankin' <mankin@psg.com>,
	'Brian E Carpenter' <brc@zurich.ibm.com>,
	'Colin Perkins' <csp@csperkins.org>, 'Joerg Ott' <jo@acm.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org


On Feb 8, 2006, at 12:54 PM, Hadriel Kaplan wrote:

> Comments inline...
>
>> -----Original Message-----
>> From: Mark Baugher [mailto:mbaugher@cisco.com]
>> Sent: Wednesday, February 08, 2006 2:15 PM
>> To: Hadriel Kaplan
>> Cc: mmusic@ietf.org; 'Flemming Andreasen'; 'Dan Wing'; 'Jon  
>> Peterson';
>> 'Allison Mankin'; 'Brian E Carpenter'; 'Colin Perkins'; 'Joerg Ott'
>> Subject: Re: [MMUSIC] Re: ADs - Re: Status ofdraft-ietf-mmusic-
>> sdescriptions-12.txt?
>> What you say is correct and thanks for the clarification.  My point
>> is that it is not simply a matter of handing a bidirectional master
>> key or a second, unidirectional master key to the receiver for
>> sending its media so long as multiple offers are possible.  The real
>> problem to the problem of early commencement of media is the presence
>> of multiple offers in the SDP message not the way a key is sent.
>
> But doesn't that problem get solved with unique MKIs?  In the way
> draft-wing-mmusic-sdes-early-media-00.txt handles it, or at least  
> that's how
> I read it.

I think it's tricky to use MKIs in this way.

>
>>> the sdes offerer sent the keys for transmitting media, instead of
>>> the ones
>>> for receive-side as it does with everything else in SDP.
>>
>> I'm not sure what you mean by "as it does with everything else in
>> SDP."  There are recvonly, sendonly and sendrecv attributes in SDP
>> for specifying direction semantics.  In the earliest versions of SDP
>
> Yup, sorry meant it more in the sense that when you make the offer  
> you're
> saying you can immediately receive any of the offered codecs at the  
> offered
> ports. (ie, with respect to early media)  A nit really.

I see your point.  We chose to treat keys differently than codecs for  
the reasons I mentioned in my previous note.

>
>> So why not have the SDP offerer offer two keys? The quality of the
>> encryption is greatly affected by the randomness of the key.  When
>> creating keys, it is best to have each side add some randomness in
>> the key derivation as is commonly done in pairwise key establishment
>> protocols.  This is not possible for groups and sdesc needs to
>> support groups.  Supplying an encryption key to the receiver is risky
>> because in some protocols, such as SIP, the supplied key is handed to
>> a group of receivers when forking occurs, thus raising the
>> probability of SSRC collision.  The next best thing IMHO is to at
>> least allow a sender to ensure the quality of a key for *its* data by
>> supplying the decryption key for its data.  I'm not religious about
>> this point.  If supplying the encryption key (rather than or in
>> addition to the decryption key) to the receiver solved the problem
>> described above, I'd personally support that.  But it doesn't.
>
> I was waiting for that, so I could say wouldn't that also apply to
> draft-wing-mmusic-sdes-early-media-00.txt, since the draft allows the
> offerer to tell the answerer both keys?

I think it's fine to pass both keys to mitigate the problem of  
sending media before the answer is received.

> But thinking about this more, I
> guess having both ways lets the market choose, which is preferred.
>
> As to the overlapping SSRC problem with an offered key, I think the  
> risk of
> that happening, and happening for long enough to be cracked (in  
> practical
> terms), etc., is outweighed by the usefulness of early media.

I agree.

> But we'll get
> there with the early-media draft, or just by 1xx responses w/SDP,  
> so problem
> solved.  :)

We can only hope ;-)

cheers, Mark
>
> -hadriel

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 10 05:39:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Vgm-0000RY-Cu; Fri, 10 Feb 2006 05:39:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Vgk-0000Pt-Lm; Fri, 10 Feb 2006 05:39:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06927;
	Fri, 10 Feb 2006 05:37:58 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7Vtj-0003Q4-Gr; Fri, 10 Feb 2006 05:53:08 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:64621)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1F7VgL-0007m3-3l; Fri, 10 Feb 2006 10:39:17 +0000
In-Reply-To: <7222D14EF47E0840AD88EC7BCBAD851301A85497@trebe101.NOE.Nokia.com>
References: <7222D14EF47E0840AD88EC7BCBAD851301A85497@trebe101.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6C8D41A2-79BA-489A-BE4A-9400A26341F7@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [Rmt] SDP descriptors for ALC
Date: Fri, 10 Feb 2006 10:39:16 +0000
To: Rod.Walsh@nokia.com
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: magnus.westerlund@ericsson.com, mmusic@ietf.org, rmt@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

[inline]

On 7 Feb 2006, at 15:41, Rod.Walsh@nokia.com wrote:
> 3 issues: a=flute-tsi; "*" fmt; ALC/UDP rules.
...
> ALC/UDP rules...
>
> I'm not sure I fully grip the point. ALC is underspecified. E.g. OMA's
> use of ALC is only feasible as they create a fully specified version
> (actually by binding it to ESG metadata - a little beyond IETF  
> Transport
> Area's mandate), and for some reason they like to still call it ALC
> giving a confusing impression that it's underspecified. Check out the
> LCT and ALC RFCs or revised I-Ds and you come across a host of  
> options,
> most of which FLUTE bangs down to fully specified or leaves for
> flute-sdp to fill in the parameters. Use of the checkpoint field is
> totally open in ALC and in some fully specified versions it'll make a
> sense to give a mapping in the session description (SDP) and in others
> not. This is one example of something I simply do not want to touch
> since fancy use of this field is not backed up by the same kind of
> implementation rigour we have already got for FLUTE. OTOH, much of the
> flute-sdp semantics could be used for LCT sessions in general and  
> making
> this explicit has its distinct advantages (I won't be picking up the
> pieces of OMA-IETF divergence if it occurs, and having fought the for
> DVB+3GPP+IETF I'm not sure I would recommend the job for it's fun  
> factor
> :)
>
> So allowing underspecified ALC/UDP media means that two or more hosts
> can "out-of-band" figure out what the full-spec would be and still use
> the session description of underspecified ALC.
>
> And this brings us onto the reason I've taken these 3 points out of
> order. ALC vs. LCT. ALC is LCT with a few header extensions. If you  
> were
> to question why have separate LCT and ALC specifications and not just
> one combined one you wouldn't be the first and certainly not the  
> last as
> there is no attempt to combine them and disturb mature specification
> text and standards progress (you'd get verbose emails like this all  
> over
> the place :). It's LCT which defined the basic session semantics  
> and ALC
> and FLUTE add some more expectations of senders and recievers. As  
> such,
> I think I made and error in my response to Imed in that I should have
> suggested "lct" instead of "alc" in the text string. My mind is  
> mulling
> this over during my short commutes so I may have an epiphany before
> tomorrow.
>
> Practically, if underspecified ALC or LCT is OK then we can bundle  
> these
> basics into flute-sdp, if not then forget it and let's stonewall the
> whole discussion until the 3GPP+DVB+IETF aligned flute-sdp has been
> published. (I am certainly unwilling to work on two at once and  
> judging
> by the number of actual text writters this may be a bit of a problem).

Is it useful to signal under-specified ALC or LCT transport? Unless I  
misunderstood, wouldn't that be signalling an incomplete building block?

Colin

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 14 17:06:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F98JI-0006VU-N8; Tue, 14 Feb 2006 17:06:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F98JH-0006UT-A0; Tue, 14 Feb 2006 17:06:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06385;
	Tue, 14 Feb 2006 17:04:25 -0500 (EST)
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F98XB-0003on-26; Tue, 14 Feb 2006 17:20:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1EM5x9W008373
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 14 Feb 2006 22:05:59 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1F98J5-0006E9-9d; Tue, 14 Feb 2006 17:05:59 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1F98J5-0006E9-9d@stiedprstage1.ietf.org>
Date: Tue, 14 Feb 2006 17:05:59 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mmusic chair <csp@csperkins.org>, Internet Architecture Board <iab@iab.org>,
	mmusic mailing list <mmusic@ietf.org>, mmusic chair <jo@acm.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MMUSIC] Protocol Action: 'SDP: Session Description Protocol' to 
 Proposed Standard 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The IESG has approved the following document:

- 'SDP: Session Description Protocol '
   <draft-ietf-mmusic-sdp-new-26.txt> as a Proposed Standard

This document is the product of the Multiparty Multimedia Session Control 
Working Group. 

The IESG contact person is Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-26.txt

Technical Summary
 
This memo defines the Session Description Protocol (SDP). SDP is intended
for describing multimedia sessions for the purposes of session announcement,
session invitation, and other forms of multimedia session initiation.

In particular, this document provides a new version of SDP that incorporates
fixes and extensions that have been designed in the MMUSIC WG since the
publication of the original SDP specification, RFC2327. This document is not
SDPng, which fundamentally re-examines the problem space of SDP and arrives
at a new solution. Rather, this document collects increment fixes to SDP
that are critical to its proper operation, and merit inclusion in the core
standard.
 
Working Group Summary
 
The MMUSIC working group supported publication of this document.
 
Protocol Quality
 
This document was reviewed by Allison Mankin and Jon Peterson.

RFC-Editor Note

Please append to the start of Section 9:

OLD: 

9.  SDP Grammar

NEW:

9.  SDP Grammar
   
   This section provides a grammar for SDP.  It uses a variant of
   ABNF [4].  In this variant, contrary to section 2.3 of [4], strings
   are *not* case-insensitive, and must match exactly the case specified.

Security Considerations, last paragraph:

OLD:

   Use of the "k=" field poses a significant security risk, since it
   conveys session encryption keys in the clear.  SDP MUST NOT be used
   to convey key material, unless it can be guaranteed that the channel
   over which the SDP is delivered is both private and authenticated.

NEW:

   Use of the "k=" field poses a significant security risk, since it
   conveys session encryption keys in the clear.  SDP MUST NOT be used
   to convey key material, unless it can be guaranteed that the channel
   over which the SDP is delivered is both private and authenticated.
   Moreover, the k= line provides no way to indicate or negotiate 
   cryptographic key algorithms, and as it provides for only a single 
   symmetric key, rather than separate keys for confidentiality and 
   integrity, its utility is severely limited. Use of the k= line is 
   NOT RECOMMENDED, and any usage of the k= line MUST address these 
   shortcomings.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Thu Feb 16 04:38:01 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9faL-0004US-AH; Thu, 16 Feb 2006 04:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9faD-0004TZ-Fv
	for mmusic@megatron.ietf.org; Thu, 16 Feb 2006 04:37:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03692
	for <mmusic@ietf.org>; Thu, 16 Feb 2006 04:36:05 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9foJ-0004kQ-PG
	for mmusic@ietf.org; Thu, 16 Feb 2006 04:52:34 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B98DFA36
	for <mmusic@ietf.org>; Thu, 16 Feb 2006 10:37:45 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Feb 2006 10:37:45 +0100
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Feb 2006 10:37:44 +0100
Message-ID: <43F447E8.9030207@ericsson.com>
Date: Thu, 16 Feb 2006 10:37:44 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Feb 2006 09:37:44.0789 (UTC)
	FILETIME=[A3BCC850:01C632DC]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] The FEC grouping mechanism
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi,

The FEC grouping draft in its latest version has been available for a while:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-fec-grouping-02.txt

Are there any comments on this or could we last call it?

I would like to get this resolved so that we can submit this one 
together with the AVT ULP draft:
http://www.ietf.org/internet-drafts/draft-ietf-avt-ulp-14.txt

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Thu Feb 16 07:41:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9iSG-0002BM-Pt; Thu, 16 Feb 2006 07:41:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9iSE-0002BF-KG
	for mmusic@megatron.ietf.org; Thu, 16 Feb 2006 07:41:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18672
	for <mmusic@ietf.org>; Thu, 16 Feb 2006 07:40:03 -0500 (EST)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9igN-00031w-AH
	for mmusic@ietf.org; Thu, 16 Feb 2006 07:56:33 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	174624F0025
	for <mmusic@ietf.org>; Thu, 16 Feb 2006 13:41:43 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 16 Feb 2006 13:41:43 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 16 Feb 2006 13:41:42 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 7563A264B;
	Thu, 16 Feb 2006 14:41:42 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 431D41AB92F;
	Thu, 16 Feb 2006 14:41:42 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id BCB6C1AB90A;
	Thu, 16 Feb 2006 14:41:41 +0200 (EET)
Message-ID: <43F47301.8020408@ericsson.com>
Date: Thu, 16 Feb 2006 14:41:37 +0200
From: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Organization: Ericsson
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 16 Feb 2006 12:41:42.0873 (UTC)
	FILETIME=[56F2BC90:01C632F6]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: gonzalo.camarillo@ericsson.com
Subject: [MMUSIC] Draft: SDP Content Attribute
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi all,

We just submitted the following draft:

http://users.piuha.net/jantzgu/temp/draft-ietf-mmusic-sdp-media-content-01.txt

We feel that the draft is complete, and that it is ready for working 
group last call. If you still have some comments, I would appreciate if 
you would send them to me.


-- 
Regards,
Jani Hautakorpi

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 17 18:50:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAFMk-00025A-Dm; Fri, 17 Feb 2006 18:50:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAFMb-0001xO-JJ; Fri, 17 Feb 2006 18:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25541;
	Fri, 17 Feb 2006 18:48:25 -0500 (EST)
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FAFb6-0001JR-QF; Fri, 17 Feb 2006 19:05:13 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1HNo29W010913
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 17 Feb 2006 23:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FAFMQ-0004Og-4m; Fri, 17 Feb 2006 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FAFMQ-0004Og-4m@stiedprstage1.ietf.org>
Date: Fri, 17 Feb 2006 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-content-01.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: The SDP (Session Description Protocol) Content Attribute
	Author(s)	: J. Hautakorpi, G. Camarillo
	Filename	: draft-ietf-mmusic-sdp-media-content-01.txt
	Pages		: 11
	Date		: 2006-2-17
	
This document defines a new Session Description Protocol (SDP) media-
level attribute, 'content'.  The 'content' attribute defines the
content of the media stream in more detailed level than the media
description line.  The sender of an SDP session description can
attach the 'content' attribute to one or more media streams.  The
receiving application can then treat each media stream differently
(e.g., show it on a big screen or small screen) based on their
content.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-media-content-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mmusic-sdp-media-content-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mmusic-sdp-media-content-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-2-17150633.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-media-content-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mmusic-sdp-media-content-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-2-17150633.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--NextPart--





From mmusic-bounces@ietf.org Sat Feb 18 02:16:41 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1FAMKf-0006hZ-Cd; Sat, 18 Feb 2006 02:16:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1FAMKd-0006ge-GZ
	for mmusic@megatron.ietf.org; Sat, 18 Feb 2006 02:16:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26637
	for <mmusic@ietf.org>; Sat, 18 Feb 2006 02:14:48 -0500 (EST)
Received: from pne-smtpout1-sn2.hy.skanova.net ([81.228.8.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAMYo-0000Sk-Vx
	for mmusic@ietf.org; Sat, 18 Feb 2006 02:31:39 -0500
Received: from MISAN (213.64.230.47) by pne-smtpout1-sn2.hy.skanova.net
	(7.2.070) id 43EC8670001E56E6; Sat, 18 Feb 2006 08:16:04 +0100
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Gonzalo. Camarillo@ericsson. com" <Gonzalo.Camarillo@ericsson.com>
Date: Sat, 18 Feb 2006 08:16:05 +0100
Message-ID: <GLEFKJBKNILEBOELNIBIOEIODFAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <E1FAFMQ-0004Og-4m@stiedprstage1.ietf.org>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
Subject: [MMUSIC] Accessibility related parameters in
	draft-ietf-mmusic-sdp-media-content-01.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Gonzalo and all,

I saw that you now have two accessibility related features described in the
sdp-media-contents specification. I am glad that you have picked up these
needs.
It is the "sl" token for sign language and the "txp" token for textphone
media.

I think the draft is good. I just have one terminology question and one
timing question, and a general usage discussion:

Terminology:
------------
You use "TDD" as a term for an analogue text telephone. In my view, TDD is a
US term for a specific type of text telephone.
I suggest that you adopt the same terminology as RFC 3351, and simply call
it a "textphone".

This is how RFC 3351 defines it:

"Textphone: Sometimes called a TTY (teletypewriter), TDD (telecommunications
device for the deaf)
or a minicom, a textphone enables a deaf, hard of hearing or speech-impaired
person to place a call to a telephone or another textphone."

In order to not confuse the reader we could avoid using the term "textphone"
for IP based terminals with full text presentation capabilities. I suggest
to use the clumsy but more general "real-time text capable terminal".

Thus, my proposal is to change the definition of "txp" in section 5 to:

txp: This indicates that the media stream is originated from a textphone,
      and it requires special behavior from the receiving application.
      Typical use case for this is e.g., a connection where one endpoint
      is an analog textphone, and the other one is a native IP based real
      time text capable terminal.

And the use of it in section 10 to:

   txp                          RFC xxxx  Media originated from a textphone


Timing
------
The idea is to define detailed usage of the media content attributes in
other RFC:s
and hook them into the IANA sub-register for the media-content attribute, as
described in section 10.
For the "txp" detailed definition, we could take it into the on-going work
with ietf-draft-sipping-toip , but that gives us an external dependency for
timing of the approval of the sdp-media-content specification.
Do you recommend to make the definition of "txp" in the sipping-toip
specification or in a small separate specification dedicated for that
purpose?

Usage
-----
You have pushed the usage concerns to the specifications listed in section
10, so even if I start a discussion here I realize that you can go on and
finalizing this draft without too much concern over usage.
Anyway, here are some initial thoughts about usage of the "txp" value.
I know that the idea for usage of this parameter is for indicating
limitations in presentation and communication capabilities of the analogue
textphones behind a gateway. We assume that the real-time text capable
terminal on the IP side has full duplex text capability, rich character set
and a speed of transmission that is much more than human input produces.
There may be a need to indicate the limitations when in contact with an
analogue textphone.

But I would like to warn for too much automatic action. The variations
between different analogue textphones may be too wide for that:

-Some textphones are strictly half duplex. Only one can transmit at a time.
Users apply strict turn-taking rules.
-Some textphones have a way for the receiver to indicate a desire to type.
"Interrupt"
-Some textphones communicate in full duplex, but merge transmitted text and
received text in the same line in the same display window.
-Some textphones communicate in full duplex and separate display from
reception and transmission so that the full duplex capability can be used
fully.
-Most textphones allow alternating between voice and text during a call.
Some are text only and some can handle simultaneous voice and text.
-Most textphones use national character sets. 7-bit or even more restricted.
Only a few use Unicode.
-Some textphones can only transmit around 4 characters per second, while
others can transmit 120 characters per second.
Conclusion: The parameter is good, it can be used at least for a indication
in the user interface that there may be restrictions in the presentation and
transmission capabilities of the other terminal. sipping-toip can define
this if timing of progress of the two drafts are favourable.


Regards
Gunnar
----------------------------------------------------------------------------
-
Gunnar Hellstrom, Omnitor
gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
Mob: +46 708 204 288
Phone: +46 8 556 002 03
www.omnitor.se <http://www.omnitor.se>


-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]On Behalf
Of Internet-Drafts@ietf.org
Sent: Saturday, February 18, 2006 12:50 AM
To: i-d-announce@ietf.org
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-content-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Multiparty Multimedia Session Control
Working Group of the IETF.

	Title		: The SDP (Session Description Protocol) Content Attribute
	Author(s)	: J. Hautakorpi, G. Camarillo
	Filename	: draft-ietf-mmusic-sdp-media-content-01.txt
	Pages		: 11
	Date		: 2006-2-17

This document defines a new Session Description Protocol (SDP) media-
level attribute, 'content'.  The 'content' attribute defines the
content of the media stream in more detailed level than the media
description line.  The sender of an SDP session description can
attach the 'content' attribute to one or more media streams.  The
receiving application can then treat each media stream differently
(e.g., show it on a big screen or small screen) based on their
content.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-media-content-01.t
xt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mmusic-sdp-media-content-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mmusic-sdp-media-content-01.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 21 09:43:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBYju-0001GO-Dl; Tue, 21 Feb 2006 09:43:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBYjt-0001G9-1n
	for mmusic@ietf.org; Tue, 21 Feb 2006 09:43:41 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBYjq-0004xd-6d
	for mmusic@ietf.org; Tue, 21 Feb 2006 09:43:41 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7D1EC4F0001; Tue, 21 Feb 2006 15:43:37 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Feb 2006 15:43:37 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Feb 2006 15:43:36 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id B1A9E286D;
	Tue, 21 Feb 2006 16:43:36 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 7B3DA1AB94C;
	Tue, 21 Feb 2006 16:43:36 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 1F22E1AB88E;
	Tue, 21 Feb 2006 16:43:36 +0200 (EET)
Message-ID: <43FB270F.3030404@ericsson.com>
Date: Tue, 21 Feb 2006 16:43:27 +0200
From: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Organization: Ericsson
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Subject: Re: [MMUSIC] Accessibility related parameters in
	draft-ietf-mmusic-sdp-media-content-01.txt
References: <GLEFKJBKNILEBOELNIBIOEIODFAA.gunnar.hellstrom@omnitor.se>
In-Reply-To: <GLEFKJBKNILEBOELNIBIOEIODFAA.gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 21 Feb 2006 14:43:37.0016 (UTC)
	FILETIME=[32952380:01C636F5]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Gunnar,

Thank you for your feedback. Find my comments below:

> You use "TDD" as a term for an analogue text telephone. In my view, TDD is a
> US term for a specific type of text telephone.
> I suggest that you adopt the same terminology as RFC 3351, and simply call
> it a "textphone".

Good comment. I'll change "TDD" to "textphone", as you have indicated.

> For the "txp" detailed definition, we could take it into the on-going work
> with ietf-draft-sipping-toip , but that gives us an external dependency for
> timing of the approval of the sdp-media-content specification.

I'm sorry, I don't understand your problem. Do you think that the 
reference from ietf-draft-sipping-toip draft to sdp-media-content draft 
would slow the progress of ietf-draft-sipping-toip draft too much?

> Usage
> -----
> You have pushed the usage concerns to the specifications listed in section
> 10, so even if I start a discussion here I realize that you can go on and
> finalizing this draft without too much concern over usage.
 >
> Anyway, here are some initial thoughts about usage of the "txp" value.

I think that your thoughts about usage were fine. If you want, you can 
specify the usage of "txp" value on some other draft, e.g. in 
ietf-draft-sipping-toip.


-- 
Jani H.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 21 15:35:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBeEJ-0008Qp-RM; Tue, 21 Feb 2006 15:35:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBeEJ-0008Qe-8x
	for mmusic@ietf.org; Tue, 21 Feb 2006 15:35:27 -0500
Received: from pne-smtpout1-sn1.fre.skanova.net ([81.228.11.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBeEH-0006zi-Tk
	for mmusic@ietf.org; Tue, 21 Feb 2006 15:35:27 -0500
Received: from MISAN (213.64.230.47) by pne-smtpout1-sn1.fre.skanova.net
	(7.2.070) id 43F9BC6700067B99; Tue, 21 Feb 2006 21:35:24 +0100
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Jani Hautakorpi \(JO/LMF\)" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility related parameters
	indraft-ietf-mmusic-sdp-media-content-01.txt
Date: Tue, 21 Feb 2006 21:35:23 +0100
Message-ID: <GLEFKJBKNILEBOELNIBIMEPDDFAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <43FB270F.3030404@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
Content-Transfer-Encoding: Quoted-Printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Jani,

Thanks for positive reception of the comments.

There is one need for clarification left.
In section 10, IANA considerations, there is a list with references to RF=
C
xxxx for descriptions of the values
e.g.
    txp      RFC xxxx  Media is originated from a textphone

Explanation 1
----------------
I understand that so that you expect other specifications to appear and t=
ake
responsibility for describing the use of each parameter. Their RFC number=
s
will be registered in the table.

Explanation 2
---------------
There could be another explanation: The table in section 10 could be the
initial table, and you regard the meaning of the values enough described =
in
the media-content specification. Then all xxxx would point at the
media-content specification.


What is our intention? It could be suitable with an RFC-editor note about
the meaning of XXXX and how it shall be handled.

Timing
------
Yes, I was thinking that if we bring in a reference to "txp" in the
sipping-toip specification, then we need to wait until media-content is
published and the table of values registered by IANA until we can proceed=
 to
publication.


Regards
Gunnar

-------------------------------------------------------------------------=
---
-
Gunnar Hellstr=F6m, Omnitor
gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
Mob: +46 708 204 288
Phone: +46 8 556 002 03
www.omnitor.se <http://www.omnitor.se>


-----Original Message-----
From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
Sent: Tuesday, February 21, 2006 3:43 PM
To: Gunnar Hellstrom
Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
Subject: Re: [MMUSIC] Accessibility related parameters
indraft-ietf-mmusic-sdp-media-content-01.txt


Hi Gunnar,

Thank you for your feedback. Find my comments below:

> You use "TDD" as a term for an analogue text telephone. In my view, TDD=
 is
a
> US term for a specific type of text telephone.
> I suggest that you adopt the same terminology as RFC 3351, and simply c=
all
> it a "textphone".

Good comment. I'll change "TDD" to "textphone", as you have indicated.

> For the "txp" detailed definition, we could take it into the on-going w=
ork
> with ietf-draft-sipping-toip , but that gives us an external dependency
for
> timing of the approval of the sdp-media-content specification.

I'm sorry, I don't understand your problem. Do you think that the
reference from ietf-draft-sipping-toip draft to sdp-media-content draft
would slow the progress of ietf-draft-sipping-toip draft too much?

> Usage
> -----
> You have pushed the usage concerns to the specifications listed in sect=
ion
> 10, so even if I start a discussion here I realize that you can go on a=
nd
> finalizing this draft without too much concern over usage.
 >
> Anyway, here are some initial thoughts about usage of the "txp" value.

I think that your thoughts about usage were fine. If you want, you can
specify the usage of "txp" value on some other draft, e.g. in
ietf-draft-sipping-toip.


--
Jani H.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 21 17:21:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBft1-0007Yc-5X; Tue, 21 Feb 2006 17:21:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBft0-0007YX-1y
	for mmusic@ietf.org; Tue, 21 Feb 2006 17:21:34 -0500
Received: from brixcorp.brixnet.com ([63.122.27.50]
	helo=brixmail.ma.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBfsz-0005pr-DH
	for mmusic@ietf.org; Tue, 21 Feb 2006 17:21:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-02.txt 
Date: Tue, 21 Feb 2006 17:21:30 -0500
Message-ID: <DA7323DD48676E4CAF5C4450D4422541E45358@brixmail.ma.brixnet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-02.txt 
Thread-Index: AcXw+lIMLD99BEqcRZaReAyTFZrCmxGNqhHg
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "Colin Perkins" <csp@csperkins.org>,
	"IETF MMUSIC working group" <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Colin,

Thanks for the comments. Please see my answers below.

Regards,
Kaynam=20

> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org] On Behalf Of Colin Perkins
> Sent: Thursday, November 24, 2005 8:23 AM
> To: IETF MMUSIC working group
> Subject: Re: [MMUSIC] I-D=20
> ACTION:draft-ietf-mmusic-media-loopback-02.txt=20
>=20
> On 8 Nov 2005, at 23:50, Internet-Drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts=20
> > directories.
> > This draft is a work item of the Multiparty Multimedia=20
> Session Control=20
> > Working Group of the IETF.
> >
> > 	Title		: An Extension to the Session Description
> >                           Protocol (SDP) for Media Loopback
> > 	Author(s)	: K. Hedayat, et al.
> > 	Filename	: draft-ietf-mmusic-media-loopback-02.txt
> > 	Pages		: 17
> > 	Date		: 2005-11-8
> > =09
> > The wide deployment of VoIP and Video over IP services has
> >     introduced new challenges in managing and maintaining=20
> voice/video
> >     quality, reliability, and overall performance.  In particular,
> >     media delivery is an area that needs attention.  One method of
> >     meeting these challenges is monitoring the media delivery
> >     performance by looping media back to the transmitter.  This is
> >     typically referred to as "active monitoring" of=20
> services.   Media
> >     loopback is especially popular in ensuring the quality of=20
> > transport
> >     to the edge of a given VoIP or Video over IP service.  Today in
> >     networks that deliver real-time media, short of running=20
> 'ping' and
> >     'traceroute' to the edge, service providers are left without the
> >     necessary tools to actively monitor, manage, and=20
> diagnose quality
> >     issues with their service.  The extension defined=20
> herein adds new
> >     SDP media attributes which enables establishment of=20
> media sessions
> >     where the media is looped back to the transmitter. Such media
> >     sessions will serve as monitoring and troubleshooting tools by
> >     providing the means for measurement of more advanced VoIP and=20
> > Video
> >     Over IP performance metrics.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-media-
> > loopback-02.txt
>=20
> Some comments on this draft:
>=20
> 1) The description of how rtp-pkt-loopback interacts with=20
> normal RTP header processing should be expanded. The data is=20
> supposed to be re- encapsulated for transmission back to the=20
> source, but how that is done is not well-specified. Should=20
> the answering entity use the same payload format as the=20
> original, or should the data be transcoded or somehow=20
> encapsulated in a new stream of RTP packets? If the original=20
> format is used, how is packet loss handled (what if the=20
> payload format is aware of sequence numbers)? If=20
> encapsulating, what is the encapsulation format? How are=20
> path-MTU limitations handled?
We originally had a simpler concept of loopback and decided to change it
for more visibility into packet loss in both directions. Obviously based
on your input this approach is broken. I suggest going back to the
original approach where RTP packets are looped back without any changes
in the header but the SSRC. Packets are looped back in their original
format as soon as they arrived at the mirror endpoint. The mirror
endpoint only has to change the SSRC field. This approach improves the
performance as well.
>=20
> 2) How is congestion on the reverse path handled?
It should be handled similar to any other RTP stream generated by the
endpoint.
>=20
> 3) The security considerations should discuss how to avoid=20
> packet bombing an unsuspecting third party. The draft states=20
> that authentication is needed, but I think it needs to=20
> provide more details (e.g. give an example of what sort of=20
> authentication can be used; how it prevent the problem).
The media loopback is accepted in the context of a call. The security
aspects must be treated similar to normal calls.
>=20
> Colin
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 22 01:34:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBnZf-0005dT-G6; Wed, 22 Feb 2006 01:34:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBnZe-0005dN-Hf
	for mmusic@ietf.org; Wed, 22 Feb 2006 01:34:06 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBnZb-0002Oz-KJ
	for mmusic@ietf.org; Wed, 22 Feb 2006 01:34:06 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BBACF4F0001; Wed, 22 Feb 2006 07:34:02 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Feb 2006 07:34:02 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Feb 2006 07:34:01 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 111E0260D;
	Wed, 22 Feb 2006 08:34:02 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CDCBB1AB94C;
	Wed, 22 Feb 2006 08:34:01 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 51F721AB8EE;
	Wed, 22 Feb 2006 08:34:01 +0200 (EET)
Message-ID: <43FC05D8.5000301@ericsson.com>
Date: Wed, 22 Feb 2006 08:34:00 +0200
From: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Organization: Ericsson
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Subject: Re: [MMUSIC] Accessibility related parameters
	indraft-ietf-mmusic-sdp-media-content-01.txt
References: <GLEFKJBKNILEBOELNIBIMEPDDFAA.gunnar.hellstrom@omnitor.se>
In-Reply-To: <GLEFKJBKNILEBOELNIBIMEPDDFAA.gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 22 Feb 2006 06:34:02.0129 (UTC)
	FILETIME=[F832D810:01C63779]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Gunnar,

> Explanation 2
> ---------------
> There could be another explanation: The table in section 10 could be the
> initial table, and you regard the meaning of the values enough described in
> the media-content specification. Then all xxxx would point at the
> media-content specification.

This is the right explanation. We're planning to register the coming RFC 
number of this draft in the table. But if you want to specify the usage 
of "txp" in some other draft, we can make an informational reference 
from this draft to that one.

> What is our intention? It could be suitable with an RFC-editor note about
> the meaning of XXXX and how it shall be handled.

I'll add a note for RFC-editor.

> Yes, I was thinking that if we bring in a reference to "txp" in the
> sipping-toip specification, then we need to wait until media-content is
> published and the table of values registered by IANA until we can proceed to
> publication.

I guess this isn't a serious problem.


-- 
Jani H.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 22 05:53:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBrcD-0002QQ-RB; Wed, 22 Feb 2006 05:53:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBrcD-0002QI-0P
	for mmusic@ietf.org; Wed, 22 Feb 2006 05:53:01 -0500
Received: from uproxy.gmail.com ([66.249.92.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBrcA-0004mo-M1
	for mmusic@ietf.org; Wed, 22 Feb 2006 05:53:00 -0500
Received: by uproxy.gmail.com with SMTP id y2so759083uge
	for <mmusic@ietf.org>; Wed, 22 Feb 2006 02:52:57 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:cc:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index;
	b=qaJXdoPmI5/Sa52xb6Z3D/iU2dHU0ZzXEgB1nnpv0Bi4rWV79jt1nhUA2FwKpYrXltOUwHujHs2lCcYYVevaV85IGMtLc5SnYw7/Xxi2VwUu0II+wLqVDPDR2UfofRwFeiA+naN6rxRRD7SDhU9VLdeMwkjvKMdbKJR4NjtvQqc=
Received: by 10.66.252.6 with SMTP id z6mr2115464ugh;
	Wed, 22 Feb 2006 02:52:57 -0800 (PST)
Received: from solstice ( [82.197.192.189])
	by mx.gmail.com with ESMTP id c1sm4804377ugf.2006.02.22.02.52.57;
	Wed, 22 Feb 2006 02:52:57 -0800 (PST)
From: "Arnoud van Wijk" <degodefroi@gmail.com>
To: "'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>,
	"'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>
Subject: RE: [MMUSIC] Accessibility related
	parametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Wed, 22 Feb 2006 11:53:18 +0100
Message-ID: <001d01c6379e$31030600$2500a8c0@solstice>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <43FC05D8.5000301@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Thread-Index: AcY3ep5rovFd9tPRSe6vtF4atTxEoAAI0Jmg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

I think if we say in the ToIP draft that it is advised to use txp label to
indicate a texttelephone in the call, it should not delay the RFC.
The only thing is that when the RFC is released, will it be possible to swap
the reference to the media content draft with the media content RFC? 

Greetz

Arnoud

> -----Original Message-----
> From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> Sent: woensdag 22 februari 2006 7:34
> To: Gunnar Hellstrom
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
> 
> Gunnar,
> 
> > Explanation 2
> > ---------------
> > There could be another explanation: The table in section 10 could be the
> > initial table, and you regard the meaning of the values enough described
> in
> > the media-content specification. Then all xxxx would point at the
> > media-content specification.
> 
> This is the right explanation. We're planning to register the coming RFC
> number of this draft in the table. But if you want to specify the usage
> of "txp" in some other draft, we can make an informational reference
> from this draft to that one.
> 
> > What is our intention? It could be suitable with an RFC-editor note
> about
> > the meaning of XXXX and how it shall be handled.
> 
> I'll add a note for RFC-editor.
> 
> > Yes, I was thinking that if we bring in a reference to "txp" in the
> > sipping-toip specification, then we need to wait until media-content is
> > published and the table of values registered by IANA until we can
> proceed to
> > publication.
> 
> I guess this isn't a serious problem.
> 
> 
> --
> Jani H.
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Wed Feb 22 18:24:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC3LB-0007Zp-9l; Wed, 22 Feb 2006 18:24:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC3LA-0007Zk-9K
	for mmusic@ietf.org; Wed, 22 Feb 2006 18:24:12 -0500
Received: from pne-smtpout1-sn1.fre.skanova.net ([81.228.11.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC3L8-0001bO-TA
	for mmusic@ietf.org; Wed, 22 Feb 2006 18:24:12 -0500
Received: from MISAN (213.64.230.47) by pne-smtpout1-sn1.fre.skanova.net
	(7.2.070) id 43F9BC67000B3E33; Thu, 23 Feb 2006 00:24:07 +0100
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Arnoud van Wijk" <degodefroi@gmail.com>,
	"'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility related
	parametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Thu, 23 Feb 2006 00:24:06 +0100
Message-ID: <GLEFKJBKNILEBOELNIBIIEAADGAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <001d01c6379e$31030600$2500a8c0@solstice>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Jani,
OK, I understand. Your idea was to have the meaning of the values enough
described in the sdp-media-content specification.

Then we should add a few more words to explain suitable behaviour of a
client receiving the "txp" indicator.

I assume the most common case would be in connection with the m=text media
description.

I dislike to drag the variations of PSTN textphones into requirements on
variations in behaviour of SIP clients. But I cannot figure out how a SIP
client shall react on reception of the txp indication. The expected
variation is too wide with:
-half duplex or full duplex or interruptable half duplex,
-split window or common window,
-simultaneous voice and text or alternating voice and text,
-national character set or further limited or Unicode
-4 or 6 or 10 or 30 or 120 characters per second.

It is tempting to ask for a subparameter for the type of textphone that is
commected beyond the gateway.
One architecturally ugly way to do it would be to ask gateway implementors
to generate a
RFC 2833bisdata event in an audio channel giving information on the type of
textphone in contact, and the application would then have knowledge about
what characteristics to use towards them.
See section 2.7.1 in:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-06.txt



We could make it easy for us and just specify : "txp" indicates that the
other party has a textphone, and that the user should be made aware that
presentation and communication restrictions may apply.

So, the phrase in section 5 deascribing txp could be extended to end like
this:

	Typical use case
      for this is e.g., a connection where one endpoint is an analog
      textphone, and the other one is a native IP based text telephone.
	The user should be made aware that presentation and communication
	limitations exist.


?

Gunnar



----------------------------------------------------------------------------
-
Gunnar Hellstrom, Omnitor
gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
Mob: +46 708 204 288
Phone: +46 8 556 002 03
www.omnitor.se <http://www.omnitor.se>


-----Original Message-----
From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
Sent: Wednesday, February 22, 2006 11:53 AM
To: 'Jani Hautakorpi (JO/LMF)'; 'Gunnar Hellstrom'
Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
Subject: RE: [MMUSIC] Accessibility related
parametersindraft-ietf-mmusic-sdp-media-content-01.txt


I think if we say in the ToIP draft that it is advised to use txp label to
indicate a texttelephone in the call, it should not delay the RFC.
The only thing is that when the RFC is released, will it be possible to swap
the reference to the media content draft with the media content RFC?

Greetz

Arnoud

> -----Original Message-----
> From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> Sent: woensdag 22 februari 2006 7:34
> To: Gunnar Hellstrom
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
>
> Gunnar,
>
> > Explanation 2
> > ---------------
> > There could be another explanation: The table in section 10 could be the
> > initial table, and you regard the meaning of the values enough described
> in
> > the media-content specification. Then all xxxx would point at the
> > media-content specification.
>
> This is the right explanation. We're planning to register the coming RFC
> number of this draft in the table. But if you want to specify the usage
> of "txp" in some other draft, we can make an informational reference
> from this draft to that one.
>
> > What is our intention? It could be suitable with an RFC-editor note
> about
> > the meaning of XXXX and how it shall be handled.
>
> I'll add a note for RFC-editor.
>
> > Yes, I was thinking that if we bring in a reference to "txp" in the
> > sipping-toip specification, then we need to wait until media-content is
> > published and the table of values registered by IANA until we can
> proceed to
> > publication.
>
> I guess this isn't a serious problem.
>
>
> --
> Jani H.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic




_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Thu Feb 23 04:03:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCCNR-0004IP-Lm; Thu, 23 Feb 2006 04:03:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCCNP-0004I9-TC
	for mmusic@ietf.org; Thu, 23 Feb 2006 04:03:07 -0500
Received: from zproxy.gmail.com ([64.233.162.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCCNP-0008Ao-Ey
	for mmusic@ietf.org; Thu, 23 Feb 2006 04:03:07 -0500
Received: by zproxy.gmail.com with SMTP id 8so2954nzo
	for <mmusic@ietf.org>; Thu, 23 Feb 2006 01:03:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=s2snQj9jxXRSAOoVzFq1gfohUb97dvBi2uXe7MC5HY5dYn8W/IYEniPJvyui8yYMYqlngZbhGKsEwF+E7y8NzZe3CRTuXFsjCdXhHosK15PJkxrbOE8eCiyiO2ldoLt4z1oZiPy6dXOLbVnaQngAoO36rxX3UJG9k7VKktLwfwM=
Received: by 10.37.15.25 with SMTP id s25mr33525nzi;
	Thu, 23 Feb 2006 01:03:06 -0800 (PST)
Received: by 10.36.75.4 with HTTP; Thu, 23 Feb 2006 01:03:06 -0800 (PST)
Message-ID: <8b2b8b9e0602230103j57480cbchc9c11bc57248506@mail.gmail.com>
Date: Thu, 23 Feb 2006 17:03:06 +0800
From: "zuo bf" <zuobf.bupt@gmail.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>, mmusic <mmusic@ietf.org>
Subject: [MMUSIC] Comments on ICE version 06
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1587503239=="
Errors-To: mmusic-bounces@ietf.org

--===============1587503239==
Content-Type: multipart/alternative; 
	boundary="----=_Part_4898_14032481.1140685386815"

------=_Part_4898_14032481.1140685386815
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,
  First thanks for the great work. Then i'd like to give out the points at
which i am not clear.

1. Should all components in a candidate are in the same realm or are derive=
d
using a same way ?
And Does the derived transport address need to compare with every available
transport addresses ?

>From the draft and example you give, i think you mean it's same, but I got
confused here. In page14,
there is no explicit require for that, and the candidate comparison just
compare transport address with
transport address in another candidate, there is the point, as we compare
candidate in this way, why
the process for getting a peer-derived candidate different, in that process
we restrict that the derived address
doesn't equal any available transport addresses (even they have different
component id), but isn't there a
chance that two candidate have partial same transport addresses ? Consider
the scenario below :
(This is a strange scenario, but i think it could be used for demo)
                               Phy1
|--------- | R1 |--------------------------------| R2 |
|          --------                                -------
|             |                                       |
|          -------                                 -------
|          | H1 |                                | H2 |
|          -------                                 -------
|             |                                       |
|          -------                                 -------
|----------| R3 |--------------------------------| R4 |
           -------           Phy2              -------
H1 and H2 are both in two realms, and a candidate comprised of two realm
address may pass the STUN connection
check, and even more there could a route H1-->R1--->R3----->R4----->H2,  an=
d
if this route is better than the H1--->R1-->
R2--->H2 one, and better than the H1--->R3--->R4---->H2 because of some
factor like bandwith, then the desired candidate
can be comprised of two realm addresses, in that situation there is a chanc=
e
of collision with the peer derive procedure:
More clearly, assume Phy1 is an IPv4 network, Phy2 is an IPv6 network, H1
and H2 are dual stack clients but not capable of
conversion between IPv4 and IPv6. So the initial candidate list before any
peer-derived one added could be:
candidate1: H1_IPv4_transport_addr_1 H1_IPv6_transport_addr_2
candidate2: H1_IPv4_transport_addr_1 H1_IPv4_transport_addr_2
candidate3: H1_IPv6_transport_addr_1 H1_IPv6_transport_addr_2
We know routes H1-->R1--->R3----->R4----->H2 and H1--->R3--->R4---->H2 are
good for the two component respectively, so we want a
derived candidate4:R3_IPv6_transport_addr_1 H1_IPv6_transport_addr_2, but
because H1_IPv6_transport_addr_2 already exists
in several candidates,  and this address can't trigger the add action for i=
t
to be added to the newly created candidate.

2. De-allocation of resources

This is just a riminder, in page 39 there is

   5.  If the removed candidate was a TURN-derived candidate, the agent
       SHOULD de-allocate its transport addresses from the TURN server.

But because there is a possibility of proxy forking, so an offer/answer exc=
hange
within a single dialog doesn't mean that the TURN-derived candidate
won't be used
by other early dialogs or so.

3. When receive an update offer, why not trust the other agent ?

Also page 39, Receiving the Offer and Sending an Answer

Why not choose the a=3Dremote-candidate directly, unless the offer is not s=
ent for
just promoting one candidate to active, otherwise the pair that the
offer indicate
through m/c line and a=3Dremote-candidate Should be the most desired
one, and because of the
peer-derive process when there's symmetric NAT exist, the undesirable
candidate pair could
be valid ahead of the the desired one in the answer side, does that
mean the answer should
use that candidate only because it hasn't received the response for
the desired pair's request,
but isn't there a 100% chance for that response to come ?

4. Role of offerer and answerer ?

In page 33, there is:

   Recall that, for each candidate pair, one agent plays the role of
   offerer, and the other of answerer.  For peer-derived candidates, the
   agent that receives the STUN request and follows the processing in
   this section acts as the answerer.
If the derived pair is the desired one, and the offerer and answerer role i=
s
reversed, which one should send the updated offer ?

Thanks for your work, and hope the tcp support will be added later, my corp
block all UDP connections. Thanks again, really great work.

Sincerely,
zuobf

------=_Part_4898_14032481.1140685386815
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,<br>&nbsp; First thanks for the great work. Then i'd like to give out th=
e points at which i am not clear.<br><br>1. Should all components in a cand=
idate are in the same realm or are derived using a same way ?<br>And Does t=
he derived transport address need to compare with every available transport=
 addresses ?
<br><br>From the draft and example you give, i think you mean it's same, bu=
t I got confused here. In page14,<br>there is no explicit require for that,=
 and the candidate comparison just compare transport address with<br>transp=
ort address in another candidate, there is the point, as we compare candida=
te in this way, why
<br>the process for getting a peer-derived candidate different, in that pro=
cess we restrict that the derived address<br>doesn't equal any available tr=
ansport addresses (even they have different component id), but isn't there =
a
<br>chance that two candidate have partial same transport addresses ? Consi=
der the scenario below :<br>(This is a strange scenario, but i think it cou=
ld be used for demo)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phy1<br>|--------- |=
 R1 |--------------------------------| R2 |
<br>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------<br>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>|&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; -------<br>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
H1 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | H2 |
<br>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------<br>|&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>|&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; -------<br>|----------| R3 |--------------------------------| R4=
 |
<br>&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phy2&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------<br>H1 and H=
2 are both in two realms, and a candidate comprised of two realm address ma=
y pass the STUN connection<br>check, and even more there could a route H1--=
&gt;R1---&gt;R3-----&gt;R4-----&gt;H2,&nbsp; and if this route is better th=
an the H1---&gt;R1--&gt;
<br>R2---&gt;H2 one, and better than the H1---&gt;R3---&gt;R4----&gt;H2 bec=
ause of some factor like bandwith, then the desired candidate<br>can be com=
prised of two realm addresses, in that situation there is a chance of colli=
sion with the peer derive procedure:
<br>More clearly, assume Phy1 is an IPv4 network, Phy2 is an IPv6 network, =
H1 and H2 are dual stack clients but not capable of<br>conversion between I=
Pv4 and IPv6. So the initial candidate list before any peer-derived one add=
ed could be:
<br>candidate1: H1_IPv4_transport_addr_1 H1_IPv6_transport_addr_2<br>candid=
ate2: H1_IPv4_transport_addr_1 H1_IPv4_transport_addr_2<br>candidate3: H1_I=
Pv6_transport_addr_1 H1_IPv6_transport_addr_2<br>We know routes H1--&gt;R1-=
--&gt;R3-----&gt;R4-----&gt;H2 and H1---&gt;R3---&gt;R4----&gt;H2 are good =
for the two component respectively, so we want a
<br>derived candidate4:R3_IPv6_transport_addr_1 H1_IPv6_transport_addr_2, b=
ut because H1_IPv6_transport_addr_2 already exists<br>in several candidates=
,&nbsp; and this address can't trigger the add action for it to be added to=
 the newly created candidate.
<br><br>2. De-allocation of resources<br><br>This is just a riminder, in pa=
ge 39 there is <br><pre>   5.  If the removed candidate was a TURN-derived =
candidate, the agent<br>       SHOULD de-allocate its transport addresses f=
rom the TURN server.
<br><br>But because there is a possibility of proxy forking, so an offer/an=
swer exchange<br>within a single dialog doesn't mean that the TURN-derived =
candidate won't be used<br>by other early dialogs or so.<br><br>3. When rec=
eive an update offer, why not trust the other agent ?
<br><br>Also page 39, Receiving the Offer and Sending an Answer<br><br>Why =
not choose the a=3Dremote-candidate directly, unless the offer is not sent =
for<br>just promoting one candidate to active, otherwise the pair that the =
offer indicate
<br>through m/c line and a=3Dremote-candidate Should be the most desired on=
e, and because of the<br>peer-derive process when there's symmetric NAT exi=
st, the undesirable candidate pair could<br>be valid ahead of the the desir=
ed one in the answer side, does that mean the answer should
<br>use that candidate only because it hasn't received the response for the=
 desired pair's request,<br>but isn't there a 100% chance for that response=
 to come ?<br><br>4. Role of offerer and answerer ?<br><br>In page 33, ther=
e is:
<br><br>   Recall that, for each candidate pair, one agent plays the role o=
f<br>   offerer, and the other of answerer.  For peer-derived candidates, t=
he<br>   agent that receives the STUN request and follows the processing in
<br>   this section acts as the answerer.
<br>If the derived pair is the desired one, and the offerer and answerer ro=
le is<br>reversed, which one should send the updated offer ?<br><br>Thanks =
for your work, and hope the tcp support will be added later, my corp<br>
block all UDP connections. Thanks again, really great work.<br><br>Sincerel=
y,<br>zuobf<br></pre><br><br>

------=_Part_4898_14032481.1140685386815--


--===============1587503239==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============1587503239==--




From mmusic-bounces@ietf.org Thu Feb 23 07:46:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCFrZ-0006jQ-A2; Thu, 23 Feb 2006 07:46:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCFrX-0006jI-RE
	for mmusic@ietf.org; Thu, 23 Feb 2006 07:46:27 -0500
Received: from nproxy.gmail.com ([64.233.182.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCFrV-0007kF-Tv
	for mmusic@ietf.org; Thu, 23 Feb 2006 07:46:27 -0500
Received: by nproxy.gmail.com with SMTP id n28so44247nfc
	for <mmusic@ietf.org>; Thu, 23 Feb 2006 04:46:24 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:cc:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:in-reply-to:thread-index;
	b=arAg7A9hbftpP+smM3cCIk7lU27LNhD6tNTW8Ze51pZO+zNhEW6gMLD++/YCRP2ayoKn7D9+l13yqo+Sfd4FACuoJz3iyAoAkDVZQUdDkzxZUZPYQ/wqzQOSLWv8PIT1qHXxKVa97cFl+7Sy+XeBDXMh8YrVB7iXJ25D2jCJomU=
Received: by 10.48.255.10 with SMTP id c10mr2340376nfi;
	Thu, 23 Feb 2006 04:46:24 -0800 (PST)
Received: from solstice ( [82.197.192.189])
	by mx.gmail.com with ESMTP id m15sm146074nfc.2006.02.23.04.46.24;
	Thu, 23 Feb 2006 04:46:24 -0800 (PST)
From: "Arnoud van Wijk" <degodefroi@gmail.com>
To: "'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>,
	"'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility related
	parametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Thu, 23 Feb 2006 13:46:49 +0100
Message-ID: <004d01c63877$375949e0$2500a8c0@solstice>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
In-Reply-To: <GLEFKJBKNILEBOELNIBIIEAADGAA.gunnar.hellstrom@omnitor.se>
Thread-Index: AcY4BxOEO/vUfiiUTG67A2wsiP1LGwAboVUg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Gunnar, that is exactly what Jani and I mean here.

It has nothing to do with call mechanism/buffering etc. (RFC4103 already
offers changes in character transmission speed).
It is to alert the user that the media stream is originating from a PSTN
texttelephone.

You have to see it as a person who is used to bi-directional ToIP on a split
screen. Both users send and receive text simultaneously.
Then next call originates from a PSTN texttelephone and the user needs to be
aware that they have to wait until the other has finished typing and
indicates that it is the users turn now to type.

The txp label will also allow, depending on the user interface, to go from
split screen to a single screen, more or less behave like a PSTN
texttelephone. (and disallow cut and paste of more then 50 characters to
avoid flooding the PSTN textphone).
But it can just as well be a pop up window alerting the user that he or she
is connected to a PSTN texttelephone.

I am asuming that the callee knows the PSTN texttelephony etiquette.
(wait for turns, indicate GA or * or x when finished typing etc etc).

Greetz

Arnoud van Wijk

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> Sent: donderdag 23 februari 2006 0:24
> To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility related parametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
> 
> Jani,
> OK, I understand. Your idea was to have the meaning of the values enough
> described in the sdp-media-content specification.
> 
> Then we should add a few more words to explain suitable behaviour of a
> client receiving the "txp" indicator.
> 
> I assume the most common case would be in connection with the m=text media
> description.
> 
> I dislike to drag the variations of PSTN textphones into requirements on
> variations in behaviour of SIP clients. But I cannot figure out how a SIP
> client shall react on reception of the txp indication. The expected
> variation is too wide with:
> -half duplex or full duplex or interruptable half duplex,
> -split window or common window,
> -simultaneous voice and text or alternating voice and text,
> -national character set or further limited or Unicode
> -4 or 6 or 10 or 30 or 120 characters per second.
> 
> It is tempting to ask for a subparameter for the type of textphone that is
> commected beyond the gateway.
> One architecturally ugly way to do it would be to ask gateway implementors
> to generate a
> RFC 2833bisdata event in an audio channel giving information on the type
> of
> textphone in contact, and the application would then have knowledge about
> what characteristics to use towards them.
> See section 2.7.1 in:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-06.txt
> 
> 
> 
> We could make it easy for us and just specify : "txp" indicates that the
> other party has a textphone, and that the user should be made aware that
> presentation and communication restrictions may apply.
> 
> So, the phrase in section 5 deascribing txp could be extended to end like
> this:
> 
> 	Typical use case
>       for this is e.g., a connection where one endpoint is an analog
>       textphone, and the other one is a native IP based text telephone.
> 	The user should be made aware that presentation and communication
> 	limitations exist.
> 
> 
> ?
> 
> Gunnar
> 
> 
> 
> --------------------------------------------------------------------------
> --
> -
> Gunnar Hellstrom, Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> Mob: +46 708 204 288
> Phone: +46 8 556 002 03
> www.omnitor.se <http://www.omnitor.se>
> 
> 
> -----Original Message-----
> From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> Sent: Wednesday, February 22, 2006 11:53 AM
> To: 'Jani Hautakorpi (JO/LMF)'; 'Gunnar Hellstrom'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility related
> parametersindraft-ietf-mmusic-sdp-media-content-01.txt
> 
> 
> I think if we say in the ToIP draft that it is advised to use txp label to
> indicate a texttelephone in the call, it should not delay the RFC.
> The only thing is that when the RFC is released, will it be possible to
> swap
> the reference to the media content draft with the media content RFC?
> 
> Greetz
> 
> Arnoud
> 
> > -----Original Message-----
> > From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> > Sent: woensdag 22 februari 2006 7:34
> > To: Gunnar Hellstrom
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-
> mmusic-
> > sdp-media-content-01.txt
> >
> > Gunnar,
> >
> > > Explanation 2
> > > ---------------
> > > There could be another explanation: The table in section 10 could be
> the
> > > initial table, and you regard the meaning of the values enough
> described
> > in
> > > the media-content specification. Then all xxxx would point at the
> > > media-content specification.
> >
> > This is the right explanation. We're planning to register the coming RFC
> > number of this draft in the table. But if you want to specify the usage
> > of "txp" in some other draft, we can make an informational reference
> > from this draft to that one.
> >
> > > What is our intention? It could be suitable with an RFC-editor note
> > about
> > > the meaning of XXXX and how it shall be handled.
> >
> > I'll add a note for RFC-editor.
> >
> > > Yes, I was thinking that if we bring in a reference to "txp" in the
> > > sipping-toip specification, then we need to wait until media-content
> is
> > > published and the table of values registered by IANA until we can
> > proceed to
> > > publication.
> >
> > I guess this isn't a serious problem.
> >
> >
> > --
> > Jani H.
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> 



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Thu Feb 23 08:47:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCGoh-0001j9-9a; Thu, 23 Feb 2006 08:47:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCGog-0001j4-IR
	for mmusic@ietf.org; Thu, 23 Feb 2006 08:47:34 -0500
Received: from m5tmail1.m5t.com ([207.134.65.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCGoe-00020F-TO
	for mmusic@ietf.org; Thu, 23 Feb 2006 08:47:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6387F.572681C2"
Date: Thu, 23 Feb 2006 08:47:32 -0500
Message-ID: <83F34964B9BBA546BF2584D46870EB992011FE@m5tmail1.m5t.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Mixing Session Level and Media Level a=key-mgmt:mikey lines
Thread-Index: AcYyam1Pj/sTUjbsRQatYS5hCPetCwBYKHjgAAAKdfABLQJHEA==
From: "Pascal Dore" <pdore@m5t.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0aa23132abbc731e36938583486affe0
Subject: [MMUSIC] FW: Mixing Session Level and Media Level a=key-mgmt:mikey
	lines
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6387F.572681C2
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C6387F.572681C2"


------_=_NextPart_002_01C6387F.572681C2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Repost on behalf of Guylain Lavoie to mmusic since no answer received =
yet in msec mailing list.

=20

Thanks,

Pascal.D

________________________________

From: msec-bounces@securemulticast.org =
[mailto:msec-bounces@securemulticast.org] On Behalf Of Christian =
Beaulieu
Sent: 17 f=E9vrier 2006 09:07
To: msec@securemulticast.org
Subject: [MSEC] Mixing Session Level and Media Level a=3Dkey-mgmt:mikey =
lines

=20

From: Guylain Lavoie=20

Hi everyone,

=20

I have two questions related to the utilization of MIKEY with SDP.

=20

As stated in draft-ietf-mmusic-kmgmt-ext-15.txt, a single SRTP media =
stream generates two MIKEY crypto sessions. The first is outgoing and =
includes the locally known outgoing SSRC and ROC. The second is incoming =
and includes zeroed SSRC and ROC since they are not known. The MIKEY =
responder will later provide them in its MIKEY response.

=20

Now that being said, if a=3Dkey-mgmt:mikey line is located at the =
session level and there are two m=3D lines, the session level MIKEY =
exchange will contain four crypto sessions. Two for each of the SRTP =
streams. Here is the example.

=20

   v=3D0

   o=3Dalice 2891092738 2891092738 IN IP4 w-land.example.com

   s=3DCool stuff

   e=3Dalice@w-land.example.com

   t=3D0 0

   c=3DIN IP4 w-land.example.com

   a=3Dkey-mgmt:mikey AQAFgM0XflABZZZZZZZZZZZZZZZZZAy... <=3D=3D 4 CS

   m=3Daudio 49000 RTP/SAVP 98

   a=3Drtpmap:98 AMR/8000

   m=3Dvideo 52230 RTP/AVP 31

   a=3Drtpmap:31 H261/90000

=20

=20

draft-ietf-mmusic-kmgmt-ext-15.txt also states that if a key-mgmt =
attribute exists at the media level, the session level attribute MUST be =
ignored.

=20

Now, this puzzles me. If we reuse the previous example but with a single =
modification. If one of the media level also contains a =
a=3Dkey-mgmt:mikey line. How many crypto sessions will now be created =
within the session level MIKEY initiate message? Four or Two? Four for =
both media lines even if the first one also contains a =
a=3Dkey-mgmt:mikey line or two, only for the second media line.

=20

For example,

=20

   v=3D0

   o=3Dalice 2891092738 2891092738 IN IP4 w-land.example.com

   s=3DCool stuff

   e=3Dalice@w-land.example.com

   t=3D0 0

   c=3DIN IP4 w-land.example.com

   a=3Dkey-mgmt:mikey AQAFgM0XflABZZZZZZZZZZZZZZZZZAy... <=3D=3D 4 or 2 =
CS?

   m=3Daudio 49000 RTP/SAVP 98

   a=3Drtpmap:98 AMR/8000

   a=3Dkey-mgmt:mikey AQAFgM0XflABAAAAAAAAAAAAAAsAy... <=3D=3D 2 CS

   m=3Dvideo 52230 RTP/AVP 31

   a=3Drtpmap:31 H261/90000

=20

My second question is "What should we do if the media level MIKEY =
exchange fails while the session level MIKE exchanges is successful?". =
draft-ietf-mmusic-kmgmt-ext-15.txt says that the session level must be =
ignored. I assume that if the media level MIKEY exchange fails, then =
there will be no automatic fallback to the session level MIKEY exchange =
event if the answer to the first question is four. If the answer was =
two, then it becomes obvious that there is no fallback. I would expect =
that no fallback is possible (in all cases).

=20

Best Regards,

Guylain Lavoie

=20


------_=_NextPart_002_01C6387F.572681C2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-CA link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><a name=3D""><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Repost on behalf =
of </span></font></a><st1:PersonName
w:st=3D"on"><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;
 font-family:Arial;color:navy'>Guylain =
Lavoie</span></font></st1:PersonName><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'> to mmusic since no answer received yet in msec mailing =
list.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks,<o:p></o:p></span></font></p>=


<div>

<p><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>Pascal.D<o:p></o:p></span></font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-size:12.0pt'>

<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
msec-bounces@securemulticast.org =
[mailto:msec-bounces@securemulticast.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Christian =
Beaulieu<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 17 f=E9vrier 2006 =
09:07<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
msec@securemulticast.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [MSEC] Mixing =
Session
Level and Media Level a=3Dkey-mgmt:mikey lines</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
<st1:PersonName w:st=3D"on">Guylain Lavoie</st1:PersonName> =
</span></font><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>Hi everyone,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>I have two questions related to the =
utilization of
MIKEY with SDP.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>As stated in =
draft-ietf-mmusic-kmgmt-ext-15.txt, a
single SRTP media stream generates two MIKEY crypto sessions. The first =
is
outgoing and includes the locally known outgoing SSRC and ROC. The =
second is
incoming and includes zeroed SSRC and ROC since they are not known. The =
MIKEY
responder will later provide them in its MIKEY =
response.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>Now that being said, if a=3Dkey-mgmt:mikey =
line is
located at the session level and there are two m=3D lines, the session =
level
MIKEY exchange will contain four crypto sessions. Two for each of the =
SRTP
streams. Here is the example.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; =
v=3D0<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; o=3D<st1:place =
w:st=3D"on"><st1:City w:st=3D"on">alice</st1:City></st1:place>
2891092738 2891092738 IN IP4 =
w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; s=3DCool =
stuff<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; =
e=3Dalice@w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; t=3D0 =
0<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; c=3DIN IP4 =
w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Dkey-mgmt:mikey
AQAFgM0XflABZZZZZZZZZZZZZZZZZAy... &lt;=3D=3D 4 =
CS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; m=3Daudio 49000 RTP/SAVP =
98<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Drtpmap:98 =
AMR/8000<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; m=3Dvideo 52230 RTP/AVP =
31<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Drtpmap:31 =
H261/90000<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>draft-ietf-mmusic-kmgmt-ext-15.txt also =
states that if
a key-mgmt attribute exists at the media level, the session level =
attribute
MUST be ignored.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>Now, this puzzles me. If we reuse the =
previous example
but with a single modification. If one of the media level also contains =
a a=3Dkey-mgmt:mikey
line. How many crypto sessions will now be created within the session =
level
MIKEY initiate message? Four or Two? Four for both media lines even if =
the
first one also contains a a=3Dkey-mgmt:mikey line or two, only for the =
second
media line.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>For example,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; =
v=3D0<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; o=3D<st1:place =
w:st=3D"on"><st1:City w:st=3D"on">alice</st1:City></st1:place>
2891092738 2891092738 IN IP4 =
w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; s=3DCool =
stuff<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; =
e=3Dalice@w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; t=3D0 =
0<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; c=3DIN IP4 =
w-land.example.com<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Dkey-mgmt:mikey
AQAFgM0XflABZZZZZZZZZZZZZZZZZAy... &lt;=3D=3D 4 or 2 =
CS?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; m=3Daudio 49000 RTP/SAVP =
98<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Drtpmap:98 =
AMR/8000<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Dkey-mgmt:mikey
AQAFgM0XflABAAAAAAAAAAAAAAsAy... &lt;=3D=3D 2 =
CS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; m=3Dvideo 52230 RTP/AVP =
31<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;&nbsp; a=3Drtpmap:31 =
H261/90000<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>My second question is &#8220;What should we =
do if the
media level MIKEY exchange fails while the session level MIKE exchanges =
is
successful?&#8221;. draft-ietf-mmusic-kmgmt-ext-15.txt says that the =
session
level must be ignored. I assume that if the media level MIKEY exchange =
fails,
then there will be no automatic fallback to the session level MIKEY =
exchange
event if the answer to the first question is four. If the answer was =
two, then
it becomes obvious that there is no fallback. I would expect that no =
fallback
is possible (in all cases).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>Best Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:PersonName w:st=3D"on"><font size=3D3 =
face=3D"Times New Roman"><span
 lang=3DEN-US style=3D'font-size:12.0pt'>Guylain =
Lavoie</span></font></st1:PersonName><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_002_01C6387F.572681C2--

------_=_NextPart_001_01C6387F.572681C2
Content-Type: text/plain;
	name="ATT521743.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT521743.txt
Content-Disposition: inline;
	filename="ATT521743.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1zZWMgbWFp
bGluZyBsaXN0DQptc2VjQHNlY3VyZW11bHRpY2FzdC5vcmcNCmh0dHA6Ly9zaXgucGFpcmxpc3Qu
bmV0L21haWxtYW4vbGlzdGluZm8vbXNlYw0K

------_=_NextPart_001_01C6387F.572681C2
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

------_=_NextPart_001_01C6387F.572681C2--




From mmusic-bounces@ietf.org Thu Feb 23 09:23:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCHMx-0000PT-5t; Thu, 23 Feb 2006 09:22:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCHMv-0000PL-Bl
	for mmusic@ietf.org; Thu, 23 Feb 2006 09:22:57 -0500
Received: from 67.254.241.83.in-addr.dgcsystems.net ([83.241.254.67]
	helo=smtp.dgcsystems.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCHMs-0003xq-GK
	for mmusic@ietf.org; Thu, 23 Feb 2006 09:22:57 -0500
Received: from MISAN ([217.13.240.136]) by smtp.dgcsystems.net with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 23 Feb 2006 15:22:52 +0100
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Arnoud van Wijk" <degodefroi@gmail.com>,
	"'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility
	relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Thu, 23 Feb 2006 15:22:51 +0100
Message-ID: <GLEFKJBKNILEBOELNIBIEEHGDGAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <004d01c63877$375949e0$2500a8c0@solstice>
Importance: Normal
X-OriginalArrivalTime: 23 Feb 2006 14:22:52.0731 (UTC)
	FILETIME=[A1C1D0B0:01C63884]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Arnoud,
What I try to tell is that it may be totally wrong to shift the user
interface to
a single window for PSTN textphone communication.

1. If you have a V.18 to V.18 communication, it is full duplex and the
standards require the display to be split in some way between sent and
received text.
It looks as on IP and no strict turn taking etiquette is needed.

2. If you have a V.21 communication it is usually one screen, but fully
possible to interrupt the  other part by just sending text whenever you
want. Turn-taking etiquette is needed.

3. If you have an EDT or DTMF or Baudot-TTY, it is strictly half duplex with
no chance to transmit while you are receiving. Turn-taking etiquette is
needed.

4. If the system happens to support the proprietary US textphones,
communication is in principle half duplex, but there is a specific interrupt
function that causes some action at the other end.


So, we cannot force any strict user interface action from the client who
receives the txp indicator. I do not want to cause more work by requiring
subparameters, so let us go with txp and this description in section 5:

> 	Typical use case
>     for this is e.g., a connection where one endpoint is an analog
>     textphone, and the other one is a native IP based text telephone.
> 	The user should be made aware that presentation and communication
> 	limitations exist.

In a specific implementation no one can prevent you from taking a shortcut
and implement swap to single screen display for all txp indications, knowing
that most calls will be with textphones that matches that behaviour.




Gunnar


----------------------------------------------------------------------------
-
Gunnar Hellstrom, Omnitor
gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
Mob: +46 708 204 288
Phone: +46 8 556 002 03
www.omnitor.se <http://www.omnitor.se>


-----Original Message-----
From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
Sent: Thursday, February 23, 2006 1:47 PM
To: 'Gunnar Hellstrom'; 'Jani Hautakorpi (JO/LMF)'
Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
Subject: RE: [MMUSIC] Accessibility
relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt


Gunnar, that is exactly what Jani and I mean here.

It has nothing to do with call mechanism/buffering etc. (RFC4103 already
offers changes in character transmission speed).
It is to alert the user that the media stream is originating from a PSTN
texttelephone.

You have to see it as a person who is used to bi-directional ToIP on a split
screen. Both users send and receive text simultaneously.
Then next call originates from a PSTN texttelephone and the user needs to be
aware that they have to wait until the other has finished typing and
indicates that it is the users turn now to type.

The txp label will also allow, depending on the user interface, to go from
split screen to a single screen, more or less behave like a PSTN
texttelephone. (and disallow cut and paste of more then 50 characters to
avoid flooding the PSTN textphone).
But it can just as well be a pop up window alerting the user that he or she
is connected to a PSTN texttelephone.

I am asuming that the callee knows the PSTN texttelephony etiquette.
(wait for turns, indicate GA or * or x when finished typing etc etc).

Greetz

Arnoud van Wijk

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> Sent: donderdag 23 februari 2006 0:24
> To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility related parametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
>
> Jani,
> OK, I understand. Your idea was to have the meaning of the values enough
> described in the sdp-media-content specification.
>
> Then we should add a few more words to explain suitable behaviour of a
> client receiving the "txp" indicator.
>
> I assume the most common case would be in connection with the m=text media
> description.
>
> I dislike to drag the variations of PSTN textphones into requirements on
> variations in behaviour of SIP clients. But I cannot figure out how a SIP
> client shall react on reception of the txp indication. The expected
> variation is too wide with:
> -half duplex or full duplex or interruptable half duplex,
> -split window or common window,
> -simultaneous voice and text or alternating voice and text,
> -national character set or further limited or Unicode
> -4 or 6 or 10 or 30 or 120 characters per second.
>
> It is tempting to ask for a subparameter for the type of textphone that is
> commected beyond the gateway.
> One architecturally ugly way to do it would be to ask gateway implementors
> to generate a
> RFC 2833bisdata event in an audio channel giving information on the type
> of
> textphone in contact, and the application would then have knowledge about
> what characteristics to use towards them.
> See section 2.7.1 in:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-06.txt
>
>
>
> We could make it easy for us and just specify : "txp" indicates that the
> other party has a textphone, and that the user should be made aware that
> presentation and communication restrictions may apply.
>
> So, the phrase in section 5 deascribing txp could be extended to end like
> this:
>
> 	Typical use case
>       for this is e.g., a connection where one endpoint is an analog
>       textphone, and the other one is a native IP based text telephone.
> 	The user should be made aware that presentation and communication
> 	limitations exist.
>
>
> ?
>
> Gunnar
>
>
>
> --------------------------------------------------------------------------
> --
> -
> Gunnar Hellstrom, Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> Mob: +46 708 204 288
> Phone: +46 8 556 002 03
> www.omnitor.se <http://www.omnitor.se>
>
>
> -----Original Message-----
> From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> Sent: Wednesday, February 22, 2006 11:53 AM
> To: 'Jani Hautakorpi (JO/LMF)'; 'Gunnar Hellstrom'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility related
> parametersindraft-ietf-mmusic-sdp-media-content-01.txt
>
>
> I think if we say in the ToIP draft that it is advised to use txp label to
> indicate a texttelephone in the call, it should not delay the RFC.
> The only thing is that when the RFC is released, will it be possible to
> swap
> the reference to the media content draft with the media content RFC?
>
> Greetz
>
> Arnoud
>
> > -----Original Message-----
> > From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> > Sent: woensdag 22 februari 2006 7:34
> > To: Gunnar Hellstrom
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-
> mmusic-
> > sdp-media-content-01.txt
> >
> > Gunnar,
> >
> > > Explanation 2
> > > ---------------
> > > There could be another explanation: The table in section 10 could be
> the
> > > initial table, and you regard the meaning of the values enough
> described
> > in
> > > the media-content specification. Then all xxxx would point at the
> > > media-content specification.
> >
> > This is the right explanation. We're planning to register the coming RFC
> > number of this draft in the table. But if you want to specify the usage
> > of "txp" in some other draft, we can make an informational reference
> > from this draft to that one.
> >
> > > What is our intention? It could be suitable with an RFC-editor note
> > about
> > > the meaning of XXXX and how it shall be handled.
> >
> > I'll add a note for RFC-editor.
> >
> > > Yes, I was thinking that if we bring in a reference to "txp" in the
> > > sipping-toip specification, then we need to wait until media-content
> is
> > > published and the table of values registered by IANA until we can
> > proceed to
> > > publication.
> >
> > I guess this isn't a serious problem.
> >
> >
> > --
> > Jani H.
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
>



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 24 07:42:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCcHP-0006R0-D9; Fri, 24 Feb 2006 07:42:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCcHN-0006PV-Ip
	for mmusic@ietf.org; Fri, 24 Feb 2006 07:42:37 -0500
Received: from uproxy.gmail.com ([66.249.92.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCcHK-00014a-UO
	for mmusic@ietf.org; Fri, 24 Feb 2006 07:42:37 -0500
Received: by uproxy.gmail.com with SMTP id j40so124065ugd
	for <mmusic@ietf.org>; Fri, 24 Feb 2006 04:42:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:from:to:cc:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:in-reply-to:thread-index;
	b=gOkBq/agHdwF1b7bNpFazlfmiECZRNhP/0SPVHXa3cwLnXWE6LdRDYGz3kgrJPo50lx7moUlR1YJRXvXXJrlG8FkpwmME6ZMXqvOdpkOcSmDpnfr4be0meVMmtMzAcJCbYaXrws3dlVU0qLyJhP7TJCdbE+BW6xB29bs2bJyY20=
Received: by 10.66.216.13 with SMTP id o13mr4424355ugg;
	Fri, 24 Feb 2006 04:42:33 -0800 (PST)
Received: from solstice ( [82.197.192.189])
	by mx.gmail.com with ESMTP id c1sm844299ugf.2006.02.24.04.42.32;
	Fri, 24 Feb 2006 04:42:32 -0800 (PST)
From: "Arnoud van Wijk" <degodefroi@gmail.com>
To: "'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>,
	"'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility
	relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Fri, 24 Feb 2006 13:42:34 +0100
Message-ID: <002a01c6393f$c9eb4600$2500a8c0@solstice>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
In-reply-to: <GLEFKJBKNILEBOELNIBIEEHGDGAA.gunnar.hellstrom@omnitor.se>
Thread-Index: AcY4hKYW06R31gxfQEyQVRfcdYcvQAAuvwyA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Gunnar,
The ToIP client MAY switch from split screen to a single screen. It does not
have to. In the Dutch mobile text telephone platform, we will make it an
option in the client to go from splitscreen to single screen when
communicating with a PSTN text telephone. It is up to the users to choose
it.

The most important part is that the users know that they may have to use the
turn-taking etiquette in the call. As you wrote below, almost all textphone
calls require turn-taking etiquette.

The chance of connecting to a native V.18 is still very slim. 
Maybe we can say if it is native v1.8, that it will not use txp label. That
is more or less to be determined by trials if that is desirable or not.

But for 99% of all texttelephone calls it will require turn-taking etiquette
anyway.

Cheers

Arnoud

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> Sent: donderdag 23 februari 2006 15:23
> To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility relatedparametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
> 
> Arnoud,
> What I try to tell is that it may be totally wrong to shift the user
> interface to
> a single window for PSTN textphone communication.
> 
> 1. If you have a V.18 to V.18 communication, it is full duplex and the
> standards require the display to be split in some way between sent and
> received text.
> It looks as on IP and no strict turn taking etiquette is needed.
> 
> 2. If you have a V.21 communication it is usually one screen, but fully
> possible to interrupt the  other part by just sending text whenever you
> want. Turn-taking etiquette is needed.
> 
> 3. If you have an EDT or DTMF or Baudot-TTY, it is strictly half duplex
> with
> no chance to transmit while you are receiving. Turn-taking etiquette is
> needed.
> 
> 4. If the system happens to support the proprietary US textphones,
> communication is in principle half duplex, but there is a specific
> interrupt
> function that causes some action at the other end.
> 
> 
> So, we cannot force any strict user interface action from the client who
> receives the txp indicator. I do not want to cause more work by requiring
> subparameters, so let us go with txp and this description in section 5:
> 
> > 	Typical use case
> >     for this is e.g., a connection where one endpoint is an analog
> >     textphone, and the other one is a native IP based text telephone.
> > 	The user should be made aware that presentation and communication
> > 	limitations exist.
> 
> In a specific implementation no one can prevent you from taking a shortcut
> and implement swap to single screen display for all txp indications,
> knowing
> that most calls will be with textphones that matches that behaviour.
> 
> 
> 
> 
> Gunnar
> 
> 
> --------------------------------------------------------------------------
> --
> -
> Gunnar Hellstrom, Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> Mob: +46 708 204 288
> Phone: +46 8 556 002 03
> www.omnitor.se <http://www.omnitor.se>
> 
> 
> -----Original Message-----
> From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> Sent: Thursday, February 23, 2006 1:47 PM
> To: 'Gunnar Hellstrom'; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility
> relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
> 
> 
> Gunnar, that is exactly what Jani and I mean here.
> 
> It has nothing to do with call mechanism/buffering etc. (RFC4103 already
> offers changes in character transmission speed).
> It is to alert the user that the media stream is originating from a PSTN
> texttelephone.
> 
> You have to see it as a person who is used to bi-directional ToIP on a
> split
> screen. Both users send and receive text simultaneously.
> Then next call originates from a PSTN texttelephone and the user needs to
> be
> aware that they have to wait until the other has finished typing and
> indicates that it is the users turn now to type.
> 
> The txp label will also allow, depending on the user interface, to go from
> split screen to a single screen, more or less behave like a PSTN
> texttelephone. (and disallow cut and paste of more then 50 characters to
> avoid flooding the PSTN textphone).
> But it can just as well be a pop up window alerting the user that he or
> she
> is connected to a PSTN texttelephone.
> 
> I am asuming that the callee knows the PSTN texttelephony etiquette.
> (wait for turns, indicate GA or * or x when finished typing etc etc).
> 
> Greetz
> 
> Arnoud van Wijk
> 
> > -----Original Message-----
> > From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> > Sent: donderdag 23 februari 2006 0:24
> > To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: RE: [MMUSIC] Accessibility related parametersindraft-ietf-
> mmusic-
> > sdp-media-content-01.txt
> >
> > Jani,
> > OK, I understand. Your idea was to have the meaning of the values enough
> > described in the sdp-media-content specification.
> >
> > Then we should add a few more words to explain suitable behaviour of a
> > client receiving the "txp" indicator.
> >
> > I assume the most common case would be in connection with the m=text
> media
> > description.
> >
> > I dislike to drag the variations of PSTN textphones into requirements on
> > variations in behaviour of SIP clients. But I cannot figure out how a
> SIP
> > client shall react on reception of the txp indication. The expected
> > variation is too wide with:
> > -half duplex or full duplex or interruptable half duplex,
> > -split window or common window,
> > -simultaneous voice and text or alternating voice and text,
> > -national character set or further limited or Unicode
> > -4 or 6 or 10 or 30 or 120 characters per second.
> >
> > It is tempting to ask for a subparameter for the type of textphone that
> is
> > commected beyond the gateway.
> > One architecturally ugly way to do it would be to ask gateway
> implementors
> > to generate a
> > RFC 2833bisdata event in an audio channel giving information on the type
> > of
> > textphone in contact, and the application would then have knowledge
> about
> > what characteristics to use towards them.
> > See section 2.7.1 in:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-06.txt
> >
> >
> >
> > We could make it easy for us and just specify : "txp" indicates that the
> > other party has a textphone, and that the user should be made aware that
> > presentation and communication restrictions may apply.
> >
> > So, the phrase in section 5 deascribing txp could be extended to end
> like
> > this:
> >
> > 	Typical use case
> >       for this is e.g., a connection where one endpoint is an analog
> >       textphone, and the other one is a native IP based text telephone.
> > 	The user should be made aware that presentation and communication
> > 	limitations exist.
> >
> >
> > ?
> >
> > Gunnar
> >
> >
> >
> > ------------------------------------------------------------------------
> --
> > --
> > -
> > Gunnar Hellstrom, Omnitor
> > gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> > Mob: +46 708 204 288
> > Phone: +46 8 556 002 03
> > www.omnitor.se <http://www.omnitor.se>
> >
> >
> > -----Original Message-----
> > From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> > Sent: Wednesday, February 22, 2006 11:53 AM
> > To: 'Jani Hautakorpi (JO/LMF)'; 'Gunnar Hellstrom'
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: RE: [MMUSIC] Accessibility related
> > parametersindraft-ietf-mmusic-sdp-media-content-01.txt
> >
> >
> > I think if we say in the ToIP draft that it is advised to use txp label
> to
> > indicate a texttelephone in the call, it should not delay the RFC.
> > The only thing is that when the RFC is released, will it be possible to
> > swap
> > the reference to the media content draft with the media content RFC?
> >
> > Greetz
> >
> > Arnoud
> >
> > > -----Original Message-----
> > > From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> > > Sent: woensdag 22 februari 2006 7:34
> > > To: Gunnar Hellstrom
> > > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > > Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-
> > mmusic-
> > > sdp-media-content-01.txt
> > >
> > > Gunnar,
> > >
> > > > Explanation 2
> > > > ---------------
> > > > There could be another explanation: The table in section 10 could be
> > the
> > > > initial table, and you regard the meaning of the values enough
> > described
> > > in
> > > > the media-content specification. Then all xxxx would point at the
> > > > media-content specification.
> > >
> > > This is the right explanation. We're planning to register the coming
> RFC
> > > number of this draft in the table. But if you want to specify the
> usage
> > > of "txp" in some other draft, we can make an informational reference
> > > from this draft to that one.
> > >
> > > > What is our intention? It could be suitable with an RFC-editor note
> > > about
> > > > the meaning of XXXX and how it shall be handled.
> > >
> > > I'll add a note for RFC-editor.
> > >
> > > > Yes, I was thinking that if we bring in a reference to "txp" in the
> > > > sipping-toip specification, then we need to wait until media-content
> > is
> > > > published and the table of values registered by IANA until we can
> > > proceed to
> > > > publication.
> > >
> > > I guess this isn't a serious problem.
> > >
> > >
> > > --
> > > Jani H.
> > >
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 24 10:53:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCfGM-000533-Eb; Fri, 24 Feb 2006 10:53:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCfGK-00050M-D8; Fri, 24 Feb 2006 10:53:44 -0500
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCfGK-0007mF-44; Fri, 24 Feb 2006 10:53:44 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:52493)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1FCfG2-00024W-6t; Fri, 24 Feb 2006 15:53:26 +0000
In-Reply-To: <17374.4868.521418.118273@cnr.cs.columbia.edu>
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
	<tslacdevlba.fsf@cz.mit.edu>
	<17374.4868.521418.118273@cnr.cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DD146132-AB2C-45DA-B735-1010C568B113@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: comedia-tls: proposed change for certificate
	identities
Date: Fri, 24 Feb 2006 15:53:24 +0000
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
	Jon Peterson <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>,
	Jonathan Lennox <lennox@cs.columbia.edu>, tls@ietf.org,
	EKR <ekr@networkresonance.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

On 30 Jan 2006, at 13:22, Jonathan Lennox wrote:
> On Sunday, January 29 2006, "Sam Hartman" wrote:
>>>>>>> "Jonathan" == Jonathan Lennox <lennox@cs.columbia.edu> writes:
>>
>>     Jonathan> * If your SDP was sent over an end-to-end authenticated
>>     Jonathan> and integrity-protected channel, there are no
>>     Jonathan> constraints on what identity you assert in your TLS
>>     Jonathan> certificates; you can use anything you want.  Identity
>>     Jonathan> is handled by the transporting protocol.
>>
>> What about hop-by-hop authenticated with each hop integrity  
>> protected.
>> IMHO in many environments, this presents acceptable man-in-the-middle
>> risk.  I think that it may present significantly easier to deal with
>> usability issues so I think it should at least be allowed if not
>> encouraged.
>
> This will certainly be the most common way of securing SDP, I think  
> -- this
> describes how sips, i.e. sip over hop-by-hop TLS, works.  You're  
> vulnerable
> to a broken or subverted sip proxy server, but otherwise you're safe.
>
> If there's consensus that it's acceptable to allow this mode, I can  
> add
> language allowing it.  However, I think this is a big enough change  
> I'd like
> to hear positive consensus for it; this should get something more  
> than just
> consent-by-silence from the working group.

There was a comment from Hadriel Kaplan supporting this change, but  
this is a big enough issue that I'd like more feedback before we go  
forward. Any comments from other members of the working group (or  
from the security ADs)?

Colin

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 24 11:29:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCfpK-0004HB-RA; Fri, 24 Feb 2006 11:29:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfpK-0004Dj-3l
	for mmusic@ietf.org; Fri, 24 Feb 2006 11:29:54 -0500
Received: from 67.254.241.83.in-addr.dgcsystems.net ([83.241.254.67]
	helo=smtp.dgcsystems.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCfpH-0000Yx-4q
	for mmusic@ietf.org; Fri, 24 Feb 2006 11:29:54 -0500
Received: from MISAN ([217.13.240.136]) by smtp.dgcsystems.net with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 24 Feb 2006 17:29:49 +0100
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Arnoud van Wijk" <degodefroi@gmail.com>,
	"'Jani Hautakorpi \(JO/LMF\)'" <jani.hautakorpi@ericsson.com>
Subject: RE: [MMUSIC] Accessibility
	relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
Date: Fri, 24 Feb 2006 17:29:49 +0100
Message-ID: <GLEFKJBKNILEBOELNIBIIEJEDGAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <002a01c6393f$c9eb4600$2500a8c0@solstice>
Importance: Normal
X-OriginalArrivalTime: 24 Feb 2006 16:29:49.0642 (UTC)
	FILETIME=[8833F2A0:01C6395F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1094b1c84fa6e846d476f39271f5074f
Cc: Gonzalo.Camarillo@ericsson.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Arnoud,
OK, you are right. The txp content indicator is used for indicating
limitations in media handling. The gateway should know, and send the txp
indicator only in calls where there are limitations.
So for a call with a V.18 capable gateway to a V.18 textphone, the indicator
should not be used and the SIP client should use a user interface that
encourages two way simultaneous typing.

I agree, and then want to ask Jani to take in this extended description of
txp in the media-content specification:

Typical use case for this is when there are presentation or communication
limitations in the capability to handle simultaneous communication in both
directions. This can for example be a connection where one endpoint is an
analog textphone of the common types that requires turn-taking control by
the user, and the other one is a native IP based text telephone.
The user should be made aware that such limitations prevail.


Gunnar
----------------------------------------------------------------------------
-
Gunnar Hellstrom, Omnitor
gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
Mob: +46 708 204 288
Phone: +46 8 556 002 03
www.omnitor.se <http://www.omnitor.se>


-----Original Message-----
From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
Sent: Friday, February 24, 2006 1:43 PM
To: 'Gunnar Hellstrom'; 'Jani Hautakorpi (JO/LMF)'
Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
Subject: RE: [MMUSIC] Accessibility
relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt


Hi Gunnar,
The ToIP client MAY switch from split screen to a single screen. It does not
have to. In the Dutch mobile text telephone platform, we will make it an
option in the client to go from splitscreen to single screen when
communicating with a PSTN text telephone. It is up to the users to choose
it.

The most important part is that the users know that they may have to use the
turn-taking etiquette in the call. As you wrote below, almost all textphone
calls require turn-taking etiquette.

The chance of connecting to a native V.18 is still very slim.
Maybe we can say if it is native v1.8, that it will not use txp label. That
is more or less to be determined by trials if that is desirable or not.

But for 99% of all texttelephone calls it will require turn-taking etiquette
anyway.

Cheers

Arnoud

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> Sent: donderdag 23 februari 2006 15:23
> To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility relatedparametersindraft-ietf-mmusic-
> sdp-media-content-01.txt
>
> Arnoud,
> What I try to tell is that it may be totally wrong to shift the user
> interface to
> a single window for PSTN textphone communication.
>
> 1. If you have a V.18 to V.18 communication, it is full duplex and the
> standards require the display to be split in some way between sent and
> received text.
> It looks as on IP and no strict turn taking etiquette is needed.
>
> 2. If you have a V.21 communication it is usually one screen, but fully
> possible to interrupt the  other part by just sending text whenever you
> want. Turn-taking etiquette is needed.
>
> 3. If you have an EDT or DTMF or Baudot-TTY, it is strictly half duplex
> with
> no chance to transmit while you are receiving. Turn-taking etiquette is
> needed.
>
> 4. If the system happens to support the proprietary US textphones,
> communication is in principle half duplex, but there is a specific
> interrupt
> function that causes some action at the other end.
>
>
> So, we cannot force any strict user interface action from the client who
> receives the txp indicator. I do not want to cause more work by requiring
> subparameters, so let us go with txp and this description in section 5:
>
> > 	Typical use case
> >     for this is e.g., a connection where one endpoint is an analog
> >     textphone, and the other one is a native IP based text telephone.
> > 	The user should be made aware that presentation and communication
> > 	limitations exist.
>
> In a specific implementation no one can prevent you from taking a shortcut
> and implement swap to single screen display for all txp indications,
> knowing
> that most calls will be with textphones that matches that behaviour.
>
>
>
>
> Gunnar
>
>
> --------------------------------------------------------------------------
> --
> -
> Gunnar Hellstrom, Omnitor
> gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> Mob: +46 708 204 288
> Phone: +46 8 556 002 03
> www.omnitor.se <http://www.omnitor.se>
>
>
> -----Original Message-----
> From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> Sent: Thursday, February 23, 2006 1:47 PM
> To: 'Gunnar Hellstrom'; 'Jani Hautakorpi (JO/LMF)'
> Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> Subject: RE: [MMUSIC] Accessibility
> relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
>
>
> Gunnar, that is exactly what Jani and I mean here.
>
> It has nothing to do with call mechanism/buffering etc. (RFC4103 already
> offers changes in character transmission speed).
> It is to alert the user that the media stream is originating from a PSTN
> texttelephone.
>
> You have to see it as a person who is used to bi-directional ToIP on a
> split
> screen. Both users send and receive text simultaneously.
> Then next call originates from a PSTN texttelephone and the user needs to
> be
> aware that they have to wait until the other has finished typing and
> indicates that it is the users turn now to type.
>
> The txp label will also allow, depending on the user interface, to go from
> split screen to a single screen, more or less behave like a PSTN
> texttelephone. (and disallow cut and paste of more then 50 characters to
> avoid flooding the PSTN textphone).
> But it can just as well be a pop up window alerting the user that he or
> she
> is connected to a PSTN texttelephone.
>
> I am asuming that the callee knows the PSTN texttelephony etiquette.
> (wait for turns, indicate GA or * or x when finished typing etc etc).
>
> Greetz
>
> Arnoud van Wijk
>
> > -----Original Message-----
> > From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
> > Sent: donderdag 23 februari 2006 0:24
> > To: Arnoud van Wijk; 'Jani Hautakorpi (JO/LMF)'
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: RE: [MMUSIC] Accessibility related parametersindraft-ietf-
> mmusic-
> > sdp-media-content-01.txt
> >
> > Jani,
> > OK, I understand. Your idea was to have the meaning of the values enough
> > described in the sdp-media-content specification.
> >
> > Then we should add a few more words to explain suitable behaviour of a
> > client receiving the "txp" indicator.
> >
> > I assume the most common case would be in connection with the m=text
> media
> > description.
> >
> > I dislike to drag the variations of PSTN textphones into requirements on
> > variations in behaviour of SIP clients. But I cannot figure out how a
> SIP
> > client shall react on reception of the txp indication. The expected
> > variation is too wide with:
> > -half duplex or full duplex or interruptable half duplex,
> > -split window or common window,
> > -simultaneous voice and text or alternating voice and text,
> > -national character set or further limited or Unicode
> > -4 or 6 or 10 or 30 or 120 characters per second.
> >
> > It is tempting to ask for a subparameter for the type of textphone that
> is
> > commected beyond the gateway.
> > One architecturally ugly way to do it would be to ask gateway
> implementors
> > to generate a
> > RFC 2833bisdata event in an audio channel giving information on the type
> > of
> > textphone in contact, and the application would then have knowledge
> about
> > what characteristics to use towards them.
> > See section 2.7.1 in:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2833bisdata-06.txt
> >
> >
> >
> > We could make it easy for us and just specify : "txp" indicates that the
> > other party has a textphone, and that the user should be made aware that
> > presentation and communication restrictions may apply.
> >
> > So, the phrase in section 5 deascribing txp could be extended to end
> like
> > this:
> >
> > 	Typical use case
> >       for this is e.g., a connection where one endpoint is an analog
> >       textphone, and the other one is a native IP based text telephone.
> > 	The user should be made aware that presentation and communication
> > 	limitations exist.
> >
> >
> > ?
> >
> > Gunnar
> >
> >
> >
> > ------------------------------------------------------------------------
> --
> > --
> > -
> > Gunnar Hellstrom, Omnitor
> > gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
> > Mob: +46 708 204 288
> > Phone: +46 8 556 002 03
> > www.omnitor.se <http://www.omnitor.se>
> >
> >
> > -----Original Message-----
> > From: Arnoud van Wijk [mailto:degodefroi@gmail.com]
> > Sent: Wednesday, February 22, 2006 11:53 AM
> > To: 'Jani Hautakorpi (JO/LMF)'; 'Gunnar Hellstrom'
> > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > Subject: RE: [MMUSIC] Accessibility related
> > parametersindraft-ietf-mmusic-sdp-media-content-01.txt
> >
> >
> > I think if we say in the ToIP draft that it is advised to use txp label
> to
> > indicate a texttelephone in the call, it should not delay the RFC.
> > The only thing is that when the RFC is released, will it be possible to
> > swap
> > the reference to the media content draft with the media content RFC?
> >
> > Greetz
> >
> > Arnoud
> >
> > > -----Original Message-----
> > > From: Jani Hautakorpi (JO/LMF) [mailto:jani.hautakorpi@ericsson.com]
> > > Sent: woensdag 22 februari 2006 7:34
> > > To: Gunnar Hellstrom
> > > Cc: Gonzalo.Camarillo@ericsson.com; mmusic@ietf.org
> > > Subject: Re: [MMUSIC] Accessibility related parametersindraft-ietf-
> > mmusic-
> > > sdp-media-content-01.txt
> > >
> > > Gunnar,
> > >
> > > > Explanation 2
> > > > ---------------
> > > > There could be another explanation: The table in section 10 could be
> > the
> > > > initial table, and you regard the meaning of the values enough
> > described
> > > in
> > > > the media-content specification. Then all xxxx would point at the
> > > > media-content specification.
> > >
> > > This is the right explanation. We're planning to register the coming
> RFC
> > > number of this draft in the table. But if you want to specify the
> usage
> > > of "txp" in some other draft, we can make an informational reference
> > > from this draft to that one.
> > >
> > > > What is our intention? It could be suitable with an RFC-editor note
> > > about
> > > > the meaning of XXXX and how it shall be handled.
> > >
> > > I'll add a note for RFC-editor.
> > >
> > > > Yes, I was thinking that if we bring in a reference to "txp" in the
> > > > sipping-toip specification, then we need to wait until media-content
> > is
> > > > published and the table of values registered by IANA until we can
> > > proceed to
> > > > publication.
> > >
> > > I guess this isn't a serious problem.
> > >
> > >
> > > --
> > > Jani H.
> > >
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic





_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Fri Feb 24 11:49:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCg7s-0000U4-Mm; Fri, 24 Feb 2006 11:49:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCg7q-0000Tn-Tp; Fri, 24 Feb 2006 11:49:02 -0500
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]
	helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FCg7p-0000ws-MJ; Fri, 24 Feb 2006 11:49:02 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id BAB83E0077; Fri, 24 Feb 2006 11:48:54 -0500 (EST)
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: comedia-tls: proposed change for certificate
	identities
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
	<tslacdevlba.fsf@cz.mit.edu>
	<17374.4868.521418.118273@cnr.cs.columbia.edu>
	<DD146132-AB2C-45DA-B735-1010C568B113@csperkins.org>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 24 Feb 2006 11:48:54 -0500
In-Reply-To: <DD146132-AB2C-45DA-B735-1010C568B113@csperkins.org> (Colin
	Perkins's message of "Fri, 24 Feb 2006 15:53:24 +0000")
Message-ID: <tslaccg66tl.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
	Jon Peterson <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>,
	Jonathan Lennox <lennox@cs.columbia.edu>, tls@ietf.org,
	EKR <ekr@networkresonance.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

>>>>> "Colin" == Colin Perkins <csp@csperkins.org> writes:

    Colin> There was a comment from Hadriel Kaplan supporting this change, but
    Colin> this is a big enough issue that I'd like more feedback before we go
    Colin> forward. Any comments from other members of the working group (or
    Colin> from the security ADs)?

As the one who proposed it, I supported it.

I'm a bit worried that this may be used to bootstrap lawful intercept
more easily than some other solution.  However I think that concern is
not very realistic because without this feature, I don't think we're
going to see usable media encryption as a reality.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Sat Feb 25 03:32:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCuqk-0005i3-T7; Sat, 25 Feb 2006 03:32:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCnUP-0001K6-DQ
	for mmusic@ietf.org; Fri, 24 Feb 2006 19:40:49 -0500
Received: from mail5.dslextreme.com ([66.51.199.81])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FCnUN-0002ub-V4
	for mmusic@ietf.org; Fri, 24 Feb 2006 19:40:49 -0500
Received: (qmail 372 invoked from network); 25 Feb 2006 00:40:40 -0000
Received: from unknown (HELO server.hyervision.com) (66.159.193.111)
	by mail5.dslextreme.com with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP;
	Fri, 24 Feb 2006 16:40:40 -0800
Received: from elephant (adsl-66-159-193-142.dslextreme.com [66.159.193.142])
	by server.hyervision.com (8.13.4/8.13.4) with ESMTP id
	k1P0eMWf011093; Fri, 24 Feb 2006 16:40:35 -0800 (PST)
Message-Id: <200602250040.k1P0eMWf011093@server.hyervision.com>
From: "Adam Li" <adamli@zchannels.com>
To: "'Colin Perkins'" <csp@csperkins.org>, "'Joerg Ott'" <jo@netlab.hut.fi>
Date: Fri, 24 Feb 2006 16:40:22 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcY5pA9KqD45jRgdT7eaIC3v5PDGDA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-Mailman-Approved-At: Sat, 25 Feb 2006 03:32:21 -0500
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>,
	IETF-MMUSIC <mmusic@ietf.org>
Subject: [MMUSIC] The FEC Grouping Draft
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Dear Chairs,

Could we move forward the FEC grouping draft, and maybe request a WG last
call? The last revision of the FEC grouping draft has been posted for two
and a half months.
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-fec-grouping-02.txt.
Any comments on this?

We are working on finishing up the FEC draft in AVT (avt-fec) which will
depend on this FEC grouping draft (mmusic-fec-grouping) to be operable.
Thank you for your consideration.

Regards,

Adam




_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 27 05:10:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDfL8-0001Xs-Gn; Mon, 27 Feb 2006 05:10:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FD8Hc-0007yD-6i; Sat, 25 Feb 2006 17:53:00 -0500
Received: from laser.networkresonance.com ([198.144.196.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FD8Ha-0007hh-Pe; Sat, 25 Feb 2006 17:53:00 -0500
Received: from networkresonance.com (raman.networkresonance.com
	[198.144.196.3])
	by laser.networkresonance.com (Postfix) with ESMTP id 4D34C222457;
	Sat, 25 Feb 2006 14:22:52 -0800 (PST)
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: comedia-tls: proposed change for certificate
	identities 
In-reply-to: Your message of "Fri, 24 Feb 2006 15:53:24 GMT."
	<DD146132-AB2C-45DA-B735-1010C568B113@csperkins.org> 
X-Mailer: MH-E 7.4.3; nmh 1.0.4; XEmacs 21.4 (patch 18)
Date: Sat, 25 Feb 2006 14:21:28 -0800
From: Eric Rescorla <ekr@networkresonance.com>
Message-Id: <20060225222252.4D34C222457@laser.networkresonance.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
X-Mailman-Approved-At: Mon, 27 Feb 2006 05:10:49 -0500
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
	Jon Peterson <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>,
	Jonathan Lennox <lennox@cs.columbia.edu>, tls@ietf.org,
	Sam Hartman <hartmans-ietf@mit.edu>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Colin Perkins <csp@csperkins.org> wrote:
> On 30 Jan 2006, at 13:22, Jonathan Lennox wrote:
> > On Sunday, January 29 2006, "Sam Hartman" wrote:
> >> What about hop-by-hop authenticated with each hop integrity
> >> protected.
> >> IMHO in many environments, this presents acceptable man-in-the-middle
> >> risk.  I think that it may present significantly easier to deal with
> >> usability issues so I think it should at least be allowed if not
> >> encouraged.
> >
> > This will certainly be the most common way of securing SDP, I think
> > -- this
> > describes how sips, i.e. sip over hop-by-hop TLS, works.  You're
> > vulnerable
> > to a broken or subverted sip proxy server, but otherwise you're safe.
> >
> > If there's consensus that it's acceptable to allow this mode, I can
> > add
> > language allowing it.  However, I think this is a big enough change
> > I'd like
> > to hear positive consensus for it; this should get something more
> > than just
> > consent-by-silence from the working group.
> 
> There was a comment from Hadriel Kaplan supporting this change, but
> this is a big enough issue that I'd like more feedback before we go
> forward. Any comments from other members of the working group (or
> from the security ADs)?

This seems like the right approach to me.

-Ekr

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 27 08:58:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDitD-0005rA-VX; Mon, 27 Feb 2006 08:58:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDitC-0005qt-Ih
	for mmusic@ietf.org; Mon, 27 Feb 2006 08:58:14 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDitC-0002xf-Bl
	for mmusic@ietf.org; Mon, 27 Feb 2006 08:58:14 -0500
Received: from 71-81-78-136.dhcp.stls.mo.charter.com ([71.81.78.136]
	helo=[192.168.30.38])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.51) id 1FDitB-000K14-Vl; Mon, 27 Feb 2006 08:58:14 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 71.81.78.136
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: digitalari
Message-ID: <44030573.7020300@sipstation.com>
Date: Mon, 27 Feb 2006 07:58:11 -0600
From: Alan Johnston <alan@sipstation.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: Philip Zimmermann <prz@mit.edu>
Subject: [MMUSIC] draft-zimmermann-avt-zrtp-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

All,

We have just submitted a new Internet-Draft 
draft-zimmermann-avt-zrtp-00.txt.  Until it becomes available in the 
archives, you can get a copy at:

   http://www.philzimmermann.com/zfone/draft-zimmermann-avt-zrtp-00.txt
   http://www.philzimmermann.com/zfone/draft-zimmermann-avt-zrtp-00.html

We will request a slot in AVT in Dallas to discuss.  Discussion about 
the RTP extensions and mechanism are best held on the AVT list while 
discussions about key management for SRTP are best held on the MMUSIC 
list, with some cross posting as needed.

Thanks,
Alan

- - -

ZRTP: Extensions to RTP for Diffie-Hellman Key Agreement for SRTP
                   draft-zimmermann-avt-zrtp-00

Abstract

This document defines ZRTP, RTP (Real-time Transport Protocol) header
extensions for a Diffie-Hellman exchange to agree on a session key
and parameters for establishing Secure RTP (SRTP) sessions.  The ZRTP
protocol is completely self-contained in RTP and does not require
support in the signaling protocol or assume a Public Key
Infrastructure (PKI) infrastructure.  For the media session, ZRTP
provides confidentiality and, in cases where a secret is available
from the signaling protocol, authentication.

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Mon Feb 27 13:34:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDnCd-0003fU-OD; Mon, 27 Feb 2006 13:34:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDnCc-0003ei-01
	for mmusic@ietf.org; Mon, 27 Feb 2006 13:34:34 -0500
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDnCY-0005RA-AO
	for mmusic@ietf.org; Mon, 27 Feb 2006 13:34:33 -0500
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id k1RIYObT012915
	for <mmusic@ietf.org>; Mon, 27 Feb 2006 11:34:29 -0700 (MST)
Received: from de01exm61.ds.mot.com (de01exm61.am.mot.com [10.176.8.106])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k1RImkR4002290
	for <mmusic@ietf.org>; Mon, 27 Feb 2006 12:48:46 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C63BCC.6DC5EE71"
Date: Mon, 27 Feb 2006 13:34:15 -0500
Message-ID: <768EE6AB7D56D54BB5000EC2DD113E715EBC1D@de01exm61.ds.mot.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: SIP-RSTP Draft
Thread-Index: AcY7y7HzN6ZTuullTSqIVrTcpZQAjQAAE21g
From: "Montpetit Marie-Jose-MGIF0300" <mmontpetit@motorola.com>
To: <mmusic@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d11a451997816a91a305dcb5ab1b85dd
Cc: steven.d.whitehead@verizon.com
Subject: [MMUSIC] SIP-RSTP Draft
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C63BCC.6DC5EE71
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C63BCC.6DC5EE71"


------_=_NextPart_002_01C63BCC.6DC5EE71
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Attached. We missed the deadline :-( With the Winter Break here I guess
it was unavoidable.=20
=20
I guess we can start a discussion? Xavier Marjou and I will be at the
meeting.
=20
Marie-Jose
=20
Marie-Jose Montpetit, Eng. Ph.D.
Motorola Connected Home Solutions
NEW PHONE: +1-781-372-8115
mmontpetit@motorola.com
=20
=20

------_=_NextPart_002_01C63BCC.6DC5EE71
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D359422618-27022006>Attached. We missed the deadline :-( With the =
Winter=20
Break here I guess it was unavoidable. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D359422618-27022006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D359422618-27022006>I =
guess we can start=20
a discussion? Xavier Marjou and I will be at the =
meeting.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D359422618-27022006></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D359422618-27022006>Marie-Jose</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DVerdana color=3D#0000ff =
size=3D2>Marie-Jose Montpetit,=20
Eng. Ph.D.</FONT></DIV>
<DIV align=3Dleft><FONT face=3DVerdana color=3D#0000ff size=3D2>Motorola =
Connected Home=20
Solutions</FONT></DIV>
<DIV align=3Dleft><FONT color=3D#0000ff><FONT size=3D2><FONT =
face=3DVerdana><FONT=20
color=3D#ff00ff>NEW PHONE:</FONT> +1-781-372-<FONT=20
color=3D#ff00ff>8115</FONT></FONT></FONT></FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2><A=20
href=3D"mailto:mmontpetit@motorola.com">mmontpetit@motorola.com</A></FONT=
></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_002_01C63BCC.6DC5EE71--

------_=_NextPart_001_01C63BCC.6DC5EE71
Content-Type: application/x-zip-compressed;
	name="SIP-for-streaming-media-sw-00.zip"
Content-Transfer-Encoding: base64
Content-Description: SIP-for-streaming-media-sw-00.zip
Content-Disposition: attachment; filename="SIP-for-streaming-media-sw-00.zip"

UEsDBBQAAAAIADxkWzTGtUYeizQAAGqdAAAhAAAAU0lQLWZvci1zdHJlYW1pbmctbWVkaWEtc3ct
MDAudHh0tX3rc9tGsu931dX/MOUPx1IVSVnyI7HWyS6tR8ys9Tii7GTvVu4pkByKWIMAFwBFK7V/
/O1fd88DICXbiQ6160gE0NPT3dPvGQzySXqbTpZJZr7lM6ztrc3NL7O0tjObTLa3Bnlty9zW3eMy
mdZfhtD+fLRl+nuRb299+da1z1lSprb7c1FZc1bk9cLWaf21gM6KuiiLLDFHRZ7bcW0n5l0xt2ZY
ZMs6LfLqD2Gkn1+T29SWwO9fxfJPADotk3xszbXN7LiYb29tb518XqSlrQ5Nf1GmmXn+rGMOnj17
9WVQ5tSOymVS3vH9ANW83M/NyW2SLRNM3hRTM7RVhV8HeVqn8u1lSUQbF5nZGQ4ud83miU2L0iyJ
I2lO0lLaZJ7mN+bMTtKEcF5k6TjZSN4JxKc7ny+rdNxdOfnqVumiSxC7lQPVnQNU99mzXv25xjSG
dVIvK2Bcz9KKRpoXOru3d6ZajuZpXQMFvtqU1o6xyXhmkmU9I6RLuyDK2ryu6N6kNkl+x2ASwXqU
WbNIarpu6OainhGDB5dXZpwl6ZzHJ6wJ2sziekX/ofGSVVJahjJLbq0ZWVo8dHWVZhn9YSZpNc5I
fCcdGm2CETfBGYH5VijGADc9T+ROxuOinLDErNJ6RhwcM9teAejbo0vz3euekqZJB8ITQIvyEwg1
KcbLOZOBaWr9zeYkv0lzSws2v2Eo10n1yZwWJQ24Mzi5Pt0lNARYUsmM8KeDe1MWy0XVM+a8qC2T
mIEIJeWimSd3JsmqAjOry3S0rDfhlUSMZBgyCze5a3Da3Q0ukBT8i2hh6oLnU6Y3s5oQJK7avLIV
Y0qspwHHQTbHpFESmu4EpGXqfS9zsp/HdlEDiYpoQsJJpMYcbJp3GL7Ik0ApLYDQnDJcSksd/CE+
8EqIZkurMp3wskqIPp/T+XIOzlTpZwYxJzxnMgdQj6RiuZiQnJJMkERnyRi/QWJHVZFZ6LnRnRLd
jyGixSJv6nRuiUkDplyak/SXBemaBDwreGWvIe2mOiUiQPrmdDM9kWFYemacMr/tXIcl1ucg3xNw
FtSlEW6I/tWTnvEstMSeqsZEx8uyBCPbw44JCs2WpJ4epWmpPM3qenG4t7darXqprae9orzZwy97
++mkm4yIy8mYGEDao7dhsJY5G86SSbEyx6Rzx2QvUvtNw1b8dG9Wz7OGbLYG4dVsWbEbWq5Nzc4P
HhWLOxYcrB2SWgUWvt452uVp+KU6LMaExp3ZAYxdBrLpxxty0/qonfmCmfnnZXJjzf5v21v/535P
gGwFS2/bGvBnzSrhp69caqxnBlpaMqyriv777yXhp+oAi1JsF2FcOQMO0UvnJFu3ooGxNFPC8ab0
Ng5ffdHO8cP/vDo9en7wav83p0SuLMn3dQqPwc8rPHd1PbxkvPiX24MAxBwQGL40OMbF34ytFnZM
qyW7w1oAbKge+1mEv8hvbXlDcsZ2j8FUtrwlISBVCpZ7RTch1ywrSIkmRmaYkMXCQI4iplqQNmBe
MBwytYQ02MPmwptYGcrZPaZlT5jAejW30CDTtKQV4zRllU7YLLB+GCdQqmJDSaSXWCVEtYmdkjo1
NzanW8cNFgp/CrJ52YLAzRd4jimhax/TWBQwvkKo3K4Co5kOooKSnOQRytELAdT/J1uPZ4REsaSV
QljNaM10M5BrV+zu5DYhZX8jpoAhkf2JvoWdXWK1C8kDdCd2gDGBCqNbp6wGRSvwIGxIY8mblsUc
dO8WOc2FNSz5IZYlFi55d6GCJOz283TrgX0RgnkEOWHy8ff7pLahAcpishTL3/umH2PEohzg12tb
kiwUWXFz921QApzn+PUDCcQRCYQZkrElf72ovhnOC/x6Fa/4r4XQhPOS4filgXUQiy4x5OvgvMKv
Lk4wFwsRha/DJYYDSPvGBElQUH8EzgH9e4xozuugr8fLwfkOv/aJNndV+q00juF8L/yidUzcmiTf
NKcYzmuW5/55H4LObBJY5mvhfBY4+8/od3KGl2VKFrEF62sAOThYYP3xp7xYZXZy8xWyeA8cLLCj
Geuqd+R3FGT+HgTT/nFwsMCunNf17RxzcBgSBPG8KMl1S2/tt0FtwIEgDvLpH4Hk4PTZf35Kzofq
1C+jwD9tOHBIMoqca10XC1sS/6Hwg+OE6PFeRgLOl34exYM6+BMeFH/W3CgS1dgSEOzL7iiBJSb4
8Lsl1oCnkeZLcT7YVwJ0uCGk/tlujYheq3RSz7a3xgn5D6mSkBy0vFpQ8GP+TY/jW5hd8Ux6pl+z
+a4S8o8QUHTMiGzcZMTm1fkvaxiQD0w3cKyYFSP+qts1I4oaGiiVHLVvbwEN2F/bJeNLM2v4RWRx
1CFSJ5HGyohNnAooaAoEcoxA1RIk9bvy5XxE8YnALdl/puEmFEUVd+xiVd6GgR1th4kwarhMZxrP
14xNeJYIjZTVeEYztAipb9if2d5qeLWF4FSlN6SRcY9zCirxqMgHexiBBs2mmf2cjlIwqkOoJFki
f/BkVSSYEDRbUtpYsOxuiH4ikMSMjniz8GLhxP5mZhTEcUpjM6Lsv84KYglB3kSwJrn65JKPbtNi
WXmXCIBzuHDEMXKICTGCJL51RVjbidCBeQePMBIA+H0ko+R0sYdlk5LAwm8iUEQn1SzzwCKG0ORA
7H57oV0h1CcQ82VWpwsCOKOgmgJYcmuBusxR5G3Oj/bMBcJe+Yqg3bGPmI7peUVmPEtJVNUfdy6v
kAjLo0REQeJUlJZimbKjpMDNTAsCMrcWzniFDKaXuMZkVsUyQyrjtshuOQ5i3dBg19ySSOZpRdgT
UhnNY4I1SRKA28iPtTz3jslpWUu0As3k8jxJVVHQyc4wI1gJWzmgQwYEuk1sgmevcNY5YcwFWhqV
CipmIjTheW1vYbQQiE1tUi+hYQmPhyWLdHSG52eRMDPqXoB5RYlDOJ8vc33UM13yOp5QtE7qymZT
4C8Li8DbvFjezMwOyePEYjHsYm6yKigkIx1qY62i4ZyKS8zdSZkix06zyhKSH0PBUO2kvBn3BoJv
b3EI55X8fdNoTFrECHHRrRJ/e+uOFwoU5IYVwuq8gYIKK5FzmoxFkX1GTo6DPBlcGBIY1GQNueM+
JYQM2q3mV7e3Jku5z24UUKKOyD5HmbGsqlh2TMIaNanI2wd/vDbQLBnNkeLRCVhDX2hqC/RJ86om
cKz+mqlEsk9ZUXJse4+g8npABB604faWx/+LOlBWC0LMEMFLPt0BBzpi1kT1SRgehzGJl7LtLZjk
1nguQA/2yJnLYKCiqJ34YCGP5utsU8/8xMK7roA621v1N8yrFZg9hfIWWjf09/o4PJu8E8X4yqkg
AsjiSRIkGv9hHSKJWU5gOMGIMi9spRzGVRiPBIslVRL6GGbMWnik5KVLTgPcm3ZZFeI6oc5QIa8S
ZTfiCRFNCEVCgNypaWonh6YfAkt+tpkXYVU+unPE9wpwe4v9rUqzYrm9KVxajFPM0Wr2xolzKM3M
BcH5hkHvGw0+nuSMPdwd27vpiSey24CxCTNyKkQQtrdEFEgzj8uUI2NgJuWfyBqxBzzhekxWEEtY
qyZgExO/YnYjmwP128gaNTNGjYTro4QIzx89RGiIMBFsnC2JPOxXLudz0gS/s6+MgkZzpqQTGtmx
NULiJjVYKpB3HpTes2OrXWgE0t7zgjTYKikpoKh3ql0zXZbM8th9Z3qibnTICbjFsmQXutCiX1zs
IYGBjkDVopAy5AQ1GPJGcxg4TraS9xX5mEWkhxoqurtpRYrF6kC7LktO68m4MPYU6iwzmCxNGELM
IEIaX6BG5kyzut6Iquoku/udFOIS7oxxRRGeGEpppAQK+YusdcdgVG/LvC0nWpLN3nVEMw/p2tGu
z1t2uOoTKUtS00nspgy9SxHSlFIGG+965nZMOjVRoYjdJXL5ZUJrfGznF8mxszZy7AA9BBnAvY6S
kYAwyOGfpLyMMdNpkWXFimWMA55IWx+SoJPL98lcZsndIf9LAVBdLDrkWJHyQJVsxX4A/X+aVFzR
I2mcmIbxJH8fskCjv3kjZSzmOApBHHuuYAJyi5oQrbEffwSWz3ucoSU9lNEdwwfNCyJqrg+Sh4PS
B1k+kqYxp3b7VXDsfBhtJiQ3ISrh8rLG0i7dLpIgUiahNUnPAjE75M9ZwQfNHoPlgiy7MVk6hVtn
J1oIBUwgZe8KmQDSAsIXcnqnJfmLEGeNxxD5S15a1PAI1RrCsqR7H8AiuCwE4H6nJc2ypawLRiSS
YSKL4OTUl81v07LIxZfx9vlBQiDYBFWRRKIhesLffTMc0zdOm1b4AyM2HmUBbmopp2sb97GtES8p
yHNLHA6lNpTXZNe7EztnnrYQh2pi37+qu7FR5Ir3LXcVlBadAhwnMLSOWY5S8qFqDr65sklAdsj1
p0EgYFjyd125siteKhkvwj2FV0yz4WDPTYx0cB46NpzJnhSrPCPpdbWs3b9gshw0aX0ENXghFf0P
xRosQaap0BChAHdoeFJ6PhytL5tT94wYi2rNWkhUB41hno7DQn0wq/K02SZig2u1zssmJ0nTt3kJ
LLvGJxKwmFmvwCq6MjN5T0s0WIgcs7EZEWWqmUBdLhBvQGlDvYuPCwcoqRW71KIU9eYNLBQm7/sc
bu1foaa6bBfhPxWlu19RICmxEBgGJGM/ulvz4tHdmi7jGws+nAqsX6exJxbroIQDTgH0jDQBiT3S
WzvsisBAFzlb5or8jUBGMfYOzE2KiDXXGCWMObLTovSDIAojqqOmieYL0zUZFpeOAU7af0vyk9s8
RCRFEEhOrbgzrIURzIosCAJL1Bm9TCxJ82cNXMFqBMV0r2NkWkM3yGpMRBlMiS7o5OpC0tQL5zAa
fkW94jQBnCSFyuVkxq5nHKndY3BQqppi7bSawYMm5UQc1tYmseBsOmqiOBY9nl2yVsfq2RBMdoJu
dpHGHPb1RlPHpHi4iAKVvmNTcRq5U4PIWcA3c3/t+slEFFKbG82HO1hKUfS0qp66mXnUnro5x+ap
WrJNre6JQK7DiDscXyWY4Oc7YzOOWEnfcn4N4mBnSTZ12RZ5iIR3l908HjaOgYm+6ULczbbE80gS
OCVweGsHM8J719zCyMGouumpnW6RIXqmG5i040Mux5sI0K6o5QNSBQkEnxXkRl9IlnM/1p0+7+K8
BQ3KKkkD2gjkV6vt6qkwwj8M+aEQJUfqNEEh//OMvEFoxQ6vyqSUugDbs4nhnC/6Se51MtbcOd+L
EHktolen6AaLwgLvNrgUAkPpiTLTGj/E45jtvTmBrkRXGUtPTDqPsPlIYApGo7+cpIVhn2vO1RcA
ZXWbsBHg5tLblOW8CQs3Xtk5mvXOCnIYC1Z06/cck7bgpsP3Ninzzfdckl1jn9BNZ0i2cPOtDVmQ
fDVuPPKZ+KHzeXdueZZENdd4pr05cDRrdvFXdhR8ZL0q14ytxz2V0+emz6vkG8X06H7hW8sdBdv/
Oye4DmGTTzhYlgUqBiqJMxRinsnb6Hp/Df4BuWisur1J7rIaJdRdHYeW5sIRfJLepBRgGqGVAiIn
Y+f44xVCcNJndwtZTYL6TgKJ2eP7pT2GSFtwtWFHikWacOEKoFxhOFmhChGSrH7Ef3mnxpXYBEXc
T9oOcdd5/3rv9BdGxJcUxcsuympPS3IEEkoTMQvdBYAcdohOd4NJRVAHBMASpisJOVp3I24bhttA
K5JhiGXjCejHGTyCSTFHEyfKHh32bUuy/lXNLsT2Fm7BpT2+FAHTJOUje0wv/xc8JmLdMhIB1ars
FdTeh+yS05lgyskcqTFHzJ2/7rob6W+K5VjCCQMnjfQt2yyoPmZO1XA5kShkSMKxTBbNLF0E/qrO
UDtQturP7usdEecRggg7RV+uWy42n0FBTTaUqgMcUQUvfMMS4fPBN7P5jLh37KMUFIUAZZTievqF
AIKxL1wxQVQSN+a1rIhYrIJbl9l7qzjJIxzTMSXGQJxt9tSO4JuQfsK9kdFyBcIlvKgQPPNdmswx
URHRfLJ3xFntxHaRSaTKcFNlRbpdg5fZN90N6np7qw8SlvATV0k9noFArMiuPyJP+7FAfhymMeVA
spBqkTppfAH2TTtLOFkcufRptciSOwie6BnA/CVFeFnzkmBrzSrQZdzFl/X+jH7p4vwR9CupSvVZ
NZxCAXpRUBgAb/EX7rFX2PPlZ3bihGwk+JjFDYGEL1ql5HRwVr6HdnnnhcAZl6yOJDmQ5fY91JGy
5FgwraolwsHL/ofhiRtHkRbFNzw5Pw60iimlho9o0uDTc+MNvJBm7s087hvIGIzYKuGosBDOueDB
LUzOKPx7iYUngLy7gSkySo16JEjDBUJu+ggxAzwyJPY7nu3OxRc/SpYTkv552hXfPoWRQ7u6FO1w
n0Dgagv6zJG8GoUuVPYNlpIgbWDV0VDjJr3VCp9PcbtMn7YPVKQEuAGF+zgTaLMuaoiBfK35wo82
ozTCGFovvoUWQKa5EK5dvru+vgRZT683zCINc5VuCG3MQJQgjmobeecW1pwJxUphDBMNZhH5QAy4
pi+eoS/xsYRpYECjdzkRN87I1YNgz4qVagXEI5+cCtSuj6ioSnNhHNGCI7lyaJkvFBZgxyT6ZHg9
8y5hX5AtFKsXrJQ4tDsI1VbX8sA9xczA3E7TWppvGxTyG10OQo9Nc6W87JozZGmQU9PVIT0F8+hb
g3aimqfis1msWdTSFAjY8YWU2VRlibTIOqpQPiBf2nI+gleR6yZm1SO5ODQLxMNCoivJv2nSyKVX
yXWTqFjXFbjA4oUIhy7ckWfDCYYESSrp0UnMdInNKkFSXPmuZ968kVKK07quWmYk3938eRRn59Wj
OzuBp6T9PjptJaHVIfv00ouStC+aHTSPwAcXz9ix1RMBNUvGyGl1Vd9ixz9eHPtHokKjdAtoutan
UupCio5gOutf4bxRheMyFtdOPUOAsKsFTzVSE5JI2t7a6Q93JRMkajqJ8RFA/SEKZZymUf0nupxX
N4+yvdU0A15N5wEBXljRliHvBGqyY+f8ZFftleJCxr4W1BhbE7JcLunLg+MJRHppOTejhGST9VbN
iMsEaFBS0HNQV7VgEvJiIDkMtyTYzk94qUD0Ie13RGnU7oCwhDhSho4TKwEt7Ttz2K1mBTcXTZbN
fSVEYO5pU2MvXo3UMegORD00F7uipVd1pHwk04lwQ6cxwxpcdjWY2JP4yOXFcPGKbIQ6AqSPSeWR
/DnFTXh2/U1tKLzviPsDWGeMU1/IqlG+Y43hJPITqQPoyWnPqF9Q3eWcO01/99N23WD8JBd8tLVt
EuwxaRzdDOdhi0GOav8UVMjWNbUnisvw5PrDJbGDDOVktyej8Byc01Ynn3gHlVfxl+/7/6AvUM6r
pHTX1zR4ymvliQs0n8Q9JH/hFiEwYGSNTwFpAOvKmj/+yJ44gUTnlq9RaWbJAvPQ0CLCWxLpF4V4
/wKq3W6Ib9FB5VNfoljjDRAEKFlIhJraai1XlnHqFm57A7Y08Uwi49eqr0m2u4pMh853gS1X3Ngo
I8haa/ahlbHJkW5a13cKEDHCQfGRTeJMKKc/4E16OyP24wVX13yjKpoIgy0iw1vVsU+Gva/zeYGN
j4eIZs5ILliSWmG/S0cI49k8N4wuZ6ByTh3r9njVoSwSKmea8TXw2Cp2oiTNF0HShnhjnJRD/tqg
NS28CXRC3lw+IeUkoIcR6BgiyHRghj6KeU/zz8fILr21Y5S3nQJV4eT4AuM0/Hfck8mT5BpMbmwt
qxeNyiWNWjdVMUWuJE7cImze+WDFAUCBLRUWpznzwu2wW0fT1D7f7NNzDo4KD8QJG/Oylrogu7my
tPbpv5Lodpc5hQDX51aTQo2U4p5oc03dPYiIzTVgsGyssHSrUIlsZEpoyktfBnKICHeeI6FQ+sYs
F2tgjzC+0SUI0ZRtw6pOoVnIcPoAl7sMnDZ4Yfok7jBt+U2H4/Eb/k0EvK4zt6vuXhiP6KJ99+gu
2oveS03Pmfcup3icVmO0qd49SJhXsKtMhlO1reZa0oVJpiX6hgJRZRR6QF1yEXCqBiCstkbszoZS
QkF26sU1k0DqC6Eggr+csdJosBWIshsABEYpt3lXatidTYLhgLmU5l9VA9+5daadIlGCrCDpvwtZ
vQcI+D2xnlu3uX0RCY7SSn4aiEc2wxV9fAKFfMyh6i5uGQ6RS/wY55p3H0ThtfFwWFAiv+CrWBic
N7Bfq2IuQNqxN4fr5Od14+RzV1xydus6+H3NJEqj0gvtucY3HNrtEb1XUETqM3MfJZq33a5x72N6
/RHXdLU134+iOCt395+ZPoI0lwY/1K/376fWIRYlnBdIIWns7pSeV/3338XwQSbsH3i4mzJ5Dz35
3D+ZYYfVyvI+q5Cjf+jZF/5ZUoZFl/39G/Wr95D2IJZ+ST1u2OXpW99wvY9CbY7LgdZuO4QsP2Zc
w5eFhxPUuhogCUh4FYScg0ZEstpQNJD+eaJgRutAwvWGPzSyFdc2/yUOjXokaZagfg0nu04+M1T1
WESHEBSkiPb2e/udeAN53EzLaLrNDzwN8uUmnKFwk5tx7wg3EFZLbu7hcEi3POmxIpyp8bvGsvST
CLA/amB7i9MRIljD5ai6q2oKw3YGZxRzptqTuQIhJlL/D1mhGF2lqyReWv3BrsyryZJ7VWelxVtk
yyTLcsm9OmOJ65AkJG+me8ZdBCkK3sY3n0/dWR/NRkRCy9X3Xa9avLtlqBsqQJHQ67OQzYayTrtG
QvOKzUM+sb/fwosLHc2sRlhOYsngYsY4KfnQidiviHuYHRCuzjg8SZOktRcVl1tAvcWljbxCfDQv
4PtH9wI06LtPDEKRpSkBEGQUVdV59G045E6u7GhMQXLDNmv7G26Ob5Xcz4XL/XQkZRGWA3vT648N
LlF38PFvS6gOXh08/02TH1+UmUhoYj26QYD4bs/8kLgTZdTs0djhntc9aXnd007XvV6vx9L2TeL2
h+XtJQV2v8x4E8BfWSGjnFhJFNLMyTa2h0hsgA1R2CVU1ZxOoiCStTXvXESR6y7SleypJ9oKNc3k
kC/V+LqGb62JtndKqIUOafagfOPA1M1FiNnStytaJNzU5e8XvfGRc+C8t4pA7qC+tYuMkPbl+Px8
Y26h3o06FVRmOXEZFilqQsLLkrx/tutp7Y7mcD2lrJvRaC47HtAa1bvpHWKNLVD+d72wnabXAhmI
tCeRSfBcR2NUTCAjDNaY5z9dXnbM9WB42T/vmMH1h465TMafbH2E0JwmTPGPmD0Qlp3mFC7iJwuC
IaKSBhzmFHDndKHb0cWnjUwlbS25nu0tOMFRma60C8t2RVuwVxEfymDa1U8+FTVy29rU6ZKcIk0l
znYBtyMtI2tJ7UbLiOPYK602SPY9LV1egpSD9L3x3Mj+Et+SfCw7drSR1PrdEqgbBl8ikjOCBEHC
OWBO6bgFzpuhLG/5W2AvInsVKHATtyqpSrskbHNDKMjF05VeJ/E91rbkBKN8krsKhPasVCIqjZKp
ZM9R6BzUYXeCtjvyfifoSNy+WFYz53xRIJ/exB08Lk3DTpa4jj09kkr0ellkvkgdSiOMRmbz0Njn
tuzmbvIT5xHV0pKeRLt/Khf5aKFFIiBZmHMK7Mq7jjm6/MBYLYoVdoGkkr4RqcSuwnIZcgS+BczB
C9slXYZQ/Cx1VnTDhMebvmRWgOuZvUnGdx6SKDYt60miXvuasIHrM4pEsu64JKEhYYic+Jg1hBOO
EXHRH8o0Ygln25vtO5KvEAAgtDrt/HzqG3LaWzU4CczG7YS3ZFaNjpF+v8+zld6aMuRFxnJAI2tA
VyuGCHNqydkguolPZSMUfB+S0rFx38JK/ov/GwWv8Kjv+3kUB+n1oztIL3sHbEchec6WyolQ7d1Z
bEFFVpj8wdyQLmfHRSSo0bUmxjcuxy+DU+V39GgXRqpbPisvi77ry1U8IAWaIeNILPYlBCGXP6yW
TsDVbIvorXWCFe1dqAQ0qWeH6jHkT+tGKQrkfQJf7Qkr+C4reJ/AW+Zsw2WCXswh4hVaAsRDS4tS
22+5nKHPuhlgFxUt0JvS8oSjIxdAB2GCGqOKseZ8YI4IqqG8nYGDtzLlfoQ8tAGJVeNoUetzyPPM
U9/tk6OUlqXckVnkzS4st+dHKmqt1suNxxrhwps3plFj0NC2CoWccOQauLZC9U1P3gy2jbMu0klU
lNVfQJLE7XmDrKTCzjt/uOU0zaTFLrnBaCwFzZKJBPynSBFYs28a+zKah571zFtSC59MX1sW3CEL
wdnD4QluFhD3Ed//1t8ptYAaujA6eMyPzbaE1NZyjAlxWRfZ/JlqSPHFUIvgdha+6M82C+d/wd6g
yWsRkXTBGxkhfyRJdcaNc8RjB+imYENSrNj55o46l0niNUbPkpWG33mnoBqGAHIkijzU85zT7dIf
UYMBWz7OuLm1HLWkP2Ff4YnaXnEfom3xaD7WfoR2V0jscIxd47zvHY9Vl7IRSTxRmqhfhgtvwwW2
3YC+h39uDxrfn10dXTa/GF41v3h7Kne0P//ztZ8ND/9nHdw9n/98xdN+qQ65ezC+8/HH/vJ89bPp
aQGx+Wt/+b7nPm7+2l9uPbeOUfP+9etNABvQbHy16fo9EPrrXzX+eBu+2gShT2oQ4th8yP/Bp70N
WSFtgLBOhSaEDdfXGPAlkdnwRPdHnEI4OD+92PyEXvenDK0f1/3HBj3oGQRaMDdHF+fXVxfv167j
wLWclPDgePOYIatn2p8/QBoa83mPjGjy7yWikk8234T3c04gds9Oft0EY/2J/2lL89r1+1aR+ziD
1Wupjz/r5epJsM8e3csd6E5453zAuLgjRCPLCacoHByAJjUN+HHE4rB1wCK+h6Msh6f4CNBH8DDO
umEPDaqNEN5vf2DDJcm8OJ0dmlvaRYLpMtfuT3bEsAzWglCOx2P7uZ7CQyeTLWkoNPdgi8IQ51Ze
66lUXdcD6HeV8iEk8L+5FUfMdsqZRb2zQoQ+Iod+5TZV+31EhwwRORXOc5Nw8NYRe+PFlm1l+wZy
7QbnHwfXJ3sfLo/71ye7MRSXPsLfv569lxBE/WNWHLrHr/GQNP1INd+Fk41MPCD4o6riYVDwGx5f
hi72XQnqzBc/b96s1ZYevF+X1sFhkDf5JwgdCSOJ4wcJiNyEnTQ2+xvAWQiCEDLqkq6k/ZUPCHaJ
BicbaJF2GyQ9vNSfCeNccTSId1M9zFYHCHvSCcrVyX9/GFydHCtHxa3HHhfxrZ9wkrnLSeYngQmG
FMkn7jiWhmAUr8eJ3zcQHgpRV5Q0c3tyfYuSdsfwpgeJ8xZdbcZRse+CfLIb/ayo/CZHENblScpl
Ho63+nAsa5Qb5Bu5BCHF9tbnOcWFvB/KZ/72Wp0eHhqGEfeWxTZSRttbfl4u6yS6QXprm+s5tNdK
XorA7uEATRMfDeR1CKDkeUGqRDeP5uhNGfNOhRvuaouP4UA6V9p62ynNUBHg2D4UDXZdSksTWnKs
GW9V0I4ipfIovXFpyBWfuIRhXLNj0thM6Lo5pKmoVec+vj475c7Tccj4oJEafxR+16qP4oOoq1i4
Cj+3xHJ5l0/uSdqpCG11drmqIR8RVjtOOslShSw56YRzX9266HIOLCSiDnkHE1KdLiMJYYi6d+tZ
2NgkZSJtUtJHEtPortQnYoQ1JagElVOtDGqEsY40fBhCe8Wsr5eGQPJecOw0R+JAeqXSnJ7BmUaM
FUT2NsmceFURzO2tGEdZelBqB2rI/SpRhX6k3AqKWrRdGs5pl6Qx9wHnUjGTlLUo/kjDc9aODZ+i
0lqYO43zXCRppRUulCFOi6h5J/EDQNn9Mjg/NrohQs9Cl5r3yps0n4dVba7lj2qB/fP+RDDeJjgp
k5XkTMFnf2q570/mfDDWzaFPj9VsvSUP7w23S3PpOikLvAwjUnFe1cvTeqxdIsA7uu7dgow3SbAa
cH2+uvFICMsIg4qyPYWzvJpMbz7EN3mScYGN6xTBM8FrEcLy5PxH788nU9XN/DNvHODPmpsJIX5u
zluOzAax9a6aFHfjexynAMFlNxvdGalrIVb4XE/m/bgs3NrJ5FMQuNcfKaSJksiHvPNih3Zffxpm
kBB20EioOHFyZbtq6Ykw4pb52jrpSt5W1jFXJ0cXV8fMdOmdnmoGqNugi5y+UMvpkT7R0jJs3l1E
F6/tbG8NsVhoDCSu2Au7ICWKHvccR+JK06JWOkPP/BNPDuFh4CmUoyP9E7d7K41OhuLqFGpQscco
W0G1P9L1CrD2Xo58oXuPLIVv1mTN447QcBp7Tu6lv6EjYQCPF4314WqA/i9ym2qnQrT/HugH4+57
wLhFnVN4a54nyyf5jn2f2HfM98HQ2namoabHgqptuPXDlA+M8X0oktzUECts+v2Qi+8YHf0QCqiu
LYid9dOQ8MafWJ3ujQcSJtAvwXxIJ5nM7BX6O5NHmZoTVdaCZBPIcUhuBAnnUivSjPOZ672W/VGu
9Y6tJow17uFmkL3YzzBRBYTT/6w4xLOwojO1Xd950FgxktOXOR9I/sYTvxWZVlyo3xyaxtHmxt7o
jtaFcePa+Yl4CsdWoIPknsiUHt2BL7i3qVlkN8StHrvKQsyxvRgiJOrhk13waTNwlHh5sXRxc0au
7Wj+kJJdudoJai/01TrDJdZEuvHUJAEsoZHZ6Vp7albcpGPtjPAiIhUIHJBWOTp6mBEu3qHgZY9q
Dd8W9aUTLq0um7Eml/yzE077OFPgRFA2rRyYHTEDGVpj5MU2/9S3wex6u8JoKZrXR3ysbGPPu563
6iTGHWoTESEK6ZocSMzTqKfoqd+m7kMS3CkhUdx7JADCPhYpcRTTmt9JpkFf6zQcB9J3L1aKQdgT
jXN2SGqBhh7vi1ldz5qufWg3WmvPFEzxDbI2JF557U0bhwmhJbjVDtw699Hpdj64KISFmulZB46H
sE2DtWJzvt45S/MgtGM5SbS1I1mGC0jFG6L1SHCcMUZczRwqxyfDo6vB25M92RJF0jAmQS1tFZob
WtTzB89WRPVaim+PU99Wl+zxX2HgWKyxUiA/Judep2MjJenrf/lybksoOPTGeNORRtuSiBwL5prE
z9wfZHwR9i7eXUIwbpPUbUPqPZAEcqn0+2/xaWPkdn3m/b57WhcC+Ptu+Y/QedP3+kvrWfUIm/fw
v/4K/mSgeBa/fOjjyx/850f6M82nZSI3xxeAD4tfc9w3/hb8iaIpLTTcHF9o4OymTl8Ojo3/tHF2
l8L9X8kK/uv/rd/jONRmBd/unvtSLSD68O1/5rlb803P8e33i9q9H3///bJ23+deWfuKT+NZXvSm
KS8/OPdRFHX4/ocf/6Ntt/zskRjDrx9XE1QtWfuaTyxrG6QtJIV9/cmlY0tfghE1zFa8mI9Qa0gL
t6F2D6Xqg//S/n09CC0xN0URaT5oVmfEvcLXMnrbujXynqz/MEKjFC/eyXr2MRQjnAPvCg9iXuDZ
aatfTbY8T1H80ld/tHYLO7fOKXkM2fRUud9PkxoTObtZrCG7fsfkssX5DU8pObKKUzWcKkJX9rFW
gg6kFrQnIa2vLDn/kOMe5VIauISCS8KvevSJtmGU7fOJyEZGb4ctLLfWEZYLTvsCcunadeEHkVeU
CInCcLiujVbRcRRKYGId26bwmhZ+D6k7cF7jUDb+cXwawgdXJHW5U4of5su5C56jrlyeFd+tIRO3
I9nb8F693LUkyn4P6fZ780b6weZyBCYfFuEC2APsVHVswlf9EJu02lK0bbvItHoQ4u40vKXRc8Nl
AluZbSKxP11HmSZjB5cbf/7Wi19Iiz4QliD0f3AgE7+4hBy4SSpbaIg8DMyLKe+6Z0H9GjE1XdTd
+Kb+AqxMP6+/pfNRHLPHPzj+VQ9H5h3JQrd+s+n21lv1zPe8xxvmy0E2wS/KuAfKrZsD/OGDB6cr
u4NoWTgVCXC3B0H3aRVz6U7nOoy0cPKDrmf6bqojY3W3tRFQjXbO9RqqfG5+aIRVzw9e7L9CSKZ6
RPdmOhycAhV1IBNigFe0XErfN6XaQtRojDMh7RJCh5/xBjKnA/XtE6pxU/QJhmp0YlxM4GsDkkOq
uAIRqjeuPh2/aiHV13pqWW2PxNbnFoHnoTt5gQG3dsG4etHIRo2LEjhxCjGkkvUuOcDZndPKIf8G
fjud8XJDymue/KuId1AU01ZCIq3ihGpklvhcnmnCb6RS8dO0og1HqmDVAlfXXp3oERNcKJn6U7WS
UcHlNReOMFytdepUffWPbZLPDwnD/JsIsJmAhthBOhRjy0snNg6KDSRZ5uXGjYOOVQ1x/Vll6sFX
oNA9205AGCdrHJhy63QAcRZHkDuDZo7WWyB5z5Gu3O0tl1wKLkKjBTyJXu1NA5Vj6DhumuQOfE8j
vHEjNDHEsazMmjfWjlO8kZ2z6HnUMzF29dBazrbic2as3+7hZWst7XgtZ8p7I8fLK1JXnG3A041X
ZcLsNRpkXQdrfHZIs9MV/a/uxc/yRi7XhXqR85nMXEBiC3f77C9Ka8yIoKOndM6Jax0fhMOS9K97
X7FNJCLhvB5OMSBbaxp9NFzyS/AKJN4ArZDkzR/u1RRl8x2e7lkx6Jve8rneK/xNpJBpGjjEbRrI
mPe+ETToKvPUH1cqq+ap9y9RzxNBio40jA/fGHF/sTvas2WOH8UYP/5x5w+93BSvTDFlcUMu5vNy
wkvmzgRzxX2/MnMc+QEScacaEwy2Qg5mqniPLzczmWXedcdU2EnD4+0ZqK+Qjuf14t9Qpn6agFfF
K5WfhtdM3OdTmrg9yCs0qSXvysZ6G4c4mEhp0RnPpXEFL8fnz91xWQGsXCIPDlsDsEJwjN+KfU1+
uRfvEMQxZ/ApZA8/EmZFMbWTv4oEbnwHLC7wyx7xGrNP6tjgcNDVzFsheVUlbwtL88Wy3vReCFLj
8ma94wSt4eZ9wW+aOaIgjnTkp465qKDD39E95Lp8uuuYnwvyTPHutCsaLh/RMoetP05oRFqbVYVq
2y3FeoRWQmI1S8uiIIhnJAl1SsKVJR3z63JhU/M+9etkbrHTAotKqy3oJCjraoH6NmfNcMoQLY8N
L7KFyOmWPSKRZMvoxuabapmQqGZteuGs+l68YXZ///Vvxrwtk0kOQgx7HfPk79giwFv/MQiLaY4j
GZjsA205Mu1QPHp9tHnPL+V+0jFvycXff9Ex/Fp2GosJQyKx//r1d70ID9kNHtP4Z8JkOJ4ts9/L
lDyXjnlHXxwleGsSLaqO+akH3sxyokneaePSp4uXXBOEQWRQtDQ/gVn0+zsklC3x9qwnhZyTtZwj
jVwUGSiC6uihP2Bnwyvsn8jsMIPOGlF+XhKrSJEcxJOVt+7Es+PJXSU0LWD+PskXM8TFQPbJFfqK
rtO5XcPRqzCHitnBWt9tYCQ6k+j9vUdBCyHGrBN4DQeh2C+w7mW2RNMHiGbWJnqelEmVzrFQ+g2s
N6F50HvmUW0DuhjXBXYhEdFeRhiT1waEiXfLOvlUlIsUfGXu/dSL5eKJ8y93lGftAY6j3dYOo11/
anrf2S0i4s/L7K6NB4JWINKSxIu6FjkDQn/vGbI6cOMZmbfkAJA5Oc1IMazRzbXvBBZiBLDwvLhl
LbGBEm9PiRotDJ44Ed00PyLGMan3U1YGbRSwyBs43oOTcrJa59lmVGVZv+RlneAsw36M5oaVRFiS
EeoO1Wtvj3LCb648j/oGgqC/7GxYapp9oF+HJJfz5c0smUPFmSdi86+cY7424Y+6W+qgjcOOxMbg
D6c4uqmtp130KI1n1bg7L8eL24PuM0InkuMXkZ/zKD7O4x9Qzq8V3/xS8Ybieg3F9RajllX3vSUR
vyamnqY2gz8oygJL4D3ezVxxzEY8R4MDQV63GEr/EJSSW/LharB7aH7SxoQhH8+ijMb467p+eYMt
Vl7D7b/orb3fXI0k2Xjs9PM82N76iDO2idHvKdTk8wxQnB/k4x4N8+IZjZ7dsunHvb8kGTkCc3PW
N88OXrzcpxjl+/3ui1evui+efXeAbC6g9ya9lYP/t1sB3yMXXjwYgt/9GX7LGYncwtYpEmIkdCR9
fGRaLkcovEPs73LXhP3Ll6T47ohKpk9DkLO5j7eoYbFub723OBebrKAidqCIPf/uoPviAGgiLpfB
/jbXsRxGv5LvQkJKiP2rWG5vnZa8qREvrOAbrmioyxSvKsEtv6ekTMkw5Fga5uDg+bNn7pHtrc8M
qTdnSH+b8re1wHGDEW9e9u55Z7x/S7yKGxQnn7FQc8Y0L5CClaajspHl4Zf68InzZfR2sPyOoWwe
6wq1dt77LRF7KX9LWoHr8NhonyU4jEIUds2NkXzakLrWrXYq9ZPUm+PUPL9Lz/ijrRhOmrf8Uc1k
cZsVhwKSJoanm1EcjcMblngBkpy5wjAUW0EUVQn+RXuJtZCa2b8Y5AH5/UYpdvm613pJDhaoyOEB
8wTpl/yukfDWs/0JndQdWY9bGAcZvmeUviFZozngUClfO91MMRdnUgA4QvitElMcu4Fb4Dl+970k
ivHra6fWj4qFnr8wuLzic/izouLxeC7KH5YdCtpKWydoa5Y6t4oFBU1LFlAGo4SuNJ0nFHF07DgW
0QB4nTgLlwCpSWAXtR+1GLF8JO7gdc/Agps/df+wT15yCyiBIYBM1wX3XwPbO0eo0V0QMz5RU7YV
+9es8fMuxyVMUCoKLnE9helR5F0KLiwTjkQCC6rg92fxdMysrheHe3ur1aoHs9Yrypu9dFH22kuS
T6NBjSzX08wl9yPBL4hYamaI3+Fac3cup4CF+rRI72SGeEFkzdwHjRJ5pUe0Z7oT1mhEnngV+FTg
WDYNhIW3MUkInBxFZWFzJkWPX6EI6jKz6BaOXn5sNhzzz1Rw6wgOAFHpb45kvUcz849/NHeTj/7w
EOnFtHzefRqrzIVTmUruhlJMnSrmFAZ3bsvmLBfTNiWzyFUmVQk21r92j+vm6kBwdK5j2QFekbPw
IjLmBhPBJZIGdbP2X/X4MEu+zscZfFQb4QkQq2AXk7eGVWRRCcCqLhvHkMuKyc2T/tAMhk+QWkyl
7er63Ynsjxy8/XB9cdXhLy6ufuqfD/5v/3pwcW7enewN6TsGcXVyeXUyPDm/HtI9BMkMLy/OhxfY
F/T2H2ZncGr65//YFSCD8+uTq/OTazO8OCL2/YMuHeOCKGJ38eT8p8H5ycnV4Pwnc90f/t2cXlwd
nZjjwfDofX9wZvrv35tf+ldX/fPrwcmwY05+BQYYXuCcXb4fnBx3CODR+w/HgELzMOcX1+b94Gxw
TYhdXwApB+QfhEL/mhHEWzMuToXCjC8NfebmfHUyODe/DGh0wKJrwPCEIV0NfnonBMBfigGDCYgS
YHN2cnX0jv7svx28H9DA9MDp4Poc2J/iYXPZv7oeHH14378ylx+uLi+GJ04ivsN7YlXrrLka4crO
0a6sDnfw3rAY89vHdhDYYItDU3Q4ncvHRjgvgS2F6jZvV6QDqpKXQiKX2lgLYujYbWYo9jMfs5JU
nBaEIeaGTYih7HOR9CA2BIjBybjclJatVfB9L8qiRdM91XOtfBWNbPHJBJbAd6liYuEgHS/3srdN
DX+TQuJ5v+75Uiu7u+h6kKx73Ieh5UXXhYlY3RUAEtd6BgPjqmF8EOdR98fhoW+aqtLF4dw3df9N
98q4nTzkbnKR7aD3TOesn/kPcZXxNVcYBZv4ruQH7pY8lLe3Na9EG5Ryu2pe8zVFDQcpcpm1np6n
k8P9Fkb89rgXr/e/e2auri/3+h8vzTPz+lULdr2YJ4vDZ2Yxni/3vn8Gz7s59vhWzmmIv9Xhmj+P
YppwJPH/inEadn88OjSOfbhmLv7+EBdDrfh+TqK55JtYqVXsw+cH/ZOjtwfPXzx//v3f/ghbvz94
FbH12/lKPvvkAb72SbPw61t4qblXT1T8ClWn3Xjh4DoT9MUL8+uvv0bg1gvDjVk/O2jO+7F+HkUK
9UjM/w9QSwECFAAUAAAACAA8ZFs0xrVGHos0AABqnQAAIQAAAAAAAAABACAAtoEAAAAAU0lQLWZv
ci1zdHJlYW1pbmctbWVkaWEtc3ctMDAudHh0UEsFBgAAAAABAAEATwAAAMo0AAAAAA==

------_=_NextPart_001_01C63BCC.6DC5EE71
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

------_=_NextPart_001_01C63BCC.6DC5EE71--




From mmusic-bounces@ietf.org Mon Feb 27 19:23:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDse3-0003Ek-Me; Mon, 27 Feb 2006 19:23:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDsV8-0006b6-KV
	for mmusic@ietf.org; Mon, 27 Feb 2006 19:14:02 -0500
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDsLo-000126-Eq
	for mmusic@ietf.org; Mon, 27 Feb 2006 19:04:25 -0500
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0IVD00LV0EVAHI@mailout1.samsung.com> for mmusic@ietf.org;
	Tue, 28 Feb 2006 09:04:22 +0900 (KST)
Received: from mahesh ([165.213.213.73])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0IVD001YREVA38@mmp1.samsung.com> for mmusic@ietf.org;
	Tue, 28 Feb 2006 09:04:22 +0900 (KST)
Date: Tue, 28 Feb 2006 09:03:12 +0900
From: Mahesh Govind <mahesh.govind@samsung.com>
Subject: RE: [MMUSIC] SIP-RSTP Draft
In-reply-to: <768EE6AB7D56D54BB5000EC2DD113E715EBC1D@de01exm61.ds.mot.com>
To: 'Montpetit Marie-Jose-MGIF0300' <mmontpetit@motorola.com>
Message-id: <006501c63bfa$5db14800$49d5d5a5@mahesh>
Organization: Samsung
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb7a33d18683bf5063a44e640cf125f1
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2084752557=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2084752557==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_4JfBN80dmwZ1C8SS2wp3iQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_4JfBN80dmwZ1C8SS2wp3iQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

HI,

 

 

I have few questions here , from an implementor's point of view.

Chances are there that these may be discussed many times .

 

Instead of having dual stack, whether a convergence of RTSP with sip is
better?

This is because if you compare the syntax and semantics of a RTSP and SIP
message 

I think they have many things in common.

 

1)       Message structure

2)       Headers

3)       Message body

4)       Authorization and Authentication

5)       Problems with Nat and fire wall

 

Also sip provided many more things which RTSP lacks.

 

Why should I implement two protocols, which does some what similar job.

If you think from an endpoint perspective, where you have memory
constraints, if I can avoid

a protocol stack , I can save many things.

Another question is if I am using RTSP for media control, I have to use some
other mechanism

to fetch the details of  the media streams. 

 

 

Consider a use case of a device such as an Integrated set top box, which
provides a voip phone facility also.

For making such a device I may be using sip .SIP may be used to fetch the
program details, sip may be used to 

Make phone calls, if we can add some (missing) features to sip which will
help us to have control media streams,

I can leave with a single protocol for all the signaling purpose.

 

I think it may be better if we can have an apple to apple comparison with
SIP and RTSP .It may not seems to be fully

Logical, still I think it may be worth. I think such a comparison may cover

1)       Syntax

2)       Semantics

3)       Entities

4)       Issues which are common to both protocols

5)       Advantages of each one over other. 

If it is ok I can provide such a comparison.

 

With thanks and regards

Mahesh

 

 

 

 

 

 

-----Original Message-----
From: Montpetit Marie-Jose-MGIF0300 [mailto:mmontpetit@motorola.com] 
Sent: Tuesday, February 28, 2006 3:34 AM
To: mmusic@ietf.org
Cc: steven.d.whitehead@verizon.com
Subject: [MMUSIC] SIP-RSTP Draft

 

Attached. We missed the deadline :-( With the Winter Break here I guess it
was unavoidable. 

 

I guess we can start a discussion? Xavier Marjou and I will be at the
meeting.

 

Marie-Jose

 

Marie-Jose Montpetit, Eng. Ph.D.

Motorola Connected Home Solutions

NEW PHONE: +1-781-372-8115

mmontpetit@motorola.com

 

 


--Boundary_(ID_4JfBN80dmwZ1C8SS2wp3iQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=blue>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>HI,</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I have few questions here , from an implementor&#8217;s
point of view.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Chances are there that these may be
discussed many times .</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Instead of having dual stack, whether a
convergence of RTSP with sip is better?</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>This is because if you compare the syntax
and semantics of a RTSP and SIP message </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I think they have many things in common.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>1)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Message structure</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>2)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Headers</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>3)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Message body</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>4)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Authorization and
Authentication</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>5)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Problems with Nat and
fire wall</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Also sip provided many more things which
RTSP lacks.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Why should I implement two protocols, which
does some what similar job.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If you think from an endpoint perspective,
where you have memory constraints, if I can avoid</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>a protocol stack , I can save many things.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Another question is if I am using RTSP for
media control, I have to use some other mechanism</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>to fetch the details of &nbsp;the media
streams. </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Consider a use case of a device such as an
Integrated set top box, which provides a voip phone facility also.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>For making such a device I may be using
sip .SIP may be used to fetch the program details, sip may be used to </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Make phone calls, if we can add some (missing)
features to sip which will help us to have control media streams,</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I can leave with a single protocol for all
the signaling purpose.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I think it may be better if we can have an
apple to apple comparison with SIP and RTSP .It may not seems to be fully</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Logical, still I think it may be worth. I
think such a comparison may cover</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>1)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Syntax</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>2)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Semantics</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>3)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Entities</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>4)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Issues which are common
to both protocols</span></font></p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>5)<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>Advantages of each one
over other. </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If it is ok I can provide such a comparison.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>With thanks and regards</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Mahesh</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Montpetit
Marie-Jose-MGIF0300 [mailto:mmontpetit@motorola.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, February 28, 2006
3:34 AM<br>
<b><span style='font-weight:bold'>To:</span></b> mmusic@ietf.org<br>
<b><span style='font-weight:bold'>Cc:</span></b> steven.d.whitehead@verizon.com<br>
<b><span style='font-weight:bold'>Subject:</span></b> [MMUSIC] SIP-RSTP Draft</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Attached. We missed the deadline :-(
With the Winter Break here I guess it was unavoidable. </span></font></p>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>I guess we can start a discussion?
Xavier Marjou and I will be at the meeting.</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>Marie-Jose</span></font></p>

</div>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<p class=MsoNormal style='margin-left:.5in'><font size=2 color=blue
face=Verdana><span style='font-size:10.0pt;font-family:Verdana;color:blue'>Marie-Jose
Montpetit, Eng. Ph.D.</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 color=blue
face=Verdana><span style='font-size:10.0pt;font-family:Verdana;color:blue'>Motorola
Connected Home Solutions</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 color=fuchsia
face=Verdana><span style='font-size:10.0pt;font-family:Verdana;color:fuchsia'>NEW
PHONE:</span></font><font size=2 color=blue face=Verdana><span
style='font-size:10.0pt;font-family:Verdana;color:blue'> +1-781-372-</span></font><font
size=2 color=fuchsia face=Verdana><span style='font-size:10.0pt;font-family:
Verdana;color:fuchsia'>8115</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><a
href="mailto:mmontpetit@motorola.com">mmontpetit@motorola.com</a></span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

</div>

</body>

</html>

--Boundary_(ID_4JfBN80dmwZ1C8SS2wp3iQ)--


--===============2084752557==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============2084752557==--




From mmusic-bounces@ietf.org Tue Feb 28 08:57:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FE5Lt-0004da-Sh; Tue, 28 Feb 2006 08:57:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FE5Lr-0004dS-Um
	for mmusic@ietf.org; Tue, 28 Feb 2006 08:57:19 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FE5Lq-00043h-8u
	for mmusic@ietf.org; Tue, 28 Feb 2006 08:57:19 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2468F4F0028
	for <mmusic@ietf.org>; Tue, 28 Feb 2006 14:57:17 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Feb 2006 14:57:16 +0100
Received: from [147.214.30.119] ([147.214.30.119]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Feb 2006 14:57:16 +0100
Message-ID: <440456BC.2060909@ericsson.com>
Date: Tue, 28 Feb 2006 14:57:16 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Feb 2006 13:57:16.0852 (UTC)
	FILETIME=[E25E0740:01C63C6E]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [MMUSIC] RTSP: Removal of ranged PAUSE requests. 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi,

In the review I am conducting on the complete RTSP 2.0 specification in 
order to get it WGLC ready, I did found some overlapping functionality.

As the spec currently is written one can both use a PLAY request in play 
state and PAUSE with a range header set to a future date to halt a 
presentation in the future. I think this duplication of functionality is 
unnecessary.

I would suggest that we remove the possibility to provide a range header 
in PAUSE request. That way PAUSE will be cleaned up to be a way of 
interrupting ongoing playback directly only.

PLAY will be used to change an already ongoing PLAY request. Thus being 
a tool to modify the range provided in the initial PLAY request. For example

PLAY
range: npt=0-60

can be modified to PLAY range: npt=0-45 by:
PLAY
range: npt=-45

What does people say about this?

Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 28 09:25:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FE5n6-000672-CR; Tue, 28 Feb 2006 09:25:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FE5n4-00066x-JS
	for mmusic@ietf.org; Tue, 28 Feb 2006 09:25:26 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FE5n2-0004zz-Le
	for mmusic@ietf.org; Tue, 28 Feb 2006 09:25:26 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1BE0D633; 
	Tue, 28 Feb 2006 15:25:24 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Feb 2006 15:25:23 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Feb 2006 15:25:23 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 7401F24D8;
	Tue, 28 Feb 2006 16:25:23 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3400E1ABAD7;
	Tue, 28 Feb 2006 16:25:23 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 8F3C81AB9B1;
	Tue, 28 Feb 2006 16:25:22 +0200 (EET)
Message-ID: <44045D4C.9070709@ericsson.com>
Date: Tue, 28 Feb 2006 16:25:16 +0200
From: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Organization: Ericsson
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
Subject: Re: [MMUSIC] Accessibility
	relatedparametersindraft-ietf-mmusic-sdp-media-content-01.txt
References: <GLEFKJBKNILEBOELNIBIIEJEDGAA.gunnar.hellstrom@omnitor.se>
In-Reply-To: <GLEFKJBKNILEBOELNIBIIEJEDGAA.gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 28 Feb 2006 14:25:23.0843 (UTC)
	FILETIME=[CFE46D30:01C63C72]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mmusic@ietf.org, Gonzalo.Camarillo@ericsson.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Gunnar,

Gunnar Hellstrom wrote:
> Arnoud,
> OK, you are right. The txp content indicator is used for indicating
> limitations in media handling. The gateway should know, and send the txp
> indicator only in calls where there are limitations.
> So for a call with a V.18 capable gateway to a V.18 textphone, the indicator
> should not be used and the SIP client should use a user interface that
> encourages two way simultaneous typing.
> 
> I agree, and then want to ask Jani to take in this extended description of
> txp in the media-content specification:
> 
> Typical use case for this is when there are presentation or communication
> limitations in the capability to handle simultaneous communication in both
> directions. This can for example be a connection where one endpoint is an
> analog textphone of the common types that requires turn-taking control by
> the user, and the other one is a native IP based text telephone.
> The user should be made aware that such limitations prevail.

Now the text in the draft is:

   txp:
   This indicates that the media stream is originated from a textphone,
   and it requires special behavior from the receiving application.
   Typical use case for this is e.g., a connection where one endpoint is
   an analog textphone, and the other one is a native IP based real time
   text capable terminal.

First you proposed that the following sentence should be added "The user 
should be made aware that presentation and communication limitations 
exist". This is application behavior, and we don't want to standardize 
that. If the application supports "txp" draft, it will do it anyway.

Can you *briefly* answer what is wrong with the current text and why it 
needs to be changed? The reason why I'm asking is that the only 
difference I can see is the "application must inform the user" part.

As I have said before, I encourage you to specify the usage of "txp" 
value on some other draft, if you want.


-- 
Jani

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mmusic-bounces@ietf.org Tue Feb 28 09:37:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FE5ya-0008Ic-Ku; Tue, 28 Feb 2006 09:37:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FE5yZ-0008IX-Ef
	for mmusic@ietf.org; Tue, 28 Feb 2006 09:37:19 -0500
Received: from mail5.audiocodes.com ([212.25.125.21] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FE5yY-0005QS-5b
	for mmusic@ietf.org; Tue, 28 Feb 2006 09:37:19 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Tue, 28 Feb 2006 16:38:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] SIP-RSTP Draft
Date: Tue, 28 Feb 2006 16:37:03 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD601DCBB61@aclmsg.corp.audiocodes.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] SIP-RSTP Draft
Thread-Index: AcY7/VZMfLBdNeqHRNCcpoNfzyk+nQAdELXA
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
To: "Mahesh Govind" <mahesh.govind@samsung.com>,
	"Montpetit Marie-Jose-MGIF0300" <mmontpetit@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9d5866e4c615ceea0db8f42c46495d22
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0635745325=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0635745325==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C63C74.7040037B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C63C74.7040037B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm also speaking from the implementor's point of view, when are
speaking about using sip for call establishment, it is ok. If your call
using some media services like play video/audio announcements it is
also. If you are going to perform some voice recognition , you are going
to use MRCP2. Why? You can extend SIP to provide all MRCP logic inside.
The same is valid for RTSP. The main advantage of the contributing SIP&
RTSP together is to provide really real time streaming control (RTSP
should insert Real time inside).=20

Today SIP enables you some stream control using Application Server and
various xml based protocols like MSCML/MOML/MSCP/MSML/.. , but it is far
from being real time.

Another implementor's point of view, is Media server side. If you are
using SIP/MRCP2 for voice recognition services, you may reuse the same
resource for streaming. SIP&RTSP interworking will enable real time
stream control during the open SIP session over RTSP.

You right it is some memory constraints, but the same you have today,
when SIP is used only for call establishment and rtsp only for control.

=20

Regards

=20

Osher

=20

________________________________

From: Mahesh Govind [mailto:mahesh.govind@samsung.com]=20
Sent: Tuesday, February 28, 2006 2:03 AM
To: 'Montpetit Marie-Jose-MGIF0300'
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] SIP-RSTP Draft

=20

HI,

=20

=20

I have few questions here , from an implementor's point of view.

Chances are there that these may be discussed many times .

=20

Instead of having dual stack, whether a convergence of RTSP with sip is
better?

This is because if you compare the syntax and semantics of a RTSP and
SIP message=20

I think they have many things in common.

=20

1)       Message structure

2)       Headers

3)       Message body

4)       Authorization and Authentication

5)       Problems with Nat and fire wall

=20

Also sip provided many more things which RTSP lacks.

=20

Why should I implement two protocols, which does some what similar job.

If you think from an endpoint perspective, where you have memory
constraints, if I can avoid

a protocol stack , I can save many things.

Another question is if I am using RTSP for media control, I have to use
some other mechanism

to fetch the details of  the media streams.=20

=20

=20

Consider a use case of a device such as an Integrated set top box, which
provides a voip phone facility also.

For making such a device I may be using sip .SIP may be used to fetch
the program details, sip may be used to=20

Make phone calls, if we can add some (missing) features to sip which
will help us to have control media streams,

I can leave with a single protocol for all the signaling purpose.

=20

I think it may be better if we can have an apple to apple comparison
with SIP and RTSP .It may not seems to be fully

Logical, still I think it may be worth. I think such a comparison may
cover

1)       Syntax

2)       Semantics

3)       Entities

4)       Issues which are common to both protocols

5)       Advantages of each one over other.=20

If it is ok I can provide such a comparison.

=20

With thanks and regards

Mahesh

=20

=20

=20

=20

=20

=20

-----Original Message-----
From: Montpetit Marie-Jose-MGIF0300 [mailto:mmontpetit@motorola.com]=20
Sent: Tuesday, February 28, 2006 3:34 AM
To: mmusic@ietf.org
Cc: steven.d.whitehead@verizon.com
Subject: [MMUSIC] SIP-RSTP Draft

=20

Attached. We missed the deadline :-( With the Winter Break here I guess
it was unavoidable.=20

=20

I guess we can start a discussion? Xavier Marjou and I will be at the
meeting.

=20

Marie-Jose

=20

Marie-Jose Montpetit, Eng. Ph.D.

Motorola Connected Home Solutions

NEW PHONE: +1-781-372-8115

mmontpetit@motorola.com

=20

=20


------_=_NextPart_001_01C63C74.7040037B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.emailstyle17
	{font-family:Arial;
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m also speaking from the =
implementor&#8217;s
point of view, when are speaking about using sip for call establishment, =
it is
ok. If your call using some media services like play video/audio =
announcements
it is also. If you are going to perform some voice recognition , you are =
going
to use MRCP2. Why? You can extend SIP to provide all MRCP logic inside. =
The
same is valid for RTSP. The main advantage of the contributing SIP&amp; =
RTSP
together is to provide really real time streaming control (RTSP should =
insert
Real time inside). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Today SIP enables you some stream =
control
using Application Server and various xml based protocols like
MSCML/MOML/MSCP/MSML/.. , but it is far from being real =
time.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Another implementor&#8217;s point =
of view,
is Media server side. If you are using SIP/MRCP2 for voice recognition =
services,
you may reuse the same resource for streaming. SIP&amp;RTSP interworking =
will enable
real time stream control during the open SIP session over =
RTSP.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>You right it is some memory =
constraints, but
the same you have today, when SIP is used only for call establishment =
and rtsp
only for control.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Osher<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Mahesh Govind
[mailto:mahesh.govind@samsung.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, February =
28, 2006
2:03 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Montpetit
Marie-Jose-MGIF0300'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [MMUSIC] =
SIP-RSTP
Draft</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>HI,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have few questions here , from an
implementor&#8217;s point of view.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Chances are there that these may be
discussed many times .</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Instead of having dual stack, =
whether a
convergence of RTSP with sip is better?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This is because if you compare the =
syntax and
semantics of a RTSP and SIP message </span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think they have many things in =
common.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>1)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Message structure</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>2)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Headers</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>3)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Message body</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>4)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Authorization and =
Authentication</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>5)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Problems with Nat and fire wall</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Also sip provided many more things =
which
RTSP lacks.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why should I implement two =
protocols,
which does some what similar job.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If you think from an endpoint =
perspective,
where you have memory constraints, if I can =
avoid</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>a protocol stack , I can save many =
things.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Another question is if I am using =
RTSP for
media control, I have to use some other =
mechanism</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>to fetch the details of &nbsp;the =
media
streams. </span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Consider a use case of a device =
such as an
Integrated set top box, which provides a voip phone facility =
also.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>For making such a device I may be =
using
sip .SIP may be used to fetch the program details, sip may be used to =
</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Make phone calls, if we can add =
some
(missing) features to sip which will help us to have control media =
streams,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I can leave with a single protocol =
for all
the signaling purpose.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think it may be better if we can =
have an
apple to apple comparison with SIP and RTSP .It may not seems to be =
fully</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Logical, still I think it may be =
worth. I
think such a comparison may cover</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>1)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Syntax</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>2)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Semantics</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>3)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Entities</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>4)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Issues which are common to both =
protocols</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in;text-indent:-.25in'><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>5)</span></font><font size=3D1 color=3Dnavy><span =
style=3D'font-size:
7.0pt;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Advantages of each one over other. =
</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If it is ok I can provide such a
comparison.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>With thanks and =
regards</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Mahesh</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Montpetit =
Marie-Jose-MGIF0300
[mailto:mmontpetit@motorola.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, February =
28, 2006
3:34 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mmusic@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
steven.d.whitehead@verizon.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [MMUSIC] =
SIP-RSTP Draft</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Attached. We missed the =
deadline :-(
With the Winter Break here I guess it was unavoidable. =
</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>I guess we can start a =
discussion?
Xavier Marjou and I will be at the meeting.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Marie-Jose</span></font><o:p=
></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:blue'>Marie-Jose
Montpetit, <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">Eng.</st1:place></st1:country-region>
Ph.D.</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:blue'>Motorola
Connected Home Solutions</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dfuchsia
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:fuchsia'>NEW
PHONE:</span></font><font size=3D2 color=3Dblue face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana;color:blue'> =
+1-781-372-</span></font><font
size=3D2 color=3Dfuchsia face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:
Verdana;color:fuchsia'>8115</span></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><a
href=3D"mailto:mmontpetit@motorola.com">mmontpetit@motorola.com</a></span=
></font><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C63C74.7040037B--


--===============0635745325==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============0635745325==--




From mmusic-bounces@ietf.org Tue Feb 28 11:35:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FE7p3-0001n8-Mt; Tue, 28 Feb 2006 11:35:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FE7p1-0001ew-Um
	for mmusic@ietf.org; Tue, 28 Feb 2006 11:35:35 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FE7p0-0001BF-5p
	for mmusic@ietf.org; Tue, 28 Feb 2006 11:35:35 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-2.cisco.com with ESMTP; 28 Feb 2006 08:35:34 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1SGZTHj028582;
	Tue, 28 Feb 2006 08:35:33 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 28 Feb 2006 08:35:30 -0800
Received: from [192.168.0.10] ([10.21.81.175]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 28 Feb 2006 08:35:29 -0800
Mime-Version: 1.0 (Apple Message framework v746.2)
References: <E1FDs7u-0005jq-Hb@stiedprstage1.ietf.org>
Message-Id: <37021998-BE24-4BFE-84C8-1B9DE68F3143@cisco.com>
From: Mark Baugher <mbaugher@cisco.com>
Date: Tue, 28 Feb 2006 08:35:21 -0800
To: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@acm.org>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 28 Feb 2006 16:35:29.0526 (UTC)
	FILETIME=[FC712160:01C63C84]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fca741f5016e6ff607eaed2fd431d10d
Cc: mmusic@ietf.org
Subject: [MMUSIC] Fwd: I-D ACTION:draft-baugher-mmusic-sdp-dh-00.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2069167593=="
Errors-To: mmusic-bounces@ietf.org


--===============2069167593==
Content-Type: multipart/alternative; boundary=Apple-Mail-43--371435195


--Apple-Mail-43--371435195
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Colin, Joerg
   David and I wrote this I-D to improve the end-to-end security  
available in SDP security descriptions.  We think it is of interest  
to mmusic and would like the opportunity to present this to the  
Working Group at the next meeting.

Mark

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: February 27, 2006 3:50:02 PM PST
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-baugher-mmusic-sdp-dh-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
>
> 	Title		: Diffie-Hellman Exchanges for Multimedia Sessions
> 	Author(s)	: M. Baugher, D. McGrew
> 	Filename	: draft-baugher-mmusic-sdp-dh-00.txt
> 	Pages		: 29
> 	Date		: 2006-2-27
> 	
>    This memo defines a new Session Description Protocol (SDP)  
> attribute
>    for exchanging Diffie-Hellman (DH) public keys.  The attribute  
> is an
>    SDP session-level attribute for describing DH keys, and there is a
>    new media-level parameter for describing public keying material for
>    SRTP key generation.  The SDP attribute supports the key
>    establishment schemes of NIST Draft Special Publication 800-56,  
> adds
>    domain parameters and supports external authentication of the DH
>    endpoint without a public key infrastructure.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-baugher-mmusic-sdp-dh-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body  
> of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the  
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-baugher-mmusic-sdp-dh-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-baugher-mmusic-sdp-dh-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2006-2-27160758.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


--Apple-Mail-43--371435195
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Colin, Joerg<DIV>=A0 David and I =
wrote this I-D to improve the end-to-end security available in SDP =
security descriptions.=A0 We think it is of interest to mmusic and would =
like the opportunity to present this to the Working Group at the next =
meeting.=A0=A0</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Mark<BR><DIV><BR><DIV>Begin =
forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica">February 27, 2006 3:50:02 PM =
PST</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><B>I-D ACTION:draft-baugher-mmusic-sdp-dh-00.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Reply-To: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><A =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A New Internet-Draft is available from the on-line =
Internet-Drafts directories.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Title<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: Diffie-Hellman Exchanges for =
Multimedia Sessions</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Author(s)<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: M. Baugher, D. McGrew</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Filename<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: draft-baugher-mmusic-sdp-dh-00.txt</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Pages<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: 29</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Date<SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 2006-2-27</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>This memo defines a new =
Session Description Protocol (SDP) attribute</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>for exchanging Diffie-Hellman (DH) public keys.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>The attribute is an</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>SDP session-level attribute for describing DH keys, and there is =
a</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>new media-level parameter for describing public keying material =
for</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>SRTP key generation.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>The SDP attribute supports =
the key</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>establishment schemes of =
NIST Draft Special Publication 800-56, adds</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>domain parameters and =
supports external authentication of the DH</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>endpoint without a public =
key infrastructure.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A URL for this Internet-Draft is:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-baugher-mmusic-sdp-dh-00=
.txt">http://www.ietf.org/internet-drafts/draft-baugher-mmusic-sdp-dh-00.t=
xt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DI=
V style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of the message. <SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">You can =
also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Internet-Drafts are also available by anonymous FTP. =
Login with the username</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"anonymous" =
and a password of your e-mail address. After logging in,</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">type "cd internet-drafts" and then</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"get =
draft-baugher-mmusic-sdp-dh-00.txt".</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">A list of Internet-Drafts =
directories can be found in</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Internet-Drafts can also be obtained by =
e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Send a message to:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-baugher-mmusic-sdp-dh-00.txt".</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><BR class=3D"khtml-block-placeholder"></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2006-2-27160758.I-D@ietf.org">2006-2-27160758.I-D@ietf.org<=
/A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I-D-Announce mailing list</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.=
ietf.org/mailman/listinfo/i-d-announce</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-43--371435195--


--===============2069167593==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

--===============2069167593==--




