RFC 8022 is a proposed standard (as opposed to draft) which includes Yang module ietf-routing [0].

This yang module contains grouping special-next-hop which has leaf special-next-hop of type enumeration, which triggers MDSAL-207 (as a symptom of MDSAL-1 which will not be fixed for Java binding v1).

As an illustration, here is a Change [1] attempting to add ietf-routing to mdasal.models.

Even though IETF models should be hosted in mdsal.model (I believe), two projects are maintaining their own copies (without changing the module name):

• Honeycomd/Vbd avoids MDSAL-207 by renaming the grouping [2].
• Bier avoids MDSAL-207 by renaming the leaf [3].

This leads to a situation where adding Bier features to integration [4] fails, because Honeycomb/Vbd augments are not compatible with the Bier edit (which has newer revision).

BIER-3 and HONEYVBD-14 are opened against the two projects to move their IETF models to Mdsal, but this Bug is there to decide what to do with respect to MDSAL-207 in order for ietf-routing (Java binding v1) to be available for other ODL projects.

[0] https://tools.ietf.org/html/rfc8022#section-7
[1] https://git.opendaylight.org/gerrit/#/c/50377/1
[2] https://git.opendaylight.org/gerrit/gitweb?p=honeycomb/vbd.git;a=blob;f=api/src/main/yang/ietf-routing.yang;h=6902cd0bf2d048d020985362868c4f48f81338b3;hb=refs/heads/master#l263
[3] https://git.opendaylight.org/gerrit/gitweb?p=bier.git;a=blob;f=common/models/ietf-bier-2016-07-23/src/main/yang/imported/ietf-routing@2016-10-20.yang;h=59d01305fb11726f2faa2f43afc9913e55fce945;hb=refs/heads/master#l203
[4] https://git.opendaylight.org/gerrit/49828