<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 13 Feb 2021, at 16:26 EAT, Ben Maddison via RPD wrote:</p>
<blockquote style="border-left:2px solid #5855D5; color:#5855D5; margin:0 0 5px; padding-left:5px">
<p dir="auto">At time t2, the RIR re-allocates 2001:db8:foo::/48 to member Y, who also has AS65001.<br>
Member Y issues ROA:<br>
2001:db8:baa::/48 asID:65001</p>
</blockquote>
<p dir="auto">Bad things will always happen if member Y attempts to create a ROA different from what they were allocated.</p>
<p dir="auto">If I understand correctly at time t2 2001:db8:baa::/48 is still legitimately allocated to AS65000.</p>
<p dir="auto">At the time t2 when reallocating 2001:db8:f00::/48</p>
<ul>
<li>RIR should remove ROA 2001:db8:f00::/48 AS0 (since it’s no longer “unallocated”)
<ul>
<li>2001:db8:f00::/48 goes back to “unknown”</li>
</ul></li>
<li>RIR hands AS65001 a CA cert which contains 2001:db8:f00::/48.</li>
<li>Y optionally creates 2001:db8:f00::/48 AS65001 when allocation etc are done.
<ul>
<li>2001:db8:f00::/48 origin AS65001 goes to “valid”</li>
</ul></li>
</ul>
<p dir="auto">At this point the history of 2001:db8:f00::/48 being reclaimed from AS65000 rather than coming from IANA doesn’t matter unless I’m missing something.</p>
<p dir="auto">--<br>
patrick</p>
</div>
</div>
</body>
</html>