Re: [Uri-review] In WG last call review of URI Schemes rtsp, rtsps and rtspu
Magnus Westerlund <magnus.westerlund@ericsson.com> Tue, 08 May 2012 11:48 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CD821F84F0 for <uri-review@ietfa.amsl.com>; Tue, 8 May 2012 04:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.137
X-Spam-Level:
X-Spam-Status: No, score=-106.137 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bfI8DOLqorA for <uri-review@ietfa.amsl.com>; Tue, 8 May 2012 04:48:10 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7D24521F84B5 for <uri-review@ietf.org>; Tue, 8 May 2012 04:48:10 -0700 (PDT)
X-AuditID: c1b4fb25-b7b09ae000007d0f-c2-4fa907f956dd
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 57.B6.32015.9F709AF4; Tue, 8 May 2012 13:48:09 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.213.0; Tue, 8 May 2012 13:48:08 +0200
Message-ID: <4FA907F7.3000306@ericsson.com>
Date: Tue, 08 May 2012 13:48:07 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4F99665D.8060404@ericsson.com> <CA+9kkMAvr6eXHzB_HMVgGqBHpUpeuh-mrWRP6-Ap0w3SZLvV-Q@mail.gmail.com> <4FA13522.6020103@ericsson.com> <C68CB012D9182D408CED7B884F441D4D194AD547DE@nambxv01a.corp.adobe.com> <4FA8EB2E.8070609@ericsson.com> <4FA8F231.90407@gmx.de>
In-Reply-To: <4FA8F231.90407@gmx.de>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Ted Hardie <ted.ietf@gmail.com>, "uri-review@ietf.org" <uri-review@ietf.org>, "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: Re: [Uri-review] In WG last call review of URI Schemes rtsp, rtsps and rtspu
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 11:48:11 -0000
On 2012-05-08 12:15, Julian Reschke wrote: > On 2012-05-08 11:45, Magnus Westerlund wrote: >> Larry, >> >> Can you please clarify something for me. What I have done is that I have >> made it clear in the URI syntax that the fragment ABNF construct from >> RFC 3986 MAY occur in an valid rtsp URI syntax. Are you saying that this >> is not the right thing to do? How could I then indicate the appropriate > > It's pointless, as a URI scheme definition can't override RFC 3986, and > parsing of scheme name and fragment are already defined by RFC 3986. > > Optimally, a new scheme definition just defines the scheme-specific part. > >> syntax when the fragment identifier occur with the URI scheme being >> defined? Can't I even say that fragments is not allowed for a scheme? > > No. > >> This appear to be the case if one would implicitly define the fragment >> in an URI scheme. > > Exactly :-) > But, then what I have done isn't wrong either as I haven't override the rules for fragment, only made it clear how they interface with the URI definition. From my perspective I can remove the fragment syntax definition, but I would instead at least explicitly call out that fragments may occur following RFC 3986 syntax. Personally I don't see that as being better. Secondly, when we are on this topic. Can someone answer how you determine the media type for an rtsp URI? RTSP URI points to resources that can provide controlled playback of the resource using any number of media types in form of RTP payloads formats depending on what is suitable for the resource. In fact from issuing an PLAY request on an audio only resource you still can receive a media stream where the format it is encoded my actually change during the playback operation. To be clear I don't plan to define a fragment handling format for RTSP URIs, but there has been discussion in the past the desire has been to do something that is media format agnostic. The goal has been to have an uri where you basically say: Play this resource from 5 min 10 seconds until 9 min 37 seconds. The proposal is in this 2005 draft. http://tools.ietf.org/html/draft-pfeiffer-temporal-fragments-03 But, if the above really isn't possible the question of fragments for RTSP is really mote and is just a waste of time to discuss. Cheers Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [Uri-review] In WG last call review of URI Scheme… Magnus Westerlund
- Re: [Uri-review] In WG last call review of URI Sc… Ted Hardie
- Re: [Uri-review] In WG last call review of URI Sc… Magnus Westerlund
- Re: [Uri-review] In WG last call review of URI Sc… Larry Masinter
- Re: [Uri-review] In WG last call review of URI Sc… Magnus Westerlund
- Re: [Uri-review] In WG last call review of URI Sc… Julian Reschke
- Re: [Uri-review] In WG last call review of URI Sc… Magnus Westerlund
- Re: [Uri-review] In WG last call review of URI Sc… Larry Masinter
- Re: [Uri-review] In WG last call review of URI Sc… Julian Reschke
- Re: [Uri-review] In WG last call review of URI Sc… Ted Hardie
- Re: [Uri-review] In WG last call review of URI Sc… Larry Masinter
- Re: [Uri-review] In WG last call review of URI Sc… Julian Reschke
- Re: [Uri-review] In WG last call review of URI Sc… Ted Hardie
- Re: [Uri-review] In WG last call review of URI Sc… Roy T. Fielding
- Re: [Uri-review] In WG last call review of URI Sc… Ted Hardie
- Re: [Uri-review] In WG last call review of URI Sc… Martin J. Dürst
- Re: [Uri-review] In WG last call review of URI Sc… Roy T. Fielding
- Re: [Uri-review] In WG last call review of URI Sc… Martin J. Dürst
- Re: [Uri-review] In WG last call review of URI Sc… Ted Hardie
- Re: [Uri-review] In WG last call review of URI Sc… Roy T. Fielding
- Re: [Uri-review] In WG last call review of URI Sc… Martin J. Dürst