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

["Borchert, Oliver (Fed)" <[e-mail]>]

I read over the document, and I am happy with the latest version which follows the algorithm description that was presented at IETF 110 (https://datatracker.ietf.org/meeting/110/materials/slides-110-sidrops-sriram-aspa-alg-accuracy-01) which is implemented in the NIST BGP-SRx reference implementation (route server portion needs still some tweaks in the BGP-SRx code base as of now).

I support the WGLC, thanks for the hard work,

Oliver


From: Sidrops <[e-mail]> on behalf of Christopher Morrow <[e-mail]>
Date: Tuesday, March 7, 2023 at 8:38 PM
To: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram=[e-mail]>
Cc: Claudio Jeker <[e-mail]>, Job Snijders <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, Compton, Rich A <[e-mail]>
Subject: Re: [Sidrops] WGLC = draft-ietf-sidrops-aspa-verification - ENDS 03/22/2023 (Mar 22 2023)
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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-sidrops-aspa-verification%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=L7RbGNQKj%2FY78viTIYZvNjF%2FOzyxnSJwSH4paGm%2B534%3D&reserved=0

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

Thanks for hanging in there:
  https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fm.media-amazon.com%2Fimages%2FI%2F41iPPNniyOL._AC_.jpg&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=k%2B0j%2BQXEu35P8lFN9SdhaCeXCnBC8tiFV1R7FoIMp0Y%3D&reserved=0

-chris
co-chairiot

On Thu, Feb 9, 2023 at 1:09 PM Christopher Morrow
<[e-mail]> 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
> <[e-mail]> wrote:
> >
> > On Fri, Jan 27, 2023 at 10:51 AM Sriram, Kotikalapudi (Fed)
> > <kotikalapudi.sriram=[e-mail]> 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FKlILGgdItF-0O-xUsJde1DqGCoE%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9CeAoDzNi1LGmXv8lMg%2Bwapp%2FDjggxaFc8Y%2BH3sg8S4%3D&reserved=0
> > > My Nov 4th response: https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FcWcF2Y0msvko73zY912Y3cQj7SM%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=J6k4YBx%2B%2F58nRlXGQiGPWZzQWlRtrnEMWixWFSUa3rA%3D&reserved=0
> > >
> > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FJgxHTtynu-mihYnPxw1xgVGopPg%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=hC16Whw5iBBJVf9I6k%2B%2BV2BePlaOpujmEO16OqLwtUM%3D&reserved=0
> > >
> > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FJgxHTtynu-mihYnPxw1xgVGopPg%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=hC16Whw5iBBJVf9I6k%2B%2BV2BePlaOpujmEO16OqLwtUM%3D&reserved=0
> > >
> > > Also, I plan to incorporate comments from Rich Compton:
> > >    https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FzPXDR5iL52REtpIDoL6qdvJ2IsI%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=rtrRaeLUzvpLO7T3vFbNoODdVa1vQXwAfdwxmFla0NE%3D&reserved=0
> > >
> > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fsidrops%2FC6Ethp2aC9sJsxDtBrLQDjmCqk4%2F&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=s9wjdskY%2FeyzlaINcOZ1TpCohbsH9PeIgrjIMlMDEuo%3D&reserved=0
> > > 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
> > > [e-mail]
> > > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=%2FOzE9xYs%2BRKU20UqIv9QJPK6m%2BsC5KFfCM59rlboLnc%3D&reserved=0

_______________________________________________
Sidrops mailing list
[e-mail]
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsidrops&data=05%7C01%7Coliver.borchert%40nist.gov%7Cb7e781cb9d5a40459df808db1f759e88%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638138363180478901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=%2FOzE9xYs%2BRKU20UqIv9QJPK6m%2BsC5KFfCM59rlboLnc%3D&reserved=0