#59: Self-sufficient mechanism and cohabitation with RFC4861 or 3122
--------------------------------+-------------------------------------------
Reporter: z...@… | Owner: z...@…
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: nd | Version:
Severity: - | Keywords:
--------------------------------+-------------------------------------------
- Clarify that the specification is both required and sufficient for
LoWPAN operation
- State that cohabitation with RFC4861 and 3122 is possible briefly.
The specification of when/why to use these in a LoWPAN is out of
scope.
- Any use of 4861 with 4944 without this specification is NOT
RECOMMENDED, but certainly possible in 2-node and full-multicast
mesh-under. (That's why we say "updates 4944".)
- Eliminate dependency on RFC4861 wherever possible. Make this a
white-list specification.
- Organize more based on functionality rather than node role. Node
Registration gets its own section with subsections for SAA, DAD, AR
and NUD.
- Make it clear that this draft optimizes the host-router interface.
--
Ticket URL: <http://trac.tools.ietf.org/wg/6lowpan/trac/ticket/59>
6lowpan <http://tools.ietf.org/6lowpan/>
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
