From mmusic-bounces@ietf.org Mon Jan 02 11:44:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EtSnb-0004YS-UQ; Mon, 02 Jan 2006 11:44:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EtSna-0004YH-Jq
	for mmusic@megatron.ietf.org; Mon, 02 Jan 2006 11:44:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18919
	for <mmusic@ietf.org>; Mon, 2 Jan 2006 11:43:29 -0500 (EST)
Message-Id: <200601021643.LAA18919@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtSsg-00067p-LM
	for mmusic@ietf.org; Mon, 02 Jan 2006 11:49:59 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <mankin@psg.com>)
	id 1EtSnV-000DWS-L9; Mon, 02 Jan 2006 16:44:37 +0000
To: tls@ietf.org
Date: Mon, 02 Jan 2006 08:44:37 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: lennox@cs.columbia.edu, hartmans+ietf@mit.edu, mmusic@ietf.org,
	jon.peterson@neustar.biz, mankin@psg.com, housley@vigilsec.com
Subject: [MMUSIC] Brief Cross-WG review - draft-ietf-mmusic-comedia-tls
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The Multiparty Multimedia Session Control (MMUSIC) WG 
has completed IETF Last Call on a document related to TLS
called :

 Connection-Oriented Media Transport over the TLS
 Protocol in the Session Descriptoin Protocol (SDP)
  draft-ietf-mmusic-comedia-tls-05.txt

comedia stands for connected media

We (Sec ADs, TSV ADs) realized we should have the TLS WG
give a quick review of the document, since there hasn't
been a look by this working group, though there
have been reviews by security experts with some TLS
expertise.

This document is a dependency for three others, and
it is being reviewed by the IESG on Thursday.  In the
busy-ness of the holidays I wrote this message on Dec
26th, but did not notice when an SMTP hiccup caused the 
email not to go before I went with my family for some
email-free holiday (just back).  If it's possible for
someone give the draft a read this week despite the short
notice, that would be appreciated.

Allison


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



From mmusic-bounces@ietf.org Mon Jan 02 20:09:30 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Etag6-0002Uk-1a; Mon, 02 Jan 2006 20:09:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Etag4-0002SH-89; Mon, 02 Jan 2006 20:09:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05495;
	Mon, 2 Jan 2006 20:08:11 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EtalC-0003uP-8r; Mon, 02 Jan 2006 20:14:47 -0500
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu
	[128.59.19.61])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id k0319DGb022765
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 2 Jan 2006 20:09:14 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1])
	by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id
	k0319Dha003282; Mon, 2 Jan 2006 20:09:13 -0500 (EST)
Received: (from lennox@localhost)
	by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id
	k0319CBn003279; Mon, 2 Jan 2006 20:09:12 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to
	lennox@cs.columbia.edu using -f
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17337.52920.343464.422053@metro-north.cs.columbia.edu>
Date: Mon, 2 Jan 2006 20:09:12 -0500
To: EKR <ekr@networkresonance.com>
In-Reply-To: <86psna8lsd.fsf@raman.networkresonance.com>
References: <200601021643.LAA18903@ietf.org>
	<86psna8lsd.fsf@raman.networkresonance.com>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=%%XGAUGE%%%%IGAUGE%%, Probability=%%PROB%%,
	Report='%%HITS%%'
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit
Cc: jon.peterson@neustar.biz, hartmans+ietf@mit.edu, tls@ietf.org,
	mmusic@ietf.org, mankin@psg.com
Subject: [MMUSIC] Re: [TLS] Brief Cross-WG review -
	draft-ietf-mmusic-comedia-tls
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

On Monday, January 2 2006, "Eric Rescorla" wrote to "mankin@psg.com, tls@ietf.org, lennox@cs.columbia.edu, hartmans+ietf@mit.edu, mmusic@ietf.org, jon.peterson@neustar.biz" saying:

> Review of draft-ietf-mmusic-comedia-tls-05
> 
> SUMMARY
> This draft describes how to use SDP to describe TLS
> connection-oriented media sessions. The major new thing is putting
> certificate fingerprints in the SDP m-line so that as long as you have
> signalling integrity you can prevent MITM attacks without 3rd party
> certificates.  This draft seems like a good idea and the
> implementation seems basically solid, modulo the comments below.
> 
> S 5:
> I agree that it's fine to use the same hash as was used to
> generate the certificate, but I think you need to explain
> why it's OK here or in the security considerations section.
> The key point is that the same security properties are required
> of the hash here as in the certificate signature.

Good point.

The other motivation is that the fingerprint be usable by the recipient so
long as the certificate itself is.

> S 6.1:
> This text seems to imply that you need to have a valid identity
> in the certificate even if it's self-signed and used with a 
> fingerprint. From a security perspective, that doesn't really
> add any value, since it's the fingerprint, not the identity,
> that provides security.

The motivation here was to allow SSH-style security (per-endpoint credential
cacheing) if the SDP isn't secured, or is only secured hop-by-hop.  Perhaps
this isn't useful?

> S 6.2:
> 
>    certificate does not match the provided fingerprint, or, if there was
>    no fingerprint, the certificate identity is incorrect, the server
>    endpoint MUST either notify the user or terminate the media
>    connection with a bad certificate error.
> 
> I assume you mean "bad_certificate" here. Also, why are you
> generating that if no fingerprint is provided? That's not a 
> TLS-level error, it's an error at the upper layer protocol. You
> shouldn't even be negotiating TLS if there's no fingerprint.

This is an editing error -- earlier versions of the draft allowed
fingerprints to be optional.  

>    Note that when the offer/answer model is being used, it is possible
>    for a media connection to outrace the answer back to the offerer.
>    Thus, if the offerer has offered a 'setup:passive' or 'setup:actpass'
>    role, it MUST (as specified in the Connection-Oriented Media
>    specification [2]) begin listening for an incoming connection as soon
>    as it sends its offer.  However, because its peer's media connection
>    may outrace its answer, it MUST NOT definitively accept the peer's
>    certificate until it has received and processed the SDP answer.
> 
> What does "definitively accept" mean here. What I would assume would
> be that you would let the TLS handshake complete but then defer
> some other action till you had the fingrerprint. But what action?

I'm not sure.  Perhaps this should be re-worded as "it MUST NOT assume the data
transmitted over the TLS connection is valid until it has received a
matching fingerprint in the SDP answer.  If the received fingerprint is
invalid, the TLS connection SHOULD be torn down."  (Is there an appropriate
TLS message for "I just discovered your certificate is invalid"?)

One other question -- in the IESG review, the issue was raised that there's
not currently an IANA registry for textual names of hash functions.  I
agreed to add an IANA considerations section for this purpose, but I was
wondering if there's interest in having this registry be more broadly scoped
than just for comedia-tls?

-- 
Jonathan Lennox
lennox@cs.columbia.edu

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



From mmusic-bounces@ietf.org Tue Jan 03 12:46:02 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EtqEU-000854-35; Tue, 03 Jan 2006 12:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EtqER-00082t-Lj; Tue, 03 Jan 2006 12:45:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01321;
	Tue, 3 Jan 2006 12:44:45 -0500 (EST)
Message-Id: <200601031744.MAA01321@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EtqJj-0004Ge-LZ; Tue, 03 Jan 2006 12:51:29 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <mankin@psg.com>)
	id 1EtqEM-0009ee-Vq; Tue, 03 Jan 2006 17:45:54 +0000
To: Eric Rescorla <ekr@networkresonance.com>
Date: Tue, 03 Jan 2006 09:45:54 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Jonathan Lennox <lennox@cs.columbia.edu>, hartmans+ietf@mit.edu,
	tls@ietf.org, jon.peterson@neustar.biz, mankin@psg.com, mmusic@ietf.org
Subject: [MMUSIC] Re: [TLS] Brief Cross-WG review -
	draft-ietf-mmusic-comedia-tls 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

> 
> > One other question -- in the IESG review, the issue was raised that
> > there's not currently an IANA registry for textual names of hash
> > functions.  I agreed to add an IANA considerations section for this
> > purpose, but I was wondering if there's interest in having this
> > registry be more broadly scoped than just for comedia-tls?
> 
> Well, as far as TLS goes, we only use integer code points, so this
> wouldn't buy us anything, but speaking personally I think this
> would be a good idea.

Ekr,

I somehow missed Jonathan's original question about this.  I'll support
making this registry broad-based as long as we don't have to troubleshoot
it a lot from the security side.  Essentially this is going to be
an IANA space for SDP-folk determined names of the algorithms
from RFCs 3280 and 4055 (and later, any RFCs which update 4055).

The reason I don't want to use the broad registry if it entails
debugging is that it's not very likely to be in the consciousness of 
future security developers, not being integrated into a reference
security RFC, and there's not much precedent (if any) for using
the same registry for multiple protocols.  

Allison  


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



From mmusic-bounces@ietf.org Tue Jan 03 14:23:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Etrl9-0002PE-Vw; Tue, 03 Jan 2006 14:23:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Etrl7-0002P7-IB
	for mmusic@megatron.ietf.org; Tue, 03 Jan 2006 14:23:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15668
	for <mmusic@ietf.org>; Tue, 3 Jan 2006 14:22:34 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtrqQ-00086Z-5D
	for mmusic@ietf.org; Tue, 03 Jan 2006 14:29:20 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k03JLkJd018768; Tue, 3 Jan 2006 21:21:48 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jan 2006 21:23:06 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jan 2006 21:23:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Fwd: I-D ACTION:draft-walsh-mmusic-img-envelope-04.txt 
Date: Tue, 3 Jan 2006 21:23:05 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD8513018194DA@trebe101.NOE.Nokia.com>
In-Reply-To: <16B450DC-78EC-4FAB-84EE-595B03804E0B@csperkins.org>
Thread-Topic: [MMUSIC] Fwd: I-D ACTION:draft-walsh-mmusic-img-envelope-04.txt 
Thread-Index: AcYIABGsnXAjQUG5TISiGUCIkRTWAAImH4bg
To: <csp@csperkins.org>, <mmusic@ietf.org>
X-OriginalArrivalTime: 03 Jan 2006 19:23:06.0142 (UTC)
	FILETIME=[1F84F3E0:01C6109B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

In a nutshell, the whole IMG work aims to provide a consistent basic
tool box for metadata transport (including SDP). It's aimed at the kind
of multimedia services MMUSIC is all about and among other things, it's
likely to obsolete SAP (for multicast announcement) and specify SIP and
HTTP usage in a simple way. There's a spectrum of use cases with massive
multicast mediacast at one end.

If this is new to you, then please have a look for img-framework and
img-reqs I-Ds (both past WGLC and waiting for approval of post-IESG
comments before heading to the RFC Editor).

The IMG envelope is key to fulfilling the need for any metadata over any
transport. It acts as a metadata consistency and validation tool for
metadata transport and basic management.

This model of the envelope is now looking polished and near final (in
our limited design team view). Sweetly enough, it is also interoperable
with the metadata envelope in 3GPP/MBMS release 6 (TS26.346). Unless you
have a dire aversion to XML, take this very seriously if you're moving
media metadata between IP hosts.

Cheers, Rod.

>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]=20
>On Behalf Of ext Colin Perkins
>Sent: 23 December, 2005 22:31
>To: IETF MMUSIC working group
>Subject: [MMUSIC] Fwd: I-D=20
>ACTION:draft-walsh-mmusic-img-envelope-04.txt=20
>
>This is relevant to MMUSIC.
>Colin
>
>
>Begin forwarded message:
>> From: Internet-Drafts@ietf.org
>> Date: 20 December 2005 20:50:01 GMT
>> To: i-d-announce@ietf.org
>> Subject: I-D ACTION:draft-walsh-mmusic-img-envelope-04.txt
>> Reply-To: internet-drafts@ietf.org
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts=20
>> directories.
>>
>>
>> 	Title		: The IMG Envelope
>> 	Author(s)	: R. Walsh, et al.
>> 	Filename	: draft-walsh-mmusic-img-envelope-04.txt
>> 	Pages		: 34
>> 	Date		: 2005-12-20
>> =09
>> This document defines the metadata transfer envelope for Internet
>>    Media Guides (IMGs).  IMG metadata describes files, resources and
>>    multimedia programs available for streaming or downloading via
>>    multicast or unicast.  IMG metadata is encapsulated into, or
>>    associated with, an IMG envelope before actual transport.  The IMG
>>    envelope is a structure providing independence between IMG=20
>> transport
>>    protocols and different metadata formats.  This specification
>>    provides the IMG envelope instantiation using structured=20
>Extensible
>>    Markup Language (XML) syntax, both as a wrapper in which to embed=20
>> an
>>    IMG metadata object and as a distinct object to associate with a
>>    distinct IMG metadata object.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-walsh-mmusic-img-
>> envelope-04.txt
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>

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



From mmusic-bounces@ietf.org Tue Jan 03 14:53:07 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EtsDT-000062-9X; Tue, 03 Jan 2006 14:53:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EtsDR-0008WH-Gh
	for mmusic@megatron.ietf.org; Tue, 03 Jan 2006 14:53:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20033
	for <mmusic@ietf.org>; Tue, 3 Jan 2006 14:51:50 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtsIl-0000rS-OY
	for mmusic@ietf.org; Tue, 03 Jan 2006 14:58:37 -0500
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by mx2.foretec.com with esmtp (Exim 4.24) id 1EtsDP-0005IU-QX
	for mmusic@ietf.org; Tue, 03 Jan 2006 14:53:04 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k03JN7bc007677; Tue, 3 Jan 2006 21:23:12 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jan 2006 21:23:06 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jan 2006 21:23:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Fwd: I-D ACTION:draft-greifenberg-mmusic-img-urn-01.txt 
Date: Tue, 3 Jan 2006 21:20:28 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD8513018194DB@trebe101.NOE.Nokia.com>
In-Reply-To: <634E46E6-3118-4A0E-B695-43C8B567C9CA@csperkins.org>
Thread-Topic: [MMUSIC] Fwd: I-D ACTION:draft-greifenberg-mmusic-img-urn-01.txt
Thread-Index: AcYIABlYTFhIfn7UT5aNyfyJ/92LPQImglig
To: <csp@csperkins.org>, <mmusic@ietf.org>
X-OriginalArrivalTime: 03 Jan 2006 19:23:06.0839 (UTC)
	FILETIME=[1FEF4E70:01C6109B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The job of this little I-D is simply to define the IMG namespace.

As soon as you get into metadata fragment control and binding transport
to datamodels, you'll know why.

Since it makes it very easy to do vendor (and any domain) -specific IMG
namespaces and in itself, it does not mandate any of the other IMG
documents, it's pretty much a one-size-fits-all media metadata namespace
definition. Very nice if that's what you need.

As 01, the worse bugs should be ironed out, however please shout out any
problems you spot.

Cheers, Rod.

PS I'm on leave, so apologies for even longer than normal response
delays!

PPS "Internet Media Guides", in case you haven't been living under my
rock :)

 =20

>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]=20
>On Behalf Of ext Colin Perkins
>Sent: 23 December, 2005 22:32
>To: IETF MMUSIC working group
>Subject: [MMUSIC] Fwd: I-D=20
>ACTION:draft-greifenberg-mmusic-img-urn-01.txt=20
>
>This is relevant to MMUSIC.
>Colin
>
>Begin forwarded message:
>> From: Internet-Drafts@ietf.org
>> Date: 15 December 2005 20:50:02 GMT
>> To: i-d-announce@ietf.org
>> Subject: I-D ACTION:draft-greifenberg-mmusic-img-urn-01.txt
>> Reply-To: internet-drafts@ietf.org
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts=20
>> directories.
>>
>>
>> 	Title		: Identifiers for Internet Media Guides (IMG)
>> 	Author(s)	: J. Greifenberg
>> 	Filename	: draft-greifenberg-mmusic-img-urn-01.txt
>> 	Pages		: 10
>> 	Date		: 2005-12-15
>> =09
>> This document defines a Uniform Resource Name (URN) namespace for
>>    identifying Internet Media Guides (IMGs).  IMG metadata describes
>>    files, resources and multimedia programs available for=20
>streaming or
>>    downloading via multicast or unicast.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-greifenberg-mmusic-img-
>> urn-01.txt
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>

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



From mmusic-bounces@ietf.org Wed Jan 04 10:11:56 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EuAIu-000462-3T; Wed, 04 Jan 2006 10:11:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EuAIs-00045u-Oo
	for mmusic@megatron.ietf.org; Wed, 04 Jan 2006 10:11:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12499
	for <mmusic@ietf.org>; Wed, 4 Jan 2006 10:10:40 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuAOM-0003bC-HL
	for mmusic@ietf.org; Wed, 04 Jan 2006 10:17:36 -0500
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59295)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1EuAIh-0002Zf-QG; Wed, 04 Jan 2006 15:11:43 +0000
In-Reply-To: <7222D14EF47E0840AD88EC7BCBAD8513018194DA@trebe101.NOE.Nokia.com>
References: <7222D14EF47E0840AD88EC7BCBAD8513018194DA@trebe101.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <03FC3540-B91A-4010-B2B0-38B2AC6BC3F9@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Fwd: I-D ACTION:draft-walsh-mmusic-img-envelope-04.txt 
Date: Wed, 4 Jan 2006 15:11:40 +0000
To: Rod.Walsh@nokia.com
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Rod,

On 3 Jan 2006, at 19:23, Rod.Walsh@nokia.com wrote:
> In a nutshell, the whole IMG work aims to provide a consistent basic
> tool box for metadata transport (including SDP). It's aimed at the  
> kind
> of multimedia services MMUSIC is all about and among other things,  
> it's
> likely to obsolete SAP (for multicast announcement) and specify SIP  
> and
> HTTP usage in a simple way. There's a spectrum of use cases with  
> massive
> multicast mediacast at one end.
>
> If this is new to you, then please have a look for img-framework and
> img-reqs I-Ds (both past WGLC and waiting for approval of post-IESG
> comments before heading to the RFC Editor).
>
> The IMG envelope is key to fulfilling the need for any metadata  
> over any
> transport. It acts as a metadata consistency and validation tool for
> metadata transport and basic management.
>
> This model of the envelope is now looking polished and near final (in
> our limited design team view). Sweetly enough, it is also  
> interoperable
> with the metadata envelope in 3GPP/MBMS release 6 (TS26.346).  
> Unless you
> have a dire aversion to XML, take this very seriously if you're moving
> media metadata between IP hosts.

Some conceptual comments:

1) There was a long discussion over lunch at the 61st IETF  
(Washington DC) on whether IMG envelopes should be XML-based or  
should use MIME headers. It would be useful if the draft contained a  
design rationale section to explain why the XML-based approach is  
used, since there are good reasons for either approach.

2) I would also like to see more discussion on why IMG envelopes are  
allowed to contain or reference IMG metadata, rather than requiring  
the metadata always be contained within the envelope.

In neither case am I arguing to change the design, but I do think it  
appropriate for the draft to explain its design choices.

On a more detailed level, does section 3.2.5 ("Consistency Checking  
of IMG Metadata") impose a requirement for globally synchronised  
clocks? Such a thing would be difficult to achieve, so clarification  
on the requirements would be useful.

I am assuming that Appendix B will be replaced by a reference to the  
IMG framework draft at some point. What is the intent for Appendix C?  
Will this be split into a separate draft? Or can it be merged into  
the main body of this draft?

Colin

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



From mmusic-bounces@ietf.org Wed Jan 04 15:23:03 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EuF9z-0001hL-P1; Wed, 04 Jan 2006 15:23:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EuF9y-0001g4-60; Wed, 04 Jan 2006 15:23:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20832;
	Wed, 4 Jan 2006 15:21:46 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]
	helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EuFFV-0007MA-AJ; Wed, 04 Jan 2006 15:28:46 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id 60EF1160059; Wed,  4 Jan 2006 15:22:59 -0500 (EST)
