[net2-wg] Collection (and more in general, multihop routing)

[henri dubois-ferriere]

On 15/12/05, Rodrigo Fonseca <rfonseca at cs.berkeley.edu> wrote:

[...]

> >
> > - Is it necessary for the app to know what protocol is implementing
> > the collection interface beneath it? (and hence, be aware of the
> > addressing scheme being used). Can't we just have
> >    command result_t collect(TOS_MsgPtr msg, uint16_t length);
> > and not specify the address (since this is message is for "collection" anyway.
>
> No, the application itself shouldn't need to, but some component that
> would abstract this away from the application can sit right above the
> networking layer and know about the specific addressing of the
> RoutingEngine being used.

Are this component (and the interfaces it exports) part of the
Collection interface(s) ?


henri

>
> >
> > - Similarly, my understanding of the 3rd-to last para is that if we
> > have multiple sinks, the address would be chosen by the app to
> > indicate up which tree to send a message. In other words, a component
> > above Collection must make the routing/collection decision of which
> > tree to use. Shouldn't this be transparent to the application?
> >
>
> Same as above.
>
> > - It might be nice to have some sort of Intercept interface to allow
> > in-network processing (if we have a clear enough idea of this..)
> >
>
> Sure. This can be present in the ForwardingEngine (and in the
> interface it provides) and have the same semantics as it has today. We
> can have intercept and snoop. This doesn't change the Routing Engine
> at all.
>
>
> Rodrigo.
>