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

"Liubing (Leo)" <leo.liubing@huawei.com> Thu, 14 November 2013 08:18 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 1B1A721F9FAE for <v6ops@ietfa.amsl.com>; Thu, 14 Nov 2013 00:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.457
X-Spam-Level:
X-Spam-Status: No, score=-6.457 tagged_above=-999 required=5 tests=[AWL=0.143, 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 2EHvWeq1g7FL for <v6ops@ietfa.amsl.com>; Thu, 14 Nov 2013 00:18:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 13D3A21F9005 for <v6ops@ietf.org>; Thu, 14 Nov 2013 00:18:41 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAG61304; Thu, 14 Nov 2013 08:18:40 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 Nov 2013 08:17:38 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 Nov 2013 08:18:23 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.252]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 14 Nov 2013 16:18:16 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Thread-Topic: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
Thread-Index: AQHO2k/wLQNmfJ8fNUS0872S7bWPwZoWa54AgAAChYCACxV9gIAA6LLQgAAhCwCAAeDVwA==
Date: Thu, 14 Nov 2013 08:18:15 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7F364B@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> <8AE0F17B87264D4CAC7DE0AA6C406F453D7F3192@nkgeml506-mbx.china.huawei.com> <0CF7584E-B62C-4BB1-B1E2-B8E89BE1B83D@cisco.com>
In-Reply-To: <0CF7584E-B62C-4BB1-B1E2-B8E89BE1B83D@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: Thu, 14 Nov 2013 08:18:48 -0000

Hi Fred,

Thanks for your detailed explain. It is very useful information.
I'll consider to include it in the next version.

Best regards,
Bing

> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Wednesday, November 13, 2013 7:33 PM
> To: Liubing (Leo)
> Cc: Brian E Carpenter; v6ops@ietf.org
> Subject: Re: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
> 
> 
> On Nov 12, 2013, at 5:55 PM, Liubing (Leo) <leo.liubing@huawei.com>
> wrote:
> 
> > 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?
> 
> I am on the board of a company that produces a product that is used in these
> configurations. One of the engineers told me it is a requirement his
> customers present him with. Today, that is generally IPv4, not IPv6, so I can't
> comment on ULAs, only extrapolate. I was commenting on the DNS
> configuration.
> 
> >>   - 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?
> 
> In the particular configuration, as I understand what the engineer told me,
> "inside", "outside", and in the "partner" case, the identity of the partner, are
> attributes in the underlying database. The software looks at the request,
> determines what data should be included in the response, and includes it.