From mmusic-bounces@ietf.org Tue May 01 16:33:38 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hiz2P-0006f0-NX; Tue, 01 May 2007 16:33:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hiz2O-0006et-Ta
	for mmusic@ietf.org; Tue, 01 May 2007 16:33:28 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hiz2O-0005dF-Jh
	for mmusic@ietf.org; Tue, 01 May 2007 16:33:28 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 01 May 2007 13:33:26 -0700
X-IronPort-AV: i="4.14,475,1170662400"; 
	d="scan'208"; a="57352491:sNHT49259106"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l41KXQFh011038; 
	Tue, 1 May 2007 13:33:26 -0700
Received: from dwingwxp ([10.32.240.196])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l41KXLwn006332;
	Tue, 1 May 2007 20:33:21 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
	"'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: ICE pacing connectivity
	checks	(wasRE:[MMUSIC]	WGLC:	draft-ietf-mmusic-ice-15.txt)
Date: Tue, 1 May 2007 13:33:20 -0700
Message-ID: <053001c78c2f$f848a350$c4f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AceLi+FNFv7O0OoyQfeIcB2ppTtWsAAovvYA
In-Reply-To: <463690BF.3020500@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3287; t=1178051606;
	x=1178915606; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20ICE=20pacing=20connectivity=20checks=09(wasRE=3A[MMUS
	IC]=09WGLC=3A=09draft-ietf-mmusic-ice-15.txt) |Sender:=20;
	bh=ZTBIyvTsnfwOf80ISN/a7MQcFedSbHHGmdZXW2OGMa0=;
	b=GtB+CRPbTx6BxmxQelUsU/eF81PknpVkzPREm5L/A8M81dzo+NbAaFj9N6oxtgDmJoIerV3D
	HBfIbeOg8QXxd5xlLhNe8sf2mKT4ZVMpCThPk3FM/P4juT38R+LovVCM;
Authentication-Results: sj-dkim-5; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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>
Errors-To: mmusic-bounces@ietf.org

Magnus wrote:
 
...
> >> My question is what do you win with that rather than moving the 
> >> triggered checks to the top of the paced list. That way 
> >> you keep the 
> >> rate and avoid hurting yourself more than what you would 
> >> by instantly 
> >> initiate the triggered checks.
> > 
> > Its not just new transactions; in most cases a triggered check is a 
> > retransmit of a transaction already in progress.
> 
> I had forgotten this. And the reason for doing that is that 
> it is quite likely that the previous transmission was dropped 
> in the NAT where now a binding exist?

Exactly.  Or (less likely) the packet was dropped by the network.

> > Pacing those along with 
> > periodic checks requires me to mix both of those things 
> > into a single 
> > mechanism, which I don't like. I prefer a cleaner 
> > separation of ICE and STUN.
> 
> I can, understand that. You still have an interface question for the
> triggered checks, where ICE needs to tell an ongoing STUN transaction
> that the check should be retransmitted. Not complicating that 
> case is fine.
> 
> However for all the other cases from the list in section 7.2.1.4 using
> pacing to start the triggered checks seems easy to implement. It also
> appears there is a good reason for pacing as it prevents multiple
> triggered checks to significantly increase the bit-rate 
> consumed.

I'll let Jonathan comment.  

> But I
> would appreciate more data how this actually play out in a case where
> there is multiple medias in a session. Because to me it appears that
> when a peer finds the combination of interfaces that works, it will
> start unfreezing a lot of candidates that will get through and
> triggered checks.

At the point where ICE decides to unfreeze the other m= lines and
do its checks, it'll only do one STUN transaction on each of those
other m= lines, unless that STUN transaction fails (which isn't
very likely).  If the STUN transaction fails it'll get 
retransmitted and other a=candidates in that m= line will get 
processed per our rules.

I guess, at that time, you're already sending RTP out the first
media line (audio, probably).  And we'd want to reduce those ICE 
checks to not consume the bandwidth of the audio session.

The easiest and most effective way to do that is constrain each 
of the ICE checks to the bandwidth of their respective m= lines, 
rather than the sum of RTP bandwidth available to all of the
m= lines.

> I would really appreciate some simulation data for
> cases that are a bit more extreme when it comes to the number of
> candidates and medias.

That excel spreadsheet currently handles 10 candidates; how many
more do you want simulated?

-d


> Cheers
> 
> Magnus Westerlund
> 
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> 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 May 01 17:21:06 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HizmT-0005bl-8U; Tue, 01 May 2007 17:21:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HizmR-0005bg-LU
	for mmusic@ietf.org; Tue, 01 May 2007 17:21:03 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HizmP-0004Kn-UP
	for mmusic@ietf.org; Tue, 01 May 2007 17:21:03 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5499520585; Tue,  1 May 2007 23:21:01 +0200 (CEST)
X-AuditID: c1b4fb3e-ae9ecbb0000061ca-7d-4637af3d5055 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	33DFD2005E; Tue,  1 May 2007 23:21:01 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 23:21:01 +0200
Received: from [138.85.4.21] ([138.85.4.21]) by esealmw126.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 May 2007 23:21:00 +0200
Message-ID: <4637AF3A.30609@ericsson.com>
Date: Tue, 01 May 2007 23:20:58 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: ICE pacing connectivity
	checks	(wasRE:[MMUSIC]	WGLC:	draft-ietf-mmusic-ice-15.txt)
References: <053001c78c2f$f848a350$c4f0200a@amer.cisco.com>
In-Reply-To: <053001c78c2f$f848a350$c4f0200a@amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 May 2007 21:21:00.0306 (UTC)
	FILETIME=[9D91F720:01C78C36]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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>
Errors-To: mmusic-bounces@ietf.org

Dan Wing skrev:
> Magnus wrote:

>> But I
>> would appreciate more data how this actually play out in a case where
>> there is multiple medias in a session. Because to me it appears that
>> when a peer finds the combination of interfaces that works, it will
>> start unfreezing a lot of candidates that will get through and
>> triggered checks.
> 
> At the point where ICE decides to unfreeze the other m= lines and
> do its checks, it'll only do one STUN transaction on each of those
> other m= lines, unless that STUN transaction fails (which isn't
> very likely).  If the STUN transaction fails it'll get 
> retransmitted and other a=candidates in that m= line will get 
> processed per our rules.
> 
> I guess, at that time, you're already sending RTP out the first
> media line (audio, probably).  And we'd want to reduce those ICE 
> checks to not consume the bandwidth of the audio session.
> 
> The easiest and most effective way to do that is constrain each 
> of the ICE checks to the bandwidth of their respective m= lines, 
> rather than the sum of RTP bandwidth available to all of the
> m= lines.

Okay, I think there need to go into some thought into if the 
connectivity checks are happening from individual bit-rate budgets or if 
there are a common one. There are some issues with getting completion if 
some media streams are very low bit-rate compared to other large bandwidth.

> 
>> I would really appreciate some simulation data for
>> cases that are a bit more extreme when it comes to the number of
>> candidates and medias.
> 
> That excel spreadsheet currently handles 10 candidates; how many
> more do you want simulated?
> 

What is needed is to understand how it behaves from small cases with a 
few candidates all the way up to the upper limit that ICE allows. Which 
means at least 100 candidates needs to be looked at.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 May 01 18:54:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hj1Ee-0004QX-Lm; Tue, 01 May 2007 18:54:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hj1Ed-0004QN-Bf
	for mmusic@ietf.org; Tue, 01 May 2007 18:54:15 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hj1Eb-0005UH-0G
	for mmusic@ietf.org; Tue, 01 May 2007 18:54:15 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 01 May 2007 15:54:13 -0700
X-IronPort-AV: i="4.14,475,1170662400"; 
	d="scan'208"; a="417623787:sNHT46558788"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l41MsCGu007020; 
	Tue, 1 May 2007 15:54:12 -0700
Received: from dwingwxp ([10.32.240.196])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l41MsBwn022349;
	Tue, 1 May 2007 22:54:11 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Subject: RE: ICE pacing connectivity
	checks	(wasRE:[MMUSIC]	WGLC:	draft-ietf-mmusic-ice-15.txt)
Date: Tue, 1 May 2007 15:54:08 -0700
Message-ID: <05c501c78c43$a0de01f0$c4f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AceMNqBesZ7OSxY/RsaLHsShpVvkxwAAEZ1A
In-Reply-To: <4637AF3A.30609@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2156; t=1178060052;
	x=1178924052; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20ICE=20pacing=20connectivity=20checks=09(wasRE=3A[MMUS
	IC]=09WGLC=3A=09draft-ietf-mmusic-ice-15.txt) |Sender:=20;
	bh=t2NqQtNJSRt3rSvyvTJo35s6aDV7ZqtjSZYwAdS1pNI=;
	b=Cx8E/fgLanZqPNq9mcD7FqdYB/ejHn75l1jF0Ee9ca7mo9GdNSSzEaw0Fp2KPB0ReQkI1qxS
	hMgxkhGHufr4xo5JK3sZdmQWbAFIwHD+ONIIdMTWn2cKM8eunmofpLlI;
Authentication-Results: sj-dkim-7; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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>
Errors-To: mmusic-bounces@ietf.org


> > The easiest and most effective way to do that is constrain each 
> > of the ICE checks to the bandwidth of their respective m= lines, 
> > rather than the sum of RTP bandwidth available to all of the
> > m= lines.
> 
> Okay, I think there need to go into some thought into if the 
> connectivity checks are happening from individual bit-rate 
> budgets or if there are a common one. There are some issues 
> with getting completion if some media streams are very low 
> bit-rate compared to other large bandwidth.

We have to make some guesses, then.  The most important 
guess is if the network polices our flows by the sum of
those media lines or (as with, for example, a PacketCable
network) the network would police the flows by each m= 
line.

If the network is bandwidth constrained (dialup, DSL, etc.),
the limit is overall bandwidth.  If there is a bandwidth
policer in place doing Smart Things (tm), it may well be
smart enough to help us (give us the sum of both media
lines' bandwidth) or smart enough to be difficult (give 
us the bandwidth indicated in each of the media lines).

> >> I would really appreciate some simulation data for
> >> cases that are a bit more extreme when it comes to the number of
> >> candidates and medias.
> > 
> > That excel spreadsheet currently handles 10 candidates; how many
> > more do you want simulated?
> 
> What is needed is to understand how it behaves from small 
> cases with a few candidates all the way up to the upper 
> limit that ICE allows.  Which means at least 100 candidates 
> needs to be looked at.

With my current estimate of 108 bytes of UDP payload for a STUN
packet, and 40 bytes of UDP payload every 20ms for RTP (which
is similar to G.726), it would take a bit over 3 seconds for
the initial STUN checks to be sent out.

If we need 100 candidates to work, we would need a more 
aggressive algorithm than what I had previously suggested, 
which would exceed the already-undesirable bandwidth
consumption of RTP.

A new excel spreadsheet that handles 0-100 candidates is
at http://www.employees.org/~dwing/ice-rtp-backoff.xls

-d

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



From mmusic-bounces@ietf.org Wed May 02 15:31:29 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjKXu-0001t5-Gr; Wed, 02 May 2007 15:31:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjKXt-0001t0-J2
	for mmusic@ietf.org; Wed, 02 May 2007 15:31:25 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjKXr-0000WP-Ok
	for mmusic@ietf.org; Wed, 02 May 2007 15:31:25 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l42JVHwb024018
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 2 May 2007 12:31:17 -0700
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l42JVGkA022323;
	Wed, 2 May 2007 12:31:16 -0700 (PDT)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 2 May 2007 12:31:16 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Wed, 2 May 2007 12:31:17 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD1464@NAEX01.na.qualcomm.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B02BD2AEF@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on
	draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAHWxPNA=
References: <2CA3E1B6CEC064449CAA7D0FAB46079B02BD20FA@NAEX01.na.qualcomm.com><9F6ACAE02B6DD040A1E259977622CFDB268CC3@oslexcp1.eu.tandberg.int>
	<2CA3E1B6CEC064449CAA7D0FAB46079B02BD2AEF@NAEX01.na.qualcomm.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 02 May 2007 19:31:16.0385 (UTC)
	FILETIME=[73A91910:01C78CF0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fec852dbea6d068499ed3250edf328e2
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, roni.even@polycom.co.il,
	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>
Errors-To: mmusic-bounces@ietf.org

Given that there are already implementations of TIAS it is clear that
changing the direction of TIAS is not the correct direction.

The "MSR" attribute defined in
draft-hdesinen-mmusic-oa-send-bw-attr-02.tx would still be useful to
signal bit-rate (RTP Payload) in 'send' direction. Based on the
discussions we had on this thread, the following would make sense to
address the problem completely.=20

 1. Obsolete (TIAS, maxprate) for offer/answer and limit it to
declarative
 usage (Updates rfc3890)
 2. Propose MSPR (max send packet rate)
 3. Propose RB (receive bit-rate at layer X)
 4. Propose PO (packet overhead from layer X to the application layer)

Media Sender would attempt to satisfy the equation -->=20
MSR+ (PO*MSPR) <=3D RB=20

[
MSR - local send RTP payload bit-rate,
PO- remote packet overhead at layer X,
MSPR- local max packet send rate,
RB- remote last hop receive bit-rate at layer X
]

I prefer this to be captured in a new draft named "SDP attributes for
Offer/Answer Sessions" rather than having a draft for "MSR" attribute
alone.


Let me know if you have any comments.

Thanks,
Hari


> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Monday, April 30, 2007 4:13 AM
> To: Geir Arne Sandbakken; mmusic@ietf.org
> Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Geir,
>=20
> Thanks for your feedback.
>=20
> Can you elaborate on how exactly this attribute is used in the
> implementations known to you? I'd like to understand how closely or
> differently it is used from the way it is documented in rfc3890.
>=20
> Thanks,
> Hari
>=20
> > -----Original Message-----
> > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > Sent: Wednesday, April 25, 2007 1:31 AM
> > To: Desineni, Harikishan; mmusic@ietf.org
> > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Harikishan,
> >
> > We have been using TIAS in the 'recv' direction for quite a while,
and
> I
> > know of multiple other implementations.  Think we have been
promoting
> > the usage in the last 3 SIPit's, and changing the direction will
lead
> to
> > serious interoperability issues.
> >
> > I do agree that a 'send' direction attribute is desirable as
> additional
> > bandwidth information, and I hope it can be done without breaking
> > existing implementations.
> >
> > Cheers,
> > Geir Arne
> >
> > > -----Original Message-----
> > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > Sent: 17 April 2007 20:40
> > > To: mmusic@ietf.org
> > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Some issues with the offer/answer usage of TIAS (defined in
RFC3890)
> > > came out while discussing
> > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > >
> > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> direction
> > > attributes in offer/answer model. As 'recv' attributes, TIAS and
> > > maxprate do not solve the bandwidth negotiation problem. For
> > > offer/answer bw negotiation to work properly, the correct
direction
> in
> > > rfc3890 should have been 'send', probably with the help of few new
> > > 'recv' direction attributes (like PO - per packet overhead at
layer
> X,
> > > RB- receive BW at layer X) under discussion.
> > >
> > > A sender would choose (TIAS,maxprate) which satisfy the following
> > > formula
> > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by the
> receiver)
> > >
> > > One approach to handle this is changing the direction of
> > (TIAS,maxprate)
> > > to 'send' and prevent the incorrect ('recv') usage of
> (TIAS,maxprate)
> > in
> > > offer/answer model. While this appears to be the desired
direction,
> I
> > am
> > > interested to know the impact of such a change on (any) existing
> > > implementations of TIAS in offer/answer.
> > >
> > > Please comment if you are aware of any existing implementations of
> > TIAS
> > > in offer/answer and also describe how exactly TIAS was used in
that
> > > particular implementation.
> > >
> > > Thanks,
> > > Hari
> > >
> > >
> > > > -----Original Message-----
> > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > avt@ietf.org
> > > > Subject: RE: [MMUSIC] Comments on
> > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > 02.txt
> > > >
> > > > I copied a post (from AVT list) from Roni which states that TIAS
> was
> > > > actually used in his implementation. I am not sure if it is an
> > > > implementation in offer/answer model.
> > > >
> > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > >
> > > > "
> > > > -----Original Message-----
> > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > To: Randell Jesup
> > > > Cc: Stephan Wenger; avt@ietf.org
> > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
include
> > > > theheaderoverhead
> > > >
> > > > Randell,
> > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > compatibility
> > > > with systems that do not support TIAS. This RFC gives a good
> > > explanation
> > > > why to use TIAS. This is what we do in our implementation.
> > > > "
> > > >
> > > > > -----Original Message-----
> > > > > From: Magnus Westerlund
[mailto:magnus.westerlund@ericsson.com]
> > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > To: Desineni, Harikishan
> > > > > Cc: mmusic@ietf.org
> > > > > Subject: Re: [MMUSIC] Comments on
> > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > 02.txt
> > > > >
> > > > > Desineni, Harikishan skrev:
> > > > > >
> > > > > >
> > > > > > Magnus,
> > > > > >
> > > > > > Thanks for the comments.
> > > > > >
> > > > > > In the initial version, I captured the current understanding
> of
> > > > (TIAS
> > > > > > ,maxprate) based on RFC3890.
> > > > > >
> > > > > > Based on the current RFCs, majority of the community
> interprets
> > > TIAS
> > > > as
> > > > > > receive only direction attribute. Instead of updating
RFC3890
> to
> > > > modify
> > > > > > TIAS as a send direction only attribute, it is better to use
a
> > new
> > > > > > attribute 'MSR' proposed in this draft. This would also
avoid
> > any
> > > > > > backward compatibility/inter-op issues that can arise with
> > current
> > > > > > implementations which (correctly) interpret TIAS as receive
> > > > direction
> > > > > > only attribute in offer/answer.
> > > > >
> > > > > Well, I wonder how there can be backwards compatibility issues
> > with
> > > > > something that clearly doesn't work if you actually try to use
> it.
> > > > There
> > > > > might be implementations but I can't really understand how
they
> > > could
> > > > > work. Do you know of implementations?
> > > > >
> > > > > >
> > > > > > Another approach is to add directionality to TIAS. By
default,
> > > TIAS
> > > > is
> > > > > > receive only (not much useful) and "TIAS/sendonly" will be
> send
> > > only
> > > > > > direction. "maxprate/send" will be packet rate in send
> > direction.
> > > > > >
> > > > > > What you are proposing is the following
> > > > > > Send direction attributes: RTP Payload rate and maxpacket
rate
> > > > > > Receive direction attributes: AS (or a new one), packet
> overhead
> > > > >
> > > > > Okay, here I think the more important question is, are we
> > expecting
> > > to
> > > > > be able to specify a value on another level than IP? If not I
> > think
> > > AS
> > > > > works fine.
> > > > >
> > > > > >
> > > > > > In this draft I am proposing that 'MSR' be used for
signaling
> > RTP
> > > > > > payload rate in 'send' direction. IMO, it is not a clean
> > approach
> > > to
> > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > >
> > > > > We disagree on this. TIAS was specified as a send direction
> > > attribute.
> > > > I
> > > > > made an error in the offer/answer usage because I didn't
> consider
> > > the
> > > > > implications. And no one picked up on it.
> > > > >
> > > > > As I can see it in regards to RFC 3890 we have two
alternatives:
> > > > >
> > > > > 1. Fix the offer/answer section to correctly define it to
apply
> in
> > > the
> > > > > sending direction.
> > > > >
> > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and only
use
> > it
> > > > for
> > > > > declarative usage, like in RTSP.
> > > > >
> > > > > If there are implementations i any numbers that interpret TIAS
> as
> > a
> > > > > receiver direction attribute then I agree alternative 2 will
be
> > > best.
> > > > > However I would like to have some positive acknowledgments of
> this
> > > > > first. This was after all revealed in the attempt to apply
TIAS
> to
> > > > > offer/answer in the 3GPP MTSI standardization work. Resulting
in
> > > that
> > > > > TIAS was only included in the draft spec for a while. I don't
> know
> > > if
> > > > > some other umbrella standard has included TIAS combined with
> > > > offer/answer.
> > > > >
> > > > > >
> > > > > > I am OK with signaling packet rate in send direction. But we
> > need
> > > to
> > > > > > consider whether to reuse maxprate for this or add
> > directionality
> > > to
> > > > > > maxprate (maxprate/send) to avoid any inter-op issues with
> > current
> > > > > > implementations.
> > > > > >
> > > > >
> > > > > Cheers
> > > > >
> > > > > Magnus Westerlund
> > > > >
> > > > > IETF Transport Area Director & TSVWG Chair
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > S-164 80 Stockholm, Sweden | mailto:
> > magnus.westerlund@ericsson.com
> > > > >
> > >
> ----------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > mmusic mailing list
> > > > mmusic@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic
>=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 May 03 02:00:16 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjUMQ-0004IE-97; Thu, 03 May 2007 02:00:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjUMP-0004I9-DY
	for mmusic@ietf.org; Thu, 03 May 2007 02:00:13 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjUMN-0001oX-Hh
	for mmusic@ietf.org; Thu, 03 May 2007 02:00:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Thu, 3 May 2007 09:00:41 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0484F1CB@IsrExch01.israel.polycom.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD1464@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on
	draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAHWxPNAAFklQwA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>, <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4166dd0e0c668adc975c3d3e0f1bce3b
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Harry,
According to Geir Arne and I the usage today of TIAS is as a receive
capability in the media line. As far as I understand declaratives means
on the send direction, so please clarify the usage for receive
capability.
Roni

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Wednesday, May 02, 2007 10:31 PM
> To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Given that there are already implementations of TIAS it is clear that
> changing the direction of TIAS is not the correct direction.
>=20
> The "MSR" attribute defined in
> draft-hdesinen-mmusic-oa-send-bw-attr-02.tx would still be useful to
> signal bit-rate (RTP Payload) in 'send' direction. Based on the
> discussions we had on this thread, the following would make sense to
> address the problem completely.
>=20
>  1. Obsolete (TIAS, maxprate) for offer/answer and limit it to
> declarative
>  usage (Updates rfc3890)
>  2. Propose MSPR (max send packet rate)
>  3. Propose RB (receive bit-rate at layer X)
>  4. Propose PO (packet overhead from layer X to the application layer)
>=20
> Media Sender would attempt to satisfy the equation -->
> MSR+ (PO*MSPR) <=3D RB
>=20
> [
> MSR - local send RTP payload bit-rate,
> PO- remote packet overhead at layer X,
> MSPR- local max packet send rate,
> RB- remote last hop receive bit-rate at layer X
> ]
>=20
> I prefer this to be captured in a new draft named "SDP attributes for
> Offer/Answer Sessions" rather than having a draft for "MSR" attribute
> alone.
>=20
>=20
> Let me know if you have any comments.
>=20
> Thanks,
> Hari
>=20
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Monday, April 30, 2007 4:13 AM
> > To: Geir Arne Sandbakken; mmusic@ietf.org
> > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> > RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Geir,
> >
> > Thanks for your feedback.
> >
> > Can you elaborate on how exactly this attribute is used in the
> > implementations known to you? I'd like to understand how closely or
> > differently it is used from the way it is documented in rfc3890.
> >
> > Thanks,
> > Hari
> >
> > > -----Original Message-----
> > > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > To: Desineni, Harikishan; mmusic@ietf.org
> > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Harikishan,
> > >
> > > We have been using TIAS in the 'recv' direction for quite a while,
> and
> > I
> > > know of multiple other implementations.  Think we have been
> promoting
> > > the usage in the last 3 SIPit's, and changing the direction will
> lead
> > to
> > > serious interoperability issues.
> > >
> > > I do agree that a 'send' direction attribute is desirable as
> > additional
> > > bandwidth information, and I hope it can be done without breaking
> > > existing implementations.
> > >
> > > Cheers,
> > > Geir Arne
> > >
> > > > -----Original Message-----
> > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > Sent: 17 April 2007 20:40
> > > > To: mmusic@ietf.org
> > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Some issues with the offer/answer usage of TIAS (defined in
> RFC3890)
> > > > came out while discussing
> > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > >
> > > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> > direction
> > > > attributes in offer/answer model. As 'recv' attributes, TIAS and
> > > > maxprate do not solve the bandwidth negotiation problem. For
> > > > offer/answer bw negotiation to work properly, the correct
> direction
> > in
> > > > rfc3890 should have been 'send', probably with the help of few
new
> > > > 'recv' direction attributes (like PO - per packet overhead at
> layer
> > X,
> > > > RB- receive BW at layer X) under discussion.
> > > >
> > > > A sender would choose (TIAS,maxprate) which satisfy the
following
> > > > formula
> > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by the
> > receiver)
> > > >
> > > > One approach to handle this is changing the direction of
> > > (TIAS,maxprate)
> > > > to 'send' and prevent the incorrect ('recv') usage of
> > (TIAS,maxprate)
> > > in
> > > > offer/answer model. While this appears to be the desired
> direction,
> > I
> > > am
> > > > interested to know the impact of such a change on (any) existing
> > > > implementations of TIAS in offer/answer.
> > > >
> > > > Please comment if you are aware of any existing implementations
of
> > > TIAS
> > > > in offer/answer and also describe how exactly TIAS was used in
> that
> > > > particular implementation.
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > > avt@ietf.org
> > > > > Subject: RE: [MMUSIC] Comments on
> > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > 02.txt
> > > > >
> > > > > I copied a post (from AVT list) from Roni which states that
TIAS
> > was
> > > > > actually used in his implementation. I am not sure if it is an
> > > > > implementation in offer/answer model.
> > > > >
> > > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > > >
> > > > > "
> > > > > -----Original Message-----
> > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > To: Randell Jesup
> > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
> include
> > > > > theheaderoverhead
> > > > >
> > > > > Randell,
> > > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > > compatibility
> > > > > with systems that do not support TIAS. This RFC gives a good
> > > > explanation
> > > > > why to use TIAS. This is what we do in our implementation.
> > > > > "
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Magnus Westerlund
> [mailto:magnus.westerlund@ericsson.com]
> > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > To: Desineni, Harikishan
> > > > > > Cc: mmusic@ietf.org
> > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > 02.txt
> > > > > >
> > > > > > Desineni, Harikishan skrev:
> > > > > > >
> > > > > > >
> > > > > > > Magnus,
> > > > > > >
> > > > > > > Thanks for the comments.
> > > > > > >
> > > > > > > In the initial version, I captured the current
understanding
> > of
> > > > > (TIAS
> > > > > > > ,maxprate) based on RFC3890.
> > > > > > >
> > > > > > > Based on the current RFCs, majority of the community
> > interprets
> > > > TIAS
> > > > > as
> > > > > > > receive only direction attribute. Instead of updating
> RFC3890
> > to
> > > > > modify
> > > > > > > TIAS as a send direction only attribute, it is better to
use
> a
> > > new
> > > > > > > attribute 'MSR' proposed in this draft. This would also
> avoid
> > > any
> > > > > > > backward compatibility/inter-op issues that can arise with
> > > current
> > > > > > > implementations which (correctly) interpret TIAS as
receive
> > > > > direction
> > > > > > > only attribute in offer/answer.
> > > > > >
> > > > > > Well, I wonder how there can be backwards compatibility
issues
> > > with
> > > > > > something that clearly doesn't work if you actually try to
use
> > it.
> > > > > There
> > > > > > might be implementations but I can't really understand how
> they
> > > > could
> > > > > > work. Do you know of implementations?
> > > > > >
> > > > > > >
> > > > > > > Another approach is to add directionality to TIAS. By
> default,
> > > > TIAS
> > > > > is
> > > > > > > receive only (not much useful) and "TIAS/sendonly" will be
> > send
> > > > only
> > > > > > > direction. "maxprate/send" will be packet rate in send
> > > direction.
> > > > > > >
> > > > > > > What you are proposing is the following
> > > > > > > Send direction attributes: RTP Payload rate and maxpacket
> rate
> > > > > > > Receive direction attributes: AS (or a new one), packet
> > overhead
> > > > > >
> > > > > > Okay, here I think the more important question is, are we
> > > expecting
> > > > to
> > > > > > be able to specify a value on another level than IP? If not
I
> > > think
> > > > AS
> > > > > > works fine.
> > > > > >
> > > > > > >
> > > > > > > In this draft I am proposing that 'MSR' be used for
> signaling
> > > RTP
> > > > > > > payload rate in 'send' direction. IMO, it is not a clean
> > > approach
> > > > to
> > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > >
> > > > > > We disagree on this. TIAS was specified as a send direction
> > > > attribute.
> > > > > I
> > > > > > made an error in the offer/answer usage because I didn't
> > consider
> > > > the
> > > > > > implications. And no one picked up on it.
> > > > > >
> > > > > > As I can see it in regards to RFC 3890 we have two
> alternatives:
> > > > > >
> > > > > > 1. Fix the offer/answer section to correctly define it to
> apply
> > in
> > > > the
> > > > > > sending direction.
> > > > > >
> > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and only
> use
> > > it
> > > > > for
> > > > > > declarative usage, like in RTSP.
> > > > > >
> > > > > > If there are implementations i any numbers that interpret
TIAS
> > as
> > > a
> > > > > > receiver direction attribute then I agree alternative 2 will
> be
> > > > best.
> > > > > > However I would like to have some positive acknowledgments
of
> > this
> > > > > > first. This was after all revealed in the attempt to apply
> TIAS
> > to
> > > > > > offer/answer in the 3GPP MTSI standardization work.
Resulting
> in
> > > > that
> > > > > > TIAS was only included in the draft spec for a while. I
don't
> > know
> > > > if
> > > > > > some other umbrella standard has included TIAS combined with
> > > > > offer/answer.
> > > > > >
> > > > > > >
> > > > > > > I am OK with signaling packet rate in send direction. But
we
> > > need
> > > > to
> > > > > > > consider whether to reuse maxprate for this or add
> > > directionality
> > > > to
> > > > > > > maxprate (maxprate/send) to avoid any inter-op issues with
> > > current
> > > > > > > implementations.
> > > > > > >
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > Magnus Westerlund
> > > > > >
> > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > magnus.westerlund@ericsson.com
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > >
> > > > > _______________________________________________
> > > > > mmusic mailing list
> > > > > mmusic@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > >
> > > > _______________________________________________
> > > > mmusic mailing list
> > > > mmusic@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
> > _______________________________________________
> > 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 May 03 02:02:09 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjUOH-0004dA-LZ; Thu, 03 May 2007 02:02:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjUOF-0004cx-VP
	for mmusic@ietf.org; Thu, 03 May 2007 02:02:07 -0400
Received: from fw.polycom.co.il ([212.179.41.2]
	helo=isrexch01.israel.polycom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjUOF-0001yq-7p
	for mmusic@ietf.org; Thu, 03 May 2007 02:02:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Thu, 3 May 2007 09:02:38 +0300
Message-ID: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B02BD2AEF@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>, <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dd887a8966a4c4c217a52303814d0b5f
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hary,
TIAS is being used as a media level attribute indicating the maximum BW
that the receiver would like to get. It is not used in offer answer. The
semantic of the attribute (what is bw) is as specified in RFC 3890

Roni

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Monday, April 30, 2007 2:13 PM
> To: Geir Arne Sandbakken; mmusic@ietf.org
> Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Geir,
>=20
> Thanks for your feedback.
>=20
> Can you elaborate on how exactly this attribute is used in the
> implementations known to you? I'd like to understand how closely or
> differently it is used from the way it is documented in rfc3890.
>=20
> Thanks,
> Hari
>=20
> > -----Original Message-----
> > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > Sent: Wednesday, April 25, 2007 1:31 AM
> > To: Desineni, Harikishan; mmusic@ietf.org
> > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Harikishan,
> >
> > We have been using TIAS in the 'recv' direction for quite a while,
and
> I
> > know of multiple other implementations.  Think we have been
promoting
> > the usage in the last 3 SIPit's, and changing the direction will
lead
> to
> > serious interoperability issues.
> >
> > I do agree that a 'send' direction attribute is desirable as
> additional
> > bandwidth information, and I hope it can be done without breaking
> > existing implementations.
> >
> > Cheers,
> > Geir Arne
> >
> > > -----Original Message-----
> > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > Sent: 17 April 2007 20:40
> > > To: mmusic@ietf.org
> > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Some issues with the offer/answer usage of TIAS (defined in
RFC3890)
> > > came out while discussing
> > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > >
> > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> direction
> > > attributes in offer/answer model. As 'recv' attributes, TIAS and
> > > maxprate do not solve the bandwidth negotiation problem. For
> > > offer/answer bw negotiation to work properly, the correct
direction
> in
> > > rfc3890 should have been 'send', probably with the help of few new
> > > 'recv' direction attributes (like PO - per packet overhead at
layer
> X,
> > > RB- receive BW at layer X) under discussion.
> > >
> > > A sender would choose (TIAS,maxprate) which satisfy the following
> > > formula
> > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by the
> receiver)
> > >
> > > One approach to handle this is changing the direction of
> > (TIAS,maxprate)
> > > to 'send' and prevent the incorrect ('recv') usage of
> (TIAS,maxprate)
> > in
> > > offer/answer model. While this appears to be the desired
direction,
> I
> > am
> > > interested to know the impact of such a change on (any) existing
> > > implementations of TIAS in offer/answer.
> > >
> > > Please comment if you are aware of any existing implementations of
> > TIAS
> > > in offer/answer and also describe how exactly TIAS was used in
that
> > > particular implementation.
> > >
> > > Thanks,
> > > Hari
> > >
> > >
> > > > -----Original Message-----
> > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > avt@ietf.org
> > > > Subject: RE: [MMUSIC] Comments on
> > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > 02.txt
> > > >
> > > > I copied a post (from AVT list) from Roni which states that TIAS
> was
> > > > actually used in his implementation. I am not sure if it is an
> > > > implementation in offer/answer model.
> > > >
> > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > >
> > > > "
> > > > -----Original Message-----
> > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > To: Randell Jesup
> > > > Cc: Stephan Wenger; avt@ietf.org
> > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
include
> > > > theheaderoverhead
> > > >
> > > > Randell,
> > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > compatibility
> > > > with systems that do not support TIAS. This RFC gives a good
> > > explanation
> > > > why to use TIAS. This is what we do in our implementation.
> > > > "
> > > >
> > > > > -----Original Message-----
> > > > > From: Magnus Westerlund
[mailto:magnus.westerlund@ericsson.com]
> > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > To: Desineni, Harikishan
> > > > > Cc: mmusic@ietf.org
> > > > > Subject: Re: [MMUSIC] Comments on
> > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > 02.txt
> > > > >
> > > > > Desineni, Harikishan skrev:
> > > > > >
> > > > > >
> > > > > > Magnus,
> > > > > >
> > > > > > Thanks for the comments.
> > > > > >
> > > > > > In the initial version, I captured the current understanding
> of
> > > > (TIAS
> > > > > > ,maxprate) based on RFC3890.
> > > > > >
> > > > > > Based on the current RFCs, majority of the community
> interprets
> > > TIAS
> > > > as
> > > > > > receive only direction attribute. Instead of updating
RFC3890
> to
> > > > modify
> > > > > > TIAS as a send direction only attribute, it is better to use
a
> > new
> > > > > > attribute 'MSR' proposed in this draft. This would also
avoid
> > any
> > > > > > backward compatibility/inter-op issues that can arise with
> > current
> > > > > > implementations which (correctly) interpret TIAS as receive
> > > > direction
> > > > > > only attribute in offer/answer.
> > > > >
> > > > > Well, I wonder how there can be backwards compatibility issues
> > with
> > > > > something that clearly doesn't work if you actually try to use
> it.
> > > > There
> > > > > might be implementations but I can't really understand how
they
> > > could
> > > > > work. Do you know of implementations?
> > > > >
> > > > > >
> > > > > > Another approach is to add directionality to TIAS. By
default,
> > > TIAS
> > > > is
> > > > > > receive only (not much useful) and "TIAS/sendonly" will be
> send
> > > only
> > > > > > direction. "maxprate/send" will be packet rate in send
> > direction.
> > > > > >
> > > > > > What you are proposing is the following
> > > > > > Send direction attributes: RTP Payload rate and maxpacket
rate
> > > > > > Receive direction attributes: AS (or a new one), packet
> overhead
> > > > >
> > > > > Okay, here I think the more important question is, are we
> > expecting
> > > to
> > > > > be able to specify a value on another level than IP? If not I
> > think
> > > AS
> > > > > works fine.
> > > > >
> > > > > >
> > > > > > In this draft I am proposing that 'MSR' be used for
signaling
> > RTP
> > > > > > payload rate in 'send' direction. IMO, it is not a clean
> > approach
> > > to
> > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > >
> > > > > We disagree on this. TIAS was specified as a send direction
> > > attribute.
> > > > I
> > > > > made an error in the offer/answer usage because I didn't
> consider
> > > the
> > > > > implications. And no one picked up on it.
> > > > >
> > > > > As I can see it in regards to RFC 3890 we have two
alternatives:
> > > > >
> > > > > 1. Fix the offer/answer section to correctly define it to
apply
> in
> > > the
> > > > > sending direction.
> > > > >
> > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and only
use
> > it
> > > > for
> > > > > declarative usage, like in RTSP.
> > > > >
> > > > > If there are implementations i any numbers that interpret TIAS
> as
> > a
> > > > > receiver direction attribute then I agree alternative 2 will
be
> > > best.
> > > > > However I would like to have some positive acknowledgments of
> this
> > > > > first. This was after all revealed in the attempt to apply
TIAS
> to
> > > > > offer/answer in the 3GPP MTSI standardization work. Resulting
in
> > > that
> > > > > TIAS was only included in the draft spec for a while. I don't
> know
> > > if
> > > > > some other umbrella standard has included TIAS combined with
> > > > offer/answer.
> > > > >
> > > > > >
> > > > > > I am OK with signaling packet rate in send direction. But we
> > need
> > > to
> > > > > > consider whether to reuse maxprate for this or add
> > directionality
> > > to
> > > > > > maxprate (maxprate/send) to avoid any inter-op issues with
> > current
> > > > > > implementations.
> > > > > >
> > > > >
> > > > > Cheers
> > > > >
> > > > > Magnus Westerlund
> > > > >
> > > > > IETF Transport Area Director & TSVWG Chair
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > S-164 80 Stockholm, Sweden | mailto:
> > magnus.westerlund@ericsson.com
> > > > >
> > >
> ----------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > mmusic mailing list
> > > > mmusic@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> > > _______________________________________________
> > > mmusic mailing list
> > > mmusic@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mmusic

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



From mmusic-bounces@ietf.org Thu May 03 09:29:39 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjbNF-0002aH-E6; Thu, 03 May 2007 09:29:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjbNE-0002aC-63
	for mmusic@ietf.org; Thu, 03 May 2007 09:29:32 -0400
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjbNC-0001VW-Tr
	for mmusic@ietf.org; Thu, 03 May 2007 09:29:32 -0400
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l43DTR9u009703;
	Thu, 3 May 2007 07:29:27 -0600 (MDT)
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Thu, 3 May 2007 07:29:26 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 May 2007 07:29:25 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C607A8E1@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Status of draft-ietf-mmusic-sdpng-trans-04.txt
Thread-Index: AceNhxFE4l5uu4LhTyOlisy+BM8Vqg==
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <mmusic@ietf.org>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Colin Perkins <csp@csperkins.org>, Joerg Ott <jo@netlab.tkk.fi>
Subject: [MMUSIC] Status of draft-ietf-mmusic-sdpng-trans-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


   We briefly discussed the status of the
draft-ietf-mmusic-sdpng-trans-04.txt, an I-D in the RFC Editor queue
since 2003-06-17 currently in AUTH48 status.

   Based on a request from the authors of the above mentioned ID (Colin
and Joerg), and after considering the status of the work on SDPng, the
wg chairs intend to withdraw the I-D from publication.

If you have any comments or concerns, please let the chairs (and the
list) know by Wednesday May 9.

Thanks,
Jean-Francois.
<mmusic co-chair>


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



From mmusic-bounces@ietf.org Thu May 03 09:55:10 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hjbm1-00088m-8y; Thu, 03 May 2007 09:55:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hjblz-00088b-Ft
	for mmusic@ietf.org; Thu, 03 May 2007 09:55:07 -0400
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hjbly-0005b7-3r
	for mmusic@ietf.org; Thu, 03 May 2007 09:55:07 -0400
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l43Dt4WG017185;
	Thu, 3 May 2007 07:55:04 -0600 (MDT)
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Thu, 3 May 2007 07:55:03 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] Re: ICE micro-lite for support of IPv6 transition
Date: Thu, 3 May 2007 07:55:02 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C607A8E4@srvxchg3.cablelabs.com>
In-Reply-To: <46322667.6070602@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Re: ICE micro-lite for support of IPv6 transition
Thread-Index: AceI6ifarKjoP41ATNyjejIY3YguewEn3FuQ
References: <50B1CBA96870A34799A506B2313F26670B7D7828@ntht201e.siemenscomms.co.uk><461A3A35.8090200@cisco.com><1ECE0EB50388174790F9694F77522CCF0FF719F2@zrc2hxm0.corp.nortel.com><461B9001.9080402@cisco.com><1ECE0EB50388174790F9694F77522CCF0FFBBB88@zrc2hxm0.corp.nortel.com>
	<4630ACE9.6020607@cisco.com>
	<9AAEDF491EF7CA48AB587781B8F5D7C607A44E@srvxchg3.cablelabs.com>
	<46322667.6070602@cisco.com>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Errors-To: mmusic-bounces@ietf.org

Jonathan Rosenberg wrote:
> >
> >>3. be much simpler than ICE-full for dual-stack endpoints that are
> not
> >>natted
> >
> > After reading a few drafts and archives in the v6ops group (old and
> > current), there are known limitations of 3484 and many proposals on
> how
> > the address selection mechanism should be updated or improved to
> > ultimately guarantee connectivity. This goes beyond the NAT cases,
> and
> > it is sometimes applicable to multi-homed v6 nodes, etc.
> >
> > References:
> > http://tools.ietf.org/html/draft-ietf-v6ops-v6onbydefault-03
> > http://tools.ietf.org/html/draft-arifumi-v6ops-addr-select-ps-01
> > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-addr-select-
> req-01.
> > txt
> > http://www.ops.ietf.org/lists/v6ops/v6ops.2004/msg01072.html
> >
> > When I read your proposal trying to connect the dots between this
> thread
> > and the above v6ops references (looking at it as someone deciding
> what
> > to implement in a dual-stack host given the current state of the
> art),
> > it seems to me that with ICE, we have a mechanism to resolve those
> > potential 3484 issues by doing connectivity checks. Yet, we're about
> to
> > say, no, just do ICE-lite+ and no connectivity checks.
>=20
> No, I'm not saying that. I'm saying, if you think you can deal with
> the
> following limitations A,B, and C, then use ice-lite. Otherwise, use
> full, and full is always better.
>=20
> In the case of dual-stack, I don't follow v6ops, so if you could
> provide
> some text that I could include in ICE, summarizing limitations, giving
> some guidance for when to use full, that would be great.

I will start a thread on v6ops with some proposed txt "summarizing
limitations and giving some guidance for when to use full" and see where
we end up there before coming back at this.



> > At a minimum, there should be a strong statement made in the draft
> > that
> > dual-stack hosts using 3484 SHOULD consider full implementation of
                                ^^^^^^
> > ICE.
>=20
> I think that this is true in general, not just for dual stack. The
> introduction, section 2.7, says this:
>=20
> It is important to note that the lite implementation was added to
>     this specification to provide a stepping stone to full
>     implementation.  Even for devices that are always connected to the
>     public Internet, a full implementation is preferable if
achievable.
                                                ^^^^^^^^^^=20
>=20
> and later in the appendix:
>=20
>   It is important to note that the lite implementation was added to
>     this specification to provide a stepping stone to full
>     implementation.  Even for devices that are always connected to the
>     public Internet, a full implementation is preferable if
achievable.
                                                ^^^^^^^^^^ ^^ ^^^^^^^^^^
In both instances, I note the lack of requirements verb: at best, this
will be interpreted as a lower case may. I was thinking RECOMMENDED or
SHOULD.

Jean-Francois.

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



From mmusic-bounces@ietf.org Thu May 03 10:04:45 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HjbvI-0007Of-P2; Thu, 03 May 2007 10:04:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HjbvH-0007OX-SU
	for mmusic@ietf.org; Thu, 03 May 2007 10:04:43 -0400
Received: from prix.tandberg.no ([194.196.35.10])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HjbvF-0004SW-Vm
	for mmusic@ietf.org; Thu, 03 May 2007 10:04:43 -0400
Received: from 47mail.eu.tandberg.int (47mail.eu.tandberg.int [10.0.0.25])
	by prix.tandberg.no (8.12.11.20060308/8.12.10) with ESMTP id
	l43E4alM021062; Thu, 3 May 2007 16:04:36 +0200
Received: from oslexcp1.eu.tandberg.int ([10.47.136.29]) by
	47mail.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 3 May 2007 16:04:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Thu, 3 May 2007 16:04:34 +0200
Message-ID: <9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaAAD/BCkA==
From: "Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>
To: "Even, Roni" <roni.even@polycom.co.il>,
	"Desineni, Harikishan" <hdesinen@qualcomm.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 03 May 2007 14:04:36.0345 (UTC)
	FILETIME=[FB8A1690:01C78D8B]
X-Scanned-By: MIMEDefang 2.45
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c119f9923e40f08a1d7f390ce651ea92
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hari,

We are using it just as Roni explains. Receiver bandwidth indication has
been very useful for us, and it makes it possible to do quick
adjustments at the sender side without any renegotiation.

Cheers,
Geir Arne

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: 03 May 2007 08:03
> To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> Cc: Magnus Westerlund; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Hary,
> TIAS is being used as a media level attribute indicating the maximum
BW
> that the receiver would like to get. It is not used in offer answer.
The
> semantic of the attribute (what is bw) is as specified in RFC 3890
>=20
> Roni
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Monday, April 30, 2007 2:13 PM
> > To: Geir Arne Sandbakken; mmusic@ietf.org
> > Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Geir,
> >
> > Thanks for your feedback.
> >
> > Can you elaborate on how exactly this attribute is used in the
> > implementations known to you? I'd like to understand how closely or
> > differently it is used from the way it is documented in rfc3890.
> >
> > Thanks,
> > Hari
> >
> > > -----Original Message-----
> > > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > To: Desineni, Harikishan; mmusic@ietf.org
> > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Harikishan,
> > >
> > > We have been using TIAS in the 'recv' direction for quite a while,
> and
> > I
> > > know of multiple other implementations.  Think we have been
> promoting
> > > the usage in the last 3 SIPit's, and changing the direction will
> lead
> > to
> > > serious interoperability issues.
> > >
> > > I do agree that a 'send' direction attribute is desirable as
> > additional
> > > bandwidth information, and I hope it can be done without breaking
> > > existing implementations.
> > >
> > > Cheers,
> > > Geir Arne
> > >
> > > > -----Original Message-----
> > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > Sent: 17 April 2007 20:40
> > > > To: mmusic@ietf.org
> > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Some issues with the offer/answer usage of TIAS (defined in
> RFC3890)
> > > > came out while discussing
> > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > >
> > > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> > direction
> > > > attributes in offer/answer model. As 'recv' attributes, TIAS and
> > > > maxprate do not solve the bandwidth negotiation problem. For
> > > > offer/answer bw negotiation to work properly, the correct
> direction
> > in
> > > > rfc3890 should have been 'send', probably with the help of few
new
> > > > 'recv' direction attributes (like PO - per packet overhead at
> layer
> > X,
> > > > RB- receive BW at layer X) under discussion.
> > > >
> > > > A sender would choose (TIAS,maxprate) which satisfy the
following
> > > > formula
> > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by the
> > receiver)
> > > >
> > > > One approach to handle this is changing the direction of
> > > (TIAS,maxprate)
> > > > to 'send' and prevent the incorrect ('recv') usage of
> > (TIAS,maxprate)
> > > in
> > > > offer/answer model. While this appears to be the desired
> direction,
> > I
> > > am
> > > > interested to know the impact of such a change on (any) existing
> > > > implementations of TIAS in offer/answer.
> > > >
> > > > Please comment if you are aware of any existing implementations
of
> > > TIAS
> > > > in offer/answer and also describe how exactly TIAS was used in
> that
> > > > particular implementation.
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > > avt@ietf.org
> > > > > Subject: RE: [MMUSIC] Comments on
> > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > 02.txt
> > > > >
> > > > > I copied a post (from AVT list) from Roni which states that
TIAS
> > was
> > > > > actually used in his implementation. I am not sure if it is an
> > > > > implementation in offer/answer model.
> > > > >
> > > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > > >
> > > > > "
> > > > > -----Original Message-----
> > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > To: Randell Jesup
> > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
> include
> > > > > theheaderoverhead
> > > > >
> > > > > Randell,
> > > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > > compatibility
> > > > > with systems that do not support TIAS. This RFC gives a good
> > > > explanation
> > > > > why to use TIAS. This is what we do in our implementation.
> > > > > "
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Magnus Westerlund
> [mailto:magnus.westerlund@ericsson.com]
> > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > To: Desineni, Harikishan
> > > > > > Cc: mmusic@ietf.org
> > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > 02.txt
> > > > > >
> > > > > > Desineni, Harikishan skrev:
> > > > > > >
> > > > > > >
> > > > > > > Magnus,
> > > > > > >
> > > > > > > Thanks for the comments.
> > > > > > >
> > > > > > > In the initial version, I captured the current
understanding
> > of
> > > > > (TIAS
> > > > > > > ,maxprate) based on RFC3890.
> > > > > > >
> > > > > > > Based on the current RFCs, majority of the community
> > interprets
> > > > TIAS
> > > > > as
> > > > > > > receive only direction attribute. Instead of updating
> RFC3890
> > to
> > > > > modify
> > > > > > > TIAS as a send direction only attribute, it is better to
use
> a
> > > new
> > > > > > > attribute 'MSR' proposed in this draft. This would also
> avoid
> > > any
> > > > > > > backward compatibility/inter-op issues that can arise with
> > > current
> > > > > > > implementations which (correctly) interpret TIAS as
receive
> > > > > direction
> > > > > > > only attribute in offer/answer.
> > > > > >
> > > > > > Well, I wonder how there can be backwards compatibility
issues
> > > with
> > > > > > something that clearly doesn't work if you actually try to
use
> > it.
> > > > > There
> > > > > > might be implementations but I can't really understand how
> they
> > > > could
> > > > > > work. Do you know of implementations?
> > > > > >
> > > > > > >
> > > > > > > Another approach is to add directionality to TIAS. By
> default,
> > > > TIAS
> > > > > is
> > > > > > > receive only (not much useful) and "TIAS/sendonly" will be
> > send
> > > > only
> > > > > > > direction. "maxprate/send" will be packet rate in send
> > > direction.
> > > > > > >
> > > > > > > What you are proposing is the following
> > > > > > > Send direction attributes: RTP Payload rate and maxpacket
> rate
> > > > > > > Receive direction attributes: AS (or a new one), packet
> > overhead
> > > > > >
> > > > > > Okay, here I think the more important question is, are we
> > > expecting
> > > > to
> > > > > > be able to specify a value on another level than IP? If not
I
> > > think
> > > > AS
> > > > > > works fine.
> > > > > >
> > > > > > >
> > > > > > > In this draft I am proposing that 'MSR' be used for
> signaling
> > > RTP
> > > > > > > payload rate in 'send' direction. IMO, it is not a clean
> > > approach
> > > > to
> > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > >
> > > > > > We disagree on this. TIAS was specified as a send direction
> > > > attribute.
> > > > > I
> > > > > > made an error in the offer/answer usage because I didn't
> > consider
> > > > the
> > > > > > implications. And no one picked up on it.
> > > > > >
> > > > > > As I can see it in regards to RFC 3890 we have two
> alternatives:
> > > > > >
> > > > > > 1. Fix the offer/answer section to correctly define it to
> apply
> > in
> > > > the
> > > > > > sending direction.
> > > > > >
> > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and only
> use
> > > it
> > > > > for
> > > > > > declarative usage, like in RTSP.
> > > > > >
> > > > > > If there are implementations i any numbers that interpret
TIAS
> > as
> > > a
> > > > > > receiver direction attribute then I agree alternative 2 will
> be
> > > > best.
> > > > > > However I would like to have some positive acknowledgments
of
> > this
> > > > > > first. This was after all revealed in the attempt to apply
> TIAS
> > to
> > > > > > offer/answer in the 3GPP MTSI standardization work.
Resulting
> in
> > > > that
> > > > > > TIAS was only included in the draft spec for a while. I
don't
> > know
> > > > if
> > > > > > some other umbrella standard has included TIAS combined with
> > > > > offer/answer.
> > > > > >
> > > > > > >
> > > > > > > I am OK with signaling packet rate in send direction. But
we
> > > need
> > > > to
> > > > > > > consider whether to reuse maxprate for this or add
> > > directionality
> > > > to
> > > > > > > maxprate (maxprate/send) to avoid any inter-op issues with
> > > current
> > > > > > > implementations.
> > > > > > >
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > Magnus Westerlund
> > > > > >
> > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > magnus.westerlund@ericsson.com
> > > > > >
> > > >
> >
----------------------------------------------------------------------
> > > > >
> > > > > _______________________________________________
> > > > > mmusic mailing list
> > > > > mmusic@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > >
> > > > _______________________________________________
> > > > mmusic mailing list
> > > > mmusic@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mmusic

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



From mmusic-bounces@ietf.org Fri May 04 10:38:41 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hjyve-0001f8-6T; Fri, 04 May 2007 10:38:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hjyvc-0001f2-GA
	for mmusic@ietf.org; Fri, 04 May 2007 10:38:36 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjyvZ-0003Ze-PX
	for mmusic@ietf.org; Fri, 04 May 2007 10:38:36 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 04 May 2007 07:38:33 -0700
X-IronPort-AV: i="4.14,492,1170662400"; 
	d="scan'208"; a="144472480:sNHT58231485"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l44EcXb4020168; 
	Fri, 4 May 2007 07:38:33 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l44EcXZT016801;
	Fri, 4 May 2007 14:38:33 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 May 2007 07:38:32 -0700
Received: from [10.32.138.87] ([10.32.138.87]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 May 2007 07:38:32 -0700
Message-ID: <463B4568.2060902@cisco.com>
Date: Fri, 04 May 2007 10:38:32 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Francois Mule <jf.mule@cablelabs.com>
Subject: Re: [MMUSIC] Re: ICE micro-lite for support of IPv6 transition
References: <50B1CBA96870A34799A506B2313F26670B7D7828@ntht201e.siemenscomms.co.uk><461A3A35.8090200@cisco.com><1ECE0EB50388174790F9694F77522CCF0FF719F2@zrc2hxm0.corp.nortel.com><461B9001.9080402@cisco.com><1ECE0EB50388174790F9694F77522CCF0FFBBB88@zrc2hxm0.corp.nortel.com>
	<4630ACE9.6020607@cisco.com>
	<9AAEDF491EF7CA48AB587781B8F5D7C607A44E@srvxchg3.cablelabs.com>
	<46322667.6070602@cisco.com>
	<9AAEDF491EF7CA48AB587781B8F5D7C607A8E4@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C607A8E4@srvxchg3.cablelabs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 May 2007 14:38:32.0458 (UTC)
	FILETIME=[E39206A0:01C78E59]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3698; t=1178289513;
	x=1179153513; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20Re=3A=20ICE=20micro-lite=20for=20support=2
	0of=20IPv6=20transition |Sender:=20;
	bh=/wilirBIkZO/nxiecBf90A+NCmtOaZrItnSJuT5a/Ic=;
	b=RqD5HTXQvg6xvCs1m+CZQydjE3wpBaaPgXnkHFZo9ZBLJX02Yd1TnZwI0lWZDbWdVwFCa6NB
	+H2Vy/PAVFBBChZNLwxe3Vvzj7dET0Ps2tw/A7J2HtVF7NmZLjQxBRd1;
Authentication-Results: sj-dkim-3; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
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>
Errors-To: mmusic-bounces@ietf.org

inline.

Jean-Francois Mule wrote:

> Jonathan Rosenberg wrote:
> 
>>>>3. be much simpler than ICE-full for dual-stack endpoints that are
>>
>>not
>>
>>>>natted
>>>
>>>After reading a few drafts and archives in the v6ops group (old and
>>>current), there are known limitations of 3484 and many proposals on
>>
>>how
>>
>>>the address selection mechanism should be updated or improved to
>>>ultimately guarantee connectivity. This goes beyond the NAT cases,
>>
>>and
>>
>>>it is sometimes applicable to multi-homed v6 nodes, etc.
>>>
>>>References:
>>>http://tools.ietf.org/html/draft-ietf-v6ops-v6onbydefault-03
>>>http://tools.ietf.org/html/draft-arifumi-v6ops-addr-select-ps-01
>>>http://www.ietf.org/internet-drafts/draft-ietf-v6ops-addr-select-
>>
>>req-01.
>>
>>>txt
>>>http://www.ops.ietf.org/lists/v6ops/v6ops.2004/msg01072.html
>>>
>>>When I read your proposal trying to connect the dots between this
>>
>>thread
>>
>>>and the above v6ops references (looking at it as someone deciding
>>
>>what
>>
>>>to implement in a dual-stack host given the current state of the
>>
>>art),
>>
>>>it seems to me that with ICE, we have a mechanism to resolve those
>>>potential 3484 issues by doing connectivity checks. Yet, we're about
>>
>>to
>>
>>>say, no, just do ICE-lite+ and no connectivity checks.
>>
>>No, I'm not saying that. I'm saying, if you think you can deal with
>>the
>>following limitations A,B, and C, then use ice-lite. Otherwise, use
>>full, and full is always better.
>>
>>In the case of dual-stack, I don't follow v6ops, so if you could
>>provide
>>some text that I could include in ICE, summarizing limitations, giving
>>some guidance for when to use full, that would be great.
> 
> 
> I will start a thread on v6ops with some proposed txt "summarizing
> limitations and giving some guidance for when to use full" and see where
> we end up there before coming back at this.

OK. I'm planning on working on this next week, so if you can get some 
text then, that would be great.

> 
> 
> 
> 
>>>At a minimum, there should be a strong statement made in the draft
>>>that
>>>dual-stack hosts using 3484 SHOULD consider full implementation of
> 
>                                 ^^^^^^
> 
>>>ICE.
>>
>>I think that this is true in general, not just for dual stack. The
>>introduction, section 2.7, says this:
>>
>>It is important to note that the lite implementation was added to
>>    this specification to provide a stepping stone to full
>>    implementation.  Even for devices that are always connected to the
>>    public Internet, a full implementation is preferable if
> 
> achievable.
>                                                 ^^^^^^^^^^ 
> 
>>and later in the appendix:
>>
>>  It is important to note that the lite implementation was added to
>>    this specification to provide a stepping stone to full
>>    implementation.  Even for devices that are always connected to the
>>    public Internet, a full implementation is preferable if
> 
> achievable.
>                                                 ^^^^^^^^^^ ^^ ^^^^^^^^^^
> In both instances, I note the lack of requirements verb: at best, this
> will be interpreted as a lower case may. I was thinking RECOMMENDED or
> SHOULD.

OK, I am fine with SHOULD.

-Jonathan R.



-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   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 May 04 11:34:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hjznc-0006J3-Px; Fri, 04 May 2007 11:34:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hjznb-0006Iy-J4
	for mmusic@ietf.org; Fri, 04 May 2007 11:34:23 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hjzna-0002Qi-Pn
	for mmusic@ietf.org; Fri, 04 May 2007 11:34:23 -0400
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l44FYGoo013875
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 4 May 2007 08:34:17 -0700
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l44FYFtP004442;
	Fri, 4 May 2007 08:34:15 -0700 (PDT)
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 May 2007 08:34:14 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Fri, 4 May 2007 08:34:13 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD169B@NAEX01.na.qualcomm.com>
In-Reply-To: <9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
	[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaAAD/BCkAA2S8NQ
References: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com>
	<9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Geir Arne Sandbakken" <geir.sandbakken@tandberg.com>,
	"Even, Roni" <roni.even@polycom.co.il>, <mmusic@ietf.org>
X-OriginalArrivalTime: 04 May 2007 15:34:14.0904 (UTC)
	FILETIME=[ABD2CF80:01C78E61]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Colin Perkins <csp@csperkins.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Thanks for the responses.  I too think that the declarative usage of
TIAS as a receive bit-rate (RTP Payload) in offer/answer shall continue
to exist.

Thanks,
Hari

> -----Original Message-----
> From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> Sent: Thursday, May 03, 2007 7:05 AM
> To: Even, Roni; Desineni, Harikishan; mmusic@ietf.org
> Cc: Magnus Westerlund; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Hari,
>=20
> We are using it just as Roni explains. Receiver bandwidth indication
has
> been very useful for us, and it makes it possible to do quick
> adjustments at the sender side without any renegotiation.
>=20
> Cheers,
> Geir Arne
>=20
> > -----Original Message-----
> > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > Sent: 03 May 2007 08:03
> > To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> > Cc: Magnus Westerlund; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Hary,
> > TIAS is being used as a media level attribute indicating the maximum
> BW
> > that the receiver would like to get. It is not used in offer answer.
> The
> > semantic of the attribute (what is bw) is as specified in RFC 3890
> >
> > Roni
> >
> > > -----Original Message-----
> > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > Sent: Monday, April 30, 2007 2:13 PM
> > > To: Geir Arne Sandbakken; mmusic@ietf.org
> > > Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Geir,
> > >
> > > Thanks for your feedback.
> > >
> > > Can you elaborate on how exactly this attribute is used in the
> > > implementations known to you? I'd like to understand how closely
or
> > > differently it is used from the way it is documented in rfc3890.
> > >
> > > Thanks,
> > > Hari
> > >
> > > > -----Original Message-----
> > > > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > > To: Desineni, Harikishan; mmusic@ietf.org
> > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Harikishan,
> > > >
> > > > We have been using TIAS in the 'recv' direction for quite a
while,
> > and
> > > I
> > > > know of multiple other implementations.  Think we have been
> > promoting
> > > > the usage in the last 3 SIPit's, and changing the direction will
> > lead
> > > to
> > > > serious interoperability issues.
> > > >
> > > > I do agree that a 'send' direction attribute is desirable as
> > > additional
> > > > bandwidth information, and I hope it can be done without
breaking
> > > > existing implementations.
> > > >
> > > > Cheers,
> > > > Geir Arne
> > > >
> > > > > -----Original Message-----
> > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > Sent: 17 April 2007 20:40
> > > > > To: mmusic@ietf.org
> > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > > > [MMUSIC]Comments on
draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > >
> > > > > Some issues with the offer/answer usage of TIAS (defined in
> > RFC3890)
> > > > > came out while discussing
> > > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > > >
> > > > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> > > direction
> > > > > attributes in offer/answer model. As 'recv' attributes, TIAS
and
> > > > > maxprate do not solve the bandwidth negotiation problem. For
> > > > > offer/answer bw negotiation to work properly, the correct
> > direction
> > > in
> > > > > rfc3890 should have been 'send', probably with the help of few
> new
> > > > > 'recv' direction attributes (like PO - per packet overhead at
> > layer
> > > X,
> > > > > RB- receive BW at layer X) under discussion.
> > > > >
> > > > > A sender would choose (TIAS,maxprate) which satisfy the
> following
> > > > > formula
> > > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by the
> > > receiver)
> > > > >
> > > > > One approach to handle this is changing the direction of
> > > > (TIAS,maxprate)
> > > > > to 'send' and prevent the incorrect ('recv') usage of
> > > (TIAS,maxprate)
> > > > in
> > > > > offer/answer model. While this appears to be the desired
> > direction,
> > > I
> > > > am
> > > > > interested to know the impact of such a change on (any)
existing
> > > > > implementations of TIAS in offer/answer.
> > > > >
> > > > > Please comment if you are aware of any existing
implementations
> of
> > > > TIAS
> > > > > in offer/answer and also describe how exactly TIAS was used in
> > that
> > > > > particular implementation.
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > > > avt@ietf.org
> > > > > > Subject: RE: [MMUSIC] Comments on
> > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > 02.txt
> > > > > >
> > > > > > I copied a post (from AVT list) from Roni which states that
> TIAS
> > > was
> > > > > > actually used in his implementation. I am not sure if it is
an
> > > > > > implementation in offer/answer model.
> > > > > >
> > > > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > > > >
> > > > > > "
> > > > > > -----Original Message-----
> > > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > > To: Randell Jesup
> > > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
> > include
> > > > > > theheaderoverhead
> > > > > >
> > > > > > Randell,
> > > > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > > > compatibility
> > > > > > with systems that do not support TIAS. This RFC gives a good
> > > > > explanation
> > > > > > why to use TIAS. This is what we do in our implementation.
> > > > > > "
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Magnus Westerlund
> > [mailto:magnus.westerlund@ericsson.com]
> > > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > > To: Desineni, Harikishan
> > > > > > > Cc: mmusic@ietf.org
> > > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > 02.txt
> > > > > > >
> > > > > > > Desineni, Harikishan skrev:
> > > > > > > >
> > > > > > > >
> > > > > > > > Magnus,
> > > > > > > >
> > > > > > > > Thanks for the comments.
> > > > > > > >
> > > > > > > > In the initial version, I captured the current
> understanding
> > > of
> > > > > > (TIAS
> > > > > > > > ,maxprate) based on RFC3890.
> > > > > > > >
> > > > > > > > Based on the current RFCs, majority of the community
> > > interprets
> > > > > TIAS
> > > > > > as
> > > > > > > > receive only direction attribute. Instead of updating
> > RFC3890
> > > to
> > > > > > modify
> > > > > > > > TIAS as a send direction only attribute, it is better to
> use
> > a
> > > > new
> > > > > > > > attribute 'MSR' proposed in this draft. This would also
> > avoid
> > > > any
> > > > > > > > backward compatibility/inter-op issues that can arise
with
> > > > current
> > > > > > > > implementations which (correctly) interpret TIAS as
> receive
> > > > > > direction
> > > > > > > > only attribute in offer/answer.
> > > > > > >
> > > > > > > Well, I wonder how there can be backwards compatibility
> issues
> > > > with
> > > > > > > something that clearly doesn't work if you actually try to
> use
> > > it.
> > > > > > There
> > > > > > > might be implementations but I can't really understand how
> > they
> > > > > could
> > > > > > > work. Do you know of implementations?
> > > > > > >
> > > > > > > >
> > > > > > > > Another approach is to add directionality to TIAS. By
> > default,
> > > > > TIAS
> > > > > > is
> > > > > > > > receive only (not much useful) and "TIAS/sendonly" will
be
> > > send
> > > > > only
> > > > > > > > direction. "maxprate/send" will be packet rate in send
> > > > direction.
> > > > > > > >
> > > > > > > > What you are proposing is the following
> > > > > > > > Send direction attributes: RTP Payload rate and
maxpacket
> > rate
> > > > > > > > Receive direction attributes: AS (or a new one), packet
> > > overhead
> > > > > > >
> > > > > > > Okay, here I think the more important question is, are we
> > > > expecting
> > > > > to
> > > > > > > be able to specify a value on another level than IP? If
not
> I
> > > > think
> > > > > AS
> > > > > > > works fine.
> > > > > > >
> > > > > > > >
> > > > > > > > In this draft I am proposing that 'MSR' be used for
> > signaling
> > > > RTP
> > > > > > > > payload rate in 'send' direction. IMO, it is not a clean
> > > > approach
> > > > > to
> > > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > > >
> > > > > > > We disagree on this. TIAS was specified as a send
direction
> > > > > attribute.
> > > > > > I
> > > > > > > made an error in the offer/answer usage because I didn't
> > > consider
> > > > > the
> > > > > > > implications. And no one picked up on it.
> > > > > > >
> > > > > > > As I can see it in regards to RFC 3890 we have two
> > alternatives:
> > > > > > >
> > > > > > > 1. Fix the offer/answer section to correctly define it to
> > apply
> > > in
> > > > > the
> > > > > > > sending direction.
> > > > > > >
> > > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and
only
> > use
> > > > it
> > > > > > for
> > > > > > > declarative usage, like in RTSP.
> > > > > > >
> > > > > > > If there are implementations i any numbers that interpret
> TIAS
> > > as
> > > > a
> > > > > > > receiver direction attribute then I agree alternative 2
will
> > be
> > > > > best.
> > > > > > > However I would like to have some positive acknowledgments
> of
> > > this
> > > > > > > first. This was after all revealed in the attempt to apply
> > TIAS
> > > to
> > > > > > > offer/answer in the 3GPP MTSI standardization work.
> Resulting
> > in
> > > > > that
> > > > > > > TIAS was only included in the draft spec for a while. I
> don't
> > > know
> > > > > if
> > > > > > > some other umbrella standard has included TIAS combined
with
> > > > > > offer/answer.
> > > > > > >
> > > > > > > >
> > > > > > > > I am OK with signaling packet rate in send direction.
But
> we
> > > > need
> > > > > to
> > > > > > > > consider whether to reuse maxprate for this or add
> > > > directionality
> > > > > to
> > > > > > > > maxprate (maxprate/send) to avoid any inter-op issues
with
> > > > current
> > > > > > > > implementations.
> > > > > > > >
> > > > > > >
> > > > > > > Cheers
> > > > > > >
> > > > > > > Magnus Westerlund
> > > > > > >
> > > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > > >
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > > >
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > > magnus.westerlund@ericsson.com
> > > > > > >
> > > > >
> > >
> ----------------------------------------------------------------------
> > > > > >
> > > > > > _______________________________________________
> > > > > > mmusic mailing list
> > > > > > mmusic@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > > >
> > > > > _______________________________________________
> > > > > mmusic mailing list
> > > > > mmusic@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mmusic

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



From mmusic-bounces@ietf.org Mon May 07 10:14:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hl3yy-0002Nj-Vs; Mon, 07 May 2007 10:14:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hl3yy-0002Ne-1V
	for mmusic@ietf.org; Mon, 07 May 2007 10:14:32 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hl3yw-0006qv-8v
	for mmusic@ietf.org; Mon, 07 May 2007 10:14:32 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AA7CD206B8; Mon,  7 May 2007 16:14:27 +0200 (CEST)
X-AuditID: c1b4fb3c-a9cedbb0000073d5-4d-463f3443eef2 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	91EBD2066D; Mon,  7 May 2007 16:14:27 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 16:14:27 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 16:14:27 +0200
Message-ID: <463F3443.4040805@ericsson.com>
Date: Mon, 07 May 2007 16:14:27 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: ICE pacing connectivity
	checks	(wasRE:[MMUSIC]	WGLC:	draft-ietf-mmusic-ice-15.txt)
References: <05c501c78c43$a0de01f0$c4f0200a@amer.cisco.com>
In-Reply-To: <05c501c78c43$a0de01f0$c4f0200a@amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 May 2007 14:14:27.0225 (UTC)
	FILETIME=[05623890:01C790B2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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>
Errors-To: mmusic-bounces@ietf.org

Dan Wing skrev:
>>> The easiest and most effective way to do that is constrain each 
>>> of the ICE checks to the bandwidth of their respective m= lines, 
>>> rather than the sum of RTP bandwidth available to all of the
>>> m= lines.
>> Okay, I think there need to go into some thought into if the 
>> connectivity checks are happening from individual bit-rate 
>> budgets or if there are a common one. There are some issues 
>> with getting completion if some media streams are very low 
>> bit-rate compared to other large bandwidth.
> 
> We have to make some guesses, then.  The most important 
> guess is if the network polices our flows by the sum of
> those media lines or (as with, for example, a PacketCable
> network) the network would police the flows by each m= 
> line.
> 
> If the network is bandwidth constrained (dialup, DSL, etc.),
> the limit is overall bandwidth.  If there is a bandwidth
> policer in place doing Smart Things (tm), it may well be
> smart enough to help us (give us the sum of both media
> lines' bandwidth) or smart enough to be difficult (give 
> us the bandwidth indicated in each of the media lines).

In most cases there will be a common pool of resources. However there 
clearly are examples where the resources are allocated per media stream. 
Thus a paragraph on how to handle these cases should be included.


> 
>>>> I would really appreciate some simulation data for
>>>> cases that are a bit more extreme when it comes to the number of
>>>> candidates and medias.
>>> That excel spreadsheet currently handles 10 candidates; how many
>>> more do you want simulated?
>> What is needed is to understand how it behaves from small 
>> cases with a few candidates all the way up to the upper 
>> limit that ICE allows.  Which means at least 100 candidates 
>> needs to be looked at.
> 
> With my current estimate of 108 bytes of UDP payload for a STUN
> packet, and 40 bytes of UDP payload every 20ms for RTP (which
> is similar to G.726), it would take a bit over 3 seconds for
> the initial STUN checks to be sent out.
> 
> If we need 100 candidates to work, we would need a more 
> aggressive algorithm than what I had previously suggested, 
> which would exceed the already-undesirable bandwidth
> consumption of RTP.
> 
> A new excel spreadsheet that handles 0-100 candidates is
> at http://www.employees.org/~dwing/ice-rtp-backoff.xls
> 

My point with making 100 candidates work, is not that it completes 
quickly but that it does work. If you have to go through a 100 
candidates to find something that works, then you have prioritized 
wrongly or are extremely unlucky. But nothing breaks because the checks 
take 3 seconds to pace out? I think that is the import fact.

What I see as reasonable here is:

1) ICE consumes a reasonable and bounded amount of network resources per 
second when it is running checks.
2) ICE has a reasonable good completion time for a reasonable number of 
candidates
3) ICE still work but may take longer time as the number of candidates 
increase.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From mmusic-bounces@ietf.org Mon May 07 10:24:28 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hl48a-0008V5-0r; Mon, 07 May 2007 10:24:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hl48Y-0008Uw-CD
	for mmusic@ietf.org; Mon, 07 May 2007 10:24:26 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hl48X-0007so-Fo
	for mmusic@ietf.org; Mon, 07 May 2007 10:24:26 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C3372200D1; Mon,  7 May 2007 16:24:24 +0200 (CEST)
X-AuditID: c1b4fb3e-ae1ebbb0000061ca-88-463f3698f00c 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A30A0210FC; Mon,  7 May 2007 16:24:24 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 16:24:24 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 May 2007 16:24:24 +0200
Message-ID: <463F3698.1070606@ericsson.com>
Date: Mon, 07 May 2007 16:24:24 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Joseph Pallas <pallas@cs.stanford.edu>
Subject: Re: [MMUSIC] RTSP: Speed header
References: <4d0605c20704241137g3a2af1bfq389b317d551b17da@mail.gmail.com>	<9AAEDF491EF7CA48AB587781B8F5D7C607A42D@srvxchg3.cablelabs.com>
	<4d0605c20704271346nf4c3875ycbdcbb284322c2c1@mail.gmail.com>
In-Reply-To: <4d0605c20704271346nf4c3875ycbdcbb284322c2c1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 May 2007 14:24:24.0158 (UTC)
	FILETIME=[692EF7E0:01C790B3]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Joseph Pallas skrev:
> On 4/26/07, Jean-Francois Mule <jf.mule@cablelabs.com> wrote:
>> Some of this was discussed back then when the 2.0 draft was started. It
>> would be nice to get some specific details based on the current 2.0
>> drafts, especially the "things [in the current 2.0 draft] that no one
>> uses", and what results in "poor [1.0] interoperability".
> 
> I think the 2.0 draft is much better than 1.0 in these respects; I
> won't bother to enumerate problems with 1.0.  For 2.0, we've already
> identified the Speed header as one issue.  I think the lingering
> references to connection-less transports are unnecessary, although
> probably harmless.

We are discussing on how to clean up the 2.0 spec, and I think that one 
thing that will consider is how to write the transport parts. I know of 
only a single UDP based RTSP transport which has had very limited 
deployment as it was a top-set box of some kind. In my opinion we can 
completely remove the consideration of running RTSP 2.0 over 
non-reliable transport.

   There is no means to negotiate a content type for
> GET_PARAMETER and SET_PARAMETER, so their interoperability remain
> dubious.  (And I've already complained that there is no specification
> for "text/parameters" despite its usage both in the field and in the
> examples.)

Yes, I agree with that this isn't complete. Are you willing to write an 
definition of text/parameters?

> 
> I do not know whether any implementations are using the cache-related
> features.  I'd be interested to hear what use is being made of them.
> I think it would be quite challenging to implement a caching proxy
> that supports independently-developed clients.

I would also like to hear confirmation on that they implement this. I 
know Real has some proxy and it would be interesting to hear more about 
if it handles the caching features. But, these are cleaned up and I 
don't think it is that complicated to build a caching proxy. But there 
are a lot of streams out there that can't be cached because they are 
dynamically created for different users.

> 
> Having stated my concern about unused features, I would add this.  I
> think it is telling that the ANNOUNCE method from RTSP 1.0 may have
> never been used as specified (for unsolicited session descriptions)
> but was "repurposed" by some implementations to provide a way to
> signal various asynchronous stream events.  I agree with the decision
> to remove RTSP 1.0's ANNOUNCE from RTSP 2.0, but I'm concerned that
> failing to include that notification functionality in RTSP 2.0 simply
> means that incompatible extensions will be created. (I would be
> especially sad to see ANNOUNCE-as-it-is-used re-introduced as an RTSP
> 2.0 extension.)
> 

Do I understand you correctly that you rather see the asynchronous event 
signalling, like end of stream, to be in the base spec rather than as a 
extension specification. There was
http://tools.ietf.org/id/draft-ietf-mmusic-rtsp-announce-01.txt

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 May 08 18:47:37 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HlYT2-0006ac-4Y; Tue, 08 May 2007 18:47:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HlYT0-0006aX-BV
	for mmusic@ietf.org; Tue, 08 May 2007 18:47:34 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlYSz-0000dK-0k
	for mmusic@ietf.org; Tue, 08 May 2007 18:47:34 -0400
Received: by ug-out-1314.google.com with SMTP id 72so172073ugd
	for <mmusic@ietf.org>; Tue, 08 May 2007 15:47:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=dobErKMeYsRMuzIn7CtWT1RWWa23c6oz1JsTHlcKlGYYDlp+3scrmuAz5mSdwqVL6VHUTpqJJSWrUxe+HzNF0NDvfLCQw1TTzVw0/rj+n+lTvk7PC9DVFCfa8JiUhCbM3EH3CjAGc5g4CJzofMd362rGPIIVQn7bCvGHME0/VQk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=RKpLH3Akl1ERw1VLa94RfNJTDFr6U1F6QuTfT+DiimKG+HpYXlczY36/ASw3IrmKHt+5xJnY11uylPxsiUaq+4fhOEegRvAvYMnWJ11MqGRf32nzxUvpNtqbQQUa4bL52HPTEfgAKGNrOCis/IVJ20JBfKDUxx1sh2rWrDzzwhM=
Received: by 10.78.124.9 with SMTP id w9mr673571huc.1178664451948;
	Tue, 08 May 2007 15:47:31 -0700 (PDT)
Received: by 10.78.202.3 with HTTP; Tue, 8 May 2007 15:47:31 -0700 (PDT)
Message-ID: <4d0605c20705081547m6f1f69b0yfeb3031e88b870b1@mail.gmail.com>
Date: Tue, 8 May 2007 15:47:31 -0700
From: "Joseph Pallas" <pallas@cs.stanford.edu>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] RTSP: Speed header
In-Reply-To: <463F3698.1070606@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4d0605c20704241137g3a2af1bfq389b317d551b17da@mail.gmail.com>
	<9AAEDF491EF7CA48AB587781B8F5D7C607A42D@srvxchg3.cablelabs.com>
	<4d0605c20704271346nf4c3875ycbdcbb284322c2c1@mail.gmail.com>
	<463F3698.1070606@ericsson.com>
X-Google-Sender-Auth: 57b0c09ce75bb975
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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>
Errors-To: mmusic-bounces@ietf.org

On 5/7/07, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>    There is no means to negotiate a content type for
> > GET_PARAMETER and SET_PARAMETER, so their interoperability remain
> > dubious.  (And I've already complained that there is no specification
> > for "text/parameters" despite its usage both in the field and in the
> > examples.)
>
> Yes, I agree with that this isn't complete. Are you willing to write an
> definition of text/parameters?

Yuck.  I don't even like it.  But here's a stab:

A resource of type "text/parameters" consists of either
1) a list of parameters (for a query) or
2) a list of parameters and associated values (for an update).
Each entry of the list is a single line of text.  Parameters are
separated from values by a colon.

The ABNF [RFC2234] grammar for "text/parameters" content is:

(Note: this uses the "Core Rules" from RFC2234)

file = parameter-list / parameter-value-list
parameter-list = *(parameter CRLF)
parameter-value-list = *(parameter-value CRLF)
parameter-value = parameter WSP ":" value
parameter = 1*visible-except-colon
visible-except-colon = %x21-39 / %x3B-7E	; VCHAR - ":"
value = *VCHAR

> Do I understand you correctly that you rather see the asynchronous event
> signalling, like end of stream, to be in the base spec rather than as a
> extension specification. There was
> http://tools.ietf.org/id/draft-ietf-mmusic-rtsp-announce-01.txt

I would, in fact, prefer to see async stream event signalling in the
base spec. I think it is broadly useful.  But the ANNOUNCE draft
combines stream events with session announcements, and I don't see
async session announcements as being desirable in the base spec (does
anyone use them?), nor do I think the same method should be used for
both.

And I would rather see a finished, clean, extensible spec than my
preferred feature(s).  I do worry that extensions will be less
rigorously scrutinized because they are optional.

joe

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



From mmusic-bounces@ietf.org Wed May 09 08:07:36 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HlkxC-0007Uo-DJ; Wed, 09 May 2007 08:07:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HlkxB-0007Ui-J0
	for mmusic@ietf.org; Wed, 09 May 2007 08:07:33 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlkxA-0000G8-M5
	for mmusic@ietf.org; Wed, 09 May 2007 08:07:33 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F016220A74; Wed,  9 May 2007 14:07:31 +0200 (CEST)
X-AuditID: c1b4fb3c-a94ecbb0000073d5-7e-4641b983c5d6 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D190420A42; Wed,  9 May 2007 14:07:31 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 May 2007 14:07:31 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 May 2007 14:07:31 +0200
Message-ID: <4641B982.1020604@ericsson.com>
Date: Wed, 09 May 2007 14:07:30 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Joseph Pallas <pallas@cs.stanford.edu>
Subject: Re: [MMUSIC] RTSP: Speed header
References: <4d0605c20704241137g3a2af1bfq389b317d551b17da@mail.gmail.com>	
	<9AAEDF491EF7CA48AB587781B8F5D7C607A42D@srvxchg3.cablelabs.com>	
	<4d0605c20704271346nf4c3875ycbdcbb284322c2c1@mail.gmail.com>	
	<463F3698.1070606@ericsson.com>
	<4d0605c20705081547m6f1f69b0yfeb3031e88b870b1@mail.gmail.com>
In-Reply-To: <4d0605c20705081547m6f1f69b0yfeb3031e88b870b1@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 May 2007 12:07:31.0543 (UTC)
	FILETIME=[9EE8DE70:01C79232]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
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>
Errors-To: mmusic-bounces@ietf.org

Joseph Pallas skrev:
> On 5/7/07, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>>    There is no means to negotiate a content type for
>> > GET_PARAMETER and SET_PARAMETER, so their interoperability remain
>> > dubious.  (And I've already complained that there is no specification
>> > for "text/parameters" despite its usage both in the field and in the
>> > examples.)

I didn't respond to the question about content type negotiation. I have 
logged a bug for this so we don't forget it. However shouldn't it be 
possible to specify it so that the Accept header can be used with 
GET_PARAMETER. To me it also seems that feature tags can be used to 
express a set of capabilities that include parameter format and the 
usage of SET or GET Parameter.

However to my understanding the usage for these method has usually to do 
with particular application usages. For example 3GPP uses them for 
reporting quality of experience measurement. In these cases you have 
another specification that defines what type shall be used in the 
method. Thus it is interoperable within certain context.

>>
>> Yes, I agree with that this isn't complete. Are you willing to write an
>> definition of text/parameters?
> 
> Yuck.  I don't even like it.  But here's a stab:
> 
> A resource of type "text/parameters" consists of either
> 1) a list of parameters (for a query) or
> 2) a list of parameters and associated values (for an update).
> Each entry of the list is a single line of text.  Parameters are
> separated from values by a colon.
> 
> The ABNF [RFC2234] grammar for "text/parameters" content is:
> 
> (Note: this uses the "Core Rules" from RFC2234)
> 
> file = parameter-list / parameter-value-list
> parameter-list = *(parameter CRLF)
> parameter-value-list = *(parameter-value CRLF)
> parameter-value = parameter WSP ":" value
> parameter = 1*visible-except-colon
> visible-except-colon = %x21-39 / %x3B-7E    ; VCHAR - ":"
> value = *VCHAR

Thanks, it is at least a start. There is also need for a media type. I 
updated the bug I had from EKR's review to include your comments also.

> 
>> Do I understand you correctly that you rather see the asynchronous event
>> signalling, like end of stream, to be in the base spec rather than as a
>> extension specification. There was
>> http://tools.ietf.org/id/draft-ietf-mmusic-rtsp-announce-01.txt
> 
> I would, in fact, prefer to see async stream event signalling in the
> base spec. I think it is broadly useful.  But the ANNOUNCE draft
> combines stream events with session announcements, and I don't see
> async session announcements as being desirable in the base spec (does
> anyone use them?), nor do I think the same method should be used for
> both.

Okay, that seems like a very valid comment. I know that a common feature 
request is the inclusion of End of stream signalling. While the need for 
session announcements hasn't been as widely needed. But there has been 
expressed interest also in that.

> 
> And I would rather see a finished, clean, extensible spec than my
> preferred feature(s).  I do worry that extensions will be less
> rigorously scrutinized because they are optional.

I agree about finishing things up. That is why any new feature will need 
to have proponents that are willing to contribute with text that 
basically can be cut and past into the spec for their feature. Otherwise 
we are very likely to leave things out. Unless we deem them critical to 
make things work. For example END_OF_STREAM is nice to have but not 
necessary.

I am not certain that extensions would receive less scrutiny then things 
added to the base spec.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
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 May 09 12:51:19 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HlpNm-0001wK-1r; Wed, 09 May 2007 12:51:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HlpNl-0001tS-0F
	for mmusic@ietf.org; Wed, 09 May 2007 12:51:17 -0400
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlpNk-0003Zq-B0
	for mmusic@ietf.org; Wed, 09 May 2007 12:51:16 -0400
Received: from kyzyl.cablelabs.com (kyzyl.cablelabs.com [10.253.0.7])
	by ondar.cablelabs.com (8.13.8/8.13.8) with ESMTP id l49Gp6IM016987;
	Wed, 9 May 2007 10:51:15 -0600 (MDT)
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com);
	Wed, 9 May 2007 10:51:06 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/488/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Wed, 9 May 2007 10:37:52 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C60D92FF@srvxchg3.cablelabs.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD169B@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on
	draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaAAD/BCkAA2S8NQAP1E2pA=
References: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com><9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int>
	<2CA3E1B6CEC064449CAA7D0FAB46079B02CD169B@NAEX01.na.qualcomm.com>
From: "Jean-Francois Mule" <jf.mule@CableLabs.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22e211536bda974b2dcf811522dc525d
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>
Errors-To: mmusic-bounces@ietf.org

Hari,

   It seems there are some issues as pointed out by your
draft-hdesinen-mmusic-oa-send-bw-attr-02, and the requirements in RFC
3890 & 3264.

Based on the txt on the b param in 3264,=20
    |  "If the bandwidth attribute is present for a stream,=20
    |   it indicates the desired bandwidth that the offerer
    |   would like to receive."
and the notes from folks who have implemented it and responded to the
list, I too agree that it is best to keep the current usage (TIAS as
declarative of what the agent is willing to receive).

An update to 3890 with a new TIAS value and clarifications about the
current ones seem appropriate.=20

Does anyone disagree on this path forward?

Jean-Francois.

> -----Original Message-----
> From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> Sent: Friday, May 04, 2007 9:34 AM
> To: Geir Arne Sandbakken; Even, Roni; mmusic@ietf.org
> Cc: Magnus Westerlund; Colin Perkins
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Thanks for the responses.  I too think that the declarative usage of
> TIAS as a receive bit-rate (RTP Payload) in offer/answer shall
> continue
> to exist.
>=20
> Thanks,
> Hari
>=20
> > -----Original Message-----
> > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > Sent: Thursday, May 03, 2007 7:05 AM
> > To: Even, Roni; Desineni, Harikishan; mmusic@ietf.org
> > Cc: Magnus Westerlund; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was RE:
> > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Hari,
> >
> > We are using it just as Roni explains. Receiver bandwidth indication
> has
> > been very useful for us, and it makes it possible to do quick
> > adjustments at the sender side without any renegotiation.
> >
> > Cheers,
> > Geir Arne
> >
> > > -----Original Message-----
> > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > Sent: 03 May 2007 08:03
> > > To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> > > Cc: Magnus Westerlund; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Hary,
> > > TIAS is being used as a media level attribute indicating the
> maximum
> > BW
> > > that the receiver would like to get. It is not used in offer
> answer.
> > The
> > > semantic of the attribute (what is bw) is as specified in RFC 3890
> > >
> > > Roni
> > >
> > > > -----Original Message-----
> > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > Sent: Monday, April 30, 2007 2:13 PM
> > > > To: Geir Arne Sandbakken; mmusic@ietf.org
> > > > Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Geir,
> > > >
> > > > Thanks for your feedback.
> > > >
> > > > Can you elaborate on how exactly this attribute is used in the
> > > > implementations known to you? I'd like to understand how closely
> or
> > > > differently it is used from the way it is documented in rfc3890.
> > > >
> > > > Thanks,
> > > > Hari
> > > >
> > > > > -----Original Message-----
> > > > > From: Geir Arne Sandbakken
> [mailto:geir.sandbakken@tandberg.com]
> > > > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > > > To: Desineni, Harikishan; mmusic@ietf.org
> > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin Perkins
> > > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
> Was
> > RE:
> > > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-
> 02.txt
> > > > >
> > > > > Harikishan,
> > > > >
> > > > > We have been using TIAS in the 'recv' direction for quite a
> while,
> > > and
> > > > I
> > > > > know of multiple other implementations.  Think we have been
> > > promoting
> > > > > the usage in the last 3 SIPit's, and changing the direction
> will
> > > lead
> > > > to
> > > > > serious interoperability issues.
> > > > >
> > > > > I do agree that a 'send' direction attribute is desirable as
> > > > additional
> > > > > bandwidth information, and I hope it can be done without
> breaking
> > > > > existing implementations.
> > > > >
> > > > > Cheers,
> > > > > Geir Arne
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > > Sent: 17 April 2007 20:40
> > > > > > To: mmusic@ietf.org
> > > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin
> Perkins
> > > > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:
> > > > > > [MMUSIC]Comments on
> draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > > >
> > > > > > Some issues with the offer/answer usage of TIAS (defined in
> > > RFC3890)
> > > > > > came out while discussing
> > > > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > > > >
> > > > > > RFC3890 has incorrectly defined TIAS and maxprate as 'recv'
> > > > direction
> > > > > > attributes in offer/answer model. As 'recv' attributes, TIAS
> and
> > > > > > maxprate do not solve the bandwidth negotiation problem. For
> > > > > > offer/answer bw negotiation to work properly, the correct
> > > direction
> > > > in
> > > > > > rfc3890 should have been 'send', probably with the help of
> few
> > new
> > > > > > 'recv' direction attributes (like PO - per packet overhead
> at
> > > layer
> > > > X,
> > > > > > RB- receive BW at layer X) under discussion.
> > > > > >
> > > > > > A sender would choose (TIAS,maxprate) which satisfy the
> > following
> > > > > > formula
> > > > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by =
the
> > > > receiver)
> > > > > >
> > > > > > One approach to handle this is changing the direction of
> > > > > (TIAS,maxprate)
> > > > > > to 'send' and prevent the incorrect ('recv') usage of
> > > > (TIAS,maxprate)
> > > > > in
> > > > > > offer/answer model. While this appears to be the desired
> > > direction,
> > > > I
> > > > > am
> > > > > > interested to know the impact of such a change on (any)
> existing
> > > > > > implementations of TIAS in offer/answer.
> > > > > >
> > > > > > Please comment if you are aware of any existing
> implementations
> > of
> > > > > TIAS
> > > > > > in offer/answer and also describe how exactly TIAS was used
> in
> > > that
> > > > > > particular implementation.
> > > > > >
> > > > > > Thanks,
> > > > > > Hari
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > > > Cc: Mahendran, AC; Dondeti, Lakshminath; mmusic@ietf.org;
> > > > > avt@ietf.org
> > > > > > > Subject: RE: [MMUSIC] Comments on
> > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > 02.txt
> > > > > > >
> > > > > > > I copied a post (from AVT list) from Roni which states
> that
> > TIAS
> > > > was
> > > > > > > actually used in his implementation. I am not sure if it
> is
> an
> > > > > > > implementation in offer/answer model.
> > > > > > >
> > > > > > > [CCed AVT as TIAS was also recently discussed on AVT list]
> > > > > > >
> > > > > > > "
> > > > > > > -----Original Message-----
> > > > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > > > To: Randell Jesup
> > > > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > > > Subject: RE: [AVT] CCM draft review -- should "bandwidth"
> > > include
> > > > > > > theheaderoverhead
> > > > > > >
> > > > > > > Randell,
> > > > > > > RFC 4890 recommends sending both TIAS and AS for backward
> > > > > > compatibility
> > > > > > > with systems that do not support TIAS. This RFC gives a
> good
> > > > > > explanation
> > > > > > > why to use TIAS. This is what we do in our implementation.
> > > > > > > "
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Magnus Westerlund
> > > [mailto:magnus.westerlund@ericsson.com]
> > > > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > > > To: Desineni, Harikishan
> > > > > > > > Cc: mmusic@ietf.org
> > > > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > > 02.txt
> > > > > > > >
> > > > > > > > Desineni, Harikishan skrev:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Magnus,
> > > > > > > > >
> > > > > > > > > Thanks for the comments.
> > > > > > > > >
> > > > > > > > > In the initial version, I captured the current
> > understanding
> > > > of
> > > > > > > (TIAS
> > > > > > > > > ,maxprate) based on RFC3890.
> > > > > > > > >
> > > > > > > > > Based on the current RFCs, majority of the community
> > > > interprets
> > > > > > TIAS
> > > > > > > as
> > > > > > > > > receive only direction attribute. Instead of updating
> > > RFC3890
> > > > to
> > > > > > > modify
> > > > > > > > > TIAS as a send direction only attribute, it is better
> to
> > use
> > > a
> > > > > new
> > > > > > > > > attribute 'MSR' proposed in this draft. This would
> also
> > > avoid
> > > > > any
> > > > > > > > > backward compatibility/inter-op issues that can arise
> with
> > > > > current
> > > > > > > > > implementations which (correctly) interpret TIAS as
> > receive
> > > > > > > direction
> > > > > > > > > only attribute in offer/answer.
> > > > > > > >
> > > > > > > > Well, I wonder how there can be backwards compatibility
> > issues
> > > > > with
> > > > > > > > something that clearly doesn't work if you actually try
> to
> > use
> > > > it.
> > > > > > > There
> > > > > > > > might be implementations but I can't really understand
> how
> > > they
> > > > > > could
> > > > > > > > work. Do you know of implementations?
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Another approach is to add directionality to TIAS. By
> > > default,
> > > > > > TIAS
> > > > > > > is
> > > > > > > > > receive only (not much useful) and "TIAS/sendonly"
> will
> be
> > > > send
> > > > > > only
> > > > > > > > > direction. "maxprate/send" will be packet rate in send
> > > > > direction.
> > > > > > > > >
> > > > > > > > > What you are proposing is the following
> > > > > > > > > Send direction attributes: RTP Payload rate and
> maxpacket
> > > rate
> > > > > > > > > Receive direction attributes: AS (or a new one),
> packet
> > > > overhead
> > > > > > > >
> > > > > > > > Okay, here I think the more important question is, are
> we
> > > > > expecting
> > > > > > to
> > > > > > > > be able to specify a value on another level than IP? If
> not
> > I
> > > > > think
> > > > > > AS
> > > > > > > > works fine.
> > > > > > > >
> > > > > > > > >
> > > > > > > > > In this draft I am proposing that 'MSR' be used for
> > > signaling
> > > > > RTP
> > > > > > > > > payload rate in 'send' direction. IMO, it is not a
> clean
> > > > > approach
> > > > > > to
> > > > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > > > >
> > > > > > > > We disagree on this. TIAS was specified as a send
> direction
> > > > > > attribute.
> > > > > > > I
> > > > > > > > made an error in the offer/answer usage because I didn't
> > > > consider
> > > > > > the
> > > > > > > > implications. And no one picked up on it.
> > > > > > > >
> > > > > > > > As I can see it in regards to RFC 3890 we have two
> > > alternatives:
> > > > > > > >
> > > > > > > > 1. Fix the offer/answer section to correctly define it
> to
> > > apply
> > > > in
> > > > > > the
> > > > > > > > sending direction.
> > > > > > > >
> > > > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges and
> only
> > > use
> > > > > it
> > > > > > > for
> > > > > > > > declarative usage, like in RTSP.
> > > > > > > >
> > > > > > > > If there are implementations i any numbers that
> interpret
> > TIAS
> > > > as
> > > > > a
> > > > > > > > receiver direction attribute then I agree alternative 2
> will
> > > be
> > > > > > best.
> > > > > > > > However I would like to have some positive
> acknowledgments
> > of
> > > > this
> > > > > > > > first. This was after all revealed in the attempt to
> apply
> > > TIAS
> > > > to
> > > > > > > > offer/answer in the 3GPP MTSI standardization work.
> > Resulting
> > > in
> > > > > > that
> > > > > > > > TIAS was only included in the draft spec for a while. I
> > don't
> > > > know
> > > > > > if
> > > > > > > > some other umbrella standard has included TIAS combined
> with
> > > > > > > offer/answer.
> > > > > > > >
> > > > > > > > >
> > > > > > > > > I am OK with signaling packet rate in send direction.
> But
> > we
> > > > > need
> > > > > > to
> > > > > > > > > consider whether to reuse maxprate for this or add
> > > > > directionality
> > > > > > to
> > > > > > > > > maxprate (maxprate/send) to avoid any inter-op issues
> with
> > > > > current
> > > > > > > > > implementations.
> > > > > > > > >
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > >
> > > > > > > > Magnus Westerlund
> > > > > > > >
> > > > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > > > >
> > > > > >
> > > >
> > --------------------------------------------------------------------
> --
> > > > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > > > >
> > > > > >
> > > >
> > --------------------------------------------------------------------
> --
> > > > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > > > magnus.westerlund@ericsson.com
> > > > > > > >
> > > > > >
> > > >
> > --------------------------------------------------------------------
> --
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > mmusic mailing list
> > > > > > > mmusic@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > > > >
> > > > > > _______________________________________________
> > > > > > mmusic mailing list
> > > > > > mmusic@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
>=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 Wed May 09 14:16:58 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hlqie-0000NF-PI; Wed, 09 May 2007 14:16:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlqid-0000NA-5x
	for mmusic@ietf.org; Wed, 09 May 2007 14:16:55 -0400
Received: from [63.110.43.12] (helo=mail.covergence.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hlqia-0007v2-Ud
	for mmusic@ietf.org; Wed, 09 May 2007 14:16:55 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 9 May 2007 14:16:51 -0400
Message-ID: <0D1719326D64BD4E9F92A0C120237678020127FC@eserv.covergence.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-mmusic-media-loopback-06.txt
Thread-Index: AceSZjcU0H3IX9sQSaiFy6vkISdVVQ==
From: "Rick Porter" <rporter@covergence.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [MMUSIC] Comments on draft-ietf-mmusic-media-loopback-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Here are a few comments/questions...

1. Where does SRTP encryption/decryption come when doing packet
loopback? For media loopback, you obviously need to decrypt any
encrypted packets. If you're on a link that "always" does SRTP, I would
think that you'd want to be able to see how much jitter/loss/latency is
introduced by encryption/decryption and possibly compare
plaintext/encrypted performance.

2. Should looped back packets go thru the jitter buffer on the mirror?
If they do not, the jitter for a call will be compounded. If they do,
the latency is increased--depending on implementation, you may be able
to subtract jitter-buffer delay if the inner timestamp portion of the
encapsulated packet is set to the received timestamp (instead of simply
repeating the RTP timestamp).=20

3. Can we reduce SDP to have a single media-description, even when
mirror initially sends packets? I think the session should only have one
media stream, and the second media-description/stream may confuse
non-loopback aware devices who handle the media (e.g. SBCs).

4. With packet loopback, can/should the mirror truncate the last 16
bytes of RTP payload to preserve RTP characteristics? In many
situations, I think the RTP header should be sufficient for processing.
However, I do see some situations where a device in the middle could
potentially transcode RTP packets so that the mirror does not receive
the original RTP and it may be desirable to have the whole RTP payload.=20

Cheers,
Rick


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



From mmusic-bounces@ietf.org Wed May 09 14:53:38 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HlrI8-000402-OY; Wed, 09 May 2007 14:53:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HlrI7-0003zw-Pn
	for mmusic@ietf.org; Wed, 09 May 2007 14:53:35 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlrI4-0007K6-Qt
	for mmusic@ietf.org; Wed, 09 May 2007 14:53:35 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	l49IrS6J029214
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 9 May 2007 11:53:29 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	l49IrSgc016070; Wed, 9 May 2007 11:53:28 -0700
Received: from NAEX01.qualcomm.com ([129.46.51.60]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 May 2007 11:53:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Wed, 9 May 2007 11:53:27 -0700
Message-ID: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD19D7@NAEX01.na.qualcomm.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C60D92FF@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer Was
	RE:[MMUSIC]Comments on
	draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaAAD/BCkAA2S8NQAP1E2pAABPVIIA==
References: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com><9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int>
	<2CA3E1B6CEC064449CAA7D0FAB46079B02CD169B@NAEX01.na.qualcomm.com>
	<9AAEDF491EF7CA48AB587781B8F5D7C60D92FF@srvxchg3.cablelabs.com>
From: "Desineni, Harikishan" <hdesinen@qualcomm.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>
X-OriginalArrivalTime: 09 May 2007 18:53:28.0415 (UTC)
	FILETIME=[54BC96F0:01C7926B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b6435b1bfa5977f2eb96dc7e52434b6d
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>
Errors-To: mmusic-bounces@ietf.org

My current plan (based on the feedback received on this mailing list and
some offline discussions) is to write a new draft (updates rfc3890) with
title "SDP bandwidth attributes in offer/answer sessions". The new draft
will describe the new type of usage of TIAS and obsolete the combined
usage of (TIAS,maxprate) for offer/answer. No disagreement was expressed
for this change on this mailing list so far. At this time it would be
good to know if there are any disagreements on this part.

In addition, the new draft will propose several new SDP attributes
("MSR" for bit-rate in send direction, "RB" ...) for further review.


Thanks,
Hari

> -----Original Message-----
> From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]
> Sent: Wednesday, May 09, 2007 9:38 AM
> To: Desineni, Harikishan
> Cc: mmusic@ietf.org
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Hari,
>=20
>    It seems there are some issues as pointed out by your
> draft-hdesinen-mmusic-oa-send-bw-attr-02, and the requirements in RFC
> 3890 & 3264.
>=20
> Based on the txt on the b param in 3264,
>     |  "If the bandwidth attribute is present for a stream,
>     |   it indicates the desired bandwidth that the offerer
>     |   would like to receive."
> and the notes from folks who have implemented it and responded to the
> list, I too agree that it is best to keep the current usage (TIAS as
> declarative of what the agent is willing to receive).
>=20
> An update to 3890 with a new TIAS value and clarifications about the
> current ones seem appropriate.
>=20
> Does anyone disagree on this path forward?
>=20
> Jean-Francois.
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Friday, May 04, 2007 9:34 AM
> > To: Geir Arne Sandbakken; Even, Roni; mmusic@ietf.org
> > Cc: Magnus Westerlund; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> > RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Thanks for the responses.  I too think that the declarative usage of
> > TIAS as a receive bit-rate (RTP Payload) in offer/answer shall
> > continue
> > to exist.
> >
> > Thanks,
> > Hari
> >
> > > -----Original Message-----
> > > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > > Sent: Thursday, May 03, 2007 7:05 AM
> > > To: Even, Roni; Desineni, Harikishan; mmusic@ietf.org
> > > Cc: Magnus Westerlund; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Hari,
> > >
> > > We are using it just as Roni explains. Receiver bandwidth
indication
> > has
> > > been very useful for us, and it makes it possible to do quick
> > > adjustments at the sender side without any renegotiation.
> > >
> > > Cheers,
> > > Geir Arne
> > >
> > > > -----Original Message-----
> > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > Sent: 03 May 2007 08:03
> > > > To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> > > > Cc: Magnus Westerlund; Colin Perkins
> > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> > RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Hary,
> > > > TIAS is being used as a media level attribute indicating the
> > maximum
> > > BW
> > > > that the receiver would like to get. It is not used in offer
> > answer.
> > > The
> > > > semantic of the attribute (what is bw) is as specified in RFC
3890
> > > >
> > > > Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > Sent: Monday, April 30, 2007 2:13 PM
> > > > > To: Geir Arne Sandbakken; mmusic@ietf.org
> > > > > Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> > > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
Was
> > RE:
> > > > > [MMUSIC]Comments on
draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > >
> > > > > Geir,
> > > > >
> > > > > Thanks for your feedback.
> > > > >
> > > > > Can you elaborate on how exactly this attribute is used in the
> > > > > implementations known to you? I'd like to understand how
closely
> > or
> > > > > differently it is used from the way it is documented in
rfc3890.
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Geir Arne Sandbakken
> > [mailto:geir.sandbakken@tandberg.com]
> > > > > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > > > > To: Desineni, Harikishan; mmusic@ietf.org
> > > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin
Perkins
> > > > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
> > Was
> > > RE:
> > > > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-
> > 02.txt
> > > > > >
> > > > > > Harikishan,
> > > > > >
> > > > > > We have been using TIAS in the 'recv' direction for quite a
> > while,
> > > > and
> > > > > I
> > > > > > know of multiple other implementations.  Think we have been
> > > > promoting
> > > > > > the usage in the last 3 SIPit's, and changing the direction
> > will
> > > > lead
> > > > > to
> > > > > > serious interoperability issues.
> > > > > >
> > > > > > I do agree that a 'send' direction attribute is desirable as
> > > > > additional
> > > > > > bandwidth information, and I hope it can be done without
> > breaking
> > > > > > existing implementations.
> > > > > >
> > > > > > Cheers,
> > > > > > Geir Arne
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > > > Sent: 17 April 2007 20:40
> > > > > > > To: mmusic@ietf.org
> > > > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin
> > Perkins
> > > > > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer
Was
> > RE:
> > > > > > > [MMUSIC]Comments on
> > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > > > >
> > > > > > > Some issues with the offer/answer usage of TIAS (defined
in
> > > > RFC3890)
> > > > > > > came out while discussing
> > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > > > > >
> > > > > > > RFC3890 has incorrectly defined TIAS and maxprate as
'recv'
> > > > > direction
> > > > > > > attributes in offer/answer model. As 'recv' attributes,
TIAS
> > and
> > > > > > > maxprate do not solve the bandwidth negotiation problem.
For
> > > > > > > offer/answer bw negotiation to work properly, the correct
> > > > direction
> > > > > in
> > > > > > > rfc3890 should have been 'send', probably with the help of
> > few
> > > new
> > > > > > > 'recv' direction attributes (like PO - per packet overhead
> > at
> > > > layer
> > > > > X,
> > > > > > > RB- receive BW at layer X) under discussion.
> > > > > > >
> > > > > > > A sender would choose (TIAS,maxprate) which satisfy the
> > > following
> > > > > > > formula
> > > > > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by
the
> > > > > receiver)
> > > > > > >
> > > > > > > One approach to handle this is changing the direction of
> > > > > > (TIAS,maxprate)
> > > > > > > to 'send' and prevent the incorrect ('recv') usage of
> > > > > (TIAS,maxprate)
> > > > > > in
> > > > > > > offer/answer model. While this appears to be the desired
> > > > direction,
> > > > > I
> > > > > > am
> > > > > > > interested to know the impact of such a change on (any)
> > existing
> > > > > > > implementations of TIAS in offer/answer.
> > > > > > >
> > > > > > > Please comment if you are aware of any existing
> > implementations
> > > of
> > > > > > TIAS
> > > > > > > in offer/answer and also describe how exactly TIAS was
used
> > in
> > > > that
> > > > > > > particular implementation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Hari
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Desineni, Harikishan
[mailto:hdesinen@qualcomm.com]
> > > > > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > > > > Cc: Mahendran, AC; Dondeti, Lakshminath;
mmusic@ietf.org;
> > > > > > avt@ietf.org
> > > > > > > > Subject: RE: [MMUSIC] Comments on
> > > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > > 02.txt
> > > > > > > >
> > > > > > > > I copied a post (from AVT list) from Roni which states
> > that
> > > TIAS
> > > > > was
> > > > > > > > actually used in his implementation. I am not sure if it
> > is
> > an
> > > > > > > > implementation in offer/answer model.
> > > > > > > >
> > > > > > > > [CCed AVT as TIAS was also recently discussed on AVT
list]
> > > > > > > >
> > > > > > > > "
> > > > > > > > -----Original Message-----
> > > > > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > > > > To: Randell Jesup
> > > > > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > > > > Subject: RE: [AVT] CCM draft review -- should
"bandwidth"
> > > > include
> > > > > > > > theheaderoverhead
> > > > > > > >
> > > > > > > > Randell,
> > > > > > > > RFC 4890 recommends sending both TIAS and AS for
backward
> > > > > > > compatibility
> > > > > > > > with systems that do not support TIAS. This RFC gives a
> > good
> > > > > > > explanation
> > > > > > > > why to use TIAS. This is what we do in our
implementation.
> > > > > > > > "
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Magnus Westerlund
> > > > [mailto:magnus.westerlund@ericsson.com]
> > > > > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > > > > To: Desineni, Harikishan
> > > > > > > > > Cc: mmusic@ietf.org
> > > > > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > > > 02.txt
> > > > > > > > >
> > > > > > > > > Desineni, Harikishan skrev:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Magnus,
> > > > > > > > > >
> > > > > > > > > > Thanks for the comments.
> > > > > > > > > >
> > > > > > > > > > In the initial version, I captured the current
> > > understanding
> > > > > of
> > > > > > > > (TIAS
> > > > > > > > > > ,maxprate) based on RFC3890.
> > > > > > > > > >
> > > > > > > > > > Based on the current RFCs, majority of the community
> > > > > interprets
> > > > > > > TIAS
> > > > > > > > as
> > > > > > > > > > receive only direction attribute. Instead of
updating
> > > > RFC3890
> > > > > to
> > > > > > > > modify
> > > > > > > > > > TIAS as a send direction only attribute, it is
better
> > to
> > > use
> > > > a
> > > > > > new
> > > > > > > > > > attribute 'MSR' proposed in this draft. This would
> > also
> > > > avoid
> > > > > > any
> > > > > > > > > > backward compatibility/inter-op issues that can
arise
> > with
> > > > > > current
> > > > > > > > > > implementations which (correctly) interpret TIAS as
> > > receive
> > > > > > > > direction
> > > > > > > > > > only attribute in offer/answer.
> > > > > > > > >
> > > > > > > > > Well, I wonder how there can be backwards
compatibility
> > > issues
> > > > > > with
> > > > > > > > > something that clearly doesn't work if you actually
try
> > to
> > > use
> > > > > it.
> > > > > > > > There
> > > > > > > > > might be implementations but I can't really understand
> > how
> > > > they
> > > > > > > could
> > > > > > > > > work. Do you know of implementations?
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Another approach is to add directionality to TIAS.
By
> > > > default,
> > > > > > > TIAS
> > > > > > > > is
> > > > > > > > > > receive only (not much useful) and "TIAS/sendonly"
> > will
> > be
> > > > > send
> > > > > > > only
> > > > > > > > > > direction. "maxprate/send" will be packet rate in
send
> > > > > > direction.
> > > > > > > > > >
> > > > > > > > > > What you are proposing is the following
> > > > > > > > > > Send direction attributes: RTP Payload rate and
> > maxpacket
> > > > rate
> > > > > > > > > > Receive direction attributes: AS (or a new one),
> > packet
> > > > > overhead
> > > > > > > > >
> > > > > > > > > Okay, here I think the more important question is, are
> > we
> > > > > > expecting
> > > > > > > to
> > > > > > > > > be able to specify a value on another level than IP?
If
> > not
> > > I
> > > > > > think
> > > > > > > AS
> > > > > > > > > works fine.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > In this draft I am proposing that 'MSR' be used for
> > > > signaling
> > > > > > RTP
> > > > > > > > > > payload rate in 'send' direction. IMO, it is not a
> > clean
> > > > > > approach
> > > > > > > to
> > > > > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > > > > >
> > > > > > > > > We disagree on this. TIAS was specified as a send
> > direction
> > > > > > > attribute.
> > > > > > > > I
> > > > > > > > > made an error in the offer/answer usage because I
didn't
> > > > > consider
> > > > > > > the
> > > > > > > > > implications. And no one picked up on it.
> > > > > > > > >
> > > > > > > > > As I can see it in regards to RFC 3890 we have two
> > > > alternatives:
> > > > > > > > >
> > > > > > > > > 1. Fix the offer/answer section to correctly define it
> > to
> > > > apply
> > > > > in
> > > > > > > the
> > > > > > > > > sending direction.
> > > > > > > > >
> > > > > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges
and
> > only
> > > > use
> > > > > > it
> > > > > > > > for
> > > > > > > > > declarative usage, like in RTSP.
> > > > > > > > >
> > > > > > > > > If there are implementations i any numbers that
> > interpret
> > > TIAS
> > > > > as
> > > > > > a
> > > > > > > > > receiver direction attribute then I agree alternative
2
> > will
> > > > be
> > > > > > > best.
> > > > > > > > > However I would like to have some positive
> > acknowledgments
> > > of
> > > > > this
> > > > > > > > > first. This was after all revealed in the attempt to
> > apply
> > > > TIAS
> > > > > to
> > > > > > > > > offer/answer in the 3GPP MTSI standardization work.
> > > Resulting
> > > > in
> > > > > > > that
> > > > > > > > > TIAS was only included in the draft spec for a while.
I
> > > don't
> > > > > know
> > > > > > > if
> > > > > > > > > some other umbrella standard has included TIAS
combined
> > with
> > > > > > > > offer/answer.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I am OK with signaling packet rate in send
direction.
> > But
> > > we
> > > > > > need
> > > > > > > to
> > > > > > > > > > consider whether to reuse maxprate for this or add
> > > > > > directionality
> > > > > > > to
> > > > > > > > > > maxprate (maxprate/send) to avoid any inter-op
issues
> > with
> > > > > > current
> > > > > > > > > > implementations.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Cheers
> > > > > > > > >
> > > > > > > > > Magnus Westerlund
> > > > > > > > >
> > > > > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > > > > magnus.westerlund@ericsson.com
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > mmusic mailing list
> > > > > > > > mmusic@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > mmusic mailing list
> > > > > > > mmusic@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
> > _______________________________________________
> > 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 May 09 23:38:32 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HlzU5-0004mS-11; Wed, 09 May 2007 23:38:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HlzU4-0004mN-CH
	for mmusic@ietf.org; Wed, 09 May 2007 23:38:28 -0400
Received: from smtp1.lifesize.com ([209.163.159.7] helo=ns1.lifesize.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlzU1-0003qq-IP
	for mmusic@ietf.org; Wed, 09 May 2007 23:38:28 -0400
Received: from lsmail.austin.kmvtechnologies.com
	(lsmail.austin.kmvtechnologies.com [10.10.10.50])
	by ns1.lifesize.com (8.13.8/8.12.8) with ESMTP id l4A3cKqS001461;
	Wed, 9 May 2007 22:38:20 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
	WasRE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Date: Wed, 9 May 2007 22:38:18 -0500
Message-ID: <717562D70E24CF489737F81B0EA234DF05DD36A3@lsmail.austin.kmvtechnologies.com>
In-Reply-To: <2CA3E1B6CEC064449CAA7D0FAB46079B02CD19D7@NAEX01.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal to modify RFC3890 TIAS in offer/answer
	WasRE:[MMUSIC]Comments on
	draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
Thread-Index: Acdn6mV7RvdCSEKsS5ew8hdKBSP3egAeU+fgBd+tG7ABy+/cUAEBgCNwAIwRsaAAD/BCkAA2S8NQAP1E2pAABPVIIAASHcTg
References: <144ED8561CE90C41A3E5908EDECE315C0484F1CC@IsrExch01.israel.polycom.com><9F6ACAE02B6DD040A1E259977622CFDB2699D5@oslexcp1.eu.tandberg.int><2CA3E1B6CEC064449CAA7D0FAB46079B02CD169B@NAEX01.na.qualcomm.com><9AAEDF491EF7CA48AB587781B8F5D7C60D92FF@srvxchg3.cablelabs.com>
	<2CA3E1B6CEC064449CAA7D0FAB46079B02CD19D7@NAEX01.na.qualcomm.com>
From: "Ashish Goyal" <agoyal@lifesize.com>
To: "Desineni, Harikishan" <hdesinen@qualcomm.com>,
	"Jean-Francois Mule" <jf.mule@cablelabs.com>
X-Scanned-By: MIMEDefang 2.57 on 10.10.10.41
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c07eeb7900970a16fe4056cc74ae9ce2
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>
Errors-To: mmusic-bounces@ietf.org

Hi Hari,=20
	As long as the declarative usage of TIAS remains - I am fine. We
have been using it in a declarative mode in videoconferencing arena. I
would be interested in staying the loop for the proposed modifications
to rfc 3890 or of the usage of TIAS/maxprate.

Thanks,=20
Ashish

-----Original Message-----
From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]=20
Sent: Thursday, May 10, 2007 12:23 AM
To: Jean-Francois Mule
Cc: mmusic@ietf.org
Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
WasRE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt

My current plan (based on the feedback received on this mailing list and
some offline discussions) is to write a new draft (updates rfc3890) with
title "SDP bandwidth attributes in offer/answer sessions". The new draft
will describe the new type of usage of TIAS and obsolete the combined
usage of (TIAS,maxprate) for offer/answer. No disagreement was expressed
for this change on this mailing list so far. At this time it would be
good to know if there are any disagreements on this part.

In addition, the new draft will propose several new SDP attributes
("MSR" for bit-rate in send direction, "RB" ...) for further review.


Thanks,
Hari

> -----Original Message-----
> From: Jean-Francois Mule [mailto:jf.mule@cablelabs.com]
> Sent: Wednesday, May 09, 2007 9:38 AM
> To: Desineni, Harikishan
> Cc: mmusic@ietf.org
> Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was=20
> RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
>=20
> Hari,
>=20
>    It seems there are some issues as pointed out by your=20
> draft-hdesinen-mmusic-oa-send-bw-attr-02, and the requirements in RFC=20
> 3890 & 3264.
>=20
> Based on the txt on the b param in 3264,
>     |  "If the bandwidth attribute is present for a stream,
>     |   it indicates the desired bandwidth that the offerer
>     |   would like to receive."
> and the notes from folks who have implemented it and responded to the=20
> list, I too agree that it is best to keep the current usage (TIAS as=20
> declarative of what the agent is willing to receive).
>=20
> An update to 3890 with a new TIAS value and clarifications about the=20
> current ones seem appropriate.
>=20
> Does anyone disagree on this path forward?
>=20
> Jean-Francois.
>=20
> > -----Original Message-----
> > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > Sent: Friday, May 04, 2007 9:34 AM
> > To: Geir Arne Sandbakken; Even, Roni; mmusic@ietf.org
> > Cc: Magnus Westerlund; Colin Perkins
> > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was=20
> > RE:[MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> >
> > Thanks for the responses.  I too think that the declarative usage of

> > TIAS as a receive bit-rate (RTP Payload) in offer/answer shall=20
> > continue to exist.
> >
> > Thanks,
> > Hari
> >
> > > -----Original Message-----
> > > From: Geir Arne Sandbakken [mailto:geir.sandbakken@tandberg.com]
> > > Sent: Thursday, May 03, 2007 7:05 AM
> > > To: Even, Roni; Desineni, Harikishan; mmusic@ietf.org
> > > Cc: Magnus Westerlund; Colin Perkins
> > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
RE:
> > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > >
> > > Hari,
> > >
> > > We are using it just as Roni explains. Receiver bandwidth
indication
> > has
> > > been very useful for us, and it makes it possible to do quick=20
> > > adjustments at the sender side without any renegotiation.
> > >
> > > Cheers,
> > > Geir Arne
> > >
> > > > -----Original Message-----
> > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > Sent: 03 May 2007 08:03
> > > > To: Desineni, Harikishan; Geir Arne Sandbakken; mmusic@ietf.org
> > > > Cc: Magnus Westerlund; Colin Perkins
> > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer Was
> > RE:
> > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > >
> > > > Hary,
> > > > TIAS is being used as a media level attribute indicating the
> > maximum
> > > BW
> > > > that the receiver would like to get. It is not used in offer
> > answer.
> > > The
> > > > semantic of the attribute (what is bw) is as specified in RFC
3890
> > > >
> > > > Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > Sent: Monday, April 30, 2007 2:13 PM
> > > > > To: Geir Arne Sandbakken; mmusic@ietf.org
> > > > > Cc: Magnus Westerlund; Even, Roni; Colin Perkins
> > > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
Was
> > RE:
> > > > > [MMUSIC]Comments on
draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > >
> > > > > Geir,
> > > > >
> > > > > Thanks for your feedback.
> > > > >
> > > > > Can you elaborate on how exactly this attribute is used in the

> > > > > implementations known to you? I'd like to understand how
closely
> > or
> > > > > differently it is used from the way it is documented in
rfc3890.
> > > > >
> > > > > Thanks,
> > > > > Hari
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Geir Arne Sandbakken
> > [mailto:geir.sandbakken@tandberg.com]
> > > > > > Sent: Wednesday, April 25, 2007 1:31 AM
> > > > > > To: Desineni, Harikishan; mmusic@ietf.org
> > > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin
Perkins
> > > > > > Subject: RE: Proposal to modify RFC3890 TIAS in offer/answer
> > Was
> > > RE:
> > > > > > [MMUSIC]Comments on draft-hdesinen-mmusic-oa-send-bw-attr-
> > 02.txt
> > > > > >
> > > > > > Harikishan,
> > > > > >
> > > > > > We have been using TIAS in the 'recv' direction for quite a
> > while,
> > > > and
> > > > > I
> > > > > > know of multiple other implementations.  Think we have been
> > > > promoting
> > > > > > the usage in the last 3 SIPit's, and changing the direction
> > will
> > > > lead
> > > > > to
> > > > > > serious interoperability issues.
> > > > > >
> > > > > > I do agree that a 'send' direction attribute is desirable as
> > > > > additional
> > > > > > bandwidth information, and I hope it can be done without
> > breaking
> > > > > > existing implementations.
> > > > > >
> > > > > > Cheers,
> > > > > > Geir Arne
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Desineni, Harikishan [mailto:hdesinen@qualcomm.com]
> > > > > > > Sent: 17 April 2007 20:40
> > > > > > > To: mmusic@ietf.org
> > > > > > > Cc: Magnus Westerlund; roni.even@polycom.co.il; Colin
> > Perkins
> > > > > > > Subject: Proposal to modify RFC3890 TIAS in offer/answer
Was
> > RE:
> > > > > > > [MMUSIC]Comments on
> > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt
> > > > > > >
> > > > > > > Some issues with the offer/answer usage of TIAS (defined
in
> > > > RFC3890)
> > > > > > > came out while discussing
> > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-02.txt.
> > > > > > >
> > > > > > > RFC3890 has incorrectly defined TIAS and maxprate as
'recv'
> > > > > direction
> > > > > > > attributes in offer/answer model. As 'recv' attributes,
TIAS
> > and
> > > > > > > maxprate do not solve the bandwidth negotiation problem.
For
> > > > > > > offer/answer bw negotiation to work properly, the correct
> > > > direction
> > > > > in
> > > > > > > rfc3890 should have been 'send', probably with the help of
> > few
> > > new
> > > > > > > 'recv' direction attributes (like PO - per packet overhead
> > at
> > > > layer
> > > > > X,
> > > > > > > RB- receive BW at layer X) under discussion.
> > > > > > >
> > > > > > > A sender would choose (TIAS,maxprate) which satisfy the
> > > following
> > > > > > > formula
> > > > > > > TIAS + (maxprate * PO) <=3D RB (PO and RB are signaled by
the
> > > > > receiver)
> > > > > > >
> > > > > > > One approach to handle this is changing the direction of
> > > > > > (TIAS,maxprate)
> > > > > > > to 'send' and prevent the incorrect ('recv') usage of
> > > > > (TIAS,maxprate)
> > > > > > in
> > > > > > > offer/answer model. While this appears to be the desired
> > > > direction,
> > > > > I
> > > > > > am
> > > > > > > interested to know the impact of such a change on (any)
> > existing
> > > > > > > implementations of TIAS in offer/answer.
> > > > > > >
> > > > > > > Please comment if you are aware of any existing
> > implementations
> > > of
> > > > > > TIAS
> > > > > > > in offer/answer and also describe how exactly TIAS was
used
> > in
> > > > that
> > > > > > > particular implementation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Hari
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Desineni, Harikishan
[mailto:hdesinen@qualcomm.com]
> > > > > > > > Sent: Saturday, March 17, 2007 12:26 AM
> > > > > > > > To: Magnus Westerlund; roni.even@polycom.co.il
> > > > > > > > Cc: Mahendran, AC; Dondeti, Lakshminath;
mmusic@ietf.org;
> > > > > > avt@ietf.org
> > > > > > > > Subject: RE: [MMUSIC] Comments on
> > > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > > 02.txt
> > > > > > > >
> > > > > > > > I copied a post (from AVT list) from Roni which states
> > that
> > > TIAS
> > > > > was
> > > > > > > > actually used in his implementation. I am not sure if it
> > is
> > an
> > > > > > > > implementation in offer/answer model.
> > > > > > > >
> > > > > > > > [CCed AVT as TIAS was also recently discussed on AVT
list]
> > > > > > > >
> > > > > > > > "
> > > > > > > > -----Original Message-----
> > > > > > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > > > > > Sent: Monday, January 08, 2007 7:35 AM
> > > > > > > > To: Randell Jesup
> > > > > > > > Cc: Stephan Wenger; avt@ietf.org
> > > > > > > > Subject: RE: [AVT] CCM draft review -- should
"bandwidth"
> > > > include
> > > > > > > > theheaderoverhead
> > > > > > > >
> > > > > > > > Randell,
> > > > > > > > RFC 4890 recommends sending both TIAS and AS for
backward
> > > > > > > compatibility
> > > > > > > > with systems that do not support TIAS. This RFC gives a
> > good
> > > > > > > explanation
> > > > > > > > why to use TIAS. This is what we do in our
implementation.
> > > > > > > > "
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Magnus Westerlund
> > > > [mailto:magnus.westerlund@ericsson.com]
> > > > > > > > > Sent: Friday, March 16, 2007 9:44 AM
> > > > > > > > > To: Desineni, Harikishan
> > > > > > > > > Cc: mmusic@ietf.org
> > > > > > > > > Subject: Re: [MMUSIC] Comments on
> > > > > > > > draft-hdesinen-mmusic-oa-send-bw-attr-
> > > > > > > > > 02.txt
> > > > > > > > >
> > > > > > > > > Desineni, Harikishan skrev:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Magnus,
> > > > > > > > > >
> > > > > > > > > > Thanks for the comments.
> > > > > > > > > >
> > > > > > > > > > In the initial version, I captured the current
> > > understanding
> > > > > of
> > > > > > > > (TIAS
> > > > > > > > > > ,maxprate) based on RFC3890.
> > > > > > > > > >
> > > > > > > > > > Based on the current RFCs, majority of the community
> > > > > interprets
> > > > > > > TIAS
> > > > > > > > as
> > > > > > > > > > receive only direction attribute. Instead of
updating
> > > > RFC3890
> > > > > to
> > > > > > > > modify
> > > > > > > > > > TIAS as a send direction only attribute, it is
better
> > to
> > > use
> > > > a
> > > > > > new
> > > > > > > > > > attribute 'MSR' proposed in this draft. This would
> > also
> > > > avoid
> > > > > > any
> > > > > > > > > > backward compatibility/inter-op issues that can
arise
> > with
> > > > > > current
> > > > > > > > > > implementations which (correctly) interpret TIAS as
> > > receive
> > > > > > > > direction
> > > > > > > > > > only attribute in offer/answer.
> > > > > > > > >
> > > > > > > > > Well, I wonder how there can be backwards
compatibility
> > > issues
> > > > > > with
> > > > > > > > > something that clearly doesn't work if you actually
try
> > to
> > > use
> > > > > it.
> > > > > > > > There
> > > > > > > > > might be implementations but I can't really understand
> > how
> > > > they
> > > > > > > could
> > > > > > > > > work. Do you know of implementations?
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Another approach is to add directionality to TIAS.
By
> > > > default,
> > > > > > > TIAS
> > > > > > > > is
> > > > > > > > > > receive only (not much useful) and "TIAS/sendonly"
> > will
> > be
> > > > > send
> > > > > > > only
> > > > > > > > > > direction. "maxprate/send" will be packet rate in
send
> > > > > > direction.
> > > > > > > > > >
> > > > > > > > > > What you are proposing is the following Send=20
> > > > > > > > > > direction attributes: RTP Payload rate and
> > maxpacket
> > > > rate
> > > > > > > > > > Receive direction attributes: AS (or a new one),
> > packet
> > > > > overhead
> > > > > > > > >
> > > > > > > > > Okay, here I think the more important question is, are
> > we
> > > > > > expecting
> > > > > > > to
> > > > > > > > > be able to specify a value on another level than IP?
If
> > not
> > > I
> > > > > > think
> > > > > > > AS
> > > > > > > > > works fine.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > In this draft I am proposing that 'MSR' be used for
> > > > signaling
> > > > > > RTP
> > > > > > > > > > payload rate in 'send' direction. IMO, it is not a
> > clean
> > > > > > approach
> > > > > > > to
> > > > > > > > > > redefine TIAS to be a 'send' direction attribute.
> > > > > > > > >
> > > > > > > > > We disagree on this. TIAS was specified as a send
> > direction
> > > > > > > attribute.
> > > > > > > > I
> > > > > > > > > made an error in the offer/answer usage because I
didn't
> > > > > consider
> > > > > > > the
> > > > > > > > > implications. And no one picked up on it.
> > > > > > > > >
> > > > > > > > > As I can see it in regards to RFC 3890 we have two
> > > > alternatives:
> > > > > > > > >
> > > > > > > > > 1. Fix the offer/answer section to correctly define it
> > to
> > > > apply
> > > > > in
> > > > > > > the
> > > > > > > > > sending direction.
> > > > > > > > >
> > > > > > > > > 2. Obsolete usage of TIAS in Offer/Answer exchanges
and
> > only
> > > > use
> > > > > > it
> > > > > > > > for
> > > > > > > > > declarative usage, like in RTSP.
> > > > > > > > >
> > > > > > > > > If there are implementations i any numbers that
> > interpret
> > > TIAS
> > > > > as
> > > > > > a
> > > > > > > > > receiver direction attribute then I agree alternative
2
> > will
> > > > be
> > > > > > > best.
> > > > > > > > > However I would like to have some positive
> > acknowledgments
> > > of
> > > > > this
> > > > > > > > > first. This was after all revealed in the attempt to
> > apply
> > > > TIAS
> > > > > to
> > > > > > > > > offer/answer in the 3GPP MTSI standardization work.
> > > Resulting
> > > > in
> > > > > > > that
> > > > > > > > > TIAS was only included in the draft spec for a while.
I
> > > don't
> > > > > know
> > > > > > > if
> > > > > > > > > some other umbrella standard has included TIAS
combined
> > with
> > > > > > > > offer/answer.
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I am OK with signaling packet rate in send
direction.
> > But
> > > we
> > > > > > need
> > > > > > > to
> > > > > > > > > > consider whether to reuse maxprate for this or add
> > > > > > directionality
> > > > > > > to
> > > > > > > > > > maxprate (maxprate/send) to avoid any inter-op
issues
> > with
> > > > > > current
> > > > > > > > > > implementations.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Cheers
> > > > > > > > >
> > > > > > > > > Magnus Westerlund
> > > > > > > > >
> > > > > > > > > IETF Transport Area Director & TSVWG Chair
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > > > Multimedia Technologies, Ericsson Research EAB/TVM/M
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > > > Ericsson AB                | Phone +46 8 4048287
> > > > > > > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > > > > > > S-164 80 Stockholm, Sweden | mailto:
> > > > > > magnus.westerlund@ericsson.com
> > > > > > > > >
> > > > > > >
> > > > >
> > >
--------------------------------------------------------------------
> > --
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > mmusic mailing list
> > > > > > > > mmusic@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > mmusic mailing list
> > > > > > > mmusic@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/mmusic
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic


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

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



From mmusic-bounces@ietf.org Thu May 10 08:09:12 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hm7S8-0008Ks-Px; Thu, 10 May 2007 08:09:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm7S7-0008Ji-AU
	for mmusic@ietf.org; Thu, 10 May 2007 08:08:59 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm7S4-0003OK-RP
	for mmusic@ietf.org; Thu, 10 May 2007 08:08:59 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4AC8dtb020972; Thu, 10 May 2007 15:08:52 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 May 2007 15:08:44 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 May 2007 15:08:44 +0300
Received: from esdhcp04138.research.nokia.com ([172.21.41.38]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 May 2007 15:08:44 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: mmusic@ietf.org, "ext Jonathan Rosenberg" <jdrosen@cisco.com>
Date: Thu, 10 May 2007 15:08:50 +0300
User-Agent: KMail/1.9.6
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200705101508.51165.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 10 May 2007 12:08:44.0587 (UTC)
	FILETIME=[F4DC3FB0:01C792FB]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: 
Subject: [MMUSIC] ICE question: Authentication of errors ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mmusic@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>
Errors-To: mmusic-bounces@ietf.org

	Hello,

It is not clear to me whether/when should STUN Binding Error Responses need=
 to=20
be authenticated (in ICE context or otherwise). RFC3489bis seems to imply=20
that only succesful Binding Responses are authenticated using=20
MESSAGE-INTEGRITY...

So so, is the 96-bits transaction ID sufficient for authenticating, say Rol=
e=20
conflict errors? I would assume YES, since only a MITM can learn the=20
pseudo-random transaction ID, and an MITM can DoS the media in any case.

=2D-=20
R=E9mi Denis-Courmont

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



From mmusic-bounces@ietf.org Thu May 10 10:10:47 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hm9Lp-0007DD-W6; Thu, 10 May 2007 10:10:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm9Lh-0006gw-VE
	for mmusic@ietf.org; Thu, 10 May 2007 10:10:29 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm9JQ-0005vD-3c
	for mmusic@ietf.org; Thu, 10 May 2007 10:08:11 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 10 May 2007 07:08:03 -0700
X-IronPort-AV: i="4.14,518,1170662400"; 
	d="scan'208"; a="147121030:sNHT40335525"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l4AE83pT031379
	for <mmusic@ietf.org>; Thu, 10 May 2007 07:08:03 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4AE83ZT001687
	for <mmusic@ietf.org>; Thu, 10 May 2007 14:08:03 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 May 2007 07:08:03 -0700
Received: from [10.32.241.146] ([10.32.241.146]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 May 2007 07:08:02 -0700
Message-ID: <46432742.4020107@cisco.com>
Date: Thu, 10 May 2007 10:08:02 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
References: <200705101508.51165.remi.denis-courmont@nokia.com>
In-Reply-To: <200705101508.51165.remi.denis-courmont@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 10 May 2007 14:08:02.0974 (UTC)
	FILETIME=[9F976BE0:01C7930C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1123; t=1178806083;
	x=1179670083; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20ICE=20question=3A=20Authentication=20of=20errors=20?
	|Sender:=20; bh=y/VcFLHlRK88NeJJSWqc7LjU/7QWMiJTVoV2CHrznVs=;
	b=Tf+HOQXMG8DzmXyPozR2K+IpqLwYysgdm0t5ro6sd3mhDFc8xMxg2dg298+V+Vy9HSPFDbhk
	vWa7UL4BtqQ1mEY+mkMNB2rMliX6uB8ztWTCyaCsFgiupzJkHmRS/tfs;
Authentication-Results: sj-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [MMUSIC] Re: ICE question: Authentication of errors ?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

The idea is that all errors except for a few related to lack of 
available credentials, should be authenticated. Otherwise an attacker 
can inject fake error responses. They would only need to inspect the 
request to learn the transaction ID.

-Jonathan R.

Rémi Denis-Courmont wrote:

> 	Hello,
> 
> It is not clear to me whether/when should STUN Binding Error Responses need to 
> be authenticated (in ICE context or otherwise). RFC3489bis seems to imply 
> that only succesful Binding Responses are authenticated using 
> MESSAGE-INTEGRITY...
> 
> So so, is the 96-bits transaction ID sufficient for authenticating, say Role 
> conflict errors? I would assume YES, since only a MITM can learn the 
> pseudo-random transaction ID, and an MITM can DoS the media in any case.
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   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 May 10 21:10:26 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmJeK-0008Cf-Rl; Thu, 10 May 2007 21:10:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmJeJ-0008CQ-AB
	for mmusic@ietf.org; Thu, 10 May 2007 21:10:23 -0400
Received: from nz-out-0506.google.com ([64.233.162.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmJeJ-00025n-0c
	for mmusic@ietf.org; Thu, 10 May 2007 21:10:23 -0400
Received: by nz-out-0506.google.com with SMTP id z6so889974nzd
	for <mmusic@ietf.org>; Thu, 10 May 2007 18:10:22 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=jGPySlaCHtQz6atnPCjQXT+1YojMCmsWKcZaos86ps14C6W0nP0d0v7IW8noBUScqZzlupEIBTw8vmSG6ejP522G6t8CmWIIcIwD+ALvxelBJY3WoczvE/NDtKehsR6Drmh304QA2UlF2Yug4A200q9wrnYA5AlboghiXsY8URg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=T7R8dD1xkbSXzjtOsTA1m+UOpeFTbepybsGvVsMc3GrauYCVhHQSfuajJ7KW5C/E46/JFM54avEtDupbtycNq6Juw2PiDAEtEbVolI24DpHpOjl7GNGjwWxfZ77Zdq4FPVlpTFUcK7hEOLBlTrpDn4ZquDmT/UzmtNMTCPn57wY=
Received: by 10.114.53.1 with SMTP id b1mr752162waa.1178845822336;
	Thu, 10 May 2007 18:10:22 -0700 (PDT)
Received: by 10.114.132.13 with HTTP; Thu, 10 May 2007 18:10:22 -0700 (PDT)
Message-ID: <38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com>
Date: Thu, 10 May 2007 18:10:22 -0700
From: "Greg Shepherd" <gjshep@gmail.com>
To: fecframe@ietf.org, rmt@ietf.org, mmusic@ietf.org, avt@ietf.org
In-Reply-To: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com>
MIME-Version: 1.0
References: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
Subject: [MMUSIC] Re: Request For FEC Schemes
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="===============1540192124=="
Errors-To: mmusic-bounces@ietf.org

--===============1540192124==
Content-Type: multipart/alternative; 
	boundary="----=_Part_117884_24314310.1178845822263"

------=_Part_117884_24314310.1178845822263
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

All,

On 4/12/07, Greg Shepherd <gjshep@gmail.com> wrote:
>
> Greetings,
>
> From the 68th IETF meeting in Prague, the FECFrame working group came away
> with some action items which we need to get to in order stay on track with
> our milestones:
>
> 1) Streaming Content Delivery Protocol
>        Define specific protocol elements for signalling the use of FEC
>        SDP, in particular, requires coordination with mmusic, avt and rmt
> - thus the current distribution.
>        Call for volunteers to participate as the part of a Design Team.


So far we've had two step forward willing to work on the team. This doesn't
include Mark (opt-out assigned) or the chairs. Last call.

2) Call for FEC Schemes:
>
>      Like the RMT FEC Building Block, we should define the requirements
> that FECFRAME FEC Schemes should meet;
>           Data elements that must be defined
>           Procedures that must be defined
>           Format for FEC Scheme specifications


No reponse here. Perhaps we need to expand out request outside of the above
groups.

Greg

If you're interested enough to be on this list, and/or interested enough to
> attend the WG meetings, then you must be interested enough to see this
> through to functional result - please step-up.
>
> Thanks,
> Greg
>
>

------=_Part_117884_24314310.1178845822263
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

All,<br><br><div><span class="gmail_quote">On 4/12/07, <b class="gmail_sendername">Greg Shepherd</b> &lt;<a href="mailto:gjshep@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">gjshep@gmail.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greetings,<br><br>From the 68th IETF meeting in Prague, the <span name="st">FECFrame</span> working group came away with some action items which we need to get to in order stay on track with our milestones:
<br><br>1) Streaming Content Delivery Protocol
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Define specific protocol elements for signalling the use of FEC<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SDP, in particular, requires coordination with mmusic, avt and rmt - thus the current distribution.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="font-weight: bold;">


Call for volunteers to participate as the part of a Design Team.</span></blockquote><div><br>So far we&#39;ve had two step forward willing to work on the team. This doesn&#39;t include Mark (opt-out assigned) or the chairs. Last call.&nbsp;
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2) Call for FEC Schemes:<br><br>&nbsp;&nbsp;&nbsp;&nbsp; Like the RMT FEC Building Block, we should define the requirements that 
<span name="st">FECFRAME</span> FEC Schemes should meet;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Data elements that must be defined<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Procedures that must be defined<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Format for FEC Scheme specifications</blockquote><div><br>No reponse here. Perhaps we need to expand out request outside of the above groups.
<br><br>Greg<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If you&#39;re interested enough to be on this list, and/or interested enough to attend the WG meetings, then you must be interested enough to see this through to functional result - please step-up.
<br><br>Thanks,<br><span>Greg<br><br>
</span></blockquote></div><br>

------=_Part_117884_24314310.1178845822263--


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

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

--===============1540192124==--




From mmusic-bounces@ietf.org Fri May 11 04:52:52 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmQra-0004ns-0t; Fri, 11 May 2007 04:52:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmKWK-0000Gq-V4; Thu, 10 May 2007 22:06:12 -0400
Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HmKWJ-00085B-NH; Thu, 10 May 2007 22:06:12 -0400
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1])
	by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
	with ESMTP-TLS id 6588098; Thu, 10 May 2007 22:06:11 -0400
In-Reply-To: <38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com>
References: <38c19b540704121450k611cfa11ic3ff20deee967849@mail.gmail.com>
	<38c19b540705101810y30c29b9dkff8a1f02c8a95a7@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8823D258-B4A5-4393-A334-94EA605F5F05@multicasttech.com>
Content-Transfer-Encoding: 7bit
From: Marshall Eubanks <tme@multicasttech.com>
Date: Thu, 10 May 2007 22:06:04 -0400
To: "Greg Shepherd" <gjshep@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
X-Mailman-Approved-At: Fri, 11 May 2007 04:52:33 -0400
Cc: mmusic@ietf.org, fecframe@ietf.org,
	Reliable Multicast Transport Transport <rmt@ietf.org>
Subject: [MMUSIC] Re: [Fecframe] Re: Request For FEC Schemes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

The curse of cross posting :

Hello;

I am going to the VSF Meeting in Austin next week -

http://www.videoservicesforum.org/upcoming_events/2007-05_MtgSeries- 
AustinTX.shtml

Mark Watson should be there are well; hopefully we can drum up some  
interest.

Regards
Marshall

On May 10, 2007, at 9:10 PM, Greg Shepherd wrote:

> All,
>
> On 4/12/07, Greg Shepherd <gjshep@gmail.com > wrote: Greetings,
>
> From the 68th IETF meeting in Prague, the FECFrame working group  
> came away with some action items which we need to get to in order  
> stay on track with our milestones:
>
> 1) Streaming Content Delivery Protocol
>        Define specific protocol elements for signalling the use of FEC
>        SDP, in particular, requires coordination with mmusic, avt  
> and rmt - thus the current distribution.
>        Call for volunteers to participate as the part of a Design  
> Team.
>
> So far we've had two step forward willing to work on the team. This  
> doesn't include Mark (opt-out assigned) or the chairs. Last call.
>
> 2) Call for FEC Schemes:
>
>      Like the RMT FEC Building Block, we should define the  
> requirements that FECFRAME FEC Schemes should meet;
>           Data elements that must be defined
>           Procedures that must be defined
>           Format for FEC Scheme specifications
>
> No reponse here. Perhaps we need to expand out request outside of  
> the above groups.
>
> Greg
>
> If you're interested enough to be on this list, and/or interested  
> enough to attend the WG meetings, then you must be interested  
> enough to see this through to functional result - please step-up.
>
> Thanks,
> Greg
>
>
> _______________________________________________
> Fecframe mailing list
> Fecframe@ietf.org
> https://www1.ietf.org/mailman/listinfo/fecframe


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



From mmusic-bounces@ietf.org Fri May 11 07:51:18 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmTeV-0000Ms-KL; Fri, 11 May 2007 07:51:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmTeU-0000Mn-Sv
	for mmusic@ietf.org; Fri, 11 May 2007 07:51:14 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmTeT-0005CN-Ji
	for mmusic@ietf.org; Fri, 11 May 2007 07:51:14 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59718)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HmTeT-0006AH-4z
	for mmusic@ietf.org; Fri, 11 May 2007 12:51:13 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <E1HhWSA-0002Qo-EV@stiedprstage1.ietf.org>
References: <E1HhWSA-0002Qo-EV@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1283BDA0-B2CF-45AD-9938-D44FA75AD34F@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-file-transfer-mech-01.txt 
Date: Fri, 11 May 2007 12:51:11 +0100
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

On 27 Apr 2007, at 20:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session  
> Control Working Group of the IETF.
>
> 	Title		: A Session Description Protocol (SDP) Offer/Answer  
> Mechanism to Enable File Transfer
> 	Author(s)	: M. Garcia-Martin, et al.
> 	Filename	: draft-ietf-mmusic-file-transfer-mech-01.txt
> 	Pages		: 38
> 	Date		: 2007-4-27

One issue which still concerns me about this draft is that it spreads  
new values all over the SDP attribute namespace. Looking at section  
11.1, we see the following registrations:

file-sector        (should be file-selector, I assume?)
disposition
file-date
icon
file-range

How feasible would it be to rename the "disposition" and "icon"  
attributes to have a "file-" prefix (allowing for others types of  
icons, or the disposition of things other than files, in future)?

Colin

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



From mmusic-bounces@ietf.org Fri May 11 08:32:45 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmUIe-0002Lu-Tw; Fri, 11 May 2007 08:32:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmUId-0002Ll-4O
	for mmusic@ietf.org; Fri, 11 May 2007 08:32:43 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmUIb-0002u9-R8
	for mmusic@ietf.org; Fri, 11 May 2007 08:32:43 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:59838)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HmUIb-0005CY-B6
	for mmusic@ietf.org; Fri, 11 May 2007 13:32:41 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: mmusic@ietf.org
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 11 May 2007 13:32:39 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [MMUSIC] IPR statement on draft-ietf-mmusic-ice-15.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

The secretariat informs us that updated IPR disclosures have been  
submitted pertaining to ICE (These were submitted on 13th April -  
apologies for the delayed notification):

https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=838
https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=839
https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=840

Colin (as chair)

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



From mmusic-bounces@ietf.org Fri May 11 13:16:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmYjT-0007xO-J2; Fri, 11 May 2007 13:16:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmYjS-0007ux-3m
	for mmusic@ietf.org; Fri, 11 May 2007 13:16:42 -0400
Received: from corp-fw-main.jabber.com ([207.182.164.14] helo=roundabout.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmYjP-0007va-J9
	for mmusic@ietf.org; Fri, 11 May 2007 13:16:42 -0400
Received: from roundabout.local (localhost [127.0.0.1])
	by roundabout.local (Postfix) with ESMTP id 25CDC6163C7;
	Fri, 11 May 2007 11:17:39 -0600 (MDT)
Message-ID: <4644A532.8090105@jabber.org>
Date: Fri, 11 May 2007 11:17:38 -0600
From: Peter Saint-Andre <stpeter@jabber.org>
Organization: XMPP Standards Foundation
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] IPR statement on draft-ietf-mmusic-ice-15.txt
References: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
In-Reply-To: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
Jabber-ID: stpeter@jabber.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1665659291=="
Errors-To: mmusic-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1665659291==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms010003060702040906090209"

This is a cryptographically signed message in MIME format.

--------------ms010003060702040906090209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Colin Perkins wrote:
> The secretariat informs us that updated IPR disclosures have been 
> submitted pertaining to ICE (These were submitted on 13th April - 
> apologies for the delayed notification):
> 
> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=838
> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=839
> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=840

What is the appropriate venue to discuss these disclosures? Seeing none, 
I reply on the MMUSIC list.

The patent holder states that it shall grant licenses "on reasonable 
terms and conditions", but the terms and conditions are not defined. 
Therefore this is merely a promissory note. A definition of the terms 
and conditions would be helpful.

The following text is an improvement over the original version:

    In addition, the Patent Holder grants a "free" license to any
    prospective licensee if such prospective licensee commits to
    license its own essential patent(s) or essential patent claim(s)
    (if any) for implementation of any IETF specification for "free".

The newly-added words "if any" are particularly helpful, since some 
entities (e.g., open-source projects) do not typically hold patents or 
make patent claims. Will such an entity need to explicitly register with 
or apply to the patent holder in order to obtain a license? What 
penalties will ensue if such an entity does not obtain a license?

The text does not define the procedure by which a prospective licensee 
can become a licensee. Is that procedure still to be defined? Presumably 
the procedure will include a mechanism by which the prospective licensee 
"commits to license its own essential patent(s) or essential patent 
claim(s) (if any) for implementation of any IETF specification for 
'free'". However, in the absence of a defined procedure it is difficult 
to know.

Given the strong and widespread interest in the NAT traversal 
technologies specified in draft-ietf-mmusic-ice, more clarity regarding 
the licensing terms, conditions, and procedures would be appreciated.

Thanks.

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


--------------ms010003060702040906090209
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIYVDCC
B3AwggbZoAMCAQICAQkwDQYJKoZIhvcNAQEEBQAwgbAxCzAJBgNVBAYTAklMMQ8wDQYDVQQI
EwZJc3JhZWwxDjAMBgNVBAcTBUVpbGF0MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMRowGAYD
VQQLExFDQSBBdXRob3JpdHkgRGVwLjEpMCcGA1UEAxMgRnJlZSBTU0wgQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzAeFw0wNTA0
MDUxNDUxMDNaFw0xMDA0MDQxNDUxMDNaMIGvMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNy
YWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2VydGlmaWNh
dGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVtYWlsIEZy
ZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAOOY75tn3YhiCOsNXQn9/4WfpNrX8HLIUlBTLrGtMINvcYJ0
3Nlr9kJyOF5Z8g+2G9Zg+zN8iWGBEpl37bgjYdea3q0AaO9uyZOMLa0rztjFeo7Uw8AjdDmW
kaJQU1c6q9OoieOT6Tf4MvHMGqtbnaOL3Xvz4o6XnH+Ek9h8zPgYgiUw2tIF0ueLayTGiInH
dWM5eYMoz7OnVlUeIurDweT4C9V1TtwplnhWZ7bilcuN4w3/8hndqryqqflbCMlLZWn+1uaT
21d12cdpjBOaqtg6hqiTY4S4+wVAmGrAiOPQ3Z574gljhUKf5ehz7p9xtsb+mjvM1I4yPP8/
vjKZoRUCAwEAAaOCBBMwggQPMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgHmMB0GA1Ud
DgQWBBS4Zr17owi6irSy+USIcU+li0GzUTCB3QYDVR0jBIHVMIHSgBQcicOWzL3+MtUNjIEx
tpidjShkjaGBtqSBszCBsDELMAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEOMAwGA1UE
BxMFRWlsYXQxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xGjAYBgNVBAsTEUNBIEF1dGhvcml0
eSBEZXAuMSkwJwYDVQQDEyBGcmVlIFNTTCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEhMB8G
CSqGSIb3DQEJARYSYWRtaW5Ac3RhcnRjb20ub3JnggEAMB0GA1UdEQQWMBSBEmFkbWluQHN0
YXJ0Y29tLm9yZzAdBgNVHRIEFjAUgRJhZG1pbkBzdGFydGNvbS5vcmcwYgYDVR0fBFswWTAp
oCegJYYjaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NhLWNybC5jcmwwLKAqoCiGJmh0dHA6
Ly9jcmwuc3RhcnRjb20ub3JnL2NybC9jYS1jcmwuY3JsMIIBSgYDVR0gBIIBQTCCAT0wggE5
BgsrBgEEAYG1NwEBATCCASgwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9y
Zy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvaW50
ZXJtZWRpYXRlLnBkZjCBvQYIKwYBBQUHAgIwgbAwFBYNU3RhcnRDb20gTHRkLjADAgEBGoGX
TGltaXRlZCBMaWFiaWxpdHksIHJlYWQgdGhlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25z
KiBvZiB0aGUgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWls
YWJsZSBhdCBodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjARBglghkgBhvhC
AQEEBAMCAAcwUAYJYIZIAYb4QgENBEMWQVN0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRl
cm1lZGlhdGUgRnJlZSBTU0wgRW1haWwgQ2VydGlmaWNhdGVzMDIGCWCGSAGG+EIBBAQlFiNo
dHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDAzBglghkgBhvhCAQMEJhYkaHR0
cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydC1jcmwuY3JsMDIGCWCGSAGG+EIBCAQlFiNodHRw
Oi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjANBgkqhkiG9w0BAQQFAAOBgQDss9KK
Fx/bCifYjAQTmBtRoHFsdR5ZQ1nlagXKoyJ+IwmdGdiYqAKeaDfjT6bTXHfQvK8kp5xSoz0I
PcpSwztY7UKtylgJwplu1q6vjj4BGB621sD60qzirAhLSqxmpBgjl8HMMMoiM28DCLsshihl
g7wG7Oi/rPIuR8dawiaDejCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STGCBCwwggQoAgEBMIG3MIGvMQswCQYDVQQGEwJJTDEPMA0GA1UE
CBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2Vy
dGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVt
YWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwIDAOhwMAkG
BSsOAwIaBQCgggJJMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X
DTA3MDUxMTE3MTczOFowIwYJKoZIhvcNAQkEMRYEFBlvt3nb8Ze4Rue9N02SwJZyZsClMFIG
CSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHIBgkrBgEEAYI3EAQxgbowgbcwga8xCzAJ
BgNVBAYTAklMMQ8wDQYDVQQIEwZJc3JhZWwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xIzAh
BgNVBAsTGlNlY3VyZSBDZXJ0aWZpY2F0ZSBTaWduaW5nMS8wLQYDVQQDEyZTdGFydENvbSBD
bGFzcyAyIFByaW1hcnkgRW1haWwgRnJlZSBDQTEhMB8GCSqGSIb3DQEJARYSYWRtaW5Ac3Rh
cnRjb20ub3JnAgMA6HAwgcoGCyqGSIb3DQEJEAILMYG6oIG3MIGvMQswCQYDVQQGEwJJTDEP
MA0GA1UECBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1
cmUgQ2VydGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmlt
YXJ5IEVtYWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwID
AOhwMA0GCSqGSIb3DQEBAQUABIIBACoen0PaGGuC6OgDdPbsqRvVW7w8S3c0dHPI7HAdneAc
xVUEgiX881F+YmJ8cjc/KW1K67VsI6HyIewrFbve3UdEDEbsaxR1TTN6ycTc4MsRzY7bX7yi
BRFiSKphsVgS5vD9TGpbuY44XEhGxrLaZf+uAz5yEPjp6ocDlysjAiPaFaS8fbIBEUNnsQ0b
b3p/P8q1olJS+YVjMyNwpuooc7Q6T/HlB0wv9pkmE4kkROEm6z59w7kb8q4RI8U59HR04qt+
PIfx/dx3qdVnGA1Dl2TMjOUrhxunrIKCsx/A3FXinjTq3292EN5RNn5ze5G6AleGo+EtWDk3
nw2mpN4vDMUAAAAAAAA=
--------------ms010003060702040906090209--


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

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

--===============1665659291==--




From mmusic-bounces@ietf.org Fri May 11 13:41:04 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmZ6y-0005Vu-TF; Fri, 11 May 2007 13:41:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmZ6x-0005Vo-Ar
	for mmusic@ietf.org; Fri, 11 May 2007 13:40:59 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmZ6w-0002EN-0z
	for mmusic@ietf.org; Fri, 11 May 2007 13:40:59 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:60606)
	by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42)
	id 1HmZ6v-0004Tf-LS; Fri, 11 May 2007 18:40:57 +0100
In-Reply-To: <4644A532.8090105@jabber.org>
References: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
	<4644A532.8090105@jabber.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <101253F9-6109-45E3-8FB2-BCA92D8EEB7A@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] IPR statement on draft-ietf-mmusic-ice-15.txt
Date: Fri, 11 May 2007 18:40:57 +0100
To: Peter Saint-Andre <stpeter@jabber.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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>
Errors-To: mmusic-bounces@ietf.org

On 11 May 2007, at 18:17, Peter Saint-Andre wrote:
> Colin Perkins wrote:
>> The secretariat informs us that updated IPR disclosures have been  
>> submitted pertaining to ICE (These were submitted on 13th April -  
>> apologies for the delayed notification):
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=838
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=839
>> https://datatracker.ietf.org/public/ipr_detail_show.cgi?ipr_id=840
>
> What is the appropriate venue to discuss these disclosures? Seeing  
> none, I reply on the MMUSIC list.

The MMUSIC list is the correct venue, since this is an MMUSIC working  
group draft.

Colin (as chair)

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



From mmusic-bounces@ietf.org Fri May 11 15:52:14 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hmb9u-00064e-QX; Fri, 11 May 2007 15:52:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hmb9Y-00057k-I6
	for mmusic@ietf.org; Fri, 11 May 2007 15:51:48 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hmb9X-0005Zc-4Y
	for mmusic@ietf.org; Fri, 11 May 2007 15:51:48 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 11 May 2007 12:51:46 -0700
X-IronPort-AV: i="4.14,523,1170662400"; d="scan'208"; a="213028:sNHT19302666"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l4BJpkxl000358; 
	Fri, 11 May 2007 12:51:46 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4BJpYVF010323;
	Fri, 11 May 2007 19:51:43 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 May 2007 12:51:26 -0700
Received: from [192.168.0.10] ([10.21.91.87]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 May 2007 12:51:25 -0700
In-Reply-To: <4644A532.8090105@jabber.org>
References: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
	<4644A532.8090105@jabber.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A17B0286-A6EE-4FD5-A1FD-7C1CDE12E0D9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] IPR statement on draft-ietf-mmusic-ice-15.txt
Date: Fri, 11 May 2007 12:51:19 -0700
To: Peter Saint-Andre <stpeter@jabber.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 11 May 2007 19:51:25.0612 (UTC)
	FILETIME=[C2223EC0:01C79405]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=625; t=1178913106;
	x=1179777106; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mbaugher@cisco.com;
	z=From:=20Mark=20Baugher=20<mbaugher@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20IPR=20statement=20on=20draft-ietf-mmusic-i
	ce-15.txt |Sender:=20;
	bh=kfjtjF2I5vhUjuSJLqAWd1BhtyuO1pqtdjnjRm+Nee4=;
	b=sVwS017hrMt8DJq9YDEUgdhbgVJa/7RQAfuX2vbNtz5AMyTFX6VXhk6NQjwFWlSSHD0OCbKU
	eZPZ2TS+McswKQxQ27mAJcso3RGQTG9T5GldDzTfJ4Ps72CqlWhR119w;
Authentication-Results: sj-dkim-5; header.From=mbaugher@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: 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>
Errors-To: mmusic-bounces@ietf.org


On May 11, 2007, at 10:17 AM, Peter Saint-Andre wrote:

>
> The newly-added words "if any" are particularly helpful, since some  
> entities (e.g., open-source projects) do not typically hold patents  
> or make patent claims. Will such an entity need to explicitly  
> register with or apply to the patent holder in order to obtain a  
> license? What penalties will ensue if such an entity does not  
> obtain a license?
>
I'm no lawyer, but I always understood this to mean that if you don't  
sue the patent holder than the patent holder won't sue you.  I always  
understood it to be that simple.

Mark

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



From mmusic-bounces@ietf.org Fri May 11 16:17:40 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmbYZ-0002eE-Cu; Fri, 11 May 2007 16:17:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmbYY-0002e9-Ka
	for mmusic@ietf.org; Fri, 11 May 2007 16:17:38 -0400
Received: from corp-fw-main.jabber.com ([207.182.164.14] helo=roundabout.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmbYX-0000CZ-62
	for mmusic@ietf.org; Fri, 11 May 2007 16:17:38 -0400
Received: from roundabout.local (localhost [127.0.0.1])
	by roundabout.local (Postfix) with ESMTP id B87E4616550;
	Fri, 11 May 2007 14:18:36 -0600 (MDT)
Message-ID: <4644CF9C.1000801@jabber.org>
Date: Fri, 11 May 2007 14:18:36 -0600
From: Peter Saint-Andre <stpeter@jabber.org>
Organization: XMPP Standards Foundation
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] IPR statement on draft-ietf-mmusic-ice-15.txt
References: <9BA5115B-3E75-4812-9EED-A1B0BC32A851@csperkins.org>
	<4644A532.8090105@jabber.org>
	<A17B0286-A6EE-4FD5-A1FD-7C1CDE12E0D9@cisco.com>
In-Reply-To: <A17B0286-A6EE-4FD5-A1FD-7C1CDE12E0D9@cisco.com>
Jabber-ID: stpeter@jabber.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Cc: 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>
Content-Type: multipart/mixed; boundary="===============1173481232=="
Errors-To: mmusic-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============1173481232==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms070701000408070405080506"

This is a cryptographically signed message in MIME format.

--------------ms070701000408070405080506
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mark Baugher wrote:
> 
> On May 11, 2007, at 10:17 AM, Peter Saint-Andre wrote:
> 
>>
>> The newly-added words "if any" are particularly helpful, since some 
>> entities (e.g., open-source projects) do not typically hold patents or 
>> make patent claims. Will such an entity need to explicitly register 
>> with or apply to the patent holder in order to obtain a license? What 
>> penalties will ensue if such an entity does not obtain a license?
>>
> I'm no lawyer, but I always understood this to mean that if you don't 
> sue the patent holder than the patent holder won't sue you.  I always 
> understood it to be that simple.

IANAL too. Your interpretation has common sense on its side, but common 
sense is not legally binding. To my suspicious mind, the phrase "X 
grants License A if Y commits to do B" might be construed to imply "X 
will grant License A only after Y has completed a legal agreement in 
which it promises to do B".

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


--------------ms070701000408070405080506
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIYVDCC
B3AwggbZoAMCAQICAQkwDQYJKoZIhvcNAQEEBQAwgbAxCzAJBgNVBAYTAklMMQ8wDQYDVQQI
EwZJc3JhZWwxDjAMBgNVBAcTBUVpbGF0MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMRowGAYD
VQQLExFDQSBBdXRob3JpdHkgRGVwLjEpMCcGA1UEAxMgRnJlZSBTU0wgQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzAeFw0wNTA0
MDUxNDUxMDNaFw0xMDA0MDQxNDUxMDNaMIGvMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNy
YWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2VydGlmaWNh
dGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVtYWlsIEZy
ZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAOOY75tn3YhiCOsNXQn9/4WfpNrX8HLIUlBTLrGtMINvcYJ0
3Nlr9kJyOF5Z8g+2G9Zg+zN8iWGBEpl37bgjYdea3q0AaO9uyZOMLa0rztjFeo7Uw8AjdDmW
kaJQU1c6q9OoieOT6Tf4MvHMGqtbnaOL3Xvz4o6XnH+Ek9h8zPgYgiUw2tIF0ueLayTGiInH
dWM5eYMoz7OnVlUeIurDweT4C9V1TtwplnhWZ7bilcuN4w3/8hndqryqqflbCMlLZWn+1uaT
21d12cdpjBOaqtg6hqiTY4S4+wVAmGrAiOPQ3Z574gljhUKf5ehz7p9xtsb+mjvM1I4yPP8/
vjKZoRUCAwEAAaOCBBMwggQPMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgHmMB0GA1Ud
DgQWBBS4Zr17owi6irSy+USIcU+li0GzUTCB3QYDVR0jBIHVMIHSgBQcicOWzL3+MtUNjIEx
tpidjShkjaGBtqSBszCBsDELMAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEOMAwGA1UE
BxMFRWlsYXQxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xGjAYBgNVBAsTEUNBIEF1dGhvcml0
eSBEZXAuMSkwJwYDVQQDEyBGcmVlIFNTTCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEhMB8G
CSqGSIb3DQEJARYSYWRtaW5Ac3RhcnRjb20ub3JnggEAMB0GA1UdEQQWMBSBEmFkbWluQHN0
YXJ0Y29tLm9yZzAdBgNVHRIEFjAUgRJhZG1pbkBzdGFydGNvbS5vcmcwYgYDVR0fBFswWTAp
oCegJYYjaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NhLWNybC5jcmwwLKAqoCiGJmh0dHA6
Ly9jcmwuc3RhcnRjb20ub3JnL2NybC9jYS1jcmwuY3JsMIIBSgYDVR0gBIIBQTCCAT0wggE5
BgsrBgEEAYG1NwEBATCCASgwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9y
Zy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvaW50
ZXJtZWRpYXRlLnBkZjCBvQYIKwYBBQUHAgIwgbAwFBYNU3RhcnRDb20gTHRkLjADAgEBGoGX
TGltaXRlZCBMaWFiaWxpdHksIHJlYWQgdGhlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25z
KiBvZiB0aGUgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWls
YWJsZSBhdCBodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjARBglghkgBhvhC
AQEEBAMCAAcwUAYJYIZIAYb4QgENBEMWQVN0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRl
cm1lZGlhdGUgRnJlZSBTU0wgRW1haWwgQ2VydGlmaWNhdGVzMDIGCWCGSAGG+EIBBAQlFiNo
dHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDAzBglghkgBhvhCAQMEJhYkaHR0
cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydC1jcmwuY3JsMDIGCWCGSAGG+EIBCAQlFiNodHRw
Oi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjANBgkqhkiG9w0BAQQFAAOBgQDss9KK
Fx/bCifYjAQTmBtRoHFsdR5ZQ1nlagXKoyJ+IwmdGdiYqAKeaDfjT6bTXHfQvK8kp5xSoz0I
PcpSwztY7UKtylgJwplu1q6vjj4BGB621sD60qzirAhLSqxmpBgjl8HMMMoiM28DCLsshihl
g7wG7Oi/rPIuR8dawiaDejCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzEL
MAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj
MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29t
IENsYXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBz
dGFydGNvbS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UE
BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBT
b2Z0d2FyZSBGb3VuZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZp
Y2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkB
FhJzdHBldGVyQGphYmJlci5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCr
zNmM5bxrSxV81PynU608wdGBJaKs0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6Koz
XDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZz
BHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd
0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVu
bA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQpAgMBAAGjggR+MIIEejAM
BgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUwgdKAFLhmvXuj
CLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs
MQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMRQ0Eg
QXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3
MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh
cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQu
MAMCAQEagY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGlt
aXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFi
bGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAs
oCqgKIYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0
dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3
BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9j
YTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNl
ci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBB
dXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8v
Y2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhCAQMEKBYmaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEIBCUWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6Ly9jZXJ0LnN0
YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+613ejmlb
DG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4bxJn
0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh
BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKM
LTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ
uYJCLgc0S5jgHntNU6X/STGCBCwwggQoAgEBMIG3MIGvMQswCQYDVQQGEwJJTDEPMA0GA1UE
CBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2Vy
dGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVt
YWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwIDAOhwMAkG
BSsOAwIaBQCgggJJMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X
DTA3MDUxMTIwMTgzNlowIwYJKoZIhvcNAQkEMRYEFPoW+oe3j/W3xXSz9i291MgF/sqsMFIG
CSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIHIBgkrBgEEAYI3EAQxgbowgbcwga8xCzAJ
BgNVBAYTAklMMQ8wDQYDVQQIEwZJc3JhZWwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xIzAh
BgNVBAsTGlNlY3VyZSBDZXJ0aWZpY2F0ZSBTaWduaW5nMS8wLQYDVQQDEyZTdGFydENvbSBD
bGFzcyAyIFByaW1hcnkgRW1haWwgRnJlZSBDQTEhMB8GCSqGSIb3DQEJARYSYWRtaW5Ac3Rh
cnRjb20ub3JnAgMA6HAwgcoGCyqGSIb3DQEJEAILMYG6oIG3MIGvMQswCQYDVQQGEwJJTDEP
MA0GA1UECBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1
cmUgQ2VydGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmlt
YXJ5IEVtYWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwID
AOhwMA0GCSqGSIb3DQEBAQUABIIBAH8f3z1tUSrp3ykjIR5nywVhQlUPRuWlv3cMBdI2MwTu
IQmgldnxLZ4Yu4Vkitt3qwQmhTid19MzHyN4zJrr7HZm4jFc5R1VoshGZugo5MY66bbSaxQM
Qqb8YAgyvRozpX6XErY3DmnZIhTYtQnRUoGRvT/rLqewsDTaOnuKN3UWOahycHcktI+KlMP/
2vgiI9rtoacsZqrNdTVnSfiz+e9LaM+51jcNYmA94M8XA3884ZLhX/ozjoOCfc7skaVu4M0k
2Htjsnd13PQfm7aSr6TyeM8i5kLmRULIk5hA5KpsWJIFkmofXJcu1Y351s5DLTrlWHCLtIs5
ONOQ+BtTDy4AAAAAAAA=
--------------ms070701000408070405080506--


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

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

--===============1173481232==--




From mmusic-bounces@ietf.org Sat May 12 17:36:47 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HmzGf-0005y0-Af; Sat, 12 May 2007 17:36:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HmzGe-0005xv-ED
	for mmusic@ietf.org; Sat, 12 May 2007 17:36:44 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmzGd-0003to-5k
	for mmusic@ietf.org; Sat, 12 May 2007 17:36:44 -0400
Received: from zcarhxs1.corp.nortel.com (zcarhxs1.corp.nortel.com
	[47.129.230.89])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l4CLadR18399; Sat, 12 May 2007 21:36:39 GMT
Received: from [47.130.24.184] ([47.130.24.184] RDNS failed) by
	zcarhxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 12 May 2007 17:36:38 -0400
Message-ID: <4646332E.2020003@nortel.com>
Date: Sat, 12 May 2007 17:35:42 -0400
From: "Tom-PT Taylor" <taylor@nortel.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: mmusic@ietf.org, Colin Perkins <csp@csperkins.org>,
	Roni Even <roni.even@polycom.co.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 May 2007 21:36:38.0973 (UTC)
	FILETIME=[9F9A6ED0:01C794DD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: 
Subject: [MMUSIC] draft-ietf-avt-rtp-and-rtcp-mux-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

The RTP/RTCP multiplexing draft has passed WGLC in AVT. It contains sections on 
how to negotiate multiplexing of RTP and RTCP on the same port, and on the 
relationship of this capability to ICE. Please have a look and report any 
concerns on the AVT list or to the AVT chairs.

Tom Taylor

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



From mmusic-bounces@ietf.org Mon May 14 08:53:37 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hna3T-0007Va-0R; Mon, 14 May 2007 08:53:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hna3S-0007VV-GW
	for mmusic@ietf.org; Mon, 14 May 2007 08:53:34 -0400
Received: from rvil-eframer.radvision.com ([80.74.106.104]
	helo=eframer.radvision.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hna3O-0006CX-PF
	for mmusic@ietf.org; Mon, 14 May 2007 08:53:34 -0400
Received: (from root@localhost)
	by eframer.radvision.com (8.13.4/8.12.9) id l4ECtjK2008394
	for mmusic@ietf.org; Mon, 14 May 2007 15:55:45 +0300
Received: from rvil-mail1.RADVISION.com (rvil-mail1.radvision.com
	[172.20.2.100])
	by eframer.radvision.com (8.13.4/8.12.9) with ESMTP id l4ECtZ4J008374; 
	Mon, 14 May 2007 15:55:35 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 May 2007 15:53:24 +0300
Message-ID: <C1CE9803A586A94C87AB380B61B5646D8B3D73@rvil-mail1.RADVISION.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: questions odraft-ietf-mmusic-ice-15.txt 
Thread-Index: AceWJtveQ+lq/c8TS+O7hbIp+RfiUg==
From: "Rafael Kiel" <rafael@radvision.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e654cfa5e44bd623be3eb2c720858b05
Cc: 
Subject: [MMUSIC] questions odraft-ietf-mmusic-ice-15.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1967996673=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1967996673==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C79626.DB2CBB51"

This is a multi-part message in MIME format.

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

Hi

I have two question regarding draft-ietf-mmusic-ice-15.txt

=20

1.	Chapter 15.1. ( "candidate" Attribute) says the following:

.. In that case, when receiving an offer or answer containing an FQDN
in an a=3Dcandidate attribute, the FQDN is looked up in the DNS using an =
A
or AAAA record, and the resulting IP address is used for the remainder
of ICE processing ...

=20

What should be done if the DNS look up results in more than address?
Does agent has to perform AAAA DNS request if the A request succeeds?=20

The implementation could create the remote candidate for each IPv4 and
IPv6 address learned as the result of DNS lookup or it can take one
arbitrary address. I believe it needs to be clarified.

=20

2.	Chapter 8.2.  (Updating States) says:

=20

If an In-Progress pair in the check list is for the same

=20

o  If there is at least one nominated pair in the valid list for a

      media stream and the state of the check list is Running:

=20

            ...

=20

      *  If an In-Progress pair in the check list is for the same

         component as a nominated pair, the agent SHOULD cease

         retransmissions for its check if its pair priority is lower

         than the lowest priority nominated pair for that component

=20

            ...

=20

Why an agent does not discard this check completely? If it succeeds the
pair will not be used since there exists another pair with higher
priority but letting this check to complete will require some
(superfluous) work to be done.

=20

Thanks,

            Rafi Kiel=20

            RADVISION

=20


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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1930192249;
	mso-list-type:hybrid;
	mso-list-template-ids:-560318918 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have two question regarding =
draft-ietf-mmusic-ice-15.txt<o:p></o:p></span></font></p>

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

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Chapter 15.1. ( =
&quot;candidate&quot;
     Attribute) says the following:<o:p></o:p></span></font></li>
</ol>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&#8230;</s=
pan></font>
</i><i><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
font-style:italic'>In that case, when receiving an offer or answer =
containing
an FQDN in an a=3Dcandidate attribute, the FQDN is looked up in the DNS =
using an
A or AAAA record, and the resulting IP address is used for the remainder =
of ICE
processing &#8230;<o:p></o:p></span></font></i></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>What should be done if the =
DNS look
up results in more than address? Does agent has to perform AAAA DNS =
request if
the A request succeeds? <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The implementation could =
create the
remote candidate for each IPv4 and IPv6 address learned as the result of =
DNS
lookup or it can take one arbitrary address. I believe it needs to be
clarified.<o:p></o:p></span></font></p>

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

<ol style=3D'margin-top:0in' start=3D2 type=3D1>
 <li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'><font size=3D2 =
face=3DArial><span
     style=3D'font-size:10.0pt;font-family:Arial'>Chapter 8.2.&nbsp; =
(Updating
     States) says:<o:p></o:p></span></font></li>
</ol>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>If an In-Progress pair in =
the check
list is for the same<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>o&nbsp; =
If there
is at least one nominated pair in the valid list for =
a<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
media stream and the state of the check list is =
Running:<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'><o:p>&nbsp=
;</o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&#8230;<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'><o:p>&nbsp=
;</o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
*&nbsp; If an In-Progress pair in the check list is for the =
same<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
component as a nominated pair, the agent SHOULD =
cease<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
retransmissions for its check if its pair priority is =
lower<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
than the lowest priority nominated pair for that =
component<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'><o:p>&nbsp=
;</o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'>&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&#8230;<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'><o:p>&nbsp=
;</o:p></span></font></i></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Why an agent does not =
discard this
check completely? If it succeeds the pair will not be used since there =
exists another
pair with higher priority but letting this check to complete will =
require some (superfluous)
work to be done.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Thanks,<o:p></o:p></span></f=
ont></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rafi
Kiel <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
RADVISION<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><i><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-style:italic'><o:p>&nbsp=
;</o:p></span></font></i></p>

</div>

</body>

</html>

------_=_NextPart_001_01C79626.DB2CBB51--


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

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

--===============1967996673==--




From mmusic-bounces@ietf.org Wed May 16 08:16:43 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HoIQs-0006An-38; Wed, 16 May 2007 08:16:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HoIQW-0005nJ-Gj
	for mmusic@ietf.org; Wed, 16 May 2007 08:16:20 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoIQV-0006IV-1L
	for mmusic@ietf.org; Wed, 16 May 2007 08:16:20 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4GCGBva026071; Wed, 16 May 2007 15:16:16 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 16 May 2007 15:16:07 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 16 May 2007 15:16:06 +0300
Received: from [172.21.58.33] ([172.21.58.33]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 16 May 2007 15:16:06 +0300
Message-ID: <464AF606.2070200@nsn.com>
Date: Wed, 16 May 2007 15:16:06 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] I-D ACTION:draft-ietf-mmusic-file-transfer-mech-01.txt
References: <E1HhWSA-0002Qo-EV@stiedprstage1.ietf.org>
	<1283BDA0-B2CF-45AD-9938-D44FA75AD34F@csperkins.org>
In-Reply-To: <1283BDA0-B2CF-45AD-9938-D44FA75AD34F@csperkins.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 May 2007 12:16:06.0570 (UTC)
	FILETIME=[FAC800A0:01C797B3]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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>
Errors-To: mmusic-bounces@ietf.org

Hi Colin:

I have no problems with your suggestion to rename these attributes.

Since I haven't heard any comments against it, I will rename these 
attributes in the next version of the draft.

/Miguel

Colin Perkins wrote:
> On 27 Apr 2007, at 20:50, Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control 
>> Working Group of the IETF.
>>
>>     Title        : A Session Description Protocol (SDP) Offer/Answer 
>> Mechanism to Enable File Transfer
>>     Author(s)    : M. Garcia-Martin, et al.
>>     Filename    : draft-ietf-mmusic-file-transfer-mech-01.txt
>>     Pages        : 38
>>     Date        : 2007-4-27
> 
> One issue which still concerns me about this draft is that it spreads 
> new values all over the SDP attribute namespace. Looking at section 
> 11.1, we see the following registrations:
> 
> file-sector        (should be file-selector, I assume?)
> disposition
> file-date
> icon
> file-range
> 
> How feasible would it be to rename the "disposition" and "icon" 
> attributes to have a "file-" prefix (allowing for others types of icons, 
> or the disposition of things other than files, in future)?
> 
> Colin
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Fri May 18 02:27:18 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hovvg-0002Kf-L9; Fri, 18 May 2007 02:27:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hovvf-0002KX-R4
	for mmusic@ietf.org; Fri, 18 May 2007 02:27:07 -0400
Received: from [217.205.209.100] (helo=vegastream.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hovvd-0001it-0y
	for mmusic@ietf.org; Fri, 18 May 2007 02:27:07 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC]  RFC 3264 offer/answer - multicast questions
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 18 May 2007 07:27:04 +0100
Message-ID: <8F1F2062CA7D754A838F0E66097D23A0C2433E@veg-brk-svr-pri.vegastream>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] I-D ACTION:draft-ietf-mmusic-file-transfer-mech-01.txt
Thread-Index: AceXtBvAcZuDMMrQRleU18pWIUkfHQBYUHPA
From: "Attila Sipos" <Attila.Sipos@vegastream.com>
To: <mmusic@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


(SIP-Implementors didn't come up with an answer.
 Maybe MMUSIC will...)


I have some questions on section 5.2:

5 Generating the Initial Offer
5.2 Multicast Streams

   If a session description contains a multicast media stream which is
   listed as receive (send) only, it means that the participants,
   including the offerer and answerer, can only receive (send) on that
   stream.  This differs from the unicast view, where the directionality
   refers to the flow of media between offerer and answerer.

I am confused about this.  It seems to say that if the offer has =
recvonly
then both the "offerer and answerer" can only receive on that port.

I am sure my interpretation is wrong -
what is the correct interpretation?

              =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=


Also regarding, "6.2 Multicast Streams", generating the answer, it seems
that if the offer was a multicast SDP, the answer has to be an almost =
identical
mulicast SDP.  Fine.  But what happens if the offer was unicast and the
desired answer is multicast?

For example, if you sent an INVITE to a server with unicast
but the server wanted to use multicast to send the same RTP to
everyone, can this happen?
Would there need to be anything special in the SDP?

              =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=


And who is allowed to send (say RTP) to a multicast IP address?
Surely it only makes sense that the server sends the multicasts
while the clients keep quiet.  ??

Regards,

	Attila


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



From mmusic-bounces@ietf.org Fri May 18 06:28:24 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hozh9-00069B-Bz; Fri, 18 May 2007 06:28:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hozh8-000696-Mo
	for mmusic@ietf.org; Fri, 18 May 2007 06:28:22 -0400
Received: from py-out-1112.google.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hozh6-0002F6-Cf
	for mmusic@ietf.org; Fri, 18 May 2007 06:28:22 -0400
Received: by py-out-1112.google.com with SMTP id f31so1090708pyh
	for <mmusic@ietf.org>; Fri, 18 May 2007 03:28:20 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=Onk7yXv+EewriwKdW0ss9OlBTKYsZ7TBzsJfmtwpLI1hIkoWzi4Zn6LjdUvBcjUXPQLeNkiK83sMYoE1+WDcbUaOk9iMENX8kGBfqXJi5z9BOQp1/6mvpgk1MC9meR9mhA4j4ywlufgJf564KvegJpclu09BnT1drdqGsKEAI8Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=oVr60MELMnngzhKnw8mqnFWgJ0oAVVB9k7pWGHBpWj1nyh/Ti6aF9TmAn8Gyfw2LZQ1rN59BTq8hQqCSwo0oz5Q/f4ZymsWFFyx9WbZ1PzSnyVNvxxEwyZDvu1zb7cfTkKpZx3Y2HdA1QAxP8EZ6OlG9tmJAqq6FJtoF8hMNMcQ=
Received: by 10.35.89.10 with SMTP id r10mr2544896pyl.1179484100090;
	Fri, 18 May 2007 03:28:20 -0700 (PDT)
Received: by 10.35.41.6 with HTTP; Fri, 18 May 2007 03:28:20 -0700 (PDT)
Message-ID: <f83cb47f0705180328k6d14c8a2s7564cf833536b074@mail.gmail.com>
Date: Fri, 18 May 2007 15:58:20 +0530
From: "Maruthi Ram namburu" <nmaruthiram@gmail.com>
To: mmusic@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [MMUSIC] Reg. RTSP SETUP request
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="===============0645970017=="
Errors-To: mmusic-bounces@ietf.org

--===============0645970017==
Content-Type: multipart/alternative; 
	boundary="----=_Part_21186_18644071.1179484100045"

------=_Part_21186_18644071.1179484100045
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

       In the RFC2326 the following is mentioned about the SETUP request

       "A client can issue a SETUP request for a stream that is already
playing to change transport parameters."

       Lets say that there is a NAT device between the client and server
which selectively opens up the ports and also does statistics collection. It
has to track the SETUP request and response to start natting the packets
flowing on the data stream.

      The following situation will arise when the NAT device sees a SETUP
request with a Session ID on the control connection.

       Case 1.  This new SETUP may be sent to change the transport
parameters of the existing data stream. In this case ports
  of the data stream  may change and NAT device may have to modify/cleanup
and recreate the datastructures it was using for the
 address translation so far.

       Case 2.  This new SETUP may be trying to aggregate another stream in
to the current session. In this case there
  will be a new additional datastream and NAT device has to create a new set
of datastructures to NAT the new datastream.

       From my understanding of the RFC I see that NAT device has to
remember the URL to differentiate these two cases.
  If the new SETUP carries the same URL then it is Case 1 otherwise it is
Case 2. But remebering the URL may turnout to
 be memory intensive for the NAT device which has to deal with large number
of connections.

  Is there any other way these two cases can be distiguished in NAT device ?

  In case if this is not the right forum for this discussion can you please
redirect me to the correct one ?

Thanks and Regards,
Maruthi

------=_Part_21186_18644071.1179484100045
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the RFC2326 the following is mentioned about the SETUP request <br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;A client can issue a SETUP request for a stream that is already playing to change transport parameters.&quot;<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lets say that there is a NAT device between the client and server which selectively opens up the ports and also does statistics collection. It has to track the SETUP request and response to start natting the packets flowing on the data stream.
<br><br>&nbsp; &nbsp; &nbsp; The following situation will arise when the NAT device sees a SETUP request with a Session ID on the control connection.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Case 1.&nbsp; This new SETUP may be sent to change the transport parameters of the existing data stream. In this case ports
<br>&nbsp; of the data stream&nbsp; may change and NAT device may have to modify/cleanup and recreate the datastructures it was using for the<br>&nbsp;address translation so far.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Case 2.&nbsp; This new SETUP may be trying to aggregate another stream in to the current session. In this case there
<br>&nbsp; will be a new additional datastream and NAT device has to create a new set of datastructures to NAT the new datastream.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From my understanding of the RFC I see that NAT device has to remember the URL to differentiate these two cases.
<br>&nbsp; If the new SETUP carries the same URL then it is Case 1 otherwise it is Case 2. But remebering the URL may turnout to<br>&nbsp;be memory intensive for the NAT device which has to deal with large number of connections.<br>
<br>&nbsp; Is there any other way these two cases can be distiguished in NAT device ?<br><br>&nbsp; In case if this is not the right forum for this discussion can you please redirect me to the correct one ?<br><br>Thanks and Regards,
<br>Maruthi<br>

------=_Part_21186_18644071.1179484100045--


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

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

--===============0645970017==--




From mmusic-bounces@ietf.org Fri May 18 09:04:40 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hp28K-0007BW-Gb; Fri, 18 May 2007 09:04:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp28I-0007BO-MW
	for mmusic@ietf.org; Fri, 18 May 2007 09:04:34 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hp28H-0002Gi-77
	for mmusic@ietf.org; Fri, 18 May 2007 09:04:34 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4ID4MoT016838 for <mmusic@ietf.org>; Fri, 18 May 2007 16:04:29 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 May 2007 16:04:06 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 May 2007 16:04:06 +0300
Received: from [172.21.59.31] ([172.21.59.31]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 May 2007 16:04:06 +0300
Message-ID: <464DA446.5020400@nsn.com>
Date: Fri, 18 May 2007 16:04:06 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 May 2007 13:04:06.0109 (UTC)
	FILETIME=[03F248D0:01C7994D]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [MMUSIC] File transfer verrsion -02
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

I have submitted version -02 of the file transfer draft.

Until it appears in the repository, you can fetch a copy from:

http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html

and a diff version:
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html

The changes in this version are:
- Rename of attributes:
   s/icon/file-icon
   s/disposition/file-disposition

- Fixed SDP in example in Section 9.3 to include mime types.

With this, I think the document is complete. I am not aware of any 
further open issues.

Regards,

     Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Fri May 18 12:33:07 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hp5O6-00017P-AQ; Fri, 18 May 2007 12:33:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp5O3-0000z0-AL
	for mmusic@ietf.org; Fri, 18 May 2007 12:33:03 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hp5O1-00037p-LD
	for mmusic@ietf.org; Fri, 18 May 2007 12:33:03 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-4.cisco.com with ESMTP; 18 May 2007 09:33:01 -0700
X-IronPort-AV: i="4.14,553,1170662400"; d="scan'208"; a="1470579:sNHT24768228"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l4IGX1cT027476; 
	Fri, 18 May 2007 09:33:01 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4IGWwVB003800;
	Fri, 18 May 2007 16:33:00 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 May 2007 12:33:00 -0400
Received: from [161.44.174.124] ([161.44.174.124]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 18 May 2007 12:33:00 -0400
Message-ID: <464DD53D.9060900@cisco.com>
Date: Fri, 18 May 2007 12:33:01 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
Subject: Re: [MMUSIC] File transfer verrsion -02
References: <464DA446.5020400@nsn.com>
In-Reply-To: <464DA446.5020400@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 May 2007 16:33:00.0131 (UTC)
	FILETIME=[32CE4330:01C7996A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5365; t=1179505981;
	x=1180369981; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20File=20transfer=20verrsion=20-02
	|Sender:=20; bh=RRwCFi/lrnMtn4jakSw2gQkjYSX5ARxxzBCTLgUwA80=;
	b=maMobsNvT2B9bgpY5d/4x2cfv7alWsvAGO2FzuXnxum7ZKtk20Wq+ZFSijj/alzbNCA/y1Lp
	8imHFedU2zsFLU2f5lJ1LjImBYhE9WAwcC/tqVebvjmOU1tJeg2O9S1K;
Authentication-Results: sj-dkim-8; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: mmusic <mmusic@ietf.org>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

This is looking pretty good - much improved over the last version I 
looked at. I have an assortment of comments, mostly nits or issues with 
wording:

Section 5:

    Specially in case the SDP offer is generated by the file receiver,
    the offer needs a mechanism to unambiguously identify the requested
    file.  For this purpose, the file transfer mechanism introduces the
    concept of a file selector, which is defined as the combination of
    the 4-tuple composed of the name, size, type, and hash of the file.
    We call each of these individual items a selector.

I find the above confusing. Is the selector the individual item, or the 
tuple of all the items? Also, is the combination always a 4-tuple, or 
may it have a subset of the items? If it may have a subset I guess it 
may still considered a 4-tuple that may contain null entries.

Section 6:

     file-icon-value      = cid-url        ;cid-url defined in RFC 2392

I don't really have a problem with the syntax, but this implies that 
there must be a multipart body. The use of SDP attributes rather than an 
external body was justified on the assumption that many UAs don't 
support multipart. There is an inconsistency here.

Section 7:

    To indicate that a file should be automatically rendered, this memo
    uses the existing 'render' value of the Content Disposition type in
    the new 'file-disposition' attribute in SDP.  To indicate that a file
    should not be automatically rendered, this memo defines a new value
    'not-render' of the Content Disposition type.  The default value is
    'render', i.e., the absence of a 'file-disposition' attribute in the
    SDP has the same semantics as 'render'.

The "not-render" disposition seems strange, because it is a negative. 
IMO something positive would be preferable - perhaps "storage" or 
"recipient-discretion".

Section 8.2.2:

    If the SDP offer included several
    'hash' parameters, the file sender SHOULD include at least one in the
    SDP answer, selected among those present in the offer and, at the
    same time, supported by the file sender.  If the SDP offer did not
    include a 'hash' parameter, the file sender SHOULD add one or more
    'hash' parameters, according to the supported hashing algorithms.

What should the file sender do if it supports multiple hash algorithms 
but the hashes supplied are not all consistent? Namely a file that 
matches one of them doesn't match the others. E.g. suppose the offer 
contained:

     a=file-selector:hash:sha-1:ABC hash:md5:DEF

and the matching file matches the sha-1 hash but not the md5 hash.

It could treat this as an error and reject the request, or it could 
treat this as ok as long as one of the hashes matches. The latter seems 
better. In that case, I think it should only return the hashes that 
actually match the file being returned. This does imply that if it 
supports multiple hashes then it needs to test the file against all of 
those supplied. Alternatively, perhaps it should only return those 
hashes that it has actually tested against the file being returned.

Section 8.4.  Re-usage of Existing m= Lines in SDP

    The SDP Offer/Answer Model [7] provides rules that allow SDP offerers
    and answerers to modify an existing media line, i.e., re-use an
    existing media line with different attributes.  The same is also
    possible when SDP signals a file transfer operation according to the
    rules of this memo.  Therefore, the procedures defined in RFC 3264
    [7], in particular those defined in Section 8.3, MUST apply for file
    transfer operations.

What does this mean? In other usage, a reinvite will cause another o/a 
exchange. In some cases the SDP is unchanged in this o/a and the result 
is that things remain as they are.

When using the procedures of this draft, if a new o/a exchange is made 
where there are no changes in the SDP, does it initiate a new transfer 
of the file that was previously exchanged? Or does it do nothing?

There will be cases following a file transfer when there is need to do 
another o/a without repeating the transfer. And there may also be cases 
when there is an explicit desire to repeat the transmission. (Maybe via 
other means it is known that the file has changed.)

Either the port must be set to zero in the subsequent o/a if 
retransmission is not desired, or else something must be changed (e.g. 
the msrp url) if retransmission is desired.

	That's it,
	Paul







Miguel Garcia wrote:
> I have submitted version -02 of the file transfer draft.
> 
> Until it appears in the repository, you can fetch a copy from:
> 
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt 
> 
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html 
> 
> 
> and a diff version:
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html 
> 
> 
> The changes in this version are:
> - Rename of attributes:
>   s/icon/file-icon
>   s/disposition/file-disposition
> 
> - Fixed SDP in example in Section 9.3 to include mime types.
> 
> With this, I think the document is complete. I am not aware of any 
> further open issues.
> 
> Regards,
> 
>     Miguel

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



From mmusic-bounces@ietf.org Fri May 18 15:50:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hp8Ss-0005go-6f; Fri, 18 May 2007 15:50:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hp8Sh-0005NI-4I; Fri, 18 May 2007 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hp8Sg-0006zi-Qo; Fri, 18 May 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 874DB26EE3;
	Fri, 18 May 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hp8Sg-0000RD-9b; Fri, 18 May 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Hp8Sg-0000RD-9b@stiedprstage1.ietf.org>
Date: Fri, 18 May 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-file-transfer-mech-02.txt 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

--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		: A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
	Author(s)	: M. Garcia-Martin, et al.
	Filename	: draft-ietf-mmusic-file-transfer-mech-02.txt
	Pages		: 38
	Date		: 2007-5-18
	
This document provides a mechanism to negotiate the transfer of one
   or more files between two endpoints by using the Session Description
   Protocol (SDP) offer/answer model specified in RFC 3264.  SDP is
   extended to describe the attributes of the files to be transferred.
   The offerer can either describe the files it wants to send, or the
   files it would like to receive.  The answerer can either accept or
   reject the offer separately for each individual file.  The transfer
   of one or more files is initiated after a successful negotiation.
   The Message Session Relay Protocol (MSRP) is defined as the default
   mechanism to actually carry the files between the endpoints.  The
   conventions on how to use MSRP for file transfer are also provided in
   this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-file-transfer-mech-02.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-file-transfer-mech-02.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-file-transfer-mech-02.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: <2007-5-18114706.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-file-transfer-mech-02.txt

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

Content-Type: text/plain
Content-ID: <2007-5-18114706.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From mmusic-bounces@ietf.org Sat May 19 06:05:45 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HpLok-0000wQ-5K; Sat, 19 May 2007 06:05:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HoHtC-0008Pv-RH
	for mmusic@ietf.org; Wed, 16 May 2007 07:41:54 -0400
Received: from web51403.mail.re2.yahoo.com ([206.190.38.182])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HoHtB-0008Nx-BJ
	for mmusic@ietf.org; Wed, 16 May 2007 07:41:54 -0400
Received: (qmail 47510 invoked by uid 60001); 16 May 2007 11:41:53 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=hp2lhm2cK+Mb8KXLidLkM9cF6Xg7vPHAE6UpqRtTogAaM5uQt88uvs12yPjiHNLRZVCYiBOBLZyn/IUKq2Bti0y8Hy7siYqLDZG1lMG3x52lEf/ax6Qn2UuJtkzJR8leT+a5quQYSSdfanr6Z3GbDkZ2SopIxDOe1/HOPJBcAD8=;
X-YMail-OSG: uGoTz4kVM1kMobTNFq9GDD5gn0.t.oAizcKLmRDmluBg8B2.J37Q9Dxaouf2_blOckVoB_g1av1lN4HIZf2G6LLYIzVslOMdaPVq0Sb_KsjapEzeK1IU3ZpztHl9WBCCX2tIgy5dtOwWD.1.xPEz89zcMQ--
Received: from [125.16.211.34] by web51403.mail.re2.yahoo.com via HTTP;
	Wed, 16 May 2007 04:41:53 PDT
X-Mailer: YahooMailRC/651.23 YahooMailWebService/0.7.41.10
Date: Wed, 16 May 2007 04:41:53 -0700 (PDT)
From: sudhakar an <sudhakar_aqua@yahoo.com>
To: mmusic@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-ID: <160660.47177.qm@web51403.mail.re2.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Sat, 19 May 2007 06:05:40 -0400
Subject: [MMUSIC] ABNF errors in draft-ietf-mmusic-file-transfer-mech-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>
Errors-To: mmusic-bounces@ietf.org

1)=0A    filename-selector    =3D "name:"  DQUOTE filename-string DQUOTE=0A=
                                        ; DQUOTE defined in RFC 4234=0A    =
filename-string      =3D byte-string ;byte-string defined in RFC 4566=0A =
=0AFrom rfc4566=0A   byte-string =3D         1*(%x01-09/%x0B-0C/%x0E-FF)=0A=
                         ;any byte except NUL, CR, or LF=0A =0AAs it can be=
 seen, the regular expression for byte-string would eat up the second DQUOT=
E and all subsequent character until CRLF. Possibly the draft needs to be m=
odified to mention that any DQUOTE appearing within byte=97string should be=
 escaped properly.=0A =0A2)=0A =0A   hash-selector        =3D "hash:" hash-=
algorithm ":" hash-value=0A    hash-algorithm       =3D token     ;see IANA=
 Hash Function=0A                                     ;Textual Names regist=
ry=0A    hash-value           =3D hex-val   ;hex-val defined in RFC 4234=0A=
 =0AFrom rfc4234=0A =0A        hex-val        =3D  "x" 1*HEXDIG=0A         =
                  [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]=0A =0AAll examples =
in draft-ietf-mmusic-file-transfer-mech-01.txt seem to show the hash select=
or like this=0A =0A    a=3Dfile-selector:name:"My cool picture.jpg" type:im=
age/jpeg=0A          size:32349 hash:sha-1:72245FE8653DDAF371362F86D471913E=
E4A2CE2E=0A =0APlease remove the ambiguity in specifying hash selector=0A =
=0AThanks =0ASudhakar=0A=0A=0A =0A_________________________________________=
___________________________________________=0ABe a PS3 game guru.=0AGet you=
r game face on with the latest PS3 news and previews at Yahoo! Games.=0Ahtt=
p://videogames.yahoo.com/platform?platform=3D120121

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



From mmusic-bounces@ietf.org Sun May 20 14:42:59 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HpqMl-0003td-6d; Sun, 20 May 2007 14:42:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HpqMk-0003tY-EX
	for mmusic@ietf.org; Sun, 20 May 2007 14:42:50 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HpqMj-0002B3-6B
	for mmusic@ietf.org; Sun, 20 May 2007 14:42:50 -0400
Received: by ug-out-1314.google.com with SMTP id 72so725379ugd
	for <mmusic@ietf.org>; Sun, 20 May 2007 11:42:48 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=XYmlESaygbv1tDH7B9zPhSFYi9Wz0UhN7xZt6l0z93ttFBB5ml+lRVeKvBlqsXytPz9lgyCwXmIlCvVqUWngrL8JBvUNTb0gmd0Opug2d2bWhNYZDpaoaILcnrKtdyY3SK+vVFCLaGRrhEr5qGRwHcVZ31tXNZqotYl1J6RtdKI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=R4diPq4/4dF+eA5FgK5hU7G71ZrAcjOG2u5ocqGyo8b8pF9jECRtE0zEUx+Gu2maRhlqo9C1Co+G0VTPucrGducH8ZQAkB5iEUXBHyNDfn9cBayAyuCkYZmqmwfMZ6ZgA9X6IfZyp+fIAuvACmhFCD0PQYIRUqKfA/h2VtqYweM=
Received: by 10.78.201.10 with SMTP id y10mr937585huf.1179686568412;
	Sun, 20 May 2007 11:42:48 -0700 (PDT)
Received: by 10.78.200.7 with HTTP; Sun, 20 May 2007 11:42:48 -0700 (PDT)
Message-ID: <4d0605c20705201142q354644f4v8524dd4928a748b@mail.gmail.com>
Date: Sun, 20 May 2007 11:42:48 -0700
From: "Joseph Pallas" <pallas@cs.stanford.edu>
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Reg. RTSP SETUP request
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: 0f91f9d1b7689638
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Maruthi asked about how a firewall/ALG might tell the difference
between in-session SETUP for aggregation and in-session SETUP for new
transport parameters:

> From my understanding of the RFC I see that NAT device has to remember the URL to differentiate these two cases.

How to distinguish between these two cases invites a more basic
question:  Does any implementation actually support changing the
transport stream parameters in mid-session?  And is SETUP really the
best way to do that?

I'm frankly skeptical about changing transports without a new session.
 What are the benefits of including that in the protocol?

joe

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



From mmusic-bounces@ietf.org Mon May 21 05:12:56 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq3wi-0006UT-RI; Mon, 21 May 2007 05:12:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq3wh-0006UL-OB
	for mmusic@ietf.org; Mon, 21 May 2007 05:12:51 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq3wg-0002WN-UC
	for mmusic@ietf.org; Mon, 21 May 2007 05:12:51 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	426672082E; Mon, 21 May 2007 11:12:48 +0200 (CEST)
X-AuditID: c1b4fb3c-a84eabb0000073d5-51-46516290bf16 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	38FAE207E9; Mon, 21 May 2007 11:12:48 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 11:12:48 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 11:12:47 +0200
Message-ID: <4651628F.6000405@ericsson.com>
Date: Mon, 21 May 2007 11:12:47 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Maruthi Ram namburu <nmaruthiram@gmail.com>
Subject: Re: [MMUSIC] Reg. RTSP SETUP request
References: <f83cb47f0705180328k6d14c8a2s7564cf833536b074@mail.gmail.com>
In-Reply-To: <f83cb47f0705180328k6d14c8a2s7564cf833536b074@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 09:12:47.0789 (UTC)
	FILETIME=[330FF5D0:01C79B88]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
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>
Errors-To: mmusic-bounces@ietf.org

Maruthi Ram namburu skrev:
> Hello,
> 
>        In the RFC2326 the following is mentioned about the SETUP request
> 
>        "A client can issue a SETUP request for a stream that is already 
> playing to change transport parameters."
> 
>        Lets say that there is a NAT device between the client and server 
> which selectively opens up the ports and also does statistics 
> collection. It has to track the SETUP request and response to start 
> natting the packets flowing on the data stream.
> 
>       The following situation will arise when the NAT device sees a 
> SETUP request with a Session ID on the control connection.
> 
>        Case 1.  This new SETUP may be sent to change the transport 
> parameters of the existing data stream. In this case ports
>   of the data stream  may change and NAT device may have to 
> modify/cleanup and recreate the datastructures it was using for the
>  address translation so far.
> 
>        Case 2.  This new SETUP may be trying to aggregate another stream 
> in to the current session. In this case there
>   will be a new additional datastream and NAT device has to create a new 
> set of datastructures to NAT the new datastream.
> 
>        From my understanding of the RFC I see that NAT device has to 
> remember the URL to differentiate these two cases.
>   If the new SETUP carries the same URL then it is Case 1 otherwise it 
> is Case 2. But remebering the URL may turnout to
>  be memory intensive for the NAT device which has to deal with large 
> number of connections.

Your summary seems to be right. I think that is the price you have to 
pay for having an RTSP ALG function in your NAT.

> 
>   Is there any other way these two cases can be distiguished in NAT device ?

Not that I can think of.

> 
>   In case if this is not the right forum for this discussion can you 
> please redirect me to the correct one ?
> 

Yes, it is the right forum.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From mmusic-bounces@ietf.org Mon May 21 05:27:30 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq4Ar-0000kO-UZ; Mon, 21 May 2007 05:27:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq4Aq-0000kH-EO
	for mmusic@ietf.org; Mon, 21 May 2007 05:27:28 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq4Ap-0006SS-DT
	for mmusic@ietf.org; Mon, 21 May 2007 05:27:28 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	99D5E20072; Mon, 21 May 2007 11:27:26 +0200 (CEST)
X-AuditID: c1b4fb3e-ad9eabb0000061ca-78-465165fe68c8 
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7B1C320026; Mon, 21 May 2007 11:27:26 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 11:27:26 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 11:27:26 +0200
Message-ID: <465165FE.3020002@ericsson.com>
Date: Mon, 21 May 2007 11:27:26 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Joseph Pallas <pallas@cs.stanford.edu>
Subject: Re: [MMUSIC] Reg. RTSP SETUP request
References: <4d0605c20705201142q354644f4v8524dd4928a748b@mail.gmail.com>
In-Reply-To: <4d0605c20705201142q354644f4v8524dd4928a748b@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 09:27:26.0239 (UTC)
	FILETIME=[3EA8CAF0:01C79B8A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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>
Errors-To: mmusic-bounces@ietf.org

Joseph Pallas skrev:
> Maruthi asked about how a firewall/ALG might tell the difference
> between in-session SETUP for aggregation and in-session SETUP for new
> transport parameters:
> 
>> From my understanding of the RFC I see that NAT device has to remember 
>> the URL to differentiate these two cases.
> 
> How to distinguish between these two cases invites a more basic
> question:  Does any implementation actually support changing the
> transport stream parameters in mid-session?  And is SETUP really the
> best way to do that?
> 
> I'm frankly skeptical about changing transports without a new session.
> What are the benefits of including that in the protocol?
> 

Hi Joe,

This is an interesting question. Lets start with the motivation as I see 
it. There are a few different cases when changing the transport 
parameters makes sense.

1. Session portability. Looking at the home environment use cases of 
RTSP today, there are people proposing/using RTSP to move a session from 
the living room "TV" to the bedroom "TV". I haven't looked at how DLNA 
does this, but I wouldn't be surprised if they use RTSP.

2. Session survivability. If a client experience either some mobility 
event or other change of network attachment that affects what IP address 
it is using, SETUP can be used to move the session to new address.

3. NAT Traversal. There is one part which is very similar to 2. In case 
the NAT bindings are lost, there is likely need for updating your 
transport parameters to get the session working again. However, looking 
at the proposals on how to do standardized NAT traversal for RTSP using 
ICE. In this there is likely a need to promote a candidate to primary 
address usage after having found it.

But as you say these things could be accomplished creating a new 
session. However the issues here I think are three:

A. The churn on the media servers to setup new back end readers for the 
files and position things correctly.

B. The impression in the client's state regarding playout information.

C. The need to do a complete rebuffer and resynchronization for the 
media streams instead of simply continue with the available state.

If these are strong enough arguments for including the mechanism is to 
me the real question. To me it appears that the functionality has been 
little used prior but starts to see more use as usage of RTSP evolves 
into more advanced usages.

The reason the SETUP is used for changing these parameters is to not 
require ALGs, Proxies etc to read other methods that affect parameters 
that the SETUP has created the initial values for. This motivation is 
documented in RFC 2326. Can you please provide any arguments why it is a 
bad idea?

cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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



From mmusic-bounces@ietf.org Mon May 21 09:36:24 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq83e-0002vr-IQ; Mon, 21 May 2007 09:36:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq83a-0002vd-F5
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:15 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq83Y-0002ES-Sg
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:14 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDa059027082; Mon, 21 May 2007 16:36:07 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:35:58 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:35:57 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:35:52 +0300
Message-ID: <4651A038.3020303@nsn.com>
Date: Mon, 21 May 2007 16:35:52 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [MMUSIC] File transfer verrsion -02
References: <464DA446.5020400@nsn.com> <464DD53D.9060900@cisco.com>
In-Reply-To: <464DD53D.9060900@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:35:52.0885 (UTC)
	FILETIME=[F3B67650:01C79BAC]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Paul:

Thanks for your comments. Rather than answering in a very long e-mail, I 
have decided to chunk your e-mail on a per issue basis. I will be 
posting each of them separately, along with an issue number. Keep tuned.

/Miguel

Paul Kyzivat wrote:
> This is looking pretty good - much improved over the last version I 
> looked at. I have an assortment of comments, mostly nits or issues with 
> wording:
> 
> Section 5:
> 
>    Specially in case the SDP offer is generated by the file receiver,
>    the offer needs a mechanism to unambiguously identify the requested
>    file.  For this purpose, the file transfer mechanism introduces the
>    concept of a file selector, which is defined as the combination of
>    the 4-tuple composed of the name, size, type, and hash of the file.
>    We call each of these individual items a selector.
> 
> I find the above confusing. Is the selector the individual item, or the 
> tuple of all the items? 
> 
> Section 6:
> 
>     file-icon-value      = cid-url        ;cid-url defined in RFC 2392
> 
> I don't really have a problem with the syntax, but this implies that 
> there must be a multipart body. The use of SDP attributes rather than an 
> external body was justified on the assumption that many UAs don't 
> support multipart. There is an inconsistency here.
> 
> Section 7:
> 
>    To indicate that a file should be automatically rendered, this memo
>    uses the existing 'render' value of the Content Disposition type in
>    the new 'file-disposition' attribute in SDP.  To indicate that a file
>    should not be automatically rendered, this memo defines a new value
>    'not-render' of the Content Disposition type.  The default value is
>    'render', i.e., the absence of a 'file-disposition' attribute in the
>    SDP has the same semantics as 'render'.
> 
> The "not-render" disposition seems strange, because it is a negative. 
> IMO something positive would be preferable - perhaps "storage" or 
> "recipient-discretion".
> 
> Section 8.2.2:
> 
>    If the SDP offer included several
>    'hash' parameters, the file sender SHOULD include at least one in the
>    SDP answer, selected among those present in the offer and, at the
>    same time, supported by the file sender.  If the SDP offer did not
>    include a 'hash' parameter, the file sender SHOULD add one or more
>    'hash' parameters, according to the supported hashing algorithms.
> 
> What should the file sender do if it supports multiple hash algorithms 
> but the hashes supplied are not all consistent? Namely a file that 
> matches one of them doesn't match the others. E.g. suppose the offer 
> contained:
> 
>     a=file-selector:hash:sha-1:ABC hash:md5:DEF
> 
> and the matching file matches the sha-1 hash but not the md5 hash.
> 
> It could treat this as an error and reject the request, 
> or it could 
> treat this as ok as long as one of the hashes matches. The latter seems 
> better. In that case, I think it should only return the hashes that 
> actually match the file being returned. This does imply that if it 
> supports multiple hashes then it needs to test the file against all of 
> those supplied. Alternatively, perhaps it should only return those 
> hashes that it has actually tested against the file being returned.
> 
> Section 8.4.  Re-usage of Existing m= Lines in SDP
> 
>    The SDP Offer/Answer Model [7] provides rules that allow SDP offerers
>    and answerers to modify an existing media line, i.e., re-use an
>    existing media line with different attributes.  The same is also
>    possible when SDP signals a file transfer operation according to the
>    rules of this memo.  Therefore, the procedures defined in RFC 3264
>    [7], in particular those defined in Section 8.3, MUST apply for file
>    transfer operations.
> 
> What does this mean? In other usage, a reinvite will cause another o/a 
> exchange. In some cases the SDP is unchanged in this o/a and the result 
> is that things remain as they are.
> 
> When using the procedures of this draft, if a new o/a exchange is made 
> where there are no changes in the SDP, does it initiate a new transfer 
> of the file that was previously exchanged? Or does it do nothing?
> 
> There will be cases following a file transfer when there is need to do 
> another o/a without repeating the transfer. And there may also be cases 
> when there is an explicit desire to repeat the transmission. (Maybe via 
> other means it is known that the file has changed.)
> 
> Either the port must be set to zero in the subsequent o/a if 
> retransmission is not desired, or else something must be changed (e.g. 
> the msrp url) if retransmission is desired.
> 
>     That's it,
>     Paul
> 
> 
> 
> 
> 
> 
> 
> Miguel Garcia wrote:
>> I have submitted version -02 of the file transfer draft.
>>
>> Until it appears in the repository, you can fetch a copy from:
>>
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt 
>>
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html 
>>
>>
>> and a diff version:
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html 
>>
>>
>> The changes in this version are:
>> - Rename of attributes:
>>   s/icon/file-icon
>>   s/disposition/file-disposition
>>
>> - Fixed SDP in example in Section 9.3 to include mime types.
>>
>> With this, I think the document is complete. I am not aware of any 
>> further open issues.
>>
>> Regards,
>>
>>     Miguel

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:36:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq843-000356-UH; Mon, 21 May 2007 09:36:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq841-000324-71
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:41 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq83z-0002IZ-OQ
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:41 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDaEiw012214; Mon, 21 May 2007 16:36:35 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:33 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:33 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:33 +0300
Message-ID: <4651A060.6000908@nsn.com>
Date: Mon, 21 May 2007 16:36:32 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:36:33.0134 (UTC)
	FILETIME=[0BB3F8E0:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: 
Subject: [MMUSIC] File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote:
 > Section 6:
 >
 >     file-icon-value      = cid-url        ;cid-url defined in RFC 2392
 >
 > I don't really have a problem with the syntax, but this implies that
 > there must be a multipart body. The use of SDP attributes rather than an
 > external body was justified on the assumption that many UAs don't
 > support multipart. There is an inconsistency here.

There are two issues here:
1) O/A exchange between two endpoints that implement this draft
2) O/A exchange when the file sender implements the draft but the file
receiver does not, and probably, does not implement multipart either.

With respect point 1) above: I think it is assumed that if you
implement this specification you HAVE to implement multipart. I have
added a new section about the file-icon to capture this. The current
text reads:

8.6.  Considerations with respect the 'file-icon' attribute

    This specification allows a file sender to include a small preview of
    an image file: an icon.  A 'file-icon' attribute contains a CID URL
    [5] that points to an additional body that contains the actual icon.
    Since the icon is sent as a separate body along the SDP body, the
    file sender has to use a MIME multipart/mixed body that contains an
    SDP body part and the icon body part.  Therefore, implementations
    according to this specification MUST implement the multipart/mix MIME
    type [3].

With respect point 2) above: If the file receiver gets a multipart
body, and it does not implement multipart, then it would reject (via
SIP, presumably) the request. I think in this case we should recommed
to remove the icon body and the multipart and re-try the request with
SDP only. So, I have added a new paragraph, below the above text:

    However, if the file sender sends a request that contains a
    multipart/mix MIME body that includes an SDP body part and an icon
    body part, and the file receiver does not support multipart MIME
    types, then the file receiver will reject, via a higher protocol
    mechanism (e.g., SIP), the request.  In this case, it is RECOMMENDED
    that the file sender removes the icon body part, creates a single SDP
    body (i.e., without multipart MIME) and re-tries the request again.
    This increases the chances of getting the SDP accepted at the file
    receiver (albeit the file receiver will not implement this
    specification, which mandates the implementation of multipart MIME
    bodies).

/Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:36:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq844-000382-GB; Mon, 21 May 2007 09:36:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq841-00032P-IF
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:41 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq840-0002Ib-3i
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:41 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDaJ0A018178; Mon, 21 May 2007 16:36:36 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:28 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:27 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:27 +0300
Message-ID: <4651A05A.8030401@nsn.com>
Date: Mon, 21 May 2007 16:36:26 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:36:27.0525 (UTC)
	FILETIME=[085C1B50:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: 
Subject: [MMUSIC] File-transfer issue 28: Minimum number of selectors in a
	file selector
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote:
 > Also, is the combination always a 4-tuple, or
 > may it have a subset of the items? If it may have a subset I guess it
 > may still considered a 4-tuple that may contain null entries.

The combination can contains any number of items. In a special case
(see example in Section 9.3) it can even contain 0 items. The syntax
is carefully designed to allow it. However, you are right that is not
explicitly said in the text. So I would add a sentence to clarify it.

/Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:36:47 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq846-0003Bc-Qr; Mon, 21 May 2007 09:36:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq844-00037P-6h
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:44 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq842-0002Ik-Om
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:44 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDa7s0017973; Mon, 21 May 2007 16:36:39 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:38 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:38 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:37 +0300
Message-ID: <4651A065.2080005@nsn.com>
Date: Mon, 21 May 2007 16:36:37 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:36:37.0916 (UTC)
	FILETIME=[0E8DA5C0:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: 
Subject: [MMUSIC] File-transfer issue 30: file disposition values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote:
 > Section 7:
 >
 >    To indicate that a file should be automatically rendered, this memo
 >    uses the existing 'render' value of the Content Disposition type in
 >    the new 'file-disposition' attribute in SDP.  To indicate that a file
 >    should not be automatically rendered, this memo defines a new value
 >    'not-render' of the Content Disposition type.  The default value is
 >    'render', i.e., the absence of a 'file-disposition' attribute in the
 >    SDP has the same semantics as 'render'.
 >
 > The "not-render" disposition seems strange, because it is a negative.
 > IMO something positive would be preferable - perhaps "storage" or
 > "recipient-discretion".

I am fine with the suggestion. I went to the IANA registry once more,
and evaluate the possibility of reusing an existing disposition type.

So, what about the "attachment" disposition type? Its definition in
RFC 2183 says:

    Bodyparts can be designated `attachment' to indicate that they are
    separate from the main body of the mail message, and that their
    display should not be automatic, but contingent upon some further
    action of the user.

I think it meets our requirements, so my proposal is to replace the
existing "not-render" by "attachment". Any views?


/Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:37:01 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq84L-0004AA-SN; Mon, 21 May 2007 09:37:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq84J-0003xh-AG
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:59 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq84H-0002K3-48
	for mmusic@ietf.org; Mon, 21 May 2007 09:36:59 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDaHgM027158; Mon, 21 May 2007 16:36:24 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:21 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:21 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:36:20 +0300
Message-ID: <4651A053.7000202@nsn.com>
Date: Mon, 21 May 2007 16:36:19 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:36:20.0275 (UTC)
	FILETIME=[0409D830:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
Subject: [MMUSIC] File-transfer issue 27: File selector terminology is
	confusing
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote:
 > This is looking pretty good - much improved over the last version I
 > looked at. I have an assortment of comments, mostly nits or issues with
 > wording:
 >
 > Section 5:
 >
 >    Specially in case the SDP offer is generated by the file receiver,
 >    the offer needs a mechanism to unambiguously identify the requested
 >    file.  For this purpose, the file transfer mechanism introduces the
 >    concept of a file selector, which is defined as the combination of
 >    the 4-tuple composed of the name, size, type, and hash of the file.
 >    We call each of these individual items a selector.
 >
 > I find the above confusing. Is the selector the individual item, or the
 > tuple of all the items?

I think the above text was clear: there is a file selector that can 
contain up to four individual "items" that describe the file. Those 
items are called selectors, but I don't mind the name, if you find it 
confusing, please suggest another one. So, to answer your question, each 
of the individual items is a selector.


/Miguel

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:37:17 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq84a-0004Ze-NT; Mon, 21 May 2007 09:37:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq84Z-0004ZZ-MJ
	for mmusic@ietf.org; Mon, 21 May 2007 09:37:15 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq84Z-0002LA-7C
	for mmusic@ietf.org; Mon, 21 May 2007 09:37:15 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDb5d1018792; Mon, 21 May 2007 16:37:11 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:10 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:10 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:10 +0300
Message-ID: <4651A086.8010900@nsn.com>
Date: Mon, 21 May 2007 16:37:10 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:37:10.0556 (UTC)
	FILETIME=[22021DC0:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: 
Subject: [MMUSIC] File-transfer issue 32: Re-send of the same file,
 vs. re-send of SDP only
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote
 > Section 8.4.  Re-usage of Existing m= Lines in SDP
 >
 >    The SDP Offer/Answer Model [7] provides rules that allow SDP offerers
 >    and answerers to modify an existing media line, i.e., re-use an
 >    existing media line with different attributes.  The same is also
 >    possible when SDP signals a file transfer operation according to the
 >    rules of this memo.  Therefore, the procedures defined in RFC 3264
 >    [7], in particular those defined in Section 8.3, MUST apply for file
 >    transfer operations.
 >
 > What does this mean? In other usage, a reinvite will cause another o/a
 > exchange. In some cases the SDP is unchanged in this o/a and the result
 > is that things remain as they are.
 >
 > When using the procedures of this draft, if a new o/a exchange is made
 > where there are no changes in the SDP, does it initiate a new transfer
 > of the file that was previously exchanged? Or does it do nothing?
 >
 > There will be cases following a file transfer when there is need to do
 > another o/a without repeating the transfer. And there may also be cases
 > when there is an explicit desire to repeat the transmission. (Maybe via
 > other means it is known that the file has changed.)
 >
 > Either the port must be set to zero in the subsequent o/a if
 > retransmission is not desired, or else something must be changed (e.g.
 > the msrp url) if retransmission is desired.


I think this is a good point. There are cases when the endpoint wants
to repeat the SDP, for example due to session timer, but does not want
to repeat the file transfer. This implies a copy of the previously
sent SDP without changes.

There are other cases where the sender wants to add additional media
streams to the session (not related to MSRP). In this case, the m=
line would be the same, especially if a file transfer is still going
on. But there would be additional m= lines. We don't want to repeat
the file transfer here either.

There are other cases where we want to repeat the file transfer,
perhaps because the hash computation failed, or because the user
accidentally deleted the file.

So, considering the use cases we have, and the discussion in
SIP/SIPPING of the service-ID, I would apply Jonathan's view: be
explicit in the signaling with what you ask. I would propose that we
create a new attribute, named 'file-transfer', which can take two
values: "new" (which is the default) and "existing". A file transfer
with the "new" attribute indicates the desire to do a new file
transfer, i.e., repeat it (if it was already done). A file transfer
with the "existing" attribute indicates that the file already exists
and we the file transfer should not take place. This approach was used
in the past with comedia and the management of TCP connections. Any
views?

/Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:37:42 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq850-0004gu-Gw; Mon, 21 May 2007 09:37:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq84y-0004gj-D6
	for mmusic@ietf.org; Mon, 21 May 2007 09:37:40 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq84x-0002Vx-Uh
	for mmusic@ietf.org; Mon, 21 May 2007 09:37:40 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LDbIko013106; Mon, 21 May 2007 16:37:22 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:06 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:05 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:37:05 +0300
Message-ID: <4651A081.8080608@nsn.com>
Date: Mon, 21 May 2007 16:37:05 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 13:37:05.0727 (UTC)
	FILETIME=[1F2144F0:01C79BAD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 
Subject: [MMUSIC] File-transfer issue 31: Errors when multiple hashes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Paul Kyzivat wrote:
 >
 > Section 8.2.2:
 >
 >    If the SDP offer included several
 >    'hash' parameters, the file sender SHOULD include at least one in the
 >    SDP answer, selected among those present in the offer and, at the
 >    same time, supported by the file sender.  If the SDP offer did not
 >    include a 'hash' parameter, the file sender SHOULD add one or more
 >    'hash' parameters, according to the supported hashing algorithms.
 >
 > What should the file sender do if it supports multiple hash algorithms
 > but the hashes supplied are not all consistent? Namely a file that
 > matches one of them doesn't match the others. E.g. suppose the offer
 > contained:
 >
 >     a=file-selector:hash:sha-1:ABC hash:md5:DEF
 >
 > and the matching file matches the sha-1 hash but not the md5 hash.
 >
 > It could treat this as an error and reject the request,

How can you reject the request due to a malformed hash, if you still
don't have the file? To calculate that the hash is correct, you need
to have the file, compute the hash over it (with an appropriate
algorithm) and then compare the obtained hash with the one that the
sender sent you in the SDP.

 > or it could
 > treat this as ok as long as one of the hashes matches. The latter seems
 > better. In that case, I think it should only return the hashes that
 > actually match the file being returned. This does imply that if it
 > supports multiple hashes then it needs to test the file against all of
 > those supplied. Alternatively, perhaps it should only return those
 > hashes that it has actually tested against the file being returned.

This is obviously an error case: if you implement several hashing
encoding algorithms, then each one should produce a correct output and
all should be consistent.

Thinking with an implementation mindset, I think this is the sequence
flow at the file receiver side. Once I have received the offer, I
would select ONE hash algorithm that I implement. I would use this one
to detect if I have already got the same file or not. If not, I will
create the SDP answer, get the file, and hash it with the same
algorithm that I selected to detect whether the file was received or
not. If the result matches the hash declared in the SDP, then fine. If
not, then I would deem it as a transmission error and inform the user
that the file is corrupted. I would never check another hashing
algorithm, even if supported.

Conclusion: once the file receiver selects a hashing algorithm, it is
like if only that algorithm has been sent in SDP. Do we agree with the
conclusion? Is there anything that needs to be added to the draft?

/Miguel
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 09:51:29 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq8IK-0005El-0D; Mon, 21 May 2007 09:51:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq8IH-0005Ee-Bj
	for mmusic@ietf.org; Mon, 21 May 2007 09:51:26 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq8IF-0004kM-Us
	for mmusic@ietf.org; Mon, 21 May 2007 09:51:25 -0400
Received: from epmmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JIE00I6Q95M3O@mailout2.samsung.com> for mmusic@ietf.org;
	Mon, 21 May 2007 22:51:22 +0900 (KST)
Received: from MAHESHALAPTOP ([107.108.70.26])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0JIE0008Z95K0F@mmp2.samsung.com> for
	mmusic@ietf.org; Mon, 21 May 2007 22:51:22 +0900 (KST)
Date: Mon, 21 May 2007 19:27:28 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
To: mmusic@ietf.org
Message-id: <007a01c79baf$f9555650$1a466c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <464DA446.5020400@nsn.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: [MMUSIC] Re: File transfer verrsion -02
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

hi Miguel,
A File  Receiver should be given the provision to indicate to the File
Sender as to
what is the maximum File size it is capable of receiving. This will be
especially
useful if the File Sneder does NOT provide the File-Size in the INVITE(SDP).

For this i suggest the following
"A Receiver MAY indicate the maximum size MSRP message(translates to max
File Size) that it wishes to
receive by including  the max-size a-line attribute in the SDP of
200OK(INVITE).
Max-size refers to the complete message in octets, not the size of any one
chunk.
Senders  SHALL NOT exceed the max-size limit for any message sent in the
resulting session".

regards
Mahesh


----- Original Message ----- 
From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
To: "mmusic" <mmusic@ietf.org>
Sent: Friday, May 18, 2007 6:34 PM
Subject: File transfer verrsion -02


> I have submitted version -02 of the file transfer draft.
>
> Until it appears in the repository, you can fetch a copy from:
>
>
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt
>
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html
>
> and a diff version:
>
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html
>
> The changes in this version are:
> - Rename of attributes:
>    s/icon/file-icon
>    s/disposition/file-disposition
>
> - Fixed SDP in example in Section 9.3 to include mime types.
>
> With this, I think the document is complete. I am not aware of any
> further open issues.
>
> Regards,
>
>      Miguel
> -- 
> Please note my new e-mail address: miguel.garcia at nsn.com
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Siemens Networks     Helsinki, Finland
>
>
>


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



From mmusic-bounces@ietf.org Mon May 21 10:09:10 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq8ZR-0008Ai-Bz; Mon, 21 May 2007 10:09:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq8ZM-00087g-NM
	for mmusic@ietf.org; Mon, 21 May 2007 10:09:06 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq8ZM-0008J5-7x
	for mmusic@ietf.org; Mon, 21 May 2007 10:09:04 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LE8uGN003541; Mon, 21 May 2007 17:09:02 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:08:56 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:08:56 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:08:56 +0300
Message-ID: <4651A7F8.9030507@nsn.com>
Date: Mon, 21 May 2007 17:08:56 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sudhakar an <sudhakar_aqua@yahoo.com>
Subject: Re: [MMUSIC] ABNF errors in
	draft-ietf-mmusic-file-transfer-mech-01.txt
References: <160660.47177.qm@web51403.mail.re2.yahoo.com>
In-Reply-To: <160660.47177.qm@web51403.mail.re2.yahoo.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-OriginalArrivalTime: 21 May 2007 14:08:56.0285 (UTC)
	FILETIME=[91E948D0:01C79BB1]
X-Nokia-AV: Clean
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext13.nokia.com id
	l4LE8uGN003541
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
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>
Errors-To: mmusic-bounces@ietf.org

Hi Sudhakar:

Thanks for your comments. See inline discussion:


sudhakar an wrote:
> 1)
>     filename-selector    =3D "name:"  DQUOTE filename-string DQUOTE
>                                         ; DQUOTE defined in RFC 4234
>     filename-string      =3D byte-string ;byte-string defined in RFC 45=
66
> =20
> From rfc4566
>    byte-string =3D         1*(%x01-09/%x0B-0C/%x0E-FF)
>                          ;any byte except NUL, CR, or LF
> =20
> As it can be seen, the regular expression for byte-string would eat up =
the second DQUOTE and all subsequent character until CRLF. Possibly the d=
raft needs to be modified to mention that any DQUOTE appearing within byt=
e=97string should be escaped properly.

I agree with you, we ought to say that if quotes are used they should be=20
escaped along other characters that we already mention.

So, I have modified the filename-string ABNF, which is now defined as:

    filename-string      =3D 1*(%x01-09/%x0B-0C/%x0E-21/%x23-FF)
                          ;any byte except NUL, CR, LF, or double quotes

And I have added the following sentence later in the description:

    If a file name contains double quotes, they MUST be percent-encoded.


> =20
> 2)
> =20
>    hash-selector        =3D "hash:" hash-algorithm ":" hash-value
>     hash-algorithm       =3D token     ;see IANA Hash Function
>                                      ;Textual Names registry
>     hash-value           =3D hex-val   ;hex-val defined in RFC 4234
> =20
> From rfc4234
> =20
>         hex-val        =3D  "x" 1*HEXDIG
>                            [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]
> =20
> All examples in draft-ietf-mmusic-file-transfer-mech-01.txt seem to sho=
w the hash selector like this
> =20
>     a=3Dfile-selector:name:"My cool picture.jpg" type:image/jpeg
>           size:32349 hash:sha-1:72245FE8653DDAF371362F86D471913EE4A2CE2=
E
> =20
> Please remove the ambiguity in specifying hash selector

I am not sure if I understood where the problem is. I was comparing the=20
ABNF and the example and to my knowledge, the example fits the ABNF. Can=20
you please elaborate?


> =20
> Thanks=20
> Sudhakar
>=20
>=20

Thanks for you review.

/Miguel
> =20
> _______________________________________________________________________=
_____________
> Be a PS3 game guru.
> Get your game face on with the latest PS3 news and previews at Yahoo! G=
ames.
> http://videogames.yahoo.com/platform?platform=3D120121
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
>=20

--=20
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 10:29:50 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq8tR-000326-EV; Mon, 21 May 2007 10:29:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq8tL-0002xr-Bh
	for mmusic@ietf.org; Mon, 21 May 2007 10:29:45 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq8tJ-0004ug-RT
	for mmusic@ietf.org; Mon, 21 May 2007 10:29:43 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LETW41011916; Mon, 21 May 2007 17:29:39 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:29:30 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:29:30 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 17:29:30 +0300
Message-ID: <4651ACCA.4090001@nsn.com>
Date: Mon, 21 May 2007 17:29:30 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [MMUSIC] Re: File transfer verrsion -02
References: <464DA446.5020400@nsn.com>
	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
In-Reply-To: <007a01c79baf$f9555650$1a466c6b@sisodomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 14:29:30.0542 (UTC)
	FILETIME=[7195F4E0:01C79BB4]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
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>
Errors-To: mmusic-bounces@ietf.org

Hi Mahesh:

Thanks for the comment.

I took a look at the vanilla MSRP draft 
(draft-ietf-simple-message-sessions) and it already offers a 'max-size' 
attribute with similar (mostly the same) semantics that you mention.

    An endpoint MAY indicate the maximum size message they wish to
    receive using the max-size a-line attribute.  Max-size refers to the
    complete message in octets, not the size of any one chunk.  Senders
    SHOULD NOT exceed the max-size limit for any message sent in the
    resulting session.  However, the receiver should consider max-size
    value as a hint.

The difference between MSRP max-size and your proposed max-file-size is 
that max-size comprises the CPIM overhead whereas max-file-size do not.

Honestly, I think the difference is on the order of hundreds of bytes at 
maximum. I think we shouldn't be defining a new attribute for it.
Which other view do we have on this one?

/Miguel




Mahesh Anjanappa wrote:
> hi Miguel,
> A File  Receiver should be given the provision to indicate to the File
> Sender as to
> what is the maximum File size it is capable of receiving. This will be
> especially
> useful if the File Sneder does NOT provide the File-Size in the INVITE(SDP).
> 
> For this i suggest the following
> "A Receiver MAY indicate the maximum size MSRP message(translates to max
> File Size) that it wishes to
> receive by including  the max-size a-line attribute in the SDP of
> 200OK(INVITE).
> Max-size refers to the complete message in octets, not the size of any one
> chunk.
> Senders  SHALL NOT exceed the max-size limit for any message sent in the
> resulting session".
> 
> regards
> Mahesh
> 
> 
> ----- Original Message ----- 
> From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
> To: "mmusic" <mmusic@ietf.org>
> Sent: Friday, May 18, 2007 6:34 PM
> Subject: File transfer verrsion -02
> 
> 
>> I have submitted version -02 of the file transfer draft.
>>
>> Until it appears in the repository, you can fetch a copy from:
>>
>>
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html
>> and a diff version:
>>
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html
>> The changes in this version are:
>> - Rename of attributes:
>>    s/icon/file-icon
>>    s/disposition/file-disposition
>>
>> - Fixed SDP in example in Section 9.3 to include mime types.
>>
>> With this, I think the document is complete. I am not aware of any
>> further open issues.
>>
>> Regards,
>>
>>      Miguel
>> -- 
>> Please note my new e-mail address: miguel.garcia at nsn.com
>> Miguel A. Garcia           tel:+358-50-4804586
>> Nokia Siemens Networks     Helsinki, Finland
>>
>>
>>
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 11:03:33 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hq9Q4-0007sm-Fc; Mon, 21 May 2007 11:03:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq9Pz-0007dJ-LD
	for mmusic@ietf.org; Mon, 21 May 2007 11:03:27 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq9Pz-0004UJ-4p
	for mmusic@ietf.org; Mon, 21 May 2007 11:03:27 -0400
Received: from epmmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JIE00JQ9CHPPF@mailout2.samsung.com> for mmusic@ietf.org;
	Tue, 22 May 2007 00:03:25 +0900 (KST)
Received: from MAHESHALAPTOP ([107.108.70.26])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0JIE00403CHOHK@mmp2.samsung.com> for
	mmusic@ietf.org; Tue, 22 May 2007 00:03:25 +0900 (KST)
Date: Mon, 21 May 2007 20:39:28 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [MMUSIC] Re: File transfer verrsion -02
To: Miguel Garcia <Miguel.Garcia@nsn.com>
Message-id: <009a01c79bba$079b7780$1a466c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <464DA446.5020400@nsn.com>
	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
	<4651ACCA.4090001@nsn.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
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>
Errors-To: mmusic-bounces@ietf.org

hi Miguel,
Actually , my Comment was with reference to the excerpt in MSRP draft
itself,
i dont intend to introduce a new attribute(i should have mentioned the MSRP
draft).
In MSRP draft, it does not enforce a "shall" for Senders to adhere to
max-size a-line attribute
value if the Receiver specified one.

But in File Transfer draft, i think it can be explicitly recommended to use
the max-size
a-line attribute and make it mandatory for Sender to adhere IF  the Receiver
specifies
a max-size.
It will be useful for File Transfer applications to refrain from sending
file sizes more than that
the Receiver can receive.

regards
Mahesh
----- Original Message ----- 
From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
To: "Mahesh Anjanappa" <mahesha@samsung.com>
Cc: <mmusic@ietf.org>
Sent: Monday, May 21, 2007 7:59 PM
Subject: Re: [MMUSIC] Re: File transfer verrsion -02


> Hi Mahesh:
>
> Thanks for the comment.
>
> I took a look at the vanilla MSRP draft
> (draft-ietf-simple-message-sessions) and it already offers a 'max-size'
> attribute with similar (mostly the same) semantics that you mention.
>
>     An endpoint MAY indicate the maximum size message they wish to
>     receive using the max-size a-line attribute.  Max-size refers to the
>     complete message in octets, not the size of any one chunk.  Senders
>     SHOULD NOT exceed the max-size limit for any message sent in the
>     resulting session.  However, the receiver should consider max-size
>     value as a hint.
>
> The difference between MSRP max-size and your proposed max-file-size is
> that max-size comprises the CPIM overhead whereas max-file-size do not.
>
> Honestly, I think the difference is on the order of hundreds of bytes at
> maximum. I think we shouldn't be defining a new attribute for it.
> Which other view do we have on this one?
>
> /Miguel
>
>
>
>
> Mahesh Anjanappa wrote:
> > hi Miguel,
> > A File  Receiver should be given the provision to indicate to the File
> > Sender as to
> > what is the maximum File size it is capable of receiving. This will be
> > especially
> > useful if the File Sneder does NOT provide the File-Size in the
INVITE(SDP).
> >
> > For this i suggest the following
> > "A Receiver MAY indicate the maximum size MSRP message(translates to max
> > File Size) that it wishes to
> > receive by including  the max-size a-line attribute in the SDP of
> > 200OK(INVITE).
> > Max-size refers to the complete message in octets, not the size of any
one
> > chunk.
> > Senders  SHALL NOT exceed the max-size limit for any message sent in the
> > resulting session".
> >
> > regards
> > Mahesh
> >
> >
> > ----- Original Message ----- 
> > From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
> > To: "mmusic" <mmusic@ietf.org>
> > Sent: Friday, May 18, 2007 6:34 PM
> > Subject: File transfer verrsion -02
> >
> >
> >> I have submitted version -02 of the file transfer draft.
> >>
> >> Until it appears in the repository, you can fetch a copy from:
> >>
> >>
> >
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt
> >
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html
> >> and a diff version:
> >>
> >
http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html
> >> The changes in this version are:
> >> - Rename of attributes:
> >>    s/icon/file-icon
> >>    s/disposition/file-disposition
> >>
> >> - Fixed SDP in example in Section 9.3 to include mime types.
> >>
> >> With this, I think the document is complete. I am not aware of any
> >> further open issues.
> >>
> >> Regards,
> >>
> >>      Miguel
> >> -- 
> >> Please note my new e-mail address: miguel.garcia at nsn.com
> >> Miguel A. Garcia           tel:+358-50-4804586
> >> Nokia Siemens Networks     Helsinki, Finland
> >>
> >>
> >>
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mmusic
> >
>
> -- 
> Please note my new e-mail address: miguel.garcia at nsn.com
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Siemens Networks     Helsinki, Finland
>
>
>


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



From mmusic-bounces@ietf.org Mon May 21 13:01:40 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqBGK-0005jr-Jl; Mon, 21 May 2007 13:01:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqBGI-0005jk-7C
	for mmusic@ietf.org; Mon, 21 May 2007 13:01:34 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqBGH-0003vS-UW
	for mmusic@ietf.org; Mon, 21 May 2007 13:01:34 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 May 2007 13:01:34 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="121649718:sNHT47002308"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4LH1XhJ003821; 
	Mon, 21 May 2007 13:01:33 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4LH1V5j006958; 
	Mon, 21 May 2007 17:01:33 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:01:19 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:01:19 -0400
Message-ID: <4651D05A.9080706@cisco.com>
Date: Mon, 21 May 2007 13:01:14 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A060.6000908@nsn.com>
In-Reply-To: <4651A060.6000908@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 17:01:19.0383 (UTC)
	FILETIME=[A6E0CA70:01C79BC9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2932; t=1179766893;
	x=1180630893; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2029=3A=20Multipart=20due=20to=
	20icon |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=NJjbgeAZtIPIWP5oKk1LT7Zb/hAiE5EKnJ7coxIS8p8=;
	b=Q9rVuOkdcRRzf23OPt3fE8vbq19XPfmi7wmqSmcdCI55UDMnC0bD0V+hZnui/f0pha43EIZa
	WA8CSwwSGIazRWmErNpZVtkZAoyG4TTDYeplf7xp4pDm/GkPTKUnAbUj;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Wouldn't the logic below, that explains the handling of the body for the 
icon, also allow the use of an external body for all the file attributes 
- contrary to the rationale for using sdp attributes rather than an 
external body?

(But I'm not going to give you a hard time on this.)

	Paul

Miguel Garcia wrote:
> Paul Kyzivat wrote:
>  > Section 6:
>  >
>  >     file-icon-value      = cid-url        ;cid-url defined in RFC 2392
>  >
>  > I don't really have a problem with the syntax, but this implies that
>  > there must be a multipart body. The use of SDP attributes rather than an
>  > external body was justified on the assumption that many UAs don't
>  > support multipart. There is an inconsistency here.
> 
> There are two issues here:
> 1) O/A exchange between two endpoints that implement this draft
> 2) O/A exchange when the file sender implements the draft but the file
> receiver does not, and probably, does not implement multipart either.
> 
> With respect point 1) above: I think it is assumed that if you
> implement this specification you HAVE to implement multipart. I have
> added a new section about the file-icon to capture this. The current
> text reads:
> 
> 8.6.  Considerations with respect the 'file-icon' attribute
> 
>    This specification allows a file sender to include a small preview of
>    an image file: an icon.  A 'file-icon' attribute contains a CID URL
>    [5] that points to an additional body that contains the actual icon.
>    Since the icon is sent as a separate body along the SDP body, the
>    file sender has to use a MIME multipart/mixed body that contains an
>    SDP body part and the icon body part.  Therefore, implementations
>    according to this specification MUST implement the multipart/mix MIME
>    type [3].
> 
> With respect point 2) above: If the file receiver gets a multipart
> body, and it does not implement multipart, then it would reject (via
> SIP, presumably) the request. I think in this case we should recommed
> to remove the icon body and the multipart and re-try the request with
> SDP only. So, I have added a new paragraph, below the above text:
> 
>    However, if the file sender sends a request that contains a
>    multipart/mix MIME body that includes an SDP body part and an icon
>    body part, and the file receiver does not support multipart MIME
>    types, then the file receiver will reject, via a higher protocol
>    mechanism (e.g., SIP), the request.  In this case, it is RECOMMENDED
>    that the file sender removes the icon body part, creates a single SDP
>    body (i.e., without multipart MIME) and re-tries the request again.
>    This increases the chances of getting the SDP accepted at the file
>    receiver (albeit the file receiver will not implement this
>    specification, which mandates the implementation of multipart MIME
>    bodies).
> 
> /Miguel

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



From mmusic-bounces@ietf.org Mon May 21 13:20:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqBYW-0000b6-G8; Mon, 21 May 2007 13:20:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqBYU-0000Zr-JK
	for mmusic@ietf.org; Mon, 21 May 2007 13:20:23 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqBYU-0000sR-9z
	for mmusic@ietf.org; Mon, 21 May 2007 13:20:22 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 May 2007 13:20:22 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="121651635:sNHT49079682"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4LHKMOx012622; 
	Mon, 21 May 2007 13:20:22 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l4LHKLBk004019; 
	Mon, 21 May 2007 17:20:21 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:20:17 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:20:17 -0400
Message-ID: <4651D4D0.3080105@cisco.com>
Date: Mon, 21 May 2007 13:20:16 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A065.2080005@nsn.com>
In-Reply-To: <4651A065.2080005@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 17:20:17.0527 (UTC)
	FILETIME=[4D43C870:01C79BCC]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3301; t=1179768022;
	x=1180632022; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2030=3A=20file=20disposition=20
	values |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=SChzeRo5GDFq+gjWnJdRgrVSEK4rKLRUTTnhmk5Gkzo=;
	b=BIgTXNZYKZB7QVtHyoIsHuHQS2ns6f0uKN4v4RwA1PCx+ODX3g10T2OfSZVBGoUt7J6FjLWW
	OiDx84xMSEnTjrpE0TYQYCEXm2AwO4GpliTDNu2DgmunpzIsVtt67Kc8;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 30: file disposition values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

I know this one is coming full circle, since I was the one who 
originally objected to "attachment". More inline.

	Paul


- In the file transfer

Miguel Garcia wrote:
> Paul Kyzivat wrote:
>  > Section 7:
>  >
>  >    To indicate that a file should be automatically rendered, this memo
>  >    uses the existing 'render' value of the Content Disposition type in
>  >    the new 'file-disposition' attribute in SDP.  To indicate that a file
>  >    should not be automatically rendered, this memo defines a new value
>  >    'not-render' of the Content Disposition type.  The default value is
>  >    'render', i.e., the absence of a 'file-disposition' attribute in the
>  >    SDP has the same semantics as 'render'.
>  >
>  > The "not-render" disposition seems strange, because it is a negative.
>  > IMO something positive would be preferable - perhaps "storage" or
>  > "recipient-discretion".
> 
> I am fine with the suggestion. I went to the IANA registry once more,
> and evaluate the possibility of reusing an existing disposition type.

I looked again too, and didn't find anything *clearly* applicable.

> So, what about the "attachment" disposition type? Its definition in
> RFC 2183 says:
> 
>    Bodyparts can be designated `attachment' to indicate that they are
>    separate from the main body of the mail message, and that their
>    display should not be automatic, but contingent upon some further
>    action of the user.

I do think that the kind of behavior you desire is somewhat similar to 
what happens for "attachment" with emails. But there are some 
significant differences:

- in the case of email, the message itself is typically stored, and the 
attachment stays with it by default. Typically it takes an overt action 
by the user to extract the attachment from the message and put it 
somewhere else. (I do think that "attachment" could be used in an MSRP 
stream as part of a multipart/mixed IM message. But that wouldn't be 
quite the semantics you are looking for.)

- When used as you are proposing, the above definition is problematic 
because there is no email message (nor an IM message) as the main body 
for this to be attached to.

New values that come to mind (more than before): "save", "store", "ask", 
"prompt", "storage".

(I'm not clear on what UI action is expected in this case. I'm imagining 
some sort of popup saying "You have a File" or something like that. If 
the sip session that contains this file transfer also has another MSRP 
session used for interactive IM, I guess the request could be 
interspersed with the display of IM messages. But if there was no IM 
session then that wouldn't work. I realize this could be done a lot of 
ways and we don't need to standardize them, but I'm just trying to have 
at least one workable use case in mind. The use case would help motivate 
naming a new disposition.)

At the end of the day, if you want to use "attachment", then as long as 
the draft has a clear description of how it is interpreted in this case, 
and how it differs from the registered definition, then I won't complain.

> I think it meets our requirements, so my proposal is to replace the
> existing "not-render" by "attachment". Any views?
> 
> 
> /Miguel

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



From mmusic-bounces@ietf.org Mon May 21 13:56:43 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqC7a-0005at-4H; Mon, 21 May 2007 13:56:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqC7Y-0005ao-Fn
	for mmusic@ietf.org; Mon, 21 May 2007 13:56:36 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqC7W-0008VK-U8
	for mmusic@ietf.org; Mon, 21 May 2007 13:56:36 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LHuW5S014010; Mon, 21 May 2007 20:56:32 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 20:56:32 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 20:56:32 +0300
Received: from [10.162.65.146] ([10.162.65.146]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 20:56:31 +0300
Message-ID: <4651DD4F.6050606@nsn.com>
Date: Mon, 21 May 2007 20:56:31 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [MMUSIC] Re: File transfer verrsion -02
References: <464DA446.5020400@nsn.com>
	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
	<4651ACCA.4090001@nsn.com>
	<009a01c79bba$079b7780$1a466c6b@sisodomain.com>
In-Reply-To: <009a01c79bba$079b7780$1a466c6b@sisodomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 17:56:31.0239 (UTC)
	FILETIME=[5CE5E970:01C79BD1]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
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>
Errors-To: mmusic-bounces@ietf.org

Hi Mahesh:

Ah, ok... So, if the comment is to refer to the max-size in MSRP, I 
think it is fine to mention something.

I have added the following paragraph to Section 8.5:

    The MSRP specification [13] defines a 'max-size' SDP attribute.  This
    attribute specifies the maximum number of octets of an MSRP message
    that the creator of the SDP is willing to receive (notice once more
    the definition of "MSRP message").  File receivers MAY add a 'max-
    size' attribute to the MSRP m= line that specifies the file,
    indicating the maximum number of octets of an MSRP message.  File
    senders MUST NOT exceed the 'max-size' limit for any message sent in
    the resulting session.

I hope this is OK.

/Miguel

Mahesh Anjanappa wrote:
> hi Miguel,
> Actually , my Comment was with reference to the excerpt in MSRP draft
> itself,
> i dont intend to introduce a new attribute(i should have mentioned the MSRP
> draft).
> In MSRP draft, it does not enforce a "shall" for Senders to adhere to
> max-size a-line attribute
> value if the Receiver specified one.
> 
> But in File Transfer draft, i think it can be explicitly recommended to use
> the max-size
> a-line attribute and make it mandatory for Sender to adhere IF  the Receiver
> specifies
> a max-size.
> It will be useful for File Transfer applications to refrain from sending
> file sizes more than that
> the Receiver can receive.
> 
> regards
> Mahesh
> ----- Original Message ----- 
> From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
> To: "Mahesh Anjanappa" <mahesha@samsung.com>
> Cc: <mmusic@ietf.org>
> Sent: Monday, May 21, 2007 7:59 PM
> Subject: Re: [MMUSIC] Re: File transfer verrsion -02
> 
> 
>> Hi Mahesh:
>>
>> Thanks for the comment.
>>
>> I took a look at the vanilla MSRP draft
>> (draft-ietf-simple-message-sessions) and it already offers a 'max-size'
>> attribute with similar (mostly the same) semantics that you mention.
>>
>>     An endpoint MAY indicate the maximum size message they wish to
>>     receive using the max-size a-line attribute.  Max-size refers to the
>>     complete message in octets, not the size of any one chunk.  Senders
>>     SHOULD NOT exceed the max-size limit for any message sent in the
>>     resulting session.  However, the receiver should consider max-size
>>     value as a hint.
>>
>> The difference between MSRP max-size and your proposed max-file-size is
>> that max-size comprises the CPIM overhead whereas max-file-size do not.
>>
>> Honestly, I think the difference is on the order of hundreds of bytes at
>> maximum. I think we shouldn't be defining a new attribute for it.
>> Which other view do we have on this one?
>>
>> /Miguel
>>
>>
>>
>>
>> Mahesh Anjanappa wrote:
>>> hi Miguel,
>>> A File  Receiver should be given the provision to indicate to the File
>>> Sender as to
>>> what is the maximum File size it is capable of receiving. This will be
>>> especially
>>> useful if the File Sneder does NOT provide the File-Size in the
> INVITE(SDP).
>>> For this i suggest the following
>>> "A Receiver MAY indicate the maximum size MSRP message(translates to max
>>> File Size) that it wishes to
>>> receive by including  the max-size a-line attribute in the SDP of
>>> 200OK(INVITE).
>>> Max-size refers to the complete message in octets, not the size of any
> one
>>> chunk.
>>> Senders  SHALL NOT exceed the max-size limit for any message sent in the
>>> resulting session".
>>>
>>> regards
>>> Mahesh
>>>
>>>
>>> ----- Original Message ----- 
>>> From: "Miguel Garcia" <Miguel.Garcia@nsn.com>
>>> To: "mmusic" <mmusic@ietf.org>
>>> Sent: Friday, May 18, 2007 6:34 PM
>>> Subject: File transfer verrsion -02
>>>
>>>
>>>> I have submitted version -02 of the file transfer draft.
>>>>
>>>> Until it appears in the repository, you can fetch a copy from:
>>>>
>>>>
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html
>>>> and a diff version:
>>>>
> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html
>>>> The changes in this version are:
>>>> - Rename of attributes:
>>>>    s/icon/file-icon
>>>>    s/disposition/file-disposition
>>>>
>>>> - Fixed SDP in example in Section 9.3 to include mime types.
>>>>
>>>> With this, I think the document is complete. I am not aware of any
>>>> further open issues.
>>>>
>>>> Regards,
>>>>
>>>>      Miguel
>>>> -- 
>>>> Please note my new e-mail address: miguel.garcia at nsn.com
>>>> Miguel A. Garcia           tel:+358-50-4804586
>>>> Nokia Siemens Networks     Helsinki, Finland
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>>
>> -- 
>> Please note my new e-mail address: miguel.garcia at nsn.com
>> Miguel A. Garcia           tel:+358-50-4804586
>> Nokia Siemens Networks     Helsinki, Finland
>>
>>
>>
> 

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 14:02:57 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqCDe-0000ey-8Q; Mon, 21 May 2007 14:02:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqCDd-0000db-CN
	for mmusic@ietf.org; Mon, 21 May 2007 14:02:53 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqCDa-0001hm-Qg
	for mmusic@ietf.org; Mon, 21 May 2007 14:02:53 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LI2goR018675; Mon, 21 May 2007 21:02:46 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:02:41 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:02:41 +0300
Received: from [10.162.65.146] ([10.162.65.146]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:02:40 +0300
Message-ID: <4651DEB9.6040908@nsn.com>
Date: Mon, 21 May 2007 21:02:33 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A060.6000908@nsn.com> <4651D05A.9080706@cisco.com>
In-Reply-To: <4651D05A.9080706@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 18:02:40.0920 (UTC)
	FILETIME=[393EC180:01C79BD2]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Paul:

The logic below explains the backward compatibility issues when one of 
the endpoints do not implement multipart.

What the logic below does not explain is what are the problems 
associated with B2BUAs and other nasty intermediary in the signaling 
path. Back some time ago, when Dan Wing proposed to use the external 
body, we became aware that some B2BUAS do nasty things to mutipart 
bodies (which I am not going to elaborate here). It was decided, in the 
sake of easy B2BUA traversal, to add these attributes rather than 
defining a message-external multipart body.

So I appreciate that you are not going to give me a hard time on this. 
We will stick to the decisions we took some time ago.

/Miguel

Paul Kyzivat wrote:
> Wouldn't the logic below, that explains the handling of the body for the 
> icon, also allow the use of an external body for all the file attributes 
> - contrary to the rationale for using sdp attributes rather than an 
> external body?
> 
> (But I'm not going to give you a hard time on this.)
> 
>     Paul
> 
> Miguel Garcia wrote:
>> Paul Kyzivat wrote:
>>  > Section 6:
>>  >
>>  >     file-icon-value      = cid-url        ;cid-url defined in RFC 2392
>>  >
>>  > I don't really have a problem with the syntax, but this implies that
>>  > there must be a multipart body. The use of SDP attributes rather 
>> than an
>>  > external body was justified on the assumption that many UAs don't
>>  > support multipart. There is an inconsistency here.
>>
>> There are two issues here:
>> 1) O/A exchange between two endpoints that implement this draft
>> 2) O/A exchange when the file sender implements the draft but the file
>> receiver does not, and probably, does not implement multipart either.
>>
>> With respect point 1) above: I think it is assumed that if you
>> implement this specification you HAVE to implement multipart. I have
>> added a new section about the file-icon to capture this. The current
>> text reads:
>>
>> 8.6.  Considerations with respect the 'file-icon' attribute
>>
>>    This specification allows a file sender to include a small preview of
>>    an image file: an icon.  A 'file-icon' attribute contains a CID URL
>>    [5] that points to an additional body that contains the actual icon.
>>    Since the icon is sent as a separate body along the SDP body, the
>>    file sender has to use a MIME multipart/mixed body that contains an
>>    SDP body part and the icon body part.  Therefore, implementations
>>    according to this specification MUST implement the multipart/mix MIME
>>    type [3].
>>
>> With respect point 2) above: If the file receiver gets a multipart
>> body, and it does not implement multipart, then it would reject (via
>> SIP, presumably) the request. I think in this case we should recommed
>> to remove the icon body and the multipart and re-try the request with
>> SDP only. So, I have added a new paragraph, below the above text:
>>
>>    However, if the file sender sends a request that contains a
>>    multipart/mix MIME body that includes an SDP body part and an icon
>>    body part, and the file receiver does not support multipart MIME
>>    types, then the file receiver will reject, via a higher protocol
>>    mechanism (e.g., SIP), the request.  In this case, it is RECOMMENDED
>>    that the file sender removes the icon body part, creates a single SDP
>>    body (i.e., without multipart MIME) and re-tries the request again.
>>    This increases the chances of getting the SDP accepted at the file
>>    receiver (albeit the file receiver will not implement this
>>    specification, which mandates the implementation of multipart MIME
>>    bodies).
>>
>> /Miguel

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 14:18:23 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqCSc-00020X-VJ; Mon, 21 May 2007 14:18:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqCSZ-00020O-Lv
	for mmusic@ietf.org; Mon, 21 May 2007 14:18:19 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqCSZ-0006fL-9B
	for mmusic@ietf.org; Mon, 21 May 2007 14:18:19 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 May 2007 14:18:19 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="60784934:sNHT49292820"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l4LIIJQH028119; 
	Mon, 21 May 2007 14:18:19 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4LII95v028668; 
	Mon, 21 May 2007 18:18:14 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 14:18:14 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 14:18:13 -0400
Message-ID: <4651E263.9010804@cisco.com>
Date: Mon, 21 May 2007 14:18:11 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A060.6000908@nsn.com> <4651D05A.9080706@cisco.com>
	<4651DEB9.6040908@nsn.com>
In-Reply-To: <4651DEB9.6040908@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 18:18:14.0021 (UTC)
	FILETIME=[656AAB50:01C79BD4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4177; t=1179771499;
	x=1180635499; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2029=3A=20Multipart=20due=20to=
	20icon |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=5J8Kh7pFzKJGEQEC+E3/acT0buNnJhnQY7q8IbGQF0A=;
	b=HQjZD6mtpVABJ8Mg2xazdZoyn+CO7e85T330041uD0NrWN+0RZgHuzHM7fGiV+70t7eFK7i8
	878adwAyzbaMfEZ28/iWb726UvdcEu5ObYx4Y1v+gPFMblzEcyVOotqg;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org



Miguel Garcia wrote:
> Hi Paul:
> 
> The logic below explains the backward compatibility issues when one of 
> the endpoints do not implement multipart.
> 
> What the logic below does not explain is what are the problems 
> associated with B2BUAs and other nasty intermediary in the signaling 
> path. Back some time ago, when Dan Wing proposed to use the external 
> body, we became aware that some B2BUAS do nasty things to mutipart 
> bodies (which I am not going to elaborate here). It was decided, in the 
> sake of easy B2BUA traversal, to add these attributes rather than 
> defining a message-external multipart body.

I'm still confused then, about how the problems with multipart for 
message-external arent' a problem for the mulipart for the icon. It 
seems like the same problems would apply to both, and the same solutions 
to those problems would apply to both.

What am I missing?

	Paul

> So I appreciate that you are not going to give me a hard time on this. 
> We will stick to the decisions we took some time ago.
> 
> /Miguel
> 
> Paul Kyzivat wrote:
>> Wouldn't the logic below, that explains the handling of the body for 
>> the icon, also allow the use of an external body for all the file 
>> attributes - contrary to the rationale for using sdp attributes rather 
>> than an external body?
>>
>> (But I'm not going to give you a hard time on this.)
>>
>>     Paul
>>
>> Miguel Garcia wrote:
>>> Paul Kyzivat wrote:
>>>  > Section 6:
>>>  >
>>>  >     file-icon-value      = cid-url        ;cid-url defined in RFC 
>>> 2392
>>>  >
>>>  > I don't really have a problem with the syntax, but this implies that
>>>  > there must be a multipart body. The use of SDP attributes rather 
>>> than an
>>>  > external body was justified on the assumption that many UAs don't
>>>  > support multipart. There is an inconsistency here.
>>>
>>> There are two issues here:
>>> 1) O/A exchange between two endpoints that implement this draft
>>> 2) O/A exchange when the file sender implements the draft but the file
>>> receiver does not, and probably, does not implement multipart either.
>>>
>>> With respect point 1) above: I think it is assumed that if you
>>> implement this specification you HAVE to implement multipart. I have
>>> added a new section about the file-icon to capture this. The current
>>> text reads:
>>>
>>> 8.6.  Considerations with respect the 'file-icon' attribute
>>>
>>>    This specification allows a file sender to include a small preview of
>>>    an image file: an icon.  A 'file-icon' attribute contains a CID URL
>>>    [5] that points to an additional body that contains the actual icon.
>>>    Since the icon is sent as a separate body along the SDP body, the
>>>    file sender has to use a MIME multipart/mixed body that contains an
>>>    SDP body part and the icon body part.  Therefore, implementations
>>>    according to this specification MUST implement the multipart/mix MIME
>>>    type [3].
>>>
>>> With respect point 2) above: If the file receiver gets a multipart
>>> body, and it does not implement multipart, then it would reject (via
>>> SIP, presumably) the request. I think in this case we should recommed
>>> to remove the icon body and the multipart and re-try the request with
>>> SDP only. So, I have added a new paragraph, below the above text:
>>>
>>>    However, if the file sender sends a request that contains a
>>>    multipart/mix MIME body that includes an SDP body part and an icon
>>>    body part, and the file receiver does not support multipart MIME
>>>    types, then the file receiver will reject, via a higher protocol
>>>    mechanism (e.g., SIP), the request.  In this case, it is RECOMMENDED
>>>    that the file sender removes the icon body part, creates a single SDP
>>>    body (i.e., without multipart MIME) and re-tries the request again.
>>>    This increases the chances of getting the SDP accepted at the file
>>>    receiver (albeit the file receiver will not implement this
>>>    specification, which mandates the implementation of multipart MIME
>>>    bodies).
>>>
>>> /Miguel
> 

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



From mmusic-bounces@ietf.org Mon May 21 14:41:51 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqCpK-0006Kx-VO; Mon, 21 May 2007 14:41:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqCpK-0006Ks-Iq
	for mmusic@ietf.org; Mon, 21 May 2007 14:41:50 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqCpK-0000gI-2w
	for mmusic@ietf.org; Mon, 21 May 2007 14:41:50 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LIfjkN015929; Mon, 21 May 2007 21:41:46 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:41:45 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:41:45 +0300
Received: from [10.162.65.146] ([10.162.65.146]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:41:45 +0300
Message-ID: <4651E7E8.2000503@nsn.com>
Date: Mon, 21 May 2007 21:41:44 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A065.2080005@nsn.com> <4651D4D0.3080105@cisco.com>
In-Reply-To: <4651D4D0.3080105@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 18:41:45.0171 (UTC)
	FILETIME=[AE871230:01C79BD7]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 30: file disposition values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Yeah, I remember that you objected to "attachment". The reason I am 
coming back to it is not because of the e-mail experience, but because 
of the definition of the "attachment" disposition in RFC 2183, which I 
copy here once more:

     Bodyparts can be designated `attachment' to indicate that they are
     separate from the main body of the mail message, and that their
     display should not be automatic, but contingent upon some further
     action of the user.

So, there are two aspects in the definition of "attachment":
a) what it indicates
b) how they are displayed

In file transfer, a) is different, because it does not indicate 
something separate from the main body of the mail message. However, b) 
is the same: "their display should not be automatic, but continget upon 
some further actions of the user."

I don't have a strong opinion to lean towards one or the other side. I 
just thought that if someone were checking the IANA table of registered 
disposition values, would ask what is the difference between 
"attachment" and "whatever-name-we-defined-for-file-transfer".

Do we have any other opinions who can guide us?

/Miguel


Paul Kyzivat wrote:
> I know this one is coming full circle, since I was the one who 
> originally objected to "attachment". More inline.
> 
>     Paul
> 
> 
> - In the file transfer
> 
> Miguel Garcia wrote:
>> Paul Kyzivat wrote:
>>  > Section 7:
>>  >
>>  >    To indicate that a file should be automatically rendered, this memo
>>  >    uses the existing 'render' value of the Content Disposition type in
>>  >    the new 'file-disposition' attribute in SDP.  To indicate that a 
>> file
>>  >    should not be automatically rendered, this memo defines a new value
>>  >    'not-render' of the Content Disposition type.  The default value is
>>  >    'render', i.e., the absence of a 'file-disposition' attribute in 
>> the
>>  >    SDP has the same semantics as 'render'.
>>  >
>>  > The "not-render" disposition seems strange, because it is a negative.
>>  > IMO something positive would be preferable - perhaps "storage" or
>>  > "recipient-discretion".
>>
>> I am fine with the suggestion. I went to the IANA registry once more,
>> and evaluate the possibility of reusing an existing disposition type.
> 
> I looked again too, and didn't find anything *clearly* applicable.
> 
>> So, what about the "attachment" disposition type? Its definition in
>> RFC 2183 says:
>>
>>    Bodyparts can be designated `attachment' to indicate that they are
>>    separate from the main body of the mail message, and that their
>>    display should not be automatic, but contingent upon some further
>>    action of the user.
> 
> I do think that the kind of behavior you desire is somewhat similar to 
> what happens for "attachment" with emails. But there are some 
> significant differences:
> 
> - in the case of email, the message itself is typically stored, and the 
> attachment stays with it by default. Typically it takes an overt action 
> by the user to extract the attachment from the message and put it 
> somewhere else. (I do think that "attachment" could be used in an MSRP 
> stream as part of a multipart/mixed IM message. But that wouldn't be 
> quite the semantics you are looking for.)
> 
> - When used as you are proposing, the above definition is problematic 
> because there is no email message (nor an IM message) as the main body 
> for this to be attached to.
> 
> New values that come to mind (more than before): "save", "store", "ask", 
> "prompt", "storage".
> 
> (I'm not clear on what UI action is expected in this case. I'm imagining 
> some sort of popup saying "You have a File" or something like that. If 
> the sip session that contains this file transfer also has another MSRP 
> session used for interactive IM, I guess the request could be 
> interspersed with the display of IM messages. But if there was no IM 
> session then that wouldn't work. I realize this could be done a lot of 
> ways and we don't need to standardize them, but I'm just trying to have 
> at least one workable use case in mind. The use case would help motivate 
> naming a new disposition.)
> 
> At the end of the day, if you want to use "attachment", then as long as 
> the draft has a clear description of how it is interpreted in this case, 
> and how it differs from the registered definition, then I won't complain.
> 
>> I think it meets our requirements, so my proposal is to replace the
>> existing "not-render" by "attachment". Any views?
>>
>>
>> /Miguel

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 14:47:10 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqCuQ-0001vt-Ju; Mon, 21 May 2007 14:47:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqCuP-0001vi-Jy
	for mmusic@ietf.org; Mon, 21 May 2007 14:47:05 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqCuN-0002Vl-5t
	for mmusic@ietf.org; Mon, 21 May 2007 14:47:05 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4LIktUJ011962; Mon, 21 May 2007 21:46:57 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:46:56 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:46:56 +0300
Received: from [10.162.65.146] ([10.162.65.146]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 21:46:55 +0300
Message-ID: <4651E91F.2060308@nsn.com>
Date: Mon, 21 May 2007 21:46:55 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A060.6000908@nsn.com> <4651D05A.9080706@cisco.com>
	<4651DEB9.6040908@nsn.com> <4651E263.9010804@cisco.com>
In-Reply-To: <4651E263.9010804@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 18:46:55.0681 (UTC)
	FILETIME=[679B2310:01C79BD8]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org



Paul Kyzivat wrote:

> 
> I'm still confused then, about how the problems with multipart for 
> message-external arent' a problem for the mulipart for the icon. It 
> seems like the same problems would apply to both, and the same solutions 
> to those problems would apply to both.
> 
> What am I missing?

What you are missing is the additional interoperability case we get with 
the current specification and that we wouldn't get with the 
message-external body. Let's assume both parties implement the file 
transfer spec, but there is a B2BUA that removes bodies that are not 
know or duly authorized.

- With the current specification, we get SDP O/A for file transfer, but 
if there are icon bodies, there will be removed. Things mostly work, 
only the icon fails to be displayed due to the B2BUA.

- With the message-external alternative, we don't get SDP O/A, we can 
just fall back to vanilla MSRP. User's wouldn't be able to see the file 
meta data and accept or reject a file based on that. They can still do a 
trial an error and send the file with vanilla MSRP, but no more.

/Miguel
> 
>     Paul
> 
-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Mon May 21 15:42:47 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqDmI-00017I-0S; Mon, 21 May 2007 15:42:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqDmG-00017D-VZ
	for mmusic@ietf.org; Mon, 21 May 2007 15:42:44 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqDmF-0004St-B9
	for mmusic@ietf.org; Mon, 21 May 2007 15:42:44 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 May 2007 15:42:43 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="60793090:sNHT61140616"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l4LJghRV001060; 
	Mon, 21 May 2007 15:42:43 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4LJgc5h019873; 
	Mon, 21 May 2007 19:42:42 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 15:42:36 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 15:42:35 -0400
Message-ID: <4651F62C.3090509@cisco.com>
Date: Mon, 21 May 2007 15:42:36 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A081.8080608@nsn.com>
In-Reply-To: <4651A081.8080608@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 19:42:35.0983 (UTC)
	FILETIME=[2E94C5F0:01C79BE0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6776; t=1179776563;
	x=1180640563; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2031=3A=20Errors=20when=20multi
	ple=20hashes |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=kGI9Cnd02JzAADOzSfgLEhTJrMWiiA7VXwJVSws1vLg=;
	b=Dn2C4zmfEhJeRDW6w/o2D/XZuiqv6JFdL322Z1Tgds1bKxuhDHUXSWpvkUuo08///SzwwPPX
	Ht+hipVElRUn3lwuG8YlXiyME6pgqap5Vk0JTlHvWXL2FkKp8alIDLRI;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 31: Errors when multiple hashes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Inline.

	Paul

Miguel Garcia wrote:
> Paul Kyzivat wrote:
>  >
>  > Section 8.2.2:
>  >
>  >    If the SDP offer included several
>  >    'hash' parameters, the file sender SHOULD include at least one in the
>  >    SDP answer, selected among those present in the offer and, at the
>  >    same time, supported by the file sender.  If the SDP offer did not
>  >    include a 'hash' parameter, the file sender SHOULD add one or more
>  >    'hash' parameters, according to the supported hashing algorithms.
>  >
>  > What should the file sender do if it supports multiple hash algorithms
>  > but the hashes supplied are not all consistent? Namely a file that
>  > matches one of them doesn't match the others. E.g. suppose the offer
>  > contained:
>  >
>  >     a=file-selector:hash:sha-1:ABC hash:md5:DEF
>  >
>  > and the matching file matches the sha-1 hash but not the md5 hash.
>  >
>  > It could treat this as an error and reject the request,
> 
> How can you reject the request due to a malformed hash, if you still
> don't have the file? To calculate that the hash is correct, you need
> to have the file, compute the hash over it (with an appropriate
> algorithm) and then compare the obtained hash with the one that the
> sender sent you in the SDP.

Well, you may have found the file based on the sha-1 hash. So you have 
the file. But perhaps the md5 hash of that file is not "DEF"?

(I think we may have different assumptions about the cases where this 
occurs. See below for more.)

>  > or it could
>  > treat this as ok as long as one of the hashes matches. The latter seems
>  > better. In that case, I think it should only return the hashes that
>  > actually match the file being returned. This does imply that if it
>  > supports multiple hashes then it needs to test the file against all of
>  > those supplied. Alternatively, perhaps it should only return those
>  > hashes that it has actually tested against the file being returned.
> 
> This is obviously an error case: if you implement several hashing
> encoding algorithms, then each one should produce a correct output and
> all should be consistent.

Right. For this to occur somebody must implement a hash incorrectly. (Of 
course the one that detects a problem will assume that it is the other 
party that made the mistake.) Its just a matter of how to respond.

> Thinking with an implementation mindset, I think this is the sequence
> flow at the file receiver side.  Once I have received the offer, I
> would select ONE hash algorithm that I implement. I would use this one
> to detect if I have already got the same file or not. If not, I will
> create the SDP answer, get the file, and hash it with the same
> algorithm that I selected to detect whether the file was received or
> not. If the result matches the hash declared in the SDP, then fine. If
> not, then I would deem it as a transmission error and inform the user
> that the file is corrupted. I would never check another hashing
> algorithm, even if supported.

I'm a little lost above.

The case I had in mind was a pull scenario. The file receiver sends an 
offer with multiple hash algorithms as I stated before. The file sender 
receives the offer and uses one of the hash algorithms to select the 
file. (Or it might use the name to select the file.) It then gets ready 
to send the file, so it prepares the answer. In the answer it needs to 
include hash information. As the draft was written, it wasn't clear 
whether it was to echo the hash parameters from the offer into the 
answer, or to include the hash algorithms from the offer in the answer, 
with the hash values it computes for the file. If the hash values 
requested are the same as those it computes it doesn't matter, but if 
they are different it does matter.

I think it would be bad in the case I mentioned for it to include md5 
with the incorrect value of DEF. It might be confusing for it to include 
a correct md5 hash that differed from what was requested, or maybe that 
would be an ok thing to do. It might be a burden on some file senders to 
recalculate all the hashes for the file that were mentioned in the request.

I think a reasonable answer is for the file *sender* in this case to 
include those hashes it knows for the file, including the one (if any) 
that was used to select the file. This could be limited to those 
mentioned in the request, but I see no reason to make such a limitation.

> Conclusion: once the file receiver selects a hashing algorithm, it is
> like if only that algorithm has been sent in SDP. Do we agree with the
> conclusion? Is there anything that needs to be added to the draft?

Yes, I think something is needed. For one thing, I note that there are 
no actions specified for the offerer when the answer is received, or 
when the file itself is received.

I think the following could be added to the end of 8.1.2:

"When the File Receiver receives the answer, if the port number of the 
answer for a file request is non-zero then it SHOULD receive the file 
using the MSRP protocol. If the answer contains a supported hashing 
algorithm, then the receiver SHOULD compute the hash of the file after 
receipt and check against the hash received in the answer."

In 8.2.2 I would suggest a change in the following:

                                    ... If the SDP offer included several
    'hash' parameters, the file sender SHOULD include at least one in the
    SDP answer, selected among those present in the offer and, at the
    same time, supported by the file sender.  If the SDP offer did not
    include a 'hash' parameter, the file sender SHOULD add one or more
    'hash' parameters, according to the supported hashing algorithms.

changed as follows:

                                    ... The file sender SHOULD add
    one or more 'hash' parameters in the answer, with algorithms
    supported by the file sender and values computed by the file sender,
    and SHOULD include at least one with a hash algorithm selected among
    those present in the offer. The file sender MUST NOT include a 'hash'
    parameter with an algorithm that was present in the offer and a value
    that differs from what was in the offer. (If a hash value computed
    by the file sender differs from that specified by the file receiver,
    the file sender can either send the file without the hash value or
    reject the request with a 400 (Bad Request) response.


I also now see a typo in 8.2.1:

    In a push operation the answerer is the file receiver.  When the file
    receiver gets the SDP answer, it extracts the attributes and

in above s/SDP answer/SDP offer/

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



From mmusic-bounces@ietf.org Mon May 21 16:08:36 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqEBI-0002VA-3t; Mon, 21 May 2007 16:08:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqE6Q-0008LR-Mg
	for mmusic@ietf.org; Mon, 21 May 2007 16:03:34 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HqE4K-0002v3-6J
	for mmusic@ietf.org; Mon, 21 May 2007 16:01:25 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 21 May 2007 13:01:24 -0700
X-IronPort-AV: i="4.14,562,1170662400"; 
	d="scan'208"; a="375440193:sNHT46248712"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l4LK1NVI015619; 
	Mon, 21 May 2007 13:01:23 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l4LK1Ctd017087;
	Mon, 21 May 2007 20:01:14 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:01:12 -0700
Received: from [10.32.241.149] ([10.32.241.149]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 13:01:12 -0700
Message-ID: <4651D3F6.2000608@cisco.com>
Date: Mon, 21 May 2007 13:16:38 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Attila Sipos <Attila.Sipos@vegastream.com>
Subject: Re: [MMUSIC]  RFC 3264 offer/answer - multicast questions
References: <8F1F2062CA7D754A838F0E66097D23A0C2433E@veg-brk-svr-pri.vegastream>
In-Reply-To: <8F1F2062CA7D754A838F0E66097D23A0C2433E@veg-brk-svr-pri.vegastream>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 20:01:12.0478 (UTC)
	FILETIME=[C81063E0:01C79BE2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2505; t=1179777683;
	x=1180641683; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[MMUSIC]=20=20RFC=203264=20offer/answer=20-=20multica
	st=20questions |Sender:=20;
	bh=IOJDJAqyA9EwoBzIqlPLtVV0UB673G93bNt428pvsEM=;
	b=sBbNU5TZ+poeXKZLUcp7Au6DttSXoBsWKnG3Mu7FSEMTVlLG/iR2J+u+wGj9dIPLOps7wh8Y
	VxQRa7Ikwdwx5JlIMUBkLodVkJK1UHkyulxQAVG0rNJB5m6F2rUaemdM;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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>
Errors-To: mmusic-bounces@ietf.org

inline.

Attila Sipos wrote:

> (SIP-Implementors didn't come up with an answer.
>  Maybe MMUSIC will...)
> 
> 
> I have some questions on section 5.2:
> 
> 5 Generating the Initial Offer
> 5.2 Multicast Streams
> 
>    If a session description contains a multicast media stream which is
>    listed as receive (send) only, it means that the participants,
>    including the offerer and answerer, can only receive (send) on that
>    stream.  This differs from the unicast view, where the directionality
>    refers to the flow of media between offerer and answerer.
> 
> I am confused about this.  It seems to say that if the offer has recvonly
> then both the "offerer and answerer" can only receive on that port.
> 
> I am sure my interpretation is wrong -
> what is the correct interpretation?

You are correct.

The usage of multicast with SIP was trying (for right or wrong), to 
maintain the original, original, way-back-when mode of operation of SIP, 
whereby you were inviting someone else to an mbone conference. In those 
original models there was only an SDP in the INVITE and both 
participants just joined the multicast group. So if the mbone session 
was recv-only, it was recv-only for everyone.


> 
>               =========================
> 
> Also regarding, "6.2 Multicast Streams", generating the answer, it seems
> that if the offer was a multicast SDP, the answer has to be an almost identical
> mulicast SDP.  Fine.  But what happens if the offer was unicast and the
> desired answer is multicast?

Not permitted at this time.

This might be fixable with the new capability negotiation framework.

> 
> For example, if you sent an INVITE to a server with unicast
> but the server wanted to use multicast to send the same RTP to
> everyone, can this happen?

No.

> Would there need to be anything special in the SDP?
> 
>               =========================
> 
> And who is allowed to send (say RTP) to a multicast IP address?
> Surely it only makes sense that the server sends the multicasts
> while the clients keep quiet.  ??

Depends on the session and who owns it.

-Jonathan R.


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

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



From mmusic-bounces@ietf.org Mon May 21 16:09:29 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqEC9-0003Fq-3c; Mon, 21 May 2007 16:09:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqEC8-0003Fk-73
	for mmusic@ietf.org; Mon, 21 May 2007 16:09:28 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HqEC7-0006DY-Jw
	for mmusic@ietf.org; Mon, 21 May 2007 16:09:28 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 21 May 2007 13:09:27 -0700
X-IronPort-AV: i="4.14,562,1170662400"; 
	d="scan'208"; a="487355918:sNHT210104886"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l4LK9RfD025946; 
	Mon, 21 May 2007 13:09:27 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4LK8cao003737;
	Mon, 21 May 2007 20:09:26 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:09:19 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:09:19 -0400
Message-ID: <4651FC6E.7020800@cisco.com>
Date: Mon, 21 May 2007 16:09:18 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A086.8010900@nsn.com>
In-Reply-To: <4651A086.8010900@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 20:09:19.0711 (UTC)
	FILETIME=[EA7A3EF0:01C79BE3]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3234; t=1179778167;
	x=1180642167; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2032=3A=20Re-send=20of=20the=20
	same=20file,=20vs.=20re-send=0A=20of=20SDP=20only |Sender:=20;
	bh=3QHIqtX4SRcA2XjQexFFmXxaPssV82ZHsLRklKqjqqY=;
	b=tftKJivce7CoqIhmjWdWfQaQ7jYjTF8Rw/A25h7sLiwoJ1vNvUv+OTVN4bY5aY9SvXoqiciN
	0okvaIEH6BaNiNqww3YfAYeBscntBwC/tMjX0FEP4f6yVHtLzAc9Ib88;
Authentication-Results: sj-dkim-4; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 32: Re-send of the same file,
 vs. re-send of SDP only
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

This seems reasonable to me. My first thought was that we should reuse 
the parameter from comedia, but it isn't quite right because it refers 
to the connection rather than the transfer. So this seems appropriate.

	Paul

Miguel Garcia wrote:
> Paul Kyzivat wrote
>  > Section 8.4.  Re-usage of Existing m= Lines in SDP
>  >
>  >    The SDP Offer/Answer Model [7] provides rules that allow SDP offerers
>  >    and answerers to modify an existing media line, i.e., re-use an
>  >    existing media line with different attributes.  The same is also
>  >    possible when SDP signals a file transfer operation according to the
>  >    rules of this memo.  Therefore, the procedures defined in RFC 3264
>  >    [7], in particular those defined in Section 8.3, MUST apply for file
>  >    transfer operations.
>  >
>  > What does this mean? In other usage, a reinvite will cause another o/a
>  > exchange. In some cases the SDP is unchanged in this o/a and the result
>  > is that things remain as they are.
>  >
>  > When using the procedures of this draft, if a new o/a exchange is made
>  > where there are no changes in the SDP, does it initiate a new transfer
>  > of the file that was previously exchanged? Or does it do nothing?
>  >
>  > There will be cases following a file transfer when there is need to do
>  > another o/a without repeating the transfer. And there may also be cases
>  > when there is an explicit desire to repeat the transmission. (Maybe via
>  > other means it is known that the file has changed.)
>  >
>  > Either the port must be set to zero in the subsequent o/a if
>  > retransmission is not desired, or else something must be changed (e.g.
>  > the msrp url) if retransmission is desired.
> 
> 
> I think this is a good point. There are cases when the endpoint wants
> to repeat the SDP, for example due to session timer, but does not want
> to repeat the file transfer. This implies a copy of the previously
> sent SDP without changes.
> 
> There are other cases where the sender wants to add additional media
> streams to the session (not related to MSRP). In this case, the m=
> line would be the same, especially if a file transfer is still going
> on. But there would be additional m= lines. We don't want to repeat
> the file transfer here either.
> 
> There are other cases where we want to repeat the file transfer,
> perhaps because the hash computation failed, or because the user
> accidentally deleted the file.
> 
> So, considering the use cases we have, and the discussion in
> SIP/SIPPING of the service-ID, I would apply Jonathan's view: be
> explicit in the signaling with what you ask. I would propose that we
> create a new attribute, named 'file-transfer', which can take two
> values: "new" (which is the default) and "existing". A file transfer
> with the "new" attribute indicates the desire to do a new file
> transfer, i.e., repeat it (if it was already done). A file transfer
> with the "existing" attribute indicates that the file already exists
> and we the file transfer should not take place. This approach was used
> in the past with comedia and the management of TCP connections. Any
> views?
> 
> /Miguel

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



From mmusic-bounces@ietf.org Mon May 21 16:12:04 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqEEe-0004tM-Bw; Mon, 21 May 2007 16:12:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqEEd-0004sw-3h
	for mmusic@ietf.org; Mon, 21 May 2007 16:12:03 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqEEb-00073Q-Df
	for mmusic@ietf.org; Mon, 21 May 2007 16:12:02 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 May 2007 16:12:01 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="121668788:sNHT50690084"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4LKC17c025388; 
	Mon, 21 May 2007 16:12:01 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4LKBd5j027104; 
	Mon, 21 May 2007 20:12:00 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:11:50 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:11:49 -0400
Message-ID: <4651FD03.9040400@cisco.com>
Date: Mon, 21 May 2007 16:11:47 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A065.2080005@nsn.com> <4651D4D0.3080105@cisco.com>
	<4651E7E8.2000503@nsn.com>
In-Reply-To: <4651E7E8.2000503@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 20:11:49.0699 (UTC)
	FILETIME=[43E09930:01C79BE4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4887; t=1179778321;
	x=1180642321; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2030=3A=20file=20disposition=20
	values |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=KkZajx2ud4WwndFxOToXCSHA/tJjKhMvOBGyecwYJa8=;
	b=phJtWj4GyxHLQdP4gN8VnsvYBzvL9ZuLcGsqFtsg5l/2lYCg8ohi6pkXo1B1gpbp4GIBSgxv
	ZqdcQI6Y5hxmUXXftOmCvbS2sK+0e3sVGn9iM+wV0cHmpo7WKOnFBmF8;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Eric Burger <eburger@bea.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 30: file disposition values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

We need a MIME expert here. Who do we have who qualifies? Eric?

	Paul

Miguel Garcia wrote:
> Yeah, I remember that you objected to "attachment". The reason I am 
> coming back to it is not because of the e-mail experience, but because 
> of the definition of the "attachment" disposition in RFC 2183, which I 
> copy here once more:
> 
>     Bodyparts can be designated `attachment' to indicate that they are
>     separate from the main body of the mail message, and that their
>     display should not be automatic, but contingent upon some further
>     action of the user.
> 
> So, there are two aspects in the definition of "attachment":
> a) what it indicates
> b) how they are displayed
> 
> In file transfer, a) is different, because it does not indicate 
> something separate from the main body of the mail message. However, b) 
> is the same: "their display should not be automatic, but continget upon 
> some further actions of the user."
> 
> I don't have a strong opinion to lean towards one or the other side. I 
> just thought that if someone were checking the IANA table of registered 
> disposition values, would ask what is the difference between 
> "attachment" and "whatever-name-we-defined-for-file-transfer".
> 
> Do we have any other opinions who can guide us?
> 
> /Miguel
> 
> 
> Paul Kyzivat wrote:
>> I know this one is coming full circle, since I was the one who 
>> originally objected to "attachment". More inline.
>>
>>     Paul
>>
>>
>> - In the file transfer
>>
>> Miguel Garcia wrote:
>>> Paul Kyzivat wrote:
>>>  > Section 7:
>>>  >
>>>  >    To indicate that a file should be automatically rendered, this 
>>> memo
>>>  >    uses the existing 'render' value of the Content Disposition 
>>> type in
>>>  >    the new 'file-disposition' attribute in SDP.  To indicate that 
>>> a file
>>>  >    should not be automatically rendered, this memo defines a new 
>>> value
>>>  >    'not-render' of the Content Disposition type.  The default 
>>> value is
>>>  >    'render', i.e., the absence of a 'file-disposition' attribute 
>>> in the
>>>  >    SDP has the same semantics as 'render'.
>>>  >
>>>  > The "not-render" disposition seems strange, because it is a negative.
>>>  > IMO something positive would be preferable - perhaps "storage" or
>>>  > "recipient-discretion".
>>>
>>> I am fine with the suggestion. I went to the IANA registry once more,
>>> and evaluate the possibility of reusing an existing disposition type.
>>
>> I looked again too, and didn't find anything *clearly* applicable.
>>
>>> So, what about the "attachment" disposition type? Its definition in
>>> RFC 2183 says:
>>>
>>>    Bodyparts can be designated `attachment' to indicate that they are
>>>    separate from the main body of the mail message, and that their
>>>    display should not be automatic, but contingent upon some further
>>>    action of the user.
>>
>> I do think that the kind of behavior you desire is somewhat similar to 
>> what happens for "attachment" with emails. But there are some 
>> significant differences:
>>
>> - in the case of email, the message itself is typically stored, and 
>> the attachment stays with it by default. Typically it takes an overt 
>> action by the user to extract the attachment from the message and put 
>> it somewhere else. (I do think that "attachment" could be used in an 
>> MSRP stream as part of a multipart/mixed IM message. But that wouldn't 
>> be quite the semantics you are looking for.)
>>
>> - When used as you are proposing, the above definition is problematic 
>> because there is no email message (nor an IM message) as the main body 
>> for this to be attached to.
>>
>> New values that come to mind (more than before): "save", "store", 
>> "ask", "prompt", "storage".
>>
>> (I'm not clear on what UI action is expected in this case. I'm 
>> imagining some sort of popup saying "You have a File" or something 
>> like that. If the sip session that contains this file transfer also 
>> has another MSRP session used for interactive IM, I guess the request 
>> could be interspersed with the display of IM messages. But if there 
>> was no IM session then that wouldn't work. I realize this could be 
>> done a lot of ways and we don't need to standardize them, but I'm just 
>> trying to have at least one workable use case in mind. The use case 
>> would help motivate naming a new disposition.)
>>
>> At the end of the day, if you want to use "attachment", then as long 
>> as the draft has a clear description of how it is interpreted in this 
>> case, and how it differs from the registered definition, then I won't 
>> complain.
>>
>>> I think it meets our requirements, so my proposal is to replace the
>>> existing "not-render" by "attachment". Any views?
>>>
>>>
>>> /Miguel
> 

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



From mmusic-bounces@ietf.org Mon May 21 16:14:08 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqEGd-0005sD-GN; Mon, 21 May 2007 16:14:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqEGc-0005s2-Ax
	for mmusic@ietf.org; Mon, 21 May 2007 16:14:06 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqEGa-0008E0-2Q
	for mmusic@ietf.org; Mon, 21 May 2007 16:14:06 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 May 2007 16:14:04 -0400
X-IronPort-AV: i="4.14,562,1170651600"; 
	d="scan'208"; a="121669027:sNHT46801896"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4LKE39u026378; 
	Mon, 21 May 2007 16:14:03 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l4LKE3Bg019608; 
	Mon, 21 May 2007 20:14:03 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:14:03 -0400
Received: from [10.86.240.6] ([10.86.240.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 May 2007 16:14:03 -0400
Message-ID: <4651FD89.1000005@cisco.com>
Date: Mon, 21 May 2007 16:14:01 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A060.6000908@nsn.com> <4651D05A.9080706@cisco.com>
	<4651DEB9.6040908@nsn.com> <4651E263.9010804@cisco.com>
	<4651E91F.2060308@nsn.com>
In-Reply-To: <4651E91F.2060308@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2007 20:14:03.0276 (UTC)
	FILETIME=[937ED4C0:01C79BE4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1347; t=1179778443;
	x=1180642443; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2029=3A=20Multipart=20due=20to=
	20icon |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=LDnh7Ek2ar1qcmU1NIhMbd7Io0aQWlnFZPAOH7X4x44=;
	b=PnBiqdBnMFLVdXA0zx0hL5QHboKf8lMjC0KaoZgtwKDPJRyicmdpwnLQ7sI4dT1rDk4RigJf
	Nl2mAvdA4dCgnmBjeI1M5lFGvjOhousZWgMwvaWp/loQr5v9vcMbpLU0;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 29: Multipart due to icon
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

OK. I was missing that aspect of what you were trying to say.
I guess that is a plausible case.

I'll shut up now.

	Paul

Miguel Garcia wrote:
> 
> 
> Paul Kyzivat wrote:
> 
>>
>> I'm still confused then, about how the problems with multipart for 
>> message-external arent' a problem for the mulipart for the icon. It 
>> seems like the same problems would apply to both, and the same 
>> solutions to those problems would apply to both.
>>
>> What am I missing?
> 
> What you are missing is the additional interoperability case we get with 
> the current specification and that we wouldn't get with the 
> message-external body. Let's assume both parties implement the file 
> transfer spec, but there is a B2BUA that removes bodies that are not 
> know or duly authorized.
> 
> - With the current specification, we get SDP O/A for file transfer, but 
> if there are icon bodies, there will be removed. Things mostly work, 
> only the icon fails to be displayed due to the B2BUA.
> 
> - With the message-external alternative, we don't get SDP O/A, we can 
> just fall back to vanilla MSRP. User's wouldn't be able to see the file 
> meta data and accept or reject a file based on that. They can still do a 
> trial an error and send the file with vanilla MSRP, but no more.
> 
> /Miguel
>>
>>     Paul
>>

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



From mmusic-bounces@ietf.org Mon May 21 21:38:44 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqJKk-0002Jy-Us; Mon, 21 May 2007 21:38:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqJKj-0002IY-6h
	for mmusic@ietf.org; Mon, 21 May 2007 21:38:41 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqJKh-0002G1-TN
	for mmusic@ietf.org; Mon, 21 May 2007 21:38:41 -0400
Received: by ug-out-1314.google.com with SMTP id 72so83414ugd
	for <mmusic@ietf.org>; Mon, 21 May 2007 18:38:39 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=eKVC1tvGmCcFdfeHUvi/JnyswbbnscvR59YckkAeqOqyYjURFwmU0ipQGftcVfPOHZ2rAyMCoEPe5+aD0Mhm8DHlfOFbXT8FFNqpRvfny1A0ZLAFwfKIgw13/74OFBstXbvQCjjZAZjV87Pawb3n7ujakYIHoihvCoIgb9JR3ac=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=eJuHnaiPhj8PKbuHm3sBdIoI2SHbbiTGrGG0GqgNSMtwmki39o5X99jspJLiC93d6xPW9voyNQzqxBu0RjJ3cw0M84q6gleM2pPZZxxeXOH2If9dzutj8Jk1TdK3ftcMkqf43gKzqejoMNOReOXDNfZdtOPb1jOojb3AEY9WEE8=
Received: by 10.78.200.3 with SMTP id x3mr1286003huf.1179797918911;
	Mon, 21 May 2007 18:38:38 -0700 (PDT)
Received: by 10.78.200.7 with HTTP; Mon, 21 May 2007 18:38:38 -0700 (PDT)
Message-ID: <4d0605c20705211838s62c8f70fmd8dfd4a8984cdd14@mail.gmail.com>
Date: Mon, 21 May 2007 18:38:38 -0700
From: "Joseph Pallas" <pallas@cs.stanford.edu>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Subject: Re: [MMUSIC] Reg. RTSP SETUP request
In-Reply-To: <465165FE.3020002@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4d0605c20705201142q354644f4v8524dd4928a748b@mail.gmail.com>
	<465165FE.3020002@ericsson.com>
X-Google-Sender-Auth: 9be9e9e698a9e22b
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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>
Errors-To: mmusic-bounces@ietf.org

I'll jump to the end ...

On 5/21/07, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
> The reason the SETUP is used for changing these parameters is to not
> require ALGs, Proxies etc to read other methods that affect parameters
> that the SETUP has created the initial values for. This motivation is
> documented in RFC 2326. Can you please provide any arguments why it is a
> bad idea?

I'm not honestly certain that it is a bad idea.  But the case that was
raised here suggests that there may be something wrong: the motivation
is to make life easier for ALGs and proxies, but the chosen approach
also makes life harder for ALGs and proxies.

With regard to the three issues you raised (media server churn, client
playout state, and rebuffering/resynchronization), I'm not sure they
are all valid.  I will accept that a media server might use fewer
resources to redirect an existing session than to tear down and
reestablish.  But I think that changing the destination address will
likely require rebuffering/resynchronization, unless the client is
receiving on both addresses at once.  Client playout state would fall
into two cases: streams that support user-specified starting points
and streams that don't (live only).  Live-only streams won't have any
client playout state associated with a session; random-access ones can
easily issue a PAUSE to learn the current playout point.

But if we believe that changing transports in mid-stream is sometimes
desirable, maybe overloading SETUP is not the best way to do it, since
SETUP is already overloaded for initial session creation and
aggregation.  Client-to-server REDIRECT might be an alternative.

joe

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



From mmusic-bounces@ietf.org Tue May 22 02:37:13 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqNzb-0004Mn-PK; Tue, 22 May 2007 02:37:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqNza-0004IV-9N
	for mmusic@ietf.org; Tue, 22 May 2007 02:37:10 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqNzY-0008Lm-IF
	for mmusic@ietf.org; Tue, 22 May 2007 02:37:10 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4M6b0mm021254; Tue, 22 May 2007 09:37:06 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:37:00 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:37:00 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:36:59 +0300
Message-ID: <46528F8B.2010204@nsn.com>
Date: Tue, 22 May 2007 09:36:59 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: sudhakar an <sudhakar_aqua@yahoo.com>, mmusic <mmusic@ietf.org>,
	"Isomaki Markus (Nokia-SIR/Espoo)" <Markus.Isomaki@nokia.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	"Salvatore Loreto (SA/ERI)" <Salvatore.Loreto@ericsson.com>
Subject: Re: [MMUSIC] ABNF errors in
	draft-ietf-mmusic-file-transfer-mech-01.txt
References: <105542.4793.qm@web51405.mail.re2.yahoo.com>
In-Reply-To: <105542.4793.qm@web51405.mail.re2.yahoo.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-OriginalArrivalTime: 22 May 2007 06:36:59.0756 (UTC)
	FILETIME=[999D12C0:01C79C3B]
X-Nokia-AV: Clean
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext12.nokia.com id
	l4M6b0mm021254
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Sudhakar:

Thanks for the reply. I missed the innocent "x" there.

So, I was looking at how the syntax should look like. I have another=20
proposal instead.


Alternative 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
My proposal is to remove the "x", which does not add any value (IMHO).=20
According to this, the syntax would be become:

     hash-selector        =3D "hash:" hash-algorithm ":" hash-value
     hash-algorithm       =3D token     ;see IANA Hash Function
                                      ;Textual Names registry
     hash-value           =3D 1*HEXDIG  ;HEXDIG defined in RFC 4234

and an example would be:

     a=3Dfile-selector:name:"My cool picture.jpg" type:image/jpeg
          size:32349 hash:sha-1:72245FE8653DDAF371362F86D471913EE4A2CE2E


Alternative 2:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RFC 4572 (Comedia) has a different way of encoding hashes in SDP, in the=20
'fingerprint' attribute. The difference is the presence of dots in=20
between each byte. Do people want to use this way of encoding hashes?=20
The syntax would be:

     hash-selector        =3D "hash:" hash-algorithm ":" hash-value
     hash-algorithm       =3D token     ;see IANA Hash Function
                                      ;Textual Names registry
     hash-value           =3D 2UHEX *(":" 2UHEX)
                              ; Each byte in upper-case hex, separated
                              ; by colons.

and an example would be:

     a=3Dfile-selector:name:"My cool picture.jpg" type:image/jpeg
   size:32349
   hash:sha-1:72:24:5F:E8:65:3D:DA:F3:71:36:2F:86:D4:71:91:3E:E4:A2:CE:2E


I don't like much alternative 2, but I reckon it will ease=20
implementations that have already implemented RFC 4572 and have a=20
function to calculate the hash and return it as a string.

So I propose that we change the draft to use to Alternative 2, so it is=20
aligned with Comedia. Any comments?

/Miguel

sudhakar an wrote:
> Hi Miguel,
>=20
> Thanks for the response. My reasoning/response below.
>=20
>  =20
>     hash-selector        =3D "hash:" hash-algorithm ":" hash-value
>     hash-algorithm       =3D token     ;see IANA Hash Function
>                                       ;Textual Names registry
>     hash-value           =3D hex-val   ;hex-val defined in RFC 4234
>  =20
>  From rfc4234
>  =20
>          hex-val        =3D  "x" 1*HEXDIG
>                             [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]
>=20
> If we go by this syntax the hash value will look like.
>=20
> hash:sha-1:x72245FE8653DDAF371362F86D471913EE4A2CE2E
>=20
> Note the "x" after "sha-1:". and "x" is not optional.
>=20
> Examples in draft-ietf-mmusic-file-transfer-mech-01.txt seem to show th=
e hash selector like this
>  =20
>      a=3Dfile-selector:name:"My cool picture.jpg" type:image/jpeg
>            size:32349 hash:sha-1:72245FE8653DDAF371362F86D471913EE4A2CE=
2E
>=20
> These do not have  "x" as the first charachter. Hence, I believe the ex=
amples are not conforming to the above mentioned ABNF.
>=20
> Thanks
> Sudhakar
>=20
> ----- Original Message ----
> From: Miguel Garcia <Miguel.Garcia@nsn.com>
> To: sudhakar an <sudhakar_aqua@yahoo.com>
> Cc: mmusic@ietf.org
> Sent: Monday, May 21, 2007 7:38:56 PM
> Subject: Re: [MMUSIC] ABNF errors in draft-ietf-mmusic-file-transfer-me=
ch-01.txt
>=20
>=20
> Hi Sudhakar:
>=20
> Thanks for your comments. See inline discussion:
>=20
>=20
> sudhakar an wrote:
>> 1)
>>     filename-selector    =3D "name:"  DQUOTE filename-string DQUOTE
>>                                         ; DQUOTE defined in RFC 4234
>>     filename-string      =3D byte-string ;byte-string defined in RFC 4=
566
>> =20
>> From rfc4566
>>    byte-string =3D         1*(%x01-09/%x0B-0C/%x0E-FF)
>>                          ;any byte except NUL, CR, or LF
>> =20
>> As it can be seen, the regular expression for byte-string would eat up=
 the second DQUOTE and all subsequent character until CRLF. Possibly the =
draft needs to be modified to mention that any DQUOTE appearing within by=
te=97string should be escaped properly.
>=20
> I agree with you, we ought to say that if quotes are used they should b=
e=20
> escaped along other characters that we already mention.
>=20
> So, I have modified the filename-string ABNF, which is now defined as:
>=20
>     filename-string      =3D 1*(%x01-09/%x0B-0C/%x0E-21/%x23-FF)
>                           ;any byte except NUL, CR, LF, or double quote=
s
>=20
> And I have added the following sentence later in the description:
>=20
>     If a file name contains double quotes, they MUST be percent-encoded.
>=20
>=20
>> =20
>> 2)
>> =20
>>    hash-selector        =3D "hash:" hash-algorithm ":" hash-value
>>     hash-algorithm       =3D token     ;see IANA Hash Function
>>                                      ;Textual Names registry
>>     hash-value           =3D hex-val   ;hex-val defined in RFC 4234
>> =20
>> From rfc4234
>> =20
>>         hex-val        =3D  "x" 1*HEXDIG
>>                            [ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]
>> =20
>> All examples in draft-ietf-mmusic-file-transfer-mech-01.txt seem to sh=
ow the hash selector like this
>> =20
>>     a=3Dfile-selector:name:"My cool picture.jpg" type:image/jpeg
>>           size:32349 hash:sha-1:72245FE8653DDAF371362F86D471913EE4A2CE=
2E
>> =20
>> Please remove the ambiguity in specifying hash selector
>=20
> I am not sure if I understood where the problem is. I was comparing the=
=20
> ABNF and the example and to my knowledge, the example fits the ABNF. Ca=
n=20
> you please elaborate?
>=20
>=20
>> =20
>> Thanks=20
>> Sudhakar
>>
>>
>=20
> Thanks for you review.
>=20
> /Miguel
>> =20
>> ______________________________________________________________________=
______________
>> Be a PS3 game guru.
>> Get your game face on with the latest PS3 news and previews at Yahoo! =
Games.
>> http://videogames.yahoo.com/platform?platform=3D120121
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>=20

--=20
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Tue May 22 02:42:45 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqO4y-00007I-Mk; Tue, 22 May 2007 02:42:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqO4w-000076-8D
	for mmusic@ietf.org; Tue, 22 May 2007 02:42:43 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqO4v-0001xI-Ng
	for mmusic@ietf.org; Tue, 22 May 2007 02:42:42 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4M6gPwj003249; Tue, 22 May 2007 09:42:38 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:42:33 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:42:33 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 09:42:33 +0300
Message-ID: <465290D9.5050605@nsn.com>
Date: Tue, 22 May 2007 09:42:33 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A086.8010900@nsn.com> <4651FC6E.7020800@cisco.com>
In-Reply-To: <4651FC6E.7020800@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 May 2007 06:42:33.0504 (UTC)
	FILETIME=[608AFA00:01C79C3C]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 32: Re-send of the same file,
 vs. re-send of SDP only
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Ok, since we seem to be converging, I will start implementing these changes.

/Miguel

Paul Kyzivat wrote:
> This seems reasonable to me. My first thought was that we should reuse 
> the parameter from comedia, but it isn't quite right because it refers 
> to the connection rather than the transfer. So this seems appropriate.
> 
>     Paul
> 
> Miguel Garcia wrote:
>> Paul Kyzivat wrote
>>  > Section 8.4.  Re-usage of Existing m= Lines in SDP
>>  >
>>  >    The SDP Offer/Answer Model [7] provides rules that allow SDP 
>> offerers
>>  >    and answerers to modify an existing media line, i.e., re-use an
>>  >    existing media line with different attributes.  The same is also
>>  >    possible when SDP signals a file transfer operation according to 
>> the
>>  >    rules of this memo.  Therefore, the procedures defined in RFC 3264
>>  >    [7], in particular those defined in Section 8.3, MUST apply for 
>> file
>>  >    transfer operations.
>>  >
>>  > What does this mean? In other usage, a reinvite will cause another o/a
>>  > exchange. In some cases the SDP is unchanged in this o/a and the 
>> result
>>  > is that things remain as they are.
>>  >
>>  > When using the procedures of this draft, if a new o/a exchange is made
>>  > where there are no changes in the SDP, does it initiate a new transfer
>>  > of the file that was previously exchanged? Or does it do nothing?
>>  >
>>  > There will be cases following a file transfer when there is need to do
>>  > another o/a without repeating the transfer. And there may also be 
>> cases
>>  > when there is an explicit desire to repeat the transmission. (Maybe 
>> via
>>  > other means it is known that the file has changed.)
>>  >
>>  > Either the port must be set to zero in the subsequent o/a if
>>  > retransmission is not desired, or else something must be changed (e.g.
>>  > the msrp url) if retransmission is desired.
>>
>>
>> I think this is a good point. There are cases when the endpoint wants
>> to repeat the SDP, for example due to session timer, but does not want
>> to repeat the file transfer. This implies a copy of the previously
>> sent SDP without changes.
>>
>> There are other cases where the sender wants to add additional media
>> streams to the session (not related to MSRP). In this case, the m=
>> line would be the same, especially if a file transfer is still going
>> on. But there would be additional m= lines. We don't want to repeat
>> the file transfer here either.
>>
>> There are other cases where we want to repeat the file transfer,
>> perhaps because the hash computation failed, or because the user
>> accidentally deleted the file.
>>
>> So, considering the use cases we have, and the discussion in
>> SIP/SIPPING of the service-ID, I would apply Jonathan's view: be
>> explicit in the signaling with what you ask. I would propose that we
>> create a new attribute, named 'file-transfer', which can take two
>> values: "new" (which is the default) and "existing". A file transfer
>> with the "new" attribute indicates the desire to do a new file
>> transfer, i.e., repeat it (if it was already done). A file transfer
>> with the "existing" attribute indicates that the file already exists
>> and we the file transfer should not take place. This approach was used
>> in the past with comedia and the management of TCP connections. Any
>> views?
>>
>> /Miguel

-- 
Please note my new e-mail address: miguel.garcia at nsn.com
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Tue May 22 03:36:12 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqOug-0003qT-A8; Tue, 22 May 2007 03:36:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqOue-0003p2-IW
	for mmusic@ietf.org; Tue, 22 May 2007 03:36:08 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqOub-00071m-QL
	for mmusic@ietf.org; Tue, 22 May 2007 03:36:08 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4M7Zrvw009109; Tue, 22 May 2007 10:36:01 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 10:35:40 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 10:35:39 +0300
Received: from [172.21.58.62] ([172.21.58.62]) by esebh101.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 10:35:39 +0300
Message-ID: <46529D4B.8090701@nsn.com>
Date: Tue, 22 May 2007 10:35:39 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A081.8080608@nsn.com> <4651F62C.3090509@cisco.com>
In-Reply-To: <4651F62C.3090509@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 May 2007 07:35:39.0265 (UTC)
	FILETIME=[CB678710:01C79C43]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 31: Errors when multiple hashes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Some text was cut. Let's go to the point of discussion.

Paul Kyzivat wrote:
> Inline.
> 
>     Paul
> 
> Miguel Garcia wrote:
> 
>> Thinking with an implementation mindset, I think this is the sequence
>> flow at the file receiver side.  Once I have received the offer, I
>> would select ONE hash algorithm that I implement. I would use this one
>> to detect if I have already got the same file or not. If not, I will
>> create the SDP answer, get the file, and hash it with the same
>> algorithm that I selected to detect whether the file was received or
>> not. If the result matches the hash declared in the SDP, then fine. If
>> not, then I would deem it as a transmission error and inform the user
>> that the file is corrupted. I would never check another hashing
>> algorithm, even if supported.
> 

Clarification: The above paragraph tried to describe the push scenario. 
You thought of the pull scneario, so that explains the confusion.

> I'm a little lost above.
> 
> The case I had in mind was a pull scenario. The file receiver sends an 
> offer with multiple hash algorithms as I stated before. The file sender 
> receives the offer and uses one of the hash algorithms to select the 
> file. (Or it might use the name to select the file.) 

So far so good. Clarification: the draft says that the file receiver 
must select one hash (if there are multiple) and all the other 
selectors. So, it can't use only the file name, it has to use the file 
name and one hash.

> It then gets ready 
> to send the file, so it prepares the answer. In the answer it needs to 
> include hash information. As the draft was written, it wasn't clear 
> whether it was to echo the hash parameters from the offer into the 
> answer, or to include the hash algorithms from the offer in the answer, 
> with the hash values it computes for the file. If the hash values 
> requested are the same as those it computes it doesn't matter, but if 
> they are different it does matter.

I think it is written:

- Push scenario, Section 8.2.1:

    If
    the offer contains one ore more 'hash' parameters in the 'file-
    selector' attribute, the answerer discards those with non-supported
    hashing algorithms and MUST copy the remaining (if any) to the 'file-
    selector' attribute of the answer.

- Pull scenario, Section 8.2.2 (see also discussion at the end of this 
mail):

    If the SDP offer included several
    'hash' parameters, the file sender SHOULD include at least one in the
    SDP answer, selected among those present in the offer and, at the
    same time, supported by the file sender.  If the SDP offer did not
    include a 'hash' parameter, the file sender SHOULD add one or more
    'hash' parameters, according to the supported hashing algorithms.

> 
> I think it would be bad in the case I mentioned for it to include md5 
> with the incorrect value of DEF. It might be confusing for it to include 
> a correct md5 hash that differed from what was requested, or maybe that 
> would be an ok thing to do. It might be a burden on some file senders to 
> recalculate all the hashes for the file that were mentioned in the request.
> 
> I think a reasonable answer is for the file *sender* in this case to 
> include those hashes it knows for the file, including the one (if any) 
> that was used to select the file. This could be limited to those 
> mentioned in the request, but I see no reason to make such a limitation.
> 
>> Conclusion: once the file receiver selects a hashing algorithm, it is
>> like if only that algorithm has been sent in SDP. Do we agree with the
>> conclusion? Is there anything that needs to be added to the draft?
> 
> Yes, I think something is needed. For one thing, I note that there are 
> no actions specified for the offerer when the answer is received, or 
> when the file itself is received.
> 
> I think the following could be added to the end of 8.1.2:
> 
> "When the File Receiver receives the answer, if the port number of the 
> answer for a file request is non-zero then it SHOULD receive the file 
> using the MSRP protocol. If the answer contains a supported hashing 
> algorithm, then the receiver SHOULD compute the hash of the file after 
> receipt and check against the hash received in the answer."

I am fine with the text.. I will loose a bit the words, because MSRP is 
used only because it is indicated in the m= line, so it is possible that 
in the future we extend the mechanism to use other transfer protocols. I 
have a problem with the first "SHOULD", because it depends on an action 
done by the remote endpoint (because it has to send), so it is obviously 
a "should". I have also indicated what the user agent should do if the 
check fails (inform the user and consider that the file transfer 
failed). The current text reads:

    When the file receiver receives the SDP answer, if the port number of
    the answer for a file request is non-zero then it should receive the
    file using the protocol indicated in the m= line.  If the SDP answer
    contains a supported hashing algorithm in the 'hash' parameter of the
    'file-selector' attribute, then the file receiver SHOULD compute the
    hash of the file after receipt and check against the hash received in
    the answer.  In case the computed hash does not match the one
    contained in the SDP answer, the file receiver SHOULD consider that
    the file transfer failed and SHOULD inform the user.

> 
> In 8.2.2 I would suggest a change in the following:
> 
>                                    ... If the SDP offer included several
>    'hash' parameters, the file sender SHOULD include at least one in the
>    SDP answer, selected among those present in the offer and, at the
>    same time, supported by the file sender.  If the SDP offer did not
>    include a 'hash' parameter, the file sender SHOULD add one or more
>    'hash' parameters, according to the supported hashing algorithms.
> 
> changed as follows:
> 
>                                    ... The file sender SHOULD add
>    one or more 'hash' parameters in the answer, with algorithms
>    supported by the file sender and values computed by the file sender,
>    and SHOULD include at least one with a hash algorithm selected among
>    those present in the offer. The file sender MUST NOT include a 'hash'
>    parameter with an algorithm that was present in the offer and a value
>    that differs from what was in the offer. (If a hash value computed
>    by the file sender differs from that specified by the file receiver,
>    the file sender can either send the file without the hash value or
>    reject the request with a 400 (Bad Request) response.

I think we need to discuss the principles a bit more. To put things in 
context first: An file receiver (offerer) learned by some magic (e.g., 
resource event package draft) one or more hashes of a file. It selects 
one or more that it supports and included into the offer (the offerer is 
not going to add a hash algorithm it does not support). It sends the 
offer to the file receiver, who extracts one and only one hash algorithm 
to select the file (perhaps together with other selectors, that is 
irrelevant). Then, why in the heck does the file sender need to send 
MORE hash algorithms, (and presumably compute them). I think it is a 
waist of time and CPU cycles.

Also, your text "The file sender MUST NOT include a 'hash' parameter 
with an algorithm that was present in the offer and a value that differs 
from what was in the offer". This will never happen with the scenario I 
mentioned, because:
a) there is only one chosen hash algorithm
b) the hash is used to select the file, if the hash was wrong, then it 
would not select a file.

> 
> 
> I also now see a typo in 8.2.1:
> 
>    In a push operation the answerer is the file receiver.  When the file
>    receiver gets the SDP answer, it extracts the attributes and
> 
> in above s/SDP answer/SDP offer/

good catch. Fixed.

BR,

     Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Tue May 22 10:27:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqVKk-0007ts-DZ; Tue, 22 May 2007 10:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqUsv-0004Ci-0y; Tue, 22 May 2007 09:58:45 -0400
Received: from repmmg02.bea.com ([66.248.192.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HqUst-0004Zh-JR; Tue, 22 May 2007 09:58:44 -0400
Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72])
	by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id
	l4MDwfIg007181; Tue, 22 May 2007 06:58:41 -0700
Received: from rcpbex01.amer.bea.com (rcpbex01.bea.com [10.168.26.17])
	by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.5) with ESMTP id
	l4MDwdeO023458; Tue, 22 May 2007 06:58:40 -0700
Received: from 10.43.242.244 ([10.43.242.244]) by rcpbex01.amer.bea.com
	([10.168.26.17]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 22 May 2007 13:58:39 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 22 May 2007 19:48:42 +0800
From: Eric Burger <eburger@bea.com>
To: <mmusic@ietf.org>
Message-ID: <C278F99A.398F%eburger@bea.com>
Thread-Topic: [Speechsc] WGLC MRCPv2-12
Thread-Index: Acdy5kyPCIt7w37GTz+qURNeG5V+RgpgNh0F
In-Reply-To: <460D3708.90109@ericsson.com>
Mime-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Tue, 22 May 2007 10:27:28 -0400
Cc: speechsc@ietf.org
Subject: [MMUSIC] FW: [Speechsc] WGLC MRCPv2-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

OK, MMUSIC folks, can you help us SPEECHSC folks out?

Magnus noted the following may be an issue:
> ------ Forwarded Message
> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
> Date: Fri, 30 Mar 2007 09:12:56 -0700
[snip]
> In section 4.2 you define behavior for using the comedia a=connection
> attribute with the TCP/MRCPv2 protocol. Based on the text and example
> (add recognizer example starting on page 16) it seems that you try to
> allow that multiple m= lines reuses the same TCP connection. However it
> is far from obvious that comedia (RFC 4145) support this behavior. It
> doesn't talk about any relation between multiple m= lines and their TCP
> connections. I would recommend discussing this with MMUSIC.
------ End of Forwarded Message

The "section 4.2" referenced is to MRCPv2, draft-ietf-speechsc-mrcpv2:

When using TCP the m-lines MUST conform to comedia [10], which describes the
usage of SDP for connection-oriented transport.
[snip]
The a=setup attribute, as described in comedia [10], MUST be "active" for
the offer from the client and MUST be "passive" for the answer from the
MRCPv2 server. The a=connection attribute MUST have a value of "new" on the
very first control m-line offer from the client to an MRCPv2 server.
Subsequent control m-line offers from the client to the MRCP server MAY
contain "new" or "existing", depending on whether the client wants to set up
a new connection or share an existing connection, respectively.



Do you think we are OK?  If not, why not, and how can we fix it?

Thanks.


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

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



From mmusic-bounces@ietf.org Tue May 22 10:27:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqVKk-0007ta-3Y; Tue, 22 May 2007 10:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqQOW-00014u-5r
	for mmusic@ietf.org; Tue, 22 May 2007 05:11:05 -0400
Received: from smw151.hostingcare.net ([67.19.193.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqQOV-0005vS-J5
	for mmusic@ietf.org; Tue, 22 May 2007 05:11:04 -0400
Received: from smw151 ([127.0.0.1]) by smw151.hostingcare.net with MailEnable
	ESMTP; Tue, 22 May 2007 03:11:49 -0500
thread-index: AcecSNi3aJBpJit/SPSISj4v89Jxag==
Thread-Topic: Call for Paper :: Special issue on Intelligent information
	processing in wireless domain
From: <newsletters@ubicc.org>
To: <mmusic@ietf.org>
Date: Tue, 22 May 2007 03:11:49 -0500
Message-ID: <F30C11CC661E4C1B8D5D44B4F57BBFAC@hostingcare.net>
MIME-Version: 1.0
X-Mailer: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: high
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3959
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
X-Mailman-Approved-At: Tue, 22 May 2007 10:27:29 -0400
Subject: [MMUSIC] Call for Paper :: Special issue on Intelligent information
	processing in wireless domain
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="===============0924146265=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0924146265==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_7E36_01C79C1E.EFE1C0D0"
Content-Class: urn:content-classes:message

This is a multi-part message in MIME format.

------=_NextPart_000_7E36_01C79C1E.EFE1C0D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Ubiquitous Computing and Communication Journal	
Call for Paper	
Special issue on Intelligent information processing in wireless domain	
    Home<http://www.ubicc.org/images/icon_home.gif> Home
<http://www.ubicc.org/index.aspx>  |  About
Us<http://www.ubicc.org/images/icon_about.gif> About Us
<http://www.ubicc.org/aboutus.aspx>  |  Contact
Us<http://www.ubicc.org/images/icon_contact.gif> Contact Us
<http://www.ubicc.org/contactus.aspx>  |
<http://www.ubicc.org/images/icon_account.gif> Login
<http://www.ubicc.org/login.aspx> 

Tuesday, May 22, 2007 

Information Technology is the umbrella term that encompasses the entire
area of information processing, storage as well as dissemination of
information content using computer and communication technology every
aspect of human life is being affected by information technology due to
capability of digital communication and computation power. Information
Communication technology is making it possible for more and more
individual than ever to access the knowledge and to learn a new and
different ways. The information technology is changing the way of
conducting, managing as well as executing business transaction using
advance sophisticated computer & network. Ever expanding capabilities of
data network and availability of devices and system with high
computational power is changing the modality of a communication between
person to person as well as person to organization in digital global
world. This has ushred in a new set of opportunity and services in
different areas of wireless scenario. Keeping in view of advancement in
information communication technology, it becomes essential to identify
and study the impact of Ubiquitous Computing and Communication on
different aspects of human life. 

 

Theme of the Special Issue.

 

*	Intelligent information processing in wireless domain. 

 Papers are invited in the following areas:-

*	Artificial intelligent techniques in wireless communication 
*	Multi-Radio and Multi channel Wireless mesh networking 
*	Wireless LAN, PAN, WAN, MAN. 
*	Modeling and Performance Evaluations. 
*	Digital. Signal Processing in Communication 
*	Speech Communication 
*	Computational intelligent information retrieval 
*	Intelligent network and mobile computing 
*	3G,4G mobile system, Wi Fi , Wi Max 
*	Wireless Access Technologies 
*	Protocol / Security 
*	Wireless / Adhoc networks. 

IMPORTANT DATES:

 

Manuscript Submission:                  June 20, 2007

First Notification:                             July 01,2007

Revised Final Submission:               September 10, 2007

Publication Date:                             October 2007

  

Editor Special Issue.

Dr. Jasvir Singh

      B.E, M-Tech, P.hD

Professor

Communication Signal Processing Research Lab

Dept. of Electronics Technology

Faculty of Engineering & Technology,

Guru Nanak Dev University, 

      Amritsar, Punjab, India,     j_singh00@rediffmail.com
<mailto:j_singh00@rediffmail.com> 

                                                 jsingh@ubicc.org
<mailto:jsingh@ubicc.org> 

 	

------=_NextPart_000_7E36_01C79C1E.EFE1C0D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

<META http-equiv=Content-Language content=en-us>
<META content="The journal of Ubiquitous Computing and Communication Journal (UBICC) is a bimonthly and peer-reviewed International Journal promoting dissemination of research and technological implementation experiences. We welcome research Papers, case studies, technical and conference reports for submission, in the areas of Computer Science, Engineering, Telecommunication, and Information Systems." name=description>
<META content="UBICC Journal, UBICC, Journal, Research, Ubiquitous, Computing, Communication, Ubiquitous Computing and Communication Journal, 6Lowpan, Security, Privacy, Mobile Computing, Mobile, Notebook, Computer, Lab, Research, electronics, electronic, electrical, conferences, UBICC conferences, UBICC membership, biomed, conference, UBICC fellow, nanotechnology, UBICC xplore, fellow, UBICC pes, UBICC explore, UBICCxplore, electrical engineer, electrical engineering, electronic engineering, engineer, engineering, technical professions, technical, standards, society, membership, scientific computing society, educational computing society, computing professionals, information technology, IT professionals, IT students, association for computing machinery, programming, computer programmers, algorithms and computational theory, Ada, APL, applied computing, computer architecture, artificial intelligence, biomedical computing, computer science education, design automation, computer graphics, HCI, human-computer interaction, multimedia, hypermedia, mobile computing, programming languages, software engineering, computer science, supercomputing, university and college computing services, journals, books, special interest groups" name=keywords>
<META content="Microsoft FrontPage 5.0" name=GENERATOR>
<META content=FrontPage.Editor.Document name=ProgId>
<META content="Visual Basic .NET 7.1" name=CODE_LANGUAGE>
<META content=JavaScript name=vs_defaultClientScript>
<META content=http://schemas.microsoft.com/intellisense/ie5 name=vs_targetSchema>
<DIV align=center>
<CENTER>
<TABLE id=AutoNumber1 style="BORDER-COLLAPSE: collapse" borderColor=#111111 height=41 cellPadding=2 width=600 border=0>
<TBODY>
<TR>
<TD align=middle width=596 bgColor=#737373 colSpan=2 height=51><B><FONT face=Arial color=#ffffff size=5>Ubiquitous Computing and Communication Journal</FONT></B></TD></TR>
<TR>
<TD align=middle width=596 bgColor=#909090 colSpan=2 height=29><FONT face=Arial color=#ffff00 size=4>Call for Paper</FONT></TD></TR>
<TR>
<TD align=middle width=596 bgColor=#adadad colSpan=2 height=33><FONT face=Arial size=4>Special issue on Intelligent information processing in wireless domain</FONT></TD></TR>
<TR>
<TD align=middle width=356 bgColor=#d4d4d4 height=26>
<P align=left><B><FONT face=Arial size=2><FONT color=#ffffff>&nbsp;&nbsp; <IMG height=9 alt=Home src="http://www.ubicc.org/images/icon_home.gif" width=9 align=absMiddle> </FONT><A style="TEXT-DECORATION: none" href="http://www.ubicc.org/index.aspx"><FONT color=#ffffff>Home</FONT></A><FONT color=#ffffff> | <IMG height=9 alt="About Us" src="http://www.ubicc.org/images/icon_about.gif" width=9 align=absMiddle> </FONT><A style="TEXT-DECORATION: none" href="http://www.ubicc.org/aboutus.aspx"><FONT color=#ffffff>About Us</FONT></A><FONT color=#ffffff> | <IMG height=9 alt="Contact Us" src="http://www.ubicc.org/images/icon_contact.gif" width=9 align=absMiddle> </FONT><A style="TEXT-DECORATION: none" href="http://www.ubicc.org/contactus.aspx"><FONT color=#ffffff>Contact Us</FONT></A><FONT color=#ffffff> | <IMG height=9 src="http://www.ubicc.org/images/icon_account.gif" width=9 align=absMiddle> </FONT><A style="TEXT-DECORATION: none" href="http://www.ubicc.org/login.aspx"><FONT color=#ffffff>Login</FONT></A></FONT></B></P></TD>
<TD align=middle width=236 bgColor=#d4d4d4 height=26>
<P align=right><B><FONT face=Arial size=2>Tuesday, May 22, 2007 </FONT></B></P></TD></TR>
<TR>
<TD borderColor=#d4d4d4 align=middle width=596 bgColor=#d4d4d4 colSpan=2 height=70>
<DIV align=center>
<CENTER>
<TABLE id=AutoNumber2 style="BORDER-COLLAPSE: collapse" borderColor=#111111 cellSpacing=0 cellPadding=0 width="99%" border=0>
<TBODY>
<TR>
<TD borderColor=#ffffff width="100%" bgColor=#ffffff>
<DIV align=center>
<CENTER>
<TABLE id=AutoNumber3 style="BORDER-COLLAPSE: collapse" borderColor=#111111 cellSpacing=0 cellPadding=0 width="99%" border=0>
<TBODY>
<TR>
<TD width="100%">
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Information Technology is the umbrella term that encompasses the entire area of information processing, storage as well as dissemination of information content using computer and communication technology every aspect of human life is being affected by information technology due to capability of digital communication and computation power. Information Communication technology is making it possible for more and more individual than ever to access the knowledge and to learn a new and different ways. The information technology is changing the way of conducting, managing as well as executing business transaction using advance sophisticated computer &amp; network. Ever expanding capabilities of data network and availability of devices and system with high computational power is changing the modality of a communication between person to person as well as person to organization in digital global world. This has ushred in a new set of opportunity and services in different areas of wireless scenario. Keeping in view of advancement in information communication technology, it becomes essential to identify and study the impact of Ubiquitous Computing and Communication on different aspects of human life. </SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;</SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: rgb(51,102,255); FONT-FAMILY: Arial">Theme of the Special Issue.</SPAN></B></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;</SPAN></B></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Intelligent information processing in wireless domain.</SPAN> </LI></UL>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;</SPAN><B><SPAN style="FONT-SIZE: 10pt; COLOR: rgb(51,102,255); FONT-FAMILY: Arial">Papers are invited in the following areas</SPAN></B><SPAN style="FONT-SIZE: 10pt; COLOR: rgb(51,102,255); FONT-FAMILY: Arial">:-</SPAN></P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Artificial intelligent techniques in wireless communication</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Multi-Radio and Multi channel Wireless mesh networking</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Wireless LAN, PAN, WAN, MAN.</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Modeling and Performance Evaluations.</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Digital. Signal Processing in Communication </SPAN>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Speech Communication </SPAN>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Computational intelligent information retrieval</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Intelligent network and mobile computing </SPAN>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">3G,4G mobile system, Wi Fi , Wi Max </SPAN>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Wireless Access Technologies</SPAN><FONT face=Arial size=2><SPAN> </SPAN></FONT>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Protocol / Security </SPAN>
<LI class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; COLOR: black; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Wireless / Adhoc networks.</SPAN> </LI></UL><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><U><SPAN style="FONT-SIZE: 12pt"><FONT face=Arial size=2>IMPORTANT DATES:</FONT></SPAN></U></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">&nbsp;</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face=Arial size=2>Manuscript Submission:<SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><ST1:DATE month="5" day="20" year="2007" w:st="on"><B>June 20, 2007</B></ST1:DATE></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face=Arial size=2>First Notification:<SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><ST1:DATE month="7" day="23" year="2007" w:st="on"><B>July 01,2007</B></ST1:DATE></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face=Arial size=2>Revised Final Submission:<SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><ST1:DATE month="9" day="10" year="2007" w:st="on"><B>&nbsp;September 10, 2007</B></ST1:DATE></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 11pt"><FONT face=Arial size=2>Publication Date:<B><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>October 2007</B></FONT></SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial">&nbsp;</SPAN><FONT face=Arial size=2>&nbsp;</FONT></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-WEIGHT: 700; FONT-SIZE: 10pt; COLOR: #3366ff; FONT-FAMILY: Arial">Editor Special Issue.</SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Dr. Jasvir Singh</SPAN></B></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>B.E, M-Tech, P.hD</SPAN></B></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Professor</SPAN></B></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Communication Signal Processing Research Lab</SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Dept. of Electronics Technology</SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Faculty of Engineering &amp; Technology,</SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt 0.25in; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><ST1:PLACE w:st="on"><ST1:PLACENAME w:st="on"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Guru</SPAN></ST1:PLACENAME><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"> <ST1:PLACENAME w:st="on">Nanak</ST1:PLACENAME> <ST1:PLACENAME w:st="on">Dev</ST1:PLACENAME> <ST1:PLACETYPE w:st="on">University</ST1:PLACETYPE></SPAN></ST1:PLACE><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">, </SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>Amritsar, Punjab, India,</SPAN></B><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><SPAN>&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><A href="mailto:j_singh00@rediffmail.com"><SPAN style="COLOR: black; TEXT-DECORATION: none">j_singh00@rediffmail.com</SPAN></A></SPAN></P>
<P class=MsoNormal style="BACKGROUND: white; MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial"><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A href="mailto:jsingh@ubicc.org"><SPAN style="COLOR: black; TEXT-DECORATION: none">jsingh@ubicc.org</SPAN></A></SPAN></P></TD></TR></TBODY></TABLE></CENTER></DIV></TD></TR>
<TR>
<TD width="100%">&nbsp;</TD></TR></TBODY></TABLE></CENTER></DIV></TD></TR></TBODY></TABLE></CENTER></DIV>
------=_NextPart_000_7E36_01C79C1E.EFE1C0D0--




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

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

--===============0924146265==--




From mmusic-bounces@ietf.org Tue May 22 12:58:21 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqXgh-0003ME-MK; Tue, 22 May 2007 12:58:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqXgg-0003KR-5S
	for mmusic@ietf.org; Tue, 22 May 2007 12:58:18 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqXgf-0000MZ-K2
	for mmusic@ietf.org; Tue, 22 May 2007 12:58:18 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 22 May 2007 12:58:17 -0400
X-IronPort-AV: i="4.14,566,1170651600"; 
	d="scan'208"; a="60909830:sNHT82228196"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4MGwHDP001538; 
	Tue, 22 May 2007 12:58:17 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4MGw463019312; 
	Tue, 22 May 2007 16:58:17 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 12:58:12 -0400
Received: from [161.44.174.124] ([161.44.174.124]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 May 2007 12:58:11 -0400
Message-ID: <46532125.9050902@cisco.com>
Date: Tue, 22 May 2007 12:58:13 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
References: <4651A081.8080608@nsn.com> <4651F62C.3090509@cisco.com>
	<46529D4B.8090701@nsn.com>
In-Reply-To: <46529D4B.8090701@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 May 2007 16:58:11.0797 (UTC)
	FILETIME=[617B3050:01C79C92]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7593; t=1179853097;
	x=1180717097; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20File-transfer=20issue=2031=3A=20Errors=20when=20multi
	ple=20hashes |Sender:=20
	|To:=20Miguel=20Garcia=20<Miguel.Garcia@nsn.com>;
	bh=I76JXESBITX8uOnyW0JjourNQ5Qu0PwZ2GAF9gmlW5A=;
	b=eOrOKkmyk1Tw94QDnWx4PlIlengnZUIRZ84/UnryqxORPGQ+Zftn+GtOZ08e+2b232tBR81v
	1H8bF+0y6+tMW1qHrfWT+dqXiIP0lKWRhEXpp9N2PigFm2TMCw4BuDCe;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 31: Errors when multiple hashes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

I think we are close to converging.  More inline. (I'm trimming 
extraneous text.)

	Paul

Miguel Garcia wrote:

>> It then gets ready to send the file, so it prepares the answer. In the 
>> answer it needs to include hash information. As the draft was written, 
>> it wasn't clear whether it was to echo the hash parameters from the 
>> offer into the answer, or to include the hash algorithms from the 
>> offer in the answer, with the hash values it computes for the file. If 
>> the hash values requested are the same as those it computes it doesn't 
>> matter, but if they are different it does matter.
> 
> I think it is written:
> 
> - Push scenario, Section 8.2.1:
> 
>    If
>    the offer contains one ore more 'hash' parameters in the 'file-
>    selector' attribute, the answerer discards those with non-supported
>    hashing algorithms and MUST copy the remaining (if any) to the 'file-
>    selector' attribute of the answer.
> 
> - Pull scenario, Section 8.2.2 (see also discussion at the end of this 
> mail):
> 
>    If the SDP offer included several
>    'hash' parameters, the file sender SHOULD include at least one in the
>    SDP answer, selected among those present in the offer and, at the
>    same time, supported by the file sender.  If the SDP offer did not
>    include a 'hash' parameter, the file sender SHOULD add one or more
>    'hash' parameters, according to the supported hashing algorithms.

None of the above says that the sender computes the hash that it 
includes. Copying the hash values from the offer seems to be perfectly 
consistent with the above text. In fact, the above seems to demand 
copying them rather than recomputing or verifying. And it could be an 
easy and natural thing to do. But its the *wrong* thing to do if the 
value hasn't been confirmed to be correct.

>> I think the following could be added to the end of 8.1.2:
>>
>> "When the File Receiver receives the answer, if the port number of the 
>> answer for a file request is non-zero then it SHOULD receive the file 
>> using the MSRP protocol. If the answer contains a supported hashing 
>> algorithm, then the receiver SHOULD compute the hash of the file after 
>> receipt and check against the hash received in the answer."
> 
> I am fine with the text.. I will loose a bit the words, because MSRP is 
> used only because it is indicated in the m= line, so it is possible that 
> in the future we extend the mechanism to use other transfer protocols. I 
> have a problem with the first "SHOULD", because it depends on an action 
> done by the remote endpoint (because it has to send), so it is obviously 
> a "should". I have also indicated what the user agent should do if the 
> check fails (inform the user and consider that the file transfer 
> failed). The current text reads:
> 
>    When the file receiver receives the SDP answer, if the port number of
>    the answer for a file request is non-zero then it should receive the
>    file using the protocol indicated in the m= line.  If the SDP answer
>    contains a supported hashing algorithm in the 'hash' parameter of the
>    'file-selector' attribute, then the file receiver SHOULD compute the
>    hash of the file after receipt and check against the hash received in
>    the answer.  In case the computed hash does not match the one
>    contained in the SDP answer, the file receiver SHOULD consider that
>    the file transfer failed and SHOULD inform the user.

This seems fine.

>> In 8.2.2 I would suggest a change in the following:
>>
>>                                    ... If the SDP offer included several
>>    'hash' parameters, the file sender SHOULD include at least one in the
>>    SDP answer, selected among those present in the offer and, at the
>>    same time, supported by the file sender.  If the SDP offer did not
>>    include a 'hash' parameter, the file sender SHOULD add one or more
>>    'hash' parameters, according to the supported hashing algorithms.
>>
>> changed as follows:
>>
>>                                    ... The file sender SHOULD add
>>    one or more 'hash' parameters in the answer, with algorithms
>>    supported by the file sender and values computed by the file sender,
>>    and SHOULD include at least one with a hash algorithm selected among
>>    those present in the offer. The file sender MUST NOT include a 'hash'
>>    parameter with an algorithm that was present in the offer and a value
>>    that differs from what was in the offer. (If a hash value computed
>>    by the file sender differs from that specified by the file receiver,
>>    the file sender can either send the file without the hash value or
>>    reject the request with a 400 (Bad Request) response.
> 
> I think we need to discuss the principles a bit more. To put things in 
> context first: An file receiver (offerer) learned by some magic (e.g., 
> resource event package draft) one or more hashes of a file. It selects 
> one or more that it supports and included into the offer (the offerer is 
> not going to add a hash algorithm it does not support). It sends the 
> offer to the file receiver, who extracts one and only one hash algorithm 
> to select the file (perhaps together with other selectors, that is 
> irrelevant). Then, why in the heck does the file sender need to send 
> MORE hash algorithms, (and presumably compute them). I think it is a 
> waist of time and CPU cycles.

It doesn't NEED to. And the text I suggested doesn't require that. I 
said "one or more" that are "supported by the file sender", at least one 
of which has an algorithm included in the offer. One is enough to 
satisfy all of those requirements. The sender can include others if it 
wishes, mentioned in the offer or not.

Why would the sender include extras? Perhaps it keeps all the hashes 
around for its files, and its simply easier to include them all than to 
check which of them is an algorithm mentioned in the request.

If there are several in the answer, then the recipient can choose which 
one to use for verifying the receipt of the file. It might choose an 
easier one to compute than the one it requested.

Also, this unifies with the case where the offer included *no* hashes, 
because none were known. In that case the sender doesn't know what 
hashes the receiver supports, so sending multiples increases the odds 
that the receiver will be able to check the hash.

Doesn't really matter. This just gives a little more latitude to the 
sender without requiring any more work.

> Also, your text "The file sender MUST NOT include a 'hash' parameter 
> with an algorithm that was present in the offer and a value that differs 
> from what was in the offer". This will never happen with the scenario I 
> mentioned, because:
> a) there is only one chosen hash algorithm
> b) the hash is used to select the file, if the hash was wrong, then it 
> would not select a file.

I think it could still be possible, if the sender can include multiple 
hashes. Suppose the offer included sha-1:ABC and md5:DEF. And suppose 
the answerer/sender chose the sha-1 hash to select the file, so it does 
actually have the sha-1:ABC hash. But suppose the sender's md5 hash 
value for the file is CDE.

It could return 'sha-1:ABC md5:CDE' but that might expose the conflict 
with what the offerer requested. This statement just prevents that conflict.

But I don't care much about this. It would simplify things to leave it out.

	Paul

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



From mmusic-bounces@ietf.org Tue May 22 19:35:26 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hqdsz-0001Yi-4X; Tue, 22 May 2007 19:35:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hqdss-0001VQ-If; Tue, 22 May 2007 19:35:18 -0400
Received: from kal-el.real.com ([207.188.23.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hqdsr-00007o-5t; Tue, 22 May 2007 19:35:18 -0400
Received: from SEAL25947 ([::ffff:172.22.147.244])
	(AUTH: LOGIN csteck, TLS: TLSv1/SSLv3,128bits,RC4-MD5)
	by kal-el.real.com with esmtp; Tue, 22 May 2007 16:35:16 -0700
	id 00080037.46537E34.00000801
From: "Chris Steck" <csteck@real.com>
To: "'mmusic \(E-mail\)'" <mmusic@ietf.org>,
	"'SIP IETF'" <sip@ietf.org>, avt@ietf.org
Date: Tue, 22 May 2007 16:35:16 -0700
Message-ID: <00e501c79cc9$da1112a0$9383cf87@corp.real.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aceck/nkw5z1pOa2QKGJBFBMtgRkbgAMleDw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: 
Subject: [MMUSIC] FW: [imtcmembers] IMTC Multimedia Standards Historical
	Archive - contributions?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

[Taking off my RealNetworks hat and putting on my IMTC CTO hat...]

Sorry if you get this multiple times,

A while back there were some threads going on pre-existing IPR for IP
telephony and I encouraged people to drop the topic on the reflectors due to
the unknown impact it may have on your causes to discuss and share
information in that manner.  Today I wanted to follow up by letting you all
know about a valuable resource from IMTC which you can both leverage and
help strengthen:

The IMTC has an IPR AG which is developing a Multimedia Standards Historical
Archive which contains contributions to standards meetings, reports, records
of IPR licensing declarations, copies of standard organizations patent
databases, publications such as journal articles, books, etc.

See below for the process to contact the IMTC Secretariat if you think you
have actual historical documentation that can benefit the archive. (or for
that matter, want to join IMTC so that you can leverage the archive!) While
the mail below is targeted at member companies, we also encourage
non-members with documentation of interest to submit via the same process
indicated below.  (Please don't reply to this mail to the misc
reflectors...)

Thanks,

Chris Steck
CTO of IMTC

-----Original Message-----
From: Patrick Luthi [mailto:patrick.luthi@tandberg.com] 
Sent: Tuesday, May 22, 2007 8:55 AM
To: IMTC Members
Subject: [imtcmembers] IMTC Multimedia Standards Historical Archive -
contributions?

Dear IMTC Members,

Many of you are aware of the existence of the IMTC Multimedia Standards
Historical Archive and an increasing number of you are regularly consulting
it.

The IMTC Multimedia Standards Historical Archive contains contributions to
standards meetings, reports, records of IPR licensing declarations, copies
of standard organizations patent databases, publications such as journal
articles, books, etc.

Much of this information originated 10 to 25 years ago. Due to the huge
amount of information, and the difficulty to find old documentation,
archives containing this kind of information are incomplete, and must be
built up step by step. For example, the ITU keeps fairly good records on
ITU-T SG level, but none on the Rapporteurs Group level, which is the most
important for IPR work. In addition, prior to 1995, the majority of records
were still paper, making them almost inaccessible for today's purposes.

Thanks to contributions made by members, we are slowly building up the IMTC
archive. We would like to encourage members to submit their own old archived
records to the IMTC to help us adding value to the historical archive. These
contributions can be made in paper form, scanned copies of documents, or
electronic files. Anything related to our industry that can help us complete
our existing documentation is useful. We kindly ask members, willing to
submit their records, to first send a list of documents to the Secretariat
(jpolizotto@inventures.com). This will allow the IPR Activity Group to check
if those documents are not already archived in the database and that way
avoid submission of numerous duplicate records.

For any questions on the Historical Archive or submissions of documents,
please feel free to contact Jim Polizotto, IMTC Secretary
(jpolizotto@inventures.com).

Thank you and best regards,

Patrick Luthi
IMTC Vice President



---


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



From mmusic-bounces@ietf.org Wed May 23 06:48:34 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqoOO-0005Pq-PP; Wed, 23 May 2007 06:48:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqoON-0005Pg-Lm
	for mmusic@ietf.org; Wed, 23 May 2007 06:48:31 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqoOK-0005al-S2
	for mmusic@ietf.org; Wed, 23 May 2007 06:48:31 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4NAm3bo017193; Wed, 23 May 2007 13:48:24 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 13:48:22 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 13:48:22 +0300
Received: from [172.21.59.31] ([172.21.59.31]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 13:48:21 +0300
Message-ID: <46541BF5.6090701@nsn.com>
Date: Wed, 23 May 2007 13:48:21 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4651A081.8080608@nsn.com> <4651F62C.3090509@cisco.com>
	<46529D4B.8090701@nsn.com> <46532125.9050902@cisco.com>
In-Reply-To: <46532125.9050902@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 May 2007 10:48:21.0937 (UTC)
	FILETIME=[E1B50210:01C79D27]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
Cc: "Salvatore Loreto \(SA/ERI\)" <Salvatore.Loreto@ericsson.com>,
	Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
	mmusic <mmusic@ietf.org>,
	"Isomaki Markus \(Nokia-SIR/Espoo\)" <Markus.Isomaki@nokia.com>
Subject: [MMUSIC] Re: File-transfer issue 31: Errors when multiple hashes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Paul:

See some more inlines discussion


Paul Kyzivat wrote:
> I think we are close to converging.  More inline. (I'm trimming 
> extraneous text.)
> 
>     Paul
> 
> Miguel Garcia wrote:
> 
>>> It then gets ready to send the file, so it prepares the answer. In 
>>> the answer it needs to include hash information. As the draft was 
>>> written, it wasn't clear whether it was to echo the hash parameters 
>>> from the offer into the answer, or to include the hash algorithms 
>>> from the offer in the answer, with the hash values it computes for 
>>> the file. If the hash values requested are the same as those it 
>>> computes it doesn't matter, but if they are different it does matter.
>>
>> I think it is written:
>>
>> - Push scenario, Section 8.2.1:
>>
>>    If
>>    the offer contains one ore more 'hash' parameters in the 'file-
>>    selector' attribute, the answerer discards those with non-supported
>>    hashing algorithms and MUST copy the remaining (if any) to the 'file-
>>    selector' attribute of the answer.
>>
>> - Pull scenario, Section 8.2.2 (see also discussion at the end of this 
>> mail):
>>
>>    If the SDP offer included several
>>    'hash' parameters, the file sender SHOULD include at least one in the
>>    SDP answer, selected among those present in the offer and, at the
>>    same time, supported by the file sender.  If the SDP offer did not
>>    include a 'hash' parameter, the file sender SHOULD add one or more
>>    'hash' parameters, according to the supported hashing algorithms.
> 
> None of the above says that the sender computes the hash that it 
> includes. 

But it has to compute the has. Let me re-explain:
- Push scenario:
   If  a file sender is going to send a file along with its hash, then 
at some point in time the hash was computed for that file.

- Pull scenario:
   The offerer includes a file selector that includes one or more 
hashes. The draft says that the answerer chooses one hash and together 
with the other selectors, selects a file. This means that the file 
sender goes comparing the computed hashes of existing files with that in 
the offer.

In both cases the hash has been computed, perhaps earlier, not in 
realtime, but I think the time at which a hash is computed is an 
implementation issue.

What am I missing here?

> Copying the hash values from the offer seems to be perfectly 
> consistent with the above text. In fact, the above seems to demand 
> copying them rather than recomputing or verifying. And it could be an 
> easy and natural thing to do. But its the *wrong* thing to do if the 
> value hasn't been confirmed to be correct.





> 
>>> I think the following could be added to the end of 8.1.2:
>>>
>>> "When the File Receiver receives the answer, if the port number of 
>>> the answer for a file request is non-zero then it SHOULD receive the 
>>> file using the MSRP protocol. If the answer contains a supported 
>>> hashing algorithm, then the receiver SHOULD compute the hash of the 
>>> file after receipt and check against the hash received in the answer."
>>
>> I am fine with the text.. I will loose a bit the words, because MSRP 
>> is used only because it is indicated in the m= line, so it is possible 
>> that in the future we extend the mechanism to use other transfer 
>> protocols. I have a problem with the first "SHOULD", because it 
>> depends on an action done by the remote endpoint (because it has to 
>> send), so it is obviously a "should". I have also indicated what the 
>> user agent should do if the check fails (inform the user and consider 
>> that the file transfer failed). The current text reads:
>>
>>    When the file receiver receives the SDP answer, if the port number of
>>    the answer for a file request is non-zero then it should receive the
>>    file using the protocol indicated in the m= line.  If the SDP answer
>>    contains a supported hashing algorithm in the 'hash' parameter of the
>>    'file-selector' attribute, then the file receiver SHOULD compute the
>>    hash of the file after receipt and check against the hash received in
>>    the answer.  In case the computed hash does not match the one
>>    contained in the SDP answer, the file receiver SHOULD consider that
>>    the file transfer failed and SHOULD inform the user.
> 
> This seems fine.
> 
>>> In 8.2.2 I would suggest a change in the following:
>>>
>>>                                    ... If the SDP offer included several
>>>    'hash' parameters, the file sender SHOULD include at least one in the
>>>    SDP answer, selected among those present in the offer and, at the
>>>    same time, supported by the file sender.  If the SDP offer did not
>>>    include a 'hash' parameter, the file sender SHOULD add one or more
>>>    'hash' parameters, according to the supported hashing algorithms.
>>>
>>> changed as follows:
>>>
>>>                                    ... The file sender SHOULD add
>>>    one or more 'hash' parameters in the answer, with algorithms
>>>    supported by the file sender and values computed by the file sender,
>>>    and SHOULD include at least one with a hash algorithm selected among
>>>    those present in the offer. The file sender MUST NOT include a 'hash'
>>>    parameter with an algorithm that was present in the offer and a value
>>>    that differs from what was in the offer. (If a hash value computed
>>>    by the file sender differs from that specified by the file receiver,
>>>    the file sender can either send the file without the hash value or
>>>    reject the request with a 400 (Bad Request) response.
>>
>> I think we need to discuss the principles a bit more. To put things in 
>> context first: An file receiver (offerer) learned by some magic (e.g., 
>> resource event package draft) one or more hashes of a file. It selects 
>> one or more that it supports and included into the offer (the offerer 
>> is not going to add a hash algorithm it does not support). It sends 
>> the offer to the file receiver, who extracts one and only one hash 
>> algorithm to select the file (perhaps together with other selectors, 
>> that is irrelevant). Then, why in the heck does the file sender need 
>> to send MORE hash algorithms, (and presumably compute them). I think 
>> it is a waist of time and CPU cycles.
> 
> It doesn't NEED to. And the text I suggested doesn't require that. I 
> said "one or more" that are "supported by the file sender", at least one 
> of which has an algorithm included in the offer. One is enough to 
> satisfy all of those requirements. The sender can include others if it 
> wishes, mentioned in the offer or not.
> 
> Why would the sender include extras? Perhaps it keeps all the hashes 
> around for its files, and its simply easier to include them all than to 
> check which of them is an algorithm mentioned in the request.
> 
> If there are several in the answer, then the recipient can choose which 
> one to use for verifying the receipt of the file. It might choose an 
> easier one to compute than the one it requested.
> 
> Also, this unifies with the case where the offer included *no* hashes, 
> because none were known. In that case the sender doesn't know what 
> hashes the receiver supports, so sending multiples increases the odds 
> that the receiver will be able to check the hash.
> 
> Doesn't really matter. This just gives a little more latitude to the 
> sender without requiring any more work.

Ok, I can agree with this issue. So the answerer will include all the 
supported hashes he wants to include in the answer. Those are locally 
computed, not copied from the offer.


> 
>> Also, your text "The file sender MUST NOT include a 'hash' parameter 
>> with an algorithm that was present in the offer and a value that 
>> differs from what was in the offer". This will never happen with the 
>> scenario I mentioned, because:
>> a) there is only one chosen hash algorithm
>> b) the hash is used to select the file, if the hash was wrong, then it 
>> would not select a file.
> 
> I think it could still be possible, if the sender can include multiple 
> hashes. Suppose the offer included sha-1:ABC and md5:DEF. And suppose 
> the answerer/sender chose the sha-1 hash to select the file, so it does 
> actually have the sha-1:ABC hash. But suppose the sender's md5 hash 
> value for the file is CDE.
> 
> It could return 'sha-1:ABC md5:CDE' but that might expose the conflict 
> with what the offerer requested. This statement just prevents that 
> conflict.

If we go for the suggestion I had below, the error case is possible, but 
certainly unlikely. In any case, there should be at least one common 
hash in the offer and the answer, so the error does not have a side effect.

> 
> But I don't care much about this. It would simplify things to leave it out.
> 
>     Paul

I'll write some text around these lines and post it for further comments.

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Wed May 23 06:51:25 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HqoRB-0006wN-N9; Wed, 23 May 2007 06:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HqoR8-0006w8-9L
	for mmusic@ietf.org; Wed, 23 May 2007 06:51:22 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqoR6-00066O-5t
	for mmusic@ietf.org; Wed, 23 May 2007 06:51:22 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8DF0A214F3; Wed, 23 May 2007 12:51:19 +0200 (CEST)
X-AuditID: c1b4fb3e-b1a1dbb0000061ca-1a-46541ca7ffc1 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	74AC221537; Wed, 23 May 2007 12:51:19 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 12:51:19 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 12:51:18 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id C33DF2467;
	Wed, 23 May 2007 13:51:18 +0300 (EEST)
Message-ID: <46541CA6.1020605@ericsson.com>
Date: Wed, 23 May 2007 13:51:18 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Miguel Garcia <Miguel.Garcia@nsn.com>
Subject: Re: [MMUSIC] Re: File transfer verrsion -02
References: <464DA446.5020400@nsn.com>	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
	<4651ACCA.4090001@nsn.com>
In-Reply-To: <4651ACCA.4090001@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 May 2007 10:51:19.0067 (UTC)
	FILETIME=[4B48E6B0:01C79D28]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
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>
Errors-To: mmusic-bounces@ietf.org

Hi,

I agree we should keep it simple and refrain from defining a new attribute.

Cheers,

Gonzalo

Miguel Garcia wrote:
> Hi Mahesh:
> 
> Thanks for the comment.
> 
> I took a look at the vanilla MSRP draft 
> (draft-ietf-simple-message-sessions) and it already offers a 'max-size' 
> attribute with similar (mostly the same) semantics that you mention.
> 
>    An endpoint MAY indicate the maximum size message they wish to
>    receive using the max-size a-line attribute.  Max-size refers to the
>    complete message in octets, not the size of any one chunk.  Senders
>    SHOULD NOT exceed the max-size limit for any message sent in the
>    resulting session.  However, the receiver should consider max-size
>    value as a hint.
> 
> The difference between MSRP max-size and your proposed max-file-size is 
> that max-size comprises the CPIM overhead whereas max-file-size do not.
> 
> Honestly, I think the difference is on the order of hundreds of bytes at 
> maximum. I think we shouldn't be defining a new attribute for it.
> Which other view do we have on this one?
> 
> /Miguel
> 
> 
> 
> 
> Mahesh Anjanappa wrote:
>> hi Miguel,
>> A File  Receiver should be given the provision to indicate to the File
>> Sender as to
>> what is the maximum File size it is capable of receiving. This will be
>> especially
>> useful if the File Sneder does NOT provide the File-Size in the 
>> INVITE(SDP).
>>
>> For this i suggest the following
>> "A Receiver MAY indicate the maximum size MSRP message(translates to max
>> File Size) that it wishes to
>> receive by including  the max-size a-line attribute in the SDP of
>> 200OK(INVITE).
>> Max-size refers to the complete message in octets, not the size of any 
>> one
>> chunk.
>> Senders  SHALL NOT exceed the max-size limit for any message sent in the
>> resulting session".
>>
>> regards
>> Mahesh
>>
>>
>> ----- Original Message ----- From: "Miguel Garcia" 
>> <Miguel.Garcia@nsn.com>
>> To: "mmusic" <mmusic@ietf.org>
>> Sent: Friday, May 18, 2007 6:34 PM
>> Subject: File transfer verrsion -02
>>
>>
>>> I have submitted version -02 of the file transfer draft.
>>>
>>> Until it appears in the repository, you can fetch a copy from:
>>>
>>>
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.txt 
>>
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02.html 
>>
>>> and a diff version:
>>>
>> http://people.nokia.net/~miguel/drafts/draft-ietf-mmusic-file-transfer-mech-02-from-1.html 
>>
>>> The changes in this version are:
>>> - Rename of attributes:
>>>    s/icon/file-icon
>>>    s/disposition/file-disposition
>>>
>>> - Fixed SDP in example in Section 9.3 to include mime types.
>>>
>>> With this, I think the document is complete. I am not aware of any
>>> further open issues.
>>>
>>> Regards,
>>>
>>>      Miguel
>>> -- 
>>> Please note my new e-mail address: miguel.garcia at nsn.com
>>> Miguel A. Garcia           tel:+358-50-4804586
>>> Nokia Siemens Networks     Helsinki, Finland
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> 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 May 23 07:27:29 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hqp03-0002QH-TU; Wed, 23 May 2007 07:27:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hqp02-0002Ly-8V; Wed, 23 May 2007 07:27:26 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hqp01-00055p-Eo; Wed, 23 May 2007 07:27:26 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	ACBE520A8B; Wed, 23 May 2007 13:27:24 +0200 (CEST)
X-AuditID: c1b4fb3c-ac51ebb0000073d5-8c-4654251c774c 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	92F1E20947; Wed, 23 May 2007 13:27:24 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 13:27:24 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 May 2007 13:27:23 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id CF7AA2467;
	Wed, 23 May 2007 14:27:23 +0300 (EEST)
Message-ID: <4654251B.7000401@ericsson.com>
Date: Wed, 23 May 2007 14:27:23 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Eric Burger <eburger@bea.com>
Subject: Re: [MMUSIC] FW: [Speechsc] WGLC MRCPv2-12
References: <C278F99A.398F%eburger@bea.com>
In-Reply-To: <C278F99A.398F%eburger@bea.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 May 2007 11:27:24.0069 (UTC)
	FILETIME=[55B9FD50:01C79D2D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: speechsc@ietf.org, mmusic@ietf.org,
	"Magnus Westerlund \(KI/EAB\)" <magnus.westerlund@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Eric,

comedia was not designed to handle different m lines sharing a single 
TCP connection. Some time ago, the best practice was not to use the same 
port number in two m lines (assuming the same IP address). Nowadays that 
rule does not seem to apply any longer and some specs use the same port 
in different m lines.

For example, Section 8.1 of the draft below explains how to use a single 
TCP connection for different MSRP sessions. The trick there is that they 
fill the SDP parameters with dummy values and then define their own 
stuff in an MSRP-specific way:

http://www.ietf.org/internet-drafts/draft-ietf-simple-message-sessions-19.txt

If sharing a single TCP connection between different m lines is 
something we want to specify (and it should not be hard to specify), I 
would suggest that it is done in a way that can be reused by any 
upper-layer protocol so that we do not need to re-define the same stuff 
over and over again.

Something else to think about is TCP-ICE and its interactions with 
shared transport connections.

Cheers,

Gonzalo



Eric Burger wrote:
> OK, MMUSIC folks, can you help us SPEECHSC folks out?
> 
> Magnus noted the following may be an issue:
>> ------ Forwarded Message
>> From: Magnus Westerlund <magnus.westerlund@ericsson.com>
>> Date: Fri, 30 Mar 2007 09:12:56 -0700
> [snip]
>> In section 4.2 you define behavior for using the comedia a=connection
>> attribute with the TCP/MRCPv2 protocol. Based on the text and example
>> (add recognizer example starting on page 16) it seems that you try to
>> allow that multiple m= lines reuses the same TCP connection. However it
>> is far from obvious that comedia (RFC 4145) support this behavior. It
>> doesn't talk about any relation between multiple m= lines and their TCP
>> connections. I would recommend discussing this with MMUSIC.
> ------ End of Forwarded Message
> 
> The "section 4.2" referenced is to MRCPv2, draft-ietf-speechsc-mrcpv2:
> 
> When using TCP the m-lines MUST conform to comedia [10], which describes the
> usage of SDP for connection-oriented transport.
> [snip]
> The a=setup attribute, as described in comedia [10], MUST be "active" for
> the offer from the client and MUST be "passive" for the answer from the
> MRCPv2 server. The a=connection attribute MUST have a value of "new" on the
> very first control m-line offer from the client to an MRCPv2 server.
> Subsequent control m-line offers from the client to the MRCP server MAY
> contain "new" or "existing", depending on whether the client wants to set up
> a new connection or share an existing connection, respectively.
> 
> 
> 
> Do you think we are OK?  If not, why not, and how can we fix it?
> 
> Thanks.
> 
> 
> Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
> 
> _______________________________________________
> 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 May 24 06:02:30 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrA9K-00059Z-NB; Thu, 24 May 2007 06:02:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HrA9J-00059U-E0
	for mmusic@ietf.org; Thu, 24 May 2007 06:02:25 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrA9H-0004x6-VV
	for mmusic@ietf.org; Thu, 24 May 2007 06:02:25 -0400
Received: from epmmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JIJ00H2MIJYUV@mailout2.samsung.com> for mmusic@ietf.org;
	Thu, 24 May 2007 19:02:22 +0900 (KST)
Received: from MAHESHALAPTOP ([107.108.70.26])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0JIJ00HHIIJWWR@mmp2.samsung.com> for
	mmusic@ietf.org; Thu, 24 May 2007 19:02:22 +0900 (KST)
Date: Thu, 24 May 2007 15:38:29 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: [MMUSIC] File transfer verrsion -02 : Regarding Multiple File Transfer
To: Miguel Garcia <Miguel.Garcia@nsn.com>
Message-id: <005101c79deb$7ad42f70$1a466c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <464DA446.5020400@nsn.com>
	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
	<4651ACCA.4090001@nsn.com>
	<009a01c79bba$079b7780$1a466c6b@sisodomain.com>
	<4651DD4F.6050606@nsn.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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>
Errors-To: mmusic-bounces@ietf.org

hi Miguel,
>From Sec 8.1.3, i understand that in order for a Sender to send mulitple
Files,
an "m=" line per file needs to be introduced in the SDP.

So there will be a single SIP Session and multiple associated MSRP Sessions
(however, Single COnnection)
, each File being transferred over separate MSRP Session.

Please clarify how to Stop/Abort a Particular File Transfer among the 'n'
File Transfers
running.

regards
Mahesh


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



From mmusic-bounces@ietf.org Thu May 24 06:20:59 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrARG-0002ig-3h; Thu, 24 May 2007 06:20:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HrARE-0002bk-Q7
	for mmusic@ietf.org; Thu, 24 May 2007 06:20:56 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrARD-0006VF-D3
	for mmusic@ietf.org; Thu, 24 May 2007 06:20:56 -0400
Received: from epmmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JIJ009JJJET6P@mailout2.samsung.com> for mmusic@ietf.org;
	Thu, 24 May 2007 19:20:53 +0900 (KST)
Received: from MAHESHALAPTOP ([107.108.70.26])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0JIJ0018JJERVX@mmp1.samsung.com> for mmusic@ietf.org;
	Thu, 24 May 2007 19:20:53 +0900 (KST)
Date: Thu, 24 May 2007 15:57:00 +0530
From: Mahesh Anjanappa <mahesha@samsung.com>
Subject: [MMUSIC] draft-ietf-mmusic-file-transfer-mech-02::Clarification for
	"file transfer" from "file attached to IM",
To: Miguel Garcia <Miguel.Garcia@nsn.com>, mmusic@ietf.org
Message-id: <00a501c79dee$114c2a50$1a466c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0773769343=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0773769343==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_KNIci8yAV6R9zxvMjxgN3A)"

This is a multi-part message in MIME format.

--Boundary_(ID_KNIci8yAV6R9zxvMjxgN3A)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

hi Miguel
Please elaborate on what you mean by following two excerpts in Sec 1 of the draft-ietf-mmusic-file-transfer-mech-02.

1. "With MSRP it is possible to embed files as MIME objects inside the stream of instant messages. "

2." The recipient MUST be able to distinguish "file transfer" from "file attached to IM", allowing 
        the recipient to treat the cases differently."

regards
Mahesh

--Boundary_(ID_KNIci8yAV6R9zxvMjxgN3A)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1593" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>hi Miguel</FONT></DIV>
<DIV><FONT face=Arial size=2>Please elaborate on what you mean by following two 
excerpts in Sec 1 of the draft-ietf-mmusic-file-transfer-mech-02.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>1. "<FONT size=2>With MSRP it is possible to embed 
files as MIME objects inside the stream of instant messages. 
"<BR></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT size=2>2."</FONT></FONT><FONT face=Arial 
size=2><FONT size=2><FONT size=2>&nbsp;The recipient MUST be able to distinguish 
"file transfer" from "file attached to IM", allowing </FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT size=2><FONT size=2>&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp; the recipient to treat the cases 
differently."</DIV></FONT></FONT></FONT>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>regards</FONT></DIV>
<DIV><FONT face=Arial size=2>Mahesh</FONT></DIV></FONT></DIV></BODY></HTML>

--Boundary_(ID_KNIci8yAV6R9zxvMjxgN3A)--


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

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

--===============0773769343==--




From mmusic-bounces@ietf.org Thu May 24 08:39:11 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrCb0-00063B-0H; Thu, 24 May 2007 08:39:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HrCay-000630-8r
	for mmusic@ietf.org; Thu, 24 May 2007 08:39:08 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrCaw-0007FS-Qe
	for mmusic@ietf.org; Thu, 24 May 2007 08:39:08 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4OCcvw2021697; Thu, 24 May 2007 15:39:04 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:38:58 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:38:58 +0300
Received: from [172.21.59.40] ([172.21.59.40]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:38:58 +0300
Message-ID: <4655875F.9080500@nsn.com>
Date: Thu, 24 May 2007 15:38:55 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [MMUSIC] File transfer verrsion -02 : Regarding Multiple File
	Transfer
References: <464DA446.5020400@nsn.com>
	<007a01c79baf$f9555650$1a466c6b@sisodomain.com>
	<4651ACCA.4090001@nsn.com>
	<009a01c79bba$079b7780$1a466c6b@sisodomain.com>
	<4651DD4F.6050606@nsn.com>
	<005101c79deb$7ad42f70$1a466c6b@sisodomain.com>
In-Reply-To: <005101c79deb$7ad42f70$1a466c6b@sisodomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 May 2007 12:38:58.0285 (UTC)
	FILETIME=[7FB119D0:01C79E00]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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>
Errors-To: mmusic-bounces@ietf.org

Hi Mahesh:

Some inline discussion.

Mahesh Anjanappa wrote:
> hi Miguel,
> From Sec 8.1.3, i understand that in order for a Sender to send mulitple
> Files,
> an "m=" line per file needs to be introduced in the SDP.

Correct.


> So there will be a single SIP Session and multiple associated MSRP Sessions
> (however, Single COnnection)
> , each File being transferred over separate MSRP Session.

Correct: One SIP session, composed of several MSRP sessions, which may 
or may not be bound to the same TCP connection (I guess typically the 
will all share the same TCP connection).

> 
> Please clarify how to Stop/Abort a Particular File Transfer among the 'n'
> File Transfers
> running.

The sender can always abort an ongoing transfer by using regular MSRP 
procedures: sending an MSRP SEND message that contains the '#' 
continuation flag at the end of the end-line. Since this is part of an 
MSRP session, the MSRP session will be present in the From-Path, To-Path 
  headers. This allow to demultiplex this MSRP session from the rest.

If the receiving side wants to abort a transfer, I guess it should 
re-INVITE and set the appropriate port in the m= line to 0. The sending 
side should abort (as described in the previous paragraph).

/Miguel

> 
> regards
> Mahesh
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Thu May 24 08:46:26 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrCi2-0002gL-P9; Thu, 24 May 2007 08:46:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HrCi1-0002g5-3N
	for mmusic@ietf.org; Thu, 24 May 2007 08:46:25 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrChz-0008T1-Ku
	for mmusic@ietf.org; Thu, 24 May 2007 08:46:25 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4OCkJwe014017; Thu, 24 May 2007 15:46:21 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:46:07 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:46:07 +0300
Received: from [172.21.59.40] ([172.21.59.40]) by esebh102.NOE.Nokia.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:46:07 +0300
Message-ID: <4655890B.6090908@nsn.com>
Date: Thu, 24 May 2007 15:46:03 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Mahesh Anjanappa <mahesha@samsung.com>
Subject: Re: [MMUSIC] draft-ietf-mmusic-file-transfer-mech-02::Clarification
	for "file transfer" from "file attached to IM",
References: <00a501c79dee$114c2a50$1a466c6b@sisodomain.com>
In-Reply-To: <00a501c79dee$114c2a50$1a466c6b@sisodomain.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 May 2007 12:46:07.0418 (UTC)
	FILETIME=[7F7999A0:01C79E01]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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>
Errors-To: mmusic-bounces@ietf.org

Hi Majesh,

thanks for your comment. Inline answers.

Mahesh Anjanappa wrote:
> hi Miguel
> Please elaborate on what you mean by following two excerpts in Sec 1 of 
> the draft-ietf-mmusic-file-transfer-mech-02.
>  
> 1. "With MSRP it is possible to embed files as MIME objects inside the 
> stream of instant messages. "

The sentence is trying to say that *without* this draft, it is already 
possible to establish a session of instant messages. MSRP SEND requests 
can carry a text message or they can carry a MIME object that contains a 
file (think of an image). So, this draft is not bringing the capability 
of transmitting files in MSRP, which is already part of the vanilla MSRP 
draft.

> 2." The recipient MUST be able to distinguish "file transfer" from "file 
> attached to IM", allowing
>         the recipient to treat the cases differently."

So, here, by "file transfer" we mean the offer/answer exchange that 
allows the answerer to accept or reject a file operation before it 
actually takes place.

The "file attached to IM" refers to the previous point: an MSRP SEND 
request can carry either some text or a file.

BR,

        Miguel
>  
> regards
> Mahesh

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Helsinki, Finland


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



From mmusic-bounces@ietf.org Thu May 24 08:49:02 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrCkY-0004Za-H9; Thu, 24 May 2007 08:49:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrCkX-0004ZE-EV; Thu, 24 May 2007 08:49:01 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrCkV-0000X9-5r; Thu, 24 May 2007 08:49:01 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JIJ00ADOQ8FXA@szxga03-in.huawei.com>; Thu,
	24 May 2007 20:48:15 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JIJ00A31Q8EYX@szxga03-in.huawei.com>; Thu,
	24 May 2007 20:48:15 +0800 (CST)
Received: from j36340 ([10.164.5.105])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JIJ00C07Q8AZB@szxml03-in.huawei.com>; Thu,
	24 May 2007 20:48:14 +0800 (CST)
Date: Thu, 24 May 2007 20:48:10 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
To: jdrosen@cisco.com
Message-id: <000001c79e01$c93cf640$6905a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AceeAcjWFi3SPqvFTTKMJGlpNok7TQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: behave@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi, Jonathan:

I have read your draft and have a question to ask you. Would you please give
me some explanations?

ICE is making use of offer/answer mechanism to collect some candidate pairs
and check the connectivity between the local candidates and remote
candidates.  If a remote candidate is of type of relayed address, in my
understanding, when the agent want to send a STUN check packet to the remote
relayed address, it may not arrived at the remote candidate because the STUN
server may filter the packet because of no permission. 

In other words, Relay usage makes the STUN servers act as a NAT with end
independent mapping behavior and address dependent filtering behavior. If
there is no permission for a specific external peer, the STUN server will
filter the packet from the remote peer unless client has created permissions
for the remote peer in advance. 

I don't find any action taken make the agent to notify the STUN server relay
packets from the remote candidates.  Maybe I miss something and my
understanding is not correct. Could you please give me more explanations?

Regards!

--
Jiang XingFeng




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



From mmusic-bounces@ietf.org Thu May 24 08:56:42 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrCry-0006pb-6l; Thu, 24 May 2007 08:56:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HrCrw-0006gP-Id
	for mmusic@ietf.org; Thu, 24 May 2007 08:56:40 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrCrv-00037h-45
	for mmusic@ietf.org; Thu, 24 May 2007 08:56:40 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4OCuUQO014193; Thu, 24 May 2007 15:56:32 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:56:31 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:56:31 +0300
Received: from esdhcp04155.research.nokia.com ([172.21.41.55]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 24 May 2007 15:56:31 +0300
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: "ext JiangXingFeng" <jiang.x.f@huawei.com>
Date: Thu, 24 May 2007 15:56:50 +0300
User-Agent: KMail/1.9.6
References: <000001c79e01$c93cf640$6905a40a@china.huawei.com>
In-Reply-To: <000001c79e01$c93cf640$6905a40a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200705241556.51032.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 May 2007 12:56:31.0533 (UTC)
	FILETIME=[F379FDD0:01C79E02]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

On Thursday 24 May 2007 15:48:10 ext JiangXingFeng wrote:
> ICE is making use of offer/answer mechanism to collect some candidate pai=
rs
> and check the connectivity between the local candidates and remote
> candidates.  If a remote candidate is of type of relayed address, in my
> understanding, when the agent want to send a STUN check packet to the
> remote relayed address, it may not arrived at the remote candidate because
> the STUN server may filter the packet because of no permission.

Yes.

> In other words, Relay usage makes the STUN servers act as a NAT with end
> independent mapping behavior and address dependent filtering behavior. If
> there is no permission for a specific external peer, the STUN server will
> filter the packet from the remote peer unless client has created
> permissions for the remote peer in advance.

Yes.

> I don't find any action taken make the agent to notify the STUN server
> relay packets from the remote candidates.  Maybe I miss something and my
> understanding is not correct. Could you please give me more explanations?

You have to create the permission on the STUN relay server first. This is=20
typically done by sending a STUN/ICE connectivity check within a STUN Send=
=20
Indication through the STUN relay server.

Since ICE works fine from behind a NAT with independant mapping and=20
address-dependant filtering, it also works fine through a STUN relay server=
=20
all the same.

=2D-=20
R=E9mi Denis-Courmont

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



From mmusic-bounces@ietf.org Thu May 24 14:38:13 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrICR-0005Rv-T6; Thu, 24 May 2007 14:38:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrICP-0005RX-U7; Thu, 24 May 2007 14:38:09 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrICO-0000gv-J3; Thu, 24 May 2007 14:38:09 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-4.cisco.com with ESMTP; 24 May 2007 11:38:08 -0700
X-IronPort-AV: i="4.14,574,1170662400"; d="scan'208"; a="2446397:sNHT19242468"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l4OIc7MQ015449; 
	Thu, 24 May 2007 11:38:07 -0700
Received: from dwingwxp (dhcp-128-107-163-206.cisco.com [128.107.163.206])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4OIc7V1001646;
	Thu, 24 May 2007 18:38:07 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>
Date: Thu, 24 May 2007 11:38:07 -0700
Message-ID: <019d01c79e32$ac58c280$c6f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <000001c79e01$c93cf640$6905a40a@china.huawei.com>
Thread-Index: AceeAcjWFi3SPqvFTTKMJGlpNok7TQAMLaTw
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1793; t=1180031888;
	x=1180895888; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20A=20question=20on=20draft-ietf-mmusic-ice-
	15 |Sender:=20;
	bh=MhlgQBQQDiauUhUyzQEx8c9J/k4+EwmFrmpEbNDV4vU=;
	b=mSaYJ2RDGKQ/bjmLPy7YlfRVTNGBa91FIeUceXv7cs22xWxzG/NUxinKV6mbm46gAz+3/lov
	E2AyGwhs+Wx/3iyCbt4EvZqDREGqLvlgCr/n29yByXjExyqnYjMY4HyH;
Authentication-Results: sj-dkim-5; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: behave@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] RE: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

TURN's Set Active Destination accomplishes that.  See 
http://tools.ietf.org/html/draft-ietf-behave-turn-03#section-6.3.2

-d



> -----Original Message-----
> From: JiangXingFeng [mailto:jiang.x.f@huawei.com] 
> Sent: Thursday, May 24, 2007 5:48 AM
> To: jdrosen@cisco.com
> Cc: behave@ietf.org; mmusic@ietf.org
> Subject: [BEHAVE] A question on draft-ietf-mmusic-ice-15
> 
> Hi, Jonathan:
> 
> I have read your draft and have a question to ask you. Would 
> you please give
> me some explanations?
> 
> ICE is making use of offer/answer mechanism to collect some 
> candidate pairs
> and check the connectivity between the local candidates and remote
> candidates.  If a remote candidate is of type of relayed 
> address, in my
> understanding, when the agent want to send a STUN check 
> packet to the remote
> relayed address, it may not arrived at the remote candidate 
> because the STUN
> server may filter the packet because of no permission. 
> 
> In other words, Relay usage makes the STUN servers act as a 
> NAT with end
> independent mapping behavior and address dependent filtering 
> behavior. If
> there is no permission for a specific external peer, the STUN 
> server will
> filter the packet from the remote peer unless client has 
> created permissions
> for the remote peer in advance. 
> 
> I don't find any action taken make the agent to notify the 
> STUN server relay
> packets from the remote candidates.  Maybe I miss something and my
> understanding is not correct. Could you please give me more 
> explanations?
> 
> Regards!
> 
> --
> Jiang XingFeng
> 
> 
> 
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave

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



From mmusic-bounces@ietf.org Fri May 25 00:05:36 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrR3U-0006zB-NT; Fri, 25 May 2007 00:05:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrR3T-0006yp-VI; Fri, 25 May 2007 00:05:31 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrR3S-0005Bt-Ge; Fri, 25 May 2007 00:05:31 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JIK009ULWNVD8@szxga02-in.huawei.com>; Fri,
	25 May 2007 12:04:43 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JIK00BBBWNVCO@szxga02-in.huawei.com>; Fri,
	25 May 2007 12:04:43 +0800 (CST)
Received: from j36340 ([10.164.5.105])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JIK008S2WNRNO@szxml03-in.huawei.com>; Fri,
	25 May 2007 12:04:43 +0800 (CST)
Date: Fri, 25 May 2007 12:04:39 +0800
From: JiangXingFeng <jiang.x.f@huawei.com>
In-reply-to: <019d01c79e32$ac58c280$c6f0200a@amer.cisco.com>
To: 'Dan Wing' <dwing@cisco.com>
Message-id: <000001c79e81$d119d790$6905a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AceeAcjWFi3SPqvFTTKMJGlpNok7TQAMLaTwABOgDCA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: behave@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] RE: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

> TURN's Set Active Destination accomplishes that.  See
> http://tools.ietf.org/html/draft-ietf-behave-turn-03#section-6.3.2

Thanks for your reply. Besides Set Active Destination, there are some other
methods could do the same thing, such as Open, Send indications. 

Do we need to add more text to ICE draft and say that "before connectivity
check begins, agent A should create permission for Relayed address in order
to allow connectivity check's packet from other agent through the NAT and
reach the agent. A"?


---
JiangXingFeng



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



From mmusic-bounces@ietf.org Fri May 25 00:30:22 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrRRV-00061W-SE; Fri, 25 May 2007 00:30:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HrRRS-00060c-TE; Fri, 25 May 2007 00:30:18 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HrRRR-0001QX-J0; Fri, 25 May 2007 00:30:18 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 24 May 2007 21:30:17 -0700
X-IronPort-AV: i="4.14,577,1170662400"; 
	d="scan'208"; a="157374659:sNHT40034259"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l4P4UG0F020784; 
	Thu, 24 May 2007 21:30:16 -0700
Received: from dwingwxp ([10.32.240.198])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l4P4UG06013284;
	Fri, 25 May 2007 04:30:16 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'JiangXingFeng'" <jiang.x.f@huawei.com>
Date: Thu, 24 May 2007 21:30:15 -0700
Message-ID: <043a01c79e85$64e8dd10$c6f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <000001c79e81$d119d790$6905a40a@china.huawei.com>
Thread-Index: AceeAcjWFi3SPqvFTTKMJGlpNok7TQAMLaTwABOgDCAAAPRDUA==
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=757; t=1180067416;
	x=1180931416; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20A=20question=20on=20draft-ietf-mmusic-ice-
	15 |Sender:=20;
	bh=GyFqoNwVIks9iCxYxTI6fGa5jnqP616TtTOh8WOEV1o=;
	b=fo8dZtEu9HvOlk1G++PzDO06g08xPc6pctsXjGz3WwISqzFqmLBjQ07kVyHF/ipK5Xd7SH6C
	Z128J9dtM5XQ82G4ZxRiPchVOCZsT/UualfcVNIN4FWdMW1P6Gasvz2p;
Authentication-Results: sj-dkim-5; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: behave@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] RE: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

> > TURN's Set Active Destination accomplishes that.  See
> > http://tools.ietf.org/html/draft-ietf-behave-turn-03#section-6.3.2
> 
> Thanks for your reply. Besides Set Active Destination, there 
> are some other methods could do the same thing, such as Open, 
> Send indications. 
> 
> Do we need to add more text to ICE draft and say that "before 
> connectivity check begins, agent A should create permission 
> for Relayed address in order to allow connectivity check's 
> packet from other agent through the NAT and reach the agent. 
> A"?

It's not necessary -- the combination of the triggered checks
and retries by the answerer cause the permission and the
connectivity check to complete as soon as the permission is
created.

-d


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



From mmusic-bounces@ietf.org Mon May 28 05:04:12 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hsb91-0002WY-4H; Mon, 28 May 2007 05:04:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hsb8z-0002WD-K9
	for mmusic@ietf.org; Mon, 28 May 2007 05:04:01 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hsb8y-000276-Hm
	for mmusic@ietf.org; Mon, 28 May 2007 05:04:01 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C3276207D3; Mon, 28 May 2007 11:03:59 +0200 (CEST)
X-AuditID: c1b4fb3c-a94ecbb0000073d5-a4-465a9affd52b 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	0C920207BF; Mon, 28 May 2007 11:03:59 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 28 May 2007 11:03:45 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 28 May 2007 11:03:45 +0200
Message-ID: <465A9AF1.6040705@ericsson.com>
Date: Mon, 28 May 2007 11:03:45 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
Content-Type: multipart/mixed; boundary="------------040704070703030806010509"
X-OriginalArrivalTime: 28 May 2007 09:03:45.0187 (UTC)
	FILETIME=[1889B730:01C7A107]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.5 (/)
X-Scan-Signature: fe105289edd72640d9f392da880eefa2
Cc: Lakshminath Dondeti <ldondeti@qualcomm.com>
Subject: [MMUSIC] [Fwd: I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-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>
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.
--------------040704070703030806010509
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

This should be of interest for MMUSIC.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

--------------040704070703030806010509
Content-Type: message/rfc822;
	name="I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-01.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-01.txt"

X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw103.eemea.ericsson.se with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 25 May 2007 22:05:47 +0200
Received: from mailgw1.ericsson.se ([193.180.251.45]) by
	esealmw127.eemea.ericsson.se with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 25 May 2007 21:55:14 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C79F08.15581F80"
Received: from mailgw1.ericsson.se (unknown [127.0.0.1]) by
	mailgw1.ericsson.se (Symantec Mail Security) with ESMTP id
	60B3840694; Fri, 25 May 2007 21:55:14 +0200 (CEST)
Received: from megatron.ietf.org (odin.ietf.ORG [156.154.16.145]) (using TLSv1
	with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client
	certificate requested) by mailgw1.ericsson.se (Symantec Mail
	Security) with ESMTP id 91CEB406B7;
	Fri, 25 May 2007 21:55:13 +0200 (CEST)
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by
	megatron.ietf.org with esmtp (Exim 4.43) id 1Hrfnm-0002un-5p;
	Fri, 25 May 2007 15:50:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with
	esmtp (Exim 4.43) id 1HrfnX-0002qV-QT for i-d-announce@ietf.org;
	Fri, 25 May 2007 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by
	ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrfnX-0001hT-90 for
	i-d-announce@ietf.org; Fri, 25 May 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id
	BB5EE26ECF for <i-d-announce@ietf.org>;
	Fri, 25 May 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id
	1HrfnW-0007yN-JU for i-d-announce@ietf.org;
	Fri, 25 May 2007 15:50:02 -0400
Return-Path: <i-d-announce-bounces@ietf.org>
X-OriginalArrivalTime: 25 May 2007 19:55:14.0545 (UTC)
	FILETIME=[9C5F2610:01C79F06]
Errors-to: i-d-announce-bounces@ietf.org
X-Spam-Score: -2.5 (--)
List-Post: <mailto:i-d-announce@ietf.org>
List-Id: i-d-announce.ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
X-Brightmail-Tracker: AAAAAA==
X-AuditID: c1b4fb2d-b0dd6bb000005e3d-7c-46573f218ca0 
Content-class: urn:content-classes:message
Subject: I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-01.txt 
Date: Fri, 25 May 2007 21:50:02 +0200
Message-ID: <E1HrfnW-0007yN-JU@stiedprstage1.ietf.org>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-01.txt 
Thread-Index: AcefCBj9RYj4GS1HRzCq+8BKbXwNhg==
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Reply-To: <internet-drafts@ietf.org>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C79F08.15581F80
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C79F08.15581F80"


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

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


	Title		: SDP Attributes for OMA BCAST Service and Content Protection
	Author(s)	: L. Dondeti, A. Jerichow
	Filename	: draft-dondeti-oma-sip-sdp-attrs-01.txt
	Pages		: 7
	Date		: 2007-5-25
=09
This document provides descriptions of SDP attributes used by the
   Open Mobile Alliance's Broadcast Service and Content Protection
   specification.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-dondeti-oma-sip-sdp-attrs-01.tx=
t

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

Internet-Drafts are also available by anonymous FTP. Login with the=20
username "anonymous" and a password of your e-mail address. After=20
logging in, type "cd internet-drafts" and then=20
"get draft-dondeti-oma-sip-sdp-attrs-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
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-dondeti-oma-sip-sdp-attrs-01.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

------_=_NextPart_002_01C79F08.15581F80
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>I-D ACTION:draft-dondeti-oma-sip-sdp-attrs-01.txt </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>A New Internet-Draft is available from the on-line =
Internet-Drafts<BR>
directories.<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : SDP Attributes for OMA =
BCAST Service and Content Protection<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : L. Dondeti, A. =
Jerichow<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-dondeti-oma-sip-sdp-attrs-01.txt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 7<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2007-5-25<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
This document provides descriptions of SDP attributes used by the<BR>
&nbsp;&nbsp; Open Mobile Alliance's Broadcast Service and Content =
Protection<BR>
&nbsp;&nbsp; specification.<BR>
<BR>
A URL for this Internet-Draft is:<BR>
<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-dondeti-oma-sip-sdp-att=
rs-01.txt">http://www.ietf.org/internet-drafts/draft-dondeti-oma-sip-sdp-=
attrs-01.txt</A><BR>
<BR>
To remove yourself from the I-D Announcement list, send a message to<BR>
i-d-announce-request@ietf.org with the word unsubscribe in the body =
of<BR>
the message.<BR>
You can also visit <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1=
.ietf.org/mailman/listinfo/I-D-announce</A><BR>
to change your subscription settings.<BR>
<BR>
Internet-Drafts are also available by anonymous FTP. Login with the<BR>
username &quot;anonymous&quot; and a password of your e-mail address. =
After<BR>
logging in, type &quot;cd internet-drafts&quot; and then<BR>
&quot;get draft-dondeti-oma-sip-sdp-attrs-01.txt&quot;.<BR>
<BR>
A list of Internet-Drafts directories can be found in<BR>
<A =
HREF=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/A><BR>
or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</A><BR>
<BR>
Internet-Drafts can also be obtained by e-mail.<BR>
<BR>
Send a message to:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.<BR>
In the body type:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE =
/internet-drafts/draft-dondeti-oma-sip-sdp-attrs-01.txt&quot;.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
NOTE:&nbsp;&nbsp; The mail server at ietf.org can return the document =
in<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using =
the &quot;mpack&quot; utility.&nbsp; To use this<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command =
&quot;ENCODING mime&quot; before the &quot;FILE&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode the =
response(s), you will need &quot;munpack&quot; or<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail =
reader.&nbsp; Different MIME-compliant mail readers<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior, =
especially when dealing with<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME =
messages (i.e. documents which have been split<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages), =
so check your local documentation on<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these =
messages.<BR>
<BR>
Below is the data which will enable a MIME compliant mail reader<BR>
implementation to automatically retrieve the ASCII version of the<BR>
Internet-Draft.<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_002_01C79F08.15581F80--

------_=_NextPart_001_01C79F08.15581F80
Content-Type: application/octet-stream;
	name="ATT00534.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT00534.TXT
Content-Disposition: attachment;
	filename="ATT00534.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNy01LTI1MTA0NDA2LkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWRvbmRldGktb21hLXNpcC1z
ZHAtYXR0cnMtMDEudHh0DQo=

------_=_NextPart_001_01C79F08.15581F80
Content-Type: text/plain; charset="us-ascii";
	name="draft-dondeti-oma-sip-sdp-attrs-01.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-dondeti-oma-sip-sdp-attrs-01.txt
Content-Disposition: attachment;
	filename="draft-dondeti-oma-sip-sdp-attrs-01.txt"

RklMRSBERUxFVEVEDQotLS0tLS0tLS0tLS0NCg0KV2FybmluZyENCg0KVGhlIGF0dGFjaGVkIGZp
bGUgZHJhZnQtZG9uZGV0aS1vbWEtc2lwLXNkcC1hdHRycy0wMS5VUkwgaGFzIG5vdCBiZWVuIGRl
bGl2ZXJlZC4NClRoZSByZWFzb24gaXMgZHVlIHRvIHRoYXQgdGhlIGZpbHRlciBGSUxFIEZJTFRF
Uj0gdW5uYW1lZDogKi51cmwgaXMgaW4gZWZmZWN0Lg0KDQoNCkVyaWNzc29uIEdyb3VwIElU

------_=_NextPart_001_01C79F08.15581F80
Content-Type: text/plain;
	name="ATT00535.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT00535.txt
Content-Disposition: attachment;
	filename="ATT00535.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

------_=_NextPart_001_01C79F08.15581F80--


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

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

--------------040704070703030806010509--




From mmusic-bounces@ietf.org Tue May 29 06:41:35 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hsz8o-0004qH-1i; Tue, 29 May 2007 06:41:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hsz8m-0004qA-1S
	for mmusic@ietf.org; Tue, 29 May 2007 06:41:24 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hsz8k-0004o8-J7
	for mmusic@ietf.org; Tue, 29 May 2007 06:41:24 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4TAeoko017118; Tue, 29 May 2007 13:41:16 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 29 May 2007 13:41:06 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 29 May 2007 13:41:06 +0300
Received: from [172.21.154.97] ([172.21.154.97]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 29 May 2007 13:41:06 +0300
Message-ID: <465C0342.3010602@nsn.com>
Date: Tue, 29 May 2007 13:41:06 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 May 2007 10:41:06.0124 (UTC)
	FILETIME=[DC6BB8C0:01C7A1DD]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: "Willekens, Marc" <marc.willekens@nsn.com>
Subject: [MMUSIC] New draft: multiple times problem description:
	draft-garcia-mmusic-multiple-ptimes-problem-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi:

We have just submitted a new short draft that describes the problem with 
the lack of multiple packetization times in SDP.

The draft should be soon available in the traditional repositories. 
Until that time, you can fetch a copy from:

http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-multiple-ptimes-problem-00.txt
http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-multiple-ptimes-problem-00.html

We are aware that the issue has been discussed in the past, without a 
clear conclusion on whether a problem exists. We believe there is an 
interoperability problem, and thus, we are soliciting comments about it. 
At this stage, we are not discussing solutions yet, we rather agree 
first that there is a problem that needs to be solved.

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland


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



From mmusic-bounces@ietf.org Tue May 29 13:50:31 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht5q0-0008Ih-1A; Tue, 29 May 2007 13:50:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht5py-0008IM-LO; Tue, 29 May 2007 13:50:26 -0400
Received: from mail5.primus.ca ([216.254.141.172] helo=smtp-04.primus.ca)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Ht5pw-0007eR-OD; Tue, 29 May 2007 13:50:26 -0400
Received: from [216.13.42.68] (helo=[10.10.80.124])
	by smtp-04.primus.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.50)
	id 1Ht5q4-0003pa-Fx; Tue, 29 May 2007 13:50:32 -0400
In-Reply-To: <043a01c79e85$64e8dd10$c6f0200a@amer.cisco.com>
References: <043a01c79e85$64e8dd10$c6f0200a@amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0F2C075D-A4CF-4287-A228-CF2979624B30@magma.ca>
Content-Transfer-Encoding: 7bit
From: Philip Matthews <philip_matthews@magma.ca>
Date: Tue, 29 May 2007 13:50:34 -0400
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Authenticated: philip_matthews - ([10.10.80.124]) [216.13.42.68]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: behave@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Re: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


On 25-May-07, at 00:30 , Dan Wing wrote:

>>> TURN's Set Active Destination accomplishes that.  See
>>> http://tools.ietf.org/html/draft-ietf-behave-turn-03#section-6.3.2
>>
>> Thanks for your reply. Besides Set Active Destination, there
>> are some other methods could do the same thing, such as Open,
>> Send indications.
>>
>> Do we need to add more text to ICE draft and say that "before
>> connectivity check begins, agent A should create permission
>> for Relayed address in order to allow connectivity check's
>> packet from other agent through the NAT and reach the agent.
>> A"?
>
> It's not necessary -- the combination of the triggered checks
> and retries by the answerer cause the permission and the
> connectivity check to complete as soon as the permission is
> created.

Just a bit more clarification here.

"Set Active Destination" is one way to install a filtering entry for the
remote peer in the TURN server, but there is another way.

Consider two peers, L and R, which are behind different NATs.
L uses a TURN server T.

If R sends a connectivity check to L's allocated address on T
before anything else happens, then you are correct that T will
discard the packet. However, this will install a filtering entry
into R's local NAT.
Then when L sends a connectivity check from T towards R,
this will install a filtering entry on T for R, and this connectivity
check packet will also get through R's NAT because of the
previously installed filtering entry.

If the order is reversed (L sends first), then a connectivity check
from L's allocated address on T towards R will be dropped by
R's NAT, but will install a filtering entry on T.
Then when R sends a connectivity check from R to L's address
on T, this connectivity check will get through because of the
previously installed filtering entry on T.


To summarize:
If R sends first, then its connectivity check packets get dropped
by T until L sends its first packet towards R.
If L sends first, then its connectivity check packets get dropped
by R's NAT until R sends its first packet towards L's address on T.

In other words, the packets do not get through until both ends try
to send. This is the reason that ICE defines a priority function for
candidate pairs -- so both ends will send checks at approximately
the same time.

- Philip

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



From mmusic-bounces@ietf.org Tue May 29 21:35:31 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtD5v-0005AA-UC; Tue, 29 May 2007 21:35:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HtD5v-0005A3-3z
	for mmusic@ietf.org; Tue, 29 May 2007 21:35:23 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtD5t-00060c-PP
	for mmusic@ietf.org; Tue, 29 May 2007 21:35:23 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-4.cisco.com with ESMTP; 29 May 2007 18:35:21 -0700
X-IronPort-AV: i="4.14,590,1170662400"; d="scan'208"; a="3107916:sNHT20790666"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l4U1ZLZe004883; 
	Tue, 29 May 2007 18:35:21 -0700
Received: from dwingwxp ([10.32.240.194])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4U1ZKV1014631;
	Wed, 30 May 2007 01:35:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Miguel Garcia'" <Miguel.Garcia@nsn.com>, "'mmusic'" <mmusic@ietf.org>
Subject: RE: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Date: Tue, 29 May 2007 18:35:19 -0700
Message-ID: <0b5e01c7a25a$c8f675a0$c6f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <465C0342.3010602@nsn.com>
Thread-Index: Aceh3fyIPFb3GUFTTjKBocnO7d7xDAAfFKqQ
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2495; t=1180488921;
	x=1181352921; c=relaxed/simple; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[MMUSIC]=20New=20draft=3A=20multiple=20times=20proble
	m=20description=3Adraft-garcia-mmusic-multiple-ptimes-problem-00.txt
	|Sender:=20; bh=utzqzqagDgOL7//7Khz69poOWcCtRq/YbPCcJrVt5/Q=;
	b=YbeEihqK49A3ACC40YFKrqTSyJVCPP3un45hswXh9JuLuhr7yuiRe6H0wfcOKnse5yeaW2yx
	yj1SURDdn3CW3qNStZgdxrTFYNKSFxAYd541NlTmcBnA+o5wXRcs2d7j;
Authentication-Results: sj-dkim-8; header.From=dwing@cisco.com; dkim=pass (s
	ig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: "'Willekens, Marc'" <marc.willekens@nsn.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Would a solution that meets REQ-10 and REQ-20 from
draft-ietf-mmusic-sdp-capability-negotiation-reqts also resolve the ptime
problem?

   REQ-10: It MUST be possible to indicate and negotiate alternative 
   media formats on a per media stream basis. 

      For example, many implementations support multiple codecs, but 
      only one at a time.  Changes between codecs cannot be done on-
      the-fly, e.g. when receiving a simple RTP payload type change. 

   REQ-20: It MUST be possible to indicate and negotiate alternative 
   attribute values ("a=") on a per media stream basis.  

      For example, T.38 [T38] defines new attributes that may need to 
      be conveyed as part of a capability. Also, alternative SRTP 
      keying mechanisms (e.g. [SDES] and [KMGMT]) may use SDP 
      attributes to negotiate SRTP keying material. 

I noticed your document didn't reference
draft-ietf-mmusic-sdp-capability-negotiation-reqts, but I think there is an
overlap of a requirement you have and the solution proposed in
draft-ietf-mmusic-sdp-capability-negotiation-05.txt.

-d


> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.Garcia@nsn.com] 
> Sent: Tuesday, May 29, 2007 3:41 AM
> To: mmusic
> Cc: Willekens, Marc
> Subject: [MMUSIC] New draft: multiple times problem 
> description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
> 
> Hi:
> 
> We have just submitted a new short draft that describes the 
> problem with 
> the lack of multiple packetization times in SDP.
> 
> The draft should be soon available in the traditional repositories. 
> Until that time, you can fetch a copy from:
> 
> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
> tiple-ptimes-problem-00.txt
> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
> tiple-ptimes-problem-00.html
> 
> We are aware that the issue has been discussed in the past, without a 
> clear conclusion on whether a problem exists. We believe there is an 
> interoperability problem, and thus, we are soliciting 
> comments about it. 
> At this stage, we are not discussing solutions yet, we rather agree 
> first that there is a problem that needs to be solved.
> 
> /Miguel
> -- 
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Siemens Networks     Espoo, Finland
> 
> 
> _______________________________________________
> 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 May 30 02:21:40 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtHYt-000760-2W; Wed, 30 May 2007 02:21:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HtHYr-00075v-PG
	for mmusic@ietf.org; Wed, 30 May 2007 02:21:33 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtHYo-00018G-6q
	for mmusic@ietf.org; Wed, 30 May 2007 02:21:33 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4U6LF84018608; Wed, 30 May 2007 09:21:21 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 May 2007 09:21:17 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 May 2007 09:21:18 +0300
Received: from [172.21.154.97] ([172.21.154.97]) by esebh102.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 May 2007 09:21:17 +0300
Message-ID: <465D17DD.10207@nsn.com>
Date: Wed, 30 May 2007 09:21:17 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
References: <0b5e01c7a25a$c8f675a0$c6f0200a@amer.cisco.com>
In-Reply-To: <0b5e01c7a25a$c8f675a0$c6f0200a@amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 May 2007 06:21:17.0466 (UTC)
	FILETIME=[BB4507A0:01C7A282]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 'mmusic' <mmusic@ietf.org>, "'Willekens, Marc'" <marc.willekens@nsn.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi Dan:

Thanks for the reaction. Some inline discussion.

Dan Wing wrote:
> Would a solution that meets REQ-10 and REQ-20 from
> draft-ietf-mmusic-sdp-capability-negotiation-reqts also resolve the ptime
> problem?
> 
>    REQ-10: It MUST be possible to indicate and negotiate alternative 
>    media formats on a per media stream basis. 

No, this isn't the problem we are trying to tackle, because this 
requirement speaks about "alternative media formats" and speaks "on a 
per media stream basis".

However, our problem is not about alternative media formats, but about 
"specific parameters" and is not "on a per media stream basis" but "on a 
per media format (or codec) basis".

> 
>       For example, many implementations support multiple codecs, but 
>       only one at a time.  Changes between codecs cannot be done on-
>       the-fly, e.g. when receiving a simple RTP payload type change. 

Right... but this seems to be a different problem than the one we 
describe in the draft.

> 
>    REQ-20: It MUST be possible to indicate and negotiate alternative 
>    attribute values ("a=") on a per media stream basis.  

Again, the "on a per media stream basis" does not fulfill the 
requirement of the draft. It should say "on a per media type basis".

> 
>       For example, T.38 [T38] defines new attributes that may need to 
>       be conveyed as part of a capability. Also, alternative SRTP 
>       keying mechanisms (e.g. [SDES] and [KMGMT]) may use SDP 
>       attributes to negotiate SRTP keying material. 
> 
> I noticed your document didn't reference
> draft-ietf-mmusic-sdp-capability-negotiation-reqts, but I think there is an
> overlap of a requirement you have and the solution proposed in
> draft-ietf-mmusic-sdp-capability-negotiation-05.txt.

At this stage, the goal of the draft is just to highlight the problem 
and serve for deriving requirements, which we are doing in this thread. 
I am not sure how to reference your requirements...

As for the solution, the solution is space is quite broad, ranging from 
any of the proprietary solutions that have been specified elsewhere to 
the SDP capability negotiation, to SDP grouping of media, or perhaps 
others.

I would prefer that we don't derive the discussion to discuss a solution 
until we agree that there is a problem to be solved.

BR,

       Miguel
> 
> -d
> 
> 
>> -----Original Message-----
>> From: Miguel Garcia [mailto:Miguel.Garcia@nsn.com] 
>> Sent: Tuesday, May 29, 2007 3:41 AM
>> To: mmusic
>> Cc: Willekens, Marc
>> Subject: [MMUSIC] New draft: multiple times problem 
>> description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
>>
>> Hi:
>>
>> We have just submitted a new short draft that describes the 
>> problem with 
>> the lack of multiple packetization times in SDP.
>>
>> The draft should be soon available in the traditional repositories. 
>> Until that time, you can fetch a copy from:
>>
>> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
>> tiple-ptimes-problem-00.txt
>> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
>> tiple-ptimes-problem-00.html
>>
>> We are aware that the issue has been discussed in the past, without a 
>> clear conclusion on whether a problem exists. We believe there is an 
>> interoperability problem, and thus, we are soliciting 
>> comments about it. 
>> At this stage, we are not discussing solutions yet, we rather agree 
>> first that there is a problem that needs to be solved.
>>
>> /Miguel
>> -- 
>> Miguel A. Garcia           tel:+358-50-4804586
>> Nokia Siemens Networks     Espoo, Finland
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mmusic

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland


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



From mmusic-bounces@ietf.org Wed May 30 23:55:46 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtblE-0006BS-Bn; Wed, 30 May 2007 23:55:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HtblD-0006BN-EQ
	for mmusic@ietf.org; Wed, 30 May 2007 23:55:39 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Htbks-0003Bq-0m
	for mmusic@ietf.org; Wed, 30 May 2007 23:55:39 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 30 May 2007 20:55:17 -0700
X-IronPort-AV: i="4.14,596,1170662400"; 
	d="scan'208,217"; a="156728602:sNHT267702903"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l4V3tHE4006823; 
	Wed, 30 May 2007 20:55:17 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l4V3tHtV026245;
	Thu, 31 May 2007 03:55:17 GMT
Received: from xmb-sjc-233.amer.cisco.com ([128.107.191.88]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 May 2007 20:55:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Date: Wed, 30 May 2007 20:55:15 -0700
Message-ID: <CDB8E728D94C3A48BAACD57F390C40220329DE2C@xmb-sjc-233.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Thread-Index: AcejN38aYj5Tf3DMRSKH4+YWZVbs7A==
From: "Joe Stone \(joestone\)" <joestone@cisco.com>
To: <Miguel.Garcia@nsn.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 31 May 2007 03:55:16.0900 (UTC)
	FILETIME=[7FFA7E40:01C7A337]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=27559; t=1180583717;
	x=1181447717; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=joestone@cisco.com;
	z=From:=20=22Joe=20Stone=20\(joestone\)=22=20<joestone@cisco.com>
	|Subject:=20RE=3A=20[MMUSIC]=20New=20draft=3A=20multiple=20times=20proble
	m=20description=3Adraft-garcia-mmusic-multiple-ptimes-problem-00.txt
	|Sender:=20; bh=FVMPeoRgjwxVhvtGPH414TOkYb90/nNr+Vz6JnsBhpo=;
	b=XWVpheI+H37TY9O+K0W53ciaWtbWQkUpW8QISUbe3jkvtuzNAHnJQYO/W86x3nlJOyB3wYnT
	v0jGyLp8I4/gAI+LzG3V6nRrBN/4rJ5+C30vNnRf5Sq6RPhzG1BCDKtw;
Authentication-Results: sj-dkim-2; header.From=joestone@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 645960076aa293effd9740db2f975dc3
Cc: 
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1290680050=="
Errors-To: mmusic-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1290680050==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A337.7FD5696E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A337.7FD5696E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think think that your Problem Statement has short-changed the
"maxmptime" SDP attribute of V.152,

	One of these mechanisms is the 'maxmptime' attribute, defined
	in the ITU-T Recommendation V.152 [ITU.V152], which "indicates
the
	supported packetization period for all codec payload types". =20

The complete definition of the 'maxmptime' SDP attribute follows,

	In addition to negotiating support of V.152 and the
corresponding RTP payload type, a V.152 implementation should include
the 'maxmptime' attribute (maximum multiple ptime) to indicate the
supported packetisation period for all codec payload types.=20
	=20
	a=3Dmaxmptime:<list of packet times separated by space>
	This attribute is a media-level attribute. The maxmptime
attribute defines a list of maximum packetisation time values, expressed
in milliseconds, the endpoint is capable of using (sending and
receiving) for this connection. There shall be precisely one entry in
the list for each <format> entry provided in the "m=3D" line. Each entry
is separated by a space. Entry number j in this list defines the maximum
packetisation time for entry number j in the "m=3D" line. The first =
entry
in the list shall be a decimal number whereas subsequent entries in the
list shall be either a decimal number or a hyphen. For those media
formats where a single maximum packetisation rate does not apply (e.g.
non- voice codecs such as telephone-event or comfort noise), a hyphen
("-") shall be included at the corresponding location in the list of
packetisation periods.
	When receiving an SDP session description the maxmptime
attribute conveys the list of maximum packetisation periods that the
remote endpoint is capable of using for this connection; one for each
media format in the "m=3D" line. For media formats whose packetization
period is specified as a hyphen ("-"), the VBD gateway shall use one of
the maximum packetization periods that was actually specified in the
list.=20
	The "a=3Dptime" attribute  defined in RFC 2327 shall be ignored if
the SDP session description contains the "maxmptime" attribute.=20
	If the "maxmptime" attribute is absent, then the value of the
"ptime" attribute, if present, shall be taken as indicating the
packetization period for all codecs present in the "m=3D" line.
	If neither the 'ptime' nor 'maxmptime' attribute are present in
the SDP session description, then a V.152 implementation shall assume
the default packetisation period defined in RFC3550 (which is 20 ms for
G.711 and G.726-32k). A V.152 implementation shall not transmit V.152
packets with a packetisaton time greater other than the one offered by
the remote end.

With the 'maxmptime' SDP attribute, there is one maximum packetization
period value (possibly "-") for each media format (payload type) in the
media description.
=20
You've misrepresented the PacketCable 'mptime' SDP attribute,
=20
   Another
   one is the 'mptime' attribute, defined in the PacketCable Network-
   Based Call Signaling Protocol Specification [PKT.PKT-SP-EC-MGCP],
   which indicates "a list of packetization period values the endpoint
   is capable of using (sending and receiving) for this connection".
   While all have similar semantics, there is obviously no
   interoperability between them, creating a nightmare for the
   implementor who happens to be defining a common SDP stack for
   different applications.

defined in the PacketCable Network-Based Call Signaling Protocol
Specification,
=20
=20
http://www.packetcable.com/downloads/specs/PKT-SP-NCS1.5-I03-040712.pdf
=20
and the PacketCable PSTN Gateway Call Signaling Protocol Specification,
=20
=20
http://www.packetcable.com/downloads/specs/PKT-SP-TGCP1.5-I03-040712.pdf
=20
The 'mptime' SDP attribute is more than "a list of packetization period
values the endpoint is capable of using (sending and receiving) for this
connection". The complete definition of the 'mptime' SDP attribute
follows,

	mptime:
	=20
	This attribute is a media-level attribute defined by
PacketCable. The mptime attribute defines a list of packetization
	period values the endpoint is capable of using (sending and
receiving) for this connection.
=09

		Send: The mptime attribute MUST be present. There MUST
be precisely one entry in the list for
		each <format> entry provided in the "m=3D" line. Entry
number j in this list defines the
		packetization period for entry number j in the "m=3D"
line. The first entry in the list MUST be a
		decimal number whereas subsequent entries in the list
MUST be either a decimal number or a
		hyphen. For those media formats where a single
packetization rate does not apply (e.g., nonvoice
		codecs such as telephone-event or comfort noise), a
hyphen ("-") MUST be encoded at
		the corresponding location in the list of packetization
periods.
		=20
	=09
		Receive: Conveys the list of packetization periods that
the remote endpoint is capable of using for this
		connection; one for each media format in the "m=3D" line.
For media formats whose
		packetization period is specified as a hyphen ("-"), the
endpoint MUST use one of the
		packetization periods that was actually specified in the
list. If the "mptime" attribute is
		absent, then the value of the "ptime" attribute, if
present, MUST be taken as indicating the
		packetization period for all codecs present in the "m=3D"
line.

and note the PacketCable semantics related to the 'ptime' SDP attribute,

	ptime:
=09

		Send: The ptime SHOULD be sent if it was received in a
Remote Connection Descriptor or if the
		CMS used the packetization period ('p:')
LocalConnectionOption.
		=20
	=09
		Receive: The field MUST be ignored if the SDP contains
the "mptime" attribute (as required in
		PacketCable compliant devices). If the "mptime"
attribute is not present, then this field is
		used to define the packetization interval for all codecs
present in the SDP description and the
		MTA MUST use the ptime in the calculation of QoS
reservations.

With the 'mptime' SDP attribute, there is one packetization period value
(possibly "-") for each media format (payload type) in the media
description.
=20
There's no "interoperability nightmare" within the context in which the
'mptime' SDP attribute is defined. The above semantics state that the
'mptime' SDP attribute takes precedence over the 'ptime' SDP attribute,
if present. An implementation which does not recognize the 'mptime' SDP
attribute must ignore it. Note that similar precedence rules *could* be
defined between the 'maxptime' and 'maxmptime' SDP attributes.=20
=20
Your Problem Statement should address the issue of backward
compatibility. Regardless of your final solution, the proposed syntax
and semantics must be backward compatible with existing implementations.
PacketCable addresses backward compatibility through the precedence
rule, the fundamental SDP principle of ignoring unrecognized attributes,
"offers" which include both old and new syntax and "answers" which are
consistent (in terms of syntax) with "offers".
=20
I think that you've understated the problem of existing packetization
period semantics being nothing more than a preference or recommendation
(as it relates to actually sending based on the "negotiated"
packetization period). If we can agree on per media format packetization
period syntax and semantics, have we really solved the problem if the
"negotiated" packetization period is nothing more than a recommendation?
This problem (the lack of "strict" negotiation) isn't unique to
packetization period. I think that there's a general solution that we
can discuss at a later date.
=20
I appreciate the fact that you're attempting to finally bring closure to
this long-standing issue.
=20
Joe
=20

------_=_NextPart_001_01C7A337.7FD5696E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3086" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D510054901-31052007>I =
think think that=20
your Problem Statement has short-changed the "maxmptime" SDP attribute =
of=20
V.152,</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT><SPAN class=3D510054901-31052007><FONT face=3DArial =
size=3D2>One of these=20
  mechanisms is the 'maxmptime' attribute, defined<BR>in the ITU-T=20
  Recommendation V.152 [ITU.V152], which "indicates the<BR>supported=20
  packetization period for all codec payload types".&nbsp;=20
</FONT></DIV></BLOCKQUOTE>
<DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><SPAN lang=3DEN-GB=20
style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE"><FONT=20
face=3DArial size=3D2>The complete definition of the '<SPAN=20
class=3D510054901-31052007>maxm</SPAN>ptime' SDP attribute=20
follows,</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><SPAN =
lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE"><FONT=20
  size=3D2><SPAN class=3D510054901-31052007></SPAN><FONT face=3DArial>In =
addition to=20
  negotiating support of V.152 and the corresponding RTP payload type, a =
V.152=20
  implementation should include the &#8216;maxmptime&#8217; attribute =
(maximum multiple=20
  ptime) to indicate the supported packetisation period for all codec =
payload=20
  types.&nbsp;</FONT></FONT></SPAN></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><SPAN =
lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE"></SPAN><SPAN=20
  lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE; mso-bidi-font-size: 12.0pt"><?xml:namespace=20
  prefix =3D o ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p><FONT=20
  face=3DArial size=3D2>&nbsp;</FONT></o:p></SPAN></DIV>
  <DIV class=3DSDP style=3D"MARGIN: 0in 0in 0pt 134.65pt"><SPAN =
lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun"><FONT size=3D2><FONT=20
  face=3DArial>a=3Dmaxmptime:&lt;list of packet times separated by=20
  space&gt;<o:p></o:p></FONT></FONT></SPAN></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; mso-fareast-font-family: SimSun; =
mso-fareast-language: ZH-CN; mso-bidi-language: HE">This=20
  attribute is a media-level attribute. The maxmptime attribute defines =
a list=20
  of</SPAN><SPAN lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">=20
  maximum <SPAN style=3D"LAYOUT-GRID-MODE: line">packetisation time =
values,=20
  expressed in milliseconds, the endpoint is capable of using (sending =
and=20
  receiving) for this connection. There shall be precisely one entry in =
the<SPAN=20
  style=3D"COLOR: maroon"> </SPAN>list for each &lt;format&gt; entry =
provided in=20
  the "m=3D" line. Each entry is separated by a space. Entry number j in =
this=20
  list<SPAN style=3D"COLOR: maroon"> </SPAN>defines the maximum =
packetisation time=20
  for entry number j in the "m=3D" line. The first entry in<SPAN=20
  style=3D"COLOR: maroon"> </SPAN>the list shall be a decimal number =
whereas=20
  subsequent entries in the list shall be<SPAN style=3D"COLOR: maroon">=20
  </SPAN>either a decimal number or a hyphen. For those media formats =
where a=20
  single<SPAN style=3D"COLOR: maroon"> </SPAN>maximum<SPAN =
style=3D"COLOR: maroon">=20
  </SPAN>packetisation rate does not apply (e.g. non- voice codecs such =
as=20
  telephone-event or<SPAN style=3D"COLOR: maroon"> </SPAN>comfort =
noise), a hyphen=20
  ("-") shall be included at the corresponding location in the<SPAN=20
  style=3D"COLOR: maroon"> </SPAN>list of packetisation=20
  periods.</SPAN><o:p></o:p></SPAN></FONT></FONT></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; mso-fareast-font-family: SimSun; =
mso-fareast-language: ZH-CN; mso-bidi-language: HE">When=20
  receiving an SDP </SPAN><SPAN lang=3DEN-GB>session =
description</SPAN><SPAN=20
  lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; mso-fareast-font-family: SimSun; =
mso-fareast-language: ZH-CN; mso-bidi-language: HE">=20
  the maxmptime attribute conveys the list of maximum packetisation =
periods that=20
  the remote endpoint is capable of using<SPAN style=3D"COLOR: maroon"> =
</SPAN>for=20
  this connection; one for each media format in the "m=3D" line. For =
media=20
  formats<SPAN style=3D"COLOR: maroon"> </SPAN>whose packetization =
period is=20
  specified as a hyphen ("-"), the VBD gateway shall use one<SPAN=20
  style=3D"COLOR: maroon"> </SPAN>of the maximum packetization periods =
that was=20
  actually specified in the list. <o:p></o:p></SPAN></FONT></FONT></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial><SPAN lang=3DEN-GB style=3D"LAYOUT-GRID-MODE: line">The =
&#8220;a=3Dptime&#8221;=20
  attribute&nbsp; defined in RFC 2327 shall be ignored if the SDP =
</SPAN><SPAN=20
  lang=3DEN-GB>session description <SPAN style=3D"LAYOUT-GRID-MODE: =
line">contains=20
  the "maxmptime" attribute. =
<o:p></o:p></SPAN></SPAN></FONT></FONT></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; COLOR: black; =
mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">If=20
  the "maxmptime"</SPAN><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; COLOR: maroon; =
mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">=20
  </SPAN><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; COLOR: black; =
mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">attribute=20
  is absent, then the value of the "ptime" attribute, if present, shall =
be=20
  taken</SPAN><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; COLOR: maroon; =
mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">=20
  </SPAN><SPAN lang=3DEN-GB=20
  style=3D"LAYOUT-GRID-MODE: line; COLOR: black; =
mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE">as=20
  indicating the packetization period for all codecs present in the =
"m=3D"=20
  line.<o:p></o:p></SPAN></FONT></FONT></DIV>
  <DIV class=3DMsoNormal style=3D"MARGIN: 6pt 0in 0pt"><FONT =
size=3D2><FONT=20
  face=3DArial><SPAN lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE; mso-bidi-font-size: 12.0pt">If=20
  neither the &#8216;ptime&#8217; nor &#8216;maxmptime&#8217; attribute =
are present in the SDP=20
  </SPAN><SPAN lang=3DEN-GB>session description,</SPAN><SPAN =
lang=3DEN-GB=20
  style=3D"mso-fareast-font-family: SimSun; mso-fareast-language: ZH-CN; =
mso-bidi-language: HE; mso-bidi-font-size: 12.0pt">=20
  then a V.152 implementation shall assume the default packetisation =
period=20
  defined in RFC3550 (which is 20 ms for G.711 and G.726-32k). A V.152=20
  implementation shall not transmit V.152 packets with a packetisaton =
time=20
  greater other than the one offered by the remote=20
  end.</SPAN></FONT></FONT></SPAN></FONT></DIV></BLOCKQUOTE><FONT =
face=3DArial=20
size=3D2><SPAN class=3D510054901-31052007>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2>With the 'maxmptime' SDP attribute, there is one maximum =
packetization=20
period value (possibly "-") for each media format (payload type)&nbsp;in =
the=20
media description.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV>You've misrepresented the PacketCable 'mptime' SDP=20
attribute,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007>&nbsp;&nbsp;&nbsp;Another<BR>&nbsp;&nbsp; one =
is the=20
'mptime' attribute, defined in the PacketCable Network-<BR>&nbsp;&nbsp; =
Based=20
Call Signaling Protocol Specification =
[PKT.PKT-SP-EC-MGCP],<BR>&nbsp;&nbsp;=20
which indicates "a list of packetization period values the=20
endpoint<BR>&nbsp;&nbsp; is capable of using (sending and receiving) for =
this=20
connection".<BR>&nbsp;&nbsp; While all have similar semantics, there is=20
obviously no<BR>&nbsp;&nbsp; interoperability between them, creating a =
nightmare=20
for the<BR>&nbsp;&nbsp; implementor who happens to be defining a common =
SDP=20
stack for<BR>&nbsp;&nbsp; different =
applications.<BR></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D510054901-31052007>defined in the=20
PacketCable Network-Based Call Signaling Protocol=20
Specification,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D510054901-31052007>&nbsp;&nbsp;&nbsp;=20
<A=20
href=3D"http://www.packetcable.com/downloads/specs/PKT-SP-NCS1.5-I03-0407=
12.pdf">http://www.packetcable.com/downloads/specs/PKT-SP-NCS1.5-I03-0407=
12.pdf</A></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT><SPAN class=3D510054901-31052007><FONT face=3DArial =
size=3D2>and the=20
</FONT><FONT face=3DArial size=3D2>PacketCable PSTN Gateway Call =
Signaling Protocol=20
Specification</FONT><FONT face=3DArial =
size=3D2>,</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D510054901-31052007>&nbsp;&nbsp;&nbsp;=20
<A=20
href=3D"http://www.packetcable.com/downloads/specs/PKT-SP-TGCP1.5-I03-040=
712.pdf">http://www.packetcable.com/downloads/specs/PKT-SP-TGCP1.5-I03-04=
0712.pdf</A></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D510054901-31052007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D510054901-31052007>The =
'mptime' SDP=20
attribute is more than "a list of packetization period values the =
endpoint is=20
capable of using (sending and receiving) for this connection". The =
complete=20
definition of the 'mptime' SDP attribute follows,</SPAN></FONT><FONT=20
face=3DArial><SPAN class=3D510054901-31052007><FONT face=3D"Times New =
Roman"></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft><FONT face=3DArial size=3D2>mptime:</FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>This attribute is a =
media-level=20
  attribute defined by PacketCable. The mptime attribute defines a list =
of=20
  packetization</FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>period values the =
endpoint is capable=20
  of using (sending and receiving) for this =
connection.</FONT></DIV></FONT><FONT=20
  face=3D"Times New Roman">
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV align=3Dleft></FONT><FONT face=3DArial size=3D2>Send: The =
mptime attribute=20
    MUST be present. There MUST be precisely one entry in the list=20
    for</FONT><FONT face=3D"Times New Roman"></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>each &lt;format&gt; =
entry provided=20
    in the "m=3D" line. Entry number j in this list defines =
the</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>packetization period =
for entry=20
    number j in the "m=3D" line. The first entry in the list MUST be=20
a</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>decimal number whereas =
subsequent=20
    entries in the list MUST be either a decimal number or =
a</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>hyphen. For those =
media formats=20
    where a single packetization rate does not apply (e.g.,=20
nonvoice</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>codecs such as =
telephone-event or=20
    comfort noise), a hyphen ("-") MUST be encoded at</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>the corresponding =
location in the=20
    list of packetization periods.</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></FONT><FONT=20
    face=3D"Times New Roman">
    <DIV align=3Dleft></FONT><FONT face=3DArial size=3D2>Receive: =
Conveys the list of=20
    packetization periods that the remote endpoint is capable of using =
for=20
    this</FONT><FONT face=3D"Times New Roman"></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>connection; one for =
each media=20
    format in the "m=3D" line. For media formats whose</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>packetization period =
is specified as=20
    a hyphen ("-"), the endpoint MUST use one of the</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>packetization periods =
that was=20
    actually specified in the list. If the "mptime" attribute =
is</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>absent, then the value =
of the=20
    "ptime" attribute, if present, MUST be taken as indicating =
the</FONT></DIV>
    <DIV align=3Dleft><FONT face=3DArial size=3D2>packetization period =
for all codecs=20
    present in the "m=3D" line.</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE>
<DIV dir=3Dltr style=3D"MARGIN-RIGHT: 0px" align=3Dleft><SPAN=20
class=3D510054901-31052007><FONT face=3DArial size=3D2>and note the =
PacketCable=20
semantics related to the 'ptime' SDP attribute,</FONT></SPAN><SPAN=20
class=3D510054901-31052007><FONT face=3D"Times New Roman" =
size=3D2></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr align=3Dleft><FONT =
face=3DArial>ptime:</FONT></DIV></FONT><FONT=20
  face=3D"Times New Roman" size=3D2>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV dir=3Dltr align=3Dleft><FONT =
face=3DArial>Send</FONT></FONT><FONT=20
    face=3D"Times New Roman" size=3D2><FONT face=3DArial>: The ptime =
SHOULD be sent if=20
    it was received in a Remote Connection Descriptor or if =
the</FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial>CMS used the =
packetization period=20
    ('p:') LocalConnectionOption.</FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT =
face=3DArial></FONT>&nbsp;</DIV></FONT><FONT=20
    face=3D"Times New Roman" size=3D2>
    <DIV dir=3Dltr align=3Dleft><FONT =
face=3DArial>Receive</FONT></FONT><FONT=20
    face=3D"Times New Roman" size=3D2><FONT face=3DArial>: The field =
MUST be ignored=20
    if the SDP contains the "mptime" attribute (as required =
in</FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial>PacketCable compliant =
devices). If=20
    the "mptime" attribute is not present, then this field =
is</FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial>used to define the =
packetization=20
    interval for all codecs present in the SDP description and =
the</FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial>MTA MUST use the =
ptime in the=20
    calculation of QoS=20
reservations.</FONT></FONT></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2>With the 'mptime' SDP attribute, there is one packetization =
period value=20
(possibly "-") for each media format (payload type)&nbsp;in the media=20
description.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2>There's no "interoperability nightmare" within the context in =
which the=20
'mptime' SDP attribute is defined. The&nbsp;above&nbsp;semantics state =
that the=20
'mptime' SDP attribute takes precedence over the 'ptime' SDP attribute, =
if=20
present. An implementation which does not recognize the 'mptime' SDP =
attribute=20
must ignore it. Note that similar precedence rules *could* be defined =
between=20
the 'maxptime' and 'maxmptime' SDP attributes. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2>Your Problem Statement should address the issue of backward=20
compatibility. Regardless of your final solution, the proposed syntax =
and=20
semantics must be backward compatible with existing implementations. =
PacketCable=20
addresses backward compatibility through the precedence rule, the =
fundamental=20
SDP principle of ignoring unrecognized attributes, "offers" which =
include both=20
old and new syntax and "answers" which are consistent (in terms of =
syntax) with=20
"offers".</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial size=3D2>I=20
think that you've understated the problem of existing packetization =
period=20
semantics being nothing more than a preference or recommendation (as it =
relates=20
to actually sending based on the "negotiated" packetization period). If =
we can=20
agree on per media format packetization period syntax and semantics, =
have we=20
really solved the problem if the "negotiated" packetization period is =
nothing=20
more than a recommendation? This problem (the lack of "strict" =
negotiation)=20
isn't unique to packetization period. I think that there's a general =
solution=20
that we can discuss at a later date.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial size=3D2>I=20
appreciate the fact that you're attempting to finally bring closure to =
this=20
long-standing issue.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2>Joe</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D510054901-31052007><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></FONT></SPAN></FONT></BODY></HTML>

------_=_NextPart_001_01C7A337.7FD5696E--


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

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

--===============1290680050==--




From mmusic-bounces@ietf.org Thu May 31 04:12:51 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Htfm2-0001oq-Gn; Thu, 31 May 2007 04:12:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Htfm0-0001oh-Gu
	for mmusic@ietf.org; Thu, 31 May 2007 04:12:44 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Htfly-0002DT-Vq
	for mmusic@ietf.org; Thu, 31 May 2007 04:12:44 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l4V8CV2N007057; Thu, 31 May 2007 11:12:38 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 11:12:34 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 11:12:34 +0300
Received: from [172.21.154.97] ([172.21.154.97]) by esebh101.NOE.Nokia.com
	over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 11:12:34 +0300
Message-ID: <465E8371.2060605@nsn.com>
Date: Thu, 31 May 2007 11:12:33 +0300
From: Miguel Garcia <Miguel.Garcia@nsn.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Joe Stone (joestone)" <joestone@cisco.com>
Subject: Re: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
References: <CDB8E728D94C3A48BAACD57F390C40220329DE2C@xmb-sjc-233.amer.cisco.com>
In-Reply-To: <CDB8E728D94C3A48BAACD57F390C40220329DE2C@xmb-sjc-233.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 May 2007 08:12:34.0073 (UTC)
	FILETIME=[71402890:01C7A35B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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>
Errors-To: mmusic-bounces@ietf.org

Hi Joe:

Thanks for your comments.

You probably have noticed that the quoted text in the draft has been 
copied from the corresponding specification, so if you think the quoted 
text is wrong, don't shoot the messenger :-)

More seriously now... I didn't want to have a discussion on the exact 
semantics on those attributes, I understand that I a summary of a few 
words may offer the wrong impression.

The idea with that text is to highlight that the same problem has been 
discussed in the past elsewhere with different type of solutions. If the 
text is offensive, I can remove the references in a future version of 
the draft.

Some more discussion below.

Joe Stone (joestone) wrote:
>  
> There's no "interoperability nightmare" within the context in which the 
> 'mptime' SDP attribute is defined. The above semantics state that the 
> 'mptime' SDP attribute takes precedence over the 'ptime' SDP attribute, 
> if present. An implementation which does not recognize the 'mptime' SDP 
> attribute must ignore it. Note that similar precedence rules *could* be 
> defined between the 'maxptime' and 'maxmptime' SDP attributes.

Right, this is correct. However, by "interoperability nightmare" I meant 
the possibility of two independent SDP implementations to interoperate, 
if one has been customized for, say, V.152, and the other had 
implemented a proprietary mechanism. They won't interoperate for the 
packetization time per media type. Or, in other words, they interoperate 
(for the packetization time per media type) as long as both SDP 
implementations are in the same context, I mean, both follow what V.152 say.


> Your Problem Statement should address the issue of backward 
> compatibility. Regardless of your final solution, the proposed syntax 
> and semantics must be backward compatible with existing implementations. 

Agreed, it is assumed that whatever solution the IETF develops should be 
backwards compatible. I don't mind mentioning it explicitly in a future 
version of draft.


> PacketCable addresses backward compatibility through the precedence 
> rule, the fundamental SDP principle of ignoring unrecognized attributes, 
> "offers" which include both old and new syntax and "answers" which are 
> consistent (in terms of syntax) with "offers".

Yes, I've noticed it.

>  
> I think that you've understated the problem of existing packetization 
> period semantics being nothing more than a preference or recommendation 
> (as it relates to actually sending based on the "negotiated" 
> packetization period). If we can agree on per media format packetization 
> period syntax and semantics, have we really solved the problem if the 
> "negotiated" packetization period is nothing more than a recommendation? 

This is a point for discussion. The text about ptime in RFC 4566 says: 
"It should not be necessary to know ptime to decode RTP or vat audio, 
and it is intended as a recommendation for the encoding/packetisation of 
audio. "

If you agree with the text, then there is nothing to negotiate. It is 
only that the SDP creator should have the means to express: "hey, I 
would understand any packetization time you send me for this media 
format, but if you happen to be able to use xx ms. packetization time, I 
will get better performance, so please, please, please, use that 
packetization time.". But at the end of the day, it is up to the RTP 
sender to decide the packetization time for that particular media type.


> This problem (the lack of "strict" negotiation) isn't unique to 
> packetization period. I think that there's a general solution that we 
> can discuss at a later date.

We should first agree on whether there is a need for a negotiation or it 
is just a plea for using a packetization time for a given media type.
>  
> I appreciate the fact that you're attempting to finally bring closure to 
> this long-standing issue.

Thanks.

/Miguel
>  
> Joe
>  

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland


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



From mmusic-bounces@ietf.org Thu May 31 09:37:37 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtkqN-00012h-Mv; Thu, 31 May 2007 09:37:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtkqM-00012J-5Y; Thu, 31 May 2007 09:37:34 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HtkqI-0005Ej-Gu; Thu, 31 May 2007 09:37:34 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 31 May 2007 06:37:30 -0700
X-IronPort-AV: i="4.14,598,1170662400"; 
	d="scan'208"; a="159417858:sNHT46795500"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l4VDbThc025078; 
	Thu, 31 May 2007 06:37:29 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4VDbTV1025672;
	Thu, 31 May 2007 13:37:29 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 06:37:29 -0700
Received: from [10.32.241.149] ([10.32.241.149]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 06:37:29 -0700
Message-ID: <465ECF97.9080208@cisco.com>
Date: Thu, 31 May 2007 09:37:27 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <043a01c79e85$64e8dd10$c6f0200a@amer.cisco.com>
	<0F2C075D-A4CF-4287-A228-CF2979624B30@magma.ca>
In-Reply-To: <0F2C075D-A4CF-4287-A228-CF2979624B30@magma.ca>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 May 2007 13:37:29.0122 (UTC)
	FILETIME=[D5349020:01C7A388]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3361; t=1180618649;
	x=1181482649; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20A=20question=20on=20draft-ietf-mmusic-ice-
	15 |Sender:=20;
	bh=JrENpEqluXNCn2izJrc1tVJOevfvrHLcOUoKcyRleU8=;
	b=hD9zR2LywnivPfVfxTscY2SsgmCEqMO8+VkHjkP2GxVHcN9XFCek1ienMv3eX9pJT57m8pju
	fVgJfDJ/8gkegtve/sVshp5IHeTyDbN2QkroD3sJAmZ38Co6zv82Blf2;
Authentication-Results: sj-dkim-5; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: behave@ietf.org, mmusic@ietf.org, Dan Wing <dwing@cisco.com>
Subject: [MMUSIC] Re: [BEHAVE] A question on draft-ietf-mmusic-ice-15
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

To be clear - there is no special behavior required from the endpoint 
connected to the TURN server for this to work. The ICE processing 
defined in the specification will cause an endpoint to naturally send 
connectivity checks which open up permissions. SetActiveDestination is 
not required and would not need to be used for this purpose.

Thanks,
Jonathan R.

Philip Matthews wrote:

> 
> On 25-May-07, at 00:30 , Dan Wing wrote:
> 
>>>> TURN's Set Active Destination accomplishes that.  See
>>>> http://tools.ietf.org/html/draft-ietf-behave-turn-03#section-6.3.2
>>>
>>>
>>> Thanks for your reply. Besides Set Active Destination, there
>>> are some other methods could do the same thing, such as Open,
>>> Send indications.
>>>
>>> Do we need to add more text to ICE draft and say that "before
>>> connectivity check begins, agent A should create permission
>>> for Relayed address in order to allow connectivity check's
>>> packet from other agent through the NAT and reach the agent.
>>> A"?
>>
>>
>> It's not necessary -- the combination of the triggered checks
>> and retries by the answerer cause the permission and the
>> connectivity check to complete as soon as the permission is
>> created.
> 
> 
> Just a bit more clarification here.
> 
> "Set Active Destination" is one way to install a filtering entry for the
> remote peer in the TURN server, but there is another way.
> 
> Consider two peers, L and R, which are behind different NATs.
> L uses a TURN server T.
> 
> If R sends a connectivity check to L's allocated address on T
> before anything else happens, then you are correct that T will
> discard the packet. However, this will install a filtering entry
> into R's local NAT.
> Then when L sends a connectivity check from T towards R,
> this will install a filtering entry on T for R, and this connectivity
> check packet will also get through R's NAT because of the
> previously installed filtering entry.
> 
> If the order is reversed (L sends first), then a connectivity check
> from L's allocated address on T towards R will be dropped by
> R's NAT, but will install a filtering entry on T.
> Then when R sends a connectivity check from R to L's address
> on T, this connectivity check will get through because of the
> previously installed filtering entry on T.
> 
> 
> To summarize:
> If R sends first, then its connectivity check packets get dropped
> by T until L sends its first packet towards R.
> If L sends first, then its connectivity check packets get dropped
> by R's NAT until R sends its first packet towards L's address on T.
> 
> In other words, the packets do not get through until both ends try
> to send. This is the reason that ICE defines a priority function for
> candidate pairs -- so both ends will send checks at approximately
> the same time.
> 
> - Philip
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www1.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   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 May 31 13:06:14 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hto66-0001h3-ND; Thu, 31 May 2007 13:06:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hto64-0001gx-IR
	for mmusic@ietf.org; Thu, 31 May 2007 13:06:00 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hto62-0001dh-2w
	for mmusic@ietf.org; Thu, 31 May 2007 13:06:00 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 31 May 2007 10:05:54 -0700
X-IronPort-AV: i="4.14,599,1170662400"; 
	d="scan'208"; a="159541933:sNHT2813078268"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4VH5smI007606; 
	Thu, 31 May 2007 10:05:54 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4VH5Zae028175;
	Thu, 31 May 2007 17:05:54 GMT
Received: from xmb-sjc-233.amer.cisco.com ([128.107.191.88]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 May 2007 10:05:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Date: Thu, 31 May 2007 10:05:48 -0700
Message-ID: <CDB8E728D94C3A48BAACD57F390C40220329DFB9@xmb-sjc-233.amer.cisco.com>
In-Reply-To: <465E8371.2060605@nsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Thread-Index: AcejW3ZHszTmaoqnQteIpUJR4g2MUgAJhfHQ
From: "Joe Stone \(joestone\)" <joestone@cisco.com>
To: "Miguel Garcia" <Miguel.Garcia@nsn.com>
X-OriginalArrivalTime: 31 May 2007 17:05:49.0884 (UTC)
	FILETIME=[F03D77C0:01C7A3A5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3973; t=1180631154;
	x=1181495154; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=joestone@cisco.com;
	z=From:=20=22Joe=20Stone=20\(joestone\)=22=20<joestone@cisco.com>
	|Subject:=20RE=3A=20[MMUSIC]=20New=20draft=3A=20multiple=20times=20proble
	m=20description=3Adraft-garcia-mmusic-multiple-ptimes-problem-00.txt
	|Sender:=20; bh=loQmhcnZGn/0yngOSkWDBC+x5Bh+G9fssAQU4o3JfWc=;
	b=KyGMo77D3kPb7skype9i5oYZJeNceFuB0eLhN5QYyZ0FCuxKPG4r6Q33nFqujLbHi8oERCtW
	6w6sM3FmiyZk9YXGpEiVOAYJRf4qqmFDcOz1NmjLpGojhFy09CgewthLhDUYWiiTxpqpO9VPSF
	MRmwyc6A6nJouZrGX69tPk3kU=;
Authentication-Results: sj-dkim-1; header.From=joestone@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
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>
Errors-To: mmusic-bounces@ietf.org

Hi Miguel,

[js] Comments in line...

More seriously now... I didn't want to have a discussion on the exact
semantics on those attributes, I understand that I a summary of a few
words may offer the wrong impression.

[js] Yes, I'm simply suggesting that we could more accurately paraphrase
rather than take a single sentence out of context.

The idea with that text is to highlight that the same problem has been
discussed in the past elsewhere with different type of solutions. If the
text is offensive, I can remove the references in a future version of
the draft.

[js] I certainly wouldn't remove the references. These references
contain viable solutions.

[js] I'd also like to point out the PacketCable Call Management Server
Signaling Specification,

=09
http://www.packetcable.com/downloads/specs/PKT-SP-CMSS1.5-I04-070412.pdf

[js] Section 8.4.10 of this specification deals with SIP-NCS/TGCP SDP
interworking. We could consider this in the (slightly) more general
context of SIP-xGCP SDP interworking where xGCP refers to MGCP and its
variants (including NCS, TGCP, ...). For example, section 8.4.10.1
deals with the fact that preferred SIP call hold SDP syntax
("a=3Dsendonly" SDP attribute, IP address "0.0.0.0", ...) is commonly
ignored or rejected by xGCP implementations. I wanted to highlight
section 8.4.10.2 which deals with ptime and mptime SDP interworking.
This section addresses the relationship between the packetization period
*value* of the "a=3Dptime" SDP attribute and the possible packetization
period *values* of the per media format "a=3Dmptime" SDP attribute
assuming the two co-exist as part of the same media description for
backward compatibility. This issue would need to be addressed with any
per media format packetization period approach.

> I think that you've understated the problem of existing packetization=20
> period semantics being nothing more than a preference or=20
> recommendation (as it relates to actually sending based on the
"negotiated"
> packetization period). If we can agree on per media format=20
> packetization period syntax and semantics, have we really solved the=20
> problem if the "negotiated" packetization period is nothing more than
a recommendation?

This is a point for discussion. The text about ptime in RFC 4566 says:=20
"It should not be necessary to know ptime to decode RTP or vat audio,
and it is intended as a recommendation for the encoding/packetisation of
audio. "

If you agree with the text, then there is nothing to negotiate. It is
only that the SDP creator should have the means to express: "hey, I
would understand any packetization time you send me for this media
format, but if you happen to be able to use xx ms. packetization time, I
will get better performance, so please, please, please, use that
packetization time.". But at the end of the day, it is up to the RTP
sender to decide the packetization time for that particular media type.

[js] There's the world of I-Ds and RFCs and then there's reality. Dan
Wing's E-mail points out the reality that some implementations can't
change between codecs on-the-fly. There's a similar reality in that some
implementations can only send and receive using a finite set of
packetization periods (in some cases a single packetization period). I'm
sure that we've all seen cases of one-way audio (or no audio) in which
the two parties failed to agree on a common, bi-directional
packetization period. RFC 3551 suggests, "A receiver SHOULD accept
packets representing between 0 and 200 ms of audio data". The reality is
that not all implementations can accept packets over that entire range.
We can dismiss these implementations as non-compliant or we can
recognize these as real problems in need of a solution. In addition,
intermediary devices which shape or police may depend on a negotiated
packetization period which is more than simply a recommendation.=20



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



From mmusic-bounces@ietf.org Thu May 31 23:11:52 2007
Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HtxYB-0002Ye-Dv; Thu, 31 May 2007 23:11:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HtxYA-0002VV-BA
	for mmusic@ietf.org; Thu, 31 May 2007 23:11:38 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtxY8-0000Ji-Kd
	for mmusic@ietf.org; Thu, 31 May 2007 23:11:38 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5E87F20072; Fri,  1 Jun 2007 05:11:35 +0200 (CEST)
X-AuditID: c1b4fb3e-ae1ebbb0000061ca-07-465f8e676dfd 
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4F74C20018; Fri,  1 Jun 2007 05:11:35 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Jun 2007 05:11:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
Date: Fri, 1 Jun 2007 05:11:33 +0200
Message-ID: <7374777208BDC7449D5620EF9423256704991181@esealmw113.eemea.ericsson.se>
In-Reply-To: <465C0342.3010602@nsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] New draft: multiple times problem
	description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
thread-index: Aceh3f2gopH2+H6KRHm93ENSvgJv2gCG+SKQ
References: <465C0342.3010602@nsn.com>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "Miguel Garcia" <Miguel.Garcia@nsn.com>,
	"mmusic" <mmusic@ietf.org>
X-OriginalArrivalTime: 01 Jun 2007 03:11:35.0094 (UTC)
	FILETIME=[8FAC6560:01C7A3FA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: "Willekens, Marc" <marc.willekens@nsn.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org


Hi,

RFC3108 defines a "vsel" attribute (and also a "onewaySel" attribute),
which allows you to to specify Packet Length and Packet Time per code.=20

Now, I know RFC3108 was written for ATM, but I don't think there is
anything ATM specific with these attributes (and, if there is, at least
we should look whether we can use the attributes as base for our work).

Regards,

Christer

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.Garcia@nsn.com]=20
> Sent: 29. toukokuuta 2007 13:41
> To: mmusic
> Cc: Willekens, Marc
> Subject: [MMUSIC] New draft: multiple times problem=20
> description:draft-garcia-mmusic-multiple-ptimes-problem-00.txt
>=20
> Hi:
>=20
> We have just submitted a new short draft that describes the=20
> problem with the lack of multiple packetization times in SDP.
>=20
> The draft should be soon available in the traditional repositories.=20
> Until that time, you can fetch a copy from:
>=20
> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
> tiple-ptimes-problem-00.txt
> http://people.nokia.net/~miguel/drafts/draft-garcia-mmusic-mul
> tiple-ptimes-problem-00.html
>=20
> We are aware that the issue has been discussed in the past,=20
> without a clear conclusion on whether a problem exists. We=20
> believe there is an interoperability problem, and thus, we=20
> are soliciting comments about it.=20
> At this stage, we are not discussing solutions yet, we rather=20
> agree first that there is a problem that needs to be solved.
>=20
> /Miguel
> --=20
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Siemens Networks     Espoo, Finland
>=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



