IETF Logo Mail Archive

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

Job Snijders <job@fastly.com> Thu, 21 July 2022 12:42 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 83989C131959 for <sidrops@ietfa.amsl.com>; Thu, 21 Jul 2022 05:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 RClcKMdDTgt3 for <sidrops@ietfa.amsl.com>; Thu, 21 Jul 2022 05:42:26 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 DEDE1C13195B for <sidrops@ietf.org>; Thu, 21 Jul 2022 05:42:26 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id d4so721287ilc.8 for <sidrops@ietf.org>; Thu, 21 Jul 2022 05:42:26 -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=jZHfAIFYekgb+c98bQwNn1+n9+KBPq9C9qJQadNSc60=; b=UAXFS6VaJIvdjyW+Llvgs0EPG3NKM2PDtQHEWYmTCZuLJEWM/j2FD2eut8j7cgXJ16 j+o3Fq+qn7Zmra3flx9rtGN7jiIBPTVL2401LIm/Xl/Sn23FFoY7WjNDg1ChZ4NvwUOE f3817myuLTxwxOUKadSXhZ6kuLZDICICXvt6c=
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=jZHfAIFYekgb+c98bQwNn1+n9+KBPq9C9qJQadNSc60=; b=a3Ql3zYjdhRldfh5TlhpRaR/mgZTyaxjdCHR+Ijs55HO2bVG4rekZ/Jy7C/ODKcTsY /w5mP7sm+94mS+sLUQmLRa5kLJK3+X+WBEcM07h6lYBboM1r3ECyJ6iDnVSsYjT3Hf+6 RZYwm1wuNsLjycS2RYdu4pvjuSn6XZpi3OMazYT4zJSpCfHyEPDC7YCyuFBteA5erXxt 89wHbeyk+NLNYVm/+1/mRmlP3JwnP2vuvspPeaJh+SEXa0Ku5BM2dSyAOAMUOMzu338H grunHpVllbxbTusF5AbFiqKmTJKfASNP8J23QFWLVEMIRrEARZw5vmshcZQWEIWFeH1P uAhw==
X-Gm-Message-State: AJIora82FRk0ucx20488XOTRsWhVzFhWxicllQALtnKg84BSbLA9lX81 BU0iRVC7iPf83/DZRVVQ3agJEh1xNCzMoQTw78FAkA==
X-Google-Smtp-Source: AGRyM1s1Up5w+r8GXi5USf9QLjBexqX+EX5av/x1kHuBY1Cu+3CL56TD3vYgOcZdqu5z9gfcL5wXvJn+Ev7ndiBk48o=
X-Received: by 2002:a05:6e02:1645:b0:2dd:15dd:97ef with SMTP id v5-20020a056e02164500b002dd15dd97efmr579837ilu.217.1658407345797; Thu, 21 Jul 2022 05:42:25 -0700 (PDT)
MIME-Version: 1.0
References: <SA1PR09MB8142D357A98BFAAF206C387C848F9@SA1PR09MB8142.namprd09.prod.outlook.com> <66814cfa-8425-8063-9193-272bc8b28291@foobar.org> <CAMFGGcDRhaLVi9ESK3+C-pB7rdts2-WTKXFhMSCjuvFFGQ=Cqw@mail.gmail.com> <SA1PR09MB8142AA6AE482BA4D80168C8B84919@SA1PR09MB8142.namprd09.prod.outlook.com>
In-Reply-To: <SA1PR09MB8142AA6AE482BA4D80168C8B84919@SA1PR09MB8142.namprd09.prod.outlook.com>
From: Job Snijders <job@fastly.com>
Date: Thu, 21 Jul 2022 14:42:15 +0200
Message-ID: <CAMFGGcC36KPJe6ap3VMG=7x38WvpWJmgxx1k-HKp36mf43-quw@mail.gmail.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
Cc: GROW WG <grow@ietf.org>, Nick Hilliard <nick@foobar.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="000000000000bd542b05e4500c22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/jJaKd4EruMfSwQ7WlwizNKA57mg>
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 12:42:30 -0000

Dear Sriram,

On Thu, 21 Jul 2022 at 14:08, Sriram, Kotikalapudi (Fed) <
kotikalapudi.sriram@nist.gov> wrote:

> Treating an UPDATE with an AS_SET as always 'Invalid' may be reasonable
> and simplifies the algorithm description except the diagnostic value of the
> 'Unverifiable' flavor is lost.


This would be my preference: marking UPDATES as “invalid” if they contain
an AS_SET anywhere in the AS_PATH.

The diagnostic value of the “Unverifiable” flavour to me seems limited, as
it introduces a potential for ambiguity and confusion.

Kind regards,

Job

v2.23.0 | Report a Bug | By Email