Re: [Int-area] Review of draft-narten-ipv6-3177bis-48boundary-05

Fred Baker <fred@cisco.com> Fri, 20 August 2010 23:00 UTC

Return-Path: <fred@cisco.com>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 898CD3A67FA for <int-area@core3.amsl.com>; Fri, 20 Aug 2010 16:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.182
X-Spam-Level:
X-Spam-Status: No, score=-110.182 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6FYSnGIr5qVq for <int-area@core3.amsl.com>; Fri, 20 Aug 2010 16:00:07 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id ADDAC3A67FB for <int-area@ietf.org>; Fri, 20 Aug 2010 16:00:07 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAqmbkyrR7Ht/2dsb2JhbACgOnGfOJtRhTcEhDSFPw
X-IronPort-AV: E=Sophos;i="4.56,242,1280707200"; d="scan'208";a="243197217"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 20 Aug 2010 23:00:38 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o7KN0UFh003888; Fri, 20 Aug 2010 23:00:32 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 20 Aug 2010 16:00:37 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 20 Aug 2010 16:00:37 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F1058062E716@EUSAACMS0701.eamcs.ericsson.se>
Date: Fri, 20 Aug 2010 16:00:24 -0700
Message-Id: <FE3A892F-DF2F-407A-88D8-54ABF7221308@cisco.com>
References: <D74F3837-E115-49FB-A9AB-5E0C53406621@tony.li> <C0AC8FAB6849AB4FADACCC70A949E2F1058062E62F@EUSAACMS0701.eamcs.ericsson.se> <188C11C5-CDBA-4213-83AC-453AE06ADAD5@cisco.com> <4C6EE713.9080805@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F1058062E716@EUSAACMS0701.eamcs.ericsson.se>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ops.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] Review of draft-narten-ipv6-3177bis-48boundary-05
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Aug 2010 23:00:08 -0000

On Aug 20, 2010, at 2:55 PM, Eric Gray wrote:

> 	Following the CIDR model for IPv6 seems to allow for as
> many as (on the order of) 7-10 times as many possibly usable
> address allocation sizes.

Well, yes, saying that "you can pick any length you like" gives the address allocation authorities, at least in theory, 64 orders of magnitude.

There is a line of reasoning, which I subscribe to, that all of those options really aren't needed, and that there are human factors reasons to prefer prefix lengths on nibble (hex digit) boundaries. Not that allocations like 192.0.2.20/30 are impossible to grok - they're not - but if we have the opportunity to simplify things, why not?

One comment that comes to mind is a recent conversation with my son. He works for a company that makes radio-controlled model airplanes, the kind that have a 66 foot wingspan and shoot missiles. The planes are full of computers, and no they don't ask the DNS root to translate names. If you're in one of those computers and need to talk with another one, you need to know its IP address. So he is used to being in computer A and logging into computer B as 192.0.2.17 or whatever.

He and I spoke a few weeks about, and he asked "Dad, when you guys were designing IPv6, did you think at all about how LONG those addresses were?"

ta-dum!

Now ask yourself about being in my daughter's network (women enter her home as the girl-next-door and leave beautiful), telling her that she can use anything she likes in 2001:0db8:2775:1234/62, and having her notice that the address of something or another is 2001:0db8:2775:1235... In IPv4, I said "deal with it, you have to be somewhat technical". In IPv6, I would like to not have to go there. It's not her expertise, and she doesn't ask me to cut/color her hair either.

So, yes, I tend to think that the common rabble should deal with addresses that break on nibble boundaries.

That has nothing to do with RIRs or service providers, mind you; they are often "somewhat technical". Within their networks I expect them to do what makes sense to them, and I regard myself more as their student than their teacher...