Netscape Certificate Management System 6.0, Manual

Page: 292 / 377

IssuerAlternativeName Rule
292 Netscape Certificate Management System Plug-Ins Guide • March 2002
• If the type is
ediPartyName
, the name must be an IA5String. For
example,
Example Corporation
.
• If the type is
URL
, the value must be a non-relative universal resource
identifier (URI) following the URL syntax and encoding rules specified
in RFC 1738 (
http://www.ietf.org/rfc/rfc1738.txt
). 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 the type is
iPAddress
, the value must be a valid IP address
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 the type is
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” for information on allocating private
OIDs. For example,
1.2.3.4.55.6.5.99
.
• If the type is
otherName
, the name must be must be the absolute path
to the file that contains the general name in its base-64 encoded format.
For example,
/usr/netscape/servers/extn/ian/othername.txt
.
Table 7-8
Description of parameters defined in the IssuerAlternativeName rule (Continued)
Parameter Description