Re: [nvo3] [Int-area] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 17 June 2016 13:11 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4753112D56F; Fri, 17 Jun 2016 06:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 L6KxibfRu82n; Fri, 17 Jun 2016 06:11:32 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75C4A12D1E7; Fri, 17 Jun 2016 06:11:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u5HDBW8J008267; Fri, 17 Jun 2016 06:11:32 -0700
Received: from XCH15-05-06.nw.nos.boeing.com (xch15-05-06.nw.nos.boeing.com [137.137.100.84]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u5HDBMAI007736 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2016 06:11:22 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-06.nw.nos.boeing.com (2002:8989:6454::8989:6454) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 17 Jun 2016 06:11:21 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000; Fri, 17 Jun 2016 06:11:20 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tom Herbert <tom@herbertland.com>, Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [Int-area] [nvo3] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt
Thread-Index: AQHRx9yJu0Wq3f0jeEOqDbqa+JuiIJ/to2yQ
Date: Fri, 17 Jun 2016 13:11:20 +0000
Message-ID: <78395b4781d0452c92bfcf24f607dac8@XCH15-05-05.nw.nos.boeing.com>
References: <20160610171451.30437.44413.idtracker@ietfa.amsl.com> <CALx6S34_ba2kBhUY7keEMmPO3fTRAAQsCkyGiy47=NnPm8xgug@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5647FB@NKGEML515-MBX.china.huawei.com> <CALx6S37K2H+SuEN+5Nmi-GOX0nX-k34YQt0anWJWTUBpBZZGew@mail.gmail.com>
In-Reply-To: <CALx6S37K2H+SuEN+5Nmi-GOX0nX-k34YQt0anWJWTUBpBZZGew@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.137.12.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/xFMDASa1_B0M1G9GBDpl86ksvs4>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [nvo3] [Int-area] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 13:11:34 -0000

Hi,

> > 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.

It also saves an RFC number.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Tom Herbert
> Sent: Thursday, June 16, 2016 7:37 AM
> To: Xuxiaohu <xuxiaohu@huawei.com>
> Cc: nvo3@ietf.org; int-area@ietf.org
> Subject: Re: [Int-area] [nvo3] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt
> 
> On Thu, Jun 16, 2016 at 2:12 AM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> >
> >
> >> -----Original Message-----
> >> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Tom Herbert
> >> Sent: Saturday, June 11, 2016 1:21 AM
> >> To: int-area@ietf.org; nvo3@ietf.org
> >> 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.

It also saves an RFC number.
> 
> Tom
> 
> > Best regards,
> > Xiaohu
> >
> >> Thanks,
> >> Tom
> >>
> >> ---------- Forwarded message ----------
> >> From:  <internet-drafts@ietf.org>
> >> Date: Fri, Jun 10, 2016 at 10:14 AM
> >> Subject: New Version Notification for draft-ietf-nvo3-gue-03.txt
> >> To: Tom Herbert <tom@herbertland.com>, Lucy Yong
> >> <lucy.yong@huawei.com>, Osama Zia <osamaz@microsoft.com>
> >>
> >>
> >>
> >> 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
> >> Int-area@ietf.org
> >> https://www.ietf.org/mailman/listinfo/int-area
> >
> > _______________________________________________
> > nvo3 mailing list
> > nvo3@ietf.org
> > https://www.ietf.org/mailman/listinfo/nvo3
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area