40 likes | 242 Views
FCAST: scalable object delivery for the ALC and NORM protocols draft-roca-rmt-newfcast-03. IETF 73 – Minneapolis, November 2008 Vincent Roca (INRIA) Brian Adamson (NRL). Status. Updated the I-D as suggested in IETF72: NORM: send meta-data in NORM_INFO messages
E N D
FCAST: scalable object delivery for the ALC and NORM protocolsdraft-roca-rmt-newfcast-03 IETF 73– Minneapolis, November 2008 Vincent Roca (INRIA) Brian Adamson (NRL)
Status • Updated the I-D as suggested in IETF72: • NORM: send meta-data in NORM_INFO messages • clarified the use of CIO (Carousel Instance Object) with an empty TOI list: • to say that all the previous objects have been removed from the carousel • to provide a heartbeat during idle periods • clarified that a receiver MUST NOT filter packets based on the CIO TOI list • plus various text improvements
Status… (cont’) • document is now almost finished • THE question: is there sufficient support to make it a WG Item? • not sure… • no answer on the mailing list after Brian’s call for opinion in September
Status… (cont’) • IOHO there are several advantages: • KISS design principle; • addresses simple use-cases in an efficient way (even if the result is more specialized than the FLUTE); • provides a CDP for NORM, which (additional benefit) is almost identical to FCAST/ALC; • bypasses known IPRs; • to summarize, IOHO: • FCAST/NORM is the only opportunity to have a standardized, interoperable CDP over NORM • taken individually points 1-4 are not sufficient to support FCAST/ALC, taken globally it’s more than enough