From mailman-bounces@ietf.org  Wed Jun  1 06:10:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18895
	for <mmusic-archive@ietf.org>; Wed, 1 Jun 2005 06:10:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DdQV8-0001KO-Dj
	for mmusic-archive@ietf.org; Wed, 01 Jun 2005 06:31:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdPK4-0002d4-Io
	for mmusic-archive@ietf.org; Wed, 01 Jun 2005 05:15:36 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: mmusic-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.12349.1117616679.11688.mailman@lists.ietf.org>
Date: Wed, 01 Jun 2005 05:04:39 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for mmusic-archive@ietf.org:

List                                     Password // URL
----                                     --------  
mmusic@ietf.org                          isokuc    
https://www1.ietf.org/mailman/options/mmusic/mmusic-archive%40ietf.org


From mmusic-bounces@ietf.org  Wed Jun  1 16:31:25 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06184
	for <mmusic-archive@ietf.org>; Wed, 1 Jun 2005 16:31:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DdaBz-0004gl-Ok
	for mmusic-archive@ietf.org; Wed, 01 Jun 2005 16:52:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdZqD-0006Dn-1F; Wed, 01 Jun 2005 16:29:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdZqC-0006DJ-0k
	for mmusic@megatron.ietf.org; Wed, 01 Jun 2005 16:29:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05287
	for <mmusic@ietf.org>; Wed, 1 Jun 2005 16:29:25 -0400 (EDT)
