[Live-devel] Patch request and question

[Derk-Jan Hartman]

http://www.dmn.tzi.org/ietf/mmusic/47/id/draft-sheedy-mmusic-rtsp-ext 
-00.txt

draft from nCUBE Corporation for their MediaCube VoD server platform  
(see extract below)

Basically they added ideas/formalization for Satellite and other types  
of transport common in the TV world.
Not such a bad idea actually, but also shows that RTSP definitely needs  
an official all encompasing RTSP2 standard, since atm everyone is just  
taking and implementing what they need and when they need it.

DJ

> 2.3  Profiles
>
>    Since AVP is intertwined with RTP, additional profiles are needed.
>    Enhancements to the "profile" file are:
>
>         H2221   The ITU H.222.1 standard for MPEG delivery over
>                 ATM [6].  The default lower transport is AAL5-SVC.
>
>         DVBC    The Digital Video Broadcasting - Cable standard
>                 [7].  The default lower transport is QAM.
>
>    The new syntax of "profile" would then be:
>
>         profile = "AVP" | "H2221" | "DVBC"
>
> 2.4  Transport/Profile/Lower-Transport Combinations
>
>    Only the following combinations of protocols, profiles, and lower
>    transports are meaningful:
>
>         MP2T/H2221/AAL5-PVC
>         MP2T/H2221/AAL5-SVC
>         MP2T/DVBC/QAM
>         MP2T/DVBC/ASI


On 20 jan 2005, at 22:22, Ross Finlayson wrote:

>
>> First, can someone please add the following line to the class
>> definition of MediaSubsession in MediaSession.hh to add access to the
>> rtp payload type:
>>
>> unsigned char rtpPayloadFormat() const { return fRTPPayloadFormat; }
>
> Are you sure you really need this?  If you've already called  
> "initiate()", you can also get this value by calling
>         subsession->rtpSource()->rtpPayloadFormat()
>
>> Second, I have run into a RTSP server that expects "M2TP/H2221/UDP" in
>> the SETUP message instead of the RAW/RAW/UDP like Kaseena uses to
>> setup a MPEG2-TS connection over UDP.  Unfortunately the capture I
>> have doesn't tell me what type of server this is.  Is anyone familiar
>> with it?
>
> I've never seen "M2TP/H2221/UDP" before.  As far as I can tell, it's  
> totally non-standard.  (I have no idea what "H2221" is supposed to  
> mean, or how such a stream differs from just raw MPEG-2 Transport over  
> UDP.)
>
>> Is it possible to interoperate with it without modifying the live  
>> stack?
>
> Probably not.
>
>
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel
>
>
---
Universiteit Twente
Derk-Jan Hartman (d.hartman at student.utwente dot nl)
http://home.student.utwente.nl/d.hartman