IETF Logo Mail Archive

Re: [v6ops] ULA draft revision #2 Regarding isolated networks

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 27 May 2014 15:28 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2781A0428 for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 08:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.872
X-Spam-Level:
X-Spam-Status: No, score=-1.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Maig5iE_T70s for <v6ops@ietfa.amsl.com>; Tue, 27 May 2014 08:28:05 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967451A0137 for <v6ops@ietf.org>; Tue, 27 May 2014 08:28:04 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s4RFRxb3019423; Tue, 27 May 2014 16:27:59 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s4RFRxb3019423
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1401204479; bh=5pwiz1553V9KNN86R8WTxmQRUSQ=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=bUGYAnsRTVgPuVAz53gNh/ExtfeYJ4madm7XKVOmyQRn2/KeZn/HJsnyvEYnuXDFi jTgHCp0xkvf3pGM9eNqYPQrM0SnZbPO8OD69qbyfEmMXeQiJx04aO0We/42PeBtwuG VtYqS/MDYFPUjbEeL0NzsQTr4/zgsWbDaYMYU4Gc=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q4QGRx0546013735S8 ret-id none; Tue, 27 May 2014 16:27:59 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s4RFRxrs025528 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 27 May 2014 16:27:59 +0100
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <3CD5F864-EF19-49B4-9103-BD134C39C842@nominum.com>
Date: Tue, 27 May 2014 16:27:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|00928d08683d2c9be54bb8de01c0e0fdq4QGRx03tjc|ecs.soton.ac.uk|9501818D-AD68-4ACF-9FA8-3EB2C3479062@ecs.soton.ac.uk>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6B9A@nkgeml506-mbx.china.huawei.com> <m261ks7xww.wl%randy@psg.com> <53840070.90801@gmail.com> <m2y4xn7wep.wl%randy@psg.com> <53840723.8010606@gmail.com> <CAKD1Yr1O_poMR200sjU=ttRvGaeQRkC1ZfXC0Ok4uQxdq3K=NQ@mail.gmail.com> <m2mwe37tbn.wl%randy@psg.com> <CAKD1Yr2t3-vxuG=iDi4biBNFpJwuzuHgfpB74i_uydWWRV7qZg@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D8B6E02@nkgeml506-mbx.china.huawei.com> <m2fvjv7q4h.wl%randy@psg.com> <m1WpDcc-0000BMC@stereo.hq.phicoh.net> <43BB867C-7BCA-45F6-8ADC-A49B34D6C0DC@nominum.com> <m1WpHrp-0000BQC@stereo.hq.phicoh.net> <9DB71B37-999E-4F7F-A7DA-6B243574E818@nominum.com> <m1WpISc-0000CGC@stereo.hq.phicoh.net> <EFD7A8B5-7A9D-4135-8DE1-7835D9CE4903@nominum.com> <m1WpIj0-0000BNC@stereo.hq.phicoh.net> <3CD5F864-EF19-49B4-9103-BD134C39C842@nominum.com> <9501818D-AD68-4ACF-9FA8-3EB2C3479062@ecs.soton.ac.uk>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1878.2)
X-smtpf-Report: sid=q4QGRx054601373500; tid=q4QGRx0546013735S8; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s4RFRxb3019423
X-ECS-MailScanner: Found to be clean
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/yZ_OyJGq4A72Y4NguyVt7KttZF8
Cc: Philip Homburg <pch-v6ops-3a@u-1.phicoh.com>, v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] ULA draft revision #2 Regarding isolated networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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, 27 May 2014 15:28:06 -0000

On 27 May 2014, at 16:01, Ted Lemon <ted.lemon@nominum.com> wrote:

> On May 27, 2014, at 10:51 AM, Philip Homburg <pch-v6ops-3a@u-1.phicoh.com> wrote:
>> Hmm. What RFC changed that? I looked at RFC-6724, but that still considers ULAs as
>> a special case of global scope. (Section 3.1 "Also, note that ULAs are considered as
>> global, not site-local, [...]")
> 
> Read section 10.   I'm not sure if/where there's a clear normative requirement that ULAs be treated as less preferable than GUAs, but they are definitely treated that way by stacks I've used.   I have a ULA configured on my home network, and none of the IPv6-capable devices in the home have trouble getting out to the internet.

As you say Ted, RFC6724 observes the scope of ULAs being what it is, but in the part Philip quotes the rest of the sentence replacing the “…” reads “... but are handled via the prefix policy table as discussed in Section 10.6.)”   Any system that is 6724-compliant should prefer globals over ULAs, unless the policy table has been modified. This issue was discussed in some depth in homenet.

> ULAs are global in scope in the sense that they are (notionally) unique across the internet, but not in the sense that they are globally reachable.

Perhaps (probabilistically) rathr than (notionally).

Tim

v2.23.0 | Report a Bug | By Email