Re: [Sidrops] Format of ASPA RTR PDU

Martin Hoffmann <martin@nlnetlabs.nl> Wed, 06 December 2023 10:12 UTC

Return-Path: <martin@nlnetlabs.nl>
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 A52EFC14F5FF for <sidrops@ietfa.amsl.com>; Wed, 6 Dec 2023 02:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.085
X-Spam-Level:
X-Spam-Status: No, score=-6.085 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nlnetlabs.nl
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 PgEZ-YuwsgfD for <sidrops@ietfa.amsl.com>; Wed, 6 Dec 2023 02:12:53 -0800 (PST)
Received: from mout-b-206.mailbox.org (mout-b-206.mailbox.org [IPv6:2001:67c:2050:102:465::206]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 3D988C14F5E8 for <sidrops@ietf.org>; Wed, 6 Dec 2023 02:12:51 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-206.mailbox.org (Postfix) with ESMTPS id 4SlYB62zXkz9tBY for <sidrops@ietf.org>; Wed, 6 Dec 2023 11:12:46 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nlnetlabs.nl; s=MBO0001; t=1701857566; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: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=W6gFHS5qL2H3U5o7Sq0dRPgvA7UwznzoU+D+ak9apqQ=; b=ETXlnQxmVof56nJ625gp3a0KDjNCxDe1BCJPRtl6LXH8tLrYrYHBcE/fvlqJGLpx9Z/tVM clBNRBoeHTFvQPY869yzcEReeGgDwNFVpz2P5JLX4eONc9hIPal1xUeojfkegVGyq8f54u Bbs/HpCLiw3+sE9XQLw0RbrWkNd8itzzcrsyu6wjbVAbOWnbR0TyOgULbZcRJ5gZhX2fj/ RAYwk2vPE6aISJy2CDwAS/e5oLPawTlauVb69CirWl+xeY73MEM1O9GQhPTo07Ym+2b86z +STm9caipwR53NQjaBxqbwYdseTE4eSk2vW+RrC9KIU7W1UVVqUZK42ZqLv7pQ==
Date: Wed, 06 Dec 2023 11:12:46 +0100
From: Martin Hoffmann <martin@nlnetlabs.nl>
Cc: sidrops <sidrops@ietf.org>
Message-ID: <20231206111246.077a9d46@glaurung.nlnetlabs.nl>
In-Reply-To: <63ecbc8e-afe9-468a-9f84-91ed436ac4ce@nic.cz>
References: <0d8fcb69-54e1-4ba3-b5c9-29f93b3271eb@nic.cz> <ZUpWsu5xtPSJwUN2@diehard.n-r-g.com> <20231108103704.45af35c2@glaurung.nlnetlabs.nl> <ZUtYi01nYNExFAOY@diehard.n-r-g.com> <63ecbc8e-afe9-468a-9f84-91ed436ac4ce@nic.cz>
Organization: NLnet Labs
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/kDdjDDPG9QjMBQtkzz1gGcKNOz0>
Subject: Re: [Sidrops] Format of ASPA RTR PDU
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: Wed, 06 Dec 2023 10:12:58 -0000

Dear Working Group Chairs,

can we please get some guidance as to what should happen with the
8210bis draft?

We’ve now had feedback from three implementers suggesting that the
ASPA PDU proposed in the document is flawed in light of the revised
ASPA profile and algorithm.

But even so, there are now more people looking into adding ASPA support
to their RTR code and we really need clarity on how the RTR ASPA PDU is
supposed to look, lest we end up with severe interoperability issues
down the line.

  -- Martin