From mailman-bounces@ietf.org  Sat Jan  1 08:13:33 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 IAA17825
	for <mmusic-web-archive@ietf.org>; Sat, 1 Jan 2005 08:13:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkjGK-0000gu-Gn
	for mmusic-web-archive@ietf.org; Sat, 01 Jan 2005 08:25:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgSE-0003hm-Gz
	for mmusic-web-archive@ietf.org; Sat, 01 Jan 2005 05:25:50 -0500
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-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.27947.1104574255.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:10:55 -0500
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-web-archive@ietf.org:

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


From mmusic-bounces@ietf.org  Mon Jan  3 11:57:55 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 LAA13272
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 11:57:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClVix-0000BV-Sj
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 12:10:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClVVe-0006Ui-9j; Mon, 03 Jan 2005 11:56:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClVUj-0006CW-Ad; Mon, 03 Jan 2005 11:55:50 -0500
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 LAA13182;
	Mon, 3 Jan 2005 11:55:46 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClVgs-00009S-6p; Mon, 03 Jan 2005 12:08:25 -0500
Received: from [10.10.108.16] ([65.119.52.228]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id j03GtajI097298
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Mon, 3 Jan 2005 10:55:37 -0600 (CST) (envelope-from ben@nostrum.com)
In-Reply-To: <41D0955B.2080704@nostrum.com>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
From: Ben Campbell <ben@nostrum.com>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Mon, 3 Jan 2005 10:55:43 -0600
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, mmusic@ietf.org,
        Simple WG <simple@ietf.org>, Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0875506610=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86


--===============0875506610==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-8--237391422;
	protocol="application/pkcs7-signature"


--Apple-Mail-8--237391422
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

I sent the following proposed compromise out before the holidays. If 
anyone commented on it, I have not seen the comments. The general idea 
is that MSRP aware endpoints would use the path attribute, but a non 
MSRP aware device could still determine the destination address and 
port from the m and c lines. thoughts?

> How about this as a potential compromise:
>
> We keep the path attribute as is, but _also_ copy the information for 
> the endpoint into the m and c lines. This would seem to me to be 
> consistent with the usage in the current ICE draft, in which ICE aware 
> endpoints use the candidate attributes to determine the address and 
> port, but the default address and port are copied into the m and c 
> line for backwards compatibility? Considering that the ICE need for 
> backwards compatibility seems much more clear than the MSRP need for 
> the same?




--Apple-Mail-8--237391422
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEjCCAssw
ggI0oAMCAQICAwwdSDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwNDEyMjA0NTUyWhcNMDUwNDEyMjA0NTUyWjBBMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg9iZW5Abm9zdHJ1bS5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDGFv8c1i8a9NXiEohMEryzypOcyz39k8PN
WxTS4F45JSYwQ0/RAZ4vaemHCyJaUc7tc5DN3o7zl2oaqQuOIrvnjk79ILGJVfRgwt+uGDIGyaSM
YmBeKXSdawFiJdk5jGtMzlgF8tzJzc4do5Mzl5YS39AR8mj8PF4zEgIlYYkKXBByHQ2jPA0qVfm/
Aj71RdYZyDAD4P7TyW9jKvZCl7KCfajar1llEQVj+kWMvt/3AE6mwAHXfkU7nL9XzLvGSnMUJvYx
hq3UDju4IacXsYFw2oLb4LQdvwP4Lbg6qdp08h59+TkHlV6WNdt3ggM9C/cGQTDCa0CVJsr+76Dm
mPorAgMBAAGjLDAqMBoGA1UdEQQTMBGBD2JlbkBub3N0cnVtLmNvbTAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBAApFAg5tsI2OhByoUglTZ+ip3M/1xfWDsCNsDB4+HtnH9fZfKkrkGp4e
JQyuvl5VhvW67qYU6wEPMD0EKoWDU3v7l1huzR7Cpkf7n21y4LLG+VxldYiA3SEkv7RBPhhVhdMl
sHwNZAYyVXFCdnvuVjfeytdAeXK6vzcaUvo9EwkHMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0B
AQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw
ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv
biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAw
MDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1
aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/
ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoT
zyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GU
MIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3
dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQi
MCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQ
g+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsA
xRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXe
JLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMMHUgwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc
BgkqhkiG9w0BCQUxDxcNMDUwMTAzMTY1NTQ0WjAjBgkqhkiG9w0BCQQxFgQU5ss49FkudmMZXARB
JAaQksR1okkweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwwdSDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMMHUgwDQYJKoZIhvcNAQEBBQAEggEAYg1InaMf42hj4GVJ
ZPn0HJ2Z00C5KZDA3RzFk5o/Ty1PyFUA8bp4gWiuxfxTTXF6/qL8XiasRoeRL7+IqsWJdLy/Kln1
mYCQKDwPX7SlP7Ia/vcBEKhYuqaIszt8mjbaI2B5kEPcNjA6jiZt+FfSTtso9pIUO7+iKZid6QrV
eKaUDH/NK0M62N+qem04SOhaTFyZ6DiL0LwMZ+t33r674BFQhPj2625EERUu/WN+Os/j5xi+BTXc
S5k2xOFo3x6wKXiAZF1ej4O2FDhj3M15syMEYaa9EKVXA6aiNRoE4Tk9nujCKYTbSFWMpX8oZwNS
2XDMK70+CnKz3Eg4tlG3NAAAAAAAAA==

--Apple-Mail-8--237391422--



--===============0875506610==
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

--===============0875506610==--




From mmusic-bounces@ietf.org  Mon Jan  3 12:27:40 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 MAA15817
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 12:27:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWBn-0000tK-OF
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 12:40:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClVpk-000713-DC; Mon, 03 Jan 2005 12:17:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClVkX-0003fB-N1; Mon, 03 Jan 2005 12:12:10 -0500
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 MAA14382;
	Mon, 3 Jan 2005 12:12:07 -0500 (EST)
Received: from voyager.coretrek.no ([212.33.142.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClVwX-0000TN-8E; Mon, 03 Jan 2005 12:24:46 -0500
Received: from localhost (localhost [127.0.0.1])
	by voyager.coretrek.no (Postfix) with ESMTP
	id DF3E6A9653; Mon,  3 Jan 2005 18:11:19 +0100 (CET)
Received: from [192.168.1.67] (unknown [82.196.203.62])
	by voyager.coretrek.no (Postfix) with ESMTP
	id A2B5DA9652; Mon,  3 Jan 2005 18:11:18 +0100 (CET)
In-Reply-To: <4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
Content-Transfer-Encoding: 7bit
From: Hisham Khartabil <hisham.khartabil@telio.no>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Mon, 3 Jan 2005 18:11:09 +0100
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS perl-11 (CoreTrek clamav patch 1)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Simple WG <simple@ietf.org>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Adam Roach <adam@nostrum.com>, mmusic@ietf.org,
        Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit

I don't see the need. The information in the c and m line will be 
ignored anyway by the receiver, so why waste CPU cycles?

Also, backwards compatible with what?

Anyway, I don't feel too strongly about this. If it makes the SDP 
people happy, then we can add it.

Regards,
Hisham

On Jan 3, 2005, at 5:55 PM, Ben Campbell wrote:

> I sent the following proposed compromise out before the holidays. If 
> anyone commented on it, I have not seen the comments. The general idea 
> is that MSRP aware endpoints would use the path attribute, but a non 
> MSRP aware device could still determine the destination address and 
> port from the m and c lines. thoughts?
>
>> How about this as a potential compromise:
>>
>> We keep the path attribute as is, but _also_ copy the information for 
>> the endpoint into the m and c lines. This would seem to me to be 
>> consistent with the usage in the current ICE draft, in which ICE 
>> aware endpoints use the candidate attributes to determine the address 
>> and port, but the default address and port are copied into the m and 
>> c line for backwards compatibility? Considering that the ICE need for 
>> backwards compatibility seems much more clear than the MSRP need for 
>> the same?
>
>
>


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


From mmusic-bounces@ietf.org  Mon Jan  3 12:45:11 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 MAA17630
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 12:45:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWSl-0001Rd-1T
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 12:57:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClW8i-0007FO-Py; Mon, 03 Jan 2005 12:37:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClW5m-0005sD-75; Mon, 03 Jan 2005 12:34:06 -0500
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 MAA16658;
	Mon, 3 Jan 2005 12:34:03 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWHv-00017J-Jz; Mon, 03 Jan 2005 12:46:42 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 03 Jan 2005 10:44:00 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j03HXSvl012197;
	Mon, 3 Jan 2005 09:33:29 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-2-24.cisco.com [10.86.242.24])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOB13618;
	Mon, 3 Jan 2005 12:33:27 -0500 (EST)
Message-ID: <41D981E7.4020202@cisco.com>
Date: Mon, 03 Jan 2005 12:33:27 -0500
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: Ben Campbell <ben@nostrum.com>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Adam Roach <adam@nostrum.com>, mmusic@ietf.org,
        Simple WG <simple@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

Ben,

I think there is a potential problem with this solution, and in fact 
with any solution that uses the m- and c- lines for address and port:

it is possible that there could be two (or more) MSRP media streams in 
the same offer/answer. Because of the multiplexing capabilities of MSRP, 
there could be multiple streams that share the same address and port.

In the case of RTP streams, every stream must have a unique 
address/port. Technically I believe the rules about this are transport 
dependent, so that there could be separate rules for MSRP, permitting 
this. However, I am concerned that those arguing that we must use m- and 
c- for address and port will also object to duplicates, even with the 
msrp transport.

Conversely, if we are permitted to define the rules differently for 
msrp, I don't see why we can't define the rules so we don't use m- and 
c- for address and port.

	Paul

Ben Campbell wrote:
> I sent the following proposed compromise out before the holidays. If 
> anyone commented on it, I have not seen the comments. The general idea 
> is that MSRP aware endpoints would use the path attribute, but a non 
> MSRP aware device could still determine the destination address and port 
> from the m and c lines. thoughts?
> 
>> How about this as a potential compromise:
>>
>> We keep the path attribute as is, but _also_ copy the information for 
>> the endpoint into the m and c lines. This would seem to me to be 
>> consistent with the usage in the current ICE draft, in which ICE aware 
>> endpoints use the candidate attributes to determine the address and 
>> port, but the default address and port are copied into the m and c 
>> line for backwards compatibility? Considering that the ICE need for 
>> backwards compatibility seems much more clear than the MSRP need for 
>> the same?
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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 Jan  3 13:18:55 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 NAA22251
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 13:18:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWzO-0002SP-Gj
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 13:31:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClWhr-0003sj-Fr; Mon, 03 Jan 2005 13:13:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClWZE-0000my-Ri; Mon, 03 Jan 2005 13:04:32 -0500
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 NAA20839;
	Mon, 3 Jan 2005 13:04:30 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWlQ-00025i-Ie; Mon, 03 Jan 2005 13:17:09 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:62322
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1ClWYh-0001Ze-EW; Mon, 03 Jan 2005 18:03:59 +0000
In-Reply-To: <768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Mon, 3 Jan 2005 18:03:52 +0000
To: Hisham Khartabil <hisham.khartabil@telio.no>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        mmusic@ietf.org, Simple WG <simple@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: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
> I don't see the need. The information in the c and m line will be 
> ignored anyway by the receiver, so why waste CPU cycles?

Because SDP requires the "c=" and "m=" lines to indicate where the 
media is sent, and because there could be a middlebox or other device 
processing the SDP that needs that information.

> Also, backwards compatible with what?

Other devices that parse SDP, some of which may be outside your control.

Colin


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


From mmusic-bounces@ietf.org  Mon Jan  3 13:19:59 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 NAA22383
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 13:19:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClX0Q-0002UC-Jq
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 13:32:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClWiJ-0004AM-HG; Mon, 03 Jan 2005 13:13:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClWbN-0001M4-L1; Mon, 03 Jan 2005 13:06:45 -0500
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 NAA21044;
	Mon, 3 Jan 2005 13:06:42 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClWnZ-00028E-Dj; Mon, 03 Jan 2005 13:19:22 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:62350
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1ClWar-0001aM-KG; Mon, 03 Jan 2005 18:06:13 +0000
In-Reply-To: <4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <25DF6EBA-5DB2-11D9-ADD5-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Mon, 3 Jan 2005 18:06:10 +0000
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        Simple WG <simple@ietf.org>, 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 3 Jan 2005, at 16:55, Ben Campbell wrote:
> I sent the following proposed compromise out before the holidays. If 
> anyone commented on it, I have not seen the comments. The general idea 
> is that MSRP aware endpoints would use the path attribute, but a non 
> MSRP aware device could still determine the destination address and 
> port from the m and c lines. thoughts?

Not ideal, but better than ignoring the addresses in the "c=" and "m=" 
lines.

Colin


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


From mmusic-bounces@ietf.org  Mon Jan  3 13:59:59 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 NAA26901
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 13:59:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClXd7-0003hP-Ea
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 14:12:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClXLW-0003Kz-LX; Mon, 03 Jan 2005 13:54:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClXHx-0002Fd-Ia; Mon, 03 Jan 2005 13:50:45 -0500
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 NAA25585;
	Mon, 3 Jan 2005 13:50:44 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClXU9-0003N7-Bp; Mon, 03 Jan 2005 14:03:22 -0500
Received: from [10.10.108.16] ([65.119.52.228]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id j03Iocp6006905
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Mon, 3 Jan 2005 12:50:39 -0600 (CST) (envelope-from ben@nostrum.com)
In-Reply-To: <41D981E7.4020202@cisco.com>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
	<41D981E7.4020202@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <60AB4694-5DB8-11D9-A341-000D93B0AE1A@nostrum.com>
From: Ben Campbell <ben@nostrum.com>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Mon, 3 Jan 2005 12:50:45 -0600
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@tzi.uni-bremen.de>,
        Adam Roach <adam@nostrum.com>, mmusic@ietf.org,
        Simple WG <simple@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1545623523=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f


--===============1545623523==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3--230489038;
	protocol="application/pkcs7-signature"


--Apple-Mail-3--230489038
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed
Content-Transfer-Encoding: 7bit

It sounds to me that you have just described a real technical issue  
where using the m and c lines _cannot_ work in the general case unless  
we break other SDP rules anyway.

On Jan 3, 2005, at 11:33 AM, Paul Kyzivat wrote:

> Ben,
>
> I think there is a potential problem with this solution, and in fact  
> with any solution that uses the m- and c- lines for address and port:
>
> it is possible that there could be two (or more) MSRP media streams in  
> the same offer/answer. Because of the multiplexing capabilities of  
> MSRP, there could be multiple streams that share the same address and  
> port.
>
> In the case of RTP streams, every stream must have a unique  
> address/port. Technically I believe the rules about this are transport  
> dependent, so that there could be separate rules for MSRP, permitting  
> this. However, I am concerned that those arguing that we must use m-  
> and c- for address and port will also object to duplicates, even with  
> the msrp transport.
>
> Conversely, if we are permitted to define the rules differently for  
> msrp, I don't see why we can't define the rules so we don't use m- and  
> c- for address and port.
>
> 	Paul
>
> Ben Campbell wrote:
>> I sent the following proposed compromise out before the holidays. If  
>> anyone commented on it, I have not seen the comments. The general  
>> idea is that MSRP aware endpoints would use the path attribute, but a  
>> non MSRP aware device could still determine the destination address  
>> and port from the m and c lines. thoughts?
>>> How about this as a potential compromise:
>>>
>>> We keep the path attribute as is, but _also_ copy the information  
>>> for the endpoint into the m and c lines. This would seem to me to be  
>>> consistent with the usage in the current ICE draft, in which ICE  
>>> aware endpoints use the candidate attributes to determine the  
>>> address and port, but the default address and port are copied into  
>>> the m and c line for backwards compatibility? Considering that the  
>>> ICE need for backwards compatibility seems much more clear than the  
>>> MSRP need for the same?
>> ---------------------------------------------------------------------- 
>> --
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic

--Apple-Mail-3--230489038
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEjCCAssw
ggI0oAMCAQICAwwdSDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwNDEyMjA0NTUyWhcNMDUwNDEyMjA0NTUyWjBBMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg9iZW5Abm9zdHJ1bS5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDGFv8c1i8a9NXiEohMEryzypOcyz39k8PN
WxTS4F45JSYwQ0/RAZ4vaemHCyJaUc7tc5DN3o7zl2oaqQuOIrvnjk79ILGJVfRgwt+uGDIGyaSM
YmBeKXSdawFiJdk5jGtMzlgF8tzJzc4do5Mzl5YS39AR8mj8PF4zEgIlYYkKXBByHQ2jPA0qVfm/
Aj71RdYZyDAD4P7TyW9jKvZCl7KCfajar1llEQVj+kWMvt/3AE6mwAHXfkU7nL9XzLvGSnMUJvYx
hq3UDju4IacXsYFw2oLb4LQdvwP4Lbg6qdp08h59+TkHlV6WNdt3ggM9C/cGQTDCa0CVJsr+76Dm
mPorAgMBAAGjLDAqMBoGA1UdEQQTMBGBD2JlbkBub3N0cnVtLmNvbTAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBAApFAg5tsI2OhByoUglTZ+ip3M/1xfWDsCNsDB4+HtnH9fZfKkrkGp4e
JQyuvl5VhvW67qYU6wEPMD0EKoWDU3v7l1huzR7Cpkf7n21y4LLG+VxldYiA3SEkv7RBPhhVhdMl
sHwNZAYyVXFCdnvuVjfeytdAeXK6vzcaUvo9EwkHMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0B
AQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw
ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv
biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAw
MDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1
aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/
ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoT
zyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GU
MIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3
dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQi
MCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQ
g+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsA
xRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXe
JLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMMHUgwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc
BgkqhkiG9w0BCQUxDxcNMDUwMTAzMTg1MDQ2WjAjBgkqhkiG9w0BCQQxFgQUFWWiV6SSFKYhkgWe
P3I5NrhHxBgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwwdSDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMMHUgwDQYJKoZIhvcNAQEBBQAEggEAApXDrVq0ASterhK6
BSD57OYU1o+NqZQSi93JK2amJQ1em54wC4XCR/kr68yzvG1Oq0b6a7oadw8AtCEJywG/x9YW1bON
iwkXee3QAbM6qIPUMdJaRkIU9xgTjiTx9mzo/e7EBrsYS3Rvxs9oYFdeh0sRy5a4aIv5E7TvU9gE
zNWSJ5ueEVVF+yzn5sSmXERbLOeU5976GW6yOk6jJ4/DjPe2CrbFWe2KtANCPrig/XEAuzamGcKi
/wfzWK5lhhhpTAt/wzJO60t29lvWoF0E3NliUC5YZIljrARPkKV3R4VPaCiJzobmhIheodAa4Ftq
2xbmQUEcqii492Ol7XQSpQAAAAAAAA==

--Apple-Mail-3--230489038--



--===============1545623523==
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

--===============1545623523==--




From mmusic-bounces@ietf.org  Mon Jan  3 23:17:26 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 XAA22582
	for <mmusic-web-archive@ietf.org>; Mon, 3 Jan 2005 23:17:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClgKh-0003AZ-EW
	for mmusic-web-archive@ietf.org; Mon, 03 Jan 2005 23:30:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clfz6-0002H3-EK; Mon, 03 Jan 2005 23:07:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClfyY-0001rF-J0; Mon, 03 Jan 2005 23:07:19 -0500
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 XAA22108;
	Mon, 3 Jan 2005 23:07:16 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClgAn-0002zs-L9; Mon, 03 Jan 2005 23:20:00 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 03 Jan 2005 21:17:18 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0446cvl002406;
	Mon, 3 Jan 2005 20:06:38 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-2-24.cisco.com [10.86.242.24])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOB28551;
	Mon, 3 Jan 2005 23:06:38 -0500 (EST)
Message-ID: <41DA164E.40603@cisco.com>
Date: Mon, 03 Jan 2005 23:06:38 -0500
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: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        mmusic@ietf.org, Simple WG <simple@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: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit



Colin Perkins wrote:
> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
> 
>> I don't see the need. The information in the c and m line will be 
>> ignored anyway by the receiver, so why waste CPU cycles?
> 
> Because SDP requires the "c=" and "m=" lines to indicate where the media 
> is sent, and because there could be a middlebox or other device 
> processing the SDP that needs that information.

For a middlebox to work with this, it must understand the *semantics*, 
not just the syntax. Even if we were to use the m- and c- lines as 
requested, a middlebox without specific knowledge of msrp will not know 
what to do: is the tcp, udp, rtp, or what?

And in the case of msrp, the msrp relay *is* the middlebox, and the sdp 
syntax has been designed specifically to accomodate it.

>> Also, backwards compatible with what?
> 
> Other devices that parse SDP, some of which may be outside your control.

I still don't buy this. There is no issue of *parsing* the SDP. Nothing 
we have done is inconsistent with SDP parsing.

I think the issue you are alluding to must be more to "implementing" SDP 
to a greater extent than just parsing it. But in all cases the semantics 
are a function of the particular transport. Its not clear to me that are 
any standard semantics.

Colin - I would like to hear exactly what you think can be implemented 
generically across all transports, including unknown ones.

	Paul



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


From mmusic-bounces@ietf.org  Tue Jan  4 12:42:49 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 MAA01143
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 12:42:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClsuD-0002N6-QZ
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 12:55:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClseP-0004Np-8k; Tue, 04 Jan 2005 12:39:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClscX-0003dZ-AT; Tue, 04 Jan 2005 12:37:25 -0500
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 MAA00552;
	Tue, 4 Jan 2005 12:37:22 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Clsov-0002EG-4B; Tue, 04 Jan 2005 12:50:14 -0500
Received: from tzi.uni-bremen.de (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	j04HajKu018198; Tue, 4 Jan 2005 18:36:53 +0100 (MET)
Message-ID: <41DAD42A.4060508@tzi.uni-bremen.de>
Date: Tue, 04 Jan 2005 18:36:42 +0100
From: Joerg Ott <jo@tzi.uni-bremen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com>
In-Reply-To: <41DA164E.40603@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
Cc: Simple WG <simple@ietf.org>, Adam Roach <adam@nostrum.com>,
        Colin Perkins <csp@csperkins.org>, 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: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit

The essence of what I hear (or read) Paul saying is:

 From SDP, we need the "m=<media-type>" part to delimit streams
and to identify something as MSRP.  There may be a few common
attributes and further fields but do not count on them because
the rest is up to the interpretation per media protocol.

This viewpoint doesn't really convince me at this point.
We have numerous rules and extensions for SDP (preconditions,
labels, etc.), and I haven't yet gone through the exercise
to find out whether such a "usage" of SDP would actually
work with all of these.  (This does not mean that I would
like this approach even if we can make this work.)

But leaving alone the "ugliness" issue for the moment, I
would like to discuss two issues so that we can take a
meaningful decision and move on:


1.  Need for Relays

MSRP motivates relays primarily by NAT/firewall traversal.
But, of course, it would be much nicer if two endpoints
could talk to each other directly (rather than via an
intermediary).  Then, we would not really need multiplexing
(unless maybe two gateways talk -- which is conceptually
different) and a single m=/c= line would be sufficient
(and might simply reuse comedia and be done with it).

Hence, what we are arguing over is a (potentially endlessly
lasting) interim solution until we get the connectivity right.
If there was a way to do something like ICE here as well,
we would be done with it.

So, how much hassle are we willing to take up to make the
interim solution work.  This should add to the basic version
instead of having the basic version designed as a special
case of the interim.

2.  Generality

Assuming that there is a need for a stepwise connection via
some relay (and that this will never go away), I suspect that
MSRP will not be only application protocol that is going to
need it.  T.38 via TCP may be another example and so may a
shared PowerPoint presetation or VNC application.

Then, I would like to have a general solution developed that
is _not_ specific to MSRP and is documented as such.  We would
need to design something like draft-*-comedia-muxed-via-relays
rather than having one specific solution now and coming up
with another one every week.

This appears to call for some explicitly spelled out requirements
rather than a detailed discussion about a partial technical
solution.

Joerg

Paul Kyzivat wrote:

> 
> 
> Colin Perkins wrote:
> 
>> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
>>
>>> I don't see the need. The information in the c and m line will be 
>>> ignored anyway by the receiver, so why waste CPU cycles?
>>
>>
>> Because SDP requires the "c=" and "m=" lines to indicate where the 
>> media is sent, and because there could be a middlebox or other device 
>> processing the SDP that needs that information.
> 
> 
> For a middlebox to work with this, it must understand the *semantics*, 
> not just the syntax. Even if we were to use the m- and c- lines as 
> requested, a middlebox without specific knowledge of msrp will not know 
> what to do: is the tcp, udp, rtp, or what?
> 
> And in the case of msrp, the msrp relay *is* the middlebox, and the sdp 
> syntax has been designed specifically to accomodate it.
> 
>>> Also, backwards compatible with what?
>>
>>
>> Other devices that parse SDP, some of which may be outside your control.
> 
> 
> I still don't buy this. There is no issue of *parsing* the SDP. Nothing 
> we have done is inconsistent with SDP parsing.
> 
> I think the issue you are alluding to must be more to "implementing" SDP 
> to a greater extent than just parsing it. But in all cases the semantics 
> are a function of the particular transport. Its not clear to me that are 
> any standard semantics.
> 
> Colin - I would like to hear exactly what you think can be implemented 
> generically across all transports, including unknown ones.
> 
>     Paul
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 



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


From mmusic-bounces@ietf.org  Tue Jan  4 14:08: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 OAA08909
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 14:08:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CluEl-0004hT-57
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 14:20:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CltvF-0005Ps-VY; Tue, 04 Jan 2005 14:00:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cltmx-000127-DA; Tue, 04 Jan 2005 13:52:15 -0500
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 NAA07376;
	Tue, 4 Jan 2005 13:52:14 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CltzM-0004DT-UT; Tue, 04 Jan 2005 14:05:05 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 04 Jan 2005 12:02:24 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j04Ipdvl003760;
	Tue, 4 Jan 2005 10:51:40 -0800 (PST)
Received: from cisco.com ([161.44.79.149]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AOB71474; Tue, 4 Jan 2005 13:51:38 -0500 (EST)
Message-ID: <41DAE5BA.6080100@cisco.com>
Date: Tue, 04 Jan 2005 13:51:38 -0500
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: Joerg Ott <jo@tzi.uni-bremen.de>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com> <41DAD42A.4060508@tzi.uni-bremen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Content-Transfer-Encoding: 7bit
Cc: Simple WG <simple@ietf.org>, Adam Roach <adam@nostrum.com>,
        Colin Perkins <csp@csperkins.org>, 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: a3f7094ccc62748c06b21fcf44c073ee
Content-Transfer-Encoding: 7bit



Joerg Ott wrote:
> The essence of what I hear (or read) Paul saying is:
> 
>  From SDP, we need the "m=<media-type>" part to delimit streams
> and to identify something as MSRP.  There may be a few common
> attributes and further fields but do not count on them because
> the rest is up to the interpretation per media protocol.

Its not the m=media-type part (m=application) that is significant here. 
It is the transport protocol in the m-line that is most significant. 
(m=application 9 msrp *).

And it really isn't just about msrp, although that is clearly what is 
motivating the discussion. SDP *claims* to be flexible to different 
transport protocols, and makes a considerable part of the semantics 
conditional on that. But in large part it seems like lip service, 
because the document is heavily biased towards RTP.

Only in the context of the transport protocol is it possible to know 
what to do with the address and port. A middlebox looking at SDP cannot 
do anything useful to influence the communication in any way without 
understanding the protocol identifier and the semantics attached to it. 
For instance, no matter what else we do, a middlebox that doesn't 
understand "msrp" as a transport protocol identifier will not be able to 
open a pinhole thru a firewall - it won't know whether it is looking at 
a TCP address/port, a UDP address/port, or something else. There in 
nothing in the protocol identifier that would permit it to guess that.

And those components that *do* understand the protocol identifier need 
to understand *all* the associated semantics, and the attributes that 
convey it. Once you assume they do, then it doesn't matter that the c= 
line or the port on the m= line is irrelevant.

> This viewpoint doesn't really convince me at this point.
> We have numerous rules and extensions for SDP (preconditions,
> labels, etc.), and I haven't yet gone through the exercise
> to find out whether such a "usage" of SDP would actually
> work with all of these.  (This does not mean that I would
> like this approach even if we can make this work.)

Have you gone thru the exercise to see if they all work for comedia?

At a superficial level I see no reason why they wouldn't. Certainly it 
should be no issue for label, and the generic mechanism for 
preconditions should also be unaffected.

The establishment of QoS itself clearly is dependent on the kind of 
transport that is in use. I think there may indeed be some problems with 
any connection oriented transport, such as defined by comedia. This is 
highly intertwined with the semantics of the transport, and only 
incidentally with the specifics of the sdp notation used to specify the 
connection establishment parameters.

> But leaving alone the "ugliness" issue for the moment, I
> would like to discuss two issues so that we can take a
> meaningful decision and move on:
> 
> 1.  Need for Relays
> 
> MSRP motivates relays primarily by NAT/firewall traversal.

This is one of the reasons. But there is a general understanding that 
enterprises may require a policy engine in the media path for IM for 
other reasons as well.

Also, unlike voice, it is common to have several concurrent IM sessions 
open. Some endpoints wish to multiplex the sessions over a single 
connection. Because competing protocols do this it is desirable to 
retain this as a possibility.

> But, of course, it would be much nicer if two endpoints
> could talk to each other directly (rather than via an
> intermediary). 

We have worked hard to retain this as the preferred path when possible 
and permitted by policy. However,

 > Then, we would not really need multiplexing
> (unless maybe two gateways talk -- which is conceptually
> different)

I don't see why this is conceptually different.
Are you suggesting we invent a different solution for this case?

 > and a single m=/c= line would be sufficient
> (and might simply reuse comedia and be done with it).

We have been down that path - its probably been two years now, when that 
was the assumed solution, until we found a multitude of reasons why it 
wouldn't work.

Remember, this is at least our 3rd (depending on how you count) attempt 
to produce a solution that meets our needs. If you didn't walk the path 
with us, then please don't discount all the work we did before arriving 
at the solution we have.

> Hence, what we are arguing over is a (potentially endlessly
> lasting) interim solution until we get the connectivity right.
> If there was a way to do something like ICE here as well,
> we would be done with it.

I think it would be easy to argue that this is better than ICE, and is 
an option specifically because we have no backward compatibility issues 
to deal with.

There are enough reasons for relays, besides NATs and FWs, that I don't 
imagine they will go away any time soon. In any case, I expect to be 
dead before NATs and FWs are gone.

> So, how much hassle are we willing to take up to make the
> interim solution work.  This should add to the basic version
> instead of having the basic version designed as a special
> case of the interim.

If you want to take up the general case, fine. But we don't have the 
time. MSRP is long overdue. If it is *ever* to be adopted we need to get 
it out *soon*.

> 2.  Generality
> 
> Assuming that there is a need for a stepwise connection via
> some relay (and that this will never go away), I suspect that
> MSRP will not be only application protocol that is going to
> need it.  T.38 via TCP may be another example and so may a
> shared PowerPoint presetation or VNC application.
>
> Then, I would like to have a general solution developed that
> is _not_ specific to MSRP and is documented as such.  We would
> need to design something like draft-*-comedia-muxed-via-relays
> rather than having one specific solution now and coming up
> with another one every week.

I don't think we know how to do that, and I doubt there is a quorum to 
work on that problem. The main issue is that to multiplex, you need to 
have addressing associated with the chunks that are being multiplexed. 
We could do that in MSRP because we defined the protocol. How would you 
do that for an unspecified transport protocol?

> This appears to call for some explicitly spelled out requirements
> rather than a detailed discussion about a partial technical
> solution.

We have a sufficient solution for our needs. It would be helpful to have 
suggestions on how to *improve* this, rather than suggestions for how we 
could delay msrp for another couple of years.

Also, I thought there was a goal to minimize work on SDP. Is it really 
worth investing in a general mechanism that likely won't be used again?

I have been looking thru sdp-new-23 carefully for specifics that relate 
to the problems being discussed. I will post another message shortly 
with the results of that. Perhaps I can propose something that will be 
considered more in keeping with the "philosophy" of sdp.

	Paul

> Joerg
> 
> Paul Kyzivat wrote:
> 
>>
>>
>> Colin Perkins wrote:
>>
>>> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
>>>
>>>> I don't see the need. The information in the c and m line will be 
>>>> ignored anyway by the receiver, so why waste CPU cycles?
>>>
>>>
>>>
>>> Because SDP requires the "c=" and "m=" lines to indicate where the 
>>> media is sent, and because there could be a middlebox or other device 
>>> processing the SDP that needs that information.
>>
>>
>>
>> For a middlebox to work with this, it must understand the *semantics*, 
>> not just the syntax. Even if we were to use the m- and c- lines as 
>> requested, a middlebox without specific knowledge of msrp will not 
>> know what to do: is the tcp, udp, rtp, or what?
>>
>> And in the case of msrp, the msrp relay *is* the middlebox, and the 
>> sdp syntax has been designed specifically to accomodate it.
>>
>>>> Also, backwards compatible with what?
>>>
>>>
>>>
>>> Other devices that parse SDP, some of which may be outside your control.
>>
>>
>>
>> I still don't buy this. There is no issue of *parsing* the SDP. 
>> Nothing we have done is inconsistent with SDP parsing.
>>
>> I think the issue you are alluding to must be more to "implementing" 
>> SDP to a greater extent than just parsing it. But in all cases the 
>> semantics are a function of the particular transport. Its not clear to 
>> me that are any standard semantics.
>>
>> Colin - I would like to hear exactly what you think can be implemented 
>> generically across all transports, including unknown ones.
>>
>>     Paul
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
> 

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


From mmusic-bounces@ietf.org  Tue Jan  4 15:38:22 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 PAA16328
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 15:38:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Clve6-0006XQ-Pt
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 15:51:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClvHo-0002qE-42; Tue, 04 Jan 2005 15:28:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clv8x-0004Ip-P1; Tue, 04 Jan 2005 15:19:03 -0500
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 PAA14967;
	Tue, 4 Jan 2005 15:19:01 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClvLK-0006C7-Sj; Tue, 04 Jan 2005 15:31:54 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 04 Jan 2005 13:29:10 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j04KIPjw000087;
	Tue, 4 Jan 2005 12:18:25 -0800 (PST)
Received: from cisco.com ([161.44.79.149]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AOB80391; Tue, 4 Jan 2005 15:18:23 -0500 (EST)
Message-ID: <41DAFA0F.9070805@cisco.com>
Date: Tue, 04 Jan 2005 15:18:23 -0500
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: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@tzi.uni-bremen.de>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org, Simple WG <simple@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: 1094b1c84fa6e846d476f39271f5074f
Content-Transfer-Encoding: 7bit

I have been looking carefully at sdp-new-23 for further enlightenment on 
this discussion. The following are interesting:

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

Section 4.1:

   "For unicast IP sessions, the following are conveyed:

    o  The remote address for media

    o  The remote transport port for media

    The semantics of this address and port depend on the media and
    transport protocol defined.  By default, this SHOULD be the remote
    address and remote port to which data is sent.  Some media types MAY
    redefine this behaviour, but this is NOT RECOMMENDED."

The above is already somewhat suspect for TCP (e.g. comedia), because 
the address and port are not those to which data is sent, but instead is 
the remote address with which a connection is (sometimes) established. 
It seems to me that the above shows a strong bias towards UDP and RTP, 
and must be taken with a large grain of salt for transports that are 
dissimilar from those.

I think there may be some question as to whether it is even proper to 
describe an MSRP session as a "unicast IP session", since it may be 
multiplexed with other MSRP sessions on a single TCP connection.

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

Section 5.7 (c=):

   "The first sub-field ("<nettype>") is the network type, which is a
    text string giving the type of network.  Initially "IN" is defined to
    have the meaning "Internet", but other values MAY be registered in
    the future (see Section 8).

    The second sub-field ("<addrtype>") is the address type.  This allows
    SDP to be used for sessions that are not IP based.  This memo only
    defines IP4 and IP6, but other values MAY be registered in the future
    (see Section 8).

    The third sub-field ("<connection-address>") is the connection
    address.  OPTIONAL sub-fields MAY be added after the connection
    address depending on the value of the <addrtype> field."

The above textual description is not entirely in line with the syntax. 
In particular, while the above says additional subfields may follow the 
connection address depending on the value of <addrtype>, the syntax 
makes no provision for this.

   "When the <addrtype> is IP4 and IP6, the connection address is defined
    as follows:

    o  If the session is multicast, the connection address will be an IP
       multicast group address.  If the session is not multicast, then
       the connection address contains the unicast IP address of the
       expected data source or data relay or data sink as determined by
       additional attribute fields.  It is not expected that unicast
       addresses will be given in a session description that is
       communicated by a multicast announcement, though this is not
       prohibited."

The above seems to assume that the data source, relay, or sink can be 
identified by the connection address (presumably in conjunction with the 
port), and that attributes simply specify whether it is a source, relay, 
or sink. The possibility doesn't seem to have been considered that there 
might be multiple sinks at the same address/port that must be identified.

There is however the possibility of defining a new net type or address 
type that would fit our needs, permitting a complete identification to 
be included in the c-line. Assuming the problem with additional 
subfields were corrected, a possible accomodation might be to 
reformulate the "path" attribute as a c-line with a new addrtype, such as:

     c=IN MSRP-PATH <msrp-url> <msrp-url> ...

where "MSRP-PATH" is a new addrtype, the first msrp-url is the 
<connection-address> (a newly defined form of <extn-addr>), and the 
remaining urls in the path are "additional subfields".

This would arguably be more in the spirit of SDP, but for compatibility 
purposes I don't find it nearly as friendly as what is currently defined.

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

Section 5.13 (a=):

   "Attribute interpretation depends on the media tool being invoked.
    Thus receivers of session descriptions should be configurable in
    their interpretation of session descriptions in general and of
    attributes in particular."

The above provides a great deal of lattitude. But there is little 
clarity about what how "media tools" should behave with things they have 
not been configured for. (There is the general requirement that a-lines 
not understood must be ignored. I don't believe there is any similar 
requirement re transport protocol identifiers in the m-line.

Rather than worrying about the particular usage of the c-line and port 
with the msrp protocol, I think it would be more worthwhile to specify 
processing when encountering a protocol that is not understood.

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

Section 5.14 (m=):

   "<port> is the transport port to which the media stream is sent.  The
       meaning of the transport port depends on the network being used as
       specified in the relevant "c=" field, and on the transport
       protocol defined in the <proto> sub-field of the media field.
       Other ports used by the media application (such as the RTCP port
       [18]) MAY be derived algorithmically from the base media port or
       MAY be specified in a separate attribute (for example "a=rtcp:" as
       defined in [21])."

So the meaning of the port depends on the transport protocol. Since we 
are defining a new transport protocol, we get to define the meaning of 
the port with that protocol.

      "The combination of ports specified in "m=" lines and IP addresses
       specified in "c=" lines MUST comply with the following rules for
       RTP-based media streams (other protocols SHOULD define similar
       rules):"

So the provided rules do not apply in our case, and we should define 
appropriate ones that do apply to our usage.

(However there are also other rules in the offer/answer protocol that 
also affect this, and that may not have been made conditional on 
transport protocol.)

      "Two media sessions with the same transport address indicate
       alternatives for the same media stream, i.e.  all profiles, media
       types, and payload types provided in any of the "m=" lines are
       valid."

The way the text is formatted (following the rules mentioned above), 
this does not appear to be scoped by the transport protocol, and so 
would seem to be intended to apply regardless of transport protocol.

If this indeed applies for new transport protocols (such as msrp), then 
it constrains how we use the connection-address and port. If we were to 
follow the suggestion to insert the IP address from the first path entry 
  in the c-line, and the insert the port into the m-line, then two msrp 
sessions with the same next hop would be treated as alternatives, which 
is not correct. This is not a problem as we currently have things 
specified, because we require unique ports be used, even though they are 
ignored.

=======================================================================

To fix the problem that the syntax doesn't support the text in allowing 
additional subfields following connection-address depending on addrtype, 
I would propose the following change to the syntax:

old:
       extn-addr =      non-ws-string

new:
       extn-addr =      non-ws-string *(SP non-ws-string)

Then, using that, I propose the following SDP extensions to support 
msrp. (It is my impression that these can be in the msrp draft rather 
than in sdp-new):

old:
       unicast-address = IP4-address / IP6-address / FQDN / extn-addr

new:
       unicast-address = IP4-address / IP6-address / FQDN
                       / msrp-path ; valid for addrtype of "msrp-path"
                       / extn-addr


        Also, define "MSRP-PATH" as a new <addrtype>.
        (Not part of syntax.)

Then the c-line replaces the path attribute. For example:

- as currently proposed:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     c=IN IP4 alice.example.com
     m=message 9 msrp *
     a=accept-types:text/plain
     a=path:msrp://a.example.com:7394/2s93i;tcp

- with info replicated in c- and m-:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     c=IN IP4 a.example.com
     m=message 7394 msrp *
     a=accept-types:text/plain
     a=path:msrp://a.example.com:7394/2s93i;tcp

- with new c- format:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     m=message 9 msrp *
     c=IN MSRP-PATH msrp://a.example.com:7394/2s93i;tcp
     a=accept-types:text/plain

Another example with relays and multiple sessions:

- as currently proposed:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     c=IN IP4 alice.example.com
     m=message 9 msrp *
     a=accept-types:text/plain
     a=path:msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://a.example.com:7394/2s93i;tcp
     m=message 10 msrp *
     a=accept-types:text/plain
     a=path:msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://b.example.com:1234/fuige;tcp

     (Note the use of different port numbers. This makes the
      media streams independent of one another even though the
      address is otherwise the same. It can be used because the
      port is ignored.)

- with info replicated in c- and m-:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     m=message 9000 msrp *
     c=IN IP4 relay.example.com
     a=accept-types:text/plain
     a=path:msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://a.example.com:7394/2s93i;tcp
     m=message 9000 msrp *
     c=IN IP4 relay.example.com
     a=accept-types:text/plain
     a=path:msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://b.example.com:1234/fuige;tcp

     (Note that this doesn't work right! We have two media
      sessions with the same transport address, but which
      are not alternatives.)

- with new c- format:
     v=0
     o=alice 2890844526 2890844527 IN IP4 alice.example.com
     s=
     m=message 9 msrp *
     c=IN MSRP-PATH msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://a.example.com:7394/2s93i;tcp
     a=accept-types:text/plain
     m=message 9 msrp *
     c=IN MSRP-PATH msrp://relay.example.com:9000/hjdhfha;tcp  \
      msrp://b.example.com:1234/fuige;tcp
     a=accept-types:text/plain

     (Note that here I am assuming we can use port 9 all the time,
      because the media sessions have different values for the
      c-line.)

Is this better than what is currently proposed in 
draft-ietf-simple-message-sessions-09? Debatable.

Does it come closer to the spirit of SDP? Also debatable.

	Paul

Paul Kyzivat wrote:
> 
> 
> Colin Perkins wrote:
> 
>> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
>>
>>> I don't see the need. The information in the c and m line will be 
>>> ignored anyway by the receiver, so why waste CPU cycles?
>>
>>
>> Because SDP requires the "c=" and "m=" lines to indicate where the 
>> media is sent, and because there could be a middlebox or other device 
>> processing the SDP that needs that information.
> 
> 
> For a middlebox to work with this, it must understand the *semantics*, 
> not just the syntax. Even if we were to use the m- and c- lines as 
> requested, a middlebox without specific knowledge of msrp will not know 
> what to do: is the tcp, udp, rtp, or what?
> 
> And in the case of msrp, the msrp relay *is* the middlebox, and the sdp 
> syntax has been designed specifically to accomodate it.
> 
>>> Also, backwards compatible with what?
>>
>>
>> Other devices that parse SDP, some of which may be outside your control.
> 
> 
> I still don't buy this. There is no issue of *parsing* the SDP. Nothing 
> we have done is inconsistent with SDP parsing.
> 
> I think the issue you are alluding to must be more to "implementing" SDP 
> to a greater extent than just parsing it. But in all cases the semantics 
> are a function of the particular transport. Its not clear to me that are 
> any standard semantics.
> 
> Colin - I would like to hear exactly what you think can be implemented 
> generically across all transports, including unknown ones.
> 
>     Paul
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

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


From mmusic-bounces@ietf.org  Tue Jan  4 21:46:35 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 VAA16101
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 21:46:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1OV-00076I-GU
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 21:59:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm15l-0002ri-N1; Tue, 04 Jan 2005 21:40:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm129-0001ck-8f; Tue, 04 Jan 2005 21:36:26 -0500
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 VAA15315;
	Tue, 4 Jan 2005 21:36:23 -0500 (EST)
Received: from mta7.srv.hcvlny.cv.net ([167.206.5.74])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1Eb-0006tq-7q; Tue, 04 Jan 2005 21:49:19 -0500
Received: from Nadia (ool-44c6903d.dyn.optonline.net [68.198.144.61])
	by mta7.srv.hcvlny.cv.net
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with SMTP id <0I9T00I14OKLPN@mta7.srv.hcvlny.cv.net>; Tue,
	04 Jan 2005 21:36:22 -0500 (EST)
Date: Tue, 04 Jan 2005 21:36:22 -0500
From: prarch <prarch@optonline.net>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
To: Paul Kyzivat <pkyzivat@cisco.com>, Colin Perkins <csp@csperkins.org>
Message-id: <056501c4f2cf$581b9050$3d90c644@Nadia>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>
	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>
	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>
	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7BIT
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        mmusic@ietf.org, Simple WG <simple@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.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7BIT

A new start up company located in New York, NY in VoIP/Telephony software 
space is looking for software architects and developers.



  1.. Network Management Software product architects
  2.. SNMP/MIB architects and developers
  3.. Voice application product architects
  4.. Voice protocol architects and developers
  5.. Application GUI architects and developers
  6.. Technical marketing and product engineering
  7.. Sales engineers




Please send your resume to prarch@optonline.net

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>
Cc: "Joerg Ott" <jo@tzi.uni-bremen.de>; "Adam Roach" <adam@nostrum.com>; 
<mmusic@ietf.org>; "Simple WG" <simple@ietf.org>
Sent: Monday, January 03, 2005 11:06 PM
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern


>
>
> Colin Perkins wrote:
>> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
>>
>>> I don't see the need. The information in the c and m line will be 
>>> ignored anyway by the receiver, so why waste CPU cycles?
>>
>> Because SDP requires the "c=" and "m=" lines to indicate where the media 
>> is sent, and because there could be a middlebox or other device 
>> processing the SDP that needs that information.
>
> For a middlebox to work with this, it must understand the *semantics*, not 
> just the syntax. Even if we were to use the m- and c- lines as requested, 
> a middlebox without specific knowledge of msrp will not know what to do: 
> is the tcp, udp, rtp, or what?
>
> And in the case of msrp, the msrp relay *is* the middlebox, and the sdp 
> syntax has been designed specifically to accomodate it.
>
>>> Also, backwards compatible with what?
>>
>> Other devices that parse SDP, some of which may be outside your control.
>
> I still don't buy this. There is no issue of *parsing* the SDP. Nothing we 
> have done is inconsistent with SDP parsing.
>
> I think the issue you are alluding to must be more to "implementing" SDP 
> to a greater extent than just parsing it. But in all cases the semantics 
> are a function of the particular transport. Its not clear to me that are 
> any standard semantics.
>
> Colin - I would like to hear exactly what you think can be implemented 
> generically across all transports, including unknown ones.
>
> Paul
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 



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


From mmusic-bounces@ietf.org  Tue Jan  4 21:53: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 VAA16667
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 21:53:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1V0-0007Hr-GP
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 22:06:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm15q-0002tl-80; Tue, 04 Jan 2005 21:40:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm132-0001wq-31; Tue, 04 Jan 2005 21:37:20 -0500
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 VAA15412;
	Tue, 4 Jan 2005 21:37:18 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1FW-0006uU-6W; Tue, 04 Jan 2005 21:50:14 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 04 Jan 2005 19:42:56 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j052W6l2028524;
	Tue, 4 Jan 2005 18:32:06 -0800 (PST)
Received: from [10.0.45.182] (sjc-vpn7-653.cisco.com [10.21.146.141])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AVF54429;
	Tue, 4 Jan 2005 18:32:06 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Tue, 04 Jan 2005 19:35:09 -0500
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
From: Cullen Jennings <fluffy@cisco.com>
To: Joerg Ott <jo@tzi.uni-bremen.de>, Paul H Kyzivat <pkyzivat@cisco.com>
Message-ID: <BE00A06D.218E4%fluffy@cisco.com>
In-Reply-To: <41DAD42A.4060508@tzi.uni-bremen.de>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Adam Roach <adam@nostrum.com>,
        "simple@ietf.org" <simple@ietf.org>, Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

On 1/4/05 9:36 AM, "Joerg Ott" <jo@tzi.uni-bremen.de> wrote:

> 1.  Need for Relays
 
I view the primary need for relays was around logging and policy control.
Things like filtering for viruses. People have allowed IM to do things like
email and expect to be able to apply similar policy and control to it.
Luckily I'm not aware of any reported virus sent over T.38 yet but there are
virus that can propagate over IM.

Systems apply policy to the signaling of all the media - things like who can
talk to who. However they don't apply policy to the semantic content of
audio or video because the state of the art does not allow for automatic
interpretation of it well enough to apply policy. However, text based media
such as IM and email people do want to apply policy to the content.
Brokerage firms filter on key words that can be sent from certain types of
users to others. Many people check for viruses.

If this is used only for NAT traversal, the exit mechanism is the same as
STUN where devices that were not behind a NAT just do not use a relay. The
behave wg is having pretty good luck forming peer to peer TCP connections
between endpoints that are both behind NATs so it's even hopeful that relays
would not always be needed even if there still were NATs.

The motivation text in the document may need some update - there were many
long threads on the need for relays and I'm not sure that the document
captured all that. Once the WG all agreed they were needed, we were pretty
worn down on documenting all the detail of how we came to that decision.



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


From mmusic-bounces@ietf.org  Tue Jan  4 21:54:44 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 VAA16802
	for <mmusic-web-archive@ietf.org>; Tue, 4 Jan 2005 21:54:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1WO-0007KY-DE
	for mmusic-web-archive@ietf.org; Tue, 04 Jan 2005 22:07:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm15s-0002uL-4D; Tue, 04 Jan 2005 21:40:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm13u-0002E4-FV; Tue, 04 Jan 2005 21:38:14 -0500
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 VAA15455;
	Tue, 4 Jan 2005 21:38:12 -0500 (EST)
Received: from mta1.srv.hcvlny.cv.net ([167.206.5.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm1GO-0006wk-Ic; Tue, 04 Jan 2005 21:51:08 -0500
Received: from Nadia (ool-44c6903d.dyn.optonline.net [68.198.144.61])
	by mta1.srv.hcvlny.cv.net
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with SMTP id <0I9T0055MOMO1Q@mta1.srv.hcvlny.cv.net>; Tue,
	04 Jan 2005 21:37:37 -0500 (EST)
Date: Tue, 04 Jan 2005 21:37:37 -0500
From: prarch <prarch@optonline.net>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
To: Paul Kyzivat <pkyzivat@cisco.com>, Colin Perkins <csp@csperkins.org>
Message-id: <058301c4f2cf$85280100$3d90c644@Nadia>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>
	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>
	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>
	<41BC325D.4010808@tzi.uni-bremen.de>
	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>
	<41D0955B.2080704@nostrum.com>
	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>
	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>
	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7BIT
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, Adam Roach <adam@nostrum.com>,
        mmusic@ietf.org, Simple WG <simple@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.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7BIT

A new start up company located in New York, NY in VoIP/Telephony software 
space is looking for software architects and developers.



  1.. Network Management Software product architects
  2.. SNMP/MIB architects and developers
  3.. Voice application product architects
  4.. Voice protocol architects and developers
  5.. Application GUI architects and developers
  6.. Technical marketing and product engineering
  7.. Sales engineers




Please send your resume to prarch@optonline.net

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Colin Perkins" <csp@csperkins.org>
Cc: "Joerg Ott" <jo@tzi.uni-bremen.de>; "Adam Roach" <adam@nostrum.com>; 
<mmusic@ietf.org>; "Simple WG" <simple@ietf.org>
Sent: Monday, January 03, 2005 11:06 PM
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern


>
>
> Colin Perkins wrote:
>> On 3 Jan 2005, at 17:11, Hisham Khartabil wrote:
>>
>>> I don't see the need. The information in the c and m line will be 
>>> ignored anyway by the receiver, so why waste CPU cycles?
>>
>> Because SDP requires the "c=" and "m=" lines to indicate where the media 
>> is sent, and because there could be a middlebox or other device 
>> processing the SDP that needs that information.
>
> For a middlebox to work with this, it must understand the *semantics*, not 
> just the syntax. Even if we were to use the m- and c- lines as requested, 
> a middlebox without specific knowledge of msrp will not know what to do: 
> is the tcp, udp, rtp, or what?
>
> And in the case of msrp, the msrp relay *is* the middlebox, and the sdp 
> syntax has been designed specifically to accomodate it.
>
>>> Also, backwards compatible with what?
>>
>> Other devices that parse SDP, some of which may be outside your control.
>
> I still don't buy this. There is no issue of *parsing* the SDP. Nothing we 
> have done is inconsistent with SDP parsing.
>
> I think the issue you are alluding to must be more to "implementing" SDP 
> to a greater extent than just parsing it. But in all cases the semantics 
> are a function of the particular transport. Its not clear to me that are 
> any standard semantics.
>
> Colin - I would like to hear exactly what you think can be implemented 
> generically across all transports, including unknown ones.
>
> Paul
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 



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


From mmusic-bounces@ietf.org  Wed Jan  5 01:18:54 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 BAA00173
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 01:18:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm4hy-00039c-Pz
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 01:31:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4U1-0005nB-Mq; Wed, 05 Jan 2005 01:17:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4Sd-0004wb-CF
	for mmusic@megatron.ietf.org; Wed, 05 Jan 2005 01:15:59 -0500
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 BAA00015
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 01:15:58 -0500 (EST)
Received: from eastmail1.ntt-east.co.jp ([202.229.5.44]
	helo=evx1.enoc.east.ntt.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cm4f4-00035b-Bf
	for mmusic@ietf.org; Wed, 05 Jan 2005 01:28:55 -0500
Received: from emix2.enoc.east.ntt.co.jp 
	by evx1.enoc.east.ntt.co.jp with ESMTP id j056FKs23416;
	Wed, 5 Jan 2005 15:15:20 +0900 (JST)
Received: from cip6.noc.east.ntt.co.jp 
	by emix2.enoc.east.ntt.co.jp with ESMTP id j056FKc24280;
	Wed, 5 Jan 2005 15:15:20 +0900 (JST)
Received: from [10.8.52.30] ([10.8.52.30])
	by cip6.noc.east.ntt.co.jp (MOS 3.4.6-GR) with ESMTP id AUI02700;
	Wed, 5 Jan 2005 15:15:19 +0900 (JST)
Date: Wed, 05 Jan 2005 15:15:20 +0900
From: Jun KOSHIKO <j.koshiko@rdc.east.ntt.co.jp>
To: mmusic@ietf.org
Message-Id: <20050105150945.8FCC.J.KOSHIKO@rdc.east.ntt.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.11.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Video phone and offer/answer model
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

Hello Folks,

Is there anything which bundle a number of m= lines of SDP?  I would
like a session to be established only when the offerer and the answerer
agree in the codec of both video and audio. Otherwise, the answerer
would reject the offer. (see the following sequence)

video phone#1                       video phone#2
 (offerer)                            (answerer)
     | (offer)                            |
     | m=audio ...                        |
     | m=video ...                        |
     |----------------------------------->|
     |                                    |
     |                           (answer) |
     |                        m=audio ... |
     |                        m=video ... |
     |<-----------------------------------|

But according to examples in RFC3264 (offer/answer model), each m= line
(video/audio/etc...) seems like being dealt with independently. So a
session would be established when they agree in the codec of ether audio,
video or etc. If the offerer and the answerer agreed in the codec of
video and they didn't agreed in that of audio, they establish a session
and there becomes a video phone service without voice.

I would like to avoid this situation. And I'm looking for the means that
enables offerers to desire the video/audio communication at a time.

Could you give me some advice?

Regards,
Jun

---------------------------------------------------------
Jun KOSHIKO
Next Generation Strategy
Research and Development Center
NTT-east Corporation

Telephone  +81 3 5359 5104
Facsimile  +81 3 5359 4768
E-mail: j.koshiko@rdc.east.ntt.co.jp
19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
---------------------------------------------------------


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


From mmusic-bounces@ietf.org  Wed Jan  5 01:39:28 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 BAA01603
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 01:39:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cm51k-0003Xi-Fm
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 01:52:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cm4mw-00036D-Cj; Wed, 05 Jan 2005 01:36:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cm4mC-0002m2-Ga
	for mmusic@megatron.ietf.org; Wed, 05 Jan 2005 01:36:12 -0500
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 BAA01335
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 01:36:11 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cm4yi-0003TA-Dj
	for mmusic@ietf.org; Wed, 05 Jan 2005 01:49:08 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j056a9h5000946
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 07:36:10 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 5 Jan 2005 07:36:09 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <YDRLANY9>; Wed, 5 Jan 2005 07:36:09 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF07B08A39@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Jun KOSHIKO'" <j.koshiko@rdc.east.ntt.co.jp>, mmusic@ietf.org
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Wed, 5 Jan 2005 07:36:08 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 05 Jan 2005 06:36:09.0706 (UTC)
	FILETIME=[D7A2CCA0:01C4F2F0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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


Hi,

>Is there anything which bundle a number of m= lines of SDP?  I would
>like a session to be established only when the offerer and 
>the answerer
>agree in the codec of both video and audio. Otherwise, the answerer
>would reject the offer. (see the following sequence)
> 
> video phone#1                       video phone#2
>  (offerer)                            (answerer)
>      | (offer)                            |
>      | m=audio ...                        |
>      | m=video ...                        |
>      |----------------------------------->|
>      |                                    |
>      |                           (answer) |
>      |                        m=audio ... |
>      |                        m=video ... |
>      |<-----------------------------------|
> 
>But according to examples in RFC3264 (offer/answer model), 
>each m= line (video/audio/etc...) seems like being dealt with independently. So a
>session would be established when they agree in the codec of ether audio,
>video or etc. If the offerer and the answerer agreed in the codec of
>video and they didn't agreed in that of audio, they establish 
>a session and there becomes a video phone service without voice.

Correct. Of course, your application can choose to reject also the video stream if no common audio codecs are found. That's an implementation issue. You don't have to set up a video only service just because you happen to have common video codecs.

>I would like to avoid this situation. And I'm looking for the means that enables offerers to desire the video/audio 
>communication at a time.

I guess you're talking about some indicator saying "please accept this call if you find common codecs for both audio and video"? I don't think SDP supports that, so you would have to handle it on the application level. The easiest way, without using any protocol extensions etc, would be that the offerer simply terminates the session setup when it receveis the answer indicating video only.

Regards,

Christer Holmberg
Ericsson Finland

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


From mmusic-bounces@ietf.org  Wed Jan  5 09:28: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 JAA07462
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 09:28:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmCLe-0005uW-EQ
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 09:41:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmC52-0001CQ-2Z; Wed, 05 Jan 2005 09:24:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmBwI-0006xq-E9
	for mmusic@megatron.ietf.org; Wed, 05 Jan 2005 09:15:06 -0500
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 JAA06263
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 09:15:03 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmC8p-0005Xu-Kc
	for mmusic@ietf.org; Wed, 05 Jan 2005 09:28:06 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 05 Jan 2005 09:14:32 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j05EETW0000976; 
	Wed, 5 Jan 2005 09:14:29 -0500 (EST)
Received: from cisco.com ([161.44.79.149]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AOC25727; Wed, 5 Jan 2005 09:14:27 -0500 (EST)
Message-ID: <41DBF643.2040301@cisco.com>
Date: Wed, 05 Jan 2005 09:14:27 -0500
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: Jun KOSHIKO <j.koshiko@rdc.east.ntt.co.jp>
Subject: Re: [MMUSIC] Video phone and offer/answer model
References: <20050105150945.8FCC.J.KOSHIKO@rdc.east.ntt.co.jp>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit



Jun KOSHIKO wrote:
> Hello Folks,
> 
> Is there anything which bundle a number of m= lines of SDP?  I would
> like a session to be established only when the offerer and the answerer
> agree in the codec of both video and audio. Otherwise, the answerer
> would reject the offer. (see the following sequence)
> 
> video phone#1                       video phone#2
>  (offerer)                            (answerer)
>      | (offer)                            |
>      | m=audio ...                        |
>      | m=video ...                        |
>      |----------------------------------->|
>      |                                    |
>      |                           (answer) |
>      |                        m=audio ... |
>      |                        m=video ... |
>      |<-----------------------------------|
> 
> But according to examples in RFC3264 (offer/answer model), each m= line
> (video/audio/etc...) seems like being dealt with independently. So a
> session would be established when they agree in the codec of ether audio,
> video or etc. If the offerer and the answerer agreed in the codec of
> video and they didn't agreed in that of audio, they establish a session
> and there becomes a video phone service without voice.
> 
> I would like to avoid this situation. And I'm looking for the means that
> enables offerers to desire the video/audio communication at a time.
> 
> Could you give me some advice?

The callee is free to apply this kind of policy now. In fact, a limited 
form of it is quite common: a voice-only endpoint that receives an 
offerthat doesn't include voice, so that the answer would contain no 
accepted media, will usually fail the call. Similarly a voice+video 
endpoint could do the same if it doesn't receive an offer containing both.

But I think your issue is that the *caller* doesn't want the call to 
succeed unless there is both voice and video. I don't know of any *good* 
way to do this currently.

This could be solved with preconditions, if both sides support them. It 
doesn't matter much what the precondition is, so long as the caller can 
prevent it from being resolved in this case. For instance, you could put 
an unresolved QoS precondition on the voice, and fail the call rather 
than resolving it if you don't get an answer containing video.

	Paul

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


From mmusic-bounces@ietf.org  Wed Jan  5 10:10:54 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 KAA11073
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 10:10:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmD0t-0006w9-OK
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 10:23:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmCjZ-0004cp-4n; Wed, 05 Jan 2005 10:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmCWO-0007kX-Gw
	for mmusic@megatron.ietf.org; Wed, 05 Jan 2005 09:52:24 -0500
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 JAA09068
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 09:52:21 -0500 (EST)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmCiv-0006QF-NG
	for mmusic@ietf.org; Wed, 05 Jan 2005 10:05:25 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j05EqIYq026262
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 15:52:18 +0100
Received: from mchh247e.mchh.siemens.de (mchh247e.mchh.siemens.de
	[139.21.200.57])
	by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id j05EqI3r002262
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 15:52:18 +0100
Received: by mchh247e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <YDW9GP21>; Wed, 5 Jan 2005 15:50:05 +0100
Message-ID: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1D3@mchh266e.mchh.siemens.de>
From: Belling Thomas <thomas.belling@siemens.com>
To: mmusic@ietf.org
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Wed, 5 Jan 2005 15:52:17 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
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: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable

Hi folks,

> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Wednesday, January 05, 2005 3:14 PM
> To: Jun KOSHIKO
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Video phone and offer/answer model
>=20

...

>=20
> But I think your issue is that the *caller* doesn't want the call to=20
> succeed unless there is both voice and video. I don't know of=20
> any *good*=20
> way to do this currently.
>=20


A clean way to resolve that would probably bee a new type of grouping =
within the grouping framework. As a minimum, the grouping would express =
that all media for the grouped m-lines need to be established together, =
or none of them.
As the media belong together in the sense that they need to be handled =
by a combined application, the more far-reaching idea would be to =
indicate the application in the new grouping type. This obviously is =
more complicated, but also more powerful, and issues like how to define =
and/or register such applications come up.

I do not know if this is worth the effort, and there would certainly be =
a backward compatibilty issue with hosts not understnding the =
extension. For those kind of hosts as callee, the caller would still =
need to terminate the call if undesirable media combinations are =
selected.

Best regards,

Th Belling


----------------------------------
Dr. Thomas Belling
Siemens AG          =20
Sankt-Martin-Str. 76=20
D-81541 M=FCnchen Germany
Com MN PG NT MN 1
MCH M 34 307
Tel     +49 89 636 75207
Fax     +49 89 636 75577
Mobile  +49 172 2974678
Email   Thomas.Belling@siemens.com



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


From mmusic-bounces@ietf.org  Wed Jan  5 13:47:57 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 NAA29717
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 13:47:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmGOx-0001qz-3s
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 14:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmGB8-0002cH-5q; Wed, 05 Jan 2005 13:46:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmG5F-0001i7-R9
	for mmusic@megatron.ietf.org; Wed, 05 Jan 2005 13:40:37 -0500
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 NAA29223
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 13:40:34 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmGHp-00013k-Fn
	for mmusic@ietf.org; Wed, 05 Jan 2005 13:53:40 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 05 Jan 2005 10:40:07 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j05Ie0RO001352
	for <mmusic@ietf.org>; Wed, 5 Jan 2005 10:40:01 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com
	[171.68.225.134]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA18067 for
	<mmusic@ietf.org>; Wed, 5 Jan 2005 10:40:00 -0800 (PST)
Message-Id: <4.3.2.7.2.20050105122617.025c7768@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 05 Jan 2005 12:40:20 -0600
To: mmusic@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [MMUSIC] Video phone and offer/answer model
In-Reply-To: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1D3@mchh266e.mchh.sie
	mens.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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: 1.1 (+)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: quoted-printable

comments below

At 03:52 PM 1/5/2005 +0100, Belling Thomas wrote:
>Hi folks,
>
> > -----Original Message-----
> > From: mmusic-bounces@ietf.org
> > [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
> > Sent: Wednesday, January 05, 2005 3:14 PM
> > To: Jun KOSHIKO
> > Cc: mmusic@ietf.org
> > Subject: Re: [MMUSIC] Video phone and offer/answer model
> >
>...
> >
> > But I think your issue is that the *caller* doesn't want the call to
> > succeed unless there is both voice and video. I don't know of
> > any *good*
> > way to do this currently.
> >
>A clean way to resolve that would probably bee a new type of grouping=20
>within the grouping framework. As a minimum, the grouping would express=20
>that all media for the grouped m-lines need to be established together, or=
=20
>none of them.

ah, but don't we really then need to address the scenario of the offer=20
containing more than 1 audio codec and more than 1 video codec (i.e. "MUST=
=20
choose one codec from each M line"), and only wishing to accept the call if=
=20
one from each (1 audio and 1 video) is chosen - and not one from either=20
(audio *or* video)?

For example, I might offer you (0 4 18) in audio and (31 34) in video in my=
=20
SDP1 to you, and I care that you choose one each from both of these groups,=
=20
not one total from either.

>I do not know if this is worth the effort, and there would certainly be a=
=20
>backward compatibilty issue with hosts not understnding the extension.

If an indication is created requiring one codec from each M line to be=20
chosen - and the answerer does not comply - this leaves it up to the=20
offerer to decide if it wants to mandate both audio and video MUST be=20
supported by the answerer in order to complete the call. If the offerer=20
believes this is true, I do not believe there is a backwards compatibility=
=20
issue, is there? The answer is simply rejected. This rejection should=20
indicate to the offerer that the called party either doesn't support=20
mandating audio and video, or doesn't support one of the M lines.

>For those kind of hosts as callee, the caller would still need to=20
>terminate the call if undesirable media combinations are selected.
>
>Best regards,
>
>Th Belling
>
>
>----------------------------------
>Dr. Thomas Belling
>Siemens AG
>Sankt-Martin-Str. 76
>D-81541 M=FCnchen Germany
>Com MN PG NT MN 1
>MCH M 34 307
>Tel     +49 89 636 75207
>Fax     +49 89 636 75577
>Mobile  +49 172 2974678
>Email   Thomas.Belling@siemens.com
>
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented

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


From mmusic-bounces@ietf.org  Wed Jan  5 16:57:40 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 QAA22992
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 16:57:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmJMd-0004t9-Ez
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 17:10:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmJ7H-0002vy-Ed; Wed, 05 Jan 2005 16:54:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmJ3v-00027v-Hp; Wed, 05 Jan 2005 16:51:27 -0500
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 QAA22466;
	Wed, 5 Jan 2005 16:51:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmJGa-0003kY-6V; Wed, 05 Jan 2005 17:04:32 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CmIvf-0008Ao-8V; Wed, 05 Jan 2005 16:42:55 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1CmIvf-0008Ao-8V@megatron.ietf.org>
Date: Wed, 05 Jan 2005 16:42:55 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: mmusic@ietf.org
Subject: [MMUSIC] Last Call: 'Key Management Extensions for Session
 Description Protocol
 (SDP) and Real Time Streaming Protocol (RTSP)' to Proposed Standard 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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: d6b246023072368de71562c0ab503126

The IESG has received a request from the Multiparty Multimedia Session Control
WG to consider the following document:

- 'Key Management Extensions for Session Description Protocol (SDP) and Real 
   Time Streaming Protocol (RTSP) '
   <draft-ietf-mmusic-kmgmt-ext-12.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-01-19.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-12.txt


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


From mmusic-bounces@ietf.org  Wed Jan  5 17:08: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 RAA23912
	for <mmusic-web-archive@ietf.org>; Wed, 5 Jan 2005 17:08:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmJX2-00076U-NQ
	for mmusic-web-archive@ietf.org; Wed, 05 Jan 2005 17:21:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmJ7J-0002wT-RE; Wed, 05 Jan 2005 16:54:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmJ41-0002AW-Nf; Wed, 05 Jan 2005 16:51:33 -0500
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 QAA22474;
	Wed, 5 Jan 2005 16:51:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmJGg-0003ko-CJ; Wed, 05 Jan 2005 17:04:38 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CmIwV-0008U8-Hn; Wed, 05 Jan 2005 16:43:47 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1CmIwV-0008U8-Hn@megatron.ietf.org>
Date: Wed, 05 Jan 2005 16:43:47 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mmusic@ietf.org
Subject: [MMUSIC] Last Call: 'Session Description Protocol Security
 Descriptions for Media Streams' to Proposed Standard 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Multiparty Multimedia Session Control
WG to consider the following document:

- 'Session Description Protocol Security Descriptions for Media Streams '
   <draft-ietf-mmusic-sdescriptions-08.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-01-19.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions-08.txt


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


From mmusic-bounces@ietf.org  Thu Jan  6 03:23:54 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 DAA20554
	for <mmusic-web-archive@ietf.org>; Thu, 6 Jan 2005 03:23:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmT8j-0005n6-LE
	for mmusic-web-archive@ietf.org; Thu, 06 Jan 2005 03:37:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmSuJ-0007q9-P8; Thu, 06 Jan 2005 03:22:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmSpV-00072d-OY
	for mmusic@megatron.ietf.org; Thu, 06 Jan 2005 03:17:14 -0500
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 DAA20281
	for <mmusic@ietf.org>; Thu, 6 Jan 2005 03:17:12 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmT2D-0002Fo-NM
	for mmusic@ietf.org; Thu, 06 Jan 2005 03:30:24 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 06 Jan 2005 00:17:12 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j068Gb1X028763;
	Thu, 6 Jan 2005 00:16:38 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-152.cisco.com
	[10.86.240.152]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AGV82582; Thu, 6 Jan 2005 00:16:36 -0800 (PST)
Message-ID: <41DCF3E4.40108@cisco.com>
Date: Thu, 06 Jan 2005 03:16:36 -0500
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 issue: RTP specificity of the candidate attribute
References: <41B67F33.2030203@cisco.com> <41B730FD.7060709@ericsson.com>
In-Reply-To: <41B730FD.7060709@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit

Sorry for the huge delay in responding here.

I don't think the approach you are proposing works. Each of the 
candidates can have a different q-value and different usernames and 
ports. Your BNF "factors those out" so that they are common for all 
candidates. Since they differ for each candidate, you'd need to repeat 
them. Thus, nothing would be shared (I think id should be different 
too), and then I don't see what is gained by putting them on the same line.

Using separate lines also makes it easier to extend the candidate line 
in the future. We've discussed allowing to specify tcp as an alternate 
for a udp media stream. Though we decided not to do that now, I think we 
will need to do something like that eventually and I want to leave the 
door open. I think the extensibility is easier if each candidate is its 
own line.

Thanks,
Jonathan R.

Magnus Westerlund wrote:

> Hi Jonathan,
> 
> I think this is the right direction. I do however wonder if it is the 
> right solution. Your current solution indicates multiple lines that are 
> part of the same address candidate. I think using a ABNF that kept each 
> candidate on a single line might be better. As all address for the same 
> candidate is needed, due to the protocols need, like both RTP and RTCP 
> addresses for RTP. The question here is if one should use explicit 
> binding as you propose, or rely on the order defined by the protocol 
> when specifying address. However it might be easier to do the binding 
> explicitly. My proposal for ABNF for a single line solution would be:
> 
> candidate-attribute   = "candidate" ":" id SP qvalue SP
>                          user-frag SP password 1*(SP address-spec)
> address-spec          =  (unicast-address "/" port ";"
>                          candidate-addr "/" candidate-port )
> 
> 
> 
> Jonathan Rosenberg wrote:
> 
>> Folks,
>>
>> I got some private comments on the ICE-03 spec, and in the process of
>> going through them, a few of them were significant enough that they
>> require group discussion.
>>
>> The issue that was raised here is that the SDP candidate attribute is
>> currently very RTP specific. This would make it necessary to define new
>> SDP attributes for other transport protocols that wish to use the ICE
>> framework. It also means that its hard to handle cases like RFC 2733,
>> where there is an IP/port conveyed in an fmtp line.
>>
> 
> I would like to point out that I at least are trying to deprecate that 
> type of usage, due to its unsuitability in SDP. As we have deployed a 
> number of SDP extension, that applies to the media session, specifying 
> another session inside FMTP lines looses all these extensions. Thus my 
> personal opinion is that it is easier to remove the few special cases 
> like RFC 2733 than to get the other mechanisms to work for the special 
> cases. That is why I have argued in the ULP context to change the 
> binding between original data and FEC data.
> 
> 
> 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
> 

-- 
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 Jan  6 04:47:17 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 EAA24104
	for <mmusic-web-archive@ietf.org>; Thu, 6 Jan 2005 04:47:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmURP-0006v7-5S
	for mmusic-web-archive@ietf.org; Thu, 06 Jan 2005 05:00:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmUAK-0007rz-FG; Thu, 06 Jan 2005 04:42:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmU8w-0007SH-8o
	for mmusic@megatron.ietf.org; Thu, 06 Jan 2005 04:41:23 -0500
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 EAA23741
	for <mmusic@ietf.org>; Thu, 6 Jan 2005 04:41:20 -0500 (EST)
Received: from eastmail3.ntt-east.co.jp ([202.229.5.46]
	helo=evx3.enoc.east.ntt.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmULd-00034h-H3
	for mmusic@ietf.org; Thu, 06 Jan 2005 04:54:33 -0500
Received: from emix1.enoc.east.ntt.co.jp 
	by evx3.enoc.east.ntt.co.jp with ESMTP id j069eTp07446;
	Thu, 6 Jan 2005 18:40:29 +0900 (JST)
Received: from cip4.noc.east.ntt.co.jp 
	by emix1.enoc.east.ntt.co.jp with ESMTP id j069eTj23660;
	Thu, 6 Jan 2005 18:40:29 +0900 (JST)
Received: from [10.8.52.30] ([10.8.52.30])
	by cip4.noc.east.ntt.co.jp (MOS 3.4.6-GR) with ESMTP id BCG00407;
	Thu, 6 Jan 2005 18:40:28 +0900 (JST)
Date: Thu, 06 Jan 2005 18:40:30 +0900
From: Jun KOSHIKO <j.koshiko@rdc.east.ntt.co.jp>
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Video phone and offer/answer model
In-Reply-To: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1D3@mchh266e.mchh.siemens.de>
References: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1D3@mchh266e.mchh.siemens.de>
Message-Id: <20050106183400.14E8.J.KOSHIKO@rdc.east.ntt.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.11.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
Cc: Belling Thomas <thomas.belling@siemens.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: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit

Hello Folks;

Thank you for your replies.

> Belling Thomas wrote:
...

> A clean way to resolve that would probably bee a new type of grouping
> within the grouping framework. As a minimum, the grouping would express
> that all media for the grouped m-lines need to be established together,
> or none of them. As the media belong together in the sense that they
> need to be handled by a combined application, the more far-reaching
> idea would be to indicate the application in the new grouping type.
> This obviously is more complicated, but also more powerful, and issues
> like how to define and/or register such applications come up.

RFC3388, grouping framework of m line, seems like a good resolution for
the problem. Thanks for the information.

I imagine that your idea of indication of the application like the
following example. A new semantic like "VIDEO-PHONE" will be defined,
and lines of two m lines (audio/video) will be grouped. And some
attributes will be newly defined for video-phone specific use. 
Is my understanding true?

...
a=group:VIDEO-PHONE 1 2
m=audio 30000 RTP/AVP 0 4 18
a=mid:1
a=xxx:xxx  (<- newly defined attribute)
m=video 30002 RTP/AVP 31 34
a=mid:2
a=xxx:xxx  (<- newly defined attribute)


As a minimum, I guess LS(Lip Synchronization) semantic defined in
RFC3388 could be applicable without difining a new type of grouping.

I think that video and audio stream need to be synchronized for the
video phone service. And synchronization of video and audio implies the
existance of common codecs both of video and of audio. Considering the
following case, I guess that a callee usually rejects the offer if it
doesn't support either (0) of audio codec or (31) of video codec. 

I feel slightly uncomfortable about using LS semantic because the usage
of LS semantic seems like different from the problem.

 Caller                                 Callee
   |                                       |
   | (offer)                               |
   | a=group:LS 1 2                        |
   | m=audio 30000 RTP/AVP 0               |
   | .                                     |
   | .                                     |
   | a=mid:1                               |
   | m=video 30002 RTP/AVP 31              |
   | .                                     |
   | .                                     |
   | a=mid:2                               |
   |-------------------------------------->|
   |                                       |
   |                               (answer)|
   |<--------------------------------------|

> I do not know if this is worth the effort, and there would certainly be
> a backward compatibilty issue with hosts not understnding the extension.
> For those kind of hosts as callee, the caller would still need to
> terminate the call if undesirable media combinations are selected.

I think something like SIP require header may be needed to avoid
undesirable media combinations considering a backward compatibility.

Best regards,
Jun Koshiko

> 
> Best regards,
> 
> Th Belling
> 
> 
> ----------------------------------
> Dr. Thomas Belling
> Siemens AG           
> Sankt-Martin-Str. 76 
> D-81541 M|nchen Germany
> Com MN PG NT MN 1
> MCH M 34 307
> Tel     +49 89 636 75207
> Fax     +49 89 636 75577
> Mobile  +49 172 2974678
> Email   Thomas.Belling@siemens.com
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic

---------------------------------------------------------
Jun KOSHIKO
Next Generation Strategy
Research and Development Center
NTT-east Corporation

Telephone  +81 3 5359 5104
Facsimile  +81 3 5359 4768
E-mail: j.koshiko@rdc.east.ntt.co.jp
19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
---------------------------------------------------------


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


From mmusic-bounces@ietf.org  Thu Jan  6 05:00: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 FAA24776
	for <mmusic-web-archive@ietf.org>; Thu, 6 Jan 2005 05:00:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmUdp-0003jm-7W
	for mmusic-web-archive@ietf.org; Thu, 06 Jan 2005 05:13:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmUKj-0001Jw-6M; Thu, 06 Jan 2005 04:53:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmUHz-0000Vq-VY
	for mmusic@megatron.ietf.org; Thu, 06 Jan 2005 04:50:44 -0500
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 EAA24266
	for <mmusic@ietf.org>; Thu, 6 Jan 2005 04:50:42 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmUUX-0008Ei-DZ
	for mmusic@ietf.org; Thu, 06 Jan 2005 05:03:55 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j069nvPs011964; Thu, 6 Jan 2005 10:50:26 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 6 Jan 2005 10:45:26 +0100
Received: from [147.214.97.151] ([147.214.97.151]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 6 Jan 2005 10:45:26 +0100
Message-ID: <41DD08B4.4030500@ericsson.com>
Date: Thu, 06 Jan 2005 10:45:24 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE issue: RTP specificity of the candidate attribute
References: <41DCF3E4.40108@cisco.com>
In-Reply-To: <41DCF3E4.40108@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jan 2005 09:45:26.0356 (UTC)
	FILETIME=[7323D140:01C4F3D4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
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: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit

Hi Jonathan,

Apparently some confusion here. I am not talking about putting multiple 
candidates on the same line. I am only talking about candidates that in 
fact consist of multiple addresses. My prime example is the RTP and RTCP 
case, where each candidate address has one RTP component and another 
RTCP component. The reason I think this grouping of multiple address 
that a single candidate needs, is that it is not desired to have 
different address components over different candidates. At least for RTP 
and RTCP sending RTCP the long way by a relay and RTP directly will 
provide bad RTCP statistics. Some are using RTCP to at least avoid 
catastrophic congestion, some are even going further. If RTP and RTCP 
already on application level get routed by different paths, this is bad.

I hope you understand my motivation to put multiple addresses in a 
candidate and forcing a grouping of the different protocol components.

So lets start in the more fundamental end of the question: Should one 
group multiple address per candidate and only use a candidate if all 
addresses for that candidate works?

Cheers

Magnus

Jonathan Rosenberg wrote:
> Sorry for the huge delay in responding here.
> 
> I don't think the approach you are proposing works. Each of the 
> candidates can have a different q-value and different usernames and 
> ports. Your BNF "factors those out" so that they are common for all 
> candidates. Since they differ for each candidate, you'd need to repeat 
> them. Thus, nothing would be shared (I think id should be different 
> too), and then I don't see what is gained by putting them on the same line.
> 
> Using separate lines also makes it easier to extend the candidate line 
> in the future. We've discussed allowing to specify tcp as an alternate 
> for a udp media stream. Though we decided not to do that now, I think we 
> will need to do something like that eventually and I want to leave the 
> door open. I think the extensibility is easier if each candidate is its 
> own line.
> 
> Thanks,
> Jonathan R.
> 
> Magnus Westerlund wrote:
> 
> 
>>Hi Jonathan,
>>
>>I think this is the right direction. I do however wonder if it is the 
>>right solution. Your current solution indicates multiple lines that are 
>>part of the same address candidate. I think using a ABNF that kept each 
>>candidate on a single line might be better. As all address for the same 
>>candidate is needed, due to the protocols need, like both RTP and RTCP 
>>addresses for RTP. The question here is if one should use explicit 
>>binding as you propose, or rely on the order defined by the protocol 
>>when specifying address. However it might be easier to do the binding 
>>explicitly. My proposal for ABNF for a single line solution would be:
>>
>>candidate-attribute   = "candidate" ":" id SP qvalue SP
>>                         user-frag SP password 1*(SP address-spec)
>>address-spec          =  (unicast-address "/" port ";"
>>                         candidate-addr "/" candidate-port )
>>
>>
>>

-- 

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Thu Jan  6 13:36:23 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 NAA00039
	for <mmusic-web-archive@ietf.org>; Thu, 6 Jan 2005 13:36:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmchX-0007Th-JE
	for mmusic-web-archive@ietf.org; Thu, 06 Jan 2005 13:49:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmcJc-00074E-W7; Thu, 06 Jan 2005 13:24:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmcGe-0006IW-0S; Thu, 06 Jan 2005 13:21:52 -0500
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 NAA29121;
	Thu, 6 Jan 2005 13:21:49 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmcTO-0006oq-2K; Thu, 06 Jan 2005 13:35:07 -0500
Received: from [10.10.108.16] ([65.119.52.228]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id j06ILbVu031640
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 6 Jan 2005 12:21:38 -0600 (CST) (envelope-from ben@nostrum.com)
In-Reply-To: <41DAFA0F.9070805@cisco.com>
References: <A0199C6C-48A6-11D9-91F3-000D93B0AE1A@nostrum.com>	<3604A854-4AF4-11D9-91F3-000D93B0AE1A@nostrum.com>	<6709D884-4B70-11D9-8877-000A957FC5F2@csperkins.org>	<41BC325D.4010808@tzi.uni-bremen.de>	<C7C9823E-4CE6-11D9-8A90-000D93C60BA0@telio.no>	<41D0955B.2080704@nostrum.com>	<4E86F292-5DA8-11D9-A1D2-000D93B0AE1A@nostrum.com>	<768E41B2-5DAA-11D9-9BB1-000D93C60BA0@telio.no>	<D3D4EE48-5DB1-11D9-ADD5-000A957FC5F2@csperkins.org>
	<41DA164E.40603@cisco.com> <41DAFA0F.9070805@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <C9BFAA80-600F-11D9-B9AF-000D93B0AE1A@nostrum.com>
From: Ben Campbell <ben@nostrum.com>
Subject: Re: [MMUSIC] Re: [Simple] MSRP: SDP usage concern
Date: Thu, 6 Jan 2005 12:21:30 -0600
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mmusic@ietf.org, Joerg Ott <jo@tzi.uni-bremen.de>,
        Colin Perkins <csp@csperkins.org>, Simple WG <simple@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0440912010=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2


--===============0440912010==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3-26955797;
	protocol="application/pkcs7-signature"


--Apple-Mail-3-26955797
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit


On Jan 4, 2005, at 2:18 PM, Paul Kyzivat wrote:

[...]

[Lots of text removed concerning moving the MSRP path from an a-line 
into the c-line]

> Is this better than what is currently proposed in 
> draft-ietf-simple-message-sessions-09? Debatable.
>
> Does it come closer to the spirit of SDP? Also debatable.
>

It also seems like it would also have a higher chance of breaking 
existing parsers than the a-line attribute approach.

[...]
--Apple-Mail-3-26955797
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEjCCAssw
ggI0oAMCAQICAwwdSDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwNDEyMjA0NTUyWhcNMDUwNDEyMjA0NTUyWjBBMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg9iZW5Abm9zdHJ1bS5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDGFv8c1i8a9NXiEohMEryzypOcyz39k8PN
WxTS4F45JSYwQ0/RAZ4vaemHCyJaUc7tc5DN3o7zl2oaqQuOIrvnjk79ILGJVfRgwt+uGDIGyaSM
YmBeKXSdawFiJdk5jGtMzlgF8tzJzc4do5Mzl5YS39AR8mj8PF4zEgIlYYkKXBByHQ2jPA0qVfm/
Aj71RdYZyDAD4P7TyW9jKvZCl7KCfajar1llEQVj+kWMvt/3AE6mwAHXfkU7nL9XzLvGSnMUJvYx
hq3UDju4IacXsYFw2oLb4LQdvwP4Lbg6qdp08h59+TkHlV6WNdt3ggM9C/cGQTDCa0CVJsr+76Dm
mPorAgMBAAGjLDAqMBoGA1UdEQQTMBGBD2JlbkBub3N0cnVtLmNvbTAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBAApFAg5tsI2OhByoUglTZ+ip3M/1xfWDsCNsDB4+HtnH9fZfKkrkGp4e
JQyuvl5VhvW67qYU6wEPMD0EKoWDU3v7l1huzR7Cpkf7n21y4LLG+VxldYiA3SEkv7RBPhhVhdMl
sHwNZAYyVXFCdnvuVjfeytdAeXK6vzcaUvo9EwkHMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0B
AQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw
ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv
biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAw
MDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1
aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/
ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoT
zyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GU
MIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3
dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQi
MCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQ
g+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsA
xRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXe
JLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMMHUgwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc
BgkqhkiG9w0BCQUxDxcNMDUwMTA2MTgyMTMxWjAjBgkqhkiG9w0BCQQxFgQUJ3fPjsAU2/lqb4F3
gUTm0vwa+ncweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwwdSDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMMHUgwDQYJKoZIhvcNAQEBBQAEggEAapvqcgWcLTdSGKhT
JvE4ikfSg1VesI8e1O+5ZFanTFpMSe4NSo7I6H9jnv/9NwW4AcK9KZS/39P1PkL6/p2QEVWE6m0a
0MXRFqBDf6xicLgiaTmiYOajElVnkok54YNWMEDcTox/iKrgWP8AJtd+IyeDYJjP/MxzEEVNBYb/
JTQnRpSHXTOqmiBW3auTJUEfZL5I5nDky8V+VPoMKkxC/cArWyt60wOF9f7GTRLS7/xEBsqXFWJR
DL2ucyvVM8ueBOUsuo/V+VVdZnEt3W3XT6zsSDy/Ib/rfwmFpl6tTduwYr5KpE/LFNhbHQlDnpj/
3QSCJIvH3nTxmn68wh4P7AAAAAAAAA==

--Apple-Mail-3-26955797--



--===============0440912010==
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

--===============0440912010==--




From mmusic-bounces@ietf.org  Fri Jan  7 11:58:37 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 LAA27898
	for <mmusic-web-archive@ietf.org>; Fri, 7 Jan 2005 11:58:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cmxef-0006JK-8m
	for mmusic-web-archive@ietf.org; Fri, 07 Jan 2005 12:12:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmxKn-0003Rj-VN; Fri, 07 Jan 2005 11:51:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cmx7v-0007aE-SW
	for mmusic@megatron.ietf.org; Fri, 07 Jan 2005 11:38:15 -0500
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 LAA25547
	for <mmusic@ietf.org>; Fri, 7 Jan 2005 11:38:13 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmxKv-0004k6-0G
	for mmusic@ietf.org; Fri, 07 Jan 2005 11:51:43 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 07 Jan 2005 08:38:31 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j07GbdRO009494;
	Fri, 7 Jan 2005 08:37:40 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-2-84.cisco.com [10.86.242.84])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AGW71964;
	Fri, 7 Jan 2005 08:37:38 -0800 (PST)
Message-ID: <41DEBAD1.2070900@cisco.com>
Date: Fri, 07 Jan 2005 11:37:37 -0500
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 issue: RTP specificity of the candidate attribute
References: <41DCF3E4.40108@cisco.com> <41DD08B4.4030500@ericsson.com>
In-Reply-To: <41DD08B4.4030500@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit



Magnus Westerlund wrote:

> Hi Jonathan,
> 
> Apparently some confusion here. I am not talking about putting multiple 
> candidates on the same line. I am only talking about candidates that in 
> fact consist of multiple addresses.

Ah, OK, that wasn't clear to me.

  My prime example is the RTP and RTCP
> case, where each candidate address has one RTP component and another 
> RTCP component. The reason I think this grouping of multiple address 
> that a single candidate needs, is that it is not desired to have 
> different address components over different candidates.

I'm not sure I agree with that. More below.

> At least for RTP 
> and RTCP sending RTCP the long way by a relay and RTP directly will 
> provide bad RTCP statistics. Some are using RTCP to at least avoid 
> catastrophic congestion, some are even going further. If RTP and RTCP 
> already on application level get routed by different paths, this is bad.

To be clear, I think the only reason its really problematic is that RTCP 
is used to take RTT measurements for RTP. Beyond that, reporting of loss 
  statistics and sent/received RTP packets could be done on a totally 
separate path.

So, though it is better for RTP, it may not be better for other usages 
of multiple addresses. Its less clear to me that it would matter for 
FEC, for example.

> 
> I hope you understand my motivation to put multiple addresses in a 
> candidate and forcing a grouping of the different protocol components.

I understand the motivation, yes. Forcing the grouping does mean that 
its possible that a call fails because you couldn't get successful 
checks for all components on the same "bundle" of addresses. In other 
words, if you are advertising STUN addresses for RTP and RTCP, and also 
local interfaces, it could be that the ICE checks succeed for STUN RTP 
and local RTCP. The grouping you propose would cause the call to fail. 
Admittedly, I am hard pressed to think about when this would happen, but 
you never know.

Indeed, if you think it will seldom happen, you can accomplish a loose 
form of the grouping by making sure that the priorities for the 
candidates for RTP and RTCP are in the same relative order. In other 
words, using the same example as above, if I assign priority 1.0 to the 
local interface RTP, 0.8 to the local interface RTCP, 0.5 to the STUn 
RTP and 0.4 to the STUN RTCP, the RTP and RTCP candidates have the same 
relative priorities. If its likely that the local interface ones are 
likely to fail or succeed for BOTH RTCP and RTP, then you end up 
selecting the same transport for both.

Furthermore, if it turns out that, for some oddball reason, it succeeds 
for one and not the other, the call would still go through.

As such, I am inclined to instead suggest that prioritization be used to 
realize the grouping, and then we are free to put each on a separate 
line. I prefer separate lines since I think it makes future 
extensibility easier.

> 
> So lets start in the more fundamental end of the question: Should one 
> group multiple address per candidate and only use a candidate if all 
> addresses for that candidate works?

Per above, I would say SHOULD is the right thing here; you want them to 
use the same in some cases (like RTP/RTCP), but its preferable to have 
the call proceed if you can't, than for the call to fail.

-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  Sat Jan  8 15:03:52 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 PAA27422
	for <mmusic-web-archive@ietf.org>; Sat, 8 Jan 2005 15:03:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CnN1j-0006Lz-Te
	for mmusic-web-archive@ietf.org; Sat, 08 Jan 2005 15:17:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CnMm5-00027g-Uk; Sat, 08 Jan 2005 15:01:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CnMkn-00014H-Gd
	for mmusic@megatron.ietf.org; Sat, 08 Jan 2005 15:00:05 -0500
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 PAA27128
	for <mmusic@ietf.org>; Sat, 8 Jan 2005 15:00:04 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CnMy2-0006HD-1P
	for mmusic@ietf.org; Sat, 08 Jan 2005 15:13:46 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61409
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CnMkF-0004Kx-W3
	for mmusic@ietf.org; Sat, 08 Jan 2005 19:59:32 +0000
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <200412282051.PAA25487@ietf.org>
References: <200412282051.PAA25487@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <CB30367C-61AF-11D9-B0D1-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-00.txt
Date: Sat, 8 Jan 2005 19:59:24 +0000
To: IETF MMUSIC Working Group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit

On 28 Dec 2004, at 20:51, Internet-Drafts@ietf.org wrote:
> 	Title		: An Extension to the Session Description Protocol
> 			  (SDP) for Media Loopback
> 	Author(s)	: K. Hedayat, et al.
> 	Filename	: draft-ietf-mmusic-media-loopback-00.txt
> 	Pages		: 14
> 	Date		: 2004-12-28

I have some comments on this draft:

I'd like to see more motivation for why rtp-pkt-loopback is useful. I 
can see why rtp-media-loopback would work, since it returns the media 
as presented to the remote user, but the benefits of rtp-pkt-loopback 
are less clear, especially since the receiver must regenerate the RTP 
sequence number when it loops back the media, making it difficult to 
detect lost packets.

The requirements on use of RTCP XR in section 7 are, I believe, too 
strong. This is because not all applications support voice, or 
necessarily wish to implement RTCP XR. I would recommend changing 
section 7 to state that RTCP MUST be implemented, and to note that RTCP 
XR MAY be used in addition (with an explanation of why it would be 
beneficial to implement RTCP XR, rather than a normative "SHOULD" 
strength requirement to do so).

I don't believe the security considerations are adequate. The draft 
needs to discuss the potential for DoS attacks in more detail, explain 
how the use of authentication will prevent such attacks, and provide 
recommendations of how to perform authentication such that 
interoperable implementations can be built. I'd also expect there to be 
some greater discussion of the privacy implications, and a 
recommendation that end points either MUST NOT loopback media without a 
users knowledge, or MUST allow the user to disable loopback.

IANA considerations is inaccurate, since the IANA must register certain 
new SDP attributes.

Please also fix the following nits:

idnits 1.49 (16 Nov 2004)

draft-ietf-mmusic-media-loopback-00.txt:

   Checking conformance with RFC 3667/3668 boilerplate...
   The document seems to lack an RFC 3667 Section 5.1 IPR Disclosure 
Acknowledgement
   -- however, there's a paragraph with a matching beginning. 
Boilerplate error?
   The document seems to lack an RFC 3667 Section 5.4 Copyright Notice
   -- however, there's a paragraph with a matching beginning. 
Boilerplate error?
   There are 1 instances of lines with control characters in the 
document.

   Warnings:
     There are 1 instances of lines with hyphenated line breaks in the 
document.



Colin


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


From mmusic-bounces@ietf.org  Mon Jan 10 13:06:29 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 NAA10011
	for <mmusic-web-archive@ietf.org>; Mon, 10 Jan 2005 13:06:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co49e-0002tz-D4
	for mmusic-web-archive@ietf.org; Mon, 10 Jan 2005 13:20:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co3lk-00068j-Jl; Mon, 10 Jan 2005 12:55:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co3h7-00059F-4Q
	for mmusic@megatron.ietf.org; Mon, 10 Jan 2005 12:51:09 -0500
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 MAA08657
	for <mmusic@ietf.org>; Mon, 10 Jan 2005 12:51:06 -0500 (EST)
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co3ui-0002Nm-7F
	for mmusic@ietf.org; Mon, 10 Jan 2005 13:05:15 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.12.6/8.12.6) with ESMTP id j0AHnrtr012076;
	Mon, 10 Jan 2005 18:49:53 +0100
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id j0AHnrPQ005700;
	Mon, 10 Jan 2005 18:49:53 +0100
Received: from mchh275e.mchh.siemens.de (mchh275e.mchh.siemens.de
	[139.21.200.61])
	by moody.mchh.siemens.de (8.12.6/8.12.6) with ESMTP id j0AHnr3g021866; 
	Mon, 10 Jan 2005 18:49:53 +0100
Received: by mchh275e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <YRW8QVPD>; Mon, 10 Jan 2005 18:48:32 +0100
Message-ID: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1E8@mchh266e.mchh.siemens.de>
From: Belling Thomas <thomas.belling@siemens.com>
To: "'James M. Polk'" <jmpolk@cisco.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Mon, 10 Jan 2005 18:49:52 +0100
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: d8ae4fd88fcaf47c1a71c804d04f413d
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: bdc523f9a54890b8a30dd6fd53d5d024

Hi James,

comments below.

Thomas

> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org] On Behalf Of James M. Polk
> Sent: Wednesday, January 05, 2005 7:40 PM
> To: mmusic@ietf.org
> Subject: RE: [MMUSIC] Video phone and offer/answer model
> > >
> > > But I think your issue is that the *caller* doesn't want 
> the call to
> > > succeed unless there is both voice and video. I don't know of
> > > any *good*
> > > way to do this currently.
> > >
> >A clean way to resolve that would probably bee a new type of 
> grouping 
> >within the grouping framework. As a minimum, the grouping 
> would express 
> >that all media for the grouped m-lines need to be 
> established together, or 
> >none of them.
> 
> ah, but don't we really then need to address the scenario of 
> the offer 
> containing more than 1 audio codec and more than 1 video 
> codec (i.e. "MUST 
> choose one codec from each M line"), and only wishing to 
> accept the call if 
> one from each (1 audio and 1 video) is chosen - and not one 
> from either 
> (audio *or* video)?


In my understanding each m-line talks about a single media stream, with different encoding possibilities. Requiring a selection of only 1 codec for each media stream is different from the problem beeing discussed so far, i.e. expressing that several media streams are required in a combination.

RFC 3264 states:
"The offer will contain zero or more media streams (each media stream
   is described by an "m=" line and its associated attributes). 
...
The list of media formats for each media stream conveys two pieces of
   information, namely the set of formats (codecs and any parameters
   associated with the codec, in the case of RTP) that the offerer is
   capable of sending and/or receiving (depending on the direction
   attributes), and, in the case of RTP, the RTP payload type numbers
   used to identify those formats.  If multiple formats are listed, it
   means that the offerer is capable of making use of any of those
   formats during the session.  In other words, the answerer MAY change
   formats in the middle of the session, making use of any of the
   formats listed, without sending a new offer.
...
10.2 One of N Codec Selection

   A common occurrence in embedded phones is that the Digital Signal
   Processor (DSP) used for compression can support multiple codecs at a
   time, but once that codec is selected, it cannot be readily changed
   on the fly.  This example shows how a session can be set up using an
   initial offer/answer exchange, followed immediately by a second one
   to lock down the set of codecs."

> 
> For example, I might offer you (0 4 18) in audio and (31 34) 
> in video in my 
> SDP1 to you, and I care that you choose one each from both of 
> these groups, 
> not one total from either.

This is not what I had in mind in my proposal. The grouping would rather indicate that the answerer MUST either accept all the grouped media streams (each described by a separate m-line) or reject them all.
Accepting or Rejecting would be done for each media stream according to RFC 3264, i.e. the answerer needs to select at least one of the offered codecs for each m-line to accept the corresponding media stream.

 

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


From mmusic-bounces@ietf.org  Mon Jan 10 13:25: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 NAA11321
	for <mmusic-web-archive@ietf.org>; Mon, 10 Jan 2005 13:25:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co4SU-0003X7-1y
	for mmusic-web-archive@ietf.org; Mon, 10 Jan 2005 13:40:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co49l-0002Wa-AT; Mon, 10 Jan 2005 13:20:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co44V-0001JU-FW
	for mmusic@megatron.ietf.org; Mon, 10 Jan 2005 13:15:19 -0500
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 NAA10729
	for <mmusic@ietf.org>; Mon, 10 Jan 2005 13:15:16 -0500 (EST)
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co4I7-0003Dx-RE
	for mmusic@ietf.org; Mon, 10 Jan 2005 13:29:26 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by david.siemens.de (8.12.6/8.12.6) with ESMTP id j0AIFDtr029294;
	Mon, 10 Jan 2005 19:15:14 +0100
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id j0AIFD3r012897;
	Mon, 10 Jan 2005 19:15:13 +0100
Received: from mchh253e.mchh.siemens.de (mchh253e.mchh.siemens.de
	[139.21.200.63])
	by moody.mchh.siemens.de (8.12.6/8.12.6) with ESMTP id j0AIFC3g026993; 
	Mon, 10 Jan 2005 19:15:13 +0100
Received: by mchh253e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <YBAH3Z95>; Mon, 10 Jan 2005 19:13:53 +0100
Message-ID: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1E9@mchh266e.mchh.siemens.de>
From: Belling Thomas <thomas.belling@siemens.com>
To: "'Jun KOSHIKO'" <j.koshiko@rdc.east.ntt.co.jp>, mmusic@ietf.org
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Mon, 10 Jan 2005 19:15:11 +0100
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: 789c141a303c09204b537a4078e2a63f
Cc: Belling Thomas <thomas.belling@siemens.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: d16ce744298aacf98517bc7c108bd198

Dear Jon,

comments below

BR, Thomas

> -----Original Message-----
> From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp] 
> Sent: Thursday, January 06, 2005 10:41 AM
> To: mmusic@ietf.org
> Cc: Belling Thomas
> Subject: Re: [MMUSIC] Video phone and offer/answer model
> 
> 
> Hello Folks;
> 
> Thank you for your replies.
> 
> > Belling Thomas wrote:
> ...
> 
> > A clean way to resolve that would probably bee a new type 
> of grouping
> > within the grouping framework. As a minimum, the grouping 
> would express
> > that all media for the grouped m-lines need to be 
> established together,
> > or none of them. As the media belong together in the sense that they
> > need to be handled by a combined application, the more far-reaching
> > idea would be to indicate the application in the new grouping type.
> > This obviously is more complicated, but also more powerful, 
> and issues
> > like how to define and/or register such applications come up.
> 
> RFC3388, grouping framework of m line, seems like a good 
> resolution for
> the problem. Thanks for the information.
> 
> I imagine that your idea of indication of the application like the
> following example. A new semantic like "VIDEO-PHONE" will be defined,
> and lines of two m lines (audio/video) will be grouped. And some
> attributes will be newly defined for video-phone specific use. 
> Is my understanding true?
> 
> ...
> a=group:VIDEO-PHONE 1 2
> m=audio 30000 RTP/AVP 0 4 18
> a=mid:1
> a=xxx:xxx  (<- newly defined attribute)
> m=video 30002 RTP/AVP 31 34
> a=mid:2
> a=xxx:xxx  (<- newly defined attribute)
> 
> 

As I stated, I see two options:

1. Having a general new semantics, e.g. "COMBINED-APPLICATION" to express that the answerer shall either accept or reject all grouped media streams together.

2. Having specific semantics for each combined application, e.g. VIDEO-PHONE as you propose. For each application, this may imply different additional things compared to 1, e.g. lipsynch.

> As a minimum, I guess LS(Lip Synchronization) semantic defined in
> RFC3388 could be applicable without difining a new type of grouping.
> 
> I think that video and audio stream need to be synchronized for the
> video phone service. And synchronization of video and audio 
> implies the
> existance of common codecs both of video and of audio. Considering the
> following case, I guess that a callee usually rejects the offer if it
> doesn't support either (0) of audio codec or (31) of video codec. 
> 
> I feel slightly uncomfortable about using LS semantic because 
> the usage
> of LS semantic seems like different from the problem.
> 
>  Caller                                 Callee
>    |                                       |
>    | (offer)                               |
>    | a=group:LS 1 2                        |
>    | m=audio 30000 RTP/AVP 0               |
>    | .                                     |
>    | .                                     |
>    | a=mid:1                               |
>    | m=video 30002 RTP/AVP 31              |
>    | .                                     |
>    | .                                     |
>    | a=mid:2                               |
>    |-------------------------------------->|
>    |                                       |
>    |                               (answer)|
>    |<--------------------------------------|

If you are only intrested in a combination of audio and video, LS might do, although it is not exactly what you had in mind. An answerer will probably accept or reject both media streams if lipsynch is required, because this implies the media streams are closely linked together. One the other hand, you might only want a combined acceptance or rejection of media streams without lipsynch, and then LS would not be appropriate - perhaps a bit theoretical for an audio and video combination.

> 
> > I do not know if this is worth the effort, and there would 
> certainly be
> > a backward compatibilty issue with hosts not understnding 
> the extension.
> > For those kind of hosts as callee, the caller would still need to
> > terminate the call if undesirable media combinations are selected.
> 
> I think something like SIP require header may be needed to avoid
> undesirable media combinations considering a backward compatibility.

The drawback of this solution is that an answering host supporting a combined audio-video application, but not the new semantics, would reject the offer, although it might well behave in the desired way if no SIP require header is used. It is more graceful for the offerer to terminate the session only if such an answerer indeed did an undesirable selection. 

> 
> Best regards,
> Jun Koshiko
> 
> > 
> > Best regards,
> > 
> > Th Belling
> > 
> > 
> > ----------------------------------
> > Dr. Thomas Belling
> > Siemens AG           
> > Sankt-Martin-Str. 76 
> > D-81541 M|nchen Germany
> > Com MN PG NT MN 1
> > MCH M 34 307
> > Tel     +49 89 636 75207
> > Fax     +49 89 636 75577
> > Mobile  +49 172 2974678
> > Email   Thomas.Belling@siemens.com
> > 
> > 
> > 
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> 
> ---------------------------------------------------------
> Jun KOSHIKO
> Next Generation Strategy
> Research and Development Center
> NTT-east Corporation
> 
> Telephone  +81 3 5359 5104
> Facsimile  +81 3 5359 4768
> E-mail: j.koshiko@rdc.east.ntt.co.jp
> 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> ---------------------------------------------------------
> 

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


From mmusic-bounces@ietf.org  Mon Jan 10 15:50:55 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 PAA23729
	for <mmusic-web-archive@ietf.org>; Mon, 10 Jan 2005 15:50:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co6in-0007sr-It
	for mmusic-web-archive@ietf.org; Mon, 10 Jan 2005 16:05:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co6PT-0001q9-IG; Mon, 10 Jan 2005 15:45:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Co6IZ-0006C4-7I
	for mmusic@megatron.ietf.org; Mon, 10 Jan 2005 15:37:59 -0500
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 PAA22281
	for <mmusic@ietf.org>; Mon, 10 Jan 2005 15:37:57 -0500 (EST)
Message-Id: <200501102037.PAA22281@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co6W3-0007Be-Qp
	for mmusic@ietf.org; Mon, 10 Jan 2005 15:52:07 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1Co77q-0006q6-Ts; Mon, 10 Jan 2005 14:30:59 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Belling Thomas'" <thomas.belling@siemens.com>,
        "'Jun KOSHIKO'" <j.koshiko@rdc.east.ntt.co.jp>, <mmusic@ietf.org>
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Mon, 10 Jan 2005 15:36:53 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcT3SV5NKdAH+VaKSCqLophL+2NUDQAB7MLw
In-Reply-To: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1E9@mchh266e.mchh.siemens.de>
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
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.8 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Content-Transfer-Encoding: 7bit

I think this is bordering on silliness.

Read the thread.

You have the four cases of two variables:
1) The caller offers audio and video, the called answers with both
	This works with multiple sections, choices for each from the 
	offer, a single choice for each from the answer.
2) The caller offers audio and video, the called answers audio only
	99.99% of the time, the caller will accept the call audio only.
	This is the normal case of a video phone calling an audio phone.
	You almost always want to accept the call.  If you DON'T want to
	let the call complete, the caller can reject accept the answer.  
	Done.
3) The caller offers audio, the called would like video.  This is the
	audio phone calling the video phone.  99.99% of the time, the 
	right thing is to just make an audio choice and be happy.  
	If you want to reject the call, the called party can do that.
4) The caller offers audio, the called is audio only.  No problem, 
	right?

Where is the problem?

I say this as someone who has done this.  I'm happy to show you a SIP video
phone that places and receives calls from other video phones and audio
phones.  It works very nicely, as anyone who has seen it can attest.

Lip Sync is a completely separate issue from offer/answer.  The videophone
mentioned above has perfect lip sync with no problems without any
proprietary anything.   If you want to make lip sync better, the only
thing I think you would like is to understand the absolute time difference
between the audio clock and the video clock.  In every system I've seen,
if you maintain the sync implied by the first packets, you're fine.
It would be nice to not have to assume this.  Just for reference, the above
system maintains perfect sync on calls lasting 6-8 hours.  It probably works
for longer, but I haven't looked to see if it does.

If we don't absolutely need another mechanism, please, let's not make more
work.

Brian

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Belling Thomas
> Sent: Monday, January 10, 2005 1:15 PM
> To: 'Jun KOSHIKO'; mmusic@ietf.org
> Cc: Belling Thomas
> Subject: RE: [MMUSIC] Video phone and offer/answer model
> 
> Dear Jon,
> 
> comments below
> 
> BR, Thomas
> 
> > -----Original Message-----
> > From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> > Sent: Thursday, January 06, 2005 10:41 AM
> > To: mmusic@ietf.org
> > Cc: Belling Thomas
> > Subject: Re: [MMUSIC] Video phone and offer/answer model
> >
> >
> > Hello Folks;
> >
> > Thank you for your replies.
> >
> > > Belling Thomas wrote:
> > ...
> >
> > > A clean way to resolve that would probably bee a new type
> > of grouping
> > > within the grouping framework. As a minimum, the grouping
> > would express
> > > that all media for the grouped m-lines need to be
> > established together,
> > > or none of them. As the media belong together in the sense that they
> > > need to be handled by a combined application, the more far-reaching
> > > idea would be to indicate the application in the new grouping type.
> > > This obviously is more complicated, but also more powerful,
> > and issues
> > > like how to define and/or register such applications come up.
> >
> > RFC3388, grouping framework of m line, seems like a good
> > resolution for
> > the problem. Thanks for the information.
> >
> > I imagine that your idea of indication of the application like the
> > following example. A new semantic like "VIDEO-PHONE" will be defined,
> > and lines of two m lines (audio/video) will be grouped. And some
> > attributes will be newly defined for video-phone specific use.
> > Is my understanding true?
> >
> > ...
> > a=group:VIDEO-PHONE 1 2
> > m=audio 30000 RTP/AVP 0 4 18
> > a=mid:1
> > a=xxx:xxx  (<- newly defined attribute)
> > m=video 30002 RTP/AVP 31 34
> > a=mid:2
> > a=xxx:xxx  (<- newly defined attribute)
> >
> >
> 
> As I stated, I see two options:
> 
> 1. Having a general new semantics, e.g. "COMBINED-APPLICATION" to express
> that the answerer shall either accept or reject all grouped media streams
> together.
> 
> 2. Having specific semantics for each combined application, e.g. VIDEO-
> PHONE as you propose. For each application, this may imply different
> additional things compared to 1, e.g. lipsynch.
> 
> > As a minimum, I guess LS(Lip Synchronization) semantic defined in
> > RFC3388 could be applicable without difining a new type of grouping.
> >
> > I think that video and audio stream need to be synchronized for the
> > video phone service. And synchronization of video and audio
> > implies the
> > existance of common codecs both of video and of audio. Considering the
> > following case, I guess that a callee usually rejects the offer if it
> > doesn't support either (0) of audio codec or (31) of video codec.
> >
> > I feel slightly uncomfortable about using LS semantic because
> > the usage
> > of LS semantic seems like different from the problem.
> >
> >  Caller                                 Callee
> >    |                                       |
> >    | (offer)                               |
> >    | a=group:LS 1 2                        |
> >    | m=audio 30000 RTP/AVP 0               |
> >    | .                                     |
> >    | .                                     |
> >    | a=mid:1                               |
> >    | m=video 30002 RTP/AVP 31              |
> >    | .                                     |
> >    | .                                     |
> >    | a=mid:2                               |
> >    |-------------------------------------->|
> >    |                                       |
> >    |                               (answer)|
> >    |<--------------------------------------|
> 
> If you are only intrested in a combination of audio and video, LS might
> do, although it is not exactly what you had in mind. An answerer will
> probably accept or reject both media streams if lipsynch is required,
> because this implies the media streams are closely linked together. One
> the other hand, you might only want a combined acceptance or rejection of
> media streams without lipsynch, and then LS would not be appropriate -
> perhaps a bit theoretical for an audio and video combination.
> 
> >
> > > I do not know if this is worth the effort, and there would
> > certainly be
> > > a backward compatibilty issue with hosts not understnding
> > the extension.
> > > For those kind of hosts as callee, the caller would still need to
> > > terminate the call if undesirable media combinations are selected.
> >
> > I think something like SIP require header may be needed to avoid
> > undesirable media combinations considering a backward compatibility.
> 
> The drawback of this solution is that an answering host supporting a
> combined audio-video application, but not the new semantics, would reject
> the offer, although it might well behave in the desired way if no SIP
> require header is used. It is more graceful for the offerer to terminate
> the session only if such an answerer indeed did an undesirable selection.
> 
> >
> > Best regards,
> > Jun Koshiko
> >
> > >
> > > Best regards,
> > >
> > > Th Belling
> > >
> > >
> > > ----------------------------------
> > > Dr. Thomas Belling
> > > Siemens AG
> > > Sankt-Martin-Str. 76
> > > D-81541 M|nchen Germany
> > > Com MN PG NT MN 1
> > > MCH M 34 307
> > > Tel     +49 89 636 75207
> > > Fax     +49 89 636 75577
> > > Mobile  +49 172 2974678
> > > Email   Thomas.Belling@siemens.com
> > >
> > >
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
> > ---------------------------------------------------------
> > Jun KOSHIKO
> > Next Generation Strategy
> > Research and Development Center
> > NTT-east Corporation
> >
> > Telephone  +81 3 5359 5104
> > Facsimile  +81 3 5359 4768
> > E-mail: j.koshiko@rdc.east.ntt.co.jp
> > 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> > ---------------------------------------------------------
> >
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 




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


From mmusic-bounces@ietf.org  Tue Jan 11 05:19:26 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 FAA08901
	for <mmusic-web-archive@ietf.org>; Tue, 11 Jan 2005 05:19:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoJKn-0001Dg-24
	for mmusic-web-archive@ietf.org; Tue, 11 Jan 2005 05:33:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoJ4w-0008D0-OE; Tue, 11 Jan 2005 05:16:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoJ2J-0007dX-RL
	for mmusic@megatron.ietf.org; Tue, 11 Jan 2005 05:14:03 -0500
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 FAA08568
	for <mmusic@ietf.org>; Tue, 11 Jan 2005 05:14:01 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoJG5-00018T-B6
	for mmusic@ietf.org; Tue, 11 Jan 2005 05:28:19 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0BAE0O6001084 for <mmusic@ietf.org>; Tue, 11 Jan 2005 11:14:00 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 11 Jan 2005 11:14:00 +0100
Received: from [147.214.34.55] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.55]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id ZCW23PJV; Tue, 11 Jan 2005 11:14:00 +0100
Message-ID: <41E3A6E8.5060206@ericsson.com>
Date: Tue, 11 Jan 2005 11:14:00 +0100
X-Sybari-Trust: a4d5c065 a5e9b67f a78f8e0a 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [MMUSIC] ICE issue: RTP specificity of the candidate attribute
References: <41DEBAD1.2070900@cisco.com>
In-Reply-To: <41DEBAD1.2070900@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jan 2005 10:14:00.0466 (UTC)
	FILETIME=[44E4FF20:01C4F7C6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

Hi Jonathan,

I agree that the main problem with sending RTP and RTCP is the RTT 
measurement. It really should go the same path, however I think it is 
okay with the more simplistic grouping based on priorities. If it 
actually shows that the grouping needs to be strict, an attribute using 
the candidate IDs could be used to accomplish this. So we have a way 
forward if it really would be required. However it doesn't seem that 
likely that one candidate would work and not the other.

So the proposed resolution is to write a recommendation into the ICE 
spec for RTP and RTCP to use the same priorities, so that it most likely 
that the same candidate will be used for both. Including the motivation 
that the RTT measurement would otherwise not be correct, if different 
paths where selected.

Is there agreement on this?

Cheers

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Wed Jan 12 16:43:39 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 QAA20139
	for <mmusic-web-archive@ietf.org>; Wed, 12 Jan 2005 16:43:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoqVB-0000uU-DE
	for mmusic-web-archive@ietf.org; Wed, 12 Jan 2005 16:58:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Coq2o-0004eE-Mt; Wed, 12 Jan 2005 16:28:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CopsA-0007YM-JS
	for mmusic@megatron.ietf.org; Wed, 12 Jan 2005 16:17:47 -0500
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 QAA17315
	for <mmusic@ietf.org>; Wed, 12 Jan 2005 16:17:44 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Coq65-0008Q8-1A
	for mmusic@ietf.org; Wed, 12 Jan 2005 16:32:20 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0CLHXO6005647 for <mmusic@ietf.org>; Wed, 12 Jan 2005 22:17:33 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 12 Jan 2005 22:17:32 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id YDRMB10R; Wed, 12 Jan 2005 22:17:32 +0100
Received: from ericsson.com (rvi2-94-27.sw.ericsson.se [153.88.94.27])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 9AE8718A90; Wed, 12 Jan 2005 23:17:31 +0200 (EET)
Message-ID: <41E593EB.7080901@ericsson.com>
Date: Wed, 12 Jan 2005 23:17:31 +0200
X-Sybari-Trust: adf0c541 a5e9b67f 61e0878d 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [MMUSIC] Floor-media stream mappings
References: <BDF86721.2113A%fluffy@cisco.com>
In-Reply-To: <BDF86721.2113A%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jan 2005 21:17:32.0997 (UTC)
	FILETIME=[216CDF50:01C4F8EC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: Joerg Ott <jo@tzi.uni-bremen.de>, "mmusic@ietf.org" <mmusic@ietf.org>,
        Keith Drage <drage@lucent.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: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit

Hi,

inline:

Cullen Jennings wrote:

> On 12/28/04 11:00 AM, "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
> wrote:
> 
> 
>>Folks,
>>
>>I am working on a new version of the draft below, which will be an
>>MMUSIC WG item as agreed in our last meeting in DC.
>>
>>http://www.ietf.org/internet-drafts/draft-camarillo-mmusic-sdp-bfcp-00.txt
>>
>>We need a means to provide clients with the Floor IDs to be used in the
>>conference and with the mapping of  each Floor ID with one or more media
>>streams. For example, floor ID 123 maps to the media stream whose media
>>label is 456.
>>
>>a=floorid:123 m-stream:456
>>
> 
> 
> Just to make sure I understand - I assume that several floors could map to
> one media stream

Yes. The syntax would be:

a=floorid:123 m-stream:456
a=floorid:111 m-stream:456

> and a single floor could also map to multiple media stream
> (like audio and video).

Yes. The syntax would be:

a=floorid:123 m-stream:456 779


>>We would like to get feedback on a couple of issues:
>>
>>1) Do we want to include human readable information about the floors
>>encoded in the SDP? (e.g., "request this floor if you want to make a
>>comment on the issue being discussed" or "request this floor if you want
>>to bring up a new issue to be discussed")
>>
> 
> 
> no - the human language issues make me not want to do this. I'm fine with a
> a convention that if their is a floor, you probably need to request it if
> you want anyone to pay intention to your media. Clearly your second example
> would not follow this but I think there are many ways other that SDP that
> users could get the idea of what to floor was used for. I don't find these
> human readable things in SDP very useful in practice.
> 
> That said, I don't feel strongly about this - it the human readable
> description is never used, it does no harm. It could also be added later if
> it was needed. 

I do not feel strongly about this either, but, in any case, we can 
always add it later if we see the need (as you point out). So, I will 
not include it in the draft.

> 
> 
>>2) Do we want to allow the syntax of the 'floorid' attribute to express
>>Floor IDs that do not map to any media stream? If the answer to both 1)
>>and 2) is yes, we could use the floor control protocol to moderate
>>face-to-face meetings where the media does not traverse any mixer, for
>>example.
>>
> 
> 
> yes 

I also think this is useful. We can use the following syntax:

a=floorid:123

> 
> And would also like to consider being able to specify a floor id when no
> media stream exists but where the media stream and association to floor will
> be added in a future SDP. It may be the requesting of the floor that causes
> the creation of the media stream.

The syntax above would cover this as well.

Thanks,

Gonzalo



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


From mmusic-bounces@ietf.org  Thu Jan 13 05:49:05 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 FAA24935
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 05:49:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cp2lZ-00087E-6N
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 06:03:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cp2ST-0001mI-KU; Thu, 13 Jan 2005 05:44:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cp2MS-0000Q4-Vq
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 05:37:53 -0500
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 FAA24139
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 05:37:49 -0500 (EST)
Received: from eastmail2.ntt-east.co.jp ([202.229.5.45]
	helo=evx2.enoc.east.ntt.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cp2ae-0007pf-UR
	for mmusic@ietf.org; Thu, 13 Jan 2005 05:52:33 -0500
Received: from emix2.enoc.east.ntt.co.jp 
	by evx2.enoc.east.ntt.co.jp with ESMTP id j0DAb2p29460;
	Thu, 13 Jan 2005 19:37:03 +0900 (JST)
Received: from cip9.noc.east.ntt.co.jp 
	by emix2.enoc.east.ntt.co.jp with ESMTP id j0DAb2c16572;
	Thu, 13 Jan 2005 19:37:02 +0900 (JST)
Received: from [10.35.200.201] ([10.35.200.201])
	by cip9.noc.east.ntt.co.jp (MOS 3.4.6-GR) with ESMTP id AVD00438;
	Thu, 13 Jan 2005 19:37:01 +0900 (JST)
Date: Thu, 13 Jan 2005 19:37:02 +0900
From: Jun KOSHIKO <j.koshiko@rdc.east.ntt.co.jp>
To: <mmusic@ietf.org>
Subject: Re: [MMUSIC] Video phone and offer/answer model
In-Reply-To: <200501102037.j0AKbFx01173@emox1.enoc.east.ntt.co.jp>
References: <9A59FBE53A4DD74B9BCD5E44AFB668A9012CC1E9@mchh266e.mchh.siemens.de>
	<200501102037.j0AKbFx01173@emox1.enoc.east.ntt.co.jp>
Message-Id: <20050113191650.E1BB.J.KOSHIKO@rdc.east.ntt.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.11.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935
Content-Transfer-Encoding: 7bit
Cc: "'Belling Thomas'" <thomas.belling@siemens.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: 8d89ee9312a95de8ee48d1c94511f1bb
Content-Transfer-Encoding: 7bit

Thank you for your reply.

Brian Rosen wrote:
> I think this is bordering on silliness.
> 
> Read the thread.
> 
> You have the four cases of two variables:
> 1) The caller offers audio and video, the called answers with both
> 	This works with multiple sections, choices for each from the 
> 	offer, a single choice for each from the answer.
> 2) The caller offers audio and video, the called answers audio only
> 	99.99% of the time, the caller will accept the call audio only.
> 	This is the normal case of a video phone calling an audio phone.
> 	You almost always want to accept the call.  If you DON'T want to
> 	let the call complete, the caller can reject accept the answer.  
> 	Done.
> 3) The caller offers audio, the called would like video.  This is the
> 	audio phone calling the video phone.  99.99% of the time, the 
> 	right thing is to just make an audio choice and be happy.  
> 	If you want to reject the call, the called party can do that.
> 4) The caller offers audio, the called is audio only.  No problem, 
> 	right?
> 
> Where is the problem?

I can grasp the understanding for what you are saying. Now I would like
to consider about human interface. For example, in the following case,
if the caller reject the offer which includes audio and doesn't include
video, although the callee's phone ring and the it's hung up, the call
will be cancelled. This way seems unfriendly interface, I think.

If the caller can group m lines of video and audio and the callee
understand it, the callee can reject the offer to avoid such a situation.
Definitely, whether the situation can be avoided or not depends on the
implementation of the device of callee.  If the callee which doesn't
understand the grouping attribute of m lines will accept the offer, and
then the call will be cancelled after the callee's phone rang and the
user got the phone up, naturally.

   Caller                                  Callee
(Video phone)                          (Audio Phone)
      |                                      |
      | INVITE with SDP(video/audio)         |
      |------------------------------------->|
      | 180 Ringing without SDP              |
      |<-------------------------------------| Phone Ring!!
      | 200 OK with SDP(audio)               |
      |<-------------------------------------| Hung up!!
      | ACK                                  |
      |------------------------------------->|
      | BYE                                  |
      |------------------------------------->| Call cancelled!!
      | 200 OK                               |
      |<-------------------------------------|
      | ACK                                  |
      |------------------------------------->|
      |                                      |

Best Regards,
Jun Koshiko

> I say this as someone who has done this.  I'm happy to show you a SIP video
> phone that places and receives calls from other video phones and audio
> phones.  It works very nicely, as anyone who has seen it can attest.
>
> Lip Sync is a completely separate issue from offer/answer.  The videophone
> mentioned above has perfect lip sync with no problems without any
> proprietary anything.   If you want to make lip sync better, the only
> thing I think you would like is to understand the absolute time difference
> between the audio clock and the video clock.  In every system I've seen,
> if you maintain the sync implied by the first packets, you're fine.
> It would be nice to not have to assume this.  Just for reference, the above
> system maintains perfect sync on calls lasting 6-8 hours.  It probably works
> for longer, but I haven't looked to see if it does.
>
> If we don't absolutely need another mechanism, please, let's not make more
> work.
> 
> Brian
> 
> > -----Original Message-----
> > From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> > Of Belling Thomas
> > Sent: Monday, January 10, 2005 1:15 PM
> > To: 'Jun KOSHIKO'; mmusic@ietf.org
> > Cc: Belling Thomas
> > Subject: RE: [MMUSIC] Video phone and offer/answer model
> > 
> > Dear Jon,
> > 
> > comments below
> > 
> > BR, Thomas
> > 
> > > -----Original Message-----
> > > From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> > > Sent: Thursday, January 06, 2005 10:41 AM
> > > To: mmusic@ietf.org
> > > Cc: Belling Thomas
> > > Subject: Re: [MMUSIC] Video phone and offer/answer model
> > >
> > >
> > > Hello Folks;
> > >
> > > Thank you for your replies.
> > >
> > > > Belling Thomas wrote:
> > > ...
> > >
> > > > A clean way to resolve that would probably bee a new type
> > > of grouping
> > > > within the grouping framework. As a minimum, the grouping
> > > would express
> > > > that all media for the grouped m-lines need to be
> > > established together,
> > > > or none of them. As the media belong together in the sense that they
> > > > need to be handled by a combined application, the more far-reaching
> > > > idea would be to indicate the application in the new grouping type.
> > > > This obviously is more complicated, but also more powerful,
> > > and issues
> > > > like how to define and/or register such applications come up.
> > >
> > > RFC3388, grouping framework of m line, seems like a good
> > > resolution for
> > > the problem. Thanks for the information.
> > >
> > > I imagine that your idea of indication of the application like the
> > > following example. A new semantic like "VIDEO-PHONE" will be defined,
> > > and lines of two m lines (audio/video) will be grouped. And some
> > > attributes will be newly defined for video-phone specific use.
> > > Is my understanding true?
> > >
> > > ...
> > > a=group:VIDEO-PHONE 1 2
> > > m=audio 30000 RTP/AVP 0 4 18
> > > a=mid:1
> > > a=xxx:xxx  (<- newly defined attribute)
> > > m=video 30002 RTP/AVP 31 34
> > > a=mid:2
> > > a=xxx:xxx  (<- newly defined attribute)
> > >
> > >
> > 
> > As I stated, I see two options:
> > 
> > 1. Having a general new semantics, e.g. "COMBINED-APPLICATION" to express
> > that the answerer shall either accept or reject all grouped media streams
> > together.
> > 
> > 2. Having specific semantics for each combined application, e.g. VIDEO-
> > PHONE as you propose. For each application, this may imply different
> > additional things compared to 1, e.g. lipsynch.
> > 
> > > As a minimum, I guess LS(Lip Synchronization) semantic defined in
> > > RFC3388 could be applicable without difining a new type of grouping.
> > >
> > > I think that video and audio stream need to be synchronized for the
> > > video phone service. And synchronization of video and audio
> > > implies the
> > > existance of common codecs both of video and of audio. Considering the
> > > following case, I guess that a callee usually rejects the offer if it
> > > doesn't support either (0) of audio codec or (31) of video codec.
> > >
> > > I feel slightly uncomfortable about using LS semantic because
> > > the usage
> > > of LS semantic seems like different from the problem.
> > >
> > >  Caller                                 Callee
> > >    |                                       |
> > >    | (offer)                               |
> > >    | a=group:LS 1 2                        |
> > >    | m=audio 30000 RTP/AVP 0               |
> > >    | .                                     |
> > >    | .                                     |
> > >    | a=mid:1                               |
> > >    | m=video 30002 RTP/AVP 31              |
> > >    | .                                     |
> > >    | .                                     |
> > >    | a=mid:2                               |
> > >    |-------------------------------------->|
> > >    |                                       |
> > >    |                               (answer)|
> > >    |<--------------------------------------|
> > 
> > If you are only intrested in a combination of audio and video, LS might
> > do, although it is not exactly what you had in mind. An answerer will
> > probably accept or reject both media streams if lipsynch is required,
> > because this implies the media streams are closely linked together. One
> > the other hand, you might only want a combined acceptance or rejection of
> > media streams without lipsynch, and then LS would not be appropriate -
> > perhaps a bit theoretical for an audio and video combination.
> > 
> > >
> > > > I do not know if this is worth the effort, and there would
> > > certainly be
> > > > a backward compatibilty issue with hosts not understnding
> > > the extension.
> > > > For those kind of hosts as callee, the caller would still need to
> > > > terminate the call if undesirable media combinations are selected.
> > >
> > > I think something like SIP require header may be needed to avoid
> > > undesirable media combinations considering a backward compatibility.
> > 
> > The drawback of this solution is that an answering host supporting a
> > combined audio-video application, but not the new semantics, would reject
> > the offer, although it might well behave in the desired way if no SIP
> > require header is used. It is more graceful for the offerer to terminate
> > the session only if such an answerer indeed did an undesirable selection.
> > 
> > >
> > > Best regards,
> > > Jun Koshiko
> > >
> > > >
> > > > Best regards,
> > > >
> > > > Th Belling
> > > >
> > > >
> > > > ----------------------------------
> > > > Dr. Thomas Belling
> > > > Siemens AG
> > > > Sankt-Martin-Str. 76
> > > > D-81541 M|nchen Germany
> > > > Com MN PG NT MN 1
> > > > MCH M 34 307
> > > > Tel     +49 89 636 75207
> > > > Fax     +49 89 636 75577
> > > > Mobile  +49 172 2974678
> > > > Email   Thomas.Belling@siemens.com
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > mmusic mailing list
> > > > mmusic@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> > > ---------------------------------------------------------
> > > Jun KOSHIKO
> > > Next Generation Strategy
> > > Research and Development Center
> > > NTT-east Corporation
> > >
> > > Telephone  +81 3 5359 5104
> > > Facsimile  +81 3 5359 4768
> > > E-mail: j.koshiko@rdc.east.ntt.co.jp
> > > 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> > > ---------------------------------------------------------
> > >
> > 
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> > 
> 
> 

---------------------------------------------------------
Jun KOSHIKO
Next Generation Strategy
Research and Development Center
NTT-east Corporation

Telephone  +81 3 5359 5104
Facsimile  +81 3 5359 4768
E-mail: j.koshiko@rdc.east.ntt.co.jp
19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
---------------------------------------------------------


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


From mmusic-bounces@ietf.org  Thu Jan 13 06:38:26 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 GAA29083
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 06:38:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cp3XL-0000o8-F1
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 06:53:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cp3Fr-00068Y-9q; Thu, 13 Jan 2005 06:35:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cp3Br-0005bl-Cz
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 06:30:59 -0500
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 GAA28676
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 06:30:56 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cp3Q3-0000gE-Oe
	for mmusic@ietf.org; Thu, 13 Jan 2005 06:45:41 -0500
Received: from esealmw127.eemea.ericsson.se ([153.88.254.122])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0DBUuh7029711
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 12:30:56 +0100 (MET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 13 Jan 2005 12:30:56 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.13]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 13 Jan 2005 12:30:55 +0100
Received: from ericsson.com (rvi2-94-80.sw.ericsson.se [153.88.94.80])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id EBB4D18A90
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 13:30:54 +0200 (EET)
Message-ID: <41E65BEE.8020809@ericsson.com>
Date: Thu, 13 Jan 2005 13:30:54 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Jan 2005 11:30:55.0505 (UTC)
	FILETIME=[587F9010:01C4F963]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] SDP format for BFCP
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: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

Folks,

I have just submitted a new revision of the SDP format for BFCP. Until 
it appears in the archives you can fetch it from:

http://users.piuha.net/gonzalo/temp/draft-ietf-mmusic-sdp-bfcp-00.txt

Your comments are welcome.

Thanks,

Gonzalo


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


From mmusic-bounces@ietf.org  Thu Jan 13 09:45:31 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 JAA15112
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 09:45:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cp6SO-0005rs-PV
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 10:00:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cp67X-0004Xl-AR; Thu, 13 Jan 2005 09:38:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cp5sT-0006ai-Bz
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 09:23:09 -0500
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 JAA13338
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 09:23:07 -0500 (EST)
Message-Id: <200501131423.JAA13338@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cp66Y-0005IH-4z
	for mmusic@ietf.org; Thu, 13 Jan 2005 09:37:52 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1Cp6hQ-0003v2-3k; Thu, 13 Jan 2005 08:15:48 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>,
        "'Cullen Jennings'" <fluffy@cisco.com>
Subject: RE: [MMUSIC] Floor-media stream mappings
Date: Thu, 13 Jan 2005 09:21:59 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcT490Hu9Z5uJF/9R6+2pwlwVIYoeAAgvm7g
In-Reply-To: <41E593EB.7080901@ericsson.com>
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: 7bit
Cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, mmusic@ietf.org,
        "'Keith Drage'" <drage@lucent.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.8 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: 7bit

I will again say that I think this is 100% overlap with XCON templates and
"mixing patterns".  It is impossible to use a simple relationship between a
media stream and a floor to understand what the heck the floor does.  The
information needed is in the XCON template and text description.  Allowing
the relationship to also be expressed with SDP leads to conflicts where one
mechanism claims one thing and another mechanism claims another.

Yes, I'm aware of POC work and deadlines, but a bad idea is a bad idea, and
I think this is a bad idea.

Brian

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
> Of Gonzalo Camarillo
> Sent: Wednesday, January 12, 2005 4:18 PM
> To: Cullen Jennings
> Cc: Joerg Ott; mmusic@ietf.org; Keith Drage
> Subject: Re: [MMUSIC] Floor-media stream mappings
> 
> Hi,
> 
> inline:
> 
> Cullen Jennings wrote:
> 
> > On 12/28/04 11:00 AM, "Gonzalo Camarillo"
> <Gonzalo.Camarillo@ericsson.com>
> > wrote:
> >
> >
> >>Folks,
> >>
> >>I am working on a new version of the draft below, which will be an
> >>MMUSIC WG item as agreed in our last meeting in DC.
> >>
> >>http://www.ietf.org/internet-drafts/draft-camarillo-mmusic-sdp-bfcp-
> 00.txt
> >>
> >>We need a means to provide clients with the Floor IDs to be used in the
> >>conference and with the mapping of  each Floor ID with one or more media
> >>streams. For example, floor ID 123 maps to the media stream whose media
> >>label is 456.
> >>
> >>a=floorid:123 m-stream:456
> >>
> >
> >
> > Just to make sure I understand - I assume that several floors could map
> to
> > one media stream
> 
> Yes. The syntax would be:
> 
> a=floorid:123 m-stream:456
> a=floorid:111 m-stream:456
> 
> > and a single floor could also map to multiple media stream
> > (like audio and video).
> 
> Yes. The syntax would be:
> 
> a=floorid:123 m-stream:456 779
> 
> 
> >>We would like to get feedback on a couple of issues:
> >>
> >>1) Do we want to include human readable information about the floors
> >>encoded in the SDP? (e.g., "request this floor if you want to make a
> >>comment on the issue being discussed" or "request this floor if you want
> >>to bring up a new issue to be discussed")
> >>
> >
> >
> > no - the human language issues make me not want to do this. I'm fine
> with a
> > a convention that if their is a floor, you probably need to request it
> if
> > you want anyone to pay intention to your media. Clearly your second
> example
> > would not follow this but I think there are many ways other that SDP
> that
> > users could get the idea of what to floor was used for. I don't find
> these
> > human readable things in SDP very useful in practice.
> >
> > That said, I don't feel strongly about this - it the human readable
> > description is never used, it does no harm. It could also be added later
> if
> > it was needed.
> 
> I do not feel strongly about this either, but, in any case, we can
> always add it later if we see the need (as you point out). So, I will
> not include it in the draft.
> 
> >
> >
> >>2) Do we want to allow the syntax of the 'floorid' attribute to express
> >>Floor IDs that do not map to any media stream? If the answer to both 1)
> >>and 2) is yes, we could use the floor control protocol to moderate
> >>face-to-face meetings where the media does not traverse any mixer, for
> >>example.
> >>
> >
> >
> > yes
> 
> I also think this is useful. We can use the following syntax:
> 
> a=floorid:123
> 
> >
> > And would also like to consider being able to specify a floor id when no
> > media stream exists but where the media stream and association to floor
> will
> > be added in a future SDP. It may be the requesting of the floor that
> causes
> > the creation of the media stream.
> 
> The syntax above would cover this as well.
> 
> Thanks,
> 
> 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  Thu Jan 13 10:12:13 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 KAA17105
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 10:12:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cp6sF-0006R5-1x
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 10:26:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cp6QJ-0003rH-IC; Thu, 13 Jan 2005 09:58:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cp6Fi-0008RJ-T3
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 09:47:11 -0500
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 JAA15236
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 09:47:08 -0500 (EST)
Message-Id: <200501131447.JAA15236@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cp6Tx-0005uH-Ot
	for mmusic@ietf.org; Thu, 13 Jan 2005 10:01:54 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1Cp74v-0005Au-Lk; Thu, 13 Jan 2005 08:40:07 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Jun KOSHIKO'" <j.koshiko@rdc.east.ntt.co.jp>, <mmusic@ietf.org>
