Move the up-transitions leaf from the async and echo sub-containers into the state container.

[AnilKR123]

Change Scope

Currently there is an up-transitions leaf in both the async and echo subcontainers:

/bfd/interfaces/interface/peers/peer/state/echo/up-transitions
/bfd/interfaces/interface/peers/peer/state/async/up-transitions

I have moved this leaf into the state container, so that it is grouped with the failure-transitions leaf:

/bfd/interfaces/interface/peers/peer/state/failure-transitions
/bfd/interfaces/interface/peers/peer/state/up-transitions

• Discussed here: Clarification on Bfd up-transitions and failure-transitions.

[AnilKR123]

Hi @dplore,

I have launched this pr to address the issue discussed in: #1251.

Thanks,

Anil

[dplore]

/gcbrun

[OpenConfigBot]

No major YANG version changes in commit 4f19162

[dplore]

/gcbrun

[dplore]

/gcbrun

[dplore]

/gcbrun

[AnilKR123]

Hi @dplore, what is pending on this PR? Merging seems to be blocked.

[dplore]

This will be reviewed in the Feb 25, 2025 OC Operators meeting. If there is no objection, we'll set to "last-call" status for any further comments and then merge after the last-call period ends (typically two weeks).

The change as proposed is a breaking change because a leaf is deleted (moved). Unless there's a strong reason to delete this leaf, it should instead have a status field set todeprecated. Please also update the description to indicate it's deprecated and what should be used in it's place so the information is easy to reference in documentation.

[AnilKR123]

Thank you for the clarification. I deprecated the leaf instead of deleting it, and updated the description to reflect that as well as specify the new leaf to be used in its place.

[dplore]

Due to the other bfd contributions which were just merged, please update release/models/bfd/openconfig-bfd.yang to resolve conflicts. Otherwise, this LGTM. Setting to last call for March 18th,2025

[dplore]

/gcbrun

[dplore]

/gcbrun

[dplore]

/gcbrun

[dplore]

/gcbrun