IETF Logo Mail Archive

Re: [sidr] New Version Notification for draft-ymbk-sidr-transfer-00.txt

Stephen Kent <kent@bbn.com> Tue, 14 July 2015 00:26 UTC

Return-Path: <kent@bbn.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8AB1A885D for <sidr@ietfa.amsl.com>; Mon, 13 Jul 2015 17:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRVAscd56MWv for <sidr@ietfa.amsl.com>; Mon, 13 Jul 2015 17:26:39 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 429131A8860 for <sidr@ietf.org>; Mon, 13 Jul 2015 17:26:39 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:51868 helo=COMSEC-2.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1ZEo3Q-0009wj-VA; Mon, 13 Jul 2015 20:26:37 -0400
To: Randy Bush <randy@psg.com>
References: <20150530231211.10362.50102.idtracker@ietfa.amsl.com> <m2lhg33u84.wl%randy@psg.com> <556CF530.4010408@ops-netman.net> <m27frn3qye.wl%randy@psg.com> <87F5B607-2ECC-4C54-A8D8-D8CE5F587F07@tislabs.com> <559A8B31.50408@bbn.com> <m2vbdw24mv.wl%randy@psg.com> <559BF347.60609@bbn.com> <9DFC9C7C-CBFC-427C-8589-C13457EDD091@tislabs.com> <7A433ECB-5AEE-4521-A099-1E48DDF25E2B@arin.net> <55A0312D.3050401@bbn.com> <m21tgf1zqr.wl%randy@psg.com>
From: Stephen Kent <kent@bbn.com>
Message-ID: <55A4573C.5020006@bbn.com>
Date: Mon, 13 Jul 2015 20:26:36 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <m21tgf1zqr.wl%randy@psg.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/L18sItNWNngawmU6EMPM9YQ21yM>
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] New Version Notification for draft-ymbk-sidr-transfer-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2015 00:26:40 -0000

I disagree.

In this context the entity relinquishing the address space should
know whether the space is in use or not. We ought to be able to
take advantage of this knowledge to simplify the transfer process,
when applicable.

Steve

On 7/10/15 5:14 PM, Randy Bush wrote:
> making assumptions if and how address space is or is not used is a
> recipe for mistakes and is not really useful.
>
> randy
>

v2.23.0 | Report a Bug | By Email