[NETVIRT-1228] OVS Based NA Responder for IPv6 default Gateway (ovs_based_na_responder_for_gw) Created: 25/Apr/18  Updated: 05/Sep/18  Resolved: 05/Sep/18

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Medium
Reporter: Karthikeyan Krishnan Assignee: Karthikeyan Krishnan
Resolution: Won't Do Votes: 0
Labels: spec_approved
Remaining Estimate: 4 weeks
Time Spent: 1 week
Original Estimate: 5 weeks

Issue Links:
Cloners
clones NETVIRT-1191 <Change Blueprint Title (add topic ta... Resolved

 Description   

OVS Based NA Responder for IPv6 default Gateway (ovs_based_na_responder_for_gw)

Description

This spec addresses OVS Based Neighbor Advertisement(NA) responder for IPv6 default Gateway.
Neighbor Solicitation(NS) request which has initiated from IPv6 configured/enabled Data Center(DC) VMs are served by OVS based NA responder.

Specification Gerrit: 71293

Specification Final

Gerrits Topic: ovs_based_na_responder_for_gw

Dependencies
============
The following changes are required to support this feature in ODL controller.

1) The following OF Plugin Support is required in ODL to support OVS based NA responder solution.
    *NA Flags (Router[R], Solicitation[S], Override[O], Reserved).
    *Re-computation of ICMPv6 checksum logic.

2) OVS changes for supporting NA Flags and icmpv6_options_type TLL set if TLL field is not present in the packet.



 Comments   
Comment by Karthikeyan Krishnan [ 31/Jul/18 ]

Hi All,

We have a bit challenges with respect to doing the code changes in OF plugin to support the new IPv6 attributes [0] as a mandatory for complete this feature(OVS_NA_RESPONDER) from ODL controller side. These new attributes are not comes under the NXM or OXMs standards. So, to add new extension standards in OF plugin also not feasible at this point of time due to IPR clearance of the proprietary code changes.

we can add this feature support once OVS side changes are ready. Till that point we can put this feature on hold.

We can not able to deliver this feature in fluorine release.

 

Thanks,

Karthikeyan.

 

 

Comment by Karthikeyan Krishnan [ 03/Sep/18 ]

Hi Sam, 

  Request to remove the required fields in this Jira ticket to un-appear from the fluorine feature blue print list.

Thanks in Advance,

Karthikeyan.

Comment by Karthikeyan Krishnan [ 05/Sep/18 ]

we can add this feature support once OVS side changes are ready. Till that point we can put this feature on hold.

Generated at Wed Feb 07 20:23:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.