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

"Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com> Wed, 14 January 2015 08:55 UTC

Return-Path: <albrecht.schwarz@alcatel-lucent.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 DF58D1A6F96 for <mmusic@ietfa.amsl.com>; Wed, 14 Jan 2015 00:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 j9gS5Jz66ur7 for <mmusic@ietfa.amsl.com>; Wed, 14 Jan 2015 00:55:09 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4BFE1A1B3A for <mmusic@ietf.org>; Wed, 14 Jan 2015 00:55:08 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 937B43AC25804; Wed, 14 Jan 2015 08:55:04 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t0E8ssqI026453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 Jan 2015 09:55:04 +0100
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.75]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 14 Jan 2015 09:55:04 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Christian Groves <Christian.Groves@nteczone.com>, mmusic mailing list <mmusic@ietf.org>, Roni Even <ron.even.tlv@gmail.com>
Thread-Topic: [MMUSIC] Mod to draft-ietf-mmusic-rfc2326bis-40
Thread-Index: AQHQL59AiRulbR9t6U+xkzgsFTUxF5y/T9+A
Date: Wed, 14 Jan 2015 08:55:04 +0000
Message-ID: <786615F3A85DF44AA2A76164A71FE1AC38394F@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <54B5CFFC.7000904@nteczone.com>
In-Reply-To: <54B5CFFC.7000904@nteczone.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/oxXGtkQxuzJNegeqADqlVAomeM0>
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: Wed, 14 Jan 2015 08:55:16 -0000

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