[Int-area] Is the UDP destination port number resource running out?// re: I-D Action: draft-ietf-intarea-gue-04.txt

Hi all,

With regard to directly encapsulating IPvx packet in UDP, I think the following argument for using Version 1 of GUE is not valid:

"This technique saves encapsulation overhead on costly links
   for the common use of IP encapsulation, and also obviates the need to
   allocate a separate port number for IP-over-UDP encapsulation."

First, I don't think the encapsulation overhead of 4 bytes is a matter. However, the premise is that it's meaningful for the IETF to develop such a GENERIC and COVERALL encapsulation method which is still looking for nails:)  If I remembered correctly, this draft was originally adopted by the NVO3 WG which is focused on multi-tenancy, although this draft has nothing to do with multi-tenancy:) Latter it becomes a INTAREA WG draft. by the way, did I miss the WG adoption call for this draft in the INTAREA WG or the WG adoption call isn't occurred at all?

Second, UDP itself has been widely used as a tunnel technology due to its load-balancing capability. See LISP [RFC6830], VXLAN [RFC7346], MPLS-in-UDP [RFC7510], GRE-in-UDP [RFC8086], ESP-in-UDP [RFC3948], TRILL-in-UDP, NSH-in-UDP, VXLAN-GPE, GENEVE, GUE, ... The destination port is used to distinguish these different UDP tunnel payload types. For IP-in-UDP, there has been a draft (https://tools.ietf.org/html/draft-xu-intarea-ip-in-udp) which was originally discussed in Softwire WG (https://tools.ietf.org/html/draft-xu-softwire-ip-in-udp) . IMHO, it seems ugly to use a version field within the GUE header to distinguish IPvx header from the GUE header itself. Is the UDP destination port number resource running out? If so, why not use GRE-in-UDP to carry GUE so as to save one more UDP destination port number? 

Third, if the GUE devotes itself to save the UDP destination port number for the interest of the internet community, the 2-bit version field abused as a payload type indicator is obviously not enough:)

Best regards,
Xiaohu

> -----邮件原件-----
> 发件人: Int-area [mailto:int-area-bounces@ietf.org] 代表
> internet-drafts@ietf.org
> 发送时间: 2017年5月19日 6:53
> 收件人: i-d-announce@ietf.org
> 抄送: int-area@ietf.org
> 主题: [Int-area] I-D Action: draft-ietf-intarea-gue-04.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Internet Area Working Group of the IETF.
> 
>         Title           : Generic UDP Encapsulation
>         Authors         : Tom Herbert
>                           Lucy Yong
>                           Osama Zia
> 	Filename        : draft-ietf-intarea-gue-04.txt
> 	Pages           : 37
> 	Date            : 2017-05-18
> 
> Abstract:
>    This specification describes Generic UDP Encapsulation (GUE), which
>    is a scheme for using UDP to encapsulate packets of different 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
>    as 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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-intarea-gue/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-intarea-gue-04
> https://datatracker.ietf.org/doc/html/draft-ietf-intarea-gue-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-intarea-gue-04
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area