From daemon@optimus.ietf.org  Thu Aug  1 03:00:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09145
	for <mmusic-archive@odin.ietf.org>; Thu, 1 Aug 2002 03:00:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA16508
	for mmusic-archive@odin.ietf.org; Thu, 1 Aug 2002 03:02:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15892;
	Thu, 1 Aug 2002 02:56:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15863
	for <mmusic@optimus.ietf.org>; Thu, 1 Aug 2002 02:56:46 -0400 (EDT)
Received: from prix.tandberg.no (prix.tandberg.no [193.212.161.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09064
	for <mmusic@ietf.org>; Thu, 1 Aug 2002 02:55:38 -0400 (EDT)
Received: from there ([10.0.2.14])
	by prix.tandberg.no (8.11.6/8.11.6) with SMTP id g716uBu09104;
	Thu, 1 Aug 2002 08:56:11 +0200
Message-Id: <200208010656.g716uBu09104@prix.tandberg.no>
Content-Type: text/plain;
  charset="iso-8859-15"
From: Nils Henrik Lorentzen <nhl@tandberg.no>
Organization: TANDBERG ASA
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [MMUSIC] Signaling FIR/Freeze in SIP
Date: Thu, 1 Aug 2002 08:52:51 +0200
X-Mailer: KMail [version 1.3.1]
References: <B2518D608282D511BEA400508BBB9148EAA1E0@ACCORD-NTSRV3>
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1E0@ACCORD-NTSRV3>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Cc: mmusic@ietf.org
X-Scanned-By: MIMEDefang 2.14 (www dot roaringpenguin dot com slash mimedefang)
Content-Transfer-Encoding: 8bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 8bit

On Wednesday 31 July 2002 12:38, you wrote:

> 1. Sending a freeze a couple of times may cause a problem. The freeze
> requests are sent from the MCU and not from the encoding endpoints while
> the full picture is coming from the endpoint. So what happens if a freeze
> arrives after the intra frame with the freeze release code. The decoder
> will freeze, he has no way to know if the freeze was for a switch in the
> past or for a switch in future.

As mentioned in anther post,  this problem could probably be solved
by sending the RTP's timestamp/sequence number at the time of sending
the first freeze. Possible this introduces more problems though.

> 2. The customers of the video conferencing MCUs do not like to have an ugly
> video during the video switch, so we need a solution which will be more
> reliable.

If we can do retransmits of freeze, then in my opinion loss of all freeze
packets would be rare enough to justify best-effort sending.

> So how do you see inter-op between H.323 and SIP or is this not an issue

It sure is an issue.  Making old H.323 endpoints support new RTCP packets
would take time or more likely never happen, so the only possibility would
be to also handle RTCP/RTP in a H.323/SIP GW. I agree this speaks
strongly against an RTCP based solution.

> > If an endpoint sends the exact same SDP to another endpoint
> > several times in
> > sequence, only the first SDP arriving at remote should trigger any
> > change/sideeffects.
>
> OK, so let us call the two messages freeze and freeze release. Sending
> freeze a couple of times will keep the receive in a freeze state. Sending
> freeze release will keep the receiver in a freeze release state. The two
> requests cause a change of state.

OK, I have reread you posts even more thoroughly, but I'm still
not sure I understand your proposal fully. You want to put decoder in freeze 
state using SDP. The freeze will be released, not by a new SDP, but by a full 
intra or a timeout at the decoder.

Although it seems a bit odd to me to change the state back using non-SDP
means, I  cannot see any problem with this. Both encoder and conf controller
should eventually end up having the correct view of the others' state even if 
timeout occurs or full intra is lost. Nitpick: I would name the attribute
"paused" or similar, to reflect the local view of the state at the conf
controller. SDPs are not for sending requests, but rather snapshots of the
local state.

You also have to send a FIR to the encoder. AFAI understand you
want to do this using a "new-stream" attribute. This will cause
a full-intra to be sent.

This does not pass the test mentioned above, as sending several
such SDPs would trigger the sideeffect of sending a full intra
each time. 
I think classifying "new-stream" as a state-change is
a bit far-fetched, but not  wrong; You would then have a
possibly infinite number of states," receiving-stream-1",
"receiving-stream-2"  etc. You somewhere compared this to
asking for a new orientation. A  difference here is that in the latter case
you have a finite number of  well-defined states, "portrait" and
"landscape". Using an a=receiving-stream-x attribute would
pass the test, as it would only cause a full intra when "x "
was increased.
In fact I think you could signal almost any kind of
request as a local state change, for example you could signal
DTMFs as a=cur-dtmf # 4, where "#" is digit and 4 is a
sequence-number. While possible,  I don't think SDP was meant
for signaling in such a manner.

You still would have to send FIRs when synchronization issues occur.
You could argue this is a statechange between receiving
deltas and receiving full intras (ie. a=recving-delta, a=recving-intra, 
a=recving-gob). This could also replace the above "new-stream" 
attribute.
Is this a somewhat correct understanding of your proposal ?

There has not been any discussion yet of the third
alternative, using a new protocol in INFO (or similar). AFAI have
understood, everyone has acknowledged the need for such a protocol
(to signal many of the commands sent in H.245, like confernce control), and
one should probably define  one to accompany SDPng.
However, we could define a simple more short-term one to accompany SDP.
This protocol would fade away alongside SDP as we move to
SDPng and the new command protocol.

Something like:

"version" ":" version        ; protocol version
command [  media-line-number ] [ " :" parameters  ]

Example:
version : 0
fir 0         ; full intra for stream corresponding to 1st SDP m-line
freeze 1  ; send freeze for stream corresponding 2nd SDP m-line

Is something like this a possible solution or is it completely out of the 
question ? Has it  already been discussed and rejected ? It would not
have the SIP/H323 GW issue and would not require changes in existing
implementations.
 
Nils Henrik Lorentzen


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



From daemon@optimus.ietf.org  Thu Aug  1 09:29:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00256
	for <mmusic-archive@odin.ietf.org>; Thu, 1 Aug 2002 09:29:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA26347
	for mmusic-archive@odin.ietf.org; Thu, 1 Aug 2002 09:30:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA25935;
	Thu, 1 Aug 2002 09:23:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA25905
	for <mmusic@optimus.ietf.org>; Thu, 1 Aug 2002 09:23:26 -0400 (EDT)
Received: from radvpost.us.radvision.com ([12.44.63.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29845
	for <mmusic@ietf.org>; Thu, 1 Aug 2002 09:22:13 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2653.19)
	id <PC5BMWWS>; Thu, 1 Aug 2002 09:22:26 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD949450188561C@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] Signaling FIR/Freeze in SIP
Date: Thu, 1 Aug 2002 09:22:20 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Nils and all the rest!
I am replying to the whole thread being exchanged today so far.
I agree with the bottom line conclusion (although my reasoning may be
slightly different).

Since, there is no agreement to standardize the required primitives within
the old SDP and taking into account all the drawbacks of such a solution,
there is no point pursuing this direction.

Instead, we need two things:
1. Working on a new point-to-point media control protocol
2. Agree on a doable way (such as INFO) to convey the required primitives in
the call signaling path. It doesn't have to be a standard. 

For all the practical reasons, multimedia vendors will need to support both.

We (as RADVISION together with its partners) already have a simple
extensible XML scheme to be conveyed in the INFO messages for exactly this
purpose. I plan to publish it as an IETF draft shortly.

BR,
Orit Levin
Chief Architect
RADVISION Inc.
Tel:  +1.201.689.6330

 -----Original Message-----
From: 	Nils Henrik Lorentzen [mailto:nhl@tandberg.no] 
Sent:	Wednesday, July 31, 2002 6:04 AM
To:	mmusic@ietf.org
Subject:	[MMUSIC] Signaling FIR/Freeze in SIP

Hi,

We at TANDBERG would like to voice our opinion on the full intra/freeze 
request issue, as the decision made may affect us in the future.

There are as far as we can see three proposed solutions to the problem of 
signaling these requests within the SIP framework:

1. Use RTCP
2. Use SDP
3. Some kind of new protocol tunneled in INFO or a similar SIP method.

Our opinion so far:

1. This is in our opinion the best solution from a design perspective. We
see 
it this way: Keeping a good quality video stream and output is an issue 
between the encoder and decoder, thus information for that purpose should be

sent directly between them. Ideally it should not be sent along the
signaling 
path, but along the media path.

There seems to be two main arguments against the RTCP solution:

- RTCP is not reliable.
We agree with Colin, in that this is a non-issue. The FIR message could be 
retransmitted until a full intra is received. As for freeze requests, these 
could be retransmitted a predefined number of times with a predefined 
interval. If any of them arrive at the decoder all is fine. In the rare case

where none do, the user will see some ugly video output for a relatively 
small amount of time, until it receives a full intra, but it will not 
otherwise affect the call.
There may be issues here we have not thought of, though.

- H.323 EPs do not support these new RTCP packets. We think this is more of 
an issue. As Roni pointed out, a SIP/H.323 signaling GW would not be able to

gather the FIR requests from the SIP side and pass it on to the H.323 side, 
unless it is also acts as GW for the RTP/RTCP traffic. The latter is of 
course not ideal, but could do as a temporary solution. One would probably 
need to add a new option flag to H.323 call setup messages telling whether 
the endpoint supports FIR/freeze in RTCP.

2. Using a media attribute in SDP for signaling a FIR is wrong in our 
opinion. SDPs are for telling what kind of streams you want from the time
you 
send it until the next time you send an SDP.  A full intra is a request that

is executed only once when received.

We believe the following can be used as a "litmus test" for determining what

information is OK to send in SDP and what is not:

If an endpoint sends the exact same SDP to another endpoint several times in

sequence, only the first SDP arriving at remote should trigger any 
change/sideeffects.

This holds true in for example hold/resume but not for full intra req.

3. This is in our opinion not the ideal solution from a design POV, but it 
will interoperate better with existing H.323 EPs when SIP/H323 GWs are 
implemented. It would require a new protocol to be defined., but could be a 
very simple and limited protocol though, as it would just be a temporary 
solution.
We would possibly need a new such protocol when SDPng arrives, since we have

to refer to a SDPng media channel in a different manner than refering to an 
SDP channel.

To conclude, we support solutions 1 and 3, while 2 is definitely the worst 
alternative. While using RTCP (or similar protocol directly between 
encoder/decoder) is in our opinion the cleanest solution, 3 might be used if

the SIP/H.323 switching problem is deemed important enough and no other 
problems with using RTCP are found.

Nils Henrik Lorentzen

Software Developer
TANDBERG
http://www.tandberg.net


_______________________________________________
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 daemon@optimus.ietf.org  Thu Aug  1 17:13:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15026
	for <mmusic-archive@odin.ietf.org>; Thu, 1 Aug 2002 17:13:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA22952
	for mmusic-archive@odin.ietf.org; Thu, 1 Aug 2002 17:14:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22733;
	Thu, 1 Aug 2002 17:08:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19703
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 16:11:20 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06902
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 16:10:15 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate2.mot.com (motgate2 2.1) with ESMTP id NAA22118; Fri, 26 Jul 2002 13:11:22 -0700 (MST)]
Received: [from artibeus.nsr.labs.mot.com (artibeus.nsr.labs.mot.com [173.23.95.73]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id NAA14250; Fri, 26 Jul 2002 13:09:49 -0700 (MST)]
Received: from motorola.com (localhost [127.0.0.1])
	by artibeus.nsr.labs.mot.com (8.11.6/8.11.6) with ESMTP id g6QKFhi04100;
	Fri, 26 Jul 2002 15:15:43 -0500
Message-ID: <3D41ADEF.5332BAF4@motorola.com>
Date: Fri, 26 Jul 2002 15:15:43 -0500
From: Bryan Thale <bryan.thale@motorola.com>
Organization: Networks & Infrastructure Research, Motorola Labs
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Colin Perkins <csp@isi.edu>
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] Re: Tool starting mode attributes in SDP
References: <200207261906.g6QJ6mh4008182@purple.nge.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Right.  To do it properly you need something like

"a=toolmode:" ("recvonly" / "sendonly" / "sendrecv") [ 1*SP "inactive" ] CRLF

to group the values of the toolmode attribute together but such a change is not
backward compatible with current implementations.  You could get most of the
benefits of such a change with a combination of a change to the ABNF and a
change to the text describing the recvonly, sendonly, sendrecv, and inactive
attributes.


  1. Change the ABNF to allow only one of recvonly, sendonly, and sendrecv to
     appear in a session or media description and to allow inactive to appear
     only in combination with one of those three.
  2. Change the text to state that the appearance of any of the three at the
     media level overrides any setting at the session level.

Bryan.

--
Bryan Thale
Networks & Infrastructure Research, Motorola Labs
mailto:bryan.thale@motorola.com

Colin Perkins wrote:

> Right, the problem is the override between session and media level. I don't
> think we can express that in the ABNF.
>
> Colin
>



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



From daemon@optimus.ietf.org  Fri Aug  2 15:52:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03777
	for <mmusic-archive@odin.ietf.org>; Fri, 2 Aug 2002 15:52:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04603
	for mmusic-archive@odin.ietf.org; Fri, 2 Aug 2002 15:53:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04507;
	Fri, 2 Aug 2002 15:48:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04479
	for <mmusic@optimus.ietf.org>; Fri, 2 Aug 2002 15:48:39 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03614
	for <mmusic@ietf.org>; Fri, 2 Aug 2002 15:47:27 -0400 (EDT)
Received: from mira-sjc5-1.cisco.com (IDENT:mirapoint@mira-sjc5-1.cisco.com [171.71.163.15])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g72Jm8AK001406
	for <mmusic@ietf.org>; Fri, 2 Aug 2002 12:48:08 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-142-64.cisco.com [128.107.142.64])
	by mira-sjc5-1.cisco.com (Mirapoint)
	with ESMTP id AEY46746;
	Fri, 2 Aug 2002 12:44:16 -0700 (PDT)
Message-ID: <3D4AE1F7.95E8761@cisco.com>
Date: Fri, 02 Aug 2002 12:48:07 -0700
From: Mahesh Shankar <mshankar@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] RTSP SETUP and ANNOUNCE requests
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

I was looking at the RTSP rfc, and I have a couple of questions:

1. Can an RTSP client request a PLAY session to be unicast to a host
other than itself ?
2. If so, would sending a SETUP message followed by an ANNOUNCE message
with the SDP information for the media-receiving-host be the way to do
it ?

I would appreciate it if someone could shed some light on this.

TIA.

-M


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



From daemon@optimus.ietf.org  Mon Aug  5 04:25:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04947
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 04:25:36 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA17475
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 04:26:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17249;
	Mon, 5 Aug 2002 04:20:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17220
	for <mmusic@optimus.ietf.org>; Mon, 5 Aug 2002 04:20:39 -0400 (EDT)
