search

nihalpasham / rustdhipv2

A prototype implementation of the Host Identity Protocol v2 for bare-metal systems, written in pure-rust.
MIT License
37 stars 7 forks source link

Slight inaccuracy in README, related RFCs #2

Closed eternaleye closed 3 years ago

eternaleye commented 3 years ago

In the "Conclusion" section, you state:

Note - Certifying public keys or otherwise creating trust relationships between hosts has explicitly been left out of the HIP architecture, it is expected that each system using HIP may want to address it differently.

However, this is not entirely accurate. In HIPv1, HIP Certificates were specified in RFC 6253, which was then updated for HIPv2 as RFC 8002. It's far from mandatory, and alternative trust mechanisms are openly and explicitly discussed in the relevant RFCs, but it is part of the architecture.

You may also be interested in some of the other RFCs in the working group's document tracker, such as RFC 8046, which acts to pull together the topics relevant to making mobility work with HIPv2. There's also a draft (submitted to the IESG for publication as an RFC, but sitting in queue) covering NAT traversal.

EDIT: I would like to say that I'm quite excited to find this project - I've been interested in HIPv2 for some years now, but never managed to get over the line and start implementing it in Rust myself.

nihalpasham commented 3 years ago

Thanks for this. I can see how my conclusion can be confusing.

I meant to say - HIPv2 doesn't mandate the use of a specific method when it comes to 'establishing trust'.

I'll update it.

Note: although this is an early PoC for now, I intend to keep working on it as time permits. But please feel free to contribute.