From mailman-owner@ietf.org  Mon Jul  1 06:19:11 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 GAA19843
	for <mmusic-archive@odin.ietf.org>; Mon, 1 Jul 2002 06:19:11 -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 GAA10049
	for <mmusic-web-archive@ietf.org>; Mon, 1 Jul 2002 06:19:58 -0400 (EDT)
Date: Mon, 1 Jul 2002 06:19:58 -0400 (EDT)
Message-Id: <200207011019.GAA10049@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: mmusic-web-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

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

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

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

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

                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

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

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions. 

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

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

Passwords for mmusic-web-archive@ietf.org:

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


From mmusic-admin@ietf.org  Mon Jul  1 19:36:49 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 TAA09731
	for <mmusic-archive@odin.ietf.org>; Mon, 1 Jul 2002 19:36: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 TAA20150;
	Mon, 1 Jul 2002 19:31: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 TAA20123
	for <mmusic@optimus.ietf.org>; Mon, 1 Jul 2002 19:31:25 -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 TAA09532
	for <mmusic@ietf.org>; Mon, 1 Jul 2002 19:30:36 -0400 (EDT)
Received: from orion.cs.columbia.edu (orion.cs.columbia.edu [128.59.16.21])
	by cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g61NVNxc020177;
	Mon, 1 Jul 2002 19:31:24 -0400 (EDT)
Received: from Shinkansen (shinkansen.cs.columbia.edu [128.59.19.93])
	by orion.cs.columbia.edu (8.12.1/8.12.1) with SMTP id g61NVNpB021437;
	Mon, 1 Jul 2002 19:31:23 -0400 (EDT)
Message-ID: <004901c22157$6981a290$5d133b80@cs.columbia.edu>
From: "Yuji Nomura" <nomura@cs.columbia.edu>
To: <cdn@ops.ietf.org>
Cc: <mmusic@ietf.org>
Date: Mon, 1 Jul 2002 19:27:55 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] draft-nomura-cdi-mmusic-mupdate-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
Content-Transfer-Encoding: 7bit

Hi all,

This is an individual submission for CDI-WG and MMUSIC-WG.
Comments and questions are very welcome.

Title: SIP Event Notification for Metadata Update Protocol
http://www.ietf.org/internet-drafts/draft-nomura-cdi-mmusic-mupdate-00.txt

Abstract
   This document specifies an update notification protocol for metadata
   using SIP event notification. This protocol improves metadata
   coherency and efficiency between content providers and receivers by
   up-to-date notifications when metadata changes. This protocol can
   also be applied to several systems such as a streaming video
   distribution system and a web content ditsribution system.

Thank you,
-----
Yuji Nomura
Fujitsu Laboratories Ltd. / Columbia University



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


From mmusic-admin@ietf.org  Tue Jul  2 10:22:15 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 KAA11641
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 10:22: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 KAA22435;
	Tue, 2 Jul 2002 10:15:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA22388
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 10:15:55 -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 KAA10967;
	Tue, 2 Jul 2002 10:15:06 -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 g62EDam02104;
	Tue, 2 Jul 2002 16:13:37 +0200 (MEST)
Message-ID: <3D21B579.7449C733@tzi.uni-bremen.de>
Date: Tue, 02 Jul 2002 16:15:21 +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: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Even, Roni" <roni.even@polycom.co.il>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>, "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [MMUSIC] FWD: I-D  
 ACTION:draft-even-mmusic-video-media-control-00.txt
References: <313680C9A886D511A06000204840E1CF030B55B6@whq-msgusr-02.pit.comms.marconi.com>
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

> We need to think carefully about this.
> If you accept that we need a reasonably reliable communication
> mechanism to accomplish tasks like video refresh, then we have,
> it seems to me, three choices:
> 
> 1. Use the signalling channel to do this.  Roni proposed
> a solution.

There is a sub-choice to be made here: The representation used to
convey the information.

The signaling channel may be adequate in some scenarios but SDP may not.

Also, as Henning pointed out, some signaling protocols -- such as RTSP --
may already provide reasonable hooks to achieve what Roni wants.  Others,
such as SIP, may have to rely on the message content to convey the
intended meaning.

We probably do not want to require all entities to speak both RTSP and
SIP.

> 2. Create an entirely new protocol to do this.
> You proposed to do this.

I'd consider this to be more on the worst case side of choices.

> 3. Make RTCP reliable and use it.

I don't think we need to make RTCP reliable, nor should we aim
for such a thing.

> 
> I'm not thrilled about using the signalling channel,
> but it has the very large advantage that it's, by far,
> the simplest way to solve the problem.  What Roni proposes may
> be ugly to you, but it will work. Sure, there may be latency
> issues, but I suspect that it won't be a big deal.

I think it is a rather ugly solution -- except for Jonathan's comment
pointing out that picture freeze is to some degree comparable to putting
a call on hold.  But again: which signaling protocol would you use
and how do you convey the information.

Also, I don't think reliability is key in all cases.  Taken to the
extreme, whether a command does not get through for a while
(because of re-transmissions), takes a while because some FEC scheme
is used, or is substituted by a later command after some (short) period
of time should not make too much a difference for many scenarios.
In either case, you will get rubbish (or nothing) on your screen
for a while; this can only be dealt with by the receiver.

> Designing an entirely new media level protocol for
> command/response of course keeps us protocol designers with vast
> new opportunities to enjoy 'many fine lunches', and a purpose
> built protocol MAY be the most appropriate thing to do, but,
> realistically, how long would you estimate it could be done,
> and what do we do in the mean time?

Right.  This is not an approach feasible for the short term.

> Enhancing RTCP might be between these two approaches,
> but seems to warp the original purpose a fair amount.
> I'm not real sure it still isn't the wisest approach.
> Besides, it might make the acronym more appropriate :)

We have been doing some work on RTCP feedback for receivers,
and we have discussed Roni's ideas in this context.  While "feedback"
is of course misleading for some of the cases, the mechanisms
described there could be applicable in such a different context,
too.  But I was reluctant to include the fairly different semantics
in the same document.  But one can probably build on top of it.

Joerg

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


From mmusic-admin@ietf.org  Tue Jul  2 11:02:43 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 LAA16470
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 11:02: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 KAA26228;
	Tue, 2 Jul 2002 10:54: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 KAA26145
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 10:54:29 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15189;
	Tue, 2 Jul 2002 10:53:41 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA05505;
	Tue, 2 Jul 2002 10:53:51 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA20065;
	Tue, 2 Jul 2002 10:53:50 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <N5N119WL>; Tue, 2 Jul 2002 10:53:50 -0400
Message-ID: <313680C9A886D511A06000204840E1CF030B55E2@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Even, Roni"
	 <roni.even@polycom.co.il>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>, "'avt@ietf.org'" <avt@ietf.org>
Subject: RE: [AVT] Re: [MMUSIC] FWD: I-D ACTION:draft-even-mmusic-video-me
	dia-control-00.txt
Date: Tue, 2 Jul 2002 10:53:49 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

I agree that the signalling channel might be appropriate
I agree that SDP may not be the best way to do it in the signalling 
	channel, but I think it could work
I agree that requiring RTSP to get a picture refresh in a SIP based
	terminal is not a good idea
I agree that designing a new protocol for this purpose is not 
	feasible

I think we need to decide whether RTCP or SIP signalling is the 
best way to solve the problem.  

I'll agree that there are many grades of reliability, and picture 
refresh doesn't need a lot of reliability, but wouldn't you say 
that you tend to need picture refresh when RTCP is pretty unlikely 
to get through?  It seems to me that you need something better than 
what RTCP currently does.  I'm neutral on whether it's easier to put 
it in the signalling channel, or enhance RTCP.  I just want to decide 
how best to do it, and go do it.

I observe that what you need is a lightweight mechanism that is
reasonably "robust" in the face of congestion.  Robust means that
refresh requests get through reasonably reliably without contributing
substantially to the congestion problem.  I observe that the more
reliable the mechanism is, the better the sender behaves with respect
to congestion -- if the receiver blocks waiting for the refresh,
and the sender doesn't get the request, it sends updates that are 
discarded at the receiver, until the refresh comes.  Then it sends
the refreshed image.  If the refresh came in a timely and somewhat
reliable (in the face of congestion) manner, then the sender would
be more likely to send only useful data.

Brian


> -----Original Message-----
> From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
> Sent: Tuesday, July 02, 2002 10:15 AM
> To: Rosen, Brian
> Cc: 'Jonathan Rosenberg'; Even, Roni; 'mmusic@ietf.org'; 
> 'avt@ietf.org'
> Subject: [AVT] Re: [MMUSIC] FWD: I-D
> ACTION:draft-even-mmusic-video-media-control-00.txt
> 
> 
> > We need to think carefully about this.
> > If you accept that we need a reasonably reliable communication
> > mechanism to accomplish tasks like video refresh, then we have,
> > it seems to me, three choices:
> > 
> > 1. Use the signalling channel to do this.  Roni proposed
> > a solution.
> 
> There is a sub-choice to be made here: The representation used to
> convey the information.
> 
> The signaling channel may be adequate in some scenarios but 
> SDP may not.
> 
> Also, as Henning pointed out, some signaling protocols -- 
> such as RTSP --
> may already provide reasonable hooks to achieve what Roni 
> wants.  Others,
> such as SIP, may have to rely on the message content to convey the
> intended meaning.
> 
> We probably do not want to require all entities to speak both RTSP and
> SIP.
> 
> > 2. Create an entirely new protocol to do this.
> > You proposed to do this.
> 
> I'd consider this to be more on the worst case side of choices.
> 
> > 3. Make RTCP reliable and use it.
> 
> I don't think we need to make RTCP reliable, nor should we aim
> for such a thing.
> 
> > 
> > I'm not thrilled about using the signalling channel,
> > but it has the very large advantage that it's, by far,
> > the simplest way to solve the problem.  What Roni proposes may
> > be ugly to you, but it will work. Sure, there may be latency
> > issues, but I suspect that it won't be a big deal.
> 
> I think it is a rather ugly solution -- except for Jonathan's comment
> pointing out that picture freeze is to some degree comparable 
> to putting
> a call on hold.  But again: which signaling protocol would you use
> and how do you convey the information.
> 
> Also, I don't think reliability is key in all cases.  Taken to the
> extreme, whether a command does not get through for a while
> (because of re-transmissions), takes a while because some FEC scheme
> is used, or is substituted by a later command after some 
> (short) period
> of time should not make too much a difference for many scenarios.
> In either case, you will get rubbish (or nothing) on your screen
> for a while; this can only be dealt with by the receiver.
> 
> > Designing an entirely new media level protocol for
> > command/response of course keeps us protocol designers with vast
> > new opportunities to enjoy 'many fine lunches', and a purpose
> > built protocol MAY be the most appropriate thing to do, but,
> > realistically, how long would you estimate it could be done,
> > and what do we do in the mean time?
> 
> Right.  This is not an approach feasible for the short term.
> 
> > Enhancing RTCP might be between these two approaches,
> > but seems to warp the original purpose a fair amount.
> > I'm not real sure it still isn't the wisest approach.
> > Besides, it might make the acronym more appropriate :)
> 
> We have been doing some work on RTCP feedback for receivers,
> and we have discussed Roni's ideas in this context.  While "feedback"
> is of course misleading for some of the cases, the mechanisms
> described there could be applicable in such a different context,
> too.  But I was reluctant to include the fairly different semantics
> in the same document.  But one can probably build on top of it.
> 
> Joerg
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

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


From mmusic-admin@ietf.org  Tue Jul  2 11:16:14 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 LAA18287
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 11:16:14 -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 LAA28132;
	Tue, 2 Jul 2002 11:11:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28075
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 11:11:10 -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 LAA17204;
	Tue, 2 Jul 2002 11:10:19 -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 g62FAhm17890;
	Tue, 2 Jul 2002 17:10:43 +0200 (MEST)
Message-ID: <3D21C2DB.E9C652B8@tzi.uni-bremen.de>
Date: Tue, 02 Jul 2002 17:12:27 +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: Henning Schulzrinne <hgs@cs.columbia.edu>
CC: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Even, Roni" <roni.even@polycom.co.il>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>, "'avt@ietf.org'" <avt@ietf.org>
Subject: Re: [AVT] RE: [MMUSIC] FWD: I-D  
 ACTION:draft-even-mmusic-video-media-control-00.txt
References: <313680C9A886D511A06000204840E1CF030B55B6@whq-msgusr-02.pit.comms.marconi.com> <3D1C9211.6090206@cs.columbia.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

> > 1. Use the signalling channel to do this.  Roni proposed
> > a solution.
> > 2. Create an entirely new protocol to do this.
> > You proposed to do this.
> > 3. Make RTCP reliable and use it.
> 
> There have been hints of this nature; see RFC 2032 for H.261.

See also draft-ietf-avt-rtcp-feedback-03.txt, which doesn't
make it reliable but still conveys similar information to the
sender.

> > I'm not thrilled about using the signalling channel,
> > but it has the very large advantage that it's, by far,
> > the simplest way to solve the problem.  What Roni proposes may
> > be ugly to you, but it will work. Sure, there may be latency
> > issues, but I suspect that it won't be a big deal.
> >
> > Designing an entirely new media level protocol for
> > command/response of course keeps us protocol designers with vast
> > new opportunities to enjoy 'many fine lunches', and a purpose
> > built protocol MAY be the most appropriate thing to do, but,
> > realistically, how long would you estimate it could be done,
> > and what do we do in the mean time?
> 
> There's always RTSP that probably fits a bit better and avoids the proxy
> issues. (I'm not suggesting that this is the ideal solution, but it's
> another point in the design space.) It specifically has SET_PARAMETER
> for such purposes.

Right.  It would also be cleaner from the semantics perspective.
I am not sure what kind other "remote control" protocols will be
showing up in the near future (there have been some discussion of
desired functionality which is not yet covered over the past months)
but RTSP has been suggested for at least two of them as being a
reasonable candidate.  But as stated in an earlier mail, there
is probably still a long way to go.

There are other issues: e.g. with broadcast-style scenarios in which
you do not have individual control connections to each those.  But
you still may want to be able to communicate "freeze" events as
Roni pointed out.  In many-to-many scenarios, we may or may not want
to have (yet) full mesh or n:m signaling relationships (besides SIP)
set-up just to send such commands and indications.

> > Enhancing RTCP might be between these two approaches,
> > but seems to warp the original purpose a fair amount.
> > I'm not real sure it still isn't the wisest approach.
> > Besides, it might make the acronym more appropriate :)
> 
> It would be tricky to do this right in the presence of RTP mixers and
> translators, to name just one set of problems.

What is actually the default behavior of a mixer/translator if it
receives an RTCP compound packet in which individual RTCP packets
are not understood?  The spec seems to be rather silent about this.

Joerg

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


From mmusic-admin@ietf.org  Tue Jul  2 11:58: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 LAA24331
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 11:58: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 LAA02824;
	Tue, 2 Jul 2002 11:53: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 LAA02760
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 11:53:00 -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 LAA23976;
	Tue, 2 Jul 2002 11:52:09 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <3BT0ZBHN>; Tue, 2 Jul 2002 18:52:22 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA137@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>,
        "Rosen, Brian"
	 <Brian.Rosen@marconi.com>
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Even, Roni"
	 <roni.even@polycom.co.il>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>, "'avt@ietf.org'" <avt@ietf.org>
Subject: RE: [AVT] Re: [MMUSIC] FWD: I-D ACTION:draft-even-mmusic-video-me
	dia-control-00.txt
Date: Tue, 2 Jul 2002 18:52:21 +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,
I want to emphasis that one of the usage case for fast update and freeze is
to support smooth video source switch like is being done in multipoint video
switching. The switch is handled by the conference control who may not have
a direct access to the RTCP channel. This is a session control and not media
control request. The draft outline the process.

Thanks
Roni Even

> -----Original Message-----
> From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
> Sent: Tuesday, July 02, 2002 5:15 PM
> To: Rosen, Brian
> Cc: 'Jonathan Rosenberg'; Even, Roni; 'mmusic@ietf.org'; 
> 'avt@ietf.org'
> Subject: [AVT] Re: [MMUSIC] FWD: I-D 
> ACTION:draft-even-mmusic-video-media-control-00.txt
> 
> 
> > We need to think carefully about this.
> > If you accept that we need a reasonably reliable communication
> > mechanism to accomplish tasks like video refresh, then we have,
> > it seems to me, three choices:
> > 
> > 1. Use the signalling channel to do this.  Roni proposed
> > a solution.
> 
> There is a sub-choice to be made here: The representation used to
> convey the information.
> 
> The signaling channel may be adequate in some scenarios but 
> SDP may not.
> 
> Also, as Henning pointed out, some signaling protocols -- 
> such as RTSP --
> may already provide reasonable hooks to achieve what Roni 
> wants.  Others,
> such as SIP, may have to rely on the message content to convey the
> intended meaning.
> 
> We probably do not want to require all entities to speak both RTSP and
> SIP.
> 
> > 2. Create an entirely new protocol to do this.
> > You proposed to do this.
> 
> I'd consider this to be more on the worst case side of choices.
> 
> > 3. Make RTCP reliable and use it.
> 
> I don't think we need to make RTCP reliable, nor should we aim
> for such a thing.
> 
> > 
> > I'm not thrilled about using the signalling channel,
> > but it has the very large advantage that it's, by far,
> > the simplest way to solve the problem.  What Roni proposes may
> > be ugly to you, but it will work. Sure, there may be latency
> > issues, but I suspect that it won't be a big deal.
> 
> I think it is a rather ugly solution -- except for Jonathan's comment
> pointing out that picture freeze is to some degree comparable 
> to putting
> a call on hold.  But again: which signaling protocol would you use
> and how do you convey the information.
> 
> Also, I don't think reliability is key in all cases.  Taken to the
> extreme, whether a command does not get through for a while
> (because of re-transmissions), takes a while because some FEC scheme
> is used, or is substituted by a later command after some 
> (short) period
> of time should not make too much a difference for many scenarios.
> In either case, you will get rubbish (or nothing) on your screen
> for a while; this can only be dealt with by the receiver.
> 
> > Designing an entirely new media level protocol for
> > command/response of course keeps us protocol designers with vast
> > new opportunities to enjoy 'many fine lunches', and a purpose
> > built protocol MAY be the most appropriate thing to do, but,
> > realistically, how long would you estimate it could be done,
> > and what do we do in the mean time?
> 
> Right.  This is not an approach feasible for the short term.
> 
> > Enhancing RTCP might be between these two approaches,
> > but seems to warp the original purpose a fair amount.
> > I'm not real sure it still isn't the wisest approach.
> > Besides, it might make the acronym more appropriate :)
> 
> We have been doing some work on RTCP feedback for receivers,
> and we have discussed Roni's ideas in this context.  While "feedback"
> is of course misleading for some of the cases, the mechanisms
> described there could be applicable in such a different context,
> too.  But I was reluctant to include the fairly different semantics
> in the same document.  But one can probably build on top of it.
> 
> Joerg
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt
> 

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


From mmusic-admin@ietf.org  Tue Jul  2 15:38: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 PAA11154
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 15:38:50 -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 PAA19770;
	Tue, 2 Jul 2002 15:36:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19735
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 15:36:52 -0400 (EDT)
Received: from ns.live.com (ns.live.com [66.80.62.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10939
	for <mmusic@ietf.org>; Tue, 2 Jul 2002 15:36:02 -0400 (EDT)
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.4/8.12.3) with ESMTP id g62Jao8s091757
	for <mmusic@ietf.org>; Tue, 2 Jul 2002 12:36:50 -0700 (PDT)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.4/8.12.3/Submit) id g62Jaorb091756;
	Tue, 2 Jul 2002 12:36:50 -0700 (PDT)
Message-Id: <4.3.1.1.20020702122204.00cb9400@laptop-localhost>
X-Sender: rsf@laptop-localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 02 Jul 2002 12:32:14 -0700
To: mmusic@ietf.org
From: Ross Finlayson <finlayson@live.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [MMUSIC] FYI: Updated "mmusic-sdp-srcfilter" Internet 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

Bob Quinn and I have updated, and re-submitted, the MMUSIC Internet Draft 
that describes how to specify source-filtered multicast sessions in 
SDP.  In particular, this describes how Source-Specific Multicast (SSM) 
sessions are described in SDP.  (For RTP SSM sessions, it also refers to 
the Chesterfield et al RTCP unicast feedback draft.)

Until the draft is announced in the IETF directory, you can find a copy 
online as <http://www.live.com/mmusic-sdp-srcfilter-01.txt>

This draft had been a MMUSIC work item, but it accidentally fell off our 
radar screens for a while.  I hope this will put it back on track.  If you 
have any comments, please send them to the "mmusic" mailing list.  (I won't 
be at the Yokohama meeting.)

	Ross.


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


From mmusic-admin@ietf.org  Tue Jul  2 15:56:41 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 PAA12209
	for <mmusic-archive@odin.ietf.org>; Tue, 2 Jul 2002 15:56:41 -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 PAA20505;
	Tue, 2 Jul 2002 15:52:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA20474
	for <mmusic@optimus.ietf.org>; Tue, 2 Jul 2002 15:52:21 -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 PAA11877
	for <mmusic@ietf.org>; Tue, 2 Jul 2002 15:51:32 -0400 (EDT)
Received: (from jo@localhost)
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) id g62Jq6O15971;
	Tue, 2 Jul 2002 21:52:06 +0200 (MEST)
From: Joerg Ott <jo@Informatik.Uni-Bremen.DE>
Message-Id: <200207021952.g62Jq6O15971@nmh.informatik.uni-bremen.de>
Subject: Re: [MMUSIC] FYI: Updated "mmusic-sdp-srcfilter" Internet Draft
To: finlayson@live.com (Ross Finlayson)
Date: Tue, 2 Jul 2002 21:52:05 +0200 (MEST)
Cc: mmusic@ietf.org
In-Reply-To: <4.3.1.1.20020702122204.00cb9400@laptop-localhost> from "Ross Finlayson" at Jul 02, 2002 12:32:14 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

Ross,

looks like we got two versions of -01 now :-)

With your mail to Colin and my mail to Bob bouncing, Colin and myself
figured that we better submit a revised version of Bob's document.
Which I did.  I shall take care of the process with the I-D editor
to make sure that the right version (yours) will get posted.

Cheers,
Joerg

> 
> Bob Quinn and I have updated, and re-submitted, the MMUSIC Internet Draft 
> that describes how to specify source-filtered multicast sessions in 
> SDP.  In particular, this describes how Source-Specific Multicast (SSM) 
> sessions are described in SDP.  (For RTP SSM sessions, it also refers to 
> the Chesterfield et al RTCP unicast feedback draft.)
> 
> Until the draft is announced in the IETF directory, you can find a copy 
> online as <http://www.live.com/mmusic-sdp-srcfilter-01.txt>
> 
> This draft had been a MMUSIC work item, but it accidentally fell off our 
> radar screens for a while.  I hope this will put it back on track.  If you 
> have any comments, please send them to the "mmusic" mailing list.  (I won't 
> be at the Yokohama meeting.)
> 
> 	Ross.
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 


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


From mmusic-admin@ietf.org  Wed Jul  3 10:04: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 KAA14769
	for <mmusic-archive@odin.ietf.org>; Wed, 3 Jul 2002 10:04:31 -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 KAA13326;
	Wed, 3 Jul 2002 10:01: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 KAA13032
	for <mmusic@ns.ietf.org>; Wed, 3 Jul 2002 10:00:32 -0400 (EDT)
Received: from smtp.wanadoo.es (smtp5.wanadoo.es [62.37.236.139] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14278
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 09:59:41 -0400 (EDT)
Received: from risitas (62-36-178-3.dialup.uni2.es [62.36.178.3])
	by smtp.wanadoo.es (8.11.6/8.11.6) with ESMTP id g63DxCs22956
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 09:59:12 -0400
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17Pkih-0001Ij-00
	for <mmusic@ietf.org>; Wed, 03 Jul 2002 16:02:59 +0200
Date: Wed, 3 Jul 2002 16:02:59 +0200
From: Federico Montesino Pouzols <fedemp@suidzer0.org>
To: mmusic@ietf.org
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines?
Message-ID: <20020703140259.GA609@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@suidzer0.org>
Mail-Followup-To: mmusic@ietf.org
References: <20020627203108.GA4407@risitas> <200206301858.g5UIwPtD006165@purple.nge.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200206301858.g5UIwPtD006165@purple.nge.isi.edu>
User-Agent: Mutt/1.3.25i
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

On Sun, Jun 30, 2002 at 02:58:25PM -0400, Colin Perkins wrote:
> --> Federico Montesino Pouzols writes:
> >Hello everyone,
> >
> >  On section 6 in draft-ietf-mmusic-sdp-new-10.txt the following
> >examples of r= lines are given:
> >
> ># r=604800 3600 0 90000
> ># r=7d 1h 0 25h
> >
> >  From this examples, I understand that "0" is a valid value for the
> >offsets. However on appendix A r= lines are defined like this:
> >
> ># repeat-fields =       "r=" repeat-interval SP typed-time
> >#                      1*(SP typed-time)
> >
> ># repeat-interval =     typed-time
> >
> ># typed-time =          POS-DIGIT *DIGIT [fixed-len-time-unit]
> >
> ># POS-DIGIT =           %x31-39 ; 1 - 9
> >
> >  The two examples above would violate this syntax, since the first
> >offset is "0", which is not a POS-DIGIT. In RFC 2327, typed-time
> >started with DIGIT, so there was no problem.
> >
> >  It seems to me, correct me please if I am wrong, that the first
> >offset, "0", is not necessary and could be assumed. Anyway, to keep
> >backward compatibility it has to be there. Would the following rule
> >solve the problem?
> >
> ># repeat-fields =       "r=" repeat-interval SP typed-time SP "0"
> >#                      1*(SP typed-time)
> 
> I agree that it looks like a bug in the ABNF. A better fix might be to
> change typed-time to be
> 
> 	typed-time = 1*DIGIT [fixed-len-time-unit]
> 
> to avoid mandating a leading zero?
> 
> Colin

	I understand the draft mandates the leading zero from the 
following paragraph:

o    ``r='' fields specify repeat times for a session.  For example, if
    a session is active at 10am on Monday and 11am on Tuesday for one
    hour each week for three months, then the <start time> in the
    corresponding ``t='' field would be the NTP representation of 10am
    on the first Monday, the <repeat interval> would be 1 week, the
    <active duration> would be 1 hour, and the offsets would be zero and
    25 hours. The corresponding ``t='' field stop time would be the NTP
    representation of the end of the last session three months later. By
    default all fields are in seconds, so the ``r='' and ``t='' fields
    might be:


	So I guess the first offset could be non zero only if the start
time given in the corresponding t= line were shifted from the actual
beginning of the session. I believe the first offset is always 0 and it
could be omitted if backward compatibility were not a concern. Is it
true?


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


From mmusic-admin@ietf.org  Wed Jul  3 16:08:11 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 QAA04032
	for <mmusic-archive@odin.ietf.org>; Wed, 3 Jul 2002 16:08:11 -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 QAA10118;
	Wed, 3 Jul 2002 16:03: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 KAA15433
	for <mmusic@ns.ietf.org>; Wed, 3 Jul 2002 10:42:14 -0400 (EDT)
Received: from smtp.wanadoo.es (smtp1.wanadoo.es [62.37.236.135] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16954
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 10:41:17 -0400 (EDT)
Received: from risitas (62-36-178-3.dialup.uni2.es [62.36.178.3])
	by smtp.wanadoo.es (8.11.3/8.10.2) with ESMTP id g63EaFw00990
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 16:36:16 +0200 (MEST)
Received: from fedemp by risitas with local (Exim 3.35 #1 (Debian))
	id 17PlIX-0001Jm-00
	for <mmusic@ietf.org>; Wed, 03 Jul 2002 16:40:01 +0200
Date: Wed, 3 Jul 2002 16:40:00 +0200
From: Federico Montesino Pouzols <fedemp@suidzer0.org>
To: mmusic@ietf.org
Message-ID: <20020703144000.GA5045@risitas>
Reply-To: Federico Montesino Pouzols <fedemp@suidzer0.org>
Mail-Followup-To: mmusic@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.25i
Subject: [MMUSIC] A bug in SDP Syntax (CRLF)?
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 everyone,

        draft-ietf-mmusic-sdp-new-10.txt, Section 6, says:

        "The sequence CRLF (0x0d0a) is used to end a record, although
parsers SHOULD be tolerant and also accept records terminated with a
single newline character."

        However, if we look at each and every line definition in the
ABNF syntax in appendix A, all lines must end with CRLF, defined in
RFC 2234 as:

        CRLF           =  CR LF

        CR             =  %d13

        LF             =  %x0A

        An implementor would have to choose between strictly
applying the ABNF or being tolerant with single LFs.

         Should not -at least- a note be added to the ABNF clarifying
this exception? CRLF could also be replaced with something like this:

         line-end      =   CR / CR LF




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


From mmusic-admin@ietf.org  Thu Jul  4 02:08: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 CAA08633
	for <mmusic-archive@odin.ietf.org>; Thu, 4 Jul 2002 02:08: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 CAA26711;
	Thu, 4 Jul 2002 02:01: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 RAA15408
	for <mmusic@ns.ietf.org>; Wed, 3 Jul 2002 17:25:36 -0400 (EDT)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07207
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 17:24:47 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate4.mot.com (motgate4 2.1) with ESMTP id OAA11083 for <mmusic@ietf.org>; Wed, 3 Jul 2002 14:25:34 -0700 (MST)]
Received: [from artibeus.nsr.labs.mot.com (artibeus.nsr.labs.mot.com [173.23.95.73]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id OAA27685 for <mmusic@ietf.org>; Wed, 3 Jul 2002 14:25:34 -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 g63LTDZ08001
	for <mmusic@ietf.org>; Wed, 3 Jul 2002 16:29:13 -0500
Message-ID: <3D236CA9.BF8B3C64@motorola.com>
Date: Wed, 03 Jul 2002 16:29:13 -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: mmusic@ietf.org
Subject: Re: [MMUSIC] A bug in SDP Syntax (CRLF)?
References: <20020703144000.GA5045@risitas>
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

> Should not -at least- a note be added to the ABNF clarifying
> this exception? CRLF could also be replaced with something like this:
>
>          line-end      =   CR / CR LF
>

Well, line-end = LF / CR LF would be more in keeping with the text.

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 mmusic-admin@ietf.org  Thu Jul  4 09:06: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 JAA16658
	for <mmusic-archive@odin.ietf.org>; Thu, 4 Jul 2002 09:06: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 IAA17344;
	Thu, 4 Jul 2002 08:59: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 IAA17313
	for <mmusic@optimus.ietf.org>; Thu, 4 Jul 2002 08:59:18 -0400 (EDT)
Received: from purple.nge.isi.edu (ras02.isi.edu [128.9.176.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16544
	for <mmusic@ietf.org>; Thu, 4 Jul 2002 08:58:27 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g64CxDOK009984;
	Thu, 4 Jul 2002 08:59:14 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207041259.g64CxDOK009984@purple.nge.isi.edu>
To: Federico Montesino Pouzols <fedemp@suidzer0.org>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] A bug in SDP Syntax (CRLF)? 
In-Reply-To: Your message of "Wed, 03 Jul 2002 16:40:00 +0200."
             <20020703144000.GA5045@risitas> 
Date: Thu, 04 Jul 2002 08:59:13 -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

--> Federico Montesino Pouzols writes:
>        Hello everyone,
>
>        draft-ietf-mmusic-sdp-new-10.txt, Section 6, says:
>
>        "The sequence CRLF (0x0d0a) is used to end a record, although
>parsers SHOULD be tolerant and also accept records terminated with a
>single newline character."
>
>        However, if we look at each and every line definition in the
>ABNF syntax in appendix A, all lines must end with CRLF, defined in
>RFC 2234 as:
>
>        CRLF           =  CR LF
>
>        CR             =  %d13
>
>        LF             =  %x0A
>
>        An implementor would have to choose between strictly
>applying the ABNF or being tolerant with single LFs.
>
>         Should not -at least- a note be added to the ABNF clarifying
>this exception? 

No. A correct implementation will use CRLF in all cases, and the ABNF
reflects this. Using a single LF to terminate lines is a bug.

Colin

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


From mmusic-admin@ietf.org  Thu Jul  4 09:06:33 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 JAA16673
	for <mmusic-archive@odin.ietf.org>; Thu, 4 Jul 2002 09:06: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 JAA17923;
	Thu, 4 Jul 2002 09:02: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 JAA17878
	for <mmusic@optimus.ietf.org>; Thu, 4 Jul 2002 09:01:58 -0400 (EDT)
Received: from purple.nge.isi.edu (ras02.isi.edu [128.9.176.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16581
	for <mmusic@ietf.org>; Thu, 4 Jul 2002 09:01:05 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g64D1sOK010046;
	Thu, 4 Jul 2002 09:01:54 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207041301.g64D1sOK010046@purple.nge.isi.edu>
To: Federico Montesino Pouzols <fedemp@suidzer0.org>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines? 
In-Reply-To: Your message of "Wed, 03 Jul 2002 16:02:59 +0200."
             <20020703140259.GA609@risitas> 
Date: Thu, 04 Jul 2002 09:01: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

--> Federico Montesino Pouzols writes:
>	I understand the draft mandates the leading zero from the 
>following paragraph:
>
>o    ``r='' fields specify repeat times for a session.  For example, if
>    a session is active at 10am on Monday and 11am on Tuesday for one
>    hour each week for three months, then the <start time> in the
>    corresponding ``t='' field would be the NTP representation of 10am
>    on the first Monday, the <repeat interval> would be 1 week, the
>    <active duration> would be 1 hour, and the offsets would be zero and
>    25 hours. The corresponding ``t='' field stop time would be the NTP
>    representation of the end of the last session three months later. By
>    default all fields are in seconds, so the ``r='' and ``t='' fields
>    might be:
>
>	So I guess the first offset could be non zero only if the start
>time given in the corresponding t= line were shifted from the actual
>beginning of the session. I believe the first offset is always 0 and it
>could be omitted if backward compatibility were not a concern. Is it
>true?

The ABNF in RFC 2327 does not require the leading zero.

Colin

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


From mmusic-admin@ietf.org  Fri Jul  5 06:40:09 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 GAA17964
	for <mmusic-archive@odin.ietf.org>; Fri, 5 Jul 2002 06:40: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 GAA23489;
	Fri, 5 Jul 2002 06:36:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23460
	for <mmusic@optimus.ietf.org>; Fri, 5 Jul 2002 06:36:50 -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 GAA17399;
	Fri, 5 Jul 2002 06:35:58 -0400 (EDT)
Message-Id: <200207051035.GAA17399@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: Fri, 05 Jul 2002 06:35:58 -0400
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-01.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.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

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

Receiver applications are expected use the SDP source-filter
information to identify traffic from legitimate senders and discard
traffic from illegitimate senders.  Applications and hosts may also
share the source-filter information with network elements (e.g., with
routers using IGMPv3) so they can potentially perform the traffic
filtering operation further 'upstream,' closer to the source(s).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcfilter-01.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-ietf-mmusic-sdp-srcfilter-01.txt".

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--



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


From mmusic-admin@ietf.org  Sat Jul  6 09:17:02 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 JAA20220
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 09:17: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 JAA08399;
	Sat, 6 Jul 2002 09:11: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 JAA08370
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 09:11:10 -0400 (EDT)
Received: from Hardcore.suidzer0.org (aboukir-101-2-4-sudizero.adsl.nerim.net [62.212.111.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20130
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 09:10:19 -0400 (EDT)
Received: from suidzer0.org (localhost [127.0.0.1])
          by Hardcore.suidzer0.org (8.11.4/jtpda-5.3.3) with SMTP id g66D8Qw19294
          for <mmusic@ietf.org>; Sat, 6 Jul 2002 15:08:27 +0200
Received: from 62.36.188.231
        (SquirrelMail authenticated user fedemp)
        by webmail.suidzer0.org with HTTP;
        Sat, 6 Jul 2002 15:08:27 +0200 (CEST)
Message-ID: <4172.62.36.188.231.1025960907.squirrel@webmail.suidzer0.org>
Date: Sat, 6 Jul 2002 15:08:27 +0200 (CEST)
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines?
From: "Federico Montesino Pouzols" <fedemp@suidzer0.org>
To: <mmusic@ietf.org>
In-Reply-To: <200207041301.g64D1sOK010046@purple.nge.isi.edu>
References: Your
        message
        of
        "Wed,
        03
        Jul
        2002
        16:02:59
        +0200."
        <200207041301.g64D1sOK010046@purple.nge.isi.edu>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: fedemp@suidzer0.org
X-Mailer: SquirrelMail (version 1.2.7)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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

>>	So I guess the first offset could be non zero only if the start
>>time given in the corresponding t= line were shifted from the actual
>> beginning of the session. I believe the first offset is always 0 and it
>> could be omitted if backward compatibility were not a concern. Is it
>> true?
>
> The ABNF in RFC 2327 does not require the leading zero.
>
> Colin
>

I see, the explicit zero does not fit the RFC ABNF. However
I keep wondering the same question: is actually the first offset
always zero? I mean, although the RFC ABNF does not mandate it, the
text describing r= lines (the same in both RFC 2327 and
draft-ietf-mmusic-sdp-new-10) seems to imply that the first offset is
always zero. The examples and explanations given in both documents
make me think that the first offset correponds to the beginning of the
session (as opposed to the first time the session is resumed), thus
being zero.

	Is this interpretation right or is there any case in which the
first offset can be non zero?




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


From mmusic-admin@ietf.org  Sat Jul  6 09:20:00 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 JAA20285
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 09:20: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 JAA08504;
	Sat, 6 Jul 2002 09:17:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08474
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 09:17:27 -0400 (EDT)
Received: from Hardcore.suidzer0.org (aboukir-101-2-4-sudizero.adsl.nerim.net [62.212.111.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20202
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 09:16:36 -0400 (EDT)
Received: from suidzer0.org (localhost [127.0.0.1])
          by Hardcore.suidzer0.org (8.11.4/jtpda-5.3.3) with SMTP id g66DElw19351
          for <mmusic@ietf.org>; Sat, 6 Jul 2002 15:14:47 +0200
Received: from 62.36.188.231
        (SquirrelMail authenticated user fedemp)
        by webmail.suidzer0.org with HTTP;
        Sat, 6 Jul 2002 15:14:47 +0200 (CEST)
Message-ID: <4174.62.36.188.231.1025961287.squirrel@webmail.suidzer0.org>
Date: Sat, 6 Jul 2002 15:14:47 +0200 (CEST)
Subject: Re: [MMUSIC] A bug in SDP Syntax (CRLF)?
From: "Federico Montesino Pouzols" <fedemp@suidzer0.org>
To: <mmusic@ietf.org>
In-Reply-To: <200207041259.g64CxDOK009984@purple.nge.isi.edu>
References: Your
        message
        of
        "Wed,
        03
        Jul
        2002
        16:40:00
        +0200."
        <200207041259.g64CxDOK009984@purple.nge.isi.edu>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: fedemp@suidzer0.org
X-Mailer: SquirrelMail (version 1.2.7)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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

>>        An implementor would have to choose between strictly
>>applying the ABNF or being tolerant with single LFs.
>>
>>         Should not -at least- a note be added to the ABNF clarifying
>>this exception?
>
> No. A correct implementation will use CRLF in all cases, and the ABNF
> reflects this. Using a single LF to terminate lines is a bug.
>
> Colin
>

   Then I infer that if I am doing a new implementation and I want it
to be compliant with the specification I must always use CR LF and
consider single LFs as a mistake. All the lines in the SDP
descriptions generated by the new implementation must end with CR LF
and my new parser must not accept descriptions with lines ending with
a single LF?

   This new implementation would follow the ABNF, however it would
also cowardly ignore the _"although parsers SHOULD be tolerant and also
accept records terminated with a single newline character"_ in section
6.

   Using a LF to terminate lines may not be strictly correct, but the
specification recommends (SHOULD) parsers to be tolerant about it. So
I think it would be clearer for implementors if the ABNF syntax
mentioned this exception as a note or whatever.

   From my point of view and my understanding of the draft, an
implementation that in all cases only accepts CR LF is correct in some
sense but would be incorrect at the same time, since it ignores the
quoted sentence in the draft and RFC. In fact, it would reject a lot
of SDP descriptions and could not interoperate with many tools out
there.





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


From mmusic-admin@ietf.org  Sat Jul  6 10:44: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 KAA22527
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 10:44:55 -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 KAA12192;
	Sat, 6 Jul 2002 10:41:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12161
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 10:41:44 -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 KAA22467
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 10:40:53 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g66EeRK5001316;
	Sat, 6 Jul 2002 10:40:27 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207061440.g66EeRK5001316@purple.nge.isi.edu>
To: fedemp@suidzer0.org
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] A bug in SDP Syntax (CRLF)? 
In-Reply-To: Your message of "Sat, 06 Jul 2002 15:14:47 +0200."
             <4174.62.36.188.231.1025961287.squirrel@webmail.suidzer0.org> 
Date: Sat, 06 Jul 2002 10:40:27 -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

--> "Federico Montesino Pouzols" writes:
>>>        An implementor would have to choose between strictly
>>>applying the ABNF or being tolerant with single LFs.
>>>
>>>         Should not -at least- a note be added to the ABNF clarifying
>>>this exception?
>>
>> No. A correct implementation will use CRLF in all cases, and the ABNF
>> reflects this. Using a single LF to terminate lines is a bug.
>
>   Then I infer that if I am doing a new implementation and I want it
>to be compliant with the specification I must always use CR LF and
>consider single LFs as a mistake. All the lines in the SDP
>descriptions generated by the new implementation must end with CR LF
>and my new parser must not accept descriptions with lines ending with
>a single LF?
>
>   This new implementation would follow the ABNF, however it would
>also cowardly ignore the _"although parsers SHOULD be tolerant and also
>accept records terminated with a single newline character"_ in section
>6.
>
>   Using a LF to terminate lines may not be strictly correct, but the
>specification recommends (SHOULD) parsers to be tolerant about it. So
>I think it would be clearer for implementors if the ABNF syntax
>mentioned this exception as a note or whatever.
>
>   From my point of view and my understanding of the draft, an
>implementation that in all cases only accepts CR LF is correct in some
>sense but would be incorrect at the same time, since it ignores the
>quoted sentence in the draft and RFC. In fact, it would reject a lot
>of SDP descriptions and could not interoperate with many tools out
>there.

SDP descriptions where the lines end in a single LF are incorrect. You may
wish to design your parser such that it accepts them anyway - as suggested
by the draft - but there is no requirement that you do this, and you could
reject such descriptions.

Colin

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


From mmusic-admin@ietf.org  Sat Jul  6 10: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 KAA22696
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 10:54:04 -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 KAA12439;
	Sat, 6 Jul 2002 10:48:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12407
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 10:48:51 -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 KAA22584
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 10:47:59 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g66EmoK5001620
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 10:48:50 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207061448.g66EmoK5001620@purple.nge.isi.edu>
To: mmusic@ietf.org
Date: Sat, 06 Jul 2002 10:48:50 -0400
From: Colin Perkins <csp@isi.edu>
Subject: [MMUSIC] Last call: simcap and fid
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

FYI...

------- Forwarded Message
>To: IETF-Announce: ;
>From: The IESG <iesg-secretary@ietf.org>
>SUBJECT: Last Call: SDP Simple Capability Declaration to Proposed Standard
>Date: Fri, 05 Jul 2002 13:47:14 -0400
>
>The IESG has received a request to consider SDP Simple Capability 
>Declaration <draft-andreasen-mmusic-sdp-simcap-05.txt> as a Proposed 
>Standard.  This has been reviewed in the IETF but is not the product 
>of an IETF Working Group.
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the 
>iesg@ietf.org or ietf@ietf.org mailing lists by August 2, 2002.
>
>Files can be obtained via 
>http://www.ietf.org/internet-drafts/draft-andreasen-mmusic-sdp-simcap-05.txt
------- End of Forwarded Message


------- Forwarded Message
>To: IETF-Announce: ;
>From: The IESG <iesg-secretary@ietf.org>
>SUBJECT: Last Call: Grouping of m lines in SDP to Proposed Standard
>Date: Fri, 05 Jul 2002 15:51:06 -0400
>
>The IESG has received a request from the Multiparty Multimedia Session 
>Control Working Group to consider Grouping of m lines in SDP 
><draft-ietf-mmusic-fid-06.txt> as a Proposed Standard.  
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the 
>iesg@ietf.org or ietf@ietf.org mailing lists by August 2, 2002.
>
>Files can be obtained via 
>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-fid-06.txt
------- End of Forwarded Message

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


From mmusic-admin@ietf.org  Sat Jul  6 11:40:06 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 KAA22528
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 10:44:55 -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 KAA12234;
	Sat, 6 Jul 2002 10:41:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12202
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 10:41:50 -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 KAA22469
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 10:40:58 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g66EA2K5001273;
	Sat, 6 Jul 2002 10:10:02 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207061410.g66EA2K5001273@purple.nge.isi.edu>
To: fedemp@suidzer0.org
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines? 
In-Reply-To: Your message of "Sat, 06 Jul 2002 15:08:27 +0200."
             <4172.62.36.188.231.1025960907.squirrel@webmail.suidzer0.org> 
Date: Sat, 06 Jul 2002 10:10:02 -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

--> "Federico Montesino Pouzols" writes:
>>>	So I guess the first offset could be non zero only if the start
>>>time given in the corresponding t= line were shifted from the actual
>>> beginning of the session. I believe the first offset is always 0 and it
>>> could be omitted if backward compatibility were not a concern. Is it
>>> true?
>>
>> The ABNF in RFC 2327 does not require the leading zero.
>
>I see, the explicit zero does not fit the RFC ABNF. However
>I keep wondering the same question: is actually the first offset
>always zero? I mean, although the RFC ABNF does not mandate it, the
>text describing r= lines (the same in both RFC 2327 and
>draft-ietf-mmusic-sdp-new-10) seems to imply that the first offset is
>always zero. The examples and explanations given in both documents
>make me think that the first offset correponds to the beginning of the
>session (as opposed to the first time the session is resumed), thus
>being zero.
>
>	Is this interpretation right or is there any case in which the
>first offset can be non zero?

The first offset does correspond to the beginning of the session, and I
would expect it to be zero. There's no requirement for this though, and
a non-zero offset would change the start time of the session.

Colin

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


From mmusic-admin@ietf.org  Sat Jul  6 13:19:41 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 NAA25690
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 13:19:41 -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 NAA19455;
	Sat, 6 Jul 2002 13:14: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 NAA19426
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 13:14:10 -0400 (EDT)
Received: from Hardcore.suidzer0.org (aboukir-101-2-4-sudizero.adsl.nerim.net [62.212.111.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25436
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 13:12:59 -0400 (EDT)
Received: from suidzer0.org (localhost [127.0.0.1])
          by Hardcore.suidzer0.org (8.11.4/jtpda-5.3.3) with SMTP id g66HApw22192
          for <mmusic@ietf.org>; Sat, 6 Jul 2002 19:10:52 +0200
Received: from 62.36.176.107
        (SquirrelMail authenticated user fedemp)
        by webmail.suidzer0.org with HTTP;
        Sat, 6 Jul 2002 19:10:52 +0200 (CEST)
Message-ID: <4457.62.36.176.107.1025975452.squirrel@webmail.suidzer0.org>
Date: Sat, 6 Jul 2002 19:10:52 +0200 (CEST)
Subject: Re: [MMUSIC] A bug in SDP Syntax (CRLF)?
From: "Federico Montesino Pouzols" <fedemp@suidzer0.org>
To: <mmusic@ietf.org>
In-Reply-To: <200207061440.g66EeRK5001316@purple.nge.isi.edu>
References: Your
        message
        of
        "Sat,
        06
        Jul
        2002
        15:14:47
        +0200."
        <200207061440.g66EeRK5001316@purple.nge.isi.edu>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: fedemp@suidzer0.org
X-Mailer: SquirrelMail (version 1.2.7)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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

> SDP descriptions where the lines end in a single LF are incorrect. You
> may wish to design your parser such that it accepts them anyway - as
> suggested by the draft - but there is no requirement that you do this,
> and you could reject such descriptions.
>
> Colin

My doubt arises from the fact that the key word "SHOULD" is used in
the draft. So it seems more a recommendation than a slight
suggestion. Certainly, accepting single LFs is not a must but is is
not a MAY.

When I read the draft, I understand that I could reject descriptions
with single LFs, but only if there are "valid reasons in particular
circumstances...", as the SHOULD key word suggests.




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


From mmusic-admin@ietf.org  Sat Jul  6 13:21:12 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 NAA25853
	for <mmusic-archive@odin.ietf.org>; Sat, 6 Jul 2002 13:21:11 -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 NAA19584;
	Sat, 6 Jul 2002 13:18: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 NAA19549
	for <mmusic@optimus.ietf.org>; Sat, 6 Jul 2002 13:18:13 -0400 (EDT)
Received: from Hardcore.suidzer0.org (aboukir-101-2-4-sudizero.adsl.nerim.net [62.212.111.83])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25579
	for <mmusic@ietf.org>; Sat, 6 Jul 2002 13:17:07 -0400 (EDT)
Received: from suidzer0.org (localhost [127.0.0.1])
          by Hardcore.suidzer0.org (8.11.4/jtpda-5.3.3) with SMTP id g66HF0w22241
          for <mmusic@ietf.org>; Sat, 6 Jul 2002 19:15:00 +0200
Received: from 62.36.176.107
        (SquirrelMail authenticated user fedemp)
        by webmail.suidzer0.org with HTTP;
        Sat, 6 Jul 2002 19:15:00 +0200 (CEST)
Message-ID: <4460.62.36.176.107.1025975700.squirrel@webmail.suidzer0.org>
Date: Sat, 6 Jul 2002 19:15:00 +0200 (CEST)
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines?
From: "Federico Montesino Pouzols" <fedemp@suidzer0.org>
To: <mmusic@ietf.org>
In-Reply-To: <200207061410.g66EA2K5001273@purple.nge.isi.edu>
References: Your
        message
        of
        "Sat,
        06
        Jul
        2002
        15:08:27
        +0200."
        <200207061410.g66EA2K5001273@purple.nge.isi.edu>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: fedemp@suidzer0.org
X-Mailer: SquirrelMail (version 1.2.7)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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

> The first offset does correspond to the beginning of the session, and I
> would expect it to be zero. There's no requirement for this though, and
> a non-zero offset would change the start time of the session.
>
> Colin

Another question is if specifying the first offset is redundant. After
all, any value of the first offset may be added to the start time of
the corresponding t= line. Are the session start time and the repeat
sequence start time distinguished for any particular reason/purpose?




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


From mmusic-admin@ietf.org  Sun Jul  7 12:16:52 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 MAA24645
	for <mmusic-archive@odin.ietf.org>; Sun, 7 Jul 2002 12:16:52 -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 MAA12276;
	Sun, 7 Jul 2002 12:11: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 MAA12209
	for <mmusic@optimus.ietf.org>; Sun, 7 Jul 2002 12:11:15 -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 MAA24400;
	Sun, 7 Jul 2002 12:10:20 -0400 (EDT)
Message-Id: <200207071610.MAA24400@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: Sun, 07 Jul 2002 12:10:20 -0400
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdpng-trans-01.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.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: SDPng Transition
	Author(s)	: J. Ott, C. Perkins
	Filename	: draft-ietf-mmusic-sdpng-trans-01.txt
	Pages		: 12
	Date		: 05-Jul-02
	
The Session Description Protocol (SDP) is today widely used in the
Internet to announce as well as negotiate multimedia sessions and
exchange capabilities.  Having originally been designed for session
announcements only, as opposed to announcements and capabilities
negotiation announcements, native SDP lacks numerous features to be
applicable in many session scenarios.  Numerous extensions have been
developed to circumvent SDP's shortcomings -- but they have also
repeatedly shown its inherent limitations.  A successor protocol --
termed 'SDPng' for the time being -- is developed to address the
aforementioned needs of Internet applications in a more structured
manner.  With the huge installed base of SDP-based applications, a
migration path needs to be developed to move from SDP to SDPng over
time.  This document outlines how this migration can be achieved: in
general as well as for the various IETF control protocols that
potentially make use of SDP and SDPng.
This document is a product of the Multiparty Multimedia Session
Control (MMUSIC) working group of the Internet Engineering Task
Force.  Comments are solicited and should be addressed to the working
group's mailing list at mmusic@ietf.org and/or the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdpng-trans-01.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-ietf-mmusic-sdpng-trans-01.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdpng-trans-01.txt

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

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

--OtherAccess--

--NextPart--



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


From mmusic-admin@ietf.org  Sun Jul  7 16:45:46 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 QAA04869
	for <mmusic-archive@odin.ietf.org>; Sun, 7 Jul 2002 16:45:46 -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 QAA23142;
	Sun, 7 Jul 2002 16:40:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21139
	for <mmusic@optimus.ietf.org>; Fri, 5 Jul 2002 15:51:58 -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 PAA13858;
	Fri, 5 Jul 2002 15:51:06 -0400 (EDT)
Message-Id: <200207051951.PAA13858@ietf.org>
To: IETF-Announce: ;
Cc: mmusic@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Fri, 05 Jul 2002 15:51:06 -0400
Subject: [MMUSIC] Last Call: Grouping of m lines in SDP to Proposed Standard
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


The IESG has received a request from the Multiparty Multimedia Session 
Control Working Group to consider Grouping of m lines in SDP 
<draft-ietf-mmusic-fid-06.txt> as a Proposed Standard.  

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

Files can be obtained via 
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-fid-06.txt





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


From mmusic-admin@ietf.org  Mon Jul  8 11:07:46 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 LAA18524
	for <mmusic-archive@odin.ietf.org>; Mon, 8 Jul 2002 11:07:46 -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 LAA23206;
	Mon, 8 Jul 2002 11:04:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23173
	for <mmusic@optimus.ietf.org>; Mon, 8 Jul 2002 11:04:20 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18317
	for <mmusic@ietf.org>; Mon, 8 Jul 2002 11:03:27 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g68F4JrU008654
	for <mmusic@ietf.org>; Mon, 8 Jul 2002 17:04:19 +0200 (MEST)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.108]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NHMV54XZ; Mon, 8 Jul 2002 17:04:19 +0200
Message-ID: <3D29A9F3.1030006@era.ericsson.se>
Date: Mon, 08 Jul 2002 17:04:19 +0200
X-Sybari-Trust: 03bf4dd2 7216406a e4ad19be 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: IETF MMUSIC WG <mmusic@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Comments on draft-ietf-mmusic-sdp-srcfilter-01.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
Content-Transfer-Encoding: 7bit

Hi,

I have some comments about the draft.

Section 2 and Appendix A.
The definition of the filter attribute. Wouldn't it be better to define 
a short attribute name to the source filter instead of having two 
attributes called incl and excl? I would propose 
a=SF:<filter-mode>:<filter-spec>.

Section 2.2.
The media description 1 port number is not even, Please change to 54320 
which is a possible number. Also the payload type for video shoul be 
changed. A possible value would be 34 that are a static payload type for 
h.263 video.

Section 2.2.4
The example text is in contradiction with the processing rules in 
section 2.1. According to the processing rules all three src adresses 
(1.1.1.1, 2.2.2.2 and 3.3.3.3) are valid for any of the three multicast 
adresses.

Appendix A.

The definition of src-list i believe is in error. The addresses should 
not be seperate by email-safe but rather SP.

The definition from draft-ietf-mmusic-sdp-new-10.txt says:
email-safe =          1*(%x01-09/%x0B-0C/%x0E-27/
                         %x2A-3B/%x3D/%x3E-FF)
                      ;any byte except NUL, CR, LF, or the quoting
                      ;characters ()<>

Which includes lots of more charachters than space which is referenced 
in the text in section 2.

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 mmusic-admin@ietf.org  Mon Jul  8 11:48:07 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 LAA20688
	for <mmusic-archive@odin.ietf.org>; Mon, 8 Jul 2002 11:48: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 LAA26051;
	Mon, 8 Jul 2002 11:41:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26013
	for <mmusic@optimus.ietf.org>; Mon, 8 Jul 2002 11:41: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 LAA20219
	for <mmusic@ietf.org>; Mon, 8 Jul 2002 11:40:08 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g68FeT313247;
	Mon, 8 Jul 2002 11:40:41 -0400
Message-Id: <200207081540.g68FeT313247@chiron.nge.isi.edu>
To: fedemp@suidzer0.org
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] An error in SDP syntax regarding r= lines? 
In-Reply-To: Your message of "Sat, 06 Jul 2002 19:15:00 +0200."
             <4460.62.36.176.107.1025975700.squirrel@webmail.suidzer0.org> 
Date: Mon, 08 Jul 2002 11:40:29 -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

--> "Federico Montesino Pouzols" writes:
>> The first offset does correspond to the beginning of the session, and I
>> would expect it to be zero. There's no requirement for this though, and
>> a non-zero offset would change the start time of the session.
>>
>> Colin
>
>Another question is if specifying the first offset is redundant. After
>all, any value of the first offset may be added to the start time of
>the corresponding t= line. Are the session start time and the repeat
>sequence start time distinguished for any particular reason/purpose?

Huh? One indicates the start of the session, one indicates the repeat
offset. They're separate things.

Colin

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


From mmusic-admin@ietf.org  Mon Jul  8 15:27: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 PAA04448
	for <mmusic-archive@odin.ietf.org>; Mon, 8 Jul 2002 15:27:24 -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 PAA15730;
	Mon, 8 Jul 2002 15:23:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15573
	for <mmusic@optimus.ietf.org>; Mon, 8 Jul 2002 15:22:04 -0400 (EDT)
Received: from goobox (tog-wakko3.prognet.com [207.188.29.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04143
	for <mmusic@ietf.org>; Mon, 8 Jul 2002 15:21:10 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
  (uid 500)
  by goobox with local; Mon, 08 Jul 2002 12:21:43 -0700
>Return-Path: <rtspspec-bugs-admin@lists.sourceforge.net>
Received: from mail.real.com [207.188.7.41] by localhost with POP3 (fetchmail-5.9.6) for robla@localhost (single-drop); Mon, 08 Jul 2002 12:21:43 -0700 (PDT)
Received: from usw-sf-list2.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by real.com (8.12.2/8.12.2) with ESMTP id g68JJ8MA031470 for <robla@real.com>; Mon, 8 Jul 2002 12:19:08 -0700
Received: from usw-sf-list1-b.sourceforge.net ([10.3.1.13] helo=usw-sf-list1.sourceforge.net) by usw-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 17Re2P-0005tr-00 for <robla@real.com>; Mon, 08 Jul 2002 12:19:09 -0700
Date: Mon, 08 Jul 2002 12:18:41 -0700
From: rtspspec-bugs-request@lists.sourceforge.net
X-Mailer: Mailman v2.0.9-sf.net
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Old-To: rtspspec-bugs@lists.sourceforge.net
X-BeenThere: rtspspec-bugs@lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
Message-Id: <E17Re2P-0005tr-00@usw-sf-list2.sourceforge.net>
X-Spam-Status: No, hits=0.5 required=5.5 tests=NO_REAL_NAME version=2.31
X-UIDL: ff854ee17f738e4e5ff4614bea744c15
To: mmusic@ietf.org
Reply-to: mmusic@ietf.org
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #43 - 1 msg
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




This is an automatic digest of bugs submitted and changed on the RTSP bug tracker.  To see a list of bugs, visit:

http://sf.net/projects/rtspspec

When replying, please make your Subject line more specific than "Re: Rtspspec-bugs digest"



Today's Topics:

   1. [ rtspspec-Bugs-513758 ] Proxy-Require clarification (noreply@sourceforge.net)

--__--__--

Message: 1
To: noreply@sourceforge.net
From: noreply@sourceforge.net
Date: Sun, 07 Jul 2002 14:56:52 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-513758 ] Proxy-Require clarification

Bugs item #513758, was opened at 2002-02-06 06:16
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=513758&group_id=23194

Category: General
Group: Fix for DS - Need WG Input
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Rob Lanphier (robla)
Summary: Proxy-Require clarification

Initial Comment:
Today the proxy-require method says that the server should treat the proxy-require header 
identically as require. I don't understand how that mechanism work for paramters/functionallity that 
only the proxies should answer to. To avoid a negative acknowledgment the server must be aware 
of these parameters to not place them in the Unsupported header. I can't see that any proxy can 
modify the response as it will not know if the response comes from a proxy or a server. 

Can someone please clarify this?  

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

Comment By: Nobody/Anonymous (nobody)
Date: 2002-07-07 14:56

Message:
Logged In: NO 

gfjhn

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=513758&group_id=23194




End of Rtspspec-bugs Digest



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


From mmusic-admin@ietf.org  Mon Jul  8 20:43: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 UAA21093
	for <mmusic-archive@odin.ietf.org>; Mon, 8 Jul 2002 20:43:25 -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 UAA11419;
	Mon, 8 Jul 2002 20:38:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11388
	for <mmusic@optimus.ietf.org>; Mon, 8 Jul 2002 20:37:59 -0400 (EDT)
Received: from ns.live.com (ns.live.com [66.80.62.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20823
	for <mmusic@ietf.org>; Mon, 8 Jul 2002 20:37:06 -0400 (EDT)
Received: from ns.live.com (localhost.live.com [127.0.0.1])
	by ns.live.com (8.12.4/8.12.3) with ESMTP id g690baC2043171;
	Mon, 8 Jul 2002 17:37:36 -0700 (PDT)
	(envelope-from rsf@ns.live.com)
Received: (from rsf@localhost)
	by ns.live.com (8.12.4/8.12.3/Submit) id g690bZO9043170;
	Mon, 8 Jul 2002 17:37:35 -0700 (PDT)
Message-Id: <4.3.1.1.20020708172501.00b9b100@laptop-localhost>
X-Sender: rsf@laptop-localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 08 Jul 2002 17:36:02 -0700
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Ross Finlayson <finlayson@live.com>
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-sdp-srcfilter-01.txt
Cc: bquinn@celoxnetworks.com, rcq@sockets.com
In-Reply-To: <3D29A9F3.1030006@era.ericsson.se>
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

Magnus,

Thanks for the feedback.

>Section 2 and Appendix A.
>The definition of the filter attribute. Wouldn't it be better to define a 
>short attribute name to the source filter instead of having two attributes 
>called incl and excl? I would propose a=SF:<filter-mode>:<filter-spec>.

I'm not sure.  The syntax of "a=incl:" and "a=excl:" seems more consistent 
with that of other SDP attributes.  OTOH, they introduce two new attributes 
rather than one.  A possible alternative might be something like
         a=filter <filter-mode> <filter-spec>
where <filter-mode> is "incl" or "excl" (or "include" or "exclude").

Does anyone else have an opinion on this?


>Section 2.2.
>The media description 1 port number is not even, Please change to 54320 
>which is a possible number. Also the payload type for video shoul be 
>changed. A possible value would be 34 that are a static payload type for 
>h.263 video.

You're right - thanks for noting this.


>Section 2.2.4
>The example text is in contradiction with the processing rules in section 
>2.1. According to the processing rules all three src adresses (1.1.1.1, 
>2.2.2.2 and 3.3.3.3) are valid for any of the three multicast adresses.

Question for Bob (Quinn): Section 2.1 says
         "all unicast addresses in the <src-list> are valid sources for any
         of the multicast addresses in the address series implied by the
         <number of addresses>."
but the example in 2.2.4 contradicts this.  Which semantics did you intend?


>Appendix A.
>
>The definition of src-list i believe is in error. The addresses should not 
>be seperate by email-safe but rather SP.

Yes, I think so.

         Ross.


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


From mmusic-admin@ietf.org  Tue Jul  9 07:18: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 HAA19674
	for <mmusic-archive@odin.ietf.org>; Tue, 9 Jul 2002 07:18:30 -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 HAA24598;
	Tue, 9 Jul 2002 07:17:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA24568
	for <mmusic@optimus.ietf.org>; Tue, 9 Jul 2002 07:17:05 -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 HAA19577;
	Tue, 9 Jul 2002 07:16:08 -0400 (EDT)
Message-Id: <200207091116.HAA19577@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: Tue, 09 Jul 2002 07:16:08 -0400
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdpng-05.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.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Session Description and Capability Negotiation
	Author(s)	: D. Kutscher, J. Ott, C. Bormann
	Filename	: draft-ietf-mmusic-sdpng-05.txt
	Pages		: 78
	Date		: 08-Jul-02
	
This document defines a language for describing multimedia sessions
with respect to configuration parameters and capabilities of end
systems. 
This document is a product of the Multiparty Multimedia Session
Control (MMUSIC) working group of the Internet Engineering Task
Force. Comments are solicited and should be addressed to the working
group's mailing list at confctrl@isi.edu and/or the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdpng-05.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-ietf-mmusic-sdpng-05.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mmusic-sdpng-05.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:	<20020708101221.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdpng-05.txt

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

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

--OtherAccess--

--NextPart--



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


From mmusic-admin@ietf.org  Tue Jul  9 08: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 IAA20804
	for <mmusic-archive@odin.ietf.org>; Tue, 9 Jul 2002 08:00: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 HAA26664;
	Tue, 9 Jul 2002 07:59: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 HAA26594
	for <mmusic@optimus.ietf.org>; Tue, 9 Jul 2002 07:59:38 -0400 (EDT)
Received: from gw-nl4.philips.com (gw-nl4.philips.com [212.153.190.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20743;
	Tue, 9 Jul 2002 07:58:45 -0400 (EDT)
From: philippe.gentric@philips.com
Received: from smtpscan-nl4.philips.com (smtpscan-nl4.philips.com [130.139.36.24])
	by gw-nl4.philips.com (Postfix) with ESMTP
	id AD67C453B3; Tue,  9 Jul 2002 13:59:36 +0200 (MET DST)
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) 
	by smtpscan-nl4.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id NAA12130; Tue, 9 Jul 2002 13:59:36 +0200 (MET DST)
Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.45]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id NAA09731; Tue, 9 Jul 2002 13:59:35 +0200 (MET DST)
Subject: Re: [MMUSIC] Last Call: Grouping of m lines in SDP to Proposed Standard
To: mmusic@ietf.org
Cc: iesg@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF7DC0E1DF.D8D3DBD8-ONC1256BF1.0040EC20@diamond.philips.com>
Date: Tue, 9 Jul 2002 13:55:33 +0200
X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.9a |January 7, 2002) at
 09/07/2002 14:00:30
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



SDP evolutions do not only benefit SIP but also can affect other protocols (RTSP, SAP)
I am surprised that there is no mention/comment about that.



Philippe Gentric
Software Architect
Philips MP4Net
philippe.gentric@philips.com
http://www.mpeg-4.philips.com


                                                                                                                                       
                      The IESG                                                                                                         
                      <iesg-secretary@             To:  IETF-Announce:;                                                                
                      ietf.org>                    cc:  mmusic@ietf.org                                                                
                      Sent by:                      (bcc: Philippe Gentric/MP4-SUR/CE/PHILIPS)                                         
                      mmusic-admin@iet             Subject:   [MMUSIC] Last Call: Grouping of m lines in SDP to Proposed Standard      
                      f.org                                                                                                            
                                                   Classification:                                                                     
                                                                                                                                       
                      05/07/2002 21:51                                                                                                 
                      Please respond                                                                                                   
                      to iesg                                                                                                          
                                                                                                                                       
                                                                                                                                       





The IESG has received a request from the Multiparty Multimedia Session
Control Working Group to consider Grouping of m lines in SDP
<draft-ietf-mmusic-fid-06.txt> as a Proposed Standard.

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

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-fid-06.txt





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





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


From mmusic-admin@ietf.org  Tue Jul  9 12:53:27 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 MAA02948
	for <mmusic-archive@odin.ietf.org>; Tue, 9 Jul 2002 12:53:27 -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 MAA20739;
	Tue, 9 Jul 2002 12:50:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20702
	for <mmusic@optimus.ietf.org>; Tue, 9 Jul 2002 12:50:52 -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 MAA02832
	for <mmusic@ietf.org>; Tue, 9 Jul 2002 12:49:53 -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 g69GoaA09867;
	Tue, 9 Jul 2002 18:50:36 +0200 (MEST)
Message-ID: <3D2B14CC.746C4D27@tzi.uni-bremen.de>
Date: Tue, 09 Jul 2002 18:52:28 +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: mmusic@ietf.org
CC: csp@isi.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Draft MMUSIC Agenda for Yokohama
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

Folks,

please find below the draft agenda for the MMUSIC meeting
in Yokohama.  Please let us know if we have missed somebody.

Joerg



Agenda of the MMUSIC WG  at the 54th IETF
=========================================

Thursday, 18 July 2002, 0900 - 1130, Room 304
---------------------------------------------

0900    Agenda Bashing and Status update		(chairs, 15)

	Recent RFCs
        - draft-ietf-mmusic-sdp-offer-answer-02.txt -> RFC 3264
        - draft-ietf-mmusic-sdp-ipv6-03.txt	    -> RFC 3266

	In IESG Last Call
	- draft-ietf-mmusic-fid-06.txt
        - draft-andreasen-mmusic-sdp-simcap-05.txt
        - draft-ietf-mmusic-sdp-new-10.txt

	Other documents (pretty much finished)
	- draft-ietf-mmusic-sdp-comedia-03.txt
        - draft-ietf-mmusic-sdp4nat-02.txt
        - draft-ietf-mmusic-kmgmt-ext-05.txt

	Misc Updates
        - draft-ietf-mmusic-sdpng-trans-01.txt

0915	SDP Source Filters				(chairs, 5)
	- draft-ietf-mmusic-sdp-srcfilters-01.txt

0920    SDPng update					(Kutscher, 20)
        - draft-ietf-mmusic-sdpng-05.txt

0940	MMUSIC and Conference/Media Control		(chairs, 15)
	- draft-prandolini-mmusic-jpip-requirements-00.txt
	- draft-even-mmusic-video-media-control-00.txt

0955	SDP attributes for Video media Media Control	(Even, 15)
	- draft-even-mmusic-video-media-control-00.txt

1010    Metadata Update Protocol			(Nomura, 15)
	- draft-nomura-mmusic-pguide-requirements-00.txt
	- draft-nomura-cdi-mmusic-mupdate-00.txt

1025	Revised RTSP spec				(Lanphier, 60)
        - draft-ietf-mmusic-rfc2326bis-01.txt

1125	Wrap-up						(chairs, 5)

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


From mmusic-admin@ietf.org  Wed Jul 10 04:23: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 EAA24498
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 04:23: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 EAA06040;
	Wed, 10 Jul 2002 04:18: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 EAA06008
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 04:18:25 -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 EAA24395
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 04:17:30 -0400 (EDT)
Received: from danutf (dan.softtel.ro [192.168.0.27])
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with SMTP id g6A8I6004774;
	Wed, 10 Jul 2002 11:18:06 +0300
X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: mail.redlinecommunications.ro
Message-ID: <006301c227ea$a4ac9700$1b00a8c0@softtel.ro>
From: "Dan Firac" <danutf@redlinecommunications.ro>
To: <mmusic@ietf.org>
Cc: <csp@isi.edu>
Date: Wed, 10 Jul 2002 11:20:24 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0060_01C22803.C98450E0"
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
Subject: [MMUSIC] Small typos in draft-ietf-mmusic-sdp-new-10.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

This is a multi-part message in MIME format.

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

Hello all,

I found some small typos in SDP ABNF, and I have some suggetions.

1)
         email-safe =3D          1*(%x01-09/%x0B-0C/%x0E-27/
                                     %x2A-3B/%x3D/%x3E-FF)
                                    ;any byte except NUL, CR, LF, or the =
quoting
                                    ;characters ()<>

The '>' character is 0x3E, so the last alternative should be %x3F-FF.

2) As shown above email-safe is one or more, let's say, =
email-safe-chars.
This definition of email-safe appears in the following definitions:
         email-address =3D     email *SP "(" 1*email-safe ")" /
                                     1*email-safe "<" email ">" /
                                      email
         ...
         phone-number =3D    phone *SP "(" 1*email-safe ")" /
                                     1*email-safe "<" phone ">" /
                                     phone

And it is used as one ore more email-safe. Something is redundant here.
In order to modify less, I think email-safe definition should be:
         email-safe =3D          %x01-09/%x0B-0C/%x0E-27/
                                     %x2A-3B/%x3D/%x3F-FF

3) In order to be more clear 'email-safe' name could be changed to =
'email-safe-char' (IMHO).

4) For clarification reasons, you should include a definition for =
'decimal-uchar', as it is not
a core ANBF type.
It is used as:
           b1 =3D                  decimal-uchar
                                    ; less than "224"; not "0" or "127"
Its definition is simple, but should be included.
I think it might look like:
           decimal-uchar =3D   DIGIT / POS-DIGIT DIGIT /
                                     ("1" 2DIGIT) /=20
                                     ("2" ("0"/"1"/"2"/"3"/"4" ) DIGIT) =
/
                                     ("25" ("0"/"1"/"2"/"3"/"4"/"5"))

If I am wrong with 2), please correct me.

Best regards,
Dan Firac
Software Engineer,
Redline Communications,
Romania.
Phone: +40 723 260 623



------=_NextPart_000_0060_01C22803.C98450E0
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>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I found&nbsp;some small typos in SDP =
ABNF, and I=20
have some suggetions.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>1)</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email-safe=20
=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1*(%x01-09/%x0B-0C/%x0E-27/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
%x2A-3B/%x3D/%x3E-FF)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
&nbsp;;any byte except NUL, CR, LF, or the=20
quoting<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
;characters ()&lt;&gt;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>The '&gt;' character is 0x3E, so the last alternative should be=20
%x3F-FF.</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2) As shown above email-safe is one or =
more, let's=20
say, email-safe-chars.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This definition of =
email-safe&nbsp;appears in the=20
following definitions:</FONT></DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;email-address =

=3D&nbsp;&nbsp;&nbsp;&nbsp; email *SP "(" 1*email-safe ")"=20
/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
1*email-safe "&lt;" email "&gt;"=20
/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

email<BR><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
...</FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;phone=
-number=20
=3D&nbsp;&nbsp;&nbsp; phone *SP "(" 1*email-safe ")"=20
/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

1*email-safe "&lt;" phone "&gt;"=20
/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
phone<BR><BR><FONT face=3DArial size=3D2>And it is used as one ore more =
email-safe.=20
Something is redundant here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In order to modify less, I think =
email-safe=20
definition should be:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email-safe=20
=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
%x01-09/%x0B-0C/%x0E-27/<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
%x2A-3B/%x3D/%x3F-FF<BR></DIV>
<DIV><FONT face=3DArial size=3D2>3) In order to be more clear =
'email-safe' name=20
could be changed to 'email-safe-char' (IMHO).</FONT></DIV><FONT =
face=3DArial=20
size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>4)&nbsp;For clarification reasons, you =
should=20
include a definition for 'decimal-uchar', as it is not</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>a core ANBF type.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It is used as:</FONT></DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b1=20
=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
decimal-uchar<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; less than =
"224";=20
not "0" or "127"<BR><FONT face=3DArial size=3D2>Its definition is =
simple, but should=20
be included.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think it&nbsp;might&nbsp;look =
like:</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
decimal-uchar =3D&nbsp;&nbsp; DIGIT / POS-DIGIT DIGIT /</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><FONT=20
face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
face=3DArial=20
size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
("1" 2DIGIT) / </FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
("2" ("0"/"1"/"2"/"3"/"4" ) DIGIT) /</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
("25"=20
("0"/"1"/"2"/"3"/"4"/"5"))</FONT><BR></DIV>
<DIV><FONT face=3DArial size=3D2>If I am wrong with&nbsp;2), please =
correct=20
me.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Dan Firac</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Software Engineer,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Redline Communications,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Romania.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Phone: +40 723 260 623</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0060_01C22803.C98450E0--


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


From mmusic-admin@ietf.org  Wed Jul 10 08:34:58 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 IAA29590
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 08:34: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 IAA19987;
	Wed, 10 Jul 2002 08:30: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 IAA19939
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 08:30:09 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29291
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 08:29:14 -0400 (EDT)
From: emre.aksu@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6ACUci03464
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 15:30:38 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c018cf5d2ac158f23078@esvir03nok.nokia.com> for <mmusic@ietf.org>;
 Wed, 10 Jul 2002 15:30:06 +0300
Received: from esebe012.NOE.Nokia.com ([172.21.138.51]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 15:30:03 +0300
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe012.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 15:30:03 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 10 Jul 2002 15:30:03 +0300
Message-ID: <B519AC26B144EF479CFB036F7B84E7C8117ED4@trebe006.NOE.Nokia.com>
Thread-Topic: OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
Thread-Index: AcIoDYvQmeIVRZM6EdatiwDQt2aNIw==
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 10 Jul 2002 12:30:03.0453 (UTC) FILETIME=[8406F6D0:01C2280D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA19945
Subject: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
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,
 
I have a question related to the RTSP OPTIONS method.
In the latest draft of RTSP RFC and also in the RFC 2326, in Table 2, OPTIONS method requirement is listed as follows:
 
 method            direction        object     requirement
 
OPTIONS           C->S, S->C       P,S        required  (S->C: optional)
 
In the Annex D.1 , minimal RTSP Client implementation, OPTIONS method is not included to the list of methods which MUST be implemented. 
 
So, My question is: How should this be interpreted? According to Table 2, OPTIONS method looks like to be mandated at least in the C->S direction. But this seems to conflict with the minimal implementation. If Table.2 does not apply to the minimal implementation, how should Table 2 be interpreted? I would really appreciate if this could be clarified.
 
I would also like to point out the usefulness of OPTIONS, especially for checking the 'session aliveness' according to the latest draft...
 
BR
Emre
 



Emre Baris Aksu
Senior Design Engineer

Nokia Mobile Phones
Tampere / Finland
e-mail : emre.aksu@nokia.com
Mobile : +358 40 743 1972
Fax    : +358 7180 70504





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


From mmusic-admin@ietf.org  Wed Jul 10 10:16: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 KAA03747
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 10:16: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 KAA27857;
	Wed, 10 Jul 2002 10:10:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27824
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 10:10:20 -0400 (EDT)
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 KAA03222
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 10:09:24 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g6AEAGRb003544;
	Wed, 10 Jul 2002 16:10:16 +0200 (MEST)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.108]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3SKD6VX1; Wed, 10 Jul 2002 16:10:16 +0200
Message-ID: <3D2C4048.50409@era.ericsson.se>
Date: Wed, 10 Jul 2002 16:10:16 +0200
X-Sybari-Trust: 5331a260 7216406a e4ad19be 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: emre.aksu@nokia.com
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
References: <B519AC26B144EF479CFB036F7B84E7C8117ED4@trebe006.NOE.Nokia.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

Hi Emre,

Table 2 is actually rather unclear regarding the requirement levels. It 
does not specify which entity the requirements concern. If you would 
read both the clients and the server minimal implementation requirements 
you would find a difference. The server is required to implement the 
options method while the client is not.

So follow annex D and be aware that the table is incomplete. It is 
necessary to do something about it.

I agree that options is very useful and all clients are recommended to 
implement it. I would say that options is the third or fourth variant of 
doing keep alive on my list after RTCP and PING and in hard combat with 
SET_PARAMETER. It main purpose however is capability discovery.

Regards

Magnus

emre.aksu@nokia.com wrote:

>Hello,
> 
>I have a question related to the RTSP OPTIONS method.
>In the latest draft of RTSP RFC and also in the RFC 2326, in Table 2, OPTIONS method requirement is listed as follows:
> 
> method            direction        object     requirement
> 
>OPTIONS           C->S, S->C       P,S        required  (S->C: optional)
> 
>In the Annex D.1 , minimal RTSP Client implementation, OPTIONS method is not included to the list of methods which MUST be implemented. 
> 
>So, My question is: How should this be interpreted? According to Table 2, OPTIONS method looks like to be mandated at least in the C->S direction. But this seems to conflict with the minimal implementation. If Table.2 does not apply to the minimal implementation, how should Table 2 be interpreted? I would really appreciate if this could be clarified.
> 
>I would also like to point out the usefulness of OPTIONS, especially for checking the 'session aliveness' according to the latest draft...
> 
>BR
>Emre
> 
>
>
>
>Emre Baris Aksu
>Senior Design Engineer
>
>Nokia Mobile Phones
>Tampere / Finland
>e-mail : emre.aksu@nokia.com
>Mobile : +358 40 743 1972
>Fax    : +358 7180 70504
>
>
>
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>

-- 

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 mmusic-admin@ietf.org  Wed Jul 10 10:25:11 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 KAA04118
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 10:25:11 -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 KAA29797;
	Wed, 10 Jul 2002 10:23: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 KAA29761
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 10:23:25 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04056
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 10:22:29 -0400 (EDT)
From: emre.aksu@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6AENei04959
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 17:23:40 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c01f472cfac158f24077@esvir04nok.ntc.nokia.com> for <mmusic@ietf.org>;
 Wed, 10 Jul 2002 17:23:08 +0300
Received: from esebe003.NOE.Nokia.com ([172.21.138.39]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 17:23:08 +0300
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 17:23:07 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
Date: Wed, 10 Jul 2002 17:23:07 +0300
Message-ID: <B519AC26B144EF479CFB036F7B84E7C8A124F4@trebe006.NOE.Nokia.com>
Thread-Topic: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
Thread-Index: AcIoHVeImeIVhpM6EdatiwDQt2aNIw==
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 10 Jul 2002 14:23:07.0746 (UTC) FILETIME=[4FC7EC20:01C2281D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA29762
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 Magnus,

Thanhs for the quick answer. The reason why I asked this mainly is that, I don't actually know an RTSP client which didn't implement OPTIONS :-) (by implementing, I mean which can send OPTIONS request). So, wouldn't it be better to make it required also for the minimal implementation on the client side?

I also think that it is a quite clean solution to use OPTIONS with Session-Id to check/keep session aliveness. I remember the big discussions about this in this reflector, and I don't intend open them again :-). Just to keep in mind, in 3GPP Packet Switched Streaming Service definitions, RTCP and OPTIONS are the preferred methods for session aliveness checking, in the given preference order. (Ref: Section A.2.2.2.2 in document TS 26.234 v4.40 (Release 4) and v5.10 (Release 5)).

Best Regards,

Emre

 

 

> -----Original Message-----

> From: ext Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]

> Sent: 10. July 2002 17:10

> To: Aksu Emre (NMP/Tampere)

> Cc: mmusic@ietf.org

> Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not in

> minimal client and server implementations?

> 

> 

> Hi Emre,

> 

> Table 2 is actually rather unclear regarding the requirement 

> levels. It 

> does not specify which entity the requirements concern. If you would 

> read both the clients and the server minimal implementation 

> requirements 

> you would find a difference. The server is required to implement the 

> options method while the client is not.

> 

> So follow annex D and be aware that the table is incomplete. It is 

> necessary to do something about it.

> 

> I agree that options is very useful and all clients are 

> recommended to 

> implement it. I would say that options is the third or fourth 

> variant of 

> doing keep alive on my list after RTCP and PING and in hard 

> combat with 

> SET_PARAMETER. It main purpose however is capability discovery.

> 

> Regards

> 

> Magnus

> 

> emre.aksu@nokia.com wrote:

> 

> >Hello,

> > 

> >I have a question related to the RTSP OPTIONS method.

> >In the latest draft of RTSP RFC and also in the RFC 2326, in 

> Table 2, OPTIONS method requirement is listed as follows:

> > 

> > method direction object requirement

> > 

> >OPTIONS C->S, S->C P,S required 

> (S->C: optional)

> > 

> >In the Annex D.1 , minimal RTSP Client implementation, 

> OPTIONS method is not included to the list of methods which 

> MUST be implemented. 

> > 

> >So, My question is: How should this be interpreted? 

> According to Table 2, OPTIONS method looks like to be 

> mandated at least in the C->S direction. But this seems to 

> conflict with the minimal implementation. If Table.2 does not 

> apply to the minimal implementation, how should Table 2 be 

> interpreted? I would really appreciate if this could be clarified.

> > 

> >I would also like to point out the usefulness of OPTIONS, 

> especially for checking the 'session aliveness' according to 

> the latest draft...

> > 

> >BR

> >Emre

> > 

> >

> >

> >

> >Emre Baris Aksu

> >Senior Design Engineer

> >

> >Nokia Mobile Phones

> >Tampere / Finland

> >e-mail : emre.aksu@nokia.com

> >Mobile : +358 40 743 1972

> >Fax : +358 7180 70504

> >

> >

> >

> >

> >

> >_______________________________________________

> >mmusic mailing list

> >mmusic@ietf.org

> >https://www1.ietf.org/mailman/listinfo/mmusic

> >

> 

> -- 

> 

> 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

> 


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


From mmusic-admin@ietf.org  Wed Jul 10 11:47: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 LAA07895
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 11:47:16 -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 LAA10078;
	Wed, 10 Jul 2002 11:44:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10047
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 11:44:41 -0400 (EDT)
Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07776
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 11:43:45 -0400 (EDT)
Received: from real.com (murrow2k1.real.com [207.188.7.41])
	by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g6AFi0KR007436;
	Wed, 10 Jul 2002 08:44:00 -0700
Received: from A7397.real.com ([172.22.124.125])
	by real.com (8.12.2/8.12.2) with ESMTP id g6AFi0MB032133;
	Wed, 10 Jul 2002 08:44:00 -0700
Message-Id: <5.1.0.14.2.20020710082644.0411ae60@mail.real.com>
X-Sender: jworley@mail.real.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 10 Jul 2002 08:41:43 -0700
To: emre.aksu@nokia.com, <mmusic@ietf.org>
From: Jeremy Worley <jworley@real.com>
Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not
  in minimal client and server implementations?
In-Reply-To: <B519AC26B144EF479CFB036F7B84E7C8A124F4@trebe006.NOE.Nokia.
 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

Hello Emre,

At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
>Hi Magnus,
>
>Thanhs for the quick answer. The reason why I asked this mainly is that, I 
>don't actually know an RTSP client which didn't implement OPTIONS :-) (by 
>implementing, I mean which can send OPTIONS request). So, wouldn't it be 
>better to make it required also for the minimal implementation on the 
>client side?

I agree most clients implement sending of OPTIONS requests.  It also common 
for clients to not implement OPTIONS response.  The rationale for not 
requiring to send OPTIONS requests on the client is OK in my opinion 
because it is usually used to query features that a server implements.  If 
the client does not use any optional features, then it has no need to send 
an OPTIONS request, and so it would not need to implement sending of 
OPTIONS.  On the other hand, if the client uses optional RTSP features, 
then it must implement an OPTIONS request.

I agree with Magnus that Table 2 should be clarified to describe what must 
be implemented as both requests and responses by client and server.


>I also think that it is a quite clean solution to use OPTIONS with 
>Session-Id to check/keep session aliveness. I remember the big discussions 
>about this in this reflector, and I don't intend open them again :-). Just 
>to keep in mind, in 3GPP Packet Switched Streaming Service definitions, 
>RTCP and OPTIONS are the preferred methods for session aliveness checking, 
>in the given preference order. (Ref: Section A.2.2.2.2 in document TS 
>26.234 v4.40 (Release 4) and v5.10 (Release 5)).

When the new RTSP draft becomes an RFC, we may want to add PING to the list 
of methods for checking session aliveness in 26.234.  In such a scenario, I 
think PING might be preferred over OPTIONS.

Thanks,
         Jeremy


>Best Regards,
>
>Emre
>
>
>
>
>
> > -----Original Message-----
>
> > From: ext Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]
>
> > Sent: 10. July 2002 17:10
>
> > To: Aksu Emre (NMP/Tampere)
>
> > Cc: mmusic@ietf.org
>
> > Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not in
>
> > minimal client and server implementations?
>
> >
>
> >
>
> > Hi Emre,
>
> >
>
> > Table 2 is actually rather unclear regarding the requirement
>
> > levels. It
>
> > does not specify which entity the requirements concern. If you would
>
> > read both the clients and the server minimal implementation
>
> > requirements
>
> > you would find a difference. The server is required to implement the
>
> > options method while the client is not.
>
> >
>
> > So follow annex D and be aware that the table is incomplete. It is
>
> > necessary to do something about it.
>
> >
>
> > I agree that options is very useful and all clients are
>
> > recommended to
>
> > implement it. I would say that options is the third or fourth
>
> > variant of
>
> > doing keep alive on my list after RTCP and PING and in hard
>
> > combat with
>
> > SET_PARAMETER. It main purpose however is capability discovery.
>
> >
>
> > Regards
>
> >
>
> > Magnus
>
> >
>
> > emre.aksu@nokia.com wrote:
>
> >
>
> > >Hello,
>
> > >
>
> > >I have a question related to the RTSP OPTIONS method.
>
> > >In the latest draft of RTSP RFC and also in the RFC 2326, in
>
> > Table 2, OPTIONS method requirement is listed as follows:
>
> > >
>
> > > method direction object requirement
>
> > >
>
> > >OPTIONS C->S, S->C P,S required
>
> > (S->C: optional)
>
> > >
>
> > >In the Annex D.1 , minimal RTSP Client implementation,
>
> > OPTIONS method is not included to the list of methods which
>
> > MUST be implemented.
>
> > >
>
> > >So, My question is: How should this be interpreted?
>
> > According to Table 2, OPTIONS method looks like to be
>
> > mandated at least in the C->S direction. But this seems to
>
> > conflict with the minimal implementation. If Table.2 does not
>
> > apply to the minimal implementation, how should Table 2 be
>
> > interpreted? I would really appreciate if this could be clarified.
>
> > >
>
> > >I would also like to point out the usefulness of OPTIONS,
>
> > especially for checking the 'session aliveness' according to
>
> > the latest draft...
>
> > >
>
> > >BR
>
> > >Emre
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >Emre Baris Aksu
>
> > >Senior Design Engineer
>
> > >
>
> > >Nokia Mobile Phones
>
> > >Tampere / Finland
>
> > >e-mail : emre.aksu@nokia.com
>
> > >Mobile : +358 40 743 1972
>
> > >Fax : +358 7180 70504
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >_______________________________________________
>
> > >mmusic mailing list
>
> > >mmusic@ietf.org
>
> > >https://www1.ietf.org/mailman/listinfo/mmusic
>
> > >
>
> >
>
> > --
>
> >
>
> > 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
>
> >
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


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


From mmusic-admin@ietf.org  Wed Jul 10 12:09:07 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 MAA08972
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 12:09: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 MAA14574;
	Wed, 10 Jul 2002 12:05: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 MAA14536
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 12:05:47 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08739
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 12:04:50 -0400 (EDT)
From: emre.aksu@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6AG6Di23671
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 19:06:13 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c02525897ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 10 Jul 2002 19:05:42 +0300
Received: from esebe012.NOE.Nokia.com ([172.21.138.51]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 19:05:42 +0300
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe012.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 10 Jul 2002 19:05:41 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
Date: Wed, 10 Jul 2002 19:05:41 +0300
Message-ID: <B519AC26B144EF479CFB036F7B84E7C8117ED8@trebe006.NOE.Nokia.com>
Thread-Topic: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not in minimal client and server implementations?
Thread-Index: AcIoKLYkY+wI6W4TRROxQFBAKqn2CAAASMAw
To: <jworley@real.com>, <mmusic@ietf.org>
X-OriginalArrivalTime: 10 Jul 2002 16:05:41.0444 (UTC) FILETIME=[A3ABB840:01C2282B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA14537
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 Jeremy,
Please find my comments inlined:

> -----Original Message-----
> From: ext Jeremy Worley [mailto:jworley@real.com]
> Sent: 10. July 2002 18:42
> To: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it 
> required or not
> in minimal client and server implementations?
> 
> 
> Hello Emre,
> 
> At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> >Hi Magnus,
> >
> >Thanhs for the quick answer. The reason why I asked this 
> mainly is that, I 
> >don't actually know an RTSP client which didn't implement 
> OPTIONS :-) (by 
> >implementing, I mean which can send OPTIONS request). So, 
> wouldn't it be 
> >better to make it required also for the minimal 
> implementation on the 
> >client side?
> 
> I agree most clients implement sending of OPTIONS requests.  
> It also common 
> for clients to not implement OPTIONS response. 

I agree with this. But in such a case, at least a "Not implemented" error status message has to be sent by the client to the server, right? In fact, my intention was to have the request to be a mandated requirement for the client. For the response to OPTIONS on the cliet side, I agree it can be optional as an implementation. 

> The rationale for not 
> requiring to send OPTIONS requests on the client is OK in my opinion 
> because it is usually used to query features that a server 
> implements.  If 
> the client does not use any optional features, then it has no 
> need to send 
> an OPTIONS request, and so it would not need to implement sending of 
> OPTIONS.  On the other hand, if the client uses optional RTSP 
> features, 
> then it must implement an OPTIONS request.
> 

I see your point, but this is quite a statement, which I believe should be present in the RFC then. Also, the minimal implementation for server and client has some 'or' statements in it (for example for RECORD and PLAY method), which I believe, means that different sets of minimal implementations are possible, and a client has to check which set of implemenentation the server supports, even if the server is assumed to be a minimal implementation in the very beginning.

> I agree with Magnus that Table 2 should be clarified to 
> describe what must 
> be implemented as both requests and responses by client and server.
> 
> 
> >I also think that it is a quite clean solution to use OPTIONS with 
> >Session-Id to check/keep session aliveness. I remember the 
> big discussions 
> >about this in this reflector, and I don't intend open them 
> again :-). Just 
> >to keep in mind, in 3GPP Packet Switched Streaming Service 
> definitions, 
> >RTCP and OPTIONS are the preferred methods for session 
> aliveness checking, 
> >in the given preference order. (Ref: Section A.2.2.2.2 in 
> document TS 
> >26.234 v4.40 (Release 4) and v5.10 (Release 5)).
> 
> When the new RTSP draft becomes an RFC, we may want to add 
> PING to the list 
> of methods for checking session aliveness in 26.234.  In such 
> a scenario, I 
> think PING might be preferred over OPTIONS.
> 

I agree, PING is a very good choice and I believe it will definitely find its place in the 3GPP spec. I have one question though. Can PING method identify a streaming session?. What I exactly mean is that, can a PING request bear a Session-ID?

Best Regards,
Emre



> Thanks,
>          Jeremy
> 
> 
> >Best Regards,
> >
> >Emre
> >
> >
> >
> >
> >
> > > -----Original Message-----
> >
> > > From: ext Magnus Westerlund 
> [mailto:magnus.westerlund@era.ericsson.se]
> >
> > > Sent: 10. July 2002 17:10
> >
> > > To: Aksu Emre (NMP/Tampere)
> >
> > > Cc: mmusic@ietf.org
> >
> > > Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it 
> required or not in
> >
> > > minimal client and server implementations?
> >
> > >
> >
> > >
> >
> > > Hi Emre,
> >
> > >
> >
> > > Table 2 is actually rather unclear regarding the requirement
> >
> > > levels. It
> >
> > > does not specify which entity the requirements concern. 
> If you would
> >
> > > read both the clients and the server minimal implementation
> >
> > > requirements
> >
> > > you would find a difference. The server is required to 
> implement the
> >
> > > options method while the client is not.
> >
> > >
> >
> > > So follow annex D and be aware that the table is incomplete. It is
> >
> > > necessary to do something about it.
> >
> > >
> >
> > > I agree that options is very useful and all clients are
> >
> > > recommended to
> >
> > > implement it. I would say that options is the third or fourth
> >
> > > variant of
> >
> > > doing keep alive on my list after RTCP and PING and in hard
> >
> > > combat with
> >
> > > SET_PARAMETER. It main purpose however is capability discovery.
> >
> > >
> >
> > > Regards
> >
> > >
> >
> > > Magnus
> >
> > >
> >
> > > emre.aksu@nokia.com wrote:
> >
> > >
> >
> > > >Hello,
> >
> > > >
> >
> > > >I have a question related to the RTSP OPTIONS method.
> >
> > > >In the latest draft of RTSP RFC and also in the RFC 2326, in
> >
> > > Table 2, OPTIONS method requirement is listed as follows:
> >
> > > >
> >
> > > > method direction object requirement
> >
> > > >
> >
> > > >OPTIONS C->S, S->C P,S required
> >
> > > (S->C: optional)
> >
> > > >
> >
> > > >In the Annex D.1 , minimal RTSP Client implementation,
> >
> > > OPTIONS method is not included to the list of methods which
> >
> > > MUST be implemented.
> >
> > > >
> >
> > > >So, My question is: How should this be interpreted?
> >
> > > According to Table 2, OPTIONS method looks like to be
> >
> > > mandated at least in the C->S direction. But this seems to
> >
> > > conflict with the minimal implementation. If Table.2 does not
> >
> > > apply to the minimal implementation, how should Table 2 be
> >
> > > interpreted? I would really appreciate if this could be clarified.
> >
> > > >
> >
> > > >I would also like to point out the usefulness of OPTIONS,
> >
> > > especially for checking the 'session aliveness' according to
> >
> > > the latest draft...
> >
> > > >
> >
> > > >BR
> >
> > > >Emre
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >Emre Baris Aksu
> >
> > > >Senior Design Engineer
> >
> > > >
> >
> > > >Nokia Mobile Phones
> >
> > > >Tampere / Finland
> >
> > > >e-mail : emre.aksu@nokia.com
> >
> > > >Mobile : +358 40 743 1972
> >
> > > >Fax : +358 7180 70504
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >_______________________________________________
> >
> > > >mmusic mailing list
> >
> > > >mmusic@ietf.org
> >
> > > >https://www1.ietf.org/mailman/listinfo/mmusic
> >
> > > >
> >
> > >
> >
> > > --
> >
> > >
> >
> > > 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
> >
> > >
> >
> >
> >_______________________________________________
> >mmusic mailing list
> >mmusic@ietf.org
> >https://www1.ietf.org/mailman/listinfo/mmusic
> 
> 

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


From mmusic-admin@ietf.org  Wed Jul 10 13:22: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 NAA12010
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 13:22:25 -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 NAA22089;
	Wed, 10 Jul 2002 13:19: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 NAA22051
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 13:19:00 -0400 (EDT)
Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11892
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 13:18:05 -0400 (EDT)
Received: from real.com (murrow2k1.real.com [207.188.7.41])
	by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g6AHIKKR016330;
	Wed, 10 Jul 2002 10:18:20 -0700
Received: from A7397.real.com ([172.22.124.125])
	by real.com (8.12.2/8.12.2) with ESMTP id g6AHIEMB028382;
	Wed, 10 Jul 2002 10:18:19 -0700
Message-Id: <5.1.0.14.2.20020710095355.0301f7e0@mail.real.com>
X-Sender: jworley@mail.real.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 10 Jul 2002 10:14:47 -0700
To: <emre.aksu@nokia.com>, <mmusic@ietf.org>
From: Jeremy Worley <jworley@real.com>
Subject: RE: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not
  in minimal client and server implementations?
In-Reply-To: <B519AC26B144EF479CFB036F7B84E7C8117ED8@trebe006.NOE.Nokia.
 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 Emre,

At 07:05 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
>Hi Jeremy,
>Please find my comments inlined:
>
> > -----Original Message-----
> > From: ext Jeremy Worley [mailto:jworley@real.com]
> > Sent: 10. July 2002 18:42
> > To: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> > Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it
> > required or not
> > in minimal client and server implementations?
> >
> >
> > Hello Emre,
> >
> > At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> > >Hi Magnus,
> > >
> > >Thanhs for the quick answer. The reason why I asked this
> > mainly is that, I
> > >don't actually know an RTSP client which didn't implement
> > OPTIONS :-) (by
> > >implementing, I mean which can send OPTIONS request). So,
> > wouldn't it be
> > >better to make it required also for the minimal
> > implementation on the
> > >client side?
> >
> > I agree most clients implement sending of OPTIONS requests.
> > It also common
> > for clients to not implement OPTIONS response.
>
>I agree with this. But in such a case, at least a "Not implemented" error 
>status message has to be sent by the client to the server, right? In fact, 
>my intention was to have the request to be a mandated requirement for the 
>client. For the response to OPTIONS on the cliet side, I agree it can be 
>optional as an implementation.

I agree that the client should respond if it does not support responding to 
a server OPTIONS request.

My opinion is that if the client does not use optional features, then it 
should not have to issue an OPTIONS request.


> > The rationale for not
> > requiring to send OPTIONS requests on the client is OK in my opinion
> > because it is usually used to query features that a server
> > implements.  If
> > the client does not use any optional features, then it has no
> > need to send
> > an OPTIONS request, and so it would not need to implement sending of
> > OPTIONS.  On the other hand, if the client uses optional RTSP
> > features,
> > then it must implement an OPTIONS request.
> >
>
>I see your point, but this is quite a statement, which I believe should be 
>present in the RFC then. Also, the minimal implementation for server and 
>client has some 'or' statements in it (for example for RECORD and PLAY 
>method), which I believe, means that different sets of minimal 
>implementations are possible, and a client has to check which set of 
>implemenentation the server supports, even if the server is assumed to be 
>a minimal implementation in the very beginning.

You raise an interesting point.  Table 2 of 2326 and 2326bis states that 
RECORD is optional and PLAY is mandatory for the client.  However D.1 and 
D.2 appear to state that it is required that either PLAY or RECORD can be 
implemented.  RECORD is described as an optional feature in several places 
in 2326 (e.g., 1.5, 10.11, table 2).  I think in this case, it makes sense 
to make Section D consistent with the rest of the document.


> > I agree with Magnus that Table 2 should be clarified to
> > describe what must
> > be implemented as both requests and responses by client and server.
> >
> >
> > >I also think that it is a quite clean solution to use OPTIONS with
> > >Session-Id to check/keep session aliveness. I remember the
> > big discussions
> > >about this in this reflector, and I don't intend open them
> > again :-). Just
> > >to keep in mind, in 3GPP Packet Switched Streaming Service
> > definitions,
> > >RTCP and OPTIONS are the preferred methods for session
> > aliveness checking,
> > >in the given preference order. (Ref: Section A.2.2.2.2 in
> > document TS
> > >26.234 v4.40 (Release 4) and v5.10 (Release 5)).
> >
> > When the new RTSP draft becomes an RFC, we may want to add
> > PING to the list
> > of methods for checking session aliveness in 26.234.  In such
> > a scenario, I
> > think PING might be preferred over OPTIONS.
> >
>
>I agree, PING is a very good choice and I believe it will definitely find 
>its place in the 3GPP spec. I have one question though. Can PING method 
>identify a streaming session?. What I exactly mean is that, can a PING 
>request bear a Session-ID?

Table 4 in the draft states that the Session header mandatory for 
PING.  Interestingly, the example transaction in 10.12 does not include a 
Session header.  That example should be modified to include a Session header.

A minor editorial note: table 4 also seems to have floated to a later 
section of the document in the current draft.  That should be cleaned up in 
the next draft.

Best,
         Jeremy


>Best Regards,
>Emre
>
>
>
> > Thanks,
> >          Jeremy
> >
> >
> > >Best Regards,
> > >
> > >Emre
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > >
> > > > From: ext Magnus Westerlund
> > [mailto:magnus.westerlund@era.ericsson.se]
> > >
> > > > Sent: 10. July 2002 17:10
> > >
> > > > To: Aksu Emre (NMP/Tampere)
> > >
> > > > Cc: mmusic@ietf.org
> > >
> > > > Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it
> > required or not in
> > >
> > > > minimal client and server implementations?
> > >
> > > >
> > >
> > > >
> > >
> > > > Hi Emre,
> > >
> > > >
> > >
> > > > Table 2 is actually rather unclear regarding the requirement
> > >
> > > > levels. It
> > >
> > > > does not specify which entity the requirements concern.
> > If you would
> > >
> > > > read both the clients and the server minimal implementation
> > >
> > > > requirements
> > >
> > > > you would find a difference. The server is required to
> > implement the
> > >
> > > > options method while the client is not.
> > >
> > > >
> > >
> > > > So follow annex D and be aware that the table is incomplete. It is
> > >
> > > > necessary to do something about it.
> > >
> > > >
> > >
> > > > I agree that options is very useful and all clients are
> > >
> > > > recommended to
> > >
> > > > implement it. I would say that options is the third or fourth
> > >
> > > > variant of
> > >
> > > > doing keep alive on my list after RTCP and PING and in hard
> > >
> > > > combat with
> > >
> > > > SET_PARAMETER. It main purpose however is capability discovery.
> > >
> > > >
> > >
> > > > Regards
> > >
> > > >
> > >
> > > > Magnus
> > >
> > > >
> > >
> > > > emre.aksu@nokia.com wrote:
> > >
> > > >
> > >
> > > > >Hello,
> > >
> > > > >
> > >
> > > > >I have a question related to the RTSP OPTIONS method.
> > >
> > > > >In the latest draft of RTSP RFC and also in the RFC 2326, in
> > >
> > > > Table 2, OPTIONS method requirement is listed as follows:
> > >
> > > > >
> > >
> > > > > method direction object requirement
> > >
> > > > >
> > >
> > > > >OPTIONS C->S, S->C P,S required
> > >
> > > > (S->C: optional)
> > >
> > > > >
> > >
> > > > >In the Annex D.1 , minimal RTSP Client implementation,
> > >
> > > > OPTIONS method is not included to the list of methods which
> > >
> > > > MUST be implemented.
> > >
> > > > >
> > >
> > > > >So, My question is: How should this be interpreted?
> > >
> > > > According to Table 2, OPTIONS method looks like to be
> > >
> > > > mandated at least in the C->S direction. But this seems to
> > >
> > > > conflict with the minimal implementation. If Table.2 does not
> > >
> > > > apply to the minimal implementation, how should Table 2 be
> > >
> > > > interpreted? I would really appreciate if this could be clarified.
> > >
> > > > >
> > >
> > > > >I would also like to point out the usefulness of OPTIONS,
> > >
> > > > especially for checking the 'session aliveness' according to
> > >
> > > > the latest draft...
> > >
> > > > >
> > >
> > > > >BR
> > >
> > > > >Emre
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >Emre Baris Aksu
> > >
> > > > >Senior Design Engineer
> > >
> > > > >
> > >
> > > > >Nokia Mobile Phones
> > >
> > > > >Tampere / Finland
> > >
> > > > >e-mail : emre.aksu@nokia.com
> > >
> > > > >Mobile : +358 40 743 1972
> > >
> > > > >Fax : +358 7180 70504
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > >_______________________________________________
> > >
> > > > >mmusic mailing list
> > >
> > > > >mmusic@ietf.org
> > >
> > > > >https://www1.ietf.org/mailman/listinfo/mmusic
> > >
> > > > >
> > >
> > > >
> > >
> > > > --
> > >
> > > >
> > >
> > > > 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
> > >
> > > >
> > >
> > >
> > >_______________________________________________
> > >mmusic mailing list
> > >mmusic@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/mmusic
> >
> >


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


From mmusic-admin@ietf.org  Wed Jul 10 17:31:40 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 RAA20554
	for <mmusic-archive@odin.ietf.org>; Wed, 10 Jul 2002 17:31: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 RAA10470;
	Wed, 10 Jul 2002 17:21:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10439
	for <mmusic@optimus.ietf.org>; Wed, 10 Jul 2002 17:21:51 -0400 (EDT)
Received: from ns2.packetvideo.com (ns2.packetvideo.com [63.214.191.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20245
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 17:20:56 -0400 (EDT)
Received: from misty.packetvideo.com (pv-fw [63.214.191.66])
	by ns2.packetvideo.com (8.11.4/8.11.4) with ESMTP id g6ALLJJ16344
	for <mmusic@ietf.org>; Wed, 10 Jul 2002 14:21:19 -0700 (PDT)
Received: by misty.packetvideo.com with Internet Mail Service (5.5.2653.19)
	id <N3P5XCW3>; Wed, 10 Jul 2002 14:18:25 -0700
Message-ID: <72263E8E8622D611975C0002B32C19D84A7272@misty.packetvideo.com>
From: Thomas Zeng <zeng@packetvideo.com>
To: mmusic@ietf.org
Cc: Thomas Zeng <zeng@packetvideo.com>
Subject: RTSP Feature Tags RE: [MMUSIC] RTSP: Connectionless vs. connectio
	n-based
Date: Wed, 10 Jul 2002 14:18:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Filter-Version: 1.6a (ns2.packetvideo.com)
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

Dear MMUSIC:

During the discussion of persistent-connection vs connection-less operating
modes of RTSP,  
it has become clear that  some relevant feature tags in support of
capability probing should be defined 
(see attached email for background). Here are draft definitions of  two of
them. Your comments are quite welcome.

ping-b4-session-timeout
ping-b4-connection-timeout


1. Option Tag For RTSP:   "Ping Before Timing Out RTSP Session"

- RTSP Feature Tag Name:
   ping-b4-session-timeout

- Summary of the RTSP Features Indicated By This Feature Tag:
   
     This feature tag is intended as part of the RTSP base specification.
This feature tag is only to be used by an RTSP server, 
   and only when operating in "persistent-connection" mode (see [RFC2326
sec. 9]).

     Normally RTSP clients are responsible for "keep-alive" RTSP requests in
order to prevent server from removing the RTSP session
   due to RTSP timeout (see [RFC2326 12.37]). An RTSP server may use this
feature tag to tell its client that it will always ping the 
   client with an RTSP message before removing the session. Conversely, an
RTSP client can use this tag to query whether 
   the server support this feature.

      If an RTSP server agrees to suport this feature, then the client does
NOT have to periodically send "keep-alive" RTSP messages
    to server, as long as the client answers to the server ping message
within the RTSP timeout as defined in  [RFC2326 12.37]. The 
    server ping message must contain the proper session ID (GET_MESSAGE RTSP
request can satisfy this requirement). This is 
    necessary when there are more than one sessions carried over one
connection. In this way the client implementation may be 
    simplified. It is then up to  the discretion of the server to decide
when to ping the client.  If the server is 
    very careful about  Denial of Server Attacks (DSAs), it may 
    ping inmediately after RTSP timeout so as to remove an inactive session
as soon as possible to free up resources.

      In any event, after the ping RTSP message, the server MUST NOT remove
the client session earlier than RTSP timeout, because the protocol is      
    that the client has up to RTSP timeout to respond to ping message.

      Note that  any client wanting to exploit this  feature MUST use a
persistent connection to the server. Otherwise the server 
    cannot reach the client.


2. Option Tag For RTSP:   "Ping Before Timing Out RTSP Connection"

- RTSP Feature tag name:
   ping-b4-connection-timeout

- Summary of the RTSP features indicated by this feature tag:
   
    This feature tag is intended as part of the RTSP base specification.
This feature tag may be used either by client or server.

       During RTSP communications, either the server or the client can drop
the connection due to lack of activity. An RTSP protocol 
    engine (either server or client) may use this feature tag to tell its
peer that it will always ping the other party with 
    an RTSP message before dropping  the RTSP connection.

       If one side agree to this feature tag,  then the other side does NOT
have to periodically send "keep-alive" RTSP messages 
    to maintain the RTSP connection. If an RTSP protocol engine  detects no
activity on the connection after CONNECTION TIMEOUT, 
    it can send a ping RTSP message such as OPTION request (which does not
need a session ID) to probe the other party, if the peer 
    answers to the ping RTSP message quickly, the connection is deemed
alive, but if no response is received within RTSP timeout (
    see [RFC2326 12.37]), then the connection can be removed. Furthurmore,
if the mode of RTSP operation happens to be the 
    persistent-connection mode, then any RTSP sessions  carried over it will
be removed as well. Magnus:

- Thomas Zeng

PacketVideo Corp,
10350 Science Center Drive, Suite 210,
San Diego, CA92121
858 731 5465
      


-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]
Sent: Friday, June 28, 2002 12:04 AM
To: vmudgil@neomagic.com
Cc: Thomas Zeng; mmusic@ietf.org
Subject: Re: [MMUSIC] RTSP: Connectionless vs. connection-based


Hi Vivek and Thomas,

See my comments to both your mails inline.

Vivek Mudgil wrote:

> It has been an interesting reading this discussion on connectionless 
> vs connection-based. Logically
> it would make more sense if clients send the "I am alive" signal to 
> the server. This philosophically is in line with the concept of load 
> distribution.

Yes, I agree with you that it is a responsibility of the client to keep 
the connection alive. This would be in line with that it also is the 
clients responsibility to keep the RTSP session alive. However the 
server may of course try to ping the client before closing the 
connection. We can't mandate such a mechanism but it be a may or 
recommended. Also I do believe that  an options tag for this could be 
beneficial. That way the client will know how the server will behave.

>
> Secondly I was just wondering why can't the "persistent connection" be 
> made a default option for
> RTSP connection with a time out on server side. This passes the onus 
> of keeping the connection alive to the clients. Clients may have a 
> configurable parameter which will allow the user to decide whether it 
> wishes to work in persistent mode by periodically sending the 
> "connection alive" signal or wishes to run in connectionless mode by 
> closing the connection after each transaction. This is turn will be 
> based on delay performance observed by the user in re-establishment of 
> connection.
>
I don't want to make it default because that may result in loss of 
backwards compatibility towards non-persistent connections. To my 
understanding persistent connections is a special case of 
non-persistent. My goal is to write the specification so that makes no 
difference for the server to support both modes. The client has the 
choice to use what suits it. I do believe we are aiming for the same 
goal, let the client choose. 

> Thomas Zeng wrote:
>
>>Hi Magnus:
>>
>>In the message below you suggest that  "the server shall not 
>>close the a connection unless at least the RTSP session time-out  has 
>>passed without traffic."
>>
>>Later on you seem to imply that the onus is on the client to make sure 
>>that it sends a message (could be some keep alive message such as
>>OPTIONS) at least every 60 seconds (or according to RTSP  timeout
interval).
>>(Or did you mean
>>the server is to ensure one message every 60 seconds? It was not clear to
>>me... hence this email...)
>>
It is the client that needs to send regular keep alive messages.

>>
>>How about putting the onus on the server to ping the client when RTSP
>>session time-out
>>expires, and only kick out the client if no ping-response is receive after
a
>>"RTSP response
>>timeout" (again a negotiable value, perhaps a few seconds)?
>>
I can see the usefulness of this, but the default behavior must remain 
that it is the responsibility of the client. An options tag could be 
used by the server in a supported header to tell the client that it has 
this capability. Such a mechanism can be used for both the RTSP timeout 
and the connection timeout. Should both be included in the same tag or 
could they be separately implemented?

Thomas, could you draft a paragraph defining this for the connection to 
be included in the proposed section 9.3. I would like it to also define 
the options tag to use.

>>
>>I say because I may have thin clients that I'd like to keep as simple as
>>possible. Servers on the other hand 
>>have more leeway. 
>>

Implementing a keep alive mechanism is still required for the client. 
Otherwise it will lose the RTSP session, it can of course rely on RTCP. 
But if the code to implement a timer that sends regular connection and 
session keep alive is to much, I would recommend that this client use 
non-persistent connections. 

Best 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 mmusic-admin@ietf.org  Thu Jul 11 05:18:07 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 FAA13967
	for <mmusic-archive@odin.ietf.org>; Thu, 11 Jul 2002 05:18: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 FAA24610;
	Thu, 11 Jul 2002 05:14: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 FAA24529
	for <mmusic@optimus.ietf.org>; Thu, 11 Jul 2002 05:14:36 -0400 (EDT)
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 FAA13869
	for <mmusic@ietf.org>; Thu, 11 Jul 2002 05:13:42 -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 g6B9ERRc029829;
	Thu, 11 Jul 2002 11:14:27 +0200 (MEST)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.108]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3SKCA8LK; Thu, 11 Jul 2002 11:14:25 +0200
Message-ID: <3D2D4C71.2040405@era.ericsson.se>
Date: Thu, 11 Jul 2002 11:14:25 +0200
X-Sybari-Trust: 2b476d85 7216406a e4ad19be 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: Jeremy Worley <jworley@real.com>
CC: emre.aksu@nokia.com, mmusic@ietf.org
Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not  in minimal client and server implementations?
References: <5.1.0.14.2.20020710095355.0301f7e0@mail.real.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

Hi Jeremy,

See comments inline:

Jeremy Worley wrote:

> Hi Emre,
>
> At 07:05 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
>
>> Hi Jeremy,
>> Please find my comments inlined:
>>
>> > -----Original Message-----
>> > From: ext Jeremy Worley [mailto:jworley@real.com]
>> > Sent: 10. July 2002 18:42
>> > To: Aksu Emre (NMP/Tampere); mmusic@ietf.org
>> > Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it
>> > required or not
>> > in minimal client and server implementations?
>> >
>> >
>> > Hello Emre,
>> >
>> > At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
>> > >Hi Magnus,
>> > >
>> > >Thanhs for the quick answer. The reason why I asked this
>> > mainly is that, I
>> > >don't actually know an RTSP client which didn't implement
>> > OPTIONS :-) (by
>> > >implementing, I mean which can send OPTIONS request). So,
>> > wouldn't it be
>> > >better to make it required also for the minimal
>> > implementation on the
>> > >client side?
>> >
>> > I agree most clients implement sending of OPTIONS requests.
>> > It also common
>> > for clients to not implement OPTIONS response.
>>
>> I agree with this. But in such a case, at least a "Not implemented" 
>> error status message has to be sent by the client to the server, 
>> right? In fact, my intention was to have the request to be a mandated 
>> requirement for the client. For the response to OPTIONS on the cliet 
>> side, I agree it can be optional as an implementation.
>
>
> I agree that the client should respond if it does not support 
> responding to a server OPTIONS request.
>
> My opinion is that if the client does not use optional features, then 
> it should not have to issue an OPTIONS request.

In other word you are happy with what is written today in appendix D. 
Server must implement OPTIONS while it is totally optional for a client.

>
>
>> > The rationale for not
>> > requiring to send OPTIONS requests on the client is OK in my opinion
>> > because it is usually used to query features that a server
>> > implements.  If
>> > the client does not use any optional features, then it has no
>> > need to send
>> > an OPTIONS request, and so it would not need to implement sending of
>> > OPTIONS.  On the other hand, if the client uses optional RTSP
>> > features,
>> > then it must implement an OPTIONS request.
>> >
>>
>> I see your point, but this is quite a statement, which I believe 
>> should be present in the RFC then. Also, the minimal implementation 
>> for server and client has some 'or' statements in it (for example for 
>> RECORD and PLAY method), which I believe, means that different sets 
>> of minimal implementations are possible, and a client has to check 
>> which set of  implementationthe server supports, even if the server 
>> is assumed to be a minimal implementation in the very beginning.
>
>
> You raise an interesting point.  Table 2 of 2326 and 2326bis states 
> that RECORD is optional and PLAY is mandatory for the client.  However 
> D.1 and D.2 appear to state that it is required that either PLAY or 
> RECORD can be implemented.  RECORD is described as an optional feature 
> in several places in 2326 (e.g., 1.5, 10.11, table 2).  I think in 
> this case, it makes sense to make Section D consistent with the rest 
> of the document.
>
In this case my interpretation is that Appendix D is correct. There 
actually exist several types of minimal implementations, one for doing 
playback from server, one for doing playback for servers of on demand 
content and a third for recording to servers. They can further also 
support authentication. The contradictions we must do the best to 
remove. They are unfortunately very common in RFC 2326. As an example I 
found one more in Appendix D. The user agent header is only RECOMMENDED 
to implement by clients in Appendix D while the header definition in 
RFC2616 section 14.43 says: "User agents SHOULD include this field with 
requests."

>
>> > I agree with Magnus that Table 2 should be clarified to
>> > describe what must
>> > be implemented as both requests and responses by client and server.
>> >
>> >
>> > >I also think that it is a quite clean solution to use OPTIONS with
>> > >Session-Id to check/keep session aliveness. I remember the
>> > big discussions
>> > >about this in this reflector, and I don't intend open them
>> > again :-). Just
>> > >to keep in mind, in 3GPP Packet Switched Streaming Service
>> > definitions,
>> > >RTCP and OPTIONS are the preferred methods for session
>> > aliveness checking,
>> > >in the given preference order. (Ref: Section A.2.2.2.2 in
>> > document TS
>> > >26.234 v4.40 (Release 4) and v5.10 (Release 5)).
>> >
>> > When the new RTSP draft becomes an RFC, we may want to add
>> > PING to the list
>> > of methods for checking session aliveness in 26.234.  In such
>> > a scenario, I
>> > think PING might be preferred over OPTIONS.
>> >
>>
>> I agree, PING is a very good choice and I believe it will definitely 
>> find its place in the 3GPP spec. I have one question though. Can PING 
>> method identify a streaming session?. What I exactly mean is that, 
>> can a PING request bear a Session-ID?
>
>
> Table 4 in the draft states that the Session header mandatory for 
> PING.  Interestingly, the example transaction in 10.12 does not 
> include a Session header.  That example should be modified to include 
> a Session header.

Yes, an error which will be corrected in the next version.

>
> A minor editorial note: table 4 also seems to have floated to a later 
> section of the document in the current draft.  That should be cleaned 
> up in the next draft.

Yes, the tables are floating around a bit. I don't think we will fix 
that. I do feel that it is better to have as much of the table as 
possible in one page. We still have to reformat the table as it is to 
wide for a single page.

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 mmusic-admin@ietf.org  Thu Jul 11 05:51: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 FAA14424
	for <mmusic-archive@odin.ietf.org>; Thu, 11 Jul 2002 05:51: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 FAA26224;
	Thu, 11 Jul 2002 05:48:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26192
	for <mmusic@optimus.ietf.org>; Thu, 11 Jul 2002 05:48:45 -0400 (EDT)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14382
	for <mmusic@ietf.org>; Thu, 11 Jul 2002 05:47:50 -0400 (EDT)
From: emre.aksu@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x3.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6B9ogW29997
	for <mmusic@ietf.org>; Thu, 11 Jul 2002 12:50:43 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c061f90beac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 11 Jul 2002 12:48:43 +0300
Received: from esebe015.NOE.Nokia.com ([172.21.138.54]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 11 Jul 2002 12:48:42 +0300
Received: from trebe006.NOE.Nokia.com ([172.22.232.181]) by esebe015.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 11 Jul 2002 12:48:42 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not  in minimal client and server implementations?
Date: Thu, 11 Jul 2002 12:48:41 +0300
Message-ID: <B519AC26B144EF479CFB036F7B84E7C8A12503@trebe006.NOE.Nokia.com>
Thread-Topic: [MMUSIC] OPTIONS method in RTSP. Is it required or not  in minimal client and server implementations?
Thread-Index: AcIou2Y28EfNWaqHSeCxF9vmsLs/OwAA/yTw
To: <magnus.westerlund@era.ericsson.se>, <jworley@real.com>
Cc: <mmusic@ietf.org>
X-OriginalArrivalTime: 11 Jul 2002 09:48:42.0027 (UTC) FILETIME=[23DC57B0:01C228C0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA26193
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 Magnus,

Please see my comments inlined:


> -----Original Message-----
> From: ext Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]
> Sent: 11. July 2002 12:14
> To: Jeremy Worley
> Cc: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not in
> minimal client and server implementations?
> 
> 
> Hi Jeremy,
> 
> See comments inline:
> 
> Jeremy Worley wrote:
> 
> > Hi Emre,
> >
> > At 07:05 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> >
> >> Hi Jeremy,
> >> Please find my comments inlined:
> >>
> >> > -----Original Message-----
> >> > From: ext Jeremy Worley [mailto:jworley@real.com]
> >> > Sent: 10. July 2002 18:42
> >> > To: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> >> > Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it
> >> > required or not
> >> > in minimal client and server implementations?
> >> >
> >> >
> >> > Hello Emre,
> >> >
> >> > At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> >> > >Hi Magnus,
> >> > >
> >> > >Thanhs for the quick answer. The reason why I asked this
> >> > mainly is that, I
> >> > >don't actually know an RTSP client which didn't implement
> >> > OPTIONS :-) (by
> >> > >implementing, I mean which can send OPTIONS request). So,
> >> > wouldn't it be
> >> > >better to make it required also for the minimal
> >> > implementation on the
> >> > >client side?
> >> >
> >> > I agree most clients implement sending of OPTIONS requests.
> >> > It also common
> >> > for clients to not implement OPTIONS response.
> >>
> >> I agree with this. But in such a case, at least a "Not 
> implemented" 
> >> error status message has to be sent by the client to the server, 
> >> right? In fact, my intention was to have the request to be 
> a mandated 
> >> requirement for the client. For the response to OPTIONS on 
> the cliet 
> >> side, I agree it can be optional as an implementation.
> >
> >
> > I agree that the client should respond if it does not support 
> > responding to a server OPTIONS request.
> >
> > My opinion is that if the client does not use optional 
> features, then 
> > it should not have to issue an OPTIONS request.
> 
> In other word you are happy with what is written today in appendix D. 
> Server must implement OPTIONS while it is totally optional 
> for a client.
> 
> >
> >
> >> > The rationale for not
> >> > requiring to send OPTIONS requests on the client is OK 
> in my opinion
> >> > because it is usually used to query features that a server
> >> > implements.  If
> >> > the client does not use any optional features, then it has no
> >> > need to send
> >> > an OPTIONS request, and so it would not need to 
> implement sending of
> >> > OPTIONS.  On the other hand, if the client uses optional RTSP
> >> > features,
> >> > then it must implement an OPTIONS request.
> >> >
> >>
> >> I see your point, but this is quite a statement, which I believe 
> >> should be present in the RFC then. Also, the minimal 
> implementation 
> >> for server and client has some 'or' statements in it (for 
> example for 
> >> RECORD and PLAY method), which I believe, means that 
> different sets 
> >> of minimal implementations are possible, and a client has to check 
> >> which set of  implementationthe server supports, even if 
> the server 
> >> is assumed to be a minimal implementation in the very beginning.
> >
> >
> > You raise an interesting point.  Table 2 of 2326 and 2326bis states 
> > that RECORD is optional and PLAY is mandatory for the 
> client.  However 
> > D.1 and D.2 appear to state that it is required that either PLAY or 
> > RECORD can be implemented.  RECORD is described as an 
> optional feature 
> > in several places in 2326 (e.g., 1.5, 10.11, table 2).  I think in 
> > this case, it makes sense to make Section D consistent with 
> the rest 
> > of the document.
> >
> In this case my interpretation is that Appendix D is correct. There 
> actually exist several types of minimal implementations, one 
> for doing 
> playback from server, one for doing playback for servers of on demand 
> content and a third for recording to servers. They can further also 
> support authentication. 


If these many possibilites are present for minimal implementation where the implementations actually differ in means of supported functionalities, how does a client identify what kind of a server it is dealing with without using OPTIONS method, if OPTIONS is not mandated also for the client as a way of request to check the server capabilities? Can there be a logical mismatch here? 


Best Regards,
Emre



> The contradictions we must do the best to 
> remove. They are unfortunately very common in RFC 2326. As an 
> example I 
> found one more in Appendix D. The user agent header is only 
> RECOMMENDED 
> to implement by clients in Appendix D while the header definition in 
> RFC2616 section 14.43 says: "User agents SHOULD include this 
> field with 
> requests."
> 
> >
> >> > I agree with Magnus that Table 2 should be clarified to
> >> > describe what must
> >> > be implemented as both requests and responses by client 
> and server.
> >> >
> >> >
> >> > >I also think that it is a quite clean solution to use 
> OPTIONS with
> >> > >Session-Id to check/keep session aliveness. I remember the
> >> > big discussions
> >> > >about this in this reflector, and I don't intend open them
> >> > again :-). Just
> >> > >to keep in mind, in 3GPP Packet Switched Streaming Service
> >> > definitions,
> >> > >RTCP and OPTIONS are the preferred methods for session
> >> > aliveness checking,
> >> > >in the given preference order. (Ref: Section A.2.2.2.2 in
> >> > document TS
> >> > >26.234 v4.40 (Release 4) and v5.10 (Release 5)).
> >> >
> >> > When the new RTSP draft becomes an RFC, we may want to add
> >> > PING to the list
> >> > of methods for checking session aliveness in 26.234.  In such
> >> > a scenario, I
> >> > think PING might be preferred over OPTIONS.
> >> >
> >>
> >> I agree, PING is a very good choice and I believe it will 
> definitely 
> >> find its place in the 3GPP spec. I have one question 
> though. Can PING 
> >> method identify a streaming session?. What I exactly mean is that, 
> >> can a PING request bear a Session-ID?
> >
> >
> > Table 4 in the draft states that the Session header mandatory for 
> > PING.  Interestingly, the example transaction in 10.12 does not 
> > include a Session header.  That example should be modified 
> to include 
> > a Session header.
> 
> Yes, an error which will be corrected in the next version.
> 
> >
> > A minor editorial note: table 4 also seems to have floated 
> to a later 
> > section of the document in the current draft.  That should 
> be cleaned 
> > up in the next draft.
> 
> Yes, the tables are floating around a bit. I don't think we will fix 
> that. I do feel that it is better to have as much of the table as 
> possible in one page. We still have to reformat the table as it is to 
> wide for a single page.
> 
> 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
> 

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


From mmusic-admin@ietf.org  Thu Jul 11 07:10:22 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 HAA15579
	for <mmusic-archive@odin.ietf.org>; Thu, 11 Jul 2002 07:10: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 HAA29877;
	Thu, 11 Jul 2002 07:03: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 HAA29847
	for <mmusic@optimus.ietf.org>; Thu, 11 Jul 2002 07:03:16 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15497
	for <mmusic@ietf.org>; Thu, 11 Jul 2002 07:02:21 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g6BB3DrU023368;
	Thu, 11 Jul 2002 13:03:14 +0200 (MEST)
Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.108]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3SKCCFAF; Thu, 11 Jul 2002 13:03:13 +0200
Message-ID: <3D2D65F1.40900@era.ericsson.se>
Date: Thu, 11 Jul 2002 13:03:13 +0200
X-Sybari-Trust: c808fa0c 7216406a 2358112d 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: emre.aksu@nokia.com
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not  in minimal client and server implementations?
References: <B519AC26B144EF479CFB036F7B84E7C8A12503@trebe006.NOE.Nokia.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

Hi Emre,

A client does not need to know in advance if its going to work, instead 
it can simply try to perform a certain task. If some functionality is 
not supported, it will fail and an error message will be generated in 
response to the unsupported request. For example a setup request for 
record contains mode=record, it the server does not support record it 
shall answer with "461 Unsupported Transport".

I have been thinking of defining option tags for the basic 
functionality's that can be used in the Require header. This allows a 
client to already during the first request to know if it will work or 
not. However I don't think we can distinguish so easily between live and 
on-demand content and the requirement that put onto a client. It may 
actually be reasonable to require that a client shall handle both live 
and on-demand content. Further input into what shall be minimal 
implementation is encouraged. Please remember that we should not 
substantially change the RFC 2326 rules but we may clarify them.

Regards

Magnus

emre.aksu@nokia.com wrote:

>If these many possibilites are present for minimal implementation where the implementations actually differ in means of supported functionalities, how does a client identify what kind of a server it is dealing with without using OPTIONS method, if OPTIONS is not mandated also for the client as a way of request to check the server capabilities? Can there be a logical mismatch here? 
>
>
-- 

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 mmusic-admin@ietf.org  Thu Jul 11 10:41: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 KAA19426
	for <mmusic-archive@odin.ietf.org>; Thu, 11 Jul 2002 10:41: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 KAA11534;
	Thu, 11 Jul 2002 10:33:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11509
	for <mmusic@optimus.ietf.org>; Thu, 11 Jul 2002 10:33:45 -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 KAA19173;
	Thu, 11 Jul 2002 10:32:51 -0400 (EDT)
Received: from rubin.ipv6.tzi.de (rubin.informatik.uni-bremen.de [134.102.224.59])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g6BEXZH21761;
	Thu, 11 Jul 2002 16:33:35 +0200 (MEST)
From: Joerg Ott <jo@Informatik.Uni-Bremen.DE>
Received: (from jo@localhost)
	by rubin.ipv6.tzi.de (8.11.6/8.8.7) id g6BEXXO05976;
	Thu, 11 Jul 2002 16:33:33 +0200
Message-Id: <200207111433.g6BEXXO05976@rubin.ipv6.tzi.de>
To: mmusic@ietf.org, agenda@ietf.org
Date: Thu, 11 Jul 2002 16:33:33 +0200 (MEST)
Cc: jo@Informatik.Uni-Bremen.DE (Joerg Ott), csp@isi.edu
X-Mailer: ELM [version 2.5 PL6]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Slightly Revised MMUSIC Agenda
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

Folks,

please note the slightly revised MMUSIC agenda below.
Available as text and as HTML with links to the documents
at
	http://www.dmn.tzi.org/ietf/mmusic/

Joerg



Agenda of the MMUSIC WG  at the 54th IETF
=========================================

Thursday, 18 July 2002, 0900 - 1130, Room 304
---------------------------------------------

0900    Agenda Bashing and Status update               (chairs, 15)

        Recent RFCs
        - draft-ietf-mmusic-mbus-transport-06.txt   -> RFC 3259
        - draft-ietf-mmusic-sdp-offer-answer-02.txt -> RFC 3264
        - draft-ietf-mmusic-sdp-ipv6-03.txt         -> RFC 3266

        In IESG Last Call
        - draft-ietf-mmusic-fid-06.txt
        - draft-andreasen-mmusic-sdp-simcap-05.txt
        - draft-ietf-mmusic-sdp-new-10.txt

        Other documents (pretty much finished)
        - draft-ietf-mmusic-sdp-comedia-03.txt
        - draft-ietf-mmusic-sdp4nat-02.txt
        - draft-ietf-mmusic-kmgmt-ext-05.txt

        Misc Updates
        - draft-ietf-mmusic-sdpng-trans-01.txt

0915    SDP Source Filters                              (chairs, 5)
        - draft-ietf-mmusic-sdp-srcfilter-01.txt

0920    SDPng update                                    (Kutscher/Klemets, 30)
        - draft-ietf-mmusic-sdpng-05.txt
        - draft-rojas-mmusic-qosreq-00.txt

0950    MMUSIC and Conference/Media Control             (chairs, 15)
        - draft-prandolini-mmusic-jpip-requirements-00.txt
        - draft-even-mmusic-video-media-control-00.txt

1005    SDP attributes for Video media Media Control    (Even, 15)
        - draft-even-mmusic-video-media-control-00.txt

1020    Metadata Update Protocol                        (Nomura, 15)
        - draft-nomura-mmusic-pguide-requirements-00.txt
        - draft-nomura-cdi-mmusic-mupdate-00.txt

1035    Revised RTSP spec                               (Lanphier, 55)
        - draft-ietf-mmusic-rfc2326bis-01.txt

1130    Wrap-up                                         (chairs)



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


From mmusic-admin@ietf.org  Fri Jul 12 01:12: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 BAA26550
	for <mmusic-archive@odin.ietf.org>; Fri, 12 Jul 2002 01:12:30 -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 BAA16376;
	Fri, 12 Jul 2002 01:09: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 BAA16324
	for <mmusic@optimus.ietf.org>; Fri, 12 Jul 2002 01:09:02 -0400 (EDT)
Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26341
	for <mmusic@ietf.org>; Fri, 12 Jul 2002 01:08:05 -0400 (EDT)
Received: from real.com (murrow2k1.real.com [207.188.7.41])
	by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g6C58NKR028828;
	Thu, 11 Jul 2002 22:08:23 -0700
Received: from A7397.real.com (bdsl.66.14.45.90.gte.net [66.14.45.90] (may be forged))
	by real.com (8.12.2/8.12.2) with ESMTP id g6C58KMB006025;
	Thu, 11 Jul 2002 22:08:21 -0700
Message-Id: <5.1.0.14.2.20020711214905.03130cb8@mail.real.com>
X-Sender: jworley@mail.real.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 11 Jul 2002 22:07:00 -0700
To: <emre.aksu@nokia.com>, <magnus.westerlund@era.ericsson.se>
From: Jeremy Worley <jworley@real.com>
Subject: RE: [MMUSIC] OPTIONS method in RTSP. Is it required or not  in
  minimal client and server implementations?
Cc: <mmusic@ietf.org>
In-Reply-To: <B519AC26B144EF479CFB036F7B84E7C8A12503@trebe006.NOE.Nokia.
 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 Emre and Magnus,

More comments inline.

At 12:48 PM 7/11/2002 +0300, emre.aksu@nokia.com wrote:
>Hi Magnus,
>
>Please see my comments inlined:
>
>
> > -----Original Message-----
> > From: ext Magnus Westerlund [mailto:magnus.westerlund@era.ericsson.se]
> > Sent: 11. July 2002 12:14
> > To: Jeremy Worley
> > Cc: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> > Subject: Re: [MMUSIC] OPTIONS method in RTSP. Is it required or not in
> > minimal client and server implementations?
> >
> >
> > Hi Jeremy,
> >
> > See comments inline:
> >
> > Jeremy Worley wrote:
> >
> > > Hi Emre,
> > >
> > > At 07:05 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> > >
> > >> Hi Jeremy,
> > >> Please find my comments inlined:
> > >>
> > >> > -----Original Message-----
> > >> > From: ext Jeremy Worley [mailto:jworley@real.com]
> > >> > Sent: 10. July 2002 18:42
> > >> > To: Aksu Emre (NMP/Tampere); mmusic@ietf.org
> > >> > Subject: Re: RE: [MMUSIC] OPTIONS method in RTSP. Is it
> > >> > required or not
> > >> > in minimal client and server implementations?
> > >> >
> > >> >
> > >> > Hello Emre,
> > >> >
> > >> > At 05:23 PM 7/10/2002 +0300, emre.aksu@nokia.com wrote:
> > >> > >Hi Magnus,
> > >> > >
> > >> > >Thanhs for the quick answer. The reason why I asked this
> > >> > mainly is that, I
> > >> > >don't actually know an RTSP client which didn't implement
> > >> > OPTIONS :-) (by
> > >> > >implementing, I mean which can send OPTIONS request). So,
> > >> > wouldn't it be
> > >> > >better to make it required also for the minimal
> > >> > implementation on the
> > >> > >client side?
> > >> >
> > >> > I agree most clients implement sending of OPTIONS requests.
> > >> > It also common
> > >> > for clients to not implement OPTIONS response.
> > >>
> > >> I agree with this. But in such a case, at least a "Not
> > implemented"
> > >> error status message has to be sent by the client to the server,
> > >> right? In fact, my intention was to have the request to be
> > a mandated
> > >> requirement for the client. For the response to OPTIONS on
> > the cliet
> > >> side, I agree it can be optional as an implementation.
> > >
> > >
> > > I agree that the client should respond if it does not support
> > > responding to a server OPTIONS request.
> > >
> > > My opinion is that if the client does not use optional
> > features, then
> > > it should not have to issue an OPTIONS request.
> >
> > In other word you are happy with what is written today in appendix D.
> > Server must implement OPTIONS while it is totally optional
> > for a client.
> >
> > >
> > >
> > >> > The rationale for not
> > >> > requiring to send OPTIONS requests on the client is OK
> > in my opinion
> > >> > because it is usually used to query features that a server
> > >> > implements.  If
> > >> > the client does not use any optional features, then it has no
> > >> > need to send
> > >> > an OPTIONS request, and so it would not need to
> > implement sending of
> > >> > OPTIONS.  On the other hand, if the client uses optional RTSP
> > >> > features,
> > >> > then it must implement an OPTIONS request.
> > >> >
> > >>
> > >> I see your point, but this is quite a statement, which I believe
> > >> should be present in the RFC then. Also, the minimal
> > implementation
> > >> for server and client has some 'or' statements in it (for
> > example for
> > >> RECORD and PLAY method), which I believe, means that
> > different sets
> > >> of minimal implementations are possible, and a client has to check
> > >> which set of  implementationthe server supports, even if
> > the server
> > >> is assumed to be a minimal implementation in the very beginning.
> > >
> > >
> > > You raise an interesting point.  Table 2 of 2326 and 2326bis states
> > > that RECORD is optional and PLAY is mandatory for the
> > client.  However
> > > D.1 and D.2 appear to state that it is required that either PLAY or
> > > RECORD can be implemented.  RECORD is described as an
> > optional feature
> > > in several places in 2326 (e.g., 1.5, 10.11, table 2).  I think in
> > > this case, it makes sense to make Section D consistent with
> > the rest
> > > of the document.
> > >
> > In this case my interpretation is that Appendix D is correct. There
> > actually exist several types of minimal implementations, one
> > for doing
> > playback from server, one for doing playback for servers of on demand
> > content and a third for recording to servers. They can further also
> > support authentication.
>
>
>If these many possibilites are present for minimal implementation where 
>the implementations actually differ in means of supported functionalities, 
>how does a client identify what kind of a server it is dealing with 
>without using OPTIONS method, if OPTIONS is not mandated also for the 
>client as a way of request to check the server capabilities? Can there be 
>a logical mismatch here?

For the client, I think it is OK to send a PLAY or a ANNOUNCE and get a 501 
(Not implemented) back.  In other words, a client should not be required to 
send an OPTIONS before it issues a PLAY or ANNOUNCE request.

On a related topic, I think that a problem does exist in section D.2 vs. 
the rest of the document.  Table 2 states that PLAY is required and 
ANNOUNCE/RECORD is optional.  Here again, a problem exists in that the 
table is not clear as to whether the requirement for support is on the 
client, server, or both.  I interpret this and statements in other sections 
(1.5, Table 3 in 12) to mean this:

- A client must implement one or more of PLAY, RECORD.  A client 
implementing RECORD must implement sending ANNOUNCE.  A server implementing 
RECORD must implement handling ANNOUNCE from a client and may implement 
sending ANNOUNCE to a client.

- A server must implement PLAY and may implement RECORD.

Reasoning:  there are reasonable cases where a client may implement only 
PLAY or RECORD.  I can't think of a likely scenario where a server would 
implement record functionality but not playback.

Jeremy



>Best Regards,
>Emre
>
>
>
> > The contradictions we must do the best to
> > remove. They are unfortunately very common in RFC 2326. As an
> > example I
> > found one more in Appendix D. The user agent header is only
> > RECOMMENDED
> > to implement by clients in Appendix D while the header definition in
> > RFC2616 section 14.43 says: "User agents SHOULD include this
> > field with
> > requests."
> >
> > >
> > >> > I agree with Magnus that Table 2 should be clarified to
> > >> > describe what must
> > >> > be implemented as both requests and responses by client
> > and server.
> > >> >
> > >> >
> > >> > >I also think that it is a quite clean solution to use
> > OPTIONS with
> > >> > >Session-Id to check/keep session aliveness. I remember the
> > >> > big discussions
> > >> > >about this in this reflector, and I don't intend open them
> > >> > again :-). Just
> > >> > >to keep in mind, in 3GPP Packet Switched Streaming Service
> > >> > definitions,
> > >> > >RTCP and OPTIONS are the preferred methods for session
> > >> > aliveness checking,
> > >> > >in the given preference order. (Ref: Section A.2.2.2.2 in
> > >> > document TS
> > >> > >26.234 v4.40 (Release 4) and v5.10 (Release 5)).
> > >> >
> > >> > When the new RTSP draft becomes an RFC, we may want to add
> > >> > PING to the list
> > >> > of methods for checking session aliveness in 26.234.  In such
> > >> > a scenario, I
> > >> > think PING might be preferred over OPTIONS.
> > >> >
> > >>
> > >> I agree, PING is a very good choice and I believe it will
> > definitely
> > >> find its place in the 3GPP spec. I have one question
> > though. Can PING
> > >> method identify a streaming session?. What I exactly mean is that,
> > >> can a PING request bear a Session-ID?
> > >
> > >
> > > Table 4 in the draft states that the Session header mandatory for
> > > PING.  Interestingly, the example transaction in 10.12 does not
> > > include a Session header.  That example should be modified
> > to include
> > > a Session header.
> >
> > Yes, an error which will be corrected in the next version.
> >
> > >
> > > A minor editorial note: table 4 also seems to have floated
> > to a later
> > > section of the document in the current draft.  That should
> > be cleaned
> > > up in the next draft.
> >
> > Yes, the tables are floating around a bit. I don't think we will fix
> > that. I do feel that it is better to have as much of the table as
> > possible in one page. We still have to reformat the table as it is to
> > wide for a single page.
> >
> > 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
> >


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


From mmusic-admin@ietf.org  Fri Jul 12 02:34: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 CAA08188
	for <mmusic-archive@odin.ietf.org>; Fri, 12 Jul 2002 02:34: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 CAA24994;
	Fri, 12 Jul 2002 02:30:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24943
	for <mmusic@optimus.ietf.org>; Fri, 12 Jul 2002 02:30:48 -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 CAA07942
	for <mmusic@ietf.org>; Fri, 12 Jul 2002 02:29:53 -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 g6C6Uf310312;
	Fri, 12 Jul 2002 08:30:41 +0200 (MEST)
Message-ID: <3D2E7803.AFEF2934@tzi.uni-bremen.de>
Date: Fri, 12 Jul 2002 08:32:35 +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: mmusic@ietf.org
CC: csp@isi.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Slides for the MMUSIC meeting
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

Everybody who will be presenting in MMUSIC on Thursday, please
send us a copy of your slides (as PPT, PDF, or PS) latest by
midnight on Wednesday so that we can have all presentations off
a single laptop.

Thanks,
Joerg

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


From mmusic-admin@ietf.org  Sun Jul 14 01:49:14 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 BAA16200
	for <mmusic-archive@odin.ietf.org>; Sun, 14 Jul 2002 01:49:14 -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 BAA05088;
	Sun, 14 Jul 2002 01:44: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 BAA05057
	for <mmusic@optimus.ietf.org>; Sun, 14 Jul 2002 01:44:39 -0400 (EDT)
Received: from embexcil01.emblaze.ent (esafe.emblaze.com [212.68.150.132])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16086
	for <mmusic@ietf.org>; Sun, 14 Jul 2002 01:43:42 -0400 (EDT)
Received: through eSafe SMTP Relay 1026399920; Sun Jul 14 08:42:09 2002
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Date: Sun, 14 Jul 2002 08:43:49 +0300
Message-ID: <980C7B879697C7448A54C9B065AAFAAC08E036@embexcil01.emblaze.ent>
Thread-Topic: different RTP/RTSP server
Thread-Index: AcIq+W1zL+gIwUrISOivrNIYf7sXdQ==
From: "Lior Sion" <lior.sion@emblaze.com>
To: "Mmusic (E-mail)" <mmusic@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA05058
Subject: [MMUSIC] different RTP/RTSP server
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 all,

I was wondering if there's any standard way to separate RTP/RTSP servers today. 
My problem is that in unicast sessions, there's no apparent way to signal the player about a different origin of RTP packets than that of the RTSP server, since the "c=" field of SDP is supposed to be set to 0.0.0.0 in unicast.

Am i wrong? Is there a different way to signal this?

Thanks,
Lior Sion
**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or  the 
sender immediately and do not disclose the contents to any one or make copies.

** eSafe scanned this email for viruses, vandals and malicious content **
**************************************************************************************************


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


From mmusic-admin@ietf.org  Sun Jul 14 08:06:41 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 IAA02913
	for <mmusic-archive@odin.ietf.org>; Sun, 14 Jul 2002 08:06:41 -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 IAA17395;
	Sun, 14 Jul 2002 08:04: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 IAA17370
	for <mmusic@ns.ietf.org>; Sun, 14 Jul 2002 08:04:35 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02814
	for <mmusic@ietf.org>; Sun, 14 Jul 2002 08:03:37 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g6EC4NrU029923;
	Sun, 14 Jul 2002 14:04:23 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <3YS9WWSW>; Sun, 14 Jul 2002 14:04:23 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754602BF412D@esealnt448.al.sw.ericsson.se>
From: "Magnus Westerlund (EAB)" <Magnus.Westerlund@era.ericsson.se>
To: "'Lior Sion '" <lior.sion@emblaze.com>,
        "'Mmusic (E-mail) '"
	 <mmusic@ietf.org>
Subject: RE: [MMUSIC] different RTP/RTSP server
Date: Sun, 14 Jul 2002 14:02:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="windows-1255"
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 Lior,

Yes, RTSP does support seperate RTSP and RTP servers. In the setup response the RTSP server can tell the client that the RTP traffic will orginate from the RTP server by using the source field in the transport header. 

Regards

Magnus 

-----Original Message-----
From: Lior Sion
To: Mmusic (E-mail)
Sent: 7/14/2002 7:43 AM
Subject: [MMUSIC] different RTP/RTSP server

Hi all,

I was wondering if there's any standard way to separate RTP/RTSP servers
today. 
My problem is that in unicast sessions, there's no apparent way to
signal the player about a different origin of RTP packets than that of
the RTSP server, since the "c=" field of SDP is supposed to be set to
0.0.0.0 in unicast.

Am i wrong? Is there a different way to signal this?

Thanks,
Lior Sion
************************************************************************
**************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system
manager or  the 
sender immediately and do not disclose the contents to any one or make
copies.

** eSafe scanned this email for viruses, vandals and malicious content
**
************************************************************************
**************************


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

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


From mmusic-admin@ietf.org  Mon Jul 15 06:31: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 GAA23105
	for <mmusic-archive@odin.ietf.org>; Mon, 15 Jul 2002 06:31: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 GAA14628;
	Mon, 15 Jul 2002 06:20:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14597
	for <mmusic@optimus.ietf.org>; Mon, 15 Jul 2002 06:20:40 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (h33s128a211n47.user.nortelnetworks.com [47.211.128.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22492
	for <mmusic@ietf.org>; Mon, 15 Jul 2002 06:19:41 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6FAK5M00445
	for <mmusic@ietf.org>; Mon, 15 Jul 2002 11:20:06 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <356NC4N4>; Mon, 15 Jul 2002 11:20:06 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7435@zwcwd00r.europe.nortel.com>
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: mmusic@ietf.org
Subject: RE: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-01.txt
Date: Mon, 15 Jul 2002 11:20:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C22BE9.3009A32C"
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_01C22BE9.3009A32C
Content-Type: text/plain;
	charset="iso-8859-1"

A quick question on this one:

The draft suggests that the actual filtering based on source address may be
carried out in the network, rather than at the host.

I'm not familar with the mechanisms which were envisaged to install such
filters in the network, but I would like to know if interaction with
MobileIP has been considered ?

I guess if the sender is a MobileIP host, then the source address in the IP
packets may be the Care Of Address. Presumably the address visible at the
application layer is the Home Address.

I am not sure if the situation is different as between MobileIPv4 &
MobileIPv6.

Regards,

Mark Watson


> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: 05 July 2002 11:36
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-srcfilter-01.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Multiparty Multimedia 
> Session Control Working Group of the IETF.
> 
> 	Title		: SDP Source-Filters
> 	Author(s)	: B. Quinn, R. Finlayson
> 	Filename	: draft-ietf-mmusic-sdp-srcfilter-01.txt
> 	Pages		: 10
> 	Date		: 03-Jul-02
> 	
> This document describes how to adapt the Session Description Protocol
> (SDP) to express one or more source addresses as a source filter for
> one or more destination 'connection' addresses.  It defines the syntax
> and semantics for an SDP 'source-filter' attribute that may reference
> either IPv4 or IPv6 address(es) as either an inclusive or exclusive
> source list for either multicast or unicast destinations.  In 
> particular,an inclusive source-filter can be used to specify 
> a Source-Specific Multicast ('SSM') session.
> 
> Receiver applications are expected use the SDP source-filter
> information to identify traffic from legitimate senders and discard
> traffic from illegitimate senders.  Applications and hosts may also
> share the source-filter information with network elements (e.g., with
> routers using IGMPv3) so they can potentially perform the traffic
> filtering operation further 'upstream,' closer to the source(s).
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcf
ilter-01.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-ietf-mmusic-sdp-srcfilter-01.txt".

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


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

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

------_=_NextPart_001_01C22BE9.3009A32C
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>RE: [MMUSIC] I-D =
ACTION:draft-ietf-mmusic-sdp-srcfilter-01.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>A quick question on this one:</FONT>
</P>

<P><FONT SIZE=3D2>The draft suggests that the actual filtering based on =
source address may be carried out in the network, rather than at the =
host.</FONT></P>

<P><FONT SIZE=3D2>I'm not familar with the mechanisms which were =
envisaged to install such filters in the network, but I would like to =
know if interaction with MobileIP has been considered ?</FONT></P>

<P><FONT SIZE=3D2>I guess if the sender is a MobileIP host, then the =
source address in the IP packets may be the Care Of Address. Presumably =
the address visible at the application layer is the Home =
Address.</FONT></P>

<P><FONT SIZE=3D2>I am not sure if the situation is different as =
between MobileIPv4 &amp; MobileIPv6.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>
</P>

<P><FONT SIZE=3D2>Mark Watson</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Internet-Drafts@ietf.org [<A =
HREF=3D"mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 05 July 2002 11:36</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: mmusic@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [MMUSIC] I-D =
ACTION:draft-ietf-mmusic-sdp-srcfilter-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A New Internet-Draft is available from the =
on-line </FONT>
<BR><FONT SIZE=3D2>&gt; Internet-Drafts directories.</FONT>
<BR><FONT SIZE=3D2>&gt; This draft is a work item of the Multiparty =
Multimedia </FONT>
<BR><FONT SIZE=3D2>&gt; Session Control Working Group of the =
IETF.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : SDP =
Source-Filters</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : B. Quinn, R. =
Finlayson</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-ietf-mmusic-sdp-srcfilter-01.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
10</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
03-Jul-02</FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; This document describes how to adapt the =
Session Description Protocol</FONT>
<BR><FONT SIZE=3D2>&gt; (SDP) to express one or more source addresses =
as a source filter for</FONT>
<BR><FONT SIZE=3D2>&gt; one or more destination 'connection' =
addresses.&nbsp; It defines the syntax</FONT>
<BR><FONT SIZE=3D2>&gt; and semantics for an SDP 'source-filter' =
attribute that may reference</FONT>
<BR><FONT SIZE=3D2>&gt; either IPv4 or IPv6 address(es) as either an =
inclusive or exclusive</FONT>
<BR><FONT SIZE=3D2>&gt; source list for either multicast or unicast =
destinations.&nbsp; In </FONT>
<BR><FONT SIZE=3D2>&gt; particular,an inclusive source-filter can be =
used to specify </FONT>
<BR><FONT SIZE=3D2>&gt; a Source-Specific Multicast ('SSM') =
session.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Receiver applications are expected use the SDP =
source-filter</FONT>
<BR><FONT SIZE=3D2>&gt; information to identify traffic from legitimate =
senders and discard</FONT>
<BR><FONT SIZE=3D2>&gt; traffic from illegitimate senders.&nbsp; =
Applications and hosts may also</FONT>
<BR><FONT SIZE=3D2>&gt; share the source-filter information with =
network elements (e.g., with</FONT>
<BR><FONT SIZE=3D2>&gt; routers using IGMPv3) so they can potentially =
perform the traffic</FONT>
<BR><FONT SIZE=3D2>&gt; filtering operation further 'upstream,' closer =
to the source(s).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; A URL for this Internet-Draft is:</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-srcf" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-mmusic-=
sdp-srcf</A></FONT>
<BR><FONT SIZE=3D2>ilter-01.txt</FONT>
</P>

<P><FONT SIZE=3D2>To remove yourself from the IETF Announcement list, =
send a message to </FONT>
<BR><FONT SIZE=3D2>ietf-announce-request with the word unsubscribe in =
the body of the message.</FONT>
</P>

<P><FONT SIZE=3D2>Internet-Drafts are also available by anonymous FTP. =
Login with the username</FONT>
<BR><FONT SIZE=3D2>&quot;anonymous&quot; and a password of your e-mail =
address. After logging in,</FONT>
<BR><FONT SIZE=3D2>type &quot;cd internet-drafts&quot; and then</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>&quot;get =
draft-ietf-mmusic-sdp-srcfilter-01.txt&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>A list of Internet-Drafts directories can be found =
in</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT>
<BR><FONT SIZE=3D2>or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Internet-Drafts can also be obtained by =
e-mail.</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C22BE9.3009A32C--

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


From daemon@ns.ietf.org  Wed Jul 17 22:44: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 WAA08614
	for <mmusic-archive@odin.ietf.org>; Wed, 17 Jul 2002 22:44:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA19654
	for mmusic-archive@odin.ietf.org; Wed, 17 Jul 2002 22:45: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 WAA19472;
	Wed, 17 Jul 2002 22:40: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 WAA19443
	for <mmusic@ns.ietf.org>; Wed, 17 Jul 2002 22:40:09 -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 WAA08407
	for <mmusic@ietf.org>; Wed, 17 Jul 2002 22:39:07 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXHFT>; Thu, 18 Jul 2002 05:39:30 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A1@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'mmusic@ietf.org'" <mmusic@ietf.org>
Date: Thu, 18 Jul 2002 05:39:29 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Subject: [MMUSIC] draft-even-mmusic-video-media-control-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

Hi,
During the meeting the discussion was about the new picture attribute.
The options were to have it as a new attribute as suggested by the draft or
to use RTCP for requesting the new picture.

We have two uses for new pictures one is an indication and the other is a
request.

The indication is not mandating the sending of the new picture. The
situation it addresses is that during the stream flow the receiver lost
synchronization and want help from the encoder. The encoder can decide to
send a new picture or can start referencing a previous picture that was sent
previously. In the new codecs the decoder can have more then one reference
picture in storage.
The other  case is a request is when the stream change and the receiver
cannot use previous information. So it needs a new picture.
I think that RTCP is good for the first case and having an attribute is
important for the second case. I think the text should explain the
difference cases.

**********************************************
Roni Even
Polycom Network Systems
Tel: +972-3-9251200
Mobile: +972-55-481099
Fax: +972-3-9211571
Email: roni.even@polycom.co.il


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



From daemon@ns.ietf.org  Wed Jul 17 23:34: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 XAA09702
	for <mmusic-archive@odin.ietf.org>; Wed, 17 Jul 2002 23:34:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA22084
	for mmusic-archive@odin.ietf.org; Wed, 17 Jul 2002 23:35:25 -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 XAA22027;
	Wed, 17 Jul 2002 23:31:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA21996
	for <mmusic@ns.ietf.org>; Wed, 17 Jul 2002 23:31:53 -0400 (EDT)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09648
	for <mmusic@ietf.org>; Wed, 17 Jul 2002 23:30:53 -0400 (EDT)
Received: from oak.ietf54.wide.ad.jp (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.11.6/8.11.6) with ESMTP id g6I3VLw03294
	for <mmusic@ietf.org>; Wed, 17 Jul 2002 20:31:21 -0700 (PDT)
	(envelope-from casner@packetdesign.com)
X-Received: from oak.ietf54.wide.ad.jp (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.11.6/8.11.6) with ESMTP id g6I3LPw03075;
	Wed, 17 Jul 2002 20:21:25 -0700 (PDT)
	(envelope-from casner@packetdesign.com)
Date: Wed, 17 Jul 2002 20:42:42 -0700 (Pacific Daylight Time)
From: Stephen Casner <casner@packetdesign.com>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1A1@ACCORD-NTSRV3>
Message-ID: <Pine.WNT.4.30.0207172008400.-483215@oak.ietf54.wide.ad.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
ReSent-Date: Wed, 17 Jul 2002 20:52:31 -0700 (Pacific Daylight Time)
ReSent-From: Stephen Casner <casner@packetdesign.com>
ReSent-To: <mmusic@ietf.org>
ReSent-Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
ReSent-Message-ID: <Pine.WNT.4.30.0207172052310.-483215@oak.ietf54.wide.ad.jp>
ReSent-Sender: casner@packetdesign.com
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

Roni,

> The indication is not mandating the sending of the new picture. The
> situation it addresses is that during the stream flow the receiver lost
> synchronization and want help from the encoder. The encoder can decide to
> send a new picture or can start referencing a previous picture that was sent
> previously. In the new codecs the decoder can have more then one reference
> picture in storage.
> The other  case is a request is when the stream change and the receiver
> cannot use previous information. So it needs a new picture.

For the first case, do you need to indicate which (one or more)
reference picture(s) you do have and could use?  For the second case,
that set is empty.  So you might call these two indications or two
variations on one indication.

> I think that RTCP is good for the first case and having an attribute is
> important for the second case. I think the text should explain the
> difference cases.

I don't agree.  In both cases, the receiver is saying "Help, I can't
display a picture until you send different data."  In both cases, the
server may have to (implicitly) reply, "Sorry, I can't help you right
now."  There is no qualitative difference between the two situations.

As I said before, the argument at the last IETF was about whether the
document can say the server MUST send a new picture.  As Jonathan said
in MMUSIC today, using the attribute rather than RTCP does not affect
that argument.

We could say something like this:

    The transmitter MUST implement the capability to send a new
    intra-coded frame when requested via <the RTCP feedback
    mechanism>.  However, in some situations, the transmitter may not
    be able to respond to such a request due to congestion control or
    other considerations.  The transmitter MUST consider bandwidth
    limitations in deciding whether or when to respond to such a
    request.  In particular, the transmitter must prevent a receiver
    from inducing congestion by repeatedly requesting intra-coded
    frames.

                                                        -- Steve


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



From daemon@ns.ietf.org  Thu Jul 18 00:05: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 AAA10250
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 00:05:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA23407
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 00:06: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 AAA23194;
	Thu, 18 Jul 2002 00:04:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA21215
	for <mmusic@ns.ietf.org>; Wed, 17 Jul 2002 23:22:43 -0400 (EDT)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09473
	for <mmusic@ietf.org>; Wed, 17 Jul 2002 23:21:44 -0400 (EDT)
Received: from oak.ietf54.wide.ad.jp (main-fw-eth1.packetdesign.com [192.168.0.254])
	by mailman.packetdesign.com (8.11.6/8.11.6) with ESMTP id g6I3LPw03075;
	Wed, 17 Jul 2002 20:21:25 -0700 (PDT)
	(envelope-from casner@packetdesign.com)
Date: Wed, 17 Jul 2002 20:42:42 -0700 (Pacific Daylight Time)
From: Stephen Casner <casner@packetdesign.com>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1A1@ACCORD-NTSRV3>
Message-ID: <Pine.WNT.4.30.0207172008400.-483215@oak.ietf54.wide.ad.jp>
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

Roni,

> The indication is not mandating the sending of the new picture. The
> situation it addresses is that during the stream flow the receiver lost
> synchronization and want help from the encoder. The encoder can decide to
> send a new picture or can start referencing a previous picture that was sent
> previously. In the new codecs the decoder can have more then one reference
> picture in storage.
> The other  case is a request is when the stream change and the receiver
> cannot use previous information. So it needs a new picture.

For the first case, do you need to indicate which (one or more)
reference picture(s) you do have and could use?  For the second case,
that set is empty.  So you might call these two indications or two
variations on one indication.

> I think that RTCP is good for the first case and having an attribute is
> important for the second case. I think the text should explain the
> difference cases.

I don't agree.  In both cases, the receiver is saying "Help, I can't
display a picture until you send different data."  In both cases, the
server may have to (implicitly) reply, "Sorry, I can't help you right
now."  There is no qualitative difference between the two situations.

As I said before, the argument at the last IETF was about whether the
document can say the server MUST send a new picture.  As Jonathan said
in MMUSIC today, using the attribute rather than RTCP does not affect
that argument.

We could say something like this:

    The transmitter MUST implement the capability to send a new
    intra-coded frame when requested via <the RTCP feedback
    mechanism>.  However, in some situations, the transmitter may not
    be able to respond to such a request due to congestion control or
    other considerations.  The transmitter MUST consider bandwidth
    limitations in deciding whether or when to respond to such a
    request.  In particular, the transmitter must prevent a receiver
    from inducing congestion by repeatedly requesting intra-coded
    frames.

                                                        -- Steve



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



From daemon@ns.ietf.org  Thu Jul 18 00:46: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 AAA11098
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 00:46:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA25696
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 00: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 AAA25329;
	Thu, 18 Jul 2002 00:39: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 AAA25283
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 00:39: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 AAA10951;
	Thu, 18 Jul 2002 00:38:00 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXJ5P>; Thu, 18 Jul 2002 07:38:21 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A2@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Stephen Casner'" <casner@packetdesign.com>, mmusic@ietf.org
Cc: "'mmusic@ietf.org'" <mmusic@ietf.org>
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
Date: Thu, 18 Jul 2002 07:38:13 +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

Stephan,
The situation is very different.
In the first case the receiver lost synchronization, maybe due to loss and
want some error correction, it is up to the encoder to decide what to do,
for example to reduce the rate or to change reference picture. In the second
case the need is for restarting the stream ASAP any other policy from the
encoder will not work, it is not a problem indication!!!! due to congestion
is just a switch of stream that the decoder needs to start decoding. There
was no problem in the transport it is a change in the stream state and that
is why I think it should be an attribute
Roni

> -----Original Message-----
> From: Stephen Casner [mailto:casner@packetdesign.com]
> Sent: Thursday, July 18, 2002 6:53 AM
> To: mmusic@ietf.org
> Cc: 'mmusic@ietf.org'
> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
> 
> 
> Roni,
> 
> > The indication is not mandating the sending of the new picture. The
> > situation it addresses is that during the stream flow the 
> receiver lost
> > synchronization and want help from the encoder. The encoder 
> can decide to
> > send a new picture or can start referencing a previous 
> picture that was sent
> > previously. In the new codecs the decoder can have more 
> then one reference
> > picture in storage.
> > The other  case is a request is when the stream change and 
> the receiver
> > cannot use previous information. So it needs a new picture.
> 
> For the first case, do you need to indicate which (one or more)
> reference picture(s) you do have and could use?  For the second case,
> that set is empty.  So you might call these two indications or two
> variations on one indication.
> 
> > I think that RTCP is good for the first case and having an 
> attribute is
> > important for the second case. I think the text should explain the
> > difference cases.
> 
> I don't agree.  In both cases, the receiver is saying "Help, I can't
> display a picture until you send different data."  In both cases, the
> server may have to (implicitly) reply, "Sorry, I can't help you right
> now."  There is no qualitative difference between the two situations.
> 
> As I said before, the argument at the last IETF was about whether the
> document can say the server MUST send a new picture.  As Jonathan said
> in MMUSIC today, using the attribute rather than RTCP does not affect
> that argument.
> 
> We could say something like this:
> 
>     The transmitter MUST implement the capability to send a new
>     intra-coded frame when requested via <the RTCP feedback
>     mechanism>.  However, in some situations, the transmitter may not
>     be able to respond to such a request due to congestion control or
>     other considerations.  The transmitter MUST consider bandwidth
>     limitations in deciding whether or when to respond to such a
>     request.  In particular, the transmitter must prevent a receiver
>     from inducing congestion by repeatedly requesting intra-coded
>     frames.
> 
>                                                         -- Steve
> 
> 
> _______________________________________________
> 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@ns.ietf.org  Thu Jul 18 00:57:05 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 AAA11217
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 00:57:05 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA25967
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 00:58: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 AAA25923;
	Thu, 18 Jul 2002 00:56:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA25896
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 00:56:20 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11205
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 00:55:22 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g6I4tYYH010795;
	Thu, 18 Jul 2002 00:55:36 -0400 (EDT)
Message-ID: <3D364A43.9070507@dynamicsoft.com>
Date: Thu, 18 Jul 2002 13:55:31 +0900
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: "Even, Roni" <roni.even@polycom.co.il>
CC: "'Stephen Casner'" <casner@packetdesign.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
References: <B2518D608282D511BEA400508BBB9148EAA1A2@ACCORD-NTSRV3>
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



Even, Roni wrote:
> Stephan,
> The situation is very different.
> In the first case the receiver lost synchronization, maybe due to loss
> and
> want some error correction, it is up to the encoder to decide what to
> do,
> for example to reduce the rate or to change reference picture. In the
> second
> case the need is for restarting the stream ASAP any other policy from
> the
> encoder will not work, it is not a problem indication!!!! 

And how does the sender KNOW that the receiver has asked for this 
bandwidth-intensive update because it has actually decided to change 
reference picture? What is to stop someone from deciding that they want 
the maximal picture quality, so that when they have loss an their 
quality degrades, they send the "force intra-req" message?

The sends has to make sure it obeys congestion control guidelines, 
independent of what someone else says.

-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@ns.ietf.org  Thu Jul 18 01:35:35 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 BAA12455
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 01:35:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA07168
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 01:36: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 BAA06974;
	Thu, 18 Jul 2002 01:35:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06943
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 01:35:19 -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 BAA12399
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 01:34:19 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXLD1>; Thu, 18 Jul 2002 08:34:42 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A3@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Even, Roni"
	 <roni.even@polycom.co.il>
Cc: "'Stephen Casner'" <casner@packetdesign.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
Date: Thu, 18 Jul 2002 08:34:41 +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

Jonathan,
I agree and that is why I think we need two different methods. The RTCP is
defined to monitor the quality of service of the received stream  and that
is why this is an indication, I would not like to use it for requests and I
think that it was the consensus in the previous IETF AVT meeting.. What we
want with the attribute, and the text will say it, is that it is intended to
be used only when the receiver wants to receive a new stream due to change
of source. We can call the attribute "new stream" so it will be clearer. As
for abusing the usage this may happen in many aspects of protocols, if the
text clarifies the usage then any one who does  differently abuses the
protocol.
The request for a new stream as I view it is like changing the state since
the receiver wants to get a new stream or switch the current stream he is
receiving, the same can be said when he asks for new orientation like
changing from portrait to landscape on the current stream.
Thanks
Roni Even

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> Sent: Thursday, July 18, 2002 7:56 AM
> To: Even, Roni
> Cc: 'Stephen Caner'; mmusic@ietf.org
> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
> 
> 
> 
> 
> Even, Roni wrote:
> > Stephan,
> > The situation is very different.
> > In the first case the receiver lost synchronization, maybe 
> due to loss
> > and
> > want some error correction, it is up to the encoder to 
> decide what to
> > do,
> > for example to reduce the rate or to change reference 
> picture. In the
> > second
> > case the need is for restarting the stream ASAP any other 
> policy from
> > the
> > encoder will not work, it is not a problem indication!!!! 
> 
> And how does the sender KNOW that the receiver has asked for this 
> bandwidth-intensive update because it has actually decided to change 
> reference picture? What is to stop someone from deciding that 
> they want 
> the maximal picture quality, so that when they have loss an their 
> quality degrades, they send the "force intra-req" message?
> 
> The sends has to make sure it obeys congestion control guidelines, 
> independent of what someone else says.
> 
> -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@ns.ietf.org  Thu Jul 18 01:48:22 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 BAA13085
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 01:48:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08170
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 01:49:20 -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 BAA07710;
	Thu, 18 Jul 2002 01:44:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA07679
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 01:44:37 -0400 (EDT)
Received: from purple.nge.isi.edu (ietf-wireless-dhcp-71-239.dyn.ietf54.wide.ad.jp [133.93.71.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12724
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 01:43:38 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6I5iPnm001199;
	Thu, 18 Jul 2002 01:44:25 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207180544.g6I5iPnm001199@purple.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Stephen Casner'" <casner@packetdesign.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
In-Reply-To: Your message of "Thu, 18 Jul 2002 08:34:41 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1A3@ACCORD-NTSRV3> 
Date: Thu, 18 Jul 2002 14:44:25 +0900
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

Roni,

The objection from previous AVT meetings was that the RTCP indication could
not say "MUST send an intra-frame", because there may be reasons why it is
not appropriate for the sender to do so (for example, but not limited to,
congestion on the forward path).  Those reasons exist no matter how the
request is signalled, and using an attribute instead will not change that.

Colin



--> "Even, Roni" writes:
>Jonathan,
>I agree and that is why I think we need two different methods. The RTCP is
>defined to monitor the quality of service of the received stream  and that
>is why this is an indication, I would not like to use it for requests and I
>think that it was the consensus in the previous IETF AVT meeting.. What we
>want with the attribute, and the text will say it, is that it is intended to
>be used only when the receiver wants to receive a new stream due to change
>of source. We can call the attribute "new stream" so it will be clearer. As
>for abusing the usage this may happen in many aspects of protocols, if the
>text clarifies the usage then any one who does  differently abuses the
>protocol.
>The request for a new stream as I view it is like changing the state since
>the receiver wants to get a new stream or switch the current stream he is
>receiving, the same can be said when he asks for new orientation like
>changing from portrait to landscape on the current stream.
>Thanks
>Roni Even
>
>> -----Original Message-----
>> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
>> Sent: Thursday, July 18, 2002 7:56 AM
>> To: Even, Roni
>> Cc: 'Stephen Caner'; mmusic@ietf.org
>> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
>> 
>> 
>> 
>> 
>> Even, Roni wrote:
>> > Stephan,
>> > The situation is very different.
>> > In the first case the receiver lost synchronization, maybe 
>> due to loss
>> > and
>> > want some error correction, it is up to the encoder to 
>> decide what to
>> > do,
>> > for example to reduce the rate or to change reference 
>> picture. In the
>> > second
>> > case the need is for restarting the stream ASAP any other 
>> policy from
>> > the
>> > encoder will not work, it is not a problem indication!!!! 
>> 
>> And how does the sender KNOW that the receiver has asked for this 
>> bandwidth-intensive update because it has actually decided to change 
>> reference picture? What is to stop someone from deciding that 
>> they want 
>> the maximal picture quality, so that when they have loss an their 
>> quality degrades, they send the "force intra-req" message?
>> 
>> The sends has to make sure it obeys congestion control guidelines, 
>> independent of what someone else says.
>> 
>> -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

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



From daemon@ns.ietf.org  Thu Jul 18 01:53: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 BAA13596
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 01:53:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08688
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 01:54:28 -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 BAA08638;
	Thu, 18 Jul 2002 01:53: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 BAA08611
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 01:53:25 -0400 (EDT)
Received: from purple.nge.isi.edu (ietf-wireless-dhcp-71-239.dyn.ietf54.wide.ad.jp [133.93.71.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13586
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 01:52:25 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6I5rTnm001420;
	Thu, 18 Jul 2002 01:53:29 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207180553.g6I5rTnm001420@purple.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
In-Reply-To: Your message of "Thu, 18 Jul 2002 08:49:52 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1A4@ACCORD-NTSRV3> 
Date: Thu, 18 Jul 2002 14:53:29 +0900
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

But, the key point is, "request" a new intra. In neither case can it
require that a new intra is sent.

Colin



--> "Even, Roni" writes:
>Colin,
>I agree to the RTCP semantic, I do not agree to the meaning of attribute,
>since any attribute that you will use in re-invite in video will have the
>same affect as request for a new intra. And as I said the difference in the
>situation in that the receiver does not inform the sender of QOS problem as
>stated in the RTCP definition in the RTP draft.
>Roni
>
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@isi.edu]
>> Sent: Thursday, July 18, 2002 8:44 AM
>> To: Even, Roni
>> Cc: 'Jonathan Rosenberg'; 'Stephen Casner'; mmusic@ietf.org
>> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
>> 
>> 
>> Roni,
>> 
>> The objection from previous AVT meetings was that the RTCP 
>> indication could
>> not say "MUST send an intra-frame", because there may be 
>> reasons why it is
>> not appropriate for the sender to do so (for example, but not 
>> limited to,
>> congestion on the forward path).  Those reasons exist no 
>> matter how the
>> request is signalled, and using an attribute instead will not 
>> change that.
>> 
>> Colin
>> 
>> 
>> 
>> --> "Even, Roni" writes:
>> >Jonathan,
>> >I agree and that is why I think we need two different 
>> methods. The RTCP is
>> >defined to monitor the quality of service of the received 
>> stream  and that
>> >is why this is an indication, I would not like to use it for 
>> requests and I
>> >think that it was the consensus in the previous IETF AVT 
>> meeting.. What we
>> >want with the attribute, and the text will say it, is that 
>> it is intended to
>> >be used only when the receiver wants to receive a new stream 
>> due to change
>> >of source. We can call the attribute "new stream" so it will 
>> be clearer. As
>> >for abusing the usage this may happen in many aspects of 
>> protocols, if the
>> >text clarifies the usage then any one who does  differently 
>> abuses the
>> >protocol.
>> >The request for a new stream as I view it is like changing 
>> the state since
>> >the receiver wants to get a new stream or switch the current 
>> stream he is
>> >receiving, the same can be said when he asks for new orientation like
>> >changing from portrait to landscape on the current stream.
>> >Thanks
>> >Roni Even
>> >
>> >> -----Original Message-----
>> >> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
>> >> Sent: Thursday, July 18, 2002 7:56 AM
>> >> To: Even, Roni
>> >> Cc: 'Stephen Caner'; mmusic@ietf.org
>> >> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
>> >> 
>> >> 
>> >> 
>> >> 
>> >> Even, Roni wrote:
>> >> > Stephan,
>> >> > The situation is very different.
>> >> > In the first case the receiver lost synchronization, maybe 
>> >> due to loss
>> >> > and
>> >> > want some error correction, it is up to the encoder to 
>> >> decide what to
>> >> > do,
>> >> > for example to reduce the rate or to change reference 
>> >> picture. In the
>> >> > second
>> >> > case the need is for restarting the stream ASAP any other 
>> >> policy from
>> >> > the
>> >> > encoder will not work, it is not a problem indication!!!! 
>> >> 
>> >> And how does the sender KNOW that the receiver has asked for this 
>> >> bandwidth-intensive update because it has actually decided 
>> to change 
>> >> reference picture? What is to stop someone from deciding that 
>> >> they want 
>> >> the maximal picture quality, so that when they have loss an their 
>> >> quality degrades, they send the "force intra-req" message?
>> >> 
>> >> The sends has to make sure it obeys congestion control guidelines, 
>> >> independent of what someone else says.
>> >> 
>> >> -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
>> 
>
>_______________________________________________
>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@ns.ietf.org  Thu Jul 18 01:54:00 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 BAA13638
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 01:54:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08712
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 01:54: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 BAA08374;
	Thu, 18 Jul 2002 01:50: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 BAA08343
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 01:50: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 BAA13440
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 01:49:30 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXL3W>; Thu, 18 Jul 2002 08:49:53 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A4@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Even, Roni" <roni.even@polycom.co.il>
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
Date: Thu, 18 Jul 2002 08:49:52 +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

Colin,
I agree to the RTCP semantic, I do not agree to the meaning of attribute,
since any attribute that you will use in re-invite in video will have the
same affect as request for a new intra. And as I said the difference in the
situation in that the receiver does not inform the sender of QOS problem as
stated in the RTCP definition in the RTP draft.
Roni

> -----Original Message-----
> From: Colin Perkins [mailto:csp@isi.edu]
> Sent: Thursday, July 18, 2002 8:44 AM
> To: Even, Roni
> Cc: 'Jonathan Rosenberg'; 'Stephen Casner'; mmusic@ietf.org
> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
> 
> 
> Roni,
> 
> The objection from previous AVT meetings was that the RTCP 
> indication could
> not say "MUST send an intra-frame", because there may be 
> reasons why it is
> not appropriate for the sender to do so (for example, but not 
> limited to,
> congestion on the forward path).  Those reasons exist no 
> matter how the
> request is signalled, and using an attribute instead will not 
> change that.
> 
> Colin
> 
> 
> 
> --> "Even, Roni" writes:
> >Jonathan,
> >I agree and that is why I think we need two different 
> methods. The RTCP is
> >defined to monitor the quality of service of the received 
> stream  and that
> >is why this is an indication, I would not like to use it for 
> requests and I
> >think that it was the consensus in the previous IETF AVT 
> meeting.. What we
> >want with the attribute, and the text will say it, is that 
> it is intended to
> >be used only when the receiver wants to receive a new stream 
> due to change
> >of source. We can call the attribute "new stream" so it will 
> be clearer. As
> >for abusing the usage this may happen in many aspects of 
> protocols, if the
> >text clarifies the usage then any one who does  differently 
> abuses the
> >protocol.
> >The request for a new stream as I view it is like changing 
> the state since
> >the receiver wants to get a new stream or switch the current 
> stream he is
> >receiving, the same can be said when he asks for new orientation like
> >changing from portrait to landscape on the current stream.
> >Thanks
> >Roni Even
> >
> >> -----Original Message-----
> >> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> >> Sent: Thursday, July 18, 2002 7:56 AM
> >> To: Even, Roni
> >> Cc: 'Stephen Caner'; mmusic@ietf.org
> >> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
> >> 
> >> 
> >> 
> >> 
> >> Even, Roni wrote:
> >> > Stephan,
> >> > The situation is very different.
> >> > In the first case the receiver lost synchronization, maybe 
> >> due to loss
> >> > and
> >> > want some error correction, it is up to the encoder to 
> >> decide what to
> >> > do,
> >> > for example to reduce the rate or to change reference 
> >> picture. In the
> >> > second
> >> > case the need is for restarting the stream ASAP any other 
> >> policy from
> >> > the
> >> > encoder will not work, it is not a problem indication!!!! 
> >> 
> >> And how does the sender KNOW that the receiver has asked for this 
> >> bandwidth-intensive update because it has actually decided 
> to change 
> >> reference picture? What is to stop someone from deciding that 
> >> they want 
> >> the maximal picture quality, so that when they have loss an their 
> >> quality degrades, they send the "force intra-req" message?
> >> 
> >> The sends has to make sure it obeys congestion control guidelines, 
> >> independent of what someone else says.
> >> 
> >> -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
> 

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



From daemon@ns.ietf.org  Thu Jul 18 02:06:20 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 CAA22490
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 02:06:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA09979
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 02:07:18 -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 CAA09873;
	Thu, 18 Jul 2002 02:05:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09769
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 02:05:48 -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 CAA20361
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 02:04:49 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6I64ZW27482;
	Thu, 18 Jul 2002 02:04:35 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NYVCFZYJ>; Thu, 18 Jul 2002 02:04:34 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A69D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Colin Perkins'" <csp@isi.edu>, "Even, Roni" <roni.even@polycom.co.il>
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Stephen Casner'"
	 <casner@packetdesign.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
Date: Thu, 18 Jul 2002 02:04:32 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
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



Would it satisfy everyone to make that "SHOULD send an intra-frame"?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Thursday, July 18, 2002 1:44 AM
To: Even, Roni
Cc: 'Jonathan Rosenberg'; 'Stephen Casner'; mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 


Roni,

The objection from previous AVT meetings was that the RTCP indication could
not say "MUST send an intra-frame", because there may be reasons why it is
not appropriate for the sender to do so (for example, but not limited to,
congestion on the forward path).  Those reasons exist no matter how the
request is signalled, and using an attribute instead will not change that.

Colin



--> "Even, Roni" writes:
>Jonathan,
>I agree and that is why I think we need two different methods. The RTCP is
>defined to monitor the quality of service of the received stream  and that
>is why this is an indication, I would not like to use it for requests and I
>think that it was the consensus in the previous IETF AVT meeting.. What we
>want with the attribute, and the text will say it, is that it is intended
to
>be used only when the receiver wants to receive a new stream due to change
>of source. We can call the attribute "new stream" so it will be clearer. As
>for abusing the usage this may happen in many aspects of protocols, if the
>text clarifies the usage then any one who does  differently abuses the
>protocol.
>The request for a new stream as I view it is like changing the state since
>the receiver wants to get a new stream or switch the current stream he is
>receiving, the same can be said when he asks for new orientation like
>changing from portrait to landscape on the current stream.
>Thanks
>Roni Even
>
>> -----Original Message-----
>> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
>> Sent: Thursday, July 18, 2002 7:56 AM
>> To: Even, Roni
>> Cc: 'Stephen Caner'; mmusic@ietf.org
>> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
>> 
>> 
>> 
>> 
>> Even, Roni wrote:
>> > Stephan,
>> > The situation is very different.
>> > In the first case the receiver lost synchronization, maybe 
>> due to loss
>> > and
>> > want some error correction, it is up to the encoder to 
>> decide what to
>> > do,
>> > for example to reduce the rate or to change reference 
>> picture. In the
>> > second
>> > case the need is for restarting the stream ASAP any other 
>> policy from
>> > the
>> > encoder will not work, it is not a problem indication!!!! 
>> 
>> And how does the sender KNOW that the receiver has asked for this 
>> bandwidth-intensive update because it has actually decided to change 
>> reference picture? What is to stop someone from deciding that 
>> they want 
>> the maximal picture quality, so that when they have loss an their 
>> quality degrades, they send the "force intra-req" message?
>> 
>> The sends has to make sure it obeys congestion control guidelines, 
>> independent of what someone else says.
>> 
>> -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

_______________________________________________
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@ns.ietf.org  Thu Jul 18 02:06:27 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 CAA22664
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 02:06:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA10001
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 02:07:25 -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 CAA09922;
	Thu, 18 Jul 2002 02:06:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09891
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 02:06:19 -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 CAA21090
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 02:05:20 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXL58>; Thu, 18 Jul 2002 09:05:43 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A6@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: mmusic@ietf.org
Date: Thu, 18 Jul 2002 09:05:38 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Subject: [MMUSIC] draft-even-mmusic-video-media-control-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

Hi,
I think I would like to put focus on the subject
1. In order to support simple voice activated video switching conference
with end-points that are not conference aware. This is the most basic video
conference. We need to be able to have a clean video switch. This means that
like when you change a channel in your cables, you may see a blank screen
and then you will see the new channel without any artifact. 
2. The process includes a freeze n the receiver and new stream from the new
sender.
3. I think we agree that the freeze is an attribute.
4. From the options I presented for the new streams there were two that are
being discussed.
 4.1 use the RTCP feedback - the current meaning of the RTCP message is an
indication of a QOS problem.
 4.2 Use a new SDP attribute. - the discussion was if that is a stream state
change - I argued that to the receiver it is a change in the state of the
stream he will receive
5. I prefer to use the attribute.
   5.1. It makes the process use the same protocol layer as the freeze -
both will be SDP based
  5.2 it does not change the meaning of the RTCP indication.

Thanks

Roni Even

**********************************************
Roni Even

Polycom Network Systems
Tel: +972-3-9251200
Mobile: +972-55-481099
Fax: +972-3-9211571
Email: roni.even@polycom.co.il


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



From daemon@ns.ietf.org  Thu Jul 18 02:13: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 CAA23075
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 02:13:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA10190
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 02: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 CAA10072;
	Thu, 18 Jul 2002 02:09:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10040
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 02:09:49 -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 CAA23034
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 02:08:50 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXL85>; Thu, 18 Jul 2002 09:09:13 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1A7@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Colin Perkins'" <csp@isi.edu>
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
Date: Thu, 18 Jul 2002 09:09:03 +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

Colin,
In the case of the video switch there is no other way that the encoder can
fix the problem for the receiver without sending a new full picture. Also it
was not a problem with QOS and encoder will still follow the bandwidth
limitation of the session so there is no problem with adding congestion
Roni

> -----Original Message-----
> From: Colin Perkins [mailto:csp@isi.edu]
> Sent: Thursday, July 18, 2002 8:53 AM
> To: Even, Roni
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
> 
> 
> But, the key point is, "request" a new intra. In neither case can it
> require that a new intra is sent.
> 
> Colin
> 
> 
> 
> --> "Even, Roni" writes:
> >Colin,
> >I agree to the RTCP semantic, I do not agree to the meaning 
> of attribute,
> >since any attribute that you will use in re-invite in video 
> will have the
> >same affect as request for a new intra. And as I said the 
> difference in the
> >situation in that the receiver does not inform the sender of 
> QOS problem as
> >stated in the RTCP definition in the RTP draft.
> >Roni
> >
> >> -----Original Message-----
> >> From: Colin Perkins [mailto:csp@isi.edu]
> >> Sent: Thursday, July 18, 2002 8:44 AM
> >> To: Even, Roni
> >> Cc: 'Jonathan Rosenberg'; 'Stephen Casner'; mmusic@ietf.org
> >> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
> >> 
> >> 
> >> Roni,
> >> 
> >> The objection from previous AVT meetings was that the RTCP 
> >> indication could
> >> not say "MUST send an intra-frame", because there may be 
> >> reasons why it is
> >> not appropriate for the sender to do so (for example, but not 
> >> limited to,
> >> congestion on the forward path).  Those reasons exist no 
> >> matter how the
> >> request is signalled, and using an attribute instead will not 
> >> change that.
> >> 
> >> Colin
> >> 
> >> 
> >> 
> >> --> "Even, Roni" writes:
> >> >Jonathan,
> >> >I agree and that is why I think we need two different 
> >> methods. The RTCP is
> >> >defined to monitor the quality of service of the received 
> >> stream  and that
> >> >is why this is an indication, I would not like to use it for 
> >> requests and I
> >> >think that it was the consensus in the previous IETF AVT 
> >> meeting.. What we
> >> >want with the attribute, and the text will say it, is that 
> >> it is intended to
> >> >be used only when the receiver wants to receive a new stream 
> >> due to change
> >> >of source. We can call the attribute "new stream" so it will 
> >> be clearer. As
> >> >for abusing the usage this may happen in many aspects of 
> >> protocols, if the
> >> >text clarifies the usage then any one who does  differently 
> >> abuses the
> >> >protocol.
> >> >The request for a new stream as I view it is like changing 
> >> the state since
> >> >the receiver wants to get a new stream or switch the current 
> >> stream he is
> >> >receiving, the same can be said when he asks for new 
> orientation like
> >> >changing from portrait to landscape on the current stream.
> >> >Thanks
> >> >Roni Even
> >> >
> >> >> -----Original Message-----
> >> >> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> >> >> Sent: Thursday, July 18, 2002 7:56 AM
> >> >> To: Even, Roni
> >> >> Cc: 'Stephen Caner'; mmusic@ietf.org
> >> >> Subject: Re: [MMUSIC] 
> draft-even-mmusic-video-media-control-00.txt
> >> >> 
> >> >> 
> >> >> 
> >> >> 
> >> >> Even, Roni wrote:
> >> >> > Stephan,
> >> >> > The situation is very different.
> >> >> > In the first case the receiver lost synchronization, maybe 
> >> >> due to loss
> >> >> > and
> >> >> > want some error correction, it is up to the encoder to 
> >> >> decide what to
> >> >> > do,
> >> >> > for example to reduce the rate or to change reference 
> >> >> picture. In the
> >> >> > second
> >> >> > case the need is for restarting the stream ASAP any other 
> >> >> policy from
> >> >> > the
> >> >> > encoder will not work, it is not a problem indication!!!! 
> >> >> 
> >> >> And how does the sender KNOW that the receiver has 
> asked for this 
> >> >> bandwidth-intensive update because it has actually decided 
> >> to change 
> >> >> reference picture? What is to stop someone from deciding that 
> >> >> they want 
> >> >> the maximal picture quality, so that when they have 
> loss an their 
> >> >> quality degrades, they send the "force intra-req" message?
> >> >> 
> >> >> The sends has to make sure it obeys congestion control 
> guidelines, 
> >> >> independent of what someone else says.
> >> >> 
> >> >> -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
> >> 
> >
> >_______________________________________________
> >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@ns.ietf.org  Thu Jul 18 02:31: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 CAA23398
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 02:31:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA11273
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 02:32: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 CAA11094;
	Thu, 18 Jul 2002 02:31: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 CAA11052
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 02:31:15 -0400 (EDT)
Received: from purple.nge.isi.edu (ietf-wireless-dhcp-71-239.dyn.ietf54.wide.ad.jp [133.93.71.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23377
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 02:30:14 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6I6VInm001718;
	Thu, 18 Jul 2002 02:31:18 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207180631.g6I6VInm001718@purple.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
In-Reply-To: Your message of "Thu, 18 Jul 2002 09:09:03 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1A7@ACCORD-NTSRV3> 
Date: Thu, 18 Jul 2002 15:31:18 +0900
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

I understand. In some cases, for example if the network is congested, it
may not be possible to fix the problem.

Colin

--> "Even, Roni" writes:
>Colin,
>In the case of the video switch there is no other way that the encoder can
>fix the problem for the receiver without sending a new full picture. Also it
>was not a problem with QOS and encoder will still follow the bandwidth
>limitation of the session so there is no problem with adding congestion
>Roni
>
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@isi.edu]
>> Sent: Thursday, July 18, 2002 8:53 AM
>> To: Even, Roni
>> Cc: mmusic@ietf.org
>> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
>> 
>> 
>> But, the key point is, "request" a new intra. In neither case can it
>> require that a new intra is sent.
>> 
>> Colin
>> 
>> 
>> 
>> --> "Even, Roni" writes:
>> >Colin,
>> >I agree to the RTCP semantic, I do not agree to the meaning 
>> of attribute,
>> >since any attribute that you will use in re-invite in video 
>> will have the
>> >same affect as request for a new intra. And as I said the 
>> difference in the
>> >situation in that the receiver does not inform the sender of 
>> QOS problem as
> >stated in the RTCP definition in the RTP draft.
>> >Roni
>> >
>> >> -----Original Message-----
>> >> From: Colin Perkins [mailto:csp@isi.edu]
>> >> Sent: Thursday, July 18, 2002 8:44 AM
>> >> To: Even, Roni
>> >> Cc: 'Jonathan Rosenberg'; 'Stephen Casner'; mmusic@ietf.org
>> >> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
>> >> 
>> >> 
>> >> Roni,
>> >> 
>> >> The objection from previous AVT meetings was that the RTCP 
>> >> indication could
>> >> not say "MUST send an intra-frame", because there may be 
>> >> reasons why it is
>> >> not appropriate for the sender to do so (for example, but not 
>> >> limited to,
>> >> congestion on the forward path).  Those reasons exist no 
>> >> matter how the
>> >> request is signalled, and using an attribute instead will not 
>> >> change that.
>> >> 
>> >> Colin
>> >> 
>> >> 
>> >> 
>> >> --> "Even, Roni" writes:
>> >> >Jonathan,
>> >> >I agree and that is why I think we need two different 
>> >> methods. The RTCP is
>> >> >defined to monitor the quality of service of the received 
>> >> stream  and that
>> >> >is why this is an indication, I would not like to use it for 
>> >> requests and I
>> >> >think that it was the consensus in the previous IETF AVT 
>> >> meeting.. What we
>> >> >want with the attribute, and the text will say it, is that 
>> >> it is intended to
>> >> >be used only when the receiver wants to receive a new stream 
>> >> due to change
>> >> >of source. We can call the attribute "new stream" so it will 
>> >> be clearer. As
>> >> >for abusing the usage this may happen in many aspects of 
>> >> protocols, if the
>> >> >text clarifies the usage then any one who does  differently 
>> >> abuses the
>> >> >protocol.
>> >> >The request for a new stream as I view it is like changing 
>> >> the state since
>> >> >the receiver wants to get a new stream or switch the current 
>> >> stream he is
>> >> >receiving, the same can be said when he asks for new 
>> orientation like
>> >> >changing from portrait to landscape on the current stream.
>> >> >Thanks
>> >> >Roni Even
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
>> >> >> Sent: Thursday, July 18, 2002 7:56 AM
>> >> >> To: Even, Roni
>> >> >> Cc: 'Stephen Caner'; mmusic@ietf.org
>> >> >> Subject: Re: [MMUSIC] 
>> draft-even-mmusic-video-media-control-00.txt
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> Even, Roni wrote:
>> >> >> > Stephan,
>> >> >> > The situation is very different.
>> >> >> > In the first case the receiver lost synchronization, maybe 
>> >> >> due to loss
>> >> >> > and
>> >> >> > want some error correction, it is up to the encoder to 
>> >> >> decide what to
>> >> >> > do,
>> >> >> > for example to reduce the rate or to change reference 
>> >> >> picture. In the
>> >> >> > second
>> >> >> > case the need is for restarting the stream ASAP any other 
>> >> >> policy from
>> >> >> > the
>> >> >> > encoder will not work, it is not a problem indication!!!! 
>> >> >> 
>> >> >> And how does the sender KNOW that the receiver has 
>> asked for this 
>> >> >> bandwidth-intensive update because it has actually decided 
>> >> to change 
>> >> >> reference picture? What is to stop someone from deciding that 
>> >> >> they want 
>> >> >> the maximal picture quality, so that when they have 
>> loss an their 
>> >> >> quality degrades, they send the "force intra-req" message?
>> >> >> 
>> >> >> The sends has to make sure it obeys congestion control 
>> guidelines, 
>> >> >> independent of what someone else says.
>> >> >> 
>> >> >> -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
>> >> 
>> >
>> >_______________________________________________
>> >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@ns.ietf.org  Thu Jul 18 02:33: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 CAA23436
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 02:33:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA11372
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 02:34: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 CAA10919;
	Thu, 18 Jul 2002 02:30: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 CAA10885
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 02:30:32 -0400 (EDT)
Received: from purple.nge.isi.edu (ietf-wireless-dhcp-71-239.dyn.ietf54.wide.ad.jp [133.93.71.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23344
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 02:29:32 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6I6UWnm001685;
	Thu, 18 Jul 2002 02:30:32 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207180630.g6I6UWnm001685@purple.nge.isi.edu>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "Even, Roni" <roni.even@polycom.co.il>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Stephen Casner'" <casner@packetdesign.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt 
In-Reply-To: Your message of "Thu, 18 Jul 2002 02:04:32 -0400."
             <4D79C746863DD51197690002A52CDA0001E8A69D@zcard0kc.ca.nortel.com> 
Date: Thu, 18 Jul 2002 15:30:32 +0900
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

--> "Tom-PT Taylor" writes:
>Would it satisfy everyone to make that "SHOULD send an intra-frame"?

SHOULD send an intra-frame, provided this is possible which behaving in a
congestion controlled manner.

Colin

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



From daemon@ns.ietf.org  Thu Jul 18 03:13: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 DAA24308
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 03:13:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA13963
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 03:14:51 -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 DAA13745;
	Thu, 18 Jul 2002 03: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 DAA13715
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 03:08:00 -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 DAA24231
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 03:07:00 -0400 (EDT)
Received: (from jo@localhost)
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) id g6I77eq04402;
	Thu, 18 Jul 2002 09:07:40 +0200 (MEST)
From: Joerg Ott <jo@Informatik.Uni-Bremen.DE>
Message-Id: <200207180707.g6I77eq04402@nmh.informatik.uni-bremen.de>
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
To: roni.even@polycom.co.il (Even, Roni)
Date: Thu, 18 Jul 2002 09:07:40 +0200 (MEST)
Cc: jdrosen@dynamicsoft.com ('Jonathan Rosenberg'),
        roni.even@polycom.co.il (Even Roni),
        casner@packetdesign.com ('Stephen Casner'), mmusic@ietf.org
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1A3@ACCORD-NTSRV3> from "Even, Roni" at Jul 18, 2002 08:34:41 AM
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

> 
> Jonathan,
> I agree and that is why I think we need two different methods. The RTCP is
> defined to monitor the quality of service of the received stream  and that
> is why this is an indication, I would not like to use it for requests and I
> think that it was the consensus in the previous IETF AVT meeting.. What we
> want with the attribute, and the text will say it, is that it is intended to
> be used only when the receiver wants to receive a new stream due to change
> of source. We can call the attribute "new stream" so it will be clearer. As
> for abusing the usage this may happen in many aspects of protocols, if the
> text clarifies the usage then any one who does  differently abuses the
> protocol.

Sorry for the  delay in responding (in it may not matter too much anymore)
but: once you have set the "a=new-stream" attribute for the stream, how
are you going to indicate the next FIR (remember, it's state).

Joerg


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



From daemon@ns.ietf.org  Thu Jul 18 03:30: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 DAA24975
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 03:30:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA15206
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 03:31: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 DAA14395;
	Thu, 18 Jul 2002 03:26:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA14360
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 03:26: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 DAA24812
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 03:25:31 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXNYA>; Thu, 18 Jul 2002 10:25:54 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1AC@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@Informatik.Uni-Bremen.DE>,
        "Even, Roni"
	 <roni.even@polycom.co.il>
Cc: jdrosen@dynamicsoft.com, "Even, Roni" <roni.even@polycom.co.il>,
        casner@packetdesign.com, mmusic@ietf.org
Subject: RE: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
Date: Thu, 18 Jul 2002 10:25:48 +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,
The receiver want a new stream from the encoder. The encoder will restart
the stream he is sending. This changes the whole stream. For example, if in
a conference we had A, B and C.  A was viewed by B and C ,while A was
viewing C. Now we have a switch. C will still view A, while B and A will see
C. so for A, he still receive the same stream from C, and  nothing needs to
be changed. But we have a new viewer for stream C. So even though A was
seeing it we need to ask for a new stream from C. The stream  will be reset
for both A and B. The change is that even though A was receiving a stream
from C the request from the conference control to new picture changed the
stream flow for him as well as for B who is getting a new stream. So for
both A and B the stream state has changed, for them this is a new
stream!!!!!
Roni 

> -----Original Message-----
> From: Joerg Ott [mailto:jo@Informatik.Uni-Bremen.DE]
> Sent: Thursday, July 18, 2002 10:08 AM
> To: roni.even@polycom.co.il
> Cc: jdrosen@dynamicsoft.com; roni.even@polycom.co.il; 
> casner@packetdesign.com; mmusic@ietf.org
> Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
> 
> 
> > 
> > Jonathan,
> > I agree and that is why I think we need two different 
> methods. The RTCP is
> > defined to monitor the quality of service of the received 
> stream  and that
> > is why this is an indication, I would not like to use it 
> for requests and I
> > think that it was the consensus in the previous IETF AVT 
> meeting.. What we
> > want with the attribute, and the text will say it, is that 
> it is intended to
> > be used only when the receiver wants to receive a new 
> stream due to change
> > of source. We can call the attribute "new stream" so it 
> will be clearer. As
> > for abusing the usage this may happen in many aspects of 
> protocols, if the
> > text clarifies the usage then any one who does  differently 
> abuses the
> > protocol.
> 
> Sorry for the  delay in responding (in it may not matter too 
> much anymore)
> but: once you have set the "a=new-stream" attribute for the 
> stream, how
> are you going to indicate the next FIR (remember, it's state).
> 
> Joerg
> 

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



From daemon@ns.ietf.org  Thu Jul 18 03:34: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 DAA25086
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 03:34:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA15345
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 03:35:53 -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 DAA14555;
	Thu, 18 Jul 2002 03:28: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 DAA14522
	for <mmusic@ns.ietf.org>; Thu, 18 Jul 2002 03:28:24 -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 DAA24864
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 03:27:24 -0400 (EDT)
Received: (from jo@localhost)
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) id g6I7SES07329;
	Thu, 18 Jul 2002 09:28:14 +0200 (MEST)
From: Joerg Ott <jo@Informatik.Uni-Bremen.DE>
Message-Id: <200207180728.g6I7SES07329@nmh.informatik.uni-bremen.de>
Subject: Re: [MMUSIC] draft-even-mmusic-video-media-control-00.txt
To: roni.even@polycom.co.il (Even, Roni)
Date: Thu, 18 Jul 2002 09:28:14 +0200 (MEST)
Cc: mmusic@ietf.org
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1A6@ACCORD-NTSRV3> from "Even, Roni" at Jul 18, 2002 09:05:38 AM
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

> I think I would like to put focus on the subject
> 1. In order to support simple voice activated video switching conference
> with end-points that are not conference aware. This is the most basic video
> conference. We need to be able to have a clean video switch. This means that
> like when you change a channel in your cables, you may see a blank screen
> and then you will see the new channel without any artifact. 
> 2. The process includes a freeze n the receiver and new stream from the new
> sender.
> 3. I think we agree that the freeze is an attribute.

Just some random thought for curiosity:

Let me quickly express why I think you need this attribute (or find
out that you don't really need it).

- You use "freeze" to indicate that a receiver shall stop decoding.
- A receiver would (should) do this anyway if it stops receiving packets.
- As long as only valid data is received in the packets, that works fine.
- In a pure IP environment, no sender would packetize send rubbish.
- Can this be different in ISDN where just cannot easily send "no data"
  (expect for video fill patterns) and this, consequently, only
  be an issue for MCUs who need to switch from one source to the next
  and may not be able or willing to packetize only fully decodable
  video frame fragments (e.g. macroblocks, GOBs).
- if the MCU would do proper parsing and packetization of the media
  stream and forward only valid frames or blocks, would this be a non-issue?

Am I missing something here?

> 4. From the options I presented for the new streams there were two that are
> being discussed.
>  4.1 use the RTCP feedback - the current meaning of the RTCP message is an
> indication of a QOS problem.
>  4.2 Use a new SDP attribute. - the discussion was if that is a stream state
> change - I argued that to the receiver it is a change in the state of the
> stream he will receive
> 5. I prefer to use the attribute.
>    5.1. It makes the process use the same protocol layer as the freeze -
> both will be SDP based
>   5.2 it does not change the meaning of the RTCP indication.

As pointed out in a previous mail; what would be the state change in the
next round?  What would be the proper "negotiation" behavior in o/a?
(since both parties would need to agree on this)?

That's why I think it does not fit in SDP.

Joerg
> Roni Even
> 
> **********************************************
> Roni Even
> 
> Polycom Network Systems
> Tel: +972-3-9251200
> Mobile: +972-55-481099
> Fax: +972-3-9211571
> Email: roni.even@polycom.co.il
> 
> 
> _______________________________________________
> 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 Jul 18 10:12:35 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 KAA03082
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 10:12:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09629
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 10:13: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 KAA09555;
	Thu, 18 Jul 2002 10:10:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09524
	for <mmusic@optimus.ietf.org>; Thu, 18 Jul 2002 10:10:06 -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 KAA03021
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 10:09:06 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DTXXHZ>; Thu, 18 Jul 2002 17:09:30 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1AF@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: mmusic@ietf.org
Date: Thu, 18 Jul 2002 17:09:23 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
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

Hi,
The authors of the draft feel that the current situation with the new
picture request is not answering their requirements. The reason we brought
the issue to MMUSIC and not AVT was that we need a signalling solution for
the problem.
RTCP will not work for the following reasons
1. H.323 use signaling path and not RTCP. If we have an H.323 bridge and a
SIP participant will participate through a signalling GW then the H.323
bridge will send a message in the signalling path. The signalling GW will
not be able to forward the request since it is not handling the RTP/RTCP
stream. If we have a SIP conferencing bridge and an H.323 participant
through a signalling GW then the SIP server will send an RTCP message which
is not supported in H.323 EP.
2. We need a reliable channel for the request. RTCP is not a reliable
channel. I assume that with the direction SIP is going we will prefer to use
TCP for signalling in the video conferencing products.
3. About the change of state issue - my understanding of a change of state
is that if a change of state occurs then there may be another message which
will causes a change from the current state. What I am again claiming is
that if we have a typical stream that has only delta pictures (and no full
pictures). This state will stay until a request for change of state asking
for a full picture will arrive. Then a full picture will be sent and delta
pictures which reference the new picture will arrive in the stream. Again
this state remains until a request for a new picture/stream arrives and
again a new stream is started with a new full picture causing a new state of
the stream. It is common in video conferencing from encoder to send one full
picture and from then on just delta pictures until a request for a full
picture arrives

Thanks
Roni Even 

**********************************************
Roni Even

Polycom Network Systems
Tel: +972-3-9251200
Mobile: +972-55-481099
Fax: +972-3-9211571
Email: roni.even@polycom.co.il


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



From daemon@optimus.ietf.org  Thu Jul 18 10:43:12 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 KAA03686
	for <mmusic-archive@odin.ietf.org>; Thu, 18 Jul 2002 10:43:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11120
	for mmusic-archive@odin.ietf.org; Thu, 18 Jul 2002 10:44: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 KAA11060;
	Thu, 18 Jul 2002 10:42: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 KAA11029
	for <mmusic@optimus.ietf.org>; Thu, 18 Jul 2002 10:42:17 -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 KAA03649
	for <mmusic@ietf.org>; Thu, 18 Jul 2002 10:41:18 -0400 (EDT)
From: danutf@redlinecommunications.ro
Received: from localhost (danutf@localhost)
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with ESMTP id g6IEfFc10132;
	Thu, 18 Jul 2002 17:41:15 +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: Thu, 18 Jul 2002 17:41:15 +0300 (EEST)
To: <mmusic@ietf.org>
cc: <mjh@icir.org>, <van@packetdesign.com>, <csp@isi.edu>
Message-ID: <Pine.LNX.4.33.0207181709270.10034-100000@mail.redlinecommunications.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [MMUSIC] ABNF inconsistency in draft-ietf-sdp-new-10.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


Hello all,

In the latest SDP draft is presented an example for "r" fields
at page 16:
r=604800 3600 0 90000

Note that the first offset from the list is 0!

The following ABNF definitions are extracted from the same draft:
repeat-fields= "r=" repeat-interval SP typed-time 1*(SP typed-time)
typed-time= POS-DIGIT *DIGIT [fixed-len-time-unit]

So, the ABNF definition of 'typed-time' cannot match zeros, and
that makes your EXAMPLE INCORRECT.


I have also sent some comment on a redundancy regarding email-safe /
email and phone ABNF definition.
But nobody seemed to care about them...

Is this mailing-list still on?
Dan Firac,
Software Engineer,
Redline Communications,
Romania.
+40 723 260 623


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



From daemon@ns.ietf.org  Fri Jul 19 22:44: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 WAA23234
	for <mmusic-archive@odin.ietf.org>; Fri, 19 Jul 2002 22:44:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA16290
	for mmusic-archive@odin.ietf.org; Fri, 19 Jul 2002 22:45: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 WAA16183;
	Fri, 19 Jul 2002 22:41: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 WAA16152
	for <mmusic@ns.ietf.org>; Fri, 19 Jul 2002 22:41:02 -0400 (EDT)
Received: from radvpost.us.radvision.com ([12.44.63.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23181
	for <mmusic@ietf.org>; Fri, 19 Jul 2002 22:40:03 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2653.19)
	id <PC5BMLYM>; Fri, 19 Jul 2002 22:40:17 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD94945012DE524@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Fri, 19 Jul 2002 22:40:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
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

It is unfortunate that we couldn't find time during the MMUSIC meeting to
reasonably discuss the "Picture Update" topic face to face. That is in order
to be sure that we all understand the requested functionality and the
consequences of not having its standard definition ASAP.

I would like to reinforce the following points:

1. Without diving into scenarios, but based on videoconferencing EXPERIENCE
(including over IP), this is the ONLY video command that is absolutely MUST
and is WIDELY USED today in any video-related application (including the
simplest scenarios). It REQUIRES a coordinated (and desirably STANDARDIZED
in the IETF!) operation on both sides of the video stream. 

2. From an architectural point of view, any RTCP mechanism is not the right
answer for application layer commands. While applications use call signaling
and application media control for media stream establishment and
manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
dealing with congestion, etc. over IP in PARALLEL to the applications
running above. This allows for a loosely coupled architecture between the
application and the RTP/RTCP modules.

3. We also shouldn't forget the lack of the RTCP reliability being
(potentially) reflected on our applications' behavior.

4. Finally, the need for a real "application layer media control protocol"
has never been disputed. It takes time to define a new protocol. We are
looking for a reasonable (i.e. doable and decently working) interim solution
for the Picture Update Request. I don't think it is reasonable to expect
vendors to TWIST their existing (and, in this case, architecturally correct
:-) implementations in order to achieve this required functionality as an
interim patch in the RTCP!!!

As a side bar conversation, I cannot prevent myself from not commenting on
the "Change of State" topic. Where does the definition of the "state of
stream" exist? Is it the same for voice, video, etc.?
How about renaming the "Picture Update Request" into "Reset (Picture) State
Request"?

Orit Levin
Chief Architect
RADVISION Inc.
Tel:  +1.201.689.6330 


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



From daemon@optimus.ietf.org  Sun Jul 21 01:04: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 BAA22167
	for <mmusic-archive@odin.ietf.org>; Sun, 21 Jul 2002 01:04:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA17349
	for mmusic-archive@odin.ietf.org; Sun, 21 Jul 2002 01:05:56 -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 BAA16560;
	Sun, 21 Jul 2002 01:03: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 BAA16529
	for <mmusic@optimus.ietf.org>; Sun, 21 Jul 2002 01:03:29 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22136
	for <mmusic@ietf.org>; Sun, 21 Jul 2002 01:02:27 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.192])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g6L52wYH014675;
	Sun, 21 Jul 2002 01:02:58 -0400 (EDT)
Message-ID: <3D3A4080.40704@dynamicsoft.com>
Date: Sun, 21 Jul 2002 14:02:56 +0900
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: Orit Levin <orit@radvision.com>
CC: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft
References: <0D5BBF5D638DD4119E3400508BD94945012DE524@RADVPOST>
Content-Type: text/plain; charset=windows-1255; 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



Orit Levin wrote:

> 1. Without diving into scenarios, but based on videoconferencing
> EXPERIENCE
> (including over IP), this is the ONLY video command that is absolutely
> MUST
> and is WIDELY USED today in any video-related application (including the
> simplest scenarios). It REQUIRES a coordinated (and desirably
> STANDARDIZED
> in the IETF!) operation on both sides of the video stream. 

I don't think there is really dispute on that point.


> 
> 2. From an architectural point of view, any RTCP mechanism is not the
> right
> answer for application layer commands. While applications use call
> signaling
> and application media control for media stream establishment and
> manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
> dealing with congestion, etc. over IP in PARALLEL to the applications
> running above. This allows for a loosely coupled architecture between
> the
> application and the RTP/RTCP modules.

Well, it seems that it has already been done, since apparently an 
existing RFC uses RTCP for picture update. Its just codec specific at 
this point. While I don't think RTCP is ideal here, I don't find it 
architecturally incorrect.



> 4. Finally, the need for a real "application layer media control
> protocol"
> has never been disputed. It takes time to define a new protocol. We are
> looking for a reasonable (i.e. doable and decently working) interim
> solution
> for the Picture Update Request. I don't think it is reasonable to expect
> vendors to TWIST their existing (and, in this case, architecturally
> correct
> :-) implementations in order to achieve this required functionality as
> an
> interim patch in the RTCP!!!
> 
> As a side bar conversation, I cannot prevent myself from not commenting
> on
> the "Change of State" topic. Where does the definition of the "state of
> stream" exist? Is it the same for voice, video, etc.?
> How about renaming the "Picture Update Request" into "Reset (Picture)
> State
> Request"?

That changes nothing. In the offer/answer model, the SDP attributes are 
the current descriptions of the state of the stream - its encodings, its 
packetizations, etc. Furthermore, the attributes describe the local view 
of the streams. For example, if A sends an offer to B, the SDP in the 
offer describes A's view of the streams. What has been proposed is to 
add an SDP attribute that diverges from both assumptions. A "picture 
update request" attribute does not represent the state of the stream, 
since its not state - its a request. Furthermore, it does not describe 
the local view of the stream - it rather is an instruction for the 
recipient.

This kind of inconsistency can be troublesome in many ways. One way is 
in third party call control. Many 3pcc applications have the controller 
reusing the last SDP from a participant to generate an offer to a new 
participant that is to be brought in. If that last SDP was the result of 
a re-invite with this "picture update request", the controller will end 
up asking the new participant to generate a picture update, even though 
that is not what is intended. I fear that there are other complications 
that will arise. The SDP attribute proposal breaks several very 
fundamental assumptions in the O/A model.

-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  Sun Jul 21 20:27:57 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 UAA12461
	for <mmusic-archive@odin.ietf.org>; Sun, 21 Jul 2002 20:27:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA00625
	for mmusic-archive@odin.ietf.org; Sun, 21 Jul 2002 20:28:56 -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 UAA00579;
	Sun, 21 Jul 2002 20:27:35 -0400 (EDT)
Received: from purple.nge.isi.edu (dial167.east.isi.edu [65.114.169.167])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00545
	for <mmusic@ietf.org>; Sun, 21 Jul 2002 20:27:32 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6LD7DKM005945;
	Sun, 21 Jul 2002 09:07:13 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207211307.g6LD7DKM005945@purple.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Thu, 18 Jul 2002 17:09:23 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1AF@ACCORD-NTSRV3> 
Date: Sun, 21 Jul 2002 22:07:13 +0900
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

--> "Even, Roni" writes:
>Hi,
>The authors of the draft feel that the current situation with the new
>picture request is not answering their requirements. The reason we brought
>the issue to MMUSIC and not AVT was that we need a signalling solution for
>the problem.
>RTCP will not work for the following reasons
>1. H.323 use signaling path and not RTCP. If we have an H.323 bridge and a
>SIP participant will participate through a signalling GW then the H.323
>bridge will send a message in the signalling path. The signalling GW will
>not be able to forward the request since it is not handling the RTP/RTCP
>stream. If we have a SIP conferencing bridge and an H.323 participant
>through a signalling GW then the SIP server will send an RTCP message which
>is not supported in H.323 EP.
>2. We need a reliable channel for the request. RTCP is not a reliable
>channel. I assume that with the direction SIP is going we will prefer to use
>TCP for signalling in the video conferencing products.

I have difficulty understanding this second requirement: a reliable channel
would seem inappropriate, compared to a timely request that arrives before
the next full picture is naturally sent.

>3. About the change of state issue - my understanding of a change of state
>is that if a change of state occurs then there may be another message which
>will causes a change from the current state. What I am again claiming is
>that if we have a typical stream that has only delta pictures (and no full
>pictures). This state will stay until a request for change of state asking
>for a full picture will arrive. Then a full picture will be sent and delta
>pictures which reference the new picture will arrive in the stream. Again
>this state remains until a request for a new picture/stream arrives and
>again a new stream is started with a new full picture causing a new state of
>the stream. It is common in video conferencing from encoder to send one full
>picture and from then on just delta pictures until a request for a full
>picture arrives

Is this not very fragile if packet loss occurs?  Why would you not send a
full picture occasionally, avoiding the fragility and the requirement for
reliable signalling? 

Colin

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



From daemon@optimus.ietf.org  Sun Jul 21 20:30:21 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 UAA12539
	for <mmusic-archive@odin.ietf.org>; Sun, 21 Jul 2002 20:30:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA01211
	for mmusic-archive@odin.ietf.org; Sun, 21 Jul 2002 20:31: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 UAA00533;
	Sun, 21 Jul 2002 20:27:03 -0400 (EDT)
Received: from purple.nge.isi.edu (dial167.east.isi.edu [65.114.169.167])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00502
	for <mmusic@ietf.org>; Sun, 21 Jul 2002 20:27:00 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6LDIoKM006155;
	Sun, 21 Jul 2002 09:18:50 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207211318.g6LDIoKM006155@purple.nge.isi.edu>
To: danutf@redlinecommunications.ro
cc: mmusic@ietf.org, mjh@icir.org, van@packetdesign.com
In-Reply-To: Your message of "Thu, 18 Jul 2002 17:41:15 +0300."
             <Pine.LNX.4.33.0207181709270.10034-100000@mail.redlinecommunications.ro> 
Date: Sun, 21 Jul 2002 22:18:50 +0900
From: Colin Perkins <csp@isi.edu>
Subject: [MMUSIC] Re: ABNF inconsistency in draft-ietf-sdp-new-10.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

--> danutf@redlinecommunications.ro writes:
>
>Hello all,
>
>In the latest SDP draft is presented an example for "r" fields
>at page 16:
>r=604800 3600 0 90000
>
>Note that the first offset from the list is 0!
>
>The following ABNF definitions are extracted from the same draft:
>repeat-fields= "r=" repeat-interval SP typed-time 1*(SP typed-time)
>typed-time= POS-DIGIT *DIGIT [fixed-len-time-unit]
>
>So, the ABNF definition of 'typed-time' cannot match zeros, and
>that makes your EXAMPLE INCORRECT.

This was raised on the mailing list recently, and will be fixed in the next
version. 

>I have also sent some comment on a redundancy regarding email-safe /
>email and phone ABNF definition.
>But nobody seemed to care about them...

Sorry, didn't have time yet to read them yet. It's on my list of things to
do...

Colin

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



From daemon@optimus.ietf.org  Mon Jul 22 11:23: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 LAA07219
	for <mmusic-archive@odin.ietf.org>; Mon, 22 Jul 2002 11:23:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA24583
	for mmusic-archive@odin.ietf.org; Mon, 22 Jul 2002 11:24:53 -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 LAA24106;
	Mon, 22 Jul 2002 11:17:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24075
	for <mmusic@optimus.ietf.org>; Mon, 22 Jul 2002 11:17:08 -0400 (EDT)
Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06935
	for <mmusic@ietf.org>; Mon, 22 Jul 2002 11:16:01 -0400 (EDT)
Received: from host213-122-159-170.in-addr.btopenworld.com ([213.122.159.170] helo=tkw)
	by gadolinium.btinternet.com with smtp (Exim 3.22 #8)
	id 17Wevc-0002qA-00; Mon, 22 Jul 2002 16:16:53 +0100
Message-ID: <007001c23193$09ea51a0$0200000a@tkw>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Even, Roni" <roni.even@polycom.co.il>, "Colin Perkins" <csp@isi.edu>
Cc: <mmusic@ietf.org>
References: <200207211307.g6LD7DKM005945@purple.nge.isi.edu>
Subject: Re: [MMUSIC] video media control draft 
Date: Mon, 22 Jul 2002 16:12:30 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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
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

----- Original Message -----
From: "Colin Perkins" <csp@isi.edu>


> --> "Even, Roni" writes:
> >2. We need a reliable channel for the request. RTCP is not a reliable
> >channel. I assume that with the direction SIP is going we will prefer to
use
> >TCP for signalling in the video conferencing products.
>
> I have difficulty understanding this second requirement: a reliable
channel
> would seem inappropriate, compared to a timely request that arrives before
> the next full picture is naturally sent.

Assuming this discussion is still on the same page as I am on.... Its
important that a refresh is reliably signalled sometime after the switch is
made.  Timeliness would be nice, but reliability is more important.  Even a
couple of seconds delay would be better than no signal arriving.

> >3. About the change of state issue - my understanding of a change of
state
> >is that if a change of state occurs then there may be another message
which
> >will causes a change from the current state. What I am again claiming is
> >that if we have a typical stream that has only delta pictures (and no
full
> >pictures). This state will stay until a request for change of state
asking
> >for a full picture will arrive. Then a full picture will be sent and
delta
> >pictures which reference the new picture will arrive in the stream. Again
> >this state remains until a request for a new picture/stream arrives and
> >again a new stream is started with a new full picture causing a new state
of
> >the stream. It is common in video conferencing from encoder to send one
full
> >picture and from then on just delta pictures until a request for a full
> >picture arrives
>
> Is this not very fragile if packet loss occurs?  Why would you not send a
> full picture occasionally, avoiding the fragility and the requirement for
> reliable signalling?

Just in case people on this list are not video codec experts by first
calling (apologies to those that are),... we used to do cyclic
replenishment.  In other words, block 1 was done intra on the 1st frame and
all the rest were done inter, then block 2 was done intra on the 2nd frame
and so on.  This would clear up accumulated noise and transmission errors.
Full intras were sent only on request (or start up) as this involved a
significant increase in bandwidth, and typically involving using coarser
quantisers which meant a visible degradation in the picture.  These
startegies were admittedly for fixed rate ISDN and IP would be more tolerant
to data bursts when a full intra is sent, but even there you want to keep
this bursting to a minimum in case it causes congestion (possibly on your
access link) and packet loss results in more problems than is solves.


Pete.

=============================================
Pete Cordell
Tech-Know-Ware
pete@tech-know-ware.com
+44 1473 635863
=============================================




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



From daemon@optimus.ietf.org  Mon Jul 22 12:39:15 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 MAA13615
	for <mmusic-archive@odin.ietf.org>; Mon, 22 Jul 2002 12:39:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA26999
	for mmusic-archive@odin.ietf.org; Mon, 22 Jul 2002 12:40:16 -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 MAA21067;
	Mon, 22 Jul 2002 12:33:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20994
	for <mmusic@optimus.ietf.org>; Mon, 22 Jul 2002 12:32:57 -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 MAA12580
	for <mmusic@ietf.org>; Mon, 22 Jul 2002 12:31:53 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6MGW8h4001532;
	Mon, 22 Jul 2002 12:32:08 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207221632.g6MGW8h4001532@purple.nge.isi.edu>
To: "Pete Cordell" <pete@tech-know-ware.com>
cc: "Even, Roni" <roni.even@polycom.co.il>, mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Mon, 22 Jul 2002 16:12:30 BST."
             <007001c23193$09ea51a0$0200000a@tkw> 
Date: Mon, 22 Jul 2002 12:32:08 -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

--> "Pete Cordell" writes:
>----- Original Message -----
>From: "Colin Perkins" <csp@isi.edu>
>
>
>> --> "Even, Roni" writes:
>> >2. We need a reliable channel for the request. RTCP is not a reliable
>> >channel. I assume that with the direction SIP is going we will prefer to
>use
>> >TCP for signalling in the video conferencing products.
>>
>> I have difficulty understanding this second requirement: a reliable
>channel
>> would seem inappropriate, compared to a timely request that arrives before
>> the next full picture is naturally sent.
>
>Assuming this discussion is still on the same page as I am on.... Its
>important that a refresh is reliably signalled sometime after the switch is
>made.  Timeliness would be nice, but reliability is more important.  Even a
>couple of seconds delay would be better than no signal arriving.

Okay, but this doesn't imply sending it via SIP. You could just drop the
request into the next RTCP packet going out (either a regular packet, or
another early feedback packet).

>> >3. About the change of state issue - my understanding of a change of
>state
>> >is that if a change of state occurs then there may be another message
>which
>> >will causes a change from the current state. What I am again claiming is
>> >that if we have a typical stream that has only delta pictures (and no
>full
>> >pictures). This state will stay until a request for change of state
>asking
>> >for a full picture will arrive. Then a full picture will be sent and
>delta
>> >pictures which reference the new picture will arrive in the stream. Again
>> >this state remains until a request for a new picture/stream arrives and
>> >again a new stream is started with a new full picture causing a new state
>of
>> >the stream. It is common in video conferencing from encoder to send one
>full
>> >picture and from then on just delta pictures until a request for a full
>> >picture arrives
>>
>> Is this not very fragile if packet loss occurs?  Why would you not send a
>> full picture occasionally, avoiding the fragility and the requirement for
>> reliable signalling?
>
>Just in case people on this list are not video codec experts by first
>calling (apologies to those that are),... we used to do cyclic
>replenishment.  In other words, block 1 was done intra on the 1st frame and
>all the rest were done inter, then block 2 was done intra on the 2nd frame
>and so on.  This would clear up accumulated noise and transmission errors.
>Full intras were sent only on request (or start up) as this involved a
>significant increase in bandwidth, and typically involving using coarser
>quantisers which meant a visible degradation in the picture.  These
>startegies were admittedly for fixed rate ISDN and IP would be more tolerant
>to data bursts when a full intra is sent, but even there you want to keep
>this bursting to a minimum in case it causes congestion (possibly on your
>access link) and packet loss results in more problems than is solves.

Clearly, so. I'm surprised there's not a rolling cyclic replenishment
though, to recover from packet loss, which would also recover if the
full update was lost.

Colin

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



From daemon@optimus.ietf.org  Mon Jul 22 13:15:22 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 NAA18004
	for <mmusic-archive@odin.ietf.org>; Mon, 22 Jul 2002 13:15:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA24321
	for mmusic-archive@odin.ietf.org; Mon, 22 Jul 2002 13:16: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 NAA20581;
	Mon, 22 Jul 2002 13:10: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 NAA20515
	for <mmusic@optimus.ietf.org>; Mon, 22 Jul 2002 13:10:54 -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 NAA17397
	for <mmusic@ietf.org>; Mon, 22 Jul 2002 13:09:50 -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 g6MHAev25439;
	Mon, 22 Jul 2002 19:10:40 +0200 (MEST)
Message-ID: <3D3C3D04.CC30A69B@tzi.uni-bremen.de>
Date: Mon, 22 Jul 2002 19:12:36 +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: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft
References: <0D5BBF5D638DD4119E3400508BD94945012DE524@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

Roni and Orit,

let me make a quick basic points before we turn again to trying to
solve this problem:

A)  I very much and very well understand *what* you want to achieve
    and *why* you want to have this.  There is no point in re-iterating
    the same thing over and over again.

B)  I also very much appreciate your desire and your efforts to create
    a standardized solution (particularly, standardized in the IETF).

C)  That said, however, it does not seem too productive to argue
    "yes, we want a standardized solution" followed by "but only if
    it is the solution we have in mind."

Roni, Stephan, and myself sat together to discuss a number of possible
scenarios that could solve your problem, ruling out our current ideas
one by one with only RTCP remaining as senssible option.  In my opionion,
this is because

- either there is no other sensisble option using existing signaling
  protocols (and hence a new one would be needed -- which all of us 
  seem to agree is kind of the long-term perspective);

- or we just have not found it yet -- in which case I would like you to
  come up with ideas that fit the respective protocol's spirit rather
  that re-stating that you want it your way.

I also understand your need to implement interworking with H.323 and
H.320.  As we know, H.320 has a control protocol which is synchronized
with the media stream so that Fast-Infra-Request, Picture-Freeze, and
other commands made sense.  This coupling was lost in H.323 when the
media stream was decoupled from the control signaling.  As far as I
know this happened when the H.230/H.242/H.243 commands and indications
were simply copied into the H.245 spec without too much consideration
whether this approach was sufficient or particularly meaningful from
a semantics perspective.  

This was a clear "design" mistake -- why should we repeat this here?
We try to make proper use of the protocols that we have created and
we must not be the ones setting bad precedent here.  So, please let's
do it together, but also do it "right".

Roni pointed out the possible decoupling of focus ("MC") and media
processor in a mixed protocol MCU.  Well, this is surely a valid point
but I suspect those two communicate via something similar to MEGACO.
Why can't they communicate reception of a FIR or indicate that one
shall be send.  As a working group, we cannot accept to make your
system design a starting point for our protocol decisions.

BTW: Once we have enabled "just a single command", more will follow.
     Been there, seen that.

Finally, let we quickly address your points one by one:

> It is unfortunate that we couldn't find time during the MMUSIC meeting to
> reasonably discuss the "Picture Update" topic face to face. That is in order
> to be sure that we all understand the requested functionality and the
> consequences of not having its standard definition ASAP.

As WG co-chair I have to reject this: I think we did more than fair
job allocating time to this discussion.  Just because we did not come
to a resolution in twice the time was not because a lack of time but
because of apparent disagreement.  Rather than running around in circles
the next reasonable step was to go back to the list and come up with
further ideas and reasoning -- which we are now doing.  This is good.

> 1. Without diving into scenarios, but based on videoconferencing EXPERIENCE
> (including over IP), this is the ONLY video command that is absolutely MUST
> and is WIDELY USED today in any video-related application (including the
> simplest scenarios). It REQUIRES a coordinated (and desirably STANDARDIZED
> in the IETF!) operation on both sides of the video stream.

I accept that and, again, I appreciate your coming to the IETF to do this.

> 2. From an architectural point of view, any RTCP mechanism is not the right
> answer for application layer commands. While applications use call signaling
> and application media control for media stream establishment and
> manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
> dealing with congestion, etc. over IP in PARALLEL to the applications
> running above. This allows for a loosely coupled architecture between the
> application and the RTP/RTCP modules.

From an architectural point of view, what you want to do is neither
SIP nor RTCP.  Just because SIP fits your system design better does
not make it more applicable.  What we try to do here is a short-term
fix and given what we know right now, RTCP seems more appropriate.

> 3. We also shouldn't forget the lack of the RTCP reliability being
> (potentially) reflected on our applications' behavior.

As I had iterated in an email some time back and someone else stated
at the meeting: there is no such thing like reliability but only
probably of arrivel within a certain time bound.  I accept that this
short-time arrival is more probably with active retransmissions.
But again, we try to find a short-term fix here.

(BTW: You assume that signaling will be fast (and hence lossless to be
 on time but at the same time expect the media to be pretty much
 unreliable -- this does not go together very well.)

> 4. Finally, the need for a real "application layer media control protocol"
> has never been disputed. It takes time to define a new protocol. We are

We are all in violent agreement on this.

> looking for a reasonable (i.e. doable and decently working) interim solution
> for the Picture Update Request. I don't think it is reasonable to expect
> vendors to TWIST their existing (and, in this case, architecturally correct
> :-) implementations in order to achieve this required functionality as an
> interim patch in the RTCP!!!

But you want to patch SIP/SDP in an architecturally incorrect way?
Let's not continue this religious debate here but try a more productive
approach (see further below).

> As a side bar conversation, I cannot prevent myself from not commenting on
> the "Change of State" topic. Where does the definition of the "state of
> stream" exist? Is it the same for voice, video, etc.?
> How about renaming the "Picture Update Request" into "Reset (Picture) State
> Request"?

A quick and simple answer:
State is something you NEGOTIATE with offer/answer.  You DO NOT NEGOTIATE
a picture update!  Or did you want to define a mechanism for the answerer
to reject this, fall back to a different state, etc.


Finally, I would like to close this controversy here and ask all of
us to get to a productive approach.

In current thinking -- and I feel that this reflects the rough consensus
in the group -- SDP is just a NO GO!  I am only with you for SIP if we
find a proper use of a signaling protocol.

This leaves us with two alternatives: RTCP and some other mechanism
in SIP (or RTSP but I think this is really too far away).

I would like to you to describe a few pices of the intended
functionality first.  For this, let us assume the following setting:

    A --------- MCU --------- B
                    \_________C

B and C speak alternatingly, A sees the respective speaker.

B speaks, then stops.  C starts speaking.  The voice-activity
detection decides to switch to C.  What is the threshold here?
How frequently may this happen (every second, every 10 seconds, ...?)
This parameter is important as the time scales may have an influence
on the design decisions here.

(Is there, assuming the typical head-and-shoulders image, a 
graph indicating the maximum switch frequency for a given bandwidth?)

You said that you need a picture freeze command.  Please briefly
re-state why -- why will A at all receive rubbish in RTP payloads
instead of meaningful content?  (I am still just curious.)

When we switch from B to C, the MCU sends C an FIR.  What are the
"perceived" delay contraints between the voice activity detection
and the FIR sent to C?  How is, particularly in a distributed MCU,
the process between switching the media stream and sending out
the FIR synchronized.  What comes first?  What kind of media is
sent to A in the interim?

I think I'll have more questions for you but I'd like to start
with these to kind of scope the design space a bit to come up with
a quick and efficient solution for you?

Joerg

PS: Please note that, in principle, I am on vacation and have only
    infrequent Internet connectivity at most.  So replies may take
    a while.

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



From daemon@ns.ietf.org  Mon Jul 22 18:56:27 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 SAA18563
	for <mmusic-archive@odin.ietf.org>; Mon, 22 Jul 2002 18:56:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA21899
	for mmusic-archive@odin.ietf.org; Mon, 22 Jul 2002 18:57:27 -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 SAA20395;
	Mon, 22 Jul 2002 18:54:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA20346
	for <mmusic@ns.ietf.org>; Mon, 22 Jul 2002 18:54: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 SAA18311
	for <mmusic@ietf.org>; Mon, 22 Jul 2002 18:53:24 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2653.19)
	id <PC5BMNHS>; Mon, 22 Jul 2002 18:53:38 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD94945018855C1@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: "Jonathan Rosenberg (E-mail)" <jdrosen@dynamicsoft.com>,
        "'Joerg Ott'"
	 <jo@tzi.uni-bremen.de>
Cc: mmusic@ietf.org, "Roni Even (E-mail)" <roni.even@polycom.co.il>
Subject: RE: [MMUSIC] video media control draft
Date: Mon, 22 Jul 2002 18:53:37 -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

	I would summarize the situation from the standards' perspective:
1. Violently Agreed: Both RTCP (as is + "feedback") and SDP+Offer/Answer are
interim patches for the purpose.
2. Disagreed: Which one is more "architecturally incorrect".
3. Agreed: Definition of a new protocol/approach requires time. Hopefully,
we will start work on it.
	I would like to summarize the situation from the multimedia
implementers perspective:
1. Although the "RTCP based FIR" has been defined since 1996 (as per RFC
2032), it neither hasn't been used for application purposes nor hasn't been
expanded beyond H.261. There are good reasons for this...
2. On the contrary, we know about at least 6 (!) major multimedia vendors
that have been (almost desperately) seeking for an agreed doable solution
since yesterday and, in the meanwhile, are working on proprietary
extensions.
3. I would like to ask (additional) interested vendors that are looking into
this problem to contact me (or my co-authors) directly in order to compile
our preferences and agree on the intermediate solution.

Best Regards,
Orit Levin
Chief Architect
RADVISION Inc.
Tel:  +1.201.689.6330
	Side Bar "SDP Stream State" topic:
I can see the difference in "a data model" between sending a request
implicitly (i.e. using a future state description) and sending a request
explicitly (i.e. using an attribute). I am afraid, I disagree about the
difference in consequences in both cases.
For example, in the "put-on-hold" case, the situation is very similar to the
"reset-state-request" with all the potential fears expressed in the previous
Jonathan's mail.

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



From daemon@optimus.ietf.org  Tue Jul 23 04:02:32 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 EAA02893
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 04:02:32 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA21920
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 04:03: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 DAA20447;
	Tue, 23 Jul 2002 03:50: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 DAA20417
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 03:50:18 -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 DAA02589
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 03:49:15 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DT5PZR>; Tue, 23 Jul 2002 10:49:40 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1B7@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        Orit Levin
	 <orit@radvision.com>
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Tue, 23 Jul 2002 10:49:39 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
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,
My comment on this item are below

>From an architectural point of view, any RTCP mechanism is not the
> right
> answer for application layer commands. While applications use call
> signaling
> and application media control for media stream establishment and
> manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
> dealing with congestion, etc. over IP in PARALLEL to the applications
> running above. This allows for a loosely coupled architecture between
> the
> application and the RTP/RTCP modules.

Well, it seems that it has already been done, since apparently an 
existing RFC uses RTCP for picture update. Its just codec specific at 
this point. While I don't think RTCP is ideal here, I don't find it 
architecturally incorrect.

Roni Even: 
This text is from H.261 that was mentioned in the MMUSIC discussion, as can
be seen it says to use the signaling protocol and not the RTP/RTCP for that

4.3 Multipoint considerations
The following facilities are provided to support switched multipoint
operation.
4.3.1	Freeze picture request
Causes the decoder to freeze its displayed picture until a freeze picture
release signal is received or a timeout period of at least six seconds has
expired. The transmission of this signal is via external means (for example
by Recommendation H.221).
4.3.2	Fast update request
Causes the encoder to encode its next picture in INTRA mode with coding
parameters such as to avoid buffer overflow. The transmission method for
this signal is via external means (for example by Recommendation H.221).

As for the RTCP feedback, the AVT group did not agree on requests but on an
indication that will still allow the encoder to ignore the message. As can
be seen from 4.3.2 above the request for full picture will not cause
congestion even in H.320 sine the encoder may reduce quality of the full
picture.

Thanks
Roni Even

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



From daemon@optimus.ietf.org  Tue Jul 23 04:03:32 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 EAA02955
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 04:03:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA21952
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 04:04: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 EAA21409;
	Tue, 23 Jul 2002 04:01: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 EAA21377
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 04:01:20 -0400 (EDT)
Received: from parsmtp1.rd.francetelecom.com (parsmtp1.rd.francetelecom.com [194.167.105.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02789
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 04:00:18 -0400 (EDT)
Received: from parmhs3.rd.francetelecom.fr ([10.193.117.62]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 23 Jul 2002 10:01:18 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: [MMUSIC] video media control draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Tue, 23 Jul 2002 10:01:18 +0200
Message-ID: <A2200E9A0E413B4C99FB7384D740878124E2EF@parmhs3.rd.francetelecom.fr>
Thread-Topic: [MMUSIC] video media control draft
Thread-Index: AcIxo1WYbTTqEJ2UEda32AAIxyRtkQAb75ig
From: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
To: "Joerg Ott" <jo@tzi.uni-bremen.de>, "Orit Levin" <orit@radvision.com>
Cc: <mmusic@ietf.org>
X-OriginalArrivalTime: 23 Jul 2002 08:01:18.0804 (UTC) FILETIME=[205B8940:01C2321F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA21378
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

All,

We am working on UA with Video (www.econf-communication.com), we totally
agree with the requirements as expressed by the "video media control
draft". 

We already have support for H323 protocol and can't actually release our
product because of the lack of support for video control in SIP/SDP (we
do not want to loose some existing features available for the end-user).
We are very concerned by  the quality of the conference once it has been
initiated.

There is a lack of expressivness in the actual SDP, a UA can not specify
the video format etc...  There is also a lack of control of media in
SIP/SDP(offer/answer model).

Regarding video, these two points have been discussed in the draft
called "draft-koskelainen-sdp263-02.txt". (found in the input queue for
SDPng).

We would like to revive this draft. It effectively allows a UA to
express video capability in a good way.

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.
"

So what is still needed from our point of view is a standard way to
control media.

We have ideas on this last issue and will be pleased to contribute to
this effort,

Best Regards,

----------------------------------------------------
Patrick Monfort
R&D Engineer
France Telcom R&D DMI/SGV
38-40 Av du Leclerc
92794 Issy Les Moulineaux - France
Tel: +33 1.45.29.43.95
Fax: +33 1.45.29.52.94
---------------------------------------------------



-----Original Message-----
From: Joerg Ott [mailto:jo@tzi.uni-bremen.de]
Sent: lundi 22 juillet 2002 19:13
To: Orit Levin
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft


Roni and Orit,

let me make a quick basic points before we turn again to trying to
solve this problem:

A)  I very much and very well understand *what* you want to achieve
    and *why* you want to have this.  There is no point in re-iterating
    the same thing over and over again.

B)  I also very much appreciate your desire and your efforts to create
    a standardized solution (particularly, standardized in the IETF).

C)  That said, however, it does not seem too productive to argue
    "yes, we want a standardized solution" followed by "but only if
    it is the solution we have in mind."

Roni, Stephan, and myself sat together to discuss a number of possible
scenarios that could solve your problem, ruling out our current ideas
one by one with only RTCP remaining as senssible option.  In my
opionion,
this is because

- either there is no other sensisble option using existing signaling
  protocols (and hence a new one would be needed -- which all of us 
  seem to agree is kind of the long-term perspective);

- or we just have not found it yet -- in which case I would like you to
  come up with ideas that fit the respective protocol's spirit rather
  that re-stating that you want it your way.

I also understand your need to implement interworking with H.323 and
H.320.  As we know, H.320 has a control protocol which is synchronized
with the media stream so that Fast-Infra-Request, Picture-Freeze, and
other commands made sense.  This coupling was lost in H.323 when the
media stream was decoupled from the control signaling.  As far as I
know this happened when the H.230/H.242/H.243 commands and indications
were simply copied into the H.245 spec without too much consideration
whether this approach was sufficient or particularly meaningful from
a semantics perspective.  

This was a clear "design" mistake -- why should we repeat this here?
We try to make proper use of the protocols that we have created and
we must not be the ones setting bad precedent here.  So, please let's
do it together, but also do it "right".

Roni pointed out the possible decoupling of focus ("MC") and media
processor in a mixed protocol MCU.  Well, this is surely a valid point
but I suspect those two communicate via something similar to MEGACO.
Why can't they communicate reception of a FIR or indicate that one
shall be send.  As a working group, we cannot accept to make your
system design a starting point for our protocol decisions.

BTW: Once we have enabled "just a single command", more will follow.
     Been there, seen that.

Finally, let we quickly address your points one by one:

> It is unfortunate that we couldn't find time during the MMUSIC meeting
to
> reasonably discuss the "Picture Update" topic face to face. That is in
order
> to be sure that we all understand the requested functionality and the
> consequences of not having its standard definition ASAP.

As WG co-chair I have to reject this: I think we did more than fair
job allocating time to this discussion.  Just because we did not come
to a resolution in twice the time was not because a lack of time but
because of apparent disagreement.  Rather than running around in circles
the next reasonable step was to go back to the list and come up with
further ideas and reasoning -- which we are now doing.  This is good.

> 1. Without diving into scenarios, but based on videoconferencing
EXPERIENCE
> (including over IP), this is the ONLY video command that is absolutely
MUST
> and is WIDELY USED today in any video-related application (including
the
> simplest scenarios). It REQUIRES a coordinated (and desirably
STANDARDIZED
> in the IETF!) operation on both sides of the video stream.

I accept that and, again, I appreciate your coming to the IETF to do
this.

> 2. From an architectural point of view, any RTCP mechanism is not the
right
> answer for application layer commands. While applications use call
signaling
> and application media control for media stream establishment and
> manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
> dealing with congestion, etc. over IP in PARALLEL to the applications
> running above. This allows for a loosely coupled architecture between
the
> application and the RTP/RTCP modules.

From an architectural point of view, what you want to do is neither
SIP nor RTCP.  Just because SIP fits your system design better does
not make it more applicable.  What we try to do here is a short-term
fix and given what we know right now, RTCP seems more appropriate.

> 3. We also shouldn't forget the lack of the RTCP reliability being
> (potentially) reflected on our applications' behavior.

As I had iterated in an email some time back and someone else stated
at the meeting: there is no such thing like reliability but only
probably of arrivel within a certain time bound.  I accept that this
short-time arrival is more probably with active retransmissions.
But again, we try to find a short-term fix here.

(BTW: You assume that signaling will be fast (and hence lossless to be
 on time but at the same time expect the media to be pretty much
 unreliable -- this does not go together very well.)

> 4. Finally, the need for a real "application layer media control
protocol"
> has never been disputed. It takes time to define a new protocol. We
are

We are all in violent agreement on this.

> looking for a reasonable (i.e. doable and decently working) interim
solution
> for the Picture Update Request. I don't think it is reasonable to
expect
> vendors to TWIST their existing (and, in this case, architecturally
correct
> :-) implementations in order to achieve this required functionality as
an
> interim patch in the RTCP!!!

But you want to patch SIP/SDP in an architecturally incorrect way?
Let's not continue this religious debate here but try a more productive
approach (see further below).

> As a side bar conversation, I cannot prevent myself from not
commenting on
> the "Change of State" topic. Where does the definition of the "state
of
> stream" exist? Is it the same for voice, video, etc.?
> How about renaming the "Picture Update Request" into "Reset (Picture)
State
> Request"?

A quick and simple answer:
State is something you NEGOTIATE with offer/answer.  You DO NOT
NEGOTIATE
a picture update!  Or did you want to define a mechanism for the
answerer
to reject this, fall back to a different state, etc.


Finally, I would like to close this controversy here and ask all of
us to get to a productive approach.

In current thinking -- and I feel that this reflects the rough consensus
in the group -- SDP is just a NO GO!  I am only with you for SIP if we
find a proper use of a signaling protocol.

This leaves us with two alternatives: RTCP and some other mechanism
in SIP (or RTSP but I think this is really too far away).

I would like to you to describe a few pices of the intended
functionality first.  For this, let us assume the following setting:

    A --------- MCU --------- B
                    \_________C

B and C speak alternatingly, A sees the respective speaker.

B speaks, then stops.  C starts speaking.  The voice-activity
detection decides to switch to C.  What is the threshold here?
How frequently may this happen (every second, every 10 seconds, ...?)
This parameter is important as the time scales may have an influence
on the design decisions here.

(Is there, assuming the typical head-and-shoulders image, a 
graph indicating the maximum switch frequency for a given bandwidth?)

You said that you need a picture freeze command.  Please briefly
re-state why -- why will A at all receive rubbish in RTP payloads
instead of meaningful content?  (I am still just curious.)

When we switch from B to C, the MCU sends C an FIR.  What are the
"perceived" delay contraints between the voice activity detection
and the FIR sent to C?  How is, particularly in a distributed MCU,
the process between switching the media stream and sending out
the FIR synchronized.  What comes first?  What kind of media is
sent to A in the interim?

I think I'll have more questions for you but I'd like to start
with these to kind of scope the design space a bit to come up with
a quick and efficient solution for you?

Joerg

PS: Please note that, in principle, I am on vacation and have only
    infrequent Internet connectivity at most.  So replies may take
    a while.

_______________________________________________
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 Jul 23 07:41: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 HAA06705
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 07:41:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA03077
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 07:42: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 HAA02914;
	Tue, 23 Jul 2002 07:36:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA02883
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 07:36:45 -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 HAA06524
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 07:35:40 -0400 (EDT)
From: danutf@redlinecommunications.ro
Received: from localhost (danutf@localhost)
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with ESMTP id g6NBaNM30725;
	Tue, 23 Jul 2002 14:36:23 +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: Tue, 23 Jul 2002 14:36:22 +0300 (EEST)
To: <mmusic@ietf.org>
cc: <csp@isi.edu>
Message-ID: <Pine.LNX.4.33.0207231419310.30591-100000@mail.redlinecommunications.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [MMUSIC] Another ABNF inconsistency in draft-ietf-sdp-new-10.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


Hello all,

Sorry for beeing insistent about this matter. But as I couldn't find
any feedback on the list regarding SDP ABNF since the lastest draft
is on, I conclude that the errors have propagated from one draft to
another(which is not a very good thing). So, I think it is better
to remind them even if they might be known.

Small one this time:
connection-field= ["c=" nettype ....]
media-descriptions= *(media field
                      information field
                      *connection-field
                      ....)

connection-field is already an optional field by its definition.
That makes redundant the "*" before the connection-field in the
media_descriptions definition.


Best regards,
Dan Firac,
Software Engineer,
Redline Communications,
Romania.
+40 723 260 623



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



From daemon@optimus.ietf.org  Tue Jul 23 08:37: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 IAA08639
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 08:37:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA06638
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 08:38:16 -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 IAA06380;
	Tue, 23 Jul 2002 08:33: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 IAA06311
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 08:33:38 -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 IAA08439
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 08:32:34 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DT5QW5>; Tue, 23 Jul 2002 15:33:00 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Orit Levin <orit@radvision.com>
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft
Date: Tue, 23 Jul 2002 15:33:00 +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,

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.
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.
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.



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.

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.

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. 

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

Regards
Roni Even



> 

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



From daemon@optimus.ietf.org  Tue Jul 23 10:59:10 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 KAA15702
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 10:59:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15883
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 11:00:10 -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 KAA15145;
	Tue, 23 Jul 2002 10:50:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15114
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 10:50:08 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14887
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 10:49:07 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g6NEnad05979
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 10:49:36 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <P3R3DSHC>; Tue, 23 Jul 2002 10:49:32 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0476FC62@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: mmusic@ietf.org
Cc: "Graeme Currie" <graeme.currie@nortelnetworks.com>,
        "Debbie Ng" <debng@nortelnetworks.com>
Date: Tue, 23 Jul 2002 10:49:31 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [MMUSIC] Need input on SDP "multiple ptime" parameter proposal
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

Mmusic experts,

I am hoping you can provide opinions on a proposed SDP alteration that is
being considered by PacketCable, but I think is of use to both SIP and
MEGACO.

MEGACO and SIP (as well as MGCP/NCS which is used by PacketCable) use the
offer/answer model with SDP for achieving negotiation while we all wait for
SDPng.  PacketCable has discovered that while multiple codecs are often
specified in one m= line, only one ptime can be specified across all those
codecs.  The offshoot of this is that individual packetization rates for
each codec cannot be specified (without going through some gyrations which
will make the SDP grow significantly, and which draws a question about
alternatives versus simultaneous transmission that isn't easily answered).
This limitation then removes the possibility of a media gateway controller
controlling bandwidth allocations during the negotiation process between two
media gateways.  This control has turned out to be very important for QoS
reservations.

A solution that has been proposed is a new SDP "multiple ptime" parameter
(a=mptime) that will take a list of packetization rates seperated by
semicolons; one entry for each encoding algorithm in the associated m= line.
Those algorithms to which packetization rate doesn't apply (like 96 -
telephone event) will have a dash for the appropriate entry.

I have read in the charter that most items of this nature will be deferred
to SDPng.  However, we have a real opportunity here to prevent the protocols
that use SDP for negotiation from diverging with each other and becoming
non-interoperable by defining their own proprietary extensions to SDP.  I
believe that this addition would fall within the spirit of the charter, as
this extension is within the framework of SDP.

What are your opinions of this proposal?  My plan is to issue an I-D for
eventual promotion to Informational RFC status, and then to push in the
negotiating protocols for utilization of the new parameter.  However, if the
working group is dead-set against such an addition, then I will not bother,
and I'll seek other methods of keeping the negotiating protocols from
deviating from each other.

Thanks for your consideration.

Kevin
--
Kevin J. Boyle II
Nortel Networks
+1 919 991 2690

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



From daemon@optimus.ietf.org  Tue Jul 23 13:45: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 NAA25955
	for <mmusic-archive@odin.ietf.org>; Tue, 23 Jul 2002 13:45:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02117
	for mmusic-archive@odin.ietf.org; Tue, 23 Jul 2002 13:46:14 -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 NAA01915;
	Tue, 23 Jul 2002 13:41: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 NAA01882
	for <mmusic@optimus.ietf.org>; Tue, 23 Jul 2002 13:41:08 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25719
	for <mmusic@ietf.org>; Tue, 23 Jul 2002 13:40:06 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA17785;
	Tue, 23 Jul 2002 13:39:52 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA02461;
	Tue, 23 Jul 2002 13:39:53 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W98970Y>; Tue, 23 Jul 2002 13:39:52 -0400
Message-ID: <313680C9A886D511A06000204840E1CF030B56D4@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Kevin Boyle'" <kboyle@nortelnetworks.com>, mmusic@ietf.org
Cc: Graeme Currie <graeme.currie@nortelnetworks.com>,
        Debbie Ng
	 <debng@nortelnetworks.com>
Subject: RE: [MMUSIC] Need input on SDP "multiple ptime" parameter proposa
	l
Date: Tue, 23 Jul 2002 13:39:52 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

fid is your friend.

Brian

> -----Original Message-----
> From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
> Sent: Tuesday, July 23, 2002 10:50 AM
> To: mmusic@ietf.org
> Cc: Graeme Currie; Debbie Ng
> Subject: [MMUSIC] Need input on SDP "multiple ptime" 
> parameter proposal
> 
> 
> Mmusic experts,
> 
> I am hoping you can provide opinions on a proposed SDP 
> alteration that is
> being considered by PacketCable, but I think is of use to both SIP and
> MEGACO.
> 
> MEGACO and SIP (as well as MGCP/NCS which is used by 
> PacketCable) use the
> offer/answer model with SDP for achieving negotiation while 
> we all wait for
> SDPng.  PacketCable has discovered that while multiple codecs 
> are often
> specified in one m= line, only one ptime can be specified 
> across all those
> codecs.  The offshoot of this is that individual 
> packetization rates for
> each codec cannot be specified (without going through some 
> gyrations which
> will make the SDP grow significantly, and which draws a question about
> alternatives versus simultaneous transmission that isn't 
> easily answered).
> This limitation then removes the possibility of a media 
> gateway controller
> controlling bandwidth allocations during the negotiation 
> process between two
> media gateways.  This control has turned out to be very 
> important for QoS
> reservations.
> 
> A solution that has been proposed is a new SDP "multiple 
> ptime" parameter
> (a=mptime) that will take a list of packetization rates seperated by
> semicolons; one entry for each encoding algorithm in the 
> associated m= line.
> Those algorithms to which packetization rate doesn't apply (like 96 -
> telephone event) will have a dash for the appropriate entry.
> 
> I have read in the charter that most items of this nature 
> will be deferred
> to SDPng.  However, we have a real opportunity here to 
> prevent the protocols
> that use SDP for negotiation from diverging with each other 
> and becoming
> non-interoperable by defining their own proprietary 
> extensions to SDP.  I
> believe that this addition would fall within the spirit of 
> the charter, as
> this extension is within the framework of SDP.
> 
> What are your opinions of this proposal?  My plan is to issue 
> an I-D for
> eventual promotion to Informational RFC status, and then to 
> push in the
> negotiating protocols for utilization of the new parameter.  
> However, if the
> working group is dead-set against such an addition, then I 
> will not bother,
> and I'll seek other methods of keeping the negotiating protocols from
> deviating from each other.
> 
> Thanks for your consideration.
> 
> Kevin
> --
> Kevin J. Boyle II
> Nortel Networks
> +1 919 991 2690
> 
> _______________________________________________
> 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 Jul 24 16:18:15 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 QAA01008
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 16:18:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA22477
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 16:19: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 QAA22305;
	Wed, 24 Jul 2002 16:16:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22276
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 16:16:25 -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 QAA00808
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 16:15:20 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OKG7a30630;
	Wed, 24 Jul 2002 16:16:08 -0400
Message-Id: <200207242016.g6OKG7a30630@chiron.nge.isi.edu>
To: danutf@redlinecommunications.ro
cc: mmusic@ietf.org
In-Reply-To: Your message of "Tue, 23 Jul 2002 14:36:22 +0300."
             <Pine.LNX.4.33.0207231419310.30591-100000@mail.redlinecommunications.ro> 
Date: Wed, 24 Jul 2002 16:16:07 -0400
From: Colin Perkins <csp@isi.edu>
Subject: [MMUSIC] Re: Another ABNF inconsistency in draft-ietf-sdp-new-10.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

--> danutf@redlinecommunications.ro writes:
>
>Hello all,
>
>Sorry for beeing insistent about this matter. But as I couldn't find
>any feedback on the list regarding SDP ABNF since the lastest draft
>is on, I conclude that the errors have propagated from one draft to
>another(which is not a very good thing). So, I think it is better
>to remind them even if they might be known.

Thanks for the careful reading, these fixes are important.

>Small one this time:
>connection-field= ["c=" nettype ....]
>media-descriptions= *(media field
>                      information field
>                      *connection-field
>                      ....)
>
>connection-field is already an optional field by its definition.
>That makes redundant the "*" before the connection-field in the
>media_descriptions definition.

Agreed. Fixed.

Colin

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



From daemon@optimus.ietf.org  Wed Jul 24 16:38: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 QAA01939
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 16:38:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23977
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 16:40: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 QAA23577;
	Wed, 24 Jul 2002 16:34: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 QAA23547
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 16:34:24 -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 QAA01755
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 16:33:18 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OKYFW30741;
	Wed, 24 Jul 2002 16:34:17 -0400
Message-Id: <200207242034.g6OKYFW30741@chiron.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        Orit Levin <orit@radvision.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Tue, 23 Jul 2002 10:49:39 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1B7@ACCORD-NTSRV3> 
Date: Wed, 24 Jul 2002 16:34:15 -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

--> "Even, Roni" writes:
>Hi,
>My comment on this item are below
>
>>From an architectural point of view, any RTCP mechanism is not the
>> right
>> answer for application layer commands. While applications use call
>> signaling
>> and application media control for media stream establishment and
>> manipulation, RTP/RTCP (with the addition of the "RTCP feedback") are
>> dealing with congestion, etc. over IP in PARALLEL to the applications
>> running above. This allows for a loosely coupled architecture between
>> the
>> application and the RTP/RTCP modules.
>
>Well, it seems that it has already been done, since apparently an 
>existing RFC uses RTCP for picture update. Its just codec specific at 
>this point. While I don't think RTCP is ideal here, I don't find it 
>architecturally incorrect.
>
>Roni Even: 
>This text is from H.261 that was mentioned in the MMUSIC discussion, as can
>be seen it says to use the signaling protocol and not the RTP/RTCP for that

This doesn't seem to be a productive argument, since you could argue that
"external means (for example by Recommendation H.221)" requires that a
signalling protocol is used, and I could argue that RTCP is a suitable
"external means" since it's external to H.261. 

>4.3 Multipoint considerations
>The following facilities are provided to support switched multipoint
>operation.
>4.3.1	Freeze picture request
>Causes the decoder to freeze its displayed picture until a freeze picture
>release signal is received or a timeout period of at least six seconds has
>expired. The transmission of this signal is via external means (for example
>by Recommendation H.221).
>4.3.2	Fast update request
>Causes the encoder to encode its next picture in INTRA mode with coding
>parameters such as to avoid buffer overflow. The transmission method for
>this signal is via external means (for example by Recommendation H.221).
>
>As for the RTCP feedback, the AVT group did not agree on requests but on an
>indication that will still allow the encoder to ignore the message. As can
>be seen from 4.3.2 above the request for full picture will not cause
>congestion even in H.320 sine the encoder may reduce quality of the full
>picture.

This is the core point of disagreement, I believe. I would argue that, no
matter how the fast update request message is transmitted, the encoder MUST
be able to ignore the request (because, for example, there may be IP level
congestion). The fact that the encoder can reduce quality so that the bit-
rate does not increase due to the full intra picture is irrelevent, since
it is possible that the network will have insufficient capacity for that
rate too.

Colin

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



From daemon@optimus.ietf.org  Wed Jul 24 16:39: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 QAA01972
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 16:39:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA24061
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 16:40: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 QAA23877;
	Wed, 24 Jul 2002 16:38: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 QAA23843
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 16:38:21 -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 QAA01872
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 16:37:16 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OKcEY30766;
	Wed, 24 Jul 2002 16:38:15 -0400
Message-Id: <200207242038.g6OKcEY30766@chiron.nge.isi.edu>
To: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
cc: "Joerg Ott" <jo@tzi.uni-bremen.de>, "Orit Levin" <orit@radvision.com>,
        mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Tue, 23 Jul 2002 10:01:18 +0200."
             <A2200E9A0E413B4C99FB7384D740878124E2EF@parmhs3.rd.francetelecom.fr> 
Date: Wed, 24 Jul 2002 16:38:14 -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

--> "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  Wed Jul 24 16: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 QAA02203
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 16:47:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA24475
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 16:48:25 -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 QAA24327;
	Wed, 24 Jul 2002 16: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 QAA24297
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 16:46:29 -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 QAA02145
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 16:45:24 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OKkNq30786;
	Wed, 24 Jul 2002 16:46:23 -0400
Message-Id: <200207242046.g6OKkNq30786@chiron.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Orit Levin <orit@radvision.com>,
        mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Tue, 23 Jul 2002 15:33:00 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1BA@ACCORD-NTSRV3> 
Date: Wed, 24 Jul 2002 16:46:23 -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

--> "Even, Roni" writes:
>Joerg,
>
>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.

In this case, the mixer is broken. It should change the SSRC on the
outgoing packets (or change the CSRC, depending if it is implemented as an
RTP translator or mixer) which will inform the decoder that a new source is
active, and prevent it using the delta pictures on data from a previous
source.

>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.

The source switch should always be accompanied by a change in either SSRC
or CSRC, so the receiver will always know it has occured. This is the
reason RTP mixers include CSRC information, and why RTP translators
preserve SSRC information.

>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.

Again, since the pictures will be identified by CSRC in the mixed RTP
packet, the decoder can perform all these functions without the use of 
freeze requests.

>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.
>
>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.
>
>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 cannot agree on MUST if the command is passed by the signalling channel
either: an encoder running over IP has to be aware of congestion control.

Colin

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



From daemon@optimus.ietf.org  Wed Jul 24 17:26: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 RAA03106
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 17:26:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA26799
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 17:27: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 RAA26583;
	Wed, 24 Jul 2002 17:22:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26552
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 17:22:50 -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 RAA02980
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 17:21:45 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OLMhu31095;
	Wed, 24 Jul 2002 17:22:43 -0400
Message-Id: <200207242122.g6OLMhu31095@chiron.nge.isi.edu>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>
cc: mmusic@ietf.org, "Graeme Currie" <graeme.currie@nortelnetworks.com>,
        "Debbie Ng" <debng@nortelnetworks.com>
Subject: Re: [MMUSIC] Need input on SDP "multiple ptime" parameter proposal 
In-Reply-To: Your message of "Tue, 23 Jul 2002 10:49:31 EDT."
             <ABA227A15B80D511BD1A00508BF93A1C0476FC62@zrtpd0jq.us.nortel.com> 
Date: Wed, 24 Jul 2002 17:22:43 -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

--> "Kevin Boyle" writes:
>Mmusic experts,
>
>I am hoping you can provide opinions on a proposed SDP alteration that is
>being considered by PacketCable, but I think is of use to both SIP and
>MEGACO.
>
>MEGACO and SIP (as well as MGCP/NCS which is used by PacketCable) use the
>offer/answer model with SDP for achieving negotiation while we all wait for
>SDPng.  PacketCable has discovered that while multiple codecs are often
>specified in one m= line, only one ptime can be specified across all those
>codecs.  The offshoot of this is that individual packetization rates for
>each codec cannot be specified (without going through some gyrations which
>will make the SDP grow significantly, and which draws a question about
>alternatives versus simultaneous transmission that isn't easily answered).

Could you elaborate on what you mean here? 

>This limitation then removes the possibility of a media gateway controller
>controlling bandwidth allocations during the negotiation process between two
>media gateways.  This control has turned out to be very important for QoS
>reservations.
>
>A solution that has been proposed is a new SDP "multiple ptime" parameter
>(a=mptime) that will take a list of packetization rates seperated by
>semicolons; one entry for each encoding algorithm in the associated m= line.
>Those algorithms to which packetization rate doesn't apply (like 96 -
>telephone event) will have a dash for the appropriate entry.
>
>I have read in the charter that most items of this nature will be deferred
>to SDPng.  However, we have a real opportunity here to prevent the protocols
>that use SDP for negotiation from diverging with each other and becoming
>non-interoperable by defining their own proprietary extensions to SDP.  I
>believe that this addition would fall within the spirit of the charter, as
>this extension is within the framework of SDP.

We're getting strong input from our Area Directors to keep QoS extensions
out of SDP, and to leave such work for SDPng where it can be done properly.

>What are your opinions of this proposal?  My plan is to issue an I-D for
>eventual promotion to Informational RFC status, and then to push in the
>negotiating protocols for utilization of the new parameter.  However, if the
>working group is dead-set against such an addition, then I will not bother,
>and I'll seek other methods of keeping the negotiating protocols from
>deviating from each other.

I'd like to see discussion of alternative mechanisms, for example FID, too.
Your proposal is one solution to the problem, I'm not yet convinced that
there are not other solutions using existing mechanisms.

Colin

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



From daemon@optimus.ietf.org  Wed Jul 24 18:20:09 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 SAA04177
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 18:20:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA00093
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 18:21:10 -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 SAA29648;
	Wed, 24 Jul 2002 18:13:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA29615
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 18:13:05 -0400 (EDT)
Received: from radvpost.us.radvision.com ([12.44.63.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03898
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 18:11:59 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2653.19)
	id <PC5BMP64>; Wed, 24 Jul 2002 18:12:13 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD94945018855E5@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: "'Colin Perkins'" <csp@isi.edu>, "Even, Roni" <roni.even@polycom.co.il>
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        Orit Levin
	 <orit@radvision.com>, mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft 
Date: Wed, 24 Jul 2002 18:12:04 -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

I have been thinking that this is the simplest one :-)

Of cause, the Encoder MUST be able to ignore any request... because it MUST
comply to whatever "prevent congestion algorithms" it supports. It doesn't
contradict the fact that the higher application MUST be able to request
whatever it needs to (... and be capable to get rejected by the lower
layer).

These are different decision layers. Both exist in any valid application.

The point here is that the resultant behavior of the low layer would be
DIFFERENT between the too cases! Only in one of the cases (out of the two)
the FIR is also a symptom of congestion condition in the network - the input
that would be taken into account while performing the local "prevent
congestion algorithm".

Cheers,

Orit Levin
Chief Architect
RADVISION Inc.
Tel:  +1.201.689.6330

>As for the RTCP feedback, the AVT group did not agree on requests but on an
>indication that will still allow the encoder to ignore the message. As can
>be seen from 4.3.2 above the request for full picture will not cause
>congestion even in H.320 sine the encoder may reduce quality of the full
>picture.

This is the core point of disagreement, I believe. I would argue that, no
matter how the fast update request message is transmitted, the encoder MUST
be able to ignore the request (because, for example, there may be IP level
congestion). The fact that the encoder can reduce quality so that the bit-
rate does not increase due to the full intra picture is irrelevent, since
it is possible that the network will have insufficient capacity for that
rate too.

Colin

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



From daemon@optimus.ietf.org  Wed Jul 24 18:35:22 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 SAA04523
	for <mmusic-archive@odin.ietf.org>; Wed, 24 Jul 2002 18:35:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA01284
	for mmusic-archive@odin.ietf.org; Wed, 24 Jul 2002 18:36:25 -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 SAA00403;
	Wed, 24 Jul 2002 18:29: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 SAA00372
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 18:29: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 SAA04301
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 18:27:54 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6OMSpk31700;
	Wed, 24 Jul 2002 18:28:52 -0400
Message-Id: <200207242228.g6OMSpk31700@chiron.nge.isi.edu>
To: Orit Levin <orit@radvision.com>
cc: "Even, Roni" <roni.even@polycom.co.il>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Wed, 24 Jul 2002 18:12:04 EDT."
             <0D5BBF5D638DD4119E3400508BD94945018855E5@RADVPOST> 
Date: Wed, 24 Jul 2002 18:28:51 -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

--> Orit Levin writes:
>I have been thinking that this is the simplest one :-)
>
>Of cause, the Encoder MUST be able to ignore any request... because it MUST
>comply to whatever "prevent congestion algorithms" it supports. It doesn't
>contradict the fact that the higher application MUST be able to request
>whatever it needs to (... and be capable to get rejected by the lower
>layer).
>
>These are different decision layers. Both exist in any valid application.

Yes, of course, that's what I've been saying all along. My complaint was
with the statement in the message I replied to, which said that this was
not acceptable behaviour.

>The point here is that the resultant behavior of the low layer would be
>DIFFERENT between the too cases! Only in one of the cases (out of the two)
>the FIR is also a symptom of congestion condition in the network - the input
>that would be taken into account while performing the local "prevent
>congestion algorithm".

Yes, agreed.
Colin

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



From daemon@optimus.ietf.org  Thu Jul 25 03:03: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 DAA24984
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 03:03:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA04829
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 03:04: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 DAA04228;
	Thu, 25 Jul 2002 03:00: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 DAA04194
	for <mmusic@optimus.ietf.org>; Thu, 25 Jul 2002 03:00:24 -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 CAA24890
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 02:59:19 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <38DT6A0C>; Thu, 25 Jul 2002 09:59:46 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1D0@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Colin Perkins'" <csp@isi.edu>, "Even, Roni" <roni.even@polycom.co.il>
Cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Orit Levin <orit@radvision.com>,
        mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft 
Date: Thu, 25 Jul 2002 09:59:35 +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



> -----Original Message-----
> From: Colin Perkins [mailto:csp@isi.edu]
> Sent: Wednesday, July 24, 2002 11:46 PM
> To: Even, Roni
> Cc: 'Joerg Ott'; Orit Levin; mmusic@ietf.org
> Subject: Re: [MMUSIC] video media control draft 
> 
> 
> --> "Even, Roni" writes:
> >Joerg,
> >
> >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.
> 
> In this case, the mixer is broken. It should change the SSRC on the
> outgoing packets (or change the CSRC, depending if it is 
> implemented as an
> RTP translator or mixer) which will inform the decoder that a 
> new source is
> active, and prevent it using the delta pictures on data from 
> a previous
> source.
The RTP mixer may be broken but not the MCU. H.225 states that

RTP translators and mixers are not elements of the H.323 system, and any
information about them in Annexes A and B shall be regarded as informative.
Note that both gateways and MCUs have some aspects of both mixers and
translators, and the information in Annexes A and B may be helpful in the
implementation of gateways and MCUs. However, MCUs are not mixers, and
mixers are not MCUs. Note that gateways, for example, on a packet-based
network-to-packet-based network call via the gateway may act as translators.

We have to interoperate with H.323 based systems even through signalling GW
who do not look at RTCP/RTP information
> 
> >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.
> 
> The source switch should always be accompanied by a change in 
> either SSRC
> or CSRC, so the receiver will always know it has occured. This is the
> reason RTP mixers include CSRC information, and why RTP translators
> preserve SSRC information.

Again like before, more about using CSRC H.225 says

CSRC Count (CC): Use of the CSRC count in this Recommendation is optional.
When not in use, the value of CC shall be zero (0). The CSRC may be used by
MCUs to provide information on contributors to the audio sum when
distributed audio processing is occurring. Note that there are no
capabilities associated with the ability to understand the CSRC count so the
MCU/MC has no way of knowing whether and how the terminal in the conference
makes use of the information.

> 
> >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.
> 
> Again, since the pictures will be identified by CSRC in the mixed RTP
> packet, the decoder can perform all these functions without 
> the use of 
> freeze requests.

See above
> 
> >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.
> >
> >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.
> >
> >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 cannot agree on MUST if the command is passed by the 
> signalling channel
> either: an encoder running over IP has to be aware of 
> congestion control.
> 
> Colin
> 

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



From daemon@ns.ietf.org  Thu Jul 25 15:49:20 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 PAA18715
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 15:49:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA22145
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 15:50:24 -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 PAA22016;
	Thu, 25 Jul 2002 15:44:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21985
	for <mmusic@ns.ietf.org>; Thu, 25 Jul 2002 15:44:06 -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 PAA18474
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 15:43:01 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6PJi0i04156;
	Thu, 25 Jul 2002 15:44:01 -0400
Message-Id: <200207251944.g6PJi0i04156@chiron.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: "'Joerg Ott'" <jo@tzi.uni-bremen.de>, Orit Levin <orit@radvision.com>,
        mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Thu, 25 Jul 2002 09:59:35 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1D0@ACCORD-NTSRV3> 
Date: Thu, 25 Jul 2002 15:44:00 -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

My point was that RTP has the facilities needed to handle freeze. It may 
be appropriate to change implementations to use those facilities, rather 
than defining a new mechanism, and changing implementations to use that.

Colin





--> "Even, Roni" writes:
>
>
>> -----Original Message-----
>> From: Colin Perkins [mailto:csp@isi.edu]
>> Sent: Wednesday, July 24, 2002 11:46 PM
>> To: Even, Roni
>> Cc: 'Joerg Ott'; Orit Levin; mmusic@ietf.org
>> Subject: Re: [MMUSIC] video media control draft 
>> 
>> 
>> --> "Even, Roni" writes:
>> >Joerg,
>> >
>> >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.
>> 
>> In this case, the mixer is broken. It should change the SSRC on the
>> outgoing packets (or change the CSRC, depending if it is 
>> implemented as an
>> RTP translator or mixer) which will inform the decoder that a 
>> new source is
>> active, and prevent it using the delta pictures on data from 
>> a previous
>> source.
>The RTP mixer may be broken but not the MCU. H.225 states that
>
>RTP translators and mixers are not elements of the H.323 system, and any
>information about them in Annexes A and B shall be regarded as informative.
>Note that both gateways and MCUs have some aspects of both mixers and
>translators, and the information in Annexes A and B may be helpful in the
>implementation of gateways and MCUs. However, MCUs are not mixers, and
>mixers are not MCUs. Note that gateways, for example, on a packet-based
>network-to-packet-based network call via the gateway may act as translators.
>
>We have to interoperate with H.323 based systems even through signalling GW
>who do not look at RTCP/RTP information
>> 
>> >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.
>> 
>> The source switch should always be accompanied by a change in 
>> either SSRC
>> or CSRC, so the receiver will always know it has occured. This is the
>> reason RTP mixers include CSRC information, and why RTP translators
>> preserve SSRC information.
>
>Again like before, more about using CSRC H.225 says
>
>CSRC Count (CC): Use of the CSRC count in this Recommendation is optional.
>When not in use, the value of CC shall be zero (0). The CSRC may be used by
>MCUs to provide information on contributors to the audio sum when
>distributed audio processing is occurring. Note that there are no
>capabilities associated with the ability to understand the CSRC count so the
>MCU/MC has no way of knowing whether and how the terminal in the conference
>makes use of the information.
>
>> 
>> >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.
>> 
>> Again, since the pictures will be identified by CSRC in the mixed RTP
>> packet, the decoder can perform all these functions without 
>> the use of 
>> freeze requests.
>
>See above
>> 
>> >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.
>> >
>> >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.
>> >
>> >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 cannot agree on MUST if the command is passed by the 
>> signalling channel
>> either: an encoder running over IP has to be aware of 
>> congestion control.
>> 
>> Colin
>> 

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



From daemon@ns.ietf.org  Thu Jul 25 16:23:20 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 QAA19858
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 16:23:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA24445
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 16:24:24 -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 QAA23706;
	Thu, 25 Jul 2002 16:17:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23676
	for <mmusic@ns.ietf.org>; Thu, 25 Jul 2002 16:17:20 -0400 (EDT)
Received: from web12908.mail.yahoo.com (web12908.mail.yahoo.com [216.136.174.75])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA19625
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 16:16:15 -0400 (EDT)
Message-ID: <20020725201719.52691.qmail@web12908.mail.yahoo.com>
Received: from [64.180.210.202] by web12908.mail.yahoo.com via HTTP; Thu, 25 Jul 2002 13:17:19 PDT
Date: Thu, 25 Jul 2002 13:17:19 -0700 (PDT)
From: Biz Biz <bizbiz112000@yahoo.com>
To: moms@pcolist.org
Cc: dc-urban-moms-list@mailman.dcurbanmom.com, mmusic@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-59369276-1027628239=:52331"
Subject: [MMUSIC] ALERT #1 Reading this letter changed my life!
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

--0-59369276-1027628239=:52331
Content-Type: text/plain; charset=us-ascii


GREETING !

Please follow the EXACT instructions and you will make over $50 000 in 3 months, just as I did. I found this on a bulletin board and decided to try it: A little while back, I was browsing through news groups and e-mails just like you are now, and came across an article similar to this that said you can make thousand of dollars within weeks with only an initial investment of $6.00. So I thought, "yeah right, this must be a scam," but like most of us, I was curious, so I kept reading. Anyway, it said that you send $1.00 to each of the six names and addresses stated in the article. You then place your own name and address on the bottom of the list and post the article in at least 500 news groups (there are thousands). No catch, that was it. So after thinking it over, and talking to a few people first, I thought about trying it. I figured, "What have I got to lose; except six stamps and $6.00 right, right?" Then I invested the measly $6.00. 


WELL GUESS WHAT?........Within seven days, I started getting money in the mail I was in awe. I figured it would end soon, but the money just kept coming in. In my first week I made about $31.00. By the end of the second week I had made a total of more than five hundred dollars. In the third week I had considerably more than the previous week, nearly two thousand, and it is still growing! This is my fourth week and I have made a few thousand more and it is still coming rapidly. It is certainly worth the six-dollar investment and six stamps, believe it or not I have spent more on lottery with no returns. Let me explain how this works and most important, why it works.....Also, make sure you print this article out NOW, so you can get the information. 


STOP NOW: Print this article out so you can get the information you need off of it. I promise you that if you follow the directions exactly you will start making more money than you thought possible by doing something so easy. Suggestion: Read this entire message carefully, and follow the simple directions and watch the money come in. It is easy, It is legal, and your investment is only $6.00 plus postage. Important: This is not a rip-off, it is decent, it is legal; and it virtually without risk– it really works! If all of the following instructions are adhered to, you will receive extraordinary dividends. It became an international business!


PLEASE NOTE: Please follow the directions EXACTLY, and 50-thousand-dollars or more can be yours in 20 to 60 days. This program remains successful because of the honesty and integrity of the participants. Please continue its success by carefully adhering to the instructions. You will now become a part of the Mail Order business. You are in the business of developing Mailing Lists. Many large corporations are happy to pay big bucks for quality lists. However, this money made from the mailing lists is secondary to income that is made from people like you and me asking to be included on that list. 


Here Are The Four Easy Steps To Success: 


Get six (6) separate pieces of paper and write the following on each piece of paper. "PLEASE PUT ME ON YOUR MAILING LIST." Now get six (6) U.S. 1.00 bills and place one (1) inside of each of the six pieces of paper so the bill will not be seen through the envelope (to prevent thievery). Next, place one paper in each of the six envelopes and seal them with the dollar bill enclosed. U.S RESIDENTS must remember that when sending an envelope outside the U.S (ie: Canada) you need a 60 cents stamp. You now should have six sealed envelopes each with a piece of paper stating the above phrase with your name and address written thereon [don't forget to enclose the $1.00]. What you are doing is creating a service –THIS IS ABSOLUTELY LEGAL! You are requesting a legitimate service and you are paying for it. Clearly, I was a little skeptical and a little worried about the legal aspects of it all. Therefore, I checked it out with the U.S. Postal Service (1-800-275-8777) and they confirmed !
 that it is indeed legal. 


Mail the six envelopes to the following addresses: 

 

[1] J. Dough 

2309 Catalpa Drive 

Dayton, Ohio 45406, USA


[2] Joy Moore 

400 S Kingsley Drive 

Los Angeles, CA 90020-3224, USA 


[3] Hussain 

103 Village Drive 

Avenel, NJ 07001, USA 

 

[4] Ryan Levine 

4342 Reyes Drive 

Tarzana, Ca 91356, USA 


[5] Brad Wilson 

920 Cambridge

SE, MI 49506, USA

 

[6] Frederic Desjardins,

#201-504 Alexander St. 

Vancouver, BC, V6A 1C7, Canada

 

U.S residents! **Canada and other countries: U.S International postage is a 60 cents stamp**


Now take the #1 name off the list that you see above, move the other names up (six becomes 5, and 5 becomes 4, and etc.) and add YOUR NAME as number 6 on the list. 


Change anything you need to but try to keep this article as close to the original as possible. Now post your amended article to at least 200 news groups. (I think there are close to 24,000 groups). All you need is 500, but remember, the more you post, the more money you make! This is perfectly legal. If you have any doubts, refer to Title 18 Section 1302 & 1341 of the United-States Postal Lottery Statute and the Canadian Competition Act (C-34). A legitimate service is created. Keep a copy of these directions for yourself and whenever you need money you can reuse it again. 


Please Remember: That this program remains successful because of the honesty and integrity of the participants and by their carefully adhering to directions. Look at it this way, if you are of integrity, the program will continue and the money that so many others have received will come your way. 


NOTE: You may want to retain every name and address sent to you, either on a computer or hard copy and keep the notes people send you. This VERIFIES that you are truly providing a service. Also, it is a good practice to wrap the $1.00 bill in dark paper to avoid the risk of mail theft. So, as each post is downloaded and the directions carefully followed, all members will be reimbursed for their participation as a List Developer with one dollar each. Your name will be moved up the list geometrically so that when your name reaches the #1 position you will be receiving Thousand of Dollars in Cash! What an opportunity for only six-dollars ($6) one-dollar ($!) for each of the six people listed above. Send it now, add your own name to the list and you are in business. 


Directions on How To Post To News Groups: 

You do not need to retype this letter to do your own posting. Simply put your cursor at the beginning of this letter and drag your cursor to the bottom of this document, and select copy from the edit menu. This will copy the entire letter into the computer's memory. Open a blank notepad file and place your cursor at the top of the blank page. From the edit menu select paste. This will paste a copy of the letter into the notepad so that you will add your name to the list. Save your new notepad file as a text File, if you want to do your posting in different settings, you will always have this file to go back to. Use Netscape or Internet explorer and try searching for various new groups (on-line forums, message boards, chat sites, discussions, mailing lists). Visit these message boards and post this article as a new message by highlighting the text of this letter and selecting paste from the edit menu. Fill in the subject, this will be the header that everyone sees as they scr!
 oll through the list of postings in a particular group, click the post message button. You are finished You have finished your first posting. Congratulations! 


THAT'S IT. All you have to do is jump news groups and post away, after you get the hang of it, it will take about 30 seconds for each news group. 


***REMEMBER THE MORE NEWS GROUPS YOU POST IN, THE MORE MONEY YOU WILL MAKE! *** IT IS A MOST FOR YOU TO POST A MINIMUM OF 500.***

This letter is sent only once



---------------------------------
Do You Yahoo!?
Yahoo! Health - Feel better, live better
--0-59369276-1027628239=:52331
Content-Type: text/html; charset=us-ascii

<P><FONT face=Verdana color=crimson size=4><STRONG>GREETING !</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Please follow the <FONT color=crimson>EXACT </FONT>instructions and you will make over $50 000 in 3 months, just as I did. I found this on a bulletin board and decided to try it: A little while back, I was browsing through news groups and e-mails just like you are now, and came across an article similar to this that said you can make thousand of dollars within weeks with only an initial investment of $6.00. So I thought, "yeah right, this must be a scam," but like most of us, I was curious, so I kept reading. Anyway, it said that you send $1.00 to each of the six names and addresses stated in the article. You then place your own name and address on the bottom of the list and post the article in at least 500 news groups (there are thousands). No catch, that was it. So after thinking it over, and talking to a few people first, I thought about trying it. I figured, "What have I got to lose; except six stamps and $6.00 right, right?" Then I i!
 nvested the measly $6.00. </STRONG></FONT></P>
<P><BR><FONT face=Verdana><STRONG><FONT size=4><FONT color=darkgreen>WELL GUESS WHAT?........</FONT>Within seven days, I started getting money in the mail I was in awe. I figured it would end soon, but the money just kept coming in. In my first week I made about $31.00. By the end of the second week I had made a total of more than five hundred dollars. In the third week I had considerably more than the previous week, nearly two thousand, and it is still growing! This is my fourth week and I have made a few thousand more and it is still coming rapidly. It is certainly worth the six-dollar investment and six stamps, believe it or not I have spent more on lottery with no returns. Let me explain how this works and most important, why it works.....Also, make sure you print this article out NOW, so you can get the information. </FONT></STRONG></FONT></P>
<P><BR><FONT face=Verdana><STRONG><FONT size=4><FONT color=crimson>STOP NOW:</FONT> Print this article out so you can get the information you need off of it. I promise you that if you follow the directions exactly you will start making more money than you thought possible by doing something so easy. Suggestion: Read this entire message carefully, and follow the simple directions and watch the money come in. It is easy, It is legal, and your investment is only $6.00 plus postage. Important: This is not a rip-off, it is decent, it is legal; and it virtually without risk– it really works! If all of the following instructions are adhered to, you will receive extraordinary dividends. It became an international business!</FONT></STRONG></FONT></P>
<P><BR><FONT face=Verdana><STRONG><FONT size=4><FONT color=blue>PLEASE NOTE:</FONT> Please follow the directions<FONT color=crimson> EXACTLY</FONT>, and <FONT color=crimson>50-thousand-dollars or more</FONT> can be yours in 20 to 60 days. This program remains successful because of the honesty and integrity of the participants. Please continue its success by carefully adhering to the instructions. You will now become a part of the Mail Order business. You are in the business of developing Mailing Lists. Many large corporations are happy to pay big bucks for quality lists. However, this money made from the mailing lists is secondary to income that is made from people like you and me asking to be included on that list. </FONT></STRONG></FONT></P>
<P><BR><FONT color=#0000ff><FONT face=Verdana size=4><STRONG>Here Are The Four Easy Steps To Success: </STRONG></FONT></P></FONT>
<P><BR><FONT face=Verdana size=4><STRONG>Get six (6) separate pieces of paper and write the following on each piece of paper. "PLEASE PUT ME ON YOUR MAILING LIST." Now get six (6) U.S. 1.00 bills and place one (1) inside of each of the six pieces of paper so the bill will not be seen through the envelope (to prevent thievery). Next, place one paper in each of the six envelopes and seal them with the dollar bill enclosed. U.S RESIDENTS must remember that when sending an envelope outside the U.S (ie: Canada) you need a 60 cents stamp. You now should have six sealed envelopes each with a piece of paper stating the above phrase with your name and address written thereon [don't forget to enclose the $1.00]. What you are doing is creating a service –THIS IS ABSOLUTELY LEGAL! You are requesting a legitimate service and you are paying for it. Clearly, I was a little skeptical and a little worried about the legal aspects of it all. Therefore, I checked it out with the U.S. Postal Ser!
 vice (1-800-275-8777) and they confirmed that it is indeed legal. </STRONG></FONT></P>
<P><BR><FONT color=#0000ff><FONT face=Verdana size=4><STRONG>Mail the six envelopes to the following addresses: </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG></STRONG></FONT>&nbsp;</P></FONT>
<P><FONT face=Verdana size=4><STRONG>[1] J. Dough </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>2309 Catalpa Drive </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Dayton, Ohio 45406, USA</STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>[2] Joy Moore </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>400 S Kingsley Drive </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Los Angeles, CA 90020-3224, USA </STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>[3] Hussain </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>103 Village Drive </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Avenel, NJ 07001, USA </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG></STRONG></FONT>&nbsp;</P>
<P><FONT face=Verdana size=4><STRONG>[4] Ryan Levine </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>4342 Reyes Drive </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Tarzana, Ca 91356, USA </STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>[5] Brad Wilson </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>920 Cambridge</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>SE, MI 49506, USA</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG></STRONG></FONT>&nbsp;</P>
<P><FONT face=Verdana size=4><STRONG>[6] Frederic Desjardins,</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>#201-504 Alexander St. </STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>Vancouver, BC, V6A 1C7, Canada</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG></STRONG></FONT>&nbsp;</P><FONT face=Verdana color=#0000ff size=4>
<P><STRONG>U.S residents! **Canada and other countries: U.S International postage is a 60 cents stamp**</STRONG></P></FONT>
<P><BR><FONT face=Verdana size=4><STRONG>Now take the #1 name off the list that you see above, move the other names up (six becomes 5, and 5 becomes 4, and etc.) and add YOUR NAME as number 6 on the list. </STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>Change anything you need to but try to keep this article as close to the original as possible. Now post your amended article to at least 200 news groups. (I think there are close to 24,000 groups). All you need is 500, but remember, the more you post, the more money you make! This is perfectly legal. If you have any doubts, refer to Title 18 Section 1302 &amp; 1341 of the United-States Postal Lottery Statute and the Canadian Competition Act (C-34). A legitimate service is created. Keep a copy of these directions for yourself and whenever you need money you can reuse it again. </STRONG></FONT></P>
<P><BR><FONT face=Verdana><STRONG><FONT size=4><FONT color=#0000ff>Please Remember:</FONT> That this program remains successful because of the honesty and integrity of the participants and by their carefully adhering to directions. Look at it this way, if you are of integrity, the program will continue and the money that so many others have received will come your way. </FONT></STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>NOTE: You may want to retain every name and address sent to you, either on a computer or hard copy and keep the notes people send you. This VERIFIES that you are truly providing a service. Also, it is a good practice to wrap the $1.00 bill in dark paper to avoid the risk of mail theft. So, as each post is downloaded and the directions carefully followed, all members will be reimbursed for their participation as a List Developer with one dollar each. Your name will be moved up the list geometrically so that when your name reaches the #1 position you will be receiving Thousand of Dollars in Cash! What an opportunity for only six-dollars ($6) one-dollar ($!) for each of the six people listed above. Send it now, add your own name to the list and you are in business. </STRONG></FONT></P>
<P><BR><FONT face=Verdana><STRONG><FONT size=4><FONT color=#0000ff>Directions on How To Post To News Groups:</FONT> </FONT></STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>You do not need to retype this letter to do your own posting. Simply put your cursor at the beginning of this letter and drag your cursor to the bottom of this document, and select copy from the edit menu. This will copy the entire letter into the computer's memory. Open a blank notepad file and place your cursor at the top of the blank page. From the edit menu select paste. This will paste a copy of the letter into the notepad so that you will add your name to the list. Save your new notepad file as a text File, if you want to do your posting in different settings, you will always have this file to go back to. Use Netscape or Internet explorer and try searching for various new groups (on-line forums, message boards, chat sites, discussions, mailing lists). Visit these message boards and post this article as a new message by highlighting the text of this letter and selecting paste from the edit menu. Fill in the subject, this will be the !
 header that everyone sees as they scroll through the list of postings in a particular group, click the post message button. You are finished You have finished your first posting. Congratulations! </STRONG></FONT></P>
<P><BR><FONT face=Verdana size=4><STRONG>THAT'S IT. All you have to do is jump news groups and post away, after you get the hang of it, it will take about 30 seconds for each news group. </STRONG></FONT></P>
<P><BR><FONT color=#0000ff><FONT face=Verdana size=4><STRONG>***REMEMBER THE MORE NEWS GROUPS YOU POST IN, THE MORE MONEY YOU WILL MAKE! *** IT IS A MOST FOR YOU TO POST A MINIMUM OF 500.***</STRONG></FONT></P>
<P><FONT face=Verdana size=4><STRONG>This letter is sent only once</STRONG></FONT></P></FONT><p><br><hr size=1><b>Do You Yahoo!?</b><br>
<a href="http://health.yahoo.com/">Yahoo! Health</a> - Feel better, live better
--0-59369276-1027628239=:52331--

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



From daemon@ns.ietf.org  Thu Jul 25 16:28: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 QAA20039
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 16:28:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA24592
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 16:29: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 QAA24287;
	Thu, 25 Jul 2002 16:22: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 PAA19683
	for <mmusic@optimus.ietf.org>; Wed, 24 Jul 2002 15:40:01 -0400 (EDT)
Received: from goobox (tog-wakko3.prognet.com [207.188.29.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29402
	for <mmusic@ietf.org>; Wed, 24 Jul 2002 15:38:56 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
  (uid 500)
  by goobox with local; Wed, 24 Jul 2002 12:39:34 -0700
>Return-Path: <rtspspec-bugs-admin@lists.sourceforge.net>
Received: from mail.real.com [207.188.7.41] by localhost with POP3 (fetchmail-5.9.6) for robla@localhost (single-drop); Wed, 24 Jul 2002 12:39:34 -0700 (PDT)
Received: from usw-sf-list2.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by real.com (8.12.2/8.12.2) with ESMTP id g6OJdBMA004248 for <robla@real.com>; Wed, 24 Jul 2002 12:39:12 -0700
Received: from usw-sf-list1-b.sourceforge.net ([10.3.1.13] helo=usw-sf-list1.sourceforge.net) by usw-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 17XRyb-0006uO-00 for <robla@real.com>; Wed, 24 Jul 2002 12:39:13 -0700
Date: Wed, 24 Jul 2002 12:38:23 -0700
From: rtspspec-bugs-request@lists.sourceforge.net
X-Mailer: Mailman v2.0.9-sf.net
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Old-To: rtspspec-bugs@lists.sourceforge.net
X-BeenThere: rtspspec-bugs@lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
Message-Id: <E17XRyb-0006uO-00@usw-sf-list2.sourceforge.net>
X-Spam-Status: No, hits=1.6 required=5.5 tests=NO_REAL_NAME,DOUBLE_CAPSWORD version=2.31
X-Spam-Level: *
X-UIDL: 5f4257f5bd3e3d8a1620b15a98d66b86
To: mmusic@ietf.org
Reply-to: mmusic@ietf.org
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #44 - 1 msg
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




This is an automatic digest of bugs submitted and changed on the RTSP bug tracker.  To see a list of bugs, visit:

http://sf.net/projects/rtspspec

When replying, please make your Subject line more specific than "Re: Rtspspec-bugs digest"



Today's Topics:

   1. [ rtspspec-Bugs-585865 ] Use of Date, and Host in RTSP (noreply@sourceforge.net)

--__--__--

Message: 1
To: noreply@sourceforge.net
From: noreply@sourceforge.net
Date: Wed, 24 Jul 2002 04:22:13 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-585865 ] Use of Date, and Host in RTSP

Bugs item #585865, was opened at 2002-07-24 13:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=585865&group_id=23194

Category: General
Group: Fix for Draft Standard
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Rob Lanphier (robla)
Summary: Use of Date, and Host in RTSP

Initial Comment:
There exist a number of HTTP headers that are just
referenced into the specification. Several is hard to
interpret on how they relate to RTSP and what
requirement level that is needed. 

Date:
The date header MUST be sent by origin server in
responses. What is an origin server and what exceptions
exist for RTSP? For RTSP does that include requests also?

Host:
The comment is that this should not be used in RTSP.
This should be reflected in the heade table. 

Other headers that are simply referenced needs most
probably some specification on applicability and
exceptions.


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=585865&group_id=23194




End of Rtspspec-bugs Digest



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



From daemon@ns.ietf.org  Thu Jul 25 16:40: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 QAA20548
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 16:40:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA25730
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 16:41: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 QAA25430;
	Thu, 25 Jul 2002 16:36: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 QAA24536
	for <mmusic@ns.ietf.org>; Thu, 25 Jul 2002 16:28:34 -0400 (EDT)
Received: from imo-m01.mx.aol.com (imo-m01.mx.aol.com [64.12.136.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19973
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 16:27:29 -0400 (EDT)
From: Mookiedome@aol.com
Received: from Mookiedome@aol.com
	by imo-m01.mx.aol.com (mail_out_v32.21.) id d.18c.b4e2ff8 (30960);
	Thu, 25 Jul 2002 16:27:45 -0400 (EDT)
Message-ID: <18c.b4e2ff8.2a71b941@aol.com>
Date: Thu, 25 Jul 2002 16:27:45 EDT
To: bizbiz112000@yahoo.com, moms@pcolist.org
CC: dc-urban-moms-list@mailman.dcurbanmom.com, mmusic@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Mac sub 39
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: [DC-Urban-Moms-List] ALERT #1 Reading this letter changed my life!
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

You Could Be Prosecuted 
Sometimes posters claim that these schemes are completely legal, claiming 
they are mailing list or recipe services. These posters may even cite title 
18, sections 1302, 1341, 1342, and 1343 of the "Postal Lottery Laws." These 
sections are part of the U.S. Code. I'm sure that none of these people have 
actually read them, because they do not authorize pyramid schemes. In fact, 
these are the very laws that make pyramid schemes illegal. (Take a minute to 
read 18 USC 1302, 1341, 1342, and 1343 for yourself.)

They may also claim that their e-mails are legal under "S. 1618" or "H.R. 
3113." These were bills in the U.S. Congress that failed to become law. They 
have no legal effect. (See this Web page from a British site for a nice 
summary.)

Pyramid schemes have long been illegal when conducted by mail in the United 
States or Canada. The same laws apply to Internet chain letters if the mails 
are used at any point in the scheme.

The latest twist in these schemes is to claim to be selling something, such 
as reports, mailing lists, or recipes. The U.S. Postal Service warns:

Do not be fooled if the chain letter is used to sell inexpensive reports on 
credit, mail order sales, mailing lists, or other topics. The primary purpose 
is to take your money, not to sell information. "Selling" a product does not 
ensure legality. 

[A couple of ideas for Americans wishing to report pyramid schemes: If the 
e-mail asks you to send money through the mail, you may report it using the 
U.S. Postal Inspection Service Mail Fraud Complaint Form, e-mail 
fraud@uspis.gov, or report it via snail mail to
Postal Inspector
c/o Postmaster
Your City, Your State, Your Zip


(A stamp is required.)]


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



From daemon@ns.ietf.org  Thu Jul 25 16:42:01 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 QAA20599
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 16:42:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA25782
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 16:43: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 QAA25656;
	Thu, 25 Jul 2002 16:40: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 QAA25591
	for <mmusic@ns.ietf.org>; Thu, 25 Jul 2002 16:40:28 -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 QAA20487
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 16:39:23 -0400 (EDT)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g6PKeRP04666
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 16:40:27 -0400
Message-Id: <200207252040.g6PKeRP04666@chiron.nge.isi.edu>
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Re: [DC-Urban-Moms-List] ALERT #1 Reading this letter changed my life! 
In-Reply-To: Your message of "Thu, 25 Jul 2002 16:27:45 EDT."
             <18c.b4e2ff8.2a71b941@aol.com> 
Date: Thu, 25 Jul 2002 16:40:27 -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

Folks,

I approved this, but please no more posts on this subject. The original
spam came from a subscriber to the mmusic list, and so avoided the spam
filter. That subscriber has now been removed from the list.

Colin



--> Mookiedome@aol.com writes:
>You Could Be Prosecuted 
>Sometimes posters claim that these schemes are completely legal, claiming 
>they are mailing list or recipe services. These posters may even cite title 
>18, sections 1302, 1341, 1342, and 1343 of the "Postal Lottery Laws." These 
>sections are part of the U.S. Code. I'm sure that none of these people have 
>actually read them, because they do not authorize pyramid schemes. In fact, 
>these are the very laws that make pyramid schemes illegal. (Take a minute to 
>read 18 USC 1302, 1341, 1342, and 1343 for yourself.)
>
>They may also claim that their e-mails are legal under "S. 1618" or "H.R. 
>3113." These were bills in the U.S. Congress that failed to become law. They 
>have no legal effect. (See this Web page from a British site for a nice 
>summary.)
>
>Pyramid schemes have long been illegal when conducted by mail in the United 
>States or Canada. The same laws apply to Internet chain letters if the mails 
>are used at any point in the scheme.
>
>The latest twist in these schemes is to claim to be selling something, such 
>as reports, mailing lists, or recipes. The U.S. Postal Service warns:
>
>Do not be fooled if the chain letter is used to sell inexpensive reports on 
>credit, mail order sales, mailing lists, or other topics. The primary purpose 
>is to take your money, not to sell information. "Selling" a product does not 
>ensure legality. 
>
>[A couple of ideas for Americans wishing to report pyramid schemes: If the 
>e-mail asks you to send money through the mail, you may report it using the 
>U.S. Postal Inspection Service Mail Fraud Complaint Form, e-mail 
>fraud@uspis.gov, or report it via snail mail to
>Postal Inspector
>c/o Postmaster
>Your City, Your State, Your Zip
>
>
>(A stamp is required.)]
>
>
>_______________________________________________
>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@ns.ietf.org  Thu Jul 25 18:45:52 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 SAA23764
	for <mmusic-archive@odin.ietf.org>; Thu, 25 Jul 2002 18:45:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA02327
	for mmusic-archive@odin.ietf.org; Thu, 25 Jul 2002 18:46:55 -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 SAA02263;
	Thu, 25 Jul 2002 18:44:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA02232
	for <mmusic@ns.ietf.org>; Thu, 25 Jul 2002 18:44:56 -0400 (EDT)
Received: from gw-nl6.philips.com (gw-nl6.philips.com [212.153.235.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23694
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 18:43:51 -0400 (EDT)
From: erwin.riemens@philips.com
Received: from smtpscan-nl1.philips.com (smtpscan-nl1.philips.com [130.139.36.21])
	by gw-nl6.philips.com (Postfix) with ESMTP id 80BFAA1013
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 00:44:55 +0200 (MET DST)
Received: from smtprelay-nl1.philips.com (localhost [127.0.0.1]) 
	by smtpscan-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id AAA12534
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 00:44:55 +0200 (MET DST)
Received: from ehv501soh.diamond.philips.com (e3soh01.diamond.philips.com [130.139.54.47]) 
	by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id AAA26205
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 00:44:54 +0200 (MET DST)
To: mmusic@ietf.org
Message-ID: <OF24DF7443.6B163217-ONC1256C01.007CB98A-C1256C01.007CB98B@diamond.philips.com>
Date: Fri, 26 Jul 2002 00:42:19 +0200
X-MIMETrack: Serialize by Router on ehv501soh/H/SERVER/PHILIPS(Release 5.0.9a |January 7, 2002) at
 26/07/2002 00:42:21
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [MMUSIC] Erwin Riemens is out of the office.
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

I will be out of the office starting  2002-07-22 and will not return until 2002-08-09.

I will respond to your message when I return.


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



From daemon@ns.ietf.org  Fri Jul 26 01:50: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 BAA00356
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 01:50:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA00110
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 01:51:31 -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 BAA29918;
	Fri, 26 Jul 2002 01:45: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 BAA29890
	for <mmusic@ns.ietf.org>; Fri, 26 Jul 2002 01:45:13 -0400 (EDT)
Received: from node24.neomagic.com (h-21-82-20.ccnet.com [207.21.82.20] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00282
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 01:44:06 -0400 (EDT)
Received: from node27.neomagic.com (node27.neomagic.com [192.168.51.27])
	by node24.neomagic.com (8.12.5/8.12.5) with ESMTP id g6Q5iapl013878
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 22:44:36 -0700
Received: from neomagic.com ([192.168.31.253])
	by node27.neomagic.com (8.12.5/8.12.5) with ESMTP id g6Q5iWOm007109
	for <mmusic@ietf.org>; Thu, 25 Jul 2002 22:44:34 -0700
Message-ID: <3D4233E1.6020709@neomagic.com>
Date: Sat, 27 Jul 2002 11:17:13 +0530
From: Mukul Purohit <mpurohit@neomagic.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020326
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] a trivial question
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,

I have been going through RTSP draft, and want some clarity on one 
point. Is it a valid assumtion that a client will not send multiple RTSP 
requests simultaneously for a single session, i. e. before getting 
response for a previous request, another request is sent.

An example of such situation is when a client want to send multiple 
SETUP (also TEARDOWN) request for different media, simultaneously.

The state machine  (which is for server I suppose) described in the 
draft doesnt say that one cannot do multiple sends ( or I have not found 
it). So a client implementation may be such that  it sends multiple 
requests (to save upon some delay in round-trip), although at the cost 
of  increase complexity at client. Will this be processed properly ?

thanks and regards
mukul


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



From daemon@ns.ietf.org  Fri Jul 26 02:24: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 CAA09694
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 02:24:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA01426
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 02:25: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 CAA01264;
	Fri, 26 Jul 2002 02:15: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 CAA01229
	for <mmusic@ns.ietf.org>; Fri, 26 Jul 2002 02:15:16 -0400 (EDT)
Received: from parsmtp1.rd.francetelecom.com (parsmtp1.rd.francetelecom.com [194.167.105.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09603
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 02:14:10 -0400 (EDT)
Received: from parmhs3.rd.francetelecom.fr ([10.193.117.62]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Fri, 26 Jul 2002 08:15:14 +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: Fri, 26 Jul 2002 08:15:14 +0200
Message-ID: <A2200E9A0E413B4C99FB7384D740878124DFC2@parmhs3.rd.francetelecom.fr>
Thread-Topic: [MMUSIC] video media control draft 
Thread-Index: AcIzUgquis44glBlRk+HP6BFJdD5uQBF6yQA
From: "MONFORT Patrick FTRD/DMI/ISS" <patrick.monfort@rd.francetelecom.com>
To: "Colin Perkins" <csp@isi.edu>
Cc: <mmusic@ietf.org>
X-OriginalArrivalTime: 26 Jul 2002 06:15:14.0859 (UTC) FILETIME=[CE63D7B0:01C2346B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA01230
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

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  Fri Jul 26 06:05: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 GAA13022
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 06:05:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA11856
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 06:06:34 -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 FAA10803;
	Fri, 26 Jul 2002 05:54: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 FAA10774
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 05:54:18 -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 FAA12863
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 05:53:06 -0400 (EDT)
From: danutf@redlinecommunications.ro
Received: from localhost (danutf@localhost)
	by mail.redlinecommunications.ro (8.11.4/8.11.4) with ESMTP id g6Q9rS515243;
	Fri, 26 Jul 2002 12:53:29 +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: Fri, 26 Jul 2002 12:53:28 +0300 (EEST)
To: <mmusic@ietf.org>
cc: <mjh@icir.org>, <van@packetdesign.com>, <csp@isi.edu>
Message-ID: <Pine.LNX.4.33.0207261227270.15043-100000@mail.redlinecommunications.ro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [MMUSIC] Tool starting mode attributes in SDP
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 all,

In the latest SDP draft are defined four complementary attributes
which specify how to start the media tools:
a=recvonly
a=sendonly
a=sendrecv
a=inactive

In my opinion only ONE attribute of this types makes sense
at session-level and at each media level.
This is obvious, of course, but the current draft text allows for MORE
THAN ONE starting mode attribute per session and per media level.

Even if it is obvious, maybe you would like to explicitly enforce this
matter in the next draft.

Best regards,
Dan Firac,
Software Engineer,
Redline Communications,
Romania.
+40 723 260 623




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



From daemon@optimus.ietf.org  Fri Jul 26 08:13:10 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 IAA16146
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 08:13:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA17527
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 08:14:16 -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 IAA17284;
	Fri, 26 Jul 2002 08:11:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17255
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 08:11:19 -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 IAA15930;
	Fri, 26 Jul 2002 08:10:11 -0400 (EDT)
Message-Id: <200207261210.IAA15930@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: Fri, 26 Jul 2002 08:10:11 -0400
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-comedia-04.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.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Connection-Oriented Media Transport in SDP
	Author(s)	: D. Yon
	Filename	: draft-ietf-mmusic-sdp-comedia-04.txt
	Pages		: 16
	Date		: 25-Jul-02
	
This document describes how to express media transport over 
connection-oriented protocols using the Session Description Protocol 
(SDP).  It defines two new protocol identifiers: TCP and TLS.  It 
also defines the syntax and semantics for an SDP 'direction' 
attribute that describes the connection setup procedure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-comedia-04.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-ietf-mmusic-sdp-comedia-04.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mmusic-sdp-comedia-04.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:	<20020725151313.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mmusic-sdp-comedia-04.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Fri Jul 26 12:18:06 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 MAA27923
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 12:18:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA05171
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 12:19:11 -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 MAA04869;
	Fri, 26 Jul 2002 12:13:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04838
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 12:13:37 -0400 (EDT)
Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27652
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 12:12:32 -0400 (EDT)
Received: from real.com (murrow2k1.real.com [207.188.7.41])
	by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g6QGCxqk030773;
	Fri, 26 Jul 2002 09:12:59 -0700
Received: from localhost (cronkite.prognet.com [208.147.89.1])
	by real.com (8.12.2/8.12.2) with ESMTP id g6QGCtMB000959;
	Fri, 26 Jul 2002 09:12:57 -0700
Date: Fri, 26 Jul 2002 10:13:38 -0700 (Pacific Daylight Time)
From: Rob Lanphier <robla@real.com>
To: Mukul Purohit <mpurohit@neomagic.com>
cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] a trivial question
In-Reply-To: <3D4233E1.6020709@neomagic.com>
Message-ID: <Pine.WNT.4.43.0207261011400.-309325@Default.pacbell.net>
X-X-Sender: robla@goobox.prognet.com
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

On Sat, 27 Jul 2002, Mukul Purohit wrote:
> I have been going through RTSP draft, and want some clarity on one
> point. Is it a valid assumtion that a client will not send multiple RTSP
> requests simultaneously for a single session, i. e. before getting
> response for a previous request, another request is sent.
>
> An example of such situation is when a client want to send multiple
> SETUP (also TEARDOWN) request for different media, simultaneously.
>
> The state machine  (which is for server I suppose) described in the
> draft doesnt say that one cannot do multiple sends ( or I have not found
> it). So a client implementation may be such that  it sends multiple
> requests (to save upon some delay in round-trip), although at the cost
> of  increase complexity at client. Will this be processed properly ?

This should be valid, so long as the requests are all valid in context.

Rob

-- 
Rob Lanphier, Program Manager  --  Interoperability, RealNetworks
http://helixcommunity.org http://rtsp.org http://realnetworks.com



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



From daemon@optimus.ietf.org  Fri Jul 26 13:47:18 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 NAA01835
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 13:47:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA11151
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 13:48: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 NAA11002;
	Fri, 26 Jul 2002 13:45: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 NAA10973
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 13:45:38 -0400 (EDT)
Received: from purple.nge.isi.edu (wireless219.east.isi.edu [65.123.202.219])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01765
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 13:44:32 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6QHjWh4007396;
	Fri, 26 Jul 2002 13:45:38 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207261745.g6QHjWh4007396@purple.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 "Fri, 26 Jul 2002 08:15:14 +0200."
             <A2200E9A0E413B4C99FB7384D740878124DFC2@parmhs3.rd.francetelecom.fr> 
Date: Fri, 26 Jul 2002 13:45:32 -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

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  Fri Jul 26 13:51: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 NAA02047
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 13:51:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA11308
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 13:52: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 NAA11129;
	Fri, 26 Jul 2002 13:47:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11092
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 13:47:32 -0400 (EDT)
Received: from purple.nge.isi.edu (wireless219.east.isi.edu [65.123.202.219])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01818
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 13:46:26 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6QHlUh4007453;
	Fri, 26 Jul 2002 13:47:30 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207261747.g6QHlUh4007453@purple.nge.isi.edu>
To: danutf@redlinecommunications.ro
cc: mmusic@ietf.org, mjh@icir.org, van@packetdesign.com
In-Reply-To: Your message of "Fri, 26 Jul 2002 12:53:28 +0300."
             <Pine.LNX.4.33.0207261227270.15043-100000@mail.redlinecommunications.ro> 
Date: Fri, 26 Jul 2002 13:47:30 -0400
From: Colin Perkins <csp@isi.edu>
Subject: [MMUSIC] Re: Tool starting mode attributes in SDP
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

--> danutf@redlinecommunications.ro writes:
>Hello all,
>
>In the latest SDP draft are defined four complementary attributes
>which specify how to start the media tools:
>a=recvonly
>a=sendonly
>a=sendrecv
>a=inactive
>
>In my opinion only ONE attribute of this types makes sense
>at session-level and at each media level.
>This is obvious, of course, but the current draft text allows for MORE
>THAN ONE starting mode attribute per session and per media level.
>
>Even if it is obvious, maybe you would like to explicitly enforce this
>matter in the next draft.

Do you have a suggested wording change? This doesn't seem like something
that can easily be enforced in the ABNF.

Colin

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



From daemon@optimus.ietf.org  Fri Jul 26 14:49: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 OAA04072
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 14:49:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14940
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 14:50: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 OAA14845;
	Fri, 26 Jul 2002 14:47: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 OAA14526
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 14:44:12 -0400 (EDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03837
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 14:43:05 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate.mot.com (motgate 2.1) with ESMTP id LAA04448 for <mmusic@ietf.org>; Fri, 26 Jul 2002 11:44:11 -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 LAA16789 for <mmusic@ietf.org>; Fri, 26 Jul 2002 11:42:43 -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 g6QImai03691
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 13:48:36 -0500
Message-ID: <3D419984.2358520F@motorola.com>
Date: Fri, 26 Jul 2002 13:48:36 -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: mmusic@ietf.org
References: <Pine.LNX.4.33.0207261227270.15043-100000@mail.redlinecommunications.ro> <200207261747.g6QHlUh4007453@purple.nge.isi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [MMUSIC] Re: Tool starting mode attributes in SDP
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


How about...

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

or, since that involves a protocol change...

toolmode = [ "a=" ( "recvonly" / "sendonly" / "sendrecv") CRLF
            [ "a=inactive" CRLF ] ]

which only involves a change to the ABNF.  The problem with the latter
approach is that it doesn't reliably disambiguate between a session default
and a media override.  Does a media level "a=recvonly" override a session
level "a=sendonly"? No, according to sdp-new-10, Section 6


> The connection (`c=') and attribute (`a=') information in the session-
> level section applies to all the media of that session unless overridden
> by connection information or an attribute of the same name in the media
> description.
>
Bryan.

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

Colin Perkins wrote:

> --> danutf@redlinecommunications.ro writes:
> >Hello all,
> >
> >In the latest SDP draft are defined four complementary attributes
> >which specify how to start the media tools:
> >a=recvonly
> >a=sendonly
> >a=sendrecv
> >a=inactive
> >
> >In my opinion only ONE attribute of this types makes sense
> >at session-level and at each media level.
> >This is obvious, of course, but the current draft text allows for MORE
> >THAN ONE starting mode attribute per session and per media level.
> >
> >Even if it is obvious, maybe you would like to explicitly enforce this
> >matter in the next draft.
>
> Do you have a suggested wording change? This doesn't seem like something
> that can easily be enforced 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  Fri Jul 26 15:11: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 PAA04728
	for <mmusic-archive@odin.ietf.org>; Fri, 26 Jul 2002 15:11:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA16655
	for mmusic-archive@odin.ietf.org; Fri, 26 Jul 2002 15:12:59 -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 PAA16466;
	Fri, 26 Jul 2002 15:06:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA16435
	for <mmusic@optimus.ietf.org>; Fri, 26 Jul 2002 15:06:49 -0400 (EDT)
Received: from purple.nge.isi.edu (wireless219.east.isi.edu [65.123.202.219])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04576
	for <mmusic@ietf.org>; Fri, 26 Jul 2002 15:05:44 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6QJ6mh4008182;
	Fri, 26 Jul 2002 15:06:48 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207261906.g6QJ6mh4008182@purple.nge.isi.edu>
To: Bryan Thale <bryan.thale@motorola.com>
cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Re: Tool starting mode attributes in SDP 
In-Reply-To: Your message of "Fri, 26 Jul 2002 13:48:36 CDT."
             <3D419984.2358520F@motorola.com> 
Date: Fri, 26 Jul 2002 15:06:48 -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

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

Colin



--> Bryan Thale writes:
>How about...
>
>"a=toolmode:" *SP ("recvonly" / "sendonly" / "sendrecv") [ 1*SP "inactive"
>] CRLF
>
>or, since that involves a protocol change...
>
>toolmode = [ "a=" ( "recvonly" / "sendonly" / "sendrecv") CRLF
>            [ "a=inactive" CRLF ] ]
>
>which only involves a change to the ABNF.  The problem with the latter
>approach is that it doesn't reliably disambiguate between a session default
>and a media override.  Does a media level "a=recvonly" override a session
>level "a=sendonly"? No, according to sdp-new-10, Section 6
>
>
>> The connection (`c=') and attribute (`a=') information in the session-
>> level section applies to all the media of that session unless overridden
>> by connection information or an attribute of the same name in the media
>> description.
>>
>Bryan.
>
>--
>Bryan Thale
>Networks & Infrastructure Research, Motorola Labs
>mailto:bryan.thale@motorola.com
>
>Colin Perkins wrote:
>
>> --> danutf@redlinecommunications.ro writes:
>> >Hello all,
>> >
>> >In the latest SDP draft are defined four complementary attributes
>> >which specify how to start the media tools:
>> >a=recvonly
>> >a=sendonly
>> >a=sendrecv
>> >a=inactive
>> >
>> >In my opinion only ONE attribute of this types makes sense
>> >at session-level and at each media level.
>> >This is obvious, of course, but the current draft text allows for MORE
>> >THAN ONE starting mode attribute per session and per media level.
>> >
>> >Even if it is obvious, maybe you would like to explicitly enforce this
>> >matter in the next draft.
>>
>> Do you have a suggested wording change? This doesn't seem like something
>> that can easily be enforced 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  Sun Jul 28 03:12:49 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 DAA22911
	for <mmusic-archive@odin.ietf.org>; Sun, 28 Jul 2002 03:12:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA21238
	for mmusic-archive@odin.ietf.org; Sun, 28 Jul 2002 03:13:56 -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 DAA21138;
	Sun, 28 Jul 2002 03:08: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 DAA21107
	for <mmusic@optimus.ietf.org>; Sun, 28 Jul 2002 03:08:01 -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 DAA22845
	for <mmusic@ietf.org>; Sun, 28 Jul 2002 03:06:49 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <PVKD5G5Y>; Sun, 28 Jul 2002 10:07:18 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1DA@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Colin Perkins'" <csp@isi.edu>,
        MONFORT Patrick FTRD/DMI/ISS
	 <patrick.monfort@rd.francetelecom.com>
Cc: mmusic@ietf.org
Subject: RE: [MMUSIC] video media control draft 
Date: Sun, 28 Jul 2002 10:07:17 +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

Colin,
I think that you responses are missing the point. The RTP and RTCP can give
INDICATIONS about the status of the call but they were not meant to serve as
requests for changing the stream state and flow. Furthermore the RTP and
RTCP are unreliable channels and that prevent them from being used for the
requests we want. We want to have a way to request state change and stream
flow change in the signalling protocol since this is done by the call
management application and not by the encoder/decoder!!!.
We need a solution that will be available in SIP and that means SDP or INFO
method. Developing a  new control protocols will take too long or maybe you
want to suggest that we will use H.245 which is tunneled today in H.323 in
the call setup channel.
Regards
Roni Even

> -----Original Message-----
> From: Colin Perkins [mailto:csp@isi.edu]
> Sent: Friday, July 26, 2002 8:46 PM
> 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  Sun Jul 28 12:39: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 MAA29268
	for <mmusic-archive@odin.ietf.org>; Sun, 28 Jul 2002 12:39:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA08389
	for mmusic-archive@odin.ietf.org; Sun, 28 Jul 2002 12:40:59 -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 MAA08371;
	Sun, 28 Jul 2002 12:39: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 MAA08341
	for <mmusic@optimus.ietf.org>; Sun, 28 Jul 2002 12:39:16 -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 MAA29257
	for <mmusic@ietf.org>; Sun, 28 Jul 2002 12:38:09 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1])
	by purple.nge.isi.edu (8.12.4/8.12.4) with ESMTP id g6SGc1h4056051;
	Sun, 28 Jul 2002 12:38:01 -0400 (EDT)
	(envelope-from csp@purple.nge.isi.edu)
Message-Id: <200207281638.g6SGc1h4056051@purple.nge.isi.edu>
To: "Even, Roni" <roni.even@polycom.co.il>
cc: MONFORT Patrick FTRD/DMI/ISS <patrick.monfort@rd.francetelecom.com>,
        mmusic@ietf.org
Subject: Re: [MMUSIC] video media control draft 
In-Reply-To: Your message of "Sun, 28 Jul 2002 10:07:17 +0300."
             <B2518D608282D511BEA400508BBB9148EAA1DA@ACCORD-NTSRV3> 
Date: Sun, 28 Jul 2002 12:38:01 -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

Roni,

--> "Even, Roni" writes:
>Colin,
>I think that you responses are missing the point. The RTP and RTCP can give
>INDICATIONS about the status of the call but they were not meant to serve as
>requests for changing the stream state and flow. Furthermore the RTP and
>RTCP are unreliable channels and that prevent them from being used for the
>requests we want. We want to have a way to request state change and stream
>flow change in the signalling protocol since this is done by the call
>management application and not by the encoder/decoder!!!.

I disagree with your characterisation of RTCP. 

I believe RTCP is more appropriate for your needs, since you are requesting
a change in the encoder operation (to send a full intra frame). Controlling
the state of the encoder based on feedback from the receivers would seem to
fit very well with the RTCP model.

Reliability is a non-issue, since you can resend the message if the codec
hasn't changed its behaviour in a reasonable time. 

>We need a solution that will be available in SIP and that means SDP or INFO
>method. Developing a  new control protocols will take too long or maybe you
>want to suggest that we will use H.245 which is tunneled today in H.323 in
>the call setup channel.

I believe Jonathan Rosenberg described why SIP/SDP are not the appropriate
solutions here. What you are requesting is not a change to the call state,
it's a request to the encoder. As such, it should be sent to the encoder.

Colin

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



From daemon@optimus.ietf.org  Mon Jul 29 06:10: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 GAA22683
	for <mmusic-archive@odin.ietf.org>; Mon, 29 Jul 2002 06:10:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA26005
	for mmusic-archive@odin.ietf.org; Mon, 29 Jul 2002 06:12: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 GAA25874;
	Mon, 29 Jul 2002 06:07:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA25843
	for <mmusic@optimus.ietf.org>; Mon, 29 Jul 2002 06:07:11 -0400 (EDT)
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22598
	for <mmusic@ietf.org>; Mon, 29 Jul 2002 06:06:03 -0400 (EDT)
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6TA5Td29972
	for <mmusic@ietf.org>; Mon, 29 Jul 2002 13:05:29 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c62e2e8abac158f240b2@esvir04nok.ntc.nokia.com>;
 Mon, 29 Jul 2002 13:07:09 +0300
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 29 Jul 2002 13:07:09 +0300
Received: from agni.research.nokia.com (agni.research.nokia.com [172.21.40.24])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id NAA09748;
	Mon, 29 Jul 2002 13:07:08 +0300 (EETDST)
Received: (from ppessi@localhost)
	by agni.research.nokia.com (8.11.6/8.11.2) id g6QFUfh07754;
	Fri, 26 Jul 2002 18:30:41 +0300
To: Mukul Purohit <mpurohit@neomagic.com>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] a trivial question
References: <3D4233E1.6020709@neomagic.com>
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <3D4233E1.6020709@neomagic.com>
Date: 26 Jul 2002 18:30:40 +0300
Message-ID: <pvy9byfqvz.fsf@agni.research.nokia.com>
Lines: 21
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 29 Jul 2002 10:07:09.0007 (UTC) FILETIME=[B31B95F0:01C236E7]
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

Mukul Purohit <mpurohit@neomagic.com> writes:
>I have been going through RTSP draft, and want some clarity on one point. Is
>it a valid assumtion that a client will not send multiple RTSP requests
>simultaneously for a single session, i. e. before getting response for a
>previous request, another request is sent.

	No. See section 9.1:

9.1 Pipelining

   A client that supports persistent connections or connectionless mode
   MAY "pipeline" its requests (i.e., send multiple requests without
   waiting for each response). A server MUST send its responses to those
   requests in the same order that the requests were received.

	I recall it has been discussed whether some pipelined requests
	(like multiple PLAYs) make any sense, but pipelining can be used
	in RTSP.

						Pekka


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



From daemon@optimus.ietf.org  Wed Jul 31 06:10: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 GAA19596
	for <mmusic-archive@odin.ietf.org>; Wed, 31 Jul 2002 06:10:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA27553
	for mmusic-archive@odin.ietf.org; Wed, 31 Jul 2002 06:11:38 -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 GAA27448;
	Wed, 31 Jul 2002 06:07:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA27417
	for <mmusic@optimus.ietf.org>; Wed, 31 Jul 2002 06:07:10 -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 GAA19505
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 06:06:02 -0400 (EDT)
Received: from there ([10.0.2.14])
	by prix.tandberg.no (8.11.6/8.11.6) with SMTP id g6VA6du29275
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 12:06:39 +0200
Message-Id: <200207311006.g6VA6du29275@prix.tandberg.no>
Content-Type: text/plain;
  charset="iso-8859-15"
X-KMail-Redirect-From: Nils Henrik Lorentzen <nhl@tandberg.no>
From: Nils Henrik Lorentzen <nhl@tandberg.no> (by way of Nils Henrik Lorentzen <nhl@tandberg.no>)
Date: Wed, 31 Jul 2002 12:03:33 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
To: mmusic@ietf.org
X-Scanned-By: MIMEDefang 2.14 (www dot roaringpenguin dot com slash mimedefang)
Content-Transfer-Encoding: 8bit
Subject: [MMUSIC] Signaling FIR/Freeze in SIP
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,

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



From daemon@optimus.ietf.org  Wed Jul 31 06: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 GAA20416
	for <mmusic-archive@odin.ietf.org>; Wed, 31 Jul 2002 06:40:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA29245
	for mmusic-archive@odin.ietf.org; Wed, 31 Jul 2002 06:41: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 GAA29177;
	Wed, 31 Jul 2002 06:39:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA29144
	for <mmusic@optimus.ietf.org>; Wed, 31 Jul 2002 06:39:18 -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 GAA20370
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 06:38:09 -0400 (EDT)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <P0L2KGVR>; Wed, 31 Jul 2002 13:38:39 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EAA1E0@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Nils Henrik Lorentzen'" <nhl@tandberg.no>, mmusic@ietf.org
Subject: RE: [MMUSIC] Signaling FIR/Freeze in SIP
Date: Wed, 31 Jul 2002 13:38:38 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-15"
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,
My comments are inside
Roni Even

> -----Original Message-----
> From: Nils Henrik Lorentzen [mailto:nhl@tandberg.no]
> Sent: Wednesday, July 31, 2002 1:04 PM
> 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.

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. 
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.


> 
> - 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.

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

> 
> 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.

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.

> 
> 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  Wed Jul 31 08:22: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 IAA23137
	for <mmusic-archive@odin.ietf.org>; Wed, 31 Jul 2002 08:22:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA04352
	for mmusic-archive@odin.ietf.org; Wed, 31 Jul 2002 08:24: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 IAA04182;
	Wed, 31 Jul 2002 08:19:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04146
	for <mmusic@optimus.ietf.org>; Wed, 31 Jul 2002 08:19:46 -0400 (EDT)
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23016
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 08:18:37 -0400 (EDT)
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g6VCVXf08049
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 15:31:33 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5c6da903e3ac158f22079@esvir02nok.ntc.nokia.com> for <mmusic@ietf.org>;
 Wed, 31 Jul 2002 15:19:44 +0300
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 31 Jul 2002 15:19:44 +0300
Received: from agni.research.nokia.com (agni.research.nokia.com [172.21.40.24])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id PAA18112
	for <mmusic@ietf.org>; Wed, 31 Jul 2002 15:19:43 +0300 (EETDST)
Received: (from ppessi@localhost)
	by agni.research.nokia.com (8.11.6/8.11.2) id g6VCLhW17211;
	Wed, 31 Jul 2002 15:21:43 +0300
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Signaling FIR/Freeze in SIP
References: <B2518D608282D511BEA400508BBB9148EAA1E0@ACCORD-NTSRV3>
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <B2518D608282D511BEA400508BBB9148EAA1E0@ACCORD-NTSRV3>
Date: 31 Jul 2002 15:21:42 +0300
Message-ID: <pvado83x61.fsf@agni.research.nokia.com>
Lines: 10
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 31 Jul 2002 12:19:44.0199 (UTC) FILETIME=[8D990D70:01C2388C]
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

>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. 

	You can always include sender's timestamp in the request.

					Pekka

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



