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:54 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEF21F0D2F; Thu, 6 Jun 2013 18:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.741
X-Spam-Level:
X-Spam-Status: No, score=-106.741 tagged_above=-999 required=5 tests=[AWL=-0.143, 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 oVgvBWRamFFY; Thu, 6 Jun 2013 18:54:42 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 39B9611E80A3; Thu, 6 Jun 2013 18:54:34 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUbE9WTc85TpSQgmbYJJI6Df288QEBIr1@postini.com; Thu, 06 Jun 2013 18:54:34 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 BF7761B80A0; Thu, 6 Jun 2013 18:54:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 B511919005D; Thu, 6 Jun 2013 18:54:33 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 6 Jun 2013 18:54:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXm45WoMnwVBJ2U2+cujDGH1pcpkgllOAgAAGw4CAAIlogIAAHNkAgAA7XoCAANwAAIAAGRcAgACZEACAAFFqgIAAA0MAgAAlngCAAERTAIAAmIuAgAAWAQCAALv5gIAAMI2AgACc9YCAACD6gIAAH1gAgACZeoCAAAjegIAAwruAgAAV84CAAAZKgIAAAigAgAC9mQCAAIcfgIAAe8GAgABs5wCAAAM+AIAABHyA
Date: Fri, 07 Jun 2013 01:54:33 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751C86DF@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>
In-Reply-To: <CAKD1Yr0Y2_-k0sj=RsSicubJT6dUq7FJDvBoCv5h_DUTjY9ZOw@mail.gmail.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_8D23D4052ABE7A4490E77B1A012B6307751C86DFmbx01winnominum_"
MIME-Version: 1.0
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>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 01:54:49 -0000

On Jun 6, 2013, at 9:38 PM, Lorenzo Colitti <lorenzo@google.com<mailto:lorenzo@google.com>> wrote:
What about the APNIC policy I cited a few emails ago? You have not explained why you think it supports your point of view that using semantic bits does not make it harder for ISPs to assign /48s to users.

The policy says that if you want to assign something bigger than a /48 to an end site, you have to explain why it's necessary.   If you get more bits but don't assign them to the end site, that doesn't relate to the text you cited.   If you get enough bits to assign a /48 to the end site, and assign special meaning to some of those bits, that's not covered by the text.   The text simply doesn't speak to this issue.   I do not get the impression from reading the text that semantic bits are not allowed, or that an ISP's desire to use semantic bits will not be accommodated.   Apparently you do, but I don't see it in there anywhere.

Which goes back to the point I am apparently failing badly at getting across: we aren't talking about a core issue here.   If semantic prefixes are a bad idea, they are a bad idea because of some reason other than bits.

This is a really frustrating conversation.   I don't claim to know whether semantic prefix bits are a good idea or a bad idea.   I really don't know.   I haven't heard a single convincing argument for or against them yet, because we keep beating this dead horse that there aren't enough bits, despite the fact that there obviously are.