IETF Logo Mail Archive

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

Jen Linkova <furry13@gmail.com> Tue, 05 November 2013 17:53 UTC

Return-Path: <furry13@gmail.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 C3C8321F9E91 for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 09:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 drLsley2F8E8 for <v6ops@ietfa.amsl.com>; Tue, 5 Nov 2013 09:53:05 -0800 (PST)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id D9E3621F9D19 for <v6ops@ietf.org>; Tue, 5 Nov 2013 09:50:53 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id x12so5046343qcv.28 for <v6ops@ietf.org>; Tue, 05 Nov 2013 09:50:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=67C5OCEzVMes86iHkWZ3j7Q4aj6jD8ld/q6xvNjq+r4=; b=QSq5bOCEFWVylErmBGzX1YxFLJbPlzL3QvOL5SSTjvtv1e3t9u5u2maNInImYMc+D0 hUg2dZJ2MVtoHG7yPCU7h+CvPU04kPmUzg5oSzTKwmrPztrMq3EtYU+iSK4euwwER8eR oo28zsrTlGpbnJwp8AqSBXaHSUEXTipjBaHldtSskT8qNEOewayDDz3Dlx7+WdtYsLZY 3FdPYjs1BgxWx9E8mLcHGGXgJcurwhM9nJc9tb80Eg54BVVRS4Hw/4w77ydJkA54IhWb w5E+E66aJuTb4PGLjxy4EUlSq4K6tg6B4NmNQhMU564Mx1J68HJwuqakp3Ib4jjfUfCc E+Zg==
X-Received: by 10.224.129.74 with SMTP id n10mr30887120qas.92.1383673852637; Tue, 05 Nov 2013 09:50:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.100.195 with HTTP; Tue, 5 Nov 2013 09:50:32 -0800 (PST)
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 05 Nov 2013 18:50:32 +0100
Message-ID: <CAFU7BAR3C8FwU49CsWua20Tmz24Jzd6UVuN=Aoea8Z03drvELQ@mail.gmail.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [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 17:53:06 -0000

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

v2.23.0 | Report a Bug | By Email