Re: what problem is solved by proscribing non-64 bit prefixes?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: what problem is solved by proscribing non-64 bit prefixes?
- To: Brian Dickson <briand at ca.afilias.info>
- Subject: Re: what problem is solved by proscribing non-64 bit prefixes?
- From: Brian E Carpenter <brian.e.carpenter at gmail.com>
- Date: Wed, 01 Oct 2008 09:23:25 +1300
- Cc: Alexandru Petrescu <alexandru.petrescu at gmail.com>, IETF IPv6 Mailing List <ipv6 at ietf.org>, Pekka Savola <pekkas at netcore.fi>, Ron Bonica <rbonica at juniper.net>, Steve_Eiserman at ao.uscourts.gov, Pasi Eronen <Pasi.Eronen at nokia.com>, "Sherman, Kurt T." <ksherman at mitre.org>, draft-ietf-v6ops-addcon at tools.ietf.org, ralph.liguori at disa.mil, night at nist.gov, dougm at nist.gov, V6ops Chairs <v6ops-chairs at tools.ietf.org>, "Martin, Cynthia E." <cemartin at mitre.org>
- Delivered-to: ietfarch-ipv6-web-archive at core3.amsl.com
- Delivered-to: ipv6 at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=UthEqnvTn7dqwsYb9H/U5i0L3sAOhgTcl5jG8a/f7U0=; b=cCmaBmhLJAg+2qGJ6JJ9yk/VnoYU6gXHJm3hopKP/5p7K9ZmrHpKABT8uZ6Nm7Z6Gu pDGLslKYfea39tFwGcQS+HP2l0jrayaMouirBHaklyuGYgXyF0fGZklr4FMX7PFd1usY 7RHANWjqk4VWvnDIVitqRvYupmErgiezxToz4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=in0r+plYzLQjQefoCWpGzPg3yqABk98Arw5JIZQUdLj5udi7opDKtQM/nnrJrJ0b55 Znl+vL9lvA/WBZzIAxqrCJ681FAQeQLYYgLdGh2Qo3ovzCdiQLi5RDXVBhwxUQ8meiVG qdb7pThSbGgxCKttYDZ8Y66xIFzDOO+gT7jm4=
- In-reply-to: <48E27D57.7040807 at ca.afilias.info>
- List-archive: <https://www.ietf.org/mailman/private/ipv6>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
- Organization: University of Auckland
- References: <48DB374B.1000308 at piuha.net> <0AC4B700F00DBB4C94F95727E0991414014B2441 at IMCSRV7.MITRE.ORG> <48E230D5.3040204 at gmail.com> <0AC4B700F00DBB4C94F95727E0991414014B24D2 at IMCSRV7.MITRE.ORG> <48E24F78.70004 at ca.afilias.info> <alpine.LRH.2.00.0809301958310.20045 at netcore.fi> <48E27D57.7040807 at ca.afilias.info>
- Sender: ipv6-bounces at ietf.org
- User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
On 2008-10-01 08:26, Brian Dickson wrote:
...
> we would ideally also have corresponding IPv6 subnets that are
> algorithmically derived from the IPv4 subnets.
I used to think that was a good way to design an initial
IPv6 addressing plan. But from helping people design a real
addressing plan for a real campus with many years of IPv4
history, I've reached the conclusion that it's a really bad idea.
It's much better to design a clean IPv6 plan from the ground up,
rather than sweeping up the messy history of the IPv4 plan.
If you design a clean IPv6 plan that way, there doesn't seem to be
any incentive whatever to use anything other than /64 as
subnet prefixes (except for the router-router links, as Pekka
mentioned). There's a strong incentive in favour of /64,
i.e. the ability to use SLAAC, privacy addresses, and CGAs.
Brian C
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.