Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bgpd: implement SendHoldTimer #11225

Merged
merged 1 commit into from
May 19, 2022

Conversation

eqvinox
Copy link
Contributor

@eqvinox eqvinox commented May 19, 2022

As described by https://www.ietf.org/archive/id/draft-spaghetti-idr-bgp-sendholdtimer-04.html

Since this replicates the HoldTime check on the receiver that is already part of the protocol, I do not believe it necessary to wait for IETF progress on this draft. It's just replicating an existing element of the protocol at the other side of the session.


This supersedes #8530 (it's also the "alternate suggestion" mentioned in #8530 (comment))

As described by
https://www.ietf.org/archive/id/draft-spaghetti-idr-bgp-sendholdtimer-04.html

Since this replicates the HoldTime check on the receiver that is already
part of the protocol, I do not believe it necessary to wait for IETF
progress on this draft.  It's just replicating an existing element of
the protocol at the other side of the session.

Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
@NetDEF-CI
Copy link
Collaborator

NetDEF-CI commented May 19, 2022

Continuous Integration Result: SUCCESSFUL

Continuous Integration Result: SUCCESSFUL

Congratulations, this patch passed basic tests

Tested-by: NetDEF / OpenSourceRouting.org CI System

CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-5478/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Warnings Generated during build:

Checkout code: Successful with additional warnings
Report for bgp_errors.c | 12 issues
===============================================
< WARNING: line over 80 characters
< #187: FILE: /tmp/f1-31676/bgp_errors.c:187:
< WARNING: line over 80 characters
< #188: FILE: /tmp/f1-31676/bgp_errors.c:188:
< WARNING: line over 80 characters
< #199: FILE: /tmp/f1-31676/bgp_errors.c:199:
< WARNING: line over 80 characters
< #491: FILE: /tmp/f1-31676/bgp_errors.c:491:
< WARNING: line over 80 characters
< #492: FILE: /tmp/f1-31676/bgp_errors.c:492:
< WARNING: line over 80 characters
< #493: FILE: /tmp/f1-31676/bgp_errors.c:493:

@NetDEF-CI
Copy link
Collaborator

Continuous Integration Result: SUCCESSFUL

Congratulations, this patch passed basic tests

Tested-by: NetDEF / OpenSourceRouting.org CI System

CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-5479/

This is a comment from an automated CI system.
For questions and feedback in regards to this CI system, please feel free to email
Martin Winter - mwinter (at) opensourcerouting.org.

Warnings Generated during build:

Checkout code: Successful with additional warnings
Report for bgp_errors.c | 12 issues
===============================================
< WARNING: line over 80 characters
< #187: FILE: /tmp/f1-19208/bgp_errors.c:187:
< WARNING: line over 80 characters
< #188: FILE: /tmp/f1-19208/bgp_errors.c:188:
< WARNING: line over 80 characters
< #199: FILE: /tmp/f1-19208/bgp_errors.c:199:
< WARNING: line over 80 characters
< #491: FILE: /tmp/f1-19208/bgp_errors.c:491:
< WARNING: line over 80 characters
< #492: FILE: /tmp/f1-19208/bgp_errors.c:492:
< WARNING: line over 80 characters
< #493: FILE: /tmp/f1-19208/bgp_errors.c:493:

@donaldsharp donaldsharp merged commit d37879b into FRRouting:master May 19, 2022
@eqvinox
Copy link
Contributor Author

eqvinox commented May 20, 2022

Well I'm an idiot and forgot to cover holdtime == 0 ... will fix later today.

@eqvinox eqvinox deleted the bgp-sendhold branch May 20, 2022 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants