IETF Logo Mail Archive

Re: [Sidrops] ASPA verification algorithm error

Lukas Tribus <lukas@ltri.eu> Thu, 11 February 2021 21:21 UTC

Return-Path: <lukas@ltri.eu>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D343A003D for <sidrops@ietfa.amsl.com>; Thu, 11 Feb 2021 13:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ltri.eu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQiunTzUHRSJ for <sidrops@ietfa.amsl.com>; Thu, 11 Feb 2021 13:20:59 -0800 (PST)
Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [IPv6:2001:67c:2050::465:102]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0A6A3A003F for <sidrops@ietf.org>; Thu, 11 Feb 2021 13:20:58 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [80.241.60.241]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4Dc8gW0yq7zQlWZ for <sidrops@ietf.org>; Thu, 11 Feb 2021 22:20:55 +0100 (CET)
X-Virus-Scanned: amavisd-new at heinlein-support.de
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ltri.eu; s=MBO0001; t=1613078453; 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: in-reply-to:in-reply-to:references:references; bh=k+wyFCQj8+un3E6rqil7lXy5SSIPdLK7JUaZXhuBj+4=; b=WuR8ZmV/qKBXEgiHAM8g90SI3/r7o2WROflQBkRg4sEdzTAprFvS7WZP2qZN9a8LDEMp/A blARxBchcmsEOfqzAa7LLjxUBfJz6Wpm0PHT7jOqiQ9FU0uDj78ORoCqO+jYcvzbLMA4gi 44BCt1M44dug3I0WgM+nuhrf/loqIpIlpTZsOmdPmFEcpWEMJg4t80pWshMQilcIgtVgJS Gsw4YMekIsonM0qEnOUUWyMejjljIYYrRYf8WmYMN1FnMNx8nnkybWNMsSibXNeOVXRUMX NvCwsPV6EDryLGDzc6m5aAjipp1pC68+ZZW0hWquwD4v72p2rXHoTp+Flss8Pg==
Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter03.heinlein-hosting.de (spamfilter03.heinlein-hosting.de [80.241.56.117]) (amavisd-new, port 10030) with ESMTP id hnUxSWWrgNuz for <sidrops@ietf.org>; Thu, 11 Feb 2021 22:20:52 +0100 (CET)
Received: by mail-il1-f181.google.com with SMTP id z18so6400908ile.9 for <sidrops@ietf.org>; Thu, 11 Feb 2021 13:20:51 -0800 (PST)
X-Gm-Message-State: AOAM532HKKbO9i6Bytbd0WkJobwCtKDcb95RfUWiQqlq+fyCBgySa85E il2r/Y81ID7qtcErN/cc0hqgOzV3iudJNh8Sb1A=
X-Google-Smtp-Source: ABdhPJwfss1lfczo4OwcC6wEQDtk8Qcm4yMJiZOGPDHbSCSAWEifWB6d8Ya2uMdy8VVxATCmB8fk5+D7Z25kfeyZo7g=
X-Received: by 2002:a92:da8a:: with SMTP id u10mr66357iln.238.1613078450505; Thu, 11 Feb 2021 13:20:50 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR11MB320714401DE9AFBF5D24C832C0A09@BYAPR11MB3207.namprd11.prod.outlook.com> <CACC_My906OxmEphW=DOrGhwSagZKf--hd5oLR9uF=24kuA24ag@mail.gmail.com> <BYAPR11MB3207BD021F246199C7E4CCD6C08C9@BYAPR11MB3207.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB3207BD021F246199C7E4CCD6C08C9@BYAPR11MB3207.namprd11.prod.outlook.com>
From: Lukas Tribus <lukas@ltri.eu>
Date: Thu, 11 Feb 2021 22:20:38 +0100
X-Gmail-Original-Message-ID: <CACC_My8Kg33v=2kXgDZb+11QHSPwJtiFSmuXm_w=LuoEP2crBA@mail.gmail.com>
Message-ID: <CACC_My8Kg33v=2kXgDZb+11QHSPwJtiFSmuXm_w=LuoEP2crBA@mail.gmail.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
Cc: "Jakob Heitz (jheitz)" <jheitz=40cisco.com@dmarc.ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-MBO-SPAM-Probability: *
X-Rspamd-Score: 0.93 / 15.00 / 15.00
X-Rspamd-Queue-Id: 2ECCD17C9
X-Rspamd-UID: 3f6809
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/0CB6mhFRMIg2EbBCpGVb8j0L3xI>
Subject: Re: [Sidrops] ASPA verification algorithm error
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2021 21:21:01 -0000

On Thu, 11 Feb 2021 at 03:27, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
>
> All we have is the attestations.
> We don't know the actual relationships.
> Thus we need to try all possible relationships given the available attestations.
> Using the notation where the arrow points to the provider:
> A -> B means B is provider for A
> A <- B means A is provider for B
> A -- B means A and B are bilateral peers
> A <> B means A and B are complex or siblings.
> then the possible relationships are:
> 1 -> 2 -- 3 <- 4
> 1 -> 2 -- 3 <> 4
> 1 -> 2 -> 3 <- 4
> 1 -> 2 -> 3 <> 4
> 1 -> 2 <- 3 <- 4
> 1 -> 2 <- 3 <> 4
> 1 -> 2 <> 3 <- 4
> 1 -> 2 <> 3 <> 4
> 1 <> 2 -- 3 <- 4
> 1 <> 2 -- 3 <> 4
> 1 <> 2 -> 3 <- 4
> 1 <> 2 -> 3 <> 4
> 1 <> 2 <- 3 <- 4
> 1 <> 2 <- 3 <> 4
> 1 <> 2 <> 3 <- 4
> 1 <> 2 <> 3 <> 4
> All of these possible relationships represent a valid AS_PATH.

How does 5.2. "Downstream Paths" not address this?


Lukas

v2.23.0 | Report a Bug | By Email