IETF Logo Mail Archive

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

"Liubing (Leo)" <leo.liubing@huawei.com> Tue, 05 November 2013 18:47 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 73DCB11E8210 for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 10:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.151
X-Spam-Level:
X-Spam-Status: No, score=-6.151 tagged_above=-999 required=5 tests=[AWL=-0.152, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 HkCm15Sf6ghP for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 10:46:52 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4979011E8215 for <v6ops@ietf.org>; Tue, 5 Nov 2013 10:46:00 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZX56832; Tue, 05 Nov 2013 18:45:48 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 5 Nov 2013 18:45:07 +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; Tue, 5 Nov 2013 18:45:48 +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; Wed, 6 Nov 2013 02:45:43 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Arturo Servin <arturo.servin@gmail.com>
Thread-Topic: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
Thread-Index: AQHO2k/wLQNmfJ8fNUS0872S7bWPwZoWa54AgAAChYCAAItPAw==
Date: Tue, 05 Nov 2013 18:45:42 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D7F086C@nkgeml506-mbx.china.huawei.com>
References: <CAFU7BAR3C8FwU49CsWua20Tmz24Jzd6UVuN=Aoea8Z03drvELQ@mail.gmail.com> <CALo9H1b1EFtjExsy89gLtPmWPoYc1DqmigfLrybPdxm0OsKKdw@mail.gmail.com>, <52793827.2040708@gmail.com>
In-Reply-To: <52793827.2040708@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.132.36]
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: Tue, 05 Nov 2013 18:47:09 -0000

Hi, Brian

Thanks for your explanation, that is what the draft means.
It might needs re-wording to make it clearer.

Regards,
Bing

________________________________________
From: v6ops-bounces@ietf.org [v6ops-bounces@ietf.org] on behalf of Brian E Carpenter [brian.e.carpenter@gmail.com]
Sent: Tuesday, November 05, 2013 10:25
To: Arturo Servin
Cc: v6ops@ietf.org
Subject: Re: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis

On 06/11/2013 07:16, Arturo Servin wrote:
> Blocking according to DNS content would be something like Deep Packet
> Inspection, isn't it?
>
> Do we want to go there?

No, but that's not what he means. He means split DNS, where
the internal DNS server includes records that are not present
in the external DNS server. That, like it or not, is standard
practice today in many enterprise networks.

   Brian

>
> /as
>
>
> On Tue, Nov 5, 2013 at 3:50 PM, Jen Linkova <furry13@gmail.com> wrote:
>
>> Section 4.2. says that
>> "
>>
>> So when using ULAs in a network, the administrators should clearly
>>    set the scope of the ULAs and configure ACLs on relevant border
>>    routers to block them out of the scope. And if internal DNS are
>>    enabled, the administrators might also need to use internal-only DNS
>>    names for ULAs.
>> "
>> I believe it should that that the administrator MUST configure egress
>> ACLs on borders routers and MUST ensure that their DNS servers do not
>> include ULAs in any responses to external clients.
>>
>>
>>
>>
>> --
>> SY, Jen Linkova aka Furry
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email