[
https://issues.apache.org/jira/browse/DERBY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505450
]
Bernt M. Johnsen commented on DERBY-526:
----------------------------------------
Excellent observation Dag. I think that tying into RFC 3986 is an elegant idea,
it's forwards compatible, it is extensible wrt. future IP versions and it's
standards based. The full Derby host syntax in the URL would then be:
host = IP-literal / IPv4address / reg-name
port = *DIGIT
IP-literal = "[" ( IPv6address / IPvFuture ) "]"
IPvFuture = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" )
IPv6address = 6( h16 ":" ) ls32
/ "::" 5( h16 ":" ) ls32
/ [ h16 ] "::" 4( h16 ":" ) ls32
/ [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32
/ [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32
/ [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32
/ [ *4( h16 ":" ) h16 ] "::" ls32
/ [ *5( h16 ":" ) h16 ] "::" h16
/ [ *6( h16 ":" ) h16 ] "::"
h16 = 1*4HEXDIG
ls32 = ( h16 ":" h16 ) / IPv4address
IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet
> Network Client URL cannot take the IP Address as host name for IPV6 machines
> ----------------------------------------------------------------------------
>
> Key: DERBY-526
> URL: https://issues.apache.org/jira/browse/DERBY-526
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Affects Versions: 10.1.1.0
> Reporter: Kathey Marsden
>
> Network Client can not take the ip adrress as host name for
> IPV6 machines, sicne the ip address for those machines is of the format
> xx:xx:xx:xx:xx:xx:xx:xx:.
> The colons create a problem with our hostname:1527 format.
> The workaround is to use the host name for the server machine instead of the
> ip address
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
