Re: draft-bourbaki-6man-classless-ipv6-00

David Farmer <farmer@umn.edu> Mon, 05 June 2017 20:05 UTC

Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7951293DA for <ipv6@ietfa.amsl.com>; Mon, 5 Jun 2017 13:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level:
X-Spam-Status: No, score=-3.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 0vQarQMlRJyW for <ipv6@ietfa.amsl.com>; Mon, 5 Jun 2017 13:05:31 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11303126CE8 for <ipv6@ietf.org>; Mon, 5 Jun 2017 13:05:31 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 8A2766BE for <ipv6@ietf.org>; Mon, 5 Jun 2017 20:05:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zCFYx6X2WO3 for <ipv6@ietf.org>; Mon, 5 Jun 2017 15:05:30 -0500 (CDT)
Received: from mail-ua0-f199.google.com (mail-ua0-f199.google.com [209.85.217.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 5700F85C for <ipv6@ietf.org>; Mon, 5 Jun 2017 15:05:30 -0500 (CDT)
Received: by mail-ua0-f199.google.com with SMTP id 44so22277370uae.2 for <ipv6@ietf.org>; Mon, 05 Jun 2017 13:05:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=V4I+10s/Sn+ak5S9ctbanYM9Z8eD1+JiWhDNUR0DR8s=; b=M2g56/6zUYP7UQ56XzTI1weRUPL53QBdJhkhz68ziDWh3bcVEm9sZv2/nnIoODvTbL vMUqtHjx4lsyL7sqT15PDIYukAthXOvnaSj46QlQPWXn+IYi5vRGskEmgBXbThuxM5Ak GwarYEDVWirQe3OOAC255g5tE8GsRaAnAxeIKtA/17DB4uJOPrB4ofe5Fxa3hoz5sa3F ubB2o7v3fbxGEMK6ZtjlhcTFN80vlUWVh8HvNfMeP0a36qjwMPDRlvWFs5SPJQsLYrKZ T2P73GpFbcIV9kJCfH/s4Yi64NUZlKpNYGMsT3/UTmrkw8y9jwZn2T+TDIjxLTCB5zd3 geag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=V4I+10s/Sn+ak5S9ctbanYM9Z8eD1+JiWhDNUR0DR8s=; b=UiHa8SAHeYvEoab0734sy1V3Ttyc7Mm6TKEzdGb702HkRa4mIypWxPUrTYZg1VOrXF PT9MqFoR9tNNvQoCF813NHYcti73GuGfUQdRAwN9Knsqz4YsPwE+tTjOrL8rRT9fyf38 3yKkpabhctSwhgzOsbGZw9wFdw+XcSThy+1tuoII2zuZqhxBJIJwkKhK10phqgbTG0VV nxDbNGKEwp/cCHImjEr9olxKYgyxv1voFdXA/1CjDw+oCvmI3NsI+FWpy7+icTLhEGFr bWDDb/1d56p7+Cc5eX+54GSc8IdTexdRumZP9Fh/bulBqndCA82pa0g8X7afg238QbuI S7wQ==
X-Gm-Message-State: AODbwcBwQMZe8uKlkNXTJKBB7KcK3F4F7AZpaOzDZp2D2TE75wWk5hN5 NF8o9dg9+RN9rXsgkJRAsS1cpY0cwNBbu9b0246wsrvp42QNEDQqXOPFA3rMxzA9DTwmVcuhdEP PXrrQpFsvPEuFhfI=
X-Received: by 10.176.23.201 with SMTP id p9mr10349071uaf.24.1496693129037; Mon, 05 Jun 2017 13:05:29 -0700 (PDT)
X-Received: by 10.176.23.201 with SMTP id p9mr10349065uaf.24.1496693128810; Mon, 05 Jun 2017 13:05:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.183.11 with HTTP; Mon, 5 Jun 2017 13:05:27 -0700 (PDT)
In-Reply-To: <CAKFn1SG0aY-1TtQx_HcFus+WxUO=nxHtVisv8f+_cSsAH1_9hA@mail.gmail.com>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <CAKFn1SEdjhsQ3tKPZdbdfF4ArDzw-FZfjQT68gV55Fc-5vzBvw@mail.gmail.com> <CAKD1Yr3ppM0UF8HoN8PgS7F0iEmK26ebiuJK=tkAdZnuLWpkZg@mail.gmail.com> <CAKFn1SHASt34ihJmGN0iRFQQzLTMspZfxXHgBjBatXXcRYF4cw@mail.gmail.com> <20170604093119.nt733rb3ymmjssww@Vurt.local> <m1dHTLx-0000DcC@stereo.hq.phicoh.net> <CAKD1Yr0ZZwRar6D-2bkXBKPYehqqW99+BMtDOjyovR8WDXKzxw@mail.gmail.com> <CAD6AjGTjikAWutcenW8qn7OW8kPM9c_x_yDUy5vQxJmXKL85dg@mail.gmail.com> <91c3c0f4-eb8b-cdf7-b9c9-7d1eecb7fe64@gmail.com> <CAKFn1SG0aY-1TtQx_HcFus+WxUO=nxHtVisv8f+_cSsAH1_9hA@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Mon, 05 Jun 2017 15:05:27 -0500
Message-ID: <CAN-Dau3M98r1M8zzQjnNyQsKOkFkLeCvzFaDFvpjvLsjRqyRTA@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Roger Jørgensen <rogerj@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="089e0820012448608105513c0619"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-Y6bQmXJOjLv7bUXs0gKWneubAo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 05 Jun 2017 20:05:32 -0000

On Mon, Jun 5, 2017 at 12:42 PM, Roger Jørgensen <rogerj@gmail.com> wrote:

>
> Also, I think I remember that most hardware are optimized around that
> /64 boundary, how will this affect newer chipset and hardware? Should they
> optimize their hardware to route anything from /8 to /128? Sounds very
> expensive and not something that will make IPv6 more popular.
>

I'm fine with systems being optimized for /64, they just can't ignore or
assume there will never be anything longer than /64. If they assume there
will never be any prefixes longer than /64, that's not optimizing for /64,
that's building a broken system. Optimizing for /64 is assuming something
like approximately 60-75% of prefixes will be /64 or shorter, maybe even
80-90% for that matter, but the latter is probably a little over optimized
in my opinion.

To one extent that's already covered in BCP198/RFC7608, this draft is more
about the IID length, but they are really just opposite sides of the same
coin.

Thanks.
-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================