Last Call Review of draft-ietf-nvo3-geneve-oam-13
review-ietf-nvo3-geneve-oam-13-secdir-lc-nir-2024-12-22-00
| Request | Review of | draft-ietf-nvo3-geneve-oam |
|---|---|---|
| Requested revision | No specific revision (document currently at 16) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2024-12-16 | |
| Requested | 2024-12-02 | |
| Authors | Greg Mirsky , Sami Boutros , David L. Black , Santosh Pallagatti | |
| I-D last updated | 2025-04-22 (Latest revision 2025-02-26) | |
| Completed reviews |
Rtgdir Early review of -04
by Himanshu C. Shah
(diff)
Rtgdir Early review of -11 by Stig Venaas (diff) Genart Early review of -10 by Paul Kyzivat (diff) Secdir IETF Last Call review of -13 by Yoav Nir (diff) Intdir IETF Last Call review of -14 by Tim Chown (diff) Opsdir Telechat review of -13 by Tony Li (diff) |
|
| Assignment | Reviewer | Yoav Nir |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-nvo3-geneve-oam by Security Area Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/secdir/1l2SJR1QUZ2ENAcxvVrbKlbIaNI | |
| Reviewed revision | 13 (document currently at 16) | |
| Result | Ready | |
| Completed | 2024-12-22 |
review-ietf-nvo3-geneve-oam-13-secdir-lc-nir-2024-12-22-00
This document's security considerations are mostly by-reference to the original Geneve document (RFC 8926). The OAM traffic is in-band, so follows the same path as the regular traffic, and the only additional security mechanism is the RFC 5082 (Generic TTL Security mechanism), which just means dropping any packet whose TTL is not 255 - not sent from an adjacent node. Anyway, this seems sufficient for what this draft does.