Hi Roland! (And greetings to my former hometown, Karlsruhe!)
On Tuesday, March 8th, 2022 at 12:21, Bless, Roland (TM) roland.bl...@kit.edu wrote: > I'm not sure about your requirements. I think that identifiers for AAA > > can be unique and static on their "layer" and do not need to coincide > > with network addresses. > > (snip) I agree; this is also the approach we currently take. The set of requirements for drones is complex, and I have not laid it out well - mostly because this conversation thread is about addressing, while most of the issues I perceive are to do with routing. Of course the two are hard to separate. I also have another use case in mind that is unrelated to drones. I have been pointed in some interesting directions on this list - thank you all! - and I think at this time it's best that I read through this material carefully. I can then come back, lay out my use cases, and provide some comments on which approach does and does not work so well from their point of view. That seems a lot better than continuing, because conceptually, the split between identifier and locator as proposed makes a lot of sense to me as well; we're effectively pursuing much the same direction. Jens
publickey - jens@interpeer.io - 0x5C345E9C.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
