On Dec 22, 2022, at 5:00 PM, Eliot Lear <l...@lear.ch> wrote: > I view this differently. First, we don't have good deployment numbers for > TEAP. If we bump the version and nobody is using TEAP, then nobody will > care. If we don't bump the version and people ARE using TEAP, we'll get to > hear from everyone who cares! From a code standpoint, I imagine that the > incompabitibilies will be small in number, and so we're talking about a > handful of conditionals.
We have "something" implemented today as TEAPv1. Whatever it is, it's shipped by multiple vendors on tens of millions of devices. Plus, there are multiple other vendors planning on shipping TEAP support in Q2 2023. We can rev TEAP, but we can't change existing implementations. And any new rev will be deployed in the time frame (at best) of 12-18 months. If we document 7170bis now "as implemented", that can be done in a short time frame. We then have the freedom to do whatever we want with TEAPv2. But I'm wary of not documenting TEAPv1, and I'm wary of delaying that documentation in the interest of doing a TEAPv2. I'm not even sure what we'd do for TEAPv2. There isn't much point in changing the key derivations. The current one is arguably suboptimal, but it works. I wouldn't see a need to change it for something "better" in a TEAPv2. So I'd like to know what would be in TEAPv2, and what issues there would be if we just documented TEAPv1 "as implemented". Alan DeKok. _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
