IETF Logo Mail Archive

Re: [MMUSIC] Progressing draft-ietf-mmusic-rfc2326bis

"Ali C. Begen (abegen)" <abegen@cisco.com> Thu, 21 November 2013 10:38 UTC

Return-Path: <abegen@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 84A3C1ADFBC for <mmusic@ietfa.amsl.com>; Thu, 21 Nov 2013 02:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.026
X-Spam-Level:
X-Spam-Status: No, score=-15.026 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, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, 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 S0xTSlwhZzUq for <mmusic@ietfa.amsl.com>; Thu, 21 Nov 2013 02:38:29 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CD5011ADFB7 for <mmusic@ietf.org>; Thu, 21 Nov 2013 02:38:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1610; q=dns/txt; s=iport; t=1385030302; x=1386239902; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hAH+1Muxc3OOQ1q7UtWBpD2uqLqpXpwU2RhxrU/9IoA=; b=EcDY5WM29w+cKTYEsfblVtivn0QW5+d7v/JU4F+yaUrXIR6tCc7zQAHX 9OiT/4XxIM/wtRS9uw0I68Sb28I+RbAAwIj1if6KMHExiNkuzBDdjv2EY F+HPuV19T4i2DnOAZM1eel67hFyEkwwxBSHcmVIbIQ4G+AURMqmpZNz9A c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAEvijVKtJV2b/2dsb2JhbABZgmYhOFO8Lk6BHxZ0giUBAQEDAQEBATc0CwULAgEINhAnCyUCBA4Fh3sGAQzAWxePODMHgyCBEgOYEoEwkGCDKIIq
X-IronPort-AV: E=Sophos;i="4.93,743,1378857600"; d="scan'208";a="286577909"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 21 Nov 2013 10:38:22 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rALAcMCP003799 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Nov 2013 10:38:22 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 21 Nov 2013 04:38:21 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [MMUSIC] Progressing draft-ietf-mmusic-rfc2326bis
Thread-Index: AQHO5qPO/tHe3jytkUWT0R0uH9FYH5ov4uWA
Date: Thu, 21 Nov 2013 10:38:21 +0000
Message-ID: <0C52DDFC-9792-48BB-89AF-09FB022F5159@cisco.com>
References: <528DDF12.6030701@ericsson.com>
In-Reply-To: <528DDF12.6030701@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.255.39]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <398C46BC59CB3349ADED55958189C51E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mmusic@ietf.org>" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Progressing draft-ietf-mmusic-rfc2326bis
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: Thu, 21 Nov 2013 10:38:30 -0000

I am feeling terrible to say this as obviously much effort has gone into this document.

But to me, this spec is simply too late to have any chance to get deployed. Today there are lots of massive RTSP based streaming systems, yet they are obsolete and present lots of scalability and management issues. They also have lots of interop issues as not every vendor actually implemented RTSP in the same way.

Providers are not very eager to ditch these systems right a way. The ones that pull the trigger are mostly ditching RTSP altogether and moving towards http/cdn based streaming. Chances are quite slim for them to switch from RTSP 1.0 to RTSP 2.0. Needless to say, RTSP is a difficult protocol to both implement and deploy/manage.

Whether this should this draft from moving forward, that is a separate discussion, I think.



On Nov 21, 2013, at 12:23 PM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:

> Folks,
> 
> the IESG is reviewing the RTSP 2.0 spec below:
> 
> http://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/
> 
> Before progressing the draft, I have been asked by the IESG to check
> with the MMUSIC WG whether or not people still think it is worthwhile
> publishing this spec. In particular, they would like to know what level
> of deployment we can expect once the spec is published.
> 
> Your input is appreciated.
> 
> Thanks,
> 
> Gonzalo
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email