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

Xuxiaohu <xuxiaohu@huawei.com> Sat, 20 May 2017 03:58 UTC

Return-Path: <xuxiaohu@huawei.com>
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 2B45A1294F5 for <int-area@ietfa.amsl.com>; Fri, 19 May 2017 20:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 PbmO4kXGBvPW for <int-area@ietfa.amsl.com>; Fri, 19 May 2017 20:58:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B662129464 for <int-area@ietf.org>; Fri, 19 May 2017 20:57:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGY64474; Sat, 20 May 2017 03:57:57 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 20 May 2017 04:57:56 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Sat, 20 May 2017 11:57:49 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, Tom Herbert <tom@herbertland.com>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: =?utf-8?B?W0ludC1hcmVhXSDnrZTlpI06IElzIHRoZSBVRFAgZGVzdGluYXRpb24gcG9y?= =?utf-8?B?dCBudW1iZXIgcmVzb3VyY2UgcnVubmluZyBvdXQ/Ly8gcmU6IEktRCBBY3Rp?= =?utf-8?Q?on:_draft-ietf-intarea-gue-04.txt?=
Thread-Index: AQHS0RsMnyvO0qVuZEOz5xejzfeIJKH8l23w
Date: Sat, 20 May 2017 03:57:48 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA8903@NKGEML515-MBX.china.huawei.com>
References: <149514799195.6631.3231700013200014494@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA82B7@NKGEML515-MBX.china.huawei.com> <CALx6S37nrJNGLdRHWx9DYNQyS54YdwLCXcG9Mp3zi4L_wrr6=g@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA8877@NKGEML515-MBX.china.huawei.com> <a3915b87-f104-51d8-11e3-d9f8196462b5@isi.edu>
In-Reply-To: <a3915b87-f104-51d8-11e3-d9f8196462b5@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.184.181]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0202.591FBEC5.005C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 6ecba1e192b3aa802aa2cb6432b75690
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/jampXVS3LYnIIbHYKrcEaHEU06Y>
Subject: [Int-area] =?utf-8?b?562U5aSNOiAg562U5aSNOiBJcyB0aGUgVURQIGRlc3Rp?= =?utf-8?q?nation_port_number_resource_running_out=3F//_re=3A_I-D_Action?= =?utf-8?q?=3A_draft-ietf-intarea-gue-04=2Etxt?=
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: Sat, 20 May 2017 03:58:01 -0000

Hi Joe,

> -----邮件原件-----
> 发件人: Joe Touch [mailto:touch@isi.edu]
> 发送时间: 2017年5月20日 11:41
> 收件人: Xuxiaohu; Tom Herbert
> 抄送: int-area@ietf.org
> 主题: Re: [Int-area] 答复: Is the UDP destination port number resource running
> out?// re: I-D Action: draft-ietf-intarea-gue-04.txt
> 
> 
> 
> On 5/19/2017 6:39 PM, Xuxiaohu wrote:
> > If the saving is beneficial, it'd better to assign a dedicated port
> > number for each UDP payload type( e.g., IP packet), rather than
> > combining the UDP port number dedicated for GUE and the version field
> > within the GUE header together to indicate whether the UDP payload is
> > GUE or IP (or even other payload type if the GUE is devoted to help
> > save the UDP port number resource for the IETF community:))
> FWIW, IANA strives to assign one port for a service.

Great. Hence IPvx should be taken as a service rather than taking IPvx and GUE as a service, IMO.

> Services are expected to have version fields and subtype demultiplexing
> indicators, to so that all message variants of current and future versions can use
> a single port number.

Sure, the version field within the IPvx packet could be used for demultiplexing purpose.

Best regards,
Xiaohu

> Joe