Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.txt

Tore Anderson <tore@fud.no> Thu, 30 July 2015 17:16 UTC

Return-Path: <tore@fud.no>
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 754921ACCFF for <v6ops@ietfa.amsl.com>; Thu, 30 Jul 2015 10:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 fblEWfOu-iOg for <v6ops@ietfa.amsl.com>; Thu, 30 Jul 2015 10:16:39 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43CF81ACCFE for <v6ops@ietf.org>; Thu, 30 Jul 2015 10:16:39 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=44808 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1ZKrRW-0004LV-Fb; Thu, 30 Jul 2015 19:16:30 +0200
Date: Thu, 30 Jul 2015 19:16:29 +0200
From: Tore Anderson <tore@fud.no>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-ID: <20150730191629.1817894a@envy.fud.no>
In-Reply-To: <2134F8430051B64F815C691A62D9831832ED2A37@XCH-BLV-504.nw.nos.boeing.com>
References: <20150723130715.12113.47480.idtracker@ietfa.amsl.com> <20150727091241.GL84167@Space.Net> <m1ZJfOr-0000CgC@stereo.hq.phicoh.net> <C9C3FBC4-44F3-45D2-B8C4-3725396E5D40@nominum.com> <CAPi140Mx96dBgeaCkrsDD+-J85OZDo5Di+gHTBiaGDzYK2us4w@mail.gmail.com> <20150728115944.GZ84167@Space.Net> <CAPi140PKh64L=nr96pv3dn7FO_Y9pW162YzBT8kZHSMsedGYtQ@mail.gmail.com> <BE811683-3BBA-40F0-B047-282DA7E774AA@nominum.com> <CAKD1Yr3pHBRk+BTOJOOSC=c6M4FNaumGEKwHvFW=ThED7M744g@mail.gmail.com> <4AB2ED61-23CF-40D5-B2A6-F1F4064EC0C6@nominum.com> <CAKD1Yr3-omr_M7pU9TgoECGnTGf-ta64UcE8ddbAom-rB8exZA@mail.gmail.com> <90E6B48E-B3FC-4AAD-B356-7D92A2777632@nominum.com> <m1ZK99A-0000DCC@stereo.hq.phicoh.net> <804F2F0B-B0EF-4054-99C5-C0CD8957C434@nominum.com> <m1ZK9Qp-0000CWC@stereo.hq.phicoh.net> <2134F8430051B64F815C691A62D9831832ED2 9AC@XCH-BLV-504.nw.nos.boeing.com> <m1ZKpuC-0000D4C@stereo.hq.phicoh.net> <2134F8430051B64F815C691A62D9831832ED2A37@XCH-BLV-504.nw.nos.boeing.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/GN-C4Fm0LZpQFmyOGOMKPSbZF6s>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-colitti-v6ops-host-addr-availability-01.txt
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: <https://mailarchive.ietf.org/arch/browse/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, 30 Jul 2015 17:16:40 -0000

* Templin, Fred L

> You can't give a device a /64 using SLAAC; SLAAC only allows for
> autoconfiguration of singleton addresses taken from an on-link
> /64 prefix.

Hi Fred,

Actually, SLAAC works equally well with off-link prefixes. There is no
inherent requirement in SLAAC that prefixes from which the addresses
are auto-configured must be on-link; the L and A bits in an RA's PIO
are completely orthogonal.

> If you want to give a device a /64, the only choices
> I am aware of are administrative configuration or DHCPv6 PD.

True, although 3GPP networks is an exception. There a /64 prefix
advertised to the UE via standard RA/PIO with SLAAC can be treated as
if it was a delegated prefix. RFC7278 depends on this.

Tore