IETF Logo Mail Archive

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

Joe Touch <touch@isi.edu> Sat, 20 May 2017 04:15 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 7AEEE129AD5 for <int-area@ietfa.amsl.com>; Fri, 19 May 2017 21:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.5
X-Spam-Level:
X-Spam-Status: No, score=-5.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 HGLOMecXhPKG for <int-area@ietfa.amsl.com>; Fri, 19 May 2017 21:15:53 -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 848CE129649 for <int-area@ietf.org>; Fri, 19 May 2017 21:15:53 -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 v4K4F2bG000053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 19 May 2017 21:15:12 -0700 (PDT)
To: Xuxiaohu <xuxiaohu@huawei.com>, Tom Herbert <tom@herbertland.com>
Cc: "int-area@ietf.org" <int-area@ietf.org>
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> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA8903@NKGEML515-MBX.china.huawei.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <54980b3a-2dc9-2ab1-f150-45b3f500f7ac@isi.edu>
Date: Fri, 19 May 2017 21:15:01 -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: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BBA8903@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
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/GkM84GhyOHa2YlbRtAETLd3Bo-0>
Subject: Re: [Int-area] =?utf-8?b?562U5aSNOiAg562U5aSNOiBJcyB0aGUgVURQIGRl?= =?utf-8?q?stination_port_number_resource_running_out=3F//_re=3A_I-D_Actio?= =?utf-8?q?n=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 04:15:54 -0000


On 5/19/2017 8:57 PM, Xuxiaohu wrote:
> 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.
GUE is supposed to be both signalling and content (data), where the data
are IP packets.

Take away the IP part and GUE isn't an E anymore.
>> 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.

That demultiplexes within IPvx. There still needs to be a way to
demultiplex non-IPvx packets (control) from IPvx.

Joe

v2.2.0 | Report a Bug | By Email