Received: from firewall.objectworld.com ([209.87.233.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DdaA0-0004Ly-Sg
	for mmusic@ietf.org; Wed, 01 Jun 2005 16:50:01 -0400
Received: from prothos.objectworld.com (prothos.objectworld.com [192.168.1.4])
	by firewall.objectworld.com (8.12.11/8.12.11) with ESMTP id
	j51KTDso005206 for <mmusic@ietf.org>; Wed, 1 Jun 2005 16:29:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Jun 2005 16:29:13 -0400
Message-ID: <D4E4FE59174AE145B4B03202A060D5FE3C9345@prothos.objectworld.com>
Thread-Topic: Status of ICE Internet-Draft
Thread-Index: AcVm6I8Ug3KJEyI/T9SCVD5X+9pmRw==
From: "Michael Slavitch" <slavitch@objectworld.com>
To: <mmusic@ietf.org>
X-CanItPRO-Stream: outgoing
X-Spam-Score: undef - Host Whitelisted (192.168.1.4: prothos.objectworld.com)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.168.1.1
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [MMUSIC] Status of ICE Internet-Draft
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0858396108=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc

This is a multi-part message in MIME format.

--===============0858396108==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C566E8.931A4316"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C566E8.931A4316
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Could someone please fill me in on the current status of this draft and
its elevation to proposed standard?
=20
Regards
=20
Michael
=20
=20

Michael Slavitch           Lead, Strategic Initiatives=20
slavitch@objectworld.com   Objectworld, Inc.=20
613.599.9698 x225          Ottawa, Ontario=20

=20

------_=_NextPart_001_01C566E8.931A4316
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D201212820-01062005>Could =
someone please=20
fill me in on the current status of this draft and its elevation to =
proposed=20
standard?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D201212820-01062005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D201212820-01062005>Regards</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D201212820-01062005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D201212820-01062005>Michael</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D201212820-01062005></SPAN></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<P><FONT face=3D"Courier New" size=3D2>Michael=20
Slavitch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Lead,=20
Strategic Initiatives</FONT> <BR><FONT face=3D"Courier New"=20
size=3D2>slavitch@objectworld.com&nbsp;&nbsp; Objectworld, Inc.</FONT> =
<BR><FONT=20
face=3D"Courier New" size=3D2>613.599.9698=20
x225&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ottawa,=20
Ontario</FONT> </P>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C566E8.931A4316--


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

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

--===============0858396108==--



From mmusic-bounces@ietf.org  Thu Jun  2 08:04:07 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07384
	for <mmusic-archive@ietf.org>; Thu, 2 Jun 2005 08:04:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ddokk-0000pR-Hq
	for mmusic-archive@ietf.org; Thu, 02 Jun 2005 08:24:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdoP9-0003kF-Kh; Thu, 02 Jun 2005 08:02:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdoP7-0003iX-EJ
	for mmusic@megatron.ietf.org; Thu, 02 Jun 2005 08:02:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07170
	for <mmusic@ietf.org>; Thu, 2 Jun 2005 08:02:28 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ddoj7-0000ly-N7
	for mmusic@ietf.org; Thu, 02 Jun 2005 08:23:11 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 02 Jun 2005 14:02:18 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j52C2F7F008673; 
	Thu, 2 Jun 2005 14:02:15 +0200 (MEST)
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 2 Jun 2005 14:01:54 +0200
Received: from [172.20.100.215] ([10.89.20.17]) by xfe-ams-331.emea.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Thu, 2 Jun 2005 14:01:54 +0200
Message-ID: <429E44A0.5070905@cisco.com>
Date: Wed, 01 Jun 2005 19:28:32 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Slavitch <slavitch@objectworld.com>
Subject: Re: [MMUSIC] Status of ICE Internet-Draft
References: <D4E4FE59174AE145B4B03202A060D5FE3C9345@prothos.objectworld.com>
In-Reply-To: <D4E4FE59174AE145B4B03202A060D5FE3C9345@prothos.objectworld.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jun 2005 12:01:54.0805 (UTC)
	FILETIME=[DE8F3A50:01C5676A]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

The draft is currently being revised based on discussions that took 
place at the last IETF. The update will represent a substantial change, 
and I believe substantial improvement in the document. I have been 
working on it so I am expecting an update substantially in advance of 
the Paris meeting.

Thanks,
Jonathan R.

Michael Slavitch wrote:

> Could someone please fill me in on the current status of this draft and 
> its elevation to proposed standard?
>  
> Regards
>  
> Michael
>  
>  
> 
> Michael Slavitch           Lead, Strategic Initiatives
> slavitch@objectworld.com   Objectworld, Inc.
> 613.599.9698 x225          Ottawa, Ontario
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Thu Jun  2 08:04:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07408
	for <mmusic-archive@ietf.org>; Thu, 2 Jun 2005 08:04:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ddokv-0000pi-BB
	for mmusic-archive@ietf.org; Thu, 02 Jun 2005 08:25:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdoPK-0003r4-B2; Thu, 02 Jun 2005 08:02:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdoPI-0003q5-PK
	for mmusic@megatron.ietf.org; Thu, 02 Jun 2005 08:02:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07216
	for <mmusic@ietf.org>; Thu, 2 Jun 2005 08:02:39 -0400 (EDT)
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.33)
	id 1DdojK-0000mJ-1O
	for mmusic@ietf.org; Thu, 02 Jun 2005 08:23:22 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 02 Jun 2005 05:02:31 -0700
X-IronPort-AV: i="3.93,161,1115017200"; 
	d="scan'208"; a="273143053:sNHT30431216"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j52C1ZcM029660
	for <mmusic@ietf.org>; Thu, 2 Jun 2005 05:02:27 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 2 Jun 2005 08:02:02 -0400
Received: from [172.20.100.215] ([10.89.20.17]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Thu, 2 Jun 2005 08:02:02 -0400
Message-ID: <429E479A.4070204@cisco.com>
Date: Wed, 01 Jun 2005 19:41:14 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jun 2005 12:02:02.0273 (UTC)
	FILETIME=[E302C110:01C5676A]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] ICE: move away from generic framework to offer/answer
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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

One of the complaints I have gotten about the ICE draft from many 
different sources is that it is too complicated. People I know who I 
consider very smart have told me that reading it "made their head hurt". 
This is a recipe for interoperability problems, and so one of my goals 
in this revision, beyond moving to the imroved re-invite based approach 
we discussed last IETF, is to simplify the document.

One of the sources of complexity is the fact that the spec is written as 
a meta-protocol. Its defined in terms of exchanges between abstract 
entities (intiator and responder) with abstract protocol messages 
defined in XML. The document then maps the XML into real protocol 
messages (specifically, SDP).

The reason we did that was to allow ICE to be used by RTSP for NAT 
traversal, since RTSP is not offer/answer based. However, the new 
mechanism discussed in Minneapolis relies on a re-invite to promote a 
candidate to actual usage in the m/c line. RTSP has no support for 
re-invites, and thus it won't be able to use ICE with this new 
mechanism, at least not directly (more on that below). As such, in the 
interests of simplifying the document for its primary customer - SIP - 
I'd like to convert this to be offer/answer based.

So what about RTSP? I think there are several paths:

1. define a separate specification that is specific to RTSP, borrowing 
as much from the ICE concepts as we can

2. define an extension to RTSP so that it uses offer/answer

3. if ICE is needed with RTSP, then use SIP and offer/answer to set up 
the session, focusing RTSP on control. That allows for direct usage of 
ICE to facilitate nat traversal for streaming sessions.

I personally like (3) a lot, but it can be discussed downstream. I'd 
like to focus on getting the main ICE draft done and working for SIP, 
and I believe going (back) to an offer/answer approach is a good thing.

Comments?

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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


From mmusic-bounces@ietf.org  Thu Jun  2 09:42:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14137
	for <mmusic-archive@ietf.org>; Thu, 2 Jun 2005 09:42:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DdqHg-0005nv-Lg
	for mmusic-archive@ietf.org; Thu, 02 Jun 2005 10:02:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdpxJ-00016o-Bi; Thu, 02 Jun 2005 09:41:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdpxH-00016j-PM
	for mmusic@megatron.ietf.org; Thu, 02 Jun 2005 09:41:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14128
	for <mmusic@ietf.org>; Thu, 2 Jun 2005 09:41:50 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DdqHI-0005nZ-Pj
	for mmusic@ietf.org; Thu, 02 Jun 2005 10:02:34 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by delivery_mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B9D3E390108; Thu,  2 Jun 2005 15:41:36 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by outbound_mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	601464F0002; Thu,  2 Jun 2005 15:41:30 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Jun 2005 15:41:29 +0200
Received: from [147.214.34.60] ([147.214.34.60]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Jun 2005 15:41:29 +0200
Message-ID: <429F0C88.8040300@ericsson.com>
Date: Thu, 02 Jun 2005 15:41:28 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE: move away from generic framework to offer/answer
References: <429E479A.4070204@cisco.com>
In-Reply-To: <429E479A.4070204@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Jun 2005 13:41:29.0251 (UTC)
	FILETIME=[C79B5730:01C56778]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC WG <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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Hi Jonathan,

A few comments in regards to RTSP. Although RTSP doesn't have re-invites 
it has re-setup that are used similar. Having said that however I am not 
greatly troubled if you change ICE to being offer/answer specific. 
Because I still think it is quite possible to do an not that difficult 
mapping of the different requests and information mapping.

See more below:

Jonathan Rosenberg wrote:
> 1. define a separate specification that is specific to RTSP, borrowing 
> as much from the ICE concepts as we can

Could be done, however I don't think we need to go that far. My 
preferred way would be to write the specification that  maps 
offer/answer ICE to RTSP.

> 
> 2. define an extension to RTSP so that it uses offer/answer

Would be a major change to the protocol.

> 
> 3. if ICE is needed with RTSP, then use SIP and offer/answer to set up 
> the session, focusing RTSP on control. That allows for direct usage of 
> ICE to facilitate nat traversal for streaming sessions.

Would be a new protocol, or at least RTSP version 2.0. I think MRCPv2 
has shown that this approach is possible. However as there specification 
shows this will still be quite a thick protocol specification.

> 
> I personally like (3) a lot, but it can be discussed downstream. I'd 
> like to focus on getting the main ICE draft done and working for SIP, 
> and I believe going (back) to an offer/answer approach is a good thing.
> 

Being realistic, I think only alternative 1 could be possible today with 
the current interest in moving forward with RTSP.

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 Jun  3 01:02:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28963
	for <mmusic-archive@ietf.org>; Fri, 3 Jun 2005 01:02:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1De4eM-00029R-NF
	for mmusic-archive@ietf.org; Fri, 03 Jun 2005 01:23:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1De4Jf-0006Qq-3h; Fri, 03 Jun 2005 01:01:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1De4JX-0006Pj-Pd
	for mmusic@megatron.ietf.org; Fri, 03 Jun 2005 01:01:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28907
	for <mmusic@ietf.org>; Fri, 3 Jun 2005 01:01:47 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1De4dg-00028H-8S
	for mmusic@ietf.org; Fri, 03 Jun 2005 01:22:38 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 03 Jun 2005 01:01:37 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5351X4u010761; 
	Fri, 3 Jun 2005 01:01:34 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 3 Jun 2005 01:01:33 -0400
Received: from [172.20.100.215] ([10.89.16.91]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Jun 2005 01:01:32 -0400
Message-ID: <429FE42C.2090503@cisco.com>
Date: Fri, 03 Jun 2005 01:01:32 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] ICE: move away from generic framework to offer/answer
References: <429E479A.4070204@cisco.com> <429F0C88.8040300@ericsson.com>
In-Reply-To: <429F0C88.8040300@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2005 05:01:33.0030 (UTC)
	FILETIME=[4F9F8860:01C567F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC WG <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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit



Magnus Westerlund wrote:

> Hi Jonathan,
> 
> A few comments in regards to RTSP. Although RTSP doesn't have re-invites 
> it has re-setup that are used similar. Having said that however I am not 
> greatly troubled if you change ICE to being offer/answer specific. 
> Because I still think it is quite possible to do an not that difficult 
> mapping of the different requests and information mapping.

OK, that is good.

> 
> See more below:
> 
> Jonathan Rosenberg wrote:
> 
>> 1. define a separate specification that is specific to RTSP, borrowing 
>> as much from the ICE concepts as we can
> 
> 
> Could be done, however I don't think we need to go that far. My 
> preferred way would be to write the specification that  maps 
> offer/answer ICE to RTSP.

That would be another option, yes.


>> 3. if ICE is needed with RTSP, then use SIP and offer/answer to set up 
>> the session, focusing RTSP on control. That allows for direct usage of 
>> ICE to facilitate nat traversal for streaming sessions.
> 
> 
> Would be a new protocol, or at least RTSP version 2.0. I think MRCPv2 
> has shown that this approach is possible. However as there specification 
> shows this will still be quite a thick protocol specification.

I'm not convinced you need to do much except for subset it, but I've not 
done a detailed analysis here.

> 
>>
>> I personally like (3) a lot, but it can be discussed downstream. I'd 
>> like to focus on getting the main ICE draft done and working for SIP, 
>> and I believe going (back) to an offer/answer approach is a good thing.
>>
> 
> Being realistic, I think only alternative 1 could be possible today with 
> the current interest in moving forward with RTSP.

OK, in that case it would be ideal if someone from the RTSP community 
that wants to see ICE used with RTSP, could write a draft that maps o/a 
into RTSP. Probably that would be handy for a few things, not just ICE.

Thanks,
Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Mon Jun  6 07:45:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21308
	for <mmusic-archive@ietf.org>; Mon, 6 Jun 2005 07:45:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DfGNH-00071n-Lg
	for mmusic-archive@ietf.org; Mon, 06 Jun 2005 08:06:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfFzc-000764-9u; Mon, 06 Jun 2005 07:42:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfFzb-00075z-Ra
	for mmusic@megatron.ietf.org; Mon, 06 Jun 2005 07:42:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21167
	for <mmusic@ietf.org>; Mon, 6 Jun 2005 07:42:06 -0400 (EDT)
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfGKP-0006z9-WC
	for mmusic@ietf.org; Mon, 06 Jun 2005 08:03:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [MMUSIC] Working group last call:
	draft-ietf-mmusic-sdp-bfcp-01.txt - comment
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Jun 2005 14:42:51 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C01C5823E@IsrExch01.israel.polycom.com>
Thread-Topic: [MMUSIC] Working group last call:
	draft-ietf-mmusic-sdp-bfcp-01.txt - comment
Thread-Index: AcVh5BypJJqLWjJ9Sc6jDZYGoopSnwIqH+vw
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Colin Perkins" <csp@csperkins.org>,
        "IETF MMUSIC working group" <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: Gonzalo.Camarillo@ericsson.com
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable


Hi,
I am resending my comments



I have some concerns about the offer answer model usage for defining the
floor control server.

=20

1. Assume we have a point to point call between two endpoints, EPA and
EPB. EPA offers a BFCP m line with confide and userid attributes
suggesting to become the BFCP server for a specific media. Now EPB wants
to be the floor control server for that media and to reject the offer.
Does it reject the m line with port 0 and offers a new BFCP m line. Is
there some way to break such tie if both sides want to be the BFCP
server.

=20

2. In the above case does EPB need to keep the floor-id defined in the
offer from EPA so that the media line will have the same labels.

=20

3. Now suppose that EPB is the current floor server. And EPA wants to
become the floor control server. The questions are as in 1 and 2. An
example for such a case is if EPA is also an MCU and another party, EPC,
called EPA and now it's a three way where EPA is the MCU and EPB and EPC
are connected to it. It is logical in this case to have the floor
control server on EPA.

=20

Thanks

Roni Even

=20

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Colin Perkins
Sent: Thursday, May 26, 2005 2:12 PM
To: IETF MMUSIC working group
Subject: [MMUSIC] Working group last call:
draft-ietf-mmusic-sdp-bfcp-01.txt

This is to announce a working group last call on the SDP format for BFCP
streams. Please send any final comments on this draft to the list before
10th June 2005. If no substantive issues are raised by that time, we
will request the IESG publish this document as a proposed standard RFC.

Colin



On 4 May 2005, at 20:47, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control

> Working Group of the IETF.
>
>     Title        : Session Description Protocol (SDP) Format for
>               Binary Floor Control Protocol (BFCP) Streams
>     Author(s)    : G. Camarillo
>     Filename    : draft-ietf-mmusic-sdp-bfcp-01.txt
>     Pages        : 15
>     Date        : 2005-5-4
>
> This document specifies how to describe BFCP streams in SDP session
>    descriptions.  User agents using the offer/answer model to=20
> establish
>    BFCP streams use this format in their offers and their answers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-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  Mon Jun  6 10:05:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02468
	for <mmusic-archive@ietf.org>; Mon, 6 Jun 2005 10:05:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DfIZ1-0001ay-J5
	for mmusic-archive@ietf.org; Mon, 06 Jun 2005 10:26:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfID4-0004rB-EQ; Mon, 06 Jun 2005 10:04:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfID2-0004qn-Kx
	for mmusic@megatron.ietf.org; Mon, 06 Jun 2005 10:04:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02290
	for <mmusic@ietf.org>; Mon, 6 Jun 2005 10:04:06 -0400 (EDT)
Received: from smtp7.clb.oleane.net ([213.56.31.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfIXs-0001Yb-0s
	for mmusic@ietf.org; Mon, 06 Jun 2005 10:25:41 -0400
Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be
	forged)) by smtp7.clb.oleane.net with ESMTP id j56E3mQ1020798
	for <mmusic@ietf.org>; Mon, 6 Jun 2005 16:03:51 +0200
Message-Id: <200506061403.j56E3mQ1020798@smtp7.clb.oleane.net>
From: "PETER" <peter.lewis@upperside.fr>
To: <mmusic@ietf.org>
Date: Mon, 6 Jun 2005 16:03:45 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcVqoIz/6ktLzpobTJubpe21aUck5w==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Subject: [MMUSIC] WiMAX Summit - Paris - France - Call for proposals
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="===============0468866680=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb

This is a multi-part message in MIME format.

--===============0468866680==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C56AB1.5182CF10"

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C56AB1.5182CF10
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The third edition of the WiMAX Summit, the most important European event
dedicated to this technology, will stand in Paris next February 21-24, 2006.

A call for proposals is online at:

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

The dead line for turning in abstracts is June 30.

 


------=_NextPart_000_0008_01C56AB1.5182CF10
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: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"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	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 third edition of the WiMAX Summit, the =
most
important European event dedicated to this technology, will stand in =
<st1:City
w:st=3D"on"><st1:place w:st=3D"on">Paris</st1:place></st1:City> next =
February
21-24, 2006.</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 call for proposals is online =
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=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The dead line for turning in abstracts is June =
30.</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'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0008_01C56AB1.5182CF10--



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

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

--===============0468866680==--




From mmusic-bounces@ietf.org  Wed Jun  8 19:33:58 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01879
	for <mmusic-archive@ietf.org>; Wed, 8 Jun 2005 19:33:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgAOV-0007eq-6u
	for mmusic-archive@ietf.org; Wed, 08 Jun 2005 19:55:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgA1k-0001ek-0I; Wed, 08 Jun 2005 19:32:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgA1i-0001eW-4D; Wed, 08 Jun 2005 19:32:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01720;
	Wed, 8 Jun 2005 19:31:58 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgAMY-0007ac-OW; Wed, 08 Jun 2005 19:53:36 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j58NUYL02542;
	Wed, 8 Jun 2005 16:30:34 -0700 (PDT)
Message-Id: <200506082330.j58NUYL02542@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 08 Jun 2005 16:30:34 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] RFC 4091 on The Alternative Network Address Types (ANAT)
	Semantics for the Session Description Protocol (SDP) Grouping
	Framework
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
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 4091

        Title:      The Alternative Network Address Types (ANAT)
                    Semantics for the Session Description Protocol
                    (SDP) Grouping Framework
        Author(s):  G. Camarillo, J. Rosenberg
        Status:     Standards Track
        Date:       June 2005
        Mailbox:    Gonzalo.Camarillo@ericsson.com, jdrosen@cisco.com
        Pages:      7
        Characters: 12931
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mmusic-anat-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4091.txt


This document defines the Alternative Network Address Types (ANAT)
semantics for the Session Description Protocol (SDP) grouping
framework.  The ANAT semantics allow alternative types of
network addresses to establish a particular media stream.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050608162611.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4091

--OtherAccess
Content-Type: Message/External-body; name="rfc4091.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050608162611.RFC@RFC-EDITOR.ORG>


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

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

--NextPart--



From mmusic-bounces@ietf.org  Thu Jun  9 15:59:13 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11512
	for <mmusic-archive@ietf.org>; Thu, 9 Jun 2005 15:59:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgTWr-0006Qt-QJ
	for mmusic-archive@ietf.org; Thu, 09 Jun 2005 16:21:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgT4v-0006nw-IX; Thu, 09 Jun 2005 15:52:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgT4r-0006mu-Bn; Thu, 09 Jun 2005 15:52:33 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10101;
	Thu, 9 Jun 2005 15:52:30 -0400 (EDT)
Message-Id: <200506091952.PAA10101@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 09 Jun 2005 15:52:30 -0400
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-07.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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		: Session Description Protocol (SDP) Source Filters
	Author(s)	: B. Quinn, R. Finlayson
	Filename	: draft-ietf-mmusic-sdp-srcfilter-07.txt
	Pages		: 10
	Date		: 2005-6-9
	
This document describes how to adapt the Session Description Protocol
    (SDP) to express one or more source addresses as a source filter for
    one or more destination "connection" addresses.  It defines the
    syntax and semantics for an SDP "source-filter" attribute that may
    reference either IPv4 or IPv6 address(es) as either an inclusive or
    exclusive source list for either multicast or unicast destinations.
    In particular, an inclusive source-filter can be used to specify a
    Source-Specific Multicast (SSM) session.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcfilter-07.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-srcfilter-07.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-srcfilter-07.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: <2005-6-9160704.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-srcfilter-07.txt

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

Content-Type: text/plain
Content-ID: <2005-6-9160704.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Fri Jun 10 09:53:22 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21342
	for <mmusic-archive@ietf.org>; Fri, 10 Jun 2005 09:53:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgkIW-00065z-DI
	for mmusic-archive@ietf.org; Fri, 10 Jun 2005 10:15:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgjwY-0001hV-Kz; Fri, 10 Jun 2005 09:53:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DgjwW-0001hQ-LW
	for mmusic@megatron.ietf.org; Fri, 10 Jun 2005 09:53:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21329
	for <mmusic@ietf.org>; Fri, 10 Jun 2005 09:53:02 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgkIB-00065P-JA
	for mmusic@ietf.org; Fri, 10 Jun 2005 10:15:28 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:53044)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1DgjwL-0006Jm-Oc; Fri, 10 Jun 2005 14:52:53 +0100
In-Reply-To: <2E7339CE-E404-4ACA-9D5A-A0BE50A61563@csperkins.org>
References: <200505041947.PAA21300@ietf.org>
	<2E7339CE-E404-4ACA-9D5A-A0BE50A61563@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <73A19B1F-E146-439D-8918-286402FD0476@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Working group last call:
	draft-ietf-mmusic-sdp-bfcp-01.txt
Date: Fri, 10 Jun 2005 14:52:48 +0100
To: IETF MMUSIC working group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

This last call ends today. We received last call comments from Roni  
Even which have not yet been addressed. Given the outstanding issues,  
we will not advance the draft at this time.

Colin



On 26 May 2005, at 12:11, Colin Perkins wrote:
> This is to announce a working group last call on the SDP format for  
> BFCP streams. Please send any final comments on this draft to the  
> list before 10th June 2005. If no substantive issues are raised by  
> that time, we will request the IESG publish this document as a  
> proposed standard RFC.
>
> Colin
>
>
>
> On 4 May 2005, at 20:47, 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        : Session Description Protocol (SDP) Format for
>>               Binary Floor Control Protocol (BFCP) Streams
>>     Author(s)    : G. Camarillo
>>     Filename    : draft-ietf-mmusic-sdp-bfcp-01.txt
>>     Pages        : 15
>>     Date        : 2005-5-4
>>
>> This document specifies how to describe 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.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-bfcp-01.txt

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


From mmusic-bounces@ietf.org  Fri Jun 10 15:59:47 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02263
	for <mmusic-archive@ietf.org>; Fri, 10 Jun 2005 15:59:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dgq19-0005Rl-A2
	for mmusic-archive@ietf.org; Fri, 10 Jun 2005 16:22:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgpM6-0004tW-0b; Fri, 10 Jun 2005 15:39:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgpM1-0004sd-Fa; Fri, 10 Jun 2005 15:39:45 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25080;
	Fri, 10 Jun 2005 15:39:43 -0400 (EDT)
Message-Id: <200506101939.PAA25080@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 10 Jun 2005 15:39:43 -0400
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdescriptions-10.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--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		: Session Description Protocol Security Descriptions 
			  for Media Streams
	Author(s)	: F. Andreasen, et al.
	Filename	: draft-ietf-mmusic-sdescriptions-10.txt
	Pages		: 37
	Date		: 2005-6-10
	
This document defines a Session Description Protocol (SDP) 
   cryptographic attribute for unicast media streams.  The attribute 
   describes a cryptographic key and other parameters, which serve to 
   configure security for a unicast media stream in either a single 
   message or a roundtrip exchange.  The attribute can be used with a 
   variety of SDP media transports and this document defines how to use 
   it for the Secure Real-time Transport Protocol (SRTP) unicast media 
   streams.  The SDP crypto attribute requires the services of a data 
   security protocol to secure the SDP message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-10.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-sdescriptions-10.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-sdescriptions-10.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: <2005-6-10154612.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdescriptions-10.txt

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

Content-Type: text/plain
Content-ID: <2005-6-10154612.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Fri Jun 10 17:53:53 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16387
	for <mmusic-archive@ietf.org>; Fri, 10 Jun 2005 17:53:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgrnZ-0008Am-R0
	for mmusic-archive@ietf.org; Fri, 10 Jun 2005 18:16:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgrQB-0005Pd-Me; Fri, 10 Jun 2005 17:52:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgkPr-0008UU-Fi; Fri, 10 Jun 2005 10:23:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24674;
	Fri, 10 Jun 2005 10:23:21 -0400 (EDT)
Received: from pollux.cic.ipn.mx ([148.204.211.160] helo=cic.ipn.mx)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgklT-0003ti-EV; Fri, 10 Jun 2005 10:45:48 -0400
Received: from cic.ipn.mx (localhost [127.0.0.1])
	by cic.ipn.mx (8.13.1/8.13.1) with ESMTP id j5A5BJWa008760
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <cfp-list@cic.ipn.mx>; Fri, 10 Jun 2005 00:11:19 -0500
Received: (from majordomo@localhost)
	by cic.ipn.mx (8.13.1/8.13.1/Submit) id j5A5BECW008759
	for cfp-list; Fri, 10 Jun 2005 00:11:14 -0500
X-Authentication-Warning: cic.ipn.mx: majordomo set sender to
	owner-cfp@cic.ipn.mx using -f
Received: from micron ([148.204.20.147])
	by cic.ipn.mx (8.13.1/8.13.1) with ESMTP id j5A5AqsA008751;
	Fri, 10 Jun 2005 00:10:52 -0500
From: "Alexander Gelbukh \(NWeSP\)" <nwesp@micai.org>
To: "'Web Services group'" <nwesp@micai.org>
Date: Fri, 10 Jun 2005 00:16:29 -0500
Organization: NWeSP
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAHPjpMKBGKUWkg/DsW6jnP8KAAAAQAAAARe3qa38rpEyRD/+yiq/yrAEAAAAA@micai.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcVLlbmrThUAhM+3RoyO9f5uy8VVdA==
X-MailScanner: Found to be clean, Found to be clean
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 10 Jun 2005 17:52:10 -0400
Subject: [MMUSIC] CFP: NWeSP-2005 Web Services conference,
	IEEE: submission reminder (extended deadline)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit

	NWeSP-2005: International Conference
	"Next Generation Web Services Practices"
	
	August 23-27, 2005, Seoul, Korea

	www.NWeSP.org

	*** EXTENDED SUBMISSION DEADLINE: June 17. ***

	Published by IEEE Computer Society Press, USA.

	NWeSP authors will have publishing opportunities
	in several special issues, see below.

Keynote speakers:
- Kwei-Jay Lin, University of California at Irvine,
- Jen-Yao Chung, IBM Research Division, USA,
- Shim Yoon, Web Services Advance Force, Samsung,
- David Du, University of Minnesota.

In cooperation with:
- IEEE Computer Society,
- Task force on Electronic Commerce,
- Technical Committee on Internet,
- Technical Committee on Scaleable Computing,
- The International World-Wide Web Conference Committee, IW3C2,
- Microsoft, Korea.

TOPICS:
- Web Services Architecture, Modeling and Design,
- Semantic Web, Ontologies (creation, merging, linking, reconciliation),
- Database Technologies for Web Services,
- Customization, Reusability, Enhancements,
- Information Security Issues,
- Quality of Service, Scalability and Performance,
- User Interfaces, Visualization and modeling,
- Web Services Standards,
- Autonomic Computing Paradigms,
- Web Based e-Commerce, e-learning applications,
- Grid Based Web Services.

SUBMISSION:
Proceedings of the conference will be published by IEEE CS Press. 
Submissions are received via www.NWeSP.org.
Proposals to organize technical session and workshops are welcome.

JOURNAL PUBLICATION OPPORTUNITIES:
Good quality papers will be invited for publication in the
International Journal of Web Services Practices.
Selected papers will be considered for a special issue an "Recent
trends in Web Services Prectices" in the International journal of
Digital information Management(JDIM).
Several other International Journal special issues are being planned
and will be available in the conference web site very soon.

IMPORTANT DATES (extended):
June 17: Deadline for full paper submission.
July 15: Notification of acceptance.
July 29: Deadline for camera ready papers and registration.

CONTACT:
Sang Yong Han, hansy AT cau.ac.kr;
Ajith Abraham, ajith.abraham AT ieee.org.
For inquires about this message use Reply button.

Please distribute this CFP to your colleagues and students.


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


From mmusic-bounces@ietf.org  Mon Jun 13 16:17:54 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02011
	for <mmusic-archive@ietf.org>; Mon, 13 Jun 2005 16:17:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dhvjx-0003bF-Iz
	for mmusic-archive@ietf.org; Mon, 13 Jun 2005 16:41:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dhunn-0005kN-PW; Mon, 13 Jun 2005 15:40:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dhunj-0005j5-AL; Mon, 13 Jun 2005 15:40:51 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16155;
	Mon, 13 Jun 2005 15:40:48 -0400 (EDT)
Message-Id: <200506131940.PAA16155@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 13 Jun 2005 15:40:47 -0400
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdescriptions-11.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--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		: Session Description Protocol Security Descriptions 
			  for Media Streams
	Author(s)	: F. Andreasen, et al.
	Filename	: draft-ietf-mmusic-sdescriptions-11.txt
	Pages		: 37
	Date		: 2005-6-13
	
This document defines a Session Description Protocol (SDP) 
   cryptographic attribute for unicast media streams.  The attribute 
   describes a cryptographic key and other parameters, which serve to 
   configure security for a unicast media stream in either a single 
   message or a roundtrip exchange.  The attribute can be used with a 
   variety of SDP media transports and this document defines how to use 
   it for the Secure Real-time Transport Protocol (SRTP) unicast media 
   streams.  The SDP crypto attribute requires the services of a data 
   security protocol to secure the SDP message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-11.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-sdescriptions-11.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-sdescriptions-11.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: <2005-6-13160826.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdescriptions-11.txt

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

Content-Type: text/plain
Content-ID: <2005-6-13160826.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Tue Jun 14 12:21:12 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01549
	for <mmusic-archive@ietf.org>; Tue, 14 Jun 2005 12:21:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiEWc-0003Il-7Z
	for mmusic-archive@ietf.org; Tue, 14 Jun 2005 12:44:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiE7W-00071b-8g; Tue, 14 Jun 2005 12:18:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiE7U-00071S-Tx
	for mmusic@megatron.ietf.org; Tue, 14 Jun 2005 12:18:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01402
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 12:18:30 -0400 (EDT)
Received: from go4.ext.ti.com ([192.91.75.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiETw-00036n-T5
	for mmusic@ietf.org; Tue, 14 Jun 2005 12:41:49 -0400
Received: from dlep31.itg.ti.com ([157.170.139.161])
	by go4.ext.ti.com (8.13.1/8.13.1) with ESMTP id j5EGIE2X028938
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 11:18:15 -0500 (CDT)
Received: from dlep90.itg.ti.com (localhost [127.0.0.1])
	by dlep31.itg.ti.com (8.12.11/8.12.11) with ESMTP id j5EGIE20007292
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 11:18:14 -0500 (CDT)
Received: from dlee70.ent.ti.com (localhost [127.0.0.1])
	by dlep90.itg.ti.com (8.12.11/8.12.11) with ESMTP id j5EGIERo005937
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 11:18:14 -0500 (CDT)
Received: from dlee03.ent.ti.com ([157.170.170.66]) by dlee70.ent.ti.com with
	Microsoft SMTPSVC(6.0.3790.0); Tue, 14 Jun 2005 11:18:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 14 Jun 2005 11:18:13 -0500
Message-ID: <6F1AB8A9A94550408E37D83FA0DC4E7952BF1E@dlee03.ent.ti.com>
Thread-Topic: mmusic Digest, Vol 14, Issue 8 - differences
Thread-Index: AcVw+8fLCZc/8HxWSIO4s5famz3W8AAALW7Q
From: "Bhal, Sanjay" <sbhal@ti.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 14 Jun 2005 16:18:14.0194 (UTC)
	FILETIME=[AA58C120:01C570FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC] RE: mmusic Digest, Vol 14, Issue 8 - differences
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable

=20
Hello,
How do I know what is new in this draft? Any document available with
comparison between the two drafts?

Thanks for your help,
Sanjay
-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of mmusic-request@ietf.org
Sent: Tuesday, June 14, 2005 12:12 PM
To: mmusic@ietf.org
Subject: mmusic Digest, Vol 14, Issue 8

Send mmusic mailing list submissions to
	mmusic@ietf.org

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

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

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


Today's Topics:

   1. I-D ACTION:draft-ietf-mmusic-sdescriptions-11.txt
      (Internet-Drafts@ietf.org)


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

Message: 1
Date: Mon, 13 Jun 2005 15:40:47 -0400
From: Internet-Drafts@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdescriptions-11.txt
To: i-d-announce@ietf.org
Cc: mmusic@ietf.org
Message-ID: <200506131940.PAA16155@ietf.org>
Content-Type: text/plain; charset=3D"us-ascii"

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		: Session Description Protocol Security
Descriptions=20
			  for Media Streams
	Author(s)	: F. Andreasen, et al.
	Filename	: draft-ietf-mmusic-sdescriptions-11.txt
	Pages		: 37
	Date		: 2005-6-13
=09
This document defines a Session Description Protocol (SDP)=20
   cryptographic attribute for unicast media streams.  The attribute=20
   describes a cryptographic key and other parameters, which serve to=20
   configure security for a unicast media stream in either a single=20
   message or a roundtrip exchange.  The attribute can be used with a=20
   variety of SDP media transports and this document defines how to use=20
   it for the Secure Real-time Transport Protocol (SRTP) unicast media=20
   streams.  The SDP crypto attribute requires the services of a data=20
   security protocol to secure the SDP message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-11.t
xt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message. =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-ietf-mmusic-sdescriptions-11.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-sdescriptions-11.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.
-------------- next part --------------
Skipped content of type multipart/alternative

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

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


End of mmusic Digest, Vol 14, Issue 8
*************************************

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


From mmusic-bounces@ietf.org  Tue Jun 14 13:23:54 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06154
	for <mmusic-archive@ietf.org>; Tue, 14 Jun 2005 13:23:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiFVJ-0007CU-Lr
	for mmusic-archive@ietf.org; Tue, 14 Jun 2005 13:47:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiF8c-0001xo-S8; Tue, 14 Jun 2005 13:23:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiF8b-0001xe-Al
	for mmusic@megatron.ietf.org; Tue, 14 Jun 2005 13:23:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06125
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 13:23:42 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiFV6-0007Be-5j
	for mmusic@ietf.org; Tue, 14 Jun 2005 13:47:02 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:50706)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1DiF8M-0007Av-St; Tue, 14 Jun 2005 18:23:30 +0100
In-Reply-To: <6F1AB8A9A94550408E37D83FA0DC4E7952BF1E@dlee03.ent.ti.com>
References: <6F1AB8A9A94550408E37D83FA0DC4E7952BF1E@dlee03.ent.ti.com>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <03221649-9290-4000-B5C8-E6195303C304@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] RE: mmusic Digest, Vol 14, Issue 8 - differences
Date: Tue, 14 Jun 2005 18:23:24 +0100
To: "Bhal, Sanjay" <sbhal@ti.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

On 14 Jun 2005, at 17:18, Bhal, Sanjay wrote:
> How do I know what is new in this draft?

The tool at http://ietf.levkowetz.com/tools/rfcdiff/ can be used to  
compare drafts, as can any other diff utility.

> Any document available with comparison between the two drafts?

In draft-ietf-mmusic-sdescriptions-11.txt some sections are  
rearranged compared to the -10 draft. There are no technical changes.

Colin

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


From mmusic-bounces@ietf.org  Tue Jun 14 14:18:33 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14540
	for <mmusic-archive@ietf.org>; Tue, 14 Jun 2005 14:18:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiG3x-0001Wj-Q4
	for mmusic-archive@ietf.org; Tue, 14 Jun 2005 14:23:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiFhK-0008BT-Vr; Tue, 14 Jun 2005 13:59:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiFhJ-0008Ab-9F
	for mmusic@megatron.ietf.org; Tue, 14 Jun 2005 13:59:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11868
	for <mmusic@ietf.org>; Tue, 14 Jun 2005 13:59:36 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiG3m-0001Gl-2L
	for mmusic@ietf.org; Tue, 14 Jun 2005 14:22:51 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-4.cisco.com with ESMTP; 14 Jun 2005 10:59:09 -0700
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 j5EHwQcU011937;
	Tue, 14 Jun 2005 10:59:04 -0700 (PDT)
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);
	Tue, 14 Jun 2005 10:59:04 -0700
