-
Notifications
You must be signed in to change notification settings - Fork 21
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
Recommend that PATH_ABANDON should be retransmitted on another path #470
Comments
The feedback from Dublin was quite clear: a bunch of these strategies are still research issues. We should generally not try to solve them as part of the draft, because it makes the whole draft look like a research project. And we should certainly not make normative statements that implementation SHOULD or MUST implement a variant of an algorithm for which research is still ongoing. |
Actually we already have this sentence in section 3.3 (Path Closure):
I would maybe just like to add one more sentence here to make the case above a bit more clear like this:
|
I created PR #473 to see the proposed change in context. |
I closed #473 but based on the discussion there created PR #477. This new PR is a slight rephrasing of the existing sentence but makes it now clear that it is generally recommend to send the PATH_ABANDON on another path. That was the take-away for me from the discussion on #473. Please let me know if you agree to that or not! |
Maybe this is obvious but if a path_abandon frame gets lost, this will usually lead to a PTO. In this case the path is highly likely to be already broken and I probably should retransmit the path_abandon frame on another path to actually be able to close the path. We already say in the new "handling PTO" section that it makes sense to generally retransmit on another path. However, maybe we should actually say this using normative language (SHOULD or MUST?) in the path closure section in case of the path_abandon frame?
The text was updated successfully, but these errors were encountered: