minutes-124-sidrops-202511031930-00

Chairs:

Russ Housley ( housley AT vigilsec.com )
Luigi Iannone ( ggx AT gigix.net )

SECRETARY: Krishnaswamy Ananthamurthy (kriswamy AT cisco.com)

Monday, November 3, 2025 - Session 1/1 (120 Minutes)

14:30 - 16:30 Montreal (EST), Session III, 120 Minutes
- 11:30 -> 13:30 PST (San Francisco)
- 14:30 -> 16:30 EST (New York)
- 19:30 -> 21:30 UTC
- 20:30 -> 22:30 CET (Paris)
- 03:30 -> 05:30 CST (Beijing - Note: November 4)
- 06:30 -> 08:30 AEDT (Sydney - Note: November 4)

Room: Van Horne

AGENDA

0. Administration

Speakers: Russ/Luigi/Krishna
- Agenda Bashing
- Status reports for WG drafts
5 Minutes (Cumulative Time: 5 Minutes)

1. Rechartering Discussion

Speakers: All
- https://datatracker.ietf.org/doc/charter-ietf-sidrops/
40 Minutes (Cumulative Time: 45 Minutes)

Job: I agree with Chairs decision.
RPKI is 15+ yeras old. Implmenting the code is the key before it
gets RFC.
John: One Client and Server is count as 2 saperate things.
Job: It is bare minimum. 2 client and 2 server implmentation is what
I belive. Legally 1 clinet and 1 server is good enough.
Luigi: It was raised in mailing list and at a minimum, one client
and one server are required.
Tim: At a minimum, one client and one server are required.
Rob: Recommends 2 Servers and 2 Clients.
Job: Agree with Rob, but we capture it in charter is key.
Implmentation is subjective like, open source, closed, deployment
grade or not doesn't matter.
Maria: Implmentations should be available for public to evalute
Tobias: Agree with Maria.
Luigi: Agree with 2 implmentations on client.
Rudiger: It is not a good thing on the rules very preciesly.
Luigi: Real concensus on 1 or 2 implmentations from client/server
Tim: There should be a clear consensus on having 1 or 2
implementations on the client and server sides.

Job: Most of the goals are good. YANG models are part of the SIDROPS
goals.
Luigi: Disagree. Charter is about scope. We need to include it as a goal
like YANG if needed.
Job: Enumerating all in the charter might not be possible.
Rudiger: SNMP is kind of obselote. Refer to RFC XXXX. YANG covers
majority of things.

2. NRO TA Constraints

Speaker: Tim Bruijnzeels
- https://www.ietf.org/archive/id/draft-nro-sidrops-ta-constraints-00.txt
15 Minutes (Cumulative Time: 60)

3. The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)

Speaker: Job Snijders
- https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-erik-protocol/
15 Minutes (Cumulative Time: 75)

4. A Profile for Resource Public Key Infrastructure (RPKI) Canonical Cache Representation (CCR)

Speaker: Job Snijders
- https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-ccr/
5 Minutes (Cumulative Time: 80)

5. Transition to Full BGPsec Deployment: Transitive-BGPsec is Incompatible with BGPsec

Speaker: Zhuotao Liu
- https://datatracker.ietf.org/doc/html/draft-wang-sidrops-bgpsec-transition
10 Minutes (Cumulative Time: 90)
Rudiger: Refer to 2011 transitioning from BGP to BGP Sec. Not Major
vendors are not implementing BGP Sec

6. Forwarding Commitment BGP Testbed and Deployment Experience

Speaker: Ziwei Li
- https://datatracker.ietf.org/doc/draft-li-sidrops-fcbgp-experiment/
5 Minutes (Cumulative Time: 95)

7. Filtering Out RPKI Data by Type based on Enhanced SLURM Filters

Speaker: Yu Fu
- https://datatracker.ietf.org/doc/draft-fu-sidrops-enhanced-slurm-filter/
10 Minutes (Cumulative Time: 105)

8. Open Source Tools for RP Testing

Speakers: Jorge Cano / Carlos Martinez
- https://github.com/LACNIC/barry
- https://github.com/LACNIC/rapport
10 Minutes (Cumulative Time: 115)

Meeting Wrap-Up / Buffer Time

Speakers: Russ/Luigi/Krishna
5 Minutes (Cumulative Time: 120)

IF TIME ALLOWS