
From rem@videolan.org  Sun Aug  2 12:03:48 2009
Return-Path: <rem@videolan.org>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EE233A6C55 for <mmusic@core3.amsl.com>; Sun,  2 Aug 2009 12:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kX6qxSalrJii for <mmusic@core3.amsl.com>; Sun,  2 Aug 2009 12:03:47 -0700 (PDT)
Received: from yop.chewa.net (yop.chewa.net [91.121.105.214]) by core3.amsl.com (Postfix) with ESMTP id 743063A6C4E for <mmusic@ietf.org>; Sun,  2 Aug 2009 12:03:42 -0700 (PDT)
Received: from basile.remlab.net (cs27060099.pp.htv.fi [89.27.60.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: remi) by yop.chewa.net (Postfix) with ESMTPSA id 319CD578 for <mmusic@ietf.org>; Sun,  2 Aug 2009 21:03:41 +0200 (CEST)
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <rem@videolan.org>
Organization: VideoLAN project - www.videolan.org
To: mmusic@ietf.org
Date: Sun, 2 Aug 2009 22:03:39 +0300
User-Agent: KMail/1.11.4 (Linux/2.6.30.2; KDE/4.2.4; i686; ; )
References: <A0EC3C02-523E-480F-BCE4-FDAB64F51675@cisco.com>
In-Reply-To: <A0EC3C02-523E-480F-BCE4-FDAB64F51675@cisco.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200908022203.39541.rem@videolan.org>
Subject: Re: [MMUSIC] Quick written version of the taxonomy of alternatives I mentioned at the mic at the end of the SIP/RTSP discussion
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: remi@remlab.net
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Aug 2009 19:03:48 -0000

Le jeudi 30 juillet 2009 11:39:59 David R Oran, vous avez =E9crit :
> 1. Do a "system reset" on the RTSPv2 specification in order to make it
> capable of being used in the same overall signaling architecture the
> proponents today use SIP for (e.g. IMS environments). This entails
> giving up on full backward compatibility with RTSP v1 (which we don't
> have in practice anyway, and we have no RTSPv2 deployment yet to worry
> much about). We would re-cast RTSPv2 to use SDP offer-answer and ICE
> exactly as they are used by SIP, instead of the hybrid media
> description used in the current RTSPv2 specification. We could also
> import the P-header extension set to get the same IMS features for
> RTSP as we have for SIP. This would preserve the existing RTSP
> addressing model, its media source selection model, and its failover
> model, none of which are straightforward with SIP.

Offer-answer would simplify the specification work at the expanse of the (m=
uch=20
more costly) implementation works. VoIP stacks are _not_ usually the same a=
s=20
media playback stacks. Using the same protocol would unavoidably cause=20
impedance mismatches (some will be discovered too late in the specification=
=20
work flow) and troubles from user interface stand point. In other words, we=
=20
would screw up RTSP *again*, and have to wait for another ~15 years until..=
=2E=20
RTSP/3.0 actually works.

Media playback and multi-party sessions have very different logic. RTSP fit=
s=20
the media player model and control rather well: play, pause, seek, stop... =
SIP=20
does not, at all: invite uh? Also, those things are significantly different=
 on=20
the media path. In SIP, RTP must be optimized for low-latency. In RTSP (and=
=20
SAP too), buffering latency is more tolerable.

> 2. Design a new in-session control protocol for the media servers to
> give SIP sessions the same media control capabilities that exist in
> RTSP (e.g. play/pause/ff etc.). This would be negotiated with SDP
> offer answer just like the media itself and other in-session control
> schemes like floor control in conferences.

> 3. Adopt MRCPv2 as an in-session media control protocol. MRCPv2
> arguably has EVERYTHING needed - play, pause, scale, skip, etc. and is
> already fully integrated with SIP and deployed enough to have
> confidence that it will glue together correctly. The disadvantage is
> the MRCPv2 is gross overkill for the simple media control problem. It
> might be possible to define a minimal subset or "profile" that would
> be light weight, but I haven't even begun to think through the details
> to see if this would be easy or hard.

Those two make more sense to me.

> As an designer/implementer of both media servers and embedded
> streaming media clients, I find any of these more attractive than
> trying to glue SIP and RTSP together using interworking, state machine
> tricks, etc.

Might well be. I don't figure out what "gluing" means here.

=2D-=20
R=E9mi Denis-Courmont
http://git.remlab.net/cgi-bin/gitweb.cgi?p=3Dvlc-courmisch.git;a=3Dsummary

From rem@videolan.org  Sun Aug  2 12:12:56 2009
Return-Path: <rem@videolan.org>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB6AA3A68EF for <mmusic@core3.amsl.com>; Sun,  2 Aug 2009 12:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpZNEgzYtAJh for <mmusic@core3.amsl.com>; Sun,  2 Aug 2009 12:12:56 -0700 (PDT)
Received: from yop.chewa.net (yop.chewa.net [91.121.105.214]) by core3.amsl.com (Postfix) with ESMTP id 1734F3A6869 for <mmusic@ietf.org>; Sun,  2 Aug 2009 12:12:56 -0700 (PDT)
Received: from basile.remlab.net (cs27060099.pp.htv.fi [89.27.60.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: remi) by yop.chewa.net (Postfix) with ESMTPSA id 4AA1255A; Sun,  2 Aug 2009 21:12:57 +0200 (CEST)
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <rem@videolan.org>
Organization: VideoLAN project - www.videolan.org
To: mmusic@ietf.org, http-live-streaming-review@group.apple.com
Date: Sun, 2 Aug 2009 22:12:55 +0300
User-Agent: KMail/1.11.4 (Linux/2.6.30.2; KDE/4.2.4; i686; ; )
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200908022212.55982.rem@videolan.org>
Cc: streaming@videolan.org
Subject: [MMUSIC] Comments on draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: remi@remlab.net
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Aug 2009 19:12:56 -0000

	Hello,

A few comments:

* I'm not sure I see the point of the EXT-X-ALLOW-CACHE parameter. Does HTT=
P=20
not have extensive caching negotiation built-in already?

* It is not clear to me whether EXT-X-TARGETDURATION is mandatory or not.

* I don't understand how the receiver (the client) of the playlist can=20
_reliably_ distinguish a plain old playlist file from a live streaming file=
=2E=20
M3U URLs are already in common use to deliver "real" playlist, and the=20
semantics are significantly different from what your draft does. If none of=
the=20
new parameters you introduce are mandatory, this protocol is basically=20
impossible to implement in a way that does not break existing functionality=
 in=20
many media players.

=2D-=20
R=C3=A9mi Denis-Courmont
The VideoLAN project

From csp@csperkins.org  Mon Aug  3 04:44:29 2009
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CBCB3A694C for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 04:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1F8FBYsQ24t for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 04:44:28 -0700 (PDT)
Received: from anchor-msapost-1.mail.demon.net (anchor-msapost-1.mail.demon.net [195.173.77.164]) by core3.amsl.com (Postfix) with ESMTP id 61C783A6ABA for <mmusic@ietf.org>; Mon,  3 Aug 2009 04:44:28 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by anchor-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1MXvxu-0002f5-hV; Mon, 03 Aug 2009 11:44:30 +0000
Message-Id: <A334F10B-025F-4893-B9B4-2A6C390D2477@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
To: Ali C. Begen (abegen) <abegen@cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D5409B987D7@xmb-sjc-215.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 3 Aug 2009 12:44:29 +0100
References: <04CAD96D4C5A3D48B1919248A8FE0D5409B987D7@xmb-sjc-215.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] [Fecframe] Fw: WGLC request for draft-ietf-mmusic-rfc4756bis-02
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 11:44:29 -0000

Ali,

I've reviewed this draft, and the SDP extensions look fine to me. My  
question, which relates to some of the comments I made in FECFRAME  
last week, is if the semantics of an RTP FEC stream protecting several  
media streams with different top-level media types (e.g. a single FEC  
flow protecting both audio and video) are well defined? It might be  
worth adding some wording to explain that the signalling offers  
flexibility about which flows can be grouped, but that not all FEC  
schemes support the full range of scenarios that can be signalled.

Cheers,
Colin



On 10 Jul 2009, at 18:23, Ali C. Begen (abegen) wrote:
> I would appreciate if you could review this doc and post your  
> comments to mmusic.
>
> Thanks.
> -acbegen
>
> -----Original Message-----
> From: fecframe-bounces@ietf.org [mailto:fecframe-bounces@ietf.org]  
> On Behalf Of Ali C. Begen (abegen)
> Sent: Tuesday, July 07, 2009 4:46 PM
> To: fecframe@ietf.org
> Subject: [Fecframe] Fw: WGLC request for draft-ietf-mmusic- 
> rfc4756bis-02
>
> This short draft needs to be reviewed. Any volunteers? Thanks.
>
> -acbegen
>
> ----- Original Message -----
> From: Jean-Francois Mule <jf.mule@CableLabs.com>
> To: Ali C. Begen (abegen); mmusic@ietf.org <mmusic@ietf.org>; Joerg  
> Ott <jo@netlab.tkk.fi>
> Sent: Mon Jul 06 07:38:08 2009
> Subject: RE: WGLC request for draft-ietf-mmusic-rfc4756bis-02
>
> Ali,
>
>  Ok, noted, will send a separate WGLC announcement.
>
>  We have at least 3 drafts that need to go through WGLC but given the
> FECframe dependency, we'll expedite this one.  Can you ping one or two
> folks involved in fecframe that would be willing to formally review  
> the
> doc during WGLC?
>
> Jean-Francois
>
>> -----Original Message-----
>> From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
>> Sent: Monday, July 06, 2009 7:52 AM
>> To: mmusic@ietf.org; Joerg Ott; Jean-Francois Mule
>> Subject: WGLC request for draft-ietf-mmusic-rfc4756bis-02
>>
>> Hello,
>>
>> I would like to request WGLC for the following draft:
>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc4756bis-
>> 02.txt
>>
>> This draft is dependant on the source-specific media attributes in
>> SDP, which recently became an RFC (5576) and the current version
>> addressed all the outstanding issues. This draft is needed by the
>> FECframe WG.
>>
>> Thanks.
>> -acbegen
>
>



-- 
Colin Perkins
http://csperkins.org/




From abegen@cisco.com  Mon Aug  3 05:01:12 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F39E3A6D1F for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 05:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.989
X-Spam-Level: 
X-Spam-Status: No, score=-5.989 tagged_above=-999 required=5 tests=[AWL=0.609,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0taT2ggDxRnj for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 05:01:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 0BF2E3A6A3B for <mmusic@ietf.org>; Mon,  3 Aug 2009 05:01:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMFAJZudkqrR7MV/2dsb2JhbACCJTCWJaARiCmOJAWEGA
X-IronPort-AV: E=Sophos;i="4.43,314,1246838400";  d="scan'208,217";a="359212778"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 03 Aug 2009 12:01:13 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n73C1Dub022724;  Mon, 3 Aug 2009 05:01:13 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n73C1C61003847; Mon, 3 Aug 2009 12:01:13 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 3 Aug 2009 05:01:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1432.17F502EC"
Date: Mon, 3 Aug 2009 05:01:11 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5406618552@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fecframe] Fw: WGLC request for draft-ietf-mmusic-rfc4756bis-02
Thread-Index: AcoUL8SNWVg90otBQO2BpqavuFZkOwAAlMh9
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <csp@csperkins.org>
X-OriginalArrivalTime: 03 Aug 2009 12:01:12.0495 (UTC) FILETIME=[18787BF0:01CA1432]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9953; t=1249300873; x=1250164873; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=abegen@cisco.com; z=From:=20=22Ali=20C.=20Begen=20(abegen)=22=20<abegen@cisco. com> |Subject:=20Re=3A=20[Fecframe]=20Fw=3A=20WGLC=20request=20f or=20draft-ietf-mmusic-rfc4756bis-02 |Sender:=20; bh=kmayZsNk7R4R7urcqWs76hSax9mGqvqrWU7frpLXlwc=; b=kAVC+CjgNaKqZtaGIE0QayDAjJ+Om2l46W30WKJkOcMzQiq632nL2WCupf ZfSPfMhj9HKaEWYvhqsAv3bpDQLN+UDNVZ2cRCUhhXPMxX9qzg/nU6ch1pui t8o9uYnG35iRJkZ9pqjn+3BxTpz3K0z4Qe4U2iMwuulQC0vzmv36o=;
Authentication-Results: sj-dkim-1; header.From=abegen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] [Fecframe] Fw: WGLC request for draft-ietf-mmusic-rfc4756bis-02
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 12:01:12 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA1432.17F502EC
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhhbmtzIGZvciB0aGUgcmV2aWV3LiBZb3VyIGNvbW1lbnQgaXMgcmlnaHQgdG8gdGhlIHBvaW50
IGFuZCBJIHdpbGwgYWRkIHRoYXQgd2l0aCAoYW55KSBvdGhlciBjb21tZW50cyBJIGhvcGUgdG8g
cmVjZWl2ZS4gDQoNCi1hY2JlZ2VuDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZy
b206IENvbGluIFBlcmtpbnMgPGNzcEBjc3BlcmtpbnMub3JnPg0KVG86IEFsaSBDLiBCZWdlbiAo
YWJlZ2VuKQ0KQ2M6IG1tdXNpYyBXRyA8bW11c2ljQGlldGYub3JnPg0KU2VudDogTW9uIEF1ZyAw
MyAwNDo0NDoyOSAyMDA5DQpTdWJqZWN0OiBSZTogW0ZlY2ZyYW1lXSBGdzogV0dMQyByZXF1ZXN0
IGZvciBkcmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2YmlzLTAyDQoNCkFsaSwNCg0KSSd2ZSByZXZp
ZXdlZCB0aGlzIGRyYWZ0LCBhbmQgdGhlIFNEUCBleHRlbnNpb25zIGxvb2sgZmluZSB0byBtZS4g
TXkgIA0KcXVlc3Rpb24sIHdoaWNoIHJlbGF0ZXMgdG8gc29tZSBvZiB0aGUgY29tbWVudHMgSSBt
YWRlIGluIEZFQ0ZSQU1FICANCmxhc3Qgd2VlaywgaXMgaWYgdGhlIHNlbWFudGljcyBvZiBhbiBS
VFAgRkVDIHN0cmVhbSBwcm90ZWN0aW5nIHNldmVyYWwgIA0KbWVkaWEgc3RyZWFtcyB3aXRoIGRp
ZmZlcmVudCB0b3AtbGV2ZWwgbWVkaWEgdHlwZXMgKGUuZy4gYSBzaW5nbGUgRkVDICANCmZsb3cg
cHJvdGVjdGluZyBib3RoIGF1ZGlvIGFuZCB2aWRlbykgYXJlIHdlbGwgZGVmaW5lZD8gSXQgbWln
aHQgYmUgIA0Kd29ydGggYWRkaW5nIHNvbWUgd29yZGluZyB0byBleHBsYWluIHRoYXQgdGhlIHNp
Z25hbGxpbmcgb2ZmZXJzICANCmZsZXhpYmlsaXR5IGFib3V0IHdoaWNoIGZsb3dzIGNhbiBiZSBn
cm91cGVkLCBidXQgdGhhdCBub3QgYWxsIEZFQyAgDQpzY2hlbWVzIHN1cHBvcnQgdGhlIGZ1bGwg
cmFuZ2Ugb2Ygc2NlbmFyaW9zIHRoYXQgY2FuIGJlIHNpZ25hbGxlZC4NCg0KQ2hlZXJzLA0KQ29s
aW4NCg0KDQoNCk9uIDEwIEp1bCAyMDA5LCBhdCAxODoyMywgQWxpIEMuIEJlZ2VuIChhYmVnZW4p
IHdyb3RlOg0KPiBJIHdvdWxkIGFwcHJlY2lhdGUgaWYgeW91IGNvdWxkIHJldmlldyB0aGlzIGRv
YyBhbmQgcG9zdCB5b3VyICANCj4gY29tbWVudHMgdG8gbW11c2ljLg0KPg0KPiBUaGFua3MuDQo+
IC1hY2JlZ2VuDQo+DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGZlY2Zy
YW1lLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpmZWNmcmFtZS1ib3VuY2VzQGlldGYub3JnXSAg
DQo+IE9uIEJlaGFsZiBPZiBBbGkgQy4gQmVnZW4gKGFiZWdlbikNCj4gU2VudDogVHVlc2RheSwg
SnVseSAwNywgMjAwOSA0OjQ2IFBNDQo+IFRvOiBmZWNmcmFtZUBpZXRmLm9yZw0KPiBTdWJqZWN0
OiBbRmVjZnJhbWVdIEZ3OiBXR0xDIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLSANCj4g
cmZjNDc1NmJpcy0wMg0KPg0KPiBUaGlzIHNob3J0IGRyYWZ0IG5lZWRzIHRvIGJlIHJldmlld2Vk
LiBBbnkgdm9sdW50ZWVycz8gVGhhbmtzLg0KPg0KPiAtYWNiZWdlbg0KPg0KPiAtLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tDQo+IEZyb206IEplYW4tRnJhbmNvaXMgTXVsZSA8amYubXVsZUBD
YWJsZUxhYnMuY29tPg0KPiBUbzogQWxpIEMuIEJlZ2VuIChhYmVnZW4pOyBtbXVzaWNAaWV0Zi5v
cmcgPG1tdXNpY0BpZXRmLm9yZz47IEpvZXJnICANCj4gT3R0IDxqb0BuZXRsYWIudGtrLmZpPg0K
PiBTZW50OiBNb24gSnVsIDA2IDA3OjM4OjA4IDIwMDkNCj4gU3ViamVjdDogUkU6IFdHTEMgcmVx
dWVzdCBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtcmZjNDc1NmJpcy0wMg0KPg0KPiBBbGksDQo+DQo+
ICBPaywgbm90ZWQsIHdpbGwgc2VuZCBhIHNlcGFyYXRlIFdHTEMgYW5ub3VuY2VtZW50Lg0KPg0K
PiAgV2UgaGF2ZSBhdCBsZWFzdCAzIGRyYWZ0cyB0aGF0IG5lZWQgdG8gZ28gdGhyb3VnaCBXR0xD
IGJ1dCBnaXZlbiB0aGUNCj4gRkVDZnJhbWUgZGVwZW5kZW5jeSwgd2UnbGwgZXhwZWRpdGUgdGhp
cyBvbmUuICBDYW4geW91IHBpbmcgb25lIG9yIHR3bw0KPiBmb2xrcyBpbnZvbHZlZCBpbiBmZWNm
cmFtZSB0aGF0IHdvdWxkIGJlIHdpbGxpbmcgdG8gZm9ybWFsbHkgcmV2aWV3ICANCj4gdGhlDQo+
IGRvYyBkdXJpbmcgV0dMQz8NCj4NCj4gSmVhbi1GcmFuY29pcw0KPg0KPj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IEFsaSBDLiBCZWdlbiAoYWJlZ2VuKSBbbWFpbHRvOmFi
ZWdlbkBjaXNjby5jb21dDQo+PiBTZW50OiBNb25kYXksIEp1bHkgMDYsIDIwMDkgNzo1MiBBTQ0K
Pj4gVG86IG1tdXNpY0BpZXRmLm9yZzsgSm9lcmcgT3R0OyBKZWFuLUZyYW5jb2lzIE11bGUNCj4+
IFN1YmplY3Q6IFdHTEMgcmVxdWVzdCBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtcmZjNDc1NmJpcy0w
Mg0KPj4NCj4+IEhlbGxvLA0KPj4NCj4+IEkgd291bGQgbGlrZSB0byByZXF1ZXN0IFdHTEMgZm9y
IHRoZSBmb2xsb3dpbmcgZHJhZnQ6DQo+PiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2YmlzLQ0KPj4gMDIudHh0DQo+Pg0KPj4gVGhp
cyBkcmFmdCBpcyBkZXBlbmRhbnQgb24gdGhlIHNvdXJjZS1zcGVjaWZpYyBtZWRpYSBhdHRyaWJ1
dGVzIGluDQo+PiBTRFAsIHdoaWNoIHJlY2VudGx5IGJlY2FtZSBhbiBSRkMgKDU1NzYpIGFuZCB0
aGUgY3VycmVudCB2ZXJzaW9uDQo+PiBhZGRyZXNzZWQgYWxsIHRoZSBvdXRzdGFuZGluZyBpc3N1
ZXMuIFRoaXMgZHJhZnQgaXMgbmVlZGVkIGJ5IHRoZQ0KPj4gRkVDZnJhbWUgV0cuDQo+Pg0KPj4g
VGhhbmtzLg0KPj4gLWFjYmVnZW4NCj4NCj4NCg0KDQoNCi0tIA0KQ29saW4gUGVya2lucw0KaHR0
cDovL2NzcGVya2lucy5vcmcvDQoNCg0KDQo=

