IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Fri, 17 July 2015 04:25 UTC

Return-Path: <randy@psg.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 205261ACD6E for <sidr@ietfa.amsl.com>; Thu, 16 Jul 2015 21:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 CC0wpz35BRnb for <sidr@ietfa.amsl.com>; Thu, 16 Jul 2015 21:25:00 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EFD81B2AD5 for <sidr@ietf.org>; Thu, 16 Jul 2015 21:24:37 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1ZFxCL-0002LU-TE; Fri, 17 Jul 2015 04:24:34 +0000
Date: Fri, 17 Jul 2015 06:24:32 +0200
Message-ID: <m2a8uvfm2n.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andy Newton <andy@arin.net>
In-Reply-To: <8BE719A0-0EC1-4E35-8BAD-A64E06D0979C@arin.net>
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> <55A6C585.6060602@bbn.com> <8BE719A0-0EC1-4E35-8BAD-A64E06D0979C@arin.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/GSTcJCdyjfs6GvifVz3xPExRRtk>
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, 17 Jul 2015 04:25:01 -0000

> Randy's view is that it is preferable to engineer a single solution
> that is agnostic about whether the address space is in use or not,
> even if that is a more complex solution. His rationale seems to be
> that its safer to treat all space as in use, so as to avoid the damage
> to users that arises if the entity transferring the space can't
> properly classify it properly.

thank you for putting words in my mouth, especially as they are the
correct words :)

> Isn’t the “unused” scenario what we have today? Why do we need a
> solution for something that is already being accomplished?

in steve's model, one has to implement both.  job security for engineers
:)

randy

v2.23.0 | Report a Bug | By Email