Received: from [192.168.0.10] ([10.21.114.157]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 14 Jun 2005 10:59:04 -0700
In-Reply-To: <6F1AB8A9A94550408E37D83FA0DC4E7952BF1E@dlee03.ent.ti.com>
References: <6F1AB8A9A94550408E37D83FA0DC4E7952BF1E@dlee03.ent.ti.com>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <41db018263a0def247c66518d6aabb00@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] RE: mmusic Digest, Vol 14, Issue 8 - differences
Date: Tue, 14 Jun 2005 10:59:03 -0700
To: "Bhal, Sanjay" <sbhal@ti.com>
X-Mailer: Apple Mail (2.622)
X-OriginalArrivalTime: 14 Jun 2005 17:59:04.0271 (UTC)
	FILETIME=[C0793DF0:01C5710A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: 7bit

hi,
   version -10 had some boilerplate problems and was quickly replaced by  
-11.  The significant differences are between -9 and -10.  We should  
have posted an explanation to the list when we posted -10.  The major  
change was an Applicability section that explains when one would use  
SDP Security Descriptions instead of kmgmt+MIKEY.  We also fixed some  
smaller problems with revision -9 that were pointed out by persons on  
the list.

Mark
On Jun 14, 2005, at 9:18 AM, Bhal, Sanjay wrote:

>
> Hello,
> How do I know what is new in this draft? Any document available with
> comparison between the two drafts?
>
> Thanks for your help,
> Sanjay
> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On  
> Behalf
> Of mmusic-request@ietf.org
> Sent: Tuesday, June 14, 2005 12:12 PM
> To: mmusic@ietf.org
> Subject: mmusic Digest, Vol 14, Issue 8
>
> Send mmusic mailing list submissions to
> 	mmusic@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www1.ietf.org/mailman/listinfo/mmusic
> or, via email, send a message with subject or body 'help' to
> 	mmusic-request@ietf.org
>
> You can reach the person managing the list at
> 	mmusic-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific  
> than
> "Re: Contents of mmusic digest..."
>
>
> Today's Topics:
>
>    1. I-D ACTION:draft-ietf-mmusic-sdescriptions-11.txt
>       (Internet-Drafts@ietf.org)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 13 Jun 2005 15:40:47 -0400
> From: Internet-Drafts@ietf.org
> Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdescriptions-11.txt
> To: i-d-announce@ietf.org
> Cc: mmusic@ietf.org
> Message-ID: <200506131940.PAA16155@ietf.org>
> Content-Type: text/plain; charset="us-ascii"
>
> 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		: Session Description Protocol Security
> Descriptions
> 			  for Media Streams
> 	Author(s)	: F. Andreasen, et al.
> 	Filename	: draft-ietf-mmusic-sdescriptions-11.txt
> 	Pages		: 37
> 	Date		: 2005-6-13
> 	
> This document defines a Session Description Protocol (SDP)
>    cryptographic attribute for unicast media streams.  The attribute
>    describes a cryptographic key and other parameters, which serve to
>    configure security for a unicast media stream in either a single
>    message or a roundtrip exchange.  The attribute can be used with a
>    variety of SDP media transports and this document defines how to use
>    it for the Secure Real-time Transport Protocol (SRTP) unicast media
>    streams.  The SDP crypto attribute requires the services of a data
>    security protocol to secure the SDP message.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions 
> -11.t
> xt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-mmusic-sdescriptions-11.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-sdescriptions-11.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.
> -------------- next part --------------
> Skipped content of type multipart/alternative
>
> ------------------------------
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>
>
> End of mmusic Digest, Vol 14, Issue 8
> *************************************
>
> _______________________________________________
> 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 Jun 14 16:09:20 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26359
	for <mmusic-archive@ietf.org>; Tue, 14 Jun 2005 16:09:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiI5Q-0004ga-Fs
	for mmusic-archive@ietf.org; Tue, 14 Jun 2005 16:32:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiHcY-00074y-U0; Tue, 14 Jun 2005 16:02:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiHcV-00074J-Ks; Tue, 14 Jun 2005 16:02:47 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25710;
	Tue, 14 Jun 2005 16:02:45 -0400 (EDT)
Message-Id: <200506142002.QAA25710@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 14 Jun 2005 16:02:45 -0400
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-kmgmt-ext-15.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--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		: Key Management Extensions for Session Description 
			  Protocol (SDP) and Real Time Streaming Protocol (RTSP)
	Author(s)	: J. Arkko, et al.
	Filename	: draft-ietf-mmusic-kmgmt-ext-15.txt
	Pages		: 28
	Date		: 2005-6-14
	
This document defines general extensions for SDP and RTSP to carry
   messages, as specified by a key management protocol, in order to
   secure the media. These extensions are presented as a framework, to
   be used by one or more key management protocols. As such, their use
   is meaningful only when complemented by an appropriate key management
   protocol.

   General guidelines are also given on how the framework should be used
   together with SIP and RTSP. The usage with the MIKEY key management
   protocol is also defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-15.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-kmgmt-ext-15.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-kmgmt-ext-15.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: <2005-6-14163656.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-kmgmt-ext-15.txt

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

Content-Type: text/plain
Content-ID: <2005-6-14163656.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Tue Jun 14 16:26:11 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00687
	for <mmusic-archive@ietf.org>; Tue, 14 Jun 2005 16:26:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiILj-0006te-Nz
	for mmusic-archive@ietf.org; Tue, 14 Jun 2005 16:49:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiHcx-000761-D5; Tue, 14 Jun 2005 16:03:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiHct-00075P-9W; Tue, 14 Jun 2005 16:03:11 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25735;
	Tue, 14 Jun 2005 16:03:09 -0400 (EDT)
Message-Id: <200506142003.QAA25735@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 14 Jun 2005 16:03:09 -0400
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-08.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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		: Session Description Protocol (SDP) Source Filters
	Author(s)	: B. Quinn, R. Finlayson
	Filename	: draft-ietf-mmusic-sdp-srcfilter-08.txt
	Pages		: 0
	Date		: 2005-6-14
	
This document describes how to adapt the Session Description Protocol
    (SDP) to express one or more source addresses as a source filter for
    one or more destination "connection" addresses.  It defines the
    syntax and semantics for an SDP "source-filter" attribute that may
    reference either IPv4 or IPv6 address(es) as either an inclusive or
    exclusive source list for either multicast or unicast destinations.
    In particular, an inclusive source-filter can be used to specify a
    Source-Specific Multicast (SSM) session.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcfilter-08.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-srcfilter-08.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-srcfilter-08.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: <2005-6-14163704.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-srcfilter-08.txt

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

Content-Type: text/plain
Content-ID: <2005-6-14163704.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From mmusic-bounces@ietf.org  Wed Jun 15 04:36:46 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22758
	for <mmusic-archive@ietf.org>; Wed, 15 Jun 2005 04:36:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiTkq-0007wa-PF
	for mmusic-archive@ietf.org; Wed, 15 Jun 2005 05:00:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiTKQ-0004az-0w; Wed, 15 Jun 2005 04:32:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiTKO-0004au-IQ
	for mmusic@megatron.ietf.org; Wed, 15 Jun 2005 04:32:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22547
	for <mmusic@ietf.org>; Wed, 15 Jun 2005 04:32:50 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiTh3-0007le-8d
	for mmusic@ietf.org; Wed, 15 Jun 2005 04:56:17 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 15 Jun 2005 10:31:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] ICE: move away from generic framework to offer/answer
Date: Wed, 15 Jun 2005 10:31:39 +0200
Message-ID: <B30D6148F304A743A53B9B44751CDB9A02FE7117@FTRDMEL2.rd.francetelecom.fr>
Thread-Topic: [MMUSIC] ICE: move away from generic framework to offer/answer
Thread-Index: AcVna0++ArO0Jx7YT8uIvFyhbywk7AKGINlw
From: "MARJOU Xavier RD-MAPS-LAN" <xavier.marjou@francetelecom.com>
To: "IETF MMUSIC WG" <mmusic@ietf.org>
X-OriginalArrivalTime: 15 Jun 2005 08:31:40.0813 (UTC)
	FILETIME=[A7678BD0:01C57184]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable

Hi,

Personnally, I have a dream ; that SIP and RTSP evolve to merge into a
single protocol (eg: modifications within SIP to integrate the delta
needed for RTSP features). For some works like NAT, work would need to
be done only once.

Xavier=20

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Jonathan Rosenberg
Sent: jeudi 2 juin 2005 01:41
To: IETF MMUSIC WG
Subject: [MMUSIC] ICE: move away from generic framework to offer/answer

One of the complaints I have gotten about the ICE draft from many
different sources is that it is too complicated. People I know who I
consider very smart have told me that reading it "made their head hurt".

This is a recipe for interoperability problems, and so one of my goals
in this revision, beyond moving to the imroved re-invite based approach
we discussed last IETF, is to simplify the document.

One of the sources of complexity is the fact that the spec is written as
a meta-protocol. Its defined in terms of exchanges between abstract
entities (intiator and responder) with abstract protocol messages
defined in XML. The document then maps the XML into real protocol
messages (specifically, SDP).

The reason we did that was to allow ICE to be used by RTSP for NAT
traversal, since RTSP is not offer/answer based. However, the new
mechanism discussed in Minneapolis relies on a re-invite to promote a
candidate to actual usage in the m/c line. RTSP has no support for
re-invites, and thus it won't be able to use ICE with this new
mechanism, at least not directly (more on that below). As such, in the
interests of simplifying the document for its primary customer - SIP -
I'd like to convert this to be offer/answer based.

So what about RTSP? I think there are several paths:

1. define a separate specification that is specific to RTSP, borrowing
as much from the ICE concepts as we can

2. define an extension to RTSP so that it uses offer/answer

3. if ICE is needed with RTSP, then use SIP and offer/answer to set up
the session, focusing RTSP on control. That allows for direct usage of
ICE to facilitate nat traversal for streaming sessions.

I personally like (3) a lot, but it can be discussed downstream. I'd
like to focus on getting the main ICE draft done and working for SIP,
and I believe going (back) to an offer/answer approach is a good thing.

Comments?

-Jonathan R.
--=20
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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

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


From mmusic-bounces@ietf.org  Wed Jun 15 04:55:21 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23758
	for <mmusic-archive@ietf.org>; Wed, 15 Jun 2005 04:55:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiU2q-0000UW-TZ
	for mmusic-archive@ietf.org; Wed, 15 Jun 2005 05:18:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiTfs-0000HB-Li; Wed, 15 Jun 2005 04:55:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiTfp-0000G6-Tx
	for mmusic@megatron.ietf.org; Wed, 15 Jun 2005 04:55:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23753
	for <mmusic@ietf.org>; Wed, 15 Jun 2005 04:54:59 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiU2T-0000UJ-RW
	for mmusic@ietf.org; Wed, 15 Jun 2005 05:18:27 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:60258
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1DiTfe-0006Os-QL
	for mmusic@ietf.org; Wed, 15 Jun 2005 09:54:51 +0100
Mime-Version: 1.0 (Apple Message framework v730)
In-Reply-To: <200506142003.QAA25735@ietf.org>
References: <200506142003.QAA25735@ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3235FC96-BB8E-49C8-B23C-BFBC73C9B809@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-08.txt
Date: Wed, 15 Jun 2005 09:54:43 +0100
To: IETF MMUSIC working group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit

Folks,

The latest revisions to the srcfilter draft address the IESG review  
comments:
https://datatracker.ietf.org/public/pidtracker.cgi? 
command=view_id&dTag=5370&rfc_flag=0

This draft has previously completed working group last call, but  
since a normative MUST has been removed from the draft in response to  
IESG comments, we need confirmation from the group that the revisions  
are appropriate. Accordingly, please review the changes to the draft  
(see below) and send any final comments to the mailing list before  
Monday 20th June 2005. If no comments are received we will consider  
the changes appropriate, and ask the IESG to continue processing the  
draft.

Colin



Changes between -06 and -07 (change log from Ross):

Normative References:
- Updated the dates of the "rtcpssm" and "sdp-new" Internet Drafts.
- Replaced the reference to the (obsolete) RFC 2044 with one to RFC  
3629.

Informative References:
- Updated the "IGMPv3" reference to refer to RFC 3376.
- Updated the "Socket Interface Extensions ..." reference to refer to  
RFC 3678.
- Updated the "Overview of SSM" reference to refer to RFC 3569.

Appendix A:
- Added necessary 'space characters' to the ABNF syntax.
- Updated the "src-list" ABNF definition to reference "unicast- 
address" rather than "addr" (which is no longer used in the 'sdp-new'  
ABNF).

Elsewhere:
- Changed the unicast addresses used in examples to come from the  
range of 'example' addresses as specified in RFCs 3330 and 3849.
- Updated boilerplate text to pass "idnits".

Changes between -07 and -08:

<     are those that are seen by a receiver.  If source addresses  
undergo
<     translation en route from the original sender to the receiver
<     - e.g., due to NAT (Network Address Translation) or some tunneling
<     mechanism - then the SDP "source-filter" attribute - as  
presented to
<     the receiver - MUST be translated accordingly.
---
 >     are those that are seen by a receiver.  Therefore, if source
 >     addresses undergo translation en route from the original  
sender to
 >     the receiver - e.g., due to NAT (Network Address Translation)  
or some
 >     tunneling mechanism - then the SDP "source-filter" attribute - as
 >     presented to the receiver, will not be accurate, unless the  
source
 >     addresses therein are also translated accordingly.


On 14 Jun 2005, at 21:03, 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        : Session Description Protocol (SDP) Source Filters
>     Author(s)    : B. Quinn, R. Finlayson
>     Filename    : draft-ietf-mmusic-sdp-srcfilter-08.txt
>     Pages        : 0
>     Date        : 2005-6-14
>
> This document describes how to adapt the Session Description Protocol
>     (SDP) to express one or more source addresses as a source  
> filter for
>     one or more destination "connection" addresses.  It defines the
>     syntax and semantics for an SDP "source-filter" attribute that may
>     reference either IPv4 or IPv6 address(es) as either an  
> inclusive or
>     exclusive source list for either multicast or unicast  
> destinations.
>     In particular, an inclusive source-filter can be used to specify a
>     Source-Specific Multicast (SSM) session.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp- 
> srcfilter-08.txt


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


From mmusic-bounces@ietf.org  Wed Jun 15 05:18:58 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25167
	for <mmusic-archive@ietf.org>; Wed, 15 Jun 2005 05:18:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiUPi-0001pQ-0o
	for mmusic-archive@ietf.org; Wed, 15 Jun 2005 05:42:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiU27-0004rY-Pq; Wed, 15 Jun 2005 05:18:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DiU26-0004rT-Od
	for mmusic@megatron.ietf.org; Wed, 15 Jun 2005 05:18:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25140
	for <mmusic@ietf.org>; Wed, 15 Jun 2005 05:18:00 -0400 (EDT)
Received: from serrano.cc.columbia.edu ([128.59.29.6] ident=cu41754)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DiUOm-0001oz-4F
	for mmusic@ietf.org; Wed, 15 Jun 2005 05:41:28 -0400
Received: from [192.168.0.31] (pool-141-153-173-119.mad.east.verizon.net
	[141.153.173.119]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5F9HxqS003709
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Jun 2005 05:17:59 -0400 (EDT)
Message-ID: <42AFF246.8000407@cs.columbia.edu>
Date: Wed, 15 Jun 2005 05:17:58 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: MARJOU Xavier RD-MAPS-LAN <xavier.marjou@francetelecom.com>,
        mmusic@ietf.org
Subject: Re: [MMUSIC] ICE: move away from generic framework to offer/answer
References: <B30D6148F304A743A53B9B44751CDB9A02FE7117@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <B30D6148F304A743A53B9B44751CDB9A02FE7117@FTRDMEL2.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

MARJOU Xavier RD-MAPS-LAN wrote:
> Hi,
> 
> Personnally, I have a dream ; that SIP and RTSP evolve to merge into a
> single protocol (eg: modifications within SIP to integrate the delta
> needed for RTSP features). For some works like NAT, work would need to
> be done only once.

This comes up periodically. Unfortunately, this faces a number of 
practical hurdles:

- RTSP and SIP are widely deployed, in literally millions of pieces of 
software. Merging them would cause interoperability issues, with no 
major advantage in functionality.

- RTSP has a much more limited scope, which makes it relatively easy for 
implementors to grasp. SIP has dozens of extensions, leaving alone 
abominations like SIP-* (where * is just about any letter of the 
alphabet). SIP needs those, since it has much broader scope.

- RTSP and SIP URLs are fundamentally different, and justifiably so 
(file vs. person).

- Any merging activity would take a decade, given the current speed, or 
lack thereof, in the IETF. By that time, industry confusion will be such 
that only proprietary protocols will remain. It's taking several years 
just to rev the RTSP spec, with modest modifications.

With hindsight, it would have been nice to have a common framework for 
both protocols, so that infrastructure such as ICE works across both. 
Unfortunately, hindsight is good for bar discussions, but not IETF and 
protocol realities.

Henning

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


From mmusic-bounces@ietf.org  Thu Jun 16 13:52:44 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19263
	for <mmusic-archive@ietf.org>; Thu, 16 Jun 2005 13:52:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Diyul-0000uR-Hg
	for mmusic-archive@ietf.org; Thu, 16 Jun 2005 14:16:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiyXQ-0003Yn-Hy; Thu, 16 Jun 2005 13:52:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DiyXK-0003Vy-1O; Thu, 16 Jun 2005 13:52:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19183;
	Thu, 16 Jun 2005 13:52:13 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DiyuG-0000tN-CB; Thu, 16 Jun 2005 14:16:00 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DiyXA-0006fC-Lw; Thu, 16 Jun 2005 13:52:08 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1DiyXA-0006fC-Lw@newodin.ietf.org>
Date: Thu, 16 Jun 2005 13:52:08 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: mmusic chair <csp@csperkins.org>,
        Internet Architecture Board <iab@iab.org>,
        mmusic mailing list <mmusic@ietf.org>, mmusic chair <jo@acm.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MMUSIC] Protocol Action: 'The SDP (Session Description Protocol) 
 Label Attribute' to Proposed Standard 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003

The IESG has approved the following document:

- 'The SDP (Session Description Protocol) Label Attribute '
   <draft-ietf-mmusic-sdp-media-label-01.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-media-label-01.txt

Technical Summary
 
   This specification defines a new Session Description Protocol (SDP)
   media-level attribute: "label".  The "label" attribute carries a
   pointer to a media stream in the context of an arbitrary network
   application that uses SDP.  The sender of the SDP document can attach
   the "label" attribute to a particular media stream or streams.  The
   application can then use the provided pointer to refer to each or all
   of the media in its particular context.

   SDP is a body or document used by other protocols.  It is left to the using
   applications to manage the "label" attribute.  However an important 
   user of the attribute is identified, the XCON framework.  The
   SIP conferencing package, in review at the same time as this
   specification,  is another important using protocol.

