1 note and 1 change...
Please note, FLUTE (§3.1) makes the TOI field mandatory (except for A flag packets with no payload), which basically mean ERT is only for objects/files in FLUTE and never for sessions. I am not sure that this is widely understood. Any problem with that? (Remember that ERT is now in seconds and not in milliseconds as before).
Also, in our proposed text §3 only mentions ERT for sessions (it should also mention objects) and §4.2 is fine (but a little confusing when you only think about FLUTE :). (§5.2.2 is correct and unambiguous).
I recommend this change to §3:
"the Expected Residual Time (ERT) conveys the amount of time the session will be continued for,..."
->
"the Expected Residual Time (ERT) conveys the amount of time either the session or transmission object will be continued for,..."
Cheers, rod.
>-----Original Message-----
>From: [email protected] [mailto:[email protected]] On
>Behalf Of ext Vincent Roca
>Sent: 31 January, 2006 17:18
>To: [email protected]
>Subject: [Rmt] EXT_TIME: a new HE for timing information in LCT
>
>Dear Mark et al.
>
>Here is the follow-up of a discussion we had in December on
>the possibility of defining a new header extension for LCT to
>carry several kinds of timing information.
>Cheers,
>
> Vincent / Toni / Rod
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.