Subject: RE: [MMUSIC] Video phone and offer/answer model
Date: Thu, 13 Jan 2005 09:46:20 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcT5Y3TOFM4yrXFqRVawNOYI1BFXAQAF/zJA
In-Reply-To: <20050113191650.E1BB.J.KOSHIKO@rdc.east.ntt.co.jp>
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fac892abe0c719c7bb99f6e7c710cdae
Content-Transfer-Encoding: 7bit
Cc: "'Belling Thomas'" <thomas.belling@siemens.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.8 (/)
X-Scan-Signature: bc102ac530ba955ef81f1f75b8bebe44
Content-Transfer-Encoding: 7bit

I think this is a poor system design.  This is scenario 2 where the caller
offers audio and video, but the called party only has audio, and you want
refuse the answer because the caller insists on video.  Your problem is that
the called party doesn't know it's going to be refused, so it begins
alerting.  The call is cancelled after the alerting begins, and you don't
like that.

I'd prefer your caller to accept the call audio only.  That's what all the
systems I've ever seen would do.  I've never seen a system refuse a call if
it didn't offer/answer video.  In the systems I'm most familiar with, this
scenario occurs even though the called party has video capability.  It
occurs when the called user disables the video, and it also occurs when the
local environment can't handle the bandwidth implied.  The caller should not
have an expectation that everyone he calls will accept video, even if he
knows they have the capability to.  

