#88: Space optimization in RS/RA
--------------------------------+-------------------------------------------
Reporter: z...@… | Owner: z...@…
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: nd | Version:
Severity: - | Keywords:
--------------------------------+-------------------------------------------
Several space optimizations have been suggested for the information
carried in RAs, in particular the combination of ABRO, PIO and 6CO is
getting very large (already requires fragmentation). Can we avoid or
minimize fragmentation by optimizing these somewhat? Current suggestions
on the table:
1. PIO in classic ND only allows to set option length to 4 and there
are 8 bytes you don’t use. Could we set it to 3 to save 8 bytes? The
problem with this suggestion is that the last 8 bytes are used with the R
bit is set.
2. Allowing for a default CID=0 of some kind by usigng information in the
PIO and/or ABRO options. Currently the prefix is carried in all 3 options:
ABRO, PIO and 6CO. How to reduce the overlap?
3. Colin suggested ICMPv6/ND optimization using HC next-header
compression. Would it require us to add a work item for that in a future
charter?
--
Ticket URL: <http://wiki.tools.ietf.org/wg/6lowpan/trac/ticket/88>
6lowpan <http://tools.ietf.org/6lowpan/>
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
