[nvo3] NVO3 WG Adoption of draft-quinn-vxlan-gpe-04

[Benson Schliesser <[e-mail]>]

Hi, Behcet.

Still writing as an individual:

After reading your email (quoted below) several times, I suspect that you
don't understand the way layering works. I'm not sure if this is just in
the context of what NVO3 is doing or in the general case, but I think it is
well understood by others that have been contributing here. It's up to them
to decide how much they want to respond to your questions. But I
personally don't have the time to provide you this education.

Now writing as co-chair:

You can certainly ask people to help you understand and/or explain their
drafts. I'm very tolerant of open discussion on the list as long as it is
constructive toward the WG goals.

NVO3 has adopted GUE and VXLAN-GPE, and is in process of adopting GENEVE
pending an IPR statement from one of the authors. These are potentially
implemented as overlay data plane encaps.

As a WG chair I am guided by WG consensus. The consensus seems to favor
these protocols as WG work items. I'm not yet aware of any specific issues
that need to be addressed by the authors.

-Benson



On Thursday, April 30, 2015, Behcet Sarikaya <[e-mail]
<javascript:_e(%7B%7D,'cvml','[e-mail]');>> wrote:

> On Thu, Apr 30, 2015 at 6:50 AM, Benson Schliesser
> <[e-mail]> wrote:
> > Hi, Behcet. Just speaking as an individual: I understand the purpose of
> GPE
> > as being the addition of a protocol field to VXLAN.
>
> This is where I have concerns.
> Protocol field is defined for IP header. Ethernet also has a similar
> field (called Ether Type).
> In RFC 7348, it is clearly defined that the next protocol is UDP
> (value 17) for VXLAN.
> Protocol field values are defined in
> http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
>
> Yes, there is IPv4 (value 4) and IPv6 (value 41). Just like Ethernet
> Ether Type has values, I think someone mentioned it.
>
> GPE draft is introducing another registry for the protocol field,.
>
> There must be some reason why they defined protocol field only for
> IPv4/v6 not e.g. for UDP.
>
> VXLAN is UDP encapsulation, it is not a different protocol.
>
> It seems like Paul has different opinion on these, because I noticed
> he added protocol field to his NSH draft also.
>
> Benson, is it OK to ask from Paul why?
> Or you want to ban me from asking these types of technical questions?
>
>
> > It is not specifically a
> > IPv4/v6 attribute, but more general.
>
> Please see above.
> > If you don't understand the general
> > case of how or why v4 and v6 are multiplexed with the lower-layer
> protocol
> > field then I don't think that's specifically germane to the nvo3 mailing
> > list.
>
> I made my point above, please see above.
> >
> > As for comparing GUE and VXLAN-GPE, that seems like a fair discussion to
> > have. But I don't currently see any especially constructive way to do
> that.
> >
>
> Can you please then explain it? How are these two compared?
> I am saying they are different things. GUE is currently being
> discussed in Intarea list.
>
> Regards,
>
> Behcet
> > Cheers,
> > -Benson
> >
> >
> > On Wednesday, April 29, 2015, Behcet Sarikaya <[e-mail]>
> > wrote:
> >>
> >>  Is gpe talking about encapsulation of inner packets, i.e. data plane?
> >> If yes then it is like GUE. Then one would ask why do we need another
> >> GUE?
> >>
> >> Looking at the abstract which says
> >>
> >> changes to the VXLAN header
> >>
> >> I think the answer is no.
> >>
> >> I would understand a few flags like OAM that you defined as extensions
> to
> >> VXLAN.
> >>
> >> But I have trouble understanding next protocol field.
> >> I think VXLAN encapsulation does not need next protocol field because
> >> what is being encapsulated is completely defined in RFC7348.
> >>
> >> If in the future the need arises that something like NSH also needs to
> >> be defined then the best way to do is to.define RFC7348bis and add it
> >> there.
> >>
> >> Regards,
> >>
> >> Behcet
> >>
> >>
> >> On Wed, Apr 29, 2015 at 2:09 PM, Larry Kreeger (kreeger)
> >> <[e-mail]> wrote:
> >> > Regarding Joe Touch's comment about explicitly NOT indicating IPv4 vs
> >> > IPv6
> >> > in the Next Protocol (only indicating IP), I don't see what the
> >> > advantages
> >> > of doing this are.  It seems more philosophical.
> >> >
> >> > By indicating IPv4/IPv6 in the next protocol, it allows
> implementations
> >> > to
> >> > only make one decision before parsing the IP header.  By doing two
> steps
> >> > NP->IP->IPv4/v6, it adds one more parsing step to the implementation,
> >> > for
> >> > no gain that I can think of.
> >> >
> >> > As Diego pointed out earlier, there is already a precedent in Ethernet
> >> > for
> >> > indicating the IP version in the next protocol from the layer below
> it.
> >> >
> >> >  - Larry
> >> >
> >> > On 4/29/15 11:36 AM, "Behcet Sarikaya" <[e-mail]>
> wrote:
> >> >
> >> >>On Wed, Apr 29, 2015 at 1:13 PM, Paul Quinn (paulq) <[e-mail]>
> >> >>wrote:
> >> >>>
> >> >>>> On Apr 29, 2015, at 12:01 PM, Behcet Sarikaya
> >> >>>> <[e-mail]>
> >> >>>>wrote:
> >> >>>>
> >> >>>> On Tue, Apr 28, 2015 at 5:03 PM, Behcet Sarikaya
> >> >>>><[e-mail]> wrote:
> >> >>>>> Hi Benson,
> >> >>>>>
> >> >>>>> Joe Touch wrote this on intarea list:
> >> >>>>>
> >> >>>>> There is no reason for having the GUE header differentiate between
> >> >>>>> payload=IPv4 and payload=IPv6. The IP version is addressed by the
> >> >>>>> version field of the IP header. If GUE encapsulates both type of
> IP
> >> >>>>>the
> >> >>>>> same way (and it should), it should NOT differentiate between them
> >> >>>>> in
> >> >>>>> its (GUE) header.
> >> >>>>>
> >> >>>>>
> >> >>>>> I think the same applies to gpe header.
> >> >>>>>
> >> >>>>> Plus the issues on the "NSH" protocol.
> >> >>>>
> >> >>>> Curiously if you look at the nsh draft, Section 3.2,
> >> >>>>
> >> >>>> NSH Base Header
> >> >>>>
> >> >>>> also has a next protocol field with the same encoding.
> >> >>>>
> >> >>>> Anybody understands what is going on?
> >> >>>
> >> >>> Yes, the concept is that you don't know what you want to carry via
> >> >>> GPE.
> >> >>> Today it might be v4, v6, ethernet, NSH or something else.
> Tomorrow,
> >> >>>who knows?  But more importantly, we need to enable that stacking to
> >> >>>occur.
> >> >>>
> >> >>
> >> >>
> >> >>Please convince not me but Joe Touch on v4 and v6 thing.
> >> >>
> >> >>> The format of NSH is orthogonal -- as is the format of Ethernet for
> >> >>>that matter.  From an outer header (i.e. VXLAN-GPE or other) you need
> >> >>> to
> >> >>>be able to identify the inner protocol.
> >> >>>
> >> >>
> >> >>Are we talking about VM-to-VM communication? I think that is what
> >> >>VXLAN was designed for.
> >> >>
> >> >>Regards,
> >> >>
> >> >>Behcet
> >> >>> Paul
> >> >>>
> >> >
>