openconfig / public

Repository for publishing OpenConfig models, documentation, and other material for the community.
Apache License 2.0
891 stars 645 forks source link

unable to support IPv6 address type distinction such as global, link-local and anycast in openconfig-if-ip.yang file #151

Closed sunseawq closed 3 weeks ago

sunseawq commented 6 years ago

The addresses defintiion in openconfig-if-ip.yang is as follows: " container addresses { description "Enclosing container for address list";

    list address {
      key "ip";
      description
       "The list of configured IPv6 addresses on the interface.";

      leaf ip {
        type leafref {
          path "../config/ip";
        }
        description "References the configured IP address";
      }

" I am wondering how to distinguish different IPv6 address types such as global, link-local, anycast, in addition, how to distinguish different address generation algorithms such as EUI-64, CGA, null, etc.

robshakir commented 6 years ago

Please can you explain the use case for this? There can be entries for auto-learned addresses in this list - but it's not necessarily clear to me why we need to have a type or the algorithm that was used to come up with them.

Are there operational reasons for having such state available?

Thanks, r.

sunseawq commented 6 years ago

auto-learned addresses are operational data, I am wondering how to distinguish auto-learned addresses from static addresses, how do I get only operational data such as auto-learned addresses ? It looks that ip under addressed list only point to address under config, my impression, we can not get auto-learned addresses using such state or config construct.

github-actions[bot] commented 2 months ago

This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.