For route-server clients OTC handling can be performed like for the
peer-to-peer role. This comes from the fact that the route-server itself
should tag all routes with its own AS in the OTC attribute and so if the
OTC attribute is not equal to the RS AS then the route-server did not do
its job to drop this leak.

See also draft-herdes-idr-otc-rs-verification-01
-- 
:wq Claudio

Index: rde.c
===================================================================
RCS file: /cvs/src/usr.sbin/bgpd/rde.c,v
diff -u -p -r1.713 rde.c
--- rde.c	30 Aug 2026 23:43:22 -0000	1.713
+++ rde.c	19 Oct 2026 07:13:24 -0000
@@ -2421,6 +2421,7 @@ rde_attr_parse(struct ibuf *buf, struct 
 			a->flags |= F_ATTR_OTC_LEAK;
 			break;
 		case ROLE_PEER:
+		case ROLE_RS_CLIENT:
 			ibuf_from_ibuf(&tmpbuf, &attrbuf);
 			if (ibuf_get_n32(&tmpbuf, &tmp32) == -1)
 				goto bad_len;