IETF
xrblock@jabber.ietf.org
Monday, July 29, 2013< ^ >
Room Configuration
Room Occupants

GMT+0
[13:09:27] shidaschubert joins the room
[13:10:23] alanclark@comm.unicate.me joins the room
[13:10:43] Jonathan Lennox joins the room
[13:36:04] <alanclark@comm.unicate.me> The clean approach is to move the block, the expedient approach is not to - my vote would be to move the block
[13:40:09] <alanclark@comm.unicate.me> Implementors sometimes feel that they have to implement all the blocks in a draft - so it would be a burden to have to implement RLE if you only wanted bytes discarded
[13:40:21] <alanclark@comm.unicate.me> Alan's hand - to move the block
[13:42:36] <alanclark@comm.unicate.me> mplementors sometimes feel that they have to implement all the blocks in a draft - so it would be a burden to have to implement RLE if you only wanted bytes discarded
[13:44:40] <alanclark@comm.unicate.me> Those writing the requirements may not be smart but they generally have the check book
[13:45:21] <alanclark@comm.unicate.me> Three drafts would be better than keeping discarded bytes and RLE together IMHO
[13:46:49] <alanclark@comm.unicate.me> It is a "requirement bullet point" and not a filename
[13:48:38] <alanclark@comm.unicate.me> Which is ok IF the blocks are related closely
[13:50:13] <alanclark@comm.unicate.me> Alan's hand - split the draft
[13:51:51] <alanclark@comm.unicate.me> Alan's vote - opposed to keeping two blocks together
[14:04:53] <alanclark@comm.unicate.me> Don't see why we would need a WEBRTC/RTCWEB draft that would effectively list the XR BLOCK blocks - RTCWEB is essentially the same as other RTP applications and the use cases would be the same. It "may" be useful to have a non RTCWEB specific user guide to xr blocks to explain what they are intended for and how to use them.
[14:05:27] <alanclark@comm.unicate.me> Plus - if a review of RTCWEB showed that other new metrics were needed then XRBLOCK could define those.
[14:06:38] <alanclark@comm.unicate.me> Yes - some do have IPR such as concealed loss metrics
[14:13:16] <alanclark@comm.unicate.me> The block needs to identify the MPEG transport stream that the TR101290 metrics related to  - SSRC/PID1, SSRC/PID2….
[14:14:11] <alanclark@comm.unicate.me> Need to either have a block that defines SSRC and PID or a block that defines SSRC and then has PID specific sub-blocks
[14:16:15] <alanclark@comm.unicate.me> Yes - I'm familiar
[14:16:34] <alanclark@comm.unicate.me> TR101290 metrics are useful but does need PID
[14:18:22] alanclark@comm.unicate.me leaves the room
[14:18:25] Jonathan Lennox leaves the room
[14:18:27] shidaschubert leaves the room
[17:03:32] shidaschubert joins the room
[17:03:57] shidaschubert leaves the room