Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03

Lorenzo Colitti <lorenzo@google.com> Sat, 08 June 2013 02:00 UTC

Return-Path: <lorenzo@google.com>
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 D566221F9A08 for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2013 19:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.033
X-Spam-Level:
X-Spam-Status: No, score=-3.033 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OX4q1tM9T2WK for <ipv6@ietfa.amsl.com>; Fri, 7 Jun 2013 19:00:46 -0700 (PDT)
Received: from mail-qe0-f47.google.com (mail-qe0-f47.google.com [209.85.128.47]) by ietfa.amsl.com (Postfix) with ESMTP id 6719B21F9A10 for <ipv6@ietf.org>; Fri, 7 Jun 2013 19:00:46 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id 1so3182518qec.34 for <ipv6@ietf.org>; Fri, 07 Jun 2013 19:00:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Gpn8PBhsW5aA/8wTcX67U4GR87QJaNfWaXTsS5YJqTo=; b=R3GePgv7d+a/Iit33TQEz/cdHZln0Gb0hm9So/g0MAsJYHDnkNLaVfAHrwO9zDA56y NMYWFrahLkLLH86+pAbogLJ9HrRU0QQ+0YLLgXXZLI/w7NROmO1gE52gnndy5YwbFGR0 tmo0wzLgX620iw5anch49ipi6f6ZJhhxH2Mfo91bxjV+dQQrtkj7t5mNeIS8/RlZm3xo CY42cDNeL7yLNttIfMF37hLerfPlkSUHM4pv7ZhQZpyho/oDMGUnRvyYq83jG2aFR9aN 4JkRUbgLq5t/s7ridbkZ31eTnUZZWvGMu/v3ZCZesOxAB5vtu3EiOSpFa1QyY2gRQlxa 22tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=Gpn8PBhsW5aA/8wTcX67U4GR87QJaNfWaXTsS5YJqTo=; b=KiT6nc4OXPNM66AlO7bWYAL/kN77VR37nBQNuRE40c1yxXvpZ1RwWe09/Vj4PSkrX3 sblq8YfA6EBCie/pT3z/NiGjkTj5CxtNHH74HMkFQWUFWY5b6tVUXroIGfNYPfiMLpZj vNTDh0CChL7BrkIdEwvqN0WZBI8FOuDYCvl0g3JxTKqIfjBYb0A/Bt8lr7G1uz6nAUhs laJ6JkRlaKntfrlQDRn991B+vBFBHHKm4B/ITU3bafYMqs/+yh0VFHFyuzOAOJtY23bK 94hR2rpkjTMwEDF8rTMiEcjAXH6G+KE48WpDh0g5Eae2SCszziXCjPu5XBWL87H3bnu4 3yxA==
X-Received: by 10.229.119.72 with SMTP id y8mr514006qcq.39.1370656845782; Fri, 07 Jun 2013 19:00:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.158.8 with HTTP; Fri, 7 Jun 2013 19:00:24 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751C90F7@mbx-01.win.nominum.com>
References: <05DB0BDC-9B6D-4852-B878-5320ABC14D67@steffann.nl> <8D23D4052ABE7A4490E77B1A012B6307751C5A63@mbx-01.win.nominum.com> <CAKD1Yr1tSy9XZ5A8Zc-doBTfWiPX1TkqGuJeqty9=mhwwHPRKA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C6F61@mbx-01.win.nominum.com> <9B71CE05-E12D-4FE9-8222-6FBFD7938F0C@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751C850C@mbx-01.win.nominum.com> <CAKD1Yr0Y2_-k0sj=RsSicubJT6dUq7FJDvBoCv5h_DUTjY9ZOw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C86DF@mbx-01.win.nominum.com> <CAKD1Yr0EQwqEzPe_FK+XnN+mOGaVU2NWW2Sr5toGZhKiMwkW2A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751C90F7@mbx-01.win.nominum.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 08 Jun 2013 11:00:24 +0900
Message-ID: <CAKD1Yr3frpGOYDoDBfvZR+XocgQZzYeK-_G=3sbtASb3ZfuRSQ@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary="001a1133327067026004de9aea2f"
X-Gm-Message-State: ALoCoQkKZ1VdmZsrrUFloAD1MMCp6kWjgHk9to6jfDfw7A4sepKdwS2XwPcuKC7PQCMhmVFZ6h8NqFt33f+CTwv9mBNdLhPqTBVY9sAW/k8+JK/1f5S4aT6oMXKRHRx469UEaHCz0H52u8IN3I3tn4jdOnAMAtnCFDMggou6M2EPAsRKm/9ZaxxsNbJ6OxI+mCcLx/pWRMp2
Cc: "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>, "<draft-jiang-v6ops-semantic-prefix@tools.ietf.org>" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 08 Jun 2013 02:00:59 -0000

On Fri, Jun 7, 2013 at 10:23 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  Argh.   I don't think anybody ever said that there was no cost to these
> bits, and I agree that the cost should be discussed.   So I guess we've
> been arguing over a nonexistent disagreement!   :|
>

Yes, that happens. :-(

One thing to bear in mind is that it depends a lot on how much space you
already have. Examples:

1. Deutsche Telekom has a /19. That's over 500M /48s, and if they use it
only in Germany, that's 5 for every person in the country, with a fair bit
left over. So they can afford to use 2 bits for semantic prefixes.

2. Comcast only appears to have a /29 and a /28 (2001:558::/29, 2601::/28).
That's only 1.5M /48s, and they have about 10x that many customers. They
likely can't use /48 plus semantic prefixes, because if ARIN doesn't accept
"semantic prefixes" as using space efficiently (and word from ARIN on this
thread seems, well, negative on the matter), then they won't be able to get
more space from ARIN. That means that there is a fundamental tension
between using semantic prefixes and giving more address space to customers.

We need to be very careful not to create an incentive to give less address
space to customers, because IPv4 shows us very clearly how that ends up
complicating the whole network.

Cheers,
Lorenzo