Dear Working Group Members, Please find below a newly submitted document: "Explicitly excluding objects from RPSL sets". The purpose of this document is to address the issue faced by many operators today; namely that AS-SETs and ROUTE-SETs contain member entries which are undesirable for one reason or another, but the set owner has no method to exclude these unwanted members from their own set because they are deep within the set hierarchy. I have spoken to several people in the community who suffer from this problem and would like something done about it. In the long term we hope to phase out IRR based filtering, but we are many years away from that, so in the mean time we’d like to improve the situation until such time. Feedback and support from the community is appreciated. https://datatracker.ietf.org/doc/draft-bensley-rpsl-exclude-members/ https://www.ietf.org/archive/id/draft-bensley-rpsl-exclude-members-00.html With kind regards, James. [CompanySignature] Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: hello@inter.link<mailto:hello@inter.link> | Web: inter.link<https://inter.link>