From: Ted Lemon <mellon@fugue.com>
Message-Id: <CAF32DC6-8EF3-4D5D-8D81-9A6B3F9F319C@fugue.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_6F4C01BD-1B0F-47C9-8A9F-96D182223DBF"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 11 Nov 2017 12:00:09 +0800
In-Reply-To: <6BA4A174-FCE5-4A28-8E9A-B1CAF8685264@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>,
 "6man@ietf.org" <6man@ietf.org>,
 "6man-ads@tools.ietf.org" <6man-ads@ietf.org>,
 "v6ops-ads@ietf.org" <v6ops-ads@ietf.org>,
 draft-ietf-v6ops-unique-ipv6-prefix-per-host@tools.ietf.org
To: DY Kim <dykim6@gmail.com>
References: <be9724f5-2ff5-d90c-2749-ecae2c628b78@si6networks.com>
 <CAKD1Yr0_a2Qm8U4oK+BQU57DeDUD9i-o_+G+YhnH4pVXRxmxxQ@mail.gmail.com>
 <BBB987EF-D91C-4FD1-9084-21382F24E7BF@gmail.com>
 <37b58331-ecfc-aaf8-bde4-91dd4d375834@si6networks.com>
 <029B5A33-0C3F-4021-BA86-50E6DF37F879@gmail.com>
 <59F47233-62ED-489D-9421-00128C8E7EB2@fugue.com>
 <D36B8133-7258-4EDD-8CA9-85B574D095BC@gmail.com>
 <F5C714A6-4987-465F-9154-6D1E39394511@fugue.com>
 <6BA4A174-FCE5-4A28-8E9A-B1CAF8685264@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/w0s5tDQqbBk5uhDGQg6TwwWQxSk>
Subject: Re: [v6ops] Stateful SLAAC
 (draft-ietf-v6ops-unique-ipv6-prefix-per-host)
Precedence: list


--Apple-Mail=_6F4C01BD-1B0F-47C9-8A9F-96D182223DBF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 11, 2017, at 11:57 AM, DY Kim <dykim6@gmail.com> wrote:
> That the router has to preserve the prefix(es) applies the same to =
both SLAAC and DHCP. The draft has not brought anything new/strange to =
the usual behavior of the router in association with SLAAC.

Not correct.   In the case where we are not doing unique prefix per =
host, the prefix is static.   In a sense it's stateful, in that it is =
configured on the router, but there is no binding between the host and =
the prefix.   With unique prefix per host, the router has to have a =
bunch of prefixes, each of which is allocated to a specific host.   =
These allocations are dynamic, have lifetimes, and need to be managed.   =
It is simply not the case that the default behavior and the new behavior =
are analogous.


--Apple-Mail=_6F4C01BD-1B0F-47C9-8A9F-96D182223DBF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Nov 11, 2017, at 11:57 AM, DY Kim &lt;<a =
href=3D"mailto:dykim6@gmail.com" class=3D"">dykim6@gmail.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">That the router has =
to preserve the prefix(es) applies the same to both SLAAC and DHCP. The =
draft has not brought anything new/strange to the usual behavior of the =
router in association with SLAAC.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">Not =
correct. &nbsp; In the case where we are not doing unique prefix per =
host, the prefix is static. &nbsp; In a sense it's stateful, in that it =
is configured on the router, but there is no binding between the host =
and the prefix. &nbsp; With unique prefix per host, the router has to =
have a bunch of prefixes, each of which is allocated to a specific host. =
&nbsp; These allocations are dynamic, have lifetimes, and need to be =
managed. &nbsp; It is simply not the case that the default behavior and =
the new behavior are analogous.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_6F4C01BD-1B0F-47C9-8A9F-96D182223DBF--