------_=_NextPart_001_01CA1432.17F502EC
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTQuMTIiPg0KPFRJVExFPlJlOiBbRmVjZnJh
bWVdIEZ3OiBXR0xDIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ3NTZiaXMtMDI8
L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+DQo8IS0tIENvbnZlcnRlZCBmcm9tIHRleHQvcGxhaW4g
Zm9ybWF0IC0tPg0KDQo8UD48Rk9OVCBTSVpFPTI+VGhhbmtzIGZvciB0aGUgcmV2aWV3LiBZb3Vy
IGNvbW1lbnQgaXMgcmlnaHQgdG8gdGhlIHBvaW50IGFuZCBJIHdpbGwgYWRkIHRoYXQgd2l0aCAo
YW55KSBvdGhlciBjb21tZW50cyBJIGhvcGUgdG8gcmVjZWl2ZS48QlI+DQo8QlI+DQotYWNiZWdl
bjxCUj4NCjxCUj4NCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS08QlI+DQpGcm9tOiBDb2xp
biBQZXJraW5zICZsdDtjc3BAY3NwZXJraW5zLm9yZyZndDs8QlI+DQpUbzogQWxpIEMuIEJlZ2Vu
IChhYmVnZW4pPEJSPg0KQ2M6IG1tdXNpYyBXRyAmbHQ7bW11c2ljQGlldGYub3JnJmd0OzxCUj4N
ClNlbnQ6IE1vbiBBdWcgMDMgMDQ6NDQ6MjkgMjAwOTxCUj4NClN1YmplY3Q6IFJlOiBbRmVjZnJh
bWVdIEZ3OiBXR0xDIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ3NTZiaXMtMDI8
QlI+DQo8QlI+DQpBbGksPEJSPg0KPEJSPg0KSSd2ZSByZXZpZXdlZCB0aGlzIGRyYWZ0LCBhbmQg
dGhlIFNEUCBleHRlbnNpb25zIGxvb2sgZmluZSB0byBtZS4gTXkmbmJzcDs8QlI+DQpxdWVzdGlv
biwgd2hpY2ggcmVsYXRlcyB0byBzb21lIG9mIHRoZSBjb21tZW50cyBJIG1hZGUgaW4gRkVDRlJB
TUUmbmJzcDs8QlI+DQpsYXN0IHdlZWssIGlzIGlmIHRoZSBzZW1hbnRpY3Mgb2YgYW4gUlRQIEZF
QyBzdHJlYW0gcHJvdGVjdGluZyBzZXZlcmFsJm5ic3A7PEJSPg0KbWVkaWEgc3RyZWFtcyB3aXRo
IGRpZmZlcmVudCB0b3AtbGV2ZWwgbWVkaWEgdHlwZXMgKGUuZy4gYSBzaW5nbGUgRkVDJm5ic3A7
PEJSPg0KZmxvdyBwcm90ZWN0aW5nIGJvdGggYXVkaW8gYW5kIHZpZGVvKSBhcmUgd2VsbCBkZWZp
bmVkPyBJdCBtaWdodCBiZSZuYnNwOzxCUj4NCndvcnRoIGFkZGluZyBzb21lIHdvcmRpbmcgdG8g
ZXhwbGFpbiB0aGF0IHRoZSBzaWduYWxsaW5nIG9mZmVycyZuYnNwOzxCUj4NCmZsZXhpYmlsaXR5
IGFib3V0IHdoaWNoIGZsb3dzIGNhbiBiZSBncm91cGVkLCBidXQgdGhhdCBub3QgYWxsIEZFQyZu
YnNwOzxCUj4NCnNjaGVtZXMgc3VwcG9ydCB0aGUgZnVsbCByYW5nZSBvZiBzY2VuYXJpb3MgdGhh
dCBjYW4gYmUgc2lnbmFsbGVkLjxCUj4NCjxCUj4NCkNoZWVycyw8QlI+DQpDb2xpbjxCUj4NCjxC
Uj4NCjxCUj4NCjxCUj4NCk9uIDEwIEp1bCAyMDA5LCBhdCAxODoyMywgQWxpIEMuIEJlZ2VuIChh
YmVnZW4pIHdyb3RlOjxCUj4NCiZndDsgSSB3b3VsZCBhcHByZWNpYXRlIGlmIHlvdSBjb3VsZCBy
ZXZpZXcgdGhpcyBkb2MgYW5kIHBvc3QgeW91ciZuYnNwOzxCUj4NCiZndDsgY29tbWVudHMgdG8g
bW11c2ljLjxCUj4NCiZndDs8QlI+DQomZ3Q7IFRoYW5rcy48QlI+DQomZ3Q7IC1hY2JlZ2VuPEJS
Pg0KJmd0OzxCUj4NCiZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08QlI+DQomZ3Q7IEZy
b206IGZlY2ZyYW1lLWJvdW5jZXNAaWV0Zi5vcmcgWzxBIEhSRUY9Im1haWx0bzpmZWNmcmFtZS1i
b3VuY2VzQGlldGYub3JnIj5tYWlsdG86ZmVjZnJhbWUtYm91bmNlc0BpZXRmLm9yZzwvQT5dJm5i
c3A7PEJSPg0KJmd0OyBPbiBCZWhhbGYgT2YgQWxpIEMuIEJlZ2VuIChhYmVnZW4pPEJSPg0KJmd0
OyBTZW50OiBUdWVzZGF5LCBKdWx5IDA3LCAyMDA5IDQ6NDYgUE08QlI+DQomZ3Q7IFRvOiBmZWNm
cmFtZUBpZXRmLm9yZzxCUj4NCiZndDsgU3ViamVjdDogW0ZlY2ZyYW1lXSBGdzogV0dMQyByZXF1
ZXN0IGZvciBkcmFmdC1pZXRmLW1tdXNpYy08QlI+DQomZ3Q7IHJmYzQ3NTZiaXMtMDI8QlI+DQom
Z3Q7PEJSPg0KJmd0OyBUaGlzIHNob3J0IGRyYWZ0IG5lZWRzIHRvIGJlIHJldmlld2VkLiBBbnkg
dm9sdW50ZWVycz8gVGhhbmtzLjxCUj4NCiZndDs8QlI+DQomZ3Q7IC1hY2JlZ2VuPEJSPg0KJmd0
OzxCUj4NCiZndDsgLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLTxCUj4NCiZndDsgRnJvbTog
SmVhbi1GcmFuY29pcyBNdWxlICZsdDtqZi5tdWxlQENhYmxlTGFicy5jb20mZ3Q7PEJSPg0KJmd0
OyBUbzogQWxpIEMuIEJlZ2VuIChhYmVnZW4pOyBtbXVzaWNAaWV0Zi5vcmcgJmx0O21tdXNpY0Bp
ZXRmLm9yZyZndDs7IEpvZXJnJm5ic3A7PEJSPg0KJmd0OyBPdHQgJmx0O2pvQG5ldGxhYi50a2su
ZmkmZ3Q7PEJSPg0KJmd0OyBTZW50OiBNb24gSnVsIDA2IDA3OjM4OjA4IDIwMDk8QlI+DQomZ3Q7
IFN1YmplY3Q6IFJFOiBXR0xDIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ3NTZi
aXMtMDI8QlI+DQomZ3Q7PEJSPg0KJmd0OyBBbGksPEJSPg0KJmd0OzxCUj4NCiZndDsmbmJzcDsg
T2ssIG5vdGVkLCB3aWxsIHNlbmQgYSBzZXBhcmF0ZSBXR0xDIGFubm91bmNlbWVudC48QlI+DQom
Z3Q7PEJSPg0KJmd0OyZuYnNwOyBXZSBoYXZlIGF0IGxlYXN0IDMgZHJhZnRzIHRoYXQgbmVlZCB0
byBnbyB0aHJvdWdoIFdHTEMgYnV0IGdpdmVuIHRoZTxCUj4NCiZndDsgRkVDZnJhbWUgZGVwZW5k
ZW5jeSwgd2UnbGwgZXhwZWRpdGUgdGhpcyBvbmUuJm5ic3A7IENhbiB5b3UgcGluZyBvbmUgb3Ig
dHdvPEJSPg0KJmd0OyBmb2xrcyBpbnZvbHZlZCBpbiBmZWNmcmFtZSB0aGF0IHdvdWxkIGJlIHdp
bGxpbmcgdG8gZm9ybWFsbHkgcmV2aWV3Jm5ic3A7PEJSPg0KJmd0OyB0aGU8QlI+DQomZ3Q7IGRv
YyBkdXJpbmcgV0dMQz88QlI+DQomZ3Q7PEJSPg0KJmd0OyBKZWFuLUZyYW5jb2lzPEJSPg0KJmd0
OzxCUj4NCiZndDsmZ3Q7IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPEJSPg0KJmd0OyZndDsg
RnJvbTogQWxpIEMuIEJlZ2VuIChhYmVnZW4pIFs8QSBIUkVGPSJtYWlsdG86YWJlZ2VuQGNpc2Nv
LmNvbSI+bWFpbHRvOmFiZWdlbkBjaXNjby5jb208L0E+XTxCUj4NCiZndDsmZ3Q7IFNlbnQ6IE1v
bmRheSwgSnVseSAwNiwgMjAwOSA3OjUyIEFNPEJSPg0KJmd0OyZndDsgVG86IG1tdXNpY0BpZXRm
Lm9yZzsgSm9lcmcgT3R0OyBKZWFuLUZyYW5jb2lzIE11bGU8QlI+DQomZ3Q7Jmd0OyBTdWJqZWN0
OiBXR0xDIHJlcXVlc3QgZm9yIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ3NTZiaXMtMDI8QlI+DQom
Z3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IEhlbGxvLDxCUj4NCiZndDsmZ3Q7PEJSPg0KJmd0OyZndDsg
SSB3b3VsZCBsaWtlIHRvIHJlcXVlc3QgV0dMQyBmb3IgdGhlIGZvbGxvd2luZyBkcmFmdDo8QlI+
DQomZ3Q7Jmd0OyA8QSBIUkVGPSJodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2YmlzLSI+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtaWV0Zi1tbXVzaWMtcmZjNDc1NmJpcy08L0E+PEJSPg0KJmd0OyZndDsg
MDIudHh0PEJSPg0KJmd0OyZndDs8QlI+DQomZ3Q7Jmd0OyBUaGlzIGRyYWZ0IGlzIGRlcGVuZGFu
dCBvbiB0aGUgc291cmNlLXNwZWNpZmljIG1lZGlhIGF0dHJpYnV0ZXMgaW48QlI+DQomZ3Q7Jmd0
OyBTRFAsIHdoaWNoIHJlY2VudGx5IGJlY2FtZSBhbiBSRkMgKDU1NzYpIGFuZCB0aGUgY3VycmVu
dCB2ZXJzaW9uPEJSPg0KJmd0OyZndDsgYWRkcmVzc2VkIGFsbCB0aGUgb3V0c3RhbmRpbmcgaXNz
dWVzLiBUaGlzIGRyYWZ0IGlzIG5lZWRlZCBieSB0aGU8QlI+DQomZ3Q7Jmd0OyBGRUNmcmFtZSBX
Ry48QlI+DQomZ3Q7Jmd0OzxCUj4NCiZndDsmZ3Q7IFRoYW5rcy48QlI+DQomZ3Q7Jmd0OyAtYWNi
ZWdlbjxCUj4NCiZndDs8QlI+DQomZ3Q7PEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KLS08QlI+DQpD
b2xpbiBQZXJraW5zPEJSPg0KPEEgSFJFRj0iaHR0cDovL2NzcGVya2lucy5vcmcvIj5odHRwOi8v
Y3NwZXJraW5zLm9yZy88L0E+PEJSPg0KPEJSPg0KPEJSPg0KPEJSPg0KPC9GT05UPg0KPC9QPg0K
DQo8L0JPRFk+DQo8L0hUTUw+

------_=_NextPart_001_01CA1432.17F502EC--

From Albrecht.Schwarz@alcatel-lucent.de  Mon Aug  3 05:03:15 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56F683A6D63 for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 05:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.582
X-Spam-Level: 
X-Spam-Status: No, score=-5.582 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXU6zTVr4sES for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 05:03:14 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 12F9F3A6BEE for <mmusic@ietf.org>; Mon,  3 Aug 2009 05:03:13 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n73C2hXg023468;  Mon, 3 Aug 2009 14:03:14 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Aug 2009 14:03:13 +0200
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
Date: Mon, 3 Aug 2009 14:03:12 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B0021C7F3A@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <1249061213.3819.38.camel@victoria-pingtel-com.us.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] Example correct? (draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt); RE:  Revised SDPO/A; RE:  codec negotiation
Thread-Index: AcoSBB50aikTtbXzRluKoPyZHJMIdgCLNXeg
References: <4A5C1D70.1010702@evaristesys.com> <95E7FD6C1C61F640B8A25C8ED11B17C8081086CB@HSP03.SLAN.LK> <001601ca0446$69e83d50$6c4d220a@rildelhi.com> <95E7FD6C1C61F640B8A25C8ED11B17C80810876C@HSP03.SLAN.LK> <F4562D4585113D42AC08DC47FDEC49B0020D30FE@FRVELSMBS23.ad2.ad.alcatel.com> <F4562D4585113D42AC08DC47FDEC49B0021C7CF4@FRVELSMBS23.ad2.ad.alcatel.com> <1249061213.3819.38.camel@victoria-pingtel-com.us.nortel.com>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Dale Worley" <dworley@nortel.com>
X-OriginalArrivalTime: 03 Aug 2009 12:03:13.0986 (UTC) FILETIME=[60E28A20:01CA1432]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>, sip-implementors@lists.cs.columbia.edu
Subject: Re: [MMUSIC] [Sip-implementors] Example correct? (draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt); RE:  Revised SDPO/A; RE:  codec negotiation
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 12:03:15 -0000

Right, the draft is very initial, the crucial part is just the SDP =
example only.
As soon as we got agreement that the SDP syntax is correct and inline =
with SDPCapNeg and SDPMediaNeg, we'll polish the text and update scope, =
abstract etc.

The challenge with the codec negotiation example here is the fact that =
we got
a) mono-media vs dual-media configurations (VoIP vs VoIP+FoIP), and
b) consecutive media-formats on a single RTP session (VoIP - VBDoIP).

That's the interesting part from offer/answer perspective, which may be =
solved in an elegant manner by the revised SDP O/A syntax in our =
understanding.

[Know-ledge about T.38 & V.152 is not required from O/A perspective. =
That's just the references which defining part of the SDP syntax for =
that media formats.]
=20
Albrecht

> -----Original Message-----
> From: Dale Worley [mailto:dworley@nortel.com]=20
> Sent: Freitag, 31. Juli 2009 19:27
> To: Schwarz Albrecht
> Cc: sip-implementors@lists.cs.columbia.edu; mmusic (E-mail)
> Subject: Re: [Sip-implementors] Example=20
> correct?(draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt
> ); RE: Revised SDPO/A; RE: codec negotiation
>=20
> On Fri, 2009-07-31 at 15:23 +0200, Schwarz Albrecht wrote:
> >=20
> http://www.ietf.org/internet-drafts/draft-schwarz-mmusic-sdp-offer-ans
> > wer-examples-00.txt
> >=20
> > Dear SDP Offer/Answer experts!
> >=20
> > Our draft provides an example in =A7 4.4.1.3, using the new=20
> SDP syntax=20
> > according revised SDP O/A:
> > "SDP Capability Negotiation",
> > draft-ietf-mmusic-sdp-capability-negotiation
> > "SDP media capabilities Negotiation",
> > draft-ietf-mmusic-sdp-media-capabilities
> >=20
> > Before progressing our draft we would appreciate any feedback,=20
> > comments by the SDP O/A experts.
>=20
> The Abstract isn't very clear.  The Abstract just describes=20
> the draft as providing offer/answer examples.  But I think=20
> that the draft is trying to give examples specifically for=20
> V.152 and T.38, and it seems that=20
> draft-ietf-mmusic-sdp-capability-negotiation and=20
> draft-ietf-mmusic-sdp-media-capabilities are essential to=20
> handling those situations well.  If that is so, the Abstract=20
> should make it clear.
> Otherwise, people won't realize why they want to read the I-D/RFC.
>=20
> Dale
>=20
>=20
>=20

From Albrecht.Schwarz@alcatel-lucent.de  Mon Aug  3 23:36:03 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E625B3A6F61 for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 23:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.749
X-Spam-Level: 
X-Spam-Status: No, score=-5.749 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6X7PEMUXfRh4 for <mmusic@core3.amsl.com>; Mon,  3 Aug 2009 23:36:03 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id CD7993A6F5C for <mmusic@ietf.org>; Mon,  3 Aug 2009 23:36:02 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n746Zxcq027138;  Tue, 4 Aug 2009 08:36:03 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 4 Aug 2009 08:35:00 +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
Date: Tue, 4 Aug 2009 08:34:59 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B0021C80C6@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <1249315787.3791.16.camel@victoria-pingtel-com.us.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip-implementors] Example correct?(draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt); RE:  RevisedSDPO/A; RE:  codec negotiation
Thread-Index: AcoUVNcTZ8IdNlBhSMe63fz6jxNIlAAd0hcQ
References: <4A5C1D70.1010702@evaristesys.com> <95E7FD6C1C61F640B8A25C8ED11B17C8081086CB@HSP03.SLAN.LK> <001601ca0446$69e83d50$6c4d220a@rildelhi.com> <95E7FD6C1C61F640B8A25C8ED11B17C80810876C@HSP03.SLAN.LK> <F4562D4585113D42AC08DC47FDEC49B0020D30FE@FRVELSMBS23.ad2.ad.alcatel.com> <F4562D4585113D42AC08DC47FDEC49B0021C7CF4@FRVELSMBS23.ad2.ad.alcatel.com> <1249061213.3819.38.camel@victoria-pingtel-com.us.nortel.com> <F4562D4585113D42AC08DC47FDEC49B0021C7F3A@FRVELSMBS23.ad2.ad.alcatel.com> <1249315787.3791.16.camel@victoria-pingtel-com.us.nortel.com>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Dale Worley" <dworley@nortel.com>, "mmusic (E-mail)" <mmusic@ietf.org>
X-OriginalArrivalTime: 04 Aug 2009 06:35:00.0174 (UTC) FILETIME=[B0DF0EE0:01CA14CD]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: sip-implementors <sip-implementors@lists.cs.columbia.edu>
Subject: Re: [MMUSIC] [Sip-implementors] Example correct?(draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt); RE:  RevisedSDPO/A; RE:  codec negotiation
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 06:36:04 -0000

The request was addressed to MMUSIC (and for info for SIP implementors).
MMUSIC developed the revised SDP O/A protocol AFAIK:
http://tools.ietf.org/wg/mmusic/draft-ietf-mmusic-sdp-capability-negotia
tion/
http://tools.ietf.org/wg/mmusic/draft-ietf-mmusic-sdp-media-capabilities
/

Any SDP experts in MMUSIC, familiar with that SDP extensions?
If yes, please have a look at just the SDP Offer of the example.
http://www.ietf.org/internet-drafts/draft-schwarz-mmusic-sdp-offer-answe
r-examples-00.txt
You may focus on the syntax first (Table x1) ...

Albrecht

PS
If the format as a 'draft' is an issue, then we may put just the 80 SDP
lines of the SDP Offer in an email.


> -----Original Message-----
> From: Dale Worley [mailto:dworley@nortel.com]=20
> Sent: Montag, 3. August 2009 18:10
> To: Schwarz Albrecht
> Cc: sip-implementors
> Subject: RE: [Sip-implementors] Example=20
> correct?(draft-schwarz-mmusic-sdp-offer-answer-examples-00.txt
> ); RE: RevisedSDPO/A; RE: codec negotiation
>=20
> On Mon, 2009-08-03 at 14:03 +0200, Schwarz Albrecht wrote:
> > Right, the draft is very initial, the crucial part is just the SDP=20
> > example only.
> > As soon as we got agreement that the SDP syntax is correct=20
> and inline=20
> > with SDPCapNeg and SDPMediaNeg, we'll polish the text and update=20
> > scope, abstract etc.
>=20
> It is extremely hard to determine if a particular SDP example=20
> is correct if one does not have a clear description of what=20
> the SDP is attempting to accomplish.  That is why you want to=20
> update the abstract and descriptive text before bringing the=20
> question to a general mailing list like SIP-Implementors. =20
> After all, most of your readers here don't know what=20
> "SDPCapNeg", "SDPMediaNeg", T.38, and V.152 are, nor have=20
> they thought about the usage scenarios that the SDP is=20
> intended to support.
>=20
> Dale
>=20
>=20
>=20

From veera.andersson@ericsson.com  Tue Aug  4 02:54:40 2009
Return-Path: <veera.andersson@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1795F28C2E4 for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 02:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[AWL=1.140,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-haBkO5A69a for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 02:54:39 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 7D72A28C32A for <mmusic@ietf.org>; Tue,  4 Aug 2009 02:54:07 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b53ae000004f0b-d9-4a780539dfd7
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 64.91.20235.935087A4; Tue,  4 Aug 2009 11:54:01 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 4 Aug 2009 11:53:02 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 4 Aug 2009 11:53:02 +0200
Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 031A32450; Tue,  4 Aug 2009 12:53:01 +0300 (EEST)
Message-ID: <4A7804FD.9080909@ericsson.com>
Date: Tue, 04 Aug 2009 12:53:01 +0300
From: Veera Andersson <veera.andersson@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: jdrosen@cisco.com
References: <4A683D35.6000207@ericsson.com>
In-Reply-To: <4A683D35.6000207@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Aug 2009 09:53:02.0548 (UTC) FILETIME=[5B517140:01CA14E9]
X-Brightmail-Tracker: AAAAAA==
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Issue with ICE controlling/controlled tie-breaker
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 09:54:40 -0000

Hi,

Actually the described case is taken care of by the error response code.


Regards,
Veera


Veera Andersson wrote:
> Hi,
> 
> I have a question concerning ICE that came up while implementing an ICE 
> prototype. I think it is possible for two agents to end up with 
> different selected pairs if both agents are initially in controlling 
> role. I mean, regardless of having detecting and repairing of role 
> conflicts implemented.
> 
> This could happen in a situation where it takes a long time for an ICE 
> answer, from the agent with a lower tie-breaker value, to the initial 
> ICE offer to arrive. For the peer (with lower tie-breaker) to realize to 
> change its role, it needs to receive a Binding request (with 
> ICE-CONTROLLING attribute) from the other endpoint. But this might not 
> happen in time, since the agent with the higher tie-breaker value is 
> still waiting for the answer to its initial ICE offer to arrive in order 
> to start Binding requests. Mean while, it is responding to requests it 
> receives.
> 
> In such a case, the agent with the lower tie-breaker value might already 
> nominate some pair before the other endpoint has started its checks. 
> When the endpoint with higher tie-breaker finally starts checks, it may 
> (and is likely to) end up nominating another pair since it doesn't 
> accept nomination from the lower tie-breaker peer.
> 
> Is this perhaps a feature of the specification or is there some other 
> mechanism that covers this case?
> 
> In case there is not, at least adding the controlling/controlled 
> attribute also to the Binding response messages would solve the problem.
> 
> 
> Regards,
> Veera
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From Jose.Rey@eu.panasonic.com  Tue Aug  4 07:55:29 2009
Return-Path: <Jose.Rey@eu.panasonic.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAE953A6BCF for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 07:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8i0EuKLkb53L for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 07:55:29 -0700 (PDT)
Received: from cluster-a.mailcontrol.com (cluster-a.mailcontrol.com [85.115.52.190]) by core3.amsl.com (Postfix) with ESMTP id E9C383A6A89 for <mmusic@ietf.org>; Tue,  4 Aug 2009 07:55:28 -0700 (PDT)
Received: from eundsmtpout02.pan.eu ([168.87.60.204]) by rly11a.srv.mailcontrol.com (MailControl) with ESMTP id n74EtIFX022624 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <mmusic@ietf.org>; Tue, 4 Aug 2009 15:55:19 +0100
Received: from eundadmi02.pan.eu ([10.109.33.23]) by eundsmtpout02.pan.eu (Lotus Domino Release 7.0.2) with ESMTP id 2009080416550999-62023 ; Tue, 4 Aug 2009 16:55:09 +0200 
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55]) by eundadmi02.pan.eu (Lotus Domino Release 7.0.3) with ESMTP id 2009080416550925-186730 ; Tue, 4 Aug 2009 16:55:09 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de for mmusic@ietf.org; Tue, 4 Aug 2009 16:54:09 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: GET_PARAMETER for keep-alive in RTSP 2.0?
Thread-Index: AcoVE3MI16aY0FzWSu6aleBw9KulXA==
To: <mmusic@ietf.org>
X-TNEFEvaluated: 1
Message-ID: <1FEB9B9F2EC38343955D02B2AE86AACB0133308C@lan-ex-02.panasonic.de>
Date: Tue, 4 Aug 2009 16:54:21 +0200
From: "Jose Rey" <Jose.Rey@eu.panasonic.com>
X-MIMETrack: Itemize by SMTP Server on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 04.08.2009 16:55:09, Serialize by Router on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 04.08.2009 16:55:10, Serialize complete at 04.08.2009 16:55:10, Itemize by SMTP Server on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 08/04/2009 04:55:09 PM, Serialize by Router on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 08/04/2009 04:55:19 PM, Serialize complete at 08/04/2009 04:55:19 PM
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Content-Type: text/plain; charset="iso-8859-1"
X-Scanned-By: MailControl A-09-20-00 (www.mailcontrol.com) on 10.65.0.121
Subject: [MMUSIC] GET_PARAMETER for keep-alive in RTSP 2.0?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 14:55:30 -0000

