Skip to main content

Last Call Review of draft-ietf-spring-bfd-12
review-ietf-spring-bfd-12-tsvart-lc-trammell-2025-01-27-00

Request Review of draft-ietf-spring-bfd
Requested revision No specific revision (document currently at 12)
Type IETF Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2025-01-21
Requested 2025-01-06
Requested by Alvaro Retana
Authors Greg Mirsky , Jeff Tantsura , Ilya Varlashkin , Mach Chen , Jiang Wenying
I-D last updated 2025-03-17 (Latest revision 2024-09-10)
Completed reviews Rtgdir IETF Last Call review of -12 by Loa Andersson
Tsvart IETF Last Call review of -12 by Brian Trammell
Secdir IETF Last Call review of -12 by Stefan Santesson
Comments
This is a BFD-focused document; familiarity with the topic would be helpful.  If available, the reviewers who read draft-ietf-bfd-unaffiliated-echo would be ideal.
Assignment Reviewer Brian Trammell
State Completed
Request IETF Last Call review on draft-ietf-spring-bfd by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/T8UCWCZ5C4WYxqpsq91zWXf3pqM
Reviewed revision 12
Result Ready
Completed 2025-01-27
review-ietf-spring-bfd-12-tsvart-lc-trammell-2025-01-27-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

From a transport standpoint, this document is ready, as it presents no new
concerns with respect to the interaction between BFD and the transport layer. I
have not reviewed the document in detail for the correctness of the
interactions between BFD and SR, and will rely on the RTG and GEN reviews of
this document as to its utility to its intended audience.

(While the normal operating envelope of the BFD system of protocols is probably
RFC 8085 compliant by default, I continue to rely on trust that implementors of
routing-layer protocols encapsulated in UDP/IP will follow the guidance in
8085. But that concern is by no means specific to this specification.)