This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[iot-wg] algorithm agility for IoT
- Previous message (by thread): [iot-wg] algorithm agility for IoT
- Next message (by thread): [iot-wg] algorithm agility for IoT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Mon Jan 21 14:47:24 CET 2019
> On 21 Jan 2019, at 13:29, Mat Ford <ford at isoc.org> wrote: > > Hi Jim, > >> On 21 Jan 2019, at 12:53, Jim Reid <jim at rfc1035.com> wrote: >> >> * It’s such basic common sense it isn’t written down anywhere. As least I’ve not been able to find it in a standards document yet. Which means that common sense can’t get baked into equipment procurements, RFPs and so on. So if there’s an RFC or ITU Recommendation or whatever along those lines... > > See https://datatracker.ietf.org/doc/rfc7696/ Thanks Mat. RFC7696 is mostly about the trade-offs and implementation choices. It has lots of great advice. However it’s not quite on target. Which is about trying to ensure IoT platforms have the frameworks to support diverse implementation choices. And of course those choices almost certainly will change over time as new algorithms emerge and old ones get killed. ie It’s about how to facilitate those choices, not the choices themselves. If you consider RFC7696 as a meta-discussion on making those choices, I’m aiming at a meta-meta discussion about how IoT platforms can enable things like RFC7696-based decision making.
- Previous message (by thread): [iot-wg] algorithm agility for IoT
- Next message (by thread): [iot-wg] algorithm agility for IoT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]