[Roll] DAO-Projection and new MOPs

[Rahul Jadhav <[e-mail]>]

Hi Pascal, WG,

This mail is regarding concern on how to handle MOP exhaustion in DIO. With
AODV-RPL and DAO-projection we would essentially use up all the possible
MOP values. This point was raised in ROLL-sessions before but we haven't
really discussed this on ML.

To begin with, I was wondering, do we really need new MOPs for
dao-projection?
Can we handle dao-projection as something which can be incrementally added
to existing MOPs? For e.g. if the network is established in NS-MOP
(non-storing MOP=1) then we can use P-DAO to project routes down the
network and if the destination legacy node does not understand P-DAO then
it should send a negative ACK for the DAO. Problem is, right now i don't
see how legacy nodes (who dont understand new RPO options) can distinguish
between P-DAO and normal DAO.
As i understand, the new MOP is required because of this new mandatory
handling required for P-DAOs. Is it possible to have P-DAO such that legacy
nodes generate negative ACK if they cannot handle it?

Also currently we have two types of storing MOPs (in 6550), one with
multicast (MOP=3) and one without multicast (MOP=2). DAO-Projection defines
only one storing MOP. Thus as i understand in DAO-Projection draft the
storing MOP has multicast support by default. Is this ok to assume?

Regards,
Rahul