[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [DNA-BOF] Charter statements for DAD optimization
Hi all
> > As Mobile IPv6 matures, the need for reliable and fast
> address allocation
> > and DAD scheme becomes critical to the goal of providing real-time
> > data service. It should be also useful for nodes that are not doing
> > movement detection, but get detached and attached. For any node
> > wishing to send/receive packets immediately after achieving a new
> > attachment, therefore, DAD optimization can be applicable.
>
> Maybe we need to talk about the issue with sending and receiving
> packets within the first second of connectivity, rather than
> starting with Mobile IPv6.
>
I assure that the meaning of "attachment" is a mobile node, incorrect ?
So, I guess it would be better to begin the DAD issue with MIPv6
simultaneously.
>
> There are some subsystems which need to send or receive packets,
> immediately after attaching to a new network. Currently DA
> specifications prevent transmission or reception from an
> address on the new link within the first second of attachment.
> Therefore, DAD optimization may be applicable.
>
> > DAD optimization may reveal two distinct strategies: Stateless DAD
> > and Stateful DAD, which may be used to develop new DAD schemes.
> > Such classification of DAD optimization schemes is
> determined according
> > to whether the DAD state of addresses is stores in a node
> until they are
> > allocated.
>
> I'm not sure that this needs to be in the charter at this stage,
> since it looks like it belongs either in the requirements space
> or solution space.
>
> I think that charter wants to provide an overview of
> problem drivers for the working group.
I guess we have to make a initial charter and milestone which
includes above issues in now. After then, we can add this issue
to the charter again. In order to discuss these issues, we have to
begin two kinds of work, problem statement and requirement
in advance.
Daniel