-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Job,
> Some years ago, as part of a tabletop exercise, I tried to imagine what > 'sets in RPKI' could look like, and from the get-go had 'exclusion' as a > feature in mind: > > > https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-asgroup-00.html > > but, working out the full complexities of inter-domain set theory > operations seemed daunting, and lacking architectural documents > detailing considerations around 'set exclusion' as a concept, me merely > specifying a binary encoding format was not the way to make progress. > > Please take this message as encouragement. I think that Gap analysis of > the RPSL (and proposed fixes) can in turn positively impact developments > in the space of (RPKI-based) signed routing intensions. > Thanks for pointing me to this. I have been this about exactly this recently. I think that today it's a missing feature in the RPKI based toolset; the only way for me to know which ASNs/Prefixes a neighbour will provide me connectivity to, is to ingest all ASPA objects and reconstruct the tree by working out who's an upstream of whom (and it's not possible right now due to lack of ASPA objects). So I see that there is feature disparity we need to make up for in the new RPKI world vs legacy IRR DB world. And also new features; I will still need to exclude stuff regardless of weather my data comes from IRR DB or RPKI. This draft you have linked is more or less what I have been thinking about, so thanks I'll give it a proper read through (just scanned it for now to get the idea). Cheers, James. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsG5BAEBCgBtBYJp4KliCRCoEx+igX+A+0UUAAAAAAAcACBzYWx0QG5vdGF0 aW9ucy5vcGVucGdwanMub3JnoaYiq2+Nq41tD/LptgAft8NPnjvcFu9dqqob 7Jl580kWIQQ+k2NZBObfK8Tl7sKoEx+igX+A+wAAV/oP/0StpNqhPZDOGp+s AZMQgY0a02Ur6+sy7bEr9PWfSOLOCEv6fPWhgN/PURECffNvi2cpLvRQrN5g f0KX+DdRYuftLaT1DX3JbD+AiRF3q1mNnyj84CrKkS2BGFMDtOg69P9kKXsc jVK3EM4yooMZQtTm40LBiMcZ9NBj6VacVAumwztO1CHS1vWiwpr8g3iCtLRy jqsahUwFl0IfCK58YSmWyJci15Hox8yFooMMYULpQ5luutiQbh5HD9u08yoV xzu9uYFcrFIwOAMpSXno5Nu9L8ptPeNJVJZvMizsPe0hKUcLTaJHERu338EI bFTEz17VxpwWAMqNJ6KNWZSGbqdiq93EaLpqaSUngfn4KQzb/2An0orEtWcM V82xqMSsBPP4EbzUhBBj21puhyRb4cu/Yyb49ys8KrvqbibRdueqM/Con0F7 LY2Z61AfghGjdiTS1DhUGVP6lFkJsLfb6OsEsUujqSuMfO0cEQMEmt/FRota qSHde5MxQUV/9Sg8LdJmwOTH70x2ORJy24t3ESRrs1FNH6MO4H7b4SLzpNbF N6gDYIOnTdaBQhQsuFia2EjwQk0Y/T47zrjNeRcmdt21his+U/7abRT8E/cU qRjrqO//6AwbQAPpWtFH9Ucyqc3QMS4HZHgkf4PszzMIN/vX3equRDHFAuLY 4H/6cnp8 =09ik -----END PGP SIGNATURE-----
publickey - [email protected] - 0x3E936359.asc
Description: application/pgp-keys
publickey - [email protected] - 0x3E936359.asc.sig
Description: PGP signature
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
