Re: router behaviour with prefixes longer than /64

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 18 March 2014 07:37 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4EC41A0281 for <ipv6@ietfa.amsl.com>; Tue, 18 Mar 2014 00:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 KwRWM7T_35xw for <ipv6@ietfa.amsl.com>; Tue, 18 Mar 2014 00:37:22 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA1C1A0368 for <ipv6@ietf.org>; Tue, 18 Mar 2014 00:37:22 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id x13so5608706wgg.14 for <ipv6@ietf.org>; Tue, 18 Mar 2014 00:37:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=paekxUFP+w5/5Q1jxFn9XCbKfzWJWYmh+jXWrOPVlg8=; b=Tsp5d5kOwZI00tq7uhaQ4Du3C+Y7x2Tx2cmNJumGPqXE/d1692Qsw8wLm2gaQYCT3q MqM5dDktRiXBkta9FqmsWquHsHYSThoeqT2EZ+2o+/Q+vTbbbmhUnDasnxOgTlTbm9z0 yq/SBSGdxnl1IlBb84sFTkvd4uWtQLApNY/lCSr+SZ1tJ/2Tg52G8BZoIOV7vKcYrNhv 68Hu09Zp+nagYzR7aE6MY5l7O2dZSA2Xnc0HnyeEZAGMIQeJvHKZuVsvEqRLmVluo5QD 6IFYWhr+abt03Xdm3dAZq1gUbegCBQg3hRuW5B7I7sp5XZlTgUWwdTEnKl0isAjCB0F+ mvtw==
X-Received: by 10.180.211.239 with SMTP id nf15mr13315418wic.9.1395128233922; Tue, 18 Mar 2014 00:37:13 -0700 (PDT)
Received: from [192.168.0.6] (cpc8-mort6-2-0-cust102.croy.cable.virginm.net. [82.43.108.103]) by mx.google.com with ESMTPSA id 19sm44835641wjy.17.2014.03.18.00.37.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Mar 2014 00:37:13 -0700 (PDT)
Message-ID: <5327F7AD.4080909@gmail.com>
Date: Tue, 18 Mar 2014 20:37:17 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Usman Latif <osmankh@yahoo.com>
Subject: Re: router behaviour with prefixes longer than /64
References: <A0A90E3A-50C3-4A28-A33C-CE1882E57967@yahoo.com>
In-Reply-To: <A0A90E3A-50C3-4A28-A33C-CE1882E57967@yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8s9Z83KWqMX1rgkIhHeWr5de6m8
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 07:37:24 -0000

On 18/03/2014 10:55, Usman Latif wrote:
> I think (although not sure if such a method exists today) that if there was a way to identify looking at specific (reserved?) bits in the upper 64-bit portion of the IPv6 address to tell the routing system whether the lower 64-bits are IID or not, that would probably give best of both worlds to IPv6 addressing and provide a more efficient use of address space..

No, we are definitely not going to waste bits in the routing prefix for this.

   Brian