Hi all,

Is there any reason why GET_PARAMETER is not mentioned in "10.5. Showing =
Liveness" as mechanism for keep-alive? The description of the method =
itself would suggest it should go between SET_PARAMETER and OPTIONS.

Thanks,

Jos=E9


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



From Remi.Denis-Courmont@nokia.com  Tue Aug  4 08:02:37 2009
Return-Path: <Remi.Denis-Courmont@nokia.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0F5628C35D for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 08:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.217
X-Spam-Level: 
X-Spam-Status: No, score=-6.217 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTvJy2kdPdxT for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 08:02:36 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 12B303A6BCF for <mmusic@ietf.org>; Tue,  4 Aug 2009 08:02:36 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n74F1wOq019341; Tue, 4 Aug 2009 10:02:13 -0500
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 4 Aug 2009 18:02:15 +0300
Received: from mgw-sa02.ext.nokia.com ([147.243.1.48]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 4 Aug 2009 18:02:12 +0300
Received: from leon.remlab.net (esdhcp035210.research.nokia.com [172.21.35.210]) by mgw-sa02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n74F2Acf031755; Tue, 4 Aug 2009 18:02:11 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Devices - Nokia
To: mmusic@ietf.org
Date: Tue, 4 Aug 2009 18:02:10 +0300
User-Agent: KMail/1.11.2 (Linux/2.6.29.6; KDE/4.2.2; i686; ; )
References: <1FEB9B9F2EC38343955D02B2AE86AACB0133308C@lan-ex-02.panasonic.de>
In-Reply-To: <1FEB9B9F2EC38343955D02B2AE86AACB0133308C@lan-ex-02.panasonic.de>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200908041802.10341.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 04 Aug 2009 15:02:12.0356 (UTC) FILETIME=[8BDD8440:01CA1514]
X-Nokia-AV: Clean
Cc: ext Jose Rey <Jose.Rey@eu.panasonic.com>
Subject: Re: [MMUSIC] GET_PARAMETER for keep-alive in RTSP 2.0?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 15:02:37 -0000

On Tuesday 04 August 2009 17:54:21 ext Jose Rey wrote:
> Hi all,
>
> Is there any reason why GET_PARAMETER is not mentioned in "10.5. Showing
> Liveness" as mechanism for keep-alive? The description of the method itse=
lf
> would suggest it should go between SET_PARAMETER and OPTIONS.

The problem is, there are no standardized actual GET_PARAMETER request=20
parameter, so the rely cannot rely on this... (I do agree that this is the=
=20
most common method in existing RTSP/1.0 deployment)

=2D-=20
R=E9mi Denis-Courmont
Nokia Devices R&D, Maemo Software, Helsinki


From Jose.Rey@eu.panasonic.com  Tue Aug  4 08:08:15 2009
Return-Path: <Jose.Rey@eu.panasonic.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FB6428C253 for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 08:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.208
X-Spam-Level: 
X-Spam-Status: No, score=-3.208 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WG1thXTWQ2Yr for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 08:08:14 -0700 (PDT)
Received: from cluster-j.mailcontrol.com (cluster-j.mailcontrol.com [85.115.54.190]) by core3.amsl.com (Postfix) with ESMTP id A8F163A7067 for <mmusic@ietf.org>; Tue,  4 Aug 2009 08:08:14 -0700 (PDT)
Received: from rly41j.srv.mailcontrol.com (localhost.localdomain [127.0.0.1]) by rly41j.srv.mailcontrol.com (MailControl) with ESMTP id n74F7Zjr008576 for <mmusic@ietf.org>; Tue, 4 Aug 2009 16:07:55 +0100
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by rly41j.srv.mailcontrol.com (MailControl) id n74F6bRM002964 for <mmusic@ietf.org>; Tue, 4 Aug 2009 16:06:37 +0100
Received: from eundsmtpout02.pan.eu ([168.87.60.204]) by rly41j-eth0.srv.mailcontrol.com (envelope-sender <Jose.Rey@eu.panasonic.com>) (MIMEDefang) with ESMTP id n74F6LEc002093; Tue, 04 Aug 2009 16:06:37 +0100 (BST)
Received: from eundadmi02.pan.eu ([10.109.33.23]) by eundsmtpout02.pan.eu (Lotus Domino Release 7.0.2) with ESMTP id 2009080417062066-62123 ; Tue, 4 Aug 2009 17:06:20 +0200 
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55]) by eundadmi02.pan.eu (Lotus Domino Release 7.0.3) with ESMTP id 2009080417061934-187080 ; Tue, 4 Aug 2009 17:06:19 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de; Tue, 4 Aug 2009 17:05:19 +0200
MIME-Version: 1.0
In-Reply-To: <200908041802.10341.remi.denis-courmont@nokia.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] GET_PARAMETER for keep-alive in RTSP 2.0?
Thread-Index: AcoVFIpIdh0A4NAtTL6tLoYY1jzFSQAAEPeg
References: <1FEB9B9F2EC38343955D02B2AE86AACB0133308C@lan-ex-02.panasonic.de> <200908041802.10341.remi.denis-courmont@nokia.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>, <mmusic@ietf.org>
X-TNEFEvaluated: 1
Message-ID: <1FEB9B9F2EC38343955D02B2AE86AACB01333090@lan-ex-02.panasonic.de>
Date: Tue, 4 Aug 2009 17:05:33 +0200
From: "Jose Rey" <Jose.Rey@eu.panasonic.com>
X-MIMETrack: Itemize by SMTP Server on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 04.08.2009 17:06:19, Serialize by Router on EUNDADMI02/EUR/Matsushita(Release 7.0.3|September 26, 2007) at 04.08.2009 17:06:21, Serialize complete at 04.08.2009 17:06:21, Itemize by SMTP Server on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 08/04/2009 05:06:20 PM, Serialize by Router on EUNDSMTPOUT02/EUR/PANEXTOUT(Release 7.0.2|September 26, 2006) at 08/04/2009 05:06:36 PM, Serialize complete at 08/04/2009 05:06:36 PM
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Content-Type: text/plain; charset="iso-8859-1"
X-Scanned-By: MailControl A-09-20-00 (www.mailcontrol.com) on 10.74.1.151
Cc: ext Jose Rey <Jose.Rey@eu.panasonic.com>
Subject: Re: [MMUSIC] GET_PARAMETER for keep-alive in RTSP 2.0?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 15:08:15 -0000

But I don't really need parameters for keep-alive. An empty body is good =
enough...so is that still a problem?=20

> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com]=20
> Sent: Tuesday, August 04, 2009 5:02 PM
> To: mmusic@ietf.org
> Cc: ext Jose Rey
> Subject: Re: [MMUSIC] GET_PARAMETER for keep-alive in RTSP 2.0?
>=20
> On Tuesday 04 August 2009 17:54:21 ext Jose Rey wrote:
> > Hi all,
> >
> > Is there any reason why GET_PARAMETER is not mentioned in "10.5.=20
> > Showing Liveness" as mechanism for keep-alive? The=20
> description of the=20
> > method itself would suggest it should go between=20
> SET_PARAMETER and OPTIONS.
>=20
> The problem is, there are no standardized actual=20
> GET_PARAMETER request parameter, so the rely cannot rely on=20
> this... (I do agree that this is the most common method in=20
> existing RTSP/1.0 deployment)
>=20
> --
> R=E9mi Denis-Courmont
> Nokia Devices R&D, Maemo Software, Helsinki
>=20
>=20
>=20


Panasonic R=26D Center Germany GmbH
63225 Langen=2C Hessen=2C Germany
Reg=3A AG Offenbach =28Hessen=29 HRB 33974
Managing Director=3A Thomas Micke



From singer@apple.com  Tue Aug  4 15:07:19 2009
Return-Path: <singer@apple.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED2823A70C2 for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 15:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.751
X-Spam-Level: 
X-Spam-Status: No, score=-107.751 tagged_above=-999 required=5 tests=[AWL=-2.548, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VoNEhldHZGm for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 15:07:19 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 402D73A6918 for <mmusic@ietf.org>; Tue,  4 Aug 2009 15:07:19 -0700 (PDT)
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out4.apple.com (Postfix) with ESMTP id 38D40703C263; Tue,  4 Aug 2009 15:07:22 -0700 (PDT)
X-AuditID: 11807135-b7b69ae000004d3d-c7-4a78b119a009
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52]) by  (Apple SCV relay) with SMTP id 85.FE.19773.911B87A4; Tue,  4 Aug 2009 15:07:22 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06240801c69e600c7cf4@[17.202.35.52]>
Date: Tue, 4 Aug 2009 15:06:17 -0700
To: mmusic@ietf.org
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Brightmail-Tracker: AAAAAQAAAZE=
Cc: http-live-streaming-review <http-live-streaming-review@group.apple.com>, streaming@videolan.org
Subject: Re: [MMUSIC] Comments on draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 22:07:20 -0000

Hello R=E9mi. Thanks for looking at the draft.

On Aug 2, 2009, at 12:12 PM, R=E9mi Denis-Courmont wrote:
>* I'm not sure I see the point of the EXT-X-ALLOW-CACHE parameter. Does HTT=
P
>not have extensive caching negotiation built-in already?

It does. EXT-X-ALLOW-CACHE is there to allow=20
providers to specify the lifetime of the content=20
on the device independently of its lifetime on=20
the network. Particularly, some media=20
distribution agreements require limited lifetime=20
of the media on the device to distinguish a=20
"broadcast" from a "recording."

>* It is not clear to me whether EXT-X-TARGETDURATION is mandatory or not.

=46rom section 3.1.1 of the draft:

3.1.1.  EXT-X-TARGETDURATION

    The EXT-X-TARGETDURATION tag indicates the approximate duration of
    the next media file that will be added to the main presentation.  It
    MUST appear in the Playlist file.

As specified by RFC 2119, the MUST indicates that=20
the EXT-X-TARGETDURATION tag is mandatory.

>* I don't understand how the receiver (the client) of the playlist can
>_reliably_ distinguish a plain old playlist file from a live streaming file=
=2E
>M3U URLs are already in common use to deliver "real" playlist, and the
>semantics are significantly different from what your draft does. If none of=
the
>new parameters you introduce are mandatory, this protocol is basically
>impossible to implement in a way that does not break existing functionality=
 in
>many media players.

Players can use the presence of the=20
EXT-X-TARGETDURATION tag to determine whether the=20
playlist file follows the rules of the draft.


-- 
David Singer
Multimedia Standards, Apple Inc.

From Remi.Denis-Courmont@nokia.com  Tue Aug  4 23:25:17 2009
Return-Path: <Remi.Denis-Courmont@nokia.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CA2828C4C4 for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 23:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.225
X-Spam-Level: 
X-Spam-Status: No, score=-6.225 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kT1d1d4yPIZs for <mmusic@core3.amsl.com>; Tue,  4 Aug 2009 23:25:16 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 5551028C4AA for <mmusic@ietf.org>; Tue,  4 Aug 2009 23:25:16 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n756NfqO010913; Wed, 5 Aug 2009 09:23:45 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 5 Aug 2009 09:23:43 +0300
Received: from mgw-sa02.ext.nokia.com ([147.243.1.48]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 5 Aug 2009 09:23:42 +0300
Received: from leon.remlab.net (esdhcp034203.research.nokia.com [172.21.34.203]) by mgw-sa02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n756Ne0R002612; Wed, 5 Aug 2009 09:23:40 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Devices - Nokia
To: mmusic@ietf.org
Date: Wed, 5 Aug 2009 09:23:43 +0300
User-Agent: KMail/1.11.2 (Linux/2.6.29.6; KDE/4.2.2; i686; ; )
References: <p06240801c69e600c7cf4@[17.202.35.52]>
In-Reply-To: <p06240801c69e600c7cf4@[17.202.35.52]>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200908050923.44381.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 05 Aug 2009 06:23:42.0910 (UTC) FILETIME=[479A85E0:01CA1595]
X-Nokia-AV: Clean
Cc: http-live-streaming-review <http-live-streaming-review@group.apple.com>, "streaming@videolan.org" <streaming@videolan.org>, ext David Singer <singer@apple.com>
Subject: Re: [MMUSIC] Comments on draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 06:25:17 -0000

On Wednesday 05 August 2009 01:06:17 ext David Singer wrote:
> On Aug 2, 2009, at 12:12 PM, R=E9mi Denis-Courmont wrote:
> >* I'm not sure I see the point of the EXT-X-ALLOW-CACHE parameter. Does
> > HTTP not have extensive caching negotiation built-in already?
>
> It does. EXT-X-ALLOW-CACHE is there to allow
> providers to specify the lifetime of the content
> on the device independently of its lifetime on
> the network. Particularly, some media
> distribution agreements require limited lifetime
> of the media on the device to distinguish a
> "broadcast" from a "recording."

Hmm, ok... Where would timeshifting fit in this?

=2D-=20
R=E9mi Denis-Courmont
Nokia Devices R&D, Maemo Software, Helsinki


From tomhiller@alcatel-lucent.com  Wed Aug  5 12:03:06 2009
Return-Path: <tomhiller@alcatel-lucent.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 851673A6980 for <mmusic@core3.amsl.com>; Wed,  5 Aug 2009 12:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6ZLazH2ZhZt for <mmusic@core3.amsl.com>; Wed,  5 Aug 2009 12:03:05 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id C5A6B3A688B for <mmusic@ietf.org>; Wed,  5 Aug 2009 12:03:05 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n75J37Wl007175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mmusic@ietf.org>; Wed, 5 Aug 2009 14:03:07 -0500 (CDT)
Received: from [135.244.36.253] (tomhille.lra.lucent.com [135.244.36.253]) by umail.lucent.com (8.13.8/TPES) with ESMTP id n75J37Ko003546 for <mmusic@ietf.org>; Wed, 5 Aug 2009 14:03:07 -0500 (CDT)
Message-ID: <4A79D76F.40503@alcatel-lucent.com>
Date: Wed, 05 Aug 2009 14:03:11 -0500
From: Tom Hiller <tomhiller@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: [MMUSIC] "SIP-SDP Overlap with RTSP" and OMA
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 19:03:06 -0000

Hello,

Last week at MMUSIC, the last slide of the presentation "SIP-SDP Overlap 
with RTSP" associated with "draft-lindquist-mmusic-sip-rtsp-00.txt", 
which involves bypassing the RTSP SETUP and DESCRIBE requests, suggests 
that this direction is on-going work in OMA, i.e.,:
 
> Ongoing work in other standard forums (ETSI TISPAN, 3GPP, OIPF, OMA, etc)

However, it is not the case.  In OMA we had discussed using SIP to 
signal the establishment of an RTSP session, bypassing the RTSP SETUP as 
in this draft, and we did not go that direction. Main reasons were that 
we wanted to be compliant with existing RTSP implementations and with 
RTSP 2.0 going forward. 


Thanks.


  - Tom





From singer@apple.com  Wed Aug  5 16:56:26 2009
Return-Path: <singer@apple.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5BEE3A6CAA for <mmusic@core3.amsl.com>; Wed,  5 Aug 2009 16:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.949
X-Spam-Level: 
X-Spam-Status: No, score=-107.949 tagged_above=-999 required=5 tests=[AWL=-1.650, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGR-pUyepm43 for <mmusic@core3.amsl.com>; Wed,  5 Aug 2009 16:56:26 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 67BBF3A71D0 for <mmusic@ietf.org>; Wed,  5 Aug 2009 16:56:25 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 5862B706A31C; Wed,  5 Aug 2009 16:56:28 -0700 (PDT)
X-AuditID: 1180711d-b7c7aae0000053b3-9c-4a7a1c2b7a66
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52]) by relay13.apple.com (Apple SCV relay) with SMTP id EF.C8.21427.B2C1A7A4; Wed,  5 Aug 2009 16:56:28 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0624084ac69fcc193e68@[17.202.35.52]>
In-Reply-To: <200908050923.44381.remi.denis-courmont@nokia.com>
References: <p06240801c69e600c7cf4@[17.202.35.52]> <200908050923.44381.remi.denis-courmont@nokia.com>
Date: Wed, 5 Aug 2009 16:54:46 -0700
To: =?iso-8859-1?Q?R=E9mi_Denis=2DCourmont?=  <remi.denis-courmont@nokia.com>,  mmusic@ietf.org
From: David Singer <singer@apple.com>
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Brightmail-Tracker: AAAAAQAAAZE=
Cc: http-live-streaming-review <http-live-streaming-review@group.apple.com>, "streaming@videolan.org" <streaming@videolan.org>
Subject: Re: [MMUSIC] Comments on draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 23:56:27 -0000

At 9:23  +0300 5/08/09, R=E9mi Denis-Courmont wrote:
>On Wednesday 05 August 2009 01:06:17 ext David Singer wrote:
>>  On Aug 2, 2009, at 12:12 PM, R=E9mi Denis-Courmont wrote:
>>  >* I'm not sure I see the point of the EXT-X-ALLOW-CACHE parameter. Does
>>  > HTTP not have extensive caching negotiation built-in already?
>>
>>  It does. EXT-X-ALLOW-CACHE is there to allow
>>  providers to specify the lifetime of the content
>>  on the device independently of its lifetime on
>>  the network. Particularly, some media
>>  distribution agreements require limited lifetime
>>  of the media on the device to distinguish a
>>  "broadcast" from a "recording."
>
>Hmm, ok... Where would timeshifting fit in this?
>

=46rom a technical point of view, the presence of=20
the EXT-X-ALLOW-CACHE tag with a value of NO=20
would forbid a client from timeshifting.=20
Otherwise a client would be allowed to cache the=20
content for later viewing.

Note that providing a VOD / progressive download=20
link is another way to do timeshifting.

-- 
David Singer
Multimedia Standards, Apple Inc.

From christer.holmberg@ericsson.com  Fri Aug  7 02:52:09 2009
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EB3E3A6A60 for <mmusic@core3.amsl.com>; Fri,  7 Aug 2009 02:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.515
X-Spam-Level: 
X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=-1.266, BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49BpXsYxJZp2 for <mmusic@core3.amsl.com>; Fri,  7 Aug 2009 02:52:08 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 131133A6EBD for <mmusic@ietf.org>; Fri,  7 Aug 2009 02:52:07 -0700 (PDT)
X-AuditID: c1b4fb24-b7c01ae00000498b-56-4a7bf9495835
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw5.ericsson.se (Symantec Brightmail Gateway) with SMTP id 31.E6.18827.949FB7A4; Fri,  7 Aug 2009 11:52:09 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 7 Aug 2009 11:51:47 +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
Date: Fri, 7 Aug 2009 11:51:45 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0B1683D8@esealmw113.eemea.ericsson.se>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC319890C504A@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] A replacement for ANAT
Thread-Index: Acn+Ht6b7BCUGPf8Sx21Vd9MnFbb/wAD2+LAACQixBAADQRQgAAgkgEAAA5LAuAETrbMAAADMw1gAZNMzzA=
References: <08BA2C59E081884DB2AAE4A0BE9D6DC1368EAB@ftrdmel0.rd.francetelecom.fr><E6C2E8958BA59A4FB960963D475F7AC31960080508@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE1366@NOK-EUMSG-01.mgdnok.nokia.com><E6C2E8958BA59A4FB960963D475F7AC31961194B3B@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE193D@NOK-EUMSG-01.mgdnok.nokia.com><4a714f63.02a1660a.40cd.0c70@mx.google.com> <E6C2E8958BA59A4FB960963D475F7AC319890C504A@mail>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>, "Roni Even" <ron.even.tlv@gmail.com>, <Simo.Veikkolainen@nokia.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 07 Aug 2009 09:51:47.0291 (UTC) FILETIME=[ADB362B0:01CA1744]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [MMUSIC] A replacement for ANAT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2009 09:52:09 -0000