Working Group Summary
 
 The document carefully reviews why other SDP attributes or functionality which
 to provide this labeling function were not chosen.  The working group had
 raised each of the alternatives and discussed the points through to consensus.
 Before working group last call, there was a thorough document review by
 Magnus Westerlund, and the specification revised for small issues from that
 was supported for advancement.
 
Protocol Quality
 
 Allison Mankin has reviewed the specification for the IESG.

Note(s) to the RFC Editor
 
Replace normative reference to RFC 2234 with normative reference
to draft-crocker-abnf-rfc2234bis-00.txt
[DS in RFC Editor Queue]

Section 1. Add a sentence at the end of the second paragraph.

OLD:
[...]
media stream's role in the conference) about it.

NEW:
[...]
media stream's role in the conference) about it. The SIP Event
Package for Conference State [Informative refence to
draft-ietf-sipping-conference-package] defines and uses a concrete
format for such external documents.

Section 4:  extend the ABNF as follows:

OLD:

Its formatting in SDP is described by the following BNF
   [2]:


       label-attribute    = "a=label:" pointer
       pointer            = token

NEW:

Its formatting in SDP is described by the following ABNF
   [normative reference to  draft-crocker-abnf-rfc2234bis-00.txt]:


       label-attribute    = "a=label:" pointer
       pointer            = token
       token-char =          %x21 / %x23-27 / %x2A-2B / %x2D-2E / %x30-39
                            / %x41-5A / %x5E-7E

       token =               1*(token-char)


      The token-char and token elements are defined in [give a Normative
      reference to draft-ietf-mmusic-sdp-new-24.txt] but included here to
      provide support for the implementor of this SDP feature.


Section 6: addition of an 'i' line to the example:
OLD:
          v=0
          o=bob 280744730 28977631 IN IP4 host.example.com
          s=
          c=IN IP4 192.0.2.2
          t=0 0
          m=audio 6886 RTP/AVP 0
          a=label:1
          m=audio 22334 RTP/AVP 0
          a=label:2

NEW
          v=0
          o=bob 280744730 28977631 IN IP4 host.example.com
          s=
          i=A Seminar on the session description protocol
          c=IN IP4 192.0.2.2
          t=0 0
          m=audio 6886 RTP/AVP 0
          a=label:1
          m=audio 22334 RTP/AVP 0
          a=label:2

 Add to the beginning of Section 8 -

     Upon approval of this specification, IANA is requested to register
     the following new SDP attribute:


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


From mmusic-bounces@ietf.org  Thu Jun 16 16:14:44 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06194
	for <mmusic-archive@ietf.org>; Thu, 16 Jun 2005 16:14:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj18D-0002fH-5T
	for mmusic-archive@ietf.org; Thu, 16 Jun 2005 16:38:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj0NY-0006h7-BV; Thu, 16 Jun 2005 15:50:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj0NL-0006da-IR; Thu, 16 Jun 2005 15:50:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00656;
	Thu, 16 Jun 2005 15:50:01 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj0kH-0008IX-2I; Thu, 16 Jun 2005 16:13:49 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1Dj0NG-00058M-Eh; Thu, 16 Jun 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Dj0NG-00058M-Eh@newodin.ietf.org>
Date: Thu, 16 Jun 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-comedia-tls-03.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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		: Connection-Oriented Media Transport over the 
                          Transport Layer Security (TLS) Protocol in the
                          Session Description Protocol (SDP)
	Author(s)	: J. Lennox
	Filename	: draft-ietf-mmusic-comedia-tls-03.txt
	Pages		: 15
	Date		: 2005-6-16
	
This document specifies how to establish secure connection-oriented
   media transport sessions over the Transport Layer Security (TLS)
   protocol using the Session Description Protocol (SDP).  It defines a
   new protocol identifier, TCP/TLS.  It also defines the syntax and
   semantics for an SDP "fingerprint" attribute that identifies the
   certificate which will be presented for the TLS session.  This
   mechanism allows media transport over TLS connections to be
   established securely, so long as the integrity of session
   descriptions is assured.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-comedia-tls-03.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-comedia-tls-03.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-comedia-tls-03.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: <2005-6-16151353.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-comedia-tls-03.txt

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

Content-Type: text/plain
Content-ID: <2005-6-16151353.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--



From mmusic-bounces@ietf.org  Thu Jun 16 16:15:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06269
	for <mmusic-archive@ietf.org>; Thu, 16 Jun 2005 16:15:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj18b-0002gk-SW
	for mmusic-archive@ietf.org; Thu, 16 Jun 2005 16:38:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj0NX-0006gs-W8; Thu, 16 Jun 2005 15:50:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj0NL-0006dM-8J; Thu, 16 Jun 2005 15:50:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00645;
	Thu, 16 Jun 2005 15:50:01 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj0kG-0008IV-Sm; Thu, 16 Jun 2005 16:13:49 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1Dj0NG-00058Q-Fc; Thu, 16 Jun 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Dj0NG-00058Q-Fc@newodin.ietf.org>
Date: Thu, 16 Jun 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-09.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--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		: Session Description Protocol (SDP) Source Filters
	Author(s)	: B. Quinn, R. Finlayson
	Filename	: draft-ietf-mmusic-sdp-srcfilter-09.txt
	Pages		: 0
	Date		: 2005-6-16
	
This document describes how to adapt the Session Description Protocol
    (SDP) to express one or more source addresses as a source filter for
    one or more destination "connection" addresses.  It defines the
    syntax and semantics for an SDP "source-filter" attribute that may
    reference either IPv4 or IPv6 address(es) as either an inclusive or
    exclusive source list for either multicast or unicast destinations.
    In particular, an inclusive source-filter can be used to specify a
    Source-Specific Multicast (SSM) session.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcfilter-09.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-srcfilter-09.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-srcfilter-09.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: <2005-6-16151442.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-srcfilter-09.txt

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

