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

Ted Lemon <Ted.Lemon@nominum.com> Fri, 07 June 2013 01:27 UTC

Return-Path: <Ted.Lemon@nominum.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 4FB9F11E80A2; Thu, 6 Jun 2013 18:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.765
X-Spam-Level:
X-Spam-Status: No, score=-106.765 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 GrIP2A4h6UbB; Thu, 6 Jun 2013 18:26:56 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7025F21F8994; Thu, 6 Jun 2013 18:26:56 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUbE23/E5Q3H1b8s6B7TI2zkMM6wuD5vu@postini.com; Thu, 06 Jun 2013 18:26:56 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D828C1B81FA; Thu, 6 Jun 2013 18:26:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CF05419005D; Thu, 6 Jun 2013 18:26:54 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 6 Jun 2013 18:26:54 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXm45WoMnwVBJ2U2+cujDGH1pcpkgllOAgAAGw4CAAIlogIAAHNkAgAA7XoCAANwAAIAAGRcAgACZEACAAFFqgIAAA0MAgAAlngCAAERTAIAAmIuAgAAWAQCAALv5gIAAMI2AgACc9YCAACD6gIAAH1gAgACZeoCAAAjegIAAwruAgAAV84CAAAZKgIAAAigAgAC9mQCAAIcfgIAAe8GAgABs5wA=
Date: Fri, 07 Jun 2013 01:26:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751C850C@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>
In-Reply-To: <9B71CE05-E12D-4FE9-8222-6FBFD7938F0C@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751C850Cmbx01winnominum_"
MIME-Version: 1.0
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "<draft-jiang-v6ops-semantic-prefix@tools.ietf.org>" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>, Lorenzo Colitti <lorenzo@google.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: Fri, 07 Jun 2013 01:27:03 -0000

On Jun 6, 2013, at 2:57 PM, Owen DeLong <owen@delong.com<mailto:owen@delong.com>> wrote:
If you claim you gave a customer a /48 and the customer reports that they are not allowed to exercise control over the use of that /48, then, you have not, in fact, delegated authority over that /48 as you have claimed to ARIN and that is, in fact, resource fraud in violation of ARIN policy. I'm not sure why you think this is an absurd claim.

Because you haven't cited a policy that substantiates it, despite claiming to have written the policy that would say this.

There are enough bits to do it in your first allocation. Whether you will be able to get a subsequent allocation when you run out without achieving sufficiently efficient utilization later due to the inefficiencies imposed by this particular style of use is the open question. Other than you, most posters seem to recognize that this is, in fact, a likely drawback.

Yes, we're aware that it's a drawback.   Consumption of address space is a drawback of using a 64-bit host identifier, too.   But it's not a strong argument against doing it.   You seem to feel _really_ strongly about this; is it really the case that your only objection is that you think it's not possible for an ISP to get enough bits to do it?