Hi,

This is what I said at the mic: we already do "replace" ICE.

However, even with ICE, I think one problem is that it is not very clear
how to use ICE for pure offering-of-alternative-IP-addresses, when you
don't use NAT traversal - or you use another mechanism for NAT
traversal.

Let's take a simple example:

Alice sends an offer, with a single IPv4 and a single IPv6 address,
using ICE candidates. There are no STUN or TURN candidates.

Bob only supports IPv4, so he sends back an IPv4 candidate. Bob doesn't
provide any STUN or TURN candidates either.

Now, is it is possible for Alice and Bob to start using the IPv4
addresses at this point (I guess a new offer may be required to indicate
which candicate was chosen), or are they required (by ICE) to initiate
connectivity checks? What if the checks fail, e.g. due to the usage of
some other NAT traversal mechanism, or because there is no end-to-end
media path yet - which may be the reason that another NAT traversal
mechanism in the first place.

Regards,

Christer
=20

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Hadriel Kaplan
Sent: Thursday, July 30, 2009 12:15 PM
To: Roni Even; Simo.Veikkolainen@nokia.com; mmusic@ietf.org
Subject: Re: [MMUSIC] A replacement for ANAT


I'm confused by this - how does offering different *addresses* in
sdp-cap not "replace" ICE, but offering different ports does replace it?

-hadriel

> -----Original Message-----
> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Thursday, July 30, 2009 3:43 AM
> To: Simo.Veikkolainen@nokia.com; Hadriel Kaplan; mmusic@ietf.org
> Subject: RE: [MMUSIC] A replacement for ANAT
>=20
> Simo,
> The reason for not offering different ports in cap negotiation work is

> to not replace ICE Roni Even
>=20
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

From guyingjie@huawei.com  Mon Aug 10 23:04:48 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E0323A68D4 for <mmusic@core3.amsl.com>; Mon, 10 Aug 2009 23:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.215
X-Spam-Level: 
X-Spam-Status: No, score=0.215 tagged_above=-999 required=5 tests=[AWL=0.399,  BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22iJw0M-thmN for <mmusic@core3.amsl.com>; Mon, 10 Aug 2009 23:04:47 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id D63C53A6EA9 for <mmusic@ietf.org>; Mon, 10 Aug 2009 23:04:19 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO70011C7J9ZN@szxga01-in.huawei.com> for mmusic@ietf.org; Tue, 11 Aug 2009 14:04:22 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO700CN17J9A8@szxga01-in.huawei.com> for mmusic@ietf.org; Tue, 11 Aug 2009 14:04:21 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KO700LX27J9C5@szxml04-in.huawei.com> for mmusic@ietf.org; Tue, 11 Aug 2009 14:04:21 +0800 (CST)
Date: Tue, 11 Aug 2009 14:04:20 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
To: mmusic@ietf.org
Message-id: <001701ca1a49$91bcba40$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_yjj42zFXcNgcfbcqichw+Q)"
Thread-index: AcoaSZFrx3F0JjKoTPW+S2B9sWpzWg==
Subject: [MMUSIC]  Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2009 06:04:48 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_yjj42zFXcNgcfbcqichw+Q)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT

Hi all,
In RTSP 2.0, it is permitted to transmit several client requests in one
Transport Connection. 
I think this may introduce new problems when RTSP proxy is intervened, and
existing RTSP can not deal with the scenario correctly.
The following is an example. To display the figure correctly, please
maximize this email window.
   Suppose that client A and client B wants to join different multicast
groups on the same server.
   +----------+                      +--------------+
+--------+ 
   | Client A |                       | RTSP proxy|
| Server |
   +----------+                      +--------------+
+--------+
        |                                              |
|
        |    +----------+                        |
|
        |    | Client B |                         |
|
        |    +----------+                        |
|
        |         |                                    |
|
        |         |    Setup                       |
| 
        |==================>  |
|
        |         |                                    |
|
        |         |                                    |      Setup
|
        |         |
|====================> |
        |         |                                    |
|  
        |         |    Setup                       |
|
        |         |*****************>|
|
        |         |                                   |      Setup
|
        |         |
|************************> |
        |         |                                   |
|
        |         |                                   |
|
        |         |
|<=====================|
        |         |                                   | 200 OK
(SessionID=12345678)|
        |         |
|<************************ |
        |         |                                   | 200 OK
(SessionID=23456789)| 
        |         |                    ?????????|
|
        |         |                                   |
|
             
                           
                          Fig.2  Multicast 
                                     
 
   The interactive messages are listed as following.
 
   Session issued by Client A:
   C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 111
         Transport: RTP/AVP;multicast
 
   P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 333
         Transport: RTP/AVP;multicast
   Session issued by Client A:
   C->P: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
         CSeq: 222
         Transport: RTP/AVP;multicast
   P->S: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
         CSeq: 444
         Transport: RTP/AVP;multicast
 

   Proxy will receive the following responses from server:
   S->P: RTSP/2.0 200 OK
         CSeq: 333
         Server: PhonyServer/1.0
         Date: Thu, 23 Jan 2009 15:35:06 GMT
         Transport: RTP/AVP;multicast;
              dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16
         Session: 12345678
   S->P: RTSP/2.0 200 OK
         CSeq: 444
         Server: PhonyServer/1.0
         Date: Thu, 23 Jan 2009 15:35:06 GMT
         Transport: RTP/AVP;multicast;
              dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16
         Session: 23456789
 
In this case, RTSP proxy can not distinguish the responses, then it may
respond client with wrong message and induce client to join a wrong
mutlicast group. 
 
Do anybody think this is an possible trap/deficiency, and RTSP should try to
resolve?
Thanks.
 

Regards

Yingjie Gu

 

--Boundary_(ID_yjj42zFXcNgcfbcqichw+Q)
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 content="MSHTML 6.00.2900.3562" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT size=5><SPAN class=772445903-11082009>Hi all,</SPAN></FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>In RTSP 2.0, it is permitted to 
transmit several client requests in one Transport Connection.</SPAN> 
</FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>I think this may introduce new 
problems when RTSP proxy is intervened,&nbsp;and existing RTSP can not deal with 
the&nbsp;scenario&nbsp;correctly.</SPAN></FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>The following is an example. To 
display the figure correctly, please maximize this email 
window.</SPAN></FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>&nbsp;&nbsp; Suppose that 
client A and client B wants to join different multicast&nbsp;groups on the same 
server.<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;&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;&nbsp; 
+--------+ <BR>&nbsp;&nbsp; | Client A 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
| RTSP proxy| 
&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; 
&nbsp;&nbsp;&nbsp;&nbsp; | Server |<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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp; |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
| Client B 
|&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;&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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp; 
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
Setup&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;&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;&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; |==================&gt; 
&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;&nbsp;&nbsp;&nbsp;&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;&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;&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;&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;&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;&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;&nbsp; 
Setup&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|====================&gt; |<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;&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;&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;&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;&nbsp; |&nbsp;&nbsp;&nbsp; 
Setup&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;&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;&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;&nbsp; 
|*****************&gt;|&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;&nbsp;&nbsp;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Setup&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;&nbsp;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp; |************************&gt; 
|<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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&lt;=====================|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;200 OK 
(SessionID=12345678)|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp; |&lt;************************ 
|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;|&nbsp;200 OK (SessionID=23456789)| 
<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;&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;&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;&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;&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;&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;&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;<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;<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; 
Fig.2&nbsp; 
Multicast&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>&nbsp;&nbsp; The interactive 
messages are listed as following.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>&nbsp;&nbsp; Session issued by 
Client A:<BR>&nbsp;&nbsp; C-&gt;P: SETUP rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
111<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>&nbsp;&nbsp; P-&gt;S: SETUP 
rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
333<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN></FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>&nbsp;&nbsp; Session issued by 
Client A:<BR>&nbsp;&nbsp; C-&gt;P: SETUP 
rtsp://live.example.com/anotherconcert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
222<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast<BR>&nbsp;&nbsp; P-&gt;S: SETUP 
rtsp://live.example.com/anotherconcert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
444<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV><SPAN class=772445903-11082009>
<DIV><BR><FONT size=5>&nbsp;&nbsp; Proxy will receive the following responses 
from server:<BR>&nbsp;&nbsp; S-&gt;P: RTSP/2.0 200 
OK<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
333<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server: 
PhonyServer/1.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date: Thu, 
23 Jan 2009 15:35:06 GMT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Transport: 
RTP/AVP;multicast;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Session:&nbsp;<SPAN class=772445903-11082009>12345678</SPAN></FONT></DIV>
<DIV><FONT size=5>&nbsp;&nbsp; S-&gt;P: RTSP/2.0 200 
OK<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
444<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server: 
PhonyServer/1.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date: Thu, 
23 Jan 2009 15:35:06 GMT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Transport: 
RTP/AVP;multicast;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Session:&nbsp;<SPAN class=772445903-11082009>23456789</SPAN></FONT></DIV>
<DIV><FONT size=5></FONT>&nbsp;</DIV>
<DIV><FONT size=5>In this case,<SPAN class=772445903-11082009> </SPAN>RTSP proxy 
can not&nbsp;<SPAN class=772445903-11082009>distinguish </SPAN>the response<SPAN 
class=772445903-11082009>s</SPAN>, then it may&nbsp;respond client with wrong 
message and induce&nbsp;<SPAN class=772445903-11082009>c</SPAN>lient<SPAN 
class=772445903-11082009>&nbsp;to</SPAN>&nbsp;join a wrong&nbsp;mutlicast group. 
</FONT></SPAN></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>Do anybody think this is an 
possible trap/deficiency, and&nbsp;RTSP should try to 
resolve?</SPAN></FONT></DIV>
<DIV><FONT size=5><SPAN class=772445903-11082009>Thanks.</SPAN></FONT></DIV>
<DIV><FONT size=5></FONT>&nbsp;</DIV>
<DIV align=left><FONT size=2>
<P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial"></SPAN><SPAN 
lang=EN-US><?xml:namespace prefix = o ns = 
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><FONT 
size=4>Regards</FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"></FONT><SPAN lang=EN-US 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt"><FONT 
size=4>Yingjie Gu</FONT></SPAN></P></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_yjj42zFXcNgcfbcqichw+Q)--

From web-usrn@ISI.EDU  Tue Aug 11 00:41:14 2009
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 143E93A6F78 for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 00:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.852
X-Spam-Level: 
X-Spam-Status: No, score=-16.852 tagged_above=-999 required=5 tests=[AWL=0.747, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OLg6LMAwyk6u for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 00:41:11 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 7EDEB3A68A4 for <mmusic@ietf.org>; Tue, 11 Aug 2009 00:41:11 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7B7dw16003684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Aug 2009 00:39:59 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n7B7dvYo003673; Tue, 11 Aug 2009 00:39:57 -0700 (PDT)
Date: Tue, 11 Aug 2009 00:39:57 -0700 (PDT)
Message-Id: <200908110739.n7B7dvYo003673@boreas.isi.edu>
To: ts@thomas-schierl.de, stewe@stewe.org, rjsparks@nostrum.com, fluffy@cisco.com, jo@acm.org, jf.mule@cablelabs.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: ah@TR-Sys.de, mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] [Editorial Errata Reported] RFC5583 (1828)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2009 07:41:14 -0000

The following errata report has been submitted for RFC5583,
"Signaling Media Decoding Dependency in the Session Description Protocol (SDP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5583&eid=1828

--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 5.2.2, pg.10

Original Text
-------------
[[ last paragraph of Section 5.2.2: ]]

          v
|  Further, dependency types MUST be defined in a Standards-Track
   document.


Corrected Text
--------------
|  Further dependency types MUST be defined in a Standards-Track
   document.


Notes
-----
Rationale:
  In this case, "Further" is an attribute; the spurious comma
  separates this attribute from its noun "[dependency] types",
  and thus changes the sense of the sentence in an inappropriate
  manner.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5583 (draft-ietf-mmusic-decoding-dependency-08)
--------------------------------------
Title               : Signaling Media Decoding Dependency in the Session Description Protocol (SDP)
Publication Date    : July 2009
Author(s)           : T. Schierl, S. Wenger
Category            : PROPOSED STANDARD
Source              : Multiparty Multimedia Session Control
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From web-usrn@ISI.EDU  Tue Aug 11 01:06:42 2009
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 391273A69F3 for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 01:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.868
X-Spam-Level: 
X-Spam-Status: No, score=-16.868 tagged_above=-999 required=5 tests=[AWL=0.731, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2c+O33Cc8iV for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 01:06:41 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 454AC3A6F78 for <mmusic@ietf.org>; Tue, 11 Aug 2009 01:06:41 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n7B85U0C015430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Aug 2009 01:05:31 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n7B85UNk015429; Tue, 11 Aug 2009 01:05:30 -0700 (PDT)
Date: Tue, 11 Aug 2009 01:05:30 -0700 (PDT)
Message-Id: <200908110805.n7B85UNk015429@boreas.isi.edu>
To: ts@thomas-schierl.de, stewe@stewe.org, rjsparks@nostrum.com, fluffy@cisco.com, jo@acm.org, jf.mule@cablelabs.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: ah@TR-Sys.de, mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] [Editorial Errata Reported] RFC5583 (1829)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2009 08:06:42 -0000

The following errata report has been submitted for RFC5583,
"Signaling Media Decoding Dependency in the Session Description Protocol (SDP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5583&eid=1829

--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 6.3, pg.12

Original Text
-------------
   The signaling mechanisms defined in this document MUST NOT be used to
|  negotiate between using the attribute-value pair (AVP) [RFC3551] and
                               ^^^^^^^^^^^^^^^^^^^^ 
   SAVP [RFC3711] profile for RTP.  However, both profiles MAY be used
   separately or jointly with the signaling mechanism defined in this
   document.


Corrected Text
--------------
   The signaling mechanisms defined in this document MUST NOT be used to
|  negotiate between using the Audio/Video Profile (AVP) [RFC3551] and
|  Secure Audio/Video Profile (SAVP) [RFC3711] for RTP.  However, both
   profiles MAY be used separately or jointly with the signaling
   mechanism defined in this document.


Notes
-----
Rationale:
  Nonsensical acronym expansion (introduced late in the process).
  The correct expansion could have been found by inspection of
  the References in Section 10.1, in the entry for [RFC3551] !

  Only changing the bad expansion turns the sentence weird;
  therefore, the above change proposal tries to balance the
  language by also expanding "SAVP" and saving the trailing
  instance of "profile" (being part of both acronym expansions).

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5583 (draft-ietf-mmusic-decoding-dependency-08)
--------------------------------------
Title               : Signaling Media Decoding Dependency in the Session Description Protocol (SDP)
Publication Date    : July 2009
Author(s)           : T. Schierl, S. Wenger
Category            : PROPOSED STANDARD
Source              : Multiparty Multimedia Session Control
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

From guyingjie@huawei.com  Tue Aug 11 21:20:53 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 431313A68DB for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 21:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.024
X-Spam-Level: 
X-Spam-Status: No, score=0.024 tagged_above=-999 required=5 tests=[AWL=0.518,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfQMt0F+I3RD for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 21:20:51 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 795413A657C for <mmusic@ietf.org>; Tue, 11 Aug 2009 21:20:32 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO800B7QWK299@szxga03-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 12:02:26 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO8002EAWK2T7@szxga03-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 12:02:26 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KO800KJ6WK10Y@szxml06-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 12:02:26 +0800 (CST)
Date: Wed, 12 Aug 2009 12:02:25 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <A181547BA711A7428A5C5091FEF75E74AACF41@SEA1CORPMAIL01.mediator.com>
To: 'Jaehwan Kim' <jhkim@vidiator.com>, mmusic@ietf.org
Message-id: <002301ca1b01$b3a54330$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_Yv6MgywzIF70yx0sLKtnKA)"
Thread-index: AcoaSZFrx3F0JjKoTPW+S2B9sWpzWgAL0zegABvK6LA=
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 04:20:53 -0000

This is a multi-part message in MIME format.

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

Hi Jaehwan,
RTSP may try to match CSeqs in (P->S) and (S->P) messages to differentiate,
but CSeq is used to arrange messages, changing CSeq's semantics may be
confusing. Besides, Proxy may generate a same CSeq for different requests,
then matching CSeq is not feasible in this scenario.  
Below is another example, in which server may not works correctly.
RTSP proxy receives two requests from different clients to the same resource
on one server.
 
   +----------+                      +--------------+          +--------+ 
   | Client A |                      | RTSP proxy |           | Server |
   +----------+                      +--------------+          +--------+
        |                                             |
|
        |    +----------+                       |
|
        |    | Client B |                        |
|
        |    +----------+                       |
|
        |         |                                   |
|
        |         |    Setup                      |
| 
        |==================>|                               |
        |         |                                   |
|
        |         |                                   |      Setup
|
        |         |                                   |============>|\
        |         |                                   |
| \ 
        |         |    Setup                      |
|  \  ???
        |         |****************>|                                |  /
what's difference?
        |         |                                   |      Setup
| /
        |         |                                   |**************>|/
        |         |                                   |
|

   The interactive messages of the above scenario is as following.
 
   Session issued by Client A:
 
   C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 111
         Transport: RTP/AVP;multicast 

 

   P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 333
         Transport: RTP/AVP;multicast

 

   Session issued by Client B:
   C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 222
         Transport: RTP/AVP;multicast

 

   P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 444

         Transport: RTP/AVP;multicast

        
Typically, RTSP server differentiates sessions by client IP address and
client port. But in this case, there is only one transport connection
bewteen RTSP proxy and RTSP server, so server can not find the difference
between the two requests. As a result, server regards them as the same
repeated request and I don't know how this abnormity will be dealed in RTSP
2.0.  
Maybe, server can differentiate by CSeq also, but there introduce at least
two matters.
1) proxy has to guarantee no repeated initial CSeq is generated
2) things become complicated when different proxy generate same CSeq, server
has to check both the IP/Port and CSeq in order to differentiate.
 
 
Regards

Yingjie Gu

 

  _____  

From: Jaehwan Kim [mailto:jhkim@vidiator.com] 
Sent: Tuesday, August 11, 2009 7:48 PM
To: Y.J. Gu; mmusic@ietf.org
Subject: RE: [MMUSIC] Question about RTSP proxy



Hi,

I think Proxy should handle different CSeq on Server side, while it can do
different TCP sessions on Client side.

 

Regards,

Jaehwan

 

From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Y.J. Gu
Sent: Tuesday, August 11, 2009 3:04 PM
To: mmusic@ietf.org
Subject: [MMUSIC] Question about RTSP proxy

 

Hi all,

In RTSP 2.0, it is permitted to transmit several client requests in one
Transport Connection. 

I think this may introduce new problems when RTSP proxy is intervened, and
existing RTSP can not deal with the scenario correctly.

The following is an example. To display the figure correctly, please
maximize this email window.

   Suppose that client A and client B wants to join different multicast
groups on the same server.
   +----------+                      +--------------+
+--------+ 
   | Client A |                       | RTSP proxy|
| Server |
   +----------+                      +--------------+
+--------+
        |                                              |
|
        |    +----------+                        |
|
        |    | Client B |                         |
|
        |    +----------+                        |
|
        |         |                                    |
|
        |         |    Setup                       |
| 
        |==================>  |
|
        |         |                                    |
|
        |         |                                    |      Setup
|
        |         |
|====================> |
        |         |                                    |
|  
        |         |    Setup                       |
|
        |         |*****************>|
|
        |         |                                   |      Setup
|
        |         |
|************************> |
        |         |                                   |
|
        |         |                                   |
|
        |         |
|<=====================|
        |         |                                   | 200 OK
(SessionID=12345678)|
        |         |
|<************************ |
        |         |                                   | 200 OK
(SessionID=23456789)| 
        |         |                    ?????????|
|
        |         |                                   |
|
             
                           
                          Fig.2  Multicast 
                                     

 

   The interactive messages are listed as following.

 

   Session issued by Client A:
   C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 111
         Transport: RTP/AVP;multicast

 

   P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
         CSeq: 333
         Transport: RTP/AVP;multicast

   Session issued by Client A:
   C->P: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
         CSeq: 222
         Transport: RTP/AVP;multicast
   P->S: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
         CSeq: 444
         Transport: RTP/AVP;multicast

 


   Proxy will receive the following responses from server:
   S->P: RTSP/2.0 200 OK
         CSeq: 333
         Server: PhonyServer/1.0
         Date: Thu, 23 Jan 2009 15:35:06 GMT
         Transport: RTP/AVP;multicast;
              dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16
         Session: 12345678

   S->P: RTSP/2.0 200 OK
         CSeq: 444
         Server: PhonyServer/1.0
         Date: Thu, 23 Jan 2009 15:35:06 GMT
         Transport: RTP/AVP;multicast;
              dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16
         Session: 23456789

 

In this case, RTSP proxy can not distinguish the responses, then it may
respond client with wrong message and induce client to join a wrong
mutlicast group. 

 

Do anybody think this is an possible trap/deficiency, and RTSP should try to
resolve?

Thanks.

 

 

Regards

