IETF Logo Mail Archive

Re: [sunset4] WG Adoption call for draft-chen-sunset4-nat64-port-allocation

"Huangjing (A)" <james.huang@huawei.com> Tue, 19 May 2015 02:20 UTC

Return-Path: <james.huang@huawei.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E17D1B2D36 for <sunset4@ietfa.amsl.com>; Mon, 18 May 2015 19:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 QHxpiJwUFCR5 for <sunset4@ietfa.amsl.com>; Mon, 18 May 2015 19:20:14 -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 84F1C1B2D32 for <sunset4@ietf.org>; Mon, 18 May 2015 19:20:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSR80818; Tue, 19 May 2015 02:20:11 +0000 (GMT)
Received: from SZXEMA413-HUB.china.huawei.com (10.82.72.72) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 19 May 2015 03:20:09 +0100
Received: from SZXEMA501-MBX.china.huawei.com ([169.254.1.61]) by SZXEMA413-HUB.china.huawei.com ([10.82.72.72]) with mapi id 14.03.0158.001; Tue, 19 May 2015 10:20:05 +0800
From: "Huangjing (A)" <james.huang@huawei.com>
To: JF Tremblay <jean-francois.tremblay@viagenie.ca>
Thread-Topic: [sunset4] WG Adoption call for draft-chen-sunset4-nat64-port-allocation
Thread-Index: AQHQhE6PMBpj4xu2SU+ujvNRQXuteZ1pvXaAgAGhUYCAAZy9UP//zuGAgBXha1A=
Date: Tue, 19 May 2015 02:20:04 +0000
Message-ID: <774B240D54DAB844B37EE80C2DD8E8BC649471E6@SZXEMA501-MBX.china.huawei.com>
References: <D15C0547.4E335%wesley.george@twcable.com> <66189322-D15E-4D84-9844-493C00D8068A@viagenie.ca> <CAM+vMES8KK2gRYD+0Q-8W5mMHLzTrTRt=7ChEshXpO=Y1Vazjg@mail.gmail.com> <096F8AFE-9A16-4986-8050-85047DD87C17@viagenie.ca> <774B240D54DAB844B37EE80C2DD8E8BC6492CBB7@SZXEMA501-MBX.china.huawei.com> <02A44511-C2D6-4DA2-9733-79546259A528@viagenie.ca>
In-Reply-To: <02A44511-C2D6-4DA2-9733-79546259A528@viagenie.ca>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.116.136]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sunset4/BJ2CodYPPB5dF9oSTsea0m7MCHU>
Cc: Tom Taylor <tom.taylor.stds@gmail.com>, "sunset4@ietf.org" <sunset4@ietf.org>, GangChen <phdgang@gmail.com>
Subject: Re: [sunset4] WG Adoption call for draft-chen-sunset4-nat64-port-allocation
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2015 02:20:16 -0000

Hi, JF,

Thanks for the information!

James

> -----Original Message-----
> From: JF Tremblay [mailto:jean-francois.tremblay@viagenie.ca]
> Sent: Tuesday, May 05, 2015 8:11 PM
> To: Huangjing (A)
> Cc: sunset4@ietf.org; GangChen; Tom Taylor
> Subject: Re: [sunset4] WG Adoption call for
> draft-chen-sunset4-nat64-port-allocation
> 
> 
> > On May 5, 2015, at 3:11 AM, Huangjing (A) <james.huang@huawei.com>
> wrote:
> >
> >>>
> >>> Good to know more if you point me a reference of "port block
> >> randomization”.
> >>
> >> There isn’t a reference. I might have coined the term a couple of
> >> years back, not sure. This is basically the act of randomizing the
> >> assignments of blocks instead or in conjunction with port randomization
> within the block.
> >> This could be a concept defined and discussed in this document.
> >
> > I think you are talking about the port block randomization algorithms similar
> to those defined in RFC6431.
> > Will add some analysis and reference
> 
> Thanks for the reference, James. Interesting. I had in mind a
> non-cryptographically random set of port, which doesn’t seem to be handled in
> RFC6431. That would basically be a continuous set of ports where the first port
> is assigned randomly or semi-randomly (could be on block boundary for
> example). This concept could be defined and discussed in this document, but
> it’s just a minor point for discussion/improvement.
> 
> JF
> 
>

v2.46.0 | Report a Bug | By Email | System Status