Netscape MANAGEMENT SYSTEM 6.01 - PLUG-IN Manual page 185

Table 4-12 Description of parameters defined in the IssuerAltNameExt module (Continued)
Parameter Description
• If you selected dNSName, the value must be a valid domain name in the
preferred-name syntax as specified by RFC 1034
(http://www.ietf.org/rfc/rfc1034.txt). You may use upper
and lower case letters in the domain name; no significance is attached
to the case. Do not use the string " " for the DNS name. Also don't use
the DNS representation for Internet mail addresses; such identities
should be encoded as rfc822Name. For example,
testCA.example.com.
• If you selected ediPartyName, the value must be an IA5String. For
example, Example Corporation.
• If you selected URL, the value must be a non-relative universal resource
identifier (URI) following the URL syntax and encoding rules specified
in RFC 1738. That is, the name must include both a scheme (for
example, http) and a fully qualified domain name or IP address of the
host. For example, http://testCA.example.com.
• If you selected iPAddress, the value must be a valid IP address (IPv4
or IPv6) specified in dot-separated numeric component notation. The
syntax for specifying the IP address is as follows:
For IP version 4 (IPv4), the address should be in the form specified in
RFC 791 (http://www.ietf.org/rfc/rfc0791.txt). IPv4
address must be in the n.n.n.n format; for example, 128.21.39.40.
IPv4 address with netmask must be in the n.n.n.n,m.m.m.m format.
For example, 128.21.39.40,255.255.255.00.
For IP version 6 (IPv6), the address should be in the form described in
RFC 1884 (http://www.ietf.org/rfc/rfc1884.txt), with
netmask separated by a comma. Examples of IPv6 addresses with no
netmask are 0:0:0:0:0:0:13.1.68.3 and FF01::43. Examples of
IPv6 addresses with netmask are 0:0:0:0:0:0:13.1.68.3,FFFF:
FFFF:FFFF:FFFF:FFFF:FFFF:255.255.255.0 and
FF01::43,FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FF00:0000.
• If you selected OID, the value must be a unique, valid OID specified in
the dot-separated numeric component notation. Although you can
invent your own OIDs for the purposes of evaluating and testing this
server, in a production environment, you should comply with the ISO
rules for defining OIDs and for registering subtrees of IDs. See
Appendix B, "Object Identifiers"
private OIDs. For example, 1.2.3.4.55.6.5.99.
• If you selected otherName, the value must be the absolute path to the
file that contains the base-64 encoded string of the alternative name.
For example,
/usr/netscape/servers/ext/ian/othername.txt.
IssuerAltNameExt Plug-in Module
for information on allocating
Chapter 4 Certificate Extension Plug-in Modules 185