To: Jonathan Lennox <lennox@cs.columbia.edu>
References: <200601021643.LAA18903@ietf.org>
	<86psna8lsd.fsf@raman.networkresonance.com>
	<17337.52920.343464.422053@metro-north.cs.columbia.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Wed, 04 Jan 2006 15:22:59 -0500
In-Reply-To: <17337.52920.343464.422053@metro-north.cs.columbia.edu> (Jonathan
	Lennox's message of "Mon, 2 Jan 2006 20:09:12 -0500")
Message-ID: <tslr77nspy4.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: tls@ietf.org, mmusic@ietf.org, EKR <ekr@networkresonance.com>,
	jon.peterson@neustar.biz, mankin@psg.com
Subject: [MMUSIC] Re: [TLS] Brief Cross-WG review -
	draft-ietf-mmusic-comedia-tls
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org


Especially in the case where a fingerprint is present I think that the
requirements for identity matching would introduce usability problems
with no security benefit.  So I strongly argue for relaxing the
identity checking in the case where a fingerprint is available in an
integrity protected SDP exchange.

In the case where the cert is being matched against a trust anchor
through the process described in RFC 3280, the identity constraints
given in this document (or similar constraints) are absolutely
essential.

In the case where you are doing ssh-style leap of faith you do need to
decide what identity you are binding the leap of faith entry to in
your cache.  In that case the identity requirements may be helpful but
are not strict security requirements.

If you are going to support ssh-style leap of faith you do need to be
careful not to make rekeying/changing a cert harder than it needs to
be.  In particular, the user should not get a warning because there is
a leap of faith cache entry with a different certificate in it and a
valid fingerprint is presented in an integrity protected SDP session.
I'm not sure updating the cache entry would be good in that case, but
presenting a warning to the user because the cert changed would
definitely be a bad idea because it would discourage rekeying.

Now you do need to present the warning in the case where the SDP
session is not integrity protected.

--Sam


P.S. If I was too terse I can expand.

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



From mmusic-bounces@ietf.org Thu Jan 05 08:37:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EuVIw-00084n-37; Thu, 05 Jan 2006 08:37:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EuVIv-00084d-51
	for mmusic@megatron.ietf.org; Thu, 05 Jan 2006 08:37:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14446
	for <mmusic@ietf.org>; Thu, 5 Jan 2006 08:36:04 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuVOb-0002Op-1H
	for mmusic@ietf.org; Thu, 05 Jan 2006 08:43:14 -0500
Received: from metro-north.cs.columbia.edu (metro-north.cs.columbia.edu
	[128.59.19.61])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id k05DawGt024216
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 5 Jan 2006 08:37:13 -0500 (EST)
Received: from metro-north.cs.columbia.edu (localhost [127.0.0.1])
	by metro-north.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id
	k05Damha007383; Thu, 5 Jan 2006 08:36:48 -0500 (EST)
Received: (from lennox@localhost)
	by metro-north.cs.columbia.edu (8.12.10/8.12.10/Submit) id
	k05DalXU007380; Thu, 5 Jan 2006 08:36:47 -0500 (EST)
X-Authentication-Warning: metro-north.cs.columbia.edu: lennox set sender to
	lennox@cs.columbia.edu using -f
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17341.8431.863840.69690@metro-north.cs.columbia.edu>
Date: Thu, 5 Jan 2006 08:36:47 -0500
To: mankin@psg.com
In-Reply-To: <200512262030.jBQKUtQw006890@cs.columbia.edu>
References: <200512262030.jBQKUtQw006890@cs.columbia.edu>
X-Mailer: VM 7.19 under Emacs 20.7.1
X-PerlMx-Spam: Gauge=%%XGAUGE%%%%IGAUGE%%, Probability=%%PROB%%,
	Report='%%HITS%%'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: csp@csperkins.org, mmusic@ietf.org
Subject: [MMUSIC] Re: Need text for a sub-registry in comedia-tls
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Here's some text for the IANA considerations.  Hopefully this is in time for
your teleconference.

This specification creates a new IANA registry named "Hash Function Textual
Names".

The names of hash functions used for certificate fingerprints are registered
by the IANA.  Hash functions MUST be defined by standards-track RFCs which
update or obsolete RFC 3279 [7].

When registering a new hash function textual name, the following information
MUST be provided.

   o  The textual name of the hash function.
   o  The Object Identifier (OID) of the hash function as used in X.509
      certificates.
   o  A reference to the standards-track RFC, updating or obsoleting RFC 3279[7],
      defining the use of the hash function in X.509 certificates.

Table 1 contains the initial values of this registry.

   Hash Function Name     OID                         Reference
   ------------------     ---                         ---------
   "md2"                  1.2.840.113549.2.2          RFC 3279
   "md5"                  1.2.840.113549.2.5          RFC 3279
   "sha-1"                1.3.14.3.2.26               RFC 3279
   "sha-224"              2.16.840.1.101.3.4.2.4      RFC 4055
   "sha-256"              2.16.840.1.101.3.4.2.1      RFC 4055
   "sha-384"              2.16.840.1.101.3.4.2.2      RFC 4055
   "sha-512"              2.16.840.1.101.3.4.2.3      RFC 4055

Table 1: IANA Hash Function Textual Name Registry

-- 
Jonathan Lennox
lennox@cs.columbia.edu

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



From mmusic-bounces@ietf.org Thu Jan 05 10:32:20 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EuX6C-0002ka-J4; Thu, 05 Jan 2006 10:32:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EuX69-0002kH-TY
	for mmusic@megatron.ietf.org; Thu, 05 Jan 2006 10:32:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27086
	for <mmusic@ietf.org>; Thu, 5 Jan 2006 10:31:01 -0500 (EST)
Message-Id: <200601051531.KAA27086@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuXBp-0006Ky-6P
	for mmusic@ietf.org; Thu, 05 Jan 2006 10:38:12 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <mankin@psg.com>)
	id 1EuX64-0007X0-4f; Thu, 05 Jan 2006 15:32:12 +0000
To: Jonathan Lennox <lennox@cs.columbia.edu>
Date: Thu, 05 Jan 2006 07:32:12 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mankin@psg.com, csp@csperkins.org, mmusic@ietf.org
Subject: [MMUSIC] Re: Need text for a sub-registry in comedia-tls 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Jonathan,

Thank you - it's just in time, and it looks good.

I've also added a forward reference to it:

OLD:
   Following RFC 3279
   [7] as updated by RFC 4055 [9], therefore, the defined hash functions
   are 'SHA-1' [11] [19], 'SHA-224' [11], 'SHA-256' [11], 'SHA-384'
   [11], 'SHA-512' [11], 'MD5' [12], and 'MD2' [13], with 'SHA-1'
   preferred.  Additional hash functions can be defined only by
   standards-track RFCs which update or obsolete RFC 3279 [7].
NEW:
   Following RFC 3279 [7] as updated by RFC 4055 [9], the defined hash
   functions are 'SHA-1' [11] [19], 'SHA-224' [11], 'SHA-256' [11],
   'SHA-384' [11], 'SHA-512' [11], 'MD5' [12], and 'MD2' [13], with
   'SHA-1' preferred.  A new IANA registry called "Hash Function
   Textual Names," specified in Section 8, allows for addition of
   future tokens, but they may only be added to the registry if they are 
   specified in standards-track RFCs which update or obsolete RFC 3279 [7].

Allison

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



From mmusic-bounces@ietf.org Sun Jan 08 03:09:31 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EvVcI-0000Ry-WF; Sun, 08 Jan 2006 03:09:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EvVcG-0000Rp-JG
	for mmusic@megatron.ietf.org; Sun, 08 Jan 2006 03:09:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09430
	for <mmusic@ietf.org>; Sun, 8 Jan 2006 03:08:10 -0500 (EST)
Received: from mail1.audiocodes.com ([212.25.125.19] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EvViV-00061l-3Z
	for mmusic@ietf.org; Sun, 08 Jan 2006 03:15:56 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Sun, 08 Jan 2006 11:20:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 8 Jan 2006 10:09:55 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD601ADF68D@aclmsg.corp.audiocodes.com>
Thread-Topic: RTSP & Megaco
Thread-Index: AcYUKui1fp/1Bb/MRH+MbZGlQr0Dng==
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Subject: [MMUSIC] RTSP & Megaco
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0129117411=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0129117411==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6142A.EA2A111F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6142A.EA2A111F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

=20

Osher=20

=20

R&D Audiocodes


------_=_NextPart_001_01C6142A.EA2A111F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

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

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

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C6142A.EA2A111F--


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

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

--===============0129117411==--




From mmusic-bounces@ietf.org Mon Jan 09 10:46:04 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EvzDg-0000tc-PI; Mon, 09 Jan 2006 10:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EvzDb-0000sL-1h; Mon, 09 Jan 2006 10:46:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23079;
	Mon, 9 Jan 2006 10:44:40 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EvzK6-0000CV-OD; Mon, 09 Jan 2006 10:52:43 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1EvzDZ-0001PR-03; Mon, 09 Jan 2006 10:45:57 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1EvzDZ-0001PR-03@newodin.ietf.org>
Date: Mon, 09 Jan 2006 10:45:57 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mmusic chair <csp@csperkins.org>, Internet Architecture Board <iab@iab.org>,
	mmusic mailing list <mmusic@ietf.org>, mmusic chair <jo@acm.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MMUSIC] Document Action: 'A Framework for the Usage of Internet
 Media Guides' to Informational RFC 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The IESG has approved the following document:

- 'A Framework for the Usage of Internet Media Guides '
   <draft-ietf-mmusic-img-framework-09.txt> as an Informational RFC

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

The IESG contact persons are Jon Peterson and Allison Mankin.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-img-framework-09.txt

Technical Summary
 
This document defines a framework for the delivery of Internet Media
Guides (IMGs). An IMG is a structured collection of multimedia
session descriptions expressed using SDP, SDPng or some similar
session description format. This document describes a generalized
model for IMG delivery mechanisms, the use of existing protocols and
the need for additional work to create an IMG delivery
infrastructure.
 
Working Group Summary
 
This document is a product of the MMUSIC WG.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.


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



From mmusic-bounces@ietf.org Mon Jan 09 15:37:33 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ew3ll-0006lG-6S; Mon, 09 Jan 2006 15:37:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ew3lj-0006l5-C1
	for mmusic@megatron.ietf.org; Mon, 09 Jan 2006 15:37:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20209;
	Mon, 9 Jan 2006 15:36:12 -0500 (EST)
Received: from smtp1.netglobalis.cl ([200.14.80.91])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ew3sG-0002bD-AT; Mon, 09 Jan 2006 15:44:18 -0500
Received: from mail3.netglobalis.cl ([200.14.80.83]:40100)
	by smtp1.netglobalis.cl with esmtp (Exim 4.50 #1 (mailNG/UNIX))
	id 1Ew3lQ-0004k6-Qu; Mon, 09 Jan 2006 17:37:12 -0300
Received: from 192-152.adsl.cust.tie.cl ([200.54.192.152]:63809
	helo=[172.21.21.172])
	by mail3.netglobalis.cl with esmtp (Exim 4.52 #1 (mailNG/UNIX))
	id 1Ew3lQ-00011G-Kd; Mon, 09 Jan 2006 17:37:12 -0300
Message-ID: <43C2C977.3020407@chile.com>
Date: Mon, 09 Jan 2006 17:37:11 -0300
From: miguel <don_miguel@chile.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: The IESG <iesg-secretary@ietf.org>, mmusic@ietf.org
Subject: Re: [MMUSIC] Protocol Action: 'Session Description Protocol (SDP)
	Format for Binary Floor Control Protocol (BFCP) Streams' to Proposed
	Standard
References: <E1EoqtB-0004M5-D0@newodin.ietf.org>
In-Reply-To: <E1EoqtB-0004M5-D0@newodin.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Granted-User: msaravia (200.54.192.152) by WHOSON.
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

It's a very intresting draft..... but, if BFCP is only a draft jet, what 
could it be the standatr to have compilance when sharing resourses with SIP?

Regards

Miguel


The IESG wrote:

>The IESG has approved the following document:
>
>- 'Session Description Protocol (SDP) Format for Binary Floor Control Protocol 
>   (BFCP) Streams '
>   <draft-ietf-mmusic-sdp-bfcp-03.txt> as a Proposed Standard
>
>This document is the product of the Multiparty Multimedia Session Control 
>Working Group. 
>
>The IESG contact persons are Allison Mankin and Jon Peterson.
>
>A URL of this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-03.txt
>
>Technical Summary
> 
>    This document specifies how to describe Basic Floor Control
>    Protocol (BFCP) streams in SDP session descriptions.
>    User agents using the offer/answer model to establish
>    BFCP streams use this format in their offers and their answers.
>    BFCP is defined by an accompanying specification from the
>    XCON working group.  This document also describes
>    key management and security principles for BFCP establishment,
>    using existing protocol capabilities available through SDP.
> 
>Working Group Summary
> 
>   There was strong working group consensus behind this draft.
> 
>Protocol Quality
> 
>  The protocol has been reviewed by the MMUSIC working group. It
>  defines a number of new SDP parameters within the existing framework. 
>  The new parameters are not controversial.
>
>  Allison Mankin has acted as the Area Director for the document in order
>  to coordinate this document with the XCON BFCP document.  Colin Perkins is
>  the WG Chair shepherd for this document.  The Editor, Gonzalo Camarillo,
>  took  the initiative in shepherding the Discuss comments.
>   
>
>Note to RFC Editor
> 
> Replace Reference 3 (RFC 2234) with a reference to RFC 4234.
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>
>  
>


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



From mmusic-bounces@ietf.org Tue Jan 10 06:40:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwHrW-0002QM-6S; Tue, 10 Jan 2006 06:40:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwHrU-0002Q8-Rs
	for mmusic@megatron.ietf.org; Tue, 10 Jan 2006 06:40:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23724
	for <mmusic@ietf.org>; Tue, 10 Jan 2006 06:39:05 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwHyC-0005s9-2u
	for mmusic@ietf.org; Tue, 10 Jan 2006 06:47:20 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-221-14-69.lucent.com
	[135.221.14.69])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k0ABe3Il026836; 
	Tue, 10 Jan 2006 05:40:04 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service
	(5.5.2657.72) id <XN7D52T6>; Tue, 10 Jan 2006 11:40:03 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00C290731@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'miguel'" <don_miguel@chile.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] Protocol Action: 'Session Description Protocol (SDP)
	Format for Binary Floor Control Protocol (BFCP) Streams' to Proposed
	Sta ndard
Date: Tue, 10 Jan 2006 11:40:02 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Both 

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-xcon-bfcp-06.txt

were approved by IESG at the same time and are now in the RFC editor's queue. The only outstanding work in this area is

http://www.ietf.org/internet-drafts/draft-ietf-xcon-bfcp-connection-00.txt

which implements additional security requirements discussed in the last IETF meeting.

The relationship of BFCP with other protocols in conferencing is discussed in the two framework documents:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-framework-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-02.txt

The first of these is approved by IESG and in the RFC editor's queue. The second is still under discussion in the XCON WG.

regards

Keith

Keith Drage
Lucent Technologies
drage@lucent.com
tel: +44 1793 776249



> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org]On Behalf
> Of miguel
> Sent: 09 January 2006 20:37
> To: The IESG; mmusic@ietf.org
> Subject: Re: [MMUSIC] Protocol Action: 'Session Description Protocol
> (SDP) Format for Binary Floor Control Protocol (BFCP) Streams' to
> Proposed Standard
> 
> 
> It's a very intresting draft..... but, if BFCP is only a 
> draft jet, what 
> could it be the standatr to have compilance when sharing 
> resourses with SIP?
> 
> Regards
> 
> Miguel
> 
> 
> The IESG wrote:
> 
> >The IESG has approved the following document:
> >
> >- 'Session Description Protocol (SDP) Format for Binary 
> Floor Control Protocol 
> >   (BFCP) Streams '
> >   <draft-ietf-mmusic-sdp-bfcp-03.txt> as a Proposed Standard
> >
> >This document is the product of the Multiparty Multimedia 
> Session Control 
> >Working Group. 
> >
> >The IESG contact persons are Allison Mankin and Jon Peterson.
> >
> >A URL of this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-03.txt
> >
> >Technical Summary
> > 
> >    This document specifies how to describe Basic Floor Control
> >    Protocol (BFCP) streams in SDP session descriptions.
> >    User agents using the offer/answer model to establish
> >    BFCP streams use this format in their offers and their answers.
> >    BFCP is defined by an accompanying specification from the
> >    XCON working group.  This document also describes
> >    key management and security principles for BFCP establishment,
> >    using existing protocol capabilities available through SDP.
> > 
> >Working Group Summary
> > 
> >   There was strong working group consensus behind this draft.
> > 
> >Protocol Quality
> > 
> >  The protocol has been reviewed by the MMUSIC working group. It
> >  defines a number of new SDP parameters within the existing 
> framework. 
> >  The new parameters are not controversial.
> >
> >  Allison Mankin has acted as the Area Director for the 
> document in order
> >  to coordinate this document with the XCON BFCP document.  
> Colin Perkins is
> >  the WG Chair shepherd for this document.  The Editor, 
> Gonzalo Camarillo,
> >  took  the initiative in shepherding the Discuss comments.
> >   
> >
> >Note to RFC Editor
> > 
> > Replace Reference 3 (RFC 2234) with a reference to RFC 4234.
> >
> >
> >_______________________________________________
> >mmusic mailing list
> >mmusic@ietf.org
> >https://www1.ietf.org/mailman/listinfo/mmusic
> >
> >  
> >
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

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



From mmusic-bounces@ietf.org Tue Jan 10 07:25:14 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwIYs-0004DJ-Ng; Tue, 10 Jan 2006 07:25:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwIYr-0004CB-1y
	for mmusic@megatron.ietf.org; Tue, 10 Jan 2006 07:25:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26429
	for <mmusic@ietf.org>; Tue, 10 Jan 2006 07:23:52 -0500 (EST)
Received: from mail1.audiocodes.com ([212.25.125.19] helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwIfV-00073Z-If
	for mmusic@ietf.org; Tue, 10 Jan 2006 07:32:07 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Tue, 10 Jan 2006 15:35:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 10 Jan 2006 14:25:38 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD601B38295@aclmsg.corp.audiocodes.com>
Thread-Topic: Using RTSP with SIP
Thread-Index: AcYV4PalPJO7dTPARcCEunhAesvg2g==
From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Subject: [MMUSIC] Using RTSP with SIP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1078187443=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1078187443==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C615E0.F80E32FF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C615E0.F80E32FF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

a=3Dchannel:xxx

=20

as part of application SDP.

=20

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

=20

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

=20

Thanks a lot.

=20

Osher

=20

=20

=20

=20


------_=_NextPart_001_01C615E0.F80E32FF
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C615E0.F80E32FF--


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

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

--===============1078187443==--




From mmusic-bounces@ietf.org Tue Jan 10 20:44:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwV2A-0008S3-Lj; Tue, 10 Jan 2006 20:44:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwV29-0008Rk-E8
	for mmusic@megatron.ietf.org; Tue, 10 Jan 2006 20:44:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29849
	for <mmusic@ietf.org>; Tue, 10 Jan 2006 20:42:56 -0500 (EST)
Received: from acsys.apac.edu.au ([150.203.56.17] helo=acsys.anu.edu.au)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwV8v-0000SH-0a
	for mmusic@ietf.org; Tue, 10 Jan 2006 20:51:19 -0500
Received: from accordion3.acsys.anu.edu.au ([150.203.20.19])
	by acsys.anu.edu.au (8.9.3/8.9.3) with ESMTP id MAA28188;
	Wed, 11 Jan 2006 12:44:09 +1100 (EST)
Message-Id: <6.1.0.6.2.20060111112845.0353a8b0@acsys.anu.edu.au>
X-Sender: markus2@acsys.anu.edu.au
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 11 Jan 2006 12:29:03 +1100
To: mmusic@ietf.org
From: Markus Buchhorn <Markus.Buchhorn@anu.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [MMUSIC] rtsp describe and containers
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi all

First off, Happy New Year to all! [who celebrate the Julian calendar] 

I have a quick couple of questions about the rtsp (v1) spec, and the v2 rfc2326bis draft as well. 

The ability to control 'container' files doesn't appear to be described consistently. The example in 11.2 (2326bis; 10.2 in rfc2326) for DESCRIBE has an SDP showing multiple media (m=) streams, but no control information per stream. Yet the examples in 17.1/17.2 (2326bis; 14.1/14.2 in rfc2326) have individual control information per m= line. Is there a mechanism for handling container'ed materials that uses the SDP description as the DESCRIBE examples show, or should the example SDP in 10.2/11.2 be like the examples in 14.1-2/17.1-2? :-) 

