> -----Original Message-----
> From: Joe Touch [mailto:[email protected]]
> Sent: Monday, June 20, 2016 11:14 AM
> To: Xuxiaohu; Tom Herbert
> Cc: [email protected]; [email protected]
> Subject: Re: [nvo3] [Int-area] Fwd: New Version Notification for
> draft-ietf-nvo3-gue-03.txt
>
>
>
> On 6/19/2016 7:47 PM, Xuxiaohu wrote:
> > Sure. That's why we usually need to determine a WG which is more
> > suitable for a given draft firstly in the IETF. If you firmly believe
> > the more suitable WG for draft-ietf-nvo3-gue is NVO3, rather than
> > INTAREA and TSVWG, please give your rationale
>
> My rationale is simple - it's sufficient and that's where it already is a WG
> doc.
There was a famous saying: " it's never too late to mend!"
> If that were not the case, you'd have a stronger argument.
It has been said clearly before, " 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)
++++++++++"
Xiaohu
> But I really don't care all that much. If the chairs want to shift WGs, then
> they
> can make the case for a call for adoption elsewhere.
>
> However, given the substantial review this doc has already received both here
> and from TSV reviewers, I think that's largely wasted effort.
>
> Joe
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
