Re: [Sidrops] Format of ASPA RTR PDU

Claudio Jeker <cjeker@diehard.n-r-g.com> Thu, 16 November 2023 19: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 56239C14CE54 for <sidrops@ietfa.amsl.com>; Thu, 16 Nov 2023 11:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 Mmsrqty91SzB for <sidrops@ietfa.amsl.com>; Thu, 16 Nov 2023 11:09:17 -0800 (PST)
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 DEEDBC14CE42 for <sidrops@ietf.org>; Thu, 16 Nov 2023 11:09:15 -0800 (PST)
Received: (qmail 14516 invoked by uid 1000); 16 Nov 2023 19:09:12 -0000
Date: Thu, 16 Nov 2023 20:09:12 +0100
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: "Borchert, Oliver (Fed)" <oliver.borchert@nist.gov>
Cc: Martin Hoffmann <martin@nlnetlabs.nl>, Maria Matejka <maria.matejka=40nic.cz@dmarc.ietf.org>, sidrops <sidrops@ietf.org>, Kateřina Kubecová <katerina.kubecova@nic.cz>, Ondrej Zajicek <santiago@crfreenet.org>
Message-ID: <ZVZo2GpiccGGO1gi@diehard.n-r-g.com>
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> <BLAPR09MB6322518A5183FC1724C7657598B0A@BLAPR09MB6322.namprd09.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <BLAPR09MB6322518A5183FC1724C7657598B0A@BLAPR09MB6322.namprd09.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/BKhA2FUv1kpC5k5rMuQ5l5klEAc>
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: Thu, 16 Nov 2023 19:09:21 -0000

On Thu, Nov 16, 2023 at 05:07:11PM +0000, Borchert, Oliver (Fed) wrote:
> Re-reading the email of Claudio from Sept. 22 which he referred to,
> in particular the very first comment made me wonder.
> 
> 4.  Operational Overview
> 
>    ... It is configured with a semi-ordered list of caches and establishes a
>    connection to the most preferred cache, or set of caches, caches with that
>    same priority, which accept the connections.
> 
> You added something about priority. Now this is the only time a priority
> is mentioned in this whole document. There is no description on what such
> a priority is and why it is required.
> 
> I re-read the original 8210 for comparison and the changes are not much, only the
> Introduction of the mentioned priority. I understand the priority in the sense of
> only choosing the configured cache(s) with the highest priority.
> Thinking more about using data from 2 or more caches simultaneously and not for fallback,
> made me stumbled upon something that confuses me.
> 
> PDU 11 (Section 5.12) mentions in the second paragraph that:
> “The router MUST see at most one ASPA from a cache for a particular Customer Autonomous System Number active at any time.”
> This makes sense, considering that an ASPA PDU overwrites the previous one.
> I am now asking myself, what if the router uses two caches simultaneously, both with
> the same priority and receives its information from both.
> 
> In this case the router might see 2 ASPA’s for a particular CAS – though only a single
> one per cache, but still two active ones.
> What if their content is different? For ROAS and Keys there is no problem but how
> to deal with this in ASPA? 2 caches, both of same priority, but here conflicting ASPA
> information? A different list of Providers?
> Guidance would be nice here – maybe there is but I did not find it.

This is covered in draft-ietf-sidrops-aspa-verification-16 Section 3:

If a CAS has a single ASPA, then the SPAS for the CAS is the set of
Provider ASes listed in that ASPA. In case a CAS has multiple ASPAs, then
the SPAS is the union of the Provider ASes listed in all ASPAs of the CAS.

This is how we implemented this case. 
 
> On 11/8/23, 4:45 AM, "Sidrops" <sidrops-bounces@ietf.org> wrote:
> 
> On Wed, Nov 08, 2023 at 10:38:38AM +0100, Martin Hoffmann wrote:
> > Claudio Jeker wrote:
> > > On Tue, Nov 07, 2023 at 04:00:49PM +0100, Maria Matejka wrote:
> > > >
> > > > While trying to implement ASPA in RTR, we got confused by § 5.12,
> > > > ASPA PDU, as of draft-ietf-sidrops-8210bis-11. Bytes 2 and 3 are
> > > > set to zero and bytes 10 and 11 are encoding Provider AS Count
> > > > which can be inferred from the overall PDU length easily. Is there
> > > > any good reason to have this redundant information inside the PDU?
> > > > We are suggesting to move the Flags and AFI Flags to bytes 2 and 3
> > > > and to drop Provider AS Count completely. The Customer ASN would
> > > > then start at byte 8 and Provider ASNs would start at byte 12.
> > >
> > > To be honest, the RTR bits are nowhere close to be ready. Especially
> > > these questions have been raised numerous times by various developers
> > > implementing this draft but the authors seem to not listen.
> > > Right now draft-ietf-sidrops-8210bis is holding up all of ASPA.
> >
> > Ironically, all of ASPA is holding up publishing 8210bis. Maybe it is
> > time to admit that moving it forward was a mistake and use the
> > opportunity to get it back and fix the issues properly?
> 
> That happened a few weeks ago. There is now draft-ietf-sidrops-8210bis-11
> pulished on 2023-09-21. I sent my feedback on 2023-09-22 see
> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FqOygwqeF8PGZeSMCt5Hjq8_jGU4%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cbe033b2211c8417b920d08dbe03f60e7%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638350335063634454%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RPews9mCu12TE%2ByYTeLkeInZ4oh7cWGVu%2BGBhOn9mz8%3D&reserved=0<https://mailarchive.ietf.org/arch/msg/sidrops/qOygwqeF8PGZeSMCt5Hjq8_jGU4/>
> 
> I would love to see your feedback to the -11 update.
> --
> :wq Claudio
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&data=05%7C01%7Coliver.borchert%40nist.gov%7Cbe033b2211c8417b920d08dbe03f60e7%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638350335063634454%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ly9hgq6e5DNrJjUQB9S%2BQ4Sp6wCxuJFoXlJ2wfSNI8A%3D&reserved=0<https://www.ietf.org/mailman/listinfo/sidrops>

-- 
:wq Claudio