You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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)
The text was updated successfully, but these errors were encountered: