Administrative
Jabber scribe: Job Snijders
Minute taker: Nathalie Trenaman

Chairs:
Chris Morrow
Keyur Patel

Agenda:
0) Agenda bashing and Chair's slides - [5 minutes]

1) Tim Bruijnzeels - [15 minutes]
https://datatracker.ietf.org/doc/draft-sidrops-bruijnzeels-deprecate-rsync/

2) Randy Bush - [10 minutes]
https://datatracker.ietf.org/doc/draft-ymbk-sidrops-transfer/

3) Alexander Azimov - [10 minutes]
https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-profile/
https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/

3) Randy Bush - [10 minutes]
https://datatracker.ietf.org/doc/draft-ymbk-sidrops-transfer/

4) Di Ma - [10 minutes]
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rp/

5) Di Ma - [10 minutes]
Distributing RPKI Validated Cache in JSON over HTTPS

6) Oliver Borchert - [15 minutes]
https://datatracker.ietf.org/doc/draft-borchert-sidrops-bgpsec-state-unverified/
https://datatracker.ietf.org/doc/draft-borchert-sidrops-rpki-state-unverified/

Added to the agenda: 

Tim Bruijnzeels 
https://datatracker.ietf.org/doc/draft-sidrops-bruijnzeels-deprecate-rsync/ 
Discussion:
Geoff Huston: rsync was a mistake from the beginning. Problem is reliable flooding of information. I'm not sure if RRDP is the solution. Are we not replacing one bad thing with another? Are there alternatives that do reliable flooding? This doesn't seem to change a lot;
Tim: At this moment supporting rsyinc is impacting people
Ruediger: I oppose using BGP for flooding. Maybe reseach groups can look into altertatives. We need to have a roadmap to move forward. The repositories have to move first, but RP can't be left behind. A fixed timeschedule will not work. 
Di Ma: I like your idea, I'm wondering if you is easy to support delta protocol.
Tim: I think the tricky part is generating the files. I agree with Ruediger, we should build operational experience. RIPE NCC has extensive experience with RRDP
Di Ma: Delta is working much better than rsynch in our testbed
Randy: Is there another sequense that doesn't drop things on the floor?
Tim: I want RP software to move forward. A roadmap might get outdated in an RFC. 
Job: It is good if IETF, in a BCP, that rsync is not prefered. State why we don't like rsync for this purpose
Rob Arccus: The problem to completely remove rsync, is hashes. Our CA code was designed badly. There are a few interesting characteristics on the RP side, especially for large repositories like RIPE NCC.I think RRDP is mature enough to move forward. 
Tim: I will send an adaption call to the list. 

Randy Bush 
https://datatracker.ietf.org/doc/draft-ymbk-sidrops-transfer/ -
Discussion:
    



Alexander Azimov 
https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-profile/
https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/
Discussion:
    



Di Ma 
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rp/
Discussion:

Di Ma 
Distributing RPKI Validated Cache in JSON over HTTPS
Discussion:

Oliver Borchert 
https://datatracker.ietf.org/doc/draft-borchert-sidrops-bgpsec-state-unverified/
https://datatracker.ietf.org/doc/draft-borchert-sidrops-rpki-state-unverified/
Discussion: