IETF Logo Mail Archive

Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 15 February 2012 01:51 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BAD921E8021 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.07
X-Spam-Level:
X-Spam-Status: No, score=-0.07 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 kAtRs9TF2z3V for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:51:07 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id BFD1521E8015 for <ietf@ietf.org>; Tue, 14 Feb 2012 17:51:06 -0800 (PST)
Received: (qmail 65601 invoked from network); 15 Feb 2012 02:06:08 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 02:06:08 -0000
Message-ID: <4F3B0F5D.7050506@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 10:50:21 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com>
In-Reply-To: <m2d39hi267.wl%randy@psg.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 01:51:08 -0000

Randy Bush wrote:

> what silliness.  it will be used as rfc 1918 space no matter what the document
> says.

The difference is on how future conflicts can be resolved.

> nine years ago i was in bologna and did a traceroute out.  i was surprised
> to find that the isp was using un-announced us military space as rfc 1918
> space internal to their network.  this turns out to be common.

What if the military space is sold to public and announced?

Who is forced to renumber and why?

						Masataka Ohta

v2.23.0 | Report a Bug | By Email