Re: [Sidrops] WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023)

Christopher Morrow <christopher.morrow@gmail.com> Wed, 08 March 2023 01:36 UTC

Return-Path: <christopher.morrow@gmail.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 53CABC1526FB; Tue, 7 Mar 2023 17:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.428
X-Spam-Level:
X-Spam-Status: No, score=-0.428 tagged_above=-999 required=5 tests=[AMAZON_IMG_NOT_RCVD_AMZN=1.667, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 K90PJVGcXor6; Tue, 7 Mar 2023 17:36:31 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 44B52C15257A; Tue, 7 Mar 2023 17:36:31 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id j8so4872961ilf.4; Tue, 07 Mar 2023 17:36:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678239390; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ipEwQI8HNEqZ+ysv55gveOx9ekNEM0RKX9CPNri7/B4=; b=WyIQ+ED/JiJdE7II6bxBgBVD/B3fKPa7dSOGe979T4UEu5/W2IAFfCJlCZc62+pJZ6 hx0L3oUgfVolR5AQUzjayr+lDykR8xLKVYzjHZ94ciMwZLNwziBWY7uW0m/Py4ZX0ook lua1TVuJPIC4VmCUZPQlbCFrec6mpCuTAUBiwEHaz57pxOsgDtpwNSlkvlUZWZm7i7sv wSS+mU3heOQRZoe7QDw7X5YhewIXyEZiiZDB0c0lef5NhmxsFnBxq3uhgfQ+BgWV/49A Q0Aicympa7Y8K6PQxGg4TZxMcHbpE+TrTFNyDOZulmQX9zX9KdwAL8wVNt4kK5j5VSek oIGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678239390; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ipEwQI8HNEqZ+ysv55gveOx9ekNEM0RKX9CPNri7/B4=; b=Ia8iKuIpymkA2DAVXXDDv8zXbckkJa7jMrkgr6LNlTu9MVyQ6GzHKj+ChTOaJDhAxt ALCfYU4XSaZuDFFAW8H3P4XtHH39kDTG/nCdffh7a6zNJmcUCJA0lqnTeeokwAyWNd7+ s2R1J4GCRTjTl3fxqO1SLxDn+Mqg8+/01gWNi0B3LV08XFiuk4/xwP4IruWRRi+21qqY 0AzWRbDHzyq1XpoTEC7T+WjNNHZbwAxIGGsvXmM3CzsKWWuIJOWbND0tyLRV236DMZLo hNCfyqr88eroJRbXNxjwQs210NLCZG+8hDrRxoz82qseKU16qp+85gwOEfafJ/gDgzSP AOxA==
X-Gm-Message-State: AO0yUKV1PW0K3y/cQNgPkL+bqqzfV43J7NxdEGKRx3CD6aZzJ9fh591R W4OBYtDoDaP4J7czbKOunnuuXTmcDOP03Z+Pvcw=
X-Google-Smtp-Source: AK7set/3rzOKO4SWlYr5bbhX9NSBFk373LeRsNKBjkAlo3dYu5Z0RXGq2kk/UWgQ4xHYWt29x/6mZo/PmlPeFcauzNU=
X-Received: by 2002:a05:6e02:13c8:b0:315:50a4:c5e5 with SMTP id v8-20020a056e0213c800b0031550a4c5e5mr7848193ilj.2.1678239390162; Tue, 07 Mar 2023 17:36:30 -0800 (PST)
MIME-Version: 1.0
References: <SA1PR09MB814241245D01E81BADE3ED0884CF9@SA1PR09MB8142.namprd09.prod.outlook.com> <31FDE1E9-3E87-4011-B65B-C6B3A264303F@vigilsec.com> <SA1PR09MB81427B4A1B126A5D1C1E289C84CF9@SA1PR09MB8142.namprd09.prod.outlook.com> <SA1PR09MB8142E41F2D6B537BCAA758F384CC9@SA1PR09MB8142.namprd09.prod.outlook.com> <CAL9jLaYz3OhcwBBcVMqnUseBR9J1ZyktcJo5YLeefQHMoYJu+A@mail.gmail.com> <CAL9jLaZ7eDc+zbhapS8dTYQKnTfgLd=MOPYw97-qcJ4eP6S6Mg@mail.gmail.com>
In-Reply-To: <CAL9jLaZ7eDc+zbhapS8dTYQKnTfgLd=MOPYw97-qcJ4eP6S6Mg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 07 Mar 2023 20:36:19 -0500
Message-ID: <CAL9jLaYJ4ODfumG9Yk3-yv=_TaTSUeD++U4sGy7S-0xWcGBQPw@mail.gmail.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org>
Cc: Claudio Jeker <cjeker@diehard.n-r-g.com>, Job Snijders <job@fastly.com>, "sidrops@ietf.org" <sidrops@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, "draft-ietf-sidrops-aspa-verification@ietf.org" <draft-ietf-sidrops-aspa-verification@ietf.org>, "draft-ietf-sidrops-aspa-profile@ietf.org" <draft-ietf-sidrops-aspa-profile@ietf.org>, "Compton, Rich A" <Rich.Compton@charter.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KTwBImVNrmQLTjrSgT642v3YRrE>
Subject: Re: [Sidrops] 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, 08 Mar 2023 01:36:35 -0000

Guess who's not jumping the gun this time?? <this guy!>

Ok, the authors have asked ot re-issue this WGLC!!
I believe 3/22 will be 'just before ietf meeting' (25th start) so that
MAY be a little tight, if so we can skip til 4/12/2023. Either way,
please give the updated version:
  https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/

a solid read/consider and let's see how things feel by F2F meeting time?

Thanks for hanging in there:
  https://m.media-amazon.com/images/I/41iPPNniyOL._AC_.jpg

-chris
co-chairiot

On Thu, Feb 9, 2023 at 1:09 PM Christopher Morrow
<christopher.morrow@gmail.com> wrote:
>
> Guns were Jumped, Things were Slowed.. Did the new v12 appear? or is
> it appearing soon?
> (what's the timeline I mean to ask)
>
> On Fri, Jan 27, 2023 at 11:27 AM Christopher Morrow
> <christopher.morrow@gmail.com> wrote:
> >
> > On Fri, Jan 27, 2023 at 10:51 AM Sriram, Kotikalapudi (Fed)
> > <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org> wrote:
> > >
> > > Hi, Claudio and all,
> > >
> > > Yes, please wait a few weeks and then read the upcoming version 12 (ASPA verification) draft for commenting.
> > >
> >
> > yup! I jumped the gun, no worries. We can defer until -12 arrives.
> >
> > > I was puzzled as did some of my co-authors seeing the WGLC posted yesterday.
> > >
> > > I have closely interacted with Claudio who has a nearly complete implementation of ASPA verification. Much of the proposed revisions for v-12 are motivated by his feedback.
> > >
> > > Claudio wrote:
> > > >I sent a mail on Nov 2nd with a large amount of feedback to this draft.
> > > >None of it has been incorporated so a last-call for this draft is very
> > > >premature.
> > >
> > > Your Nov 2nd post: https://mailarchive.ietf.org/arch/msg/sidrops/KlILGgdItF-0O-xUsJde1DqGCoE/
> > > My Nov 4th response: https://mailarchive.ietf.org/arch/msg/sidrops/cWcF2Y0msvko73zY912Y3cQj7SM/
> > >
> > > Yes, your excellent and detailed feedback will be incorporated in v-12.
> > >
> > > Claudio wrote:
> > > >There are additional concerns I have with this draft after working on the
> > > >only BGP implementation over the last weeks. I will send a follow up
> > > >regarding my findings.
> > >
> > > Yes, please send. In part, you may be referring to the IXP RS AS (transp./non-transp.) and RS-client discussion we had (via video chat). I posted about our discussion and conclusions here:
> > > Jan 13, 2023 post: https://mailarchive.ietf.org/arch/msg/sidrops/JgxHTtynu-mihYnPxw1xgVGopPg/
> > >
> > > So, yes those proposed changes about the part of the verification algorithm that deals with IXP RS & RS-client will also be included in v-12.
> > >
> > > Claudio wrote:
> > > >1. Introduction
> > > >
> > > >    When the CAS has multiple Providers, all Provider ASes are listed in the
> > > >    ASPA including any internet exchange point (IXP) route server (RS) AS that
> > > >    serves the CAS.
> > >
> > > >This requirement is wrong and I will not approve any version of this draft
> > > >which requires inclusion of "any internet exchange point (IXP) route server
> > > >(RS) AS" in the SPAS.
> > >
> > > Yes, as you and I discussed, that requirement will only apply to non-transparent IXP RS AS. We'll make that clear in both ASPA drafts.
> > > This was also stated in my post of Jan 13: https://mailarchive.ietf.org/arch/msg/sidrops/JgxHTtynu-mihYnPxw1xgVGopPg/
> > >
> > > Also, I plan to incorporate comments from Rich Compton:
> > >    https://mailarchive.ietf.org/arch/msg/sidrops/zPXDR5iL52REtpIDoL6qdvJ2IsI/
> > >
> > > Job asked:
> > > >What is the status of ASPA in NIST BGP-SRx?
> > >
> > > I had posted about implementation of ASPA path verification in BGP-SRx in Dec. 2021:
> > > https://mailarchive.ietf.org/arch/msg/sidrops/C6Ethp2aC9sJsxDtBrLQDjmCqk4/
> > > BGP-SRx ASPA unit test cases/examples:
> > > https://github.com/usnistgov/NIST-BGP-SRx/blob/master/examples/example-demo-aspa-new/README
> > > BGP-SRx project Github page: https://github.com/usnistgov/NIST-BGP-SRx
> > >
> > > We have not yet included the IXP RS portion of the ASPA verification algorithm in BGP-SRx implementation.
> > >
> > > Thank you.
> > >
> > > Sriram
> > >
> > > _______________________________________________
> > > Sidrops mailing list
> > > Sidrops@ietf.org
> > > https://www.ietf.org/mailman/listinfo/sidrops