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: Pekka Savola <pekkas at netcore.fi>
- Date: Tue, 30 Sep 2008 20:07:08 +0300 (EEST)
- Cc: Alexandru Petrescu <alexandru.petrescu at gmail.com>, IETF IPv6 Mailing List <ipv6 at ietf.org>, 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>, "Martin, Cynthia E." <cemartin 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>
- Delivered-to: ietfarch-ipv6-web-archive at core3.amsl.com
- Delivered-to: ipv6 at core3.amsl.com
- In-reply-to: <48E24F78.70004 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>
- 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>
- Sender: ipv6-bounces at ietf.org
- User-agent: Alpine 2.00 (LRH 1167 2008-08-23)
On Tue, 30 Sep 2008, Brian Dickson wrote:
Dunn, Jeffrey H. wrote:
My basic question is: What basic engineering problem is solved by
proscribing non-64 bit prefixes?
If the non-64 prefixes had not been proscribed, we wouldn't have been
able to use the existing engineering method to develop CGA/SEND
specifications. These are being leveraged in SHIM6 and potentially in
other applications as well. Likely we couldn't even solve these
engineering problems (at least without major drawbacks/other
assumptions) if we couldn't have made assumptions about the
widely-used prefix length.
That said, I personally use non-64 bit prefixes on point-to-point
links between routers, but I have done so willingly and knowing that
if the IETF develops anything fancy new stuff, I might not be able to
use it or I might need to renumber.
When managing such a scheme alongside an IPv6 prefix which needs to
be assigned to the same set of servers, which are all dual-stack,
the *number* of prefixes, their *relative* numbering, and the host
*addresses* within the prefixes, it is quickly apparent that use of
only /64 prefixes makes for a management nightmare, particularly if
renumbering of prefixes and/or servers occurs, e.g. re-balancing the
VLSM arrangement itself in IPv4-land.
I don't understand why *relative* numbering (i.e: overlapping subnet
masks) is important in IPv6, and I'm not sure if I see the case even
for v4. Could you enlighten me?
I assume you refer to a scenario where on the same broadcast domain
there are hosts which are configured with say A.B.C.0/24 length, and
some others are configured with, say, A.B.C.D/28 prefix length.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
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.