search

openconfig / public

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

Query on decapsulate-header in ipv4 and ipv6 entries #483

Closed manirk-jnpr closed 2 months ago

manirk-jnpr commented 3 years ago

Hi @aashaikh and @robshakir,

Regarding: /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/decapsulate-header /network-instances/network-instance/afts/ipv6-unicast/ipv6-entry/state/decapsulate-header

OC restricts prefix(oc-inet:ipv4-prefix or ipv6-prefix) length to 32/128 bits where as tunnel decapsulate route is 72/264 bits in Juniper. This route has information about tunnel source(32/128 bits), destination(32/128 bits) and tunnel type(ex: GRE, 8 bits). There is no provision to stream such routes with the restriction. Can OC be flexible with this restriction of @@32/128 bits for the prefix length?

Thanks, Mani Juniper Networks

manirk-jnpr commented 2 years ago

Hi @aashaikh and @robshakir,

Could you respond to this query?

Thanks, Mani

robshakir commented 2 years ago

If the decapsulation is occurring based on more than just the destination then in the OpenConfig AFT model, this is a policy-forwarding entry. Entries in the IPv4 and IPv6 AFTs correspond to solely destination based routing.

Thanks, r.

github-actions[bot] commented 4 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.