I think we have so much work to do, and this requirement is of so little
interest, that we should not spend any time on it.  If there are lots of
systems that need to be able to refuse a call if the caller can't handle
video, I'd like to hear about them.

Brian





> -----Original Message-----
> From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> Sent: Thursday, January 13, 2005 5:37 AM
> To: mmusic@ietf.org
> Cc: 'Belling Thomas'; Brian Rosen
> Subject: Re: [MMUSIC] Video phone and offer/answer model
> 
> Thank you for your reply.
> 
> Brian Rosen wrote:
> > I think this is bordering on silliness.
> >
> > Read the thread.
> >
> > You have the four cases of two variables:
> > 1) The caller offers audio and video, the called answers with both
> > 	This works with multiple sections, choices for each from the
> > 	offer, a single choice for each from the answer.
> > 2) The caller offers audio and video, the called answers audio only
> > 	99.99% of the time, the caller will accept the call audio only.
> > 	This is the normal case of a video phone calling an audio phone.
> > 	You almost always want to accept the call.  If you DON'T want to
> > 	let the call complete, the caller can reject accept the answer.
> > 	Done.
> > 3) The caller offers audio, the called would like video.  This is the
> > 	audio phone calling the video phone.  99.99% of the time, the
> > 	right thing is to just make an audio choice and be happy.
> > 	If you want to reject the call, the called party can do that.
> > 4) The caller offers audio, the called is audio only.  No problem,
> > 	right?
> >
> > Where is the problem?
> 
> I can grasp the understanding for what you are saying. Now I would like
> to consider about human interface. For example, in the following case,
> if the caller reject the offer which includes audio and doesn't include
> video, although the callee's phone ring and the it's hung up, the call
> will be cancelled. This way seems unfriendly interface, I think.
> 
> If the caller can group m lines of video and audio and the callee
> understand it, the callee can reject the offer to avoid such a situation.
> Definitely, whether the situation can be avoided or not depends on the
> implementation of the device of callee.  If the callee which doesn't
> understand the grouping attribute of m lines will accept the offer, and
> then the call will be cancelled after the callee's phone rang and the
> user got the phone up, naturally.
> 
>    Caller                                  Callee
> (Video phone)                          (Audio Phone)
>       |                                      |
>       | INVITE with SDP(video/audio)         |
>       |------------------------------------->|
>       | 180 Ringing without SDP              |
>       |<-------------------------------------| Phone Ring!!
>       | 200 OK with SDP(audio)               |
>       |<-------------------------------------| Hung up!!
>       | ACK                                  |
>       |------------------------------------->|
>       | BYE                                  |
>       |------------------------------------->| Call cancelled!!
>       | 200 OK                               |
>       |<-------------------------------------|
>       | ACK                                  |
>       |------------------------------------->|
>       |                                      |
> 
> Best Regards,
> Jun Koshiko
> 
> > I say this as someone who has done this.  I'm happy to show you a SIP
> video
> > phone that places and receives calls from other video phones and audio
> > phones.  It works very nicely, as anyone who has seen it can attest.
> >
> > Lip Sync is a completely separate issue from offer/answer.  The
> videophone
> > mentioned above has perfect lip sync with no problems without any
> > proprietary anything.   If you want to make lip sync better, the only
> > thing I think you would like is to understand the absolute time
> difference
> > between the audio clock and the video clock.  In every system I've seen,
> > if you maintain the sync implied by the first packets, you're fine.
> > It would be nice to not have to assume this.  Just for reference, the
> above
> > system maintains perfect sync on calls lasting 6-8 hours.  It probably
> works
> > for longer, but I haven't looked to see if it does.
> >
> > If we don't absolutely need another mechanism, please, let's not make
> more
> > work.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf
> > > Of Belling Thomas
> > > Sent: Monday, January 10, 2005 1:15 PM
> > > To: 'Jun KOSHIKO'; mmusic@ietf.org
> > > Cc: Belling Thomas
> > > Subject: RE: [MMUSIC] Video phone and offer/answer model
> > >
> > > Dear Jon,
> > >
> > > comments below
> > >
> > > BR, Thomas
> > >
> > > > -----Original Message-----
> > > > From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> > > > Sent: Thursday, January 06, 2005 10:41 AM
> > > > To: mmusic@ietf.org
> > > > Cc: Belling Thomas
> > > > Subject: Re: [MMUSIC] Video phone and offer/answer model
> > > >
> > > >
> > > > Hello Folks;
> > > >
> > > > Thank you for your replies.
> > > >
> > > > > Belling Thomas wrote:
> > > > ...
> > > >
> > > > > A clean way to resolve that would probably bee a new type
> > > > of grouping
> > > > > within the grouping framework. As a minimum, the grouping
> > > > would express
> > > > > that all media for the grouped m-lines need to be
> > > > established together,
> > > > > or none of them. As the media belong together in the sense that
> they
> > > > > need to be handled by a combined application, the more far-
> reaching
> > > > > idea would be to indicate the application in the new grouping
> type.
> > > > > This obviously is more complicated, but also more powerful,
> > > > and issues
> > > > > like how to define and/or register such applications come up.
> > > >
> > > > RFC3388, grouping framework of m line, seems like a good
> > > > resolution for
> > > > the problem. Thanks for the information.
> > > >
> > > > I imagine that your idea of indication of the application like the
> > > > following example. A new semantic like "VIDEO-PHONE" will be
> defined,
> > > > and lines of two m lines (audio/video) will be grouped. And some
> > > > attributes will be newly defined for video-phone specific use.
> > > > Is my understanding true?
> > > >
> > > > ...
> > > > a=group:VIDEO-PHONE 1 2
> > > > m=audio 30000 RTP/AVP 0 4 18
> > > > a=mid:1
> > > > a=xxx:xxx  (<- newly defined attribute)
> > > > m=video 30002 RTP/AVP 31 34
> > > > a=mid:2
> > > > a=xxx:xxx  (<- newly defined attribute)
> > > >
> > > >
> > >
> > > As I stated, I see two options:
> > >
> > > 1. Having a general new semantics, e.g. "COMBINED-APPLICATION" to
> express
> > > that the answerer shall either accept or reject all grouped media
> streams
> > > together.
> > >
> > > 2. Having specific semantics for each combined application, e.g.
> VIDEO-
> > > PHONE as you propose. For each application, this may imply different
> > > additional things compared to 1, e.g. lipsynch.
> > >
> > > > As a minimum, I guess LS(Lip Synchronization) semantic defined in
> > > > RFC3388 could be applicable without difining a new type of grouping.
> > > >
> > > > I think that video and audio stream need to be synchronized for the
> > > > video phone service. And synchronization of video and audio
> > > > implies the
> > > > existance of common codecs both of video and of audio. Considering
> the
> > > > following case, I guess that a callee usually rejects the offer if
> it
> > > > doesn't support either (0) of audio codec or (31) of video codec.
> > > >
> > > > I feel slightly uncomfortable about using LS semantic because
> > > > the usage
> > > > of LS semantic seems like different from the problem.
> > > >
> > > >  Caller                                 Callee
> > > >    |                                       |
> > > >    | (offer)                               |
> > > >    | a=group:LS 1 2                        |
> > > >    | m=audio 30000 RTP/AVP 0               |
> > > >    | .                                     |
> > > >    | .                                     |
> > > >    | a=mid:1                               |
> > > >    | m=video 30002 RTP/AVP 31              |
> > > >    | .                                     |
> > > >    | .                                     |
> > > >    | a=mid:2                               |
> > > >    |-------------------------------------->|
> > > >    |                                       |
> > > >    |                               (answer)|
> > > >    |<--------------------------------------|
> > >
> > > If you are only intrested in a combination of audio and video, LS
> might
> > > do, although it is not exactly what you had in mind. An answerer will
> > > probably accept or reject both media streams if lipsynch is required,
> > > because this implies the media streams are closely linked together.
> One
> > > the other hand, you might only want a combined acceptance or rejection
> of
> > > media streams without lipsynch, and then LS would not be appropriate -
> > > perhaps a bit theoretical for an audio and video combination.
> > >
> > > >
> > > > > I do not know if this is worth the effort, and there would
> > > > certainly be
> > > > > a backward compatibilty issue with hosts not understnding
> > > > the extension.
> > > > > For those kind of hosts as callee, the caller would still need to
> > > > > terminate the call if undesirable media combinations are selected.
> > > >
> > > > I think something like SIP require header may be needed to avoid
> > > > undesirable media combinations considering a backward compatibility.
> > >
> > > The drawback of this solution is that an answering host supporting a
> > > combined audio-video application, but not the new semantics, would
> reject
> > > the offer, although it might well behave in the desired way if no SIP
> > > require header is used. It is more graceful for the offerer to
> terminate
> > > the session only if such an answerer indeed did an undesirable
> selection.
> > >
> > > >
> > > > Best regards,
> > > > Jun Koshiko
> > > >
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Th Belling
> > > > >
> > > > >
> > > > > ----------------------------------
> > > > > Dr. Thomas Belling
> > > > > Siemens AG
> > > > > Sankt-Martin-Str. 76
> > > > > D-81541 M|nchen Germany
> > > > > Com MN PG NT MN 1
> > > > > MCH M 34 307
> > > > > Tel     +49 89 636 75207
> > > > > Fax     +49 89 636 75577
> > > > > Mobile  +49 172 2974678
> > > > > Email   Thomas.Belling@siemens.com
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > mmusic mailing list
> > > > > mmusic@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > >
> > > > ---------------------------------------------------------
> > > > Jun KOSHIKO
> > > > Next Generation Strategy
> > > > Research and Development Center
> > > > NTT-east Corporation
> > > >
> > > > Telephone  +81 3 5359 5104
> > > > Facsimile  +81 3 5359 4768
> > > > E-mail: j.koshiko@rdc.east.ntt.co.jp
> > > > 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> > > > ---------------------------------------------------------
> > > >
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> >
> >
> 
> ---------------------------------------------------------
> Jun KOSHIKO
> Next Generation Strategy
> Research and Development Center
> NTT-east Corporation
> 
> Telephone  +81 3 5359 5104
> Facsimile  +81 3 5359 4768
> E-mail: j.koshiko@rdc.east.ntt.co.jp
> 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> ---------------------------------------------------------
> 
> 




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


