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
As already mentioned, to specify an IPv6 non-global address without
ambiguity, an intended scope zone should be specified as well. As a
common notation to specify the scope zone, an implementation SHOULD
support the following format:
<address>%<zone_id>
where
<address> is a literal IPv6 address,
<zone_id> is a string identifying the zone of the address, and
`%' is a delimiter character to distinguish between <address> and
<zone_id>.
That prevents such IPv6 addresses from being used in org.bouncycastle.asn1.x509.GeneralName for example.
Are there any plans to support such IPv6 addresses in org.bouncycastle.asn1.x509.GeneralName?
The text was updated successfully, but these errors were encountered:
IPv6 addresses as described in https://datatracker.ietf.org/doc/html/rfc4007#section-11 are considered not valid by IPAddress#isValidIPv6
That prevents such IPv6 addresses from being used in
org.bouncycastle.asn1.x509.GeneralName
for example.Are there any plans to support such IPv6 addresses in
org.bouncycastle.asn1.x509.GeneralName
?The text was updated successfully, but these errors were encountered: