Hi Sriram,
Functionally, your solution does detect the route leak.
But the actual operation may be difficult, how to encourage so many RS Clients
to claim their ASPAs?
Or do we need to create an ASPA database with such ASPAs locally by collecting
and analyzing Internet routing and data?
In a project I've been through, we did do something similar. We mine those RS
Clients that are interconnected by IXP RS, and then create a P2P relational
database for them.
Take the following topology as an example:
AS1 (RS Client) -----> AS2 (RS) -----> AS3 (RS Client) ---p2p (lateral peer)
---> AS4 (validating AS)
\
\
AS5(RS Client)
By some probing we can find AS1/AS3/AS5 are AS2 (RS)'s clients, so we can add
AS-Pairs: {AS1 AS3}, {AS1 AS5}, {AS3 AS5} into the local P2P AS-Relationships
database.
By the similar method, we can also create a local RS-Client to RS ASPA
database.
Kind Regards,
Shunwan
> -----Original Message-----
> From: Sriram, Kotikalapudi (Fed) [mailto:[email protected]]
> Sent: Thursday, March 24, 2022 3:01 AM
> To: Zhuangshunwan <[email protected]>; Jakob Heitz (jheitz)
> <[email protected]>; Jeffrey Haas <[email protected]>
> Cc: [email protected]; [email protected]; Nick Hilliard <[email protected]>
> Subject: RE: [GROW] [Sidrops] ASPA and Route Server (was RE: IXP Route
> Server question)
>
> Hi Shunwan,
>
> >> AS1 (RS Client) -----> AS2 (RS) -----> AS3 (RS Client) ---p2p (lateral
> >> peer) --->
> AS4 (validating AS)
>
> >2. AS3 is not included in the set of C2P AS numbers set registered by AS1;
>
> #2 (above) from your list is what we have focused on as a solution. Please
> see my previous post responding to Jakob where the set of ASPAs is
> enumerated.
>
> Sriram
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