From mmusic-bounces@ietf.org  Thu Jan 13 13:12:38 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 NAA29527
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 13:12:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cp9gs-0001vJ-UG
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 13:27:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cp9RH-0002sl-4h; Thu, 13 Jan 2005 13:11:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cp9QQ-0002T8-My
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 13:10:29 -0500
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 NAA29341
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 13:10:22 -0500 (EST)
Received: from bzq-179-41-2.cust.bezeqint.net ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cp9ec-0001pQ-8Z
	for mmusic@ietf.org; Thu, 13 Jan 2005 13:25:10 -0500
Content-class: urn:content-classes:message
Subject: RE: [MMUSIC] Video phone and offer/answer model
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 13 Jan 2005 19:43:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <144ED8561CE90C41A3E5908EDECE315CBF263D@IsrExch01.israel.polycom.com>
Thread-Topic: [MMUSIC] Video phone and offer/answer model
Thread-Index: AcT5Y3TOFM4yrXFqRVawNOYI1BFXAQAF/zJAAAbk50A=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Brian Rosen" <br@brianrosen.net>,
        "Jun KOSHIKO" <j.koshiko@rdc.east.ntt.co.jp>, <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: da41e01217ab11ad82db577473e913ae
Content-Transfer-Encoding: quoted-printable
Cc: Belling Thomas <thomas.belling@siemens.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: abb8110dde048486ea2be9c769692569
Content-Transfer-Encoding: quoted-printable

Hi,
I would like to add that the caller can use caller prefs (RFC3841) to
say that he prefers to get the called party video phone if he has one
Roni Even

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Brian Rosen
Sent: Thursday, January 13, 2005 4:46 PM
To: 'Jun KOSHIKO'; mmusic@ietf.org
Cc: 'Belling Thomas'
Subject: RE: [MMUSIC] Video phone and offer/answer model

I think this is a poor system design.  This is scenario 2 where the
caller
offers audio and video, but the called party only has audio, and you
want
refuse the answer because the caller insists on video.  Your problem is
that
the called party doesn't know it's going to be refused, so it begins
alerting.  The call is cancelled after the alerting begins, and you
don't
like that.

I'd prefer your caller to accept the call audio only.  That's what all
the
systems I've ever seen would do.  I've never seen a system refuse a call
if
it didn't offer/answer video.  In the systems I'm most familiar with,
this
scenario occurs even though the called party has video capability.  It
occurs when the called user disables the video, and it also occurs when
the
local environment can't handle the bandwidth implied.  The caller should
not
have an expectation that everyone he calls will accept video, even if he
knows they have the capability to. =20

I think we have so much work to do, and this requirement is of so little
interest, that we should not spend any time on it.  If there are lots of
systems that need to be able to refuse a call if the caller can't handle
video, I'd like to hear about them.

Brian





> -----Original Message-----
> From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> Sent: Thursday, January 13, 2005 5:37 AM
> To: mmusic@ietf.org
> Cc: 'Belling Thomas'; Brian Rosen
> Subject: Re: [MMUSIC] Video phone and offer/answer model
>=20
> Thank you for your reply.
>=20
> Brian Rosen wrote:
> > I think this is bordering on silliness.
> >
> > Read the thread.
> >
> > You have the four cases of two variables:
> > 1) The caller offers audio and video, the called answers with both
> > 	This works with multiple sections, choices for each from the
> > 	offer, a single choice for each from the answer.
> > 2) The caller offers audio and video, the called answers audio only
> > 	99.99% of the time, the caller will accept the call audio only.
> > 	This is the normal case of a video phone calling an audio phone.
> > 	You almost always want to accept the call.  If you DON'T want to
> > 	let the call complete, the caller can reject accept the answer.
> > 	Done.
> > 3) The caller offers audio, the called would like video.  This is
the
> > 	audio phone calling the video phone.  99.99% of the time, the
> > 	right thing is to just make an audio choice and be happy.
> > 	If you want to reject the call, the called party can do that.
> > 4) The caller offers audio, the called is audio only.  No problem,
> > 	right?
> >
> > Where is the problem?
>=20
> I can grasp the understanding for what you are saying. Now I would
like
> to consider about human interface. For example, in the following case,
> if the caller reject the offer which includes audio and doesn't
include
> video, although the callee's phone ring and the it's hung up, the call
> will be cancelled. This way seems unfriendly interface, I think.
>=20
> If the caller can group m lines of video and audio and the callee
> understand it, the callee can reject the offer to avoid such a
situation.
> Definitely, whether the situation can be avoided or not depends on the
> implementation of the device of callee.  If the callee which doesn't
> understand the grouping attribute of m lines will accept the offer,
and
> then the call will be cancelled after the callee's phone rang and the
> user got the phone up, naturally.
>=20
>    Caller                                  Callee
> (Video phone)                          (Audio Phone)
>       |                                      |
>       | INVITE with SDP(video/audio)         |
>       |------------------------------------->|
>       | 180 Ringing without SDP              |
>       |<-------------------------------------| Phone Ring!!
>       | 200 OK with SDP(audio)               |
>       |<-------------------------------------| Hung up!!
>       | ACK                                  |
>       |------------------------------------->|
>       | BYE                                  |
>       |------------------------------------->| Call cancelled!!
>       | 200 OK                               |
>       |<-------------------------------------|
>       | ACK                                  |
>       |------------------------------------->|
>       |                                      |
>=20
> Best Regards,
> Jun Koshiko
>=20
> > I say this as someone who has done this.  I'm happy to show you a
SIP
> video
> > phone that places and receives calls from other video phones and
audio
> > phones.  It works very nicely, as anyone who has seen it can attest.
> >
> > Lip Sync is a completely separate issue from offer/answer.  The
> videophone
> > mentioned above has perfect lip sync with no problems without any
> > proprietary anything.   If you want to make lip sync better, the
only
> > thing I think you would like is to understand the absolute time
> difference
> > between the audio clock and the video clock.  In every system I've
seen,
> > if you maintain the sync implied by the first packets, you're fine.
> > It would be nice to not have to assume this.  Just for reference,
the
> above
> > system maintains perfect sync on calls lasting 6-8 hours.  It
probably
> works
> > for longer, but I haven't looked to see if it does.
> >
> > If we don't absolutely need another mechanism, please, let's not
make
> more
> > work.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf
> > > Of Belling Thomas
> > > Sent: Monday, January 10, 2005 1:15 PM
> > > To: 'Jun KOSHIKO'; mmusic@ietf.org
> > > Cc: Belling Thomas
> > > Subject: RE: [MMUSIC] Video phone and offer/answer model
> > >
> > > Dear Jon,
> > >
> > > comments below
> > >
> > > BR, Thomas
> > >
> > > > -----Original Message-----
> > > > From: Jun KOSHIKO [mailto:j.koshiko@rdc.east.ntt.co.jp]
> > > > Sent: Thursday, January 06, 2005 10:41 AM
> > > > To: mmusic@ietf.org
> > > > Cc: Belling Thomas
> > > > Subject: Re: [MMUSIC] Video phone and offer/answer model
> > > >
> > > >
> > > > Hello Folks;
> > > >
> > > > Thank you for your replies.
> > > >
> > > > > Belling Thomas wrote:
> > > > ...
> > > >
> > > > > A clean way to resolve that would probably bee a new type
> > > > of grouping
> > > > > within the grouping framework. As a minimum, the grouping
> > > > would express
> > > > > that all media for the grouped m-lines need to be
> > > > established together,
> > > > > or none of them. As the media belong together in the sense
that
> they
> > > > > need to be handled by a combined application, the more far-
> reaching
> > > > > idea would be to indicate the application in the new grouping
> type.
> > > > > This obviously is more complicated, but also more powerful,
> > > > and issues
> > > > > like how to define and/or register such applications come up.
> > > >
> > > > RFC3388, grouping framework of m line, seems like a good
> > > > resolution for
> > > > the problem. Thanks for the information.
> > > >
> > > > I imagine that your idea of indication of the application like
the
> > > > following example. A new semantic like "VIDEO-PHONE" will be
> defined,
> > > > and lines of two m lines (audio/video) will be grouped. And some
> > > > attributes will be newly defined for video-phone specific use.
> > > > Is my understanding true?
> > > >
> > > > ...
> > > > a=3Dgroup:VIDEO-PHONE 1 2
> > > > m=3Daudio 30000 RTP/AVP 0 4 18
> > > > a=3Dmid:1
> > > > a=3Dxxx:xxx  (<- newly defined attribute)
> > > > m=3Dvideo 30002 RTP/AVP 31 34
> > > > a=3Dmid:2
> > > > a=3Dxxx:xxx  (<- newly defined attribute)
> > > >
> > > >
> > >
> > > As I stated, I see two options:
> > >
> > > 1. Having a general new semantics, e.g. "COMBINED-APPLICATION" to
> express
> > > that the answerer shall either accept or reject all grouped media
> streams
> > > together.
> > >
> > > 2. Having specific semantics for each combined application, e.g.
> VIDEO-
> > > PHONE as you propose. For each application, this may imply
different
> > > additional things compared to 1, e.g. lipsynch.
> > >
> > > > As a minimum, I guess LS(Lip Synchronization) semantic defined
in
> > > > RFC3388 could be applicable without difining a new type of
grouping.
> > > >
> > > > I think that video and audio stream need to be synchronized for
the
> > > > video phone service. And synchronization of video and audio
> > > > implies the
> > > > existance of common codecs both of video and of audio.
Considering
> the
> > > > following case, I guess that a callee usually rejects the offer
if
> it
> > > > doesn't support either (0) of audio codec or (31) of video
codec.
> > > >
> > > > I feel slightly uncomfortable about using LS semantic because
> > > > the usage
> > > > of LS semantic seems like different from the problem.
> > > >
> > > >  Caller                                 Callee
> > > >    |                                       |
> > > >    | (offer)                               |
> > > >    | a=3Dgroup:LS 1 2                        |
> > > >    | m=3Daudio 30000 RTP/AVP 0               |
> > > >    | .                                     |
> > > >    | .                                     |
> > > >    | a=3Dmid:1                               |
> > > >    | m=3Dvideo 30002 RTP/AVP 31              |
> > > >    | .                                     |
> > > >    | .                                     |
> > > >    | a=3Dmid:2                               |
> > > >    |-------------------------------------->|
> > > >    |                                       |
> > > >    |                               (answer)|
> > > >    |<--------------------------------------|
> > >
> > > If you are only intrested in a combination of audio and video, LS
> might
> > > do, although it is not exactly what you had in mind. An answerer
will
> > > probably accept or reject both media streams if lipsynch is
required,
> > > because this implies the media streams are closely linked
together.
> One
> > > the other hand, you might only want a combined acceptance or
rejection
> of
> > > media streams without lipsynch, and then LS would not be
appropriate -
> > > perhaps a bit theoretical for an audio and video combination.
> > >
> > > >
> > > > > I do not know if this is worth the effort, and there would
> > > > certainly be
> > > > > a backward compatibilty issue with hosts not understnding
> > > > the extension.
> > > > > For those kind of hosts as callee, the caller would still need
to
> > > > > terminate the call if undesirable media combinations are
selected.
> > > >
> > > > I think something like SIP require header may be needed to avoid
> > > > undesirable media combinations considering a backward
compatibility.
> > >
> > > The drawback of this solution is that an answering host supporting
a
> > > combined audio-video application, but not the new semantics, would
> reject
> > > the offer, although it might well behave in the desired way if no
SIP
> > > require header is used. It is more graceful for the offerer to
> terminate
> > > the session only if such an answerer indeed did an undesirable
> selection.
> > >
> > > >
> > > > Best regards,
> > > > Jun Koshiko
> > > >
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Th Belling
> > > > >
> > > > >
> > > > > ----------------------------------
> > > > > Dr. Thomas Belling
> > > > > Siemens AG
> > > > > Sankt-Martin-Str. 76
> > > > > D-81541 M|nchen Germany
> > > > > Com MN PG NT MN 1
> > > > > MCH M 34 307
> > > > > Tel     +49 89 636 75207
> > > > > Fax     +49 89 636 75577
> > > > > Mobile  +49 172 2974678
> > > > > Email   Thomas.Belling@siemens.com
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > mmusic mailing list
> > > > > mmusic@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > >
> > > > ---------------------------------------------------------
> > > > Jun KOSHIKO
> > > > Next Generation Strategy
> > > > Research and Development Center
> > > > NTT-east Corporation
> > > >
> > > > Telephone  +81 3 5359 5104
> > > > Facsimile  +81 3 5359 4768
> > > > E-mail: j.koshiko@rdc.east.ntt.co.jp
> > > > 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> > > > ---------------------------------------------------------
> > > >
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> >
> >
>=20
> ---------------------------------------------------------
> Jun KOSHIKO
> Next Generation Strategy
> Research and Development Center
> NTT-east Corporation
>=20
> Telephone  +81 3 5359 5104
> Facsimile  +81 3 5359 4768
> E-mail: j.koshiko@rdc.east.ntt.co.jp
> 19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
> ---------------------------------------------------------
>=20
>=20




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

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


From mmusic-bounces@ietf.org  Thu Jan 13 14:04:12 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 OAA04134
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 14:04:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpAUl-0003HV-LG
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 14:18:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpA9O-0008FC-CF; Thu, 13 Jan 2005 13:56:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpA3o-0006Jj-LH; Thu, 13 Jan 2005 13:51:08 -0500
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 NAA03352;
	Thu, 13 Jan 2005 13:51:07 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpAI5-00030e-7j; Thu, 13 Jan 2005 14:05:54 -0500
Received: from lion.cs.columbia.edu
	(IDENT:8gGL90w3GvBNSpM7kFc2O5pcZ7ZFqLnq@lion.cs.columbia.edu
	[128.59.16.120])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j0DIp2ir004457
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Thu, 13 Jan 2005 13:51:02 -0500 (EST)
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by lion.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id j0DIp1u9024671
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 13 Jan 2005 13:51:02 -0500
Message-ID: <41E6C310.4020800@cs.columbia.edu>
Date: Thu, 13 Jan 2005 13:50:56 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avt@ietf.org, mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0,
	Antispam-Data: 2005.1.12.43
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

We have put together an initial draft on how to do applicationg sharing, 
at the pixel level. For reasons discussed also in our earlier 
requirements document 
(http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-00.txt), 
we believe that this is closely related to remote access to applications 
and that timing information is relevant. Thus, the initial draft 
primarily defines RTP payload types. Until the draft appears in the 
archives, you can find it at

http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.txt

Note that this type of application sharing is application-neutral and 
application-unaware, i.e., this is not a "shared whiteboard" or "shared 
editor" protocol.

We would appreciate your comments and suggestions.

Henning

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


From mmusic-bounces@ietf.org  Thu Jan 13 16:40:20 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 QAA24169
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 16:40:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpCvu-0000iQ-JD
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 16:55:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpC1C-0001Jj-Ra; Thu, 13 Jan 2005 15:56:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpBuN-0005ig-FL; Thu, 13 Jan 2005 15:49:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14428;
	Thu, 13 Jan 2005 15:49:29 -0500 (EST)
Message-Id: <200501132049.PAA14428@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, 13 Jan 2005 15:49:28 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-bfcp-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.4 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

--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) Format for Binary 
			  Floor Control Protocol (BFCP) Streams
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-mmusic-sdp-bfcp-00.txt
	Pages		: 11
	Date		: 2005-1-13
	
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-00.txt

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


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

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


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

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

--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-1-13153526.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-bfcp-00.txt

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

Content-Type: text/plain
Content-ID: <2005-1-13153526.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 Jan 13 20:55:24 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 UAA15837
	for <mmusic-web-archive@ietf.org>; Thu, 13 Jan 2005 20:55:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpGul-0006ly-7p
	for mmusic-web-archive@ietf.org; Thu, 13 Jan 2005 21:10:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpGev-00044P-RJ; Thu, 13 Jan 2005 20:53:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CpGbz-0001uJ-Io
	for mmusic@megatron.ietf.org; Thu, 13 Jan 2005 20:50:51 -0500
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 UAA15352
	for <mmusic@ietf.org>; Thu, 13 Jan 2005 20:50:49 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpGqJ-0006e3-Qg
	for mmusic@ietf.org; Thu, 13 Jan 2005 21:05:41 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 13 Jan 2005 18:56:46 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0E1oDl2015946;
	Thu, 13 Jan 2005 17:50:14 -0800 (PST)
Received: from [10.0.147.181] (sjc-vpn7-411.cisco.com [10.21.145.155])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AVO86033;
	Thu, 13 Jan 2005 17:50:13 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Thu, 13 Jan 2005 17:50:12 -0800
Subject: Re: [MMUSIC] SDP format for BFCP
From: Cullen Jennings <fluffy@cisco.com>
To: "gonzalo.camarillo@ericsson.com" <Gonzalo.Camarillo@ericsson.com>,
        "mmusic@ietf.org" <mmusic@ietf.org>
Message-ID: <BE0C6554.230CD%fluffy@cisco.com>
In-Reply-To: <41E65BEE.8020809@ericsson.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit


I like the draft - I think it work well for what conferencing folks wants to
do. I don't even have any trivial NITS. Nice.

Cullen


On 1/13/05 3:30 AM, "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
wrote:

> Folks,
> 
> I have just submitted a new revision of the SDP format for BFCP. Until
> it appears in the archives you can fetch it from:
> 
> http://users.piuha.net/gonzalo/temp/draft-ietf-mmusic-sdp-bfcp-00.txt
> 
> Your comments are welcome.
> 
> Thanks,
> 
> 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  Fri Jan 14 07:47:40 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 HAA04248
	for <mmusic-web-archive@ietf.org>; Fri, 14 Jan 2005 07:47:40 -0500 (EST)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpR4h-0000un-6u
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 08:01:14 -0500
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1CpQSv-0006vz-M1
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 07:22:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpQLj-0007wX-1K; Fri, 14 Jan 2005 07:14:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpQH3-0006eI-LC; Fri, 14 Jan 2005 07:09:53 -0500
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 HAA02631;
	Fri, 14 Jan 2005 07:09:50 -0500 (EST)
From: philippe.gentric@philips.com
Received: from gw-eur4.philips.com ([161.85.125.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpPgk-0008U6-3j; Fri, 14 Jan 2005 07:24:48 -0500
Received: from smtpscan-eur4.philips.com (smtpscan-eur4.mail.philips.com
	[130.144.57.167])
	by gw-eur4.philips.com (Postfix) with ESMTP id 7FE1A49742;
	Fri, 14 Jan 2005 11:16:51 +0000 (UTC)
Received: from smtpscan-eur4.philips.com (localhost [127.0.0.1])
	by localhost.philips.com (Postfix) with ESMTP
	id 445B3B86; Fri, 14 Jan 2005 11:16:51 +0000 (GMT)
Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com
	[130.144.57.171]) by smtpscan-eur4.philips.com (Postfix) with ESMTP
	id 10E72B82; Fri, 14 Jan 2005 11:16:51 +0000 (GMT)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com
	[130.139.27.125]) 
	by smtprelay-eur2.philips.com (8.9.3p3/8.9.3-1.2.2m-20040401) with
	ESMTP id LAA07156; Fri, 14 Jan 2005 11:16:50 GMT
To: Henning Schulzrinne <hgs@cs.columbia.edu>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.9a  January 7, 2002
Message-ID: <OF1DB49F87.CEB907F1-ONC1256F89.0034FB42-C1256F89.003DD017@philips.com>
Date: Fri, 14 Jan 2005 12:15:58 +0100
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release
	6.53HF120 | November 19, 2004) at 14/01/2005 12:16:01,
	Serialize complete at 14/01/2005 12:16:01
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: avt@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Re: [AVT] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

Henning,

I like this idea a lot ;-)

1) I understand the need to "multiplex" data from all windows into a 
single RTP session,
what is unclear is if you intend to mix all the *types* 
(graphics,keyboard, pointing device, etc)
into a single RTP session, or if each would have its own RTP session
e.g. UDP port and one line in SDP, just as audio and video ?

2) Obviously if you dont use TCP you will have to find a way to ask for a 
full refresh !

3) Since this corresponds to defining a number of RTP payload formats, 
did you consider diving into the PNG format in order to make a "true" RTP 
payload for it,
i.e. one that would improve robustness to packet losses ?

regards,


Philippe Gentric









Henning Schulzrinne <hgs@cs.columbia.edu>
Sent by: 
avt-bounces@ietf.org
13/01/2005 19:50

 
        To:     avt@ietf.org
mmusic@ietf.org
        cc:     (bcc: Philippe Gentric/SUR/PSW/PHILIPS)
        Subject:        [AVT] Application sharing - a first protocol draft
        Classification: 




We have put together an initial draft on how to do applicationg sharing,
at the pixel level. For reasons discussed also in our earlier
requirements document
(http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-00.txt),
we believe that this is closely related to remote access to applications
and that timing information is relevant. Thus, the initial draft
primarily defines RTP payload types. Until the draft appears in the
archives, you can find it at

http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.txt

Note that this type of application sharing is application-neutral and
application-unaware, i.e., this is not a "shared whiteboard" or "shared
editor" protocol.

We would appreciate your comments and suggestions.

Henning

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



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


From mmusic-bounces@ietf.org  Fri Jan 14 08:11:32 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 IAA11905
	for <mmusic-web-archive@ietf.org>; Fri, 14 Jan 2005 08:11:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpRT9-0002RL-GP
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 08:26:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpR4x-0002KD-8F; Fri, 14 Jan 2005 08:01:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpR0K-0000uF-E4; Fri, 14 Jan 2005 07:56:40 -0500
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 HAA08987;
	Fri, 14 Jan 2005 07:56:39 -0500 (EST)
From: philippe.gentric@philips.com
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpRC5-0001Z0-Jz; Fri, 14 Jan 2005 08:08:50 -0500
Received: from gw-eur4.philips.com ([161.85.125.10])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1CpPca-00029F-P0; Fri, 14 Jan 2005 06:28:04 -0500
Received: from smtpscan-eur4.philips.com (smtpscan-eur4.mail.philips.com
	[130.144.57.167])
	by gw-eur4.philips.com (Postfix) with ESMTP id 7FE1A49742;
	Fri, 14 Jan 2005 11:16:51 +0000 (UTC)
Received: from smtpscan-eur4.philips.com (localhost [127.0.0.1])
	by localhost.philips.com (Postfix) with ESMTP
	id 445B3B86; Fri, 14 Jan 2005 11:16:51 +0000 (GMT)
Received: from smtprelay-eur2.philips.com (smtprelay-eur2.philips.com
	[130.144.57.171]) by smtpscan-eur4.philips.com (Postfix) with ESMTP
	id 10E72B82; Fri, 14 Jan 2005 11:16:51 +0000 (GMT)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com
	[130.139.27.125]) 
	by smtprelay-eur2.philips.com (8.9.3p3/8.9.3-1.2.2m-20040401) with
	ESMTP id LAA07156; Fri, 14 Jan 2005 11:16:50 GMT
To: Henning Schulzrinne <hgs@cs.columbia.edu>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.9a  January 7, 2002
Message-ID: <OF1DB49F87.CEB907F1-ONC1256F89.0034FB42-C1256F89.003DD017@philips.com>
Date: Fri, 14 Jan 2005 12:15:58 +0100
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release
	6.53HF120 | November 19, 2004) at 14/01/2005 12:16:01,
	Serialize complete at 14/01/2005 12:16:01
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: avt@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Re: [AVT] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

Henning,

I like this idea a lot ;-)

1) I understand the need to "multiplex" data from all windows into a 
single RTP session,
what is unclear is if you intend to mix all the *types* 
(graphics,keyboard, pointing device, etc)
into a single RTP session, or if each would have its own RTP session
e.g. UDP port and one line in SDP, just as audio and video ?

2) Obviously if you dont use TCP you will have to find a way to ask for a 
full refresh !

3) Since this corresponds to defining a number of RTP payload formats, 
did you consider diving into the PNG format in order to make a "true" RTP 
payload for it,
i.e. one that would improve robustness to packet losses ?

regards,


Philippe Gentric









Henning Schulzrinne <hgs@cs.columbia.edu>
Sent by: 
avt-bounces@ietf.org
13/01/2005 19:50

 
        To:     avt@ietf.org
mmusic@ietf.org
        cc:     (bcc: Philippe Gentric/SUR/PSW/PHILIPS)
        Subject:        [AVT] Application sharing - a first protocol draft
        Classification: 




We have put together an initial draft on how to do applicationg sharing,
at the pixel level. For reasons discussed also in our earlier
requirements document
(http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-00.txt),
we believe that this is closely related to remote access to applications
and that timing information is relevant. Thus, the initial draft
primarily defines RTP payload types. Until the draft appears in the
archives, you can find it at

http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.txt

Note that this type of application sharing is application-neutral and
application-unaware, i.e., this is not a "shared whiteboard" or "shared
editor" protocol.

We would appreciate your comments and suggestions.

Henning

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



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


From mmusic-bounces@ietf.org  Fri Jan 14 08:54: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 IAA14955
	for <mmusic-web-archive@ietf.org>; Fri, 14 Jan 2005 08:54:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpS8O-0003T2-Kv
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 09:09:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpRtC-00006l-OL; Fri, 14 Jan 2005 08:53:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CpRjs-0006W1-Vu
	for mmusic@megatron.ietf.org; Fri, 14 Jan 2005 08:43:45 -0500
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 IAA14331
	for <mmusic@ietf.org>; Fri, 14 Jan 2005 08:43:43 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CpRyJ-0003FI-JT
	for mmusic@ietf.org; Fri, 14 Jan 2005 08:58:40 -0500
