Re: [AVTCORE] Benjamin Kaduk's Discuss on draft-ietf-payload-tsvcis-03: (with DISCUSS and COMMENT)

[Benjamin Kaduk <[e-mail]>]

On Sun, Oct 06, 2019 at 06:08:51AM +0000, Roni Even (A) wrote:
> Hi,
> About the reference to TSVCIS.
> The RTP payload is about how to encapsulate the payload in an RTP packet. The objective is to define how an RTP stack can insert the tsvcis frames and  extract the tsvcis frames from the RTP packet. Typically it is not required to understand the payload structure in order to be able to perform the encapsulation.
> This is why the reference to the payload is Informational and we did not require to have it publically available.  If there is a need to understand the payload itself for the encapsulating than we need more information in the RTP payload specification and a publically available normative reference. I think this is not the case here

I for the most part agree with you, but the current draft is saying that
TSVCIS is going to give the encoder "some parameters" and the draft
specifies a way to pack those parameters into a byte encoding.  We don't
have enough information to decode that encoding without some canonical
ordered list of parmeters that gives a mapping from encoded bytestream
length to which parameters are to be extracted.  It feels like something
best done as "TSVCIS gives us an opaque octet string that we blindly
transport", but that doesn't seem to be the case.

-Ben