Netscape MANAGEMENT SYSTEM 6.01 - PLUG-IN Manual page 161

Description of parameters defined in the CertificateScopeOfUseExt module (Continued)
Table 4-7
Parameter
entry<n>_name_type
entry<n>_name
Description
Specifies the general-name type for the site that you want to include in the
extension.
Permissible values: rfc822Name, directoryName, dNSName,
ediPartyName, URL, iPAddress, OID, or otherName.
• Select rfc822Name if the site is an Internet mail address.
• Select directoryName if the site is an X.500 directory name.
• Select dNSName if the site is a DNS name (default).
• Select ediPartyName if the site is a EDI party name.
• Select URL if the site is a uniform resource identifier.
• Select iPAddress if the site is an IP address.
• Select OID if the site is an object identifier.
• Select otherName if the site is in any other name form.
Example: URL
Specifies the general-name value for the site you want to include in the
extension.
Permissible values: Depends on the general-name type you selected in the
entry<n>_name_type field.
• If you selected rfc822Name, the value must be a valid Internet mail address
in the local-part@domain format; see the definition of an rfc822Name
as defined in RFC 822 (http://www.ietf.org/rfc/rfc0822.txt).
You may use upper and lower case letters in the mail address; no
significance is attached to the case. For example, webSite@example.com.
• If you selected directoryName, the value must be a string form of X.500
name, similar to the subject name in a certificate, in the RFC 2253 syntax (see
http://www.ietf.org/rfc/rfc2253.txt). Note that RFC 2253
replaces RFC 1779. For example: CN=corpDirectory, OU=IS,
O=example.com, C=US.
• If you selected dNSName, the value must be a valid domain name in the
preferred-name syntax as specified in 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, webSite.example.com.
CertificateScopeOfUseExt Plug-in Module
Chapter 4 Certificate Extension Plug-in Modules 161