Re: [Sidrops] Call for SIDROPS WG Agenda Items

Hi Alexander,

Nice drafts! I have some questions that may come back when you present, but let me ask here as well.

In-line

> On 28 Jun 2018, at 15:57, Alexander Azimov <aa@qrator.net> wrote:
> 
> I would like to reserve 15 minutes for:
> https://datatracker.ietf.org/doc/draft-azimov-sidrops-aspa-profile/ <https://datatracker.ietf.org/doc/draft-azimov-sidrops-aspa-profile/>

Since it’s the customer ASN who signs would it be a good idea if they listed all provider ASNs in a single object? There is no fate sharing risk like we have in ROAs when including multiple signing prefixes. On the other hand this would guarantee atomicity.

One small thing, eventually this will need a filename extension to be included in the IANA “RPKI Repository Name Scheme” registry. See also:
https://tools.ietf.org/html/rfc6481#section-7.2 <https://tools.ietf.org/html/rfc6481#section-7.2>

> https://datatracker.ietf.org/doc/draft-azimov-sidrops-aspa-verification/ <https://datatracker.ietf.org/doc/draft-azimov-sidrops-aspa-verification/>

I am not entirely clear on the AS_PATH verification in section 5. It reads to me like the outcome is invalid, or unverifiable if not all of the ASNs on the path have published ASPAs. And that unverifiable is considered close to invalid. But I may have misunderstood.. so I would be particularly interested in this part of your presentation.

All that said, I think that it would be extremely useful if a partial, incremental deployment can be supported. IMHO one of the big issues with BGPSec deployment is that it’s all or nothing, so there really is no incentive to deploy until everybody else has done so. With ASPAs you could argue that a route should be dropped if any of the pairs in the path turns out to be invalid, but it’s okay to accept unknowns. This would allow ASNs to get benefits from publishing ASPAs without requiring that everyone else does so as well. Of course things will be better when they do as well, but until that time there still is a benefit. So, there is incentive for ASNs to be pro-active.

But as I said.. I am not sure that I got this section 5 completely..

Regards,

Tim

> 
> 2018-06-28 1:33 GMT+03:00 Keyur Patel <keyur@arrcus.com <mailto:keyur@arrcus.com>>:
> Done. Thanks.
> 
> Regards,
> Keyur
> 
> > On Jun 27, 2018, at 3:32 PM, George Michaelson <ggm@algebras.org <mailto:ggm@algebras.org>> wrote:
> > 
> > I have been asked by my RIR colleagues to talk about modified
> > validation deployment planning. I think about 10 minutes should do it.
> > 
> > cheers
> > 
> > -george
> > 
> >> On Thu, Jun 28, 2018 at 6:34 AM, Keyur Patel <keyur@arrcus.com <mailto:keyur@arrcus.com>> wrote:
> >> Done. Thanks.
> >> 
> >> Regards,
> >> Keyur
> >> 
> >> On 6/27/18, 1:32 PM, "Randy Bush" <randy@psg.com <mailto:randy@psg.com>> wrote:
> >> 
> >>> SIDROPS will meet at IETF-102 on Monday, July 16th from 1:30 pm - 3:30
> >>> pm. Please forward any SIDROPS agenda items you may have to Chris and
> >>> me. Please also make sure that your slides are available to the chairs
> >>> by Friday morning (07/13/2018). Slides received after the deadline may
> >>> not be available for use during the meeting.
> >> 
> >>    i would appreciate 10-15 minutes to discuss
> >> 
> >>        draft-ymbk-sidrops-ov-signal-01
> >> 
> >>    i do NOT plan to present it.  folk who want to discuss it and/or have
> >>    questions MUST have read it beforehand.
> >> 
> >>    randy
> >> 
> >> 
> >> _______________________________________________
> >> Sidrops mailing list
> >> Sidrops@ietf.org <mailto:Sidrops@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org <mailto:Sidrops@ietf.org>
> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>
> 
> 
> 
> -- 
> | Alexander Azimov  | HLL l QRATOR
> | tel.: +7 499 241 81 92
> | mob.: +7 915 360 08 86
> | skype: mitradir
> | mailto: aa@qrator.net <mailto:aa@qrator.net>
> | visit: www.qrator.net <http://www.qrator.net/>_______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops