Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-14 Thread Jeffrey Haas
Christian, Reshad, > On Jun 13, 2024, at 12:41 PM, Christian Huitema wrote: > On 6/13/2024 8:46 AM, Reshad Rahman wrote: >> Was there any consideration to change the procedure to increment the >> loss count so that if we get 1-3-2-4, we increment loss count when we >> receive 3 (2 is deemed l

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-13 Thread Christian Huitema
On 6/13/2024 8:46 AM, Reshad Rahman wrote: Chiming in late. Inline. On Monday, June 10, 2024, 12:22:13 PM EDT, Jeffrey Haas wrote: Christian, Thanks for your review.  Some of my comments will overlap those from Alan. On Fri, Jun 07, 2024 at 09:54:57PM -0700, Christian Huitema

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-13 Thread Reshad Rahman
Chiming in late. Inline. On Monday, June 10, 2024, 12:22:13 PM EDT, Jeffrey Haas wrote: Christian, Thanks for your review.  Some of my comments will overlap those from Alan. On Fri, Jun 07, 2024 at 09:54:57PM -0700, Christian Huitema via Datatracker wrote: > The authentication sequen

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-11 Thread Jeffrey Haas
Christian, On Tue, Jun 11, 2024 at 11:36:13AM -0700, Christian Huitema wrote: > On 6/11/2024 7:03 AM, Jeffrey Haas wrote: > >And again, sequence rollover for replay has the presumption that you're > >using exactly the same contents for the BFD PDU. The procedures for > >randomizing the Discrimina

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-11 Thread Christian Huitema
On 6/11/2024 7:03 AM, Jeffrey Haas wrote: And again, sequence rollover for replay has the presumption that you're using exactly the same contents for the BFD PDU. The procedures for randomizing the Discriminators provide an appropriate nonce to prevent replay since the authentication data is

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-11 Thread Jeffrey Haas
Christian, On Mon, Jun 10, 2024 at 05:11:17PM -0700, Christian Huitema wrote: > On 6/10/2024 9:22 AM, Jeffrey Haas wrote: > >For our authentication purposes, without the presence of some sort of > >computed digest across the packet, NULL authentication means that an active > >attacker can knock th

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-10 Thread Christian Huitema
On 6/10/2024 9:22 AM, Jeffrey Haas wrote: ... In RFC 5880, the specification of Meticulous Keyed MD5 addresses both number rollover and out of order delivery. The same text is repeated for meticulous MD5 and meticulous SHA1: ... if the sequence number lies outside of the range o

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-10 Thread Jeffrey Haas
Christian, Thanks for your review. Some of my comments will overlap those from Alan. On Fri, Jun 07, 2024 at 09:54:57PM -0700, Christian Huitema via Datatracker wrote: > The authentication sequence number is a 32 bit field. Such numbers can roll > over, either after a long duration session or d

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-08 Thread Christian Huitema
Thanks for the comments, Alan. I understand that the main use of BFD is between directly connected nodes, but then RFC 5880 says: BFD can provide failure detection on any kind of path between systems, including direct physical links, virtual circuits, tunnels, MPLS Label Switched Path

Re: Secdir early review of draft-ietf-bfd-stability-13

2024-06-08 Thread Alan DeKok
(removing secdir) The security analysis is perhaps simplified a bit by understanding the limited use-case for BFD. From the introduction to RFC 5880: The goal of Bidirectional Forwarding Detection (BFD) is to provide low-overhead, short-duration detection of failures in the path be