[Sidrops] ASPA duplicates

Jay Borkenhagen <jayb@braeburn.org> Tue, 28 April 2020 16:53 UTC

Return-Path: <jayb@oz.mt.att.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 498973A0878 for <sidrops@ietfa.amsl.com>; Tue, 28 Apr 2020 09:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ygxOBqma-XFT for <sidrops@ietfa.amsl.com>; Tue, 28 Apr 2020 09:53:13 -0700 (PDT)
Received: from hrabosky.cbbtier3.att.net (braeburn.org []) by ietfa.amsl.com (Postfix) with ESMTP id CA97D3A0829 for <sidrops@ietf.org>; Tue, 28 Apr 2020 09:53:08 -0700 (PDT)
Received: from oz.mt.att.com (zoe.cbbtier3.att.net []) by hrabosky.cbbtier3.att.net (Postfix) with ESMTP id 6016135EBD for <sidrops@ietf.org>; Tue, 28 Apr 2020 16:53:08 +0000 (UTC)
Received: by oz.mt.att.com (Postfix, from userid 1000) id 43C6B56411B3; Tue, 28 Apr 2020 12:53:08 -0400 (EDT)
X-Mailer: emacs 25.2.2 (via feedmail 11-beta-1 I); VM 8.2.0b under 25.2.2 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <24232.24434.41224.396200@oz.mt.att.com>
Date: Tue, 28 Apr 2020 12:53:06 -0400
From: Jay Borkenhagen <jayb@braeburn.org>
To: sidrops@ietf.org
In-Reply-To: <87pnbrspdr.wl-morrowc@ops-netman.net>
References: <87pnbrspdr.wl-morrowc@ops-netman.net>
Reply-To: Jay Borkenhagen <jayb@braeburn.org>
X-GPG-Fingerprint: DDDB 542E D988 94D0 82D3 D198 7DED 6648 2308 D3C0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/XtdXoKVlm4_ny3Xqy9O9Tg4GvcM>
Subject: [Sidrops] ASPA duplicates
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: Tue, 28 Apr 2020 16:53:14 -0000

The current ASPA Verification draft:


... says in Section 3 "For a selected Customer AS MAY exist only
single ASPA object."

I concur that an ASPA object should list every authorized upstream ASN
to avoid possible race conditions, and as such it makes sense for only
a single ASPA object to exist at any point in time.

But how is that uniqueness to be ensured?  What should RPs do if
multiple validated ASPA objects are ever found to exist?


						Jay B.