Also, there is the use of a 'streamid' in several rfc2326 examples, and both 'streamid' and 'trackid' are used in rfc2326bis. streamid is never explained in either document, and it appears that trackid takes on its role in 2326bis? Trackid doesn't have any introduction in the latter, is only covered briefly in C.1.1 under URI handling, and is very late in the document :-) A sentence or two specifically on it up earlier could be helpful to implementors...

I presume 'trackid' (to replace 'streamid'?) is a new standard for rtsp-v2 clients as well then? In which case should streamid go away from 2326bis/rtsp-v2?

Thanks for any advice/comments! We're trying to code up a small rtsp (v1 for now) server and the various clients ain't totally happy :-) Seems like too many differing examples to choose from just caused us some confusion.

Cheers,
	Markus

Markus Buchhorn, ANU Internet Futures             |Ph: +61 2 61258810
Markus.Buchhorn@anu.edu.au                        |Fx: +61 2 61259805
The Australian National University, Canberra 0200 |Mob: 0417 281429


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



From mmusic-bounces@ietf.org Wed Jan 11 05:58:56 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ewdgu-0005vY-SZ; Wed, 11 Jan 2006 05:58:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ewdgt-0005vT-1v
	for mmusic@megatron.ietf.org; Wed, 11 Jan 2006 05:58:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02036
	for <mmusic@ietf.org>; Wed, 11 Jan 2006 05:57:35 -0500 (EST)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ewdni-0006md-41
	for mmusic@ietf.org; Wed, 11 Jan 2006 06:06:02 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 009C29C1; 
	Wed, 11 Jan 2006 11:58:41 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jan 2006 11:58:40 +0100
Received: from [147.214.34.70] ([147.214.34.70]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jan 2006 11:58:40 +0100
Message-ID: <43C4E4E0.5020209@ericsson.com>
Date: Wed, 11 Jan 2006 11:58:40 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Markus Buchhorn <Markus.Buchhorn@anu.edu.au>
Subject: Re: [MMUSIC] rtsp describe and containers
References: <6.1.0.6.2.20060111112845.0353a8b0@acsys.anu.edu.au>
In-Reply-To: <6.1.0.6.2.20060111112845.0353a8b0@acsys.anu.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jan 2006 10:58:40.0442 (UTC)
	FILETIME=[FB0FA1A0:01C6169D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi Markus,

Markus Buchhorn wrote:
> Hi all
> 
> First off, Happy New Year to all! [who celebrate the Julian calendar] 
> 
> I have a quick couple of questions about the rtsp (v1) spec, and the v2 rfc2326bis draft as well. 
> 
> The ability to control 'container' files doesn't appear to be described consistently. The example in 11.2 (2326bis; 10.2 in rfc2326) for DESCRIBE has an SDP showing multiple media (m=) streams, but no control information per stream. Yet the examples in 17.1/17.2 (2326bis; 14.1/14.2 in rfc2326) have individual control information per m= line. Is there a mechanism for handling container'ed materials that uses the SDP description as the DESCRIBE examples show, or should the example SDP in 10.2/11.2 be like the examples in 14.1-2/17.1-2? :-) 

The example in 11.2 is not a container file example, it is an multicast 
example.

> 
> Also, there is the use of a 'streamid' in several rfc2326 examples, and both 'streamid' and 'trackid' are used in rfc2326bis. streamid is never explained in either document, and it appears that trackid takes on its role in 2326bis? Trackid doesn't have any introduction in the latter, is only covered briefly in C.1.1 under URI handling, and is very late in the document :-) A sentence or two specifically on it up earlier could be helpful to implementors...

The issue here is that there are no standard for this. These are merely 
examples. If you look in section 3.2:

"The syntax of any URI query string is unspecified and responder
    (usually the server) specific. As it is from the requestor an opaque
    string, it needs to be handled as such."

Thus, RTSP does not at all specify any URI structure for container 
files. If a container file think it necessary to have a common structure 
then it should define that.


> 
> I presume 'trackid' (to replace 'streamid'?) is a new standard for rtsp-v2 clients as well then? In which case should streamid go away from 2326bis/rtsp-v2?

This is an example. We probably should clarify this.

> 
> Thanks for any advice/comments! We're trying to code up a small rtsp (v1 for now) server and the various clients ain't totally happy :-) Seems like too many differing examples to choose from just caused us some confusion.

The issue is that RTSPv1 isn't possible to get fully interoperable from 
the specification. One needs to know the common core that people 
support. And I think a lot of commercial servers uses If User-Agent = 
"client X" then ...

Please remember also to implement from the specification text, not the 
examples.

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Wed Jan 11 11:06:06 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwiUA-000750-JG; Wed, 11 Jan 2006 11:06:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwiU8-00074v-BT
	for mmusic@megatron.ietf.org; Wed, 11 Jan 2006 11:06:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22561
	for <mmusic@ietf.org>; Wed, 11 Jan 2006 11:04:44 -0500 (EST)
