JIRA:IPVSIX-29

Change-Id: I6fa05469f1e506d1e44d8aa1fede886f69240677
Signed-off-by: Bin Hu <bh526r@att.com>

2 files changed, 45 insertions, 8 deletions

diff --git a/docs/gapanalysis/gap-analysis-odl-lithium.rst b/docs/gapanalysis/gap-analysis-odl-lithium.rst
index 5a3d06b..faa260b 100644
--- a/docs/gapanalysis/gap-analysis-odl-lithium.rst
+++ b/docs/gapanalysis/gap-analysis-odl-lithium.rst
@@ -7,10 +7,47 @@ Open Daylight Lithium Official Release. The following table lists the use cases
 requirements of VIM-agnostic IPv6 functionality, including infrastructure layer and VNF
 (VM) layer, and its gap analysis with Open Daylight Lithium Official Release.
 
-+------------------------------------------------------+------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|Use Case / Requirement                                |Supported in ODL Lithium|Comments                                                                                                                                                                                                                                                                                                                                                                                                          |
-+======================================================+========================+==================================================================================================================================================================================================================================================================================================================================================================================================================+
-|REST API support for IPv6 subnet creation in ODL      |Yes                     |Yes, it is possible to create IPv6 subnet in ODL using Neutron REST APIs.                                                                                                                                                                                                                                                                                                                                         |
-|                                                      |                        || For a network with both IPv4 and IPv6 subnets, ODL mechanism driver will send the port information which includes IPv4 and IPv6 addresses to ODL Neutron NB API. When port information is queried, it displays IPv4 and IPv6 addresses. However, in Lithium Release, ODL net-virt provider does not support IPv6 feature, i.e. the actual functionality is missing. It would be available only in later release.|
-+------------------------------------------------------+------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|Use Case / Requirement                                       |Supported in ODL Lithium|Notes                                                                    |
++=============================================================+========================+=========================================================================+
+|REST API support for IPv6 subnet creation in ODL             |Yes                     |Yes, it is possible to create IPv6 subnets in ODL using Neutron REST API.|
+|                                                             |                        |                                                                         |
+|                                                             |                        |For a network which has both IPv4 and IPv6 subnets, ODL mechanism driver |
+|                                                             |                        |will send the port information which includes IPv4/v6 addresses to ODL   |
+|                                                             |                        |Neutron northbound API. When port information is queried it displays IPv4|
+|                                                             |                        |and IPv6 addresses. However, in Lithium release, ODL net-virt provider   |
+|                                                             |                        |does not support IPv6 features (i.e., the actual functionality is missing|
+|                                                             |                        |and would be available only in the later releases of ODL).               |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|IPv6 Router support in ODL                                   |**No**                  |ODL net-virt provider in Lithium release only supports IPv4 Router.      |
+|                                                             |                        |Support for IPv6 Router is planned using ``Routing Manager`` as part of  |
+|1. Communication between VMs on same compute node            |                        |Beryllium Release. In the meantime, if IPv6 Routing is necessary, we can |
+|2. Communication between VMs on different compute nodes      |                        |use ODL for L2 connectivity and Neutron L3 agent for IPv4/v6 routing.    |
+|   (east-west)                                               |                        |                                                                         |
+|3. External routing (north-south)                            |                        |**Note**: In Lithium SR1 release, we have the following `issue           |
+|                                                             |                        |<http://fpaste.org/275362>`_, which is fixed upstream and back-ported to |
+|                                                             |                        |``stable/lithium``.                                                      |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|IPAM: Support for IPv6 Address assignment modes.             |**No**                  |Although it is possible to create different types of IPv6 subnets in ODL,|
+|                                                             |                        |ODL_L3 would have to implement the IPv6 Router that can send out Router  |
+|1. SLAAC                                                     |                        |Advertisements based on the IPv6 addressing mode. Router Advertisement   |
+|2. DHCPv6 Stateless                                          |                        |is also necessary for VMs to configure the default route.                |
+|3. DHCPv6 Stateful                                           |                        |                                                                         |
+|                                                             |                        |This could be part of ``Routing Manager`` in ``Beryllium`` release.      |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|When using ODL for L2 forwarding/tunneling, is it compatible |Yes                     |                                                                         |
+|with IPv6.                                                   |                        |                                                                         |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|Full support for IPv6 matching (i.e., IPv6, ICMPv6, TCP, UDP)|**No**                  |Security Groups for IPv6 are currently not supported.                    |
+|in security groups. Ability to control and manage all IPv6   |                        |                                                                         |
+|security group capabilities via Neutron/Nova API (REST and   |                        |                                                                         |
+|CLI) as well as via Horizon.                                 |                        |                                                                         |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|Shared Networks support                                      |**No**                  |ODL currently assumes a single tenant to network mapping and does not    |
+|                                                             |                        |support shared networks among tenants.                                   |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|IPv6 external L2 VLAN directly attached to a VM.             |**ToDo**                |                                                                         |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
+|ODL on an IPv6 only Infrastructure.                          |**ToDo**                |Deploying OpenStack with ODL on an IPv6 only infrastructure where the API|
+|                                                             |                        |endpoints are all IPv6 addresses.                                        |
++-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
diff --git a/docs/gapanalysis/gap-analysis-openstack-kilo.rst b/docs/gapanalysis/gap-analysis-openstack-kilo.rst
index c20aa98..afd50e9 100644
--- a/docs/gapanalysis/gap-analysis-openstack-kilo.rst
+++ b/docs/gapanalysis/gap-analysis-openstack-kilo.rst
@@ -33,7 +33,7 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer
 |   to assign vRouters to the L3 agents)                    |                         |                                                                    |
 +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+
 |Ability for a NIC to support both IPv4 and IPv6 (dual      |                         |Dual-stack is supported in Neutron with the addition of             |
-|stack) address.                                            |                         |Multiple IPv6 Prefixes Blueprint:                                   |
+|stack) address.                                            |                         |``Multiple IPv6 Prefixes`` Blueprint                                |
 |                                                           |                         |                                                                    |
 |1. VM with a single interface associated with a network,   |1. Yes                   |                                                                    |
 |   which is then associated with two subnets.              |                         |                                                                    |