IPv6 support

You can learn more about IPv6 support through the information provided here.

Internet Protocol Version 6 (IPv6) is the protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 (IPv4). IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4 addresses. IPv6 uses a wider address (128-bit vs 32-bit) than IPv4, and this has an impact on the TCP application level. It also has improvements in areas such as routing and network autoconfiguration. IPv6 is expected to gradually replace IPv4.

All supported servers and clients for IBM® Security Directory Server 6.2 and above versions are enabled to support IPv6 as well as IPv4 nodes. The following examples show the format of LDAP URLs for IPv4 and IPv6 .

Note: If :portnumber is not specified in the URL, the default ports (389 for non-SSL and 636 for SSL) are used.

To use a literal IPv4 address in a URL, the format is x.x.x.x:port. An example of an LDAP server name in a URL for non-SSL communication listening on port 80 is:
- ldap://9.53.90.21:80
An example of an LDAP server name in a URL for SSL communication listening on the default port of 636 is:
- ldaps://9.53.90.21
To comply with RFC 2732, literal IPv6 address in URLs must be enclosed in [ and ] characters. Examples of LDAP server names in URLs for non-SSL communication listening on the respective ports of 80 and the default of 389 are:
- ldap://[107:0:0:0:200:7051]:80
- ldap://[::ffff:9.53.96.21]
Examples of LDAP server names in URLs for SSL communication listening on the respective ports of 80 and the default of 636 are:
- ldaps://[107:0:0:0:200:7051]:80
- ldaps://[::ffff:9.53.96.21]

Note:

If you are using the IPv6 URL format in a mixed environment with directory servers that are not IPv6 enabled, the IPv6 URL format is not recognized by the non-IPv6 enabled clients and servers. For example:
- Referals do not work if a non-IPv6 enabled client receives a URL address in the IPv6 format.
- Replication does not work if a non-IPv6 enabled consumer server receives its supplier URL information in the IPv6 format.
Linux™ systems require an interface ID for resolving the link-local IP address. The getaddrinfo or other interface conversion routines work, but then the resolved IP address does not work for the connect() function. Use the following format to specify an IP address with interfaces ID:
```
ldap://[xxxx:xxxx:xxxx:xxxx:xxxx%InterfaceID]
```
The link-local IPv6 address with scope:local does not work on Linux systems. IBM Security Directory Server version 6.2 and above supports scope:global only in IPv6 addresses on Linux systems.