Opened 8 years ago

Last modified 8 years ago

#28 new defect

Section 11: Track

Reported by: bernard_aboba@… Owned by: draft-ietf-rtcweb-rtp-usage@…
Priority: minor Milestone: milestone1
Component: rtp-usage Version: 1.0
Severity: Active WG Document Keywords:
Cc:

Description

A track is an
individual stream of media from any type of media source like a
microphone or a camera, but also conceptual sources, like a audio
mix or a video composition, are possible.

[BA] This doesn't seem quite right, if by "individual stream of media" you mean RTP Media Stream as defined in Section 3, since a track can be comprised of one or more channels.

Change History (1)

comment:1 Changed 8 years ago by bernard_aboba@…

[Magnus Westerlund]

A media source according to the above can be multi-channel audio mix or
capture. The point is that a track is an independent media with an
time-line.

However, this comment do point towards two open issues around this.

First, the use of terminology that should be aligned and help contribute
to the taxonomy draft discussion.

Secondly, that we need to take a serious look at the mapping between the
API and the RTP level. As noted by the TBD in section 11:

(tbd: This text needs to be improved and achieved consensus on.
Interim meeting in June 2012 shows large differences in opinions.)

Note: See TracTickets for help on using tickets.