Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Directorate Review #18

Open
inesrob opened this issue Feb 29, 2024 · 0 comments
Open

Security Directorate Review #18

inesrob opened this issue Feb 29, 2024 · 0 comments
Milestone

Comments

@inesrob
Copy link
Contributor

inesrob commented Feb 29, 2024

Source: https://datatracker.ietf.org/doc/review-ietf-roll-enrollment-priority-10-secdir-early-shekh-yusef-2024-01-29/

"The following is a quote from the Security Consideration section of the draft:
"The use of layer-2 or layer-3 security for RPL control messages prevents the
two aforementioned attacks, by preventing malicious nodes from becoming part of
the control plane."

The following quote is from RFC7416, section 7.1.2:
"A number of deployments, such as [ZigBeeIP] specify no Layer 3 (L3) / RPL
encryption or authentication and rely upon similar security at Layer 2 (L2).
These networks are immune to outside wiretapping attacks but are vulnerable to
passive (and active) routing attacks through compromises of nodes (see Section
8.2)."

The draft seems to suggest layer-2 security might be sufficient protection,
while RFC7416 seems to suggest that solely relying on layer-2 might not be
enough.

RFC7416, section 8.2 states:
"RPL provides for asymmetric authentication at L3 of the RPL Control Message
carrying the DIO, and this may be warranted in some deployments."

I feel that this should be discussed here to make it clear that in some
deployments, layer-2 by itself might not be sufficient and the use of
asymmetric authentication at L3 might be required."

@ariskou ariskou added this to the IESG milestone Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants