> Though if someone knows of a vendor who plans to support vxlan-gpe on their
> already installed vxlan supporting hardware please speak up. I certainly did
> not check with every vendor.
As a silicon vendor, Marvell have the same silicon that supports both VXLAN and
VXLAN-GPE. Our customers
On Jul 22, 2016 3:38 AM, "Dino Farinacci" wrote:
>
> > - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN host
receives a VXLAN packet for some protocol other than Ethern the payload
will be misinterpreted. A separate port number was required. I assume that
a
Some NICs on the market can support VxLAN-GPE while originally designed for
VxLAN only
That was part of the work towards the path VxLAN-GPE took
Thx
Uri (“Oo-Ree”)
C: 949-378-7568
From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Jon Hudson
Sent: Friday, July 22, 2016 1:58 AM
To: Dino
On Jul 22, 2016 11:44 AM, "Tom Herbert" wrote:
>
> On Jul 22, 2016 3:38 AM, "Dino Farinacci" wrote:
> >
> > > - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN
host receives a VXLAN packet for some protocol other than Ethern the
payload
Hi Ed,
I agree with Yizhou that this sentence doesn't exclude anything.
If the sentence were rephrased as "In the simplest case, ..." instead of "In
the majority of cases, ..." that would still make the point and mitigate the
concern about inclusion of more complex cases (which are definitely
+1.
Besides, IETF already has specified many encapsulations, is it really that bad
having one extra?
Linda
From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Anoop Ghanwani
Sent: Friday, July 22, 2016 7:55 AM
To: Bocci, Matthew (Nokia - GB)
Cc: NVO3
Subject: Re: [nvo3] Consensus call on
> - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN host
> receives a VXLAN packet for some protocol other than Ethern the payload will
> be misinterpreted. A separate port number was required. I assume that a user
> using VXLAN in HW must upgrade HW to use VXLAN-GPE
Tom, one
On Fri, Jul 22, 2016 at 1:38 AM, Dino Farinacci wrote:
> > - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN host
> receives a VXLAN packet for some protocol other than Ethern the payload
> will be misinterpreted. A separate port number was required. I assume
> On Fri, Jul 22, 2016 at 1:38 AM, Dino Farinacci wrote:
> > - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN host
> > receives a VXLAN packet for some protocol other than Ethern the payload
> > will be misinterpreted. A separate port number was required. I
> On Jul 21, 2016, at 4:56 PM, Bocci, Matthew (Nokia - GB)
> wrote:
> 2) Does anyone have a significant technical objection to selecting VXLAN-GPE
> as the single NVO3 Standards track document? Please be as concrete and
> detailed as possible as to your technical
On Jul 22, 2016, at 10:38 AM, Dino Farinacci wrote:
> I am told you can do this with BGP as well by negotiating what encapsulations
> are supported.
Of course, this also applies to any other encapsulation protocol, both BGP and
other control planes have done this. I don't
11 matches
Mail list logo