Re: [Sidrops] [GROW] Any credence to AS_SET in the *middle* between AS_SEQUENCEs?

Job Snijders <job@fastly.com> Thu, 21 July 2022 09:37 UTC

Return-Path: <jsnijders@fastly.com>
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 F11AEC14CF10 for <sidrops@ietfa.amsl.com>; Thu, 21 Jul 2022 02:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OzoX6PP4QNN for <sidrops@ietfa.amsl.com>; Thu, 21 Jul 2022 02:37:41 -0700 (PDT)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F41AC157B5A for <sidrops@ietf.org>; Thu, 21 Jul 2022 02:37:38 -0700 (PDT)
Received: by mail-il1-x133.google.com with SMTP id f1so538575ilu.3 for <sidrops@ietf.org>; Thu, 21 Jul 2022 02:37:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JrvUTY4sS43Toe4+lMnknP7GLIsr8NPinUZAggLt6Ug=; b=Nh+NB1yihvPHwFA3/ceun5ku4coHrnEkmVJgRY1nGJZW2zltHBZuoNGB14msbgsk0m Egxr/aj/P/9BP7r0LBwMJqJiwd7bh34sNylV1zTxZxEXguJ+5FcGBDTZ+f7mDRSfeu5e 5Hh5Dp2nAmaUWJ9C6Gt5eZr1xZxMzgjy16mq8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JrvUTY4sS43Toe4+lMnknP7GLIsr8NPinUZAggLt6Ug=; b=4zsoN0xArwM0sQKnJFgKCk+jYBP4pI96Y6+9J2rJxGfAAS11LVCQwocVrapgTewi1v kwdRqVm28QTVDHAgitywjvGhKhblv93q3VUxzNPme/oYChhrUnT/698MAro0MqBHKbdR JTxR+yS2riGUdYNNpS0ikTVJKWunlFmDPFO15AHoeM5iDocUewjkIzUq0eljRt+MFcql hvU39sBhaef6wm+TOLCOy0T3Rhs/S8fu7jCkQEIwv4/3/Qn5Amp8Sz6mujUpX49yadJN 3JE+Tc3qYFPgi9j6VKoX3nDcZUP4krKshZLZxmV6uxC7Q3fUazMFo4p/LvhmqCFmnU2C 8GjA==
X-Gm-Message-State: AJIora8XQV5WDYpjaWF+N9GUyrIEcsnr5CjTZxYbQV6jArWf5q9WJ2Fq lwRY48CjEYYqh3mIiSSUnaH0C+MosUOLcwo1xIZQlYPm6Y0=
X-Google-Smtp-Source: AGRyM1vpPGfM5J172P9t4WxC/iaJfYN9M2ysC6LNdtxkDXXcswCdxD42fT/4ZCsuu/U65CrZYwcOXrj7qXoMse+L8J0=
X-Received: by 2002:a05:6e02:16cc:b0:2dc:6780:3abd with SMTP id 12-20020a056e0216cc00b002dc67803abdmr19539628ilx.222.1658396256972; Thu, 21 Jul 2022 02:37:36 -0700 (PDT)
MIME-Version: 1.0
References: <SA1PR09MB8142D357A98BFAAF206C387C848F9@SA1PR09MB8142.namprd09.prod.outlook.com> <66814cfa-8425-8063-9193-272bc8b28291@foobar.org>
In-Reply-To: <66814cfa-8425-8063-9193-272bc8b28291@foobar.org>
From: Job Snijders <job@fastly.com>
Date: Thu, 21 Jul 2022 11:37:26 +0200
Message-ID: <CAMFGGcDRhaLVi9ESK3+C-pB7rdts2-WTKXFhMSCjuvFFGQ=Cqw@mail.gmail.com>
To: Nick Hilliard <nick@foobar.org>
Cc: GROW WG <grow@ietf.org>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org>, "draft-ietf-sidrops-aspa-verification@ietf.org" <draft-ietf-sidrops-aspa-verification@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb502f05e44d77ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/lxBv-4EUY_jMrHwV0zrUSytB1DM>
Subject: Re: [Sidrops] [GROW] Any credence to AS_SET in the *middle* between AS_SEQUENCEs?
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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, 21 Jul 2022 09:37:45 -0000

On Thu, 21 Jul 2022 at 10:37, Nick Hilliard <nick@foobar.org> wrote:

> Sriram, Kotikalapudi (Fed) wrote on 19/07/2022 22:24:
> > Question: Operationally, is an AS_SET ever used in the*middle*
> > between AS_SEQUENCEs? Or, should one simply give zero credence to
> > it?


>
> tl;dr: epsilon levels of credence.


My take on this:

In the spirit of RFC6472, any route with an AS_SET in it should not be
considered valid (by ASPA-based validation).

If the route contains an AS_SET and a covering ASPA object exists for the
origin ASN of the route, then the route must be marked with an Invalid
status.

Kind regards,

Job

>