IETF Logo Mail Archive

Re: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 13 November 2013 01:55 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F35C11E816F for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2013 17:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.451
X-Spam-Level:
X-Spam-Status: No, score=-6.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsisYa+TGaKa for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2013 17:55:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C0CE411E816D for <v6ops@ietf.org>; Tue, 12 Nov 2013 17:55:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXU97515; Wed, 13 Nov 2013 01:55:25 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 13 Nov 2013 01:55:10 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 13 Nov 2013 01:55:25 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.252]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 13 Nov 2013 09:55:20 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
Thread-Index: AQHO2k/wLQNmfJ8fNUS0872S7bWPwZoWa54AgAAChYCACxV9gIAA6LLQ
Date: Wed, 13 Nov 2013 01:55:19 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7F3192@nkgeml506-mbx.china.huawei.com>
References: <CAFU7BAR3C8FwU49CsWua20Tmz24Jzd6UVuN=Aoea8Z03drvELQ@mail.gmail.com> <CALo9H1b1EFtjExsy89gLtPmWPoYc1DqmigfLrybPdxm0OsKKdw@mail.gmail.com> <52793827.2040708@gmail.com> <21C0A698-E56B-4B0B-8454-1323027AD04E@cisco.com>
In-Reply-To: <21C0A698-E56B-4B0B-8454-1323027AD04E@cisco.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
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Nov 2013 01:55:38 -0000

Hi, Fred

> </chair>
> 
> I'm told that it goes beyond that. There are at least three "directions" in the
> split:
[Bing] Did you mean you are told from some real deployment, or told from the ULA draft?

>    - inside, where internal-only names are advertised, might use an
> internal-only prefix, and even "outside" names might have different servers
> and different addresses.
>    - outside, where internal-only names are not advertised
>    - partner, which is "outside" plus some names made accessible to the
> partner, and may imply some form of b2b routing as well.
[Bing] Say if ULAs are used for b2b private routing, in the "partner" case, does it means the b2b ULAs are stored in the outside DNS, so that the partners could get the ULAs through public DNS, and access to the ULAs through private routing?

Best Regards,
Bing

v2.23.0 | Report a Bug | By Email