Received: from razor.cs.columbia.edu
	(IDENT:hXLPCFj8Yo8EqvfFHCDhcEKPq2beHpRm@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j0EDhcir003461
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <mmusic@ietf.org>; Fri, 14 Jan 2005 08:43:39 -0500 (EST)
Received: from [127.0.0.1] (IDENT:tW+lCiwpPTTJDnlgqx43rVsDyBjyXxSW@localhost
	[127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j0EDhciw002554
	for <mmusic@ietf.org>; Fri, 14 Jan 2005 08:43:38 -0500
Message-ID: <41E7CC83.1010807@cs.columbia.edu>
Date: Fri, 14 Jan 2005 08:43:31 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0,
	Antispam-Data: 2005.1.14.2
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: [AVT] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit

To avoid needless cross-posting, I'm keeping any application sharing 
discussion contributions on AVT for now.

Henning

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


From mmusic-bounces@ietf.org  Fri Jan 14 09:54:50 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 JAA18439
	for <mmusic-web-archive@ietf.org>; Fri, 14 Jan 2005 09:54:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpT5A-0004c6-EQ
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 10:09:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpSov-0006u8-83; Fri, 14 Jan 2005 09:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CpSjK-0005Qd-7I
	for mmusic@megatron.ietf.org; Fri, 14 Jan 2005 09:47:14 -0500
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 JAA18067
	for <mmusic@ietf.org>; Fri, 14 Jan 2005 09:47:12 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpSxl-0004Sl-16
	for mmusic@ietf.org; Fri, 14 Jan 2005 10:02:10 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 14 Jan 2005 07:53:15 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0EEkdjw017083
	for <mmusic@ietf.org>; Fri, 14 Jan 2005 06:46:39 -0800 (PST)
Received: from cisco.com ([161.44.79.149]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AOI32681; Fri, 14 Jan 2005 09:46:38 -0500 (EST)
Message-ID: <41E7DB4E.5060906@cisco.com>
Date: Fri, 14 Jan 2005 09:46:38 -0500
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: mmusic@ietf.org
References: <200501132049.PAA14428@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re:draft-ietf-mmusic-sdp-bfcp-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: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

This looks good to me. I am especially happy to se the description of 
connection reestablishment procedures.

One nit:

In serveral places (X= confid, userid, nonce, floorid) when describing 
the syntax, there is text of the form:

    X-attribute       = "a=X: " X-value
    X-value           = token

    The 'X' attribute carries the integer representation of the X

It would be better to really specify an integer in ABNF, rather than a 
token.

	Paul

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


From mmusic-bounces@ietf.org  Fri Jan 14 16:37:38 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 QAA25146
	for <mmusic-web-archive@ietf.org>; Fri, 14 Jan 2005 16:37:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpZN2-0007BK-77
	for mmusic-web-archive@ietf.org; Fri, 14 Jan 2005 16:52:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpYz0-0005ha-7y; Fri, 14 Jan 2005 16:27:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpYL0-0004oH-Bm; Fri, 14 Jan 2005 15:46:30 -0500
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 PAA15560;
	Fri, 14 Jan 2005 15:46:28 -0500 (EST)
Received: from is3smtp03.cec.eu.int ([147.67.3.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CpYZU-0003yV-Kk; Fri, 14 Jan 2005 16:01:30 -0500
Received: from mail pickup service by is3smtp03.cec.eu.int with Microsoft
	SMTPSVC; Fri, 14 Jan 2005 21:44:46 +0100
Received: from megatron.ietf.org ([132.151.6.71]) by is3smtp03.cec.eu.int with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 Jan 2005 22:41:21 +0100
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpC1E-0001Jp-Np; Thu, 13 Jan 2005 15:56:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpBuN-0005ig-FL; Thu, 13 Jan 2005 15:49:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14428;
	Thu, 13 Jan 2005 15:49:29 -0500 (EST)
Message-Id: <200501132049.PAA14428@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, 13 Jan 2005 15:49:28 -0500
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-OriginalArrivalTime: 13 Jan 2005 21:41:25.0343 (UTC)
	FILETIME=[A19546F0:01C4F9B8]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-bfcp-00.txt
X-BeenThere: mmusic@ietf.org
Reply-To: internet-drafts@ietf.org
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: 6d95a152022472c7d6cdf886a0424dc6

--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) Format for Binary 
			  Floor Control Protocol (BFCP) Streams
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-mmusic-sdp-bfcp-00.txt
	Pages		: 11
	Date		: 2005-1-13
	
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-00.txt

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


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

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


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

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

--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-1-13153526.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-bfcp-00.txt

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

Content-Type: text/plain
Content-ID: <2005-1-13153526.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
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--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  Sat Jan 15 03:50:21 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 DAA24111
	for <mmusic-web-archive@ietf.org>; Sat, 15 Jan 2005 03:50:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cpjs8-0003iv-Cj
	for mmusic-web-archive@ietf.org; Sat, 15 Jan 2005 04:05:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CpjZg-0008Rb-AF; Sat, 15 Jan 2005 03:46:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CpjUf-0007Wl-RQ
	for mmusic@megatron.ietf.org; Sat, 15 Jan 2005 03:41:14 -0500
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 DAA23648
	for <mmusic@ietf.org>; Sat, 15 Jan 2005 03:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CpjjF-0003R4-1f
	for mmusic@ietf.org; Sat, 15 Jan 2005 03:56:19 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0F8f9O6013778 for <mmusic@ietf.org>; Sat, 15 Jan 2005 09:41:09 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Sat, 15 Jan 2005 09:41:09 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id YDRM3CJ1; Sat, 15 Jan 2005 09:41:09 +0100
Received: from ericsson.com (rvi2-94-23.sw.ericsson.se [153.88.94.23])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id A10BB189CC; Sat, 15 Jan 2005 10:41:07 +0200 (EET)
Message-ID: <41E8D71F.1030300@ericsson.com>
Date: Sat, 15 Jan 2005 10:41:03 +0200
X-Sybari-Trust: dcbd8103 b8ec86c7 4bf381f2 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-kmgmt-ext-12.txt
References: <1ECE0EB50388174790F9694F77522CCF0122F1D8@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0122F1D8@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Jan 2005 08:41:09.0267 (UTC)
	FILETIME=[F5DA7E30:01C4FADD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: 7bit
Cc: "'jari.arkko@ericsson.com'" <jari.arkko@ericsson.com>,
        "'elisabetta.carrara@ericasson.com'"
	<elisabetta.carrara@ericasson.com.cnri.reston.va.us>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'Mats.naslund@ericsson.com'" <Mats.naslund@ericsson.com>,
        "'Karl.norrmann@ericsson.com'" <Karl.norrmann@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: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: 7bit

Hi,

Francois is right in pointing out that there is a known problem with SIP 
forking referred to as HERFP (Heterogeneous Error Response Forking 
Problem). RFC 3326 refers to it in its abstract.

We never got around to resolving this issue. However, as Francois 
suggests, there could be ways around it. If both UAs support 100rel the 
offer can be accepted in a provisional (e.g., 183) response. Further 
negotiations could be carried out using PRACKs, and when the key 
management procedure completed, the UAS could finally accept the session 
with a 200 OK response for the INVITE.

UAs that do not suppor 100rel would need to use a 200 OK or live with 
the HERFP, as Francois pointed out.

Regards,

Gonzalo



Francois Audet wrote:

> Hi,
> 
> I have a 2 comments on
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-12.txt.
> 
> 
> This first comment is for a clarification:
> 
> - Section 3.1.2 explains that SIP 488 is used for rejecting a key 
> management offer.
>   488 allows for the inclusion of an SDP indicating the capabilities of the
>   answerer (the same way an SDP in a 200 OK sent in an OPTIONS request 
> indicates
>   capabilities). It would be desireable to explain how this works with
>   kmgmt. I assume that this is what is meant by wording saying "Further 
> details
>   about the cause of failure MAY be described in an included message 
> from the key
>   management protocol." Perhaps a wording like the following would help:
> 
>         Further details about the media capabilities of the offerer MAY 
> be in
>         included in 488 according to normal RFC 3261 rules. Further 
> details about
>         the cause of the rejection of the key message itself MAY be 
> described in
>       the key message in the SDP in the 488, according to the rules
>         of the key management protocol. The session is then ...
> 
>  ...or something along those lines.
> 
>  It would also be worthwile to describe how this relates to MIKEY in
>  particular (i.e, that the MIKEY message itself in the key-mgmt may have
>  the key management rejection reason). It would also be helpful to have
>  an Example of a failure case for SIP 488/MIKEY.
>  
> -----------------------
> 
> This next comment is concerning a potential issue with SIP forking. I'm
> not sure we can fix it in MMUSIC, but I'll state it anyways.
> 
> - There is a somewhat unpleasant side-effect of using a SIP failure 
> response
>   for rejecting a key management message.
> 
> - Suppose that there is a SIP forking proxy forking the offer (in the 
> INVITE).
>   Let's say the call is forked to A and B. A is a device for which no
>   user is present at the time (say, an office phone). Suppose A rejects the
>   call with 401 Unauthorized because it needs authorization. Suppose the 
> user
>   is at home (B), but rejects the offer with 488 (because it's using the 
> key
>   management protocol used for the corporation which is different than 
> the one
>   used at home). The forking proxy will see both the 401 an the 488, but 
> can only
>   forward one to the offerer. There is nothing saying which one should 
> be forwarded
>   beyong the error response that indicates that there could be 
> retransmission (which
>   applies to both codes in this case). Worst, in this particular 
> example, if the proxy
>   follows the rule section 6/RFC 3261, chances are it will pick 401. 
> This means
>   that you won't be able to call home because you'll never receive a 488.
> 
> - This is a weakness of the forking procedures in SIP, and perhaps it 
> should be
>   addresses in the SIP working group.
> 
> - The other alternative would be to not consider the rejection of the 
> key as a
>   rejection of the offer. Instead of sending a 488, you would accept the
>   offer with an answer, and the key rejection would be included in the 
> key message
>   itself (which could then trigger another offer/answer). In other 
> words, the
>   offer/answer is sucessful, but the key exchanged is not. This would 
> have the obvious
>   advantage of the previous scenario working properly. However, if there 
> is no
>   suitable key management protocol, we could run into the reverse 
> problem (when the
>   user is at work (A) instead of (B). In this case, the proxy would 
> forward the
>   200 with the answer with the key message, and drop the 401. There 
> would be another
>   offer/answer round which would then fail. The caller in this case 
> would never get
>   the 401.
> 
> I'm not sure how to deal with this forking issue.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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  Sun Jan 16 13:09:29 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 NAA02535
	for <mmusic-web-archive@ietf.org>; Sun, 16 Jan 2005 13:09:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CqF55-0007K6-EG
	for mmusic-web-archive@ietf.org; Sun, 16 Jan 2005 13:24:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqEoX-0002h8-F3; Sun, 16 Jan 2005 13:07:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqEkt-0002EQ-D1
	for mmusic@megatron.ietf.org; Sun, 16 Jan 2005 13:04:03 -0500
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 NAA02150
	for <mmusic@ietf.org>; Sun, 16 Jan 2005 13:04:00 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqEzl-0007DA-R7
	for mmusic@ietf.org; Sun, 16 Jan 2005 13:19:27 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63032
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CqEkM-0003KD-Bo; Sun, 16 Jan 2005 18:03:30 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EB5072E4-67E8-11D9-B484-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Sun, 16 Jan 2005 18:03:26 +0000
To: IETF MMUSIC Working Group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?J=F6rg_Ott?= <jo@tzi.uni-bremen.de>
Subject: [MMUSIC] Working group last call:
	draft-ietf-mmusic-connection-precon-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

This is to announce a working group last call on the 
Connection-Establishment Preconditions work 
<draft-ietf-mmusic-connection-precon-01.txt>. Please send any final 
comments to the mailing list by 31 January 2005. If no substantive 
technical issues are raised by this time, we intend to request the IESG 
to publish this as a proposed standard RFC.

Colin


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


From mmusic-bounces@ietf.org  Mon Jan 17 16:59:05 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 QAA24951
	for <mmusic-web-archive@ietf.org>; Mon, 17 Jan 2005 16:59:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cqf94-0002F6-NO
	for mmusic-web-archive@ietf.org; Mon, 17 Jan 2005 17:14:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqeA5-0003Y2-80; Mon, 17 Jan 2005 16:11:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cqe5P-0001MJ-Sz; Mon, 17 Jan 2005 16:06:55 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14830;
	Mon, 17 Jan 2005 16:06:53 -0500 (EST)
Message-Id: <200501172106.QAA14830@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, 17 Jan 2005 16:06:53 -0500
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-media-label-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
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		: The SDP (Session Description Protocol) Label Attribute
	Author(s)	: O. Levin, G. Camarillo
	Filename	: draft-ietf-mmusic-sdp-media-label-01.txt
	Pages		: 7
	Date		: 2005-1-17
	
This document 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
   particular media stream in its context.

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

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2005-1-17154028.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 Jan 18 07:45:54 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 HAA18406
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 07:45:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CqszO-0006s6-7x
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 08:01:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cqsgr-0008Nr-Vn; Tue, 18 Jan 2005 07:42:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cqsfn-0008HA-So
	for mmusic@megatron.ietf.org; Tue, 18 Jan 2005 07:41:28 -0500
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 HAA18205
	for <mmusic@ietf.org>; Tue, 18 Jan 2005 07:41:26 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cqsv2-0006ez-SF
	for mmusic@ietf.org; Tue, 18 Jan 2005 07:57:14 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0ICfOO6024940; Tue, 18 Jan 2005 13:41:24 +0100
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 18 Jan 2005 13:41:23 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.13]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 18 Jan 2005 13:41:23 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id CA9B4189CC; Tue, 18 Jan 2005 14:41:22 +0200 (EET)
Message-ID: <41ED03F2.2090405@ericsson.com>
Date: Tue, 18 Jan 2005 14:41:22 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] Working group last
	call:	draft-ietf-mmusic-sdp-media-label-00.txt
References: <41BECE64.3040401@ericsson.com> <41C0354C.5080403@ericsson.com>
	<6843E474-502D-11D9-8152-000A957FC5F2@csperkins.org>
In-Reply-To: <6843E474-502D-11D9-8152-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2005 12:41:23.0596 (UTC)
	FILETIME=[04B3CCC0:01C4FD5B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>, Joerg Ott <jo@tzi.uni-bremen.de>,
        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: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit

Colin,

a new revision of the draft that addresses the comments received during 
its WGLC is already in the archives:

http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-media-label-01.txt

Feel free to request its publication as an RFC whenever you wish.

Thanks,

Gonzalo

Colin Perkins wrote:

> This last call ends today. It looks like there are minor issues to be 
> resolved in an updated draft. Once the revised draft is available, we'll 
> allow a short time to check that all comments have been addressed, then 
> advance the draft.
> 
> Colin
> 
> 
> 
> On 15 Dec 2004, at 12:59, Magnus Westerlund wrote:
> 
>> Hi Gonzalo,
>>
>> The proposed changes looks fine. See below about point 3.
>>
>> Gonzalo Camarillo (JO/LMF) wrote:
>>
>>>  > 3. Section 5. I am a bit worried about the offer/answer section. 
>>> It is
>>>  > very unclear on the handling of this attribute. Can we really trust
>>>  > applications to define such behavior? From my work with 
>>> Offer/Answer I
>>>  > sometimes find it difficult to get the right behavior out of SDP in
>>>  > offer/answer usage. If this behavior is left to the application then
>>>  > there is need for a much more explicit section that explains the
>>>  > different choices. Also I think using application defined behavior 
>>> will
>>>  > result in quite divergent behavior.
>>> If this was an attribute that had any influence in the offer/answer
>>> behabior I would agree with you. But this attribute, from the
>>> offer/answer point of view, is just informational. That's why offerers
>>> and answerers can use it as the wish. It does not have any influence in
>>> the session being established.
>>> The behavior we expect applications to define would be something like,
>>> "use the same label in the media line as in the XML document you are
>>> using to describe your conference". Note that this attribute is always
>>> for the remote's UA information, so, the values that this attribute
>>> takes in an answer is completely independent from the value it takes in
>>> the offer.
>>
>>
>> Okay, I do understand. I think it is okay with the current text.
>>
>>
>> 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
>>
> 

-- 
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 Jan 18 18:23: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 SAA17449
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 18:23:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr2wL-0008OT-Ao
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 18:39:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr2fY-0000sF-CP; Tue, 18 Jan 2005 18:21:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cr2WF-0003uj-WB
	for mmusic@megatron.ietf.org; Tue, 18 Jan 2005 18:12:16 -0500
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 SAA16292
	for <mmusic@ietf.org>; Tue, 18 Jan 2005 18:12:12 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cr2la-0008AD-S8
	for mmusic@ietf.org; Tue, 18 Jan 2005 18:28:08 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63827
	helo=[192.168.0.5])
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1Cr2Vj-0007HD-90
	for mmusic@ietf.org; Tue, 18 Jan 2005 23:11:43 +0000
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <4F8E39AD-69A6-11D9-81B8-000A957FC5F2@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: IETF MMUSIC Working Group <mmusic@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Tue, 18 Jan 2005 23:11:40 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Potential IPR relating to draft-ietf-mmusic-img-req-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.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

Folks,

We've been informed by the secretariat that a third-party IPR 
disclosure has been made relating to draft-ietf-mmusic-img-req-07.txt. 
Details can be found at 
https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=520

Colin


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


From mmusic-bounces@ietf.org  Tue Jan 18 19:00:50 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 TAA20465
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 19:00:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr3Wf-0000nk-4y
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 19:16:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr39J-0007od-Pb; Tue, 18 Jan 2005 18:52:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr38B-0007cD-Dc; Tue, 18 Jan 2005 18:51:27 -0500
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 SAA19759;
	Tue, 18 Jan 2005 18:51:24 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr3NW-0000Z5-HE; Tue, 18 Jan 2005 19:07:19 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 18 Jan 2005 16:58:21 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0INoql2023484;
	Tue, 18 Jan 2005 15:50:52 -0800 (PST)
Received: from [10.0.0.204] (rtp-vpn2-268.cisco.com [10.82.241.12])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AVR68909;
	Tue, 18 Jan 2005 15:50:49 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Tue, 18 Jan 2005 13:33:34 -1000
From: Cullen Jennings <fluffy@cisco.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>, <avt@ietf.org>,
        "mmusic@ietf.org" <mmusic@ietf.org>
Message-ID: <BE12C0AE.23BA8%fluffy@cisco.com>
In-Reply-To: <41E6C310.4020800@cs.columbia.edu>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: [AVT] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit


Interesting stuff. 

Why would you use UDP for this?

Have you had a look at VNC?


On 1/13/05 10:50 AM, "Henning Schulzrinne" <hgs@cs.columbia.edu> wrote:

> We have put together an initial draft on how to do applicationg sharing,
> at the pixel level. For reasons discussed also in our earlier
> requirements document
> (http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-00.txt),
> we believe that this is closely related to remote access to applications
> and that timing information is relevant. Thus, the initial draft
> primarily defines RTP payload types. Until the draft appears in the
> archives, you can find it at
> 
> http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.txt
> 
> Note that this type of application sharing is application-neutral and
> application-unaware, i.e., this is not a "shared whiteboard" or "shared
> editor" protocol.
> 
> We would appreciate your comments and suggestions.
> 
> Henning
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


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


From mmusic-bounces@ietf.org  Tue Jan 18 19:06:49 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 TAA20856
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 19:06:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr3cT-0000wH-CQ
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 19:22:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr3Iw-0001ZN-8J; Tue, 18 Jan 2005 19:02:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr3DZ-0008Rs-F2; Tue, 18 Jan 2005 18:57:01 -0500
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 SAA20122;
	Tue, 18 Jan 2005 18:56:58 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr3Su-0000hx-Qx; Tue, 18 Jan 2005 19:12:54 -0500
Received: from lion.cs.columbia.edu
	(IDENT:HZcKoMdeVcwOKThuYsCVwrH1qec1RF6s@lion.cs.columbia.edu
	[128.59.16.120])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j0INuuir017233
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Tue, 18 Jan 2005 18:56:56 -0500 (EST)
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by lion.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id j0INutiJ030323
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 18 Jan 2005 18:56:55 -0500
Message-ID: <41EDA242.10605@cs.columbia.edu>
Date: Tue, 18 Jan 2005 18:56:50 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <BE12C0AE.23BA8%fluffy@cisco.com>
In-Reply-To: <BE12C0AE.23BA8%fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0,
	Antispam-Data: 2005.1.18.7
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0,
	__PORN_PHRASE_15_0 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: [MMUSIC] Re: [AVT] Application sharing - a first protocol 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>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit



Cullen Jennings wrote:
> Interesting stuff. 
> 
> Why would you use UDP for this?

We anticipate using TCP, namely the connection-oriented transport of 
RTP, in almost all cases, with UDP only in the case where you want to 
distribute the shared application data via multicast.

> 
> Have you had a look at VNC?

Yes, among others, such as T.128. Indeed, our current screen sharing 
application in our SIP client (sipc) is a slightly modified vnc. The 
limitations of that approach partially motivated the work summarized in 
the draft. Among other problems, vnc has its own rather "unique" 
security model, doesn't really support an offer-answer style negotiation 
of pixel "codecs" and only deals with whole-screen sharing, not 
application (window) sharing. We are working on a test implementation, 
probably using vnc as a skeleton.

> 
> 
> On 1/13/05 10:50 AM, "Henning Schulzrinne" <hgs@cs.columbia.edu> wrote:
> 
> 
>>We have put together an initial draft on how to do applicationg sharing,
>>at the pixel level. For reasons discussed also in our earlier
>>requirements document
>>(http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-00.txt),
>>we believe that this is closely related to remote access to applications
>>and that timing information is relevant. Thus, the initial draft
>>primarily defines RTP payload types. Until the draft appears in the
>>archives, you can find it at
>>
>>http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.txt
>>
>>Note that this type of application sharing is application-neutral and
>>application-unaware, i.e., this is not a "shared whiteboard" or "shared
>>editor" protocol.
>>
>>We would appreciate your comments and suggestions.
>>
>>Henning
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>>avt@ietf.org
>>https://www1.ietf.org/mailman/listinfo/avt

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


From mmusic-bounces@ietf.org  Tue Jan 18 20:23:04 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 UAA28467
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 20:23:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr4oE-0002uY-Tw
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 20:38:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr4WB-0000CC-Dx; Tue, 18 Jan 2005 20:20:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cr4UM-0008B9-Fx
	for mmusic@megatron.ietf.org; Tue, 18 Jan 2005 20:18:27 -0500
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 UAA27747
	for <mmusic@ietf.org>; Tue, 18 Jan 2005 20:18:24 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cr4jf-0002hE-P9
	for mmusic@ietf.org; Tue, 18 Jan 2005 20:34:19 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0J1HBh15221; Tue, 18 Jan 2005 20:17:11 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S98V3W>; Tue, 18 Jan 2005 20:17:12 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0155A1CA@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Subject: RE: [MMUSIC] Comments on draft-ietf-mmusic-kmgmt-ext-12.txt
Date: Tue, 18 Jan 2005 20:17:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 8bebc843ecf489bb7d907f63ccb001af
Cc: "'jari.arkko@ericsson.com'" <jari.arkko@ericsson.com>,
        "'elisabetta.carrara@ericasson.com'"
	<elisabetta.carrara@ericasson.com.cnri.reston.va.us>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'Mats.naslund@ericsson.com'" <Mats.naslund@ericsson.com>,
        "'Karl.norrmann@ericsson.com'" <Karl.norrmann@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>
Content-Type: multipart/mixed; boundary="===============2011351460=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 578029c71870398e30dc7af6a1ae528d

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============2011351460==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4FDC4.98D5C321"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4FDC4.98D5C321
Content-Type: text/plain

Thank you Gonzalo!

I agree with what you are saying as a way around the HERPF problem for
keymgmt. This is what I had in mind.

As Gonzalo describes, we need to accept the offer (even if we are
rejecting the keymgmt) instead of sending the 488.

The answerer would send a provisional response (e.g., 183) with the 
SDP-Answer. In the SDP-Answer, the a=key-mgmt:mikey attribute is included, 
but instead of the keying material, I would assume it would have the 
rejection. For example, I would assume that a proper value in the MIKEY
error 
payload (ERR) for that purpose already exists.

After that, the keying information can be renegotiated using additionnal
offer/answer cycles (I think UPDATE/re-INVITE would be appropriate).

In other words, 488 is rejecting the session completely. But to reject
just the keymgmt (and keep the session) you would reject explicitly 
the keymgmt using the native keymgmt procedures (e.g., MIKEY).

This would be a small change to kmgmt section 3.1.2. 

I don't think there are any other alternatives. Waiting for a general 
solution to the HERPF problem does not seem acceptable to me, because
it won't be backward compatible and because it may take a very long
time. Also, to me it seems logical that we accept the Offer, but reject the 
key. It really should be the same dialog, but with additional MIKEY
interactions.
It really emphases the strenght of MIKEY as a key management protocol. 

Let me know if you think this is a good idea. I can certainly help with the
wording.



> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
> Sent: Saturday, January 15, 2005 00:41
> To: Audet, Francois [SC100:9T51:EXCH]
> Cc: 'mmusic@ietf.org'; 'elisabetta.carrara@ericasson.com'; 
> 'Mats.naslund@ericsson.com'; 'jari.arkko@ericsson.com'; 
> 'Karl.norrmann@ericsson.com'
> Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-kmgmt-ext-12.txt
> 
> 
> Hi,
> 
> Francois is right in pointing out that there is a known 
> problem with SIP 
> forking referred to as HERFP (Heterogeneous Error Response Forking 
> Problem). RFC 3326 refers to it in its abstract.
> 
> We never got around to resolving this issue. However, as Francois 
> suggests, there could be ways around it. If both UAs support 
> 100rel the 
> offer can be accepted in a provisional (e.g., 183) response. Further 
> negotiations could be carried out using PRACKs, and when the key 
> management procedure completed, the UAS could finally accept 
> the session 
> with a 200 OK response for the INVITE.
> 
> UAs that do not suppor 100rel would need to use a 200 OK or live with 
> the HERFP, as Francois pointed out.
> 
> Regards,
> 
> Gonzalo
> 
> 
> 
> Francois Audet wrote:
> 
> > Hi,
> > 
> > I have a 2 comments on 
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-12.txt
> > .
> > 
> > 
> > This first comment is for a clarification:
> > 
> > - Section 3.1.2 explains that SIP 488 is used for rejecting a key
> > management offer.
> >   488 allows for the inclusion of an SDP indicating the 
> capabilities of the
> >   answerer (the same way an SDP in a 200 OK sent in an 
> OPTIONS request 
> > indicates
> >   capabilities). It would be desireable to explain how this 
> works with
> >   kmgmt. I assume that this is what is meant by wording 
> saying "Further 
> > details
> >   about the cause of failure MAY be described in an 
> included message 
> > from the key
> >   management protocol." Perhaps a wording like the 
> following would help:
> > 
> >         Further details about the media capabilities of the offerer 
> > MAY
> > be in
> >         included in 488 according to normal RFC 3261 rules. Further 
> > details about
> >         the cause of the rejection of the key message itself MAY be 
> > described in
> >       the key message in the SDP in the 488, according to the rules
> >         of the key management protocol. The session is then ...
> > 
> >  ...or something along those lines.
> > 
> >  It would also be worthwile to describe how this relates to 
> MIKEY in  
> > particular (i.e, that the MIKEY message itself in the key-mgmt may 
> > have  the key management rejection reason). It would also 
> be helpful 
> > to have  an Example of a failure case for SIP 488/MIKEY.
> >  
> > -----------------------
> > 
> > This next comment is concerning a potential issue with SIP forking. 
> > I'm not sure we can fix it in MMUSIC, but I'll state it anyways.
> > 
> > - There is a somewhat unpleasant side-effect of using a SIP failure
> > response
> >   for rejecting a key management message.
> > 
> > - Suppose that there is a SIP forking proxy forking the 
> offer (in the
> > INVITE).
> >   Let's say the call is forked to A and B. A is a device 
> for which no
> >   user is present at the time (say, an office phone). 
> Suppose A rejects the
> >   call with 401 Unauthorized because it needs 
> authorization. Suppose the 
> > user
> >   is at home (B), but rejects the offer with 488 (because 
> it's using the 
> > key
> >   management protocol used for the corporation which is 
> different than 
> > the one
> >   used at home). The forking proxy will see both the 401 an 
> the 488, but 
> > can only
> >   forward one to the offerer. There is nothing saying which 
> one should 
> > be forwarded
> >   beyong the error response that indicates that there could be 
> > retransmission (which
> >   applies to both codes in this case). Worst, in this particular 
> > example, if the proxy
> >   follows the rule section 6/RFC 3261, chances are it will 
> pick 401. 
> > This means
> >   that you won't be able to call home because you'll never 
> receive a 488.
> > 
> > - This is a weakness of the forking procedures in SIP, and 
> perhaps it
> > should be
> >   addresses in the SIP working group.
> > 
> > - The other alternative would be to not consider the 
> rejection of the
> > key as a
> >   rejection of the offer. Instead of sending a 488, you 
> would accept the
> >   offer with an answer, and the key rejection would be 
> included in the 
> > key message
> >   itself (which could then trigger another offer/answer). In other 
> > words, the
> >   offer/answer is sucessful, but the key exchanged is not. 
> This would 
> > have the obvious
> >   advantage of the previous scenario working properly. 
> However, if there 
> > is no
> >   suitable key management protocol, we could run into the reverse 
> > problem (when the
> >   user is at work (A) instead of (B). In this case, the proxy would 
> > forward the
> >   200 with the answer with the key message, and drop the 401. There 
> > would be another
> >   offer/answer round which would then fail. The caller in this case 
> > would never get
> >   the 401.
> > 
> > I'm not sure how to deal with this forking issue.
> > 
> > 
> > 
> ----------------------------------------------------------------------
> > --
> > 
> > _______________________________________________
> > 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
> 
> 
> 

------_=_NextPart_001_01C4FDC4.98D5C321
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] Comments on =
draft-ietf-mmusic-kmgmt-ext-12.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Thank you Gonzalo!</FONT>
</P>

<P><FONT SIZE=3D2>I agree with what you are saying as a way around the =
HERPF problem for</FONT>
<BR><FONT SIZE=3D2>keymgmt. This is what I had in mind.</FONT>
</P>

<P><FONT SIZE=3D2>As Gonzalo describes, we need to accept the offer =
(even if we are</FONT>
<BR><FONT SIZE=3D2>rejecting the keymgmt) instead of sending the =
488.</FONT>
</P>

<P><FONT SIZE=3D2>The answerer would send a provisional response (e.g., =
183) with the </FONT>
<BR><FONT SIZE=3D2>SDP-Answer. In the SDP-Answer, the =
a=3Dkey-mgmt:mikey attribute is included, </FONT>
<BR><FONT SIZE=3D2>but instead of the keying material, I would assume =
it would have the </FONT>
<BR><FONT SIZE=3D2>rejection. For example, I would assume that a proper =
value in the MIKEY error </FONT>
<BR><FONT SIZE=3D2>payload (ERR) for that purpose already =
exists.</FONT>
</P>

<P><FONT SIZE=3D2>After that, the keying information can be =
renegotiated using additionnal</FONT>
<BR><FONT SIZE=3D2>offer/answer cycles (I think UPDATE/re-INVITE would =
be appropriate).</FONT>
</P>

<P><FONT SIZE=3D2>In other words, 488 is rejecting the session =
completely. But to reject</FONT>
<BR><FONT SIZE=3D2>just the keymgmt (and keep the session) you would =
reject explicitly </FONT>
<BR><FONT SIZE=3D2>the keymgmt using the native keymgmt procedures =
(e.g., MIKEY).</FONT>
</P>

<P><FONT SIZE=3D2>This would be a small change to kmgmt section 3.1.2. =
</FONT>
</P>

<P><FONT SIZE=3D2>I don't think there are any other alternatives. =
Waiting for a general </FONT>
<BR><FONT SIZE=3D2>solution to the HERPF problem does not seem =
acceptable to me, because</FONT>
<BR><FONT SIZE=3D2>it won't be backward compatible and because it may =
take a very long</FONT>
<BR><FONT SIZE=3D2>time. Also, to me it seems logical that we accept =
the Offer, but reject the </FONT>
<BR><FONT SIZE=3D2>key. It really should be the same dialog, but with =
additional MIKEY interactions.</FONT>
<BR><FONT SIZE=3D2>It really emphases the strenght of MIKEY as a key =
management protocol. </FONT>
</P>

<P><FONT SIZE=3D2>Let me know if you think this is a good idea. I can =
certainly help with the</FONT>
<BR><FONT SIZE=3D2>wording.</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@ericsson.com">mailto:Gonzalo.Camarillo@=
ericsson.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Saturday, January 15, 2005 00:41</FONT>
<BR><FONT SIZE=3D2>&gt; To: Audet, Francois [SC100:9T51:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'mmusic@ietf.org'; =
'elisabetta.carrara@ericasson.com'; </FONT>
<BR><FONT SIZE=3D2>&gt; 'Mats.naslund@ericsson.com'; =
'jari.arkko@ericsson.com'; </FONT>
<BR><FONT SIZE=3D2>&gt; 'Karl.norrmann@ericsson.com'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [MMUSIC] Comments on =
draft-ietf-mmusic-kmgmt-ext-12.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois is right in pointing out that there is =
a known </FONT>
<BR><FONT SIZE=3D2>&gt; problem with SIP </FONT>
<BR><FONT SIZE=3D2>&gt; forking referred to as HERFP (Heterogeneous =
Error Response Forking </FONT>
<BR><FONT SIZE=3D2>&gt; Problem). RFC 3326 refers to it in its =
abstract.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We never got around to resolving this issue. =
However, as Francois </FONT>
<BR><FONT SIZE=3D2>&gt; suggests, there could be ways around it. If =
both UAs support </FONT>
<BR><FONT SIZE=3D2>&gt; 100rel the </FONT>
<BR><FONT SIZE=3D2>&gt; offer can be accepted in a provisional (e.g., =
183) response. Further </FONT>
<BR><FONT SIZE=3D2>&gt; negotiations could be carried out using PRACKs, =
and when the key </FONT>
<BR><FONT SIZE=3D2>&gt; management procedure completed, the UAS could =
finally accept </FONT>
<BR><FONT SIZE=3D2>&gt; the session </FONT>
<BR><FONT SIZE=3D2>&gt; with a 200 OK response for the INVITE.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; UAs that do not suppor 100rel would need to use =
a 200 OK or live with </FONT>
<BR><FONT SIZE=3D2>&gt; the HERFP, as Francois pointed out.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Francois Audet wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I have a 2 comments on </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-=
12.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-mmusic-=
kmgmt-ext-12.txt</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; .</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This first comment is for a =
clarification:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Section 3.1.2 explains that SIP 488 is =
used for rejecting a key</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; management offer.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; 488 allows for the inclusion =
of an SDP indicating the </FONT>
<BR><FONT SIZE=3D2>&gt; capabilities of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; answerer (the same way an SDP =
in a 200 OK sent in an </FONT>
<BR><FONT SIZE=3D2>&gt; OPTIONS request </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; indicates</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; capabilities). It would be =
desireable to explain how this </FONT>
<BR><FONT SIZE=3D2>&gt; works with</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; kmgmt. I assume that this is =
what is meant by wording </FONT>
<BR><FONT SIZE=3D2>&gt; saying &quot;Further </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; details</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; about the cause of failure MAY =
be described in an </FONT>
<BR><FONT SIZE=3D2>&gt; included message </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; from the key</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; management protocol.&quot; =
Perhaps a wording like the </FONT>
<BR><FONT SIZE=3D2>&gt; following would help:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Further details =
about the media capabilities of the offerer </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; MAY</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be in</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; included in 488 =
according to normal RFC 3261 rules. Further </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; details about</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the cause of the =
rejection of the key message itself MAY be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; described in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
key message in the SDP in the 488, according to the rules</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the key =
management protocol. The session is then ...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; ...or something along those =
lines.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; It would also be worthwile to =
describe how this relates to </FONT>
<BR><FONT SIZE=3D2>&gt; MIKEY in&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; particular (i.e, that the MIKEY message =
itself in the key-mgmt may </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; have&nbsp; the key management rejection =
reason). It would also </FONT>
<BR><FONT SIZE=3D2>&gt; be helpful </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to have&nbsp; an Example of a failure case =
for SIP 488/MIKEY.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----------------------</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This next comment is concerning a =
potential issue with SIP forking. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'm not sure we can fix it in MMUSIC, but =
I'll state it anyways.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - There is a somewhat unpleasant =
side-effect of using a SIP failure</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; response</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; for rejecting a key management =
message.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - Suppose that there is a SIP forking =
proxy forking the </FONT>
<BR><FONT SIZE=3D2>&gt; offer (in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; INVITE).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; Let's say the call is forked =
to A and B. A is a device </FONT>
<BR><FONT SIZE=3D2>&gt; for which no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; user is present at the time =
(say, an office phone). </FONT>
<BR><FONT SIZE=3D2>&gt; Suppose A rejects the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; call with 401 Unauthorized =
because it needs </FONT>
<BR><FONT SIZE=3D2>&gt; authorization. Suppose the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; user</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; is at home (B), but rejects =
the offer with 488 (because </FONT>
<BR><FONT SIZE=3D2>&gt; it's using the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; key</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; management protocol used for =
the corporation which is </FONT>
<BR><FONT SIZE=3D2>&gt; different than </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the one</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; used at home). The forking =
proxy will see both the 401 an </FONT>
<BR><FONT SIZE=3D2>&gt; the 488, but </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; can only</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; forward one to the offerer. =
There is nothing saying which </FONT>
<BR><FONT SIZE=3D2>&gt; one should </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be forwarded</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; beyong the error response that =
indicates that there could be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; retransmission (which</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; applies to both codes in this =
case). Worst, in this particular </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; example, if the proxy</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; follows the rule section 6/RFC =
3261, chances are it will </FONT>
<BR><FONT SIZE=3D2>&gt; pick 401. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This means</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; that you won't be able to call =
home because you'll never </FONT>
<BR><FONT SIZE=3D2>&gt; receive a 488.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - This is a weakness of the forking =
procedures in SIP, and </FONT>
<BR><FONT SIZE=3D2>&gt; perhaps it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; should be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; addresses in the SIP working =
group.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; - The other alternative would be to not =
consider the </FONT>
<BR><FONT SIZE=3D2>&gt; rejection of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; key as a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; rejection of the offer. =
Instead of sending a 488, you </FONT>
<BR><FONT SIZE=3D2>&gt; would accept the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; offer with an answer, and the =
key rejection would be </FONT>
<BR><FONT SIZE=3D2>&gt; included in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; key message</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; itself (which could then =
trigger another offer/answer). In other </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; words, the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; offer/answer is sucessful, but =
the key exchanged is not. </FONT>
<BR><FONT SIZE=3D2>&gt; This would </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; have the obvious</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; advantage of the previous =
scenario working properly. </FONT>
<BR><FONT SIZE=3D2>&gt; However, if there </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; is no</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; suitable key management =
protocol, we could run into the reverse </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; problem (when the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; user is at work (A) instead of =
(B). In this case, the proxy would </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; forward the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; 200 with the answer with the =
key message, and drop the 401. There </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; would be another</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; offer/answer round which would =
then fail. The caller in this case </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; would never get</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; the 401.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'm not sure how to deal with this forking =
issue.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
----------------------------------------------------------------------</=
FONT>
<BR><FONT SIZE=3D2>&gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mmusic mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/mmusic" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/mmusic</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo =
Camarillo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone :&nbsp; =
+358&nbsp; 9 299 33 71</FONT>
<BR><FONT SIZE=3D2>&gt; Oy L M Ericsson =
Ab&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile:&nbsp; +358 40 702 =
35 35</FONT>
<BR><FONT SIZE=3D2>&gt; Telecom =
R&amp;D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; Fax&nbsp;&nbsp; :&nbsp; +358&nbsp; 9 299 30 =
52</FONT>
<BR><FONT SIZE=3D2>&gt; FIN-02420 =
Jorvas&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Email =
:&nbsp; Gonzalo.Camarillo@ericsson.com</FONT>
<BR><FONT SIZE=3D2>&gt; =
Finland&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.hut.fi/~gonzalo" =
TARGET=3D"_blank">http://www.hut.fi/~gonzalo</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4FDC4.98D5C321--


--===============2011351460==
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

--===============2011351460==--



From mmusic-bounces@ietf.org  Tue Jan 18 20:34:03 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 UAA29108
	for <mmusic-web-archive@ietf.org>; Tue, 18 Jan 2005 20:34:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr4ys-00038P-5O
	for mmusic-web-archive@ietf.org; Tue, 18 Jan 2005 20:49:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr4iU-0002Ko-21; Tue, 18 Jan 2005 20:33:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr4hC-00023p-JJ; Tue, 18 Jan 2005 20:31:42 -0500
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 UAA28901;
	Tue, 18 Jan 2005 20:31:40 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cr4wZ-00034t-Jq; Tue, 18 Jan 2005 20:47:35 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0J1Ukh15764; Tue, 18 Jan 2005 20:30:46 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y0S98VS5>; Tue, 18 Jan 2005 20:30:47 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF0155A1CD@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Cullen Jennings'" <fluffy@cisco.com>,
        "'Henning Schulzrinne'"
	<hgs@cs.columbia.edu>,
        "'avt@ietf.org'" <avt@ietf.org>, "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: RE: [MMUSIC] Re: [AVT] Application sharing - a first protocol dra ft
Date: Tue, 18 Jan 2005 20:30:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
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="===============0467107299=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0467107299==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4FDC6.7E67950C"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4FDC6.7E67950C
Content-Type: text/plain

I believe section 4 suggests that normally this would be RTP transported
over TCP, not over UDP.

> -----Original Message-----
> From: mmusic-bounces@ietf.org 
> [mailto:mmusic-bounces@ietf.org] On Behalf Of Cullen Jennings
> Sent: Tuesday, January 18, 2005 15:34
> To: Henning Schulzrinne; avt@ietf.org; mmusic@ietf.org
> Subject: [MMUSIC] Re: [AVT] Application sharing - a first 
> protocol draft
> 
> 
> 
> Interesting stuff. 
> 
> Why would you use UDP for this?
> 
> Have you had a look at VNC?
> 
> 
> On 1/13/05 10:50 AM, "Henning Schulzrinne" 
> <hgs@cs.columbia.edu> wrote:
> 
> > We have put together an initial draft on how to do applicationg 
> > sharing, at the pixel level. For reasons discussed also in 
> our earlier 
> > requirements document 
> > 
> (http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sharing-
> > 00.txt),
> > we believe that this is closely related to remote access to 
> applications
> > and that timing information is relevant. Thus, the initial draft
> > primarily defines RTP payload types. Until the draft appears in the
> > archives, you can find it at
> > 
> > 
> http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing-00.tx
> > t
> > 
> > Note that this type of application sharing is 
> application-neutral and 
> > application-unaware, i.e., this is not a "shared whiteboard" or 
> > "shared editor" protocol.
> > 
> > We would appreciate your comments and suggestions.
> > 
> > Henning
> > 
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www1.ietf.org/mailman/listinfo/avt
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 

------_=_NextPart_001_01C4FDC6.7E67950C
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [MMUSIC] Re: [AVT] Application sharing - a first protocol =
draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I believe section 4 suggests that normally this would =
be RTP transported</FONT>
<BR><FONT SIZE=3D2>over TCP, not over UDP.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: mmusic-bounces@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</=
A>] On Behalf Of Cullen Jennings</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, January 18, 2005 15:34</FONT>
<BR><FONT SIZE=3D2>&gt; To: Henning Schulzrinne; avt@ietf.org; =
mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [MMUSIC] Re: [AVT] Application sharing =
- a first </FONT>
<BR><FONT SIZE=3D2>&gt; protocol draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Interesting stuff. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Why would you use UDP for this?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Have you had a look at VNC?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On 1/13/05 10:50 AM, &quot;Henning =
Schulzrinne&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;hgs@cs.columbia.edu&gt; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; We have put together an initial draft on =
how to do applicationg </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sharing, at the pixel level. For reasons =
discussed also in </FONT>
<BR><FONT SIZE=3D2>&gt; our earlier </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; requirements document </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; (<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-schulzrinne-mmusic-sha=
ring-" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-schulzrinne-=
mmusic-sharing-</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 00.txt),</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; we believe that this is closely related to =
remote access to </FONT>
<BR><FONT SIZE=3D2>&gt; applications</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; and that timing information is relevant. =
Thus, the initial draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; primarily defines RTP payload types. Until =
the draft appears in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; archives, you can find it at</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-app-sharing=
-00.tx" =
TARGET=3D"_blank">http://www1.cs.columbia.edu/~lennox/draft-lennox-avt-a=
pp-sharing-00.tx</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; t</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Note that this type of application sharing =
is </FONT>
<BR><FONT SIZE=3D2>&gt; application-neutral and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; application-unaware, i.e., this is not a =
&quot;shared whiteboard&quot; or </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;shared editor&quot; protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; We would appreciate your comments and =
suggestions.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Henning</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Audio/Video Transport Working Group</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; avt@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/avt" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/avt</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; mmusic mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/mmusic" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/mmusic</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4FDC6.7E67950C--


--===============0467107299==
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

--===============0467107299==--



From mmusic-bounces@ietf.org  Wed Jan 19 02:07:31 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 CAA23100
	for <mmusic-web-archive@ietf.org>; Wed, 19 Jan 2005 02:07:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CrABb-0001gd-Q4
	for mmusic-web-archive@ietf.org; Wed, 19 Jan 2005 02:23:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cr9v5-00081M-ES; Wed, 19 Jan 2005 02:06:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cr9qC-0005ai-PS
	for mmusic@megatron.ietf.org; Wed, 19 Jan 2005 02:01:20 -0500
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 CAA18117
	for <mmusic@ietf.org>; Wed, 19 Jan 2005 02:01:19 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrA5b-0001aM-47
	for mmusic@ietf.org; Wed, 19 Jan 2005 02:17:17 -0500
Received: from esealmw126.eemea.ericsson.se ([153.88.254.123])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0J719O6020859; Wed, 19 Jan 2005 08:01:09 +0100
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 19 Jan 2005 08:01:08 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.13]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 19 Jan 2005 08:01:08 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 60369189CC; Wed, 19 Jan 2005 09:01:06 +0200 (EET)
Message-ID: <41EE05B2.5070309@ericsson.com>
Date: Wed, 19 Jan 2005 09:01:06 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-kmgmt-ext-12.txt
References: <1ECE0EB50388174790F9694F77522CCF0155A1CA@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0155A1CA@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2005 07:01:08.0512 (UTC)
	FILETIME=[A6C6F200:01C4FDF4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Content-Transfer-Encoding: 7bit
Cc: "'jari.arkko@ericsson.com'" <jari.arkko@ericsson.com>,
        "'elisabetta.carrara@ericasson.com'"
	<elisabetta.carrara@ericasson.com.cnri.reston.va.us>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'Mats.naslund@ericsson.com'" <Mats.naslund@ericsson.com>,
        "'Karl.norrmann@ericsson.com'" <Karl.norrmann@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: f0b5a4216bfa030ed8a6f68d1833f8ae
Content-Transfer-Encoding: 7bit

Hi,

additionally, the authors of this draft may want to have a look at the 
security preconditions draft:
http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-securityprecondition-02.txt

This type of precondition keeps the callee from being alerted until the 
crypto stuff is ready.

Regards,

Gonzalo

Francois Audet wrote:

> Thank you Gonzalo!
> 
> I agree with what you are saying as a way around the HERPF problem for
> keymgmt. This is what I had in mind.
> 
> As Gonzalo describes, we need to accept the offer (even if we are
> rejecting the keymgmt) instead of sending the 488.
> 
> The answerer would send a provisional response (e.g., 183) with the
> SDP-Answer. In the SDP-Answer, the a=key-mgmt:mikey attribute is included,
> but instead of the keying material, I would assume it would have the
> rejection. For example, I would assume that a proper value in the MIKEY 
> error
> payload (ERR) for that purpose already exists.
> 
> After that, the keying information can be renegotiated using additionnal
> offer/answer cycles (I think UPDATE/re-INVITE would be appropriate).
> 
> In other words, 488 is rejecting the session completely. But to reject
> just the keymgmt (and keep the session) you would reject explicitly
> the keymgmt using the native keymgmt procedures (e.g., MIKEY).
> 
> This would be a small change to kmgmt section 3.1.2.
> 
> I don't think there are any other alternatives. Waiting for a general
> solution to the HERPF problem does not seem acceptable to me, because
> it won't be backward compatible and because it may take a very long
> time. Also, to me it seems logical that we accept the Offer, but reject the
> key. It really should be the same dialog, but with additional MIKEY 
> interactions.
> It really emphases the strenght of MIKEY as a key management protocol.
> 
> Let me know if you think this is a good idea. I can certainly help with the
> wording.
> 
> 
> 
>  > -----Original Message-----
>  > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
>  > Sent: Saturday, January 15, 2005 00:41
>  > To: Audet, Francois [SC100:9T51:EXCH]
>  > Cc: 'mmusic@ietf.org'; 'elisabetta.carrara@ericasson.com';
>  > 'Mats.naslund@ericsson.com'; 'jari.arkko@ericsson.com';
>  > 'Karl.norrmann@ericsson.com'
>  > Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-kmgmt-ext-12.txt
>  >
>  >
>  > Hi,
>  >
>  > Francois is right in pointing out that there is a known
>  > problem with SIP
>  > forking referred to as HERFP (Heterogeneous Error Response Forking
>  > Problem). RFC 3326 refers to it in its abstract.
>  >
>  > We never got around to resolving this issue. However, as Francois
>  > suggests, there could be ways around it. If both UAs support
>  > 100rel the
>  > offer can be accepted in a provisional (e.g., 183) response. Further
>  > negotiations could be carried out using PRACKs, and when the key
>  > management procedure completed, the UAS could finally accept
>  > the session
>  > with a 200 OK response for the INVITE.
>  >
>  > UAs that do not suppor 100rel would need to use a 200 OK or live with
>  > the HERFP, as Francois pointed out.
>  >
>  > Regards,
>  >
>  > Gonzalo
>  >
>  >
>  >
>  > Francois Audet wrote:
>  >
>  > > Hi,
>  > >
>  > > I have a 2 comments on
>  > >
>  > http://www.ietf.org/internet-drafts/draft-ietf-mmusic-kmgmt-ext-12.txt
>  > > .
>  > >
>  > >
>  > > This first comment is for a clarification:
>  > >
>  > > - Section 3.1.2 explains that SIP 488 is used for rejecting a key
>  > > management offer.
>  > >   488 allows for the inclusion of an SDP indicating the
>  > capabilities of the
>  > >   answerer (the same way an SDP in a 200 OK sent in an
>  > OPTIONS request
>  > > indicates
>  > >   capabilities). It would be desireable to explain how this
>  > works with
>  > >   kmgmt. I assume that this is what is meant by wording
>  > saying "Further
>  > > details
>  > >   about the cause of failure MAY be described in an
>  > included message
>  > > from the key
>  > >   management protocol." Perhaps a wording like the
>  > following would help:
>  > >
>  > >         Further details about the media capabilities of the offerer
>  > > MAY
>  > > be in
>  > >         included in 488 according to normal RFC 3261 rules. Further
>  > > details about
>  > >         the cause of the rejection of the key message itself MAY be
>  > > described in
>  > >       the key message in the SDP in the 488, according to the rules
>  > >         of the key management protocol. The session is then ...
>  > >
>  > >  ...or something along those lines.
>  > >
>  > >  It would also be worthwile to describe how this relates to
>  > MIKEY in 
>  > > particular (i.e, that the MIKEY message itself in the key-mgmt may
>  > > have  the key management rejection reason). It would also
>  > be helpful
>  > > to have  an Example of a failure case for SIP 488/MIKEY.
>  > > 
>  > > -----------------------
>  > >
>  > > This next comment is concerning a potential issue with SIP forking.
>  > > I'm not sure we can fix it in MMUSIC, but I'll state it anyways.
>  > >
>  > > - There is a somewhat unpleasant side-effect of using a SIP failure
>  > > response
>  > >   for rejecting a key management message.
>  > >
>  > > - Suppose that there is a SIP forking proxy forking the
>  > offer (in the
>  > > INVITE).
>  > >   Let's say the call is forked to A and B. A is a device
>  > for which no
>  > >   user is present at the time (say, an office phone).
>  > Suppose A rejects the
>  > >   call with 401 Unauthorized because it needs
>  > authorization. Suppose the
>  > > user
>  > >   is at home (B), but rejects the offer with 488 (because
>  > it's using the
>  > > key
>  > >   management protocol used for the corporation which is
>  > different than
>  > > the one
>  > >   used at home). The forking proxy will see both the 401 an
>  > the 488, but
>  > > can only
>  > >   forward one to the offerer. There is nothing saying which
>  > one should
>  > > be forwarded
>  > >   beyong the error response that indicates that there could be
>  > > retransmission (which
>  > >   applies to both codes in this case). Worst, in this particular
>  > > example, if the proxy
>  > >   follows the rule section 6/RFC 3261, chances are it will
>  > pick 401.
>  > > This means
>  > >   that you won't be able to call home because you'll never
>  > receive a 488.
>  > >
>  > > - This is a weakness of the forking procedures in SIP, and
>  > perhaps it
>  > > should be
>  > >   addresses in the SIP working group.
>  > >
>  > > - The other alternative would be to not consider the
>  > rejection of the
>  > > key as a
>  > >   rejection of the offer. Instead of sending a 488, you
>  > would accept the
>  > >   offer with an answer, and the key rejection would be
>  > included in the
>  > > key message
>  > >   itself (which could then trigger another offer/answer). In other
>  > > words, the
>  > >   offer/answer is sucessful, but the key exchanged is not.
>  > This would
>  > > have the obvious
>  > >   advantage of the previous scenario working properly.
>  > However, if there
>  > > is no
>  > >   suitable key management protocol, we could run into the reverse
>  > > problem (when the
>  > >   user is at work (A) instead of (B). In this case, the proxy would
>  > > forward the
>  > >   200 with the answer with the key message, and drop the 401. There
>  > > would be another
>  > >   offer/answer round which would then fail. The caller in this case
>  > > would never get
>  > >   the 401.
>  > >
>  > > I'm not sure how to deal with this forking issue.
>  > >
>  > >
>  > >
>  > ----------------------------------------------------------------------
>  > > --
>  > >
>  > > _______________________________________________
>  > > 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
>  >
>  >
>  >
> 

-- 
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  Wed Jan 19 03:09:31 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 DAA20069
	for <mmusic-web-archive@ietf.org>; Wed, 19 Jan 2005 03:09:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CrB9c-0002wJ-Mo
	for mmusic-web-archive@ietf.org; Wed, 19 Jan 2005 03:25:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrApU-000823-Ux; Wed, 19 Jan 2005 03:04:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CrAoD-0007pY-LE
	for mmusic@megatron.ietf.org; Wed, 19 Jan 2005 03:03:22 -0500
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 DAA19655
	for <mmusic@ietf.org>; Wed, 19 Jan 2005 03:03:19 -0500 (EST)
Received: from mailgate2.ebu.ch ([194.158.3.232])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrB3c-0002nG-Kx
	for mmusic@ietf.org; Wed, 19 Jan 2005 03:19:18 -0500
Received: from gnvasrelay1b.gva.ebu.ch (unverified [10.73.222.59]) by 
	mailgate2.ebu.ch (Content Technologies SMTPRS 4.3.14) with ESMTP id 
	<T6e969d42b3c29e03e856c@mailgate2.ebu.ch>; Wed, 19 Jan 2005 09:01:31 
	+0100
Received: from gnvasmail1a.gva.ebu.ch ([10.73.222.209]) by 
	gnvasrelay1b.gva.ebu.ch with Microsoft SMTPSVC (5.0.2195.6713); Wed, 19 
	Jan 2005 09:02:42 +0100
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] Potential IPR relating to
	draft-ietf-mmusic-img-req-07.txt
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
Date: Wed, 19 Jan 2005 09:02:42 +0100
Message-ID: <9BB211A65FCBFD43B95F67BA2485759DFB8E97@gnvasmail1a.gva.ebu.ch>
Thread-Topic: [MMUSIC] Potential IPR relating to 
	draft-ietf-mmusic-img-req-07.txt
Thread-Index: AcT9tOXqZctg+LQSTvmKELEuZZpmuQAR9nQw
From: "Evain, Jean-Pierre" <evain@ebu.ch>
To: "Colin Perkins" <csp@csperkins.org>,
        "IETF MMUSIC Working Group" 
	<mmusic@ietf.org>
X-OriginalArrivalTime: 19 Jan 2005 08:02:42.0910 (UTC) 
	FILETIME=[40CF57E0:01C4FDFD]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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.2 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable

Colin,

Thanks for the useful information.

Correct me if I am wrong but this is just an application filed early 2002.
The patent has not be granted yet. There is a lot of anteriority on this
subject and I would be surprised that such a patent is ever assessed as
"essential" by a patent pool doing a thorough research.

Jean-Pierre

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of
Colin Perkins
Sent: mercredi, 19. janvier 2005 00:12
To: IETF MMUSIC Working Group
Subject: [MMUSIC] Potential IPR relating to draft-ietf-mmusic-img-req-07.txt


Folks,

We've been informed by the secretariat that a third-party IPR=20
disclosure has been made relating to draft-ietf-mmusic-img-req-07.txt.=20
Details can be found at=20
https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=3D520

Colin


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


**********************************************************************
 This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************
=20


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


From mmusic-bounces@ietf.org  Mon Jan 24 01:05:08 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 BAA24008
	for <mmusic-web-archive@ietf.org>; Mon, 24 Jan 2005 01:05:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Csxc1-00087R-Ka
	for mmusic-web-archive@ietf.org; Mon, 24 Jan 2005 01:22:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CsxJX-00062P-2m; Mon, 24 Jan 2005 01:03:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsxJ1-0005yv-B2
	for mmusic@megatron.ietf.org; Mon, 24 Jan 2005 01:02:31 -0500
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 BAA23902
	for <mmusic@ietf.org>; Mon, 24 Jan 2005 01:02:29 -0500 (EST)
Received: from auds952.usa.alcatel.com ([143.209.238.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsxZS-00082J-Lw
	for mmusic@ietf.org; Mon, 24 Jan 2005 01:19:31 -0500
Received: from srsdmail01.PVNS.COM (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j0O61tvE027971; Mon, 24 Jan 2005 00:01:55 -0600 (CST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Sun, 23 Jan 2005 22:01:55 -0800
Message-ID: <758B5A159B385447B4F950DE72D7D7AD678C2F@srsdmail01.PVNS.COM>
Thread-Topic: Question on the Usage of Feature Tags in
	draft-ietf-mmusic-rfc2326bis-08.txt
Thread-Index: AcTrOegZBxnDuX4DRtqaD9NDQ5OmWAWoBi5Q
From: "Thomas Zeng" <zeng@pvnetsolutions.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable
Cc: mmusic@ietf.org
Subject: [MMUSIC] RE: Question on the Usage of Feature Tags in
	draft-ietf-mmusic-rfc2326bis-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.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: quoted-printable

Hi Magnus:

A belated reply is inlined.

Thanks,
-Thomas

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Saturday, December 25, 2004 7:47 AM
> To: Thomas Zeng
> Cc: mmusic@ietf.org
> Subject: Re: Question on the Usage of Feature Tags in=20
> draft-ietf-mmusic-rfc2326bis-08.txt
>=20
>=20
> Hi Thomas,
>=20
> My intention with "Supported" is that these are not linked to=20
> the URI,=20
> and instead describe features supported by the client and server=20
> depending on the direction of the message.
>=20
> In the case one has features that are media type specific, the ones=20
> understanding the features, knows that it is media specific. Also the=20
> definer of a feature must consider if further negotiation of the=20
> functionality is needed. The Supported mechanism is really only a=20
> mechanism for intial discovery of support of features. It has the=20
> meaning like: Hey, here is what I support, please send me=20
> what you can.
>=20
> So I could see that one clarifies this in the next version, I would=20
> propose to make the following change in the section 14.43, see last=20
> sentencte of paragraph 2:
>=20
>     The Supported header field enumerates all the extensions=20
> supported by
>     the client or server using feature tags. The header carries the
>     extensions supported by the message sending entity.  The Supported
>     header MAY be included in any request.  When present in a request,
>     the receiver MUST respond with its corresponding Supported header.
>     Note, also in 4xx and 5xx responses is the supported=20
> header included.
>=20
>     The Supported header field contains a list of=20
> feature-tags, described
>     in Section 3.7, that are understood by the client or=20
> server. The list
>     is not depending on the request URI context, and=20
> describes the client
>     and server capabilities in general.
>=20
> What do you say?

This looks OK to us.
>=20
> Merry Chrismtas and a Happy new Year
>=20
> Magnus
>=20
>=20
> Thomas Zeng wrote:
> > Hello Magnus:
> > =20
> > Merry Christmas.
> > =20
> > We have been looking at the subject of capability handling=20
> which led us=20
> > to RFC2326bis-08, Chapter 10, where it is suggested that=20
> the server uses=20
> > the Supported header to advertise the list of feature tags=20
> it is capable=20
> > of handling.
> > =20
> > It is worth clarifying whether the list of tags in the Supported=20
> > header should be a function of  the request URL or not.
> > =20
> > For instance, if a client issues a DESCRIBE on a audio only=20
> request URL,=20
> > and the server in its 200 OK response includes the feature tag=20
> > "com.A_company.video-bit-stream-switching". Is that appropriate?
> > =20
> > Clearly video-bit-stream-switching does not apply to an=20
> audio-only URL,=20
> > but one could argue that video-bit-stream-switching is one of the=20
> > server's capabilities and the client may choose to take=20
> advantage of it=20
> > later on.
> > =20
> > What is your interpretation? What does the group think?
> > =20
> > Thanks,
> > -Thomas
>=20
>=20
> --=20
>=20
> Magnus Westerlund
>=20
> 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
>=20
>=20

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


From mmusic-bounces@ietf.org  Mon Jan 24 03:38:00 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 DAA17722
	for <mmusic-web-archive@ietf.org>; Mon, 24 Jan 2005 03:38:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ct000-0003XD-4u
	for mmusic-web-archive@ietf.org; Mon, 24 Jan 2005 03:55:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CszfH-0002Qg-2e; Mon, 24 Jan 2005 03:33:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CszdJ-0002CX-LA; Mon, 24 Jan 2005 03:31:37 -0500
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 DAA17358;
	Mon, 24 Jan 2005 03:31:34 -0500 (EST)
Received: from ns.live.com ([66.80.62.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Csztl-0003Nc-5l; Mon, 24 Jan 2005 03:48:38 -0500
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.13.1/8.12.11) with ESMTP id j0O8VMBL005556;
	Mon, 24 Jan 2005 00:31:22 -0800 (PST) (envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.13.1/8.12.9/Submit) id j0O8VMOV005555;
	Mon, 24 Jan 2005 00:31:22 -0800 (PST) (envelope-from rsf)
Message-Id: <6.2.0.14.1.20050124002039.0293e240@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Mon, 24 Jan 2005 00:30:10 -0800
To: avt@ietf.org, mmusic@ietf.org
From: Ross Finlayson <finlayson@live.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [MMUSIC] Representing Boolean MIME-type parameters in 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: 9466e0365fc95844abaf7c3f15a05c7d

I recently encountered a MPEG-4 video + AMR audio RTSP/RTP session whose 
SDP lines contained the following (for the AMR audio stream):

	a=rtpmap:97 AMR/8000
...
	a=fmtp:97 octet-align

Is that last line legal?  I had thought that only the following would be legal:
	a=fmtp:97 octet-align=1

RFC 3267 (which defines the RTP payload format for AMR) defines the 
"octet-align" MIME parameter as follows:
	"octet-align: Permissible values are 0 and 1."

So, for Boolean MIME parameters like this, is it permissible to omit the 
value assignment in the SDP "a=fmtp:" line, thereby assuming the value 
1?  I had assumed not (and in fact our own RTSP client code got confused by 
the example above), but it would be nice to get some clarification of this 
question, in case examples like the one above become commonplace.

	Ross Finlayson
	LIVE.COM
	<http://www.live.com/>


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


From mmusic-bounces@ietf.org  Mon Jan 24 04:58:12 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 EAA22750
	for <mmusic-web-archive@ietf.org>; Mon, 24 Jan 2005 04:58:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ct1Fc-0005hg-Jz
	for mmusic-web-archive@ietf.org; Mon, 24 Jan 2005 05:15:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ct0tm-00017z-Jt; Mon, 24 Jan 2005 04:52:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ct0pn-0000fc-3a; Mon, 24 Jan 2005 04:48:35 -0500
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 EAA21851;
	Mon, 24 Jan 2005 04:48:32 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ct16F-0005Pe-8G; Mon, 24 Jan 2005 05:05:37 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0O9mVh5005808; Mon, 24 Jan 2005 10:48:31 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Jan 2005 10:48:31 +0100
Received: from [147.214.34.55] (research-1fd0e1.ki.sw.ericsson.se
	[147.214.34.55]) by esealnt610.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id DL9J323Y; Mon, 24 Jan 2005 10:48:27 +0100
Message-ID: <41F4C46A.5000503@ericsson.com>
Date: Mon, 24 Jan 2005 10:48:26 +0100
X-Sybari-Trust: bf2eb586 b8ec86c7 ffd13dea 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ross Finlayson <finlayson@live.com>
References: <6.2.0.14.1.20050124002039.0293e240@localhost>
In-Reply-To: <6.2.0.14.1.20050124002039.0293e240@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2005 09:48:31.0707 (UTC)
	FILETIME=[DD0DA2B0:01C501F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
Cc: avt@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Re: [AVT] Representing Boolean MIME-type parameters in 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: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit

Hi Ross,

It is required for RTP media types to have values. This is due to the 
following in RFC 3555:

"3. Mapping to SDP Parameters

    The representation of a MIME media type is specified in the syntax of
    the Content-Type header field in RFC 2045 [6] as follows:

       type "/" subtype  *(";" parameter)

    Parameters may be required for a particular type or subtype or they
    may be optional.  For media types which represent RTP payload
    formats, the parameters "rate", "channels", "ptime", and "maxptime"
    have general definitions (given above) that may apply across types
    and subtypes.  The format for a parameter is specified in RFC 2045 as

       attribute "=" value

    where attribute is the parameter name and the permissible values are
    specified for each parameter.  The value may need to be a quoted
    string if it contains any of the special characters listed in RFC
    2045."


So the usage you have witnessed is ilegal.

Cheers

Magnus


Ross Finlayson wrote:
> I recently encountered a MPEG-4 video + AMR audio RTSP/RTP session whose 
> SDP lines contained the following (for the AMR audio stream):
> 
> 	a=rtpmap:97 AMR/8000
> ...
> 	a=fmtp:97 octet-align
> 
> Is that last line legal?  I had thought that only the following would be legal:
> 	a=fmtp:97 octet-align=1
> 
> RFC 3267 (which defines the RTP payload format for AMR) defines the 
> "octet-align" MIME parameter as follows:
> 	"octet-align: Permissible values are 0 and 1."
> 
> So, for Boolean MIME parameters like this, is it permissible to omit the 
> value assignment in the SDP "a=fmtp:" line, thereby assuming the value 
> 1?  I had assumed not (and in fact our own RTSP client code got confused by 
> the example above), but it would be nice to get some clarification of this 
> question, in case examples like the one above become commonplace.
> 
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 


-- 

Magnus Westerlund

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

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


From mmusic-bounces@ietf.org  Tue Jan 25 07:24:39 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 HAA28228
	for <mmusic-web-archive@ietf.org>; Tue, 25 Jan 2005 07:24:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtQ15-0006ry-SN
	for mmusic-web-archive@ietf.org; Tue, 25 Jan 2005 07:41:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtPiT-0003i6-R8; Tue, 25 Jan 2005 07:22:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtPaI-0001Hy-5T
	for mmusic@megatron.ietf.org; Tue, 25 Jan 2005 07:14:14 -0500
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 HAA27557
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 07:14:11 -0500 (EST)
From: Rod.Walsh@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtPqz-0006WY-TU
	for mmusic@ietf.org; Tue, 25 Jan 2005 07:31:30 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j0PCDol03486; Tue, 25 Jan 2005 14:13:52 +0200 (EET)
X-Scanned: Tue, 25 Jan 2005 14:22:55 +0200 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id j0PCMtsf017037;
	Tue, 25 Jan 2005 14:22:55 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00Thta8C; Tue, 25 Jan 2005 14:21:55 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	j0PCBwU17046; Tue, 25 Jan 2005 14:11:58 +0200 (EET)
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 25 Jan 2005 14:11:39 +0200
Received: from trebe051.NOE.Nokia.com ([172.22.124.60]) by
	esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 25 Jan 2005 14:11:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Potential IPR relating todraft-ietf-mmusic-img-req-07.txt
Date: Tue, 25 Jan 2005 14:11:38 +0200
Message-ID: <B3C148BF4CBD19489565161DF52D7963DA0E40@trebe051.ntc.nokia.com>
Thread-Topic: [MMUSIC] Potential IPR relating to
	draft-ietf-mmusic-img-req-07.txt
Thread-Index: AcT9tOXqZctg+LQSTvmKELEuZZpmuQAR9nQwASoT6OA=
To: <evain@ebu.ch>, <csp@csperkins.org>
X-OriginalArrivalTime: 25 Jan 2005 12:11:38.0949 (UTC)
	FILETIME=[05DC8750:01C502D7]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
Cc: hardie@qualcomm.com, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable

Hi Jean-Pierre, Colin et al.

I took a brief look and yes, it was filed Jan.2002.

As is, I do not see this as any threat whatsoever. Given the prior =
existence of SDP/SAP, MPEG2-PSI and DVB-SI (and others), it is unclear =
what new aspect is introduced. I am told that patents can undergo =
massive transformations between initial filing and any granted version =
so my opinions on the level of novelty might well become irrelevant =
compared to any updated version. So at the moment, it's hard to say =
anything except "no threat perceived" and "no compelling technology we =
to adopt that wasn't available earlier".

PS. It was good to see this in plenty of time before any standard track =
IMG documents are chartered - thanks Ted.

Cheers, Rod.



> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org]On Behalf
> Of ext Evain, Jean-Pierre
> Sent: Wednesday, January 19, 2005 10:03 AM
> To: Colin Perkins; IETF MMUSIC Working Group
> Subject: RE: [MMUSIC] Potential IPR relating
> todraft-ietf-mmusic-img-req-07.txt
>=20
>=20
> Colin,
>=20
> Thanks for the useful information.
>=20
> Correct me if I am wrong but this is just an application=20
> filed early 2002.
> The patent has not be granted yet. There is a lot of=20
> anteriority on this
> subject and I would be surprised that such a patent is ever=20
> assessed as
> "essential" by a patent pool doing a thorough research.
>=20
> Jean-Pierre
>=20
> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org] On Behalf Of
> Colin Perkins
> Sent: mercredi, 19. janvier 2005 00:12
> To: IETF MMUSIC Working Group
> Subject: [MMUSIC] Potential IPR relating to=20
> draft-ietf-mmusic-img-req-07.txt
>=20
>=20
> Folks,
>=20
> We've been informed by the secretariat that a third-party IPR=20
> disclosure has been made relating to=20
> draft-ietf-mmusic-img-req-07.txt.=20
> Details can be found at=20
> https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=3D520
>=20
> Colin
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20
>=20
> **********************************************************************
>  This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>=20
> **********************************************************************
> =20
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20

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


From mmusic-bounces@ietf.org  Tue Jan 25 13:47:15 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 NAA27505
	for <mmusic-web-archive@ietf.org>; Tue, 25 Jan 2005 13:47:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtVzQ-0003fL-4A
	for mmusic-web-archive@ietf.org; Tue, 25 Jan 2005 14:04:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtVes-0008Rb-QH; Tue, 25 Jan 2005 13:43:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtVeE-0008Hu-Kc
	for mmusic@megatron.ietf.org; Tue, 25 Jan 2005 13:42:42 -0500
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 NAA27048
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 13:42:38 -0500 (EST)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtVuw-0003SM-Di
	for mmusic@ietf.org; Tue, 25 Jan 2005 13:59:59 -0500
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j0PIjMAO022996
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 11:45:22 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j0PIgn8p015044
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 12:42:50 -0600 (CST)
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWSMZ78>; Wed, 26 Jan 2005 00:12:22 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245C22@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        "'mmusic@ietf.org'"
	<mmusic@ietf.org>
Date: Wed, 26 Jan 2005 00:12:21 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: "'fandreas@cisco.com'" <fandreas@cisco.com>,
        "'Karl Norrman \(KI/EAB\)'" <karl.norrman@ericsson.com>,
        "'David A. McGrew'" <mcgrew@cisco.com>,
        "'dwing@cisco.com'" <dwing@cisco.com>
Subject: [MMUSIC] MKI length and MKI format
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

Mark and MMUSIC community

Ref: <draft-ietf-mmusic-sdescriptions-08.txt> Section:5.1 Page:14

It was specified in the draft that the MKI length is the size of the MKI
field in the SRTP packet, specified in Bytes. And the upper limit for that
value is 128 Bytes. Is it (128) Bytes or (128) bits? What is the intention
of keeping such a big value for the MKI length value?

Also what is the data type of MKI? Is it an "integer" of length specified by
MKI-Length or a "byte string" of length specified by MKI-Length?

According to the example "1026:4" given in the draft, it was said that the
example assigns to the key a master key identifier of 1026 that is 4 bytes
long. In this case what is the value of MKI filed in each SRTP packet? Is it
"1026" or "0402" (where 1026 = 0x0402)?

Please clarify me in this regard.

Regards
Srikanth





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


From mmusic-bounces@ietf.org  Tue Jan 25 14:17:20 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 OAA29367
	for <mmusic-web-archive@ietf.org>; Tue, 25 Jan 2005 14:17:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtWSX-0004aX-7o
	for mmusic-web-archive@ietf.org; Tue, 25 Jan 2005 14:34:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtW2r-0003LD-5L; Tue, 25 Jan 2005 14:08:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtW04-000318-Cr
	for mmusic@megatron.ietf.org; Tue, 25 Jan 2005 14:05:16 -0500
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 OAA28473
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 14:05:15 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtWGp-0004E4-Su
	for mmusic@ietf.org; Tue, 25 Jan 2005 14:22:36 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 25 Jan 2005 11:10:31 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0PJ4al2012624;
	Tue, 25 Jan 2005 11:04:36 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn6-559.cisco.com [10.21.122.47])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0PJ0pn4012683;
	Tue, 25 Jan 2005 11:00:51 -0800
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245C22@zin24exm01.ap.mot.com>
References: <772BCEF88A1DD91191F80011856715F3245C22@zin24exm01.ap.mot.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F4ED044C-6F03-11D9-9EA5-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Date: Tue, 25 Jan 2005 11:04:36 -0800
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106679651.835659"; x:"432200"; a:"rsa-sha1"; b:"nofws:1611";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"rUNuJlAt7wEIwMn1uhhIfOJtyDLMRqucNwdA91/FmMmyUn+eEaoqrwgnscabnakHX2QFss9F"
	"RFoZ+M/iTW8zSonW5blYwV+yIFf9HYpD+0n+7r58EvY0dgnnASj5uRxkZknwpb4cNkzme23huB0"
	"iqdzq5FkbxRPV/979NDSMPFo=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: MKI length and MKI format";
	c:"Date: Tue, 25 Jan 2005 11:04:36 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc: "'fandreas@cisco.com'" <fandreas@cisco.com>,
        "'David A. McGrew'" <mcgrew@cisco.com>,
        "'dwing@cisco.com'" <dwing@cisco.com>,
        "'Karl Norrman \(KI/EAB\)'" <karl.norrman@ericsson.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: [MMUSIC] Re: MKI length and MKI format
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

hi Srikanth,

On Jan 25, 2005, at 10:42 AM, Vavilapalli Srikanth-A19563 wrote:

> Mark and MMUSIC community
>
> Ref: <draft-ietf-mmusic-sdescriptions-08.txt> Section:5.1 Page:14
>
> It was specified in the draft that the MKI length is the size of the 
> MKI
> field in the SRTP packet, specified in Bytes. And the upper limit for 
> that
> value is 128 Bytes. Is it (128) Bytes or (128) bits?

It's in bytes, that's clear.
> What is the intention
> of keeping such a big value for the MKI length value?

It has a high upper bound in order to help with possible future 
migration of digital TV services to IP networks.  I expect that two or 
four bytes would be the typical value.  We made the upper bound 
configurable in the SRTP specification owing to the practice found in 
TV conditional access systems that use a key indicator to encode a 
variety of information for a broadcast receiver.  I was told by people 
from NDS and Nagra that they would prefer the size to be configurable.  
We did not see any reason why it should not be, but we have not yet 
seen any applications materialize for this particular feature.  I'd be 
interested to know what the Motorola Digicipher folks think - when they 
think about video over IP.

I cannot imagine that the MKI will serve any telephony purpose 
whatsoever.  The default size is zero and this is what is mandatory to 
implement (and test).

>
> Also what is the data type of MKI? Is it an "integer" of length 
> specified by
> MKI-Length or a "byte string" of length specified by MKI-Length?

It is a byte string.
>
> According to the example "1026:4" given in the draft, it was said that 
> the
> example assigns to the key a master key identifier of 1026 that is 4 
> bytes
> long. In this case what is the value of MKI filed in each SRTP packet? 
> Is it
> "1026" or "0402" (where 1026 = 0x0402)?

Sorry, we're using decimal and not hexadecimal.  That should have been 
pointed out in the document.

Mark
>
> Please clarify me in this regard.
>
> Regards
> Srikanth
>

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


From mmusic-bounces@ietf.org  Tue Jan 25 18:23:15 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 SAA24903
	for <mmusic-web-archive@ietf.org>; Tue, 25 Jan 2005 18:23:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtaIY-0006S0-SP
	for mmusic-web-archive@ietf.org; Tue, 25 Jan 2005 18:40:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtZmH-00077z-5J; Tue, 25 Jan 2005 18:07:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtZlx-0006p5-7T
	for mmusic@megatron.ietf.org; Tue, 25 Jan 2005 18:06:57 -0500
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 SAA23185
	for <mmusic@ietf.org>; Tue, 25 Jan 2005 18:06:54 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cta2j-0005yq-Tr
	for mmusic@ietf.org; Tue, 25 Jan 2005 18:24:19 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 25 Jan 2005 15:14:15 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0PN6LNt009980;
	Tue, 25 Jan 2005 15:06:22 -0800 (PST)
Received: from [10.241.17.79] (che-vpn-cluster-2-95.cisco.com [10.86.242.95])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AHG83389;
	Tue, 25 Jan 2005 15:06:20 -0800 (PST)
Message-ID: <41F6D0EB.4010900@cisco.com>
Date: Tue, 25 Jan 2005 18:06:19 -0500
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 issue: RTP specificity of the candidate attribute
References: <41DEBAD1.2070900@cisco.com> <41E3A6E8.5060206@ericsson.com>
In-Reply-To: <41E3A6E8.5060206@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Hearing no further comments, I'll go with this approach.

-Jonathan R.

Magnus Westerlund wrote:

> Hi Jonathan,
> 
> I agree that the main problem with sending RTP and RTCP is the RTT 
> measurement. It really should go the same path, however I think it is 
> okay with the more simplistic grouping based on priorities. If it 
> actually shows that the grouping needs to be strict, an attribute using 
> the candidate IDs could be used to accomplish this. So we have a way 
> forward if it really would be required. However it doesn't seem that 
> likely that one candidate would work and not the other.
> 
> So the proposed resolution is to write a recommendation into the ICE 
> spec for RTP and RTCP to use the same priorities, so that it most likely 
> that the same candidate will be used for both. Including the motivation 
> that the RTT measurement would otherwise not be correct, if different 
> paths where selected.
> 
> Is there agreement on this?
> 
> Cheers
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> 

-- 
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 Jan 26 06:27: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 GAA13013
	for <mmusic-web-archive@ietf.org>; Wed, 26 Jan 2005 06:27:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtlbI-00028p-QT
	for mmusic-web-archive@ietf.org; Wed, 26 Jan 2005 06:44:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtlIk-00004r-P6; Wed, 26 Jan 2005 06:25:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtlGt-00081j-Ms
	for mmusic@megatron.ietf.org; Wed, 26 Jan 2005 06:23:39 -0500
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 GAA12800
	for <mmusic@ietf.org>; Wed, 26 Jan 2005 06:23:36 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtlXn-00023A-Oi
	for mmusic@ietf.org; Wed, 26 Jan 2005 06:41:08 -0500
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id j0QBPWJD008169
	for <mmusic@ietf.org>; Wed, 26 Jan 2005 04:25:32 -0700 (MST)
Received: from zin24exm01.ap.mot.com (zin24exm01.ap.mot.com [10.232.25.1])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j0QBNiYT029116
	for <mmusic@ietf.org>; Wed, 26 Jan 2005 05:23:45 -0600 (CST)
Received: by zin24exm01.ap.mot.com with Internet Mail Service (5.5.2657.72)
	id <WYWSNAF3>; Wed, 26 Jan 2005 16:53:26 +0530
Message-ID: <772BCEF88A1DD91191F80011856715F3245C23@zin24exm01.ap.mot.com>
From: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>
Date: Wed, 26 Jan 2005 16:53:25 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: quoted-printable
Cc: "'fandreas@cisco.com'" <fandreas@cisco.com>,
        "'David A. McGrew'" <mcgrew@cisco.com>,
        "'dwing@cisco.com'" <dwing@cisco.com>,
        "'Karl Norrman \(KI/EAB\)'" <karl.norrman@ericsson.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: [MMUSIC] RE: MKI length and MKI format
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: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable

Hi Mark

Thanks for your explanation. Few more queries related to the same:

1. If MKI value is a byte string of specified length, then in the below
example, MKI is of 4 byte length.=20

inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:4

But actual value has only one byte. Then should the master key be =
associated
with MKI of "0001" string or "1000" string?

Similarly in the following example also:
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:32


2. Grammatically are the below two crypto lines equivalent?

 .... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:4
(.... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|0001:4 or=20
 .... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1000:4)


Regards
Srikanth


-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com]=20
Sent: Wednesday, January 26, 2005 12:35 AM
To: Vavilapalli Srikanth-A19563
Cc: 'Karl Norrman (KI/EAB)'; 'dwing@cisco.com'; 'fandreas@cisco.com'; =
'Mats
N=E4slund'; 'David A. McGrew'; 'mmusic@ietf.org'
Subject: Re: MKI length and MKI format

hi Srikanth,

On Jan 25, 2005, at 10:42 AM, Vavilapalli Srikanth-A19563 wrote:

> Mark and MMUSIC community
>
> Ref: <draft-ietf-mmusic-sdescriptions-08.txt> Section:5.1 Page:14
>
> It was specified in the draft that the MKI length is the size of the=20
> MKI
> field in the SRTP packet, specified in Bytes. And the upper limit for =

> that
> value is 128 Bytes. Is it (128) Bytes or (128) bits?

It's in bytes, that's clear.
> What is the intention
> of keeping such a big value for the MKI length value?

It has a high upper bound in order to help with possible future=20
migration of digital TV services to IP networks.  I expect that two or=20
four bytes would be the typical value.  We made the upper bound=20
configurable in the SRTP specification owing to the practice found in=20
TV conditional access systems that use a key indicator to encode a=20
variety of information for a broadcast receiver.  I was told by people=20
from NDS and Nagra that they would prefer the size to be configurable.  =

We did not see any reason why it should not be, but we have not yet=20
seen any applications materialize for this particular feature.  I'd be=20
interested to know what the Motorola Digicipher folks think - when they =

think about video over IP.

I cannot imagine that the MKI will serve any telephony purpose=20
whatsoever.  The default size is zero and this is what is mandatory to=20
implement (and test).

>
> Also what is the data type of MKI? Is it an "integer" of length=20
> specified by
> MKI-Length or a "byte string" of length specified by MKI-Length?

It is a byte string.
>
> According to the example "1026:4" given in the draft, it was said =
that=20
> the
> example assigns to the key a master key identifier of 1026 that is 4=20
> bytes
> long. In this case what is the value of MKI filed in each SRTP =
packet?=20
> Is it
> "1026" or "0402" (where 1026 =3D 0x0402)?

Sorry, we're using decimal and not hexadecimal.  That should have been=20
pointed out in the document.

Mark
>
> Please clarify me in this regard.
>
> Regards
> Srikanth
>

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


From mmusic-bounces@ietf.org  Wed Jan 26 08:21:19 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 IAA22027
	for <mmusic-web-archive@ietf.org>; Wed, 26 Jan 2005 08:21:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtnNi-0005jz-A1
	for mmusic-web-archive@ietf.org; Wed, 26 Jan 2005 08:38:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ctmwg-0002ez-1M; Wed, 26 Jan 2005 08:10:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cslgt-0004Dp-MM; Sun, 23 Jan 2005 12:38:24 -0500
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 MAA27050;
	Sun, 23 Jan 2005 12:38:20 -0500 (EST)
Received: from orion.lrg.ufsc.br ([150.162.63.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CslxE-0006zf-Du; Sun, 23 Jan 2005 12:55:17 -0500
Received: by orion.lrg.ufsc.br (Postfix, from userid 3002)
	id ABC51A2C6; Sun, 23 Jan 2005 15:43:25 -0400 (WST)
Received: from localhost (localhost [127.0.0.1])
	by orion.lrg.ufsc.br (Postfix) with ESMTP
	id 7A864DD6D; Sun, 23 Jan 2005 15:43:25 -0400 (WST)
Date: Sun, 23 Jan 2005 15:43:25 -0400 (WST)
From: Carlos Becker Westphall <westphal@lrg.ufsc.br>
To: sip@ietf.org, mmusic@ietf.org, manet@ietf.org, cfp@mmlab.snu.ac.kr
Message-ID: <Pine.GSO.4.10.10501231543070.10287-100000@orion.lrg.ufsc.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Mailman-Approved-At: Wed, 26 Jan 2005 08:10:53 -0500
Subject: [MMUSIC] LANOMS 2005 - Call for Papers  (fwd)
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: 7268a2980febc47a9fa732aba2b737ba
Content-Transfer-Encoding: QUOTED-PRINTABLE



---------- Forwarded message ----------
Date: Sun, 23 Jan 2005 15:39:34 -0400 (WST)
From: Carlos Becker Westphall <westphal@lrg.ufsc.br>
To: mboned@network-services.uoregon.edu
Subject: LANOMS 2005 - Call for Papers=20

---------------------------------------------------------------------------=
-
LANOMS 2005 - 4th Latin American Network Operations and Management Symposiu=
m
Sheraton Hotel - Porto Alegre, Brazil -  August 29-31, 2005
http://www.lanoms.org/2005/

---------------------------------------------------------------------------=
-
The 4th Latin American Network Operations and Management Symposium - LANOMS=
=20
2005, to be held in Porto Alegre - Brazil, is the result of the great=20
success of the previous LANOMS 1999 (held in Rio de Janeiro), LANOMS
2001 (held in Belo Horizonte), and LANOMS 2003 (held in Iguassu Falls), as=
=20
well as the other successful events in the area of network management:=20
NOMS and APNOMS.=20

The LANOMS 2005 is promoted by the Federal University of Rio Grande do Sul
(UFRGS) and by the University of Vale do Rio dos Sinos (UNISINOS). The main=
=20
goal of LANOMS 2005 is to create a forum more specific to the necessities o=
f

Latin American in the area of network management involving networking and=
=20
telecommunications companies, academic institutions and equipment vendors.
LANOMS is an event open to participants from all over the world who are=20
interested in having, or already have, research or commercial liaisons in=
=20
Latin America - one of the fastest growing regions in the world in=20
networking.

Topics
---------------------------------------------------------------------------=
-
The LANOMS 2005 invites authors to submit original and unpublished work to=
=20
both technical and application tracks. Topics of interest include but are=
=20
not limited to:

- Management architectures and platforms
- Distributed and cooperative management
- Self management
- Policy and role-based management
- Security management
- Configuration management
- Adaptive and programmable management
- Context and subscriber-aware networks, mobile computing
- Management information models, ontologies
- Web Services
- Smart homes, Personal Area Networks
- Multisensor and RFID-enabled networks
- Ad hoc and self organizing networks
- WLANs, metro Ethernet, optical networks
- Overlay networks, virtual topologies
- QoS management
- IPv4/v6 networks and services
- VoIP and video distribution management
- Storage Area Networks, content hosting
- Utility computing, virtualized resources
- Grid, cluster, and peer-to-peer management
- Converged networks and services =20

Important dates:
---------------------------------------------------------------------------=
-
- Deadline for receipt of papers: April 18, 2005
- Notification of acceptance: May 30, 2005
- Final camera ready paper due: June 06, 2005

Paper format and submission instructions
---------------------------------------------------------------------------=
-
Scientific papers should not exceed the limit of 12 pages. Sample files and
templates can be downloaded from the LANOMS 2005 Web site. Application=20
papers should have a visual in the upper half of a page and the explanatory=
=20
text in the lower half, following the current IM/NOMS format, and should=20
not exceed 12 visuals. A PowerPoint template and a sample PDF file can be=
=20
downloaded from the LANOMS Web site as well. All selected papers will be=20
published in the LANOMS proceedings. Authors of scientific papers should=20
submit a PDF file at https://submissoes.sbc.org.br/lanoms2005. Authors of=
=20
application papers should submit at=20
https://submissoes.sbc.org.br/lanoms2005_app. Submission implies the=20
willingness of at least one of the authors to register and present the=20
paper, if accepted.

Organizing Committee
---------------------------------------------------------------------------=
-
GENERAL CO-CHAIRS:
- Lisandro Zambenedetti Granville
  Federal University of Rio Grande do Sul, Brazil
- Luciano Paschoal Gaspary
  University of Vale do Rio dos Sinos, Brazil=20

TECHNICAL PROGRAM CO-CHAIRS:
- Bruno Schulze
  National Laboratory on Scientific Computing, Brazil
- Jos=E9 Neuman de Souza
  Federal University of Cear=E1, Brazil=20
=20
APPLICATION PROGRAM CO-CHAIRS:
- Iara Machado
  National Research Network, Brazil
- Michael Stanton
  Fluminense Federal University, Brazil

PUBLICITY CHAIR:
- Carlos Becker Westphall
  Federal University of Santa Catarina, Brazil=20
=20
Steering Committee
---------------------------------------------------------------------------=
-
- Elias Proc=F3pio Duarte Jr.
  Federal University of Paran=E1, Brazil
- Edmundo Roberto Mauro Madeira
  State University of Caminas, Brazil
- Jos=E9 Marcos Silva Nogueira
  Federal University of Minas Gerais, Brazil
- Ant=F4nio Alfredo Ferreira Loureiro
  Federal University of Minas Gerais, Brazil
=20
Technical Program Committee
---------------------------------------------------------------------------=
-
- Abdelmalek Benzekri
  Universit=E9 Paul Sabatier, France
- Ahmed Karmouch
  University of Ottawa, Canada
- Antonio Alfredo Ferreira Loureiro
  Federal University of Minas Gerais, Brazil
- Benjam=EDn Bar=E1n
  Universidad Nacional de Asunci=F3n, Paraguay
- Bruno R. Schulze
  LNCC, Brazil
- Carlos Becker Westphall
  Federal University of Santa Catarina, Brazil
- Carlos de Castro Goulart
  Federal University of Vi=E7osa, Brazil
- Elias Proc=F3pio Duarte Jr.=20
  Federal University of Paran=E1, Brazil
- Edmundo Monteiro
  University of Coimbra, Portugal
- Edmundo Roberto Mauro Madeira
  State University of Campinas, Brazil
- Edward L. Pinnes
  Telcordia, USA
- Florencio Utreras
  Cooperacion Latinoamericana de Redes Avanzadas, Chile
- Germ=E1n Goldszmidt
  IBM, USA
- Hanan Lutfiyya
  University of Western Ontario, Canada
- Iara Machado
  RNP, Brazil
- James Won-Ki Hong
  POSTECH, Korea
- Javier Diaz
  University La Plata, Argentina
- Jauvane de Oliveira
  LNCC, Brazil
- Jos=E9 Marcos Silva Nogueira
  Federal University of Minas Gerais, Brazil
- Jos=E9 Neuman de Souza
  Federal University of Cear=E1, Brazil
- Liane Margarida Rockenbach Tarouco
  Federal University of Rio Grande do Sul, Brazil
- Lisandro Zambenedetti Granville
  Federal University of Rio Grande do Sul, Brazil
- Luciano Paschoal Gaspary
  University of Vale do Rio dos Sinos, Brazil
- Lundy Lewis
  Verizon, USA
- Manu Malek
  Stevens Institute of Technology, USA
- Masayoshi Ejiri
  Fujitsu, Japan
- Mehmet Ulema
  Manhattan College, USA
- Nazim Agoulmine
  Univ. of Evry, France
- Thomas Magedanz
  IKV++ Technologies AG, TU Berlin, Germany
- Linnyer Beatrys Ruiz
  Federal University of Minas Gerais, Brazil
- Paulo Sim=F5es
  University Coimbra, Portugal
- Raouf Boutaba
  University of Waterloo, Canada
- Rossana Andrade
  Federal University of Cear=E1, Brazil
- Tereza Carvalho
  University of S=E3o Paulo, Brazil
- Yezid Donoso
  Universidad del Norte Barranquilla, Col=F4mbia



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


From mmusic-bounces@ietf.org  Wed Jan 26 08:22:45 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 IAA22243
	for <mmusic-web-archive@ietf.org>; Wed, 26 Jan 2005 08:22:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtnP3-0005pL-55
	for mmusic-web-archive@ietf.org; Wed, 26 Jan 2005 08:40:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ctmwg-0002f4-DT; Wed, 26 Jan 2005 08:10:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Csqzz-00056f-HV; Sun, 23 Jan 2005 18:18:28 -0500
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 SAA19118;
	Sun, 23 Jan 2005 18:18:24 -0500 (EST)
Received: from orion.lrg.ufsc.br ([150.162.63.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CsrGN-0005in-Bf; Sun, 23 Jan 2005 18:35:23 -0500
Received: by orion.lrg.ufsc.br (Postfix, from userid 3002)
	id D1D5DA2AC; Sun, 23 Jan 2005 21:23:30 -0400 (WST)
Received: from localhost (localhost [127.0.0.1])
	by orion.lrg.ufsc.br (Postfix) with ESMTP
	id A0D44DD6D; Sun, 23 Jan 2005 21:23:30 -0400 (WST)
Date: Sun, 23 Jan 2005 21:23:30 -0400 (WST)
From: Carlos Becker Westphall <westphal@lrg.ufsc.br>
To: sip@ietf.org, mmusic@ietf.org, manet@ietf.org, cfp@mmlab.snu.ac.kr
In-Reply-To: <Pine.GSO.4.10.10501231543070.10287-100000@orion.lrg.ufsc.br>
Message-ID: <Pine.GSO.4.10.10501232122500.14534-100000@orion.lrg.ufsc.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Mailman-Approved-At: Wed, 26 Jan 2005 08:10:53 -0500
Subject: [MMUSIC] WP2P
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.6 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Content-Transfer-Encoding: QUOTED-PRINTABLE




       *****************************************************
       *                                                   *
       *   I PEER-TO-PEER NETWORKS WORKSHOP - WP2P 2005    *
       *                                                   *
       *****************************************************

                    http://www.sbrc2005.ufc.br

         * 23th BRAZILIAN SYMPOSIUM ON COMPUTER NETWORKS *
                   Fortaleza, CE - May 09, 2005

                           Promotion of:=20
                 Brazilian Computing Society (SBC)
=09     Computer Networks National Laboratory (LARC)

                      - FIRST CALL FOR PAPERS -


INTRODUCTION
------------

In the last recent years, Peer-to-peer (P2P) networks have been promoting
a revolutionary change in computer communication models. A concept born
from the extensive use of innovative applications such as Napster,
Gnutella, and Kazaa, P2P networks are not just used as a file sharing tool
anymore; P2P networks have grown and became an intensive research topic in
several computer science fields.=20

Besides allowing the sharing of diverse resources such as network
bandwidth, volatile and non-volatile storage, processing power, among
others, P2P can enable the use of technologies already previously
investigated (e.g. mobile agents, active networks, cooperative
environments) but whose applicability did not reach industry as originally
expected.

The main goal of the I Peer-to-Peer Networks Workshop (WP2P) is to provide
a forum for the presentation and discussion of P2P researches and
developments. Thus, WP2P is an opportunity for professors, researchers,
and students to present the investigations that have been carried out by
universities and research centers.

The Workshop will take place at May 9, 2005 as part of the 23th Brazilian
Symposium on Computer Networks (SBRC 2005).


TOPICS
------

Authors are invited to submit papers that present finished or under
development investigations related to relevant aspects of P2P networks,
which include (but is not limited) to:

- P2P architectures
- Techniques, development environment and toolkits for P2P programming
- P2P and Web Services
- P2P and grids
- Performance and scalability of P2P networks
- Algorithms for P2P networks
- P2P and security
- Indexing and resource discovery
- P2P protocols
- Routing and multicast
- Fault tolerance in P2P networks
- Mobility management and P2P mobile networks
- Accounting and resource management
- Active and programmable P2P networks
- P2P networks management
- Visualization techniques
- Reputation
- P2P and quality of service
- Self-adaptable P2P networks
- Applications and study case of P2P networks

Submitted papers will be reviewed by the workshop technical program
committee, and selected papers will be organized in order to be presented
and published in the WP2P proceedings. At least one paper author, per
selected paper, must register in SBRC and WP2P in order to have the
selected paper published.

PAPER SUBMISSION
----------------

Papers must be written in English or Portuguese and are limited to 12
pages including abstract, figures, diagrams, tables, and references. Paper
formatting must follow the Brazilian Computing Society (SBC) template,
available at http://www.sbrc2005.ufc.br/templates. Authors should avoid
bitmap-based or too small figures. Paper submission is exclusively
electronic through the EDAS system at
https://submissoes.sbc.org.br/sbrc2005_wp2p. Paper must be submitted only
via PDF files readable by the Adobe Acrobat Reader.


IMPORTANT DATES
---------------
- Paper submission deadline:  March 25, 2005
- Author notification:        April 14, 2005
- Camera-ready copy deadline: April 20, 2005


TECHNICAL PROGRAM COMMITTEE
---------------------------

- Antonio Alfredo Loureiro (UFMG)
- Alfredo Goldman (USP)
- Ant=F4nio Jorge G. Abel=E9m (UFPA)
- Bruno Schulze (LNCC)
- Carla Merkle Westphall (UFSC)=20
- Carlos Alberto Kamienski (CEFET-PA)
- Cl=E1udio Geyer (UFRGS)
- Djamel Sadok (UFPE)
- Edmundo Madeira (UNICAMP)
- Elias Proc=F3pio Duarte Jr. (UFPR)
- Fl=E1vio Morais de Assis Silva (UFBA)
- Francisco Villar Brasileiro (UFCG)
- Geraldo Robson Mateus (UFMG)
- Joni da Silva Fraga (UFSC)
- Jos=E9 Neuman de Souza (UFCE)
- Lisandro Zambenedetti Granville (UFRGS) - chair
- Luci Pirmez (UFRJ)
- Luciano Paschoal Gaspary (UNISINOS)
- Luis Carlos Trevelin (UFSCar)
- Marcelo Pias (Cambridge)
- Markus Endler (PUC-RIO)
- Maur=EDcio Ferreira Magalh=E3es (UNICAMP)
- Paulo Henrique Aguiar Rodrigues (UFRJ)
- Rossana Andrade (UFCE)
- Tereza Cristina Carvalho (USP)
- Thais Vasconcelos Baptista (UFRN)

CONTACT
-------
Lisandro Zambenedetti Granville (WP2P chair)
granville@inf.ufrgs.br







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


From mmusic-bounces@ietf.org  Wed Jan 26 12:18: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 MAA17632
	for <mmusic-web-archive@ietf.org>; Wed, 26 Jan 2005 12:18:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ctr5D-0004e3-9h
	for mmusic-web-archive@ietf.org; Wed, 26 Jan 2005 12:35:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ctqb6-0003Cv-MM; Wed, 26 Jan 2005 12:04:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtqOi-0000OI-NS
	for mmusic@megatron.ietf.org; Wed, 26 Jan 2005 11:52:04 -0500
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 LAA15391
	for <mmusic@ietf.org>; Wed, 26 Jan 2005 11:52:02 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ctqfd-0003uS-A1
	for mmusic@ietf.org; Wed, 26 Jan 2005 12:09:36 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-5.cisco.com with ESMTP; 26 Jan 2005 08:52:42 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0QGpRNt021195;
	Wed, 26 Jan 2005 08:51:27 -0800 (PST)
Received: from [192.168.0.10] (sjc-vpn7-108.cisco.com [10.21.144.108])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0QGlY81022135;
	Wed, 26 Jan 2005 08:47:34 -0800
In-Reply-To: <772BCEF88A1DD91191F80011856715F3245C23@zin24exm01.ap.mot.com>
References: <772BCEF88A1DD91191F80011856715F3245C23@zin24exm01.ap.mot.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <82C2421B-6FBA-11D9-9811-000A95DC10F2@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] RE: MKI length and MKI format
Date: Wed, 26 Jan 2005 08:51:23 -0800
To: Vavilapalli Srikanth-A19563 <srikanthv@motorola.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106758054.782365"; x:"432200"; a:"rsa-sha1"; b:"nofws:3736";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"TRphtR9M8pEwnK64zsz4yG4pIQ+2p8g08oH8BrAYzRqgPcXuucnVzzGV6GZUmiA+QrfWIxTp"
	"rPnN1bOP1LfqSGRsObwR80sdOAE7gPJ6ueDkI37uhgbGrVLjJRWyc4IIXAt1vMtQzoSYemPSNEt"
	"VGkjrFu52Khu+o1VjYF+lRto=";
	c:"From: Mark Baugher <mbaugher@cisco.com>";
	c:"Subject: Re: [MMUSIC] RE: MKI length and MKI format";
	c:"Date: Wed, 26 Jan 2005 08:51:23 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: quoted-printable
Cc: "'fandreas@cisco.com'" <fandreas@cisco.com>,
        "'Karl Norrman \(KI/EAB\)'" <karl.norrman@ericsson.com>,
        "'David A. McGrew'" <mcgrew@cisco.com>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>,
        "'dwing@cisco.com'" <dwing@cisco.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: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable

hi Srikanth,
    You're right.  I now see that the MKI is not well-specified.  It's =20=

clear that =20
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions=20
-08.txt uses as the notation is a big-endian, integer with unused, =20
high-order bytes set to zero.  This is illustrated in the examples (see =20=

the p. 14 inline example where the MKI has an initial value of 1066) =20
provided that you assume that a number in an I-D has the usual, decimal =20=

notation by default.  This is not a good way to specify something.  I'd =20=

like to add some clarifying text and will check with the chairs and the =20=

ADs to see if I can do that while it's awaiting a second AD review.

   I think we should say that the MKI is expressed as a big-endian, =20
positive integer with unused high-order bytes set to zero.  My original =20=

intention for the MKI was to allow it to be whatever the key =20
establishment system wants it to be, but our syntax does not support =20
that.  It's a bit late to change this, however, and no one has asked =20
for us to support, say, hexadecimal notation.

thanks, Mark

On Jan 26, 2005, at 3:23 AM, Vavilapalli Srikanth-A19563 wrote:

> Hi Mark
>
> Thanks for your explanation. Few more queries related to the same:
>
> 1. If MKI value is a byte string of specified length, then in the =
below
> example, MKI is of 4 byte length.
>
> inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:4
>
> But actual value has only one byte. Then should the master key be =20
> associated
> with MKI of "0001" string or "1000" string?
>
> Similarly in the following example also:
> inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:32
>
>
> 2. Grammatically are the below two crypto lines equivalent?
>
>  .... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1:4
> (.... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|0001:4 or
>  .... inline:d0RmdmcmVCspeEc3QGZiNWpVLFJhQX1cfHAwJSoj|2^20|1000:4)
>
>
> Regards
> Srikanth
>
>
> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> Sent: Wednesday, January 26, 2005 12:35 AM
> To: Vavilapalli Srikanth-A19563
> Cc: 'Karl Norrman (KI/EAB)'; 'dwing@cisco.com'; 'fandreas@cisco.com'; =20=

> 'Mats
> N=E4slund'; 'David A. McGrew'; 'mmusic@ietf.org'
> Subject: Re: MKI length and MKI format
>
> hi Srikanth,
>
> On Jan 25, 2005, at 10:42 AM, Vavilapalli Srikanth-A19563 wrote:
>
>> Mark and MMUSIC community
>>
>> Ref: <draft-ietf-mmusic-sdescriptions-08.txt> Section:5.1 Page:14
>>
>> It was specified in the draft that the MKI length is the size of the
>> MKI
>> field in the SRTP packet, specified in Bytes. And the upper limit for
>> that
>> value is 128 Bytes. Is it (128) Bytes or (128) bits?
>
> It's in bytes, that's clear.
>> What is the intention
>> of keeping such a big value for the MKI length value?
>
> It has a high upper bound in order to help with possible future
> migration of digital TV services to IP networks.  I expect that two or
> four bytes would be the typical value.  We made the upper bound
> configurable in the SRTP specification owing to the practice found in
> TV conditional access systems that use a key indicator to encode a
> variety of information for a broadcast receiver.  I was told by people
> from NDS and Nagra that they would prefer the size to be configurable.
> We did not see any reason why it should not be, but we have not yet
> seen any applications materialize for this particular feature.  I'd be
> interested to know what the Motorola Digicipher folks think - when =
they
> think about video over IP.
>
> I cannot imagine that the MKI will serve any telephony purpose
> whatsoever.  The default size is zero and this is what is mandatory to
> implement (and test).
>
>>
>> Also what is the data type of MKI? Is it an "integer" of length
>> specified by
>> MKI-Length or a "byte string" of length specified by MKI-Length?
>
> It is a byte string.
>>
>> According to the example "1026:4" given in the draft, it was said =
that
>> the
>> example assigns to the key a master key identifier of 1026 that is 4
>> bytes
>> long. In this case what is the value of MKI filed in each SRTP =
packet?
>> Is it
>> "1026" or "0402" (where 1026 =3D 0x0402)?
>
> Sorry, we're using decimal and not hexadecimal.  That should have been
> pointed out in the document.
>
> Mark
>>
>> Please clarify me in this regard.
>>
>> Regards
>> Srikanth
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>

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


From mmusic-bounces@ietf.org  Thu Jan 27 13:53:38 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 NAA12319
	for <mmusic-web-archive@ietf.org>; Thu, 27 Jan 2005 13:53:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuF37-0003Vm-E2
	for mmusic-web-archive@ietf.org; Thu, 27 Jan 2005 14:11:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuEfc-0002Hu-3R; Thu, 27 Jan 2005 13:47:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CuEbn-0000hO-Ck
	for mmusic@megatron.ietf.org; Thu, 27 Jan 2005 13:43:11 -0500
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 NAA10743
	for <mmusic@ietf.org>; Thu, 27 Jan 2005 13:43:07 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuEsy-0003AA-40
	for mmusic@ietf.org; Thu, 27 Jan 2005 14:00:56 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 27 Jan 2005 11:51:50 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0RIgYl2000217
	for <mmusic@ietf.org>; Thu, 27 Jan 2005 10:42:35 -0800 (PST)
Received: from [192.168.6.88] (che-vpn-cluster-2-60.cisco.com [10.86.242.60])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AHI11230;
	Thu, 27 Jan 2005 10:42:36 -0800 (PST)
Message-ID: <41F9361B.1030206@cisco.com>
Date: Thu, 27 Jan 2005 13:42:35 -0500
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] ICE feature - TCP alternates for a UDP stream
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: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit

Folks,

In the past, we had considered whether or not to also apply ICE to allow 
a TCP session to be an alternate for a UDP one. We decided to keep the 
scope narrow, and not consider this.

However, in reality, I think there is an extremely pressing need for 
this. In particular, there are many deployments where we would like to 
support SIP, but (for better or for worse), networks are only allowing 
outbound TCP connections. This is not a NAT issue so much as a firewall 
issue, but in this case the firewall is introducing a connectivity 
problem of the sort that ICE was designed to address. As such, I think 
its in scope. If we defer this to a future document, I fear we will get 
implementations missing this feature and thus SIP/ICE clients will find 
themselves in situations where it STILL doesnt "just work", despite the 
fact that ICE is supposed to make it "just work".

Now, all of us agree, no doubt, that RTP over UDP is far preferable to 
RTP over TCP, but if TCP is all you can get working, TCP is better than 
nothing. ICE can serve a crucial role of figuring out, dynamically, 
whether or not UDP can be made to work, and thus whether the lower 
priority alternative of TCP, should be used.

So, here's how it would work. A client would include UDP local 
addresses, STUn derived addresses, TURN derived (using UDP), and ALSO 
TURN derived using TCP (recall that TURN supports TCP connections). We 
have a spec for RTP over TCP (draft-ietf-avt-rtp-framing-contrans), 
which makes use of the comedia spec. The client would specify that it is 
passive. The INVITE is sent. The peer connects to this (indicating that 
it is active in its answer); that connection terminates on the TURN 
relay used by the caller. The peer, as with any other session, uses STUN 
to check connectivity. The caller can then use STUN itself to verify 
connectivity in its direction (presumably it would always work in both 
directions).

The nice thing is, by setting the priorities appropriately, this 
connection would only get used if the other UDP choices fail. That gives 
us even further robustness.

Presumably this could also work for TLS, in which case the TURN server 
would terminate the TLS connection from the caller and from the callee.

Specifying this isn't really hard. The main issue is just a grouping 
one. We need to be able to apply the comedia parameters to candidates. 
You can't just include them under the m-line, since then you don't know 
to what they apply. In any case, we don't really need or even want a 
generic grouping framework here; I would HATE for this to be used as an 
alternative for negotiating codec parameters in yet another way. As 
such, I would suggest merely extending the candidate line to include the 
transports and comedia information when needed.

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  Fri Jan 28 10:55:49 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 KAA11730
	for <mmusic-web-archive@ietf.org>; Fri, 28 Jan 2005 10:55:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuYkk-0008FQ-Mi
	for mmusic-web-archive@ietf.org; Fri, 28 Jan 2005 11:13:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuYI0-0000Jl-Mw; Fri, 28 Jan 2005 10:44:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CuGt3-0002rk-MH; Thu, 27 Jan 2005 16:09:09 -0500
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 QAA25577;
	Thu, 27 Jan 2005 16:09:07 -0500 (EST)
Received: from mail.lumenvox.com ([206.169.193.45] helo=lv-svr.lumenvox.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CuHAF-00076L-Mx; Thu, 27 Jan 2005 16:26:56 -0500
Received: from PROGTHOMAS ([10.0.0.141]) by lv-svr.lumenvox.com with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 27 Jan 2005 13:04:17 -0800
From: "Thomas Gal" <ThomasGal@LumenVox.com>
To: "'Sarvi Shanmugham'" <sarvi@cisco.com>,
        "'Reifenrath, Klaus'" <Klaus.Reifenrath@Scansoft.com>
Date: Thu, 27 Jan 2005 13:08:30 -0800
Organization: LumenVox LLC
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcUEmQ1T8171hj7nSxqgDz7VFnK1NwAGqlWg
In-Reply-To: <41F92B76.7080601@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <LV-SVRzAJ95sZKxt8zP00000a0c@lv-svr.lumenvox.com>
X-OriginalArrivalTime: 27 Jan 2005 21:04:17.0390 (UTC)
	FILETIME=[C36720E0:01C504B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
X-Mailman-Approved-At: Fri, 28 Jan 2005 10:43:59 -0500
Cc: Thomas Gal <ThomasGal@LumenVox.com>, mmusic@ietf.org,
        "'Dan Burnett'" <dan_burnett2000@yahoo.com>, speechsc@ietf.org
Subject: [MMUSIC] RE: [Speechsc] IANA considerations for group feedback
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ThomasGal@LumenVox.com
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1461258034=="
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af

This is a multi-part message in MIME format.

--===============1461258034==
Content-Type: multipart/signed;
	boundary="----=_NextPart_000_0017_01C50471.4B26D9A0";
	micalg=SHA1; protocol="application/x-pkcs7-signature"

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C50471.4B26D9A0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Klaus,

	MRCPv2 is the "control" for a media server. It can be
application/mrcpv2 or control/mrcpv2 but not both correct? Currently we are
specifying it in the draft as application/mrcpv2, which would obviate the
need for control no? Or are you proposing something different? I certainly
think control/mrcpv2 makes more sense despite the seeming tradition toward
using application/xxxx for everything.

-Tom

thomasgal@lumenvox.com  

> -----Original Message-----
> From: Sarvi Shanmugham [mailto:sarvi@cisco.com] 
> Sent: Thursday, January 27, 2005 9:57 AM
> To: Reifenrath, Klaus
> Cc: Thomas Gal; 'Dan Burnett'; speechsc@ietf.org
> Subject: Re: [Speechsc] IANA considerations for group feedback
> 
> Which is exactly what is being done here. 
> 
> So we are fine.
> 
> Sarvi
> Reifenrath, Klaus wrote: 
> 
> 	Quoting from
> 	
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-23.txt:
> 	   Note: The media types "control" and "data" were 
> listed as valid in
> 	   the previous version of this specification [6], however their
> 	   semantics were never fully specified and they are 
> not widely used.
> 	   These media types have been removed in this 
> specification, although
> 	   they still remain valid media type capabilities for 
> a SIP user agent
> 	   as defined in RFC 3840 [23].  If these media types 
> are considered
> 	   useful in future, a Standards Track RFC MUST be 
> produced to document
> 	   their use.  Until that is done, applications SHOULD 
> NOT use these
> 	   types and SHOULD NOT declare support for them in SIP 
> capabilities
> 	   declarations (even though they exist in the registry 
> created by RFC
> 	   3840).
> 	
> 	-----Original Message-----
> 	From: Thomas Gal [mailto:ThomasGal@LumenVox.com]
> 	Sent: Mittwoch, 26. Januar 2005 20:48
> 	To: 'Dan Burnett'; 'Reifenrath, Klaus'
> 	Cc: speechsc@ietf.org
> 	Subject: RE: [Speechsc] IANA considerations for group feedback
> 	
> 	
> 	inlinemmusic@ietf.org
> 	
> 	-Tom
> 	
> 	thomasgal@lumenvox.com  
> 	
> 	  
> 
> 		-----Original Message-----
> 		From: speechsc-bounces@ietf.org 
> 		[mailto:speechsc-bounces@ietf.org] On Behalf Of 
> Dan Burnett
> 		Sent: Wednesday, January 26, 2005 10:15 AM
> 		To: Reifenrath, Klaus
> 		Cc: speechsc@ietf.org
> 		Subject: RE: [Speechsc] IANA considerations for 
> group feedback
> 		
> 		I agree that there needs to be an registration of 
> 		application/x-nlsml (or, as an email from Tom 
> pointed out, 
> 		application/nlsml).  Technically it should be 
> in a separate 
> 		RFC from MRCP, but I can include it in the 
> draft if there are 
> 		no objections.
> 		
> 		    
> 
> 	
> 	I would certainly agree with not using 
> "application/nlsml" but something
> 	similar to obviate confusion, even mrcp-nlsml or something.
> 	
> 	  
> 
> 		If "control" is already registered, do we need 
> to do it?  In 
> 		short, it's not clear to me in which
> 		namespace(s) the SDP items you mention should 
> be registered.  
> 		Are they new namespaces for MRCP or are there existing 
> 		namespaces to which the items should be added?
> 		
> 		    
> 
> 	
> 	Isn't MRCPv2 "control"? I would guess control is too 
> ambiguous and probably
> 	why it's being deprecated.
> 	
> 	-Tom
> 	
> 	_______________________________________________
> 	Speechsc mailing list
> 	Speechsc@ietf.org
> 	https://www1.ietf.org/mailman/listinfo/speechsc
> 	
> 	  
> 
> 
> 

------=_NextPart_000_0017_01C50471.4B26D9A0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMBDCCBL8w
ggKnoAMCAQICAwDQ9DANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wNDEyMDEyMTI1MzBaFw0w
NTEyMDEyMTI1MzBaMDwxEzARBgNVBAMTClRob21hcyBHYWwxJTAjBgkqhkiG9w0BCQEWFnRob21h
c2dhbEBsdW1lbnZveC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDR7eXh1399
BXAlOs1kGnSeVSRasyxQd1eRcRle/mNHGMJ3COpMB3bkd8vRIqW9CuPTzjnHrCbLSbduJRoQNNjc
p6Df0TkAvMDNxk6tGtEfrKk71WJ0btokYb1cxAXb7A2GHEWXVnSu+nvQ68n+/T6pJzOeesqS2cDI
n79lw8owwxQixgYDKUz+nC2a+A0a2wktL+E9lXFJgCSE2CL9w9dCO5w2NeqqiPBLTxe3aiDkoRSk
yvBX1tCT5s486pkko/sAko8eY/ZXE1IrAKn6U8Wr2mHUmDhcVNaRGe0w12yS/WRC+YW3/S3a1T4b
Tpgb5hRiK/IbV8f/0aSDLn4GaFnLAgMBAAGjgYwwgYkwDAYDVR0TAQH/BAIwADBWBglghkgBhvhC
AQ0ESRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBo
dHRwOi8vd3d3LkNBY2VydC5vcmcwIQYDVR0RBBowGIEWdGhvbWFzZ2FsQGx1bWVudm94LmNvbTAN
BgkqhkiG9w0BAQQFAAOCAgEAdI6mD6HejUJaFjEPtruQpOOUat6eLetY94CoPmYiIqSoYSwBt6+m
7nJl5fGJcfUaugez/AJzMBC8Nfphtr0yw5O8EYUtvfWxtpY272eR9evAzFk2l8ZzvzGLphXuSlfK
RCMLQcPN+fEnX66yu6wseF5/Z1nZnjn9TtQQ2xlZjFAKkU4L2oczvfaadOVuB1iUMx4Sbr49ukhc
sRjQ4F1VS0lf/INqhL3SHGOaLDD7nWoaZM35jP/8zNHrWGr4Jait0epazMLFen4LSEJH6hsbKxVv
VGVef8KczVK4f5qVX8BlediiLCH7DZkT/uY4YB/2NPr3bHZnZmmff7vYp7cIsLiUYaD565f9Isbc
eHjihQarb+bDMcm8qlkaYPc6pt1t9cUgLMi0YbyjCzi5PQFX8BIjPvRYAM9iOJdjO9lIyEZnpb2S
fclvuhRupYIOJC6bTIVa2qXuzNfkCRtWG7RwIu+bfLuHiIfyh/c2P66140q278zz/euPHTQSr6A7
uGhpwYTfkzO4btn7FPA8bE9hnz82Wd9dGBcQc7yTEmN11+hEGS3Ie+q2jCuOP4jONgGTKAPRFsXG
86aZr12DVZHcDrh7zt71sBwD2AMCaMuLZpClWlIFwCX0wryt2Qr9/IjvcM2hn2kHu3kIusy/UOU5
FU3SYYCpevzG7qhvoAbrIkowggc9MIIFJaADAgECAgEAMA0GCSqGSIb3DQEBBAUAMHkxEDAOBgNV
BAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0Eg
Q2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn
MB4XDTAzMDMzMDEyMjk0OVoXDTMzMDMyOTEyMjk0OVoweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwG
A1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0
aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwggIiMA0GCSqGSIb3DQEB
AQUAA4ICDwAwggIKAoICAQDOIsDiRn3sNigHUJbyoDNAjEvxO2Y/MeVrAjbb1nz28YiPTnc2BUGV
+QnwEs9GhnNgt25+6MBYZK7NsK1FFwxj+mcK6NbSvz7nmMTwTPrgA7s1XWwh3p4g2brNZjI3cvr3
CPXHzVjJjucOXuo+/hyhFAoVbIaEW2RmKnqpS1N59Yiie+4vCmErjbJ+TValE+zq2pKerERBHlhg
ZQVm+MBEvcuU90J+C/dlaJhRBfDzBZEEHRsXguzIV7vDa3qI8bByzCVbIJHsFgISjzLpFxhI0McF
LgIwQrglnAVrP6o6p+tTSPfo0rYHmNwbxjR/f8kcgnoFWCsIW/M4oqsXXWbJmNeeEIui0t10mvdx
DHJg381vmDOdljR2PiR6krAOlR5v5qBFOEeq10HtSrcS9tcbg4oPLtgJtlnXqgT/0pN9aC7di0ur
WLovjeqVp6DDVIml+9uLUSKdssO+Eb4skYaLlnitINOKLxo/xtBRZYchsRkBZX9FHIf1fNBBTE8p
mCH9Mx91DARR+hl329QUHO6Bwx31mLdpBpEi3QBQzIExrBIHezjaaFvmK9R+yV+t6OtyTPMB5Usg
v5qmV8qRAAGLoXUhN7VjDWc+Rk9wIGfOxdZZ2wLg8NLLzbpit5BB6N0g5Cm8ZClCyCLceJr/Q+yY
GwlRS1pawnHxxMtzqeWhCwIDAQABo4IBzjCCAcowHQYDVR0OBBYEFBa1MhvUx/Pg5o7zvdKwOu6y
ORjRMIGjBgNVHSMEgZswgZiAFBa1MhvUx/Pg5o7zvdKwOu6yORjRoX2kezB5MRAwDgYDVQQKEwdS
b290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQg
U2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZ4IBADAP
BgNVHRMBAf8EBTADAQH/MDIGA1UdHwQrMCkwJ6AloCOGIWh0dHBzOi8vd3d3LmNhY2VydC5vcmcv
cmV2b2tlLmNybDAwBglghkgBhvhCAQQEIxYhaHR0cHM6Ly93d3cuY2FjZXJ0Lm9yZy9yZXZva2Uu
Y3JsMDQGCWCGSAGG+EIBCAQnFiVodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lkPTEw
MFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZSRUUgaGVh
ZCBvdmVyIHRvIGh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzANBgkqhkiG9w0BAQQFAAOCAgEAKMfunIIC
ulyAEso1Ch2Bb4lqmczyaA9/p+GNWJU+vfIGw5BarLVg9plDAaOIcJydYp2kh69nWA0wNjvmrUjT
y3QChnE+4isDaPE0YkBGO1PqKPSs+2aVU4pNXf072WDXynlpO7FlkqbGgYJcnM3rTQGKpd8RVaoV
yh83wIKYcGHbanyWo44uVD5PIamQ79yCv9zoRa1NkHMIPJRlsASZdn/ivMJqFaqXBDck2B6UTm0O
Ub7WxI/Klm33Q9/oMGUnO3u7Q0NjxEP3suxozOEZjiL7mOF7Wj4BNzuLCLCi85VOGsubzZqx27Jw
8C1K29iw429FSDMS//48MipU98T3ivCII8JH/mR6ccDRHqZjsAd+pC/TAY/cnyu2xgipD5NIJfwS
/Z9C3PPEPvZXsNfdadEGdzQKS9LKoP8cxozJFr7EzDI3aHNfCPtR90lTNgUKlQJM8nkaEPbYOnWc
8x3xog1wZ4Ybsxb1L+Wk63mG+T0LwnMLpZmsb/xnuOUvC6YYJI170Ug1KRhArJNg4ZaGULR6WdiP
IQufz4KRxju/a9wHkbmXViOqtmyUxkgGPOTOTqrk9i8J3FNvLvx06zpjmcKmrIm8p7JEoA2KEONs
8iTL+pufcEcu3hSL1LIgCZaiZPEkHNyhNZwVstS8VS59BvWcDlX0WtaT2natJXNMxUMxggOcMIID
mAIBATCBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5v
cmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1
cHBvcnRAY2FjZXJ0Lm9yZwIDAND0MAkGBSsOAwIaBQCgggHwMBgGCSqGSIb3DQEJAzELBgkqhkiG
9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA1MDEyNzIxMDgyOFowIwYJKoZIhvcNAQkEMRYEFEJ8D8tZ
zJOEMfavnCo7ma+TRyGCMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC
AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqG
SIb3DQIFMIGRBgkrBgEEAYI3EAQxgYMwgYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMV
aHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5
MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAwDQ9DCBkwYLKoZIhvcNAQkQAgsx
gYOggYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3Jn
MSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBw
b3J0QGNhY2VydC5vcmcCAwDQ9DANBgkqhkiG9w0BAQEFAASCAQAPkoNoz92afzxvDMCKsh+MxWBe
LstOmwKYopADbO6OLEgcxzamJH8tWduRFdmSRtIjzRuZrgYoT4pDdhpwszCJY7tDyPBQZYnbDRE2
L0SlE2FYaSn6sbtJO3I6OUN/8k652UMUnwOqMR2DuwcRqLWurr56yeb1X1O0PXm4dYoD9ZmiEiMG
84kCyJBMTxAftKhMJhfOBGjINHgRCOd+27Gyr1I1xOXEjD/wIAIFDrVRKCiqY2aszK85ezgs8nS4
Nfeylr0yij9KJXsvR/5ZbvDyKUwgTIIxMJ2h3dAAh3SloXQZJpcQzvF8A2hRZaf3nwjE43u0odde
owHaZUp5fejiAAAAAAAA

------=_NextPart_000_0017_01C50471.4B26D9A0--



--===============1461258034==
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

--===============1461258034==--




From mmusic-bounces@ietf.org  Mon Jan 31 04:13:26 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 EAA04668
	for <mmusic-web-archive@ietf.org>; Mon, 31 Jan 2005 04:13:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CvXuZ-00063x-FR
	for mmusic-web-archive@ietf.org; Mon, 31 Jan 2005 04:31:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvXSl-0002ny-AN; Mon, 31 Jan 2005 04:03:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvXLH-0001o9-Ju
	for mmusic@megatron.ietf.org; Mon, 31 Jan 2005 03:55:31 -0500
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 DAA03789
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 03:55:30 -0500 (EST)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvXdC-0005nw-Al
	for mmusic@ietf.org; Mon, 31 Jan 2005 04:14:02 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id j0V8tTFF003759
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 09:55:29 +0100
Received: from MCHN070C (mhpaba5c.mchp.siemens.de [139.23.204.46])
	by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id j0V8tSHY001218
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 09:55:28 +0100
From: "Steffen Fries" <steffen.fries@siemens.com>
Organization: Siemens AG
To: mmusic@ietf.org
Date: Mon, 31 Jan 2005 09:55:29 +0100
MIME-Version: 1.0
Message-ID: <41FE0091.10297.E111418@localhost>
Priority: normal
X-mailer: Pegasus Mail for Windows (4.21c)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7BIT
Subject: [MMUSIC] Question to draft-ietf-mmusic-kmgmt-ext-12.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: steffen.fries@siemens.com
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7BIT

Hi,

I've got a question to the usage of draft-ietf-mmusic-kmgmt-ext-
12.txt together with MIKEY. 

Within section 6.1 the MIKEY interface is described. Both uses 
cases stream related MIKEY and session related MIKEY is 
desribed. While the stream related usage is straight forward and 
also discussed within MIKEY I'm not sure if the same is true for 
the session related MIKEY application. 

The following is stated to MIKEY usage on session level:
" ... When referring to streams described in SDP, MIKEY 
allocated two consecutive numbers for the related Crypto Session 
indexes (as each stream can be bi-directional). An example: if 
the SDP contains two m lines (specifying whatever direction of 
the streams), and MIKEY is at the session level, then MIKEY 
allocates e.g. the Crypto Sessions Identifiers (CS IDs, see 
[MIKEY)] '1' and '2' for the first m line, and '3' and '4' for 
the second m line. ..."

This describes a recommendation but doesn't it need to be a MUST 
statement to ensure interoperability of products from different 
vendors? Maybe I missed something in the draft or is it stated 
elsewhere?

Regards
	Steffen


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


From mmusic-bounces@ietf.org  Mon Jan 31 07:43:33 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 HAA22278
	for <mmusic-web-archive@ietf.org>; Mon, 31 Jan 2005 07:43:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CvbBv-0001wI-Cj
	for mmusic-web-archive@ietf.org; Mon, 31 Jan 2005 08:02:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvalx-0007lE-B9; Mon, 31 Jan 2005 07:35:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvafo-0006wQ-GX
	for mmusic@megatron.ietf.org; Mon, 31 Jan 2005 07:28:56 -0500
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 HAA21362
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 07:28:55 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvaxk-0001Yp-Cz
	for mmusic@ietf.org; Mon, 31 Jan 2005 07:47:29 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:51617)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42)
	id 1CvafH-0001SG-NN
	for mmusic@ietf.org; Mon, 31 Jan 2005 12:28:23 +0000
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <200501132049.PAA14428@ietf.org>
References: <200501132049.PAA14428@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <e8f9cec21f8872aab2fccd4dee113c7e@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-bfcp-00.txt
Date: Mon, 31 Jan 2005 12:28:17 +0000
To: IETF MMUSIC Working Group <mmusic@ietf.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

On 13 Jan 2005, at 20:49, Internet-Drafts@ietf.org wrote:
> Title		: Session Description Protocol (SDP) Format for Binary
> 			  Floor Control Protocol (BFCP) Streams
> Author(s)	: G. Camarillo
> Filename	: draft-ietf-mmusic-sdp-bfcp-00.txt
> Pages		: 11
> Date		: 2005-1-13

I have just one comment: the "k=" line is marked as "NOT RECOMMENDED" 
in sdp-new-23, which also states that "The key field MUST NOT be used 
unless it can be guaranteed that the SDP is conveyed over a secure and 
trusted channel" (these changes were made as a result of IESG review 
comments).

To be compatible with these rules this draft needs to clearly explain 
why "k=" is the right solution, and mandate that the SDP is protected 
("MUST" rather than the current "SHOULD" in Security Considerations).

Otherwise, this looks good.

Colin


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


From mmusic-bounces@ietf.org  Mon Jan 31 09:50:01 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 JAA07534
	for <mmusic-web-archive@ietf.org>; Mon, 31 Jan 2005 09:50:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CvdAK-0005Cl-5j
	for mmusic-web-archive@ietf.org; Mon, 31 Jan 2005 10:08:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvcma-0004K8-Sr; Mon, 31 Jan 2005 09:44:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvciS-0003KT-O8
	for mmusic@megatron.ietf.org; Mon, 31 Jan 2005 09:39:49 -0500
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 JAA06271
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 09:39:47 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvd0Q-0004tS-11
	for mmusic@ietf.org; Mon, 31 Jan 2005 09:58:22 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	j0VEdjh5006534; Mon, 31 Jan 2005 15:39:45 +0100 (MET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 31 Jan 2005 15:39:56 +0100
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 31 Jan 2005 15:39:55 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [MMUSIC] Question to draft-ietf-mmusic-kmgmt-ext-12.txt
Date: Mon, 31 Jan 2005 15:39:54 +0100
Message-ID: <0CDAE977A7172A40A2A3A1C20C12BD6559AFB0@esealmw106.eemea.ericsson.se>
Thread-Topic: [MMUSIC] Question to draft-ietf-mmusic-kmgmt-ext-12.txt
Thread-index: AcUHdTI1AjjIFMLaS42cp/D3/S5DxwALRIlw
From: "Elisabetta Carrara \(AL/EAB\)" <elisabetta.carrara@ericsson.com>
To: <steffen.fries@siemens.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 31 Jan 2005 14:39:55.0013 (UTC)
	FILETIME=[BACEAB50:01C507A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable

Hi Steffen,
right, thanks for pointing this out.=20
We will modify the text.

Cheers
/E

>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]On Behalf
>Of Steffen Fries
>Sent: den 31 januari 2005 09:55
>To: mmusic@ietf.org
>Subject: [MMUSIC] Question to draft-ietf-mmusic-kmgmt-ext-12.txt
>
>
>Hi,
>
>I've got a question to the usage of draft-ietf-mmusic-kmgmt-ext-
>12.txt together with MIKEY.=20
>
>Within section 6.1 the MIKEY interface is described. Both uses=20
>cases stream related MIKEY and session related MIKEY is=20
>desribed. While the stream related usage is straight forward and=20
>also discussed within MIKEY I'm not sure if the same is true for=20
>the session related MIKEY application.=20
>
>The following is stated to MIKEY usage on session level:
>" ... When referring to streams described in SDP, MIKEY=20
>allocated two consecutive numbers for the related Crypto Session=20
>indexes (as each stream can be bi-directional). An example: if=20
>the SDP contains two m lines (specifying whatever direction of=20
>the streams), and MIKEY is at the session level, then MIKEY=20
>allocates e.g. the Crypto Sessions Identifiers (CS IDs, see=20
>[MIKEY)] '1' and '2' for the first m line, and '3' and '4' for=20
>the second m line. ..."
>
>This describes a recommendation but doesn't it need to be a MUST=20
>statement to ensure interoperability of products from different=20
>vendors? Maybe I missed something in the draft or is it stated=20
>elsewhere?
>
>Regards
>	Steffen
>
>
>_______________________________________________
>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 Jan 31 10:27:33 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 KAA12000
	for <mmusic-web-archive@ietf.org>; Mon, 31 Jan 2005 10:27:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cvdkf-00068Y-4L
	for mmusic-web-archive@ietf.org; Mon, 31 Jan 2005 10:46:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvdRc-0005rD-LS; Mon, 31 Jan 2005 10:26:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvdM8-0004ig-Kc
	for mmusic@megatron.ietf.org; Mon, 31 Jan 2005 10:20:48 -0500
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 KAA11287
	for <mmusic@ietf.org>; Mon, 31 Jan 2005 10:20:46 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvde6-0005xn-TD
	for mmusic@ietf.org; Mon, 31 Jan 2005 10:39:23 -0500
Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com
	[132.245.205.52])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j0VFKDq26924; Mon, 31 Jan 2005 10:20:13 -0500 (EST)
Received: from [47.16.67.123] (ldondeti-3.us.nortel.com [47.16.67.123]) by
	zbl6c002.us.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id ZAVFJBWG; Mon, 31 Jan 2005 10:20:12 -0500
Message-ID: <41FE4CAC.8060406@nortelnetworks.com>
Date: Mon, 31 Jan 2005 23:20:12 +0800
From: "Dondeti, Lakshminath" <ldondeti@nortelnetworks.com>
Organization: Nortel Networks
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: msec@securemulticast.org, mmusic@ietf.org
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit
Cc: Dragan Ignjatic <ignjatic@nortel.com>
Subject: [MMUSIC] [Fwd: I-D ACTION:draft-ignjatic-msec-mikey-rsa-r-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: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit

Hi all,

Dragan Ignjatic and I submitted an I-D proposing a new MIKEY RSA 
exchange that is very useful in certain deployment scenarios.  Please 
review and send comments to the MSEC list.  We plan to present it at the 
Minneapolis meeting, but a discussion on the list would benefit folks 
who might not be making the trip. 

Many thanks.

best regards,
Lakshminath

-------- Original Message --------
Subject: 	I-D ACTION:draft-ignjatic-msec-mikey-rsa-r-00.txt
Date: 	Fri, 28 Jan 2005 15:56:54 -0500
From: 	Internet-Drafts@ietf.org
Reply-To: 	internet-drafts@ietf.org
To: 	i-d-announce@ietf.org



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


	Title		: An additional mode of key distribution in MIKEY
	Author(s)	: D. Ignjatic, L. Dondeti
	Filename	: draft-ignjatic-msec-mikey-rsa-r-00.txt
	Pages		: 10
	Date		: 2005-1-28
	
The MIKEY specification [2] describes several modes of key
   distribution to setup SRTP [4] sessions, viz., pre-shared key,
   public-key, and an optional Diffie-Hellman key exchange.  In the
   public-key mode the initiator encrypts a random key with the
   responder's public key and sends it to the responder.  In many VoIP
   calling scenarios, the initiator may not know the responder's public
   key or in some cases the responder's ID (e.g., call forwarding) in
   advance.  We propose a new MIKEY mode that works well in such
   scenarios.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ignjatic-msec-mikey-rsa-r-00.txt

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


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ignjatic-msec-mikey-rsa-r-00.txt".

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


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

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




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