Received: from parsmtp2.rd.francetelecom.com (parsmtp2.rd.francetelecom.com [194.167.105.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04814
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 04:19:26 -0400 (EDT)
Received: from parmhs3.rd.francetelecom.fr ([10.193.117.62]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 10:20:32 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: [MMUSIC] video media control draft 
Date: Mon, 5 Aug 2002 10:20:31 +0200
Message-ID: <A2200E9A0E413B4C99FB7384D740878124DFC7@parmhs3.rd.francetelecom.fr>
Thread-Topic: [MMUSIC] video media control draft 
Thread-Index: AcI0zEHfY3BXHpbFSbaN2q545noJDQHiyLBQ
From: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
To: "Colin Perkins" <csp@isi.edu>
Cc: <mmusic@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 08:20:32.0925 (UTC) FILETIME=[F7A32CD0:01C23C58]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA17221
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 8bit

Hello,

Th draft I mentioned in a previous mail
"draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
codec. How do you propose the manage them during a call.

All thoses things are in the stream itself, but, a Video UA need a way
to express them during the initiation of the call and to control them
during the call.

Thanks,

Patrick,


-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: vendredi 26 juillet 2002 19:46
To: MONFORT Patrick FTRD/DMI/ISS
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 


I'm not sure we agree on the list of other things are needed. Some form
of
fast intro request, certainly, but what else? Freeze has been discussed,
but that may not be necessary. Are there others?

Colin



--> "MONFORT Patrick FTRD/DMI/ISS" writes:
>Yes, that would help.
>
>As other things are needed, would it be possible to have/imagine an
>attribute in the SDP (associated to media or the session) that can
>manage all the "control" aspect of media. UA could listen on this
>"control" port to receive command from other(s) party(ies).
>
>Or else, if we don't want to manage a new port, I think we will have a
>new SIP message that will carry a new SDP with constraints on it (like
>to update only attribute of the declared media) ?
>
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: mercredi 24 juillet 2002 22:38
>To: MONFORT Patrick FTRD/DMI/ISS
>Cc: Joerg Ott; Orit Levin; mmusic@ietf.org
>Subject: Re: [MMUSIC] video media control draft 
>
>
>--> "MONFORT Patrick FTRD/DMI/ISS" writes:
>...deleted...
>>Regarding the control, RFC 2032 (which describes RTCP packet for
>>IntraRequest) can't be deployed. The reason is that these RTCP packets
>>are not sent to the 'standard' RTCP Port.
>>
>>Here are the text taken from RFC 2032, that explains this issue
>(section
>>5.1):
>>
>>"
>>The H.261-specific control packets differ from normal RTCP packets in
>>   that they are not transmitted to the normal RTCP destination
>>   transport address for the RTP session (which is often a multicast
>>   address).  Instead, these control packets are sent directly via
>>   unicast from the decoder to the coder.  The destination port for
>>   these control packets is the same port that the coder uses as a
>>   source port for transmitting RTP (data) packets.  Therefore, these
>>   packets may be considered "reverse" control packets.
>>
>>   As a consequence, these control packets may only be used when no
RTP
>>   mixers or translators intervene in the path from the coder to the
>>   decoder.  If such intermediate systems do intervene, the address of
>>   the coder would no longer be present as the network-level source
>>   address in packets received by the decoder, and in fact, it might
>not
>>   be possible for the decoder to send packets directly to the coder.
>>"
>
>The proposal is to use the same FIR packet format as in RFC 2032, but
to
>send the request to the standard RTCP port, using the mechanisms from
>draft-ietf-avt-rtcp-feedback-03.txt to ensure timely feedback. Would 
>that help?
>
>Colin

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



From daemon@optimus.ietf.org  Mon Aug  5 07:17:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07857
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 07:17:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA26033
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 07:18:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25992;
	Mon, 5 Aug 2002 07:16:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA14836
	for <mmusic@optimus.ietf.org>; Fri, 2 Aug 2002 19:24:40 -0400 (EDT)
Received: from harp.interval.com ([64.94.69.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11104;
	Fri, 2 Aug 2002 19:23:20 -0400 (EDT)
Received: by harp.interval.com with Internet Mail Service (5.5.2653.19)
	id <Q1R97KZQ>; Fri, 2 Aug 2002 16:20:35 -0700
Message-ID: <50750ECDD09ED411AF9A00508B6A823B7E4391@harp.interval.com>
From: Kathy Kwan <kathyk@interval.com>
To: "'sip@ietf.org'" <sip@ietf.org>, "'mmusic@ietf.org'" <mmusic@ietf.org>
Cc: Kathy Kwan <kathyk@interval.com>
Date: Fri, 2 Aug 2002 16:20:34 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C23A7B.33DD1330"
Subject: [MMUSIC] Port changeability in response to Invite -- expected behavior?
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

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

------_=_NextPart_001_01C23A7B.33DD1330
Content-Type: text/plain

To the SIP/MMUSIC community,
 
I was looking at the method proposed by Rosenberg and Schulzrinne in the
IETF Internet Draft entitled "Models for Multiparty Conferencing in SIP"
(dated July 2002, expires Jan 2003), Section 7, entitled "Centralized
Signaling, Distributed Media".    This method describes the conferencing
case where a server controls the SIP connections with all participants, and
uses third party call control to enable media connections to go directly
between the participants.   Hence, the signaling is centralized, but media
is distributed.  In order for the method to work, an inherent assumption is
made that the original ports do not change in the response to an Invite.
Two examples of this assumption are shown in the call flow diagram of
"Centralized Signaling, Distributed Media" Figure 7:
 
(1)      If a participant is taken off hold, the participant cannot change
its ports in its response.
 
In Figure 7, participant  D is taken off hold in the very last Invite
transaction between D and the server.   It is assumed that D does not change
its ports D1,D2, and D3 in its Invite 200 OK response.   
 
(Perhaps there is a way to interleave invites using provisional responses
that could fix this particular case, but if that exists, the response could
be delayed by as long as it takes to receive the responses from all other
participants in the conference.)
 
(2)      If a participant receives a re-Invite for any reason, the
participant must maintain its original offered ports in the response.
 
In Figure 7, parties A, B and C are assumed to not change their original
ports when they receive a re-Invite from the server asking for an additional
port for D.   According to Figure 7, A, B, and C are not put on hold when D
arrives, so this case is distinct from (1) above.     
 
My questions are:
 
(3)      What assumptions can be made about the ports being able to change
in the response to an Invite?    Is there documentation of this in any RFCs?

 
Perhaps a media attribute could be used to request that the ports don't
change if it is not already implied in either of the cases above?
 
(4)      There are two ways to convey hold described below.   Is the
expectation for port behavior the same for both cases of hold?
 
The original way to convey hold is to set the IP address to 0.0.0.0.  This
case does not require RTCP to be sent during the hold period.   A new method
to convey hold is to use the media attributes "a=inactive", "a=sendonly" or
"a=recvonly", depending on the direction of the hold.  Because of the
different implications for the hold methods, particularly for RTCP, I am
asking this question with both methods in mind.
 
Thank you in advance for your comments.
 
Regards,
Kathy Kwan
Interval Media
 

------_=_NextPart_001_01C23A7B.33DD1330
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C23A41.01D58190">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1580947881;
	mso-list-type:hybrid;
	mso-list-template-ids:1182555644 1698734832 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"\(%1\)";
	mso-level-tab-stop:40.5pt;
	mso-level-number-position:left;
	margin-left:40.5pt;
	text-indent:-22.5pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>To the SIP/MMUSIC community,<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I was looking at the method proposed by Rosenberg and <span
class=3DSpellE>Schulzrinne</span> in the IETF Internet Draft entitled
"Models for Multiparty Conferencing in SIP" (dated July 2002,
expires Jan 2003), Section 7, entitled "Centralized Signaling,
Distributed Media".<span style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp;
</span>This method describes the conferencing case where a server =
controls the
SIP connections with all participants, and uses third party call =
control to
enable media connections to go directly between the participants.<span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>Hence, the signaling is
centralized, but media is distributed.<span =
style=3D'mso-spacerun:yes'>&nbsp;
</span>In order for the method to work, an inherent assumption is made =
that the
original ports do not change in the response to an Invite.<span
style=3D'mso-spacerun:yes'>&nbsp; </span>Two examples of this =
assumption are
shown in the call flow diagram of "Centralized Signaling, Distributed
Media" Figure 7:<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal =
style=3D'margin-left:40.5pt;text-indent:-22.5pt;mso-list:l0 level1 =
lfo1;
tab-stops:list 40.5pt'><![if !supportLists]><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><span style=3D'mso-list:Ignore'>(1)<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>If a participant is taken =
off
hold, the participant cannot change its ports in its =
response.<o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'margin-left:40.5pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>In Figure 7, =
<span
class=3DGramE>participant <span =
style=3D'mso-spacerun:yes'>&nbsp;</span>D</span> is
taken off hold in the very last Invite transaction between D and the
server.<span style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span><i =
style=3D'mso-bidi-font-style:
normal'><span style=3D'font-style:italic;mso-bidi-font-style:normal'>It =
is
assumed that D does not change its ports D1<span =
class=3DGramE>,D2</span>, and D3
in its Invite 200 OK response.</span></i><span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; =
</span><o:p></o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'margin-left:40.5pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>(Perhaps =
there is a way
to interleave invites using provisional responses that could fix this
particular case, but if that exists, the response could be delayed by =
as long
as it takes to receive the responses from all other participants in the
conference.)<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal =
style=3D'margin-left:40.5pt;text-indent:-22.5pt;mso-list:l0 level1 =
lfo1;
tab-stops:list 40.5pt'><![if !supportLists]><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><span style=3D'mso-list:Ignore'>(2)<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>If a participant receives =
a
re-Invite for any reason, the participant must maintain its original =
offered
ports in the response.<o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'margin-left:40.5pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>In Figure 7, =
parties A, B
and C are assumed to not change their original ports when they receive =
a
re-Invite from the server asking for an additional port for D.<span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>According to Figure 7, =
A, B, and C
are not put on hold when D arrives, so this case is distinct from (1) =
above.<span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp;&nbsp; =
</span><o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>My questions are:<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal =
style=3D'margin-left:40.5pt;text-indent:-22.5pt;mso-list:l0 level1 =
lfo1;
tab-stops:list 40.5pt'><![if !supportLists]><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><span style=3D'mso-list:Ignore'>(3)<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>What assumptions can be =
made about
the ports being able to change in the response to an Invite? <span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp;</span>Is there =
documentation of
this in any <span class=3DSpellE>RFCs</span>?<span
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp; </span><o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'margin-left:40.5pt'><i =
style=3D'mso-bidi-font-style:
normal'><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
font-style:italic;mso-bidi-font-style:normal'>Perhaps a media attribute =
could
be used to request that the ports don't change if it is not already =
implied
in either of the cases above?</span></font></i><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-left:.25in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:40.5pt;text-indent:-22.5pt;mso-list:l0 level1 =
lfo1;
tab-stops:list 40.5pt'><![if !supportLists]><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><span style=3D'mso-list:Ignore'>(4)<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>There are two ways to =
convey hold
described below.<span style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>Is =
the
expectation for port behavior the same for both cases of =
hold?<o:p></o:p></p>

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

<p class=3DMsoNormal style=3D'margin-left:40.5pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>The original =
way to
convey hold is to set the IP address to 0.0.0.0.<span
style=3D'mso-spacerun:yes'>&nbsp; </span>This case does not require =
RTCP to be
sent during the hold period.<span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>A
new method to convey hold is to use the media attributes
"a=3Dinactive", "a=3D<span class=3DSpellE>sendonly</span>" or
"a=3D<span class=3DSpellE>recvonly</span>", depending on the direction
of the hold.<span style=3D'mso-spacerun:yes'>&nbsp; </span>Because of =
the
different implications for the hold methods, particularly for RTCP, I =
am asking
this question with both methods in mind.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thank you in advance for your =
comments.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:PersonName><font size=3D3 face=3D"Times New =
Roman"><span
 style=3D'font-size:12.0pt'>Kathy =
Kwan</span></font></st1:PersonName><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Interval Media<o:p></o:p></span></font></p>

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

</div>

</body>

</html>

------_=_NextPart_001_01C23A7B.33DD1330--


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



From daemon@optimus.ietf.org  Mon Aug  5 12:29:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20504
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 12:29:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA13803
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 12:30:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13520;
	Mon, 5 Aug 2002 12:25:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10028
	for <mmusic@optimus.ietf.org>; Mon, 5 Aug 2002 11:44:51 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18222
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 11:43:40 -0400 (EDT)
Received: from dynamo.cs.columbia.edu (dynamo.cs.columbia.edu [128.59.16.4])
	by cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g75Fihx3014677
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 11:44:43 -0400 (EDT)
Received: from dynamo.cs.columbia.edu (localhost [127.0.0.1])
	by dynamo.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g75Fih9F025727
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 11:44:43 -0400 (EDT)
Received: (from petkos@localhost)
	by dynamo.cs.columbia.edu (8.12.1/8.12.1/Submit) id g75FihGO025725
	for mmusic@ietf.org; Mon, 5 Aug 2002 11:44:43 -0400 (EDT)
From: "Petri K. Koskelainen" <petkos@cs.columbia.edu>
Message-Id: <200208051544.g75FihGO025725@dynamo.cs.columbia.edu>
To: mmusic@ietf.org
Date: Mon, 5 Aug 2002 11:44:42 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] video media control draft
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

That draft works only for H.263 codec so it is not
a general solution. Moreover, using SDP a line 
to express options (or group of options and 
complex restrictions) is very difficult.

In the setup phase, you could advertize your
codec capabilities (in SDP), so it
is possible to change options during a call
without further signaling. But I guess
it makes sense to inform also signaling level
about the change (since e.g. bandwidth requirement 
may change considerably if you change options).


Petri

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

Hello,

Th draft I mentioned in a previous mail
"draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
codec. How do you propose the manage them during a call.

All thoses things are in the stream itself, but, a Video UA need a way
to express them during the initiation of the call and to control them
during the call.

Thanks,

Patrick,


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



From daemon@optimus.ietf.org  Mon Aug  5 14:13:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25409
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:13:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19983
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 14:14:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19550;
	Mon, 5 Aug 2002 14:08:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19522
	for <mmusic@optimus.ietf.org>; Mon, 5 Aug 2002 14:08:04 -0400 (EDT)
Received: from parsmtp2.rd.francetelecom.com (parsmtp2.rd.francetelecom.com [194.167.105.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25170
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 14:06:51 -0400 (EDT)
Received: from parmhs3.rd.francetelecom.fr ([10.193.117.62]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 20:08:03 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: [MMUSIC] video media control draft
Date: Mon, 5 Aug 2002 20:08:03 +0200
Message-ID: <A2200E9A0E413B4C99FB7384D740878124DFC8@parmhs3.rd.francetelecom.fr>
Thread-Topic: [MMUSIC] video media control draft
Thread-Index: AcI8nNqU/72P1VzXR+ac4My4Qyc7MwABbXqw
From: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:08:03.0446 (UTC) FILETIME=[0A95D160:01C23CAB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA19523
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 8bit

Hello,

The draft allows to express H263, H263+ options, but also the format of
the picture (whatever codec you use).

I agree with you saying that simple SDP line is not the best way, but
expressing video capabilities (options, format), without any SDP info
(which is actually the case or else I've missed something) is also very
difficult to do.

To me, the setup phase is one thing, but controlling the media once the
communication is important (someone may want to change the format of the
other's party encoder for example). And yes, if something changes
(option, but once again format), the bandwith may be impacted, and so,
as you mentioned, it makes sense to have signaling to do that.

Patrick,


-----Original Message-----
From: Petri K. Koskelainen [mailto:petkos@cs.columbia.edu]
Sent: lundi 5 aout 2002 17:45
To: mmusic@ietf.org
Subject: [MMUSIC] video media control draft



Hi,

That draft works only for H.263 codec so it is not
a general solution. Moreover, using SDP a line 
to express options (or group of options and 
complex restrictions) is very difficult.

In the setup phase, you could advertize your
codec capabilities (in SDP), so it
is possible to change options during a call
without further signaling. But I guess
it makes sense to inform also signaling level
about the change (since e.g. bandwidth requirement 
may change considerably if you change options).


Petri

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

Hello,

Th draft I mentioned in a previous mail
"draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
codec. How do you propose the manage them during a call.

All thoses things are in the stream itself, but, a Video UA need a way
to express them during the initiation of the call and to control them
during the call.

Thanks,

Patrick,


_______________________________________________
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 daemon@optimus.ietf.org  Mon Aug  5 16:12:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00244
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 16:12:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA27233
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 16:14:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27064;
	Mon, 5 Aug 2002 16:09:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27033
	for <mmusic@optimus.ietf.org>; Mon, 5 Aug 2002 16:09:00 -0400 (EDT)
Received: from chiron.nge.isi.edu (chiron.nge.isi.edu [65.114.169.204])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00004
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 16:07:47 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g75K8wX14190;
	Mon, 5 Aug 2002 16:08:59 -0400
Message-Id: <200208052008.g75K8wX14190@chiron.nge.isi.edu>
To: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Mon, 05 Aug 2002 10:20:31 +0200."
             <A2200E9A0E413B4C99FB7384D740878124DFC7@parmhs3.rd.francetelecom.fr> 
Date: Mon, 05 Aug 2002 16:08:58 -0400
From: Colin Perkins <csp@isi.edu>
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

That would seem to be something for the signalling protocol, since it
changes the media format. It's not clear to me that this information
can cleanly be siganlled in SDP though, it may be better suited to an
SDPng expression?

Colin



--> "MONFORT Patrick FTRD/DMI/ISS" writes:
>Hello,
>
>Th draft I mentioned in a previous mail
>"draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
>codec. How do you propose the manage them during a call.
>
>All thoses things are in the stream itself, but, a Video UA need a way
>to express them during the initiation of the call and to control them
>during the call.
>
>Thanks,
>
>Patrick,
>
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: vendredi 26 juillet 2002 19:46
>To: MONFORT Patrick FTRD/DMI/ISS
>Cc: mmusic@ietf.org
>Subject: Re: [MMUSIC] video media control draft 
>
>
>I'm not sure we agree on the list of other things are needed. Some form
>of
>fast intro request, certainly, but what else? Freeze has been discussed,
>but that may not be necessary. Are there others?
>
>Colin
>
>
>
>--> "MONFORT Patrick FTRD/DMI/ISS" writes:
>>Yes, that would help.
>>
>>As other things are needed, would it be possible to have/imagine an
>>attribute in the SDP (associated to media or the session) that can
>>manage all the "control" aspect of media. UA could listen on this
>>"control" port to receive command from other(s) party(ies).
>>
>>Or else, if we don't want to manage a new port, I think we will have a
>>new SIP message that will carry a new SDP with constraints on it (like
>>to update only attribute of the declared media) ?
>>
>>
>>-----Original Message-----
>>From: Colin Perkins [mailto:csp@isi.edu]
>>Sent: mercredi 24 juillet 2002 22:38
>>To: MONFORT Patrick FTRD/DMI/ISS
>>Cc: Joerg Ott; Orit Levin; mmusic@ietf.org
>>Subject: Re: [MMUSIC] video media control draft 
>>
>>
>>--> "MONFORT Patrick FTRD/DMI/ISS" writes:
>>...deleted...
>>>Regarding the control, RFC 2032 (which describes RTCP packet for
>>>IntraRequest) can't be deployed. The reason is that these RTCP packets
>>>are not sent to the 'standard' RTCP Port.
>>>
>>>Here are the text taken from RFC 2032, that explains this issue
>>(section
>>>5.1):
>>>
>>>"
>>>The H.261-specific control packets differ from normal RTCP packets in
>>>   that they are not transmitted to the normal RTCP destination
>>>   transport address for the RTP session (which is often a multicast
>>>   address).  Instead, these control packets are sent directly via
>>>   unicast from the decoder to the coder.  The destination port for
>>>   these control packets is the same port that the coder uses as a
>>>   source port for transmitting RTP (data) packets.  Therefore, these
>>>   packets may be considered "reverse" control packets.
>>>
>>>   As a consequence, these control packets may only be used when no
>RTP
>>>   mixers or translators intervene in the path from the coder to the
>>>   decoder.  If such intermediate systems do intervene, the address of
>>>   the coder would no longer be present as the network-level source
>>>   address in packets received by the decoder, and in fact, it might
>>not
>>>   be possible for the decoder to send packets directly to the coder.
>>>"
>>
>>The proposal is to use the same FIR packet format as in RFC 2032, but
>to
>>send the request to the standard RTCP port, using the mechanisms from
>>draft-ietf-avt-rtcp-feedback-03.txt to ensure timely feedback. Would 
>>that help?
>>
>>Colin
>
>_______________________________________________
>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 daemon@optimus.ietf.org  Mon Aug  5 16:21:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00583
	for <mmusic-archive@odin.ietf.org>; Mon, 5 Aug 2002 16:21:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA27477
	for mmusic-archive@odin.ietf.org; Mon, 5 Aug 2002 16:23:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27441;
	Mon, 5 Aug 2002 16:20:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27410
	for <mmusic@optimus.ietf.org>; Mon, 5 Aug 2002 16:20:48 -0400 (EDT)
Received: from nmh.informatik.uni-bremen.de (jo@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00523
	for <mmusic@ietf.org>; Mon, 5 Aug 2002 16:19:34 -0400 (EDT)
Received: (from jo@localhost)
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) id g75KKZn02337;
	Mon, 5 Aug 2002 22:20:35 +0200 (MEST)
From: Joerg Ott <jo@Informatik.Uni-Bremen.DE>
Message-Id: <200208052020.g75KKZn02337@nmh.informatik.uni-bremen.de>
Subject: Re: [MMUSIC] video media control draft
To: csp@isi.edu (Colin Perkins)
Date: Mon, 5 Aug 2002 22:20:35 +0200 (MEST)
Cc: patrick.monfort@rd.francetelecom.com (MONFORT Patrick FTRD/DMI/ISS),
        mmusic@ietf.org
In-Reply-To: <200208052008.g75K8wX14190@chiron.nge.isi.edu> from "Colin Perkins" at Aug 05, 2002 04:08:58 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

> 
> That would seem to be something for the signalling protocol, since it
> changes the media format. It's not clear to me that this information
> can cleanly be siganlled in SDP though, it may be better suited to an
> SDPng expression?

That's the idea.  And as discussed at the last IETF, we start looking
into a video profile right now.  Depending on the video conferencing
requirements, you may need a few (trivial) parameters in SDP though.

Joerg


> --> "MONFORT Patrick FTRD/DMI/ISS" writes:
> >Hello,
> >
> >Th draft I mentioned in a previous mail
> >"draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
> >codec. How do you propose the manage them during a call.
> >
> >All thoses things are in the stream itself, but, a Video UA need a way
> >to express them during the initiation of the call and to control them
> >during the call.
> >
> >Thanks,
> >
> >Patrick,
> >
> >
> >-----Original Message-----
> >From: Colin Perkins [mailto:csp@isi.edu]
> >Sent: vendredi 26 juillet 2002 19:46
> >To: MONFORT Patrick FTRD/DMI/ISS
> >Cc: mmusic@ietf.org
> >Subject: Re: [MMUSIC] video media control draft 
> >
> >
> >I'm not sure we agree on the list of other things are needed. Some form
> >of
> >fast intro request, certainly, but what else? Freeze has been discussed,
> >but that may not be necessary. Are there others?
> >
> >Colin
> >
> >
> >
> >--> "MONFORT Patrick FTRD/DMI/ISS" writes:
> >>Yes, that would help.
> >>
> >>As other things are needed, would it be possible to have/imagine an
> >>attribute in the SDP (associated to media or the session) that can
> >>manage all the "control" aspect of media. UA could listen on this
> >>"control" port to receive command from other(s) party(ies).
> >>
> >>Or else, if we don't want to manage a new port, I think we will have a
> >>new SIP message that will carry a new SDP with constraints on it (like
> >>to update only attribute of the declared media) ?
> >>
> >>
> >>-----Original Message-----
> >>From: Colin Perkins [mailto:csp@isi.edu]
> >>Sent: mercredi 24 juillet 2002 22:38
> >>To: MONFORT Patrick FTRD/DMI/ISS
> >>Cc: Joerg Ott; Orit Levin; mmusic@ietf.org
> >>Subject: Re: [MMUSIC] video media control draft 
> >>
> >>
> >>--> "MONFORT Patrick FTRD/DMI/ISS" writes:
> >>...deleted...
> >>>Regarding the control, RFC 2032 (which describes RTCP packet for
> >>>IntraRequest) can't be deployed. The reason is that these RTCP packets
> >>>are not sent to the 'standard' RTCP Port.
> >>>
> >>>Here are the text taken from RFC 2032, that explains this issue
> >>(section
> >>>5.1):
> >>>
> >>>"
> >>>The H.261-specific control packets differ from normal RTCP packets in
> >>>   that they are not transmitted to the normal RTCP destination
> >>>   transport address for the RTP session (which is often a multicast
> >>>   address).  Instead, these control packets are sent directly via
> >>>   unicast from the decoder to the coder.  The destination port for
> >>>   these control packets is the same port that the coder uses as a
> >>>   source port for transmitting RTP (data) packets.  Therefore, these
> >>>   packets may be considered "reverse" control packets.
> >>>
> >>>   As a consequence, these control packets may only be used when no
> >RTP
> >>>   mixers or translators intervene in the path from the coder to the
> >>>   decoder.  If such intermediate systems do intervene, the address of
> >>>   the coder would no longer be present as the network-level source
> >>>   address in packets received by the decoder, and in fact, it might
> >>not
> >>>   be possible for the decoder to send packets directly to the coder.
> >>>"
> >>
> >>The proposal is to use the same FIR packet format as in RFC 2032, but
> >to
> >>send the request to the standard RTCP port, using the mechanisms from
> >>draft-ietf-avt-rtcp-feedback-03.txt to ensure timely feedback. Would 
> >>that help?
> >>
> >>Colin
> >
> >_______________________________________________
> >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 daemon@optimus.ietf.org  Tue Aug  6 02:00:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17989
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 02:00:36 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA05066
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 02:01:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA04743;
	Tue, 6 Aug 2002 02:00:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA04706
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 02:00:31 -0400 (EDT)
Received: from accord-ntsrv3.accord.co.il ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17172
	for <mmusic@ietf.org>; Tue, 6 Aug 2002 01:59:16 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <QLHNRN4N>; Tue, 6 Aug 2002 08:59:51 +0300
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136A8A@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Petri K. Koskelainen'" <petkos@cs.columbia.edu>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Tue, 6 Aug 2002 08:59:51 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Hi Petri,
In my draft draft-even-mmusic-video-media-control-00.txt, I have a
video-resolution attribute that allow to specify the maximum frame rate
supported per resolution. In the meeting this attribute was accepted for
SDP. I could not find the draft mentioned "draft-koskelainen-sdp263-02.txt"
Thanks
Roni Even

> -----Original Message-----
> From: Petri K. Koskelainen [mailto:petkos@cs.columbia.edu]
> Sent: Monday, August 05, 2002 6:45 PM
> To: mmusic@ietf.org
> Subject: [MMUSIC] video media control draft
> 
> 
> 
> Hi,
> 
> That draft works only for H.263 codec so it is not
> a general solution. Moreover, using SDP a line 
> to express options (or group of options and 
> complex restrictions) is very difficult.
> 
> In the setup phase, you could advertize your
> codec capabilities (in SDP), so it
> is possible to change options during a call
> without further signaling. But I guess
> it makes sense to inform also signaling level
> about the change (since e.g. bandwidth requirement 
> may change considerably if you change options).
> 
> 
> Petri
> 
> -----------------------------
> 
> Hello,
> 
> Th draft I mentioned in a previous mail
> "draft-koskelainen-sdp263-02.txt" deals with SIZE and OPTIONS of video
> codec. How do you propose the manage them during a call.
> 
> All thoses things are in the stream itself, but, a Video UA need a way
> to express them during the initiation of the call and to control them
> during the call.
> 
> Thanks,
> 
> Patrick,
> 
> 
> _______________________________________________
> 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 daemon@optimus.ietf.org  Tue Aug  6 03:42:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28503
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 03:42:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA10413
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 03:44:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09826;
	Tue, 6 Aug 2002 03:35:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09793
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 03:35:14 -0400 (EDT)
Received: from prix.tandberg.no (prix.tandberg.no [193.212.161.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28243
	for <mmusic@ietf.org>; Tue, 6 Aug 2002 03:33:59 -0400 (EDT)
Received: from there ([10.0.2.14])
	by prix.tandberg.no (8.11.6/8.11.6) with SMTP id g767Ydu21987;
	Tue, 6 Aug 2002 09:34:39 +0200
Message-Id: <200208060734.g767Ydu21987@prix.tandberg.no>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Nils Henrik Lorentzen <nhl@tandberg.no>
Organization: TANDBERG ASA
To: mmusic@ietf.org, "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [MMUSIC] video media control draft
Date: Tue, 6 Aug 2002 09:34:36 +0200
X-Mailer: KMail [version 1.3.1]
References: <C550397C3B6AEB418E62170D9E349CE2136A8A@ACCORD-NTSRV3>
In-Reply-To: <C550397C3B6AEB418E62170D9E349CE2136A8A@ACCORD-NTSRV3>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.14 (www dot roaringpenguin dot com slash mimedefang)
Content-Transfer-Encoding: 8bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 8bit

On Tuesday 06 August 2002 07:59, Even, Roni wrote:

> Hi Petri,
> In my draft draft-even-mmusic-video-media-control-00.txt, I have a
> video-resolution attribute that allow to specify the maximum frame rate
> supported per resolution.

A difference between your draft and draft-koskelainen-sdp263-02.txt is that 
in the latter you may specify resolutions and options per payload type, 
instead of per media line. I think this is more flexible, and would suit our 
needs better. Any particular reason for having it per media-line ?

In your draft it would be a simple change to make it per payload:
a=video-resolution:<size>
to
a=video-resolution: <payload no> <size>
or possibly
a=video-resolution: [ PT=<payload no>] <size>
ie payload no is optional, so if not specified the resolutions would apply to 
all the payload types on the media line.

> In the meeting this attribute was accepted for
> SDP. I could not find the draft mentioned "draft-koskelainen-sdp263-02.txt"

It expired quite some time ago, but can be found at:
http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelainen-sdp263-02.txt

Nils Henrik Lorentzen


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



From daemon@optimus.ietf.org  Tue Aug  6 08:29:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07937
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 08:29:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA02015
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 08:30:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01666;
	Tue, 6 Aug 2002 08:25:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01638
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 08:25:40 -0400 (EDT)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07596
	for <mmusic@ietf.org>; Tue, 6 Aug 2002 08:24:25 -0400 (EDT)
Received: from tzi.uni-bremen.de (root@localhost [127.0.0.1])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g76CPK225189;
	Tue, 6 Aug 2002 14:25:20 +0200 (MEST)
Message-ID: <3D4FC0B5.25445F81@tzi.uni-bremen.de>
Date: Tue, 06 Aug 2002 14:27:33 +0200
From: Joerg Ott <jo@tzi.uni-bremen.de>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
CC: Orit Levin <orit@radvision.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft
References: <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Roni,

thanks for the reply.  Comments inline.

> The freeze tells the decoder to continue to decode but to not present until
> the freeze is released. The release is caused by asking from the encoder a
> new full frame, so maybe this is the state change since it releases the
> decoder from the released state.
> The reasons for the freeze.
> 1. A mixer can just switch the video without handling of the RTP format, so
> the mixer is not looking for the new picture in the RTP payload and may
> start sending from the new source before the full picture. This will cause
> the decoder to use delta pictures on a previous source information.

You should have other information at hand: the SSRC (in case of a
translator)
or the CSRC (in case of a mixer) will be different.

> 2. A mixer that looks at the information and start to send the new source
> information only after detecting a full picture may still want to use freeze
> in order to let the decoder know that a source switch has occurred, this is
> important if the mixer do not change the RTP sequence numbers in order to
> keep the sequence numbers from the source. The decoder may think that he
> lost packets due to jump in sequence number if he does not know that a
> switch has occurred.

Again, shouldn't a source change result in a different SSRC/CSRC?

> 3. This is a more advanced one. If we are doing continuous presence based on
> taking 4 QCIF images from different source and building a composite CIF
> picture, using freeze gives us an option to let the decoder start decoding
> after all 4 pictures are available when building the initial picture, the
> decoder will get the other full pictures and since he continues to decode
> then when the last full QCIF is available, the mixer will release the freeze
> and the display will be OK. The same goes for changing one of the QCIF
> sources during the conference.

Ok.  That's a good one.  Thanks for elaborating on this.

> As for your design comment, I do not think that we have a design problem in
> H.323. In H.320 the signalling and media are synchronized like in IP. They

Still, I don't think they are in IP as they take different paths with
unknown
latency properties.

> run in the same pipe but may have different latencies due to fixed channels
> BW, furthermore the fast update and streams are in reverse directions. Also
> for fast update the issue is not to have it synchronized with the switch on
> the mixer but to have it delivered to the encoder so it will happen sometime
> after the switch and free the receiver from the freeze state so it will
> start presenting.
> 
> As for reliability we are OK with H.245 reliability and I assume will try to
> use TCP for videoconferencing due to all reasons mentioned in the SIP
> session.
> 
> AS for no go in SDP, I do not understand how you reached a consensus, I
> think that we are still arguing the issue and will keep our draft alive.

SDP does not make sense for the FIR command.  I think enough people have
argued this and I would like to close this part of the debate and focus
on alternatives.

The rest of the SDP extensions you are proposing (picture size, etc.) are
fine.  We surely had consensus on this.

> Again, I can give you a rough consensus from the video conferencing people
> that RTCP is not a solution for us and since the requirement is coming from
> people that are doing video conferencing and have the knowledge you cannot
> come and say that you should have the solution on RTCP even if it does not
> work. I think that the AVT guys did not agree on a must anyhow since RTCP is
> for indication and not for commands.

I believe have seen statements from videoconferencing folks that did
not favor the SDP approach.  We are just trying to find a solution
that fits the spirit of the protocols we are using.

> As for SIP, are you stirring us to a INFO based solution , I am not aware of
> other existing solution

I hope that I did not convey this impression.  I would like to keep you
away
from INFO as far as possible.  In my opinion, INFO should be treated as if
it
were non-existent.

Joerg

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



From daemon@optimus.ietf.org  Tue Aug  6 11:44:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15594
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 11:44:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12035
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 11:45:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11983;
	Tue, 6 Aug 2002 11:43:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11951
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 11:43:41 -0400 (EDT)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15555
	for <mmusic@ietf.org>; Tue, 6 Aug 2002 11:42:24 -0400 (EDT)
Received: from tzi.uni-bremen.de (root@localhost [127.0.0.1])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g76FhJ213365;
	Tue, 6 Aug 2002 17:43:19 +0200 (MEST)
Message-ID: <3D4FEF13.D0FB68A0@tzi.uni-bremen.de>
Date: Tue, 06 Aug 2002 17:45:23 +0200
From: Joerg Ott <jo@tzi.uni-bremen.de>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Orit Levin <orit@radvision.com>
CC: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: Re: [MMUSIC] Signaling FIR/Freeze in SIP
References: <0D5BBF5D638DD4119E3400508BD949450188561C@RADVPOST>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Orit and all,

I have gone through a number of scenarios and, apparently, one particular
case of H.323-SIP interworking (namely if an H.323 endpoint is connected
via a piece of SIP in the middle to a SIP- or H.323-based MCU) is not
workable at all with just RTCP.  So, what we are doing right now is
solely for the purpose of interworking.

Your proposal to provide a description of the actual event information
to be conveyed has merit -- particularly as it can be discussed 
independently of the transport used later on to carry it.  In addition,
we obviously need to define a MIME type for this data format.

I would like to encourage you to think a bit beyond the pure video
conferencing applications as it would be perfect if we could keep
whatever we come up with right now and build on this for the future
rather than having two or more mechanisms to deal with eventually.

As for the transport: you know that I am very much opposed to tunneling
in SIP INFO, so I'd still like to research other ways -- even within
SIP -- to carry this contents.  Basically, what you want to do is
have the MCU provide an endpoint with an indication/command that a
new intra frame is needed.  Can this information be derived from a
(slightly extended) conference event package or modeled as a different
application-specific event package?  After all, the intra frame is
triggered by a change in the "viewer status" (who sees the video of
the endpoint) which should be watchable in some way.

From what Roni and myself have discussed, the conference package is
insufficient insofar as the send-status types defined so far
("received-by-all", "muted", "unknown") do not allow to reflect the
transition you are interested in.  Adding "received-by-one" would
solve only part of the problem.  But a meaningful addition may make
sense to be explored here (and obtain all you need from a mechanism
already under development).  A SIP MCU is likely to support the
conference package anyway.

Of course, any SIP-H.323 gateway would need to be aware that the
user is connected to a conference and subscribe to the respective
state.  But, on the other hand, it would need to translate SIP INFO
into some H.323 stuff, too.  So while being potentially cleaner,
using SUBSCRIBE/NOTIFY is not worse from the backwards compatibility
point of view.

Thoughts?

Joerg

> Since, there is no agreement to standardize the required primitives within
> the old SDP and taking into account all the drawbacks of such a solution,
> there is no point pursuing this direction.
> 
> Instead, we need two things:
> 1. Working on a new point-to-point media control protocol
> 2. Agree on a doable way (such as INFO) to convey the required primitives in
> the call signaling path. It doesn't have to be a standard.
> 
> For all the practical reasons, multimedia vendors will need to support both.
> 
> We (as RADVISION together with its partners) already have a simple
> extensible XML scheme to be conveyed in the INFO messages for exactly this
> purpose. I plan to publish it as an IETF draft shortly.
> 
> BR,
> Orit Levin
> Chief Architect
> RADVISION Inc.
> Tel:  +1.201.689.6330
> 
>  -----Original Message-----
> From:   Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> Sent:   Wednesday, July 31, 2002 6:04 AM
> To:     mmusic@ietf.org
> Subject:        [MMUSIC] Signaling FIR/Freeze in SIP
> 
> Hi,
> 
> We at TANDBERG would like to voice our opinion on the full intra/freeze
> request issue, as the decision made may affect us in the future.
> 
> There are as far as we can see three proposed solutions to the problem of
> signaling these requests within the SIP framework:
> 
> 1. Use RTCP
> 2. Use SDP
> 3. Some kind of new protocol tunneled in INFO or a similar SIP method.
> 
> Our opinion so far:
> 
> 1. This is in our opinion the best solution from a design perspective. We
> see
> it this way: Keeping a good quality video stream and output is an issue
> between the encoder and decoder, thus information for that purpose should be
> 
> sent directly between them. Ideally it should not be sent along the
> signaling
> path, but along the media path.
> 
> There seems to be two main arguments against the RTCP solution:
> 
> - RTCP is not reliable.
> We agree with Colin, in that this is a non-issue. The FIR message could be
> retransmitted until a full intra is received. As for freeze requests, these
> could be retransmitted a predefined number of times with a predefined
> interval. If any of them arrive at the decoder all is fine. In the rare case
> 
> where none do, the user will see some ugly video output for a relatively
> small amount of time, until it receives a full intra, but it will not
> otherwise affect the call.
> There may be issues here we have not thought of, though.
> 
> - H.323 EPs do not support these new RTCP packets. We think this is more of
> an issue. As Roni pointed out, a SIP/H.323 signaling GW would not be able to
> 
> gather the FIR requests from the SIP side and pass it on to the H.323 side,
> unless it is also acts as GW for the RTP/RTCP traffic. The latter is of
> course not ideal, but could do as a temporary solution. One would probably
> need to add a new option flag to H.323 call setup messages telling whether
> the endpoint supports FIR/freeze in RTCP.
> 
> 2. Using a media attribute in SDP for signaling a FIR is wrong in our
> opinion. SDPs are for telling what kind of streams you want from the time
> you
> send it until the next time you send an SDP.  A full intra is a request that
> 
> is executed only once when received.
> 
> We believe the following can be used as a "litmus test" for determining what
> 
> information is OK to send in SDP and what is not:
> 
> If an endpoint sends the exact same SDP to another endpoint several times in
> 
> sequence, only the first SDP arriving at remote should trigger any
> change/sideeffects.
> 
> This holds true in for example hold/resume but not for full intra req.
> 
> 3. This is in our opinion not the ideal solution from a design POV, but it
> will interoperate better with existing H.323 EPs when SIP/H323 GWs are
> implemented. It would require a new protocol to be defined., but could be a
> very simple and limited protocol though, as it would just be a temporary
> solution.
> We would possibly need a new such protocol when SDPng arrives, since we have
> 
> to refer to a SDPng media channel in a different manner than refering to an
> SDP channel.
> 
> To conclude, we support solutions 1 and 3, while 2 is definitely the worst
> alternative. While using RTCP (or similar protocol directly between
> encoder/decoder) is in our opinion the cleanest solution, 3 might be used if
> 
> the SIP/H.323 switching problem is deemed important enough and no other
> problems with using RTCP are found.
> 
> Nils Henrik Lorentzen
> 
> Software Developer
> TANDBERG
> http://www.tandberg.net
> 
> _______________________________________________
> 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 daemon@optimus.ietf.org  Tue Aug  6 14:40:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23079
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 14:40:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA23788
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 14:41:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23552;
	Tue, 6 Aug 2002 14:36:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23407
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 14:33:10 -0400 (EDT)
Received: from igw3.watson.ibm.com (igw3.watson.ibm.com [198.81.209.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22829;
	Tue, 6 Aug 2002 14:31:57 -0400 (EDT)
Received: from sp1n293en1.watson.ibm.com (sp1n293en1.watson.ibm.com [9.2.112.57])
	by igw3.watson.ibm.com (8.11.4/8.11.4) with ESMTP id g76IWdC15210;
	Tue, 6 Aug 2002 14:32:39 -0400
Received: from ornavella.watson.ibm.com (ornavella.watson.ibm.com [9.2.16.80])
	by sp1n293en1.watson.ibm.com (8.11.4/8.11.4) with ESMTP id g76IWdH48702;
	Tue, 6 Aug 2002 14:32:39 -0400
Received: (from canetti@localhost)
	by ornavella.watson.ibm.com (AIX4.3/8.9.3/8.9.3/01-10-2000) id OAA34826;
	Tue, 6 Aug 2002 14:32:38 -0400
Date: Tue, 6 Aug 2002 14:32:38 -0400
From: Ran Canetti <canetti@watson.ibm.com>
Message-Id: <200208061832.OAA34826@ornavella.watson.ibm.com>
To: avt@ietf.org, mmusic@ietf.org, msec@securemulticast.org
Subject: [MMUSIC] Implementing MIKEY: A straw poll
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org


Folks,

This note is meant as a "straw poll" for finding out the level of
interest people have in implementing the MIKEY key exchange protocol
(draft-ietf-msec-mikey-03.txt).

MIKEY is designed to work well with real-time multimedia applications
(both 1:1, 1:M, and M:M). In particular, it is designed to support the
SRTP data encryption and authentication protocl.

Last fall, the protocol was accepted as a work item at MSEC, following
requests within the MMUSIC and AVT working groups. It now seems to have
stabilized. The MIKEY authors have approached us requesting a last call, 
and we are in the process of issuing that last call.

So, is any of you folks implementing it? is anyone planning on
implementing it once it is standardized? Please let us know.

Also, if you're even remotely thinking of implementing it, then NOW is the
time to go over it and make comments!

Best,

Ran Canetti
Thomas Hardjono
MSEC co-chairs



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



From daemon@optimus.ietf.org  Tue Aug  6 15:55:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26622
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 15:55:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28505
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 15:56:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28199;
	Tue, 6 Aug 2002 15:50:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28150
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 15:50:23 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26303;
	Tue, 6 Aug 2002 15:49:08 -0400 (EDT)
Received: from mira-sjc5-6.cisco.com (IDENT:mirapoint@mira-sjc5-6.cisco.com [171.71.163.23])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g76JnphI003048;
	Tue, 6 Aug 2002 12:49:51 -0700 (PDT)
Received: from mbaugher-w2k1.cisco.com (stealth-10-34-251-93.cisco.com [10.34.251.93])
	by mira-sjc5-6.cisco.com (Mirapoint)
	with SMTP id ACG15900;
	Tue, 6 Aug 2002 12:46:56 -0700 (PDT)
Message-Id: <4.3.2.7.2.20020806124135.04bfaa80@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 06 Aug 2002 12:47:27 -0700
To: Ran Canetti <canetti@watson.ibm.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [MMUSIC] Implementing MIKEY: A straw poll
Cc: avt@ietf.org, mmusic@ietf.org, msec@securemulticast.org
In-Reply-To: <200208061832.OAA34826@ornavella.watson.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

hi Ran,
    The problem with your question is that product plans and internal 
company prototype development are often not to be shared on public mailing 
lists.  Reference implementations don't suffer from this limitation, so I'm 
curious to know the status of the MIKEY reference implementation.  Also, 
I'm concerned that there has been very little discussion of MIKEY within 
MSEC or any other WGs that I know.  I think there was one note posted on 
the latest MIKEY draft.  I had a number of issues with the last draft and 
plan to read it the new version as soon as I can.

Mark

At 02:32 PM 8/6/2002 -0400, Ran Canetti wrote:

>Folks,
>
>This note is meant as a "straw poll" for finding out the level of
>interest people have in implementing the MIKEY key exchange protocol
>(draft-ietf-msec-mikey-03.txt).
>
>MIKEY is designed to work well with real-time multimedia applications
>(both 1:1, 1:M, and M:M). In particular, it is designed to support the
>SRTP data encryption and authentication protocl.
>
>Last fall, the protocol was accepted as a work item at MSEC, following
>requests within the MMUSIC and AVT working groups. It now seems to have
>stabilized. The MIKEY authors have approached us requesting a last call,
>and we are in the process of issuing that last call.
>
>So, is any of you folks implementing it? is anyone planning on
>implementing it once it is standardized? Please let us know.
>
>Also, if you're even remotely thinking of implementing it, then NOW is the
>time to go over it and make comments!
>
>Best,
>
>Ran Canetti
>Thomas Hardjono
>MSEC co-chairs
>
>
>
>_______________________________________________
>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 daemon@optimus.ietf.org  Tue Aug  6 17:47:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00753
	for <mmusic-archive@odin.ietf.org>; Tue, 6 Aug 2002 17:47:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA05348
	for mmusic-archive@odin.ietf.org; Tue, 6 Aug 2002 17:48:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA05198;
	Tue, 6 Aug 2002 17:43:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA05169
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 17:43:31 -0400 (EDT)
Received: from radvpost.us.radvision.com ([12.44.63.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00587
	for <mmusic@ietf.org>; Tue, 6 Aug 2002 17:42:15 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2653.19)
	id <PC5BM6F9>; Tue, 6 Aug 2002 17:42:30 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD9494501885652@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>
Cc: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] Signaling FIR/Freeze in SIP
Date: Tue, 6 Aug 2002 17:42:29 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Joerg and all!
These are my thoughts:
1. The XML scheme is defined as a general Media Control Protocol. Video
specific commands are arranged under a separate branch.
2. I think that developing this initial work into a complete standard
protocol is doable and would be very beneficial.
3. The transport of this protocol is (almost) a separate topic. We can spend
more time on this in SIP/SIPPING in parallel to the protocol definition
itself in MMUSIC.
4. In regards to using the Events mechanism:
a. I wouldn't like to ignite a debate about the applicability of the
Subscribe/Event approach to a CONTROL protocol in general. I would just say
that, in my opinion, it is a real twist to the whole EVENTs' purpose. 
b. Additionally, it carries all the cons of SIP being used for Media Control
with only a "slight improvement" (from a standardization point of view) by
using the Packages' concept.
c. A Media Control protocol doesn't have to be SIP.
d. My main opposition to the EVENTs mechanism is because its Data Model
would be completely different from a straight-forward CONTROL protocol. If,
as a multimedia vendor, I need in parallel to support both, I would "prefer"
to implement two similar (or very close) data models that differ in their
transport only.

Hope it makes sense,
Orit .

 -----Original Message-----
From: 	Joerg Ott [mailto:jo@tzi.uni-bremen.de] 
Sent:	Tuesday, August 06, 2002 11:45 AM
To:	Orit Levin
Cc:	'Nils Henrik Lorentzen'; mmusic@ietf.org
Subject:	Re: [MMUSIC] Signaling FIR/Freeze in SIP

Orit and all,

I have gone through a number of scenarios and, apparently, one particular
case of H.323-SIP interworking (namely if an H.323 endpoint is connected
via a piece of SIP in the middle to a SIP- or H.323-based MCU) is not
workable at all with just RTCP.  So, what we are doing right now is
solely for the purpose of interworking.

Your proposal to provide a description of the actual event information
to be conveyed has merit -- particularly as it can be discussed 
independently of the transport used later on to carry it.  In addition,
we obviously need to define a MIME type for this data format.

I would like to encourage you to think a bit beyond the pure video
conferencing applications as it would be perfect if we could keep
whatever we come up with right now and build on this for the future
rather than having two or more mechanisms to deal with eventually.

As for the transport: you know that I am very much opposed to tunneling
in SIP INFO, so I'd still like to research other ways -- even within
SIP -- to carry this contents.  Basically, what you want to do is
have the MCU provide an endpoint with an indication/command that a
new intra frame is needed.  Can this information be derived from a
(slightly extended) conference event package or modeled as a different
application-specific event package?  After all, the intra frame is
triggered by a change in the "viewer status" (who sees the video of
the endpoint) which should be watchable in some way.

From what Roni and myself have discussed, the conference package is
insufficient insofar as the send-status types defined so far
("received-by-all", "muted", "unknown") do not allow to reflect the
transition you are interested in.  Adding "received-by-one" would
solve only part of the problem.  But a meaningful addition may make
sense to be explored here (and obtain all you need from a mechanism
already under development).  A SIP MCU is likely to support the
conference package anyway.

Of course, any SIP-H.323 gateway would need to be aware that the
user is connected to a conference and subscribe to the respective
state.  But, on the other hand, it would need to translate SIP INFO
into some H.323 stuff, too.  So while being potentially cleaner,
using SUBSCRIBE/NOTIFY is not worse from the backwards compatibility
point of view.

Thoughts?

Joerg

> Since, there is no agreement to standardize the required primitives within
> the old SDP and taking into account all the drawbacks of such a solution,
> there is no point pursuing this direction.
> 
> Instead, we need two things:
> 1. Working on a new point-to-point media control protocol
> 2. Agree on a doable way (such as INFO) to convey the required primitives
in
> the call signaling path. It doesn't have to be a standard.
> 
> For all the practical reasons, multimedia vendors will need to support
both.
> 
> We (as RADVISION together with its partners) already have a simple
> extensible XML scheme to be conveyed in the INFO messages for exactly this
> purpose. I plan to publish it as an IETF draft shortly.
> 
> BR,
> Orit Levin
> Chief Architect
> RADVISION Inc.
> Tel:  +1.201.689.6330
> 
>  -----Original Message-----
> From:   Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> Sent:   Wednesday, July 31, 2002 6:04 AM
> To:     mmusic@ietf.org
> Subject:        [MMUSIC] Signaling FIR/Freeze in SIP
> 
> Hi,
> 
> We at TANDBERG would like to voice our opinion on the full intra/freeze
> request issue, as the decision made may affect us in the future.
> 
> There are as far as we can see three proposed solutions to the problem of
> signaling these requests within the SIP framework:
> 
> 1. Use RTCP
> 2. Use SDP
> 3. Some kind of new protocol tunneled in INFO or a similar SIP method.
> 
> Our opinion so far:
> 
> 1. This is in our opinion the best solution from a design perspective. We
> see
> it this way: Keeping a good quality video stream and output is an issue
> between the encoder and decoder, thus information for that purpose should
be
> 
> sent directly between them. Ideally it should not be sent along the
> signaling
> path, but along the media path.
> 
> There seems to be two main arguments against the RTCP solution:
> 
> - RTCP is not reliable.
> We agree with Colin, in that this is a non-issue. The FIR message could be
> retransmitted until a full intra is received. As for freeze requests,
these
> could be retransmitted a predefined number of times with a predefined
> interval. If any of them arrive at the decoder all is fine. In the rare
case
> 
> where none do, the user will see some ugly video output for a relatively
> small amount of time, until it receives a full intra, but it will not
> otherwise affect the call.
> There may be issues here we have not thought of, though.
> 
> - H.323 EPs do not support these new RTCP packets. We think this is more
of
> an issue. As Roni pointed out, a SIP/H.323 signaling GW would not be able
to
> 
> gather the FIR requests from the SIP side and pass it on to the H.323
side,
> unless it is also acts as GW for the RTP/RTCP traffic. The latter is of
> course not ideal, but could do as a temporary solution. One would probably
> need to add a new option flag to H.323 call setup messages telling whether
> the endpoint supports FIR/freeze in RTCP.
> 
> 2. Using a media attribute in SDP for signaling a FIR is wrong in our
> opinion. SDPs are for telling what kind of streams you want from the time
> you
> send it until the next time you send an SDP.  A full intra is a request
that
> 
> is executed only once when received.
> 
> We believe the following can be used as a "litmus test" for determining
what
> 
> information is OK to send in SDP and what is not:
> 
> If an endpoint sends the exact same SDP to another endpoint several times
in
> 
> sequence, only the first SDP arriving at remote should trigger any
> change/sideeffects.
> 
> This holds true in for example hold/resume but not for full intra req.
> 
> 3. This is in our opinion not the ideal solution from a design POV, but it
> will interoperate better with existing H.323 EPs when SIP/H323 GWs are
> implemented. It would require a new protocol to be defined., but could be
a
> very simple and limited protocol though, as it would just be a temporary
> solution.
> We would possibly need a new such protocol when SDPng arrives, since we
have
> 
> to refer to a SDPng media channel in a different manner than refering to
an
> SDP channel.
> 
> To conclude, we support solutions 1 and 3, while 2 is definitely the worst
> alternative. While using RTCP (or similar protocol directly between
> encoder/decoder) is in our opinion the cleanest solution, 3 might be used
if
> 
> the SIP/H.323 switching problem is deemed important enough and no other
> problems with using RTCP are found.
> 
> Nils Henrik Lorentzen
> 
> Software Developer
> TANDBERG
> http://www.tandberg.net
> 
> _______________________________________________
> 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 daemon@optimus.ietf.org  Wed Aug  7 02:16:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24127
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 02:16:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA16902
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 02:17:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06790;
	Wed, 7 Aug 2002 02:12:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06761
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 02:12:26 -0400 (EDT)
Received: from accord-ntsrv3.accord.co.il ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22760
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 02:11:10 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <QLHNRSFL>; Wed, 7 Aug 2002 09:11:46 +0300
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136A93@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Orit Levin <orit@radvision.com>
Cc: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] Signaling FIR/Freeze in SIP
Date: Wed, 7 Aug 2002 09:11:46 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Joerg,
I think you did not look at the case where we have an H.323 MCU connected
through a signalling GW to a SIP client or an H.320 MCU connected through a
GW to the SIP client. In that case the GW function will need to include the
support for the control package, so it is not only for MCU to implement this
package.
Roni Even

> -----Original Message-----
> From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
> Sent: Tuesday, August 06, 2002 6:45 PM
> To: Orit Levin
> Cc: 'Nils Henrik Lorentzen'; mmusic@ietf.org
> Subject: Re: [MMUSIC] Signaling FIR/Freeze in SIP
> 
> 
> Orit and all,
> 
> I have gone through a number of scenarios and, apparently, 
> one particular
> case of H.323-SIP interworking (namely if an H.323 endpoint 
> is connected
> via a piece of SIP in the middle to a SIP- or H.323-based MCU) is not
> workable at all with just RTCP.  So, what we are doing right now is
> solely for the purpose of interworking.
> 
> Your proposal to provide a description of the actual event information
> to be conveyed has merit -- particularly as it can be discussed 
> independently of the transport used later on to carry it.  In 
> addition,
> we obviously need to define a MIME type for this data format.
> 
> I would like to encourage you to think a bit beyond the pure video
> conferencing applications as it would be perfect if we could keep
> whatever we come up with right now and build on this for the future
> rather than having two or more mechanisms to deal with eventually.
> 
> As for the transport: you know that I am very much opposed to 
> tunneling
> in SIP INFO, so I'd still like to research other ways -- even within
> SIP -- to carry this contents.  Basically, what you want to do is
> have the MCU provide an endpoint with an indication/command that a
> new intra frame is needed.  Can this information be derived from a
> (slightly extended) conference event package or modeled as a different
> application-specific event package?  After all, the intra frame is
> triggered by a change in the "viewer status" (who sees the video of
> the endpoint) which should be watchable in some way.
> 
> From what Roni and myself have discussed, the conference package is
> insufficient insofar as the send-status types defined so far
> ("received-by-all", "muted", "unknown") do not allow to reflect the
> transition you are interested in.  Adding "received-by-one" would
> solve only part of the problem.  But a meaningful addition may make
> sense to be explored here (and obtain all you need from a mechanism
> already under development).  A SIP MCU is likely to support the
> conference package anyway.
> 
> Of course, any SIP-H.323 gateway would need to be aware that the
> user is connected to a conference and subscribe to the respective
> state.  But, on the other hand, it would need to translate SIP INFO
> into some H.323 stuff, too.  So while being potentially cleaner,
> using SUBSCRIBE/NOTIFY is not worse from the backwards compatibility
> point of view.
> 
> Thoughts?
> 
> Joerg
> 
> > Since, there is no agreement to standardize the required 
> primitives within
> > the old SDP and taking into account all the drawbacks of 
> such a solution,
> > there is no point pursuing this direction.
> > 
> > Instead, we need two things:
> > 1. Working on a new point-to-point media control protocol
> > 2. Agree on a doable way (such as INFO) to convey the 
> required primitives in
> > the call signaling path. It doesn't have to be a standard.
> > 
> > For all the practical reasons, multimedia vendors will need 
> to support both.
> > 
> > We (as RADVISION together with its partners) already have a simple
> > extensible XML scheme to be conveyed in the INFO messages 
> for exactly this
> > purpose. I plan to publish it as an IETF draft shortly.
> > 
> > BR,
> > Orit Levin
> > Chief Architect
> > RADVISION Inc.
> > Tel:  +1.201.689.6330
> > 
> >  -----Original Message-----
> > From:   Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> > Sent:   Wednesday, July 31, 2002 6:04 AM
> > To:     mmusic@ietf.org
> > Subject:        [MMUSIC] Signaling FIR/Freeze in SIP
> > 
> > Hi,
> > 
> > We at TANDBERG would like to voice our opinion on the full 
> intra/freeze
> > request issue, as the decision made may affect us in the future.
> > 
> > There are as far as we can see three proposed solutions to 
> the problem of
> > signaling these requests within the SIP framework:
> > 
> > 1. Use RTCP
> > 2. Use SDP
> > 3. Some kind of new protocol tunneled in INFO or a similar 
> SIP method.
> > 
> > Our opinion so far:
> > 
> > 1. This is in our opinion the best solution from a design 
> perspective. We
> > see
> > it this way: Keeping a good quality video stream and output 
> is an issue
> > between the encoder and decoder, thus information for that 
> purpose should be
> > 
> > sent directly between them. Ideally it should not be sent along the
> > signaling
> > path, but along the media path.
> > 
> > There seems to be two main arguments against the RTCP solution:
> > 
> > - RTCP is not reliable.
> > We agree with Colin, in that this is a non-issue. The FIR 
> message could be
> > retransmitted until a full intra is received. As for freeze 
> requests, these
> > could be retransmitted a predefined number of times with a 
> predefined
> > interval. If any of them arrive at the decoder all is fine. 
> In the rare case
> > 
> > where none do, the user will see some ugly video output for 
> a relatively
> > small amount of time, until it receives a full intra, but 
> it will not
> > otherwise affect the call.
> > There may be issues here we have not thought of, though.
> > 
> > - H.323 EPs do not support these new RTCP packets. We think 
> this is more of
> > an issue. As Roni pointed out, a SIP/H.323 signaling GW 
> would not be able to
> > 
> > gather the FIR requests from the SIP side and pass it on to 
> the H.323 side,
> > unless it is also acts as GW for the RTP/RTCP traffic. The 
> latter is of
> > course not ideal, but could do as a temporary solution. One 
> would probably
> > need to add a new option flag to H.323 call setup messages 
> telling whether
> > the endpoint supports FIR/freeze in RTCP.
> > 
> > 2. Using a media attribute in SDP for signaling a FIR is 
> wrong in our
> > opinion. SDPs are for telling what kind of streams you want 
> from the time
> > you
> > send it until the next time you send an SDP.  A full intra 
> is a request that
> > 
> > is executed only once when received.
> > 
> > We believe the following can be used as a "litmus test" for 
> determining what
> > 
> > information is OK to send in SDP and what is not:
> > 
> > If an endpoint sends the exact same SDP to another endpoint 
> several times in
> > 
> > sequence, only the first SDP arriving at remote should trigger any
> > change/sideeffects.
> > 
> > This holds true in for example hold/resume but not for full 
> intra req.
> > 
> > 3. This is in our opinion not the ideal solution from a 
> design POV, but it
> > will interoperate better with existing H.323 EPs when 
> SIP/H323 GWs are
> > implemented. It would require a new protocol to be 
> defined., but could be a
> > very simple and limited protocol though, as it would just 
> be a temporary
> > solution.
> > We would possibly need a new such protocol when SDPng 
> arrives, since we have
> > 
> > to refer to a SDPng media channel in a different manner 
> than refering to an
> > SDP channel.
> > 
> > To conclude, we support solutions 1 and 3, while 2 is 
> definitely the worst
> > alternative. While using RTCP (or similar protocol directly between
> > encoder/decoder) is in our opinion the cleanest solution, 3 
> might be used if
> > 
> > the SIP/H.323 switching problem is deemed important enough 
> and no other
> > problems with using RTCP are found.
> > 
> > Nils Henrik Lorentzen
> > 
> > Software Developer
> > TANDBERG
> > http://www.tandberg.net
> > 
> > _______________________________________________
> > 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 daemon@optimus.ietf.org  Wed Aug  7 02:23:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02689
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 02:23:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA20796
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 02:24:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20505;
	Wed, 7 Aug 2002 02:20:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20482
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 02:20:29 -0400 (EDT)
Received: from accord-ntsrv3.accord.co.il ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27226
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 02:19:14 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <QLHNRSGB>; Wed, 7 Aug 2002 09:19:50 +0300
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136A96@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "Even, Roni"
	 <roni.even@polycom.co.il>
Cc: Orit Levin <orit@radvision.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Wed, 7 Aug 2002 09:19:49 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Joerg and Collin
Thanks for your help, I will advance the work on the video resolution in the
next draft.
As for freeze I had some discussions in Polycom and we think that we can
leave without having a freeze request. We need a solution for fast update
picture and I will be working with Orit on it.
Roni

> -----Original Message-----
> From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
> Sent: Tuesday, August 06, 2002 3:28 PM
> To: Even, Roni
> Cc: Orit Levin; mmusic@ietf.org
> Subject: Re: [MMUSIC] video media control draft
> 
> 
> Roni,
> 
> thanks for the reply.  Comments inline.
> 
> > The freeze tells the decoder to continue to decode but to 
> not present until
> > the freeze is released. The release is caused by asking 
> from the encoder a
> > new full frame, so maybe this is the state change since it 
> releases the
> > decoder from the released state.
> > The reasons for the freeze.
> > 1. A mixer can just switch the video without handling of 
> the RTP format, so
> > the mixer is not looking for the new picture in the RTP 
> payload and may
> > start sending from the new source before the full picture. 
> This will cause
> > the decoder to use delta pictures on a previous source information.
> 
> You should have other information at hand: the SSRC (in case of a
> translator)
> or the CSRC (in case of a mixer) will be different.
> 
> > 2. A mixer that looks at the information and start to send 
> the new source
> > information only after detecting a full picture may still 
> want to use freeze
> > in order to let the decoder know that a source switch has 
> occurred, this is
> > important if the mixer do not change the RTP sequence 
> numbers in order to
> > keep the sequence numbers from the source. The decoder may 
> think that he
> > lost packets due to jump in sequence number if he does not 
> know that a
> > switch has occurred.
> 
> Again, shouldn't a source change result in a different SSRC/CSRC?
> 
> > 3. This is a more advanced one. If we are doing continuous 
> presence based on
> > taking 4 QCIF images from different source and building a 
> composite CIF
> > picture, using freeze gives us an option to let the decoder 
> start decoding
> > after all 4 pictures are available when building the 
> initial picture, the
> > decoder will get the other full pictures and since he 
> continues to decode
> > then when the last full QCIF is available, the mixer will 
> release the freeze
> > and the display will be OK. The same goes for changing one 
> of the QCIF
> > sources during the conference.
> 
> Ok.  That's a good one.  Thanks for elaborating on this.
> 
> > As for your design comment, I do not think that we have a 
> design problem in
> > H.323. In H.320 the signalling and media are synchronized 
> like in IP. They
> 
> Still, I don't think they are in IP as they take different paths with
> unknown
> latency properties.
> 
> > run in the same pipe but may have different latencies due 
> to fixed channels
> > BW, furthermore the fast update and streams are in reverse 
> directions. Also
> > for fast update the issue is not to have it synchronized 
> with the switch on
> > the mixer but to have it delivered to the encoder so it 
> will happen sometime
> > after the switch and free the receiver from the freeze 
> state so it will
> > start presenting.
> > 
> > As for reliability we are OK with H.245 reliability and I 
> assume will try to
> > use TCP for videoconferencing due to all reasons mentioned 
> in the SIP
> > session.
> > 
> > AS for no go in SDP, I do not understand how you reached a 
> consensus, I
> > think that we are still arguing the issue and will keep our 
> draft alive.
> 
> SDP does not make sense for the FIR command.  I think enough 
> people have
> argued this and I would like to close this part of the debate 
> and focus
> on alternatives.
> 
> The rest of the SDP extensions you are proposing (picture 
> size, etc.) are
> fine.  We surely had consensus on this.
> 
> > Again, I can give you a rough consensus from the video 
> conferencing people
> > that RTCP is not a solution for us and since the 
> requirement is coming from
> > people that are doing video conferencing and have the 
> knowledge you cannot
> > come and say that you should have the solution on RTCP even 
> if it does not
> > work. I think that the AVT guys did not agree on a must 
> anyhow since RTCP is
> > for indication and not for commands.
> 
> I believe have seen statements from videoconferencing folks that did
> not favor the SDP approach.  We are just trying to find a solution
> that fits the spirit of the protocols we are using.
> 
> > As for SIP, are you stirring us to a INFO based solution , 
> I am not aware of
> > other existing solution
> 
> I hope that I did not convey this impression.  I would like 
> to keep you
> away
> from INFO as far as possible.  In my opinion, INFO should be 
> treated as if
> it
> were non-existent.
> 
> Joerg
> 

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



From daemon@optimus.ietf.org  Wed Aug  7 02:24:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04442
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 02:24:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA20848
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 02:26:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20604;
	Wed, 7 Aug 2002 02:21:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA20569
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 02:21:48 -0400 (EDT)
Received: from accord-ntsrv3.accord.co.il ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28913
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 02:20:33 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <QLHNRSGD>; Wed, 7 Aug 2002 09:21:09 +0300
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136A97@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org,
        "Even, Roni" <roni.even@polycom.co.il>
Subject: RE: [MMUSIC] video media control draft
Date: Wed, 7 Aug 2002 09:21:08 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Nils,
I think your suggestion makes sense. I will update the draft
Roni

> -----Original Message-----
> From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> Sent: Tuesday, August 06, 2002 10:35 AM
> To: mmusic@ietf.org; Even, Roni
> Subject: Re: [MMUSIC] video media control draft
> 
> 
> On Tuesday 06 August 2002 07:59, Even, Roni wrote:
> 
> > Hi Petri,
> > In my draft draft-even-mmusic-video-media-control-00.txt, I have a
> > video-resolution attribute that allow to specify the 
> maximum frame rate
> > supported per resolution.
> 
> A difference between your draft and 
> draft-koskelainen-sdp263-02.txt is that 
> in the latter you may specify resolutions and options per 
> payload type, 
> instead of per media line. I think this is more flexible, and 
> would suit our 
> needs better. Any particular reason for having it per media-line ?
> 
> In your draft it would be a simple change to make it per payload:
> a=video-resolution:<size>
> to
> a=video-resolution: <payload no> <size>
> or possibly
> a=video-resolution: [ PT=<payload no>] <size>
> ie payload no is optional, so if not specified the 
> resolutions would apply to 
> all the payload types on the media line.
> 
> > In the meeting this attribute was accepted for
> > SDP. I could not find the draft mentioned 
> "draft-koskelainen-sdp263-02.txt"
> 
> It expired quite some time ago, but can be found at:
> http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai
> nen-sdp263-02.txt
> 
> Nils Henrik Lorentzen
> 

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



From daemon@optimus.ietf.org  Wed Aug  7 03:40:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08784
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 03:40:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA24685
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 03:42:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24542;
	Wed, 7 Aug 2002 03:36:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24514
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 03:36:58 -0400 (EDT)
Received: from prix.tandberg.no (prix.tandberg.no [193.212.161.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08698
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 03:35:42 -0400 (EDT)
Received: from there ([10.0.2.14])
	by prix.tandberg.no (8.11.6/8.11.6) with SMTP id g777aPu27650
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 09:36:25 +0200
Message-Id: <200208070736.g777aPu27650@prix.tandberg.no>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Nils Henrik Lorentzen <nhl@tandberg.no>
Organization: TANDBERG ASA
To: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft
Date: Wed, 7 Aug 2002 09:36:05 +0200
X-Mailer: KMail [version 1.3.1]
References: <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3> <3D4FC0B5.25445F81@tzi.uni-bremen.de>
In-Reply-To: <3D4FC0B5.25445F81@tzi.uni-bremen.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.14 (www dot roaringpenguin dot com slash mimedefang)
Content-Transfer-Encoding: 8bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 8bit


Hi Joerg

> > As for SIP, are you stirring us to a INFO based solution , I am not aware
> > of other existing solution
>
> I hope that I did not convey this impression.  I would like to keep you
> away
> from INFO as far as possible.  In my opinion, INFO should be treated as if
> it
> were non-existent.

Out of curiosity, what do you think is wrong with INFO ? Is it too much of a 
generic "contain anything that does not fit elsewhere" message ? 

Nils Henrik Lorentzen

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



From daemon@optimus.ietf.org  Wed Aug  7 16:58:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08626
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 16:58:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA07601
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 16:59:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06822;
	Wed, 7 Aug 2002 16:54:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA06791
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 16:54:18 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08264
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 16:53:03 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g77Krkr23960
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 16:53:46 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <QDHJZXJM>; Wed, 7 Aug 2002 16:53:46 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A782@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Date: Wed, 7 Aug 2002 16:53:45 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C23E54.83CED360"
Subject: [MMUSIC] Apparent Contradiction In Offer-Answer
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

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

------_=_NextPart_001_01C23E54.83CED360
Content-Type: text/plain;
	charset="iso-8859-1"

I found these two passages next to each other in section 6.1 of RFC 3264.
If I strain I can make a case that they do not contradict each other, but I
suspect the second was actually meant to replace the first.


   ... The media formats in the "m=" line MUST be listed in order of
   preference, with the first format listed being preferred.  In this case,
   preferred means that the offerer SHOULD use the format with the
   highest preference from the answer.

   Although the answerer MAY list the formats in their desired order of
   preference, it is RECOMMENDED that unless there is a specific reason,
   the answerer list formats in the same relative order they were
   present in the offer.


Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

------_=_NextPart_001_01C23E54.83CED360
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 =
5.5.2655.35">
<TITLE>Apparent Contradiction In Offer-Answer</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I found these two passages next to each other in =
section 6.1 of RFC 3264.&nbsp; If I strain I can make a case that they =
do not contradict each other, but I suspect the second was actually =
meant to replace the first.</FONT></P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp; ... The media formats in the =
&quot;m=3D&quot; line MUST be listed in order of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; preference, with the first format =
listed being preferred.&nbsp; In this case,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; preferred means that the offerer SHOULD =
use the format with the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; highest preference from the =
answer.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Although the answerer MAY list the =
formats in their desired order of</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; preference, it is RECOMMENDED that =
unless there is a specific reason,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; the answerer list formats in the same =
relative order they were</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; present in the offer.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Tom Taylor</FONT>
<BR><FONT SIZE=3D2>taylor@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>Ph. +1 613 736 0961 (ESN 396 1490)</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C23E54.83CED360--

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



From daemon@optimus.ietf.org  Wed Aug  7 21:04:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15526
	for <mmusic-archive@odin.ietf.org>; Wed, 7 Aug 2002 21:04:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA18593
	for mmusic-archive@odin.ietf.org; Wed, 7 Aug 2002 21:05:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA18467;
	Wed, 7 Aug 2002 21:03:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA18438
	for <mmusic@optimus.ietf.org>; Wed, 7 Aug 2002 21:03:16 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15459
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 21:02:02 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g7812dR09655
	for <mmusic@ietf.org>; Wed, 7 Aug 2002 21:02:39 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <QDHJZYYZ>; Wed, 7 Aug 2002 21:02:40 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A786@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Date: Wed, 7 Aug 2002 21:02:38 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [MMUSIC] Another Inconsistency In Offer-Answer
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

In section 8.3.1, talking about changes of port, the first paragraph ends
with this text:

   The offerer SHOULD NOT cease listening for media on the old
   port until the answer is received and media arrives on the new port.
   Doing so could result in loss of media during the transition.

Two paragraphs later we have:

   ... The
   same is true for an offerer that sends an updated offer with a new
   port; it MUST NOT cease listening for media on the old port until
   media arrives on the new port.

Which strength did we choose in the end?

Sorry about spotting these only now: I'm a bit behind at preparing a
compliancy matrix.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From daemon@optimus.ietf.org  Thu Aug  8 13:27:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20414
	for <mmusic-archive@odin.ietf.org>; Thu, 8 Aug 2002 13:27:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA18397
	for mmusic-archive@odin.ietf.org; Thu, 8 Aug 2002 13:29:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18224;
	Thu, 8 Aug 2002 13:23:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA20716
	for <mmusic@optimus.ietf.org>; Tue, 6 Aug 2002 23:19:03 -0400 (EDT)
Received: from host.serversanddomains.com (host.serversanddomains.com [209.239.59.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09767;
	Tue, 6 Aug 2002 23:17:48 -0400 (EDT)
Received: from victorpc ([206.184.140.168])
	by host.serversanddomains.com (8.10.2/8.10.2) with SMTP id g773Ix809832;
	Tue, 6 Aug 2002 23:18:59 -0400
From: "Victor Paulsamy" <victor@zapex.com>
To: "Kathy Kwan" <kathyk@interval.com>, <sip@ietf.org>, <mmusic@ietf.org>
Date: Tue, 6 Aug 2002 20:14:39 -0700
Message-ID: <NEBBIPNANPGLCDPGFJGPCEIKCFAA.victor@zapex.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C23D85.E4E34700"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <50750ECDD09ED411AF9A00508B6A823B7E4391@harp.interval.com>
Subject: [MMUSIC] RE: [Sip] Port changeability in response to Invite -- expected behavior?
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

This is a multi-part message in MIME format.

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

Cathy: Comments inline ...

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Kathy Kwan
Sent: Friday, August 02, 2002 4:21 PM
To: 'sip@ietf.org'; 'mmusic@ietf.org'
Cc: Kathy Kwan
Subject: [Sip] Port changeability in response to Invite -- expected
behavior?


  To the SIP/MMUSIC community,



  I was looking at the method proposed by Rosenberg and Schulzrinne in the
IETF Internet Draft entitled "Models for Multiparty Conferencing in SIP"
(dated July 2002, expires Jan 2003), Section 7, entitled "Centralized
Signaling, Distributed Media".    This method describes the conferencing
case where a server controls the SIP connections with all participants, and
uses third party call control to enable media connections to go directly
between the participants.   Hence, the signaling is centralized, but media
is distributed.  In order for the method to work, an inherent assumption is
made that the original ports do not change in the response to an Invite.
Two examples of this assumption are shown in the call flow diagram of
"Centralized Signaling, Distributed Media" Figure 7:



  (1)      If a participant is taken off hold, the participant cannot change
its ports in its response.



  In Figure 7, participant  D is taken off hold in the very last Invite
transaction between D and the server.   It is assumed that D does not change
its ports D1,D2, and D3 in its Invite 200 OK response.



  (Perhaps there is a way to interleave invites using provisional responses
that could fix this particular case, but if that exists, the response could
be delayed by as long as it takes to receive the responses from all other
participants in the conference.)



  (2)      If a participant receives a re-Invite for any reason, the
participant must maintain its original offered ports in the response.



  In Figure 7, parties A, B and C are assumed to not change their original
ports when they receive a re-Invite from the server asking for an additional
port for D.   According to Figure 7, A, B, and C are not put on hold when D
arrives, so this case is distinct from (1) above.



  My questions are:



  (3)      What assumptions can be made about the ports being able to change
in the response to an Invite?    Is there documentation of this in any RFCs?



  Perhaps a media attribute could be used to request that the ports don't
change if it is not already implied in either of the cases above?



  All aspects of a session can be changed as a result of a reINVITE. In this
example that you refere to, the address/port MUST NOT change.



  (4)      There are two ways to convey hold described below.   Is the
expectation for port behavior the same for both cases of hold?



  The original way to convey hold is to set the IP address to 0.0.0.0.  This
case does not require RTCP to be sent during the hold period.   A new method
to convey hold is to use the media attributes "a=inactive", "a=sendonly" or
"a=recvonly", depending on the direction of the hold.  Because of the
different implications for the hold methods, particularly for RTCP, I am
asking this question with both methods in mind.



      The first one is (0.0.0.0) used by old UAs and using media attributes
to convey hold status is used by new UAs (perhaps bis05 onwards). However,
they do not imply anything with regards to the port that can otherwise be
changed using a reINVITE



  Regards,



  --victor



  Thank you in advance for your comments.



  Regards,

  Kathy Kwan

  Interval Media




------=_NextPart_000_0008_01C23D85.E4E34700
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C23A41.01D58190" =
rel=3DFile-List><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1580947881;
	mso-list-type:hybrid;
	mso-list-template-ids:1182555644 1698734832 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"\(%1\)";
	mso-level-tab-stop:40.5pt;
	mso-level-number-position:left;
	margin-left:40.5pt;
	text-indent:-22.5pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D871040403-07082002><FONT face=3DTahoma =
size=3D2>Cathy: Comments=20
inline ...</FONT></SPAN></DIV>
<DIV><SPAN class=3D871040403-07082002><FONT face=3DTahoma=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D871040403-07082002></SPAN><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> sip-admin@ietf.org=20
[mailto:sip-admin@ietf.org]<B>On Behalf Of </B>Kathy =
Kwan<BR><B>Sent:</B>=20
Friday, August 02, 2002 4:21 PM<BR><B>To:</B> 'sip@ietf.org';=20
'mmusic@ietf.org'<BR><B>Cc:</B> Kathy Kwan<BR><B>Subject:</B> [Sip] Port =

changeability in response to Invite -- expected =
behavior?<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">To the SIP/MMUSIC=20
  community,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">I was looking at the method proposed by =
Rosenberg and=20
  <SPAN class=3DSpellE>Schulzrinne</SPAN> in the IETF Internet Draft =
entitled=20
  "Models for Multiparty Conferencing in SIP" (dated July 2002, expires =
Jan=20
  2003), Section 7, entitled "Centralized Signaling, Distributed =
Media".<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>This method =
describes the=20
  conferencing case where a server controls the SIP connections with all =

  participants, and uses third party call control to enable media =
connections to=20
  go directly between the participants.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>Hence, the signaling =
is=20
  centralized, but media is distributed.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>In order for the method to work, an inherent assumption is made =
that=20
  the original ports do not change in the response to an Invite.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>Two examples of this =
assumption are=20
  shown in the call flow diagram of "Centralized Signaling, Distributed =
Media"=20
  Figure 7:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 40.5pt; TEXT-INDENT: -22.5pt; mso-list: l0 =
level1 lfo1; tab-stops: list 40.5pt"><![if !supportLists]><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><SPAN=20
  style=3D"mso-list: Ignore">(1)<FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN></SPAN></FONT><![endif]>If a participant is taken =
off=20
  hold, the participant cannot change its ports in its =
response.<o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt">In Figure 7, <SPAN=20
  class=3DGramE>participant <SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN>D</SPAN>=20
  is taken off hold in the very last Invite transaction between D and =
the=20
  server.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN><I=20
  style=3D"mso-bidi-font-style: normal"><SPAN=20
  style=3D"FONT-STYLE: italic; mso-bidi-font-style: normal">It is =
assumed that D=20
  does not change its ports D1<SPAN class=3DGramE>,D2</SPAN>, and D3 in =
its Invite=20
  200 OK response.</SPAN></I><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
  </SPAN><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt">(Perhaps there is a way to =
interleave=20
  invites using provisional responses that could fix this particular =
case, but=20
  if that exists, the response could be delayed by as long as it takes =
to=20
  receive the responses from all other participants in the=20
  conference.)<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 40.5pt; TEXT-INDENT: -22.5pt; mso-list: l0 =
level1 lfo1; tab-stops: list 40.5pt"><![if !supportLists]><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><SPAN=20
  style=3D"mso-list: Ignore">(2)<FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN></SPAN></FONT><![endif]>If a participant receives =
a=20
  re-Invite for any reason, the participant must maintain its original =
offered=20
  ports in the response.<o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt">In Figure 7, parties A, B and =
C are=20
  assumed to not change their original ports when they receive a =
re-Invite from=20
  the server asking for an additional port for D.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>According to Figure 7, =
A, B, and=20
  C are not put on hold when D arrives, so this case is distinct from =
(1)=20
  above.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">My questions =
are:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 40.5pt; TEXT-INDENT: -22.5pt; mso-list: l0 =
level1 lfo1; tab-stops: list 40.5pt"><![if !supportLists]><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><SPAN=20
  style=3D"mso-list: Ignore">(3)<FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN></SPAN></FONT><![endif]>What assumptions can be =
made=20
  about the ports being able to change in the response to an Invite? =
<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;</SPAN>Is there =
documentation of=20
  this in any <SPAN class=3DSpellE>RFCs</SPAN>?<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><I=20
  style=3D"mso-bidi-font-style: normal"><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; FONT-STYLE: italic; mso-bidi-font-style: =
normal">Perhaps=20
  a media attribute could be used to request that the ports don't change =
if it=20
  is not already implied in either of the cases=20
  above?</SPAN></FONT></I><o:p></o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in"><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><SPAN style=3D"FONT-SIZE: =
12pt"><o:p></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt"><o:p><SPAN =
class=3D871040403-07082002><FONT=20
  face=3DArial color=3D#0000ff size=3D2>All aspects of a session can be =
changed as a=20
  result of a reINVITE. In this example that you refere to,=20
  the&nbsp;address/port&nbsp;MUST=20
  NOT&nbsp;change.</FONT></SPAN></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in"><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><SPAN style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002></SPAN></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN-LEFT: 40.5pt; TEXT-INDENT: -22.5pt; mso-list: l0 =
level1 lfo1; tab-stops: list 40.5pt"><![if !supportLists]><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt"><SPAN=20
  style=3D"mso-list: Ignore">(4)<FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
  style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT></SPAN></SPAN></FONT><![endif]>There are two ways to =
convey hold=20
  described below.<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>Is the=20
  expectation for port behavior the same for both cases of =
hold?<o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 40.5pt"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN style=3D"FONT-SIZE: 12pt">The original way to convey =
hold is to set=20
  the IP address to 0.0.0.0.<SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN>This=20
  case does not require RTCP to be sent during the hold period.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>A new method to convey =
hold is=20
  to use the media attributes "a=3Dinactive", "a=3D<SPAN=20
  class=3DSpellE>sendonly</SPAN>" or "a=3D<SPAN =
class=3DSpellE>recvonly</SPAN>",=20
  depending on the direction of the hold.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
  </SPAN>Because of the different implications for the hold methods,=20
  particularly for RTCP, I am asking this question with both methods in=20
  mind.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN =
class=3D871040403-07082002>&nbsp;&nbsp;&nbsp;=20
  <FONT size=3D2>The first one is (0.0.0.0) used by old UAs and using =
media=20
  attributes to convey hold status is used by&nbsp;new UAs (perhaps =
bis05=20
  onwards). However, they do not imply anything with regards to the port =
that=20
  can otherwise be changed using a=20
reINVITE</FONT></SPAN></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002></SPAN></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002>Regards,</SPAN></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002></SPAN></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002>--victor</SPAN></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =

  style=3D"FONT-SIZE: 12pt"><o:p><SPAN=20
  class=3D871040403-07082002></SPAN></o:p></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">Thank you in advance for your=20
  comments.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">Regards,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><st1:PersonName><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">Kathy=20
  Kwan</SPAN></FONT></st1:PersonName><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">Interval Media<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------=_NextPart_000_0008_01C23D85.E4E34700--



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



From daemon@optimus.ietf.org  Fri Aug  9 12:29:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02425
	for <mmusic-archive@odin.ietf.org>; Fri, 9 Aug 2002 12:29:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA06714
	for mmusic-archive@odin.ietf.org; Fri, 9 Aug 2002 12:30:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06296;
	Fri, 9 Aug 2002 12:29:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06249
	for <mmusic@optimus.ietf.org>; Fri, 9 Aug 2002 12:29:08 -0400 (EDT)
Received: from flyingfox.snowshore.com (flyingfox.snowshore.com [216.57.133.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02377
	for <mmusic@ietf.org>; Fri, 9 Aug 2002 12:27:52 -0400 (EDT)
Received: from eburger (keeper.snowshore.com [216.57.133.4])
	by flyingfox.snowshore.com (8.11.2/8.11.2) with SMTP id g79GT5M21741;
	Fri, 9 Aug 2002 12:29:06 -0400 (EDT)
Reply-To: <eburger@snowshore.com>
From: "Eric Burger" <eburger@snowshore.com>
To: "Even, Roni" <roni.even@polycom.co.il>
Cc: <mmusic@ietf.org>
Subject: RE: [MMUSIC] video media control draft
Date: Fri, 9 Aug 2002 12:29:05 -0400
Message-ID: <BEEMKJGAMKLMAIKEECBAGENBCLAA.eburger@snowshore.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3>
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

I am at a bit of a loss here.

With a partner, we do a H.323 <-> SIP gateway for voice.  One thing we have
to do is take things in the H.323 signaling realm (like H.245 tones) and put
them into the RTP realm (like RFC2833 tones).

For some things, H.323 and SIP have fundamentally different architectures.
I would propose that trying to force H.323 into SIP or SIP into H.323 is not
a useful exercise.  For example, if you have things like full-frame refresh
in the signaling channel on the H.323 side, you can easily insert a media
server in the media stream to insert the appropriate RTCP packet on the SIP
side, and vice-versa.

-----Original Message-----
From: mmusic-admin@ietf.org [mailto:mmusic-admin@ietf.org]On Behalf Of
Even, Roni
Sent: Tuesday, July 23, 2002 8:33 AM
To: 'Joerg Ott'; Orit Levin
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft

[snip]

As for your design comment, I do not think that we have a design problem in
H.323. In H.320 the signalling and media are synchronized like in IP. They
run in the same pipe but may have different latencies due to fixed channels
BW, furthermore the fast update and streams are in reverse directions. Also
for fast update the issue is not to have it synchronized with the switch on
the mixer but to have it delivered to the encoder so it will happen sometime
after the switch and free the receiver from the freeze state so it will
start presenting.

As for reliability we are OK with H.245 reliability and I assume will try to
use TCP for videoconferencing due to all reasons mentioned in the SIP
session.
[snip]


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



From daemon@optimus.ietf.org  Mon Aug 12 03:32:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12194
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 03:32:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA22524
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 03:34:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21899;
	Mon, 12 Aug 2002 03:30:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21859
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 03:30:02 -0400 (EDT)
Received: from mail.redlinecommunications.ro (root@gate.redlinecommunications.ro [213.154.146.122])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12143
	for <mmusic@ietf.org>; Mon, 12 Aug 2002 03:28:42 -0400 (EDT)
From: danutf@redlinecommunications.ro
Received: from localhost (danutf@localhost)
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with ESMTP id g7C7S4t01440;
	Mon, 12 Aug 2002 10:28:08 +0300
X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: mail.redlinecommunications.ro
X-Authentication-Warning: mail.redlinecommunications.ro: danutf owned process doing -bs
Date: Mon, 12 Aug 2002 10:28:04 +0300 (EEST)
To: Bryan Thale <bryan.thale@motorola.com>
cc: Colin Perkins <csp@isi.edu>, <mmusic@ietf.org>
Subject: Re: [MMUSIC] Re: Tool starting mode attributes in SDP
In-Reply-To: <3D41ADEF.5332BAF4@motorola.com>
Message-ID: <Pine.LNX.4.33.0208120954210.1191-100000@mail.redlinecommunications.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Hello,

Sorry for the delay.
When I've posted the mail about the four complementary attributes
I was thinking only of changing the text protocol(something like:
'Only one of these attibutes MAY appear at session level and at each
media level').

I think that changing the ABNF syntax may be postponed to the next version
of the SDP protocol (v=3).

Dan Firac,
Software Engineer,
Redline Communications, Romania.

On Fri, 26 Jul 2002, Bryan Thale wrote:

> Right.  To do it properly you need something like
>
> "a=toolmode:" ("recvonly" / "sendonly" / "sendrecv") [ 1*SP "inactive" ] CRLF
>
> to group the values of the toolmode attribute together but such a change is not
> backward compatible with current implementations.  You could get most of the
> benefits of such a change with a combination of a change to the ABNF and a
> change to the text describing the recvonly, sendonly, sendrecv, and inactive
> attributes.
>
>
>   1. Change the ABNF to allow only one of recvonly, sendonly, and sendrecv to
>      appear in a session or media description and to allow inactive to appear
>      only in combination with one of those three.
>   2. Change the text to state that the appearance of any of the three at the
>      media level overrides any setting at the session level.
>
> Bryan.
>
> --
> Bryan Thale
> Networks & Infrastructure Research, Motorola Labs
> mailto:bryan.thale@motorola.com
>
> Colin Perkins wrote:
>
> > Right, the problem is the override between session and media level. I don't
> > think we can express that in the ABNF.
> >
> > Colin
> >
>
>
>
> _______________________________________________
> 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 daemon@optimus.ietf.org  Mon Aug 12 05:01:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13463
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 05:01:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA26150
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 05:01:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25494;
	Mon, 12 Aug 2002 04:54:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25463
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 04:53:59 -0400 (EDT)
Received: from mail.redlinecommunications.ro (root@gate.redlinecommunications.ro [213.154.146.122])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13307
	for <mmusic@ietf.org>; Mon, 12 Aug 2002 04:52:30 -0400 (EDT)
From: danutf@redlinecommunications.ro
Received: from localhost (danutf@localhost)
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with ESMTP id g7C8q2R02713;
	Mon, 12 Aug 2002 11:52:05 +0300
X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: mail.redlinecommunications.ro
X-Authentication-Warning: mail.redlinecommunications.ro: danutf owned process doing -bs
Date: Mon, 12 Aug 2002 11:52:01 +0300 (EEST)
To: Bryan Thale <bryan.thale@motorola.com>
cc: Colin Perkins <csp@isi.edu>, <mmusic@ietf.org>
In-Reply-To: <Pine.LNX.4.33.0208120954210.1191-100000@mail.redlinecommunications.ro>
Message-ID: <Pine.LNX.4.33.0208121149550.2670-100000@mail.redlinecommunications.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [MMUSIC] erata
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org


See below,

On Mon, 12 Aug 2002 danutf@redlinecommunications.ro wrote:

> Hello,
>
> Sorry for the delay.
> When I've posted the mail about the four complementary attributes
> I was thinking only of changing the text protocol(something like:
> 'Only one of these attibutes MAY appear at session level and at each
> media level').
>
> I think that changing the ABNF syntax may be postponed to the next version
> of the SDP protocol (v=3).
Oops,  I meant v=1.

>
> Dan Firac,
> Software Engineer,
> Redline Communications, Romania.
>
> On Fri, 26 Jul 2002, Bryan Thale wrote:
>
> > Right.  To do it properly you need something like
> >
> > "a=toolmode:" ("recvonly" / "sendonly" / "sendrecv") [ 1*SP "inactive" ] CRLF
> >
> > to group the values of the toolmode attribute together but such a change is not
> > backward compatible with current implementations.  You could get most of the
> > benefits of such a change with a combination of a change to the ABNF and a
> > change to the text describing the recvonly, sendonly, sendrecv, and inactive
> > attributes.
> >
> >
> >   1. Change the ABNF to allow only one of recvonly, sendonly, and sendrecv to
> >      appear in a session or media description and to allow inactive to appear
> >      only in combination with one of those three.
> >   2. Change the text to state that the appearance of any of the three at the
> >      media level overrides any setting at the session level.
> >
> > Bryan.
> >
> > --
> > Bryan Thale
> > Networks & Infrastructure Research, Motorola Labs
> > mailto:bryan.thale@motorola.com
> >
> > Colin Perkins wrote:
> >
> > > Right, the problem is the override between session and media level. I don't
> > > think we can express that in the ABNF.
> > >
> > > Colin
> > >
> >
> >
> >
> > _______________________________________________
> > 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 daemon@optimus.ietf.org  Mon Aug 12 07:29:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16787
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 07:29:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA04338
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 07:30:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03928;
	Mon, 12 Aug 2002 07:25:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03898
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 07:25:25 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16681;
	Mon, 12 Aug 2002 07:24:06 -0400 (EDT)
Message-Id: <200208121124.HAA16681@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mmusic@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 12 Aug 2002 07:24:06 -0400
Subject: [MMUSIC] I-D ACTION:draft-koskelainen-mmusic-floor-req-00.txt
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

--NextPart

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


	Title		: Requirements for Floor Control
	Author(s)	: P. Koskelainen, H. Schulzrinne
	Filename	: draft-koskelainen-mmusic-floor-req-00.txt
	Pages		: 7
	Date		: 09-Aug-02
	
This document defines the requirements for floor control.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-koskelainen-mmusic-floor-req-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-koskelainen-mmusic-floor-req-00.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-koskelainen-mmusic-floor-req-00.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Mon Aug 12 17:17:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11786
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 17:17:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA11182
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 17:19:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA11106;
	Mon, 12 Aug 2002 17:15:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00537
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 14:29:06 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04705
	for <mmusic@ietf.org>; Mon, 12 Aug 2002 14:27:48 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate2.mot.com (motgate2 2.1) with ESMTP id LAA28832; Mon, 12 Aug 2002 11:29:04 -0700 (MST)]
Received: [from artibeus.nsr.labs.mot.com (artibeus.nsr.labs.mot.com [173.23.95.73]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id LAA16894; Mon, 12 Aug 2002 11:27:10 -0700 (MST)]
Received: from motorola.com (localhost [127.0.0.1])
	by artibeus.nsr.labs.mot.com (8.11.6/8.11.6) with ESMTP id g7CIZUt07688;
	Mon, 12 Aug 2002 13:35:30 -0500
Message-ID: <3D57FFF2.6768B34E@motorola.com>
Date: Mon, 12 Aug 2002 13:35:30 -0500
From: Bryan Thale <bryan.thale@motorola.com>
Organization: Networks & Infrastructure Research, Motorola Labs
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: danutf@redlinecommunications.ro
CC: mmusic@ietf.org
References: <Pine.LNX.4.33.0208121149550.2670-100000@mail.redlinecommunications.ro>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: erata
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

> > When I've posted the mail about the four complementary attributes
> > I was thinking only of changing the text protocol(something like:
> > 'Only one of these attibutes MAY appear at session level and at each
> > media level').

Well, you really need to say more than that to adequately clear up that part of the
spec.  For example, what does it mean if the session is set to sendonly and the media
to recvonly?  Each section contains only a single directive, but there is nothing to
explain the relationship between them.  The current mechanism in the spec says the two
attributes are unrelated since they have different attribute names.


> > I think that changing the ABNF syntax may be postponed to the next version
> > of the SDP protocol (v=3).
> Oops,  I meant v=1.

Unlikely since I think XML-based SDPng is meant to replace the current v=0 version of
SDP.

Bryan.

--
Bryan Thale
Networks & Infrastructure Research, Motorola Labs
mailto:bryan.thale@motorola.com





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



From daemon@optimus.ietf.org  Mon Aug 12 19:59:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15136
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 19:59:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA18683
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 20:01:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA18029;
	Mon, 12 Aug 2002 19:56:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA17998
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 19:56:14 -0400 (EDT)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15042
	for <mmusic@ietf.org>; Mon, 12 Aug 2002 19:54:57 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g7CNtoc18089;
	Mon, 12 Aug 2002 18:55:51 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KKXYRMAX>; Mon, 12 Aug 2002 18:55:36 -0500
Message-ID: <933FADF5E673D411B8A30002A5608A0E03A63444@zrc2c012.us.nortel.com>
From: "Sanjoy Sen" <sanjoy@nortelnetworks.com>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Nils Henrik Lorentzen'"
	 <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Mon, 12 Aug 2002 18:55:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2425B.BB815E30"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

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

------_=_NextPart_001_01C2425B.BB815E30
Content-Type: text/plain

I saw this pretty old thread. I do support proposing frame-size on a per
codec (payload-type) basis. I would also like to throw in the requirement
that we need to be able to specify the preferred media qualities (e.g., in a
scale of 0-10) per payload-type (right now SDP defines a quality attribute
per m line). Thoughts?

Does it make sense to encode all these information as part of an "fmtp"
attribute for the payload-type? - e.g., a:fmtp:<PT> res=QCIF/quality=5

-Sanjoy

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il] 
> Sent: Wednesday, August 07, 2002 1:21 AM
> To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, Roni
> Subject: RE: [MMUSIC] video media control draft
> 
> 
> Nils,
> I think your suggestion makes sense. I will update the draft Roni
> 
> > -----Original Message-----
> > From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> > Sent: Tuesday, August 06, 2002 10:35 AM
> > To: mmusic@ietf.org; Even, Roni
> > Subject: Re: [MMUSIC] video media control draft
> > 
> > 
> > On Tuesday 06 August 2002 07:59, Even, Roni wrote:
> > 
> > > Hi Petri,
> > > In my draft draft-even-mmusic-video-media-control-00.txt, 
> I have a 
> > > video-resolution attribute that allow to specify the
> > maximum frame rate
> > > supported per resolution.
> > 
> > A difference between your draft and
> > draft-koskelainen-sdp263-02.txt is that 
> > in the latter you may specify resolutions and options per 
> > payload type, 
> > instead of per media line. I think this is more flexible, and 
> > would suit our 
> > needs better. Any particular reason for having it per media-line ?
> > 
> > In your draft it would be a simple change to make it per payload: 
> > a=video-resolution:<size> to
> > a=video-resolution: <payload no> <size>
> > or possibly
> > a=video-resolution: [ PT=<payload no>] <size>
> > ie payload no is optional, so if not specified the 
> > resolutions would apply to 
> > all the payload types on the media line.
> > 
> > > In the meeting this attribute was accepted for
> > > SDP. I could not find the draft mentioned
> > "draft-koskelainen-sdp263-02.txt"
> > 
> > It expired quite some time ago, but can be found at: 
> > http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai
> > nen-sdp263-02.txt
> > 
> > Nils Henrik Lorentzen
> > 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 

------_=_NextPart_001_01C2425B.BB815E30
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [MMUSIC] video media control draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I saw this pretty old thread. I do support proposing =
frame-size on a per codec (payload-type) basis. I would also like to =
throw in the requirement that we need to be able to specify the =
preferred media qualities (e.g., in a scale of 0-10) per payload-type =
(right now SDP defines a quality attribute per m line). =
Thoughts?</FONT></P>

<P><FONT SIZE=3D2>Does it make sense to encode all these information as =
part of an &quot;fmtp&quot; attribute for the payload-type? - e.g., =
a:fmtp:&lt;PT&gt; res=3DQCIF/quality=3D5</FONT></P>

<P><FONT SIZE=3D2>-Sanjoy</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Even, Roni [<A =
HREF=3D"mailto:roni.even@polycom.co.il">mailto:roni.even@polycom.co.il</=
A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, August 07, 2002 1:21 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; =
Even, Roni</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [MMUSIC] video media control =
draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Nils,</FONT>
<BR><FONT SIZE=3D2>&gt; I think your suggestion makes sense. I will =
update the draft Roni</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Nils Henrik Lorentzen [<A =
HREF=3D"mailto:nhl@tandberg.no">mailto:nhl@tandberg.no</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Tuesday, August 06, 2002 10:35 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: mmusic@ietf.org; Even, Roni</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: Re: [MMUSIC] video media control =
draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; On Tuesday 06 August 2002 07:59, Even, =
Roni wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Hi Petri,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; In my draft =
draft-even-mmusic-video-media-control-00.txt, </FONT>
<BR><FONT SIZE=3D2>&gt; I have a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; video-resolution attribute that allow =
to specify the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; maximum frame rate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; supported per resolution.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A difference between your draft and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; draft-koskelainen-sdp263-02.txt is that =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; in the latter you may specify resolutions =
and options per </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; payload type, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; instead of per media line. I think this is =
more flexible, and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; would suit our </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; needs better. Any particular reason for =
having it per media-line ?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; In your draft it would be a simple change =
to make it per payload: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a=3Dvideo-resolution:&lt;size&gt; =
to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a=3Dvideo-resolution: &lt;payload no&gt; =
&lt;size&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; or possibly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a=3Dvideo-resolution: [ PT=3D&lt;payload =
no&gt;] &lt;size&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ie payload no is optional, so if not =
specified the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; resolutions would apply to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; all the payload types on the media =
line.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; In the meeting this attribute was =
accepted for</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; SDP. I could not find the draft =
mentioned</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&quot;draft-koskelainen-sdp263-02.txt&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; It expired quite some time ago, but can be =
found at: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai" =
TARGET=3D"_blank">http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-=
koskelai</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; nen-sdp263-02.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Nils Henrik Lorentzen</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; mmusic mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/mmusic" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/mmusic</A></FON=
T>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2425B.BB815E30--

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



From daemon@optimus.ietf.org  Mon Aug 12 23:46:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20108
	for <mmusic-archive@odin.ietf.org>; Mon, 12 Aug 2002 23:46:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA29872
	for mmusic-archive@odin.ietf.org; Mon, 12 Aug 2002 23:47:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA29850;
	Mon, 12 Aug 2002 23:46:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA29819
	for <mmusic@optimus.ietf.org>; Mon, 12 Aug 2002 23:46:28 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20095
	for <mmusic@ietf.org>; Mon, 12 Aug 2002 23:45:11 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.55])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g7D3jrYH000173;
	Mon, 12 Aug 2002 23:45:54 -0400 (EDT)
Message-ID: <3D5880F0.4070904@dynamicsoft.com>
Date: Mon, 12 Aug 2002 23:45:52 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Apparent Contradiction In Offer-Answer
References: <4D79C746863DD51197690002A52CDA0001E8A782@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Sorry for the delay. I am only now beginning to recover from a massive 
flood of work at my "real" job:

Tom-PT Taylor wrote:
> I found these two passages next to each other in section 6.1 of RFC
> 3264.  If I strain I can make a case that they do not contradict each
> other, but I suspect the second was actually meant to replace the first.
> 
> 
>    ... The media formats in the "m=" line MUST be listed in order of 
>    preference, with the first format listed being preferred.  In this
> case, 
>    preferred means that the offerer SHOULD use the format with the 
>    highest preference from the answer. 
> 
>    Although the answerer MAY list the formats in their desired order of 
>    preference, it is RECOMMENDED that unless there is a specific reason,
> 
>    the answerer list formats in the same relative order they were 
>    present in the offer. 

These are not inconsistent.

The first paragraph is saying that the offerer SHOULD use the highest 
preference codec listed by the answerer. How does the answerer decide 
what his preferences are? The next paragraph recommends that, unless it 
has a reason otherwise, it ought to use the same preferences expressed 
by the offerer.

So, if the offerer says it does codecs 1,2,3 and 4, in that order, the 
answerer (based on the second paragraph), would list codecs 2 and 4, in 
that order, in its answer (assuming it doesn't support 1 and 3). Then, 
based on the first paragraph, the offerer SHOULD use codec 1.

Both paragraphs combined make symmetric codecs (encode and decode with 
the same codec) SHOULD strength.

-Jonathan R.



-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


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



From daemon@optimus.ietf.org  Tue Aug 13 03:54:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04138
	for <mmusic-archive@odin.ietf.org>; Tue, 13 Aug 2002 03:54:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA20663
	for mmusic-archive@odin.ietf.org; Tue, 13 Aug 2002 03:55:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA20425;
	Tue, 13 Aug 2002 03:47:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA20394
	for <mmusic@optimus.ietf.org>; Tue, 13 Aug 2002 03:47:23 -0400 (EDT)
Received: from vs.informatik.uni-ulm.de (vs.informatik.uni-ulm.de [134.60.77.243])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04030
	for <mmusic@ietf.org>; Tue, 13 Aug 2002 03:46:02 -0400 (EDT)
Received: from lamagra (lamagra.informatik.uni-ulm.de [134.60.77.31])
	by vs.informatik.uni-ulm.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with SMTP id g7D6o2B10138;
	Tue, 13 Aug 2002 08:50:02 +0200
X-Authentication-Warning: vs.informatik.uni-ulm.de: Host lamagra.informatik.uni-ulm.de [134.60.77.31] claimed to be lamagra
Message-ID: <005201c2429d$ecc41f90$1f4d3c86@lamagra>
From: "Andreas Kassler" <kassler@informatik.uni-ulm.de>
To: "Sanjoy Sen" <sanjoy@nortelnetworks.com>,
        "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, <mmusic@ietf.org>
References: <933FADF5E673D411B8A30002A5608A0E03A63444@zrc2c012.us.nortel.com>
Subject: Re: [MMUSIC] video media control draft
Date: Tue, 13 Aug 2002 09:49:16 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_004E_01C242AE.AFFE3350"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_004E_01C242AE.AFFE3350
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_004F_01C242AE.AFFE3350"


------=_NextPart_001_004F_01C242AE.AFFE3350
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RE: [MMUSIC] video media control draftSanjoy et al,
we were also concerned about the expressability of quality attributes =
that
defines the quality of service at application level for a given =
video(audio) stream.=20
In draft-guenkova-mmusic-e2enp-sdpng-00.txt we basically have identified =
a requirement
to ... introduce (per) codec parametrization attributes like frame-rate, =
frame-size, color-
quality-range, overall-quality-range, etc. which should be  uniquely =
interpreted by the end-systems.

When it comes to negotiation of such attributes with the peer for =
setting up quality enhanced
media streams, we propose to specify such parameters on a per codec =
basis. The reason is=20
that not all codecs support all combinations of such parameters. For =
example with a given
hardware, a sender may be able to compress at 25 fps at CIF a H.261 =
stream but may
not be able to compress at 25 fps at CIF a MPEG-4 stream due to limited =
resources.

We propose also to work on these issues within the SDPng context.

-Andreas
  ----- Original Message -----=20
  From: Sanjoy Sen=20
  To: 'Even, Roni' ; 'Nils Henrik Lorentzen' ; mmusic@ietf.org=20
  Sent: Tuesday, August 13, 2002 1:55 AM
  Subject: RE: [MMUSIC] video media control draft


  I saw this pretty old thread. I do support proposing frame-size on a =
per codec (payload-type) basis. I would also like to throw in the =
requirement that we need to be able to specify the preferred media =
qualities (e.g., in a scale of 0-10) per payload-type (right now SDP =
defines a quality attribute per m line). Thoughts?

  Does it make sense to encode all these information as part of an =
"fmtp" attribute for the payload-type? - e.g., a:fmtp:<PT> =
res=3DQCIF/quality=3D5

  -Sanjoy=20

  > -----Original Message-----=20
  > From: Even, Roni [mailto:roni.even@polycom.co.il]=20
  > Sent: Wednesday, August 07, 2002 1:21 AM=20
  > To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, Roni=20
  > Subject: RE: [MMUSIC] video media control draft=20
  >=20
  >=20
  > Nils,=20
  > I think your suggestion makes sense. I will update the draft Roni=20
  >=20
  > > -----Original Message-----=20
  > > From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no]=20
  > > Sent: Tuesday, August 06, 2002 10:35 AM=20
  > > To: mmusic@ietf.org; Even, Roni=20
  > > Subject: Re: [MMUSIC] video media control draft=20
  > >=20
  > >=20
  > > On Tuesday 06 August 2002 07:59, Even, Roni wrote:=20
  > >=20
  > > > Hi Petri,=20
  > > > In my draft draft-even-mmusic-video-media-control-00.txt,=20
  > I have a=20
  > > > video-resolution attribute that allow to specify the=20
  > > maximum frame rate=20
  > > > supported per resolution.=20
  > >=20
  > > A difference between your draft and=20
  > > draft-koskelainen-sdp263-02.txt is that=20
  > > in the latter you may specify resolutions and options per=20
  > > payload type,=20
  > > instead of per media line. I think this is more flexible, and=20
  > > would suit our=20
  > > needs better. Any particular reason for having it per media-line ? =

  > >=20
  > > In your draft it would be a simple change to make it per payload:=20
  > > a=3Dvideo-resolution:<size> to=20
  > > a=3Dvideo-resolution: <payload no> <size>=20
  > > or possibly=20
  > > a=3Dvideo-resolution: [ PT=3D<payload no>] <size>=20
  > > ie payload no is optional, so if not specified the=20
  > > resolutions would apply to=20
  > > all the payload types on the media line.=20
  > >=20
  > > > In the meeting this attribute was accepted for=20
  > > > SDP. I could not find the draft mentioned=20
  > > "draft-koskelainen-sdp263-02.txt"=20
  > >=20
  > > It expired quite some time ago, but can be found at:=20
  > > http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai=20
  > > nen-sdp263-02.txt=20
  > >=20
  > > Nils Henrik Lorentzen=20
  > >=20
  >=20
  > _______________________________________________=20
  > mmusic mailing list=20
  > mmusic@ietf.org=20
  > https://www1.ietf.org/mailman/listinfo/mmusic=20
  >=20


------=_NextPart_001_004F_01C242AE.AFFE3350
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [MMUSIC] video media control draft</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Sanjoy et al,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>we were also concerned about the =
expressability of=20
quality attributes that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>defines the quality of service at =
application level=20
for a given video(audio) stream. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In =
draft-guenkova-mmusic-e2enp-sdpng-00.txt we=20
basically have identified a requirement</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to&nbsp;...</FONT><FONT face=3DArial =
size=3D2>=20
introduce (per) codec&nbsp;parametrization attributes like frame-rate,=20
frame-size, color-<BR>quality-range, overall-quality-range, etc. which =
should=20
be&nbsp;&nbsp;uniquely interpreted by the end-systems.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When it comes to negotiation of such =
attributes=20
with the peer for setting up quality enhanced</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>media streams, we propose to specify =
such=20
parameters on a per codec basis. The reason is </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that not all codecs support all =
combinations of=20
such parameters. For example with a given</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>hardware, a sender may be able to =
compress at 25=20
fps at CIF a H.261&nbsp;stream but may</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>not be able to compress at 25 fps at =
CIF a MPEG-4=20
stream due to limited resources.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We propose also to work on these issues =
within the=20
SDPng context.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-Andreas</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dsanjoy@nortelnetworks.com=20
  href=3D"mailto:sanjoy@nortelnetworks.com">Sanjoy Sen</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Droni.even@polycom.co.il=20
  href=3D"mailto:roni.even@polycom.co.il">'Even, Roni'</A> ; <A=20
  title=3Dnhl@tandberg.no href=3D"mailto:nhl@tandberg.no">'Nils Henrik=20
  Lorentzen'</A> ; <A title=3Dmmusic@ietf.org=20
  href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, August 13, 2002 =
1:55=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video =
media control=20
  draft</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><BR></DIV>
  <P><FONT size=3D2>I saw this pretty old thread. I do support proposing =

  frame-size on a per codec (payload-type) basis. I would also like to =
throw in=20
  the requirement that we need to be able to specify the preferred media =

  qualities (e.g., in a scale of 0-10) per payload-type (right now SDP =
defines a=20
  quality attribute per m line). Thoughts?</FONT></P>
  <P><FONT size=3D2>Does it make sense to encode all these information =
as part of=20
  an "fmtp" attribute for the payload-type? - e.g., a:fmtp:&lt;PT&gt;=20
  res=3DQCIF/quality=3D5</FONT></P>
  <P><FONT size=3D2>-Sanjoy</FONT> </P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
  From: Even, Roni [<A=20
  =
href=3D"mailto:roni.even@polycom.co.il">mailto:roni.even@polycom.co.il</A=
>]=20
  </FONT><BR><FONT size=3D2>&gt; Sent: Wednesday, August 07, 2002 1:21 =
AM</FONT>=20
  <BR><FONT size=3D2>&gt; To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; =
Even,=20
  Roni</FONT> <BR><FONT size=3D2>&gt; Subject: RE: [MMUSIC] video media =
control=20
  draft</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Nils,</FONT> <BR><FONT size=3D2>&gt; I =
think your=20
  suggestion makes sense. I will update the draft Roni</FONT> <BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; &gt; -----Original=20
  Message-----</FONT> <BR><FONT size=3D2>&gt; &gt; From: Nils Henrik =
Lorentzen [<A=20
  href=3D"mailto:nhl@tandberg.no">mailto:nhl@tandberg.no</A>]</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; Sent: Tuesday, August 06, 2002 10:35 AM</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; To: mmusic@ietf.org; Even, Roni</FONT> <BR><FONT =
size=3D2>&gt;=20
  &gt; Subject: Re: [MMUSIC] video media control draft</FONT> <BR><FONT=20
  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; On Tuesday 06 August 2002 07:59, Even, Roni =
wrote:</FONT>=20
  <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; &gt; =
Hi=20
  Petri,</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; In my draft=20
  draft-even-mmusic-video-media-control-00.txt, </FONT><BR><FONT =
size=3D2>&gt; I=20
  have a </FONT><BR><FONT size=3D2>&gt; &gt; &gt; video-resolution =
attribute that=20
  allow to specify the</FONT> <BR><FONT size=3D2>&gt; &gt; maximum frame =

  rate</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; supported per =
resolution.</FONT>=20
  <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; A =
difference=20
  between your draft and</FONT> <BR><FONT size=3D2>&gt; &gt;=20
  draft-koskelainen-sdp263-02.txt is that </FONT><BR><FONT size=3D2>&gt; =
&gt; in=20
  the latter you may specify resolutions and options per =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; payload type, </FONT><BR><FONT size=3D2>&gt; &gt; =
instead of=20
  per media line. I think this is more flexible, and </FONT><BR><FONT=20
  size=3D2>&gt; &gt; would suit our </FONT><BR><FONT size=3D2>&gt; &gt; =
needs=20
  better. Any particular reason for having it per media-line ?</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; In your draft =
it would be a=20
  simple change to make it per payload: </FONT><BR><FONT size=3D2>&gt; =
&gt;=20
  a=3Dvideo-resolution:&lt;size&gt; to</FONT> <BR><FONT size=3D2>&gt; =
&gt;=20
  a=3Dvideo-resolution: &lt;payload no&gt; &lt;size&gt;</FONT> <BR><FONT =

  size=3D2>&gt; &gt; or possibly</FONT> <BR><FONT size=3D2>&gt; &gt;=20
  a=3Dvideo-resolution: [ PT=3D&lt;payload no&gt;] &lt;size&gt;</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; ie payload no is optional, so if not specified the=20
  </FONT><BR><FONT size=3D2>&gt; &gt; resolutions would apply to =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; all the payload types on the media line.</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; &gt; In the =
meeting this=20
  attribute was accepted for</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; =
SDP. I could=20
  not find the draft mentioned</FONT> <BR><FONT size=3D2>&gt; &gt;=20
  "draft-koskelainen-sdp263-02.txt"</FONT> <BR><FONT size=3D2>&gt; &gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; It expired quite some time ago, =
but can be=20
  found at: </FONT><BR><FONT size=3D2>&gt; &gt; <A=20
  =
href=3D"http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai"=20
  =
target=3D_blank>http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-kos=
kelai</A></FONT>=20
  <BR><FONT size=3D2>&gt; &gt; nen-sdp263-02.txt</FONT> <BR><FONT =
size=3D2>&gt; &gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Nils Henrik Lorentzen</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  _______________________________________________</FONT> <BR><FONT =
size=3D2>&gt;=20
  mmusic mailing list</FONT> <BR><FONT size=3D2>&gt; =
mmusic@ietf.org</FONT>=20
  <BR><FONT size=3D2>&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mmusic"=20
  =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mmusic</A></FONT> =

  <BR><FONT size=3D2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_001_004F_01C242AE.AFFE3350--

------=_NextPart_000_004E_01C242AE.AFFE3350
Content-Type: text/x-vcard;
	name="Andreas J. Kassler.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="Andreas J. Kassler.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Kassler;Andreas;J.;Dr.
FN:Andreas J. Kassler
ORG:University of Ulm;Distributed Systems
TITLE:Project Manager
TEL;WORK;VOICE:++49 731 502 4146
TEL;WORK;FAX:++49 731 502 4142
ADR;WORK:;;Oberer Eselsberg 9;Ulm;Baden W=FCrttemberg;89069
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Oberer Eselsberg 9=3D0D=3D0AUlm, =
Baden W=3DFCrttemberg 89069
URL;WORK:http://www-vs.informatik.uni-ulm.de
EMAIL;PREF;INTERNET:kassler@informatik.uni-ulm.de
REV:20020813T074916Z
END:VCARD

------=_NextPart_000_004E_01C242AE.AFFE3350--


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



From daemon@optimus.ietf.org  Tue Aug 13 14:05:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11843
	for <mmusic-archive@odin.ietf.org>; Tue, 13 Aug 2002 14:05:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA26120
	for mmusic-archive@odin.ietf.org; Tue, 13 Aug 2002 14:07:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25255;
	Tue, 13 Aug 2002 13:59:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25223
	for <mmusic@optimus.ietf.org>; Tue, 13 Aug 2002 13:59:15 -0400 (EDT)
Received: from chiron.nge.isi.edu (chiron.nge.isi.edu [65.114.169.204])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11459
	for <mmusic@ietf.org>; Tue, 13 Aug 2002 13:57:56 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g7DHx5n11883;
	Tue, 13 Aug 2002 13:59:05 -0400
Message-Id: <200208131759.g7DHx5n11883@chiron.nge.isi.edu>
To: "Sanjoy Sen" <sanjoy@nortelnetworks.com>
cc: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Mon, 12 Aug 2002 18:55:27 CDT."
             <933FADF5E673D411B8A30002A5608A0E03A63444@zrc2c012.us.nortel.com> 
Date: Tue, 13 Aug 2002 13:59:05 -0400
From: Colin Perkins <csp@isi.edu>
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

--> "Sanjoy Sen" writes:
>I saw this pretty old thread. I do support proposing frame-size on a per
>codec (payload-type) basis. I would also like to throw in the requirement
>that we need to be able to specify the preferred media qualities (e.g., in a
>scale of 0-10) per payload-type (right now SDP defines a quality attribute
>per m line). Thoughts?
>
>Does it make sense to encode all these information as part of an "fmtp"
>attribute for the payload-type? - e.g., a:fmtp:<PT> res=QCIF/quality=5

No, because a=fmtp is part of the payload type definition. If we do this at
all, it should be a new attribute (there was a "generic format parameter"
attribute proposal a while back, that may be suitable).

But, really, this is something for SDPng to do right.

Colin

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



From daemon@optimus.ietf.org  Wed Aug 14 02:37:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28331
	for <mmusic-archive@odin.ietf.org>; Wed, 14 Aug 2002 02:37:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA06427
	for mmusic-archive@odin.ietf.org; Wed, 14 Aug 2002 02:38:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06374;
	Wed, 14 Aug 2002 02:36:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06335
	for <mmusic@optimus.ietf.org>; Wed, 14 Aug 2002 02:36:04 -0400 (EDT)
Received: from accord-ntsrv3.accord.co.il ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28303
	for <mmusic@ietf.org>; Wed, 14 Aug 2002 02:34:43 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <Q7GGJPWG>; Wed, 14 Aug 2002 09:35:23 +0300
Message-ID: <C550397C3B6AEB418E62170D9E349CE2136ADD@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Andreas Kassler'" <kassler@informatik.uni-ulm.de>,
        Sanjoy Sen
	 <sanjoy@nortelnetworks.com>,
        "Even, Roni" <roni.even@polycom.co.il>,
        "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Wed, 14 Aug 2002 09:35:22 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2435C.C453E580"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

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

------_=_NextPart_001_01C2435C.C453E580
Content-Type: text/plain;
	charset="ISO-8859-1"

Hi,
I understand the need for asking for frame rate and frame size since these
are absolute numbers and that is why we have the media control draft and I
will add the support for per payload type.
As for the quality how do you define that in absolute terms, isn't it
something that is an application or codec specific. Is someone using the
quality attribute in SDP and if yes what are the user expectations when he
ask for higher quality comparing to lower quality.How does the encoder use
this parameter, one way to get "high quality" is by reducing the frame rate
or resolution at the same line rate but this can be controlled by those
attributes. At least in this case the receiver can say what he is willing to
scarifies (frame rate or resolution) to get higher quality
Thanks
Roni Even

 
 
 -----Original Message-----
From: Andreas Kassler [mailto:kassler@informatik.uni-ulm.de]
Sent: Tuesday, August 13, 2002 10:49 AM
To: Sanjoy Sen; 'Even, Roni'; 'Nils Henrik Lorentzen'; mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft



Sanjoy et al,
we were also concerned about the expressability of quality attributes that
defines the quality of service at application level for a given video(audio)
stream. 
In draft-guenkova-mmusic-e2enp-sdpng-00.txt we basically have identified a
requirement
to ... introduce (per) codec parametrization attributes like frame-rate,
frame-size, color-
quality-range, overall-quality-range, etc. which should be  uniquely
interpreted by the end-systems.
 
When it comes to negotiation of such attributes with the peer for setting up
quality enhanced
media streams, we propose to specify such parameters on a per codec basis.
The reason is 
that not all codecs support all combinations of such parameters. For example
with a given
hardware, a sender may be able to compress at 25 fps at CIF a H.261 stream
but may
not be able to compress at 25 fps at CIF a MPEG-4 stream due to limited
resources.
 
We propose also to work on these issues within the SDPng context.
 
-Andreas

----- Original Message ----- 
From: Sanjoy Sen <mailto:sanjoy@nortelnetworks.com>  
To: 'Even, Roni' <mailto:roni.even@polycom.co.il>  ; 'Nils Henrik
<mailto:nhl@tandberg.no> Lorentzen' ; mmusic@ietf.org
<mailto:mmusic@ietf.org>  
Sent: Tuesday, August 13, 2002 1:55 AM
Subject: RE: [MMUSIC] video media control draft



I saw this pretty old thread. I do support proposing frame-size on a per
codec (payload-type) basis. I would also like to throw in the requirement
that we need to be able to specify the preferred media qualities (e.g., in a
scale of 0-10) per payload-type (right now SDP defines a quality attribute
per m line). Thoughts?

Does it make sense to encode all these information as part of an "fmtp"
attribute for the payload-type? - e.g., a:fmtp:<PT> res=QCIF/quality=5

-Sanjoy 

> -----Original Message----- 
> From: Even, Roni [ mailto:roni.even@polycom.co.il
<mailto:roni.even@polycom.co.il> ] 
> Sent: Wednesday, August 07, 2002 1:21 AM 
> To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, Roni 
> Subject: RE: [MMUSIC] video media control draft 
> 
> 
> Nils, 
> I think your suggestion makes sense. I will update the draft Roni 
> 
> > -----Original Message----- 
> > From: Nils Henrik Lorentzen [ mailto:nhl@tandberg.no
<mailto:nhl@tandberg.no> ] 
> > Sent: Tuesday, August 06, 2002 10:35 AM 
> > To: mmusic@ietf.org; Even, Roni 
> > Subject: Re: [MMUSIC] video media control draft 
> > 
> > 
> > On Tuesday 06 August 2002 07:59, Even, Roni wrote: 
> > 
> > > Hi Petri, 
> > > In my draft draft-even-mmusic-video-media-control-00.txt, 
> I have a 
> > > video-resolution attribute that allow to specify the 
> > maximum frame rate 
> > > supported per resolution. 
> > 
> > A difference between your draft and 
> > draft-koskelainen-sdp263-02.txt is that 
> > in the latter you may specify resolutions and options per 
> > payload type, 
> > instead of per media line. I think this is more flexible, and 
> > would suit our 
> > needs better. Any particular reason for having it per media-line ? 
> > 
> > In your draft it would be a simple change to make it per payload: 
> > a=video-resolution:<size> to 
> > a=video-resolution: <payload no> <size> 
> > or possibly 
> > a=video-resolution: [ PT=<payload no>] <size> 
> > ie payload no is optional, so if not specified the 
> > resolutions would apply to 
> > all the payload types on the media line. 
> > 
> > > In the meeting this attribute was accepted for 
> > > SDP. I could not find the draft mentioned 
> > "draft-koskelainen-sdp263-02.txt" 
> > 
> > It expired quite some time ago, but can be found at: 
> > http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai
<http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai>  
> > nen-sdp263-02.txt 
> > 
> > Nils Henrik Lorentzen 
> > 
> 
> _______________________________________________ 
> mmusic mailing list 
> mmusic@ietf.org 
> https://www1.ietf.org/mailman/listinfo/mmusic
<https://www1.ietf.org/mailman/listinfo/mmusic>  
> 


------_=_NextPart_001_01C2435C.C453E580
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>RE: [MMUSIC] video media control draft</TITLE>

<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff 
size=2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff size=2>I 
understand the need for asking for frame rate and frame size since these are 
absolute numbers and that is why we have the media control draft and I will add 
the support for per payload type.</FONT></SPAN></DIV>
<DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff size=2>As for 
the quality how do you define that in absolute terms, isn't it something that is 
an application or codec specific. Is someone using the quality attribute in SDP 
and if yes what are the user expectations when he ask for higher quality 
comparing to lower quality.How does the encoder use this parameter, one way to 
get "high quality" is by reducing the frame rate or resolution at the same line 
rate but this can be controlled by those attributes. At least in this case the 
receiver can say what he is willing to scarifies (frame rate or resolution) to 
get higher quality</FONT></SPAN></DIV>
<DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff 
size=2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff size=2>Roni 
Even</FONT></SPAN></DIV><SPAN class=223252506-14082002></SPAN><FONT face=Tahoma>
<DIV><BR><FONT size=2><SPAN class=223252506-14082002><FONT face=Arial 
color=#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=223252506-14082002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=223252506-14082002>&nbsp;</SPAN>-----Original 
Message-----<BR><B>From:</B> Andreas Kassler 
[mailto:kassler@informatik.uni-ulm.de]<BR><B>Sent:</B> Tuesday, August 13, 2002 
10:49 AM<BR><B>To:</B> Sanjoy Sen; 'Even, Roni'; 'Nils Henrik Lorentzen'; 
mmusic@ietf.org<BR><B>Subject:</B> Re: [MMUSIC] video media control 
draft<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV><FONT face=Arial size=2>Sanjoy et al,</FONT></DIV>
  <DIV><FONT face=Arial size=2>we were also concerned about the expressability 
  of quality attributes that</FONT></DIV>
  <DIV><FONT face=Arial size=2>defines the quality of service at application 
  level for a given video(audio) stream. </FONT></DIV>
  <DIV><FONT face=Arial size=2>In draft-guenkova-mmusic-e2enp-sdpng-00.txt we 
  basically have identified a requirement</FONT></DIV>
  <DIV><FONT face=Arial size=2>to&nbsp;...</FONT><FONT face=Arial size=2> 
  introduce (per) codec&nbsp;parametrization attributes like frame-rate, 
  frame-size, color-<BR>quality-range, overall-quality-range, etc. which should 
  be&nbsp;&nbsp;uniquely interpreted by the end-systems.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>When it comes to negotiation of such attributes 
  with the peer for setting up quality enhanced</FONT></DIV>
  <DIV><FONT face=Arial size=2>media streams, we propose to specify such 
  parameters on a per codec basis. The reason is </FONT></DIV>
  <DIV><FONT face=Arial size=2>that not all codecs support all combinations of 
  such parameters. For example with a given</FONT></DIV>
  <DIV><FONT face=Arial size=2>hardware, a sender may be able to compress at 25 
  fps at CIF a H.261&nbsp;stream but may</FONT></DIV>
  <DIV><FONT face=Arial size=2>not be able to compress at 25 fps at CIF a MPEG-4 
  stream due to limited resources.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>We propose also to work on these issues within 
  the SDPng context.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>-Andreas</FONT></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=sanjoy@nortelnetworks.com 
    href="mailto:sanjoy@nortelnetworks.com">Sanjoy Sen</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=roni.even@polycom.co.il 
    href="mailto:roni.even@polycom.co.il">'Even, Roni'</A> ; <A 
    title=nhl@tandberg.no href="mailto:nhl@tandberg.no">'Nils Henrik 
    Lorentzen'</A> ; <A title=mmusic@ietf.org 
    href="mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, August 13, 2002 1:55 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video media 
    control draft</DIV>
    <DIV><FONT face=Arial size=2></FONT><FONT face=Arial 
size=2></FONT><BR></DIV>
    <P><FONT size=2>I saw this pretty old thread. I do support proposing 
    frame-size on a per codec (payload-type) basis. I would also like to throw 
    in the requirement that we need to be able to specify the preferred media 
    qualities (e.g., in a scale of 0-10) per payload-type (right now SDP defines 
    a quality attribute per m line). Thoughts?</FONT></P>
    <P><FONT size=2>Does it make sense to encode all these information as part 
    of an "fmtp" attribute for the payload-type? - e.g., a:fmtp:&lt;PT&gt; 
    res=QCIF/quality=5</FONT></P>
    <P><FONT size=2>-Sanjoy</FONT> </P>
    <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
    From: Even, Roni [<A 
    href="mailto:roni.even@polycom.co.il">mailto:roni.even@polycom.co.il</A>] 
    </FONT><BR><FONT size=2>&gt; Sent: Wednesday, August 07, 2002 1:21 AM</FONT> 
    <BR><FONT size=2>&gt; To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, 
    Roni</FONT> <BR><FONT size=2>&gt; Subject: RE: [MMUSIC] video media control 
    draft</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
    </FONT><BR><FONT size=2>&gt; Nils,</FONT> <BR><FONT size=2>&gt; I think your 
    suggestion makes sense. I will update the draft Roni</FONT> <BR><FONT 
    size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
    Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Nils Henrik Lorentzen 
    [<A href="mailto:nhl@tandberg.no">mailto:nhl@tandberg.no</A>]</FONT> 
    <BR><FONT size=2>&gt; &gt; Sent: Tuesday, August 06, 2002 10:35 AM</FONT> 
    <BR><FONT size=2>&gt; &gt; To: mmusic@ietf.org; Even, Roni</FONT> <BR><FONT 
    size=2>&gt; &gt; Subject: Re: [MMUSIC] video media control draft</FONT> 
    <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
    </FONT><BR><FONT size=2>&gt; &gt; On Tuesday 06 August 2002 07:59, Even, 
    Roni wrote:</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
    &gt; &gt; Hi Petri,</FONT> <BR><FONT size=2>&gt; &gt; &gt; In my draft 
    draft-even-mmusic-video-media-control-00.txt, </FONT><BR><FONT size=2>&gt; I 
    have a </FONT><BR><FONT size=2>&gt; &gt; &gt; video-resolution attribute 
    that allow to specify the</FONT> <BR><FONT size=2>&gt; &gt; maximum frame 
    rate</FONT> <BR><FONT size=2>&gt; &gt; &gt; supported per resolution.</FONT> 
    <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; A difference 
    between your draft and</FONT> <BR><FONT size=2>&gt; &gt; 
    draft-koskelainen-sdp263-02.txt is that </FONT><BR><FONT size=2>&gt; &gt; in 
    the latter you may specify resolutions and options per </FONT><BR><FONT 
    size=2>&gt; &gt; payload type, </FONT><BR><FONT size=2>&gt; &gt; instead of 
    per media line. I think this is more flexible, and </FONT><BR><FONT 
    size=2>&gt; &gt; would suit our </FONT><BR><FONT size=2>&gt; &gt; needs 
    better. Any particular reason for having it per media-line ?</FONT> 
    <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; In your draft 
    it would be a simple change to make it per payload: </FONT><BR><FONT 
    size=2>&gt; &gt; a=video-resolution:&lt;size&gt; to</FONT> <BR><FONT 
    size=2>&gt; &gt; a=video-resolution: &lt;payload no&gt; &lt;size&gt;</FONT> 
    <BR><FONT size=2>&gt; &gt; or possibly</FONT> <BR><FONT size=2>&gt; &gt; 
    a=video-resolution: [ PT=&lt;payload no&gt;] &lt;size&gt;</FONT> <BR><FONT 
    size=2>&gt; &gt; ie payload no is optional, so if not specified the 
    </FONT><BR><FONT size=2>&gt; &gt; resolutions would apply to 
    </FONT><BR><FONT size=2>&gt; &gt; all the payload types on the media 
    line.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
    &gt; In the meeting this attribute was accepted for</FONT> <BR><FONT 
    size=2>&gt; &gt; &gt; SDP. I could not find the draft mentioned</FONT> 
    <BR><FONT size=2>&gt; &gt; "draft-koskelainen-sdp263-02.txt"</FONT> 
    <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; It expired 
    quite some time ago, but can be found at: </FONT><BR><FONT size=2>&gt; &gt; 
    <A href="http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai" 
    target=_blank>http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai</A></FONT> 
    <BR><FONT size=2>&gt; &gt; nen-sdp263-02.txt</FONT> <BR><FONT size=2>&gt; 
    &gt; </FONT><BR><FONT size=2>&gt; &gt; Nils Henrik Lorentzen</FONT> 
    <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
    size=2>&gt; _______________________________________________</FONT> <BR><FONT 
    size=2>&gt; mmusic mailing list</FONT> <BR><FONT size=2>&gt; 
    mmusic@ietf.org</FONT> <BR><FONT size=2>&gt; <A 
    href="https://www1.ietf.org/mailman/listinfo/mmusic" 
    target=_blank>https://www1.ietf.org/mailman/listinfo/mmusic</A></FONT> 
    <BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2435C.C453E580--

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



From daemon@optimus.ietf.org  Wed Aug 14 02:58:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28603
	for <mmusic-archive@odin.ietf.org>; Wed, 14 Aug 2002 02:58:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA07039
	for mmusic-archive@odin.ietf.org; Wed, 14 Aug 2002 02:59:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA07004;
	Wed, 14 Aug 2002 02:58:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06939
	for <mmusic@optimus.ietf.org>; Wed, 14 Aug 2002 02:58:08 -0400 (EDT)
Received: from vs.informatik.uni-ulm.de (vs.informatik.uni-ulm.de [134.60.77.243])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28584
	for <mmusic@ietf.org>; Wed, 14 Aug 2002 02:56:47 -0400 (EDT)
Received: from lamagra (lamagra.informatik.uni-ulm.de [134.60.77.31])
	by vs.informatik.uni-ulm.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with SMTP id g7E60rB16254;
	Wed, 14 Aug 2002 08:00:53 +0200
X-Authentication-Warning: vs.informatik.uni-ulm.de: Host lamagra.informatik.uni-ulm.de [134.60.77.31] claimed to be lamagra
Message-ID: <003901c24360$399b0fa0$1f4d3c86@lamagra>
From: "Andreas Kassler" <kassler@informatik.uni-ulm.de>
To: "Even, Roni" <roni.even@polycom.co.il>,
        "Sanjoy Sen" <sanjoy@nortelnetworks.com>,
        "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, <mmusic@ietf.org>
References: <C550397C3B6AEB418E62170D9E349CE2136ADD@ACCORD-NTSRV3>
Subject: Re: [MMUSIC] video media control draft
Date: Wed, 14 Aug 2002 09:00:07 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01C24370.FCF68E10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0036_01C24370.FCF68E10
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RE: [MMUSIC] video media control draftHi,
regarding the visual quality, I was targeting more to variable bitrate =
codecs, where you can change
the visual quality (e.g. by changing the quantization) independent from =
the frame size and the frame
rate. Of course this may result in a change of the data rate, which may =
lead to a renegotiation for
network resources (using RSVP updates or to be defined NSIS signalling).
When you think about constant bitrate codecs I absolutely agree with you =
that we need some preferences:
- e.g. frame rate is more important than visual quality
We could use here e.g. some weighting factors and it is up to the codec =
to configure itself correctly.
For the "frame rate is more important than visual quality" scenario, we =
could have something like=20
- frame_rate =3D 70, visual_quality =3D 30
For the "frame rate is equally important as visual quality" scenario, we =
could have something like=20
- frame_rate =3D 50, visual_quality =3D 50, and so on.
What do you think?
Regards, Andreas.
  ----- Original Message -----=20
  From: Even, Roni=20
  To: 'Andreas Kassler' ; Sanjoy Sen ; Even, Roni ; 'Nils Henrik =
Lorentzen' ; mmusic@ietf.org=20
  Sent: Wednesday, August 14, 2002 8:35 AM
  Subject: RE: [MMUSIC] video media control draft


  Hi,
  I understand the need for asking for frame rate and frame size since =
these are absolute numbers and that is why we have the media control =
draft and I will add the support for per payload type.
  As for the quality how do you define that in absolute terms, isn't it =
something that is an application or codec specific. Is someone using the =
quality attribute in SDP and if yes what are the user expectations when =
he ask for higher quality comparing to lower quality.How does the =
encoder use this parameter, one way to get "high quality" is by reducing =
the frame rate or resolution at the same line rate but this can be =
controlled by those attributes. At least in this case the receiver can =
say what he is willing to scarifies (frame rate or resolution) to get =
higher quality
  Thanks
  Roni Even

  =20

   -----Original Message-----
  From: Andreas Kassler [mailto:kassler@informatik.uni-ulm.de]
  Sent: Tuesday, August 13, 2002 10:49 AM
  To: Sanjoy Sen; 'Even, Roni'; 'Nils Henrik Lorentzen'; mmusic@ietf.org
  Subject: Re: [MMUSIC] video media control draft


    Sanjoy et al,
    we were also concerned about the expressability of quality =
attributes that
    defines the quality of service at application level for a given =
video(audio) stream.=20
    In draft-guenkova-mmusic-e2enp-sdpng-00.txt we basically have =
identified a requirement
    to ... introduce (per) codec parametrization attributes like =
frame-rate, frame-size, color-
    quality-range, overall-quality-range, etc. which should be  uniquely =
interpreted by the end-systems.

    When it comes to negotiation of such attributes with the peer for =
setting up quality enhanced
    media streams, we propose to specify such parameters on a per codec =
basis. The reason is=20
    that not all codecs support all combinations of such parameters. For =
example with a given
    hardware, a sender may be able to compress at 25 fps at CIF a H.261 =
stream but may
    not be able to compress at 25 fps at CIF a MPEG-4 stream due to =
limited resources.

    We propose also to work on these issues within the SDPng context.

    -Andreas
      ----- Original Message -----=20
      From: Sanjoy Sen=20
      To: 'Even, Roni' ; 'Nils Henrik Lorentzen' ; mmusic@ietf.org=20
      Sent: Tuesday, August 13, 2002 1:55 AM
      Subject: RE: [MMUSIC] video media control draft


      I saw this pretty old thread. I do support proposing frame-size on =
a per codec (payload-type) basis. I would also like to throw in the =
requirement that we need to be able to specify the preferred media =
qualities (e.g., in a scale of 0-10) per payload-type (right now SDP =
defines a quality attribute per m line). Thoughts?

      Does it make sense to encode all these information as part of an =
"fmtp" attribute for the payload-type? - e.g., a:fmtp:<PT> =
res=3DQCIF/quality=3D5

      -Sanjoy=20

      > -----Original Message-----=20
      > From: Even, Roni [mailto:roni.even@polycom.co.il]=20
      > Sent: Wednesday, August 07, 2002 1:21 AM=20
      > To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, Roni=20
      > Subject: RE: [MMUSIC] video media control draft=20
      >=20
      >=20
      > Nils,=20
      > I think your suggestion makes sense. I will update the draft =
Roni=20
      >=20
      > > -----Original Message-----=20
      > > From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no]=20
      > > Sent: Tuesday, August 06, 2002 10:35 AM=20
      > > To: mmusic@ietf.org; Even, Roni=20
      > > Subject: Re: [MMUSIC] video media control draft=20
      > >=20
      > >=20
      > > On Tuesday 06 August 2002 07:59, Even, Roni wrote:=20
      > >=20
      > > > Hi Petri,=20
      > > > In my draft draft-even-mmusic-video-media-control-00.txt,=20
      > I have a=20
      > > > video-resolution attribute that allow to specify the=20
      > > maximum frame rate=20
      > > > supported per resolution.=20
      > >=20
      > > A difference between your draft and=20
      > > draft-koskelainen-sdp263-02.txt is that=20
      > > in the latter you may specify resolutions and options per=20
      > > payload type,=20
      > > instead of per media line. I think this is more flexible, and=20
      > > would suit our=20
      > > needs better. Any particular reason for having it per =
media-line ?=20
      > >=20
      > > In your draft it would be a simple change to make it per =
payload:=20
      > > a=3Dvideo-resolution:<size> to=20
      > > a=3Dvideo-resolution: <payload no> <size>=20
      > > or possibly=20
      > > a=3Dvideo-resolution: [ PT=3D<payload no>] <size>=20
      > > ie payload no is optional, so if not specified the=20
      > > resolutions would apply to=20
      > > all the payload types on the media line.=20
      > >=20
      > > > In the meeting this attribute was accepted for=20
      > > > SDP. I could not find the draft mentioned=20
      > > "draft-koskelainen-sdp263-02.txt"=20
      > >=20
      > > It expired quite some time ago, but can be found at:=20
      > > http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai =

      > > nen-sdp263-02.txt=20
      > >=20
      > > Nils Henrik Lorentzen=20
      > >=20
      >=20
      > _______________________________________________=20
      > mmusic mailing list=20
      > mmusic@ietf.org=20
      > https://www1.ietf.org/mailman/listinfo/mmusic=20
      >=20


------=_NextPart_000_0036_01C24370.FCF68E10
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [MMUSIC] video media control draft</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>regarding the visual quality, I was =
targeting more=20
to variable bitrate codecs, where you can change</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the visual quality (e.g. by changing =
the=20
quantization) independent from the frame size and the frame</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>rate. Of course this may result in a =
change of the=20
data rate, which may lead to a renegotiation for</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>network resources (using RSVP updates =
or to be=20
defined NSIS signalling).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>When you think about constant bitrate =
codecs I=20
absolutely agree with you that we need some preferences:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- e.g. frame rate is more important =
than visual=20
quality</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>We could use here e.g. some weighting =
factors and=20
it is up to the codec to configure itself correctly.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>For the "frame rate is more important =
than visual=20
quality" scenario, we could have something like </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- frame_rate =3D 70, visual_quality =3D =
30</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>For the "frame rate is&nbsp;equally=20
important&nbsp;as visual quality" scenario, we could have something like =

</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- frame_rate =3D 50, visual_quality =3D =
50, and so=20
on.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What do you think?</FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2>Regards, Andreas.</FONT></DIV></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Droni.even@polycom.co.il =
href=3D"mailto:roni.even@polycom.co.il">Even,=20
  Roni</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  title=3Dkassler@informatik.uni-ulm.de=20
  href=3D"mailto:kassler@informatik.uni-ulm.de">'Andreas Kassler'</A> ; =
<A=20
  title=3Dsanjoy@nortelnetworks.com =
href=3D"mailto:sanjoy@nortelnetworks.com">Sanjoy=20
  Sen</A> ; <A title=3Droni.even@polycom.co.il=20
  href=3D"mailto:roni.even@polycom.co.il">Even, Roni</A> ; <A=20
  title=3Dnhl@tandberg.no href=3D"mailto:nhl@tandberg.no">'Nils Henrik=20
  Lorentzen'</A> ; <A title=3Dmmusic@ietf.org=20
  href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, August 14, =
2002 8:35=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video =
media control=20
  draft</DIV>
  <DIV><BR></DIV>
  <DIV><SPAN class=3D223252506-14082002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Hi,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D223252506-14082002><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
  understand the need for asking for frame rate and frame size since =
these are=20
  absolute numbers and that is why we have the media control draft and I =
will=20
  add the support for per payload type.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D223252506-14082002><FONT face=3DArial =
color=3D#0000ff size=3D2>As=20
  for the quality how do you define that in absolute terms, isn't it =
something=20
  that is an application or codec specific. Is someone using the quality =

  attribute in SDP and if yes what are the user expectations when he ask =
for=20
  higher quality comparing to lower quality.How does the encoder use =
this=20
  parameter, one way to get "high quality" is by reducing the frame rate =
or=20
  resolution at the same line rate but this can be controlled by those=20
  attributes. At least in this case the receiver can say what he is =
willing to=20
  scarifies (frame rate or resolution) to get higher =
quality</FONT></SPAN></DIV>
  <DIV><SPAN class=3D223252506-14082002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Thanks</FONT></SPAN></DIV>
  <DIV><SPAN class=3D223252506-14082002><FONT face=3DArial =
color=3D#0000ff size=3D2>Roni=20
  Even</FONT></SPAN></DIV><SPAN class=3D223252506-14082002></SPAN><FONT=20
  face=3DTahoma>
  <DIV><BR><FONT size=3D2><SPAN class=3D223252506-14082002><FONT =
face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
  <DIV><FONT size=3D2><SPAN =
class=3D223252506-14082002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2><SPAN =
class=3D223252506-14082002>&nbsp;</SPAN>-----Original=20
  Message-----<BR><B>From:</B> Andreas Kassler=20
  [mailto:kassler@informatik.uni-ulm.de]<BR><B>Sent:</B> Tuesday, August =
13,=20
  2002 10:49 AM<BR><B>To:</B> Sanjoy Sen; 'Even, Roni'; 'Nils Henrik =
Lorentzen';=20
  mmusic@ietf.org<BR><B>Subject:</B> Re: [MMUSIC] video media control=20
  draft<BR><BR></DIV></FONT></FONT>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV><FONT face=3DArial size=3D2>Sanjoy et al,</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>we were also concerned about the =
expressability=20
    of quality attributes that</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>defines the quality of service at =
application=20
    level for a given video(audio) stream. </FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>In =
draft-guenkova-mmusic-e2enp-sdpng-00.txt we=20
    basically have identified a requirement</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>to&nbsp;...</FONT><FONT =
face=3DArial size=3D2>=20
    introduce (per) codec&nbsp;parametrization attributes like =
frame-rate,=20
    frame-size, color-<BR>quality-range, overall-quality-range, etc. =
which=20
    should be&nbsp;&nbsp;uniquely interpreted by the =
end-systems.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>When it comes to negotiation of =
such attributes=20
    with the peer for setting up quality enhanced</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>media streams, we propose to =
specify such=20
    parameters on a per codec basis. The reason is </FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>that not all codecs support all =
combinations of=20
    such parameters. For example with a given</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>hardware, a sender may be able to =
compress at=20
    25 fps at CIF a H.261&nbsp;stream but may</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2>not be able to compress at 25 fps =
at CIF a=20
    MPEG-4 stream due to limited resources.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>We propose also to work on these =
issues within=20
    the SDPng context.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>-Andreas</FONT></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>
      <DIV=20
      style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
      <A title=3Dsanjoy@nortelnetworks.com=20
      href=3D"mailto:sanjoy@nortelnetworks.com">Sanjoy Sen</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Droni.even@polycom.co.il=20
      href=3D"mailto:roni.even@polycom.co.il">'Even, Roni'</A> ; <A=20
      title=3Dnhl@tandberg.no href=3D"mailto:nhl@tandberg.no">'Nils =
Henrik=20
      Lorentzen'</A> ; <A title=3Dmmusic@ietf.org=20
      href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, August 13, =
2002 1:55=20
      AM</DIV>
      <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video =
media=20
      control draft</DIV>
      <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
      size=3D2></FONT><BR></DIV>
      <P><FONT size=3D2>I saw this pretty old thread. I do support =
proposing=20
      frame-size on a per codec (payload-type) basis. I would also like =
to throw=20
      in the requirement that we need to be able to specify the =
preferred media=20
      qualities (e.g., in a scale of 0-10) per payload-type (right now =
SDP=20
      defines a quality attribute per m line). Thoughts?</FONT></P>
      <P><FONT size=3D2>Does it make sense to encode all these =
information as part=20
      of an "fmtp" attribute for the payload-type? - e.g., =
a:fmtp:&lt;PT&gt;=20
      res=3DQCIF/quality=3D5</FONT></P>
      <P><FONT size=3D2>-Sanjoy</FONT> </P>
      <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =

      size=3D2>&gt; From: Even, Roni [<A=20
      =
href=3D"mailto:roni.even@polycom.co.il">mailto:roni.even@polycom.co.il</A=
>]=20
      </FONT><BR><FONT size=3D2>&gt; Sent: Wednesday, August 07, 2002 =
1:21=20
      AM</FONT> <BR><FONT size=3D2>&gt; To: 'Nils Henrik Lorentzen';=20
      mmusic@ietf.org; Even, Roni</FONT> <BR><FONT size=3D2>&gt; =
Subject: RE:=20
      [MMUSIC] video media control draft</FONT> <BR><FONT size=3D2>&gt;=20
      </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Nils,</FONT>=20
      <BR><FONT size=3D2>&gt; I think your suggestion makes sense. I =
will update=20
      the draft Roni</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
      &gt; -----Original Message-----</FONT> <BR><FONT size=3D2>&gt; =
&gt; From:=20
      Nils Henrik Lorentzen [<A=20
      href=3D"mailto:nhl@tandberg.no">mailto:nhl@tandberg.no</A>]</FONT> =
<BR><FONT=20
      size=3D2>&gt; &gt; Sent: Tuesday, August 06, 2002 10:35 AM</FONT> =
<BR><FONT=20
      size=3D2>&gt; &gt; To: mmusic@ietf.org; Even, Roni</FONT> =
<BR><FONT=20
      size=3D2>&gt; &gt; Subject: Re: [MMUSIC] video media control =
draft</FONT>=20
      <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt;=20
      </FONT><BR><FONT size=3D2>&gt; &gt; On Tuesday 06 August 2002 =
07:59, Even,=20
      Roni wrote:</FONT> <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT =
size=3D2>&gt;=20
      &gt; &gt; Hi Petri,</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; In my =
draft=20
      draft-even-mmusic-video-media-control-00.txt, </FONT><BR><FONT =
size=3D2>&gt;=20
      I have a </FONT><BR><FONT size=3D2>&gt; &gt; &gt; video-resolution =
attribute=20
      that allow to specify the</FONT> <BR><FONT size=3D2>&gt; &gt; =
maximum frame=20
      rate</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; supported per=20
      resolution.</FONT> <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT =
size=3D2>&gt;=20
      &gt; A difference between your draft and</FONT> <BR><FONT =
size=3D2>&gt; &gt;=20
      draft-koskelainen-sdp263-02.txt is that </FONT><BR><FONT =
size=3D2>&gt; &gt;=20
      in the latter you may specify resolutions and options per =
</FONT><BR><FONT=20
      size=3D2>&gt; &gt; payload type, </FONT><BR><FONT size=3D2>&gt; =
&gt; instead=20
      of per media line. I think this is more flexible, and =
</FONT><BR><FONT=20
      size=3D2>&gt; &gt; would suit our </FONT><BR><FONT size=3D2>&gt; =
&gt; needs=20
      better. Any particular reason for having it per media-line =
?</FONT>=20
      <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; &gt; =
In your draft=20
      it would be a simple change to make it per payload: =
</FONT><BR><FONT=20
      size=3D2>&gt; &gt; a=3Dvideo-resolution:&lt;size&gt; to</FONT> =
<BR><FONT=20
      size=3D2>&gt; &gt; a=3Dvideo-resolution: &lt;payload no&gt;=20
      &lt;size&gt;</FONT> <BR><FONT size=3D2>&gt; &gt; or =
possibly</FONT>=20
      <BR><FONT size=3D2>&gt; &gt; a=3Dvideo-resolution: [ =
PT=3D&lt;payload no&gt;]=20
      &lt;size&gt;</FONT> <BR><FONT size=3D2>&gt; &gt; ie payload no is =
optional,=20
      so if not specified the </FONT><BR><FONT size=3D2>&gt; &gt; =
resolutions=20
      would apply to </FONT><BR><FONT size=3D2>&gt; &gt; all the payload =
types on=20
      the media line.</FONT> <BR><FONT size=3D2>&gt; &gt; =
</FONT><BR><FONT=20
      size=3D2>&gt; &gt; &gt; In the meeting this attribute was accepted =

      for</FONT> <BR><FONT size=3D2>&gt; &gt; &gt; SDP. I could not find =
the draft=20
      mentioned</FONT> <BR><FONT size=3D2>&gt; &gt;=20
      "draft-koskelainen-sdp263-02.txt"</FONT> <BR><FONT size=3D2>&gt; =
&gt;=20
      </FONT><BR><FONT size=3D2>&gt; &gt; It expired quite some time =
ago, but can=20
      be found at: </FONT><BR><FONT size=3D2>&gt; &gt; <A=20
      =
href=3D"http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai"=20
      =
target=3D_blank>http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-kos=
kelai</A></FONT>=20
      <BR><FONT size=3D2>&gt; &gt; nen-sdp263-02.txt</FONT> <BR><FONT =
size=3D2>&gt;=20
      &gt; </FONT><BR><FONT size=3D2>&gt; &gt; Nils Henrik =
Lorentzen</FONT>=20
      <BR><FONT size=3D2>&gt; &gt; </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
      size=3D2>&gt; =
_______________________________________________</FONT>=20
      <BR><FONT size=3D2>&gt; mmusic mailing list</FONT> <BR><FONT =
size=3D2>&gt;=20
      mmusic@ietf.org</FONT> <BR><FONT size=3D2>&gt; <A=20
      href=3D"https://www1.ietf.org/mailman/listinfo/mmusic"=20
      =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mmusic</A></FONT> =

      <BR><FONT size=3D2>&gt;=20
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0036_01C24370.FCF68E10--


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



From daemon@optimus.ietf.org  Wed Aug 14 20:48:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29281
	for <mmusic-archive@odin.ietf.org>; Wed, 14 Aug 2002 20:48:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA07731
	for mmusic-archive@odin.ietf.org; Wed, 14 Aug 2002 20:49:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA07614;
	Wed, 14 Aug 2002 20:46:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA07583
	for <mmusic@optimus.ietf.org>; Wed, 14 Aug 2002 20:46:13 -0400 (EDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29207
	for <mmusic@ietf.org>; Wed, 14 Aug 2002 20:44:54 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g7F0jg6I005581;
	Wed, 14 Aug 2002 17:45:42 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g7F0jq8v014520;
	Wed, 14 Aug 2002 17:45:52 -0700 (PDT)
Received: from RKUMARW2K (dhcp-128-107-142-101.cisco.com [128.107.142.101]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id RAA09977; Wed, 14 Aug 2002 17:45:40 -0700 (PDT)
Reply-To: <rkumar@cisco.com>
From: "Rajesh Kumar" <rkumar@cisco.com>
To: <mmusic@ietf.org>
Cc: <tr301@tiacomm.org>, <tsg16q11@itu.int>
Date: Wed, 14 Aug 2002 17:45:41 -0700
Message-ID: <HKENKJNMHBIBLCDGOHAFCEPHCFAA.rkumar@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Request for IANA 'gfmtp' registry
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Dear MMUSIC colleagues,

I have submitted  the following application to the IANA for a new registry
where subparameters of the 'gfmtp' SDP attribute  may be registered. This
parameter is defined in
http://search.ietf.org/internet-drafts/draft-rajeshkumar-mmusic-gfmtp-02.txt
and will, most likely, be part of the ITU V.150.1 modem relay standard.

The reason why 'gfmtp'  should not be registered simply as an SDP attribute
is that in the IANA SDP registry it is not possible to add sub-parameters of
the 'gfmtp'  attribute (such as vbd=on/off) in the same way as new
attributes can be added. The attribute 'fmtp' which is similar to 'gfmtp'
does not have this problem because its subparameters are covered under MIME
registrations.

Please advise, correct and guide.

Thanks,

Rajesh

 | -----Original Message-----
 | From: rkumar@cisco.com [mailto:rkumar@cisco.com]
 | Sent: Wednesday, August 14, 2002 5:07 PM
 | To: iana@iana.org; rkumar@cisco.com
 | Subject: General Request for Assignments
 |
 |
 | Contact Name :
 | Rajesh Kumar
 |
 | Contact Email :
 | rkumar@cisco.com
 |
 | Type of Assignment :
 | A new registry for the values of the SDP 'gfmtp' attribute. A
 | new registry is needed since new sub-parameters and their values
 | may be defined.
 |
 | Registry :
 | A new registry is needed since new sub-parameters and their
 | values may be defined. The SDP parameters registry allow the
 | additon of attributes that are statically defined in a standards
 | specification.
 |
 | Description :
 | There may be generic parameters (such as the boolean VBD) that
 | may be applied across the board to a number of formats, and are
 | not an integral part of the MIME definition of any particular
 | format. For these, the 'fmtp' attribute in RFC 2327 may not be
 | applied. A new SDP attribute, 'gfmtp' is defined for these, per
 | the recommendation of the IETF MMUSIC group. Since the
 | sub-parameters of the 'gfmtp' parameter are not part of any MIME
 | definition, a new registry is needed for vendors to define
 | sub-parameters for it in an interoperable manner.
 |
 | Additional Info :
 | draft-rajeshkumar-mmusic-gfmtp-02.txt defines the concept and
 | its history.
 | This parameter is being standardized in the ITU V.150
 | specification which addressed modem relay. Contact:Keith Chu,
 | Chairperson TIA TR-30.1, 949 579 4121 keith.chu@mindspeed.com
 |
 |


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



From daemon@optimus.ietf.org  Wed Aug 14 22:45:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02012
	for <mmusic-archive@odin.ietf.org>; Wed, 14 Aug 2002 22:45:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA13558
	for mmusic-archive@odin.ietf.org; Wed, 14 Aug 2002 22:47:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA13427;
	Wed, 14 Aug 2002 22:42:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA13396
	for <mmusic@optimus.ietf.org>; Wed, 14 Aug 2002 22:42:08 -0400 (EDT)
Received: from purple.nge.isi.edu (dial167.east.isi.edu [65.114.169.167])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01959
	for <mmusic@ietf.org>; Wed, 14 Aug 2002 22:40:47 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.5/8.12.5) with ESMTP id g7F2es0e045374;
	Wed, 14 Aug 2002 22:40:54 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200208150240.g7F2es0e045374@purple.nge.isi.edu>
To: rkumar@cisco.com
cc: mmusic@ietf.org, tr301@tiacomm.org, tsg16q11@itu.int, iana@iana.org
Subject: Re: [MMUSIC] Request for IANA 'gfmtp' registry 
In-Reply-To: Your message of "Wed, 14 Aug 2002 17:45:41 PDT."
             <HKENKJNMHBIBLCDGOHAFCEPHCFAA.rkumar@cisco.com> 
Date: Wed, 14 Aug 2002 22:40:54 -0400
From: Colin Perkins <csp@isi.edu>
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

Rajesh,

This request should be included as part of the "IANA Considerations"
section of draft-rajeshkumar-mmusic-gfmtp-02.txt draft, rather than 
being submitted separately. 

Colin Perkins
MMUSIC co-chair



--> "Rajesh Kumar" writes:
>Dear MMUSIC colleagues,
>
>I have submitted  the following application to the IANA for a new registry
>where subparameters of the 'gfmtp' SDP attribute  may be registered. This
>parameter is defined in
>http://search.ietf.org/internet-drafts/draft-rajeshkumar-mmusic-gfmtp-02.txt
>and will, most likely, be part of the ITU V.150.1 modem relay standard.
>
>The reason why 'gfmtp'  should not be registered simply as an SDP attribute
>is that in the IANA SDP registry it is not possible to add sub-parameters of
>the 'gfmtp'  attribute (such as vbd=on/off) in the same way as new
>attributes can be added. The attribute 'fmtp' which is similar to 'gfmtp'
>does not have this problem because its subparameters are covered under MIME
>registrations.
>
>Please advise, correct and guide.
>
>Thanks,
>
>Rajesh
>
> | -----Original Message-----
> | From: rkumar@cisco.com [mailto:rkumar@cisco.com]
> | Sent: Wednesday, August 14, 2002 5:07 PM
> | To: iana@iana.org; rkumar@cisco.com
> | Subject: General Request for Assignments
> |
> |
> | Contact Name :
> | Rajesh Kumar
> |
> | Contact Email :
> | rkumar@cisco.com
> |
> | Type of Assignment :
> | A new registry for the values of the SDP 'gfmtp' attribute. A
> | new registry is needed since new sub-parameters and their values
> | may be defined.
> |
> | Registry :
> | A new registry is needed since new sub-parameters and their
> | values may be defined. The SDP parameters registry allow the
> | additon of attributes that are statically defined in a standards
> | specification.
> |
> | Description :
> | There may be generic parameters (such as the boolean VBD) that
> | may be applied across the board to a number of formats, and are
> | not an integral part of the MIME definition of any particular
> | format. For these, the 'fmtp' attribute in RFC 2327 may not be
> | applied. A new SDP attribute, 'gfmtp' is defined for these, per
> | the recommendation of the IETF MMUSIC group. Since the
> | sub-parameters of the 'gfmtp' parameter are not part of any MIME
> | definition, a new registry is needed for vendors to define
> | sub-parameters for it in an interoperable manner.
> |
> | Additional Info :
> | draft-rajeshkumar-mmusic-gfmtp-02.txt defines the concept and
> | its history.
> | This parameter is being standardized in the ITU V.150
> | specification which addressed modem relay. Contact:Keith Chu,
> | Chairperson TIA TR-30.1, 949 579 4121 keith.chu@mindspeed.com
> |
> |
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic

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



From daemon@optimus.ietf.org  Fri Aug 16 15:04:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28359
	for <mmusic-archive@odin.ietf.org>; Fri, 16 Aug 2002 15:04:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA22583
	for mmusic-archive@odin.ietf.org; Fri, 16 Aug 2002 15:05:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA22528;
	Fri, 16 Aug 2002 15:03:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA22497
	for <mmusic@optimus.ietf.org>; Fri, 16 Aug 2002 15:03:15 -0400 (EDT)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28280
	for <mmusic@ietf.org>; Fri, 16 Aug 2002 15:01:53 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g7GJ2GI15153;
	Fri, 16 Aug 2002 14:02:17 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KKXYTHK9>; Fri, 16 Aug 2002 14:02:02 -0500
Message-ID: <933FADF5E673D411B8A30002A5608A0E03A63462@zrc2c012.us.nortel.com>
From: "Sanjoy Sen" <sanjoy@nortelnetworks.com>
To: "'Andreas Kassler'" <kassler@informatik.uni-ulm.de>,
        "Even, Roni"
	 <roni.even@polycom.co.il>,
        "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Fri, 16 Aug 2002 14:02:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C24557.665A2410"
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org

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

------_=_NextPart_001_01C24557.665A2410
Content-Type: text/plain

Its meant to be a signal to the endpoint what level of quality the receiver
is willing to receive, so that the transmitter can act accordingly (like
adapt the quantization rate, mark the DS code point etc.). Separate profiles
need to specify these parameter values (for each QoS level) for each
supported codec type. 
 
 
-Sanjoy

-----Original Message-----
From: Andreas Kassler [mailto:kassler@informatik.uni-ulm.de] 
Sent: Wednesday, August 14, 2002 2:00 AM
To: Even, Roni; Sen, Sanjoy [NGC:B677:EXCH]; 'Nils Henrik Lorentzen';
mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft


Hi,
regarding the visual quality, I was targeting more to variable bitrate
codecs, where you can change
the visual quality (e.g. by changing the quantization) independent from the
frame size and the frame
rate. Of course this may result in a change of the data rate, which may lead
to a renegotiation for
network resources (using RSVP updates or to be defined NSIS signalling).
When you think about constant bitrate codecs I absolutely agree with you
that we need some preferences:
- e.g. frame rate is more important than visual quality
We could use here e.g. some weighting factors and it is up to the codec to
configure itself correctly.
For the "frame rate is more important than visual quality" scenario, we
could have something like 
- frame_rate = 70, visual_quality = 30
For the "frame rate is equally important as visual quality" scenario, we
could have something like 
- frame_rate = 50, visual_quality = 50, and so on.
What do you think?
Regards, Andreas.

----- Original Message ----- 
From: Even,  <mailto:roni.even@polycom.co.il> Roni 
To: 'Andreas Kassler' <mailto:kassler@informatik.uni-ulm.de>  ; Sanjoy Sen
<mailto:sanjoy@nortelnetworks.com>  ; Even,
<mailto:roni.even@polycom.co.il> Roni ; 'Nils  <mailto:nhl@tandberg.no>
Henrik Lorentzen' ; mmusic@ietf.org <mailto:mmusic@ietf.org>  
Sent: Wednesday, August 14, 2002 8:35 AM
Subject: RE: [MMUSIC] video media control draft

Hi,
I understand the need for asking for frame rate and frame size since these
are absolute numbers and that is why we have the media control draft and I
will add the support for per payload type.
As for the quality how do you define that in absolute terms, isn't it
something that is an application or codec specific. Is someone using the
quality attribute in SDP and if yes what are the user expectations when he
ask for higher quality comparing to lower quality.How does the encoder use
this parameter, one way to get "high quality" is by reducing the frame rate
or resolution at the same line rate but this can be controlled by those
attributes. At least in this case the receiver can say what he is willing to
scarifies (frame rate or resolution) to get higher quality
Thanks
Roni Even


 
 
 -----Original Message-----
From: Andreas Kassler [mailto:kassler@informatik.uni-ulm.de]
Sent: Tuesday, August 13, 2002 10:49 AM
To: Sanjoy Sen; 'Even, Roni'; 'Nils Henrik Lorentzen'; mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft



Sanjoy et al,
we were also concerned about the expressability of quality attributes that
defines the quality of service at application level for a given video(audio)
stream. 
In draft-guenkova-mmusic-e2enp-sdpng-00.txt we basically have identified a
requirement
to ... introduce (per) codec parametrization attributes like frame-rate,
frame-size, color-
quality-range, overall-quality-range, etc. which should be  uniquely
interpreted by the end-systems.
 
When it comes to negotiation of such attributes with the peer for setting up
quality enhanced
media streams, we propose to specify such parameters on a per codec basis.
The reason is 
that not all codecs support all combinations of such parameters. For example
with a given
hardware, a sender may be able to compress at 25 fps at CIF a H.261 stream
but may
not be able to compress at 25 fps at CIF a MPEG-4 stream due to limited
resources.
 
We propose also to work on these issues within the SDPng context.
 
-Andreas

----- Original Message ----- 
From: Sanjoy Sen <mailto:sanjoy@nortelnetworks.com>  
To: 'Even, Roni' <mailto:roni.even@polycom.co.il>  ; 'Nils Henrik
<mailto:nhl@tandberg.no> Lorentzen' ; mmusic@ietf.org
<mailto:mmusic@ietf.org>  
Sent: Tuesday, August 13, 2002 1:55 AM
Subject: RE: [MMUSIC] video media control draft



I saw this pretty old thread. I do support proposing frame-size on a per
codec (payload-type) basis. I would also like to throw in the requirement
that we need to be able to specify the preferred media qualities (e.g., in a
scale of 0-10) per payload-type (right now SDP defines a quality attribute
per m line). Thoughts?

Does it make sense to encode all these information as part of an "fmtp"
attribute for the payload-type? - e.g., a:fmtp:<PT> res=QCIF/quality=5

-Sanjoy 

> -----Original Message----- 
> From: Even, Roni [mailto:roni.even@polycom.co.il
<mailto:roni.even@polycom.co.il> ] 
> Sent: Wednesday, August 07, 2002 1:21 AM 
> To: 'Nils Henrik Lorentzen'; mmusic@ietf.org; Even, Roni 
> Subject: RE: [MMUSIC] video media control draft 
> 
> 
> Nils, 
> I think your suggestion makes sense. I will update the draft Roni 
> 
> > -----Original Message----- 
> > From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no
<mailto:nhl@tandberg.no> ] 
> > Sent: Tuesday, August 06, 2002 10:35 AM 
> > To: mmusic@ietf.org; Even, Roni 
> > Subject: Re: [MMUSIC] video media control draft 
> > 
> > 
> > On Tuesday 06 August 2002 07:59, Even, Roni wrote: 
> > 
> > > Hi Petri, 
> > > In my draft draft-even-mmusic-video-media-control-00.txt, 
> I have a 
> > > video-resolution attribute that allow to specify the 
> > maximum frame rate 
> > > supported per resolution. 
> > 
> > A difference between your draft and 
> > draft-koskelainen-sdp263-02.txt is that 
> > in the latter you may specify resolutions and options per 
> > payload type, 
> > instead of per media line. I think this is more flexible, and 
> > would suit our 
> > needs better. Any particular reason for having it per media-line ? 
> > 
> > In your draft it would be a simple change to make it per payload: 
> > a=video-resolution:<size> to 
> > a=video-resolution: <payload no> <size> 
> > or possibly 
> > a=video-resolution: [ PT=<payload no>] <size> 
> > ie payload no is optional, so if not specified the 
> > resolutions would apply to 
> > all the payload types on the media line. 
> > 
> > > In the meeting this attribute was accepted for 
> > > SDP. I could not find the draft mentioned 
> > "draft-koskelainen-sdp263-02.txt" 
> > 
> > It expired quite some time ago, but can be found at: 
> > http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai
<http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai>  
> > nen-sdp263-02.txt 
> > 
> > Nils Henrik Lorentzen 
> > 
> 
> _______________________________________________ 
> mmusic mailing list 
> mmusic@ietf.org 
> https://www1.ietf.org/mailman/listinfo/mmusic
<https://www1.ietf.org/mailman/listinfo/mmusic>  
> 


------_=_NextPart_001_01C24557.665A2410
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 5.50.4913.1100" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=705265518-16082002><FONT face="Courier New" color=#0000ff 
size=2>Its meant to be a signal to the endpoint what level of quality the 
receiver is willing to receive, so that the transmitter can act accordingly 
(like adapt the quantization rate, mark the DS code point etc.). Separate 
profiles&nbsp;need to&nbsp;specify&nbsp;these parameter values&nbsp;(for each 
QoS level) for each supported codec type. </FONT></SPAN></DIV>
<DIV><SPAN class=705265518-16082002><FONT face="Courier New" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=705265518-16082002><FONT face="Courier New" color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=705265518-16082002><FONT face="Courier New" color=#0000ff 
size=2>-Sanjoy</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Andreas Kassler 
  [mailto:kassler@informatik.uni-ulm.de] <BR><B>Sent:</B> Wednesday, August 14, 
  2002 2:00 AM<BR><B>To:</B> Even, Roni; Sen, Sanjoy [NGC:B677:EXCH]; 'Nils 
  Henrik Lorentzen'; mmusic@ietf.org<BR><B>Subject:</B> Re: [MMUSIC] video media 
  control draft<BR><BR></FONT></DIV>
  <DIV>
  <DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
  <DIV><FONT face=Arial size=2>regarding the visual quality, I was targeting 
  more to variable bitrate codecs, where you can change</FONT></DIV>
  <DIV><FONT face=Arial size=2>the visual quality (e.g. by changing the 
  quantization) independent from the frame size and the frame</FONT></DIV>
  <DIV><FONT face=Arial size=2>rate. Of course this may result in a change of 
  the data rate, which may lead to a renegotiation for</FONT></DIV>
  <DIV><FONT face=Arial size=2>network resources (using RSVP updates or to be 
  defined NSIS signalling).</FONT></DIV>
  <DIV><FONT face=Arial size=2>When you think about constant bitrate codecs I 
  absolutely agree with you that we need some preferences:</FONT></DIV>
  <DIV><FONT face=Arial size=2>- e.g. frame rate is more important than visual 
  quality</FONT></DIV>
  <DIV><FONT face=Arial size=2>We could use here e.g. some weighting factors and 
  it is up to the codec to configure itself correctly.</FONT></DIV>
  <DIV><FONT face=Arial size=2>For the "frame rate is more important than visual 
  quality" scenario, we could have something like </FONT></DIV>
  <DIV><FONT face=Arial size=2>- frame_rate = 70, visual_quality = 
  30</FONT></DIV>
  <DIV>
  <DIV><FONT face=Arial size=2>For the "frame rate is&nbsp;equally 
  important&nbsp;as visual quality" scenario, we could have something like 
  </FONT></DIV>
  <DIV><FONT face=Arial size=2>- frame_rate = 50, visual_quality = 50, and so 
  on.</FONT></DIV>
  <DIV><FONT face=Arial size=2>What do you think?</FONT></DIV></DIV>
  <DIV><FONT face=Arial size=2>Regards, Andreas.</FONT></DIV></DIV>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=roni.even@polycom.co.il href="mailto:roni.even@polycom.co.il">Even, 
    Roni</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A 
    title=kassler@informatik.uni-ulm.de 
    href="mailto:kassler@informatik.uni-ulm.de">'Andreas Kassler'</A> ; <A 
    title=sanjoy@nortelnetworks.com 
    href="mailto:sanjoy@nortelnetworks.com">Sanjoy Sen</A> ; <A 
    title=roni.even@polycom.co.il href="mailto:roni.even@polycom.co.il">Even, 
    Roni</A> ; <A title=nhl@tandberg.no href="mailto:nhl@tandberg.no">'Nils 
    Henrik Lorentzen'</A> ; <A title=mmusic@ietf.org 
    href="mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, August 14, 2002 8:35 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video media 
    control draft</DIV>
    <DIV><BR></DIV>
    <DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff 
    size=2>Hi,</FONT></SPAN></DIV>
    <DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff size=2>I 
    understand the need for asking for frame rate and frame size since these are 
    absolute numbers and that is why we have the media control draft and I will 
    add the support for per payload type.</FONT></SPAN></DIV>
    <DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff size=2>As 
    for the quality how do you define that in absolute terms, isn't it something 
    that is an application or codec specific. Is someone using the quality 
    attribute in SDP and if yes what are the user expectations when he ask for 
    higher quality comparing to lower quality.How does the encoder use this 
    parameter, one way to get "high quality" is by reducing the frame rate or 
    resolution at the same line rate but this can be controlled by those 
    attributes. At least in this case the receiver can say what he is willing to 
    scarifies (frame rate or resolution) to get higher 
    quality</FONT></SPAN></DIV>
    <DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff 
    size=2>Thanks</FONT></SPAN></DIV>
    <DIV><SPAN class=223252506-14082002><FONT face=Arial color=#0000ff 
    size=2>Roni Even</FONT></SPAN></DIV><SPAN 
    class=223252506-14082002></SPAN><FONT face=Tahoma>
    <DIV><BR><FONT size=2><SPAN class=223252506-14082002><FONT face=Arial 
    color=#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
    <DIV><FONT size=2><SPAN class=223252506-14082002></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=2><SPAN class=223252506-14082002>&nbsp;</SPAN>-----Original 
    Message-----<BR><B>From:</B> Andreas Kassler 
    [mailto:kassler@informatik.uni-ulm.de]<BR><B>Sent:</B> Tuesday, August 13, 
    2002 10:49 AM<BR><B>To:</B> Sanjoy Sen; 'Even, Roni'; 'Nils Henrik 
    Lorentzen'; mmusic@ietf.org<BR><B>Subject:</B> Re: [MMUSIC] video media 
    control draft<BR><BR></DIV></FONT></FONT>
    <BLOCKQUOTE dir=ltr 
    style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
      <DIV><FONT face=Arial size=2>Sanjoy et al,</FONT></DIV>
      <DIV><FONT face=Arial size=2>we were also concerned about the 
      expressability of quality attributes that</FONT></DIV>
      <DIV><FONT face=Arial size=2>defines the quality of service at application 
      level for a given video(audio) stream. </FONT></DIV>
      <DIV><FONT face=Arial size=2>In draft-guenkova-mmusic-e2enp-sdpng-00.txt 
      we basically have identified a requirement</FONT></DIV>
      <DIV><FONT face=Arial size=2>to&nbsp;...</FONT><FONT face=Arial size=2> 
      introduce (per) codec&nbsp;parametrization attributes like frame-rate, 
      frame-size, color-<BR>quality-range, overall-quality-range, etc. which 
      should be&nbsp;&nbsp;uniquely interpreted by the end-systems.</FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>When it comes to negotiation of such 
      attributes with the peer for setting up quality enhanced</FONT></DIV>
      <DIV><FONT face=Arial size=2>media streams, we propose to specify such 
      parameters on a per codec basis. The reason is </FONT></DIV>
      <DIV><FONT face=Arial size=2>that not all codecs support all combinations 
      of such parameters. For example with a given</FONT></DIV>
      <DIV><FONT face=Arial size=2>hardware, a sender may be able to compress at 
      25 fps at CIF a H.261&nbsp;stream but may</FONT></DIV>
      <DIV><FONT face=Arial size=2>not be able to compress at 25 fps at CIF a 
      MPEG-4 stream due to limited resources.</FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>We propose also to work on these issues 
      within the SDPng context.</FONT></DIV>
      <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2>-Andreas</FONT></DIV>
      <BLOCKQUOTE dir=ltr 
      style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
        <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
        <DIV 
        style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
        <A title=sanjoy@nortelnetworks.com 
        href="mailto:sanjoy@nortelnetworks.com">Sanjoy Sen</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>To:</B> <A 
        title=roni.even@polycom.co.il 
        href="mailto:roni.even@polycom.co.il">'Even, Roni'</A> ; <A 
        title=nhl@tandberg.no href="mailto:nhl@tandberg.no">'Nils Henrik 
        Lorentzen'</A> ; <A title=mmusic@ietf.org 
        href="mailto:mmusic@ietf.org">mmusic@ietf.org</A> </DIV>
        <DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, August 13, 2002 1:55 
        AM</DIV>
        <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [MMUSIC] video media 
        control draft</DIV>
        <DIV><FONT face=Arial size=2></FONT><FONT face=Arial 
        size=2></FONT><BR></DIV>
        <P><FONT size=2>I saw this pretty old thread. I do support proposing 
        frame-size on a per codec (payload-type) basis. I would also like to 
        throw in the requirement that we need to be able to specify the 
        preferred media qualities (e.g., in a scale of 0-10) per payload-type 
        (right now SDP defines a quality attribute per m line). 
        Thoughts?</FONT></P>
        <P><FONT size=2>Does it make sense to encode all these information as 
        part of an "fmtp" attribute for the payload-type? - e.g., 
        a:fmtp:&lt;PT&gt; res=QCIF/quality=5</FONT></P>
        <P><FONT size=2>-Sanjoy</FONT> </P>
        <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT 
        size=2>&gt; From: Even, Roni [<A 
        href="mailto:roni.even@polycom.co.il">mailto:roni.even@polycom.co.il</A>] 
        </FONT><BR><FONT size=2>&gt; Sent: Wednesday, August 07, 2002 1:21 
        AM</FONT> <BR><FONT size=2>&gt; To: 'Nils Henrik Lorentzen'; 
        mmusic@ietf.org; Even, Roni</FONT> <BR><FONT size=2>&gt; Subject: RE: 
        [MMUSIC] video media control draft</FONT> <BR><FONT size=2>&gt; 
        </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Nils,</FONT> 
        <BR><FONT size=2>&gt; I think your suggestion makes sense. I will update 
        the draft Roni</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
        &gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: 
        Nils Henrik Lorentzen [<A 
        href="mailto:nhl@tandberg.no">mailto:nhl@tandberg.no</A>]</FONT> 
        <BR><FONT size=2>&gt; &gt; Sent: Tuesday, August 06, 2002 10:35 
        AM</FONT> <BR><FONT size=2>&gt; &gt; To: mmusic@ietf.org; Even, 
        Roni</FONT> <BR><FONT size=2>&gt; &gt; Subject: Re: [MMUSIC] video media 
        control draft</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
        size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; On Tuesday 06 August 
        2002 07:59, Even, Roni wrote:</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; &gt; Hi Petri,</FONT> <BR><FONT 
        size=2>&gt; &gt; &gt; In my draft 
        draft-even-mmusic-video-media-control-00.txt, </FONT><BR><FONT 
        size=2>&gt; I have a </FONT><BR><FONT size=2>&gt; &gt; &gt; 
        video-resolution attribute that allow to specify the</FONT> <BR><FONT 
        size=2>&gt; &gt; maximum frame rate</FONT> <BR><FONT size=2>&gt; &gt; 
        &gt; supported per resolution.</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; A difference between your draft 
        and</FONT> <BR><FONT size=2>&gt; &gt; draft-koskelainen-sdp263-02.txt is 
        that </FONT><BR><FONT size=2>&gt; &gt; in the latter you may specify 
        resolutions and options per </FONT><BR><FONT size=2>&gt; &gt; payload 
        type, </FONT><BR><FONT size=2>&gt; &gt; instead of per media line. I 
        think this is more flexible, and </FONT><BR><FONT size=2>&gt; &gt; would 
        suit our </FONT><BR><FONT size=2>&gt; &gt; needs better. Any particular 
        reason for having it per media-line ?</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; In your draft it would be a simple 
        change to make it per payload: </FONT><BR><FONT size=2>&gt; &gt; 
        a=video-resolution:&lt;size&gt; to</FONT> <BR><FONT size=2>&gt; &gt; 
        a=video-resolution: &lt;payload no&gt; &lt;size&gt;</FONT> <BR><FONT 
        size=2>&gt; &gt; or possibly</FONT> <BR><FONT size=2>&gt; &gt; 
        a=video-resolution: [ PT=&lt;payload no&gt;] &lt;size&gt;</FONT> 
        <BR><FONT size=2>&gt; &gt; ie payload no is optional, so if not 
        specified the </FONT><BR><FONT size=2>&gt; &gt; resolutions would apply 
        to </FONT><BR><FONT size=2>&gt; &gt; all the payload types on the media 
        line.</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
        &gt; &gt; In the meeting this attribute was accepted for</FONT> 
        <BR><FONT size=2>&gt; &gt; &gt; SDP. I could not find the draft 
        mentioned</FONT> <BR><FONT size=2>&gt; &gt; 
        "draft-koskelainen-sdp263-02.txt"</FONT> <BR><FONT size=2>&gt; &gt; 
        </FONT><BR><FONT size=2>&gt; &gt; It expired quite some time ago, but 
        can be found at: </FONT><BR><FONT size=2>&gt; &gt; <A target=_blank 
        href="http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai">http://www.dmn.tzi.org/ietf/mmusic/sdp-ng/input/draft-koskelai</A></FONT> 
        <BR><FONT size=2>&gt; &gt; nen-sdp263-02.txt</FONT> <BR><FONT 
        size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; Nils Henrik 
        Lorentzen</FONT> <BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
        </FONT><BR><FONT size=2>&gt; 
        _______________________________________________</FONT> <BR><FONT 
        size=2>&gt; mmusic mailing list</FONT> <BR><FONT size=2>&gt; 
        mmusic@ietf.org</FONT> <BR><FONT size=2>&gt; <A target=_blank 
        href="https://www1.ietf.org/mailman/listinfo/mmusic">https://www1.ietf.org/mailman/listinfo/mmusic</A></FONT> 
        <BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C24557.665A2410--

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



From daemon@optimus.ietf.org  Mon Aug 19 08:19:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29546
	for <mmusic-archive@odin.ietf.org>; Mon, 19 Aug 2002 08:19:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA15603
	for mmusic-archive@odin.ietf.org; Mon, 19 Aug 2002 08:21:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15491;
	Mon, 19 Aug 2002 08:16:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15459
	for <mmusic@optimus.ietf.org>; Mon, 19 Aug 2002 08:16:22 -0400 (EDT)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29492
	for <mmusic@ietf.org>; Mon, 19 Aug 2002 08:14:57 -0400 (EDT)
Received: from tzi.uni-bremen.de (root@localhost [127.0.0.1])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g7JCFwv23179;
	Mon, 19 Aug 2002 14:15:58 +0200 (MEST)
Message-ID: <3D609335.6060009@tzi.uni-bremen.de>
Date: Mon, 19 Aug 2002 08:41:57 +0200
From: Joerg Ott <jo@tzi.uni-bremen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Nils Henrik Lorentzen <nhl@tandberg.no>
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft
References: <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3> <3D4FC0B5.25445F81@tzi.uni-bremen.de> <200208070736.g777aPu27650@prix.tandberg.no>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
X-BeenThere: mmusic@ietf.org
Content-Transfer-Encoding: 7bit

Looks like I haven't responded to this one yet:

 >>>As for SIP, are you stirring us to a INFO based solution , I am not aware
 >>>of other existing solution
 >>>
 >>I hope that I did not convey this impression.  I would like to keep you
 >>away
 >>from INFO as far as possible.  In my opinion, INFO should be treated as if
 >>it
 >>were non-existent.
 >>
 >
 > Out of curiosity, what do you think is wrong with INFO ? Is it too much 
of a
 > generic "contain anything that does not fit elsewhere" message ?

This is essentially the point.  It is ill-defined.  SIP is a signaling
protocol intended to create, modify, and delete session state.  SIP INFO
has been invented to transparently carry ISUP data end-to-end in case of
SS7 trunking via SIP.  Other uses have been envisioned but have been
abandoned one by one.  As INFO does not specify semantics, handling of
forking is not defined; congestion control is not applied (not even
warned about in the spec), for example.

This essentially turns SIP into a transport protocol which is
probably one of the most inefficient uses one can imagine.
SIP INFO has no defined semantics besides "carry this byte bucket
to the other side".

In ISUP, the intend is to simply forward the data (unprocessed) to
the PSTN (INFO explicitly states that call state MUST NOT be altered
based upon the contained message body).  It has been repeatedly
discussed, however, that entities may actually look at the payload and
take some actions according to the contents (which would be bad by
itself  because it contradicts the idea of transparent end-to-end
carriage).  Either you specify syntax and semantics in SIP -- then
your endpoints and intermediaries may use it -- or you don't --
then they better don't touch it at all.  So far for the potential
flaws of INFO in the ISUP context.

In other cases, SIP INFO is just semantics-free by itself and invites
(mis)use by and for evertything.  But, at least arrive at a common
understanding and thus achieve interoperability, protocol elements
must have a well-defined meaning by themselves rather than requiring
this to be implied from the message body (or a header).

Joerg




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



From mailnull@www1.ietf.org  Thu Aug 22 15:15:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07174
	for <mmusic-archive@odin.ietf.org>; Thu, 22 Aug 2002 15:15:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7MJG3B12204
	for mmusic-archive@odin.ietf.org; Thu, 22 Aug 2002 15:16:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MJG3o12201
	for <mmusic-web-archive@optimus.ietf.org>; Thu, 22 Aug 2002 15:16:03 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07163
	for <mmusic-web-archive@ietf.org>; Thu, 22 Aug 2002 15:14:33 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MJFQo12151;
	Thu, 22 Aug 2002 15:15:26 -0400
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14538
	for <mmusic@optimus.ietf.org>; Tue, 20 Aug 2002 11:09:24 -0400 (EDT)
Received: from brixcorp2.brixnet.com ([63.122.27.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16872
	for <mmusic@ietf.org>; Tue, 20 Aug 2002 11:08:00 -0400 (EDT)
Received: by mail.brixnet.com with Internet Mail Service (5.5.2656.59)
	id <PV4TJ2L0>; Tue, 20 Aug 2002 11:08:44 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB01E49F6C@mail.brixnet.com>
From: "Venna, Nagarjuna" <nvenna@Brixnet.com>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Cc: "Venna, Nagarjuna" <nvenna@Brixnet.com>
Date: Tue, 20 Aug 2002 11:08:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [MMUSIC] Issues with disambiguating RTCP RR by a RTSP Server
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>

This mail is a follow-up on a discussion I had with Darwin Streaming Server
developers on the DSS mailing list. 

Background:

DSS implements a timeout mechanism to drop RTSP sessions if a client appears
to be dead. A client is deemed to be "alive" if it has sent a RTCP Reception
Report in the past n seconds (I believe n is about 100 secs). When the
server is streaming a live session, DSS uses a single port pair for media
and control packets for all clients and expects to receive RTCP RR on that
port (specified as part of "server_port" in Transport Header of SETUP
response). DSS uses the source address/source port of the RTCP packet to
identify the client and update its status tables. 

Issues:

My understanding of an RTP session (Section 3 and Section 5.2 of RFC 1889)
is that it is entirely determined by the destination address and destination
port. Source Port should not matter when looking at an RTP packet. The above
strategy used by DSS has problems with multicast sessions because the client
has to come with a control packet whose source port is actually chosen by
the server. In addition, the "client_port" parameter in the Transport header
of a RTSP SETUP message only specifies where the client is willing to
receive media and control data. The spec does not say anything about where
the client is going to send its control data from.

Looking at the client SSRC should be the correct solution. As the clients do
not send any media packets, the server has no way of knowing what the SSRC
is. There is also no guarantee that the SSRC across clients is going to be
unique. So, the larger question is how does a server identify who it is
receiving a RTCP report from when it does not receive any media packets.

I do not know of a good way to solve this problem. Please let me know if I'm
missing something. If not, a possible solution follows.

Possible Solution:

The only way to guarantee SSRC's that the clients use in RTCP will be unique
is to let the server generate them and tell the clients during session
setup. I would think the right place is to send "client_ssrc" in the
RTP-Info header of the PLAY response from the server. 

The server SSRC is sent to the client in the Transport header of SETUP
response. I'm not really sure why it is here instead of in the RTP-Info
Header in the PLAY response. If there is a good reason to do this, then the
"client_ssrc" header can also be sent in the SETUP response.

Thanks,
nagarjuna


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



From mailnull@www1.ietf.org  Thu Aug 22 15:15:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07187
	for <mmusic-archive@odin.ietf.org>; Thu, 22 Aug 2002 15:15:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7MJG3712219
	for mmusic-archive@odin.ietf.org; Thu, 22 Aug 2002 15:16:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MJG3o12216
	for <mmusic-web-archive@optimus.ietf.org>; Thu, 22 Aug 2002 15:16:03 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07166
	for <mmusic-web-archive@ietf.org>; Thu, 22 Aug 2002 15:14:34 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MJFSo12167;
	Thu, 22 Aug 2002 15:15:28 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by optimus.ietf.org (8.11.6/8.11.6) with ESMTP id g7LM6DW11676
	for <mmusic@optimus.ietf.org>; Wed, 21 Aug 2002 18:06:13 -0400
Received: from brixcorp2.brixnet.com ([63.122.27.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27354
	for <mmusic@ietf.org>; Wed, 21 Aug 2002 18:04:42 -0400 (EDT)
Received: by mail.brixnet.com with Internet Mail Service (5.5.2656.59)
	id <PV4TJLFL>; Wed, 21 Aug 2002 18:05:31 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB01E49F77@mail.brixnet.com>
From: "Venna, Nagarjuna" <nvenna@Brixnet.com>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Date: Wed, 21 Aug 2002 18:05:27 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [MMUSIC] Issues with disambiguating RTCP RR by a RTSP Server
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>

This mail is a follow-up on a discussion I had with Darwin Streaming Server
developers on the DSS mailing list. 

Background:

DSS implements a timeout mechanism to drop RTSP sessions if a client appears
to be dead. A client is deemed to be "alive" if it has sent a RTCP Reception
Report in the past n seconds (I believe n is about 100 secs). When the
server is streaming a live session, DSS uses a single port pair for media
and control packets for all clients and expects to receive RTCP RR on that
port (specified as part of "server_port" in Transport Header of SETUP
response). DSS uses the source address/source port of the RTCP packet to
identify the client and update its status tables. 

Issues:

My understanding of an RTP session (Section 3 and Section 5.2 of RFC 1889)
is that it is entirely determined by the destination address and destination
port. Source Port should not matter when looking at an RTP packet. The above
strategy used by DSS has problems with multicast sessions because the client
has to come with a control packet whose source port is actually chosen by
the server. In addition, the "client_port" parameter in the Transport header
of a RTSP SETUP message only specifies where the client is willing to
receive media and control data. The spec does not say anything about where
the client is going to send its control data from.

Looking at the client SSRC should be the correct solution. As the clients do
not send any media packets, the server has no way of knowing what the SSRC
is. There is also no guarantee that the SSRC across clients is going to be
unique. So, the larger question is how does a server identify who it is
receiving a RTCP report from when it does not receive any media packets.

I do not know of a good way to solve this problem. Please let me know if I'm
missing something. If not, a possible solution follows.

Possible Solution:

The only way to guarantee SSRC's that the clients use in RTCP will be unique
is to let the server generate them and tell the clients during session
setup. I would think the right place is to send "client_ssrc" in the
RTP-Info header of the PLAY response from the server. 

The server SSRC is sent to the client in the Transport header of SETUP
response. I'm not really sure why it is here instead of in the RTP-Info
Header in the PLAY response. If there is a good reason to do this, then the
"client_ssrc" header can also be sent in the SETUP response.

Thanks,
nagarjuna

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



From mailnull@www1.ietf.org  Thu Aug 22 21:53:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15987
	for <mmusic-archive@odin.ietf.org>; Thu, 22 Aug 2002 21:53:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7N1sNH32483
	for mmusic-archive@odin.ietf.org; Thu, 22 Aug 2002 21:54:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N1sNo32480
	for <mmusic-web-archive@optimus.ietf.org>; Thu, 22 Aug 2002 21:54:23 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15965
	for <mmusic-web-archive@ietf.org>; Thu, 22 Aug 2002 21:52:50 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N1rho32463;
	Thu, 22 Aug 2002 21:53:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N1pZo32391
	for <mmusic@optimus.ietf.org>; Thu, 22 Aug 2002 21:51:35 -0400
Received: from gumby.cs.berkeley.edu (IDENT:root@gumby.CS.Berkeley.EDU [128.32.36.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15920;
	Thu, 22 Aug 2002 21:50:01 -0400 (EDT)
Received: from BMRC.Berkeley.EDU (opus.CS.Berkeley.EDU [128.32.168.232])
	by gumby.cs.berkeley.edu (8.11.6/8.9.3) with ESMTP id g7N1pQt22631;
	Thu, 22 Aug 2002 18:51:26 -0700
Message-ID: <3D65951E.637E3E74@BMRC.Berkeley.EDU>
Date: Thu, 22 Aug 2002 18:51:26 -0700
From: "Lawrence A. Rowe" <Rowe@BMRC.Berkeley.EDU>
Reply-To: Rowe@BMRC.Berkeley.EDU
Organization: U.C. Berkeley
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: avt@ietf.org, mmusic@ietf.org, wg-multicast@internet2.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] The Berkeley MIG Seminar returns!
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-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-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi -

I have returned from sabbatical and will be offering the Berkeley MIG
Seminar webcasts again this year.  I have already lined up some exciting
speakers, and I have several more people who are trying to arrange a
date. The current list of speakers is on the seminar webpage
	http://bmrc.berkeley.edu/bibs/archive?prog=1&group=25

We will be webcasting the seminars using a variety of technologies
including the Internet Mbone (using our AG virtual room), Real Networks,
an Ncast Telepresenter (MPEG1), and RTPtv.  More details on these
technologies and the software needed to play them will be posted on
the seminar webpage.

The first seminar is next Wednesday, August 28th, at which I will give
my traditional introduction to the seminar. I will also present some 
examples ofthe software we have been developing in the past 6-8 months
to simplify the development of media streaming control and automation
applications. More details are on the website.

The seminar will be announced through the usual publicity channels (e.g.
U Oregon, AG, sdr, etc.), but this will be the only announcement to
these
IETF and Internet2 mailing lists. If you want to continue to receive
these announcements, send me email and I will add you to the local
announcement list I use. The list is moderated, so the only mail you
will receive from me will be the seminar annoucements.

I am excited to be doing the seminar again.  We webcst this event for 7
years before I took sabbatical.  I hope this year will be another
exciting series.

Best wishes,
	Larry Rowe 
-- 
Professor Lawrence A. Rowe          Internet:  Rowe@BMRC.Berkeley.EDU
Computer Science Division - EECS       Phone: 510-642-5117
University of California, Berkeley       Fax: 510-642-5615
Berkeley, CA 94720-1776            URL: http://bmrc.berkeley.edu/~larry
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



From mailnull@www1.ietf.org  Fri Aug 23 04:32:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01245
	for <mmusic-archive@odin.ietf.org>; Fri, 23 Aug 2002 04:32:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7N8Xk225792
	for mmusic-archive@odin.ietf.org; Fri, 23 Aug 2002 04:33:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N8Xjo25789
	for <mmusic-web-archive@optimus.ietf.org>; Fri, 23 Aug 2002 04:33:45 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01226
	for <mmusic-web-archive@ietf.org>; Fri, 23 Aug 2002 04:32:09 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N8X9o25756;
	Fri, 23 Aug 2002 04:33:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7N8WIo25737
	for <mmusic@optimus.ietf.org>; Fri, 23 Aug 2002 04:32:18 -0400
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01195
	for <mmusic@ietf.org>; Fri, 23 Aug 2002 04:30:41 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g7N8W4Rb011225;
	Fri, 23 Aug 2002 10:32:04 +0200 (MEST)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.65]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id RNFV6R9C; Fri, 23 Aug 2002 10:32:04 +0200
Message-ID: <3D65F304.1050604@era.ericsson.se>
Date: Fri, 23 Aug 2002 10:32:04 +0200
X-Sybari-Trust: 6fd34ddf 9c5d1ec5 900170aa 00000138
From: Magnus Westerlund <magnus.westerlund@era.ericsson.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Venna, Nagarjuna" <nvenna@Brixnet.com>
CC: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Issues with disambiguating RTCP RR by a RTSP Server
References: <07B0D4912B83D31188F300A0C9F62EBB01E49F77@mail.brixnet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-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-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi, Nagarjuna

See comments below.

Venna, Nagarjuna wrote:

>This mail is a follow-up on a discussion I had with Darwin Streaming Server
>developers on the DSS mailing list. 
>
>Background:
>
>DSS implements a timeout mechanism to drop RTSP sessions if a client appears
>to be dead. A client is deemed to be "alive" if it has sent a RTCP Reception
>Report in the past n seconds (I believe n is about 100 secs). When the
>server is streaming a live session, DSS uses a single port pair for media
>and control packets for all clients and expects to receive RTCP RR on that
>port (specified as part of "server_port" in Transport Header of SETUP
>response). DSS uses the source address/source port of the RTCP packet to
>identify the client and update its status tables. 
>
>Issues:
>
>My understanding of an RTP session (Section 3 and Section 5.2 of RFC 1889)
>is that it is entirely determined by the destination address and destination
>port. Source Port should not matter when looking at an RTP packet. The above
>strategy used by DSS has problems with multicast sessions because the client
>has to come with a control packet whose source port is actually chosen by
>the server. In addition, the "client_port" parameter in the Transport header
>of a RTSP SETUP message only specifies where the client is willing to
>receive media and control data. The spec does not say anything about where
>the client is going to send its control data from.
>
>
>Looking at the client SSRC should be the correct solution. As the clients do
>not send any media packets, the server has no way of knowing what the SSRC
>is. There is also no guarantee that the SSRC across clients is going to be
>unique. So, the larger question is how does a server identify who it is
>receiving a RTCP report from when it does not receive any media packets.
>
I can agree that there are some difficulties in identifying the client 
based on RTCP reports and knowing for sure how to connect that with the 
RTSP session. However it seem that they have taken a reasonable solution.

The problem with multicast that a receiver must use the ports that the 
server decides on is also true for receiving the data. So unless you can 
get these port and receive the data on you neither has any problem with 
sending reports.

 From what you write in the background paragraph I can't determine if 
they are using a port pair per each RTP session or if they share port 
pair over multiple RTP sessions. Having a single RTP session on each 
port pair makes this problem much simpler and is according to RTP 
specification. If DSS tries to have multiple RTP session on a port pair 
this makes the problem much more difficult. However I understand that 
one might try for such a solution to allow the server to have many RTSP 
session simultaneous.

Having a single RTP session on each port pair solves this problem almost 
completely. Receiving a RTCP report on the control port can somewhat 
simplified be directly interpreted as the client (unicast) or some 
client (multicast) is alive and the RTSP session shall be kept alive. To 
prevent that somebody else is keeping a session alive the address should 
be checked so it comes from the receiver of the media. The client port 
can also be used in the match to remove any doubt that the sender is 
another client due to NAT or multi-user hosts. This requires that the 
client sends its report from its receiver ports. However I don't see 
that as a limitation, I would in fact strongly recommend it. It is in 
accordance whit how the designers of RTP thought it should be done, it 
is also a requirement if one wants to transmit RTCP messages from behind 
certain kinds of NATs. In multicast the client does not have a problem 
with this type of attack as it can discontinue delivery of media by 
leaving the multicast group. There exist other problems with RTSP 
security regarding multicast and rights to invite a server into a 
multicast group but they do not effect this problem.

A reason why not the clients SSRC itself should be connected into the 
RTSP keep alive mechanism is that it might change due to collision. It 
is rather unlikely in the case of unicast and if the server send the 
SSRC it will use I would say it is zero. In multicast this probability 
goes up especially due to bad implementations that does not use the 
complete number space when doing randomizations or don't do random SSRC. 
Therefore the SSRC can change (also the server's) and the RTP mechanism 
is definitely capable of coping with this.

Another problem with SSRC is that it gives no information about who the 
sender is, it is simply a administrative number that is used to connect 
different pieces of information together within RTP/RTCP. To identify 
the source of a report packet it is much more giving to look at sender 
adress/port and the CNAME.

Having multiple RTP sessions onto the same port pair create problems. As 
each session has its own SSRC space the risk of collision increase with 
the number of sessions. These are also not going away as they do not 
trigger any RTP collision resolving mechanism. Therefore this does not 
work when a multicast session is involved. It might work with multiple 
unicast sessions by matching the packets adress/port from the RTSP setup 
process. But I would not recommended it.  

>
>I do not know of a good way to solve this problem. Please let me know if I'm
>missing something. If not, a possible solution follows.
>
>Possible Solution:
>
>The only way to guarantee SSRC's that the clients use in RTCP will be unique
>is to let the server generate them and tell the clients during session
>setup. I would think the right place is to send "client_ssrc" in the
>RTP-Info header of the PLAY response from the server. 
>
>
>The server SSRC is sent to the client in the Transport header of SETUP
>response. I'm not really sure why it is here instead of in the RTP-Info
>Header in the PLAY response. If there is a good reason to do this, then the
>"client_ssrc" header can also be sent in the SETUP response.
>
As the SSRC is a rather permanent identifier in a RTP session it should 
be given when the RTP session is created and that is as a result of the 
SETUP request. The RTP-info header is not the right place as this header 
is sent for every PLAY response. However I don't see a reason why the 
server should be setting the clients SSRC. First, it can't be used in 
multicast. In unicast I don't see how it gives any advantage at all.


Regards


Magnus Westerlund 

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



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



From mailnull@www1.ietf.org  Mon Aug 26 15:14:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19585
	for <mmusic-archive@odin.ietf.org>; Mon, 26 Aug 2002 15:14:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7QJFqJ17091
	for mmusic-archive@odin.ietf.org; Mon, 26 Aug 2002 15:15:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QJFpo17088
	for <mmusic-web-archive@optimus.ietf.org>; Mon, 26 Aug 2002 15:15:51 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19569
	for <mmusic-web-archive@ietf.org>; Mon, 26 Aug 2002 15:14:18 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QJEVo17050;
	Mon, 26 Aug 2002 15:14:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QJDTo17016
	for <mmusic@optimus.ietf.org>; Mon, 26 Aug 2002 15:13:29 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19433;
	Mon, 26 Aug 2002 15:11:53 -0400 (EDT)
Message-Id: <200208261911.PAA19433@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>,
        mmusic@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Date: Mon, 26 Aug 2002 15:11:53 -0400
Subject: [MMUSIC] Protocol Action: Grouping of m lines in SDP to Proposed
 Standard
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>



The IESG has approved the Internet-Draft 'Grouping of m lines in SDP' 
<draft-ietf-mmusic-fid-06.txt> as a Proposed Standard.  This document 
is the product of the Multiparty Multimedia Session Control Working 
Group.  The IESG contact persons are Allison Mankin and Scott Bradner.
 
 
Technical Summary
 
  A Session Description Protocol (SDP) description typically contains 
  a number (one or more) media lines - which are commonly known as 
  "m" lines. When a session description contains more than one "m" 
  line, SDP does not provide any means to express a particular 
  relationship between them. When an application receives an SDP 
  session description with more than one "m" line it is currently up 
  to the application to figure out what to do with them.  SDP currently 
  does not carry any information about grouping media streams.
 
  While in some environments this information can be carried out of 
  band, it would be desirable to have extensions to SDP that allowed 
  the sender to express how different media streams within a session  
  description relate to each other. This document defines such 
  extensions.
 
  Specifically, this document defines two new SDP attributes: "group" 
  and "mid". They allow a sender to group together several "m" lines 
  for two different purposes: for lip synchronization and for 
  receiving media from a single flow (several media streams), encoded 
  in different formats during a particular session, through different 
  ports and host interfaces.

  The further handling of the media for the grouping are then handling
  by the application, and the grouping in the SDP description by this
  extension is a convenince.
   
Working Group Summary
 
  The mmusic working group supported the publication of this document
  with no controversy.
 
Protocol Quality
 
  This document was reviewed for the IESG by Allison Mankin


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



From mailnull@www1.ietf.org  Tue Aug 27 17:12:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12912
	for <mmusic-archive@odin.ietf.org>; Tue, 27 Aug 2002 17:12:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g7RLDE803920
	for mmusic-archive@odin.ietf.org; Tue, 27 Aug 2002 17:13:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7RLDEo03917
	for <mmusic-web-archive@optimus.ietf.org>; Tue, 27 Aug 2002 17:13:14 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12900
	for <mmusic-web-archive@ietf.org>; Tue, 27 Aug 2002 17:11:39 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7RLCEo03853;
	Tue, 27 Aug 2002 17:12:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7RJGgo28185
	for <mmusic@optimus.ietf.org>; Tue, 27 Aug 2002 15:16:42 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06546
	for <1timer>; Tue, 27 Aug 2002 14:44:44 -0400 (EDT)
Message-Id: <200208271844.OAA06546@ietf.org>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: IETF WG Participants: ;
Date: Tue, 27 Aug 2002 14:44:44 -0400
Subject: [MMUSIC] Nomcom call for volunteers
Sender: mmusic-admin@ietf.org
Errors-To: mmusic-admin@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>,
	<mailto:mmusic-request@ietf.org?subject=subscribe>


The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering 
to be on the nominations committee.
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic



