Chris,
Yes, the example you provided matches what I had in mind.
Steve
-
On Tue, Apr 2, 2013 at 1:59 PM, Stephen Kent <k...@bbn.com
<mailto:k...@bbn.com>> wrote:
Danny,
The architecture permits overlapping allocations to accommodate
transfers that involve address space that
is in use. I've been told by several operators that, for this sort
of transfer, such overlap
is required.
overlap with respect to:
ADDRESSBLOCK + ASN
right? so initially:
128.2.35.0/24 <http://128.2.35.0/24> + AS28
In the near-future as 128.2.35.0/24 <http://128.2.35.0/24> moves from
AS28 -> AS22224:
128.2.35.0/24 <http://128.2.35.0/24> + AS28
128.2.35.0/24 <http://128.2.35.0/24> + AS22224
and at some point in the further future:
128.2.35.0/24 <http://128.2.35.0/24> + AS22224
(and ideally the initial ROA ends up on a CRL...)
right? Enable /make before break/ for customers moving from attachment
point to attachment point.
-chris
Steve
On 4/2/13 12:02 PM, Danny McPherson wrote:
...
As for today, the architecture permits such collisions, which
I think is the issue most agree is, err.. suboptimal.
-danny
_______________________________________________
sidr mailing list
sidr@ietf.org <mailto:sidr@ietf.org>
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
sidr@ietf.org <mailto:sidr@ietf.org>
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
