> ________________________________________
> From: Sandra Murphy [[email protected]]
> Sent: Tuesday, April 06, 2010 3:34 PM
> .... snip ....
> As I understand proxy aggregation, an ISP receives updates from two peers
> and discovers that the NLRI in the two updates coincidentally aggregate
> and the ISP wants to announce the aggregate. (If I'm wrong, I should be
> corrected - I'm thinking of description in rfc2519 and Geoff's example
> in http://www.potaroo.net/ispcol/2006-05/bgp.html.)
>
> So neither origin AS has authority over the aggregate prefix. So neither
> origin AS would be able to issue a ROA for the proxy aggregated prefix.
> --Sandy
You are right. What you describe may indeed be more often the case with proxy
aggregation.
I was considering the other (may be less common) case when the deaggregate
blocks are all owned
by one common entity, and originated by different ASs which are also owned by
that entity.
In the case which you described (possibly the more common case), I agree it is
not possible
to have multiple ROAs for the aggregate.
I would lean towards having such proxy aggregated updates receive a "Not known"
validation assertion during partial deployment period (if no conflicting ROA is
found),
and disallow them (i.e., Invalid) when deployment is considered to be complete.
Sriram
>
> P.S. I found the long ago discussion on the pre-wg sidr list starting with:
> http://www.ietf.org/mail-archive/web/sidr/current/msg00025.html
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr