IETF Last Call Review of draft-ietf-raw-architecture-25
review-ietf-raw-architecture-25-secdir-lc-salz-2025-06-17-00

Request Review of draft-ietf-raw-architecture
Requested revision No specific revision (document currently at 27)
Type IETF Last Call Review
Team Security Area Directorate (secdir)
Deadline 2025-06-24
Requested 2025-06-10
Authors Pascal Thubert
I-D last updated 2025-07-09 (Latest revision 2025-07-07)
Completed reviews Rtgdir Early review of -21 by Acee Lindem (diff)
Genart IETF Last Call review of -25 by Behcet Sarikaya (diff)
Tsvart IETF Last Call review of -25 by Wesley Eddy (diff)
Secdir IETF Last Call review of -25 by Rich Salz (diff)
Opsdir IETF Last Call review of -25 by Giuseppe Fioccola (diff)
Intdir Telechat review of -25 by Brian Haberman (diff)
Iotdir Telechat review of -25 by Dave Thaler (diff)
Assignment Reviewer Rich Salz
State Completed
Request IETF Last Call review on draft-ietf-raw-architecture by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/OQ1e9MbiowjGNvoAvLN0RIIChSg
Reviewed revision 25 (document currently at 27)
Result Has nits
Completed 2025-06-17
review-ietf-raw-architecture-25-secdir-lc-salz-2025-06-17-00
I know nothing about routing, and wireless stuff, except to not trust the WiFi
in my local coffee shop.

The document gives a good overview about the need for and structure for
reliable wireless, and its layered approach.

I found Figure 1 confusing: the unlabeled lowercase "o" look like air bubbles
to me.  What are they and why are they relevant?

Similarly the "flakes of dandruff" in Figure 4 and the extra dots in Figure 8
and 10

Having griped about the diagrams, I must say that they are a tour de force of
ASCII art.

Focusing on the security considerations of Section 6 ...

"RAW uses all forms of diversity ..." do you mean transport?  Diversity as a
noun here seems wrong.

If Layer2 encryption prevents RAW component from promiscuous overhearing, what
is the next impact on the user?