IETF Logo Mail Archive

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

Nick Hilliard <nick@inex.ie> Thu, 21 February 2013 17:33 UTC

Return-Path: <nick@inex.ie>
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 8122A21F8EE8 for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2013 09:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 wxGDwPIe9CwU for <v6ops@ietfa.amsl.com>; Thu, 21 Feb 2013 09:33:16 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id B269921F8EC3 for <v6ops@ietf.org>; Thu, 21 Feb 2013 09:33:15 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::110]) (authenticated bits=0) by mail.netability.ie (8.14.4/8.14.5) with ESMTP id r1LHURJE053149 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 21 Feb 2013 17:30:28 GMT (envelope-from nick@inex.ie)
Message-ID: <51265A57.1000709@inex.ie>
Date: Thu, 21 Feb 2013 17:33:11 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Dino Farinacci <farinacci@gmail.com>
References: <1361465143.30805.YahooMailClassic@web2806.biz.mail.ne1.yahoo.com> <51265282.1040405@inex.ie> <37A0B1BC-ECD5-49A6-AE8D-5FC8F609E864@gmail.com>
In-Reply-To: <37A0B1BC-ECD5-49A6-AE8D-5FC8F609E864@gmail.com>
X-Enigmail-Version: 1.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
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 17:33:16 -0000

On 21/02/2013 17:08, Dino Farinacci wrote:
> It is a real user/customer requirement. IETF should not tell users how
> to assign their addresses. Just allow part of the address space
> available so they can do what they want.

if the car makers want a new VIN bin, then they can have it.  The only
requirement for creating a new bin is a common agreement between them that
their chosen range of integers or symbols means something to them.  Whether
or not this range is a subset of an ietf-assigned ipv6 subnet is completely
irrelevant.

>From the IETF's point of view, if the car makers come to them and ask them
for a range of numbers for car VINs, my reaction would be "wut?"

Nick

v2.23.0 | Report a Bug | By Email