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

Mark Andrews <marka@isc.org> Tue, 05 November 2013 19:58 UTC

Return-Path: <marka@isc.org>
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 35D2921F9BA4 for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 11:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.824
X-Spam-Level:
X-Spam-Status: No, score=-6.824 tagged_above=-999 required=5 tests=[AWL=3.175, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
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 YwL6yrehBOqG for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 11:58:40 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7A421E8097 for <v6ops@ietf.org>; Tue, 5 Nov 2013 11:58:37 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 664AA2383D9; Tue, 5 Nov 2013 19:58:22 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id CC41D160485; Tue, 5 Nov 2013 20:04:05 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 71201160484; Tue, 5 Nov 2013 20:04:05 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 957B0992B25; Wed, 6 Nov 2013 06:58:18 +1100 (EST)
To: George Michaelson <ggm@algebras.org>
From: Mark Andrews <marka@isc.org>
References: <CAFU7BAR3C8FwU49CsWua20Tmz24Jzd6UVuN=Aoea8Z03drvELQ@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D7F090A@nkgeml506-mbx.china.huawei.com> <CAKr6gn2P5R2W8Paihdc78tCpPnUE6Zo0HbrdtqFSKS4fZsHb8w@mail.gmail.com>
In-reply-to: Your message of "Tue, 05 Nov 2013 11:29:43 -0800." <CAKr6gn2P5R2W8Paihdc78tCpPnUE6Zo0HbrdtqFSKS4fZsHb8w@mail.gmail.com>
Date: Wed, 06 Nov 2013 06:58:18 +1100
Message-Id: <20131105195818.957B0992B25@rock.dv.isc.org>
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 19:58:45 -0000

In message <CAKr6gn2P5R2W8Paihdc78tCpPnUE6Zo0HbrdtqFSKS4fZsHb8w@mail.gmail.com>
, George Michaelson writes:
> 
> I tend to SHOULD. you can do what you like, but the consequence of not
> doing a local delegation is information leakage. There is no compelling MUST

And if you have random address selection you along with random
prefix selection you have a 2^114 birthday paradox space.  I'll
assume the subnet are not random.

You have a 2^40 birthday paradox space of a getting sub optimal
address selection order.  i.e. you will try the ULA before GUA.

> On Tue, Nov 5, 2013 at 11:28 AM, Liubing (Leo) <leo.liubing@huawei.com>wrote:
> 
> > Hi, Jen
> >
> > I got your comments. I'll consider to revise accordingly. Many thanks
> >
> > Regards,
> > Bing
> >
> > ________________________________________
> > From: v6ops-bounces@ietf.org [v6ops-bounces@ietf.org] on behalf of Jen
> > Linkova [furry13@gmail.com]
> > Sent: Tuesday, November 05, 2013 09:50
> > To: v6ops@ietf.org
> > Subject: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis
> >
> > 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
> >
> 
> --047d7b33da0a02fb4e04ea730e22
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr">I tend to SHOULD. you can do what you like, but the conseq=
> uence of not doing a local delegation is information leakage. There is no c=
> ompelling MUST</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_=
> quote">
> On Tue, Nov 5, 2013 at 11:28 AM, Liubing (Leo) <span dir=3D"ltr">&lt;<a hre=
> f=3D"mailto:leo.liubing@huawei.com" target=3D"_blank">leo.liubing@huawei.co=
> m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
> n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> Hi, Jen<br>
> <br>
> I got your comments. I&#39;ll consider to revise accordingly. Many thanks<b=
> r>
> <br>
> Regards,<br>
> Bing<br>
> <br>
> ________________________________________<br>
> From: <a href=3D"mailto:v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a> =
> [<a href=3D"mailto:v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a>] on b=
> ehalf of Jen Linkova [<a href=3D"mailto:furry13@gmail.com">furry13@gmail.co=
> m</a>]<br>
> 
> Sent: Tuesday, November 05, 2013 09:50<br>
> To: <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
> Subject: [v6ops] comment on draft-liu-v6ops-ula-usage-analysis<br>
> <div class=3D"HOEnZb"><div class=3D"h5"><br>
> Section 4.2. says that<br>
> &quot;<br>
> <br>
> So when using ULAs in a network, the administrators should clearly<br>
> =A0 =A0set the scope of the ULAs and configure ACLs on relevant border<br>
> =A0 =A0routers to block them out of the scope. And if internal DNS are<br>
> =A0 =A0enabled, the administrators might also need to use internal-only DNS=
> <br>
> =A0 =A0names for ULAs.<br>
> &quot;<br>
> I believe it should that that the administrator MUST configure egress<br>
> ACLs on borders routers and MUST ensure that their DNS servers do not<br>
> include ULAs in any responses to external clients.<br>
> <br>
> <br>
> <br>
> <br>
> --<br>
> SY, Jen Linkova aka Furry<br>
> _______________________________________________<br>
> v6ops mailing list<br>
> <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
> <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
> ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
> _______________________________________________<br>
> v6ops mailing list<br>
> <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
> <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
> ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
> </div></div></blockquote></div><br></div>
> 
> --047d7b33da0a02fb4e04ea730e22--
> 
> --===============5663455589702191862==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 
> --===============5663455589702191862==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org