Re: Should FLUTE File Aggregation I-D be a working group item?

Magnus Westerlund <[email protected]>
Newsgroups gmane.ietf.rmt
Message-ID <[email protected]>
Hi,

To clarify my position and say that I don't care about specific solutions.

Yes I am talking about the physically aggregated objects in previous 
emails. I think I share the same concerns that Joerg Ott raised. There 
is no meaning to reinvent an exact duplication of tar or zip at FLUTE 
level. If one should do this in flute rather than simply write a 
recommendation that applications that have many small files should use a 
aggregated file container, then I think we need to provide some clear 
benefits, for example extraction of files from partially recovered 
aggregates. Simplified or more efficient recovery and handling of 
updates of the files part of the aggregate.

Simply using multi-party MIME does not really gain anything compared to 
tar or zip, then perhaps somewhat clear rules on how URI for files are 
constructed. For example multi-party MIME requires the capability to 
search the aggregate from start to end to find delimiters. This 
operation could be seriously hampered or even produce errors if the file 
is partial. In addition it is missing any integrity mechanism that I 
think is important if one tries to use partially repaired aggregates.

My proposal is to define a physical aggregation mechanism that primarily 
defines how one builds the source block from multiple files and then 
allows the receiver to perform the reverse operation to extract them 
from that aggregate also in cases when decode has not been completely 
successful. For large burst errors the loss for an aggregate may result 
in loss of one or several objects within the aggregate but still have 
parts of the aggregate for which all source symbols has been received.

So if one can find a way around the issues with backwards compatible 
FDT, sure no problem. However my view on this is that if we introduce a 
aggregation mechanism it will any way result in all receiver to support 
it, some further required extensions of the FDT will not cost us any 
interoperability.


Cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: [email protected]
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.