Hi Tom,
By the way, I have just had a look at your draft. It seems that this draft
itself has nothing to do with the multi-tenancy capability which is the focus
of the NOV3 current charter. In addition, according to section 7 (Motivation
for GUE) of this draft, it seems that GUE is intended to be a generic UDP-based
tunneling technology. Therefore, should this draft be pursued in some WGs other
than NVO3, e.g., TSVWG or INTAREA. In this way, it would be helpful for us to
better understand the differences between GUE and GRE-in-UDP, and whether the
concerns made by Joe Touch (see below) have been addressed successfully,
especially when considering the case where the version is set to 1 (i.e.,
directly encapsulating IP packet over UDP).
+++++++++
- stronger checksums
- fragmentation support
- signalling support (e.g., to test whether a tunnel is up or
to measure MTUs)
- support for robust ID fields (related to fragmentation,
e.g., to overcome the limits of IPv4 ID as per RFC 6864)
++++++++++
Best regards,
Xiaohu
> -----Original Message-----
> From: Int-area [mailto:[email protected]] On Behalf Of Xuxiaohu
> Sent: Friday, June 17, 2016 9:49 AM
> To: Tom Herbert
> Cc: [email protected]; [email protected]
> Subject: Re: [Int-area] [nvo3] Fwd: New Version Notification for
> draft-ietf-nvo3-gue-03.txt
>
>
>
> > -----Original Message-----
> > From: Tom Herbert [mailto:[email protected]]
> > Sent: Thursday, June 16, 2016 10:37 PM
> > To: Xuxiaohu
> > Cc: [email protected]; [email protected]
> > Subject: Re: [nvo3] [Int-area] Fwd: New Version Notification for
> > draft-ietf-nvo3-gue-03.txt
> >
> > On Thu, Jun 16, 2016 at 2:12 AM, Xuxiaohu <[email protected]> wrote:
> > >
> > >
> > >> -----Original Message-----
> > >> From: Int-area [mailto:[email protected]] On Behalf Of Tom
> > >> Herbert
> > >> Sent: Saturday, June 11, 2016 1:21 AM
> > >> To: [email protected]; [email protected]
> > >> Subject: [Int-area] Fwd: New Version Notification for
> > >> draft-ietf-nvo3-gue-03.txt
> > >>
> > >> Hello,
> > >>
> > >> We've posted a new version of GUE. The primary addition is that we
> > >> added GUE version 1 that allows direct encapsulation of IPv4 and
> > >> IPv6 over UDP (port 6080). This effectively implements
> > >> draft-xu-intarea-ip-in-udp-03 also.
> > > Tom,
> > >
> > > What's the real benefit of such implementation of IP-in-UDP compared
> > > to the
> > approach as described draft-xu-intarea-ip-in-udp-03? Save one UDP port
> > number?
> > >
> > Yes, saves a port number.
>
> To save a port number, the header format is made ugly. Is it worthwhile? If
> UDP
> port resource was so sparse as you had imagined, I think the UDP port resource
> keeper would not allocate two different port numbers for VXLAN and
> VXLAN-GPE since the P-bit in VXLAN-GPE header is enough to distinguish
> VXLAN-GPE from VXLAN. For more details, please look at section 3.2 of
> (https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-02#page-6).
>
> Xiaohu
>
> > Tom
> >
> > > Best regards,
> > > Xiaohu
> > >
> > >> Thanks,
> > >> Tom
> > >>
> > >> ---------- Forwarded message ----------
> > >> From: <[email protected]>
> > >> Date: Fri, Jun 10, 2016 at 10:14 AM
> > >> Subject: New Version Notification for draft-ietf-nvo3-gue-03.txt
> > >> To: Tom Herbert <[email protected]>, Lucy Yong
> > >> <[email protected]>, Osama Zia <[email protected]>
> > >>
> > >>
> > >>
> > >> A new version of I-D, draft-ietf-nvo3-gue-03.txt has been
> > >> successfully submitted by Tom Herbert and posted to the IETF repository.
> > >>
> > >> Name: draft-ietf-nvo3-gue
> > >> Revision: 03
> > >> Title: Generic UDP Encapsulation
> > >> Document date: 2016-06-10
> > >> Group: nvo3
> > >> Pages: 28
> > >> URL:
> > >> https://www.ietf.org/internet-drafts/draft-ietf-nvo3-gue-03.txt
> > >> Status: https://datatracker.ietf.org/doc/draft-ietf-nvo3-gue/
> > >> Htmlized: https://tools.ietf.org/html/draft-ietf-nvo3-gue-03
> > >> Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-gue-03
> > >>
> > >> Abstract:
> > >> This specification describes Generic UDP Encapsulation (GUE), which
> > >> is a scheme for using UDP to encapsulate packets of arbitrary IP
> > >> protocols for transport across layer 3 networks. By encapsulating
> > >> packets in UDP, specialized capabilities in networking hardware for
> > >> efficient handling of UDP packets can be leveraged. GUE specifies
> > >> basic encapsulation methods upon which higher level constructs, such
> > >> tunnels and overlay networks for network virtualization, can be
> > >> constructed. GUE is extensible by allowing optional data fields as
> > >> part of the encapsulation, and is generic in that it can encapsulate
> > >> packets of various IP protocols.
> > >>
> > >>
> > >>
> > >>
> > >> Please note that it may take a couple of minutes from the time of
> > >> submission until the htmlized version and diff are available at
> > >> tools.ietf.org.
> > >>
> > >> The IETF Secretariat
> > >>
> > >> _______________________________________________
> > >> Int-area mailing list
> > >> [email protected]
> > >> https://www.ietf.org/mailman/listinfo/int-area
> > >
> > > _______________________________________________
> > > nvo3 mailing list
> > > [email protected]
> > > https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> Int-area mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
