#82: Space optimization in NS/NA
--------------------------------+-------------------------------------------
Reporter: z...@… | Owner: z...@…
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: nd | Version:
Severity: - | Keywords:
--------------------------------+-------------------------------------------
The worst-case in nd-10 for NS/NA messages is currently:
6LN-6LR NS/NA: 56 bytes
6LR-6LBR NS/NA: 72 bytes
This ticket is to conclude whether we need to do anything about this or
not. Really only the multihop DAD NS/NA starts to be a problem as its ARO
also contains the registration address.
Possible solution from Erik to make multihop DAD NS/NA smaller, creating
new messages has drawbacks though:
We could create a NS' and NA' messages that do not contain the target
address and save 16 bytes for the NS/NA registrations. But that means a
new pair of message types and less interoperability with 4861.
--
Ticket URL: <http://trac.tools.ietf.org/wg/6lowpan/trac/ticket/82>
6lowpan <http://tools.ietf.org/6lowpan/>
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
