[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] [task #13455] Extend neighbhor discovery ti support 6Lo
Re: [lwip-devel] [task #13455] Extend neighbhor discovery ti support 6LoWPAN better.
Fri, 20 Feb 2015 16:49:34 +0000
I must also add that processing these in 6lowpan would mean that all neighbor
discovery procedures are processed by two modules nd6 and 6lowpan and there
will be duplication of tables as well.
This is not a system friendly approach.
From: Shingala, Krishna
Sent: 20. februar 2015 17:44
To: 'Sergio R. Caprile'; Simon Goldschmidt; address@hidden; address@hidden
Subject: RE: [task #13455] Extend neighbhor discovery ti support 6LoWPAN better.
I was thinking more on lines of introducing a netif function that is called by
the nd6 module once a prefix or the interface is added or invalidated.
This way nd6 module does not have to know how the prefix or context list was
"consumed" or if was consumed at all or not.
From: Sergio R. Caprile [mailto:address@hidden
Sent: 20. februar 2015 17:33
To: Simon Goldschmidt; Shingala, Krishna; address@hidden; address@hidden
Subject: [task #13455] Extend neighbhor discovery ti support 6LoWPAN better.
Follow-up Comment #2, task #13455 (project lwip):
My best guess is that the info gathered by nd6/mld6 should be available,
probably (desirable) by a callback function, so link-level protocols could use
it. Some way to detect changes is also desirable.
(IMHO,) I don't really think the netif but the 6LoWPAN implementation should
care about this. Point is: is there an open source 6LoWPAN implementation to
provide hooks/callbacks to ?
Should this task turn to "write a 6LoWPAN module" ? (perhaps followed by a ROLL
Reply to this item at:
Message sent via/by Savannah