Content-Type: text/plain
Content-ID: <2005-6-16151442.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mmusic-bounces@ietf.org  Tue Jun 21 00:53:23 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16702
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 00:53:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkb9B-0000UF-LQ
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 01:18:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dkakt-0003gb-VR; Tue, 21 Jun 2005 00:52:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkakr-0003gW-Sz
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 00:52:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16681
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 00:52:54 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkb8h-0000Tf-QL
	for mmusic@ietf.org; Tue, 21 Jun 2005 01:17:37 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 9E43FCDC
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 06:52:34 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 06:52:33 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 06:52:33 +0200
Received: from [131.160.126.5] (rvi2-126-5.lmf.ericsson.se [131.160.126.5])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 21EE12551
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 07:52:33 +0300 (EEST)
Message-ID: <42B79D10.9010302@ericsson.com>
Date: Tue, 21 Jun 2005 07:52:32 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 04:52:33.0585 (UTC)
	FILETIME=[09864210:01C5761D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Blank IPv6 c lines
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

Folks,

when a SIP user agent cannot provide an IPv4 address for some reason 
(e.g., in third-party call control scenarios) it uses the following 'c' 
line:

c=IN IP4 0.0.0.0

Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
with something.

Thanks,

Gonzalo


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


From mmusic-bounces@ietf.org  Tue Jun 21 09:36:57 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18756
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 09:36:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkjJu-00057j-MW
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 10:01:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkiuF-00089x-Li; Tue, 21 Jun 2005 09:35:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkiuD-00089s-FQ
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 09:35:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18596
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 09:35:08 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkjI7-000553-5R
	for mmusic@ietf.org; Tue, 21 Jun 2005 09:59:53 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by sj-iport-5.cisco.com with ESMTP; 21 Jun 2005 06:34:49 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5LDYYgt020603; 
	Tue, 21 Jun 2005 09:34:47 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 09:34:39 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 09:34:37 -0400
Message-ID: <42B8176D.7070902@cisco.com>
Date: Tue, 21 Jun 2005 09:34:37 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <42B79D10.9010302@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 13:34:38.0024 (UTC)
	FILETIME=[F8585480:01C57665]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: mmusic <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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:
> Folks,
> 
> when a SIP user agent cannot provide an IPv4 address for some reason 
> (e.g., in third-party call control scenarios) it uses the following 'c' 
> line:
> 
> c=IN IP4 0.0.0.0
> 
> Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
> with something.

AFAIK we don't have an equivalent.

But why would we need one? Does it really matter if the "null" address 
is IPv4 or IPv6? Either way I am not going to be sending or receiving 
with it.

	Paul

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


From mmusic-bounces@ietf.org  Tue Jun 21 09:48:00 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19644
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 09:48:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkjUc-0005Rk-1v
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 10:12:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dkj6W-0001cU-PM; Tue, 21 Jun 2005 09:47:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkj6U-0001c0-Bp
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 09:47:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19635
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 09:47:48 -0400 (EDT)
Message-Id: <200506211347.JAA19635@ietf.org>
Received: from [208.248.239.14] (helo=mail.cmguc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkjUN-0005Qc-2D
	for mmusic@ietf.org; Tue, 21 Jun 2005 10:12:34 -0400
Received: (qmail 20093 invoked from network); 21 Jun 2005 13:42:09 -0000
Received: from unknown (HELO loualexadell) ([10.239.70.253])
	(envelope-sender <louis.alexander@logicacmg.com>)
	by 0 (qmail-ldap-1.03) with SMTP
	for <Gonzalo.Camarillo@ericsson.com>; 21 Jun 2005 13:42:09 -0000
From: "Louis Alexander" <louis.alexander@logicacmg.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Subject: RE: [MMUSIC] Blank IPv6 c lines
Date: Tue, 21 Jun 2005 09:46:56 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <42B8176D.7070902@cisco.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-index: AcV2ZfEt9eDVZ03HR22BBNI9uPDdbAAAUBuw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: "'mmusic'" <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
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Is this not an appropriate place to use a SDP attribute such as a=sendonly
or a=inactive?

Louis

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: Tuesday, June 21, 2005 9:35 AM
To: Gonzalo Camarillo
Cc: mmusic
Subject: Re: [MMUSIC] Blank IPv6 c lines



Gonzalo Camarillo wrote:
> Folks,
> 
> when a SIP user agent cannot provide an IPv4 address for some reason 
> (e.g., in third-party call control scenarios) it uses the following 'c' 
> line:
> 
> c=IN IP4 0.0.0.0
> 
> Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
> with something.

AFAIK we don't have an equivalent.

But why would we need one? Does it really matter if the "null" address 
is IPv4 or IPv6? Either way I am not going to be sending or receiving 
with it.

	Paul

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


This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.


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


From mmusic-bounces@ietf.org  Tue Jun 21 10:49:06 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26647
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 10:49:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkkRk-0007It-3D
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 11:13:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dkk3E-0003xc-IH; Tue, 21 Jun 2005 10:48:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkk3C-0003xF-Cp
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 10:48:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26570
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 10:48:28 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkkR5-0007FQ-Sb
	for mmusic@ietf.org; Tue, 21 Jun 2005 11:13:14 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 6C886AE1; 
	Tue, 21 Jun 2005 16:48:06 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 16:48:05 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 16:48:05 +0200
Received: from [131.160.126.5] (rvi2-126-5.lmf.ericsson.se [131.160.126.5])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id BF58B250C;
	Tue, 21 Jun 2005 17:48:04 +0300 (EEST)
Message-ID: <42B828A1.50605@ericsson.com>
Date: Tue, 21 Jun 2005 17:48:01 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Louis Alexander <louis.alexander@logicacmg.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org>
In-Reply-To: <200506211347.JAA19635@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 14:48:05.0195 (UTC)
	FILETIME=[3B3941B0:01C57670]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>, "'mmusic'" <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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: 7bit

Paul,

I am concerned with IPv6-only user agents. If they see an IP4 address 
they will assume they do not understand it. They will not even parse the 
0.0.0.0 part. We may also think of a solution that is address type 
independent. Something like c=null.

Louis,

an inactive stream still carries RTCP traffic... a null c line is 
something different.

Thanks,

Gonzalo


Louis Alexander wrote:
> Is this not an appropriate place to use a SDP attribute such as a=sendonly
> or a=inactive?
> 
> Louis
> 
> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: Tuesday, June 21, 2005 9:35 AM
> To: Gonzalo Camarillo
> Cc: mmusic
> Subject: Re: [MMUSIC] Blank IPv6 c lines
> 
> 
> 
> Gonzalo Camarillo wrote:
> 
>>Folks,
>>
>>when a SIP user agent cannot provide an IPv4 address for some reason 
>>(e.g., in third-party call control scenarios) it uses the following 'c' 
>>line:
>>
>>c=IN IP4 0.0.0.0
>>
>>Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
>>with something.
> 
> 
> AFAIK we don't have an equivalent.
> 
> But why would we need one? Does it really matter if the "null" address 
> is IPv4 or IPv6? Either way I am not going to be sending or receiving 
> with it.
> 
> 	Paul
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo

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


From mmusic-bounces@ietf.org  Tue Jun 21 11:12:50 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29258
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 11:12:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkkoh-00083y-Us
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 11:37:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkkQf-0000QW-Qa; Tue, 21 Jun 2005 11:12:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkkQe-0000Q8-TK
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 11:12:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29255
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 11:12:42 -0400 (EDT)
Received: from cmailg2.svr.pol.co.uk ([195.92.195.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dkkoa-00083n-92
	for mmusic@ietf.org; Tue, 21 Jun 2005 11:37:29 -0400
Received: from user-5893.l1.c4.dsl.pol.co.uk ([81.79.151.5] helo=RW)
	by cmailg2.svr.pol.co.uk with smtp (Exim 4.41)
	id 1DkkQQ-0005Yr-S1; Tue, 21 Jun 2005 16:12:31 +0100
Message-ID: <04bd01c57673$a29e3100$6400a8c0@RW>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
        "Louis Alexander" <louis.alexander@logicacmg.com>
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
Date: Tue, 21 Jun 2005 16:12:23 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit
Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>, "'mmusic'" <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
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit

Gonzalo,

I have a vague recollection of an IESG review comment that suggested using 
the .invalid domain in this context, even for IPv4 (because 0.0.0.0 wasn't a 
real address).  I'm not sure what the details were though, or where to find 
out more.  Maybe it was with regard to third party control, or offer answer. 
In that case it was decided that such an option wouldn't be backward 
compatible with what was deployed, but it maybe appropriate for IPv6.

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware
http://www.tech-know-ware.com/lmx
for LMX XML to C++ binding
(or http://www.xml2cpp.com)
=============================================

----- Original Message ----- 
From: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
To: "Louis Alexander" <louis.alexander@logicacmg.com>
Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>; "'mmusic'" <mmusic@ietf.org>
Sent: Tuesday, June 21, 2005 3:48 PM
Subject: Re: [MMUSIC] Blank IPv6 c lines


> Paul,
>
> I am concerned with IPv6-only user agents. If they see an IP4 address they 
> will assume they do not understand it. They will not even parse the 
> 0.0.0.0 part. We may also think of a solution that is address type 
> independent. Something like c=null.
>
> Louis,
>
> an inactive stream still carries RTCP traffic... a null c line is 
> something different.
>
> Thanks,
>
> Gonzalo
>
>
> Louis Alexander wrote:
>> Is this not an appropriate place to use a SDP attribute such as 
>> a=sendonly
>> or a=inactive?
>>
>> Louis
>>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf 
>> Of
>> Paul Kyzivat
>> Sent: Tuesday, June 21, 2005 9:35 AM
>> To: Gonzalo Camarillo
>> Cc: mmusic
>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>
>>
>>
>> Gonzalo Camarillo wrote:
>>
>>>Folks,
>>>
>>>when a SIP user agent cannot provide an IPv4 address for some reason 
>>>(e.g., in third-party call control scenarios) it uses the following 'c' 
>>>line:
>>>
>>>c=IN IP4 0.0.0.0
>>>
>>>Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
>>>with something.
>>
>>
>> AFAIK we don't have an equivalent.
>>
>> But why would we need one? Does it really matter if the "null" address is 
>> IPv4 or IPv6? Either way I am not going to be sending or receiving with 
>> it.
>>
>> Paul
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> This e-mail and any attachment is for authorised use by the intended
>> recipient(s) only. It may contain proprietary material, confidential
>> information and/or be subject to legal privilege. It should not be 
>> copied,
>> disclosed to, retained or used by, any other party. If you are not an
>> intended recipient then please promptly delete this e-mail and any
>> attachment and all copies and inform the sender. Thank you.
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>
> -- 
> Gonzalo Camarillo         Phone :  +358  9 299 33 71
> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
> Telecom R&D               Fax   :  +358  9 299 30 52
> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
> Finland                   http://www.hut.fi/~gonzalo
>
> _______________________________________________
> 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 Jun 21 12:26:12 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05623
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 12:26:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dklxj-0001oJ-4Z
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 12:51:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DklZU-0000zx-8D; Tue, 21 Jun 2005 12:25:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DklZS-0000zp-RF; Tue, 21 Jun 2005 12:25:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05606;
	Tue, 21 Jun 2005 12:25:52 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DklxO-0001ng-Ti; Tue, 21 Jun 2005 12:50:40 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:56393)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1DklZF-0008LU-KP; Tue, 21 Jun 2005 17:25:41 +0100
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 21 Jun 2005 17:25:34 +0100
To: IETF MMUSIC working group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Naming of RTP payload formats within SDP
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit

I'd like to draw the attention of the working group to the IESG draft  
"A question on Media Type Registrations" which has recently been  
submitted:

     http://www.ietf.org/internet-drafts/draft-iesg-media-type-00.txt

There has been considerable controversy on the <ietf-types@iana.org>  
mailing list over the use of MIME media types to identify RTP payload  
formats within SDP, triggered by our attempted registration of RTP  
payload formats for real-time text conversation. This has led some in  
the community to review the use of media types to identify RTP  
payload formats, and to suggest it is inappropriate to use the  
existing media types registry for this purpose. The above mentioned  
draft summarises the issues, suggests three possible future  
directions for use of media types, and solicits feedback from the  
community. The three directions are (from section 2 of the draft):

"All media type protocols may specify handling" -- this is  
essentially the status quo, requiring no changes to RTP payload  
format naming in SDP.

"MIME handling is the model for other using protocols" -- this would  
prevent registrations for media types which cannot be passed directly  
to a MIME parser, in effect preventing RTP payload types from using  
the media types namespace and requiring (at least a partial) registry  
split.

"Registry split" -- the media types registry is split into two, with  
all RTP payload formats moving to a new registry. This would require  
updates to all RFCs that define RTP payload formats, reference the  
SDP "m=" and "a=rtpmap:" lines to name RTP payload formats or other  
media types, or reference MIME media types to name RTP payload formats.

I would strongly urge you to read the draft, and to consider the  
effects of either of the latter two directions on RTP, SDP, SIP and  
RTSP. Comments should be sent to either <iesg@ietf.org> or  
<ietf@ietf.org> before 1st July 2005.

Colin

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


From mmusic-bounces@ietf.org  Tue Jun 21 13:18:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09267
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 13:18:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkmm2-00035e-41
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 13:42:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkmNI-0001f4-Ct; Tue, 21 Jun 2005 13:17:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkmNG-0001ez-Nl
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 13:17:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09168
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 13:17:19 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkmlD-00033R-8c
	for mmusic@ietf.org; Tue, 21 Jun 2005 13:42:08 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by sj-iport-4.cisco.com with ESMTP; 21 Jun 2005 10:16:38 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5LHEho8014213; 
	Tue, 21 Jun 2005 13:16:36 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 13:16:02 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 13:16:16 -0400
Message-ID: <42B84B5F.7000509@cisco.com>
Date: Tue, 21 Jun 2005 13:16:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Louis Alexander <louis.alexander@logicacmg.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <40qi1j$3rkoir@sj-inbound-a.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 17:16:16.0764 (UTC)
	FILETIME=[EF0303C0:01C57684]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>,
        "'mmusic'" <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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

The a= solution is preferred when possible. However there are cases when 
one party has no address to use. Some 3pcc scenarios fall into this, 
where a node that does switching but has no media capability must 
construct an offer.

	Paul

Louis Alexander wrote:
> Is this not an appropriate place to use a SDP attribute such as a=sendonly
> or a=inactive?
> 
> Louis
> 
> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: Tuesday, June 21, 2005 9:35 AM
> To: Gonzalo Camarillo
> Cc: mmusic
> Subject: Re: [MMUSIC] Blank IPv6 c lines
> 
> 
> 
> Gonzalo Camarillo wrote:
> 
>>Folks,
>>
>>when a SIP user agent cannot provide an IPv4 address for some reason 
>>(e.g., in third-party call control scenarios) it uses the following 'c' 
>>line:
>>
>>c=IN IP4 0.0.0.0
>>
>>Do we have an equivalent for IPv6 'c' lines? If not, we need to come up 
>>with something.
> 
> 
> AFAIK we don't have an equivalent.
> 
> But why would we need one? Does it really matter if the "null" address 
> is IPv4 or IPv6? Either way I am not going to be sending or receiving 
> with it.
> 
> 	Paul
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
> 

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


From mmusic-bounces@ietf.org  Tue Jun 21 13:22:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09654
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 13:22:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkmpt-0003F3-L9
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 13:46:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkmQX-0002jF-68; Tue, 21 Jun 2005 13:20:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkmQV-0002jA-EW
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 13:20:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09548
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 13:20:40 -0400 (EDT)
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.33)
	id 1DkmoT-0003By-1s
	for mmusic@ietf.org; Tue, 21 Jun 2005 13:45:29 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 21 Jun 2005 10:20:34 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5LHKEqw026301;
	Tue, 21 Jun 2005 10:20:31 -0700 (PDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 13:19:20 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 13:19:22 -0400
Message-ID: <42B84C17.3080302@cisco.com>
Date: Tue, 21 Jun 2005 13:19:19 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 17:19:22.0130 (UTC)
	FILETIME=[5D7F9F20:01C57685]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: "'mmusic'" <mmusic@ietf.org>,
        Louis Alexander <louis.alexander@logicacmg.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:
> Paul,
> 
> I am concerned with IPv6-only user agents. If they see an IP4 address 
> they will assume they do not understand it. They will not even parse the 
> 0.0.0.0 part. We may also think of a solution that is address type 
> independent. Something like c=null.

Anything one does here introduces backward compatibility issues for 
those that already support the c=IN IP4 0.0.0.0 but nothing else. And 
even if you were to invent something else, the IPv6 UAs will need to be 
changed to support it. Why not just change them to support this 
particular special case of an IPv4 address? Just consider it a peculiar 
notation for c=null.

	Paul

> Louis,
> 
> an inactive stream still carries RTCP traffic... a null c line is 
> something different.
> 
> Thanks,
> 
> Gonzalo
> 
> 
> Louis Alexander wrote:
> 
>> Is this not an appropriate place to use a SDP attribute such as 
>> a=sendonly
>> or a=inactive?
>>
>> Louis
>>
>> -----Original Message-----
>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On 
>> Behalf Of
>> Paul Kyzivat
>> Sent: Tuesday, June 21, 2005 9:35 AM
>> To: Gonzalo Camarillo
>> Cc: mmusic
>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>
>>
>>
>> Gonzalo Camarillo wrote:
>>
>>> Folks,
>>>
>>> when a SIP user agent cannot provide an IPv4 address for some reason 
>>> (e.g., in third-party call control scenarios) it uses the following 
>>> 'c' line:
>>>
>>> c=IN IP4 0.0.0.0
>>>
>>> Do we have an equivalent for IPv6 'c' lines? If not, we need to come 
>>> up with something.
>>
>>
>>
>> AFAIK we don't have an equivalent.
>>
>> But why would we need one? Does it really matter if the "null" address 
>> is IPv4 or IPv6? Either way I am not going to be sending or receiving 
>> with it.
>>
>>     Paul
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> This e-mail and any attachment is for authorised use by the intended
>> recipient(s) only. It may contain proprietary material, confidential
>> information and/or be subject to legal privilege. It should not be 
>> copied,
>> disclosed to, retained or used by, any other party. If you are not an
>> intended recipient then please promptly delete this e-mail and any
>> attachment and all copies and inform the sender. Thank you.
>>
>>
>> _______________________________________________
>> 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 Jun 21 13:33:42 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10522
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 13:33:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkn14-0003YB-Ij
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 13:58:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkmYR-0004WH-6B; Tue, 21 Jun 2005 13:28:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkmYQ-0004W8-9D
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 13:28:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10201
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 13:28:51 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkmwN-0003SB-UT
	for mmusic@ietf.org; Tue, 21 Jun 2005 13:53:40 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 21 Jun 2005 13:28:45 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5LHRcnv018065; 
	Tue, 21 Jun 2005 13:27:57 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 13:27:15 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 13:27:33 -0400
Message-ID: <42B84E02.3070207@cisco.com>
Date: Tue, 21 Jun 2005 13:27:30 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pete Cordell <pete@tech-know-ware.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
	<04bd01c57673$a29e3100$6400a8c0@RW>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 17:27:33.0703 (UTC)
	FILETIME=[827FB570:01C57686]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Content-Transfer-Encoding: 7bit
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
        Louis Alexander <louis.alexander@logicacmg.com>,
        "'mmusic'" <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
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: 7bit



Pete Cordell wrote:
> Gonzalo,
> 
> I have a vague recollection of an IESG review comment that suggested 
> using the .invalid domain in this context, even for IPv4 (because 
> 0.0.0.0 wasn't a real address).  I'm not sure what the details were 
> though, or where to find out more.  Maybe it was with regard to third 
> party control, or offer answer. In that case it was decided that such an 
> option wouldn't be backward compatible with what was deployed, but it 
> maybe appropriate for IPv6.

Yes, there was such a proposal. And yes, I pointed out that it wasn't 
backwards compatible. So I *think* the whole idea was dropped.

Because of the need to preserve backward compatibility, UAs will need to 
support c=IN IP4 0.0.0.0. I see little value in introducing another 
notation, which will simply further complicate implementations.

About the only thing that might be achieved by coming up with some other 
notation for this is to improve the "elegance" of the representation. 
But "elegance" and "sdp" don't belong in the same sentence, so I 
wouldn't spend much time on that.

As inelegant as it is, I think it would be simpler and less disruptive 
to simply declare c=IN IP4 0.0.0.0 as *the* way to specify "no address", 
that should be understood regardless of what transport protocol is 
otherwise used.

	Paul

> Pete.
> -- 
> =============================================
> Pete Cordell
> Tech-Know-Ware
> http://www.tech-know-ware.com/lmx
> for LMX XML to C++ binding
> (or http://www.xml2cpp.com)
> =============================================
> 
> ----- Original Message ----- From: "Gonzalo Camarillo" 
> <Gonzalo.Camarillo@ericsson.com>
> To: "Louis Alexander" <louis.alexander@logicacmg.com>
> Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>; "'mmusic'" <mmusic@ietf.org>
> Sent: Tuesday, June 21, 2005 3:48 PM
> Subject: Re: [MMUSIC] Blank IPv6 c lines
> 
> 
>> Paul,
>>
>> I am concerned with IPv6-only user agents. If they see an IP4 address 
>> they will assume they do not understand it. They will not even parse 
>> the 0.0.0.0 part. We may also think of a solution that is address type 
>> independent. Something like c=null.
>>
>> Louis,
>>
>> an inactive stream still carries RTCP traffic... a null c line is 
>> something different.
>>
>> Thanks,
>>
>> Gonzalo
>>
>>
>> Louis Alexander wrote:
>>
>>> Is this not an appropriate place to use a SDP attribute such as 
>>> a=sendonly
>>> or a=inactive?
>>>
>>> Louis
>>>
>>> -----Original Message-----
>>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On 
>>> Behalf Of
>>> Paul Kyzivat
>>> Sent: Tuesday, June 21, 2005 9:35 AM
>>> To: Gonzalo Camarillo
>>> Cc: mmusic
>>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>>
>>>
>>>
>>> Gonzalo Camarillo wrote:
>>>
>>>> Folks,
>>>>
>>>> when a SIP user agent cannot provide an IPv4 address for some reason 
>>>> (e.g., in third-party call control scenarios) it uses the following 
>>>> 'c' line:
>>>>
>>>> c=IN IP4 0.0.0.0
>>>>
>>>> Do we have an equivalent for IPv6 'c' lines? If not, we need to come 
>>>> up with something.
>>>
>>>
>>>
>>> AFAIK we don't have an equivalent.
>>>
>>> But why would we need one? Does it really matter if the "null" 
>>> address is IPv4 or IPv6? Either way I am not going to be sending or 
>>> receiving with it.
>>>
>>> Paul
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>> This e-mail and any attachment is for authorised use by the intended
>>> recipient(s) only. It may contain proprietary material, confidential
>>> information and/or be subject to legal privilege. It should not be 
>>> copied,
>>> disclosed to, retained or used by, any other party. If you are not an
>>> intended recipient then please promptly delete this e-mail and any
>>> attachment and all copies and inform the sender. Thank you.
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>> -- 
>> Gonzalo Camarillo         Phone :  +358  9 299 33 71
>> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
>> Telecom R&D               Fax   :  +358  9 299 30 52
>> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
>> Finland                   http://www.hut.fi/~gonzalo
>>
>> _______________________________________________
>> 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 Jun 21 14:27:34 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15088
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 14:27:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DknrB-0004uz-IP
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 14:52:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DknRH-0005q0-JO; Tue, 21 Jun 2005 14:25:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DknRF-0005pp-Am
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 14:25:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14892
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 14:25:32 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DknpB-0004s2-2o
	for mmusic@ietf.org; Tue, 21 Jun 2005 14:50:19 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id DC9CA96A; 
	Tue, 21 Jun 2005 20:25:23 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 20:25:23 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 20:25:22 +0200
Received: from [131.160.126.5] (rvi2-126-5.lmf.ericsson.se [131.160.126.5])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 362E12558;
	Tue, 21 Jun 2005 21:25:22 +0300 (EEST)
Message-ID: <42B85B90.7070807@ericsson.com>
Date: Tue, 21 Jun 2005 21:25:20 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
	<04bd01c57673$a29e3100$6400a8c0@RW> <42B84E02.3070207@cisco.com>
In-Reply-To: <42B84E02.3070207@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 18:25:22.0736 (UTC)
	FILETIME=[96342300:01C5768E]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Content-Transfer-Encoding: 7bit
Cc: Pete Cordell <pete@tech-know-ware.com>, "'mmusic'" <mmusic@ietf.org>,
        Louis Alexander <louis.alexander@logicacmg.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
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Content-Transfer-Encoding: 7bit

Paul,

I agree with you on all those points. However, I am thinking of the case 
when a user agent needs to provide an IPv6 and an IPv4 address using 
ANAT (e.g., the user agent is a 3pcc controller). How does the answerer 
knows that what is being offered is an IPv6 line and an IPv4 line? The 
answerer will only see two m lines with c=IN IP4 0.0.0.0

Thanks,

Gonzalo

Paul Kyzivat wrote:
> 
> 
> Pete Cordell wrote:
> 
>> Gonzalo,
>>
>> I have a vague recollection of an IESG review comment that suggested 
>> using the .invalid domain in this context, even for IPv4 (because 
>> 0.0.0.0 wasn't a real address).  I'm not sure what the details were 
>> though, or where to find out more.  Maybe it was with regard to third 
>> party control, or offer answer. In that case it was decided that such 
>> an option wouldn't be backward compatible with what was deployed, but 
>> it maybe appropriate for IPv6.
> 
> 
> Yes, there was such a proposal. And yes, I pointed out that it wasn't 
> backwards compatible. So I *think* the whole idea was dropped.
> 
> Because of the need to preserve backward compatibility, UAs will need to 
> support c=IN IP4 0.0.0.0. I see little value in introducing another 
> notation, which will simply further complicate implementations.
> 
> About the only thing that might be achieved by coming up with some other 
> notation for this is to improve the "elegance" of the representation. 
> But "elegance" and "sdp" don't belong in the same sentence, so I 
> wouldn't spend much time on that.
> 
> As inelegant as it is, I think it would be simpler and less disruptive 
> to simply declare c=IN IP4 0.0.0.0 as *the* way to specify "no address", 
> that should be understood regardless of what transport protocol is 
> otherwise used.
> 
>     Paul
> 
>> Pete.
>> -- 
>> =============================================
>> Pete Cordell
>> Tech-Know-Ware
>> http://www.tech-know-ware.com/lmx
>> for LMX XML to C++ binding
>> (or http://www.xml2cpp.com)
>> =============================================
>>
>> ----- Original Message ----- From: "Gonzalo Camarillo" 
>> <Gonzalo.Camarillo@ericsson.com>
>> To: "Louis Alexander" <louis.alexander@logicacmg.com>
>> Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>; "'mmusic'" <mmusic@ietf.org>
>> Sent: Tuesday, June 21, 2005 3:48 PM
>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>
>>
>>> Paul,
>>>
>>> I am concerned with IPv6-only user agents. If they see an IP4 address 
>>> they will assume they do not understand it. They will not even parse 
>>> the 0.0.0.0 part. We may also think of a solution that is address 
>>> type independent. Something like c=null.
>>>
>>> Louis,
>>>
>>> an inactive stream still carries RTCP traffic... a null c line is 
>>> something different.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>>
>>> Louis Alexander wrote:
>>>
>>>> Is this not an appropriate place to use a SDP attribute such as 
>>>> a=sendonly
>>>> or a=inactive?
>>>>
>>>> Louis
>>>>
>>>> -----Original Message-----
>>>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On 
>>>> Behalf Of
>>>> Paul Kyzivat
>>>> Sent: Tuesday, June 21, 2005 9:35 AM
>>>> To: Gonzalo Camarillo
>>>> Cc: mmusic
>>>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>>>
>>>>
>>>>
>>>> Gonzalo Camarillo wrote:
>>>>
>>>>> Folks,
>>>>>
>>>>> when a SIP user agent cannot provide an IPv4 address for some 
>>>>> reason (e.g., in third-party call control scenarios) it uses the 
>>>>> following 'c' line:
>>>>>
>>>>> c=IN IP4 0.0.0.0
>>>>>
>>>>> Do we have an equivalent for IPv6 'c' lines? If not, we need to 
>>>>> come up with something.
>>>>
>>>>
>>>>
>>>>
>>>> AFAIK we don't have an equivalent.
>>>>
>>>> But why would we need one? Does it really matter if the "null" 
>>>> address is IPv4 or IPv6? Either way I am not going to be sending or 
>>>> receiving with it.
>>>>
>>>> Paul
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>>
>>>>
>>>> This e-mail and any attachment is for authorised use by the intended
>>>> recipient(s) only. It may contain proprietary material, confidential
>>>> information and/or be subject to legal privilege. It should not be 
>>>> copied,
>>>> disclosed to, retained or used by, any other party. If you are not an
>>>> intended recipient then please promptly delete this e-mail and any
>>>> attachment and all copies and inform the sender. Thank you.
>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>>>
>>>
>>> -- 
>>> Gonzalo Camarillo         Phone :  +358  9 299 33 71
>>> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
>>> Telecom R&D               Fax   :  +358  9 299 30 52
>>> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
>>> Finland                   http://www.hut.fi/~gonzalo
>>>
>>> _______________________________________________
>>> 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
>>

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo

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


From mmusic-bounces@ietf.org  Tue Jun 21 15:40:18 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23851
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 15:40:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dkoza-0007AQ-3P
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 16:05:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkoaJ-0002vm-8B; Tue, 21 Jun 2005 15:38:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkoaH-0002vh-9C
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 15:38:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23774
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 15:38:55 -0400 (EDT)
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.33)
	id 1DkoyF-00077l-Jw
	for mmusic@ietf.org; Tue, 21 Jun 2005 16:03:44 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 21 Jun 2005 12:38:47 -0700
X-IronPort-AV: i="3.93,218,1115017200"; 
	d="scan'208"; a="281470578:sNHT36300226"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5LJcfFs021566;
	Tue, 21 Jun 2005 12:38:44 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 15:38:32 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 15:38:32 -0400
Message-ID: <42B86CB7.2040302@cisco.com>
Date: Tue, 21 Jun 2005 15:38:31 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
	<04bd01c57673$a29e3100$6400a8c0@RW>
	<42B84E02.3070207@cisco.com> <42B85B90.7070807@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 19:38:32.0225 (UTC)
	FILETIME=[CE8B0110:01C57698]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Content-Transfer-Encoding: 7bit
Cc: Pete Cordell <pete@tech-know-ware.com>, "'mmusic'" <mmusic@ietf.org>,
        Louis Alexander <louis.alexander@logicacmg.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
X-Spam-Score: 1.8 (+)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:
> Paul,
> 
> I agree with you on all those points. However, I am thinking of the case 
> when a user agent needs to provide an IPv6 and an IPv4 address using 
> ANAT (e.g., the user agent is a 3pcc controller). How does the answerer 
> knows that what is being offered is an IPv6 line and an IPv4 line? The 
> answerer will only see two m lines with c=IN IP4 0.0.0.0

The answerer isn't being offered either an IPv4 or an IPv6 address - it 
is being offered a null address. In the case when the null address is 
being offered, what purpose would be served by offering both a v4 and a 
v6 form?

If a null address is being offered, then before real communication can 
occur a new address will have to be negotiated. At that time a choice of 
v4 and v6 can be made.

	Paul

> Thanks,
> 
> Gonzalo
> 
> Paul Kyzivat wrote:
> 
>>
>>
>> Pete Cordell wrote:
>>
>>> Gonzalo,
>>>
>>> I have a vague recollection of an IESG review comment that suggested 
>>> using the .invalid domain in this context, even for IPv4 (because 
>>> 0.0.0.0 wasn't a real address).  I'm not sure what the details were 
>>> though, or where to find out more.  Maybe it was with regard to third 
>>> party control, or offer answer. In that case it was decided that such 
>>> an option wouldn't be backward compatible with what was deployed, but 
>>> it maybe appropriate for IPv6.
>>
>>
>>
>> Yes, there was such a proposal. And yes, I pointed out that it wasn't 
>> backwards compatible. So I *think* the whole idea was dropped.
>>
>> Because of the need to preserve backward compatibility, UAs will need 
>> to support c=IN IP4 0.0.0.0. I see little value in introducing another 
>> notation, which will simply further complicate implementations.
>>
>> About the only thing that might be achieved by coming up with some 
>> other notation for this is to improve the "elegance" of the 
>> representation. But "elegance" and "sdp" don't belong in the same 
>> sentence, so I wouldn't spend much time on that.
>>
>> As inelegant as it is, I think it would be simpler and less disruptive 
>> to simply declare c=IN IP4 0.0.0.0 as *the* way to specify "no 
>> address", that should be understood regardless of what transport 
>> protocol is otherwise used.
>>
>>     Paul
>>
>>> Pete.
>>> -- 
>>> =============================================
>>> Pete Cordell
>>> Tech-Know-Ware
>>> http://www.tech-know-ware.com/lmx
>>> for LMX XML to C++ binding
>>> (or http://www.xml2cpp.com)
>>> =============================================
>>>
>>> ----- Original Message ----- From: "Gonzalo Camarillo" 
>>> <Gonzalo.Camarillo@ericsson.com>
>>> To: "Louis Alexander" <louis.alexander@logicacmg.com>
>>> Cc: "'Paul Kyzivat'" <pkyzivat@cisco.com>; "'mmusic'" <mmusic@ietf.org>
>>> Sent: Tuesday, June 21, 2005 3:48 PM
>>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>>
>>>
>>>> Paul,
>>>>
>>>> I am concerned with IPv6-only user agents. If they see an IP4 
>>>> address they will assume they do not understand it. They will not 
>>>> even parse the 0.0.0.0 part. We may also think of a solution that is 
>>>> address type independent. Something like c=null.
>>>>
>>>> Louis,
>>>>
>>>> an inactive stream still carries RTCP traffic... a null c line is 
>>>> something different.
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>>
>>>> Louis Alexander wrote:
>>>>
>>>>> Is this not an appropriate place to use a SDP attribute such as 
>>>>> a=sendonly
>>>>> or a=inactive?
>>>>>
>>>>> Louis
>>>>>
>>>>> -----Original Message-----
>>>>> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On 
>>>>> Behalf Of
>>>>> Paul Kyzivat
>>>>> Sent: Tuesday, June 21, 2005 9:35 AM
>>>>> To: Gonzalo Camarillo
>>>>> Cc: mmusic
>>>>> Subject: Re: [MMUSIC] Blank IPv6 c lines
>>>>>
>>>>>
>>>>>
>>>>> Gonzalo Camarillo wrote:
>>>>>
>>>>>> Folks,
>>>>>>
>>>>>> when a SIP user agent cannot provide an IPv4 address for some 
>>>>>> reason (e.g., in third-party call control scenarios) it uses the 
>>>>>> following 'c' line:
>>>>>>
>>>>>> c=IN IP4 0.0.0.0
>>>>>>
>>>>>> Do we have an equivalent for IPv6 'c' lines? If not, we need to 
>>>>>> come up with something.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> AFAIK we don't have an equivalent.
>>>>>
>>>>> But why would we need one? Does it really matter if the "null" 
>>>>> address is IPv4 or IPv6? Either way I am not going to be sending or 
>>>>> receiving with it.
>>>>>
>>>>> Paul
>>>>>
>>>>> _______________________________________________
>>>>> mmusic mailing list
>>>>> mmusic@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>>>
>>>>>
>>>>> This e-mail and any attachment is for authorised use by the intended
>>>>> recipient(s) only. It may contain proprietary material, confidential
>>>>> information and/or be subject to legal privilege. It should not be 
>>>>> copied,
>>>>> disclosed to, retained or used by, any other party. If you are not an
>>>>> intended recipient then please promptly delete this e-mail and any
>>>>> attachment and all copies and inform the sender. Thank you.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> mmusic mailing list
>>>>> mmusic@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Gonzalo Camarillo         Phone :  +358  9 299 33 71
>>>> Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
>>>> Telecom R&D               Fax   :  +358  9 299 30 52
>>>> FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
>>>> Finland                   http://www.hut.fi/~gonzalo
>>>>
>>>> _______________________________________________
>>>> 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 Jun 21 16:12:11 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00454
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 16:12:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkpUQ-0000xa-PT
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 16:37:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dkomn-0005YQ-SQ; Tue, 21 Jun 2005 15:51:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkomm-0005YC-S0
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 15:51:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24926
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 15:51:51 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkpAk-0007VU-Bb
	for mmusic@ietf.org; Tue, 21 Jun 2005 16:16:39 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id EFDC7AD9; 
	Tue, 21 Jun 2005 21:51:35 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 21:50:12 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Jun 2005 21:50:11 +0200
Received: from [131.160.126.5] (rvi2-126-5.lmf.ericsson.se [131.160.126.5])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 681452558;
	Tue, 21 Jun 2005 22:50:11 +0300 (EEST)
Message-ID: <42B86F71.8080407@ericsson.com>
Date: Tue, 21 Jun 2005 22:50:09 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
	<04bd01c57673$a29e3100$6400a8c0@RW>
	<42B84E02.3070207@cisco.com> <42B85B90.7070807@ericsson.com>
	<42B86CB7.2040302@cisco.com>
In-Reply-To: <42B86CB7.2040302@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 19:50:11.0900 (UTC)
	FILETIME=[6F94EFC0:01C5769A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: Pete Cordell <pete@tech-know-ware.com>, "'mmusic'" <mmusic@ietf.org>,
        Louis Alexander <louis.alexander@logicacmg.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit

Paul,

the offerer is offering a null address, but the answerer needs to know 
which address type to provide in the answer. If the offer contains a 
null IPv4 and a null IPV6 address, the answerer knows that it can use 
any of them. If the offer just contains a generic null address, the 
answerer does not know which address type to use in the answer.

That is, even if the offerer cannot provide a particular address at this 
point, it can at least negotiate the address type to be used.

Gonzalo


Paul Kyzivat wrote:
> 
> 
> Gonzalo Camarillo wrote:
> 
>> Paul,
>>
>> I agree with you on all those points. However, I am thinking of the 
>> case when a user agent needs to provide an IPv6 and an IPv4 address 
>> using ANAT (e.g., the user agent is a 3pcc controller). How does the 
>> answerer knows that what is being offered is an IPv6 line and an IPv4 
>> line? The answerer will only see two m lines with c=IN IP4 0.0.0.0
> 
> 
> The answerer isn't being offered either an IPv4 or an IPv6 address - it 
> is being offered a null address. In the case when the null address is 
> being offered, what purpose would be served by offering both a v4 and a 
> v6 form?
> 
> If a null address is being offered, then before real communication can 
> occur a new address will have to be negotiated. At that time a choice of 
> v4 and v6 can be made.
> 
>     Paul
> 

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


From mmusic-bounces@ietf.org  Tue Jun 21 17:05:48 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14525
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 17:05:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkqKM-0005lo-Gn
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 17:30:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkpuU-0006qW-Mg; Tue, 21 Jun 2005 17:03:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkpuQ-0006pQ-R5
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 17:03:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14271
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 17:03:48 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkqIQ-0005hw-Ei
	for mmusic@ietf.org; Tue, 21 Jun 2005 17:28:38 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 21 Jun 2005 17:03:43 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5LL3Jnw020898; 
	Tue, 21 Jun 2005 17:03:39 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Tue, 21 Jun 2005 17:03:09 -0400
Received: from cisco.com ([161.44.79.130]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 21 Jun 2005 17:03:10 -0400
Message-ID: <42B8808E.5040200@cisco.com>
Date: Tue, 21 Jun 2005 17:03:10 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org> <42B828A1.50605@ericsson.com>
	<04bd01c57673$a29e3100$6400a8c0@RW>
	<42B84E02.3070207@cisco.com> <42B85B90.7070807@ericsson.com>
	<42B86CB7.2040302@cisco.com> <42B86F71.8080407@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Jun 2005 21:03:10.0614 (UTC)
	FILETIME=[A17FAB60:01C576A4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc: Pete Cordell <pete@tech-know-ware.com>, "'mmusic'" <mmusic@ietf.org>,
        Louis Alexander <louis.alexander@logicacmg.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:
> Paul,
> 
> the offerer is offering a null address, but the answerer needs to know 
> which address type to provide in the answer. If the offer contains a 
> null IPv4 and a null IPV6 address, the answerer knows that it can use 
> any of them. If the offer just contains a generic null address, the 
> answerer does not know which address type to use in the answer.
> 
> That is, even if the offerer cannot provide a particular address at this 
> point, it can at least negotiate the address type to be used.

Hmm. I just looked at 3264, and I find no disucssion of negotiation of 
network type. As far as 3264 is concerned it appears fine to offer an 
IPv4 address and get an answer with an IPv6 address. Of course in 
practice this may not be fine. (Or is this specified someplace I missed.)

I think you are assuming that there is an additional rule in 
offer/answer - that answered network type should be the same as offered 
network type. If so, then there is indeed a problem if somebody wants to 
offer a null address but desires an IPv6 answer. If so, then I guess it 
may be necessary to devise an IPv6 equivalent of c=IN IP4 0.0.0.0. If 
so, then I think an ammendment to 3264 is also required.

	Paul

> Gonzalo
> 
> 
> Paul Kyzivat wrote:
> 
>>
>>
>> Gonzalo Camarillo wrote:
>>
>>> Paul,
>>>
>>> I agree with you on all those points. However, I am thinking of the 
>>> case when a user agent needs to provide an IPv6 and an IPv4 address 
>>> using ANAT (e.g., the user agent is a 3pcc controller). How does the 
>>> answerer knows that what is being offered is an IPv6 line and an IPv4 
>>> line? The answerer will only see two m lines with c=IN IP4 0.0.0.0
>>
>>
>>
>> The answerer isn't being offered either an IPv4 or an IPv6 address - 
>> it is being offered a null address. In the case when the null address 
>> is being offered, what purpose would be served by offering both a v4 
>> and a v6 form?
>>
>> If a null address is being offered, then before real communication can 
>> occur a new address will have to be negotiated. At that time a choice 
>> of v4 and v6 can be made.
>>
>>     Paul
>>
> 

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


From mmusic-bounces@ietf.org  Tue Jun 21 19:37:52 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26802
	for <mmusic-archive@ietf.org>; Tue, 21 Jun 2005 19:37:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkshY-0002sm-4o
	for mmusic-archive@ietf.org; Tue, 21 Jun 2005 20:02:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DksFK-00042Q-So; Tue, 21 Jun 2005 19:33:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DksFJ-00042L-W5
	for mmusic@megatron.ietf.org; Tue, 21 Jun 2005 19:33:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26452
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 19:33:30 -0400 (EDT)
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DksdJ-0002kQ-Ni
	for mmusic@ietf.org; Tue, 21 Jun 2005 19:58:23 -0400
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
	by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j5LNXNDY004965
	for <mmusic@ietf.org>; Tue, 21 Jun 2005 16:33:23 -0700 (PDT)
Received: from relay4.apple.com (relay4.apple.com) by mailgate1.apple.com
	(Content Technologies SMTPRS 4.3.17) with ESMTP id
	<T71ac27f142118064e143c@mailgate1.apple.com>; 
	Tue, 21 Jun 2005 16:33:23 -0700
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay4.apple.com (8.12.11/8.12.11) with ESMTP id j5LNXJcf005432;
	Tue, 21 Jun 2005 16:33:21 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p0623054ebede524a61af@[17.202.35.52]>
In-Reply-To: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
Date: Tue, 21 Jun 2005 16:31:36 -0700
To: Colin Perkins <csp@csperkins.org>,
        IETF MMUSIC working group <mmusic@ietf.org>
From: Dave Singer <singer@apple.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

I have not (yet) replied to the IESG or IETF.  But I thought maybe 
some discussion here was worthwhile before doing so (you might set me 
straight).

I have been repeatedly troubled by people who want to use MIME types 
intended for RTP payloads as types for files.  This is especially 
acute in the case of MPEG-4 where the file MIME type is still not 
registered, but the RTP payload is.  Thus we find people trying to 
use video/mpeg4-generic or video/mp4v-es for MP4 files, though in 
fact they are for RTP payloads.  (video/mp4 is intended to be 
registered for files, by the way).  Even if the latter were 
registered, it's still confusing having them in the same registry.

Also, the restrictions on 'true' MIME types are, as noted in the I-D, 
a stumbling block for RTP.  No-one I know expects to be able to treat 
an RTP TEXT payload as text/plain, for example.

So, I tend to solution (3).  Split the registry.  Are there *any* 
types valid both for a mail message and an RTP payload?  If not, 
splitting is harmless.  We can start the RTP 'tree' with video/, 
audio/, text/ etc. so the actual 'bits on the wire' (e.g. in an 
RTPMAP) don't change, right?
-- 
David Singer
Apple Computer/QuickTime

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


From mmusic-bounces@ietf.org  Wed Jun 22 00:56:03 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21107
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 00:56:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkxfW-0002GU-K2
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 01:20:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkxEq-0007wN-Hs; Wed, 22 Jun 2005 00:53:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkxEo-0007wI-00
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 00:53:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20651
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 00:53:19 -0400 (EDT)
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.33)
	id 1Dkxcr-0002Bz-N8
	for mmusic@ietf.org; Wed, 22 Jun 2005 01:18:14 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 21 Jun 2005 21:53:10 -0700
X-IronPort-AV: i="3.93,219,1115017200"; 
	d="scan'208"; a="645085283:sNHT30446660"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5M4qqG2011312;
	Tue, 21 Jun 2005 21:53:05 -0700 (PDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 22 Jun 2005 00:51:21 -0400
Received: from [192.168.1.100] ([10.86.242.143]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Jun 2005 00:51:20 -0400
Message-ID: <42B8EE48.1090000@cisco.com>
Date: Wed, 22 Jun 2005 00:51:20 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [MMUSIC] Blank IPv6 c lines
References: <200506211347.JAA19635@ietf.org>
	<42B828A1.50605@ericsson.com>	<04bd01c57673$a29e3100$6400a8c0@RW>	<42B84E02.3070207@cisco.com>
	<42B85B90.7070807@ericsson.com>	<42B86CB7.2040302@cisco.com>
	<42B86F71.8080407@ericsson.com> <42B8808E.5040200@cisco.com>
In-Reply-To: <42B8808E.5040200@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2005 04:51:20.0866 (UTC)
	FILETIME=[0897F820:01C576E6]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: Pete Cordell <pete@tech-know-ware.com>,
        Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
        Louis Alexander <louis.alexander@logicacmg.com>,
        "'mmusic'" <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
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

inline.

Paul Kyzivat wrote:

> 
> 
> Gonzalo Camarillo wrote:
> 
>> Paul,
>>
>> the offerer is offering a null address, but the answerer needs to know 
>> which address type to provide in the answer. If the offer contains a 
>> null IPv4 and a null IPV6 address, the answerer knows that it can use 
>> any of them. If the offer just contains a generic null address, the 
>> answerer does not know which address type to use in the answer.
>>
>> That is, even if the offerer cannot provide a particular address at 
>> this point, it can at least negotiate the address type to be used.
> 
> 
> Hmm. I just looked at 3264, and I find no disucssion of negotiation of 
> network type. As far as 3264 is concerned it appears fine to offer an 
> IPv4 address and get an answer with an IPv6 address. Of course in 
> practice this may not be fine. (Or is this specified someplace I missed.)

I agree with Paul, this is not specified in RFC3264.

> 
> I think you are assuming that there is an additional rule in 
> offer/answer - that answered network type should be the same as offered 
> network type.

I think it should. Things will get really complicated and ugly 
otherwise. If I offer up a v4 address, how would the answerer know that 
it is OK to provide a v6 answer? It could only do so if the sender had 
the ability to send packets to a v6 address, which may not be possible. 
Also, over time, it has become clear that symmetric operation is highly 
preferable, and this is built-in to the ICE algorithms. Using different 
networks for send and receive obviously won't work with that.


> If so, then there is indeed a problem if somebody wants to 
> offer a null address but desires an IPv6 answer. If so, then I guess it 
> may be necessary to devise an IPv6 equivalent of c=IN IP4 0.0.0.0. If 
> so, then I think an ammendment to 3264 is also required.

I also agree here.

I'd suggest that, for v6, we allow for a .invalid domain name, but only 
for v6 endpoints. v4 would continue with 0.0.0.0. Since there are no v6 
endpoints doing this yet, this presents no backwards compatibility 
issue, as it did previously for v4.

Sounds like a small draft outlining changes to offer/answer for v6 is 
needed.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Wed Jun 22 04:56:55 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14932
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 04:56:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl1Qd-0008KI-MA
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 05:21:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl121-0003Sq-5x; Wed, 22 Jun 2005 04:56:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl11w-0003SV-PQ
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 04:56:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14909
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 04:56:18 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl1Q1-0008Jf-Jf
	for mmusic@ietf.org; Wed, 22 Jun 2005 05:21:15 -0400
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63428
	helo=[192.168.0.2])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Dl11m-0000JQ-3W; Wed, 22 Jun 2005 09:56:10 +0100
In-Reply-To: <p0623054ebede524a61af@[17.202.35.52]>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
	<p0623054ebede524a61af@[17.202.35.52]>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Date: Wed, 22 Jun 2005 09:56:02 +0100
To: Dave Singer <singer@apple.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

On 22 Jun 2005, at 00:31, Dave Singer wrote:
> I have not (yet) replied to the IESG or IETF.  But I thought maybe  
> some discussion here was worthwhile before doing so (you might set  
> me straight).
>
> I have been repeatedly troubled by people who want to use MIME  
> types intended for RTP payloads as types for files.  This is  
> especially acute in the case of MPEG-4 where the file MIME type is  
> still not registered, but the RTP payload is.  Thus we find people  
> trying to use video/mpeg4-generic or video/mp4v-es for MP4 files,  
> though in fact they are for RTP payloads.  (video/mp4 is intended  
> to be registered for files, by the way).  Even if the latter were  
> registered, it's still confusing having them in the same registry.

Would it be any less confusing to have similar looking names in a  
different registry? Especially since there would be the potential for  
conflicting use of names between the two registries.

> Also, the restrictions on 'true' MIME types are, as noted in the I- 
> D, a stumbling block for RTP.  No-one I know expects to be able to  
> treat an RTP TEXT payload as text/plain, for example.

This discussion was started because some in the MIME community think  
there is a real concern that some will expect to treat RTP text  
formats as text/plain.

> So, I tend to solution (3).  Split the registry.  Are there *any*  
> types valid both for a mail message and an RTP payload?

Yes. Several of the audio types are defined for use in both RTP and  
as a file format: audio/amr, audio/amr-wb, audio/L16, audio/smv,  
audio/evrc, audio/ilbc

> If not, splitting is harmless.  We can start the RTP 'tree' with  
> video/, audio/, text/ etc. so the actual 'bits on the wire' (e.g.  
> in an RTPMAP) don't change, right?

The bits wouldn't change, but there would be a pretty big semantic  
difference. Do we really want to restrict SDP to negotiating only RTP  
payload formats? We can use SDP to signal a session using the  
"application/bfcp" media type now - because there is a single  
namespace for all types. With a split registry we'd either have to  
give up this capability, or rework SDP to indicate which name space  
was intended.

Colin

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


From mmusic-bounces@ietf.org  Wed Jun 22 09:10:00 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06849
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 09:10:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5NZ-0007Ht-Si
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 09:34:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4uz-0003id-Jz; Wed, 22 Jun 2005 09:05:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl4ut-0003gN-E5
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 09:05:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06404
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 09:05:17 -0400 (EDT)
Received: from jalapeno.cc.columbia.edu ([128.59.29.5] ident=cu41754)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl5Iz-000773-Jb
	for mmusic@ietf.org; Wed, 22 Jun 2005 09:30:15 -0400
Received: from [192.168.0.31] (pool-141-153-173-119.mad.east.verizon.net
	[141.153.173.119]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id
	j5MD56GJ012726
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 22 Jun 2005 09:05:06 -0400 (EDT)
Message-ID: <42B961DD.30807@cs.columbia.edu>
Date: Wed, 22 Jun 2005 09:04:29 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
In-Reply-To: <CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Would it ever make sense to just convey a file type in SDP? I can't see 
how application/pdf or application/powerpoint or text/xml would be 
particularly useful. Thus, I'm not sure why one would ever need to 
indicate the namespace.

I agree that unplanned name collisions would be confusing, but the 
registries could be set up so that the two are coupled, i.e., a new one 
in either registry can't duplicate the name unless they are indeed the 
same bits on the wire.

Henning

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


From mmusic-bounces@ietf.org  Wed Jun 22 09:25:55 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08676
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 09:25:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5cy-0007td-EX
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 09:50:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl5EG-0006Fu-Qb; Wed, 22 Jun 2005 09:25:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl5EF-0006F7-Ln
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 09:25:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08490
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 09:25:17 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl5cH-0007p5-FH
	for mmusic@ietf.org; Wed, 22 Jun 2005 09:50:16 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 75D14EB4; 
	Wed, 22 Jun 2005 15:24:45 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Jun 2005 15:24:44 +0200
Received: from [147.214.34.71] ([147.214.34.71]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 22 Jun 2005 15:24:44 +0200
Message-ID: <42B9669C.9000202@ericsson.com>
Date: Wed, 22 Jun 2005 15:24:44 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
In-Reply-To: <42B961DD.30807@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2005 13:24:44.0488 (UTC)
	FILETIME=[C0FBAC80:01C5772D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
        Colin Perkins <csp@csperkins.org>, Dave Singer <singer@apple.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

Hi Henning,

A quick comment on your suggestion to be taken into consideration.

Henning Schulzrinne wrote:
> 
> I agree that unplanned name collisions would be confusing, but the 
> registries could be set up so that the two are coupled, i.e., a new one 
> in either registry can't duplicate the name unless they are indeed the 
> same bits on the wire.
> 

Me and Colin has been involved in discussion on what is considered the 
same bits on the wire with some of the APPS area folks. For example Ned 
Freed has been quite clear that he doesn't consider a solution like that 
for AMR to be the same media type between the file format and RTP 
payload format. Despite them producing the same basic output of a FT + Q 
header byte and a speech data frame. Sure in some cases the RTP payload 
format makes strange sorting of the bit, but the basic information is 
always there and is recovered after depacketization.

Especially problematic was that the files has a magic word in this 
beginning. That make them clearly different from interpreter point of view.

We also have some serious backwards compatibility issues. The audio/amr 
media type are probably supported in around a 100 million devices, most 
actually supporting both file format and RTP payload format. This being 
devices not easily upgraded as most are mobile phones.

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 Jun 22 11:02:17 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20530
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 11:02:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl78G-000355-Io
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 11:27:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6ju-0002cQ-RN; Wed, 22 Jun 2005 11:02:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl6js-0002bd-VU
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 11:02:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20498
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 11:02:01 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl780-00034T-OZ
	for mmusic@ietf.org; Wed, 22 Jun 2005 11:27:02 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:60175)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Dl6jh-0000PY-SH; Wed, 22 Jun 2005 16:01:53 +0100
In-Reply-To: <42B961DD.30807@cs.columbia.edu>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Date: Wed, 22 Jun 2005 16:01:46 +0100
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

On 22 Jun 2005, at 14:04, Henning Schulzrinne wrote:
> Would it ever make sense to just convey a file type in SDP? I can't  
> see how application/pdf or application/powerpoint or text/xml would  
> be particularly useful. Thus, I'm not sure why one would ever need  
> to indicate the namespace.

Because otherwise we're restricted to using the RTP payload format  
namespace with SDP, and can't use non-RTP formats (or vice versa)?

> I agree that unplanned name collisions would be confusing, but the  
> registries could be set up so that the two are coupled, i.e., a new  
> one in either registry can't duplicate the name unless they are  
> indeed the same bits on the wire.

So why not use the same namespace, and define restrictions on use?  
(i.e. the way  the registry has been managed for the last 7 years or  
so...)

What is the benefit of a change?

Colin

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


From mmusic-bounces@ietf.org  Wed Jun 22 12:48:41 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01322
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 12:48:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8nG-0006t7-Mx
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 13:13:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8Ot-00005k-O5; Wed, 22 Jun 2005 12:48:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl8Or-000057-F3
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 12:48:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01302
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 12:48:21 -0400 (EDT)
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl8mv-0006sb-FE
	for mmusic@ietf.org; Wed, 22 Jun 2005 13:13:22 -0400
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j5MGm1mD022172
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 22 Jun 2005 12:48:02 -0400 (EDT)
Message-ID: <42B9963C.7000305@cs.columbia.edu>
Date: Wed, 22 Jun 2005 12:47:56 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
In-Reply-To: <1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

> Because otherwise we're restricted to using the RTP payload format  
> namespace with SDP, and can't use non-RTP formats (or vice versa)?

Let's assume for a moment that we're only talking about identifying RTP 
payload types for now, not using SDP to convey some other media exchange 
(e.g., support of media types over MSRP). In that case, there are 
several sub-cases, assuming a split registry, if somebody wants to 
stream some data type X over RTP:

(1) Registrations exist in both --> no issue

(2) Registration exist in the "email" registry, but not in the RTP registry

   (2a) The very same bit pattern could be used for both and there are 
no special SDP parameters needed.

   (2b) A payload format is needed or RTP-specific parameters are needed.


We want to avoid case (2), in particular (2a). This case arises if 
somebody registers a new media type for "email", but the MMUSIC/AVT 
community doesn't find out until there are problems in implementations. 
Making sure that such registrations are passed on to an appropriate 
expert review in AVT/MMUSIC would allow us to catch this case and then 
decide whether an RTP version makes sense or not. My perception is that 
this is not currently happening, i.e., somebody could register an 
"email" type for audio/* and AVT would never find out (except by accident).



> 
>> I agree that unplanned name collisions would be confusing, but the  
>> registries could be set up so that the two are coupled, i.e., a new  
>> one in either registry can't duplicate the name unless they are  
>> indeed the same bits on the wire.
> 
> 
> So why not use the same namespace, and define restrictions on use?  
> (i.e. the way  the registry has been managed for the last 7 years or  
> so...)
> 
> What is the benefit of a change?

I see no major benefit to change the current setup, but I don't see that 
this would be a big deal, either.

I'd be curious as to whether there was a specific issue or incident that 
caused the movement to change the status quo.




> 
> Colin

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


From mmusic-bounces@ietf.org  Wed Jun 22 14:51:57 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16478
	for <mmusic-archive@ietf.org>; Wed, 22 Jun 2005 14:51:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlAU1-0005Cg-Vd
	for mmusic-archive@ietf.org; Wed, 22 Jun 2005 15:01:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlA4Z-00008S-AH; Wed, 22 Jun 2005 14:35:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlA4Y-00007m-FI
	for mmusic@megatron.ietf.org; Wed, 22 Jun 2005 14:35:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14896
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 14:35:34 -0400 (EDT)
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlAK1-0004Ng-Eh
	for mmusic@ietf.org; Wed, 22 Jun 2005 14:51:38 -0400
Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204])
	by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j5MIQSxm019926
	for <mmusic@ietf.org>; Wed, 22 Jun 2005 11:26:28 -0700 (PDT)
Received: from relay3.apple.com (relay3.apple.com) by mailgate2.apple.com
	(Content Technologies SMTPRS 4.3.17) with ESMTP id
	<T71b035505a118064cc894@mailgate2.apple.com>; 
	Wed, 22 Jun 2005 11:26:28 -0700
Received: from [17.202.35.52] (singda.apple.com [17.202.35.52])
	by relay3.apple.com (8.12.11/8.12.11) with ESMTP id j5MIQQXv026658;
	Wed, 22 Jun 2005 11:26:27 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p06230514bedf5c6c3d29@[17.202.35.52]>
In-Reply-To: <1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
Date: Wed, 22 Jun 2005 11:24:38 -0700
To: Colin Perkins <csp@csperkins.org>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
From: Dave Singer <singer@apple.com>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

At 16:01  +0100 22/06/05, Colin Perkins wrote:
>On 22 Jun 2005, at 14:04, Henning Schulzrinne wrote:
>>Would it ever make sense to just convey a file type in SDP? I can't 
>>see how application/pdf or application/powerpoint or text/xml would 
>>be particularly useful. Thus, I'm not sure why one would ever need 
>>to indicate the namespace.
>
>Because otherwise we're restricted to using the RTP payload format 
>namespace with SDP, and can't use non-RTP formats (or vice versa)?
>
>>I agree that unplanned name collisions would be confusing, but the 
>>registries could be set up so that the two are coupled, i.e., a new 
>>one in either registry can't duplicate the name unless they are 
>>indeed the same bits on the wire.
>
>So why not use the same namespace, and define restrictions on use? 
>(i.e. the way  the registry has been managed for the last 7 years or 
>so...)
>
>What is the benefit of a change?
>
>Colin

For me, if the IANA is managing two spaces, it can be clear which one 
is which and we can avoid arguments like -- "audio/whatever" may make 
sense as a file format (i.e. MIME) but none as an RTP format, or 
vice-versa.

Logically we then have
mime/audio/midi
rtp/audio/amr

(where mime/ and rtp/ are separate IANA entry points).

and so on.  There's no reason why one shouldn't request that 
something be inserted into both mime/ and rtp/, of course.  But then 
it's explicit and an intent, and both communities get to review.

It makes no sense to me that we are currently populating the MIME 
tree with types that can't be used in a MIME context (e.g. email).

This changes no bits on the wire;  we initially populate rtp/ from 
the mime/ tree, using those types that make sense.  We amend the 
appropriate spec. to say that RTPMAP lines reference the rtp/ tree.
-- 
David Singer
Apple Computer/QuickTime

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


From mmusic-bounces@ietf.org  Thu Jun 23 08:06:08 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02162
	for <mmusic-archive@ietf.org>; Thu, 23 Jun 2005 08:06:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlQrU-0008Gn-4n
	for mmusic-archive@ietf.org; Thu, 23 Jun 2005 08:31:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQPD-0002cs-5L; Thu, 23 Jun 2005 08:02:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlQPC-0002cn-Hn
	for mmusic@megatron.ietf.org; Thu, 23 Jun 2005 08:02:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01348
	for <mmusic@ietf.org>; Thu, 23 Jun 2005 08:02:01 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlQnV-0007yj-Ny
	for mmusic@ietf.org; Thu, 23 Jun 2005 08:27:11 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (Motorola/Motgate7) with ESMTP id j5NCAdW9006707
	for <mmusic@ietf.org>; Thu, 23 Jun 2005 05:10:39 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j5NC76ac025989
	for <mmusic@ietf.org>; Thu, 23 Jun 2005 07:07:07 -0500 (CDT)
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <NJKJFJHZ>; Thu, 23 Jun 2005 17:31:51 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F303BF949F@zin24exm01.ap.mot.com>
From: M Subramanya-A5007C <A5007C@motorola.com>
To: IETF MMUSIC working group <mmusic@ietf.org>
Date: Thu, 23 Jun 2005 17:31:46 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: H Viditha-A20502 <viditha@motorola.com>
Subject: [MMUSIC] Media Attribute lines in answer for unsupported media lines
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034


Hi,
	we have a scenario like...


	<------ offer with 2 media lines
	
	m=audio 50001 RTP/AVP 8 
	a=rtpmap:8 SIPUA_G711U/8000
	m=audio 50001 RTP/AVP 100
	a=rtpmap:100 SIPUA_DTMF/8000 


	--------> ? Now in the answer is it mandatory to send out media
attribute lines(a lines) for unsupported media line 	like shown below 

	m=audio 0 RTP/AVP 8 		is this valid...?
	m=audio 50001 RTP/AVP 100
	a=rtpmap:100 SIPUA_DTMF/8000 

-Subbu


	

	

	
	

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


From mmusic-bounces@ietf.org  Thu Jun 23 11:25:38 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23875
	for <mmusic-archive@ietf.org>; Thu, 23 Jun 2005 11:25:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlTyb-0001PB-Nt
	for mmusic-archive@ietf.org; Thu, 23 Jun 2005 11:50:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlTYl-0000u4-3p; Thu, 23 Jun 2005 11:24:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlTYj-0000tq-Ds
	for mmusic@megatron.ietf.org; Thu, 23 Jun 2005 11:24:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23557
	for <mmusic@ietf.org>; Thu, 23 Jun 2005 11:24:03 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlTx3-0001GR-9n
	for mmusic@ietf.org; Thu, 23 Jun 2005 11:49:15 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by sj-iport-5.cisco.com with ESMTP; 23 Jun 2005 08:23:50 -0700
X-IronPort-AV: i="3.93,224,1115017200"; 
	d="scan'208"; a="193696648:sNHT28699796"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5NFNkbp014352; 
	Thu, 23 Jun 2005 11:23:49 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 23 Jun 2005 11:23:42 -0400
Received: from [10.0.1.15] ([10.86.242.157]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Jun 2005 11:23:40 -0400
Message-ID: <42BAD3EC.7030707@cisco.com>
Date: Thu, 23 Jun 2005 11:23:24 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: M Subramanya-A5007C <A5007C@motorola.com>
Subject: Re: [MMUSIC] Media Attribute lines in answer for unsupported media
	lines
References: <772BCEF88A1DD91191F80011856715F303BF949F@zin24exm01.ap.mot.com>
In-Reply-To: <772BCEF88A1DD91191F80011856715F303BF949F@zin24exm01.ap.mot.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2005 15:23:42.0162 (UTC)
	FILETIME=[89C80B20:01C57807]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
        H Viditha-A20502 <viditha@motorola.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit

inline.

M Subramanya-A5007C wrote:

> Hi,
> 	we have a scenario like...
> 
> 
> 	<------ offer with 2 media lines
> 	
> 	m=audio 50001 RTP/AVP 8 
> 	a=rtpmap:8 SIPUA_G711U/8000
> 	m=audio 50001 RTP/AVP 100
> 	a=rtpmap:100 SIPUA_DTMF/8000 

These m-lines are strange in that they indicate the same port for two 
different media streams. We've been through many discussions on that and 
I believe the conclusion is that it is not allowed.


> 
> 
> 	--------> ? Now in the answer is it mandatory to send out media
> attribute lines(a lines) for unsupported media line 	like shown below 
> 
> 	m=audio 0 RTP/AVP 8 		is this valid...?
> 	m=audio 50001 RTP/AVP 100
> 	a=rtpmap:100 SIPUA_DTMF/8000 


note section 6 of rfc3264:

An offered stream MAY be rejected in the answer, for any reason.  If
    a stream is rejected, the offerer and answerer MUST NOT generate
    media (or RTCP packets) for that stream.  To reject an offered
    stream, the port number in the corresponding stream in the answer
    MUST be set to zero.  Any media formats listed are ignored.  At least
    one MUST be present, as specified by SDP.


so what you list in the answer is fine.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From mmusic-bounces@ietf.org  Mon Jun 27 11:32:37 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03592
	for <mmusic-archive@ietf.org>; Mon, 27 Jun 2005 11:32:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dmw0P-00080Y-2g
	for mmusic-archive@ietf.org; Mon, 27 Jun 2005 11:58:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmvb0-0002th-QZ; Mon, 27 Jun 2005 11:32:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmvaz-0002ta-Ri
	for mmusic@megatron.ietf.org; Mon, 27 Jun 2005 11:32:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03570
	for <mmusic@ietf.org>; Mon, 27 Jun 2005 11:32:23 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dmw09-000805-6v
	for mmusic@ietf.org; Mon, 27 Jun 2005 11:58:26 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id ADA70AD2; 
	Mon, 27 Jun 2005 17:32:20 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 27 Jun 2005 17:32:18 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 27 Jun 2005 17:32:18 +0200
Received: from [131.160.126.95] (rvi2-126-95.lmf.ericsson.se [131.160.126.95])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id EDD01262E;
	Mon, 27 Jun 2005 18:32:17 +0300 (EEST)
Message-ID: <42C01C00.6090602@ericsson.com>
Date: Mon, 27 Jun 2005 18:32:16 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [MMUSIC] Working group last call:
	draft-ietf-mmusic-sdp-bfcp-01.txt - comment
References: <144ED8561CE90C41A3E5908EDECE315C01C5823E@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C01C5823E@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2005 15:32:18.0423 (UTC)
	FILETIME=[67263870:01C57B2D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: Colin Perkins <csp@csperkins.org>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit

Hi Roni,

thanks for the comments on the draft. Answers inline:

> 1. Assume we have a point to point call between two endpoints, EPA and
> EPB. EPA offers a BFCP m line with confide and userid attributes
> suggesting to become the BFCP server for a specific media. Now EPB wants
> to be the floor control server for that media and to reject the offer.
> Does it reject the m line with port 0 and offers a new BFCP m line. Is
> there some way to break such tie if both sides want to be the BFCP
> server.

We need to decide the granularity of this negotiation. I would say that 
we do not want to have a finer granularity than the BFCP stream level. 
That is, we do not want to negotiate for every floor which endpoint acts 
as the floor control server.

What about an attribute that allows an endpoint to state, for a given 
BFCP stream, whether:

1) I want to act only as a floor control server
2) I want to act only as a floor control client
3) I could act as a server or a client, you decide
4) I want to act as a floor control server, and maybe as a client as 
well if you decide so

The syntax could be something like:

a=floor-control: only-server
a=floor-control: only-client
a=floor-control: any
a=floor-control: both

Would this meet the requirements of your application?

> 
> 2. In the above case does EPB need to keep the floor-id defined in the
> offer from EPA so that the media line will have the same labels.
> 

Floor IDs are local to the endpoint. Therefore, they need not be the 
same in the offer and in the answer.


> 3. Now suppose that EPB is the current floor server. And EPA wants to
> become the floor control server. The questions are as in 1 and 2. An
> example for such a case is if EPA is also an MCU and another party, EPC,
> called EPA and now it's a three way where EPA is the MCU and EPB and EPC
> are connected to it. It is logical in this case to have the floor
> control server on EPA.

With the attribute above this is cover. EPA would issue a new offer with 
the new attribute set to "only-server".

Thanks,

Gonzalo

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


From mmusic-bounces@ietf.org  Wed Jun 29 16:06:35 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09943
	for <mmusic-archive@ietf.org>; Wed, 29 Jun 2005 16:06:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DnjF4-0001F6-5c
	for mmusic-archive@ietf.org; Wed, 29 Jun 2005 16:33:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dnia5-0002II-Qt; Wed, 29 Jun 2005 15:50:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DniZU-0001wU-CI; Wed, 29 Jun 2005 15:50:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03664;
	Wed, 29 Jun 2005 15:50:06 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dniz3-0006fV-Nz; Wed, 29 Jun 2005 16:16:34 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1DniZO-0000gz-LC; Wed, 29 Jun 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1DniZO-0000gz-LC@newodin.ietf.org>
Date: Wed, 29 Jun 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-offer-answer-examples-06.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
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--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		: Session Description Protocol Offer/Answer Examples
	Author(s)	: A. Johnston, R. Sparks
	Filename	: draft-ietf-mmusic-offer-answer-examples-06.txt
	Pages		: 25
	Date		: 2005-6-29
	
This document gives examples of Session Description Protocol (SDP)
   offer/answer exchanges.  Examples include codec negotiation and
   selection, hold and resume, and addition and deletion of media
   streams.  The examples show multiple media types, bidirectional,
   unidirectional, inactive streams and dynamic payload types.  Common
   Third Party Call Control (3pcc) examples are also given.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-offer-answer-examples-06.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-offer-answer-examples-06.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-offer-answer-examples-06.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: <2005-6-29145207.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-offer-answer-examples-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mmusic-offer-answer-examples-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-6-29145207.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mmusic-bounces@ietf.org  Thu Jun 30 11:18:54 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22867
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 11:18:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do1EM-0005F7-Fd
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 11:45:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do0lD-0005zX-KV; Thu, 30 Jun 2005 11:15:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do0lC-0005zN-8X
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 11:15:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22467
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 11:15:23 -0400 (EDT)
Received: from mail25.messagelabs.com ([193.109.254.115])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Do1Ax-000393-06
	for mmusic@ietf.org; Thu, 30 Jun 2005 11:42:04 -0400
X-VirusChecked: Checked
X-Env-Sender: Cristovao.DaSilva@three.co.uk
X-Msg-Ref: server-13.tower-25.messagelabs.com!1120144513!27171209!1
X-StarScan-Version: 5.4.15; banners=-,-,-
X-Originating-IP: [195.10.3.199]
Received: (qmail 10979 invoked from network); 30 Jun 2005 15:15:13 -0000
Received: from rsvd-hutchinson-3g-uk-ltd-199.3.10.195.in-addr.arpa (HELO
	h3gshmsw2.hutchison3g.com) (195.10.3.199)
	by server-13.tower-25.messagelabs.com with SMTP;
	30 Jun 2005 15:15:13 -0000
Received: from andromeda.corpuk.net (ANDROMEDA) by h3gshmsw2.hutchison3g.com 
	(Content Technologies SMTPRS 4.3.10) with ESMTP id 
	<T71da76acb80af80e8d65c@h3gshmsw2.hutchison3g.com> for
	<mmusic@ietf.org>; Thu, 30 Jun 2005 16:21:55 +0100
Received: by andromeda.corpuk.net with Internet Mail Service (5.5.2653.19) id 
	<M7Z3NM4N>; Thu, 30 Jun 2005 16:15:13 +0100
Message-ID: <346CEBBC97A0E74E9862A8B8E4DB03C91180A6@W104CS060V01.corpuk.net>
From: Cristovao DaSilva <Cristovao.DaSilva@three.co.uk>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Date: Thu, 30 Jun 2005 16:15:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [MMUSIC] Use of TIAS as alt-group-subtype in 3GPP PSS R6 media
 alternative s framework
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002



In Release 6 3GPP PSS  (TS 26.234) the use of the transport independent bw
modifier (TIAS) (RFC 3890) is recommended instead of AS.

However R6 PSS also introduces the media alternative framework by which the
session level grouping attribute, 'alt-group' is used to inform the PSS
client of which possible alternative media combinations are available for
the same content.

When AS is used as the alt-group-subtype (alt-group-type=BW obviously) then
the grouping value i.e. session level AS bandwidth for each combination is
enough to compute the UMTS/3G bandwidth required to carry each combination

However if TIAS is used then the grouping value, i.e the session level TIAS
bandwidth for each combination is not enough because the UMTS bandwidth also
depends on the session level maxprate (max packet rate over all media
components that compose the session) for which no alternative values can be
provided.

Is this interpretation correct or am I missing something?


Cris





________________________________________________________________________

This e-mail message (including any attachment) is intended only for the personal 
use of the recipient(s) named above. This message is confidential and may be 
legally privileged.  If you are not an intended recipient, you may not review, copy or 
distribute this message. If you have received this communication in error, please notify 
us immediately by e-mail and delete the original message.

Any views or opinions expressed in this message are those of the author only. 
Furthermore, this message (including any attachment) does not create any legally 
binding rights or obligations whatsoever, which may only be created by the exchange 
of hard copy documents signed by a duly authorised representative of Hutchison 
3G UK Limited.
________________________________________________________________________


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


From mmusic-bounces@ietf.org  Thu Jun 30 11:55:41 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26973
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 11:55:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do1ny-000628-Rl
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 12:22:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do1O1-0005b6-GN; Thu, 30 Jun 2005 11:55:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do1Ny-0005an-D9
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 11:55:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26946
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 11:55:27 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do1nk-00061W-1m
	for mmusic@ietf.org; Thu, 30 Jun 2005 12:22:09 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:50485)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Do1Nm-0007yj-V6; Thu, 30 Jun 2005 16:55:18 +0100
In-Reply-To: <42B9963C.7000305@cs.columbia.edu>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
	<42B9963C.7000305@cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BFF494E9-B598-46A4-8B8D-C86FC6A0178C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Date: Thu, 30 Jun 2005 16:55:14 +0100
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit

Henning,

[back from vacation, hence the slow response]

On 22 Jun 2005, at 17:47, Henning Schulzrinne wrote:
>> Because otherwise we're restricted to using the RTP payload  
>> format  namespace with SDP, and can't use non-RTP formats (or vice  
>> versa)?
>
> Let's assume for a moment that we're only talking about identifying  
> RTP payload types for now, not using SDP to convey some other media  
> exchange (e.g., support of media types over MSRP).

Don't forget that SDP can be used to signal other protocols than RTP.

> In that case, there are several sub-cases, assuming a split  
> registry, if somebody wants to stream some data type X over RTP:
>
> (1) Registrations exist in both --> no issue
>
> (2) Registration exist in the "email" registry, but not in the RTP  
> registry
>
>   (2a) The very same bit pattern could be used for both and there  
> are no special SDP parameters needed.
>
>   (2b) A payload format is needed or RTP-specific parameters are  
> needed.
>
>
> We want to avoid case (2), in particular (2a). This case arises if  
> somebody registers a new media type for "email", but the MMUSIC/AVT  
> community doesn't find out until there are problems in  
> implementations. Making sure that such registrations are passed on  
> to an appropriate expert review in AVT/MMUSIC would allow us to  
> catch this case and then decide whether an RTP version makes sense  
> or not. My perception is that this is not currently happening,  
> i.e., somebody could register an "email" type for audio/* and AVT  
> would never find out (except by accident).

All new media types are supposed to be reviewed on the <ietf- 
types@iana.org> mailing list. Both AVT chairs are on that list, so we  
would find out that way. This is one of the good things of the  
combined registry: it's very easy to do cross area review, since  
there's a single list.

>>> I agree that unplanned name collisions would be confusing, but  
>>> the  registries could be set up so that the two are coupled,  
>>> i.e., a new  one in either registry can't duplicate the name  
>>> unless they are  indeed the same bits on the wire.
>>>
>> So why not use the same namespace, and define restrictions on  
>> use?  (i.e. the way  the registry has been managed for the last 7  
>> years or  so...)
>> What is the benefit of a change?
>
> I see no major benefit to change the current setup, but I don't see  
> that this would be a big deal, either.

You don't consider having to change 70+ registrations, dozens of  
RFCs, books, articles, and code to be a big deal? Likely to cause  
confusion?

> I'd be curious as to whether there was a specific issue or incident  
> that caused the movement to change the status quo.

The attempt to register RTP payload formats under the "text" top- 
level media type worried some people. In particular, there was  
concern that text mode email clients might accidentally receive an  
RTP stream which they wouldn't be able to process.

Colin

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


From mmusic-bounces@ietf.org  Thu Jun 30 12:10:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28438
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 12:10:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do21y-0006RS-9t
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 12:36:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do1Wu-00071S-V2; Thu, 30 Jun 2005 12:04:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do1Wu-00071K-6U
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 12:04:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27975
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 12:04:41 -0400 (EDT)
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do1wf-0006H0-Au
	for mmusic@ietf.org; Thu, 30 Jun 2005 12:31:23 -0400
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j5UG4XmD014414
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 30 Jun 2005 12:04:34 -0400 (EDT)
Message-ID: <42C4180C.1050409@cs.columbia.edu>
Date: Thu, 30 Jun 2005 12:04:28 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
	<42B9963C.7000305@cs.columbia.edu>
	<BFF494E9-B598-46A4-8B8D-C86FC6A0178C@csperkins.org>
In-Reply-To: <BFF494E9-B598-46A4-8B8D-C86FC6A0178C@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __PORN_PHRASE_15_0 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

> You don't consider having to change 70+ registrations, dozens of  RFCs, 
> books, articles, and code to be a big deal? Likely to cause  confusion?

I don't know the intent here, but I was assuming that none of the 
over-the-wire bits would change and that the old audio/* and video/* 
registrations would simply be copied wholesale to the new list. Thus, 
unless the RFC or book talks in detail about registration procedures for 
new media types, I don't see how this changes the world all that much, 
except that IANA needs to do some editing.

Again, I don't see the need to create work for anybody ("ain't broke"), 
but I'm not sure if the discussion is helped by exaggerating the work 
involved.

> 
>> I'd be curious as to whether there was a specific issue or incident  
>> that caused the movement to change the status quo.
> 
> 
> The attempt to register RTP payload formats under the "text" top- level 
> media type worried some people. In particular, there was  concern that 
> text mode email clients might accidentally receive an  RTP stream which 
> they wouldn't be able to process.

Is this a valid concern? Are there other good ways to address this concern?

(My vague recollection is that a system should be able to usefully 
render any text/* stream, so this sounds like a vaguely plausible concern.)



> 
> Colin

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


From mmusic-bounces@ietf.org  Thu Jun 30 12:12:18 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28694
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 12:12:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do243-0006Vf-72
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 12:39:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do1Vl-0006gk-Jg; Thu, 30 Jun 2005 12:03:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do1Vj-0006gU-NW
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 12:03:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27855
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 12:03:29 -0400 (EDT)
Received: from mxs1.siemens.at ([194.138.12.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do1vP-0006EJ-99
	for mmusic@ietf.org; Thu, 30 Jun 2005 12:30:11 -0400
Received: from vies1kbx.sie.siemens.at ([158.226.129.82])
	by mxs1.siemens.at  with ESMTP id j5UG3EYS010248
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 18:03:14 +0200
Received: from vies141a.sie.siemens.at ([158.226.129.98])
	by vies1kbx.sie.siemens.at (8.12.11/8.12.1) with ESMTP id
	j5UG3DZe005023 for <mmusic@ietf.org>; Thu, 30 Jun 2005 18:03:14 +0200
Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2655.55)
	id <M55ZBN9K>; Thu, 30 Jun 2005 18:05:07 +0200
Message-ID: <B517DF063D33D611A2F20800060DA3268EB33E@vieg127a.gud.siemens.at>
From: Stach Thomas <thomas.stach@siemens.com>
To: "'fandreas@cisco.com'" <fandreas@cisco.com>,
        "'dwing@cisco.com'"
	<dwing@cisco.com>
Date: Thu, 30 Jun 2005 18:00:17 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: [MMUSIC] Comment on draft-ietf-mmusic-securityprecondition-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

Fleming, Dan,
 
I think the draft in general is quite clear.
Is a WGLC planned for the near future?

Nevertheless, I propose to change the example call flows in Figure 1 and 2
to show usage of the UPDATE method for the second SDP offer/answer exchange.
It could look like this

                  A                                            B 
    
                  |                                            | 
                  |-------------(1) INVITE SDP1--------------->| 
                  |                                            | 
                  |<------(2) 183 Session Progress SDP2--------| 
                  |                                            | 
                  |----------------(3) PRACK ----------------->| 
                  |                                            | 
                  |<-----------(4) 200 OK (PRACK) -------------| 
                  |                                            | 
                  |---------------(5) UPDATE SDP3------------->| 
                  |                                            | 
                  |<----------(6) 200 OK (UDATE) SDP4 ---------| 
                  |                                            | 
                  |<-------------(7) 180 Ringing---------------| 
                  |                                            | 
                  |                                            | 
                  |                                            | 

And of course a normative reference to RFC 3262 for PRACK and RFC3311 for
the UPDATE method should be added.

Kind Regards 

Thomas 

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


From mmusic-bounces@ietf.org  Thu Jun 30 12:33:49 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00516
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 12:33:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do2Ot-00072T-G7
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 13:00:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do1xr-0003O9-NY; Thu, 30 Jun 2005 12:32:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do1xq-0003O4-9e
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 12:32:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00433
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 12:32:31 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do2Nc-00070i-Cz
	for mmusic@ietf.org; Thu, 30 Jun 2005 12:59:13 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:50548)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Do1xf-0003Sa-PV; Thu, 30 Jun 2005 17:32:23 +0100
In-Reply-To: <42C4180C.1050409@cs.columbia.edu>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
	<42B9963C.7000305@cs.columbia.edu>
	<BFF494E9-B598-46A4-8B8D-C86FC6A0178C@csperkins.org>
	<42C4180C.1050409@cs.columbia.edu>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EA0BA559-06AC-4C15-93BB-B47F7BD96CAA@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Date: Thu, 30 Jun 2005 17:32:19 +0100
To: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Dave Singer <singer@apple.com>,
        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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

On 30 Jun 2005, at 17:04, Henning Schulzrinne wrote:
>> You don't consider having to change 70+ registrations, dozens of   
>> RFCs, books, articles, and code to be a big deal? Likely to cause   
>> confusion?
>
> I don't know the intent here, but I was assuming that none of the  
> over-the-wire bits would change and that the old audio/* and video/ 
> * registrations would simply be copied wholesale to the new list.  
> Thus, unless the RFC or book talks in detail about registration  
> procedures for new media types, I don't see how this changes the  
> world all that much, except that IANA needs to do some editing.
>
> Again, I don't see the need to create work for anybody ("ain't  
> broke"), but I'm not sure if the discussion is helped by  
> exaggerating the work involved.

RTP payload types contain a MIME registration form. We'd need to  
update 22 such RFCs if the change went ahead. This could be done as a  
single new RFC (like RFC 3555), or as part of the usual update cycle.  
This is a lot of work for someone, but is clearly possible. It  
creates a lot of confusion, however, since the old references will be  
around for a long time.

>>> I'd be curious as to whether there was a specific issue or  
>>> incident  that caused the movement to change the status quo.
>>>
>> The attempt to register RTP payload formats under the "text" top-  
>> level media type worried some people. In particular, there was   
>> concern that text mode email clients might accidentally receive  
>> an  RTP stream which they wouldn't be able to process.
>
> Is this a valid concern? Are there other good ways to address this  
> concern?
>
> (My vague recollection is that a system should be able to usefully  
> render any text/* stream, so this sounds like a vaguely plausible  
> concern.)

It's a vaguely plausible concern, which I believe is addressed by the  
concept of framed media types which have restricted applicability.

Colin

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


From mmusic-bounces@ietf.org  Thu Jun 30 12:35:10 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00595
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 12:35:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do2QC-00074L-Az
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 13:01:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do1zu-0004Ck-FW; Thu, 30 Jun 2005 12:34:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do1zr-00049e-If
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 12:34:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00541
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 12:34:36 -0400 (EDT)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do2Pb-000731-UJ
	for mmusic@ietf.org; Thu, 30 Jun 2005 13:01:19 -0400
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:50549)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Do1zf-0003Vb-Gd; Thu, 30 Jun 2005 17:34:27 +0100
In-Reply-To: <p06230514bedf5c6c3d29@[17.202.35.52]>
References: <5D18C7F8-81FA-4B69-990F-2E78D1121BC6@csperkins.org>
	<p0623054ebede524a61af@[17.202.35.52]>
	<CF10C28D-75D9-4B9E-AEE4-9B945A4369BA@csperkins.org>
	<42B961DD.30807@cs.columbia.edu>
	<1F6007FF-8B72-4FA9-B295-959898E712B6@csperkins.org>
	<p06230514bedf5c6c3d29@[17.202.35.52]>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8CD21687-BDD0-473D-8DCE-83074A6E5A5F@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [AVT] Naming of RTP payload formats within SDP
Date: Thu, 30 Jun 2005 17:34:22 +0100
To: Dave Singer <singer@apple.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: IETF MMUSIC working group <mmusic@ietf.org>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

On 22 Jun 2005, at 19:24, Dave Singer wrote:
...
> For me, if the IANA is managing two spaces, it can be clear which  
> one is which and we can avoid arguments like -- "audio/whatever"  
> may make sense as a file format (i.e. MIME) but none as an RTP  
> format, or vice-versa.
>
> Logically we then have
> mime/audio/midi
> rtp/audio/amr
>
> (where mime/ and rtp/ are separate IANA entry points).
>
> and so on.  There's no reason why one shouldn't request that  
> something be inserted into both mime/ and rtp/, of course.  But  
> then it's explicit and an intent, and both communities get to review.

Both communities can review existing media type registrations:  
there's a single dedicated mailing list for the purpose; it seems to  
work quite well.

> It makes no sense to me that we are currently populating the MIME  
> tree with types that can't be used in a MIME context (e.g. email).

The decision to convert the MIME tree into a general purpose media  
types registry was made in AVT at the 40th IETF, with help from the  
applications area directors. At the time it was thought that a single  
registry was important to avoid confusion from overlapping names in  
different registries. Indeed, the use of conflicting names for the  
same data format ("audio/basic" versus "audio/pcmu") was one of the  
primary drivers for the unification.

Colin

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


From mmusic-bounces@ietf.org  Thu Jun 30 12:56:04 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02261
	for <mmusic-archive@ietf.org>; Thu, 30 Jun 2005 12:56:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Do2kR-0007ZS-14
	for mmusic-archive@ietf.org; Thu, 30 Jun 2005 13:22:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Do2Jn-00033d-0a; Thu, 30 Jun 2005 12:55:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Do2Jl-00031H-MR
	for mmusic@megatron.ietf.org; Thu, 30 Jun 2005 12:55:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02215
	for <mmusic@ietf.org>; Thu, 30 Jun 2005 12:55:10 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Do2jY-0007Yj-8k
	for mmusic@ietf.org; Thu, 30 Jun 2005 13:21:53 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 30 Jun 2005 12:55:04 -0400
X-IronPort-AV: i="3.93,246,1115006400"; 
	d="scan'208"; a="60526159:sNHT29446424"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5UGt1aU013783; 
	Thu, 30 Jun 2005 12:55:03 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 30 Jun 2005 12:54:57 -0400
Received: from [161.44.55.240] ([161.44.55.240]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 30 Jun 2005 12:54:57 -0400
Message-ID: <42C423E1.5070604@cisco.com>
Date: Thu, 30 Jun 2005 12:54:57 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stach Thomas <thomas.stach@siemens.com>
References: <B517DF063D33D611A2F20800060DA3268EB33E@vieg127a.gud.siemens.at>
In-Reply-To: <B517DF063D33D611A2F20800060DA3268EB33E@vieg127a.gud.siemens.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Jun 2005 16:54:57.0410 (UTC)
	FILETIME=[722CD620:01C57D94]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Cc: "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'dwing@cisco.com'" <dwing@cisco.com>
Subject: [MMUSIC] Re: Comment on
	draft-ietf-mmusic-securityprecondition-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit



Stach Thomas wrote:

> Fleming, Dan,
>  
> I think the draft in general is quite clear.
> Is a WGLC planned for the near future?
>
I'll defer to the WG chairs, but as far as I know, all comments and 
outstanding issues have been addressed and I believe it is ready for WGLC.


> Nevertheless, I propose to change the example call flows in Figure 1 
> and 2 to show usage of the UPDATE method for the second SDP 
> offer/answer exchange.
>
An earlier version of the document did that and it was pointed out that 
you save the UPDATE because you already have the necesssary information 
available at the time you want to send the PRACK, so it was removed. We 
could change one of the examples to include UPDATE if the WG wants to.

> It could look like this
>
>                   A                                            B
>    
>                   |                                            |
>                   |-------------(1) INVITE SDP1--------------->|
>                   |                                            |
>                   |<------(2) 183 Session Progress SDP2--------|
>                   |                                            |
>                   |----------------(3) PRACK ----------------->|
>                   |                                            |
>                   |<-----------(4) 200 OK (PRACK) -------------|
>                   |                                            |
>                   |---------------(5) UPDATE SDP3------------->|
>                   |                                            |
>                   |<----------(6) 200 OK (UDATE) SDP4 ---------|
>                   |                                            |
>                   |<-------------(7) 180 Ringing---------------|
>                   |                                            |
>                   |                                            |
>                   |                                            |
>
> And of course a normative reference to RFC 3262 for PRACK and RFC3311 
> for the UPDATE method should be added.
>
They are effectively there already because RFC 3312 makes it mandatory 
for you to support them, so I don't think we need to add them to the list.

-- Flemming

> Kind Regards
>
> Thomas
>

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


