IETF Logo Mail Archive

Re: [v6ops] ULA draft revision #2 Regarding isolated networks

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 28 May 2014 03:13 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534421A02EF for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 20:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 bNmH2yO38G45 for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 20:13:37 -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 A67D51A02E9 for <v6ops@ietf.org>; Tue, 27 May 2014 20:13:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEP61400; Wed, 28 May 2014 03:13:31 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 28 May 2014 04:13:03 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 28 May 2014 04:13:26 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.207]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 28 May 2014 11:13:23 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Ted Lemon <ted.lemon@nominum.com>, Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>
Thread-Topic: [v6ops] ULA draft revision #2 Regarding isolated networks
Thread-Index: Ac943yf4qhJ96dkPR9CtEDOlyHC2QQAMeJCAAAEGaQAAABxQAAAA4z6AAACtv4AAAMLCAAAAXbuAABGuc9D//4LtAIAAzDrt//+xewCAAJhKW///fSkA//6mNvA=
Date: Wed, 28 May 2014 03:13:22 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B7268@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <m261ks7xww.wl%randy@psg.com> <53840070.90801@gmail.com> <m2y4xn7wep.wl%randy@psg.com> <53840723.8010606@gmail.com> <CAKD1Yr1O_poMR200sjU=ttRvGaeQRkC1ZfXC0Ok4uQxdq3K=NQ@mail.gmail.com> <m2mwe37tbn.wl%randy@psg.com> <CAKD1Yr2t3-vxuG=iDi4biBNFpJwuzuHgfpB74i_uydWWRV7qZg@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6E02@nkgeml506-mbx.china.huawei.com> <m2fvjv7q4h.wl%randy@psg.com> <m1WpDcc-0000BMC@stereo.hq.phicoh.net> <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <m1WpHrp-0000BQC@stereo.hq.phicoh.net> <9DB71B37-999E-4F7F-A7DA-6B243574E818@nominum.com>
In-Reply-To: <9DB71B37-999E-4F7F-A7DA-6B243574E818@nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/aRnZgbvsN2vzuxi3ZPfBh8vm8Ho
Cc: v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] ULA draft revision #2 Regarding isolated networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2014 03:13:39 -0000


> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Tuesday, May 27, 2014 10:09 PM
> To: Philip Homburg
> Cc: v6ops WG
> Subject: Re: [v6ops] ULA draft revision #2 Regarding isolated networks
> 
> On May 27, 2014, at 9:56 AM, Philip Homburg
> <pch-v6ops-3a@u-1.phicoh.com> wrote:
> > If you are a large entrprise, just spend the 50 euro or so (RIPE
> > service region) it costs to get your own prefix.
> 
> Yes, but do we tell them to do that?   Do we tell them how to make it work?
> Do we tell them how to make source address selection do the right thing?
> ULAs have a nice feature that GUAs don't: your stack won't choose a ULA as
> a source when the destination is a GUA.   If they get a GUA from RIPE, they
> lose that feature.
[Bing] This is a very good point. In current draft, we proposed to use ULA+GUA for separated local and global communication, and pointed out the address selection issue. But we didn't make an explicit comparison that "ULA+GUA" prefers "GUA1+GUA2" because of the address selection policy.
We'll add some description of it. Thanks Ted for pointing it out.

Regards,
Bing
 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email