#97: IESG comment #6 - Mechanism for securing routing data
------------------------------------+---------------------------------------
Reporter: carle...@… | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: routing-requirements | Version:
Severity: - | Keywords:
------------------------------------+---------------------------------------
According to RFC 4919:
IEEE 802.15.4 mandates link-layer security based on AES
so why isn't this need to define /taking in to account a MUST?
In a nutshell it's not clear to me how the routing data is going to be
secured. MUST it be the IEEE mechanism, can it be something else that is
WG defined, or can it be something already defined elsewhere in the IETF?
--
Ticket URL: <http://tools.ietf.org/wg/6lowpan/trac/ticket/97>
6lowpan <http://tools.ietf.org/6lowpan/>
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
