IETF Logo Mail Archive

Re: [Sidrops] Making ASPA AFI-Agnostic - coordination (Was: WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023))

Claudio Jeker <cjeker@diehard.n-r-g.com> Wed, 07 June 2023 09:09 UTC

Return-Path: <cjeker@diehard.n-r-g.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 61294C151075 for <sidrops@ietfa.amsl.com>; Wed, 7 Jun 2023 02:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.895
X-Spam-Level:
X-Spam-Status: No, score=-6.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
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 yPLrlJVRtAjn for <sidrops@ietfa.amsl.com>; Wed, 7 Jun 2023 02:09:43 -0700 (PDT)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 613BEC14CE2F for <sidrops@ietf.org>; Wed, 7 Jun 2023 02:09:42 -0700 (PDT)
Received: (qmail 785 invoked by uid 1000); 7 Jun 2023 09:09:39 -0000
Date: Wed, 07 Jun 2023 11:09:39 +0200
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
Cc: Job Snijders <job=40fastly.com@dmarc.ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Martin Hoffmann <martin@nlnetlabs.nl>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, "sidrops@ietf.org" <sidrops@ietf.org>, "draft-ietf-sidrops-8210bis@ietf.org" <draft-ietf-sidrops-8210bis@ietf.org>
Message-ID: <ZIBJUycE10HjIfAP@diehard.n-r-g.com>
References: <88D8A314-0D17-4EA7-9E33-424021AF0FFF@vigilsec.com> <SA1PR09MB814232A57F80E8B92637ABF684639@SA1PR09MB8142.namprd09.prod.outlook.com> <SA1PR09MB8142A3F0D8E30F4F154863A084639@SA1PR09MB8142.namprd09.prod.outlook.com> <SA1PR09MB81427668A874A3EEFDE61DAE846A9@SA1PR09MB8142.namprd09.prod.outlook.com> <20230428100855.3450881e@glaurung.nlnetlabs.nl> <SA1PR09MB8142DA858A2039F2ED7DAD2B846E9@SA1PR09MB8142.namprd09.prod.outlook.com> <20230502124540.6bc662ba@glaurung.nlnetlabs.nl> <CAL9jLaaL2vvRYL6+ftu8vP9fDWWBoF5NFCGGL_nDj+_VSc5E4Q@mail.gmail.com> <ZH+hdvAwuZ7nN3vK@snel> <4dbb0ef4-91fc-6bbd-d979-2d0b736295ac@tu-dresden.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4dbb0ef4-91fc-6bbd-d979-2d0b736295ac@tu-dresden.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/MZhj8HZXj0Tu3rKtCyahF8eFxAA>
Subject: Re: [Sidrops] Making ASPA AFI-Agnostic - coordination (Was: WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023))
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, 07 Jun 2023 09:09:44 -0000

On Wed, Jun 07, 2023 at 10:31:24AM +0200, Matthias Waehlisch wrote:
> 
> our plan is to update RTRlib during IETF 118 hackathon to support ASPA.
> 

I guess we need to figure out how to adjust RTR by then. Right now only
OpenBGPD and StayRTR seem to support ASPA record over RTR. Please correct
me if I'm wrong.

I told Job that I would prefer to not introduce a new RTR version, the
protocol version negotiation in RTR is underspecified and fragile.
It is probably enough to remove / force-to-zero the AFI flags field in the
ASPA PDU.

My plan for OpenBGPD is to remove the AFI support but still allow old
formats in for now. The system will union all AFI into a single table.
This will allow the couple of users to update then remove these old
formats (config and RTR).

-- 
:wq Claudio

v2.23.0 | Report a Bug | By Email