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

[Stephen Kent <[e-mail]>]

Randy,


> really do appreciate review.
you're welcome.
> 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 review docs in MS Word, because it makes it easy for me to correct typos
and to precisely identify where comments apply. Because you reject Word
docs, the best accommodation I can offer, given my unwillingness to
adopt a different review mechanism, is to generate a PDF of the Word doc.
I have no trouble copying and pasting text from a PDF, so I don't understand
your comment about the difficulty of copy/paste. I do admit that responding,
inline, to comments inn the PDF format is not easy. It would work fine if
you accepted the Word doc, but ...
>> - 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 :)
yes, 8 years ago I said that I (the royal I?) could do this. Time passed
and I advised you a couple of years ago that it was not going to happen.
I relayed this news based on advice from Matt Lepinski, who is much
more knowledgeable on these crypto protocols than I. His conclusion was
that the papers published on this sort of mechanism did not yet yield
mature, practical, implementable protocols.
>> - 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 TAO I-D describes the differences in constraints imposed on the
transfer process based on live vs. unused space. Unused is much, much easier
and seems to be the most common type of space transferred across RIR 
boundaries.
Thus it seems worth considering the distinction in a discussion of the 
problem.

Steve