With in 3GPP work (and fed into DVB) we were hard put to come up with a reason to start allocating TOI values to files from anything but "1" (obviously not "0" with that being reserved for FDT Instances). Similarly, we could not invent any good reason to have any progressive allocation other than using incremental values.
Hence restricting FLUTE to work in this way (as has been done for 3GPP) would be a simplification with the added bonus of providing an indirect versioning (using TOI value) for any particular fileuri value (i.e. any particular file).
Note, this applies to allocations of values (i.e. server-end), although it would not require a server the send in TOI order (hence there's no difference in what a client would expect regarding reception of TOI order).
If anyone has a reason why either of these things are unwise please speak up to prevent me recommending them for the FLUTEbis:
- start TOI value allocations for FLUTE at "1"
- for each subsequent TOI allocation use the previous value plus 1 (i.e. increment by 1)
Mike raised a similar issue in his email "[Rmt] RE: Comments to draft-ietf-rmt-fec-bb-revised-00.txt" last Wednesday which hinted at a use case for allocating any initial value (and then incrementing by one) - any details on the use case?
Cheers, 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.