You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an update to the F3 FIP outlining the additions/changes related to the protocol changes as a result of the learnings from nv24 passive testing that will be include in nv25. The set of changes that should be included are:
TBD - fill this in
Why Important
There have been non-trivial changes to F3 based on the learnings from nv24. These should make them back to the FIP for visibility to the community, especially since these changes will be shipped as part of nv25.
While we don't expect anyone to care too much about the details, this is about giving visibility into what's changing and following the standard that we'd want any contributing group to follow.
User/Customer
Network upgrade scope reviewers
Future f3 implementers
Notes
The text was updated successfully, but these errors were encountered:
@masih or @Kubuxu : can you please help fill out the done criteria with the list of things we should include in the FIP update? I'm hoping to capture those now so we can have @Stebalien eyeball it to keep us honest.
Let me know if you disagree, but I'm viewing this FIP update work as procedural requirement for bundling the new changes in the nv25 network upgrade.
Done Criteria
There is an update to the F3 FIP outlining the additions/changes related to the protocol changes as a result of the learnings from nv24 passive testing that will be include in nv25. The set of changes that should be included are:
Why Important
There have been non-trivial changes to F3 based on the learnings from nv24. These should make them back to the FIP for visibility to the community, especially since these changes will be shipped as part of nv25.
While we don't expect anyone to care too much about the details, this is about giving visibility into what's changing and following the standard that we'd want any contributing group to follow.
User/Customer
Notes
The text was updated successfully, but these errors were encountered: