Skip to content

Conformance test results DestinationPortMatching and ParentRefPort are confusing #4302

@rouke-broersma

Description

@rouke-broersma

What would you like to be added:

Explanation of what is covered by a conformance test, and/or link to the GEP the conformance test is supposed to cover

Why this is needed:

After spending quite some time trying to figure out the difference between DestinationPortMatching and ParentRefPort I am coming to the conclusion that these features seem to be about the same feature? There is a GEP mentioning destination port matching, which clearly describes the parent ref port as the chosen solution. However the results are not the same for all implementations, possibly because implementations are also not clear that these are the same feature so don't list them as supported in their conformance tests which I think skips testing the feature.

Or all of the above is wrong, which would further add to my point that the conformance tests and what they cover are unclear.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/documentationCategorizes issue or PR as related to documentation.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions