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

Stephen Kent <kent@bbn.com> Fri, 10 July 2015 20:55 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 5379F1B2AF8 for <sidr@ietfa.amsl.com>; Fri, 10 Jul 2015 13:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 GJ9P23b4SB5k for <sidr@ietfa.amsl.com>; Fri, 10 Jul 2015 13:55:14 -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 7101E1A010D for <sidr@ietf.org>; Fri, 10 Jul 2015 13:55:14 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:42392 helo=COMSEC-2.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1ZDfK9-0007ZK-M9; Fri, 10 Jul 2015 16:55:09 -0400
To: Andy Newton <andy@arin.net>, Sandra Murphy <sandy@tislabs.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>
From: Stephen Kent <kent@bbn.com>
Message-ID: <55A0312D.3050401@bbn.com>
Date: Fri, 10 Jul 2015 16:55:09 -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: <7A433ECB-5AEE-4521-A099-1E48DDF25E2B@arin.net>
Content-Type: multipart/alternative; boundary="------------070700090400080806050204"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/RH9WQqsPV9ruXp_RAjFfvOCfMk0>
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: Fri, 10 Jul 2015 20:55:19 -0000

Andy,

In this context "live" refers to address space in use as opposed to 
allocated
but not in use. So your reply doesn't address the question.

Steve

>
>> On Jul 8, 2015, at 1:30 PM, Sandra Murphy <sandy@tislabs.com 
>> <mailto:sandy@tislabs.com>> wrote:
>>
>> I think it would be interesting to hear from the RIR's as to whether 
>> they require resources to be unused, and for how long, before a 
>> transfer is possible.
>
> The reality is that we rarely get transfers of RPKI certified space, 
> but to answer your question: we don’t deny or delay a transfer just 
> because it is RPKI live.
>
> -andy