SIDROPS Working Group

 IETF 116  Yokohama 
 Wednesday 29 March 2023 04:00 - 06:00 UTC

• Chair Slides / AOB - 5 mins

• "RPKI Ecosystem Measurement"
  https://datatracker.ietf.org/doc/slides-116-sidrops-rpki-ecosystem/

  Randy Bush - 20 minutes

  "the problem is, its a pull protocol"

  there was a lively discussion at the microphone.

• "ASPA deployment experience-yycix
  https://datatracker.ietf.org/doc/slides-116-sidrops-aspa-deployment-experience-yycix/

  Job Snijders - 5 Minutes

  suggests that ASPA invalids should be DROPPED at the start, not
  later on as we did with ROA (with only 5 active ASPA)
  discussion at the level of SHOULD vs MUST on this, applicability to
  IX, general case

• "Update on draft-spaghetti-sidrops-aspa-slurm
  https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-aspa-slurm/

  Job Snijders - 5 Minutes

  seeking the lowest common denominator/MVP for SLURM in ASPA amongst
  the RP/RTR developers. KISS principle

  also seeking WG adoption. Some interest in the room in this work

• "Update on draft-ietf-sidrops-rfc6482bis
  https://datatracker.ietf.org/doc/draft-ietf-sidrops-rfc6482bis/01/

  Job Snijders - 5 Minutes

  WGLC on the proposed BIS. Nobody spoke against so it goes to the
  list for WGLC noting some concerns/nits to come

• "draft-spaghetti-sidrops-rpki-asgroup" (new work)
  https://www.ietf.org/id/draft-spaghetti-sidrops-rpki-asgroup-00.html

  Job Snijders - 15 Minutes

  the inevitable consequences of not having flag days in a world of
  IRR/RPSL and RPKI signed objects. proposing a strawman 3779 related
  ASN1 object to manage the AS_SET/grouping function in a managed
  cryptographically verified hierarchical manner

  Some lively discussion. If this is a strawman it did it's job (hah)

• "ASPA-based AS Path Verification Draft Update"
  https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-aspa-verification

  Kotikalapudi Sriram - 10 Minutes

  v13 in WGLC. No time for Qs

• "RFC 8183 BPKI Key Rollovers" (new work)
  Tim Bruijnzeels - 20 Minutes

  mechanistic and logistical issues around managing children, so its
  not RPKI its the bPKI alongside
  proposes 2 docs. Comment from Chat: (RobA) I want problem analysis
  for what Tim is talking about before we decide what protocol changes
  are needed. Best practice document is reasonable.