Re: [MMUSIC] Mod to draft-ietf-mmusic-rfc2326bis-40

Flemming Andreasen <fandreas@cisco.com> Tue, 20 January 2015 21:32 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5A1A001C for <mmusic@ietfa.amsl.com>; Tue, 20 Jan 2015 13:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJPyWQVud9Wn for <mmusic@ietfa.amsl.com>; Tue, 20 Jan 2015 13:32:28 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C18C81A0012 for <mmusic@ietf.org>; Tue, 20 Jan 2015 13:32:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2783; q=dns/txt; s=iport; t=1421789548; x=1422999148; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=T4YXQhiZAbuFpm84ADqX79IsRaSpyd8rlF53a3xcPjM=; b=Qk0FYzMQmm8aauLJmHNs5x72xmdVPdooGkRhOOkneyyR7yC3vuNE+eYN oUp/JS5clgU2OpxE86oPr5jXSgCu1BdPMJeBSe7+wyQ5BTXZYTn5h3j1i 0X0D5SwZGrCaX6lg5CeWZJr9QwkPhMEBlBQ07DUIo3cwiG0ciuzwq3/xT M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AooUAO7IvlStJV2a/2dsb2JhbABbgwZSWLNpAQEBAwUBd5FGCoUnSgKBKUMBAQEBAX2EDAEBAQQBAQE1NgoNBAsRBAEBAQkWCAcJAwIBAgEVHwkIBgEMBgIBAYgoDdEGAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSGBYl7BoQjAQSJdYgrhVCGL4t7IoF/H4FuIDGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,437,1418083200"; d="scan'208";a="115597384"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP; 20 Jan 2015 21:32:27 +0000
Received: from [10.98.149.196] (bxb-fandreas-8813.cisco.com [10.98.149.196]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t0KLWQQ3016305; Tue, 20 Jan 2015 21:32:27 GMT
Message-ID: <54BEC96A.4090504@cisco.com>
Date: Tue, 20 Jan 2015 16:32:26 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>, Christian Groves <Christian.Groves@nteczone.com>, mmusic mailing list <mmusic@ietf.org>, Roni Even <ron.even.tlv@gmail.com>
References: <54B5CFFC.7000904@nteczone.com> <786615F3A85DF44AA2A76164A71FE1AC38394F@FR711WXCHMBA03.zeu.alcatel-lucent.com>
In-Reply-To: <786615F3A85DF44AA2A76164A71FE1AC38394F@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RW0IU1rtgx4-7y0BRbNGFWjiD6M>
Subject: Re: [MMUSIC] Mod to draft-ietf-mmusic-rfc2326bis-40
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 20 Jan 2015 21:32:31 -0000

We'll probably need to hear from Magnus as well (since he's the main 
author). I'm not sure if he is back from leave yet or not.

Thanks

-- Flemming

On 1/14/15 3:55 AM, Schwarz, Albrecht (Albrecht) wrote:
> No objections from my side because the requirement as such is still sufficiently covered.
> Thus, would support that change proposal.
> -Albrecht
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christian Groves
> Sent: Mittwoch, 14. Januar 2015 03:10
> To: mmusic mailing list; Roni Even
> Subject: [MMUSIC] Mod to draft-ietf-mmusic-rfc2326bis-40
>
> Hello,
>
> draft-ietf-mmusic-rfc2326bis-40
> <https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/> has been in state MISSREF for some time now. See below:
>
> 2014-02-11    draft-ietf-mmusic-rfc2326bis-40.txt [C214]
> MISSREF*R(1G)
> REF    draft-ietf-avtcore-rtp-circuit-breakers    NOT-RECEIVED
>       draft-ietf-mmusic-rtsp-nat    IN-QUEUE
> H. Schulzrinne, A. Rao, R. Lanphier, M. Westerlund, M. Stiemerling, Ed.
> "Real Time Streaming Protocol 2.0 (RTSP)"
> Bytes: 764018
> Working Group: Multiparty Multimedia Session Control
>
> There is still a dependency on draft-ietf-avtcore-rtp-circuit breakers which is holding up an RFC number being assigned. My understanding is that it could be quite awhile before the circuit breakers draft is approved.
>
> There's only one reference to the circuit breakers draft in C.1.6.3 "Bit-rate adaption", i.e.
>      To ensure that the implementation's adaptation mechanism has a well
>      defined outer envelope, all implementations using a non-congestion
>      controlled unicast transport protocol, like UDP, MUST implement
>      Multimedia Congestion Control: Circuit Breakers for Unicast RTP
>      Sessions [I-D.ietf-avtcore-rtp-circuit-breakers].
>
> I wondering if it would be possible to change this slightly so that the circuit breakers draft becomes informative whilst still keeping the congestion control requirement as a MUST? i.e.
> "... all implementations using a non-congestion controlled unicast transport protocol, like UDP, MUST implement multimedia congestion control. For example: by utilising the mechanism defined by "Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions [I-D.ietf-avtcore-rtp-circuit-breakers]."
>
> This would mean that RTSP2.0 could finally become an RFC.
>
> Would this be possible?
>
> Regards,
> Christian
>
>
> _______________________________________________
> 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
> .
>