Minutes interim-2026-ediint-01: Thu 14:00
minutes-interim-2026-ediint-01-202603051400-00

IETF EDIINT Interim Meeting Notes
2026-03-05 9h00-10h30 Eastern

~14 participants

Agenda

• Charter review, co-chairs
• draft-petta-rfc4130bis, Debra Petta

Charter review, Joe Mandel, co-chair

• see
  https://datatracker.ietf.org/doc/slides-interim-2026-ediint-01-sessa-chair-slides/
• charter text is shown on screen and briefly summarized
• no questions asked

draft-petta-rfc4130bis, Debra Petta

• see
  https://datatracker.ietf.org/doc/slides-interim-2026-ediint-01-sessa-rfcbis/
• S/MIME 3.2 support only for original RFC4130
• what happens with mix of S/MIME 3.2 and 4.0
• MD5, SHA-1, 3DES, RC2 support only for original RFC4130
• Bojidar Ivanov: AES-256-CBC MUST because of FIPS requirements
• Erik Wramner: customers may not migrate soon to new algos
• Russ Housley: OAEP not implemented by CAs. MUST ECDH
• Asger Smidt: our customers do their own configuration, without
  implementators/service providers being involved
• someone: we need a way for a peer to advertise in advance which AS2
  version it is supporting, instead of only doing with AS2-Version
  header.
• Marc Blanchet: need to differentiate between migration and new
  standard
• Bojidar Ivanov: two different problems: new servers supporting new
  standard with strong algorithms, and other issue is to support both
• Erik Wrammer: two documents is more difficult for implementors to
  read both
• Marc Blanchet: look at .well-known for discovery (RFC8615)
• Erik Wrammer: .well-known is JSON, while EDI is XML. Not a big
  hurdle however.
• Asger Smidt: we should work first on 1.3 and then 2.0 later.
• at slide 31 "Approach to Feature Documentation", Joe Mandel,
  co-chair, says that the meeting time is almost over and a new
  interim meeting will be scheduled to continue the rest of the slide
  deck, most likely in April, after IETF week.