Next we have overlay encapsulation that is Geneva.
In L.A. 60 and a 60 user Geneva.
Like in ACA we have we explained our IVF clan.
Like that we have Geneva and in Geneva it's actually quite a bit extensive.
You can say that protocol which is which is providing enhanced flexibility in terms of data plan X extensively
here you can see the format and I have given the link as well so you can go and refer this link where
you will get the draft of all this Geneva that and in 60 years using.
So it is providing extra flexibility extensively inside the cell for example with respect to re-explain
inside the data plane and with Geneva actually or watch the one of the most advantageous thing we have
with Geneva is that they have something called the Hillary type land value and with the help of deal
B This will allow any vendor to add its own metadata in the later.
And that's quite interesting.
We have one small example related to this Actually that example that how Geneva with type land value
helping to learn other TPP metadata when he is sending the flood package to the other hypervisor.
We'll see that.
So what are the features it has identified the DP that source internal Packard's identification of Kip
there is a version built inside that just to identify what the stage of created this there is one big
wave which is indicating whether encapsulated frame is twist.
No the point number forward here that we have an example.
So we'll see that in two tier hierarchy hierarchical flooding mechanism.
They come to know are they store the metadata.
So when the packet or window frame is going to their destination hypervisor they should understand that
which particular MAC this DP belongs to.
I'll show you this example in the next slide and this Jean-Yves they have two bits identify the type
of the source.
DP Daniel endpoint.
So what I tried to explain here is that so for example in two tier architectures recall this diagram
we have discussed about this.
So here you can see that we have different different subnets you have different transport and to optimize
the data plan what we are doing from one hypervisor is the suppose VM one wants to communicate with
the VM for so he will send only one packet to any random hypervisor in this group.
Now what will happen is if for example this particular guy is also being tested to take the flag it
package I suppose I have saying this packet here are the frame here to hypervisor 6.
Now what will happen now.
It's the responsibility of hypervisor 6 is to replicate its true seeing the replicated packets to other
hypervisor and whoever hypervisor having the VM for they will respond and then they will start communicating
our communication right the same way.
I have an example Lucy that instead of six it is going to five and then five is sending the replicated
packet to DP four.
So let's see the example first.
So here I can see that web 1 This is the Web VM over hypervisor one wants to communicate.
So for example the web 0 4 of hypervisor for like what is happening that is sending the packet or the
frame to the IP with a five.
And he is sending the replicator creams to all the hypervisor in that group.
In that case when hypervisor 4 is getting that frame he is thinking oh Maca.
This one actually belongs to DP vibe and that's the confusion he has because Mac one belongs to hypervisor
one DP one.
Correct.
So in that case learning of the matrix is very important.
So when we are using the Geneva encapsulation in indexes you can see that in the tunnel here they have
the metadata.
So now when the frame arrives to hypervisor for he looked that they will only find 0 Mac 1.
Actually its parent is DP 1 It belongs to DP 1 and that's why the data plane learning has been optimized
in this case.
All right.
So we can stop here now.