Yingjie Gu

 


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = 
"urn:schemas-microsoft-com:vml" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word" xmlns:x = 
"urn:schemas-microsoft-com:office:excel" xmlns:p = 
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a = 
"urn:schemas-microsoft-com:office:access" xmlns:dt = 
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = 
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = 
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = 
"urn:schemas-microsoft-com:office:publisher" xmlns:ss = 
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = 
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = 
"urn:schemas-microsoft-com:office:odc" xmlns:oa = 
"urn:schemas-microsoft-com:office:activation" xmlns:html = 
"http://www.w3.org/TR/REC-html40" xmlns:q = 
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc = 
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl = 
"http://schemas.microsoft.com/repl/" xmlns:mt = 
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = 
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda = 
"http://www.passport.com/NameSpace.xsd" xmlns:ois = 
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = 
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = 
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = 
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = 
"http://schemas.microsoft.com/data/udc" xmlns:xsd = 
"http://www.w3.org/2001/XMLSchema" xmlns:sub = 
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = 
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp = 
"http://schemas.microsoft.com/sharepoint/" xmlns:sps = 
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = 
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = 
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = 
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = 
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = 
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = 
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = 
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = 
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = 
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = 
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = 
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = 
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = 
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = 
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = 
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = 
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" 
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{mso-style-priority:99;
	mso-style-link:"\C778\C0AC\B9D0 Char";
	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","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.Char
	{mso-style-name:"\C778\C0AC\B9D0 Char";
	mso-style-priority:99;
	mso-style-link:\C778\C0AC\B9D0;
	font-family:"Malgun Gothic";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Malgun Gothic";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=KO vLink=purple link=blue>
<DIV dir=ltr align=left><FONT color=#0000ff size=5><SPAN 
class=459435800-12082009>Hi Jaehwan,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT size=5>RTSP may try to match 
CSeqs in&nbsp;(P-&gt;S) and (S-&gt;P) messages to&nbsp;differentiate, but CSeq 
is used to arrange&nbsp;messages, changing CSeq's&nbsp;<SPAN 
class=459435800-12082009>semantics</SPAN> may be confusing.&nbsp;<SPAN 
class=459435800-12082009>Besides, </SPAN><SPAN class=459435800-12082009>Proxy 
may generate a same CSeq for different requests, t</SPAN>hen matching 
CSeq&nbsp;is not feasible in this scenario.&nbsp;<SPAN class=459435800-12082009> 
</SPAN></FONT></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT color=#0000ff 
size=5>Below is another&nbsp;example, in which server may not works 
correctly.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT color=#0000ff 
size=5>RTSP proxy receives two requests from different clients to the same 
resource on one server.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009>&nbsp;</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
+--------+ <BR>&nbsp;&nbsp; | Client A 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
| RTSP proxy |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; | Server 
|<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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&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;&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;&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; | Client B 
|&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;&nbsp;&nbsp;&nbsp;&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;&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;&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;&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;&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;&nbsp;&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; 
Setup&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;&nbsp;&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; 
|==================&gt;|&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Setup&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|============&gt;|\<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;&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;&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;\ <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
Setup&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;&nbsp;&nbsp;&nbsp;&nbsp;&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;&nbsp; 
|****************&gt;|&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;&nbsp;&nbsp;&nbsp; 
|&nbsp; /&nbsp;&nbsp;what's 
difference?<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;&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; 
Setup&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;|**************&gt;|/<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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|<BR><BR>&nbsp;&nbsp; The interactive messages of the above scenario is as 
following.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp; Session issued by Client A:</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT size=5><FONT 
color=#0000ff>&nbsp;&nbsp; C-&gt;P: SETUP rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
111<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast<SPAN lang=EN-US><o:p></o:p></SPAN></FONT>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US><FONT 
color=#0000ff>&nbsp;<o:p></o:p></FONT></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><FONT color=#0000ff><SPAN lang=EN-US 
style="FONT-SIZE: 18pt">&nbsp;&nbsp; P-&gt;S: SETUP 
rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
333<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN></FONT></P>
<P class=MsoNormal><FONT color=#0000ff><SPAN lang=EN-US 
style="FONT-SIZE: 18pt"></SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></FONT>&nbsp;</P></DIV></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=459435800-12082009><FONT size=5><FONT 
color=#0000ff>&nbsp;&nbsp; Session issued by Client B:<BR>&nbsp;&nbsp; C-&gt;P: 
SETUP rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
CSeq:&nbsp;222<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast<SPAN lang=EN-US><o:p></o:p></SPAN></FONT></DIV>
<DIV dir=ltr align=left>
<P class=MsoNormal><SPAN lang=EN-US><FONT 
color=#0000ff>&nbsp;<o:p></o:p></FONT></SPAN></P></DIV>
<DIV dir=ltr align=left>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt"><FONT 
color=#0000ff>&nbsp;&nbsp; P-&gt;S: SETUP rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq:&nbsp;<SPAN 
class=459435800-12082009>444</SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt"><SPAN 
class=459435800-12082009></SPAN><FONT 
color=#0000ff>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</FONT></SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV dir=ltr align=left></FONT><FONT color=#0000ff><FONT 
size=5>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR><SPAN 
class=459435800-12082009>Typically,</SPAN> RTSP server differentiates sessions 
by client IP address and client<SPAN class=459435800-12082009>&nbsp;</SPAN>port. 
But in this case, there is only one transport connection&nbsp;bewteen RTSP proxy 
and RTSP server, so server can not find the&nbsp;difference between the two 
requests. As a result, server regards&nbsp;them as the same repeated request 
and&nbsp;<SPAN class=459435800-12082009>I don't know how this abnormity will be 
dealed in RTSP 2.0</SPAN>.<SPAN class=459435800-12082009>&nbsp;</SPAN><SPAN 
class=459435800-12082009>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT size=5><SPAN 
class=459435800-12082009>Maybe, server can differentiate by CSeq also, but there 
introduce at least&nbsp;two matters.</SPAN></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT size=5><SPAN 
class=459435800-12082009>1) proxy has to guarantee no&nbsp;repeated initial CSeq 
is&nbsp;generated</SPAN></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><FONT size=5><SPAN 
class=459435800-12082009>2) things become complicated when different proxy 
generate same CSeq, server has to check both the IP/Port and CSeq in order to 
differentiate.</SPAN></FONT></FONT></DIV>
<DIV><FONT color=#0000ff size=5><SPAN 
class=459435800-12082009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff size=5><SPAN 
class=459435800-12082009></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff size=5><SPAN 
class=459435800-12082009></SPAN></FONT></SPAN><FONT size=2><SPAN 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><FONT 
size=4>Regards</FONT></SPAN></DIV>
<DIV align=left>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"></FONT><SPAN lang=EN-US 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt"><FONT 
size=4>Yingjie Gu</FONT></SPAN></P></DIV>
<DIV>&nbsp;</DIV><BR>
<DIV class=OutlookMessageHeader lang=zh-cn dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Jaehwan Kim [mailto:jhkim@vidiator.com] 
<BR><B>Sent:</B> Tuesday, August 11, 2009 7:48 PM<BR><B>To:</B> Y.J. Gu; 
mmusic@ietf.org<BR><B>Subject:</B> RE: [MMUSIC] Question about RTSP 
proxy<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Hi,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">I think 
Proxy should handle different CSeq on Server side, while it can do different TCP 
sessions on Client side.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Jaehwan<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<DIV>
<DIV 
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN 
lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> 
mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] <B>On Behalf Of 
</B>Y.J. Gu<BR><B>Sent:</B> Tuesday, August 11, 2009 3:04 PM<BR><B>To:</B> 
mmusic@ietf.org<BR><B>Subject:</B> [MMUSIC] Question about RTSP 
proxy<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><SPAN lang=EN-US><o:p>&nbsp;</o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">Hi all,</SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">In RTSP 2.0, it is 
permitted to transmit several client requests in one Transport Connection. 
</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">I think this may 
introduce new problems when RTSP proxy is intervened,&nbsp;and existing RTSP can 
not deal with the&nbsp;scenario&nbsp;correctly.</SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">The following is an 
example. To display the figure correctly, please maximize this email 
window.</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; Suppose 
that client A and client B wants to join different multicast&nbsp;groups on the 
same server.<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;&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;&nbsp; 
+--------+ <BR>&nbsp;&nbsp; | Client A 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
| RTSP proxy| 
&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; 
&nbsp;&nbsp;&nbsp;&nbsp; | Server |<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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp; |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
| Client B 
|&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;&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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp; 
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; 
Setup&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;&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;&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; |==================&gt; 
&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;&nbsp;&nbsp;&nbsp;&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;&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;&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;&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;&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;&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;&nbsp; 
Setup&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|====================&gt; |<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;&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;&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;&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;&nbsp; |&nbsp;&nbsp;&nbsp; 
Setup&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;&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;&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;&nbsp; 
|*****************&gt;|&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;&nbsp;&nbsp;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Setup&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;&nbsp;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp; |************************&gt; 
|<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;&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;&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;&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;&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;&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;&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;&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&lt;=====================|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;200 OK 
(SessionID=12345678)|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp; |&lt;************************ 
|<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;|&nbsp;200 OK (SessionID=23456789)| 
<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;&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;&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;&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;&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;&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;&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;<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;<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; 
Fig.2&nbsp; 
Multicast&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; The 
interactive messages are listed as following.</SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; Session 
issued by Client A:<BR>&nbsp;&nbsp; C-&gt;P: SETUP 
rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
111<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; 
P-&gt;S: SETUP rtsp://live.example.com/concert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
333<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; Session 
issued by Client A:<BR>&nbsp;&nbsp; C-&gt;P: SETUP 
rtsp://live.example.com/anotherconcert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
222<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast<BR>&nbsp;&nbsp; P-&gt;S: SETUP 
rtsp://live.example.com/anotherconcert/audio 
RTSP/2.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
444<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transport: 
RTP/AVP;multicast</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US><BR></SPAN><SPAN lang=EN-US 
style="FONT-SIZE: 18pt">&nbsp;&nbsp; Proxy will receive the following responses 
from server:<BR>&nbsp;&nbsp; S-&gt;P: RTSP/2.0 200 
OK<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CSeq: 
333<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server: 
PhonyServer/1.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date: Thu, 
23 Jan 2009 15:35:06 GMT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Transport: 
RTP/AVP;multicast;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Session:&nbsp;12345678</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">&nbsp;&nbsp; 
S-&gt;P: RTSP/2.0 200 OK<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
CSeq: 444<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server: 
PhonyServer/1.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date: Thu, 
23 Jan 2009 15:35:06 GMT<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Transport: 
RTP/AVP;multicast;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Session:&nbsp;23456789</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">In this case, RTSP 
proxy can not&nbsp;distinguish the responses, then it may&nbsp;respond client 
with wrong message and induce&nbsp;client&nbsp;to&nbsp;join a 
wrong&nbsp;mutlicast group. </SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">Do anybody think 
this is an possible trap/deficiency, and&nbsp;RTSP should try to 
resolve?</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt">Thanks.</SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
<P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US 
style="FONT-SIZE: 10pt"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 13.5pt; FONT-FAMILY: 'Arial','sans-serif'">Regards</SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 13.5pt; FONT-FAMILY: 'Arial','sans-serif'">Yingjie 
Gu</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN 
lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV></DIV></BODY></HTML>

--Boundary_(ID_Yv6MgywzIF70yx0sLKtnKA)--

From guyingjie@huawei.com  Tue Aug 11 23:37:17 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ADCD3A6801 for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 23:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.703
X-Spam-Level: *
X-Spam-Status: No, score=1.703 tagged_above=-999 required=5 tests=[AWL=-1.176,  BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_BACKHAIR_11=1,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Rt3JSHweFN7 for <mmusic@core3.amsl.com>; Tue, 11 Aug 2009 23:37:16 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 81B5A3A67D8 for <mmusic@ietf.org>; Tue, 11 Aug 2009 23:37:14 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO9009CL3JYYE@szxga03-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 14:33:34 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO90029Y3JYT7@szxga03-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 14:33:34 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KO900M873JY1E@szxml06-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 14:33:34 +0800 (CST)
Date: Wed, 12 Aug 2009 14:33:34 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <A181547BA711A7428A5C5091FEF75E74AAD08C@SEA1CORPMAIL01.mediator.com>
To: 'Jaehwan Kim' <jhkim@vidiator.com>, mmusic@ietf.org
Message-id: <003901ca1b16$d129d2d0$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_LyzV7DYu7W70Zh4es740tg)"
Thread-index: AcoaSZFrx3F0JjKoTPW+S2B9sWpzWgAL0zegABvK6LAACBxtQAADgmow
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 06:37:17 -0000

This is a multi-part message in MIME format.

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

Hi Jaehwan
well, for the above 2 examples, I am considering the second case. Two
requests/responses on one TCP connection.
By the latest above example, I meant when the two SETUP requests for same
resource transmitted through one TCP connection, server will have difficult
to differentiate them. 
By the example in my first email, I meant when two responses sent by one
server through one TCP connection to Proxy, Proxy 
may have difficult to differentiate them.
 
Surely, RTSP proxy, when implemented, can handle the problem by compromised
solutions, e.g. CSeq. While proxy has to guarantee to generate different
initial CSeq for each session by, e.g. ,comparing the current CSeq with
those generated before. How many concurrent sessions can a proxy support,
maybe 10000, then comparing CSeq would be a huge burden, because that will
be a large order of magnitude. 
 
Here is another assumption. Proxy send 2 RTSP requests to 2 servers, but,
unfortunately,  the 2 servers response the same session ID, by what mean
will the proxy handle the following messages of the 2 sessions?  Maybe take
session ID and TCP connection together into consideration. Proxy has to do
this every time it receive a message from the servers. That will be a huge
workload. Besides, that will tie RTSP closely toTransport protocol, however
RTSP 2.0 is in no way tied to a Transport protocol according to RFC2326.
 
Basically, I think the existing solutions to proxy can work but are very
much compromised and result in complexity. We should find a easy and  clear
way to resolve the problem.  
 
BTW,Multicast is just an example, the problem doesn't limit to multicast.
 
 
 

Regards

Yingjie Gu

 

  _____  

From: Jaehwan Kim [mailto:jhkim@vidiator.com] 
Sent: Wednesday, August 12, 2009 1:09 PM
To: Y.J. Gu; mmusic@ietf.org
Subject: RE: [MMUSIC] Question about RTSP proxy



Hi Yingjie,

On P<->S side, there would be two cases:

1/ using two different TCP sessions(typical case): Although the same cseq is
found, Proxy should be able to handle different TCP sessions. And Proxy
should map two different Client requests with these.

2/ using just one TCP session for two different RTSP sessions: Simple
solution is to manage cseq well because proxy assign the value.

 

Which one do you consider?

 

And you may consider also non-permanent connection case, but still proxy
could manage them and deliver Session ID generated from the server from my
understanding.

 

Anyway it looks not multicast issue. And there are already many
off-the-shelf RTSP proxy handle this matter without any problem.

 

Regards,

Jaehwan

 


 


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = 
"urn:schemas-microsoft-com:vml" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word" xmlns:x = 
"urn:schemas-microsoft-com:office:excel" xmlns:p = 
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a = 
"urn:schemas-microsoft-com:office:access" xmlns:dt = 
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = 
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = 
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = 
"urn:schemas-microsoft-com:office:publisher" xmlns:ss = 
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = 
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = 
"urn:schemas-microsoft-com:office:odc" xmlns:oa = 
"urn:schemas-microsoft-com:office:activation" xmlns:html = 
"http://www.w3.org/TR/REC-html40" xmlns:q = 
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc = 
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl = 
"http://schemas.microsoft.com/repl/" xmlns:mt = 
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = 
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda = 
"http://www.passport.com/NameSpace.xsd" xmlns:ois = 
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = 
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = 
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = 
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = 
"http://schemas.microsoft.com/data/udc" xmlns:xsd = 
"http://www.w3.org/2001/XMLSchema" xmlns:sub = 
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = 
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp = 
"http://schemas.microsoft.com/sharepoint/" xmlns:sps = 
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = 
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = 
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = 
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = 
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = 
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = 
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = 
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = 
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = 
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = 
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = 
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = 
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = 
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = 
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = 
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = 
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" 
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR><!--[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:SimSun;
	panose-1:2 1 6 0 3 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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{mso-style-priority:99;
	mso-style-link:"\C778\C0AC\B9D0 Char";
	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","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.Char
	{mso-style-name:"\C778\C0AC\B9D0 Char";
	mso-style-priority:99;
	mso-style-link:\C778\C0AC\B9D0;
	font-family:"Malgun Gothic";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Malgun Gothic";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Malgun Gothic";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=KO vLink=purple link=blue>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5>Hi Jaehwan</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5>well,&nbsp;for the above 2 examples,&nbsp;I am considering the second 
case. Two requests/responses on one TCP connection.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5>By&nbsp;the latest above example, I meant when the two SETUP requests for 
same resource&nbsp;transmitted through one TCP connection, server will have 
difficult to differentiate them. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5>By the example in my first email, I meant when two responses sent by one 
server through one TCP connection to Proxy, Proxy </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5>may have difficult to differentiate them.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5></FONT></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009><FONT color=#0000ff size=5>Surely, RTSP 
proxy, when implemented, can handle the problem by compromised solutions, e.g. 
CSeq. While proxy has to guarantee to&nbsp;generate different initial CSeq for 
each session by, e.g. ,comparing the current CSeq with those generated 
before.&nbsp;How many&nbsp;concurrent sessions can a proxy support, maybe 10000, 
then comparing CSeq would be a huge burden, because that will be a large order 
of magnitude. </FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009>Here is another assumption. Proxy send 2 
RTSP requests to 2 servers, but, unfortunately,&nbsp; the 2 servers response the 
same session ID,&nbsp;by what mean&nbsp;will the proxy handle the following 
messages of the 2 sessions?&nbsp; Maybe take session ID and TCP connection 
together into consideration. Proxy has to do this every time it receive a 
message from the servers. That will be a huge workload. Besides, that will tie 
RTSP closely toTransport protocol, however RTSP 2.0 is in no way tied to a 
Transport protocol according to RFC2326.</SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009>Basically, I think the existing solutions 
to proxy can work but are&nbsp;very much compromised and result in complexity. 
We should find a easy and &nbsp;clear way to resolve the problem.&nbsp; 
</SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT color=#0000ff 
size=5><SPAN class=149541805-12082009><FONT face=&#23435;&#20307; color=#0000ff 
size=5>BTW,Multicast is just an example, the problem doesn't limit to 
multicast.</FONT></SPAN></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT face=&#23435;&#20307; 
color=#0000ff size=5><SPAN 
class=149541805-12082009></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=149541805-12082009><FONT face=&#23435;&#20307; 
color=#0000ff size=5><SPAN 
class=149541805-12082009></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV align=left><FONT size=2>
<P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial"></SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><FONT 
size=4>Regards</FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"></FONT><SPAN lang=EN-US 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt"><FONT 
size=4>Yingjie Gu</FONT></SPAN></P></DIV>
<DIV>&nbsp;</DIV><BR>
<DIV class=OutlookMessageHeader lang=zh-cn dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Jaehwan Kim [mailto:jhkim@vidiator.com] 
<BR><B>Sent:</B> Wednesday, August 12, 2009 1:09 PM<BR><B>To:</B> Y.J. Gu; 
mmusic@ietf.org<BR><B>Subject:</B> RE: [MMUSIC] Question about RTSP 
proxy<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Hi 
Yingjie,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">On 
P&lt;-&gt;S side, there would be two cases:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">1/ using 
two different TCP sessions(typical case): Although the same cseq is found, Proxy 
should be able to handle different TCP sessions. And Proxy should map two 
different Client requests with these.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">2/ using 
just one TCP session for two different RTSP sessions: Simple solution is to 
manage cseq well because proxy assign the value.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Which one 
do you consider?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">And you 
may consider also non-permanent connection case, but still proxy could manage 
them and deliver Session ID generated from the server from my 
understanding.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Anyway it 
looks not multicast issue. And there are already many off-the-shelf RTSP proxy 
handle this matter without any problem.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-US 
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Jaehwan<o:p></o:p></SPAN></P></DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV align=left><FONT size=2>
<P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial"></SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" align=left>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"></FONT><SPAN lang=EN-US 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt"><FONT 
size=4></FONT></SPAN></P><SPAN 
lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV></BODY></HTML>

--Boundary_(ID_LyzV7DYu7W70Zh4es740tg)--

From guyingjie@huawei.com  Wed Aug 12 01:26:55 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A21E3A6963 for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 01:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.115
X-Spam-Level: 
X-Spam-Status: No, score=0.115 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ozPhAfLEIea for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 01:26:54 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [58.251.152.67]) by core3.amsl.com (Postfix) with ESMTP id 6ECA83A67C2 for <mmusic@ietf.org>; Wed, 12 Aug 2009 01:26:54 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO900FSH7ZE7L@szxga04-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 16:09:15 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KO9003ZI7ZE8K@szxga04-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 16:09:14 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KO900DJU7ZET0@szxml04-in.huawei.com> for mmusic@ietf.org; Wed, 12 Aug 2009 16:09:14 +0800 (CST)
Date: Wed, 12 Aug 2009 16:09:13 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <63cccc5eec3c5aec41135823d30bdf2f@chewa.net>
To: =?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?= <remi@remlab.net>
Message-id: <004401ca1b24$2e182f70$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Thread-index: AcobHAMwghOcqQuNRkKcFEat3OS78AABrRzQ
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 08:26:55 -0000

Hi Remi, see in line please.

Regards

Yingjie Gu

=20

> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi@remlab.net]=20
> Sent: Wednesday, August 12, 2009 2:50 PM
> To: Y.J. Gu
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Question about RTSP proxy
>=20
>=20
>     Hello,
>=20
> On Tue, 11 Aug 2009 14:04:20 +0800, "Y.J. Gu"=20
> <guyingjie@huawei.com> wrote:
> > In RTSP 2.0, it is permitted to transmit several client requests in=20
> > one Transport Connection.
> > I think this may introduce new problems when RTSP proxy is=20
> intervened,
> and
> > existing RTSP can not deal with the scenario correctly.
>=20
> I fail to see why.
>=20
> > The following is an example. To display the figure=20
> correctly, please=20
> > maximize this email window.
> >    Suppose that client A and client B wants to join different=20
> > multicast groups on the same server.
> (...)=20
> > In this case, RTSP proxy can not distinguish the responses, then it=20
> > may respond client with wrong message and induce client to join a=20
> > wrong mutlicast group.
>=20
> The RTSP proxy can (and in fact probably MUST) pair requests=20
> and responses from the CSeq and/or from the ordering. As far=20
> as I know, the RTSP server must send responses in the same=20
> order as it receives requests (although it may interleave=20
> some server-to-client requests).

If I understand correctly, you mean if RTSP proxy send Request A earlier
than Request B, then server must response A earlier than B. By this =
order,
RTSP proxy can pair the requests&responses.=20
But what if server receive B earlier than A when traffic congest. Server
will response B earlier than A.

> Besides, I fail to see how this would be specific to multicast.

Yes, Multicast is an example, it is not specific to multicast.=20

> --
> R=E9mi Denis-Courmont
>=20


From Simo.Veikkolainen@nokia.com  Wed Aug 12 02:10:34 2009
Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 408993A69CC for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 02:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krs1e36xfpD6 for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 02:10:33 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id B6A2B3A635F for <mmusic@ietf.org>; Wed, 12 Aug 2009 02:10:32 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n7C82ilx009114 for <mmusic@ietf.org>; Wed, 12 Aug 2009 11:02:58 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 12 Aug 2009 11:02:58 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 12 Aug 2009 11:02:58 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 12 Aug 2009 11:02:53 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Wed, 12 Aug 2009 10:02:47 +0200
From: <Simo.Veikkolainen@nokia.com>
To: <mmusic@ietf.org>
Date: Wed, 12 Aug 2009 10:02:41 +0200
Thread-Topic: [MMUSIC] A replacement for ANAT
Thread-Index: Acn+Ht6b7BCUGPf8Sx21Vd9MnFbb/wAD2+LAACQixBAADQRQgAAgkgEAAA5LAuAETrbMAAADMw1gAZNMzzAA92lJsA==
Message-ID: <B23B311878A0B4438F5F09F47E01AAE03A73F09484@NOK-EUMSG-01.mgdnok.nokia.com>
References: <08BA2C59E081884DB2AAE4A0BE9D6DC1368EAB@ftrdmel0.rd.francetelecom.fr><E6C2E8958BA59A4FB960963D475F7AC31960080508@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE1366@NOK-EUMSG-01.mgdnok.nokia.com><E6C2E8958BA59A4FB960963D475F7AC31961194B3B@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE193D@NOK-EUMSG-01.mgdnok.nokia.com><4a714f63.02a1660a.40cd.0c70@mx.google.com> <E6C2E8958BA59A4FB960963D475F7AC319890C504A@mail> <CA9998CD4A020D418654FCDEF4E707DF0B1683D8@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0B1683D8@esealmw113.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Aug 2009 08:02:53.0173 (UTC) FILETIME=[4B20DA50:01CA1B23]
X-Nokia-AV: Clean
Subject: Re: [MMUSIC] A replacement for ANAT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 09:10:34 -0000

=20

>-----Original Message-----
>From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
>Sent: 07 August, 2009 12:52
>To: Hadriel Kaplan; Roni Even; Veikkolainen Simo=20
>(Nokia-D/Helsinki); mmusic@ietf.org
>Subject: RE: [MMUSIC] A replacement for ANAT
>
>
>Hi,
>
>This is what I said at the mic: we already do "replace" ICE.

Well, not quite. ICE is currently the only WG document that defines how to =
indicate alternative transport addresses (IP address and port for a particu=
lar transport protocol). Just indicating alternative IP addresses is not en=
ough - unless you assume that the port is always the same.


>However, even with ICE, I think one problem is that it is not=20
>very clear how to use ICE for pure=20
>offering-of-alternative-IP-addresses, when you don't use NAT=20
>traversal - or you use another mechanism for NAT traversal.

ICE does not consider this case, since it *is* the NAT traversal mechanism.=
=20

>Let's take a simple example:
>
>Alice sends an offer, with a single IPv4 and a single IPv6=20
>address, using ICE candidates. There are no STUN or TURN candidates.
>
>Bob only supports IPv4, so he sends back an IPv4 candidate.=20
>Bob doesn't provide any STUN or TURN candidates either.
>
>Now, is it is possible for Alice and Bob to start using the=20
>IPv4 addresses at this point (I guess a new offer may be=20
>required to indicate which candicate was chosen), or are they=20
>required (by ICE) to initiate connectivity checks? What if the=20
>checks fail, e.g. due to the usage of some other NAT traversal=20
>mechanism, or because there is no end-to-end media path yet -=20
>which may be the reason that another NAT traversal mechanism=20
>in the first place.

Full ICE implementations do connectivity checks. If there is "some other NA=
T traversal mechanism", then I guess ICE is not needed.

Simo


>Regards,
>
>Christer
>=20
>
>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]=20
>On Behalf Of Hadriel Kaplan
>Sent: Thursday, July 30, 2009 12:15 PM
>To: Roni Even; Simo.Veikkolainen@nokia.com; mmusic@ietf.org
>Subject: Re: [MMUSIC] A replacement for ANAT
>
>
>I'm confused by this - how does offering different *addresses*=20
>in sdp-cap not "replace" ICE, but offering different ports=20
>does replace it?
>
>-hadriel
>
>> -----Original Message-----
>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>> Sent: Thursday, July 30, 2009 3:43 AM
>> To: Simo.Veikkolainen@nokia.com; Hadriel Kaplan; mmusic@ietf.org
>> Subject: RE: [MMUSIC] A replacement for ANAT
>>=20
>> Simo,
>> The reason for not offering different ports in cap=20
>negotiation work is
>
>> to not replace ICE Roni Even
>>=20
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic
>=

