Re: [Int-area] I-D Action: draft-ietf-intarea-gue-04.txt
Joe Touch <touch@isi.edu> Fri, 19 May 2017 21:41 UTC
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE6B0128656; Fri, 19 May 2017 14:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdsNi64gaWnF; Fri, 19 May 2017 14:41:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FF471200F1; Fri, 19 May 2017 14:41:36 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v4JLfIKd011471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 19 May 2017 14:41:28 -0700 (PDT)
To: internet-drafts@ietf.org, i-d-announce@ietf.org
Cc: int-area@ietf.org
References: <149514799195.6631.3231700013200014494@ietfa.amsl.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <24f2fc9f-7bed-b91c-9aaa-20ccd77454b8@isi.edu>
Date: Fri, 19 May 2017 14:41:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149514799195.6631.3231700013200014494@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/KELmKRtCCA9p7U8yySbw_kMfEes>
Subject: Re: [Int-area] I-D Action: draft-ietf-intarea-gue-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 May 2017 21:41:38 -0000
FWIW: It might be useful for this document to be more clear in showing a) the specific header it introduces, before it talks about variations (e.g. in Sec 2 when it is introduced, rather than in subsections) b) examples of that header in the context they would appear in a typical packet, clearly indicating the GUE portion as distinct from that context The current explanation is a bit confusing because it uses atypical terms: - sec 2, what is a UDP/IP header? When we say TCP/IP, we mean the protocol suite, not a header AFAICT, this should show UDP and IP as separate: [IP][UDP][GUE][GUE payload] - sec 3.1, 4.1, and 4.2 present a header format in a confusing way GUE doesn't change the UDP header; it's a header inside UDP, so the UDP part should be omitted (making it consistent with what I expect for sec 2) the representation in 3.1 is confusing in comparison to 3.3.2, which is just the GUE header (again, omitting UDP from 3.1, 4.1, and 4.2 fixes this) Sec 4.1 should make it clear that the fields shown are just that of the IPv4 header - and the fact that the first two bits are 01 is what helps GUE realize that this is a special case. Sec 4.2 should do the same for IPv6. It seems like you also need to address what happens for IPv5, IPv7, and later values of IP (i.e., 00 = GUE, 01=IPv4-7, and what happens for 1x?). Joe On 5/18/2017 3:53 PM, internet-drafts@ietf.org wrote: > 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
- [Int-area] I-D Action: draft-ietf-intarea-gue-04.… internet-drafts
- [Int-area] Is the UDP destination port number res… Xuxiaohu
- Re: [Int-area] Is the UDP destination port number… Tom Herbert
- Re: [Int-area] Is the UDP destination port number… Joe Touch
- Re: [Int-area] I-D Action: draft-ietf-intarea-gue… Joe Touch
- [Int-area] 答复: Is the UDP destination port number… Xuxiaohu
- Re: [Int-area] 答复: Is the UDP destination port nu… Joe Touch
- [Int-area] 答复: 答复: Is the UDP destination port nu… Xuxiaohu
- Re: [Int-area] 答复: 答复: Is the UDP destination por… Joe Touch
- [Int-area] 答复: 答复: 答复: Is the UDP destination por… Xuxiaohu
- Re: [Int-area] 答复: Is the UDP destination port nu… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: Is the UDP destination… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: Is the UDP destination… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: Is the UDP destination… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: Is the UDP destination… Joe Touch
- [Int-area] 答复: 答复: 答复: 答复: Is the UDP destination… Xuxiaohu
- [Int-area] 答复: 答复: Is the UDP destination port nu… Xuxiaohu
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Templin, Fred L
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Templin, Fred L
- [Int-area] 答复: 答复: 答复: 答复: 答复: Is the UDP destina… Xuxiaohu
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: 答复: Is the UDP des… Tom Herbert
- Re: [Int-area] 答复: 答复: 答复: 答复: Is the UDP destina… Joe Touch