[Last-Call] UDP Guidelines and draft-ietf-bfd-unaffiliated-echo-12

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a few comments, but i am not a routing expert, so I'm maybe misisng context on the intended use, and why this is a good thing to allow....

I did not find a description of why this was needed.

Whereas I understand BFD is a protocol setup between two endpoints, this draft appears to describe a version without the setup, which makes it a UDP-based request/response protocol in itself. That brings questions about how it addresses RFC 8085 (also known as BCP 145), with respect to the UDP Usage? This does not appear to be explained.

Can this be misused as a DoS vector?
 
GTSM, aka  RFC 5082, isn't mentioned or used, but it seems to be relevent? If not, then the mechanism used to protect from forwarding needs more explanation.

Best wishes,
Gorry

P.S. I didn't understand this:  "Unaffiliated BFD Echo requires the remote device to loop Unaffiliated
   BFD Echo packets.", so the packetw ould fail an RPF check to the source - why is this good?
-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux