Rare project developers

[mc36 <>]

hi,
i went through your mpolka paper, first of all, congrats, nice work!
my first impression was that after the mod operation, it's basically do what 
bier
does, that is, we take the result, and interpret it as an outport bitmap, 
don't we?
and this is where we hit a limitation, depending on the size of crc is in use,
we can only describe 16 output ports, which is clearly not enough...
in freerouter, polka is bound to segment routing ids, and the result of the 
mod
is not a port but an sr index... my idea to overcome the above, what if we 
interpret
mpolka mod result as a bitmap to this index table? it then raises the 
limitation to
16 igp neighbors per core node, which is more friendly...
an other implementation idea is to use a different ethertype for mpolka to not
confuse the unicast or multicast packets on the wire as they'll differ on 
handling...
afterall, i found it feasible both for software and dataplane implementations,
so it could become a drop-in replacement for the current ip multicast over 
bier...
any opinion?
thanks,
cs