From christer.holmberg@ericsson.com  Wed Aug 12 02:19:34 2009
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03BA63A635F for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 02:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.527
X-Spam-Level: 
X-Spam-Status: No, score=-5.527 tagged_above=-999 required=5 tests=[AWL=0.722,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CPdAeyl+-zx for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 02:19:33 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 712703A695F for <mmusic@ietf.org>; Wed, 12 Aug 2009 02:19:27 -0700 (PDT)
X-AuditID: c1b4fb3c-b7bccae00000385d-15-4a8288ccb760
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 92.EB.14429.CC8828A4; Wed, 12 Aug 2009 11:18:04 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 12 Aug 2009 11:18:04 +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
Date: Wed, 12 Aug 2009 11:18:03 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0E2D22E2@esealmw113.eemea.ericsson.se>
In-Reply-To: <B23B311878A0B4438F5F09F47E01AAE03A73F09484@NOK-EUMSG-01.mgdnok.nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] A replacement for ANAT
Thread-Index: Acn+Ht6b7BCUGPf8Sx21Vd9MnFbb/wAD2+LAACQixBAADQRQgAAgkgEAAA5LAuAETrbMAAADMw1gAZNMzzAA92lJsAADD/dg
References: <08BA2C59E081884DB2AAE4A0BE9D6DC1368EAB@ftrdmel0.rd.francetelecom.fr><E6C2E8958BA59A4FB960963D475F7AC31960080508@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE1366@NOK-EUMSG-01.mgdnok.nokia.com><E6C2E8958BA59A4FB960963D475F7AC31961194B3B@mail><B23B311878A0B4438F5F09F47E01AAE03A72CE193D@NOK-EUMSG-01.mgdnok.nokia.com><4a714f63.02a1660a.40cd.0c70@mx.google.com><E6C2E8958BA59A4FB960963D475F7AC319890C504A@mail><CA9998CD4A020D418654FCDEF4E707DF0B1683D8@esealmw113.eemea.ericsson.se> <B23B311878A0B4438F5F09F47E01AAE03A73F09484@NOK-EUMSG-01.mgdnok.nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Simo.Veikkolainen@nokia.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 12 Aug 2009 09:18:04.0378 (UTC) FILETIME=[CC041BA0:01CA1B2D]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [MMUSIC] A replacement for ANAT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 09:19:34 -0000

Hi,=20

>>This is what I said at the mic: we already do "replace" ICE.
>=20
>Well, not quite. ICE is currently the only WG document that=20
>defines how to indicate alternative transport addresses (IP=20
>address and port for a particular transport protocol). Just=20
>indicating alternative IP addresses is not enough - unless=20
>you assume that the port is always the same.

Well, we "partly" replace ICE, then :)

>>However, even with ICE, I think one problem is that it is not very=20
>>clear how to use ICE for pure offering-of-alternative-IP-addresses,=20
>>when you don't use NAT traversal - or you use another=20
>>mechanism for NAT traversal.
>=20
>ICE does not consider this case, since it *is* the NAT traversal
mechanism.=20

Well, that is the problem, if I only want to provide alternative
addresses/ports.

ANAT was not a NAT traversal mechanism, and AFAIK ICE was supposed to
replace ANAT.=20

>>Let's take a simple example:
>>
>>Alice sends an offer, with a single IPv4 and a single IPv6 address,=20
>>using ICE candidates. There are no STUN or TURN candidates.
>>
>>Bob only supports IPv4, so he sends back an IPv4 candidate.=20
>>Bob doesn't provide any STUN or TURN candidates either.
>>
>>Now, is it is possible for Alice and Bob to start using the
>>IPv4 addresses at this point (I guess a new offer may be required to=20
>>indicate which candicate was chosen), or are they required=20
>>(by ICE) to initiate connectivity checks? What if the checks fail,
e.g.=20
>>due to the usage of some other NAT traversal mechanism, or because
there is no=20
>>end-to-end media path yet - which may be the reason that another NAT=20
>>traversal mechanism in the first place.
>=20
>Full ICE implementations do connectivity checks. If there is=20
>"some other NAT traversal mechanism", then I guess ICE is not needed.

Well, in that case you can't offer alternative IP addresses/ports.

Regards,

Christer





> >-----Original Message-----
> >From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On=20
> >Behalf Of Hadriel Kaplan
> >Sent: Thursday, July 30, 2009 12:15 PM
> >To: Roni Even; Simo.Veikkolainen@nokia.com; mmusic@ietf.org
> >Subject: Re: [MMUSIC] A replacement for ANAT
> >
> >
> >I'm confused by this - how does offering different *addresses* in=20
> >sdp-cap not "replace" ICE, but offering different ports does replace=20
> >it?
> >
> >-hadriel
> >
> >> -----Original Message-----
> >> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >> Sent: Thursday, July 30, 2009 3:43 AM
> >> To: Simo.Veikkolainen@nokia.com; Hadriel Kaplan; mmusic@ietf.org
> >> Subject: RE: [MMUSIC] A replacement for ANAT
> >>=20
> >> Simo,
> >> The reason for not offering different ports in cap
> >negotiation work is
> >
> >> to not replace ICE Roni Even
> >>=20
> >_______________________________________________
> >mmusic mailing list
> >mmusic@ietf.org
> >https://www.ietf.org/mailman/listinfo/mmusic
> >
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>=20

