Re: [v6ops] Comments to draft-mlevy-v6ops-auto-v6-allocation-per-asn

Bill Jouris <bill.jouris@insidethestack.com> Thu, 21 February 2013 14:25 UTC

Return-Path: <bill.jouris@insidethestack.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 215A521F8D0D for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2013 06:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ks+yjdg-bsid for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2013 06:25:27 -0800 (PST)
Received: from nm9.access.bullet.mail.sp2.yahoo.com (nm9.access.bullet.mail.sp2.yahoo.com [98.139.44.136]) by ietfa.amsl.com (Postfix) with ESMTP id 4796F21F865D for <v6ops@ietf.org>; Thu, 21 Feb 2013 06:25:27 -0800 (PST)
Received: from [98.139.44.100] by nm9.access.bullet.mail.sp2.yahoo.com with NNFMP; 21 Feb 2013 14:25:27 -0000
Received: from [98.139.44.65] by tm5.access.bullet.mail.sp2.yahoo.com with NNFMP; 21 Feb 2013 14:25:26 -0000
Received: from [127.0.0.1] by omp1002.access.mail.sp2.yahoo.com with NNFMP; 21 Feb 2013 14:25:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 137376.66033.bm@omp1002.access.mail.sp2.yahoo.com
Received: (qmail 6241 invoked by uid 60001); 21 Feb 2013 14:25:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361456725; bh=QrA0ZLAizEacmGtJ9iPDgaaRPptoRgUBf+Co+tNDxvk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=FP+3AAMPk6aYD4oR521A+b/SfQ2lW1VReRGLCbpn7qWA86NcxAcODDGKBIyVGYH+/ihioPIiBOys/9mu0WNjtzXDWCg6VjGYPVPpC/kFpc6MjJEQB1fegEeHSBGX8qAVQzVulWhRhgxhqtATXj+z0kmYPZKuuzTlJCkih3xhtJk=
X-YMail-OSG: ZeBocYEVM1m2etOrvzc7zsg8ssSzNFv_3GcaXekxovAT979 06oaMVjK8eYxLnmgmNr.Co3ENILY1YbuVxIe3SKcSp7fut9u3uTEpK4kwAyE GscbBI5Rxq6sn1IjoRnnVZOMCpcoTEcDr5a_Y.mvuXZrOC4VLYi_WkFDz.8t uKAv35RJLraETlXF2nILw.psk.a1aUXminELArgyAFabDSpzxWWQpVSBofx8 t4ttgQxCz75b.9BUHn4LjdKxAh4ZXRtI1DC.LUM_Ha3N0UILNfu2vyx6kweS IukO6xDbwkTqWrTg9PNpbAGdDzL07AZM8Rb7JvAXGXVY_Y8AWf2u6CfamKQP UKWcowXKraB_Binia.4iHA5D6zli26APOYHhECBYpbzQy3qxqWw09KFBUSSL g9xinmokEmZMiS5Seyvh75lXj0ACJi0WRFtbSChbB1MWPSFNNSkVWWJWcw_S qE0ZsIEigu4Jbptr7KQsSG9V0fJaGxdh5kHuxABM.h45BqIK01cZtzB.L1wI xttG1t6q0peNTVcGVmbOz_22GdoGzX3HR3N4qMGhGshIBnHE4DyjZpOKeIa1 W8.ALEs4dGZLNLnQIvsj1G_9utf4FSLM-
Received: from [50.148.178.232] by web2803.biz.mail.ne1.yahoo.com via HTTP; Thu, 21 Feb 2013 06:25:24 PST
X-Rocket-MIMEInfo: 001.001, VGhhdCBiZWluZyB0aGUgY2FzZSwgd291bGRuJ3Qgd2UgYmUgc3RlcHBpbmcgYXdheSBmcm9tIHRoZSB3aG9sZSBpZGVhIG9mIGhhdmluZyBJUHY2IGFkZHJlc3NlcyByZWxhdGVkIHRvIFZJTiBudW1iZXJzP8KgIExlYXZlIGl0IHRvIHRoZSBhdXRvIGluZHVzdHJ5IHRvIGZpZ3VyZSBvdXQgaG93IHRoZXkgd2FudCB0byBkZWFsIHdpdGggdGhlIHN1YmplY3Q_DQoNCg0KQmlsbCBKb3VyaXMNCkluc2lkZSBQcm9kdWN0cywgSW5jLg0Kd3d3Lmluc2lkZXRoZXN0YWNrLmNvbQ0KODMxLTY1OS04MzYwDQo5MjUtODUBMAEBAQE-
X-Mailer: YahooMailClassic/15.1.2 YahooMailWebService/0.8.134.513
Message-ID: <1361456724.31374.YahooMailClassic@web2803.biz.mail.ne1.yahoo.com>
Date: Thu, 21 Feb 2013 06:25:24 -0800
From: Bill Jouris <bill.jouris@insidethestack.com>
To: v6ops@ietf.org, joel jaeggli <joelja@bogus.com>
In-Reply-To: <5125CB24.1090104@bogus.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1551098171-868201502-1361456724=:31374"
Subject: Re: [v6ops] Comments to draft-mlevy-v6ops-auto-v6-allocation-per-asn
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: Thu, 21 Feb 2013 14:25:28 -0000

That being the case, wouldn't we be stepping away from the whole idea of having IPv6 addresses related to VIN numbers?  Leave it to the auto industry to figure out how they want to deal with the subject?


Bill Jouris
Inside Products, Inc.
www.insidethestack.com
831-659-8360
925-855-9512 (direct)


--- On Wed, 2/20/13, joel jaeggli <joelja@bogus.com> wrote:

From: joel jaeggli <joelja@bogus.com>
Subject: Re: [v6ops] Comments to draft-mlevy-v6ops-auto-v6-allocation-per-asn
To: "Bill Jouris" <bill.jouris@insidethestack.com>, v6ops@ietf.org
Date: Wednesday, February 20, 2013, 11:22 PM

On 2/20/13 2:20 PM, Bill Jouris wrote:
> Owen,
> 
> So what you seem to be saying is: If manufacturers want to use a specific part of their company allocation of addresses to give addresses to the cars that they make based on VIN numbers, that is up to them.  But IETF should not mandate allocating part of the overall spectrum of addresses to them.
> 
The assignment of global unicast v6 addresses to Registries, LIRs, service providers and direct assignments is done elsewhere.

We have examples of aircraft and other large structures such as airports/tunnels and buildings receiving prefixes from their manufacturers which had originally been obtained from RIRs.
> If so, perhaps we should at least suggest to the SAE (Society of Automotive Engineers), which makes standards for that industry, that they look at whether it makes sense for all of the companies to take a uniform approach to how they do that.
> 
> Bill Jouris
> Inside Products, Inc.
> www.insidethestack.com
> 831-659-8360
> 925-855-9512 (direct)
> 
> 
>     > On Feb 19, 2013, at 5:09 PM, Owen DeLong <owen@delong.com
>     </mc/compose?to=owen@delong.com>> wrote:
> 
> 
>     I do not support allocating globally unique prefixes for things
>     that are not networks.
> 
>     Perhaps that will better explain my position.
> 
>     I think that overloading the IPv6 prefix space with semantics for
>     arbitrary collections of things is a really bad idea that has
>     tremendous potential to consume vast amounts of addresses while
>     yielding no network benefit in return.
> 
>     Will it exhaust the IPv6 space immediately, probably not. Could we
>     easily exhaust the ASN space if we start promoting the idea of
>     claiming ASNs to support this? Yeah, we could probably burn 4
>     billion ASNs that way without too much trouble.
> 
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops