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

Randy Bush <randy@psg.com> Tue, 07 July 2015 00:27 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 818A91A700D for <sidr@ietfa.amsl.com>; Mon, 6 Jul 2015 17:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.034
X-Spam-Level: *
X-Spam-Status: No, score=1.034 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FRT_COCK=1.544, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 Spn-DjDB4yhI for <sidr@ietfa.amsl.com>; Mon, 6 Jul 2015 17:27:57 -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 AAC121A6EF1 for <sidr@ietf.org>; Mon, 6 Jul 2015 17:27:57 -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 1ZCGjq-0007VS-Ud; Tue, 07 Jul 2015 00:27:55 +0000
Date: Tue, 07 Jul 2015 09:27:52 +0900
Message-ID: <m2vbdw24mv.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Kent <kent@bbn.com>
In-Reply-To: <559A8B31.50408@bbn.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>
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="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/8tIaSgVoS9FtkFD1LuP7yn9c-Pw>
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, 07 Jul 2015 00:27:58 -0000

really do appreciate review.

do not appreciate pdfs of word docs; makes copy paste and commenting
back a major pain.  though i have come to suspect that is one of your
goals.  so i will not comment on your comments in that pdf, though i
adopted/adapted the majority, with which i agreed.  

> - I don't consider myself to be on the hook for a "torn Euro" protocol

back in 2007, you really did say you would do it.  but this year it the
kook kids would use a blockchain contract; that'll be a fun section to
write :)

> - I think the doc should distinguish between transfers of "live"
>   address space vs. transfers of space that is not currently in
>   use. The former are more complex tan the latter and thus merit a
>   different discussion

operationally, you do not have a solid proof of [dis-]use.  and i do not
see how they should be treated differently.  prudence says do it as if it
is live.

> - the text does not yet adequately describe the steps that need to
>   take place when the Buyer or Seller are not directly under a Swing
>   Point.

sent text

> - the TAO doc described a procedure for resource transfer that
>   avoids the concern you cited in Section 5.

good.  when we get to that doc, we can then deal

i did not finish until after the dreadline.  so all will be revealed in
two weeks.  for a small fee, early peeks might be available.

randy