From jgordon@real.com  Wed Aug 12 11:43:45 2009
Return-Path: <jgordon@real.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC0B03A6994 for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 11:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level: 
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_BACKHAIR_56=1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5XOLRBYTumt for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 11:43:44 -0700 (PDT)
Received: from cir-el.real.com (cir-el.real.com [207.188.23.7]) by core3.amsl.com (Postfix) with ESMTP id DDDD73A6807 for <mmusic@ietf.org>; Wed, 12 Aug 2009 11:43:44 -0700 (PDT)
Received: from [172.23.147.119] ([::ffff:172.23.147.119]) (AUTH: PLAIN jgordon, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by cir-el.real.com with esmtp; Wed, 12 Aug 2009 11:36:53 -0700 id 001FC185.4A830BC5.00006F8D
Message-ID: <4A830BC4.30301@real.com>
Date: Wed, 12 Aug 2009 11:36:52 -0700
From: Jamie Gordon <jgordon@real.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: "Y.J. Gu" <guyingjie@huawei.com>
References: <001701ca1a49$91bcba40$400ca40a@china.huawei.com>
In-Reply-To: <001701ca1a49$91bcba40$400ca40a@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 18:43:45 -0000

On 8/10/2009 11:04 PM, Y.J. Gu wrote:
> Hi all,
> In RTSP 2.0, it is permitted to transmit several client requests in one 
> Transport Connection.
> I think this may introduce new problems when RTSP proxy is 
> intervened, and existing RTSP can not deal with the scenario correctly.
> The following is an example. To display the figure correctly, please 
> maximize this email window.

This has not changed from RTSP 1.0, and even some existing clients will
do similar, for instance when streaming multiple separate contents which
it is syncing via smil. The RTSP sequence number applies to the RTSP
session on which it is carried. A proxy must handle any associated
sequence number mapping between client connections and server
connections.

So for your example:

>  
>    The interactive messages are listed as following.
>  
>    Session issued by Client A:
>    C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
>          CSeq: 111
>          Transport: RTP/AVP;multicast
>  
>    P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
>          CSeq: 333
>          Transport: RTP/AVP;multicast
>    Session issued by Client A:
>    C->P: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
>          CSeq: 222
>          Transport: RTP/AVP;multicast
>    P->S: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
>          CSeq: 444
>          Transport: RTP/AVP;multicast
>  
> 
>    Proxy will receive the following responses from server:
>    S->P: RTSP/2.0 200 OK
>          CSeq: 333
>          Server: PhonyServer/1.0
>          Date: Thu, 23 Jan 2009 15:35:06 GMT
>          Transport: RTP/AVP;multicast;
>               dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16
>          Session: 12345678
>    S->P: RTSP/2.0 200 OK
>          CSeq: 444
>          Server: PhonyServer/1.0
>          Date: Thu, 23 Jan 2009 15:35:06 GMT
>          Transport: RTP/AVP;multicast;
>               dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16
>          Session: 23456789
>  

This is not correct. If the proxy is using the same RTSP proxy<->server
connection for multiple client<->proxy connections, it must resequence
and internally track the associations. It can't just blindly pass
through the sequence numbers from it's client connections, those are
clearly not correct. So if Client A and Client B send

CA -> P:
SETUP rtsp://live.example.com/concert/audio RTSP/2.0
CSeq: 111
Transport: RTP/AVP;multicast

CB->P:
SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
CSeq: 222
Transport: RTP/AVP;multicast

The proxy must then send to the server

P->S:
SETUP rtsp://live.example.com/concert/audio RTSP/2.0
CSeq: 1
Transport: RTP/AVP;multicast

SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
CSeq: 2
Transport: RTP/AVP;multicast

and store the mappings [Client A CSeq 111 -> Server CSeq 1] and
[Client B CSeq 222 -> Server CSeq 2]

and when it receives the responses it certainly knows the correct
response for each client. Similarly if the proxy is not in pure pass
through mode and is actually handling some requests and/or inserting
some requests, it would need to adjust sequence numbers appropriately
between server and client.

Thanks,
Jamie

> In this case, RTSP proxy can not distinguish the responses, then it 
> may respond client with wrong message and induce client to join a 
> wrong mutlicast group.
>  
> Do anybody think this is an possible trap/deficiency, and RTSP should 
> try to resolve?
> Thanks.
>  
> 
> Regards
> 
> Yingjie Gu
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

From guyingjie@huawei.com  Wed Aug 12 18:26:15 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26DAA3A6864 for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 18:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.452
X-Spam-Level: 
X-Spam-Status: No, score=-0.452 tagged_above=-999 required=5 tests=[AWL=1.147,  BAYES_00=-2.599, J_BACKHAIR_56=1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BrTYOIS80MZ for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 18:26:14 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 8FF893A6CE0 for <mmusic@ietf.org>; Wed, 12 Aug 2009 18:26:13 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOA00DKGJXWUV@szxga01-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 09:25:08 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOA00IQSJXW75@szxga01-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 09:25:08 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KOA00790JXVJD@szxml06-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 09:25:08 +0800 (CST)
Date: Thu, 13 Aug 2009 09:25:07 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <4A830BC4.30301@real.com>
To: 'Jamie Gordon' <jgordon@real.com>
Message-id: <001101ca1bb4$e4d99b50$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcobfLT/+QdABTDuQIuBj0o+FKEUTwANxhgQ
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2009 01:26:15 -0000

Hi Jamie, see in line please.

Regards

Yingjie Gu

 

> -----Original Message-----
> From: Jamie Gordon [mailto:jgordon@real.com] 
> Sent: Thursday, August 13, 2009 2:37 AM
> To: Y.J. Gu
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Question about RTSP proxy
> 
> On 8/10/2009 11:04 PM, Y.J. Gu wrote:
> > Hi all,
> > In RTSP 2.0, it is permitted to transmit several client requests in 
> > one Transport Connection.
> > I think this may introduce new problems when RTSP proxy is 
> intervened, 
> > and existing RTSP can not deal with the scenario correctly.
> > The following is an example. To display the figure 
> correctly, please 
> > maximize this email window.
> 
> This has not changed from RTSP 1.0, and even some existing 
> clients will do similar, for instance when streaming multiple 
> separate contents which it is syncing via smil. The RTSP 
> sequence number applies to the RTSP session on which it is 
> carried. A proxy must handle any associated sequence number 
> mapping between client connections and server connections.
> 
> So for your example:
> 
> >  
> >    The interactive messages are listed as following.
> >  
> >    Session issued by Client A:
> >    C->P: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
> >          CSeq: 111
> >          Transport: RTP/AVP;multicast
> >  
> >    P->S: SETUP rtsp://live.example.com/concert/audio RTSP/2.0
> >          CSeq: 333
> >          Transport: RTP/AVP;multicast
> >    Session issued by Client A:
> >    C->P: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
> >          CSeq: 222
> >          Transport: RTP/AVP;multicast
> >    P->S: SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
> >          CSeq: 444
> >          Transport: RTP/AVP;multicast
> >  
> > 
> >    Proxy will receive the following responses from server:
> >    S->P: RTSP/2.0 200 OK
> >          CSeq: 333
> >          Server: PhonyServer/1.0
> >          Date: Thu, 23 Jan 2009 15:35:06 GMT
> >          Transport: RTP/AVP;multicast;
> >               dest_addr="224.2.0.1:3456"/"224.2.0.1:3457";ttl=16
> >          Session: 12345678
> >    S->P: RTSP/2.0 200 OK
> >          CSeq: 444
> >          Server: PhonyServer/1.0
> >          Date: Thu, 23 Jan 2009 15:35:06 GMT
> >          Transport: RTP/AVP;multicast;
> >               dest_addr="224.2.0.2:1234"/"224.2.0.2:1235";ttl=16
> >          Session: 23456789
> >  
> 
> This is not correct. If the proxy is using the same RTSP 
> proxy<->server connection for multiple client<->proxy 
> connections, it must resequence and internally track the 
> associations. It can't just blindly pass through the sequence 
> numbers from it's client connections, those are clearly not 
> correct. So if Client A and Client B send
> 
> CA -> P:
> SETUP rtsp://live.example.com/concert/audio RTSP/2.0
> CSeq: 111
> Transport: RTP/AVP;multicast
> 
> CB->P:
> SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
> CSeq: 222
> Transport: RTP/AVP;multicast
> 
> The proxy must then send to the server
> 
> P->S:
> SETUP rtsp://live.example.com/concert/audio RTSP/2.0
> CSeq: 1
> Transport: RTP/AVP;multicast
> 
> SETUP rtsp://live.example.com/anotherconcert/audio RTSP/2.0
> CSeq: 2
> Transport: RTP/AVP;multicast

Welll, I do resequence the client CSeq to proxy CSeq, 
For client A, CSeq is from 111 to 333
For client B, CSeq is from 222 to 444
And yes of course the proxy will store the mapping as you said. 

> and store the mappings [Client A CSeq 111 -> Server CSeq 1] 
> and [Client B CSeq 222 -> Server CSeq 2]
> 
> and when it receives the responses it certainly knows the 
> correct response for each client. Similarly if the proxy is 
> not in pure pass through mode and is actually handling some 
> requests and/or inserting some requests, it would need to 
> adjust sequence numbers appropriately between server and client.

RTSP surely can distinguish the response by CSeq. I gave other problem
statement in my following email, please check them.

> Thanks,
> Jamie
> 
> > In this case, RTSP proxy can not distinguish the responses, then it 
> > may respond client with wrong message and induce client to join a 
> > wrong mutlicast group.
> >  
> > Do anybody think this is an possible trap/deficiency, and 
> RTSP should 
> > try to resolve?
> > Thanks.
> >  
> > 
> > Regards
> > 
> > Yingjie Gu
> > 
> >  
> > 
> > 
> > 
> ----------------------------------------------------------------------
> > --
> > 
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic


From guyingjie@huawei.com  Wed Aug 12 19:24:58 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 826AF3A6CE3 for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 19:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.568
X-Spam-Level: *
X-Spam-Status: No, score=1.568 tagged_above=-999 required=5 tests=[AWL=-1.027,  BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, J_BACKHAIR_11=1, J_CHICKENPOX_64=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43KtMyEk6v2G for <mmusic@core3.amsl.com>; Wed, 12 Aug 2009 19:24:57 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 0315A3A6CCF for <mmusic@ietf.org>; Wed, 12 Aug 2009 19:24:56 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOA00HMBMHVIE@szxga04-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 10:20:19 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOA006NRMHVN7@szxga04-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 10:20:19 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KOA00HM2MHVP2@szxml04-in.huawei.com> for mmusic@ietf.org; Thu, 13 Aug 2009 10:20:19 +0800 (CST)
Date: Thu, 13 Aug 2009 10:20:18 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <A181547BA711A7428A5C5091FEF75E74AAD10F@SEA1CORPMAIL01.mediator.com>
To: 'Jaehwan Kim' <jhkim@vidiator.com>, mmusic@ietf.org
Message-id: <001801ca1bbc$9a7b8bb0$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_BbbpO31Dkd+tZJJWOkwXDQ)"
Thread-index: AcoaSZFrx3F0JjKoTPW+S2B9sWpzWgAL0zegABvK6LAACBxtQAADgmowAAOGpPAAJeencA==
Subject: Re: [MMUSIC] Question about RTSP proxy
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2009 02:24:58 -0000

This is a multi-part message in MIME format.

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

I would like to compose a draft, in order to clarify the problem clearly. I
feel that there might be other scenarios that we haven't noticed.
 

Regards

Yingjie Gu

 


  _____  

From: Jaehwan Kim [mailto:jhkim@vidiator.com] 
Sent: Wednesday, August 12, 2009 6:13 PM
To: Y.J. Gu; mmusic@ietf.org
Subject: RE: [MMUSIC] Question about RTSP proxy



Hi Yingjie,

It looks that the current 2326bis specification is not crystal clear to this
problem although we have a workaround. Then, we might introduce an
identifier which is only used between proxy and server. Probably this is why
a proprietary RTSP solution requires client driven Session ID from Describe
which is not allowed in the current specification. 

 

And two different servers mean two different TCP sessions. When I consider
non-permanent connection case, it is still no issue. Therefore, this issue
could be limited only to the case you use one TCP connection for two
different RTSP sessions for the same resource but this is not common(case
2/). Or maybe you could provide some usecases?

 

Regards,

Jaehwan

 

From: Y.J. Gu [mailto:guyingjie@huawei.com] 
Sent: Wednesday, August 12, 2009 3:34 PM
To: Jaehwan Kim; mmusic@ietf.org
Subject: RE: [MMUSIC] Question about RTSP proxy

 

Hi Jaehwan

well, for the above 2 examples, I am considering the second case. Two
requests/responses on one TCP connection.

By the latest above example, I meant when the two SETUP requests for same
resource transmitted through one TCP connection, server will have difficult
to differentiate them. 

By the example in my first email, I meant when two responses sent by one
server through one TCP connection to Proxy, Proxy 

may have difficult to differentiate them.

 

Surely, RTSP proxy, when implemented, can handle the problem by compromised
solutions, e.g. CSeq. While proxy has to guarantee to generate different
initial CSeq for each session by, e.g. ,comparing the current CSeq with
those generated before. How many concurrent sessions can a proxy support,
maybe 10000, then comparing CSeq would be a huge burden, because that will
be a large order of magnitude. 

 

Here is another assumption. Proxy send 2 RTSP requests to 2 servers, but,
unfortunately,  the 2 servers response the same session ID, by what mean
will the proxy handle the following messages of the 2 sessions?  Maybe take
session ID and TCP connection together into consideration. Proxy has to do
this every time it receive a message from the servers. That will be a huge
workload. Besides, that will tie RTSP closely toTransport protocol, however
RTSP 2.0 is in no way tied to a Transport protocol according to RFC2326.

 

Basically, I think the existing solutions to proxy can work but are very
much compromised and result in complexity. We should find a easy and  clear
way to resolve the problem.  

 

BTW,Multicast is just an example, the problem doesn't limit to multicast.

 

 

 

 

Regards

Yingjie Gu

 

 


  _____  


From: Jaehwan Kim [mailto:jhkim@vidiator.com] 
Sent: Wednesday, August 12, 2009 1:09 PM
To: Y.J. Gu; mmusic@ietf.org
Subject: RE: [MMUSIC] Question about RTSP proxy

Hi Yingjie,

On P<->S side, there would be two cases:

1/ using two different TCP sessions(typical case): Although the same cseq is
found, Proxy should be able to handle different TCP sessions. And Proxy
should map two different Client requests with these.

2/ using just one TCP session for two different RTSP sessions: Simple
solution is to manage cseq well because proxy assign the value.

 

Which one do you consider?

 

And you may consider also non-permanent connection case, but still proxy
could manage them and deliver Session ID generated from the server from my
understanding.

 

Anyway it looks not multicast issue. And there are already many
off-the-shelf RTSP proxy handle this matter without any problem.

 

Regards,

Jaehwan

 

 

 


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = 
"urn:schemas-microsoft-com:vml" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word" xmlns:x = 
"urn:schemas-microsoft-com:office:excel" xmlns:p = 
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a = 
"urn:schemas-microsoft-com:office:access" xmlns:dt = 
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = 
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = 
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = 
"urn:schemas-microsoft-com:office:publisher" xmlns:ss = 
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = 
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = 
"urn:schemas-microsoft-com:office:odc" xmlns:oa = 
"urn:schemas-microsoft-com:office:activation" xmlns:html = 
"http://www.w3.org/TR/REC-html40" xmlns:q = 
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc = 
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl = 
"http://schemas.microsoft.com/repl/" xmlns:mt = 
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = 
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda = 
"http://www.passport.com/NameSpace.xsd" xmlns:ois = 
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = 
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = 
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = 
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = 
"http://schemas.microsoft.com/data/udc" xmlns:xsd = 
"http://www.w3.org/2001/XMLSchema" xmlns:sub = 
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = 
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp = 
"http://schemas.microsoft.com/sharepoint/" xmlns:sps = 
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = 
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = 
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = 
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = 
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = 
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = 
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = 
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = 
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = 
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = 
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = 
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = 
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = 
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = 
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = 
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = 
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" 
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR><!--[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:SimSun;
	panose-1:2 1 6 0 3 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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{mso-style-priority:99;
	mso-style-link:"\C778\C0AC\B9D0 Char";
	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","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.Char
	{mso-style-name:"\C778\C0AC\B9D0 Char";
	mso-style-priority:99;
	mso-style-link:\C778\C0AC\B9D0;
	font-family:"Malgun Gothic";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Malgun Gothic";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Malgun Gothic";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Malgun Gothic";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=KO vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=894441702-13082009><FONT color=#0000ff 
size=5>I would like to compose a draft, in order to clarify the problem clearly. 
I feel that there might be other scenarios that we haven't 
noticed.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV align=left><FONT size=2>
<P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial"></SPAN><SPAN 
lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" align=left><SPAN 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: &#23435;&#20307;; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial"><FONT 
size=4>Regards</FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"></FONT><SPAN lang=EN-US 
style="FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt"><FONT 
size=4>Yingjie Gu</FONT></SPAN></P></DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader lang=zh-cn dir=ltr align=left>
  <HR tabIndex=-1>
  <FONT face=Tahoma size=2><B>From:</B> Jaehwan Kim [mailto:jhkim@vidiator.com] 
  <BR><B>Sent:</B> Wednesday, August 12, 2009 6:13 PM<BR><B>To:</B> Y.J. Gu; 
  mmusic@ietf.org<BR><B>Subject:</B> RE: [MMUSIC] Question about RTSP 
  proxy<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Hi 
  Yingjie,<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">It looks 
  that the current 2326bis specification is not crystal clear to this problem 
  although we have a workaround. Then, we might introduce an identifier which is 
  only used between proxy and server. Probably this is why a proprietary RTSP 
  solution requires client driven Session ID from Describe which is not allowed 
  in the current specification. <o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">And two 
  different servers mean two different TCP sessions. When I consider 
  non-permanent connection case, it is still no issue. Therefore, this issue 
  could be limited only to the case you use one TCP connection for two different 
  RTSP sessions for the same resource but this is not common(case 2/). Or maybe 
  you could provide some usecases?<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Regards,<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Jaehwan<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV>
  <DIV 
  style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=MsoNormal><B><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN 
  lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Y.J. 
  Gu [mailto:guyingjie@huawei.com] <BR><B>Sent:</B> Wednesday, August 12, 2009 
  3:34 PM<BR><B>To:</B> Jaehwan Kim; mmusic@ietf.org<BR><B>Subject:</B> RE: 
  [MMUSIC] Question about RTSP proxy<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=MsoNormal><SPAN lang=EN-US><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt; COLOR: blue">Hi 
  Jaehwan</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 18pt; COLOR: blue">well,&nbsp;for the above 2 
  examples,&nbsp;I am considering the second case. Two requests/responses on one 
  TCP connection.</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 18pt; COLOR: blue">By&nbsp;the latest above example, I meant 
  when the two SETUP requests for same resource&nbsp;transmitted through one TCP 
  connection, server will have difficult to differentiate them. </SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt; COLOR: blue">By 
  the example in my first email, I meant when two responses sent by one server 
  through one TCP connection to Proxy, Proxy </SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt; COLOR: blue">may 
  have difficult to differentiate them.</SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 18pt; COLOR: blue">Surely, RTSP proxy, when implemented, can 
  handle the problem by compromised solutions, e.g. CSeq. While proxy has to 
  guarantee to&nbsp;generate different initial CSeq for each session by, e.g. 
  ,comparing the current CSeq with those generated before.&nbsp;How 
  many&nbsp;concurrent sessions can a proxy support, maybe 10000, then comparing 
  CSeq would be a huge burden, because that will be a large order of magnitude. 
  </SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US style="FONT-SIZE: 18pt; COLOR: blue">Here 
  is another assumption. Proxy send 2 RTSP requests to 2 servers, but, 
  unfortunately,&nbsp; the 2 servers response the same session ID,&nbsp;by what 
  mean&nbsp;will the proxy handle the following messages of the 2 
  sessions?&nbsp; Maybe take session ID and TCP connection together into 
  consideration. Proxy has to do this every time it receive a message from the 
  servers. That will be a huge workload. Besides, that will tie RTSP closely 
  toTransport protocol, however RTSP 2.0 is in no way tied to a Transport 
  protocol according to RFC2326.</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 18pt; COLOR: blue">Basically, I think the existing solutions 
  to proxy can work but are&nbsp;very much compromised and result in complexity. 
  We should find a easy and &nbsp;clear way to resolve the problem.&nbsp; 
  </SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 18pt; COLOR: blue; FONT-FAMILY: 'SimSun','serif'">BTW,Multicast 
  is just an example, the problem doesn't limit to multicast.</SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P>
  <DIV>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
  <P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt"><SPAN 
  lang=EN-US><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 13.5pt; FONT-FAMILY: 'Arial','sans-serif'">Regards</SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 13.5pt; FONT-FAMILY: 'Arial','sans-serif'">Yingjie 
  Gu</SPAN><SPAN lang=EN-US><o:p></o:p></SPAN></P>
  <DIV>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
  <P class=MsoNormal><SPAN lang=EN-US><o:p>&nbsp;</o:p></SPAN></P>
  <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN lang=EN-US>
  <HR align=center width="100%" SIZE=2>
  </SPAN></DIV>
  <P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN 
  lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> 
  Jaehwan Kim [mailto:jhkim@vidiator.com] <BR><B>Sent:</B> Wednesday, August 12, 
  2009 1:09 PM<BR><B>To:</B> Y.J. Gu; mmusic@ietf.org<BR><B>Subject:</B> RE: 
  [MMUSIC] Question about RTSP proxy</SPAN><SPAN 
  lang=EN-US><o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Hi 
  Yingjie,<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">On 
  P&lt;-&gt;S side, there would be two cases:<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">1/ using 
  two different TCP sessions(typical case): Although the same cseq is found, 
  Proxy should be able to handle different TCP sessions. And Proxy should map 
  two different Client requests with these.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">2/ using 
  just one TCP session for two different RTSP sessions: Simple solution is to 
  manage cseq well because proxy assign the value.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Which 
  one do you consider?<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">And you 
  may consider also non-permanent connection case, but still proxy could manage 
  them and deliver Session ID generated from the server from my 
  understanding.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Anyway 
  it looks not multicast issue. And there are already many off-the-shelf RTSP 
  proxy handle this matter without any problem.<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Regards,<o:p></o:p></SPAN></P>
  <P class=MsoNormal><SPAN lang=EN-US 
  style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Malgun Gothic'">Jaehwan<o:p></o:p></SPAN></P>
  <DIV>
  <P class=MsoNormal><SPAN lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV>
  <P class=MsoSalutation style="MARGIN: 0cm 0cm 0pt"><SPAN 
  lang=EN-US><o:p>&nbsp;</o:p></SPAN></P>
  <P class=MsoNormal><SPAN 
lang=EN-US>&nbsp;<o:p></o:p></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_BbbpO31Dkd+tZJJWOkwXDQ)--

From shin@cyb.softfront.co.jp  Tue Aug 18 21:05:03 2009
Return-Path: <shin@cyb.softfront.co.jp>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4745C3A6890 for <mmusic@core3.amsl.com>; Tue, 18 Aug 2009 21:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.398
X-Spam-Level: ****
X-Spam-Status: No, score=4.398 tagged_above=-999 required=5 tests=[AWL=0.894,  BAYES_40=-0.185, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265, RCVD_IN_SORBS_DUL=0.877, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bdYEtvcmrFE5 for <mmusic@core3.amsl.com>; Tue, 18 Aug 2009 21:05:02 -0700 (PDT)
Received: from uiwd.iwavedesign.com (cyb.softfront.co.jp [203.191.246.104]) by core3.amsl.com (Postfix) with ESMTP id 903BE3A682E for <mmusic@ietf.org>; Tue, 18 Aug 2009 21:05:02 -0700 (PDT)
Received: from cyb.softfront.co.jp (rt1.softfront.co.jp [221.186.247.166]) by uiwd.iwavedesign.com (Postfix) with ESMTP id AC534640DF for <mmusic@ietf.org>; Wed, 19 Aug 2009 13:04:59 +0900 (JST)
From: shin <shin@softfront.co.jp>
To: mmusic@ietf.org
Date: Wed, 19 Aug 2009 13:05:02 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: HidemaruMail 5.19 (WinNT,501)
Message-Id: <5ACA20823A105Dshin@softfront.co.jp>
Subject: [MMUSIC] SDP media type
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 04:09:53 -0000

Hi all,

I have one little question regarding the media type of SDP.


RFC4566 obsoletes RFC2327 and describes:
8.2.1.  Media Types ("media")
   The set of media types is intended to be small and SHOULD NOT be
   extended except under rare circumstances.  The same rules should
   apply for media names as for top-level media content types, and where
   possible the same name should be registered for SDP as for MIME.  For
   media other than existing top-level media content types, a Standards
   Track RFC MUST be produced for a new top-level content type to be
   registered, and the registration MUST provide good justification why
   no existing media name is appropriate (the "Standards Action" policy
   of RFC 2434 [8].

   This memo registers the media types "audio", "video", "text",
   "application", and "message".


"image" is registered with IANA as MIME media Types.
But it is excluded from the above five media types.

Is it necessary for "image" to be registered as SDP media types ?

From guyingjie@huawei.com  Wed Aug 19 20:58:18 2009
Return-Path: <guyingjie@huawei.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DE093A6929 for <mmusic@core3.amsl.com>; Wed, 19 Aug 2009 20:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.054
X-Spam-Level: 
X-Spam-Status: No, score=0.054 tagged_above=-999 required=5 tests=[AWL=0.548,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5lsuIvbYuzDL for <mmusic@core3.amsl.com>; Wed, 19 Aug 2009 20:58:17 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id DA9813A697D for <mmusic@ietf.org>; Wed, 19 Aug 2009 20:58:16 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KON008BLPOZ2O@szxga04-in.huawei.com> for mmusic@ietf.org; Thu, 20 Aug 2009 11:58:12 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KON0094APOZ1R@szxga04-in.huawei.com> for mmusic@ietf.org; Thu, 20 Aug 2009 11:58:11 +0800 (CST)
Received: from g00107907 ([10.164.12.64]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KON00EK0POZQB@szxml06-in.huawei.com> for mmusic@ietf.org; Thu, 20 Aug 2009 11:58:11 +0800 (CST)
Date: Thu, 20 Aug 2009 11:58:10 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <A181547BA711A7428A5C5091FEF75E74AAD10F@SEA1CORPMAIL01.mediator.com>
To: schulzrinne@cs.columbia.edu, mmusic@ietf.org
Message-id: <007001ca214a$6ef4e480$400ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_27C6sqGX2DrSWTFVb8BGsQ)"
Thread-index: AcoaSZFrx3F0JjKoTPW+S2B9sWpzWgAL0zegABvK6LAACBxtQAADgmowAAOGpPABiLcKEA==
Subject: [MMUSIC] RFC2326bis-22, Section 16.19 need clarification.
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2009 03:58:18 -0000

This is a multi-part message in MIME format.

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

 In RFC2326bis-22
 16.19.  CSeq
 
   The CSeq general-header field specifies the sequence number for an
   RTSP request-response pair.  This field MUST be present in all
   requests and responses.  For every RTSP request containing the given
   sequence number, the corresponding response will have the same
   number.  Any retransmitted request MUST contain the same sequence
   number as the original (i.e. the sequence number is not incremented
   for retransmissions of the same request).  For each new RTSP request
   the CSeq value MUST be incremented by one.  The initial sequence
   number MAY be any number, however it is RECOMMENDED to start at 0.
   Each sequence number series is unique between each requester and
   responder, i.e. the client has one series for its request to a server
   and the server has another when sending request to the client.  Each
   requester and responder is identified with its network address.
 
   Proxies that aggregate several sessions on the same transport will
   regularly need to renumber the CSeq header field in requests and
   responses to fulfill the rules for the header.
 
I am not very clear about the colored words.
 For each new RTSP request
   the CSeq value MUST be incremented by one.  
When Proxy aggregate serveral sessions, it can be understanded in different
way:
1) Without regard of different sessions, proxy increase the CSeq by one for
each request it transmits.
     +-----+           +-----------+
+----------+
      | C1  | ---------|   proxy   |      C1 setup, CSeq=1  |  server  |
     +-----+          /+-----------+    C1 play,   CSeq=2 +----------+
                        /                          C2 setup, CSeq=3 
     +-----+    /                              C1 pause, CSeq=4
      | C2  |  /
     +-----+
2) CSeq is incremented by one for each request of a particular session. 
     +-----+           +-----------+
+----------+
      | C1  | ---------|   proxy   |      C1 setup, CSeq=1  |  server  |
     +-----+          /+-----------+    C1 play,   CSeq=2 +----------+
                        /                          C2 setup, CSeq=101 
     +-----+    /                              C1 pause, CSeq=3
      | C2  |  /                                 C2 play,   CSeq=102
     +-----+
I guess it should be 2), but I am not sure, 'cause there can be various
explanations.
Each sequence number series is unique between each requester and
   responder, i.e. the client has one series for its request to a server
   and the server has another when sending request to the client.
What does unique mean? Are {0,1,2,3} and {1,2,3,4} unique, or {0,1,2,3} and
{101,102,103,104} unique?
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = 
"urn:schemas-microsoft-com:vml" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word" xmlns:x = 
"urn:schemas-microsoft-com:office:excel" xmlns:p = 
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a = 
"urn:schemas-microsoft-com:office:access" xmlns:dt = 
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = 
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = 
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = 
"urn:schemas-microsoft-com:office:publisher" xmlns:ss = 
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = 
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = 
"urn:schemas-microsoft-com:office:odc" xmlns:oa = 
"urn:schemas-microsoft-com:office:activation" xmlns:html = 
"http://www.w3.org/TR/REC-html40" xmlns:q = 
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc = 
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl = 
"http://schemas.microsoft.com/repl/" xmlns:mt = 
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = 
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda = 
"http://www.passport.com/NameSpace.xsd" xmlns:ois = 
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = 
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = 
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = 
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = 
"http://schemas.microsoft.com/data/udc" xmlns:xsd = 
"http://www.w3.org/2001/XMLSchema" xmlns:sub = 
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = 
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp = 
"http://schemas.microsoft.com/sharepoint/" xmlns:sps = 
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = 
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = 
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = 
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = 
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = 
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = 
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = 
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = 
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = 
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = 
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = 
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = 
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = 
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = 
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = 
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = 
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" 
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR><!--[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:SimSun;
	panose-1:2 1 6 0 3 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:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{mso-style-priority:99;
	mso-style-link:"\C778\C0AC\B9D0 Char";
	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","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.Char
	{mso-style-name:"\C778\C0AC\B9D0 Char";
	mso-style-priority:99;
	mso-style-link:\C778\C0AC\B9D0;
	font-family:"Malgun Gothic";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Malgun Gothic";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Malgun Gothic";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Malgun Gothic";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=KO vLink=purple link=blue>
<DIV><FONT size=4><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;In RFC2326bis-22</FONT></SPAN></FONT></DIV>
<DIV><FONT size=4><SPAN class=012043703-20082009>&nbsp;</SPAN>16.19.&nbsp; 
CSeq</FONT></DIV>
<DIV><FONT size=4></FONT>&nbsp;</DIV>
<DIV><FONT size=4>&nbsp;&nbsp; The CSeq general-header field specifies the 
sequence number for an<BR>&nbsp;&nbsp; RTSP request-response pair.&nbsp; This 
field MUST be present in all<BR>&nbsp;&nbsp; requests and responses.&nbsp; For 
every RTSP request containing the given<BR>&nbsp;&nbsp; sequence number, the 
corresponding response will have the same<BR>&nbsp;&nbsp; number.&nbsp; Any 
retransmitted request MUST contain the same sequence<BR>&nbsp;&nbsp; number as 
the original (i.e. the sequence number is not incremented<BR>&nbsp;&nbsp; for 
retransmissions of the same request).&nbsp;<FONT color=#800000 size=5> For each 
new RTSP request<BR>&nbsp;&nbsp; the CSeq value MUST be incremented by 
one.</FONT>&nbsp; The initial sequence<BR>&nbsp;&nbsp; number MAY be any number, 
however it is RECOMMENDED to start at 0.<BR>&nbsp;&nbsp;<FONT color=#800000 
size=5> Each sequence number series is unique between each requester 
and<BR>&nbsp;&nbsp; responder, i.e. the client has one series for its request to 
a server<BR>&nbsp;&nbsp; and the server has another when sending request to the 
client.</FONT>&nbsp; Each<BR>&nbsp;&nbsp; requester and responder is identified 
with its network address.</FONT></DIV>
<DIV><FONT size=4></FONT>&nbsp;</DIV>
<DIV><FONT size=4>&nbsp;&nbsp; Proxies that aggregate several sessions on the 
same transport will<BR>&nbsp;&nbsp; regularly need to renumber the CSeq header 
field in requests and<BR>&nbsp;&nbsp; responses to fulfill the rules for the 
header.<BR></FONT><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>I am not very 
clear about the colored words.</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009>&nbsp;<FONT color=#800000 size=5>For each 
new RTSP request<BR>&nbsp;&nbsp; the CSeq value MUST be incremented by 
one.</FONT><FONT size=4>&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>When Proxy 
aggregate serveral sessions, it can be understanded in different 
way:</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>1) Without regard 
of different sessions, proxy increase the CSeq by one for each request it 
transmits.</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
+----------+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 
C1&nbsp;&nbsp;|&nbsp;---------|&nbsp;&nbsp; proxy&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C1 setup, CSeq=1&nbsp; |&nbsp; server&nbsp; 
|</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp; 
+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/+-----------+&nbsp;&nbsp;&nbsp;&nbsp;C1 
play,&nbsp;&nbsp; CSeq=2&nbsp;+----------+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C2 
setup, CSeq=3&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
C1 pause, CSeq=4</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | C2&nbsp; |&nbsp; /</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp; +-----+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>2) CSeq is 
incremented by one for each request of a&nbsp;particular 
session.&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
+----------+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 
C1&nbsp;&nbsp;|&nbsp;---------|&nbsp;&nbsp; proxy&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C1 setup, CSeq=1&nbsp; |&nbsp; server&nbsp; 
|</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp; 
+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/+-----------+&nbsp;&nbsp;&nbsp;&nbsp;C1 
play,&nbsp;&nbsp; CSeq=2&nbsp;+----------+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C2 
setup, CSeq=101&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
C1 pause, CSeq=3</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | C2&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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
C2 play,&nbsp;&nbsp; CSeq=102</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5>&nbsp;&nbsp;&nbsp;&nbsp; +-----+</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009>I guess it should be 2), but I am not sure, 
'cause there can be various explanations.</SPAN></DIV></FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#800000 size=5>Each sequence 
number series is unique between each requester and<BR>&nbsp;&nbsp; responder, 
i.e. the client has one series for its request to a server<BR>&nbsp;&nbsp; and 
the server has another when sending request to the client.</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff size=5>What does unique 
mean?&nbsp;Are {0,1,2,3} and {1,2,3,4} unique, or {0,1,2,3} and 
{101,102,103,104} unique?</FONT></SPAN></DIV>
<DIV><SPAN class=012043703-20082009><FONT color=#0000ff 
size=5></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_27C6sqGX2DrSWTFVb8BGsQ)--

From shin@softfront.co.jp  Fri Aug 21 04:41:07 2009
Return-Path: <shin@softfront.co.jp>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 742B93A6B58 for <mmusic@core3.amsl.com>; Fri, 21 Aug 2009 04:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.502
X-Spam-Level: ****
X-Spam-Status: No, score=4.502 tagged_above=-999 required=5 tests=[AWL=0.212,  BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HOST_EQ_JP=1.265, J_CHICKENPOX_15=0.6, RCVD_IN_SORBS_DUL=0.877, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zD9eRpwINg9f for <mmusic@core3.amsl.com>; Fri, 21 Aug 2009 04:41:06 -0700 (PDT)
Received: from uiwd.iwavedesign.com (cyb.softfront.co.jp [203.191.246.104]) by core3.amsl.com (Postfix) with ESMTP id 712DD3A6AC9 for <mmusic@ietf.org>; Fri, 21 Aug 2009 04:41:05 -0700 (PDT)
Received: from softfront.co.jp (rt1.softfront.co.jp [221.186.247.166]) by uiwd.iwavedesign.com (Postfix) with SMTP id 8C3CF640DF for <mmusic@ietf.org>; Fri, 21 Aug 2009 20:41:09 +0900 (JST)
From: OKUMURA Shinji <shin@softfront.co.jp>
To: mmusic@ietf.org
Date: Fri, 21 Aug 2009 20:41:08 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: HidemaruMail 5.19 (WinNT,501)
Message-Id: <73CA225445F8A2shin@softfront.co.jp>
Subject: [MMUSIC] SDP extensions for Explicit Asymmetric RTP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 11:41:07 -0000

Hi all,

I apologize if this has already been discussed.

I am thinking a little about "SDP extensions for Explicit Asymmetric RTP".
It is very simple extensions as below.

   m=audio 62986 RTP/AVP 0 4 18
   a=rtpmap:0 PCMU/8000
   a=rtpmap:4 G723/8000
   a=rtpmap:18 G729/8000
   a=fmtp:4 sendonly
   a=fmtp:18 recvonly
   a=fmtp:4 ptime:30
   a=fmtp:18 ptime:20

Any thoughts on this extensions?

Regards,
Shinji

From ingemar.s.johansson@ericsson.com  Fri Aug 21 06:05:43 2009
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AAA33A6845 for <mmusic@core3.amsl.com>; Fri, 21 Aug 2009 06:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.268
X-Spam-Level: 
X-Spam-Status: No, score=-3.268 tagged_above=-999 required=5 tests=[AWL=-1.619, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5x6RxaJLEu76 for <mmusic@core3.amsl.com>; Fri, 21 Aug 2009 06:05:42 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id EF4123A6B52 for <mmusic@ietf.org>; Fri, 21 Aug 2009 06:05:41 -0700 (PDT)
X-AuditID: c1b4fb24-b7c01ae00000498b-29-4a8e9baaff21
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Brightmail Gateway) with SMTP id 18.39.18827.AAB9E8A4; Fri, 21 Aug 2009 15:05:46 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 21 Aug 2009 15:04:47 +0200
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
Date: Fri, 21 Aug 2009 15:04:46 +0200
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C01AADD0D@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re : SDP extensions for Explicit Asymmetric RTP
Thread-Index: AcoiX/UT+ia/RlolRpGuEWxftU71Sw==
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: <shin@softfront.co.jp>, <mmusic@ietf.org>
X-OriginalArrivalTime: 21 Aug 2009 13:04:47.0433 (UTC) FILETIME=[F5C95390:01CA225F]
X-Brightmail-Tracker: AAAAAA==
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: [MMUSIC] Re : SDP extensions for Explicit Asymmetric RTP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 13:05:43 -0000

Hi

While the proposal below is very tempning it is not valid according to =
RFC2327. The only way to solve asymmetry in a general fashion is to =
define several media lines.

I sketched on a general solution to asymmetry issues some time ago
http://tools.ietf.org/html/draft-johansson-mmusic-asymmetric-media-00
The whole thing was meant to be a partly backwards compatible extension =
to SDPCapNeg, the interest was however quite low. Still I believe that =
questions like these will show up more in the future and then it would =
be good to have a generic solution.

Regards
Ingemar


>Hi all,

>I apologize if this has already been discussed.

>I am thinking a little about "SDP extensions for Explicit Asymmetric =
RTP".
>It is very simple extensions as below.

>   m=3Daudio 62986 RTP/AVP 0 4 18
>   a=3Drtpmap:0 PCMU/8000
>   a=3Drtpmap:4 G723/8000
>   a=3Drtpmap:18 G729/8000
>   a=3Dfmtp:4 sendonly
>   a=3Dfmtp:18 recvonly
>   a=3Dfmtp:4 ptime:30
>   a=3Dfmtp:18 ptime:20

>Any thoughts on this extensions?

>Regards,
>Shinji

*******************************************=20
Ingemar Johansson=20
Senior Research Engineer, IETF "nethead"=20
EAB/TVK - Multimedia Technologies=20
Ericsson Research Ericsson AB=20
Box 920 S-971 28 Lule=E5, Sweden=20
Tel: +46 (0)10 7143042=20
ECN: 852-43042=20
ECC: 852-19042
Mobile: +46 (0)730 783289=20
Visit http://labs.ericsson.com !
*******************************************=20

From jouni.maenpaa@ericsson.com  Mon Aug 24 04:36:31 2009
Return-Path: <jouni.maenpaa@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E34BB28C1A9 for <mmusic@core3.amsl.com>; Mon, 24 Aug 2009 04:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkI95LkkgKiW for <mmusic@core3.amsl.com>; Mon, 24 Aug 2009 04:36:31 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id A79A028C1AB for <mmusic@ietf.org>; Mon, 24 Aug 2009 04:36:30 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b24ae000003bbc-25-4a927b43e75f
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id B6.8D.15292.34B729A4; Mon, 24 Aug 2009 13:36:35 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 24 Aug 2009 13:36:10 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 24 Aug 2009 13:36:10 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id D4AFA24DC; Mon, 24 Aug 2009 14:36:09 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A06B121A0F; Mon, 24 Aug 2009 14:36:09 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 59FA9219CF; Mon, 24 Aug 2009 14:36:09 +0300 (EEST)
Message-ID: <4A927B2A.9080102@ericsson.com>
Date: Mon, 24 Aug 2009 14:36:10 +0300
From: =?ISO-8859-1?Q?Jouni_M=E4enp=E4=E4?= <jouni.maenpaa@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Tom Hiller <tomhiller@alcatel-lucent.com>
References: <4A79D76F.40503@alcatel-lucent.com>
In-Reply-To: <4A79D76F.40503@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 24 Aug 2009 11:36:10.0166 (UTC) FILETIME=[13B00560:01CA24AF]
X-Brightmail-Tracker: AAAAAA==
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] "SIP-SDP Overlap with RTSP" and OMA
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2009 11:36:32 -0000

Hi,

> In OMA we had discussed using SIP to signal the establishment of an
> RTSP session, bypassing the RTSP SETUP as in this draft, and we did
> not go that direction.

Just wanted to point out that at least ETSI TISPAN defines a model in
which SIP/SDP is used to establish a control channel for RTSP. They
define two alternatives, one of which bypasses the RTSP SETUP. The other
alternative uses SETUP and TEARDOWN.

Regards,
Jouni

Tom Hiller wrote:
> Hello,
> 
> Last week at MMUSIC, the last slide of the presentation "SIP-SDP Overlap
> with RTSP" associated with "draft-lindquist-mmusic-sip-rtsp-00.txt",
> which involves bypassing the RTSP SETUP and DESCRIBE requests, suggests
> that this direction is on-going work in OMA, i.e.,:
> 
>> Ongoing work in other standard forums (ETSI TISPAN, 3GPP, OIPF, OMA, etc)
> 
> However, it is not the case.  In OMA we had discussed using SIP to
> signal the establishment of an RTSP session, bypassing the RTSP SETUP as
> in this draft, and we did not go that direction. Main reasons were that
> we wanted to be compliant with existing RTSP implementations and with
> RTSP 2.0 going forward.
> 
> Thanks.
> 
> 
>  - Tom
> 
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From jouni.maenpaa@ericsson.com  Mon Aug 24 05:37:52 2009
Return-Path: <jouni.maenpaa@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4E483A6DC0 for <mmusic@core3.amsl.com>; Mon, 24 Aug 2009 05:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdlLE1qC-K+M for <mmusic@core3.amsl.com>; Mon, 24 Aug 2009 05:37:51 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 6B8B13A69B2 for <mmusic@ietf.org>; Mon, 24 Aug 2009 05:37:51 -0700 (PDT)
X-AuditID: c1b4fb24-b7c01ae00000498b-30-4a9289a3396f
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Brightmail Gateway) with SMTP id 2F.82.18827.3A9829A4; Mon, 24 Aug 2009 14:37:56 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 24 Aug 2009 14:37:15 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 24 Aug 2009 14:37:15 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 5307024DC; Mon, 24 Aug 2009 15:37:14 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 1E39421A0F; Mon, 24 Aug 2009 15:37:14 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id C2B99219CB; Mon, 24 Aug 2009 15:37:13 +0300 (EEST)
Message-ID: <4A92897B.1000209@ericsson.com>
Date: Mon, 24 Aug 2009 15:37:15 +0300
From: =?ISO-8859-1?Q?Jouni_M=E4enp=E4=E4?= <jouni.maenpaa@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
References: <A0EC3C02-523E-480F-BCE4-FDAB64F51675@cisco.com>
In-Reply-To: <A0EC3C02-523E-480F-BCE4-FDAB64F51675@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 24 Aug 2009 12:37:15.0179 (UTC) FILETIME=[9C349FB0:01CA24B7]
X-Brightmail-Tracker: AAAAAA==
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Quick written version of the taxonomy of alternatives I	mentioned at the mic at the end of the SIP/RTSP discussion
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2009 12:37:52 -0000

Hi David,

> Since it seems the WG didn't sow much support for gluing the existing
> SIP and RTCP protocols together as proposed in the sip-rtsp draft, I
> offered three alternatives that might represent a decent technical way
> forward and that meet the same (technical) goals as articulated in the
> draft. 

If I recall correctly, there was no indication during the MMUSIC meeting
that the WG wouldn't support "gluing" SIP and RTSP together. The
discussion focused entirely on whether the WG would be interested in
working on the topic of interaction between the session establishment
and content control protocols (using the terminology defined in the
draft) and not on the technical details. Therefore, I would consider the
use of SIP/SDP to establish a control channel for RTSP as one further
possible way forward along with the three alternatives you are
proposing. More comments below.

Regards,
Jouni

> They clearly don't meet the goal of trying to use SIP and RTSP
> "as-is".
> 
> 1. Do a "system reset" on the RTSPv2 specification in order to make it
> capable of being used in the same overall signaling architecture the
> proponents today use SIP for (e.g. IMS environments). This entails
> giving up on full backward compatibility with RTSP v1 (which we don't
> have in practice anyway, and we have no RTSPv2 deployment yet to worry
> much about). We would re-cast RTSPv2 to use SDP offer-answer and ICE
> exactly as they are used by SIP, instead of the hybrid media description
> used in the current RTSPv2 specification. We could also import the
> P-header extension set to get the same IMS features for RTSP as we have
> for SIP. This would preserve the existing RTSP addressing model, its
> media source selection model, and its failover model, none of which are
> straightforward with SIP.

I agree with the comments that Rémi Denis-Courmont sent earlier;
modifying RTSPv2 to use SDP offer/answer wouldn't probably be the best
way forward from the implementation point of view.

> 2. Design a new in-session control protocol for the media servers to
> give SIP sessions the same media control capabilities that exist in RTSP
> (e.g. play/pause/ff etc.). This would be negotiated with SDP offer
> answer just like the media itself and other in-session control schemes
> like floor control in conferences.

The risk with this alternative is that we would end up re-specifying
much of what has already been specified for RTSP in the new in-session
control protocol.

> 3. Adopt MRCPv2 as an in-session media control protocol. MRCPv2 arguably
> has EVERYTHING needed - play, pause, scale, skip, etc. and is already
> fully integrated with SIP and deployed enough to have confidence that it
> will glue together correctly. The disadvantage is the MRCPv2 is gross
> overkill for the simple media control problem. 

I tend to agree with you in that the use of MRCPv2 would probably be an
overkill.

> It might be possible to
> define a minimal subset or "profile" that would be light weight, but I
> haven't even begun to think through the details to see if this would be
> easy or hard.
> 
> As an designer/implementer of both media servers and embedded streaming
> media clients, I find any of these more attractive than trying to glue
> SIP and RTSP together using interworking, state machine tricks, etc.
> 
> Thanks for listening,
> 
> DaveO.
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 


From Jim.Kleck@8x8.com  Fri Aug 28 10:46:31 2009
Return-Path: <Jim.Kleck@8x8.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B0653A6E65 for <mmusic@core3.amsl.com>; Fri, 28 Aug 2009 10:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.471
X-Spam-Level: 
X-Spam-Status: No, score=-0.471 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_05=-1.11, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QfHEzTEOGbK for <mmusic@core3.amsl.com>; Fri, 28 Aug 2009 10:46:30 -0700 (PDT)
Received: from mailx.8x8.com (ns25.8x8.com [192.84.19.225]) by core3.amsl.com (Postfix) with ESMTP id 600943A6E59 for <mmusic@ietf.org>; Fri, 28 Aug 2009 10:46:30 -0700 (PDT)
Received: from [10.0.2.15] (192.168.84.42) by 8X8EXCH01.8x8.com (192.168.84.92) with Microsoft SMTP Server id 8.1.336.0; Fri, 28 Aug 2009 10:46:37 -0700
Message-ID: <4A9817FC.6070408@8x8.com>
Date: Fri, 28 Aug 2009 10:46:36 -0700
From: Jim Kleck <jimk@8x8.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081030 Iceape/1.1.13 (Debian-1.1.13-1)
MIME-Version: 1.0
To: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC]  draft-ietf-mmusic-ice-19 question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2009 17:46:31 -0000

In looking at draft-ietf-mmusic-ice-19, we have run into a
point of confusion. Our understanding of the draft is that all
local candidates for a particular component for a mediastream
should use the same host IP Addr & port for gathering candidates
and for sending and receiving connectivity checks: section  4.1.1.2
says:

The agent next pairs each host candidate with the STUN or TURN server
    with which it is configured or has discovered by some means.

and:

The result is a set of pairs of host candidates with STUN or TURN
    servers.


However, section 7.2.1.4 (which deals with the ICE agent processing
a received Binding Request) states:

    Next, the agent constructs a pair whose local candidate is equal to
    the transport address on which the STUN request was received, and a
    remote candidate equal to the source transport address where the
    request came from (which may be peer-reflexive remote candidate that
    was just learned).


If all local candidates for a component have the same host IPaddr:port,
how can the local agent determine which transport address the remote
agent sent the request to (which I assume is the first transport address
referenced in the 7.2.1.4 quote from the draft)? I dont see anything in
the STUN Binding Request pkt which identifies the target candidate,
nor does the IPaddr:port the request was received on identify the target
candidate. Or does the local agent actually need a different host IPaddr
and port for each local transport address?

James Kleck
8x8, Inc.




From Jim.Kleck@8x8.com  Mon Aug 31 11:05:11 2009
Return-Path: <Jim.Kleck@8x8.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AD8528C475 for <mmusic@core3.amsl.com>; Mon, 31 Aug 2009 11:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.713
X-Spam-Level: 
X-Spam-Status: No, score=0.713 tagged_above=-999 required=5 tests=[AWL=-1.160,  BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xLOlJaU0zDY for <mmusic@core3.amsl.com>; Mon, 31 Aug 2009 11:05:09 -0700 (PDT)
Received: from mailx.8x8.com (ns25.8x8.com [192.84.19.225]) by core3.amsl.com (Postfix) with ESMTP id 275E228C464 for <mmusic@ietf.org>; Mon, 31 Aug 2009 11:02:45 -0700 (PDT)
Received: from [10.0.2.15] (192.168.84.42) by 8X8EXCH01.8x8.com (192.168.84.92) with Microsoft SMTP Server id 8.1.336.0; Mon, 31 Aug 2009 11:02:53 -0700
Message-ID: <4A9C104A.9000406@8x8.com>
Date: Mon, 31 Aug 2009 11:02:50 -0700
From: Jim Kleck <jimk@8x8.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081030 Iceape/1.1.13 (Debian-1.1.13-1)
MIME-Version: 1.0
To: Julian C. <julian@orchidseed.org>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <4A9817FC.6070408@8x8.com> <26AA8E5A-72BD-4576-B9E6-8839FC2D6D2D@orchidseed.org>
In-Reply-To: <26AA8E5A-72BD-4576-B9E6-8839FC2D6D2D@orchidseed.org>
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [MMUSIC] draft-ietf-mmusic-ice-19 question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 18:05:11 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Julian,<br>
<br>
That would make sense for processing a Binding Response, since the<br>
local agent originated the Binding Request and thus set the STUN <br>
transaction id in the first place. However, our problem is in processing<br>
a recvd Binding Request, which the remote agent originated. That<br>
is the subject of section <span>7.2.1.4.<br>
<br>
JimK<br>
<br>
</span><br>
Julian C. wrote:
<blockquote
 cite="mid:26AA8E5A-72BD-4576-B9E6-8839FC2D6D2D@orchidseed.org"
 type="cite">
  <div><span class="Apple-style-span" style="font-size: 15px;"><span>By
the use of the stun transaction ID that you'd use for retransmission.
If you don't have one then it didn't come from your stun/turn server.</span><br>
  <span></span></span><br>
Sent from my iPhone</div>
  <div><br>
On Aug 28, 2009, at 10:46 AM, Jim Kleck &lt;<a moz-do-not-send="true"
 href="mailto:jimk@8x8.com">jimk@8x8.com</a>&gt; wrote:<br>
  <br>
  </div>
  <blockquote type="cite">
    <div><span></span><br>
    <span>In looking at draft-ietf-mmusic-ice-19, we have run into a</span><br>
    <span>point of confusion. Our understanding of the draft is that all</span><br>
    <span>local candidates for a particular component for a mediastream</span><br>
    <span>should use the same host IP Addr &amp; port for gathering
candidates</span><br>
    <span>and for sending and receiving connectivity checks: section
 4.1.1.2</span><br>
    <span>says:</span><br>
    <span></span><br>
    <span>The agent next pairs each host candidate with the STUN or
TURN server</span><br>
    <span>   with which it is configured or has discovered by some
means.</span><br>
    <span></span><br>
    <span>and:</span><br>
    <span></span><br>
    <span>The result is a set of pairs of host candidates with STUN or
TURN</span><br>
    <span>   servers.</span><br>
    <span></span><br>
    <span></span><br>
    <span>However, section 7.2.1.4 (which deals with the ICE agent
processing</span><br>
    <span>a received Binding Request) states:</span><br>
    <span></span><br>
    <span>   Next, the agent constructs a pair whose local candidate is
equal to</span><br>
    <span>   the transport address on which the STUN request was
received, and a</span><br>
    <span>   remote candidate equal to the source transport address
where the</span><br>
    <span>   request came from (which may be peer-reflexive remote
candidate that</span><br>
    <span>   was just learned).</span><br>
    <span></span><br>
    <span></span><br>
    <span>If all local candidates for a component have the same host
IPaddr:port,</span><br>
    <span>how can the local agent determine which transport address the
remote</span><br>
    <span>agent sent the request to (which I assume is the first
transport address</span><br>
    <span>referenced in the 7.2.1.4 quote from the draft)? I dont see
anything in</span><br>
    <span>the STUN Binding Request pkt which identifies the target
candidate,</span><br>
    <span>nor does the IPaddr:port the request was received on identify
the target</span><br>
    <span>candidate. Or does the local agent actually need a different
host IPaddr</span><br>
    <span>and port for each local transport address?</span><br>
    <span></span><br>
    <span>James Kleck</span><br>
    <span>8x8, Inc.</span><br>
    <span></span><br>
    <span></span><br>
    <span></span><br>
    <span>_______________________________________________</span><br>
    <span>mmusic mailing list</span><br>
    <span><a moz-do-not-send="true" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a></span><br>
    <span><a moz-do-not-send="true"
 href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a></span><br>
    </div>
  </blockquote>
</blockquote>
</body>
</html>
