IETF Logo Mail Archive

Re: [MMUSIC] MMUSIC Draft Agenda for IETF 86

Mary Barnes <mary.ietf.barnes@gmail.com> Thu, 28 February 2013 14:21 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E4621F8745 for <mmusic@ietfa.amsl.com>; Thu, 28 Feb 2013 06:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level:
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGjuVaqTErWb for <mmusic@ietfa.amsl.com>; Thu, 28 Feb 2013 06:21:33 -0800 (PST)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id A901121F8621 for <mmusic@ietf.org>; Thu, 28 Feb 2013 06:21:33 -0800 (PST)
Received: by mail-qe0-f48.google.com with SMTP id 9so1427918qea.35 for <mmusic@ietf.org>; Thu, 28 Feb 2013 06:21:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=k+7DVgkPoZNORwAA56kT5clnUU0sxKqtoUEtttT0rQM=; b=fPiTI9Rp2e1Ro4F/a+UTcEX5rsO5zNjxbLuBD95zFE7bKO3uGiUHCWtr0V/pDeUNtA PhTyzuwJa9lPyMnkCLXaipLOvspK6EqP3gJvLJmff6M2i63XCl3InIAYzyghAs1k0hem qj/zYWMVDAtAdJjHdj3IqTYRP6HXKVcH/yrf4gOYYVDF6lTO3AZsk4ysEbcJMbq8GO7d bxiJLdYwlQFY/Nfe3Nlm2v1C+7v0LlXDGeJoDuYJeakc19blzYOdFSiuSMHTl6GZsDEG GOakrLdHMltUyxuRevhgSmveOlqsZLGUFuAAIYqC0hHbQkwxbt5sP01aFO12ktr3xegs 0e8w==
MIME-Version: 1.0
X-Received: by 10.224.193.200 with SMTP id dv8mr6412191qab.85.1362061286737; Thu, 28 Feb 2013 06:21:26 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Thu, 28 Feb 2013 06:21:26 -0800 (PST)
In-Reply-To: <CA+9kkMA8c38QSnhsV9UAObCBj+nB+TEOgFRTMyik5647=NjV4w@mail.gmail.com>
References: <512E6AEF.2050200@cisco.com> <CAHBDyN5ODjWnpjwNW=eLUcrXEYhpFrj920KFoHdzdMez8yp8fA@mail.gmail.com> <CA+9kkMA8c38QSnhsV9UAObCBj+nB+TEOgFRTMyik5647=NjV4w@mail.gmail.com>
Date: Thu, 28 Feb 2013 08:21:26 -0600
Message-ID: <CAHBDyN6YNw7EckX=adsJUztvvoQNhzt7Omd6Oa-HzzcoGGiqSw@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] MMUSIC Draft Agenda for IETF 86
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 14:21:35 -0000

On Wed, Feb 27, 2013 at 6:34 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> On Wed, Feb 27, 2013 at 3:53 PM, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>> I think it would be much clearer and more accurate if you would
>> separate out the documents under the "RTCWEB related drafts" into
>> those that are more general multi-stream related documents and those
>> that are RTCWEB specific - e.g., draft-jennings-rtcweb-plan-01 is
>> clearly an RTCWEB related draft.
>
> Actually, that document says this:
>
>    "The requirements listed here are a collection of requirements that
>    have come from WebRTC, CLUE, and the general community that uses RTP
>    for interactive communications based on Offer/Answer."
>
> So filename may not be the perfect indicator of author intent.
>
> Ted
[MB] Yeah - I had just assumed that was rtcweb only stuff.  But, that
just re-enforces my point that I don't believe this section should be
referenced as "RTCWEB related drafts" - either include CLUE in the
header or make the topic more general. I actually prefer the former as
I think it's really important for more of the CLUE participants to get
engaged in these discussions and understand that the decisions in
MMUSIC need CLUE input and may impact the overall CLUE solution. [/MB]
>
>> Whereas, many of the other drafts are
>> proposing solutions that might well be useful for other applications
>> such as CLUE.  I think it's really important that the MMUSIC WG keeps
>> in mind that RTCWEB requirements are not the only ones that need to be
>> considered in the context of the multi-stream work.
>>
>> Thanks,
>> Mary
>>
>> On Wed, Feb 27, 2013 at 2:22 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
>>> The MMUSIC draft agenda for IETF 86 has been posted at:
>>>
>>>     https://datatracker.ietf.org/meeting/86/agenda/mmusic/
>>>
>>> Please take a look and let us know if you have any questions or comments.
>>>
>>> Thanks
>>>
>>>     Ari & Flemming
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email