Open ewpratten opened 8 months ago
I realize that this is the wrong language, but I do have an implementation of this hiding away here if you are curious: https://github.com/ewpratten/protomask/tree/ewpratten/reorg2/libs/rfc6052/src
Hello @ewpratten, I appreciate you bringing up this issue. Personally, I'm not well-acquainted with rfc6052, and I plan to dedicate some time to thoroughly understand it. In the meantime, could you share a few use cases and elaborate on why you believe integrating rfc6052
would add value to cidr
? Additionally, does rfc6052
take into account both IPv4 and IPv6 (the intention behind cidr
is to be agnostic to both IPv4 and IPv6, offering features that naturally support both) ? I'll also be doing my research on this topic. Thanks again!
It would be nice to have support for
rfc6052
addresses, which follow a pretty weird format.Two commands (
rfc6052-pack
andrfc6052-extract
) would be handy.Heres an at-a-glance view of how this addressing scheme works:
Example syntax could be:
The first command would return an IPv6 address, and the second would return an IPv6 prefix, an IPv4 address, and an optional suffix. (or just error, if its invalid)