[Sidrops] Re: ASPA validation of paths received from customers and providers

Maria Matejka <maria.matejka@nic.cz> Mon, 02 June 2025 20:06 UTC

Return-Path: <maria.matejka@nic.cz>
X-Original-To: sidrops@mail2.ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 121752FE5ECF for <sidrops@mail2.ietf.org>; Mon, 2 Jun 2025 13:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEP4UtVf6U-t for <sidrops@mail2.ietf.org>; Mon, 2 Jun 2025 13:06:24 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 31E782FE5EC8 for <sidrops@ietf.org>; Mon, 2 Jun 2025 13:06:23 -0700 (PDT)
Received: from struhadlo.private.jmq.cz (unknown [IPv6:2001:1488:fffe:6:b094:83ff:fecd:1f52]) by mail.nic.cz (Postfix) with ESMTPSA id BDA421C0638; Mon, 2 Jun 2025 22:06:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1748894782; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=f8WtCszCokIRyuk2leRjvhCgyJpaZyf2g4BCaqo9Q1E=; b=o1CnbtA2SqSxwq2gQM2Ii7ZzJhNxeTVUqc7gEaMYJv4e1HeVnsCziB+VfNw3enfZuiorUI 6Wod3d3eNHvcYQcM49C2QBfC7Umw7Aa2LfVJQ8r7p/zmyBYS8kCjmu5Ljzx2EyxSaoSovh CCG6X38/+FegZpfEVtX2siKBAu+EpuM=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=maria.matejka@nic.cz smtp.mailfrom=maria.matejka@nic.cz
Date: Mon, 02 Jun 2025 22:06:16 +0200
From: Maria Matejka <maria.matejka@nic.cz>
To: Randy Bush <randy@psg.com>
Message-ID: <aD4EOMKW3KJYQ9RO@struhadlo.private.jmq.cz>
References: <aDhFek0kKlCyj8pq@struhadlo.private.jmq.cz> <DS0PR09MB105981A10DCA72C22221C82418466A@DS0PR09MB10598.namprd09.prod.outlook.com> <aDlVmigl8R_34g1w@anton.sobornost.net> <aDmMC4CQmXi6Rs1p@struhadlo.private.jmq.cz> <m2y0uecbqp.wl-randy@psg.com> <aD2bc3zFdyM-vgIW@struhadlo.private.jmq.cz> <m2ecw2c5kd.wl-randy@psg.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nQGEfEU6u+hksHvT"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <m2ecw2c5kd.wl-randy@psg.com>
X-Rspamd-Action: no action
X-Rspamd-Server: mail
X-Spamd-Bar: /
X-Rspamd-Queue-Id: BDA421C0638
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP
X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]; WHITELISTED_IP(0.00)[2001:1488:fffe:6:b094:83ff:fecd:1f52]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; MIME_TRACE(0.00)[0:+,1:+,2:~]
Message-ID-Hash: B7BHF35LF2334JNTCJ5Q3B2UWHU3VTA7
X-Message-ID-Hash: B7BHF35LF2334JNTCJ5Q3B2UWHU3VTA7
X-MailFrom: maria.matejka@nic.cz
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: SIDR Operations WG <sidrops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: ASPA validation of paths received from customers and providers
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/hp1HDWIg4QMeFLrRKAS0sGzKse8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Randy,

> >> as a node may have multiple local ASs, is what you want really test
> >> at egress?
> > 
> > Theoretically, yes.  Practically, that's relying on the neighbor to do
> > the checks properly, and that's not how BGP is designed to work, imho.
> 
> i am not sure what you're meaning here.  i assume not that i am not
> responsible to ensure that what i send is proper, and solely the
> receiver is responsible for checking it.  i don't think we have
> signaling mechanisms with granularity sufficient to the latter.  and,
> even if we did, dealing with diagnostic signal from receiver to sender
> would seem to be more complex than just being more careful with what we
> send.

The export check on my neighbor's BGP speaker shouldn't be enough for me
to not check the same on import.

> my suggestion is not to have the neighbor report my misconfiguration,
> but for me to detect it before sending to neighbor.  see e.g. RFC 8893.

I want to detect my neighbor's misconfiguration before considering their
route for best route selection (and subsequently failing to export it
further).

Maria

-- 
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.