Received: from smtp7.clb.oleane.net ([213.56.31.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ewib0-0007P3-UW
	for mmusic@ietf.org; Wed, 11 Jan 2006 11:13:14 -0500
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp7.clb.oleane.net with ESMTP id k0BG5jop022243
	for <mmusic@ietf.org>; Wed, 11 Jan 2006 17:05:46 +0100
Message-Id: <200601111605.k0BG5jop022243@smtp7.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mmusic@ietf.org>
Date: Wed, 11 Jan 2006 17:04:44 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYWyLyAN/C9bQMRQVSXgUsFByNjyQ==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Subject: [MMUSIC] International SIP Conference / WiMAX Summit 2006 - Paris -
	France 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0956729489=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0956729489==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_031D_01C616D1.1EC571F0"

This is a multi-part message in MIME format.

------=_NextPart_000_031D_01C616D1.1EC571F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 The International SIP conference and the WiMAX Summit will start next
February 21st in Paris. The two events are co-organised and will bring any
necessary information on VoIP, mobility convergence and wireless broadband
access.

 

The early registration 10% discount will end in one week.

 

Get all details on International SIP at:

 <http://www.upperside.fr/sip2006/sip2006intro.htm>
http://www.upperside.fr/sip2006/sip2006intro.htm

 

Get all details on the WiMAX Summit at:

http://www.upperside.fr/wimax2006/wimax2006intro.htm

 

 

 


------=_NextPart_000_031D_01C616D1.1EC571F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'>&nbsp;</span></font><font size=3D2 =
face=3DArial><span
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:Arial'>The =
International SIP conference
and the WiMAX Summit will start next February 21st in <st1:place =
w:st=3D"on"><st1:City
 w:st=3D"on">Paris</st1:City></st1:place>. The two events are =
co-organised and
will bring any necessary information on VoIP, mobility convergence and =
wireless
broadband access.</span></font><span lang=3DEN-GB><o:p></o:p></span></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The early registration 10% discount will end =
in one
week.</span></font><span lang=3DEN-GB><o:p></o:p></span></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a =
href=3D"http://www.upperside.fr/sip2006/sip2006intro.htm"
title=3D"http://www.upperside.fr/sip2006/sip2006intro.htm"><span =
lang=3DEN-GB><span
title=3D"http://www.upperside.fr/sip2006/sip2006intro.htm">http://www.upp=
erside.fr/sip2006/sip2006intro.htm</span></span></a></span></font><span
lang=3DEN-GB><o:p></o:p></span></p>

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

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

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

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

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

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

</div>

</body>

</html>

------=_NextPart_000_031D_01C616D1.1EC571F0--



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

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

--===============0956729489==--





From mmusic-bounces@ietf.org Thu Jan 12 14:22:33 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ex81p-0006rK-0q; Thu, 12 Jan 2006 14:22:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ex81j-0006qZ-IX; Thu, 12 Jan 2006 14:22:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10487;
	Thu, 12 Jan 2006 14:21:06 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ex88u-0006BI-4p; Thu, 12 Jan 2006 14:29:52 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1Ex81e-0005Qw-Qz; Thu, 12 Jan 2006 14:22:22 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1Ex81e-0005Qw-Qz@newodin.ietf.org>
Date: Thu, 12 Jan 2006 14:22:22 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mmusic chair <csp@csperkins.org>, Internet Architecture Board <iab@iab.org>,
	mmusic mailing list <mmusic@ietf.org>, mmusic chair <jo@acm.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MMUSIC] Document Action: 'Requirements for Internet Media Guides'
 to Informational RFC 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

The IESG has approved the following document:

- 'Requirements for Internet Media Guides '
   <draft-ietf-mmusic-img-req-08.txt> as an Informational RFC

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

The IESG contact persons are Jon Peterson and Allison Mankin.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-img-req-08.txt

Technical Summary
 
This memo specifies requirements for a framework and protocols for
accessing and updating Internet Media Guide (IMG) information for
media-on-demand and multicast applications. These requirements are
designed to guide choice and development of IMG protocols for
efficient and scalable delivery.
 
Working Group Summary
 
This document is a product of the MMUSIC WG.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.


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



From mmusic-bounces@ietf.org Thu Jan 19 09:54:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzbBZ-0008Ql-NX; Thu, 19 Jan 2006 09:54:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzbBV-0008NB-Rz
	for mmusic@megatron.ietf.org; Thu, 19 Jan 2006 09:54:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28588
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 09:53:18 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EzbK3-0001u5-MU
	for mmusic@ietf.org; Thu, 19 Jan 2006 10:03:36 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-2.cisco.com with ESMTP; 19 Jan 2006 06:54:36 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k0JEsYQi020210;
	Thu, 19 Jan 2006 06:54:35 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 19 Jan 2006 06:54:34 -0800
Received: from [10.21.144.120] ([10.21.144.120]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 19 Jan 2006 06:54:33 -0800
Message-ID: <43CFA829.5010304@cisco.com>
Date: Thu, 19 Jan 2006 09:54:33 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Joerg Ott <jo@netlab.hut.fi>
Subject: Re: Sharing ports between "m=" lines [Was Re: [MMUSIC] Re: Question
	on	sdp-new}
References: <200510131847.j9DIlNub002020@sj-core-1.cisco.com>	<219F0A96-C91F-4279-B5F3-2C8B3A0F0F20@csperkins.org>	<43569970.1080508@cisco.com>
	<438AB3EA.7040403@netlab.hut.fi> <4394712D.1040605@cisco.com>
	<43C4E7E1.7080200@netlab.hut.fi>
In-Reply-To: <43C4E7E1.7080200@netlab.hut.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2006 14:54:33.0981 (UTC)
	FILETIME=[42884AD0:01C61D08]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Content-Transfer-Encoding: 7bit
Cc: Dan Wing <dwing@cisco.com>, "'Elwell, John'" <john.elwell@siemens.com>,
	mmusic@ietf.org, M.Handley@cs.ucl.ac.uk,
	Colin Perkins <csp@csperkins.org>, van@packetdesign.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org



Joerg Ott wrote:

>>> Let me briefly recap where this comes from:
>>>
>>> 1.  This practice was originally documented in the SDP offer/anser
>>>     examples draft.  The chairs felt that it was inappropriate to
>>>     document such behavior by example only and that some normative
>>>     language should be backing this since it was commonly felt a
>>>     useful thing to have.  The result is in the SDP spec.  There
>>>     was not much input though.
>>>
>> OK. Part of the input provided though raised some concerns with this.
>>
>>> 2.  When RFC2327 was done, there was only a single RTP profile defined.
>>>     Some profiles allow mixing in a session but SDP does not allow that
>>>     to be specified.  But we must also care of those applications that
>>>     do not use offer/answer.
>>>
>>> In principle, I am all in favor of solving this problem in a reasonable
>>> way and I do not care that much which way it is.  The present text in
>>> SDP was meant to reflect observed behavior.  This is why it is there.
>>> The text itself was meant to be rather minimalistic, so it may well
>>> have holes.  If so (and what you sat clearly points into that
>>> direction), we need to fix these (and of course your help is very
>>> welcome here :-)
>>>
>> I'll be happy to help out. Can we start out by clarifying exactly 
>> what the scope of the problem we want to solve here is ? Once we 
>> agree on that we can then look at appropriate solutions.
>
>
> I am afraid we have two scope issues here: one is the problem at hand
> and the other one is the fact that SDP-new has essentially cleared
> all hurdles towards being published.
>
> The ID tracker notes: "Ancient returning item: no longer has enough 
> ballot positions to advance. Mercy for these poor souls, new reviewers!"
>
> And indeed SDP-new seems to have entered this in mid 2003 (not sure
> where the record is).
>
> This means that we should craft our second scope carefully to allow
> for quick completion.  The task at hand seems twofold:
>
> 1.  Documenting the behavior of SIP endpoints that was previously
>     stated in the offer-answer examples draft.
>
> 2.  Defining semantics for the case that two m/c lines specify
>     the same transport address (which simply was omitted entirely
>     in SDP before).
>
> For 1., an interesting question is whether this behevior still exists.

Right. I took a look at the T.38, V.150, and V.152 specs (who were the 
suspected culprits here), and I didn't see it in either of those. I also 
asked one of the authors of those specs, and he indicated they did not 
add such  behavior (based on feedback received from AVT, however they 
would have liked to).

Another equally important thing to consider here is, that even if such 
behavior does exist in certain endpoints, but were never part of the 
spec, should you now make it part of the updated sdp-new spec ? If you 
do so, you all of a sudden run the risk of making a bunch of endpoints 
that worked and were compliant with RFC 2327 non-compliant with sdp-new. 
I think we would need pretty strong arguments for doing so.


> If it does not then one could argue that there is no point in
> documenting this in the first place and we are completely free how
> to make up 2.  Otherwise, the semantics for 2. must consider this.

Given this is not part of any existing spec I know, I think we have 
substantial degrees of freedom here, but backwards compatibility must be 
an important consideration.


> For 2., I would hope to stick with a minimal scope here:
> -- identification of "equal" media sessions
> -- defining their semantics and handling

That is one option. Another is to simply say, that using the same 
address for two different media lines is not part of the basic SDP 
semantics. We could then define a more explicit framework that would 
actually allow for "equal" media sessions to be specified as 
alternatives along with more elaborate rules (particular O/A rules).

>
> At first, we need to identify when two media sessions are
> considered "equal" (bearing in mind that if they are, they are
> supposed to indicate alternatives that may of course differ
> significantly in many attributes).
>
> This equality must obviously be based upon mandatory attributes
> defined in the SDP spec and must also allow for differentiation
> of session.  It looks like the triple (IP address, port number,
> media type) should do the job.  Obviously, one would need to
> mandate that the transport addresses need to be kept identical
> across o/a exchange (i.e., if they change they all need to change
> and if they were the same before, they all need to change to the
> same new value).
>
That's not clear to me. Let's say I start out by offering RTP/AVP and 
RTP/AVPF, and the answer indicates that AVP was accepted, whereas AVPF 
was not. Is there really a need to keep offering AVPF in subsequent O/A 
exchanges ? Having said though, I agree that you would need to keep the 
transport address in sync across the multiple alternatives if they were 
being included in subsequent offers. Again, I think there's an argument 
for a more explicit grouping of alternatives here than simply looking at 
the m= lines that have identical transport addresses, but it could work.

> Thinking of your considerations on a=sendonly and a=recvonly:
> You are allowed to put calls on hold and so this attribute
> may change during a sequence of o/a exchanges.  I would count
> this into a different category than the triple avove.
>
> Further thoughts on identification?

I like the capabilities I get by using the triple <IP address, port 
number, media type>, but it leaves open some issues, which I think the 
current sdp-new text was trying to avoid (and which you address below). 
For example, if I indicate RTP/AVP and RTP/SAVP as alternatives and I 
now receive a media packet, which profile is it actually encoded under ? 
Do payload type mappings have to be the same between these alternatives 
? In general, once I allow for quite a bit of variability in the 
parameters included in these alternatives, it becomes potentially 
problematic to use them not only outside offer/answer, but also within 
offer/answer if I want to support receiving media prior to receiving the 
answer.

>
> Defining their semantics is partly influenced by legacy.
>
> If there was no legacy, we could simply declare equal descriptions
> to be illegal and a reason for rejection.  Or we could treat them
> as a single media session that just happens to be signaling twice.
> This is probably independent of o/a.
>
Agreed.

> If no negotiation mechanism is available (e.g., when retrieving
> SDP via HTTP or announcing it via SAP), the media sessions must
> be compatible as there is no way to agree on one over the other

Agree again. Here, it becomes important that we accurately define what 
"compatible" means.

> .
> (This is obvious but may be worthwhile stating anyway).


> If a negotiation mechanism is available, we have presently either

> o/a or RTSP.  RFC2326 is in such a poor condition that any fix
> need not really be backward compatible because of the many holes
> and because rfc2326-bis get a new version number anway.  (a bit
> of pragmatism here)
>
> This leaves o/a as the major thing to deal with:
>
> If you are an offerer and want to indicate (without the grouping
> framework) two alternatives, you just do so, expecting that the
> peer will accept only one of these.  

Meaning it sets the port to zero for the other one, or it doesn't 
include it in the answer (presumably the former, although I think we'll 
need some text here to state what you do in either case plus the case 
where it is actually accepted) ?


> If it does, fine, you know
> what to do.  If the peer accepts none, ok as well.  If the peer
> accepts both, you can would need to re-INVITE and pick one anyway.
> The very same holds if the peer does not understanding grouping
> except that you notice this by the absence of the grouping
> attributes.

True.

>
> The quote from o/a below does not define what multiple streams are.
> An RTP session is defined by its target transport address(es).
> If you make reference to the same RTP session in two m/c lines this
> does not create another session either.  RFC 3264 does not say
> much about allowed or disallowed addresses except that multicast
> must be responded to with and multicast and unicast with unicast.
>
> But RFC3264 does say that, if multiple streams of the same type
> are offered, it is up to the local policy how these are mapped
> to cameras, mikes, etc.  Local interpretation is what is needed
> here.
>
> Please let me know what you think so we can craft some text here.

See above. To summarize:
- It is not clear to me that we really need to define the operation of 
multiple m= lines with the same transport address in sdp-new.
- I agree we very much need the capability to negotiate alternatives 
(incl. profiles) in SDP. Whether that should be done using m= lines with 
identical transport address or something else, as well as whether it 
needs to be part of sdp-new or not (and if so, whether it is a mandatory 
or optional part of it), is something that is less clear to me. I think 
it's worth taking a step back and consider the alternatives here.

I'd be interested in what other people think about all of this as well.

-- Flemming

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



From mmusic-bounces@ietf.org Thu Jan 19 12:52:46 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ezdxm-0002Fd-Sh; Thu, 19 Jan 2006 12:52:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ezdxk-0002FQ-S2
	for mmusic@megatron.ietf.org; Thu, 19 Jan 2006 12:52:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10996
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 12:51:18 -0500 (EST)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eze6G-0007b1-E3
	for mmusic@ietf.org; Thu, 19 Jan 2006 13:01:36 -0500
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
	(PMDF V6.0-24 #40642) id <0ITC00801PIP44@siemenscomms.co.uk> for
	mmusic@ietf.org; Thu, 19 Jan 2006 17:49:38 +0000 (GMT)
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0ITC0080DPIP37@siemenscomms.co.uk>; Thu,
	19 Jan 2006 17:49:37 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <ZRJP9W7C>; Thu, 19 Jan 2006 17:52:16 +0000
Content-return: allowed
Date: Thu, 19 Jan 2006 17:52:16 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: Sharing ports between "m=" lines [Was Re: [MMUSIC] Re: Questi	on
	on sdp-new}
To: Flemming Andreasen <fandreas@cisco.com>, Joerg Ott <jo@netlab.hut.fi>
Message-id: <50B1CBA96870A34799A506B2313F266707D3E1D7@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7BIT
Cc: van@packetdesign.com, mmusic@ietf.org, M.Handley@cs.ucl.ac.uk,
	Dan Wing <dwing@cisco.com>, Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Flemming,

I will just comment on one point:

<snip/> 
> I like the capabilities I get by using the triple <IP address, port 
> number, media type>, but it leaves open some issues, which I 
> think the 
> current sdp-new text was trying to avoid (and which you 
> address below). 
> For example, if I indicate RTP/AVP and RTP/SAVP as alternatives and I 
> now receive a media packet, which profile is it actually 
> encoded under ? 
> Do payload type mappings have to be the same between these 
> alternatives 
> ? In general, once I allow for quite a bit of variability in the 
> parameters included in these alternatives, it becomes potentially 
> problematic to use them not only outside offer/answer, but 
> also within 
> offer/answer if I want to support receiving media prior to 
> receiving the 
> answer.
[JRE] Is this an argument for saying that we need to be able to group media
as equals even if they have diffent addresses?

<snip/>

John

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



From mmusic-bounces@ietf.org Thu Jan 19 15:13:37 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzgA5-00064u-Jb; Thu, 19 Jan 2006 15:13:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzgA3-00064m-SW
	for mmusic@megatron.ietf.org; Thu, 19 Jan 2006 15:13:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23059
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 15:12:09 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EzgIb-0003if-V9
	for mmusic@ietf.org; Thu, 19 Jan 2006 15:22:29 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-3.cisco.com with ESMTP; 19 Jan 2006 12:13:21 -0800
X-IronPort-AV: i="4.01,201,1136188800"; 
	d="scan'208"; a="393855219:sNHT31818720"
Received: from dwingwxp ([128.107.171.55])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k0JKDKjt010462;
	Thu, 19 Jan 2006 12:13:20 -0800 (PST)
Message-Id: <200601192013.k0JKDKjt010462@sj-core-5.cisco.com>
From: "Dan Wing" <dwing@cisco.com>
To: "'Elwell, John'" <john.elwell@siemens.com>,
	"'Flemming Andreasen'" <fandreas@cisco.com>,
	"'Joerg Ott'" <jo@netlab.hut.fi>
Subject: RE: Sharing ports between "m=" lines [Was Re: [MMUSIC] Re:
	Questi	onon sdp-new}
Date: Thu, 19 Jan 2006 12:13:20 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYdIYND3uwBncIDRxusBLtusscTEwAEtM+A
In-Reply-To: <50B1CBA96870A34799A506B2313F266707D3E1D7@ntht201e.siemenscomms.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: 'Colin Perkins' <csp@csperkins.org>, mmusic@ietf.org, van@packetdesign.com,
	M.Handley@cs.ucl.ac.uk
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

> I will just comment on one point:
> 
> <snip/> 
> > I like the capabilities I get by using the triple <IP address,
> > port number, media type>, but it leaves open some issues, which I
> > think the current sdp-new text was trying to avoid (and which you
> > address below).  For example, if I indicate RTP/AVP and RTP/SAVP
> > as alternatives and I now receive a media packet, which profile is
> > it actually encoded under ? Do payload type mappings have to be
> > the same between these alternatives ? In general, once I allow for
> > quite a bit of variability in the parameters included in these
> > alternatives, it becomes potentially problematic to use them not
> > only outside offer/answer, but also within offer/answer if I want
> > to support receiving media prior to receiving the answer.
>
> [JRE] Is this an argument for saying that we need to be able to
> group media as equals even if they have diffent addresses?

RFC4091 does that already -- it groups media lines as equal even 
when those media lines have different addresses.  RFC4091 restricts
itself to grouping IPv4 and IPv6 addresses, though.

-d

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



From mmusic-bounces@ietf.org Thu Jan 19 23:34:41 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eznyz-0006u1-3t; Thu, 19 Jan 2006 23:34:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eznyv-0006ru-PR
	for mmusic@megatron.ietf.org; Thu, 19 Jan 2006 23:34:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03690
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 23:33:09 -0500 (EST)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ezo7Z-0003rf-Ui
	for mmusic@ietf.org; Thu, 19 Jan 2006 23:43:35 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 712789008E
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 23:34:20 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 06738-02 for <mmusic@ietf.org>;
	Thu, 19 Jan 2006 23:34:18 -0500 (EST)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mmusic@ietf.org>; Thu, 19 Jan 2006 23:34:18 -0500 (EST)
Received: from EXCHINDIA2.starentnetworks.com ([10.4.0.4]) by
	ames.starentnetworks.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 19 Jan 2006 23:34:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Jan 2006 10:03:27 +0530
Message-ID: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
Thread-Topic: simultaneous RTSP sessions over the same TCP connection?
Thread-Index: AcYdIYND3uwBncIDRxusBLtusscTEwAEtM+AABER1RA=
From: "Patankar, Sujay" <spatankar@starentnetworks.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 20 Jan 2006 04:34:18.0713 (UTC)
	FILETIME=[C6EACC90:01C61D7A]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi,
I had a couple of questions about RTSP. I'll be greatly thankful to
anyone who answers them.

1:  Can there be more than one RTSP session-ids in simultaneous use over
a single TCP connection between a client and a server? (I mean over the
same {src IP, src port} and {dst IP, dst port} pair) If I receive, for
example, a request or response w/o a session ID, can I safely assume
that it belongs the same session id as that was present in other RTSP
messages seen on this TCP connection?

2: The RTSP RFC (2326) states that the session id is required in all
requests as well as responses except the OPTIONS and SETUP requests.
However, I have seen a RealPlayer receiving a 200 reply to a PLAY. The
200 OK reply didn't contain any session id. (it had the matching CSeq
though) I was under the impression that every reply MUST contain a
session id.

3: If multiple session ids can be in use on the same TCP connection at
the same time, what happens when one of the sessions does a TEARDOWN?
Will the TCP connection be torn down? What will the other sessions do in
such case? Does an RTSP TEARDOWN always involve a TCP connection
teardown?

Thanks in advance for any help,
Sujay.

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



From mmusic-bounces@ietf.org Fri Jan 20 06:56:35 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ezusd-0007eT-Sd; Fri, 20 Jan 2006 06:56:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ezusa-0007dQ-4e
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 06:56:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05076
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 06:55:03 -0500 (EST)
Received: from smtp8.clb.oleane.net ([213.56.31.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ezv1I-0000yl-FF
	for mmusic@ietf.org; Fri, 20 Jan 2006 07:05:33 -0500
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp8.clb.oleane.net with ESMTP id k0KBuA61005136
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 12:56:10 +0100
Message-Id: <200601201156.k0KBuA61005136@smtp8.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mmusic@ietf.org>
Date: Fri, 20 Jan 2006 12:54:59 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYduFb5n6nA4HwdR/W1mysDWEswqA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Subject: [MMUSIC] WiMAX Summit - International SIP conference - Paris -
	France
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1323214442=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1323214442==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0105_01C61DC0.B9164A90"

This is a multi-part message in MIME format.

------=_NextPart_000_0105_01C61DC0.B9164A90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The WiMAX Summit and the International SIP conference will jointly open
their doors in one month, on February 21st, in Paris.

Everything you must know about broadband wireless access, VoIP and
convergence will be delivered by operators and key technical players.

An exhibition, close to the two conferences, welcome industrials wishing to
demonstrate their solutions.

 

Get details on International SIP at:

 <http://www.upperside.fr/sip2006/sip2006intro.htm>
http://www.upperside.fr/sip2006/sip2006intro.htm

 

Get details on the WiMAX Summit at:

 <http://www.upperside.fr/wimax2006/wimax2006intro.htm>
http://www.upperside.fr/wimax2006/wimax2006intro.htm

 

 


------=_NextPart_000_0105_01C61DC0.B9164A90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The WiMAX Summit and the International SIP =
conference
will jointly open their doors in one month, on February 21st, in =
<st1:place
w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>.</span></font><span
lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Everything you must know about broadband =
wireless
access, VoIP and convergence will be delivered by operators and key =
technical
players.</span></font><span lang=3DEN-GB><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>An exhibition, close to the two conferences,
welcome&nbsp;industrials wishing to demonstrate their =
solutions.</span></font><span
lang=3DEN-GB><o:p></o:p></span></p>

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

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

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

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

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

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0105_01C61DC0.B9164A90--



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

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

--===============1323214442==--





From mmusic-bounces@ietf.org Fri Jan 20 08:30:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzwLs-0002k0-Uf; Fri, 20 Jan 2006 08:30:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzwLo-0002fr-Pu
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 08:30:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12683
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 08:29:21 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EzwUX-0004Kx-ME
	for mmusic@ietf.org; Fri, 20 Jan 2006 08:39:51 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-1.cisco.com with ESMTP; 20 Jan 2006 05:30:38 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k0KDUbQi003632;
	Fri, 20 Jan 2006 05:30:37 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 20 Jan 2006 05:30:37 -0800
Received: from [10.21.120.177] ([10.21.120.177]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 20 Jan 2006 05:30:36 -0800
Message-ID: <43D0E5FA.1010807@cisco.com>
Date: Fri, 20 Jan 2006 08:30:34 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: Sharing ports between "m=" lines [Was Re: [MMUSIC] Re: Questi
	on on sdp-new}
References: <50B1CBA96870A34799A506B2313F266707D3E1D7@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F266707D3E1D7@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jan 2006 13:30:36.0700 (UTC)
	FILETIME=[B27DF5C0:01C61DC5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@netlab.hut.fi>, Dan Wing <dwing@cisco.com>, mmusic@ietf.org,
	M.Handley@cs.ucl.ac.uk, Colin Perkins <csp@csperkins.org>,
	van@packetdesign.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org



Elwell, John wrote:

>Flemming,
>
>I will just comment on one point:
>
><snip/> 
>  
>
>>I like the capabilities I get by using the triple <IP address, port 
>>number, media type>, but it leaves open some issues, which I 
>>think the 
>>current sdp-new text was trying to avoid (and which you 
>>address below). 
>>For example, if I indicate RTP/AVP and RTP/SAVP as alternatives and I 
>>now receive a media packet, which profile is it actually 
>>encoded under ? 
>>Do payload type mappings have to be the same between these 
>>alternatives 
>>? In general, once I allow for quite a bit of variability in the 
>>parameters included in these alternatives, it becomes potentially 
>>problematic to use them not only outside offer/answer, but 
>>also within 
>>offer/answer if I want to support receiving media prior to 
>>receiving the 
>>answer.
>>    
>>
>[JRE] Is this an argument for saying that we need to be able to group media
>as equals even if they have diffent addresses?
>  
>
It's certainly a solution (and probably the easiest and most backwards 
compatible one too) to the problem of supporting "incompatible" profiles 
and media before receiving an answer at the same time, and based on all 
the discussions that have been (and still are) going on around avoiding 
preconditions, it seems solving this problem is a real-life requirement.

-- Flemming

><snip/>
>
>John
>
>  
>

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



From mmusic-bounces@ietf.org Fri Jan 20 08:35:06 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzwPy-0003rt-Uc; Fri, 20 Jan 2006 08:35:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzwPw-0003ro-Tm
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 08:35:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12847
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 08:33:38 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EzwYg-0004Q0-5S
	for mmusic@ietf.org; Fri, 20 Jan 2006 08:44:07 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 20 Jan 2006 05:34:54 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k0KDYsWF022435;
	Fri, 20 Jan 2006 05:34:54 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 20 Jan 2006 05:34:54 -0800
Received: from [10.21.120.177] ([10.21.120.177]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 20 Jan 2006 05:34:53 -0800
Message-ID: <43D0E6FC.3050302@cisco.com>
Date: Fri, 20 Jan 2006 08:34:52 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: Sharing ports between "m=" lines [Was Re: [MMUSIC] Re: Questi
	onon sdp-new}
References: <200601192013.k0JKDKjt010462@sj-core-5.cisco.com>
In-Reply-To: <200601192013.k0JKDKjt010462@sj-core-5.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jan 2006 13:34:53.0606 (UTC)
	FILETIME=[4B9EB460:01C61DC6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: 'Joerg Ott' <jo@netlab.hut.fi>, "'Elwell, John'" <john.elwell@siemens.com>,
	mmusic@ietf.org, M.Handley@cs.ucl.ac.uk,
	'Colin Perkins' <csp@csperkins.org>, van@packetdesign.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org



Dan Wing wrote:

>>I will just comment on one point:
>>
>><snip/> 
>>    
>>
>>>I like the capabilities I get by using the triple <IP address,
>>>port number, media type>, but it leaves open some issues, which I
>>>think the current sdp-new text was trying to avoid (and which you
>>>address below).  For example, if I indicate RTP/AVP and RTP/SAVP
>>>as alternatives and I now receive a media packet, which profile is
>>>it actually encoded under ? Do payload type mappings have to be
>>>the same between these alternatives ? In general, once I allow for
>>>quite a bit of variability in the parameters included in these
>>>alternatives, it becomes potentially problematic to use them not
>>>only outside offer/answer, but also within offer/answer if I want
>>>to support receiving media prior to receiving the answer.
>>>      
>>>
>>[JRE] Is this an argument for saying that we need to be able to
>>group media as equals even if they have diffent addresses?
>>    
>>
>
>RFC4091 does that already -- it groups media lines as equal even 
>when those media lines have different addresses.  RFC4091 restricts
>itself to grouping IPv4 and IPv6 addresses, though.
>  
>
Right. More precisely:
<quote>
   The ANAT semantics MUST NOT be used to group media streams whose
   network addresses are of the same type.
</quote>
Thus RFC 4091 does not solve the general case John describes above (e.g. 
two different profiles both using IPv4 addresses).

-- Flemming

>-d
>
>  
>

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



From mmusic-bounces@ietf.org Fri Jan 20 10:27:08 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzyAN-0000Fm-W5; Fri, 20 Jan 2006 10:27:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzyAM-0000Fh-H1
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 10:27:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21386
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 10:25:38 -0500 (EST)
Received: from mail.icgcomm.com ([204.32.218.26] helo=denexg15.icgcomm.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EzyJ6-0007xB-LC
	for mmusic@ietf.org; Fri, 20 Jan 2006 10:36:10 -0500
Received: from Hagens1 ([10.138.85.33]) by denexg15.icgcomm.com with Microsoft
	SMTPSVC(6.0.3790.211); Fri, 20 Jan 2006 08:26:37 -0700
From: "Robert Hagens" <rhagens@envysion.com>
To: "'Patankar, Sujay'" <spatankar@starentnetworks.com>, <mmusic@ietf.org>
Subject: RE: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?
Date: Fri, 20 Jan 2006 08:27:35 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYdIYND3uwBncIDRxusBLtusscTEwAEtM+AABER1RAAFymssA==
In-Reply-To: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
Message-ID: <DENEXG15vIPNTAbAWFs00000521@denexg15.icgcomm.com>
X-OriginalArrivalTime: 20 Jan 2006 15:26:37.0820 (UTC)
	FILETIME=[E7A493C0:01C61DD5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hello,

Regarding (1), I interpret section 9.2 of the 2.0 draft
	"A persistent connection MAY be used for all
	transactions between the server and client, including messages to
multiple RTSP sessions"
to mean that you can run multiple sessions on the same transport. The
comment in section 9.3 regarding closing connections I think should answer
your third question as well ("The server, however, SHOULD NOT close a
connection until all RTSP sessions being managed through the 	connection
have been timed out")

Hope this helps,

Rob

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Patankar, Sujay
Sent: Thursday, January 19, 2006 9:33 PM
To: mmusic@ietf.org
Subject: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?

Hi,
I had a couple of questions about RTSP. I'll be greatly thankful to
anyone who answers them.

1:  Can there be more than one RTSP session-ids in simultaneous use over
a single TCP connection between a client and a server? (I mean over the
same {src IP, src port} and {dst IP, dst port} pair) If I receive, for
example, a request or response w/o a session ID, can I safely assume
that it belongs the same session id as that was present in other RTSP
messages seen on this TCP connection?

2: The RTSP RFC (2326) states that the session id is required in all
requests as well as responses except the OPTIONS and SETUP requests.
However, I have seen a RealPlayer receiving a 200 reply to a PLAY. The
200 OK reply didn't contain any session id. (it had the matching CSeq
though) I was under the impression that every reply MUST contain a
session id.

3: If multiple session ids can be in use on the same TCP connection at
the same time, what happens when one of the sessions does a TEARDOWN?
Will the TCP connection be torn down? What will the other sessions do in
such case? Does an RTSP TEARDOWN always involve a TCP connection
teardown?

Thanks in advance for any help,
Sujay.

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


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



From mmusic-bounces@ietf.org Fri Jan 20 10:34:53 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzyHt-0002h0-4A; Fri, 20 Jan 2006 10:34:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzyHr-0002gv-AZ
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 10:34:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22209
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 10:33:23 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzyQW-0008Jn-UG
	for mmusic@ietf.org; Fri, 20 Jan 2006 10:43:54 -0500
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A8C4F4F0001
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 16:34:34 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Jan 2006 16:34:34 +0100
Received: from [147.214.34.70] ([147.214.34.70]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 20 Jan 2006 16:34:34 +0100
Message-ID: <43D1030A.5070209@ericsson.com>
Date: Fri, 20 Jan 2006 16:34:34 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?
References: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
In-Reply-To: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jan 2006 15:34:34.0614 (UTC)
	FILETIME=[03D59160:01C61DD7]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Patankar, Sujay wrote:
> Hi,
> I had a couple of questions about RTSP. I'll be greatly thankful to
> anyone who answers them.
> 
> 1:  Can there be more than one RTSP session-ids in simultaneous use over
> a single TCP connection between a client and a server? (I mean over the
> same {src IP, src port} and {dst IP, dst port} pair) If I receive, for
> example, a request or response w/o a session ID, can I safely assume
> that it belongs the same session id as that was present in other RTSP
> messages seen on this TCP connection?
> 

One may send more control traffic for more than one session over the
same TCP connection. Some RTSP 1.0 servers may not like it, but the
specification allows for it. You can not assume that any request
received over the TCP connection is for a already established
connection. If they are related or not is indicated in each request by
the inclusion of the session header. For example A SETUP request without
a session header creates a new session, while one with binds that media
into the aggregated session identified.

It is the recommend procedure for a proxy that connects several clients
to the same server in RTSP 2.0. B

> 2: The RTSP RFC (2326) states that the session id is required in all
> requests as well as responses except the OPTIONS and SETUP requests.
> However, I have seen a RealPlayer receiving a 200 reply to a PLAY. The
> 200 OK reply didn't contain any session id. (it had the matching CSeq
> though) I was under the impression that every reply MUST contain a
> session id.

Then they are breaking the following normative statement in section
12.37 of RFC 2326:

Once a client receives a Session
    identifier, it MUST return it for any request related to that
    session.

> 
> 3: If multiple session ids can be in use on the same TCP connection at
> the same time, what happens when one of the sessions does a TEARDOWN?
> Will the TCP connection be torn down? What will the other sessions do in
> such case? Does an RTSP TEARDOWN always involve a TCP connection
> teardown?

If I remember correctly this is a bit unclear. However an TEARDOWN must
indicate which session and resource the TEARDOWN is for. An TEARDOWN
with a media URI indicates that only the media should be removed from
the session, not the complete session. If the session URI is used, then
the whole session identified is removed.

Cheers

Magnus Westerlund

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


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



From mmusic-bounces@ietf.org Fri Jan 20 10:37:30 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzyKQ-0003lG-Mg; Fri, 20 Jan 2006 10:37:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzyKP-0003l0-7H
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 10:37:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22714
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 10:36:01 -0500 (EST)
Received: from mail.icgcomm.com ([204.32.218.26] helo=denexg15.icgcomm.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EzyTA-0008Vw-CW
	for mmusic@ietf.org; Fri, 20 Jan 2006 10:46:32 -0500
Received: from Hagens1 ([10.138.85.33]) by denexg15.icgcomm.com with Microsoft
	SMTPSVC(6.0.3790.211); Fri, 20 Jan 2006 08:37:18 -0700
From: "Robert Hagens" <rhagens@envysion.com>
To: <mmusic@ietf.org>
Date: Fri, 20 Jan 2006 08:38:16 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYd14ffgkRQCWrnQkKceiXDdgudxg==
Message-ID: <DENEXG15yD7TfSr0fVw00000527@denexg15.icgcomm.com>
X-OriginalArrivalTime: 20 Jan 2006 15:37:18.0965 (UTC)
	FILETIME=[65CB8A50:01C61DD7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f6ef73100908d67495ce675c3fe8f472
Subject: [MMUSIC] RTSP server behind NAT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0688114559=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0688114559==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_043B_01C61D9C.DBAE3A50"

This is a multi-part message in MIME format.

------=_NextPart_000_043B_01C61D9C.DBAE3A50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Does anyone have any thoughts about the following scenario?

 

The RTSP server is behind a NAT

Client is publicly routable

No ALG is deployed (to be compatible with the thousands of NATs deployed
today)

Don't want to configure port forwarding on the NAT

 

This problem definition has led me to imagine that SIP is used to 

negotiate the media. Via SIP I could create the situation where the 

RTSP server and client both know about an SDP that has been 

negotiated. The problem is that I can't get the RTSP transport connection
established.

 

If RTSP/UDP was not deprecated, that might be an option, as you could 

use something like STUN to open the UDP pinhole in the firewall to 

allow the RTSP messages in. 

 

I've thought about having the RTSP server initiate the TCP connection 

outbound to the client, somewhat akin to RFC 4145/draft-sip-outbound. 

That might work, but I need a way for the RTSP client to identify the 

server that just connected via TCP. (or TLS). Maybe OPTIONS ? STUN over the
transport

connection to an embedded STUN server in the client?

 

This may seem like a wacky scenario, but I think it could become prevalent
as

people deploy home media servers over typical residential broadband.

 

Thanks,


Rob

 


------=_NextPart_000_043B_01C61D9C.DBAE3A50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Does anyone have =
any
thoughts about the following scenario?<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-indent:.5in;text-autospace:none'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>The
RTSP server is behind a NAT<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-indent:.5in;text-autospace:none'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Client
is publicly routable<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-indent:.5in;text-autospace:none'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>No
ALG is deployed (to be compatible with the thousands of NATs deployed =
today)<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-indent:.5in;text-autospace:none'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Don&#8217;t
want to configure port forwarding on the =
NAT<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>This problem =
definition has
led me to imagine that SIP is used to <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>negotiate the =
media. Via SIP
I could create the situation where the <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>RTSP server and =
client both
know about an SDP that has been <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>negotiated. The =
problem is
that I can't get the RTSP transport connection =
established.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>If RTSP/UDP was not
deprecated, that might be an option, as you could =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>use something like =
STUN to
open the UDP pinhole in the firewall to <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>allow the RTSP =
messages in. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>I've thought about =
having
the RTSP server initiate the TCP connection =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>outbound to the =
client,
somewhat akin to RFC 4145/draft-sip-outbound. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>That might work, =
but I need
a way for the RTSP client to identify the <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>server that just =
connected
via TCP. (or TLS). Maybe OPTIONS ? STUN over the =
transport<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>connection to an =
embedded
STUN server in the client?<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>This may seem like =
a wacky
scenario, but I think it could become prevalent =
as<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>people deploy home =
media
servers over typical residential =
broadband&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
Rob<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_043B_01C61D9C.DBAE3A50--



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

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

--===============0688114559==--





From mmusic-bounces@ietf.org Fri Jan 20 10:54:11 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzyaZ-0004bu-NP; Fri, 20 Jan 2006 10:54:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzyaY-0004bp-7j
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 10:54:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24708
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 10:52:42 -0500 (EST)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly10d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzyjI-0000sB-78
	for mmusic@ietf.org; Fri, 20 Jan 2006 11:03:14 -0500
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly10d.srv.mailcontrol.com (MailControl) with SMTP id
	k0KFrhTX004129; Fri, 20 Jan 2006 15:53:43 GMT
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 2dfd_ad2886be_89c5_11da_9003_0030482aac25;
	Fri, 20 Jan 2006 16:01:45 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.2)
	with ESMTP id 2006012016533801-80797 ;
	Fri, 20 Jan 2006 16:53:38 +0100 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Fri, 20 Jan 2006 16:56:19 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [MMUSIC] RTSP server behind NAT
Thread-Topic: [MMUSIC] RTSP server behind NAT
Thread-Index: AcYd14ffgkRQCWrnQkKceiXDdgudxgAAYN+A
To: "Robert Hagens" <rhagens@envysion.com>, <mmusic@ietf.org>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F7D5806@lan-ex-01.panasonic.de>
Date: Fri, 20 Jan 2006 16:53:30 +0100
From: "Jose Rey" <Jose.Rey@eu.panasonic.com>
Content-class: urn:content-classes:message
X-Scanned-By: MailControl A-05-40-01 (www.mailcontrol.com) on 10.68.0.120
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 918f4bd8440e8de4700bcf6d658bc801
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1143202349=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1143202349==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61DD9.AB28A74B"

This is a multi-part message in MIME format.

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

Hi,
=20

=20

	Does anyone have any thoughts about the following scenario?

	=20

	The RTSP server is behind a NAT

	Client is publicly routable

	No ALG is deployed (to be compatible with the thousands of NATs =
deployed today)

	Don't want to configure port forwarding on the NAT

	=20

	This problem definition has led me to imagine that SIP is used to=20

	negotiate the media. Via SIP I could create the situation where the=20

	RTSP server and client both know about an SDP that has been=20

	negotiated. The problem is that I can't get the RTSP transport =
connection established.=20

	=20

	Have you looked at=20

	"How to make RTSP traverse NAT & FW" =
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-nat-04.txt?=20

	=20

	If RTSP/UDP was not deprecated, that might be an option, as you could=20

	use something like STUN to open the UDP pinhole in the firewall to=20

	allow the RTSP messages in.=20

	=20

	I've thought about having the RTSP server initiate the TCP connection=20

	outbound to the client, somewhat akin to RFC 4145/draft-sip-outbound.=20

	That might work, but I need a way for the RTSP client to identify the=20

	server that just connected via TCP. (or TLS). Maybe OPTIONS ? STUN over =
the transport

	connection to an embedded STUN server in the client?

	=20

	This may seem like a wacky scenario, but I think it could become =
prevalent as

	people deploy home media servers over typical residential broadband...=20

	=20

	I think so too...=20

=09
	Cheers,
	Jos=E9

	=20

	=20

	I find it

	=20

	Thanks,

=09
	Rob

	=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR>
<STYLE>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Courier New" color=3D#008080 =
size=3D2><SPAN=20
class=3D252064915-20012006>Hi,</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" color=3D#008080 =
size=3D2></FONT><BR>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008080 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Does anyone have =
any=20
  thoughts about the following scenario?<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 0.5in"><FONT =
face=3D"Courier New"=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">The RTSP=20
  server is behind a NAT<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 0.5in"><FONT =
face=3D"Courier New"=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Client is=20
  publicly routable<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 0.5in"><FONT =
face=3D"Courier New"=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">No ALG is=20
  deployed (to be compatible with the thousands of NATs deployed=20
  today)<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 0.5in"><FONT =
face=3D"Courier New"=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Don=92t want to=20
  configure port forwarding on the NAT<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">This problem =
definition=20
  has led me to imagine that SIP is used to =
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">negotiate the =
media. Via=20
  SIP I could create the situation where the =
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">RTSP server and =
client=20
  both know about an SDP that has been <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">negotiated. The =
problem is=20
  that I can't get the RTSP transport connection established.<FONT=20
  color=3D#008080><SPAN =
class=3D252064915-20012006>&nbsp;</SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006>Have you looked&nbsp;at </P><PRE>"How to =
make RTSP traverse NAT &amp; FW" <A =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-nat-04=
.txt">http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rtsp-nat-04.t=
xt</A>? </PRE></SPAN></FONT></SPAN>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">If RTSP/UDP was =
not=20
  deprecated, that might be an option, as you could=20
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">use something =
like STUN to=20
  open the UDP pinhole in the firewall to <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">allow the RTSP =
messages=20
  in. <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">I've thought =
about having=20
  the RTSP server initiate the TCP connection =
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">outbound to the =
client,=20
  somewhat akin to RFC 4145/draft-sip-outbound. =
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">That might work, =
but I=20
  need a way for the RTSP client to identify the =
<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">server that just =
connected=20
  via TCP. (or TLS). Maybe OPTIONS ? STUN over the=20
  transport<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">connection to an =
embedded=20
  STUN server in the client?<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">This may seem =
like a wacky=20
  scenario, but I think it could become prevalent=20
as<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">people deploy =
home media=20
  servers over typical residential broadband=85<FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006>&nbsp;</SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006>I think so =
too...&nbsp;</SPAN></FONT></SPAN></P><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><FONT =
color=3D#008080><SPAN=20
  class=3D252064915-20012006><PRE>Cheers,</PRE><PRE>Jos=E9</PRE>
  <P class=3DMsoNormal>&nbsp;</SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><o:p><SPAN=20
  class=3D252064915-20012006>I find it</SPAN></o:p></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">Thanks,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><BR>Rob<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML=
>

------_=_NextPart_001_01C61DD9.AB28A74B--



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

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

--===============1143202349==--





From mmusic-bounces@ietf.org Fri Jan 20 12:19:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ezzuq-0001CR-T0; Fri, 20 Jan 2006 12:19:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ezzuo-0001BY-9u
	for mmusic@megatron.ietf.org; Fri, 20 Jan 2006 12:19:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01887
	for <mmusic@ietf.org>; Fri, 20 Jan 2006 12:17:40 -0500 (EST)
Received: from flawless.real.com ([207.188.23.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F003V-0003sR-Cu
	for mmusic@ietf.org; Fri, 20 Jan 2006 12:28:13 -0500
Received: from d845pebt2_xp.real.com ([::ffff:172.22.143.254])
	(AUTH: LOGIN rmathew, SSL: TLSv1/SSLv3,168bits,DES-CBC3-SHA)
	by flawless.real.com with esmtp; Fri, 20 Jan 2006 09:18:33 -0800
	id 001CD5E9.43D11B69.00006B6A
Message-Id: <6.2.1.2.2.20060120091516.047ffdc0@mailone.real.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Fri, 20 Jan 2006 09:18:52 -0800
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	"mmusic (E-mail)" <mmusic@ietf.org>
From: Rishi Mathew <rmathew@real.com>
Subject: Re: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?
In-Reply-To: <43D1030A.5070209@ericsson.com>
References: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
	<43D1030A.5070209@ericsson.com>
Mime-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1899556232=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--===============1899556232==
Content-Type: multipart/alternative;
	boundary="=_flawless.real.com-27498-1137777513-0001-2"

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_flawless.real.com-27498-1137777513-0001-2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

At 07:34 AM 1/20/2006, Magnus Westerlund wrote:
>Patankar, Sujay wrote:
>>Hi,
>>I had a couple of questions about RTSP. I'll be greatly thankful to
>>anyone who answers them.
>>1:  Can there be more than one RTSP session-ids in simultaneous use over
>>a single TCP connection between a client and a server? (I mean over the
>>same {src IP, src port} and {dst IP, dst port} pair) If I receive, for
>>example, a request or response w/o a session ID, can I safely assume
>>that it belongs the same session id as that was present in other RTSP
>>messages seen on this TCP connection?
>
>One may send more control traffic for more than one session over the
>same TCP connection. Some RTSP 1.0 servers may not like it, but the
>specification allows for it. You can not assume that any request
>received over the TCP connection is for a already established
>connection. If they are related or not is indicated in each request by
>the inclusion of the session header. For example A SETUP request without
>a session header creates a new session, while one with binds that media
>into the aggregated session identified.
>
>It is the recommend procedure for a proxy that connects several clients
>to the same server in RTSP 2.0. B
>
>>2: The RTSP RFC (2326) states that the session id is required in all
>>requests as well as responses except the OPTIONS and SETUP requests.
>>However, I have seen a RealPlayer receiving a 200 reply to a PLAY. The
>>200 OK reply didn't contain any session id. (it had the matching CSeq
>>though) I was under the impression that every reply MUST contain a
>>session id.
>
>Then they are breaking the following normative statement in section
>12.37 of RFC 2326:

Not true! Atul's statement is that "I have seen a RealPlayer receiving a 
200 reply to a PLAY. The 200 OK reply didn't contain any session id." Which 
means that he is seeing the absence of a session-id in the 
response(generated by the server) not the request.  In any case, the 
session-id is not a necessity in the PLAY response.

-Rishi.


>Once a client receives a Session
>    identifier, it MUST return it for any request related to that
>    session.
>
>>3: If multiple session ids can be in use on the same TCP connection at
>>the same time, what happens when one of the sessions does a TEARDOWN?
>>Will the TCP connection be torn down? What will the other sessions do in
>>such case? Does an RTSP TEARDOWN always involve a TCP connection
>>teardown?
>
>If I remember correctly this is a bit unclear. However an TEARDOWN must
>indicate which session and resource the TEARDOWN is for. An TEARDOWN
>with a media URI indicates that only the media should be removed from
>the session, not the complete session. If the session URI is used, then
>the whole session identified is removed.
>
>Cheers
>
>Magnus Westerlund
>
>Multimedia Technologies, Ericsson Research EAB/TVA/A
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


Rishi Mathew
Software Development Engineer
Helix Community
RealNetworks, Inc.
rmathew@real.com
http://www.helixcommunity.org
http://www.realnetworks.com/products/support/devsupport.html

--=_flawless.real.com-27498-1137777513-0001-2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<body>
At 07:34 AM 1/20/2006, Magnus Westerlund wrote:<br>
<blockquote type=cite class=cite cite="">Patankar, Sujay wrote:<br>
<blockquote type=cite class=cite cite="">Hi,<br>
I had a couple of questions about RTSP. I'll be greatly thankful to<br>
anyone who answers them.<br>
1:&nbsp; Can there be more than one RTSP session-ids in simultaneous use
over<br>
a single TCP connection between a client and a server? (I mean over
the<br>
same {src IP, src port} and {dst IP, dst port} pair) If I receive,
for<br>
example, a request or response w/o a session ID, can I safely assume<br>
that it belongs the same session id as that was present in other
RTSP<br>
messages seen on this TCP connection?<br>
</blockquote><br>
One may send more control traffic for more than one session over the<br>
same TCP connection. Some RTSP 1.0 servers may not like it, but the<br>
specification allows for it. You can not assume that any request<br>
received over the TCP connection is for a already established<br>
connection. If they are related or not is indicated in each request
by<br>
the inclusion of the session header. For example A SETUP request
without<br>
a session header creates a new session, while one with binds that
media<br>
into the aggregated session identified.<br><br>
It is the recommend procedure for a proxy that connects several
clients<br>
to the same server in RTSP 2.0. B<br><br>
<blockquote type=cite class=cite cite="">2: The RTSP RFC (2326) states
that the session id is required in all<br>
requests as well as responses except the OPTIONS and SETUP requests.<br>
However, I have seen a RealPlayer receiving a 200 reply to a PLAY.
The<br>
200 OK reply didn't contain any session id. (it had the matching
CSeq<br>
though) I was under the impression that every reply MUST contain a<br>
session id.</blockquote><br>
Then they are breaking the following normative statement in section<br>
12.37 of RFC 2326:</blockquote><br>
Not true! Atul's statement is that &quot;I have seen a RealPlayer
<b>receiving </b>a 200 reply to a PLAY. The 200 OK reply didn't contain
any session id.&quot; Which means that he is seeing the absence of a
session-id in the response(generated by the server) not the
request.&nbsp; In any case, the session-id is not a necessity in the PLAY
response.<br><br>
-Rishi.<br><br>
<br>
<blockquote type=cite class=cite cite="">Once a client receives a
Session<br>
&nbsp;&nbsp; identifier, it MUST return it for any request related to
that<br>
&nbsp;&nbsp; session.<br><br>
<blockquote type=cite class=cite cite="">3: If multiple session ids can
be in use on the same TCP connection at<br>
the same time, what happens when one of the sessions does a
TEARDOWN?<br>
Will the TCP connection be torn down? What will the other sessions do
in<br>
such case? Does an RTSP TEARDOWN always involve a TCP connection<br>
teardown?</blockquote><br>
If I remember correctly this is a bit unclear. However an TEARDOWN
must<br>
indicate which session and resource the TEARDOWN is for. An TEARDOWN<br>
with a media URI indicates that only the media should be removed
from<br>
the session, not the complete session. If the session URI is used,
then<br>
the whole session identified is removed.<br><br>
Cheers<br><br>
Magnus Westerlund<br><br>
Multimedia Technologies, Ericsson Research EAB/TVA/A<br>
----------------------------------------------------------------------<br>
Ericsson
AB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| Phone +46 8 4048287<br>
Torshamsgatan
23&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
Fax&nbsp;&nbsp; +46 8 7575550<br>
S-164 80 Stockholm, Sweden | mailto:
magnus.westerlund@ericsson.com<br><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
mmusic@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/mmusic" eudora="autourl">
https://www1.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote>
<x-sigsep><p></x-sigsep>
<br>
<font size=2><b>Rishi Mathew<br>
</b>Software Development Engineer<br>
Helix Community<br>
</font><font size=2 color="#0000FF"><b>Real</b></font><font size=2>
Networks, Inc. <br>
rmathew@real.com <br>
</font><font size=2 color="#0000FF"><u>
<a href="http://www.helixcommunity.org/" eudora="autourl">
http://www.helixcommunity.org<br>
</a>
<a href="http://www.realnetworks.com/products/support/devsupport.html" eudora="autourl">
http://www.realnetworks.com/products/support/devsupport.html<br>
</a></font></u></body>
</html>

--=_flawless.real.com-27498-1137777513-0001-2--


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

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

--===============1899556232==--




From mmusic-bounces@ietf.org Mon Jan 23 03:43:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F0xIm-00022Q-Jg; Mon, 23 Jan 2006 03:43:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0xIl-00022I-Gg
	for mmusic@megatron.ietf.org; Mon, 23 Jan 2006 03:43:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28591
	for <mmusic@ietf.org>; Mon, 23 Jan 2006 03:42:21 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0xS0-0005Zy-NE
	for mmusic@ietf.org; Mon, 23 Jan 2006 03:53:29 -0500
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 12DB4AAE; 
	Mon, 23 Jan 2006 09:43:28 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 23 Jan 2006 09:43:28 +0100
Received: from [147.214.34.70] ([147.214.34.70]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 23 Jan 2006 09:43:27 +0100
Message-ID: <43D4972E.4080500@ericsson.com>
Date: Mon, 23 Jan 2006 09:43:26 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rishi Mathew <rmathew@real.com>
Subject: Re: [MMUSIC] simultaneous RTSP sessions over the same TCP connection?
References: <CF406A890CCCA14E9543EAFBE3A2C2D1071250@EXCHINDIA2.starentnetworks.com>
	<43D1030A.5070209@ericsson.com>
	<6.2.1.2.2.20060120091516.047ffdc0@mailone.real.com>
In-Reply-To: <6.2.1.2.2.20060120091516.047ffdc0@mailone.real.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jan 2006 08:43:27.0562 (UTC)
	FILETIME=[145D62A0:01C61FF9]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Rishi Mathew wrote:
> At 07:34 AM 1/20/2006, Magnus Westerlund wrote:
> 
>> Patankar, Sujay wrote:
>>
>>> Hi,
>>> I had a couple of questions about RTSP. I'll be greatly thankful to
>>> anyone who answers them.
>>> 1:  Can there be more than one RTSP session-ids in simultaneous use over
>>> a single TCP connection between a client and a server? (I mean over the
>>> same {src IP, src port} and {dst IP, dst port} pair) If I receive, for
>>> example, a request or response w/o a session ID, can I safely assume
>>> that it belongs the same session id as that was present in other RTSP
>>> messages seen on this TCP connection?
>>
>>
>> One may send more control traffic for more than one session over the
>> same TCP connection. Some RTSP 1.0 servers may not like it, but the
>> specification allows for it. You can not assume that any request
>> received over the TCP connection is for a already established
>> connection. If they are related or not is indicated in each request by
>> the inclusion of the session header. For example A SETUP request without
>> a session header creates a new session, while one with binds that media
>> into the aggregated session identified.
>>
>> It is the recommend procedure for a proxy that connects several clients
>> to the same server in RTSP 2.0. B
>>
>>> 2: The RTSP RFC (2326) states that the session id is required in all
>>> requests as well as responses except the OPTIONS and SETUP requests.
>>> However, I have seen a RealPlayer receiving a 200 reply to a PLAY. The
>>> 200 OK reply didn't contain any session id. (it had the matching CSeq
>>> though) I was under the impression that every reply MUST contain a
>>> session id.
>>
>>
>> Then they are breaking the following normative statement in section
>> 12.37 of RFC 2326:
> 
> 
> Not true! Atul's statement is that "I have seen a RealPlayer receiving a 
> 200 reply to a PLAY. The 200 OK reply didn't contain any session id." 
> Which means that he is seeing the absence of a session-id in the 
> response(generated by the server) not the request.  In any case, the 
> session-id is not a necessity in the PLAY response.
> 
Hi Rishi,

Sorry my misstake. You are correct that statment I quoted applies to the 
client, not the server. And as long as any proxy or client is correctly 
made there exist a way of correctly binding the response to the request 
and thus determining which session ID it belongs to. I would however say 
that it is recommended to include the Session header in any response 
that relates to a session.

In RTSP 2.0 as currently proposed it will be required to include the 
session ID in response for SETUP, PLAY, and PAUSE.

Cheers

Magnus Westerlund

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

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



From mmusic-bounces@ietf.org Tue Jan 24 08:49:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1OYK-0003GG-UR; Tue, 24 Jan 2006 08:49:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F0rod-0001P9-4d
	for mmusic@megatron.ietf.org; Sun, 22 Jan 2006 21:52:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07851
	for <mmusic@ietf.org>; Sun, 22 Jan 2006 21:50:54 -0500 (EST)
Received: from web33307.mail.mud.yahoo.com ([68.142.206.122])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F0rxq-0004d6-GJ
	for mmusic@ietf.org; Sun, 22 Jan 2006 22:01:57 -0500
Received: (qmail 10151 invoked by uid 60001); 23 Jan 2006 02:52:10 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=fVjUSlYPqsIjerErJq43stLeETmauHDXTTMzBS8hTZLiSTi82/3wVnlilpBmZSSpV7VlKHCCLlQug2b+prL+h2V+fmANekp9lMmZko2PfNoHJLeR1kuxRETqK+jfUCSGoSvjPOLo87QlBZMH/uz3NlYl9AWWHNjpqv81y/n0fBE=
	; 
Message-ID: <20060123025210.10149.qmail@web33307.mail.mud.yahoo.com>
Received: from [69.236.93.54] by web33307.mail.mud.yahoo.com via HTTP;
	Sun, 22 Jan 2006 18:52:10 PST
Date: Sun, 22 Jan 2006 18:52:10 -0800 (PST)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: jdrosen@cisco.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 24 Jan 2006 08:49:43 -0500
Cc: Pyda Srisuresh <srisuresh@yahoo.com>, mmusic@ietf.org
Subject: [MMUSIC] Comments on draft-ietf-mmusic-ice-06
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Jonathan,

I have a few questions on media flow setup in ICE.

1. It seems all candidate endpoints  for media (including private endpoint,
STUN derived endpoint and TURN derived endpoint) must be prepared to send and
process STUN Binding requests. 

If this is true, dont you think it is overbearing to require media endpoints to
offer STUN service (irrespective of whehter a node is behind a NAT or not) and
multiplex it with the real media content? 

You suggest a way to distinguish STUN messages from RTP/RTCP data from the
first 2 bits of the RTP/RTCP header. This  can be problematic for other media
stream protocols and in general for other P2P applications. Is ICE intended
principally for use with RTP and RTCP only?

2. Say, the two peering nodes are not behind NAT. In such a case, why should
the media endpoints be required to process STUN messages? That adds no value,
right?

Likewise, say, one of the endpoints is relay endpoint and the other is public
endpoint. Why should either of the endpoints be required to process STUN
messages? I.e., Once again, I donot see the value in exchanging STUN messages
between the endpoints. Might as well not bother with STUN messages and simply
exchange media between the endpoints.

3. Say, both nodes are behind Cone NAT devices. How can you ensure that STUN
Binding request sent by one node is received by the peer node or vice versa.
There is a chance that this might succeed only if they both parties try sending
at the same time. But, I dont see how you can ensure that in that in the
connectivity model.

4. Lastly, if both nodes are behind cone NAT, and each node has 3 candidate
endpoints (private endpoint, STUN derived endpoint and TURN derived endpoint),
I believe, the connection between TURN derived endpoints is most likely to
succeed at the earliest. DO you agree? If not, please explain why.

Thanks.

regards,
suresh



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



From mmusic-bounces@ietf.org Wed Jan 25 04:19:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1gjD-0002JY-L6; Wed, 25 Jan 2006 04:14:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1gjB-0002JQ-4J
	for mmusic@megatron.ietf.org; Wed, 25 Jan 2006 04:14:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22961
	for <mmusic@ietf.org>; Wed, 25 Jan 2006 04:12:37 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1gsp-0008Ty-Ni
	for mmusic@ietf.org; Wed, 25 Jan 2006 04:24:12 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 41D3D101B
	for <mmusic@ietf.org>; Wed, 25 Jan 2006 10:14:01 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jan 2006 10:14:00 +0100
Received: from [147.214.34.70] ([147.214.34.70]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 25 Jan 2006 10:14:00 +0100
Message-ID: <43D74158.5040401@ericsson.com>
Date: Wed, 25 Jan 2006 10:14:00 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: multipart/mixed; boundary="------------050506010501020403010306"
X-OriginalArrivalTime: 25 Jan 2006 09:14:00.0589 (UTC)
	FILETIME=[ADC29BD0:01C6218F]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Subject: [MMUSIC] [Fwd: [AVT] Working Group Last Call:
	draft-ietf-avt-profile-savpf-05.txt]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org


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

Hi MMUSIC participants,

I would like to inform all of you about this WG last call. The reason is 
the rules it proposes for providing alternative RTP profiles in SDP. 
Please see section 3 of the draft. Please send any comments to the AVT list.

Cheers

Magnus Westerlund
AVT Chair

--------------050506010501020403010306
Content-Type: message/rfc822; name*0="[AVT] Working Group Last Call:
	draft-ietf-avt-profile-savpf-05.t"; name*1="xt"
Content-Disposition: inline; filename*0="[AVT] Working Group Last Call:
	draft-ietf-avt-profile-savpf-"; filename*1="05.txt"

Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jan 2006 16:34:52 +0100
Received: from esealmw126.eemea.ericsson.se ([130.100.184.161]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jan 2006 16:34:52 +0100
Received: from mailgw1.ericsson.se ([193.180.251.59]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jan 2006 16:34:52 +0100
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by mailgw1.ericsson.se (Symantec Mail Security) with ESMTP id 663284DC; 
	Tue, 24 Jan 2006 16:34:50 +0100 (CET)
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1QAC-0006Tx-Jd; Tue, 24 Jan 2006 10:32:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1QAA-0006Tf-Co
	for avt@megatron.ietf.org; Tue, 24 Jan 2006 10:32:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21850
	for <avt@ietf.org>; Tue, 24 Jan 2006 10:31:22 -0500 (EST)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1QJg-000725-Ef
	for avt@ietf.org; Tue, 24 Jan 2006 10:42:47 -0500
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7DF794F0002 for <avt@ietf.org>; Tue, 24 Jan 2006 16:32:48 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jan 2006 16:32:48 +0100
Received: from [147.214.34.70] ([147.214.34.70]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jan 2006 16:32:48 +0100
Message-ID: <43D648A0.9020405@ericsson.com>
Date: Tue, 24 Jan 2006 16:32:48 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 24 Jan 2006 15:32:48.0068 (UTC)
	FILETIME=[6DFAF040:01C620FB]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [AVT] Working Group Last Call: draft-ietf-avt-profile-savpf-05.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>,
	<mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Return-Path: avt-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is to announce a 2 week working group last call on the Extended 
Secure RTP Profile for RTCP-based Feedback (RTP/SAVPF). Please send any 
final comments on  this draft to the AVT mailing list by 7th February 
2006. If no substantive issues are raised by that time, we will request 
that the IESG consider this draft for publication as a proposed standard.

http://www.ietf.org/internet-drafts/draft-ietf-avt-profile-savpf-05.txt

Cheers

Magnus Westerlund
AVT Chair

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

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt


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

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

--------------050506010501020403010306--




From mmusic-bounces@ietf.org Wed Jan 25 18:50:41 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1uPR-0001yR-8T; Wed, 25 Jan 2006 18:50:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1uOr-0001oP-Ht; Wed, 25 Jan 2006 18:50:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05181;
	Wed, 25 Jan 2006 18:48:33 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F1uYf-0006xS-Kh; Wed, 25 Jan 2006 19:00:14 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1F1uOo-00051j-7I; Wed, 25 Jan 2006 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F1uOo-00051j-7I@newodin.ietf.org>
Date: Wed, 25 Jan 2006 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-new-26.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

--NextPart

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

	Title		: SDP: Session Description Protocol
	Author(s)	: M. Handley, et al.
	Filename	: draft-ietf-mmusic-sdp-new-26.txt
	Pages		: 49
	Date		: 2006-1-25
	
This memo defines the Session Description Protocol (SDP).  SDP is
   intended for describing multimedia sessions for the purposes of
   session announcement, session invitation, and other forms of
   multimedia session initiation.

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

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


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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-new-26.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mmusic-bounces@ietf.org Wed Jan 25 19:35:55 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1v7D-0006AS-4r; Wed, 25 Jan 2006 19:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1v7C-00069o-BD
	for mmusic@megatron.ietf.org; Wed, 25 Jan 2006 19:35:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17595
	for <mmusic@ietf.org>; Wed, 25 Jan 2006 19:34:22 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1vH0-0003K6-OA
	for mmusic@ietf.org; Wed, 25 Jan 2006 19:46:05 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61647
	helo=[192.168.0.3])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1F1v6q-0003ve-Rs; Thu, 26 Jan 2006 00:35:33 +0000
In-Reply-To: <E1F1uOo-00051j-7I@newodin.ietf.org>
References: <E1F1uOo-00051j-7I@newodin.ietf.org>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <65F7A9D2-79B3-462F-9151-305CF5FA83A3@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-new-26.txt 
Date: Thu, 26 Jan 2006 00:35:39 +0000
To: Jon Peterson <jon.peterson@neustar.biz>, Allison Mankin <mankin@psg.com>, 
	=?ISO-8859-1?Q?J=F6rg_Ott?= <jo@netlab.hut.fi>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC working group <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

On 25 Jan 2006, at 23:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
> This draft is a work item of the Multiparty Multimedia Session  
> Control Working Group of the IETF.
>
> 	Title		: SDP: Session Description Protocol
> 	Author(s)	: M. Handley, et al.
> 	Filename	: draft-ietf-mmusic-sdp-new-26.txt
> 	Pages		: 49
> 	Date		: 2006-1-25
> 	
> This memo defines the Session Description Protocol (SDP).  SDP is
>    intended for describing multimedia sessions for the purposes of
>    session announcement, session invitation, and other forms of
>    multimedia session initiation.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-26.txt

This version is intended to address the GenART comments received  
during IESG review (http://www.alvestrand.no/ietf/gen/reviews/draft- 
ietf-mmusic-sdp-new-25-dawkins.txt). In addition the discussion of  
sharing ports between "m=" lines has been removed from section 5.14,  
since there was no consensus on that approach.

A complete list of changes is as follows:

- Fix reference to H.332 ([15] -> [25])
- Section 1: clarify that this obsoletes RFC 2327 and RFC 3266, rather
   than just updating RFC 2327.
- Section 3: mention that SDP is used by SIP/RTSP use before mentioning
   its use with SAP.  No longer comment that SAP is "commonly used", and
   remove the mention of SAP when discussing use of SDP with email/WWW.
- Section 4: clarify that sessions need not be continually active.
- Section 4.1: explain why it it NOT RECOMMENDED to redefine the  
semantics
   of the destination address/port. Correct use of RFC 2119 terms.
- Section 4.2: add cross reference to section 5.9
- Section 4.3: grammar fixes
- Section 4.5: add cross reference to "a=cat:" in section 6
- Section 5: correct use of RFC 2119 terms in penultimate paragraph  
(`the
   presence of the "a=charset" attribute MAY force' -> `...may  
force...')
- Section 5.2: clarify what is meant by "A local IP address MUST NOT be
   used in any context where the SDP description might leave the  
scope in
   which the address is meaningful"
- Section 5.9: simply note that permanent sessions are discouraged,  
rather
   than giving different degrees of discouragement for differing  
durations
- Section 5.10: simply state that the "s" unit specification  
character is
   allowed for completeness, rather than also stating that its use is  
"NOT
   RECOMMENDED" (the RFC 2119 term is too strong here).
- Section 5.12: clarify that "k=uri:" often uses SSL/TLS-protected HTTP
   (i.e. "https:") and not secure HTTP [RFC2660].
- Section 5.12: remove last sentence of the section, which confused
   operational security with protocol security.
- Section 5.14: remove discussion of sharing ports between "m=" lines,
   and instead not that the semantics of this are currently undefined,
   and that no implicit grouping is implied; add reference to RFC 3388
- Section 6: note that neither "a=cat:" nor "a=keywds:" have a central
   registry of legal values.
- Section 7 (1st paragraph): s/agree/agree on/. Note that SAP is no
   longer frequently used.
- Section 7 (2nd paragraph): clarify the security issues with using  
an SDP
   file obtained via an untrusted transport
- Section 7 (6th paragraph): clarify interactions with intermediary  
systems
   that parse SDP contained in signalling messages

I believe this is now ready to go to the RFC Editor.

Colin

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



From mmusic-bounces@ietf.org Fri Jan 27 17:24:55 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F2c1X-0007YL-H2; Fri, 27 Jan 2006 17:24:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F2c1V-0007Y6-7h
	for mmusic@megatron.ietf.org; Fri, 27 Jan 2006 17:24:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21776
	for <mmusic@ietf.org>; Fri, 27 Jan 2006 17:23:20 -0500 (EST)
Received: from mail.icgcomm.com ([204.32.218.26] helo=denexg15.icgcomm.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F2cBi-0001Vw-3b
	for mmusic@ietf.org; Fri, 27 Jan 2006 17:35:28 -0500
Received: from Hagens1 ([10.138.85.33]) by denexg15.icgcomm.com with Microsoft
	SMTPSVC(6.0.3790.211); Fri, 27 Jan 2006 15:24:18 -0700
From: "Robert Hagens" <rhagens@envysion.com>
To: <mediactrl@lists.ubiquitysoftware.com>, <mmusic@ietf.org>
Date: Fri, 27 Jan 2006 15:25:28 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcYjkJNaEonhZMg+QRC+HgwlqsAfXQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <DENEXG158vWyu9kstC7000002b5@denexg15.icgcomm.com>
X-OriginalArrivalTime: 27 Jan 2006 22:24:18.0785 (UTC)
	FILETIME=[6A089D10:01C62390]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: 
Subject: [MMUSIC] draft-boulton-sip-control-framework-00
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2055638205=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2055638205==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0271_01C62355.E7304350"

This is a multi-part message in MIME format.

------=_NextPart_000_0271_01C62355.E7304350
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Greetings,

 

I am investigating the use of SIP and a control protocol for management of
media. The basic functions I need are typical VCR-like control
(play/pause/.) but I also will need other primitives (like camera control).
I have been working through scenarios of how to use SIP to negotiate the
SDP, in which one media is a control channel which in turn runs RTSP.

 

It occurs to me that one could use this framework to base a control package
to accomplish the VCR-like control. RTSP-lite anyone?

 

My question is, has anyone thought about how such a control package might
relate to a protocol like RTSP? 

 

In particular, I appreciate the section relating this to COMEDIA and the
potential that an external server may initiate the TCP connection. I think
this will help in a wide variety of NAT scenarios (for example, if the media
server is behind a NAT). One item that I am thinking through is how this
might work in practice. If the client sends in its SDP
(a=setup:passive<CRLF>a=connection:new), and subsequently the server
initiates the control connection back to the client, how is the client to
identify which server initiated the TCP connection (assume it was setting
two of these up in parallel)?

 

Thanks in advance for any thoughts on this.

 

Rob Hagens

Envysion

 


------=_NextPart_000_0271_01C62355.E7304350
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

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

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am investigating the use of SIP and a control =
protocol for
management of media. The basic functions I need are typical VCR-like =
control
(play/pause/&#8230;) but I also will need other primitives (like camera
control). I have been working through scenarios of how to use SIP to =
negotiate
the SDP, in which one media is a control channel which in turn runs =
RTSP.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It occurs to me that one could use this framework to =
base a
control package to accomplish the VCR-like control. RTSP-lite =
anyone?<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>My question is, has anyone thought about how such a =
control
package might relate to a protocol like RTSP? =
<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In particular, I appreciate the section relating this =
to
COMEDIA and the potential that an external server may initiate the TCP
connection. I think this will help in a wide variety of NAT scenarios =
(for
example, if the media server is behind a NAT). One item that I am =
thinking
through is how this might work in practice. If the client sends in its =
SDP (a=3Dsetup:passive&lt;CRLF&gt;a=3Dconnection:new),
and subsequently the server initiates the control connection back to the
client, how is the client to identify which server initiated the TCP =
connection
(assume it was setting two of these up in =
parallel)?<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks in advance for any thoughts on =
this&#8230;<o:p></o:p></span></font></p>

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

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0271_01C62355.E7304350--



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

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

--===============2055638205==--





From mmusic-bounces@ietf.org Sun Jan 29 14:04:50 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3Hr0-0005Qh-JQ; Sun, 29 Jan 2006 14:04:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3Hqt-0005PF-Ca; Sun, 29 Jan 2006 14:04:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18790;
	Sun, 29 Jan 2006 14:02:42 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3I13-0008UV-MN; Sun, 29 Jan 2006 14:15:16 -0500
Received: from cnr.cs.columbia.edu (cnr.cs.columbia.edu [128.59.19.133])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id k0TJ48KG026030
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sun, 29 Jan 2006 14:04:08 -0500 (EST)
Received: from cnr.cs.columbia.edu (localhost [127.0.0.1])
	by cnr.cs.columbia.edu (8.13.3/8.13.3) with ESMTP id k0TJ48WI036653;
	Sun, 29 Jan 2006 14:04:08 -0500 (EST)
	(envelope-from lennox@cnr.cs.columbia.edu)
Received: (from lennox@localhost)
	by cnr.cs.columbia.edu (8.13.3/8.13.3/Submit) id k0TJ427k036632;
	Sun, 29 Jan 2006 14:04:02 -0500 (EST) (envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17373.4514.607960.660335@cnr.cs.columbia.edu>
Date: Sun, 29 Jan 2006 14:04:02 -0500
To: mmusic@ietf.org, tls@ietf.org
X-Mailer: VM 7.19 under Emacs 21.3.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, EKR <ekr@networkresonance.com>,
	jon.peterson@neustar.biz, mankin@psg.com
Subject: [MMUSIC] comedia-tls: proposed change for certificate identities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi, all --

I'm working on a revision of draft-ietf-mmusic-comedia-tls following IESG
review.  A preliminary version of the revised draft is available at
<http://www1.cs.columbia.edu/~lennox/draft-ietf-mmusic-comedia-tls-06pre1.html> and
<http://www1.cs.columbia.edu/~lennox/draft-ietf-mmusic-comedia-tls-06pre1.txt>;
a document showing changes from the previous version is at
<http://www1.cs.columbia.edu/~lennox/draft-ietf-mmusic-comedia-tls-06pre1.diff.html>.

Most of the issues raised resulted in pretty minor and hopefully
uncontroversial changes, but one change, having to do with certificate
identity choice, is fairly major.  I'm still
uncertain about the practical usability of the resulting rules.

Here's the scheme I'm proposing:

* If your SDP was sent over an end-to-end authenticated and
integrity-protected channel, there are no constraints on what identity you
assert in your TLS certificates; you can use anything you want.  Identity is
handled by the transporting protocol.

* If it wasn't, however, you have to have use certificate that asserts
either a) the host in your SDP c= line (which can be either an IP address or
host name), or b) a URI representing the protocol transporting the SDP
(which in practice usually means a SIP URI).

* For self-signed certificates sent un-authenticated, you can use SSH
"leap-of-faith" mode: you warn the user if you've never seen a certificate
before for a given identity, or if the certificate you got for an identity
is different from the one you have cached.  This means that once you've
communicated with someone, you can be sure no one's launching a
man-in-the-middle on you in the future.  It does, however, present usability
problems when someone has to change their cert.

* For SIP, if the unauthenticated cert you get (whether or not self-signed)
doesn't reflect the AoR of the party you initially contacted, the user is
again warned and user confirmation is requested.  (This applies whether it's
a different AoR, a device URI, or a hostname/IP address.)


This last point is the tricky one.  The goal here is that if you were trying
to reach sip:alice@example.com, and you get a cert asserting the identity
sip:bob@example.com, this could be a problem, and only a human can usefully
determine whether it is or not.

Of course, given that the initial user of comedia-TLS will be BFCP, for
which at least one side is an automated system without a human in the loop,
it's not entirely clear how practical this requirement will be.  But the
alternative leaves you vulnerable to hostile or subverted sip proxy servers.

The other question is whether it's worthwhile to say that single-hop sips
connections should count as end-to-end integrity-protected.  On the one
hand, they are; on the other hand, allowing certain operational modes for
single-hop but not multi-hop SIP seems like a bad idea, and it would break
in the face of third-party call control and other back-to-back UAs.

Do people have alternate suggestions, or thoughts on better solutions?  I
note that these requirements are strictly more lenient than the protocol
mode which got through WGLC.

-- 
Jonathan Lennox
lennox@cs.columbia.edu

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



From mmusic-bounces@ietf.org Sun Jan 29 15:20:05 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3J1p-0003YT-27; Sun, 29 Jan 2006 15:20:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3J1m-0003X3-9r; Sun, 29 Jan 2006 15:20:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23799;
	Sun, 29 Jan 2006 15:18:16 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]
	helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3JCE-00029z-4l; Sun, 29 Jan 2006 15:30:51 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id 0D69CE0053; Sun, 29 Jan 2006 15:19:37 -0500 (EST)
To: Jonathan Lennox <lennox@cs.columbia.edu>
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Sun, 29 Jan 2006 15:19:37 -0500
In-Reply-To: <17373.4514.607960.660335@cnr.cs.columbia.edu> (Jonathan
	Lennox's message of "Sun, 29 Jan 2006 14:04:02 -0500")
Message-ID: <tslacdevlba.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mankin@psg.com, EKR <ekr@networkresonance.com>, mmusic@ietf.org,
	jon.peterson@neustar.biz, tls@ietf.org
Subject: [MMUSIC] Re: comedia-tls: proposed change for certificate identities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

>>>>> "Jonathan" == Jonathan Lennox <lennox@cs.columbia.edu> writes:


    Jonathan> * If your SDP was sent over an end-to-end authenticated
    Jonathan> and integrity-protected channel, there are no
    Jonathan> constraints on what identity you assert in your TLS
    Jonathan> certificates; you can use anything you want.  Identity
    Jonathan> is handled by the transporting protocol.

What about hop-by-hop authenticated with each hop integrity protected.
IMHO in many environments, this presents acceptable man-in-the-middle
risk.  I think that it may present significantly easier to deal with
usability issues so I think it should at least be allowed if not
encouraged.

    Jonathan> * If it wasn't, however, you have to have use
    Jonathan> certificate that asserts either a) the host in your SDP
    Jonathan> c= line (which can be either an IP address or host
    Jonathan> name), or b) a URI representing the protocol
    Jonathan> transporting the SDP (which in practice usually means a
    Jonathan> SIP URI).

    Jonathan> * For self-signed certificates sent un-authenticated,
    Jonathan> you can use SSH "leap-of-faith" mode: you warn the user
    Jonathan> if you've never seen a certificate before for a given
    Jonathan> identity, or if the certificate you got for an identity
    Jonathan> is different from the one you have cached.  This means
    Jonathan> that once you've communicated with someone, you can be
    Jonathan> sure no one's launching a man-in-the-middle on you in
    Jonathan> the future.  It does, however, present usability
    Jonathan> problems when someone has to change their cert.

Do you have explicit language that a self-signed cert cache must not
get in the way of the rekeying in the previous two cases?
    Jonathan> The other question is whether it's worthwhile to say
    Jonathan> that single-hop sips connections should count as
    Jonathan> end-to-end integrity-protected.  On the one hand, they
    Jonathan> are; on the other hand, allowing certain operational
    Jonathan> modes for single-hop but not multi-hop SIP seems like a
    Jonathan> bad idea, and it would break in the face of third-party
    Jonathan> call control and other back-to-back UAs.

    Jonathan> Do people have alternate suggestions, or thoughts on
    Jonathan> better solutions?  I note that these requirements are
    Jonathan> strictly more lenient than the protocol mode which got
    Jonathan> through WGLC.


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



From mmusic-bounces@ietf.org Mon Jan 30 08:22:50 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3Yza-0007ws-Ow; Mon, 30 Jan 2006 08:22:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3YzX-0007w7-Ny; Mon, 30 Jan 2006 08:22:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22017;
	Mon, 30 Jan 2006 08:21:12 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3ZAJ-0003Qr-JJ; Mon, 30 Jan 2006 08:33:55 -0500
Received: from cnr.cs.columbia.edu (cnr.cs.columbia.edu [128.59.19.133])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id k0UDMCKG012673
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 30 Jan 2006 08:22:41 -0500 (EST)
Received: from cnr.cs.columbia.edu (localhost [127.0.0.1])
	by cnr.cs.columbia.edu (8.13.3/8.13.3) with ESMTP id k0UDMCoJ044681;
	Mon, 30 Jan 2006 08:22:12 -0500 (EST)
	(envelope-from lennox@cnr.cs.columbia.edu)
Received: (from lennox@localhost)
	by cnr.cs.columbia.edu (8.13.3/8.13.3/Submit) id k0UDMCn2044678;
	Mon, 30 Jan 2006 08:22:12 -0500 (EST) (envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17374.4868.521418.118273@cnr.cs.columbia.edu>
Date: Mon, 30 Jan 2006 08:22:12 -0500
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslacdevlba.fsf@cz.mit.edu>
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
	<tslacdevlba.fsf@cz.mit.edu>
X-Mailer: VM 7.19 under Emacs 21.3.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: mankin@psg.com, EKR <ekr@networkresonance.com>, mmusic@ietf.org,
	jon.peterson@neustar.biz, tls@ietf.org
Subject: [MMUSIC] Re: comedia-tls: proposed change for certificate identities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

On Sunday, January 29 2006, "Sam Hartman" wrote to "Jonathan Lennox, mmusic@ietf.org, tls@ietf.org, EKR, jon.peterson@neustar.biz, mankin@psg.com" saying:

> >>>>> "Jonathan" == Jonathan Lennox <lennox@cs.columbia.edu> writes:
> 
> 
>     Jonathan> * If your SDP was sent over an end-to-end authenticated
>     Jonathan> and integrity-protected channel, there are no
>     Jonathan> constraints on what identity you assert in your TLS
>     Jonathan> certificates; you can use anything you want.  Identity
>     Jonathan> is handled by the transporting protocol.
> 
> What about hop-by-hop authenticated with each hop integrity protected.
> IMHO in many environments, this presents acceptable man-in-the-middle
> risk.  I think that it may present significantly easier to deal with
> usability issues so I think it should at least be allowed if not
> encouraged.

This will certainly be the most common way of securing SDP, I think -- this
describes how sips, i.e. sip over hop-by-hop TLS, works.  You're vulnerable
to a broken or subverted sip proxy server, but otherwise you're safe.

If there's consensus that it's acceptable to allow this mode, I can add
language allowing it.  However, I think this is a big enough change I'd like
to hear positive consensus for it; this should get something more than just
consent-by-silence from the working group.

>     Jonathan> * If it wasn't, however, you have to have use
>     Jonathan> certificate that asserts either a) the host in your SDP
>     Jonathan> c= line (which can be either an IP address or host
>     Jonathan> name), or b) a URI representing the protocol
>     Jonathan> transporting the SDP (which in practice usually means a
>     Jonathan> SIP URI).
> 
>     Jonathan> * For self-signed certificates sent un-authenticated,
>     Jonathan> you can use SSH "leap-of-faith" mode: you warn the user
>     Jonathan> if you've never seen a certificate before for a given
>     Jonathan> identity, or if the certificate you got for an identity
>     Jonathan> is different from the one you have cached.  This means
>     Jonathan> that once you've communicated with someone, you can be
>     Jonathan> sure no one's launching a man-in-the-middle on you in
>     Jonathan> the future.  It does, however, present usability
>     Jonathan> problems when someone has to change their cert.
> 
> Do you have explicit language that a self-signed cert cache must not
> get in the way of the rekeying in the previous two cases?

I'm not sure how I distinguish rekeying from a man-in-the-middle attacker
presenting a new certificate.  Is there an obvious distinction here?  Does
it have to do with certificate expiration?

-- 
Jonathan Lennox
lennox@cs.columbia.edu

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



From mmusic-bounces@ietf.org Mon Jan 30 10:34:25 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3b2v-00055N-3X; Mon, 30 Jan 2006 10:34:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3b2t-00054Z-2N; Mon, 30 Jan 2006 10:34:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01009;
	Mon, 30 Jan 2006 10:32:40 -0500 (EST)
From: Imed.Bouazizi@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3bDU-0007U5-Ss; Mon, 30 Jan 2006 10:45:21 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k0UFT9Y5008606; Mon, 30 Jan 2006 17:29:09 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Jan 2006 17:33:46 +0200
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 30 Jan 2006 17:33:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Jan 2006 17:33:42 +0200
Message-ID: <C84E0A4ABA6DD74DA5221E0833A35DF304ED5B6F@esebe101.NOE.Nokia.com>
Thread-Topic: SDP descriptors for ALC
Thread-Index: AcYlsoy/uGymdjSnQauQKxcPmol9iw==
To: <mmusic@ietf.org>, <rmt@ietf.org>
X-OriginalArrivalTime: 30 Jan 2006 15:33:43.0027 (UTC)
	FILETIME=[8D378430:01C625B2]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [MMUSIC] SDP descriptors for ALC
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi All,

I was reading the new version of the "SDP Descriptors for FLUTE" I-D and
figured out that there is no counterpart for this specification to
describe ALC sessions.=20
As most of the parameters and descriptors should be identical for ALC
and FLUTE transport protocols, my proposal is to create a separate
section in the proposed I-D to describe SDP descriptors for ALC.

I included below a proposal on how to modify the new version of the I-D
to fulfill this purpose.
Any comments or alternative proposals?=20

Best Regards,
Imed Bouazizi

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


<3rd sentence is new>

Abstract

   This document specifies the use of SDP to describe the parameters
   required to begin, join, receive data from, and/or end FLUTE
   sessions.  It also provides a Composite Session SDP media grouping
   semantic for grouping media streams into protocol-specific sessions,
   such as multiple-channel FLUTE sessions. General SDP for ALC session=20
   is also specified, mostly by reusing FLUTE descriptors.

-----

1.  Introduction

<3rd paragraph, 3rd sentence is new>

   This document defines a new protocol identifier for File Delivery
   over Unidirectional Transport (FLUTE) protocol [1] and other required
   SDP attributes for initiating a FLUTE session.  The formal ABNF
   syntax [5] is used for the attributes.  A protocol identifier and=20
   other SDP attributes are also provided for general underspecified=20
   ALC-based sessions, reusing the majority of syntax specified for=20
   FLUTE session descriptions. This SDP syntax is
   independent of Any Source Multicast (ASM) or Source Specific
   Multicast (SSM) is used to route the media.

---

<new section>

5.  ALC Descriptors

   The ALC specification [XX] describes the underspecified ALC transport

protocol on which FLUTE is based. Many session characteristics of ALC
are=20
the same as FLUTE, as both originate from LCT session semantics [XX].
Hence,=20
to aid the session description of a fully-specified ALC-based transport=20
protocol, and ensure the minimum of difference in SDP descriptors for
similar=20
parameters, the following rules apply to ALC-based transport protocols
other=20
than FLUTE.

The descriptors for these parameters for ALC sessions SHALL be identical
to=20
those for FLUTE sessions, as specified in section 3:
   o  Source IP Address
   o  Session Timing Parameters
   o  FEC Object Transmission Information
   o  Content Description Pointer
   o  Bandwidth Specification
   o  Composite Session Semantics

The descriptors for these ALC parameters differs from those of FLUTE and
are=20
according to the specification of the following subsections:
   o  Number of channels
   o  Transport Session Identifier
   o  Protocol Id

5.1.  ALC Protocol Identifier

   A new value for the "proto" sub-field for ALC media is defined:
ALC/UDP.  The
   ALC/UDP protocol identifier specifies that the session being
   described will use the underspecified ALC [XX] protocol on top of a
UDP connection.

   The remainder of ALC session media line syntax is the same as for
FLUTE=20
(section >>3.1<<), with respect to: the fmt (format) list and the use of
a "*"=20
character; and, describing more than one ALC session may be described by
a single=20
SDP using the Composite Session mechanism.

5.2.  Transport Session Identifier

   The TSI MUST be described by the "alc-tsi" attribute. Otherwise, ALC
Transport=20
Session Identifier syntax for ALC SHALL be the same as for FLUTE as
specified in=20
section >>3.4<<.

   The syntax for the attribute in ABNF is given below:

      alc-tsi-line =3D "a=3Dalc-tsi:" tsi CRLF

5.3.  Channelisation Descriptors

   Destination IP address and port number for ALC channels shall be
according to=20
the same specification as FLUTE (section >>3.6<<) with the one exception
that the=20
number of channels MAY be signalled using an "alc-ch" attribute that
behaves exactly=20
like the "flute-ch" attribute (section >>3.6.1<<).

   The syntax for the attribute in ABNF is given below:

      alc-channel-line =3D "a=3Dalc-ch:" ch CRLF

5.4.  Fully-specified ALC-based Protocols other than FLUTE

Specification of fully-specified ALC-based protocols is beyond the scope
of this=20
document, as is the specification of descriptors specific to such
protocols, other=20
than FLUTE.

-----

6.2.  Attribute Names

<snip to new registrations>

   SDP Attribute ("att-field"):
     Attribute name:     alc-tsi
     Long form:          Underspecified ALC Transport Session Identifier
     Type of name:       att-field
     Type of attribute:  Session level or media level
     Subject to charset: No
     Purpose:            See this document
     Reference:          This document
     Values:             See this document

   SDP Attribute ("att-field"):
     Attribute name:     alc-ch
     Long form:          Number of Channels in an Underspecified ALC
Session
     Type of name:       att-field
     Type of attribute:  Session level or media level
     Subject to charset: No
     Purpose:            See this document
     Reference:          This document
     Values:             See this document

-----





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



From mmusic-bounces@ietf.org Mon Jan 30 15:51:19 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3fzb-0004bR-TU; Mon, 30 Jan 2006 15:51:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3fzS-0004Xp-LM; Mon, 30 Jan 2006 15:51:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26451;
	Mon, 30 Jan 2006 15:49:24 -0500 (EST)
Received: from [66.114.247.24] (helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3gA6-0001bt-Uj; Mon, 30 Jan 2006 16:02:12 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id A4FF7E0053; Mon, 30 Jan 2006 15:50:36 -0500 (EST)
To: Jonathan Lennox <lennox@cs.columbia.edu>
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
	<tslacdevlba.fsf@cz.mit.edu>
	<17374.4868.521418.118273@cnr.cs.columbia.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 30 Jan 2006 15:50:36 -0500
In-Reply-To: <17374.4868.521418.118273@cnr.cs.columbia.edu> (Jonathan
	Lennox's message of "Mon, 30 Jan 2006 08:22:12 -0500")
Message-ID: <tsl7j8htp7n.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mankin@psg.com, EKR <ekr@networkresonance.com>, mmusic@ietf.org,
	jon.peterson@neustar.biz, tls@ietf.org
Subject: [MMUSIC] Re: comedia-tls: proposed change for certificate identities
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

>>>>> "Jonathan" == Jonathan Lennox <lennox@cs.columbia.edu> writes:

    Jonathan> * For self-signed certificates sent un-authenticated,
    Jonathan> you can use SSH "leap-of-faith" mode: you warn the user
    Jonathan> if you've never seen a certificate before for a given
    Jonathan> identity, or if the certificate you got for an identity
    Jonathan> is different from the one you have cached.  This means
    Jonathan> that once you've communicated with someone, you can be
    Jonathan> sure no one's launching a man-in-the-middle on you in
    Jonathan> the future.  It does, however, present usability
    Jonathan> problems when someone has to change their cert.
    >>  Do you have explicit language that a self-signed cert cache
    >> must not get in the way of the rekeying in the previous two
    >> cases?

    Jonathan> I'm not sure how I distinguish rekeying from a
    Jonathan> man-in-the-middle attacker presenting a new certificate.
    Jonathan> Is there an obvious distinction here?  Does it have to
    Jonathan> do with certificate expiration?


Basically,  what I never want to happen is:

* you get a self signed cert in a previous session

* In the current session you have end-to-end integrity and get
  errors/warnings because you are not getting the same cert you did in
  that previous session.



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



From mmusic-bounces@ietf.org Mon Jan 30 16:39:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3gk2-000576-H9; Mon, 30 Jan 2006 16:39:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3gjx-00052g-Ir; Mon, 30 Jan 2006 16:39:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08381;
	Mon, 30 Jan 2006 16:37:31 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3gue-0006BO-Mg; Mon, 30 Jan 2006 16:50:18 -0500
Received: from cnr.cs.columbia.edu (cnr.cs.columbia.edu [128.59.19.133])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id k0ULd06j009906
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 30 Jan 2006 16:39:00 -0500 (EST)
Received: from cnr.cs.columbia.edu (localhost [127.0.0.1])
	by cnr.cs.columbia.edu (8.13.3/8.13.3) with ESMTP id k0ULd0pd048809;
	Mon, 30 Jan 2006 16:39:00 -0500 (EST)
	(envelope-from lennox@cnr.cs.columbia.edu)
Received: (from lennox@localhost)
	by cnr.cs.columbia.edu (8.13.3/8.13.3/Submit) id k0ULcx13048806;
	Mon, 30 Jan 2006 16:38:59 -0500 (EST) (envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17374.34675.730633.706221@cnr.cs.columbia.edu>
Date: Mon, 30 Jan 2006 16:38:59 -0500
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [MMUSIC] Re: comedia-tls: proposed change for certificate
	identities
In-Reply-To: <tsl7j8htp7n.fsf@cz.mit.edu>
References: <17373.4514.607960.660335@cnr.cs.columbia.edu>
	<tslacdevlba.fsf@cz.mit.edu>
	<17374.4868.521418.118273@cnr.cs.columbia.edu>
	<tsl7j8htp7n.fsf@cz.mit.edu>
X-Mailer: VM 7.19 under Emacs 21.3.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org, mmusic@ietf.org, EKR <ekr@networkresonance.com>,
	jon.peterson@neustar.biz, mankin@psg.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

On Monday, January 30 2006, "Sam Hartman" wrote to "Jonathan Lennox, mankin@psg.com, EKR, mmusic@ietf.org, jon.peterson@neustar.biz, tls@ietf.org" saying:

> Basically,  what I never want to happen is:
> 
> * you get a self signed cert in a previous session
> 
> * In the current session you have end-to-end integrity and get
>   errors/warnings because you are not getting the same cert you did in
>   that previous session.

Oh, I see.  Yes, if you receive a cert with end-to-end integrity, it should
never warn you about certificate mismatches; I'll make sure that language is
clear.

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



From mmusic-bounces@ietf.org Tue Jan 31 04:58:13 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sH7-00088d-Kh; Tue, 31 Jan 2006 04:58:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sH4-00086n-0t; Tue, 31 Jan 2006 04:58:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00822;
	Tue, 31 Jan 2006 04:56:23 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3sRo-0004jq-Hq; Tue, 31 Jan 2006 05:09:19 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k0V9qpqi031669; Tue, 31 Jan 2006 11:52:54 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 11:57:54 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 11:57:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6264C.CD496782"
Date: Tue, 31 Jan 2006 11:57:52 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD8513019EC4D3@trebe101.NOE.Nokia.com>
X-MS-Has-Attach: yes
Thread-Topic: I-D ACTION:draft-mehta-rmt-flute-sdp-05.txt 
Thread-Index: AcYl38J50q/DSxz4RzuR3aUjw//vJAAbLp9Q
To: <mmusic@ietf.org>, <rmt@ietf.org>
X-OriginalArrivalTime: 31 Jan 2006 09:57:53.0536 (UTC)
	FILETIME=[CD98F000:01C6264C]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: 
Subject: [MMUSIC] I-D ACTION:draft-mehta-rmt-flute-sdp-05.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6264C.CD496782
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: SDP Descriptors for FLUTE
	Author(s)	: H. Mehta, et al.
	Filename	: draft-mehta-rmt-flute-sdp-05.txt
	Pages		: 30
	Date		: 2006-1-30
=09
This document specifies the use of SDP to describe the parameters
   required to begin, join, receive data from, and/or end FLUTE
   sessions.  It also provides a Composite Session SDP media grouping
   semantic for grouping media streams into protocol-specific sessions,
   such as multiple-channel FLUTE sessions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-mehta-rmt-flute-sdp-05.txt

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


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

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


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

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

------_=_NextPart_001_01C6264C.CD496782
Content-Type: application/octet-stream;
	name="ATT9090926.TXT"
Content-Description: ATT9090926.TXT
Content-Disposition: attachment;
	filename="ATT9090926.TXT"
Content-Transfer-Encoding: base64

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi0xLTMwMTA0NjAwLkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW1laHRhLXJtdC1mbHV0ZS1z
ZHAtMDUudHh0DQo=

------_=_NextPart_001_01C6264C.CD496782
Content-Type: application/octet-stream; name="draft-mehta-rmt-flute-sdp-05.URL"
Content-Description: draft-mehta-rmt-flute-sdp-05.URL
Content-Disposition: attachment;
	filename="draft-mehta-rmt-flute-sdp-05.URL"
Content-Transfer-Encoding: base64

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1tZWh0YS1ybXQtZmx1dGUtc2RwLTA1LnR4dA0K

------_=_NextPart_001_01C6264C.CD496782
Content-Type: text/plain;
	name="ATT9090927.txt"
Content-Description: ATT9090927.txt
Content-Disposition: attachment;
	filename="ATT9090927.txt"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

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

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

------_=_NextPart_001_01C6264C.CD496782--




From mmusic-bounces@ietf.org Tue Jan 31 05:17:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sZi-00037y-5m; Tue, 31 Jan 2006 05:17:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sZf-00032g-G0; Tue, 31 Jan 2006 05:17:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02015;
	Tue, 31 Jan 2006 05:15:36 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3skQ-0005I6-A8; Tue, 31 Jan 2006 05:28:30 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k0VAH5HO023681; Tue, 31 Jan 2006 12:17:09 +0200
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 12:17:06 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 12:17:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 Jan 2006 12:17:05 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD8513019EC535@trebe101.NOE.Nokia.com>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF304ED5B6F@esebe101.NOE.Nokia.com>
Thread-Topic: [Rmt] SDP descriptors for ALC
Thread-Index: AcYlsoy/uGymdjSnQauQKxcPmol9iwAmsk6w
To: <rmt-bounces@ietf.org>, <mmusic@ietf.org>, <rmt@ietf.org>
X-OriginalArrivalTime: 31 Jan 2006 10:17:06.0853 (UTC)
	FILETIME=[7D072550:01C6264F]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [MMUSIC] RE: [Rmt] SDP descriptors for ALC
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Thanks Imed

The flute-sdp 05 version should be public (see earlier email from me
today). After quite a lot of work figuring out a version to suit all
comments, I'm not too keen on late additions.

However, the proposed text isn't that much and doesn't damage the
existing document and it would help for these "common" parts of an ALC
SDP to be specified in the same way as for a FLUTE SDP. So my initial
reaction is this is OK if there's very rapid consensus (so I could
submit an 06 Friday). If there's disagreement or many key unsolved
issues then I would suggest going through the rigmarole of a separate
RFC since it wouldn't have the 3GPP rel.6 dependency tied to it. So
let's see what others think...

Note, earlier comments have been group initiated so 05 is the first
version that would be stable and "satisfying" enough for WGLC. i.e. if
this ALC stuff gets added, it will certainly be subject to WGLC as for
the rest of the flute-sdp.

Cheers, Rod.


>-----Original Message-----
>From: rmt-bounces@ietf.org [mailto:rmt-bounces@ietf.org]=20
>Sent: 30 January, 2006 17:34
>To: mmusic@ietf.org; rmt@ietf.org
>Subject: [Rmt] SDP descriptors for ALC
>
>Hi All,
>
>I was reading the new version of the "SDP Descriptors for=20
>FLUTE" I-D and figured out that there is no counterpart for=20
>this specification to describe ALC sessions.=20
>As most of the parameters and descriptors should be identical=20
>for ALC and FLUTE transport protocols, my proposal is to=20
>create a separate section in the proposed I-D to describe SDP=20
>descriptors for ALC.
>
>I included below a proposal on how to modify the new version=20
>of the I-D to fulfill this purpose.
>Any comments or alternative proposals?=20
>
>Best Regards,
>Imed Bouazizi
>
>---------------------------------------------------------------
>---------
>------------------------
>
>
><3rd sentence is new>
>
>Abstract
>
>   This document specifies the use of SDP to describe the parameters
>   required to begin, join, receive data from, and/or end FLUTE
>   sessions.  It also provides a Composite Session SDP media grouping
>   semantic for grouping media streams into protocol-specific sessions,
>   such as multiple-channel FLUTE sessions. General SDP for=20
>ALC session=20
>   is also specified, mostly by reusing FLUTE descriptors.
>
>-----
>
>1.  Introduction
>
><3rd paragraph, 3rd sentence is new>
>
>   This document defines a new protocol identifier for File Delivery
>   over Unidirectional Transport (FLUTE) protocol [1] and=20
>other required
>   SDP attributes for initiating a FLUTE session.  The formal ABNF
>   syntax [5] is used for the attributes.  A protocol identifier and=20
>   other SDP attributes are also provided for general underspecified=20
>   ALC-based sessions, reusing the majority of syntax specified for=20
>   FLUTE session descriptions. This SDP syntax is
>   independent of Any Source Multicast (ASM) or Source Specific
>   Multicast (SSM) is used to route the media.
>
>---
>
><new section>
>
>5.  ALC Descriptors
>
>   The ALC specification [XX] describes the underspecified ALC=20
>transport
>
>protocol on which FLUTE is based. Many session characteristics=20
>of ALC are the same as FLUTE, as both originate from LCT=20
>session semantics [XX].
>Hence,
>to aid the session description of a fully-specified ALC-based=20
>transport protocol, and ensure the minimum of difference in=20
>SDP descriptors for similar parameters, the following rules=20
>apply to ALC-based transport protocols other than FLUTE.
>
>The descriptors for these parameters for ALC sessions SHALL be=20
>identical to those for FLUTE sessions, as specified in section 3:
>   o  Source IP Address
>   o  Session Timing Parameters
>   o  FEC Object Transmission Information
>   o  Content Description Pointer
>   o  Bandwidth Specification
>   o  Composite Session Semantics
>
>The descriptors for these ALC parameters differs from those of=20
>FLUTE and are according to the specification of the following=20
>subsections:
>   o  Number of channels
>   o  Transport Session Identifier
>   o  Protocol Id
>
>5.1.  ALC Protocol Identifier
>
>   A new value for the "proto" sub-field for ALC media is defined:
>ALC/UDP.  The
>   ALC/UDP protocol identifier specifies that the session being
>   described will use the underspecified ALC [XX] protocol on=20
>top of a UDP connection.
>
>   The remainder of ALC session media line syntax is the same=20
>as for FLUTE (section >>3.1<<), with respect to: the fmt=20
>(format) list and the use of a "*"=20
>character; and, describing more than one ALC session may be=20
>described by a single SDP using the Composite Session mechanism.
>
>5.2.  Transport Session Identifier
>
>   The TSI MUST be described by the "alc-tsi" attribute.=20
>Otherwise, ALC Transport Session Identifier syntax for ALC=20
>SHALL be the same as for FLUTE as specified in section >>3.4<<.
>
>   The syntax for the attribute in ABNF is given below:
>
>      alc-tsi-line =3D "a=3Dalc-tsi:" tsi CRLF
>
>5.3.  Channelisation Descriptors
>
>   Destination IP address and port number for ALC channels=20
>shall be according to the same specification as FLUTE (section=20
>>>3.6<<) with the one exception that the number of channels=20
>MAY be signalled using an "alc-ch" attribute that behaves=20
>exactly like the "flute-ch" attribute (section >>3.6.1<<).
>
>   The syntax for the attribute in ABNF is given below:
>
>      alc-channel-line =3D "a=3Dalc-ch:" ch CRLF
>
>5.4.  Fully-specified ALC-based Protocols other than FLUTE
>
>Specification of fully-specified ALC-based protocols is beyond=20
>the scope of this document, as is the specification of=20
>descriptors specific to such protocols, other than FLUTE.
>
>-----
>
>6.2.  Attribute Names
>
><snip to new registrations>
>
>   SDP Attribute ("att-field"):
>     Attribute name:     alc-tsi
>     Long form:          Underspecified ALC Transport Session=20
>Identifier
>     Type of name:       att-field
>     Type of attribute:  Session level or media level
>     Subject to charset: No
>     Purpose:            See this document
>     Reference:          This document
>     Values:             See this document
>
>   SDP Attribute ("att-field"):
>     Attribute name:     alc-ch
>     Long form:          Number of Channels in an Underspecified ALC
>Session
>     Type of name:       att-field
>     Type of attribute:  Session level or media level
>     Subject to charset: No
>     Purpose:            See this document
>     Reference:          This document
>     Values:             See this document
>
>-----
>
>
>
>
>
>_______________________________________________
>Rmt mailing list
>Rmt@ietf.org
>https://www1.ietf.org/mailman/listinfo/rmt
>

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



From mmusic-bounces@ietf.org Tue Jan 31 05:34:42 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sqP-0000ct-9Z; Tue, 31 Jan 2006 05:34:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3sqN-0000c9-Iu; Tue, 31 Jan 2006 05:34:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03177;
	Tue, 31 Jan 2006 05:33:04 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F3t1K-0005nF-E5; Tue, 31 Jan 2006 05:45:58 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k0VATXIl012346; Tue, 31 Jan 2006 12:29:36 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 12:34:31 +0200
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 12:34:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 Jan 2006 12:34:30 +0200
Message-ID: <7222D14EF47E0840AD88EC7BCBAD8513019EC57B@trebe101.NOE.Nokia.com>
Thread-Topic: I-D ACTION:draft-mehta-rmt-flute-sdp-05.txt 
Thread-Index: AcYl38J50q/DSxz4RzuR3aUjw//vJAAbLp9QAADIlIA=
To: <mmusic@ietf.org>, <rmt@ietf.org>
X-OriginalArrivalTime: 31 Jan 2006 10:34:31.0482 (UTC)
	FILETIME=[EBACE1A0:01C62651]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [MMUSIC] RE: I-D ACTION:draft-mehta-rmt-flute-sdp-05.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi All

The changes to this version of the flute-sdp document are:

- "Restricted behaviour" (formally named "default behaviour") is no
longer the default. So the mode not using "Composite Session" is still
allowed but is generally not recommended (this allows compatibility with
3GPP's FLUTE SDP and DVB's FLUTE SDP whilst still making it clear what
is expected for the Public Internet). Note, this was previously the
show-stopper but the text and meaning has been improved in several
places so that now all commenters are satisfied.

- Composite Session semantics+syntax are now first specified generically
and specifically for FLUTE sessions. i.e. it now much easier to
reference this document to use a CS grouping token for other-than-FLUTE
sessions in future

- Bandwidth specification is improved with TIAS being recommended (AS is
still optional)

- And a handful of formatting improvements

Based on all prior comments this I-D is ready for WGLC (in the humble
opinion of the authors). Only response to Imed's question on applying
thee semantics and syntax to SDP for underspecified ALC sessions remains
to be tested and decided whether Imed's additions shall be added.

Cheers, Rod.


>-----Original Message-----
>From: Walsh Rod (Nokia-NRC/Tampere)=20
>Sent: 31 January, 2006 11:58
>To: mmusic@ietf.org; rmt@ietf.org
>Subject: I-D ACTION:draft-mehta-rmt-flute-sdp-05.txt=20
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
>
>
>	Title		: SDP Descriptors for FLUTE
>	Author(s)	: H. Mehta, et al.
>	Filename	: draft-mehta-rmt-flute-sdp-05.txt
>	Pages		: 30
>	Date		: 2006-1-30
>=09
>This document specifies the use of SDP to describe the parameters
>   required to begin, join, receive data from, and/or end FLUTE
>   sessions.  It also provides a Composite Session SDP media grouping
>   semantic for grouping media streams into protocol-specific sessions,
>   such as multiple-channel FLUTE sessions.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-mehta-rmt-flute-sdp-05.txt
>
>To remove yourself from the I-D Announcement list, send a=20
>message to i-d-announce-request@ietf.org with the word=20
>unsubscribe in the body of the message. =20
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
>
>
>Internet-Drafts are also available by anonymous FTP. Login=20
>with the username "anonymous" and a password of your e-mail=20
>address. After logging in, type "cd internet-drafts" and then
>	"get draft-mehta-rmt-flute-sdp-05.txt".
>
>A list of Internet-Drafts directories can be found in=20
>http://www.ietf.org/shadow.html or=20
>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>	mailserv@ietf.org.
>In the body type:
>	"FILE /internet-drafts/draft-mehta-rmt-flute-sdp-05.txt".
>=09
>NOTE:	The mail server at ietf.org can return the document in
>	MIME-encoded form by using the "mpack" utility.  To use this
>	feature, insert the command "ENCODING mime" before the "FILE"
>	command.  To decode the response(s), you will need "munpack" or
>	a MIME-compliant mail reader.  Different MIME-compliant=20
>mail readers
>	exhibit different behavior, especially when dealing with
>	"multipart" MIME messages (i.e. documents which have been split
>	up into multiple messages), so check your local documentation on
>	how to manipulate these messages.
>	=09
>	=09
>Below is the data which will enable a MIME compliant mail=20
>reader implementation to automatically retrieve the ASCII=20
>version of the Internet-Draft.
>

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



From mmusic-bounces@ietf.org Tue Jan 31 06:37:35 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3tpH-0007Za-Io; Tue, 31 Jan 2006 06:37:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F3tpF-0007WR-I2
	for mmusic@megatron.ietf.org; Tue, 31 Jan 2006 06:37:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07741
	for <mmusic@ietf.org>; Tue, 31 Jan 2006 06:35:49 -0500 (EST)
Received: from smtp11.clb.oleane.net ([213.56.31.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3u03-0007pC-Od
	for mmusic@ietf.org; Tue, 31 Jan 2006 06:48:45 -0500
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp11.clb.oleane.net with ESMTP id k0VBb7AZ019108
	for <mmusic@ietf.org>; Tue, 31 Jan 2006 12:37:11 +0100
Message-Id: <200601311137.k0VBb7AZ019108@smtp11.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mmusic@ietf.org>
Date: Tue, 31 Jan 2006 12:37:03 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcYmWqekzRzWhosxR/6Uc3X4YtJcNQ==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
Subject: [MMUSIC] International SIP/WiMAX Summit - Paris - France
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1223629396=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1223629396==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00A8_01C62663.09B06210"

This is a multi-part message in MIME format.

------=_NextPart_000_00A8_01C62663.09B06210
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

More than 500 participants will attend International SIP and the WiMAX
Summit next February 21st to 24th in Paris.

 


Registration is still open for both events.

 

The 7th edition of the International SIP conference program is mainly
dedicated to IMS architectures and Peer-to-Peer communications:

 <http://www.upperside.fr/sip2006/sip2006intro.htm>
http://www.upperside.fr/sip2006/sip2006intro.htm

 

The 3rd WiMAX Summit is largely devoted to case studies presented by both
incumbent and new entrant operators:

 <http://www.upperside.fr/wimax2006/wimax2006intro.htm>
http://www.upperside.fr/wimax2006/wimax2006intro.htm

 

Close to the conference rooms an exhibition welcomes industrials involved in
VoIP and wireless broadband access.

 


------=_NextPart_000_00A8_01C62663.09B06210
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

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

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
8.0pt;font-family:Arial'>More than 500 participants will attend =
<strong><b><font
face=3DArial><span style=3D'font-family:Arial'>International =
SIP</span></font></b></strong>
and the <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>WiMAX
Summit</span></font></b></strong> next February 21st to 24th in =
<st1:place
w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>.</span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:8.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
8.0pt;font-family:Arial'>Registration is still open for both =
events.</span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
8.0pt;font-family:Arial'>The 7th edition of the International SIP =
conference
program is mainly dedicated to <strong><b><font face=3DArial><span
style=3D'font-family:Arial'>IMS architectures</span></font></b></strong> =
and
Peer-to-Peer communications:</span></font><font size=3D1><span =
lang=3DEN-GB
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:8.0pt;
font-family:Arial'><a =
href=3D"http://www.upperside.fr/sip2006/sip2006intro.htm"
title=3D"http://www.upperside.fr/sip2006/sip2006intro.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/sip2006/sip2006intro.htm</span></a><=
/span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
8.0pt;font-family:Arial'>The 3rd WiMAX Summit is largely devoted to case
studies presented by both <strong><b><font face=3DArial><span =
style=3D'font-family:
Arial'>incumbent and new entrant =
operators</span></font></b></strong>:</span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:8.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wimax2006/wimax2006intro.htm"
title=3D"http://www.upperside.fr/wimax2006/wimax2006intro.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/wimax2006/wimax2006intro.htm</span><=
/a></span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
8.0pt;font-family:Arial'>Close to the conference rooms an exhibition =
welcomes
industrials involved in VoIP and wireless broadband =
access.</span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:8.0pt'><o:p></o:p></span></font></p>

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

</div>

</body>

</html>

------=_NextPart_000_00A8_01C62663.09B06210--



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

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

--===============1223629396==--





