Registration of media type application/iptv_rtsp
Roni Even
Even.roni at huawei.com
Fri Jan 22 00:11:32 CET 2010
Hi,
The registration template looks OK.
I looked at the specification ETSI 183 063 and I am not sure about the
usage there
It has m = application 9 tcp iptv_rtsp
I think it should have been m = application 9 tcp/iptv_rtsp *
I also saw an optional parameter "h-session" which in my view should have
been in the registration request
Roni Even
From: ietf-types-bounces at alvestrand.no
[mailto:ietf-types-bounces at alvestrand.no] On Behalf Of Miguel Angel Reina
Ortega
Sent: Friday, December 04, 2009 12:22 PM
To: ietf-types at iana.org; iesg at ietf.org
Subject: Registration of media type application/iptv_rtsp
Type name:
application
Subtype name:
Standards tree - iptv_rtsp
Required parameters:
No parameters
Optional parameters:
No parameters
Encoding considerations:
8 bit text (this media type may require encoding on transports not
capable of handling 8 bit text)
The iptv_rtsp media type is intended to be a media descriptor
for an RTSP content control channel. The encoding of the RTSP
protocol is specified in RFC 2326 - Real Time Streaming Protocol
(RTSP).
Security considerations:
The same security considerations apply as for the RTSP protocol,
which is specified in RFC 2326 - Real Time Streaming Protocol
(RTSP).
Interoperability considerations:
Interoperability of the RTSP protocol is specified in RFC 2326 -
Real Time Streaming Protocol (RTSP).
Published specification:
ETSI TS 183 063 v2.4.2 (2009-06). Available at
http://pda.etsi.org/pda/queryform.asp
Applications that use this media type:
The iptv_rtsp media type is intended to be a media descriptor
for an RTSP content control channel. An RTSP content control
channel is established using SIP and the SDP offer/answer model as
described in ETSI TS 183 063 Telecommunications and Internet
Converged Services and Protocols for Advanced Networking (TISPAN);
IMS-based IPTV Stage 3 Specification", ETSI TS 183 063 v2.4.2
(2009-06).
Additional information:
Magic number(s):
There is no single string that is always present.
File extension(s):
No specific file extension is recommended for this type.
Macintosh file type code(s):
No specific Macintosh file type codes are recommended for this
type.
Person & email address to contact for further information:
MiguelAngel.ReinaOrtega at etsi.org on behalf of ETSI
Intended usage:
COMMON
Restrictions on usage:
No restrictions apply.
Authors:
the rapporteur (zhouzhipeng <zhouzp at HUAWEI.COM>)
The WG chairman (Raymond.forbes at ericsson.com)
Change controller:
the ETSI TO (sonia.compans at etsi.org)
-------------------------------------------
Miguel A. Reina Ortega
Technical Expert
Centre for Testing and Interoperability (CTI)
tel: +33 (0)4 92 94 43 49
mob: +33 (0)6 76 73 60 99
web: <http://www.etsi.org/> http://www.etsi.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20100122/86d63b10/attachment.htm
More information about the Ietf-types
mailing list