We got some good responses from the TLS list on the interpretation of their suites, please review them:
https://mailarchive.ietf.org/arch/msg/tls/LXBUvjMdhEpgIEC1CEzTuDKZNwY/ OS On Mon, Jan 8, 2024 at 8:33 AM Manu Sporny <[email protected]> wrote: > On Mon, Jan 8, 2024 at 4:19 AM Neil Madden <[email protected]> > wrote: > > It’s pretty clear that we’re just talking past each other now. I’ve made > the points I wanted to make. I don’t think you have addressed any of them, > so I still don’t support adoption of this draft. > > I found Neil's concerns compelling. > > For better or worse, JOSE uses "polymorphic" algorithm identifiers and > that's the way things have worked for a long time. The Working Group > was warned that this was not a good idea at the time, but rough > consensus landed in the "polymorphic" camp and that's what the > ecosystem does today. > > Adding more options to support both "polymorphic" and "fully > specified" approaches creates additional complexity that will lead to > interoperability failures. Don't complicate the ecosystem more than it > already is. > > I do not support the adoption of this draft for the reasons Neil > mentioned as well as the reasons stated above. > > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > https://www.digitalbazaar.com/ > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
